Noctambule wrote in <bgkVRdHpIWxjB0H2RgJcIJFR9pElylgwALVQvwbBc5QXCfC1gtihB0wNGVS7KRd2tDvT0yy\ [email protected]>: |> Steffen Nurpmeso wrote in |> 20210309204740.an4hv%[email protected]: |>|Noctambule wrote in |>| <dLA6_e_vNCbvsTxWwOXzqadfhZtjeE0Adiqth5iYNtLqoB8WlEqgxoP0FTh0mwb91LKK0J4\ |>| [email protected]>: .. |> I have added (?t and) ?h type-marker support for pipe-TYPE/SUBTYPE |> yesterday, so |> |>| define showhtml { |>| \local set mime-alternative-favour-rich pipe-text/html=?h |>| \type "$@" |>|} |>| commandalias html \\call showhtml |> |> will work in v14.10. | |Hum, I have been using the previous define variant without |'pipe-text/html=?h' with 14.9.22 for a few days, it seems to display |'text/html' part using HTML-tagsoup-to-text converter. Would you mind |explain me what your 'pipe-text/html=?h' does, I am not sure I |understand it ? :)
At least no more additional `mimetype' command nor *mimetype-load-control* necessary, but simply do the above and it will work under all circumstances. ... |> the bill, so to say. That is fixed on [master] etc. |> |> Credit to both of these changes due to you, Noctambule, than you! | |Oh, thanks for credit, it's great. Glad you noticed it with my stupid |question. Very much appreciated. Should have read "thank you", of course. Somehow i produce a lot of dark spots like that in the last year or so. |You will also find an one line patch as attachment, to add proper |UTF-8 display if we use your lynx(1) example, as 'pipe-text/html'. |It prevents strange glyphs. |I'm not sure you'll accept it, but if you do, it's included with that |mail. Thanks for this. I will not :). Of course lynx is much better, w3m was once i tried it last, etc. I mean yes, we do go for *ttycharset*, but then we do not look into the tagsoup to choose the source character set, but take what the mail says it is. Some messages suck, there really is software out there which enwraps everything (line of the text version for example) in additional <div> tags, whereas others use (or used) that for paragraphs. So what to do about that. It is a very simple thing. On the other hand it just works for me, and i read some things which look terrifying on source level. I only know about one problem which is generated by a german computer magazine, they produce very strange tags like <% or something, and we do not know about this. I mean, it should be doable to look into the according parameters of the HTML/XML, collect text data and apply character set conversion. On the other hand generators which use different character set specifications for the mail message and the text in the HTML part of the mail message ... are not known to me. (I would prefer to continue living on that island, too.) |Have a nice sunday Hope you had, too, and virus-free. Thanks again, and ciao from Germany, Noctambule! --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
