[dregoth]

When I export use-case diagrams into SVG, the text placed within the ellipses representing use cases is generated in a strange, and possibly wrong way.

The text within these constructs is specified to use sans-serif font with size 0 (zero), which causes some viewers not to display the text at all, and also causing the transcoding API in Batik to fail to generate the correct shape outline for the ensuing fonts when exporting EPS. (the java "Shape" objects representing a GlyphVector's outline is composed of NaN coordinates)

Moreover, the XML tags within the referred SVG uses an inconsistent representation for the sans-serif font, sometimes writing it as "sansserif" and sometimes writing it "sans-serif". Also, if I am not mistaken, the usage of control statements like ' is only to be used in text nodes within XML but not in attribute declarations.

I believe this might be caused by the version of batik you are currently using to draw these diagrams, in which case I do not know how it could be solved.

With regards for the feature request, I would like you to consider adding EPS as a possible exporting format for the diagrams. The reason for my sugestion is that the academic comunity uses LaTeX a lot to typeset articles and reports, which in turn uses EPS as the main figure format. I don't think these feature would be very hard to implement in case the GEF plug-in uses a Java2D representation for the graphical objects. In this case the pdf-transcoder API included in batik contains a PSGraphics2D implementation that could be easily used in this process.

I'm sorry for the long post

Regards,

[julien]

We have noticed this issue. It is already fixed in our Studio edition.

julien
omondo

[dregoth]

I am using Omondo Studio Edition version 1.0.0 and the problem still happens.

At first I though this could be caused by the diagrams being originally created by Omondo Enterprise, but I created a new project from scratch and the Use Case Diagrams are still exported with the font errors.