Re: [NTG-context] Dubious "checksum mismatch" message on log file

1 Feb 2012

      Hello,
** luigi scarso [2012-02-01 10:54:04 +0100]:
...
On Wed, Feb 1, 2012 at 10:21 AM, Vladimir Lomov  wrote:
...
Hello,
** luigi scarso [2012-02-01 08:45:18 +0100]:
...
...
...
On Wed, Feb 1, 2012 at 7:00 AM, Vladimir Lomov  wrote:
...
...
...
...
I specially chose that font (txr, txr.tfm and txr.vf files), it is
distributed by txfonts "package". May be you installation doesn't have
them because I installed context suite with './first-setup.sh --modules=all'.
...
...
...
...
Nevertheless, that 'Font ... at 600 ...' reminds me how pdftex (pdflatex
actually) deals with tfm/mf/pk fonts (generate pk and insert them into
pdf file).
Even with --modules=all'
LuaTeX warning (file rtxptmr): Font rtxptmr at 600 not found
and
$> pdffonts test.pdf
...
...
...
name                                 type              emb sub uni object ID
------------------------------------ ----------------- --- --- --- ---------
Error: font resource is not a dictionary
JFRMQG+LMRoman10-Regular             CID Type 0C       yes yes yes     18  0
...
...
...
It seems that this font is not a font of the suite.
...
...
Let me stess it in other words: this ("Font ... not found") is not the
topic of thread. It is completely inrelated (IMHO) with vf font
problem (vf font leads to that "checksum" message). I took that font
because it has corresponding vf file.
ok it was just to have as much data as possible.
...
We have
...
$>vftovp txr.vf
(VTITLE )
(FAMILY TXR)
(FACE F MRR)
(CODINGSCHEME TEX TEXT)
(DESIGNSIZE R 10.0)
(COMMENT DESIGNSIZE IS IN POINTS)
(COMMENT OTHER SIZES ARE MULTIPLES OF DESIGNSIZE)
(CHECKSUM O 32212676346)
...
while from  luatex source
...
source/texk/web2c/luatexdir/font/vfovf.w:
@ process a local font in \.{VF} file
@c
static internal_font_number
vf_def_font(internal_font_number f, unsigned char *vf_buffer, int *vf_cr)
{
:
unsigned long checksum;
    cs.b0 = vf_buffer[(*vf_cr)];
    cs.b1 = vf_buffer[(*vf_cr) + 1];
    cs.b2 = vf_buffer[(*vf_cr) + 2];
    cs.b3 = vf_buffer[(*vf_cr) + 3];
    (*vf_cr) += 4;
    checksum = (unsigned)
        (cs.b0 * 256 * 256 * 256 + cs.b1 * 256 * 256 + cs.b2 * 256 + cs.b3);
:
...
if (checksum != 0 && font_checksum(k) != 0
            && checksum != font_checksum(k))
            vf_local_font_warning(f, k, "checksum mismatch", (int) checksum,
                                  (int) font_checksum(k));
        if (ds != font_dsize(k))
            vf_local_font_warning(f, k, "design size mismatch", ds,
                                  font_dsize(k));
...
It's not related to MKIV but to luatex, and it's a warning.
It doesn't even matter to have --modules==all, this vf file  in the
standard standalone.
Of course you must have the pfb/afm or otf or ttf file, as usual,
otherwise the pdf is wrong
I was not sure, that why I began this thread. I started with latex example,
then strip it down to plain tex one and after that came to context
minimal example.

AFAIU, context suite doesn't have "plain" pdftex and luatex formats,
therefore I compile minimal plain tex example with TeX Live 2011, and
luatex doesn't print such message though it reads vf file.

The problem indeed may be it luatex and how it works with vf fonts, but
as I said, I'm not sure (don't know very well either plain tex or context).

P.S. Unrelated: seems I completely lost, I read web sources, the
quoted extract from luatex source and I don't understand how this
number '32212676346' can be presented as

cs.b0 * 256 * 256 * 256 + cs.b1 * 256 * 256 + cs.b2 * 256 + cs.b3

If I don't lose my math skills the '32212676346' is
32212676346=7·256^{4}+128·256^{3}+6·256^{2}+110·256^{1}+250·256^{0}

---
WBR, Vladimir Lomov

-- 
If only God would give me some clear sign!  Like making a large deposit
in my name at a Swiss bank.
		-- Woody Allen, "Without Feathers"