Created attachment 127751 [details] Error message when I open any ePUB file with Okular format. SUMMARY I have an epub and Okular can read it without any issues. I add some annotations and want to save them with the "Okular document archive" file format. But when I open these files, Okular says "Error while opening EPub document." I tried it with different ePUB files. So at the moment I can not add any annotations, because I am not able to save them. STEPS TO REPRODUCE 1. I save a file with the Okular format 2. I try to open this file, but I get an error message instead. 3. OBSERVED RESULT Attached screenshot qmake --version QMake version 3.1 Using Qt version 5.14.2 in /usr/lib System: Host: manjaro-2019-11 Kernel: 5.6.5-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Xfce 4.14.2 Distro: Manjaro Linux Machine: Type: Desktop System: Intel product: KBL-R MRD v: 0.1 serial: <filter> Mobo: Intel model: MIR1 v: RVP7 serial: <filter> UEFI [Legacy]: American Megatrends v: 5.12 date: 07/12/2018 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K270 charge: 55% (should be ignored) status: Discharging CPU: Topology: Quad Core model: Intel Core i7-8650U bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 8192 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33615 Speed: 800 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: intel unloaded: modesetting resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.4 direct render: Yes Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Casio CASIO USB-MIDI type: USB driver: snd-usb-audio bus ID: 1-2:5 Sound Server: ALSA v: k5.6.5-1-MANJARO Network: Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel port: f040 bus ID: 01:00.0 IF: wlp1s0 state: up mac: <filter> Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: e000 bus ID: 02:00.0 IF: enp2s0 state: down mac: <filter> Drives: Local Storage: total: 942.70 GiB used: 720.64 GiB (76.4%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-9WS142 size: 465.76 GiB ID-2: /dev/sdb vendor: SanDisk model: SD8SN8U512G1027 size: 476.94 GiB Partition: ID-1: / size: 19.10 GiB used: 16.02 GiB (83.9%) fs: ext4 dev: /dev/sdb6 ID-2: /home size: 400.62 GiB used: 244.36 GiB (61.0%) fs: ext4 dev: /dev/sdb7 Sensors: System Temperatures: cpu: 65.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 278 Uptime: 10h 13m Memory: 15.43 GiB used: 5.36 GiB (34.7%) Init: systemd Compilers: gcc: 9.3.0 clang: 9.0.1 Shell: bash v: 5.0.16 inxi: 3.0.37
Are you naming the file as .epub instead of .okular?
Oh it works! Great! Thank you. But still, I think it's a bug or a missing feature. Most often I open epub files and then I just save it on the same filename, or change the prefix. But I would never come up with the idea to call the suffix .okular. There is no information I am supposed to do so.
(In reply to shinanqu from comment #2) > Oh it works! Great! Thank you. > > But still, I think it's a bug or a missing feature. Most often I open epub > files and then I just save it on the same filename, or change the prefix. > But I would never come up with the idea to call the suffix .okular. There is > no information I am supposed to do so. From Okular official handbook: Okular has the "document archiving" feature. This is an Okular-specific format for carrying the document plus various metadata related to it (currently only annotations). You can save a "document archive" from the open document by choosing File → Save As and selecting Okular document archive in the Filter selector. Documents saved this way will get .okular as their filename extension. To open an Okular document archive, just open it with Okular as it would be e.g. a PDF document. https://docs.kde.org/trunk5/en/kdegraphics/okular/annotations.html
Isn't .okular the default suggested extension when saving? Ah, actually i think there was an issue with the Qt/GTK save dialog integration and maybe you don't get that and that's why it's confusing for you. Not really something we can easily fix sadly :/
Yes, sadly it's not intuitive. Now I know and it's not an issue for me anymore. But alone I would never come up with this solution. Sadly I am not a manual reader.