how to find my own language

[erikos]

Model a: translate the language options to the current locale: English, Spanish, German...

Model b: display the language options in the original language: English, Espanol, Deutsch...

The latter model is what gdm is using. I think it makes sense, because you should be able to always at least find 'your' language. Eben what are your thoughts on this?

[eben]

I think (b) is the appropriate choice.

[sayamindu]

The way GDM does this is not very efficient, unfortunately. I have attached a patch, but I don't know if this is going to make sense (performance wise) on an XO.
I had to resort to a hack to force sorting make sense though.

[sayamindu]

Patch (with a couple of Pylint fixes)

[erikos]

Hmm, it takes quite a while to load the language section (noticeable on my T61 as well). Is this the only way to generate the information? Maybe making it async?

[sayamindu]

I don't think it will be possible to add a better performing solution at this stage (we are already at freeze). Implementing an async solution would require us to implement a custom treemodel, which may be too invasive and complicated at this stage.

[garycmartin]

Replying to erikos:

Hmm, it takes quite a while to load the language section (noticeable on my T61 as well). Is this the only way to generate the information? Maybe making it async?

Testing Joyride 2631 on XO-1, this click take 6 or more seconds to have any visible effect! The user is given the impression they did not click at all or that something crashed (luckily multiple clicks on the Language icon does not appear to bork anything). Would it be possible to modify the mouse cursor to show the spinning wait icon?

[tomeu]

Replying to garycmartin:

Testing Joyride 2631 on XO-1, this click take 6 or more seconds to have any visible effect! The user is given the impression they did not click at all or that something crashed (luckily multiple clicks on the Language icon does not appear to bork anything). Would it be possible to modify the mouse cursor to show the spinning wait icon?

Opened #245 about that. Moving this one to 0.86.

[erikos]

This is not a blocker, and the proper fix would be invasive, so I move to 0.88

[sayamindu]

The only way to fix this seems to ship a pre-built list of translations, and look that up while building the list. Does that seem acceptable ?

[walter]

We should settle on a solution to this (and also consider  http://wiki.sugarlabs.org/go/Features/Feature_intro_language_keyboard_options as well)

[Rohit U]

Is speed still an issue? Should I try implementing an async method?

[sascha_silbe]

Choosing language and time zone is a distro level issue. Sugar currently does it itself (sometimes), but that brings in a whole lot of trouble. See  a recent mail about problems with the time zone code. #1492 and #1672 are blockers bugs for the keyboard layout support that are still unsolved. At least one distro has reported issues with Sugar settings (~/.i18n) vs. locale chosen via the display manager.

The way forward is to move this out of Sugar as much as possible.
On systems using a display manager with login prompt, that's a good place to put it (and should be the default). For systems that boot straight into Sugar, we'll need to retain an in-Sugar way of changing things, but it should offload as much as possible to other code. We should take a look at how Gnome handles this. There's a chance they already solved this issue and we can build on their code.

[sascha_silbe]

Replying to sascha_silbe:

[...] #1492 and #1672 are blockers bugs for the keyboard layout support that are still unsolved.

Sorry, that should have read #1942.