> I have so extended the encoding used to generate the virtual fonts so > that for the ASCII range it matches the Computer Modern expectations > (hence it is totally compatible with plain TeX), and so that the latin1 > encoding used as input will give the correct glyphes. And the cryptic > names will be gone, because loading the (virtual) font will be defined > by calling latin1/the_font. > > Why latin1? Not only because, as a French, I use it, but because it is > compatible with unicode.
perhaps you mean the subset of unicode corresponding to the codepoints encoded by latin1 encoded in utf-8. the system character set is utf-8, and latin1 is not a compatable encoding. utf-8 is assumed everwhere except when the data is inbound, and explicitly tagged as having a different caracter set. programs like upas/fs and webfs do the conversion at the border. there's really no reason for latin1 in 2011. - erik
