Fix up documentation around Windows wildcard fix

This commit is contained in:
Jay Berkenbilt 2019-11-10 20:19:38 -05:00
parent 5e6dfc938e
commit 0e94aa6919
2 changed files with 6 additions and 11 deletions

View File

@ -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

View File

@ -4687,9 +4687,9 @@ print "\n";
</listitem>
<listitem>
<para>
Improve shell wildcard expansion behavior
(<literal>*</literal> and <literal>?</literal>) of the
<command>qpdf.exe</command> as built my MSVC.
Fix shell wildcard expansion behavior (<literal>*</literal>
and <literal>?</literal>) of the <command>qpdf.exe</command>
as built my MSVC.
</para>
</listitem>
</itemizedlist>