From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: an ugly bug
Date: Tue, 22 May 2007 19:40:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.WNT.0.99.0705221939340.3656@nqvgln> (raw)
In-Reply-To: <op.tsqgs8whnx1yh1@your-b27fb1c401>
On Tue, 22 May 2007, Idris Samawi Hamid wrote:
> Hi Taco,
>
> On Tue, 22 May 2007 01:39:55 -0600, Taco Hoekwater <taco@elvenkind.com>
> wrote:
>
>>>>> This is an ugly bug; The right kerning of the the numeral '1' is
>>>>> really
>>>>> bad:
>>>> The latin-modern-os typescript uses the widths of the table figures
>>>> with the oldstyle shapes, because latin modern does not ship with
>>>> correct metrics for oldstyle digits.
>>>
>>> So it's an lm bug then. Any possibility of getting it fixed, or sending
>>> the maintainers an urgent note (might be more effective coming from you
>>> or
>>> Hans)?
>>
>> If you want these metrics, it makes sense to drop them a note. But no
>> way are they going to create new metrics for you before next Thursday,
>> so we had better come up with something else. I can create a bunch of
>> metrics for you, but I do not have time to create hundreds of these
>> by hand, so tell me: are you using 'modern-base, texnansi' in your
>> actual project as well?
>
> Here is my exact setup for the project:
>
> =====================
> \usetypescript[serif,sans,mono][hanging][hz,normal]
> \setupalign[hz,hanging]
> \usetypescript[modern-base][texnansi] % a simplified latin-modern
> typescript
> \usetypescript [map] [latin-modern-os] [texnansi]
> \setupbodyfont[reset]
> \setupbodyfont[modern,11pt]
> =====================
>
> 2 problems:
>
> i) bad kerning (subject of this thread);
>
> ii) \type gives way to complaints about missing numerals in lmtt10 (see
> other thread "oldstyle bug"). Apparently the <numeral>.oldstyle glyphs
> have been renamed <numeral>.taoldstyle. WHY ON EARTH would they do that?!?
> Didn't the maintainers realize this would break things? It certainly makes
> encoding font collections more difficult.
>
> This is a journal so I need to maintain consistency: can't go back to
> upright.
Maybe as a temporary workaround, try to get old lmodern files and use
them instead. I do not know if they are archived somewhere or not.
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2007-05-22 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 18:52 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 ` Latin Modern bug in lm-texnansi-os.enc Taco Hoekwater
2007-05-22 23:40 ` Aditya Mahajan [this message]
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=alpine.WNT.0.99.0705221939340.3656@nqvgln \
--to=adityam@umich.edu \
--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).