On 16 Sep 2017, at 2:22, Martin J. Dürst wrote: > P.P.S.: Regarding the content of that RFC, I think may already know, but for the record, I'll repeat here that I think it's way outdated. I really wish the HTTP WG would take some hints from this RFC work and finally get the message that straightforward UTF-8 is the way to go (we all knew that ages ago, anyway). +1 RFC 2130 from April 1997: > This report recommends the use of ISO 10646 as the default Coded > Character Set, and UTF-8 as the default Character Encoding Scheme in > the creation of new protocols or new version of old protocols which > transmit text. These defaults do not deprecate the use of other > character sets when and where they are needed; they are simply > intended to provide guidance and a specification for > interoperability. ;-) paf
Attachment:
signature.asc
Description: OpenPGP digital signature