added SVG export of parse tree #1917
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
|
@rlfnb Can you change it so the whitespace doesn't show up as changed? I can't understand the difference with all those showing. |
rlfnb
force-pushed
the
master
branch
6 times, most recently
from
77f158b
to
9e1b556
Compare
|
rebased it and resolved the whitespace issues |
|
thanks! |
|
It seems some special chars are not handled/translated? |
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.
Main driver for exporting to SVG was the ability to search in big parse trees. I wont add new dependencies to the pom.xml, but if its ok, I'll prepare the next commit for the SVG view, too.