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

Lübbe Onken wrote:
> Hi Folks,
>
> I just stumbled upon a possible solution for this translation
> problem. I was wondering why the command line parameters of
> TortoiseMerge weren't translated, but the explanations were.
>
> In TortoiseMerge we use a "variablelist" to describe the commandline
> parameters. In TortoiseSVN's automation appendix we use a table. The
> "term" in a "variablelist" isn't sent through the translation, so if

We use 'variablelist' elsewhere, where we _do_ want a translation.

tme_appa.xml (keyboard shortcuts)
tme_ch00.xml (credits)
tme_glossary (is this still in? it's useless)
tsvn_app_faq.xml (all over - we _are_ getting rid of this, aren't we?)
tsvn_basic.xml (working copy states)
tsvn_introduction.xml (subversion features, tsvn features)
tsvn_preface.xml (credits)
dug_branchtag.xml (make branch from ...)
dug_bugtracker.xml (bugtraq: properties - hooray we want this
untranslated)
dug_commit.xml (progress dialog line colours)
dug_conflicts.xml (filename.mine.rxx)
dug_diff.xml (common diff scenarios, external programs)
dug_revgraph.xml (graph node types)
dug_settings.xml (most of them :-(
dug_update.xml (as dug_commit.xml)
server_apache.xml (Apache features)

We either need to find an alternative to <term>, or we need to convert
these lists to a different type.

Simon

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