| | Re: Tags
|
|
(...) I'm a bit nervous about the <Hn> family too...but some types of answers (see the LDraw FAQ for an example) can get pretty long and do benefit from little section headers, right? --Todd (26 years ago, 7-May-99, to lugnet.faq)
|
|
| | Re: Working sketch of FAQ item data format
|
|
(...) Here's a rough sketch: File A has these headers: Flarn: Gook Cheeseball: Snorkle Include: B Include: C File B has these headers: Flarn: Gobbledegook Slack: Snafu Snarf: Quest File C has these headers: Flarn: Vorlon Snarf: Wormy Queen: Keep (...) (26 years ago, 7-May-99, to lugnet.faq)
|
|
| | Re: Tags
|
|
(...) I pretty much agree with Todd, except for the H3 -- I'm personally nervous to allow any H elements. As for attributes, I say allow them with the disclaimer that we will ignore them unless we're surprised otherwise. Cheers, - jsproat (26 years ago, 7-May-99, to lugnet.faq)
|
|
| | Re: Progress so far, and a new header
|
|
(...) I was afraid of that. :-, (...) I'm prone to just go with the simpler form, copying the X-Ref header, for several reasons: a) I don't have to enter the Web interface and search for messages to find the URL, b) The URL can be automagically (...) (26 years ago, 7-May-99, to lugnet.faq)
|
|
| | Tags
|
|
(...) That sounds like a pretty good list. Also need: - <I> and <B>, - <TT> and possibly <VAR> for things like command lines, program names, and newsgroup names, - <BR> for breaking closely-spaced runs of lines like command line sequences, - (...) (26 years ago, 7-May-99, to lugnet.faq)
|
|
| | Re: Progress so far, and a new header
|
|
(...) Ahh, good idea. The URLs for the articles are less stable than the Xref lines are. For example, when the new web-interface/hierarchy is moved into place, shortly after that will come a remapping of all the article URLs (but the old ones will (...) (26 years ago, 7-May-99, to lugnet.faq)
|
|
| | Re: How do I format an entry in the Lugnet FAQ?
|
|
Todd: (...) Sorry. You are right. Allowed elements: P A DL DT DD UL OL LI CODE STRONG EM PRE H2 (H1 is reserved for the question) More? Which attributes? Jacob ---...--- -- E-mail: sparre@cats.nbi.dk -- -- Web...: <URL:(URL) -- ---...--- (26 years ago, 7-May-99, to lugnet.faq)
|
|
| | Re: Progress so far, and a new header
|
|
Jeremy: (...) No. We should use full URL's, so we can refer to data outside Lugnet too. Play well, Jacob ---...--- -- E-mail: sparre@cats.nbi.dk -- -- Web...: <URL:(URL) -- ---...--- (26 years ago, 7-May-99, to lugnet.faq)
|
|
| | Re: Working sketch of FAQ item data format
|
|
(...) OK, yes, that's a good way of putting it. I guess I still don't understand what you mean by the include mechanism for headers. I'll have to go back and read the threads more carefully... (...) Maybe; but it wouldn't allow specialized (...) (26 years ago, 7-May-99, to lugnet.faq)
|
|
| | Re: Working sketch of FAQ item data format
|
|
(...) What you're talking about sounds more like an inherited directory filter than a header exclude. Hmmm, could this be solved by placing a token file at strategic spots in the directory structure? Cheers, - jsproat (26 years ago, 6-May-99, to lugnet.faq)
|