Post without Account — your post will be reviewed, and if appropriate, posted under Anonymous. You can also use this link to report any problems registering or logging in.
Example 1, corefonts with default (latin1) encoding: I don't think it should be considered a problem if non-Latin-1 characters (t-caron and c-caron) don't show up when using "latin1" encoding, even though they are defined in the font.
Example 2, corefonts with explicit "UTF-8" encoding, none of the non-ASCII special characters are recognized. Same with "utf8" encoding. Is "-encode" supposed to be used when the input stream is already UTF-8? I would expect all three special characters to be recognized under UTF-8.
Should this be treated as a bug of some sort? That is, correct UTF-8 sequences are not being recognized under default and UTF-8 encoding?
I'm not sure why 020_corefonts shows t-caron and s-caron under "latin1" encoding,
I don't see a problem with corefonts rejecting characters which are not true Latin-1, when "latin1" encoding is specified, but it needs to be consistent with other encodings and inputs.