On Mon, Oct 31, 2016 at 7:46 PM, Martin Karlgren <ma...@roxen.com> wrote: >> New proposal: MIME.decode_words_text_remapped is the single most >> obvious way to decode a Subject header (among others), but that's >> really not obvious from the docs. Can we somehow make that more >> discoverable? I ended up implementing my own version of that >> (tediously and buggily [1]), then wanting to fold that into core so >> other people don't. > > Copy+paste of Marcus Comstedt’s reply in LysKOM: > > "It would probably make sense to link to decode_words_text and > decode_words_tokenized from the entries for MIME.parse_headers and > MIME.Message->headers. The various specializations (including > _mapped) are then cross-linked from there.” >
Good plan. I've added some copy to those exact places. Also, have mentioned RFC 2047 alongside RFC 1522; when I did my research, it was 2047 that I found (since it's the current standard), and searching the docs for that number came up blank. (2047 is the current standard; 1522 is when these were first introduced. Like 2822 vs 822.) ChrisA
