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 628762 - chart with two identical image filled styles exports the image twice
chart with two identical image filled styles exports the image twice
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export OOo / OASIS
git master
Other Linux
: Urgent normal
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2010-09-04 11:20 UTC by Jean Bréfort
Modified: 2010-09-04 22:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Simple sample file (95.69 KB, application/x-gnumeric)
2010-09-04 11:20 UTC, Jean Bréfort
Details

Description Jean Bréfort 2010-09-04 11:20:04 UTC
Created attachment 169477 [details]
Simple sample file

Exporting attached sample to ODF gives a file whihc lacks the graph when reopening. Messages in the console are:

(gnumeric:26634): XML-CRITICAL **: Input is not proper UTF-8, indicate encoding !
Bytes: 0xE1 0xAA 0x22 0x20


** (gnumeric:26634): WARNING **: Document likely damaged.
Comment 1 Morten Welinder 2010-09-04 15:33:43 UTC
During ssconvert from fill.gnumeric to fff.ods I see:

** (/home/welinder/gnome/gnumeric/src/.libs/ssconvert:10529): WARNING **: Unknown char 0x10 in string

** (/home/welinder/gnome/gnumeric/src/.libs/ssconvert:10529): WARNING **: Unknown char 0x06 in string

** (/home/welinder/gnome/gnumeric/src/.libs/ssconvert:10529): WARNING **: Unknown char 0x04 in string
Comment 2 Andreas J. Guelzow 2010-09-04 15:56:46 UTC
I see what is going on. I messed something up here and elsewhere.
Comment 3 Andreas J. Guelzow 2010-09-04 16:10:15 UTC
I fixed this issue but we are now exporting multiple copies of images, gradients, patterns,... So that still needs to be fixed.
Comment 4 Andreas J. Guelzow 2010-09-04 22:43:07 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.