Unicode and APIs

[Ken Raeburn]

On Sep 21, 2007, at 10:24, Sam Hartman wrote:
> Can you see a way to make app does encoding work with any of the
> existing IETF i18n proposals?

Probably not cleanly.  But even if we assume we can do any necessary  
conversions in the library, I'm not sure a single flag is adequate,  
with our existing data structures.

If "everything is UTF-8" is set, do we convert client principal names  
on the server side?  If so, what encoding do we assume for the wire  
representation?  Remember, the local encoding on the server might be  
UTF-8 already; do we assume ISO-8859-something, or just fail?

The resolution of the file-format issues Jeff raises (plus the  
krb5.conf issue I mentioned) might affect the API, too.

Ken