[NTG-context] Re: pdfcrop with context
On Sun, 15 Sep 2024, Bruce Horrocks wrote:
>
>
> > On 15 Sep 2024, at 16:56, Alan Caruanambo
> > wrote:
> >
> > Hello, basically my question is to know if there is a way to use ConTeXt to
> > perform the functions that pdfcrop does.
> >
> > pdfcrop: A Perl script that can either trim pages of any whitespace border,
> > or trim them of a fixed border
>
> The \clip command works on a PDF file.
>
> <https://wiki.contextgarden.net/Command/clip>
>
> But you need to give it exact measurements.
There is an old perl script `pdftrimwhite` which will do the calculations for
you.
mtxrun --script pdftrimwhite
I hadn't used it for a while and I tried it and it fails because it is still
calling context using texexec:
sub RunTeX
{ if ($UsePlain)
{ $result = `pdftex -prog=pdftex -fmt=plain -int=batchmode $tempfile` }
else
{ $result = `texexec --batch --once --purge $tempfile` }
print $result if $Verbose ; $results .= "$result\n" }
I suspect that changing `texexec` to `context` should make it work with the
current installation as well.
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] BUG REPORT: Italic Correction in ConTeXt LMTX
Hello,
I started using ConTeXt LMTX 2 days ago and after some initial testing I
noticed an unexpected behavior regarding italic correction.
In short, I cannot seem to produce italic correction like I could in plain TeX
or even LaTeX.
I've asked the question on TeX StackExchange and another user confirmed the
suspicion in his answer. I would suggest you take a look at it because the
formatting of the question and the answer is prettier than in this plain text
email. Furthermore, a person who provided the answer already did some research.
See the question here:
https://tex.stackexchange.com/questions/724568/how-to-invoke-italic-correction-in-context-lmtx
Here is what I observed:
Compare the kerning produced in between 'r' and 'p' in the word "airport" when
italic correction is applied in plain TeX (compiled with `pdftex`) and in
ConTeXt LMTX (compiled with `luametatex`). Here are the minimal working
examples.
Plain TeX
```
airport (regular font)
{\it air\/}port (italic correction applied)
{\it air}port (no italic correction applied)
\bye
```
ConTeXt LMTX
```
\starttext
airport (regular font)
{\it air\/}port (italic correction applied)
{\it air}port (no italic correction applied)
\stoptext
```
Please confirm if this, in fact, is the issue/bug or if I am not approaching
this correctly. I am brand new to ConTeXt, so it could be me. Thank you in
advance!
Vladimir
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Bug Regarding IIalic Correction in ConTeXt LMTX
Hello,
I started using ConTeXt LMTX 2 days ago and after some initial testing I
noticed an unexpected behavior regarding italic correction.
In short, I cannot seem to produce italic correction like I could in plain TeX
or even LaTeX.
I've asked the question on TeX StackExchange and another user confirmed the
suspicion in his answer. I would suggest you take a look at it because the
formatting of the question and the answer is prettier than in this plain text
email. Furthermore, a person who provided the answer already did some research.
See the question here:
https://tex.stackexchange.com/questions/724568/how-to-invoke-italic-correction-in-context-lmtx
Here is what I observed:
Compare the kerning produced in between 'r' and 'p' in the word "airport" when
italic correction is applied in plain TeX (compiled with `pdftex`) and in
ConTeXt LMTX (compiled with `luametatex`). Here are the minimal working
examples.
Plain TeX
```
airport (regular font)
{\it air\/}port (italic correction applied)
{\it air}port (no italic correction applied)
\bye
```
ConTeXt LMTX
```
\starttext
airport (regular font)
{\it air\/}port (italic correction applied)
{\it air}port (no italic correction applied)
\stoptext
```
Please confirm if this, in fact, is the issue/bug or if I am not approaching
this correctly. I am brand new to ConTeXt, so it could be me. Thank you in
advance!
Vladimir
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Error after latest update
On Tue, 6 Aug 2024, Shiv Shankar Dayal wrote: > Hi, > > I do not remember where it came from, probably AMS Math or something like > that. It comes from plain: ❯ pdftex This is pdfTeX, Version 3.141592653-2.6-1.40.26 (TeX Live 2024/Arch Linux) (preloaded format=pdftex) restricted \write18 enabled. **\relax entering extended mode *\show\multispan > \multispan=macro: #1->\omit \mscount #1\relax \loop \ifnum \mscount >\@ne \sp@n \repeat . <*> \show\multispan Aditya___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Back in the 90s
On 4/13/2024 2:12 PM, Riviera Taylor wrote: Hello, I was reading about the history of ConTeXt in the Not So Short Introduction To ConTeXt and I have a historical question. I noticed that the PDF specification was published in 1993 yet ConTeXt was invented in 1991. The book suggests that PDF output was handled by the PdfTeX engine in MKII in 2005. What sort of output did the software produce before PdfTeX was introduced? Was this the same as the output produced by the software before the publication of the PDF specification? 2005 is when we started with luatex which is a follow up on pdftex, and pdftex is more a mid 90's thing; we immediately adopted pdftex (which made some believe that context depended on pdftex which is not true) anyway, we started with dvi which needs a postprocessor to go to some printer format like specific hp or more general postscript but also can drive viewers we went from epson dot matrix printer -> early 300 dpi laser -> 600 dpi laser printer -> high speed oce 512 dpi printer (metric) -> high speed oce 600 dpi printer (+ crappy canon color laser printer) -> fast page-wide hp color inkjet office printer in mkii all is controlled by backend drivers, that use so called specials to support color, hyperlinks, images so a workflow can have - dvipsone : high quality postscript - dviwindo : viewer with typeone support and hyperlinks - acrobat : postscript to pdf and as all these external backends have their demands we could handle all these things in an abstract way (that way one could also drive printer properties like duplex or paper bins etc from a tex job) that meant that when pdf came around we could almost immediately support most of the interactive features in a dvi -> ps -> acrobat workflow when pdftex came around the intermediate step of postscript could be avoided which btw was also possible with dvipdfm(x) so we also supported that so to summarize, it went from tex -> dvi -> printer format tex -> dvi -> postscript -> more generic printer format tex -> dvi -> pdf -> print from acrobat tex -> pdf -> print from pdf viewer in the meantime we are pdf (as from that one can produce other formats) Hans (btw, the fact that we could easily support pdf was also a reason why at that time some adobe folk in nl used documents produced by context to show somewhat extrems usage of interactive features, thanks to the fact that tex can adapt to such new situations, also via the dvi route in this case with pdfmarks; at that time pdf usage - and features - was a bit more dualistic: ps replacement format versus storage and preview format, but that's a different story; but it still shows in how the standard evolved) - 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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Back in the 90s
Hello, I was reading about the history of ConTeXt in the Not So Short Introduction To ConTeXt and I have a historical question. I noticed that the PDF specification was published in 1993 yet ConTeXt was invented in 1991. The book suggests that PDF output was handled by the PdfTeX engine in MKII in 2005. What sort of output did the software produce before PdfTeX was introduced? Was this the same as the output produced by the software before the publication of the PDF specification? Kind regards, Riviera she, her, hers https://wiki.contextgarden.net/User:River ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Sorry for once more asking, i am at Work
Hi Uschi, I think there are two separate issues. The first is possible trouble with the install from the ConTeXt garden. (Maybe this is related to “startup error : no format file given, quitting.”) The second is that you call PdfLaTeX to typeset your document, even though I know that is not what you intend. Since you have TeX Live, I recommend you get the ConTeXt in TeX Live working first, then decide if you need the latest ConTeXt from the garden. > On Feb 20, 2024, at 7:21 AM, Pablo Rodriguez via ntg-context > wrote: > > The engine you are using is pdfTeX (from TeX Live 2023). In ConTeXt > terms, this is almost ancient (»uralt«). Just to clarify, TeX Live 2023 has a perfectly good, rather up-to-date version of ConTeXt. I’m using it to typeset books and papers with all sorts of MetaFun craziness. However, if I attempt to typeset one of these ConTeXt documents using PdfLaTeX, I get exactly the same error and log file that you get. I don’t know how you are calling PdfLaTeX to typeset your document, context-test.tex, but that is what you are doing. Until you get that straightened out, it won’t matter what version of ConTeXt you have installed. Gavin ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Sorry for once more asking, i am at Work
On 2/20/24 14:45, Ursula Hermann wrote: > Dear Pablo, Dear List > > I have done all you told me yesterday. > > What I do not understand is that the Diagnosis in WinEdt 11 says, > that everything is ok. Also the PDF-Viewer. Sorry, but I can't copy > it, so I tell what I see. What I do not understand, because there is > no PDF Sorry, dear Uschi, but I’m afraid that I’m on Linux and WinEdt is totally unknown to me. That being said, if the messages from your computer are in German, there is no problem with the language (after all, https://www.deepl.com/ is an option too). Reading your log (which I simply ignored and Gavin took care to read it [totally my fault]), the first line you get is: This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023) (preloaded format=pdflatex 2024.2.6) 19 FEB 2024 12:41 The engine you are using is pdfTeX (from TeX Live 2023). In ConTeXt terms, this is almost ancient (»uralt«). ConTeXt MkII used pdfTeX as engine. In MkIV, the engine is LuaTeX. The latest engine is LuaMetaTeX for what is named either LMTX or MkXL. The format file is for pdfLaTeX, so ConTeXt cannot really do anything with it. It is consistent that ConTeXt complains about not finding the format file. > But now I tried to do what you have told me and the last line, Pablo > in cmd.exe says the same, what I get, if I compile: no format five > given, quitting. If you still happen to have the brand new installation on your desktop (and "test-doc.tex" [sorry, but redo if required]), open the command prompt and do the following: cd %USERPROFILE%\Desktop set PATH=%USERPROFILE%\Desktop\context\tex\texmf-mswin\bin For that window (or session), your system will be able to find only the path to the latest ConTeXt. This will prevent TeX Live 2023 messing with ConTeXt (well, if system-wide paths are not set for TeX Live [you might check that with "echo %PATH%" after setting the path as explained in the previous command]). After that, you may run: mtxrun --generate && context test-doc.tex If this works, the installation of TeX Live seems to set paths in a way that prevent ConTeXt to work. In that case, you would have to ask about that on the TeX Live list. I hope it helps now, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Sorry for once more asking, i am at Work
Hi Uschi, The log file is certainly helpful. It tells me two things. First, you have TeX Live 2023 installed. TeX Live 2023 has a good version of ConTeXt. Unless you need specific, newer ConTeXt features, you can use the ConTeXt version in TeX Live that you already have. Second, when you tried to typeset your file, context-test.tex, your computer attempted to use pdftex rather than ConTeXt. To figure out why it did that, we need to know how you are doing the typesetting. Do you use a command on the command line? Are use using an editor that has a “typeset” button? Something in that part of the process needs to be changed so the typesetting uses ConTeXt rather than pdftex. Gavin > On Feb 19, 2024, at 5:06 AM, Ursula Hermann > wrote: > > Dear List, > I have done the new download at Work. After compiling is always the same: > Command Line: context.exe --synctex=-1 "context-test.tex" > Startup Folder: > C:\Users\Hermann\Downloads\context-mswin\tex\texmf-context\tex\context\test\mkiv > startup error : no format file given, quitting > I wrote on Wednesday last week. I also did an download of cont- lmt and cont- > tmf. Don’t know if there is a mistake which is my fault? > I don’t know, maybe important: > The log file says: > This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023) (preloaded > format=pdflatex 2024.2.6) 19 FEB 2024 12:41 > entering extended mode > restricted \write18 enabled. > %&-line parsing enabled. > **context-test.tex > (./context-test.tex > LaTeX2e <2023-11-01> patch level 1 > L3 programming layer <2024-01-22> > ! Undefined control sequence. > l.1 \starttext > ? ! Emergency stop. > l.1 >End of file on the terminal! > Here is how much of TeX's memory you used: > 16 strings out of 474221 > 403 string characters out of 5750189 > 1922978 words of memory out of 500 > 22371 multiletter control sequences out of 15000+60 > 558069 words of font info for 36 fonts, out of 800 for 9000 > 1141 hyphenation exceptions out of 8191 > 12i,0n,13p,58b,8s stack positions out of 1i,1000n,2p,20b,20s > ! ==> Fatal error occurred, no output PDF file produced! > Uschi > Von: Ursula Hermann > Gesendet: Mittwoch, 14. Februar 2024 14:16 > An: 'mailing list for ConTeXt users' > Betreff: AW: Sorry for once more asking, i am at Work > Dear Hans, > This was before you wrote, that you did an new upload, but i saw it in the > installation. Because there were more files. > Uschi > Von: Ursula Hermann > Gesendet: Mittwoch, 14. Februar 2024 13:42 > An: 'mailing list for ConTeXt users' > Betreff: Sorry for once more asking, i am at Work > So after a new update on my Computer at Work, I did once more download the > installation. After compiling with context-mswin I got this file > Command Line: context.exe --synctex=-1 "context-test.tex" > Startup Folder: > C:\Users\Hermann\Downloads\context-mswin\tex\texmf-context\tex\context\test\mkiv > startup error : no format file given, quitting > > ConTeXt Compilation Report (Pages: 0) > Errors: 0 Warnings: 0 Bad Boxes: 0 > Did I something wrong? > Uschi > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl > webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) > archive : https://github.com/contextgarden/context > wiki : https://wiki.contextgarden.net > ___ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Sorry for once more asking, i am at Work
Dear List, I have done the new download at Work. After compiling is always the same: Command Line: context.exe --synctex=-1 "context-test.tex" Startup Folder: C:\Users\Hermann\Downloads\context-mswin\tex\texmf-context\tex\context\test\mkiv startup error : no format file given, quitting I wrote on Wednesday last week. I also did an download of cont- lmt and cont- tmf. Don't know if there is a mistake which is my fault? I don't know, maybe important: The log file says: This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023) (preloaded format=pdflatex 2024.2.6) 19 FEB 2024 12:41 entering extended mode restricted \write18 enabled. %&-line parsing enabled. **context-test.tex (./context-test.tex LaTeX2e <2023-11-01> patch level 1 L3 programming layer <2024-01-22> ! Undefined control sequence. l.1 \starttext ? ! Emergency stop. l.1 End of file on the terminal! Here is how much of TeX's memory you used: 16 strings out of 474221 403 string characters out of 5750189 1922978 words of memory out of 500 22371 multiletter control sequences out of 15000+60 558069 words of font info for 36 fonts, out of 800 for 9000 1141 hyphenation exceptions out of 8191 12i,0n,13p,58b,8s stack positions out of 1i,1000n,2p,20b,20s ! ==> Fatal error occurred, no output PDF file produced! Uschi Von: Ursula Hermann Gesendet: Mittwoch, 14. Februar 2024 14:16 An: 'mailing list for ConTeXt users' Betreff: AW: Sorry for once more asking, i am at Work Dear Hans, This was before you wrote, that you did an new upload, but i saw it in the installation. Because there were more files. Uschi Von: Ursula Hermann Gesendet: Mittwoch, 14. Februar 2024 13:42 An: 'mailing list for ConTeXt users' mailto:ntg-context@ntg.nl>> Betreff: Sorry for once more asking, i am at Work So after a new update on my Computer at Work, I did once more download the installation. After compiling with context-mswin I got this file Command Line: context.exe --synctex=-1 "context-test.tex" Startup Folder: C:\Users\Hermann\Downloads\context-mswin\tex\texmf-context\tex\context\test\mkiv startup error : no format file given, quitting ConTeXt Compilation Report (Pages: 0) Errors: 0 Warnings: 0 Bad Boxes: 0 Did I something wrong? Uschi ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Using plain TeX commands in ConTeXt
Thanks for correcting me, Wolfgang. I meant only TeX commands not plan TeX macros. On Wed, Jan 24, 2024 at 9:20 PM Wolfgang Schuster < wolfgang.schuster.li...@gmail.com> wrote: > Shiv Shankar Dayal schrieb am 24.01.2024 um 16:37: > > For example: \kern, \parindent and so on. Rephrasing the question, can > > LuaMetaTeX/ConTeXt compile > > plain TeX files. If yes, how can I do that? > > You mix up two different things here. > > 1. Plain TeX is a collection of TeX macros like ConTeXt or LaTeX. > > 2. LuaMetaTeX is a program like pdfTeX or LuaTeX which provides commands > which are used by above mentioned collections to create macros. > > Even though ConTeXt provides some commands which available in plain TeX > not all of the are supported which means you can't process plain TeX > documents. > > On the other hand commands which are provided by the engine like > \parindent can be used in a ConTeXt document but higher level mechanism > like \setupindenting are the better choice. > > Wolfgang > > -- Respect, Shiv Shankar Dayal ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Using plain TeX commands in ConTeXt
Shiv Shankar Dayal schrieb am 24.01.2024 um 16:37: For example: \kern, \parindent and so on. Rephrasing the question, can LuaMetaTeX/ConTeXt compile plain TeX files. If yes, how can I do that? You mix up two different things here. 1. Plain TeX is a collection of TeX macros like ConTeXt or LaTeX. 2. LuaMetaTeX is a program like pdfTeX or LuaTeX which provides commands which are used by above mentioned collections to create macros. Even though ConTeXt provides some commands which available in plain TeX not all of the are supported which means you can't process plain TeX documents. On the other hand commands which are provided by the engine like \parindent can be used in a ConTeXt document but higher level mechanism like \setupindenting are the better choice. Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
On 1/19/2024 11:00 AM, Henning Hraban Ramm wrote: Am 19.01.24 um 10:31 schrieb Hans Hagen: (that said: luametatex runs fine on my mobile phone) What’s the smallest/oldest device someone tried LMTX on? (We were joking about “Hans’ thermostate and Alan’s fridge“…) Would it run on some 8 bit homecomputer? (I’d guess the RAM is too limited, and loading from datasette would need hours…) Just curious. The smallest i have here is a https://en.wikipedia.org/wiki/RCA_1802 which actually was a very nicely designed thing (also powers the hubble); processors never became cleaner. Now, as the kit I used only had 512 bytes ram (later 2K or so) it really learns one how to program efficiently (thihk of writing a simple game, save and load from cassette player, etc in that space; dynamic adaptive functions and such) and you know where I'm coming from'(later pascal and modula). That said: luametatex has a smaller memory footprint than luatex although nodes are way bigger but even that won't make it run well on an 8 bit processor, assuming it can address 32 bit mem. Context mkii started on 4.7 Mhz intel (386) so now we're 1000 times faster but performance gain is not linear. After all, tex has to compete with other applications running at the same time (browsers, remote clients, media apps, web polling apps, zoom, etc.) so it's kin dof amazing that it actually performs okay. What boosted performance is for instance ssd's. What might boost is ddr5 memory but that has to catch up with ddr4 first. What also boosted luametatex is cpu cache. I remember when taco and I moved to the math part we noticed a drop in performance, until machines got updated with larger cache. We'd just crossed some magic threshold. Actually, I kind of assume that we're stuck with cpu performance but nevertheless luametatex became faster. It helps to develop on an older machine and not on a yearly updated one as that obscures matters. (Not that I'd not like a faster machine, but that comes at a steep price.) Hans ps. In the tranmsition from pdftex to luatex to luametatex one should not underestimate Taco's effort of going from basically unreadable and useless C output by web2c (pascal -> c) to what became the luatex C code base (with embedded original documentation). From that we added more functionality gradually over a decade till luametatex spun off, which then lead to quite a bit of refactoring again (but trying to maintain the spirit of how tex is programmed). - 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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
On 1/18/2024 11:15 PM, Bruce Horrocks wrote: On 18 Jan 2024, at 18:56, Shiv Shankar Dayal wrote: I understand that why it is slow, but the problem is that the difference is too high. My book has lots of math, so perhaps that is the reason. Option 1: Buy or borrow a faster computer. You'll get your desired speed-up far faster than waiting for Hans to make changes, even assuming there is something that can be changed. I'd recommend a Mac M3 :-) As tex is a single core process (ok, the os might delegate some file handling to other cores) it benefits from jump in core speed. I use a 2017 laptop with a reasonable fast intel xeon. I have a few docks spread round with different resolution monitors (1920x1200, 2560×1440, 4096×2160) and performance also depends on the connected monitor. I'd be curious to know how much these new processors impact performance over time because the ages of dohbling performance every year are past. There are several factors that impact performance: tex engine : quite a bit faster in luametatex mp engine : quite a bit faster in luametatex lua engine : not much we can do about but inefficient macros and usage can offset any gain in engine. One thing to keep in mind is that tex is an interpreter and all gets tokenized which is more costly in a 32 bit engine than in an 8 bit one (like pdftex). And although luametatex is more efficient than luatex that gets offset by more features that come at a price, but we still win. It helps a bit to know what tex does and what macros add to that. Simple timing operations is useless as in practice we have less cache hits than with a simple loop test: tex is jumping all over memory. Bottlenecks are often noe where one expects them. Anyway, if one can choose: go for a few high perfotmance cores over dozens of so called efficient cores. (that said: luametatex runs fine on my mobile phone) Option 2: Split your book into a project with each chapter, or even part of a chapter as a separate component and compile only the chapter you are working on. Set up a nighttime (or lunchtime) run to regenerate the entire book while you're away from the computer and speed doesn't matter. Indeed. That's the natural way to deal with large documents. 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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: LuaMetaTeX code
On 1/19/2024 9:31 AM, Shiv Shankar Dayal wrote: I see code like # define luametatex_version 210 # define luametatex_revision 10 # define luametatex_release 10 # define luametatex_version_string "2.10.10" starting with C99 these become unnecessary. Rather they should be like const int luametatex_version=210; const char* luametatex_version_string="2.10.10"; These ensure type-safety in the code and are good coding practice. Good coding practice discussions are wasted on me (you don't want me to look at your tex code -) The versioning is abit special in te xdue to the fact thet some numbers en dup in registers and others as token list (string). I have considered changing that but it would also break some 'testing for tex version' so for now we have to accept this mix of tex/etex/pdftex inheritance. 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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: LuaMetaTeX code
On 1/19/2024 9:26 AM, Shiv Shankar Dayal wrote: Dear Hans, I saw the C code of LuaMetaTeX and I saw a lot of gotos which is not good coding practice. These potions of code which have goto should be refactored. I am a C programmer, but I know very little of TeX. If you can point me towards where should I start for TeX(perhaps TeX Book or TeX for the Impatient), I can help with refactoring of code to make is more efficient/easier. Luametatex evolves out of traditional tex so we have/keep some and although i grew up in the 'anti goto' times (pascal) there are plenty cases where i see no problem. Occasionaly I clean up such bits (when it makes sense). And I'm not going to enter coding practice discussions. Forget about refactoring ... there has already be done a lot of that and we want to stay sort of close to the original (also due to doicumentation). I know the code quite wel now and refactoring is for me counter productive. These are projects running for decades and engines need to be stable so changes come slow. You can compare the luanmetatex source to luatex and pdftex to see how we proiceed. 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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
On Fri, 19 Jan 2024, Hans Hagen via ntg-context wrote:
> On 1/19/2024 12:34 AM, Aditya Mahajan wrote:
> > On Thu, 18 Jan 2024, Hans Hagen wrote:
> >
> >> Of course we'll never be as fast as (pure) plain tex (no layers added) or
> >> latex (which often is advocated as faster than context).
> >
> > I was curious, so did a quick experiment: typeset \input knuth 500 times.
> > Here are the results:
> >
> > pdflatex: 547 pages/sec
> > lualatex: 308 pages/sec
>
> opentype or type 1 ?
type 1. I did not change anything in the defaults. I'll try to figure out how
to load opentype fonts in latex, and test lualatex.
> > MKIV: 130 pages/sec
> > LMTX: 147 pages/sec
>
> that is weird as lmtx is always faster here (we loose some 15% on the backend
> compared to luatex, maybe even more, but we gain back quite a bit elsewhere
> for various reasons)
LMTX is faster for me as well.
> > Interestingly, pdflatex, lualatex, and MkIV all generated pdf with 1112
> > pages, while LMTX generated a pdf with 1250 pages. Both MkIV and LMTX take
> > the same time to run (8.5 sec) but LMTX generates more pages so it is
> > faster.
>
> puzzling
>
> > Of course, this is a meaningless experiment from a practical point of view
> > as a 1000 page document will be more complex than just text.
> % engine=pdftex 1.2
> % engine=luatmetatex 1.6
> % engine=luatex 1.8
> % engine=xetex 2.4
>
> \starttext
>
> \dorecurse{500} {
> \input knuth \par
> }
>
> \stoptext
>
> 125 pages, so how does your test file look
5000 recursions (not 500, sorry about that).
\starttext
\dorecurse{5000}{\ReadFile{knuth}}
\stoptext
I'll send you the PDFs offlist.
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Why LuaMetaTex is so slow?
On 1/19/2024 12:34 AM, Aditya Mahajan wrote:
On Thu, 18 Jan 2024, Hans Hagen wrote:
Of course we'll never be as fast as (pure) plain tex (no layers added) or
latex (which often is advocated as faster than context).
I was curious, so did a quick experiment: typeset \input knuth 500 times. Here
are the results:
pdflatex: 547 pages/sec
lualatex: 308 pages/sec
opentype or type 1 ?
MKIV: 130 pages/sec
LMTX: 147 pages/sec
that is weird as lmtx is always faster here (we loose some 15% on the
backend compared to luatex, maybe even more, but we gain back quite a
bit elsewhere for various reasons)
Interestingly, pdflatex, lualatex, and MkIV all generated pdf with 1112 pages,
while LMTX generated a pdf with 1250 pages. Both MkIV and LMTX take the same
time to run (8.5 sec) but LMTX generates more pages so it is faster.
puzzling
Of course, this is a meaningless experiment from a practical point of view as a
1000 page document will be more complex than just text.
% engine=pdftex 1.2
% engine=luatmetatex 1.6
% engine=luatex 1.8
% engine=xetex 2.4
\starttext
\dorecurse{500} {
\input knuth \par
}
\stoptext
125 pages, so how does your test file look
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 /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Why LuaMetaTex is so slow?
Hi Shiv, ConTeXt’s project structure has many benefits. One is speed. See https://wiki.contextgarden.net/Project_structure. My books and long papers are products, each containing many components (chapters or sections). When I’m working, I have both the product and a component open. I frequently typeset the component as I’m working. This is very quick. I only typeset the entire product if I intend print or send it, or when I need to check some product-wide element like references. Components can be nested, so take this approach to whatever extreme you desire. You can also use buffers if there are specific parts of your book (like diagrams) that demand significant processing. Buffers can save the typeset version of the contents. These will only be typeset again if you change the buffer contents (or if you are typesetting with a different version of ConTeXt.) See https://wiki.contextgarden.net/Command/typesetbuffer My biggest book is about 200 pages. It takes 4 minutes to fully typeset on an M1 Mac. (I saw this time after downloading a new ConTeXt version.) This is mostly due to the 100+ complex TikZ diagrams. However, all of those diagrams are buffered, and when I’m working I only typeset the component. A typical chapter typesets in 1.6 seconds if I haven’t changed the diagrams. (I just did one to check.) That’s fast enough for me. Hope that helps, Gavin > On Jan 18, 2024, at 10:24 AM, Shiv Shankar Dayal > wrote: > > I can process TeXBook in almost an instant using PDFTeX which is about 450+ > pages but my math book takes around 30 seconds averaging ~40 pages/second. > > Why LuaMetaTeX is so slow? How can I speed it up? > -- > Respect, > Shiv Shankar Dayal > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl > webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) > archive : https://github.com/contextgarden/context > wiki : https://wiki.contextgarden.net > ___ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
On 1/18/2024 7:56 PM, Shiv Shankar Dayal wrote: In comparison to LaTeX with LuaHBTeX, ConTeXt with LuaMetaTeX is lightning fast. pdfTeX is 8bit, and Knuth’s plain TeX is very low level – for a fairer comparison, try the TeXbook on LuaMetaTeX (I don’t know if “plain” works though). I understand that why it is slow, but the problem is that the difference is too high. My book has lots of math, so perhaps that is the reason. You can run the texbook with \tracingall and see what actually happens. The texbook uses plain tex (very lightweight) with a dedicated style (also lightweight). On the contrary context uses layers of abstraction, a more complex font, math, structure, page etc etc etc sytstem. In fact, plain tex had to be as it is because otherwise it would take ages to process teh texbook. On a pc one could see the page numbers crawl so in the end wr're quite okay nowadays. If you run context with \tracingall you'll see that more goes on. For me 40 pps sounds not that bad. If you use only text you can get to 500 pps but that's not realistic. Maybe your style is suboptimal. Also, open type fonts, opentype math, unicode, color, etc etc comes at a price. And, compared to pdftex, in most cases luametatex is faster on documents of average complexity. If you also use xml and/or metapost you migh tbe dragged down to a few pages per second while lmtx doesn't suffer much. Anyway, if you think it can be made faster you can always post code to this list that identifies bottlenecks. Of course we'll never be as fast as (pure) plain tex (no layers added) or latex (which often is advocated as faster than context). 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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
Hi, On Thu, Jan 18, 2024 at 7:58 PM Shiv Shankar Dayal wrote: > > > > >> In comparison to LaTeX with LuaHBTeX, ConTeXt with LuaMetaTeX is >> lightning fast. >> >> pdfTeX is 8bit, and Knuth’s plain TeX is very low level – for a fairer >> comparison, try the TeXbook on LuaMetaTeX (I don’t know if “plain” works >> though). > > > I understand that why it is slow, but the problem is that the difference is > too high. > My book has lots of math, so perhaps that is the reason. > For what it is worth, I have a math book (lots of math and references back and forth and some figures) and the 300 pages compiles in around 10s, so 30 pages/s. I don't have too much to compare with, and that is a bit slower than your 40 pages/s (but 40*30 is 1200 and not 450), but I consider that pretty fast. One thing you can try is \enableexperiments[fonts.compact] (as it sounds, it is still experimental). Also, if you do not provide any example code, it will be difficult for people to guess how _you_ can speed up your compilation (if at all). /Mikael ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
In comparison to LaTeX with LuaHBTeX, ConTeXt with LuaMetaTeX is > lightning fast. > > pdfTeX is 8bit, and Knuth’s plain TeX is very low level – for a fairer > comparison, try the TeXbook on LuaMetaTeX (I don’t know if “plain” works > though). > I understand that why it is slow, but the problem is that the difference is too high. My book has lots of math, so perhaps that is the reason. -- Respect, Shiv Shankar Dayal ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
Am 18.01.24 um 18:47 schrieb Pablo Rodriguez via ntg-context: On 1/18/24 18:24, Shiv Shankar Dayal wrote: I can process TeXBook in almost an instant using PDFTeX which is about 450+ pages but my math book takes around 30 seconds averaging ~40 pages/second. Hi Shiv Shankar Dayal, I guess that “The TeXbook” (having been written by Knuth himself) may be optimized for speed. Your math book may use features (I’m guessing again) that require more resources than the features used by “The TeXbook”. Why LuaMetaTeX is so slow? How can I speed it up? https://www.pragma-ade.com/general/manuals/musings.pdf#page=96 might explain why Lua(Meta)TeX is slower. Other chapters in that document from Hans might give you some insight on the reasons why LMTX has to pay a price for being more feature-rich. I got such impression when I read it. Just in case it might help, In comparison to LaTeX with LuaHBTeX, ConTeXt with LuaMetaTeX is lightning fast. pdfTeX is 8bit, and Knuth’s plain TeX is very low level – for a fairer comparison, try the TeXbook on LuaMetaTeX (I don’t know if “plain” works though). Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
On 1/18/24 18:24, Shiv Shankar Dayal wrote: > I can process TeXBook in almost an instant using PDFTeX which is about > 450+ pages but my math book takes around 30 seconds averaging ~40 > pages/second. Hi Shiv Shankar Dayal, I guess that “The TeXbook” (having been written by Knuth himself) may be optimized for speed. Your math book may use features (I’m guessing again) that require more resources than the features used by “The TeXbook”. > Why LuaMetaTeX is so slow? How can I speed it up? https://www.pragma-ade.com/general/manuals/musings.pdf#page=96 might explain why Lua(Meta)TeX is slower. Other chapters in that document from Hans might give you some insight on the reasons why LMTX has to pay a price for being more feature-rich. I got such impression when I read it. Just in case it might help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Why LuaMetaTex is so slow?
I can process TeXBook in almost an instant using PDFTeX which is about 450+ pages but my math book takes around 30 seconds averaging ~40 pages/second. Why LuaMetaTeX is so slow? How can I speed it up? -- Respect, Shiv Shankar Dayal ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: context not producing synctex output that my synctex program can use
Henning and Hans, thanks for the replies. I have two follow-up questions below, as well as some other comments which other synctex users might find useful. On Sun, Nov 12, 2023 at 10:26 (+0100), Henning Hraban Ramm wrote: > Am 12.11.23 um 00:59 schrieb Jim: >> Hi, >> I've read the wiki, looked at workflows-synctex.tex, searched the web, and >> scratched my head, all to no avail. So here I am, cap in hand... >> When I run context, I get a .synctex file which has some information in it, >> but I can't find any invocation of synctex to return anything useful. Nor >> does the okular example in the wiki (https://wiki.contextgarden.net/SyncTeX) >> work for me. Ocular starts, but always on the first page, regardless of >> what line number I give it. >> On the other hand, pdftex creates a .synctex file which my copy of synctex >> find useful. >> I am using the synctex from the current version of texlive: >> This is SyncTeX command line utility, version 1.5 >> Can anyone either >> (a) enlighten me on what I am doing wrong; or >> (b) definitively confirm that context is not currently playing nicely with >> synctex (the wiki notwithstanding) and I should give up this quest for >> now. > ConTeXt doesn’t work with the synctex binary, but with > mtxrun --script synctex Thanks for that pointer. Q1: Should that be in the wiki (https://wiki.contextgarden.net/SyncTeX) somewhere? When I try that out, for example with mtxrun --script synctex --edit --name=a.tex --line=222 a.tex I am rewarded with sandbox | variable 'linenumber' has no checker (I tried various variations on that line I won't bore you with, but I keep getting that error message.) I also tried mtxrun --script synctex --goto --page=4 --x=100 --y=100 a.synctex and that silently returns without apparently doing anything. (While I don't have a 'scite' editor, I created a program called 'scite' that pops a message up on the screen if it is called.) Similar to --edit, mtxrun --script synctex --goto --page=19 --x=400 --y=180 --tolerance=99 --editor=scite a.synctex complains sandbox | variable 'tolerance' has no checker Although I don't know lua, the code is easy enough to read, but a short dive in to mtx-synctex.lua did not enlighten me. Q2: any enlightening comments on why I am getting these complaints. In any case, --find and --report (appear to) give meaningful results, so I can work with those. > Unfortunately, it’s not a drop-in replacement, so it doesn’t work with most > editors. (I was thinking about a translating wrapper script, but didn’t do > anything yet.) So much code to write, so little time ...:-) My immediate concern is forward search (i.e., editor tells viewer which page to display) and that one should be easy for me to create a wrapper. (I use emacs + auctex, which calls the synctex program, so writing my own synctex wrapper looks easy. Hopefully I won't regret using the word "easy" later.) > AFAIK TeXshop (MacOS) is the only TeX editor that supports ConTeXt’s > workflow. I've been thinking of patching some of evince's more annoying features, if I do, maybe I should look into making it work with context. > ConTeXt’s synctex format is much simpler than the “standard” LaTeX one and > should be at least as good, but alas it needs support from the editors. Indeed! On Sun, Nov 12, 2023 at 12:00 (+0100), Hans Hagen wrote: > On 11/12/2023 10:26 AM, Henning Hraban Ramm wrote: >> Am 12.11.23 um 00:59 schrieb Jim: >>> Hi, >>> >> ConTeXt doesn’t work with the synctex binary, but with >> mtxrun --script synctex > afaik there is no binary ... there is a library that has to be compiled into > a pdf viewer that intercept some 'goto the text file' command and then > launches an editor (afik the library has some heuristics build in wrt boxes > and nesting and so); at the tex end there is also a library that kicks in > addiional code for nodes and the backend (which is why enabling synctex will > have an impact on runtime) > wrt the synctex file, that one is generated by context (so we don't use the > synctex code in luatex and as luametatex has no backend there it's even > completely absent ... context generates the file itself which is also a bit > more efficient) >> Unfortunately, it’s not a drop-in replacement, so it doesn’t work with >> most editors. (I was thinking about a translating wrapper script, but >> didn’t do anything yet.) >> AFAIK TeXshop (MacOS) is the only TeX editor that supports ConTeXt’s >> workflow. > indeed texshop uses the approach that avoids the library and just calls > mtxrun to figure out t
[NTG-context] Re: context not producing synctex output that my synctex program can use
On 11/12/2023 10:26 AM, Henning Hraban Ramm wrote: Am 12.11.23 um 00:59 schrieb Jim: Hi, I've read the wiki, looked at workflows-synctex.tex, searched the web, and scratched my head, all to no avail. So here I am, cap in hand... When I run context, I get a .synctex file which has some information in it, but I can't find any invocation of synctex to return anything useful. Nor does the okular example in the wiki (https://wiki.contextgarden.net/SyncTeX) work for me. Ocular starts, but always on the first page, regardless of what line number I give it. On the other hand, pdftex creates a .synctex file which my copy of synctex find useful. I am using the synctex from the current version of texlive: This is SyncTeX command line utility, version 1.5 Can anyone either (a) enlighten me on what I am doing wrong; or (b) definitively confirm that context is not currently playing nicely with synctex (the wiki notwithstanding) and I should give up this quest for now. ConTeXt doesn’t work with the synctex binary, but with mtxrun --script synctex afaik there is no binary ... there is a library that has to be compiled into a pdf viewer that intercept some 'goto the text file' command and then launches an editor (afik the library has some heuristics build in wrt boxes and nesting and so); at the tex end there is also a library that kicks in addiional code for nodes and the backend (which is why enabling synctex will have an impact on runtime) wrt the synctex file, that one is generated by context (so we don't use the synctex code in luatex and as luametatex has no backend there it's even completely absent ... context generates the file itself which is also a bit more efficient) Unfortunately, it’s not a drop-in replacement, so it doesn’t work with most editors. (I was thinking about a translating wrapper script, but didn’t do anything yet.) AFAIK TeXshop (MacOS) is the only TeX editor that supports ConTeXt’s workflow. indeed texshop uses the approach that avoids the library and just calls mtxrun to figure out the file/line that relates to the position; this is more reliable because there is no need to recompile a viewer when synctex updates you can run mtxrun --script synctex on the synctex file and check what areas are there ConTeXt’s synctex format is much simpler than the “standard” LaTeX one and should be at least as good, but alas it needs support from the editors. simpler in the sense that we only output what is needed for the synchronization to work reliable; fwiw, my collegue already for many years uses context with synctex enabled with sumatra pdf in pretty complex setups: a mix of tex and xml files with deeply nested inputs and it works ok (so we also get to the right spot in an (included) xml file) for synctex to work one has to call context with --synctex or put a directive on the topline of the file. Otherwise you won't get the right jobname. Of course it then still depends on the pdf viewer + lib used if things work out as expected. there isn't much we can do about the viewer part unless tit is not locked into the binary but as flexible like the texshop viewer is 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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: context not producing synctex output that my synctex program can use
Am 12.11.23 um 00:59 schrieb Jim: Hi, I've read the wiki, looked at workflows-synctex.tex, searched the web, and scratched my head, all to no avail. So here I am, cap in hand... When I run context, I get a .synctex file which has some information in it, but I can't find any invocation of synctex to return anything useful. Nor does the okular example in the wiki (https://wiki.contextgarden.net/SyncTeX) work for me. Ocular starts, but always on the first page, regardless of what line number I give it. On the other hand, pdftex creates a .synctex file which my copy of synctex find useful. I am using the synctex from the current version of texlive: This is SyncTeX command line utility, version 1.5 Can anyone either (a) enlighten me on what I am doing wrong; or (b) definitively confirm that context is not currently playing nicely with synctex (the wiki notwithstanding) and I should give up this quest for now. ConTeXt doesn’t work with the synctex binary, but with mtxrun --script synctex Unfortunately, it’s not a drop-in replacement, so it doesn’t work with most editors. (I was thinking about a translating wrapper script, but didn’t do anything yet.) AFAIK TeXshop (MacOS) is the only TeX editor that supports ConTeXt’s workflow. ConTeXt’s synctex format is much simpler than the “standard” LaTeX one and should be at least as good, but alas it needs support from the editors. Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] context not producing synctex output that my synctex program can use
Hi, I've read the wiki, looked at workflows-synctex.tex, searched the web, and scratched my head, all to no avail. So here I am, cap in hand... When I run context, I get a .synctex file which has some information in it, but I can't find any invocation of synctex to return anything useful. Nor does the okular example in the wiki (https://wiki.contextgarden.net/SyncTeX) work for me. Ocular starts, but always on the first page, regardless of what line number I give it. On the other hand, pdftex creates a .synctex file which my copy of synctex find useful. I am using the synctex from the current version of texlive: This is SyncTeX command line utility, version 1.5 Can anyone either (a) enlighten me on what I am doing wrong; or (b) definitively confirm that context is not currently playing nicely with synctex (the wiki notwithstanding) and I should give up this quest for now. Thanks very much. Jim ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: lpdf.registerfontmethod
On 7/7/2023 4:51 AM, Max Chernoff wrote: Hi Hans, In lpdf-emb.lmt, there's a commented-out definition of lpdf.registerfontmethod that I'd like to use. I've uncommented this in my installation and it's worked pretty well for me, so can you please uncomment/enable this by default in the distribution? I'll check it but no time today. btw ... as you like low level hacking ... pdftex has a mechanism called pgc (pdf glyph containers) and these are used when no pk font is found (which also means: no map entry) \pdffont ... = \pdfscale 1000 \pdfglyph 1 100 0 0 100 100 ... pdf code ... \pdfendglyph \pdfendfont of course one needs a matching tfm file. I searched my disk but it looks like i removed all the test files of those times. It was some playground for Thanh and me in the good old pdftex dev days but the outlines from mp at that time were not good enough to use in these containers. (It was when the mp to pdf conmverter showed up in context mkii.) One or these now obsolete sub projects; it was kind of fun anyway. Other experiments, like with saving positions (which originally was a context feature that involved betweeen run dvi parsing with dvipos) did make it into a stable feature eventually (read: documented). The code is still there (in write3.c) but I bet that there is no documentation. 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] lpdf.registerfontmethod
Hi Hans,
In lpdf-emb.lmt, there's a commented-out definition of
lpdf.registerfontmethod that I'd like to use. I've uncommented this in
my installation and it's worked pretty well for me, so can you please
uncomment/enable this by default in the distribution?
If you want further background, this is how I'm using it:
lpdf.registerfontmethod("rawpdf", function(filename, details)
return
details.properties.indexdata[1],
0.001,
function(char)
return char.code, char.width / t3_to_sp
end,
function() end,
function() end
end)
local function make_glyph(codepoint, unicode, width, height, code)
local spec = {
width = width * t3_to_sp,
height = height * t3_to_sp,
depth = 0,
unicode = { utf8.codepoint(unicode or "", 1, -1, true) },
code = width .. " 0 d0 " .. code,
}
local tfmdata = fonts.hashes.identifiers[font.current()]
tfmdata.characters[codepoint] = spec
fonts.dropins.swapone(
"rawpdf",
tfmdata,
{ code = spec },
codepoint
)
fonts.constructors.addcharacters(
font.current(),
{ characters = { [codepoint] = spec } }
)
end
I specifically need something that writes out a raw PDF stream. I'm
using this to write a 4000+ page PDF file to be included by pdfTeX, so I
can't have any XObject indirection or similar, otherwise the number of
objects skyrockets and pdfTeX (+qpdf) gets really slow.
If you're curious, the actual code where I'm using this is here:
https://github.com/gucci-on-fleek/unnamed-emoji/blob/master/source/svg-to-pdf.cld
https://github.com/gucci-on-fleek/unnamed-emoji/blob/master/source/unnamed-emoji.lua
I know that what I'm doing in the .cld file is wildly unsupported, but
I'm the only one who will ever need to run that. I am planning on
distributing the .lua file though, so I'd like to get this change in the
distribution.
I'm also open to using a different interface instead if you don't want
to publicly-expose lpdf.registerfontmethod.
Thanks,
-- Max
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] context-on-web broken
thanks a lot for the overleaf hack Aditya, i once tried to configure
something similar but it did not work!
and thanks for the latexcgi link, it has much more speed in processing,
though that is not important for me (i am learning the basics in my spare
time, so a couple of seconds more or less is ok).
On a quick search i found a lot of Zdeněk Svoboda, but i will try to find
the one of the project and ask him to offer it to the community, I found
context-on-web simple and effective, it even hat a table-generator for easy
things.
El lun, 26 jun 2023 a las 20:39, Hans Hagen via ntg-context (<
ntg-context@ntg.nl>) escribió:
> On 6/26/2023 7:53 PM, Aditya Mahajan via ntg-context wrote:
> > On Mon, 26 Jun 2023, Miguel Diaz via ntg-context wrote:
> >
> >> indeed it is a simple simulation of overleaf (for latex).
> >
> > FWIW, context works on overleaf as well!
> >
> > Simply create a `latexmkrc` file with the following content:
> >
> > ```
> > $pdflatex="context --synctex=1 --result=output %S; cp output.log
> /compile/output.log;cp output.pdf /compile/output.pdf";
> > $recorder=0;
> > $pdf_mode=1;
> I found back this link:
>
> https://davidcarlisle.github.io/latexcgi/testc
>
>
> % !TEX mtxrun --script context
>
> \starttext
>
> \dorecurse{500}{\samplefile{tufte}\par}
>
> \stoptext
>
> Runs 113 pages in 1.13 sec so quite ok for a remote un I guess.
>
> I'm not sure how up to date it is.
>
> (The default is some old tex document using pdftex.)
>
> 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 /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
>
> ___
>
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] context-on-web broken
On 6/26/2023 7:53 PM, Aditya Mahajan via ntg-context wrote:
On Mon, 26 Jun 2023, Miguel Diaz via ntg-context wrote:
indeed it is a simple simulation of overleaf (for latex).
FWIW, context works on overleaf as well!
Simply create a `latexmkrc` file with the following content:
```
$pdflatex="context --synctex=1 --result=output %S; cp output.log
/compile/output.log;cp output.pdf /compile/output.pdf";
$recorder=0;
$pdf_mode=1;
I found back this link:
https://davidcarlisle.github.io/latexcgi/testc
% !TEX mtxrun --script context
\starttext
\dorecurse{500}{\samplefile{tufte}\par}
\stoptext
Runs 113 pages in 1.13 sec so quite ok for a remote un I guess.
I'm not sure how up to date it is.
(The default is some old tex document using pdftex.)
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Off topic: Does a 'free for commercial use' flared-sans font exist in the world?
On 6/18/2023 8:37 PM, Carlos via ntg-context wrote: On Sat, Jun 17, 2023 at 06:53:06PM +0200, Hans Hagen via ntg-context wrote: On 6/17/2023 2:06 AM, linguafalsa--- via ntg-context wrote: On Fri, Jun 16, 2023 at 06:35:49PM +0200, Gerben Wierda via ntg-context wrote: I know this is off topic, but I suspect this community is actually one of the best places to find an answer. It is the best community. And I tell you what. What happened is that all TeX engines have neglected fonts from the beginning. Really? When tex showed up digital font technology was pretty much in flux. And, with metafont being part of the tex ecosystem, one can argue that tex was quite innovative too. Ecosystem. I would be very careful by including an ecosystem there. Yes. Yes. The TeX ecosystem is obviously part of TeX but is not part of the ecosystem of fonts either. And what is done on ecosystems can either benefit or affect ecosystems greatly. And it's a known trait that humans have been known for having more of a flock group mentality for no apparent rationally-based reasons than just being themselves making these decisions/following instincts or whatever and not because of a particular ecosystem, or for the benefit of the latter. With ecosystemn I mean: tex, metafont, cmr fonts, all kind of tools ... evolving into more engines, more fonts, macro packages, distributions, user groups and use group journals, meetings etc And the above does not imply, bear with me here, that metafont was not innovative, but it can be argued that without TeX there is no metafont, so no room is left for errors either. So, yes, it must be innovative. It has to be. There had to be metafont because there was not much else that could provide what tex needed (at that time). Potscript and its fonts came aroudn at the same time and were rather closed technologies. But as soon possible backend drivers (also part of the tex ecosystem) kicked in. Then we got virtual fonts which enhanced tex's capabilities. I really like Optima, and what I really like about it is the 'flared style'. But I would like to move to a flared-sans font that gives me more licensing freedom. I haven't been able to find one after extensive searching. The only one who were reasonably priced (not free) were the URW Classico ones in Adobe Creative Cloud, but those can only be used in Adobe programs like InDesign (and not TeX). Licensing freedom is an oxymoron. There's no freedom in licensing. Only greed. The only extension engine that at one point had a plan in mind, or most of the bases covered in this regard was Omega. One needs morr than plans. Afaik omega was more about input processing and th efont part was mostly going beyond 8 bit fonts but i might have missed something (omega was never productin ready). Notwithstanding the intricacies/details of what may have actually happened with its short lifespan I think it's more than clear the lack of support behind it. I'm not going to delve into what exactly caused its demise or if it was simply the after effect of other projects that contributed to it. It's irrelevant. Hm, its time span was not that short ... I first heard of omega at the eurotex meeting in arnhem where also etex was discussed (and you dont'want me to cite things said there) .. in successive years there have been announcemnts etc. However, for an engine to be used it must work reliable and guiseppes 'aleph' was basically a variant of omega that also had etex on board. In fact, that was supported in context mkii (and some used it because of the input processor which i think was the more innovative thing in omega but i never dived into it, other users did) It makes no sense to discuss into all this as all teams involved in engines have published in user group journals or presented plans at meetings. Also keep in mind that we're talking frontend here; omega is dvi based so like regular tex and etex whatever it does with fonts is not really related to the engine bu tup to the backend: the engine only needs metrics (omega extended tfm into ofm for that). pdftex brought a pdf backend, xetex pipes into a dvi backend, luatex has a pdf backend built in; (nts being related to etec never took of also because it was not that useable and in the meantime pdftex had taken over); there are afaik some very useable japanese tex engines; the fact that dvi survived was due to dvipdfmx development But stand by for a second. I look forward to your quick witted answers. But hear me out Suppose that on my prior message I was referring indeed to 'mkii' and not to 'omega' And also suppose for a second that the term 'omega' is to be replaced with 'mkii' on your reply accordingly After careful observation the resemblance is quite possibly identical, isn't it? and it could also inarguably apply to the circumstances
Re: [NTG-context] Off topic: Does a 'free for commercial use' flared-sans font exist in the world?
On Sat, Jun 17, 2023 at 06:53:06PM +0200, Hans Hagen via ntg-context wrote: > On 6/17/2023 2:06 AM, linguafalsa--- via ntg-context wrote: > > On Fri, Jun 16, 2023 at 06:35:49PM +0200, Gerben Wierda via ntg-context > > wrote: > > > I know this is off topic, but I suspect this community is actually one of > > > the best places to find an answer. > > > > > > > It is the best community. And I tell you what. > > > > What happened is that all TeX engines have neglected fonts from the > > beginning. > > Really? When tex showed up digital font technology was pretty much in flux. > And, with metafont being part of the tex ecosystem, one can argue that tex > was quite innovative too. Ecosystem. I would be very careful by including an ecosystem there. Yes. Yes. The TeX ecosystem is obviously part of TeX but is not part of the ecosystem of fonts either. And what is done on ecosystems can either benefit or affect ecosystems greatly. And it's a known trait that humans have been known for having more of a flock group mentality for no apparent rationally-based reasons than just being themselves making these decisions/following instincts or whatever and not because of a particular ecosystem, or for the benefit of the latter. And the above does not imply, bear with me here, that metafont was not innovative, but it can be argued that without TeX there is no metafont, so no room is left for errors either. So, yes, it must be innovative. It has to be. > > Potscript and its fonts came aroudn at the same time and were rather closed > technologies. But as soon possible backend drivers (also part of the tex > ecosystem) kicked in. > > Then we got virtual fonts which enhanced tex's capabilities. > > > > I really like Optima, and what I really like about it is the 'flared > > > style'. > > > > > > But I would like to move to a flared-sans font that gives me more > > > licensing freedom. I haven't been able to find one after extensive > > > searching. The only one who were reasonably priced (not free) were the > > > URW Classico ones in Adobe Creative Cloud, but those can only be used in > > > Adobe programs like InDesign (and not TeX). > > > > > > > Licensing freedom is an oxymoron. There's no freedom in licensing. > > Only greed. > > > > The only extension engine that at one point had a plan in mind, > > or most of the bases covered in this regard was Omega. > > One needs morr than plans. Afaik omega was more about input processing and > th efont part was mostly going beyond 8 bit fonts but i might have missed > something (omega was never productin ready). Notwithstanding the intricacies/details of what may have actually happened with its short lifespan I think it's more than clear the lack of support behind it. I'm not going to delve into what exactly caused its demise or if it was simply the after effect of other projects that contributed to it. It's irrelevant. But stand by for a second. I look forward to your quick witted answers. But hear me out Suppose that on my prior message I was referring indeed to 'mkii' and not to 'omega' And also suppose for a second that the term 'omega' is to be replaced with 'mkii' on your reply accordingly After careful observation the resemblance is quite possibly identical, isn't it? and it could also inarguably apply to the circumstances as well. Don't you think? I mean, it's like comparing oranges with apples, and mkii with mkiv and mkvi and so forth If you were to tell me then, that mkii for instance was not aimed as an input processing I can almos assure its falsiliability is written all over, even before the sentence is processed and thought out loud by you. Bottom line is that the production-ready part is an obvious byproduct of its short lifespan, but one cannot be making the claim (false as would have been seen later, because omega carbon footprint lasted more on books than on shelves really, not for selling out fast but rather discontinued quickly) and that its goal was solely within this input processing spectrum. Because it wasn't. Or heck or heck. Let's go even further. By making the dubious assertion that we've been built with noses to hold our eyeglasses lest these eyeglasses fall off while reading, or that we've been built with ears to hold pencils and pens in the ears while thinking and writing. For crying out loud. > > It is xetex that hooked into opentype although pdftex can actually deal with > truetype fonts to some extend. Before there was something 'opentype' we had > two competing but similar technologies. And it took a while before it was > even clear
Re: [NTG-context] Off topic: Does a 'free for commercial use' flared-sans font exist in the world?
On 6/17/2023 2:06 AM, linguafalsa--- via ntg-context wrote: On Fri, Jun 16, 2023 at 06:35:49PM +0200, Gerben Wierda via ntg-context wrote: I know this is off topic, but I suspect this community is actually one of the best places to find an answer. It is the best community. And I tell you what. What happened is that all TeX engines have neglected fonts from the beginning. Really? When tex showed up digital font technology was pretty much in flux. And, with metafont being part of the tex ecosystem, one can argue that tex was quite innovative too. Potscript and its fonts came aroudn at the same time and were rather closed technologies. But as soon possible backend drivers (also part of the tex ecosystem) kicked in. Then we got virtual fonts which enhanced tex's capabilities. I really like Optima, and what I really like about it is the 'flared style'. But I would like to move to a flared-sans font that gives me more licensing freedom. I haven't been able to find one after extensive searching. The only one who were reasonably priced (not free) were the URW Classico ones in Adobe Creative Cloud, but those can only be used in Adobe programs like InDesign (and not TeX). Licensing freedom is an oxymoron. There's no freedom in licensing. Only greed. The only extension engine that at one point had a plan in mind, or most of the bases covered in this regard was Omega. One needs morr than plans. Afaik omega was more about input processing and th efont part was mostly going beyond 8 bit fonts but i might have missed something (omega was never productin ready). It is xetex that hooked into opentype although pdftex can actually deal with truetype fonts to some extend. Before there was something 'opentype' we had two competing but similar technologies. And it took a while before it was even clear how to interpre the specification (also think about reverse engeneering fonts and heuristics and ... bugs or features ...). TeX was always pretty fast in picking up new stuff (maybe users less so). When it came to commercial fonts the plan of action ahead was by including PFC data on these very same commercial fonts that would benefit primarily its opentype versions in the long run. What is PFC data? What do you have right now? Opentype fonts only. Sure. Quality can be even the same than its type1 counterpart, and at times not so much according so some folks that have bothered to go the extra length in making the most accurate comparison that's available between them two. For most fonts it's just 'more shapes' which then also leads to more ligatures, kerns etc btu that is already nice. And when fonts lack something we can always tweak them (runtime). But looking at it from a bright side/perspective, I think we're no longer facing the same pre-historic constraints of including a font as before, as long as it's not for commercial purposes, You are well aware of these non and commercial uses even before your extensive search anyway, I'm not sure what is the difference between commercial fonts and free ones as they use the same technology; with some exceptions, fonts are not that expensive (take lucida from tug, making fonts takes time after all); and for publishers it's noise on their budgets. p.s many many years ago I read and followed some publications about the aformentioned extension and just went over them recently, to have an idea what did and did not work. In regards to typefaces, its goal was unmatched, or so I think. It might be comforting to know that right from the start luatex made a lot possible wrt fonts (runtime manipulation) and was also one of the first to support variable fonts, color fonts etc (not that many care about that). And with luametatex we go even further. I found some flared-sans fonts, but not one with at least regular, italic, bold, and bold-italic. Is there really not a single flared-sans font that is really free (so also for commercial use) to use out there? I had to search the net to figure out that flare sans fonts are sans fonts with serifs For those into fonts: https://tug.org/TUGboat/tb44-1/tb136carter-romano.pdf I a very nice overview of how it went with digital fonts (and what we probably lost in getting where we are now and might loose soon). 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpag
Re: [NTG-context] TiKz with LMTX
On 6/12/2023 6:49 PM, Carlos via ntg-context wrote: On Thu, Jun 08, 2023 at 11:57:36PM -0400, Aditya Mahajan via ntg-context wrote: On Thu, 8 Jun 2023, Jigé via ntg-context wrote: Thanks a lot Aditya. The very simple TikZ example with the cross works. The more complex example with the trigonometric circle from the pgf manual, quoted in https://wiki.contextgarden.net/TikZ , does not compile unless you also comment out or find(n,"pdftex") in line 181 of the mtx-install-modules.lua file before doing mtxrun --script install-modules --install tikz but I could guess that from a: Driver file ``pgfsys-pdftex.def'' not found.. message Ah so tikz uses both drivers. @Hans, so the validate function should be: local function validate(n) return not ( find(n,"latex") what's the point of latex there? -- or find(n,"lualatex") or for that matter this one lualatex too or find(n,"plain") or find(n,"optex") -- or find(n,"luatex") -- or find(n,"pdftex") ) end just getting rid of files we don't need 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On Thu, Jun 08, 2023 at 11:57:36PM -0400, Aditya Mahajan via ntg-context wrote: > On Thu, 8 Jun 2023, Jigé via ntg-context wrote: > > > Thanks a lot Aditya. > > > > The very simple TikZ example with the cross works. > > The more complex example with the trigonometric circle from the pgf manual, > > quoted in https://wiki.contextgarden.net/TikZ , does not compile > > unless you also comment out > > or find(n,"pdftex") > > in line 181 of the mtx-install-modules.lua file > > before doing mtxrun --script install-modules --install tikz > > but I could guess that from a: > > Driver file ``pgfsys-pdftex.def'' not found.. > > message > > Ah so tikz uses both drivers. > > @Hans, so the validate function should be: > > local function validate(n) > return not ( >find(n,"latex") what's the point of latex there? > -- or find(n,"lualatex") or for that matter this one lualatex too > or find(n,"plain") > or find(n,"optex") > -- or find(n,"luatex") > -- or find(n,"pdftex") > ) > end > > > Aditya Through rsync only and by default without mtx-install-modules script, obviously, it'll simply fall back loading by pgfsys-pdftex so you'd be better off by just having local function validate(n) return not ( find(n,"latex") or find(n,"lualatex") or find(n,"plain") or find(n,"optex") -- or find(n,"luatex") or find(n,"pdftex") ) end instead. Also, forget about the curl --ssl or whatever you mentioned earlier. > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ -- Brian Kernighan has an automobile which he helped design. Unlike most automobiles, it has neither speedometer, nor gas gauge, nor any of the numerous idiot lights which plague the modern driver. Rather, if the driver makes any mistake, a giant "?" lights up in the center of the dashboard. "The experienced driver", he says, "will usually know what's wrong." ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On Fri, 9 Jun 2023, Hans Hagen via ntg-context wrote: > On 6/9/2023 5:57 AM, Aditya Mahajan via ntg-context wrote: > > On Thu, 8 Jun 2023, Jigé via ntg-context wrote: > > > >> Thanks a lot Aditya. > >> > >> The very simple TikZ example with the cross works. > >> The more complex example with the trigonometric circle from the pgf > >> manual, > >> quoted in https://wiki.contextgarden.net/TikZ , does not compile > >> unless you also comment out > >> or find(n,"pdftex") > >> in line 181 of the mtx-install-modules.lua file > >> before doing mtxrun --script install-modules --install tikz > >> but I could guess that from a: > >> Driver file ``pgfsys-pdftex.def'' not found.. > >> message > > > > Ah so tikz uses both drivers. > > > > @Hans, so the validate function should be: > > > > local function validate(n) > > return not ( > > find(n,"latex") > > -- or find(n,"lualatex") > > or find(n,"plain") > > or find(n,"optex") > > -- or find(n,"luatex") > > -- or find(n,"pdftex") > > ) > > end > so an alternative is to ignore deleting those two files > > what is in lualatex that we need? can hardly be something generic pgf/tikz doesn't have anything with lualatex in the name. The only files that match luatex/pdftex are these def files. > (it being pretty big makes me wonder if we should have texmf-tikz for it as i > don't want to polute the modules tree too much - it gets hard to check other > modules for instance when i want to see if some change has impact) If it makes things easier to manage, we can definitely do that. We already have 7 trees, one more isn't going to make any difference :-) Aditya___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On 6/9/2023 5:57 AM, Aditya Mahajan via ntg-context wrote: On Thu, 8 Jun 2023, Jigé via ntg-context wrote: Thanks a lot Aditya. The very simple TikZ example with the cross works. The more complex example with the trigonometric circle from the pgf manual, quoted in https://wiki.contextgarden.net/TikZ , does not compile unless you also comment out or find(n,"pdftex") in line 181 of the mtx-install-modules.lua file before doing mtxrun --script install-modules --install tikz but I could guess that from a: Driver file ``pgfsys-pdftex.def'' not found.. message Ah so tikz uses both drivers. @Hans, so the validate function should be: local function validate(n) return not ( find(n,"latex") -- or find(n,"lualatex") or find(n,"plain") or find(n,"optex") -- or find(n,"luatex") -- or find(n,"pdftex") ) end so an alternative is to ignore deleting those two files what is in lualatex that we need? can hardly be something generic (it being pretty big makes me wonder if we should have texmf-tikz for it as i don't want to polute the modules tree too much - it gets hard to check other modules for instance when i want to see if some change has impact) 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On Thu, 8 Jun 2023, Jigé via ntg-context wrote: > Thanks a lot Aditya. > > The very simple TikZ example with the cross works. > The more complex example with the trigonometric circle from the pgf manual, > quoted in https://wiki.contextgarden.net/TikZ , does not compile > unless you also comment out > or find(n,"pdftex") > in line 181 of the mtx-install-modules.lua file > before doing mtxrun --script install-modules --install tikz > but I could guess that from a: > Driver file ``pgfsys-pdftex.def'' not found.. > message Ah so tikz uses both drivers. @Hans, so the validate function should be: local function validate(n) return not ( find(n,"latex") -- or find(n,"lualatex") or find(n,"plain") or find(n,"optex") -- or find(n,"luatex") -- or find(n,"pdftex") ) end Aditya ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
Thanks a lot Aditya. The very simple TikZ example with the cross works. The more complex example with the trigonometric circle from the pgf manual, quoted in https://wiki.contextgarden.net/TikZ , does not compile unless you also comment out or find(n,"pdftex") in line 181 of the mtx-install-modules.lua file before doing mtxrun --script install-modules --install tikz but I could guess that from a: Driver file ``pgfsys-pdftex.def'' not found.. message Thanks again Jean-Guillaume Le jeudi 8 juin 2023 à 12:28:34 UTC+2, a écrit : Date: Mon, 5 Jun 2023 22:32:37 -0400 (EDT) From: Aditya Mahajan To: Aditya Mahajan via ntg-context Subject: Re: [NTG-context] TiKz with LMTX Message-ID: Content-Type: text/plain; charset="iso-8859-15" On Mon, 5 Jun 2023, Aditya Mahajan via ntg-context wrote: > On Sun, 4 Jun 2023, Jig? via ntg-context wrote: > > > > $ mkdir ~/.local/share/context > > $ cd ~/.local/share/context > > $ wget https://lmtx.pragma-ade.com/install-lmtx/context-linux-64.zip > > $ unzip context-linux-64.zip > > $ sh install.sh > > $ rm context-linux-64.zip > > $ cd ~/.local/share/context/tex > > $ mtxrun --script install-modules --list > > $ mtxrun --script install-modules --install tikz > > (And for good measure, I later did `mtxrun --script install-modules > > --install all`) > > > > $ cd my-working-directory > > $ vi some-sample-context-file.tex > > $ export PATH=/home/myname/.local/share/context/tex/texmf-linux-64/bin:$PATH > > $ context some-sample-context-file.tex > > > > Did I miss anything? It works just fine. > > On a new machine and pgfsys-luatex.def is missing for me as well. I'll try to > check what is going on. This was a bit crazy to track down. Here is the fix: In line 180 of mtx-install-modules.lua, comment the line or find(n,"luatex") Otherwise, the file tex/generic/pgf/systemlayer/pgfsys-luatex.def is not extracted from the tikz.zip! I don't know why OP and I (both on archlinux) were the only ones who had pgfsys-luatex.def missing. Everyone should have been affected by this. Aditya PS: Also on line 103, it may be a good idea to change the curl call to curl --ssl --location mirros.ctan.org will also do a HTTP 302 redirect and without the --location flag, curl will not follow the redirect. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On Mon, Jun 05, 2023 at 03:43:59PM -0400, Carlos via ntg-context wrote: > On Mon, Jun 05, 2023 at 03:06:10PM +0200, Floris van Manen via ntg-context > wrote: > > > > > > On 05/06/2023 14:49, Carlos via ntg-context wrote: > > > %# Synchronize all modules from ConTeXt Garden in the 'modules' > > > directory, which is created if it doesn’t exist. > > > to wherever the modules are > > > > > > isn't the command > > > > mtxrun --script install-modules --install tikz > > > > or > > > > mtxrun --script install-modules --install --all > > > > doing exactly that? > > > > Okay Floris. I see Aditya nearby. He'll take over from now on :) stand > by please. I know you didn't ask the original question but this is over > the pgfsys-pdftex and the pgfsys-luatex. It's a race between them !! > sort of > > The solutions are a few if any really, either as I suggested first and update > afterwards or install tikz > > if the driver is the problem, what does common sense tells you Floris? > the database needs to be updated, correct? The driver needs to be > loaded somehow, right? > > > system > ConTeXt ver: 2023.06.04 18:58 LMTX fmt: 2023.6.5 int: > english/english > > So install tikz. then run the file > > mtx-install-modules | from > 'https://mirrors.ctan.org/install/graphics/pgf/base/pgf.tds.zip' > mtx-install-modules | into 'texmf-modules' > 64 files of 642 done,2108636 bytes, 0.015 seconds > 128 files of 642 done, 13693106 bytes, 0.089 seconds > 194 files of 642 done, 15194110 bytes, 0.100 seconds > 317 files of 642 done, 16096396 bytes, 0.108 seconds > 382 files of 642 done, 17178524 bytes, 0.116 seconds > 446 files of 642 done, 17768214 bytes, 0.123 seconds > 510 files of 642 done, 18327708 bytes, 0.130 seconds > 574 files of 642 done, 18656649 bytes, 0.136 seconds > 638 files of 642 done, 18860083 bytes, 0.142 seconds > 642 files of 642 done, 18864376 bytes, 0.142 seconds > mtx-install-modules | from > 'https://mirrors.ctan.org/install/graphics/pgf/contrib/pgfplots.tds.zip' > mtx-install-modules | into 'texmf-modules' > 29 files of 168 done, 69116 bytes, 0.002 seconds > 48 files of 168 done,1596420 bytes, 0.010 seconds > 67 files of 168 done,1889062 bytes, 0.012 seconds > 83 files of 168 done,2761170 bytes, 0.017 seconds > 100 files of 168 done,3156638 bytes, 0.021 seconds > 116 files of 168 done,3508192 bytes, 0.024 seconds > 132 files of 168 done,4035279 bytes, 0.027 seconds > 148 files of 168 done,4163894 bytes, 0.029 seconds > 168 files of 168 done,4195360 bytes, 0.029 seconds > mtx-install-modules | from > 'https://mirrors.ctan.org/install/graphics/pgf/contrib/circuitikz.tds.zip' > mtx-install-modules | into 'texmf-modules' >7 files of 70 done, 14967 bytes, 0.000 seconds > 21 files of 70 done, 61604 bytes, 0.001 seconds > 28 files of 70 done,4839027 bytes, 0.033 seconds > 35 files of 70 done,5906994 bytes, 0.040 seconds > 42 files of 70 done,6399050 bytes, 0.043 seconds > 70 files of 70 done,6879048 bytes, 0.045 seconds > mtx-install-modules | wiping 17 files in 'tex/context/third/pgf/**' > mtx-install-modules | wiping 0 files in 'doc/context/third/pgf/**' > mtx-install-modules | wiping 0 files in 'source/context/third/pgf/**' > mtx-install-modules | wiping 0 files in 'tex/context/pgf/**' > mtx-install-modules | wiping 0 files in 'doc/context/pgf/**' > mtx-install-modules | wiping 0 files in 'source/context/pgf/**' > mtx-install-modules | wiping 0 files in 'scripts/pgf/**' > mtx-install-modules | wiping 2 files in 'tex/context/third/pgfplots/**' > mtx-install-modules | wiping 3 files in 'doc/context/third/pgfplots/**' > mtx-install-modules | wiping 1 files in 'source/context/third/pgfplots/**' > mtx-install-modules | wiping 0 files in 'tex/context/pgfplots/**' > mtx-install-modules | wiping 0 files in 'doc/context/pgfplots/**' > mtx-install-modules | wiping 0 files in 'source/context/pgfplots/**' > mtx-install-modules | wiping 4 files in 'scripts/pgfplots/**' > mtx-install-modules | wiping 8 files in 'tex/context/third/circuitikz/**' > mtx-install-modules | wiping 2 files in 'doc/context/third/circuitikz/**' > mtx-install-modules | wiping 0 files in 'source/context/third/circuitikz/**' > mtx-install-modules | wiping 0 files in 'te
Re: [NTG-context] TiKz with LMTX
On Mon, Jun 05, 2023 at 03:06:10PM +0200, Floris van Manen via ntg-context wrote: > > > On 05/06/2023 14:49, Carlos via ntg-context wrote: > > %# Synchronize all modules from ConTeXt Garden in the 'modules' directory, > > which is created if it doesn’t exist. > > to wherever the modules are > > > isn't the command > > mtxrun --script install-modules --install tikz > > or > > mtxrun --script install-modules --install --all > > doing exactly that? > Okay Floris. I see Aditya nearby. He'll take over from now on :) stand by please. I know you didn't ask the original question but this is over the pgfsys-pdftex and the pgfsys-luatex. It's a race between them !! sort of The solutions are a few if any really, either as I suggested first and update afterwards or install tikz if the driver is the problem, what does common sense tells you Floris? the database needs to be updated, correct? The driver needs to be loaded somehow, right? system > ConTeXt ver: 2023.06.04 18:58 LMTX fmt: 2023.6.5 int: english/english So install tikz. then run the file mtx-install-modules | from 'https://mirrors.ctan.org/install/graphics/pgf/base/pgf.tds.zip' mtx-install-modules | into 'texmf-modules' 64 files of 642 done,2108636 bytes, 0.015 seconds 128 files of 642 done, 13693106 bytes, 0.089 seconds 194 files of 642 done, 15194110 bytes, 0.100 seconds 317 files of 642 done, 16096396 bytes, 0.108 seconds 382 files of 642 done, 17178524 bytes, 0.116 seconds 446 files of 642 done, 17768214 bytes, 0.123 seconds 510 files of 642 done, 18327708 bytes, 0.130 seconds 574 files of 642 done, 18656649 bytes, 0.136 seconds 638 files of 642 done, 18860083 bytes, 0.142 seconds 642 files of 642 done, 18864376 bytes, 0.142 seconds mtx-install-modules | from 'https://mirrors.ctan.org/install/graphics/pgf/contrib/pgfplots.tds.zip' mtx-install-modules | into 'texmf-modules' 29 files of 168 done, 69116 bytes, 0.002 seconds 48 files of 168 done,1596420 bytes, 0.010 seconds 67 files of 168 done,1889062 bytes, 0.012 seconds 83 files of 168 done,2761170 bytes, 0.017 seconds 100 files of 168 done,3156638 bytes, 0.021 seconds 116 files of 168 done,3508192 bytes, 0.024 seconds 132 files of 168 done,4035279 bytes, 0.027 seconds 148 files of 168 done,4163894 bytes, 0.029 seconds 168 files of 168 done,4195360 bytes, 0.029 seconds mtx-install-modules | from 'https://mirrors.ctan.org/install/graphics/pgf/contrib/circuitikz.tds.zip' mtx-install-modules | into 'texmf-modules' 7 files of 70 done, 14967 bytes, 0.000 seconds 21 files of 70 done, 61604 bytes, 0.001 seconds 28 files of 70 done,4839027 bytes, 0.033 seconds 35 files of 70 done,5906994 bytes, 0.040 seconds 42 files of 70 done,6399050 bytes, 0.043 seconds 70 files of 70 done,6879048 bytes, 0.045 seconds mtx-install-modules | wiping 17 files in 'tex/context/third/pgf/**' mtx-install-modules | wiping 0 files in 'doc/context/third/pgf/**' mtx-install-modules | wiping 0 files in 'source/context/third/pgf/**' mtx-install-modules | wiping 0 files in 'tex/context/pgf/**' mtx-install-modules | wiping 0 files in 'doc/context/pgf/**' mtx-install-modules | wiping 0 files in 'source/context/pgf/**' mtx-install-modules | wiping 0 files in 'scripts/pgf/**' mtx-install-modules | wiping 2 files in 'tex/context/third/pgfplots/**' mtx-install-modules | wiping 3 files in 'doc/context/third/pgfplots/**' mtx-install-modules | wiping 1 files in 'source/context/third/pgfplots/**' mtx-install-modules | wiping 0 files in 'tex/context/pgfplots/**' mtx-install-modules | wiping 0 files in 'doc/context/pgfplots/**' mtx-install-modules | wiping 0 files in 'source/context/pgfplots/**' mtx-install-modules | wiping 4 files in 'scripts/pgfplots/**' mtx-install-modules | wiping 8 files in 'tex/context/third/circuitikz/**' mtx-install-modules | wiping 2 files in 'doc/context/third/circuitikz/**' mtx-install-modules | wiping 0 files in 'source/context/third/circuitikz/**' mtx-install-modules | wiping 0 files in 'tex/context/circuitikz/**' mtx-install-modules | wiping 0 files in 'doc/context/circuitikz/**' mtx-install-modules | wiping 0 files in 'source/context/circuitikz/**' mtx-install-modules | wiping 0 files in 'scripts/circuitikz/**' mtx-install-modules | wiping 0 files in 'tex/latex/**' mtx-install-modules | wiping 0 files in 'tex/plain/**' mtx-install-modules | wiping 0 files in 'doc/latex/**' mtx-install-modules | wiping 0 files in 'doc/plain/**' mtx-insta
Re: [NTG-context] TiKz with LMTX
I tried: $ mtxrun --generate and also commenting out "source/generic/**" in mtx-install-imp-tikz.lua but with no success. Same error: Driver file ``pgfsys-luatex.def'' not found. This file does not exist in my installation. $ find ~/.local/share/context -iname "*.def" /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-vtex.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-textures.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-common-postscript.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvisvgm4ht.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvipdfm.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvipdfmx.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-common-pdf.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-common-pdf-via-dvi.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-tex4ht.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvisvgm.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvi.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-common-svg.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-xetex.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvips.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/utilities/pgfutil-context.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sys/pgflibrarypgfplots.surfshading.pgfsys-xetex.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sys/pgflibrarypgfplots.surfshading.pgfsys-dvips.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sys/pgflibrarypgfplots.surfshading.pgfsys-dvipdfmx.def Il tried using some of these files by writing them in context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgf.cfg , by the way, but it either doesn't compile or produces a bad picture. Here are some quotes from the online pgf/tikz manual ( https://tikz.dev/drivers#section-formats ) : > 10.2.1 Selecting the Backend Driver > > When TEX typesets your document, it does not know which program you are going > to use to transform the .dvi-file. If your .dvi-file does not contain any > special commands, > this would be fine; but these days almost all .dvi-files contain lots of > special commands. > It is thus necessary to tell TEX which program you are going to use later on. > > Unfortunately, there is no “standard” way of telling this to TEX. > For the LATEX format a sophisticated mechanism exists inside the graphics > package > and pgf plugs into this mechanism. For other formats and when this plugging > does not work > as expected, it is necessary to tell pgf directly which program you are going > to use. > This is done by redefining the macro \pgfsysdriver to an appropriate value > before you load pgf. > If you are going to use the dvips program, you set this macro to the value > pgfsys-dvips.def; > if you use pdftex or pdflatex, you set it to pgfsys-pdftex.def; and so on. > In the following, details of the support of the different programs are > discussed. > > 10.2.2 Producing PDF Output > > pgf supports three programs that produce pdf output [...]: > dvipdfm, pdftex, and vtex. The pdflatex program is the same as the pdftex > program: > it uses a different input format, but the output is exactly the same. > > File pgfsys-pdftex.def > This is the driver file for use with pdfTEX, that is, with the pdftex or > pdflatex command. > It includes pgfsys-common-pdf.def. > > This driver has a lot of functionality. > (Almost) everything pgf “can do at all” is implemented in this driver. > > File [...] [...] (And so on with pgfsys-dvipdfm.def pgfsys-xetex.def pgfsys-vtex.def... Basicaly all the other drivers cited have serious shortcomings in processing TiKz pictures.) So, we need the driver: pgfsys-luatex.def . Or do we? The name of this driver is guessed at compile time. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] new units
On 5/7/2023 11:29 AM, Mojca Miklavec via ntg-context wrote: On Sun, 7 May 2023 at 11:11, Henning Hraban Ramm via ntg-context wrote: And what’s the abbreviation for Theodores? I assume it must be "tr", though it's somewhat ambiguous what the "r" in "tr" stands for, it seems to be country-dependent ;) The problem with introducing the theodore is that it introduces another 'male name' unit while actually the new ones got 'female names' in order to counter the didot and cicero (and dk although we considere that a neutral unit), which was one of the projects objectives. Okay, we can from now on assume the 'mm' to be the Mojca which is also more officient: 4 mojcas instead of 4 millimeters. It's a downward compatible change (only in the documentation). Then we can introduce the tr as precisely 5 es, a kind of snaposhot unit, whgich makes me wonder, as the theodore eventually will come close to a foot we might have a \thfactor then that starts out at 5. We can decide at the ctx meeting. (In case one wonders: because internally tex works with fractions mm/cm and ts/es (/tr) make sense.) (As explained during the presentation, adding units to luametatex is not really putting a (performance) burden on this engine. In pdftex and luatex it would have an impact, although in luatex somewhat less because we prioritize our favourite units anyway.) - 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
On Tue, Apr 11, 2023 at 11:23:45AM +0200, Hans Hagen via ntg-context wrote:
> On 4/11/2023 11:11 AM, Carlos via ntg-context wrote:
>
> > Hello Alan, my PATH is set to:
> >
> > PATH=/home/ce/context-install/bin:/home/ce/context-install/tex/texmf-linux-64/bin:/opt/texlive/2023/bin/x86_64-linux:$PATH;
> > export PATH
>
> what is that first path doing there
>
okay. Let's remove it. The second one wouldn't hurt it I guess, right?
and it's needed.
> > Do we actually need to list all kpsea variable here ?? fine
>
> doesn't hurt .. also because they can be set badly at the os level (you
> really don't want to knwo when has be encountered in the 20th century)
>
:)
> > Here are some of them, which are really irrelevant by the way, but just
> > adding info
> >
> > $ kpsewhich --var-value TEXMFROOT
> > /opt/texlive/2023
> > $ kpsewhich --var-value TEXMFDIST
> > /opt/texlive/2023/texmf-dist
> > $ kpsewhich --var-value TEXMFLOCAL
> > /opt/texlive/texmf-local
> >
> > Now let's take a peek inside the TeX Live infrastructure-only, shall
> > we? (just for additional info as TeX Live is ocnsidered one of the
> > many scripts out there, right? One is interested in the standalone in
> > the end)
> >
> > LICENSE.CTAN bin install-tl.log texmf-config
> > texmfcnf.lua
> > LICENSE.TL doc.htmlreadme-html.dir texmf-disttlpkg
> > README index.html readme-txt.dir texmf-var
> > README.usergroups install-tl release-texlive.txt texmf.cnf
>
> that si texlive, not standalone
>
> > that texmfcnf.lua only holds
> >
> > return {
> >content = {
> > variables = {
> > },
> >},
> > }
> >
> > which is useless
>
> and harmless (somethign old texlive)
>
> > so, no bueno. Not when the aim is to install a fully functional context
> > standalone
> >
> > Now let's take a peek instide and see the binaries
> >
> > afm2tfm etex kpsereadlink mfmtxrun.lua texluac
> > bibtex extractbb kpsestat mf-nowin pdfetex tlmgr
> > context fmtutil kpsewhichmft pdflatextlshell
> > context.lua fmtutil-sys latexmkindex pdftex updmap
> > dvilualatex fmtutil-user luahbtex mktexfmt pktogf updmap-sys
> > dviluatexgftodvi lualatex mktexlsr pktype
> > updmap-user
> > dvipdfm gftopkluametatex mktexmf rungs xdvi
> > dvipdfmx gftypeluaotfload-tool mktexpk simpdftex xdvi-xaw
> > dvipdft inimf luatex mktextfm tex xdvipdfmx
> > dvipsinitexmakeindexmptopdf texhash
> > ebb kpseaccessman mtxruntexlua
> >
> > Do you see that context and context.lua out there, right? That's
> > only after running tlmgr and installing it, so no bueno, because in
> > the meantime there's no texmfcnf.lua around
>
> comes from the tex live base package ... harmless, just takes bytes (only
> luatex, luametatex, context, mtxrun, context.lua and mtxrun.lua matter)
>
> > Then again, remember in the current state I actually don't have
> > texmfcnf.lua for the simple reason that first-setup.sh never provided
> > it, correct?
>
> aditya pointer that out (and it's one of the files that one doesn't want to
> be overwritten anyway)
>
For clarification, Do you mean the file that consists of
-- the distributed file (.../texlive//texmf-dist/web2c/texmfcnf.lua).
-- And include *only* your changed values, not a copy of the whole thing!
return {
content = {
variables = {
},
},
}
and belongs to TeX Live?
> > Here we go! Back to point A where we were at before
> as alan pointed out: just install with the lmtx installer in a path separate
> from tex live, set the path and you're done; don't try to mix texlive with a
> adapted of standalone, texlive has its own context package and updates etc;
> keep them separated
alright. That's fine. That's what I thought.
So copy over the mtxrun binary on texmf-linux-64/bin to context and call it a
day?
>
> 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
>
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
On 4/11/2023 11:11 AM, Carlos via ntg-context wrote:
Hello Alan, my PATH is set to:
PATH=/home/ce/context-install/bin:/home/ce/context-install/tex/texmf-linux-64/bin:/opt/texlive/2023/bin/x86_64-linux:$PATH;
export PATH
what is that first path doing there
Do we actually need to list all kpsea variable here ?? fine
doesn't hurt .. also because they can be set badly at the os level (you
really don't want to knwo when has be encountered in the 20th century)
Here are some of them, which are really irrelevant by the way, but just
adding info
$ kpsewhich --var-value TEXMFROOT
/opt/texlive/2023
$ kpsewhich --var-value TEXMFDIST
/opt/texlive/2023/texmf-dist
$ kpsewhich --var-value TEXMFLOCAL
/opt/texlive/texmf-local
Now let's take a peek inside the TeX Live infrastructure-only, shall
we? (just for additional info as TeX Live is ocnsidered one of the
many scripts out there, right? One is interested in the standalone in
the end)
LICENSE.CTAN bin install-tl.log texmf-config texmfcnf.lua
LICENSE.TL doc.htmlreadme-html.dir texmf-disttlpkg
README index.html readme-txt.dir texmf-var
README.usergroups install-tl release-texlive.txt texmf.cnf
that si texlive, not standalone
that texmfcnf.lua only holds
return {
content = {
variables = {
},
},
}
which is useless
and harmless (somethign old texlive)
so, no bueno. Not when the aim is to install a fully functional context
standalone
Now let's take a peek instide and see the binaries
afm2tfm etex kpsereadlink mfmtxrun.lua texluac
bibtex extractbb kpsestat mf-nowin pdfetex tlmgr
context fmtutil kpsewhichmft pdflatextlshell
context.lua fmtutil-sys latex mkindex pdftex updmap
dvilualatex fmtutil-user luahbtex mktexfmt pktogf updmap-sys
dviluatexgftodvi lualatex mktexlsr pktype updmap-user
dvipdfm gftopkluametatex mktexmf rungs xdvi
dvipdfmx gftypeluaotfload-tool mktexpk simpdftex xdvi-xaw
dvipdft inimf luatex mktextfm tex xdvipdfmx
dvipsinitexmakeindexmptopdf texhash
ebb kpseaccessman mtxruntexlua
Do you see that context and context.lua out there, right? That's
only after running tlmgr and installing it, so no bueno, because in
the meantime there's no texmfcnf.lua around
comes from the tex live base package ... harmless, just takes bytes
(only luatex, luametatex, context, mtxrun, context.lua and mtxrun.lua
matter)
Then again, remember in the current state I actually don't have
texmfcnf.lua for the simple reason that first-setup.sh never provided
it, correct?
aditya pointer that out (and it's one of the files that one doesn't want
to be overwritten anyway)
Here we go! Back to point A where we were at before
as alan pointed out: just install with the lmtx installer in a path
separate from tex live, set the path and you're done; don't try to mix
texlive with a adapted of standalone, texlive has its own context
package and updates etc; keep them separated
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
On Mon, Apr 10, 2023 at 10:01:55PM -0600, Alan Braslau via ntg-context wrote:
> On Mon, 10 Apr 2023 20:51:58 -0400 (EDT)
> Aditya Mahajan via ntg-context wrote:
>
> > Did you source the `setuptex` script, which sets the correct path.
>
> My PATH is set to
> PATH=./context/tex/texmf-freebsd-amd64/bin:/home/MyAccount/context/tex/texmf-freebsd-amd64/bin:...
>
> If my current working directory ("./") is a project that contains its
> very own subdirectory ./context/, then this is used to typeset the
> project. If not, it falls back on my own general standalone
> $HOME/context/, and if that does not exist, then it falls back on, say,
> a systemwide TeXlive installation.
>
> This is all that is needed to have many versions coexist.
>
> Alan
Hello Alan, my PATH is set to:
PATH=/home/ce/context-install/bin:/home/ce/context-install/tex/texmf-linux-64/bin:/opt/texlive/2023/bin/x86_64-linux:$PATH;
export PATH
because not by going by TeX Live infrastructure only, but rather
by standalone resolvers that's exactly what the additional steps to
install that very same standalone required, a folder
texmf-linux-64/bin, which it's pretty much self-explanatory
And I already mentioned the above earlier
Again
Do we actually need to list all kpsea variable here ?? fine
Here are some of them, which are really irrelevant by the way, but just
adding info
$ kpsewhich --var-value TEXMFROOT
/opt/texlive/2023
$ kpsewhich --var-value TEXMFDIST
/opt/texlive/2023/texmf-dist
$ kpsewhich --var-value TEXMFLOCAL
/opt/texlive/texmf-local
Now let's take a peek inside the TeX Live infrastructure-only, shall
we? (just for additional info as TeX Live is ocnsidered one of the
many scripts out there, right? One is interested in the standalone in
the end)
LICENSE.CTAN bin install-tl.log texmf-config texmfcnf.lua
LICENSE.TL doc.htmlreadme-html.dir texmf-disttlpkg
README index.html readme-txt.dir texmf-var
README.usergroups install-tl release-texlive.txt texmf.cnf
that texmfcnf.lua only holds
return {
content = {
variables = {
},
},
}
which is useless
so, no bueno. Not when the aim is to install a fully functional context
standalone
Now let's take a peek instide and see the binaries
afm2tfm etex kpsereadlink mfmtxrun.lua texluac
bibtex extractbb kpsestat mf-nowin pdfetex tlmgr
context fmtutil kpsewhichmft pdflatextlshell
context.lua fmtutil-sys latexmkindex pdftex updmap
dvilualatex fmtutil-user luahbtex mktexfmt pktogf updmap-sys
dviluatexgftodvi lualatex mktexlsr pktype updmap-user
dvipdfm gftopkluametatex mktexmf rungs xdvi
dvipdfmx gftypeluaotfload-tool mktexpk simpdftex xdvi-xaw
dvipdft inimf luatex mktextfm tex xdvipdfmx
dvipsinitexmakeindexmptopdf texhash
ebb kpseaccessman mtxruntexlua
Do you see that context and context.lua out there, right? That's
only after running tlmgr and installing it, so no bueno, because in
the meantime there's no texmfcnf.lua around
Then again, remember in the current state I actually don't have
texmfcnf.lua for the simple reason that first-setup.sh never provided
it, correct?
So, wwith that in mind and in place, even that context binary from TeX
Live infrastructure as shown before is a known fact that texmfcnf.lua
is nowhere to be found
So let me see if I can copy one from an otherwise fully functional TeX Live
with almost 5g of space taken over and copy it over to this TeX Live
infrastrcutre so
everything checks out in the end
What happens then is not really surprising
If I were to copy over a copy that I found elsewhere over to web2c
of the TeX Live-infrastructure-only installation, this is what happens:
$ context --generate --luatex
mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'
Here we go! Back to point A where we were at before
>
> P.S. It can be a good practice to keep a ConTeXt standalone version
> associated with each project, which can be "frozen" with the project,
> assuring that the sources can always be typeset in the future "as is".
>
> P.P.S. This per-project ./context/ subdirectory can include multiple
> tex/texmf-system-architecture subdirectories and the project shared
> between different machines, all in happy coexistence. (Hans told me a
> while ago that they all use unique luametatex caches.)
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On Fri, Mar 31, 2023 at 04:40:27PM +0200, Hans Hagen via ntg-context wrote: > On 3/31/2023 1:40 PM, Carlos via ntg-context wrote: > > > > so why not use lucida math fonts? > > > > I have. But only with a couple of math fonts. I don't have all these fonts. > > It really pays off to buy the official lucida opentype package. I'll do that eventually. > > > mkiv lua stats > loaded fonts: 3 files: lucidanewmathitalic.ttf, > > lucidanewmathsymbol.ttf, lucidabrightregular.otf > > mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 6 > > instances, 3 shared in backend, 1 common vectors, 2 common hashes, load > > time 16.733 seconds > > I never heard of these math ones. Did you get these from yandytex (no longer > around) or TUG (the official distributer of lucida opentype math)? Anyway, > as we fine tune math fonts for sure you get suboptimal results (or even > wrong output). Mikael and I put quite a bit of care into lucida opentype > math. > > > I do agree with you in that that loading time is perhaps unacceptable but… > > ... > > You ought to specify that must be only after subsequent callbacks. I just > > tried it with a one liner file of \setupbodyfont[lucida] and (looking > > around in disbelief) it took a whooping ahem > > fonts > names > skipped files: 164 > > fonts > names > duplicate files : 164 > > fonts > names > total scan time : 16.487 seconds > > I have no clue, unless that relates to your font path including some home > dir which gets scanned every time for whatever reason and that has tens of > thousands of files. I can process the 350+ page luametatex manual twice in > these 16 seconds and that one loads quite some (also math) fonts and my > laptop is not a fancy 2023 one > > > before it produced even error messages. > > > > beating me for 2 seconds. Great. And then it restricted my freedom by saying > > > > «Sorry, but I can't typeset math unless various parameters have been set. > > This is > > normally done by loading special math fonts into the math family slots. > > Your font > > set is lacking at least the parameter mentioned earlier.» > > that's pretty clear: you don't load a math font at all, maybe some text font > pretending it is math > > > Sorry, but sorry doesn't cut it here. > > it does: no proper math font found so reason to complain > > > I guess it must have been referring to \strc_formulas_place_number > > \strc_formulas_flush_number \dostarttagged \t!formulacontent \empty > > \dotagregisterformula \c_strc_formulas_n \csname \e!stop \formulaparameter > > \c!alternative \v!formula \endcsname > > dunno, that's numbering, not math > > > Okay. So I tried another file. This time around with only > > > > \setupbodyfont[lucida] > > > > \starttext > > $ test $ > > \stoptext > > > > and then the output message was «Somewhere in the math formula just ended, > > you used the stated character from an > > undefined font family. For example, plain TeX doesn't allow \it or \sl in > > subscripts. Proceed, and I'll try to forget that I needed that character.» > > > > There's not even a fallback to cmr or any other font. > > sure, why should it, you want lucida so better quit with an error than > kicking in some font; actually cmr math fonts have been obsoleted for way > over a decade by latin modern math fonts in 32 bit font engines I was actually thinking to ask you about that, and by falling back to cmr math font that perhaps would expedite loading time along the way. Thank you for the info on that last sentence. I didn't know. > > > There was not even a personalized touch in the output. That message sounds > > like one of these new GPT-chat features. Dry. When I read that «Proceed, > > and I'll try to forget it…» part the first thing I thought was: yeah, I'll > > proceed by removing that file altogether and you'll forget it for sure . > > that message is part of 'reference tex the program' for over 40 years so if > chatgpt would come up with it, it would do so by having parsed plenty of tex > sources instead of inventing it (and when it comes to answering tex related > questions chargpt is pretty unreliable, but that's another topic) > > > But instaed I looked at it and though to myself «how much has changed?!» In > > plain TeX (I have forgotten it a bit) but I can still type > > > \par > > > $test$ > > > \end > > > > and
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On 3/31/2023 1:40 PM, Carlos via ntg-context wrote: so why not use lucida math fonts? I have. But only with a couple of math fonts. I don't have all these fonts. It really pays off to buy the official lucida opentype package. mkiv lua stats > loaded fonts: 3 files: lucidanewmathitalic.ttf, lucidanewmathsymbol.ttf, lucidabrightregular.otf mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 6 instances, 3 shared in backend, 1 common vectors, 2 common hashes, load time 16.733 seconds I never heard of these math ones. Did you get these from yandytex (no longer around) or TUG (the official distributer of lucida opentype math)? Anyway, as we fine tune math fonts for sure you get suboptimal results (or even wrong output). Mikael and I put quite a bit of care into lucida opentype math. I do agree with you in that that loading time is perhaps unacceptable but… > ... You ought to specify that must be only after subsequent callbacks. I just tried it with a one liner file of \setupbodyfont[lucida] and (looking around in disbelief) it took a whooping ahem fonts > names > skipped files: 164 fonts > names > duplicate files : 164 fonts > names > total scan time : 16.487 seconds I have no clue, unless that relates to your font path including some home dir which gets scanned every time for whatever reason and that has tens of thousands of files. I can process the 350+ page luametatex manual twice in these 16 seconds and that one loads quite some (also math) fonts and my laptop is not a fancy 2023 one before it produced even error messages. beating me for 2 seconds. Great. And then it restricted my freedom by saying «Sorry, but I can't typeset math unless various parameters have been set. This is normally done by loading special math fonts into the math family slots. Your font set is lacking at least the parameter mentioned earlier.» that's pretty clear: you don't load a math font at all, maybe some text font pretending it is math Sorry, but sorry doesn't cut it here. it does: no proper math font found so reason to complain I guess it must have been referring to \strc_formulas_place_number \strc_formulas_flush_number \dostarttagged \t!formulacontent \empty \dotagregisterformula \c_strc_formulas_n \csname \e!stop \formulaparameter \c!alternative \v!formula \endcsname dunno, that's numbering, not math Okay. So I tried another file. This time around with only \setupbodyfont[lucida] \starttext $ test $ \stoptext and then the output message was «Somewhere in the math formula just ended, you used the stated character from an undefined font family. For example, plain TeX doesn't allow \it or \sl in subscripts. Proceed, and I'll try to forget that I needed that character.» There's not even a fallback to cmr or any other font. sure, why should it, you want lucida so better quit with an error than kicking in some font; actually cmr math fonts have been obsoleted for way over a decade by latin modern math fonts in 32 bit font engines There was not even a personalized touch in the output. That message sounds like one of these new GPT-chat features. Dry. When I read that «Proceed, and I'll try to forget it…» part the first thing I thought was: yeah, I'll proceed by removing that file altogether and you'll forget it for sure . that message is part of 'reference tex the program' for over 40 years so if chatgpt would come up with it, it would do so by having parsed plenty of tex sources instead of inventing it (and when it comes to answering tex related questions chargpt is pretty unreliable, but that's another topic) But instaed I looked at it and though to myself «how much has changed?!» In plain TeX (I have forgotten it a bit) but I can still type > \par > $test$ > \end and it'll produce a dvi file in return. a lot has changed: opentype math, unicode, more demands but indeed there is nothing against using plain tex with cmr and dvi fonts if that suits well; and plain tex will always be faster than context (or latex) just like pdftex with 8 bit fonts is faster than luatex with 32 bit fonts (with luametatex sitting in between wrt performance) anyway, i bet that if you want to use lucida with plain you also have to do some work and it will complain as loud as luametatex when th efont parameters are not set 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
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On Wed, Mar 29, 2023 at 12:48:53AM +0200, Hans Hagen via ntg-context wrote: > On 3/28/2023 7:05 PM, Carlos via ntg-context wrote: > > On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote: > > > On 3/27/2023 3:31 PM, Carlos via ntg-context wrote: > > > > > > > mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf, > > > > lmroman10-regular.otf, lucidabrightregular.ttf, lucidasansregular.ttf > > > > > > i admit never having seen lucida ttf files (but when opentype ttf files > > > are > > > used with an afm file present then no map files are needed at all because > > > we're in wide font mode and encidings are ignored) > > > > > > > I hadn't either. But everything aligned and thought it was nice. > > > > You're right that loading a map file is not needed, but If you're concerned > > about afm files then bring these files over to the working directory, and > > then mtxrun --generate the same > > > > So yes. Even though the file was something like (intended originally to > > load the map file, correct?) but since the map file is no longer necessary > > then afm should suffice > > > > \starttypescript [serif] [lucida] [texnansi] > > > > \definefontsynonym[LucidaBrightDemiBold][texnansi-lucidabrightdemibold][encoding=texnansi] > > > > \definefontsynonym[LucidaBrightDemiItalic][texnansi-lucidabrightdemiitalic][encoding=texnansi] > > > > \definefontsynonym[LucidaBrightItalic][texnansi-lucidabrightitalic][encoding=texnansi] > > > > \definefontsynonym[LucidaBrightRegular][texnansi-lucidabrightregular][encoding=texnansi] > > \stoptypescript > > these encodings only make sense with mkii (in which case the map file tells > pdftex if a ttf or pfb file is used) > > in mkiv encodings are ignored, when a ttf/otf file is used no afm is read, > and when a pfb fils is used the afm is used (ligature adn kerning info etc) > but a wide font is assembled > > (when a ttf is used the lucidaot typescript file can serve as example) > > in mkxl we assume the otf files sold by TUG are used (recently the math font > was updated) > > > and not with the file specification as in: > > > > > > \starttypescript [mylucidaserif] % or mylucidasans > >\definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular] > >\definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic] > >\definefontsynonym[LucidaBrightBold] [file:LucidaBrightDemiBold] > > \stoptypescript > > > > and \setups[font:fallback:serif:sans] wouldn't be needed either > > > > you'd end up with > > in mkxl (lmtx) > > \setupbodyfont[lucida] > > will load open type definitions > > > mkiv lua stats > loaded patterns: en::1, load time: 0.000 > > mkiv lua stats > loaded fonts: 4 files: lucidabrightregular.otf, > > lucidasansregular.otf, latinmodern-math.otf, lmroman10-regular.otf > > so why not use lucida math fonts? I have. But only with a couple of math fonts. I don't have all these fonts. mkiv lua stats > loaded fonts: 3 files: lucidanewmathitalic.ttf, lucidanewmathsymbol.ttf, lucidabrightregular.otf mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 6 instances, 3 shared in backend, 1 common vectors, 2 common hashes, load time 16.733 seconds I do agree with you in that that loading time is perhaps unacceptable but… > > > > > mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 12 > > > > instances, 5 shared in backend, 3 common vectors, 2 common hashes, load > > > > time 16.898 seconds > > > > i assume that you don't get this 16 seconds load time each run > > > > You're correct. That's why you recommended to use otf first . > even with type one fonts 17 sec load time for a few fonts is not okay, i > expect more something like: > > mkiv lua stats > loaded fonts: 3 files: lucidabrightmathot.otf, > lucidabrightot.otf, lucidasansot.otf > mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 14 > instances, 10 shared in backend, 6 common vectors, 4 common hashes, load > time 0.161 seconds You ought to specify that must be only after subsequent callbacks. I just tried it with a one liner file of \setupbodyfont[lucida] and (looking around in disbelief) it took a whooping ahem fonts > names > skipped files: 164 fonts > names > duplicate files : 164 fonts > names > total scan time : 16.487 seconds before it produced even error mess
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On 3/28/2023 7:05 PM, Carlos via ntg-context wrote: On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote: On 3/27/2023 3:31 PM, Carlos via ntg-context wrote: mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf, lmroman10-regular.otf, lucidabrightregular.ttf, lucidasansregular.ttf i admit never having seen lucida ttf files (but when opentype ttf files are used with an afm file present then no map files are needed at all because we're in wide font mode and encidings are ignored) I hadn't either. But everything aligned and thought it was nice. You're right that loading a map file is not needed, but If you're concerned about afm files then bring these files over to the working directory, and then mtxrun --generate the same So yes. Even though the file was something like (intended originally to load the map file, correct?) but since the map file is no longer necessary then afm should suffice \starttypescript [serif] [lucida] [texnansi] \definefontsynonym[LucidaBrightDemiBold][texnansi-lucidabrightdemibold][encoding=texnansi] \definefontsynonym[LucidaBrightDemiItalic][texnansi-lucidabrightdemiitalic][encoding=texnansi] \definefontsynonym[LucidaBrightItalic][texnansi-lucidabrightitalic][encoding=texnansi] \definefontsynonym[LucidaBrightRegular][texnansi-lucidabrightregular][encoding=texnansi] \stoptypescript these encodings only make sense with mkii (in which case the map file tells pdftex if a ttf or pfb file is used) in mkiv encodings are ignored, when a ttf/otf file is used no afm is read, and when a pfb fils is used the afm is used (ligature adn kerning info etc) but a wide font is assembled (when a ttf is used the lucidaot typescript file can serve as example) in mkxl we assume the otf files sold by TUG are used (recently the math font was updated) and not with the file specification as in: \starttypescript [mylucidaserif] % or mylucidasans \definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular] \definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic] \definefontsynonym[LucidaBrightBold] [file:LucidaBrightDemiBold] \stoptypescript and \setups[font:fallback:serif:sans] wouldn't be needed either you'd end up with in mkxl (lmtx) \setupbodyfont[lucida] will load open type definitions mkiv lua stats > loaded patterns: en::1, load time: 0.000 mkiv lua stats > loaded fonts: 4 files: lucidabrightregular.otf, lucidasansregular.otf, latinmodern-math.otf, lmroman10-regular.otf so why not use lucida math fonts? mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 12 instances, 5 shared in backend, 3 common vectors, 2 common hashes, load time 16.898 seconds i assume that you don't get this 16 seconds load time each run You're correct. That's why you recommended to use otf first . even with type one fonts 17 sec load time for a few fonts is not okay, i expect more something like: mkiv lua stats > loaded fonts: 3 files: lucidabrightmathot.otf, lucidabrightot.otf, lucidasansot.otf mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 14 instances, 10 shared in backend, 6 common vectors, 4 common hashes, load time 0.161 seconds (so 100 times less load time here) 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On Sat, Mar 25, 2023 at 09:26:36PM +0100, Hans Hagen via ntg-context wrote: > On 3/25/2023 8:55 PM, Carlos via ntg-context wrote: > > Hello list: > > > > This is under a fresh TeXLive installation. Sort as to put aside any > > texlive prepackaged issues. > > > > And the followign lines is the output of the error I've been having with > > the call of context on a recent texlive installation by both mtxrun > > --generate and luatools --generate right after. > > there i no need to use luatools (it's something old from the early days) > > what does > > mtxrun --generate --verbose > > report (whre does it fail) > > > 57 \starttext > > 58 > > 59 \usetypescriptfile[type-lucida] > > 60 \usetypescript[Lucida][texnansi] > > 61 >> \setupbodyfont[MyLucida, 10pt] > > 62 > > 63 \input zapf > > 64 > > 65 \input tufte > > fwiw, lucida type one makes no sense any more because the opentype version > is way better (and in the updated math setup in lmtx we didn't even look at > it) > > > Is LuaLaTeX behaving the same way? > > > > Answer: no. > > no surprise because it doesn't use the same setup > > what cache path does > > mtxrun --variables > > report > > Hans > > Thanks a lot Hans! Of course your sugggestion by using otf rather than going through the ttf as it may be deprecated works. No doubt. But look at the output of only a few lines.. This is exactly what I wanted to see!: system >6: filename=texnansi-bandh-lucida.map filetype=map format=map foundname=/usr/local/texlive/2023/texmf-local/fonts/map/pdftex/context/texnansi-bandh-lucida.map fullname=/usr/local/texlive/2023/texmf-local/fonts/map/pdftex/context/texnansi-bandh-lucida.map usedmethod=database system > 13: filename=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightDemiBold.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightDemiBold.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightDemiBold.afm usedmethod=direct system > 14: filename=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightDemiItalic.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightDemiItalic.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightDemiItalic.afm usedmethod=direct system > 15: filename=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightItalic.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightItalic.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightItalic.afm usedmethod=direct system > 16: filename=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightRegular.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightRegular.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaBrightRegular.afm usedmethod=direct system > 17: filename=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansDemiBold.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansDemiBold.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansDemiBold.afm usedmethod=direct system > 18: filename=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansDemiOblique.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansDemiOblique.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansDemiOblique.afm usedmethod=direct system > 19: filename=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansOblique.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansOblique.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansOblique.afm usedmethod=direct system > 20: filename=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansRegular.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansRegular.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaSansRegular.afm usedmethod=direct system > 21: filename=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaTypewriterBold.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaTypewriterBold.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaTypewriterBold.afm usedmethod=direct system > 22: filename=/us
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
| lists | var: BIBINPUTS
resolvers | lists | exp: .\{home:.texlive2023/texmf-config, home:texmf,
!!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-fonts,
!!selfautoparent:texmf-local,
!!selfautoparent:texmf-dist}/bibtex/bib//\{home:.texlive2023/texmf-config,
home:texmf, !!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-fonts,
!!selfautoparent:texmf-local, !!selfautoparent:texmf-dist}/tex/context//
resolvers | lists | res: .\{/home/ce/.texlive2023/texmf-config,
/home/ce/texmf, !!/usr/local/texlive/2023/texmf-config,
!!/usr/local/texlive/2023/texmf-var, !!/usr/local/texlive/2023/texmf-project,
!!/usr/local/texlive/2023/texmf-fonts, !!/usr/local/texlive/2023/texmf-local,
!!/usr/local/texlive/2023/texmf-dist}/bibtex/bib/\{/home/ce/.texlive2023/texmf-config,
/home/ce/texmf, !!/usr/local/texlive/2023/texmf-config,
!!/usr/local/texlive/2023/texmf-var, !!/usr/local/texlive/2023/texmf-project,
!!/usr/local/texlive/2023/texmf-fonts, !!/usr/local/texlive/2023/texmf-local,
!!/usr/local/texlive/2023/texmf-dist}/tex/context/
resolvers | lists | BSTINPUTS
resolvers | lists | env: unset
resolvers | lists | var: BSTINPUTS
resolvers | lists | exp: .\{home:.texlive2023/texmf-config, home:texmf,
!!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-fonts,
!!selfautoparent:texmf-local,
!!selfautoparent:texmf-dist}/bibtex/bst//\{home:.texlive2023/texmf-config,
home:texmf, !!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-fonts,
!!selfautoparent:texmf-local, !!selfautoparent:texmf-dist}/tex/context//
resolvers | lists | res: .\{/home/ce/.texlive2023/texmf-config,
/home/ce/texmf, !!/usr/local/texlive/2023/texmf-config,
!!/usr/local/texlive/2023/texmf-var, !!/usr/local/texlive/2023/texmf-project,
!!/usr/local/texlive/2023/texmf-fonts, !!/usr/local/texlive/2023/texmf-local,
!!/usr/local/texlive/2023/texmf-dist}/bibtex/bst/\{/home/ce/.texlive2023/texmf-config,
/home/ce/texmf, !!/usr/local/texlive/2023/texmf-config,
!!/usr/local/texlive/2023/texmf-var, !!/usr/local/texlive/2023/texmf-project,
!!/usr/local/texlive/2023/texmf-fonts, !!/usr/local/texlive/2023/texmf-local,
!!/usr/local/texlive/2023/texmf-dist}/tex/context/
resolvers | lists | CLUAINPUTS
resolvers | lists | env: unset
resolvers | lists | var: CLUAINPUTS
resolvers | lists | exp:
.\/usr/local/texlive/2023/bin/x86_64-linuxmusl/lib/luametatex//
resolvers | lists | res:
.\/usr/local/texlive/2023/bin/x86_64-linuxmusl/lib/luametatex//
resolvers | lists | CMAPFONTS
resolvers | lists | env: unset
resolvers | lists | var: CMAPFONTS
resolvers | lists | exp: .\{home:.texlive2023/texmf-config, home:texmf,
!!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-fonts,
!!selfautoparent:texmf-local, !!selfautoparent:texmf-dist}/fonts/cmap//
resolvers | lists | res: .\{/home/ce/.texlive2023/texmf-config,
/home/ce/texmf, !!/usr/local/texlive/2023/texmf-config,
!!/usr/local/texlive/2023/texmf-var, !!/usr/local/texlive/2023/texmf-project,
!!/usr/local/texlive/2023/texmf-fonts, !!/usr/local/texlive/2023/texmf-local,
!!/usr/local/texlive/2023/texmf-dist}/fonts/cmap/
resolvers | lists | ENCFONTS
resolvers | lists | env: unset
resolvers | lists | var: ENCFONTS
resolvers | lists | exp: .\{home:.texlive2023/texmf-config, home:texmf,
!!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-fonts,
!!selfautoparent:texmf-local,
!!selfautoparent:texmf-dist}/fonts/data//\{home:.texlive2023/texmf-config,
home:texmf, !!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-fonts,
!!selfautoparent:texmf-local, !!selfautoparent:texmf-dist}/fonts/enc/{dvips,
pdftex}//
resolvers | lists | res: .\{/home/ce/.texlive2023/texmf-config,
/home/ce/texmf, !!/usr/local/texlive/2023/texmf-config,
!!/usr/local/texlive/2023/texmf-var, !!/usr/local/texlive/2023/texmf-project,
!!/usr/local/texlive/2023/texmf-fonts, !!/usr/local/texlive/2023/texmf-local,
!!/usr/local/texlive/2023/texmf-dist}/fonts/data/\{/home/ce/.texlive2023/texmf-config,
/home/ce/texmf, !!/usr/local/texlive/2023/texmf-config,
!!/usr/local/texlive/2023/texmf-var, !!/usr/local/texlive/2023/texmf-project,
!!/usr/local/texlive/2023/texmf-fonts, !!/usr/local/texlive/2023/texmf-local,
!!/usr/local/texlive/2023/texmf-dist}/fonts/enc/{dvips, pdftex}//
resolvers | lists | FONTCIDMAPS
resolvers | lists | env: unset
resolvers | lists | var: FONTCIDMAPS
resolvers | lists | exp: .\{home:.texlive202
[NTG-context] Cron /var/www/aanhet.net/context/bin/cron/context-mirror
receiving incremental file list ./ articles/ collect/present/ context/latest/ general/ general/columnsets/ general/faqs/ general/fonts/ general/magazines/ general/manuals/ general/mathml/ general/programs/ general/qrcs/ general/qrcs/keeppdf/ general/sources/ general/technotes/ general/uptodate/ itdemos/external/ex-files/ itdemos/internal/ itdemos/internal/calculat/ itdemos/internal/color/ itdemos/internal/cweb/ itdemos/internal/fonts/ itdemos/internal/gw/ itdemos/internal/johan/ itdemos/internal/maps/ itdemos/internal/media/ itdemos/internal/spell/ itdemos/internal/telecom/ itdemos/internal/travel/ pdftex/ pragma/ present/euronts/ present/road/ present/talks/ present/tug-2000/ specials/fonts/ texdemos/suite/ sent 204 bytes received 17,573 bytes 11,851.33 bytes/sec total size is 449,010,176 speedup is 25,257.93 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Cron /var/www/aanhet.net/context/bin/cron/context-mirror
receiving incremental file list ./ articles/ collect/present/ context/latest/ general/ general/columnsets/ general/faqs/ general/fonts/ general/magazines/ general/manuals/ general/mathml/ general/programs/ general/qrcs/ general/qrcs/keeppdf/ general/sources/ general/technotes/ general/uptodate/ itdemos/external/ex-files/ itdemos/internal/ itdemos/internal/calculat/ itdemos/internal/color/ itdemos/internal/cweb/ itdemos/internal/fonts/ itdemos/internal/gw/ itdemos/internal/johan/ itdemos/internal/maps/ itdemos/internal/media/ itdemos/internal/spell/ itdemos/internal/telecom/ itdemos/internal/travel/ pdftex/ pragma/ present/euronts/ present/road/ present/talks/ present/tug-2000/ specials/fonts/ texdemos/suite/ sent 196 bytes received 13,933 bytes 28,258.00 bytes/sec total size is 449,010,176 speedup is 31,779.33 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers
On 10/4/2022 12:53 PM, Leah Neukirchen wrote: Hans Hagen via ntg-context writes: On 10/4/2022 4:16 AM, Angel M Alganza via ntg-context wrote: On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via ntg-context wrote: When I print this "directly" (i.e. sending the raw PDF to the printer) on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page. I believe that is the exact same problem I have and that I described a few days ago in my email with subject "Missing letters and numbers in printout". I have some grids on my document, which gets printed out, but nothing else does. Another data point: Brother B205 doesn't print it either. But would all of these use the same licensed PDF renderer... The PDFs render fine on every PDF reader I could find. Same here. PDFs generated directly from Context MKIV from TeXLive 2022 using LuaTeX 1.5 render fine on these printers. I've also printed PDFs from pdfTeX in the past fine. Same here. Any ideas what I should try to help debug this? I was told that this is the default now, that isn't going to change, and that I could always use LuaTeX instead. I could also use LaTeX, I guess, but I'd rather keep using ConTeXt at least while my old 32 bits OpenBSD installation works. what happens if you include the lmtx pdf in a mkiv document as image On above Brother B205, this document: \starttext \externalfigure[foo.mkxl.pdf] \stoptext only prints the page number of the outer document, which is kept in a seperate font: NREXLC+LMRoman12-Regular CID Type 0C Identity-H yes yes yes 5 0 CLLXEY+LMRoman12-Regular CID Type 0C Identity-H yes yes yes 8 0 I tried converting the pdf with pdfjam (which uses pdfTeX internally) before, which probably uses similar mechanisms, and it didn't work either. what is sent to the printer .. maybe not pdf but something the printer driver produces 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers
Hans Hagen via ntg-context writes: > On 10/4/2022 4:16 AM, Angel M Alganza via ntg-context wrote: >> On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via >> ntg-context wrote: >> >>> When I print this "directly" (i.e. sending the raw PDF to the printer) >>> on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page. >> I believe that is the exact same problem I have and that I described >> a >> few days ago in my email with subject "Missing letters and numbers in >> printout". I have some grids on my document, which gets printed out, >> but nothing else does. Another data point: Brother B205 doesn't print it either. But would all of these use the same licensed PDF renderer... >>> The PDFs render fine on every PDF reader I could find. >> Same here. >> >>> PDFs generated directly from Context MKIV from TeXLive 2022 using >>> LuaTeX 1.5 render fine on these printers. >>> I've also printed PDFs from pdfTeX in the past fine. >> Same here. >> >>> Any ideas what I should try to help debug this? >> I was told that this is the default now, that isn't going to change, >> and >> that I could always use LuaTeX instead. I could also use LaTeX, I >> guess, but I'd rather keep using ConTeXt at least while my old 32 bits >> OpenBSD installation works. > what happens if you include the lmtx pdf in a mkiv document as image On above Brother B205, this document: \starttext \externalfigure[foo.mkxl.pdf] \stoptext only prints the page number of the outer document, which is kept in a seperate font: NREXLC+LMRoman12-Regular CID Type 0C Identity-H yes yes yes 5 0 CLLXEY+LMRoman12-Regular CID Type 0C Identity-H yes yes yes 8 0 I tried converting the pdf with pdfjam (which uses pdfTeX internally) before, which probably uses similar mechanisms, and it didn't work either. -- Leah Neukirchenhttps://leahneukirchen.org/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers
On 10/4/2022 4:16 AM, Angel M Alganza via ntg-context wrote: On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via ntg-context wrote: When I print this "directly" (i.e. sending the raw PDF to the printer) on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page. I believe that is the exact same problem I have and that I described a few days ago in my email with subject "Missing letters and numbers in printout". I have some grids on my document, which gets printed out, but nothing else does. The PDFs render fine on every PDF reader I could find. Same here. PDFs generated directly from Context MKIV from TeXLive 2022 using LuaTeX 1.5 render fine on these printers. I've also printed PDFs from pdfTeX in the past fine. Same here. Any ideas what I should try to help debug this? I was told that this is the default now, that isn't going to change, and that I could always use LuaTeX instead. I could also use LaTeX, I guess, but I'd rather keep using ConTeXt at least while my old 32 bits OpenBSD installation works. what happens if you include the lmtx pdf in a mkiv document as image 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers
On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via ntg-context wrote: When I print this "directly" (i.e. sending the raw PDF to the printer) on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page. I believe that is the exact same problem I have and that I described a few days ago in my email with subject "Missing letters and numbers in printout". I have some grids on my document, which gets printed out, but nothing else does. The PDFs render fine on every PDF reader I could find. Same here. PDFs generated directly from Context MKIV from TeXLive 2022 using LuaTeX 1.5 render fine on these printers. I've also printed PDFs from pdfTeX in the past fine. Same here. Any ideas what I should try to help debug this? I was told that this is the default now, that isn't going to change, and that I could always use LuaTeX instead. I could also use LaTeX, I guess, but I'd rather keep using ConTeXt at least while my old 32 bits OpenBSD installation works. Cheers, Ángel ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers
Hans Hagen via ntg-context writes: > On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote: >> Hi, >> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11. >> Here's a tiny test document, I disabled PDF compression but it also >> doesn't work with the default settings. >> \setupbackend[level=0,compresslevel=0] >> \starttext >> Just a line of text. >> \stoptext >> When I print this "directly" (i.e. sending the raw PDF to the >> printer) >> on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page. >> The PDFs render fine on every PDF reader I could find. >> Conversion to PostScript with pstopdf (poppler-22.07.0) and then >> sending the PS renders the document correctly on the printer. >> PDFs generated directly from Context MKIV from TeXLive 2022 using >> LuaTeX 1.5 render fine on these printers. >> I've also printed PDFs from pdfTeX in the past fine. >> I attached the non-working 'foo.pdf.mkix' >> and the working 'foo.pdf.mkiv' file. >> I tried to disable font subsetting to debug this further, but I >> couldn't figure out how to do it. > > subsetting should not be a problem and both files are subsetted (lmxt > a bit different but not fundamentally) Well the idea was to have the same font stream in both files, so we exclude that from the reasons it breaks. Curiously, when I use Deja Vu: \setupbodyfont[dejavu] Then I get a VHOYGZ+DejaVuSansMonoCID TrueType Identity-H yes yes yes 8 0 and the PDF prints fine! So it must be related to how Type 0C fonts are written out, I think. -- Leah Neukirchenhttps://leahneukirchen.org ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] LMTX generates PDFs with non-working fonts on real printers
On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote: Hi, I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11. Here's a tiny test document, I disabled PDF compression but it also doesn't work with the default settings. \setupbackend[level=0,compresslevel=0] \starttext Just a line of text. \stoptext When I print this "directly" (i.e. sending the raw PDF to the printer) on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page. The PDFs render fine on every PDF reader I could find. Conversion to PostScript with pstopdf (poppler-22.07.0) and then sending the PS renders the document correctly on the printer. PDFs generated directly from Context MKIV from TeXLive 2022 using LuaTeX 1.5 render fine on these printers. I've also printed PDFs from pdfTeX in the past fine. I attached the non-working 'foo.pdf.mkix' and the working 'foo.pdf.mkiv' file. I tried to disable font subsetting to debug this further, but I couldn't figure out how to do it. subsetting should not be a problem and both files are subsetted (lmxt a bit different but not fundamentally) Any ideas what I should try to help debug this? i'm clueless ... 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] LMTX generates PDFs with non-working fonts on real printers
Hi, I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11. Here's a tiny test document, I disabled PDF compression but it also doesn't work with the default settings. \setupbackend[level=0,compresslevel=0] \starttext Just a line of text. \stoptext When I print this "directly" (i.e. sending the raw PDF to the printer) on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page. The PDFs render fine on every PDF reader I could find. Conversion to PostScript with pstopdf (poppler-22.07.0) and then sending the PS renders the document correctly on the printer. PDFs generated directly from Context MKIV from TeXLive 2022 using LuaTeX 1.5 render fine on these printers. I've also printed PDFs from pdfTeX in the past fine. I attached the non-working 'foo.pdf.mkix' and the working 'foo.pdf.mkiv' file. I tried to disable font subsetting to debug this further, but I couldn't figure out how to do it. Any ideas what I should try to help debug this? foo.pdf.mkxl Description: Binary data foo.pdf.mkiv Description: Binary data cu, -- Leah Neukirchenhttps://leahneukirchen.org/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Fwd: Typesetting modern Greek (UTF8) with ConTeXt
Thanks Hanx for the fix!
>> Just curious: you're still in mkii?
No, I was just trying to compare an old project (nothing important) with
lmtx, otherwise I wouldn't have even noticed.
Adam
On Fri, Aug 12, 2022 at 8:14 AM Hans Hagen wrote:
> On 8/12/2022 2:57 AM, Adam Reviczky wrote:
> > Hi Hans,
> >
> > I get a 'Nonletter' error with *fmtutil* for the mkii greek patterns
> (from
> > the latest cont-tmf.zip 2022-08-05 17:17).
> >
> > Is that an issue with texlive's *fmtutil* itself or something wrong with
> > the mkii greek pattern file?
>
> Actually, we never had a greek hyphenation pattern file, only for
> ancient greek. Modern greek in mkii has not encoding defined (we're
> talking 2005 and before when Tomas made the greek encoding that dealt
> with utf in pdftex). It has to do with 'setting what are letters' and
> these modern greek patterns have plenty different.
>
> You can patch lang-grk.mkii:
>
> \installlanguage
>[\s!gr]
>[\c!spacing=\v!packed,
> \c!leftsentence=---,
> \c!rightsentence=---,
> \c!leftsubsentence=---,
> \c!rightsubsentence=---,
> \c!leftquote=\greekleftquot,
> \c!rightquote=\greekrightquot,
> \c!leftquotation=\greekleftquot,
> \c!rightquotation=\greekrightquot,
> % we're missing an encoding for greek
> \s!patterns=\s!agr,
> \s!mapping=\s!agr,
> \s!encoding=\s!agr,
> % but one can use mkiv / lmtx anyway
> \c!date={\v!day\ \v!month\ \v!year}]
>
> At least you get something. In mkiv and lmtx we have both.
>
> Just curious: you're still in mkii?
>
> 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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Fwd: Typesetting modern Greek (UTF8) with ConTeXt
On 8/12/2022 2:57 AM, Adam Reviczky wrote:
Hi Hans,
I get a 'Nonletter' error with *fmtutil* for the mkii greek patterns (from
the latest cont-tmf.zip 2022-08-05 17:17).
Is that an issue with texlive's *fmtutil* itself or something wrong with
the mkii greek pattern file?
Actually, we never had a greek hyphenation pattern file, only for
ancient greek. Modern greek in mkii has not encoding defined (we're
talking 2005 and before when Tomas made the greek encoding that dealt
with utf in pdftex). It has to do with 'setting what are letters' and
these modern greek patterns have plenty different.
You can patch lang-grk.mkii:
\installlanguage
[\s!gr]
[\c!spacing=\v!packed,
\c!leftsentence=---,
\c!rightsentence=---,
\c!leftsubsentence=---,
\c!rightsubsentence=---,
\c!leftquote=\greekleftquot,
\c!rightquote=\greekrightquot,
\c!leftquotation=\greekleftquot,
\c!rightquotation=\greekrightquot,
% we're missing an encoding for greek
\s!patterns=\s!agr,
\s!mapping=\s!agr,
\s!encoding=\s!agr,
% but one can use mkiv / lmtx anyway
\c!date={\v!day\ \v!month\ \v!year}]
At least you get something. In mkiv and lmtx we have both.
Just curious: you're still in mkii?
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Workshop at FrOSCon
Am 09.07.22 um 19:27 schrieb Henning Hraban Ramm via ntg-context: Am 09.07.22 um 17:48 schrieb juh+ntg-context--- via ntg-context: My workshop was accepted. What shall I cover? It's a workshop for beginners? - Installation - Hello word What would you cover? Project structure? Style creation? In my experience, most participants will know LaTeX, i.e. you must tell them to forget everything they believe to know about TeX ;P Oh, and don’t tell them that ConTeXt LMTX is much, much faster than any LaTeX, because that’s a secret ;) (On the German list TeX-D-L some are discussing if LuaTeX is better than pdfTeX/XeTeX, and some are complaining that LuaLaTeX is too slow, of course...) HR ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Transliteration
On 2/3/2022 10:01 PM, Mojca Miklavec wrote:
On Thu, 3 Feb 2022 at 21:41, Hans Hagen wrote:
I have also merged the Serbian hyphenation patterns, so there is no need
to switch the language in order to have hyphenation in transliterated text.
That was possible because cyrillic and latin scripts use different code
points, and there are no conflicts in patterns.
So I suggest merging the patterns for Serbian cyrillic and latin.
I'd like to hear Arthur / Mojca on that we can of course load them
both but if that is an upstream merge i'll wait for that
Yes, loading both patterns at once is definitely the correct approach.
That's what the rest of the TeX world already does (at least LuaTeX
and XeTeX; pdfTeX not of course), see
https://github.com/hyphenation/tex-hyphen/blob/master/hyph-utf8/tex/generic/hyph-utf8/loadhyph/loadhyph-sr-latn.tex
We have two sets of Cyrillic patterns (and several Latin ones as
well), so composing a single file was a bit of a (somewhat political)
challenge.
Now at least in theory the users are free to choose which of the two
sets of patterns they want.
I never checked what ConTeXt was doing with the Serbian patterns.
Personally I would suggest taking hyph-sh-cyrl.pat.txt and hyph-sh-latn.pat.txt.
we currently do this:
{ "sr", "hyph-sr","serbian", false, { "hyph-sr-cyrl",
"hyph-sr-latn" }, },
so you suggest to replace that by the "sh" variants
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] Transliteration
On Thu, 3 Feb 2022 at 21:41, Hans Hagen wrote: > > > I have also merged the Serbian hyphenation patterns, so there is no need > > to switch the language in order to have hyphenation in transliterated text. > > That was possible because cyrillic and latin scripts use different code > > points, and there are no conflicts in patterns. > > So I suggest merging the patterns for Serbian cyrillic and latin. > > I'd like to hear Arthur / Mojca on that we can of course load them > both but if that is an upstream merge i'll wait for that Yes, loading both patterns at once is definitely the correct approach. That's what the rest of the TeX world already does (at least LuaTeX and XeTeX; pdfTeX not of course), see https://github.com/hyphenation/tex-hyphen/blob/master/hyph-utf8/tex/generic/hyph-utf8/loadhyph/loadhyph-sr-latn.tex We have two sets of Cyrillic patterns (and several Latin ones as well), so composing a single file was a bit of a (somewhat political) challenge. Now at least in theory the users are free to choose which of the two sets of patterns they want. I never checked what ConTeXt was doing with the Serbian patterns. Personally I would suggest taking hyph-sh-cyrl.pat.txt and hyph-sh-latn.pat.txt. Mojca ___ 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] Critical Editions?
On 12/21/2021 10:50 AM, hanneder--- via ntg-context wrote: I just started switching after long years of typesetting with La-/Omega-/pdfTeX to Context and was exploring the capabilities of the program for typesetting critical editions. So I was wondering whether there is any updated information on how to produce critical editions? Maybe Idris has input because he made a partial inventory. There are all kind of mechanisms that support it but one needs to know where to look. Details: I was able to find the article "Ediciones críticas con ConTeXt" (is this in use?) as well as a plan of and a remark concerning critTeXt: "As I learned from a thread on NTG-context from early 2010 we shouldn't expect a dedicated package, but that ConTeXt will eventually incorporate the needed functionalities." What is the status of that? a lot related to numbering, referencing and notes and much of that is present so if you can team up with other critical edition users ... i suppose that Idris can send you his onthology-so-far 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] Critical Editions?
Thanks for bringing this topic up again. I'd also be highly interested in this!
Denis
> -Ursprüngliche Nachricht-
> Von: ntg-context Im Auftrag von hanneder--
> - via ntg-context
> Gesendet: Dienstag, 21. Dezember 2021 10:51
> An: ntg-context@ntg.nl
> Cc: hanne...@staff.uni-marburg.de
> Betreff: [NTG-context] Critical Editions?
>
>
> I just started switching after long years of typesetting with La-/Omega-
> /pdfTeX to Context and was exploring the capabilities of the program for
> typesetting critical editions. So I was wondering whether there is any
> updated information on how to produce critical editions?
>
>
> Details:
> I was able to find the article "Ediciones críticas con ConTeXt" (is this in
> use?)
> as well as a plan of and a remark concerning critTeXt: "As I learned from a
> thread on NTG-context from early 2010 we shouldn't expect a dedicated
> package, but that ConTeXt will eventually incorporate the needed
> functionalities." What is the status of that?
>
>
> I also found out that for simple editions context already works. For critical
> editions in my field we need both footnote references based on
> linenumbers (for prose), but also references to verse number, which can be
> entered manually. The main problem for me was to find the command
> \linenote :)
>
> % Setup of \linenote
> \setupnotation[linenote]
> [alternative=serried,width=broad,distance=.5em,display=no]
> \setupnote[linenote][way=bypage,paragraph=yes,rule=off]
>
> % \variant as a footnote without reference number \definenote [variant]
> [footnote] \setupnotation[variant][number=no]
> \setupnote[variant][way=bypage,paragraph=yes,rule=off]
>
> % Two "environments" for Sanskrit verses, one with, one without
> linenumbers.
>
> % SANSKRIT EDITION linenumbers
> \definelines[slokaed][][indenting={yes, small, even},
>
> before=\startnarrower\startlinenumbering,after=\stoplinenumbering\stopn
> arrower]
>
> % SANSKRIT EDITION plain (referring to verses)
> \definelines[slokaedplain][][indenting={yes, small, even},
>before=\startnarrower,after=\stopnarrower]
>
> With this the code of the edition can be pleasently minimalistic:
>
> \startslokaed
> mano buddhir ahaṃ prāṇās tanmātrendriyajīvanam
>yaṃ dṛṣṭvā\linenote{dṛṣṭvā ] dṛṣṭva G\lohi{pc}{1}} vinivartante tam
> \linenote{tam ] tat} upāsyam upāsmahe} \stopslokaed
>
>
> \startslokaedplain
> mano buddhir ahaṃ prāṇās tanmātrendriyajīvanam yaṃ dṛṣṭvā\variant{2c
> dṛṣṭvā ] dṛṣṭva} vinivartante tam \variant{2d tam ] tat} upāsyam upāsmahe
> (2) \stopslokaedplain
>
> So far, so good. Any hints to a more sophisticated solution are highly
> welcome. (I am a simple TeX
> user)
> Thanks
> Jürgen
>
>
>
> ---
>
> Prof. Dr. Juergen Hanneder
> Philipps-Universitaet Marburg
> FG Indologie u. Tibetologie
> Deutschhausstr.12
> 35032 Marburg
> Germany
> Tel. 0049-6421-28-24930
> hanne...@staff.uni-marburg.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
> __
> _
___
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] Critical Editions?
I just started switching after long years of typesetting with
La-/Omega-/pdfTeX to Context and was exploring the capabilities of the
program for typesetting critical editions. So I was
wondering whether there is any updated information on how to produce
critical editions?
Details:
I was able to find the article "Ediciones críticas con ConTeXt" (is
this in use?) as well as a
plan of and a remark concerning critTeXt: "As I learned from a thread
on NTG-context from early 2010 we shouldn't expect a dedicated
package, but that ConTeXt will eventually incorporate the needed
functionalities." What is the status of that?
I also found out that for simple editions context already works. For
critical editions in my
field we need both footnote references based on linenumbers (for
prose), but also references to
verse number, which can be entered manually. The main problem for me
was to find the command \linenote :)
% Setup of \linenote
\setupnotation[linenote]
[alternative=serried,width=broad,distance=.5em,display=no]
\setupnote[linenote][way=bypage,paragraph=yes,rule=off]
% \variant as a footnote without reference number
\definenote [variant] [footnote]
\setupnotation[variant][number=no]
\setupnote[variant][way=bypage,paragraph=yes,rule=off]
% Two "environments" for Sanskrit verses, one with, one without
linenumbers.
% SANSKRIT EDITION linenumbers
\definelines[slokaed][][indenting={yes, small, even},
before=\startnarrower\startlinenumbering,after=\stoplinenumbering\stopnarrower]
% SANSKRIT EDITION plain (referring to verses)
\definelines[slokaedplain][][indenting={yes, small, even},
before=\startnarrower,after=\stopnarrower]
With this the code of the edition can be pleasently minimalistic:
\startslokaed
mano buddhir ahaṃ prāṇās tanmātrendriyajīvanam
yaṃ dṛṣṭvā\linenote{dṛṣṭvā ] dṛṣṭva G\lohi{pc}{1}} vinivartante tam
\linenote{tam ] tat} upāsyam upāsmahe}
\stopslokaed
\startslokaedplain
mano buddhir ahaṃ prāṇās tanmātrendriyajīvanam
yaṃ dṛṣṭvā\variant{2c dṛṣṭvā ] dṛṣṭva} vinivartante tam \variant{2d
tam ] tat} upāsyam upāsmahe (2)
\stopslokaedplain
So far, so good. Any hints to a more sophisticated solution are highly
welcome. (I am a simple TeX
user)
Thanks
Jürgen
---
Prof. Dr. Juergen Hanneder
Philipps-Universitaet Marburg
FG Indologie u. Tibetologie
Deutschhausstr.12
35032 Marburg
Germany
Tel. 0049-6421-28-24930
hanne...@staff.uni-marburg.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] new upload, new trickery
endrightparbox{\ruledhbox{\smallinfofont[R #1.3]}}%
> %
> \samplefile{tufte}
> }
>
> But as this is not really user friendly, there is more: a mechanism for
> hooking in handlers.
>
> \definelocalboxes
>[linenumber]
>[command=\LeftNumber,
> location=left,
> width=3em,
> style=\bs,
> color=darkred]
>
> \definelocalboxes
>[linenumbertwo]
>[linenumber]
>[command=\RightNumber,
> location=right,
> width=6em,
> style=\bf,
> color=darkgreen]
>
> \definelocalboxes
>[linetext]
>[command=\LeftText,
> location=lefttext,
> style=\bs,
> color=darkblue]
>
> \definelocalboxes
>[linetexttwo]
>[linetext]
>[command=\RightText,
> location=righttext,
> style=\bf,
> color=darkgray]
>
> % just using the content
>
> % \protected\def\LeftNumber {\hbox to
> \localboxesparameter{width}{\strut\box\localboxcontentbox\hss)}}
> % \protected\def\RightNumber{\hbox to
> \localboxesparameter{width}{\strut(\hss\box\localboxcontentbox)}}
>
> % using the provided line number:
>
> % \def\LineNumberL{\the\localboxlinenumber}
> % \def\LineNumberR{\the\localboxlinenumber}
>
> % using a tex counter
>
> % \newcount\MyLineNumberL
> % \newcount\MyLineNumberR
> % \def\LineNumberL{\global\advance\MyLineNumberL\plusone\the\MyLineNumberL}
> % \def\LineNumberR{\global\advance\MyLineNumberR\plusone\the\MyLineNumberR}
>
> % using proper counters
>
> \definecounter[MyLineNumberL]
> \definecounter[MyLineNumberR]
>
> \setupcounter[MyLineNumberL][numberconversion=characters]
> \setupcounter[MyLineNumberR][numberconversion=romannumerals]
>
>
> \def\LineNumberL{\incrementcounter[MyLineNumberL]\convertedcounter[MyLineNumberL]}
>
> \def\LineNumberR{\incrementcounter[MyLineNumberR]\convertedcounter[MyLineNumberR]}
>
> \protected\def\LeftNumber {\hbox to
> \localboxesparameter{width}{\strut(\LineNumberL\hss)}}
> \protected\def\RightNumber{\hbox to
> \localboxesparameter{width}{\strut(\hss\LineNumberR)}}
>
> \protected\def\LeftText #1{#1\quad}
> \protected\def\RightText#1{\quad#1}
>
> \showframe
>
> \starttext
>
> \start
> \localbox[linenumber]{}%
> \localbox[linenumbertwo]{}%
> \localbox[linetext]{L}%
> \startlocalbox[linetexttwo]
> R
> \stoplocalbox
> \dorecurse{100}{
> \samplefile{tufte}
> \par
> }
> \stop
>
> If you play a bit with these low level mechanism the luametatex /
> context combination now permits weird applications (which for sure some
> of you will (ab)use). The above example shows how to implement line
> numbers (there are drawbacks compared to the existing mechanisms) and
> other stuff in the margins and text edges but the most important aspect
> is that when the content in these boxes has width, it will be taken into
> account in the par builder because that is what this is about: these
> local boxes are taken into acount when breaking lines. When the handlers
> kick in, you have
>
> \localboxattribute : more for internal use
> \localboxlinenumber: as the par builder sees it
> \localboxwidth : the local box width
> \localboxoffset : the total distance to the edge
> \localboxleftskip : the effective leftskip
> \localboxrightskip : the effective rightskip
> \localboxlefthang : the current shape related value
> \localboxrighthang : the current shape related value
> \localboxindent: only first line
> \localboxparfillleftskip : effective value (onky last line)
> \localboxparfillrightskip : effective value (only last line)
> \localboxovershoot : overfull compensation
>
> most of these relate to normalized lines and as such there is plenty to
> play with. Others can be seen in the examples.
>
> I might add some more control to both these 'injection' mechanism
> because directly out of the (pdftex/omega/luatex) they are not that
> useful (which is probably also why we don't use them.) These are cheap
> extensions so they don't really influence runtime much, so .. when not
> used ... no harm done. I really have no clue how useful this is.
>
> I need to ponder this usage:
>
> \definelocalboxes
>[linetextA]
>[command=\LeftTextA,
> location=lefttext,
> style=\bs,
> color=darkblue]
>
> \protected\def\LeftTextA#1{\llap{#1}\quad}
>
> \definelocalboxes
>[linetextB]
>[command=\LeftTextB,
> location=left,
> style=\bs,
> color=darkgreen]
>
> \protected\def\LeftTextB{\llap{\unhbox\localboxcontentbox}\quad}
>
> \startte
[NTG-context] new upload, new trickery
box)}}
% using the provided line number:
% \def\LineNumberL{\the\localboxlinenumber}
% \def\LineNumberR{\the\localboxlinenumber}
% using a tex counter
% \newcount\MyLineNumberL
% \newcount\MyLineNumberR
% \def\LineNumberL{\global\advance\MyLineNumberL\plusone\the\MyLineNumberL}
% \def\LineNumberR{\global\advance\MyLineNumberR\plusone\the\MyLineNumberR}
% using proper counters
\definecounter[MyLineNumberL]
\definecounter[MyLineNumberR]
\setupcounter[MyLineNumberL][numberconversion=characters]
\setupcounter[MyLineNumberR][numberconversion=romannumerals]
\def\LineNumberL{\incrementcounter[MyLineNumberL]\convertedcounter[MyLineNumberL]}
\def\LineNumberR{\incrementcounter[MyLineNumberR]\convertedcounter[MyLineNumberR]}
\protected\def\LeftNumber {\hbox to
\localboxesparameter{width}{\strut(\LineNumberL\hss)}}
\protected\def\RightNumber{\hbox to
\localboxesparameter{width}{\strut(\hss\LineNumberR)}}
\protected\def\LeftText #1{#1\quad}
\protected\def\RightText#1{\quad#1}
\showframe
\starttext
\start
\localbox[linenumber]{}%
\localbox[linenumbertwo]{}%
\localbox[linetext]{L}%
\startlocalbox[linetexttwo]
R
\stoplocalbox
\dorecurse{100}{
\samplefile{tufte}
\par
}
\stop
If you play a bit with these low level mechanism the luametatex /
context combination now permits weird applications (which for sure some
of you will (ab)use). The above example shows how to implement line
numbers (there are drawbacks compared to the existing mechanisms) and
other stuff in the margins and text edges but the most important aspect
is that when the content in these boxes has width, it will be taken into
account in the par builder because that is what this is about: these
local boxes are taken into acount when breaking lines. When the handlers
kick in, you have
\localboxattribute : more for internal use
\localboxlinenumber: as the par builder sees it
\localboxwidth : the local box width
\localboxoffset: the total distance to the edge
\localboxleftskip : the effective leftskip
\localboxrightskip : the effective rightskip
\localboxlefthang : the current shape related value
\localboxrighthang : the current shape related value
\localboxindent: only first line
\localboxparfillleftskip : effective value (onky last line)
\localboxparfillrightskip : effective value (only last line)
\localboxovershoot : overfull compensation
most of these relate to normalized lines and as such there is plenty to
play with. Others can be seen in the examples.
I might add some more control to both these 'injection' mechanism
because directly out of the (pdftex/omega/luatex) they are not that
useful (which is probably also why we don't use them.) These are cheap
extensions so they don't really influence runtime much, so .. when not
used ... no harm done. I really have no clue how useful this is.
I need to ponder this usage:
\definelocalboxes
[linetextA]
[command=\LeftTextA,
location=lefttext,
style=\bs,
color=darkblue]
\protected\def\LeftTextA#1{\llap{#1}\quad}
\definelocalboxes
[linetextB]
[command=\LeftTextB,
location=left,
style=\bs,
color=darkgreen]
\protected\def\LeftTextB{\llap{\unhbox\localboxcontentbox}\quad}
\starttext
\dorecurse{10}{some text #1 }
\leftparbox {\red \bf keyword}HERE\leftparbox{}
\dorecurse{10}{some text #1 }
\blank
{\dorecurse{10}{some text #1 }
\leftparbox {\red \bf keyword}test
\dorecurse{10}{some text #1 }}
\blank
{\dorecurse{10}{some text #1 }
\localbox[linetextA]{keyword}HERE
\dorecurse{10}{some text #1 }}
{\dorecurse{10}{some text #1 }
\localbox[linetextB]{keyword}HERE
\dorecurse{10}{some text #1 }}
{\dorecurse{10}{some text #1 }
\localbox[linetextB]{keyword 1}HERE1
\dorecurse{10}{some text #1 }
\localbox[linetextB]{keyword 2}HERE2
\dorecurse{10}{some text #1 }}
\stoptext
so there's always so echallenge left.
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] problem with MkIV/TeXlive/TEXMFCACHE
Hello Luigi,
you asked:
> On Fri, Aug 27, 2021 at 10:35 AM Rainer J.H. Brandt via ntg-context <
> ntg-context@ntg.nl> wrote:
>
> > Dear experts,
> >
> > I want to use ConTeXt MkIV as supplied by TeXlive 2021.
> > After installation, I ran "mtxrun --generate".
> > I also tried "context --generate".
> > Both create output in the wrong place.
> >
> > The TeXlive documentation says that ConTeXt uses TEXMFCACHE,
> > which uses the default $TEXMFSYSVAR;$TEXMFVAR in my texmf.cnf.
> > My TEXMFSYSVAR is /var/opt/texlive, but ConTeXt doesn't use it.
> > Instead, it creates /opt/texmf-var and creates its output there.
> > I don't understand why it used that path; I've never used or configured
> > it.
> >
> > How can I convice ConTeXt to use TEXMFSYSVAR?
> > [...]
>
> What does
> $> tlmgr conf
> say ?
The output is appended below and looks reasonable. In particular, it shows
that I installed under /opt/local/share/texlive and doesn't mention the
"mtxrun --generate" output path /opt/texmf-var at all.
Please note that I don't use tlmgr and also that I didn't use the TeX Live
installer. I built the binaries from their sources and then installed
the rest from the texmf archive file. I use other engines on a daily basis,
mostly pdflatex, and they work flawlessly.
Thanks, Rainer
=== version information ==
tlmgr revision 57970 (2021-02-27 15:17:34 +0100)
tlmgr using installation: /opt
executables found by searching PATH =
PATH:
/opt/local/bin:/opt/local/bin:/usr/local/bin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/bin:/sbin:/Users/rjhb/doc/cvs/rjhb/perl5/bin:.:/Applications/Qt/current/clang_64/bin:/usr/X11/bin
dvipdfmx: /opt/local/bin/dvipdfmx
dvips: /opt/local/bin/dvips
fmtutil: /opt/local/bin/fmtutil
kpsewhich: /opt/local/bin/kpsewhich
luatex:/opt/local/bin/luatex
mktexpk: /opt/local/bin/mktexpk
pdftex:/opt/local/bin/pdftex
tex: /opt/local/bin/tex
tlmgr: /opt/local/bin/tlmgr
updmap:/opt/local/bin/updmap
xetex: /opt/local/bin/xetex
=== active config files ==
config.ps:/opt/local/share/texlive/texmf-dist/dvips/config/config.ps
fmtutil.cnf: /opt/local/share/texlive/texmf-dist/web2c/fmtutil.cnf
mktex.cnf:/opt/local/share/texlive/texmf-dist/web2c/mktex.cnf
pdftexconfig.tex:
/opt/local/share/texlive/texmf-dist/tex/generic/tex-ini-files/pdftexconfig.tex
texmf.cnf:/opt/local/share/texlive/texmf-dist/web2c/texmf.cnf
updmap.cfg: /opt/local/share/texlive/texmf-dist/web2c/updmap.cfg
= font map files =
kanjix.map:
/opt/local/share/texlive/texmf-dist/fonts/map/dvipdfmx/updmap/kanjix.map
pdftex.map:
/opt/local/share/texlive/texmf-dist/fonts/map/pdftex/updmap/pdftex.map
ps2pk.map:
/opt/local/share/texlive/texmf-dist/fonts/map/dvips/updmap/ps2pk.map
psfonts.map:
/opt/local/share/texlive/texmf-dist/fonts/map/dvips/updmap/psfonts.map
=== kpathsea variables ===
ENCFONTS=.:{{}/Users/rjhb/etc/texmf,/Users/rjhb/var/texmf,/Users/rjhb/lib/texmf,!!/opt/local/share/texlive/texmf-local,!!/opt/local/share/texlive/texmf-config,!!/var/opt/texlive,!!/opt/local/share/texlive/texmf-dist}/fonts/enc//
SYSTEXMF=/var/opt/texlive:/opt/local/share/texlive/texmf-local:/opt/local/share/texlive/texmf-dist
TEXCONFIG={{}/Users/rjhb/etc/texmf,/Users/rjhb/var/texmf,/Users/rjhb/lib/texmf,!!/opt/local/share/texlive/texmf-local,!!/opt/local/share/texlive/texmf-config,!!/var/opt/texlive,!!/opt/local/share/texlive/texmf-dist}/dvips//
TEXFONTMAPS=.:{{}/Users/rjhb/etc/texmf,/Users/rjhb/var/texmf,/Users/rjhb/lib/texmf,!!/opt/local/share/texlive/texmf-local,!!/opt/local/share/texlive/texmf-config,!!/var/opt/texlive,!!/opt/local/share/texlive/texmf-dist}/fonts/map/{kpsewhich,pdftex,dvips,}//
TEXMF={{}/Users/rjhb/etc/texmf,/Users/rjhb/var/texmf,/Users/rjhb/lib/texmf,!!/opt/local/share/texlive/texmf-local,!!/opt/local/share/texlive/texmf-config,!!/var/opt/texlive,!!/opt/local/share/texlive/texmf-dist}
TEXMFCONFIG=/Users/rjhb/etc/texmf
TEXMFDBS={!!/opt/local/share/texlive/texmf-local,!!/opt/local/share/texlive/texmf-config,!!/var/opt/texlive,!!/opt/local/share/texlive/texmf-dist}
TEXMFDIST=/opt/local/share/texlive/texmf-dist
TEXMFHOME=/Users/rjhb/lib/texmf
TEXMFLOCAL=/opt/local/share/texlive/texmf-local
TEXMFMAIN=/opt/local/share/texlive/texmf-dist
TEXMFSYSCONFIG=/opt/local/share/texlive/texmf-config
TEXMFSYSVAR=/var/opt/texlive
TEXMFVAR=/Users/rjhb/var/texmf
TEXPSHEADERS=.:{{}/Users/rjhb/etc/texmf,/Users/rjhb/var/texmf,/Users/rjhb/lib/texmf,!!/opt/local/share/texlive/texmf-local,!!/opt/local/share/texlive/texmf-config,!!/var/opt/texlive,!!/opt/local/share/texlive/texmf-dist}/{dvips,f
Re: [NTG-context] Invalid keyword \spaceskip
On 6/27/2021 11:36 AM, Steffen Wolfrum wrote:
Am 27.06.2021 um 09:16 schrieb Hans Hagen :
On 6/26/2021 11:56 PM, Wolfgang Schuster wrote:
Steffen Wolfrum schrieb am 26.06.2021 um 23:38:
Am 26.06.2021 um 22:43 schrieb Wolfgang Schuster
:
Steffen Wolfrum schrieb am 26.06.2021 um 22:26:
PS: with
% engine=luatex
it works fine.
Add \relax after the last skip value, i.e.
\spaceskip = 1pt plus 1pt minus 1.5pt\relax
LMTX allows multiple plus and minus values for a skip value and the M in
Matilda starts the scan for an additional minus value.
Wow, this sounds interesting. Is there an example of how to use multiple values?
I think the only examples are in mails from Hans. When you set multiple plus or
minus values (as far as i remember) only the last setting is used and all
previous ones are ignored.
Maybe in some article. Anyway, here is an example:
\starttext
test \skip0=10pt plus 10pt minus 10pt plus 20pt
test \skip0=10pt plus 10pt plus 20pt minus 10pt
test \vrule width 10pt height 10pt depth 10pt depth 10pt height 10pt
% test \hbox to 10pt to 10pt {x}
\stoptext
compare pdftex and luametatex.
ok. but why does this run fine
\starttext
Test \spaceskip = 1.0pt plus 1pt minus 1.5pt Wolfgang
\stoptext
while this ends in an error message?
\starttext
Test \spaceskip = 1.0pt plus 1pt minus 1.5pt Matilda
\stoptext
because scanning is case insensitive so the m triggeres the keyword
error ... keep in mind that by omitting a \relax you've always been
lucky so far (probably no follow up texts that had plus or minus) ..
luametatex just warns earlier
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] Invalid keyword \spaceskip
> Am 27.06.2021 um 09:16 schrieb Hans Hagen :
>
> On 6/26/2021 11:56 PM, Wolfgang Schuster wrote:
>> Steffen Wolfrum schrieb am 26.06.2021 um 23:38:
>>>> Am 26.06.2021 um 22:43 schrieb Wolfgang Schuster
>>>> :
>>>>
>>>> Steffen Wolfrum schrieb am 26.06.2021 um 22:26:
>>>>> PS: with
>>>>>
>>>>> % engine=luatex
>>>>>
>>>>> it works fine.
>>>> Add \relax after the last skip value, i.e.
>>>>
>>>> \spaceskip = 1pt plus 1pt minus 1.5pt\relax
>>>>
>>>> LMTX allows multiple plus and minus values for a skip value and the M in
>>>> Matilda starts the scan for an additional minus value.
>>> Wow, this sounds interesting. Is there an example of how to use multiple
>>> values?
>> I think the only examples are in mails from Hans. When you set multiple plus
>> or minus values (as far as i remember) only the last setting is used and all
>> previous ones are ignored.
> Maybe in some article. Anyway, here is an example:
>
> \starttext
> test \skip0=10pt plus 10pt minus 10pt plus 20pt
>
> test \skip0=10pt plus 10pt plus 20pt minus 10pt
>
> test \vrule width 10pt height 10pt depth 10pt depth 10pt height 10pt
>
> % test \hbox to 10pt to 10pt {x}
>
> \stoptext
>
> compare pdftex and luametatex.
ok. but why does this run fine
\starttext
Test \spaceskip = 1.0pt plus 1pt minus 1.5pt Wolfgang
\stoptext
while this ends in an error message?
\starttext
Test \spaceskip = 1.0pt plus 1pt minus 1.5pt Matilda
\stoptext
Steffen
___
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] Invalid keyword \spaceskip
On 6/26/2021 11:56 PM, Wolfgang Schuster wrote:
Steffen Wolfrum schrieb am 26.06.2021 um 23:38:
Am 26.06.2021 um 22:43 schrieb Wolfgang Schuster
:
Steffen Wolfrum schrieb am 26.06.2021 um 22:26:
PS: with
% engine=luatex
it works fine.
Add \relax after the last skip value, i.e.
\spaceskip = 1pt plus 1pt minus 1.5pt\relax
LMTX allows multiple plus and minus values for a skip value and the M
in Matilda starts the scan for an additional minus value.
Wow, this sounds interesting. Is there an example of how to use
multiple values?
I think the only examples are in mails from Hans. When you set multiple
plus or minus values (as far as i remember) only the last setting is
used and all previous ones are ignored.
Maybe in some article. Anyway, here is an example:
\starttext
test \skip0=10pt plus 10pt minus 10pt plus 20pt
test \skip0=10pt plus 10pt plus 20pt minus 10pt
test \vrule width 10pt height 10pt depth 10pt depth 10pt height 10pt
% test \hbox to 10pt to 10pt {x}
\stoptext
compare pdftex and luametatex.
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] LMTX problem with doifmode in \setuplayout
Hans Hagen schrieb am 09.06.2021 um 00:08:
On 6/8/2021 11:44 PM, Wolfgang Schuster wrote:
Rik Kabel schrieb am 08.06.2021 um 23:01:
Yes, that works. Of course, to say that you can never be sure if
such combinations will work is not a welcome statement about the
state of ConTeXt.
More recent LMTX releases also now break older documents that worked
(with LMTX and MkIV) before. If there is an error in what was
previously written that is only noticed because of tighter
enforcement, that is one thing, but an undocumented change to
supported behaviour is less to be desired. And that it works with
dimensions but not on/off/yes/no is very strange and suggests some
other problem may be lurking.
Just because it did work doesn't mean it was intended to be used in
this case. The different behavior between keywords and dimensions is
a result of the different ways how the are implemented and the way
TeX (the engine) works when it reads arguments.
and, also in mkiv \dofmode is unexpandable so cannot act as keyword
(it might not crash but also doesn't work)
Here is a short example which demonstrates the differences between
LuaTeX (eTeX, pdfTeX etc.) and LuaMetaTeX.
\starttext
\def\one{first}
\def\two{second}
\def\foo{one}
\protected\def\bar{two}
\csname\foo\endcsname
\csname\bar\endcsname
\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
___
[NTG-context] new upload
Hi,
I uploaded a new lmtx version. This time a new mechanism.
-
From an upcoming details chapter:
-
The mechanism described here is still experimental. Although it could be
implemented in \MKIV\ it is only available in \LMTX. Already early in
\MKII\ we had a positioning mechanism available. At that time we had
\DVI\ output and specials were used to track positions. A script
calculated the positions that were then fed back into the second run.
Later Taco wrote \DVIPOS\ which sped up the analysis between runs. When
\PDFTEX\ showed, an equivalent positioning mechanism was added there. In
\MKIV\ positioning support was optimized a bit as part of the upgrading
process but the principles remained the same. The interface to
positioning comes with a lot of commands and many of them relate to what
we want to do with \METAFUN. The alternative interface discussed here is
a bit simpler and has (at least now) less commands and, combined with
local name spaces, can be easier to use in more local situations. It's
also integrated in the frequently used \type {\framed} commands and has
basic support at the \METAFUN\ end. The performance is comparable to the
regular positioning mechanisms but especially at the \METAPOST\ end has
less overhead.
-
Here are some examples:
-
\framed [synchronize=yes,align=normal] {%
test test test 1 \sync{one}{1}test test 2 \crlf
test test 1 \sync{one}{1}test test test 2 \crlf
test 1\sync{one}{1}test 2 \crlf
test test test test 1 \sync{one}{1}test test 2
}
\framed [synchronize=yes,align=normal] {%
one one \sync{a}{1}two \sync{a}{2}three \crlf
one one \sync{a}{1}two two \sync{a}{2}three \crlf
one \sync{a}{1}two \sync{a}{2}three \crlf
one one one \sync{a}{1}two \sync{a}{2}three
}
\framed [synchronize=yes,align=normal] {%
\syncanchor{one}{1}{1}A
\syncanchor{one}{2}{1}BBB
\syncanchor{one}{3}{1}C \crlf
\syncanchor{one}{1}{2}AA
\syncanchor{one}{3}{2}C \crlf
\syncanchor{one}{1}{3}AAA
\syncanchor{one}{2}{3}BB
\syncanchor{one}{3}{3}C
}
\framed [synchronize=yes,align=normal] {%
\alignanchor{one}{1}{1}{l}A
\alignanchor{one}{1}{2}{m}AA
\alignanchor{one}{1}{3}{r}AAA
\syncanchor {one}{1}{4}\crlf
\alignanchor{one}{2}{1}{right}B
\alignanchor{one}{2}{2}{middle}BB
\alignanchor{one}{2}{3}{left}BBB
\syncanchor {one}{2}{4}
}
\startuseMPgraphic{whatever-1}
fill OverlayBox withcolor "lightgray" ;
drawdot anchorxy("one", 0, 1)
withpen pencircle scaled 1mm
withcolor "red" ;
drawdot anchorxy("one", 0, 2)
withpen pencircle scaled 1mm
withcolor "red" ;
drawdot anchorxy("two", 0, 1)
withpen pencircle scaled 1mm
withcolor "red" ;
drawdot anchorxy("two", 0, 2)
withpen pencircle scaled 1mm
withcolor "red" ;
drawdot anchorxy("three", 0, 1)
withpen pencircle scaled 1mm
withcolor "red" ;
setbounds currentpicture to OverlayBox ;
\stopuseMPgraphic
\startuseMPgraphic{whatever-2}
pair a ; a := anchorxy("one", 0, 1) ;
pair b ; b := anchorxy("one", 0, 2) ;
drawarrow
anchorxy("one", 0, 1) { right } ..
anchorxy("one", 0, 2)
withcolor "blue" withtransparency (1,.75) ;
drawarrow
anchorxy("two", 0, 1) { down } ..
anchorxy("two", 0, 2)
withcolor "blue" withtransparency (1,.75) ;
drawarrow
anchorxy("two", 0, 1) { dir 30 } ..
anchorxy("three", 0, 1)
withcolor "blue" withtransparency (1,.75) ;
setbounds currentpicture to OverlayBox ;
\stopuseMPgraphic
\defineoverlay[whatever-1][\useMPgraphic{whatever-1}]
\defineoverlay[whatever-2][\useMPgraphic{whatever-2}]
\framed
[synchronize=yes,
align=normal,
offset=10pt,
frame=off,
background={whatever-1,foreground,whatever-2}]
{%
\markanchor{two}{0}{1}{\red\bf foo}%
\markanchor{one}{0}{1} bar rab oof\crlf
foo bar rab oof\crlf
oof rab bar foo\crlf
oof rab \markanchor{two}{0}{2}{\red\bf bar}%
\markanchor{one}{0}{2} foo%
\markanchor{three}{0}{1}%
}
\framed
[synchronize=yes,
align=normal,
offset=10pt,
frame=off,
background={whatever-1,foreground,whatever-2}]
{%
one one one \syncanchor{a}{1}{1}two two two
\syncanchor{a}{2}{1}three three\par
one \syncanchor{a}{1}{2}two
\syncanchor{a}{2}{2}three\par
one \syncanchor{a}{1}{3}two
\syncanchor{a}{2}{3}three\par
\blank
\markanchor{two}{0}{1}{\red\bf foo}%
\markanchor{one}{0}{1} bar
Re: [NTG-context] Issue running ConTeXt from TeX Live 2019 on Alpine Linux 3.12
On 2021-05-01, Mojca Miklavec wrote:
> On Fri, 30 Apr 2021 at 20:53, Nicola wrote:
>> Then, I run `mtxrun --generate`, which exits instantly with the output
>> reported below. However, that is apparently not enough. I still get:
>>
>> $ context Hello-world.tex
>> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
>
> This sounds like a missing or misconfigured texmfcnf.lua (which should
> be next to texmf.cnf).
> This would need to be handled by the distribution (Alpine Linux devs).
>
> Can you try to locate both files and share the contents? (There may
> also be multiple copies of them.)
I report below the content of the two files, as they are in TeX Live
2020 (I have switched to `docker pull alpine`, as suggested in another
post, in which I can install Tex Live 2020).
Nicola
~ # find / -name texmfcnf.lua
/usr/share/texmf-dist/web2c/texmfcnf.lua
~ # cat /usr/share/texmf-dist/web2c/texmfcnf.lua
-- public domain
-- ConTeXt needs a properly expanded TEXMFLOCAL, so here is a
-- bit of lua code to make that happen
local texmflocal = resolvers.prefixes.selfautoparent();
texmflocal = string.gsub(texmflocal, "20%d%d$", "texmf-local");
return {
type= "configuration",
version = "1.1.0",
date= "2012-05-24",
time= "12:12:12",
comment = "ConTeXt MkIV configuration file",
author = "Hans Hagen, PRAGMA-ADE, Hasselt NL",
content = {
-- Originally there was support for engines and progname but I don't
expect
-- other engines to use this file, so first engines were removed. After
that
-- if made sense also to get rid of progname. At some point specific
formats
-- will be supported but then as a subtable with fallbacks, which
sounds more
-- natural. Also, at some point the paths will become tables. For the
moment
-- I don't care too much about it as extending is easy.
variables = {
-- The following variable is predefined (but can be overloaded) and
in
-- most cases you can leve this one untouched. The built-in
definition
-- permits relocation of the tree.
--
-- TEXMFCNF =
"{selfautodir:,selfautoparent:}{,{/share,}/texmf{-local,}/web2c}"
--
-- more readable than "selfautoparent:{/texmf{-local,}{,/web2c},}}"
is:
--
-- TEXMFCNF = {
-- "selfautoparent:/texmf-local",
-- "selfautoparent:/texmf-local/web2c",
-- "selfautoparent:/texmf-dist",
-- "selfautoparent:/texmf/web2c",
-- "selfautoparent:",
-- }
-- only used for FONTCONFIG_PATH & TEXMFCACHE in TeX Live
TEXMFSYSVAR = "selfautoparent:texmf-var",
TEXMFVAR= "home:.texlive2020/texmf-var",
-- We have only one cache path but there can be more. The first
writable one
-- will be chosen but there can be more readable paths.
TEXMFCACHE = "$TEXMFSYSVAR;$TEXMFVAR",
TEXMFCONFIG = "home:.texlive2020/texmf-config",
-- I don't like this texmf under home and texmf-home would make more
-- sense. One never knows what installers put under texmf anywhere
and
-- sorting out problems will be a pain. But on the other hand ...
home
-- mess is normally under the users own responsibility.
--
-- By using prefixes we don't get expanded paths in the cache
__path__
-- entry. This makes the tex root relocatable.
TEXMFOS = "selfautodir:",
TEXMFDIST = "selfautoparent:texmf-dist",
TEXMFLOCAL = texmflocal,
TEXMFSYSCONFIG = "selfautoparent:texmf-config",
TEXMFFONTS = "selfautoparent:texmf-fonts",
TEXMFPROJECT= "selfautoparent:texmf-project",
TEXMFHOME = "home:texmf",
-- TEXMFHOME = os.name == "macosx" and "home:Library/texmf" or
"home:texmf",
-- We need texmfos for a few rare files but as I have a few more
bin trees
-- a hack is needed. Maybe other users also have texmf-platform-new
trees.
TEXMF =
"{$TEXMFCONFIG,$TEXMFHOME,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFPROJECT,!!$TEXMFFONTS,!!$TEXMFLOCAL,!!$TEXMFDIST}",
TEXFONTMAPS =
".;$TEXMF/fonts/data//;$TEXMF/fonts/map/{pdftex,dvips}//",
ENCFONT
[NTG-context] Luatex 1.13.0 announcement.
== LuaTeX 1.13.0 2021-03-12 == This is the release for TeX live 2021. Callback for nesting level used in tracingmacros. It is is a variant of \tracingstacklevels by Petr Olsak implemented in pdftex and xetex. Two TeX January 2021 DEK buglet fixes (H.Hagen) Mark math glyphs as protected (in order to prevent processing as text in base mode). Removed width/ic compensation for traditional math code path. When restricted system commands is enabled os.setenv has no effect. Minor clean-up and bugs fixed (see ChangeLog) -- luigi ___ 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] tex live code freeze
Hi, The 2021 texlive code is currently being frozen. This means that Mojca will check-in the current context release right before tl gets deep frozen. The MKII code (mkii and mpii files) hasn't changed so it should still work well with pdftex and xetex although I admit that I haven't checked to what extend updates to those engines have side effects for context, but I assume none. Let me know if there are problems. The MKIV code (mkiv, mkvi, mpiv, lua files) has changed but not much, mostly as a side effect of the code split and move to LMTX where the focus is on now. There have been recent changes in the metafun code, but new functionality is LMTX only, simply because we use an extended library (more features). Of course there have been some bug fixes to MKIV and if you think more (bugs) should be fixed let us know. The yearly texlive release is also the 'official' yearly current release but of course after that there will be updates when needed. In these updates we don't distinguish between betas and currents: we dropped that some time ago because it was only confusing. Last/this year much of LMTX (mkxl, mpxl, lmt files) already got split and I expect that this year all the lua and mp files also will be independent so that at some point we have a more or less frozen MKIV that uses luatex (which doesn't change fundamentally apart from fixes so we don't need to adapt code to it i.e. MKIV should keep working just like MKII does with pdftex; updates to for instance fonts and languages will be applied). I get the impression that most users already moved to LMTX which helped getting it in the state it is now (thanks for all the testing). Although MKII/MKIV serves a reference for functionality, new stuff got and gets added to LMTX. I could backport some but it probably makes no sense (some is probably easy). There is of course untested code like the overload protection mechasnisms but I have that enabled on my machine (users can do that too) so I can notice side effects. The new engine (luametatex) doesn't change much. Recent changes are mostly cosmetic and I don't expect many more fundamental additions, but who knows ... (not all in there is yet used extensively) and maybe context users have interesting demands that trigger extra stuff (read: challenges me). So apart from new trickery at the tex macro end, we also reach a more stable state in LMTX. Soon I'll pick up some todo's. Some users want parallel stuff (keeps coming up), I also want to see how we can do more metafun - let me know what is missing as I'm currently in metafun mode - and go over some older lua code that started as experiment but hasn't been checked recently. I also want to cleanup the export code a bit but it's kind of boring to do and maybe we should ditch some pdf backend functionilty that adobe dropped from its viewers. And there are always manuals to complete / update ... Anyway, the current LMTX release is also a kind of yearly snapshot. So, if there is some last minute stuff that needs to be done to context MKII and MKIV before the tl code freeze, let us know. 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] Warning: "nodes: unable to store reference from lua in tex"
usedmethod=database system >4: filename=cont-new.mkiv filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv usedmethod=database system >5: filename=lang-exc.lua filetype=scripts foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua usedmethod=database system >6: filename=lang-us.lua filetype=scripts foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua usedmethod=database system >7: filename=D:/Lukas/Jobs/Chrastany-D5.4-RDS/SO_201/t.mkiv foundname=D:/Lukas/Jobs/Chrastany-D5.4-RDS/SO_201/t.mkiv fullname=D:/Lukas/Jobs/Chrastany-D5.4-RDS/SO_201/t.mkiv usedmethod=direct system >8: filename=lm.lfg filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg usedmethod=database system >9: filename=lmroman12-regular filetype=otf format=otf foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf usedmethod=database system > 10: filename=latinmodern-math.otf filetype=opentypefonts foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf usedmethod=database system > 11: filename=lmmono12-regular filetype=otf format=otf foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmmono12-regular.otf fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmmono12-regular.otf usedmethod=database system > 12: filename=pdftex.map filetype=map format=map foundname=d:/Ctx-Beta/tex/texmf/fonts/map/pdftex/plain/pdftex.map fullname=d:/Ctx-Beta/tex/texmf/fonts/map/pdftex/plain/pdftex.map usedmethod=database system > 13: filename=lpdf-pdx.xml filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml usedmethod=database system > stop used files system > start commandline options system > currentrun="1" system > fulljobname="D:/Lukas/Jobs/Chrastany-D5.4-RDS/SO_201/t.mkiv" system > input="D:/Lukas/Jobs/Chrastany-D5.4-RDS/SO_201/t.mkiv" system > kindofrun="1" system > maxnofruns="9" system > nonstopmode="true" system > path="d:/Lukas/ConTeXt/Styles" system > texmfbinpath="d:/Ctx-Beta/tex/texmf-mswin/bin" system > stop commandline options system > start commandline files system >1: D:/Lukas/Jobs/Chrastany-D5.4-RDS/SO_201/t.mkiv system > stop commandline files modules > start used modules modules > stop used modules mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: d:/Ctx-Beta/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mkiv lua stats > resource resolver: loadtime 0.008 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 13 found files, scanned paths: mkiv lua stats > stored bytecode data: 454 modules (0.230 sec), 95 tables (0.013 sec), 549 chunks (0.243 sec) mkiv lua stats > traced context: maxstack: 1420, freed: 0, unreachable: 1420 mkiv lua stats > cleaned up reserved nodes: 57 nodes, 9 lists of 442 mkiv lua stats > node memory usage: 24 attribute, 8 attribute_list, 1 glue, 51 glue_spec, 3 kern, 3 penalty, 4 rule, 2 temp, 2 user_defined mkiv lua stats > node list callback tasks: 8 unique task lists, 6 instances (re)created, 10949 calls mkiv lua stats > h-node processing time: 0.027 seconds including kernel mkiv lua stats > attribute processing time: 0.059 seconds front- and backend mkiv lua stats > driver time: 0.066 seconds mkiv lua stats > used backend: pdf (backend for directly generating pdf output) mkiv lua stats > jobdata time: 0.004 seconds saving, 0.001 seconds loading mkiv lua stats > callbacks: internal: 55815, file: 82, direct: 3, late: 0, function 6072, total: 61972 (632 per page) mkiv lua stats > randomizer: resumed with value 0.30966186523438 mkiv lua stats > v-node processing time: 0.366 seconds mkiv lua stats > result saved in file: t.pdf, compresslevel 3, objectcompresslevel 1 mkiv lua stats > loaded patterns: en::1, load time: 0.000 mkiv lua stats > loaded fonts: 3 files: latinmodern-
Re: [NTG-context] composing commands
On 2/6/2021 12:01 AM, Thomas A. Schmitz wrote: On 2/5/21 10:30 PM, Hans Hagen wrote: Is this ok for you? tex error > tex error on line 6 in file ./oeps.tex: Undefined control sequence \v 4 5 \starttext 6 >> \v 7 \stoptext 8 Otared has already replied what I was thinking: would it be possible, for a certain period of time, to not stop compilation, but flag the issue on the console? When you say that such changes won't happen suddenly, this would be a wonderful compromise for me. My consolidated bibtex database began its life many many years ago, when bibtex was still pure 7bit, and you had to pepper your sources with all sorts of silly workarounds in order to get accents and umlauts and whatever you wanted. Those were the days - barefoot through the snow, and it was uphill both ways... So how did you do the greek then? I played a bit with an alternative implementation (same commands): less hash and mem, delegate more to lua. That way we can a less cost issue such a message (once only of course). There is of course a price to pay % .16 sec per 10 \"u : old method (more mkii-ish) % .25 sec per 10 \"u : new method (more lmtx-ish) (actually with mkii in pdftex we need .3 seconds, xetex freezes with 100K but needs 0.53 for 10K, luatex needs 0.18) but I'm sure you don't care much about that so I just implements a variant with warning which takes .19 seconds per 100K so it's a nice compromise. (Probably less than half of that time on your machine.) system > instead of old school '\"u' you can input the utf sequence ü (The old school narative is that context is slow, which is why we need to keep an eye on performance, right?) 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] composing commands
On 2/5/2021 5:49 PM, Jairo A. del Rio wrote: I agree with the optional alternative. If LuaMetaTeX goes (c)leaner, it can get rid of obsolete constructions made for a pre-Unicode world. Some are already angry with primitives gone and I think that's positive, but it's only my opinion. I never got saw angry mails here about gone primitives. Context commands seldom go away; in the transition to mkiv some encoding stuff became obsolete and after many years might have been removed from mkiv because no use needed/used them anyway. New stuff gets added, old stuff stays or gets improved. Primitives are an engine thing and there are differences between engines, for sure. When context overloads primitives (happens in a few cases) the original often is available as \normal. There is a core set of primives (original tex, luametatex has dropped some backend related ones and nilled some prefixes that we never used in context anyway), some etex enhancements brought new primitives (some make no sense in the luametex universe but one can always fake something), some auxiliary pdftex primitives never were available in lua(meta)tex because we have lua, and from omega/aleph we ended up with nearly nothing (luametatex dropped some useless direction stuff). So: no real harm done. And then of course luametatex brought some new primitives. When overloadmode is enabled one cannot redefine primitives and/or macros, depending on what property they have gotten (i'm now down to four pages todo). 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 and PDF.js
08. 01. 2021. u 05:41, Aditya Mahajan piše: On Fri, 8 Jan 2021, Hans Hagen wrote: On 1/8/2021 12:39 AM, Vedran Miletić wrote: It's whatever ConTeXt standalone has. I don't have any extra Lua installed: --credits should mention the lua version Should I see it on non-HiDPI as well? Because it seems it's there. depends on what you consider (non) hdpi ... the positioning of glyphs depends on font scale, rounding of stems and such (hints in fonts but these get less relevant with high res displays), caching, inter glyph corrections (that pdftex/luatex/...) put in the text stream to resync within certain tolerances, etc ... (often a print is a better reference as displays are seldom 600+ dpi) .. it's also why often expansion looks bad on screen because even a sub percentage difference can give such effects Another way to see it is just zoom in on the PDF. If the artifacts go away on zooming in, then they are due to anti-aliasing. Aditya Thanks to both of you for the detailed explanations. Printed page shows no artifacts and neither does PDF.js when the text is zoomed. So it is an issue with anti-aliasing after all. I'll report it to PDF.js and see what they tell me. Regards, Vedran -- Vedran Miletić vedran.miletic.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] LuaTeX and PDF.js
On Fri, 8 Jan 2021, Hans Hagen wrote: > On 1/8/2021 12:39 AM, Vedran Miletić wrote: > > > It's whatever ConTeXt standalone has. I don't have any extra Lua installed: > > --credits should mention the lua version > > > Should I see it on non-HiDPI as well? Because it seems it's there. > > depends on what you consider (non) hdpi ... the positioning of glyphs > depends on font scale, rounding of stems and such (hints in fonts but > these get less relevant with high res displays), caching, inter glyph > corrections (that pdftex/luatex/...) put in the text stream to resync > within certain tolerances, etc ... (often a print is a better reference > as displays are seldom 600+ dpi) .. it's also why often expansion looks > bad on screen because even a sub percentage difference can give such > effects Another way to see it is just zoom in on the PDF. If the artifacts go away on zooming in, then they are due to anti-aliasing. Aditya___ 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 and PDF.js
On 1/8/2021 12:39 AM, Vedran Miletić wrote: It's whatever ConTeXt standalone has. I don't have any extra Lua installed: --credits should mention the lua version Should I see it on non-HiDPI as well? Because it seems it's there. depends on what you consider (non) hdpi ... the positioning of glyphs depends on font scale, rounding of stems and such (hints in fonts but these get less relevant with high res displays), caching, inter glyph corrections (that pdftex/luatex/...) put in the text stream to resync within certain tolerances, etc ... (often a print is a better reference as displays are seldom 600+ dpi) .. it's also why often expansion looks bad on screen because even a sub percentage difference can give such effects 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] A not so short introduction to ConTeXt Mark IV
On 1/4/2021 5:32 PM, Joaquín Ataz López wrote:
Really? I wouldn't see it this way. I wondered a bit about the
number of primitives shown in the document of Joaquín, but that they
are used certainly doesn't make context like plaintex.
I have calculated the number of primitives from the list made in "TeX
Reference Manual" by David Bausum (of which there is a web version at
https://www.tug.org/utilities/plain/cseq.html).
According to that text the number of primitives is exactly 326. In my
document I rounded it to "approximately 300".
That list is a bit old. In the meantime we got etex extensions, which
adds a few more, and then pdftex ades some, as well as omega and after
that of course luatex. In luametatex we dropped some, and added others,
so there we currently have 770 primitives. The increase of number is
partly due to the 166 extra math related primitives of which many deal
with all kind of font related paraneters and inter-blob spacing.
\starttext
\startTEXpage[offset=2mm,width=30cm,align={verytolerant,nothyphenated,flushleft},foregroundstyle=\tttf]
\startluacode
local t = tex.primitives()
table.sort(t)
local n = 0
for i=1,#t do
if string.find(t[i],"^U") then
n =n + 1
end
end
context("%i / %i: % t",#t,n,t)
\stopluacode
\stopTEXpage
\stoptext
if yuou want to know if something is a primitive, say:
\meaningfull\vskip \par
\meaningfull\relax \par
\meaningfull\framed\par
and you get an idea (\meaningfull itself is a primitive, the more
verbose \meaning, and there's also \meaningless which I let you figure
out yourself; of course these add two primitives to the repertoire).
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] 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 ___
Re: [NTG-context] LMTX MkIV difference in expansion
On 11/19/2020 17:03, Hans Hagen wrote:
On 11/19/2020 9:41 PM, Wolfgang Schuster wrote:
Rik Kabel schrieb am 19.11.2020 um 21:20:
Another LMTX/MkIV difference, this time with expansion:
\define\Align{yes}
\starttext
\startalignment[\Align]
This works with MkIV but fails with LMTX, complaining: {\tt
tex error on line 3 in file G:/expand.mkvi: The file ended
when scanning an argument.}
\blank
It works in both when \tex{def} or \tex{defineexpandable} is
used instead of \tex{define}.
\blank
What changed?
\stopalignment
\stoptext
It may well be that I have been abusing some laxity in MkIV and that
LMTX is a bit stricter in what it accepts, but I would like to know
if this is an expected difference.
You have to wait for Hans to get an answer but here is a minimal
example.
\starttext
\protected\def\testparameter{test}
%\def\testparameter{test}
\def\test[#1]%
{\expandafter\let\expandafter\testargumentlist\csname#1\endcsname}
\test[\testparameter]
\stoptext
Often arguments to commands like \startsomething[xx] let the xx end up
in some \(if)csname expansion. A protected (\unexpanded in context
speak) macro doesn't expand inside for instance an \edef (or
comparable expandable situation). Now, from that it makes perfect
sense to also not let it expand inside a \csname or \ifcsname. One
reason is that when it does expand, you can get a pretty wild (nested)
sequence of nested expansions and one can be pretty sure that we then
don't have a proper csname. This is why in luatex we have a catch for
running wild csname checking.
The original \ifcsname test was inherited from etex. The \protected
feature also comes from etex. But \csname is a tex natural.
In pdftex (and luatex) a protected macro inside an \(if)csname does
expand which to makes no sense and smells like a bug. Or maybe it was
tricky to catch (the implementation of protected a bit of a hack).
In luametatex protected macros are native and in the process I also
decided to *not* expand them in a \(if)csname where I expect (as said)
protected macros to behave like in an edef. I nice side effect is that
running wild no longer happens (but we still catch it) which can save
quite some useless backup token list construction (needed because tex
has to push back stuff in order to be able to report an error).
So, when you still don't understand it (which I can understand) I'm
sure Wolfgang can explain it better now.
\starttext
\def\foo{foo}
\protected\def\oof{oof}
\csname foo\endcsname
\csname oof\endcsname
\csname \foo\endcsname
% error in luametatex, ok in pdftex/luatex:
% \csname \oof\endcsname
\ifcsname foo\endcsname yes\else nop\fi
\ifcsname oof\endcsname yes\else nop\fi
\ifcsname \foo\endcsname yes\else nop\fi
% nop in luametatex (error intercepted), yes in pdftex/luatex
\ifcsname \oof\endcsname yes\else nop\fi
\stoptext
Now, one can argue that if I consider it a but in the other engines,
why I don't argue that it should be solved. Well, there is too much
legacy code already that might use it as feature so it will not
change. But in luametatex we can 'fix' these things. (We also use the
csname in a rather predictable way in context so i don't expect issues
in the core.)
Hans
You are right about not quite understand.
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?
--
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
On 11/19/2020 9:41 PM, Wolfgang Schuster wrote:
Rik Kabel schrieb am 19.11.2020 um 21:20:
Another LMTX/MkIV difference, this time with expansion:
\define\Align{yes}
\starttext
\startalignment[\Align]
This works with MkIV but fails with LMTX, complaining: {\tt
tex error on line 3 in file G:/expand.mkvi: The file ended
when scanning an argument.}
\blank
It works in both when \tex{def} or \tex{defineexpandable} is
used instead of \tex{define}.
\blank
What changed?
\stopalignment
\stoptext
It may well be that I have been abusing some laxity in MkIV and that
LMTX is a bit stricter in what it accepts, but I would like to know if
this is an expected difference.
You have to wait for Hans to get an answer but here is a minimal example.
\starttext
\protected\def\testparameter{test}
%\def\testparameter{test}
\def\test[#1]%
{\expandafter\let\expandafter\testargumentlist\csname#1\endcsname}
\test[\testparameter]
\stoptext
Often arguments to commands like \startsomething[xx] let the xx end up
in some \(if)csname expansion. A protected (\unexpanded in context
speak) macro doesn't expand inside for instance an \edef (or comparable
expandable situation). Now, from that it makes perfect sense to also not
let it expand inside a \csname or \ifcsname. One reason is that when it
does expand, you can get a pretty wild (nested) sequence of nested
expansions and one can be pretty sure that we then don't have a proper
csname. This is why in luatex we have a catch for running wild csname
checking.
The original \ifcsname test was inherited from etex. The \protected
feature also comes from etex. But \csname is a tex natural.
In pdftex (and luatex) a protected macro inside an \(if)csname does
expand which to makes no sense and smells like a bug. Or maybe it was
tricky to catch (the implementation of protected a bit of a hack).
In luametatex protected macros are native and in the process I also
decided to *not* expand them in a \(if)csname where I expect (as said)
protected macros to behave like in an edef. I nice side effect is that
running wild no longer happens (but we still catch it) which can save
quite some useless backup token list construction (needed because tex
has to push back stuff in order to be able to report an error).
So, when you still don't understand it (which I can understand) I'm sure
Wolfgang can explain it better now.
\starttext
\def\foo{foo}
\protected\def\oof{oof}
\csname foo\endcsname
\csname oof\endcsname
\csname \foo\endcsname
% error in luametatex, ok in pdftex/luatex:
% \csname \oof\endcsname
\ifcsname foo\endcsname yes\else nop\fi
\ifcsname oof\endcsname yes\else nop\fi
\ifcsname \foo\endcsname yes\else nop\fi
% nop in luametatex (error intercepted), yes in pdftex/luatex
\ifcsname \oof\endcsname yes\else nop\fi
\stoptext
Now, one can argue that if I consider it a but in the other engines, why
I don't argue that it should be solved. Well, there is too much legacy
code already that might use it as feature so it will not change. But in
luametatex we can 'fix' these things. (We also use the csname in a
rather predictable way in context so i don't expect issues in the core.)
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] How to define a {\bf}-compatible fake-bold switcher?
On 11/7/2020 6:45 PM, Pablo Rodriguez wrote: On 11/7/20 6:18 PM, Sylvain Hubert wrote: Thank you so much, Pablo. This is exactly what I needed. Could you also tell me where you have learnt these features? I had been searching for this for hours but \effect was still the best of what I've got. Indeed, googling 'context+tex+boldened' or 'contextgarden+boldened' results in nothing useful. Well, I asked for that feature (https://mailman.ntg.nl/pipermail/ntg-context/2018/091128.html), which Ulrike Fischer requested a year before (https://mailman.ntg.nl/pipermail/ntg-context/2017/090091.html). And that year, BachoTeX included a presentation with the implemented feature (also included in LMTX @ tex/texmf-context/doc/context/presentations/bachotex/2018/bachotex-2018-fonteffects.pdf [also with sources]). I was very interested on that particular feature, because the previous fake bold feature was simple stretching. FYI. The literal based solution has been in context for a long time (already in mkii) .. the 'bachotex' one you refer to is different and although it does use pdf rendering primitives it is more about making sure that related dimensions etc are dealt with (more parameters and dimensions are involved in that). Actually, in luatex slanting and expanding (which is also kind of bondeling) have been inherited from pdftex. Boldening text is one case, but dealing with math yet another and the luatex engine only has some additional font property (linewidth) but all the rest has do be dealt with in lua. In lmtx the implementation of those specific font properties is a bit different. In the end it is not so much the linewidth that matters here (which is trivial) but the details which is why there are several parameters that one can tweak. For instance outlines are also done this way. (But as with many features, I'm not so sure if they are really used. The main reason for supporting it is not in text, because one should choose a proper font, but for math where bold (+heavy alphabets) are not widely available but needed for section heads.) 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] ConTeXt installation on Windows 10
Thank you Wolfgang ! It works nicely. Maybe it would be useful to change the wiki on ConteXt Garden (and other places where there is CTX help stuff ...). Such pages as here : https://wiki.contextgarden.net/ConTeXt_Standalone#Installation JP Le 04/07/2020 à 10:47, Wolfgang Schuster a écrit : Jean-Pierre Delange schrieb am 04.07.2020 um 10:33: Hello List ! Quite a dummy question : usually I use to work with CTX on Linux, but I want to install it on Windows 10 x64. Unfortunately, while I download CTX packages from there http://standalone.contextgarden.net/setup2/ , the next step fails : C:\Users\adeim\Documents\context>first-setup.bat The command returns this : "'rsync' is unknown as an internal or external command, an executable program or a command file. 'mtxrun' is not known as an internal or external command, an executable program or a command file." The same thing occurs while context is as a file at the very root on c:\, or within c:\windows, or in C:\Users\adeim\Documents\context> I suggest to use the installer from Hans website when you don't need pdfTeX. http://www.pragma-ade.nl/install.htm 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 ___ ___ 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] ConTeXt installation on Windows 10
Jean-Pierre Delange schrieb am 04.07.2020 um 10:33: Hello List ! Quite a dummy question : usually I use to work with CTX on Linux, but I want to install it on Windows 10 x64. Unfortunately, while I download CTX packages from there http://standalone.contextgarden.net/setup2/ , the next step fails : C:\Users\adeim\Documents\context>first-setup.bat The command returns this : "'rsync' is unknown as an internal or external command, an executable program or a command file. 'mtxrun' is not known as an internal or external command, an executable program or a command file." The same thing occurs while context is as a file at the very root on c:\, or within c:\windows, or in C:\Users\adeim\Documents\context> I suggest to use the installer from Hans website when you don't need pdfTeX. http://www.pragma-ade.nl/install.htm 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 ___
[NTG-context] Checking existence of a macro (control sequence) by Lua - problem after updating MkIV
ethod=database
system >9: filename=lmroman12-regular filetype=otf format=otf
foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
usedmethod=database
system > 10: filename=latinmodern-math.otf filetype=opentypefonts
foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf
fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf
usedmethod=database
system > 11: filename=pdftex.map filetype=map format=map
foundname=d:/Ctx-Beta/tex/texmf/fonts/map/pdftex/plain/pdftex.map
fullname=d:/Ctx-Beta/tex/texmf/fonts/map/pdftex/plain/pdftex.map
usedmethod=database
system > 12: filename=lpdf-pdx.xml filetype=tex
foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml
fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml
usedmethod=database
system > stop used files
system > start commandline options
system > currentrun="1"
system > fulljobname="D:/Lukas/ConTeXt/Test/IsMacDef3.mkiv"
system > input="D:/Lukas/ConTeXt/Test/IsMacDef3.mkiv"
system > kindofrun="1"
system > maxnofruns="9"
system > nonstopmode="true"
system > path="d:/Lukas/ConTeXt/Styles"
system > texmfbinpath="d:/Ctx-Beta/tex/texmf-mswin/bin"
system > stop commandline options
system > start commandline files
system >1: D:/Lukas/ConTeXt/Test/IsMacDef3.mkiv
system > stop commandline files
modules > start used modules
modules > stop used modules
mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua
mkiv lua stats > used cache path:
d:/Ctx-Beta/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e
mkiv lua stats > resource resolver: loadtime 0.008 seconds, 0 scans with
scantime 0.000 seconds, 0 shared scans, 12 found files, scanned paths:
mkiv lua stats > stored bytecode data: 452 modules (0.231 sec), 93 tables
(0.013 sec), 545 chunks (0.244 sec)
mkiv lua stats > traced context: maxstack: 1409, freed: 0, unreachable: 1409
mkiv lua stats > cleaned up reserved nodes: 57 nodes, 9 lists of 442
mkiv lua stats > node memory usage: 11 attribute, 4 attribute_list, 1 glue, 51
glue_spec, 3 kern, 2 penalty, 2 temp, 2 user_defined
mkiv lua stats > node list callback tasks: 8 unique task lists, 7 instances
(re)created, 38 calls
mkiv lua stats > used backend: pdf (backend for directly generating pdf output)
mkiv lua stats > jobdata time: 0.001 seconds saving, 0.001 seconds loading
mkiv lua stats > callbacks: internal: 138, file: 179, direct: 3, late: 0,
function 502, total: 822
mkiv lua stats > randomizer: resumed with value 0.54769897460938
mkiv lua stats > result saved in file: IsMacDef3.pdf, compresslevel 3,
objectcompresslevel 1
mkiv lua stats > loaded patterns: en::1, load time: 0.000
mkiv lua stats > loaded fonts: 2 files: latinmodern-math.otf,
lmroman12-regular.otf
mkiv lua stats > font engine: otf 3.111, afm 1.513, tfm 1.000, 7 instances, 3
shared in backend, 3 common vectors, 0 common hashes, load time 0.191 seconds
mkiv lua stats > used platform: mswin, type: windows, binary subtree:
texmf-mswin
mkiv lua stats > used engine: luatex version: 1.13, functionality level: 7353,
banner: this is luatex, version 1.13.0 (tex live 2020/w32tex)
mkiv lua stats > used hash slots: 45878 of 65536 + 10
mkiv lua stats > lua properties: engine: lua 5.3, used memory: 71 MB, ctx: 70
MB, max: unknown MB, hash chars: min(32,40), symbol mask: utf (τεχ)
mkiv lua stats > runtime: 0.494 seconds, 1 processed pages, 1 shipped pages,
2.024 pages/second
\starttext
\def\MyMacro{Ahoj}
\def\MyMacWithPars#1#2{Something}
\def\Undefined{}
\let\Undefined\undefined
\def\DoNothing{}
\let\DoNothing\donothing
\startluacode
if CONTEXTLMTXMODE == 0 then
local d = tokens.defined
local c = tokens.create
function tokens.defined(s,b)
if b then
return d(s)
else
return c(s).cmd_name == "undefined_cmd"
end
end
end
--
local defined = tokens.defined
for _, v in ipairs{ "MyMacro", "MyMacWithPars", "Undefined", "DoNothing",
"NonExisting" } do
print(string.format("\letterpercent-12s", v), defined(v), defined(v,
true), defined(v, false))
end
\stopluacode
Aaa
\stoptext
resolvers | formats | executing runner 'run luatex format':
d:/Ctx-Beta/tex/texmf-mswin/bin/luatex --interaction="nonstopmode" --j
[NTG-context] Columns: rule=on not working?
> xmp > using file 'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1, subpage 1 close source> level 2, order 6, name 'D:/Lukas/ConTeXt/Test/!Ctx/ColsRuleOn~.mkiv' close source> level 1, order 6, name 'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv' system > start used files system > text: ColsRuleOn~ system > stop used files system > start used files system >1: filename=char-prv.lua filetype=tex format=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/char-prv.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/char-prv.lua usedmethod=database system >2: filename=cont-yes.mkiv filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv usedmethod=database system >3: filename=publ-imp-default.lua filetype=scripts foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/publ-imp-default.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/publ-imp-default.lua usedmethod=database system >4: filename=cont-new.mkiv filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv usedmethod=database system >5: filename=lang-exc.lua filetype=scripts foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua usedmethod=database system >6: filename=lang-us.lua filetype=scripts foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua usedmethod=database system >7: filename=D:/Lukas/ConTeXt/Test/!Ctx/ColsRuleOn~.mkiv foundname=D:/Lukas/ConTeXt/Test/!Ctx/ColsRuleOn~.mkiv fullname=D:/Lukas/ConTeXt/Test/!Ctx/ColsRuleOn~.mkiv usedmethod=direct system >8: filename=lm.lfg filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg usedmethod=database system >9: filename=lmroman12-regular filetype=otf format=otf foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf usedmethod=database system > 10: filename=latinmodern-math.otf filetype=opentypefonts foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf usedmethod=database system > 11: filename=knuth filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/sample/common/knuth.tex fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/sample/common/knuth.tex usedmethod=database system > 12: filename=pdftex.map filetype=map format=map foundname=d:/Ctx-Beta/tex/texmf/fonts/map/pdftex/plain/pdftex.map fullname=d:/Ctx-Beta/tex/texmf/fonts/map/pdftex/plain/pdftex.map usedmethod=database system > 13: filename=lpdf-pdx.xml filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml usedmethod=database system > stop used files system > start commandline options system > currentrun="3" system > fulljobname="D:/Lukas/ConTeXt/Test/!Ctx/ColsRuleOn~.mkiv" system > input="D:/Lukas/ConTeXt/Test/!Ctx/ColsRuleOn~.mkiv" system > kindofrun="2" system > maxnofruns="9" system > nonstopmode="true" system > path="d:/Lukas/ConTeXt/Styles" system > texmfbinpath="d:/Ctx-Beta/tex/texmf-mswin/bin" system > stop commandline options system > start commandline files system >1: D:/Lukas/ConTeXt/Test/!Ctx/ColsRuleOn~.mkiv system > stop commandline files modules > start used modules modules > stop used modules mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: d:/Ctx-Beta/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mkiv lua stats > resource resolver: loadtime 0.009 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 13 found files, scanned paths: mkiv lua stats > stored bytecode data: 452 modules (0.237 sec), 93 tables (0.013 sec), 545 chunks (0.250 se
Re: [NTG-context] Retrieving original value of enviroment variable HOME
3 C:/Users/u×ivatel 4 C:/Users/u×ivatel whilst HOME environment has been set to "DummyHome" (see "echo %HOME%"). What's wrong? Lukas On 2020-05-11 10:51, Hans Hagen wrote: Hi, system > ConTeXt ver: 2020.01.30 14:13 MKIV beta fmt: 2020.5.10 int: english/english Did I updated ConTeXt correctly? Well, you made a fresh format, but use a version from january, so ... Hans open source > level 1, order 1, name 'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv' system > system > ConTeXt ver: 2020.05.08 20:46 MKIV beta fmt: 2020.5.11 int: english/english system > system > 'cont-new.mkiv' loaded open source > level 2, order 2, name 'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' system > beware: some patches loaded from cont-new.mkiv close source> level 2, order 2, name 'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' system > files > jobname 'EnvHome', input './EnvHome.mkiv', result 'EnvHome' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 2, order 3, name 'd:/Lukas/ConTeXt/Test/EnvHome/EnvHome.mkiv' fonts > preloading latin modern fonts (second stage) fonts > 'fallback modern-designsize rm 12pt' is loaded backend > xmp > using file 'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1, subpage 1 close source> level 2, order 3, name 'd:/Lukas/ConTeXt/Test/EnvHome/EnvHome.mkiv' close source> level 1, order 3, name 'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv' system > start used files system > text: EnvHome system > stop used files system > start used files system >1: filename=char-prv.lua filetype=tex format=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/char-prv.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/char-prv.lua usedmethod=database system >2: filename=cont-yes.mkiv filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv usedmethod=database system >3: filename=publ-imp-default.lua filetype=scripts foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/publ-imp-default.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/publ-imp-default.lua usedmethod=database system >4: filename=cont-new.mkiv filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv usedmethod=database system >5: filename=lang-exc.lua filetype=scripts foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua usedmethod=database system >6: filename=lang-us.lua filetype=scripts foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua usedmethod=database system >7: filename=d:\Lukas\ConTeXt\Test\EnvHome/EnvHome.mkiv foundname=d:/Lukas/ConTeXt/Test/EnvHome/EnvHome.mkiv fullname=d:/Lukas/ConTeXt/Test/EnvHome/EnvHome.mkiv usedmethod=direct system >8: filename=lm.lfg filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg usedmethod=database system >9: filename=lmroman12-regular filetype=otf format=otf foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf usedmethod=database system > 10: filename=latinmodern-math.otf filetype=opentypefonts foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf usedmethod=database system > 11: filename=pdftex.map filetype=map format=map foundname=d:/Ctx-Beta/tex/texmf/fonts/map/pdftex/plain/pdftex.map fullname=d:/Ctx-Beta/tex/texmf/fonts/map/pdftex/plain/pdftex.map usedmethod=database system > 12: filename=lpdf-pdx.xml filetype=tex foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml usedmethod=database system
Re: [NTG-context] Retrieving original value of enviroment variable HOME
ges, 2.004 pages/second
...
d:\Lukas\ConTeXt\Test\EnvHome>
3. So, logged:
"
system > ConTeXt ver: 2020.01.30 14:13 MKIV beta fmt:
2020.5.10 int: english/english
...
1 C:/Users/u×ivatel
2 nil
3 C:/Users/u×ivatel
4 C:/Users/u×ivatel
"
4. I also didn't find any "oldhome" text using fulltext search in
ConTeXt installation directory.
Did I updated ConTeXt correctly?
Lukas
On 2020-05-10 17:20, Hans Hagen wrote:
On 5/10/2020 2:33 PM, cont...@vivaldi.net wrote:
I've just renewed the Ctx Beta installation, but 'environment.oldhome'
seems be unavailable.
are you ser HOME is set?
\ctxlua{print("1",environment.homedir)}
\ctxlua{print("2",environment.oldhome)}
\ctxlua{print("3",os.getenv("HOME"))}
\ctxlua{print("4",os.getenv("USERPROFILE"))}
gives 4 values here
Hans
open source > level 1, order 1, name
'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv'
system >
system > ConTeXt ver: 2020.01.30 14:13 MKIV beta fmt: 2020.5.10
int: english/english
system >
system > 'cont-new.mkiv' loaded
open source > level 2, order 2, name
'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
system > beware: some patches loaded from cont-new.mkiv
close source> level 2, order 2, name
'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
system > files > jobname 'EnvHome', input './EnvHome.mkiv', result
'EnvHome'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 2, order 3, name
'd:/Lukas/ConTeXt/Test/EnvHome/EnvHome.mkiv'
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
backend > xmp > using file
'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1, subpage 1
close source> level 2, order 3, name
'd:/Lukas/ConTeXt/Test/EnvHome/EnvHome.mkiv'
close source> level 1, order 3, name
'd:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv'
system > start used files
system > text: EnvHome
system > stop used files
system > start used files
system >1: filename=char-prv.lua filetype=tex format=tex
foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/char-prv.lua
fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/char-prv.lua
usedmethod=database
system >2: filename=cont-yes.mkiv filetype=tex
foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv
fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv
usedmethod=database
system >3: filename=publ-imp-default.lua filetype=scripts
foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/publ-imp-default.lua
fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/publ-imp-default.lua
usedmethod=database
system >4: filename=cont-new.mkiv filetype=tex
foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv
fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv
usedmethod=database
system >5: filename=lang-exc.lua filetype=scripts
foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua
fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua
usedmethod=database
system >6: filename=lang-us.lua filetype=scripts
foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua
fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua
usedmethod=database
system >7: filename=d:\Lukas\ConTeXt\Test\EnvHome/EnvHome.mkiv
foundname=d:/Lukas/ConTeXt/Test/EnvHome/EnvHome.mkiv
fullname=d:/Lukas/ConTeXt/Test/EnvHome/EnvHome.mkiv usedmethod=direct
system >8: filename=lm.lfg filetype=tex
foundname=d:/Ctx-Beta/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg
fullname=d:/Ctx-Beta/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg
usedmethod=database
system >9: filename=lmroman12-regular filetype=otf format=otf
foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
usedmethod=database
system > 10: filename=latinmodern-math.otf filetype=opentypefonts
foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf
fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf
