In a message dated 2/22/2003 12:57:40 PM Pacific Standard Time, [EMAIL PROTECTED] writes:

As far as I know there are no text based browsers which support _javascript_ at
the moment.


Does those text browser support UTF-8, Greek and Hebrew?


Some people use a text mode browser through text terminal connection (in
universities etc.) Some people don't even have a choice.


Again, Does those text browser support UTF-8, Greek and Hebrew?


Some people like to switch _javascript_ off because of security and popup
windows.

Probably all needed UI stuff can be made with just normal html without
_javascript_.


As I said before, this is a feature, compatability trade off game. You can always use html 3.2 to implement the UI and what will you got is good compatability and less feature.

And there are WIN-WIN solution out there. We can make more than one implementation of the UI by using different selector in the GET URL to select. There are no need to be - a "you win I loss " or "I win you loss" situration. However, of course, support multiple version of browser is always a challenge. Not sure how to support Hebrew display for those text base browser. 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.

Reply via email to