-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Willi,
Am Sa den 14. Jan 2017 um 16:43 schrieb Willi Mann: > in order to come closer to a fix for this issue, I propose the following > two patches: > > > 0001-Add-outputencoding-parameter.patch > > This patch allows to configure the value for the charset in the > Content-Type line in mail output. This should address Klaus Ethgen's > original concern. Well, partly. It will, in fact, let me configure it the way, that it solves my issue. However, It does not fix the issue itself as it does not ensure that the output in mail is that charset. As I mentioned before, this is exactly the issue. The mail could be easily in UTF-8. But then there has to be logic to keep sure that the mail is in that charset. Without, you could still end with logical incorrect mails that are (partly) in different charsets that is illegal for UTF-8. > Since most people use UTF-8, I left the default at UTF-8. No objection about that. But you cannot be sure that log stuff is in the same charset. > 0002-Use-pager-on-stdout-output-to-terminal.patch [...] > Let me know what you think about these patches. Patches looks good for me for fixing the bug partly. Nevertheless I would expect some use of iconv for really ensure the choosed charset. Maybe even encguess can come to use for guessing the input. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <kl...@ethgen.ch> Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -----BEGIN PGP SIGNATURE----- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlh7pqYACgkQpnwKsYAZ 9qzURAwAvO09xg/6VmP4PyI4jJd5lnULPJtbCcIsxypOut7fYuZATF6RrUfe1at1 GyTKhQ2aayFK1TIzwMifkD96fj3wbCV35WZm2LBAAiGkKBFs1ZasN+Zj1JkGuYiL frFHBmO49TP5YKWWRCNGrg16mxfn6QdyIqKOpPqRJeNUhuhWE05vhecjG+MzJZ9C d25JO12IooHk3np7BzXHmLn4HtJawHoKHdob6WlnyIhg2rJG8WgE44zrNYlYrO5T IbRXuiLRTGmuxuNfPqEuwLohkFbP/tPGhpgeUPV6G26THhPy0aZBENKzPoLvwJ8/ 1/RxpIe++gr5uil9xS/0zjFYZwn+TrD3rkobuIArkpmEH17v733tP9922t1YWLTU bxRtKWg6sGQMY0QsFC+0+GATJD5FHQOHQQ+fHByU+kvLHYnKvD/gPprzNuWr3Mye QF/6zHSqSzdGTDfPyl3dYz438iSOnZemsuPBTEtzL9L+0+KuRRKUgPgV5omLt4oT BZ9YB7JA =qup2 -----END PGP SIGNATURE-----
