Selecting Hebrew keyboard shows English layout
Brought to you by:
starssoft
Menu
▾
▴
2 Attachments
#122 Selecting Hebrew keyboard shows English layout
Verified
nobody
None
Medium
Defect
2013-01-22
2011-12-07
Anonymous
No
Originally created by: Klaus.We...@gmail.com
Originally owned by: Klaus.We...@gmail.com
(As reported via email)
What steps will reproduce the problem?
1. Activate Hebrew in "Input Language Selection" settings menu
2. Slide space bar to activate the layout
What is the expected output? What do you see instead?
The keyboard shows that Hebrew is selected according to the text displayed on the space bar, but the layout remains English.
Activating other keyboards (Greek, French, Arabic) and switching to them works as expected, just Hebrew remains unselectable.
System locale was set to English.
System: Samsung Galaxy S2
Version: 1.27.1145 4d199a6937e9 2011-11-06
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
I've been unable to reproduce this so far and am not sure what's going on here. I'll look into preparing a debug version of the keyboard that provides more detail about what it's doing.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
A question for anyone affected by this bug - in the "input languages" menu, does it show the "5-row, 4-row", and/or "Dictionary available" message in the list entry for the "Hebrew" checkbox? And do you have the Hebrew dictionary installed?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: yis...@yishay.net
Hello
I have the same problem on same device.
On my HTC HERO and DELL STREAK the Hebrew selection works fine.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Mofet...@gmail.com
Hello,
Just switched from MIUI where the keyboard worked perfectly, to a custom Samsung rom and now I am affected by this issue as well.
To answer your question, it doesn't show the "5-row, 4-row", and/or "Dictionary available" even though I have the dictionary installed.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
I haven't made progress yet on reproducing it, I'm suspecting that it's a ROM specific issue which causes problems when trying to change the locale and loading the locale-specific data. Apparently this is only happening on Samsung devices?
Anyway, I'm making progress towards the new and completely rewritten language selection logic and hopefully this won't be an issue anymore once that's complete since it will no longer depend on locale-specific locale loading.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: yis...@yishay.net
Hello
The problem still occurs.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
See my previous update, since I can't reproduce the issue it's unfortunately difficult for me to do something about it. As far as I can tell my code is trying to do the right thing, but the Samsung OS is refusing to load the requested layout resources. When I get a chance to work on the new mode system, I'm hoping that this will take care of it.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
Issue 139 has been merged into this issue.
Related
Tickets:
#139View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
Has anyone encountered this problem on a device other than a Samsung Galaxy S2 specifically? If yes, please let me know, but current evidence seems to confirm this is most likely an OS bug in that device.
See also: http://stackoverflow.com/questions/8699650/android-emulator-displays-hebrew-resources-correctly-but-device-doesnt
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: noambeh...@gmail.com
Hi,
I checked this issue in several devices - HTC, Galaxy S1, S2. All the devices that have root access can see Hebrew fonts, and all the "pure" devices without a changed ROM can't see Hebrew. Another concern on the same hand is that on all root devices I couldn't see my Ads, and on non-root devices, I saw the Ads
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: noambeh...@gmail.com
Any updates with this bug?
If there's a workaround that can be used it would be great.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
I've added a very crude hack in version 1.28rc21, can you try that (or later) from http://code.google.com/p/hackerskeyboard/downloads/list and let me know if that changes things?
If my theory is right, this should enable the 4-row Hebrew keyboard since that will now load a (mostly) self-contained uniquely named XML resource from res/xml/ instead of trying to load the locale-specific alternate from res/xml-iw/ which apparently wasn't working.
It probably won't fix the 5-row layout since that depends on loading string resources from res/values-iw/ in a way that would be much harder to work around. As I said previously I'm planning to rewrite keyboard handling to no longer require the localized resources, but that's a complex change that will have to wait until after I get the current version stabilized and released on the Market, it's already delayed a lot more than anticipated.
For details, see [r919281f5e8d1].
Status: Started
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: noambeh...@gmail.com
Klaus,
Can you explain a bit how can I check your fix? I am supposed to install that APK in my device?
If so, how will that help my users see Hebrew in my app without this APK?
I thought that the fix is some workaround I can write in my App itself.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
Noam, the current status is that I have a hypothesis about why the Samsung S2 isn't handling Hebrew resources correctly, and I'm unable to test it myself since I don't own that device. I added an experimental workaround to the application which should help confirm or deny if the hypothesis is correct. If you or someone else can try that APK and it turns out to behave in the expected way, this would mean that the workaround is effective and could potentially be adapted for other applications in a similar way.
If you do want to help test, please install the APK and follow the onscreen instructions to activate it as an input method, activate "Hebrew" in the "Input languages" selection menu, and swipe the space bar horizontally to select that language. Then try typing in portrait and landscape mode and let me know if you see English or Hebrew letters on the keys.
Unfortunately, if it turns out that I'm right, the workaround would be difficult to do in general and may require a radical restructuring of the application, and possibly interfering with portability to other devices. It would be far better if Samsung would fix their OS instead of expecting application authors to individually add difficult workarounds to their code.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: noambeh...@gmail.com
Hi,
I want to make sure we understand eachother:
1. The problem is not with the keyboard. I have an Hebrew keyboard. I just don't see the resources written in res/values-iw/. Why is this related to the keyboard?
2. As I wrote above, it happens in all devices which are not rooted - Samsung S1, S2 and also HTCs (!). In order to repro this just grab a device which is NOT rooted, make yourself an application with Hebrew strings under res/values-iw/, change device's language to Hebrew and run the app. You'll see the default English strings. Then grab a device which IS rooted, and install the same App - now you WILL see the Hebrew resources.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Nad....@gmail.com
Hello.
Tried both rc21 and rc22 - latest.
Hebrew doesn't shows up.
How can I provide more debugging info?
Samsung galaxy S
Not rooted. Stock firmware updated.
V. 2.3.3
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
Nad.Oby, this is interesting. Just to confirm, you've activated Hebrew in input languages, and selected the 4-row layout mode? The current partial workaround doesn't help for 5-row mode which handles resources differently. It should show "Hebrew" (or "עברית") on the space bar to indicate that it attempted to switch.
If you've done all these steps and it's still showing an English layout, it appears that my hypothesis is wrong and something else is going on. For example, this could happen if requesting locale "iw" and then retrieving the 2-letter language code from it returned something different from "iw".
If you can confirm the steps, I can make a test version with a different workaround to try.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
I've added a different workaround in 1.28rc23 available from http://code.google.com/p/hackerskeyboard/downloads/list, can you try that? If the new hypothesis is right, this should hopefully fix both the 4-row and 5-row layouts.
See [rd329930b2e54] for details.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Nad....@gmail.com
Last revision works fine.
Both 4 and 5 rows layouts show all 3 languages I use fine.
Not found regressions.
Thanks.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Nad....@gmail.com
Also took a look at [rd329930b2e54]
It's a hack, hope you'll understand the root cause .
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
Glad to hear it, thanks for testing.
The new workaround simply makes a duplicate copy of the res/*-iw/ resources under res/*-he/, and I've removed the earlier special case in the code.
See my post at http://stackoverflow.com/a/8716894/405214 for more detail. It appears that the OS of the Samsung Galaxy S2 handles the Hebrew locale and resources differently than other Android devices. Android uses language code "iw" for Hebrew or legacy compatibility, while Samsung apparently changed it to use language code "he", which is arguably correct as per ISO 639-1 but incompatible. See Android issue
http://code.google.com/p/android/issues/detail?id=3639 for more background information.
The effect is that the resources in res/*-iw/aren't being loaded on the affected Samsung devices, and the workaround is to add a duplicate copy in res/*-he/.
Status: FixInTest
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
[Bulk bug update] The new Market release 1.29 includes the changes from the v1.28 prerelease series, and these "FixInTest" issues should now be fixed. If not, please reopen the bug with additional information. If the original bug covered multiple separate issues that aren't all addressed, please open new bug(s) for the leftover ones.
Status: Fixed
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
Bulk update - changing "Fixed" to "Verified" for old bugs.
(Background: I'm changing the "Fixed" status to be considered open, the next steps in the lifecycle will be the closed states "FixInTest" and "Verified". This lets me mark issues as "Fixed" in commit messages without hiding them from the issue tracker.)
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
Bulk update - changing "Fixed" to "Verified" for old bugs.
Status: Verified