 | | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) Ah...no. We need to be able to solve this without using duplicate files. Plus, this action would break if the FAQ were slurped into one big file. Urg. Cheers, - jsproat (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
Jeremy: (...) If an answer is located in two places, we will also need two copies in the _processed_ version of the FAQ, not in the raw data (of cause). (...) Yes. Do you have a better solution (preferably not one that involves too much work). Play (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) Okay, I got it. From my end, I can guarantee that all FAQ items (1) have unique file names. This is the key thing, to be able to find a specific file by its name, in any subdirectory. So, to make a HREF to "#whatsitz" in file "flarn.en.html" (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) Do we really need duplicates in the output, though? Physical location in the subdirectory structure can be worked around. Also, at this point, I'm inclined to scrap the Location header (1), since I can't see any real use for it. Cheers, - (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
Jeremy: (...) [...] (...) OK. Will you take care of keeping a list of used entry names? (...) Skip the ".en.html#whatsitz". * Fixed language codes (".en") will give us unneccessary problems when translating the FAQ. * Todd will generate the (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) Already done. Actually, this is already being done, albeit indirectly. I've been giving the FAQ items longish and semi-informative filenames; e.g. "number_bricks_sf_to...c.en.faq". This significantly reduces the odds of getting a duplicate (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
Jeremy: (...) Fine. I would like to reserve these names for entries from the LDraw FAQ: who_wrote_ldraw bmp_to_dat_conversion changing_hinge_betwe..._dat-steps changing_ldraw_output_location clear_ldraw_parts ldraw_colours comments_in_dat-files (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) Okey-dokely. I'll put empty entries for the ones I don't have yet. They'll be unanswered for the time being, but this will ensure that the filenames are held. Heh, and I was working so hard to get the number of unanswered items *down*! ;-) (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) If you make the filenames themselves unique, you'll end up in the long run encoding bastardized forms of the directory names into the filenames in order to keep the namespaces clean. No way to avoid that. :-( --Todd (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
(...) An alternative is to refer to the directory and the file specifically, leaving the slurper script to figure out if it should resolve the address or not (1). The drawback to this is, is that the author who wishes to link to another items has (...) (26 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Namespace of FAQ-entry filenames
|
|
(...) Sure. Example 1: File "twitch.faq" contains the HREF ".../twitch#kneecap". The HREF is pointing to a name within the same file. The script would convert the HREF to "#kneecap". Example 2: File "scarface.faq" contains the HREF ".../boondoggle". (...) (26 years ago, 15-May-99, to lugnet.faq)
|
| |
| | Namespace of FAQ-entry filenames
|
|
(...) By "resolve the address" do you mean munging the HREF? Can you give an example? (...) Doing that is surely gonna be easier than firstly doing that and secondly looking up the associated global ID string. (...) In a very large system of ID (...) (26 years ago, 15-May-99, to lugnet.faq)
|
