 | | 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*! ;-) (...) (25 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 (...) (25 years ago, 14-May-99, to lugnet.faq)
|
| |
| | Re: Linking between FAQ items (Was: [LDraw FAQ] Who wrote LDraw?)
|
|
Todd: (...) Yes. I think Jeremy's suggestion (".../entry_file_name") is a reasonable solution for this. (...) Each question will appear as a separate file on ldraw.org (the LDraw FAQ is more than 40 kb _text_ at the moment). (...) Five in the 32 (...) (25 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 (...) (25 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 (...) (25 years ago, 14-May-99, to lugnet.faq)
|
