On Tue, 2009-02-03 at 09:07 +0100, Petar Marić wrote: > > Why is this needed? If recode-sr-latin is in gettext-0.15 and we decided > > Alas, only 0.14.4 is available on Windows.
Then if "recode" isn't in that, we can use the Python only version. However we get there, the end goal is that translators who choose to use Windows must be able to work without too much pain (a little pain, such as upgrading to the latest released binary version is fine, but not too much pain). > > 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. > > I've been thinking about this - if Cyrillic is indeed made the > default, it's kind of a backwards incompatibility. How is it backwards incompatible? If everybody who can read Serbian can reasonably be expected to read both Cyrillic and Latin, then it shouldn't be a problem. That being said, the fact that apparently most people can read both is also why I'm not particularly worried about which is the default. The goal is to be readable by the people who speak the language. So script choice in this case is quite possibly on the same level of importance as word choice or whether to use formal or informal forms of address: we pick something that works as the default and isn't too surprising to people. > Is that a problem > for 1.1? No. When we wrote the api-stability notes, I made sure that there's a part included that explicitly excludes translated strings (in fact, *any* strings) from any stability guarantee. Otherwise you wouldn't be able to update translations, since people might be relying on the fact that a certain string wasn't translated or was translated in a particular fashion. Then we'd have endless debates about what's a bug and what's an enhancement for translations and it would be horrible. Strings aren't part of the "stable API", in other words. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to django-i18n+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Django-I18N?hl=en -~----------~----~----~----~------~----~------~--~---
