Bug 32898 - New Line and Carriage Return in mailings
Summary: New Line and Carriage Return in mailings
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-07 05:36 UTC by Olivier Hallot
Modified: 2012-08-31 10:04 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Word converts new-lines into carriages-return in mailings (54.78 KB, image/png)
2011-01-07 05:41 UTC, Olivier Hallot
Details
Writer preserves new-lines in mailings (74.08 KB, image/png)
2011-01-07 05:42 UTC, Olivier Hallot
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Hallot 2011-01-07 05:36:54 UTC
Hi

One of the differences between MSOffice 2003 and LibreOffice is the way the mailing is handled between the two applications.

The issue raises when the source of the data is an Excel spreadsheet that contains cells with several "\n" (new lines characters). These "\n"  emulates a list inside the cells text.

When Word (2003) insert the Excel content into a mailing, it transforms "\n" into "\cr" (carriage return).

Writer does not makes this conversion.

The mailing wizzard of Writer should have an option to let user choose if he wants to convert "\n" into "\cr" in order to improve compatibility between these two softwares.

the attached images show the differences in the mailing rendering of multi-lines spreadsheet cells.
Comment 1 Olivier Hallot 2011-01-07 05:41:58 UTC
Created attachment 41742 [details]
Word converts new-lines into carriages-return in mailings
Comment 2 Olivier Hallot 2011-01-07 05:42:44 UTC
Created attachment 41743 [details]
Writer preserves new-lines in mailings
Comment 3 Björn Michaelsen 2011-12-23 11:34:45 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 4 sasha.libreoffice 2012-02-23 02:52:00 UTC
In 3.5.0 still reproducible?
Comment 5 Florian Reisinger 2012-08-14 13:58:05 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Florian Reisinger 2012-08-14 13:59:23 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 Florian Reisinger 2012-08-14 14:03:58 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 8 Florian Reisinger 2012-08-14 14:06:12 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian