From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: em-/en-dashes and newotf
Date: Sun, 12 Jul 2015 18:52:06 +0200 [thread overview]
Message-ID: <55A29B36.6030707@wxs.nl> (raw)
In-Reply-To: <55A298FE.1020001@rik.users.panix.com>
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
>>> better
>> Many thanks for the new beta.
>>
>> I’m afraid that this sample doesn’t work with latest beta either:
>>
>> \usemodule[newotf]
>>
>> \definefontfeature[noliga][liga=no]
>>
>> \starttext
>> \startTEXpage[offset=1em]
>> fiflff no--liga:
>> \addfeature[noliga]fiflff
>>
>> --- em--dash
>> \stopTEXpage
>> \stoptext
>>
>> 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,
>>
>>
>> Pablo
> 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)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-07-12 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 15:09 Pablo Rodriguez
2015-07-11 21:30 ` Hans Hagen
2015-07-11 21:55 ` Rik Kabel
2015-07-12 4:55 ` Pablo Rodriguez
2015-07-12 9:33 ` Hans Hagen
2015-07-12 10:49 ` Pablo Rodriguez
2015-07-12 14:12 ` Hans Hagen
2015-07-12 14:38 ` Pablo Rodriguez
2015-07-12 15:04 ` Axel Kielhorn
2015-07-12 15:25 ` Pablo Rodriguez
2015-07-12 15:17 ` Otared Kavian
2015-07-12 15:27 ` Pablo Rodriguez
2015-07-12 15:57 ` Hans Hagen
2015-07-12 16:03 ` Pablo Rodriguez
2015-07-12 16:42 ` Rik Kabel
2015-07-12 16:52 ` Hans Hagen [this message]
2015-07-14 10:54 ` Rik Kabel
2015-07-14 13:42 ` Pablo Rodriguez
2015-07-14 17:11 ` Hans Hagen
2015-07-19 11:17 ` Pablo Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55A29B36.6030707@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).