Russell
Thank you for the clarification. Just a couple of questions below ...
On 1/08/2011 11:09pm, Russell Keith-Magee wrote:
Close, but not quite.
* USE_I18N turns on the availability of translations at all. If
USE_I18N is false, all translation-related activities are no-ops.
* Assuming
On Mon, Aug 1, 2011 at 9:14 AM, Mike Dewhirst wrote:
> On 1/08/2011 8:09am, Lucy Brennan wrote:
>>
>> I read Wikipedia and Django docs. Now, after all this debate, I see that I
>> _did_ understand the definitions when I first read it.
>>
>> Given those definitions however, the meaning of USE_I18N
On 1/08/2011 8:09am, Lucy Brennan wrote:
I read Wikipedia and Django docs. Now, after all this debate, I see
that I _did_ understand the definitions when I first read it.
Given those definitions however, the meaning of USE_I18N and USE_L10N
are not obvious. Far, far, far from obvious. There _a
I read Wikipedia and Django docs. Now, after all this debate, I see that I
_did_ understand the definitions when I first read it.
Given those definitions however, the meaning of USE_I18N and USE_L10N are
not obvious. Far, far, far from obvious. There _absolutely_ has to be some
additional expl
On Fri, 2011-07-29 at 18:21 +1000, Mike Dewhirst wrote:
> https://docs.djangoproject.com/en/dev/topics/i18n/internationalization/
> - Internationalization
>
> https://docs.djangoproject.com/en/dev/topics/i18n/localization/ -
> Localization
>
> https://docs.djangoproject.com/en/dev/topics/i18n/d
On 29/07/2011 5:38pm, Masklinn wrote:
On 2011-07-29, at 05:56 , kenneth gonsalves 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
Th
On Fri, Jul 29, 2011 at 3:48 PM, Masklinn wrote:
> On 2011-07-29, at 06:58 , Russell Keith-Magee wrote:
>> 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
On Fri, 2011-07-29 at 09:38 +0200, Masklinn wrote:
> > wrong
> That's not what the Django documentation says, at least in my reading
> of it.
i18n - preparing an app to be customised in *any* locale
l10n - actually customising it for a *particular locale
One can do i18n *without* doing *any* tra
On 2011-07-29, at 06:58 , Russell Keith-Magee wrote:
> 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 l
On 2011-07-29, at 05:56 , kenneth gonsalves 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
That's not what
On Fri, 2011-07-29 at 12:58 +0800, Russell Keith-Magee wrote:
> >> 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
> tr
On Fri, Jul 29, 2011 at 11:56 AM, kenneth gonsalves
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 - serious
On 29/07/2011 1:56pm, kenneth gonsalves 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
http://en.wikipedia.org/wiki/Internationaliza
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
--
You received this message because you are subscribed to the Google Groups
"D
Did anybody read the links I supplied. Or maybe you were busy plussing on
Google+ :)
So there seems to be two pairs of definitions for I18N / L10N:
a) I18N / L10N ~ (building software so ready to be
locale-language-customized / making a specific localized version )
b) I18N / L10N ~ (translat
On 2011-07-28, at 18:37 , 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?
yes.
--
You received this message because you are subscribed to the Google Groups
"Django users
Before I comment, I would like to actually know if I got it right. In
Django:
USE_I18N: translation
USE_L10N: localized formatting
Right?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups
On 28/07/2011 2:28, Lachlan Musicman wrote:
> On Wed, Jul 27, 2011 at 16:53, kenneth gonsalves
> wrote:
>> On Tue, 2011-07-26 at 15:09 +0100, Tom Evans wrote:
>>> I strongly disagree, i18n and l10n have explicit and well known
>>> technical meanings, dating from the late 80s. It is right and prop
On Wed, Jul 27, 2011 at 16:53, kenneth gonsalves wrote:
> On Tue, 2011-07-26 at 15:09 +0100, Tom Evans wrote:
>> I strongly disagree, i18n and l10n have explicit and well known
>> technical meanings, dating from the late 80s. It is right and proper
>> to use those names in django, as they are used
On Tue, 2011-07-26 at 15:09 +0100, Tom Evans wrote:
> I strongly disagree, i18n and l10n have explicit and well known
> technical meanings, dating from the late 80s. It is right and proper
> to use those names in django, as they are used in every other project
> under the sun.
+1
--
You receive
On Tue, Jul 26, 2011 at 1:46 PM, Andre Terra wrote:
> On Tue, Jul 26, 2011 at 5:17 AM, Lucy Brennan
> wrote:
>>
>> (...)
>>
>> For both the USE_L10N and USE_I18N their effect is not obvious from
>> their naming. I suggest, that the description of these parameters in
>> https://docs.djangoproject.
On Tue, Jul 26, 2011 at 5:17 AM, Lucy Brennan
wrote:
>
> (...)
>
> For both the USE_L10N and USE_I18N their effect is not obvious from
> their naming. I suggest, that the description of these parameters in
> https://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs are
> made more precise.
Sorry for the late response to your reply. For some reason, I did not
get your response to my email. I only saw your answer because I went
to the online archive.
Here is a follow up for the googlers.
I have read the Django documentation, e.g.:
https://docs.djangoproject.com/en/dev/topics/i18n/,
If you look up those terms in the Django docs instead of Wikipedia I think
that will erase your confusion.
--
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 th
I believe I understand the general definitions of internationalization
and localization, e.g. as defined on
http://en.wikipedia.org/wiki/Internationalization_and_localization.
Internationalization is somewhat like building/designing a piece of
software for being used with different locales. And lo
25 matches
Mail list logo
