Re: Re?rdering SVt_* constants; "internal" SV type
[email protected] (Martijn Lievaart via perl5-porters) Thu, 25 Jun 2026 07:28:53 +0200
| Newsgroups | perl.perl5.porters |
|---|---|
| Message-ID | <[email protected]> |
Op 25-06-2026 om 07:06 schreef Vadim V Konovalov via perl5-porters: >>> Content-Type: text/plain; charset=US-ASCII >>> Content-Transfer-Encoding: 7bit >> That's for the content. The content-Transfer-Encoding header does not apply >> to the subject field. > Notice that "content" here does not mean content of email message which go after the subject, but "content" of entire delivery, *including* subject. > So subject was considered to be UTF8, but after that entire message have been transformed to 7bit us-ascii. > https://datatracker.ietf.org/doc/html/rfc2045 describes this in full. The short version, headers are always sent 7bit, but UTF8 in headers is encoded without any other indication, no header to say this happened,So it's shown as the encoded (ugly) version in mail clients that do not understand it and translated to UTF8 in clients that do. The content-Transfer-Encoding field applies to the body only. The fact that your mail client translates UTF8 'รถ' to a '?' indicates a problem in your client in UTF8 handling. It understands the convention but then cannot render it. HTH, M4