hugin-devs team mailing list archive

[Christoph Spiel <cspiel@xxxxxxxxxx>]

THX for feeding the doc into Texinfo-5.1 again.
I'm still on makeinfo-4.13, so I cannot check myself yet.
Thus, the problem will remain unless someone sends us a patch.

On a medium time-scale I'm inclined to switch to plain LaTeX
and drop Texinfo.  The vast majority of users doesn't read the
documentation at all.  The rest prefers PDF.  Or whatever HTML,
if it only is on a public server.

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1181678

Title:
  build-error with texinfo 5.1

Status in Enblend:
  New

Bug description:
  Hello,

  documentation generation fails with texinfo 5.1.  texinfo seems to have stopped supporting colons in variable names (@set <-> @value), causing errors like this one:
  -----
  doc/enfuse.texi:564: bad syntax for @value
  -----

  According to texinfo 5.1 documentation basically the only thing
  guaranteed to work are alpha-numericals:

  Subsequent characters, if any, may not be whitespace, ‘@’, braces,
  angle brackets, or any of ‘~`^+|’; other characters, such as ‘%’, may
  work. However, it is best to use only letters and numerals in a flag
  name, not ‘-’ or ‘_’ or others—they will work in some contexts, but
  not all, due to limitations in TeX.

  cu Andreas

  See http://bugs.debian.org/708800 or
  https://bugzilla.redhat.com/show_bug.cgi?id=919935

To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/1181678/+subscriptions