Krzysztof Kowalczyk

Currently we're using system print dialog, which is easy. It seems to be getting worse in win 11. Unfortunately custom print dialog would be a bit of work.

Can you provide a minimal test case? Preferably something added to existing tests (https://github.com/kjk/volante/tree/master/csharp/tests/Tests).

I don't think it's an issue of raw speed. There does seem to a more visible shift in newer version. It's easier to see with `Ctrl - +` and `Ctrl...

Independently, `scroll + ctrl` is too sensitive but I don't think it's different vs 3.4.6.

My thinking is: `[Open2(,[flags])]` as an improvement over `[Open(....)]`. One of the flags will be `open in current tab`.

Can't do anything without a test PDF showing the problem

Got the document, confirmed mis-renders. Same problem in mupdf 1.23.0 Probably related debug info: ``` ignoring CMap range (225-225) that is outside of the codespace non-embedded font using identity encoding:...

Making the following change: ```diff diff --git a/mupdf/source/pdf/pdf-cmap.c b/mupdf/source/pdf/pdf-cmap.c index d38f8cd10..c72545411 100644 --- a/mupdf/source/pdf/pdf-cmap.c +++ b/mupdf/source/pdf/pdf-cmap.c @@ -535,7 +535,7 @@ add_range(fz_context *ctx, pdf_cmap *cmap, unsigned int low, unsigned int high,...

What's the difference between "closing all tabs but one" and "closing all tabs but not the selected ones"?

I've added `CloseAllTabs` and `CloseTabsToTheLeft` commands which complete this. You can invoke them via context-menu on the tab, `Ctrl + K` Command Palette or assign a custom shortcut https://www.sumatrapdfreader.org/docs/Customizing-keyboard-shortcuts