B.1 Recommended Workaround

It has been suggested to normalize the entire input string using NFKC before passing it to IDNA ToASCII. You may use stringprep_utf8_nfkc_normalize or stringprep_ucs4_nfkc_normalize. This appears to lead to similar behaviour as IE/Firefox, which would avoid the problem, but this needs to be confirmed. Feel free to discuss the issue with us.

Alternative workarounds are being considered. Eventually Libidn may implement a new flag to the idna_* functions that implements a recommended way to work around this problem.

This document was generated on February 1, 2012 using texi2html 5.0.