Comments on: Ubiquity Localization Update

By: Employment

Employment — Thu, 12 Nov 2009 06:37:52 +0000

Would you need to recompile them after every feed update?

By: neil

neil — Wed, 21 Oct 2009 18:21:48 +0000

I think you'll do find with the .po version. As I understand, it is far superior for using with mulitlingual programs, and Japanese/english should do well.

By: Essay writing

Essay writing — Wed, 14 Oct 2009 12:50:04 +0000

The overall goal for this release of Ubiquity is to come up with a format and standard for localization. It is a great goal I should say.

By: Gamre

Gamre — Tue, 06 Oct 2009 20:32:32 +0000

Awesome picture, Haha

By: coupons

coupons — Wed, 23 Sep 2009 03:10:37 +0000

The ID changes are also handled better in the gettext format and if you think a msgid (source text) is ambiguous, you can use the msgctxt field to specify the context and disambiguate it.

By: Tesco voucher codes

Tesco voucher codes — Wed, 23 Sep 2009 03:08:43 +0000

Do you mean we should make all localizable strings use keys in the code and put all localizable content in the localization files? So in the command?

By: mitcho

mitcho — Mon, 15 Jun 2009 08:14:18 +0000

Hi Axel,

Thanks for the comment. I've actually been playing around with jsgettext (http://jsgettext.berlios.de/) today and have been quite happy with it so far... It implements its own po parser but internally works with it as json. It even supports a json file format in addition to po, though I don't know how similar it is to what you and Gandalf have been working on.

We're hoping to get something workable out the door in the next week or so, though, so I think it's looking like po is the winner right now.

By: Axel Hecht

Axel Hecht — Mon, 15 Jun 2009 08:06:52 +0000

We shouldn't use po in its monolingual variant, that's just gonna make folks puke.

As for everything else, Gandalf and I are currently working on a json variant for l20n, which I owe .platform a post about. Not sure how well that's going to go, though.

I'm not sure how well re-implementing a po parser in js will go, it's usually easy to make the common things work, but if you're facing the output of a dozen different tools, you might have made faulty assumptions.

By: Julen

Julen — Sun, 14 Jun 2009 10:25:20 +0000

If you choose PO over properties the template thing is straightforward.

The ID changes are also handled better in the gettext format and if you think a msgid (source text) is ambiguous, you can use the msgctxt field to specify the context and disambiguate it.

Also please consider reading this about monolingual file formats: http://translate.sourceforge.net/wiki/guide/monolingual

By: marsf

marsf — Sat, 13 Jun 2009 07:18:02 +0000

> Is that what you mean?

Yes. (except for verb names.)

By: mitcho

mitcho — Sat, 13 Jun 2009 01:44:29 +0000

Do you mean we should make all localizable strings use keys in the code and put all localizable content in the localization files? So in the command,

_('helloMessage')

and then

hello.preview.helloMessage=Hello, world!

Is that what you mean?

By: mitcho

mitcho — Sat, 13 Jun 2009 01:44:11 +0000

Do you mean we should make all localizable strings use keys in the code and put all localizable content in the localization files? So in the command,

_('helloMessage')

and then

hello.preview.helloMessage=Hello, world!

Is that what you mean?

By: mitcho

mitcho — Sat, 13 Jun 2009 01:42:49 +0000

Stas, if we go with gettext (po) files, we'd be reading them in using JavaScript, and neither of those public libraries for JS/gettext only support po, not mo. If we just use this as is, we won't need to deal with the compiling issue.

By: marsf

marsf — Sat, 13 Jun 2009 01:39:29 +0000

Mozilla localizers are familiar with ".properties" format. If using ".properties", there is "English.properties" file and this makes easy to start localize. I think that it isn't needed any spaces in the key.

For external command feeds, define them within the command like this? CmdUtils.CreateCommand({ ... messages: { execute.hello: [en: "Hello!", ja:"こんにちは！"], preview.hello: [en: "Hello!", ja:"こんにちは！"] } });

By: Stas Malolepszy

Stas Malolepszy — Fri, 12 Jun 2009 23:06:00 +0000

gettext files need to compiled before you can use them. Would you need to recompile them after every feed update?

By: Blair McBride

Blair McBride — Fri, 12 Jun 2009 11:36:52 +0000

I'm torn between the two options here. I prefer the syntax of .properties (and the built-in tools), but like that .po works such that you can do:

msgid "Hello, World!" msgstr "Hallo, Welt!"

Where the ID is just the English version of the string. No need to decide on some normalized ID that conforms to arbitrary rule. When translating, you get the string you're translating from without needing to look up the source code, try the command, or have an additional comment (which I tihnk is usually what happens in Mozilla-land). And as an upside, if the original text changes and needs re-translated, then you get the ID change for free.

By: toniher's status on Friday, 12-Jun-09 10:57:56 UTC - Identi.ca

toniher's status on Friday, 12-Jun-09 10:57:56 UTC - Identi.ca — Fri, 12 Jun 2009 10:57:59 +0000

[…] Ubiquity localisation update: http://mitcho.com/blog/projects/ubiquity-localization-update/ […]