Re: [sup-talk] i18n?

[William Morgan <wmorgan-sup@masanjin.net>]

Hi Christopher,

Reformatted excerpts from Christopher Bertels's message of 2009-10-05:
> I'd like to hear some feedback and/or opinions/suggestions and would
> like to see it integrated into sup. I'll add more translations, if I
> find anything I havent missed yet and that is part of the user
> interface.

This looks great. A couple comments:

1. I would prefer that uppercase substitution symbols made lowercase.
The uppercase seems weird and un-Rubyish to me.

2. I think it would be nice to have a simple module along the lines of:

  module M17n
    def m s, o={}; I18n[m, o] end
  end

and to have that be the primary entry point when you want a translated
string. Then classes can include that module if they want m17n support,
and instead of writing

  I18n["text", { :var => value }]

you can have

  m("text", :var => value)

which is a little easier to read, IMO.

3. Should we call it m17n instead of i18n? I think that might be a
little more accurate. Perhaps too nitpicky. What do you think?

4. A finishing touch would be to have sup-config ask the user what
language they are interested in.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk