 | | Re: Announcing FTX for discussion groups — Todd Lehman
|
| | | (...) Unless someone go totally nuts with crazy table stuff, it should look just fine. (...) Yup! FTX was designed from day one (back in the summer of 1999) to be entirely readable as plain text. In fact, here is an example of an article I posted in (...) (22 years ago, 28-May-03, to lugnet.admin.nntp, lugnet.publish)
|
| | | |
| | | | | Re: Announcing FTX for discussion groups —William R. Ward
|
| | | | (...) Yes, but the problem is that not all FTX extensions work as well as others. For example the set and part database items, polls, etc. will not display properly on a plaintext system. For those you should convert the FTX code to an URL that (...) (21 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
| | | | |
| | | | | | Re: Announcing FTX for discussion groups — Todd Lehman
|
| | | | (...) What if lines beginning with "#" in FTX denoted comments, and the URLs of referenced resources were summarized in a comment block? In other words, if someone said [LEGOSet 6954_1] and [LDrawPart 3004:4] it would append something like this: # (...) (21 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
| | | | |
| | | | | | Re: Announcing FTX for discussion groups —Frank Filz
|
| | | | | (...) That would work decently. You would want to insert those between paragraphs (as best as you could). Of course they could also become invisible to FTX users when a NNTP user quotes the message (as I have carefully done with this message). Frank (21 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
| | | | | |
| | | | | | Re: Announcing FTX for discussion groups —William R. Ward
|
| | | | (...) That might help, but I think it would be better to just replace the FTX code with the URL directly. (21 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
| | | | |
