 | | Re: Progress so far, and a new header —Jeremy H. Sproat
|
| | | (...) I'm really gonna hate myself for this ('cause I'm gonna haveta go back and find the relevant links) but there ought to be one more optional and repeating header for "Reference:". The data would be a URL to a LUGNET posting, Web site, whatever (...) (25 years ago, 5-May-99, to lugnet.faq)
|
| | | |
| | | | | Re: Progress so far, and a new header —Jacob Sparre Andersen
|
| | | | | (...) Yes. Play well, Jacob ---...--- -- E-mail: sparre@cats.nbi.dk -- -- Web...: <URL:(URL) -- ---...--- (25 years ago, 6-May-99, to lugnet.faq)
|
| | | | | |
| | | | | | | Re: Progress so far, and a new header —Todd Lehman
|
| | | | | | (...) Me too. --Todd (25 years ago, 6-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Progress so far, and a new header —Jeremy H. Sproat
|
| | | | | | (...) Thanks guys. You realize, this would keep me away from my SW legos... :-P Would the "Xref:" header embedded into the LUGNET nntp messages work for a reference? e.g.: Xref: lugnet.com lugnet.faq:186 in the nntp message translates into: (...) (25 years ago, 6-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Progress so far, and a new header —Jacob Sparre Andersen
|
| | | | | | 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) -- ---...--- (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Progress so far, and a new header —Todd Lehman
|
| | | | | | (...) 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 (...) (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Progress so far, and a new header —Jeremy H. Sproat
|
| | | | | | (...) 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 (...) (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Progress so far, and a new header —Jeremy H. Sproat
|
| | | | | | | (...) The more I think about it, the more I think that this is exactly what I'm oging to do. The "Reference:" header would be a fully-formed URL, while the "X-Ref:" header would tell the parser that it needs to be resolved into a LUGNET article URL. (...) (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | | |
| | | | | | | | | Re: Progress so far, and a new header —Todd Lehman
|
| | | | | | | | (...) But don't copy the name 'X-Ref' if you copy the data -- that would be wicked confusing because what you want is a reference to a prior article, and the 'X-Ref' header of NNTP articles *isn't* a reference to a prior article but rather an ID of (...) (25 years ago, 8-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | | | (canceled) —Jeremy H. Sproat
|
| | | | | | | | | |
| | | | | | | | | | Re: Progress so far, and a new header —Jeremy H. Sproat
|
| | | | | | | | (...) I don't understand the difference -- is it just how the text is formatted, or does that number do some magic? Cheers, - jsproat (25 years ago, 10-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | | | Re: Progress so far, and a new header —Todd Lehman
|
| | | | | | | | (...) It's a semantic difference. - 'References' refers to other articles (ancestors). - 'Xref' is self-referential and refers both to itself and to any other copies of the same article if it has been crossposted. So copying the 'Xref' header (and (...) (25 years ago, 13-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | Re: Progress so far, and a new header —Todd Lehman
|
| | | | | | (...) Independent of the other issue, about representing arbitrarily URLs as Jacob suggested, yes, copying the X-Ref header char for char (anything to the right of the 'X-Ref:' part) is perfectly safe for this purpose. (...) Right now they're not -- (...) (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | FAQ header entries (Was: Progress so far, and a new header) —Jacob Sparre Andersen
|
| | | | Jeremy: (...) Good idea. Here comes the current edition of the FAQ header entries: Subject: [the question] Content-Language: [ISO 639 language code] Topic-Level: [integer, 0 is beginner/easy/simple] Revision: [author, ISO date] Location: (...) (25 years ago, 6-May-99, to lugnet.faq)
|
| | | | |
| | | | | | Re: FAQ header entries (Was: Progress so far, and a new header) —Jeremy H. Sproat
|
| | | | | (...) Thanks, Jacob. I've posted these in a semi-dedicated thread (1), and added notes on which ones are optional, and which ones may repeat. (...) Darn that Noah Webster. :-P Cheers, - jsproat 1. "Working sketch of FAQ item data format" (25 years ago, 6-May-99, to lugnet.faq)
|
| | | | | |
| | | | | | How do I format an entry in the Lugnet FAQ? —Jacob Sparre Andersen
|
| | | | Subject: How do I format an entry in the Lugnet FAQ? Content-Language: en Topic-Level: 1 Revision: Jacob Sparre Andersen, 1999-05-06 Location: /faq/ Reference: (URL) The raw file format for an entry in the Lugnet FAQ is a Usenet-like header, (...) (25 years ago, 6-May-99, to lugnet.faq)
|
| | | | |
| | | | | | Re: How do I format an entry in the Lugnet FAQ? —Jeremy H. Sproat
|
| | | | | (...) Cool -- thanks! :-, (...) Hmmm, what browsers in common use support 4.0? Specifically, do we want to rely on CSS? Do we require everyone to use the latest from Netscape and Microsoft? I suggest we go with something more widespread, such as 3.2 (...) (25 years ago, 6-May-99, to lugnet.faq)
|
| | | | | |
| | | | | | | Re: How do I format an entry in the Lugnet FAQ? —Todd Lehman
|
| | | | | | (...) Eeek -- not 4.0 -- probably not even 3.2 -- way unnecessarily complicated. IMO, no DTD, no nothing except a very restricted subset of HTML is really all that is necessary. The markup is only there at all (instead of pure plain-text) because (...) (25 years ago, 6-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: How do I format an entry in the Lugnet FAQ? —Jacob Sparre Andersen
|
| | | | | | 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) -- ---...--- (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Tags —Todd Lehman
|
| | | | | | (...) 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, - (...) (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Tags —Jeremy H. Sproat
|
| | | | | | (...) 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 (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Tags —Todd Lehman
|
| | | | | | (...) 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 (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Tags —Jeremy H. Sproat
|
| | | | | | (...) True. How about H5 or H6, then? Cheers, - jsproat (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Tags —Todd Lehman
|
| | | | | | (...) Heh heh. Well, <H4> is typically the same size as the base font, but in bold, so I don't think anything but <H3> is needed, if that even is. Alternatives to <H3>x</H3> might be <P><B>x</B></P> or [maybe] better yet <P CLASS=y><B>x</B></P>...? (...) (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | | | Re: Tags —Jeremy H. Sproat
|
| | | | | | | (...) SO we just reserve H1 and H2 for the parser? I can live with that. (...) Is the "CLASS=y" attribute part of CSS? Cheers, - jsproat (25 years ago, 7-May-99, to lugnet.faq)
|
| | | | | | | |
| | | | | | | | Re: Tags —Todd Lehman
|
| | | | | | | (...) Parser? As in document validation or transmogrification? (...) Yup, but not in a bad way as long as some sort of backward-compatible non- CSS code (such as <B></B>) were used in combination with <P></P> for section titles. That is, on old (...) (25 years ago, 9-May-99, to lugnet.faq)
|
| | | | | | | |
| | | | | | | | | Re: Tags —Jeremy H. Sproat
|
| | | | | | | | (...) Er... the slurpage stage whereupon the headers and body are transformed into HTML. Cheers, - jsproat (25 years ago, 10-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | Re: Tags —Jacob Sparre Andersen
|
| | | | | | | <MPG.119ea264f27724d...ugnet.com> Distribution: X-Newsreader: TIN [version 1.2 PL2] Todd: [...] (...) Good! Play well, Jacob ---...--- -- E-mail: sparre@cats.nbi.dk -- -- Web...: <URL:(URL) -- ---...--- (25 years ago, 11-May-99, to lugnet.faq)
|
| | | | | | | |
| | | | | | | | Re: Tags —Todd Lehman
|
| | | | | | | (...) I'm confused; why/how would <H1> or <H2> be used in the headers? --Todd (25 years ago, 12-May-99, to lugnet.faq)
|
| | | | | | | |
| | | | | | | | | Re: Tags —Jeremy H. Sproat
|
| | | | | | | | (...) Erm, headers? I was thinking more along the lines of using H1 and H2 for subject lines, categories, etc. in the final HTML. Sorry for the confusion. Cheers, - jsproat (25 years ago, 12-May-99, to lugnet.faq)
|
| | | | | | | | |
| | | | | | | | Re: Tags —Todd Lehman
|
| | | | | | (...) Ahh, cool-o. --Todd (25 years ago, 14-May-99, to lugnet.faq)
|
| | | | | | |
| | | | | | New thread for new items (Was: How do I format an entry in the Lugnet FAQ?) —Jeremy H. Sproat
|
| | | | (...) I know I'm picking on your FAQ item Jacob, I swear it's not personal! :-, You're doing a great job and really helping us out. I think that new FAQ items should be put in a new thread, however -- to make finding them easier and to physically (...) (25 years ago, 6-May-99, to lugnet.faq)
|
| | | | |
