Re: [Bug 27851] Add MS932 as a label of Shift_JIS

On Wed, Jan 21, 2015 at 1:44 AM, Anne van Kesteren <> wrote:

> On Tue, Jan 20, 2015 at 9:07 PM, Shawn Steele
> <> wrote:
> > To me it feels like encouraging bad behavior to make the bad behavior
> "standard".
> Basically:
> * There are less clients than content
> * It's easier to update clients than content
> There are some tradeoffs to how far we are willing to bend over
> backwards, but if we have data indicating adding a label could help a
> ton of users, there's no reason not to add it to all clients.
> > To further randomize, what are other folks doing about Zawgyi encoded
> Burmese text?  It's mangled Unicode and typically incorrectly declared as
> Unicode.  So it only works with the fonts that expect the non-Unicode
> encoding.
> I would expect such documents to include the font. Any examples?

There are lots of them. It's similar to pages in India and other South and
SE Asian countries(and eleswhere)  that declare to be in ISO-8859-1 or
windows-1252 but use 'font encoding' to represent scripts in those

Zawgy is  even worse than those mentioned above because it misuses 'UTF-8'
label. Its encoding structure is UTF-8, but Unicode codepoints in those
documents mean different things than in the Unicode. (BTW, I heard that
there are some Malayalam web sites that also 're-purpose' UTF-8 in a
similar way).

Even in a single document, the "encoding" can change depending on what font
is used for a DOM element.

I think it's better NOT to recognize / support them. Burmese is
well-supported in Unicode and we'd better encourage/promote the standard
way of representing Burmese/Myanmar.

There are extensions for Firefox and Chrome for on-the-fly transcoding of
them to Unicode.

For Zawgyi specific extensions, see Firefox should have
similar extensions.


> --

Received on Wednesday, 21 January 2015 11:21:44 UTC