Graphviz Issue Tracker
Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001254graphvizDotpublic2008-02-04 13:422011-04-28 04:03
ReporterPeter Sewell 
Assigned Toellson 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSx86-Linux-OS Version
Summary0001254: xfig export: special flag is not set - regressed in 2.12
Description



Bug 547, "xfig export: special flag is not set", while fixed in a version
that reports
<CD>
dot -V
dot version 2.8 (Wed Oct 4 21:40:27 UTC 2006)
</CD>



appears to to be unfixed in a version that reports



<CD>
dot -V
dot - Graphviz version 2.12 (Thu Jul 12 20:18:39 UTC 2007)
</CD>



This means that we can't generate decent LaTeX via fig2dev.
Additional Information

[ellson] What program is generating the message: "xfig export: special flag is not set" ?

Can you please send example graph (.dot) and the -Tfig outputs from 2.8 and 2.12, illustrating
the problem ?

Or can you provide more details about exactly what is missing in the -Tfig output?

I tried:
<CD>
    echo 'graph {a--b}' | dot -Tfig | fig2dev -L latex
</CD>

with graphviz-2.17 but didn't see the error you describe.

[peter]
The problem is that the "special" flag should be set for fig string elements,
eg in this line from the generated fig attached

<CD>
4 0 0 1 0 0 14.0 0.0000 4 0.0 0.0 2600 7620 iiid:\\{proc:0;progorder:0\\}\001
</CD>

the second "4" should be (I believe) a "2". This causes fig2dev -L pstex and
fig2dev -L pstex_t to treat the string as one potentially with
embedded latex commands, so (in this example) the \{ and \} would be
typeset correctly.

In 2.8 there's a "2" in that position.

[ellson] 've changed the font_flags field from 4 to 6, to turn on the "Special text" bit to support your current usage. The change is in CVS now
and should be in tomorrow's graphviz-2.17.xxx snapshot.

The font_flags field is defined as follows:
<CD>
        Bit Description

         0 Rigid text (text doesn't scale when scaling compound objects)
         1 Special text (for LaTeX)
         2 PostScript font (otherwise LaTeX font is used)
         3 Hidden text
</CD>

I'm not very comfortable with this change. Dot knows nothing about latex. It needs to know the length of the
strings to size the node shapes correctly. If the strings have embedded latex then the nodes sizes will be wrong - probably too big.

The PostScript flag is set because we use font metrics for postscript fonts. Trying to use latex fonts is likely to open another can of worms.

[peter] I see what you mean, but for us (and I suspect fairly widely) the only
reason to go via fig is so that we can have properly typeset complex
labels. We're happy to accept wrong spacing, or having to add some
manual override somewhere, to get that.

TagsNo tags attached.
AUXILLARY-FILES
DATE-FIXED
FIX-COMMENT
FORMER-ID1286
INPUT-FILEhttp://www.graphviz.org/bugs/b1286.dot [^]
OUTPUT-FILEhttp://www.graphviz.org/bugs/b1286.fig [^]
STATUS-COMMENTFixed (4 Feb 2008)
VERSION     2.12
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2011-04-28 04:03 user1 New Issue
2011-04-28 04:03 user1 Assigned To => user695


MantisBT 1.2.5[^]
Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker