The EMC uses the Lyx document preparation system as its standard document storage format. Lyx files are kept in the docs/src subdirectory of the emc2 module in the git repository. The current set of files has been prepared with lyx-1.3.6. You can find out a lot more about lyx by browsing http://www.lyx.org and http://wiki.lyx.org.
Lyx will run on Microsoft Windows(tm), Macintosh(tm), and most distributions of Linux. It is conveniently packaged for debian users including BDI and Ubuntu.
Master lyx files can be converted to html for web presentation, to pdf for document printing and viewing or to several other formats for further editing or publishing. Lyx works with many other packages to provide bibliography handling and image conversion. Lyx comes with many styles like book, article, slideshow, letter, and scripts. Additional styles are available for plugin.
The EMC documentation is licensed under the GFDL with no cover texts and no invariant texts, and some portions are dual licensed under the GFDL and the GPL (the dual license makes it clear that those portions of the documentation may be used freely within the source code, for instance in source code comments or in user interface text). All new contributions should be dual licensed.
The documentation from the "v2_4_branch" is also automatically updated. You can view and download it: http://www.linuxcnc.org/docs/2.4/
The html directory includes not only the LyX-format (pdf) documentation for User, Developer, and Integrator manuals, but also HTML versions of the manpages.
The directory http://www.linuxcnc.org/docs/html/ and pdf's in http://www.linuxcnc.org/docs/ are symlinks to the docs for the latest release version.
Substituting "docview" for "docs" in any of the above URLs shows the documentation integrated in the linuxcnc.org website template.
The non-english translations are given a language suffix. For example, if you are translating the documentation for the original file config/ini_config.lyx, you would name your file config/ini_config_pt.lyx or config/ini_config_pt_BR.lyx. When you create alternate versions of images, they should likewise have a language suffix.
You should use only the version of lyx that is available for ubuntu 6.06 dapper drake, which is lyx version 1.3.7.
Much of the english-language documentation would benefit from review and proofreading before it is translated--if there is something you don't understand, it may not be understandable even to people whose first language is english. Please don't hesitate to ask questions, or for advice on which documents are most important to translate first. I recommend using our mailing lists (emc-developers or emc-users) or our IRC chat channels--more details about all of those are on our website
http://www.linuxcnc.org/content/view/4/8/lang,en/
To begin with, you should send updated files directly to me and I will arrange for the improvements to be in the next released version of emc. Once you've gotten more comfortable with the work, you can be given the permission to directly make changes and improvements directly.
sudo apt-get updatethen install the packages with
sudo apt-get install lyx imagemagick xsltproc dvipngOnce you have installed the necessary packages and re-run emc2's configure script with "--enable-build-documentation". Check the output of configure to make sure that the required programs are found. If configure detected everything properly, HTML and PDF documentation will be built as a part of the normal 'make' process. You can build the documentation alone with 'make docs'. If you are on a machine without a realtime system, then use "--enable-simulator".
Building ../docs/src[/Master User]?.pdf make: *** [../docs/src[/Master User]?.pdf] Error 1To make LyX more verbose, you can add the "-dbg=all" flag in docs/src/Submakefile?:
- @$(LYX) --export pdf2 $< + @$(LYX) -dbg=all --export pdf2 $<This makes it painfully verbose; you can experiment with other -dbg= flags (just run "lyx -dbg" at the terminal to see a list of possible flags). To review the output, you may want to "make docs 2>&1 | less" so that you can review it in a pager, or "make docs > make.log 2>&1; gedit make.log" to view it in your favorite text editor.