[NTG-context] --|--- not transformed to endash|emdash

Tomas Hala tomas.hala at mendelu.cz
Wed Oct 24 19:24:17 CEST 2018


Hi Hans, 

you are right, tlig is the missing one. Thank you for directing me.

Does it mean that all features are disabled when the new "non-TeX" font is joined? 
(I used \starttypescript with \definefontsynonym; then \definetypeface and \setupbodyfont.)

Later I discovered [features=default] (at \definefontsynonym) which enables it, too.
Which features are enabled by this word default?

Side effect of my experimets was the syntantic error  "! Missing \endcsname inserted"
at \definefontsynonym [Serif][name:JohnBaskerville][] with empty last brackets.
Is it ok, or not?

Best wishes,

Tomáš

Tue, Oct 23, 2018 ve 07:08:44PM +0200 Hans Hagen napsal(a):
# On 10/23/2018 6:36 PM, Tomas Hala wrote:
# >Hi all,
# >
# >usually, if one writes -- or ---, will receive real en-dash or em-dash,
# >respectively. I just tried font called JohnBaskerville
# >(commercial; from Štorm type foundry, CZ) but I got only '--' and '---',
# >ie. sequences were not transformed to the proper characters.
# >
# >Dashes are present in then font, commands \endash and \emdash produce them correctly.
# >
# >What could be wrong?
# 
# no features enabled?
# 
# -----------------------------------------------------------------
#                                           Hans Hagen | PRAGMA ADE
#               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
#        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
# -----------------------------------------------------------------

                                         Tomáš Hála
--------------------------------------------------------------------
Mendelova univerzita, Provozně ekonomická fakulta, ústav informatiky
Zemědělská 1, CZ-613 00 Brno,  tel. +420 545 13 22 28
--------------------------------------------------------------------
http://akela.mendelu.cz/~thala


More information about the ntg-context mailing list