From: Hans Hagen <pragma@wxs.nl>
To: news3@nililand.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Dubious "checksum mismatch" message on log file
Date: Wed, 01 Feb 2012 15:22:58 +0100 [thread overview]
Message-ID: <4F294AC2.6040704@wxs.nl> (raw)
In-Reply-To: <1nnjepw9rlajm.dlg@nililand.de>
On 1-2-2012 15:15, Ulrike Fischer wrote:
> Am Wed, 1 Feb 2012 10:54:04 +0100 schrieb luigi scarso:
>
>> It's not related to MKIV but to luatex.
>
> I think it is related to MKIV (or more precisely to the fontloader).
>
> It is a bit difficult to demonstrate it with context (how to you use
> luatex without mkiv there?) but latex (or plain) it is quite easy:
>
> The followings examples load pplr7t.vf. Both give the checksum
> mismatch message in the log if and only if the lua-fontloader
> luaotfload it also loaded:
>
> %LaTeX
> \documentclass{article}
> \usepackage{luaotfload}
> \begin{document}
> \font\test=pplr7t \test abc
> \end{document}
>
> %plain
> \input luaotfload.sty
> \font\test=pplr7t \test abc
> \bye
>
> So the code from luaotfload (which is based on the context
> fontloader code) changes a checksum (either in the vf or in the
> tfm-information) and so the check in the luatex engines fails.
>
> (Imho it is only a minor problem, vf-fonts are not much used with
> luatex).
Afaik nothing is done with a checksum. There is a checksum field in the
loaded tfm but I don't think one has to be passed to luatex. Maybe one
should be passed when a regular tfm file is used but even then, loading
a vf file is independent.
So, it's best to just ignore that message.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 14:22 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 [this message]
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=4F294AC2.6040704@wxs.nl \
--to=pragma@wxs.nl \
--cc=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).