gettext parser stumbles over "#~|"
Bug #286043 reported by
Jeroen T. Vermeulen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Jeroen T. Vermeulen |
Bug Description
Some gettext files combine the "#~" marker (for obsolete messages) with the "#|" one (for fuzzy messages' previous msgids) to produce "#~|". The parser ignores "#|" but tries to make sense of "#~", and then fails because it next sees "|".
Simplest fix for this is to ignore lines that start with "#~|". (See also bug 182895).
description: | updated |
Changed in rosetta: | |
assignee: | nobody → jtv |
importance: | Undecided → High |
milestone: | none → 2.1.11 |
status: | New → In Progress |
Changed in rosetta: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is a serious issue for Kubuntu, since many of its critical components ran into this bug. We are going to work around this for 8.10 (since time is of the essence) by providing Jeroen with a translations tarball from which all lines starting with "#~|" have been stripped. Jonathan sent this to Jeroen earlier today and we're waiting for feedback now.