From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Serious bug?
Date: Tue, 23 Dec 2008 19:30:50 +0100 [thread overview]
Message-ID: <49512E5A.6050002@elvenkind.com> (raw)
In-Reply-To: <4950DA7A.60805@elvenkind.com>
Taco Hoekwater wrote:
> Alan STONE wrote:
>> I did a clean minimals install on my Windows XP Home SP3 system and
>> get the same strange output.
>>
>> ConTeXt ver: 2008.11.10 21:40 MKIV fmt: 2008.12.22 int: english/english
>> This is LuaTeX, Version snapshot-0.31.2-2008121200, build 1659
>>
>> texmfstart texexec --lua hello
>> context.cmd --lua hello
>>
>> C:\context\tex\texmf-cache\luatex-cache\context\2fea56f92e5267d7cc9662e4d5f52e1e\fonts\otf\lmroman12-regular.tma
>>
>> C:\context\tex\texmf\fonts\opentype\public\lm\lmroman12-regular.otf
>>
>> mailed to Taco.
>
> Thanks, got them. More later, but at first glance the tma does not look
> all that weird.
Short update on the files people sent me:
* the otf file is identical,
* the tma and tmc seem fine
It seems that somehow, when the tmc is read in, context (i.e. luatex)
misinterprets the numeric values in the bytecode completely, resulting
in ridiculous values for character widths, heights, depths etc.
I am afraid I still have no idea why this happens.
Best wishes,
Taco
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-12-23 18:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 7:19 Fengnan Gao
2008-12-21 11:08 ` Yue Wang
2008-12-22 19:24 ` Alan STONE
2008-12-23 12:32 ` Taco Hoekwater
2008-12-23 18:30 ` Taco Hoekwater [this message]
2008-12-24 2:45 ` Fengnan Gao
2008-12-24 10:29 ` Mojca Miklavec
2008-12-24 13:49 ` Alan STONE
2008-12-22 23:05 ` Mojca Miklavec
2008-12-23 12:31 ` Taco Hoekwater
2008-12-24 10:03 ` Taco Hoekwater
2008-12-24 12:54 ` Alan STONE
2008-12-24 13:21 ` Taco Hoekwater
2008-12-24 16:32 ` Alan STONE
2008-12-26 8:40 ` Taco Hoekwater
2008-12-23 15:21 ` Derek CORDEIRO
2008-12-23 15:28 ` Derek CORDEIRO
2008-12-21 12:58 Fengnan Gao
2008-12-21 14:18 ` Yue Wang
2008-12-21 14:28 ` Fengnan Gao
2008-12-22 1:53 ` Fengnan Gao
2008-12-22 7:26 ` Mojca Miklavec
2008-12-22 7:35 ` Mojca Miklavec
2008-12-21 14:26 ` Hans Hagen
2008-12-21 20:52 ` Mojca Miklavec
2008-12-22 9:58 ` Taco Hoekwater
2008-12-21 14:36 Fengnan Gao
2008-12-22 12:56 Fengnan Gao
2008-12-22 16:04 ` Mojca Miklavec
2008-12-23 18:22 ` Taco Hoekwater
2008-12-24 13:27 ` Alan STONE
2008-12-22 17:55 ` Taco Hoekwater
2008-12-22 18:25 ` Taco Hoekwater
2008-12-22 18:57 Tad Ashlock
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=49512E5A.6050002@elvenkind.com \
--to=taco@elvenkind.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).