home.social

#poppler — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #poppler, aggregated by home.social.

  1. “Secure #redaction by design and through extensive #testing

    #Censor 0.6.0 comes with many more #security improvements, motivated by extensive testing on more then 1,000 #PDF document samples. You may now redact securely also links, form fields and widgets. In rare cases, when partial image redaction fails, the more secure full image removal is used instead.

    But even more important, Censor now warns you, when unsuccessful redaction is detected during postprocessing. This reduces the impact of known issues of unsecure redaction.

    Polish is the 11th language you may speak with Censor. Thanks to its translators (among them, @mondstern)!

    Thanks a lot also to #pypdf, #qpdf, #pikepdf, #Ghostscript, #MuPDF, #PyMuPDF, and #poppler contributors for the great resource of PDF document samples!

    Find it at @flathub: flathub.org/apps/page.codeberg and @Codeberg: codeberg.org/censor/Censor

    #Censorship #Codeberg #Flathub #GNOME #Linux #Python

  2. “Secure #redaction by design and through extensive #testing

    #Censor 0.6.0 comes with many more #security improvements, motivated by extensive testing on more then 1,000 #PDF document samples. You may now redact securely also links, form fields and widgets. In rare cases, when partial image redaction fails, the more secure full image removal is used instead.

    But even more important, Censor now warns you, when unsuccessful redaction is detected during postprocessing. This reduces the impact of known issues of unsecure redaction.

    Polish is the 11th language you may speak with Censor. Thanks to its translators (among them, @mondstern)!

    Thanks a lot also to #pypdf, #qpdf, #pikepdf, #Ghostscript, #MuPDF, #PyMuPDF, and #poppler contributors for the great resource of PDF document samples!

    Find it at @flathub: flathub.org/apps/page.codeberg and @Codeberg: codeberg.org/censor/Censor

    #Censorship #Codeberg #Flathub #GNOME #Linux #Python

  3. “Secure #redaction by design and through extensive #testing

    #Censor 0.6.0 comes with many more #security improvements, motivated by extensive testing on more then 1,000 #PDF document samples. You may now redact securely also links, form fields and widgets. In rare cases, when partial image redaction fails, the more secure full image removal is used instead.

    But even more important, Censor now warns you, when unsuccessful redaction is detected during postprocessing. This reduces the impact of known issues of unsecure redaction.

    Polish is the 11th language you may speak with Censor. Thanks to its translators (among them, @mondstern)!

    Thanks a lot also to #pypdf, #qpdf, #pikepdf, #Ghostscript, #MuPDF, #PyMuPDF, and #poppler contributors for the great resource of PDF document samples!

    Find it at @flathub: flathub.org/apps/page.codeberg and @Codeberg: codeberg.org/censor/Censor

    #Censorship #Codeberg #Flathub #GNOME #Linux #Python

  4. “Secure #redaction by design and through extensive #testing

    #Censor 0.6.0 comes with many more #security improvements, motivated by extensive testing on more then 1,000 #PDF document samples. You may now redact securely also links, form fields and widgets. In rare cases, when partial image redaction fails, the more secure full image removal is used instead.

    But even more important, Censor now warns you, when unsuccessful redaction is detected during postprocessing. This reduces the impact of known issues of unsecure redaction.

    Polish is the 11th language you may speak with Censor. Thanks to its translators (among them, @mondstern)!

    Thanks a lot also to #pypdf, #qpdf, #pikepdf, #Ghostscript, #MuPDF, #PyMuPDF, and #poppler contributors for the great resource of PDF document samples!

    Find it at @flathub: flathub.org/apps/page.codeberg and @Codeberg: codeberg.org/censor/Censor

    #Censorship #Codeberg #Flathub #GNOME #Linux #Python

  5. “Secure #redaction by design and through extensive #testing

    #Censor 0.6.0 comes with many more #security improvements, motivated by extensive testing on more then 1,000 #PDF document samples. You may now redact securely also links, form fields and widgets. In rare cases, when partial image redaction fails, the more secure full image removal is used instead.

    But even more important, Censor now warns you, when unsuccessful redaction is detected during postprocessing. This reduces the impact of known issues of unsecure redaction.

    Polish is the 11th language you may speak with Censor. Thanks to its translators (among them, @mondstern)!

    Thanks a lot also to #pypdf, #qpdf, #pikepdf, #Ghostscript, #MuPDF, #PyMuPDF, and #poppler contributors for the great resource of PDF document samples!

    Find it at @flathub: flathub.org/apps/page.codeberg and @Codeberg: codeberg.org/censor/Censor

    #Censorship #Codeberg #Flathub #GNOME #Linux #Python

  6. My problem is not the computer (hardware) that is broken. My problem is the software that is broken.
    One of todays problems: trac.macports.org/ticket/73454
    #macports #poppler

  7. After 1.5 years in the making, @gnome Papers 50 will let you create freestanding text & ink annotations on PDFs (using a Wacom tablet stylus, for example), i.e. drawing & handwriting (to circle things or sign documents the old-fashioned way, or highlighting on scanned documents): lbaudin.pages.gitlab.gnome.org

    Used it in practice today. I've been hoping for this for about 20 years.
    Papers nightly is such a massive improvement!

    Thank you @lbaudin for implementing it :owi:

    #GNOMEPapers #PDF #Poppler

  8. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  9. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  10. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  11. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  12. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  13. Learn how to merge PDF files in Linux using pdfunite command. Step-by-step tutorial with examples, scripting tips, faq and troubleshooting.

    Read full guide here: ostechnix.com/merge-pdf-files-

    #Pdf #Pdfunite #Poppler #MergePdf #Linux #Commandline

  14. So on my laptop there's a program called "poppler" that has updates every few months. It came with the Linux Mint installation and I don't think I've ever gone out of my way to use it.

    I keep it installed because every time the name comes up in the update manager I'm reminded of Futurama and smile.

    #Linux #LinuxMint #Futurama #Poppler

  15. To find out what fonts are used by a #PDF, you can use, e.g., the "pdffonts" command that comes with #Poppler (in #Debian and Debian-based systems it's in the "poppler-utils" package).
    #FOSS

  16. <

    Update:
    If I import in #Inkscape with #poppler/#cairo library, the qrcode it's importer and working BUT I lose the multipage import 😞

    Maybe @doctormo you have some suggestion about that?

  17. Am really enjoying using Julia as a pseudo-shell.

    I needed to chop up some pdfs and rearrange the pages. Poppler-utils is great but I never really learnt Bash scripting so it was going to be a bit of a slog.

    Thankfully, Julia makes it really easy to bulk copy or move files in mostly regular sequences

    #JuliaLang #poppler

  18. pop a #Poppler in your mouth when you come to Fishy Joe's, what they're made of is a mystery, where they come from no one knows.

    You can pick 'em, you can lick 'em, you can chew 'em, you can stick 'em, if you promise not to sue us, you can shove one up your nose.

  19. @jsoriano Please don't thank me (dreua) specifically, I'm just one part of the maintenance team who runs this account 😉

    We currently don't accept donations (don't really need them) but @tsdgeos mentioned in his talk about poppler (one of the great libraries PDF Arranger is built upon) that they could use some resources for testing in or .

    Words of appreciation are, of course, always welcome. Thank you ❤️

  20. @tsdgeos Thanks for the cool talk and thanks to you and all the maintainers of ! Our small desktop app is truly standing on the shoulders of giants :)

    If anyone from the people who offered us donations is reading this: Sounds like Freedesktop and Poppler could put your money to good use 😉

  21. Long-time KDE developer Albert Astals Cid @tsdgeos is also maintainer of the PDF renderer Poppler and has given a nice lightning talk on #FOSDEM 2025 about this project:

    fosdem.org/2025/schedule/event

    By the way, at OpenPrinting we use Poppler a lot (thanks a lot, Albert), but we are working on alternatives to avoid C++ and also because of the license.

    #OpenPrinting #KDE #Poppler #PDF #Okular

  22. @timbosteron Best you use pdfimages from #poppler-tools to extract the original images embedded in the PDF file. So no loss ocurs from conversions 😇 ...

  23. @AndiBarth Same on Fedora. I'd say this is likely a bug in evince (maybe ), have you looked for open bugs or reported it?

    Fifefox and Okular can zoom in as expected. I'd suggest the latter because Firefox needs quite some time to render these complex PDFs.

  24. New hardcore #PDF rendering performance benchmark for #Poppler:
    "Jesus Christ it's a #Lyon (map), get in the car!" :blobnom:

    That map takes 26 seconds to render with Poppler on #Linux, but only 6 seconds with PDFjs, or 15 seconds with XPDF: gitlab.freedesktop.org/poppler

    I've profiled the issue on the various Poppler rendering backends, and there are some hypotheses about the slowness. If anyone can help fix this, that would be fantastic.

    #Okular #GNOMEPapers #Evince #Sysprof #profiling

  25. @thefool @sebsauvage

    Sous Linux, la plupart des lecteurs #PDF (#Evince, #Okular, Papers…) utilisent la bibliothèque #Poppler. J'imagine que le problème sera donc le même partout 😕

    poppler.freedesktop.org

  26. CW: Gigantic Fedora rant

    I have just upgraded to 41 and #okular just straight up stop working. Every time I open a file it just pops out an error dialog says Could not open <file>.

    So at first I thought… somehow
    #KDE decided to ship software without simple testing? Or probably a "it doesn't work on my machine" moment, which would be pretty painful.

    Anyhow I opened it from the terminal to obtain the logs, and:

    kf.coreaddons: "Could not load plugin from /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: Cannot load library /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: undefined symbol: _ZN7Poppler11AsyncObject4doneEv"
    org.kde.okular.core: Failed to load plugin "/usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so": "Could not load plugin from /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: Cannot load library /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: undefined symbol: _ZN7Poppler11AsyncObject4doneEv"
    Well it probably has something to do with #poppler. The weird thing is, there is no major version change for poppler between F40 and F41, so supposedly there shouldn't be any breaking changes. I'm also stuck now because there are no downgrades available for poppler.

    And then I realized I am not having the latest okular version, so I did a
    dnf up, and just remembered I didn't want to perform the update because it pulls in ibus which I really detest.

    So I did some digging and SOMEHOW FEDORA DECIDED TO PULL IN
    ibus-anthy if you install langpacks-core-ja.

    They fucking chose
    anthy. HARD DEPENDENCY. INSANE. I have no idea why. Probably because they don't like mozc (which uses Qt).

    Solution: I removed all the langpacks from my system. Now okular works.

    #opensource #rant #linux #foss #ultramarinelinux #fedora

  27. I've always envied Adobe Reader/Acrobat users and tablet apps users who have forever been able to freely write on PDFs as if they are physical sheets of papers. Yes, you can use #Xournal++, but I want it as a streamlined UX built into my day-to-day #GNOME PDF reader app.

    Although it was not implemented in #Evince, the #Poppler library has some support for ink-like handwritten #PDF annotations.

    I have now put together usecases & broad ideas into this #GNOMEPapers ticket: gitlab.gnome.org/GNOME/Incubat

  28. In which I do archaeology in the depths of Loch Ness, and describe the mythical beast that one inevitably must face on the quest for the Holy Grail of performance for the #GNOMEPapers #PDF reader: multithreaded, tile-based rendering for libView gitlab.gnome.org/GNOME/Incubat

    #Linux #Poppler #GNOME #softwaredevelopment

  29. Alright people, time to seize the opportunity in #GNOMEPapers to fix one of my long-time performance annoyances with Evince: a potential 2x speedup by… avoiding rendering everything twice (due to the sidebar's thumbnails).

    Barring #Poppler backend renderer performance issues, this should help #GNOME have a noticeably faster and power-efficient #PDF reader app 🤞 gitlab.gnome.org/GNOME/Incubat

  30. Okay, found out why pdfimages, the image extraction tool that comes with the PDF rendering library #poppler, can't extract different map versions from Paizo interactive maps that they create for their #Pathfinder adventure paths

    In short, the maps aren't image elements but form buttons with icons that get hidden/shown depending on which map version is supposed to be shown

    #ttrpg #rpg #vtt #vttrpg