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 / 4255
4254  |  4256
Subject: 
Re: // and ** vs {} and [] (was: testing in rtl...)
Newsgroups: 
lugnet.publish, lugnet.admin.nntp
Date: 
Mon, 2 Jun 2003 22:52:41 GMT
Viewed: 
4590 times
  
"Todd Lehman" <todd@lugnet.com> writes:
In lugnet.publish, William R. Ward wrote:
I agree that FTX should translate {} and [] to // and ** when displaying in
plain text, and I'm *not* joking.

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 on-the-fly by a fairly complex set of Perl5 operations.  Although it
wouldn't be the hardest thing in the world to convert {} and [] to // and **
when dispatching articles by e-mail, I sure don't like the idea of firing up
Perl to convert the content on-the-fly from the news server every time an
article is fetched.  An alternative to on-the-fly converstion might be to
store two copies of articles on the server (one raw, one converted), but that
seems pretty gunky to me.

What NNTP server do you use?  I was under the impression that it was
written in Perl itself.

[...]
Let's approach the problem from a different direction:  What if FTX simply
supported // and ** directly?  I'll bet that if it did, a lot of people would
choose that over {} and [], and you'd be able to read them in Mozilla.

How about a different interpretation - // and ** (and don't forget __
for underlining) might not be interpreted the same as the {} and [] of
FTX, but would be interpreted like this:

s% (\W) (_\w.+\w_)   (\W) %$1<u>$2</u>$3%xg;
s% (\W) (\*\w.+\w\*) (\W) %$1<b>$2</b>$3%xg;
s% (\W) (/\w.+\w/)   (\W) %$1<i>$2</i>$3%xg;

Note that since the __, **, and // are inside the parens, and
therefore inside $2, they will be printed but the markup will be
added.  This way no information is lost in case of a problem.  This is
how Mozilla handles it.  This would be independent of the other FTX
commands for bold/italics.

--Bill.

--
William R Ward            bill@wards.net          http://www.wards.net/~bill/
-----------------------------------------------------------------------------
"A foolish consistency is the hobgoblin of little minds, adored by
little statesmen and philosophers and divines."        - Emerson



Message has 1 Reply:
  Re: // and ** vs {} and [] (was: testing in rtl...)
 
(...) CNews. (...) Doesn't that look a bit redundant? /italics/ and *boldface* What do underlined underlines look like? Like this?-- _N_ew _E_ngland _L_EGO _U_sers _G_roup Not sure how either any of those are an improvement. --Todd (21 years ago, 3-Jun-03, to lugnet.publish, lugnet.admin.nntp, FTX)

Message is in Reply To:
  // 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 (...) (21 years ago, 30-May-03, to lugnet.publish, lugnet.admin.nntp)

31 Messages in This Thread:









Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

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