April 2019 - ntg-context - NTG Mailing Lists

Filterpages is broken in LMTX
by Markus Finke 08 Apr '19

08 Apr '19

\setuppapersize [A5] [A4, landscape]  \setuparranging [2SIDE]   \starttext  \filterpages[test.pdf][1:6][]  \stoptext Thank you, Markus

1 0

Ctx LMTX + Lua 5.4
by Procházka Lukáš Ing. 08 Apr '19

08 Apr '19

Hello, I'm using a custom .dll in Ctx (my own .dll written in C with some extensions to Lua). Whenever Ctx started to use a newer version of Lua, I rebuilt the .dll with the appropriate version of lua*.dll. With the latest (non-LMTX) Ctx, I used Lua53.dll from: http://www.w32tex.org/toolsw32/lua53lib.zip (THIS LINK IS NO MORE VALID!) and https://www.tug.org/svn/texlive/trunk/Master/bin/win32/lua53.dll (thanks Akira in the mailing thread "Building a custom .dll to work with ConTeXt (LuaTeX)"). I would like to "upgrade" my .dll to work with Ctx LMTX - where could I find the appropriate lua54lib.zip (.lib and Lua54.dll for Ctx LMTX)? Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS: nrpt3sn | IČO: 40763439 Bezová 1658 147 14 Praha 4 Mob.: +420 702 033 396

2 1

Variable name in lua and lmtx
by Otared Kavian 08 Apr '19

08 Apr '19

Hi Hans, While testing the new LuaMetaTeX with an old project, I noticed that lmtx crashed when I had variables named « numéro » and « prénom » as in local n, numéro, email, Nom, prénom When I changed these to local n, numero, email, Nom, prenom the file was typeset without problem. So my question is: should one avoid using UTF characters in variable names now? Thanks in advance for your attention. Best regards: OK

2 1

Re: [NTG-context] follow up
by Jeong Dal 08 Apr '19

08 Apr '19

Dear Otared, I checked the both cases in the terminal and found that there is no problem in the installation. It call “mtxrun" in right place depending on MKIV or LMTX. Actually, files which doesn’t need files in texmf-local folder are compiled well in both installations. The problem is occurred when the file tried to read files in texmf-local folder. In that case, if it is compiled well in MKIV, then it had a problem in LMTX and vice versa. I didn’t try to use a symbolic link. Since I don’t have any problem to compile files under LMTX so far, I will use LMTX mainly. So I’ll left my previous problem for a while. Thank you for your help. Best regards, Dalyoung > Subject: Re: [NTG-context] follow up > Message-ID: <F894514C-8E72-4743-B05D-B438EFE4F332(a)gmail.com <mailto:F894514C-8E72-4743-B05D-B438EFE4F332@gmail.com>> > Content-Type: text/plain; charset="utf-8" > > Dear Dalyoung, > > Actually when you have added > > export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin > > either in your engine file (using TeXShop), or when typesetting from the Terminal, then you don't need to use mtxrun --autogenerate in order to typeset a file with LuaMetaTeX: you can just have > > /context-osx-64/tex/texmf-osx-64/bin/context myfile.tex > > in this way you can use any mode you wish. > > Or have I misunderstood the issue you are asking about? > > Best regards: OK

1 0

context lmtx
by Hans Hagen 08 Apr '19

08 Apr '19

Hi, As some (and hopefully more) users are testing lmtx, here is some more information about what to watch for. - There are no changes at the macro level that would not have occurred at some point when using luatex. For instance, if \pagewidth doesn't work, that is because it is now simply gone, while before it was a temporary compatibility hack. It is some backend related measure that did more good than bad and was never meant for users. - In MkIV most of the backend code is done in Lua, and ConTeXt never used much of the engine. We now simply do all backend stuff in Lua. That also means that the pdf.* namespace is no longer supposed to be used at the user level. It might get hidden completely at some point, or maybe emulated to some extend but again, that was never meant to be a user level interface (in context). - The same is true for images. I might decide to keep the img namespace but we have different mechanisms so again, img was never meant for user level usage (in context). In lmtx the engine is no longer really involved in image inclusion at all (so we went from 'some' to 'none' in context). - Directions (there was some message about that) have a high level interface that should be used because there can be interferences otherwise (read: therefore no support for low level hacking). The directional model in luametatex has been overhauled and to what extent i will backport that to luatex is undecided (think of compatibility issues; it also depends on further experiments; and after all, it works ok in luatex) but that should not affect mkiv (and using luatex). - Font handling was already under Lua control in context so nothing changed there apart from that also tfm loading is now delegated (but i suppose that not many users use tfm fonts). The new setup will provide some interesting new options that will be explored in the future but there we're talking of non-typical usage (for those wondering about generic usage of the font loader: we could always do some more in context so the generic usage is not affected.) - Performance is in hit by all this because a lua backend is of course slower than native c but we gain a back in other areas, so overall performance is not touched (and actually a lot can be gained due to other side effects; the same is true for the memory footprint; now that luatex 1.10 is out I can also use some of its features.). - Some problems reported (like clash in cache) are easy to solve. As are some more tricky things like the page injection mechanism, which just happens to depend on alternative low level backend code. I suppose more issues like those will show up in the coming weeks. - Let me stress that deep down there is still the normal TeX engine, token handler, memory management, macro machinery at work and it will stay as such because nothing can beat the core tex performance. At the macro level context is rather optimized for using it and just in case one wonders if we could benefit from further luafication, the answer is 'no' because as said, tex parsing (and expansion) is very fast, as is the grouping model (which is fundamental to tex). So, we have (and keep) the same hybrid lua, tex, mp model as we already have for over a decade. We use each language for what it is best. - When all users have moved to luametatex i might clean up some code that now is kept around for compatibility (just because, the less code the better, and we can always make a frozen snapshot). But that is something that will go mostly unnoticed. So, thanks for testing, and please keep testing, 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 -----------------------------------------------------------------

1 0

Can not update Context Standalone
by Fabrice Couvreur 08 Apr '19

08 Apr '19

Hi, I have just updated context standalone and I get the following errors : When you want to use context, you need to initialize the tree by typing: . /home/viserion/context/tex/setuptex in your shell or add "/home/viserion/context/tex/texmf-linux-64/bin" to PATH variable if you want to set it permanently. This can usually be done in .bashrc, .bash_profile (or whatever file is used to initialize your shell). [viserion@archlinux context]$ mtxrun --generate bash: /home/viserion/bin/mtxrun: Aucun fichier ou dossier de ce type [viserion@archlinux context]$ context --make /home/viserion/texlive/2018/bin/x86_64-linux/context: ligne 2: /home/viserion/bin/mtxrun: Aucun fichier ou dossier de ce type [viserion@archlinux context]$ Thanks Fabrice

1 1

luametatex : command not found
by Fabrice Couvreur 08 Apr '19

08 Apr '19

Hi, My system is unix and my platform is linux-64. I installed ConTeXt LMTX as described, namely in my home and in the directory /data /context/ I then tried to compile but without success a file : [viserion@archlinux ~]$ /home/viserion/data/context/tex/texmf-linux-64/bin/context area.tex mtx-context | run 1: luametatex --fmt="/home/viserion/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en" --jobname="area" --lua="/home/viserion/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui" --c:currentrun=1 --c:fulljobname="./area.tex" --c:input="./area.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/home/viserion/data/context/tex/texmf-linux-64/bin" "cont-yes.mkiv" sh: luametatex : commande introuvable mtx-context | fatal error: return code: 32512 [viserion@archlinux ~]$ Thanks Fabrice

2 3

Re: [NTG-context] follow up
by Jeong Dal 08 Apr '19

08 Apr '19

Dear Hans and Otared, Thank you for your help. It is OK to use ConTeXt-LMTX in TeXShop and in Atom. I’d like to compile it in LMTX mode or in MKIV mode without running "mtxrun —geneate” when I change mode. Set path to absolute path of mtxrun in the setting doesn’t help. Actually, it is not a problem of ConTeXt. I’ll try it once more. Thank you. Best regards, Dalyoung > 2019. 4. 5. 오후 7:00, ntg-context-request(a)ntg.nl 작성: > > Send ntg-context mailing list submissions to > ntg-context(a)ntg.nl > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.ntg.nl/mailman/listinfo/ntg-context > or, via email, send a message with subject or body 'help' to > ntg-context-request(a)ntg.nl > > You can reach the person managing the list at > ntg-context-owner(a)ntg.nl > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ntg-context digest..." > > > Today's Topics: > > 1. Re: How to update LMTX? (Hans Hagen) > 2. Re: follow up (Hans Hagen) > 3. Re: (no subject) (Hans Hagen) > 4. Re: follow up (Otared Kavian) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 Apr 2019 00:20:32 +0200 > From: Hans Hagen <j.hagen(a)xs4all.nl> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] How to update LMTX? > Message-ID: <4ab6b1ec-62cd-90c8-0f54-b303f025c2b6(a)xs4all.nl> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 4/5/2019 12:09 AM, Alan Braslau wrote: >> On Thu, 4 Apr 2019 23:11:42 +0200 >> Hans Hagen <j.hagen(a)xs4all.nl> wrote: >> >>> (we just don't use rsync) >> >> As rsync can be problematic for some locations >> (TCP port 873 blocked) without the ability to >> tunnel. > > indeed, especially in schools > >> http is most often open. > right and rsync is also very unix centric so on windows one has to use > cygwin (bah) or a mingw version (hard to get); also the rsync protocol > is sometimes updated so then you need matching versions > > 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 > ----------------------------------------------------------------- > > > ------------------------------ > > Message: 2 > Date: Fri, 5 Apr 2019 00:28:19 +0200 > From: Hans Hagen <j.hagen(a)xs4all.nl> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] follow up > Message-ID: <8f908232-5516-b2a7-df76-51eba0c5140e(a)xs4all.nl> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 4/5/2019 12:17 AM, Jeong Dal wrote: >> Dear Hans, >> >> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side. >> But I have a problem to run it. >> >> If it is OK to run a file in LMTX environment, then I got a following >> error when I run it in MKIV environment. >> “I can’t fine a file …../defFonts.tex” even though it is there. >> To resolve it, I run “mtxrun —generate” in MKIV. >> But it invoke the same type error in LMTX. >> Here are the command in Atom editor which I use to run it. >> >> LMTX: >> source /Users/graph/ConTeXtLMTX/tex/setuptex; >> context {filePath} >> MKIV: >> source /Users/graph/ConTeXt/tex/setuptex; >> context {filePath} >> >> I may avoid it by adding “mtxrun —generate” before compiling it. >> But it isn’t a good solution. >> I think that there is a better way to do this. >> Would you please tell me how to fix it or what is a better way? > Does > > <path to>/mtxrun --autogenerate --script context --autopdf {filePath} > > work in your editor? > > 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 > ----------------------------------------------------------------- > > > ------------------------------ > > Message: 3 > Date: Fri, 5 Apr 2019 00:37:27 +0200 > From: Hans Hagen <j.hagen(a)xs4all.nl> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl>, Dmitry > Starostin <starostin.dmitry(a)gmail.com> > Subject: Re: [NTG-context] (no subject) > Message-ID: <2a626d5a-4378-e1f9-2278-d1496f62f810(a)xs4all.nl> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 4/4/2019 9:30 PM, Dmitry Starostin wrote: >> In terminal: >> >> mtxrun --autogenerate --script context --autopdf Test.tex >> >> -> >> >> resolvers | initialization | fatal error: kpse library is accessed >> (key: default_texmfcnf) > this normally means that there is no file database ... context mkiv nor > lmtx doesn't use kpse > > 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 > ----------------------------------------------------------------- > > > ------------------------------ > > Message: 4 > Date: Fri, 5 Apr 2019 08:49:00 +0200 > From: Otared Kavian <otared(a)gmail.com> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] follow up > Message-ID: <84D8FE1D-E7F7-418F-B10F-A141DD6D8CEC(a)gmail.com> > Content-Type: text/plain; charset=utf-8 > > Hi Dalyoung, > > If this can be of any help, here is what I did in order to install LuaMetaTeX on MacOS in order to use it with TeXShop: > > 1) I downloaded from > http://www.pragma-ade.nl/install.htm > the version of the installer for MacOS and installed a folder named context-osx-64 at an appropriate place (actually at /context-osx-64) > > 2) Then I did > sh install.sh > in that folder, and once the download was finished I replaced the directory texmf-local with a symbolic link to my texmf-local directory (which sits somewhere else) > > 3) In the directory > ~/Library/TeXShop/Engines > I created a new file named LuaMetaTeX.engine containing the following three lines: > > #!/bin/bash > > export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin > > /context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf "$1" --purgeall > > 4) Then when opening TeXShop, I can choose from the scroll menu which shows up on the top left of each a tex file, the engine LuaMetaTeX (or I can set it as default in the Preferences) in order to typeset with LuaMetaTeX engine. > > 5) When I need to update the installation I just run again > sh install.sh > from within the directory /context-osx-64 > (The symlink to my texmf-local is not destroyed). > > 6) If I need to typeset a file from a command line in Terminal, then I need to say > > export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin > > before typesetting myfile.tex by saying > > /context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf myfile.tex > > (Note that the above command should be issued when one is already in the directory containing myfile.tex, beacuse otherwise the corresponding pdf file will be created in the wrong place…). > > Best regards: OK > >> On 5 Apr 2019, at 00:17, Jeong Dal <haksan(a)me.com> wrote: >> >> Dear Hans, >> >> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side. >> But I have a problem to run it. >> >> If it is OK to run a file in LMTX environment, then I got a following error when I run it in MKIV environment. >> “I can’t fine a file …../defFonts.tex” even though it is there. >> To resolve it, I run “mtxrun —generate” in MKIV. >> But it invoke the same type error in LMTX. >> Here are the command in Atom editor which I use to run it. >> >> LMTX: >> source /Users/graph/ConTeXtLMTX/tex/setuptex; >> context {filePath} >> MKIV: >> source /Users/graph/ConTeXt/tex/setuptex; >> context {filePath} >> >> I may avoid it by adding “mtxrun —generate” before compiling it. >> But it isn’t a good solution. >> I think that there is a better way to do this. >> Would you please tell me how to fix it or what is a better way? >> >> Thank you for reading. >> >> Best regards, >> >> Dalyoung >> >> >>> >>> Hi, >>> >>> We have worked furiously all day kicking-out extra code, and are pleased >>> to present a lean-and-mean version of luatex with your favorite ConTeXt. >>> Same good taste but only half the calories and a new name: luametatex >>> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can >>> now stand on our own. Of course, good-old luatex and MkIV (as well as >>> MkII) will continue to coexist and be maintained. However, now you will >>> be able to run ConTeXt lmtx on your smart thermostat or on your >>> refrigerator for the Internet of Things - the dawn of a new era! >>> >>> Stay tuned, >>> >>> Alan and Hans >> >> ___________________________________________________________________________________ >> If your question is of interest to others as well, please add an entry to the Wiki! >> >> maillist : ntg-context(a)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 >> ___________________________________________________________________________________ > > > > ------------------------------ > > Subject: Digest Footer > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : https://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > > > ------------------------------ > > End of ntg-context Digest, Vol 178, Issue 19 > ********************************************

2 1

ConTeXt does not respect custom TEXMFHOME location
by Johannes Hermann 08 Apr '19

08 Apr '19

Hello mailinglist, I have a problem with ConTeXt (Texlive 2019) and setting a custom location of TEXMFHOME. After installation I end up with a /usr/local/texlive/2019/texmfcnf.lua as follows: return { content = { variables = { TEXMFHOME = "~/.texlive2019/texmf", }, }, } Now when I place my custom version of publ-aut.lua in the appropriate subfolder it is not used. Although this works when default TEXMFHOME is used. Is this behavior known or is this a bug? Johannes

2 1

Is t-vim still available in LMTX?
by seasoul 08 Apr '19

08 Apr '19

Dear List, I just installed LMTX and start to use. I found t-vim is not installed even I use "modules = all”. So is t-vim still supported and could be used as usual? Or there is the plan to develop a core function to pretty printing? -- Yours Sincerely Diego

2 1