[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Docs: Using backslashed in node names causes problems with pdf and texi2
From: |
Reinhold Kainhofer |
Subject: |
Docs: Using backslashed in node names causes problems with pdf and texi2html ("The \override command") |
Date: |
Mon, 11 Aug 2008 22:43:30 +0200 |
User-agent: |
KMail/1.9.9 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Although the texinfo manual does not explicitly forbid it, using backslashes
in node names causes problems with both texi2pdf and texi2html:
- -) texi2pdf throws an error (I don't know why, because "@" is the command
prefix and not "\" ...). We never ran into this problem yet, because we
don't create PDFs for translated manuals yet. The only place with a link to a
node with a backslash ("The \override command") is in the German and French
translations of tweaks.itely (but not in the original English version...)
- -) texi2html will simply remove the backslash if it is used in a macro call
(i.e. @ruser{The \override command} does the same as @ruser{The override
command} and thus points to a non-existing file/anchor).
makeinfo --html and texi2html will generate links to the correct anchors for
links when called with @ref.
However, backslashes will also cause problems if they are used in macro
arguments (and all our external refs ARE called through macro arguments).
Here, also texi2pdf and makeinfo --html fails...
As a solution I propose to remove the backslash from the node names and the
xrefs, so links will work. They can/should stay in the section titles, which
are not used for the links anyway. There they don't cause any errors anyway.
We already use node names with the @code removed, so this should not be an
issue. The only thing is that the file names will be different, but I don't
regard this as an issue, either, since all links within our docs are
automatically generated anyway.
Cheers,
Reinhold
PS: To see the problem, simply try to run the attached file with texi2html,
texi2pdf and makeinfo --html. The correct anchor would
be "The-_005coverride-command" for all links, but neither translator manages
to do this...
- --
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, http://reinhold.kainhofer.com/
* Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
* K Desktop Environment, http://www.kde.org, KOrganizer maintainer
* Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIoKR3TqjEwhXvPN0RArKwAKCl72shH8Sv7cE5Vlf2pv17q6DsbwCfRD+O
SNkFbBKgKf1VRC2JcpdNq/0=
=c73h
-----END PGP SIGNATURE-----
texi2html_backslash_section.texi
Description: Text document
- Docs: Using backslashed in node names causes problems with pdf and texi2html ("The \override command"),
Reinhold Kainhofer <=
- Re: Docs: Using backslashed in node names causes problems with pdf and texi2html ("The \override command"), Graham Percival, 2008/08/12
- Re: Docs: Using backslashed in node names causes problems with pdf and texi2html ("The \override command"), Valentin Villenave, 2008/08/12
- Re: Docs: Using backslashed in node names causes problems with pdf and texi2html ("The \override command"), Werner LEMBERG, 2008/08/12
- Re: Docs: Using backslashed in node names causes problems with pdf and texi2html ("The \override command"), Reinhold Kainhofer, 2008/08/12
- Re: Docs: Using backslashed in node names causes problems with pdfand texi2html ("The \override command"), Trevor Daniels, 2008/08/12
- Re: Docs: Using backslashed in node names causes problems with pdfand texi2html ("The \override command"), Reinhold Kainhofer, 2008/08/13
- Re: Docs: Using backslashed in node names causes problems with pdfand texi2html ("The \override command"), Trevor Daniels, 2008/08/13
Re: Using backslashed in node names causes problems with pdf andtexi2html ("The \override command"), Trevor Daniels, 2008/08/12