[NTG-context] Re: bug tracker

[Hans Hagen via ntg-context]

On 5/27/2024 3:46 PM, Peter Münster wrote:


Is there a bug tracker for ConTeXt?
(It seems, that https://tracker.luatex.org/ is no more used...)
just mail to the list as bugs are normally either solved fast or becoem 
features


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 / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Bug or feature? \numexpression and hashes

[Hans Hagen via ntg-context]

On 9/4/2023 8:17 AM, Jairo A. del Rio wrote:

Hi, list. The following fails with a "Missing number, treated as zero"
error prompt:

\starttext
\expandedrepeat2{\expandedrepeat2{\the\numexpression#I+#P\relax\ }}
\stoptext

OTOH, \numexpr works seamlessly. Tested on ConTeXt 2023.09.03 19:03. Thanks
in advance.
bug or feature: just something not done yet (there are probably a few 
more places) ... i added it (no upload)


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: Bug between \definealternativestyle and makeup?

[Alex Leray]

Ouch, thanks for opening my eyes!

Le 27/08/23 à 21:42, Mikael Sundqvist a écrit :

Remove the period:

\definecharacterkerning [mykerning] [factor=0.15]
\definealternativestyle[mystyle][{\setcharacterkerning[mykerning]}]

\definemakeup [title] [doublesided=empty, pagestate=start]
\starttext
\starttitlemakeup
Title
\stoptitlemakeup
\stoptext

/Mikael

On Sun, Aug 27, 2023 at 9:32 PM Alex Leray  wrote:


Hi,

I found that using \definealternativestyle in conjunction with Makeup
insert a page before my Makeup page.

Any idea?

Thanks

* * *

\definecharacterkerning [mykerning] [factor=0.15]
\definealternativestyle[mystyle][{\setcharacterkerning[mykerning]}]. %%%
BUG!!!

\definemakeup [title] [doublesided=empty, pagestate=start]
\starttext
\starttitlemakeup
Title
\stoptitlemakeup
\stoptext
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___


--
Alexandre Leray
+32 487 947 030

Avez-vous pensé à (vous) offrir Médor ?
https://medor.coop/ideescadeau
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: Bug between \definealternativestyle and makeup?

[Mikael Sundqvist]

Remove the period:

\definecharacterkerning [mykerning] [factor=0.15]
\definealternativestyle[mystyle][{\setcharacterkerning[mykerning]}]

\definemakeup [title] [doublesided=empty, pagestate=start]
\starttext
\starttitlemakeup
Title
\stoptitlemakeup
\stoptext

/Mikael

On Sun, Aug 27, 2023 at 9:32 PM Alex Leray  wrote:
>
> Hi,
>
> I found that using \definealternativestyle in conjunction with Makeup
> insert a page before my Makeup page.
>
> Any idea?
>
> Thanks
>
> * * *
>
> \definecharacterkerning [mykerning] [factor=0.15]
> \definealternativestyle[mystyle][{\setcharacterkerning[mykerning]}]. %%%
> BUG!!!
>
> \definemakeup [title] [doublesided=empty, pagestate=start]
> \starttext
> \starttitlemakeup
> Title
> \stoptitlemakeup
> \stoptext
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
>
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] characters.tex.toutf bug

[Max Chernoff via ntg-context]

Hi Hans,

> it is more side effect of removing the (declared obsolete some years 
> ago) `` '' input which catched it later
> 
> i tend to remove
> 
>  for k, v in next, ligaturemapping do
>  hash[k] = v
>  end
>
> in favor of an explicit 'tquo' feature that one can enable if wanted
> 
> \definefontfeature[default][default][tlig=yes,tquo=yes,trep=yes]

That does make the output more consistent, but not in the way that I'm
wanting. My real code looks more like this:

   \definefontfeature[default][default][tlig=yes, tquo=yes, trep=yes]
   
   \startbuffer[test-bib]
   @article{one,
   author = {``Auth\v{o}r---One''},
   }
   @article{two,
   author = {``Authǒr---Two''},
   }
   \stopbuffer
   
   \usebtxdataset[test-bib.buffer]
   
   \startluacode
   for key, value in 
table.sortedpairs(publications.datasets.default.luadata) do
   print(key, publications.prerollcmdstring(value.author))
   end
   \stopluacode

publications.prerollcmdstring seems to run before any of the
replacements/ligatures, so with your fix I get this as the output:

   one ``Authǒr---One''
   two ``Authǒr---Two''
   
while with my suggested fix I get:

   one “Authǒr—One”
   two “Authǒr—Two”
   
I'm using a CLD document to convert a bunch of old .bib and .tex files into
Lua tables (which I'll then convert into XML). I can't modify any of the
input files, so I'll need to somehow deal with all the LaTeX-style input.
Using publications.prerollcmdstring + characters.tex.toutf seems like the
best way to do this, but I'm open to a different solution if you have any
suggestions.

Thanks,
-- Max
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] characters.tex.toutf bug

[Hans Hagen via ntg-context]

On 3/30/2023 7:57 AM, Max Chernoff via ntg-context wrote:

Hi Hans,

"characters.tex.toutf" only works if there is a backslash somewhere in
its input string. This leads to some really surprising behaviour in the
following example:

\definefontfeature[default][tlig=no, trep=no]

\startbuffer[test-bib]

@article{one,
author = {``Author---\v{O}ne''},
}
@article{two,
author = {``Author---Two''},
}
\stopbuffer

\usebtxdataset[test-bib.buffer]

\starttext

\placelistofpublications[method=dataset]
\stoptext

Removing the following lines

elseif not find(str,"\\",1,true) then
return str

from the definition of "characters.tex.toutf" in "char-tex.{lmt,lua}"

fixes this issue for me.
it is more side effect of removing the (declared obsolete some years 
ago) `` '' input which catched it later


i tend to remove

for k, v in next, ligaturemapping do
hash[k] = v
end

in favor of an explicit 'tquo' feature that one can enable if wanted

\definefontfeature[default][default][tlig=yes,tquo=yes,trep=yes]

\startbuffer[test-bib]
@article{one,
   author = {``Author---\v{O}ne''},
}
@article{two,
   author = {``Author---Two''},
}
@article{three,
   author = {Author---Two},
}
@article{three,
   author = {,,Author---Two''},
}
\stopbuffer

so I tested that with the above which seems to work.

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] characters.tex.toutf bug

[Max Chernoff via ntg-context]

Hi Hans,

"characters.tex.toutf" only works if there is a backslash somewhere in
its input string. This leads to some really surprising behaviour in the
following example:

   \definefontfeature[default][tlig=no, trep=no]
   
   \startbuffer[test-bib]
   @article{one,
   author = {``Author---\v{O}ne''},
   }
   @article{two,
   author = {``Author---Two''},
   }
   \stopbuffer
   
   \usebtxdataset[test-bib.buffer]
   
   \starttext
   \placelistofpublications[method=dataset]
   \stoptext

Removing the following lines

   elseif not find(str,"\\",1,true) then
   return str
   
from the definition of "characters.tex.toutf" in "char-tex.{lmt,lua}"
fixes this issue for me.

Thanks,
-- Max
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Minor bug in Lua or ConTeXt

[Pablo Rodriguez via ntg-context]

On 1/18/23 19:07, Hans Hagen via ntg-context wrote:
> On 1/18/2023 6:47 PM, Pablo Rodriguez via ntg-context wrote:
> [...] 
>> If I’m not wrong (in my previous statement), I think this is
>> counterintuitive, since undefined commands are fine in TeX comments and
>> undefined variables are fine inside \startluacode … \stopluacode.
>
> I bet you'd complain if \the\scratchdimen would not expand. You cannot 
> expect context to completely parse what goes into lua beforehand, unless 
> you are willing to get a performance hit (apart from a waste of time).

I’m starting to understand that one cannot have it all.

I haven’t used so much Lua code to add an undefined TeX command in a
comment.

Different reply isn’t wrong, only it needs to be known in advance.

> Thanks for adding to the wiki,

I have discovered after the addition that this was explained before
(last paragraph from
https://wiki.contextgarden.net/Programming_in_LuaTeX#Calling_Lua_from_TeX).

To emphasize it visually, I abused the  element.

If any wiki wizard knows better, please tell.

Many thanks for your help,

Pablo

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Minor bug in Lua or ConTeXt

[Hans Hagen via ntg-context]

On 1/18/2023 6:47 PM, Pablo Rodriguez via ntg-context wrote:


from what I understand is that undefined TeX commands cannot be added to
Lua comments.


Indeed. Of course we could have some 'ignore undefined command' feature 
but that cripples the engine as well as then also never gives warning in 
the case you *do* want to expand.



If I’m not wrong (in my previous statement), I think this is
counterintuitive, since undefined commands are fine in TeX comments and
undefined variables are fine inside \startluacode … \stopluacode.
I bet you'd complain if \the\scratchdimen would not expand. You cannot 
expect context to completely parse what goes into lua beforehand, unless 
you are willing to get a performance hit (apart from a waste of time).


And even if we'd make e.g. - active (with some lookahead magick) and 
then gobble till the end of the line we would get questions why it 
doesn't work in macros.


It's a small price to pay. (I also bet that Bruce is willing to \relax 
the command.)


Thanks for adding to the wiki,

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Minor bug in Lua or ConTeXt

[Pablo Rodriguez via ntg-context]

On 1/18/23 14:41, Bruce Horrocks via ntg-context wrote:
> […] 
> Perhaps the Wiki only needs to point out that if you get a Lua
> related error and the error log lists the entire contents of \startluacode ...
> \stopluacode then a possible source of the error is a \command somewhere
> in there?

Hi Bruce,

from what I understand is that undefined TeX commands cannot be added to
Lua comments.

If I’m not wrong (in my previous statement), I think this is
counterintuitive, since undefined commands are fine in TeX comments and
undefined variables are fine inside \startluacode … \stopluacode.

So I added
https://wiki.contextgarden.net/Programming_in_LuaTeX#Undefined_Commands_in_Lua_Comments.

Let me know whether I missed something.

Many thanks for your help,

Pablo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Minor bug in Lua or ConTeXt

[Bruce Horrocks via ntg-context]

Thanks Hans.

Before Pablo spends too much effort on the wiki it's worth pointing out that 
this only happened because I was in-line documenting the Lua function that I 
had written and wanted to name the ConTeXT macro that would invoke it - so it's 
trivial for me to avoid this error.

Perhaps the Wiki only needs to point out that if you get a Lua related error 
and the error log lists the entire contents of \startluacode ... \stopluacode 
then a possible source of the error is a \command somewhere in there?

Regards,


> On 18 Jan 2023, at 09:48, Hans Hagen via ntg-context  
> wrote:
> 
> On 1/18/2023 12:36 AM, Bruce Horrocks via ntg-context wrote:
>> ConTeXt  ver: 2023.01.04
>> The following MWE won't compile because of the \dummycommand line even 
>> though it is a comment. Not sure whether it's a minor bug or an unavoidable 
>> aspect of allowing embedded Lua.
>> \startluacode
>> -- \dummycommand
>> \stopluacode
>> \starttext
>> Hello
>> \stoptext
> 
> a bang-head-against-the-wall case:
> 
> \let\dummycommand\relax
> 
> \startluacode
> -- \dummycommand
> \stopluacode
> \starttext
> Hello
> \stoptext
> 
> or:
> 
> \ifdefined\dummycommand \else \let\dummycommand\relax \fi
> 
> a document-on-the-wiki challenge for Pablo
> 
> 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 / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___

—
Bruce Horrocks
Hampshire, UK

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Minor bug in Lua or ConTeXt

[Hans Hagen via ntg-context]

On 1/18/2023 12:36 AM, Bruce Horrocks via ntg-context wrote:

ConTeXt  ver: 2023.01.04

The following MWE won't compile because of the \dummycommand line even though 
it is a comment. Not sure whether it's a minor bug or an unavoidable aspect of 
allowing embedded Lua.

\startluacode
-- \dummycommand
\stopluacode
\starttext
Hello
\stoptext


a bang-head-against-the-wall case:

\let\dummycommand\relax

\startluacode
-- \dummycommand
\stopluacode
\starttext
Hello
\stoptext

or:

\ifdefined\dummycommand \else \let\dummycommand\relax \fi

a document-on-the-wiki challenge for Pablo

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Minor bug in Lua or ConTeXt

[Pablo Rodriguez via ntg-context]

On 1/18/23 00:36, Bruce Horrocks via ntg-context wrote:
> ConTeXt  ver: 2023.01.04
> 
> The following MWE won't compile because of the \dummycommand line
> even though it is a comment. Not sure whether it's a minor bug or an
> unavoidable aspect of allowing embedded Lua.

Hi Bruce,

I think your code should read:

  \startluacode
  -- \\dummycommand
  \stopluacode
  \starttext
  Hello
  \stoptext

BTW, in pure Lua:

  a = "\a"
  b = "\\b"
  print(a..b)

outputs "\b".

Sorry, I lack the knowledge to explain this, but backslash seems to be
an special char in pure Lua too.

Just in case it might help,

Pablo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Minor bug in Lua or ConTeXt

[Bruce Horrocks via ntg-context]

ConTeXt  ver: 2023.01.04

The following MWE won't compile because of the \dummycommand line even though 
it is a comment. Not sure whether it's a minor bug or an unavoidable aspect of 
allowing embedded Lua.

\startluacode
-- \dummycommand
\stopluacode
\starttext
Hello
\stoptext

—
Bruce Horrocks
Hampshire, UK

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Math bug (maybe) - prime

[Alan Braslau via ntg-context]

On Wed, 28 Dec 2022 08:26:24 +0100
Mikael Sundqvist via ntg-context  wrote:

> Note that the 2 sits higher in
> 
> \primed{a}^2
> 
> than it does in
> 
> (a')^2.
> 
> For readability, I really prefer the version with parentheses.

Certain Mathematical writing styles seek to minimize the use of
parenthesis ...

Now, the question is whether a prime is considered an exponent or
rather some sort of accent? One can ask the same question considering
other modifiers such as asterisk/star or even $\hat{a}$. Sometimes,
these can symbolize operators, in other cases they may indicate a
variant (as does prime).

I suspect that Context is currently treating $\primed{a}^2$ as
${a^{\prime}}^2$ (although, maybe the 2 is not made smaller?).

Aesthetically, should $x^2$ and $\hat{x}^2$ display any difference in
the placement of the exponent?

Alan

P.S. As a challenge, consider the following:
\chemical{^{14}_6C^*}
(a chiral carbon-14 atom).
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Math bug (maybe) - prime

[Mikael Sundqvist via ntg-context]

On Wed, Dec 28, 2022 at 5:58 AM Alan Braslau via ntg-context
 wrote:
>
> On Wed, 28 Dec 2022 00:27:39 +0100
> Hans Hagen via ntg-context  wrote:
>
> > What you can do is:
> >
> > $\primed{a}^2$
> >
> > which basically makes the prime an operation .. a small price to pay
> > for more robust handling of primes (also across fonts)
>
> I anticipated that (unicode) prime is a pain to handle, given that
> different fonts present it differently.
>
> $\primed{a}...$ is a very readable and reasonable solution (unlike
> \mathord{}, which seems to be a messy fix). I will learn and use that.
>
> Thank you!
>
> Alan
>
> P.S. inverting the order of the "exponents", if prime is some sort of
> exponent, was a surprising result.

Alan,

Note that the 2 sits higher in

\primed{a}^2

than it does in

(a')^2.

For readability, I really prefer the version with parentheses.

/Mikael
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Math bug (maybe) - prime

[Alan Braslau via ntg-context]

On Wed, 28 Dec 2022 00:27:39 +0100
Hans Hagen via ntg-context  wrote:

> What you can do is:
> 
> $\primed{a}^2$
> 
> which basically makes the prime an operation .. a small price to pay
> for more robust handling of primes (also across fonts)

I anticipated that (unicode) prime is a pain to handle, given that
different fonts present it differently.

$\primed{a}...$ is a very readable and reasonable solution (unlike
\mathord{}, which seems to be a messy fix). I will learn and use that.

Thank you!

Alan 

P.S. inverting the order of the "exponents", if prime is some sort of
exponent, was a surprising result.
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Math bug (maybe) - prime

[Hans Hagen via ntg-context]

On 12/27/2022 6:33 PM, Alan Braslau via ntg-context wrote:

MWE:

\starttext

$a^2′$

$a′^2$

$\mathord{a′}^2$

$a^*^2$

\stoptext


Should the \mathord{} be necessary to get the desired result?
(I would expect the second line to work, just like $a^*^2$.)

primes are kind of special and a pain in tex

- traditional tex sees them as superscripts and therefore expects soem 
active character and parsing magick for successive scripts
- that assumes a special way of havign these primes in the font (read: 
is it a text size thing already raised or a script one not yet raised)
- it also sort of spoils spacing (as one can end up with an empty 
nucleus inserted)

- in mkiv we use different magick than in mkii

anyway, in lmtx (luametatex) primes have been promoted to first class 
citizens which means that a nucleus can have


- super(post)script
- sub(post)script
- superprescript
- subprescript
- prime

and each comes with spacing and positioning properties cf opentype and 
our own additions for the pre/prime)


there is some magick wrt subscripts as these often are indices (which is 
why we have for instance ^^^ and ___ too)


What you can do is:

$\primed{a}^2$

which basically makes the prime an operation .. a small price to pay for 
more robust handling of primes (also across fonts)


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Math bug (maybe) - prime

[Alan Braslau via ntg-context]

MWE:

\starttext

$a^2′$

$a′^2$

$\mathord{a′}^2$

$a^*^2$

\stoptext


Should the \mathord{} be necessary to get the desired result?
(I would expect the second line to work, just like $a^*^2$.)

Alan
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Overbar bug

[Aditya Mahajan via ntg-context]

On Mon, 4 Jul 2022, Johann Birnick via ntg-context wrote:

> please have a look at the following example:
> 
> \starttext
> $\overbar{\alpha} \overbar{\beta}$
> \stoptext
> 
> The first one works just fine, whereas the second one looks very odd.
> (At least in MkIV...)
> 
> Any ideas?

I don't understand why you are using $\overbar$ in math mode. Do you want 
$\bar{\alpha}$ and $\bar{\beta}$?

Aditya
___
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] Overbar bug

[Johann Birnick via ntg-context]

Hey there,

please have a look at the following example:

\starttext
$\overbar{\alpha} \overbar{\beta}$
\stoptext

The first one works just fine, whereas the second one looks very odd.
(At least in MkIV...)

Any ideas?

Best,
Johann
___
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] ugly bug

[Hans Hagen via ntg-context]

On 6/3/2022 5:05 PM, Steffen Wolfrum via ntg-context wrote:




Am 02.06.2022 um 20:13 schrieb Wolfgang Schuster 
:

Steffen Wolfrum schrieb am 01.06.2022 um 14:03:

Hi,

several times I got problems with my publishing house when they noticed that 
the headerlines jump up and down on pages that end/begin with qoutes (i.e. 
smaller interlineskip), see example below: on page 1 the blackrule is about 1mm 
higher than on page 2.

In the past I then used really laborious workarounds to get these single pages 
in the correct way (without jumping)… manual pagebreak, re-define layout etc.

But as the pages are hard to find it would be better that the layout would be 
reliable consistent.

How can this be solved?


\defineinterlinespace[steffen][line=4.2ex]

\starttext

\dorecurse{2}{\samplefile{lorem}\par}

\start
%\setuplocalinterlinespace[line=4.2ex]% wrong header alignment
\setuplocalinterlinespace[steffen]% correct header alignment
\dorecurse{4}{\samplefile{lorem}\par}
\stop

\dorecurse{2}{\samplefile{lorem}\par}

\stoptext


the next upload tries to revert to the global setting in the pagebody

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
___

Re: [NTG-context] ugly bug

[Steffen Wolfrum via ntg-context]

> Am 02.06.2022 um 20:13 schrieb Wolfgang Schuster 
> :
> 
> Steffen Wolfrum schrieb am 01.06.2022 um 14:03:
>> Hi,
>> 
>> several times I got problems with my publishing house when they noticed that 
>> the headerlines jump up and down on pages that end/begin with qoutes (i.e. 
>> smaller interlineskip), see example below: on page 1 the blackrule is about 
>> 1mm higher than on page 2.
>> 
>> In the past I then used really laborious workarounds to get these single 
>> pages in the correct way (without jumping)… manual pagebreak, re-define 
>> layout etc.
>> 
>> But as the pages are hard to find it would be better that the layout would 
>> be reliable consistent.
>> 
>> How can this be solved?
> 
> \defineinterlinespace[steffen][line=4.2ex]
> 
> \starttext
> 
> \dorecurse{2}{\samplefile{lorem}\par}
> 
> \start
> %\setuplocalinterlinespace[line=4.2ex]% wrong header alignment
> \setuplocalinterlinespace[steffen]% correct header alignment
> \dorecurse{4}{\samplefile{lorem}\par}
> \stop
> 
> \dorecurse{2}{\samplefile{lorem}\par}
> 
> \stoptext


ok, this minimal example works.

but for other reasons (lots of heading with various vertical spaces)!) I also 
need \setuplayout[grid=tolerant]


\setuplayout[grid=tolerant]% this kills the smaller interlinespace

\defineinterlinespace[steffen][line=4.2ex]

\starttext

\dorecurse{2}{\samplefile{lorem}\par}

\start
%\setuplocalinterlinespace[line=4.2ex]% wrong header alignment
\setuplocalinterlinespace[steffen]% correct header alignment
\dorecurse{4}{\samplefile{lorem}\par}
\stop

\dorecurse{2}{\samplefile{lorem}\par}

\stoptext


Any idea how to preserve the smaller interlinespace?
Steffen
___
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] ugly bug

[Wolfgang Schuster via ntg-context]

Steffen Wolfrum schrieb am 01.06.2022 um 14:03:

Hi,

several times I got problems with my publishing house when they noticed that 
the headerlines jump up and down on pages that end/begin with qoutes (i.e. 
smaller interlineskip), see example below: on page 1 the blackrule is about 1mm 
higher than on page 2.

In the past I then used really laborious workarounds to get these single pages 
in the correct way (without jumping)… manual pagebreak, re-define layout etc.

But as the pages are hard to find it would be better that the layout would be 
reliable consistent.

How can this be solved?


\defineinterlinespace[steffen][line=4.2ex]

\starttext

\dorecurse{2}{\samplefile{lorem}\par}

\start
%\setuplocalinterlinespace[line=4.2ex]% wrong header alignment
\setuplocalinterlinespace[steffen]% correct header alignment
\dorecurse{4}{\samplefile{lorem}\par}
\stop

\dorecurse{2}{\samplefile{lorem}\par}

\stoptext

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] ugly bug

[Steffen Wolfrum via ntg-context]

Hi,

several times I got problems with my publishing house when they noticed that 
the headerlines jump up and down on pages that end/begin with qoutes (i.e. 
smaller interlineskip), see example below: on page 1 the blackrule is about 1mm 
higher than on page 2.

In the past I then used really laborious workarounds to get these single pages 
in the correct way (without jumping)… manual pagebreak, re-define layout etc.

But as the pages are hard to find it would be better that the layout would be 
reliable consistent.

How can this be solved?


Best wishes, Steffen

===

\setupbodyfont[palatino,9.5pt]\setupinterlinespace[13pt]

\setuppagenumbering [alternative=doublesided,location=]
\setupheader[strut=yes]
\setupheadertexts[text][][\blackrule]


\definepapersize[stw][width=17cm,height=24cm]
\setuppapersize[stw][stw]

\setuplayout
[width=122mm,
backspace=18mm,topspace=10mm,
header=7mm,headerdistance=5.969mm,
footer=5mm,footerdistance=5mm,height=214.031mm, 
location=middle]


\definedelimitedtext
[narrowtext]
[leftmargin=6mm,rightmargin=0mm]%,

\starttext

%%Test 1:
\dorecurse{6}{\input linden}

%%Test 2:
%\dorecurse{5}{\input tufte}


\start
\startdelimitedtext[narrowtext]
\switchtobodyfont[8pt]\setuplocalinterlinespace[line=11pt]
\input linden\par
\stopdelimitedtext
\stop

\stoptext

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Small bug in publ-imp-aps.mkvi

[Jack Hill via ntg-context]

Hi everyone,

Just letting you know that there is an extra . (full stop) on the end of
lines 732 and 734 of publ-imp-aps.mkvi which causes references to be
typeset like "p.. 417" and "pp.. 417--418".

Thanks,
Jack
___
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] A Bug in lmt_shade

[Hans Hagen]

On 5/6/2021 1:04 PM, Keith McKay wrote:

Hi all,

I think a bug has appeared in lmt_shade in the latest upload. MWE below.

more a genwral bug (side effect of changed helper) .. fixed in next upload

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
___

[NTG-context] A Bug in lmt_shade

[Keith McKay]

Hi all,

I think a bug has appeared in lmt_shade in the latest upload. MWE below.

Thanks

Keith McKay

%%

\setuppapersize[A4,landscape][A4,landscape]

\starttext

\startMPpage

StartPage;

width := PaperWidth ; height := PaperHeight ; unit := cm ;

definecolor [ name = "MyColor1", r = 0.781, g = 0.5, b = 0.5 ] ;

definecolor [ name = "MyColor3", r = 1, g = 1, b = 0.7983 ] ;

draw lmt_shade [

path = unitsquare xscaled width yscaled height,

direction = "up",

alternative = "linear",

colors = { "MyColor1", "MyColor3" },

] ;

StopPage;

\stopMPpage

\stoptext

%%%

%%% Console Output %%%

system >

system > ConTeXt ver: 2021.05.05 19:29 LMTX fmt: 2021.5.6 int: 
english/english


system >

< snip >

metapost > initializing instance 'metafun:1' using format 'metafun' and 
method 'default'


metapost > loading 'metafun' as 'metafun.mpxl' using method 'default'

metapost > initializing number mode 'scaled'

metafun > log >

metafun > log > error: An expression can't begin with 'right delimiter'

metafun > log >

metapost > log > 

metapost > log > 0

metapost > log > 

metapost > log > )

metapost > log >  
...enter_b,alternative,s;string.color_a,color_b,alternative,s;pair.center_a,center_b;alternative:=getparameter"alternative";mfun_with_shade_method_analyze(getparameter"path")


metapost > log > ;domain_min:...

metapost > log > 
image->begingroup.save.currentpicture;picture.currentpicture;currentpicture:=nullpicture;(TEXT3)


metapost > log > 
;currentpicture.if.str(SUFFIX2)<>"":shifted(mfun_labxf(SUFFIX2)*lrcorner.p+mfun_labyf(SUFFIX2)*ulcorn...


metapost > log > 
lmt_do_shade->...ve="circular":draw.fullcircle.scaled(radius_a)shifted.center_a.dashed.evenly;draw.fullcircle.scaled(factor*radius_b)shifted-center_b.dashed.evenly;fi.fi.popparameters;)


metapost > log > endgroup

metapost > log >  lmt_do_shade

metapost > log >

metapost > log > <*> ...3", r = 1, g = 1, b = 0.7983 ] ; draw lmt_shade 
[ path = unitsquare xscaled width yscaled height, direction = "up", 
alternative = "linear", colors = { "MyColor1", "MyColor3" }, ]


metafun > log >

metafun > log > I'm afraid I need some sort of value in order to 
continue, so I've tentatively


inserted '0'.

metafun > log >

metapost > log > ; StopPage; ;

metapost > log >

___
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] Another bug with ligature-blocking?

[Hans Hagen]

On 3/24/2021 8:20 PM, denis.ma...@ub.unibe.ch wrote:

-Ursprüngliche Nachricht-
Von: Hans Hagen 
Gesendet: Mittwoch, 24. März 2021 17:42
An: mailing list for ConTeXt users ; Maier, Denis
Christian (UB) 
Betreff: Re: [NTG-context] Another bug with ligature-blocking?

On 3/24/2021 4:48 PM, denis.ma...@ub.unibe.ch wrote:


\definefontfamily[times][rm][Times New Roman]

don't assume beforehand that something that doesn't work as expected is a
bug


Sorry, Hans, I didn't mean to be offensive.


it has more to do with searching for solutions using the subjects of 
mail ... in which case 'bug' is not a good one




the font just has no ligatures defined which you can remedy (in this
cae) with because it does have the glyphs

\startluacode
  fonts.handlers.otf.addfeature {
  name = "moreligatures",
  type = "ligature",
  data = {
  ['ff'] = { "f", "f" },
  ['fi'] = { "f", "i" },
  ['fl'] = { "f", "l" },
  }
  }
\stopluacode


\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
\definefontfamily[times][rm][Times New Roman]
\definefontfamily[termes[rm][TeX Gyre Termes]

\definefontfeature[default:block][default][blockligatures=yes]

\starttext

{\switchtobodyfont[times] \definedfont[Serif*default]begrifflich
ff fi fl\blank
\definedfont[Serif*default:block] begrifflich ff fi 
fl\blank}
{\switchtobodyfont[termes]\definedfont[Serif*default]begrifflich
ff fi fl\blank
\definedfont[Serif*default:block] begrifflich ff fi 
fl\blank}

\stoptext



I'm not sure I understand what is going on here. I thought \blockligatures 
simply means that instead of a ligature you'll have the regular glyphs in the 
output. Is that not correct?
sure but times doesn't have these ligatures (it has the shapes but not 
the features)


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
___

Re: [NTG-context] Another bug with ligature-blocking?

[denis.maier]

> -Ursprüngliche Nachricht-
> Von: Hans Hagen 
> Gesendet: Mittwoch, 24. März 2021 17:42
> An: mailing list for ConTeXt users ; Maier, Denis
> Christian (UB) 
> Betreff: Re: [NTG-context] Another bug with ligature-blocking?
> 
> On 3/24/2021 4:48 PM, denis.ma...@ub.unibe.ch wrote:
> 
> > \definefontfamily[times][rm][Times New Roman]
> don't assume beforehand that something that doesn't work as expected is a
> bug

Sorry, Hans, I didn't mean to be offensive.

> 
> the font just has no ligatures defined which you can remedy (in this
> cae) with because it does have the glyphs
> 
> \startluacode
>  fonts.handlers.otf.addfeature {
>  name = "moreligatures",
>  type = "ligature",
>  data = {
>  ['ff'] = { "f", "f" },
>  ['fi'] = { "f", "i" },
>  ['fl'] = { "f", "l" },
>  }
>  }
> \stopluacode
> 
> 
> \blockligatures[begrif:fl:ich]
> \definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
> \definefontfamily[times][rm][Times New Roman]
> \definefontfamily[termes[rm][TeX Gyre Termes]
> 
> \definefontfeature[default:block][default][blockligatures=yes]
> 
> \starttext
> 
> {\switchtobodyfont[times] \definedfont[Serif*default]begrifflich
> ff fi fl\blank
>\definedfont[Serif*default:block] begrifflich ff 
> fi fl\blank}
> {\switchtobodyfont[termes]\definedfont[Serif*default]begrifflich
> ff fi fl\blank
>\definedfont[Serif*default:block] begrifflich ff 
> fi fl\blank}
> 
> \stoptext
>

I'm not sure I understand what is going on here. I thought \blockligatures 
simply means that instead of a ligature you'll have the regular glyphs in the 
output. Is that not correct?

Denis
___
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] Another bug with ligature-blocking?

[Hans Hagen]

On 3/24/2021 4:48 PM, denis.ma...@ub.unibe.ch wrote:


\definefontfamily[times][rm][Times New Roman]
don't assume beforehand that something that doesn't work as expected is 
a bug


the font just has no ligatures defined which you can remedy (in this 
cae) with because it does have the glyphs


\startluacode
fonts.handlers.otf.addfeature {
name = "moreligatures",
type = "ligature",
data = {
['ff'] = { "f", "f" },
['fi'] = { "f", "i" },
['fl'] = { "f", "l" },
}
}
\stopluacode


\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
\definefontfamily[times][rm][Times New Roman]
\definefontfamily[termes[rm][TeX Gyre Termes]

\definefontfeature[default:block][default][blockligatures=yes]

\starttext

{\switchtobodyfont[times] \definedfont[Serif*default]begrifflich 
ff fi fl\blank
  \definedfont[Serif*default:block] 
begrifflich ff fi fl\blank}
{\switchtobodyfont[termes]\definedfont[Serif*default]begrifflich 
ff fi fl\blank
  \definedfont[Serif*default:block] 
begrifflich ff fi fl\blank}


\stoptext



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

[NTG-context] Another bug with ligature-blocking?

[denis.maier]

Hi,

I just ran into something strange with ligature blocking:

---
\blockligatures[begrif:fl:ich]

\definefontfeature[default][default][dlig=yes,liga=yes,]
\definefontfeature[default:block][default][blockligatures=yes]

\definefontfamily[times][rm][Times New Roman]
\definefontfamily[termes[rm][TeX Gyre Termes]

\starttext
\switchtobodyfont[times]
\definedfont[Serif*default]
begrifflich
\blank

\definedfont[Serif*default:block]
begrifflich


\switchtobodyfont[termes]
\definedfont[Serif*default]
begrifflich
\blank

\definedfont[Serif*default:block]
begrifflich

\stoptext
---

With  I'm getting < begriff|lich> when blockligatures is 
activated. Does anyone know what's going on there?

Best,
Denis
___
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] LMTX bug? \completelistofabbreviations

[Bert Verbeek]

Thanks,

this does the job for me

Kind Regards/Met vriendelijke groet,
Bert Verbeek

On 2/12/21 3:30 PM, Hans Hagen wrote:

for now put this in cont-new.mkxl:

\unprotect
\let\strc_synonyms_place_list\placelistofsynonyms
\protect



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

Re: [NTG-context] LMTX bug? \completelistofabbreviations

[Hans Hagen]

On 2/12/2021 2:37 PM, Bert Verbeek wrote:

Hello all,

I've used ConTeXt MkIV for years to make technical reports. For a new 
computer I looked for updates of the software and discovered LMTX. I ran 
it on my latest report and found an error on 
\completelistofabbreviations, both on win-64 and linux. Context --luatex 
worked fine.


A minimal file based on the wiki examples produced the same error on 
\completelistoftests:


\definesynonyms[test][tests][\infull]

\setupsynonyms[test][criterium=all]

\test{ITU}{International Telecommunication Union}
\test{MID}{Maritime Identification Digit}
\test{Ch}{Switzerland}

\starttext

The \ITU\ is an organisation in \infull{Ch}

% \subject{Short is nice}
% \placelistoftests
\completelistoftests

\stoptext

Did something change, or did I find a bug?

for now put this in cont-new.mkxl:

\unprotect
\let\strc_synonyms_place_list\placelistofsynonyms
\protect



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

[NTG-context] LMTX bug? \completelistofabbreviations

[Bert Verbeek]

Hello all,

I've used ConTeXt MkIV for years to make technical reports. For a new 
computer I looked for updates of the software and discovered LMTX. I ran 
it on my latest report and found an error on 
\completelistofabbreviations, both on win-64 and linux. Context --luatex 
worked fine.


A minimal file based on the wiki examples produced the same error on 
\completelistoftests:


\definesynonyms[test][tests][\infull]

\setupsynonyms[test][criterium=all]

\test{ITU}{International Telecommunication Union}
\test{MID}{Maritime Identification Digit}
\test{Ch}{Switzerland}

\starttext

The \ITU\ is an organisation in \infull{Ch}

% \subject{Short is nice}
% \placelistoftests
\completelistoftests

\stoptext

Did something change, or did I find a bug?

Bert



___
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] font bug in latest from 2021.01.29 19:44?

[Jairo A. del Rio]

It is fine again. Thank you a lot, Hans.

Jairo :)

El vie., 29 de ene. de 2021 5:48 p. m., Pablo Rodriguez 
escribió:

> On 1/29/21 11:24 PM, Hans Hagen wrote:
> > On 1/29/2021 9:59 PM, Pablo Rodriguez wrote:
> >
> >> Could anyone confirm this bug?
> > hm, some overload protection side effect ... i'll fix it
>
> Many thanks for the fix, Hans.
>
> Pablo
> --
> http://www.ousia.tk
>
> ___
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://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
___

Re: [NTG-context] font bug in latest from 2021.01.29 19:44?

[Pablo Rodriguez]

On 1/29/21 11:24 PM, Hans Hagen wrote:
> On 1/29/2021 9:59 PM, Pablo Rodriguez wrote:
>
>> Could anyone confirm this bug?
> hm, some overload protection side effect ... i'll fix it

Many thanks for the fix, Hans.

Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] font bug in latest from 2021.01.29 19:44?

[Hans Hagen]

On 1/29/2021 9:59 PM, Pablo Rodriguez wrote:


Could anyone confirm this bug?

hm, some overload protection side effect ... i'll fix it

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
___

Re: [NTG-context] font bug in latest from 2021.01.29 19:44?

[Jairo A. del Rio]

Math fonts are broken. In fact, even with compact fonts disabled, math
fonts aren't working properly.

Jairo

El vie, 29 de ene. de 2021 a la(s) 16:18, Jairo A. del Rio (
jairoadelr...@gmail.com) escribió:

> Same here. It compiles well when the math font definition is commentend.
> The error seems to be there:
>
> \setfontid
>
>
> 
>
> \3>mainface-12pt-mm-mr--1
>
>  \font_helpers_low_level_define_compact ...ec \empty \let
> \lastrawfontcall \relax \mutable \letcsname #2\endcsname \relax \else \edef
> \somefontspec {at \number \ETC.
>
>  \font_helpers_trigger_define ...\def \v_font_size_relative
> {#1}\def \v_font_size_absolute {#2}\font_helpers_low_level_define
> {#3}\v_font_identifier_class
>
> \csname \v_font_identifier_class \endcsname \setfalse \c_font_auto_size
> \ifskipfontcharacteristics \else \setfontcharacter...
>
>
>  \m_font_class_direction ...fcsname \??fontinstanceready \fontclass
> -\fontbody -\s!mm -\fontfamily \endcsname \settrue \c_font_auto_size
> \lastnamedcs
>
> \else \font_helpers_set_math_family_b \fi
>
>
>  \font_helpers_set_math_family_indeed_compact
> ..._family_set_scales_compact \let \mathsizesuffix \mathtextsuffix \let
> \fontface \!!plusone \font_helpers_set_math_family_a
>
> \textfont #1\font \font_helpers_set_math_family_a \textfont #1\font
> \scriptfont #1\font \scriptscriptfont #1\font \let \ma...
>
>
>  \font_helpers_set_math_family ...!mm -#2-\fontsize -1\endcsname
> \font_helpers_preset_math_family_indeed #1#2\else
> \font_helpers_set_math_family_indeed #1#2
>
> \fi \else \font_helpers_set_math_family_indeed #1#2\fi
>
> Jairo
>
> El vie, 29 de ene. de 2021 a la(s) 15:59, Pablo Rodriguez (oi...@gmx.es)
> escribió:
>
>> Dear list,
>>
>> this sample cannot be compiled with latest LMTX (2021.01.29 19:44).
>>
>>   \enableexperiments[fonts.compact]
>>
>>   \definefontfamily
>>   [mainface]
>>   [rm]
>>   [TeX Gyre Pagella]
>>
>>   \definefontfamily
>>   [mainface]
>>   [mm]
>>   [TeX Gyre Pagella Math]
>>
>>   \setupbodyfont
>>   [mainface, 12pt]
>>
>>   \starttext
>> \input zapf
>>   \stoptext
>>
>> I get the following error message:
>>
>>   I was looking for a control sequence whose current meaning
>>   has been defined by \font or a valid font id number.
>>   mtx-context | fatal error: return code: 256
>>
>> Previous latest from compiles the sample perfectly fine.
>>
>> Could anyone confirm this bug?
>>
>> Mamy thanks for your help,
>>
>> Pablo
>> --
>> http://www.ousia.tk
>>
>> ___
>> If your question is of interest to others as well, please add an entry to
>> the Wiki!
>>
>> maillist : ntg-context@ntg.nl /
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>> webpage  : http://www.pragma-ade.nl / http://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
___

Re: [NTG-context] font bug in latest from 2021.01.29 19:44?

[Jairo A. del Rio]

Same here. It compiles well when the math font definition is commentend.
The error seems to be there:

\setfontid




\3>mainface-12pt-mm-mr--1

 \font_helpers_low_level_define_compact ...ec \empty \let
\lastrawfontcall \relax \mutable \letcsname #2\endcsname \relax \else \edef
\somefontspec {at \number \ETC.

 \font_helpers_trigger_define ...\def \v_font_size_relative {#1}\def
\v_font_size_absolute {#2}\font_helpers_low_level_define
{#3}\v_font_identifier_class

\csname \v_font_identifier_class \endcsname \setfalse \c_font_auto_size
\ifskipfontcharacteristics \else \setfontcharacter...


 \m_font_class_direction ...fcsname \??fontinstanceready \fontclass
-\fontbody -\s!mm -\fontfamily \endcsname \settrue \c_font_auto_size
\lastnamedcs

\else \font_helpers_set_math_family_b \fi


 \font_helpers_set_math_family_indeed_compact
..._family_set_scales_compact \let \mathsizesuffix \mathtextsuffix \let
\fontface \!!plusone \font_helpers_set_math_family_a

\textfont #1\font \font_helpers_set_math_family_a \textfont #1\font
\scriptfont #1\font \scriptscriptfont #1\font \let \ma...


 \font_helpers_set_math_family ...!mm -#2-\fontsize -1\endcsname
\font_helpers_preset_math_family_indeed #1#2\else
\font_helpers_set_math_family_indeed #1#2

\fi \else \font_helpers_set_math_family_indeed #1#2\fi

Jairo

El vie, 29 de ene. de 2021 a la(s) 15:59, Pablo Rodriguez (oi...@gmx.es)
escribió:

> Dear list,
>
> this sample cannot be compiled with latest LMTX (2021.01.29 19:44).
>
>   \enableexperiments[fonts.compact]
>
>   \definefontfamily
>   [mainface]
>   [rm]
>   [TeX Gyre Pagella]
>
>   \definefontfamily
>   [mainface]
>   [mm]
>   [TeX Gyre Pagella Math]
>
>   \setupbodyfont
>   [mainface, 12pt]
>
>   \starttext
> \input zapf
>   \stoptext
>
> I get the following error message:
>
>   I was looking for a control sequence whose current meaning
>   has been defined by \font or a valid font id number.
>   mtx-context | fatal error: return code: 256
>
> Previous latest from compiles the sample perfectly fine.
>
> Could anyone confirm this bug?
>
> Mamy thanks for your help,
>
> Pablo
> --
> http://www.ousia.tk
>
> ___
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://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] font bug in latest from 2021.01.29 19:44?

[Pablo Rodriguez]

Dear list,

this sample cannot be compiled with latest LMTX (2021.01.29 19:44).

  \enableexperiments[fonts.compact]

  \definefontfamily
  [mainface]
  [rm]
  [TeX Gyre Pagella]

  \definefontfamily
  [mainface]
  [mm]
  [TeX Gyre Pagella Math]

  \setupbodyfont
  [mainface, 12pt]

  \starttext
\input zapf
  \stoptext

I get the following error message:

  I was looking for a control sequence whose current meaning
  has been defined by \font or a valid font id number.
  mtx-context | fatal error: return code: 256

Previous latest from compiles the sample perfectly fine.

Could anyone confirm this bug?

Mamy thanks for your help,

Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Strange bug with obayspaces and tagging

[Hans Hagen]

On 11/26/2020 10:47 AM, Christoph Reller wrote:

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.

i'll fix it

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

[NTG-context] Strange bug with obayspaces and tagging

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

Re: [NTG-context] bizarre bug in xml

[Thomas A. Schmitz]

On 11/21/20 11:04 AM, Wolfgang Schuster wrote:
To check whether a stretch or shrink value is set LMTX takes a look at 
the next character (p, P, m or M) before it makes a decision, when you 
have now a word after \hskip which start with one of these characters 
(e.g. Materiam) you trigger the scanner which fails because it didn't 
find a keyword. To avoid such problems always add \relax after the last 
value of \hskip, this is even explained in one of the exercises in the 
TeXbook.


Thank you Wolfgang, now it all makes sense. I will relax more and dust 
off my copy of the TeXbook. I used to read small chapters in the tramway 
on my way to the university, but with the lockdown, I didn't have this 
opportunity. Nah, just kidding, I haven't looked at it in a long time.


Thomas
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] bizarre bug in xml

[Wolfgang Schuster]

Thomas A. Schmitz schrieb am 20.11.2020 um 22:57:


On 11/20/20 10:52 PM, Wolfgang Schuster wrote:
Optional arguments (e.g. plus/minus values for \hskip) for commands 
are handled different in LMTX but it was always recommended to add 
\relax after the last value.


Thank you Wolfgang, that makes the file indeed compile again! Any 
explanation for the strange behavior of the error?


In LMTX the order of the plus and minus values of \hskip can be written 
in any order and it's even possible to set them multiple times (try the 
example below with LuaTeX and LMTX).


To check whether a stretch or shrink value is set LMTX takes a look at 
the next character (p, P, m or M) before it makes a decision, when you 
have now a word after \hskip which start with one of these characters 
(e.g. Materiam) you trigger the scanner which fails because it didn't 
find a keyword. To avoid such problems always add \relax after the last 
value of \hskip, this is even explained in one of the exercises in the 
TeXbook.


\starttext

a\hskip 1cm plus 5mm minus 5mm b

a\hskip 1cm minus 5mm plus 5mm b

a\hskip 1cm pLuS 5mm MiNuS 5mm b

a\hskip 1cm plus 5mm minus 5mm plus 1cm b

\stoptext

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
___

Re: [NTG-context] bizarre bug in xml

[Hans Hagen]

On 11/21/2020 2:09 AM, Pablo Rodriguez wrote:

On 11/20/20 10:52 PM, Wolfgang Schuster wrote:

[...]
Optional arguments (e.g. plus/minus values for \hskip) for commands are
handled different in LMTX but it was always recommended to add \relax
after the last value.


Hi Wolfgang,

the same would apply to \vskip, wouldn’t it?
also for \hrule and \vrule (and in pdftex/luatex some backend related 
primitives); primitives like \hbox have their keyword scan terminated by 
a leftbrace token


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
___

Re: [NTG-context] bizarre bug in xml

[Pablo Rodriguez]

On 11/20/20 10:52 PM, Wolfgang Schuster wrote:
> [...]
> Optional arguments (e.g. plus/minus values for \hskip) for commands are
> handled different in LMTX but it was always recommended to add \relax
> after the last value.

Hi Wolfgang,

the same would apply to \vskip, wouldn’t it?

Many thanks for your help,

Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] bizarre bug in xml

[Wolfgang Schuster]

Thomas A. Schmitz schrieb am 20.11.2020 um 22:44:


Hi all,

this is the most bizarre bug I've ever seen in context. I would be 
grateful if others could try to replicate it. Test file:


\startbuffer[test]

     Materiam vati da Venus alma tuo.

\stopbuffer

\startxmlsetups xml:testsetups
     \xmlsetsetup{#1}{*}{-}
 \xmlsetsetup{#1}{document|
     hskip}{xml:*}
\stopxmlsetups

\xmlregistersetup{xml:testsetups}

\startxmlsetups xml:document
    \xmlflush{#1}
\stopxmlsetups

\startxmlsetups xml:hskip
 \hskip\xmlatt{#1}{width}


\hskip\xmlatt{#1}{width}\relax


The file compiles cleanly if I give the --luatex switch.

Now for the bizarre part: if you delete the capital M of "Materiam" or 
replace it by any other capital letter, the file compiles. What's going 
on here?


Optional arguments (e.g. plus/minus values for \hskip) for commands are 
handled different in LMTX but it was always recommended to add \relax 
after the last value.


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] bizarre bug in xml

[Thomas A. Schmitz]

Hi all,

this is the most bizarre bug I've ever seen in context. I would be 
grateful if others could try to replicate it. Test file:


\startbuffer[test]

Materiam vati da Venus alma tuo.

\stopbuffer

\startxmlsetups xml:testsetups
\xmlsetsetup{#1}{*}{-}
\xmlsetsetup{#1}{document|
hskip}{xml:*}
\stopxmlsetups

\xmlregistersetup{xml:testsetups}

\startxmlsetups xml:document
   \xmlflush{#1}
\stopxmlsetups

\startxmlsetups xml:hskip
\hskip\xmlatt{#1}{width}
\stopxmlsetups

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

This gives an error with the latest lmtx (2020.11.19 11:28, linux 64 bit):

tex error   > tex error on line 10 in file ./xmltest.tex: Valid 
keyword expected, likely 'minus'



 Ma
teriam vati da Venus alma tuo.
 \22>:xml:document #1->\xmlflush {#1}

 }


 \22>:xml:process #1->\xmlregistereddocumentsetups 
{#1}{#1}\xmlmain {#1}



 \lxml_process ...ocument {#3}#2{#3}{#4}\setcatcodetable 
\notcatcodes \doifelsenothing {#5}{\xmlsetup 
{#3}{xml:process}}{\xmlsetup {#3}{#5}}

\endgroup

 \xmlprocessbuffer{main}{test}{}

The file compiles cleanly if I give the --luatex switch.

Now for the bizarre part: if you delete the capital M of "Materiam" or 
replace it by any other capital letter, the file compiles. What's going 
on here?


Thanks, and all best

Thomas
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Table-bug in lmtx?

[Christian Prim]

Hello Hans

many thanks for the fix!

Christian

Am Mo., 30. März 2020 um 22:45 Uhr schrieb Hans Hagen :

> On 3/30/2020 6:23 PM, Christian Prim wrote:
> > Hello list
> >
> > following MWE gives a strange error "(interwoven alignment preambles are
> > not allowed)" when processed with lmtx:
> >
> > \definetabletemplate[fosa][s0|xp(3.5cm)|lw(0.7cm)|xp(5cm)s2|lw(2.5cm)|]
> > \starttext
> > \starttable[fosa]
> > \NC Cell 1 \NC\Use3[p(8cm)]{A longer cell}\NC\AR
> > \MR
> > \NC Cell 1 \NC Cell 2 \NC Cell 3 \NC Cell 4 \NC\AR
> > \stoptable
> > \stoptext
> >
> > No problems in mkiv.
> > I think Use3 is the problem, but I'm not sure...
> I found the issue (in the engine) ... tomorrow I'll upload a new one.
>
> 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
___

Re: [NTG-context] Table-bug in lmtx?

[Hans Hagen]

On 3/30/2020 6:23 PM, Christian Prim wrote:

Hello list

following MWE gives a strange error "(interwoven alignment preambles are 
not allowed)" when processed with lmtx:


\definetabletemplate[fosa][s0|xp(3.5cm)|lw(0.7cm)|xp(5cm)s2|lw(2.5cm)|]
\starttext
\starttable[fosa]
\NC Cell 1 \NC\Use3[p(8cm)]{A longer cell}\NC\AR
\MR
\NC Cell 1 \NC Cell 2 \NC Cell 3 \NC Cell 4 \NC\AR
\stoptable
\stoptext

No problems in mkiv.
I think Use3 is the problem, but I'm not sure...

I found the issue (in the engine) ... tomorrow I'll upload a new one.

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
___

Re: [NTG-context] Table-bug in lmtx?

[Wolfgang Schuster]

Christian Prim schrieb am 30.03.2020 um 18:23:

Hello list

following MWE gives a strange error "(interwoven alignment preambles are 
not allowed)" when processed with lmtx:


\definetabletemplate[fosa][s0|xp(3.5cm)|lw(0.7cm)|xp(5cm)s2|lw(2.5cm)|]
\starttext
\starttable[fosa]
\NC Cell 1 \NC\Use3[p(8cm)]{A longer cell}\NC\AR
\MR
\NC Cell 1 \NC Cell 2 \NC Cell 3 \NC Cell 4 \NC\AR
\stoptable
\stoptext

No problems in mkiv.
I think Use3 is the problem, but I'm not sure...


No, the problem is when you set a width for a cell.

\starttext

\starttable[|w(3cm)|]
\NC Cell \NC\SR
\stoptable

\stoptext

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] Table-bug in lmtx?

[Christian Prim]

Hello list

following MWE gives a strange error "(interwoven alignment preambles are
not allowed)" when processed with lmtx:

\definetabletemplate[fosa][s0|xp(3.5cm)|lw(0.7cm)|xp(5cm)s2|lw(2.5cm)|]
\starttext
\starttable[fosa]
\NC Cell 1 \NC\Use3[p(8cm)]{A longer cell}\NC\AR
\MR
\NC Cell 1 \NC Cell 2 \NC Cell 3 \NC Cell 4 \NC\AR
\stoptable
\stoptext

No problems in mkiv.
I think Use3 is the problem, but I'm not sure...

Many thanks for your help
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
___

[NTG-context] \bTABLE bug, please help !

[Taco Hoekwater]

Hi,

Please see the attached example. The \bTABLE in the footer of the page 
‘inherits' the
first line of the split \bTABLE in the running text. I have no idea how to fix 
this
or why this even happens. Help!

I’ll need a way to work around this problem in my current ConTeXt installation 
for
this project. That is now nearly 4 years old, but the same bug is still happens 
with
a new beta of mkiv.

I cannot switch to \startxtable because I would need \startembeddedxtable, and 
that
has way too many limitations to be useful in this project.

Best wishes,
Taco




test.pdf
Description: Adobe PDF document


test.tex
Description: Binary data




___
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] 'lua.registercode' bug in latest beta

[Hans Hagen]

On 11/26/2017 3:05 PM, Marco Patzer wrote:

On Tue, 7 Nov 2017 11:59:51 +0800
Li Yanrui (李延瑞)  wrote:


Using '\ctxloadluafile'  can get an error:

```
..ext/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:50: bad
argument #1 to 'gmatch' (string expected, got nil)
```

It seems to be caused by 'if options ~= ""' in `lua.registercode'.
That empyt string should be 'nil'?


that line should be:

if type(options) == "string" and options ~= "" then


I can confirm the issue, MWE:

\usemodule [letter]
\starttext
\null
\stoptext

throws:

open source > level 4, order 5, name 
'/tmp/ctx/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.mkvi'

lua error   > lua error on line 30 in file 
/tmp/ctx/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.mkvi:

...ctx/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:50: bad argument #1 
to 'gmatch' (string expected, got nil)
stack traceback:
[C]: in function 'gmatch'
...ctx/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:50: in 
function 'registercode'
[ctxlua]:1: in main chunk

>

20 %C MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
21 %C GNU General Public License for more details.
22 %C
23 %C You should have received a copy of the GNU General Public License
24 %C along with this program.  If not, see .
25
26 \unprotect
27
28 % Lua functions for the core and also for the frontend modules
29
30 >>  \ctxloadluafile{s-cor-00}

context: 2017.11.22 13:35

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




--

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

Re: [NTG-context] 'lua.registercode' bug in latest beta

[Marco Patzer]

On Tue, 7 Nov 2017 11:59:51 +0800
Li Yanrui (李延瑞)  wrote:

> Using '\ctxloadluafile'  can get an error:
> 
> ```
> ..ext/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:50: bad
> argument #1 to 'gmatch' (string expected, got nil)
> ```
> 
> It seems to be caused by 'if options ~= ""' in `lua.registercode'.
> That empyt string should be 'nil'?

I can confirm the issue, MWE:

\usemodule [letter]
\starttext
\null
\stoptext

throws:

open source > level 4, order 5, name 
'/tmp/ctx/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.mkvi'

lua error   > lua error on line 30 in file 
/tmp/ctx/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.mkvi:

...ctx/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:50: bad argument #1 
to 'gmatch' (string expected, got nil)
stack traceback:
[C]: in function 'gmatch'
...ctx/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:50: in 
function 'registercode'
[ctxlua]:1: in main chunk

20 %C MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
21 %C GNU General Public License for more details.
22 %C
23 %C You should have received a copy of the GNU General Public License
24 %C along with this program.  If not, see .
25 
26 \unprotect
27 
28 % Lua functions for the core and also for the frontend modules
29 
30 >>  \ctxloadluafile{s-cor-00}

context: 2017.11.22 13:35

Marco
___
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] 'lua.registercode' bug in latest beta

[Henning Hraban Ramm]

Am 2017-11-07 um 08:14 schrieb Henning Hraban Ramm :

> Am 2017-11-07 um 04:59 schrieb Li Yanrui (李延瑞) :
> 
>> Hi,
>> 
>> Using '\ctxloadluafile'  can get an error:
>> 
>> ```
>> ..ext/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:50: bad argument 
>> #1 to 'gmatch' (string expected, got nil)
>> ```
> 
> Same here:
> 
> lua error   > lua error on line 30 in file 
> /Users/hraban/Library/texmf/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.mkvi:
> 
> ...xmf/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:47: bad argument 
> #1 to 'gmatch' (string expected, got nil)
> stack traceback:
>   [C]: in function 'gmatch'
>   ...xmf/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:47: in 
> function 'registercode'
>   [ctxlua]:1: in main chunk
> 
> 20 %C MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> 21 %C GNU General Public License for more details.
> 22 %C
> 23 %C You should have received a copy of the GNU General Public License
> 24 %C along with this program.  If not, see 
> .
> 25 
> 26 \unprotect
> 27 
> 28 % Lua functions for the core and also for the frontend modules
> 29 
> 30 >>  \ctxloadluafile{s-cor-00}
> 
> 
> 
>> It seems to be caused by 'if options ~= ""' in `lua.registercode'. That 
>> empyt string should be 'nil'?
> 
> Yep, after 'context --make' that lets it work for me.
> Thank you!


Why is this still not fixed? It’s so easy, but I don’t like to patch it after 
every update again!

Please change "" to nil in 
tex/texmf-context/tex/context/base/mkiv/luat-cod.lua, line 49!

Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD

___
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] 'lua.registercode' bug in latest beta

[Henning Hraban Ramm]

Am 2017-11-07 um 04:59 schrieb Li Yanrui (李延瑞) :

> Hi,
> 
> Using '\ctxloadluafile'  can get an error:
> 
> ```
> ..ext/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:50: bad argument 
> #1 to 'gmatch' (string expected, got nil)
> ```

Same here:

lua error   > lua error on line 30 in file 
/Users/hraban/Library/texmf/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.mkvi:

...xmf/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:47: bad argument #1 
to 'gmatch' (string expected, got nil)
stack traceback:
[C]: in function 'gmatch'
...xmf/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:47: in 
function 'registercode'
[ctxlua]:1: in main chunk

20 %C MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
21 %C GNU General Public License for more details.
22 %C
23 %C You should have received a copy of the GNU General Public License
24 %C along with this program.  If not, see .
25 
26 \unprotect
27 
28 % Lua functions for the core and also for the frontend modules
29 
30 >>  \ctxloadluafile{s-cor-00}



> It seems to be caused by 'if options ~= ""' in `lua.registercode'. That empyt 
> string should be 'nil'?

Yep, after 'context --make' that lets it work for me.
Thank you!

Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD

___
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] 'lua.registercode' bug in latest beta

[李延瑞]

Hi,

Using '\ctxloadluafile'  can get an error:

```
..ext/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:50: bad argument
#1 to 'gmatch' (string expected, got nil)
```

It seems to be caused by 'if options ~= ""' in `lua.registercode'. That
empyt string should be 'nil'?

-- 
Best regards,

Li Yanrui (李延瑞)
___
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 bug not setting up blank spaces

[Hans Hagen]

On 2/14/2017 7:17 PM, Pablo Rodriguez wrote:

On 02/14/2017 06:41 PM, Hans Hagen wrote:

[...]
I don’t understand why \setupblank[ab][big] doesn’t work (with a
previous \defineblank[ab]).

I mean, for most elements \setupelement is possible after \defineelement.

What is different with \setupblank?


Well, you cannot

\definecolor[red][r=1]

\setupcolor[red][r=.5]

either. Adapting a blank this way would also be inefficient because then
we need to keep carry around more state info and all these relatively
basic core macro are tuned for efficiency


Many thanks for your reply, Hans.

Is there anything wrong in defining the same blank again?


not that know of


I need to add special blanks in templates. In some documents, those
blanks will be bigger than in other ones. Is there anything wrong in
redefining in the second documents the blanks I previously defined in
the template?

Many thanks for your help,

Pablo




--

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

Re: [NTG-context] defining bug not setting up blank spaces

[Pablo Rodriguez]

On 02/14/2017 06:41 PM, Hans Hagen wrote:
>> [...]
>> I don’t understand why \setupblank[ab][big] doesn’t work (with a
>> previous \defineblank[ab]).
>>
>> I mean, for most elements \setupelement is possible after \defineelement.
>>
>> What is different with \setupblank?
> 
> Well, you cannot
> 
> \definecolor[red][r=1]
> 
> \setupcolor[red][r=.5]
> 
> either. Adapting a blank this way would also be inefficient because then 
> we need to keep carry around more state info and all these relatively 
> basic core macro are tuned for efficiency

Many thanks for your reply, Hans.

Is there anything wrong in defining the same blank again?

I need to add special blanks in templates. In some documents, those
blanks will be bigger than in other ones. Is there anything wrong in
redefining in the second documents the blanks I previously defined in
the template?

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] defining bug not setting up blank spaces

[Hans Hagen]

On 2/14/2017 5:27 PM, Pablo Rodriguez wrote:

On 02/14/2017 01:13 PM, Hans Hagen wrote:

On 2/13/2017 9:16 PM, Pablo Rodriguez wrote:

Dear list,

I have the following sample:

\defineblank[ab][none]
\starttext
\defineblank[ab][big]
a
\blank[ab]
b
\stoptext

Am I missing something or is there a reason to force the new definition
(instead of the setup) of already defined blank spaces?

I mean, if this isn’t a bug, I don’t see the gain in this behavior.


?


Hans,

I don’t understand why \setupblank[ab][big] doesn’t work (with a
previous \defineblank[ab]).

I mean, for most elements \setupelement is possible after \defineelement.

What is different with \setupblank?


Well, you cannot

\definecolor[red][r=1]

\setupcolor[red][r=.5]

either. Adapting a blank this way would also be inefficient because then 
we need to keep carry around more state info and all these relatively 
basic core macro are tuned for efficiency


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
___

Re: [NTG-context] defining bug not setting up blank spaces

[Pablo Rodriguez]

On 02/14/2017 01:13 PM, Hans Hagen wrote:
> On 2/13/2017 9:16 PM, Pablo Rodriguez wrote:
>> Dear list,
>>
>> I have the following sample:
>>
>> \defineblank[ab][none]
>> \starttext
>> \defineblank[ab][big]
>> a
>> \blank[ab]
>> b
>> \stoptext
>>
>> Am I missing something or is there a reason to force the new definition
>> (instead of the setup) of already defined blank spaces?
>>
>> I mean, if this isn’t a bug, I don’t see the gain in this behavior.
> 
> ?

Hans,

I don’t understand why \setupblank[ab][big] doesn’t work (with a
previous \defineblank[ab]).

I mean, for most elements \setupelement is possible after \defineelement.

What is different with \setupblank?

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] defining bug not setting up blank spaces

[Hans Hagen]

On 2/13/2017 9:16 PM, Pablo Rodriguez wrote:

Dear list,

I have the following sample:

\defineblank[ab][none]
\starttext
\defineblank[ab][big]
a
\blank[ab]
b
\stoptext

Am I missing something or is there a reason to force the new definition
(instead of the setup) of already defined blank spaces?

I mean, if this isn’t a bug, I don’t see the gain in this behavior.


?


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

[NTG-context] defining bug not setting up blank spaces

[Pablo Rodriguez]

Dear list,

I have the following sample:

\defineblank[ab][none]
\starttext
\defineblank[ab][big]
a
\blank[ab]
b
\stoptext

Am I missing something or is there a reason to force the new definition
(instead of the setup) of already defined blank spaces?

I mean, if this isn’t a bug, I don’t see the gain in this behavior.

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] (another) bug with embeddedxtables

[Wolfgang Schuster]

Michael Eidenbenz 
2. Dezember 2016 um 12:40
Settings made to \startembeddedxtable or \startxrow they will only 
work in the first call of the macro.

In every further call the settings are ignored.

On the other hand, settings made to \startxcell work for every call of 
the macro.


I assume this is a bug.

tabl-xtb.mkvi:

\unexpanded\def\tabl_x_embedded_start[#settings]#content\stopembeddedxtable
- {\tabl_x_prepare{#settings}%
-  
\clf_assignbuffer{embedded_x_table}{\detokenize{#content}}\catcodetable\relax
+ 
{\clf_assignbuffer{embedded_x_table}{\detokenize{#content}}\catcodetable\relax

   \bgroup
+  \tabl_x_prepare{#settings}%
   \let\tabl_x_start_table\tabl_x_process_buffer
   \edef\tabl_x_current_buffer{embedded_x_table}%
   \tabl_x_process}

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] (another) bug with embeddedxtables

[Michael Eidenbenz]

Settings made to \startembeddedxtable or \startxrow they will only work in the 
first call of the macro.
In every further call the settings are ignored.

On the other hand, settings made to \startxcell work for every call of the 
macro.

I assume this is a bug.

Regards Michael


\unexpanded\def\Table#1{%
  \startembeddedxtable[height=5cm]
  \startxrow
\startxcell #1 \stopxcell
  \stopxrow
\stopembeddedxtable
}

\unexpanded\def\TableCell#1{%
  \startembeddedxtable
  \startxrow
\startxcell[height=5cm] #1 \stopxcell
  \stopxrow
\stopembeddedxtable
}

\starttext
\Table{height is 5cm}
\Table{height should be 5cm}
\TableCell{height is 5cm}
\TableCell{height is 5cm}
\stoptext
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Henri Menke]

I got it working using the patch below.  One has to rebuild the format using

context --make; contextjit --make; mtxrun --script plain --make; mtxrunjit 
--script plain --make

for the changes to take effect.


--- typo-brk.lua2016-10-12 11:15:31.769189346 +0200
+++ typo-brk.lua2016-10-12 11:16:16.897979419 +0200
@@ -272,6 +272,7 @@
 if map then
 local cmap = map[char]
 if cmap then
+setattr(current,a_breakpoints,unsetvalue) -- should 
not be needed
 -- for now we collect but when found ok we can move 
the handler here
 -- although it saves nothing in terms of performance
 local lang = getfield(current,"lang")
@@ -301,7 +302,6 @@
 else
 current = getnext(current)
 end
-setattr(start,a_breakpoints,unsetvalue) -- should not 
be needed
 else
 current = getnext(current)
 end


On 10/11/2016 03:45 PM, Mojca Miklavec wrote:
> On 11 October 2016 at 15:33, Henri Menke wrote:
>> On 10/10/2016 03:59 PM, Mojca Miklavec wrote:
>>> On 10 October 2016 at 15:31, Henri Menke wrote:
 I have found another thread reporting the same problem

 https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html

 However, Hans only replied with »has been fixed already«.

 Does anyone know how to find the fix?
>>>
>>> Unless Hans remembers what he fixed exactly, my only idea is doing a
>>> bisection over
>>> https://bitbucket.org/phg/context-mirror/commits/all
>>
>> Okay.  This does not make *any* sense!  I started merging files until the 
>> bug disappeared and it happened when I merged cont-new.mkiv.  The diff is
>>
>> -\newcontextversion{2016.05.17 10:06}
>> +\newcontextversion{2016.07.01 16:28}
>>
>> So this is basically the version number.  Can someone enlighten me what is 
>> going on?
> 
> I would suspect that changing the version number triggers regenerating
> the formats. Most likely one of the other files fixed the problem, but
> the problem only disappeared once you regenerated the format. That's
> pure guesswork though.
> 
> Mojca
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___
> 

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Otared Kavian]

On 11 Oct 2016, at 15:58, Henri Menke  wrote:
>> […]
> 
> I have to correct myself, it just looked like it worked.  It didn't generate 
> the PDF due to
> 
> Fatal Error > Your format does not match the base files!
> 
> The search continues.

Hi Henri,

The error is indeed extremely bizarre, and maybe funny, but if you want just to 
find a temporary solution in order to finish your project, it seems that adding 
a special word (or maybe something else…) allows the typesetting of your file. 

I tried the following modification of your sample with ConTeXt  ver: 2016.05.17 
19:20 (and LuaTeX Version 0.95.0) from TeX Live 2016.
The file name is bizarre-error.tex (if there no hyphen in the file name 
everything is allright).
It compiles both with the latest beta in standalone ConTeXt, as well as with 
the stable one from TeXLive 2016.

It is important to have a blank line before the line containing «  
\phantom{Junior} ».
If I remove the line «  \phantom{Junior} » then the file does not compile with 
the version of ConTeXt from TeXLive… (but it does with the latest beta)
If I replace it with the word « Junior », again it compiles fine. 
However if I replace that line with «  \phantom{Bizarre} » or even the word « 
Bizarre », the file does not compile :-)
But if your replace it with « Bizarre \phantom{Junior} » or with « 
\phantom{Bizarre} \phantom{Junior} » it compiles again…

All this seems funny to me, but I understand that it might stress you!

Best regards: OK

% begin bizarre-error.tex
\version[temporary]

\setbreakpoints[compound]

\setuppagenumbering[alternative=doublesided]

\starttext

\startstandardmakeup
\stopstandardmakeup

{\em Detailtypografie} by Friedrich Frossman 

\phantom{Junior}

\stoptext
% end bizarre-error.tex
___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[luigi scarso]

On Tue, Oct 11, 2016 at 3:58 PM, Henri Menke  wrote:
> I have to correct myself, it just looked like it worked.  It didn't generate 
> the PDF due to
>
> Fatal Error > Your format does not match the base files!
>
> The search continues.

To be sure, just give
context --make ; contextjit --make ;mtxrun --script plain --make ;
mtxrunjit --script plain --make
every time you change something (ie new version of luatex , luajittex
, context and so on)

-- 
luigi
___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Henri Menke]

On 10/11/2016 03:45 PM, Mojca Miklavec wrote:
> On 11 October 2016 at 15:33, Henri Menke wrote:
>> On 10/10/2016 03:59 PM, Mojca Miklavec wrote:
>>> On 10 October 2016 at 15:31, Henri Menke wrote:
 I have found another thread reporting the same problem

 https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html

 However, Hans only replied with »has been fixed already«.

 Does anyone know how to find the fix?
>>>
>>> Unless Hans remembers what he fixed exactly, my only idea is doing a
>>> bisection over
>>> https://bitbucket.org/phg/context-mirror/commits/all
>>
>> Okay.  This does not make *any* sense!  I started merging files until the 
>> bug disappeared and it happened when I merged cont-new.mkiv.  The diff is
>>
>> -\newcontextversion{2016.05.17 10:06}
>> +\newcontextversion{2016.07.01 16:28}
>>
>> So this is basically the version number.  Can someone enlighten me what is 
>> going on?
> 
> I would suspect that changing the version number triggers regenerating
> the formats. Most likely one of the other files fixed the problem, but
> the problem only disappeared once you regenerated the format. That's
> pure guesswork though.

I have to correct myself, it just looked like it worked.  It didn't generate 
the PDF due to

Fatal Error > Your format does not match the base files!

The search continues.

> 
> Mojca
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___
> 

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Arthur Reutenauer]

> Okay.  This does not make *any* sense!  I started merging files until the bug 
> disappeared and it happened when I merged cont-new.mkiv.  The diff is
> 
> -\newcontextversion{2016.05.17 10:06}
> +\newcontextversion{2016.07.01 16:28}
> 
> So this is basically the version number.  Can someone enlighten me what is 
> going on?

  You missed the actual change and your dichotomy resulted in a
meaningless diff.  This often happens when trying to detect “offending”
changes in a large code base.

  I can’t be sure, of course, but that seems more likely than a version
bump introducing the bug you reported.  Have you actually observed that
precisely this change caused the bug?

Best,

Arthur
___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Mojca Miklavec]

On 11 October 2016 at 15:33, Henri Menke wrote:
> On 10/10/2016 03:59 PM, Mojca Miklavec wrote:
>> On 10 October 2016 at 15:31, Henri Menke wrote:
>>> I have found another thread reporting the same problem
>>>
>>> https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html
>>>
>>> However, Hans only replied with »has been fixed already«.
>>>
>>> Does anyone know how to find the fix?
>>
>> Unless Hans remembers what he fixed exactly, my only idea is doing a
>> bisection over
>> https://bitbucket.org/phg/context-mirror/commits/all
>
> Okay.  This does not make *any* sense!  I started merging files until the bug 
> disappeared and it happened when I merged cont-new.mkiv.  The diff is
>
> -\newcontextversion{2016.05.17 10:06}
> +\newcontextversion{2016.07.01 16:28}
>
> So this is basically the version number.  Can someone enlighten me what is 
> going on?

I would suspect that changing the version number triggers regenerating
the formats. Most likely one of the other files fixed the problem, but
the problem only disappeared once you regenerated the format. That's
pure guesswork though.

Mojca
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Henri Menke]

On 10/10/2016 03:59 PM, Mojca Miklavec wrote:
> On 10 October 2016 at 15:31, Henri Menke wrote:
>> I have found another thread reporting the same problem
>>
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html
>>
>> However, Hans only replied with »has been fixed already«.
>>
>> Does anyone know how to find the fix?
> 
> Unless Hans remembers what he fixed exactly, my only idea is doing a
> bisection over
> https://bitbucket.org/phg/context-mirror/commits/all

Okay.  This does not make *any* sense!  I started merging files until the bug 
disappeared and it happened when I merged cont-new.mkiv.  The diff is

-\newcontextversion{2016.05.17 10:06}
+\newcontextversion{2016.07.01 16:28}

So this is basically the version number.  Can someone enlighten me what is 
going on?

> 
> In case you find the fix, I can "backport" it to TL's repository and
> users doing regular upgrades with tlmgr will get it at least.
> 
> Mojca
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___
> 

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Henri Menke]

On 10/10/2016 03:59 PM, Mojca Miklavec wrote:
> On 10 October 2016 at 15:31, Henri Menke wrote:
>> I have found another thread reporting the same problem
>>
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html
>>
>> However, Hans only replied with »has been fixed already«.
>>
>> Does anyone know how to find the fix?
> 
> Unless Hans remembers what he fixed exactly, my only idea is doing a
> bisection over
> https://bitbucket.org/phg/context-mirror/commits/all

Okay, I have identified the relevant commit to be da91490 [1].  Unfortunately, 
the diff to the TL 2016 version which is something like af172a8 [2] is huge.  I 
was not yet able to identify the change which fixed the bug.  Also I have no 
idea what to look out for.  So far I have just been looking for occurrences of 
setattr and the like.

[1] 
https://bitbucket.org/phg/context-mirror/commits/da9149010f4d34eef23a504682d82cdcf4fac8f5?at=beta
[2] 
https://bitbucket.org/phg/context-mirror/commits/af172a8db5f7583d0117635edde17eba5619d883?at=beta

> 
> In case you find the fix, I can "backport" it to TL's repository and
> users doing regular upgrades with tlmgr will get it at least.
> 
> Mojca
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___
> 

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Henri Menke]

On 10/10/2016 03:59 PM, Mojca Miklavec wrote:
> On 10 October 2016 at 15:31, Henri Menke wrote:
>> I have found another thread reporting the same problem
>>
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html
>>
>> However, Hans only replied with »has been fixed already«.
>>
>> Does anyone know how to find the fix?
> 
> Unless Hans remembers what he fixed exactly, my only idea is doing a
> bisection over
> https://bitbucket.org/phg/context-mirror/commits/all

I'm willing to bisect it but I don't know how to integrate the git repo into 
the standalone distribution.  Are there instructions somewhere?

> 
> In case you find the fix, I can "backport" it to TL's repository and
> users doing regular upgrades with tlmgr will get it at least.
> 
> Mojca
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___
> 

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Mojca Miklavec]

On 10 October 2016 at 15:31, Henri Menke wrote:
> I have found another thread reporting the same problem
>
> https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html
>
> However, Hans only replied with »has been fixed already«.
>
> Does anyone know how to find the fix?

Unless Hans remembers what he fixed exactly, my only idea is doing a
bisection over
https://bitbucket.org/phg/context-mirror/commits/all

In case you find the fix, I can "backport" it to TL's repository and
users doing regular upgrades with tlmgr will get it at least.

Mojca
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Henri Menke]

I have found another thread reporting the same problem

https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html

However, Hans only replied with »has been fixed already«.

Does anyone know how to find the fix?

Cheers, Henri

On 10/10/2016 02:03 PM, Thomas A. Schmitz wrote:
> On 10/10/2016 01:49 PM, Henri Menke wrote:
>> Dear Thomas,
>>
>> does it also compile on latest beta when there is a hyphen in the filename?  
>> BTW, the example can be simplified a little by just using 
>> \setbreakpoints[compound] instead of my complicated hyphen thing (Updated 
>> example is below.).  Also I'm very sure that it is mainly related to the 
>> breakpoints thing.
>>
>> As I mentioned in the original post, I currently cannot update because of 
>> critical documents being composed with the TL 2016 version and I cannot 
>> afford any regressions.
>>
>> Cheers, Henri
> 
> Yes, I had saved your file as test-test.tex, and it compiles with 2016.10.08 
> 00:11
> 
> Thomas
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Ulrike Fischer]

Am Mon, 10 Oct 2016 13:49:47 +0200 schrieb Henri Menke:

> does it also compile on latest beta when there is a hyphen in the filename?

Works fine for me with 
system  > ConTeXt  ver: 2016.10.08 00:11 MKIV beta  fmt:
2016.10.10  int: english/english

and a file "test-error.tex".


Btw: Your error report reminded me a miktex bug last year, where
everyone thought the hyphen was responsable but at the end it was
the length of file names (multiple of 9 broke) which naturally
changes is one remove the hyphen ...

-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Thomas A. Schmitz]

On 10/10/2016 01:49 PM, Henri Menke wrote:

Dear Thomas,

does it also compile on latest beta when there is a hyphen in the filename?  
BTW, the example can be simplified a little by just using 
\setbreakpoints[compound] instead of my complicated hyphen thing (Updated 
example is below.).  Also I'm very sure that it is mainly related to the 
breakpoints thing.

As I mentioned in the original post, I currently cannot update because of 
critical documents being composed with the TL 2016 version and I cannot afford 
any regressions.

Cheers, Henri


Yes, I had saved your file as test-test.tex, and it compiles with 
2016.10.08 00:11


Thomas
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Henri Menke]

Dear Thomas,

does it also compile on latest beta when there is a hyphen in the filename?  
BTW, the example can be simplified a little by just using 
\setbreakpoints[compound] instead of my complicated hyphen thing (Updated 
example is below.).  Also I'm very sure that it is mainly related to the 
breakpoints thing.

As I mentioned in the original post, I currently cannot update because of 
critical documents being composed with the TL 2016 version and I cannot afford 
any regressions.

Cheers, Henri

---

\version[temporary]

\setbreakpoints[compound]

\setuppagenumbering[alternative=doublesided]

\starttext

\startstandardmakeup
\stopstandardmakeup

{\em Detailtypografie} by Friedrich Frossman

\stoptext

On 10/10/2016 12:31 PM, Thomas A. Schmitz wrote:
> On 10/10/2016 12:14 PM, Henri Menke wrote:
>> Dear list,
>>
>> at some point my document started throwing an error
>>
>> ! error:  (nodes): trying to delete an attribute reference of a non 
>> attribute node
>>
>> I managed to extract a minimal example which shows the error (below).  
>> However, the error only occurs when the filename of the document contains a 
>> hyphen!  When I save the document as `test-error.tex' the error comes up, 
>> when I save it as `testerror.tex' it typesets smoothly.
>>
>> Unfortunately, I currently cannot update to latest beta because I have an 
>> important document where I cannot afford any regressions.
>>
>> Cheers, Henri
> 
> Hi Henri,
> 
> I can confirm that running context tl 2016 (2016.05.17 19:20) on your example 
> triggers this error; the same file compiles cleanly with the current beta. 
> Not sure if this is good news or bad news for you...
> 
> Thomas
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Paranormal bug in TL 2016

[Thomas A. Schmitz]

On 10/10/2016 12:14 PM, Henri Menke wrote:

Dear list,

at some point my document started throwing an error

! error:  (nodes): trying to delete an attribute reference of a non attribute 
node

I managed to extract a minimal example which shows the error (below).  However, 
the error only occurs when the filename of the document contains a hyphen!  
When I save the document as `test-error.tex' the error comes up, when I save it 
as `testerror.tex' it typesets smoothly.

Unfortunately, I currently cannot update to latest beta because I have an 
important document where I cannot afford any regressions.

Cheers, Henri


Hi Henri,

I can confirm that running context tl 2016 (2016.05.17 19:20) on your 
example triggers this error; the same file compiles cleanly with the 
current beta. Not sure if this is good news or bad news for you...


Thomas
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] Paranormal bug in TL 2016

[Henri Menke]

Dear list,

at some point my document started throwing an error

! error:  (nodes): trying to delete an attribute reference of a non attribute 
node

I managed to extract a minimal example which shows the error (below).  However, 
the error only occurs when the filename of the document contains a hyphen!  
When I save the document as `test-error.tex' the error comes up, when I save it 
as `testerror.tex' it typesets smoothly.

Unfortunately, I currently cannot update to latest beta because I have an 
important document where I cannot afford any regressions.

Cheers, Henri

---

\version[temporary]

\definebreakpoints[hyphen]
\definebreakpoint [hyphen] [-] [nleft=3,nright=3,type=6,range=yes]
\setbreakpoints[hyphen]

\setuppagenumbering [alternative=doublesided]

\starttext

\startstandardmakeup
\stopstandardmakeup

{\em Detailtypografie} by Friedrich Frossman

\stoptext
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] RTL bug in textbackground

[Hans Hagen]

On 7/3/2016 6:46 PM, Mohammad Hossein Bateni wrote:

Hello,

When using \definetextbackground in RTL setting, the boundaries are not
determined correctly (both for location=paragraph and location=text) and
colors gets messed up.

Here a sort-of-minimal example adapted from details.pdf.  Is there any
particular keys I should use in RTL to fix the issue?


\setupcolors[state=start]
\definecolor[infogray][s=0.5]
\definecolor[textgray][s=0.8]

\definetextbackground[intro]
 [backgroundcolor=infogray,
   backgroundoffset=.25cm,
   offset=.5cm,
   frame=on,framecolor=red,
   location=paragraph,
   color=white]

\definetextbackground[subintro]
 [backgroundcolor=textgray,
   backgroundoffset=0pt,
   offset=0pt,
   frame=off,
   location=text,
   color=blue]

\starttext

\starttextbackground[intro]
A rather common way to draw attention to a passage, is to add
a background. In this chapter we will therefore discuss how
to enhance your document with \starttextbackground [subintro]
colorful areas that either or not follow the shape of your
paragraph. \stoptextbackground\ Be warned: this chapter has
so many backgrounds that you should consider wearing sunglasses.
\stoptextbackground

\blank[3*big]

\righttoleft
\starttextbackground[intro]
A rather common way to draw attention to a passage, is to add
a background. In this chapter we will therefore discuss how
to enhance your document with \starttextbackground [subintro]
colorful areas that either or not follow the shape of your
paragraph. \stoptextbackground\ Be warned: this chapter has
so many backgrounds that you should consider wearing sunglasses.
\stoptextbackground
\stoptext


I think i fixed it (no upload yet) but this kind of tricky things 
probably need some time to get sorted out.


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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] RTL bug in textbackground

[Mohammad Hossein Bateni]

Hello,

When using \definetextbackground in RTL setting, the boundaries are not
determined correctly (both for location=paragraph and location=text) and
colors gets messed up.

Here a sort-of-minimal example adapted from details.pdf.  Is there any
particular keys I should use in RTL to fix the issue?


\setupcolors[state=start]
\definecolor[infogray][s=0.5]
\definecolor[textgray][s=0.8]

\definetextbackground[intro]
 [backgroundcolor=infogray,
   backgroundoffset=.25cm,
   offset=.5cm,
   frame=on,framecolor=red,
   location=paragraph,
   color=white]

\definetextbackground[subintro]
 [backgroundcolor=textgray,
   backgroundoffset=0pt,
   offset=0pt,
   frame=off,
   location=text,
   color=blue]

\starttext

\starttextbackground[intro]
A rather common way to draw attention to a passage, is to add
a background. In this chapter we will therefore discuss how
to enhance your document with \starttextbackground [subintro]
colorful areas that either or not follow the shape of your
paragraph. \stoptextbackground\ Be warned: this chapter has
so many backgrounds that you should consider wearing sunglasses.
\stoptextbackground

\blank[3*big]

\righttoleft
\starttextbackground[intro]
A rather common way to draw attention to a passage, is to add
a background. In this chapter we will therefore discuss how
to enhance your document with \starttextbackground [subintro]
colorful areas that either or not follow the shape of your
paragraph. \stoptextbackground\ Be warned: this chapter has
so many backgrounds that you should consider wearing sunglasses.
\stoptextbackground
\stoptext


Thanks,
MHB
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] writebetweenlist bug?

[Hans Hagen]

On 5/19/2016 5:39 PM, mass...@fastwebnet.it wrote:

Hello list,
I'm experimenting with the table of contents and I found a strange behaviour of 
writebetweenlist.
Try this:

\setuphead[chapter][number=no]

\starttext

\placecontent

\chapter{chapter 1}
\chapter{chapter 2}
\writebetweenlist[chapter]{\blank Why am I not between chapter 2 and chapter 3?}
\chapter{chapter 3}
\chapter{chapter 4}

\stoptext

I exptected the text of \writebetweenlist to fall between chapters 2 and 3, but 
it falls between chapters 1 and 2.
Is that right or is it a bug?


\writebetweenlist
  [chapter]
  [location=here]
  {\blank Why am I not between chapter 2 and chapter 3?}

but beware: that introduces a node (which can interfere with spacing) so 
best attach it to content


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] writebetweenlist bug?

[massifr]

Hello list,
I'm experimenting with the table of contents and I found a strange behaviour of 
writebetweenlist.
Try this:

\setuphead[chapter][number=no]

\starttext

\placecontent

\chapter{chapter 1}
\chapter{chapter 2}
\writebetweenlist[chapter]{\blank Why am I not between chapter 2 and chapter 3?}
\chapter{chapter 3}
\chapter{chapter 4}

\stoptext

I exptected the text of \writebetweenlist to fall between chapters 2 and 3, but 
it falls between chapters 1 and 2.
Is that right or is it a bug?

Best greetings,
Massi
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Strange bug in the latest version of ConTeXt - start-stop table problem

[Jaroslav Hajtmar]

Thanx Wolfgang for the correction of my code. This error is probably 
more than 8 years old (inside predefined macros in any old library 
code). ConTeXt was all existing time generously tolerant for my bug :-).


One more thanx for their fix.

Jaroslav Hajtmar



Dne 01.05.16 v 9:50 Wolfgang Schuster napsal(a):

Jaroslav Hajtmar 
1. Mai 2016 um 07:52
Thanx Wolfgang for reply.
I looked for possible mistakes in my library, and finally I find out 
that described error that bug is reflecting when I use \starttable 
--- \stoptable environment. I am sending now an minimal example that 
illustrates the problem. I am aware that work with tables of this 
type is not recommended, however, I was surprised that in a previous 
version of standalone ConTeXt the bug did not show. Is there any 
changes in code, which is related with tables typing?


Thanks Jaroslav Hajtmar

Here is minimal example:



\starttext

\starttable[|l w50mm|c|]

You forgot the braces around the cell width:

\starttable[|lw(50mm)|c|]

\NC \NC {\bf } \MR

1. You forgot the \NC after the last cell.

2. You don’t need the braces for the font switch because font changes 
are always local to a cell.


\NC \NC \bf  \NC\MR

Wolfgang


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Strange bug in the latest version of ConTeXt - start-stop table problem

[Wolfgang Schuster]

Jaroslav Hajtmar 
1. Mai 2016 um 07:52
Thanx Wolfgang for reply.
I looked for possible mistakes in my library, and finally I find out 
that described error that bug is reflecting when I use \starttable --- 
\stoptable environment. I am sending now an minimal example that 
illustrates the problem. I am aware that work with tables of this type 
is not recommended, however, I was surprised that in a previous 
version of standalone ConTeXt the bug did not show. Is there any 
changes in code, which is related with tables typing?


Thanks Jaroslav Hajtmar

Here is minimal example:



\starttext

\starttable[|l w50mm|c|]

You forgot the braces around the cell width:

\starttable[|lw(50mm)|c|]

\NC \NC {\bf } \MR

1. You forgot the \NC after the last cell.

2. You don’t need the braces for the font switch because font changes 
are always local to a cell.


\NC \NC \bf  \NC\MR

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Strange bug in the latest version of ConTeXt - start-stop table problem

[Jaroslav Hajtmar]

Thanx Wolfgang for reply.
I looked for possible mistakes in my library, and finally I find out 
that described error that bug is reflecting when I use \starttable --- 
\stoptable environment. I am sending now an minimal example that 
illustrates the problem. I am aware that work with tables of this type 
is not recommended, however, I was surprised that in a previous version 
of standalone ConTeXt the bug did not show. Is there any changes in 
code, which is related with tables typing?


Thanks Jaroslav Hajtmar

Here is minimal example:



\starttext

\starttable[|l w50mm|c|]
\NC \NC {\bf } \MR
\NC \NC XXX \MR
\stoptable


\stoptext




Dne 27.04.16 v 12:22 Wolfgang Schuster napsal(a):

Jaroslav Hajtmar 
26. April 2016 um 16:02
Hello ConTeXist.

I have just installed the latest version of ConTeXt standalone. When 
I compiled an my old source code, I received an error:



! You can't use `\Ustopmath' in restricted horizontal mode! You can't 
use `\Ustopmath' in restricted horizontal mode! You can't use 
`\Ustartmath' in restricted horizontal mode! Inline math should end 
with \Ustopmath



This strange error is caused something in my extensive library for 
handling CSV files. I'm not sure why, because in library I am not use 
with any mathematical mode.


I am sorry, but at this moment I am not able to reveal the mistake to 
be able make a minimal example. Some of the older versions (not 
necessarily penultimate) worked without problems. Is there someone 
who help me start look from which point look for a mistake in my code 
library? Thanks for the information.
It’s possible you’re using a math command without enabling math mode 
or you use
the a wrong catcode regime (where _ and ^ work only in math) but 
without a example

there is not much to say.

Wolfgang


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Strange bug in the latest version of ConTeXt

[Wolfgang Schuster]

Jaroslav Hajtmar 
26. April 2016 um 16:02
Hello ConTeXist.

I have just installed the latest version of ConTeXt standalone. When I 
compiled an my old source code, I received an error:



! You can't use `\Ustopmath' in restricted horizontal mode! You can't 
use `\Ustopmath' in restricted horizontal mode! You can't use 
`\Ustartmath' in restricted horizontal mode! Inline math should end 
with \Ustopmath



This strange error is caused something in my extensive library for 
handling CSV files. I'm not sure why, because in library I am not use 
with any mathematical mode.


I am sorry, but at this moment I am not able to reveal the mistake to 
be able make a minimal example. Some of the older versions (not 
necessarily penultimate) worked without problems. Is there someone who 
help me start look from which point look for a mistake in my code 
library? Thanks for the information.
It’s possible you’re using a math command without enabling math mode or 
you use
the a wrong catcode regime (where _ and ^ work only in math) but without 
a example

there is not much to say.

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] Strange bug in the latest version of ConTeXt

[Jaroslav Hajtmar]

Hello ConTeXist.

I have just installed the latest version of ConTeXt standalone. When I 
compiled an my old source code, I received an error:



! You can't use `\Ustopmath' in restricted horizontal mode! You can't 
use `\Ustopmath' in restricted horizontal mode! You can't use 
`\Ustartmath' in restricted horizontal mode! Inline math should end with 
\Ustopmath



This strange error is caused something in my extensive library for 
handling CSV files. I'm not sure why, because in library I am not use 
with any mathematical mode.


I am sorry, but at this moment I am not able to reveal the mistake to be 
able make a minimal example. Some of the older versions (not necessarily 
penultimate) worked without problems. Is there someone who help me start 
look from which point look for a mistake in my code library? Thanks for 
the information.


Jaroslav Hajtmar


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] (again) bug with bidi direction and \about references

[Rik Kabel]

On 2014-03-04 11:07, Khaled Hosny wrote:

On Mon, Mar 03, 2014 at 07:49:07PM +0100, Pablo Rodriguez wrote:

Hi Hans,

sorry for telling again, but I’m afraid that the following sample shows
a serious buggy interaction between \setupdirections[bidi=on] and \about
references.

\setupdirections[bidi=on]

No problem with \setupdirections[bidi=on,method=two] (which I still
think should be the default, but Hans is not convinced).

Regards,
Khaled


Khaled,

I too had to rely on method=two as well to get around the problem with 
references appearing at the bottom left of some pages, but this seems to 
be resolved with the recent betas and the changes Hans has made at 
Talal's urging.


Perhaps you could test to see if resolves your cases.

--
Rik
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] (again) bug with bidi direction and \about references

[Hans Hagen]

On 8/12/2015 10:19 PM, Rik Kabel wrote:

On 2014-03-04 11:07, Khaled Hosny wrote:

On Mon, Mar 03, 2014 at 07:49:07PM +0100, Pablo Rodriguez wrote:

Hi Hans,

sorry for telling again, but I’m afraid that the following sample shows
a serious buggy interaction between \setupdirections[bidi=on] and \about
references.

\setupdirections[bidi=on]

No problem with \setupdirections[bidi=on,method=two] (which I still
think should be the default, but Hans is not convinced).

Regards,
Khaled


Khaled,

I too had to rely on method=two as well to get around the problem with
references appearing at the bottom left of some pages, but this seems to
be resolved with the recent betas and the changes Hans has made at
Talal's urging.

Perhaps you could test to see if resolves your cases.


there are three methods:

- default : based on how idris uses structured tex + mixed latin/arabic
- one : from khaled, optimized and extended a bit by me
- two : a follow up on 'one' by me (updated unicode bidi specs + more 
clever fences)


'default' is more efficient and ok for most mixed cases like the ones 
idris needs; i will probably leave 'one' as-is but will at some point 
optimize method 'two' and probably add some options there; also, in the 
case of for instance writing manuals 'default' might be a better choice


anyway, the problem with all methods (and more if it's a strict one) is 
that (as with more solutions) it's hard to get around when you want 
something different; also unicode bidi evolves (and actually the last 
version handles some cases that were the reason for 'default' in the 
first place as idris noted conceptual issues with unicode bidi at that 
time) so one can wonder about compatibility issues with any such 
mechanism that applies some heuristics to input instead of tagging


now, messing with the text stream is one aspect of bidi but that will 
not solve layout issues and special cases like hyperlinks, margin notes, 
images and such because simply reversing the par dir (or text dir) can 
interfere a lot (the dir mechanism in luatex is taken from omega and was 
never made for real complex mixed cases) .. many mechanisms need to be 
made r2l aware


so ... in order to get everything all right we need to test and improve 
stepwise ... no other way


(i'm playing with a better handling of line number for instance, where 
we have quite some interaction between paragraph properties and putting 
numbers at the right spot, and that's only one thing of many ... and i 
prefer to leave the luatex engine untouched ... i'm not really a user of 
r2l myself so ... a slow free-time process)


Hans



-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bibliography (bug compiling components-001.tex?) (now with sample files)

[Alan BRASLAU]

On Fri, 10 Jul 2015 11:29:17 +0200
Procházka Lukáš Ing. - Pontex s. r. o. l...@pontex.cz wrote:

 3) I would like to alter citation style from [1] to MA2004; I
 guess this could be done by \setuppublications[refcommand=author]...

MKIV:

\cite[short][bibtexkey]

or, to make this the default cite style:

\setupbtx[alternative=short]

which should give MA04 (the short style is first two initials of the
author name or the first initials of multiple author names followed by
a two digit year)

You can modify the style using

\setupbtx[default:cite:short][left=,right=]

to get rid of the brackets.

 4) Finally, in list of publications, I'd rather enumerate
 publications in [1] style rather than simple 1, i.e. enclose the
 publication number into [].

Similarly,

\setupbtx[default:list:numbering][left={[},right={]}]

to add brackets to the list.


Alan
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bibliography (bug compiling components-001.tex?) (now with sample files)

[Procházka Lukáš Ing . - Pontex s . r . o .]

Hello Alan,

thanks for the idea. Now I have:

 Bib6.mkiv, UTF-8
\startbuffer[biblio]
@article{Angell,
   Author = {Marcia Angell},
   Journal = {New York Review of Books},
   Month = {July 15},
   Title = {The Truth About the Drug Companies},
   Year = {2004},
}
@article{Me,
   Author = {Štěpán Čech},
   Journal = {New York Review of Books},
   Month = {July 15},
   Title = {The Truth About the Drug Companies},
   Year = {2004},
}
@article{101,
   Author = {Štěpán Čech},
   Journal = {New York Review of Books},
   Month = {July 15},
   Title = {The Truth About the Drug Companies},
   Year = {2004},
}
\stopbuffer

%%

\usebtxdataset[biblio.buffer]

\if+- % (1)
   \def\bracketed#1{\hbox to 20pt{\hfill [#1]}}

   \setuppublications
 [sorttype=bbl,
  autohang=no,
  refcommand=num,
  criterium=all,
  numbering=bib,
  %numbercommand=\bracketed,
 ]
\fi

%%

\starttext
   Hello \cite[Angell] \cite[Me] \cite[101]!

   \hairline
   \placelistofpublications[criterium=all]
   \hairline
   %\placepublications[criterium=all] % (2)
\stoptext


Some more questions:

1) Is \placepublications deprecated?

I'm getting Undefined control sequence when I uncomment (2);
even though \placepublications is widely cited on wiki (e.g. 
http://wiki.contextgarden.net/Bibliography_mkiv ) and is also mentioned in 
bibmod-doc.pdf 
(http://www.let.rug.nl/alfa/texmf/tetex30/context/bib/bibmod-doc.pdf ).

2) When I turn (1) on (\if+- - \if++), the Ctx doesn't crash but citations are 
broken and no list of pubs is generated.

I copied \setuppublications from 
http://wiki.contextgarden.net/Theory_book_style ;
strange for me that also empty \setuppublications (i.e.

   \setuppublications
 [%sorttype=bbl,
  %autohang=no,
  %refcommand=num,
  %criterium=all,
  %numbering=bib,
  %numbercommand=\bracketed,
 ]

) produces the same no-result.

3) I would like to alter citation style from [1] to MA2004; I guess this could be 
done by \setuppublications[refcommand=author] (see bibmod-doc.pdf, art. 2.1, pg. 2);
but - as mentioned at 2) - it doesn't work.

4) Finally, in list of publications, I'd rather enumerate publications in [1] style 
rather than simple 1, i.e. enclose the publication number into [].

In http://wiki.contextgarden.net/Theory_book_style , 
\setuppublications[numbercommand=\bracketed] provided that, but again, it 
doesn't work here due to 2).

So, how to overcome all these obstacles?

Best regards,

Lukas


On Thu, 09 Jul 2015 20:30:27 +0200, Alan BRASLAU alan.bras...@cea.fr wrote:


On Wed, 8 Jul 2015 22:21:36 +0200
Lukáš Procházka l...@pontex.cz wrote:


- have a DB of publications (preferably in standard ConTeXt
space, not in a .bib file)


MKiv bibliographies:

\startbuffer[biblio]
entries in .bib format
\stopbuffer

\usebtxdataset[biblio.buffer]

\cite[bibkey]

\placelistofpublications



Alan




--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o.  | mailto:pon...@pontex.cz | http://www.pontex.cz
Bezová 1658
147 14 Praha 4

Tel: +420 241 096 751
Fax: +420 244 461 038

Bib6.log
Description: Binary data


Bib6.mkiv
Description: Binary data


Bib6.pdf
Description: Adobe PDF document
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bibliography (bug compiling components-001.tex?) (now with sample files)

[Alan BRASLAU]

On Fri, 10 Jul 2015 08:47:35 +0200
Procházka Lukáš Ing. - Pontex s. r. o. l...@pontex.cz wrote:

 I'm getting Undefined control sequence when I uncomment (2);
 even though \placepublications is widely cited on wiki (e.g.
 http://wiki.contextgarden.net/Bibliography_mkiv ) and is also
 mentioned in bibmod-doc.pdf
 (http://www.let.rug.nl/alfa/texmf/tetex30/context/bib/bibmod-doc.pdf
 ).

Do not mix-up the bibmod (mkii, also adapted for mkiv)
with the mkiv bibliography dataset system (which is completely new).

I do not know anything about the wiki on this subject but it must be
completely obsolete as the development of this new system has been very
active over the past year.

Hans and I are (still) working on the documentation that has been
promised.

Alan
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bibliography (bug compiling components-001.tex?) (now with sample files)

[Procházka Lukáš Ing . - Pontex s . r . o .]

On Fri, 10 Jul 2015 10:29:52 +0200, Alan BRASLAU alan.bras...@cea.fr wrote:


On Fri, 10 Jul 2015 08:47:35 +0200
Procházka Lukáš Ing. - Pontex s. r. o. l...@pontex.cz wrote:


I'm getting Undefined control sequence when I uncomment (2);
even though \placepublications is widely cited on wiki (e.g.
http://wiki.contextgarden.net/Bibliography_mkiv ) and is also
mentioned in bibmod-doc.pdf
(http://www.let.rug.nl/alfa/texmf/tetex30/context/bib/bibmod-doc.pdf
).


Do not mix-up the bibmod (mkii, also adapted for mkiv)
with the mkiv bibliography dataset system (which is completely new).


OK. I studied MkIV related part on bibliography on wiki, probably too archaic.


I do not know anything about the wiki on this subject but it must be
completely obsolete as the development of this new system has been very
active over the past year.

Hans and I are (still) working on the documentation that has been
promised.


Great.

Back to my questions:

3) I would like to alter citation style from [1] to MA2004; I guess this could be 
done by \setuppublications[refcommand=author]...

4) Finally, in list of publications, I'd rather enumerate publications in [1] style 
rather than simple 1, i.e. enclose the publication number into [].

Are / will be points 3) a 4) achievable anyhow - now, in near future, any day?

Thank you anyway.

Best regards,

Lukas


Alan




--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o.  | mailto:pon...@pontex.cz | http://www.pontex.cz
Bezová 1658
147 14 Praha 4

Tel: +420 241 096 751
Fax: +420 244 461 038

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bibliography (bug compiling components-001.tex?)

[Alan BRASLAU]

On Wed, 8 Jul 2015 22:21:36 +0200
Lukáš Procházka l...@pontex.cz wrote:

 - have a DB of publications (preferably in standard ConTeXt
 space, not in a .bib file)

MKiv bibliographies:

\startbuffer[biblio]
entries in .bib format
\stopbuffer

\usebtxdataset[biblio.buffer]

\cite[bibkey]

\placelistofpublications



Alan
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bibliography (bug compiling components-001.tex?)

[Procházka Lukáš Ing . - Pontex s . r . o .]

Hello,

I also tried one of the ConTeXt suite test files, namely:

test\doc\context\tests\mkiv\bibtex\components-002.tex

where I just commented two lines, so I got:


% Was: components-001.tex

% \endinput % to be adapted

% adapted example from list

\startpublication[
k=me,
t=manual,
a=Hoekwater,
y=2006,
s=TH2006,
n=1,
u=http://contextgarden.net/Bibliography,
]
\author{Taco}[T.]{}{Hoekwater}
\title{\CONTEXT\ Publication Module, The user documententation}
\pubyear{2006}
\note{In case you didn’t know: it’s the document you are reading now}
\pages{14}
\stoppublication

\startproduct components-001

\startfrontmatter

  % \component components-002

  two: \cite[me]

\stopfrontmatter

\placepublications
  [criterium=text]

\stopproduct


But, I'm not able to compile even this file.

I'm getting:


mtx-context | run 1: luatex 
--fmt=c:/Ctx-Beta/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en
 --interaction=nonstopmode --jobname=Bib
--c:path=C:\\Lukas\\ConTeXt\\Styles cont-yes.mkiv
This is LuaTeX, Version beta-0.80.1 (TeX Live 2015/W32TeX) (rev 5274)
 \write18 enabled.

system   callbacks  not registering frozen 'find_format_file'
open source  1  1  
c:/Ctx-Beta/tex/texmf-context/tex/context/base/cont-yes.mkiv

ConTeXt  ver: 2015.07.01 21:40 MKIV beta  fmt: 2015.7.2  int: english/english

system   'cont-new.mkiv' loaded
open source  2  2  
c:/Ctx-Beta/tex/texmf-context/tex/context/base/cont-new.mkiv
close source 2  2  
c:/Ctx-Beta/tex/texmf-context/tex/context/base/cont-new.mkiv

system   jobfiles  using path: C:\\Lukas\\ConTeXt\\Styles
system   files  jobname 'Bib', input 
'd:\\Lukas\\ConTeXt\\Test\\Bib.mkiv', result 'Bib'
fontslatin modern fonts are not preloaded
languageslanguage 'en' is active
open source  2  3  d://Lukas/ConTeXt/Test/Bib.mkiv
fontspreloading latin modern fonts (second stage)
fonts'fallback modern-designsize rm 12pt' is loaded
structures   begin of sectionblock 'frontpart'
publications analyzing previous publication run for 'default'

lua errorerror on line 30 in file d://Lukas/ConTeXt/Test/Bib.mkiv:

c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:513: attempt to 
index field '?' (a nil value)
stack traceback:
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:513: in 
function 'register'
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:591: in 
function 'findallused'
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:2503: in 
function 'processcite'
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:2814: in 
function '?'
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:2304: in function 
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:2262
(...tail calls...)

20 \pages{14}
21 \stoppublication
22
23 \startproduct components-001
24
25 \startfrontmatter
26
27   % \component components-002
28
29   two: \cite[me]
30 
31 \stopfrontmatter
32
33 \placepublications
34   [criterium=text]
35
36 \stopproduct
37


structures   end of sectionblock 'frontpart'
backend  xmp  using file 
'c:/Ctx-Beta/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pagesflushing realpage 1, userpage 1

lua errorerror on line 33 in file d://Lukas/ConTeXt/Test/Bib.mkiv:

c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:513: attempt to 
index field '?' (a nil value)
stack traceback:
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:513: in 
function 'register'
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:591: in 
function 'findallused'
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:2503: in 
function 'processcite'
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:2814: in 
function '?'
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:2304: in function 
c:/Ctx-Beta/tex/texmf-context/tex/context/base/publ-ini.lua:2262
(...tail calls...)

23 \startproduct components-001
24
25 \startfrontmatter
26
27   % \component components-002
28
29   two: \cite[me]
30
31 \stopfrontmatter
32
33   \placepublications
34   [criterium=text]
35
36 \stopproduct
37


pagesflushing realpage 2, userpage 2
close source 2  3  d://Lukas/ConTeXt/Test/Bib.mkiv
close source 1  3  
c:/Ctx-Beta/tex/texmf-context/tex/context/base/cont-yes.mkiv
...
mtx-context | fatal error: return code: 1


The full log is attached...

What is wrong?

Best regards,

Lukas


--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o.  | mailto:pon...@pontex.cz | http://www.pontex.cz
Bezová 1658
147 14 Praha 4

Tel: +420 241 096 751
Fax: +420 244 461 038