I did similar thing, you're talking about. I extend the backend to
support flattened YML files, so all my translations files look like:
en:
activerecord.errors.messages.accepted: "must be accepted"
activerecord.errors.messages.blank: "can't be blank"
The reason of doing it was complications I met with working on huge
piece of data in nested yml files. Having few thousands keys in few
translations files, was making me furious when I needed rename
translation keys, move them to another namespace etc. and had to
scroll a lot, looking and wondering what is namespace of the key.
Also, resolving merge conflicts, checking for missing translations in
other locale files are much easier, when you have and see full key.
Having the Fast backend in latest i18n, implementing it was quite
simple and it's in my fork of i18n:
http://github.com/knapo/i18n/blob/master/lib/i18n/backend/zuper_fast.rb
Btw, as Fast backend uses flattened hashes, I believe that when you
invert I18n.backend.flattened_translations hash you'll get what you
need.
Regards,
Krzysztof Knapik
2010/1/22 Joaquin Rivera Padron <joah...@gmail.com>:
> --
> You received this message because you are subscribed to the Google Groups
> "rails-i18n" group.
> To post to this group, send email to rails...@googlegroups.com.
> To unsubscribe from this group, send email to
> rails-i18n+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rails-i18n?hl=en.
>