From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Ligatures in EB Garamond
Date: Mon, 18 Jan 2016 11:09:00 +0100 [thread overview]
Message-ID: <569CB9BC.6000805@wxs.nl> (raw)
In-Reply-To: <569CAD6F.5000702@mailbox.org>
On 1/18/2016 10:16 AM, Jan U. Hasecke wrote:
> Am 17.01.2016 um 20:05 schrieb Hans Hagen:
>> On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:
>>> Am 16.01.2016 um 13:31 schrieb Schmitz Thomas A.:
>>>>
>>>> Please provide a minimal example of your problem. It’s impossible to
>>>> help when we have no clue what you’re doing.
>>>
>>> Sorry, of course.
>>>
>>> After setting up a mwe I found that it is a font related issue.
>>>
>>> When I don't specify a font, it works. --> example.tex
>>>
>>> When I choose EB Garamond, it does not work. -- example-Garamond.tex
>>>
>>> I confirmed this behaviour in my real setup.
>>
>> don't assume that ligatures are always real ligatures ... in that font
>> it's just kerning .. this kind of works okay:
>>
>> \replaceword[sellig][auflösen][auf{-}{}{\zwnj}lösen]
>
> I am confused as the specimen of EB Garamond mentions (real) ligatures.
> They are listed as glyphs.
>
> https://github.com/georgd/EB-Garamond/blob/master/specimen/Specimen.pdf
maybe the archaic st ligature is a precomposed but f f l i aren't done
that way but by either kerning or replacement of individual glyphs +
kerning (there are many methods for this) ... also, 'liga' might mean
ligature but in practice is used for all kind of things ... in opentype
'ligature substitution' is just a many-to-one replacement but that
doesn't mean that 'liga' uses that ... welcome to the inconsistent open
type mess
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | 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:[~2016-01-18 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 11:24 \replaceword and \setreplacements with xml files Jan U. Hasecke
2016-01-16 12:31 ` Schmitz Thomas A.
2016-01-16 14:58 ` Jan U. Hasecke
2016-01-17 19:05 ` Hans Hagen
2016-01-18 6:31 ` Jan U. Hasecke
2016-01-18 10:12 ` Hans Hagen
2016-01-18 9:16 ` Ligatures in EB Garamond (was: \replaceword and \setreplacements with xml files) Jan U. Hasecke
2016-01-18 10:09 ` Hans Hagen [this message]
2016-01-18 12:46 ` Ligatures in EB Garamond Jan U. Hasecke
2016-01-18 19:22 ` Hans Hagen
[not found] <mailman.9.1453133650.2231.ntg-context@ntg.nl>
2016-01-18 22:38 ` Georg Duffner
2016-01-19 7:13 ` Jan U. Hasecke
2016-01-19 8:57 ` Hans Hagen
2016-01-19 9:05 ` Arthur Reutenauer
2016-01-19 15:31 ` Kate F
2016-01-19 15:43 ` Arthur Reutenauer
2016-01-19 16:41 ` Jan U. Hasecke
2016-01-19 18:23 ` Hans Hagen
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=569CB9BC.6000805@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).