In 2005, Unicode, the standard that gives every character a number and a permanent name, added sideways brackets for Chinese written top to bottom. One shipped as PRESENTATION FORM FOR VERTICAL RIGHT WHITE LENTICULAR BRAKCET.
Fixing it would take one small edit. Unicode refused. Those names work as identifiers. Some programming languages let you call up a character by typing its exact name, and Unicode promises that a published name never changes. Correct the spelling, and code that trusted the promise breaks. Leave it, and the only cost is a wince from whoever reads the chart.
So the committee put the correction beside the error: a second official name, spelled properly and guaranteed to be just as permanent.
Once other people build on a mistake, erasing it no longer counts as a correction. What remains is to label it where everyone can see.
The character: ︘, code number U+FE18
What it is: the bracket 〗 turned on its side, for vertical Chinese text
Why it exists: China's national text-encoding standard already had it, and Unicode needed a match so text could convert without loss
Its partner, U+FE17: the left-hand bracket, spelled correctly from day one
Name #1 (2005): …LENTICULAR BRAKCET, permanent
Name #2 (2006): …LENTICULAR BRACKET, an official "alias" listed in the file NameAliases.txt, also permanent
The paper trail: a 2005 proposal, Handling 'defective' names, cataloged this typo and others like it
See it yourself: the current chart prints the typo, with the corrected alias marked ※ beneath it
For app builders: show people any friendly or translated name you like, and leave the official one untouched

