[NTG-context] oldstyle

[Meer, Hans van der]

I have the Lucida Bright otf fontset. What fontname to use in simplefonts
  \definefontfamily [mainface] [os] [Lucida Bright ??]
in order to get {\os 123} in oldstyle?

Hans van der Meer




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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Thomas A. Schmitz]

On 01/17/2016 07:24 PM, Hans Hagen wrote:

it should work in the in beta now


Hi Hans,

now I have a problem :-) What should take precedence if an entity is 
both defined in the dtd and as a \xmltexentity? The way I see it, the 
latter: e.g., in the DTD, I might declare something for use in a browser 
but require a different solution when typesetting with ConTeXt. The 
latest and greatest now takes my DTD definitions instead of the 
\xmltexentities, which did not happen before. Is that an unwanted side 
effect or the new default?


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

Re: [NTG-context] xtables doesn't work in CLD

[Romain Diss]

Hi,

Le 02/01/2016, Hans Hagen a écrit
> On 12/31/2015 2:57 PM, Romain Diss wrote:
> >Hi all,
> >
> >I am trying to use xtables in a CLD document but when I add a row, it
> >doesn't compile anymore. Is there something wrong? If xtables is not
> >usable with CLD, what is the best set of table commands to use with CLD?
> >
> >% Minimum not working example :
> >context.starttext()
> >context.startxtable()
> > context.startxrow()
> > context.startxcell()
> > context("Test")
> > context.stopxcell()
> > context.stopxrow()
> >context.stopxtable()
> >context.stoptext()
> >% end of the example.
> 
> that has to do with the fact that such a table gets buffered (it needs
> several passes)
> 
> i added an experimental trick to the next beta that makes this run ok
It works well, thank you very much.

All the best.

-- 
Romain Diss
___
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
___

Re: [NTG-context] Binaries for Linux (warning)

[Alan BRASLAU]

On Mon, 18 Jan 2016 09:44:43 +0100
Mojca Miklavec  wrote:

> Hi,
> 
> Alan now tried compiling the luatex binaries for Linux on Debian
> rather than on some ancient CentOS (like he did in the past).
> 
> In case that any Linux user experiences problems, please let us know
> and we'll switch back to CentOS with an older libc, otherwise we would
> prefer to stick with Debian (oldstable).

The ./first-setup.sh download will FAIL on CentOS 5 and other older linux 
installations
dating from the last century as follows: 

sent 19 bytes  received 47 bytes  132.00 bytes/sec
total size is 3525  speedup is 53.41
receiving incremental file list
bin/
bin/luatex

sent 17954 bytes  received 6826826 bytes  1955651.43 bytes/sec
total size is 9533569  speedup is 1.39
texlua: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by texlua)


Please note that the 32bit luatex binaries have been compiled on 
Debian/oldstable
for some time and this has not appeared to have caused any problems.

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

Re: [NTG-context] Arabic Letters are disjointed and reversed in headers and margin

[Wolfgang Schuster]

Ibn Saeed 
18. Januar 2016 um 08:15


By using right

\setupmargindata
[margintext]
[align=r2l]

and
\setupalign[r2l]

The margin arabic text appears correctly

But the arabic texts in the header is still the same.

\setupheader[style=\righttoleft]

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

[NTG-context] Ligatures in EB Garamond (was: \replaceword and \setreplacements with xml files)

[Jan U. Hasecke]

Am 17.01.2016 um 20:05 schrieb Hans Hagen:
> On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:
>> Am 16.01.2016 um 13:31 schrieb Schmitz Thomas A.:
>>>
>>> Please provide a minimal example of your problem. It’s impossible to
>>> help when we have no clue what you’re doing.
>>
>> Sorry, of course.
>>
>> After setting up a mwe I found that it is a font related issue.
>>
>> When I don't specify a font, it works. --> example.tex
>>
>> When I choose EB Garamond, it does not work. -- example-Garamond.tex
>>
>> I confirmed this behaviour in my real setup.
> 
> don't assume that ligatures are always real ligatures ... in that font
> it's just kerning .. this kind of works okay:
> 
> \replaceword[sellig][auflösen][auf{-}{}{\zwnj}lösen]

I am confused as the specimen of EB Garamond mentions (real) ligatures.
They are listed as glyphs.

https://github.com/georgd/EB-Garamond/blob/master/specimen/Specimen.pdf

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

Re: [NTG-context] Arabic Letters are disjointed and reversed in headers and margin

[Ibn Saeed]

Wolfgang Schuster  gmail.com> writes:

> 
> \setupheader[style=\righttoleft]
> Wolfgang
>

Thank you very much. 

This solves the issue of the arabic text in header as well.



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

Re: [NTG-context] \replaceword and \setreplacements with xml files

[Hans Hagen]

On 1/18/2016 7:31 AM, Jan U. Hasecke wrote:

Am 17.01.2016 um 20:05 schrieb Hans Hagen:

On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:


When I choose EB Garamond, it does not work. -- example-Garamond.tex

I confirmed this behaviour in my real setup.


don't assume that ligatures are always real ligatures ... in that font
it's just kerning .. this kind of works okay:

\replaceword[sellig][auflösen][auf{-}{}{\zwnj}lösen]


Thanks a lot. This was new to me.


there are many hidden tricks ... to be revealed in due time (so that we 
can suggest that it was just implemented)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

Re: [NTG-context] Ligatures in EB Garamond

[Hans Hagen]

On 1/18/2016 10:16 AM, Jan U. Hasecke wrote:

Am 17.01.2016 um 20:05 schrieb Hans Hagen:

On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:

Am 16.01.2016 um 13:31 schrieb Schmitz Thomas A.:


Please provide a minimal example of your problem. It’s impossible to
help when we have no clue what you’re doing.


Sorry, of course.

After setting up a mwe I found that it is a font related issue.

When I don't specify a font, it works. --> example.tex

When I choose EB Garamond, it does not work. -- example-Garamond.tex

I confirmed this behaviour in my real setup.


don't assume that ligatures are always real ligatures ... in that font
it's just kerning .. this kind of works okay:

\replaceword[sellig][auflösen][auf{-}{}{\zwnj}lösen]


I am confused as the specimen of EB Garamond mentions (real) ligatures.
They are listed as glyphs.

https://github.com/georgd/EB-Garamond/blob/master/specimen/Specimen.pdf


maybe the archaic st ligature is a precomposed but f f l i aren't done 
that way but by either kerning or replacement of individual glyphs + 
kerning (there are many methods for this) ... also, 'liga' might mean 
ligature but in practice is used for all kind of things ... in opentype 
'ligature substitution' is just a many-to-one replacement but that 
doesn't mean that 'liga' uses that ... welcome to the inconsistent open 
type mess


Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

[NTG-context] Binaries for Linux (warning)

[Mojca Miklavec]

Hi,

Alan now tried compiling the luatex binaries for Linux on Debian
rather than on some ancient CentOS (like he did in the past).

In case that any Linux user experiences problems, please let us know
and we'll switch back to CentOS with an older libc, otherwise we would
prefer to stick with Debian (oldstable).

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

Re: [NTG-context] RTL problem with figure numbers

[Hans Hagen]

On 1/18/2016 7:12 AM, Mohammad Hossein Bateni wrote:

I just found a solution to the last question:

\defineseparatorset[dashsep][][{--}]
\setuphead[section][sectionseparatorset=dashsep]


maybe collect all the r2l thing son the wiki so that eventually we can 
figure out some presets


Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

Re: [NTG-context] \quote inside \emph

[Hans Hagen]

On 1/18/2016 3:19 AM, Aditya Mahajan wrote:

On Mon, 18 Jan 2016, Wolfgang Schuster wrote:


Hans Hagen 
18. Januar 2016 um 00:56


we could change it (i don't care too much as i've never use them nested)

up to you/wolfgang/... to decide

Remove the default setting and for completeness sake add style/color
settings to the paragraph alternative.

\unexpanded\def\typo_delimited_par
 {\groupedcommand

{\dostarttaggedchained\t!delimited\currentdelimitedtext\??delimitedtext %
block?
 \typo_delimited_handle_left\c!left
+ \usedelimitedtextstyleandcolor\c!style\c!color
 \dostarttagged\t!delimitedcontent\empty}
{\dostoptagged
 \typo_delimited_handle_right\c!right
 \removelastskip
 \dostoptagged
 \typo_delimited_pop}}


I agree. Removing the default setting (style=normal) will be the
simplest solution.


ok (btw, in the past 'normal' was used as signal)

Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

[NTG-context] Page Numbers change after 9 to 01 - 11 -21 - 31 and so on.

[Ibn Saeed]

Hello

I am trying to typeset a book in arabic in ConTeXt. I have stumbled upon 
this issue

Page Numbers change after 9 
to 01 for page 10
21 for page 12
31 for page 13
41 for page 14
and so on

Here is the snapshot of the page number issue:
https://i.imgsafe.org/a5f34fb.jpg



Here is my ConTeXt Code:

\mainlanguage[arabic]

\setupdirections[bidi=global]

\definefontfeature
  [arabic]
  [mode=node,language=dflt,script=arab,
init=yes,medi=yes,fina=yes,isol=yes,
liga=yes,dlig=yes,rlig=yes,tlig=yes,
calt=yes,trep=yes,clig=yes,
mark=yes,mkmk=yes,kern=yes,curs=yes]


\starttypescript [serif] [arabic]
  \definefontsynonym [Arabic-Regular] [file:ScheherazadeRegOT.ttf] 
[features=arabic]
  \definefontsynonym [Arabic-Bold] [file:ScheherazadeRegOT.ttf] 
[features=arabic]
\stoptypescript

\starttypescript [serif] [arabic] [name]
 \usetypescript[serif][fallback]
 \definefontsynonym [Serif] [Arabic-Regular] [features=arabic]
 \definefontsynonym [SerifBold] [Arabic-Bold][features=arabic]
\stoptypescript

\starttypescript [Arabic]
  \definetypeface [Arabic] [rm] [serif] [arabic] [default] 
\stoptypescript 
  


\setupmargindata[margintext]
[align=r2l]

\setupalign[r2l]  


\setuppapersize[A4]


\setuplayout[
  grid=min,
  backspace=46.666mm, width=140mm,
  topspace=33.000mm, height=198mm,
  header=12.9mm,footer=9mm,
  ]
  
  
%% Double sided document
\setuppagenumbering[
  alternative=doublesided,
  state=none,
  location={header,marginedge},
%  conversion=romannumerals, left={--~}, right={~--},
]


\setupbodyfont[Arabic,18pt]
\setupinterlinespace[line=42pt]

 
\setupheads[number=no]
\setuphead[chapter]
[style=\bfd,before=,after=\blank,alternative=middle,grid=both]
\setuphead[section][style=\bfc,before=\blank,after=,grid=both]

\setupbackgrounds[text][text][frame=off, topframe=on]

\setupheader[style=\righttoleft, state=normal] 

\setupheadertexts
[{\getmarking[chapter]}][{\pagenumber}]
[{\pagenumber}][{\getmarking[chapter]}]



\starttext
\chapter{شرح الآجرومية}
الحمد لله رب العالمين، وصلى الله وسلم وبارك على عبده ورسوله نبينا محمد وعلى 
آله وصحبه أجمعين، أما بعد:\\
\stoptext
___
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
___

Re: [NTG-context] Page Numbers change after 9 to 01 - 11 -21 - 31 and so on.

[Ibn Saeed]

It seems to be the issue with 

\setupheader[style=\righttoleft, state=normal] 

The style is righttoleft to accomodate the proper direction for arabic text. 
But it messes up the page number direction.

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

Re: [NTG-context] Arabic Letters are disjointed and reversed in headers and margin

[Mohammad Hossein Bateni]

This makes all the text LTR, for instance if one has an English word
embedded in the RTL text, that will be shown incorrectly.  Or even if one
of the headers (say, on the left side) is plain English.

Why wouldn't something like the following work?

\startsetups setup:bidi

\setupdirections[bidi=on,method=default,fences=no]

\stopsetups

\setupheader[setups=setup:bidi]



On Mon, Jan 18, 2016 at 4:11 AM, Ibn Saeed  wrote:

> Wolfgang Schuster  gmail.com> writes:
>
> >
> > \setupheader[style=\righttoleft]
> > Wolfgang
> >
>
> Thank you very much.
>
> This solves the issue of the arabic text in header as well.
>
>
>
>
> ___
> 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
>
> ___
>
___
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
___

Re: [NTG-context] RTL problem with figure numbers

[Mohammad Hossein Bateni]

That's on my agenda.  I'll explore things a little more and hopefully will
set up such a page in a few weeks.

On Mon, Jan 18, 2016 at 5:13 AM, Hans Hagen  wrote:

> On 1/18/2016 7:12 AM, Mohammad Hossein Bateni wrote:
>
>> I just found a solution to the last question:
>>
>> \defineseparatorset[dashsep][][{--}]
>> \setuphead[section][sectionseparatorset=dashsep]
>>
>
> maybe collect all the r2l thing son the wiki so that eventually we can
> figure out some presets
>
> Hans
>
>
> -
>   Hans Hagen | PRAGMA ADE
>   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>   tel: 038 477 53 69 | 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
>
> ___
>
___
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
___

Re: [NTG-context] Page Numbers change after 9 to 01 - 11 -21 - 31 and so on.

[Mohammad Hossein Bateni]

One hacky way to fix it is the following:

\setupheadertexts
[{\getmarking[chapter]}][{\lefttoright\pagenumber}]
[{\lefttoright\pagenumber}][{\getmarking[chapter]}]

Ideally \setupdirections[bidi] or something like that should be used, as I
mentioned in the other thread; that'll fix a bunch of other problems, as
well.


On Mon, Jan 18, 2016 at 1:14 PM, Ibn Saeed  wrote:

> It seems to be the issue with
>
> \setupheader[style=\righttoleft, state=normal]
>
> The style is righttoleft to accomodate the proper direction for arabic
> text.
> But it messes up the page number direction.
>
>
> ___
> 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
>
> ___
>
___
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
___

[NTG-context] Luatex 0.88.0 announcement

[luigi scarso]

==
Luatex Release 0.88.0 was released 2016011500
==

This is a next step upto 0.90 and it has the following changes:

- mostly small bug fixes

- a few setters/getters added to the pdf namespace (were in the tex one
before)

- The current libraries under libs are now:
  * poppler-0.40.0
  * mpfr-3.1.3
  * luajit-2.1.0-beta1
  * gmp-6.1.0
  * zziplib-0.13.62
  * zlib-1.2.8
  * lua52-5.2.4
  * pixman-0.32.8
  * libpng-1.6.21
  * cairo-1.14.6


Have fun,
The luatex team
___
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
___

Re: [NTG-context] Ligatures in EB Garamond

[Jan U. Hasecke]

Am 18.01.2016 um 11:09 schrieb Hans Hagen:
> On 1/18/2016 10:16 AM, Jan U. Hasecke wrote:
>> Am 17.01.2016 um 20:05 schrieb Hans Hagen:
>>> On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:
 Am 16.01.2016 um 13:31 schrieb Schmitz Thomas A.:
>
> Please provide a minimal example of your problem. It’s impossible to
> help when we have no clue what you’re doing.

 Sorry, of course.

 After setting up a mwe I found that it is a font related issue.

 When I don't specify a font, it works. --> example.tex

 When I choose EB Garamond, it does not work. -- example-Garamond.tex

 I confirmed this behaviour in my real setup.
>>>
>>> don't assume that ligatures are always real ligatures ... in that font
>>> it's just kerning .. this kind of works okay:
>>>
>>> \replaceword[sellig][auflösen][auf{-}{}{\zwnj}lösen]
>>
>> I am confused as the specimen of EB Garamond mentions (real) ligatures.
>> They are listed as glyphs.
>>
>> https://github.com/georgd/EB-Garamond/blob/master/specimen/Specimen.pdf
> 
> maybe the archaic st ligature is a precomposed but f f l i aren't done
> that way but by either kerning or replacement of individual glyphs +
> kerning (there are many methods for this) ... also, 'liga' might mean
> ligature but in practice is used for all kind of things ... in opentype
> 'ligature substitution' is just a many-to-one replacement but that
> doesn't mean that 'liga' uses that ... welcome to the inconsistent open
> type mess
> 

Mh, yes. :-(

Two additional questions. Shall I file a bugreport for this issue? What
would be the right words: please provide real ligature glyphs instead of
composed ones?

EB Garamond is a free font also in the sense free of charge. But what
can I expect when I buy a commercial font? I would be quite annoyed when
I buy a font which does not provide the features in a way that I can use
them in ConTeXt.

Is there a font quality page on the Wiki with a feature comparison?

juh

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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Kate F]

On 18 January 2016 at 13:30, Thomas A. Schmitz
 wrote:
> On 01/17/2016 07:24 PM, Hans Hagen wrote:
>>
>> it should work in the in beta now

Wonderful! Thank you so much.


> Hi Hans,
>
> now I have a problem :-) What should take precedence if an entity is both
> defined in the dtd and as a \xmltexentity? The way I see it, the latter:
> e.g., in the DTD, I might declare something for use in a browser but require
> a different solution when typesetting with ConTeXt. The latest and greatest
> now takes my DTD definitions instead of the \xmltexentities, which did not
> happen before. Is that an unwanted side effect or the new default?

I was just about to ask the same!

I agree that \xmltexentity ought to have precedence. I have an example:



Which for some reason is being rendered as U+FFFD REPLACEMENT
CHARACTER (a question-mark in a diamond). I don't know why that comes
out as U+FFFD actually, since if I type a literal non-breaking space
character instead, the PDF comes out just as if I'd used ~ in TeX.
Maybe that's a bug somewhere?

In any case, I think that sometimes it is helpful to override entities
specifically for TeX processing, which aren't relevant for processing
the XML source in other ways.

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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Kate F]

On 18 January 2016 at 13:30, Thomas A. Schmitz
 wrote:
> On 01/17/2016 07:24 PM, Hans Hagen wrote:
>>
>> it should work in the in beta now
>
>
> Hi Hans,
>
> now I have a problem :-) What should take precedence if an entity is both
> defined in the dtd and as a \xmltexentity? The way I see it, the latter:
> e.g., in the DTD, I might declare something for use in a browser but require
> a different solution when typesetting with ConTeXt. The latest and greatest
> now takes my DTD definitions instead of the \xmltexentities, which did not
> happen before. Is that an unwanted side effect or the new default?
>

Ah, there's a bug:

-i">

This should produce an  node in the DOM tree, just as if you'd
typed that out where the entity is used. Currently ConTeXt takes that
as literal text, as if you'd typed "option-ioption/"

Often I wish XML weren't so complex...

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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Hans Hagen]

On 1/18/2016 5:22 PM, Kate F wrote:

On 18 January 2016 at 13:30, Thomas A. Schmitz
 wrote:

On 01/17/2016 07:24 PM, Hans Hagen wrote:


it should work in the in beta now



Hi Hans,

now I have a problem :-) What should take precedence if an entity is both
defined in the dtd and as a \xmltexentity? The way I see it, the latter:
e.g., in the DTD, I might declare something for use in a browser but require
a different solution when typesetting with ConTeXt. The latest and greatest
now takes my DTD definitions instead of the \xmltexentities, which did not
happen before. Is that an unwanted side effect or the new default?



Ah, there's a bug:

 -i">

This should produce an  node in the DOM tree, just as if you'd
typed that out where the entity is used. Currently ConTeXt takes that
as literal text, as if you'd typed "option-ioption/"

Often I wish XML weren't so complex...


are you sure? i've never seen that

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

[NTG-context] Accessibility and Tagged PDF/A, Footnotes showing

[Ursula Hermann]

Hello Hans and Dr. Dominik Klein!

Today I found a Thread about Accessibility from last Juli!


I work at the University in Vienna,  and I work with students, who are
blind or have a see handicap. So I read this Thread today.

Last year in Summer I began to read the manual of Context.

I have a question to this discussion, it is nessesary to know: How can
footnotes be shown in the PDF/A tagged PDF, in a text?

What I mean something, that shows in the Text the text from the footnote,
when I click on the number from the footnote.


Maybe with a tooltip? Or what is the right way? Which command?

Ursula Hermann




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

Re: [NTG-context] Ligatures in EB Garamond

[Hans Hagen]

On 1/18/2016 1:46 PM, Jan U. Hasecke wrote:

Am 18.01.2016 um 11:09 schrieb Hans Hagen:

On 1/18/2016 10:16 AM, Jan U. Hasecke wrote:

Am 17.01.2016 um 20:05 schrieb Hans Hagen:

On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:

Am 16.01.2016 um 13:31 schrieb Schmitz Thomas A.:


Please provide a minimal example of your problem. It’s impossible to
help when we have no clue what you’re doing.


Sorry, of course.

After setting up a mwe I found that it is a font related issue.

When I don't specify a font, it works. --> example.tex

When I choose EB Garamond, it does not work. -- example-Garamond.tex

I confirmed this behaviour in my real setup.


don't assume that ligatures are always real ligatures ... in that font
it's just kerning .. this kind of works okay:

\replaceword[sellig][auflösen][auf{-}{}{\zwnj}lösen]


I am confused as the specimen of EB Garamond mentions (real) ligatures.
They are listed as glyphs.

https://github.com/georgd/EB-Garamond/blob/master/specimen/Specimen.pdf


maybe the archaic st ligature is a precomposed but f f l i aren't done
that way but by either kerning or replacement of individual glyphs +
kerning (there are many methods for this) ... also, 'liga' might mean
ligature but in practice is used for all kind of things ... in opentype
'ligature substitution' is just a many-to-one replacement but that
doesn't mean that 'liga' uses that ... welcome to the inconsistent open
type mess



Mh, yes. :-(

Two additional questions. Shall I file a bugreport for this issue? What
would be the right words: please provide real ligature glyphs instead of
composed ones?


there are many fonts out that that do similar things replacing f an i by 
different shapes, or overlaying, or kerning, or replacing by one char, 
looking forward (from f to i) or backward (from i to f) ... as all is 
technically possible/permitted nothing is a bug (but there might be 
occasional differences between hyphenation although quite some effort 
went into getting that kind of right ... and it makes a good topic for 
complex hard to follow boring presentations (see attachment)


(btw, sometimes glyphs get funny non standard names in which case 
roundtrip copy/paste becomes a mess)



EB Garamond is a free font also in the sense free of charge. But what
can I expect when I buy a commercial font? I would be quite annoyed when
I buy a font which does not provide the features in a way that I can use
them in ConTeXt.


you can expect the same ... in fact you can also expect type1 -> otf 
converted fonts with hardly any use of opentype features



Is there a font quality page on the Wiki with a feature comparison?


that would be nice (has been discussed)

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-


ligatures.pdf
Description: Adobe PDF document
___
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
___

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Kate F]

On 18 January 2016 at 21:16, Hans Hagen  wrote:
> On 1/18/2016 9:49 PM, Kate F wrote:
>>
>> On 18 January 2016 at 19:13, Hans Hagen  wrote:
>>>
>>> On 1/18/2016 5:22 PM, Kate F wrote:


 On 18 January 2016 at 13:30, Thomas A. Schmitz
  wrote:
>
>
> On 01/17/2016 07:24 PM, Hans Hagen wrote:
>>
>>
>>
>> it should work in the in beta now
>
>
>
>
> Hi Hans,
>
> now I have a problem :-) What should take precedence if an entity is
> both
> defined in the dtd and as a \xmltexentity? The way I see it, the
> latter:
> e.g., in the DTD, I might declare something for use in a browser but
> require
> a different solution when typesetting with ConTeXt. The latest and
> greatest
> now takes my DTD definitions instead of the \xmltexentities, which did
> not
> happen before. Is that an unwanted side effect or the new default?
>

 Ah, there's a bug:

   -i">

 This should produce an  node in the DOM tree, just as if you'd
 typed that out where the entity is used. Currently ConTeXt takes that
 as literal text, as if you'd typed "option-ioption/"

 Often I wish XML weren't so complex...
>>>
>>>
>>>
>>> are you sure? i've never seen that
>>>
>>> Hans
>>
>>
>> Yep!
>>
>> These are called "internal parsed entities". "Parsed" requires that
>> any tags *inside* the entity must be balanced, unlike in SGML
>> entities.
>>
>> Sorry I can't find a clear explanation in the XML spec; it's a pretty
>> confusing document.
>> But here's some random person's slide illustrating an example:
>> http://images.slideplayer.com/23/6622270/slides/slide_47.jpg
>>
>> libxml2 deals with these correctly, which is what I've been using
>> (xsltproc and friends) for my documents which use them. I generally
>> trust libxml2 to get things right.
>>
>> I use these entities to centralise often-repeated fragments between
>> documents, kind of like how you might use a primitive macro in TeX.
>>
>> So for example in one external DTD I have some general things:
>>
>>  macro">
>>  =">
>>
>> And then in one specific document's internal entities, something which
>> uses them:
>>
>>  >
>> "-Ddefn">
>>
>> Then if I change my mind about how I want to mark up "=", for example,
>> I only have one place to change it. This makes life with XML a little
>> bit less painful.
>
>
> well, i've learned not to trust all these docs on the web too much and
> applications can do what they want (and thereby even influence standards)
>
> xml pocket reference:
>
> - parsed entity: replacement text that can be referenced
>
>   internal: literal string to be injected (then the example
> shows only text and entities
>
> in your example you use a (decimal) character entity ... the link you give
> says that you cannot use & and % as part of the entities value so that would
> mean your example is wrong
>

Indeed I did not mean that somebody's presentation slides are normative.

This is normative for XML 1.0:
https://www.w3.org/TR/1998/REC-xml-19980210#wf-entities

Which has the following productions:

extParsedEnt ::= TextDecl? content
content ::= (element | CharData | Reference | CDSect | PI | Comment)*

So you can see that both elements (by "element") and entity references
(by "Reference") are permitted in the grammar. The latter includes:

Reference ::= EntityRef | CharRef
EntityRef::='&' Name ';'

Per this, all my examples are correct.

O'Reilly XML in a Nutshell has an example:
http://docstore.mik.ua/orelly/xml/xmlnut/ch03_04.htm


> of course we can consider an option to parse the entity as xml
>
> (we can consider < as a trigger for parsing thereby kin dof automatically
> adapting)
>

I do not think this is a good idea - per the XML spec, these entities
should always be taken as well-formed fragments of XML. So treating
them otherwise would be incorrect.

Thanks,

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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Kate F]

On 19 January 2016 at 02:16, Kate F  wrote:
> On 18 January 2016 at 21:16, Hans Hagen  wrote:
>> On 1/18/2016 9:49 PM, Kate F wrote:
>>>
>>> On 18 January 2016 at 19:13, Hans Hagen  wrote:

 On 1/18/2016 5:22 PM, Kate F wrote:
>
>
> On 18 January 2016 at 13:30, Thomas A. Schmitz
>  wrote:
>>
>>
>> On 01/17/2016 07:24 PM, Hans Hagen wrote:
>>>
>>>
>>>
>>> it should work in the in beta now
>>
>>
>>
>>
>> Hi Hans,
>>
>> now I have a problem :-) What should take precedence if an entity is
>> both
>> defined in the dtd and as a \xmltexentity? The way I see it, the
>> latter:
>> e.g., in the DTD, I might declare something for use in a browser but
>> require
>> a different solution when typesetting with ConTeXt. The latest and
>> greatest
>> now takes my DTD definitions instead of the \xmltexentities, which did
>> not
>> happen before. Is that an unwanted side effect or the new default?
>>
>
> Ah, there's a bug:
>
>   -i">
>
> This should produce an  node in the DOM tree, just as if you'd
> typed that out where the entity is used. Currently ConTeXt takes that
> as literal text, as if you'd typed "option-ioption/"
>
> Often I wish XML weren't so complex...



 are you sure? i've never seen that

 Hans
>>>
>>>
>>> Yep!
>>>
>>> These are called "internal parsed entities". "Parsed" requires that
>>> any tags *inside* the entity must be balanced, unlike in SGML
>>> entities.
>>>
>>> Sorry I can't find a clear explanation in the XML spec; it's a pretty
>>> confusing document.
>>> But here's some random person's slide illustrating an example:
>>> http://images.slideplayer.com/23/6622270/slides/slide_47.jpg
>>>
>>> libxml2 deals with these correctly, which is what I've been using
>>> (xsltproc and friends) for my documents which use them. I generally
>>> trust libxml2 to get things right.
>>>
>>> I use these entities to centralise often-repeated fragments between
>>> documents, kind of like how you might use a primitive macro in TeX.
>>>
>>> So for example in one external DTD I have some general things:
>>>
>>>  macro">
>>>  =">
>>>
>>> And then in one specific document's internal entities, something which
>>> uses them:
>>>
>>>  >>
>>> "-Ddefn">
>>>
>>> Then if I change my mind about how I want to mark up "=", for example,
>>> I only have one place to change it. This makes life with XML a little
>>> bit less painful.
>>
>>
>> well, i've learned not to trust all these docs on the web too much and
>> applications can do what they want (and thereby even influence standards)
>>
>> xml pocket reference:
>>
>> - parsed entity: replacement text that can be referenced
>>
>>   internal: literal string to be injected (then the example
>> shows only text and entities
>>
>> in your example you use a (decimal) character entity ... the link you give
>> says that you cannot use & and % as part of the entities value so that would
>> mean your example is wrong
>>
>
> Indeed I did not mean that somebody's presentation slides are normative.
>
> This is normative for XML 1.0:
> https://www.w3.org/TR/1998/REC-xml-19980210#wf-entities
>
> Which has the following productions:
>
> extParsedEnt ::= TextDecl? content
> content ::= (element | CharData | Reference | CDSect | PI | Comment)*
>
> So you can see that both elements (by "element") and entity references
> (by "Reference") are permitted in the grammar. The latter includes:
>
> Reference ::= EntityRef | CharRef
> EntityRef::='&' Name ';'

Sorry, I pointed to an outdated version of the XML 1.0 spec there.

The current version (fifth revision) has the grammar written slightly
differently, but still permits both well-formed ... tags
and  entities inside entity declarations:

https://www.w3.org/TR/xml/#sec-entity-decl

[70]EntityDecl  ::= GEDecl | PEDecl
[72]PEDecl  ::= ''
[74]PEDef   ::= EntityValue | ExternalID
[9] EntityValue ::= '"' ([^%&"] | PEReference | Reference)* '"'
 |  "'" ([^%&'] | PEReference | Reference)* "'"
[67]Reference   ::= EntityRef | CharRef
[68]EntityRef   ::= '&' Name ';'

Thus  is permitted by productions applying ultimately to
EntityRef, and ... is permitted by productions applying
through the * closure of EntityValue's [^%&"] text (where [^...] means
"not").


> Per this, all my examples are correct.
>
> O'Reilly XML in a Nutshell has an example:
> http://docstore.mik.ua/orelly/xml/xmlnut/ch03_04.htm
>
>
>> of course we can consider an option to parse the entity as xml
>>
>> (we can consider < as a trigger for parsing thereby kin dof automatically
>> adapting)
>>
>
> I do not think this is a good idea - per the XML spec, these entities
> should always be taken as well-formed fragments 

Re: [NTG-context] Page Numbers change after 9 to 01 - 11 -21 - 31 and so on.

[Ibn Saeed]

Mohammad Hossein Bateni  gmail.com> writes:

> 
> 
> One hacky way to fix it is the following:
> 
> \setupheadertexts        [{\getmarking[chapter]}]    
[{\lefttoright\pagenumber}]        [{\lefttoright\pagenumber}]        
[{\getmarking[chapter]}]
> 
> 
> Ideally \setupdirections[bidi] or something like that should be used, as I 
mentioned in the other thread; that'll fix a bunch of other problems, as 
well

I did enable \setupdirections[bidi=global] and it did not help.

Here is how it was solved. I could not use your solution as it would move 
the position of the page number of the even page on top of the chapter name.

So here is the solution derived from your answer, which works for my 
scenario.

\setupheader[margin][
style=\righttoleft, 
state=normal
] 

\setupheadertexts
[{\righttoleft\getmarking[chapter]}][{\pagenumber}]
[{\pagenumber}][{\righttoleft\getmarking[chapter]}]

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

[NTG-context] (mashriqi) Arabic-Hindi Numerals

[Ibn Saeed]

Hello

I am trying to get mashriqi arabic numerals. 

i tried

\setupuserpagenumber[numberconversion=arabicnumerals]

but it does not make any change.

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

Re: [NTG-context] Ligatures in EB Garamond

[Jan U. Hasecke]

Hi Georg,

thank you very much for this insight. I really like the EB Garamond.
It's a wonderful typeface for reading. I used it to typeset books with
more than 500 pages together with lualatex and the selnolig package
which produced good results with no effort.

I was disappointed to learn that there is no package like selnolig for
ConTeXt but the book I am now typesetting is only 120 pages long and
I'll switch ligatures off manually with the ZWNJ replacement. (The
ConTeXt notation is a bit uncomfortable, but as I only have to use it
once...)

I only found one issue with ZWNJ. It splits up the words so that they
are not found by the search.

If ZWNJ is the right way to do it, I'll start a tiny project on Github
with a replacement file.

First time I hear about the new keyboard layout. I think I want my T2
keyboard now! ;-)

juh

Am 18.01.2016 um 23:38 schrieb Georg Duffner:
> Hi Jan, hi Hans,
> 
> This is the developer of EB Garamond. I’m only now and then reading this
> list so I only learnt about your troubles now.
> 
> The way the ligatures are composed simplifies the creation of more
> ligatures after the same scheme while not blowing up the font by having
> to create one glyph per ligature combination but only one per component.
> In fact, it’s not just kerning, like Hans said, but one-by-one glyph
> substitutions. It might be seen as inconsistency that one feature can be
> executed in different ways. I know of that problem but it’s not that
> inconsistent at user level if you use the methods intended by unicode
> and opentype to deal with breaking up ligatures. The symbol ZWNJ (zero
> width non joiner) is exactly meant to do this so if you insert it, you
> should get what you want. What’s more, by inserting ZWNJ you should also
> be able to benefit from kerning between the non ligated f and the
> following letter or from contextual alternate forms that fit better than
> the long bowed f, if you want that. With EB Garamond, this should be
> true for both, engines that handle ZWNJ correctly or not.
> 
> By the way, the newly standardized German keyboard layout even has the
> ZWNJ on it and the norm recommends its use to prevent ligation.
> 
> Best regards
> Georg Duffner
> 
> Am 18.01.2016 um 11:09 schrieb Hans Hagen:
>   > On 1/18/2016 10:16 AM, Jan U. Hasecke wrote:
>>> Am 17.01.2016 um 20:05 schrieb Hans Hagen:
 On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:
> Am 16.01.2016 um 13:31 schrieb Schmitz Thomas A.:
>>
>> Please provide a minimal example of your problem. It’s impossible to
>> help when we have no clue what you’re doing.
>
> Sorry, of course.
>
> After setting up a mwe I found that it is a font related issue.
>
> When I don't specify a font, it works. --> example.tex
>
> When I choose EB Garamond, it does not work. -- example-Garamond.tex
>
> I confirmed this behaviour in my real setup.

 don't assume that ligatures are always real ligatures ... in that font
 it's just kerning .. this kind of works okay:

 \replaceword[sellig][auflösen][auf{-}{}{\zwnj}lösen]
>>>
>>> I am confused as the specimen of EB Garamond mentions (real) ligatures.
>>> They are listed as glyphs.
>>>
>>> https://github.com/georgd/EB-Garamond/blob/master/specimen/Specimen.pdf
>>
>> maybe the archaic st ligature is a precomposed but f f l i aren't done
>> that way but by either kerning or replacement of individual glyphs +
>> kerning (there are many methods for this) ... also, 'liga' might mean
>> ligature but in practice is used for all kind of things ... in opentype
>> 'ligature substitution' is just a many-to-one replacement but that
>> doesn't mean that 'liga' uses that ... welcome to the inconsistent open
>> type mess
>>
> 
> Mh, yes. :-(
> 
> Two additional questions. Shall I file a bugreport for this issue? What
> would be the right words: please provide real ligature glyphs instead of
> composed ones?
> 
> EB Garamond is a free font also in the sense free of charge. But what
> can I expect when I buy a commercial font? I would be quite annoyed when
> I buy a font which does not provide the features in a way that I can use
> them in ConTeXt.
> 
> Is there a font quality page on the Wiki with a feature comparison?
> 
> juh
> 
> 
> 

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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Kate F]

On 18 January 2016 at 20:07, Hans Hagen  wrote:
> On 1/18/2016 2:30 PM, Thomas A. Schmitz wrote:
>>
>> On 01/17/2016 07:24 PM, Hans Hagen wrote:
>>>
>>> it should work in the in beta now
>>
>>
>> Hi Hans,
>>
>> now I have a problem :-) What should take precedence if an entity is
>
>
> so you have an example ?
>
>> both defined in the dtd and as a \xmltexentity? The way I see it, the
>> latter: e.g., in the DTD, I might declare something for use in a browser
>> but require a different solution when typesetting with ConTeXt. The
>> latest and greatest now takes my DTD definitions instead of the
>> \xmltexentities, which did not happen before. Is that an unwanted side
>> effect or the new default?
>
>
> we probably have to make it configureable

I don't think it's necessary to have the precedence configurable - I
think it would make sense to have \xmltexentity always take
precedence.

The usual case would be that there are no user-specified \xmltexentity
definitions present at all, and the document's DTD entities would be
used (by the feature you just added).

So if somebody does have their own \xmltexentity specified, it's
because they want that to be used instead. That would allow a user to
do something specific for ConTeXt processing, but I don't have a good
example for that. Personally I hope I can delete all my \xmltexentity
calls now.

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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Thomas A. Schmitz]

On 01/18/2016 10:26 PM, Hans Hagen wrote:

i already feared that ...


...


i still wonder what happens in tuc files (roundtrip mess)

beta coming



Yep, this seems to be a somewhat difficult area. Was just preparing an 
example when yours arrived. The latest beta seems to be doing the right 
thing. FYI: my example was an entity "linebreak" which I wanted to 
induce a linebreak (duh!) in the pdf but not when I serve the file via 
xsl...


Thanks for looking into it!

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

Re: [NTG-context] Accessibility and Tagged PDF/A, Footnotes showing

[Hans Hagen]

On 1/18/2016 8:26 PM, Ursula Hermann wrote:

Hello Hans and Dr. Dominik Klein!

Today I found a Thread about Accessibility from last Juli!


I work at the University in Vienna,  and I work with students, who are
blind or have a see handicap. So I read this Thread today.

Last year in Summer I began to read the manual of Context.

I have a question to this discussion, it is nessesary to know: How can
footnotes be shown in the PDF/A tagged PDF, in a text?

What I mean something, that shows in the Text the text from the footnote,
when I click on the number from the footnote.


Maybe with a tooltip? Or what is the right way? Which command?


tooltips are widgets and not part of the document text stream .. so i 
think they don't count as accessibility feature (but i might be wrong)


maybe someone else on the list knows

i wonder, as you use tex you can consider generating an additional 
document (larger fontsize, better readable fonts, inline notes, maybe 
other enhancements), pop ups etc


it'a anyway interesting to discuss how to make documents accessible 
(tagged pdf is one options but not beforehand the nicest approach)


Hans




-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

Re: [NTG-context] Greek diacriticals (combining perispomenon displaced)

[Thomas A. Schmitz]

On 01/18/2016 10:33 PM, Hans Hagen wrote:

As I review my files, I see that this is a fairly recent problem, though
I cannot say exactly when it first occurred.


looks ok here ... assuming i have the right font

you can try to wipe the font cache (otf and otl)



I can't test with HellenicaCU as I don't have the font, but I can 
confirm that output is good here with the IFAOGrec font, the combining 
circumflex is where it belongs. (most recent beta)


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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Hans Hagen]

On 1/18/2016 9:49 PM, Kate F wrote:

On 18 January 2016 at 19:13, Hans Hagen  wrote:

On 1/18/2016 5:22 PM, Kate F wrote:


On 18 January 2016 at 13:30, Thomas A. Schmitz
 wrote:


On 01/17/2016 07:24 PM, Hans Hagen wrote:



it should work in the in beta now




Hi Hans,

now I have a problem :-) What should take precedence if an entity is both
defined in the dtd and as a \xmltexentity? The way I see it, the latter:
e.g., in the DTD, I might declare something for use in a browser but
require
a different solution when typesetting with ConTeXt. The latest and
greatest
now takes my DTD definitions instead of the \xmltexentities, which did
not
happen before. Is that an unwanted side effect or the new default?



Ah, there's a bug:

  -i">

This should produce an  node in the DOM tree, just as if you'd
typed that out where the entity is used. Currently ConTeXt takes that
as literal text, as if you'd typed "option-ioption/"

Often I wish XML weren't so complex...



are you sure? i've never seen that

Hans


Yep!

These are called "internal parsed entities". "Parsed" requires that
any tags *inside* the entity must be balanced, unlike in SGML
entities.

Sorry I can't find a clear explanation in the XML spec; it's a pretty
confusing document.
But here's some random person's slide illustrating an example:
http://images.slideplayer.com/23/6622270/slides/slide_47.jpg

libxml2 deals with these correctly, which is what I've been using
(xsltproc and friends) for my documents which use them. I generally
trust libxml2 to get things right.

I use these entities to centralise often-repeated fragments between
documents, kind of like how you might use a primitive macro in TeX.

So for example in one external DTD I have some general things:

 macro">
 =">

And then in one specific document's internal entities, something which
uses them:

 -Ddefn">

Then if I change my mind about how I want to mark up "=", for example,
I only have one place to change it. This makes life with XML a little
bit less painful.


well, i've learned not to trust all these docs on the web too much and 
applications can do what they want (and thereby even influence standards)


xml pocket reference:

- parsed entity: replacement text that can be referenced

  internal: literal string to be injected (then the example
shows only text and entities

in your example you use a (decimal) character entity ... the link you 
give says that you cannot use & and % as part of the entities value so 
that would mean your example is wrong


of course we can consider an option to parse the entity as xml

(we can consider < as a trigger for parsing thereby kin dof 
automatically adapting)



Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

Re: [NTG-context] Page Numbers change after 9 to 01 - 11 -21 - 31 and so on.

[Hans Hagen]

On 1/18/2016 7:14 PM, Ibn Saeed wrote:

It seems to be the issue with

 \setupheader[style=\righttoleft, state=normal]

The style is righttoleft to accomodate the proper direction for arabic text.
But it messes up the page number direction.


you can try leftstyle instead (there's also rightstyle)


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Hans Hagen]

On 1/18/2016 2:30 PM, Thomas A. Schmitz wrote:

On 01/17/2016 07:24 PM, Hans Hagen wrote:

it should work in the in beta now


Hi Hans,

now I have a problem :-) What should take precedence if an entity is


so you have an example ?


both defined in the dtd and as a \xmltexentity? The way I see it, the
latter: e.g., in the DTD, I might declare something for use in a browser
but require a different solution when typesetting with ConTeXt. The
latest and greatest now takes my DTD definitions instead of the
\xmltexentities, which did not happen before. Is that an unwanted side
effect or the new default?


we probably have to make it configureable

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

[NTG-context] Greek diacriticals (combining perispomenon displaced)

[Alan Bowen]

​There is an oddity in processing Greek. The combining diacritical
perispomenon is not positioned properly, though it appears as it should in
the source file. This diacritical is placed properly if one inserts the
appropriate character directly.

The PDF file produced by this sample shows the problem as it appears using
two different Greek fonts. The first entries in each line are incorrect.

\definefontfamily[mainface][serif][IFAO Grec Unicode]
\setupbodyfont[mainface, 24pt]

\definefont[HellenicaCU][file:HellenicaCU.ttf at 24pt]

\starttext
αῖ %combining diacritical
αῖ %char 1FD6

\HellenicaCU{
αῖ %combining diacritical
αῖ %char 1FD6
}
\stoptext

As I review my files, I see that this is a fairly recent problem, though I
cannot say exactly when it first occurred.

The other combining diacriticals process as they should.

Alan


test.pdf
Description: Adobe PDF document
___
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
___

Re: [NTG-context] Greek diacriticals (combining perispomenon displaced)

[Hans Hagen]

On 1/18/2016 9:30 PM, Alan Bowen wrote:

​There is an oddity in processing Greek. The combining diacritical
perispomenon is not positioned properly, though it appears as it should
in the source file. This diacritical is placed properly if one inserts
the appropriate character directly.

The PDF file produced by this sample shows the problem as it appears
using two different Greek fonts. The first entries in each line are
incorrect.

\definefontfamily[mainface][serif][IFAO Grec Unicode]
\setupbodyfont[mainface, 24pt]

\definefont[HellenicaCU][file:HellenicaCU.ttf at 24pt]

\starttext
αῖ%combining diacritical
αῖ%char 1FD6

\HellenicaCU{
αῖ%combining diacritical
αῖ%char 1FD6
}
\stoptext

As I review my files, I see that this is a fairly recent problem, though
I cannot say exactly when it first occurred.


looks ok here ... assuming i have the right font

you can try to wipe the font cache (otf and otl)


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Hans Hagen]

On 1/18/2016 2:30 PM, Thomas A. Schmitz wrote:

On 01/17/2016 07:24 PM, Hans Hagen wrote:

it should work in the in beta now


Hi Hans,

now I have a problem :-) What should take precedence if an entity is
both defined in the dtd and as a \xmltexentity? The way I see it, the
latter: e.g., in the DTD, I might declare something for use in a browser
but require a different solution when typesetting with ConTeXt. The
latest and greatest now takes my DTD definitions instead of the
\xmltexentities, which did not happen before. Is that an unwanted side
effect or the new default?


i already feared that ...

% \disabledirectives[lxml.entities.escaped]
% \disabledirectives[lxml.entities.prefertex]

\setupbodyfont[dejavu]

\xmltexentity{oeps}{\textdegree}

\startbuffer[test]


 
]>

Random text with an entity:  test  test

Random text with an entity:  test

\stopbuffer

\startxmlsetups xml:testsetups
\xmlsetsetup{#1}{text}{xml:*}
\stopxmlsetups

\xmlregistersetup{xml:testsetups}

\startxmlsetups xml:text
\xmlflush{#1}\par
\stopxmlsetups

\starttext
\xmlprocessbuffer{main}{test}{}
\stoptext

i still wonder what happens in tuc files (roundtrip mess)

beta coming

Hans



-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

Re: [NTG-context] Accessibility and Tagged PDF/A, Footnotes showing

[Alan BRASLAU]

On Mon, 18 Jan 2016 22:38:56 +0100
Hans Hagen  wrote:

> On 1/18/2016 8:26 PM, Ursula Hermann wrote:
> > Hello Hans and Dr. Dominik Klein!
> >
> > Today I found a Thread about Accessibility from last Juli!
> >
> >
> > I work at the University in Vienna,  and I work with students, who
> > are blind or have a see handicap. So I read this Thread today.
> >
> > Last year in Summer I began to read the manual of Context.
> >
> > I have a question to this discussion, it is nessesary to know: How
> > can footnotes be shown in the PDF/A tagged PDF, in a text?
> >
> > What I mean something, that shows in the Text the text from the
> > footnote, when I click on the number from the footnote.
> >
> >
> > Maybe with a tooltip? Or what is the right way? Which command?  
> 
> tooltips are widgets and not part of the document text stream .. so i 
> think they don't count as accessibility feature (but i might be wrong)
> 
> maybe someone else on the list knows
> 
> i wonder, as you use tex you can consider generating an additional 
> document (larger fontsize, better readable fonts, inline notes, maybe 
> other enhancements), pop ups etc
> 
> it'a anyway interesting to discuss how to make documents accessible 
> (tagged pdf is one options but not beforehand the nicest approach)

Hello,

It is an interesting comment going beyond the simple (yet important)
question of accessibility: how in general should items such as
footnotes be handled in alternative, non-printed formats, where the
notion of a "page" becomes fuzzy?

With ConTeXt, it is easy to have such "footnotes" placed at the bottom
of the formatted page, at the end of a section, chapter or book. It is
also easy for them to have hyperlinks to jump to their location and
then back to the reference text.

Tooltips and other widgets, as Hans says, depend on the display client
and not on the document - there are many things that might work with
one reader (i.e. Adobe) and not on others. Addressing the questions of
accessibility, in particular for blind or otherwise vision-impaired
readers, one can design an appropriate action or model for the
document. Footnotes and endnotes are useful tools for a writer. Like
indexes, bibliographic references, or floating figures or tables, these
are concepts that might require some thought as to how they might be
employed in an ebook or by an audio reader. This would make an
interesting topic of discussion for our next ConTeXt users' meeting.

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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Kate F]

On 18 January 2016 at 19:13, Hans Hagen  wrote:
> On 1/18/2016 5:22 PM, Kate F wrote:
>>
>> On 18 January 2016 at 13:30, Thomas A. Schmitz
>>  wrote:
>>>
>>> On 01/17/2016 07:24 PM, Hans Hagen wrote:


 it should work in the in beta now
>>>
>>>
>>>
>>> Hi Hans,
>>>
>>> now I have a problem :-) What should take precedence if an entity is both
>>> defined in the dtd and as a \xmltexentity? The way I see it, the latter:
>>> e.g., in the DTD, I might declare something for use in a browser but
>>> require
>>> a different solution when typesetting with ConTeXt. The latest and
>>> greatest
>>> now takes my DTD definitions instead of the \xmltexentities, which did
>>> not
>>> happen before. Is that an unwanted side effect or the new default?
>>>
>>
>> Ah, there's a bug:
>>
>>  -i">
>>
>> This should produce an  node in the DOM tree, just as if you'd
>> typed that out where the entity is used. Currently ConTeXt takes that
>> as literal text, as if you'd typed "option-ioption/"
>>
>> Often I wish XML weren't so complex...
>
>
> are you sure? i've never seen that
>
> Hans

Yep!

These are called "internal parsed entities". "Parsed" requires that
any tags *inside* the entity must be balanced, unlike in SGML
entities.

Sorry I can't find a clear explanation in the XML spec; it's a pretty
confusing document.
But here's some random person's slide illustrating an example:
http://images.slideplayer.com/23/6622270/slides/slide_47.jpg

libxml2 deals with these correctly, which is what I've been using
(xsltproc and friends) for my documents which use them. I generally
trust libxml2 to get things right.

I use these entities to centralise often-repeated fragments between
documents, kind of like how you might use a primitive macro in TeX.

So for example in one external DTD I have some general things:

macro">
=">

And then in one specific document's internal entities, something which
uses them:

-Ddefn">

Then if I change my mind about how I want to mark up "=", for example,
I only have one place to change it. This makes life with XML a little
bit less painful.

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

Re: [NTG-context] TeX in \xmlsetentity and DTDs in DOCTYPEs

[Hans Hagen]

On 1/18/2016 9:56 PM, Kate F wrote:

On 18 January 2016 at 20:07, Hans Hagen  wrote:

On 1/18/2016 2:30 PM, Thomas A. Schmitz wrote:


On 01/17/2016 07:24 PM, Hans Hagen wrote:


it should work in the in beta now



Hi Hans,

now I have a problem :-) What should take precedence if an entity is



so you have an example ?


both defined in the dtd and as a \xmltexentity? The way I see it, the
latter: e.g., in the DTD, I might declare something for use in a browser
but require a different solution when typesetting with ConTeXt. The
latest and greatest now takes my DTD definitions instead of the
\xmltexentities, which did not happen before. Is that an unwanted side
effect or the new default?



we probably have to make it configureable


I don't think it's necessary to have the precedence configurable - I
think it would make sense to have \xmltexentity always take
precedence.


all is configureable because there's always someone who wants it different


The usual case would be that there are no user-specified \xmltexentity
definitions present at all, and the document's DTD entities would be
used (by the feature you just added).

So if somebody does have their own \xmltexentity specified, it's
because they want that to be used instead. That would allow a user to
do something specific for ConTeXt processing, but I don't have a good
example for that. Personally I hope I can delete all my \xmltexentity
calls now.


of course that assumes that you don't need to revert to tex for 
rendering them


Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | 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
___

Re: [NTG-context] Ligatures in EB Garamond

[Georg Duffner]

Hi Jan, hi Hans,

This is the developer of EB Garamond. I’m only now and then reading this
list so I only learnt about your troubles now.

The way the ligatures are composed simplifies the creation of more
ligatures after the same scheme while not blowing up the font by having
to create one glyph per ligature combination but only one per component.
In fact, it’s not just kerning, like Hans said, but one-by-one glyph
substitutions. It might be seen as inconsistency that one feature can be
executed in different ways. I know of that problem but it’s not that
inconsistent at user level if you use the methods intended by unicode
and opentype to deal with breaking up ligatures. The symbol ZWNJ (zero
width non joiner) is exactly meant to do this so if you insert it, you
should get what you want. What’s more, by inserting ZWNJ you should also
be able to benefit from kerning between the non ligated f and the
following letter or from contextual alternate forms that fit better than
the long bowed f, if you want that. With EB Garamond, this should be
true for both, engines that handle ZWNJ correctly or not.

By the way, the newly standardized German keyboard layout even has the
ZWNJ on it and the norm recommends its use to prevent ligation.

Best regards
Georg Duffner

Am 18.01.2016 um 11:09 schrieb Hans Hagen:
> On 1/18/2016 10:16 AM, Jan U. Hasecke wrote:
>> Am 17.01.2016 um 20:05 schrieb Hans Hagen:
>>> On 1/16/2016 3:58 PM, Jan U. Hasecke wrote:
 Am 16.01.2016 um 13:31 schrieb Schmitz Thomas A.:
>
> Please provide a minimal example of your problem. It’s impossible to
> help when we have no clue what you’re doing.

 Sorry, of course.

 After setting up a mwe I found that it is a font related issue.

 When I don't specify a font, it works. --> example.tex

 When I choose EB Garamond, it does not work. -- example-Garamond.tex

 I confirmed this behaviour in my real setup.
>>>
>>> don't assume that ligatures are always real ligatures ... in that font
>>> it's just kerning .. this kind of works okay:
>>>
>>> \replaceword[sellig][auflösen][auf{-}{}{\zwnj}lösen]
>>
>> I am confused as the specimen of EB Garamond mentions (real) ligatures.
>> They are listed as glyphs.
>>
>> https://github.com/georgd/EB-Garamond/blob/master/specimen/Specimen.pdf
>
> maybe the archaic st ligature is a precomposed but f f l i aren't done
> that way but by either kerning or replacement of individual glyphs +
> kerning (there are many methods for this) ... also, 'liga' might mean
> ligature but in practice is used for all kind of things ... in opentype
> 'ligature substitution' is just a many-to-one replacement but that
> doesn't mean that 'liga' uses that ... welcome to the inconsistent open
> type mess
>

Mh, yes. :-(

Two additional questions. Shall I file a bugreport for this issue? What
would be the right words: please provide real ligature glyphs instead of
composed ones?

EB Garamond is a free font also in the sense free of charge. But what
can I expect when I buy a commercial font? I would be quite annoyed when
I buy a font which does not provide the features in a way that I can use
them in ConTeXt.

Is there a font quality page on the Wiki with a feature comparison?

juh



-- 
EB Garamond: http://www.georgduffner.at/ebgaramond
___
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
___