#24247: makemessages command should use case insensitivity when checking for
paths
in LOCALE_PATHS
-------------------------------------+-------------------------------------
Reporter: thyleung | Owner: thyleung
Type: Bug | Status: new
Component: | Version: 1.6
Internationalization |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by thyleung):
* status: closed => new
* resolution: wontfix =>
Old description:
> The makemessages command should use case insensitivity when checking for
> paths in LOCALE_PATHS
>
> For example, I set LOCALE_PATHS to the path ‘locale’
>
> The .po files will only be generated if the locale folder is named with
> the same lowercase spelling of ‘locale’.
>
> If the locale folder has the name “LOCALE”, Django will not find the
> folder ‘locale’, and makemessages will throw out this command error:
>
> Error: This script should be run from the Django SVN tree or your project
> or app tree. If you did indeed run it from the SVN checkout or your
> project or application, maybe you are just missing the conf/locale (in
> the django tree) or locale (for project and application) directory? It is
> not created automatically, you have to create it by hand if you want to
> enable i18n for your project or application.
New description:
The makemessages command should use case insensitivity when checking for
paths in LOCALE_PATHS
For example, I set LOCALE_PATHS to the path ‘locale’
The .po files will only be generated if the locale folder is named with
the same lowercase spelling of ‘locale’.
If the locale folder has the name “LOCALE”, Django will not find the
folder ‘locale’, and makemessages will throw out this command error:
Error: This script should be run from the Django SVN tree or your project
or app tree. If you did indeed run it from the SVN checkout or your
project or application, maybe you are just missing the conf/locale (in
the django tree) or locale (for project and application) directory? It is
not created automatically, you have to create it by hand if you want to
enable i18n for your project or application.
Rationale: The problem I came across was that certain translations were
not showing in Rosetta on the beta server (web server), but were showing
on the development server (Mac OS System). After much investigation, it
was because the web server was case sensitive, thus Rosetta was not able
to recognize the LOCALE_PATH and bring in the proper translations.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/24247#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.19687b6651823b189c3788dbfc641c64%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
