Created attachment 114051 [details]
Simple spreadsheet with spanned columns
If a spreadsheet is saved in Text (CSV) format and the "Fixed Column Width" option is selected, the contents of the columns as they are shown on the screen are written to the file without delimiters, i.e. suitable for posting as plain ASCII to a blog, etc.
However spanned columns are truncated at the first column in the set. The content is not allowed to flow into succeeding columns.
For example, if the spreadsheet contains this:
A1 B1 C1 D1
Foo bar this spans C2 D2
A3 B3 Foo bar this spans
You get this when saving as fixed-column-width CSV:
A1 B1 C1 D1
Foo bar thi C2 D2
A3 B3 Foo bar thi
STEPS TO REPRODUCE:
1. Load the attached test.ods
3. Select Text CSV (.csv) from the format drop-down
4. Check the "Edit filter settings" checkbox
5. Click Save
6. Check "Fixed Column Widt" in the Field options dialog, and finish
RESULTS: Spanned columns are truncated at the end of the first column in each span group
EXPECTED RESULTS: Spanned data can flow over all the cells in the span group
Reproducible with LO 126.96.36.199, Win 8.1.
But I am not sure whether this is really a bug -> I personally think this is no bug.
If a text string is longer than the fixed column width, it will be truncated at the end (see also LO online help). And if you export data as a CSV file then only the data is stored cell by cell in a text file without any formatting (e.g. merging cells is only a visual effect which would not be stored). If there are cells merged together like in this case with cell A2 / B2 then the data/text will be stored in cell A2 and cell B2 will be empty.
Because the text in the merged cell A2 / B2 is too long for cell A2 with the fixed column width the end of the text is truncated.
Therefore, I personally would say this is no bug.
I can reproduce with LO Version: 188.8.131.52.0+
Build ID: 3e3f0f5c3051ea982f8f753e0f3e51441e8f9496
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-4, Time: 2015-02-22_10:24:01
I agree with Andy, this is not a bug. But I see bug when I unmerge A2:B2 and C3:D3, and resize columns. Then export with fixed width doesn't export text after ":", but it's another issue.
(In reply to A (Andy) from comment #1)
> Reproducible with LO 184.108.40.206, Win 8.1.
> But I am not sure whether this is really a bug -> I personally think this is
> no bug...
It seems to me like this is a limitation of the particular export format. I think this should be *documented* as such, perhaps with a warning about spanned cells loosing data when CSV export is attempted with the fixed-col-width option enabled.
Status -> NEW
Moggi: If you think this is just a Documentation issue, feel free to change the component. Thanks!
(In reply to raal from comment #2)
> ...But I see bug when I unmerge A2:B2 and
> C3:D3, and resize columns. Then export with fixed width doesn't export text
> after ":", but it's another issue.
Raal: Please file that as a separate issue, and link to this bug. Danke :-)
** 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
(5.1.5 or 5.2.1 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)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
(In reply to Robinson Tryon (qubit) from comment #3)
> It seems to me like this is a limitation of the particular export format. I
> think this should be *documented* as such, perhaps with a warning about
> spanned cells loosing data when CSV export is attempted with the
> fixed-col-width option enabled.
> Status -> NEW
But, as already explained, Help says this at https://help.libreoffice.org/Common/Export_text_files.
So, while I reproduce this with 6.4+, this is NotABug but expected and documented behavior.