From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: Re: crappy names in the fontloader
Date: Mon, 8 Jul 2019 13:54:52 +0200 [thread overview]
Message-ID: <ef4f054c-d3b1-4643-38d5-d3572d4161d2@xs4all.nl> (raw)
In-Reply-To: <ea884d13-5c0e-9772-8f69-c2f13ddb224e@xs4all.nl>
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<hexadecimal>" 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
___________________________________________________________________________________
prev parent reply other threads:[~2019-07-08 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 16:36 Marcel Fabian Krüger
2019-07-07 21:42 ` Hans Hagen
2019-07-08 11:54 ` Hans Hagen [this message]
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=ef4f054c-d3b1-4643-38d5-d3572d4161d2@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).