Lines Matching full:chunk
269 png_unknown_chunkp chunk);
271 /* The unknown chunk structure contains your
272 chunk data, along with similar data for any other
282 /* put your code here. Search for your chunk in the
283 unknown chunk structure, process it, and return one
286 return (-n); /* chunk had an error */
326 Unknown-chunk handling
333 chunk types. To change this, you can call:
337 keep - 0: default unknown chunk handling
347 five bytes per chunk, NULL or '\0' if
354 list of png_unknown_chunk structures. If a chunk that is normally
356 according to the "keep" directive. If a chunk is named in successive
362 where the private "vpAg" chunk will later be processed by a user chunk
522 in until png_read_end() has read the chunk data following the image.
609 These are also important, but their validity depends on whether the chunk
610 has been read. The png_get_valid(png_ptr, info_ptr, PNG_INFO_<chunk>) and
611 png_get_<chunk>(png_ptr, info_ptr, ...) functions return non-zero if the
613 png_get_<chunk> are set directly if they are simple data types, or a
628 The presence of the sRGB chunk
630 sRGB color space. This chunk also
700 when the library is built with iTXt chunk support.
753 unknowns[i].name - name of unknown chunk
754 unknowns[i].data - data of unknown chunk
755 unknowns[i].size - size of unknown chunk's data
756 unknowns[i].location - position of chunk in file
762 The data from the pHYs chunk can be retrieved in several convenient
784 The data from the oFFs chunk can be retrieved in several convenient
794 chunk is present but the unit is the pixel)
797 PNG specification for chunk contents. Be careful with trusting
803 keyword/text pairs, one pair per chunk, with no limit on the number
839 chunk, so this is what libpng expects for this data. The colors are
860 transparency information in a tRNS chunk. This is most useful on
885 the tRNS chunk is present, A means an alpha channel is present, and O
935 alpha channel (or the tRNS chunk data) after it's read, so that 0 is
947 If you do this, any input with a tRNS chunk will be expanded to
1089 color. If the PNG file contains a bKGD chunk (PNG_INFO_bKGD valid),
1094 (PNG_BACKGROUND_GAMMA_FILE for colors from the bKGD chunk), or one
1262 are allocating one large chunk, you will need to build an
1302 If the file is interlaced (interlace_type != 0 in the IHDR chunk), things
1453 it frees. If you need to turn the flag off for a chunk that was freed by
1547 /* This one's new also. Simply give it a chunk
1631 will usually have the same info chunk as you
1815 chunk (as of PNG Specification 1.2, anyway). See png_write_end() and
1887 the sRGB chunk means that the pixel
1889 This chunk also implies specific
1906 sRGB chunk means that the pixel
1976 when the library is built with iTXt chunk support.
2021 unknowns[i].name - name of unknown chunk
2022 unknowns[i].data - data of unknown chunk
2023 unknowns[i].size - size of unknown chunk's data
2024 unknowns[i].location - position to write chunk in file
2025 0: do not write chunk
2036 the chunk was either read from the input file or defined with
2105 use a plain tEXt chunk with the "Creation Time" keyword. This is
2111 tEXt chunk use RFC 1123 format dates (e.g. "22 May 1997 18:07:10 GMT"),
2112 although this isn't a requirement. Unlike the tIME chunk, the
2113 "Creation Time" tEXt chunk is not expected to be automatically changed
2121 for writing. You give it a chunk name, raw data, and a size; that's
2124 Any chunks previously read into the info structure's unknown-chunk
2192 chunk data has to be inverted before the tRNS chunk is written. If
2198 If you need to write a private chunk that you want to appear before
2199 the PLTE chunk when PLTE is present, you can write the PNG info in
2200 two steps, and insert code to write your own chunk between them:
2235 data is of another bit depth, you can write an sBIT chunk into the
2622 chunk and existing `intrinsic' chunks.
2624 If you need to write a new intrinsic chunk, first read the PNG
2626 Pay particular attention to the sections that describe chunk names,
2629 write chunks. Try to find a chunk that is similar to yours and use
2804 You can also turn all of the transforms and ancillary chunk capabilities
2951 Support for the iTXt chunk has been enabled by default as of
2974 tRNS chunk to alpha. The png_set_gray_1_2_4_to_8() function is
3225 The tIME chunk itself is also Y2K compliant. It uses a 2-byte unsigned
