Re: Using texinfo for works that are not software-related
Sent: Wednesday, August 30, 2023 at 6:54 PM From: "Oleander" <7059...@protonmail.com> To: dim...@gmx.com Cc: help-texinfo@gnu.org Subject: Re: Using texinfo for works that are not software-related > As far as I know latex3 does not support exporting to html, epub, > ascii and I need those formats. I should have explained it better but > I don't need all the formatting options latex offers since I mostly > write prose with some code/quote blocks. > By "good things" I meant semantic elements, indexes, cross references. > I've explored other markup languages but I've always been on the fence > about those and I keep switching. > Markdown does not support indexes so I tend to exclude it for long > documentation. > Org Mode is great but it lacks semantic elements besides blocks. > Asciidoc: good markup syntax and support semantic elements but I read > the tooling leaves something to be desired. > Restructured text: great tooling but I don't like the syntax of some > elements. > As regards at least sys admin documentation which is not only > software-related (bureaucratic stuff) and general prose, would > you still recommend texinfo? After your elaborations, texinfo will get you there. Original Message On Aug 30, 2023, 04:52, Christopher Dimech < dim...@gmx.com> wrote: Sent: Wednesday, August 30, 2023 at 9:01 AM From: "Oleander" <7059...@protonmail.com> To: help-texinfo@gnu.org Subject: Re: Using texinfo for works that are not software-related Correction: sys admin documentation is related to software obviously. Original Message On Aug 29, 2023, 22:22, Oleander < 7059...@protonmail.com> wrote: Hello everyone! > Does texinfo suit other works that are not software-related like sys > admin documentation, lectures, long essays, fictional/non fictional > books? From what I've read in the manual so far, it is possible to > produce some of them but would you recommend it? Chapter 1 states: >> Texinfo was devised specifically for the purpose of writing software >> documentation and manuals. If you want to write a good manual for >> your program, Texinfo has many features which we hope will make your >> job easier. However, Texinfo is not intended to be a general-purpose >> formatting program. > If not, what markup do you prefer for works that are not > software-related, without missing most of the good things texinfo > provides? In its current state, I would not recommend it. Use latex3 from the Latex Project (https://www.latex-project.org/) One can use colour, images can be made floating, and everything works much better. Texinfo is still mostly based on tho old tex substrate, and does not work very well for non software documentation related things.
Re: Using texinfo for works that are not software-related
Sent: Wednesday, August 30, 2023 at 9:01 AM From: "Oleander" <7059...@protonmail.com> To: help-texinfo@gnu.org Subject: Re: Using texinfo for works that are not software-related Correction: sys admin documentation is related to software obviously. Original Message On Aug 29, 2023, 22:22, Oleander < 7059...@protonmail.com> wrote: Hello everyone! > Does texinfo suit other works that are not software-related like sys > admin documentation, lectures, long essays, fictional/non fictional > books? From what I've read in the manual so far, it is possible to > produce some of them but would you recommend it? Chapter 1 states: >> Texinfo was devised specifically for the purpose of writing software >> documentation and manuals. If you want to write a good manual for >> your program, Texinfo has many features which we hope will make your >> job easier. However, Texinfo is not intended to be a general-purpose >> formatting program. > If not, what markup do you prefer for works that are not > software-related, without missing most of the good things texinfo > provides? In its current state, I would not recommend it. Use latex3 from the Latex Project (https://www.latex-project.org/) One can use colour, images can be made floating, and everything works much better. Texinfo is still mostly based on tho old tex substrate, and does not work very well for non software documentation related things.
Using a macro makes pdfetex quits and exits with bad status
> Sent: Friday, June 25, 2021 at 5:57 PM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > > From: Christopher Dimech > > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > > Date: Thu, 24 Jun 2021 21:42:10 +0200 > > > > It would be a great improvement to have a standard on how we can test > > newer versions of texinfo without affecting the stable version we normally > > use. It makes it very difficult for me to help out as a tester. > > Your suggestion of help is appreciated, but help-texinfo is not about > that. It's about helping _users_ of Texinfo in using the _released_ > versions. Could take two or more years for a release version. Would have to find some other way of scrutinising texinfo, so as not to look as a demanding user. > > > > Why can't I have multiple versions of the program and run the ones I > > > > want? > > > > > > You can, but you should know very well what you are doing, and how the > > > different parts, in particular Texinfo and TeX, work together and what > > > each one of them expects to find where. If you don't know these > > > details, my best recommendation is not to do that, as you will be > > > facing an uphill battle. > > > > I am quite sure you have more experience to be able to tell us exactly > > how to set things up in the case of development versions. > > Actually, no. My help in testing development versions is limited to > running the extensive test suite. If Gavin wants me to test specific > aspects, he gives precise instructions and I follow them. Otherwise, > I always install the new version replacing the old one. > > I only know a little about the internals because in some distant past > I ported TeX/Web2C to a non-Posix platform, that's all. Based on that > vague memory, I can tell you that you would need to futz with > TEXINPUTS, but that's about all I can tell. > > Again, using such a dual installation is not recommended unless you > have a lot of free time and don't need to actually do something useful > with Texinfo except tinker with it. Don't have free time, but waste a lot of time tinkering. Most of my problems are not really my problems though. > > Am I the only one who gets in all this trouble, I ask ? > > Most probably, you are one of a very few. > > > > Why not simply install the development version instead the one you > > > have already? It will definitely be simpler to set up and use than > > > what you are going through. > > > > So I forget about using prefix in configure? Is that what you are saying? > > I would certainly require additional systems in case development versions > > screw my working setup. > > First, the development version is quite stable at this point: Gavin > has already released 2 pretest versions. And Texinfo is stable in > general, even in early stages of development of the next release, > because the language is fairly complete, and so changes are relatively > minor. > > And if worse comes to worst, there's always "make uninstall". > > So my best advice is simply configure and install the snapshot as if > it were a released version, yes. Would need to provide more detailed information so others can figure out where things could be located for Tex. Saying "make TEXMF=/your/texmf install-tex" is not detailed enough to make sure the texinfo installation works. Got to see the installation and setup for tex and provide information to the user. Otherwise everything becomes a mystery.
Using a macro makes pdfetex quits and exits with bad status
> Sent: Friday, June 25, 2021 at 8:54 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > I don't appreciate your comparing me with other posters to this list; it's > tiring and means I have less patience for responding to your queries. The > other posters have tried to help you and you should be grateful. > > Comments below. > > On Thu, Jun 24, 2021 at 10:05:24PM +0200, Christopher Dimech wrote: > > > > Let't try again > > > > This is what I have done > > > > 2001 cd /home/hagbard/Admir/source/texinfo > > 2002 ls > > 2003 rm configure > > 2004 ./autogen.sh > > > > 2000 cd /home/hagbard/Admir/build/texinfo > > 2001 ../../source/texinfo/configure > > 2002 make > > 2003 sudo make install > > > > Then I did > > > > sudo make TEXMF=/usr/local/share/texmf install-tex > > This looks all correct. > > > Here is the consequence > > > > sudo make TEXMF=/usr/local/share/texmf install-tex > > cd doc && make TEXMF=/usr/local/share/texmf install-tex > > make[1]: Entering directory '/home/hagbard/Admir/build/texinfo/doc' > > test -n "/usr/local/share/texmf" || (echo "TEXMF must be set." >&2; exit 1) > > /bin/bash /home/hagbard/Admir/source/texinfo/build-aux/install-sh -d > > /usr/local/share/texmf/tex/texinfo /usr/local/share/texmf/tex/generic/epsf > > /usr/bin/install -c -m 644 ../../../source/texinfo/doc/texinfo.tex > > /usr/local/share/texmf/tex/texinfo/texinfo.tex > > /usr/bin/install -c -m 644 ../../../source/texinfo/doc/texinfo-ja.tex > > /usr/local/share/texmf/tex/texinfo/texinfo-ja.tex > > /usr/bin/install -c -m 644 ../../../source/texinfo/doc/epsf.tex > > /usr/local/share/texmf/tex/generic/epsf/epsf.tex > > for f in txi-ca.tex txi-cs.tex txi-de.tex txi-en.tex txi-es.tex txi-fi.tex > > txi-fr.tex txi-hu.tex txi-is.tex txi-it.tex txi-ja.tex txi-nb.tex > > txi-nl.tex txi-nn.tex txi-pl.tex txi-pt.tex txi-ru.tex txi-sr.tex > > txi-tr.tex txi-uk.tex; do \ > > /usr/bin/install -c -m 644 ../../../source/texinfo/doc/$f > > /usr/local/share/texmf/tex/texinfo/$f; done > > make[1]: Leaving directory '/home/hagbard/Admir/build/texinfo/doc' > > > > Finally I run texi2pdf, > > > > hagbard@fuckup: > > + ~/01cuneus/tdr/06ch > > texi2pdf 06a-amcoh.texi > > /usr/local/bin/texi2dvi: texinfo.tex appears to be broken. > > This may be due to the environment variable TEX set to something > > other than (plain) tex, a corrupt texinfo.tex file, or > > to tex itself simply not working. > > This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) > > (preloaded format=etex) > > restricted \write18 enabled. > > entering extended mode > > (./txiversion.tex > > ! I can't find file `texinfo.tex'. > > l.1 \input texinfo.tex > >@bye > > (Press Enter to retry, or Control-D to exit) > > Please type another input file name: > > ! Emergency stop. > > l.1 \input texinfo.tex > >@bye > > No pages of output. > > Transcript written on txiversion.log. > > /usr/local/bin/texi2dvi: quitting. > > The first thing I would do is run > > pdfetex 06a-amcoh.texi > > and see if the same error occurs. Error Occurs hagbard@fuckup: + ~/01cuneus/tdr/06ch pdfetex 06a-amcoh.texi This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=pdfetex) restricted \write18 enabled. entering extended mode (./06a-amcoh.texi ! I can't find file `texinfo'. l.2 \input texinfo (Press Enter to retry, or Control-D to exit) Please type another input file name: q (/usr/share/texlive/texmf-dist/tex/latex/tools/q.tex File ignored > If it does, you need to investigate > TeX's search list for files. You could try running > > export TEXINPUTS=/usr/local/share/texmf:$TEXINPUTS > > and running pdfetex again. See Info node "(kpathsea)Path sources". Still a problem after running pdfetex again. hagbard@fuckup: + ~/01cuneus/tdr/06ch export TEXINPUTS=/usr/local/share/texmf:$TEXINPUTS hagbard@fuckup: + ~/01cuneus/tdr/06ch pdfetex 06a-amcoh.texi This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=pdfetex) restricted \write18 enabled. entering extended mode (./06a-amcoh.texi ! I can't find file `texinfo'. l.2 \input texinfo (Press Enter to retry, or Control-D to exit) Please
Using a macro makes pdfetex quits and exits with bad status
These are problems everybody will have. Don't you think that the fact that you concede non-familiarity with how TeX works, is even more of a minefield for the user who is going through great efforts to use it. Ultimately, its value is determined by the worth in the eyes of those who use it. Right now the biggest problem with human beings is that they think this is important, this is not important, this person is great, this person is no good, this is ok, this is not ok, this is god, this is devil. It is half a life, because people think this is not important. I will introspect the comments, but then we got to document what we learn here, in the manual or installation guide. Else all this bother will be for nothing. Only if this is important should we invest our time in it. > Sent: Friday, June 25, 2021 at 8:54 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Eli Zaretskii" , help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > I don't appreciate your comparing me with other posters to this list; it's > tiring and means I have less patience for responding to your queries. The > other posters have tried to help you and you should be grateful. > > Comments below. > > On Thu, Jun 24, 2021 at 10:05:24PM +0200, Christopher Dimech wrote: > > > > Let't try again > > > > This is what I have done > > > > 2001 cd /home/hagbard/Admir/source/texinfo > > 2002 ls > > 2003 rm configure > > 2004 ./autogen.sh > > > > 2000 cd /home/hagbard/Admir/build/texinfo > > 2001 ../../source/texinfo/configure > > 2002 make > > 2003 sudo make install > > > > Then I did > > > > sudo make TEXMF=/usr/local/share/texmf install-tex > > This looks all correct. > > > Here is the consequence > > > > sudo make TEXMF=/usr/local/share/texmf install-tex > > cd doc && make TEXMF=/usr/local/share/texmf install-tex > > make[1]: Entering directory '/home/hagbard/Admir/build/texinfo/doc' > > test -n "/usr/local/share/texmf" || (echo "TEXMF must be set." >&2; exit 1) > > /bin/bash /home/hagbard/Admir/source/texinfo/build-aux/install-sh -d > > /usr/local/share/texmf/tex/texinfo /usr/local/share/texmf/tex/generic/epsf > > /usr/bin/install -c -m 644 ../../../source/texinfo/doc/texinfo.tex > > /usr/local/share/texmf/tex/texinfo/texinfo.tex > > /usr/bin/install -c -m 644 ../../../source/texinfo/doc/texinfo-ja.tex > > /usr/local/share/texmf/tex/texinfo/texinfo-ja.tex > > /usr/bin/install -c -m 644 ../../../source/texinfo/doc/epsf.tex > > /usr/local/share/texmf/tex/generic/epsf/epsf.tex > > for f in txi-ca.tex txi-cs.tex txi-de.tex txi-en.tex txi-es.tex txi-fi.tex > > txi-fr.tex txi-hu.tex txi-is.tex txi-it.tex txi-ja.tex txi-nb.tex > > txi-nl.tex txi-nn.tex txi-pl.tex txi-pt.tex txi-ru.tex txi-sr.tex > > txi-tr.tex txi-uk.tex; do \ > > /usr/bin/install -c -m 644 ../../../source/texinfo/doc/$f > > /usr/local/share/texmf/tex/texinfo/$f; done > > make[1]: Leaving directory '/home/hagbard/Admir/build/texinfo/doc' > > > > Finally I run texi2pdf, > > > > hagbard@fuckup: > > + ~/01cuneus/tdr/06ch > > texi2pdf 06a-amcoh.texi > > /usr/local/bin/texi2dvi: texinfo.tex appears to be broken. > > This may be due to the environment variable TEX set to something > > other than (plain) tex, a corrupt texinfo.tex file, or > > to tex itself simply not working. > > This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) > > (preloaded format=etex) > > restricted \write18 enabled. > > entering extended mode > > (./txiversion.tex > > ! I can't find file `texinfo.tex'. > > l.1 \input texinfo.tex > >@bye > > (Press Enter to retry, or Control-D to exit) > > Please type another input file name: > > ! Emergency stop. > > l.1 \input texinfo.tex > >@bye > > No pages of output. > > Transcript written on txiversion.log. > > /usr/local/bin/texi2dvi: quitting. > > The first thing I would do is run > > pdfetex 06a-amcoh.texi > > and see if the same error occurs. If it does, you need to investigate > TeX's search list for files. You could try running > > export TEXINPUTS=/usr/local/share/texmf:$TEXINPUTS > > and running pdfetex again. See Info node "(kpathsea)Path sources". > > Apparently you can also run > > KPATHSEA_DEBUG=32 pdfetex 06a-amcoh.texi > > to get more information on where files are sought. > > I am not very familiar with how TeX looks for files but another thing > to look into is whether an "ls-R" file is up to date. Look at the contents > of /usr/local/share/texmf/ls-R file if it exists and check that texinfo.tex > is listed there. > > >
Using a macro makes pdfetex quits and exits with bad status
Let't try again This is what I have done 2001 cd /home/hagbard/Admir/source/texinfo 2002 ls 2003 rm configure 2004 ./autogen.sh 2000 cd /home/hagbard/Admir/build/texinfo 2001 ../../source/texinfo/configure 2002 make 2003 sudo make install Then I did sudo make TEXMF=/usr/local/share/texmf install-tex Here is the consequence sudo make TEXMF=/usr/local/share/texmf install-tex cd doc && make TEXMF=/usr/local/share/texmf install-tex make[1]: Entering directory '/home/hagbard/Admir/build/texinfo/doc' test -n "/usr/local/share/texmf" || (echo "TEXMF must be set." >&2; exit 1) /bin/bash /home/hagbard/Admir/source/texinfo/build-aux/install-sh -d /usr/local/share/texmf/tex/texinfo /usr/local/share/texmf/tex/generic/epsf /usr/bin/install -c -m 644 ../../../source/texinfo/doc/texinfo.tex /usr/local/share/texmf/tex/texinfo/texinfo.tex /usr/bin/install -c -m 644 ../../../source/texinfo/doc/texinfo-ja.tex /usr/local/share/texmf/tex/texinfo/texinfo-ja.tex /usr/bin/install -c -m 644 ../../../source/texinfo/doc/epsf.tex /usr/local/share/texmf/tex/generic/epsf/epsf.tex for f in txi-ca.tex txi-cs.tex txi-de.tex txi-en.tex txi-es.tex txi-fi.tex txi-fr.tex txi-hu.tex txi-is.tex txi-it.tex txi-ja.tex txi-nb.tex txi-nl.tex txi-nn.tex txi-pl.tex txi-pt.tex txi-ru.tex txi-sr.tex txi-tr.tex txi-uk.tex; do \ /usr/bin/install -c -m 644 ../../../source/texinfo/doc/$f /usr/local/share/texmf/tex/texinfo/$f; done make[1]: Leaving directory '/home/hagbard/Admir/build/texinfo/doc' Finally I run texi2pdf, hagbard@fuckup: + ~/01cuneus/tdr/06ch texi2pdf 06a-amcoh.texi /usr/local/bin/texi2dvi: texinfo.tex appears to be broken. This may be due to the environment variable TEX set to something other than (plain) tex, a corrupt texinfo.tex file, or to tex itself simply not working. This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=etex) restricted \write18 enabled. entering extended mode (./txiversion.tex ! I can't find file `texinfo.tex'. l.1 \input texinfo.tex @bye (Press Enter to retry, or Control-D to exit) Please type another input file name: ! Emergency stop. l.1 \input texinfo.tex @bye No pages of output. Transcript written on txiversion.log. /usr/local/bin/texi2dvi: quitting. > Sent: Friday, June 25, 2021 at 6:34 AM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > > From: Christopher Dimech > > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > > Date: Thu, 24 Jun 2021 19:00:29 +0200 > > > > I used > > > > cd /home/hagbard/Admir/build/texinfo > > ../../source/texinfo/configure --prefix=/home/hagbard/Admir/bin/texinfo > > make > > sudo make install > > The --prefix sets several other directories, including $bindir, > $datadir, and several others. $bindir is supposed to be on PATH. If > it isn't, you most probably don't have the stuff expected to be in > $datadir, either. And that probably means you will have problems when > invoking commands that need to run programs outside of Texinfo, like > TeX etc. > > Why didn't you configure Texinfo to be installed in the usual place, > under /usr/local or somesuch? > > > make TEXMF=/home/hagbard/Admir/bin/texinfo/bin install-tex > > This is wrong in any case, you should have the TEXMF tree in > > /home/hagbard/Admir/bin/texinfo/share/texmf > > or somesuch. And of course one problem is that there's no TEXMF tree > there, because TeX was probably installed in the "usual" places, > somewhere under /usr. I have absolutely no idea what will happen with > commands involving TeX in such a case. > > > Have only been doing what I have been instructed to do. > > That's the problem: the instructions assume you have a normal install, > but you don't. So the instructions can easily be wrong or inaccurate > or incomplete, because no one expects such non-standard installations, > and people usually don't have a lot of experience with those. > > > But I have observed some maintainers who consistently ridicule users > > for deviating from the mainstream use of the software. > > No one ridiculed you. You just need to realize that you are on your > own when using this non-standard installation. > > > Why can't I have multiple versions of the program and run the ones I > > want? > > You can, but you should know very well what you are doing, and how the > different parts, in particular Texinfo and TeX, work together and what > each one of them expects to find where. If you don't know
Using a macro makes pdfetex quits and exits with bad status
> Sent: Friday, June 25, 2021 at 6:34 AM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > > From: Christopher Dimech > > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > > Date: Thu, 24 Jun 2021 19:00:29 +0200 > > > > I used > > > > cd /home/hagbard/Admir/build/texinfo > > ../../source/texinfo/configure --prefix=/home/hagbard/Admir/bin/texinfo > > make > > sudo make install > > The --prefix sets several other directories, including $bindir, > $datadir, and several others. $bindir is supposed to be on PATH. If > it isn't, you most probably don't have the stuff expected to be in > $datadir, either. And that probably means you will have problems when > invoking commands that need to run programs outside of Texinfo, like > TeX etc. > > Why didn't you configure Texinfo to be installed in the usual place, > under /usr/local or somesuch? > > > make TEXMF=/home/hagbard/Admir/bin/texinfo/bin install-tex > > This is wrong in any case, you should have the TEXMF tree in > > /home/hagbard/Admir/bin/texinfo/share/texmf > > or somesuch. And of course one problem is that there's no TEXMF tree > there, because TeX was probably installed in the "usual" places, > somewhere under /usr. I have absolutely no idea what will happen with > commands involving TeX in such a case. > > > Have only been doing what I have been instructed to do. > > That's the problem: the instructions assume you have a normal install, > but you don't. So the instructions can easily be wrong or inaccurate > or incomplete, because no one expects such non-standard installations, > and people usually don't have a lot of experience with those. Would agree that people usually don't have a lot of experience with that. The best thing is to tell how to get a scheme that would work. Gavin made some changes and would like to test them, and report on any pending problems. Gavin, how do you handle the different development versions, and could you add a scheme that could work in the configure and install sections. I am very satisfied with how I frequently test gcc. > > But I have observed some maintainers who consistently ridicule users > > for deviating from the mainstream use of the software. > > No one ridiculed you. You just need to realize that you are on your > own when using this non-standard installation. It would be a great improvement to have a standard on how we can test newer versions of texinfo without affecting the stable version we normally use. It makes it very difficult for me to help out as a tester. > > Why can't I have multiple versions of the program and run the ones I > > want? > > You can, but you should know very well what you are doing, and how the > different parts, in particular Texinfo and TeX, work together and what > each one of them expects to find where. If you don't know these > details, my best recommendation is not to do that, as you will be > facing an uphill battle. I am quite sure you have more experience to be able to tell us exactly how to set things up in the case of development versions. It looks as if few bother with what happens in the development version of texinfo. Am I the only one who gets in all this trouble, I ask ? > > Perhaps texinfo is a pain and you are unable to handle a solution > > that is straightforward. > > Texinfo, as any other package, is supposed to be built and installed > according to the supported procedures. Anything else is always a > pain, with any non-trivial package that installs many files, let alone > depends on other packages that are installed separately. > > > At least Gavin tries his best to understand the difficulties users > > face, unlike some others. > > I cannot speak for Gavin, I just wanted to warn you so you lower your > expectations about the effectiveness and accuracy of the help you will > get for your hand-made installation. If you don't like what I'm > telling you, feel free to disregard the advice and keep trying to make > your installation work. > > > Can you give we a scheme that works so I can test the development version > > independently of any other texinfo setup I have? > > No, I can't, not a practical scheme anyway. For example, I have no > idea how to force TeX to work correctly with texinfo.tex in one place > and the full TEXMF tree in another. That's the origin of the problem, nobody can give me a practical scheme to follow. > Why not simply install the development version instead the one
Using a macro makes pdfetex quits and exits with bad status
Don't expect this list to support you in that adventure How very convenient! I want get the regular development snapshot to test the work in progress, building it separately, from source, at another location. The problem with PATH occurred after texi2pdf called texi2dvi I used cd /home/hagbard/Admir/build/texinfo ../../source/texinfo/configure --prefix=/home/hagbard/Admir/bin/texinfo make sudo make install make TEXMF=/home/hagbard/Admir/bin/texinfo/bin install-tex Have only been doing what I have been instructed to do. But I have observed some maintainers who consistently ridicule users for deviating from the mainstream use of the software. Why can't I have multiple versions of the program and run the ones I want? Perhaps texinfo is a pain and you are unable to handle a solution that is straightforward. At least Gavin tries his best to understand the difficulties users face, unlike some others. Can you give we a scheme that works so I can test the development version independently of any other texinfo setup I have? > Sent: Friday, June 25, 2021 at 4:16 AM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > > From: Christopher Dimech > > Date: Thu, 24 Jun 2021 17:53:02 +0200 > > Sensitivity: Normal > > Cc: help-texinfo@gnu.org > > > > Ok, I added the texinfo development directory to PATH. > > > > Now getting again to the old problem of texinfo.tex > > Why did you need to add some directory to PATH? Did you install > Texinfo with "make install", as expected? Assuming you used some sane > vale of the --prefix configure option, "make install" should have made > sure every executable is on PATH from the get-go. Since you say you > need to add some directory to PATH, I suspect that instead of a normal > install you did something "by hand", and now the thing crumbles under > you feet because of that. > > Texinfo is not guaranteed to work correctly unless you install it > after building using the provided "make install" procedure (followed > by a manual install of texinfo.tex, if needed). If you didn't do > that, things will fall apart, and please don't expect this list to > support you in that adventure. >
Using a macro makes pdfetex quits and exits with bad status
Ok, I added the texinfo development directory to PATH. Now getting again to the old problem of texinfo.tex hagbard@fuckup: + ~/01cuneus/tdr/06ch /home/hagbard/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi /home/hagbard/Admir/bin/texinfo/bin/texi2dvi: texinfo.tex appears to be broken. This may be due to the environment variable TEX set to something other than (plain) tex, a corrupt texinfo.tex file, or to tex itself simply not working. This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=etex) restricted \write18 enabled. entering extended mode (./txiversion.tex ! I can't find file `texinfo.tex'. l.1 \input texinfo.tex @bye (Press Enter to retry, or Control-D to exit) Please type another input file name: ! Emergency stop. l.1 \input texinfo.tex @bye No pages of output. Transcript written on txiversion.log. /home/hagbard/Admir/bin/texinfo/bin/texi2dvi: quitting. > Sent: Friday, June 25, 2021 at 3:42 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > On Thu, Jun 24, 2021 at 04:25:21PM +0200, Christopher Dimech wrote: > > > Sent: Friday, June 25, 2021 at 1:26 AM > > > From: "Patrice Dumas" > > > To: "Christopher Dimech" > > > Cc: "Eli Zaretskii" , help-texinfo@gnu.org > > > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > > > > > On Thu, Jun 24, 2021 at 03:12:30PM +0200, Christopher Dimech wrote: > > > > > > > > Have been running the development version of texi2pdf with the following > > > > command. > > > > > > > > /home/hagbard/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi > > > > > > > > bin/tex/texinfo has been created and includes tekinfo.text as expected > > > > > > > > But, I get smacked with this message > > > > > > > > /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: 37: > > > > /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: texi2dvi: not found > > > > > > > > I do have texi2dvi in /home/hagbard/Admir/bin/texinfo/bin/ > > > > > > > > Looks like texi2pdf is looking for texi2dvi somewhere else. > > > > > > texi2dvi and texi2pdf (and texi2any, info and other installed > > > scripts/binaries) are installed classically, based on ./configure > > > options, use of DESTDIR... So my guess is that if texi2pdf is in > > > /home/hagbard/Admir/bin/texinfo/bin/, texi2dvi is there too. > > > > Correct, texi2dvi is there too. Then, how am I getting this? > > > > /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: texi2dvi: not found > > > > You need to have /home/hagbard/Admir/bin/texinfo/bin in your PATH. > >
Using a macro makes pdfetex quits and exits with bad status
> Sent: Friday, June 25, 2021 at 1:26 AM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "Eli Zaretskii" , help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > On Thu, Jun 24, 2021 at 03:12:30PM +0200, Christopher Dimech wrote: > > > > Have been running the development version of texi2pdf with the following > > command. > > > > /home/hagbard/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi > > > > bin/tex/texinfo has been created and includes tekinfo.text as expected > > > > But, I get smacked with this message > > > > /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: 37: > > /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: texi2dvi: not found > > > > I do have texi2dvi in /home/hagbard/Admir/bin/texinfo/bin/ > > > > Looks like texi2pdf is looking for texi2dvi somewhere else. > > texi2dvi and texi2pdf (and texi2any, info and other installed > scripts/binaries) are installed classically, based on ./configure > options, use of DESTDIR... So my guess is that if texi2pdf is in > /home/hagbard/Admir/bin/texinfo/bin/, texi2dvi is there too. Correct, texi2dvi is there too. Then, how am I getting this? /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: texi2dvi: not found doing ls gives hagbard@fuckup: + ~/01cuneus/tdr/06ch ls /home/hagbard/Admir/bin/texinfo/bin/ info makeinfo pod2texi texi2any texi2pdf texinfo-js install-info pdftexi2dvi tex texi2dvi texindex > texi2pdf is just a wrapper around texi2dvi --pdf. > > -- > Pat >
Using a macro makes pdfetex quits and exits with bad status
Have been running the development version of texi2pdf with the following command. /home/hagbard/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi bin/tex/texinfo has been created and includes tekinfo.text as expected But, I get smacked with this message /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: 37: /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: texi2dvi: not found I do have texi2dvi in /home/hagbard/Admir/bin/texinfo/bin/ Looks like texi2pdf is looking for texi2dvi somewhere else. > Sent: Thursday, June 24, 2021 at 5:51 PM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > > From: Christopher Dimech > > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > > Date: Wed, 23 Jun 2021 20:52:44 +0200 > > > > > That would clobber existing installations it TeX Live etc., so it's > > > not a good idea to do that by default, without the user's say-so. > > > > > > > I disagree on the additional tex/texinfo/ part of the installation > > > > > > I think your perspective is biased in this aspect. > > > > Quite likely. I compare it with how I customarily install other > > development versions in Gnu for testing. There seem to be many > > considerations when installing texinfo. > > What's special about Texinfo is that texinfo.tex is distributed by > other packages as well, and only the user knows which version he/she > wants. Installing a wrong version can easily render the entire > installation unusable. >
Using a macro makes pdfetex quits and exits with bad status
I would value writing latex files in emacs, and then call a Gnu program
to produce the latex typeset document.
> Sent: Thursday, June 24, 2021 at 6:40 AM
> From: "Eli Zaretskii"
> To: "Christopher Dimech"
> Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> > From: Christopher Dimech
> > Date: Wed, 23 Jun 2021 20:20:49 +0200
> > Cc: help-texinfo gnu
> >
> > Of course, but I also give you a point of thought from user perspective.
> >
> > That way, the texinfo installation could also handle the additional
> >
> > make TEXMF=/your/texmf install-tex
> > texinfo.tex is installed in ${TEXMF}/tex/texinfo/texinfo.tex, etc.
>
> That would clobber existing installations it TeX Live etc., so it's
> not a good idea to do that by default, without the user's say-so.
>
> > I disagree on the additional tex/texinfo/ part of the installation
>
> I think your perspective is biased in this aspect.
>
Using a macro makes pdfetex quits and exits with bad status
Does Gnu have a latex construct program to produce documents?
> Sent: Thursday, June 24, 2021 at 6:40 AM
> From: "Eli Zaretskii"
> To: "Christopher Dimech"
> Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> > From: Christopher Dimech
> > Date: Wed, 23 Jun 2021 20:20:49 +0200
> > Cc: help-texinfo gnu
> >
> > Of course, but I also give you a point of thought from user perspective.
> >
> > That way, the texinfo installation could also handle the additional
> >
> > make TEXMF=/your/texmf install-tex
> > texinfo.tex is installed in ${TEXMF}/tex/texinfo/texinfo.tex, etc.
>
> That would clobber existing installations it TeX Live etc., so it's
> not a good idea to do that by default, without the user's say-so.
>
> > I disagree on the additional tex/texinfo/ part of the installation
>
> I think your perspective is biased in this aspect.
>
Using a macro makes pdfetex quits and exits with bad status
> Sent: Thursday, June 24, 2021 at 7:07 AM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "Eli Zaretskii" , help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > On Wed, Jun 23, 2021 at 08:52:44PM +0200, Christopher Dimech wrote: > > > > Quite likely. I compare it with how I customarily install other > > development versions in Gnu for testing. There seem to be many > > considerations when installing texinfo. > > I think everybody agrees that having to install texinfo.tex separately > is a pain. However, I do not think that it is possible to do otherwise, > as the TeX installation setup dictates what can be done, and it does not > follow the GNU way -- I believe it predates the GNU way. In addition > TeX/LaTeX by itself is a very big piece of many softwares. > > What would be the other issues associated with texinfo installation? Have done sudo make TEXMF=/home/hagbard/Admir/bin/texinfo/bin install-tex running "/home/hagbard/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi" gave hagbard@fuckup: + ~/01cuneus/tdr/06ch /home/hagbard/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi /home/hagbard/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: 37: /home/hagbard/Admir/bin/texinfo/bin/texi2pdf: texi2dvi: not found It could be looking at /usr/local/bin/texi2dvi
Using a macro makes pdfetex quits and exits with bad status
I will install it as instructed, run a few tests and let you know of any difficulties. Had followed INSTALL.generic. > Sent: Thursday, June 24, 2021 at 7:07 AM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "Eli Zaretskii" , help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > On Wed, Jun 23, 2021 at 08:52:44PM +0200, Christopher Dimech wrote: > > > > Quite likely. I compare it with how I customarily install other > > development versions in Gnu for testing. There seem to be many > > considerations when installing texinfo. > > I think everybody agrees that having to install texinfo.tex separately > is a pain. However, I do not think that it is possible to do otherwise, > as the TeX installation setup dictates what can be done, and it does not > follow the GNU way -- I believe it predates the GNU way. In addition > TeX/LaTeX by itself is a very big piece of many softwares. > > What would be the other issues associated with texinfo installation? > > -- > Pat >
Using a macro makes pdfetex quits and exits with bad status
> Sent: Thursday, June 24, 2021 at 6:40 AM
> From: "Eli Zaretskii"
> To: "Christopher Dimech"
> Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> > From: Christopher Dimech
> > Date: Wed, 23 Jun 2021 20:20:49 +0200
> > Cc: help-texinfo gnu
> >
> > Of course, but I also give you a point of thought from user perspective.
> >
> > That way, the texinfo installation could also handle the additional
> >
> > make TEXMF=/your/texmf install-tex
> > texinfo.tex is installed in ${TEXMF}/tex/texinfo/texinfo.tex, etc.
>
> That would clobber existing installations it TeX Live etc., so it's
> not a good idea to do that by default, without the user's say-so.
>
> > I disagree on the additional tex/texinfo/ part of the installation
>
> I think your perspective is biased in this aspect.
Quite likely. I compare it with how I customarily install other
development versions in Gnu for testing. There seem to be many
considerations when installing texinfo.
Using a macro makes pdfetex quits and exits with bad status
Of course, but I also give you a point of thought from user perspective.
That way, the texinfo installation could also handle the additional
make TEXMF=/your/texmf install-tex
texinfo.tex is installed in ${TEXMF}/tex/texinfo/texinfo.tex, etc.
I disagree on the additional tex/texinfo/ part of the installation
Instead install in ${TEXMF}/texinfo.tex, etc.
I have just installed in /home/hagbard/Admir/bin/texinfo/bin
and using make TEXMF=/home/hagbard/Admir/bin/texinfo/bin install-tex
will install /home/hagbard/Admir/bin/texinfo/bin/tex/texinfo/texinfo.tex
The result is a convoluted installation.
Christopher
Old Fart and Curmudgeon
> Sent: Thursday, June 24, 2021 at 5:11 AM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "Patrice Dumas" , "help-texinfo gnu"
>
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> On Wed, Jun 23, 2021 at 06:38:55PM +0200, Christopher Dimech wrote:
> >
> > That is surprising.
> >
> > Could you introspect a working installation that works like this
> >
> >
> >
> > hagbard@fuckup: ~/Admir/build/texinfo
> > ../../source/texinfo/configure --prefix=/home/hagbard/Admir/bin/texinfo
> >
> > make
> >
> > sudo make install
> >
> > ~/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi
>
> You should listen to what Patrice told you. It is not enough just
> to run "make install". You need to copy texinfo.tex somewhere TeX will
> find it.
>
Using a macro makes pdfetex quits and exits with bad status
That is surprising.
Could you introspect a working installation that works like this
hagbard@fuckup: ~/Admir/build/texinfo
../../source/texinfo/configure --prefix=/home/hagbard/Admir/bin/texinfo
make
sudo make install
~/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi
> Sent: Thursday, June 24, 2021 at 3:00 AM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> On Wed, Jun 23, 2021 at 04:57:02PM +0200, Christopher Dimech wrote:
> >
> > I removed the old version installed by synaptic and installed the
> > development version.
> >
> >
> >
> > cd ~/Admir/source/texinfo
> > ./autogen.sh
> >
> > cd ~/Admir/build/texinfo
> > ../../source/texinfo/configure
> > make
> > sudo make install
> >
> >
> >
> > Could I have missed something ?
>
> Yes, there are specific instructions for texinfo.tex, as seen in
> INSTALL:
> * texinfo.tex and the other *.tex files are not installed by
> `make install', because there is no reliable way to know where to
> install them. Instead, you have to run an additional make command
> after the normal make install:
> make TEXMF=/your/texmf install-tex
> texinfo.tex is installed in ${TEXMF}/tex/texinfo/texinfo.tex, etc.
>
>
>
> >
> >
> > > Sent: Thursday, June 24, 2021 at 2:24 AM
> > > From: "Patrice Dumas"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Using a macro makes pdfetex quits and exits with bad status
> > >
> > > On Wed, Jun 23, 2021 at 04:12:24PM +0200, Christopher Dimech wrote:
> > > >
> > > > (./txiversion.tex
> > > > ! I can't find file `texinfo.tex'.
> > > > l.1 \input texinfo.tex
> > >
> > > Could it be because you didn't install it? Instruction are in INSTALL.
> > >
> > > --
> > > Pat
> > >
> > >
>
>
Using a macro makes pdfetex quits and exits with bad status
I removed the old version installed by synaptic and installed the development version. cd ~/Admir/source/texinfo ./autogen.sh cd ~/Admir/build/texinfo ../../source/texinfo/configure make sudo make install Could I have missed something ? > Sent: Thursday, June 24, 2021 at 2:24 AM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > On Wed, Jun 23, 2021 at 04:12:24PM +0200, Christopher Dimech wrote: > > > > (./txiversion.tex > > ! I can't find file `texinfo.tex'. > > l.1 \input texinfo.tex > > Could it be because you didn't install it? Instruction are in INSTALL. > > -- > Pat > >
Using a macro makes pdfetex quits and exits with bad status
After fixing a few other problems associated with the following x86_64-linux-gnu-gcc: error: MiscXS.c: No such file or directory The fix was done by doing sudo apt-get update && sudo apt-get install build-essential Now I run into a different problem, namely texi2pdf 06a-amcoh.texi /usr/local/bin/texi2dvi: texinfo.tex appears to be broken. This may be due to the environment variable TEX set to something other than (plain) tex, a corrupt texinfo.tex file, or to tex itself simply not working. This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=etex) restricted \write18 enabled. entering extended mode (./txiversion.tex ! I can't find file `texinfo.tex'. l.1 \input texinfo.tex @bye (Press Enter to retry, or Control-D to exit) Please type another input file name: ! Emergency stop. l.1 \input texinfo.tex @bye No pages of output. Transcript written on txiversion.log. /usr/local/bin/texi2dvi: quitting.
Using a macro makes pdfetex quits and exits with bad status
It was a previous installation using Synaptic Package Manager. Have now removed it, rebuilt the development version. But now I get the following problem: x86_64-linux-gnu-gcc: error: MiscXS.c: No such file or directory x86_64-linux-gnu-gcc: fatal error: no input files compilation terminated. > Sent: Wednesday, June 23, 2021 at 5:12 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > On Wed, Jun 23, 2021 at 12:17 AM Christopher Dimech wrote: > > > > somehow texi2pdf is trying to pick out an old > > /usr/share/texmf/tex/texinfo/texinfo.tex > > > > You've found the problem. It always helps to attach the output from > your command that is showing the failure and this confirms the > problem. Where have you installed texinfo.tex? > > You can probably just replace /usr/share/texmf/tex/texinfo/texinfo.tex > with the newer version. > >
Using a macro makes pdfetex quits and exits with bad status
somehow texi2pdf is trying to pick out an old
/usr/share/texmf/tex/texinfo/texinfo.tex
- Christopher Dimech
Administrator General - Naiad Informatics - Gnu Project
Society has become too quick to pass judgement and declare someone
Persona Non-Grata, the most extreme form of censure a country can
bestow.
In a new era of destructive authoritarianism, I support Richard
Stallman. Times of great crisis are also times of great
opportunity. I call upon you to make this struggle yours as well !
https://stallmansupport.org/
https://www.fsf.org/ https://www.gnu.org/
> Sent: Wednesday, June 23, 2021 at 11:09 AM
> From: "Christopher Dimech"
> To: "Gavin Smith"
> Cc: "help-texinfo gnu"
> Subject: Using a macro makes pdfetex quits and exits with bad status
>
>
> Have tested again, with the problem still occurring with the development
> version.
> The @ifset and @ifclear commands were removed.
>
> @usubsec{16D,
> Utilisation of Rapid Computations}
>
>
>
> texi2pdf 06a-amcoh.texi
> This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
> (./06a-amcoh.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2018-01-09.11]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions,
> (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.)
> (../mastaba/ramasutra.texi) (./06c-amcoh-rfc.texi)
> [1{/var/lib/texmf/fonts/map/
> pdftex/updmap/pdftex.map}] [-1] (6 @ Ameliorating Waveform Coherency)
> Cross reference values unknown; you must run TeX again. [1] [2] [3] [4]
> [5] [6] [7]
> Overfull \hbox (40.24854pt too wide) detected at line 790
> @smalli U[] @smallrm = []
> [8] [9] [10] [11] [12]
> Overfull \hbox (23.94524pt too wide) detected at line 1287
> [] []
> [13] [14] [15] [16] [17]
> Underfull \hbox (badness 1) in paragraph at lines 1719--1722
> @textrm Equipped with the In-ner Prod-uct, the set of Fourier Ba-sis
> [18] [19] [20] [21]
> Runaway argument?
> {
> ./06a-amcoh.texi:1958: Paragraph ended before @trim@ was complete.
>
>@par
> ^^M
> Utilisation of Rapid Computations
> @eatspaces ...@expandafter @trim@ @expandafter {#1
>}
> @value ...value {#1}@else @csname SET#1@endcsname
> @fi
> @writetocentry ...mp {@write @tocfile {@#1entry{#2
> }{#3}{@lastnode
> }{@noexpan...
>
> @sectionheading ...toctype @sectionlevel }{#1}{#4}
> @donoderef {#3}@nobreak
> @v...
> ...
> l.1958 Utilisation of Rapid Computations}
>
> ?
> ./06a-amcoh.texi:1958: Emergency stop.
>
>@par
> ^^M
> Utilisation of Rapid Computations
> @eatspaces ...@expandafter @trim@ @expandafter {#1
>}
> @value ...value {#1}@else @csname SET#1@endcsname
> @fi
> @writetocentry ...mp {@write @tocfile {@#1entry{#2
> }{#3}{@lastnode
> }{@noexpan...
>
> @sectionheading ...toctype @sectionlevel }{#1}{#4}
> @donoderef {#3}@nobreak
> @v...
> ...
> l.1958 Utilisation of Rapid Computations}
>
> ./06a-amcoh.texi:1958: ==> Fatal error occurred, no output PDF file produced!
> Transcript written on 06a-amcoh.log.
> This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
>
>
> Runaway argument?
> {
> ./06a-amcoh.texi:1958: Paragraph ended before @trim@ was complete.
>
>@par
> ^^M
> Utilisation of Rapid Computations
> @eatspaces ...@expandafter @trim@ @expandafter {#1
>}
> @value ...value {#1}@else @csname SET#1@endcsname
> @fi
> @writetocentry ...mp {@write @tocfile {@#1entry{#2
> }{#3}{@lastnode
> }{@noexpan...
>
> @sectionheading ...toctype @sectionlevel }{#1}{#4}
> @donoderef {#3}@nobreak
> @v...
> ...
> l.1958 Utilisation of Rapid Compu
Using a macro makes pdfetex quits and exits with bad status
Have tested again, with the problem still occurring with the development
version.
The @ifset and @ifclear commands were removed.
@usubsec{16D,
Utilisation of Rapid Computations}
texi2pdf 06a-amcoh.texi
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian)
(preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
(./06a-amcoh.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
Loading texinfo [version 2018-01-09.11]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(../mastaba/ramasutra.texi) (./06c-amcoh-rfc.texi) [1{/var/lib/texmf/fonts/map/
pdftex/updmap/pdftex.map}] [-1] (6 @ Ameliorating Waveform Coherency)
Cross reference values unknown; you must run TeX again. [1] [2] [3] [4]
[5] [6] [7]
Overfull \hbox (40.24854pt too wide) detected at line 790
@smalli U[] @smallrm = []
[8] [9] [10] [11] [12]
Overfull \hbox (23.94524pt too wide) detected at line 1287
[] []
[13] [14] [15] [16] [17]
Underfull \hbox (badness 1) in paragraph at lines 1719--1722
@textrm Equipped with the In-ner Prod-uct, the set of Fourier Ba-sis
[18] [19] [20] [21]
Runaway argument?
{
./06a-amcoh.texi:1958: Paragraph ended before @trim@ was complete.
@par
^^M
Utilisation of Rapid Computations
@eatspaces ...@expandafter @trim@ @expandafter {#1
}
@value ...value {#1}@else @csname SET#1@endcsname
@fi
@writetocentry ...mp {@write @tocfile {@#1entry{#2
}{#3}{@lastnode }{@noexpan...
@sectionheading ...toctype @sectionlevel }{#1}{#4}
@donoderef {#3}@nobreak @v...
...
l.1958 Utilisation of Rapid Computations}
?
./06a-amcoh.texi:1958: Emergency stop.
@par
^^M
Utilisation of Rapid Computations
@eatspaces ...@expandafter @trim@ @expandafter {#1
}
@value ...value {#1}@else @csname SET#1@endcsname
@fi
@writetocentry ...mp {@write @tocfile {@#1entry{#2
}{#3}{@lastnode }{@noexpan...
@sectionheading ...toctype @sectionlevel }{#1}{#4}
@donoderef {#3}@nobreak @v...
...
l.1958 Utilisation of Rapid Computations}
./06a-amcoh.texi:1958: ==> Fatal error occurred, no output PDF file produced!
Transcript written on 06a-amcoh.log.
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian)
(preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
Runaway argument?
{
./06a-amcoh.texi:1958: Paragraph ended before @trim@ was complete.
@par
^^M
Utilisation of Rapid Computations
@eatspaces ...@expandafter @trim@ @expandafter {#1
}
@value ...value {#1}@else @csname SET#1@endcsname
@fi
@writetocentry ...mp {@write @tocfile {@#1entry{#2
}{#3}{@lastnode }{@noexpan...
@sectionheading ...toctype @sectionlevel }{#1}{#4}
@donoderef {#3}@nobreak @v...
...
l.1958 Utilisation of Rapid Computations}
?
./06a-amcoh.texi:1958: Emergency stop.
@par
^^M
Utilisation of Rapid Computations
@eatspaces ...@expandafter @trim@ @expandafter {#1
}
@value ...value {#1}@else @csname SET#1@endcsname
@fi
@writetocentry ...mp {@write @tocfile {@#1entry{#2
}{#3}{@lastnode }{@noexpan...
@sectionheading ...toctype @sectionlevel }{#1}{#4}
@donoderef {#3}@nobreak @v...
...
l.1958 Utilisation of Rapid Computations}
./06a-amcoh.texi:1958: ==> Fatal error occurred, no output PDF file produced!
Transcript written on 06a-amcoh.log.
/usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
> Sent: Wednesday, June 23, 2021 at 8:01 AM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> On Tue, Jun 22, 2021 at 6:53 PM Christopher Dimech wrote:
> >
> > @macro usubsec {label, titl}
> >
> > @set lb \label\
> > @set tl \titl\
> > @ifclear usubsec-no-label
> >@unnumberedsubsec @value{lb} @
deleting the temporary files produced by texi2pdf
Doing as instructed fails to find files containing macros texi2pdf --clean 06a-amcoh.texi texi2pdf --clean 06a-amcoh.texi This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=pdfetex) restricted \write18 enabled. entering extended mode (../../.././06a-amcoh.texi (/home/hagbard/01cuneus/tdr/06ch/texinfo.tex Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs, page headings, tables, conditionals, indexing, sectioning, toc, environments, defuns, macros, cross references, insertions, (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex This is `epsf.tex' v2.7.4 <14 February 2011> ) localization, formatting, and turning on texinfo input format.) ../../.././06a-amcoh.texi:85: I can't find file `../mastaba/ramasutra.texi'. @temp ->@input ../mastaba/ramasutra.texi @includezzz ...and @input #1 }@expandafter }@temp @popthisfilestack l.85 @include ../mastaba/ramasutra.texi (Press Enter to retry, or Control-D to exit) Please type another input file name: ../../.././06a-amcoh.texi:85: Emergency stop. @temp ->@input ../mastaba/ramasutra.texi @includezzz ...and @input #1 }@expandafter }@temp @popthisfilestack l.85 @include ../mastaba/ramasutra.texi ../../.././06a-amcoh.texi:85: ==> Fatal error occurred, no output PDF file pro duced! Transcript written on 06a-amcoh.log. /usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting. > Sent: Wednesday, June 23, 2021 at 8:03 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: deleting the temporary files produced by texi2pdf > > On Tue, Jun 22, 2021 at 6:04 PM Christopher Dimech wrote: > > > > I keep having to delete the temporary files produced by texi2pdf, otherwise > > the > > command texi2pdf fails. > > > > One could think of a command option to automatically clean temporary files. > > Is there capability for that already? > > Yes, run texi2pdf --clean. >
Using a macro makes pdfetex quits and exits with bad status
> Sent: Wednesday, June 23, 2021 at 8:01 AM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> On Tue, Jun 22, 2021 at 6:53 PM Christopher Dimech wrote:
> >
> > @macro usubsec {label, titl}
> >
> > @set lb \label\
> > @set tl \titl\
> > @ifclear usubsec-no-label
> >@unnumberedsubsec @value{lb} @ @value{tl}
> > @end ifclear
> >
> > @ifset usubsec-no-label
> > @unnumberedsubsec @value{tl}
> > @end ifset
> >
> > @end macro
> >
>
> This appears to work OK?
>
> Eli gave you good advice about putting the macro definition inside the
> conditionals rather than the other way around although I don't know if
> that is part of the problem here.
No, have not seen difficulties in the way I have done them. Taking the
advice did not get things any better. So I say that people can use them.
> I remember you had problems with newlines in macro arguments before
> but I thought we had fixed them. It wouldn't be surprising if there
> were still problems though.
I thought so too. Can get the development version again' and can have
another tour to fix the last few bits.
> $ pdfetex test.texi
> This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
> (./test.texi (./texinfo.tex Loading texinfo [version 2021-04-25.21]: pdf,
> fonts, glyphs, page headings, tables, conditionals, indexing, sectioning, toc,
> environments, defuns, macros, cross references, insertions, (./epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.)
> [1{/var/lib/t
> exmf/fonts/map/pdftex/updmap/pdftex.map}]
> ) /type1/public/amsfonts/cm/cmbx12.pfb>
> Output written on test.pdf (1 page, 13595 bytes).
> Transcript written on test.log.
>
Using a macro makes pdfetex quits and exits with bad status
I would like something closer to lisp actually. > Sent: Wednesday, June 23, 2021 at 6:54 AM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: pertu...@free.fr, help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > > From: Christopher Dimech > > Cc: pertu...@free.fr, help-texinfo@gnu.org > > Date: Tue, 22 Jun 2021 20:41:16 +0200 > > > > That would make the use of macros very limited. > > Macros in Texinfo have many problems. >
Using a macro makes pdfetex quits and exits with bad status
Although I have done as instructed, the problem remains. I concur that texinfo macros are considerably limited in capability. But currently that's what we have and I quite like the structure. In the future we might require something more robust although based on similar principles. > Sent: Wednesday, June 23, 2021 at 6:54 AM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: pertu...@free.fr, help-texinfo@gnu.org > Subject: Re: Using a macro makes pdfetex quits and exits with bad status > > > From: Christopher Dimech > > Cc: pertu...@free.fr, help-texinfo@gnu.org > > Date: Tue, 22 Jun 2021 20:41:16 +0200 > > > > That would make the use of macros very limited. > > Macros in Texinfo have many problems. >
Using a macro makes pdfetex quits and exits with bad status
That would make the use of macros very limited. I have many working macros
except for the
multi-line situation. I am pushing the functionality requirements quite a bit,
but I feel
it is for the better, using realistic scenarios.
I wonder what Gavin think about this.
> Sent: Wednesday, June 23, 2021 at 6:23 AM
> From: "Eli Zaretskii"
> To: "Christopher Dimech"
> Cc: pertu...@free.fr, help-texinfo@gnu.org
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> > From: Christopher Dimech
> > Date: Tue, 22 Jun 2021 19:52:52 +0200
> > Cc: help-texinfo gnu
> >
> > @macro usubsec {label, titl}
> >
> > @set lb \label\
> > @set tl \titl\
> > @ifclear usubsec-no-label
> >@unnumberedsubsec @value{lb} @ @value{tl}
> > @end ifclear
> >
> > @ifset usubsec-no-label
> > @unnumberedsubsec @value{tl}
> > @end ifset
> >
> > @end macro
>
> IME, it's better to have 2 different variants of this macr instead of
> having @ifclear/@ifset inside the macro. IOW, move the
> @ifset/@ifclear outside of the macro, and have each condition define
> the @macro differently, but without any conditionals inside it.
>
Using a macro makes pdfetex quits and exits with bad status
@macro usubsec {label, titl}
@set lb \label\
@set tl \titl\
@ifclear usubsec-no-label
@unnumberedsubsec @value{lb} @ @value{tl}
@end ifclear
@ifset usubsec-no-label
@unnumberedsubsec @value{tl}
@end ifset
@end macro
> Sent: Wednesday, June 23, 2021 at 5:47 AM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> On Tue, Jun 22, 2021 at 07:21:33PM +0200, Christopher Dimech wrote:
> > Am running a macro that continues on the next line, but pdfetex quits and
> > exits
> > with bad status. Should this problem not have been fixed before?
>
> It probably depends on the macro and what it expands to. You would need
> to provide a real case or more information.
>
> >
> > @usubsec{16D,
> > Utilisation of Rapid Computations}
>
>
Using a macro makes pdfetex quits and exits with bad status
Am running a macro that continues on the next line, but pdfetex quits and exits
with bad status. Should this problem not have been fixed before?
@usubsec{16D,
Utilisation of Rapid Computations}
deleting the temporary files produced by texi2pdf
I keep having to delete the temporary files produced by texi2pdf, otherwise the command texi2pdf fails. One could think of a command option to automatically clean temporary files. Is there capability for that already? Felicitations Christopher
[Request] Capability to customise the layout of algorithms
I have seen tho latex package from 2005 that is today defunct called "algorithmicx". https://www.ctan.org/pkg/algorithmicx?lang=en It would be useful if tex info had such functionality. Does it exist?
Re: Texinfo with latex
Am trying to get ob-latex to do the same with regards to mathjax. Have been doing some review of things these few months. > Sent: Saturday, May 08, 2021 at 6:52 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Texinfo with latex > > On Fri, May 7, 2021 at 5:59 AM Christopher Dimech wrote: > > > > Would it be too difficult for texinfo to start accepting latex command > > structured, in addition to plain tex? Currently texinfo and org-mode > > do not work very well together - texinfo in mainly "plain tex", whereas > > org-mode in clearly "ob-latex". It makes sense to allow copying code > > between the two and be able to render and preview equations. > > We discussed this a few months ago and it is not possible to support > LaTeX in Texinfo files. If writing equations you need to stick to > plain TeX. A small number of LaTeX commands, such as \frac, can be > provided as a convenience, but proper LaTeX compatibility should be > considered a complete impossibility. Was it because of a parser problem? Forgot some details on that. > > With the latest texinfo mathjax improvements, texinfo works better with > > preview in emacs, than with ob-latex. > > That's good to hear. > > - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
Texinfo with latex
Would it be too difficult for texinfo to start accepting latex command structured, in addition to plain tex? Currently texinfo and org-mode do not work very well together - texinfo in mainly "plain tex", whereas org-mode in clearly "ob-latex". It makes sense to allow copying code between the two and be able to render and preview equations. With the latest texinfo mathjax improvements, texinfo works better with preview in emacs, than with ob-latex. Regards Christopher --------- Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
Re: tex-mode.el for setting superscript and subscript face
Anyway, I have introduced tex-font-lock-keywords-1 and tex-font-lock-keywords-2. Then defined tex-font-lock-keywords-3 (defconst tex-font-lock-keywords-3 (append tex-font-lock-keywords-2 '((tex-font-lock-match-suscript (1 (tex-font-lock-suscript (match-beginning 0)) append "Experimental expressions to highlight in TeX modes.") (defconst tex-font-lock-keywords tex-font-lock-keywords-1 "Default expressions to highlight in TeX modes.") Finally using a hook (add-hook 'texinfo-mode-hook (lambda () (font-lock-add-keywords nil tex-font-lock-keywords-3))) Still cannot get the thing enabled though > Sent: Saturday, January 16, 2021 at 11:38 PM > From: "Christopher Dimech" > To: "Christopher Dimech" > Cc: "Robert Pluim" , "help-texinfo gnu" > > Subject: Re: tex-mode.el for setting superscript and subscript face > > I do nat think that I would need most of the contents in > tex-font-lock-keywords-* > > > Sent: Saturday, January 16, 2021 at 11:35 PM > > From: "Christopher Dimech" > > To: "Christopher Dimech" > > Cc: "Robert Pluim" , "help-texinfo gnu" > > > > Subject: Re: tex-mode.el for setting superscript and subscript face > > > > I am still trying to take only the minimal code for the superscript > > and subscript option from tex-font-lock-keywords-* > > > > > > > > > Sent: Friday, January 15, 2021 at 9:35 PM > > > From: "Christopher Dimech" > > > To: "Robert Pluim" > > > Cc: "help-texinfo gnu" > > > Subject: Re: tex-mode.el for setting superscript and subscript face > > > > > > Have tried using tex-font-lock-keywords-3. But tex-font-lock-keywords-2 > > > and tex-font-lock-keywords-1 seem to be doing too many things. I only > > > require the part where the superscripts and subscripts are shown in > > > smaller > > > font and placed at a different height level. > > > > > > (defconst tex-font-lock-keywords-3 > > > (append tex-font-lock-keywords-2 > > > '((tex-font-lock-match-suscript > > >(1 (tex-font-lock-suscript (match-beginning 0)) append > > > "Experimental expressions to highlight in TeX modes.") > > > > > > > Sent: Friday, January 15, 2021 at 9:09 PM > > > > From: "Robert Pluim" > > > > To: "Christopher Dimech" > > > > Cc: "help-texinfo gnu" > > > > Subject: Re: tex-mode.el for setting superscript and subscript face > > > > > > > > >>>>> On Thu, 14 Jan 2021 17:19:54 +0100, Christopher Dimech > > > > >>>>> said: > > > > > > > > Christopher> I am having a problem introducing the > > > > tex-font-lock-keywords > > > > Christopher> and get the superscript-subscript functionality to > > > > work. > > > > > > > > Show us what you tried, and people will help (although Iʼm not sure > > > > help-texinfo is the right place for this) > > > > > > > > Robert > > > > > > > > > > > > > > > > > >
Re: tex-mode.el for setting superscript and subscript face
I am confident that I would only need something like (defconst tex-font-lock-keywords (tex-font-lock-match-suscript (1 (tex-font-lock-suscript (match-beginning 0)) append))) "Default expressions to highlight in TeX modes.") But this gives me an error because of the numeric value 1 > Sent: Saturday, January 16, 2021 at 11:38 PM > From: "Christopher Dimech" > To: "Christopher Dimech" > Cc: "Robert Pluim" , "help-texinfo gnu" > > Subject: Re: tex-mode.el for setting superscript and subscript face > > I do nat think that I would need most of the contents in > tex-font-lock-keywords-* > > > Sent: Saturday, January 16, 2021 at 11:35 PM > > From: "Christopher Dimech" > > To: "Christopher Dimech" > > Cc: "Robert Pluim" , "help-texinfo gnu" > > > > Subject: Re: tex-mode.el for setting superscript and subscript face > > > > I am still trying to take only the minimal code for the superscript > > and subscript option from tex-font-lock-keywords-* > > > > > > > > > Sent: Friday, January 15, 2021 at 9:35 PM > > > From: "Christopher Dimech" > > > To: "Robert Pluim" > > > Cc: "help-texinfo gnu" > > > Subject: Re: tex-mode.el for setting superscript and subscript face > > > > > > Have tried using tex-font-lock-keywords-3. But tex-font-lock-keywords-2 > > > and tex-font-lock-keywords-1 seem to be doing too many things. I only > > > require the part where the superscripts and subscripts are shown in > > > smaller > > > font and placed at a different height level. > > > > > > (defconst tex-font-lock-keywords-3 > > > (append tex-font-lock-keywords-2 > > > '((tex-font-lock-match-suscript > > >(1 (tex-font-lock-suscript (match-beginning 0)) append)))) > > > "Experimental expressions to highlight in TeX modes.") > > > > > > > Sent: Friday, January 15, 2021 at 9:09 PM > > > > From: "Robert Pluim" > > > > To: "Christopher Dimech" > > > > Cc: "help-texinfo gnu" > > > > Subject: Re: tex-mode.el for setting superscript and subscript face > > > > > > > > >>>>> On Thu, 14 Jan 2021 17:19:54 +0100, Christopher Dimech > > > > >>>>> said: > > > > > > > > Christopher> I am having a problem introducing the > > > > tex-font-lock-keywords > > > > Christopher> and get the superscript-subscript functionality to > > > > work. > > > > > > > > Show us what you tried, and people will help (although Iʼm not sure > > > > help-texinfo is the right place for this) > > > > > > > > Robert > > > > > > > > > > > > > > > > > >
Re: tex-mode.el for setting superscript and subscript face
I do nat think that I would need most of the contents in tex-font-lock-keywords-* > Sent: Saturday, January 16, 2021 at 11:35 PM > From: "Christopher Dimech" > To: "Christopher Dimech" > Cc: "Robert Pluim" , "help-texinfo gnu" > > Subject: Re: tex-mode.el for setting superscript and subscript face > > I am still trying to take only the minimal code for the superscript > and subscript option from tex-font-lock-keywords-* > > > > > Sent: Friday, January 15, 2021 at 9:35 PM > > From: "Christopher Dimech" > > To: "Robert Pluim" > > Cc: "help-texinfo gnu" > > Subject: Re: tex-mode.el for setting superscript and subscript face > > > > Have tried using tex-font-lock-keywords-3. But tex-font-lock-keywords-2 > > and tex-font-lock-keywords-1 seem to be doing too many things. I only > > require the part where the superscripts and subscripts are shown in smaller > > font and placed at a different height level. > > > > (defconst tex-font-lock-keywords-3 > > (append tex-font-lock-keywords-2 > > '((tex-font-lock-match-suscript > > (1 (tex-font-lock-suscript (match-beginning 0)) append > > "Experimental expressions to highlight in TeX modes.") > > > > > Sent: Friday, January 15, 2021 at 9:09 PM > > > From: "Robert Pluim" > > > To: "Christopher Dimech" > > > Cc: "help-texinfo gnu" > > > Subject: Re: tex-mode.el for setting superscript and subscript face > > > > > > >>>>> On Thu, 14 Jan 2021 17:19:54 +0100, Christopher Dimech > > > >>>>> said: > > > > > > Christopher> I am having a problem introducing the > > > tex-font-lock-keywords > > > Christopher> and get the superscript-subscript functionality to work. > > > > > > Show us what you tried, and people will help (although Iʼm not sure > > > help-texinfo is the right place for this) > > > > > > Robert > > > > > > > > > > >
Re: tex-mode.el for setting superscript and subscript face
I am still trying to take only the minimal code for the superscript and subscript option from tex-font-lock-keywords-* > Sent: Friday, January 15, 2021 at 9:35 PM > From: "Christopher Dimech" > To: "Robert Pluim" > Cc: "help-texinfo gnu" > Subject: Re: tex-mode.el for setting superscript and subscript face > > Have tried using tex-font-lock-keywords-3. But tex-font-lock-keywords-2 > and tex-font-lock-keywords-1 seem to be doing too many things. I only > require the part where the superscripts and subscripts are shown in smaller > font and placed at a different height level. > > (defconst tex-font-lock-keywords-3 > (append tex-font-lock-keywords-2 > '((tex-font-lock-match-suscript >(1 (tex-font-lock-suscript (match-beginning 0)) append > "Experimental expressions to highlight in TeX modes.") > > > Sent: Friday, January 15, 2021 at 9:09 PM > > From: "Robert Pluim" > > To: "Christopher Dimech" > > Cc: "help-texinfo gnu" > > Subject: Re: tex-mode.el for setting superscript and subscript face > > > > >>>>> On Thu, 14 Jan 2021 17:19:54 +0100, Christopher Dimech > > >>>>> said: > > > > Christopher> I am having a problem introducing the > > tex-font-lock-keywords > > Christopher> and get the superscript-subscript functionality to work. > > > > Show us what you tried, and people will help (although Iʼm not sure > > help-texinfo is the right place for this) > > > > Robert > > > > > >
Re: tex-mode.el for setting superscript and subscript face
Have tried using tex-font-lock-keywords-3. But tex-font-lock-keywords-2 and tex-font-lock-keywords-1 seem to be doing too many things. I only require the part where the superscripts and subscripts are shown in smaller font and placed at a different height level. (defconst tex-font-lock-keywords-3 (append tex-font-lock-keywords-2 '((tex-font-lock-match-suscript (1 (tex-font-lock-suscript (match-beginning 0)) append "Experimental expressions to highlight in TeX modes.") > Sent: Friday, January 15, 2021 at 9:09 PM > From: "Robert Pluim" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: tex-mode.el for setting superscript and subscript face > > >>>>> On Thu, 14 Jan 2021 17:19:54 +0100, Christopher Dimech > >>>>> said: > > Christopher> I am having a problem introducing the tex-font-lock-keywords > Christopher> and get the superscript-subscript functionality to work. > > Show us what you tried, and people will help (although Iʼm not sure > help-texinfo is the right place for this) > > Robert > >
Re: tex-mode.el for setting superscript and subscript face
I am having a problem introducing the tex-font-lock-keywords
and get the superscript-subscript functionality to work.
> Sent: Thursday, January 14, 2021 at 10:34 PM
> From: "Robert Pluim"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: tex-mode.el for setting superscript and subscript face
>
> >>>>> On Thu, 14 Jan 2021 11:29:34 +0100, Christopher Dimech
> >>>>> said:
>
> Christopher> I am working on a minor mode that will use the superscipt
> and subscript
> Christopher> functionality for texinfo-mode.
>
> Well, itʼs easy enough to locate. lisp/tex-mode.el:646
>
> (defun tex-font-lock-match-suscript (limit)
> "Match subscript and superscript patterns up to LIMIT."
> (when (and tex-fontify-script
>(re-search-forward "[_^] *\\([^\n\\{}]\\|\
> \\([a-zA-Z@]+\\|[^ \t\n]\\)\\|\\({\\)\\)" limit t))
> (when (match-end 3)
> (let ((beg (match-beginning 3))
> (end (save-restriction
> (narrow-to-region (point-min) limit)
> (condition-case nil (scan-lists (point) 1 1) (error nil)
> (store-match-data (if end
> (list (match-beginning 0) end beg end)
> (list beg beg beg beg)
> t))
>
> (defconst tex-font-lock-keywords-3
> (append tex-font-lock-keywords-2
> '((tex-font-lock-match-suscript
>(1 (tex-font-lock-suscript (match-beginning 0)) append
> "Experimental expressions to highlight in TeX modes.")
>
>
Re: tex-mode.el for setting superscript and subscript face
I am working on a minor mode that will use the superscipt and subscript
functionality for texinfo-mode.
> Sent: Thursday, January 14, 2021 at 8:34 PM
> From: "Robert Pluim"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: tex-mode.el for setting superscript and subscript face
>
> >>>>> On Wed, 13 Jan 2021 23:19:02 +0100, Christopher Dimech
> >>>>> said:
>
> Christopher> I am trying to find the part of the code in tex-mode.el that
> recognises
> Christopher> the superscript parts "^{}" and the subscript part "_{}" so
> as to use
> Christopher> a different face.
>
> Why do you need the code?
>
> (defface superscript
> '((t :height tex-suscript-height)) ;; :raise 0.2
> "Face used for superscripts."
> :group 'tex)
> (defface subscript
> '((t :height tex-suscript-height)) ;; :raise -0.2
> "Face used for subscripts."
> :group 'tex)
>
> Robert
>
>
tex-mode.el for setting superscript and subscript face
I am trying to find the part of the code in tex-mode.el that recognises
the superscript parts "^{}" and the subscript part "_{}" so as to use
a different face.
Re: Unicode char @u8: not defined for Texinfo
Am having several lines as below and need help finding problems with the code.
l.1145: Unicode char @u8: not defined for Texinfo
Have also been trying to see how ii is undefined
(see the transcript file for additional information)pdfTeX warning (dest): name
{ii} has been referenced but does not exist, replaced by a fixed one
texi2pdf 03a-chmed-html.texi
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
(preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
(./03a-chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
Loading texinfo [version 2020-11-25.18]: pdf, fonts, glyphs, page headings,
tables, conditionals, indexing, sectioning, toc, environments, defuns, macros,
cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(/home/hagbard/01cuneus/tdr/libmacro/docuseg.mc.texi)
Overfull \hbox (8.53583pt too wide) detected at line 11
[]
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]
(/home/hagbard/01cuneus/tdr/03ch/03a-chmed-html.aux) [2]
(/home/hagbard/01cuneus/tdr/03ch/03a-chmed-html.toc) [-1]
(/home/hagbard/01cuneus/tdr/03ch/03a-chmed-html.toc)
(/home/hagbard/01cuneus/tdr/03ch/03a-chmed-html.toc) (History)
Overfull \hbox (4.44653pt too wide) in paragraph at lines 8--8
@texttt Copyright:[]|
Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7
@texttt Copyright:[]|
(3 @ Microseismic Analysis of the Central Mediterranean Region) [-2]
(./03b-chmed-igm.texi ) [1] [2] [3] [4] [5] [6] [7]
Overfull \hbox (8.53583pt too wide) detected at line 4
[]
[8] [9] [10] [11] [12]
Overfull \hbox (8.53583pt too wide) detected at line 4
[]
[13] [14] l.1144: Unicode char @u8: not defined for Texinfo
l.1145: Unicode char @u8: not defined for Texinfo
l.1145: Unicode char @u8: not defined for Texinfo
l.1191: Unicode char @u8: not defined for Texinfo
l.1191: Unicode char @u8: not defined for Texinfo
l.1192: Unicode char @u8: not defined for Texinfo
l.1197: Unicode char @u8: not defined for Texinfo
l.1197: Unicode char @u8: not defined for Texinfo
l.1205: Unicode char @u8: not defined for Texinfo
l.1205: Unicode char @u8: not defined for Texinfo [15]
l.1215: Unicode char @u8: not defined for Texinfo
l.1215: Unicode char @u8: not defined for Texinfo
l.1215: Unicode char @u8: not defined for Texinfo
l.1215: Unicode char @u8: not defined for Texinfo
l.1215: Unicode char @u8: not defined for Texinfo
l.1215: Unicode char @u8: not defined for Texinfo
l.1215: Unicode char @u8: not defined for Texinfo
l.1220: Unicode char @u8: not defined for Texinfo [16] (./03c-chmed-rfc.texi
[17]) [18] (CC By-Nc-Nd 4)
(/home/hagbard/01cuneus/freelic/latest/freelic-3.4/cc/by-nc-nd/by-nc-nd.texi
[19] [20]
(/home/hagbard/01cuneus/freelic/latest/freelic-3.4/cc/by-nc-nd/grant.texi
[21]) (/home/hagbard/01cuneus/freelic/latest/freelic-3.4/cc/by-nc-nd/orgts.texi
) (/home/hagbard/01cuneus/freelic/latest/freelic-3.4/cc/by-nc-nd/retain.texi
[22]) [23] [24] [25]) [26] )
(see the transcript file for additional information)pdfTeX warning (dest): name
{ii} has been referenced but does not exist, replaced by a fixed one
Output written on 03a-chmed-html.pdf (30 pages, 23529618 bytes).
Transcript written on 03a-chmed-html.log.
> Sent: Friday, January 08, 2021 at 2:04 AM
> From: "Christopher Dimech"
> To: "help-texinfo gnu"
> Subject: Unicode char @u8: not defined for Texinfo
>
> Am getting the following text when using texi2pdf. I cannot understand
> exactly
> what is producing the problem.the problem
>
> Unicode char @u8: not defined for Texinfo
>
>
> ---
>
> Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7
> @texttt Copyright:[]|
> (3 @ Microseismic Analysis of the Central Mediterranean Region) [-2] [1]
> [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]
> l.1142: Unicode char @u8: not defined for Texinfo
> l.1143: Unicode char @u8: not defined for Texinfo
> l.1143: Unicode char @u8: not defined for Texinfo [12]
> l.1189: Unicode char @u8: not defined for Texinfo
> l.1189: Unicode char @u8: not defined for Texinfo
> l.1190: Unicode char @u8: not defined for Texinfo
> l.1195: Unicode char @u8: not defined for Texinfo
> l.1195: Unicode char @u8: not defined for Texinfo
> l.1203: Unicode char @u8: not defined for Texinfo
> l.1203: Unicode char @u8: not defined for Texinfo [13]
> l.1213: Unicode char @u8: not defined for Texinfo
> l.1213: Unicode char @u8: not defined for Texinfo
> l.1213: Unicode char @u8: not defined for Texinfo
> l.1213: Unicode char @u8: not defined for Texinfo
> l.1213: Unicode char @u8: not defined for Texinfo
> l.1213: Unicode char @u8: not defined for Texinfo
> l.1213: Unicode char @u8: not defined for Texinfo
> l.12
float identifier has been already used
I made the following macro to display an image. I am encountering a problem
because when I want to display the image image a second time, the same float
identifier (name{igc03-sicl-circumambrg}) has been already used.
@macro igmSiclCircumambrg
@set fignm igc03-sicl-circumambrg [01]
@float Figure,igc03-sicl-circumambrg
@center @image{@value{igc03-path}/igc03-01-sicl-circumambrg,12cm,,,.png}
@paragraphindent 0
@caption{@strong{Sites of the 102 seismic stations in Sicily and in
its Circum-Ambient Regions for use in the microseismic analysis
effort.}}
@shortcaption{Sites of the 102 seismic stations in Sicily and in its
Circum-Ambient Regions for use in the microseismic analysis effort.}
@end float
@end macro
Comment lines inside a @macro
Is it problematic including comment lines inside a macro? @macro showAllChmedIgm @c Station Locations (Sicily and Circum-Ambient Region) @c Label: igc03-sicl-circumambrg [1] @igmSiclCircumambrg @end macro
Unicode char @u8: not defined for Texinfo
Am getting the following text when using texi2pdf. I cannot understand exactly what is producing the problem.the problem Unicode char @u8: not defined for Texinfo --- Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7 @texttt Copyright:[]| (3 @ Microseismic Analysis of the Central Mediterranean Region) [-2] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] l.1142: Unicode char @u8: not defined for Texinfo l.1143: Unicode char @u8: not defined for Texinfo l.1143: Unicode char @u8: not defined for Texinfo [12] l.1189: Unicode char @u8: not defined for Texinfo l.1189: Unicode char @u8: not defined for Texinfo l.1190: Unicode char @u8: not defined for Texinfo l.1195: Unicode char @u8: not defined for Texinfo l.1195: Unicode char @u8: not defined for Texinfo l.1203: Unicode char @u8: not defined for Texinfo l.1203: Unicode char @u8: not defined for Texinfo [13] l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1218: Unicode char @u8: not defined for Texinfo [14] (./03c-chmed-rfc.texi [15] [16] [17]) [18] (CC By-Nc-Nd 4) (/home/hagbard/01cuneus/freelic/latest/freelic-3.4/cc/by-nc-nd/by-nc-nd.texi [19] [20] - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
warning: node `terminal-colour-node' unreferenced
I am using makeinfo to generate my info file. What does the following mean makeinfo gungadin-abbrev-usergd.texi gungadin-abbrev-usergd.texi:285: warning: node `terminal-colour-node' unreferenced I put the node in the detailed menu, and then defined it later in the section * terminal-colour-node::Colour Configuration for Terminal Sessions @node bash-resor-config-node @chapter Bash Resource Configuration @node terminal-colour-node @section Colour Configuration for Terminal Sessions I do not get any warnings about the other nodes similarly defined.
Texinfo Development Version and texinfo.texi
When installing the Texinfo Development version, one customarily also gets the latest texinfo.tex macro file. Currently I fut the macro-file in the directory of the master tex file. What would be a more permanent solution than having to copy the file this local way. - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
Re: Latest Development Version - @image with @value
> Sent: Saturday, December 05, 2020 at 8:06 AM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> On Sat, Dec 05, 2020 at 03:31:19AM +0100, Christopher Dimech wrote:
> > I often end up with may @ifset and @ifclear in my documents.
> > Is it acceptable to call the following command? It does work
> > as expected.
> >
> > @inlineifset{igrank-1, @set imgpth /home/hagbard}
> >
> > imgpth: @value{imgpth}
>
> Yes, that looks fine. You could also do
>
> @ifset igrank-1
> @set imgpth /home/hagbard
> @end ifset
Wonderful. Was using @ifset but at times using @inlineifset
is more convenient, whilst keeping initialisations compact.
This is most useful when setting up images (e.g. for the pdf
and html, where two files could be used).
Re: Latest Development Version - @image with @value
> Sent: Saturday, December 05, 2020 at 8:03 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 11:20:47PM +0100, Christopher Dimech wrote: > > Understood. It would be extremely helpful to users trying to test or check > > the development version to put a remark about /doc/texinfo.tex in the > > section > > "Getting a Copy of the Git Repository". > > I think it is clear if you say to a user, "that issue is fixed in > the development version in git", then they should know to look in git, > not on the website for versions released for users. I understand the scheme now, but is far from obvious to me. You could simplify the following page, with a short categorisation and description of the whole working scheme https://www.gnu.org/software/texinfo/ start === TEXINFO === Texinfo is the official documentation format of the GNU project. It is used by many non-GNU projects as well. Texinfo uses a single source file to produce output in a number of formats, both online and printed (DVI, HTML, Info, PDF, XML, etc.). This means that instead of writing different documents for online information and another for a printed manual, you need write only one document. And when the work is revised, you need revise only that one document. The Texinfo system is well-integrated with GNU Emacs. Official Releases = Download the latest official version (also on all GNU mirrors). Older releases are also available. Get the latest version of the texinfo.tex macro file. The macro file updates the latest official release before the next full Texinfo release is made. The file is used for converting Texinfo source to DVI or PDF files for printing and viewing, using the TeX typesetting system. Because the file is updated much more frequently; ) please use the latest version. The Development Version === You can browse and get a copy of the Development Version of Texinfo using the Git Repository. The latest development version of the texinfo.tex macro file can be found in the directory "doc" of the Texinfo development source tree. Texinfo Manual and Reference Card = The Texinfo manual and standalone Info reader manual from the latest official release, in various formats. See the GNU documentation page for manuals for other GNU packages. The Texinfo reference card formatted for letter-size paper (four landscape pages) and for A4-size paper. Texinfo Project === Texinfo project page The NEWS file listing notable changes by release, the ChangeLog file detailing all changes, and the TODO file with future projects large and small, awaiting volunteers. Pretests If available, the latest pretest. Pretests are inherently unstable. Please try them and report problems—that's why they are done, so the official release will be as reliable as it can be. === MAILING LISTS ... etc ===
Re: Latest Development Version - @image with @value
I often end up with may @ifset and @ifclear in my documents.
Is it acceptable to call the following command? It does work
as expected.
@inlineifset{igrank-1, @set imgpth /home/hagbard}
imgpth: @value{imgpth}
> Sent: Saturday, December 05, 2020 at 12:30 AM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "Gavin Smith" , "help-texinfo gnu"
>
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 11:43:09PM +0100, Christopher Dimech wrote:
> > Fantastic. Things age working now. texinfo.tex is mentioned in the README
> > file.
> >
> > There are three files README, INSTALL, INSTALL.generic. When reading them,
> > they continue
> > referring around between themselves.
>
> The INSTALL.generic is "out of our control" it is the generic
> INSTALL file for autoconf/automake based packages. So we add
> a specific INSTALL file for the texinfo specifics in link with
> installing.
>
> > Can there be just one README (otherwise have just one INSTALL file) with
> > abbreviated
> > set of instructions of typical installation, at the beginning?
>
> I am not that convinced that it is a good idea. The reference to
> INSTALL appears at the beginning of the README and I think that INSTALL*
> are best separate as otherwise the INSTALL specific parts would get in the
> way of having a short README. As I said above, the INSTALL.generic is
> outside of our control, which makes the only real option merging the
> specific INSTALL in the README.
>
> > Thank you both for bearing with me. But it was not so clear and quick
> > about what exactly one should do when trying development versions.
>
> It is indeed not clear nor quick.
>
> It seems to me that README-hacking contains most of the information
> (though not about building in a different directory from the source),
> and then the INSTALL file. It is a bit scattered, but the problem is
> that different persons will not need the same information depending on
> where they come from and need to do (from a release, the developpment
> source, testing or installing). Also the overall build system is not
> simple, there is an intrinsic complexity that we can't really remove by
> instructions (the whole autoconf/automake/gettext, with two translated
> sets, and additionally some Makefile parts being generated).
>
> It is not so clear to me what/if we need to add more information, people
> testing from the development tree are very few, answering to questions
> by mail could be more efficient than trying to document everything.
>
> That being said, if you have specific ideas of changes to the files, do
> not hesitate to propose, in particular in the form of patches.
>
> >
>
> In general there is also a need to run
> ./autogen.sh
> in the source thee before going into the build directory.
>
> >
> > % mkdir build
> > % cd build
> > % srcdir/configure [options] [target]
> > % make
> > % make install
> > % cp srcdir/doc/texinfo.tex workdir
> >
> > Where workdir is the directory of your main Texinfo input file.
> >
> >
> >
> >
> > > Sent: Friday, December 04, 2020 at 10:53 PM
> > > From: "Patrice Dumas"
> > > To: "Christopher Dimech"
> > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > >
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Fri, Dec 04, 2020 at 10:46:44PM +0100, Christopher Dimech wrote:
> > > > > Sent: Friday, December 04, 2020 at 10:30 PM
> > > > > From: "Patrice Dumas"
> > > > > To: "Christopher Dimech"
> > > > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > > > >
> > > > > Subject: Re: Latest Development Version - @image with @value
> > > > >
> > > > > On Fri, Dec 04, 2020 at 10:22:34PM +0100, Christopher Dimech wrote:
> > > > > >
> > > > > > > Sent: Friday, December 04, 2020 at 10:17 PM
> > > > > > > From: "Patrice Dumas"
> > > > > > > To: "Christopher Dimech"
> > > > > > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > > > > > >
> > > > > > > Subject: Re: Latest Development Version - @image with @value
> > > > > > >
> > > > > > > On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech
> > > > > > > w
Re: Latest Development Version - @image with @value
> Sent: Saturday, December 05, 2020 at 12:30 AM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 11:43:09PM +0100, Christopher Dimech wrote: > > Fantastic. Things age working now. texinfo.tex is mentioned in the README > > file. > > > > There are three files README, INSTALL, INSTALL.generic. When reading them, > > they continue > > referring around between themselves. > > The INSTALL.generic is "out of our control" it is the generic > INSTALL file for autoconf/automake based packages. So we add > a specific INSTALL file for the texinfo specifics in link with > installing. > > > Can there be just one README (otherwise have just one INSTALL file) with > > abbreviated > > set of instructions of typical installation, at the beginning? > > I am not that convinced that it is a good idea. The reference to > INSTALL appears at the beginning of the README and I think that INSTALL* > are best separate as otherwise the INSTALL specific parts would get in the > way of having a short README. As I said above, the INSTALL.generic is > outside of our control, which makes the only real option merging the > specific INSTALL in the README. > > > Thank you both for bearing with me. But it was not so clear and quick > > about what exactly one should do when trying development versions. > > It is indeed not clear nor quick. So we agree > It seems to me that README-hacking contains most of the information > (though not about building in a different directory from the source), > and then the INSTALL file. It is a bit scattered, but the problem is > that different persons will not need the same information depending on > where they come from and need to do (from a release, the developpment > source, testing or installing). Also the overall build system is not > simple, there is an intrinsic complexity that we can't really remove by > instructions (the whole autoconf/automake/gettext, with two translated > sets, and additionally some Makefile parts being generated). And README-hacking. Fuckin hell!!! And then, it does not contain all the necessary information. > It is not so clear to me what/if we need to add more information, people > testing from the development tree are very few, answering to questions > by mail could be more efficient than trying to document everything. I could have got on your nerves, because everything was good on your side. > That being said, if you have specific ideas of changes to the files, do > not hesitate to propose, in particular in the form of patches. Perhaps a document describing what you have said to me (in some text file). There were similar problems with Gcc in the past, which were eventually sorted out. Used to test some very dodgy versions as new standards were being implemented. I am in the process of releasing the Gunga Din Software, that is focused on setting a Gnu System for new users of Gnu-Like. Will include abbreviated versions of Gnu User Guide and Gnu Admin Guide. Could write something there. But have got to spend some time getting my head around how it would look like, and that the description works for those who need to understand what to do so they can get back rapidly to their own work - that's my focus. You could go through it and decide on whether to include some parts. Regards Christopher > > > > In general there is also a need to run > ./autogen.sh > in the source thee before going into the build directory. Yes, that's what I had to do. We can write some of these scenarios vith typical examples. > > > > % mkdir build > > % cd build > > % srcdir/configure [options] [target] > > % make > > % make install > > % cp srcdir/doc/texinfo.tex workdir > > > > Where workdir is the directory of your main Texinfo input file. > > > > > > > > > > > Sent: Friday, December 04, 2020 at 10:53 PM > > > From: "Patrice Dumas" > > > To: "Christopher Dimech" > > > Cc: "Gavin Smith" , "help-texinfo gnu" > > > > > > Subject: Re: Latest Development Version - @image with @value > > > > > > On Fri, Dec 04, 2020 at 10:46:44PM +0100, Christopher Dimech wrote: > > > > > Sent: Friday, December 04, 2020 at 10:30 PM > > > > > From: "Patrice Dumas" > > > > > To: "Christopher Dimech" > > > > > Cc: "Gavin Smith" , "help-texinfo gnu" > > > > > > > > > > Subject: Re: Latest Devel
Re: Latest Development Version - @image with @value
Fantastic. Things age working now. texinfo.tex is mentioned in the README
file.
There are three files README, INSTALL, INSTALL.generic. When reading them,
they continue
referring around between themselves.
Can there be just one README (otherwise have just one INSTALL file) with
abbreviated
set of instructions of typical installation, at the beginning?
Thank you both for bearing with me. But it was not so clear and quick
about what exactly one should do when trying development versions.
% mkdir build
% cd build
% srcdir/configure [options] [target]
% make
% make install
% cp srcdir/doc/texinfo.tex workdir
Where workdir is the directory of your main Texinfo input file.
> Sent: Friday, December 04, 2020 at 10:53 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "Gavin Smith" , "help-texinfo gnu"
>
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 10:46:44PM +0100, Christopher Dimech wrote:
> > > Sent: Friday, December 04, 2020 at 10:30 PM
> > > From: "Patrice Dumas"
> > > To: "Christopher Dimech"
> > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > >
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Fri, Dec 04, 2020 at 10:22:34PM +0100, Christopher Dimech wrote:
> > > >
> > > > > Sent: Friday, December 04, 2020 at 10:17 PM
> > > > > From: "Patrice Dumas"
> > > > > To: "Christopher Dimech"
> > > > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > > > >
> > > > > Subject: Re: Latest Development Version - @image with @value
> > > > >
> > > > > On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech wrote:
> > > > > > I done the whole thing again, however the version is still showing
> > > > > >
> > > > > > Loading texinfo [version 2020-10-24.12]
> > > > > >
> > > > > > hagbard@fuckup:
> > > > > > + ~/01cuneus/tdr/03ch
> > > > > > ls -lrt /usr/local/bin/texi2pdf
> > > > > > -rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
> > > > > >
> > > > > > hagbard@fuckup:
> > > > > > + ~/01cuneus/tdr/03ch
> > > > > > ls -lrt
> > > > > > -rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
> > > > >
> > > > > You can look at the beginning of the file to check that it is indeed
> > > > > the latest one. If it is not used, it would be very strange.
> > > >
> > > > I see texinfo.tex is saying
> > > > \def\texinfoversion{2020-10-24.12}
> > >
> > > Then it is not the one from git, the one from git has
> > > \def\texinfoversion{2020-11-14.10}
> >
> > I did a git clone. Where do you put the file? Apologies, but I cannot
> > determine
> > where texinfo.tex is located.
>
> It is in texinfo/doc/texinfo.tex
>
> --
> Pat
>
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 10:56 PM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 10:37:56PM +0100, Christopher Dimech wrote: > > > > That could be it. I got that from the website where it says > > "latest texinfo.tex macro file" > > This location is indeed used to do releases of texinfo.tex before the > whole texinfo package release, but it is still in general not as fresh > as the git file, especially when the changes are still being tested. > Understood. It would be extremely helpful to users trying to test or check the development version to put a remark about /doc/texinfo.tex in the section "Getting a Copy of the Git Repository". https://savannah.gnu.org/git/?group=texinfo > -- > Pat > >
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 10:30 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "Gavin Smith" , "help-texinfo gnu"
>
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 10:22:34PM +0100, Christopher Dimech wrote:
> >
> > > Sent: Friday, December 04, 2020 at 10:17 PM
> > > From: "Patrice Dumas"
> > > To: "Christopher Dimech"
> > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > >
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech wrote:
> > > > I done the whole thing again, however the version is still showing
> > > >
> > > > Loading texinfo [version 2020-10-24.12]
> > > >
> > > > hagbard@fuckup:
> > > > + ~/01cuneus/tdr/03ch
> > > > ls -lrt /usr/local/bin/texi2pdf
> > > > -rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
> > > >
> > > > hagbard@fuckup:
> > > > + ~/01cuneus/tdr/03ch
> > > > ls -lrt
> > > > -rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
> > >
> > > You can look at the beginning of the file to check that it is indeed
> > > the latest one. If it is not used, it would be very strange.
> >
> > I see texinfo.tex is saying
> > \def\texinfoversion{2020-10-24.12}
>
> Then it is not the one from git, the one from git has
> \def\texinfoversion{2020-11-14.10}
I did a git clone. Where do you put the file? Apologies, but I cannot
determine
where texinfo.tex is located.
> > hagbard@fuckup:
> > + ~/01cuneus/tdr/03ch
> > kpsewhich --expand-var='$TEXINPUTS'
> > .:{/home/hagbard/.texmf-config,/home/hagbard/.texmf-var,/home/hagbard/texmf,/etc/texmf,!!/var/lib/texmf,!!/usr/local/share/texmf,!!/usr/share/texmf,!!/usr/share/texlive/texmf-dist}/tex/{kpsewhich,generic,}//
>
> You have the standard path.
>
> --
> Pat
>
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 10:30 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 10:22:34PM +0100, Christopher Dimech wrote:
> >
> > > Sent: Friday, December 04, 2020 at 10:17 PM
> > > From: "Patrice Dumas"
> > > To: "Christopher Dimech"
> > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > >
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech wrote:
> > > > I done the whole thing again, however the version is still showing
> > > >
> > > > Loading texinfo [version 2020-10-24.12]
> > > >
> > > > hagbard@fuckup:
> > > > + ~/01cuneus/tdr/03ch
> > > > ls -lrt /usr/local/bin/texi2pdf
> > > > -rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
> > > >
> > > > hagbard@fuckup:
> > > > + ~/01cuneus/tdr/03ch
> > > > ls -lrt
> > > > -rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
> > >
> > > You can look at the beginning of the file to check that it is indeed
> > > the latest one. If it is not used, it would be very strange.
> >
> > I see texinfo.tex is saying
> > \def\texinfoversion{2020-10-24.12}
>
> Then it is not the one from git, the one from git has
> \def\texinfoversion{2020-11-14.10}
That could be it. I got that from the website where it says
"latest texinfo.tex macro file"
> > hagbard@fuckup:
> > + ~/01cuneus/tdr/03ch
> > kpsewhich --expand-var='$TEXINPUTS'
> > .:{/home/hagbard/.texmf-config,/home/hagbard/.texmf-var,/home/hagbard/texmf,/etc/texmf,!!/var/lib/texmf,!!/usr/local/share/texmf,!!/usr/share/texmf,!!/usr/share/texlive/texmf-dist}/tex/{kpsewhich,generic,}//
>
> You have the standard path.
>
> --
> Pat
>
>
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 10:17 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "Gavin Smith" , "help-texinfo gnu"
>
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech wrote:
> > I done the whole thing again, however the version is still showing
> >
> > Loading texinfo [version 2020-10-24.12]
> >
> > hagbard@fuckup:
> > + ~/01cuneus/tdr/03ch
> > ls -lrt /usr/local/bin/texi2pdf
> > -rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
> >
> > hagbard@fuckup:
> > + ~/01cuneus/tdr/03ch
> > ls -lrt
> > -rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
>
> You can look at the beginning of the file to check that it is indeed
> the latest one. If it is not used, it would be very strange.
I see texinfo.tex is saying
\def\texinfoversion{2020-10-24.12}
> An alternative possibility, but I doubt it a bit is if you have a non
> standard paths setting for TeX.
>
> I think that you can check your path with
>
> kpsewhich -show-path=tex
hagbard@fuckup:
+ ~/01cuneus/tdr/03ch
kpsewhich -show-path=tex
.:/home/hagbard/.texmf-config/tex/kpsewhich//:/home/hagbard/.texmf-var/tex/kpsewhich//:/home/hagbard/texmf/tex/kpsewhich//:/etc/texmf/tex/kpsewhich//:!!/var/lib/texmf/tex/kpsewhich//:!!/usr/local/share/texmf/tex/kpsewhich//:!!/usr/share/texmf/tex/kpsewhich//:!!/usr/share/texlive/texmf-dist/tex/kpsewhich//:/home/hagbard/.texmf-config/tex/generic//:/home/hagbard/.texmf-var/tex/generic//:/home/hagbard/texmf/tex/generic//:/etc/texmf/tex/generic//:!!/var/lib/texmf/tex/generic//:!!/usr/local/share/texmf/tex/generic//:!!/usr/share/texmf/tex/generic//:!!/usr/share/texlive/texmf-dist/tex/generic//:/home/hagbard/.texmf-config/tex///:/home/hagbard/.texmf-var/tex///:/home/hagbard/texmf/tex///:/etc/texmf/tex///:!!/var/lib/texmf/tex///:!!/usr/local/share/texmf/tex///:!!/usr/share/texmf/tex///:!!/usr/share/texlive/texmf-dist/tex///
> or
>
> kpsewhich --expand-var='$TEXINPUTS'
hagbard@fuckup:
+ ~/01cuneus/tdr/03ch
kpsewhich --expand-var='$TEXINPUTS'
.:{/home/hagbard/.texmf-config,/home/hagbard/.texmf-var,/home/hagbard/texmf,/etc/texmf,!!/var/lib/texmf,!!/usr/local/share/texmf,!!/usr/share/texmf,!!/usr/share/texlive/texmf-dist}/tex/{kpsewhich,generic,}//
>
> >
> >
> >
> > > Sent: Friday, December 04, 2020 at 6:28 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > You have to copy texinfo.tex manually to where it will be used.
> > > Running "make install" is not enough.
> > >
> > > On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> > > >
> > > > Have just re-downloaded the file and put in the directory
> > > > ~/01cuneus/tdr/03ch
> > > > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> > > >
> > > > To install the new version I ran gendocs.sh, then the usual configure
> > > > etc.
> > > >
> > > > I can see that the programs were updated in /usr/local/bin/
> > > >
> > > > Problem remains
> > > > C*
> > > >
> > > > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > > > From: "Gavin Smith"
> > > > > To: "Christopher Dimech"
> > > > > Cc: "help-texinfo gnu"
> > > > > Subject: Re: Latest Development Version - @image with @value
> > > > >
> > > > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > > > Using the following does not work for me. Do I require some setup?
> > > > > > Have
> > > > > > also got the latest texinfo.tex
> > > > > >
> > > > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > > > >
> > > > > > First call to @image works, the second fails.
> > > > >
> > > > > Well, I tried @image with @value with an absolute directory
> > > > > name, and it worked. What output are you getting from TeX? Are you
> > > > > sure the latest texinfo.tex is being read?
> > > > >
> > > > >
> > >
> >
>
Re: Latest Development Version - @image with @value
I am still seeing version 2020-10-24.12 which you say is not the latest one Loading texinfo [version 2020-10-24.12] Have removed the old version from synaptic, and re-installed the one I got from the git repositor, downloaded texinfo.tex, and put that in the directories where I have the .texi files. And the problem remains. How is it that the installation from git still shows version 2020-10-24.12? > Sent: Friday, December 04, 2020 at 8:51 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 08:49:55PM +0100, Christopher Dimech wrote: > > Do you still think that the problem is with texinfo.tex? > > No, you just haven't installed the file properly. > > If you don't know where to copy the file, then putting it in the > same directory as your main Texinfo input file should work. >
Re: Latest Development Version - @image with @value
I have tried that. Now I put the file in all directories where I have the all the texi files. Could you send me the file, so I can put the one you send. See what happens. > Sent: Friday, December 04, 2020 at 8:51 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 08:49:55PM +0100, Christopher Dimech wrote: > > Do you still think that the problem is with texinfo.tex? > > No, you just haven't installed the file properly. > > If you don't know where to copy the file, then putting it in the > same directory as your main Texinfo input file should work. >
Re: Latest Development Version - @image with @value
Do you still think that the problem is with texinfo.tex?
> Sent: Friday, December 04, 2020 at 6:28 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> You have to copy texinfo.tex manually to where it will be used.
> Running "make install" is not enough.
>
> On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> >
> > Have just re-downloaded the file and put in the directory
> > ~/01cuneus/tdr/03ch
> > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> >
> > To install the new version I ran gendocs.sh, then the usual configure etc.
> >
> > I can see that the programs were updated in /usr/local/bin/
> >
> > Problem remains
> > C*
> >
> > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > Using the following does not work for me. Do I require some setup?
> > > > Have
> > > > also got the latest texinfo.tex
> > > >
> > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > >
> > > > First call to @image works, the second fails.
> > >
> > > Well, I tried @image with @value with an absolute directory
> > > name, and it worked. What output are you getting from TeX? Are you
> > > sure the latest texinfo.tex is being read?
> > >
> > >
>
Re: Latest Development Version - @image with @value
I done the whole thing again, however the version is still showing
Loading texinfo [version 2020-10-24.12]
hagbard@fuckup:
+ ~/01cuneus/tdr/03ch
ls -lrt /usr/local/bin/texi2pdf
-rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
hagbard@fuckup:
+ ~/01cuneus/tdr/03ch
ls -lrt
-rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
> Sent: Friday, December 04, 2020 at 6:28 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> You have to copy texinfo.tex manually to where it will be used.
> Running "make install" is not enough.
>
> On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> >
> > Have just re-downloaded the file and put in the directory
> > ~/01cuneus/tdr/03ch
> > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> >
> > To install the new version I ran gendocs.sh, then the usual configure etc.
> >
> > I can see that the programs were updated in /usr/local/bin/
> >
> > Problem remains
> > C*
> >
> > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > Using the following does not work for me. Do I require some setup?
> > > > Have
> > > > also got the latest texinfo.tex
> > > >
> > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > >
> > > > First call to @image works, the second fails.
> > >
> > > Well, I tried @image with @value with an absolute directory
> > > name, and it worked. What output are you getting from TeX? Are you
> > > sure the latest texinfo.tex is being read?
> > >
> > >
>
Re: Latest Development Version - @image with @value
Do not usually run configure in the same directory.
I make a build directory, then run configure from there.
> Sent: Friday, December 04, 2020 at 6:28 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> You have to copy texinfo.tex manually to where it will be used.
> Running "make install" is not enough.
>
> On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> >
> > Have just re-downloaded the file and put in the directory
> > ~/01cuneus/tdr/03ch
> > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> >
> > To install the new version I ran gendocs.sh, then the usual configure etc.
> >
> > I can see that the programs were updated in /usr/local/bin/
> >
> > Problem remains
> > C*
> >
> > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > Using the following does not work for me. Do I require some setup?
> > > > Have
> > > > also got the latest texinfo.tex
> > > >
> > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > >
> > > > First call to @image works, the second fails.
> > >
> > > Well, I tried @image with @value with an absolute directory
> > > name, and it worked. What output are you getting from TeX? Are you
> > > sure the latest texinfo.tex is being read?
> > >
> > >
>
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 6:28 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> You have to copy texinfo.tex manually to where it will be used.
> Running "make install" is not enough.
Yes, I have done that. But you have said that I got texinfo [version
2020-10-24.12
using "git clone https://git.savannah.gnu.org/git/texinfo.git";.
Will install again, by doing another git clone.
> On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> >
> > Have just re-downloaded the file and put in the directory
> > ~/01cuneus/tdr/03ch
> > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> >
> > To install the new version I ran gendocs.sh, then the usual configure etc.
> >
> > I can see that the programs were updated in /usr/local/bin/
> >
> > Problem remains
> > C*
> >
> > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > Using the following does not work for me. Do I require some setup?
> > > > Have
> > > > also got the latest texinfo.tex
> > > >
> > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > >
> > > > First call to @image works, the second fails.
> > >
> > > Well, I tried @image with @value with an absolute directory
> > > name, and it worked. What output are you getting from TeX? Are you
> > > sure the latest texinfo.tex is being read?
> > >
> > >
>
Re: Latest Development Version - @image with @value
This is what I have used git clone https://git.savannah.gnu.org/git/texinfo.git > Sent: Friday, December 04, 2020 at 6:16 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 05:57:41PM +0100, Christopher Dimech wrote: > > Let me check again. Any hints on how to know which one is being used? > > > > texi2pdf 03aCh-Chmed-html.texi > > This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) > > (preloaded format=pdfetex) > > restricted \write18 enabled. > > entering extended mode > > > > (./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex > > Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs, > > It's this line here. The latest version is 2020-11-25.18. >
Re: Latest Development Version - @image with @value
Have just re-downloaded the file and put in the directory ~/01cuneus/tdr/03ch
(where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
To install the new version I ran gendocs.sh, then the usual configure etc.
I can see that the programs were updated in /usr/local/bin/
Problem remains
C*
> Sent: Friday, December 04, 2020 at 5:45 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > Using the following does not work for me. Do I require some setup? Have
> > also got the latest texinfo.tex
> >
> > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> >
> > First call to @image works, the second fails.
>
> Well, I tried @image with @value with an absolute directory
> name, and it worked. What output are you getting from TeX? Are you
> sure the latest texinfo.tex is being read?
>
>
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 5:45 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > Using the following does not work for me. Do I require some setup? Have
> > also got the latest texinfo.tex
> >
> > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> >
> > First call to @image works, the second fails.
>
> Well, I tried @image with @value with an absolute directory
> name, and it worked. What output are you getting from TeX? Are you
> sure the latest texinfo.tex is being read?
Let me check again. Any hints on how to know which one is being used?
texi2pdf 03aCh-Chmed-html.texi
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
(preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
(./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(../LibMacro/DocuSeg.mc.texi)
./03aCh-Chmed-html.texi:121: TeX capacity exceeded, sorry [input stack size=500
0].
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
...
l.121 ...pter 3 Tuesday September 15@comma{} 2020}
./03aCh-Chmed-html.texi:121: ==> Fatal error occurred, no output PDF file prod
uced!
Transcript written on 03aCh-Chmed-html.log.
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
(preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
(./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(../LibMacro/DocuSeg.mc.texi)
./03aCh-Chmed-html.texi:121: TeX capacity exceeded, sorry [input stack size=500
0].
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
...
l.121 ...pter 3 Tuesday September 15@comma{} 2020}
./03aCh-Chmed-html.texi:121: ==> Fatal error occurred, no output PDF file prod
uced!
Transcript written on 03aCh-Chmed-html.log.
/usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
Re: Latest Development Version - @image with @value
Using the following does not work for me. Do I require some setup? Have
also got the latest texinfo.tex
@set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
@image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
@image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
First call to @image works, the second fails.
> Sent: Thursday, December 03, 2020 at 6:41 PM
> From: "Christopher Dimech"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @macro line continuation
>
> It looks like I installed correctly though
>
> hagbard@fuckup:
> + ~
> which texi2pdf
> /usr/local/bin/texi2pdf
>
> hagbard@fuckup:
> + ~
> ls -lrt /usr/local/bin/texi2pdf
> -rwxr-xr-x 1 root root 1246 Dec 3 07:52 /usr/local/bin/texi2pdf
>
>
> -
> Christopher Dimech
> General Administrator - Naiad Informatics - GNU Project (Geocomputation)
> - Geophysical Simulation
> - Geological Subsurface Mapping
> - Disaster Preparedness and Mitigation
> - Natural Resource Exploration and Production
> - Free Software Advocacy
>
>
> > Sent: Thursday, December 03, 2020 at 6:28 PM
> > From: "Christopher Dimech"
> > To: "help-texinfo gnu"
> > Subject: Latest Development Version - @macro line continuation
> >
> > I have installed the latest development version but seeing an error.
> >
> > Perhaps I did not install it properly?
> >
> > --- Source Code
> >
> > @macro TdrPage{titl, titlCn, subtitl, subtitlCn, date}
> >
> > @title @sc{\titl\ @* \titlCn\}
> > @subtitle \subtitl\
> > @subtitle \subtitlCn\
> >
> > @center @strong{Text}
> > @center Text
> > @center \date\
> > @author Christopher Dimech
> > @iftex
> > @page
> > @insertcopying
> > @end iftex
> >
> > @end macro
> >
> > @TdrPage{Microseismic Analysis of the, Central Mediterranean Region,,,
> > Chapter 3 Tuesday September 15@comma{} 2020}
> >
> > Errors ---
> >
> > texi2pdf 03aCh-Chmed-html.texi
> > This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
> > (preloaded format=pdfetex)
> > restricted \write18 enabled.
> > entering extended mode
> >
> > (./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
> > Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
> > page headings, tables, conditionals, indexing, sectioning, toc,
> > environments,
> > defuns, macros, cross references, insertions,
> > (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> > This is `epsf.tex' v2.7.4 <14 February 2011>
> > ) localization, formatting, and turning on texinfo input format.)
> > (../LibMacro/DocuSeg.mc.texi)
> > Runaway argument?
> > {
> > ./03aCh-Chmed-html.texi:119: Paragraph ended before @trim@ was complete.
> >
> >@par
> > ^^M
> > Chapter 3 Tuesday September 15@comma {} 2020
> > @eatspaces ...@expandafter @trim@ @expandafter {#1
> >}
> > ... Tuesday September 15@comma {} 2020}
> > @unskip @hfil
> > @centersub ...enalty @fi @line {@kern @leftskip #1
> > @kern @rightskip }
> > @\center ...{@hfil @ignorespaces #1@unskip @hfil }
> > @let @centersub @relax
> > ...
> > l.119 Chapter 3 Tuesday September 15@comma{} 2020}
> >
> > ./03aCh-Chmed-html.texi:119: Extra }, or forgotten @endgroup.
> > @centersub ...@kern @leftskip #1@kern @rightskip }
> >
> > @\center ...{@hfil @ignorespaces #1@unskip @hfil }
> > @let @centersub @relax
> > l.25 Chapter 3 Tuesday September 15@comma{} 2020}
> >
> > @scanmacro ...@eatspaces }@scantokens {#1@comment}
> >
> > l.119 Chapter 3 Tuesday September 15@comma{} 2020}
> >
> > [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2]
> > (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) [-1]
> > (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc)
> > (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) (History)
> > (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.aux)
> > Overfull \hbox (4.44653pt too wide) in paragraph at lines 8--8
> > @texttt Copyright:[]|
> >
> > Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7
> > @texttt Copyr
Re: Latest Development Version - @macro line continuation
It looks like I installed correctly though
hagbard@fuckup:
+ ~
which texi2pdf
/usr/local/bin/texi2pdf
hagbard@fuckup:
+ ~
ls -lrt /usr/local/bin/texi2pdf
-rwxr-xr-x 1 root root 1246 Dec 3 07:52 /usr/local/bin/texi2pdf
-
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Thursday, December 03, 2020 at 6:28 PM
> From: "Christopher Dimech"
> To: "help-texinfo gnu"
> Subject: Latest Development Version - @macro line continuation
>
> I have installed the latest development version but seeing an error.
>
> Perhaps I did not install it properly?
>
> --- Source Code
>
> @macro TdrPage{titl, titlCn, subtitl, subtitlCn, date}
>
> @title @sc{\titl\ @* \titlCn\}
> @subtitle \subtitl\
> @subtitle \subtitlCn\
>
> @center @strong{Text}
> @center Text
> @center \date\
> @author Christopher Dimech
> @iftex
> @page
> @insertcopying
> @end iftex
>
> @end macro
>
> @TdrPage{Microseismic Analysis of the, Central Mediterranean Region,,,
> Chapter 3 Tuesday September 15@comma{} 2020}
>
> Errors ---
>
> texi2pdf 03aCh-Chmed-html.texi
> This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
> (./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
> Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions,
> (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.)
> (../LibMacro/DocuSeg.mc.texi)
> Runaway argument?
> {
> ./03aCh-Chmed-html.texi:119: Paragraph ended before @trim@ was complete.
>
>@par
> ^^M
> Chapter 3 Tuesday September 15@comma {} 2020
> @eatspaces ...@expandafter @trim@ @expandafter {#1
>}
> ... Tuesday September 15@comma {} 2020}
> @unskip @hfil
> @centersub ...enalty @fi @line {@kern @leftskip #1
> @kern @rightskip }
> @\center ...{@hfil @ignorespaces #1@unskip @hfil }
> @let @centersub @relax
> ...
> l.119 Chapter 3 Tuesday September 15@comma{} 2020}
>
> ./03aCh-Chmed-html.texi:119: Extra }, or forgotten @endgroup.
> @centersub ...@kern @leftskip #1@kern @rightskip }
>
> @\center ...{@hfil @ignorespaces #1@unskip @hfil }
> @let @centersub @relax
> l.25 Chapter 3 Tuesday September 15@comma{} 2020}
>
> @scanmacro ...@eatspaces }@scantokens {#1@comment}
>
> l.119 Chapter 3 Tuesday September 15@comma{} 2020}
>
> [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2]
> (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) [-1]
> (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc)
> (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) (History)
> (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.aux)
> Overfull \hbox (4.44653pt too wide) in paragraph at lines 8--8
> @texttt Copyright:[]|
>
> Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7
> @texttt Copyright:[]|
> (3 @ Microseismic Analysis of the Central Mediterranean Region) [-2] [1] )
> (see the transcript file for additional information)pdfTeX warning (dest):
> name
> {ii} has been referenced but does not exist, replaced by a fixed one
>
> hare/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb> exlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmcsc10.pfb> e/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi10.pfb> f-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb> /fonts/type1/public/amsfonts/cm/cmr10.pfb> type1/public/amsfonts/cm/cmsl10.pfb> public/amsfonts/cm/cmtt10.pfb>
> Output written on 03aCh-Chmed-html.pdf (5 pages, 95768 bytes).
> Transcript written on 03aCh-Chmed-html.log.
> /usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
>
>
>
>
Latest Development Version - @macro line continuation
I have installed the latest development version but seeing an error.
Perhaps I did not install it properly?
--- Source Code
@macro TdrPage{titl, titlCn, subtitl, subtitlCn, date}
@title @sc{\titl\ @* \titlCn\}
@subtitle \subtitl\
@subtitle \subtitlCn\
@center @strong{Text}
@center Text
@center \date\
@author Christopher Dimech
@iftex
@page
@insertcopying
@end iftex
@end macro
@TdrPage{Microseismic Analysis of the, Central Mediterranean Region,,,
Chapter 3 Tuesday September 15@comma{} 2020}
Errors ---
texi2pdf 03aCh-Chmed-html.texi
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
(preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
(./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(../LibMacro/DocuSeg.mc.texi)
Runaway argument?
{
./03aCh-Chmed-html.texi:119: Paragraph ended before @trim@ was complete.
@par
^^M
Chapter 3 Tuesday September 15@comma {} 2020
@eatspaces ...@expandafter @trim@ @expandafter {#1
}
... Tuesday September 15@comma {} 2020}
@unskip @hfil
@centersub ...enalty @fi @line {@kern @leftskip #1
@kern @rightskip }
@\center ...{@hfil @ignorespaces #1@unskip @hfil }
@let @centersub @relax
...
l.119 Chapter 3 Tuesday September 15@comma{} 2020}
./03aCh-Chmed-html.texi:119: Extra }, or forgotten @endgroup.
@centersub ...@kern @leftskip #1@kern @rightskip }
@\center ...{@hfil @ignorespaces #1@unskip @hfil }
@let @centersub @relax
l.25 Chapter 3 Tuesday September 15@comma{} 2020}
@scanmacro ...@eatspaces }@scantokens {#1@comment}
l.119 Chapter 3 Tuesday September 15@comma{} 2020}
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2]
(/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) [-1]
(/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc)
(/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) (History)
(/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.aux)
Overfull \hbox (4.44653pt too wide) in paragraph at lines 8--8
@texttt Copyright:[]|
Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7
@texttt Copyright:[]|
(3 @ Microseismic Analysis of the Central Mediterranean Region) [-2] [1] )
(see the transcript file for additional information)pdfTeX warning (dest): name
{ii} has been referenced but does not exist, replaced by a fixed one
Output written on 03aCh-Chmed-html.pdf (5 pages, 95768 bytes).
Transcript written on 03aCh-Chmed-html.log.
/usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
@float
What do you think about having floating material? Regards Christopher
Re: Numbering Menu Items in html output
> Sent: Saturday, November 28, 2020 at 7:13 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Numbering Menu Items in html output > > On Sat, Nov 28, 2020 at 06:27:06PM +0100, Christopher Dimech wrote: > > > On Sat, Nov 28, 2020 at 1:48 PM Christopher Dimech wrote: > > > > > > > > Have asked Eli to number the menu items for the "Emacs Lisp Reference > > > > Manual" > > > > who informed me that the menu gets unnumbered by Texinfo. > > > > > > > > Have done a test and can confirm. > > > > > > > > If one is using a Web Browser, it is much quicker to find if > > > > you say "See 10.4 Backquote". You just scroll to 10, then to > > > > four, rather than by a Brain Regexp. > > > > > > > > Regards > > > > Christopher > > If you are referring to numbering menus in Info output then this cannot > be changed, as Info reading programs need menu entries to begin with "* ", > not with a number. I am referring to html when using a web browser. See https://www.gnu.org/software/emacs/manual/html_node/elisp/index.html @chapter, @section, @sub.. do get numbered. I was introspecting the notion that the numbering is introduced according to what is customarily done when numbering chapters and sections. Eli mentioned that @menu is generated automatically. We want to avoid writing the numbers manually.
Re: Numbering Menu Items in html output
> Sent: Saturday, November 28, 2020 at 6:20 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" > Subject: Re: Numbering Menu Items in html output > > Please send any queries to the public mailing lists > bug-texi...@gnu.org or help-texinfo@gnu.org. Missed the mailing list. Now I include it > On Sat, Nov 28, 2020 at 1:48 PM Christopher Dimech wrote: > > > > Have asked Eli to number the menu items for the "Emacs Lisp Reference > > Manual" > > who informed me that the menu gets unnumbered by Texinfo. > > > > Have done a test and can confirm. > > > > If one is using a Web Browser, it is much quicker to find if > > you say "See 10.4 Backquote". You just scroll to 10, then to > > four, rather than by a Brain Regexp. > > > > Regards > > Christopher > > > > > > > > >
Re: Copying image files for HTML output
For when are you planning the next release? > Sent: Saturday, November 28, 2020 at 10:36 AM > From: "Gavin Smith" > To: "Patrice Dumas" , "bug-texinfo gnu" > > Subject: Copying image files for HTML output > > On Thu, Nov 19, 2020 at 11:10:55PM +0100, Patrice Dumas wrote: > > I think that if the path does not starts with . or .. or is an absolute > > path, it would make sense > > 1) to search in include directories (I think that the current directory > > is always in front of of the search path) > > 2) to check if the directories and image file exist in the destination > > directory and if not copy the file > > > > For point 2), there could be a customization variable to prevent the > > copy, that would be off in the default case, but can be turned on for > > the users who want backward compatibility or do something else by > > themselves, for instance use links. > > I think it's a good idea but I think it should be left until after the > next release to implement, as I suspect there will be enough issues from > other changes to deal with. > >
Re: Copying image files for HTML output
> Sent: Saturday, November 28, 2020 at 10:36 AM > From: "Gavin Smith" > To: "Patrice Dumas" , "bug-texinfo gnu" > > Subject: Copying image files for HTML output > > On Thu, Nov 19, 2020 at 11:10:55PM +0100, Patrice Dumas wrote: > > I think that if the path does not starts with . or .. or is an absolute > > path, it would make sense > > 1) to search in include directories (I think that the current directory > > is always in front of of the search path) > > 2) to check if the directories and image file exist in the destination > > directory and if not copy the file > > > > For point 2), there could be a customization variable to prevent the > > copy, that would be off in the default case, but can be turned on for > > the users who want backward compatibility or do something else by > > themselves, for instance use links. > > I think it's a good idea but I think it should be left until after the > next release to implement, as I suspect there will be enough issues from > other changes to deal with. Have no qualms about that.
Re: Width and Height in @image for Html Output fail
> Sent: Wednesday, November 25, 2020 at 7:07 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Width and Height in @image for Html Output fail
>
> On Thu, Nov 19, 2020 at 07:51:30PM +0100, Christopher Dimech wrote:
> > It occurs to me that one requires two image versions:
> > (1) An image for high-resolution pdf; and (2) Another
> > image for low resolution image html.
> >
> > Can we think of only having one command that calls
> > @image, rather than two (i.e. rather than having @iftex
> > and @ifhtml)?
> >
> > For instance,
> >
> > @image{../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.png}
> >
> > For pdf output will use the file
> > ../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.png
> >
> > For html output will use
> > ../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.html.png
> >
> > Or the like.
>
> If we could make @value work properly in the first argument of @image,
> then this could be used to configure image resolution. So you
> would do
>
> @image{../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.@value{imageres}.png}
>
> and elsewhere do
>
> @set imageres high
>
> to look for a file
>
> ../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.high.png
>
> I will look at the @value issue.
Yes, allowing @value would allow various possibilites and likely solve
other things, as you have mentioned.
Kind Regards
Christopher
@image with @value using texi2pdf
Running the following command using texi2pdf gives errors.
Output is correct for html output.
- Command -
@set imgf ../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg
@image{@value{imgf}.png}
- Errors -
(3 @ Microseismic Analysis of the Central Mediterranean Region) [-2]
(./03bCh--Chmed--Igm.texi)
./03aCh--Chmed--html.texi:316: TeX capacity exceeded, sorry [input stack size=5
000].
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
...
l.316 @image{@value{imgf}.png}
./03aCh--Chmed--html.texi:316: ==> Fatal error occurred, no output PDF file pr
oduced!
Transcript written on 03aCh--Chmed--html.log.
/usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
Re: @image and fifth argument during html output
Apologies, have changed to dvorak keyboard and hit period instead. I used it for
parameter illustration.
The command does not display as expected for html output. The output is
produced
with no errors, but the image is not displayed, displaying alttext instead.
When the file exists, using .png does not find the file.
@image{file,8cm,13cm,alttext,.png}
Regards
Christopher
> Sent: Wednesday, November 25, 2020 at 6:15 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @image and fifth argument during html output
>
> On Wed, Nov 25, 2020 at 05:31:49PM +0100, Christopher Dimech wrote:
> >
> > Gavin,
> >
> > Can one use for html output the command that follows. It was not working
> > even when the file exists. Texinfo was not giving an error, however, the
> > image was not being displayed in html when using .png.
> >
> > @image{file.w.h.alttext,.png}
> >
> > Regards
> > Christopher
>
> This looks wrong as the arguments should be separated by commas, not
> periods:
>
> > @image{file.w.h.alttext,.png}
> > @image{file,w,h,alttext,.png}
>
> Also w and h have to be numbers.
>
>
@image and fifth argument during html output
Gavin,
Can one use for html output the command that follows. It was not working
even when the file exists. Texinfo was not giving an error, however, the
image was not being displayed in html when using .png.
@image{file.w.h.alttext,.png}
Regards
Christopher
Re: @image for pdf and html
I am not sure, but can one pass file names to @image with @value? I remember that I could not do it when output is pdf or dvi. Have nat checked what happens for html output. Have also looked at @url, and found that it does not break at special characters as specified in the manual. Could users have something similar for break file names, as it is frequent that file names get very long, as happens with url's. Additionally, @float does not function. Regards Christopher - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy > Sent: Tuesday, November 24, 2020 at 11:17 PM > From: daniela-s...@gmx.it > To: "Gavin Smith" > Cc: "help-texinfo gnu" > Subject: Re: @image for pdf and html > > > Sent: Tuesday, November 24, 2020 at 10:55 PM > > From: "Gavin Smith" > > To: "Christopher Dimech" > > Cc: "help-texinfo gnu" > > Subject: Re: @image for pdf and html > > > > On Tue, Nov 24, 2020 at 10:11:09PM +0100, Christopher Dimech wrote: > > > It has been figured that we cannot use the same file for both > > > pdf/dvi output and html output. Because if the file has too many > > > pixels, the image will be too big for html. We could end up with > > > many calls to image with different files using @iftex and @ifhtml. > > > > You could equally say it's too big for pdf, if the pdf is going to > > put online. It's the same image either way. > > It is html that is limiting resolution, thus capability must be discussed when > compared to pdf output. Html provides serious limitations, unlike in pdf > where you can select the width and height. In geology based manual, the > resolution > is the most important aspect of any image. > > > I don't see anything wrong with using conditionals for different > > output formats to specify different image files, if that is what > > is desired. > > There is nothing wrong. However geology based manuals inherently > have many images, and defining for both is an extremely cumbersome > proposition. Besides the fact that images in html have limited use > because of the number of pixel limitation. Otherwise you cannot > see the text. > > >
Re: @image for pdf and html
It has been figured that we cannot use the same file for both pdf/dvi output and html output. Because if the file has too many pixels, the image will be too big for html. We could end up with many calls to image with different files using @iftex and @ifhtml. > Sent: Tuesday, November 24, 2020 at 10:05 PM > From: "Gavin Smith" > To: daniela-s...@gmx.it > Cc: "help-texinfo gnu" > Subject: Re: @image for pdf and html > > On Tue, Nov 24, 2020 at 09:32:15PM +0100, daniela-s...@gmx.it wrote: > > What is your opinion on using the same image file name for > > both: (1) pdf, dvi; and (2) html. > > > > @image(file,w,h,alttext,.png) > > > > Meaning that html will search for the filename, but with a token being > > appended to it. > > Sorry, I don't understand the question. > > - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
Re: Html Output for @image
> Sent: Sunday, November 22, 2020 at 6:49 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" , "help-texinfo gnu" > > Subject: Re: Html Output for @image > > On Fri, Nov 20, 2020 at 01:41:22PM +0100, Christopher Dimech wrote: > > Dear Gavin, Patrice, > > > > Have you figured out yet that even when the file exists, the image > > is not displayed when the fifth argument to @image is ".png". > > Furthermore, the error is not logged by texinfo. > > > > Regards > > Christopher > > I believe this issue is already understood and the solution is being > discussed. The issue with an extra period being added (so outputting > a reference to IMAGE..png) has already been fixed. The solution is being discussed. Fantastic.
Re: Displaying images for html output
> Sent: Sunday, November 22, 2020 at 6:46 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Displaying images for html output > > On Wed, Nov 18, 2020 at 09:47:09PM +, Gavin Smith wrote: > > On Wed, Nov 18, 2020 at 10:15:40PM +0100, Christopher Dimech wrote: > > > > > Thanks for sending the input and the output. This problem only occurs > > > > > when the image file is not found. I've tried to fix it in commit > > > > > e2d579377. > > > > > > > > Does it really! I have to check that out, give me a moment. > > > > > > No. The file exists and I use the correct path relative to > > > index.html. So the path is correct as far as html is concerned. > > > > As you said in another email the file name should be relative to > > the Texinfo file for consistency with other output formats. > > > > I doubt that relative names beginning "../" were much considered > > when @image was implemented (or even file names with directory parts > > at all). > > > > I haven't thought of a clear answer for this issue yet. I think that > > for split output, the image files need to be copied into the output > > directory and the file names should be given under that, not beginning > > "../". Alternatively, you could create a symbolic link to a directory > > containing the image files under the output directory. > > Another idea which I didn't think of before is, when the file > name begins ../, to transform this for split output by adding an > additional ../ to the front. Then the relative name would be correct > for split output. I don't support this idea, though: I think that > it's wrong for file names for images to begin with ../ as these names > are relative to the .texi input file, not for the HTML output files > which could be copied away from the .texi input file to another location. There exists the problem that for html, it is likely that one will use images with reduced number of pixels, otherwise the image will be excessively large when compared to the text. This will produce a low resolution image when using dvi and pdf output. > What could work, though, is just to strip all directories from the > file name when outputing the elements, as well as copying the > image files into the output directory. Then the output HTML manual > would be complete. This wouldn't work in case there were two > image files ../a/foo.png and ../b/foo.png but in that case you should > run texi2any -I .. and specify the names as a/foo.png and b/foo.png, > which would cause a and b directories to be created in the output > directory under the change we are considering. > >
Re: Displaying images for html output
> Sent: Sunday, November 22, 2020 at 10:02 AM > From: "Gavin Smith" > To: "Patrice Dumas" , "Christopher Dimech" > , "help-texinfo gnu" > Subject: Re: Displaying images for html output > > On Sun, Nov 22, 2020 at 12:46:35AM +0100, Patrice Dumas wrote: > > I think that > > the point is to copy the image file from where it is found to the > > destination directory. > > Could this break the build systems of any existing manuals that use images? > Are there any manuals that we could check? > > Also, what if the image files are out-of-date? > > I looked at the gendocs.sh script from gnulib, which would be one of > the most usual ways for people to generate HTML manuals that they > will upload to a website. It does take care of copying images, > copying them after running texi2any. This should be harmless if it > does it twice, just potentially slow if a manual has many images, but > gendocs.sh could potentially be altered to check if the files already > exist. > > It could be a benefit if texi2any does it instead of gendocs.sh, as there > is this comment in gendocs.sh, at the copy_images function: > > # copy_images OUTDIR HTML-FILE... > # --- > # Copy all the images needed by the HTML-FILEs into OUTDIR. > # Look for them in . and the -I directories; this is simpler than what > # makeinfo supports with -I, but hopefully it will suffice. > > I'm thinking that Texinfo's manual needs some images in it, for the dual > benefit of testing, and of showing people reading the Texinfo manual that > images actually are supported. Some ideas: > > These could be a proper diagrams, instead of ASCII art: > > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Tree-Structuring.html#Tree-Structuring > > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Heading-Format.html > > Does Anybody want to create this? We'd need at least a .png version, > and optionally a .eps version for dvi output. It should be in black > and white or at least look good in greyscale. > > Some manual-related humour, if we could get permission from the author > (the non-commercial licence is no good): https://xkcd.com/1343/ > > Maybe some photographs of old (historically important?) manuals (for > software or otherwise), or of somebody reading a book while fixing > something, to show the human side and importance of good documentation, > if anybody has an idea for something appropriate. Perhaps with a > caption like "systems are useless unless users understand how to > use them". I can do that. Regards Christopher
Re: Displaying images for html output
> Sent: Sunday, November 22, 2020 at 12:46 AM > From: "Patrice Dumas" > To: "Gavin Smith" > Cc: "Christopher Dimech" , "help-texinfo gnu" > > Subject: Re: Displaying images for html output > > On Sat, Nov 21, 2020 at 05:20:00PM +, Gavin Smith wrote: > > On Thu, Nov 19, 2020 at 10:11 PM Patrice Dumas wrote: > > > I think that if the path does not starts with . or .. or is an absolute > > > path, it would make sense > > > 1) to search in include directories (I think that the current directory > > > is always in front of of the search path) > > > 2) to check if the directories and image file exist in the destination > > > directory and if not copy the file > > > > > > For point 2), there could be a customization variable to prevent the > > > copy, that would be off in the default case, but can be turned on for > > > the users who want backward compatibility or do something else by > > > themselves, for instance use links. > > > > That sounds okay, as searching include directories matches what > > happens with TeX. When you say "current directory" this should mean > > the directory containing the Texinfo file, not the working directory > > from which texi2any is run. (What to do when a file in a subdirectory > > is @include'd and then references an image, I don't know.) I got to handle that situation an a daily basis. What I have found is that the include file that references the image got to have a number of Level Variables, so the texinfo can still get to the image. I can share a copy of the code so texinfo can get to the next level for complicated projects. Shall we do it? I have been pushing texinfo to the limit and the code would certainly provide ideas so that texinfo could handle those instances adequately. Regards Christopher > I think that it is the current directory, not the directory containing > the Texinfo file, but I do not think that it matters much. I think that > the point is to copy the image file from where it is found to the > destination directory. > > -- > Pat >
Html Output for @image
Dear Gavin, Patrice, Have you figured out yet that even when the file exists, the image is not displayed when the fifth argument to @image is ".png". Furthermore, the error is not logged by texinfo. Regards Christopher > Sent: Thursday, November 19, 2020 at 7:53 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" , "help-texinfo gnu" > > Subject: Re: Width and Height in @image for Html Output fail > > On Thu, Nov 19, 2020 at 07:40:40PM +0100, Christopher Dimech wrote: > > Choosing the maximum number of horizontal pixel to be 500 gets acceptable > > results. > > If you were serving these files from a server, using smaller files would > also save bandwidth. >
Re: Displaying images for html output
> Sent: Thursday, November 19, 2020 at 11:10 PM > From: "Patrice Dumas" > To: "Gavin Smith" > Cc: "Christopher Dimech" , "help-texinfo gnu" > > Subject: Re: Displaying images for html output > > On Wed, Nov 18, 2020 at 09:47:09PM +, Gavin Smith wrote: > > > > I doubt that relative names beginning "../" were much considered > > when @image was implemented (or even file names with directory parts > > at all). > > > > I haven't thought of a clear answer for this issue yet. I think that > > for split output, the image files need to be copied into the output > > directory and the file names should be given under that, not beginning > > "../". Alternatively, you could create a symbolic link to a directory > > containing the image files under the output directory. > > > > It's odd that the include path should be searched for image files. > > This makes sense for TeX but not for other formats, as there is no > > search path for image files for HTML or Info. It would only make sense > > if texi2any was going to copy the image files to the output location. > > I think that if the path does not starts with . or .. or is an absolute > path, it would make sense > 1) to search in include directories (I think that the current directory > is always in front of of the search path) > 2) to check if the directories and image file exist in the destination > directory and if not copy the file > > For point 2), there could be a customization variable to prevent the > copy, that would be off in the default case, but can be turned on for > the users who want backward compatibility or do something else by > themselves, for instance use links. Yes, that would be very sensible. > -- > Pat >
Re: Paragraph vertical space
Fantastic. - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy Sent: Thursday, November 19, 2020 at 8:45 PM From: "Hilaire Fernandes" To: "Christopher Dimech" , "Gavin Smith" Cc: "help-texinfo@gnu.org" Subject: Re: Paragraph vertical space I wrote it too early in the document source tree. Fine now. Thanks! Hilaire -- GNU Dr. Geo http://drgeo.eu https://pouet.chapril.org/@hilaire
Re: Paragraph vertical space
Works for me as well. > Sent: Thursday, November 19, 2020 at 8:22 PM > From: "Gavin Smith" > To: "Hilaire Fernandes" > Cc: "help-texinfo@gnu.org" > Subject: Re: Paragraph vertical space > > On Thu, Nov 19, 2020 at 08:19:55PM +0100, Hilaire Fernandes wrote: > > Doesn't work either. > > > > Le 19/11/2020 à 19:40, Gavin Smith a écrit : > > > Try > > > > > > @tex > > > \global\parskip=3em > > > @end tex > > > > > > instead. > > Works for me, we must be doing something differently. > >
Re: Width and Height in @image for Html Output fail
> Sent: Thursday, November 19, 2020 at 7:53 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" , "help-texinfo gnu" > > Subject: Re: Width and Height in @image for Html Output fail > > On Thu, Nov 19, 2020 at 07:40:40PM +0100, Christopher Dimech wrote: > > Choosing the maximum number of horizontal pixel to be 500 gets acceptable > > results. > > If you were serving these files from a server, using smaller files would > also save bandwidth. Yes, they could be part of a Gnu Manual people view from the Official Site. I have looked at the following website https://solarsystem.nasa.gov/resources/676/phases-of-the-moon/ There is an image of the phases of the moon. Doing "View Image Info" gives Dimensions: 3,728px x 3,728px (scaled to 712px x 712px) Thus in actuality, there are two imaged, one of them being 712px x 712px. But 712px x 712px is a different image, not the original scaled to 712px x 712px by the browser. That's the correct interpretation, am I right Gavin?
Re: Width and Height in @image for Html Output fail
It occurs to me that one requires two image versions:
(1) An image for high-resolution pdf; and (2) Another
image for low resolution image html.
Can we think of only having one command that calls
@image, rather than two (i.e. rather than having @iftex
and @ifhtml)?
For instance,
@image{../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.png}
For pdf output will use the file
../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.png
For html output will use
../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.html.png
Or the like.
Regards
Christopher
> Sent: Thursday, November 19, 2020 at 7:40 PM
> From: "Christopher Dimech"
> To: "Gavin Smith"
> Cc: "help-texinfo gnu"
> Subject: Re: Width and Height in @image for Html Output fail
>
> Choosing the maximum number of horizontal pixel to be 500 gets acceptable
> results.
>
> > Sent: Thursday, November 19, 2020 at 5:48 PM
> > From: "Gavin Smith"
> > To: "Christopher Dimech"
> > Cc: "Patrice Dumas" , "help-texinfo gnu"
> >
> > Subject: Re: Width and Height in @image for Html Output fail
> >
> >
> > On Thu, Nov 19, 2020 at 08:20:13AM +0100, Christopher Dimech wrote:
> > > Can't the large image be downsized with the height and width attributes in
> > > html?
> >
> > No, I mean changing the actual files themselves.
> >
>
>
Re: Width and Height in @image for Html Output fail
Choosing the maximum number of horizontal pixel to be 500 gets acceptable results. > Sent: Thursday, November 19, 2020 at 5:48 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" , "help-texinfo gnu" > > Subject: Re: Width and Height in @image for Html Output fail > > > On Thu, Nov 19, 2020 at 08:20:13AM +0100, Christopher Dimech wrote: > > Can't the large image be downsized with the height and width attributes in > > html? > > No, I mean changing the actual files themselves. >
Re: Paragraph vertical space
You can use
@vskip 3mm
-
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Thursday, November 19, 2020 at 7:23 PM
> From: "Hilaire Fernandes"
> To: "help-texinfo@gnu.org"
> Subject: Paragraph vertical space
>
> Hi,
>
> In the PDF output, I want to augment the minimum vertical space between
> paragraph.
>
> I tried without success this naive approach:
>
> @tex
> \usepackage{parskip}
> \setlength{\parskip}{3em}
> @end tex
>
> Hilaire
>
> --
> GNU Dr. Geo
> http://drgeo.eu
> https://pouet.chapril.org/@hilaire
>
>
>
Re: Width and Height in @image for Html Output fail
So what I got to do is reduce the pixel sizes? I will check that out. > Sent: Thursday, November 19, 2020 at 5:48 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" , "help-texinfo gnu" > > Subject: Re: Width and Height in @image for Html Output fail > > > On Thu, Nov 19, 2020 at 08:20:13AM +0100, Christopher Dimech wrote: > > Can't the large image be downsized with the height and width attributes in > > html? > > No, I mean changing the actual files themselves. >
Re: Width and Height in @image for Html Output fail
> Sent: Thursday, November 19, 2020 at 5:48 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" , "help-texinfo gnu" > > Subject: Re: Width and Height in @image for Html Output fail > > > On Thu, Nov 19, 2020 at 08:20:13AM +0100, Christopher Dimech wrote: > > Can't the large image be downsized with the height and width attributes in > > html? > > No, I mean changing the actual files themselves. Thusly you suggest I have two files, small ones for html. Is that how things are done for web pages?
Re: Width and Height in @image for Html Output fail
Can't the large image be downsized with the height and width attributes in html? - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy > Sent: Thursday, November 19, 2020 at 7:59 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" , "help-texinfo gnu" > > Subject: Re: Width and Height in @image for Html Output fail > > On Mon, Nov 16, 2020 at 09:44:28PM +0100, Christopher Dimech wrote: > > > > > Sent: Monday, November 16, 2020 at 9:33 PM > > > From: "Patrice Dumas" > > > To: "Christopher Dimech" > > > Cc: "help-texinfo gnu" > > > Subject: Re: Width and Height in @image for Html Output fail > > > > > > On Mon, Nov 16, 2020 at 09:32:08PM +0100, Christopher Dimech wrote: > > > > Have noticed that when using @image for html output, setting > > > > the width and height fails. > > > > > > Not sure what you mean about that, but it is documented that > > > > > > The optional WIDTH and HEIGHT arguments to the '@image' command (see the > > > previous section) specify the size to which to scale the image. They > > > are only taken into account in TeX. > > > > > > -- > > > Pat > > > > The problem that I have encountered war that the image was to large > > and the text too small. Then when I zoom, and the text becomes > > big enough, the image becomes enormous that I cannot view it. > > Could you shrink the images in the files you are using in HTML to > have fewer pixels? As far as I understand it by default images in > HTML are displayed with 1 file pixel to 1 display pixel. > > That doesn't sound like a great solution, though, because displays > can be different sizes. > > I wonder if there would be any harm in outputing the width and > height attributes for HTML as well, espcially if they are given > in display-independent units such as ems. >
Re: Width and Height in @image for Html Output fail
> Sent: Thursday, November 19, 2020 at 7:59 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" , "help-texinfo gnu" > > Subject: Re: Width and Height in @image for Html Output fail > > On Mon, Nov 16, 2020 at 09:44:28PM +0100, Christopher Dimech wrote: > > > > > Sent: Monday, November 16, 2020 at 9:33 PM > > > From: "Patrice Dumas" > > > To: "Christopher Dimech" > > > Cc: "help-texinfo gnu" > > > Subject: Re: Width and Height in @image for Html Output fail > > > > > > On Mon, Nov 16, 2020 at 09:32:08PM +0100, Christopher Dimech wrote: > > > > Have noticed that when using @image for html output, setting > > > > the width and height fails. > > > > > > Not sure what you mean about that, but it is documented that > > > > > > The optional WIDTH and HEIGHT arguments to the '@image' command (see the > > > previous section) specify the size to which to scale the image. They > > > are only taken into account in TeX. > > > > > > -- > > > Pat > > > > The problem that I have encountered war that the image was to large > > and the text too small. Then when I zoom, and the text becomes > > big enough, the image becomes enormous that I cannot view it. > > Could you shrink the images in the files you are using in HTML to > have fewer pixels? As far as I understand it by default images in > HTML are displayed with 1 file pixel to 1 display pixel. That would pose a problem as the image files are 300psi and reach 13cm in width. > That doesn't sound like a great solution, though, because displays > can be different sizes. Quite right. > I wonder if there would be any harm in outputing the width and > height attributes for HTML as well, espcially if they are given > in display-independent units such as ems. >
Re: Error with macro use case where arguments span in several lines
I have witnessed this problem. It could be related to the multi-line
problem we discussed for headings, where I started using @ at the end
of @unnumbered if the title spans more than one line.
-
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Thursday, November 19, 2020 at 7:44 AM
> From: "Gavin Smith"
> To: "Hilaire Fernandes"
> Cc: "help-texinfo gnu"
> Subject: Re: Error with macro use case where arguments span in several lines
>
> On Wed, Nov 18, 2020 at 09:46:00AM +0100, Hilaire Fernandes wrote:
> > Hi,
> >
> > With a figure macro defined as:
> >
> > @c Figure with caption @macro figure{caption,file,width} @ifnotplaintext
> > @float Figure,\file\ @center @image{\file\,\width\cm} @caption{\caption\}
> > @end float @end ifnotplaintext @ifplaintext @float Figure
> > @caption{\caption\} @end float @end ifplaintext @iftex @sp 1 @end iftex
> > @end macro
> >
>
> Ends of lines are missing here, could you send it again so I can test
> it?
>
>
Re: Displaying images for html output
For html there were four problems
1.
The file does not exist (relative to index.html) and using '.png' the
error shows '..png'
@image{../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg,8cm,8cm,AltText,.png}
2.
The file exists (relative to index.html) and using '.png' does not give an
error. But the image is not displayed in html output.
@image{../../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg,8cm,8cm,AltText,.png}
3.
The file exists (relative to index.html) and using 'png' does not give an
error. The image is displayed correctly in html output.
@image{../../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg,8cm,8cm,AltText,png}
4.
Image Width and Height have no effect in html output. Had passed an image that
was displayed very large compared to the text. Changed Width and Height in
the call to @image, but the size of the image was not reduced compared to the
text.
-
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Wednesday, November 18, 2020 at 10:47 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Displaying images for html output
>
> On Wed, Nov 18, 2020 at 10:15:40PM +0100, Christopher Dimech wrote:
> > > > Thanks for sending the input and the output. This problem only occurs
> > > > when the image file is not found. I've tried to fix it in commit
> > > > e2d579377.
> > >
> > > Does it really! I have to check that out, give me a moment.
> >
> > No. The file exists and I use the correct path relative to
> > index.html. So the path is correct as far as html is concerned.
>
> As you said in another email the file name should be relative to
> the Texinfo file for consistency with other output formats.
>
> I doubt that relative names beginning "../" were much considered
> when @image was implemented (or even file names with directory parts
> at all).
>
> I haven't thought of a clear answer for this issue yet. I think that
> for split output, the image files need to be copied into the output
> directory and the file names should be given under that, not beginning
> "../". Alternatively, you could create a symbolic link to a directory
> containing the image files under the output directory.
>
> It's odd that the include path should be searched for image files.
> This makes sense for TeX but not for other formats, as there is no
> search path for image files for HTML or Info. It would only make sense
> if texi2any was going to copy the image files to the output location.
>
Re: Displaying images for html output
> Sent: Wednesday, November 18, 2020 at 10:47 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Displaying images for html output > > On Wed, Nov 18, 2020 at 10:15:40PM +0100, Christopher Dimech wrote: > > > > Thanks for sending the input and the output. This problem only occurs > > > > when the image file is not found. I've tried to fix it in commit > > > > e2d579377. > > > > > > Does it really! I have to check that out, give me a moment. > > > > No. The file exists and I use the correct path relative to > > index.html. So the path is correct as far as html is concerned. > > As you said in another email the file name should be relative to > the Texinfo file for consistency with other output formats. Correct. I suppose you have made the change. My comment was on how I had tested it. At that time in test.texi the path that a user had to put for html output was relative to the index file. > I doubt that relative names beginning "../" were much considered > when @image was implemented (or even file names with directory parts > at all). Relative paths are very good, because if you copy your document project somewhere else or on another machine, you will still be able to execute the texinfo commands and nothing will break. And if you give a copy to your friend, he can get to work straightaway, ne need to change paths. > I haven't thought of a clear answer for this issue yet. I think that > for split output, the image files need to be copied into the output > directory and the file names should be given under that, not beginning > "../". Alternatively, you could create a symbolic link to a directory > containing the image files under the output directory. > > It's odd that the include path should be searched for image files. > This makes sense for TeX but not for other formats, as there is no > search path for image files for HTML or Info. It would only make sense > if texi2any was going to copy the image files to the output location. So the user has to transfer the files somewhere and picks them from there? 'https://path/file.svg>' always has some sort of path anyway. For large projects, image files are put in hierarchical directory structures. If you copy everything as is, your docu.texi will help you as the location of images is structured. If you put everything together, it will be a mess to manage. It is not a critical problem if internally texinfo makes a copy of the image files and refers to that. But don't mess the texinfo code itself. In the source code users must be able to use a directory structure for images.
Re: Displaying images for html output
> Sent: Wednesday, November 18, 2020 at 9:52 PM
> From: "Christopher Dimech"
> To: "Gavin Smith"
> Cc: "help-texinfo gnu"
> Subject: Re: Displaying images for html output
>
> > Sent: Wednesday, November 18, 2020 at 9:45 PM
> > From: "Gavin Smith"
> > To: "Christopher Dimech"
> > Cc: "help-texinfo gnu"
> > Subject: Re: Displaying images for html output
> >
> > On Sun, Nov 15, 2020 at 08:11:19PM +0100, Christopher Dimech wrote:
> > > When using the following, the imape is displayed.
> > >
> > > @set dirhtml ../../Ideogr/Ch03b--Chmed
> > > @image{@value{dirhtml}/igc03--01--Sicl--CircAmRg,8cm,8cm,,png}
> > >
> > > However, one gets the following warning
> > >
> > > Ch03a--Chmed--html.texi:309: warning: @image file
> > > `../../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg'
> > > (for HTML) not found, using
> > > `../../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.png'
> > >
> > > --
> > >
> > > But suppose one changes the command to include .png as below
> > >
> > > @set dirhtml ../../Ideogr/Ch03b--Chmed
> > > @image{@value{dirhtml}/igc03--01--Sicl--CircAmRg,8cm,8cm,,.png}
> > >
> > > One will get
> > >
> > > Ch03a--Chmed--html.texi:309: warning: @image file
> > > `../../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg'
> > > (for HTML) not found, using
> > > `../../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg..png'
> > >
> > > And the image is not displayed.
> >
> > Thanks for sending the input and the output. This problem only occurs
> > when the image file is not found. I've tried to fix it in commit
> > e2d579377.
>
> Does it really! I have to check that out, give me a moment.
No. The file exists and I use the correct path relative to
index.html. So the path is correct as far as html is concerned.
But the image is only displayed when using 'png' only. Whereas
the correct syntax should be '.png', and this fails.
> Regards
> Christopher
>
>
>
