Subject:
|
Re: Raw FAQ data format (Was: Format of FAQ items)
|
Newsgroups:
|
lugnet.faq
|
Date:
|
Mon, 26 Apr 1999 16:48:49 GMT
|
Viewed:
|
4825 times
|
| |
|
|
Sproaticus:
[...]
> > - These header entries have been suggested:
> > Subject [the question]
> > Category [category (and sub-category?) name]
> > Content-Language [ISO 639 language code]
> > Topic-Level [integer, 0 is beginner/easy/simple]
> > Version: [author and ISO date]
> > Newsgroups: [comma-separated list of newsgroups
> > the question could appear in]
> > Translation: [translator, from language, latest
> > version string from the translated
> > entry]
>
> (Please keep in mind Jacob, that these are nits I'm picking. :-)
> "Newsgroups" would be more appropriately named "Location",
> indicating not just a ng but specific directories in the
> LUGNET data heirarchy.
Fine.
Location: [comma-separated list of Lugnet relative URI's]
> Also, something like "Original-Language" makes more sense
> than "Translation".
What about
Translated-From: [ISO 639 language code]
Translator: [translator, ISO date]
so
Revision: Todd Lehman, 1997-12-24
Revision: Minx Kelly, 1998-09-21
Translated-From: en
Translator: Jacob Sparre Andersen, 1999-02-21
Content-Language: da
is an article written by Todd, edited by Minx, and then
translated from English to Danish by me?
We could also reuse "Revision" for translations.
> Also, I'm leaning more towards "Revision" rather than "Version".
> BTW, what *is* the format of an ISO date?
Year (all digits)
"-"
Month (two digits)
"-"
Day (two digits)
> Plus:
> Include: [applies the headers of the included file]
Which of the header entries?
Subject, Category, Topic-Level, and Location I presume.
> > - ASCII + HTML entities are allowed in the headers.
>
> At least the ® -style chars. I don't see much need
> for more HTML in the headers.
That is what you call HTML entities.
Todd seems to want Latin-1 + HTML entities. That's fine for me.
> > - Should we use ASCII or Latin-1 for the content character
> > set?
>
> My knee-jerk reaction to the ASCII question is to just use
> the lower 128 (not counting the very lowest 32 of course :-),
You need 10 and 13 for newlines :-)
> and use some form of encoding for any other characters -- at
> least for the raw FAQ format.
Todd says he doesn't have problems with processing Latin-1.
Neither does I.
I think we should allow Latin-1, but let people restrict
_themselves_ to ASCII if they prefer that.
What's the word on numeric character references outside
Latin-1?
Play well,
Jacob
------------------------------------------------------------
-- E-mail: sparre@cats.nbi.dk --
-- Web...: <URL:http://hugin.risoe.dk/JJ_Memorial/FAQ/> --
------------------------------------------------------------
Here's the edited list of header entries:
Subject [the question]
Category [category (and sub-category?) name]
Content-Language [ISO 639 language code]
Topic-Level [integer, 0 is beginner/easy/simple]
Revision [author, ISO date]
Location [comma-separated list of Lugnet relative
URI's]
Translated-From [ISO 639 language code]
Translator [translator, ISO date]
|
|
Message has 1 Reply:
 | | 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 (...) (27 years ago, 26-Apr-99, to lugnet.faq)
|
Message is in Reply To:
| | 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 (...) (27 years ago, 24-Apr-99, to lugnet.faq)
|
82 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
