(Sorry, I should have opened another thread already before.) I have another couple of questions about regimes support. How can synonyms for regimes be defined, so that \enableregime[windows-1250] would have the same effect as \enableregime[win-1250] or \enableregime[cp1250]? And \enableregime[utf8] the same effect as \enableregime[utf]. I don't won't to be discriminating, but \enableregime[windows] is like writing \enableregime[latin] ("il" in ConTeXt I think) and expecting the whole world to understand that you mean latin1. In my opinion it should be left there (for backward compatibility if for nothing else), but deprecated and given an unambigious name like "windows-1252", "windows1252", "win-1252", "win1252", "cp1252" or "windows-western".
Does anyone have any script to test the encoding (which would produce a matrix of (almost) 266 characters)?
(Seems like I should have learnt for my math exam tomorrow instead of writing this.) I meant if someone has a nice macro or a script to produce the 256 (not 266!) characters table (minus non-printable ones), maybe together with the corresponding name (only if it can still be extracted). It should either look like an usual ASCII table (perhaps with a box around like in TeX font tables) or simply one character per line with a decimal and hex number written. More or less in order to be able to test if the regi-* files are OK. I prepared the file by hand, but now as I know where to look for and after I saw the http://czyborra.com/charsets/iso8859.html page, I think it shouldn't be a problem to prepare support for all those usual and unusual encodings at once (only a clever script and some manually-prepared mapping from unicode to ConTeXt names). Unicode is great, but not everyone uses it (even vim behaves pretty system-dependent and cannot always be used for unicode out-of-the-box). (I also forgot to thank Patrick for explaining me some stuff about regimes.) Mojca