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: Wed, 26 Mar 2014 04:29:23 +0000
To: www-international@w3.org
Message-ID: <bug-25136-4285-lAIwSxhBy6@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25136

--- Comment #12 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
(In reply to queency3 from comment #9)
> and may i add that iceweasel identify the ibm862 automatically 
> and open my text files as i click on them .
> 
> this is how i see "the leading browser" operates .
> firefox is a wide trademark its a shame you choose to drop its potential.

One reason to continue to *not* support CP862 is that Firefox (and therefore
probably as well iceweasel/icecat) supports it as a *visual* order hewbrew
encoding. 

Whereas IE and Safari/Webkit support it as a *logical* order - aka
bidirectional - encoding.

Thus, unless Firefox is aligned with Safari/IE - or the other way around, we
will not have compatible implementations. Thus, the spec must decide who is
correct, IE+Safari or Firefox. My guess is that Firefox would have to be
aligned with IE+Safari.

Since you speak about Firefox, I suppose that the files you are talking about,
requires visual order. Am I right? Or would logical order work for you?

The spec cannot keep CP862 if the only reason is that you need the exact
implementation that Firefox has. The encoding spec must isntead design
something inter-operable. 

But from another angle: Since Firefox supported it as visual order, it could
perhaps be said to be correct of Firefox to drop support regardless. That move
does, in principle not prevent that it can be re-implemented in Firefox, as
logical order.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 26 March 2014 04:29:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:36 UTC