Lines Matching full:may

31 of the downsampled image.  Thus the number of samples may vary across
59 parameter values, some uncommon settings are not yet implemented and may
83 low-quality modes may not meet the JPEG standard's accuracy requirements;
113 this is just an interface to fwrite(), but some applications may need to
122     * Upsampling.  Optionally, this step may be able to do more general
124     * Color space conversion (e.g., YCbCr to RGB).  This step may also
134 There may be several implementations of each of these elements, particularly
151 additional dummy blocks may be used to fill out MCUs, but the MCU assembly and
211 reason for having the class structure is that on different runs we may create
240    module may contain several possible implementations of a particular method,
259 A data buffer control module may itself be viewed as a processing step by a
273   virtual array buffers as needed.  One or both processing steps may be
298 an "object" which may have several different implementations available.  One
318   Optionally may perform pixel-level smoothing as well.  Processes a "row
321   differs across components).  Some downsampling or smoothing algorithms may
361   for other behaviors, the surrounding application may provide its own
368   determines handling of nonfatal errors.  The surrounding application may
377 customization of the JPEG library.  A surrounding application may override
384 decompression; the progress monitor, if used, may be shared as well.
406   may require context rows above and below the current row group; when this
429   When scaled-down output is asked for, simplified DCT algorithms may be used
438 * Upsampling: restores chroma components to full size.  (May support more
453   is not used for full-color output.  Works on one pixel row at a time; may
482   may provide its own source manager.
526 look only at its own variables.  For example, the data output section may not
528 file, because these may change as the data input section advances into a new
578 * The rows forming a component array may be allocated at different times
621 The contents of a coefficient block may be in either "natural" or zigzagged
622 order, and may be true values or divided by the quantization coefficients,
627 (This latter decision may need to be revisited to support variable
639 destination may be a limited-size buffer, and we can't rely on being able to
664 permanent state is updated.  (This copying is not very expensive, and may even
733 2. "Large" objects.  These may require tens to hundreds of K depending on
735    distinguish them because pool allocation heuristics may differ for large and
738    exceed the size allowed by type size_t, which may be 64K or less on some
743    without virtual memory, the rest of the array may be swapped out to a
775   1. Modules must request virtual arrays (which may have only image lifespan)
782 Small objects of any lifespan may be allocated at any time.  We expect that
796 JPEG mode; we may as well make it available for possible other uses.)
799 order; read passes, as well as any write passes after the first one, may
801 the virtual array control logic, and partly because some file systems may not
842 It may be necessary to ensure that backing store objects are explicitly
846 jpeg_destroy) upon abnormal termination.  This may require a SIGINT signal
859 Some JPEG files may use a DNL marker to postpone definition of the image