#27069 closed Cleanup/optimization (fixed)
Documentation for what's possible to import as _
Reported by: | Mattias Loverot | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Had an issue where I attempted to import pgettext as _ which failed. Thought I could add some documentation which might be helpful for someone else.
Change History (6)
comment:2 by , 8 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 8 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
comment:4 by , 8 years ago
Repeating what I wrote on the PR:
The underlying issue is that xgettext consider _
as a shortcut to a "simple" translation function. By simple, hear "one extractable string in the first parameter with no domain, context, plural, etc.". With a lexical analysis, it would not be possible to distinguish between different function signatures aliased to the same _
shortcut.
Note:
See TracTickets
for help on using tickets.
https://github.com/lovmat/django/tree/ticket_27069