ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vladimir Lomov <lomov.vl@gmail.com>
To: General mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Dubious "checksum mismatch" message on log file
Date: Wed, 1 Feb 2012 10:09:04 +0900	[thread overview]
Message-ID: <20120201010904.GH13420@smoon> (raw)

Hello,
please consider the following example:
<example file="ex8.tex">
\starttext

\font\test=txr \test abs

\stoptext
</example>

I process this document with context (context --version -> 2012.01.25)
nothing suspecious in terminal output but in log file I see "checksum mismatch",
<terminal>
$ grep 'checksum' ex8.log
checksum mismatch in font txr.vf ignored 
</terminal>

Simple plain tex file
<example file="ex9.tex">
\font\test=txr \test abs
\bye
</example>

processed by luatex and pdftex engines (both from TeX Live 2011, I don't know
how to generate formats for them in context suite) doesn't give same message.

Is it a "bug" in font system of context?

P.S. There is a thread on tex-live mailing list about "checksum mismatch",
I took a little investigation that reveals the source of problem:
'luaotfload', adaptation of context font system for latex world. As you
can see from "ex8.tex", current context have the same behaviour. I'm not
fully sure if it is save to ignore this message (I read briefly about vf
fonts here: http://www.tex.ac.uk/tex-archive/help/virtual-fonts.knuth)
but as both pdftex and luatex engines give nothing on "plain" example I
want to report about this issue.

--
WBR, Vladimir Lomov

-- 
That's the thing about people who think they hate computers.  What they
really hate is lousy programmers.
		-- Larry Niven and Jerry Pournelle in "Oath of Fealty"
___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2012-02-01  1:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01  1:09 Vladimir Lomov [this message]
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
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=20120201010904.GH13420@smoon \
    --to=lomov.vl@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).