octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #52775] PDF user manual uses a backward apostr


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #52775] PDF user manual uses a backward apostrophe ` in code examples
Date: Fri, 12 Jan 2018 03:06:23 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Follow-up Comment #24, bug #52775 (project octave):

I think I see what you are getting at.  Texinfo now appears to be handled via
some "universal" program makeinfo which incorporates support for
TeX-derivative formats, .info, .html, and whatever else.  These apps have
names like texi2dvi, etc.  However, of note is that the one called texi2html
is on its way out (and is bundled in its own Ubuntu/Mint package).  The
texi2any app has an independent HTML conversion.

What's important for the texi2dvi support is the file texinfo.tex, and gnulib
subdirectory has an up-to-date copy of that, so in the Octave environment,
texi2dvi is effectively Texinfo 6.1--even though the system makeinfo is older.
 HTML support doesn't work in such a way, so it's implementation is the
makeinfo version.

I'll just summarize options:

1) If there is no @sortas feature support, define @sortas{} as
empty/do-nothing.  Not desirable, but it builds.

2) Nuance the manual build into TeX versions and non-TeX versions by doing
feature-tests on both.  Right now, texi2dvi is looking to the local gnuplib
texinfo.tex file and should like have the features and the TeX-derivative
versions of the manual should be built.  The non-TeX versions of the manual
have a good chance of not being built because @sortas is introduced in early
2016

https://lwn.net/Articles/675087/

3) Don't use the gnulib texinfo.tex file.  Instead always use the system true
makeinfo version, and if it fails to have the feature @sortas, then no
versions of the manual will be built.

I sort of like option #3 over #2, just because it is a simpler implementation
I guess.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52775>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]