This is the mail archive of the cygwin-developers mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 2013-11-18 05:05, Corinna Vinschen wrote:
My small fun-project is adding the AI_IDN* and NI_IDN* flags to Cygwin. The required libidn functionality exists 100% identically in kernel32.dll since Windows Vista(1) (IdnToAscii/IdnToUnicode) including the modifier flags, so it's just a matter of calling the UNICODE functions GetAddrInfoW/GetNameInfoW and calling these IdnToXXX functions, just like glibc additionally calls idna_to_ascii_lz, etc. My new getnameinfo already works with IDNs, the getaddrinfo isn't quite finished yet. However, is that really worth the effort? A portable project won't have a chance but to use libidn functions anyway. If it relies on AI_IDN/NI_IDN, it will only run on Linux. Well, and on Cygwin in future. But still, I'm not sure if we should really add this functionality. What's your stance? Yes or no?
While the lack of this feature until now hasn't required me to patch around it, all that means is that any software using this functionality does so portably (only #ifdef [AN]I_IDN). So while I can't say how many packages could benefit from this, it's certainly possible that we'll see more of it going forward. If you're that close, I say go for it.
Yaakov
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |