From: Lutz Haseloff <lutz.haseloff@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lower case "a" incompatible with hanging
Date: Mon, 21 Dec 2009 09:20:58 +0100 [thread overview]
Message-ID: <a09128560912210020s3b1e261ei988717e801539746@mail.gmail.com> (raw)
In-Reply-To: <4B2CBF95.3020309@elvenkind.com>
[-- Attachment #1.1: Type: text/plain, Size: 1817 bytes --]
2009/12/19 Taco Hoekwater <taco@elvenkind.com>
> Hi,
>
> This was a bug in luatex: the function that copies the font
> information from the base font to the expanded font did not
> copy the last glyph at all. There is a one-character patch to
> trunk/source/texk/web2c/luatexdir/font/texfont.c:
>
>
> @@ -1094,7 +1094,7 @@
> memcpy(math_param_base(k), math_param_base(f), i);
> }
>
> - for (i = 0; i < font_tables[f]->charinfo_count; i++) {
> + for (i = 0; i <= font_tables[f]->charinfo_count; i++) {
> ci = copy_charinfo(&font_tables[f]->charinfo[i]);
> font_tables[k]->charinfo[i] = *ci;
> }
>
> And that fixes it.
>
> The only oddness with this particular font is that the 'a' happens
> to be its last glyph in the ordering of the glyph implementations
> inside the otf file. Usually, the last of those is something odd
> like an alternate or a designer' logo, which is probably why nobody
> noticed before.
>
>
> Lutz Haseloff wrote:
>
>> Hi Michael,
>>
>> Your file works here without problems with the same ConTeXt and
>> LuaTeX, Version beta-0.47.0-2009121623.
>>
>
> That's weird, did you use Michaels font?
>
>
I don't think so:
My OctavianMTStd.otf:
Version 2.040;PS 002.000;honconv 1.0.51;makeotf.lib 2.0.18671
Greetings Lutz
> 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 : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 3062 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-12-21 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 21:38 Michael Green
2009-12-18 10:29 ` Lutz Haseloff
2009-12-19 11:57 ` Taco Hoekwater
2009-12-21 8:20 ` Lutz Haseloff [this message]
[not found] <mailman.1.1261393203.2155.ntg-context@ntg.nl>
2009-12-21 14:22 ` Michael Green
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=a09128560912210020s3b1e261ei988717e801539746@mail.gmail.com \
--to=lutz.haseloff@googlemail.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).