Re: [NTG-context] ligature exceptions

On 7/28/2021 7:24 PM, Thomas A. Schmitz via ntg-context wrote: Hi all, just two quick questions: a couple of weeks ago, there was a long discussion on ligature exceptions in, e.g., German. Hans provided an elegant new mechanism (\startlanguageoptions). So my two questions: 1. Is the old

[NTG-context] ligature exceptions

Hi all, just two quick questions: a couple of weeks ago, there was a long discussion on ligature exceptions in, e.g., German. Hans provided an elegant new mechanism (\startlanguageoptions). So my two questions: 1. Is the old mechanism (\replaceword[eg][Auflage][Au{fl}age]) now obsolete? I

Re: [NTG-context] ligature exceptions

On 10/08/2017 02:54 PM, Henning Hraban Ramm wrote: > Am 2017-10-08 um 10:37 schrieb Pablo Rodriguez: >> On 10/08/2017 12:22 AM, Hans Hagen wrote: >> Many thanks for your reply, Hans. >> >> I almost get it all ;-), but what is the "i" variable? > > It defines the kerning between f and i. I also

Re: [NTG-context] ligature exceptions

Am 2017-10-08 um 10:37 schrieb Pablo Rodriguez : > On 10/08/2017 12:22 AM, Hans Hagen wrote: >> You need to define features before fonts get defined because we share >> font definitions and their features as much as possible >> >> \startluacode >> fonts.handlers.otf.addfeature

Re: [NTG-context] ligature exceptions

Am 2017-10-08 um 00:22 schrieb Hans Hagen : > On 10/7/2017 9:21 PM, Pablo Rodriguez wrote: > You need to define features before fonts get defined because we share font > definitions and their features as much as possible > > \startluacode >fonts.handlers.otf.addfeature { >

Re: [NTG-context] ligature exceptions

Am 2017-10-08 um 00:14 schrieb Hans Hagen : > On 10/7/2017 9:21 PM, Pablo Rodriguez wrote: >> On 10/07/2017 01:25 PM, Henning Hraban Ramm wrote: >>> I rejoiced too early: >>> While the ligature exception handling works with some of the default >>> fonts (lm, termes, pagella), it

Re: [NTG-context] ligature exceptions

On 10/08/2017 12:22 AM, Hans Hagen wrote: > You need to define features before fonts get defined because we share > font definitions and their features as much as possible > > \startluacode > fonts.handlers.otf.addfeature { > name = "kernligatures", > type = "kern", >

Re: [NTG-context] ligature exceptions

On 10/08/2017 12:14 AM, Hans Hagen wrote: > On 10/7/2017 9:21 PM, Pablo Rodriguez wrote: > [...] > forget about Algreya as it's a useless font ... it has no kerns, no > ligatures, no features at all so the f an whatever follows will always > touch or overlap due to the design In fact, the full

Re: [NTG-context] ligature exceptions

On 10/7/2017 9:21 PM, Pablo Rodriguez wrote: The Brill fonts don’t work either (http://www.brill.com/about/brill-fonts). \definefontfamily[mainfont][rm][Alegreya] \definefontfamily[otherfont][rm][Brill] \setupbodyfont [mainfont,16pt] \starttext

Re: [NTG-context] ligature exceptions

On 10/7/2017 9:21 PM, Pablo Rodriguez wrote: On 10/07/2017 01:25 PM, Henning Hraban Ramm wrote: I rejoiced too early: While the ligature exception handling works with some of the default fonts (lm, termes, pagella), it fails with the Alegreya fonts that I’m using. forget about Algreya as it's

Re: [NTG-context] ligature exceptions

Am 2017-10-07 um 21:21 schrieb Pablo Rodriguez : > Both Alegreya and Brill don’t replace the ligature with a single glyph, > but replace the first glyph (only, as far as I know). > > I don’t know which is the way to solve it, but this might be the cause. Oh, yes. Thanks for the

Re: [NTG-context] ligature exceptions

On 10/07/2017 01:25 PM, Henning Hraban Ramm wrote: > I rejoiced too early: > While the ligature exception handling works with some of the default > fonts (lm, termes, pagella), it fails with the Alegreya fonts that I’m > using. The Brill fonts don’t work either

Re: [NTG-context] ligature exceptions

I rejoiced too early: While the ligature exception handling works with some of the default fonts (lm, termes, pagella), it fails with the Alegreya fonts that I’m using. I’d be glad if someone (you?) could look into my attached typescript file or even try downloading the fonts* to check what’s

Re: [NTG-context] ligature exceptions

On 09/28/2017 03:54 PM, Hans Hagen wrote: > On 9/28/2017 1:51 PM, Pablo Rodriguez wrote: >> [...] >> I overlooked that \blockligatures[u:fl:age, u:fl:eg] only works if there >> is also a \blockligatures[fl]. >> >> Hans, is this a bug or is it intended? > do you indeed use the latest beta? anyway,

Re: [NTG-context] ligature exceptions

On 9/28/2017 1:51 PM, Pablo Rodriguez wrote: On 09/28/2017 09:17 AM, Herbert Voss wrote: Am 28.09.2017 um 08:40 schrieb Pablo Rodriguez: using latest beta (from 2017.09.25 19:19), the following sample works: [...] How do you catch "Aufl." (the abbreviation of Auflage), which is written

Re: [NTG-context] ligature exceptions

On 09/28/2017 09:17 AM, Herbert Voss wrote: > Am 28.09.2017 um 08:40 schrieb Pablo Rodriguez: > >> using latest beta (from 2017.09.25 19:19), the following sample works: > [...] > How do you catch "Aufl." (the abbreviation of Auflage), > which is written _with_ a ligature? Herbert, I

Re: [NTG-context] ligature exceptions

Am 2017-09-27 um 23:02 schrieb Herbert Voss : >> Thank you for the suggestion. >> I tried >> \replaceword[eka][Auflage][Au{fl}age] >> \setreplacements[eka] >> and even converted the german wordlist from the selnolig package, but it >> doesn’t help. >> If I try >>

Re: [NTG-context] ligature exceptions

Am 28.09.2017 um 08:40 schrieb Pablo Rodriguez: using latest beta (from 2017.09.25 19:19), the following sample works: \starttext \blockligatures[fi,ff] \blockligatures[fl] \blockligatures[u:fl:age, u:fl:eg] \definefontfeature[default:b][default][blockligatures=yes]

Re: [NTG-context] ligature exceptions

On 09/27/2017 10:27 PM, Henning Hraban Ramm wrote: > Am 2017-09-27 um 18:13 schrieb Hans Hagen : >> [...] >> The \blockligatures[u:fl:age] is new and something of a joke >> experiment ... I can probably come up with a real advanced and robust >> mechanism if motivated enough > >

Re: [NTG-context] ligature exceptions

On 9/27/2017 11:08 PM, Thomas A. Schmitz wrote: On 09/27/2017 10:25 PM, Henning Hraban Ramm wrote: Thank you for the suggestion. I tried \replaceword[eka][Auflage][Au{fl}age] \setreplacements[eka] and even converted the german wordlist from the selnolig package, but it doesn’t help. Works

Re: [NTG-context] ligature exceptions

On 09/27/2017 10:25 PM, Henning Hraban Ramm wrote: Thank you for the suggestion. I tried \replaceword[eka][Auflage][Au{fl}age] \setreplacements[eka] and even converted the german wordlist from the selnolig package, but it doesn’t help. Works here. You'll have to make a real example.

Re: [NTG-context] ligature exceptions

Am 27.09.2017 um 22:25 schrieb Henning Hraban Ramm: Am 2017-09-27 um 15:39 schrieb Thomas A. Schmitz : On 09/27/2017 02:16 PM, Thomas Widmann wrote: That's a nice idea. If something like that existed, it could be used to change 's' to 'ſ' in relevant places, too.

Re: [NTG-context] ligature exceptions

Am 2017-09-27 um 18:13 schrieb Hans Hagen : > Anyway, in addition to Thomas answer ... we already have this > > \blockligatures[fi,ff] \blockligatures[fl] > \blockligatures[u:fl:age] > > \definefontfeature[default:nolig][default][blockligatures=yes] > > \startTEXpage[offset=1em]

Re: [NTG-context] ligature exceptions

Am 2017-09-27 um 15:39 schrieb Thomas A. Schmitz : > On 09/27/2017 02:16 PM, Thomas Widmann wrote: >> That's a nice idea. If something like that existed, it could be used >> to change 's' to 'ſ' in relevant places, too. > > This exists, see here: >

Re: [NTG-context] ligature exceptions

Am 27.09.2017 um 14:09 schrieb Henning Hraban Ramm: I know I can break ligatures with \/, like Auf\/lage, but is there a general dictionary approach, like \hyphenation{} ? https://ctan.org/tex-archive/macros/luatex/latex/selnolig is a selnolig.lua which could be used for a solution with

Re: [NTG-context] ligature exceptions

On 9/27/2017 5:53 PM, Ulrike Fischer wrote: Am Wed, 27 Sep 2017 15:10:33 +0200 schrieb Tomas Hala: From this point of view, Auf{}lage seems better. This doesn't prevent the ligature: \starttext Auflage Auf{}lage Auf\/lage \stoptext This also documented: "The most important change is

Re: [NTG-context] ligature exceptions

Am Wed, 27 Sep 2017 15:10:33 +0200 schrieb Tomas Hala: > From this point of view, Auf{}lage seems better. This doesn't prevent the ligature: \starttext Auflage Auf{}lage Auf\/lage \stoptext This also documented: "The most important change is that adding a brace group in the middle of a word

Re: [NTG-context] ligature exceptions

There is a LuaLaTeX-package "selnolig" to achieve this goal. Its wordlists and rules could probably be adapted. There is also a thorough discussion of this challenge in the documentation. https://www.ctan.org/pkg/selnolig Best regards, Florian

Re: [NTG-context] ligature exceptions

On 09/27/2017 02:16 PM, Thomas Widmann wrote: That's a nice idea. If something like that existed, it could be used to change 's' to 'ſ' in relevant places, too. This exists, see here: https://www.mail-archive.com/ntg-context@ntg.nl/msg79381.html

Re: [NTG-context] ligature exceptions

Hi Hraban, I am afraid that \/ will break not only the ligature but moreover it will erase the possible breakpoint between f and l. From this point of view, Auf{}lage seems better. General approach might be connected with font some features as Hans shown at ConTeXt Meeting this year. I

Re: [NTG-context] ligature exceptions

On 27 September 2017 at 13:09, Henning Hraban Ramm wrote: > > I know I can break ligatures with \/, like Auf\/lage, but is there a general > dictionary approach, like \hyphenation{} ? That's a nice idea. If something like that existed, it could be used to change 's' to 'ſ' in

[NTG-context] ligature exceptions

Hi all, I know I can break ligatures with \/, like Auf\/lage, but is there a general dictionary approach, like \hyphenation{} ? Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net GPG Key ID 1C9B22FD