[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: providing a libidn compatibility API
From: |
Tim Rühsen |
Subject: |
Re: providing a libidn compatibility API |
Date: |
Tue, 07 Feb 2017 21:56:21 +0100 |
User-agent: |
KMail/5.2.3 (Linux/4.9.0-1-amd64; KDE/5.28.0; x86_64; ; ) |
On Samstag, 28. Januar 2017 09:37:53 CET Nikos Mavrogiannopoulos wrote:
> On Fri, 2017-01-27 at 13:24 +0100, Tim Ruehsen wrote:
> > On Thursday, January 26, 2017 2:07:39 PM CET Nikos Mavrogiannopoulos
> >
> > wrote:
> > > Note that there few small changes from the version you submitted in
> > > gnutls (one which detects non-ascii chars, and another which allows
> > > XN-- as prefix).
> >
> > Hi Nikos, hi list,
> >
> > I am done with coding here (branch 'decode' on jas or rockdaboot) and
> > now
> > start reviewing/adding your changes. I'll post my comments /
> > questions step by
> > step.
>
> Which repository is considered to be the primary? Note that I noticed
> that the tip of the master in both repos has commits from an unnamed
> author:
> Author: userwithuid <address@hidden>
>
> 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)
So it's WIP, but any help is appreciated.
Tim
signature.asc
Description: This is a digitally signed message part.
- Re: providing a libidn compatibility API,
Tim Rühsen <=
- 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/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