On Wed, Sep 09, 2009 at 06:18:11PM -0400, Chuck Lever wrote: > IDNs are UTF16. /var therefore has to support UTF16 filenames; either > byte in a double-byte character can be '/' or '\0'. That means the > underlying fs implementation has to support UTF16 (FAT32 anyone?), and > the system's locale has to be configured correctly. If we decide not to > depend on the file system to support UTF16 filenames, then statd has to > be intelligent enough to figure out how to deal with converting UTF16 > hostnames before storing them as filenames. Then, we have to teach > matchhostname() and friends how to deal with double-byte character > strings... Googling around.... Is this accurate?: http://en.wikipedia.org/wiki/Internationalized_domain_name That makes it sound like domain names are staying ascii, and they're just adding something on top to allow encoding unicode using ascii, which may optionally be used by applications. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
