Bug 73259 - Ctrl + F10 doesn't show unprintable characters
Summary: Ctrl + F10 doesn't show unprintable characters
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) All
: medium trivial
Assignee: Not Assigned
Keywords: regression
Depends on:
Blocks: Paste
  Show dependency treegraph
Reported: 2014-01-03 13:47 UTC by Romulo
Modified: 2019-08-19 07:07 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

document and print screen with this issue (72.84 KB, application/gzip)
2014-01-03 13:47 UTC, Romulo
test non printable (23.39 KB, application/vnd.oasis.opendocument.text)
2017-10-01 00:47 UTC, Stéphane Aulery

Note You need to log in before you can comment on or make changes to this bug.
Description Romulo 2014-01-03 13:47:59 UTC
Created attachment 91462 [details]
document and print screen with this issue

When I copied the text from PDF file to Writer, the grammar checker shows that there is a extra space between words "análise" and "os". But, Ctrl+F10 doesn't show this character.
Comment 1 Marco Menardi 2014-01-05 15:28:43 UTC
Decompressing the test and analyzing content.xml I see "&#x0D" after "análise" and after "itens.". The last one is shown as a final space, the first one not as a double space. In any case, googling around I've found that should be the carriage return that a XML parser should recognize.
So probably is primary a clipboard parsing problem in addition of "non printable character" malfunction.
Libo debian sid kde 4.11.3
Comment 2 Joel Madero 2015-05-02 15:42:31 UTC Comment hidden (obsolete)
Comment 3 Buovjaga 2015-06-20 16:23:40 UTC
Confirmed, but ideally we need the pdf file to test copying with a newer version.

Win 7 Pro 64-bit Version:
Build ID: 3ecef8cedb215e49237a11607197edc91639bfcd
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-19_23:16:58
Locale: fi-FI (fi_FI)
Comment 4 QA Administrators 2017-03-06 15:25:49 UTC Comment hidden (obsolete)
Comment 5 Timur 2017-09-05 12:25:36 UTC
This one is less likely to be resolved without PDF and reproducible steps.
Comment 6 Stéphane Aulery 2017-10-01 00:47:48 UTC
Created attachment 136657 [details]
test non printable
Comment 7 Stéphane Aulery 2017-10-01 00:52:25 UTC
I can reproduce this bug with LO 5.4.1 on Debian testing.

I have just copied some Lorem Ipsum text in a new file and thried Ctrl + F10.

This shortcut is broken but the menu is working as expected.

I tried also with handwrited text, same thing. Don't to copy some text from a PDF.
Comment 8 QA Administrators 2018-10-02 02:54:14 UTC Comment hidden (obsolete)
Comment 9 Stéphane Aulery 2018-11-05 00:48:33 UTC
Not reproducible with :

LibreOffice 3.3.3 
OOO330m19 (Build:301)
tag libreoffice-
Comment 10 Xisco Faulí 2018-11-06 12:08:43 UTC
Ctrl + 10 works fine in

Build ID: 990761f5297ef7bff78f62e7df63d4d4a20616a6
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: threaded

@Stéphane Aulery, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
Comment 11 Timur 2019-01-10 10:06:00 UTC
I change this to Needinfo to have reproducible steps and test with fresh LO 6.1 (or even better with daily master from https://dev-builds.libreoffice.org/daily/master/Win-x86@39/current/).
Comment 12 QA Administrators 2019-07-10 02:54:26 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2019-08-19 07:07:03 UTC
Dear Romulo,

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