e issue in our docs by:
- calling USE_I18N-related stuff "translation" and USE_L10N-related
"formatting",
- avoiding the words "internationalization" and "localization" as much as
possible,
- warning that the names of the settings are historical.
In th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Aymeric,
On 10/22/2011 05:02 AM, Aymeric Augustin wrote:
> On IRC, Bas Peschier pointed out that the current docs follow the
> "definitions" of i18n and l10n.
>
> In fact, the code (in particular the settings) uses the "gettext"
> definitions whil
t; http://en.wikipedia.org/wiki/Internationalization_and_localization
Does this make sense?
--
Aymeric Augustin.
On 22 oct. 2011, at 00:10, Aymeric Augustin wrote:
> Hello,
>
> Maybe it's just me, but I find the i18n docs quite confusing, and I often
> struggle to locate the i
Hello,
Maybe it's just me, but I find the i18n docs quite confusing, and I often
struggle to locate the information I need:
https://docs.djangoproject.com/en/1.3/topics/i18n/
For instance, I don't understand why:
- the index page immediately dives into gettext technicalities;
- /t
