Bug 40200 - SYLK Ignores Character Limits and Encoding
Summary: SYLK Ignores Character Limits and Encoding
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Spreadsheet (show other bugs)
Version: 3.6.3.1 rc
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-18 08:05 UTC by Scott M. Sanders
Modified: 2015-01-19 10:15 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Scott M. Sanders 2011-08-18 08:05:33 UTC
The SYLK / Symbolic Link / Multiplan format has a character limit per cell of 255 characters. It is also encoded in ANSI.

LibreOffice and OpenOffice.org seem to ignore these, which is OK when used with them but not when you try to open a LibreOffice or OpenOffice.org-exported SYLK file in Excel or another SYLK app.
Comment 1 Scott M. Sanders 2011-08-18 10:04:52 UTC
My exported SYLK files from LibO and OOo seem to be encoded in Windows-1252.

Related: http://openoffice.org/bugzilla/show_bug.cgi?id=76602
Comment 2 Björn Michaelsen 2011-12-23 12:31:49 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 3 Scott M. Sanders 2011-12-30 07:46:56 UTC
This persists in 3.5.0beta2.
Comment 4 QA Administrators 2015-01-05 17:51:00 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team
Comment 5 Beluga 2015-01-19 10:15:51 UTC
Confirmed this is still the case.

Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+
Build ID: 5f6bdce0c0ac687f418821ce328f2987bf340cda
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-17_01:06:46


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.