Unsetting is_imported translations doesn't work from uploads

Bug #312130 reported by Данило Шеган
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
High
Unassigned

Bug Description

When there is an existing imported translation (packaged/upstream), it's impossible to override it with an empty imported translation in the future.

This usually happens if a someone had inadvertently copied a different language PO file to another one in a package without being properly cleaned up (at least, this is the only few cases I've encountered so far).

However, more important might be cases where maintainers fix translations so programs don't crash (i.e. C format strings and similar), when they usually just mark the string as fuzzy (which is equivalent of empty in LP).

Revision history for this message
Данило Шеган (danilo) wrote :

Btw, we should note that this was an intentional design choice in early days so we keep at least one good translation (assumption was that whatever is coming from a package is good). Maybe we should revisit it.

Changed in rosetta:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Данило Шеган (danilo) wrote :

Changing this with message sharing would cause more problems than solve (i.e. older untranslated release might get a half-empty translation imported, and then that would unset newer fully translated one as well). We won't do it.

Changed in rosetta:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.