 | | // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) The problem with that is that articles are stored in the news server in their raw original format only. When they're displayed by the web interface, and the FTX content is rendered into HTML for viewing on a web browser, it's done so (...) (22 years ago, 30-May-03, to lugnet.publish, lugnet.admin.nntp)
|
| |
| | Re: testing in rtl...
|
|
(...) [...] (...) Mozilla does this too (the *bold* and _underline_ and /italics/ convention, and the smileys). But I don't use Mozilla on Lugnet. I agree that FTX should translate {} and [] to // and ** when displaying in plain text, and I'm *not* (...) (22 years ago, 29-May-03, to lugnet.publish)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) That might help, but I think it would be better to just replace the FTX code with the URL directly. (22 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) 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 (22 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) 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: # (...) (22 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) 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 (...) (22 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Oh! Thanks for catching that, Brian. I had a typo in my regex. --Todd (22 years ago, 29-May-03, to lugnet.publish, FTX)
|
| |
| | Re: testing in rtl...
|
|
(...) I recommend it! So far it has given me no trouble, only benefits. BTW, Windows is no longer (since W98?) in the DOS world, the two have separated. On WinXP you can hardly say you have a DOS world... (...) all-time boldface Star Wars italics (...) (22 years ago, 29-May-03, to lugnet.publish)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Still needs some work in the case of when both bold and italics are used on the same text. Reference the brief description for msg# 4191 in either the main pages or as FTX'd into Tim's message </publish/?n=4207>. Brian H. Nielsen (22 years ago, 29-May-03, to lugnet.publish, FTX)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Done! --Todd (22 years ago, 29-May-03, to lugnet.publish, FTX)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Because that's where replies belong in threaded discussions? --Todd (22 years ago, 29-May-03, to lugnet.publish, FTX)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Mmm, any idea why sometimes my replies are pushed to the bottom when I want them at the top? Still, a (URL) idea. -JHK (22 years ago, 29-May-03, to lugnet.publish, FTX)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) You mean in the web posting interface? Plain text already is the default. Or at least the default default. The default reply type for a plain text message is plain text, and the default reply type for an FTX message is FTX. But the default (...) (22 years ago, 29-May-03, to lugnet.publish)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) btw, could we have a way to change the default post type to plain text, instead of it defaulting to FTX? (22 years ago, 29-May-03, to lugnet.publish)
|
| |
| | Re: testing in rtl...
|
|
(...) Hey, that looks like a pretty neat program. If I ever go back to the DOS world, I'll definitely install that on OE. (...) I'm curious what Quotefix shows you for each of the following lines...could you tell me what it shows? My *all-time* (...) (22 years ago, 28-May-03, to lugnet.publish)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Sorry about that. I think I can fix this tonight. (...) It's because of the "text/x-ftx" part of that header, yes. Although, I believe that the RFCs say that a client is supposed to assume plain text if it sees a type of "text" and a subtype (...) (22 years ago, 28-May-03, to lugnet.publish)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) 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
|
|
(...) I think we're going to lighten them a little bit. And when we get CSS going later down the road, you'll be able to assign your own colors (if you want to). (...) Well, you can still do that of course in plain-text posts. Or in FTX you could (...) (22 years ago, 28-May-03, to lugnet.publish, FTX)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Guess I'm not up on the difference between Brief and Compact. Thanks :-) -Tim (22 years ago, 28-May-03, to lugnet.publish, FTX)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) It didn't appear for me in the preview, and I didn't go back to check it afterwords until now. Now it's working. -Tim (22 years ago, 28-May-03, to lugnet.publish, FTX)
|
