ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Dubious "checksum mismatch" message on log file
Date: Wed, 1 Feb 2012 17:51:02 +0200	[thread overview]
Message-ID: <20120201155102.GA3732@khaled-laptop> (raw)
In-Reply-To: <CAG5iGsDecAYrw_8nNDRO0FyEz1jenxq_BxUB=in5e7iyxJ4V4g@mail.gmail.com>

On Wed, Feb 01, 2012 at 03:47:32PM +0100, luigi scarso wrote:
> On Wed, Feb 1, 2012 at 3:15 PM, Ulrike Fischer <news3@nililand.de> 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).
> The message can be reproduced also with luatex --fmt=luatex-plain.fmt
> The font structure has a key checksum, but luatex doesn't use e by
> default is zero
>                 from vf from tfm used value type
> checksum yes     yes          no    number     default: 0
> So maybe font_checksum is zero, and checksum is 32212676346
> (i.e. the opposite that I wrote).

So now that is a question to Taco, if checksum is not used by luatex,
why id there a difference when the font is loaded in the old way (i.e.
no callbacks involved) and when it is loaded define_font callback?

Regards,
 Khaled
___________________________________________________________________________________
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 15:51 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 [this message]
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=20120201155102.GA3732@khaled-laptop \
    --to=khaledhosny@eglug.org \
    --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).