pagedown
Our great sponsors
| pagedown | ||
|---|---|---|
| 3 | 4 | |
| 313 | 866 | |
| - | 0.3% | |
| 0.0 | 5.1 | |
| over 2 years ago | 4 months ago | |
| JavaScript | R | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
- Guide (and example code) to producing beautiful PDFs from CSS and JS
-
Beautiful PDFs from HTML
Hi dang, hope you are well. May I kindly ask why not? I spent two weeks writing the CSS / HTML / JavaScript, and did well documented code - in fact the output serves as both documentation of the code and also output from it (in my own stupid way, I was thinking I was following Donald Knuth’s Literate Programming Approach :D).
The repo (https://github.com/ashok-khanna/pdf) contains all the necessary code and is intended for others to reuse in their projects. Some of it isn’t straightforward, despite the guide looking easy - I had to figure out how CSS selectors and counters work for example, how MathJax interacted with Paged.Js.
I think the confusion comes from it being labeled as a “guide”, in fact it’s a full set of code to give the required functionality for high quality PDFs from HTML, using paged.js, the guide is just the self documentation as I figured I might as well use documentation for the sample output. Otherwise, I’d be genuinely curious on what constitutes Show HN vs normal posts?
I think the repo description and the way the output is confusing / unclear - the primary goal is very much meant to be a code base for people to reuse as I’ve noticed for many programmers, the design side can be a bit more elusive.
Separately, would it be possible to add beautiful back to the title - it’s not really about producing PDFs from html as browsers can already do that, and there are many other tools. The main aim is to have the functionality to produce very high quality typeset PDFs from HTML, which until now, I only felt PrinceXML did well and that’s a paid solution. Maybe we could say the title is “High quality PDFs from HTML using Paged.JS”? I know there has been a separate discussion on another thread on the overuse of the word beautiful in describing code - my view is that it has its place when it relates to output / UI.
Thanks for reading, and no issues otherwise (no need to reply).
pagedown
-
Bookdown PDF download option
See pagedown, you can add commands in your yaml that will automatically print a pdf when you knit.
- Rstudio/Pagedown: Paginate the HTML Output of R Markdown with CSS for Print
-
Beautiful PDFs from HTML
I use pagedown all the time.
-
Changing font family in Rmarkdown using Latex
As alternative to latex you can also use pagedown https://github.com/rstudio/pagedown
What are some alternatives?
asciidoctor-web-pdf - Convert AsciiDoc documents to PDF using web technologies
ReLaXed - Create PDF documents using web technologies
tinytex - A lightweight, cross-platform, portable, and easy-to-maintain LaTeX distribution based on TeX Live
SingleFile - Web Extension for saving a faithful copy of a complete web page in a single HTML file
bookdown-template - Template for R bookdown books
WeasyPrint - The awesome document factory
publisher - speedata Publisher - a professional database Publishing system
breezy-pdf-lite - HTML/CSS/JS in, PDF out, via Chrome
markdeep-thesis - Write your (under)graduate thesis with Markdeep and typeset it right in your browser.
MathJax - Beautiful and accessible math in all browsers