At 4:51 am +0100 24/1/01, Bart Lateur wrote:
| The FTP no longer seems to work. (It didn't when I tried it.) But http
| does:
|
| <http://www.unicode.org/Public/MAPPINGS/VENDORS/>
Sorry, I missed out the second ftp -- <ftp://ftp.unicode org/>
| And, to be pedant, you don't want the Window character set to turn into
| HTML, but ISO-Latin-1. That character set fully agrees with the lower
| 256 codes of Unicode. So, just a conversion from Mac to Unicode, is
| enough.
I quite agree. This is what I wrote before posting the first table. To use
obsolescent charsets in an age when Unicode is finally taking off is simply to
perpetuate the problem that Unicode solves -- besides not all browsers respond as they
should to the charset decalration, leaving the reader in theory to change his encoding
view, in practice just baffled.
| And, for those characters that don't exist in ISO-Latin-1: you can still
| use numerical entities, with Unicode character number, and it'll work.
| For example, the bullet is 0x2022, or 8226 in decimal. Well: both
| "•" and "•" work, even on a PC. Tested with Netscape 4.76
| and MSIE5.0.
This is just what I did in the Applescript/Perl droplet I next posted, and this is the
mapping (hex) I use myself. I do find the use of hex preferable since the hexadecimal
renderings give a pretty good guide to the range of the character, 03xx and 1Fxx for
example being the two Greek ranges, the second of which is sadly not yet implemented
either in WindowsNT or MacOS 8. Have they got round to supplying proper Greek fonts
in OS X does anyone know?
JD
