I take your points and I have certainly considered many of them. Like many things, there are design tradeoffs and you have to weigh them in your particular situation. I'm quite aware that linguistically these patterns aren't always useful and that is why they can be opted out of easily. They have sped up the process of translation for us, though (Chinese, Arabic, and Te Reo Māori so far). The professional translators for Chinese worked with Excel...
It should be noted that the "base" translations that act as building blocks are in supplement to standard named translation keys that correspond to the controller/action pattern of naming that you talk about with PO. I.e. if I'm translating "accounts.new.welcome", it will be in app/views/accounts/new template. It just may be that the value in the locale's .yml file is derived from base.welcome. Anyway, I imagine I'm providing more detail than is needed. 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.
