Bug 154910 - Converting a pdf from A3 word file with page breaks using libre office overlaps the pages and makes it hard to read
Summary: Converting a pdf from A3 word file with page breaks using libre office overla...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
7.5.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-19 14:22 UTC by shridhar.sanjeevi
Modified: 2024-02-23 03:15 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
word file (890.17 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2023-04-19 14:27 UTC, shridhar.sanjeevi
Details
attached pdf created as output (234.45 KB, application/pdf)
2023-05-15 05:54 UTC, shridhar.sanjeevi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description shridhar.sanjeevi 2023-04-19 14:22:21 UTC
Description:
Converting a pdf from A3 word file with page breaks using libre office overlaps the pages and makes it hard to read 

Actual Results:
pdf created by libre office gets content overlapping and hence hard to read

Expected Results:
convert the content of word file as visible in word to pdf


Reproducible: Always


User Profile Reset: No

Additional Info:
Converting a pdf from A3 word file with page breaks using libre office overlaps the pages and makes it hard to read
Comment 1 shridhar.sanjeevi 2023-04-19 14:27:45 UTC
Created attachment 186789 [details]
word file
Comment 2 Dieter 2023-05-02 06:18:18 UTC
I can't confirm with

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 006b35d50024b1932d84380b5d2fec1f7066bccd
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (de_DE); UI: en-GB
Calc: CL threaded

Steps:
1. Open attachment 186789 [details]
2. File -> Export as -> Export as PDF

Shridhar, could you please attach result of PDF export?
Comment 3 Buovjaga 2023-05-12 14:32:52 UTC
No problem with 7.5 either.

Arch Linux 64-bit, X11
Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 8; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
7.5.3-1
Calc: CL threaded

Please attach a PDF showing the bad result.
Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the PDF.
Comment 4 shridhar.sanjeevi 2023-05-15 05:54:52 UTC
Created attachment 187284 [details]
attached pdf created as output
Comment 5 Buovjaga 2023-05-15 07:29:58 UTC
Please copy and paste here the contents of your Help - About by clicking the copy button. This allows us to know more about your system.
Comment 6 shridhar.sanjeevi 2023-06-21 08:30:55 UTC
Version: 7.4.6.2 (x64) / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 7 QA Administrators 2023-06-22 03:14:51 UTC Comment hidden (obsolete)
Comment 8 Dieter 2023-07-25 14:00:21 UTC
(In reply to shridhar.sanjeevi from comment #6)
> Version: 7.4.6.2 (x64) / LibreOffice Community

Could you please retest with LO 7.5?
=> NEEDINFO
Comment 9 QA Administrators 2024-01-22 03:12:01 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2024-02-23 03:15:06 UTC
Dear shridhar.sanjeevi,

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