You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Markdown files are converted to $\LaTeX$ to obtain a printable PDF file. This approach was quick to setup, but has its own limitations. We don't have a fine control on how elements are displayed in the flow of text. Automatic spacing between elements is tedious while neither tables nor code blocks can break between columns or pages. Maybe $\LaTeX$ isn't flexible enough for our needs.
Maybe we should use a different intermediate language, such as EPUB? This format is used for digital books and is based on HTML and CSS. Generating EPUB files with Pandoc is already feasible. The code examples may be highlighted by a JS library. Some nice CSS3 features such as column-count would give the same feel and taste as the current approach. Bonus point, we would have the web and the print version simultaneously!
This is not a burning topic, but is something to consider if we continue to improve the cheat sheet.
The text was updated successfully, but these errors were encountered:
Currently, Markdown files are converted to$\LaTeX$ to obtain a printable PDF file. This approach was quick to setup, but has its own limitations. We don't have a fine control on how elements are displayed in the flow of text. Automatic spacing between elements is tedious while neither tables nor code blocks can break between columns or pages. Maybe $\LaTeX$ isn't flexible enough for our needs.
Maybe we should use a different intermediate language, such as EPUB? This format is used for digital books and is based on HTML and CSS. Generating EPUB files with Pandoc is already feasible. The code examples may be highlighted by a JS library. Some nice CSS3 features such as
column-count
would give the same feel and taste as the current approach. Bonus point, we would have the web and the print version simultaneously!This is not a burning topic, but is something to consider if we continue to improve the cheat sheet.
The text was updated successfully, but these errors were encountered: