Hooray wrote in Fri Jan 16, 2015 8:32 pm:- we've seen several incidents where people would even edit "the manual" (the PDF file) even though the manual is maintained in LaTex
- yes, a link to the wiki article would make sense, or some people might also start editing those PDF files (checklists)
Johan G wrote in Fri Jan 16, 2015 8:35 pm:Maybe all that information is not necessary in the footer or header on each and every page, but it should be somewhere in the document. I noted that the date already is there on the first page of the docs.
Ok. I'll add a title page to the checklists too, with a preamble stating the obvious to those users. And I'll add wiki links there.
clrCoda wrote in Fri Jan 16, 2015 8:56 pm:Ruben,
stuart wrote in Sun Jan 11, 2015 9:17 pm:As an aside, it would be worth including the source repository (generally fgaddon) for each aircraft, so a use could read the PDF and know where to download the aircraft from.
I believe that Stuart means you might consider adding a line to the resulting doc that says where the plane can be found in the flightgear world. Is it at someones hangar? The main aircraft download page? Comes with FG by default?
This one is not as easy, but I'll try to do that too.
You're very welcome. I liked to do this
On a related topic: I checked in the python script in fgdata, but now I'm thinking it'd be better to separate it from it, as I'm planning to add other files to parse other data from flightgear (rendering airport diagram's, SID's, STAR's etc.). Would it be best to create a separate repository for these scripts?
On rendering those Airport diagrams, I know there is
http://wiki.flightgear.org/Airport_Diagram_Generator, this topic
viewtopic.php?p=229897 and I know people are implementing it in Nasal using Canvas, but having it in an external script can have advantages. Just to make the parallel with the checklists: people would be able to have those things on paper or an e-reader, people will be able to download them from this central website. All this to ask: would there be interest in having those sort of diagrams, just like you would download them from Jeppesen or other non-free sources, but based on flightgear data and licensed as such and as a pdf instead of in-flightgear?
On the other hand; it would mean some duplicate work.