From: Tero Tilus <tero@tilus.net>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] i18n?
Date: Fri, 23 Oct 2009 10:00:21 +0300 [thread overview]
Message-ID: <1256280223-sup-736@tilus.net> (raw)
In-Reply-To: <1254487575-sup-5468@thinkpad-ubuntu>
Excerpts from 's message of pe loka 02 15:52:47 +0300 2009:
> Please tell me what you think.
Why not default to the english strings as translation keys and
fallback to key itself in case of missing translation? This has imo
several advantages. You can go grep the source using what you see in
sup UI (instead of first greping language yaml). Adding new strings
is cumbersome with (mostly unnecessary) key indirection. Code is more
readable when messages are inlined. If you change a string a check of
translations is forced (there is no translation for the changed
version). Most translation workflow tools expect this kind of
behavior.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-23 7:00 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
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 [this message]
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=1256280223-sup-736@tilus.net \
--to=tero@tilus.net \
--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