Talk:Hong Kong Supplementary Character Set

Requested move 28 February 2015

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: page moved. Andrewa (talk) 09:02, 8 March 2015 (UTC)

---

HKSCS → Hong Kong Supplementary Character Set – The acronym isn't that widely or commonly known. George Ho (talk) 08:10, 28 February 2015 (UTC)

• Support. Acronyms and abbreviations should be expanded—it makes more sense to visit a page for an abbreviation and get redirected to one with a title that spells out the whole term, than to visit the page for the term and get redirected to an abbreviation. Honestly, I would have just been bold and made the move directly. // coldacid (talk|contrib) 01:50, 4 March 2015 (UTC)
• Support. Full name should be used unless an acronym is widely known, which is not the case here. -Zanhe (talk) 03:01, 8 March 2015 (UTC)

---

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

Recent change in Firefox

The article talks about the support status in Mozilla 1.5 / Gecko 1.8.1. That situation is no longer the present situation. I rewrote the relevant code and the new code shipped in Firefox 43. (Shipping also documented on the support site.) Firefox/Gecko now implements what the Encoding Standard requires for Big5.

The key changes are

• Big5-HKSCS is now just a label (aka. alias) for Big5 and the two are no longer treated as distinct encodings.
• Support for Big5-UAO was removed and now the Big5 decoder supports HKSCS.
• Instead of some input getting mapped to the BMP Private Use Area, mappings to the Supplementary Ideographic Plane are used as appropriate.
• To avoid sending extension byte sequences to servers that might not understand them, the Big5 encoder never emits HKSCS byte sequences. E.g. in form submission, those characters are submitted as numeric character references when the encoding of the submission is Big5.

It would be appropriate to edit the article to reflect this change. (I'm not editing the article myself to avoid running afoul the COI editing rules, since I wrote the code.)

Hsivonen (talk) 07:06, 5 February 2016 (UTC)

Edited it with a reference to the WHATWG encoding standard. Feel free to add more detail including which versions of Firefox and Chrome follow the standard. - Yuhong (talk) 19:58, 16 August 2017 (UTC)

Thank you. In order to steer clear of COI editing, I'm refraining from editing the page myself, but I suggest. Taking merging the paragraphs:

"Mozilla 1.5 and above supports HKSCS, with HKSCS-2004 support added into Gecko 1.8.1 code base. Unlike the above-mentioned patch, Mozilla uses its own code page table. However, the fix for bug 343129 does not support characters mapped to code points above Basic Multilingual Plane."

and

"The WHATWG Encoding Standard includes HKSCS in decoding but not in encoding, and always does even with the plain Big5 label. Newer browsers follow the standard, including Firefox."

and merging them along the lines of

"The WHATWG Encoding Standard includes HKSCS in decoding but not in encoding, and always does even with the plain Big5 label. Newer browsers follow the standard, including Firefox since version 43. (From Mozilla 1.5 to Firefox 42, HKSCS was supported with non-Basic Multilingual Plane characters mapped to the Private Use Area.)"

Hsivonen (talk) 15:50, 1 January 2020 (UTC)

References

Reply 1-JAN-2020

  Unable to implement  

• The proposed merged sentence does not contain any references. Please provide references for the merged claim statement you are making.
• Please note, any references used in the portions of the statement which were merged ought to be included in the merged proposal here on the talk page, taking care to place them in their required positions within the text, per WP:INTEGRITY.
• When ready to proceed with the requested information, kindly change the {{request edit}} template's answer parameter to read from |ans=yes to |ans=no. Thank you!

Regards,  Spintendo  20:11, 1 January 2020 (UTC)

glibc/Linux support

"HKSCS support was added to glibc in 2000, but it has not been updated since then." I'm a little curious, is it needed/neglected? I could have thought C libraries, only needed to support UTF-8 (or UTF-16) and the rest of Unicode support elsewhere? comp.arch (talk) 15:02, 3 October 2016 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on Hong Kong Supplementary Character Set. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20050405003036/http://cerg1.ugc.edu.hk/cergprod/static/download_font.jsp to http://cerg1.ugc.edu.hk/cergprod/static/download_font.jsp
• Added {{dead link}} tag to http://freefonts.oaka.org/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 12:16, 6 November 2017 (UTC)