 | | Re: Announcing FTX for discussion groups
|
|
(...) Hmm...maybe Content-Type: text/x-ftx isn't the right thing to set. I didn't expect it to confuse NNTP clients...but now that you mention it, it makes sense. If it instead said Content-Type: text/plain what do you think would be a good header (...) (21 years ago, 28-May-03, to lugnet.admin.nntp)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) well - it'll display (btw, I got text/x-ftx to display too - mutt rocks)... but it won't "signify" anything but a plain text message. And considering that some of the FTX chars are NOT plain text, it'll be a lie. I think the best solution (...) (21 years ago, 28-May-03, to lugnet.admin.nntp)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) OK, that's fine. It's supposed to be readable as raw ASCII in newsreaders. (...) I'm not sure what you mean. Plain text doesn't imply assumptions about character sets. You can have UTF8 or US-ASCII or ISO-8859-1 all in plain text. All of the (...) (21 years ago, 28-May-03, to lugnet.admin.nntp)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) OK, I can think of four different RFC-2045 compliant workarounds: 1. Content-Type: text/plain; charset="ISO-8859-1" (FTX) 2. Content-Type: text/plain (FTX); charset="ISO-8859-1" 3. Content-Type: text/plain; charset="ISO-8859-1"; x-ftx=1.0 4. (...) (21 years ago, 29-May-03, to lugnet.admin.nntp)
|
