On Mon, May 08, 2006 at 12:04:21PM +0200, Xavier Conde Rueda wrote:

Hi all!

This is my first message on this list, so I'll introduce myself. My name is Xavi, and i'm in charge of the Catalan localization team. Many thanks for creating this list, it will help a lot!

I have some questions about the translation of tutorials for Inkscape. My team translated the SVG documents recently. We know the right way is to translate them on XML format, but we needed them on SVG in order to integrate them on a Windows package we deployed. We are going to move them to the XML tutorials, however I submitted the SVGs some months ago through the patch tracker but they haven't been accepted yet. I'm not sure if you don't accept SVG tutorials anymore (thus forcing to port them to XML, which anyway I think is the correct way) or if you just didn't saw them.

I'd favor adding the SVG tutorials. It's true that they need to be converted to XML in order to make it easier for translators, but I think that can be done subsequently. But I think this work is more likely to be done if the tutorials are included, than if they're sitting in the patch tracker.

I would say, check to see if anyone has raised any other issues in the tracker, aside from the XML conversion, and if not, then go ahead and add it (or find someone with commit access to apply it.) Bulia and ScislaC tend to be attentive to the tutorials and could be solicited for additional feedback, but remember that inkscape's motto is "patch first, discuss later". :-)

Also, related to Matiphas prevoius mail, i want to point a very important source for localization: the Windows installer. For my organization, it's very important to have it translated; just running it on English isn't enough, so we consider it as important as another UI element. So, in order of importance, i would say,

1. po files
2. tutorials
3. Windows installer
4. Release notes
5. Web pages
6. README, etc. (really this should be never been read at all)

In fact, you could question if translating README and HACKING is even appropriate: If a developer needs to change a process and updates one of these files, it will probably be difficult for translators to recognize the translated versions need updated right away, and in the meantime the original and the translation will be specifying different procedures; the reader then cannot trust anything but the original file, which could get frustrating. Fortunately, these files do not change very often...

A second issue with translating these files is that since they sit in the root directory, if they get translated into a lot of languages, it increases the filecount in that root inkscape/ directory quite a bit. A possible solution to this issue would be to move the translations into the doc/ directory.

Anyway, so yes I think putting them at lowest priority is the right thing.

Bryce

The TranslationInformation page should be rewritten following this list. Also, additional information for how to translate the windows installer should be added: it's not too difficult to translate, and it will save having to do a separate build with a translated installer. I would like to add the information about translating the installer, some time in the future :).

Regards!

Google talk: xavi.conde a gmail.com

---

Hackers (and creative people in general) should never be bored or have to drudge at stupid repetitive work, because when this happens it means they aren't doing what only they can do ??? solve new problems.

Eric Steven Raymond (http://catb.org/~esr/faqs/hacker-howto.html)

Hi,

Xavier:

I have some questions about the translation of tutorials for Inkscape. My team translated the SVG documents recently. We know the right way is to translate them on XML format, but we needed them on SVG in order to integrate them on a Windows package we deployed. We are going to move them to the XML tutorials, however I submitted the SVGs some months ago through the patch tracker but they haven't been accepted yet. I'm not sure if you don't accept SVG tutorials anymore (thus forcing to port them to XML, which anyway I think is the correct way) or if you just didn't saw them.

Does anyone have current info on this? I'm not sure whether the XML/SVG info on page

http://wiki.inkscape.org/wiki/index.php/TranslationInformation

is still valid or not. Can/should we still commit SVG tutorial files directly to SVN?

Arpad Biro

__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Hi Xavi

I have some questions about the translation of tutorials for Inkscape. My team translated the SVG documents recently. We know the right way is to translate them on XML format, but we needed them on SVG in order to integrate them on a Windows package we deployed. We are going to move them to the XML tutorials, however I submitted the SVGs some months ago through the patch tracker but they haven't been accepted yet. I'm not sure if you don't accept SVG tutorials anymore (thus forcing to port them to XML, which anyway I think is the correct way) or if you just didn't saw them.

OK. the first thing to do, is to install an xslt processor (such as saxon, which also needs java to run) See http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/README?vie...

or xsltproc (available on most linux distributions Then run the xslt processor on the docbook document and the xslt descriptor on order to generate an html or svg document (such as : xsltproc tutorial-svg.xsl tutorial.xml > tutorial.svg )

A potential solution, in your case, is to copy-paste strings from the svg files you've generated to some docbook new files (see them in the svn tree), then run the xslt processor on them. I can help you if you need. (Bulia may be able to provide some clues too)

The docbook format is interesting because with the appropriate xslt files, you can convert the docbook files to any other readable format.

Also, related to Matiphas prevoius mail, i want to point a very important source for localization: the Windows installer. For my organization, it's very important to have it translated; just running it on English isn't enough, so we consider it as important as another UI element. So, in order of importance, i would say,

Ah, yes, you're absolutely right !

1. po files
2. tutorials
3. Windows installer
4. Release notes
5. Web pages
6. README, etc. (really this should be never been read at all)

The TranslationInformation page should be rewritten following this list. Also, additional information for how to translate the windows installer should be added: it's not too difficult to translate, and it will save having to do a separate build with a translated installer. I would like to add the information about translating the installer, some time in the future :).

That's what i'm currently trying to do. More news within one ore two weeks I think.

regards,

Matiphas

Hi, many thanks for committing the tutorials.

Regards!

2006/5/8, bulia byak <buliabyak@...5...>:

Scislac, any news on committing the tutorials?

On 5/8/06, Matiphas <matiphas@...9...> wrote:

...

Le lundi 08 mai 2006 à 14:04 -0700, Arpad Biro a écrit :

...

Hi,

Xavier:

...

I have some questions about the translation of tutorials for Inkscape. My team translated the SVG documents recently. We know the right way is to translate them on XML format, but we needed them on SVG in order to integrate them on a Windows package we deployed. We are going to move them to the XML tutorials, however I submitted the SVGs some months ago through the patch tracker but they haven't been accepted yet. I'm not sure if you don't accept SVG tutorials anymore (thus forcing to port them to XML, which anyway I think is the correct way) or if you just didn't saw them.

Does anyone have current info on this? I'm not sure whether the XML/SVG info on page

http://wiki.inkscape.org/wiki/index.php/TranslationInformation

is still valid or not. Can/should we still commit SVG tutorial files directly to SVN?

Last time i've played with this, it was OK. I used xsltproc in order to generate svg/html from the docbook files (combined with the appropriate xsl files found in the cvs/svn)

Regards,

Matiphas

---

Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmdlnk&kid%120709&bid&3057&d... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

---

Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmdlnk&kid%120709&bid&3057&d... _______________________________________________ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator

--

Google talk: xavi.conde a gmail.com

------------------------------------------------------------------------------------------------- Hackers (and creative people in general) should never be bored or have to drudge at stupid repetitive work, because when this happens it means they aren't doing what only they can do — solve new problems.

Eric Steven Raymond (http://catb.org/~esr/faqs/hacker-howto.html) -------------------------------------------------------------------------------------------------