[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using texi2html for the documentation
From: |
Reinhold Kainhofer |
Subject: |
Re: Using texi2html for the documentation |
Date: |
Sun, 30 Mar 2008 18:59:43 +0100 |
User-agent: |
KMail/1.9.6 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Sonntag, 30. März 2008 schrieben Sie:
> > The problem that I see in general are cross references (they are a
> > problem even with multiple nodes in one file... How do we get the correct
> > file name for a cross-reference, if it cannot be deduced from the node
> > title at all????). How should be define the @r* macros to work
>
> Here's a possible solution -- I don't speak a word of Perl and haven't
> looked at the code, maybe something similar is already implemented.
> @translationof is parsed just like @node, and (@node,@translationof)
> pairs are stored in a map or a list, or whatever the right Perl data
> structure for maps. Then, it's easy to deduce the desired file name
> when writing HTML output for a x-ref.
This would only work within the same document (where it already works out of
the box anyway). For cross-manual links, there would need to be multiple runs
and this data would need to be written out to a temp file after each manual
is converted to HTML. Each manual would then need to read in all other such
temp files and heavily customize the way cross-refernces are generated.
> > The language passed to texi2html as --lang=$(ISOLANG) is now added to the
> > extension as .$(ISOLANG).html.
>
> I'm not sure this will work well with add_html_footer.py hacking,
> especially extensions stripping for automatic language selection: does
> your init script writes hrefs with .$(LANG).html too?
Of course. It simply takes the full html name of the taget.
But as I said, that's added by my init script for texi2html, so we can easily
disable adding $(LANG) to the suffix.
> If it does,
> add_html_footer.py will likely need some hacking to handle file names
> which already have a language suffix.
The add_html_footer.py needs to be adjusted to texi2html anyway (e.g. the
footer can be automatically added directly by texi2html, the <body> tag gets
some arguments automatically so that the splitting at </?body> no longer
works, etc.).
Cheers,
Reinhold
- --
- ------------------------------------------------------------------
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)
iD8DBQFH79UQTqjEwhXvPN0RAnxUAJ9x996fXUCanAjQBeLGGPCY4M0A0ACeOnA4
NINJh5d8CRhWEyQOLl1HHms=
=HdIx
-----END PGP SIGNATURE-----
- Re: Using texi2html for the documentation, (continued)
- Re: Using texi2html for the documentation, John Mandereau, 2008/03/22
- Re: Using texi2html for the documentation, Graham Percival, 2008/03/22
- Re: Using texi2html for the documentation, John Mandereau, 2008/03/23
- Re: Using texi2html for the documentation, Graham Percival, 2008/03/24
- Re: Using texi2html for the documentation, Reinhold Kainhofer, 2008/03/29
- Re: Using texi2html for the documentation, John Mandereau, 2008/03/30
- Re: Using texi2html for the documentation, John Mandereau, 2008/03/30
- Re: Using texi2html for the documentation,
Reinhold Kainhofer <=
Re: Using texi2html for the documentation, Francisco Vila, 2008/03/16
Re: Using texi2html for the documentation, John Mandereau, 2008/03/16