Re: PO-based Documentation Translation

[Malcolm Tredinnick <malcolm commsecure com au>]

On Mon, 2003-09-29 at 09:23, Malcolm Tredinnick wrote:
[...]
> Also, when I looked at the KDE tool back in March, it did not seem to do
> everything we wanted (as far as I could see from our design discussions
> ont his list). Some things that I remember
> 
>         - it did not factor out repetitive strings (like the contents of
>         a <guimenu> element) and then put a placeholder into complete
>         sentences that contain this string.
>         
>         - it did not handle general entities in a particularly
>         intelligent way (translate the entity once and leave the entity
>         reference in place; treat the entity as possible XML markup and
>         strip any tags that are not needed for translation context).
>         
> I don't think I looked at the handling of external entities or XIncluded
> files, but the documentation that you point to seems to only talk about
> single files, so that's an unknown issue for me at the moment. One of my
> design goals, is that if the source document consists of multiple files,
> then the translated version should be in one-to-one correspondence.

One item I forgot, but just remembered re-reading that stuff: the KDE
tool requires every string to be translated before a translated document
can be generated (according to
http://i18n.kde.org/translation-howto/doc-step-by-step.html). This is
unacceptable to me, since some documents are enormous and allowing
partial translations (even if just to see what it looks like) is a Good
Thing.

Malcolm