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] Puny code or UTF-8 (or both)?
- Previous message (by thread): [db-wg] Puny code or UTF-8 (or both)?
- Next message (by thread): [db-wg] Puny code or UTF-8 (or both)?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Mon Jul 13 14:18:38 CEST 2020
Hi Denis, > Do we therefore have support to introduce Puny code now and then consider how to move forward with UTF-8? I think this is probably the best solution. - Cynthia On Mon, Jul 13, 2020 at 2:13 PM ripedenis--- via db-wg <db-wg at ripe.net> wrote: > Colleagues > > After the recent discussion it seems their is support for the idea of > UTF-8, whilst there is also support for Puny code as an interim step. > > To implement UTF-8 in the RIPE Database requires much more detailed > discussions, including non technical aspects of the change. This is not > likely to happen quickly. > > There has been support shown to introduce Puny code as a first step > towards internationalisation of the data, which can be done quickly by the > RIPE NCC. > > Do we therefore have support to introduce Puny code now and then consider > how to move forward with UTF-8? > > cheers > denis > > co-chair DB-WG > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20200713/1c5ebd0a/attachment.html>
- Previous message (by thread): [db-wg] Puny code or UTF-8 (or both)?
- Next message (by thread): [db-wg] Puny code or UTF-8 (or both)?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]