[sc-features] changed/cws calcmultiline : SYLK export handling of embedded semicolons and double quotes; program ID field content changes to CALCOOO32

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[sc-features] changed/cws calcmultiline : SYLK export handling of embedded semicolons and double quotes; program ID field content changes to CALCOOO32

eike.rathke


       Product: Spreadsheet
          Type: changed
         Title: SYLK export handling of embedded semicolons and double quotes; program ID field content changes to CALCOOO32
     Posted by: [hidden email]
      Affected: sc
         TaskId: i100205
<http://www.openoffice.org/issues/show_bug.cgi?id=100205>
Effective from: cws calcmultiline
           CWS:
<http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300/calcmultiline>
    CWS status: new


*Flags*
-------
API/ BASIC [ ]
Configuration [ ]
File format change [x]
Help/ Guide [ ]
Performance test [ ]
Translation [ ]
UI relevant [ ]


*Description*
-------------
When writing SYLK files, in string data embedded double quotes are not
escaped anymore by doubling them, semicolons are now escaped by doubling
them. Previous releases had a bug that did it vice versa, doubling
quotes but not semicolons.

In formula expressions, if the formula contained embedded semicolons,
the expression was written as a quoted string, again doubling embedded
quotes, but not semicolons. Instead, expressions now are not written as
a quoted string, but semicolons escaped by doubling them.

In the previous implementation, Calc could not correctly read data
exported by/for Excel if the data contained double quotes (data is
truncated) or semicolons (read in duplicated), nor could it produce such
files correctly.

NOTE: The program ID written changes from SCALC3 (ID;PSCALC3) to
CALCOOO32 (ID;PCALCOOO32) due to the incompatible file format. Older
releases will treat such files as alien data, not reading the formula
expressions. The result will be much the same as if a file produced by
Excel was read in. The new code is able to read both variants,
translating data from the corrupted file format.



Send feedback to [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]