Printing in Kate

[Waqar Ahmed]

Hi,

Simple solution is to not use Kate for printing. If I am being honest, the
printing situation is more or less unmaintained and largely untested. For
KF7 I will propose to drop printing support from KTextEditor simply because
there is a lot of bugs that Qt doesn't want to fix or ignores and the whole
things is just buggy and crappy. There are better things out there, use
them. For e.g, export to html and use a browser like chrome to print things.

Regards,
Waqar


On Sun, Dec 1, 2024 at 9:15 PM Will Senn <will.senn at gmail.com> wrote:

> Hi All,
>
> I have been using Kate for a very long time and I really like it for
> editing tasks. The one thing it doesn't (didn't) do is print reasonably.
> By reasonably, I mean, in a different font, with correct line spacing,
> without highlighting, etc... in other words, so that it looks good on a
> laser monochrome printer. That has changed somewhere along the line and
> now it is much better - you can set a different font for printing, yay!
> However, it seems to have a few issues. I'd like to run them by y'all
> and see if there are settings or something that can address the issues:
>
> 1. When you select a duplex setting (print on long edge), the setting
> doesn't persist across restarts of KDE. My workaround, which I don't
> like, but which works, is to default my printer to duplex.
>
> 2. The inter line spacing is way to big on the printed file (looks like
> it's nearly a full line-height between printed lines. Yuck. Compared
> with Xed, or BBedit on Mac, or Notepad++ on Windows, the linespacing is
> awful. A file printed with one of these is 4 pages, but becomes 6 with
> the extra space. I saw a setting for line spacing in the editor, but
> that messes with the editing experience, and it's an upper bound anyway.
> What would be ideal is if the app used single line spacing for printing.
>
> 3. Syntax highlighting and any selections or bracket matches (if cursor
> is sitting on a bracket) get sent to the printer. It'd be swell if there
> was a way to suppress this behavior with a setting.
>
> Any solutions, workarounds, etc. appreciated.
>
> Thanks,
>
> Will
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kwrite-devel/attachments/20241202/2885cbc5/attachment.htm>