Bug Hunting Session
Bug 58250 - FILEOPEN UI Custom separator is corrupted in CSV dialog
Summary: FILEOPEN UI Custom separator is corrupted in CSV dialog
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.3.2 release
Hardware: Other All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: CSV-Dialog
  Show dependency treegraph
 
Reported: 2012-12-13 16:23 UTC by Urmas
Modified: 2017-07-20 21:37 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example (15 bytes, text/csv)
2012-12-13 16:23 UTC, Urmas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Urmas 2012-12-13 16:23:00 UTC
Created attachment 71451 [details]
Example

1. Open the attached CSV file with a proper delimiter;
2. Open another CSV file

Expected: the custom separator is preserved
Actual: an invalid character (a missing glyph) is displayed instead.
Comment 1 Planas 2012-12-20 18:14:08 UTC
I opened the test file using "," as the delimiter with no problems. Then as suggested I opened another csv file. The second csv file use ";" as the delimiter. Both files opened correctly in in Calc.

I import csv files into Calc regularly. The behavior I see is that Calc uses the last delimiter chosen when importing a new file. 

Note tests were conducted on 4.0.0 Beta 1
Comment 2 Urmas 2012-12-20 19:39:14 UTC
Except the file is not using , or ; as delimiters?
Comment 3 john.pratt 2012-12-21 16:31:31 UTC
Comment on attachment 71451 [details]
Example

correct mime type
Comment 4 Joel Madero 2013-01-10 16:57:48 UTC
Verified on 3.6.3.2, changing version to reflect oldest version that the bug has been seen on.

Just to clarify a little:
1. Download Example
2. Open Example and click on "Other" for Separator Options
3. Put · in the field
4. File opens fine
5. Without closing Example document, open another csv file


Expected:
Should see · in other

Observed: See a non functional ugly box showing a missing glyph

Marking as:
New (Confirmed)
Minor - Can slow down workflow but won't prevent high quality work
Low - Default for minor, don't see a reason to change this


Thanks for reporting Urmas, as always you find the tricky ones :)
Comment 5 QA Administrators 2015-04-19 03:21:07 UTC Comment hidden (obsolete)
Comment 6 Buovjaga 2015-06-15 19:12:21 UTC
(In reply to Joel Madero from comment #4)
> Verified on 3.6.3.2, changing version to reflect oldest version that the bug
> has been seen on.
> 
> Just to clarify a little:
> 1. Download Example
> 2. Open Example and click on "Other" for Separator Options
> 3. Put · in the field
> 4. File opens fine
> 5. Without closing Example document, open another csv file
> 
> 
> Expected:
> Should see · in other
> 
> Observed: See a non functional ugly box showing a missing glyph

Yep, it's da box.

Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+
Build ID: 01a189abcd9a4ca472a74b3b2c000c9338fc2c91
TinderBox: Win-x86@39, Branch:master, Time: 2015-06-14_07:46:28
Locale: fi-FI (fi_FI)
Comment 7 QA Administrators 2016-09-20 10:01:57 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 
(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)

http://downloadarchive.documentfoundation.org/libreoffice/old/

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!

Warm Regards,
QA Team

MassPing-UntouchedBug-20160920