From the looks of things I'd have to install all the Developers Tools in order to gain access to CVS, which I would then have to learn, and this is more work than I was envisioning.
I'm going to unsubscribe from the list now. Good luck to all with the development of this project as a whole. B. On 13 Oct 2008, at 03:04, Tatsuhiro Nishioka wrote: > Hi, > > On Sat, Oct 11, 2008 at 11:34 PM, fakesexnoises > <[EMAIL PROTECTED]> wrote: >> I've actually been marking up the PDF directly in OS X's Preview.app >> using annotations. However, if you fancy sending me a link to a >> HowTo >> I'll consider installing the appropriate software so I can apply >> patches and corrections directly to the source. I've heard of LaTex >> and have a rough idea of its purpose. > > You can google LaTeX HowTo pages by "howto latex Mac OS X." > MacTeX (http://www.tug.org/mactex/) is one of all-in-one prebuilt > LaTeX packages. > You can try it but be aware - package size is approx. 1.5GB! > > Anyway, correcting typos and sentences doesn't necessarily require TeX > environment. > Probably a text editor is all you need. > > By the way, this topic reminds me of the need for updating Mac portion > of the manual. It's way too old! I'll update it hopefully by the time > of 1.9.0 release. > > >> >> B. >> >> On 11 Oct 2008, at 14:34, Martin Spott wrote: >> >>> Hi <please enter your name here>, >>> >>> fakesexnoises wrote: >>> >>>> I'm just starting in on FlightGear (it's still downloading >>>> actually), >>>> but in the past week or so I've been reading the manual and marking >>>> it >>>> up with corrections (typos, grammar, vocabulary etc.) in my spare >>>> time >>>> (during TV ads mostly). I've completed three or four chapters so >>>> far. Who should I e-mail the PDF to when I've finished/had enough? >>> >>> Welcome to The Manual, it is being compiled from LaTeX sources and >>> Encapsulated PostScript images. Here's a site to browse and download >>> the source code from: >>> >>> http://mapserver.flightgear.org/git/gitweb.pl?p=getstart;a=tree;f=source >>> >>> So, if you're familiar with editing LaTeX, we'd be happy to recieve >>> your patches. Otherwise send us (Stuart Buchanan and myself) a >>> list of >>> corrections and we're going to merge these into the source. If you'd >>> like to extend the manual, add more detail to a certain topic or >>> even >>> add an entire chapter, we'd be happy to recieve your contribution as >>> well ! >>> >>>> Also, the copy I have is dated 15th December 2007, which seems to >>>> be >>>> the latest revision - am I right? >>> >>> Sort of, yes. Unfortunately, most people here prefer to drop a quick >>> note into a random place on the Wiki instead of going through the >>> sometimes tedious labour of maintaining a proper 'book'. Therefore >>> The Manual recieves very little advertising among 'developers'. >>> But we're still alive ;-) >>> >>> Cheers, >>> Martin. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
