Hunting For The "Lam-Alef"!

Body

So, Alaa was always complaining that katoob can't convert UTF-8 text to cp1256, And iconv outputs: "Invalid byte sequence in conversion input", Trying to know what's happening, We noticed that this is happening with the hindi digits, The unicode control characters and the lam-alef letter. Great! I do strip the unicode characters.
Now, I have to convert Hindi digits to Arabic digits, And also to convert the lam-alef character into lam+alef. Easy!
The 1st one was done with no problem, However I tried to find the unicode value for the "lam-alef" character with no success, I spent 4 days googling but no way! I tried whatever i can but i didn't come to anything. Capturing the gtk keypress events, looking at the gdkkeysyms.h file, the Xfree equivalent one, looking at the UnicodeData.txt file, looking at the unicode charts, I found the lam-alef presentation forms, And they were what i obtained from the gtk keyvalues, But I didn't find the character itself.
Panic ? smash the wall ? destroy your keyboard ? Cut your head and die happily ? Nothing. No way. Guys DAMN! How come this shit is not there!
Until Isam Bayazidi came to the rescue. Now I know where the problem is.
There is no such character, The unicode standard defines only presentation forms, And since there is no way to map 2 characters to a key in Xfree86, He had to map the keys to the isolated presentation forms, holyshit! Thanks Isam, You rescued me, You did well, But it's time to fix this thing in Xfree86/X.org.

Add new comment

The content of this field is kept private and will not be shown publicly.