Starting from development version 0.5.5.1479, we have dropped the awkward label-file based localization system, and adopted a much more versatile localization process, based on GNU gettext.
To get Gregarius to speak to you in your mother tongue, all you have to do is configure your browser and instruct it to download pages in your preferred language. At the time of writing, 16 languages are supported, and more are being added every week.
What if yours isn’t supported yet? Well, the best solution is to write a translation yourself:
Note: a more in-depth (and slightly more technical) description of this process is available on the Wiki.
Either way, if you’re interested in the internationalization and localization processes of Gregarius, please join the gregarius-i18n mailing list.
I was kindly asked to post a bit more and keep you guys updated on what is going on behind the scenes of the fancy Gregarius development world. So here is what you should expect will be in the next release, which will probably be released as 0.6.0 - codename [suggest a fancy codename here]
Multi User Support
This is probably the single most requested feature, e.g. being able to have several users, each one having his/her own set of feeds and playing a distinct role (Admin, User, Visitor), … everything happily running off a single installation.
Now, the reasons why this hasn’t been done before are rather simple: 99% of the current Gregarius users won’t need this feature, and it’ll require a huge refactoring both of the code and the database schema.
Nevertheless, we think it’s a necessary step on the road to TWD and have started discussing the design.
Database Gurus willing to lend a hand, please contact your nearest Gregarius developer.
Better Localization
We’re currently migrating from an clunky, label-files-based localization system to a more modern gettext-powered l10n engine. We’ve picked the excellent PHP-gettext library, which is also used by WordPress, among others.
Still, it’s a tedious and repetitive search-and-replace work, which I hope to finish as soon as possible.
New RSS Parser?
We’ve started evaluating SimplePie as a drop-in replacement of the aging MagpieRSS, whose Atom 1.0 support isn’t quite there yet.
Although still in beta phase, SimplePie looks quite sexy and well designed.
In a nutshell, these should be the most interesting new features in the next release. We’re still in the design phase, so you still got plenty of time to suggest killer-features you would like to see included, before 0.6.0 goes gold :)