Hi
These advices are really good. I myself made the mistake to aim for
DRY .yml files
I have an addition to the string class .to_local(key) that allows me
to use my own coventions for key and that works really good
For example I have one enumeration.class.variable for enumerations and
one key models and one key controllers etc
Ialso have one key views to be DRY but I will now change that to the
deafults in Rails 3 (i.e controller.view.word)
I also use a set of common flash messages for the common actions
(sucess and failure)
Finally I use a method that stores translations of flash messages as
flash.controller.action.flash_key (ie. error_1,error_2..., success,
warning etc)
____________________________________________
Hans Marmolin
St: Larsgatan 50, 58224 Linköping, Sweden
Phone: +46708371202
13 feb 2011 kl. 14.15 skrev Sven Fuchs:
I thought I'd drop you a note that I've written up a few things
about what tools we are using to organize translations at work. I
get asked these questions a lot so maybe it makes sense to spam the
list with this :)
http://svenfuchs.com/2011/2/11/organizing-translations-with-i18n-cascade-and-i18n-missingtranslations
What other techniques/conventions do people apply?
Comments welcome!
--
You received this message because you are subscribed to the Google
Groups "rails-i18n" 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/rails-i18n?hl=en
.
--
You received this message because you are subscribed to the Google Groups
"rails-i18n" 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/rails-i18n?hl=en.
