Comments on: Sunday thought: Discarding localizations from extensions

By: Adrian Kalla

Adrian Kalla — Mon, 30 Aug 2010 12:45:06 +0000

“Use translate.google.com as a first-order approximation for new keys”

This is the worst thing someone can do – Google’s translations are usually so bad, that it is better to leave the string in English or even better: drop the locale for as long as someone doesn’t translate it “manually”.

By: Wladimir Palant

Wladimir Palant — Mon, 30 Aug 2010 09:21:06 +0000

Yes, I made the same experience unfortunately – it is getting increasingly harder to get locales updated. I don’t expect a reply from translators, many of them simply aren’t comfortable writing English. But some of them simply disappear and finding a replacement is very hard. In Adblock Plus 1.2 I had to drop some locales, for the first time ever. I now hope to improve the situation by moving the translation process from Babelzilla to my own platform where it is better integrated with the development and accessible to more users.

By: Antoine Turmel (GeekShadow)

Antoine Turmel (GeekShadow) — Mon, 30 Aug 2010 00:38:05 +0000

Too bad

“Contacting localizers asking to complete localization without receiving reply (bad citizens???)”
Yeah I got this issue too…

now I ask to the Songbird community people I know for translating locales in their languages (Sweden, Dutch, French…)

By: Noel Grandin

Noel Grandin — Sun, 29 Aug 2010 21:30:00 +0000

Two tactics can reduce your burden

(1) Use a fallback default locale for the keys that don’t have translations
(2) Use translate.google.com as a first-order approximation for new keys

By: Mic

Mic — Sun, 29 Aug 2010 19:29:34 +0000

It would be great if you could include further localizations after the extension was made public/updated.

By: Think Global, Make Locales! » Blog Archive » How to maintain extension translations on the long term?

Sun, 29 Aug 2010 19:18:58 +0000

[...] to our site and system (not to mention the awesone Externalize strings extension), recently explained on his blog why he could not afford maintaining numerous locaizations for his extensions. Dear Davide, I know [...]

By: iacchi

iacchi — Sun, 29 Aug 2010 18:37:47 +0000

This decision is only yours, but looks a bit unfair. Why don’t you do something in the middle e.g. sending the new version to localizers (or publishing it in babelzilla) one week before release? After that week, who’s ready and sent you back the translation will be included, who didn’t won’t. Whithout loosing time waiting for localizers.

By: DarkEven

DarkEven — Sun, 29 Aug 2010 16:38:10 +0000

Did you try Babelzilla ?

http://www.babelzilla.org/

By: Tweets that mention Sunday thought: Discarding localizations from extensions « Snippets code from my daily experience -- Topsy.com

Sun, 29 Aug 2010 12:57:26 +0000

[...] This post was mentioned on Twitter by Planet Mozilla and Planet Repeater, Davide. Davide said: Sunday thought: Discarding localizations from extensions: http://wp.me/p3ITK-gV [...]