 | | Re: How do I format an entry in the Lugnet FAQ?
|
| (...) 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?
|
| (...) 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?
|
| 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)
| | | | | 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 (25 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, - (...) (25 years ago, 7-May-99, to lugnet.faq)
| | | | | 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 (25 years ago, 7-May-99, to lugnet.faq)
| | | | | Re: Tags
|
| (...) True. How about H5 or H6, then? Cheers, - jsproat (25 years ago, 7-May-99, to lugnet.faq)
| | | | | Re: Tags
|
| (...) 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
|
| (...) 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
|
| (...) 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
|
| (...) 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
|
| <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
|
| (...) 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
|
| (...) 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
|
| (...) Ahh, cool-o. --Todd (25 years ago, 14-May-99, to lugnet.faq)
| |
