Open GoogleCodeExporter opened 9 years ago
Original comment by menn...@gmail.com
on 28 Jun 2009 at 8:45
Has it been fixed? Please! Bulgarian user here who can help out if needed.
Original comment by rayner...@gmail.com
on 6 Oct 2009 at 2:48
It has not been fixed yet.
You are more than welcome to look at the code, and try to figure out the
problem :)
Original comment by menn...@gmail.com
on 6 Oct 2009 at 3:15
I can take a look at this, but first, @atg2dg and @raynerape you need to
describe the
problem better.
Do you actually mean that shift modifier pressed should show lower case letters
instead of capitals?
Original comment by henrik...@gmail.com
on 21 Dec 2009 at 12:14
Aah i think i found it, capital ь show ѝ isntead of Ъ
Can you confirm this, and i will updated the keyboard.
Original comment by henrik...@gmail.com
on 21 Dec 2009 at 1:15
I understood that there isn't a capital ѝ letter, only lowercase - at least,
usage-wise.
Again, as I recall, it was requested that the keyboard will not output capital
ѝ.
But I think you found a different bug. Where is it?
Original comment by menn...@gmail.com
on 21 Dec 2009 at 1:20
What i found was that on first key on second row key 'ь' show captial 'ѝ' but
when i
check keyboardlayout of bds
(http://commons.wikimedia.org/wiki/File:Keyboard_Layout_Bulgarian_BDS.png)
there is
no 'ѝ' at all in the layout, and 'ь' (0x44c) has a capital 'Ь' (0x42c)
Original comment by henrik...@gmail.com
on 21 Dec 2009 at 1:37
Hi capital 'ь' as well as capital 'ѝ' is not used anywhere (on regular
keyboards
there is no way to write capital 'ѝ' too). That's why the lowercase letters are
positioned on the same key (and that is the way they are positioned on a regular
keyboard too).
On AnySoftKeyboard the problem is display only - when shift or caps lock is
enabled
the keyboard outputs lower case "ѝ"(which is correct) but on the keyboard
itself it
is displayed as upper case - which is misleading because it outputs lower case.
Original comment by atg...@gmail.com
on 21 Dec 2009 at 1:38
Aah ok, ill fix that..
Original comment by henrik...@gmail.com
on 21 Dec 2009 at 1:40
So, the problem is display related?
You want that a lowercase ѝ will be shown whether shift is pressed or not?
Original comment by menn...@gmail.com
on 21 Dec 2009 at 1:42
@mennyed, the code for the small key is right, so it might be modified to
uppercase
byt the shift key press automatically
Original comment by henrik...@gmail.com
on 21 Dec 2009 at 1:46
Here is the layout used by the operating systems. On it there is a separate key
for
lower and upper case 'ь' (actually this key is some phantom :) because i don't
have
it on the physical device) but since the devices are with limited width and
upper
case 'ь' is not used (and as i mentioned there is no physical key on most
keyboards)
i just used the combined key.
"So, the problem is display related?
You want that a lowercase ѝ will be shown whether shift is pressed or not?"
Ammm mostly when shift/caps is on it should display lower case 'ѝ' otherwise
lowercase 'ь'. But yes the problem is display only - the output is ok
Original comment by atg...@gmail.com
on 21 Dec 2009 at 1:51
Attachments:
Original comment by menn...@gmail.com
on 21 Dec 2009 at 1:56
@atg2dg, the new description OK?
"Bulgarian BDS 'ѝ' problem - display related: lowercase ь key should become
ѝ when
shift is pressed"
Original comment by menn...@gmail.com
on 21 Dec 2009 at 1:56
yes
Original comment by atg...@gmail.com
on 21 Dec 2009 at 1:59
Now everything is clear.. :)
Thanks.
@henrik.4E, so, it is what you said, right? You want to handle this?
Original comment by menn...@gmail.com
on 21 Dec 2009 at 2:00
somewhat :), anyway i can look into this and updates my progress here..
Original comment by henrik...@gmail.com
on 21 Dec 2009 at 2:10
Go for it.
Original comment by menn...@gmail.com
on 21 Dec 2009 at 2:13
@mennyed, am i right when i say that we might override onDraw() for each key ?
As it seems to that the keyboardview does render keys uppercase when shift is
pressed...
Original comment by henrik...@gmail.com
on 21 Dec 2009 at 2:46
WOW.
Sounds like a pain..... I would look for a different solution.
Why does the keyboardview change it to uppercase?
Maybe a workaround at its level (without overriding onDraw) can be done? Just
for
those letters.
Original comment by menn...@gmail.com
on 21 Dec 2009 at 3:48
I made a test adding 113 = 'q' as both primary code and shift code as "113,113"
and
removed keyLabel...
The button is drawn with both a lower q and a upper Q, i disabled setShifted()
code
to KeyboardView, which made all keys lower always.. so it's internally handled
in the
keyboard view...
Dont seems to that the api allows us to override for handling this ourself due
to
each key does not have an onDraw neither setShifted()....
I'm clueless... :)
Original comment by henrik...@gmail.com
on 21 Dec 2009 at 6:00
Except, if its timed to implement a own KeyboardView that we handle all renders
of
buttons etc. this seems too must be done if there shuold be support for
theaming..
Maybe it's time for diving into a keyboardrender class..
Original comment by henrik...@gmail.com
on 21 Dec 2009 at 6:06
I believe you are correct.
We will wait with this request for the next release, I don't want to add too
many
things in one build.
OK?
Original comment by menn...@gmail.com
on 21 Dec 2009 at 8:48
Yea i agree, the nature of this issue isn't major...
Original comment by henrik...@gmail.com
on 22 Dec 2009 at 4:51
@mennyed
Anyhow, if you want i could dig into the theming issue, but i think i need a
branch
then.. and some discussion around how it to iron out what it should be capable
to or
not..
Original comment by henrik...@gmail.com
on 22 Dec 2009 at 5:34
Lets continue the talk about themes at:
http://code.google.com/p/softkeyboard/issues/detail?id=83
Original comment by menn...@gmail.com
on 22 Dec 2009 at 7:17
Bug in latest version.....QWERTY. world but not the other keyboard
...plaza fix
Original comment by arsalan...@gmail.com
on 16 May 2011 at 12:47
Bug in latest version.....QWERTY. world but not the other keyboard
...plaza fixing
Original comment by arsalan...@gmail.com
on 16 May 2011 at 12:47
What is the bug?
Original comment by menn...@gmail.com
on 16 May 2011 at 11:25
Original issue reported on code.google.com by
atg...@gmail.com
on 28 Jun 2009 at 8:17