After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 304693 - Embedded Images
Embedded Images
Status: RESOLVED FIXED
Product: dia
Classification: Other
Component: general
0.94
Other All
: Normal enhancement
: 0.98
Assigned To: Steffen Macke
Dia maintainers
: 387285 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-05-18 19:32 UTC by Brent Wells
Modified: 2010-08-15 20:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Brent Wells 2005-05-18 19:32:45 UTC 
Basically I am requested that the images that are placed within dia, be it
jpegs, png, bmp, etc., be embedded into the Dia document and not Linked to a
file on a hard drive or network drive.  This will allow for better sharing of
documents between users and the documents will not be displayed with "Broken
Images". 

Other information:
Comment 1 Alan Horkan 2005-05-18 19:49:47 UTC 
I thought this might be a duplicate and someone must have filed it already but
it is not.  Marking as New.  

This is more difficult/messy than it sounds (aren't they always)

At the moment the Dia file format is really only a flat text file, which is
sometimes gzipped.  

Embedding the images would require either base64 encoding them and including
them inside the text file (abiword does this, okay for small images but grossly
ineffecient)
or creating a container file like a tar or jar file to hold the other files
(openoffice uses a jar/zip container file)

I dont see why this would be win32 specific so I have moved it to the general
component.  

Marking as enhancement 

If you can provide code to help make this happen it would be very much
appreciated, otherwise it might not happen.
Comment 2 Lars Clausen 2005-05-18 19:55:17 UTC 
Putting it in as base64 would grow it by 33%, which is hardly grossly
ineffectient.  It should of course be optional.
Comment 3 Nguyen Thai Ngoc Duy 2006-01-19 14:28:52 UTC 
Why not making a tarball containing dia xml and other embedded files?
Comment 4 Brent Wells 2006-01-19 15:41:41 UTC 
The company that I work for is utilizing DIA for our process flow diagrams, and then we are uploading them to our off-site document control system.  If we would upload a tar, png, or anything other than a dia diagram file we would loose the functionality to update the flowchart from our document control system.  By including the image within the code of the diagram, this would allow us to upload the .dia file and not loose the image.  This is the issue that our facility faces.  If we where just saving the .dia files to our internal network, this would be fine but we are not.  Hopefully this helps!  Thanks!
Comment 5 Hans Breuer 2009-01-31 14:30:15 UTC 
*** Bug 387285 has been marked as a duplicate of this bug. ***