Bug 147481 - Writer Mail Merge does not use CR/LF as paragraph separator
Summary: Writer Mail Merge does not use CR/LF as paragraph separator
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.8.1 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Mail-Merge
  Show dependency treegraph
 
Reported: 2022-02-17 06:33 UTC by titanemdg
Modified: 2023-10-15 03:16 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 titanemdg 2022-02-17 06:33:58 UTC
Description:
Mail Merge loses CR+LF Windows and LF Unix when data source have these symbols. Writer replace these symbols by uncommon one that does not triggs paragraph separation.
The bad effect of this is for instance, application of list style does not work properly and the numbering shows only number 1 and does not go beyond. Writer sees only one paragraph.

It is a bug because if you copy paste a text from simple text editor to Writer, CR/LF is copied well and it marks paragraph separation.

Steps to Reproduce:
1.From data base source, insert multiple line separated with CR+LF Windows or LF Unix
2.Create a mail merge from the data base source
3.Check in the produced file with 'Toggle Formatting Marks' tool: CR/LF are replaced by uncommon symbol( a folded arrow) .

Actual Results:
CR+LF Windows or LF Unix are replaced by other symbol

Expected Results:
Replace CR+LF Windows or LF Unix by the right paragraph separator


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.1.8.1 (x64) / LibreOffice Community
Build ID: e1f30c802c3269a1d052614453f260e49458c82c
CPU threads: 2; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: en-US
Calc: threaded
Comment 1 Dieter 2022-03-03 18:29:52 UTC
Thank you for reporting the bug. It seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 2 titanemdg 2022-03-11 08:49:07 UTC
I set to 'Unconfirmed' because in version 7.3.1 the bug is still there.

Version: 7.3.1.3 (x64) / LibreOffice Community
Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951
CPU threads: 2; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: en-US
Calc: threaded
Comment 3 titanemdg 2022-06-27 13:27:30 UTC
(In reply to Dieter from comment #1)
> Thank you for reporting the bug. It seems you're using an old version of
> LibreOffice. Could you please try to reproduce it with the latest version of
> LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I
> have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' if the bug is still present in the latest version. Change to
> RESOLVED WORKSFORME, if the problem went away.

Hi,

The statu is still 'UNCONFIRMED'
What is the next ? Does the issues solved ?
Comment 4 Dieter 2022-06-27 15:23:19 UTC
(In reply to titanemdg from comment #3)
> The statu is still 'UNCONFIRMED'
> What is the next ? Does the issues solved ?

Next step is status NEW, that means a second user can confirm the bug. I'm not so familiar with mail merge, so for me steps in initial bug report are not detailed enough. Sorry.
Comment 5 Buovjaga 2023-03-17 12:52:56 UTC
Please attach example document and database.
Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the files.
Comment 6 QA Administrators 2023-09-14 03:05:57 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2023-10-15 03:16:31 UTC
Dear titanemdg,

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