moderated Re: On language and date localization
Andre Polykanine <andre@...>
Hi Mark,toggle quoted messageShow quoted text
Unfortunately, I don't know your stack, but basically if you use GNU
GetText for localization, the curve won't be too large: you just wrap
every text string in _() call, then you give the localizers a POT
file, and you receive from them PO/MO files. Then, if something is
changed on your side, it just is displayed in English, no errors, no
"unknown variable" or some stuff like that.
Again, I would be glad to help if needed. I've been working in
localization for six years now, so I believe I could be of some help.
With best regards from Ukraine,
Twitter: @m_elensule; Facebook: menelion
------------ Original message ------------
From: Mark Fletcher <firstname.lastname@example.org>
Date created: , 4:10:30 AM
Subject: [beta] On language and date localization
I agree that localizing Groups.io into different languages would be great, and it's on the TODO list. Unfortunately I can't dedicate the time to make it happen right now. One of the reasons is that once a site is localized, it's more difficult to add/change features. It slows development down a bit, for the rest of time. Also, no paid groups have asked for it (but have asked for other features not yet supported). Again, I think it's absolutely worthwhile. But I can't do it right now.
Date localization is a little easier, as it's a lot more limited in scope. The outstanding problem with getting that done right now (besides time) is that it's unclear if the library I use for the date picker on the add event page supports different date formats. That's on me to spend the time to figure out; I just haven't been able to yet.