ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: disabling ligatures in selected words
Date: Fri, 23 Oct 2015 21:09:24 +0200	[thread overview]
Message-ID: <562A85E4.7080306@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.20.1510231453460.22171@ybpnyubfg.ybpnyqbznva>


[-- Attachment #1.1: Type: text/plain, Size: 1712 bytes --]

> Aditya Mahajan <mailto:adityam@umich.edu>
> 23. Oktober 2015 um 20:57
> On Fri, 23 Oct 2015, Thomas A. Schmitz wrote:
>
>
> This has been asked on tex stackexchange. One option is to use the 
> translate module:
>
> http://tex.stackexchange.com/a/37465/323
> http://tex.stackexchange.com/a/28746/323
>
> Aditya
> ___________________________________________________________________________________ 
>
> 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
> ___________________________________________________________________________________
> Thomas A. Schmitz <mailto:thomas.schmitz@uni-bonn.de>
> 23. Oktober 2015 um 20:51
> Hi,
>
> in German typography, ligatures are disabled at boundaries between 
> what used to be independent words (Wortfugen). Thusly, in a correct 
> German text, you'd find
>
> Anflug (with fl-ligature) but
>
> Auf|lage (without ligature).
>
> I know that I can prevent a ligature with something like Auf\/lage or 
> even Auf|*|lage. However, I typeset from xml and would much rather 
> have a general solution so I can leave my generated xml files alone. 
> Something like a list where I could list "ligature exceptions" the way 
> we have a file with hyphenation exceptions. Is anything like this 
> possible?
Take a look at the new replacement mechanism (lang-rep.mkiv):

- http://www.ntg.nl/pipermail/ntg-context/2015/083044.html
- http://www.ntg.nl/pipermail/ntg-context/2015/083034.html

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 4346 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
___________________________________________________________________________________

  reply	other threads:[~2015-10-23 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 18:51 Thomas A. Schmitz
2015-10-23 18:57 ` Aditya Mahajan
2015-10-23 19:09   ` Wolfgang Schuster [this message]
2015-10-23 19:23     ` Thomas A. Schmitz
2016-01-12 14:37       ` Jan U. Hasecke

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=562A85E4.7080306@gmail.com \
    --to=schuster.wolfgang@gmail.com \
    --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).