-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Grapher is producing corrupt graphs #663
Comments
From glenviewjeff on October 22, 2011 10:16:43 Sorry, to add more info, this is with Guice 3.0, grapher 3.0-rc3 |
From igor.petrouk on January 23, 2012 08:27:30 The grapher causes problems. I don't think it is very usable with all that concept of dot files, which is not a common format anyway. |
From glenviewjeff on February 15, 2012 09:15:34 The following Stack Overflow answer describes what I believe to be a workaround for this bug. I'll report back if it works. http://stackoverflow.com/a/9229158/403455 |
From glenviewjeff on February 15, 2012 12:38:42 Updating: Using the workaround from the Stack Overflow site replacing all the incorrectly annotated "style=invis" with "style=solid" worked. |
From sberlin on March 25, 2013 18:46:37 (No comment was entered for this change.) Blocking: google-guice:415 |
From cgruber@google.com on May 16, 2013 11:42:49 Should be fixed now in trunk. Verification from without would be appreciated. Status: Fixed |
From glenviewjeff on October 22, 2011 13:15:56
My graphs look terrible (there are lines without parent connections.) I assume it's related to these multiple "unknown tag" errors with even simple projects when running dot -Tpng test.dot >test.png:
Error - pango_parse_markup: Unknown tag 'java.lang.Object' on line 1 char 196
It looks as if dot is parsing the < > as literal less than/greater than symbols. For instance in the .dot file, the java.lang.Object looks like this:
...<java.lang.Object>...
Attachment: gist
test.dot
Binary attachments: test.png
Original issue: http://code.google.com/p/google-guice/issues/detail?id=663
The text was updated successfully, but these errors were encountered: