Rosetta overrules number of spaces
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
When a translated string should start with a certain number of spaces (so it will be aligned with previous strings), Rosetta mistakenly forces the number of spaces that the original string starts with.
For example, message number 10 on
https:/
should be aligned with message number 9: in the translated string the "killall" should be preceded by ten spaces. When I fill that in and click 'Save&Continue' and then go back to check, Rosetta has made it into seven spaces (but only for the first line, not the second). When I try to fool it and make the line start with \r, Rosetta will precede this \r with seven spaces and leave the ten spaces after it intact. (This will work, I guess, but is ugly.)
Also when a po file is imported, Rosetta breaks the correct alignment by changing the number of spaces.
Changed in rosetta: | |
assignee: | carlos → nobody |
importance: | Medium → High |
Changed in launchpad: | |
importance: | High → Low |
We implemented it that way while fixing bug #1036
Seems like we did a mistake assuming that "fix" of the spaces.