[NTG-context] em-/en-dashes and newotf
context at rik.users.panix.com
Tue Jul 14 12:54:06 CEST 2015
On 2015-07-12 12:52, Hans Hagen wrote:
> On 7/12/2015 6:42 PM, Rik Kabel wrote:
>> On 2015-07-12 10:38, Pablo Rodriguez wrote:
>>> On 07/12/2015 04:12 PM, Hans Hagen wrote:
>>>> maybe some file is not loaded ... i uploaded a variant that might work
>>> Many thanks for the new beta.
>>> I’m afraid that this sample doesn’t work with latest beta either:
>>> fiflff no--liga:
>>> --- em--dash
>>> I may be wrong, but I think that the non-deactivated OpenType
>>> feature is
>>> related to the non-activated em- and en-dashes.
>>> To the list members: could you test the sample above and tell em- and
>>> en-dashes work and if no-liga disables ligatures? Adding architecture
>>> may help.
>>> I’m on Linux 32bits.
>>> Many thanks for your help,
>> Same result as Pablo: the ligatures remain even with liga=no, and the
>> hyphens are not replaced by appropriate dashes. Win64 8.1 with ConTeXt
>> 2015.07.12 15:40 build and LuaTeX 0.80.1 rev 5274. My texmf-local
>> contains only a locally-updated version of t-smartref.mkvi.
>> I also have other problems with newotf and definefontfeature that I will
>> put in a separate message.
> i just checked the distribution on a vm and it works ok so best first
> figure out why the tex ligs don't show up (when that relevant file is
> not loaded well other overloads might also fail so that can be the
> reason then for other issues)
Thank you, Hans, for the fixes to feature handling in 2015-07-15 10:37.
Now both the dashes and ligatures in this thread and the failed build
with script=hebr (whatever the relationship to the particular script)
work as expected.
More information about the ntg-context