Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Yes, I know it's going to lose some information in the process. But as I said, the message shown to the user is wrong. There is no "invalid byte sequence" in the original text. It should say something like "the original text contains symbols that can't be translated into the requested encoding". Giving misleading information during an error is a bug in itself.
Besides, there should be a way to allow the user to proceed with the conversion anyway because the only other option is to remove those symbols by hand.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.