Re: [NTG-context] crappy names in the fontloader
On 7/7/2019 11:42 PM, Hans Hagen wrote:
On 7/6/2019 6:36 PM, Marcel Fabian Krüger wrote:
Hi everyone,
under default settings, the fontloaders discards all glyph names which
are considered "crappy", meaning matching the "p_crappyname" pattern in
"font-oup.lua". For some names this makes a lot of sense. For example
the name "uni0303" is considered "crappy" and it really provides no
useful information. Then there are other names like "t_uni0303" which
are still considered "crappy" while they actually aren't completely
useless. So I think there would be some value in preserving them. Of
course, you can always enable "otf.keepnames" if you need names like
this.
But I actually want to talk about another class of names: Look at
"Udotbelow". This is IMHO a perfectly normal and useful name, but the
fontloader still considers it "crappy" because it starts with a "U"
followed by a letter which could be a hexadecimal number.
I think this is a bit over-agressive. Maybe the "p_crappyname" pattern
could be changed to only look for "u" if followed by
"p_done", marking the end of a component?
p_done should be:
local p_done = S("._-") + P(-1)
(hex is already checked)
i'll look into it (irr in generic mode (latex etc) one can disable that
'feature' which i thought happened)
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
___
--
-
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] crappy names in the fontloader
On 7/6/2019 6:36 PM, Marcel Fabian Krüger wrote: Hi everyone, under default settings, the fontloaders discards all glyph names which are considered "crappy", meaning matching the "p_crappyname" pattern in "font-oup.lua". For some names this makes a lot of sense. For example the name "uni0303" is considered "crappy" and it really provides no useful information. Then there are other names like "t_uni0303" which are still considered "crappy" while they actually aren't completely useless. So I think there would be some value in preserving them. Of course, you can always enable "otf.keepnames" if you need names like this. But I actually want to talk about another class of names: Look at "Udotbelow". This is IMHO a perfectly normal and useful name, but the fontloader still considers it "crappy" because it starts with a "U" followed by a letter which could be a hexadecimal number. I think this is a bit over-agressive. Maybe the "p_crappyname" pattern could be changed to only look for "u" if followed by "p_done", marking the end of a component? i'll look into it (irr in generic mode (latex etc) one can disable that 'feature' which i thought happened) 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] crappy names in the fontloader
Hi everyone, under default settings, the fontloaders discards all glyph names which are considered "crappy", meaning matching the "p_crappyname" pattern in "font-oup.lua". For some names this makes a lot of sense. For example the name "uni0303" is considered "crappy" and it really provides no useful information. Then there are other names like "t_uni0303" which are still considered "crappy" while they actually aren't completely useless. So I think there would be some value in preserving them. Of course, you can always enable "otf.keepnames" if you need names like this. But I actually want to talk about another class of names: Look at "Udotbelow". This is IMHO a perfectly normal and useful name, but the fontloader still considers it "crappy" because it starts with a "U" followed by a letter which could be a hexadecimal number. I think this is a bit over-agressive. Maybe the "p_crappyname" pattern could be changed to only look for "u" if followed by "p_done", marking the end of a component? Best regards, Marcel Krüger ___ 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 ___
