On Mon, 2009-02-02 at 18:26 +0100, Janos Guljas wrote: > > What version of gettext first contained recode-sr-latin? Most > > importantly, is it in gettext-0.15? If so, we're probably fine to rely > > on it, since that's a version that is commonly available for Windows. If > > it only appeared in, say, gettext-0.17, that's more of a problem. We're > > basically saying, these days, that if you need UTF-8 support, you can't > > use gettext-0.14.4 on Windows, which is one of the more commonly > > available binaries. For better or worse, we have a large Windows-based > > user base, including translators, so that audience is of importance, > > too. Compilation of binaries for Windows lags (by quite a few years in > > the gettext case, sadly) source releases. > > I wrote a replacement for recode-sr-latin from gettext as python 2.x > script. Somebody should test it on Windows.
Why is this needed? If recode-sr-latin is in gettext-0.15 and we decided to go with Cyrillic as the default, then there's no problem. It was only if the program was introduced in a very recent version of gettext (0.17, say) that there's a problem. Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Django-I18N?hl=en -~----------~----~----~----~------~----~------~--~---
