[NTG-context] Re: How to tell a single *.tex file to produce separate PDFs?
Hi Bruce,
I had an analogous problem a while ago, but with 7 chapter files, which I
treated manually…
Your solution is a very nice one, thank you for sharing !
For the archives, if one wishes to have the correct chapter number in each
separate PDF file, one could change the content of « test.tex » file as follows:
\starttext
\setupheadnumber[chapter][\cldcontext{\env{ChapNo}-1}]
\input chapter-\env{ChapNo}.tex
\stoptext
Best regards: Otared
> On 20 Sep 2024, at 19:04, Bruce Horrocks wrote:
>
>
>
>> On 20 Sep 2024, at 03:57, Joel via ntg-context wrote:
>>
>> I have a document that's quite long. It uses a recurse function, a bit like
>> this:
>>
>> \starttext
>>
>>\dostepwiserecurse{1}{180}{1}{%
>>
>> \input chapter\recurselevel
>>
>> }
>>
>> \stoptext
>>
>> That produces 180 chapters of content.
>>
>> Anyway, my boss is upset she has to use a table of contents to navigate to
>> the page she wants, and so wants me to split the file into 180 separate
>> files, which somehow is going to be easier to look at. Honestly, she
>> probably still won't ever actually look at it, but that's her requirement.
>
> Since you’ve already got the chapter content split into separate \input files
> ...
>
> At the Unix level, use the following script to run Context 180 times
> specifying a different output file each time:
>
> #! /bin/bash
> for i in {1..180}
> do
> context \
>--arguments="ChapNo=$i" test.tex \
>--result="chapter_$i.pdf”
> done
>
> And at the Context level, test.tex is simply:
>
> \starttext
> \input chapter\env{ChapNo}
> \stoptext
>
>
> Regards,
> —
> Bruce Horrocks
> Hampshire, UK
>
> ___
> 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
> ___
Otared Kavian
e-mail: ota...@gmail.com
Phone: +33 6 88 26 70 95
___
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: How to tell a single *.tex file to produce separate PDFs?
On Fri, 20 Sep 2024 10:33:55 +0200 Denis Maier via ntg-context wrote: > I was going to suggest pdftk which is similar to mutools. There is also qpdf. However, running a shell script to run context many times is my favorite solution. This question brings up the topic: would it be useful to be able to do the same within context, either using lua or TeX programming? Alan ___ 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: How to tell a single *.tex file to produce separate PDFs?
I am using Linux, so those tools are available, but Bruce's solution is
working great! Just had to make tiny changes to the file.
I had no idea I could send an environment variable to ConTeXt...will be using
that a lot from now! Thanks very much everyone for the help!
On Friday, September 20, 2024 at 11:04:47 AM MDT, Bruce Horrocks
wrote:
> On 20 Sep 2024, at 03:57, Joel via ntg-context wrote:
>
> I have a document that's quite long. It uses a recurse function, a bit like
> this:
>
> \starttext
>
> \dostepwiserecurse{1}{180}{1}{%
>
> \input chapter\recurselevel
>
> }
>
> \stoptext
>
> That produces 180 chapters of content.
>
> Anyway, my boss is upset she has to use a table of contents to navigate to
> the page she wants, and so wants me to split the file into 180 separate
> files, which somehow is going to be easier to look at. Honestly, she probably
> still won't ever actually look at it, but that's her requirement.
Since you’ve already got the chapter content split into separate \input files
...
At the Unix level, use the following script to run Context 180 times specifying
a different output file each time:
#! /bin/bash
for i in {1..180}
do
context \
--arguments="ChapNo=$i" test.tex \
--result="chapter_$i.pdf”
done
And at the Context level, test.tex is simply:
\starttext
\input chapter\env{ChapNo}
\stoptext
Regards,
—
Bruce Horrocks
Hampshire, UK
___
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: How to tell a single *.tex file to produce separate PDFs?
> On 20 Sep 2024, at 03:57, Joel via ntg-context wrote:
>
> I have a document that's quite long. It uses a recurse function, a bit like
> this:
>
> \starttext
>
> \dostepwiserecurse{1}{180}{1}{%
>
>\input chapter\recurselevel
>
> }
>
> \stoptext
>
> That produces 180 chapters of content.
>
> Anyway, my boss is upset she has to use a table of contents to navigate to
> the page she wants, and so wants me to split the file into 180 separate
> files, which somehow is going to be easier to look at. Honestly, she probably
> still won't ever actually look at it, but that's her requirement.
Since you’ve already got the chapter content split into separate \input files
...
At the Unix level, use the following script to run Context 180 times specifying
a different output file each time:
#! /bin/bash
for i in {1..180}
do
context \
--arguments="ChapNo=$i" test.tex \
--result="chapter_$i.pdf”
done
And at the Context level, test.tex is simply:
\starttext
\input chapter\env{ChapNo}
\stoptext
Regards,
—
Bruce Horrocks
Hampshire, UK
___
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: How to tell a single *.tex file to produce separate PDFs?
On Fri, Sep 20, 2024 at 02:57 (+), Joel via ntg-context wrote:
> I have a document that's quite long. It uses a recurse function, a bit like
> this:
> \starttext
> \dostepwiserecurse{1}{180}{1}{%
> \input chapter\recurselevel
> }
> \stoptext
> That produces 180 chapters of content.
> Anyway, my boss is upset she has to use a table of contents to navigate to
> the page she wants, and so wants me to split the file into 180 separate
> files, which somehow is going to be easier to look at. Honestly, she probably
> still won't ever actually look at it, but that's her requirement.
> The problem is, I've been splitting the file by using Print --> PDF and
> choosing a custom print range, and then saving it. If I ned to repeat that
> 180 times, it not only will have errors, but probably take 5-10 hours.
> Is there something I can put, like \breakpdf or something that will tell it
> to start a new PDF file? They can be named something like file1.pdf,
> file2.pdf, etc.
> \starttext
> \dostepwiserecurse{1}{136}{1}{%
> \input chapter\recurselevel
> \breakpdf
> }
> \stoptext
> The perhaps "obvious" answer is just make 180 *.tex files, but since the
> minimal example above is like 0.01% of the complexity of the real file, that
> isn't so easy...
Joel,
others have suggested mutool and pdftk, which could be half the solution
for you. (I use pdftk for things like this, but I assume mutool is just as
good. Either are far less tedious than printing to file.)
If the information of the chapter boundaries is available in the log file,
a judicious use of grep and a few lines of shell script code might do the
trick. Alternatively, you might be able to use a tool like pdfgrep to find
the page numbers from the PDF file, and then use a few lines of shell code.
If you are a Linux or Mac user, this should be "easy enough". I don't do
windows, but now that there is (as I understand it) a bash shell available,
you might also be able to use grep and/or pdfgrep there as well.
If the log file isn't currently sufficiently helpful, could you add
something to your "start a new chapter" command to write a comment into the
log file giving you exactly the information you need?
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: How to tell a single *.tex file to produce separate PDFs?
Denis Maier via ntg-context schrieb am 20.09.2024 um 15:05: -Ursprüngliche Nachricht- Von: Wolfgang Schuster Gesendet: Freitag, 20. September 2024 12:26 An: mailing list for ConTeXt users ; Joel via ntg-context Betreff: [NTG-context] Re: How to tell a single *.tex file to produce separate PDFs? You can use the pdf script file but it's slower than mutool or pdftk. mtxrun --script pdf --split file.pdf Where will this split the pdf? At certain headers? This splits the pdf into single pages and there are no options. 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: How to tell a single *.tex file to produce separate PDFs?
On 9/20/24 04:57, Joel via ntg-context wrote:
> [...]
> The perhaps "obvious" answer is just make 180 *.tex files, but since
> the minimal example above is like 0.01% of the complexity of the real
> file, that isn't so easy...
Hi Joel,
I tried to recreate a document with chapters that contain a different
number of pages each:
\setuppagenumbering[alternative=doublesided]
\setuphead[chapter][reference=ch\the\numexpr\namedheadnumber{chapter}+1]
\starttext
\dorecurse{180}{%
\startchapter[title={Chapter \namedheadnumber{chapter}}]
\dorecurse{\randomnumber{10}{50}}
{\input zapf\par}
\stopchapter}
\stoptext
The key above is setting a reference for each chapter, so that they may
be retrieved later automatically.
Then you should have the pages for any chapter from its reference with
the following command:
context --pages=ch100 main-file.tex
But I must confess, I cannot get this working. I don’t know what I miss.
If you are on Unix, generating a bash loop would be similar to (once
your main PDF document has been generated):
for i in {1..180}; do mutool merge -o chapter-$i.pdf main-file\
"$(context --pages=ch$i main-file)"
But for that, you need to know first how "--pages=[reference]" may work.
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] Re: How to tell a single *.tex file to produce separate PDFs?
> -Ursprüngliche Nachricht- > Von: Wolfgang Schuster > Gesendet: Freitag, 20. September 2024 12:26 > An: mailing list for ConTeXt users ; Joel via ntg-context > cont...@ntg.nl> > Betreff: [NTG-context] Re: How to tell a single *.tex file to produce separate > PDFs? > > You can use the pdf script file but it's slower than mutool or pdftk. > > mtxrun --script pdf --split file.pdf > Where will this split the pdf? At certain headers? ___ 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: How to tell a single *.tex file to produce separate PDFs?
Joel via ntg-context schrieb am 20.09.2024 um 04:57:
I have a document that's quite long. It uses a recurse function, a bit
like this:
\starttext
\dostepwiserecurse{1}{180}{1}{%
\input chapter\recurselevel
}
\stoptext
That produces 180 chapters of content.
Anyway, my boss is upset she has to use a table of contents to navigate
to the page she wants, and so wants me to split the file into 180
separate files, which somehow is going to be easier to look at.
Honestly, she probably still won't ever actually look at it, but that's
her requirement.
The problem is, I've been splitting the file by using Print --> PDF and
choosing a custom print range, and then saving it. If I ned to repeat
that 180 times, it not only will have errors, but probably take 5-10 hours.
Is there something I can put, like \breakpdf or something that will tell
it to start a new PDF file? They can be named something like file1.pdf,
file2.pdf, etc.
\starttext
\dostepwiserecurse{1}{136}{1}{%
\input chapter\recurselevel
\breakpdf
}
\stoptext
The perhaps "obvious" answer is just make 180 *.tex files, but since
the minimal example above is like 0.01% of the complexity of the real
file, that isn't so easy...
You can use the pdf script file but it's slower than mutool or pdftk.
mtxrun --script pdf --split file.pdf
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: How to tell a single *.tex file to produce separate PDFs?
On 20/09/2024 10:33, denisma...@mailbox.org wrote: indeed:> I was going to suggest pdftk which is similar to mutools. indeed: pdftk document.pdf burst will generate pg_.pdf individual pdf pg_0001,pdf pg_0002,pdf pg_0003,pdf pg_0004,pdf ... ___ 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: How to tell a single *.tex file to produce separate PDFs?
I was going to suggest pdftk which is similar to mutools. You can get boundaries from a the log file and then split the file using these tools. (Search the mailing list: I think that's also something ConTeXt might be able to do natively, but I'm not sure.) Then, you might also consider using a product-component based solution. You'll then be able to process each file indivdually while still having a main file around. The page numbers in the individual file will be incorrect, i.e. always start at 1, but for having a quick look that still might be nice. (Hans or Wolfgang probably know if there is a way to get correct page numbers when using components...) Best, Denis > -Ursprüngliche Nachricht- > Von: vm via ntg-context > Gesendet: Freitag, 20. September 2024 10:23 > An: ntg-context@ntg.nl > Cc: vm > Betreff: [NTG-context] Re: How to tell a single *.tex file to produce separate > PDFs? > > > > On 20/09/2024 04:57, Joel via ntg-context wrote: > > > > Anyway, my boss is upset she has to use a table of contents to > > navigate to the page she wants, and so wants me to split the file into > > 180 separate files, which somehow is going to be easier to look at. > > Honestly, she probably still won't ever actually look at it, but > > that's her requirement. > > > what is the difference between scrolling through your single page files folder > and scrolling through a single pdf? > > How about too search in the pdf? > > > with mutools you can take a pdf aprt into individual pages. > > > $ mutool --help > usage: mutool [options] > clean -- rewrite pdf file > convert -- convert document > create -- create pdf document > draw-- convert document > trace -- trace device calls > extract -- extract font and image resources > info-- show information about pdf resources > merge -- merge pages from multiple pdf sources into a new pdf > pages -- show information about pdf pages > poster -- split large page into many tiles > sign-- manipulate PDF digital signatures > run -- run javascript > show-- show internal pdf objects > > > __ > _ > 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: How to tell a single *.tex file to produce separate PDFs?
On 20/09/2024 04:57, Joel via ntg-context wrote: Anyway, my boss is upset she has to use a table of contents to navigate to the page she wants, and so wants me to split the file into 180 separate files, which somehow is going to be easier to look at. Honestly, she probably still won't ever actually look at it, but that's her requirement. what is the difference between scrolling through your single page files folder and scrolling through a single pdf? How about too search in the pdf? with mutools you can take a pdf aprt into individual pages. $ mutool --help usage: mutool [options] clean -- rewrite pdf file convert -- convert document create -- create pdf document draw-- convert document trace -- trace device calls extract -- extract font and image resources info-- show information about pdf resources merge -- merge pages from multiple pdf sources into a new pdf pages -- show information about pdf pages poster -- split large page into many tiles sign-- manipulate PDF digital signatures run -- run javascript show-- show internal pdf objects ___ 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] How to tell a single *.tex file to produce separate PDFs?
I have a document that's quite long. It uses a recurse function, a bit like
this:
\starttext
\dostepwiserecurse{1}{180}{1}{%
\input chapter\recurselevel
}
\stoptext
That produces 180 chapters of content.
Anyway, my boss is upset she has to use a table of contents to navigate to the
page she wants, and so wants me to split the file into 180 separate files,
which somehow is going to be easier to look at. Honestly, she probably still
won't ever actually look at it, but that's her requirement.
The problem is, I've been splitting the file by using Print --> PDF and
choosing a custom print range, and then saving it. If I ned to repeat that 180
times, it not only will have errors, but probably take 5-10 hours.
Is there something I can put, like \breakpdf or something that will tell it to
start a new PDF file? They can be named something like file1.pdf, file2.pdf,
etc.
\starttext
\dostepwiserecurse{1}{136}{1}{%
\input chapter\recurselevel
\breakpdf
}
\stoptext
The perhaps "obvious" answer is just make 180 *.tex files, but since the
minimal example above is like 0.01% of the complexity of the real file, that
isn't so easy...
--Joel
___
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
Hi Shiv, -- Original Message -- From "Shiv Shankar Dayal" mailto:shivshankar.da...@gmail.com>> To "mailing list for ConTeXt users" mailto:ntg-context@ntg.nl>> Date 1/24/2024 9:44:09 AM Subject [NTG-context] Re: Using plain TeX commands in ConTeXt ** Caution: EXTERNAL Sender ** Yes. On Wed, Jan 24, 2024 at 10:08 PM luigi scarso mailto:luigi.sca...@gmail.com>> wrote: On Wed, 24 Jan 2024 at 16:55, Shiv Shankar Dayal mailto:shivshankar.da...@gmail.com>> wrote: Thanks for correcting me, Wolfgang. I meant only TeX commands not plan TeX macros. TeX primitives ? Apologies if you are already aware: There are 21 ConTeXt manuals entitled "low-level TeX" here: https://wiki.contextgarden.net/Documentation These might be a good place to begin exploration of interactions between TeX primitives and ConTeXt. Best wishes -- Idris Samawi Hamid, Professor Department of Philosophy Colorado State University Fort Collins, CO 80523 ___ 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
Yes. On Wed, Jan 24, 2024 at 10:08 PM luigi scarso wrote: > > > On Wed, 24 Jan 2024 at 16:55, Shiv Shankar Dayal < > shivshankar.da...@gmail.com> wrote: > >> Thanks for correcting me, Wolfgang. I meant only TeX commands not plan >> TeX macros. >> >> > TeX primitives ? > > -- > luigi > > ___ > 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 > > ___ > -- 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
On Wed, 24 Jan 2024 at 16:55, Shiv Shankar Dayal < shivshankar.da...@gmail.com> wrote: > Thanks for correcting me, Wolfgang. I meant only TeX commands not plan TeX > macros. > > TeX primitives ? -- luigi ___ 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:52: Thanks for correcting me, Wolfgang. I meant only TeX commands not plan TeX macros. As I already wrote you can use \parindent etc. in your document but unless you know what you're doing you should keep it to a minimum to avoid conflicts with other mechanism which rely on certain settings, e.g. changing the \parindent value can result in unwanted result with paragraph indentation set with \setupindenting[...]. 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: 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: Using plain TeX commands in ConTeXt
For example: \kern, \parindent and so on. Rephrasing the question, can LuaMetaTeX/ConTeXt compile plain TeX files. If yes, how can I do that? On Wed, Jan 24, 2024 at 9:02 PM Hans Hagen wrote: > On 1/24/2024 2:55 PM, Shiv Shankar Dayal wrote: > > Dear List, > > > > Can we use plain TeX commands which are available in LuaMetaTeX in an > > arbitrary manner or are there any restrictions? > what do you mean with arbitrary plain tex commands > > - >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 > > ___ > -- 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
On 1/24/2024 2:55 PM, Shiv Shankar Dayal wrote: Dear List, Can we use plain TeX commands which are available in LuaMetaTeX in an arbitrary manner or are there any restrictions? what do you mean with arbitrary plain tex commands - 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] Using plain TeX commands in ConTeXt
Dear List, Can we use plain TeX commands which are available in LuaMetaTeX in an arbitrary manner or are there any restrictions? -- 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: LMTX: Command handling, Interface between TeX and Lua
Am Mittwoch, 13. Dezember 2023, 21:57:35 CET schrieb Bruce Horrocks:
>
> > On 13 Dec 2023, at 17:13, Gerion Entrup wrote:
> >
> > Is there a simple way to define a new command/environment and handle
> > the keyword arguments in Lua? For example defining a frontend command
> > like this:
>
> I don't have the answer to your other questions but I do have an example for
> this one.
> It's not mine - I'm fairly sure it came from this list but I can't find who
> that was any more.
>
> \startluacode
> userdata = userdata or { }
>
> function userdata.mycommand(keywords, keyvals, str)
> keyword_options = utilities.parsers.settings_to_array(keywords)
> named_values = utilities.parsers.settings_to_hash(keyvals)
>
> context('First option = ' .. keyword_options[1])
> context('\\par')
> context('Color chosen = ' .. named_values['color'])
> context('\\par')
> context('Curly braces = ' .. str)
> context('\\par')
> end
> \stopluacode
>
> \def\mycommand[#1][#2]#3{\ctxlua{
> userdata.mycommand('#1', '#2', [==[#3]==])}}
>
> \starttext
> \mycommand[top, inmargin, now][color=green, roof=gabled]{Anne of Green
> Gables?}
> \stoptext
Thank you. That helps a lot already!
Gerion
signature.asc
Description: This is a digitally signed message part.
___
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: LMTX: Command handling, Interface between TeX and Lua
> On 13 Dec 2023, at 17:13, Gerion Entrup wrote:
>
> Is there a simple way to define a new command/environment and handle
> the keyword arguments in Lua? For example defining a frontend command
> like this:
I don't have the answer to your other questions but I do have an example for
this one.
It's not mine - I'm fairly sure it came from this list but I can't find who
that was any more.
\startluacode
userdata = userdata or { }
function userdata.mycommand(keywords, keyvals, str)
keyword_options = utilities.parsers.settings_to_array(keywords)
named_values = utilities.parsers.settings_to_hash(keyvals)
context('First option = ' .. keyword_options[1])
context('\\par')
context('Color chosen = ' .. named_values['color'])
context('\\par')
context('Curly braces = ' .. str)
context('\\par')
end
\stopluacode
\def\mycommand[#1][#2]#3{\ctxlua{
userdata.mycommand('#1', '#2', [==[#3]==])}}
\starttext
\mycommand[top, inmargin, now][color=green, roof=gabled]{Anne of Green Gables?}
\stoptext
—
Bruce Horrocks
Hampshire, UK
___
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] LMTX: Command handling, Interface between TeX and Lua
Hi,
I'd like to understand more of the inner workings of LMTX.
When I understand it right, most of the code is now processed in Lua but
I was not able to find it.
For example, I tried to find out how setupitemgroup is handled (just as
an example of a more complex command). The wiki has a (kind of)
autogenerated description:
https://wiki.contextgarden.net/Command/setupitemgroup
I found the data for this (at least this is my guess) here:
tex/texmf-context/tex/context/interface/mkiv/i-itemgroup.xml
Are these xml files created by hand or somehow generated? Now, when I
use `\setupitemgroup[itemize:1][symbol=3,itemalign=middle]`: How are the
arguments handled and is this a generic process or specific to each
command?
Is there a simple way to define a new command/environment and handle
the keyword arguments in Lua? For example defining a frontend command
like this:
\startsomething[firstword={Some},secondword={Text}]
Body
\stopsomething
which I can handle in some lua code like this:
function something(firstword, secondword, body)
tex.print(firstword)
tex.print(secondword)
tex.print(body)
end
Are there any resources beside the context code itself where I can learn
that?
Gerion
signature.asc
Description: This is a digitally signed message part.
___
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: Bold TeX Gyre Pagella Math results in Math error: parameter 'subshiftdown' with id 48 in style 2 is not set
On Fri, 1 Dec 2023 15:09:32 +0100
Wolfgang Schuster wrote:
> You get the same error with Latin Modern as soon as you use a non
> predefined font size in combination with bold math.
True, thanks for pointing that out. I wasn't aware and frankly,
that's rather unexpected behaviour.
So to put it all together, this now works for me:
\definefontfamily [mainface] [rm] [TeX Gyre Pagella]
\definefontfamily [mainface] [ss] [TeX Gyre Heros]
\starttypescript [math] [default] [size]
\definebodyfont [8.5pt] [mm] [default]
\stoptypescript
\definetypeface [mainface] [mm] [math] [pagella]
\setupbodyfont [mainface, 8.5pt]
\starttext
\math{V_y}
\bold{\math{V_y}}
\stoptext
Thank you for your replies.
Marco
___
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: Bold TeX Gyre Pagella Math results in Math error: parameter 'subshiftdown' with id 48 in style 2 is not set
Marco Patzer schrieb am 30.11.2023 um 22:23:
On Thu, 30 Nov 2023 20:51:42 +0100
Wolfgang Schuster wrote:
Use the \definetypeface command to load the math font. Math fonts
always use special
settings or load additional settings which are missing when you use
\definefontfamily.
\definetypeface [mainface] [mm] [math] [pagella]
\definetypeface generates the same error message if the font size is
changed:
\definefontfamily [mainface] [rm] [TeX Gyre Pagella]
\definefontfamily [mainface] [ss] [TeX Gyre Heros]
\definetypeface [mainface] [mm] [math] [pagella]
%% 8pt works
\setupbodyfont [mainface, 8.5pt]
\starttext
\bold{\math{x_y}}
\stoptext
You get the same error with Latin Modern as soon as you use a non
predefined font size in combination with bold math.
begin example
% \starttypescript [math] [default] [size]
% \definebodyfont [8.5pt] [mm] [default]
% \stoptypescript
\setupbodyfont[8.5pt]
\starttext
\im{x_y}
\mb\im{x_y}
\stoptext
end example
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: Bold TeX Gyre Pagella Math results in Math error: parameter 'subshiftdown' with id 48 in style 2 is not set
On Thu, 30 Nov 2023 20:51:42 +0100
Wolfgang Schuster wrote:
> Use the \definetypeface command to load the math font. Math fonts
> always use special
> settings or load additional settings which are missing when you use
> \definefontfamily.
>
> \definetypeface [mainface] [mm] [math] [pagella]
\definetypeface generates the same error message if the font size is
changed:
\definefontfamily [mainface] [rm] [TeX Gyre Pagella]
\definefontfamily [mainface] [ss] [TeX Gyre Heros]
\definetypeface [mainface] [mm] [math] [pagella]
%% 8pt works
\setupbodyfont [mainface, 8.5pt]
\starttext
\bold{\math{x_y}}
\stoptext
Marco
___
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: Bold TeX Gyre Pagella Math results in Math error: parameter 'subshiftdown' with id 48 in style 2 is not set
On Thu, 30 Nov 2023 20:51:42 +0100 Wolfgang Schuster wrote: > > %% comment/remove this line and it works > > \definefontfamily [mainface] [mm] [TeX Gyre Pagella Math] > > Use the \definetypeface command to load the math font. That example was taken straight from https://wiki.contextgarden.net/Command/definefontfamily So that should better read like this: ? \definefontfamily [mainface] [rm][TeX Gyre Pagella] \definefontfamily [mainface] [ss][TeX Gyre Heros] \definetypeface [mainface] [mm] [math] [pagella] \setupbodyfont[mainface] Should I correct the wiki then? > Math fonts always use special settings or load additional settings > which are missing when you use > \definefontfamily. > > \definetypeface [mainface] [mm] [math] [pagella] That works, thanks. However, I discovered that: %% fails \definefontfamily [mainface] [mm] [TeX Gyre Pagella Math] %% works \definefontfamily [mainface] [mm] [pagella] So even with \definefontfamily it works, when “TeX Gyre Pagella Math” is changed to “pagella”. That I do not understand. Marco ___ 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: Bold TeX Gyre Pagella Math results in Math error: parameter 'subshiftdown' with id 48 in style 2 is not set
Marco Patzer schrieb am 30.11.2023 um 20:43: Hi! I have a strange issue when TeX Gyre Pagella Math is used together with bold text. MWE: \definefontfamily [mainface] [rm] [TeX Gyre Pagella] \definefontfamily [mainface] [ss] [TeX Gyre Heros] %% comment/remove this line and it works \definefontfamily [mainface] [mm] [TeX Gyre Pagella Math] Use the \definetypeface command to load the math font. Math fonts always use special settings or load additional settings which are missing when you use \definefontfamily. \definetypeface [mainface] [mm] [math] [pagella] 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] Bold TeX Gyre Pagella Math results in Math error: parameter 'subshiftdown' with id 48 in style 2 is not set
Hi!
I have a strange issue when TeX Gyre Pagella Math is used together
with bold text. MWE:
\definefontfamily [mainface] [rm] [TeX Gyre Pagella]
\definefontfamily [mainface] [ss] [TeX Gyre Heros]
%% comment/remove this line and it works
\definefontfamily [mainface] [mm] [TeX Gyre Pagella Math]
\setupbodyfont [mainface]
\definedescription [foo]
\starttext
%% works, no issues here
\math{x_y}
%% fails if TeX Gyre Pagella Math is used
\bold{\math{x_y}}
\stoptext
The error is:
tex error > tex error on line 14 in file /tmp/tex-xDj/xDj.mkvi: Math
error: parameter 'subshiftdown' with id 48 in style 2 is not set
\math_m_nop
#1->\relax \ifmmode #1\else \normalstartimath \begingroup #1\endgroup
\normalstopimath
\fi
\bold{\math{x_y}
What is the issue here?
Marco
LMTX 2023.09.04 19:15
___
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] TeX in Czech?
Hi, a friend just asked for a LaTeX book in Czech to give a PhD student for their birthday. According to https://www.cstug.cz/informace/literatura/, there are only outdated TeX books in Czech. Is that true? Looking at the CSTUG page, I wondered why our ConTeXt meeting isn’t listed in https://www.cstug.cz/informace/zpravy/ (While TUG 2023 in Bonn is listed, BachoTeX 2023 also isn’t.) Sad. Hraban ___ 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] OT: primes outside of TeX
typographical advise about using primes (foot/inch marks): https://practicaltypography.com/foot-and-inch-marks.html ___ 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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On 7/7/2023 1:09 PM, Carlos wrote: \showmakeup displays it astonishingly correctly indeed probably a side effect of the fact that injected stuff resynchronizes the character progression in the pdf file (every char start with explicit coordinates) while without showing it depends on the width array so when that one is wrong (could be a side effect of some bad metric in the font file like units, possibly reported in the log) you can get wrong positioning 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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Thu, Jul 06, 2023 at 12:57:57PM -0400, Carlos wrote:
> On Thu, Jul 06, 2023 at 09:16:58AM -0400, Carlos wrote:
> > On Wed, Jul 05, 2023 at 06:52:30PM +0200, Hans Hagen wrote:
> > > On 7/5/2023 6:38 PM, Carlos wrote:
> > > > On Wed, Jul 05, 2023 at 06:12:32PM +0200, Hans Hagen wrote:
> > > > > On 7/5/2023 5:53 PM, Carlos wrote:
> > > > > > On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote:
> > > > > > > On 7/5/2023 3:18 PM, Carlos wrote:
> > > > > > > > \showmakeup on \TeX\ shows a
> > > > > > > >
> > > > > > > > tSP:3.282
> > > > > > > > THK:-1.721
> > > > > > > > H__E
> > > > > > > > X
> > > > > > > > HK:-1.291
> > > > > > > > SP:3.282
> > > > > > >
> > > > > > > no MWE includes so clueless
> > > > > >
> > > > > > \starttypescript[mylucidaserif]
> > > > > > \definefontsynonym[LucidaBrightRegular]
> > > > > > [file:LucidaBrightRegular]
> > > > > > \definefontsynonym[LucidaBrightItalic]
> > > > > > [file:LucidaBrightItalic]
> > > > > > \definefontsynonym[LucidaBrightDemiBold]
> > > > > > [file:LucidaBrightDemiBold]
> > > > > > \definefontsynonym[LucidaBrightDemiItalic]
> > > > > > [file:LucidaBrightDemiItalic]
> > > > > > \stoptypescript
> > > > > Hm, isn't that this lucida rip off again? Maybe bad metricks then but
> > > > > I'm
> > > > > not going to look into that as the official TUG lucida opentype fonts
> > > > > perform okay.
> > > > >
> > > > > Hans
> > > >
> > > > The first sentence is irrelevant. And a guess. Bad metrics is not the
> > > > culprit
> > > >
> > > > if it were true, the same problem would be under lualatex, correct?
> > >
> > > well, who knows what (me)tricks those fonts have embedded .. are these the
> > > official TUG lucida open type fonts? if so,
> > >
> > > \setupbodyfont[lucida]
> > >
> > > should just work (btw, you also don't set up math)
> > >
> > > > But it's not there.
> > > I can't (and won't) check that as I don't have (lua)latex installed nor
> > > have
> > > those fonts. I also don't see where this \qquad is in your example.
> >
> >
> > Using the same fonts under lualatex yields \TeX\ without an issue.
> >
> > \documentclass{article}
> >
> > \usepackage{unicode-math}
> >
> > \defaultfontfeatures{Ligatures=TeX}
> >
> > \setmainfont[
> > ItalicFont=LucidaBrightItalic,
> > BoldFont=LucidaBrightDemiBold,
> > BoldItalicFont=LucidaBrightDemiItalic,
> > ]{LucidaBrightRegular}
> > %
> > \setsansfont[
> > ItalicFont=LucidaSansOblique,
> > BoldFont=LucidaSansDemiBold,
> > BoldItalicFont=LucidaSansDemiOblique,
> > ]{LucidaSansRegular}
> > %
> > \setmonofont[
> > % ItalicFont=LucidaTypewriterOblique,
> > BoldFont=LucidaTypewriterBold,
> > % BoldItalicFont=LucidaTypewriterBoldOblique,
> > ]{LucidaTypewriterRegular}
> >
> > \begin{document}
> >
> > {\rm\input{knuth}}
> >
> > \textsf{\input{knuth}}
> >
> > \end{document}
> >
> > >
> > > As for the \showmakup ... it is used extensively and afaiks there are no
> > > issues with it.
> >
> > After running lualatex the problem dissappears. Or it seems like it.
> >
>
> I take it back. It doesn't disappear. It's still there. \showmakeup
> yields the right readings but yet the kerning is off on \TeX\.
>
> With \showmakeup everything ‹seems› correct. I guess the readings
> output are correct, and also, amazingly, the horizontal kerning,
> as you aptly named it, for \TeX\
>
> Not under lualatex. Everytihng seems fine there.
>
> But I perfectly understand that there would not be any support for these
> fonts. Thanks though!
>
> (trying to send this message with an attachment as before but it wouldn't
> go through)
In other words, and please, just ignore my message.
But it seems as if \showmakeup masks the problem. Dont' get me wrong, I
find \showmakeup output as one of the best indicators out there.
But if one were to say
{\rm \qquad{\!\!\!\!\!\!\!\!\!\!\!hurt \TeX\ significantly}}
the readings are quite probably as accurate as readings can ever be, but
at the same time, \TeX\ is displayed perfectly, which shouldn't have.
It really doesn't matter how many quad quad quad quad happened to be, or
how many negative spaces happened to be included, because it never gets
it quite right unless \showmakeup is used
This is quite interesting actually.
If, for example, with \showmakeup, one were to say within the same document
\hbox to 1cm{\ss \input{knuth}}
or rather, \vbox to 1cm{\ss \input{knuth}} or whatever
\showmakeup displays it astonishingly correctly indeed
anyhow
___
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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Thu, Jul 06, 2023 at 09:16:58AM -0400, Carlos wrote:
> On Wed, Jul 05, 2023 at 06:52:30PM +0200, Hans Hagen wrote:
> > On 7/5/2023 6:38 PM, Carlos wrote:
> > > On Wed, Jul 05, 2023 at 06:12:32PM +0200, Hans Hagen wrote:
> > > > On 7/5/2023 5:53 PM, Carlos wrote:
> > > > > On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote:
> > > > > > On 7/5/2023 3:18 PM, Carlos wrote:
> > > > > > > \showmakeup on \TeX\ shows a
> > > > > > >
> > > > > > > tSP:3.282
> > > > > > > THK:-1.721
> > > > > > > H__E
> > > > > > > X
> > > > > > > HK:-1.291
> > > > > > > SP:3.282
> > > > > >
> > > > > > no MWE includes so clueless
> > > > >
> > > > > \starttypescript[mylucidaserif]
> > > > > \definefontsynonym[LucidaBrightRegular]
> > > > > [file:LucidaBrightRegular]
> > > > > \definefontsynonym[LucidaBrightItalic]
> > > > > [file:LucidaBrightItalic]
> > > > > \definefontsynonym[LucidaBrightDemiBold]
> > > > > [file:LucidaBrightDemiBold]
> > > > > \definefontsynonym[LucidaBrightDemiItalic]
> > > > > [file:LucidaBrightDemiItalic]
> > > > > \stoptypescript
> > > > Hm, isn't that this lucida rip off again? Maybe bad metricks then but
> > > > I'm
> > > > not going to look into that as the official TUG lucida opentype fonts
> > > > perform okay.
> > > >
> > > > Hans
> > >
> > > The first sentence is irrelevant. And a guess. Bad metrics is not the
> > > culprit
> > >
> > > if it were true, the same problem would be under lualatex, correct?
> >
> > well, who knows what (me)tricks those fonts have embedded .. are these the
> > official TUG lucida open type fonts? if so,
> >
> > \setupbodyfont[lucida]
> >
> > should just work (btw, you also don't set up math)
> >
> > > But it's not there.
> > I can't (and won't) check that as I don't have (lua)latex installed nor have
> > those fonts. I also don't see where this \qquad is in your example.
>
>
> Using the same fonts under lualatex yields \TeX\ without an issue.
>
> \documentclass{article}
>
> \usepackage{unicode-math}
>
> \defaultfontfeatures{Ligatures=TeX}
>
> \setmainfont[
> ItalicFont=LucidaBrightItalic,
> BoldFont=LucidaBrightDemiBold,
> BoldItalicFont=LucidaBrightDemiItalic,
> ]{LucidaBrightRegular}
> %
> \setsansfont[
> ItalicFont=LucidaSansOblique,
> BoldFont=LucidaSansDemiBold,
> BoldItalicFont=LucidaSansDemiOblique,
> ]{LucidaSansRegular}
> %
> \setmonofont[
> % ItalicFont=LucidaTypewriterOblique,
> BoldFont=LucidaTypewriterBold,
> % BoldItalicFont=LucidaTypewriterBoldOblique,
> ]{LucidaTypewriterRegular}
>
> \begin{document}
>
> {\rm\input{knuth}}
>
> \textsf{\input{knuth}}
>
> \end{document}
>
> >
> > As for the \showmakup ... it is used extensively and afaiks there are no
> > issues with it.
>
> After running lualatex the problem dissappears. Or it seems like it.
>
I take it back. It doesn't disappear. It's still there. \showmakeup
yields the right readings but yet the kerning is off on \TeX\.
With \showmakeup everything ‹seems› correct. I guess the readings
output are correct, and also, amazingly, the horizontal kerning,
as you aptly named it, for \TeX\
Not under lualatex. Everytihng seems fine there.
But I perfectly understand that there would not be any support for these
fonts. Thanks though!
(trying to send this message with an attachment as before but it wouldn't
go through)
--
We are experiencing system trouble -- do not adjust your terminal.
___
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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Wed, Jul 05, 2023 at 07:37:56PM +0200, Hans Hagen via ntg-context wrote: > On 7/5/2023 7:05 PM, Carlos wrote: > > > And I don't want to stir up anything here either, but if the convention of > > using non-official vs official fonts is the new de facto under lmtx, > > I guess my opening question is invalid by all acounts > Well, the policy wrt font is quite simple: > > (1) one can define a typescript for any font, and one is free to mess around > in these as much as possible > > (2) a proper font will normally work ok but of course there can be > exceptions > > (3) if a font behaves bad one can ask on the list but then you need to give > a mwe + output + indication where something is wrong > > (4) if you're lucky someone else has that font and can try, but keep in mind > that one cannot assume someone to spend time (it is not everyones hobby to > solve issues) > > (5) if nothing works out you need to provide an official (properly licenced > copy, which in the case of a commercial font means that you have to buy an > extra copy) > > (6) you have to keep in mind that you ask someone to spend time on something > that is not worth spending time on (in the case of lucida: the ones from tug > work fine, and we send quite some time on the math too, so we see no reason > to spend more time on it ... there is only so much you can expect for free) > > (7) you cannot claim someones time and to what extend questions get answered > also depends on the tone of the email, the way questions are formulates, etc > etc I agree with everything. Except (5). Last time I checked Oracle, Corporation, one of the greediest money hungry behemoth eavesdropping corporate shithole to ever set foot on planet earth, owned or included the Lucida family on every java runtime environment that there was. This piece of software was also involuntarily required to run quite a few of programs. Anyhow. Heck. Let's check the company's revenue: Revenue Increase US$49.95 billion (2023) Operating incomeIncrease US$13.09 billion (2023) Net income Increase US$8.503 billion (2023) Total assetsIncrease US$134.4 billion (2023) Total equityIncrease US$1.556 billion (2023) ouch. Billions, right? So no. Let's stop the pretty lawyerish talk and rethoric and enough with licenses too. When you said ‹ripoff›, I'm not going to take it personally, and I guess, and rightly so, you must have been referring to these folks above rather than an end-user of lmtx like myself. So no. The metrics are perfectly fine with the Lucida family from jre. > > that said ... if you think that you can deduce conventions from the fact > that it is impossible or hard to answer a (somewhat vague) question, some > introspection is needed ... i get the impressions that you have no clue what > the de-facto conventions are under lmtx so i'd be careful in drawing > conclusions > > also said: i do know the difference between input and font encoding and i do > know what tfm and afm files contain and i also do know how to implement > font/char handling (unless i have to guess what encoding, fonts, chars, > engine an dmacro package a user is using in which case I don't - want to - > know any of this) but when a user complain in certain ways i tend to not > listen > > (let's see what chat gpt mnakes of that in the future) > > anyway, i don't have these fonts, i have working lucida setup as do other > users, so i see no problem > > and, as your fonts work fine in lualatex, you have a way out of this > persistent font issue, > > 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 > ___ > -- As long as there are ill-defined goals, bizarre bugs, and unrealistic schedules, there will be Real Programmers willing to jump in and Solve The Problem, saving the documentation for later. ___ 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/ w
[NTG-context] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Wed, Jul 05, 2023 at 06:52:30PM +0200, Hans Hagen wrote:
> On 7/5/2023 6:38 PM, Carlos wrote:
> > On Wed, Jul 05, 2023 at 06:12:32PM +0200, Hans Hagen wrote:
> > > On 7/5/2023 5:53 PM, Carlos wrote:
> > > > On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote:
> > > > > On 7/5/2023 3:18 PM, Carlos wrote:
> > > > > > \showmakeup on \TeX\ shows a
> > > > > >
> > > > > > tSP:3.282
> > > > > > THK:-1.721
> > > > > > H__E
> > > > > > X
> > > > > > HK:-1.291
> > > > > > SP:3.282
> > > > >
> > > > > no MWE includes so clueless
> > > >
> > > > \starttypescript[mylucidaserif]
> > > > \definefontsynonym[LucidaBrightRegular]
> > > > [file:LucidaBrightRegular]
> > > > \definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic]
> > > > \definefontsynonym[LucidaBrightDemiBold]
> > > > [file:LucidaBrightDemiBold]
> > > > \definefontsynonym[LucidaBrightDemiItalic]
> > > > [file:LucidaBrightDemiItalic]
> > > > \stoptypescript
> > > Hm, isn't that this lucida rip off again? Maybe bad metricks then but I'm
> > > not going to look into that as the official TUG lucida opentype fonts
> > > perform okay.
> > >
> > > Hans
> >
> > The first sentence is irrelevant. And a guess. Bad metrics is not the
> > culprit
> >
> > if it were true, the same problem would be under lualatex, correct?
>
> well, who knows what (me)tricks those fonts have embedded .. are these the
> official TUG lucida open type fonts? if so,
>
> \setupbodyfont[lucida]
>
> should just work (btw, you also don't set up math)
>
> > But it's not there.
> I can't (and won't) check that as I don't have (lua)latex installed nor have
> those fonts. I also don't see where this \qquad is in your example.
Using the same fonts under lualatex yields \TeX\ without an issue.
\documentclass{article}
\usepackage{unicode-math}
\defaultfontfeatures{Ligatures=TeX}
\setmainfont[
ItalicFont=LucidaBrightItalic,
BoldFont=LucidaBrightDemiBold,
BoldItalicFont=LucidaBrightDemiItalic,
]{LucidaBrightRegular}
%
\setsansfont[
ItalicFont=LucidaSansOblique,
BoldFont=LucidaSansDemiBold,
BoldItalicFont=LucidaSansDemiOblique,
]{LucidaSansRegular}
%
\setmonofont[
% ItalicFont=LucidaTypewriterOblique,
BoldFont=LucidaTypewriterBold,
% BoldItalicFont=LucidaTypewriterBoldOblique,
]{LucidaTypewriterRegular}
\begin{document}
{\rm\input{knuth}}
\textsf{\input{knuth}}
\end{document}
>
> As for the \showmakup ... it is used extensively and afaiks there are no
> issues with it.
After running lualatex the problem dissappears. Or it seems like it.
>
> 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
> ___
>
--
You will lose an important disk file.
___
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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On 7/5/2023 7:05 PM, Carlos wrote: And I don't want to stir up anything here either, but if the convention of using non-official vs official fonts is the new de facto under lmtx, I guess my opening question is invalid by all acounts Well, the policy wrt font is quite simple: (1) one can define a typescript for any font, and one is free to mess around in these as much as possible (2) a proper font will normally work ok but of course there can be exceptions (3) if a font behaves bad one can ask on the list but then you need to give a mwe + output + indication where something is wrong (4) if you're lucky someone else has that font and can try, but keep in mind that one cannot assume someone to spend time (it is not everyones hobby to solve issues) (5) if nothing works out you need to provide an official (properly licenced copy, which in the case of a commercial font means that you have to buy an extra copy) (6) you have to keep in mind that you ask someone to spend time on something that is not worth spending time on (in the case of lucida: the ones from tug work fine, and we send quite some time on the math too, so we see no reason to spend more time on it ... there is only so much you can expect for free) (7) you cannot claim someones time and to what extend questions get answered also depends on the tone of the email, the way questions are formulates, etc etc that said ... if you think that you can deduce conventions from the fact that it is impossible or hard to answer a (somewhat vague) question, some introspection is needed ... i get the impressions that you have no clue what the de-facto conventions are under lmtx so i'd be careful in drawing conclusions also said: i do know the difference between input and font encoding and i do know what tfm and afm files contain and i also do know how to implement font/char handling (unless i have to guess what encoding, fonts, chars, engine an dmacro package a user is using in which case I don't - want to - know any of this) but when a user complain in certain ways i tend to not listen (let's see what chat gpt mnakes of that in the future) anyway, i don't have these fonts, i have working lucida setup as do other users, so i see no problem and, as your fonts work fine in lualatex, you have a way out of this persistent font issue, 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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Wed, Jul 05, 2023 at 06:15:41PM +0200, Alan Braslau via ntg-context wrote: > On 05/07/23 05/07/23, 17:53, Carlos wrote: > > (sorry for duplicate messages. sending out to mailing list works > > sporadically Sometimes works, other times doesn't). > > As reported, the contextgarden server was down following a disk controller > failure and had taken some time to be reconfigured with new hardware and > brought back online. > > However, the request that I read was not about duplicate messages but rather > to avoid superfluous signature additions when posting to a mailing list. > > Alan I have no clue what the heck you're talking about about the superflous or whatever signature. Much less about you read or did not read. Not related to my question. > ___ > 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 > ___ > -- [From the operation manual for the CI-300 Dot Matrix Line Printer, made in Japan]: The excellent output machine of MODEL CI-300 as extraordinary DOT MATRIX LINE PRINTER, built in two MICRO-PROCESSORs as well as EAROM, is featured by permitting wonderful co-existence such as; "high quality against low cost," "diversified functions with compact design," "flexibility in accessibleness and durability of approx. 2000,000,00 Dot/Head," "being sophisticated in mechanism but possibly agile operating under noises being extremely suppressed" etc. And as a matter of course, the final goal is just simply to help achieve "super shuttle diplomacy" between cool data, perhaps earned by HOST COMPUTER, and warm heart of human being. ___ 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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Wed, Jul 05, 2023 at 06:12:32PM +0200, Hans Hagen wrote: > On 7/5/2023 5:53 PM, Carlos wrote: > > On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote: > > > On 7/5/2023 3:18 PM, Carlos wrote: > > > > \showmakeup on \TeX\ shows a > > > > > > > > tSP:3.282 > > > > THK:-1.721 > > > > H__E > > > > X > > > > HK:-1.291 > > > > SP:3.282 > > > > > > no MWE includes so clueless > > > > \starttypescript[mylucidaserif] > >\definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular] > >\definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic] > >\definefontsynonym[LucidaBrightDemiBold] > > [file:LucidaBrightDemiBold] > >\definefontsynonym[LucidaBrightDemiItalic] [file:LucidaBrightDemiItalic] > > \stoptypescript > Hm, isn't that this lucida rip off again? Maybe bad metricks then but I'm > not going to look into that as the official TUG lucida opentype fonts > perform okay. > > Hans Coincidentally speaking, a while ago (as a matter of fact this was last week), I was reading about a heated discussion that happened a few decades ago in which you said: «i don't know the difference between input and font encoding and i don't know what tfm and afm files contain and what they are used for, and i don't know how to implement and use the right font /char handling macros etc etc; but i *do* know and listen when a user who actually uses some glyphs complains about something» And I don't want to stir up anything here either, but if the convention of using non-official vs official fonts is the new de facto under lmtx, I guess my opening question is invalid by all acounts > > > - > 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 > ___ > -- Help stamp out Mickey-Mouse computer interfaces -- Menus are for Restaurants! ___ 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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On 7/5/2023 6:38 PM, Carlos wrote: On Wed, Jul 05, 2023 at 06:12:32PM +0200, Hans Hagen wrote: On 7/5/2023 5:53 PM, Carlos wrote: On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote: On 7/5/2023 3:18 PM, Carlos wrote: \showmakeup on \TeX\ shows a tSP:3.282 THK:-1.721 H__E X HK:-1.291 SP:3.282 no MWE includes so clueless \starttypescript[mylucidaserif] \definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular] \definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic] \definefontsynonym[LucidaBrightDemiBold] [file:LucidaBrightDemiBold] \definefontsynonym[LucidaBrightDemiItalic] [file:LucidaBrightDemiItalic] \stoptypescript Hm, isn't that this lucida rip off again? Maybe bad metricks then but I'm not going to look into that as the official TUG lucida opentype fonts perform okay. Hans The first sentence is irrelevant. And a guess. Bad metrics is not the culprit if it were true, the same problem would be under lualatex, correct? well, who knows what (me)tricks those fonts have embedded .. are these the official TUG lucida open type fonts? if so, \setupbodyfont[lucida] should just work (btw, you also don't set up math) But it's not there. I can't (and won't) check that as I don't have (lua)latex installed nor have those fonts. I also don't see where this \qquad is in your example. As for the \showmakup ... it is used extensively and afaiks there are no issues with it. 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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Wed, Jul 05, 2023 at 06:12:32PM +0200, Hans Hagen wrote: > On 7/5/2023 5:53 PM, Carlos wrote: > > On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote: > > > On 7/5/2023 3:18 PM, Carlos wrote: > > > > \showmakeup on \TeX\ shows a > > > > > > > > tSP:3.282 > > > > THK:-1.721 > > > > H__E > > > > X > > > > HK:-1.291 > > > > SP:3.282 > > > > > > no MWE includes so clueless > > > > \starttypescript[mylucidaserif] > >\definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular] > >\definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic] > >\definefontsynonym[LucidaBrightDemiBold] > > [file:LucidaBrightDemiBold] > >\definefontsynonym[LucidaBrightDemiItalic] [file:LucidaBrightDemiItalic] > > \stoptypescript > Hm, isn't that this lucida rip off again? Maybe bad metricks then but I'm > not going to look into that as the official TUG lucida opentype fonts > perform okay. > > Hans The first sentence is irrelevant. And a guess. Bad metrics is not the culprit if it were true, the same problem would be under lualatex, correct? But it's not there. > > > - > 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 > ___ > -- C is quirky, flawed, and an enormous success. -- Dennis Ritchie (1941-2011), creator of the C programming language and of UNIX ___ 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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On 05/07/23 05/07/23, 17:53, Carlos wrote: (sorry for duplicate messages. sending out to mailing list works sporadically Sometimes works, other times doesn't). As reported, the contextgarden server was down following a disk controller failure and had taken some time to be reconfigured with new hardware and brought back online. However, the request that I read was not about duplicate messages but rather to avoid superfluous signature additions when posting to a mailing list. Alan ___ 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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On 7/5/2023 5:53 PM, Carlos wrote: On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote: On 7/5/2023 3:18 PM, Carlos wrote: \showmakeup on \TeX\ shows a tSP:3.282 THK:-1.721 H__E X HK:-1.291 SP:3.282 no MWE includes so clueless \starttypescript[mylucidaserif] \definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular] \definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic] \definefontsynonym[LucidaBrightDemiBold] [file:LucidaBrightDemiBold] \definefontsynonym[LucidaBrightDemiItalic] [file:LucidaBrightDemiItalic] \stoptypescript Hm, isn't that this lucida rip off again? Maybe bad metricks then but I'm not going to look into that as the official TUG lucida opentype fonts perform okay. 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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Wed, Jul 05, 2023 at 11:53:47AM -0400, Carlos wrote: > On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote: > > On 7/5/2023 3:18 PM, Carlos wrote: > > > \showmakeup on \TeX\ shows a > > > > > > tSP:3.282 > > > THK:-1.721 > > > H__E > > > X > > > HK:-1.291 > > > SP:3.282 > > > > no MWE includes so clueless > > \starttypescript[mylucidaserif] > \definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular] > \definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic] > \definefontsynonym[LucidaBrightDemiBold] [file:LucidaBrightDemiBold] > \definefontsynonym[LucidaBrightDemiItalic] [file:LucidaBrightDemiItalic] > \stoptypescript > > \starttypescript [mylucidaserif] > \setups[font:fallback:serif] > \definefontsynonym[Serif][LucidaBrightRegular] > [features=default] > \definefontsynonym[SerifItalic] [LucidaBrightItalic] > [features=default] > \definefontsynonym[SerifBold][LucidaBrightDemiBold] > [features=default] > \definefontsynonym[SerifBoldItalic] [LucidaBrightDemiItalic] > [features=default] > \stoptypescript > > \starttypescript[mylucidasans] > \definefontsynonym[LucidaSansRegular][file:LucidaSansRegular] > \definefontsynonym[LucidaSansOblique][file:LucidaSansOblique] > \definefontsynonym[LucidaSansDemiBold][file:LucidaSansDemiBold] > \stoptypescript > > \starttypescript[mylucidasans] > \setups[font:fallback:sans] > \definefontsynonym[Sans] [LucidaSansRegular] [features=default] > \definefontsynonym[LucidaSansItalic] [LucidaSansOblique] > [features=default] > \definefontsynonym[LucidaSansSansBold] [LucidaSansDemiBold] > [features=default] > \stoptypescript > > \starttypescript [mylucidaserif] > \definetypeface [mylucidaserif][rm] [serif] [mylucidaserif][default] > \definetypeface [mylucidaserif][ss] [sans] [mylucidasans][default] > \stoptypescript > > \setupbodyfont[mylucidaserif] > %\setupbodyfont[mylucidasans] > %\setupbodyfont[14pt] > > \starttext > > Thus, I came to the conclusion that the designer of a new > system must not only be the implementer and first > large||scale user; the designer should also write the first > user manual. > > The separation of any of these four components would have > hurt \TeX\ significantly. If I had not participated fully in > all these activities, literally hundreds of improvements > would never have been made, because I would never have > thought of them or perceived why they were important. > > But a system cannot be successful if it is too strongly > influenced by a single person. Once the initial design is > complete and fairly robust, the real test begins as people > with many different viewpoints undertake their own > experiments. > > \stoptext Loading only one font this time around, but it makes no difference. Also. thought of forgot to mention that the above with \starttypescript[mylucida] or \starttypescript [mylucida] yields the same results every time and here is the log system > system > ConTeXt ver: 2023.06.04 18:58 LMTX fmt: 2023.6.5 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/context-lmtx-2/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source> level 1, order 1, name '/context-lmtx-2/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname './atestinlucida-OTF-99', input './atestinlucida-OTF-99.mkiv', result './atestinlucida-OTF-99' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './atestinlucida-OTF-99.mkiv' fonts > preloading modern (math) fonts > 'fallback modern mm 12pt' is loaded fonts > preloading modern (mono) fonts > 'fallback modern tt 12pt' is loaded backend > xmp > using file '/context-lmtx-2/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1, subpage 1 close source> level 1, order 2, name './atestinlucida-OTF-99.mkiv' backend > fonts > width units in 'VXLOQV+LucidaBright' are 2048, forcing 1000 instead system > start used files system > text: atestinlucida-OTF-99 system > stop used files system > start used f
[NTG-context] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote:
> On 7/5/2023 3:18 PM, Carlos wrote:
> > \showmakeup on \TeX\ shows a
> >
> > tSP:3.282
> > THK:-1.721
> > H__E
> > X
> > HK:-1.291
> > SP:3.282
>
> no MWE includes so clueless
\starttypescript[mylucidaserif]
\definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular]
\definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic]
\definefontsynonym[LucidaBrightDemiBold] [file:LucidaBrightDemiBold]
\definefontsynonym[LucidaBrightDemiItalic] [file:LucidaBrightDemiItalic]
\stoptypescript
\starttypescript [mylucidaserif]
\setups[font:fallback:serif]
\definefontsynonym[Serif][LucidaBrightRegular]
[features=default]
\definefontsynonym[SerifItalic] [LucidaBrightItalic]
[features=default]
\definefontsynonym[SerifBold][LucidaBrightDemiBold]
[features=default]
\definefontsynonym[SerifBoldItalic] [LucidaBrightDemiItalic]
[features=default]
\stoptypescript
\starttypescript[mylucidasans]
\definefontsynonym[LucidaSansRegular][file:LucidaSansRegular]
\definefontsynonym[LucidaSansOblique][file:LucidaSansOblique]
\definefontsynonym[LucidaSansDemiBold][file:LucidaSansDemiBold]
\stoptypescript
\starttypescript[mylucidasans]
\setups[font:fallback:sans]
\definefontsynonym[Sans] [LucidaSansRegular] [features=default]
\definefontsynonym[LucidaSansItalic] [LucidaSansOblique]
[features=default]
\definefontsynonym[LucidaSansSansBold] [LucidaSansDemiBold]
[features=default]
\stoptypescript
\starttypescript [mylucidaserif]
\definetypeface [mylucidaserif][rm] [serif] [mylucidaserif][default]
\definetypeface [mylucidaserif][ss] [sans] [mylucidasans][default]
\stoptypescript
\setupbodyfont[mylucidaserif]
%\setupbodyfont[mylucidasans]
%\setupbodyfont[14pt]
\starttext
Thus, I came to the conclusion that the designer of a new
system must not only be the implementer and first
large||scale user; the designer should also write the first
user manual.
The separation of any of these four components would have
hurt \TeX\ significantly. If I had not participated fully in
all these activities, literally hundreds of improvements
would never have been made, because I would never have
thought of them or perceived why they were important.
But a system cannot be successful if it is too strongly
influenced by a single person. Once the initial design is
complete and fairly robust, the real test begins as people
with many different viewpoints undertake their own
experiments.
\stoptext
>
> > I assume that SP stands for space. Correct me if I'm wrong
> >
> > After reading some of the manuals that mention \showmakeup with and
> > without [spaces] and so forth, I couldn't find any more info related
> > to this.
> >
> > If anyone can provide me more information as to what does HK means there?
>
> horizontal kern
thanks
(sorry for duplicate messages. sending out to mailing list works
sporadically Sometimes works, other times doesn't).
>
> > Anyhow
> >
> > If I were to have, say, a control _word_ such as \TeX\, the sequence of
> > TeX kerning is thrown off. The only remedy would be to have a a \qquad
> > preceding the control sequence e.g., {\qquad
> > \TeX\ significantly} to sort of ameliorate this side-effect. But then
> > again. Spacing is off. e.g.,
>
> no MWE so a space cam come from anywhwere
>
> > The separation of any of these four components would have
> > hurt {\qquad\TeX\ significantly}. If I had not participated fully in
>
> x{\showmakeup[glue]x\qquad x}x
>
> imo \qquad is okay
>
> > But it's interesting that \showmakeup, kerning and spaces would
> > display what's to be expected. And yet, the aformentioned set of
> >
> > tSP:3.282
> > THK:-1.721
> > H__E
> > X
> > HK:-1.291
> > SP:3.282
> >
> > is accurate nevertheless. And a very nice implementation at that,
> > but one I fear can't be included on a final document either.
> >
> > With that being said, the introduction of a \qquad, in addition to
> > \showmakeup with, say, redundancy aside, whatever is preceding the \TeX\
> > alongside the file would also introduce a space where no space was ever
> > there before.
> >
> > Because of all of this, and unfortunately, \showmakeup is not quite helpful
> > here either. Although it does so displays the amount of spaces and
> > so forth, any addition of a \qquad also adds a very subtle unwanted
> > space.
>
> qquad is not that subtle: 2em
>
> > And since we're looking here, I pressume, solely for accuracy
[NTG-context] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On 7/5/2023 3:18 PM, Carlos wrote:
\showmakeup on \TeX\ shows a
tSP:3.282
THK:-1.721
H__E
X
HK:-1.291
SP:3.282
no MWE includes so clueless
> I assume that SP stands for space. Correct me if I'm wrong
After reading some of the manuals that mention \showmakeup with and
without [spaces] and so forth, I couldn't find any more info related
to this.
If anyone can provide me more information as to what does HK means there?
horizontal kern
Anyhow
If I were to have, say, a control _word_ such as \TeX\, the sequence of
TeX kerning is thrown off. The only remedy would be to have a a \qquad
preceding the control sequence e.g., {\qquad
\TeX\ significantly} to sort of ameliorate this side-effect. But then
again. Spacing is off. e.g.,
no MWE so a space cam come from anywhwere
The separation of any of these four components would have
hurt {\qquad\TeX\ significantly}. If I had not participated fully in
x{\showmakeup[glue]x\qquad x}x
imo \qquad is okay
But it's interesting that \showmakeup, kerning and spaces would
display what's to be expected. And yet, the aformentioned set of
tSP:3.282
THK:-1.721
H__E
X
HK:-1.291
SP:3.282
is accurate nevertheless. And a very nice implementation at that,
but one I fear can't be included on a final document either.
With that being said, the introduction of a \qquad, in addition to
\showmakeup with, say, redundancy aside, whatever is preceding the \TeX\
alongside the file would also introduce a space where no space was ever
there before.
Because of all of this, and unfortunately, \showmakeup is not quite helpful
here either. Although it does so displays the amount of spaces and
so forth, any addition of a \qquad also adds a very subtle unwanted
space.
qquad is not that subtle: 2em
And since we're looking here, I pressume, solely for accuracy and
perfection, we're left here with neither: zero, zip. It evaporates.
puzzled
> Dear Emily:
>I'm still confused as to what groups articles should be posted
> to. How about an example?
>-- Still Confused
>
> Dear Still:
can we omit these confusing additions in mails to the list? looks /
sounds like a 'bot' to me
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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Wed, Jul 05, 2023 at 09:32:51AM -0400, Carlos wrote:
> On Wed, Jul 05, 2023 at 09:18:35AM -0400, Carlos wrote:
> > \showmakeup on \TeX\ shows a
> >
> > tSP:3.282
> > THK:-1.721
> > H__E
> > X
> > HK:-1.291
> > SP:3.282
> >
> > I assume that SP stands for space. Correct me if I'm wrong
> >
> > After reading some of the manuals that mention \showmakeup with and
> > without [spaces] and so forth, I couldn't find any more info related
> > to this.
> >
> > If anyone can provide me more information as to what does HK means there?
> >
> > Anyhow
> >
> > If I were to have, say, a control _word_ such as \TeX\, the sequence of
> > TeX kerning is thrown off. The only remedy would be to have a a \qquad
> > preceding the control sequence e.g., {\qquad
> > \TeX\ significantly} to sort of ameliorate this side-effect. But then
> > again. Spacing is off. e.g.,
> >
> > The separation of any of these four components would have
> > hurt {\qquad\TeX\ significantly}. If I had not participated fully in
> >
> > But it's interesting that \showmakeup, kerning and spaces would
> > display what's to be expected. And yet, the aformentioned set of
> >
> > tSP:3.282
> > THK:-1.721
> > H__E
> > X
> > HK:-1.291
> > SP:3.282
> >
> > is accurate nevertheless. And a very nice implementation at that,
> > but one I fear can't be included on a final document either.
> >
> > With that being said, the introduction of a \qquad, in addition to
> > \showmakeup with, say, redundancy aside, whatever is preceding the \TeX\
> > alongside the file would also introduce a space where no space was ever
> > there before.
> >
> > Because of all of this, and unfortunately, \showmakeup is not quite helpful
> > here either. Although it does so displays the amount of spaces and
> > so forth, any addition of a \qquad also adds a very subtle unwanted
> > space.
this is the space I referred to here. Please see the attached screenshot
> >
> > And since we're looking here, I pressume, solely for accuracy and
> > perfection, we're left here with neither: zero, zip. It evaporates.
> >
> >
> ___
> 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
> ___
--
It's ten o'clock; do you know where your processes are?
___
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] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
On Wed, Jul 05, 2023 at 09:18:35AM -0400, Carlos wrote:
> \showmakeup on \TeX\ shows a
>
> tSP:3.282
> THK:-1.721
> H__E
> X
> HK:-1.291
> SP:3.282
>
> I assume that SP stands for space. Correct me if I'm wrong
>
> After reading some of the manuals that mention \showmakeup with and
> without [spaces] and so forth, I couldn't find any more info related
> to this.
>
> If anyone can provide me more information as to what does HK means there?
>
> Anyhow
>
> If I were to have, say, a control _word_ such as \TeX\, the sequence of
> TeX kerning is thrown off. The only remedy would be to have a a \qquad
> preceding the control sequence e.g., {\qquad
> \TeX\ significantly} to sort of ameliorate this side-effect. But then
> again. Spacing is off. e.g.,
>
> The separation of any of these four components would have
> hurt {\qquad\TeX\ significantly}. If I had not participated fully in
>
> But it's interesting that \showmakeup, kerning and spaces would
> display what's to be expected. And yet, the aformentioned set of
>
> tSP:3.282
> THK:-1.721
> H__E
> X
> HK:-1.291
> SP:3.282
>
> is accurate nevertheless. And a very nice implementation at that,
> but one I fear can't be included on a final document either.
>
> With that being said, the introduction of a \qquad, in addition to
> \showmakeup with, say, redundancy aside, whatever is preceding the \TeX\
> alongside the file would also introduce a space where no space was ever
> there before.
>
> Because of all of this, and unfortunately, \showmakeup is not quite helpful
> here either. Although it does so displays the amount of spaces and
> so forth, any addition of a \qquad also adds a very subtle unwanted
> space.
>
> And since we're looking here, I pressume, solely for accuracy and
> perfection, we're left here with neither: zero, zip. It evaporates.
>
>
> --
> Dear Emily:
> I'm still confused as to what groups articles should be posted
> to. How about an example?
> -- Still Confused
>
> Dear Still:
> Ok. Let's say you want to report that Gretzky has been traded from
> the Oilers to the Kings. Now right away you might think rec.sport.hockey
> would be enough. WRONG. Many more people might be interested. This is a
> big trade! Since it's a NEWS article, it belongs in the news.* hierarchy
> as well. If you are a news admin, or there is one on your machine, try
> news.admin. If not, use news.misc.
> The Oilers are probably interested in geology, so try sci.physics.
> He is a big star, so post to sci.astro, and sci.space because they are also
> interested in stars. Next, his name is Polish sounding. So post to
> soc.culture.polish. But that group doesn't exist, so cross-post to
> news.groups suggesting it should be created. With this many groups of
> interest, your article will be quite bizarre, so post to talk.bizarre as
> well. (And post to comp.std.mumps, since they hardly get any articles
> there, and a "comp" group will propagate your article further.)
> You may also find it is more fun to post the article once in each
> group. If you list all the newsgroups in the same article, some newsreaders
> will only show the article to the reader once! Don't tolerate this.
> -- Emily Postnews Answers Your Questions on Netiquette
>
> ___
> 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
> ___
>
--
As of next Tuesday, C will be flushed in favor of COBOL.
Please update your programs.
___
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] \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
\showmakeup on \TeX\ shows a
tSP:3.282
THK:-1.721
H__E
X
HK:-1.291
SP:3.282
I assume that SP stands for space. Correct me if I'm wrong
After reading some of the manuals that mention \showmakeup with and
without [spaces] and so forth, I couldn't find any more info related
to this.
If anyone can provide me more information as to what does HK means there?
Anyhow
If I were to have, say, a control _word_ such as \TeX\, the sequence of
TeX kerning is thrown off. The only remedy would be to have a a \qquad
preceding the control sequence e.g., {\qquad
\TeX\ significantly} to sort of ameliorate this side-effect. But then
again. Spacing is off. e.g.,
The separation of any of these four components would have
hurt {\qquad\TeX\ significantly}. If I had not participated fully in
But it's interesting that \showmakeup, kerning and spaces would
display what's to be expected. And yet, the aformentioned set of
tSP:3.282
THK:-1.721
H__E
X
HK:-1.291
SP:3.282
is accurate nevertheless. And a very nice implementation at that,
but one I fear can't be included on a final document either.
With that being said, the introduction of a \qquad, in addition to
\showmakeup with, say, redundancy aside, whatever is preceding the \TeX\
alongside the file would also introduce a space where no space was ever
there before.
Because of all of this, and unfortunately, \showmakeup is not quite helpful
here either. Although it does so displays the amount of spaces and
so forth, any addition of a \qquad also adds a very subtle unwanted
space.
And since we're looking here, I pressume, solely for accuracy and
perfection, we're left here with neither: zero, zip. It evaporates.
--
Dear Emily:
I'm still confused as to what groups articles should be posted
to. How about an example?
-- Still Confused
Dear Still:
Ok. Let's say you want to report that Gretzky has been traded from
the Oilers to the Kings. Now right away you might think rec.sport.hockey
would be enough. WRONG. Many more people might be interested. This is a
big trade! Since it's a NEWS article, it belongs in the news.* hierarchy
as well. If you are a news admin, or there is one on your machine, try
news.admin. If not, use news.misc.
The Oilers are probably interested in geology, so try sci.physics.
He is a big star, so post to sci.astro, and sci.space because they are also
interested in stars. Next, his name is Polish sounding. So post to
soc.culture.polish. But that group doesn't exist, so cross-post to
news.groups suggesting it should be created. With this many groups of
interest, your article will be quite bizarre, so post to talk.bizarre as
well. (And post to comp.std.mumps, since they hardly get any articles
there, and a "comp" group will propagate your article further.)
You may also find it is more fun to post the article once in each
group. If you list all the newsgroups in the same article, some newsreaders
will only show the article to the reader once! Don't tolerate this.
-- Emily Postnews Answers Your Questions on Netiquette
___
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 05:57:30PM +0200, Hans Hagen via ntg-context wrote: > On 4/11/2023 3:13 PM, Carlos via ntg-context wrote: > > > But where is actually luametatex under the standalone sources > just in the bin path thanks Hans. Didn't have the time to look at et . Looking at a small display on this system and sort of like going blind . Regarding old mkiv, I didn't have the time to delve more into it, but I think (couuld be wrong here) The script installation first-setup for that old mkiv is not as straightforward as lmtx is, and to top it off I had downloaded the modules only With the former I had to manually create the dir temxf-linux-64 whereas with lmtx installation was smooth right after that's why when I read the resolvers output I had pointed it out to Aditya that it was looking over and over for that dir to no avail (of course: the dir was never there; it was never created) Path is always a problem as you know. On gnu/linux bash init file means nothing, as most likely a profile file that supersedes it sets it up regardless of sessions and how many times logging off and rebooting , but the problem woudlnt' stop there as long as texmf is there I can probably venture out and say that even then, even then… it doesn't mean nothing while texmf is still there . what is mtxrun --script cache going to erase let alone /generate while texmf is in place? the chances are nil, nada, iteración infinita It's not going to happen. and an unknown script context.lua mtx-context.lua will certainly pop up all over again only after moving/removing texmf it'd go through or else it won't . then yes context --luatex --generate context --luatex --make or context --make p.s and all of the above over a lucida sans that was my own misconfiguration that's hilarious :) Hans. sorry but I just couldn't stop thinking about it. All over a sans font. Seriously. > > 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 > ___ > -- Blinding speed can compensate for a lot of deficiencies. -- David Nichols ___ 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 4/11/2023 3:13 PM, Carlos via ntg-context wrote: But where is actually luametatex under the standalone sources just in the bin path 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 Tue, Apr 11, 2023 at 12:20:32PM +0200, Hans Hagen via ntg-context wrote: > On 4/11/2023 12:00 PM, Carlos via ntg-context wrote: > > > and belongs to TeX Live? > > well, i suppose there is a non-empty copy in texlive but an empty one can go > indeed > > > > > 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? > as long as the five mentioned files are there (and best hand mtxrun, context > and luametatex the same so use links) ... luametatex is the engine as well > as stub runner (runs the luatex file in the same path with the same name and > suffix lua) > I was just going over path just to make sure that the TeX Live infrastructure would not return anything from /opt/texlive/2023/bin/x86_64-linux/ as it doing before thank you for the clarification but where is luametatex on the standalone sources > - > 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 > ___ > -- Stinginess with privileges is kindness in disguise. -- Guide to VAX/VMS Security, Sep. 1984 ___ 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 12:20:32PM +0200, Hans Hagen via ntg-context wrote: > On 4/11/2023 12:00 PM, Carlos via ntg-context wrote: > > > and belongs to TeX Live? > > well, i suppose there is a non-empty copy in texlive but an empty one can go > indeed > > > > > 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? > as long as the five mentioned files are there (and best hand mtxrun, context > and luametatex the same so use links) ... luametatex is the engine as well > as stub runner (runs the luatex file in the same path with the same name and > suffix lua) > thank you for the clarification. I was going over path to make sure that anything under /opt/texlive/2022/bin/x86_64-linux/ returns no binaries from there But where is actually luametatex under the standalone sources > - > 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 > ___ > -- As soon as we started programming, we found to our surprise that it wasn't as easy to get programs right as we had thought. Debugging had to be discovered. I can remember the exact instant when I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs. -- Maurice Wilkes, designer of EDSAC, on programming, 1949 ___ 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 4/11/2023 12:00 PM, Carlos via ntg-context wrote: and belongs to TeX Live? well, i suppose there is a non-empty copy in texlive but an empty one can go indeed 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? as long as the five mentioned files are there (and best hand mtxrun, context and luametatex the same so use links) ... luametatex is the engine as well as stub runner (runs the luatex file in the same path with the same name and suffix lua) - 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 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)
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] /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 1:58 AM, Carlos via ntg-context wrote: I'm just following some of the standalone installation instructions as per the wiki alongside a TeX Live installation, but there are a few things that don't add up or I can't seem to add them up :). first, while I was trying to mtxrun --generate it returned /usr/bin/env texlua no such file or directory So I thought heck, perhaps by creating a symbolic link we'll call it a day, but that wasn't enough, nope. That # line will go away or change because per 2023 we assume that the script is run by luametatex and we're in a sort of transition This is is circa 21st century ladies and gentlemen! And tex survived more that 4 decades so ... it operates in an eco system (tds, installations) ... todays fashion is not yesterdays and tomorrows so I thought, alright, since there seems ot be a a problem with texlua, let's also add it to path somehow. i'm not sure what you installed but the stand alone installer installs luametatex / luatex and therefore has luametatex mtxrun -> luametatex context -> luametatex mtxrun.lua context.lua in the same path (the links are stubs, not uncommon in the tex world where they are also used to launch macro packages like latex) it can't be more portable and simple than that, is efficient and works ok unless one wants some different setup, and spend time on that So with that out of the way, we'll move on to the next step and change to a directory and try to call out mtxrun --generate again It returns: > ... But this is the catch. I don't have texmfcnf.lua anymore . Not on the TeX Live installation anyway if that might've ever materialize as a question maybe that was not copied? the fact that we need a configuration and file database is also pretty much the way a tex installation works (with allits resources) If I were to invoke an mtxrun --script cache --erase Of course and going solely by the above the part whenever it says resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/ce/context/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' wont' find it anywhere because that dir does not exist. should be there with the installer; if one just installs the 'zip' it has to come from elsewhere (like texlive, where actually most lives in texmf-dist) and one has to copy a configuration file to there But remember that earlier, adding bin to path was necessary to avoid /usr/bin/env texlua no such file or directory message But even now while trying to find plain.tex I've come to the conclusion that it needs it or else fails altogether The problem is that I don't have plain.tex though. As a matter of fact the TeX Live installation I currently have, plain tex is nowhere to be seen, heck, not even latex but only a handful set of fmtutil fmtuitl-sys mktexfmt and updmap updmap-sys and the whole remainder of kpathsea but then again this in practice would not even be needed if at all. indeed, context doesn't rely on fmtutil etc In other words, only the TeX Live infrastructure needed which shouldn't be a problem, right? But itis: a problem that is. Besides. The reason I mentioned it is only to serve reference material , but that's it. to recap, mtxrun looks for a texmfcnf.lua (which I don't have) and also for a plain.tex which I don't have either, and also presumably for a contextcnf.lua (which I have) but the script concept is not so smart, and finishes off with a final note that says warning: no lua configuration files found. No shit Sherlock! Of course it can't find it, because it doesn't exist, resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/ce/texmf/web2c' from specification 'home:texmf/web2c' But at this point and without sugar coating it, the standalone installation of context proves to be a chore more problematic than waiting to install over 5gb of TeX Live alone. hm, worked for quite a while for users; and did you try oen from https://www.pragma-ade.com/install.htm The only thing that the installation instructions got right from the start was the part about running the script with all modules. I'll probably… and eventually will try to install the whole TeX Live. But going solely by what the current TeX Live on my machine looks like, , with just the infrastcucture, while anything mtx was dropped like a hot potato really, it's a predicament... not sure what you mean here .. mtxrun was not dropped, tl 2313 just moved on to lmtx which is even less demanding (unless one starts moveing files around in the tex infrastruture and then expects stuff to keep working) -- Systems programmers are the high priests of a low cult. -- R.S. Barton dunno, don't know any of them -- Rea
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
Hi Carlos, I think that you may be installing the old ConTeXt MkIV distribution instead of the new ConTeXt LMTX. ConTeXt LMTX doesn't distribute "texlua" at all, and running "./install --modules=all" doesn't make sense with LMTX (since the installer can't install modules). From what link did you download your ConTeXt? If it started with "minimals.contextgarden.net", then that's the old ConTeXt; if it started with "lmtx.pragma-ade.com" then it's the new LMTX. The wiki page that you want is https://wiki.contextgarden.net/Installation#Unix All the other wiki pages are outdated. This is just a wild guess, so I may be very wrong here. If this doesn't work, then what do you get when you run type -ap context type -ap luatex type -ap texlua type -ap luametatex /full/path/to/texlive/2023/context --version /full/path/to/context/standalone/context --version ls -la /full/path/to/texlive/2023/context ls -la /full/path/to/context/standalone/context (I'll also add that I have both the ConTeXt and TeX Live versions of "context" installed on Linux, so it's definitely possible.) 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] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
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
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 / 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 08:51:58PM -0400, Aditya Mahajan via ntg-context wrote: > On Mon, 10 Apr 2023, Carlos via ntg-context wrote: > > > I'm just following some of the standalone installation instructions > > as per the wiki alongside a TeX Live installation, but there are a > > few things that don't add up or I can't seem to add them up :). > > > > first, while I was trying to mtxrun --generate it returned > > > > /usr/bin/env texlua no such file or directory > > > > So I thought heck, perhaps by creating a symbolic link we'll call it > > a day, but that wasn't enough, nope. > > > > This is is circa 21st century ladies and gentlemen! > > > > so I thought, alright, since there seems ot be a a problem with texlua, > > let's also add it to path somehow. > > Did you source the `setuptex` script, which sets the correct path. > > > So with that out of the way, we'll move on to the next step and change > > to a directory and try to call out mtxrun --generate again > > > > It returns: > > > > mtxrun --generate resolvers | resolving | variable 'SELFAUTOLOC' > > set to '/home/ce/context/bin' resolvers | resolving | variable > > This appears to be the wrong mtxrun binary. You should include the PATH > variable listed as part of the installation. It should point to > `/home/ce/context/texmf-linux-64/bin` or something similar. with texmfcnf.lua and the contextbinary from just hte TeX Live infrastructure there is an interesting conflict with the same ol' same ol' anyhow [2/2, 00:02/02:56] install: context [92021k] running mktexlsr ... done running mktexlsr. running mtxrun --generate ... done running mtxrun --generate. running context --luatex --generate ... done running context --luatex --generate. running updmap-sys ... done running updmap-sys. then context mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' context --luatex --generate mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' same as with context --generate mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' so it's an either or. texmfcnf.lua in place mtxrun would definitely go through but breaks context calls, while without it, a context call is just ostracized to a context --generate --luatex mtx-context | redirect luametatex -> luatex: luatex --luaonly "/opt/texlive/2023/bin/x86_64-linux/mtxrun.lua" --generate --redirected but that's not what I had in mind. mtxrun --script cache --erase mtxrun | unknown script 'cache.lua' or 'mtx-cache.lua' -- Real Programmers think better when playing Adventure or Rogue. ___ 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 08:51:58PM -0400, Aditya Mahajan via ntg-context wrote: > On Mon, 10 Apr 2023, Carlos via ntg-context wrote: > > > I'm just following some of the standalone installation instructions > > as per the wiki alongside a TeX Live installation, but there are a > > few things that don't add up or I can't seem to add them up :). > > > > first, while I was trying to mtxrun --generate it returned > > > > /usr/bin/env texlua no such file or directory > > > > So I thought heck, perhaps by creating a symbolic link we'll call it > > a day, but that wasn't enough, nope. > > > > This is is circa 21st century ladies and gentlemen! > > > > so I thought, alright, since there seems ot be a a problem with texlua, > > let's also add it to path somehow. > > Did you source the `setuptex` script, which sets the correct path. > > > So with that out of the way, we'll move on to the next step and change > > to a directory and try to call out mtxrun --generate again > > > > It returns: > > > > mtxrun --generate resolvers | resolving | variable 'SELFAUTOLOC' > > set to '/home/ce/context/bin' resolvers | resolving | variable > > This appears to be the wrong mtxrun binary. You should include the PATH > variable listed as part of the installation. It should point to > `/home/ce/context/texmf-linux-64/bin` or something similar. > > Aditya Is there any rationale not to have texmfcnf.lua alongside context.cnf and contextcnf.lua under web2c with the current standalone installation? Because on TeX Live infrastructure alone, I have my doubts that that file will be somehow generated magically. would it? Of course I could probably scrounge it off somewhere but it's also besides the point On the current installation of a standalone relying solely on what tewmf/webc holds is… well. > ___ > 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 > ___ > -- Time sharing: The use of many people by the computer. ___ 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 08:51:58PM -0400, Aditya Mahajan via ntg-context wrote:
> On Mon, 10 Apr 2023, Carlos via ntg-context wrote:
>
> > I'm just following some of the standalone installation instructions
> > as per the wiki alongside a TeX Live installation, but there are a
> > few things that don't add up or I can't seem to add them up :).
> >
> > first, while I was trying to mtxrun --generate it returned
> >
> > /usr/bin/env texlua no such file or directory
> >
> > So I thought heck, perhaps by creating a symbolic link we'll call it
> > a day, but that wasn't enough, nope.
> >
> > This is is circa 21st century ladies and gentlemen!
> >
> > so I thought, alright, since there seems ot be a a problem with texlua,
> > let's also add it to path somehow.
>
> Did you source the `setuptex` script, which sets the correct path.
Of course I sourced it and complains about plain.tex
>
> > So with that out of the way, we'll move on to the next step and change
> > to a directory and try to call out mtxrun --generate again
> >
> > It returns:
> >
> > mtxrun --generate resolvers | resolving | variable 'SELFAUTOLOC'
> > set to '/home/ce/context/bin' resolvers | resolving | variable
>
> This appears to be the wrong mtxrun binary. You should include the PATH
> variable listed as part of the installation. It should point to
> `/home/ce/context/texmf-linux-64/bin` or something similar.
binaries.
Let's start over for the simple reason that texmfcnf.lua does not exist.
Not through a TeX Live infrastructure only installation anyway.
let's run ./install --modules=all and it rightly reports that
mtx-update | updating mtxrun for linux-64: rsync -tgo --chmod=a+x
'/home/ce/context-install/tex/texmf-context/scripts/context/lua/mtxrun.lua'
'/home/ce/context-install/tex/texmf-linux-64/bin/mtxrun'
mtx-update | run, rsync -tgo --chmod=a+x
'/home/ce/context-install/tex/texmf-context/scripts/context/lua/mtxrun.lua'
'/home/ce/context-install/tex/texmf-linux-64/bin/mtxrun'
rsync: [Receiver] change_dir#3
"/home/ce/context-install/tex/texmf-linux-64/bin" failed: No such file or
directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(827)
[Receiver=3.2.7]
resolvers | tds | no 'texmf-linux-64' under tree
'/home/ce/context-install/tex'
Now. Let's add the directories, correct?
If you were to look at the following
resolvers | resolving | using configuration specification
'home:texmf/web2c;{selfautoloc:,selfautoloc:/share/texmf-local/web2c,selfautoloc:/share/texmf-dist/web2c,selfautoloc:/share/texmf/web2c,selfautoloc:/texmf-local/web2c,selfautoloc:/texmf-dist/web2c,selfautoloc:/texmf/web2c,selfautodir:,selfautodir:/share/texmf-local/web2c,selfautodir:/share/texmf-dist/web2c,selfautodir:/share/texmf/web2c,selfautodir:/texmf-local/web2c,selfautodir:/texmf-dist/web2c,selfautodir:/texmf/web2c,$SELFAUTOGRANDPARENT/texmf-local/web2c,selfautoparent:,selfautoparent:/share/texmf-local/web2c,selfautoparent:/share/texmf-dist/web2c,selfautoparent:/share/texmf/web2c,selfautoparent:/texmf-local/web2c,selfautoparent:/texmf-dist/web2c,selfautoparent:/texmf/web2c}'
resolvers | resolving |
resolvers | resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/texmf/web2c' from specification 'home:texmf/web2c'
resolvers | resolving | looking for regular 'texmfcnf.lua' on weird path
'/home/ce/context-install/tex/texmf-linux-64/bin' from specification
'selfautoloc:'
you'd notice that is looking over and over for a texmfcnf.lua
But where is my texmfcnf.lua? Would you know? :) Because I don't. The
only instance of a texmfcnf.lua dates back to a prepackaged
installation that is no longer there anyway
it points to a prepackaged texlive which I'm not using and not planning
to.
and what I have under TEXMFHOME which doesn't amount to much anyway , or what's
important for the current issue is
amiga-pl.tcx cp8bit.tcx il2-t1.tcxmktex.opt tcvn-t5.tcx
cp1250cs.tcx empty.tcxkam-cs.tcxmktexdir texmf.cnf
cp1250pl.tcx fmtutil-hdr.cnf kam-t1.tcxmktexdir.opt updmap-hdr.cfg
cp1250t1.tcx fmtutil.cnf macce-pl.tcx mktexnam updmap.cfg
cp227.tcx il1-t1.tcx macce-t1.tcx mktexnam.opt viscii-t5.tcx
cp852-cs.tcx il2-cs.tcx maz-pl.tcxmktexupd
cp852-pl.tcx il2-pl.tcx mktex.cnf natural.tcx
which as you fully know, it doesn't help
What is TeX Live infrastructure doing is the question
It's besides the point to call out ./tlmgr install context here because
mtx is no lo
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, 10 Apr 2023, Carlos via ntg-context wrote: > I'm just following some of the standalone installation instructions > as per the wiki alongside a TeX Live installation, but there are a > few things that don't add up or I can't seem to add them up :). > > first, while I was trying to mtxrun --generate it returned > > /usr/bin/env texlua no such file or directory > > So I thought heck, perhaps by creating a symbolic link we'll call it > a day, but that wasn't enough, nope. > > This is is circa 21st century ladies and gentlemen! > > so I thought, alright, since there seems ot be a a problem with texlua, > let's also add it to path somehow. Did you source the `setuptex` script, which sets the correct path. > So with that out of the way, we'll move on to the next step and change > to a directory and try to call out mtxrun --generate again > > It returns: > > mtxrun --generate resolvers | resolving | variable 'SELFAUTOLOC' > set to '/home/ce/context/bin' resolvers | resolving | variable This appears to be the wrong mtxrun binary. You should include the PATH variable listed as part of the installation. It should point to `/home/ce/context/texmf-linux-64/bin` or something similar. 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 ___
[NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
I'm just following some of the standalone installation instructions
as per the wiki alongside a TeX Live installation, but there are a
few things that don't add up or I can't seem to add them up :).
first, while I was trying to mtxrun --generate it returned
/usr/bin/env texlua no such file or directory
So I thought heck, perhaps by creating a symbolic link we'll call it
a day, but that wasn't enough, nope.
This is is circa 21st century ladies and gentlemen!
so I thought, alright, since there seems ot be a a problem with texlua,
let's also add it to path somehow.
So with that out of the way, we'll move on to the next step and change
to a directory and try to call out mtxrun --generate again
It returns:
mtxrun --generate resolvers | resolving | variable 'SELFAUTOLOC'
set to '/home/ce/context/bin' resolvers | resolving | variable
'SELFAUTODIR' set to '/home/ce/context' resolvers | resolving
| variable 'SELFAUTOPARENT' set to '/home/ce' resolvers |
resolving | variable 'TEXMFCNF' set to '' resolvers |
resolving | variable 'TEXMF' set to '' resolvers | resolving
| variable 'TEXOS' set to 'context' resolvers | resolving
| resolvers | resolving | using configuration specification
'home:texmf/web2c;{selfautoloc:,selfautoloc:/share/texmf-local/web2c,selfautoloc:/share/texmf-dist/web2c,selfautoloc:/share/texmf/web2c,selfautoloc:/texmf-local/web2c,selfautoloc:/texmf-dist/web2c,selfautoloc:/texmf/web2c,selfautodir:,selfautodir:/share/texmf-local/web2c,selfautodir:/share/texmf-dist/web2c,selfautodir:/share/texmf/web2c,selfautodir:/texmf-local/web2c,selfautodir:/texmf-dist/web2c,selfautodir:/texmf/web2c,$SELFAUTOGRANDPARENT/texmf-local/web2c,selfautoparent:,selfautoparent:/share/texmf-local/web2c,selfautoparent:/share/texmf-dist/web2c,selfautoparent:/share/texmf/web2c,selfautoparent:/texmf-local/web2c,selfautoparent:/texmf-dist/web2c,selfautoparent:/texmf/web2c}'
resolvers | resolving | resolvers | resolving | looking
for regular 'texmfcnf.lua' on given path '/home/ce/texmf/web2c'
from specification 'home:texmf/web2c' resolvers |
resolving | looking for regular 'texmfcnf.lua' on weird path
'/home/ce/context/bin' from specification 'selfautoloc:'
resolvers | resolving | looking for regular 'texmfcnf.lua'
on given path '/home/ce/context/bin/share/texmf-local/web2c'
from specification 'selfautoloc:/share/texmf-local/web2c'
resolvers | resolving | looking for regular 'texmfcnf.lua'
on given path '/home/ce/context/bin/share/texmf-dist/web2c'
from specification 'selfautoloc:/share/texmf-dist/web2c'
resolvers | resolving | looking for regular 'texmfcnf.lua'
on given path '/home/ce/context/bin/share/texmf/web2c' from
specification 'selfautoloc:/share/texmf/web2c' resolvers |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/bin/texmf-local/web2c' from specification
'selfautoloc:/texmf-local/web2c' resolvers |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/bin/texmf-dist/web2c' from specification
'selfautoloc:/texmf-dist/web2c' resolvers |
resolving | looking for regular 'texmfcnf.lua' on given
path '/home/ce/context/bin/texmf/web2c' from specification
'selfautoloc:/texmf/web2c' resolvers | resolving | looking
for regular 'texmfcnf.lua' on weird path '/home/ce/context'
from specification 'selfautodir:' resolvers |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/share/texmf-local/web2c' from specification
'selfautodir:/share/texmf-local/web2c' resolvers |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/share/texmf-dist/web2c' from specification
'selfautodir:/share/texmf-dist/web2c' resolvers |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/share/texmf/web2c' from specification
'selfautodir:/share/texmf/web2c' resolvers |
resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/context/texmf-local/web2c' from specification
'selfautodir:/texmf-local/web2c' resolvers |
resolving | looking for regular 'texmfcnf.lua' on given
path '/home/ce/context/texmf-dist/web2c' from specification
'selfautodir:/texmf-dist/web2c' resolvers | resolving | looking
for regular 'texmfcnf.lua' on given path '/home/ce/context/texmf/web2c'
f
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 Sun, Apr 02, 2023 at 10:41:53AM +0200, Hans Hagen via ntg-context wrote:
> On 4/1/2023 11:21 PM, Carlos via ntg-context wrote:
> > On Fri, Mar 31, 2023 at 10:22:49PM +0200, Hans Hagen via ntg-context wrote:
> > > On 3/31/2023 10:08 PM, Carlos via ntg-context wrote:
> > >
> > > > > 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
> > >
> > > Font loading and processing time can be mosty neglected so these 16
> > > seconds
> > > come from something else, maybe there are ways to trace file access.
> > > Another
> > > possibility is that your fonts are not cached in which case every run will
> > > involve parsing the otf / ttf and producing whatever resources needed
> > > (normally cached).
> >
> > interesting. Earlier as the output was showing
> >
> > > 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
> >
> > you asked
> >
> > > so why not use lucida math fonts?
> >
> > which is a valid question but nevertheless unsettling in that
> > lmodern-regular may nat have been called out. I fully understand the
> > inclusion of a latinmodern-math in it as a lucidamath was not previously
> > available but I ponder at the idea and involuntary implementation of
> > having lmroman along the pack. Why? If this is TeX doings, or misdoings
> > (depending how one looks at it), it clearly shows to me that TeX also
> > restricts my freedom to use whatever font I may deem necessary. Don't you
> > think? You can probably disagree with me here, or anyone from the TeX
> > community can, but the roman last was imposed deliberately upon. Someoe may
> > also give a lengthy explanation but that would be just hogwash in thee very
> > end .
>
> The fact that a file is loaded doesn't mean that it is used. In fact there
> is some fallback loading going on because explaining when nothing gets
> typeset or why \nullfont is used which results in missing chars messages is
> a waste of time.
>
> It has nothing to do with restrictions: tex will load any font you want it.
> But for instance when you turn on some tracing the macro package can load a
> font it needs. Indirectly you get what you ask for.
>
You're right about that. My mistake. Somehow monospaced had been previously
defined and I hadn't even noticed it .
I think I got it (sort of) figured for what I want it so far.
The latest stats are
mkiv lua stats > loaded fonts: 5 files: latinmodern-math.otf,
lucidabrightdemiitalic.otf, lucidabrightitalic.otf, lucidabrightregular.otf,
lucidasansregular.otf
mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 17 instances,
10 shared in backend, 3 common vectors, 7 common hashes, load time 0.413
seconds
mkiv lua stats > math tweaking time: 0.162 seconds, 24 math goodie tables
which is pretty much what I was looking for, except the math font issue. Thank
you!
While I was trying to play with it a bit, I noticed a problem with the tfb and
tfc resizing in math mode
The only mention of anything similar happened back in 2009 (but then again this
was with mkii). There may be more similar issues in the list. I just didn't
have the time to look for it.
https://www.mail-archive.com/ntg-context@ntg.nl/msg40224.html
But anyhow, the following did the trick , which I found it convenient really.
But I don't use math mode, although someone else might, it's intuitive, and
does the job
\startmidaligned
$\tfc a + \overbracket{b + c} + \underbracket{d + e} + \doublebracket{f + g} +
h$
\stopmidaligned
\startformula
\int_{\infty}
\stopformula
> I bet you didn't explicitly ask for e.g. english hyphentation patterns
> either but still got them, but tex will happily let you use polish ones
> instead.
>
> Of course the best remedy against any automatism is to just start with
> initex and implement from scratch.
>
> In the above case: just add \type {foo} and you might see another font you
> didn't ask for / set up.
>
> > > > 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.
> > >
> > > These fonts are small (only huge cjk fonts with tens of thousands of
> > > glyphs
> > > o
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 4/1/2023 11:21 PM, Carlos via ntg-context wrote:
On Fri, Mar 31, 2023 at 10:22:49PM +0200, Hans Hagen via ntg-context wrote:
On 3/31/2023 10:08 PM, Carlos via ntg-context wrote:
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
Font loading and processing time can be mosty neglected so these 16 seconds
come from something else, maybe there are ways to trace file access. Another
possibility is that your fonts are not cached in which case every run will
involve parsing the otf / ttf and producing whatever resources needed
(normally cached).
interesting. Earlier as the output was showing
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
you asked
so why not use lucida math fonts?
which is a valid question but nevertheless unsettling in that lmodern-regular
may nat have been called out. I fully understand the inclusion of a
latinmodern-math in it as a lucidamath was not previously available but I
ponder at the idea and involuntary implementation of having lmroman along the
pack. Why? If this is TeX doings, or misdoings (depending how one looks at it),
it clearly shows to me that TeX also restricts my freedom to use whatever font
I may deem necessary. Don't you think? You can probably disagree with me here,
or anyone from the TeX community can, but the roman last was imposed
deliberately upon. Someoe may also give a lengthy explanation but that would be
just hogwash in thee very end .
The fact that a file is loaded doesn't mean that it is used. In fact
there is some fallback loading going on because explaining when nothing
gets typeset or why \nullfont is used which results in missing chars
messages is a waste of time.
It has nothing to do with restrictions: tex will load any font you want
it. But for instance when you turn on some tracing the macro package can
load a font it needs. Indirectly you get what you ask for.
I bet you didn't explicitly ask for e.g. english hyphentation patterns
either but still got them, but tex will happily let you use polish ones
instead.
Of course the best remedy against any automatism is to just start with
initex and implement from scratch.
In the above case: just add \type {foo} and you might see another font
you didn't ask for / set up.
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.
These fonts are small (only huge cjk fonts with tens of thousands of glyphs
or fonts with hundreds of accumulated features might have some impact but
even then not in the final embedding stage).
Yeah. I guess.
I can also have
mkiv lua stats > loaded patterns: en::1, load time: 0.000
mkiv lua stats > loaded fonts: 3 files: lucidabrightmathsymbol.ttf,
lucidanewmathitalic.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.723 seconds
but that loading time gets back at me as the culprit sweet reminder of not
using cmr then.
i won't comment because (i verified) that lucidabrightmathsymbol.ttf and
lucidanewmathitalic.ttf are illegal copies (if created on someones
machine from the typeone its all up to that user).
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 Fri, Mar 31, 2023 at 10:22:49PM +0200, Hans Hagen via ntg-context wrote: > On 3/31/2023 10:08 PM, Carlos via ntg-context wrote: > > > > 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 > > Font loading and processing time can be mosty neglected so these 16 seconds > come from something else, maybe there are ways to trace file access. Another > possibility is that your fonts are not cached in which case every run will > involve parsing the otf / ttf and producing whatever resources needed > (normally cached). interesting. Earlier as the output was showing > 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 you asked > so why not use lucida math fonts? which is a valid question but nevertheless unsettling in that lmodern-regular may nat have been called out. I fully understand the inclusion of a latinmodern-math in it as a lucidamath was not previously available but I ponder at the idea and involuntary implementation of having lmroman along the pack. Why? If this is TeX doings, or misdoings (depending how one looks at it), it clearly shows to me that TeX also restricts my freedom to use whatever font I may deem necessary. Don't you think? You can probably disagree with me here, or anyone from the TeX community can, but the roman last was imposed deliberately upon. Someoe may also give a lengthy explanation but that would be just hogwash in thee very end . > > > 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. > > These fonts are small (only huge cjk fonts with tens of thousands of glyphs > or fonts with hundreds of accumulated features might have some impact but > even then not in the final embedding stage). Yeah. I guess. I can also have mkiv lua stats > loaded patterns: en::1, load time: 0.000 mkiv lua stats > loaded fonts: 3 files: lucidabrightmathsymbol.ttf, lucidanewmathitalic.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.723 seconds but that loading time gets back at me as the culprit sweet reminder of not using cmr then. You know the story by now Hans. I can load any font but not speed things up. Not without going through cmr. It is what it is. > > Whan talking fonts, enabling for instance expansion (hz) and protusion might > increase runtime a little. In practice, enabling for instance synctex has a > bigger imnpacts on performance than handling fonts. > 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 > ___ -- There's got to be more to life than compile-and-go. ___ 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 3/31/2023 10:08 PM, Carlos via ntg-context wrote: 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 Font loading and processing time can be mosty neglected so these 16 seconds come from something else, maybe there are ways to trace file access. Another possibility is that your fonts are not cached in which case every run will involve parsing the otf / ttf and producing whatever resources needed (normally cached). 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. These fonts are small (only huge cjk fonts with tens of thousands of glyphs or fonts with hundreds of accumulated features might have some impact but even then not in the final embedding stage). Whan talking fonts, enabling for instance expansion (hz) and protusion might increase runtime a little. In practice, enabling for instance synctex has a bigger imnpacts on performance than handling fonts. 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 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
ages. 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.» Sorry, but sorry doesn't cut it here. 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 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. 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 . 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. > > (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 > ___ -- New systems generate new problems. ___ 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 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 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 \starttypescript [sans] [lucida] [texnansi] \definefontsynonym[LucidaSansDemiBold][texnansi-lucidasansdemibold][encoding=texnansi] \definefontsynonym[LucidaSansDemiOblique][texnansi-lucidasansdemioblique][encoding=texnansi] \definefontsynonym[LucidaSansOblique][texnansi-lucidasansoblique][encoding=texnansi] \definefontsynonym[LucidaSansRegular][texnansi-lucidasansregular][encoding=texnansi] \stoptypescript \starttypescript [mono] [lucida] [texnansi] \definefontsynonym[LucidaSansTypewriterBold][texnansi-lucidatypewriterbold][encoding=texnansi] \definefontsynonym[LucidaSansTypewriterBoldOblique][texnansi-lucidayypewriterboldoblique][encoding=texnansi] \definefontsynonym[LucidaSansTypewriterOblique][texnansi-lucidatypewriteroblique][encoding=texnansi] \definefontsynonym[LucidaSansTypewriterRegular][texnansi-lucidatypewriterregular][encoding=texnansi] \stoptypescript \starttypescript [serif] [lucida] [name] \usetypescript[serif][fallback] \definefontsynonym[Serif] [LucidaBrightRegular] \definefontsynonym[SerifBold] [LucidaBrightDemi] \definefontsynonym[SerifItalic][LucidaBrightItalic] \definefontsynonym[SerifBoldItalic][LucidaBrightDemiItalic] \stoptypescript \starttypescript [sans] [lucida] [name] \usetypescript[sans][fallback] \definefontsynonym[Sans][LucidaSansRegular] \definefontsynonym[SansItalic] [LucidaSansOblique] \definefontsynonym[SansBold][LucidaSansDemiBold] \definefontsynonym[SansBoldItalic] [LucidaSansDemiOblique] \stoptypescript \starttypescript [mono] [lucida] [name] \usetypescript[mono][fallback] \definefontsynonym[Mono] [LucidaSansTypewriterRegular] \definefontsynonym[MonoItalic] [LucidaSansTypewriterOblique] \definefontsynonym[MonoBold][LucidaSansTypewriterBold] \definefontsynonym[MonoBoldItalic] [LucidaSansTypewriterBoldOblique] \stoptypescript \starttypescript [Lucida] \definetypeface[MyLucida][rm][serif][lucida][default][encoding=texnansi] \definetypeface[MyLucida][ss][sans][lucida][default][encoding=texnansi] \definetypeface[MyLucida][tt][mono][lucida][default][encoding=texnansi] \stoptypescript 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 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 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 0.306 seconds mkiv lua stats > math tweaking time: 0.055 seconds, 12 math goodie tables > > 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 > > mkiv lua stats > math tweaking time: 0.102 seconds, 12 math goodie tables > > mkiv lua stats > font embedding time: 0.004 seconds, 2 fonts > > i assume that you don't get this 16 seconds load time each run
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/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) 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 mkiv lua stats > math tweaking time: 0.102 seconds, 12 math goodie tables mkiv lua stats > font embedding time: 0.004 seconds, 2 fonts i assume that you don't get this 16 seconds load time each run 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=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaTypewriterBoldOblique.afm foundname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaTypewriterBoldOblique.afm fullname=/usr/local/texlive/2023/texmf-local/fonts/afm/bandh/lucida/LucidaTypewriterBoldOblique.a
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 Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context wrote: > Am 25.03.23 um 23:42 schrieb Carlos via ntg-context: > > > > > fonts | names | 3092 afm files checked, okay > > > > fonts | names | identifying tree font files with suffix 'AFM' > > > > fonts | names | scanning path > > > > '/home/ce/.texlive2023/texmf-config' for AFM files > > > > > fonts | names | variable 'OSFONTDIR' specifies path '/home/ce' > > > > fonts | names | variable 'OSFONTDIR' specifies path > > > > '/usr/share/fonts' > > > > fonts | names | globbing path '/home/ce/**.otf' > > There is something strange here. > Is maybe TEXMFHOME set? > > Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf > might interfere. > Look into /usr/local/texlive/2023/ > > Since it scans everything in your home directory, maybe TEXMFHOME or > OSFONTDIR is set to ~ (instead ~/texmf) there? > > Hraban I created an entirely different folder and placed the otf files right in it following Hans' advice on using directly otf rather than ttf The latter was used successfully under Void TeXLive prepackaged 2021 using a loadmapfile[texnansi-bandh-lucida.map] There was a texmfcnf.lua under the TEXMFLOCAL variable, and another one under TEXMFDIST. Got rid of the former but haven't tested it enough. Thanks for bringing it up! It compiled fine, saved some rendering presumably from missing a few otf files that I didn't have under Alpine. > ___ > 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 > ___ -- !07/11 PDP a ni deppart m'I !pleH ___ 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) > Hans, your advice for using otf fonts worked. Thanks. system > lua > compiling '/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tma' into '/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tmd' system > lua > dumping '/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tma' into '/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tmd' stripped Not how I wanted it originally as in Void Linux with texnansi encoding and a TeXLive2021 prepackaged mkiv lua stats > loaded fonts: 4 files: lucidabrightregular.otf, lucidasansregular.otf, latinmodern-math.otf, lmroman12-regular.otf mkiv lua stats > font engine: otf 3.113, afm 1.513, tfm 1.000, 12 instances, 6 shared in backend, 4 common vectors, 2 common hashes, load time 0.413 seconds mkiv lua stats > used platform: linux-64, type: unix, binary subtree: usr mkiv lua stats > used engine: luatex version: 1.13, functionality level: 7418, banner: this is luatex, version 1.13.0 (tex live 2021/voidlinux) mkiv lua stats > used hash slots: 48145 of 65536 + 20 mkiv lua stats > lua properties: engine: lua 5.3, used memory: 158 MB, ctx: 158 MB, max: unknown MB, hash chars: min(64,40), symbol mask: utf (τεχ) Or with otf under Alpine. but yes. otf rather than ttf backend > fonts > width units in 'SGVYNL+LucidaBright-Italic' are 2048, forcing 1000 instead backend > fonts > width units in 'QRVECH+LucidaBright' are 2048, forcing 1000 instead system > start used files system > text: atestinlucida-OTF system > stop used files system > start used files > > 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 > > > - > 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 > ___ -- The New Testament offers the basis for modern computer coding theory, in the form of an affirmation of the binary number system. But let your communication be Yea, yea; nay, nay: for whatsoever is more than these cometh of evil. -- Matthew 5:37 ___ 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 Sun, Mar 26, 2023 at 03:21:35PM +0200, Hans Hagen via ntg-context wrote: > On 3/26/2023 3:08 PM, Carlos via ntg-context wrote: > > On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via > > ntg-context wrote: > > > Am 25.03.23 um 23:42 schrieb Carlos via ntg-context: > > > > > > > > > fonts | names | 3092 afm files checked, okay > > > > > > fonts | names | identifying tree font files with suffix > > > > > > 'AFM' > > > > > > fonts | names | scanning path > > > > > > '/home/ce/.texlive2023/texmf-config' for AFM files > > > > > > > > > fonts | names | variable 'OSFONTDIR' specifies path > > > > > > '/home/ce' > > > > > > fonts | names | variable 'OSFONTDIR' specifies path > > > > > > '/usr/share/fonts' > > > > > > fonts | names | globbing path '/home/ce/**.otf' > > > > > > There is something strange here. > > > Is maybe TEXMFHOME set? > > > > > > Since you use a TeX live installation, some other texmfcnf.lua or > > > texmf.cnf > > > might interfere. > > > Look into /usr/local/texlive/2023/ > > > > I'll check again to make sure. But keep in mind this issue predates the > > official TeX Live installation . I've been using the distro prepackaged for > > a while. And yes. It's always been there. Sort of like, it came with the > > system :) > > > > > > Since it scans everything in your home directory, maybe TEXMFHOME or > > > OSFONTDIR is set to ~ (instead ~/texmf) there? > > > > But even if there was a conflict, it wouldn't justify to be scanninp up > > everything viciously. > > Well, if fonts can be anywhere that means checking for them anywhere. TeX > installations have some directory setup for a reason. Imagine that you set > up the installation to include that wildcard path in TEXINPUITS then every > run that whole tree would get scanned for a file you ask for and that is not > in the current directory. The whole idea behind TDS and defining paths for > specific kind of files it to limit lookups. Hans, plesae… please, You know deep inside that the above paragraph does not make any sense even after writing it convincingly. The fact that fonts can be anywhere DOES NOT mean that a program whatever that program may be is following whatever TDS sets in place or is presumably setting in place.. or much less — regardless of fonts' location, that a program out there needs to act erratically. Careless. To say the least. Bear with me in this one (I'm just a bit tired): Look at the same issue from another system perspective. I said system perspective because simply put there is so much one can do whenever you're dealing with a multiuser program such as TeX Live. Bear wiht me here: I have Void Linux on a spare system. Let's put aside for a second the inconsistencies surrounding texmfcnf.lua there. We can get back to it later And there's plenty of it taht can also be said. Do you know what is the method used to handle this problem? By folder. If I were to invoke mtxrun --script cache --erase it should behave accordingly. Or I'd expect it to act accordingly. The same with mtxrun --script font --reload Of course, it doesn't help if texmfcnf.lua sets anything else by doing otherwise. Does it sound far-fetched? Maybe. But it certainly makes more sense than looking up everything under every imaginable worktree by which presumably there can be fonts. Which 100 percent of the time there's none. But What fonts are to be found on cache and headers folders? tfm, afm, otf? come on! But then again. Even in Void Linux (a system for which concurrent files lookups seem to be working now under the right expectations) threw errors back and forth with both context.lua mtx-context.lua and base.lua unknown scripts, before eventually getting it right. (that may be a misnomer) I ought to say I got it right, I guess. Were mtxrun --generate or mtxrun --script cache --erase called out? Of course. Which led me to read about that pesky behavior here for example: https://tug.org/pipermail/tex-live/2022-August/048375.html and similarly https://tex.stackexchange.com/questions/653913/context-from-texlive-2021-says-unknown-script-context-lua-or-mtx-context-lua But the above was put aside. And there soon followed a matter-of-fact «it's not broken in TeX Live» statement. Well. If looked at from that narow angle, yes, I guess. Recall this is with a prepackaged TeXLive or the one put out by the devs. And I
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/26/2023 3:08 PM, Carlos via ntg-context wrote: On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context wrote: Am 25.03.23 um 23:42 schrieb Carlos via ntg-context: fonts | names | 3092 afm files checked, okay fonts | names | identifying tree font files with suffix 'AFM' fonts | names | scanning path '/home/ce/.texlive2023/texmf-config' for AFM files fonts | names | variable 'OSFONTDIR' specifies path '/home/ce' fonts | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts' fonts | names | globbing path '/home/ce/**.otf' There is something strange here. Is maybe TEXMFHOME set? Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf might interfere. Look into /usr/local/texlive/2023/ I'll check again to make sure. But keep in mind this issue predates the official TeX Live installation . I've been using the distro prepackaged for a while. And yes. It's always been there. Sort of like, it came with the system :) Since it scans everything in your home directory, maybe TEXMFHOME or OSFONTDIR is set to ~ (instead ~/texmf) there? But even if there was a conflict, it wouldn't justify to be scanninp up everything viciously. Well, if fonts can be anywhere that means checking for them anywhere. TeX installations have some directory setup for a reason. Imagine that you set up the installation to include that wildcard path in TEXINPUITS then every run that whole tree would get scanned for a file you ask for and that is not in the current directory. The whole idea behind TDS and defining paths for specific kind of files it to limit lookups. So far I've had to move about 7-8 folders. About 6 of them are owned by root, the rest are owned by root but symlinked to user. I would not do that, instead I'd fix ny OSFONTDIR path. Even with some directories moved you still end with plenty useless scanning. And to top it off, after doing so, it didn't stop there, heck no, it also wanted to snoop in a folder with cache and headers. To be honest. I woudlnt' know what to make of it. If it's simply looking into the permissions of the directories first, or the fact that it has a colon separated pattern. But. Then again. The other folders didn't have it. I'll let you know. What if you use the regular context installation (not texlive) and see what that does? Maybe that gives a clue. (btw, the official texlive 2023 was tested on windows, linux and osx so there must be something special at your end.) 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 Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context wrote: > Am 25.03.23 um 23:42 schrieb Carlos via ntg-context: > > > > > fonts | names | 3092 afm files checked, okay > > > > fonts | names | identifying tree font files with suffix 'AFM' > > > > fonts | names | scanning path > > > > '/home/ce/.texlive2023/texmf-config' for AFM files > > > > > fonts | names | variable 'OSFONTDIR' specifies path '/home/ce' > > > > fonts | names | variable 'OSFONTDIR' specifies path > > > > '/usr/share/fonts' > > > > fonts | names | globbing path '/home/ce/**.otf' > > There is something strange here. > Is maybe TEXMFHOME set? > > Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf > might interfere. > Look into /usr/local/texlive/2023/ I'll check again to make sure. But keep in mind this issue predates the official TeX Live installation . I've been using the distro prepackaged for a while. And yes. It's always been there. Sort of like, it came with the system :) > > Since it scans everything in your home directory, maybe TEXMFHOME or > OSFONTDIR is set to ~ (instead ~/texmf) there? But even if there was a conflict, it wouldn't justify to be scanninp up everything viciously. So far I've had to move about 7-8 folders. About 6 of them are owned by root, the rest are owned by root but symlinked to user. And to top it off, after doing so, it didn't stop there, heck no, it also wanted to snoop in a folder with cache and headers. To be honest. I woudlnt' know what to make of it. If it's simply looking into the permissions of the directories first, or the fact that it has a colon separated pattern. But. Then again. The other folders didn't have it. I'll let you know. Thank you Hraban Carlos > Hraban > ___ > 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 > ___ -- This file will self-destruct in five minutes. ___ 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
Am 25.03.23 um 23:42 schrieb Carlos via ntg-context: fonts | names | 3092 afm files checked, okay fonts | names | identifying tree font files with suffix 'AFM' fonts | names | scanning path '/home/ce/.texlive2023/texmf-config' for AFM files fonts | names | variable 'OSFONTDIR' specifies path '/home/ce' fonts | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts' fonts | names | globbing path '/home/ce/**.otf' There is something strange here. Is maybe TEXMFHOME set? Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf might interfere. Look into /usr/local/texlive/2023/ Since it scans everything in your home directory, maybe TEXMFHOME or OSFONTDIR is set to ~ (instead ~/texmf) there? Hraban ___ 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 11:09:18PM +0100, Hans Hagen via ntg-context wrote: > On 3/25/2023 10:36 PM, Carlos via ntg-context wrote: > > On Sat, Mar 25, 2023 at 09:45:25PM +0100, Hans Hagen via ntg-context wrote: > > > On 3/25/2023 8:55 PM, Carlos via ntg-context wrote: > > > > > > > > > > > ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in > > > > upvalue 'walk_tree' > > > Maybe your OSFONTDIR is pointing to empty. Does > > > > Good call. Thank you for the reminder Hans. But no. That variable was set > > long ago . Even appended it to both the bash initialization file and also > > under /etc/profile (just in case here). Alpine uses ash so shells must be > > changed > > > > > > > >mtxrun --script font --reload > > > > > fonts | names | 3092 afm files checked, okay > > fonts | names | identifying tree font files with suffix 'AFM' > > fonts | names | scanning path > > '/home/ce/.texlive2023/texmf-config' for AFM files > > fonts | names | 0 AFM files checked, okay > > fonts | names | scanning path '/home/ce/texmf' for AFM files > > fonts | names | 0 AFM files checked, okay > > fonts | names | scanning path > > '/usr/local/texlive/2023/texmf-config' for AFM files > > fonts | names | 0 AFM files checked, okay > > fonts | names | scanning path '/usr/local/texlive/2023/texmf-var' > > for AFM files > > fonts | names | 0 AFM files checked, okay > > fonts | names | scanning path > > '/usr/local/texlive/2023/texmf-local' for AFM files > > fonts | names | 24 AFM files checked, okay > > fonts | names | scanning path > > '/usr/local/texlive/2023/texmf-dist' for AFM files > > fonts | names | 3092 AFM files checked, okay > > fonts | names | 6232 tree files identified, 14 skipped, 14 > > duplicates, 6218 hash entries added, runtime 8.458 seconds > > fonts | names | identifying system font files with suffix 'otf' > > fonts | names | variable 'OSFONTDIR' specifies path '/home/ce' > > fonts | names | variable 'OSFONTDIR' specifies path > > '/usr/share/fonts' > > fonts | names | globbing path '/home/ce/**.otf' > > > > lua error : function call: > > /usr/local/texlive/2023/bin/x86_64-linuxmusl/mtxrun.lua:649: cannot open > > /home/ce/cache/headers/imaps:@gmail@imap.gmail.com/[Gmail]/.: > > Permission denied > > hm, but is home/ce/cache a path where there are fonts to be found? something Not to my knownledge. It's just that that particular folder only has root permissions and not for the user. Recursively that is. Like you said. Only not with fonts. > sets that path to be a fully recursive font dir > > can you set OSFONTDIR to '/usr/share/fonts' > it's already set echo $OSFONTDIR /usr/share/fonts > (personally i never use system fonts, i always put copies in > texmf-fonts/fonts/data becasue system fonts can change or disappear) > I'll probably do that. > > Recall that the other folders owned by root had to be moved out of the way > > > > So it seems it wasn't enough, nope. Now it wants access elsewhere > > > > bottom line: it wants root permissions or else fails flat out > > well, it's not entirely clear what generates the permission denied; i can > check for the home/ce being readable but doing that for every regular file > below that would add lots of slow checks and i'm not even sure if it would > fix it; i can try to check nested dirs but that then also obscures possible > issues You would know better than I do here. I somehow postponed this current issue thinking that a fresh TeX Live installation would resolve it once and for all. But no. > > 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/listin
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/25/2023 10:36 PM, Carlos via ntg-context wrote: On Sat, Mar 25, 2023 at 09:45:25PM +0100, Hans Hagen via ntg-context wrote: On 3/25/2023 8:55 PM, Carlos via ntg-context wrote: ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in upvalue 'walk_tree' Maybe your OSFONTDIR is pointing to empty. Does Good call. Thank you for the reminder Hans. But no. That variable was set long ago . Even appended it to both the bash initialization file and also under /etc/profile (just in case here). Alpine uses ash so shells must be changed mtxrun --script font --reload fonts | names | 3092 afm files checked, okay fonts | names | identifying tree font files with suffix 'AFM' fonts | names | scanning path '/home/ce/.texlive2023/texmf-config' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/home/ce/texmf' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-config' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-var' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-local' for AFM files fonts | names | 24 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-dist' for AFM files fonts | names | 3092 AFM files checked, okay fonts | names | 6232 tree files identified, 14 skipped, 14 duplicates, 6218 hash entries added, runtime 8.458 seconds fonts | names | identifying system font files with suffix 'otf' fonts | names | variable 'OSFONTDIR' specifies path '/home/ce' fonts | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts' fonts | names | globbing path '/home/ce/**.otf' lua error : function call: /usr/local/texlive/2023/bin/x86_64-linuxmusl/mtxrun.lua:649: cannot open /home/ce/cache/headers/imaps:@gmail@imap.gmail.com/[Gmail]/.: Permission denied hm, but is home/ce/cache a path where there are fonts to be found? something sets that path to be a fully recursive font dir can you set OSFONTDIR to '/usr/share/fonts' (personally i never use system fonts, i always put copies in texmf-fonts/fonts/data becasue system fonts can change or disappear) Recall that the other folders owned by root had to be moved out of the way So it seems it wasn't enough, nope. Now it wants access elsewhere bottom line: it wants root permissions or else fails flat out well, it's not entirely clear what generates the permission denied; i can check for the home/ce being readable but doing that for every regular file below that would add lots of slow checks and i'm not even sure if it would fix it; i can try to check nested dirs but that then also obscures possible issues 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:45:25PM +0100, Hans Hagen via ntg-context wrote: > On 3/25/2023 8:55 PM, Carlos via ntg-context wrote: > > > ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: > > in upvalue 'walk_tree' > Maybe your OSFONTDIR is pointing to empty. Does Good call. Thank you for the reminder Hans. But no. That variable was set long ago . Even appended it to both the bash initialization file and also under /etc/profile (just in case here). Alpine uses ash so shells must be changed > > mtxrun --script font --reload > fonts | names | 3092 afm files checked, okay fonts | names | identifying tree font files with suffix 'AFM' fonts | names | scanning path '/home/ce/.texlive2023/texmf-config' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/home/ce/texmf' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-config' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-var' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-local' for AFM files fonts | names | 24 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-dist' for AFM files fonts | names | 3092 AFM files checked, okay fonts | names | 6232 tree files identified, 14 skipped, 14 duplicates, 6218 hash entries added, runtime 8.458 seconds fonts | names | identifying system font files with suffix 'otf' fonts | names | variable 'OSFONTDIR' specifies path '/home/ce' fonts | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts' fonts | names | globbing path '/home/ce/**.otf' lua error : function call: /usr/local/texlive/2023/bin/x86_64-linuxmusl/mtxrun.lua:649: cannot open /home/ce/cache/headers/imaps:@gmail@imap.gmail.com/[Gmail]/.: Permission denied Recall that the other folders owned by root had to be moved out of the way So it seems it wasn't enough, nope. Now it wants access elsewhere bottom line: it wants root permissions or else fails flat out Even with sudo privileges the best it can do is: resolvers | formats | executing runner 'run luametatex format': /usr/local/texlive/2023/bin/x86_64-linuxmusl/luametatex --jobname="./atestinlucida-context-55.mkiv" --fmt=/usr/local/texlive/2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/formats/luametatex/cont-en.fmt --lua=/usr/local/texlive/2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/formats/luametatex/cont-en.lui --c:currentrun=1 --c:fulljobname="./atestinlucida-context-55.mkiv" --c:input="./atestinlucida-context-55.mkiv" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/usr/local/texlive/2023/bin/x86_64-linuxmusl" system > system > ConTeXt ver: 2023.03.10 12:15 LMTX fmt: 2023.3.25 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/usr/local/texlive/2023/texmf-dist/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source> level 1, order 1, name '/usr/local/texlive/2023/texmf-dist/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname './atestinlucida-context-55', input './atestinlucida-context-55.mkiv', result './atestinlucida-context-55' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './atestinlucida-context-55.mkiv' fonts > preloading latin modern fonts (second stage) mathematics > tweak > 'LatinModernMath-Regular', size 6, math size 3, version 'Version 1.959' found, version 'Version 1.958' expected fonts > 'fallback modern rm 12pt' is loaded open source > level 2, order 3, name '/usr/local/texlive/2023/texmf-dist/tex/context/fonts/mkiv/type-imp-lucida.mkiv' close source> level 2, order 3, name '/usr/local/texlive/2023/texmf-dist/tex/context/fonts/mkiv/type-imp-lucida.mkiv' fonts > defining > forced type 'otf' of 'LucidaBrightOT' not found fonts > defining > unable to define 'LucidaBrightOT.otf' as 'MyLucida-10pt-rm-tf
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
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/25/2023 8:55 PM, Carlos via ntg-context wrote: ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in upvalue 'walk_tree' Maybe your OSFONTDIR is pointing to empty. Does mtxrun --script font --reload work 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 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 - 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] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
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.
mtxrun --script cache --erase has also been called out to no avail
registered function call [1160]:
...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.:
Permission denied
stack traceback:
[C]: in upvalue 'func'
...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: in
function 'lfs.dir'
.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:139: in
upvalue 'glob_pattern_table'
.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in
upvalue 'glob_pattern_table'
.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in
upvalue 'glob_pattern_table'
.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in
upvalue 'glob_pattern_table'
.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in
upvalue 'glob_pattern_table'
.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:180: in
function <.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:169>
(...tail calls...)
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in
upvalue 'walk_tree'
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1190: in
local 'method'
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1152: in
local 'traverse'
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1200: in
upvalue 'analyzefiles'
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1286: in
field 'identify'
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1311: in
field 'load'
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1322: in
field 'load'
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1588: in
field 'getfilename'
...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:835: in
function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:828>
(...tail calls...)
...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:378: in
function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:366>
(...tail calls...)
...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:485: in
field 'read'
...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1377: in
function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1234>
(...tail calls...)
51
;definetypeface[MyLucida][rm][serif][lucida][default][encoding=texnansi]
52 \definetypeface[MyLucida][ss][sans][lucida][default][encoding=texnansi]
53 \definetypeface[MyLucida][tt][mono][lucida][default][encoding=texnansi]
54 \stoptypescript
55
56
57 \starttext
58
59 \usetypescriptfile[type-lucida]
60 \usetypescript[Lucida][texnansi]
61 >> \setupbodyfont[MyLucida, 10pt]
62
63 \input zapf
64
65 \input tufte
66
67
68 \stoptext
69
mtx-context | fatal error: return code: 1
it doesn't matter either whatever the typescript name goes and whether is
type-lucida from texnansi-lucida-map file as it has been previously advised to
change the name from . makes no difference.
Is LuaLaTeX behaving the same way?
Answer: no.
The permission denied message happened first with folders whose permeissions
were not owned by the user, but the root, so I moved the files out of harm's
way to another folder . Anothr folder, NOT a subfolder.
Then the problem persisted to read folders and even subfolders (directories,
subdirectories) with cache filenames and headers that follow
So let's not get to apprehensive, It's understandable that say, not reasonable,
but understandable maybe? that mtxrun or lua for that matter will stop right
before.
So the folders were moved right after. Gone out of the binaries. But what I
can't understand is why would it try to access cache folders unrelated with
anything TeX or header folders for that matter
This is perhaps more serious than I thought at first.
And Let's not blame the TeXLive pre-packaged running under Alpine Linux. To put
it in laymans' terms and If anything is clear to me, is that Alpine ir not
letting Lua running beserk on the system and its folders, owned by
whatever/whoever else, and with pesmissions set elsewhere.
It's out of the question. Or it rather be. This is all writh a fresh TeX Live
Installation.
I mentioned the problem tha
Re: [NTG-context] Sentence breaks for "English-style" (TeX default in English language) spacing regime
On 2/5/23 13:44, Hans Hagen via ntg-context wrote: > On 2/4/2023 10:10 AM, Pablo Rodriguez via ntg-context wrote: >>> https://wiki.contextgarden.net/French_spacing Not helpful alas. >> >> Would you be so kind to update the wiki? >> >> I hope it helps, > Assuming that you document it I'll add > > test\fsp. test. test > > where fsp == fixed space functuation Sorry for the delay, Hans. It is documented here: https://wiki.contextgarden.net/French_spacing#Mixing_broad_and_packed_spaces. Pablo ___ 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] Sentence breaks for "English-style" (TeX default in English language) spacing regime
On 2/4/2023 10:10 AM, Pablo Rodriguez via ntg-context wrote: On 2/3/23 19:11, Henry House via ntg-context wrote: List: What method should one use to code whitespace after a period as being sentence-ending, not midsentence, when not employing French spacing? Hi Henry, not sure I’m getting your point, since this is also a question of perspective. What may be named “French spacing” in English may be considered as “English spacing” in any other European language. But this is pure TeX (https://git.savannah.gnu.org/cgit/teximpatient.git/plain/teximpatient/book.pdf#search=null): \starttext \startTEXpage[offset=1em] PhD. Next sentence PhD\null. Next sentence \stopTEXpage \stoptext I think this may be what you want. References: https://wiki.contextgarden.net/French_spacing Not helpful alas. Would you be so kind to update the wiki? I hope it helps, Assuming that you document it I'll add test\fsp. test. test where fsp == fixed space functuation 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] Sentence breaks for "English-style" (TeX default in English language) spacing regime
On 2/3/23 19:11, Henry House via ntg-context wrote: > List: What method should one use to code whitespace after a period as > being sentence-ending, not midsentence, when not employing French > spacing? Hi Henry, not sure I’m getting your point, since this is also a question of perspective. What may be named “French spacing” in English may be considered as “English spacing” in any other European language. But this is pure TeX (https://git.savannah.gnu.org/cgit/teximpatient.git/plain/teximpatient/book.pdf#search=null): \starttext \startTEXpage[offset=1em] PhD. Next sentence PhD\null. Next sentence \stopTEXpage \stoptext I think this may be what you want. > References: > > https://wiki.contextgarden.net/French_spacing Not helpful alas. Would you be so kind to update the wiki? I hope it helps, Pablo ___ 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] Sentence breaks for "English-style" (TeX default in English language) spacing regime
List: What method should one use to code whitespace after a period as being sentence-ending, not midsentence, when not employing French spacing? For example, if one writes "... John Doe, PhD. Next sentence x y z ... ." the space in "PhD. Next". In LaTeX, we have "\@. " (code whitespace following puctuation mark as sentence-separating length) and "\ " (code space as intrasentence length) to adjust the magical behavior of ASCII spaces. By experimentation I have found that "Prof.\ Smith" works as expected in ConTeXt but "PhD\@. Next sentence ..." is a nonexistent control code. Prof. Smith % heuristic thinks that the period ends a sentence --- wrong typesetting behavior Prof.\ Smith % coded as space after abbreviation not sentence-separating space --- correct typesetting behavior under English spacing regime versus: PhD\@. Next sentence % Official LaTeX method, nonexistent control References: https://wiki.contextgarden.net/French_spacing Not helpful alas. ___ 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] embedding tex and lua code in
The attached MWE shows how to:
- embed tex code in or <script
</tt><tt>type="text/vnd.lmtx"> HTML elements to be run by ConTeXt
</tt><pre style="margin: 0em;">
- embed lua code in <script type="text/x-lua"> elements to be run by ConTeXt
- redefine xmlsetups from the HTML document itself
Massi
Il 22/03/22 17:07, mf via ntg-context ha scritto:
</pre><blockquote style="border-left: #EE solid 0.2em; margin: 0em; padding-left: 0.85em"><pre style="margin: 0em;">
I've added a <script type="text/x-lua"> in the <head> element (BTW,
"text/x-lua" is the mimetype proposed by freedesktop.org for lua scripts.
That element is managed by this code:
--
if mimetype and mimetype == "text/x-lua" then
local code = xml.text(s)
context( "\\startluacode " .. code .. " \\stopluacode" )
end
--
s is the table representing the script element.
That works, but it has a problem with one-line comments:
--
<script type="text/x-lua">
-- comment
context.setuppapersize{ "A7" }
--
The code above is considered a long comment as if it were written as
--
-- comment context.setuppapersize{ "A7" }
--
so the context.setuppapersize function call is ignored.
The workaround is:
--
--[[ comment --]]
context.setuppapersize{ "A7" }
--
A lua analogous of \xmlcontext (line-wise) would be great.
Hans prompted me to use xml.content() instead of xml.text(). The first
one preserves newlines, so short comments don't extend to the next line.
* * *
Here's another problem related to space in elements.
This code:
--
<script type="text/vnd.context">
% default setup for paragraphs
\startxmlsetups myHtml:p
\dontleavehmode\red\xmlflush{#1}\par
\stopxmlsetups
% default setup for italic inlines
\startxmlsetups myHtml:i
{\it\blue\xmlflush{#1}}% <-- problem here
\stopxmlsetups
--
adds a space after an element.
A solution could be this:
--
\startxmlsetups myHtml:i
{\it\blue\xmlflush{#1}}\stopxmlsetups
--
I prefer this one:
--
\startxmlsetups myHtml:i
{\it\blue\xmlflush{#1}}\relax
\stopxmlsetups
--
You need to end the line with a macro eating up all the trailing spaces
(newlines included).
Massi
Il 22/03/22 15:23, mf via ntg-context ha scritto:
I found the solution I was looking for. The command to run is still
context --environment=nested-xmlsetup.tex --forcexml
nested-xmlsetup.xhtml
In the element there's some tex code, which redefines the
</tt><tt>xmlsetups for <p> and <i> elements, coloring the first ones in red and
</tt><tt>the second ones in blue.
</tt><pre style="margin: 0em;">
The key command is
\xmlsetsetup{\xmldocument}{p|i}{myHtml:*}
</pre><tt>where \xmldocument instead of #1 applies the myHtml:* setups to the
</tt><tt>whole XHTML document and not only to the <script> element identified
</tt><tt>by #1.
</tt><pre style="margin: 0em;">
</pre><tt>I tried also this, to prevent redefining the setups of <html>, <head>,
</tt><tt><script> elements:
</tt><pre style="margin: 0em;">
\xmlsetsetup{\xmlfirst{\xmldocument}{body}}{p|i}{myHtml:*}
</pre><tt>but it doesn't work, since \xmldocument seems to be the actual
</tt><tt>document instead of an id pointing to its root element.
</tt><pre style="margin: 0em;">
Massi
Il 10/03/22 17:52, Hans Hagen ha scritto:
</pre><blockquote style="border-left: #EE solid 0.2em; margin: 0em; padding-left: 0.85em"><pre style="margin: 0em;">
On 3/10/2022 4:59 PM, mf via ntg-context wrote:
</pre><blockquote style="border-left: #EE solid 0.2em; margin: 0em; padding-left: 0.85em"><pre style="margin: 0em;">
Hello,
</pre><tt>I'm trying to add new templates (xmlsetups) from the XML document
</tt><tt>itself.
</tt><pre style="margin: 0em;">
See the attached MWE.
- the XML document is a simple XHTML file
</pre><tt>- in the "head" element there's a "script" element with the "type"
</tt><tt>attribute s
[NTG-context] Tex capacity exceeded...
Thanks Hans, and Rik. Perhaps I need to take a much closer look at this file to see if I have created some grouping issues. The removal of the .tuc file is a very handy tip that I hadn't thought of, and I assume it is associated with the way Hans put it, namely, 'looks like you load the same file...' Julian ___ 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] TeX capacity exceeded.... but....
On 2022-03-17 18:14, jbf via ntg-context wrote: I'd like to understand what is happening in this particular instance: While playing with a suggestion to a recent request (re \currentlistentrynumber etc.) I suddenly got a compiling error: TeX capacity exceeded, sorry [file=2000]. I returned everything to how it was before I was trying out those suggestions, but still got the error, so I began the \stopdocument routine fairly early in the document... same problem still. Then I brought the \stopdocument well forward, immediately after the standard makeup pages and the document compiled. When I removed \stopdocument, the entire document compiled as it should. So the basic question is: what can be causing the error message? This has happened to me on two occasions with this document - it occurred once before I had even begun experimenting with the \currentlistentry options, so I do not think that the problem lies there. And when it occurred that time, I again solved it with \stopdocument routine, but further into the document. And similarly, once it compiled that far and I removed it, the whole document compiled once more. If it is too complicated an explanation for an email response, maybe just point me to a document that explains the issue. Julian I cannot explain what is happening, but I can tell you what I do when I come across an unexpected failure: I delete the .tuc file (and .tua file as well if present) and try again. This is an easy thing to do before halving the source (moving \stop) and such. -- 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] TeX capacity exceeded.... but....
On 3/17/2022 11:14 PM, jbf via ntg-context wrote: I'd like to understand what is happening in this particular instance: While playing with a suggestion to a recent request (re \currentlistentrynumber etc.) I suddenly got a compiling error: TeX capacity exceeded, sorry [file=2000]. I returned everything to how it was before I was trying out those suggestions, but still got the error, so I began the \stopdocument routine fairly early in the document... same problem still. Then I brought the \stopdocument well forward, immediately after the standard makeup pages and the document compiled. When I removed \stopdocument, the entire document compiled as it should. So the basic question is: what can be causing the error message? This has happened to me on two occasions with this document - it occurred once before I had even begun experimenting with the \currentlistentry options, so I do not think that the problem lies there. And when it occurred that time, I again solved it with \stopdocument routine, but further into the document. And similarly, once it compiled that far and I removed it, the whole document compiled once more. If it is too complicated an explanation for an email response, maybe just point me to a document that explains the issue. a guess ... it looks like you load the same file so you have some nesting / grouping problem; (some file loaders keep track of being loaded but you probably load before that is done) 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] TeX capacity exceeded.... but....
I'd like to understand what is happening in this particular instance: While playing with a suggestion to a recent request (re \currentlistentrynumber etc.) I suddenly got a compiling error: TeX capacity exceeded, sorry [file=2000]. I returned everything to how it was before I was trying out those suggestions, but still got the error, so I began the \stopdocument routine fairly early in the document... same problem still. Then I brought the \stopdocument well forward, immediately after the standard makeup pages and the document compiled. When I removed \stopdocument, the entire document compiled as it should. So the basic question is: what can be causing the error message? This has happened to me on two occasions with this document - it occurred once before I had even begun experimenting with the \currentlistentry options, so I do not think that the problem lies there. And when it occurred that time, I again solved it with \stopdocument routine, but further into the document. And similarly, once it compiled that far and I removed it, the whole document compiled once more. If it is too complicated an explanation for an email response, maybe just point me to a document that explains the issue. Julian ___ 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 ___
