Hi Sven,

I am happy to hear, that we totally agree on the important items.

We should tackle the problems, as you are describing:

1. use string interpolation instead of concatenation everywhere

 > Great, thanks for pointing that out. This is a known issue and I agree
 > that we should get that fixed. There are few options to do that and
 > discussion about that has already started over at
 > http://groups.google.com/group/rails-i18n

2. introducing lambda support for error messages for maximum flexibility

 > Integrating lamda support to the I18n API has been a request for a
 > long time. It's also useful for localizing dates to rather funky rules
 > and such.

3. discuss/improve the API. My opinion always was, that supporting
    different *storage* backends is a good idea. Every developer is
    comfortable with yaml files. Others can use gettext
    specific .mo or .po (bypassing, as you pointed out,
    the dated compilation approach). On the other hand, some things
    should not be optional and can not be plugged through the API,
    but lets discuss this later, after we succeeded with the first
    two things.

 > Please think about the I18n API in Rails as similar to the Rack API
 > support. Rack allows for previously unseen extensibility and
 > exchangeability of concurrent implementations of rather focussed
 > features.

This is an excellent example!

It illustrates two things: successful technical design and importance of 
experience and solution maturity. Instead of reinventing the wheel, the 
Ruby community adopted successful and proven solution from the Python 
world, where it is known under the name of WSGI, and further improved it.

I was talking about the gettext whole the time not because I admire the 
obscure .mo file format
http://www.gnu.org/software/gettext/manual/gettext.html#MO-Files , but 
because the folks at GNU have already seen all the possible problems and 
addressed them in the design, the tools, and the best practices.
http://www.gnu.org/software/gettext/manual/gettext.html#Why

Best Regards and see you
on the http://groups.google.com/group/rails-i18n shortly,

Vladimir


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" 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-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to