Hi Gabriel! On Dec 11, 2009, at 20:52, "Gabriel M. Beddingfield" <[email protected]> wrote:
> I recently tackled this issue with Hydrogen[1]. The long > story short: using DocBook 4.x XML with poxml from the KDE > 4 SDK[2] works well... especially if you don't /already/ > have a bunch of translations of your manual. Thanks for sharing your experience there. Can you point me at your po/ XML source files to see how it looks in your repository? I'm not sure I'd be too keen on a KDE/Linux centric approach (probably works fine on BSD too), or even the idea of involving a transformed representation that editors have to work with (the po files). Is it some feature of po files that actually make managing translations easier or is it just a better toolchain interface? > Taking a step back, several strategies for doing this > kind of translation. Of the free/open-source solutions, > there are: > > + Making a copy and translating it. > PROS: works, gets it done fast, translators are at > liberty to alter stuff as needed, everything is > done in DocBook (SGML or XML, your pick). > CONS: very difficult to update, translators are at > liberty to alter stuff as needed. Until we actually have a completed translation in some language, I've had this approach in mind simply because of it's efficiency and simplicity. Given the sheer quantity of existing documentation, simple is good. We can tailor script to cross validate languages that are partially translated too. Not ideal, but the the vast majority of effort is with the translators, so that feels like a good starting point. Cheers! Sean > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
