From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: em-/en-dashes and newotf
Date: Sun, 12 Jul 2015 12:17:59 -0300 [thread overview]
Message-ID: <DF047E13-61D0-4BEC-BBFC-6B4582A6AA99@gmail.com> (raw)
In-Reply-To: <55A27BDB.4080308@gmx.es>
[-- Attachment #1.1: Type: text/plain, Size: 1641 bytes --]
Hi Pablo,
On my installation everything seems to work fine: Context version 2015.07.12 15:40
Please see the attached file.
Best regards: OK
> On 12 Jul 2015, at 11:38, Pablo Rodriguez <oinos@gmx.es> 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
> --
> http://www.ousia.tk
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #1.2.1: Type: text/html, Size: 772 bytes --]
[-- Attachment #1.2.2: newotf-ligatures.pdf --]
[-- Type: application/pdf, Size: 8129 bytes --]
[-- Attachment #1.2.3: Type: text/html, Size: 2633 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 15:17 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 [this message]
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
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=DF047E13-61D0-4BEC-BBFC-6B4582A6AA99@gmail.com \
--to=otared@gmail.com \
--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).