Which tool to use for translation

Hi!
I would like to translate Rt tracker to slovenian languange for
version 3.8. I have already translated sl.po file for version 3.6.7,
and I woul like to upgrate this file to version 3.8. I already try to
do that with kbabel tool, using function Rough Translation, but when I
use translated file it did not work. The translation was more or less
ok, but when I use the file, the commands were still in english. Does
anybody has experience with using kbabel tool or is there any other
tool to do that?

Hi Marjan,

Many translators seemed to manage their translation files
independently on 3.6.x and 3.8.x (http://rt.easter-eggs.org/i18n/).
Simple “upgrade” can not work well as there are many differences between them.

In my case, I’ve made my 3.6.x translation file and submit it
reading Wiki pages (http://wiki.bestpractical.com/view/Translation).
Then I build my own dictionary and applied it to the RT 3.8
template file (http://rt.easter-eggs.org/i18n/3.8/lib/RT/I18N/rt.pot)
using “poedit” tool.
But it did not work well as there are so many little wording changes
in RT 3.8. So I corrected (erase or upgrade) a lot of entries by hand
using poedit tool. After a few days, I recorded the lowest “Not found in
src” score among other 3.8.x translations :-).From: “Marjan Bizjak” mbizjak@gmail.com
Subject: [Rt-devel] Which tool to use for translation
Date: Mon, 11 Aug 2008 13:59:19 +0200

I would like to translate Rt tracker to slovenian languange for
version 3.8. I have already translated sl.po file for version 3.6.7,
and I woul like to upgrate this file to version 3.8.
(snip)
Does anybody has experience with using kbabel tool or is there any
other tool to do that?

Shinji R. Yamane
Ph.D student / Graduate School of Interdisciplinary Information Studies, University of Tokyo

We’ve been starting to play with launchpad.net’s community translation
features.

https://translations.launchpad.net/rt/3.8/+pots/rt

This may be a much better way for folks to easily collaborate on
translation.

I’d really love your feedback.

JesseOn Aug 11, 2008, at 4:00 PM, YAMANE Shinji wrote:

Hi Marjan,

Many translators seemed to manage their translation files
independently on 3.6.x and 3.8.x (http://rt.easter-eggs.org/i18n/).
Simple “upgrade” can not work well as there are many differences
between them.

In my case, I’ve made my 3.6.x translation file and submit it
reading Wiki pages (http://wiki.bestpractical.com/view/Translation).
Then I build my own dictionary and applied it to the RT 3.8
template file (http://rt.easter-eggs.org/i18n/3.8/lib/RT/I18N/rt.pot)
using “poedit” tool.
But it did not work well as there are so many little wording changes
in RT 3.8. So I corrected (erase or upgrade) a lot of entries by hand
using poedit tool. After a few days, I recorded the lowest “Not
found in
src” score among other 3.8.x translations :-).

From: “Marjan Bizjak” mbizjak@gmail.com
Subject: [Rt-devel] Which tool to use for translation
Date: Mon, 11 Aug 2008 13:59:19 +0200

I would like to translate Rt tracker to slovenian languange for
version 3.8. I have already translated sl.po file for version 3.6.7,
and I woul like to upgrate this file to version 3.8.
(snip)
Does anybody has experience with using kbabel tool or is there any
other tool to do that?


Shinji R. Yamane
Ph.D student / Graduate School of Interdisciplinary Information
Studies, University of Tokyo


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Just a brief report:

To translate rt-3.8.x, I got password from launchpad.
https://translations.launchpad.net/rt/3.8/+pots/rt

I also got a notice that launpad.net is to apply BSD license for translations,
I believe it does not conflict with RT development.
http://help.launchpad.net/Translations/LicensingFAQ

Thanks,

Shinji R. Yamane
Ph.D student / Graduate School of Interdisciplinary Information Studies, University of TokyoFrom: Jesse Vincent jesse@bestpractical.com
Subject: Re: [Rt-devel] Which tool to use for translation
Date: Mon, 11 Aug 2008 21:44:32 +0100

We’ve been starting to play with launchpad.net’s community translation
features.

https://translations.launchpad.net/rt/3.8/+pots/rt

This may be a much better way for folks to easily collaborate on
translation.

I’d really love your feedback.

Hi Jesse,

Jesse Vincent wrote:

We’ve been starting to play with launchpad.net’s community translation
features.

https://translations.launchpad.net/rt/3.8/+pots/rt

This may be a much better way for folks to easily collaborate on
translation.

I’d really love your feedback.

This looks great. I just signed up to see if I could help.

However, right on the first translation I already noted a problem: The
source string starts with a space (see
share/html/Widgets/SavedSearch:117) which doesn’t show up in the html
output. Now that particular space isn’t really required (the resulting
space could probably be achieved with a style change if you’d like to
keep it), but I’d say it certainly is bad style to have a string
starting with a space. The same goes for ending on a space, which a
quick look at the .po file shows to be used aswell.

So what do you think? Should we just go on translating the strings
without regard for those spaces or would you like to fix that first?

Rolf.

keep it), but I’d say it certainly is bad style to have a string
starting with a space. The same goes for ending on a space, which a
quick look at the .po file shows to be used aswell.

Agreed.

Richard

keep it), but I’d say it certainly is bad style to have a string
starting with a space. The same goes for ending on a space, which a
quick look at the .po file shows to be used aswell.

Agreed.

If someone were to produce a patch today, I might be able to
squeeze it into 3.8.1, but more likely this won’t be corrected
until 3.8.2

-kevin

Just a brief report:

To translate rt-3.8.x, I got password from launchpad.
https://translations.launchpad.net/rt/3.8/+pots/rt

I also got a notice that launpad.net is to apply BSD license for
translations,
I believe it does not conflict with RT development.
http://help.launchpad.net/Translations/LicensingFAQ

I’m fine with that. It will hopefully help translation reuse.

However, right on the first translation I already noted a problem: The
source string starts with a space (see
share/html/Widgets/SavedSearch:117) which doesn’t show up in the html
output. Now that particular space isn’t really required (the resulting
space could probably be achieved with a style change if you’d like to
keep it), but I’d say it certainly is bad style to have a string
starting with a space. The same goes for ending on a space, which a
quick look at the .po file shows to be used aswell.

So what do you think? Should we just go on translating the strings
without regard for those spaces or would you like to fix that first?

I agree that they’re wrong. Translate the strings ignoring the spaces.
we’ll do an update to get rid of them all at once.