On 1/18/2016 7:31 AM, Jan U. Hasecke wrote:
Am 17.01.2016 um 20:05 schrieb Hans Hagen:
On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:
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
Am 17.01.2016 um 20:05 schrieb Hans Hagen:
> On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:
>>
>> 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
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.
> On 16 Jan 2016, at 12:24, Jan U. Hasecke wrote:
>
> Both solutions work fine if I use them in a simple context file, but I
> can't use neither solution in my xml processing.
>
> I use a customized version of the from-pandoc-to-context solution of Pablo.
>
> When
Dear list,
some time ago I ask for a way to selectively suppress ligatures. Hans
told me to use the replacement feature.
- http://www.ntg.nl/pipermail/ntg-context/2015/083044.html
- http://www.ntg.nl/pipermail/ntg-context/2015/083034.html
In another thread a solution with the translate module
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. -->