This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[db-wg] Proposal to allow non-ASCII characters in "org-name:", "person:" and "role:" attributes

• Previous message (by thread): [db-wg] Proposal to allow non-ASCII characters in "org-name:", "person:" and "role:" attributes
• Next message (by thread): [db-wg] Proposal to allow non-ASCII characters in "org-name:", "person:" and "role:" attributes

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Sander Steffann sander at steffann.nl
Mon Nov 27 16:51:26 CET 2023

Hi Ed,

> We can migrate internally to UTF-8 while keeping the current syntax rules, so nothing changes for the user yet (i.e. the database changes but not the interfaces). 
> 
> Once we use UTF-8 internally we can start to support non-latin-1 characters in attributes and convert interfaces to use UTF-8, as decided by the community.

I think this is a good idea. It's definitely a good first step in the right direction.

Cheers,
Sander

• Previous message (by thread): [db-wg] Proposal to allow non-ASCII characters in "org-name:", "person:" and "role:" attributes
• Next message (by thread): [db-wg] Proposal to allow non-ASCII characters in "org-name:", "person:" and "role:" attributes

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]