Support PDF output via LaTeX #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
Nice work! Thanks very much by updating the pull request. |
tpetricek
added a commit
that referenced
this pull request
Mar 28, 2013
Support PDF output via LaTeX
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I apply changes the new code base. Diffs now seem easier to read.
I copy comments from the last pull request:
Adding LatexFormatting to CodeFormat and Markdown project is relatively easy since I can follow the structure of HtmlFormatting. However,
Literate.fsxis quite messy since it assumes HTML as the only output format. Maybe it needs to be cleaned up a bit.Status:
template-color.texwith colorized source code andtemplate-math.texwith a few tokens being converted to math symbols.testfiles.