>Does those text browser support UTF-8, Greek and Hebrew?
lynx supports UTF-8 just fine. Greek / Hebrew would depend on whether the
user has fonts and other things set up correctly for it.
Most users don't care about that though. 90% of users will just want
English. Probably 98% just need a Latin-* charset.
:( :( :( very very very western kind of thinking. Don't know how you come out that number. (90% and 98%). English user is less than 30% of the total Internet users these days. And Latin * charset users is < 70% of the Internet users these days. Does Bible said "God so loved the World" or does the Bible said "God so loved the western world". :{
>Does those text browser build in Bi-Di ordering? Can they display
>Biblical Greek and Biblical Hebrew? Does php support Bi-Di ordering on the
>server side so you can convert the Hebrew from Logical order to Visual order
>on the php before send to those text browser?
>
>Netscape start to have Hebrew support since Nsetcape 6.2 althought we still
>have some selection bug there.
>If we are going to display OT Hebrew, it better to assume the brower could
>support Logical order Hebrew. It is not fun to add Bi-Di ordering code to the
>server side.
Just assuming browers support BiDi reordering is a bad idea. To do a
proper implementation, we would need to survey those browers and OSes that
can handle logical vs. visual ordering and serve up the appropriate one.
I would be surprised if IE on Win9x did reordering automatically (since
the rest of that OS doesn't).
I think that depend on which version of IE is running on it. Since my team implement the Bi-di support in Mozilla, I think I can figure it out early next week.
Doing the actual visual reordering on the
server side is trivial since Sword has a filter (basically just a wrapper
for an ICU call) to do this (and implementing it actually was kind of
fun :).
Not fun if you have no idea does the client support it or not
