ISO/IEC 8859-15

ISO/IEC 8859-15:1999, Information technology — 8-bit single-byte coded graphic character sets — Part 15: Latin alphabet No. 9, is part of the ISO/IEC 8859 series of ASCII-based standard character encodings, first edition published in 1999. It is informally referred to as Latin-9 (and for a while Latin-0). It is similar to ISO 8859-1, and thus also intended for “Western European” languages, but replaces some less common symbols with the euro sign and some letters that were deemed necessary:[1] This encoding is by far most used, close to half the use, by German, though this is the least used encoding for German.

A4A6A8B4B8BCBDBE
8859-1 ¤¦¨´¸¼½¾
8859-15 €ŠšŽžŒœŸ
ISO/IEC 8859-15:1999
MIME / IANAISO-8859-15
Alias(es)latin-9, latin-0, latin-6
StandardISO/IEC 8859
ClassificationISO 8859 (extended ASCII, ISO 4873 level 1)
ExtendsUS-ASCII
Based onISO-8859-1
Preceded byISO-8859-1

ISO-8859-15 is the IANA preferred charset name for this standard when supplemented with the C0 and C1 control codes from ISO/IEC 6429.

Microsoft has assigned code page 28605 a.k.a. Windows-28605 to ISO-8859-15. IBM has assigned code page 923 (CCSID 923) to ISO 8859-15.[2][3]

All the printable characters from both ISO/IEC 8859-1 and ISO/IEC 8859-15 are also found in Windows-1252. Since October 2016, less than 0.1% (actually currently less than 0.02%) of all web sites use ISO-8859-15.[4][5]

History

The identifier ISO 8859-15 was proposed for the Sami languages in 1996, which was eventually rejected, but was passed as ISO-IR 197.[6][7][8]

A proposal called ISO 8859-0 was made in 1997, to replace 4 unused or rarely used ISO 8859-1 characters (¤, ¨, ´, and ¸) with €, Œ, œ, and Ÿ.[9] € became necessary when the euro was introduced. Œ and œ are French ligatures, and Ÿ is needed so that French text can be converted from lower-case to all-caps and back again without loss. Ironically, the last three had already been present in DEC's Multinational Character Set (MCS) in 1983, a character set from which ECMA-94 (1985) and ISO-8859-1 (1987) were derived. Since their original codepoints were now occupied by other characters, less logical codepoints had to be chosen for their reintroduction.

The same proposal also recommended replacing 6 more characters (¢, ¦, ±, ¼, ½, ¾) with "some other characters to cover a maximum of languages".[9] For the euro sign, some wanted to replace the plus–minus sign instead of the currency sign. The currency sign is used in some applications as a field separator and in some others to indicate subtotal. There was strong opposition to this. One person said "The proposed «+-» is not an adequate fall-back, as this sequence, though rarely used, has already a fixed mathematical meaning, quite different from «±»; and, even if a reader would deduce the intended meaning, «±», from the context, «+-» in lieu of «±» will hurt a physicist's æsthetic feelings at least as much as «oe» in lieu of an o-e ligature a Francophone's.."[10] In the end the ± and ¢ were not replaced.

Eventually four characters were selected: Š, š, Ž, and ž, which are used in Finnish and Estonian for the transliteration of Russian loanwords and names. The proposal was renamed to ISO 8859-15.

There were attempts to make ISO 8859-15 the default character set for 8-bit communication, but it was never able to supplant the popular ISO 8859-1. It did see some use as the default character set for the text console and terminal programs under Linux when the euro sign was needed, but the use of full Unicode was not practical, but this has since been replaced with UTF-8.

Coverage

ISO 8859-15 encodes what it refers to as "Latin alphabet no. 9". This character set is used throughout the Americas, Western Europe, Oceania, and much of Africa. It is also commonly used in most standard romanizations of East-Asian languages.

Each character is encoded as a single eight-bit code value. These code values can be used in almost any data interchange system to communicate in the following languages:

Modern languages with complete coverage of their alphabet
Notes
  1. Complete support except for Ǿ/ǿ which are missing. Ǿ/ǿ can be replaced with Ø/ø at the cost of increased ambiguity.
  2. Commonly supported with nearly complete coverage of the Dutch alphabet, as the missing IJ, ij should always be represented as two-character IJ or ij in electronic form.
  3. US and modern British
  4. In 2017, the Council for German Orthography officially adopted a capital, ⟨ẞ⟩, before support for German was complete.
  5. New orthography
  6. Basic classical orthography
  7. Basic classical orthography
  8. Rumi script
  9. Bokmål and Nynorsk
  10. European and Brazilian

Coverage of punctuation signs and apostrophes
See also: Latin-script alphabet

For some languages listed above, the correct typographical quotation marks are missing, since only «, », ", and ' are included.

Also, this encoding does not provide the correct character for the apostrophe, and oriented single high quotation marks, although some texts use the spacing grave accent and spacing acute accent, which are both part of ISO 8859-1, instead of the 6-shaped/9-shaped quotations marks or apostrophes (and this works reliably with some font styles, where all these characters are displayed as slanted wedge glyphs).

Codepage layout

Differences from ISO-8859-1 have the Unicode code point shown underneath the character.

ISO/IEC 8859-15[11][12][13]
0 1 2 3 4 5 6 7 8 9 A B C D E F
0x
1x
2x  SP  ! " # $ % & ' ( ) * + , - . /
3x 0 1 2 3 4 5 6 7 8 9 : ; < = > ?
4x @ A B C D E F G H I J K L M N O
5x P Q R S T U V W X Y Z [ \ ] ^ _
6x ` a b c d e f g h i j k l m n o
7x p q r s t u v w x y z { | } ~
8x
9x
Ax NBSP ¡ ¢ £ €
20AC		 ¥ Š
0160		 § š
0161		 © ª « ¬ SHY ® ¯
Bx ° ± ² ³ Ž
017D		 µ · ž
017E		 ¹ º » Œ
0152		 œ
0153		 Ÿ
0178		 ¿
Cx À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï
Dx Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß
Ex à á â ã ä å æ ç è é ê ë ì í î ï
Fx ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ

Aliases

ISO 8859-15 also has the following, vendor-specific aliases:

See also

References
  1. "ISO-8859-15". IANA. Retrieved 8 March 2016.
  2. "Code page 923 information document". Archived from the original on 2013-02-28.
  3. "CCSID 923 information document". Archived from the original on 2014-12-01.
  4. "Historical trends in the usage of character encodings, November 2018". w3techs.com.
  5. "Frequently Asked Questions". w3techs.com.
  6. TIEKE representing Finnish Standards Association SFS (1999-12-07). Sami supplementary Latin set no 2 (PDF). ITSCJ/IPSJ. ISO-IR-209.
  7. Everson, Michael. "Proposed ISO 8859-15". Retrieved 26 February 2017.
  8. Everson, Michael. "Proposed ISO 8859-14 (later 15)". Retrieved 26 February 2017.
  9. Everson, Michael. "Proposed ISO 8859-0 (later 15)". Retrieved 26 February 2017.
  10. Stolz, Otto (July 11, 1997). "Re: New Draft ISO 8859-0". Unicode Mail List (Mailing list).
  11. Code Page CPGID 00923 (pdf) (PDF), IBM
  12. Code Page CPGID 00923 (txt), IBM
  13. International Components for Unicode (ICU), ibm-923_P100-1998.ucm, 2002-12-03
  14. Baird, Cathy; Chiba, Dan; Chu, Winson; Fan, Jessica; Ho, Claire; Law, Simon; Lee, Geoff; Linsley, Peter; Matsuda, Keni; Oscroft, Tamzin; Takeda, Shige; Tanaka, Linus; Tozawa, Makoto; Trute, Barry; Tsujimoto, Mayumi; Wu, Ying; Yau, Michael; Yu, Tim; Wang, Chao; Wong, Simon; Zhang, Weiran; Zheng, Lei; Zhu, Yan; Moore, Valarie (2002) [1996]. "Appendix A: Locale Data". Oracle9i Database Globalization Support Guide (PDF) (Release 2 (9.2) ed.). Oracle Corporation. Oracle A96529-01. Archived (PDF) from the original on 2017-02-14. Retrieved 2017-02-14.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.