Opened 14 years ago
Closed 12 years ago
#14540 closed Bug (fixed)
Wrong localization (L10N) thousand separator & decimal point character for Puerto Rico
Reported by: | Roberto Rosario | Owned by: | nobody |
---|---|---|---|
Component: | Internationalization | Version: | 1.2 |
Severity: | Normal | Keywords: | L10N, Puerto Rico |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The es-PR LANGUAGE_CODE incorrectly returns dot '.' as the thousand separator and comma ',' as decimal point symbols, which is inverted. The locale 'en-PR' is however correctly coded.
Attachments (1)
Change History (10)
comment:1 by , 14 years ago
Component: | Uncategorized → Internationalization |
---|
by , 14 years ago
Attachment: | formats.py added |
---|
follow-up: 3 comment:2 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Django currently has no Puerto Rico translation/format support. Maybe you are using files provided by another Django-based project (in that case you can reporte this to its maintainers) or locally created file (in which case you can edit the file yourself)?.
Of course, we would gladly add such a translation if anyone contributes one in good shape to Django.
comment:3 by , 14 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Replying to ramiro:
Django currently has no Puerto Rico translation/format support. Maybe you are using files provided by another Django-based project (in that case you can reporte this to its maintainers) or locally created file (in which case you can edit the file yourself)?.
Of course, we would gladly add such a translation if anyone contributes one in good shape to Django.
I'm using the official Django 1.2.4 files as downloaded by pip from djangoproject.com. The formats.py file attached here was create by myself by copying django/conf/locale/es/formats.py and editing it to provide the missing format support for es-PR locale, as for translation/i18n support the general 'es' translation is adequate for Puerto Rico, no specific 'es-PR' translation is needed.
Maybe the ticked title is what's wrong, a more appropriate title should be: "Include specific localization support for Puerto Rico 'es-PR'"
comment:4 by , 14 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:5 by , 13 years ago
Severity: | → Normal |
---|---|
Type: | → Bug |
comment:8 by , 12 years ago
Status: | reopened → new |
---|
comment:9 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Location format file to es_PR location