I personally prefer to have separate layouts for big chunks (like the Privacy Policy, for example), because YAML files become impractical for strings with more than 3 lines.
I just create policy.en.html.erb, policy.fr.html.erb, etc. This certainly introduces some duplication but you can avoid that a bit by creating partials that contain only the text that needs to be translated and rendering those partials from a common layout. On Wed, Aug 25, 2010 at 5:55 AM, Mitchell Gould <[email protected]>wrote: > I understand the practice of using yaml files for language translations > for basic things like labels, links etc. > > But for large chunks of text that might contain a lot of markup for > design etc what is the best way to offer sites in many languages? > > Is it better to have those layouts done in separate languages? > > Thanks > -- > Posted via http://www.ruby-forum.com/. > > -- > 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]<rails-i18n%[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.
