Peter:
Only once have I sent you Hebrew encoded as character entities. All the other
times, I wrote Hebrew, at least once specifically encoded as UTF-8, and
somewhere between my screen and yours it was translated to character
entities. Yet when you replied, quoting my Hebrew which was changed to
character entities, my browser rendered it as Hebrew. Even the time I
specifically wrote out the character entities, your quote of it was rendered
as Hebrew when I looked at your reply.
When I looked at http://kodesh.snunit.k12.il/i/t/t0101.htm both Camino and Safari read the third line
down in the html to find <meta http-equiv="Content-Type" content="text/html;
charset=windows-1255"> and automatically read the rest of the page as Windows Hebrew. Hence it
read the page as a Windows document, not unicode. When I tried to read it as unicode, all the Hebrew
was rendered as question marks.
As for the B-Hebrew archive software, it changed the Windows-1255 encoding
to character entities. No problem there, as all browsers should be able to
render that correctly. However, it changed character entities to html text
strings which no browser can render as Hebrew. That is definitely a bug in
the program. The program should read character entities without changing
them to html character strings. ...
... Secondly it should read UTF-8 coding correctly.
...
A non-standard encoding scheme like Windows-1255 requires a Windows aware
browser in order to render it correctly. Secondly, the browser needs to be
set to Windows Hebrew.
Not all mail programs can render character entities correctly.
There is a bug (or more) in the archive program that changes character
entities to html text strings. I have no idea what it would do to UTF-8
encoding. But seeing as it changes Windows-1255 to character entities, I am
not hopeful.
... If we could show the Hebrew text in our email messages, that would be a
big improvement. But apparently that day is not here yet.
Archive powered by MHonArc 2.6.24.