On 2011/02/17 03:38, Kevin Ford <f...@math.uiuc.edu> wrote: > BTW, I'm fluent in TeX; I could help with the manual. Who's in > charge?
Talk to Helmut Rohs <helmut.j.r...@web.de>, he's also in our IRC channel. Or just clone our git repository, edit the TeX sources in branch v6.0.x, and submit patches / pull requests to the developer mailing list. https://lists.sourceforge.net/lists/listinfo/xcsoar-devel http://webchat.freenode.net/?channels=xcsoar On 2011/02/17 03:41, Scott Penrose <sco...@dd.com.au> wrote: > We have a set of people working on the new manual. However the majority of > contributors were not happy working with Tex, so we have moved to sections in > Google Docs. The plan though, is just to edit the text there, we will likely > move the content generated there to another medium to generate the proper > page numbers, sections etc. Who is that "set of people"? Helmut Rohs is the only manual contributor I know so far, and he writes TeX, not Google Docs. (Big Kudos to Helmut, he's been verys diligent) > If you would like to help, just send me your google ID and I can add > you. No, please do not try to convince people from TeX to Google Docs. TeX is the primary source for our manual. People may contribute by editing text on Google Docs, which must be merged back to TeX. But since I havn't seen even one single contribution from Google Docs, I consider that experiment failed. Max ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
