[NTG-context] luatex crash around page 1000
The event manager says, that it is a stack exhaustion (0xc0fd, STATUS_STACK_OVERFLOW). Many thanks. I'll increase size of stack. Best, Akira ___ If your question is of interest to others as well, please add an 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 error with fontstrip in today’s beta
On 4/12/2019 11:19 PM, Henning Hraban Ramm wrote: I just updated my minimals installation (2019.04.12 17:43, still not lmtx) and run into this error: lua error > lua error on line 1 in file fontstriptest.tex: ...xmf/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:284: attempt to call a nil value (global 'setfield') 1 >> \starttext 2 3 \showfontstrip 4 5 \stoptext MWE: \starttext \showfontstrip \stoptext i'll fix it (side effect of transition to lmtx as alan mentioned) 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] caching buffers?
Am 2019-04-12 um 23:13 schrieb Hans Hagen : > On 4/12/2019 11:00 PM, Henning Hraban Ramm wrote: >> Ahoi, >> in my book I use a lot of buffers for examples. These get typeset (compiled) >> anew on every tex run (i.e. several times per context run). This needs a lot >> of time and is quite annoying. Is this somehow cacheable, so that it >> compiles only once per context run or (even better) only if the buffer >> changed? >> How does the filter module handle this? I know it uses some checksum. >> Should I "outsource" my buffers via t-filter? >> If you need a MWE for this, I’ll assemble one. My actual setup is quite >> complicated, maybe that’s the problem... > \starttext > >\startbuffer[old-feature] >% load the relevant environment if needed >It works! >\stopbuffer > >\typesetbuffer[old-feature][frame=on,width=4cm] > > \stoptext > > Only when buffers change they will be retypeset. I used the same buffer name all the time. Sorry for the noise. Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de 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 error with fontstrip in today’s beta
On Fri, 12 Apr 2019 23:19:34 +0200 Henning Hraban Ramm wrote: > minimals installation (2019.04.12 17:43, still not lmtx) Ah, when I first started using ConTeXt, MkIV was somewhat experimental and it was still recommended to use MkII (with pdftex) for "production". Now we are generally surprised when someone comes up with MkII questions or examples ... and as this has become old hat. So Hans came up with lmtx just to animate the mailing list. Keeps us on our toes! :-) Alan P.S. your MWE works fine with the latest lmtx... ___ If your question is of interest to others as well, please add an 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 error with fontstrip in today’s beta
I just updated my minimals installation (2019.04.12 17:43, still not lmtx) and run into this error: lua error > lua error on line 1 in file fontstriptest.tex: ...xmf/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:284: attempt to call a nil value (global 'setfield') 1 >> \starttext 2 3 \showfontstrip 4 5 \stoptext MWE: \starttext \showfontstrip \stoptext Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de 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] caching buffers?
On 4/12/2019 11:00 PM, Henning Hraban Ramm wrote: Ahoi, in my book I use a lot of buffers for examples. These get typeset (compiled) anew on every tex run (i.e. several times per context run). This needs a lot of time and is quite annoying. Is this somehow cacheable, so that it compiles only once per context run or (even better) only if the buffer changed? How does the filter module handle this? I know it uses some checksum. Should I "outsource" my buffers via t-filter? If you need a MWE for this, I’ll assemble one. My actual setup is quite complicated, maybe that’s the problem... \starttext \startbuffer[old-feature] % load the relevant environment if needed It works! \stopbuffer \typesetbuffer[old-feature][frame=on,width=4cm] \stoptext Only when buffers change they will be retypeset. 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] caching buffers?
Ahoi, in my book I use a lot of buffers for examples. These get typeset (compiled) anew on every tex run (i.e. several times per context run). This needs a lot of time and is quite annoying. Is this somehow cacheable, so that it compiles only once per context run or (even better) only if the buffer changed? How does the filter module handle this? I know it uses some checksum. Should I "outsource" my buffers via t-filter? If you need a MWE for this, I’ll assemble one. My actual setup is quite complicated, maybe that’s the problem... Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de 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] luaotfload
On 4/12/2019 5:57 PM, Herbert Voss wrote: will the hack be available? I just uploaded new betas 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] Unwanted uppercase letter in \high{} within bibliography
> On 12Apr19, at 02:28, Huseyin Özoguz wrote:
>
>> As you can see, we get Ème in the output instead of ème.
>> Is this a bug, or did I miss something?
>>
This is a consequence of command=\Word, set for titles. Try
\setupbtx [apa:list:title] [command=]
Explanation: APA specification asks for Words of the title to be capitalized.
If you write your bib dataset correctly (title words capitalized), having
command={\Word}, is unnecessary.
Why \Word capitalizes \high{ème} is another question - it is only so
sophisticated. Indeed, I do not know if it Capitalizes a Title Correctly
According to English Rules, not capitalizing articles and prepositions…
Furthermore, this mania of capitalizing titles is NOT the practice in French,
so I would set command=, for titles of works in French.
By the way, btx admits:
title:fr={Histoire géographie EMC 5\high{ème}, cycle 4},
title:en={Geographical History EMC 5\high{th}, 4\high{th} cycle},
to be used advantageously in multi-lingual documents or multi-lingual use of a
single bibliography database.
Alan
--
Alan Braslau
___
If your question is of interest to others as well, please add an 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] luaotfload
Am 12.04.19 um 17:34 schrieb Hans Hagen:
The font files are here:
http://tug.org/~hvoss/Sparks-Bar-Medium.otf
http://tug.org/~hvoss/Sparks-Dotline-Medium.otf
i hacked a faster solution for such fonts (now I need some 25 sec for
the initial caching so probably less on your machine and < 0.1 sec for
loading the cached font)
thanks,
will the hack be available?
Herbert
-rw-r--r-- 1 voss voss 34412 Apr 11 18:54 Sparks-Bar-Medium.otf
-rw-r--r-- 1 voss voss 403776 Apr 11 18:54 Sparks-Dotline-Medium.otf
These make a pretty good case for using proper drawing package,
\definefont[sparkBarMedium][file:Sparks-Bar-Medium.otf:mode=node;+calt]
\definefont[sparkDotlineMedium][file:Sparks-Dotline-Medium.otf:mode=node;+calt]
\starttext
Text
{\sparkBarMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}}
Text
Text
{\sparkDotlineMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}}
Text
\stoptext
Herbert
___
If your question is of interest to others as well, please add an
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] luaotfload
On 4/12/2019 3:17 PM, Herbert Voss wrote:
Hello all,
If I run the following document on a 8 GByte RAM Linux machine.
It takes more than 30 minutes until luaotfload has build
the cache for Sparks-Dotline-Medium.otf. If I run another
Program in the background that it never ends (too less memory).
On my Mac the first run with context (upcoming TL2019) needs 9.5 Gbyte
memory and nearly 100% CPU load to scan the Sparks-Dotline font.
This one is, of course, 400 kB big, but why do we need
more than 8 GByte Ram??
- the cpu load is puzzling: assuming that you have multiple cores,
luatex will only use one core
- the 30 min on linux is probably due to swapping
- the 8 gig in general is a side effect of the way this font is using
pair positioning (half a billion pairs due to classes where most pairs
are dummies)
The font files are here:
http://tug.org/~hvoss/Sparks-Bar-Medium.otf
http://tug.org/~hvoss/Sparks-Dotline-Medium.otf
i hacked a faster solution for such fonts (now I need some 25 sec for
the initial caching so probably less on your machine and < 0.1 sec for
loading the cached font)
-rw-r--r-- 1 voss voss 34412 Apr 11 18:54 Sparks-Bar-Medium.otf
-rw-r--r-- 1 voss voss 403776 Apr 11 18:54 Sparks-Dotline-Medium.otf
These make a pretty good case for using proper drawing package,
\definefont[sparkBarMedium][file:Sparks-Bar-Medium.otf:mode=node;+calt]
\definefont[sparkDotlineMedium][file:Sparks-Dotline-Medium.otf:mode=node;+calt]
\starttext
Text
{\sparkBarMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}} Text
Text
{\sparkDotlineMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}} Text
\stoptext
Herbert
___
If your question is of interest to others as well, please add an 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
___
[NTG-context] luaotfload
Hello all,
If I run the following document on a 8 GByte RAM Linux machine.
It takes more than 30 minutes until luaotfload has build
the cache for Sparks-Dotline-Medium.otf. If I run another
Program in the background that it never ends (too less memory).
On my Mac the first run with context (upcoming TL2019) needs 9.5 Gbyte
memory and nearly 100% CPU load to scan the Sparks-Dotline font.
This one is, of course, 400 kB big, but why do we need
more than 8 GByte Ram??
The font files are here:
http://tug.org/~hvoss/Sparks-Bar-Medium.otf
http://tug.org/~hvoss/Sparks-Dotline-Medium.otf
-rw-r--r-- 1 voss voss 34412 Apr 11 18:54 Sparks-Bar-Medium.otf
-rw-r--r-- 1 voss voss 403776 Apr 11 18:54 Sparks-Dotline-Medium.otf
\definefont[sparkBarMedium][file:Sparks-Bar-Medium.otf:mode=node;+calt]
\definefont[sparkDotlineMedium][file:Sparks-Dotline-Medium.otf:mode=node;+calt]
\starttext
Text
{\sparkBarMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}} Text
Text
{\sparkDotlineMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}}
Text
\stoptext
Herbert
___
If your question is of interest to others as well, please add an 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] Endnote list difference, MKIV and LMTX
On 4/12/2019 3:27 AM, Rik Kabel wrote:
List,
With the following example, endnotes are set differently with MKIV and
LMTX – incorrectly under LMTX. (MKIV 20190404, LMTX 20190411)
The problem disappears if /either//or both/ of the first two lines are
removed, but of course those usually serve an important purpose.
\setupbodyfont [12pt]
\setupindenting[yes,small]
\starttext
\chapter{Testing}
\dorecurse{5}{\samplefile{ward}\endnote{\samplefile{lorem}}\par}
\chapter{Notes}
\placenotes[endnote]
\stoptext
A workaround is to place \placenotes in a group with indenting turned off.
I found the reason .. later this day an update.
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] luatex crash around page 1000
Am 12.04.2019 um 07:36 schrieb Akira Kakuto: >> mtx-context | fatal error: return code: -1073741571 > > I suspect that may be a limitation in 32bit binary. > Try to install 64bit ConTeXt if you are using 32bit one > and your OS is 64bit. > I'm already on 64bit, so that won't help here. The event manager says, that it is a stack exhaustion (0xc0fd, STATUS_STACK_OVERFLOW). The PDF is data driven and I need to call a lot of functions per page to collect all components and values for a complete 'Mech. This seems to sum up and I just run out of stack memory after around 1000 pages. Screenshots from the event manager (application error), Process Explorer (peak memory values) and an outdated version of the PDF can be found here https://spideroak.com/browse/share/indiego/public/RogueTech/ Peter ___ If your question is of interest to others as well, please add an 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] Unwanted uppercase letter in \high{} within bibliography
Hello @list,
I have an unwanted output that might be a bug in my bibliographies.
Consider this MWE :
\setuppapersize[S4]
\mainlanguage[fr]
\language[fr]
\startbuffer[bib]
@book{Manuel5,
editor = {Martin Ivernel and Benjamin Villemagne and Jean Hubac},
title = {Histoire Géographie EMC 5\high{ème}, cycle 4},
publisher = {Hatier},
address = {Paris},
year = {2016},
pagetotal = {398},
language = {french}
}
\stopbuffer
\usebtxdataset[bib.buffer]
\definebtxrendering
[biblio]
[apa]
[numbering=no,
sorttype=cite,
title="Bibliographie"]
\starttext
\nocite[Manuel5]
\placelistofpublications
\stoptext
As you can see, we get Ème in the output instead of ème.
Is this a bug, or did I miss something?
Regards,
Damien Thiriet
Hi,
same issue here with \low and \lohi – I don't know if it is a bug or for
purpose.
But there is a simple workaround:
Dirty workaround: \high{\color[white]{e}\hskip-1.3ex ème}
Maybe better: \lohi{\color[white]{b}}{ème}
--
Huseyin Özoguz
E-Mail: h.oezo...@mmnetz.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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Prevent indentation after itemize
Hello, thanks Aditya for the explaining example! I added the sample to wiki: https://wiki.contextgarden.net/Indentation Best regards, Lukas indentnext=auto means that the next paragraph will be indented when there is a blank space and not indented when there is no blank space. So (untested) \setupindenting[medium,yes] \setupitemize[indentnext=auto] \starttext \startitem \item One \stopitem This paragraph should be indented. \startitemize \item Two \stopitemize This paragraph should not be indented. \stoptext Aditya -- Ing. Lukáš Procházka | mailto:l...@pontex.cz Pontex s. r. o. | mailto:pon...@pontex.cz | http://www.pontex.cz | IDDS: nrpt3sn | IČO: 40763439 Bezová 1658 147 14 Praha 4 Mob.: +420 702 033 396 ___ If your question is of interest to others as well, please add an 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] Difference in right justification in LMTX
Yes. I’ve deleted my lmtx installation directory and fetched the install .zip from Pragma ADE web site and ran install.bat, to double check. De : Hans Hagen Envoyé le :jeudi 11 avril 2019 22:59 À : Joseph Canedo; mailing list for ConTeXt users Objet :Re: [NTG-context] Difference in right justification in LMTX On 4/11/2019 8:07 PM, Joseph Canedo wrote: > Thanks Hans. I’ve ran install.bat to update my LMTX local copy (ran > without apparent errors) and reran context command on my MWE, but I am > afraid I see no difference. > > Not sure if I missed any step or not. it works here did the update download files and remake the format? 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] luatex crash around page 1000
On 4/12/2019 7:36 AM, Akira Kakuto wrote: mtx-context | fatal error: return code: -1073741571 I suspect that may be a limitation in 32bit binary. Try to install 64bit ConTeXt if you are using 32bit one and your OS is 64bit. Indeed. Most memory or stack related overflows in the engine itself are reported. Maybe running with the task manager open will reveal an increase of memory. 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 ___
