unicode-internal status

it now builds and runs when compiled without UNICODE_INTERNAL; this is a sign that the new char tables work, the new char-conversion system basically works, etc. with UNICODE_INTERNAL i've encountered the dreaded "iso2022-preservation" problem -- i.e. byte-compiling an iso2022-encoded lisp file is unlikely to work without further hacking. converting them to utf-8 is not an option since in many cases the lisp code depends on having the proper charset encoded in the actual chars in the file, at least in an old-Mule world. so i'm [a] trying to remove this assumption, [b] putting in hacks to make byte-compilation iso2022-preserving, using private unicode chars. ben