It works on Firebird in Win 2000… but given that, I still wouldn’t just post this kind of thing in your posts without explaining what it was in words. It’s just not going to work for someone, and they’re going to ask about it, and it’ll hijack your thread.
(copied and pasted in BBEdit, then copied and pasted back here).
In case that itself looks different to you than it does to me, it’s a double-cross sign (such as used in text after you’ve used up * and †), a period-like dot floating along at mid-height, and a comma.
Yes, evidently (as can be seen since it didn’t work for some people… I guess it’s people who have “auto-detect encoding” disabled.
So - I guess Unicode still can’t really be used universally yet
Thanks to everyone who took the trouble to peek and respond!
Don’t be so quick to give up on unicode. It’s supposed to be the new standard for all future HTML applications.
I’m suprised just how many different systems were able to see the Hebrew characters. More than if you used the symbol font.
Those who can’t see the Hebrew characters should poke around their system and browser settings to see if they can get a unicode font up and running. The web support sites for their software and systems should (in a moral sense) have the patches needed to make unicode work.
Thanks, moriah!
The problem, as I see it, is that a significant portion of browsers still aren’t configured to display Unicode by default. Sure, they can be tweaked - usually quite easily - but I can’t count on everyone seeing what I want them to see (whether it’s a quote from the OT, or maybe something in Arabic, Japanese, you name it…).
Since it seems to work for most, I may actually try using Unicode in the future if really warrented, but I’ll always have to include a description and a caveat, instead of relying on everyon’s broweser to show them what I see.
We’re getting there…
שלום (Shalom) and תודה (Toda = thanks!) again everybody!