> I started having to deal with Unicode back around 2001. I don't remember the date, but I first had to deal with unicode when it was a 16-bit encoding (pre- s

> I started having to deal with Unicode back around 2001. I don't remember the date, but I first had to deal with unicode when it was a 16-bit encoding (pre- surrogate pairs). > I mean, cave paintings were color and kinda ideographic Sure, but they weren't text, which is what we were actually talking about. > you can use colored [whatever] That's a property of the rendering, not of the characters; eg <font color=red>X</font> is a colored font tag containing a non-colored character (er, a character without color information), not vice-versa. > Let's put it this way: there are a lot of mistakes to fix once we get the time machine working. Mistakes in Unicode are very, very far down the priority list. That's fair; I have a very long and very angry priority list, but I was mainly just objecting to > all [rather than some] this complexity [is] not the UC's fault and grabbing a couple of specific examples off the top of my head. (Although now I realize I never got around to complaining about zero-width joiner, or 'skin tone' modifiers, or parity sensitive flag characters, or...)