[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libidn2 tr#46 support
|
From: |
Bruno Haible |
|
Subject: |
Re: libidn2 tr#46 support |
|
Date: |
Fri, 04 Nov 2016 13:23:05 +0100 |
|
User-agent: |
KMail/4.8.5 (Linux/3.8.0-44-generic; KDE/4.8.5; x86_64; ; ) |
Nikos Mavrogiannopoulos asks:
> Something else quite related as all authors are in CC... does it make
> sense to combine libidn2 functionality with libunistring?
You mean, introduce functions similar to
https://www.gnu.org/software/libidn/libidn2/reference/libidn2-idn2.html
into libunistring?
libunistring is for applications that want to do Unicode text processing.
libidn2 is for applications that want to connect to web sites.
The recipe for success for GNU libraries is: "Do one thing, and do it right."
There are various other standards that make use of Unicode (such as:
XML, JSON [RFC 7159], RFC 7564, RFC 7700, RFC 7940), and their number will
be growing over time. I don't believe these facilities all belong in a
single library, libunistring.
Bruno