W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

[Bug 25136] You have dropped support for encoding cp862!!

From: <bugzilla@jessica.w3.org>
Date: Thu, 27 Mar 2014 09:44:51 +0000
To: www-international@w3.org
Message-ID: <bug-25136-4285-584WHpAepg@http.www.w3.org/Bugs/Public/>

--- Comment #21 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
(In reply to queency3 from comment #20)

> I need to open TEXT files not html file.


Then you follow the advice that Martin Dürst gave in comment #19: instead of
converting to numerical character references, you must convert directly to
ISO-8859-8. Then, in Firefox, the user just need to select "Hebrew (Visual)"
from the Character Encoding menu.

However, with a little hacking, you could *also* do what I said, namely convert
the output to numeric character references: Just remember to replace the the
file suffix .txt with the file suffix .html. If you do that, then Firefox will
interpret the content as HTML, even if there is no HTML inside the file. Which
means, once again, that the user just need to choose "Hebrew (Visual)" from the
Character Encoding submenu.

Of course, if the text file contains lots of information, interpreting it as
HTML will make all the whitespace be collapsed. To workaround that problem, the
user could apply a User CSS (user style sheet) that do html{white-space:pre}.
You may also read what Martin said about CSS in comment #19.

If you want to promote Firefox, then there it has a user style sheet manager: 

In fact, if you convert the output to numerical character references and apply
the correct CSS via user style sheet, then users do not need to think about the
Character Encoding menu. All they need to think about would be the user style

You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 27 March 2014 09:44:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:04 UTC