Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: HKSCS


Related Topics

  
  Microsoft Hong Kong Supplementary Character Set
The HKSCS is a supplementary character set that includes Chinese characters used in Hong Kong but are not contained in the Big-5 standard character set.
There are two code allocation schemes for the HKSCS, one for Big-5 and the other for ISO 10646/Unicode.
And the HKSCS is formerly named as "Government Chinese Characters Set" i.e.
www.microsoft.com /hk/hkscs   (444 words)

  
  HKSCS(5)
HKSCS, the Hong Kong Supplementary Character Codeset, is a supplementary character set developed by the Chinese government, in collaboration with the Chinese Language Interface Advisory Committee, to provide Chinese characters needed in computing in Hong Kong.
The characters contained in HKSCS are only for computer use and, as developed by the Chinese government, can be represented as either Big-5 or Unicode.
HKSCS Character Groups HKSCS, as initially developed in 1999, contained 4702 Chinese characters specific to the Hong Kong environment and used in electronic communication and data exchange conducted in Chinese.
h30097.www3.hp.com /docs/base_doc/DOCUMENTATION/V51B_HTML/MAN/MAN5/0009____.HTM   (285 words)

  
  NationMaster - Encyclopedia: HKSCS   (Site not responding. Last check: )
The Hong Kong Supplementary Character Set (commonly abbreviated to HKSCS) is a set of Chinese characters -- 4,702 in total in the initial release -- used exclusively in Cantonese.
Subsequently, the HKSCS-1999 (HKSCS 1999 specification) was born.
The HKSCS is currently supported by Big5 and the ISO 10646.
www.nationmaster.com /encyclopedia/HKSCS   (248 words)

  
  YourArt.com >> Encyclopedia >> HKSCS   (Site not responding. Last check: )
The Hong Kong Supplementary Character Set (香港增補字符集; commonly abbreviated to HKSCS) is a set of Chinese characters -- 4,702 in total in the initial release -- used exclusively in Cantonese.
The HKSCS is encoded in Big5 and ISO 10646.
HKSCS support was added to glibc since 2000, but it has not been updated afterwards.
www.yourart.com /research/encyclopedia.cgi?subject=/HKSCS   (543 words)

  
 [No title]
To facilitate electronic communication in the Hong Kong Special Administrative Region (SAR), the Hong Kong Supplementary Character Set (HKSCS), a supplement to the standard character set of Big-5, was developed in 1999.
This supplementary character set includes characters collected from various sectors in Hong Kong and represents a common set for the community.
HKSCS specifies two coding schemes -- one is the extension to the Big-5 coding scheme and the other one is an extension to the ISO 10646 standard.
www.iana.org /assignments/charset-reg/Big5-HKSCS   (360 words)

  
 I'm not a Klingon : CP 951 & HKSCS
I'm not a Klingon : CP 951 and HKSCS
Previously we provided Hong Kong Supplementary Character Set (HKSCS) Support for Windows XP Platform which was effectively a replacement for the 950 code page with mappings to the Unicode PUA.
The safest bet for applications developers to have consistent support is to use Unicode, which supports the HKSCS characters now, so you don't have to worry about the PUA font mappings or other issues that have caused data portability issues between versions or systems.
blogs.msdn.com /shawnste/archive/2007/03/12/cp-951-hkscs.aspx   (0 words)

  
 [No title]
One thing we should not forget is that there are some characters in HKSCS that are not included in Unicode (1,648 characters when using Unicode3.0, or 2,175 characters when using Unicode1.1, 2.0, or 2.1).
Big5 encoding of HKSCS Unicode1.1, 2.0, 2.1, 3.0, or 3.1 0x8540 (---------------------(U+F12C User defined characters of HKSCS HKSCS heavily utilizes Big5 UDC and Unicode PUA, but HKSCS itself provides UDC area in Big5 encoding (0x8140 through 0x84FE) which is mapped to Unicode PUA (U+EEB8 through U+F12B) so that users can define their own characters.
From CodePage 950 to Big5 encoding of HKSCS If the characters in the database are encoded in GCCS and the database (encoded) character set is configured as CodePage 950 (Oracle’s name is ZHT16MSWIN950), and if you wish to migrate to the Big5 encoding of HKSCS, then the database needs to be migrated to Oracle’s ZHT16HKSCS.
www.unicode.org /iuc/iuc18/papers/b19.doc   (3361 words)

  
 [No title]   (Site not responding. Last check: )
The aim of the HKSCS is to provide a common Chinese language interface to facilitate electronic communication in Chinese.
Currently, we provide the Big-5 and ISO 10646 codes for HKSCS characters (http://www.info.gov.hk/digital21/eng/hkscs/document.html) which are key to the success of Chinese data interchange.
HKSCS in Unihan (derived from unihan.txt from UniHan 3.2 database)
cs-people.bu.edu /butta1/personal/hkscs   (378 words)

  
 Unicode and hkscs
I apologize that I am not very familiar with HKSCS, but what I can find on this standard seems to indicate that it is a standard set of characters that can be mapped into the user-defined regions of Big-5 or Unicode/ISO10646.
If by "hkscs" you mean characters encoded in the user-defined range of code points in the Unicode standard, then these could be stored in a Unicode column and would be handled just like surrogates or undefined Unicode characters as described above.
However, if by "hkscs" you are referring to Hong Kong data encoded with the Big-5 character set, that cannot be stored in the same column as Unicode data because the encoding schemes are completely different.
www.webservertalk.com /message286857.html   (433 words)

  
 Cannot insert HKSCS into VARCHAR2 column ...
I am sure that the HKSCS characters that I entered are in Big5 format, not Unicode format.
The HKSCS characters are stored and displayed correctly, regardless of using SQL Plus or C# program accessing these.
In the SQL*Plus case, the HKSCS characters are in their Big5 UDA/VDA codes.
forums.oracle.com /forums/thread.jspa?threadID=291577   (628 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.