Re: [Nmh-workers] 1.5 release and better repl/MIME handling
Ken Hornstein k...@pobox.com writes: No, and I didn’t realise it myself! I read this mailing list through gmane using gnus, so quite what happens to utf-8 is a bit of a mystery. In fact, by the time your follow-up got back to me the apostrophe had turned back into an apostrophe. (There’s also ó in my name, which means this must be happening to all my messages. I don’t put it in the From: line to avoid having that mime encoded, which some news readers [used to?] mangle) Well, if I run the replied message through mhn it automagically figures out that the charset is UTF-8 and encodes everything with quoted-printable (I assume it's getting the correct charset through my locale). So maybe all I need to do is make sure my script converts all of the text it gets into the locale character set? The current locale? Unless the locale is a Unicode one, don’t you risk mangling characters that aren’t in the locale’s charset? -- Jón Fairbairn jon.fairba...@cl.cam.ac.uk ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] 1.5 release and better repl/MIME handling
Well, if I run the replied message through mhn it automagically figures out that the charset is UTF-8 and encodes everything with quoted-printable (I assume it's getting the correct charset through my locale). So maybe all I need to do is make sure my script converts all of the text it gets into the locale character set? The current locale? Unless the locale is a Unicode one, don’t you risk mangling characters that aren’t in the locale’s charset? Yeah, probably. But I'm not sure what the right solution should be for that case. I suppose I could insert mhbuild directives labelling the text as having a particular character set, but I don't see how to tell the editor that I'm using a different character set. There's a reason I was suggesting putting this script in contrib, after all . --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] 1.5 release and better repl/MIME handling
Yeah, probably. But I'm not sure what the right solution should be for that case. As a side note ... my last message went out as quoted-printable, but I guess the mailing list software re-encoded it as base64. Go figure. --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] 1.5 release and better repl/MIME handling
Hi Ken, As a side note ... my last message went out as quoted-printable, but I guess the mailing list software re-encoded it as base64. Go figure. Yes, I think it does that. Bit annoying. Would be nice if it picked the one that shipped the least bytes. Cheers, Ralph. ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] 1.5 release and better repl/MIME handling
Yes, I think it does that. Bit annoying. Would be nice if it picked the one that shipped the least bytes. Bytes schmytes, pick the one that's maximally human readable. ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] 1.5 release and better repl/MIME handling
Hi Jerrad, Yes, I think it does that. Bit annoying. Would be nice if it picked the one that shipped the least bytes. Bytes schmytes, pick the one that's maximally human readable. That's probably the same thing? Base64 is more than 8/6ths the original, if quoted printable was bigger than that then there's probably so many =xx present that whatever's `plain' would be a pain to pick out? Cheers, Ralph. ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] 1.5 release and better repl/MIME handling
Yes, I think it does that. Bit annoying. Would be nice if it picked the one that shipped the least bytes. Bytes schmytes, pick the one that's maximally human readable. A lot of my European friends refer to quoted-printable as quoted-unreadable. But if the choice is between q-p and base64, I'd rather have the former than the latter since the vast majority of my text is ASCII. --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] 1.5 release and better repl/MIME handling
On 4/2/2012 3:17 PM, Jerrad Pierce wrote: Yes, I think it does that. Bit annoying. Would be nice if it picked the one that shipped the least bytes. Bytes schmytes, pick the one that's maximally human readable. +1. ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
