As the dev cycle for the first release of rehash winds down (one remaining bug before we're ready to deploy), I've turned my attention another large site-related project, specifically the possibility of internationalizing and localizing the site. Internationalizing a very large legacy codebase is a lot of work, and I want to gauge interest. For clarification, this work would translate the UI, and the site interface itself, and not the articles. Historically, I'm aware of two successful translation project, BarraPunto, and Slashdot.JP. However, both of those projects did so by simply rewriting the templates in their native language instead of using a more flexible system that would allow for dynamic processing.
After a few hours of cursing, I was successful in modifying rehash to use Locale::Maketext::Lexicon, and load translations dynamically from gettext when a template is loaded. The practical upshot is that if I continue with this effort, we will be able to import all the static strings in rehash, and translate them through any service that can handle standard gettext POT files (such as Launchpad Rosetta), then have rehash load the specific language on the fly depending on a user's settings, or their browsers preferences. This also has the benefit that translators would only require a minimal amount of HTML knowledge would be required to successfully translate rehash.
What I want to know is the following:
As long as the first two answers are yes, I'll push to get a localized codebase in place for the next rehash development cycle (likely landing in July or August). Please note there is a *lot* of strings to be translated, I'm expecting upwards of a couple thousand once I've finished scrubbing through all the templates and libraries. If you are interested in this, please note your native language below, and I'll get in contact with you once we're ready to start doing translation work.
Just to show that this is indeed possible, here's the output of the generate-pot-files script, with the few templates I've gone through:slashlithium~/src/rehash-ncommander$ bin/generate-pot-files * themes/default/templates/about;about;default - Total strings extracted : 21 * themes/default/templates/admin;menu;default - Total strings extracted : 7 * themes/default/templates/articlemoved;misc;default - Total strings extracted : 3 * themes/default/templates/bannedtext_ipid;misc;default - Total strings extracted : 2 * themes/default/templates/bannedtext_palm;misc;default - Total strings extracted : 2 * themes/default/templates/main;404;default - Total strings extracted : 11 READING PO FILE : i18n/rehash.pot WRITING PO FILE : ./i18n/rehash.pot DONE
(Score: 2) by krishnoid on Tuesday May 19 2015, @05:36PM
I'd prefer to have stories with hundred/s of comments, rather than many stories with only a few comments. The readership here is intelligent enough to present well-considered observations and questions in many different areas, and I'd like to see many more peoples' input on the stories, even if it was only for a trial period.
(Score: 0) by Anonymous Coward on Wednesday May 20 2015, @04:37AM
do you have any ideas for how to accomplish that?
(Score: 2) by krishnoid on Wednesday May 20 2015, @05:08PM
Maybe 2/4/6 stories a day. I suspect the readership on this site skews somewhat older, with people in routines and desk jobs, who could check the site in the morning, at lunch, late afternoon, etc. They'd then have more time to review their experience or questions on the topic, after which they could put in their carefully considered, and hopefully higher-quality 2/4/8/128 bits accordingly.
(Score: 0) by Anonymous Coward on Wednesday May 20 2015, @10:15PM
I don't think SN is suffering from too many stories. I only look at the ones that interest me, and when I'm done with those I go elsewhere, rarely do I go and read stories that I passed over the first time. If there were fewer stories here, I'd check less often, or maybe even not at all.