Bug 146783 - When printing with LibreOffice Writer, there is no facility to specify a custom sized paper for printing
Summary: When printing with LibreOffice Writer, there is no facility to specify a cust...
Status: RESOLVED DUPLICATE of bug 78916
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.5.2 release
Hardware: All Linux (All)
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-15 14:37 UTC by David
Modified: 2022-01-19 10:14 UTC (History)
0 users

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 David 2022-01-15 14:37:27 UTC
Description:
When printing with LibreOffice Writer, there is no facility to specify a custom sized paper for printing. You can only select from a selection of pre-defined sizes. It would be good if a custom size could be specified when printing, as can be done with other applications such as Mozilla Firefox and Thunderbird. These applications have the option "print using system dialogue", which allows you to set a custom size of your own specification.

Steps to Reproduce:
1.Choose print from the file menu
2.
3.

Actual Results:
No option to set custom size

Expected Results:
An option to set a paper size of my personal specification.


Reproducible: Always


User Profile Reset: No



Additional Info:
It would be nice to be able to set a custom size of paper to print.
Comment 1 Timur 2022-01-15 15:00:37 UTC
I think this is known so Duplicate. Please search and mark.
Comment 2 David 2022-01-16 14:47:11 UTC
I have tried searching previous reports but I can not find any reports that match the one I have reported.
Comment 3 Tex2002ans 2022-01-19 07:11:40 UTC
I believe this is the duplicate:

- Bug 78916 - Custom page size missing from print dialog
Comment 4 Timur 2022-01-19 10:14:07 UTC
Seems so. Thanks. If not, please explain why.

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