From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] i18n?
Date: Tue, 03 Nov 2009 17:08:00 +0200 [thread overview]
Message-ID: <1257260315-sup-830@tilus.net> (raw)
In-Reply-To: <1257256976-sup-1266@thinkpad-ubuntu>
Christopher Bertels, 2009-11-03 16:05:
> Should we use gettext then or rely on .yaml files for any additional
> translations then? I haven't used gettext yet and from what I
> remember it lookes weird, at least the ruby binding did. Maybe it's
> very easy though.
The l10n backend is an implementation detail. If we really need to we
can change backend later down the road if it is decoupled enough from
the i18n of sup itself. IMO you get to choose what we start with.
And William gets to choose if he accepts the patches or not. ;)
--
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-11-03 15:08 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
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 [this message]
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=1257260315-sup-830@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