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: Re: Ligatures in EB Garamond
Date: Tue, 19 Jan 2016 17:41:13 +0100	[thread overview]
Message-ID: <569E6729.2050302@mailbox.org> (raw)
In-Reply-To: <CAA36g0WF2qoozCthdUCyVagudcE2BgCGaKFJmCa_-06x2HL+Ag@mail.gmail.com>

Am 19.01.2016 um 16:31 schrieb Kate F:
> On 19 January 2016 at 09:05, Arthur Reutenauer
> <arthur.reutenauer@normalesup.org> wrote:
>>> I have no clue what a package is supposed to do but any solution has to come
>>> up with a list if words.
>>
>>   I think the point is that often in German, breakpoints for hyphenation
>> also break ligatures.  I mentioned that in Nasbinals.
>>
>>         Best,
>>
>>                 Arthur
> 
> The guts of the selnolig package just call \hyphenation{...}:
> http://anorien.csc.warwick.ac.uk/mirrors/CTAN/macros/luatex/latex/selnolig/selnolig-english-hyphex.sty

The interesting part for ligatures is in the patterns file

http://anorien.csc.warwick.ac.uk/mirrors/CTAN/macros/luatex/latex/selnolig/selnolig-english-patterns.sty

http://anorien.csc.warwick.ac.uk/mirrors/CTAN/macros/luatex/latex/selnolig/selnolig-german-patterns.sty

By using patterns they don't need a very huge word list, I think.

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-19 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2016-01-19 18:23             ` Hans Hagen
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  9:16       ` Ligatures in EB Garamond (was: \replaceword and \setreplacements with xml files) Jan U. Hasecke
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=569E6729.2050302@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).