--- Begin Message ---
|
Subject: |
Texinfo and node presentation names |
|
Date: |
Sun, 28 Nov 2010 06:30:46 +0100 |
Dear Karl,
I am maintaining some S/W called jPicEdt (the official site is
http://www.jpicedt.org, but you can find my very latest dev installer on my
page
http://vincentbelaiche.pagesperso-orange.fr/loli/jpicedt/jpicedt.html,
the development version has many incompletely developped feature so you
should know about it if you want to use it).
I am considering to convert the help pages from HTML to Texinfo in order
to benefit from this that Texinfo allows not only to HTML ouput but also
PDF and Info formats. I also find it more convenient to type Texinfo
code than HTML code, because Texinfo is more suited to S/W
documentation.
Now, I have met several pitfalls connected to multilingual documentation,
and I would welcome your kind feedback on whether there are solutions. I
can give a hand if some extension of Texinfo is needed:
- Because of multilingual support I translate also the node names, but
however, what I need to translate is not the node name itself (ie the
node address within the info file, or the HTML page filename in a HTML
output), but rather the node /displayed name/. I have looked into the
Texinfo manual and there is no primitive like @displaynodeas, I am
seeking something like
-----------------------------------------------------------------------
@node Node address (e.g. in English)
@displaynodeas{Node displayed name in this translation}
-----------------------------------------------------------------------
The reason why I would like different text strings for the node
address and for the node display name, is that I consider it to make
manual maintenance significantly easier if same addresses are kept
accross different translations.
- Words like Up, Next, Previous, are not translated for the HTML export,
although I have set the document language to fr. In the Texinfo build
there could be a single resource file in M4 that could be used to
produce the txi-fr.tex for tex export, and some other resource file
defining some HTML entities to be used in the HTML export (e.g. for
words Up and Next...
- In jPicEdt manual, just like in JDEE manual, the HTML display is in
two frames: there is a side frame on the left part that looks like an
navigation explorer. I would like to know whether it is possible to
generate automatically this kind of navigator during the HTML export,
for instance it could be based on the top node, or it could derived
from the table of content (from structuring commands like @section,
@subsection and suchlikes)
VBR,
Vincent.
--- End Message ---
--- Begin Message ---
|
Subject: |
Some issues with ifinfo and ifhtml |
|
Date: |
Sun, 28 Nov 2010 06:44:20 +0100 |
Hello,
FYI, the attached file produce a compilation error. It seems that the
@setfilename command cannot be enclosed within @ifhtml or @ifinfo
directives.
Furthermore, if I remove those @ifhtml and @ifinfo and just have
@setfilename jpicedtfr-html
then the HTML compilation produces plenty of warnings on macroes
previously defined.
Vincent.
jpicedtfr.texi
Description: application/texinfo
--- End Message ---