Hi, It seems that commits 4019 & 4021 have finally fixed the use of Snow Leopard's .ttc system fonts! Best wishes, Taco
On 11/30/2010 04:11 PM, Taco Hoekwater wrote:
Hi,
It seems that commits 4019 & 4021 have finally fixed the use of Snow Leopard's .ttc system fonts!
.. not that it actually does you much good now, because an incompatible change in luafilesystem means that both context and luaotfload.sty now fail to recreate the font index, but still ... I am really happy.
On Tue, Nov 30, 2010 at 16:19, Taco Hoekwater wrote:
On 11/30/2010 04:11 PM, Taco Hoekwater wrote:
It seems that commits 4019 & 4021 have finally fixed the use of Snow Leopard's .ttc system fonts!
.. not that it actually does you much good now, because an incompatible change in luafilesystem means that both context and luaotfload.sty now fail to recreate the font index, but still ... I am really happy.
Taco, thanks a lot for the good news.
However - what exactly does the following mean?
)
On Fri, Dec 03, 2010 at 10:17:49AM +0100, Mojca Miklavec wrote:
On Tue, Nov 30, 2010 at 16:19, Taco Hoekwater wrote:
On 11/30/2010 04:11 PM, Taco Hoekwater wrote:
It seems that commits 4019 & 4021 have finally fixed the use of Snow Leopard's .ttc system fonts!
.. not that it actually does you much good now, because an incompatible change in luafilesystem means that both context and luaotfload.sty now fail to recreate the font index, but still ... I am really happy.
Taco, thanks a lot for the good news.
However - what exactly does the following mean?
)
Fatal error occurred, no output PDF file produced! Test file was the following:
\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) Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer
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. 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". However, it is not clear to me whether it is more appropriate for LuaTeX to crash or to ignore that (if it crashes at least the user notices that something is wrong). If I use "\textbottomaccent" per-se then LuaTeX doesn't crash (should it?), it just doesn't output anything. So: I'm really not sure whether it should be ConTeXt or LuaTeX that should take care of missing glyphs ... And I'm not sure if there is some simple way to fake accents such as bottom dot or bottom macron as well (providing some explicit font-specific settings). But this is something for the ConTeXt gurus (or maybe for your packages), not for luatex-dev. Mojca
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, Taco
participants (3)
-
Khaled Hosny -
Mojca Miklavec -
Taco Hoekwater