1.8 Bug Reports

If you think you have found a bug in Libidn, please investigate it and report it.

• Please make sure that the bug is really in Libidn, and preferably also check that it hasn’t already been fixed in the latest version.
• You have to send us a test case that makes it possible for us to reproduce the bug.
• You also have to explain what is wrong; if you get a crash, or if the results printed are not good and in that case, in what way. Make sure that the bug report includes all information you would need to fix this kind of bug for someone else.

Please make an effort to produce a self-contained report, with something definite that can be tested or debugged. Vague queries or piecemeal messages are difficult to act on and don’t help the development effort.

If your bug report is good, we will do our best to help you to get a corrected version of the software; if the bug report is poor, we won’t do anything about it (apart from asking you to send better bug reports).

If you think something in this manual is unclear, or downright incorrect, or if the language needs to be improved, please also send a note.

Send your bug report to:

‘bug-libidn@gnu.org’

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