Opened 3 years ago
Closed 3 years ago
#33722 closed Cleanup/optimization (wontfix)
Change default domain in JavaScriptCatalog view from 'djangojs' to 'django'.
| Reported by: | Wim Feijen | Owned by: | nobody |
|---|---|---|---|
| Component: | Internationalization | Version: | 4.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Claude Paroz | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi,
When using "makemessages -l nl" and "compilemessages -l nl" , Django creates "django.po" and "django.po" files by default.
However, when using JavaScriptCatalog view, it supposes that the default domain is "djangojs", which is different. I find this confusing.
My proposal is to change the default domain to "django" in Javascriptcatalog; or else to check for both "django" and "djangojs" files if no domain is given.
At the least, we could change the documentation and hint that you might want to change the default to "django":
Translation domain containing strings to add in the view output. Defaults to 'djangojs'. *You might want to change this to 'django'.*
Change History (1)
comment:1 by , 3 years ago
| Cc: | added |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
| Summary: | proposal: change default domain in JavaScriptCatalog view from 'djangojs' to 'django' in order to match the default translation file names → Change default domain in JavaScriptCatalog view from 'djangojs' to 'django'. |
Note:
See TracTickets
for help on using tickets.
Different domains are used on purpose as they allow distinguishing translation from JavaScript files and
.py,.txt,.htmlfiles. Using the same domain would remove the option to procees them separately and would be backward incompatible.If you don't agree, you can start a discussion on DevelopersMailingList, where you'll reach a wider audience and see what other think.