Bug 65302 - FILESAVE: Linebreaks added after paragraph ending in hyperlink when saving to doc format
Summary: FILESAVE: Linebreaks added after paragraph ending in hyperlink when saving to...
Status: RESOLVED DUPLICATE of bug 66165
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.3.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
: 65445 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-06-03 15:06 UTC by Kep Amun
Modified: 2013-07-04 03:26 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Example document that explains and shows the behavior of this bug. (11.00 KB, application/msword)
2013-06-03 15:06 UTC, Kep Amun
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kep Amun 2013-06-03 15:06:54 UTC
Created attachment 80233 [details]
Example document that explains and shows the behavior of this bug.

Problem description: 
When saving a document as a doc file, a blank line is added after paragraphs that end in a hyperlink. The blank lines are not visible until the document is closed and re-opened. This effect can create many linebreaks in a document (one per paragraph ending in a hyperlink), possibly increasing the page count. Example: Single line with only link to 'homepage'.

There is no problem with paragraphs that have non-hyper link text after the hyperlink, even spaces or punctuation. This means an effective workaround is to simply add a space after the hyperlink. (Add a space at the beginning too if you want it perfectly centered)


Steps to reproduce:
1. Add a paragraph to any document that ends in a hyperlink with nothing, not even punctuation after the hyperlink in that paragraph.
2. Add another paragraph just below that one for reference so you can see the added space later.
3. Save document in '.doc' format.
4. Close document.
5. Reopen document

Current behavior:
A blank line is added below paragraphs ending in a hyperlink.

Expected behavior:
No blank line is added below paragraphs ending in a hyperlink. The document is saved just as it does now with more non-hyperlink text after the hyperlink.

Attached is an example document that shows this behavior.
To test: Open the document and delete the blank line below the second paragraph. Save. Close. Reopen. Blank line is back.

Operating System: Windows 7
Version: 4.0.3.3 release
Comment 1 ign_christian 2013-06-07 09:35:34 UTC
> Attached is an example document that shows this behavior.
> To test: Open the document and delete the blank line below the second
> paragraph. Save. Close. Reopen. Blank line is back.

I can confirm same behavior. But it doesn't persist if saving as XLSX or ODT.
Tested on LO 4.0.4.1 (Win7 32bit)
Comment 2 Michael 2013-06-07 13:47:38 UTC
I can confirm it with 4.1.0.0.beta2 and Master build de72699615bd2d12257d1a295e541ed5117fe28 4.2.0.0.alpha0+

Earliest version where this bug appeared is 4.0.3.1.
4.0.2.2 shows the expected behavior.
All tested on OSX 10.8.3.
Comment 3 Michael 2013-06-07 13:50:15 UTC
*** Bug 65445 has been marked as a duplicate of this bug. ***
Comment 4 ign_christian 2013-06-07 14:41:41 UTC
> Earliest version where this bug appeared is 4.0.3.1.
> 4.0.2.2 shows the expected behavior.
So it's a regression ?

> All tested on OSX 10.8.3.
Set Platform to: All
Comment 5 Robert Sharp 2013-07-03 11:49:15 UTC
This also appears to happen when a field is inserted at the end of the line (not just a hyperlink). It also happens in table cells in the same manner.
Comment 6 ign_christian 2013-07-04 03:26:10 UTC
> This also appears to happen when a field is inserted at the end of the line
> (not just a hyperlink). It also happens in table cells in the same manner.
It's been reported on another bug report. You could search that & perhaps you could give some important infos there.

Good news that fix for bug reported by Kep Amun is available on 4.0.5 regarding Bug 66165. So we mark this duplicate to that bug.

Please comment on that bug if it still happen in upcoming release.

*** This bug has been marked as a duplicate of bug 66165 ***