On Tue, Jun 18, 2002 at 01:24:12PM -0500, Steve Langasek wrote: > > I do hope that tdb ends up going with UTF-8. UCS2 is not particularly > pleasant to work with under Unix; it's not endian-neutral, it doesn't > provide ASCII as a compatibility subset, and it has to be converted to > something else before it can be used by the majority of Unix tools. > Granted, to a certain extent this is already true with tdb because it's > a binary format, but making the import/export tools more complex gives > you less margin for error. Unless Samba chooses UCS-2 as an internal > format for string processing (which I also don't think is the best idea > in the world ;), using UCS-2 as a backend charset seems like an > all-around bad idea, IMHO.
Yes, I think internal format (and format for tdbs) of utf8 seems like the best idea (IMHO). Jeremy.
