translation domains are assumed to be ascii but there is no restriction for that
Bug #214175 reported by
Carlos Perelló Marín
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
Right now, our language pack export code assumes that potemplate.
Changed in rosetta: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in rosetta: | |
milestone: | none → 1.2.5 |
Changed in rosetta: | |
milestone: | 1.2.5 → 1.2.6 |
Changed in rosetta: | |
milestone: | 1.2.6 → none |
visibility: | private → public |
Changed in rosetta: | |
importance: | Medium → High |
To post a comment you must log in.
Lowering priority since language codes must be one of a limited, known, ASCII-only set, and translation domains are entered by admins only.
If we want to use the database's valid_name() function to check translation domains, we must be careful that there be no important use cases for underscores or other reasonable characters it disallows.