On Tue, 13 Mar 2001, Oystein Godoy wrote:
> > 2. "Save" it as .dia
> This also "seems" to work, though the first time I try to save a
> diagram into a [.dia] file the following message is printed:
>
> xmlNewGlobalNs() deprecated function reached
>
> Note, this message comes only the first time I try to save a dia file.
>
> > 3. "Export" it as a web-usable format -- and make sure you use some
> > extension other than ".dia" for that! (If you save a jpg as ".dia"
> > it will overwrite the real .dia file, and you can no longer edit the
> > file)
> This works nice. As long as I am working on the diagram I can save it
> into any of the formats listed in the export menu. The problem comes
> when I find an error in my diagram and want to modify. Yes, I am aware
> of the risk of overwriting the dia file when saving in other formats.
> However, in the example described below using the ER-demo.dia file no
> export to other formats were involved... Then I go to:
>
> 4. Using menu [File->Open] I get the following pop-up message upon
> opening my newly saved dia file:
>
> Error loading diagram /home/faog/mydiag.dia.
> Not a Dia file.
>
> The dia source distribution contains some example dia files in the
> samples directory. I have opened the ER-demo.dia file, which was no
> problem. I then saved this file from my File->Save As menu. Both the
> original and the newly saved ER-demo.dia files were gunzipped. The
> two versions of the ER-demo.dia file are attached to this message.
> The original version as ER-demo.dia and the newly saved as
> ER-demo-mycopy.dia. As far as I can tell these files are quite different
> though I would expect them to exactly the same (I did not
> export the file in other formats after I started dia).
have you tried gzip -d filename, mv filename filename.xml and then loading
it. If that works you will have narrowed down the area of the problem to
the compression/decompression. If gzip fails then that should help locate
the bug.
I don't know if dia uses its own (de)compression lib or one of the GNU
ones (is it zlib?) the problem *might* be with with the
compression/decompression as I am using dia 0.86 with the current stable
helix gnome (its pretty okay, and I hate manually sorting out dependancies
of a hundred odd rpms) and dead rat 6.2 (i didn't install the system) and
I have had no problems loading and saving both gzip'd xml and plain xml in
dia.
in summary - if you can decompress the saved file with gzip -d then the
decompression in dia is having issues (possibly a borken dependancy) if
not then the compression in is having issues (again possibly a borken
dependancy but I haven't read the makefile or code).
Any results you have from experimenting with decompressing and compressing
and opening plain xml files should be enlightening.
A.
