[l10n] Indicator menus of "Accessibility" should behave like other indicators

Bug #1134755 reported by Hendrik Schrieber
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Translations
Expired
Low
Unassigned
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Same as bug 1040438 but it has only been fixed partially.

All indicators are in the selected language during installation except for the accessibility indicator. It changes to the desired language after clicking »Next« in the language selection window but before this it is in English although it should use the same language as other indicators.

Tags: saucy ubiquity
Revision history for this message
Hendrik Schrieber (hennekn) wrote :

Ok, let me restate the problem:

The indicator is in English before clicking on »Next« within the window where you select the language. However, all of the other indicators are already in German at this time if »German« is selected.

Changed in ubuntu-translations:
assignee: nobody → Ubuntu German Translators (ubuntu-l10n-de)
no longer affects: ubiquity
Revision history for this message
Hendrik Schrieber (hennekn) wrote :

Don't know why you marked this as not affecting ubiquity. This is clearly a localization issue and not a translations problem. There is probably something wrong with the way the indicator determines which language to use. It should work the same way as for the other indicators.

The problem still exists in Saucy.

description: updated
tags: added: saucy ubiquity
removed: raring regression
summary: - [l10n] Indicator menus of "Accessibility" should be localized for
- installer
+ [l10n] Indicator menus of "Accessibility" should behave like other
+ indicators
Changed in ubuntu-translations:
status: New → Triaged
importance: Undecided → Low
assignee: Ubuntu German Translators (ubuntu-l10n-de) → nobody
Revision history for this message
Colin Watson (cjwatson) wrote :

Hendrik, we marked this as not affecting "ubiquity" (which, on its own, refers to the upstream project entity in Launchpad) because there is absolutely zero point in tracking ubiquity bugs in two places. We do not use the ubiquity project in Launchpad for bug tracking; the "ubiquity (Ubuntu)" task on this bug (that is, the ubiquity source package in Ubuntu) is entirely sufficient.

I realise that the distinction between upstream projects and distribution source packages in Ubuntu can be confusing if you aren't closely familiar with Launchpad's taxonomy. But please take our word for it and don't open tasks on the ubiquity upstream project; we want them all on the source package in Ubuntu instead.

no longer affects: ubiquity
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1134755

and any other logs that are relevant for this particular issue.

Changed in ubuntu-translations:
status: Triaged → Incomplete
Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu Translations because there has been no activity for 60 days.]

Changed in ubuntu-translations:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.