From: Taco Hoekwater <taco@elvenkind.com>
To: "Bogusław Jackowski" <b.jackowski@bop.com.pl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Idris Samawi Hamid <ishamid@colostate.edu>,
tex-live@tug.org
Subject: Latin Modern bug in lm-texnansi-os.enc
Date: Tue, 22 May 2007 21:34:22 +0200 [thread overview]
Message-ID: <465345BE.6020207@elvenkind.com> (raw)
In-Reply-To: <op.tsqgs8whnx1yh1@your-b27fb1c401>
Hi Jacko,
On the ConTeXT mailing list, Idris posted some messages because he was
trying to use oldstyle numerals in the latest Latin Modern release,
and was experiencing two pretty big problems:
* really bad kerning around the oldstyle numerals
* pdftex generated errors for the typewriter fonts, complaining
"glyph `one.oldstyle' undefined" etc.
The implementation of 'automatic' oldstyle numbers in ConTeXt uses a
set of encoding files that used to ship with LM (lm-xxxxxx-os.enc).
By way of a map file fragment, this allows to switch the fonts
'en masse' from lining to oldstyle (and back) without the need for
special metric files, which is a pretty nice feature.
Those encoding files now apparently obsolete: they still refer to
glyphs named e.g. `one.oldstyle', whereas in the current release of
the LM fonts it really should be `one.taboldstyle'.
While writing a bug report, I noticed that these encoding files are no
longer in the font distribution (They are still included on texlive2007,
but I don't know if anybody except ConTeXt attempts to use them).
Is this trick to get oldstyle now officially unsupported? That would
be a shame, because there are no oldstyle-using TFM files in the LM
distribution either ...
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:[~2007-05-22 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 18:52 an ugly bug Idris Samawi Hamid
2007-05-21 10:43 ` Taco Hoekwater
2007-05-21 22:12 ` Idris Samawi Hamid
2007-05-22 7:39 ` Taco Hoekwater
2007-05-22 14:49 ` Idris Samawi Hamid
2007-05-22 19:34 ` Taco Hoekwater [this message]
2007-05-22 23:40 ` Aditya Mahajan
2007-05-24 13:48 Latin Modern bug in lm-texnansi-os.enc bop
2007-05-24 15:56 ` Taco Hoekwater
2007-05-25 10:47 ` bop
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=465345BE.6020207@elvenkind.com \
--to=taco@elvenkind.com \
--cc=b.jackowski@bop.com.pl \
--cc=ishamid@colostate.edu \
--cc=ntg-context@ntg.nl \
--cc=tex-live@tug.org \
/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).