GNOME Bugzilla – Bug 376662
PNG(libart) makes lines too thick
Last modified: 2007-10-30 18:34:13 UTC
The export function is buggy: 1. I have to surround my drawings with white lines because otherwise export may cut off parts of the lines that are at the border of the drawing, making those lines thinner than they're supposed to be. 2. If I have many lines perfectly on top of each other, and the width seems normal in the editor, when I export the drawing these lines are actually thicker than they're supposed to be. 3. Export may cut off parts of fonts. For example I had a text that said "ABSTRACT" and the leftmost pixel column of the left A of the did not appear. 4. If I have a horizontal line A that ends to a vertical line B, export makes it seem as if line A would continue beyond line B for a very short distance, even though it doesn't. I did lock the lines to each other. I haven't tested this with line A being vertical and B being horizontal. Of course this is just cosmetic stuff, but still these bugs make the drawings look unprofessional. Idea: an invisible box would be practical, so that it couldn't be seen but you could lock text or other objects to it. I think Dia is the best free application of this sort out there. I'll be happy if you keep on developing it!
Oh, and I have been exporting to Portable Network Graphics.
Could you attach some sample diagrams that display these issues? It may be that line width isn't properly calculated into page size, but can't reproduce any of it.
I'm seeing the same problem. All diagrams that are exported to png get cropped too aggressively. There's only maybe 1 or 2 pixels missing from each side, but it makes the diagram look odd. I'm attaching a diagram + exported image that shows the problem.
Created attachment 98053 [details] Source diagram
Created attachment 98054 [details] Resulting image after export
This is possibly related to 147386 (in particular your point 3), but not necessarily the same. It's a nice example, though. Your point 4 seems to not be a problem in 0.96.1. Your point 1 is fixed in current SVN. If you can give me an example of your point 2, I can see if that's still around, otherwise I consider this a dup of 147386.
Note: I'm not the original reporter; I just added my comment here as I was seeing issue #1. #2 may or may not still exist, but I've never noticed it. Since you say #1 is fixed you might as well close the bug; the original reporter appears to have vanished.
*** This bug has been marked as a duplicate of 147386 ***