>>One of the reason rails is so nice to work with is that "it was in
an
>>> app first". You''re right, it won''t make it
into 1.0 as noone who
>>> contributes to rails has needed to build multi lingual applications
>>> yet.
>
> IMO, if Rails is to have a major impact in the long run, this
> criteria for adding crucial features like i18n must change.
I don''t think anyone would say that i18n is not important to the future
of any web framework. Rails will support it at some point, no doubt.
However, it''s absolutely critical that this "criteria" of
adding
features only when they are a) really needed and b) extracted from an
existing project be maintained. IMHO, it would be a mistake to try to
design i18n support simply out of thin air, or to try to emulate the
support offered in some other framework, without a major project behind it.
This does not mean "it''s not valid until 37signals shows us the
way." It
seems to me, though, it would be best if Rails'' i18n support chould be
extracted, if possible, from a big site developed by a small team.
43Things has internationalized: http://de.43things.com/ What are the
chances they''d be willing to share their approach and code?