Commit 0e94aa69195b1a3f17abb486db67fe5e3b0928e5

Authored by Jay Berkenbilt
1 parent 5e6dfc93

Fix up documentation around Windows wildcard fix

ChangeLog
@@ -3,14 +3,9 @@ @@ -3,14 +3,9 @@
3 * 9.1.rc1: release 3 * 9.1.rc1: release
4 4
5 * Improve behavior of wildcard expansion for msvc executable when 5 * Improve behavior of wildcard expansion for msvc executable when
6 - run from the Windows cmd.exe shell. The behavior is not identical  
7 - to UNIX or to running the mingw executable in that, for msvc,  
8 - wildcard expansion is performed transparently by qpdf.exe itself.  
9 - That means that *.pdf and "*.pdf*" are interpreted identically. If  
10 - you need to specify the name of a file that has a * or ? in its  
11 - actual filename on the Windows CLI with the msvc-built executable,  
12 - you can write the name of the file in another file and use the  
13 - @file syntax to prevent expansion. Fixes #224. 6 + run from the Windows cmd.exe shell. Unlike in UNIX environments,
  7 + Windows leaves it up to the executable to expand its own
  8 + wildcards. Fixes #224.
14 9
15 * When reading /P from the encryption dictionary, use static_cast 10 * When reading /P from the encryption dictionary, use static_cast
16 instead of QIntC to convert the value to a signed integer. The 11 instead of QIntC to convert the value to a signed integer. The
manual/qpdf-manual.xml
@@ -4687,9 +4687,9 @@ print "\n"; @@ -4687,9 +4687,9 @@ print "\n";
4687 </listitem> 4687 </listitem>
4688 <listitem> 4688 <listitem>
4689 <para> 4689 <para>
4690 - Improve shell wildcard expansion behavior  
4691 - (<literal>*</literal> and <literal>?</literal>) of the  
4692 - <command>qpdf.exe</command> as built my MSVC. 4690 + Fix shell wildcard expansion behavior (<literal>*</literal>
  4691 + and <literal>?</literal>) of the <command>qpdf.exe</command>
  4692 + as built my MSVC.
4693 </para> 4693 </para>
4694 </listitem> 4694 </listitem>
4695 </itemizedlist> 4695 </itemizedlist>