From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: [fontloader] positioning of diacritics
Date: Mon, 15 Dec 2014 13:34:48 +0100 [thread overview]
Message-ID: <548ED568.8060400@wxs.nl> (raw)
In-Reply-To: <20141215070816.GA25478@acheron>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-12-15 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 7:08 Philipp Gesang
2014-12-15 12:34 ` Hans Hagen [this message]
2014-12-15 20:43 ` Philipp Gesang
2014-12-15 20:59 ` Herbert Voss
2014-12-15 21:16 ` Philipp Gesang
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=548ED568.8060400@wxs.nl \
--to=pragma@wxs.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).