To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.publishOpen lugnet.publish in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Publishing / 4244 (-10)
  Re: // and ** vs {} and [] (was: testing in rtl...)
 
(...) If // and ** proved superior to {} and [], then going back and removing {} and [] (and of course automatically converting existing pages to // and **) would certainly be an option. (...) But it's only an issue under one obscure set of (...) (21 years ago, 30-May-03, to lugnet.publish, lugnet.admin.nntp)
 
  Re: // and ** vs {} and [] (was: testing in rtl...)
 
(...) Since you don't think most of the above are problems because they are not on word boandaries, how do you reconcile that with FTX's support for bolding, italicizing, or underlining part of a word, such as in the example in the FTX quick start (...) (21 years ago, 30-May-03, to lugnet.publish, lugnet.admin.nntp)
 
  Re: Announcing FTX for discussion groups
 
(...) I agree (smiling). If you have scroll, of course, to read the reply, then it means that someone didn't prune the quoted text like they should have. --Todd (21 years ago, 30-May-03, to lugnet.publish, FTX)
 
  Re: Announcing FTX for discussion groups
 
(...) Yes it did. BTW thanks for all the continued effort... I really like the abiltiy to format (etc...) the posts now. SteveB (21 years ago, 30-May-03, to lugnet.publish, FTX)
 
  Re: Announcing FTX for discussion groups
 
... (...) Scrolling sucks! (he says smiling) (21 years ago, 30-May-03, to lugnet.publish, FTX)
 
  Re: Announcing FTX for discussion groups
 
(...) BTW, just to double-check... It did show you a big huge yellow and red message box on the preview page explaining this, yes? --Todd (21 years ago, 30-May-03, to lugnet.publish, FTX)
 
  Re: Announcing FTX for discussion groups
 
(...) Good! That's where your replies belongs in a threaded discussion. (...) Not if you trim irrelevant portions of the reply correctly. (...) Top-posting is a fine thing for non-threaded discussions, especially where the recipient list changes (...) (21 years ago, 30-May-03, to lugnet.publish, FTX)
 
  Re: // and ** vs {} and [] (was: testing in rtl...)
 
(...) That's what I used to think too -- but I'm not so sure anymore... (...) the double slash and (2) the http: prefix. (...) I've never seen anyone write anything like that before. But in any case, it's got two leading slashes instead of one. (...) (21 years ago, 30-May-03, to lugnet.publish, lugnet.admin.nntp)
 
  Re: Announcing FTX for discussion groups
 
(...) Please note that the above chart is not an ASCII chart. ASCII character codes range from 0 to 127 and nothing else. What the chart shows is the ISO-8859-1 (Latin1) character set. But it's not even correct at that, because 128 through 159 are (...) (21 years ago, 30-May-03, to lugnet.publish, FTX)
 
  Re: Announcing FTX for discussion groups
 
Yikes! I just posted a reply and all my text was moved to the bottom of the message! Oy! Sure it makes it easy to read when the only message you read, in a thread, is the last one. But if you read the replies as the come in then you're forced to (...) (21 years ago, 30-May-03, to lugnet.publish, FTX)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR