From Surf Wiki (app.surf) — the open knowledge base

Specials (Unicode block)

Unicode block containing some special codepoints and two non-characters

Field	Value
blockname	Specials
rangestart	FFF0
rangeend	FFFF
script1	Common
1_0_0	1
2_1	1
3_0	3
nonchar	2
note

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:

, marks start of annotated text
, marks start of annotating character(s)
, marks end of annotation block
, placeholder in the text for another unspecified object, for example in a compound document.
used to replace an unknown, unrecognised, or unrepresentable character
not a character.
not a character.

and 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. 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.

Unicode's 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 would then know that it should switch the byte order for all the following characters.

Its block name in Unicode 1.0 was Special.

Replacement character

The replacement character � (often displayed as a black rhombus with a white 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.

As an example, a text file encoded in ISO 8859-1 containing the German word für 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). Since the replacement is the same for all errors it is impossible to recover the original character.

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 character, which in most cases is an empty box, or "?" or "X" in a box (this browser displays 􏿮), 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.

Unicode chart

History

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

Version	Count	UTC ID	Document
1.0.0	U+FFFD	1
U+FFFE..FFFF	2		(to be determined)
		[doc](https://www.unicode.org/wg2/docs/n2369.doc))
		[N2403](https://www.unicode.org/wg2/docs/n2403.pdf)
2.1	U+FFFC	1
		N1365
		[N1353](https://web.archive.org/web/20200215052615/http://std.dkuug.dk/jtc1/sc2/wg2/docs/n1353.doc)
		[N1603](https://web.archive.org/web/20200215052615/http://std.dkuug.dk/jtc1/sc2/wg2/docs/n1603.doc)
		N1681
		[N1894](https://web.archive.org/web/20200215052615/http://std.dkuug.dk/jtc1/sc2/wg2/docs/n1894_02n3188_fpdam%2018.pdf)
3.0	U+FFF9..FFFB	3
		N1727
		[N1703](https://web.archive.org/web/20200215052615/http://std.dkuug.dk/jtc1/sc2/wg2/docs/n1703w97.doc)
	[html](https://www.unicode.org/L2/L1998/98281R.htm))
		[N1861](https://www.unicode.org/wg2/docs/n1861.pdf)
		[doc](https://www.unicode.org/wg2/docs/n1884.doc))
		[N1920](https://web.archive.org/web/20200215052615/http://std.dkuug.dk/jtc1/sc2/wg2/docs/n1920_02n3210_text_pdam_30_addlatin.pdf)
		[html](https://www.unicode.org/wg2/docs/n1903.htm), [doc](https://www.unicode.org/wg2/docs/n1903w97.doc))
	[doc](https://www.unicode.org/L2/L1998/98419.doc))

References

"Unicode character database". The Unicode Standard.
"Enumerated Versions of The Unicode Standard". The Unicode Standard.
"Corrigendum #9: Clarification About Noncharacters". The Unicode Standard.
"Unicode Technical Standard #35". Unicode Locale Data Markup Language (LDML).
"3.8: Block-by-Block Charts". [[Unicode Consortium]].
(September 29, 2020). "When fonts fall". Figma.
"Recommendations for OpenType Fonts (OpenType 1.7) - Typography".
Proposed code points and characters names may differ from final code points and names

Info: Wikipedia Source

This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page.

unicode-blocks

Want to explore this topic further?

Ask Mako anything about Specials (Unicode block) — get instant answers, deeper analysis, and related topics.

Research with Mako

Free with your Surf account

Content sourced from Wikipedia, available under CC BY-SA 4.0.

This content may have been generated or modified by AI. CloudSurf Software LLC is not responsible for the accuracy, completeness, or reliability of AI-generated content. Always verify important information from primary sources.

Report