On Sat, 2004-06-19 at 18:41, Hooman Mehr wrote: > [...] The best solution in my opinion is to provide exact format strings (as > arrays of Unicode characters with specific placeholders for date > elements). This will avoid any possible ambiguity in the specification.
That will be specified in a coming appendix, which will have the locale data for ICU and GNU C library. Anyway, the situation is worse than what you may guess. The Unicode Consortium has changed the bidirectional category of a few characters, including Slash, in Unicode 4.0.1. For Slash and its brethren, it's not just Neutral or things like that. We are having stuff like European Terminators and Common Separators in the Unicode Bidi algorithm. > I sincerely hope that you won't tell me that you expect the users to > type 1383 then / then 1 then / then 12 to enter a date in short format, > because it would be unnatural and none obvious (although currently it > may be the only way to get a correct result with the available software > applications). I'm not implying anything about users here. We are specifying how the final text should be displayed. We have not specified how to encode it (of course that doesn't mean one is allowed to encode it however he likes). If we do that, we may not remain conforming to Unicode if Unicode changes yet another bidirectional category in a later version. > As I have seen, you have defended going back to using the correct yeh > and correcting the faulty software/fonts, so I hope you choose the > right thing to do this time as well. I always do the right thing, don't I? ;-) > Alright I know, you may say: It is impossible any other way! What is > the solution? I say: the answer is too technical to be included in the locale specification. There will be different answers for different situations, in different contexts, or in different Unicode versions. BTW, Behdad is attending the Unicode Consortium's Technical Committee meeting right now, and later the ISO JTC1/SC2 ones. I'm sure the UTC meeting (which will be the first with a FarsiWeb member present) will have good news for us (which may include more changes and clarifications to the Bidirectional algorithm). roozbeh _______________________________________________ PersianComputing mailing list [EMAIL PROTECTED] http://lists.sharif.edu/mailman/listinfo/persiancomputing
