Re: UTF-8/non-ASCII chars in keys (was Re: 1.0.8 patches)
Yaron Minsky <[email protected]> Wed, 20 Oct 2004 22:48:40 -0400
| Newsgroups | gmane.comp.encryption.pgp.sks,gmane.comp.encryption.pgp.keyserver-folk |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 20 Oct 2004 15:44:49 -0400, Jason Harris <[email protected]> wrote: > On Wed, Oct 20, 2004 at 01:21:37PM -0400, David Shaw wrote: > Right now, there is one instance of Noèl and Köthe (same key) to > test UTF-8 searches with on hkp://keyserver.kjsl.com:11371 . Only keys > with new UTF-8 userids will be searchable by their correct (non-ASCII) > userid words, however, until I fully reload the database to fix the > existing (UTF-8) userids. SKS will require a fix as well since its > is_alnum() currently recognizes extended chars only from decimal > 192 to 255 when parsing userids. Note that both pks and SKS lowercase > all ASCII characters internally for search purposes, but lowercasing > UTF-8 characters may also be necessary. I must admit to not being particularly wise in the ways of UTF-8. So what should I do to the Is_alnum function to make it more UTF-8 friendly? Is there a simple fix, or does SKS need to grok UTF-8 more deeply? y