Specials (Unicode block)
Template:Short descriptionPage Module:Infobox/styles.css has no content.
| Specials | |
|---|---|
| Range | U+FFF0..U+FFFF (16 code points) |
| Plane | BMP |
| Scripts | Common |
| Assigned | 5 code points |
| Unused | 9 reserved code points 2 non-characters |
| Unicode version history | |
| Page Module:Infobox/styles.css has no content. | |
| 1.0.0 Template:Unicode version/version-to-date | 1 (+1) |
| 2.1 Template:Unicode version/version-to-date | 2 (+1) |
| 3.0 Template:Unicode version/version-to-date | 5 (+3) |
| Unicode documentation | |
| Code chart ∣ Web page | |
| Note: [1][2] | |
Specials is a short Unicode block of characters allocated at the very end of the Basic Multilingual Plane, at U+FFF0–FFFF, containing these code points:
- Page Template:Mono/styles.css has no content.U+FFF9 Script error: No such module "Unicode data"., marks start of annotated text
- Page Template:Mono/styles.css has no content.U+FFFA Script error: No such module "Unicode data"., marks start of annotating character(s)
- Page Template:Mono/styles.css has no content.U+FFFB Script error: No such module "Unicode data"., marks end of annotation block
- Page Template:Mono/styles.css has no content.U+FFFC  Script error: No such module "Unicode data"., placeholder in the text for another unspecified object, for example in a compound document.
- Page Template:Mono/styles.css has no content.U+FFFD � Script error: No such module "Unicode data". used to replace an unknown, unrecognised, or unrepresentable character
- Page Template:Mono/styles.css has no content.U+FFFE <noncharacter-FFFE> not a character.
- Page Template:Mono/styles.css has no content.U+FFFF <noncharacter-FFFF> not a character.
Page Template:Mono/styles.css has no content.U+FFFE <noncharacter-FFFE> and Page Template:Mono/styles.css has no content.U+FFFF <noncharacter-FFFF> are noncharacters, meaning they are reserved but do not cause ill-formed Unicode text. Versions of the Unicode standard from 3.1.0 to 6.3.0 claimed that these characters should never be interchanged, leading some applications to use them to guess text encoding by interpreting the presence of either as a sign that the text is not Unicode. However, Corrigendum #9 later specified that noncharacters are not illegal and so this method of checking text encoding is incorrect.[3] An example of an internal usage of U+FFFE is the CLDR algorithm; this extended Unicode algorithm maps the noncharacter to a minimal, unique primary weight.[4]
Unicode's Page Template:Mono/styles.css has no content.U+FEFF Script error: No such module "Unicode data". character can be inserted at the beginning of a Unicode text as a byte order mark to signal its endianness: a program reading a text encoded in for example UTF-16 and encountering Page Template:Mono/styles.css has no content.U+FFFE <noncharacter-FFFE> would then know that it should switch the byte order for all the following characters.
Its block name in Unicode 1.0 was Special.[5]
Replacement character
The replacement character � (often displayed as a rhombus with a question mark) is a symbol found in the Unicode standard at code point U+FFFD in the Specials table. It is used to indicate problems when a system is unable to render a stream of data to correct symbols.[6]
As an example, a text file encoded in ISO 8859-1 containing the German word Script error: No such module "Lang". contains the bytes 0x66 0xFC 0x72. If this file is opened with a text editor that assumes the input is UTF-8, the first and third bytes are valid UTF-8 encodings of ASCII, but the second byte (0xFC) is not valid in UTF-8. The text editor could replace this byte with the replacement character to produce a valid string of Unicode code points for display, so the user sees f�r.
A poorly implemented text editor might write out the replacement character (0xEF 0xBF 0xBD) when the user saves the file; the data in the file will then become 0x66 0xEF 0xBF 0xBD 0x72. If the file is re-opened using ISO 8859-1, it will display f�r (this is called mojibake). As the editor likely turns different errors into the same replacement character, it is also impossible to recover the original text.
At one time the replacement character was often used when there was no glyph available in a font for that character, as in font substitution. However, most modern text rendering systems instead use a font's Template:Tt character, which in most cases is an empty box, or a ? or X in a box[7] (this browser displays for U+10FFEE), sometimes called a "tofu". There is no Unicode code point for this symbol.
Thus the replacement character is now only seen for encoding errors. Some software programs translate invalid UTF-8 bytes to matching characters in Windows-1252 (since that is the most common source of these errors), so that the replacement character is never seen.[citation needed]
Unicode chart
| SpecialsPage Template:Citation/styles.css has no content.[1]Page Template:Citation/styles.css has no content.[2]Page Template:Citation/styles.css has no content.[3] Official Unicode Consortium code chart (PDF) | ||||||||||||||||
| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | C | D | E | F | |
| U+FFFx | IAA | IAS | IAT |  | � | |||||||||||
Notes
| ||||||||||||||||
History
The following Unicode-related documents record the purpose and process of defining specific characters in the Specials block:
| Version | Final code points[a] | Count | UTC ID | L2 ID | WG2 ID | Document |
|---|---|---|---|---|---|---|
| 1.0.0 | U+FFFD | 1 | (to be determined) | |||
| U+FFFE..FFFF | 2 | (to be determined) | ||||
| L2/01-295R | Page Module:Citation/CS1/styles.css has no content.Moore, Lisa (2001-11-06), "Motion 88-M2", Minutes from the UTC/L2 meeting #88 | |||||
| L2/01-355 | N2369 (html, doc) | Page Module:Citation/CS1/styles.css has no content.Davis, Mark (2001-09-26), Request to allow FFFF, FFFE in UTF-8 in the text of ISO/IEC 10646 | ||||
| L2/02-154 | N2403 | Page Module:Citation/CS1/styles.css has no content.Umamaheswaran, V. S. (2002-04-22), "9.3 Allowing FFFF and FFFE in UTF-8", Draft minutes of WG 2 meeting 41, Hotel Phoenix, Singapore, 2001-10-15/19 | ||||
| 2.1 | U+FFFC | 1 | UTC/1995-056 | Page Module:Citation/CS1/styles.css has no content.Sargent, Murray (1995-12-06), Recommendation to encode a WCH_EMBEDDING character | ||
| UTC/1996-002 | Page Module:Citation/CS1/styles.css has no content.Aliprand, Joan; Hart, Edwin; Greenfield, Steve (1996-03-05), "Embedded Objects", UTC #67 Minutes | |||||
| N1365 | Page Module:Citation/CS1/styles.css has no content.Sargent, Murray (1996-03-18), Proposal Summary – Object Replacement Character | |||||
| N1353 | Page Module:Citation/CS1/styles.css has no content.Umamaheswaran, V. S.; Ksar, Mike (1996-06-25), "8.14", Draft minutes of WG2 Copenhagen Meeting # 30 | |||||
| L2/97-288 | N1603 | Page Module:Citation/CS1/styles.css has no content.Umamaheswaran, V. S. (1997-10-24), "7.3", Unconfirmed Meeting Minutes, WG 2 Meeting # 33, Heraklion, Crete, Greece, 20 June – 4 July 1997 | ||||
| L2/98-004R | N1681 | Page Module:Citation/CS1/styles.css has no content.Text of ISO 10646 – AMD 18 for PDAM registration and FPDAM ballot, 1997-12-22 | ||||
| L2/98-070 | Page Module:Citation/CS1/styles.css has no content.Aliprand, Joan; Winkler, Arnold, "Additional comments regarding 2.1", Minutes of the joint UTC and L2 meeting from the meeting in Cupertino, February 25-27, 1998 | |||||
| L2/98-318 | N1894 | Page Module:Citation/CS1/styles.css has no content.Revised text of 10646-1/FPDAM 18, AMENDMENT 18: Symbols and Others, 1998-10-22 | ||||
| 3.0 | U+FFF9..FFFB | 3 | L2/97-255R | Page Module:Citation/CS1/styles.css has no content.Aliprand, Joan (1997-12-03), "3.D Proposal for In-Line Notation (ruby)", Approved Minutes – UTC #73 & L2 #170 joint meeting, Palo Alto, CA – August 4-5, 1997 | ||
| L2/98-055 | Page Module:Citation/CS1/styles.css has no content.Freytag, Asmus (1998-02-22), Support for Implementing Inline and Interlinear Annotations | |||||
| L2/98-070 | Page Module:Citation/CS1/styles.css has no content.Aliprand, Joan; Winkler, Arnold, "3.C.5. Support for implementing inline and interlinear annotations", Minutes of the joint UTC and L2 meeting from the meeting in Cupertino, February 25-27, 1998 | |||||
| L2/98-099 | N1727 | Page Module:Citation/CS1/styles.css has no content.Freytag, Asmus (1998-03-18), Support for Implementing Interlinear Annotations as used in East Asian Typography | ||||
| L2/98-158 | Page Module:Citation/CS1/styles.css has no content.Aliprand, Joan; Winkler, Arnold (1998-05-26), "Inline and Interlinear Annotations", Draft Minutes – UTC #76 & NCITS Subgroup L2 #173 joint meeting, Tredyffrin, Pennsylvania, April 20-22, 1998 | |||||
| L2/98-286 | N1703 | Page Module:Citation/CS1/styles.css has no content.Umamaheswaran, V. S.; Ksar, Mike (1998-07-02), "8.14", Unconfirmed Meeting Minutes, WG 2 Meeting #34, Redmond, WA, USA; 1998-03-16--20 | ||||
| L2/98-270 | Page Module:Citation/CS1/styles.css has no content.Hiura, Hideki; Kobayashi, Tatsuo (1998-07-29), Suggestion to the inline and interlinear annotation proposal | |||||
| L2/98-281R (pdf, html) | Page Module:Citation/CS1/styles.css has no content.Aliprand, Joan (1998-07-31), "In-Line and Interlinear Annotation (III.C.1.c)", Unconfirmed Minutes – UTC #77 & NCITS Subgroup L2 # 174 JOINT MEETING, Redmond, WA -- July 29-31, 1998 | |||||
| L2/98-363 | N1861 | Page Module:Citation/CS1/styles.css has no content.Sato, T. K. (1998-09-01), Ruby markers | ||||
| L2/98-372 | N1884R2 (pdf, doc) | Page Module:Citation/CS1/styles.css has no content.Whistler, Ken; et al. (1998-09-22), Additional Characters for the UCS | ||||
| L2/98-416 | N1882.zip | Page Module:Citation/CS1/styles.css has no content.Support for Implementing Interlinear Annotations, 1998-09-23 | ||||
| L2/98-329 | N1920 | Page Module:Citation/CS1/styles.css has no content.Combined PDAM registration and consideration ballot on WD for ISO/IEC 10646-1/Amd. 30, AMENDMENT 30: Additional Latin and other characters, 1998-10-28 | ||||
| L2/98-421R | Page Module:Citation/CS1/styles.css has no content.Suignard, Michel; Hiura, Hideki (1998-12-04), Notes concerning the PDAM 30 interlinear annotation characters | |||||
| L2/99-010 | N1903 (pdf, html, doc) | Page Module:Citation/CS1/styles.css has no content.Umamaheswaran, V. S. (1998-12-30), "8.2.15", Minutes of WG 2 meeting 35, London, U.K.; 1998-09-21--25 | ||||
| L2/98-419 (pdf, doc) | Page Module:Citation/CS1/styles.css has no content.Aliprand, Joan (1999-02-05), "Interlinear Annotation Characters", Approved Minutes -- UTC #78 & NCITS Subgroup L2 # 175 Joint Meeting, San Jose, CA -- December 1-4, 1998 | |||||
| UTC/1999-021 | Page Module:Citation/CS1/styles.css has no content.Duerst, Martin; Bosak, Jon (1999-06-08), W3C XML CG statement on annotation characters | |||||
| L2/99-176R | Page Module:Citation/CS1/styles.css has no content.Moore, Lisa (1999-11-04), "W3C Liaison Statement on Annotation Characters", Minutes from the joint UTC/L2 meeting in Seattle, June 8-10, 1999 | |||||
| L2/01-301 | Page Module:Citation/CS1/styles.css has no content.Whistler, Ken (2001-08-01), "E. Indicated as "strongly discouraged" for plain text interchange", Analysis of Character Deprecation in the Unicode Standard | |||||
Page Template:Reflist/styles.css has no content.
| ||||||
See also
References
Page Template:Reflist/styles.css has no content.
- ^ Page Module:Citation/CS1/styles.css has no content."Unicode character database". The Unicode Standard. Retrieved 2023-07-26.
- ^ Page Module:Citation/CS1/styles.css has no content."Enumerated Versions of The Unicode Standard". The Unicode Standard. Retrieved 2023-07-26.
- ^ Page Module:Citation/CS1/styles.css has no content."Corrigendum #9: Clarification About Noncharacters". The Unicode Standard. Archived from the original on Jun 10, 2023. Retrieved 2023-06-07.
- ^ Page Module:Citation/CS1/styles.css has no content."Unicode Technical Standard #35". Unicode Locale Data Markup Language (LDML). Retrieved 2024-08-27.
- ^ Page Module:Citation/CS1/styles.css has no content."3.8: Block-by-Block Charts" (PDF). The Unicode Standard. Version 1.0. Unicode Consortium. Archived (PDF) from the original on 2021-02-11. Retrieved 2020-09-30.
- ^ Page Module:Citation/CS1/styles.css has no content.Wichary, Marcin (September 29, 2020). "When fonts fall". Figma. Archived from the original on 13 June 2021. Retrieved 6 June 2021.
- ^ Page Module:Citation/CS1/styles.css has no content."Recommendations for OpenType Fonts (OpenType 1.7) - Typography". Microsoft Learn. Archived from the original on 19 October 2020. Retrieved 18 October 2020.
Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found.
