I haven't reported it to Debian, I did not have a test system to confirm that it is present there as well (I'm quite sure it would be present, it is the same package source) (And https://www.debian.org/Bugs/Reporting for manual reporting seems quite scary...)
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to html2text in Ubuntu. https://bugs.launchpad.net/bugs/1564317 Title: Successful return code on encoding error Status in One Hundred Papercuts: New Status in html2text package in Ubuntu: Confirmed Bug description: When running html2text on a file with incorrect encoding (e.g. indicated as us-ascii, but actually UTF-8), it fails with an error message but returns a successful result code (0). Actual output: ----------------- $ html2text test.html; echo $? Input recoding failed due to invalid input sequence. Unconverted part of text follows. “Test”) </body> </html> 0 Expected output: (substitute 1 for any appropriate failure code) ---------------------- $ html2text test.html; echo $? Input recoding failed due to invalid input sequence. Unconverted part of text follows. “Test”) </body> </html> 1 This seem to have been introduced by 611-recognize-input- encoding.patch OS: Ubuntu 14.04 / Ubuntu 16.04 Package: html2text-1.3.2a-17 / html2text-1.3.2a-18 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
