 | | 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)
|
|
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: I'll volunteer for the LEGO FAQ
|
|
Todd: (...) You're right. I hadn't reached the "one entry, one file" idea when I wrote this. Play well, Jacob ---...--- -- E-mail: sparre@cats.nbi.dk -- -- Web...: <URL:(URL) -- ---...--- (26 years ago, 26-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)
|
|
(...) 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)
|
