From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Dubious "checksum mismatch" message on log file
Date: Wed, 1 Feb 2012 10:54:04 +0100 [thread overview]
Message-ID: <CAG5iGsBO4HjMPbUVnS2512ax8cEioFtfChTj0zOAxH0HrTFRag@mail.gmail.com> (raw)
In-Reply-To: <20120201092131.GJ13420@smoon>
On Wed, Feb 1, 2012 at 10:21 AM, Vladimir Lomov <lomov.vl@gmail.com> wrote:
> Hello,
> ** luigi scarso [2012-02-01 08:45:18 +0100]:
>
>> On Wed, Feb 1, 2012 at 7:00 AM, Vladimir Lomov <lomov.vl@gmail.com> 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
--
luigi
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-02-01 9:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 1:09 Vladimir Lomov
2012-02-01 1:37 ` luigi scarso
2012-02-01 6:00 ` Vladimir Lomov
2012-02-01 7:45 ` luigi scarso
2012-02-01 9:21 ` Vladimir Lomov
2012-02-01 9:54 ` luigi scarso [this message]
2012-02-01 13:48 ` Vladimir Lomov
2012-02-01 14:04 ` luigi scarso
2012-02-02 1:28 ` Vladimir Lomov
2012-02-02 1:34 ` luigi scarso
2012-02-01 14:15 ` Ulrike Fischer
2012-02-01 14:22 ` Hans Hagen
2012-02-02 1:21 ` Vladimir Lomov
2012-02-02 8:43 ` Ulrike Fischer
2012-02-02 8:45 ` Hans Hagen
2012-02-01 14:47 ` luigi scarso
2012-02-01 15:51 ` Khaled Hosny
2012-02-01 15:23 ` Khaled Hosny
2012-02-02 8:54 ` Ulrike Fischer
2012-02-02 12:30 ` luigi scarso
2012-02-02 14:47 ` luigi scarso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAG5iGsBO4HjMPbUVnS2512ax8cEioFtfChTj0zOAxH0HrTFRag@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).