[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: providing a libidn compatibility API
From: |
Nikos Mavrogiannopoulos |
Subject: |
Re: providing a libidn compatibility API |
Date: |
Fri, 10 Feb 2017 08:32:00 +0100 |
On Tue, Feb 7, 2017 at 9:56 PM, Tim Rühsen <address@hidden> wrote:
>> Great work. The current decode branch seems very good. Do you plan to
>> add the idna_to_ascii functions as well?
>
> Just pushed the first untested code (branch 'decode').
> Needs
> - test code
> - docs (also the libidn unicode functions are still missing documentation)
What about this documentation and semantic change. That is, the flags
parameter is ignored for these functions (to make sure that libidn1
flags don't result to unintentional side-effects).
doc-sem-change.patch
Description: Text Data
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/07
- Re: providing a libidn compatibility API,
Nikos Mavrogiannopoulos <=
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/10
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/10
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/10
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/13
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/02/14
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19