 | | Re: Please consider fixing FTX...
|
|
(...) snip (...) I see the full post, as I do with the link below - maybe the truncation problem is at your end? (...) FTX DOES require newlines before list elements. The problem here is that Dave chose not to use list elements. ROSCO (21 years ago, 27-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) Well, I figured that'd be quicker than doing the conversion every time. Disk space is cheap. CPU isn't as much. (...) My old code? I wrote something for work that translated html into textural tables, but can't use that... Plus, tables with (...) (21 years ago, 27-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) But that means you need to store two copies of FTX posts - one converted, and one not. Not that that's a bad thing, but it's something to think about. As for tables, we'll have to use your old code (or to write new code) that will convert the (...) (21 years ago, 27-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) I don't think I'd change FTX-- I think I'd vote for an FTX->plain text converter, and run that on any FTX posts. Then, when someone requests the post via NNTP or SMTP, that's the post they get. It would probably do things like: - remove square (...) (21 years ago, 27-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Raw post display broken
|
|
(...) Interesting. There's a few hits to it in the http log, which all come up as status 200 (OK), but strangely it looks like yours came up with a SLIGHTLY smaller byte count. Not enough to indicate the truncating that you saw, but enough to be (...) (21 years ago, 27-May-05, to lugnet.admin.suggestions)
|
