Bug 123168 - Trim function should also apply to non-break spaces (U+00A0)
Summary: Trim function should also apply to non-break spaces (U+00A0)
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
Hardware: All Linux (All)
: medium enhancement
Assignee: Not Assigned
Keywords: needsDevAdvice
Depends on:
Blocks: Calc-Function
  Show dependency treegraph
Reported: 2019-02-05 04:31 UTC by Elmar
Modified: 2020-04-25 03:38 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

trim function examples (82.61 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-02-05 04:38 UTC, Elmar
Text file (xed) of paste from Thunderbird (310 bytes, text/plain)
2019-02-05 04:40 UTC, Elmar

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar 2019-02-05 04:31:46 UTC
When I copy something from Thunderbird mail client or off an internet page into Calc, this does not work properly unless I first copy it to a text editor and from there to Calc

Steps to Reproduce:
1. Select text in source (e.g. Thunderbird)
2. Copy into Calc

Actual Results:
In many cases (e.g. from a web page) it will not paste using CTL+V but if I use context menu, it does.
When I use a function like Trim to remove spaces, it does not.

Expected Results:
Should find spaces.

Reproducible: Always

User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Build ID: ed707a4806a489467c6d9be7d1b787dab94b5f78
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-26_22:55:03
Locale: en-GB (en_ZA.UTF-8); UI-Language: en-US
Calc: threaded

Same problem in Version 5.4
Comment 1 Elmar 2019-02-05 04:38:30 UTC
Created attachment 148885 [details]
trim function examples

The document includes pasted screen shots and multiple examples
Comment 2 Elmar 2019-02-05 04:40:50 UTC
Created attachment 148886 [details]
Text file (xed) of paste from Thunderbird

The example shows what is pasted into text file.
When pasting from the text file into Calc, the Trim function correctly identifies spaces.
Comment 3 Usama 2019-05-19 15:23:23 UTC
Hello Elmar ,
Thank you for reporting this. I've checked the text copied from Thunderbird using the following service that view non-printable Unicode characters:

I see the text copied from Thunderbird have the Unicode Character 'NO-BREAK SPACE' (U+00A0) [1], Which is not recognized as normal space by trim. I also checked the CLEAN which it's supposed to remove non printable characters but it didn't.

Will look at it further later D.V.

1. U+00A0: http://www.fileformat.info/info/unicode/char/a0/index.htm
Comment 4 Buovjaga 2019-08-18 08:41:24 UTC
I think the issue with CLEAN function falls under bug 97706.
Not sure, if this report should be closed as wontfix in favour of bug 97706
Comment 5 Xisco Faulí 2019-09-26 10:46:41 UTC
(In reply to Buovjaga from comment #4)
> I think the issue with CLEAN function falls under bug 97706.
> Not sure, if this report should be closed as wontfix in favour of bug 97706

Hi Elmar,
Do you agree with buovjaga's opinion ?
Comment 6 QA Administrators 2020-03-25 02:40:30 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2020-04-25 03:38:33 UTC
Dear Elmar,

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