search

mjg / mupdf-spec

mupdf packaging for Fedora
https://copr.fedorainfracloud.org/coprs/mjg/mupdf-git
0 stars 0 forks source link

`mupdf-gl` doesn’t get keyboard input #15

Open ousia opened 1 month ago

ousia commented 1 month ago

@mjg,

many thanks for your new release.

I have compiled it (trying to solve the issue I have with version 1.24.2-1 in Fedora 40.

I cannot get any key (q to quit, only to name one) with mupdf-gl.

I don’t know what it may be wrong here. `

Could you confirm that this is working for you?

Many thanks for your help.

mjg commented 1 month ago

Hi there, and good to know I haven't lost you as a tester :) I use mupdf mainly via zathura, and partly via the mupdf binary; not so much via mupdf-gl. That being said, mupdf-gl works over here 1.24.2-1.fc40: display, search, the key bindings that I know (mupdf-gl still does not come with a man page). This is on Fedora Workstation 40 using i3, in particular with X11.

The only "issue" is an annoying warning about being compiled without clipboard and unicode support, together with a request to file a complaint with the distribution manager.

I will shut off this warning with the next build. The background is that clipboard and unicode support in mupdf-gl work only with Artifex' forked version of freeglut. Well, I think it's fair to see: Only with their own forked version of freeglut, Artifex manage to support clipboard and unicode in mupdf-gl. It's not as if there is no app on Fedora supporting clipboard and unicode at all ...

Now, starting a few versions ago, I build mupdf (the library) as a shared library. This is not only as it should be but the only way in which mupdf's language bindings (c, cpp, python) can be built, and they are needed for PyMuPDF etc. In turn, the shared library cannot be built with a bundled forked freeglut from Artifex - their own build scripts inhibit that. And that is why their request to complain to the distribution manager leaves a somewhat sour taste (while they're a friendly upstream indeed, just not distro-focussed).

I'm fully aware that dropping unicode support leaves part of my user base in the rain, but there's simply no way around that. As far as I can see, Artifex puts a lot of effort into mupdf as a library as well as into PyMuPDF, that is into mupdf as an ecosystem or base for development. mupdf and mupdf-gl, on the other hand, are more like proofs of concepts.

Note also: If you enabled any of my copr repos for mupdf, then 1.24.2-1 may not be the same as what you are getting from the (my) official package in the Fedora repos. This is because of early testing, the python 3.13, a new tesseract etc getting in the way, and I may also mix this up with my 1.24.3 testing.

Currently, 1.24.4 is in the copr repos which I intend to bring to Fedora.

One more note: If you're rebuilding to get unicode support back, I see no way other than reenabling static builds and bundling freeglut. That may even be what Artifex is doing for their builds: static for the apps, and shared for the bindings.

ousia commented 1 month ago

No time now, in a rush.

Could you open any PDF doc with mupdf-gl whatever.pdf and check whether the program quits by pressing q?

No time to talk now. There is a bunch in your message (Artifex makes the rest of us happy).