...8859-x and you're string has utf8/16.
Why do you have to output...

...specific encoding, C-equivalent)
create utf8  (1 byte of UTF8)
create utf16 (2 bytes of...

...UNICODE character. Whether it comes from an utf8, utf16 or utf32 string shouldn't matter...

...which the old system would store as utf8 with no problem. s3 is 8 bits...

...it to char (or maybe character), giving:

utf8  (todays char)
utf16 (todays wchar)
char  (todays...

...C = Foo[4];
  if (C.encoding = unicode.utf8)
  {
     foreach (ubyte b; C)
     {
       . . .
     }
   }


We can then...

...it is causing some confusion.

The types "utf8" "utf16" and "utf32" do not in fact...

...explaining it _and_ picked terrible names.

The "utf8", "utf16" and "utf32" types I refer to...

...actually mean something like:

ascii_char (not utf8) (code point < 128)
ucs2_char (not utf16...

...don't see the point of the utf8, utf16 and utf32 types. They can all...