Sadly i noticed that you have to write the characters in the exact same order as it was written, this poses a problem for example שַׂ != שַׂ and well thats just odd for a user since they look exactly the same.
my guess is that the writing of a character in Hebrew involves a combination of keystrokes.
So, the keystrokes k1+k2 and k2+k1 both produce an equivalent letter of the alphabet.
Is that right?
If so, it is strange because internally, the strings are stored in UTF-8 format and their comparison should take into account this.
I will double check. Can you send me an example - a deck of two or three cards that illustrate the problem.
You can attach your deck to this ticket.
Meanwhile, if the scope of the problem is not too big, you can always provide all typical combinations
each on a separate line of the 'Back' field in CardView/Edit Dialog, and when testing yourself, set the match line number to '0' from default '1' in the lower control bar of the Deck Player (the third entry from the left after speaker and 'F' icons).
hope this helps,
--Vlad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-01-13
Ah sorry that I forgot too mention that, but yes you combine keys and that it was tested under GNU/Linux.
I wrote a little test deck that seems to have just that problem.
Sadly writing any alternatives might be really hard since there will just be to many mutations on some words.
A example a word with two ש based letters with a vocal under each, will have 4 diffrent mutations. :/
File Added: error.dkf
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Blambi,
my guess is that the writing of a character in Hebrew involves a combination of keystrokes.
So, the keystrokes k1+k2 and k2+k1 both produce an equivalent letter of the alphabet.
Is that right?
If so, it is strange because internally, the strings are stored in UTF-8 format and their comparison should take into account this.
I will double check. Can you send me an example - a deck of two or three cards that illustrate the problem.
You can attach your deck to this ticket.
Meanwhile, if the scope of the problem is not too big, you can always provide all typical combinations
each on a separate line of the 'Back' field in CardView/Edit Dialog, and when testing yourself, set the match line number to '0' from default '1' in the lower control bar of the Deck Player (the third entry from the left after speaker and 'F' icons).
hope this helps,
--Vlad
Ah sorry that I forgot too mention that, but yes you combine keys and that it was tested under GNU/Linux.
I wrote a little test deck that seems to have just that problem.
Sadly writing any alternatives might be really hard since there will just be to many mutations on some words.
A example a word with two ש based letters with a vocal under each, will have 4 diffrent mutations. :/
File Added: error.dkf
shalom isn't equal to shalom
Blambi,
that was what I suspected. I will take a look over the weekend and try to fix it (along with other stuff).