 | | Re: FAQ data format possibilities
|
|
Todd, I read your post just after I put up my own. Ships in the night. :-P (...) 'Kay, I hadn't thought of that. I like it; the only real drawback I can see to this is how to phrase the category titles; e.g. translating: (...) (25 years ago, 23-Apr-99, to lugnet.faq)
|
| |
| | (canceled)
|
|
|
| |
| | FAQ data format possibilities
|
|
(...) Separate files would make it even easier to parse. Also easier for editing, maintenance, and division of labor. Plenty simple to organize the individual translations using ISO 639 suffixes too, just like webpages, because then you can 'grep' (...) (25 years ago, 23-Apr-99, to lugnet.faq)
|
| |
| | Re: FAQ data format possibilities
|
|
(...) Whoops, I forgot to list <UL>/<OL>/<LI> and <DL>/<DT>/<DD> -- gotta have those! Now this is getting into nesting... :) There are some good Perl5 modules that already exist for doing all of this (the HTML->text conversion, not the FAQing). (...) (25 years ago, 23-Apr-99, to lugnet.faq)
|
| |
| | Re: FAQ data format possibilities
|
|
(...) Please see my comment regarding an index file title.en.faq : (URL) actual name of the file is unimportant.) You could then have title.fr.faq , title.es.faq , etc. (I think I now prefer "index" over "title" in the filename.) (...) It's funny (...) (25 years ago, 23-Apr-99, to lugnet.faq)
|
| |
| | Re: FAQ data format possibilities
|
|
(...) I've got a mechanism for this for the ng names so that, for example, "sf" is displayed as "San Francisco" -- but it isn't internationalized yet. Not sure how to handle subcategory names in the FAQ for virtual subcategories that don't yet (...) (25 years ago, 23-Apr-99, to lugnet.faq)
|
| |
| | Re: FAQ data format possibilities
|
|
(...) I like index.* over title.* too. (...) The funny thing to me is the strange and unpredictable sequence that things have been unfolding in. It's not that it's got a life of its own which is not under any of our control to choose the sequencing, (...) (25 years ago, 24-Apr-99, to lugnet.faq)
|
