Remove support for geostd8

RESOLVED FIXED in mozilla12

Status

()

Core
Internationalization
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: Ms2ger, Assigned: Ms2ger)

Tracking

({dev-doc-complete})

Trunk
mozilla12
dev-doc-complete
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

7 years ago
Created attachment 501673 [details] [diff] [review]
Patch v1

Anne van Kesteren's research (<https://bitbucket.org/annevk/webencodings/>)
suggests that no other browser supports this charset. Also, it was never registered at IANA. I believe we should improve interoperability by dropping support.
Flags: in-testsuite-
Attachment #501673 - Flags: review?(smontagu)
Removing support for things just because we're the only browser that supports them seems to me to be taking interoperability too far.
What's the point in supporting them, though?  Is there content that uses this encoding?  If people are creating new content, wouldn't it be better if they use UTF-8 and indicate language with the lang attribute?

Comment 3

7 years ago
There is a couple of reasons I would like browsers to consider removing encodings only they support (Opera will in due course remove support for windows-sami-2 I hope):

1. Reduces code complexity.
2. Lowers the possibility that web content will rely on support.
3. Removes the possibility that web content will use it as label while assuming non-support because it is not tested in the browser that has support.

And overall I think that tightening up the legacy encodings so that they can become a fixed list of legacy encodings shared among all browsers in the long term is a good idea. It also gets us closer to the goal of being able to define exactly what you need to do to implement a browser that can process web content around the world.
Gia, do you have any comments on this?

Comment 5

6 years ago
Ping.
Geostd8 is not even registered on the IANA registry.
https://www.iana.org/assignments/character-sets
Moreover, the implementation was broken until 2009.
https://bugzilla.mozilla.org/show_bug.cgi?id=472746
So I don't believe someone relies on the support for this encoding.
Comment on attachment 501673 [details] [diff] [review]
Patch v1

Review of attachment 501673 [details] [diff] [review]:
-----------------------------------------------------------------

OK, so be it (though I would like to have got confirmation from someone in the Georgian community)
Attachment #501673 - Flags: review?(smontagu) → review+

Comment 8

6 years ago
sorry [for the late answer],
Geostd8 is the encoding approved by the local government (not abolished yet).
For now there are [only] few sites using mentioned encoding for the content.

Anyway, personally i have no objection for removing the support.
(Assignee)

Comment 9

6 years ago
Thanks.

https://hg.mozilla.org/mozilla-central/rev/b3030d5f893b
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Keywords: dev-doc-needed
Resolution: --- → FIXED
Target Milestone: Future → mozilla12
Noted on:

https://developer.mozilla.org/en/Character_Sets_Supported_by_Gecko

Also listed on Firefox 12 for developers.
Keywords: dev-doc-needed → dev-doc-complete
You need to log in before you can comment on or make changes to this bug.