Re: [NTG-context] Another bug with ligature-blocking?

2021-03-24 Thread Hans Hagen

On 3/24/2021 8:20 PM, denis.ma...@ub.unibe.ch wrote:

-Ursprüngliche Nachricht-
Von: Hans Hagen 
Gesendet: Mittwoch, 24. März 2021 17:42
An: mailing list for ConTeXt users ; Maier, Denis
Christian (UB) 
Betreff: Re: [NTG-context] Another bug with ligature-blocking?

On 3/24/2021 4:48 PM, denis.ma...@ub.unibe.ch wrote:


\definefontfamily[times][rm][Times New Roman]

don't assume beforehand that something that doesn't work as expected is a
bug


Sorry, Hans, I didn't mean to be offensive.


it has more to do with searching for solutions using the subjects of 
mail ... in which case 'bug' is not a good one




the font just has no ligatures defined which you can remedy (in this
cae) with because it does have the glyphs

\startluacode
  fonts.handlers.otf.addfeature {
  name = "moreligatures",
  type = "ligature",
  data = {
  ['ff'] = { "f", "f" },
  ['fi'] = { "f", "i" },
  ['fl'] = { "f", "l" },
  }
  }
\stopluacode


\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
\definefontfamily[times][rm][Times New Roman]
\definefontfamily[termes[rm][TeX Gyre Termes]

\definefontfeature[default:block][default][blockligatures=yes]

\starttext

{\switchtobodyfont[times] \definedfont[Serif*default]begrifflich
ff fi fl\blank
\definedfont[Serif*default:block] begrifflich ff fi 
fl\blank}
{\switchtobodyfont[termes]\definedfont[Serif*default]begrifflich
ff fi fl\blank
\definedfont[Serif*default:block] begrifflich ff fi 
fl\blank}

\stoptext



I'm not sure I understand what is going on here. I thought \blockligatures 
simply means that instead of a ligature you'll have the regular glyphs in the 
output. Is that not correct?
sure but times doesn't have these ligatures (it has the shapes but not 
the features)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Another bug with ligature-blocking?

2021-03-24 Thread denis.maier
> -Ursprüngliche Nachricht-
> Von: Hans Hagen 
> Gesendet: Mittwoch, 24. März 2021 17:42
> An: mailing list for ConTeXt users ; Maier, Denis
> Christian (UB) 
> Betreff: Re: [NTG-context] Another bug with ligature-blocking?
> 
> On 3/24/2021 4:48 PM, denis.ma...@ub.unibe.ch wrote:
> 
> > \definefontfamily[times][rm][Times New Roman]
> don't assume beforehand that something that doesn't work as expected is a
> bug

Sorry, Hans, I didn't mean to be offensive.

> 
> the font just has no ligatures defined which you can remedy (in this
> cae) with because it does have the glyphs
> 
> \startluacode
>  fonts.handlers.otf.addfeature {
>  name = "moreligatures",
>  type = "ligature",
>  data = {
>  ['ff'] = { "f", "f" },
>  ['fi'] = { "f", "i" },
>  ['fl'] = { "f", "l" },
>  }
>  }
> \stopluacode
> 
> 
> \blockligatures[begrif:fl:ich]
> \definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
> \definefontfamily[times][rm][Times New Roman]
> \definefontfamily[termes[rm][TeX Gyre Termes]
> 
> \definefontfeature[default:block][default][blockligatures=yes]
> 
> \starttext
> 
> {\switchtobodyfont[times] \definedfont[Serif*default]begrifflich
> ff fi fl\blank
>\definedfont[Serif*default:block] begrifflich ff 
> fi fl\blank}
> {\switchtobodyfont[termes]\definedfont[Serif*default]begrifflich
> ff fi fl\blank
>\definedfont[Serif*default:block] begrifflich ff 
> fi fl\blank}
> 
> \stoptext
>

I'm not sure I understand what is going on here. I thought \blockligatures 
simply means that instead of a ligature you'll have the regular glyphs in the 
output. Is that not correct?

Denis
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Another bug with ligature-blocking?

2021-03-24 Thread Hans Hagen

On 3/24/2021 4:48 PM, denis.ma...@ub.unibe.ch wrote:


\definefontfamily[times][rm][Times New Roman]
don't assume beforehand that something that doesn't work as expected is 
a bug


the font just has no ligatures defined which you can remedy (in this 
cae) with because it does have the glyphs


\startluacode
fonts.handlers.otf.addfeature {
name = "moreligatures",
type = "ligature",
data = {
['ff'] = { "f", "f" },
['fi'] = { "f", "i" },
['fl'] = { "f", "l" },
}
}
\stopluacode


\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
\definefontfamily[times][rm][Times New Roman]
\definefontfamily[termes[rm][TeX Gyre Termes]

\definefontfeature[default:block][default][blockligatures=yes]

\starttext

{\switchtobodyfont[times] \definedfont[Serif*default]begrifflich 
ff fi fl\blank
  \definedfont[Serif*default:block] 
begrifflich ff fi fl\blank}
{\switchtobodyfont[termes]\definedfont[Serif*default]begrifflich 
ff fi fl\blank
  \definedfont[Serif*default:block] 
begrifflich ff fi fl\blank}


\stoptext



-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___