-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some improvements for the PDF of the manual #35495
Comments
The pdf of the Julia manual opens with a whole section on Release Notes, where each section of our release notes is a chapter in the documentation. This makes the documentation have many chapters in the beginning with just a couple of lines on each page. I suggest that we make all of release notes one chapter, if it is easy to do. I suspect this happens because in the web version, the next page from the landing page is the release notes. However, in the online docs, one probably uses the toc on the left for navigation. |
The reason is that the |
I guess showing release notes to someone that early on in even in the web version doesn't seem like a good idea. Perhaps we can include it as a link rather than as a separate page? The level of information in the NEWS file as we currently ship it is significantly more technical than the rest of the manual. |
Actually, is it possible to remove the NEWS altogether from the PDF? It is good the way it is in the web version, but doesn't add much value in the pdf. |
The TOC has way too much detail. Would be nice to present fewer levels of information in the Table of Contents. |
How does one go about fixing the latex generated that finally builds this PDF? Is it something in our Julia code, or some other tool that is harder for us to modify? |
This removes the NEWS.md link at the bottom of the first page of the manual. Given that we link to it prominently on top of the page, I feel this is ok. This will remove Section II of the PDF manual, where the release notes take 15 pages (because ofthe way markdown gets converted to PDF).
* Partial fix for #35495 This removes the NEWS.md link at the bottom of the first page of the manual. Given that we link to it prominently on top of the page, I feel this is ok. This will remove Section II of the PDF manual, where the release notes take 15 pages (because ofthe way markdown gets converted to PDF). * Better layout for the generated PDF
* Partial fix for #35495 This removes the NEWS.md link at the bottom of the first page of the manual. Given that we link to it prominently on top of the page, I feel this is ok. This will remove Section II of the PDF manual, where the release notes take 15 pages (because ofthe way markdown gets converted to PDF). * Better layout for the generated PDF (cherry picked from commit 43fd66c)
* Partial fix for JuliaLang#35495 This removes the NEWS.md link at the bottom of the first page of the manual. Given that we link to it prominently on top of the page, I feel this is ok. This will remove Section II of the PDF manual, where the release notes take 15 pages (because ofthe way markdown gets converted to PDF). * Better layout for the generated PDF
How about only show "Chapter" title + compact spacing? TOC-baseline (14p) v.s. inc spacing for chapter numbers (3p) patch3: en-toc-patch only show "chapter" + use compact TOC spacing inc spacing for chapter numbers ref: The memoir class doc: memman.pdf We only need to override |
Yes let's do it. |
I've designed a cover page based on julia's homepage. patch: play with itThe tex code in my repo is self-contained, you don't need to clone julia's repo to compile PDF documents. |
@inkydragon May I request you to submit a PR? This would all be great to have. |
Of course, I had the pleasure of designing the cover for julia's document. My plan is: After #43698 is merged or I get some feedback, I'll open a new pr. The main problem: finding a suitable way to customize the Documenter style. |
Also cc @fredrikekre |
Good News and Bad News
New todo list: Serious issues affecting reading
Optional improvements
|
I think we can remove the release notes from the manual altogether, and instead just link to them. |
With the improvements discussed in #43698 (comment), all the relevant items have been taken care of. I feel comfortable closing this. A big shoutout to @inkydragon for making most of this happen. |
The only nice to have thing is to see if the Julia logo can be included on the cover page. The proposed design above would be great if we can check it into the |
Thanks @inkydragon for seeing this through across multiple PRs! |
Nice to have:
Edit: I updated the title of this issue to cover various issues in the PDF of the manual.
Basically have to go 50 pages to get to the "Getting started" part of the manual, which is chapter 14.
The text was updated successfully, but these errors were encountered: