From: Christopher Bertels <mailinglist@flasht.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] i18n?
Date: Tue, 06 Oct 2009 22:35:46 +0200 [thread overview]
Message-ID: <1254861112-sup-590@thinkpad-ubuntu> (raw)
In-Reply-To: <1254842820-sup-9099@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 1518 bytes --]
Excerpts from William Morgan's message of Di Okt 06 17:38:39 +0200 2009:
> This looks great. A couple comments:
Cool, good to know you like it!
> 1. I would prefer that uppercase substitution symbols made lowercase.
> The uppercase seems weird and un-Rubyish to me.
Ok, sounds good. I thought making them uppercase to let them be more
distict from the rest of the string but since we surround them by #{}
as in Ruby, you're making a good point here. I'll change that.
> 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.
Same here. Think this is nicer, too.
> 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?
I couldn't care less about the name - but I guess m17n fits better,
since it's just multilingualization. :)
> 4. A finishing touch would be to have sup-config ask the user what
> language they are interested in.
Alright, cool. I'll add that as well, once I have the rest changed & working.
Cheers,
Christopher.
--
================================
Christopher Bertels
http://www.adztec-independent.de
GPG Key ID: 0x2345b203
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-06 20:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 23:30 Christopher Bertels
2009-10-01 16:44 ` William Morgan
2009-10-01 18:15 ` Christopher Bertels
2009-10-01 18:24 ` William Morgan
2009-10-02 0:19 ` Christopher Bertels
2009-10-02 12:52 ` Christopher Bertels
2009-10-05 16:00 ` Christopher Bertels
2009-10-06 15:38 ` William Morgan
2009-10-06 20:35 ` Christopher Bertels [this message]
2009-10-06 21:56 ` Christopher Bertels
2009-10-20 12:33 ` Christopher Bertels
2009-10-21 12:29 ` Fabio Riga
2009-10-21 16:41 ` Guillaume Quintard
2009-10-21 18:37 ` Christopher Bertels
2009-10-23 7:00 ` Tero Tilus
2009-10-23 11:23 ` Fabio Riga
2009-11-02 12:12 ` William Morgan
2009-11-02 13:58 ` Tero Tilus
2009-11-02 14:59 ` William Morgan
2009-11-03 0:01 ` Fabio Riga
2009-11-03 1:22 ` Tero Tilus
2009-11-02 12:13 ` William Morgan
2009-11-03 14:05 ` Christopher Bertels
2009-11-03 15:08 ` Tero Tilus
2009-11-03 15:13 ` William Morgan
2009-11-03 15:23 ` Christopher Bertels
2009-10-01 18:21 ` Christopher Bertels
2009-10-01 18:33 ` Christopher Bertels
2009-10-01 18:47 ` Rich Lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1254861112-sup-590@thinkpad-ubuntu \
--to=mailinglist@flasht.de \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox