From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: Dubious "checksum mismatch" message on log file
Date: Thu, 2 Feb 2012 09:54:43 +0100 [thread overview]
Message-ID: <2cxax36dyxez.dlg@nililand.de> (raw)
In-Reply-To: <20120201152309.GE3054@khaled-laptop>
Am Wed, 1 Feb 2012 17:23:09 +0200 schrieb Khaled Hosny:
> I tried printing the tfm table we pass to the backed, and the checksum
> matches the one in the VF file, so this is a bit confusing
Well I actually don't know what test is actually done (and why
exactly) but some remarks:
1. If I try to convert the binary "pplr7t.vf" to the readable
vpl-file I need *two* tfm-files: pplr7t.tfm and pplr8r.tfm.
2. vftovp tells me during the conversion:
"Check sum in VF file being replaced by TFM check sum"
which probably means that the vpl-file doesn't contain the original
checksum(s) of the vf-file.
3. The vpl file contains two checksums:
(CHECKSUM O 25136566211)
and a checksum in the mapfont entry:
(MAPFONT D 0
(FONTNAME pplr8r)
(FONTCHECKSUM O 36571141413)
(FONTAT R 1.0)
(FONTDSIZE R 10.0)
)
So which of both is actually checked against which tfm checksum (and
gives the mismatch message)?
Btw: Two years ago I ran against a checksum mismatch message
concerning the width of characters. In this case the culprit was a
different calculation method for tfm and vf:
http://tug.org/mailman/htdig/pdftex/2009-May/008035.html
--
Ulrike Fischer
___________________________________________________________________________________
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-02 8: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
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 [this message]
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=2cxax36dyxez.dlg@nililand.de \
--to=news3@nililand.de \
--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).