El jue, 29-09-2005 a las 01:31 +0400, Alexandre Prokoudine escribió:
On 9/29/05, Adib Taraben <taraben.a@...50...> wrote:
Q: that means that the translation of the tutorial remains in the po file that will be deliverd ? Even the tutorial is translated and converted to the different svg's :-?
No. How it works is:
- Convert an XML markup(p)ed file (customized DocBook/XML in case of
KDE) to PO file with a special utility that breaks the whole text into multiply PO entries sentence by sentence.
Translate.
Commit to CVS/SVN.
.
When changes to original text get committed, your PO file is
automatically updated. Changed text becomes a fuzzy entry in PO file. New text becomes untraslated entry. You can easily navigate from one fuzzy/untranslated entry to another in KBabel. Compare it to xmldiff output ;-)
- For release PO files are converted back to XML and, in case of
Inkscape, could be then converted to SVG.
I'd like to point out that there's a fairly recent tool available for translatoin of svg files: Open Language Tools (https://open-language-tools.dev.java.net/). These used to be a Sun inside project but they released it a few months ago. It's very suitable for translation of XML files (it also supports a variety of other formats) and recently some committed a filter for SVG. The great thing about these tools is that they have a fairly good translation memory, which is useful when updating a translation. I think it's easier to use than the conversion to and fro.
Cheers, Lucas
I also would like to know how we/I can add strings to the/a po that are not in the c-source ?
I'm not sure I'm really helpful here, but this is exactly what happens to inkscape.desktop file.
Alexandre
This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel