On Fri, Jul 29, 2011 at 11:56 AM, kenneth gonsalves <law...@thenilgiris.com> wrote: > On Thu, 2011-07-28 at 09:37 -0700, Lucy Brennan wrote: >> Before I comment, I would like to actually know if I got it right. In >> Django: >> >> USE_I18N: translation >> USE_L10N: localized formatting >> >> Right? > > wrong
Ok - seriously, Kenneth - if you're not going to take the time to provide a full answer (with sentences, capitalization and all the trimmings), please refrain from answering at all. A single word response doesn't contribute anything to the discussion, and just makes the whole community seem rude. Lucy: Although there are a lot of people that use L10N and I18N interchangeably, they are very distinct terms; any source you find that uses them interchangeably is categorically wrong. However, the two are very closely related, because localization usually happens in the presence of internationalization, and vice versa -- hence the common confusion. Although they share a Wikipedia page, if you read the rest of the page, you'll see they make a distinction between a localized system and an internationalized system. To a first approximation, your translation vs formatting dissection reflects Django's usage of the terms. I agree that Django's documentation doesn't do the best job at pointing out the distinction between the two (either in general, or in Django's interpretation. It would certainly be worth opening a ticket to point out this limitation of the existing docs. If you feel like contributing, producing a patch to Django's documentation to clarify the usage of i18n and l10n would be an excellent way to get involved. It has been my experience that newcomers often write the best high-level docs, because they're the people who don't have any preconceived ideas, so they know what isn't obvious, and what needs to be explained. To the rest of this thread: I want to head something off at the pass right now -- consider it a core-team decision that we're not going to rename these settings. I18n and L10n are well understood terms to anyone who has been dealing with adapting software to multiple languages and cultures reasonable descriptions of what Django does with the USE_I18N and USE_L10N settings, and we're not going to change the values because someone comes up with a slightly better name. There needs to be something fundamentally wrong or misleading before we would even consider changing the name of a setting, and given that these settings have been in the wild successfully for some time (I think it's 4 years in the case of USE_I18N) you're not going to find that here. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.