- ntg-context - NTG Mailing Lists

SyncTeX and Skim/TeXShop
by Nicola Vitacolonna 10 Apr '19

10 Apr '19

Hi, is anyone using ConTeXt with Skim, or TeXShop, on macOS? SyncTeX used to work fine with ConTeXt in both apps. Now, it seems that ConTeXt has started to generate a .synctex file rather than a .synctex.gz, and the format seems to have changed (?). As I haven’t followed recent (or perhaps not so recent) developments in this area, do you have any suggestions to make SyncTeX work again? I am using Skim, but any PDF viewer would be fine if Skim cannot be used for the purpose any longer. Thanks in advance, Nicola

3 2

Referencing the page on which an endnote was generated
by Rik Kabel 09 Apr '19

09 Apr '19

List, I would like to create headings for the endnotes appendix chapter of a book with headings like "Notes for pages x–y" but can find no way to capture x and y. Is there a way to get those page numbers to insert into the header? -- Rik

1 0

Emacs with context lmtx
by Fabrice Couvreur 09 Apr '19

09 Apr '19

Hi, I compile all my files with Emacs and standalone context. I would like to compare context lmtx. I added this in my .emacs file but it does not work. ############################################################################# (eval-after-load "context" '(setq TeX-command-list (cons '("ConTeXt" "PATH=/home/viserion/context/tex/texmf-linux-64/bin:$PATH context --purgeall %s" TeX-run-command nil t :help "Run context (MarkIV)") TeX-command-list) ("ConTeXt" "PATH=/home/viserion/data/context/tex/texmf-linux-64/bin:$PATH context --purgeall %s" TeX-run-command t t :help "Run context (LMTX)") t) ) ############################################################################# For information about GNU Emacs and the GNU system, type C-h C-a. File mode specification error: (wrong-type-argument symbolp (ConTeXt PATH=/home/viserion/data/context/tex/texmf-linux-64/bin:$PATH context --purgeall %s TeX-run-command t t :help Run context (LMTX))) Thank you. Fabrice

2 4

endnotes customizing how?
by Hans van der Meer 09 Apr '19

09 Apr '19

In typesetting my endnotes with \placenotes[endnote] I seem unable to unfluence the text characteristics. I tried things like (1) \setupnotes[endnote][textcolor=blue] (2) changed fonts before the \ bgroup\bf\placenote\egroup call (3) \startsetups[setups:endnotes] \setupwhitespace[0pt] \stopsetups % textstyle influences endnotemarker in the text. \setupnote[endnote][textcommand=\hifnmarker,before=\directsetup{setups:endnotes}] (4) \setupnotes[endnote][bodyfont=italic] Where (3) made a difference in linespacing, nothing else does. How can one determine the text characteristics of the endnotes? dr. Hans van der Meer

3 2

Expanding text across two table cells
by Todd DeVries 08 Apr '19

08 Apr '19

Hello, I use a progress note format which contains information that doesn't change much from session to session. Items like date, location, people attending a session. I would like to include two longer items, a diagnostic field and info about guardianship at the end of a table. Both of these fields should span two cells in the table and wrap to the full width. Currently, they wrap to the width of the first table column. The cells appear to be spanned correctly, but the text does not extend. What am I missing? Thank you for the assistance. \startcomponent c_DATE_clientcode_progress \project prj_cases \startsection[title=Counseling Progress Note, reference=DATE_clientcode] \placetable{Meeting Info} {\bTABLE \bTR \bTD \ptitle{Client Name}:~John Smith \eTD \bTD \ptitle{Billing code}:~90834 \eTD \eTR \bTR \bTD \ptitle{Date}:~April 8, 2019 \eTD \bTD \ptitle{Start \& stop time}~12:00-13:00 \eTD \eTR \bTR \bTD \ptitle{Next appointment}:~April 15, 2019 \eTD \bTD \ptitle{Punctuality}:~On time. \eTD \eTR \bTR \bTD \ptitle{Location of Service}:~Office \eTD \bTD \ptitle{Those in attendance}:~Counselor and John \eTD \eTR \bTR \bTD[n=2] \ptitle{Diagnosis}:~Adjustment Disorder, Unspecified (F43.20). \eTD \eTR \bTR \bTD[n=2] \ptitle{Children: Location / availability of parent / guardian}:~Not applicable. \eTD \eTR \eTABLE} Todd DeVries *Phone: (208) 847-5996* “Everyone must believe in something. I believe I'll go canoeing.” — Henry David Thoreau

2 2

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