From: Philipp Gesang <philipp.gesang@alumni.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [fontloader] positioning of diacritics
Date: Mon, 15 Dec 2014 21:43:51 +0100 [thread overview]
Message-ID: <20141215204351.GA26654@acheron> (raw)
In-Reply-To: <548ED568.8060400@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1573 bytes --]
···<date: 2014-12-15, Monday>···<from: Hans Hagen>···
> 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
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 20:43 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
2014-12-15 20:43 ` Philipp Gesang [this message]
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=20141215204351.GA26654@acheron \
--to=philipp.gesang@alumni.uni-heidelberg.de \
--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).