← Back to team overview

hugin-devs team mailing list archive

[Bug 1181678] [NEW] build-error with texinfo 5.1

 

Public bug reported:

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

** Affects: enblend
     Importance: Undecided
         Status: New

-- 
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


Follow ups

References