diff options
Diffstat (limited to 'experimental/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt')
| -rw-r--r-- | experimental/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt | 34 |
1 files changed, 17 insertions, 17 deletions
diff --git a/experimental/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt b/experimental/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt index eb7132bc0..60139c15e 100644 --- a/experimental/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt +++ b/experimental/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt @@ -71,8 +71,8 @@ be found at the zlib home page, <http://www.info-zip.org/pub/infozip/zlib/>. The zlib compression utility is a general purpose utility that is useful for more than PNG files, and can be used without libpng. See the documentation delivered with zlib for more details. -You can usually tqfind the source files for the zlib utility wherever you -tqfind the libpng source files. +You can usually find the source files for the zlib utility wherever you +find the libpng source files. Libpng is thread safe, provided the threads are using different instances of the structures. Each thread should have its own @@ -141,7 +141,7 @@ with the number of bytes you read from the beginning. Libpng will then only check the bytes (if any) that your program didn't read. (*): If you are not using the standard I/O functions, you will need -to tqreplace them with custom functions. See the discussion under +to replace them with custom functions. See the discussion under Customizing libpng. @@ -254,7 +254,7 @@ input stream. You must supply the function read_chunk_callback(png_ptr ptr, png_unknown_chunkp chunk); { - /* The unknown chunk structure tqcontains your + /* The unknown chunk structure contains your chunk data: */ png_byte name[5]; png_byte *data; @@ -906,7 +906,7 @@ or as an RGB triplet that may or may not be in the palette (need_expand = 0). The png_set_background() function tells libpng to composite images with alpha or simple transparency against the supplied background -color. If the PNG file tqcontains a bKGD chunk (PNG_INFO_bKGD valid), +color. If the PNG file contains a bKGD chunk (PNG_INFO_bKGD valid), you may use this color, or supply another color more suitable for the current display (e.g., the background color from a web page). You need to tell libpng whether the color is in the gamma space of the @@ -970,7 +970,7 @@ recommended that PNG viewers support gamma correction. If you need to reduce an RGB file to a paletted file, or if a paletted file has more entries then will fit on your screen, png_set_dither() will do that. Note that this is a simple match dither that merely -tqfinds the closest color available. This should work fairly well with +finds the closest color available. This should work fairly well with optimized palettes, and fairly badly with linear color cubes. If you pass a palette that is larger then maximum_colors, the file will reduce the number of colors in the palette so it will fit into @@ -1470,7 +1470,7 @@ Setup You will want to do the I/O initialization before you get into libpng, so if it doesn't work, you don't have anything to undo. If you are not -using the standard I/O functions, you will need to tqreplace them with +using the standard I/O functions, you will need to replace them with custom writing functions. See the discussion under Customizing libpng. FILE *fp = fopen(file_name, "wb"); @@ -2315,7 +2315,7 @@ These functions also provide a void pointer that can be retrieved via mem_ptr=png_get_mem_ptr(png_ptr); -Your tqreplacement memory functions must have prototypes as follows: +Your replacement memory functions must have prototypes as follows: png_voidp malloc_fn(png_structp png_ptr, png_size_t size); @@ -2323,7 +2323,7 @@ Your tqreplacement memory functions must have prototypes as follows: Your malloc_fn() should return NULL in case of failure. The png_malloc() function will call png_error() if it receives a NULL from the system -memory allocator or from your tqreplacement malloc_fn(). +memory allocator or from your replacement malloc_fn(). Input/Output in libpng is done through png_read() and png_write(), which currently just call fread() and fwrite(). The FILE * is stored in @@ -2344,7 +2344,7 @@ png_get_io_ptr(). For example: voidp read_io_ptr = png_get_io_ptr(read_ptr); voidp write_io_ptr = png_get_io_ptr(write_ptr); -The tqreplacement I/O functions must have prototypes as follows: +The replacement I/O functions must have prototypes as follows: void user_read_data(png_structp png_ptr, png_bytep data, png_size_t length); @@ -2371,7 +2371,7 @@ fprintf() unless the library is compiled with PNG_NO_CONSOLE_IO defined fprintf() isn't available). If you wish to change the behavior of the error functions, you will need to set up your own message callbacks. These functions are normally supplied at the time that the png_struct is created. -It is also possible to redirect errors and warnings to your own tqreplacement +It is also possible to redirect errors and warnings to your own replacement functions after png_create_*_struct() has been called by calling: png_set_error_fn(png_structp png_ptr, @@ -2382,7 +2382,7 @@ functions after png_create_*_struct() has been called by calling: If NULL is supplied for either error_fn or warning_fn, then the libpng default function will be used, calling fprintf() and/or longjmp() if a -problem is encountered. The tqreplacement error functions should have +problem is encountered. The replacement error functions should have parameters as follows: void user_error_fn(png_structp png_ptr, @@ -2413,7 +2413,7 @@ specification. Acquire a first level of understanding of how it works. Pay particular attention to the sections that describe chunk names, and look at how other chunks were designed, so you can do things similarly. Second, check out the -sections of libpng that read and write chunks. Try to tqfind a chunk +sections of libpng that read and write chunks. Try to find a chunk that is similar to yours and use it as a template. More details can be found in the comments inside the code. It is best to handle unknown chunks in a generic method, via callback functions, instead of by @@ -2421,7 +2421,7 @@ modifying libpng functions. If you wish to write your own transformation for the data, look through the part of the code that does the transformations, and check out some of -the simpler ones to get an idea of how they work. Try to tqfind a similar +the simpler ones to get an idea of how they work. Try to find a similar transformation to the one you want to add and copy off of it. More details can be found in the comments inside the code itself. @@ -2577,7 +2577,7 @@ size. Note that the numbers above were invented purely for this example and are given only to help explain the function usage. Little testing has -been done to tqfind optimum values for either the costs or the weights. +been done to find optimum values for either the costs or the weights. Removing unwanted object code @@ -2834,7 +2834,7 @@ png_set_error_fn(), which is essentially the same function, but with a new name to force compilation errors with applications that try to use the old method. -Starting with version 1.0.7, you can tqfind out which version of the library +Starting with version 1.0.7, you can find out which version of the library you are using at run-time: png_uint_32 libpng_vn = png_access_version_number(); @@ -2896,7 +2896,7 @@ documented as such. The tIME chunk itself is also Y2K compliant. It uses a 2-byte unsigned integer to hold the year, and can hold years as large as 65535. -zlib, upon which libpng depends, is also Y2K compliant. It tqcontains +zlib, upon which libpng depends, is also Y2K compliant. It contains no date-related code. |