Hi Gert, On 07.07.20 15:03, Gert Doering wrote:
Hi,
On Tue, Jul 07, 2020 at 02:53:47PM +0200, Benedikt Neuffer via db-wg wrote:
I don't get it. Does the RIPE DB prevent the usage of punycode?
Can someone give me an example, where punycode doesn't work or why punycode isn't good enough?
From what I understand, the intent is to convert incoming e-mail: attributes in "non-punycode format" to punycode before storing in the DB.
I do not have a very strong opinion on this proposed implementation.
In the long run, I think punycode is a horrible, horrible hack and must die in flames. So if we can have a proper database with proper charset support, my surname would appreciate.
And yes, this will most likely involve UTF-8 internally and export filters (I do not want to see UTF-8, ever, if I can have ISO8859-15 instead - yeah, come, sue me)
I think at the moment it would be easier to update the clients to convert punycode in whatever encoding you prefer. Regards, Benedikt