Re: [NTG-context] Contextual removal of some ligatures using fonts.handlers.otf.addfeature (LuaTeX 1.13.2)
Hi Bruce and Hans !
Thank you very much for your answers, that helped me a lot.
In fact, though I would love to switch to ConTeXt one day, I am still using
LuaLaTeX — I am a slow
learner and I know it will take me months to be able to achieve what I need for
my job with
ConTeXt and can do with LuaLaTeX and the Memoir class for the time being
(despite sometimes
being irritated by LaTeX limitations or oddities).
I need the EB Garamond variable font for future jobs, but this font, provided
by Google Fonts, is
such a mess : kerning problems, unusable OpenType features that have to be
rewritten from
scratch, shifts in glyphs table… For sure, the original font by Georg Duffner
was much better, but I
need the variable version. Lots of fixing necessary, but thanks to
fonts.handlers.otf.addfeature I
have almost succeeded to make it a usable Garamond.
Of course, it would be best to help Google improving this font, but I don’t
have time yet.
The actual problem was with the italic ligatures "a_s", "e_s", "é_s", "i_s" and
"u_s", that should occur
only at the end of words and not everywhere. Instead of removing the unwanted
ligatures, I chose
another way as soon as I understood how to fully use “current” to describe not
only a single glyph,
but a string if necessary — for instance, current={ { "a", "e", "eacute", "i",
"u"}, {"s"} }
Thanks for this wonderful tool !
Thomas Savary
1 le Grand-Plessis
F-85340 L’Île-d’Olonne
Tél. 06 22 82 61 34
https://compo85.fr/
Le samedi 25 décembre 2021, 00:04:51 CET Bruce Horrocks a écrit :
> > On 24 Dec 2021, at 18:34, Thomas Savary via ntg-context
> > wrote:
> >
> > Hello, dear list !
> >
> > In order to fix a few bugs in some OpenType features included in EB
> > Garamond font provided by Google Fonts, I am trying to remove some
> > ligatures (erroneous in some contexts) with
> > fonts.handlers.otf.addfeature.
> >
> > I must be missing something, because I can't get it to work.
> >
> > Here is a minimal —non working—example :-)
> > (The attempted removal (“f_i” → “fi” only before “o”) is of course
> > irrelevant. I chose it just for the sole purpose of this test, to
> > provide a simple example. What I am trying to achieve is more
> > complex, with other ligatures.)
> >
> > fonts.handlers.otf.addfeature{
> >
> > name = "unfio",
> > type = "chainsubstitution",
> > lookups = {
> >
> > { type = "multiple",
> > data = { [ "f_i" ] = { "f", "i" } }
> > }
> >
> > }
> > rules = {
> >
> > { after = { { "o" } },
> > current = { { "f_i" } },
> > lookups = { 1 } }
> >
> > }
> >
> > }
> >
> > }
> >
> > Could someone please explain to me what I did wrong ?
>
> Firstly, you have an extra } in the example above.
>
> Secondly, rules need to come inside a data section. Thus (untested):
>
> fonts.handlers.otf.addfeature{
> name = "unfio",
> type = "chainsubstitution",
> lookups = {
> {
> type = "substitution",
> data = {
> [ "f_i" ] = { "f", "i" }
> }
> }
> },
> data = {
> rules = {
> {
> after = { { "o" } },___
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] Why are endnotes not working with ConTeXt-SBL?
A reasonable solution for the time being would be to check if the
righttext argument is empty, and add a final period in the footnote only if
it is not (with the assumption being that the user would provide
punctuation in any righttext for footnote/endnote citations). I've pushed
the following change to the GitHub repo, if you'd like to pull and use it:
```
% Inline footnote citation setup (with intelligent trailing punctuation
replacement)
\startsetups btx:sbl:cite:footnote
\removeunwantedspaces
\doifinstring{\btxparameter{punct}}{\btxparameter{autopunctuation}}{\btxparameter{punct}}
\begingroup
\letbtxparameter{punct}\empty % don't pass the trailing punctuation down
to the inline setup
\startfootnote
\Word{\fastsetup{btx:sbl:cite:inline}}% capitalize the first word in
the footnote (needed to render "Ibid." and "Idem" correctly)
% Add a closing period if there is no righttext
\doif{\btxparameter{righttext}}{\empty} {
\btxperiod
}
\stopfootnote
\endgroup
\doifnotinstring{\btxparameter{punct}}{\btxparameter{autopunctuation}}{\btxparameter{punct}}
\stopsetups
```
This should allow your script to compile, but unfortunately, it doesn't
seem to make endnotes work, at least not when I try it. For some reason,
the macro \Word{\fastsetup{btx:sbl:cite:inline}} is expanding to nothing
inside the \startfootnote ... \stopfootnote environment. I have no idea why
this is happening, so any ideas are appreciated.
Joey
On Sat, Dec 25, 2021 at 1:11 PM Joey McCollum
wrote:
> Joel,
>
> You may not have done anything wrong; this may be an issue with
> ConTeXt-SBL. In my code for the btx:sbl:cite:footnote setup in
> publ-imp-sbl.mkvi, I added a comment to this effect:
>
> ```
> \startsetups btx:sbl:cite:footnote
> \removeunwantedspaces
>
> \doifinstring{\btxparameter{punct}}{\btxparameter{autopunctuation}}{\btxparameter{punct}}
> \begingroup
> \letbtxparameter{punct}\empty % don't pass the trailing punctuation down
> to the inline setup
> \let\doifendswithpunctelse\btx_sbl_doifendswithpunctelse % why is this
> necessary? For some reason, \btx_sbl_doifendswithpunctelse is not
> recognized within the footnote environment...
> \startfootnote
> \Word{\fastsetup{btx:sbl:cite:inline}}% capitalize the first word in
> the footnote (needed to render "Ibid." and "Idem" correctly)
> % Add a closing period, unless the righttext ends with punctuation
> \doifendswithpunctelse{\btxparameter{righttext}} {
> \removeunwantedspaces
> } {
> \removeunwantedspaces
> \btxperiod
> }
> \stopfootnote
> \endgroup
>
> \doifnotinstring{\btxparameter{punct}}{\btxparameter{autopunctuation}}{\btxparameter{punct}}
> \stopsetups
> ```
>
> I define the \btx_sbl_doifendswithpunctelse macro earlier in the module.
> Initially, when I tried to invoke this macro within the \startfootnote ...
> \stopfootnote environment (to conditionally add a period at the end of a
> footnote citation if it does not have a righttext ending with punctuation),
> I got the same error you got, but for \btx_sbl_doifendswithpunctelse. I
> wasn't sure why this was happening, so I tried defining a new
> \doifendswithpunctelse macro. Unfortunately, based on your e-mail, it looks
> like this doesn't actually fix the problem.
>
> Any help from other developers would be appreciated here! Unfortunately, I
> don't have a MWE replicating the problem on hand at the moment.
>
> Joey
>
> On Sat, Dec 25, 2021 at 1:04 PM Joel via ntg-context
> wrote:
>
>> I am using the ConTeXt-SBL package for citations. I need to move my
>> footnotes to the end of each article.
>>
>> According to the manual, I can suppress the placement of footnotes using
>> two lines of code. I've added these to my minimal working code, placing
>> \setupnote[footnote][location=none]
>> in the header and \placenotes[footnote] where I want the endnotes to
>> appear. It complains this error:
>>
>> "Undefined control sequence \doifendswithpunctelse"
>>
>> What did I do wrong?
>>
>> --Joel
>>
>> Code follows:
>>
>> \usemodule[publ-imp-sbl]
>> \startbuffer [bib]
>>
>> @Article{na2006,
>> title={Volcanoes \word{of} New Mexico},
>> year={2006},
>> journal={New Mexico Earth Matters},
>> publisher={New Mexico Bureau \word{of} Geology \word{and} Mineral
>> Resources},
>> volume={6},
>> number={1},
>> location={Socorro, New Mexico}
>> }
>>
>> @Book{clark1989,
>> author = {Clark, William},
>> title = {Railroads \word{and} railroad towns \word{in} New Mexico},
>> publisher = {New Mexico Magazine},
>> year = {1989},
>> address = {Albuquerque, New Mexico},
>> isbn = {9780937206126}
>> }
>>
>> \stopbuffer
>>
>> \usebtxdataset[bib.buffer]
>>
>> \setupbtx[dataset=default]
>> \usebtxdefinitions[sbl]
>> \setupbtx[sbl]
>>
>> \setupnote[footnote][location=none]
>>
>> \starttext
>>
>>\input knuth
>> \cite[clark1989]
>>
>> \placenotes[footnote]
>>
>>
>> \startchapter[title=Bibliography]
>> \placelistofpublications
>> \stopchapter
>>
>>
Re: [NTG-context] Why are endnotes not working with ConTeXt-SBL?
Joel,
You may not have done anything wrong; this may be an issue with
ConTeXt-SBL. In my code for the btx:sbl:cite:footnote setup in
publ-imp-sbl.mkvi, I added a comment to this effect:
```
\startsetups btx:sbl:cite:footnote
\removeunwantedspaces
\doifinstring{\btxparameter{punct}}{\btxparameter{autopunctuation}}{\btxparameter{punct}}
\begingroup
\letbtxparameter{punct}\empty % don't pass the trailing punctuation down
to the inline setup
\let\doifendswithpunctelse\btx_sbl_doifendswithpunctelse % why is this
necessary? For some reason, \btx_sbl_doifendswithpunctelse is not
recognized within the footnote environment...
\startfootnote
\Word{\fastsetup{btx:sbl:cite:inline}}% capitalize the first word in
the footnote (needed to render "Ibid." and "Idem" correctly)
% Add a closing period, unless the righttext ends with punctuation
\doifendswithpunctelse{\btxparameter{righttext}} {
\removeunwantedspaces
} {
\removeunwantedspaces
\btxperiod
}
\stopfootnote
\endgroup
\doifnotinstring{\btxparameter{punct}}{\btxparameter{autopunctuation}}{\btxparameter{punct}}
\stopsetups
```
I define the \btx_sbl_doifendswithpunctelse macro earlier in the module.
Initially, when I tried to invoke this macro within the \startfootnote ...
\stopfootnote environment (to conditionally add a period at the end of a
footnote citation if it does not have a righttext ending with punctuation),
I got the same error you got, but for \btx_sbl_doifendswithpunctelse. I
wasn't sure why this was happening, so I tried defining a new
\doifendswithpunctelse macro. Unfortunately, based on your e-mail, it looks
like this doesn't actually fix the problem.
Any help from other developers would be appreciated here! Unfortunately, I
don't have a MWE replicating the problem on hand at the moment.
Joey
On Sat, Dec 25, 2021 at 1:04 PM Joel via ntg-context
wrote:
> I am using the ConTeXt-SBL package for citations. I need to move my
> footnotes to the end of each article.
>
> According to the manual, I can suppress the placement of footnotes using
> two lines of code. I've added these to my minimal working code, placing
> \setupnote[footnote][location=none]
> in the header and \placenotes[footnote] where I want the endnotes to
> appear. It complains this error:
>
> "Undefined control sequence \doifendswithpunctelse"
>
> What did I do wrong?
>
> --Joel
>
> Code follows:
>
> \usemodule[publ-imp-sbl]
> \startbuffer [bib]
>
> @Article{na2006,
> title={Volcanoes \word{of} New Mexico},
> year={2006},
> journal={New Mexico Earth Matters},
> publisher={New Mexico Bureau \word{of} Geology \word{and} Mineral
> Resources},
> volume={6},
> number={1},
> location={Socorro, New Mexico}
> }
>
> @Book{clark1989,
> author = {Clark, William},
> title = {Railroads \word{and} railroad towns \word{in} New Mexico},
> publisher = {New Mexico Magazine},
> year = {1989},
> address = {Albuquerque, New Mexico},
> isbn = {9780937206126}
> }
>
> \stopbuffer
>
> \usebtxdataset[bib.buffer]
>
> \setupbtx[dataset=default]
> \usebtxdefinitions[sbl]
> \setupbtx[sbl]
>
> \setupnote[footnote][location=none]
>
> \starttext
>
>\input knuth
> \cite[clark1989]
>
> \placenotes[footnote]
>
>
> \startchapter[title=Bibliography]
> \placelistofpublications
> \stopchapter
>
> \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
>
> ___
>
___
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] Why are endnotes not working with ConTeXt-SBL?
I am using the ConTeXt-SBL package for citations. I need to move my footnotes
to the end of each article.
According to the manual, I can suppress the placement of footnotes using two
lines of code. I've added these to my minimal working code, placing
\setupnote[footnote][location=none] in the header and \placenotes[footnote]
where I want the endnotes to appear. It complains this error:
"Undefined control sequence \doifendswithpunctelse"
What did I do wrong?
--Joel
Code follows:
\usemodule[publ-imp-sbl]
\startbuffer [bib]
@Article{na2006,
title={Volcanoes \word{of} New Mexico},
year={2006},
journal={New Mexico Earth Matters},
publisher={New Mexico Bureau \word{of} Geology \word{and} Mineral Resources},
volume={6},
number={1},
location={Socorro, New Mexico}
}
@Book{clark1989,
author = {Clark, William},
title = {Railroads \word{and} railroad towns \word{in} New Mexico},
publisher = {New Mexico Magazine},
year = {1989},
address = {Albuquerque, New Mexico},
isbn = {9780937206126}
}
\stopbuffer
\usebtxdataset[bib.buffer]
\setupbtx[dataset=default]
\usebtxdefinitions[sbl]
\setupbtx[sbl]
\setupnote[footnote][location=none]
\starttext
\input knuth
\cite[clark1989]
\placenotes[footnote]
\startchapter[title=Bibliography]
\placelistofpublications
\stopchapter
\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] upload
On Sat, 25 Dec 2021 12:44:31 +0100
Hans Hagen wrote:
> because these are not errors in the sense of 'quit' ... for instance
> missing references can be resolved in a second run
Ok, but that's what the context runner is for, not? It's smart and
knows when it's hitting the last run and if there are still
unresolved issues, it could then report the correct return value to
the environment. The runner is responsible for the final return
value, not the individual context run AFAIK.
> you need to be explicit:
>
> \enabledirectives [logs.errors={missing references,missing
> characters}]
Ok, that works, great news. So if I understand you correctly,
there's no command to enable them *all* at once? Frankly, I'd expect
\enabledirectives [logs.errors] to enable them all (including the
correct return value), but apparently it only enables the reporting
and doesn't affect the return value.
That begs the question: Which error directives are available (so I
can manually enable them)?
Side note: A missing font is not an error:
\enabledirectives [logs.errors]
\definefontfamily [foo] [serif] [no font here really]
\setupbodyfont [foo]
\starttext foo \stoptext
But I guess that's just not supported.
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] upload
On 12/25/2021 12:22 PM, Marco Patzer via ntg-context wrote:
On Sat, 25 Dec 2021 11:55:31 +0100
Hans Hagen wrote:
>mtxrun --autogenerate --script context --autopdf "oeps.tex"
mkiv lua stats > runtime: 0.485 seconds, 1 processed pages, 1
shipped pages, 2.062 pages/second
mtx-context | fatal error: return code: 1
so ... an error ... that's the most i can do
I did some more checking. It seems to return 1 on *some* errors, but
not on all the ones supported by --errors. This example e.g.
compiles with return code 0:
%% enables logging of errors
\enabledirectives [logs.errors]
%% missing font
\definefontfamily [foo] [serif] [no font here really]
\setupbodyfont [foo]
\starttext
%% missing characters
풜
%% missing figure
\externalfigure [foo]
%% missing references
See \in{section}[sec:none].
\stoptext
because these are not errors in the sense of 'quit' ... for instance
missing references can be resolved in a second run
you need to be explicit:
\enabledirectives [logs.errors={missing references,missing characters}]
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] Contextual removal of some ligatures using fonts.handlers.otf.addfeature (LuaTeX 1.13.2)
On 12/25/2021 12:04 AM, Bruce Horrocks via ntg-context wrote:
On 24 Dec 2021, at 18:34, Thomas Savary via ntg-context
wrote:
Hello, dear list !
In order to fix a few bugs in some OpenType features included in EB Garamond
font provided by Google Fonts, I am trying to remove some ligatures (erroneous
in some contexts) with fonts.handlers.otf.addfeature.
I must be missing something, because I can't get it to work.
Here is a minimal —non working—example :-)
(The attempted removal (“f_i” → “fi” only before “o”) is of course irrelevant.
I chose it just for the sole purpose of this test, to provide a simple example.
What I am trying to achieve is more complex, with other ligatures.)
fonts.handlers.otf.addfeature{
name = "unfio",
type = "chainsubstitution",
lookups = {
{ type = "multiple",
data = { [ "f_i" ] = { "f", "i" } }
}
}
rules = {
{ after = { { "o" } },
current = { { "f_i" } },
lookups = { 1 } }
}
}
}
Could someone please explain to me what I did wrong ?
Firstly, you have an extra } in the example above.
Secondly, rules need to come inside a data section. Thus (untested):
fonts.handlers.otf.addfeature{
name = "unfio",
type = "chainsubstitution",
lookups = {
{
type = "substitution",
data = {
[ "f_i" ] = { "f", "i" }
}
}
},
data = {
rules = {
{
after = { { "o" } },
current = { { "f_i" } },
lookups = { 1 }
}
}
}
}
A better an dmore reliable approach is this:
\startluacode
local demo = {
name= "demo",
options = {
{
patterns = {
fio = "f|io",
},
words = [[ fioot fiots ]],
},
},
}
table.save("oeps-fixes.llg",demo)
\stopluacode
\setuplanguage[en][goodies={oeps-fixes.llg}]
\setupbodyfont[ebgaramond]
\starttext
fiets fiots fiats fioot
\stoptext
because you want to block certain ligatures but keep kerning etc (see
older posts for more extensive examples)
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] upload
On Sat, 25 Dec 2021 11:55:31 +0100
Hans Hagen wrote:
> >mtxrun --autogenerate --script context --autopdf "oeps.tex"
>
>
>
> mkiv lua stats > runtime: 0.485 seconds, 1 processed pages, 1
> shipped pages, 2.062 pages/second
> mtx-context | fatal error: return code: 1
>
> so ... an error ... that's the most i can do
I did some more checking. It seems to return 1 on *some* errors, but
not on all the ones supported by --errors. This example e.g.
compiles with return code 0:
%% enables logging of errors
\enabledirectives [logs.errors]
%% missing font
\definefontfamily [foo] [serif] [no font here really]
\setupbodyfont [foo]
\starttext
%% missing characters
풜
%% missing figure
\externalfigure [foo]
%% missing references
See \in{section}[sec:none].
\stoptext
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] Contextual removal of some ligatures using fonts.handlers.otf.addfeature (LuaTeX 1.13.2)
On 12/25/2021 12:04 AM, Bruce Horrocks via ntg-context wrote:
On 24 Dec 2021, at 18:34, Thomas Savary via ntg-context
wrote:
Hello, dear list !
In order to fix a few bugs in some OpenType features included in EB Garamond
font provided by Google Fonts, I am trying to remove some ligatures (erroneous
in some contexts) with fonts.handlers.otf.addfeature.
I must be missing something, because I can't get it to work.
Here is a minimal —non working—example :-)
(The attempted removal (“f_i” → “fi” only before “o”) is of course irrelevant.
I chose it just for the sole purpose of this test, to provide a simple example.
What I am trying to achieve is more complex, with other ligatures.)
fonts.handlers.otf.addfeature{
name = "unfio",
type = "chainsubstitution",
lookups = {
{ type = "multiple",
data = { [ "f_i" ] = { "f", "i" } }
}
}
rules = {
{ after = { { "o" } },
current = { { "f_i" } },
lookups = { 1 } }
}
}
}
Could someone please explain to me what I did wrong ?
Firstly, you have an extra } in the example above.
Secondly, rules need to come inside a data section. Thus (untested):
fonts.handlers.otf.addfeature{
name = "unfio",
type = "chainsubstitution",
lookups = {
{
type = "substitution",
data = {
[ "f_i" ] = { "f", "i" }
}
}
},
data = {
rules = {
{
after = { { "o" } },
current = { { "f_i" } },
lookups = { 1 }
}
}
}
}
the problem with this approach is that in a feature rich font like eb
you never know where to kick this into the sequence and you even don't
know how many variants of fi ligatures are there
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] upload
On 12/25/2021 10:09 AM, Jeong Dal via ntg-context wrote: Dear Hans, I installed the new upload and compiled “helloWorld.tex” created Sanjoy Mahajan. It runs well except the dummy figures are not appeared in the pdf output. However, I still got error message when try to compile “\startcolumnset … \stopcolumnset”. fonts > 'fallback modern-designsize rm 12pt' is loaded mtx-context | fatal error: return code: 1 The terminal process "zsh '-c', 'mtxrun --autogenerate --script context --autopdf --purge '/Users/graph/Library/Mobile Documents/com~apple~CloudDocs/texMain/exit11.tex''" terminated with exit code: 1. maybe some file access issue, i have no apple computer to test 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] upload
On 12/25/2021 10:19 AM, Marco Patzer via ntg-context wrote: On Fri, 24 Dec 2021 19:45:05 +0100 Hans Hagen via ntg-context wrote: When wrapping up before the weekend I uploaded a new lmtx (bottom floats fixed afaiks If you mean the issue I posted on 2021-11-30, then no. It still throws an error here on my end. exit codes more reliable The example I posted on 2021-12-15 still returns success when it should fail. So regarding the exit codes I see no change here. \enabledirectives [logs.errors] \starttext %% ### semi simple group … entered at line \startalignment [middle] foo \stoptext >mtxrun --autogenerate --script context --autopdf "oeps.tex" mkiv lua stats > runtime: 0.485 seconds, 1 processed pages, 1 shipped pages, 2.062 pages/second mtx-context | fatal error: return code: 1 so ... an error ... that's the most i can do 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 new float types fails in LMTX
On Tue, 30 Nov 2021 15:51:24 +0100 Marco Patzer via ntg-context wrote: > There's an issue with defining new floats in LMTX in combination > with bottom placement. > > The following works in MkIV, but throws an error in LMTX: Short followup: This issue is still present in 2021.12.25 00:55. 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] location=outer causes bad page break in LMTX
On Tue, 30 Nov 2021 14:13:52 +0100 Marco Patzer via ntg-context wrote: > In the following example “Lorem ipsum” sits on an otherwise empty > page in LMTX. Output is as expected with MkIV. This is now fixed in the latest version. Thanks Hans. 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] upload
On Fri, 24 Dec 2021 19:45:05 +0100 Hans Hagen via ntg-context wrote: > When wrapping up before the weekend I uploaded a new lmtx (bottom > floats fixed afaiks If you mean the issue I posted on 2021-11-30, then no. It still throws an error here on my end. > exit codes more reliable The example I posted on 2021-12-15 still returns success when it should fail. So regarding the exit codes I see no change here. > side float coming loose from section head issue solved; ...). That's fixed indeed. Thanks for looking into that. Marco LMTX 2021.12.25 00:55 ___ 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] upload
Dear Hans, I installed the new upload and compiled “helloWorld.tex” created Sanjoy Mahajan. It runs well except the dummy figures are not appeared in the pdf output. However, I still got error message when try to compile “\startcolumnset … \stopcolumnset”. fonts > 'fallback modern-designsize rm 12pt' is loaded mtx-context | fatal error: return code: 1 The terminal process "zsh '-c', 'mtxrun --autogenerate --script context --autopdf --purge '/Users/graph/Library/Mobile Documents/com~apple~CloudDocs/texMain/exit11.tex''" terminated with exit code: 1. As you see in the log file, "return code: 11" is changed to “return code: 1”. It might be the problem of system environment as you said. Thank you. Merry Christmas and Happy new year! Best regards, Dalyoung ___ 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 ___
