This articleneeds moresources forreliability. Please helpimprove this article by addingreliable sources. Unsourced material may bechallenged or removed. Find sources: "Specials" Unicode block – news ·newspapers ·books ·scholar ·JSTOR(April 2010) (Learn how and when to remove this message)

Specials is a shortUnicode block of characters put at the very end of theBasic Multilingual Plane, at U+FFF0–FFFF. Of these 16 code points, five have been used since Unicode 3.0:

• U+FFF9INTERLINEAR ANNOTATION ANCHOR, marks start ofannotated text
• U+FFFAINTERLINEAR ANNOTATION SEPARATOR, marks start of annotating character(s)
• U+FFFBINTERLINEAR ANNOTATION TERMINATOR, marks end of annotation block
• U+FFFCOBJECT REPLACEMENT CHARACTER, placeholder in the text for another unspecified object, for example in acompound document.
• U+FFFD�REPLACEMENT CHARACTER used to replace an unknown, unrecognized, or unrepresentable character
• U+FFFE<noncharacter-FFFE> not a character.
• U+FFFF<noncharacter-FFFF> not a character.

FFFE and FFFF are not unused in the usual way, butguaranteed not to be Unicode characters at all. They can be used to guess a text's scheme, since any text using these is not a correctly encoded Unicode text. Unicode'sU+FEFFBYTE ORDER MARK character can be put at the start of a Unicode text to signal itsendianness: a program reading such a text and finding 0xFFFE would then know that it should switch the byte order for all the following characters.

Its block name in Unicode 1.0 wasSpecial.^[3]

Thereplacement character (�) (often displayed as a blackrhombus with a white question mark) is a symbol found in theUnicode standard at code point U+FFFD in theSpecials table. It is used for problems when something is unable to render a stream of data to a correct symbol.^[4] It is usually seen when the data is not valid and does not match any character:

Consider a text file containing the German wordfür (meaning 'for') in theISO-8859-1 encoding (0x66 0xFC 0x72). This file is now opened with a text editor that thinks that the input isUTF-8. The first and last byte are valid UTF-8 encodings of ASCII, but the middle byte (0xFC) is not a valid byte in UTF-8. So, a text editor could replace this byte with the replacement character symbol to make a valid string of Unicodecode points. The whole string now looks like this: "f�r".

A poorly made text editor might save the replacement character in UTF-8, and the text file data will then look like this:0x66 0xEF 0xBF 0xBD 0x72, which will be displayed in ISO-8859-1 as "f�r" (this is calledmojibake). Since the replacement is the same for all errors this makes it impossible to get the first character. A better (but harder to make) way is to keep the original bytes, including the error, and only convert to the replacement whendisplaying the text. This will allow the text editor to save the original byte sequence, while still showing the error to the user.

At one time the replacement character was used a lot when there was noglyph that can be used in a font for that character. However, most new text rendering systems instead use a font's.notdef character, which most times is an empty box (or "?" or "X" in a box^[5]), sometimes called a "tofu" (this browser displays �). There is no Unicode point for this symbol.

So, the replacement character is now only seen for encoding errors, such as invalid UTF-8. Some software tries to hide this bytranslating the bytes of invalid UTF-8 to matching characters inWindows-1252 (since that is the most likely source of these errors), so that the replacement character is never seen.

The following Unicode-related documents record the purpose and process of defining specific characters in the Specials block:

• Unicode control characters

• Unicode blocks

• Articles needing additional references from April 2010
• All articles needing additional references
• Articles containing German-language text
• Webarchive template wayback links