[Dev-luatex] Message for the impatient Apple users

Taco Hoekwater taco at elvenkind.com
Fri Dec 3 11:07:47 CET 2010

On 12/03/2010 10:53 AM, Mojca Miklavec wrote:
> On Fri, Dec 3, 2010 at 10:28, Khaled Hosny wrote:
>> On Fri, Dec 03, 2010 at 10:17:49AM +0100, Mojca Miklavec wrote:
>>> \definefontfeature
>>>    [default]
>>>    [liga=yes,kern=yes,tlig=yes,compose=yes]
>>> \definefontsynonym[hoefler][file:Hoefler Text.ttc][features=default]
>> Can this even work? AFAIK TTC is a collection of fonts, so you need to
>> select one of the fonts in the collection, may be:
>>   file:Hoefler Text.ttc(0)
> I have no idea if that can work or not. (I have never really looked
> into how the fonts are composed. But using the zero at the end doesn't
> help.)
> But apparently it does work, since I can make the character "ŏ"
> (obreve) appear with that strategy without a problem, it only crashes
> when the needed accent is missing.

If you call on a ttc in the way you do it, then you will get entry
zero in the ttc. It works (in general), but since you do not actually
know what font you are using, it is not a wise thing to do :)
It is better to always use name: for fonts inside collections.

> It seems that the accent "bottom dot", "bottom macron" are missing in
> Hoefler TeX (and most probably some other accents as well) and this is
> the reason why it "crashes".

I think it crashes because the 'compose' feature is modifying the node
list directly, thus bypassing the 'does this glyph exist' test in the
engine itself (that test runs at node creation time). Without
'compose=yes' it does not crash, just does not show anything.

Hans and I have to discuss how to handle this (whether it should be
the engine or the lua side doing the existance test to prevent the
crash) but Hans is not online today so it will have to wait for a bit.

Best wishes,

More information about the dev-luatex mailing list