diff options
author | Glenn Randers-Pehrson <glennrp at users.sourceforge.net> | 2014-10-17 09:54:18 -0500 |
---|---|---|
committer | Glenn Randers-Pehrson <glennrp at users.sourceforge.net> | 2014-10-17 09:55:43 -0500 |
commit | eaad9f91776ed59d2809b2b80b1c5a969cd8277f (patch) | |
tree | fbaa97364f51019b5f93bedf891523c89118008e | |
parent | 70cd1a10f251b515b0948c6f89211538058b7951 (diff) | |
download | libpng-eaad9f91776ed59d2809b2b80b1c5a969cd8277f.tar.gz |
[libpng17] Minor editing of README and comments in example.c and pngtest.c.
-rw-r--r-- | README | 17 | ||||
-rw-r--r-- | example.c | 4 | ||||
-rw-r--r-- | pngtest.c | 2 |
3 files changed, 15 insertions, 8 deletions
@@ -1,4 +1,4 @@ -README for libpng version 1.7.0beta38 - September 28, 2014 (shared library 17.0) +README for libpng version 1.7.0beta38 - October 17, 2014 (shared library 17.0) See the note about version numbers near the top of png.h See INSTALL for instructions on how to install libpng. @@ -30,11 +30,18 @@ png_get_<chunk> functions. These functions should be used when accessing/storing the info_struct data, rather than manipulating it directly, to avoid such problems in the future. -It is important to note that the APIs do not make current programs +It is important to note that the APIs did not make current programs that access the info struct directly incompatible with the new -library. However, it is strongly suggested that new programs use -the new APIs (as shown in example.c and pngtest.c), and older programs -be converted to the new format, to facilitate upgrades in the future. +library, through libpng-1.2.x. In libpng-1.4.x, which was meant to +be a transitional release, members of the png_struct and the +info_struct can still be accessed, but the compiler will issue a +warning about deprecated usage. Since libpng-1.5.0, direct access +to these structs is not allowed, and the definitions of the structs +reside in private pngstruct.h and pnginfo.h header files that are not +accessible to applications. It is strongly suggested that new +programs use the new APIs (as shown in example.c and pngtest.c), and +older programs be converted to the new format, to facilitate upgrades +in the future. **** Additions since 0.90 include the ability to compile libpng as a @@ -188,13 +188,13 @@ int main(int argc, const char **argv) * * Don't repeatedly convert between the 8-bit and 16-bit forms. There is * significant data loss when 16-bit data is converted to the 8-bit encoding and - * the current libpng implementation of convertion to 16-bit is also + * the current libpng implementation of conversion to 16-bit is also * significantly lossy. The latter will be fixed in the future, but the former * is unavoidable - the 8-bit format just doesn't have enough resolution. */ /* If your program needs more information from the PNG data it reads, or if you - * need to do more complex transformations, or minimise transformations, on the + * need to do more complex transformations, or minimize transformations, on the * data you read, then you must use one of the several lower level libpng * interfaces. * @@ -646,7 +646,7 @@ set_location(png_structp png_ptr, struct user_chunk_data *data, int what) if ((data->location[0] & what) || (data->location[1] & what)) return 0; /* already have one of these */ - /* Find where we are (the code below zeros info_ptr to indicate that the + /* Find where we are (the code below zeroes info_ptr to indicate that the * chunks before the first IDAT have been read.) */ if (data->info_ptr == NULL) /* after IDAT */ |