On Jun 12, 2004, at 4:14 PM, Behnam wrote:
I had discussion with an Apple developer on this subject. She insisted that this is the way Unicode wants the mirroring characters to behave and that Apple has no intention to change its implementation of them.There has been a misunderstanding in your conversation and in a sense both of you are right. As I develop this topic further you'll better understand it. I hope she would read my posts (if she has any influence on Apple) so that something would get fixed on Apple's side as well.
On the other hand, what she needs to realize (along with most of the other developers) is: Unicode does not have to dictate the user interface of text input and editing. The user interface of text editing can be vastly improved if we properly design a GUI-optimized model to hide the true underlying Unicode bidi semantics in favor of easier and more user friendly semantics while maintaining 100% Unicode compatibility.
On the other hand, I suspect you have font related issues. read below...
This whole thing means that on Mac platform we will see the wrong parenthesis on Persian web-pages forever!Part of the issue you are experiencing could be related to fonts. Persian/Arabic Apple fonts need a suitable character property table to identify mirrored glyphs and behave correctly. Please compare the behavior of Geeza Pro standard system font with the fonts you are using. If they are different it is becuase of the missing or improperly formed 'prop' table in the font. (http://developer.apple.com/fonts/TTRefMan/RM06/Chap6prop.html) If this is the case let me know to see how I can help fix them.
I guess that along the effort in finding a proper solution for handling of mirroring characters, there has to be an effort to remove this useless mirroring effect in Unicode altogether.Don't even think about that. In the text stream level using logical opening and closing parenthesis instead of visual left and right parenthesis is actually very helpful in keeping the logical text processing model simple and elegant. Also, too many things already depend on it. We need to address this issue in text input/editing services of the operating system without touching Unicode. As I mentioned Unicode is not at fault here. The current assumption that the Unicode model necessarily applies to the user interface is the problem.
- Hooman Mehr
_______________________________________________ PersianComputing mailing list [EMAIL PROTECTED] http://lists.sharif.edu/mailman/listinfo/persiancomputing
