[HTML] Webpage containing Hebrew characters not displaying properly - part2

[HTML] Webpage containing Hebrew characters not displaying properly - part2

Regarding an earlier posting
   Webpage containing Hebrew characters not displaying properly

I wrote that "the webpage in question, when it resides locally on my computer, it displays nicely. However, when it resides on my website, it does not display properly in Firefox, IE and Chrome".

Later on realized my error. I had been coding in Notepad and didn’t realize I need to save in UTF-8 format, rather than Unicode. Once I changed it to UTF-8 it displayed fine.

So now I am wondering why a Unicode file will work ok from the local machine but not from the server???

Any suggestions would be greatly appreciated.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

To answer that question, you'll have to take a look at the coding of the formats (since I'm a bit lazy, I recommend to read the articles on UNICODE and UTF-8 on Wikipedia ...).

I short: UTF8 is downward compatible with ASCII-7, while UNICODE is not.

I presume that some component in the middle from the server to you isn't aware of UNICODE or at least labels it not that way in the mime type headers. And a program that expects ASCII or UTF-8 (because the mime-header tells to do so) will produce trash when fed with UNICODE.

If you want to view the difference, try to load the UNICODE text into an old, non-Unicode editor ... and try the same with it in UTF-8.

Locally your text will be opened as file (I suppose) , where the browser itself needs to analyze the file due to the lack of an mime -type info. It will identify it as UNIODE and display it correct.

Due to the aforementioned compatibility, ASCII-7 (which could be seen as a valid subset of UTF-8) could be interpreted robust with the UTF-8 parser as well, so it could be presumed that the browser will interpret UTF-8 correct even if mislabelled as ASCII-7.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CE101Author Commented:
Thank you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.