On Wed, Sep 8, 2010 at 2:43 AM, Marnen Laibow-Koser
<[email protected]> wrote:

> I recommend not using an army of YAML files.  Instead, install
> fast_gettext, which adopts the GNU gettext approach of using PO files.
> The advantages here are:
> * Readable string keys instead of weird symbolic ones
> * Since PO files have been widely used in software localization for some
> time, there's lots of translation tool support for PO files, and many
> translators already know how to work with them.

It's pretty easy to take YAML and transcode them to other types of
files (and vice versa) with rake tasks.  We haven't done it for PO
files, but we have for CSV and XML files to be imported to Excel for
translators and then take their Excel XML schema output and pull it
back to YAML files.

The advantage of the YAML stuff is interpolation for reuse of
translation. I.e. each translated string becomes a potential building
block for other string translations, e.g.

base:
  foo: foo
  bar: bar
  new: new
  new_foo: "{{t.base.new}} {{t.base.foo}}"
  new_bar: "{{t.base.new}} {{t.base.bar}}"

Then when I create a new locale's translation I can either replace the
base value for "new" in one place or (if grammatically necessary) edit
"new_foo" and "new_bar".  It's a potential big time saver for larger
systems and it helps ensure UI consistency of nouns and verbs.

If you don't expect to do this sort of sophisticated reuse of
translations, then Marmen may be right. It's simplest to go with the
translation industry's standard PO files.

>
> If you're looking for a Facebook-style community translation interface,
> that Translate plugin certainly looks promising (though I've never used
> it either).
>

The Translate plugin ISN'T really suitable for a Facebook-style
community translation interface, at least without significant work.
It is geared towards privileged users adding whole site translations.

You might be able to fork and hack it to be more community oriented,
but it wouldn't be trivial work.

Cheers,
Walter

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to