Jump to content

ISO/IEC 8859-15

From Wikipedia, the free encyclopedia
ISO/IEC 8859-15:1999
MIME / IANAISO-8859-15
Alias(es)latin-9, latin-0, latin-6
StandardISO/IEC 8859
Based onISO-8859-1
Preceded byISO-8859-1
Succeeded byUTF-8

ISO/IEC 8859-15:1999,Information technology — 8-bit single-byte coded graphic character sets — Part 15: Latin Alpha bet No. 9,is part of theISO/IEC 8859series of ASCII-based standardcharacter encodings,first edition published in 1999. It is informally referred to asLatin-9(and for a whileLatin-0). It is similar toISO 8859-1,and thus also intended for “Western European” languages, but replaces some less common symbols with theeuro signand 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.

A4 A6 A8 B4 B8 BC BD BE
8859-1 ¤ ¦ ¨ ´ ¸ ¼ ½ ¾
8859-15 € Š š Ž ž Œ œ Ÿ

ISO-8859-15is theIANApreferred charset name for this standard when supplemented with theC0 and C1 control codesfromISO/IEC 6429.

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

All the printable characters from both ISO/IEC 8859-1 and ISO/IEC 8859-15 are also found inWindows-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[edit]

The identifier ISO 8859-15 was proposed for theSami languagesin 1996, which was eventually rejected, but was passed asISO-IR 197.[6][7][8]

ISO 8859-16 was proposed as a similar encoding to today's ISO 8859-15, to replace 11 unused or rarely usedISO 8859-1characters with the missing French Œ œ (at the same spot as same place asDEC-MCSandLotus International Character Set) and Ÿ (which was not at the same place as these sets, as Ý was in that spot for Icelandic), Dutch IJ ij, and Turkish Ğ ğ İ ı Ş ş. The euro sign did not exist at the time.[9]

The draft was as follows:

Proposed (but not adopted) ISO/IEC 8859-15
0 1 2 3 4 5 6 7 8 9 A B C D E F
Ax NBSP ¡ ¢ £ ¤ IJ
0132 		¦ § ij
0133 		© ª « ¬ SHY ® ¯
Bx ° ± Ğ
011E 		ğ
011F 		İ
0130 		µ · ı
0131 		Ş
015E 		º » ş
015F 		½ Ÿ
0178 		¿
Cx À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï
Dx Ð Ñ Ò Ó Ô Õ Ö Œ
0152 		Ø Ù Ú Û Ü Ý Þ ß
Ex à á â ã ä å æ ç è é ê ë ì í î ï
Fx ð ñ ò ó ô õ ö œ
0153 		ø ù ú û ü ý þ ÿ

The name was later changed to ISO-8859-0 and was restructured by 1997. The Turkish characters were removed because it was considered that it would potentially do more harm to Turkish then-current practice while UCS (Unicode) implementation was not that far away, and the DutchIJligature was removed as the existing digraphijwas found to be adequate. It was also considered to add theWelshŴ ŵ and Ŷ ŷ, but that was postponed pending further investigation. 4 unused or rarely usedISO 8859-1characters (¤,¨,´,and¸) were replaced with€,Ÿ,Œ,andœrespectively.[10]€became necessary when theeurowas introduced.Ÿis needed so that French text can be converted from lower-case to all-caps and back again without loss, andŒandœare French ligatures. Ironically, the last three had already been present inDEC'sMultinational Character Set(MCS) in 1983, a character set from whichECMA-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". The reasons for choosing these characters was stated in the proposal.[10] 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 afield separatorand in some others to indicatesubtotal.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."[11] In the end,±was kept, and¤was removed (as originally planned).

Circa 1997/1998 (whenWindows-1252was updated) four characters were selected:Š,š,Ž,andž,which are used inFinnishandEstonianfor thetransliterationofRussianloanwords and names. The proposal was renamed to ISO 8859-15 at the same time. In the end the characters¦,¼,½,and¾were removed, while¢was kept because it was more common than the other four.

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 fullUnicodewas not practical, but this has since been replaced withUTF-8.

Coverage[edit]

ISO 8859-15 encodes what it refers to as "Latin Alpha betno. 9 ". This character set is used throughout theAmericas,Western Europe,Oceania,and much ofAfrica.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 Alpha bet
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 Alpha bet, as the missingIJ,ijshould always be represented as two-character IJ or ij in electronic form.
  3. ^US and modern British
  4. ^In 2017, theCouncil for German Orthographyofficially adopted a capital,⟨ẞ⟩,before support for German was complete.
  5. ^New orthography
  6. ^abBasic classical orthography
  7. ^Rumi script
  8. ^Bokmål and Nynorsk
  9. ^European and Brazilian

Coverage of punctuation signs and apostrophes[edit]

See also:Latin-script Alpha bet

For some languages listed above, the correct typographicalquotation marksare 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[edit]

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

ISO/IEC 8859-15[12][13][14]
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[edit]

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

See also[edit]

References[edit]

  1. ^"ISO-8859-15".IANA.Retrieved8 March2016.
  2. ^"Code page 923 information document".Archived fromthe originalon 2013-02-28.
  3. ^"CCSID 923 information document".Archived fromthe originalon 2014-12-01.
  4. ^"Historical trends in the usage of character encodings, November 2018".w3techs.
  5. ^"Frequently Asked Questions".w3techs.
  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".Retrieved26 February2017.
  8. ^Everson, Michael."Proposed ISO 8859-14 (later 15)".Retrieved26 February2017.
  9. ^Everson, Michael."Proposed ISO 8859-16".Retrieved26 February2017.
  10. ^abEverson, Michael."Proposed ISO 8859-0 (later 15)".Retrieved26 February2017.
  11. ^Stolz, Otto (July 11, 1997)."Re: New Draft ISO 8859-0".Unicode Mail List(Mailing list).
  12. ^Code Page CPGID 00923 (pdf)(PDF),IBM
  13. ^Code Page CPGID 00923 (txt),IBM
  14. ^International Components for Unicode (ICU), ibm-923_P100-1998.ucm,2002-12-03
  15. ^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.Retrieved2017-02-14.

External links[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=ISO/IEC_8859-15&oldid=1232083981"