In the context of the standards document and its accompanying encoding, yes, sideways-Q — the exemplar of the mark — is already a defined character; and so Unicode could just adopt it directly from that source character-set.
But my point was twofold:
1. in the source desktop-publishing files that the standard documents, sideways-Q isn’t a character. It’s an embeddable shape. This shape is the ‘reality’ to which the character in the standard is a reference. Like the difference between a real floppy disk, and the floppy-disk emoji. Making it out to be one would be like encoding a game of hangman drawn on a page as a standard “hangman glyph.” Not the same! Loses meaning!
2. Even if the standards document didn’t have its own character set where sideways-Q was defined as a character, but instead just took a particular desktop-publishing program’s sideways-Q shape and plopped it inline into the text — the fact that the text refers to the mark, requiring you to be able to see the rendering of the glyph to know what it was talking about means that that “sideways-Q exemplar” would inevitably become a Unicode codepoint, in order to encode this document successfully. (In fact, if the standards document were entirely-analogue, e.g. typewritten; and the sideways-Q were drawn onto the page after the fact; then it’d still make it into Unicode in the process of digitizing the work.)
Do you have some particular knowledge/reason for saying so? Other than your comments I can't find any evidence to this effect... maybe I'm simply misunderstanding you. I don't see anything that leads me to believe this was the rationale behind either the creation of the original standard or its inclusion in Unicode.
The sideways Q specifically, like most of this particular set, seems to originate from a British Library internal character set, was included in the earlier 5426-2 set, and from there into Unicode, with the primary interest throughout focusing on bibliographic records, i.e., MARC.
The bit about the difference between the character and the shape/glyph is fine as far as it goes (and does matter here as these older standards didn't really follow that separation) but is similarly true for all of Unicode.
The article expressly states:
> The proximate cause for the encoding of this character was the need to provide roundtrip mapping for encoded characters in ISO 5426-2:1996
What is ISO 5426-2, if not a character set?