 | | Re: Format of FAQ items
|
|
(...) You've convinced me otherwise now. Mea culpa. :-, (...) I think it would take in the whole sub-FAQ. This is (currently) my strategy for giving localized names to the different categories. Someone looking for starter questions could probably (...) (26 years ago, 23-Apr-99, to lugnet.faq)
|
| |
| | Re: Format of FAQ items
|
|
(...) What about an outline format? I made a cool little utility that displays, in outline format, any sub-tree of the global ng tree...so from any category sub-homepage you can see what's there beneath it -- especially handy for things like loc (...) (26 years ago, 24-Apr-99, to lugnet.faq)
|
| |
| | Raw FAQ data format (Was: Format of FAQ items)
|
|
Todd Lehman (lehman@javanet.com) and Sproaticus (jsproat@geocities.com) writes lots of stuff: Guys! It sounds like you are mixing the raw data format and the presentation format. I'll try to stick to the raw data format here, and list the ideas I (...) (26 years ago, 24-Apr-99, to lugnet.faq)
|
| |
| | Re: Format of FAQ items
|
|
(...) You mean like a master Table of Contents? Sure, okay. Question" How cautious do we want to get about creeping featuritis? :-, (...) Yep. (...) Oh, yeah. Integers are better for an enumerated value. (...) If you want to write the code for it, (...) (26 years ago, 24-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) Sounds mostly good. Catch my exceptions down below. (...) Or some other tool; but I agree, a well-defined subset of HTML can and should be used. (...) (Please keep in mind Jacob, that these are nits I'm picking. :-) "Newsgroups" would be more (...) (26 years ago, 24-Apr-99, to lugnet.faq)
|
| |
| | Re: Format of FAQ items
|
|
(...) Yes & no. 'Yes' in that a master TOC would/could appear. But 'no' in that the master TOC would just be a special case of a general-purpose sub- hierarchy TOC, which just happens to start at the top. I built one of these just for fun a couple (...) (26 years ago, 25-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) I'd like to see Latin-1 as the raw data format, with conversions to the presentation formats of: (a) HTML for webpages and (b) Latin-1/ASCII for text documents (i.e. news postings). (...) Is this a choice between (a) 7-bit ASCII with HTML (...) (26 years ago, 25-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) Oh man, I'm HOT on "lynx -dump -force_html"!! It doesn't do an absolutely perfect perfect job, but it comes *so* close, and I'll bet it can get even closer by specifying a custom config file on the command line. (...) Agreed -- only &xxx; (...) (26 years ago, 25-Apr-99, to lugnet.faq)
|
| |
| | Re: Format of FAQ items
|
|
(...) Sure -- suppose you have a directory full of FAQ items, some of which have pretty much the same headers. e.g. Locations: /x/y/,/x/z/,/x/,/ Content-Language: qw Translated-From: er Topic-Level: 1 Instead of maintaining each of these in every (...) (26 years ago, 26-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
Sproaticus: [...] (...) Fine. Location: [comma-separated list of Lugnet relative URI's] (...) What about Translated-From: [ISO 639 language code] Translator: [translator, ISO date] so Revision: Todd Lehman, 1997-12-24 Revision: Minx Kelly, (...) (26 years ago, 26-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) Fine. (...) Yes (but the first four _are_ ASCII characters). (...) Me too. And yes. Play well, Jacob ---...--- -- E-mail: sparre@cats.nbi.dk -- -- Web...: <URL:(URL) -- ---...--- (26 years ago, 26-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) If we ban HTML _elements_ from the headers, then we don't need to escape '<' and '>'. There has never been a need to escape '"'. If we want to allow numeric character references outside Latin-1 (like '̥') we still have to escape (...) (26 years ago, 26-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) Looks good to me. (...) You mean like, Revision: Todd Lehman, 19971224, en Revision: Minx Kelly, 19980921 Revision: Jacob Sparre Andersen, 19990221, da or some such? (...) More easily read by humans, probably just as easy to parse. What would (...) (26 years ago, 26-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) Although rare, double-quote characters (") which appear inside of tags (for example inside of URLs), have to be written as " -- e.g. <IMG SRC="(URL) Double-quote characters (") appearing in normal text (outside of tags) don't have to be (...) (26 years ago, 26-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) How is the Japanese language represented in HTML? I seem to remember seeing a page a few weeks ago that seemed like it used 2-byte ShiftJIS... I'd be shocked if they used 8-byte HTML entities. Can we imagine any possible uses for characters (...) (26 years ago, 26-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
Todd: (...) It depends on the chosen encoding of the document. I would expect most people^H^H^H^H^Hrogrammers to use plain 16 bit Unicode BMP[1]. Since I am too lazy to get my computer to operate with another character encoding (than Latin-1), I (...) (26 years ago, 27-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
Sproaticus: (...) No, like: Revision: Todd Lehman, 1997-12-24 Revision: Minx Kelly, 1998-09-21 Translated-From: en -> Revision: Jacob Sparre Andersen, 1999-02-21 <- Content-Language: da (...) Can't remember. I think you append "-" Hours (two digits) (...) (26 years ago, 27-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) it sounds like a sneeze to me... "Ecu!" "Bless you" "Thanks" Steve (26 years ago, 27-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) Since header order is important, this should work pretty well. (...) Not bad either. Wouldn't changing an included file imply that the including file has also changed? (...) ^^^...^^^ Huh? (...) But then we'd have to run the thing through a (...) (26 years ago, 27-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
Sproaticus: (...) Yes, but it is not equally clear. Please forget that I mentioned it. (...) No (but it would mean that it should be reprocessed). Imagine this: "translating.da": Content-Language: da Revision: Jacob Sparre Andersen, 1999-04-28 (...) (26 years ago, 28-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
(...) Oh waitaminute. I think I see where the confusion is. I'm not suggesting that the header text from the included file be inserted into the including file. What I mean to say is that during processing of the files, when the including file (...) (26 years ago, 28-Apr-99, to lugnet.faq)
|
| |
| | Re: Raw FAQ data format (Was: Format of FAQ items)
|
|
Jeremy: (...) I didn't think so. What I tried to explain was how the processing tools would see the file _after_ the "Include" header had been processed. (...) ~~~...~~~ This is the critical part. I hadn't noticed it earlier. (...) Yes. Play well, (...) (26 years ago, 29-Apr-99, to lugnet.faq)
|
| |
| | Re: Format of FAQ items
|
|
(...) Jeremy, Here's what I was chattering about -- here's a little demo of the prototype ng-hierarchy-TOC generator that I use to help visualize the ng layout whenever a question comes up... A top-level overview, going 2 layers deep: (URL) Just the (...) (26 years ago, 30-Apr-99, to lugnet.faq)
|
| |
| | Re: Format of FAQ items
|
|
(...) Verrry nice. I have often wanted something like this for browsing Yahoo!, but it would never crystalize in my mind. If that made any sense. :-, (...) Could you give a formatting option to use a single size fixed-width font, wrapped at, say, 78 (...) (26 years ago, 30-Apr-99, to lugnet.faq)
|
