ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan U. Hasecke" <juh+ntg-context@mailbox.org>
To: ntg-context@ntg.nl
Subject: Ligatures in EB Garamond (was: \replaceword and \setreplacements with xml files)
Date: Mon, 18 Jan 2016 10:16:31 +0100	[thread overview]
Message-ID: <569CAD6F.5000702@mailbox.org> (raw)
In-Reply-To: <569BE60D.7000900@wxs.nl>

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

juh
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2016-01-18  9:16 UTC|newest]

Thread overview: 10+ 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       ` Jan U. Hasecke [this message]
2016-01-18 10:09         ` Ligatures in EB Garamond Hans Hagen
2016-01-18 12:46           ` Jan U. Hasecke
2016-01-18 19:22             ` 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=569CAD6F.5000702@mailbox.org \
    --to=juh+ntg-context@mailbox.org \
    --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).