Re: [NTG-context] Fontloader
On 5/25/2019 9:46 PM, Herbert Voss wrote: I had a problem with the fontloader and luatex. I tried to run my test document with context (latest minimal) to compare the output, but I failed. The font LibertinusKeyboard-Regular.otf https://ctan.org/tex-archive/fonts/libertinus-fonts/ uses ligatures especially for the keys above 0x However, I cannot get it run with latest mkiv. It is no problem with xetex. It should print only the five keys and not the ones for every single letter. Herbert \font\keyboard=LibertinusKeyboard-Regular.otf \starttext \keyboard Tab Entf Enter Capslock Windows \stoptext I'll look into it. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Fontloader
Am Sat, 25 May 2019 21:46:46 +0200 schrieb Herbert Voss: > The font LibertinusKeyboard-Regular.otf > https://ctan.org/tex-archive/fonts/libertinus-fonts/ > uses ligatures especially for the keys above 0x > However, I cannot get it run with latest mkiv. as was noticed by Zauguin in https://github.com/u-fischer/luaotfload/issues/60 a work-around it to suppress hyphenation: \font\keyboard=LibertinusKeyboard-Regular.otf:mode=node;+liga \hyphenchar\keyboard=-1 \starttext \keyboard Tab Entf Enter Capslock Windows \stoptext -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Fontloader
I had a problem with the fontloader and luatex. I tried to run my test document with context (latest minimal) to compare the output, but I failed. The font LibertinusKeyboard-Regular.otf https://ctan.org/tex-archive/fonts/libertinus-fonts/ uses ligatures especially for the keys above 0x However, I cannot get it run with latest mkiv. It is no problem with xetex. It should print only the five keys and not the ones for every single letter. Herbert \font\keyboard=LibertinusKeyboard-Regular.otf \starttext \keyboard Tab Entf Enter Capslock Windows \stoptext ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] fontloader error in latex: attempt to call upvalue 'getdirection' (a nil value)
Am Fri, 11 Jan 2019 22:51:30 +0100 schrieb Hans Hagen: > afaiks it's ok for luatex 1.09+ Oh, good tipp. You are right with luatex 1.09 it compiles fine. That means that I don't need to debug but should stick to the state of 2018-12-19 until texlive 2019 comes out. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] fontloader error in latex: attempt to call upvalue 'getdirection' (a nil value)
On 1/11/2019 8:23 PM, Ulrike Fischer wrote: Am Thu, 10 Jan 2019 17:13:26 +0100 schrieb Pablo Rodriguez: On 1/7/19 12:40 AM, Ulrike Fischer wrote: I just tried to import the fontloader from 2019-01-03 into latex, and get on a simple document the error (./test-utf8.aux)error: ...ad/texmf/tex/luatex/luaotfload/fontloader-2019-01-03.lua:23868: attempt to call upvalue 'getdirection' (a nil value) [...] I have no idea (yet) if this is latex specific or if it could affect context too but thought I better mention it. The line refers to this part of the code: pardirstate=function(start) local nxt=getnext(start) local dir=getdirection(start) --<-- if dir==lefttoright then return nxt,1,1 Many thanks for your report, Ulrike. This was the same problem that prevented the compilation of the following code: \setupdirections[bidi=on, method=two] \starttext \input zapf \stoptext After your report, Hans fixed the issue Well not for generic. I tried yesterday the context state from 2019-01-07 and still have the problem that getdirection is called somewhere but actually nil. But I don't have the time to investigate or to try to create a generic example currently. afaiks it's ok for luatex 1.09+ (i have no time now either) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] fontloader error in latex: attempt to call upvalue 'getdirection' (a nil value)
Am Thu, 10 Jan 2019 17:13:26 +0100 schrieb Pablo Rodriguez: > On 1/7/19 12:40 AM, Ulrike Fischer wrote: >> I just tried to import the fontloader from 2019-01-03 into latex, >> and get on a simple document the error >> >> (./test-utf8.aux)error: >> ...ad/texmf/tex/luatex/luaotfload/fontloader-2019-01-03.lua:23868: >> attempt to call upvalue 'getdirection' (a nil value) >> [...] >> I have no idea (yet) if this is latex specific or if it could affect >> context too but thought I better mention it. The line refers to this >> part of the code: >> >> pardirstate=function(start) >> local nxt=getnext(start) >> local dir=getdirection(start) --<-- >> if dir==lefttoright then >> return nxt,1,1 > > Many thanks for your report, Ulrike. > > This was the same problem that prevented the compilation of the > following code: > > \setupdirections[bidi=on, method=two] > \starttext > \input zapf > \stoptext > > After your report, Hans fixed the issue Well not for generic. I tried yesterday the context state from 2019-01-07 and still have the problem that getdirection is called somewhere but actually nil. But I don't have the time to investigate or to try to create a generic example currently. -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] fontloader error in latex: attempt to call upvalue 'getdirection' (a nil value)
On 1/10/2019 5:13 PM, Pablo Rodriguez wrote: This was the same problem that prevented the compilation of the following code: \setupdirections[bidi=on, method=two] \starttext \input zapf \stoptext this is unlikely as you don't use generic ... probably another fix (concerning your mails: gmx is kind of special i think ... i can never send mails that gmx adresses) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] fontloader error in latex: attempt to call upvalue 'getdirection' (a nil value)
On 1/7/19 12:40 AM, Ulrike Fischer wrote: > I just tried to import the fontloader from 2019-01-03 into latex, > and get on a simple document the error > > (./test-utf8.aux)error: > ...ad/texmf/tex/luatex/luaotfload/fontloader-2019-01-03.lua:23868: > attempt to call upvalue 'getdirection' (a nil value) > [...] > I have no idea (yet) if this is latex specific or if it could affect > context too but thought I better mention it. The line refers to this > part of the code: > > pardirstate=function(start) > local nxt=getnext(start) > local dir=getdirection(start) --<-- > if dir==lefttoright then > return nxt,1,1 Many thanks for your report, Ulrike. This was the same problem that prevented the compilation of the following code: \setupdirections[bidi=on, method=two] \starttext \input zapf \stoptext After your report, Hans fixed the issue (which I tried to report twice, but the mailing list rejected my messages). Many thanks for your report and for the fix from Hans, Pablo -- http://www.ousia.tk ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] fontloader error in latex: attempt to call upvalue 'getdirection' (a nil value)
I just tried to import the fontloader from 2019-01-03 into latex,
and get on a simple document the error
(./test-utf8.aux)error:
...ad/texmf/tex/luatex/luaotfload/fontloader-2019-01-03.lua:23868:
attempt to call upvalue 'getdirection' (a nil value)
.
\newpage ...k \@nobreakfalse \everypar {}\fi \par
\ifdim \prevdepth
>\z@ \vs...
l.51 \end{document}
I have no idea (yet) if this is latex specific or if it could affect
context too but thought I better mention it. The line refers to this
part of the code:
pardirstate=function(start)
local nxt=getnext(start)
local dir=getdirection(start) --<--
if dir==lefttoright then
return nxt,1,1
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] fontloader fails with "bad argument #1 to 'for iterator"
Am Sat, 18 Aug 2018 13:47:32 +0200 schrieb Hans Hagen: >> On the luaotfload tracker was a bug report that the loading of a >> font failed if too many character variant were requested >> >> https://github.com/lualatex/luaotfload/issues/424 >> >> I wanted to check if the problem still exist with a current >> fontloader. Here (both context and latex) the loading of this fonts >> fails even if no character variants at all are requested: > What are character variants? Anyway, if it's "features" there is no > relation between choosing features and loading a font. As far as I got it they are open type features to select variants of characters and are used as any other open type feature: ;+cv01=0;+cv02=0;+cv03=0;+cv04=0;+cv05=0;+cv06=0;... In the bug report the problem seemed to be that the user used so many of this features that some string got too long. But due to the other error I couldn't look at it yet. >> it is in the 07-iosevka-type-slab-2.0.0.zip. > Hm, another of these N x M instance fonts generated from a common > source? I can catch the bad coverage table but it will never render okay. Thanks. And I will forwared the warning ;-). -- Ulrike Fischer https://www.troubleshooting-tex.de/ ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] fontloader fails with "bad argument #1 to 'for iterator"
On 8/18/2018 1:17 PM, Ulrike Fischer wrote:
On the luaotfload tracker was a bug report that the loading of a
font failed if too many character variant were requested
https://github.com/lualatex/luaotfload/issues/424
I wanted to check if the problem still exist with a current
fontloader. Here (both context and latex) the loading of this fonts
fails even if no character variants at all are requested:
What are character variants? Anyway, if it's "features" there is no
relation between choosing features and loading a font.
\starttext
\font\x={file:iosevka-type-slab-regular.ttf}
\x
ablub
\stoptext
gives
...ext/tex/texmf-context/tex/context/base/mkiv/font-oup.lua:2137:
bad argument #1 to 'for iterator' (table expected, got nil)
The font can be get from
https://github.com/be5invis/Iosevka/releases
it is in the 07-iosevka-type-slab-2.0.0.zip.
Hm, another of these N x M instance fonts generated from a common
source? I can catch the bad coverage table but it will never render okay.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] fontloader fails with "bad argument #1 to 'for iterator"
On the luaotfload tracker was a bug report that the loading of a
font failed if too many character variant were requested
https://github.com/lualatex/luaotfload/issues/424
I wanted to check if the problem still exist with a current
fontloader. Here (both context and latex) the loading of this fonts
fails even if no character variants at all are requested:
\starttext
\font\x={file:iosevka-type-slab-regular.ttf}
\x
ablub
\stoptext
gives
...ext/tex/texmf-context/tex/context/base/mkiv/font-oup.lua:2137:
bad argument #1 to 'for iterator' (table expected, got nil)
The font can be get from
https://github.com/be5invis/Iosevka/releases
it is in the 07-iosevka-type-slab-2.0.0.zip.
--
Ulrike Fischer
https://www.troubleshooting-tex.de/
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] [fontloader/old] mixed substitution / ligatures feature
·
> On 12/18/2015 7:34 AM, Philipp Gesang wrote:
> > in the old loader, defining a feature containing mixed ligature /
> > substitution causes a crash. Here’s an example:
> >
> > \enabletrackers [otf.loading]
> > \startluacode
> >fonts.handlers.otf.addfeature ("dunno", {
> >{
> >type = "substitution",
> >data = { [0x0022] = 0x201D },
> >prepend = true,
> >},
> >{
> >type = "ligature",
> >data = { [0x2013] = {0x002D, 0x002D} },
> >prepend = true,
> >},
> >})
> >fonts.handlers.otf.features.register {
> >name= "dunno",
> >description = "bug demo",
> >}
> > \stopluacode
> >
> > \definefontfeature [myfeat] [default] [dunno=yes,liga=yes,mode=node]
> >
> > \definefont [somefont] [file:cmunrm.otf*myfeat]
> > \starttext
> >\somefont foo bar " baz
> > \stoptext
> >
> > This crashes in font-otn on account of a number being indexed.
> > This used to work -- anything that can be done about it?
>
> i'll see if i can fix it but don't expect all upcoming features in the
> new loader to work in the old one
Thanks for fixing the crash. However, the substitution doesn’t
work as defined, even if there’s no ligature. It does work with
the TL 2015 version. As it doesn’t seem work with the new loader
either I guess this is related to the “em-dashes not working …”
issue :)
Best,
Philipp
pgpRVRpA2YYGA.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] [fontloader/old] mixed substitution / ligatures feature
On 12/18/2015 7:34 AM, Philipp Gesang wrote:
Hi Hans,
in the old loader, defining a feature containing mixed ligature /
substitution causes a crash. Here’s an example:
\enabletrackers [otf.loading]
\startluacode
fonts.handlers.otf.addfeature ("dunno", {
{
type = "substitution",
data = { [0x0022] = 0x201D },
prepend = true,
},
{
type = "ligature",
data = { [0x2013] = {0x002D, 0x002D} },
prepend = true,
},
})
fonts.handlers.otf.features.register {
name= "dunno",
description = "bug demo",
}
\stopluacode
\definefontfeature [myfeat] [default] [dunno=yes,liga=yes,mode=node]
\definefont [somefont] [file:cmunrm.otf*myfeat]
\starttext
\somefont foo bar " baz
\stoptext
This crashes in font-otn on account of a number being indexed.
This used to work -- anything that can be done about it?
i'll see if i can fix it but don't expect all upcoming features in the
new loader to work in the old one
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
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
___
[NTG-context] [fontloader/old] mixed substitution / ligatures feature
Hi Hans,
in the old loader, defining a feature containing mixed ligature /
substitution causes a crash. Here’s an example:
\enabletrackers [otf.loading]
\startluacode
fonts.handlers.otf.addfeature ("dunno", {
{
type = "substitution",
data = { [0x0022] = 0x201D },
prepend = true,
},
{
type = "ligature",
data = { [0x2013] = {0x002D, 0x002D} },
prepend = true,
},
})
fonts.handlers.otf.features.register {
name= "dunno",
description = "bug demo",
}
\stopluacode
\definefontfeature [myfeat] [default] [dunno=yes,liga=yes,mode=node]
\definefont [somefont] [file:cmunrm.otf*myfeat]
\starttext
\somefont foo bar " baz
\stoptext
This crashes in font-otn on account of a number being indexed.
This used to work -- anything that can be done about it?
Best,
Philipp
pgpQqZnXSG9S_.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] [fontloader] crash in font-otf.lua / actions["reorganize glyph anchors"]
· > this bug was reported a while ago by user Thérèse on > tex.stackexchange.com [1]. The font “Eadui.ttf” [2] causes the > fontloader to access a nil value because the “Anchor-1” table is > sparse (nil at index 3). Test file for Context: > > https://bitbucket.org/phg/lua-la-tex-tests/src/tip/cnt-eadui.tex > > Patch attached, though I suspect it covers only the symptoms. Thanks for fixing! Philipp pgpvIrypMFNZK.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] [fontloader] node injector / december 3 sync
·
> On 12/14/2014 2:45 PM, Philipp Gesang wrote:
> > Hi Hans,
> >
> > from the huge changeset two weeks ago:
> >
> > +texio.write_nl("The font code has been brought in sync with the
> > context version of 2014.12.01 so")
> > +texio.write_nl("if things don't work out as expected the interfacing
> > needs to be checked. When")
> >
> > -- Message received ;) First off, thanks for bringing the
> > fontloader into sync again. So far I haven’t noticed any
> > obviously broken features.
> >
> > However, something is off with the node injector. We have a bug
> > reported by Hironori Kitagawa that occurs with the ``palt``
> > feature in node mode:
> >
> > http://tug.org/pipermail/luatex/2014-November/004976.html
> >
> > Importing the shiny new font injector into the merged fontloader
> > fixes the issue. FWIW here are test files
> >
> >
> > https://bitbucket.org/phg/lua-la-tex-tests/src/tip/cnt-features-12-palt.tex
> >
> > https://bitbucket.org/phg/lua-la-tex-tests/src/tip/pln-features-12-palt.tex
> >
> > The Context version runs fine whereas the plain one does so only
> > after my “fix”. The same is true for Context itself: replace
> > font-inj.lua with node-inj.lua in the format to reproduce the
> > issue. Is there a fix to the fontloader, perhaps only temporarily
> > until the revised injector becomes ready?
>
> not really as the new injector does more ... also, the new code is kind
> of beta so it might not be a good idea to use that in latex already ...
The current goal is to add an option to load the code directly
from Context (TL, minimals). Right now this is non-trivial due to
the extra packaging step involved, so the option will facilitate
testing a lot. Let’s see if anyone is confident enough to test
the fontloader on their own if it becomes easier.
> so, i'd first like to do more tests here; of course you can use the new
> injector if you want ... (i'm not touching generic now while messing
> with the context variant)
Just running my tests ;) I’m fairly content with the prospect
that the issue is already addressed in the beta.
Philipp
pgpkr10ge7yCf.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] [fontloader] positioning of diacritics
· > Am 15.12.2014 um 21:43 schrieb Philipp Gesang: > > >> \enabletrackers[otf.bugs] > > > > Thanks for the reply and for the pointer. That tracker is indeed > > pretty handy! > > > > I attempted to open a bug report on the Libertine tracker but > > Sourceforge refuses to cooperate :/ Maybe next time. > > As far as I know there is no more a development of Libertine The font is open source to some extent, isn’t it? Any feedback will be valuable should someone decide to take up maintainance / development. Philipp pgp8701M5t2jE.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] [fontloader] positioning of diacritics
Am 15.12.2014 um 21:43 schrieb Philipp Gesang: \enabletrackers[otf.bugs] Thanks for the reply and for the pointer. That tracker is indeed pretty handy! I attempted to open a bug report on the Libertine tracker but Sourceforge refuses to cooperate :/ Maybe next time. As far as I know there is no more a development of Libertine Herbert ___ 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 ___
Re: [NTG-context] [fontloader] positioning of diacritics
· > On 12/15/2014 8:08 AM, Philipp Gesang wrote: > > Good morning! > > > > This report by Github user SverreStausland has been lingering on > > the Luaotfload tracker for a while: There appears to be a > > difference between how certain faces of the Libertine family > > handle the placement of diacritics. > > > > With Version 5.1.2 of the family [0], the "RZI" version > > (fullname: “Linux Libertine O Semibold Italic”) shows a different > > behavior than its “RZ” companion (“Linux Libertine O Semibold”). > > Short demonstration in Context: > > > > \definefontfeature [ourfeats] [default] [mode=node] > > > > \starttext > >\start \definedfont [file:LinLibertine_RI.otf*ourfeats] V\char"0306 > > \stop > >\start \definedfont [file:LinLibertine_RZI.otf*ourfeats] V\char"0306 > > \stop > > \stoptext > > > > Note the misaligned combining breve above the latter. An > > equivalent test for Plain [1] shows that the correct position > > information is there somewhere in the font, since the Xetex > > engine typesets it correctly. > > it's a bug in the font: > > uni0306 in the second one has class "base" while in the first one it has > class "mark" and context checks on that > > \enabletrackers[otf.bugs] Thanks for the reply and for the pointer. That tracker is indeed pretty handy! I attempted to open a bug report on the Libertine tracker but Sourceforge refuses to cooperate :/ Maybe next time. Best regards, Philipp pgpualdFxOdsb.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] [fontloader] positioning of diacritics
On 12/15/2014 8:08 AM, Philipp Gesang wrote: Good morning! This report by Github user SverreStausland has been lingering on the Luaotfload tracker for a while: There appears to be a difference between how certain faces of the Libertine family handle the placement of diacritics. With Version 5.1.2 of the family [0], the "RZI" version (fullname: “Linux Libertine O Semibold Italic”) shows a different behavior than its “RZ” companion (“Linux Libertine O Semibold”). Short demonstration in Context: \definefontfeature [ourfeats] [default] [mode=node] \starttext \start \definedfont [file:LinLibertine_RI.otf*ourfeats] V\char"0306 \stop \start \definedfont [file:LinLibertine_RZI.otf*ourfeats] V\char"0306 \stop \stoptext Note the misaligned combining breve above the latter. An equivalent test for Plain [1] shows that the correct position information is there somewhere in the font, since the Xetex engine typesets it correctly. it's a bug in the font: uni0306 in the second one has class "base" while in the first one it has class "mark" and context checks on that \enabletrackers[otf.bugs] Best regards, Philipp [0] MD5 hashes of the files: 4bfd3481c1486f5d1ea13304981df7a6 LinLibertine_RZI.otf 153765bd2b29d6026fb2fa0b198a4995 LinLibertine_RZ.otf [1] https://bitbucket.org/phg/lua-la-tex-tests/src/tip/pln-diacritics-1.tex ___ 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 ___ -- - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
[NTG-context] [fontloader] positioning of diacritics
Good morning! This report by Github user SverreStausland has been lingering on the Luaotfload tracker for a while: There appears to be a difference between how certain faces of the Libertine family handle the placement of diacritics. With Version 5.1.2 of the family [0], the "RZI" version (fullname: “Linux Libertine O Semibold Italic”) shows a different behavior than its “RZ” companion (“Linux Libertine O Semibold”). Short demonstration in Context: \definefontfeature [ourfeats] [default] [mode=node] \starttext \start \definedfont [file:LinLibertine_RI.otf*ourfeats] V\char"0306 \stop \start \definedfont [file:LinLibertine_RZI.otf*ourfeats] V\char"0306 \stop \stoptext Note the misaligned combining breve above the latter. An equivalent test for Plain [1] shows that the correct position information is there somewhere in the font, since the Xetex engine typesets it correctly. Best regards, Philipp [0] MD5 hashes of the files: 4bfd3481c1486f5d1ea13304981df7a6 LinLibertine_RZI.otf 153765bd2b29d6026fb2fa0b198a4995 LinLibertine_RZ.otf [1] https://bitbucket.org/phg/lua-la-tex-tests/src/tip/pln-diacritics-1.tex pgpn9cMzY_R_j.pgp Description: PGP signature ___ 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 ___
[NTG-context] [fontloader] crash in font-otf.lua / actions["reorganize glyph anchors"]
Hi Hans,
this bug was reported a while ago by user Thérèse on
tex.stackexchange.com [1]. The font “Eadui.ttf” [2] causes the
fontloader to access a nil value because the “Anchor-1” table is
sparse (nil at index 3). Test file for Context:
https://bitbucket.org/phg/lua-la-tex-tests/src/tip/cnt-eadui.tex
Patch attached, though I suspect it covers only the symptoms.
Philipp
[1] http://tex.stackexchange.com/q/195481/14066
[2] Download at http://openfontlibrary.org/font/eadui
diff --git a/tex/context/base/font-otf.lua b/tex/context/base/font-otf.lua
index 302d8ea..de392a9 100644
--- a/tex/context/base/font-otf.lua
+++ b/tex/context/base/font-otf.lua
@@ -2010,7 +2010,11 @@ actions["reorganize glyph anchors"] = function(data,filename,raw) -- when we rep
for tag, specification in next, data do
for i=1,#specification do
local si = specification[i]
-specification[i] = { si.x or 0, si.y or 0 }
+if si then
+ specification[i] = { si.x or 0, si.y or 0 }
+else
+ specification[i] = { }
+end
end
end
else
pgp7OErflgPnc.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] [fontloader] node injector / december 3 sync
On 12/14/2014 2:45 PM, Philipp Gesang wrote:
Hi Hans,
from the huge changeset two weeks ago:
+texio.write_nl("The font code has been brought in sync with the context
version of 2014.12.01 so")
+texio.write_nl("if things don't work out as expected the interfacing needs to
be checked. When")
-- Message received ;) First off, thanks for bringing the
fontloader into sync again. So far I haven’t noticed any
obviously broken features.
However, something is off with the node injector. We have a bug
reported by Hironori Kitagawa that occurs with the ``palt``
feature in node mode:
http://tug.org/pipermail/luatex/2014-November/004976.html
Importing the shiny new font injector into the merged fontloader
fixes the issue. FWIW here are test files
https://bitbucket.org/phg/lua-la-tex-tests/src/tip/cnt-features-12-palt.tex
https://bitbucket.org/phg/lua-la-tex-tests/src/tip/pln-features-12-palt.tex
The Context version runs fine whereas the plain one does so only
after my “fix”. The same is true for Context itself: replace
font-inj.lua with node-inj.lua in the format to reproduce the
issue. Is there a fix to the fontloader, perhaps only temporarily
until the revised injector becomes ready?
not really as the new injector does more ... also, the new code is kind
of beta so it might not be a good idea to use that in latex already ...
i'm still working on some issues with disc nodes and fonts that have
ligatures that are not ligatures
so, i'd first like to do more tests here; of course you can use the new
injector if you want ... (i'm not touching generic now while messing
with the context variant)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
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
___
[NTG-context] [fontloader] node injector / december 3 sync
Hi Hans,
from the huge changeset two weeks ago:
+texio.write_nl("The font code has been brought in sync with the context
version of 2014.12.01 so")
+texio.write_nl("if things don't work out as expected the interfacing
needs to be checked. When")
-- Message received ;) First off, thanks for bringing the
fontloader into sync again. So far I haven’t noticed any
obviously broken features.
However, something is off with the node injector. We have a bug
reported by Hironori Kitagawa that occurs with the ``palt``
feature in node mode:
http://tug.org/pipermail/luatex/2014-November/004976.html
Importing the shiny new font injector into the merged fontloader
fixes the issue. FWIW here are test files
https://bitbucket.org/phg/lua-la-tex-tests/src/tip/cnt-features-12-palt.tex
https://bitbucket.org/phg/lua-la-tex-tests/src/tip/pln-features-12-palt.tex
The Context version runs fine whereas the plain one does so only
after my “fix”. The same is true for Context itself: replace
font-inj.lua with node-inj.lua in the format to reproduce the
issue. Is there a fix to the fontloader, perhaps only temporarily
until the revised injector becomes ready?
Best,
Philipp
pgpsX1oE9sEkr.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] [fontloader] does base mode support combining substitutions?
On 4/5/2014 9:58 PM, Philipp Gesang wrote: · On 4/5/2014 4:37 PM, Philipp Gesang wrote: Hi Hans, when combining e.g. certain number substitutions like onum and pnum or tnum and lnum, node mode seems to work fine. However, those do have value in math mode as well which node mode does not currently support. For comparison, here is a test file: https://bitbucket.org/phg/lua-la-tex-tests/raw/93745dba31e23febb02191c039dea2de743ce77a/cnt-features-8-combined-num.tex Is there a way to define a font with the combination of, say tnum and lnum that will work in math mode? If not, are there plans to implement it in the future? basemode will always be limited because there we create static glyph sets; so. for complex substitutions node mode is the method to use what do you mean with math mode in this case; in math a digit is different from a digit in text mode; i think that if one uses *num digits we're talking text mode I’m just relaying a question of a user who wishes to use those combined lnum+tnum digits in math mode. of course in context we can support whatever we want because we're not bound to rules, but the question is: does it make sense; Ultimately I can’t judge that, the problem description does seem valid though: http://tex.stackexchange.com/q/165238/14066 In math mode characters are organized in categories, e.g. letters are grouped in alphabets. Now imagine that we start applying font features, does that mean that a 'a' should become a small caps 'A'? And when are features applied? Math is a tree and not per se sequential, so how about ligatures? Ok, digits might be something special but even then, just swapping one '1' for another one that is not math aware and then is combined with other math characters (lik ein scripts) can have weird side effects. This is not something generic. So, the only way to deal with that properly is to define a font where certain rendering is replaced by another but in the same slot. Even then one really needs to know if the font is suitable for it. I guess that such oldstyle thingies are mostly for simple math that stays close to text, but even then. In context I'd certainly not deal with that by features directly also because the *num properties are not always implemented the same (we have a mechanism for combining fonts anyway). If someone realy wants features applied to math (maybe after the math is processed, then i can imagine that the node font handler is hooked into the mlist_to_hlist callback so that they are applied afterwards. In any case it's very macro package dependent. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] [fontloader] does base mode support combining substitutions?
· > On 4/5/2014 4:37 PM, Philipp Gesang wrote: > > Hi Hans, > > > > when combining e.g. certain number substitutions like onum and > > pnum or tnum and lnum, node mode seems to work fine. However, > > those do have value in math mode as well which node mode does not > > currently support. For comparison, here is a test file: > > > > > > https://bitbucket.org/phg/lua-la-tex-tests/raw/93745dba31e23febb02191c039dea2de743ce77a/cnt-features-8-combined-num.tex > > > > Is there a way to define a font with the combination of, say tnum > > and lnum that will work in math mode? If not, are there plans to > > implement it in the future? > > basemode will always be limited because there we create static glyph > sets; so. for complex substitutions node mode is the method to use > > what do you mean with math mode in this case; in math a digit is > different from a digit in text mode; i think that if one uses *num > digits we're talking text mode I’m just relaying a question of a user who wishes to use those combined lnum+tnum digits in math mode. > of course in context we can support whatever we want because we're not > bound to rules, but the question is: does it make sense; Ultimately I can’t judge that, the problem description does seem valid though: http://tex.stackexchange.com/q/165238/14066 Philipp pgp3Iv5PkWB60.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] [fontloader] does base mode support combining substitutions?
On 4/5/2014 4:37 PM, Philipp Gesang wrote: Hi Hans, when combining e.g. certain number substitutions like onum and pnum or tnum and lnum, node mode seems to work fine. However, those do have value in math mode as well which node mode does not currently support. For comparison, here is a test file: https://bitbucket.org/phg/lua-la-tex-tests/raw/93745dba31e23febb02191c039dea2de743ce77a/cnt-features-8-combined-num.tex Is there a way to define a font with the combination of, say tnum and lnum that will work in math mode? If not, are there plans to implement it in the future? basemode will always be limited because there we create static glyph sets; so. for complex substitutions node mode is the method to use what do you mean with math mode in this case; in math a digit is different from a digit in text mode; i think that if one uses *num digits we're talking text mode of course in context we can support whatever we want because we're not bound to rules, but the question is: does it make sense; Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
[NTG-context] [fontloader] does base mode support combining substitutions?
Hi Hans, when combining e.g. certain number substitutions like onum and pnum or tnum and lnum, node mode seems to work fine. However, those do have value in math mode as well which node mode does not currently support. For comparison, here is a test file: https://bitbucket.org/phg/lua-la-tex-tests/raw/93745dba31e23febb02191c039dea2de743ce77a/cnt-features-8-combined-num.tex Is there a way to define a font with the combination of, say tnum and lnum that will work in math mode? If not, are there plans to implement it in the future? Best regards, Philipp pgp1MFd4ggd88.pgp Description: PGP signature ___ 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 ___
Re: [NTG-context] [fontloader] cached fonts have invalid tounicode values
On 6/28/2013 1:12 PM, Philipp Gesang wrote: · Hi Philipp, I’ve traced it to luatex-basics-gen.lua. luaotfload-basics-gen.lua and luaotfload-merged.lua? The latter is generated from the former, so yes. For a hot fix it suffices to patch the merged file. Anyways, luaotfload will be updated once Hans pushes a fix upstream. but be careful with that ... there will be some experimental code in coming betas that won't effect context but will probably make there way into generic some time later, when found ok Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] [fontloader] cached fonts have invalid tounicode values
· > Hi Philipp, > > >I’ve traced it to luatex-basics-gen.lua. > > luaotfload-basics-gen.lua and luaotfload-merged.lua? The latter is generated from the former, so yes. For a hot fix it suffices to patch the merged file. Anyways, luaotfload will be updated once Hans pushes a fix upstream. Best, Philipp pgpyiIopJGxNl.pgp Description: PGP signature ___ 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 ___
[NTG-context] [fontloader] cached fonts have invalid tounicode values
Hi Philipp, I’ve traced it to luatex-basics-gen.lua. luaotfload-basics-gen.lua and luaotfload-merged.lua? Thank you very much. Akira ___ 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 ___
Re: [NTG-context] [fontloader] cached fonts have invalid tounicode values
·
> Hi Hans,
>
> this has been reported by Dohyun Kim [1]: the generic fontloader
> (not Context) serializes some tounicode values as Lua numbers,
> not strings. When re-reading the cache file the values lose all
> leading zeros, so they are no longer well-formed UTF-16BE.
>
> ...
> ["tounicode"]={
>[2329]="E001",
> ...
>[2384]="0063006B", -- <-- correct
>[2385]=00630068, -- <-- invalid
>[2386]=00740074,
>[2387]=00630074,
>[2388]="017F0069",
> ...
>
> Best regards,
> Philipp
>
> [1] https://github.com/lualatex/luaotfload/issues/102
> (Kim’s example works with luatex-plain if you comment out the
> ``\input luaotfload.sty`` line.)
I’ve traced it to luatex-basics-gen.lua. The cache is compiled
with the spec “{reduce = true}” which causes values to be
analyzed and “tonumber()”ed. If I unset the reduce flag, the
values turn out correct in the PDF.
Best,
Philipp
pgp495oNB_xPk.pgp
Description: PGP signature
___
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
___
[NTG-context] [fontloader] cached fonts have invalid tounicode values
Hi Hans,
this has been reported by Dohyun Kim [1]: the generic fontloader
(not Context) serializes some tounicode values as Lua numbers,
not strings. When re-reading the cache file the values lose all
leading zeros, so they are no longer well-formed UTF-16BE.
...
["tounicode"]={
[2329]="E001",
...
[2384]="0063006B", -- <-- correct
[2385]=00630068, -- <-- invalid
[2386]=00740074,
[2387]=00630074,
[2388]="017F0069",
...
Best regards,
Philipp
[1] https://github.com/lualatex/luaotfload/issues/102
(Kim’s example works with luatex-plain if you comment out the
``\input luaotfload.sty`` line.)
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
pgp7GnelUVpi2.pgp
Description: PGP signature
___
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
___
Re: [NTG-context] fontloader: “can't convert into tounicode”
On 5/3/2013 9:04 PM, Philipp Gesang wrote:
Hi,
loading this font:
https://collab.itc.virginia.edu/access/content/group/26a34146-33a6-48ce-001e-f16ce7908a6a/Tibetan%20fonts/Tibetan%20Unicode%20Fonts/TibetanMachineUnicodeFont.zip
causes the fontloader to emit a dozen or so messages of the kind
fonts > loading > can't convert 7.27550912993e+22 into tounicode
fonts > loading > can't convert 3.1248073774797e+32 into
tounicode
fonts > loading > can't convert 4.731809353839e+27 into tounicode
...
example code:
\starttext
foo
{\definedfont[file:TibMachUni-1.901b.ttf*tibetan at 33pt]༡༢་༣༤་༥༦་༧༨}
bar
\stoptext
is this harmless? The typeset result appears to be satisfying.
in general yes; only can affect rare cases of cut-and-paste from the pdf
(fixed anyway but no upload this weekend)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
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
___
[NTG-context] fontloader: “can't convert into tounicode”
Hi,
loading this font:
https://collab.itc.virginia.edu/access/content/group/26a34146-33a6-48ce-001e-f16ce7908a6a/Tibetan%20fonts/Tibetan%20Unicode%20Fonts/TibetanMachineUnicodeFont.zip
causes the fontloader to emit a dozen or so messages of the kind
fonts > loading > can't convert 7.27550912993e+22 into tounicode
fonts > loading > can't convert 3.1248073774797e+32 into tounicode
fonts > loading > can't convert 4.731809353839e+27 into tounicode
...
example code:
\starttext
foo
{\definedfont[file:TibMachUni-1.901b.ttf*tibetan at 33pt]༡༢་༣༤་༥༦་༧༨}
bar
\stoptext
is this harmless? The typeset result appears to be satisfying.
Best regards,
Philipp
pgpjiZEPk6Q2_.pgp
Description: PGP signature
___
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
___
