You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected the table to be fitted to page width, but I do not know if this is possible.
I know that for very (very!) wide tables this could mean having to shrink the table a lot.
As annoying as it is, one can zoom in on the PDF if necessary. I find it better than to have the table cut and not being able to examine the full contents.
Logs
No response
The text was updated successfully, but these errors were encountered:
Operating system
Windows
Joplin version
3.2.11
Desktop version info
Joplin 3.2.11 (prod, win32)
Client ID: 52e7ef7a091b4b78b73f8404f40d071c
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes
Revision: 2fba101
Backup: 1.4.2
Better Code Blocks: 2.0.0
Delete unlinked resources: 1.0.0
Editor Themes: 1.0.2
Enhancement: 1.2.1
Extra Markdown editor settings: 1.8.0
Freehand Drawing: 2.14.0
Katex Input Helper: 1.0.5
Kminder Mindmap: 0.8.6
Math Mode: 0.7.1
MultiMarkdown Table Tools: 1.2.1
Note Tabs: 1.4.0
Outline: 1.5.14
Simple Highlighter: 1.0.0
Tagging: 1.0.3
Text Colorize: 1.2.5
YesYouKan: 1.0.11
Current behaviour
I have a note with a couple of wide tables (all columns do not fit into the page width).
Inside Joplin I can of course scroll horizontally to see the full contents of the table.
When I export to PDF, however, the table is cropped to page width, and the scrollbar is printed, which looks strange.
I created a dummy table just to show:
This is the output of printing to PDF:
Expected behaviour
I expected the table to be fitted to page width, but I do not know if this is possible.
I know that for very (very!) wide tables this could mean having to shrink the table a lot.
As annoying as it is, one can zoom in on the PDF if necessary. I find it better than to have the table cut and not being able to examine the full contents.
Logs
No response
The text was updated successfully, but these errors were encountered: