May 1st, 2005 — Thanks to the active help from the community, all English tutorials that we had in SVG are now converted to DocBook! From within Inkscape, they are still available as fully editable SVG which you can play with, but having the DocBook source makes it easy to produce any other formats or renditions automatically. In particular, all converted tutorials are now availble in HTML, linked from our Documentation page.
What's next? We have several of the tutorials translated into several languages. Now we need to convert these to DocBook as well. Here is a page
http://inkscape.org/cgi-bin/wiki.pl?TranslationInformation
with details on how to translate tutorials or convert existing translations. We already have the Basic in Spanish and several French ones are being worked on; the rest are up for grabs. Pick a tutorial and make it available in your native language!
bulia byak <buliabyak@...400...> wrote in news:3c78ff0305050114121d85b88e@...401...:
What's next? We have several of the tutorials translated into several languages. Now we need to convert these to DocBook as well.
I thought one of the advantages of using DocBook would be that we could use standard PO tools to translate the documentation. With the old doc format it was ~impossible to keep the tutorial translations up-to-date.
KDE and other projects use tools to convert the DocBook files to PO files (and back again), splitting each paragraph, list item &c. into separate strings. Then translators can use the tools they know to *easily* translate the documentation, and all translations would automatically be up-to-date (changed paragraphs would be marked as 'fuzzy').
Wouldn't this be possible here too?
If we manually have to constantly CVS diff the DocBook files to see which parts have changed, and manually make the same changes in the translations (i.e., the current situation) the tutorial translations will remain hopelessly outdated.
Believe me, translating from Docbook is the easiest thing you can do. I'je just updated translations (in French) then converted to Docbook Basic and Advanced tutorials, and on the other hand directly translated Callygraphy and Tracing from Docbook to Docbook : the second solution is much easier and elegant. Another huge advantage of Docbook : it's pure and simple XML, and easily readable in any text reader : you can work on the translation on any platform (Mac, Win, Solaris, Linux, BSD...) Finding a correct po file manager under windows in not so simple (poedit is ok, but far from perfect compared to kbabel under unices...)
Regards,
Matiphas
Selon Karl Ove Hufthammer <karl@...476...>:
bulia byak <buliabyak@...400...> wrote in news:3c78ff0305050114121d85b88e@...401...:
What's next? We have several of the tutorials translated into several languages. Now we need to convert these to DocBook as well.
I thought one of the advantages of using DocBook would be that we could use standard PO tools to translate the documentation. With the old doc format it was ~impossible to keep the tutorial translations up-to-date.
KDE and other projects use tools to convert the DocBook files to PO files (and back again), splitting each paragraph, list item &c. into separate strings. Then translators can use the tools they know to *easily* translate the documentation, and all translations would automatically be up-to-date (changed paragraphs would be marked as 'fuzzy').
Wouldn't this be possible here too?
If we manually have to constantly CVS diff the DocBook files to see which parts have changed, and manually make the same changes in the translations (i.e., the current situation) the tutorial translations will remain hopelessly outdated.
-- Karl Ove Hufthammer Jabber: huftis@...450...
This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Sundag 8. mai 2005 17:47 skreiv matiphas@...8...:
Believe me, translating from Docbook is the easiest thing you can do.
Believe me, I have no problem translating DocBook. What I *have* problems with, is keeping the translations in sync with the original documents. DocBook in itself doesn't help here, and the translations will get outdated.
I just tried the tools KDE uses (you'll likely find them in the package 'kdesdk' in your favourite distribution), and it looks like they're really easy to use:
1. xml2pot tutorial.xml > tutorial.pot 2. copy/msgmerge the .pot file to xx.po file(s) 3. translate the xx.po file 4. po2xml tutorial.xml xx.po > tutorial-xx.po
Finding a correct po file manager under windows in not so simple (poedit is ok, but far from perfect compared to kbabel under unices...)
Of course having xml2pot doesn't stop you from translating the DocBook files in the usual way. So if you prefer using cvs diff + Microsoft Notepad to keep the translations in sync, you're more welcome to do that. :)
Karl Ove Hufthammer wrote:
I just tried the tools KDE uses (you'll likely find them in the package 'kdesdk' in your favourite distribution), and it looks like they're really easy to use:
- xml2pot tutorial.xml > tutorial.pot
- copy/msgmerge the .pot file to xx.po file(s)
- translate the xx.po file
- po2xml tutorial.xml xx.po > tutorial-xx.po
That sounds like a good approach. Could you add information about it to the wiki page (http://inkscape.org/cgi-bin/wiki.pl?TranslationInformation) please?
participants (4)
-
unknown＠example.com -
bulia byak -
Jonathan Leighton -
Karl Ove Hufthammer