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 568919 - Creates invalid gnumeric xml
Creates invalid gnumeric xml
Status: RESOLVED DUPLICATE of bug 339335
Product: libgsf
Classification: Core
Component: General
1.14.x
Other All
: Normal critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-01-23 21:12 UTC by sum1
Modified: 2009-02-04 20:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
xls file (946.50 KB, application/vnd.ms-excel)
2009-01-23 21:14 UTC, sum1
Details

Description sum1 2009-01-23 21:12:46 UTC
Version: r17084
OS: Ubuntu Intrepid

The upcoming xls file is from http://bugs.kde.org/show_bug.cgi?id=115721.


Steps to reproduce:
- ssconvert attachment.xls foo.gnumeric
- Attempt to open the new file


Output of 'xmllint --valid':

2443: parser error : xmlParseCharRef: invalid xmlChar value 25
ipts/detalii.php?cat=sisteme_nec&id=sisteme_nec_powermate_vl6" tip="奈
Comment 1 sum1 2009-01-23 21:14:06 UTC
Created attachment 127127 [details]
xls file
Comment 2 Morten Welinder 2009-01-23 21:48:08 UTC
gsf_xml_out_add_cstr will create invalid xml with id in non-NULL.

		} else if (*cur < 0x20 && id != NULL) {
			guint8 buf[8];
			sprintf (buf, "&#%d;", *cur);

			if (cur != start)
				gsf_output_write (xout->output, cur-start, start);
			start = ++cur;

			gsf_output_write (xout->output, strlen (buf), buf);

This probably will have to be restricted to \r, \n, and \t.  Maybe \f.
Comment 3 Morten Welinder 2009-01-23 21:52:21 UTC
Note: the "solution" will be to drop such characters on the floor.  There is
really nothing we can do at this point.

And xml 1.1 isn't likely to happen.

http://norman.walsh.name/2004/09/30/xml11
Comment 4 Morten Welinder 2009-02-04 20:43:20 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.

Linking to bug 339335 for reference.
Comment 5 Morten Welinder 2009-02-04 20:43:53 UTC

*** This bug has been marked as a duplicate of 339335 ***