Nino Novak wrote:
> Additional insights: Comparing the English (original) WG2 to the German
> "translation" I noticed that the German WG has different chapter titles
> and structure in several places, so for me it seams quite reasonable
> not to stick to the proposed document path structure which just appends
> a DE/ at the beginning (Doc/WG2/... -> DE/Doc/WG2...) but to use
> different path names according to the German document stucture.
>
> What was the rationale behind the "strictly" matching path structures?
There are several reasons. For example, we are using InterWiki linking
to link from one document translation to another. There are essentially
two ways we've found to do this... either adding the interwiki linking
to every page and maintaining it all manually, or using a Template.
Adding the InterWiki linking and maintaining it all manually is
reasonably ok for say... two languages... but when you add a third and a
fourth and then a fifth, to the mix, a change in one page can mean 5 to
10 page edits to update... or add a sixth language, and then you have to
go and edit all pages in all languages to link them between each other.
it rapidly escalates into an unmanageable mess.
Using a template was, and currently is the best/easiest way I can find
to deal with this (unless of course someone can come up with a better
solution besides not using InterWiki linking to link from one translated
page to another). There are Wiki page name variables that we can use,
but that will return only the whole page name with all subpages, or only
the last part of the subpage structure. Since we are "fudging" things
with the various languages by adding an ISO language code to the subpage
structure, that ISO code is a part of the whole page name.
The template structure currently looks like this for.. for example, the
Dev Guide:
[[en:{{{1}}}]]
[[zh:Zh/{{{1}}}]]
This allows us to pass a single variable that does not need to be
maintained (ie in translations, it can simply be copied over from the
English master document, and will work for any language)
If the Chinese page names (or subpages) are localized into Chinese, I
cannot find any way to pass that as a manageable variable... or as
something that does not need to be maintained. We can pass the Chinese
page name... but it then requires manual intervention.
(explaining effectively this needs a whiteboard :-) )
It really does stem back to the old problem... we are trying to manage
multiple languages in a single Namespace, and that comes with a few
issues like this one.
As for the different structure... is this because you've found a better
way to present the information? Is this a problem/solution that could
also be used in the English side, making both document sets better? The
Chinese translation was able to maintain the same document structure...
so I'm curious what ended up in different places in the German translation.
C.
--
Clayton Cornell ccorn...@openoffice.org
OpenOffice.org Documentation Project co-lead
StarOffice - Sun Microsystems, Inc. - Hamburg, Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@documentation.openoffice.org
For additional commands, e-mail: dev-h...@documentation.openoffice.org
