Update Windows install docs: unpin GhostScript, document why Poppler stays pinned - #24
Merged
Conversation
Owner
|
Hi @DABH , you can rebase or merge in the latest changes in the default branch to fix the CI issues. |
- ghostscript: the 9.55.0 pin is unnecessary; the current package works (verified with 10.7.1 on Windows 11). The PATH snippet now auto-detects the installed GhostScript version instead of hardcoding gs9.55.0, so it keeps working across releases. - poppler: keep the 0.89.0 pin but document why it is required: Chocolatey poppler packages newer than 0.89.0 do not ship working Windows binaries (25.x+ contain only the upstream source tarball; the 22.11.x builds are conda repacks missing their dependency DLLs, so their executables cannot start). Users who want a current Poppler are pointed at the prebuilt poppler-windows releases together with the extension's existing path settings.
DABH
force-pushed
the
readme/windows-choco-versions
branch
from
August 30, 2026 00:59
23e8f06 to
c236db2
Compare
ahnafnafee
self-requested a review
August 30, 2026 01:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Windows install instructions pin
ghostscriptto 9.55.0 andpopplerto 0.89.0, with a PATH snippet hardcodinggs9.55.0paths. The GhostScript pin looks stale (and the hardcoded PATH breaks as soon as a different version is installed), while the Poppler pin looks arbitrary — tempting users (me included) to "fix" it by installing the latest, which actively breaks the extension.What I verified (Windows 11)
bindirectory to PATH on install.25.x–26.6.0packages contain only the upstream source tarball (CMakeLists,cpp/, etc.) — no Windows executables at all.22.11.0.*packages repack a conda build without its dependency DLLs (freetype.dll,zlib.dll,libpng16.dll,openjp2.dll,lcms2.dll,tiff.dll,libcurl.dllare all missing fromLibrary/bin), sopdftocairo.exe/pdfinfo.exefail to start.0.89.0remains the newest Chocolatey version with working, self-contained binaries.Changes
ghostscriptin the install command.gs*install) and update the manual-PATH block to match.poppler --version 0.89.0pin, now with a callout explaining why it must stay pinned, plus a pointer to the prebuilt poppler-windows releases + the extension'spostscript-preview.path.*settings for anyone who wants a current Poppler.