[db-wg] UTF8

Hi all,

On Wed, May 06, 2015 at 02:07:56PM +0200, Piotr Strzyzewski wrote:
> > correct name? Just for arguments sake, changing my name into Chinese
> > with Google translate changes the space to a '.'. If that is correct
> > then the current syntax check fails.
> 
> Well spotted.

The syntax check might need fixing then. The assumption that every name
consists of at least two strings seperated by a space is based on
nothing. I would consider this a bug. Who will file the issue on github?
:-)

> > Also "person:", "role:" and "org-name:" are all defined as 'lookup
> > keys'. 
> 
> This could introduce some inconveniences while using cli interface.

Why would this be an issue with UTF8? Can someone from RIPE NCC comment
on how this looks from the technical side of things?

> > There was a Labs article written some time ago on
> > UTF8 https://labs.ripe.net/Members/kranjbar/internationalisation-of-ripe-database
> 
> > This article put forward the idea of keeping all existing attributes
> > in ASCII (but really meant Latin1) and allowing additional optional
> > attributes for name and contact details in local language.

> It was back in 2010 during the RIPE61 when I propose person-idn: and
> other similar attributes. Although I understand your point of view, I
> believe that the situation has changed through years.

So you two are leaning towards allowing UTF8 in some fields, and in
other places add an optional new attribute (such as person-idn) if
people want to describe more clearly what their actual name is? 

If this is the case it would be good if you go over all
fields/attributes the database currently knows, and compile a full list
of attributes that should receive an idn-sibling or should accept UTF8
instead of whatever they currently accept.

Kind regards,

Job