 | | Please consider fixing FTX...
|
|
Take a look at this post: (URL) a newsreader or in raw form, hmm, you'll have to look at it in a newsreader, here's what I see when I look at the raw form: Xref: lugnet.com lugnet.off-topic.debate:26936 Newsgroups: lugnet.off-topic.debate Path: (...) (19 years ago, 27-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) Um, looks ok when I look at it? (...) I do agree that FTX needs to degrade much more nicely into plain text than it does. If we change FTX though, we'll need to think of what to do with older FTX posts. (19 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 (...) (19 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 (...) (19 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 (...) (19 years ago, 27-May-05, to lugnet.admin.suggestions)
|
| |
| | 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 (19 years ago, 27-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) Are you looking at the FTX post, or the raw form? The raw URL is: (URL) (19 years ago, 31-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) What's a list element? Dave! (19 years ago, 31-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) (URL) (FTX User Guide) has more info. * = bullet + = numbered - = numbered but in descending order Hope that helps. (19 years ago, 31-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) Ah, yes--now I see. I manually numbered my list of sage suggestions without realizing that an FTX option was available. Thanks Dave! (19 years ago, 31-May-05, to lugnet.admin.suggestions)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) Out of curiosity, when you wrote the post, how did you add in the newlines? That is, when I'm writing a post in FTX, I almost NEVER use the character for newlines. Instead, I forget. This causes problems like this: Pieces That Are Awesome: - (...) (19 years ago, 31-May-05, to lugnet.admin.suggestions, FTX)
|
| |
| | Re: Please consider fixing FTX...
|
|
(...) Like I said, I'm not playing to the cheap seats. Newsreaders Be Darned! Honestly, it never even occurred to me. I've accessed LUGNET via the web ever since I started reading it, and the foibles of the newsreader interface have been, at best, (...) (19 years ago, 1-Jun-05, to lugnet.admin.suggestions, FTX)
|
| |
| | Re: Please consider fixing FTX...
|
|
Hmm, it seems more and more folks are creating FTX posts with FTX hard new lines without a real new line. If these are being created in the web editor, could it reasonably force a real new line? It's slowly getting to the point that NNTP access to (...) (19 years ago, 6-Jun-05, to lugnet.admin.suggestions)
|
