Closed Bug 992153 (turkishQ-keyboard) Opened 11 years ago Closed 7 years ago

Set Turkish-Q as the default layout for Turkish

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

x86_64
Windows 8.1
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: selim, Unassigned, NeedInfo)

References

Details

(Keywords: regression, Whiteboard: [POVB])

Gaia has two keyboard layouts for Turkish: Turkish-Q and Turkish-F. Turkish-F was added as an alternative (bug 868417), and Turkish-Q should have been kept as default. However, F seems to be the default layout in current master. We need to set the default keyboard layout to Turkish-Q as for the Turkish locale.
Hi Selim Thanks for noting this. Ni David to see what happened here
Flags: needinfo?(dflanagan)
Keywords: regression
I don't know what is going on here. There have been big changes in the way the keyboard app is configured since I last looked at this. The language to layout mappings seem to be in build/config/keyboard-layouts.json, and tr-Q is listed before tr-F, but maybe that is not enough to make it the default. Rudy: can you help with this?
Flags: needinfo?(dflanagan) → needinfo?(rlu)
David, thanks for the ni. -- Selim, Could you please elaborate what do you mean by "default" layout here? As David pointed, the mapping is in "build/config/keyboard-layouts.json" and it seems ok to specify both tr-Q and tr-F as default layouts for Turkish language. By 'default' if you mean the order the keyboard layouts when you switch between them, then I guess this could be affected by the order in this line, https://github.com/mozilla-b2g/gaia/blob/d04280124a50efa3f80b3252a33d042ecac0d624/Makefile#L394
Flags: needinfo?(rlu) → needinfo?(selim)
Sure. What I mean by "default" is that once Firefox OS is set up in Turkish, Turkish-F is the layout you see unless you manually change it. If that's supposed to be an "order" issue, that's fine. We just need to make tr-Q first in order. :)
Flags: needinfo?(selim)
May I know if the build is built by yourself or where do you get your build? We have to know what "GAIA_KEYBOARD_LAYOUTS" variable is when building Gaia to make sure the root cause of this issue, https://github.com/mozilla-b2g/gaia/blob/d04280124a50efa3f80b3252a33d042ecac0d624/Makefile#L394 Thanks.
Flags: needinfo?(selim)
I haven't built it myself. I have a Geeksphone Keon getting updates from the master channel. Its current build ID seems to be 20140512024602, if that's what you need.
Flags: needinfo?(selim)
BTW, as of the order, it should be the same as what you see in Settings app > keyboards > Selected keyboards > Add more keyboards >
I'm not sure what you mean by that, Rudy. Do you mean we can't change that order?
Flags: needinfo?(rlu)
So far we don't have the UX design to change that order after the phone is shipped. That order is decided at build time, as comment 3 described. Thanks.
Flags: needinfo?(rlu)
That's understandable but I'm thinking about future releases/phones. Can we fix it? If not, then I suggest removing Turkish-F completely. It would affect user experience badly if we keep pushing it as the first (default) keyboard layout.
Flags: needinfo?(rlu)
We could get this fixed during build time, which per your comments is controlled by Geeksphone. Please help post this issue to Geeksphone's contact window if you can. Thank you.
Flags: needinfo?(rlu) → needinfo?(gp)
Whiteboard: [POVB]
Alias: turkishQ-keyboard
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.