| Summary | libidn2 support |
| Queue | gloox |
| Queue Version | SVN |
| Type | Enhancement |
| State | Canceled |
| Priority | 1. Low |
| Owners | js (at) camaya (dot) net |
| Requester | kyrios (at) skynet (dot) be |
| Created | 05/25/2017 (2270 days ago) |
| Due | 07/03/2017 (2231 days ago) |
| Updated | 06/12/2018 (1887 days ago) |
| Assigned | |
| Resolved | 06/12/2018 (1887 days ago) |
Assigned to Jakob Schröter
State ⇒ Canceled
Quoted from the libidn2 manual:
"3.5 Stringprep and libidn2
The original libidn library includes functionality for the stringprep
processing in stringprep.h. That functionality was an integral part of
an IDNA2003 implementation, but it does not apply to IDNA2008.
Furthermore, stringprep processing has been replaced by the PRECIS
framework (RFC8264).
For the reasons above, libidn2 does not implement stringprep or any
other string processing protocols unrelated to IDNA2008. Applications
requiring the stringprep processing should continue using the original
libidn, and new applications should consider using the PRECIS
framework."
gloox only uses the stringprep functions from libidn, so this rules
out the use of libidn2. I will look into alternatives and the PRECIS
framework.
State ⇒ Unconfirmed
Queue ⇒ gloox
Due ⇒ 07/03/2017
Summary ⇒ libidn2 support
Type ⇒ Enhancement
Priority ⇒ 1. Low
I saw "libidn replacement?" in the TODO file. I make to ticket to
officially request this.
Here is the reference link to Fedora which foresee to fully migrate to
libidn2 for version 27
https://fedoraproject.org/wiki/Releases/27/ChangeSet#Switch_libidn-using_applications_to_IDNA2008