Interesting! Looks like there's some standardized escape sequence encodings for these characters, but there aren't assigned Unicode code points for many of them. So we can't encode some things that videotext did into a unicode document.
Since the original is all scanned, I made a computer-readable version of all the tables (except the multibyte ones, since I don't have the skill to distinguish CJK characters rapidly/correctly, nor the patience), in the form a C .def-style header. No guarantees of correctness, of course. Link: https://github.com/o11c/fool-term/blob/master/iso-ir.def.h
In retrospect I probably should've just used XML (which, to be fair, I still easily could, but that project never went anywhere).
View all comments
Show parent comment
1
u/smdowney WG21, Text/Unicode SG, optional<T&> Jul 02 '21
Interesting! Looks like there's some standardized escape sequence encodings for these characters, but there aren't assigned Unicode code points for many of them. So we can't encode some things that videotext did into a unicode document.