Commit 6219111ed7d6b50f68ebcab5b65517f8b3572ad8

Authored by Jay Berkenbilt
1 parent dba22845

Update references to README files

Most of the README files have been renamed. Refer to the new names.
ChangeLog
  1 +2017-08-22 Jay Berkenbilt <ejb@ql.org>
  2 +
  3 + * Convert all README files to markdown. Names changed as follows:
  4 + - README --> README.md
  5 + - README.hardening --> README-hardening.md
  6 + - README.maintainer --> README-maintainer.md
  7 + - README-what-to-download.txt --> README-what-to-download.md
  8 + - README-windows.txt --> README-windows.md
  9 + The file README-windows-install.txt remains a text file.
  10 +
1 11 2017-08-21 Jay Berkenbilt <ejb@ql.org>
2 12  
3 13 * Add support for writing PCLm files. Most of the work was done by
... ...
README-maintainer.md
... ... @@ -43,7 +43,7 @@ Release Reminders
43 43 properly handled.
44 44  
45 45 * Remember to avoid using operator[] with std::string or
46   - std::vector. See README.hardening for details.
  46 + std::vector. See README-hardening.md for details.
47 47  
48 48 * Increment shared library version information as needed (LT_* in
49 49 configure.ac)
... ... @@ -110,7 +110,7 @@ Release Reminders
110 110  
111 111 * Before releasing, rebuild and test debian package.
112 112  
113   - * Remember to copy README-what-to-download.txt separately onto the
  113 + * Remember to copy README-what-to-download.md separately onto the
114 114 download area.
115 115  
116 116 * Remember to update the web page including putting new documentation
... ...
README-what-to-download.md
... ... @@ -37,7 +37,7 @@ download.
37 37  
38 38 If you want to build qpdf for Windows yourself with either MINGW or
39 39 MSVC 2010, you can download this file and extract it inside the
40   - qpdf source distribution. Please refer to README-windows.txt in
  40 + qpdf source distribution. Please refer to README-windows.md in
41 41 the qpdf source distribution for additional details. Note that you
42 42 need the 2012-06-20 version or later to be able to build qpdf 3.0
43 43 or newer. The 2009-10-24 version is required for qpdf 2.3.1 or
... ... @@ -51,6 +51,6 @@ download.
51 51 libary, it includes a README file and some scripts to help you
52 52 build it for Windows. qpdf was built using a binary distribution of
53 53 libjpeg-turbo for Windows. You will also have to provide those. See
54   - README-windows.txt for details.
  54 + README-windows.md for details.
55 55  
56   -If you want to build on Windows, please see also README-windows.txt.
  56 +If you want to build on Windows, please see also README-windows.md.
... ...
README.md
... ... @@ -17,7 +17,7 @@ QPDF depends on the external libraries &quot;zlib&quot; and &quot;jpeg&quot;. These are
17 17 part of every Linux distribution and are readily available. Download
18 18 information appears in the documentation. For Windows, you can
19 19 download pre-built binary versions of these libraries for some
20   -compilers; see README-windows.txt for additional details.
  20 +compilers; see README-windows.md for additional details.
21 21  
22 22 QPDF requires a C++ compiler that works with STL. Your compiler must
23 23 also support "long long". Almost all modern compilers do. If you are
... ... @@ -82,7 +82,7 @@ Building from a pristine checkout
82 82 When building qpdf from a pristine checkout from version control,
83 83 documentation and automatically generated files are not present.
84 84 Building on Windows from a pristine checkout is not guaranteed to work
85   -because of issues running autoconf; see README-windows.txt for how to
  85 +because of issues running autoconf; see README-windows.md for how to
86 86 handle this. For UNIX and UNIX-like systems, you must have some
87 87 addditional tools installed to build from the source repository. To
88 88 do this, you should run
... ... @@ -124,8 +124,8 @@ QPDF is known to build and pass its test suite with mingw (latest
124 124 version tested: gcc 4.6.2), mingw64 (latest version tested: 4.7.0) and
125 125 Microsoft Visual C++ 2010, both 32-bit and 64-bit versions. MSYS plus
126 126 ActiveState Perl is required to build as well in order to get make
127   -and other related tools. See README-windows.txt for details on how to
128   -build under Windows, see README-windows.txt.
  127 +and other related tools. See README-windows.md for details on how to
  128 +build under Windows, see README-windows.md.
129 129  
130 130  
131 131 Additional Notes on Build
... ... @@ -137,7 +137,7 @@ obeying the compiler specified with configure. This can be enabled by
137 137 passing --with-buildrules=buildrules where buildrules corresponds to
138 138 one of the .mk files (other than rules.mk) in the make directory.
139 139 This should never be necessary on a UNIX system, but may be necessary
140   -on a Windows system. See README-windows.txt for details. There is a
  140 +on a Windows system. See README-windows.md for details. There is a
141 141 gcc-linux.mk file enable "gcc-linux" build rules, but it is intended
142 142 to help test the build system; Linux users should build with the
143 143 "libtools" rules, which are enabled by default.
... ...
configure.ac
... ... @@ -228,7 +228,7 @@ AC_MSG_CHECKING(which build rules to use)
228 228 AC_SUBST(BUILDRULES)
229 229 AC_ARG_WITH(buildrules,
230 230 AS_HELP_STRING([--with-buildrules=rules],
231   - [which build rules to use; see README]),
  231 + [which build rules to use; see README.md]),
232 232 [BUILDRULES=$withval],
233 233 [BUILDRULES=libtool])
234 234 AC_MSG_RESULT($BUILDRULES)
... ...
libqpdf/SecureRandomDataProvider.cc
... ... @@ -118,7 +118,7 @@ SecureRandomDataProvider::provideRandomData(unsigned char* data, size_t len)
118 118  
119 119 #else
120 120  
121   -# error "Don't know how to generate secure random numbers on this platform. See random number generation in the top-level README"
  121 +# error "Don't know how to generate secure random numbers on this platform. See random number generation in the top-level README.md"
122 122  
123 123 #endif
124 124 }
... ...
make/exec-z
1 1 #!/bin/sh
2   -# This script is used for valgrind testing. See README.maintainer.
  2 +# This script is used for valgrind testing. See README-maintainer.md.
3 3  
4 4 # Create a suppressions file. This can be updated by running valgrind
5 5 # with --gen-suppressions=yes.
... ...
make_dist
1 1 #!/usr/bin/env perl
2 2 #
3 3 # This program creates a source distribution of qpdf. For details,
4   -# see README.maintainer.
  4 +# see README-maintainer.md.
5 5 #
6 6  
7 7 require 5.008;
... ...
manual/qpdf-manual.xml
... ... @@ -87,7 +87,7 @@
87 87 <title>Building and Installing QPDF</title>
88 88 <para>
89 89 This chapter describes how to build and install qpdf. Please see
90   - also the <filename>README</filename> and
  90 + also the <filename>README.md</filename> and
91 91 <filename>INSTALL</filename> files in the source distribution.
92 92 </para>
93 93 <sect1 id="ref.prerequisites">
... ... @@ -210,17 +210,17 @@ make
210 210 configured. You can also set the value of
211 211 <varname>DESTDIR</varname> during installation to install to a
212 212 temporary location, as is common with many open source packages.
213   - Please see also the <filename>README</filename> and
  213 + Please see also the <filename>README.md</filename> and
214 214 <filename>INSTALL</filename> files in the source distribution.
215 215 </para>
216 216 <para>
217 217 Building on Windows is a little bit more complicated. For
218   - details, please see <filename>README-windows.txt</filename> in the
  218 + details, please see <filename>README-windows.md</filename> in the
219 219 source distribution. You can also download a binary distribution
220 220 for Windows. There is a port of qpdf to Visual C++ version 6 in
221 221 the <filename>contrib</filename> area generously contributed by
222 222 Jian Ma. This is also discussed in more detail in
223   - <filename>README-windows.txt</filename>.
  223 + <filename>README-windows.md</filename>.
224 224 </para>
225 225 <para>
226 226 There are some other things you can do with the build. Although
... ... @@ -2102,7 +2102,7 @@ outfile.pdf&lt;/option&gt;
2102 2102 would enable you to use some software-based secure pseudorandom
2103 2103 number generator and to avoid use of whatever the operating system
2104 2104 provides. For details on how to do this, please refer to the
2105   - top-level README file in the source distribution and to comments
  2105 + top-level README.md file in the source distribution and to comments
2106 2106 in <filename>QUtil.hh</filename>.
2107 2107 </para>
2108 2108 </sect1>
... ... @@ -3256,7 +3256,7 @@ print &quot;\n&quot;;
3256 3256 converts numbers to strings. This is largely invisible to
3257 3257 users, but it does trigger a bug in some older versions of
3258 3258 mingw-w64's C++ library. See
3259   - <filename>README-windows.txt</filename> in the source
  3259 + <filename>README-windows.md</filename> in the source
3260 3260 distribution if you think this may affect you. The copy of
3261 3261 the DLL distributed with qpdf's binary distribution is not
3262 3262 affected by this problem.
... ... @@ -3677,7 +3677,7 @@ print &quot;\n&quot;;
3677 3677 not needed to verify a correct build or port of qpdf. They
3678 3678 are needed only when changing the actual PDF output generated
3679 3679 by qpdf. You should enable them if you are making deep
3680   - changes to qpdf itself. See <filename>README</filename> for
  3680 + changes to qpdf itself. See <filename>README.md</filename> for
3681 3681 details.
3682 3682 </para>
3683 3683 </listitem>
... ... @@ -3686,7 +3686,7 @@ print &quot;\n&quot;;
3686 3686 Large file tests are off by default but can be turned on with
3687 3687 <command>./configure</command> or by setting an environment
3688 3688 variable before running the test suite. See
3689   - <filename>README</filename> for details.
  3689 + <filename>README.md</filename> for details.
3690 3690 </para>
3691 3691 </listitem>
3692 3692 <listitem>
... ...