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 649906 - ODF import/export of string constants
ODF import/export of string constants
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export OOo / OASIS
git master
Other Linux
: Normal normal
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2011-05-10 15:57 UTC by Andreas J. Guelzow
Modified: 2011-05-10 18:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
sample file to test import of expressions with strings containing literal " (7.74 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-05-10 15:57 UTC, Andreas J. Guelzow 		  Details
proposed patch (3.19 KB, patch)
2011-05-10 17:51 UTC, Andreas J. Guelzow 		none Details | Review

Description Andreas J. Guelzow 2011-05-10 15:57:28 UTC 
Created attachment 187581 [details]
sample file to test import of expressions with strings containing literal "

According to OpenFormula:
Constant strings are surrounded by double-quote characters (QUOTATION MARK, U+0022); a literal double-quote character '"' (QUOTATION MARK, U+0022) as string content is escaped by duplicating it.

We currently do not handle literal double-quote characters correctly (on import or export).

FOr example importing the attached file (created by LibreOffice and not truly a valid ODF file but sufficient to illustrate this issue) yields a parsing error.
Comment 1 Andreas J. Guelzow 2011-05-10 16:18:45 UTC 
export has been fixed (which of course now broke roundtrip through ODF)
Comment 2 Andreas J. Guelzow 2011-05-10 17:51:03 UTC 
Created attachment 187590 [details] [review]
proposed patch

This patch requires review since it touches parser.y.
Comment 3 Andreas J. Guelzow 2011-05-10 18:09:54 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.