> Granted, such 128-bit characters might be useful. This would allow various > organizations to define their own characters sets. Space in the global > character encoding space would be allocated in the same way as > IP address space is allocated under IPv6. > > But to conserve file space, it would probably be best to allow intermixing of > 128-bit characters with ASCI text. UTF-8 continues to be the way to do > this, since it just a compression scheme that does not really depend on the fact > that Unicode is currently limited to 32 bits. It could just as easily be extended > to work with much larger character sets.
Agrees, the design of how UTF-8 encodes and decodes can be expanded to support more bits... so that's why UTF8 should be reasonable to be the long term solution for designing i18n applications, including IDN...
