em-/en-dashes and newotf

Pablo Rodriguez

11 Jul 2015 11 Jul '15

9:09 a.m.

Hans, with the following sample: \usemodule[newotf] %~ \setupbodyfont %~ [palatino] \starttext --- em--dash (with en--dash inside) \stoptext I discovered that em- and en-dashes aren’t enabled by default. Is this intended? Many thanks for your help, Pablo -- http://www.ousia.tk

Show replies by date

Hans Hagen

11 Jul 11 Jul

3:30 p.m.

On 7/11/2015 5:09 PM, Pablo Rodriguez wrote:

...

Hans,

with the following sample:

\usemodule[newotf]

%~ \setupbodyfont %~ [palatino]

\starttext --- em--dash (with en--dash inside) \stoptext

I discovered that em- and en-dashes aren’t enabled by default.

Is this intended?

Rik Kabel

3:55 p.m.

On 2015-07-11 17:30, Hans Hagen wrote:

...

On 7/11/2015 5:09 PM, Pablo Rodriguez wrote:

...
Hans,

with the following sample:

\usemodule[newotf]

%~ \setupbodyfont %~ [palatino]

\starttext --- em--dash (with en--dash inside) \stoptext

I discovered that em- and en-dashes aren’t enabled by default.

Is this intended?

works ok here

Hmmm. Fails here with newotf, works without. Context 2015.07.10T00:05 on Win 8.1 64-bit, with and without jit. -- Rik

Pablo Rodriguez

10:55 p.m.

On 07/11/2015 11:55 PM, Rik Kabel wrote:

...

On 2015-07-11 17:30, Hans Hagen wrote:

...
On 7/11/2015 5:09 PM, Pablo Rodriguez wrote:

...
Hans, [...] I discovered that em- and en-dashes aren’t enabled by default.

Is this intended?

works ok here

Hmmm. Fails here with newotf, works without. Context 2015.07.10T00:05 on Win 8.1 64-bit, with and without jit.

Hans, I’m afraid it still falis with beta from 2015.07.12 00:00, the same way as Rik described. May the different behaviour caused by the fact that you use LuaTeX-0.80.1 (as displayed in http://www.pragma-ade.com/general/qrcs/setup-en.pdf) and we have LuaTeX-0.80? Pablo -- http://www.ousia.tk

Hans Hagen

12 Jul 12 Jul

3:33 a.m.

On 7/12/2015 6:55 AM, Pablo Rodriguez wrote:

...

On 07/11/2015 11:55 PM, Rik Kabel wrote:

...
On 2015-07-11 17:30, Hans Hagen wrote:

...
On 7/11/2015 5:09 PM, Pablo Rodriguez wrote:

...
Hans, [...] I discovered that em- and en-dashes aren’t enabled by default.

Is this intended?

works ok here

Hmmm. Fails here with newotf, works without. Context 2015.07.10T00:05 on Win 8.1 64-bit, with and without jit.

Hans,

I’m afraid it still falis with beta from 2015.07.12 00:00, the same way as Rik described.

May the different behaviour caused by the fact that you use LuaTeX-0.80.1 (as displayed in http://www.pragma-ade.com/general/qrcs/setup-en.pdf) and we have LuaTeX-0.80?

i can't imagine .. can you wipe the cache files ----------------------------------------------------------------- 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 -----------------------------------------------------------------

Pablo Rodriguez

4:49 a.m.

On 07/12/2015 11:33 AM, Hans Hagen wrote:

...

On 7/12/2015 6:55 AM, Pablo Rodriguez wrote:

...
[...] May the different behaviour caused by the fact that you use LuaTeX-0.80.1 (as displayed in http://www.pragma-ade.com/general/qrcs/setup-en.pdf) and we have LuaTeX-0.80?

i can't imagine .. can you wipe the cache files

I do it everytime I update the beta. But I did it again. I even installed the Suite from scratch. I’m afraid none of them worked. Pablo -- http://www.ousia.tk

Hans Hagen

8:12 a.m.

On 7/12/2015 12:49 PM, Pablo Rodriguez wrote:

...

On 07/12/2015 11:33 AM, Hans Hagen wrote:

...
On 7/12/2015 6:55 AM, Pablo Rodriguez wrote:

...
[...] May the different behaviour caused by the fact that you use LuaTeX-0.80.1 (as displayed in http://www.pragma-ade.com/general/qrcs/setup-en.pdf) and we have LuaTeX-0.80?

i can't imagine .. can you wipe the cache files

I do it everytime I update the beta. But I did it again. I even installed the Suite from scratch.

I’m afraid none of them worked.

maybe some file is not loaded ... i uploaded a variant that might work better 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 -----------------------------------------------------------------

Pablo Rodriguez

8:38 a.m.

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

Axel Kielhorn

9:04 a.m.

...

Am 12.07.2015 um 16:38 schrieb Pablo Rodriguez :

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 using current version: 2015.07.12 00:00 on MacOSX 10.10 I get ligatures in both cases and neither em nor en dash. Now I have current version: 2015.07.12 15:40 still on MacOSX 10.10 No ligatures in the second case and both en and em dash. Axel

Pablo Rodriguez

9:25 a.m.

On 07/12/2015 05:04 PM, Axel Kielhorn wrote:

...

...
Am 12.07.2015 um 16:38 schrieb Pablo Rodriguez: [...] 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 using current version: 2015.07.12 00:00 on MacOSX 10.10

I get ligatures in both cases and neither em nor en dash.

Now I have current version: 2015.07.12 15:40 still on MacOSX 10.10

No ligatures in the second case and both en and em dash.

Many thanks for your reply, Axel. For some strange reason I also get ligatures with latest beta from 2015.07.12 15:40 (which I shouldn’t get). Everything works as expected when commenting \usemodule[newotf]. Pablo -- http://www.ousia.tk

Otared Kavian

9:17 a.m.

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 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 ___________________________________________________________________________________

Pablo Rodriguez

9:27 a.m.

On 07/12/2015 05:17 PM, Otared Kavian wrote:

...

Hi Pablo,

On my installation everything seems to work fine: Context version 2015.07.12 15:40

Hi Otared, many thanks for your reply. Which is your OS and architecture? Many thanks again, Pablo -- http://www.ousia.tk

Hans Hagen

9:57 a.m.

On 7/12/2015 5:27 PM, Pablo Rodriguez wrote:

...

On 07/12/2015 05:17 PM, Otared Kavian wrote:

...
Hi Pablo,

On my installation everything seems to work fine: Context version 2015.07.12 15:40

Hi Otared,

many thanks for your reply.

Which is your OS and architecture?

you use m-newotf from the distribution? ----------------------------------------------------------------- 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 -----------------------------------------------------------------

Pablo Rodriguez

10:03 a.m.

On 07/12/2015 05:57 PM, Hans Hagen wrote:

...

On 7/12/2015 5:27 PM, Pablo Rodriguez wrote:

...
[...] Hi Otared,

many thanks for your reply.

Which is your OS and architecture?

you use m-newotf from the distribution?

I use the one installed after updating the beta. I have just checked it and it differs from the one you sent to the mailing list. Pablo -- http://www.ousia.tk

Rik Kabel

10:42 a.m.

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. -- Rik Kabel

Hans Hagen

10:52 a.m.

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 -----------------------------------------------------------------

Rik Kabel

14 Jul 14 Jul

4:54 a.m.

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 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

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. -- Rik

Pablo Rodriguez

7:42 a.m.

On 07/14/2015 12:54 PM, Rik Kabel wrote:

...

On 2015-07-12 12:52, Hans Hagen wrote:

...
[...] 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

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.

Hans, checking beta from 2015.07.12 23:30 in Win7 64bit works fine (ligatures, no ligatures and dashes) with newotf. But I’m afraid that beta from 2015.07.14 10:37 doesn’t work disabling ligatures and enabling dashes in Linux 32bit. I’ll try to check the Linux 32bit ConTeXt with another computer. Many thanks for your help, Pablo -- http://www.ousia.tk

Hans Hagen

11:11 a.m.

On 7/14/2015 3:42 PM, Pablo Rodriguez wrote:

...

On 07/14/2015 12:54 PM, Rik Kabel wrote:

...
On 2015-07-12 12:52, Hans Hagen wrote:

...
[...] 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

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.

Hans,

checking beta from 2015.07.12 23:30 in Win7 64bit works fine (ligatures, no ligatures and dashes) with newotf.

But I’m afraid that beta from 2015.07.14 10:37 doesn’t work disabling ligatures and enabling dashes in Linux 32bit.

I’ll try to check the Linux 32bit ConTeXt with another computer.

there is no dependency on the platform 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 -----------------------------------------------------------------

Pablo Rodriguez

19 Jul 19 Jul

5:17 a.m.

On 07/14/2015 07:11 PM, Hans Hagen wrote:

...

On 7/14/2015 3:42 PM, Pablo Rodriguez wrote:

...
Hans,

checking beta from 2015.07.12 23:30 in Win7 64bit works fine (ligatures, no ligatures and dashes) with newotf.

But I’m afraid that beta from 2015.07.14 10:37 doesn’t work disabling ligatures and enabling dashes in Linux 32bit.

I’ll try to check the Linux 32bit ConTeXt with another computer.

there is no dependency on the platform

Hans, the problem was fixed when I remembered to remove the m-newotf.mkiv file you sent to the list from my home directory. Sorry for the noise. I’m still experiencing the issue with a particular font. Since the font was generated with FontForge, I would like to know what the font is missing to report the bug upstream. Many thanks for your help, Pablo -- http://www.ousia.tk

3285

Age (days ago)

3293

Last active (days ago)

List overview

Download

19 comments

5 participants

participants (5)

Axel Kielhorn
Hans Hagen
Otared Kavian
Pablo Rodriguez
Rik Kabel

em-/en-dashes and newotf

tags

participants (5)