1. 4.1 manual suggestion(s)

  • Posted by useless_ Feb 27, 2014
  • 2380 views

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

new topic     » topic index » view message » categorize

2. Re: 4.1 manual suggestion(s)

  • Posted by _tom (admin) Feb 27, 2014
  • 2330 views
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

new topic     » goto parent     » topic index » view message » categorize

3. Re: 4.1 manual suggestion(s)

  • Posted by mattlewis (admin) Feb 27, 2014
  • 2353 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.

It's not that difficult once you do the multi-gigabyte download of all the texlive stuff.

I'm far from an expert on tex, but it seems like there must be something to tell it to try to keep a particular section on one page. Does anyone know?

Matt

new topic     » goto parent     » topic index » view message » categorize

4. Re: 4.1 manual suggestion(s)

  • Posted by SDPringle Mar 01, 2014
  • 2206 views
mattlewis said...

I'm far from an expert on tex, but it seems like there must be something to tell it to try to keep a particular section on one page. Does anyone know?

Matt

\nobreak in "vertical mode". Whatever that means.

new topic     » goto parent     » topic index » view message » categorize

5. Re: 4.1 manual suggestion(s)

  • Posted by SDPringle Mar 01, 2014
  • 2239 views
mattlewis said...

I'm far from an expert on tex, but it seems like there must be something to tell it to try to keep a particular section on one page. Does anyone know?

Matt

Look up \nobreak

SDPringle

new topic     » goto parent     » topic index » view message » categorize

6. Re: 4.1 manual suggestion(s)

  • Posted by SDPringle Mar 02, 2014
  • 2163 views

I just found out there is also \nopagebreak. You can use \nopagebreak4 to make it a suggestion rather than a mandatory action. If an example should be longer than a complete page, the document would have to have a page break in it. If we forbid it, perhaps we will get some kind of horrible result.

For myself, PDF virtually means : print document format. It is for printing and only a nuisance format when reading things on screen.

It would be nice to have a fast way to get o the top of the HTML document while browsing. Sometimes I want to do another search after seeking another.

I wish the libraries for other languages and libraries could be searched for as elegantly as we can using the search feature in the local HTML files. Normally the local docs do not have a search engine, so you have to make a request out to the Internet in some search engine. Ridiculous!

SDPringle

new topic     » goto parent     » topic index » view message » categorize

7. Re: 4.1 manual suggestion(s)

  • Posted by andi49 Mar 03, 2014
  • 2108 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

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu