> 5. UTF-16 requires string operations that do not make assumptions about > nulls - this means re-implementing most of the C runtime functions to work > with unsigned shorts. footnote: the mad scientist has been there and done that: http://www.pythonware.com/madscientist/ (and you can replace "unsigned short" with "whatever's suitable on this platform") </F>