2010/12/3 Wolfgang Bornath
<molch.b@googlemail.com>
2010/12/3 Marek Laane <bald@smail.ee>:
>>
> One point we could discuss is avoiding same path in case of documentation as
> in Mandriva which rather intimidated translators and IMHO was somehow
> cumbersome (I never could master neither Borges nor it's successor). Maybe
> we could adapt e.g. KDE's way: make documentation available in same format
> as UI, i.e. in PO-files, and use some scripts translating PO to XML and vice
> versa?
As PO is not really usefull for floating text (my personal opinion
based on my experience with Mandrake/Mandriva manuals, your mileage
may vary) we do need a collaboraton platform. Yes, Borges was
something you had to learn to work with but we (Mandrake manual team,
later NeoDoc.biz) liked it :) There are talks between Anne and Camille
from NeoDoc about an Account in Calenco. I asked Anne if we could have
a training account at Calenco to test it. We'll see...
Of course we will discuss this when the time comes - at the moment too
many questions are open (what has to go into "official" documentation,
the one which will be delivered with the distributiona and which
should be translated into as many languages as possible, then what
will be in which part of the wiki yet to create, etc.).
That's why I postponed the creation of documentation group and
"doc-translation" group.
--
wobo
Well, yes, as KDE translator my "mileage" really shows it's much more easy to translate PO-s and then regenerate it as XML (DocBook in KDE) and add pictures and so on than fuss about in any other format - I've had years ago even translated Mandriva docs straight in XML but can't say if was great fun... Another point for PO is that you can have translation memory if you use Lokalize or some other TM-capable application. But, of course, all that may be discussable in future...
Marek Laane