فهرست منبع

correct typos in the downloads FAQ

Ashish Kulkarni 5 سال پیش
والد
کامیت
753da041ac
1فایلهای تغییر یافته به همراه2 افزوده شده و 3 حذف شده
  1. 2 3
      docs/downloads.md

+ 2 - 3
docs/downloads.md

@@ -356,8 +356,8 @@ If you need versions older than `0.12.0`, you can look at the [obsolete download
 Although the builds are static, it is very important to understand what it means in the context of Qt -- on which wkhtmltopdf is built. A static build means that _only_ Qt is linked in this manner -- the remaining system packages still need to be installed. Over a period of time, major areas of divergence between distributions were found by trial and error:
 
 * **different library versions**: not every distribution provides the same versions. This was especially the case for `libpng` and `libjpeg`, with a lot of distributions choosing between the 1.2, 1.5 and 1.6 series for the former and multiple versions of `libjpeg` and/or its fork `libjpeg-turbo`. While this could be addressed easily by linking them statically (and was actually done so for previous releases) -- it broke down when it came to the next point.
-* **different OpenSSL versions**: due to OpenSSL having a bad track record then (_it's better now_), distributions started aggressively upgrading their OpenSSL version and disabling unused part of the library. This led to a situation where there was effectively zero backward compatibility and things started breaking randomly -- see [#3001](https://github.com/wkhtmltopdf/wkhtmltopdf/issues/3001) for a very long read of the problems faced. This was the direct motivation to create a [separate packaging repository](https://github.com/wkhtmltopdf/packaging).
-* **incompatible libc**: not every distribution has the same glibc version. If you compile with a later version, it won't work on a distro which uses an older version. This was worked around earlier by using CentOS 6 (which had an old enough glibc version). But due to the rise of Docker, the `alpine` image became very popular. This doesn't use glibc at all, but the musl libc. So the generic binaries never really worked on Alpine.
+* **different OpenSSL versions**: due to OpenSSL having a bad track record then (_it's better now_), distributions started aggressively upgrading their OpenSSL version and disabling unused parts of the library. This led to a situation where there was effectively zero backward compatibility and things started breaking randomly -- see [#3001](https://github.com/wkhtmltopdf/wkhtmltopdf/issues/3001) for a very long read of the problems faced. This was the direct motivation to create a [separate packaging repository](https://github.com/wkhtmltopdf/packaging).
+* **incompatible libc**: not every distribution has the same glibc version. If you compile with a later version, it won't work on a distribution which uses an older version. This was worked around earlier by using CentOS 6 (which had an old enough glibc version). But due to the rise of Docker, the `alpine` image became very popular. This doesn't use glibc at all, but the musl libc. So the generic binaries never really worked on Alpine.
 
 While Python has also tried to do this using [manylinux](https://github.com/pypa/manylinux) -- it doesn't always work well (e.g. `alpine` is _not_ recommended with binary wheels if you google for it), and requires you to statically link everything. This may work for them, but wkhtmltopdf also depends on the runtime configuration on actual fonts installed (i.e. `fontconfig` and `freetype2`). It's not possible to abstract everything out and test/fix everything for every OS/distribution with the limited resources this project has -- it makes more sense to make distribution-specific versions which are almost guaranteed to work, as they use the specific versions that the distribution has packaged.
 
@@ -367,7 +367,6 @@ If the distribution you are using is listed:
   * but not the specific patch release -- try it, as it's very likely to work regardless.
   * the major release isn't listed -- we only support LTS versions, so try a LTS version older than your release.
   * cannot install package -- you can always extract it (google for `extract from <format>`), but you'll need to have the dependencies installed.
-* I cannot If the distribution you are using is listed, but not the specific patch release -- try it, as it's very likely to work regardless.
 
 Head over to the [packaging repository](https://github.com/wkhtmltopdf/packaging) and start a discussion if your platform isn't listed.