On Tue, 2011-09-13 at 11:46 +0300, thorsten.i.r...@jyu.fi wrote: > LaTeX is not a word processor, it is a professional typesetting tool. I > don't know about fiction books, but the vast majority of science books you > can buy is done with LaTeX. If you know how to work with it (rather than > against it), the layout you can get is orders of magnitude better than > anything else.
I fully agree with what you are saying. I even would add as reference: http://en.wikipedia.org/wiki/LaTeX http://www.latex-project.org/intro.html They all fully support what you are saying. bUT did you notice that nobody is mentioning support for Web-pages, Softcopies, wikis, references, distributed-engineering, etc.? I am sorry that some people seem to believe I am against LaTex and/or a controlled release processes - I am not! I just ran into the fact, that the present manual is not as much in use as I believe it earned to be and/or it should be. So I try to find a way how to improve that! Doing so I guess we need to evaluate the aspects of all the actors in that process: 1) Writer, Poet, Engineering, Marketing, etc. Most of those surely do not want to be bothered with the final looks of their design - but surely some do (and then run into problems). 2) Publisher and "Corporate identity" They definitely will support to use LaTex 3) Maintainer One of the questions I raised but did not yet get an answer for: How can all the many developers input there updates into the existing document? And how often? (We have the GIT for the design - but descriptions for the users in real time updates?) Do we have a "publishing department" in FlightGear? (I know there is an excellent work done right now - but how is the future? And how can we reduce the workload and turn-around times for that?) 4) Users and/or customers Those surely will require very different styles of documentation: - A university-Prof studding the possibilities of FlightGear - The FAA, that should be convinced to issue some "approvals" - other engineers that cooperate within FlightGear - real pilots that want to train - grown ups - or kids that want to play (and which we maybe able to convince to start simulating in FlightGear instead of playing killing-games) And guess where my priorities are! Still I am looking for a compromise for most of those actors! Very simply said: Look at the opening question of this thread, and tell me what you would answerer! (Maybe even considering that question came from your own kid or friend or whatever!). Would you point to the existing manual for an answer? Did you, yourself read the complete manual at least once? I did not see any answers to these issues in this thread -- and that is my big concern! -- I do not care if one of the tools used will be LaTex or something else! And let me assure you: I fully understand that FlightGear is much more then a game and thus it is no Kids-Stuff - but I would like to use it to convince people to use it and grow with it. For the time being I am interested to see how my proposed Manual gets out of this process, how long that takes, and how it gets accepted by the customers (and the community). In todays environment! joe ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn about the latest advances in developing for the BlackBerry® mobile platform with sessions, labs & more. See new tools and technologies. Register for BlackBerry® DevCon today! http://p.sf.net/sfu/rim-devcon-copy1 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
