 | | 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: 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: 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: Working sketch of FAQ item data format
|
|
(...) OK, I grok that better, yes. But why was that file referring to (or including) itself, and why were the other files including files in parent directories rather than subdirectories? For definitions? (I guess you answered this below...) (...) (...) (26 years ago, 25-Apr-99, to lugnet.faq)
|
| |
| | Re: I'll volunteer for the LEGO FAQ
|
|
(...) Tags at the beginning and end of the file? That just makes processing more difficult, not easier. More syntax = more work. Less syntax = less work. I'm looking for a model with a simple but flexible design -- where individual collections Q&A (...) (26 years ago, 25-Apr-99, to lugnet.faq)
|
