amosogra / hackerskeyboard

Automatically exported from code.google.com/p/hackerskeyboard
0 stars 0 forks source link

bulgarian input method is the same as the english one #76

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. enable bulgarian input method
2. try to write some text in bulgarian

What is the expected output? What do you see instead?
The expected output should be something written in cyrillic but instead it is 
latin.

What version of the product are you using? On what operating system?
v1.20 on android honeycomb (motorola xoom)

When you are in bulgarian input method,the keyboard on the screen looks like 
the english one.This is not a problem but the characters are also written in 
latin,so no text in bulgatian can be added.

Original issue reported on code.google.com by inspell...@gmail.com on 23 Sep 2011 at 9:03

GoogleCodeExporter commented 9 years ago
By default, the keyboard shows languages in the "Input language selection" 
dialog that don't have customized key maps, so you'll only get some translated 
menu items but not a different layout. Please look for the "4-row, 5-row, 
dictionary available" line shown below the languages that do have custom 
layouts.

I have received a contributed layout definition for Bulgarian, and am working 
on integrating this for the next release.

Original comment by Klaus.We...@gmail.com on 26 Sep 2011 at 9:00

GoogleCodeExporter commented 9 years ago
I've merged the Bulgarian layout contributed by Lyubomir Filipov.

Try v1.23rc2 (or later) from 
http://code.google.com/p/hackerskeyboard/downloads/list, and please let me know 
if that works for you.

Original comment by Klaus.We...@gmail.com on 26 Sep 2011 at 10:15

GoogleCodeExporter commented 9 years ago
v1023rc3 works perfectly. Thank you!

Original comment by inspell...@gmail.com on 27 Sep 2011 at 6:19

GoogleCodeExporter commented 9 years ago
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.)

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:33

GoogleCodeExporter commented 9 years ago
Bulk update - changing "Fixed" to "Verified" for old bugs.

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:34