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 UTF8
- Previous message (by thread): [db-wg] Proposal to allow UTF8
- Next message (by thread): [db-wg] Proposal to allow UTF8
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Fri Apr 17 14:46:25 CEST 2015
Piotr, On Fri, 17 Apr 2015 12:18:04 +0200 Piotr Strzyzewski <Piotr.Strzyzewski at polsl.pl> wrote: > Proposal: > > I propose to allow UTF8 in all free text attributes of all DB objects > except in primary keys. I think it makes sense. As someone who only knows languages with Latin characters, it does make me nervous to do a lookup and get back something like: person: Микки Маус address: Волшебное Королевство phone-no: +1 234 567 8901 # curse useless mandatory fields! nic-hdl: THE-MOUSE-RIPE mnt-by: MNT-GLOBAL-COPYRIGHT-POLICE source: RIPE Because what does it even mean if you don't understand Cyrillic? (You mention this specific issue in your proposal.) But really, it's better to have correct information than to have something forced into a specific format with an imperfect approximation. We have Google Translate to try to guess what stuff means. :) Personally I think it could be used for primary keys too, but that can always be added later. Cheers, -- Shane
- Previous message (by thread): [db-wg] Proposal to allow UTF8
- Next message (by thread): [db-wg] Proposal to allow UTF8
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]