Bug 120930 - Help reports a feature that is not implemented in LibreOffice Calc
Summary: Help reports a feature that is not implemented in LibreOffice Calc
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Documentation (show other bugs)
Version:
(earliest affected)
6.0.6.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-26 08:33 UTC by luca.manganelli
Modified: 2019-02-25 07:07 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description luca.manganelli 2018-10-26 08:33:14 UTC
Description:
In this page:

https://help.libreoffice.org/Common/List_of_Regular_Expressions

see at the cell containing \n

and it states:

Represents a line break that was inserted with the Shift+Enter key combination. To change a line break into a paragraph break, enter \n in the Find and Replace boxes, and then perform a search and replace.

\n in the Find text box stands for a line break that was inserted with the Shift+Enter key combination.

\n in the Replace text box stands for a paragraph break that can be entered with the Enter or Return key.

In LibreOffice Calc, doing this DOESN'T add a paregraph break, but inserts the \n instead (as visually inserted).

Actual Results:
Doesn't replace line feeds with paragraphs

Expected Results:
Must to do as in help page


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Oliver Brinzing 2018-10-27 13:09:17 UTC
- open new calc document
- enter text in cell A1:
  Hello
  (ctrl)+(enter)    (line break)
  World
- open search & replace dialog
- seach for \n  (with enabled regular expressions)
- replace with X
- result: HelloXWorld

IMHO calc has no paragraph breaks at all, so exchanging 
linefeeds with paragraphs is not possible.
Comment 2 Xisco Faulí 2018-11-12 14:46:23 UTC
Changing this to Documentation...
Comment 3 luca.manganelli 2019-02-25 07:07:17 UTC
If the documentation is updated, this bug doesn't appear anymore :-)