On Wed, 2 Jul 2014, Philip Prindeville wrote:
On Jul 2, 2014, at 12:37 PM, John Hardin <jhar...@impsec.org> wrote:
On Wed, 2 Jul 2014, Philip Prindeville wrote:
Given that it’s text/plain with an implicit charset=“us-ascii” and an implicit
content-transfer-encoding of 7bit, the sequence &#x[0-9A-F]{4} doesn’t really
parse into a 16-bit character, would it? That would be a broken MUA that made such
a leap...
Nope. The content-transfer-encoding is only for the *transfer* part of the
process. Once the content reaches the MUA that content can be further parsed by
the MUA according to other encoding rules, such as these escape sequences for
Unicode characters. That's perfectly valid. How else would you send, for
example, a c-cedille in spanish text via a 7-bit-clean channel?
This is a trick question, right?
You do that with base64 or quoted-printable, which are the interoperable
standards.
Apologies, you are right. I was focused on something else this morning and
dashed off a fast - and wrong - answer.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
WSJ on the Financial Stimulus package: "...today there are 700,000
fewer jobs than [the administration] predicted we would have if we
had done nothing at all."
-----------------------------------------------------------------------
2 days until the 238th anniversary of the Declaration of Independence
