Re: [NTG-context] Markdown module in LMTX

2021-03-28 Thread Christoph Reller
Hi all,

In recent versions of ConTeXt LMTX the markdown module seems to work again.
I just copied the files m-markdown.mkiv and m-markdown.loa from a MKVI
version into the directory tex\texmf-modules\m-markdown of the LMTX version.

I don't believe that this is officially supported and I did no extensive
testing, but for my use case it works.

Cheers,
Christoph

On Fri, Jan 29, 2021 at 4:16 PM J Huisman 
wrote:

> Hi all,
>
> I can confirm that this problem has not yet been resolved? Any idea
> when it might happen?
>
> Cheers,
>
> Jelle
>
> On Mon, Jan 11, 2021 at 5:48 AM Christoph Reller
>  wrote:
> > In recent versions of ConTeXt LMTX, the builtin markdown module is
> missing. (Files m-markdown.[lua|mkiv])
> > Just copying this module from an earlier version shows that they don't
> work anymore.
> >
> > MWE:
> >
> > ConTeXt file:
> > -- 8< --
> > \usemodule[markdown]
> > \starttext
> > \processmarkdownfile{file.md}
> > \stoptext
> > -- 8< --
> >
> > file.md:
> > -- 8< --
> > Title
> > =
> >
> > Here comes a paragraph text.
> > -- 8< --
> >
> > Are there plans to add and update this module?
>
>
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Table disappears in floatcombination

2021-03-28 Thread Christoph Reller
On Mon, Jan 4, 2021 at 7:59 PM Christoph Reller 
wrote:

> On Sat, Dec 26, 2020 at 3:01 PM Hans Hagen  wrote:
>
>> On 12/26/2020 2:56 PM, Christoph Reller wrote:
>> >
>> > On Sat, Dec 26, 2020 at 10:54 AM Hans Hagen > > <mailto:j.ha...@xs4all.nl>> wrote:
>> >
>> > On 12/25/2020 9:47 PM, Christoph Reller wrote:
>> >  > Hi,
>> >  >
>> >  > Consider the following MWE:
>> >  >
>> >  > \definefloat[combination][figure]
>> >  > \setupcaptions[
>> >  >number=no, %<- comment and table appears
>> >  >align=flushright]
>> >  > \starttext
>> >  > \startplacecombination[title=Combination]
>> >  >\startfloatcombination
>> >  >  \startplacetable%[title=Table] %<- uncomment and table
>> appears
>> >  >\bTABLE \bTR \bTD Cell \eTD \eTR \eTABLE
>> >  >  \stopplacetable
>> >  >\stopfloatcombination
>> >  > \stopplacecombination
>> >  > \stoptext
>> >  >
>> >  > In the latest LMTX version of ConTeXt, the table is not shown.
>> > (In MKIV
>> >  > it is present.) Either commenting line 3 or activating the table
>> > title
>> >  > in line 8 makes the table appear.
>> >
>> > what version of mkiv did you test?
>> >
>> >
>> > Okay, the MKIV version is a little bit dated: 2018.05.19_21.46.
>> > Still: How can I get floats without captions within a
>> > floatcombination environment?
>> I (or Wolfgang) needs to look into it, maybe something got lost.
>>
>
> I hope that you find the time to solve this issue. Disappearing tables are
> not so nice :(
> Your work is much appreciated!
>

Just a reminder that this issue still persists in the latest version of
ConTeXt LMTX. A fix would be highly appreciated.

Cheers, Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Typing within doifmode leads to error

2021-03-21 Thread Christoph Reller
On Sat, Mar 20, 2021 at 6:07 PM Hans Hagen  wrote:

> On 3/20/2021 4:00 PM, Christoph Reller wrote:
> > On Sat, Mar 20, 2021 at 12:12 PM Hans Hagen  > <mailto:j.ha...@xs4all.nl>> wrote:
> >
> > On 3/20/2021 8:24 AM, Aditya Mahajan wrote:
> >  > On Sat, 20 Mar 2021, Christoph Reller wrote:
> >  >> Of course we can do this in lua:
> >  >>
> >  >> if tex.modes["A"] and not tex.modes{"B"] then
> >  >> ...
> >  >> end
> >  >
> >  > ... which means that you can use that at the context end as well
> > (old feature).
> >  > Save the following as test.mkix (or add "% macros=mkix" as the
> > first line):
> >  >
> >  > ```
> >  > \starttext
> >  > 
> >  > \starttyping
> >  > A and not B
> >  > \stoptyping
> >  > 
> >  > \starttyping
> >  > not (A and not B)
> >  > \stoptyping
> >  > 
> >  > \stoptext
> > a neat application!
> >
> >
> > Thank you for this hint, Aditya. This would be a very nice solution
> > indeed. But it does not seem to work:
> >
> > % macros=mkix
> > \definemode[A][yes]
> > \starttext
> > \startluacode
> >if tex.modes['A'] then
> >  context("A")
> >end
> > \stopluacode
> > 
> > A
> > 
> > \stoptext
> >
> > With ConTeXt LMTX 2021.03.17 the output of the above is a single "A". I
> > would expect two. What am I doing wrong?
>
> When the file gets preprocessed the mode is not known
>
> context --mode=A foo.tex
>
> it does of course also work when you set the mode in a parent file and
> then include foo.tex


For me this is good enough, because I define modes always in top-level
files or in modules. Thank you!

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Typing within doifmode leads to error

2021-03-20 Thread Christoph Reller
On Sat, Mar 20, 2021 at 12:12 PM Hans Hagen  wrote:

> On 3/20/2021 8:24 AM, Aditya Mahajan wrote:
> > On Sat, 20 Mar 2021, Christoph Reller wrote:
> >> Of course we can do this in lua:
> >>
> >> if tex.modes["A"] and not tex.modes{"B"] then
> >> ...
> >> end
> >
> > ... which means that you can use that at the context end as well (old
> feature).
> > Save the following as test.mkix (or add "% macros=mkix" as the first
> line):
> >
> > ```
> > \starttext
> > 
> > \starttyping
> > A and not B
> > \stoptyping
> > 
> > \starttyping
> > not (A and not B)
> > \stoptyping
> > 
> > \stoptext
> a neat application!
>
>
Thank you for this hint, Aditya. This would be a very nice solution indeed.
But it does not seem to work:

% macros=mkix
\definemode[A][yes]
\starttext
\startluacode
  if tex.modes['A'] then
context("A")
  end
\stopluacode

A

\stoptext

With ConTeXt LMTX 2021.03.17 the output of the above is a single "A". I
would expect two. What am I doing wrong?

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Error "double-free glue_spec"

2021-03-20 Thread Christoph Reller
Hi,

For one of my projects ConTeXt LMTX 2021.03.17 17:46 fails with:

error (nodes): attempt to double-free glue_spec node 145, ignored
mtx-context | fatal error: return code: 1

Unfortunately, when I try to minimize the project, the error vanishes. I
guess I have to send Hans the whole project, or are there other
possibilities?

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Typing within doifmode leads to error

2021-03-19 Thread Christoph Reller
On Fri, Mar 19, 2021 at 9:49 AM Hans Hagen  wrote:

> On 3/19/2021 4:58 AM, Christoph Reller wrote:
> > Hi,
> >
> > Consider the following MWE:
> >
> > \definetyping[T]
> > \definemode[mode][yes]
> > \starttext
> > \doifmode{mode}{%
> >\startT
> >  Bla
> >\stopT}
> > \stoptext
> >
> > Compilation with the currently latest ConTeXt LMTX (ver: 2021.03.17
> > 17:46 LMTX  fmt: 2021.3.18) fails with:
> >
> > tex error   > runaway error: end of file encountered
> > mtx-context | fatal error: return code: 1
> >
> > Compilation is successful if I replace doifmode{mode}{...} by
> > \startmode[mode]...\stopmode.
> >
> > Is there anything I'm missing? (This could be a bug.)
> not a bug, just the way tex works .. modes cannot know that what goes
> into an argument is something verbose
>
> but you can use this (also more efficient here):
>
> \definetyping[T]
> \definemode[mode][yes]
> \starttext
> \startmode[mode]
> \startT
>  Bla
> \stopT
> \stopmode
> \stoptext
>
> % there's also \startnotmode
>
>
Thank you for hinting at the environment form. The problem with this is,
that it cannot be nested, and that there is no "else" form.
E.g:

\startmode[A]
... mode A
\startmode[B]
... mode A and mode B
\elsemode
... mode A and not mode B
\stopmode
\stopmode

I know that there is \start(not)mode and \start(not)allmodes, but there
seems to be no way to use a general boolean expression such as:

\startmodes[A and not B]
...
\stopmodes

Of course we can do this in lua:

if tex.modes["A"] and not tex.modes{"B"] then
...
end

Keep up your excellent work! Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Typing within doifmode leads to error

2021-03-19 Thread Christoph Reller
On Fri, Mar 19, 2021 at 5:38 AM Aditya Mahajan  wrote:

> On Fri, 19 Mar 2021, Christoph Reller wrote:
>
> > Consider the following MWE:
> >
> > \definetyping[T]
> > \definemode[mode][yes]
> > \starttext
> > \doifmode{mode}{%
> >   \startT
> > Bla
> >   \stopT}
> > \stoptext
> >
> > Compilation with the currently latest ConTeXt LMTX (ver: 2021.03.17 17:46
> > LMTX  fmt: 2021.3.18) fails with:
> >
> > tex error   > runaway error: end of file encountered
> > mtx-context | fatal error: return code: 1
> >
> > Compilation is successful if I replace doifmode{mode}{...} by
> > \startmode[mode]...\stopmode.
>
> Has to be with how tex works. The argument of any macro
> (\doifmode{mode}{...} in this case) is scanned under the current catcode
> regime. So, any environment (like typing) which changes catcodes does work
> inside the argument to another macro.
>

I see. Strangely, the MWE did work in older versions of ConTeXt ;-)


> So, either use the environment version of \doifmode (which doesn't
> _capture_ it content):
>
> \definetyping[T]
> \definemode[mode][yes]
> \starttext
> \startmode[mode]
>   \startT
> Bla
>   \stopT
> \stopmode
> \stoptext
>
> Or use buffers (to avoid catcode all together):
>
> \definetyping[T]
> \definemode[mode][yes]
> \starttext
> \startbuffer[code]
> \startT
> Bla
> \stopT
> \stopbuffer
>
> \doifmode{mode}{\getbuffer[code]}
> \stoptext
>
> or (note type**T**buffer so that the output is formatting according to the
> options of \definetyping[T])
>
> \definetyping[T]
> \definemode[mode][yes]
> \starttext
> \startbuffer[code]
> Bla
> \stopbuffer
>
> \doifmode{mode}{\typeTbuffer[code]}
> \stoptext
>
> Perhaps this should be added to the FAQ on the wiki.
>
> Aditya
>

 Thank you for your ultra-speedy and very helpful response!

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Typing within doifmode leads to error

2021-03-18 Thread Christoph Reller
Hi,

Consider the following MWE:

\definetyping[T]
\definemode[mode][yes]
\starttext
\doifmode{mode}{%
  \startT
Bla
  \stopT}
\stoptext

Compilation with the currently latest ConTeXt LMTX (ver: 2021.03.17 17:46
LMTX  fmt: 2021.3.18) fails with:

tex error   > runaway error: end of file encountered
mtx-context | fatal error: return code: 1

Compilation is successful if I replace doifmode{mode}{...} by
\startmode[mode]...\stopmode.

Is there anything I'm missing? (This could be a bug.)

Cheers,

Christoph Reller
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Markdown module in LMTX

2021-01-10 Thread Christoph Reller
Hi,

In recent versions of ConTeXt LMTX, the builtin markdown module is missing.
(Files m-markdown.[lua|mkiv])
Just copying this module from an earlier version shows that they don't work
anymore.

MWE:

ConTeXt file:
-- 8< --
\usemodule[markdown]
\starttext
\processmarkdownfile{file.md}
\stoptext
-- 8< --

file.md:
-- 8< --
Title
=

Here comes a paragraph text.
-- 8< --

Are there plans to add and update this module?

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] mathmatrix and tagging

2021-01-04 Thread Christoph Reller
On Sun, Dec 20, 2020 at 11:14 AM Christoph Reller <
christoph.rel...@gmail.com> wrote:

> Unfortunately, the following MNWE results in an error when compiled with
> the latest version of ConTeXt LMTX:
>
> \setuptagging[state=start]
> \definemathmatrix[mymatrix][left={\left(},right={\right)}]
> \starttext
> \startformula
>   \startmymatrix
> \NC A \NC B \NR
>   \stopmymatrix
> \stopformula
> \stoptext
>
> Omitting "\setuptagging[state=start]" removes the error.
> A fix would be highly appreciated!
>

Thank you, Hans, for having fixed this issue!
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Table disappears in floatcombination

2020-12-26 Thread Christoph Reller
On Sat, Dec 26, 2020 at 10:54 AM Hans Hagen  wrote:

> On 12/25/2020 9:47 PM, Christoph Reller wrote:
> > Hi,
> >
> > Consider the following MWE:
> >
> > \definefloat[combination][figure]
> > \setupcaptions[
> >number=no, %<- comment and table appears
> >align=flushright]
> > \starttext
> > \startplacecombination[title=Combination]
> >\startfloatcombination
> >  \startplacetable%[title=Table] %<- uncomment and table appears
> >\bTABLE \bTR \bTD Cell \eTD \eTR \eTABLE
> >  \stopplacetable
> >\stopfloatcombination
> > \stopplacecombination
> > \stoptext
> >
> > In the latest LMTX version of ConTeXt, the table is not shown. (In MKIV
> > it is present.) Either commenting line 3 or activating the table title
> > in line 8 makes the table appear.
>
> what version of mkiv did you test?
>

Okay, the MKIV version is a little bit dated: 2018.05.19_21.46.
Still: How can I get floats without captions within a
floatcombination environment?
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Table disappears in floatcombination

2020-12-25 Thread Christoph Reller
Hi,

Consider the following MWE:

\definefloat[combination][figure]
\setupcaptions[
  number=no, %<- comment and table appears
  align=flushright]
\starttext
\startplacecombination[title=Combination]
  \startfloatcombination
\startplacetable%[title=Table] %<- uncomment and table appears
  \bTABLE \bTR \bTD Cell \eTD \eTR \eTABLE
\stopplacetable
  \stopfloatcombination
\stopplacecombination
\stoptext

In the latest LMTX version of ConTeXt, the table is not shown. (In MKIV it
is present.) Either commenting line 3 or activating the table title in line
8 makes the table appear.

Also, once the captions appear, they don't align on the right side. When
changing the caption alignment to "align=flushleft", they align perfectly
on the left side.

Am I doing something wrong?

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Alternative for selector in LMTX for different heading and reference texts for descriptions

2020-12-25 Thread Christoph Reller
On Tue, Dec 22, 2020 at 5:25 AM Christoph Reller 
wrote:

> On Sat, Dec 19, 2020 at 10:43 PM Christoph Reller <
> christoph.rel...@gmail.com> wrote:
>
>> Hans Hagen  schrieb am Sa., 19. Dez. 2020, 19:16:
>>
>>> Actually, what you want is:
>>>
>>> \definedescription[desc]
>>> \starttext
>>>  \startdesc[title={Long title},reference=foo,referencetext={Short
>>> Title}]
>>>  \input jojomayer
>>>  \stopdesc
>>>  \about[foo]
>>> \stoptext
>>>
>>> So I'll add that (after all, occasionally we need to add some
>>> functionality in order to indicate progress.)
>>
>>
>> Great! That would be a good solution for me.
>> Thanks,
>> Christoph
>>
>
> Thank you for the implementation, Hans!
>
>  A small issue: When omitting the referencetext, then the shown text is
> now something like "248>desc:referencetext".
>

Thank you for the fast fix of this issue!
Cheers, Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Alternative for selector in LMTX for different heading and reference texts for descriptions

2020-12-21 Thread Christoph Reller
On Sat, Dec 19, 2020 at 10:43 PM Christoph Reller <
christoph.rel...@gmail.com> wrote:

> Hans Hagen  schrieb am Sa., 19. Dez. 2020, 19:16:
>
>> Actually, what you want is:
>>
>> \definedescription[desc]
>> \starttext
>>  \startdesc[title={Long title},reference=foo,referencetext={Short
>> Title}]
>>  \input jojomayer
>>  \stopdesc
>>  \about[foo]
>> \stoptext
>>
>> So I'll add that (after all, occasionally we need to add some
>> functionality in order to indicate progress.)
>
>
> Great! That would be a good solution for me.
> Thanks,
> Christoph
>

Thank you for the implementation, Hans!

 A small issue: When omitting the referencetext, then the shown text is now
something like "248>desc:referencetext".

MWE:
\definedescription[desc]
\starttext
\startdesc[title=Long title, reference=foo]%, referencetext=Short title]
  \input jojomayer
\stopdesc
\about[foo]
\stoptext

For backward compatibility, it might be better to use the title as a
default for the reference test.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] \dodoubleemptywithset not working in LMTX

2020-12-20 Thread Christoph Reller
On Sun, Dec 20, 2020 at 4:32 PM Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:

> Christoph Reller schrieb am 20.12.2020 um 16:15:
> > Hi,
> >
> > The following MNWE uses \dodoubleemptywithset. In ConTeXt MKIV it
> > works as expected, In ConTeXt LMTX an error results.
>
> It's a bug, the wrong argument is passed as comma list.
>
> \permanent\tolerant\protected\def\dodoubleemptywithset#1#*[#2]#*[#3]%
>{\doifsomething{#2}%
>   {\def\syst_helpers_with_set_step##1{#1[##1][#3]}%
> - \processcommalist[#1]\syst_helpers_with_set_step}}
> + \processcommalist[#2]\syst_helpers_with_set_step}}
>
> \permanent\tolerant\protected\def\dotripleemptywithset#1#*[#2]#*[#3]#*[#4]%
>{\doifsomething{#2}%
>   {\def\syst_helpers_with_set_step##1{#1[##1][#3][#4]}%
> - \processcommalist[#1]\syst_helpers_with_set_step}}
> + \processcommalist[#2]\syst_helpers_with_set_step}}
>
> Wolfgang


Thank you Wolfgang for the fast response! (And sorry for having provided a
faulty MWE.)

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] \dodoubleemptywithset not working in LMTX

2020-12-20 Thread Christoph Reller
Hi,

The following MNWE uses \dodoubleemptywithset. In ConTeXt MKIV it works as
expected,  In ConTeXt LMTX an error results.

\starttext
\unexpanded\def\doMyDefs[#1][#2]{\getparameters[MD#1][#2]}
\def\MyDefs{\dodoubleemptywithset\doMyDefs}
\MyDefs[A,B][key=val,k=v]
\MyDefs[C]
\typeTEX{\MDAkey} is \MDAkey. \typeTEX{\MDBkey} is \MDBkey.
\typeTEX{\MDAk} is \MDAk. \typeTEX{\MDBk} is \MDBk.
\stoptext

Possibly, \dodoubleemptywithset is not used anymore in LMTX, in which case
it should be removed. Otherwise this could be a bug. Or maybe I use it
wrongly?

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] mathmatrix and tagging

2020-12-20 Thread Christoph Reller
Hi,

Unfortunately, the following MNWE results in an error when compiled with
the latest version of ConTeXt LMTX:

\setuptagging[state=start]
\definemathmatrix[mymatrix][left={\left(},right={\right)}]
\starttext
\startformula
  \startmymatrix
\NC A \NC B \NR
  \stopmymatrix
\stopformula
\stoptext

Omitting "\setuptagging[state=start]" removes the error.
A fix would be highly appreciated!

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Alternative for selector in LMTX for different heading and reference texts for descriptions

2020-12-19 Thread Christoph Reller
Hans Hagen  schrieb am Sa., 19. Dez. 2020, 19:16:

> Actually, what you want is:
>
> \definedescription
>[desc]
>
> \starttext
>
>  \startdesc[title={Long title},reference=foo,referencetext={Short
> Title}]
>  \input jojomayer
>  \stopdesc
>
>  \about[foo]
>
> \stoptext
>
> So I'll add that (after all, occasionally we need to add some
> functionality in order to indicate progress.)


Great! That would be a good solution for me.
Thanks,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Alternative for selector in LMTX for different heading and reference texts for descriptions

2020-12-19 Thread Christoph Reller
Hi,

In ConTeXt MKIV, there are selectors (\defineselector, \select). In ConTeXt
LMTX, they are gone.

In LMTX, how can I achieve the following without using selectors:
(Different heading and reference texts for descriptions)

\defineselector[sel][max=2, n=2]
\definedescription[desc][headcommand={\setupselector[sel][n=1]}]
\starttext
\startdesc[title={\select{sel}{Long title}{Short}}, reference=desc]
  \input jojomayer
\stopdesc
\about[desc]
\stoptext

Any help is welcome!
Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Combinations not working as expected

2020-12-01 Thread Christoph Reller
Dear list,

In the latest version 2020.11.28 13:18 of ConTeXt LMTX, combinations don't
seem to work as expected. Example:

\starttext
\startcombination[2*1]
  {first}{a}
  {second}{b}
\stopcombination
\blank[big]
\startcombination[1*2]
  {first}{a}
  {second}{b}
\stopcombination
\stoptext

The output is
[image: image.png]
The layout argument [2*1] or [1*2] does not seem to have an effect and the
caption placement for "b" is strange.
Am I doing something wrong?

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Strange bug with obayspaces and tagging

2020-11-26 Thread Christoph Reller
Hi,

With the currently latest version of ConTeXt LMTX 2020.11.25 21:42, this
MNWE fails with the following error message:



\setuptagging[state=start]
\starttext
\obeyspaces\obeylines
  patch
\stoptext



tex error   > tex error on line 4 in file ./scratch1.tex: Valid keyword
expected, likely 'plus'

   pa
tch

1 \setuptagging[state=start]
2 \starttext
3 \obeyspaces\obeylines
4 >>patch
5 \stoptext



This may be a bug in the tagging feature.

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] XML Namespaces and XML Setups

2020-11-16 Thread Christoph Reller
Dear List,

Consider the following MWE:

\startxmlsetups xml:demo:base
  \xmlsetsetup{#1}{tag}{xml:demo:tag}
\stopxmlsetups
\xmlregisterdocumentsetup{demo}{xml:demo:base}
\startxmlsetups xml:demo:tag
  %\doif{\xmlnamespace{#1}}{o}{NameSpaceO:}
  \xmlflush{#1}
\stopxmlsetups
\starttext
\startbuffer[test]


  text text

\stopbuffer
\xmlprocessbuffer{demo}{test}{}
\stoptext

My questions:
- Is there a good way to have a separate XML setup for each XML namespace?
- Alternatively, one has to do the distinction within the same XML setup.
In this case, how do we get the complete namespace? (In this example:
"NameSpaceA" and "NameSpaceO")

Thanks in advance for your help!

Cheers, Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] ZapfDingbats Unicode differences MKIV vs LMTX

2020-09-21 Thread Christoph Reller
On Mon, Sep 21, 2020 at 3:27 PM Hans Hagen  wrote:

> On 9/21/2020 2:55 PM, Christoph Reller wrote:
>
> > \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
>
> I don't know what the previous line does ... but it works ok here when
> you remove it.


This line loads the font from a file ZapfDingbats.ttf. Without this line I
get no check marks in the output and the following log messages:

fonts   > defining > font with asked name 'uzdr' is not found using
lookup 'file'
fonts   > defining > unknown font 'uzdr', loading aborted

Correct me if I am wrong, but there does not seem to be a font file named
uzdr* in the distribution tree.

> \definefont[zapfdingbats][ZapfDingbats]
> > \starttext
> > {\zapfdingbats ✓}
> > \definedfont[name:ZapfDingbats]✓
> > \stoptext
> >
> > I still get no check mark in the output PDF and a log message "char ✓
> > (U+02713) in font 'ZapfDingbats-4' with id 8: missing". Am I using the
> > font wrongly?
> > (This has not a high priority for me, because I have the unified access
> > by glyph index.)
>
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] ZapfDingbats Unicode differences MKIV vs LMTX

2020-09-21 Thread Christoph Reller
On Sat, Sep 19, 2020 at 12:04 PM Hans Hagen  wrote:

> On 9/19/2020 6:18 AM, Christoph Reller wrote:
> > On Fri, Sep 18, 2020 at 4:17 PM Hans Hagen  > <mailto:j.ha...@xs4all.nl>> wrote:
> >
> > On 9/18/2020 11:23 AM, Christoph Reller wrote:
> >
>  \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
> >  > \usemodule [fnt-10]
> >  > \starttext
> >  > (1) \getglyphdirect{ZapfDingbats}{61491}\crlf % MKIV log: char 
> >  > (U+0F033) in font 'ZapfDingbats-4' with id 8: missing
> >  > (2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char 
> >  > (U+F0013) in font 'ZapfDingbats-4' with id 8: missing
> >  > \ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
> >  > \stoptext
> >  >
> > Dingbats are old school t1 without proper names so we can't use
> > unicodes. However, there is a goodie that should do that so that in
> > principle it should work with unicodes but there is some interference
> > going on (i'll look at that)
> >
> > For nwo access by 'name' or 'index' (these are kind of stable for
> such
> > an old font):
> >
> >n:a34  : \getglyph{ZapfDingbats}{\tochar{n:a34}}  \par
> >n:a35  : \getglyph{ZapfDingbats}{\tochar{n:a35}}  \par
> >i:48   : \getglyph{ZapfDingbats}{\tochar{i:48}}   \par
> >i:49   : \getglyph{ZapfDingbats}{\tochar{i:49}}   \par
> >n:a104 : \getglyph{ZapfDingbats}{\tochar{n:a104}} \par
> >n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
> >
> > Thank you Hans!
> > Access by glyph index with \tochar{i:19} works well for both MKIV and
> > LMTX. Access by name with \tochar{n:a39} does not work in LMTX with log
> > message: char ✓ (U+02713) in font 'ZapfDingbats-4' with id 8: missing.
> > Also \ShowCompleteFont does not report any glyph names in LMTX.
> should be a bit better in yesterdays upload (i also changed the file
> name alias so that in pinciple unicode should work too)


 Dear Hans,

Thank you for working on this. I have tried version 2020.09.20: Unicode
input works for the "Private Use Area" Unicodes reported in
\ShowCompleteFont. Such Unicodes are, however, not desirable. Moreover, in
MKIV, a Unicode U+2713 (Check Mark) in the input did produce the
ZapfDingbats check, e.g. as follows:

\definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
\definefont[zapfdingbats][ZapfDingbats]
\starttext
{\zapfdingbats ✓}
\definedfont[name:ZapfDingbats]✓
\stoptext

I still get no check mark in the output PDF and a log message "char ✓
(U+02713) in font 'ZapfDingbats-4' with id 8: missing". Am I using the font
wrongly?
(This has not a high priority for me, because I have the unified access by
glyph index.)

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] ZapfDingbats Unicode differences MKIV vs LMTX

2020-09-18 Thread Christoph Reller
On Fri, Sep 18, 2020 at 4:17 PM Hans Hagen  wrote:

> On 9/18/2020 11:23 AM, Christoph Reller wrote:
> > Dear List,
> >
> > I have the following MWE:
> >
> > \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
> > \usemodule [fnt-10]
> > \starttext
> > (1) \getglyphdirect{ZapfDingbats}{61491}\crlf % MKIV log: char 
> > (U+0F033) in font 'ZapfDingbats-4' with id 8: missing
> > (2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char 
> > (U+F0013) in font 'ZapfDingbats-4' with id 8: missing
> > \ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
> > \stoptext
> >
> Dingbats are old school t1 without proper names so we can't use
> unicodes. However, there is a goodie that should do that so that in
> principle it should work with unicodes but there is some interference
> going on (i'll look at that)
>
> For nwo access by 'name' or 'index' (these are kind of stable for such
> an old font):
>
>   n:a34  : \getglyph{ZapfDingbats}{\tochar{n:a34}}  \par
>   n:a35  : \getglyph{ZapfDingbats}{\tochar{n:a35}}  \par
>   i:48   : \getglyph{ZapfDingbats}{\tochar{i:48}}   \par
>   i:49   : \getglyph{ZapfDingbats}{\tochar{i:49}}   \par
>   n:a104 : \getglyph{ZapfDingbats}{\tochar{n:a104}} \par
>   n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
>
> Thank you Hans!

Access by glyph index with \tochar{i:19} works well for both MKIV and LMTX.
Access by name with \tochar{n:a39} does not work in LMTX with log
message: char ✓ (U+02713) in font 'ZapfDingbats-4' with id 8: missing. Also
\ShowCompleteFont does not report any glyph names in LMTX.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] ZapfDingbats Unicode differences MKIV vs LMTX

2020-09-18 Thread Christoph Reller
Dear List,

I have the following MWE:

\definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
\usemodule [fnt-10]
\starttext
(1) \getglyphdirect{ZapfDingbats}{61491}\crlf % MKIV log: char  (U+0F033)
in font 'ZapfDingbats-4' with id 8: missing
(2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char  (U+F0013)
in font 'ZapfDingbats-4' with id 8: missing
\ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
\stoptext

In MKIV, line (1) fails to output the requested glyph, while line (2)
produces a "check" (✓). In LMTX, line (2) fails and line (1) produces the
"check" (✓) . The output of "\ShowCompleteFont" reports differing Unicodes
for the same glyphs. Apparently the Unicodes for ZapfDingbats have changed.

I would like to have a "check" (✓) in the output for both MKIV and LMTX.
Options:
A) Is there a way to address the glyph in ZapfDingbats for both MKIV and
LMTX uniformly, e.g. by glyph index? (By glyph name does not seem to work:
MKIV reports glyph names, LMTX does not.)
B) Is there a conditional that I can build into the source to distinguish
between MKIV and LMTX?
C) Is there a font in the distribution for which I can have a
"check"-symbol in both MKIV and LMTX?

Any help is appreciated!
Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Access violation

2020-09-10 Thread Christoph Reller
On Thu, Sep 10, 2020 at 8:43 PM Hans Hagen  wrote:

> On 9/9/2020 2:44 PM, Christoph Reller wrote:
> > Does this help or do you really need a MWE?
> A wme would help indeed (no need to be real minimal, as you need enough
> to trigger bumping node mem so just make somethign that crashes).
>
I will try my best to produce something.
Cheers, Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Access violation

2020-09-09 Thread Christoph Reller
Dear developers,

I am using ConTeXt LMTX version 2020.09.05 21:18 on Windows 46bit.

I have a large project for which I can reproduce an access violation:
mtx-context | fatal error: return code: -1073741819
Unfortunately, the error vanishes as soon as I alter any detail in the
project's source code.

The access violation happens always at the same location. I have produced a
log file for which I have enabled \tracingall just before the error
happens. I suspect that the error is triggered due to tagging information
written to the PDF (\setuptagging[state=start]), because disabling tagging
prevents the error. The log file (as a ZIP archive) is here
.
Does this help or do you really need a MWE?

Kind regards
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Input file name containing full stop "."

2020-09-09 Thread Christoph Reller
Dear list,

I am using ConTeXt LMTX Version 2020.09.05 21:18 with an input file named,
e.g., "test.test.tex". When compiling, ConTeXt generates files "test.log",
"test.tua", "test.pdf".

ConTeXt MKIV used to produce files "test.test.log", "test.test.tua",
"test.test.pdf".

Is there a way for ConTeXt LMTX to process input files that contain full
stops consistently? I am aware of the "--result=..." option, but what about
the "...tua", "...log" and synctex files? This is a serious problem when
running multiple compilations in parallel, e.g., on "test.a.tex" and
"test.b.tex", because both processes use the same "test.tua" file.

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] MKIV - LMTX difference: stripping of leading white space in verbatim text

2020-09-03 Thread Christoph Reller
On Thu, Sep 3, 2020 at 5:53 AM Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:

> Christoph Reller schrieb am 03.09.2020 um 05:29:
> > Dear List,
> >
> > I am using ConTeXt LMTX 2018.05.19 21:46. Consider the following MWE:
> >
> > \starttext
> > \startLUA
> >  whatever
> > \stopLUA
> > \stoptext
> >
> > In contrast to ConTeXt MKIV, the leading four spaces in front of
> > "whatever" are not removed when processing the verbatim text:
> >
> > MKIV output:
> > whatever
> >
> > LMTX output:
> >  whatever
> >
> > Is there a way to get the old MKIV behavior back?
>
> \setuptyping[LUA][strip=yes]


Thank you, 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] MKIV - LMTX difference: stripping of leading white space in verbatim text

2020-09-02 Thread Christoph Reller
Dear List,

I am using ConTeXt LMTX 2018.05.19 21:46. Consider the following MWE:

\starttext
\startLUA
whatever
\stopLUA
\stoptext

In contrast to ConTeXt MKIV, the leading four spaces in front of "whatever"
are not removed when processing the verbatim text:

MKIV output:
whatever

LMTX output:
whatever

Is there a way to get the old MKIV behavior back?

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] PNG image inclusion resolution

2020-09-02 Thread Christoph Reller
On Wed, Sep 2, 2020 at 4:36 PM Hans Hagen  wrote:

> On 9/2/2020 3:35 PM, Christoph Reller wrote:
> > Dear List,
> >
> > I am using ConTeXt LMTX 2020.08.31 22:16. Consider the following MWE:
> >
> >\starttext
> >\externalfigure[resolutionTest.png]
> >\stoptext
> >
> > When comparing the output with ConTeXt MKIV, then the image size is
> > extremely small. gimp reports the resolution of resolutionTest.png as
> > 71.984 DPI. Is this a bug? (I cannot reproduce the shrinkage with
> > hacker.png.)
>
> it's an image that has its resolution internally specified in meters and
> that bit is commented (i probably had a good reason for that but for now
> i'll uncomment it and add some safeguards for zero conversion values)
>

Thank you, Hans!
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] PNG image inclusion resolution

2020-09-02 Thread Christoph Reller
Dear List,

I am using ConTeXt LMTX 2020.08.31 22:16. Consider the following MWE:

  \starttext
  \externalfigure[resolutionTest.png]
  \stoptext

When comparing the output with ConTeXt MKIV, then the image size is
extremely small. gimp reports the resolution of resolutionTest.png as
71.984 DPI. Is this a bug? (I cannot reproduce the shrinkage with
hacker.png.)

Also, I noticed that the "resolution" key when applied as:

  \externalfigure[resolutionTest.png][resolution=150]

has no effect. What is the meaning of this key?

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Verbatim typing and compound breakpoints

2020-09-01 Thread Christoph Reller
On Tue, Sep 1, 2020 at 10:50 AM Christoph Reller 
wrote:

> I am using ConTeXt LMTX 2020.08.28 13:58 with the following M(N)WE:
>
> \definetype[typeLUA][option=LUA]
> \setbreakpoints[compound]
> \starttext
> \typeLUA{function(argument)}
> \stoptext
>
> Sadly, it does not compile.
>

I found that resetting the breakpoints within the typing command works:

\setbreakpoints[compound]
\definetype[typeLUA][option=LUA, command=\resetbreakpoints]
\starttext
\typeLUA{function(argument)}\par
If compound break points are enabled then this text line is broken after
the slash/next line.
\stoptext

Nonetheless: Is this bug?

Cheers, Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Verbatim typing and compound breakpoints

2020-09-01 Thread Christoph Reller
Dear List,

I am using ConTeXt LMTX 2020.08.28 13:58 with the following M(N)WE:

\definetype[typeLUA][option=LUA]
\setbreakpoints[compound]
\starttext
\typeLUA{function(argument)}
\stoptext

Sadly, it does not compile. The problem seems to be the simultaneous use of
compound breakpoints and parenthesis. The error message is:

callback error:
...est/tex/texmf-context/tex/context/base/mkiv/lang-ini.lua:509: bad
argument #1 to 'prehyphenchar' (luatex.lang expected, got no value)
stack traceback:
[C]: in function 'lang.prehyphenchar'
...est/tex/texmf-context/tex/context/base/mkiv/lang-ini.lua:509: in field
'prehyphenchar'
...est/tex/texmf-context/tex/context/base/mkiv/typo-brk.lua:171: in local
'method'
...est/tex/texmf-context/tex/context/base/mkiv/typo-brk.lua:392: in upvalue
'typesetters_breakpoints_handler'
[string "local tonut  = nodes.tonut..."]:16: in function <[string "local
tonut  = nodes.tonut..."]:11>
(...tail calls...)
...est/tex/texmf-context/tex/context/base/mkiv/node-pro.lua:88: in function
<...est/tex/texmf-context/tex/context/base/mkiv/node-pro.lua:79>

How can I prevent this? Is this a bug?

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] follow up

2019-04-02 Thread Christoph Reller
My two cents:

I don't believe that it is the CIDSet. Both fun.pdf and fun1.pdf have no
CIDSet (which is good).
The (relevant) differences between the two PDFs are:
- Different ToUnicode
- Different embedded font stream
- Minor differences in the font descriptor
It could be the ToUnicode: If preview is not able to parse the last entry
in the ToUnicode table then it may also drop this glyph in its display,
although ToUnicode is only relevant for text extraction.
It could be the font stream: In the CFF font file there is a CharSet table
that maps character-IDs to glyph-IDs. If preview cannot read the last entry
in this table (or the last glyph, glyph nr. 10) then it might drop it.
By bet is on the ToUnicode, because, usually, if viewers fail to read a
font file then they drop the entire font file and not single glyphs.

Anyway, both PDFs seem to be valid. But I wonder if the differences in the
font descriptor are legitimate (especially StemV):
Object 9 <-> 7: Different entry Ascent integer value: 1127 <-> 806 in font
descriptor dictionary.
Object 9 <-> 7: Different entry Descent integer value: -280 <-> -194 in
font descriptor dictionary.
Object 9 <-> 7: Different entry StemV integer value: 91 <-> 0 in font
descriptor dictionary.

Cheers,
Christoph

On Tue, Apr 2, 2019 at 10:16 PM Hans Hagen  wrote:

> On 4/2/2019 8:38 PM, Taco Hoekwater wrote:
> >
> >
> >> On 2 Apr 2019, at 17:11, Hans Hagen  wrote:
> >>
> >> On 4/2/2019 4:18 PM, Ulrike Fischer wrote:
> >>> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen:
> > indeed on preview no x shows up but it does in other viewers
> >
> 
>  Not just the x.
>  In the second example the s will disappear, be shows up if you add
> some extra digits, and then dropping the 2
> >>> I don't have a mac and can't reproduce the problem. But the missing
> >>> char seems to be always the last one in the beginbfchar/endbfchar
> >>> list.
>  The OSX preview is flaky but i’d assume the output of both context
> version would be similar (enough)
> >>> The new context adds new lines inside the beginbfchar/endbfchar
> >>> block. Perhaps this confuses preview and it drops the last entry.
> >> it is indeed the last one that is the issue but changing spacing or
> adding dummies doesn't help
> >
> > More likely the problem it has is due to the omitted /CIDSet in the font
> descriptor.
> >
> > The error is in the display engine, not the text extractor (since
> cut work ok).
> > And that means the problem is almost certainly not the cmap. The only
> other non-trivial
> > difference I saw in the old vs. new pdf was that no longer present
> /CIDSet.
> >
> > Unf., generating one in the text editor is bit beyond me-on-the-could
> mode, so I can
> > not be certain of that although it seems likely (I checked with FF that
> the two glyphs
> > are indeed in the embedded font subset and in the exact slots the pdf
> says they have, so
> > that is also unlikely to be the problem.)
> ok, i'll check that tomorrow ... (cidsets are actually obsolete)
>
> Hans
>
> -
>Hans Hagen | PRAGMA ADE
>Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] \reference not working with reference prefix and focus=standard

2018-06-25 Thread Christoph Reller
Hi,

Thank you, Hans, for supporting the focus=standard option in interactive PDFs.

I stumbled over the following problem:

\setupinteraction[state=start, focus=standard]
\starttext
\pushreferenceprefix{parent}
\reference[label]{Text}Bla
\page
\about[label]
\popreferenceprefix
\stoptext

The link's visual appearance is generated correctly and the PDF link
annotation correctly references a named destination "parent:label". In
the PDF's catalog, however, the only named destination has a name
"label", lacking the prefix.

Could you please consider fixing this issue?

Kind regards,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Using goto in lua

2018-06-22 Thread Christoph Reller
On Fri, 22 Jun 2018 13:57:05 +0200 Wolfgang Schuster
 wrote:
>
> Hans gave a solution to this a while ago:
> https://mailman.ntg.nl/pipermail/ntg-context/2018/090833.html
>
> Wolfgang

Thank you Wolfgang for pointing me to this solution!

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Using goto in lua

2018-06-22 Thread Christoph Reller
Hi,

As mentioned in cld-mkiv.pdf, the entire ConTeXt interface can be called
from lua: This is great!

Unfortunately the ConTeXt command \goto is a little problematic because
goto is a lua keyword. Therefore, the following leads to a lua error:

context.goto("text", { "label" })

I guess the only way to call goto from lua is

context(false, "\\goto{text}[label]")

Am I correct?

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Defining command with optional and mandatory arguments

2018-05-24 Thread Christoph Reller
On Thu, 24 May 2018 14:50:36 +0200, Hans Hagen <j.ha...@xs4all.nl> wrote:
> On 5/24/2018 11:21 AM, Christoph Reller wrote:
>> On Wed, 23 May 2018 16:01:05 +0200, Hans Hagen <j.ha...@xs4all.nl> wrote:
>>> On 5/23/2018 3:39 PM, Christoph Reller wrote:
>>>>
>>>> What is the right way to define a command with both mandatory and
>>>> optional arguments, e.g:
>>>>
>>>> \MyCommand[optional][mandatory]
>>>>
>>>> Consider the following MWE:
>>>>
>>>> \unexpanded\def\MyCommand[#1]{
>>>> \dosingleempty{\doMyCommand[#1]}}
>>>> \def\doMyCommand[#1][#2]{
>>>> \doifsomething{#1}{number 1: #1\par}
>>>> \doifsomething{#2}{number 2: #2}\blank[big]}
>>>> \starttext
>>>> \MyCommand[A][B]
>>>> \MyCommand[A]
>>>> \stoptext
>>>>
>>>> In last year's versions of ConTeXt the output was
>>>>
>>>> number 1: A
>>>> number 2: B
>>>> number 1: A
>>>>
>>>> In the latest version of ConTeXt the output is
>>>>
>>>> number 1: A
>>>> number 2: B
>>>> number 2: A
>>>>
>>>> Is this behavior intended? How can I make a definition whose behavior
>>>> does not change in new versions of ConTeXt?
>>> i'm not sure wht happens at your end but this is the best way:
>>>
>>> \unexpanded\def\MyCommand
>>> {\dodoubleempty\doMyCommand}
>>>
>>> \def\doMyCommand[#1][#2]%
>>> {\iffirstargument
>>>number 1: #1%
>>>\par
>>>  \fi
>>>  \ifsecondargument
>>>number 2: #2%
>>>  \fi
>>>  \blank[big]}
>>>
>>> \starttext
>>>   \MyCommand[A][B]
>>>   \MyCommand[A]
>>> \stoptext
>>
>> Thank you Hans for this information. My question is rather about error
>> handling. I want:
>>
>> \MyCommand[A][B] % <- succeeds with #1->A, #2->B
>> \MyCommand[A] % <- succeeds with #1->A
>> \MyCommand % <- fails with "! Use of \MyCommand doesn't match its definition"
>>
>> I just wanted to ask whether there is a standard way to achieve this
>> with \doempty. If not, then this is also okay.
> just use \dodoubleempty instead

Thank you for your hint, Hans. \dodoubleempty renders both arguments
optional and hence the command can be used without any argument, which
is not what I intended. Of course I can still test in the command's
definition whether at least one argument is given and generate an
error myself.

In i-context.pdf, many arguments are documented as being optional and
I assume that all the others are mandatory. A quick test has, however,
shown that when omitting mandatory arguments, either no error is
generated (e.g., nothing is setup or defined) or an obscure error
emerges other than "! Use of \ doesn't match its definition".

So I take it as a design decision that reporting missing mandatory
arguments as errors is not part of the interface implementation, and
that is a perfectly acceptable decision for me. It is just good to
know.

Thank you all for your highly valued feedback!

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Defining command with optional and mandatory arguments

2018-05-24 Thread Christoph Reller
On Wed, 23 May 2018 17:54:39 +0200, Henning Hraban Ramm <te...@fiee.net> wrote:
> Date: Wed, 23 May 2018 17:54:39 +0200
> From: Henning Hraban Ramm <te...@fiee.net>
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Subject: Re: [NTG-context] Defining command with optional and
> mandatory   arguments
> Message-ID: <a21d40d2-e607-47a4-bab0-c437dc915...@fiee.net>
> Content-Type: text/plain; charset=windows-1252
>
> Am 2018-05-23 um 16:01 schrieb Hans Hagen <j.ha...@xs4all.nl>:
>
>> On 5/23/2018 3:39 PM, Christoph Reller wrote:
>>> Hi,
>>> What is the right way to define a command with both mandatory and
>>> optional arguments, e.g:
>> i'm not sure wht happens at your end but this is the best way:
>
> Also, there’s documentation at
> http://wiki.contextgarden.net/Commands_with_optional_arguments
>
> If there’s something wrong, please fix it yourself or come back to this list 
> ;)
>

Thank you Hraban for pointing me to the wiki. I was aware of this page
but it contains only the case of mandatory arguments in curly braces
{} not in brackets [].

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Defining command with optional and mandatory arguments

2018-05-24 Thread Christoph Reller
On Wed, 23 May 2018 16:01:05 +0200, Hans Hagen <j.ha...@xs4all.nl> wrote:
>
> On 5/23/2018 3:39 PM, Christoph Reller wrote:
>> Hi,
>>
>> What is the right way to define a command with both mandatory and
>> optional arguments, e.g:
>>
>> \MyCommand[optional][mandatory]
>>
>> Consider the following MWE:
>>
>> \unexpanded\def\MyCommand[#1]{
>>\dosingleempty{\doMyCommand[#1]}}
>> \def\doMyCommand[#1][#2]{
>>\doifsomething{#1}{number 1: #1\par}
>>\doifsomething{#2}{number 2: #2}\blank[big]}
>> \starttext
>> \MyCommand[A][B]
>> \MyCommand[A]
>> \stoptext
>>
>> In last year's versions of ConTeXt the output was
>>
>> number 1: A
>> number 2: B
>> number 1: A
>>
>> In the latest version of ConTeXt the output is
>>
>> number 1: A
>> number 2: B
>> number 2: A
>>
>> Is this behavior intended? How can I make a definition whose behavior
>> does not change in new versions of ConTeXt?
> i'm not sure wht happens at your end but this is the best way:
>
> \unexpanded\def\MyCommand
>{\dodoubleempty\doMyCommand}
>
> \def\doMyCommand[#1][#2]%
>{\iffirstargument
>   number 1: #1%
>   \par
> \fi
> \ifsecondargument
>   number 2: #2%
> \fi
> \blank[big]}
>
> \starttext
>  \MyCommand[A][B]
>  \MyCommand[A]
> \stoptext

Thank you Hans for this information. My question is rather about error
handling. I want:

\MyCommand[A][B] % <- succeeds with #1->A, #2->B
\MyCommand[A] % <- succeeds with #1->A
\MyCommand % <- fails with "! Use of \MyCommand doesn't match its definition"

I just wanted to ask whether there is a standard way to achieve this
with \doempty. If not, then this is also okay.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Defining command with optional and mandatory arguments

2018-05-23 Thread Christoph Reller
Hi,

What is the right way to define a command with both mandatory and
optional arguments, e.g:

\MyCommand[optional][mandatory]

Consider the following MWE:

\unexpanded\def\MyCommand[#1]{
  \dosingleempty{\doMyCommand[#1]}}
\def\doMyCommand[#1][#2]{
  \doifsomething{#1}{number 1: #1\par}
  \doifsomething{#2}{number 2: #2}\blank[big]}
\starttext
\MyCommand[A][B]
\MyCommand[A]
\stoptext

In last year's versions of ConTeXt the output was

number 1: A
number 2: B
number 1: A

In the latest version of ConTeXt the output is

number 1: A
number 2: B
number 2: A

Is this behavior intended? How can I make a definition whose behavior
does not change in new versions of ConTeXt?

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] roadmap

2018-05-18 Thread Christoph Reller
On Tue, 15 May 2018 16:51:13 +0200 luigi scarso <luigi.sca...@gmail.com> wrote:
>
> On Tue, May 15, 2018 at 4:46 PM, Christoph Reller <
> christoph.rel...@gmail.com> wrote:
>
> > On Tue, 15 May 2018 08:23:04 +0200 luigi scarso <luigi.sca...@gmail.com>
> > wrote:
> >
> >>
> >> On Tue, May 15, 2018 at 8:15 AM, Christoph Reller <
> >> christoph.rel...@gmail.com> wrote:
> >>
> >> >
> >> > Our company is producing (and weekly updating) 67 manuals and
> >> > technical documents from more than 900 ConTeXt source files for our
> >> > software products. The output PDFs are converted to PDF/A-2a, which is
> >> > only possible due to ConTeXt's tagging.
> >> >
> >> What do you think of verapdf ?
> >>
> >
> > Well, verapdf is only a validator and not a converter.
> >
> > And, by the way, there is no reasonable way to convert from, say, PDF/A-2b
> > to PDF/A-2a without a rediculous amount of AI or manual input because the
> > tagging cannot be created out of the blue. It has to be there from the
> > document's birth. This is what makes this ConTeXt feature so precious.
> >
> sure, the point is  if   verapdf  is reliable as validator.

In my opinion, verapdf has one advantage a couple of disadvantages:

+ If everything works out as planned then verapdf may become one of
the most widely adopted validators, free of charge and open source

- verapdf is yet relatively new and hence inmature
- verapdf currently only validates against the PDF/A specifications
and not (really) against the PDF specifications. This is bad because
the latter are integral parts of the former.
- verapdf does not validate embedded streams such as images, font
files and color profiles.

In short: Only if you are sure that the input document is a valid PDF,
then verapdf can be used to test PDF/A conformance.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] roadmap

2018-05-15 Thread Christoph Reller
On Tue, 15 May 2018 08:23:04 +0200 luigi scarso <luigi.sca...@gmail.com>
wrote:

>
> On Tue, May 15, 2018 at 8:15 AM, Christoph Reller <
> christoph.rel...@gmail.com> wrote:
>
> >
> > Our company is producing (and weekly updating) 67 manuals and
> > technical documents from more than 900 ConTeXt source files for our
> > software products. The output PDFs are converted to PDF/A-2a, which is
> > only possible due to ConTeXt's tagging.
> >
> What do you think of verapdf ?
>

Well, verapdf is only a validator and not a converter.

And, by the way, there is no reasonable way to convert from, say, PDF/A-2b
to PDF/A-2a without a rediculous amount of AI or manual input because the
tagging cannot be created out of the blue. It has to be there from the
document's birth. This is what makes this ConTeXt feature so precious.

Cheers,
Christoph

>
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] roadmap

2018-05-15 Thread Christoph Reller
On Tue, May 15, 2018 at 12:53 AM,  wrote:
>
>
> Message: 3
> Date: Mon, 14 May 2018 23:26:28 +0200
> From: Hans Hagen 
> To: Henning Hraban Ramm , mailing list for ConTeXt
> users 
> Subject: Re: [NTG-context] roadmap
> Message-ID: 
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 5/14/2018 9:36 PM, Henning Hraban Ramm wrote:
> > Hi Hans, thank you so much!

Keep up the good work!

> > * PDF/* (X, A, UA - probably only reasonable with external tools, but it 
> > seems like there’s not a lot that’s usable)
>
> we support various formats (to some extend the backend even adapts to
> it) ... tagged pdf ... already there for quite a while but i never had
> any demand for it so i never really check the current state (also
> because imo it's a it weird feature ... only there because publishers
> don't want to distribute sources that are suitable for rendering
> variations ... so we're stuck with some pseudo structure related to
> visuals)
>
> (i might upgrade tagging and exports as they closely relate but it's not
> easy to get motivated for something that one has no real use for so at
> most it will cold winter evening stuff)

To us, tagged PDF is important. Specifically, for PDF/A with
compliance level a, tagging is mandatory. ConTeXt is the only (!)
TeX-based PDF creation suite that can produce correct and reliable
tagging.

Our company is producing (and weekly updating) 67 manuals and
technical documents from more than 900 ConTeXt source files for our
software products. The output PDFs are converted to PDF/A-2a, which is
only possible due to ConTeXt's tagging.

From what we hear of our customers, PDF/A level a and PDF/UA are
becoming increasingly important, be it because of archiving issues or
because of legislation requirements. So please, maintain this
invaluable feature!

Cheers, and thank you for all the effort.

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] links don’t work with focus=standard

2018-04-16 Thread Christoph Reller
On Sun, 15 Apr 2018 18:45:40 +0200 , Pablo Rodriguez  wrote:
>
>
> I’m afraid that links with "focus=standard" are broken after beta from
> 2018.04.13 14:53.
>
>
In version 2018.04.15 23:11 everything seems to work fine.


>
> I think that all links that worked fine before the latest fix
> (https://mailman.ntg.nl/pipermail/ntg-context/2018/091304.html) don’t
> work now. Could you fix them?
>
>
This feature is now also implemented. Thank you Hans. I will report back if
I find any issues.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Reference links with focus=standard

2018-04-13 Thread Christoph Reller
On Fri, 13 Apr 2018 10:45:39 +0100,  Lawrence Bell
<lawrence.matthew.b...@gmail.com> wrote:
> On 13/04/18 07:31, Henri Menke wrote:
>>
>> On Fri, 2018-04-13 at 08:13 +0200, Christoph Reller wrote:
>>>
>>> Please, Hans, I kindly ask you to reconsider. I am aware of your
>>> opinion and reasoning about this issue. But I believe that for many of
>>> us users, today's PDFs need to be both, interactive *and* printable.
>>>
>>> If there is any way I can help or motivate you, then please tell me ;-)
>>>
>> The best way to motivate Hans to implement something you need, is by
>> implementing it yourself and sending him updated core files.
>> Works for me every time ;-)
>>

Well, thank you for this hint Henry, but that works only for those who
can afford the time :-/

>
> Dear Christoph,
>
> I take it from your reply that fixing this problem with interactivity
> would likely cause some trouble with the printability? And therefore,
> it's staying as it is to prioritize printability? That's understandable,
> but a bit frustrating, since I still don't have any clue what the actual
> problem is. Could you possibly explain in some more detail or point me
> to a relevant thread?
>
> Kind regards,
>
> Lawrence
>

Dear Lawrence,

(Sorry for changing to bottom posting style.)

This issue is not about a trade-off between print-ability and
inter-activeness. If I understand Hans' position correctly, then at
least part of his reasoning is the following (please correct me if I'm
wrong): It is easy to produce two versions of a document from one
common source, one version for print and one for the screen. The
former needs no interactive links and the latter should best be viewed
fullscreen, i.e., without scrolling, in which case focus=standard is
unnecessary. While I largely agree with this approach, many of the
ConTeXt users (including myself) are not in a position to decide how
their documents should be published. I believe that many of today's
PDF documents still are meant to be both, viewed on screen and
printed. And it's only for this scenario that focus=standard makes
sense.

Kind regards,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Reference links with focus=standard option

2018-04-13 Thread Christoph Reller
Fri, 13 Apr 2018 11:48:28 +0200, Hans Hagen <j.ha...@xs4all.nl> wrote:
> On 4/13/2018 8:13 AM, Christoph Reller wrote:
>>
>> This is a long standing feature request reported multiple times by
>> myself and others with MWEs in
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg79620.html and
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg79727.html.
>>
>> Another MWE in which the link is non-functional:
>>
> fixed in next beta (i'm not sure when i will upload that one as i need
> to test some new features first)
>

Thank you Hans!

This is good news. Your work is very much appreciated. I am looking
forward to the next beta.

Regards,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Reference links with focus=standard option

2018-04-13 Thread Christoph Reller
> On Wed, 11 Apr 2018 20:27:15 +0100, Lawrence Bell 
>  wrote:
>
> Thanks very much for your replies. It's reassuring to see (it seems)
> that I've not overlooked some extra option that magically does the job
> :) Worst case scenario I'll hack something together, or just settle for
> the default focus functionality, which is not the end of the world. Just
> feel like there should be a better/more elegant way.
>
> On 11/04/18 19:36, Pablo Rodriguez wrote:
>> On 04/11/2018 07:14 PM, Pablo Rodriguez wrote:
>>> On 04/11/2018 04:35 PM, Lawrence Bell wrote:
 [...]
 What's going on here?
>>> I generated an uncompressed PDF document from your source:
>>> http://pdf.ousia.tk/focus-standard.pdf.
>>> [...]
>>> (eq:ref) seems to be missing there. But I have to investigate the issue
>>> further to get a more accurate report.
>> [...]
>> Sorry, but I’m afraid that I don’t know exactly what misbehaves here. I
>> hope Hans can fix it.

Dear all,

This is a long standing feature request reported multiple times by
myself and others with MWEs in
https://www.mail-archive.com/ntg-context@ntg.nl/msg79620.html and
https://www.mail-archive.com/ntg-context@ntg.nl/msg79727.html.

Another MWE in which the link is non-functional:

\setupexternalfigures[location={local,global,default}]
\setupinteraction[state=start, focus=standard]
\starttext
\about[figure].
\page
\placefigure[][figure]{Figure}{\externalfigure[cow.pdf]}
\stoptext

Please, Hans, I kindly ask you to reconsider. I am aware of your
opinion and reasoning about this issue. But I believe that for many of
us users, today's PDFs need to be both, interactive *and* printable.

If there is any way I can help or motivate you, then please tell me ;-)

Kind regards,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] option for printing range

2018-02-27 Thread Christoph Reller
On Tue, Feb 27, 2018 at 10:05 PM, Hans Hagen <pra...@wxs.nl> wrote:
> On 2/27/2018 7:47 PM, Christoph Reller wrote:
>
> anyway, i normally test pdf with an old acrobat X pro (i don't want to lock
> into some subscription and i don't really need a more modern version) and i
> preview / print pdf using sumatra pdf
>
> (printing houses often use pretty old versions anyway)
>

You may actually be better off with Acrobat X then with Acrobat DC
when it comes to testing, because Acrobat DC has an even stronger
tendency to ignore errors silently. :-)

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] option for printing range

2018-02-27 Thread Christoph Reller
On Tue, 27 Feb 2018 09:15:37 +0100 Hans Hagen  wrote:
> On 2/26/2018 8:02 PM, Pablo Rodriguez wrote:
>> On 02/25/2018 10:51 PM, Hans Hagen wrote:
>>> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote:
 [...]
 The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10"
 (the document only contains 10 pages).
>>>
>>> is ok here (looking in the pdf file)
>>
>> I have tested the file in Acrobat XI and since I got the same wrong page
>> ranges, I asked to an Adobe engineer.
>>
>> He confirmed that the spec is wrong. Page counting for /PrintPageRange
>> should be zero-based and it shouldn’t start from one.

This is only one of many cases for which ISO-32000 is the spec and the
Adobe Reader is the de-facto spec. Others affect annotations and
rendering.

>> Sorry for this. Could you correct the implementation?
> the usual pdf spec rubish ... no one uses it (although tex is often
> first), they it gets a bugged implementation and then the specs change
> ... one of the reasons why i don't bother too much in implementing the
> latest pdf gadgets ... i wasted too much time adapting to changed
> (interpretation of the) specs
>
> Hans
>
> (I don't officially have the latest spec as i refuse to pay for a pdf
> specification that could be distributed in pdf format.)

A small detail: The ISO specification for PDF 2.0 also defines the
first page in /PrintPageRange to be page number 1 (not 0). :(

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] type and typing comments for TeX and Lua

2017-12-27 Thread Christoph Reller
On Wed, 27 Dec 2017 19:53:58 +0100, Pablo Rodriguez  wrote:
> could you enable issues in your Bitbucket repository?

Issues are enabled now.
Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] type and typing comments for TeX and Lua

2017-12-21 Thread Christoph Reller
On Thu, 21 Dec 2017 21:16:45 +0100,  Pablo Rodriguez <oi...@gmx.es> wrote:
> On 12/21/2017 05:04 PM, Christoph Reller wrote:
>> Dear Pablo,
>>
>> At least for XML you could use my module highlight-xml:
>>
>> \usemodule[highlight-xml]
>> \definetype[xml][option=xml]
>> [...]
>> Note that even partial XML is highlighted correctly.
>
> It is really a pity that it lacks TeX, since I’m focused on ConTeXt yet
> (after all, it would be a Spanish introduction to ConTeXt ;-)). XML will
> come later.

Maybe, if I find the time, I will add TeX and Lua to my module some time.

> I’m afraid that XML comments are colored the same way with your module
> and with standard ConTeXt.

That should not be the case. Could it be, that the highlight-xml
module fails to load? Please check your log file for a "module not
found" entry. I have attached the result of my earlier sample.

My module does not come in standard context. You have to download it
from https://bitbucket.org/philexander/context-highlight. If general
interest is high enough I can ask  to
add it.

Kind regards,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] type and typing comments for TeX and Lua

2017-12-21 Thread Christoph Reller
On Tue, Mon, 18 Dec 2017 23:50:09 +0100, Pablo Rodriguez  wrote:
> I have the following sample:
>
> \definetype[context][option=tex]
> \definetype[lua][option=lua]
> \starttext
> \startTEXpage[offset=2em]
>
> a \TEX\ inline comment: \context{ag%befe}
>
> \Lua\ inline comment: \lua{agb --efe}
>
> \startTEX
> This is text. % a comment, not \comment
> \stopTEX
>
> \startXML
> This is text.
> \stopXML
>
> \startLUA
> if code=="code" then --this is a comment
> \stopLUA
> \stopTEXpage
> \stoptext
>
> Would it be possible that all comments in type and typing (at least, for
> Lua, XML and TeX) would have the same formatting for the whole comment
> contents, including the comment signs?

Dear Pablo,

At least for XML you could use my module highlight-xml:

\usemodule[highlight-xml]
\definetype[xml][option=xml]
\starttext
\startTEXpage[offset=2em]
  \xml{attr="value"}\crlf
  \xml{This is text.}
  \startXML
This is text.
  \stopXML
\stopTEXpage
\stoptext

Note that even partial XML is highlighted correctly.

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] TikZ modules are missing \startmodule

2017-12-11 Thread Christoph Reller
Hi Christian,

Thank you for your support. I think you should insert a line

\startmodule[]

after \unprotect in the following files

\tex\texmf-modules\tex\context\pgf\basiclayer\t-pgf.tex
\tex\texmf-modules\tex\context\pgf\basiclayer\t-pgfbim.tex
\tex\texmf-modules\tex\context\pgf\basiclayer\t-pgfcor.tex
\tex\texmf-modules\tex\context\pgf\frontendlayer\t-tikz.tex
\tex\texmf-modules\tex\context\pgf\math\t-pgfmat.tex
\tex\texmf-modules\tex\context\pgf\systemlayer\t-pgfsys.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgfcal.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgffor.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgfkey.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgfmod.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgfrcs.tex

The  should be the file-name without the leading "t-" and
without the extension ".tex".
E.g: \startmodule[pgf]

Please anybody correct me if I am wrong or missing something.

Kind regards,
Christoph

On Fri, Dec 8, 2017 at 4:44 PM, Christian Feuersaenger
 wrote:
> Hi,
>
> thanks for making me aware of problems with ConTeXt and TikZ.
>
> I will look into it, probably after christmas. I would appreciate it if you
> could make a detailed report, especially containing the missing statements
> or the suggested modifications. The report can be a mail; ticket is also
> fine with me.
>
> Kind regards
>
> Christian
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] TikZ modules are missing \startmodule

2017-12-08 Thread Christoph Reller
On Fri, Dec 8, 2017 at 9:04 AM, Mojca Miklavec
<mojca.miklavec.li...@gmail.com> wrote:
> Dear Christoph,
>
> On 8 December 2017 at 08:38, Christoph Reller wrote:
>> Hi,
>>
>> Since a module nesting check has been introduced in file-mod.mkvi, the TikZ
>> modules provoke "module wrapping error" messages in the log file. May I
>> kindly ask the maintainer of the TikZ modules to insert the missing
>> \startmodule command in the following files:
>>
>> \tex\texmf-modules\tex\context\pgf\basiclayer\t-pgf.tex
>> \tex\texmf-modules\tex\context\pgf\basiclayer\t-pgfbim.tex
>> \tex\texmf-modules\tex\context\pgf\basiclayer\t-pgfcor.tex
>> \tex\texmf-modules\tex\context\pgf\frontendlayer\t-tikz.tex
>> \tex\texmf-modules\tex\context\pgf\math\t-pgfmat.tex
>> \tex\texmf-modules\tex\context\pgf\systemlayer\t-pgfsys.tex
>> \tex\texmf-modules\tex\context\pgf\utilities\t-pgfcal.tex
>> \tex\texmf-modules\tex\context\pgf\utilities\t-pgffor.tex
>> \tex\texmf-modules\tex\context\pgf\utilities\t-pgfkey.tex
>> \tex\texmf-modules\tex\context\pgf\utilities\t-pgfmod.tex
>> \tex\texmf-modules\tex\context\pgf\utilities\t-pgfrcs.tex
>>
>> Kind regards,
>> Christoph
>
> Thanks for the report. I suspect that the maintainer of TikZ might not
> be reading this mailing list (and is certainly not a ConTeXt user
> himself).
>
> I'm CC-ing him. The issue tracker is here:
> https://sourceforge.net/p/pgf/bugs/
>
> In the past Hans and Aditya wrote a number of patches for TikZ
> (potentially even fixing this particular issues, I'm not sure), but
> not all of them were included.
>
> So ... we need some more persistence in making sure that things get
> fixed. This list might be the best place to get the patches, but then
> you need to make sure that the patches are actually included upstream.
> (This reminds me that I probably need to check if TikZ is still
> properly synchronized with upstream in our distribution. As far as I
> know SF is dropping support for CVS and I need to check how we sync
> the sources now.)
>
> Mojca

Thank you Mojca,

I hope that Christian will take care for this. Keep up the good work!

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] TikZ modules are missing \startmodule

2017-12-07 Thread Christoph Reller
Hi,

Since a module nesting check has been introduced in file-mod.mkvi, the TikZ
modules provoke "module wrapping error" messages in the log file. May I
kindly ask the maintainer of the TikZ modules to insert the missing
\startmodule command in the following files:

\tex\texmf-modules\tex\context\pgf\basiclayer\t-pgf.tex
\tex\texmf-modules\tex\context\pgf\basiclayer\t-pgfbim.tex
\tex\texmf-modules\tex\context\pgf\basiclayer\t-pgfcor.tex
\tex\texmf-modules\tex\context\pgf\frontendlayer\t-tikz.tex
\tex\texmf-modules\tex\context\pgf\math\t-pgfmat.tex
\tex\texmf-modules\tex\context\pgf\systemlayer\t-pgfsys.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgfcal.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgffor.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgfkey.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgfmod.tex
\tex\texmf-modules\tex\context\pgf\utilities\t-pgfrcs.tex

Kind regards,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] \startitemize[columns] and footnote

2017-12-05 Thread Christoph Reller
On Fri, 1 Dec 2017 12:49:33 +0100 luigi scarso <luigi.sca...@gmail.com>
wrote:

> On Fri, Dec 1, 2017 at 10:14 AM, Christoph Reller
> <christoph.rel...@gmail.com> wrote:
> > \starttext
> > Text \footnote{Bla}
> > \startitemize[columns]
> > \item Item
> > \stopitemize
> > \stoptext
> >
> > In the rendered output, the footnote is drawn on top of the item (see
> > attached output.png). I am afraid this looks like a bug. Please consider
> > fixing this or tell me how to make footnotes render in the footnote area.
>
> dunno if it's a bug,
> but I usually do
>
> \starttext
> Text \footnote{Bla}
> \startcolumns
> \startitemize
> \item \input knuth\relax
> \item \input knuth\relax
> \stopitemize
> \stopcolumns
> \stoptext


Thank you for your answer Luigi!

(And sorry for my slow response - spam filter was doing crazy things.)

Your solution indeed makes the footnote appear at the right place. But the
layout is not the same as with \startitemize[columns]. Consider:

Text \footnote{Bla}
\startcolumns
\startitemize
\dorecurse{8}{\item Item}
\stopitemize
\stopcolumns

This results in 5 "Item"s in the left column and 3 "Item"s in the right
column. On the other hand

Text \footnote{Bla}
\startitemize[columns]
\dorecurse{8}{\item Item}
\stopitemize

results in 4 "Item"s in both columns, which IMHO is more correct.

Don't you agree that \startitmize[columns] is buggy with respect to
footnotes? Or is the [columns] parameter not supported anymore?

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] \startitemize[columns] and footnote

2017-12-01 Thread Christoph Reller
Hi,

Consider the following MWE:

\starttext
Text \footnote{Bla}
\startitemize[columns]
\item Item
\stopitemize
\stoptext

In the rendered output, the footnote is drawn on top of the item (see
attached output.png). I am afraid this looks like a bug. Please consider
fixing this or tell me how to make footnotes render in the footnote area.

Regards,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Tagging nested itemize with interaction

2017-10-31 Thread Christoph Reller
Dear Hans,

Consider the following MWE with nested multi-column itemize and item label:

\setuptagging[state=start]
\setupinteraction[state=start]
\starttext
\startitemize[n]
\item[label] First
  \startitemize[a, columns]
  \item Second
  \item Third
  \stopitemize
\stopitemize\crlf
Bla \in{Item}[label].
\stoptext

The above results in a PDF whose tag tree looks as follows:

‹document›
 |-‹itemgroup› itemize
 |  |-
 |  |  |-‹itemtag›
 |  |  |  '-"1."
 |  |  '-‹itemcontent›
 |  | |-"First"
 |  | '-‹itemgroup› itemize
 |  ||-‹item›
 |  ||  |-‹itemtag›
 |  ||  |  '-"a."
 |  ||  '-‹itemcontent›
 |  || '-"Second"
 |  |'-‹item›
 |  |   |-‹itemtag›
 |  |   |  '-"b."
 |  |   '-‹itemcontent›
 |  |  '-"Third"
 |  '-‹link›
 | '-"Item 1"
 |-"Bla"
 '-"."

In this tag tree, the ‹link› item is placed wrongly inside the topmost
‹itemgroup›. It sould be located between "Bla" and ".". This happens
only if:
1. An itemization with multiple columns is nested in an itemization
2. Interaction is enabled.

I think this is a bug. Please consider fixing it.

Kind regards,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] ntg-context Digest, Vol 160, Issue 40

2017-10-24 Thread Christoph Reller
On Tue, 24 Oct 2017 18:31:24 +0200 Pablo Rodriguez <oi...@gmx.es> wrote:

>
> On 10/24/2017 07:05 AM, Christoph Reller wrote:
> > [...]
> > Thank you Pablo for confirming this!
> >
> > Does anybody know whether this is a bug or whether it is the wrong way
> > to enable font-based kerning for quotations?
>
> Hi Christoph,
>
> from the devel mailing list
> (https://mailman.ntg.nl/pipermail/dev-context/2017/003422.html): this is
> a bug and it there is a fix for it.
>
> It will be applied in one of the next betas (but you can patch your
> ConTeXt distribution yourself).
>

Thank you Pablo for pointing me to the developer's mailing list. I have not
thought about searching through that. So, this is good news for me and I
will wait for the fix.

Cheers, Christoph

>
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Quotation with method=font produces error

2017-10-23 Thread Christoph Reller
Mon, 23 Oct 2017 17:21:25 +0200, Pablo Rodriguez <oi...@gmx.es> wrote:
> On 10/23/2017 09:03 AM, Christoph Reller wrote:
>> [...]
>> Could you please confirm (or deny) that the following MWE produces an
>> error with the currently latest version of ConTeXt:
>>
>> \setupquotation[method=font]
>> \starttext
>> \quotation{A}
>> \stoptext
>
> Hi Christoph,
>
> I’m afraid it fails:
> [...]

Thank you Pablo for confirming this!

Does anybody know whether this is a bug or whether it is the wrong way
to enable font-based kerning for quotations?

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Quotation with method=font produces error

2017-10-23 Thread Christoph Reller
On Thu, Oct 19, 2017 at 1:59 PM Christoph Reller <christoph.rel...@gmail.com>
wrote:

> On Thu, 19 Oct 2017 11:53:56 +0200 Floris van Manen <v...@klankschap.nl
> > wrote:
>
>>
>> > On 19 Oct 2017, at 11:33, Christoph Reller <christoph.rel...@gmail.com>
>> wrote:
>> >
>> > \setupquotation[method=font]
>>
>> what is the intension of the method=font ?
>>
>>
> Thank you for asking. Consider the following MWE:
>
> \setupbodyfont[cambria]
> %\setupquotation[method=font]
> \starttext
> \quotation{A}\crlf
> “A”
> \stoptext
>
> In the output rendering of the above (see attachment), the first line
> lacks kerning between the double quotes and the letter A. This can be
> enabled by saying \setupquotation[method=font]. At least that is what I
> know about this option. Am I wrong? Is there a different option for
> enabling this?
>

Dear Floris (or anybody from the list),

Could you please confirm (or deny) that the following MWE produces an error
with the currently latest version of ConTeXt:

\setupquotation[method=font]
\starttext
\quotation{A}
\stoptext

Thank you,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Caption location in floatcombination

2017-10-23 Thread Christoph Reller
On Tue, Oct 17, 2017 at 11:00 AM Christoph Reller <
christoph.rel...@gmail.com> wrote:

> On Mon, Sep 18, 2017 at 7:19 AM Christoph Reller <
> christoph.rel...@gmail.com> wrote:
>
>> On Sun, Sep 17, 2017 at 6:03 PM Hans Hagen <pra...@wxs.nl> wrote:
>>
>>> On 9/13/2017 8:30 AM, Christoph Reller wrote:
>>> > It seems to me that the location given to \setupcaptions is not honored
>>> > correctly in floatcombinations anymore. Consider the following MWE:
>>> >
>>> > \setupcaptions[location=top, number=no]
>>> > \starttext
>>> > \placetable[][]{One}{
>>> >\bTABLE \bTR \bTD First \eTD \eTR \eTABLE}
>>> > \placefloat[][]{}{
>>> >\startfloatcombination
>>> >  \placetable[][]{Two}{
>>> >\bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
>>> >\stopfloatcombination}
>>> > \stoptext
>>> >
>>> > In earlier versions of ConTeXt, both captions "One" and "Two" of both
>>> > tables are rendered above the respective table. In the currently latest
>>> > version, the caption "Two" is rendered below the table. Is this a bug
>>> or
>>> > do I have to setup caption location separately for floatcombinations?
>>> >
>>> > Any feedback is welcome.\setupcaptions[location=top,number=no]
>>>
>>> \starttext
>>>
>>> \placetable{TABLE}{\bTABLE \bTR \bTD First \eTD \eTR \eTABLE}
>>>
>>> \placefloat{FLOAT}{%
>>>\startfloatcombination
>>>  \placetable{Two}{\bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
>>>  \placetable{Two}{\bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
>>>\stopfloatcombination}
>>> \stoptext
>>
>>
>> Thank you for your input, Hans!
>>
>> I see that the captions "TABLE" and "FLOAT" are placed on top while the
>> captions "Two" and "Two" are placed on the bottom. Is there a way to setup
>> the locations of the captions of floats within a floatcombination? In this
>> particular example, the goal is, that the captions "Two" and "Two" are
>> placed on top of the respective tables.
>>
>
>  Does anybody know a way to control the caption location in
> floatcombinations? Any hint would be greatly appreciated.
>
>
Dear List,

I have noticed that in normal combinations \setupcaption[location=...] is
not honored either. MWE:

\setupcaptions[location=top, number=no]
\starttext
\placefigure{Two Tables}{
  \startcombination
{\bTABLE\bTR\bTD First\eTD\eTR\eTABLE}{First}
{\bTABLE\bTR\bTD Second\eTD\eTR\eTABLE}{Second}
  \stopcombination}
\stoptext

The caption "Two Tables" is located above the combination. The captions
"First" and "Second" are, however, located below. How can I setup captions
such that "First" and "Second" are located also above? If this is not
supported then I would be glad to know.

By the way, I have noticed that \setupcaptions is missing from
i-context.pdf. Is this omission on purpose?

Kind regards,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Quotation with method=font produces error

2017-10-19 Thread Christoph Reller
On Thu, 19 Oct 2017 11:53:56 +0200 Floris van Manen <v...@klankschap.nl
> wrote:

>
> > On 19 Oct 2017, at 11:33, Christoph Reller <christoph.rel...@gmail.com>
> wrote:
> >
> > \setupquotation[method=font]
>
> what is the intension of the method=font ?
>
>
Hi Floris,

Thank you for asking. Consider the following MWE:

\setupbodyfont[cambria]
%\setupquotation[method=font]
\starttext
\quotation{A}\crlf
“A”
\stoptext

In the output rendering of the above (see attachment), the first line lacks
kerning between the double quotes and the letter A. This can be enabled by
saying \setupquotation[method=font]. At least that is what I know about
this option. Am I wrong? Is there a different option for enabling this?

Regards,
Christoph

PS: Sorry for the wrong subject line of my previous email. It is corrected
now.
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] ntg-context Digest, Vol 160, Issue 26

2017-10-19 Thread Christoph Reller
On Tue, 17 Oct 2017 13:38:37 + Christoph Reller <
christoph.rel...@gmail.com> wrote:

>
> In previous versions of ConTeXt the following MWE worked:
>
> \setupquotation[method=font]
> \starttext
> \quotation{A}
> \stoptext
>
> In more recent versions, the above produces an error:
>
> ! Extra }, or forgotten \endgroup
> l.3 \quotation{A}
>
> Is this a bug?
>

Please, could anybody confirm or disapprove this behavior.

Regards,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Quotation with method=font produces error

2017-10-17 Thread Christoph Reller
Hi,

In previous versions of ConTeXt the following MWE worked:

\setupquotation[method=font]
\starttext
\quotation{A}
\stoptext

In more recent versions, the above produces an error:

! Extra }, or forgotten \endgroup
l.3 \quotation{A}

Is this a bug?

Regards,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Caption location in floatcombination

2017-10-17 Thread Christoph Reller
On Mon, Sep 18, 2017 at 7:19 AM Christoph Reller <christoph.rel...@gmail.com>
wrote:

> On Sun, Sep 17, 2017 at 6:03 PM Hans Hagen <pra...@wxs.nl> wrote:
>
>> On 9/13/2017 8:30 AM, Christoph Reller wrote:
>> > It seems to me that the location given to \setupcaptions is not honored
>> > correctly in floatcombinations anymore. Consider the following MWE:
>> >
>> > \setupcaptions[location=top, number=no]
>> > \starttext
>> > \placetable[][]{One}{
>> >\bTABLE \bTR \bTD First \eTD \eTR \eTABLE}
>> > \placefloat[][]{}{
>> >\startfloatcombination
>> >  \placetable[][]{Two}{
>> >\bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
>> >\stopfloatcombination}
>> > \stoptext
>> >
>> > In earlier versions of ConTeXt, both captions "One" and "Two" of both
>> > tables are rendered above the respective table. In the currently latest
>> > version, the caption "Two" is rendered below the table. Is this a bug or
>> > do I have to setup caption location separately for floatcombinations?
>> >
>> > Any feedback is welcome.\setupcaptions[location=top,number=no]
>>
>> \starttext
>>
>> \placetable{TABLE}{\bTABLE \bTR \bTD First \eTD \eTR \eTABLE}
>>
>> \placefloat{FLOAT}{%
>>\startfloatcombination
>>  \placetable{Two}{\bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
>>  \placetable{Two}{\bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
>>\stopfloatcombination}
>> \stoptext
>
>
> Thank you for your input, Hans!
>
> I see that the captions "TABLE" and "FLOAT" are placed on top while the
> captions "Two" and "Two" are placed on the bottom. Is there a way to setup
> the locations of the captions of floats within a floatcombination? In this
> particular example, the goal is, that the captions "Two" and "Two" are
> placed on top of the respective tables.
>

 Does anybody know a way to control the caption location in
floatcombinations? Any hint would be greatly appreciated.

Regards,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Module Update from GIT URL Fails

2017-09-28 Thread Christoph Reller
On Wed, 27 Sep 2017 11:55:06 +0200 Taco Hoekwater 
wrote:

>
> Alright, I think I have this figured out now. You *have to* use the https
> protocol, but then it should work.
>
>https://bitbucket.org/philexander/context-highlight.git
>
> You cannot use any git protocol except (anonymous) https. If you try
> any other protocol, the 'git clone' command that is started by the
> webserver
> will attempt to do an interactive input query and subsequently fail.
>
> I have updated help.html with the above explanation as well.
>
> Best wishes,
> Taco
>

Thank you Taco!

With the https protocol the upload of a new version indeed works. Thank you
also for updating the help page.

Regards,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Module Update from GIT URL Fails

2017-09-26 Thread Christoph Reller
On Mon, 25 Sep 2017 10:57:48 +0200 Taco Hoekwater  wrote:

> > I don't seem to be able to update my ConTeXt module "high". I try to
> create a new version by entering the URL of my git repository
> (g...@bitbucket.org:philexander/context-highlight.git) into the GIT URL
> field and clicking submit. But the website then tells me "Change to
> temporary directory failed". What am I doing wrong?
>
> Not you, me. Something was wrong with the directory permissions on the
> server. It should
> be fixed now, but I cannot test myself. Please let me know whether it
> works ok now.
>

Dear Taco,

Thank you for your effort. Unfortunately, I still get the same error
"Change to temporary directory failed". Could you please be so kind and
check once more what could be wrong with the server.

On Mon, 25 Sep 2017 21:01:18 -0400 (EDT) Aditya Mahajan  wrote:

> > I try to create
> > a new version by entering the URL of my git repository
> > (g...@bitbucket.org:philexander/context-highlight.git)
> > into the GIT URL field
>
> OT: Since you haven't uploaded your module yet, might I suggest that you
> change the name to t-highlight instead of t-high. That will be in line
> with the ConTeXt convention of using full names instead of abbreviations.
>
> Thanks,
> Aditya
>

 Thank you for this hint, Aditya. I have renamed the module and am awaiting
that the Update from GIT URL works again.

Kind regards to both of you,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Module Update from GIT URL Fails

2017-09-22 Thread Christoph Reller
Dear Taco,

Moica has told me that you are the maintainer of modules.contextgarden.net.
Is this correct?

I don't seem to be able to update my ConTeXt module "high". I try to create
a new version by entering the URL of my git repository
(g...@bitbucket.org:philexander/context-highlight.git)
into the GIT URL field and clicking submit. But the website then tells me
"Change to temporary directory failed". What am I doing wrong?

By the way: My web browser tells me that the certificate of
https://modules.contextgarden.net has expired.

Kind regards,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Caption location in floatcombination

2017-09-17 Thread Christoph Reller
On Sun, Sep 17, 2017 at 6:03 PM Hans Hagen <pra...@wxs.nl> wrote:

> On 9/13/2017 8:30 AM, Christoph Reller wrote:
> > Hi,
> >
> > It seems to me that the location given to \setupcaptions is not honored
> > correctly in floatcombinations anymore. Consider the following MWE:
> >
> > \setupcaptions[location=top, number=no]
> > \starttext
> > \placetable[][]{One}{
> >\bTABLE \bTR \bTD First \eTD \eTR \eTABLE}
> > \placefloat[][]{}{
> >\startfloatcombination
> >  \placetable[][]{Two}{
> >\bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
> >\stopfloatcombination}
> > \stoptext
> >
> > In earlier versions of ConTeXt, both captions "One" and "Two" of both
> > tables are rendered above the respective table. In the currently latest
> > version, the caption "Two" is rendered below the table. Is this a bug or
> > do I have to setup caption location separately for floatcombinations?
> >
> > Any feedback is welcome.\setupcaptions[location=top,number=no]
>
> \starttext
>
> \placetable{TABLE}{\bTABLE \bTR \bTD First \eTD \eTR \eTABLE}
>
> \placefloat{FLOAT}{%
>\startfloatcombination
>  \placetable{Two}{\bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
>  \placetable{Two}{\bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
>\stopfloatcombination
> }
> \stoptext


Thank you for your input, Hans!

I see that the captions "TABLE" and "FLOAT" are placed on top while the
captions "Two" and "Two" are placed on the bottom. Is there a way to setup
the locations of the captions of floats within a floatcombination? In this
particular example, the goal is, that the captions "Two" and "Two" are
placed on top of the respective tables.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Who is maintaining the modules website?

2017-09-14 Thread Christoph Reller
On Thu, 14 Sep 2017 11:50:03 +0200 Mojca Miklavec <
mojca.miklavec.li...@gmail.com>   wrote:

> On 13 September 2017 at 15:06, Christoph Reller wrote:
> > I tried to send an email to modu...@contextgarden.net and got the below
> > reply. On https://modules.contextgarden.net/help.html, this email
> address is
> > mentioned as the primary contact point to the maintainer of the
> > modules.contextgarden.net website. Who can I contact if I have a problem
> > with this website?
>
> Taco Hoekwater, currently busy at the ConTeXt meeting:
> http://meeting.contextgarden.net/
>
> But if the above email is not working, we'll fix it. I suspect that
> Taco asked me to create a mailing list and I forgot.
>
> Anyway, reporting infrastructure problems on this mailing list is also
> perfectly fine.
>

Thank you Mojca!

I will raise the issue once the ConTeXt meeting is over.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Who is maintaining the modules website?

2017-09-13 Thread Christoph Reller
Hi,

I am unsure whether this mailing list is the correct one to ask this
question. So please excuse the noise.

I tried to send an email to modu...@contextgarden.net and got the below
reply. On https://modules.contextgarden.net/help.html, this email address
is mentioned as the primary contact point to the maintainer of the
modules.contextgarden.net website. Who can I contact if I have a problem
with this website?

Cheers,
Christoph

-- Forwarded message -
From: Mail Delivery System 
Date: Wed, Sep 13, 2017 at 2:13 PM
Subject: Undelivered Mail Returned to Sender
To: 


This is the mail system at host mail.ijs.si.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to 

If you do so, please include this problem report, including
the few lines that follow this paragraph. You can delete your
own text from the attached returned message.

: host
lioness.ijs.si[2001:1470:ff80:88:219:d1ff:fe3c:c4cc] said: 550 5.1.1
: Recipient address rejected: User unknown in
local recipient table (in reply to RCPT TO command)
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Caption location in floatcombination

2017-09-13 Thread Christoph Reller
Hi,

It seems to me that the location given to \setupcaptions is not honored
correctly in floatcombinations anymore. Consider the following MWE:

\setupcaptions[location=top, number=no]
\starttext
\placetable[][]{One}{
  \bTABLE \bTR \bTD First \eTD \eTR \eTABLE}
\placefloat[][]{}{
  \startfloatcombination
\placetable[][]{Two}{
  \bTABLE \bTR \bTD Second \eTD \eTR \eTABLE}
  \stopfloatcombination}
\stoptext

In earlier versions of ConTeXt, both captions "One" and "Two" of both
tables are rendered above the respective table. In the currently latest
version, the caption "Two" is rendered below the table. Is this a bug or do
I have to setup caption location separately for floatcombinations?

Any feedback is welcome.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Hyphenation with dashes in natural table

2017-09-13 Thread Christoph Reller
Dear Pablo, Rik, and Thomas

Thank you so much for your quick help! This gives me much more insight into
the matter. And you provide various solutions with their pros and cons. For
the moment I will stick to Thomas' suggestion \setupbreakpoints[compound]
because I don't want to change the source files.

Many thanks,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Hyphenation with dashes in natural table

2017-09-11 Thread Christoph Reller
Hi,

It seems that the hyphenation algorithm for long words with dashes when
typeset in a natural table has changed.

MWE:

\starttext
\bTABLE[width=5cm]
\bTR
\bTD super-cali-fragi-listic-expi-ali-docious \eTD
\bTD The longest word known to me that ever had an appearance in a musical.
\eTD
\eTR
\eTABLE
\stoptext

In earlier versions of ConTeXt, the super-cali... word is hyphenated after
"expi-" and no overfull box occurs. In the currently latest version the
word is hyphenated after "super-" and, since the rest of the word does not
fit the table cell, it overlaps text in the right hand cell.

Could this be a bug or do I have to setup hyphenation differently in
natural tables? Any feedback is welcome.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Tagging and Math Matrix

2017-09-06 Thread Christoph Reller
On Wed, 6 Sep 2017 11:25:51 +0200 Hans Hagen <pra...@wxs.nl> wrote:

> On 9/6/2017 9:55 AM, Christoph Reller wrote:
> > On Tue, 5 Sep 2017 16:29:52 +0200 Hans Hagen <pra...@wxs.nl
> > <mailto:pra...@wxs.nl>>   wrote:
> >
> > On 8/30/2017 9:45 AM, Christoph Reller wrote:
> >  > On Mon, Dec 28, 2015 at 3:45 PM Christoph Reller
> >  > <christoph.rel...@gmail.com> wrote:
> >  >
> >  > There seems to be a problem with the structure information added
> >  > when using \startmatrix:
> >  >
> >  > A fix would be very much appreciated.
> >
> > should be ok now
> >
> >
> > Thank you Hans for this fix!
> >
> > There seems to be, however, still a minor issue with a more complete MWE:
> > \math{
> >\startmatrix
> >  \NC A \NC B \NR
> >  \NC C \NC D \NR
> >\stopmatrix}
>
> can you test with
>
> \def\math_matrix_process#1#2%
>{\forgettagging % otherwise dummy mrows and such
> \dowithnextbox
>   {\scratchdimen\dimexpr(\nextboxdp-\nextboxht)/2
> \ifcase#2\or+\mathaxisheight\textfont2\fi\relax
>
>
> \ifcase#1\relax\or\lower\scratchdimen\or\or\raise\scratchdimen\fi\hbox\bgroup
>  \normalstartimath
>  \mathmatrixparameter\c!left
>  \vcenter{\unvbox\nextbox}%
>  \mathmatrixparameter\c!right
>  \normalstopimath
>\egroup}%
> \vbox}
>

Indeed, this is much better! Thank you!
I recommend to include this as a patch in ConTeXt.

However: Testing never stops ;-) I have the following MWE:

\definemathmatrix[pmatrix][left={\left(},right={\right)}]
\math{
  \startpmatrix
\NC A \NC B \NR
\NC C \NC D \NR
  \stoppmatrix}

This (including your suggested fix) results in the following structure tree:


|-
| '-
|   '-
| '-
|   '-
'-
  '-
|-
| |-
| | '-
| |   '-
| | '-
| |   '-"A"
| '-
|   '-
| '-
|   '-
| '-"B"
'-
  |-
  | '-
  |   '-
  | '-
  |   '-"C"
  '-
'-
  '-
'-
  '-"D"

I think that the  should be located within the , shouldn't
it?

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Tagging and Math Matrix

2017-09-06 Thread Christoph Reller
On Tue, 5 Sep 2017 16:29:52 +0200 Hans Hagen <pra...@wxs.nl>   wrote:

> On 8/30/2017 9:45 AM, Christoph Reller wrote:
> > On Mon, Dec 28, 2015 at 3:45 PM Christoph Reller
> > <christoph.rel...@gmail.com <mailto:christoph.rel...@gmail.com
> >>   wrote:
> >
> > There seems to be a problem with the structure information added
> > when using \startmatrix:
> >
> > A fix would be very much appreciated.
>
> should be ok now
>

Thank you Hans for this fix!

There seems to be, however, still a minor issue with a more complete MWE:
\math{
  \startmatrix
\NC A \NC B \NR
\NC C \NC D \NR
  \stopmatrix}

The resulting structure tree is as follows:

'-
  '-
'-
  '-
|-
| '-
|   |-
|   | '-
|   |   '-
|   | '-
|   |   '-"A"
|   '-
| '-
|   '-
| '-
|   '-"B"
|-(*)
|-
| '-
|   |-
|   | '-
|   |   '-
|   | '-
|   |   '-"C"
|   '-
| '-
|   '-
| '-
|   '-"D"
'-(*)

The elements marked with (*) are IMHO unnecessary. Do you agree?

Cheers
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Error with tagging and lohi alignment in table

2017-08-30 Thread Christoph Reller
On Wed, 30 Aug 2017 10:35:56 +0200 Hans Hagen <pra...@wxs.nl>  wrote:

> On 8/30/2017 9:22 AM, Christoph Reller wrote:
> > The following MWE now yields an error:
> >
> > \setuptagging[state=start]
> > \starttext
> > \bTABLE
> > \setupTABLE[c][1][align=lohi]
> >\bTR \bTD test \eTD \eTR
> > \eTABLE
> > \stoptext
> >
> > I'm afraid but this may be a bug. Many thanks in advance for all your
> > effort.
> fixed in next beta ... but move your \setupTABLE ine line up
>
Thank you, Hans, for the fix and for the hint!
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Tagging and Math Matrix

2017-08-30 Thread Christoph Reller
On Mon, Dec 28, 2015 at 3:45 PM Christoph Reller <christoph.rel...@gmail.com
>   wrote:

> There seems to be a problem with the structure information added when using
> \startmatrix:
>
> \setuptagging[state=start]
> \starttext
> \math{
>   \startmatrix
> \NC A \NR
> \NC B \NR
>   \stopmatrix}
> \stoptext
>
> The log reports an open chain: document>1 => mtr>1 => mtd>1 => mtr>2 =>
> mtd>2 => mtr>3
> This may be a bug.
>

This is clearly a bug. The resulting structure tree of the above MWE is as
follows (sorry for the ASCII art):


'-
  '-
|-
| '-
|   |-
|   | '-
|   |   |-
|   |   | '-
|   |   |   '-
|   |   | '-
|   |   |   |-
|   |   |   '-
|   |   '-
|   | '-
|   |   '-
|   | |-
|   | '-
|   '-
| '-
|   '-
| '-"B"
'-
  '-
'-
  '-"A"

A fix would be very much appreciated.
Thanks in advance,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Error with tagging and lohi alignment in table

2017-08-30 Thread Christoph Reller
Hi,

The following MWE now yields an error:

\setuptagging[state=start]
\starttext
\bTABLE
\setupTABLE[c][1][align=lohi]
  \bTR \bTD test \eTD \eTR
\eTABLE
\stoptext

I'm afraid but this may be a bug. Many thanks in advance for all your
effort.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Scite module and escape does not work anymore

2017-08-30 Thread Christoph Reller
On Tue, 29 Aug 2017 13:29:59 +0200 Hans Hagen <pra...@wxs.nl>   wrote:

> On 8/29/2017 9:31 AM, Christoph Reller wrote:
> > Hi,
> >
> > I noticed that the scite module (m-scite.mkiv) has undergone some
> > changes recently. When using this module to highlight source code, then
> > the escape mechanism does not seem to work anymore.
> >
> > Can this be fixed? Thank you in advance for your effort.
> i'll intercept it (there are no escapes in scite mode)
>
Oh, I see. Thank you, Hans.
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Scite module and escape does not work anymore

2017-08-29 Thread Christoph Reller
Hi,

I noticed that the scite module (m-scite.mkiv) has undergone some changes
recently. When using this module to highlight source code, then the escape
mechanism does not seem to work anymore.

MWE:
\enabletrackers[buffers.visualize]
\usemodule[scite]
\setuptyping[TEX][escape={[[,]]}]
\starttext
\startTEX
\test[[\em test]]
\stopTEX
\stoptext

The reported error is:
[ctxlua]:221: attempt to index local 'specification' (a nil value)
stack traceback:
[ctxlua]:221: in function <[ctxlua]:220>
[C]: in function 'lpegmatch'
...ext/tex/texmf-context/tex/context/base/mkiv/buff-ver.lua:283: in
function 'n'
...ext/tex/texmf-context/tex/context/base/mkiv/buff-ver.lua:511: in
function 'visualize'
...ext/tex/texmf-context/tex/context/base/mkiv/buff-ver.lua:760: in
function <...ext/tex/texmf-context/tex/context/base/mkiv/buff-ver.lua:752>
(...tail calls...)

Can this be fixed? Thank you in advance for your effort.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Log message "Unknown filter 'DCTDecode'"

2017-06-21 Thread Christoph Reller
On Mon, 19 Jun 2017 12:21:00 +0200 luigi scarso  wrote:

> With poppler 0.55,
> I am able to reproduce it with
>
> $ convert -size 100x100 radial-gradient:  rgradient.jpg; convert
> rgradient.jpg rgradient.pdf
> $ cat test.tex
>
> \starttext
> \externalfigure[rgradient.pdf]
> \stoptext
>
> Syntax Error (623): Unknown filter 'DCTDecode'
>
> I'm investigating
>
> --
> luigi
>

Thank you Luigi,

This error message is gone now. Sorry for the confusion I have created by
not having reported a well defined way to produce this message.

Cheers, Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Log message "Unknown filter 'DCTDecode'"

2017-06-16 Thread Christoph Reller
Hi,

In recent versions of ConTeXt/luatex, I observe the following log entry:

Syntax Error (77727): Unknown filter 'DCTDecode'

This happens if the document includes JPEG images, e.g:

\starttext
\externalfigure[hacker.jpg]
\stoptext

The output PDF looks, however, fine. Does this message have any
significance?

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] \setupinteraction[focus=standard] not working

2017-01-20 Thread Christoph Reller
Dear List,

First of all: Thank you Hans and folks for supporting focus=standard
for many things. There are, however, some major places where
focus=standard does not work correctly yet. I pick out the simplest
and in my opinion most severe one: Floats.

\setupexternalfigures[location={local,global,default}]
\setupinteraction[state=start, focus=standard]
\starttext
\about[figure].
\page
\placefigure[][figure]{Figure}{\externalfigure[cow.pdf]}
\page
\input tufte
\stoptext

The link text on page 1 in the resulting PDF correctly displays
"Figure" and the overlayed PDF annotation has a seemingly correct
destination "(figure)". But, in the PDF catalog's "Names"-tree the
only named destination present has the name "(#1)". This destination
points to the correct location on the correct page, it is only the
name that should read "(figure)" instead of "(#1)".

Please consider fixing at least this issue (even if you are not very
fond of focus=standard ;-), as it will be of tremendous value for many
users. If I can be of any help, then please let me know.

Regards,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] ntg-context Digest, Vol 151, Issue 18

2017-01-18 Thread Christoph Reller
On Tue, 17 Jan 2017 20:31:20 +0100, Hans Hagen  wrote:
>
> On 1/17/2017 8:13 PM, Henri Menke wrote:
>> Bump
>>
>> On 01/09/2017 01:49 PM, Henri Menke wrote:
>>> Dear list,
>>>
>>> I cannot seem to find the documentation for the parameters which you can 
>>> set in the first line of the document.  From an example I found that you 
>>> can select the engine this way.
>>>
>>> % engine=luajittex
>>> \starttext
>>> Hello World!
>>> \stoptext
>>>
>>> What other parameters can I set this way and what is the syntax to set 
>>> multiple parameters?
>>>
>>> Cheers,
>>> Henri
>
> engine
> synctex
> jiton
> jithash
> directives
> trackers
> experiments
> epub
> ctx|ctxfile
> interface
>
> plus for scite
>
> language
>

From what I know there is also:

macros

E.g.

% macros=mkvi

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] JPEG images resolution and externalfigure size

2017-01-12 Thread Christoph Reller
Hi,

When using the currently latest version of ConTeXt to include a JPEG
image as in the MWE below, the resulting image size in the PDF is half
the size when compared with earlier versions.

\setupexternalfigures[location={local,global,default}]
\starttext
\externalfigure[hacker.jpg][scale=1000]
\stoptext

The actual width (in the PDF) of the hacker.jpg image is:
- ConTeXt version 2016.12.28: approx. 44 mm
- ConTeXt version 2016.07.01: approx. 88 mm

The correct width would be 86.868 mm (513 pixel / 150 DPI * 25.4).

Is there a factor 2 lost somewhere?

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] floatcombination alignment has changed?

2017-01-04 Thread Christoph Reller
Hi,

I have come up with a simpler MWE which shows the problem more explicitly:

\setupcaptions[number=no]

\starttext

\startplacefigure[location=right]
  \startfloatcombination
\placefigure{A Cow}{\externalfigure[cow.pdf]}
\placefigure{Another Cow}{\externalfigure[cow.pdf]}
  \stopfloatcombination
\stopplacefigure
\input ward

\startplacefigure[location=right,title=A Single Cow]
  \externalfigure[cow.pdf]
\stopplacefigure
\input ward

\stoptext

In the latest version of ConTeXt, the floatcombination is shoved to
the left and overlaps the text which is also shoved to the left and
narrowed down to a minimum. The single figure, on the other hand, is
shoved correctly to the right and the text is at the left.

In earlier versions of ConTeXt, the floatcombination is correctly
shoved to the right. The reason for this change could be line 490 of
pack-com.mkiv (in the definition of \pack_combinations_start_float).
If I delete \dontleavehmode from this line then the correct layout is
restored.

Since I don't want to maintain my own version of ConTeXt, I very much
would appreciate If anyone could tell me how to get the correct layout
back, or fix this issue in ConTeXt.

Your effort is genuinely appreciated!

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] floatcombination alignment has changed?

2016-12-28 Thread Christoph Reller
Dear List,

Consider the following MWE:

\startplacefigure
  \startfloatcombination
\startplacetable[title={Table I}] % <- shifted
%\startplacetable   % <- not shifted
  \bTABLE
\bTR \bTD Foo \eTD \bTD Text. \eTD \eTR
  \eTABLE
\stopplacetable
\startplacetable[title={Table II}] % <- shifted
%\startplacetable% <- not shifted
  \bTABLE
  \bTR \bTD Foo \eTD \bTD Text. \eTD \eTR
  \eTABLE
\stopplacetable
  \stopfloatcombination
\stopplacefigure

The resulting output looks strange to me. The tables are shifted to
the left when compared with omitting the titles. In earlier versions
of ConTeXt, no such shift happens.

Do floatcombinations not work?

Any feedback is welcome.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] references.bookmarks.preroll and quotation

2016-12-20 Thread Christoph Reller
Hi,

I have the following MWE:

\setupinteraction[state=start]
\placebookmarks[chapter]
\enabledirectives[references.bookmarks.preroll]
\starttext
\startchapter[title=B \quotation{C} D]
  \input ward
\stopchapter
\stoptext

The generated bookmark has wrongly placed spaces:

B“ C ” D

Without the directive references.bookmarks.preroll, the bookmark is:

B "C" D

I need this directive because in titles I use macros that use
\autoinsertnextspace.

Is this a bug?

Any feedback is welcome.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] floatcombination alignment has changed?

2016-12-09 Thread Christoph Reller
On Thu, 08 Dec 2016 20:27:12 +0900, Jeong Dal  wrote:
> I don’t know how to put figures horizontally using “\startfloatcombination”.
> Is there any reason to use “\startfloatcombination”?

Dear Dalyoung,

Thank you for your feedback. Indeed, \startcombinantion produces
centered combinations by default.

The problem is, that within the combination I would like to use floats
defined with \setupfloat. This is not supported by \startcombination.

I noticed that line 490 of pack-com.mkiv has an added \dontleavehmode
in the definition of \pack_combinations_start_float. When deleting
this, the combination is centered. What is the reason for
\dontleavehmode here?

Is packing floats inside a floatcombination not recommended in general?

Any feedback is welcome

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] floatcombination alignment has changed?

2016-12-07 Thread Christoph Reller
Hi,

In recent versions of ConTeXt, floatcombinations are not placed centered by
default anymore. Consider the following MWE in which two cows are placed
side by side:

\placefigure{}{
  \startfloatcombination
\placefigure{}{\externalfigure[cow.pdf]}
\placefigure{}{\externalfigure[cow.pdf]}
  \stopfloatcombination}

In version 2016.07.01_16.28, the combination is placed horizontally. In the
latest version, the combination is flushed to the left.

Is this change by intention? If yes, could please anybody tell me how to
restore the previous behavior; changing the "location" does not help.

Thank you for your effort.

Cheers,

Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Nested modes and itemizations

2016-11-17 Thread Christoph Reller
On Thu, Nov 17, 2016 at 13:14:49 +0100 Hans Hagen <pra...@wxs.nl> wrote:

>
> On 11/17/2016 11:21 AM, Christoph Reller wrote:
> > Hi,
> >
> > I have the following minimal not-working example:
> >
> > \starttext
> > \startitemize
> > \item One
> >   \startmode[modeA]
> >   \item Two
> > \startitemize
> >   \startmode[modeB] % <- this
> >   \item Two A   % <- does
> >   \stopmode % <- not work
> >   % \doifmode{modeB}{\item Two A} % <- this works
> > \item Two B
> > \stopitemize
> >   \stopmode
> > \stopitemize
> > \stoptext
> >
> > Note that both modeA and modeB are not defined and hence not enabled.
> > When compiled with the latest version of ConTeXt MkIV, I get: Missing
> > number, treated as zero.
> > However, If I use the inline version \doifmode instead of the
> > environment version \startmode \stopmode, then the example compiles
> > without problem.
> >
> > I am afraid but this may be a bug.
>
> No, just the way tex parses, \stopmode is a delimiter so the inner
> \stopmode ends the outer \startmode.
>
> Using the \doif variable doesn't have that problem.
>
>
Oh, of course! Thank you and sorry for the noise.
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Nested modes and itemizations

2016-11-17 Thread Christoph Reller
Hi,

I have the following minimal not-working example:

\starttext
\startitemize
\item One
  \startmode[modeA]
  \item Two
\startitemize
  \startmode[modeB] % <- this
  \item Two A   % <- does
  \stopmode % <- not work
  % \doifmode{modeB}{\item Two A} % <- this works
\item Two B
\stopitemize
  \stopmode
\stopitemize
\stoptext

Note that both modeA and modeB are not defined and hence not enabled.
When compiled with the latest version of ConTeXt MkIV, I get: Missing
number, treated as zero.
However, If I use the inline version \doifmode instead of the environment
version \startmode \stopmode, then the example compiles without problem.

I am afraid but this may be a bug.

Cheers,
Christoph
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] TikZ node and color

2016-07-06 Thread Christoph Reller
On Tue, 5 Jul 2016 10:21:48 +0200, Hans Hagen <pra...@wxs.nl> wrote:
> On 7/5/2016 9:25 AM, Christoph Reller wrote:
>> Dear List,
>>
>> I use the latest version of ConTeXt and I have the following MWE:
>>
>> \usemodule[tikz]
>> \starttext
>>   \starttikzpicture
>> \node {\color[red]{red}};
>> \node[xshift=30] {\color[red]{not red}};
>>   \stoptikzpicture
>> \stoptext
>>
>> Can anybody tell me why the second node is not colored red?
>>
>> Aside: In LaTeX when using \color{red}{...} this tikzpicture renders
>> correctly. For LaTeX I use TikZ version 3.0.1a, in ConTeXt it seems to
>> be version 3.0.1.
>>
>> Any feedback is welcome.
>
> tikz has its own color mechanisms and they don't mix well with context
> color support so context probbably thinks it's still in red (so you need
> to force something non red in front)
>
> \starttikzpicture
>  \node {\color[red]{red}};
>  \node[xshift=30] {\zwnj\color[red]{not red}};
> \stoptikzpicture

Thank you Hans! This workaround does the job.

For those interested: The \zwnj can be prepended automatically to
every node by setting "every node/.add code=\zwnj". The updated MWE
now is:

\usemodule[tikz]
\tikzset{every node/.add code=\zwnj}
\starttext
  \starttikzpicture
\node {\color[red]{red}};
\node[xshift=30] {\color[red]{not red}};
  \stoptikzpicture
\stoptext

Cheers,
Christoph
___
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] TikZ node and color

2016-07-05 Thread Christoph Reller
Dear List,

I use the latest version of ConTeXt and I have the following MWE:

\usemodule[tikz]
\starttext
  \starttikzpicture
\node {\color[red]{red}};
\node[xshift=30] {\color[red]{not red}};
  \stoptikzpicture
\stoptext

Can anybody tell me why the second node is not colored red?

Aside: In LaTeX when using \color{red}{...} this tikzpicture renders
correctly. For LaTeX I use TikZ version 3.0.1a, in ConTeXt it seems to
be version 3.0.1.

Any feedback is welcome.

Regards,
Christoph
___
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] placetable with location=split produces error

2016-06-20 Thread Christoph Reller
>> Christoph Reller <mailto:christoph.rel...@gmail.com>
>> 16. Juni 2016 um 15:31
>> This is a long standing issue and I would very much appreciate any
>> comment on this.
> The problem has been fixed.
>
> Wolfgang

Indeed this error is gone now. Tausend Dank, Wolfgang!
Cheers,
Christoph
___
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
___

  1   2   >