[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: providing a libidn compatibility API
From: |
Tim Ruehsen |
Subject: |
Re: providing a libidn compatibility API |
Date: |
Thu, 26 Jan 2017 13:26:12 +0100 |
User-agent: |
KMail/5.2.3 (Linux/4.9.0-1-amd64; KDE/5.28.0; x86_64; ; ) |
On Thursday, January 26, 2017 12:58:05 PM CET Nikos Mavrogiannopoulos wrote:
> Hi,
> What do you think of the following merge request:
> https://gitlab.com/jas/libidn2/merge_requests/4
>
> It introduces a (very-limited) compatibility API with libidn, allowing
> several applications to switch from IDNA2003 to IDNA2008 by changing
> idna.h with idn2.h.
I just pushed my work on
idn2_to_unicode_8z4z
idn2_to_unicode_4z4z
idn2_to_unicode_44i
idn2_to_unicode_8z8z
idn2_to_unicode_8zlz
idn2_to_unicode_lzlz
to branch 'decode' (some commits are to follow)...
If you agree I would (manually) merge your changes into that branch first. So
the idna_to_unicode_8z8z() could directly map to idn2_to_unicode_8z8z() - the
arguments are the same.
Regards, Tim
signature.asc
Description: This is a digitally signed message part.
- providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/01/26
- Re: providing a libidn compatibility API,
Tim Ruehsen <=
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/01/26
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/01/27
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/01/28
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/01/28
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/01/29
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/01/27
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/01/27