Re: [Dev-C++] HTML vs. Plain text

[<f5...@qs...>]

Hello,

Why rewriting what already exists ??

Go, for example, on http://mailman.qth.net where you can subscribe to whatever
list you want. The server (the same kind of server as the one used here) has an
analyser which removes all HTML sentences.
Mesgs posted to this server and containing HTML will be forwarded to the
indended list, HTML part removed and then the readers will get the following
notice at the end of the mesg :

<<<
--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
The reason this message is shown is because the post was in HTML
or had an attachment. Attachments are not allowed.
Please post in Plain-Text only.---
>>>

If there is only HTML in the mesg, then the rx mesg is empty, the note saying :
"HTML only, pse submit once agn, plain text only".

Here is a quoting from some info mesg coming from the "Guru" (Tim Miller
<tm...@ne...> ) there :

<<<
The stripmime is implemented as a simple filter. It reads the incoming message
one line at a time, and decides if it should keep or discard that line, based on
the current body section. If there is only one section, and that section is HTML
formatted, then it will remove the HTML tags and leave behind plaintext. It also
attempts to clean up quoted-printable text and turn it back into regular
plaintext. If the message is formatted as a MIME message with a
multipart/alternative of text/plain and text/html (this is how most rich text
email is sent) then stripmime only keeps the text/plain section.

If the message doesn't contain a text/plain section (or a top-level text/html
section) then stripmime throws out everything and appends a warning message
explaining what happened. It also prints a message when it removes or alters any
section so that the user knows what is going on.
>>>

GL.

Claude

http://www.qsl.net/f5pbl
http://www.qsl.net/soc

DIG #4451 - FISTS #7722 - SOC #503 - 10-X #71724

En réponse à Hongli Lai <h....@ch...>:

> 
> If you're willing to dig into the source code, implement it, and send
> a
> patch, please go ahead and do it.
>