[NTG-context] LMTX update 2020.11.17 ----> 11.19 | Paragraph indenting
Hello, I noticed yesterday that paragraph indenting appears to have changed between LMTX 2020.11.17 & 11.19. Usually the first paragraph after a section heading does not indent, as it does with all subsequent paragraphs. With 11.19 the first paragraph does have an indent. I've had to revert to 11.17. Best, Richard -- T +6433121699 M +64210640216 E rmaho...@indica-et-buddhica.org IM https://t.me/rmahoney W https://indica-et-buddhica.org/ Indica et Buddhica Littledene Bay Road Oxford NZ ___ 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 update 2020.11.17 ----> 11.19 | Paragraph indenting
On 11/21/20 10:44 PM, Richard Mahoney wrote: > Hello, > > I noticed yesterday that paragraph indenting appears to have changed between > LMTX 2020.11.17 & 11.19. Usually the first paragraph after a section heading > does not indent, as it does with all subsequent paragraphs. With 11.19 > the first paragraph does have an indent. I've had to revert to 11.17. Hi Richard, Hans provided a patch at https://mailman.ntg.nl/pipermail/ntg-context/2020/100284.html. Choose the more correct one (as described by him, the second one) and place in cont-new.mkiv, right before the final \protect. Run "mtxrun --script cache --erase && mtxrun --generate" (so delete cache and generate the basic files) and indenting will work again. I hope it helps, 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 ___
[NTG-context] lmtx \placefigure and bizarre captions
Hello When I compile my file with ConText-Luatex from Texlive 2019 (linux debian) I get the right result. On the other hand with the last version of LMTX I have a 2nd caption above the image (see attached file). It's not on all the pictures, it's random. ___ 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] ornaments with Linux Libertine
Hi YAHYAOUI,
This works for me with my LinuxLibertine font.
\definefont[linlib][name:linuxlibertinegregular*default at 12pt]
\starttext
\linlib
\tochar{n:Tux}
\tochar{x:E000}
\tochar{x:E001}
\tochar{x:E002}
\tochar{x:E003}
\tochar{x:2619}
\tochar{x:2767}
\stoptext
Greetings Lutz
Am 21. November 2020 13:05:18 MEZ schrieb kaddour kardio
:
>Hi dear list, i'm struggling to get ornaments from linux libertine.
>The wiki is sparse regarding this topic.
>Any help would be appreciated!
>
>--
>Dr YAHYAOUI Mohamed Kaddour, cardiologue .
___
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 MkIV difference in expansion
On 11/21/2020 10:05, Wolfgang Schuster wrote:
Rik Kabel schrieb am 20.11.2020 um 00:18:
You are right about not quite understand.
There are cases where you want to pass a command to another command as
it is without replacing it with its content, e.g. when you store the
\TeX logo in the table of content the \TeX command should be written
in the register and not the content of the command.
In the following example the first line prints the definition of the
\TeX logo but in many cases you ant to preserve the command as in the
second line.
\starttext
\tex{TeX} = \detokenize\expandafter{\TeX}
\blank
\tex{TeX} = \detokenize{\TeX}
\stoptext
To make it easier to keep the command eTeX added a new command
\protected which can be used before \def to achieve this (ConTeXt
provides the same thing under the name \unexpanded).
The following example shows how you can use \protected\def to keep
always the current meaning of \foo when you print the content of \bar.
\starttext
\def\foo{foo}
\edef\bar{\foo}
\def\foo{bar}
\startlines
bar=\bar
foo=\foo
\stoplines
\blank
\protected\def\foo{foo}
\edef\bar{\foo}
\protected\def\foo{bar}
\startlines
bar=\bar
foo=\foo
\stoplines
\stoptext
A problem in older TeX engines is that \csname ...\endcsname didn't
respect this protection and replaced the protected command with its
content, recently Hans changed this behavior in LMTX which lead to the
error message in your document.
Does this mean that I can have the same definitions in MkIV and LMTX
(after some future update), or should I hunt down the \defines in
both, or that I should fork (or mode test) my source environment
files, one set for LMTX and one for MkIV?
When you use \define to store arguments which are passed as arguments
to other command you have to change this to \defineexpandable but its
best to do this in MkIV and LMTX because protected commands are the
wrong thing in this case. Even though it would work in MkIV in some
cases you run into problems when you pass argument to Lua.
Wolfgang
Thank you, Wolfgang, for the explanation and examples.
I have in fact already gone through and replaced the impacted
occurrences of \define with \defineexpandable. LMTX made it easy to
identify them.
--
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] LMTX MkIV difference in expansion
Rik Kabel schrieb am 20.11.2020 um 00:18:
You are right about not quite understand.
There are cases where you want to pass a command to another command as
it is without replacing it with its content, e.g. when you store the
\TeX logo in the table of content the \TeX command should be written in
the register and not the content of the command.
In the following example the first line prints the definition of the
\TeX logo but in many cases you ant to preserve the command as in the
second line.
\starttext
\tex{TeX} = \detokenize\expandafter{\TeX}
\blank
\tex{TeX} = \detokenize{\TeX}
\stoptext
To make it easier to keep the command eTeX added a new command
\protected which can be used before \def to achieve this (ConTeXt
provides the same thing under the name \unexpanded).
The following example shows how you can use \protected\def to keep
always the current meaning of \foo when you print the content of \bar.
\starttext
\def\foo{foo}
\edef\bar{\foo}
\def\foo{bar}
\startlines
bar=\bar
foo=\foo
\stoplines
\blank
\protected\def\foo{foo}
\edef\bar{\foo}
\protected\def\foo{bar}
\startlines
bar=\bar
foo=\foo
\stoplines
\stoptext
A problem in older TeX engines is that \csname ...\endcsname didn't
respect this protection and replaced the protected command with its
content, recently Hans changed this behavior in LMTX which lead to the
error message in your document.
Does this mean that I can have the same definitions in MkIV and LMTX
(after some future update), or should I hunt down the \defines in both,
or that I should fork (or mode test) my source environment files, one
set for LMTX and one for MkIV?
When you use \define to store arguments which are passed as arguments to
other command you have to change this to \defineexpandable but its best
to do this in MkIV and LMTX because protected commands are the wrong
thing in this case. Even though it would work in MkIV in some cases you
run into problems when you pass argument to Lua.
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] Problem with setupcharacterspacing and comma
On 11/21/2020 04:46, Hans Hagen wrote: On 11/21/2020 4:57 AM, Rik Kabel wrote: Hello all, Playing with define/setup/set characterspacing, I have come across some odd, perhaps buggy, behavior. This applies to both MkIV 2020.11.19 11:23 and LMTX 2020.11.19 11:28. The problem is that character spacing is not effected for the left side of the comma character. It is handled as expected for other characters that I have tested, but I have not performed extensive tests. Example code: \definecharacterspacing[Test] \setupcharacterspacing [Test] ["002C] [left =.25,right=1,alternative=1] % , \setupcharacterspacing [Test] ["0065] [left=0.5,right=1,alternative=1] % e \setupcharacterspacing [Test] ["003B] [left=0.5,right=1,alternative=1] % e \startTEXpage[offset=1em] abc; def, g \setcharacterspacing[Test]abc; def, g \stopTEXpage remove the space between "left" and "=" I should have know better than to copy as I did from the source code without analyzing it sufficiently! In typo-spa.mkiv I found: \setupcharacterspacing [frenchpunctuation] ["003A] [\c!left =.25,\c!alternative=1] % : ... I see (now) that the space disappears when the \c!left macro is processed. Mea culpa. I owe you a beer. -- 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] [lmtx] ornaments with Linux Libertine
Hi dear list, i'm struggling to get ornaments from linux libertine. The wiki is sparse regarding this topic. Any help would be appreciated! -- Dr YAHYAOUI Mohamed Kaddour, cardiologue . ___ 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
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
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] Problem with setupcharacterspacing and comma
On 11/21/2020 4:57 AM, Rik Kabel wrote: Hello all, Playing with define/setup/set characterspacing, I have come across some odd, perhaps buggy, behavior. This applies to both MkIV 2020.11.19 11:23 and LMTX 2020.11.19 11:28. The problem is that character spacing is not effected for the left side of the comma character. It is handled as expected for other characters that I have tested, but I have not performed extensive tests. Example code: \definecharacterspacing[Test] \setupcharacterspacing [Test] ["002C] [left =.25,right=1,alternative=1] % , \setupcharacterspacing [Test] ["0065] [left=0.5,right=1,alternative=1] % e \setupcharacterspacing [Test] ["003B] [left=0.5,right=1,alternative=1] % e \startTEXpage[offset=1em] abc; def, g \setcharacterspacing[Test]abc; def, g \stopTEXpage remove the space between "left" and "=" - 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
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 ___
