From 0e94aa69195b1a3f17abb486db67fe5e3b0928e5 Mon Sep 17 00:00:00 2001 From: Jay Berkenbilt Date: Sun, 10 Nov 2019 20:19:38 -0500 Subject: Fix up documentation around Windows wildcard fix --- ChangeLog | 11 +++-------- manual/qpdf-manual.xml | 6 +++--- 2 files changed, 6 insertions(+), 11 deletions(-) diff --git a/ChangeLog b/ChangeLog index b7aaa693..6b5a7cdf 100644 --- a/ChangeLog +++ b/ChangeLog @@ -3,14 +3,9 @@ * 9.1.rc1: release * Improve behavior of wildcard expansion for msvc executable when - run from the Windows cmd.exe shell. The behavior is not identical - to UNIX or to running the mingw executable in that, for msvc, - wildcard expansion is performed transparently by qpdf.exe itself. - That means that *.pdf and "*.pdf*" are interpreted identically. If - you need to specify the name of a file that has a * or ? in its - actual filename on the Windows CLI with the msvc-built executable, - you can write the name of the file in another file and use the - @file syntax to prevent expansion. Fixes #224. + run from the Windows cmd.exe shell. Unlike in UNIX environments, + Windows leaves it up to the executable to expand its own + wildcards. Fixes #224. * When reading /P from the encryption dictionary, use static_cast instead of QIntC to convert the value to a signed integer. The diff --git a/manual/qpdf-manual.xml b/manual/qpdf-manual.xml index 4a817269..24747159 100644 --- a/manual/qpdf-manual.xml +++ b/manual/qpdf-manual.xml @@ -4687,9 +4687,9 @@ print "\n"; - Improve shell wildcard expansion behavior - (* and ?) of the - qpdf.exe as built my MSVC. + Fix shell wildcard expansion behavior (* + and ?) of the qpdf.exe + as built my MSVC. -- cgit v1.2.3-54-g00ecf