Hi. Sounds like GLoc would be a good fit for those requirements. However regarding the points: - translation of rails error messages and stuff - translation of model and attribute names (in error messages) would be appreciated you would have to do that yourself.
Golly On 09/01/07, David Scheffel <[EMAIL PROTECTED]> wrote: > Hello there. > > I'm looking for a localisation plugin that is: > - easy to use (like java's ressource bundle for instance) > - flexible enough* > - fast > - well documented > > *My requirements in detail: > - I want to take care of my database schema on my own (don't want a > autom. handling like globalize) > - It should not torture my database; a file-based solution (with caching > in memory) would be appreciated > - Multiple languages per site required - but not necessarily per page > - nice to have: The choise of the active language for a request should > be up to me; not handled automatically > - Unicode should be possible > - Rails 1.16, 1.2 compatible > - should work with fragment/action/page caching > - would like to have a routing like: site.com/:lang/:controller/:action > - translation of rails error messages and stuff > - translation of model and attribute names (in error messages) would be > appreciated > > However I'm still not sure if it's preferable to have multiple rhtmls > per language or to have just one with multiple calls to something like > "getText(XXXX)". I could image that the multiple rhtml-solution is more > flexible and possibly faster. What do you think or what are you > experiences? > > Thanks.. > David > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Railsi18n-discussion mailing list > Railsi18n-discussion@rubyforge.org > http://rubyforge.org/mailman/listinfo/railsi18n-discussion > _______________________________________________ Railsi18n-discussion mailing list Railsi18n-discussion@rubyforge.org http://rubyforge.org/mailman/listinfo/railsi18n-discussion
