Bug 134056 - Text to Columns malfunction
Summary: Text to Columns malfunction
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.4.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-17 03:11 UTC by Gordon Dudley Bossley
Modified: 2021-05-11 03:53 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Image of 'bug' (39.80 KB, image/png)
2020-06-17 03:11 UTC, Gordon Dudley Bossley
Details
Sample file (4.95 KB, application/zip)
2020-06-18 10:06 UTC, Gordon Dudley Bossley
Details
working well (70.47 KB, image/jpeg)
2020-06-18 10:21 UTC, BogdanB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon Dudley Bossley 2020-06-17 03:11:38 UTC
Created attachment 162087 [details]
Image of 'bug'

Text to Columnns in .xlsx spreadsheet is not functioning as I'd expect it to.

I'm trying to parse out a set of  records, using a comma separator. After selecting the cells and then selecting Data>Text to Columns I then select the comma as the separator of  choice.

The records all merge into one cell. This is one of several unexpected behaviours with this function. Image of 'bug' attached.
Comment 1 m_a_riosv 2020-06-17 21:20:59 UTC
Please attach a sample file for test.
Comment 2 Gordon Dudley Bossley 2020-06-18 02:31:06 UTC
File sent by return email. Not sure how to do it via this page.(In reply to m.a.riosv from comment #1)
> Please attach a sample file for test.

(In reply to m.a.riosv from comment #1)
> Please attach a sample file for test.
Comment 3 m_a_riosv 2020-06-18 07:39:45 UTC
(In reply to Gordon Dudley Bossley from comment #2)
> File sent by return email. Not sure how to do it via this page.(In reply to
> m.a.riosv from comment #1)
> > Please attach a sample file for test.
As you attach the screenshot. On the top of the comments.
I'm not able to reproduce your issue.
Seems the new line it's not recognized.

Please test with a clean profile Menu/Help/Restart in Safe Mode.
Comment 4 Gordon Dudley Bossley 2020-06-18 10:06:05 UTC
Created attachment 162144 [details]
Sample file

File att.
Comment 5 BogdanB 2020-06-18 10:21:16 UTC
Created attachment 162145 [details]
working well

Version: 6.4.4.2 (x64)
Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; 
Locale: ro-RO (ro_RO); UI-Language: en-US
Calc: threaded
Comment 6 m_a_riosv 2020-06-18 11:38:45 UTC
Fine for me.
Versión: 6.4.5.1 (x64)
Id. de compilación: be964ce243d03404cfeed53d0487f5d6bd49c627
Subprocs. CPU: 4; SO: Windows 10.0 Build 19608; Repres. IU: GL; VCL: win; 
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Calc: threaded
Comment 7 Buovjaga 2020-10-11 11:37:39 UTC
(In reply to m.a.riosv from comment #3)
> Please test with a clean profile Menu/Help/Restart in Safe Mode.

Gordon: you did not mention, if you tried this.

I can't reproduce the problem either

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: 54e1e5f597705a1244701c75233a2c3a68a7d844
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 9 October 2020
Comment 8 QA Administrators 2021-04-10 03:44:54 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2021-05-11 03:53:29 UTC
Dear Gordon Dudley Bossley,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp