"Search Applications" and "Search Files & Folders" messages are not translatable
Bug #644236 reported by
David Planella
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Translations |
Invalid
|
High
|
Unassigned | ||
Unity |
Invalid
|
Critical
|
Unassigned | ||
unity-lens-applications |
Invalid
|
Critical
|
Unassigned | ||
unity-lens-files |
Invalid
|
Critical
|
Unassigned | ||
unity-place-applications (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
unity-place-files (Ubuntu) |
Invalid
|
Critical
|
Unassigned |
Bug Description
In Unity, when choosing the "Applications" or "Files & Folders" launchers, the search boxes contain the "Search Applications" and "Search Files & Folders" respectively. These messages are not translatable and are always shown in English regardless of the locale used.
See the attached screenshots.
It would be great to have these translatable before the LanguagePackDea
Thanks!
Changed in unity-place-applications: | |
status: | New → Triaged |
Changed in unity-place-files: | |
status: | New → Triaged |
Changed in unity-place-files (Ubuntu): | |
status: | New → Triaged |
Changed in unity-place-files: | |
importance: | Undecided → Critical |
Changed in unity-place-applications: | |
importance: | Undecided → High |
Changed in unity-place-files (Ubuntu): | |
importance: | Undecided → Critical |
Changed in unity-place-applications: | |
importance: | High → Critical |
Changed in unity-place-applications (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in unity: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 2010-09-22 |
To post a comment you must log in.
Looking into this, there is a "Search %s", which might be responsible for showing these messages:
https:/ /translations. edge.launchpad. net/ubuntu/ maverick/ +source/ unity/+ pots/unity/ ca/14/+ translate
That string got added very recently and language packs have not yet had the time to catch up.
I'm marking this as Invalid for now, assuming that the next language pack will fix this, but I'll reopen if it doesn't.