Joshua Harvey a écrit :
>
> I also encourage people who need i18n in Rails to try my Globalize
> plugin at http://globalize.diluvia.net, and to help out with feedback,
> bug reports, patches, and advocacy.
Hi Joshua,
I'd like to talk with you of two big points:
1.a choice of lang (passed through uri : host.tld/lang/uri -> maybe
patch the routing system to implement a pre-routing of the lang ?)
1.b detect the preferred lang from the browser for the home page (when
no lang is received from uri)
2. Be able to use (and even maybe generate) well designed db schemas:
Prior trnaslation:
Table
=====
id
translatable1
translatable2
untranslatable
After globalizing:
Table Table_texts
===== ===========
id <------------\ id
untranslatable \---- table_id
lang
translatable1
translatable2
unique(table_id, lang)
I use this second schema here. It's more fine grained and allows for
different search schemes or indexing. But it needs a bit mor work to
make it work with globalize...
If you agree we need all this, direct me and I'll write all this.
--
Jean-Christophe Michel
_______________________________________________
Rails-core mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-core
