diff options
author | Lei Zhang <thestig@chromium.org> | 2017-03-20 15:46:06 -0700 |
---|---|---|
committer | Chromium commit bot <commit-bot@chromium.org> | 2017-03-21 13:12:16 +0000 |
commit | cfb6f46473777e444c8124318aa78d33aae64459 (patch) | |
tree | 272d17a7ba02251fd6d62a90c431e5af169af85a /third_party/libtiff/tif_open.c | |
parent | 34a28b470a9a4d7c7edd04e9b6a1e02a7490e58b (diff) | |
download | pdfium-cfb6f46473777e444c8124318aa78d33aae64459.tar.xz |
Upgrade libtiff to 4.0.7.
Change-Id: If3f67767f738b7f23230ca8c37c9af2e31696e82
Reviewed-on: https://pdfium-review.googlesource.com/3117
Commit-Queue: dsinclair <dsinclair@chromium.org>
Reviewed-by: dsinclair <dsinclair@chromium.org>
Diffstat (limited to 'third_party/libtiff/tif_open.c')
-rw-r--r-- | third_party/libtiff/tif_open.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/third_party/libtiff/tif_open.c b/third_party/libtiff/tif_open.c index 8c88328cf2..5c9036e6b4 100644 --- a/third_party/libtiff/tif_open.c +++ b/third_party/libtiff/tif_open.c @@ -1,4 +1,4 @@ -/* $Id: tif_open.c,v 1.46 2010-12-06 16:54:54 faxguy Exp $ */ +/* $Id: tif_open.c,v 1.47 2016-01-23 21:20:34 erouault Exp $ */ /* * Copyright (c) 1988-1997 Sam Leffler @@ -168,7 +168,7 @@ TIFFClientOpen( * The following flags may be used to control intrinsic library * behaviour that may or may not be desirable (usually for * compatibility with some application that claims to support - * TIFF but only supports some braindead idea of what the + * TIFF but only supports some brain dead idea of what the * vendor thinks TIFF is): * * 'l' use little-endian byte order for creating a file @@ -198,8 +198,8 @@ TIFFClientOpen( * The 'L', 'B', and 'H' flags are intended for applications * that can optimize operations on data by using a particular * bit order. By default the library returns data in MSB2LSB - * bit order for compatibiltiy with older versions of this - * library. Returning data in the bit order of the native cpu + * bit order for compatibility with older versions of this + * library. Returning data in the bit order of the native CPU * makes the most sense but also requires applications to check * the value of the FillOrder tag; something they probably do * not do right now. |