I don't know about Cliff, but people in Israel send me email and Word docs in Hebrew because Hebrew is their preferred language, not mine.
Most of the sites I visit are in English, too. But once in a while I need to find something at an Israeli site that doesn't have everything translated into English.
I am even involved in this. I am helping an org I belong to put content on its site, and sometimes this content arrives in Hebrew. In Word, of course. At least I translate it into pages that both Netscape and IE can read.
What that's about is that there are two ways to put Hebrew on the web. Visual Hebrew requires that text be broken up into lines, and displays them exactly as they are in the HTML. Simple, easy on the browser, supported on Netscape, but if the lines are too wide or narrow for your window, too bad. Then there's logical Hebrew. When you type Hebrew the cursor moves R2L, but if you type a number, or latin chars, the cursor moves L2R. Logical Hebrew has the chars in the order you type them. The plus is that paragraphs can be line-broken depending on the width of the window, the minus is that BiDi support in Netscape/Mozilla isn't done yet.
I already use IE for most of my browsing (because Netscape 4 loses bookmarks made during the current session if it crashes, IE doesn't). Until Mozilla BiDi works, I won't be able to use it. Why don't I contribute? I worked on BiDi code in a Hebrew word processor (Dagesh, sadly, M$ Word whomped it), and rather than learning something useful that I could contribute to Mozilla, I came away realizing that I don't understand logical order, in fact one of the things I liked about Dagesh was that sometimes it's hard to type just what you want in logical Hebrew, when that happened, I could get it to use visual.
Slashdot Mirror
I don't know about Cliff, but people in Israel send me email and Word docs in Hebrew because Hebrew is their preferred language, not mine. Most of the sites I visit are in English, too. But once in a while I need to find something at an Israeli site that doesn't have everything translated into English. I am even involved in this. I am helping an org I belong to put content on its site, and sometimes this content arrives in Hebrew. In Word, of course. At least I translate it into pages that both Netscape and IE can read. What that's about is that there are two ways to put Hebrew on the web. Visual Hebrew requires that text be broken up into lines, and displays them exactly as they are in the HTML. Simple, easy on the browser, supported on Netscape, but if the lines are too wide or narrow for your window, too bad. Then there's logical Hebrew. When you type Hebrew the cursor moves R2L, but if you type a number, or latin chars, the cursor moves L2R. Logical Hebrew has the chars in the order you type them. The plus is that paragraphs can be line-broken depending on the width of the window, the minus is that BiDi support in Netscape/Mozilla isn't done yet. I already use IE for most of my browsing (because Netscape 4 loses bookmarks made during the current session if it crashes, IE doesn't). Until Mozilla BiDi works, I won't be able to use it. Why don't I contribute? I worked on BiDi code in a Hebrew word processor (Dagesh, sadly, M$ Word whomped it), and rather than learning something useful that I could contribute to Mozilla, I came away realizing that I don't understand logical order, in fact one of the things I liked about Dagesh was that sometimes it's hard to type just what you want in logical Hebrew, when that happened, I could get it to use visual.