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/db-wg@ripe.net/

[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 ]

Leo Vegoda leo at vegoda.org
Fri Nov 24 16:18:08 CET 2023

Hi,

On Fri, 24 Nov 2023 at 03:02, Edward Shryane via db-wg <db-wg at ripe.net> wrote:

[...]

> We can migate 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.

This seems a reasonable approach.

It would be good to move to a place where registrants can record their
actual legal name in the database and have that displayed to other
users.

Kind regards,

Leo

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 ]