RE: [TSVN] Doc restructuring of automation appendix / translation

Ste wrote:

> Check the file doc/xml2po-modes/docbook.py
> The <term> tag is marked as 'final' there, so it won't show up in the
> po file. If we remove that tag, the <term> tags will again show up
> (which is probably what we should do, see Simons comment)

Wait a minute before you change anything in the python script:

In tsvn_introduction we've got the following structure:

<variablelist>
<varlistentry>
<term>Shell integration</term>
<listitem>
<para>Blah</para>
</listitem>
</varlistentry>

And this variablelist gets translated.

In tme_appb it looks like this:

<variablelist>
<varlistentry>
<term>/base:&quot;path/to/basefile&quot;</term>
<listitem>
<para>load the base file</para>
</listitem>
</varlistentry>

And this variablelist doesn't get translated. See any structural difference?
No? Neither do I.

But if we look a bit further up, we see that in tsvn_introduction the
variablelist is placed inside:
<chapter id="tsvn_introduction"><sect1>

And in tme_appb it's inside:
<appendix id="tme-commandline"><sect1>

Is it possible, that xml2po is smarter than we think and handles
variablelists inside an appendix different from variablelists inside a
chapter?!?
All <term>s in tme_appb start with a '/'. Could this make a difference?

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org