Bug 337640 - [dot4zest] Issues with DOT label parsing
Summary: [dot4zest] Issues with DOT label parsing
Status: RESOLVED FIXED
Alias: None
Product: GEF
Classification: Tools
Component: GEF-Legacy Zest (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: gef-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2011-02-19 10:38 EST by satyagraha.1956 CLA
Modified: 2014-12-09 13:02 EST (History)
4 users (show)

See Also:


Attachments
Illustrates problem. (1.84 KB, text/plain)
2011-02-19 10:39 EST, satyagraha.1956 CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description satyagraha.1956 CLA 2011-02-19 10:38:23 EST
The DOT parser for label= strings does not seem to be properly handling:
1) backslash escaping
2) multiple values using | separator
3) nested values using { }

See the "project" node label value in the attached file, and view the file in ZGRViewer to see what's expected.
Comment 1 satyagraha.1956 CLA 2011-02-19 10:39:06 EST
Created attachment 189349 [details]
Illustrates problem.
Comment 2 Fabian Steeg CLA 2011-02-20 16:07:14 EST
There are actually two different issues here:

The first is escaping in quoted strings. This part is fixed with bug 337639 according to the DOT language spec (http://www.graphviz.org/doc/info/lang.html, in particular the footnote at the bottom): surrounding quotes are removed, and escaped quotes are converted to plain quotes (see TestGraphInstanceDotImport#escapedQuotes).

The second is support for the special record syntax (http://www.graphviz.org/doc/info/shapes.html#record). Supporting that involves both extending the grammar and creating custom figures (contributions welcome, see also bug 321775).
Comment 3 Alexander Nyßen CLA 2014-12-09 13:02:26 EST
Support for record-based shapes is handled in bug #454629 and support for html-like labels is addressed in bug #321775. 

As the initially reported parsing issues have been resolved, closing this as fixed.