Re: 4.1 manual suggestion(s)
- Posted by andi49 Mar 03, 2014
- 2107 views
_tom said...
useless_ said...
Could some effort be put into not breaking examples across pages? The bottom of page 35, for instance, and bottom of page 44. Page 48, etc etc.
useless
- So far I have not discovered a simple way of creating PDF documentation.
While 4.1 is in BETA it is too much work to manually edit the PDF to make it look nice.
- Searching a PDF is also limited.
Adobe software is better at searching than generic PDF readers but still not ideal. I tested an idea where certain important words would have a typographic gimic attached to them. For example the first time the word "atom" is defined it could be typed as: "an atom... is a single value." Then searching for atom.. would lead directly to the definition, while searching atom would reveal all instances. Typing gimics into the documentation is not considered to be "good style."
(So, not much progress on one of your previous observations.)
- Searching a PDF will always be slow.
- The best hope seems to be improving the HTML documentation.
_tom
Hallo
miktex http://miktex.org/ seems to work out of the box with Windows, it has a nice installer and every additional package will be downloaded automaticly.
Also it is a big download (160Mb+), i was able to built the pdf docs at the first attempt (i did not test every link so...)
Andreas
