• Images
• Videos
• Documents
• Books
• Articles

History and naming

VISCII was designed by the Vietnamese Standardization Working Group (Viet-Std Group)¹ led by Christopher Cuong T. Nguyen, Cuong M. Bui, and Hoc D. Ngo based in Silicon Valley, California in 1992 while they were working with the Unicode consortium to include pre-composed Vietnamese characters in the Unicode standard. VISCII, along with VIQR, was first published in a bilingual report in September 1992, in which it was dubbed the "Vietnamese Standard Code for Information Interchange".² The report noted a proliferation in computer usage in Vietnam and the increasing volume of computer-based communications among Vietnamese abroad, that existing applications used vendor-specific encodings which were unable to interoperate with one another, and that standardisation between vendors was therefore necessary. The successful inclusion of composed and precomposed Vietnamese in Unicode 1.0 was the result of the lessons learned from the development of 8-bit VISCII and 7-bit VIQR.³

The next year, in 1993, Vietnam adopted TCVN 5712, its first national standard in the information technology domain.⁴ This defined a character encoding named VSCII, which had been developed by the TCVN Technical Committee on Information Technology (TCVN/TC1), and with its name standing for "Vietnamese Standard Code for Information Interchange".⁵ VSCII is incompatible with, and otherwise unrelated to, the earlier-published VISCII.⁶ Unlike VISCII, VSCII is a "Vietnamese Standard" in the sense of a national standard.

VISCII and VIQR were approved as the informational-status RFC 1456, attributed to the Viet-Std group and dated May 1993. As is the case with IETF RFCs, RFC 1456 notes them to be "conventions" used by overseas Vietnamese speakers on Usenet, and that it "specifies no level of standard". In spite of this, it continues to call VISCII the "VIetnamese Standard Code for Information Interchange" (the same name taken by VSCII).⁷ The labels VISCII and csVISCII are registered with the IANA for VISCII, with reference to RFC 1456.⁸ (There is, on the other hand, no official IANA label for TCVN 5712 / VSCII, although x-viet-tcvn5712 was previously supported by Mozilla Firefox.⁹)

Design

A traditional extended ASCII character set consists of the ASCII set plus up to 128 characters. Vietnamese requires 134 additional letter-diacritic combinations, which is six too many. There are (short of dropping tone mark support for capital letters, as in VSCII-3) essentially four different ways to handle this problem:

1. Use variable-width encoding (as does UTF-8)
2. Include combining diacritical marks for tone marks (as do VSCII-2 and Windows-1258) or for diacritics in general (as do ANSEL and VNI)
3. Replace some ASCII punctuation, preferably punctuation which is not invariant in ISO 646 (as does VNI for DOS)
4. Replace at least six of the basic ASCII control characters (as do VPS and VSCII-1)

VISCII went for the last option, replacing six of the least problematic (e.g., least likely to be recognised by an application and acted on specially) C0 control codes (STX, ENQ, ACK, DC4, EM, and RS) with six of the least-used uppercase letter-diacritic combinations.¹⁰ While this option may cause programs that use those control codes to malfunction when handling VISCII text, it creates fewer complications than the other two options (the designers note that non-8-bit clean transmission had been found to pose more difficulty in practice than the control character re-use).¹¹ Nonetheless, locations of both C0 or C1 control characters and the codes used for the non-breaking space in ISO-8859-1, Mac OS Roman and OEM-US were deliberately assigned to uppercase letters, with the intention of making use of lowercase codepoints with an all-capital font a serviceable workaround if graphical characters could not be displayed for those codes.¹²

However, using up all the extended code points for accented letters left no room to add useful symbols, superscripted numbers, curved quotes, proper dashes, etc., like most other extended ASCII character sets.

Location of characters deliberately mostly follows ISO-8859-1 where there are characters in common between the two code pages (the uppercase Õ being noted as an exception), motivated by user friendliness concerns.¹³

Support

VISCII is partially supported by the TriChlor Software Group in California, which has released various VISCII-compliant software packages, libraries, and fonts for MS-DOS and Windows, Unix, and Macintosh. VISCII-compliant software is available at many FTP sites.

VISCII was historically offered as an encoding for outgoing email by Mozilla Thunderbird.¹⁴ It was also supported by the Windows Vietnamese keyboard software, WinVNKey, created by Christopher Cuong T. Nguyen and later upgraded through various Windows versions by Hoc D. Ngo and others.

VISCII was mostly used by overseas Vietnamese speakers, with VSCII (TCVN) being more popular in northern Vietnam and VNI being more popular in southern Vietnam.¹⁵

Character set

See also

• ASCII
• Vietnamese Quoted-Readable (VIQR)
• Vietnamese Standard Code for Information Interchange (VSCII)
• Windows-1258

Further reading

• Flohr, Guido (2016) [2006]. "Locale::RecodeData::VISCII - Conversion routines for VISCII". CPAN libintl-perl. Archived from the original on 2017-01-14. Retrieved 2017-01-14.
• https://www.math.nmsu.edu/~mleisher/Software/csets/VISCII.TXT

External links

• RFC 1456 - Conventions for Encoding the Vietnamese Language
• Vietnamese-Standardization Working Group based in California
• Viet-Std Report 1992
• AnGiang Software
• VISCII-compliant software and fonts for MS-DOS and Windows
• VISCII-compliant software, libraries, and fonts for Unix
• WinVNKey, Vietnamese keyboard driver for Windows supporting multinational character sets, including VISCII
• MacVNKey, VISCII-compliant keyboard driver for Macintosh classic

References

1. Phung, Quang; Ngo, Hoc D.; Bui, Cuong. "Vietnamese-Standard Working Group Home Page". Viet-Std Group. Retrieved 2019-08-23. http://vietstd.sourceforge.net/ ↩

2. Vietnamese Character Encoding Standardization Report - VISCII And VIQR 1.1 Character Encoding Specifications (Technical report). Viet-Std Group. 1992. http://vietstd.sourceforge.net/report/rep92.htm ↩

3. Vietnamese Character Encoding Standardization Report - VISCII And VIQR 1.1 Character Encoding Specifications (Technical report). Viet-Std Group. 1992. http://vietstd.sourceforge.net/report/rep92.htm ↩

4. "[news] TCVN 5712:1993 (VSCII) -- Vietnamese national standard". 1993-06-02. Archived from the original on 2017-01-11. https://web.archive.org/web/20170111042331/http://www.informatik.uni-leipzig.de/~duc/software/misc/tcvn.txt ↩

5. "[news] TCVN 5712:1993 (VSCII) -- Vietnamese national standard". 1993-06-02. Archived from the original on 2017-01-11. https://web.archive.org/web/20170111042331/http://www.informatik.uni-leipzig.de/~duc/software/misc/tcvn.txt ↩

6. Lunde, Ken (13 January 2009). "Chapter 1: CJKV Information Processing Overview (§ Are VISCII and VSCII identical? What about TCVN?)". CJKV Information Processing (2nd ed.). p. 17. ISBN 978-0-596-51447-1. 978-0-596-51447-1 ↩

7. Vietnamese Standardization Working Group (May 1993). Conventions for Encoding the Vietnamese Language. IETF. doi:10.17487/RFC1456. RFC 1456. https://datatracker.ietf.org/doc/html/rfc1456 ↩

8. "Character Sets". IANA. https://www.iana.org/assignments/character-sets/character-sets.xhtml ↩

9. Sivonen, Henri (2014-09-26). "Character encoding changes in m-c require c-c action". mozilla.dev.apps.thunderbird. https://groups.google.com/d/msg/mozilla.dev.apps.thunderbird/2P5kCJJS_WI/oWhT0STivL0J ↩

10. Vietnamese Character Encoding Standardization Report - VISCII And VIQR 1.1 Character Encoding Specifications (Technical report). Viet-Std Group. 1992. http://vietstd.sourceforge.net/report/rep92.htm ↩

11. Vietnamese Character Encoding Standardization Report - VISCII And VIQR 1.1 Character Encoding Specifications (Technical report). Viet-Std Group. 1992. http://vietstd.sourceforge.net/report/rep92.htm ↩

12. Vietnamese Character Encoding Standardization Report - VISCII And VIQR 1.1 Character Encoding Specifications (Technical report). Viet-Std Group. 1992. http://vietstd.sourceforge.net/report/rep92.htm ↩

13. Vietnamese Character Encoding Standardization Report - VISCII And VIQR 1.1 Character Encoding Specifications (Technical report). Viet-Std Group. 1992. http://vietstd.sourceforge.net/report/rep92.htm ↩

14. Sivonen, Henri (2014-09-26). "Character encoding changes in m-c require c-c action". mozilla.dev.apps.thunderbird. VISCII and armscii-8 are special in the sense that, for long time, Thunderbird itself (misguidedly) provided these encodings in the user interface for the choice of outgoing character encoding when composing a message. Therefore, it is possible that there exists a Thunderbird-created legacy of VISCII and armscii-8 email and Usenet posts. https://groups.google.com/d/msg/mozilla.dev.apps.thunderbird/2P5kCJJS_WI/oWhT0STivL0J ↩

15. Ngo, Hoc Dinh; Tran, TuBinh. "5. Why Having Vietnamese Charset (Character Set – Encoding) Conversion?". Some special functions of WinVNKey. http://winvnkey.sourceforge.net/some-special-functions-of-winvnkey.htm#Why_having_Vietnamese_charset_conversion ↩