| |
"Todd Lehman" <todd@lugnet.com> writes:
> In lugnet.admin.nntp, William R. Ward wrote:
> > 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 points to the referenced content.
>
> 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:
>
> # <<LEGOSet(6954_1)>>
> # http://guide.lugnet.com/set/6954_1
> # <<LDrawPart(3004:4)>>
> # http://img.lugnet.com/ld/4/3004.gif
> # <<Poll(1)>>
> # http://members.lugnet.com/polls/ballots/?n=1
>
> and that would actually be there in the actual raw message -- but would be
> hidden (commented out) when displayed by the FTX processor.
That might help, but I think it would be better to just replace the
FTX code with the URL directly.
--
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 is in Reply To:
 | | 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: # (...) (21 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
5 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
