*** Welcome to piglix ***

* * * * *    piglix project (code-name) Launch Promotions    * * * * *

  • Learn more! ! if you are a bone fide Higher Education establishment and would like to learn how the piglix project may be your answer to the challenges of 'lecture room' replacement strategies, use our feedback page now to tell us about your needs and have someone contact you to explain your options and possibilities.

Specials (Unicode block)

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
1.0.0 1 (+1)
2.1 2 (+1)
3.0 5 (+3)

Specials is a short Unicode block allocated at the very end of the Basic Multilingual Plane, at U+FFF0–FFFF. Of these 16 code points, five are assigned as of Unicode 10.0:

FFFE and FFFF are not unassigned in the usual sense, but guaranteed not to be a Unicode character at all. They can be used to guess a text's encoding scheme, since any text containing these is by definition not a correctly encoded Unicode text. Unicode's U+FEFF Byte order mark character can be inserted at the beginning of a Unicode text to signal its endianness: a program reading such a text and encountering 0xFFFE would then know that it should switch the byte order for all the following characters.

The replacement character � (often a black diamond with a white question mark or an empty square box) is a symbol found in the Unicode standard at codepoint U+FFFD in the Specials table. It is used to indicate problems when a system is unable to render a stream of data to a correct symbol. It is usually seen when the data is invalid and does not match any character:

Consider a text file containing the German word "für" in the ISO-8859-1 encoding (0x66 0xFC 0x72). This file is now opened with a text editor that assumes the input is UTF-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. Therefore, a text editor could replace this byte with the replacement character symbol to produce a valid string of Unicode code points. The whole string now displays like this: "f�r".

A poorly implemented text editor might save the replacement in UTF-8 form; 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" (see mojibake). Since the replacement is the same for all errors this makes it impossible to recover the original character. A better (but harder to implement) design is to preserve the original bytes, including the error, and only convert to the replacement when displaying the text. This will allow the text editor to save the original byte sequence, while still showing the error indicator to the user.


Social Distancing Order In Force!

Don't forget! that your welfare and that of all your friends and colleagues here is of primary concern and a distance of six feet (1.8m) minimum is required at all times.