> Unfortunately this kind of misinforming is quite popular in weblogs, > where people only care about being visible to more people.
I confess that I'm one of those who use this technique on their web sites. I don't believe it's correct, and I don't think of it even as a semi-elegant solution. It's a solution which just works on the largest number of platforms. By inspecting the web server logs, I notice that still an average of 30-40 percent of the visitors are using Win9x. Hopefully one can start dropping support for Win9x users as their number is constantly decreasing, but right now if I choose the standards compliant route of using FARSI YEH everywhere, those Win9x-ers will not be able to browse my sites. I have a high respect and tendency to the standards. I'm mostly a C++ programmer, and I'm one of those "preachers" of the C++ Standard. However, today's C++ compilers are still not fully compliant to the C++ Standard, so whenever someone asks me for advice on how to accomplish a certain task on a non-conformant compiler, I show them the non-standards way, and also mention the standards way, so that they know what the *right* way is, and also what the way to do their job right now is. I see little difference in the web standards land as well. Of course this 'solution' (if it can be called so) poses other problems, such as the inability of correctly indexing of such words with both forms of YEH by search engine spiders such as Google's, which must be addressed separately. Also, if you choose to use the FARSI YEH form everywhere, then again such problems will occur (such as a Win9x-er can neither correctly see your pages nor fine them in Google; if they query for a word containing YEH.) > They even go on and use HTML entities (like ٚ) instead of UTF-8, > just because if the user's browser is set to something other than auto > and UTF-8, the page is still rendered correctly... This one is silly, and I don't see how this can solve any problem. The browsers are required to be able to correctly resolve such numerical entities only if the page's encoding is already UTF-8, and if it is so, why not use UTF-8 encoded characters in the first place? Also, some agents have difficulties interpreting such numerical forms. Furthermore, maintaining them is impossible (not hard), and even they can't be treated as text by most software packages (for example, they can't be searched for by many programs.) And the last, but not least, for a regular Persian document, they're likely to increase the document size by more than two times. They have their own usage, of course, but I don't see any sense in using them instead of UTF-8 characters for regular web pages. ------------- Ehsan Akhgari Farda Technology (http://www.farda-tech.com/) List Owner: [EMAIL PROTECTED] [ Email: [EMAIL PROTECTED] ] [ WWW: http://www.beginthread.com/Ehsan ] _______________________________________________ PersianComputing mailing list [EMAIL PROTECTED] http://lists.sharif.edu/mailman/listinfo/persiancomputing
