From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: issue with optical bounds (OpenType)
Date: Sun, 9 Dec 2018 20:54:31 +0100 [thread overview]
Message-ID: <c6cfddd9-b5bf-611a-7b69-3ea1f6189f62@gmx.es> (raw)
In-Reply-To: <dbef716c-0e22-0667-c14e-0a90e7c09ebe@xs4all.nl>
On 12/9/18 6:53 PM, Hans Hagen wrote:
> On 12/9/2018 5:35 PM, Pablo Rodriguez wrote:
>> [...]
>> -Is there any way that I can apply pure raw lfbd/rtbd values to
>> protrusion with no other protrusion calculation at all in opbd?
>
> you can create your own vectors if you want
My own vectors wouldn’t solve the issue, because the variable would be:
lfbd(Ὧ) = glyph.width(Ω) - glyph.width(Ὧ)
I need to place glyphs accurately, not characters. Character dimensions
wouldn’t help to get hanging diacritics.
>> -In order to avoid editing all the Greek fonts to get hanging
>> diacritics: is there any way to replicate the lfbd feature with
>> "fonts.handlers.otf.addfeature"?
>
> probably with some lua magic one can do a lot but these are typical
> things i do when i need them (also because one needs to check the whole
> of unicode and cook up categories, this kind of stuff is: do it all
> robust and well or don't do it; also one doesn't know how consistent
> font designs are)
The variable is so simple that the glyph with diacritical marks should
be placed in the beginning of the line as it had no such marks.
If the font has all glyphs for uppercase letters with the same width for
the letter strokes, a general approach (such as the menttioned above, I
guess it) would work.
Many thanks for your help,
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-12-09 19:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 18:54 Pablo Rodriguez
2018-12-07 19:15 ` Hans Hagen
2018-12-07 20:14 ` Pablo Rodriguez
2018-12-07 22:25 ` Hans Hagen
2018-12-09 12:34 ` Pablo Rodriguez
2018-12-09 13:22 ` Hans Hagen
2018-12-09 16:35 ` Pablo Rodriguez
2018-12-09 17:53 ` Hans Hagen
2018-12-09 19:54 ` Pablo Rodriguez [this message]
2018-12-10 9:51 ` Hans Hagen
2018-12-10 19:19 ` Pablo Rodriguez
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=c6cfddd9-b5bf-611a-7b69-3ea1f6189f62@gmx.es \
--to=oinos@gmx.es \
--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).