Dear Chris,
Thanks for your response, so what you are suggesting is that the Unicode does not change but only the display glyph should change right.
Currently, the implementation I am following is that once the user types in a particular key say: 0x0622 , I look for the joining type of the character and then on the basis of the joining type of the character and its neighbors I look up the Display form of the current character in Presentation form B and then I ask my Display Module to display the glyph matching to this Presentation form (Unicode).
If I donˇ¦t use the Unicode values of Arabic presentation form B then how will my display know which particular glyph to display? using the Unicode values of presentation form B makes this easier but then the original Unicode changes.
I am sorry but I am a bit confused with what to display and what Unicode to store, your comments would be really help full.
Thanks & Regards,
Nitin
From: "Chris Jacobs" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>, "Nitin Kapoor" <[EMAIL PROTECTED]> Subject: Re: Arabic Implementation Date: Wed, 18 Aug 2004 04:44:09 +0200
----- Original Message ----- From: "Nitin Kapoor" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, August 18, 2004 3:38 AM Subject: Arabic Implementation
> Hello Friends,
>
> I am implementing ARABIC in one of our embedded projects .I have read the
> Unicode standard well and would like to ask a question about joining types.
>
> After a character changes the display form into one mentioned in Arabic
> Presentation Form B does it still belong to a joining type.
>
> For example: Lets say Unicode Character : 0x0622 which is a right joining
> type , when this changes the display form into ISOLATED FORM its Unicode
> becomes : 0xfe81.
NO. When 0x0622 changes its display form into ISOLATED FORM because of context it still stays 0x0622.
Only the glyph changes, not the underlying char.
> So does 0xfe81 also belong to Right Joining type?
If it is really a 0xfe81 char, encoded as such, then no.
> I am asking this question
> because according to Derived Joining Type .txt provided by UNICODE, it
> doesnˇ¦t have any category for characters once they change their display
> form.
>
> I personally feel that a particular character belonging to a particular
> joining type will have all its different display forms also belonging to the
> particular joining type .
Which is indeed what happpens if you avoid using the presentation form code points, as you should.
> Please advice me if I am on the right track.
>
> Thanks
>
> Nitin
>
> _________________________________________________________________
> Apply to 50,000 jobs now. http://go.msnserver.com/IN/46921.asp Post your CV
> on naukri.com today.
>
>
>
_________________________________________________________________
Apply to 50,000 jobs now. http://go.msnserver.com/IN/46921.asp Post your CV on naukri.com today.