1994-09-24 00:00:00 +00:00
|
|
|
/*
|
|
|
|
|
* cderror.h
|
|
|
|
|
*
|
2021-01-14 18:35:15 -06:00
|
|
|
* This file was part of the Independent JPEG Group's software:
|
1998-03-27 00:00:00 +00:00
|
|
|
* Copyright (C) 1994-1997, Thomas G. Lane.
|
2018-07-20 17:21:36 -05:00
|
|
|
* Modified 2009-2017 by Guido Vollbeding.
|
2021-01-14 18:35:15 -06:00
|
|
|
* libjpeg-turbo Modifications:
|
2024-06-21 10:58:17 -04:00
|
|
|
* Copyright (C) 2021, 2024, D. R. Commander.
|
2015-10-10 10:25:46 -05:00
|
|
|
* For conditions of distribution and use, see the accompanying README.ijg
|
|
|
|
|
* file.
|
1994-09-24 00:00:00 +00:00
|
|
|
*
|
|
|
|
|
* This file defines the error and message codes for the cjpeg/djpeg
|
|
|
|
|
* applications. These strings are not needed as part of the JPEG library
|
|
|
|
|
* proper.
|
|
|
|
|
* Edit this file to add new codes, or to translate the message strings to
|
|
|
|
|
* some other language.
|
|
|
|
|
*/
|
|
|
|
|
|
1994-12-07 00:00:00 +00:00
|
|
|
/*
|
|
|
|
|
* To define the enum list of message codes, include this file without
|
|
|
|
|
* defining macro JMESSAGE. To create a message string table, include it
|
|
|
|
|
* again with a suitable JMESSAGE definition (see jerror.c for an example).
|
1994-09-24 00:00:00 +00:00
|
|
|
*/
|
1994-12-07 00:00:00 +00:00
|
|
|
#ifndef JMESSAGE
|
|
|
|
|
#ifndef CDERROR_H
|
|
|
|
|
#define CDERROR_H
|
|
|
|
|
/* First time through, define the enum list */
|
|
|
|
|
#define JMAKE_ENUM_LIST
|
|
|
|
|
#else
|
|
|
|
|
/* Repeated inclusions of this file are no-ops unless JMESSAGE is defined */
|
Improve code formatting consistency
With rare exceptions ...
- Always separate line continuation characters by one space from
preceding code.
- Always use two-space indentation. Never use tabs.
- Always use K&R-style conditional blocks.
- Always surround operators with spaces, except in raw assembly code.
- Always put a space after, but not before, a comma.
- Never put a space between type casts and variables/function calls.
- Never put a space between the function name and the argument list in
function declarations and prototypes.
- Always surround braces ('{' and '}') with spaces.
- Always surround statements (if, for, else, catch, while, do, switch)
with spaces.
- Always attach pointer symbols ('*' and '**') to the variable or
function name.
- Always precede pointer symbols ('*' and '**') by a space in type
casts.
- Use the MIN() macro from jpegint.h within the libjpeg and TurboJPEG
API libraries (using min() from tjutil.h is still necessary for
TJBench.)
- Where it makes sense (particularly in the TurboJPEG code), put a blank
line after variable declaration blocks.
- Always separate statements in one-liners by two spaces.
The purpose of this was to ease maintenance on my part and also to make
it easier for contributors to figure out how to format patch
submissions. This was admittedly confusing (even to me sometimes) when
we had 3 or 4 different style conventions in the same source tree. The
new convention is more consistent with the formatting of other OSS code
bases.
This commit corrects deviations from the chosen formatting style in the
libjpeg API code and reformats the TurboJPEG API code such that it
conforms to the same standard.
NOTES:
- Although it is no longer necessary for the function name in function
declarations to begin in Column 1 (this was historically necessary
because of the ansi2knr utility, which allowed libjpeg to be built
with non-ANSI compilers), we retain that formatting for the libjpeg
code because it improves readability when using libjpeg's function
attribute macros (GLOBAL(), etc.)
- This reformatting project was accomplished with the help of AStyle and
Uncrustify, although neither was completely up to the task, and thus
a great deal of manual tweaking was required. Note to developers of
code formatting utilities: the libjpeg-turbo code base is an
excellent test bed, because AFAICT, it breaks every single one of the
utilities that are currently available.
- The legacy (MMX, SSE, 3DNow!) assembly code for i386 has been
formatted to match the SSE2 code (refer to
ff5685d5344273df321eb63a005eaae19d2496e3.) I hadn't intended to
bother with this, but the Loongson MMI implementation demonstrated
that there is still academic value to the MMX implementation, as an
algorithmic model for other 64-bit vector implementations. Thus, it
is desirable to improve its readability in the same manner as that of
the SSE2 implementation.
2018-03-08 10:55:20 -06:00
|
|
|
#define JMESSAGE(code, string)
|
1994-12-07 00:00:00 +00:00
|
|
|
#endif /* CDERROR_H */
|
|
|
|
|
#endif /* JMESSAGE */
|
1994-09-24 00:00:00 +00:00
|
|
|
|
1994-12-07 00:00:00 +00:00
|
|
|
#ifdef JMAKE_ENUM_LIST
|
1994-09-24 00:00:00 +00:00
|
|
|
|
|
|
|
|
typedef enum {
|
|
|
|
|
|
Improve code formatting consistency
With rare exceptions ...
- Always separate line continuation characters by one space from
preceding code.
- Always use two-space indentation. Never use tabs.
- Always use K&R-style conditional blocks.
- Always surround operators with spaces, except in raw assembly code.
- Always put a space after, but not before, a comma.
- Never put a space between type casts and variables/function calls.
- Never put a space between the function name and the argument list in
function declarations and prototypes.
- Always surround braces ('{' and '}') with spaces.
- Always surround statements (if, for, else, catch, while, do, switch)
with spaces.
- Always attach pointer symbols ('*' and '**') to the variable or
function name.
- Always precede pointer symbols ('*' and '**') by a space in type
casts.
- Use the MIN() macro from jpegint.h within the libjpeg and TurboJPEG
API libraries (using min() from tjutil.h is still necessary for
TJBench.)
- Where it makes sense (particularly in the TurboJPEG code), put a blank
line after variable declaration blocks.
- Always separate statements in one-liners by two spaces.
The purpose of this was to ease maintenance on my part and also to make
it easier for contributors to figure out how to format patch
submissions. This was admittedly confusing (even to me sometimes) when
we had 3 or 4 different style conventions in the same source tree. The
new convention is more consistent with the formatting of other OSS code
bases.
This commit corrects deviations from the chosen formatting style in the
libjpeg API code and reformats the TurboJPEG API code such that it
conforms to the same standard.
NOTES:
- Although it is no longer necessary for the function name in function
declarations to begin in Column 1 (this was historically necessary
because of the ansi2knr utility, which allowed libjpeg to be built
with non-ANSI compilers), we retain that formatting for the libjpeg
code because it improves readability when using libjpeg's function
attribute macros (GLOBAL(), etc.)
- This reformatting project was accomplished with the help of AStyle and
Uncrustify, although neither was completely up to the task, and thus
a great deal of manual tweaking was required. Note to developers of
code formatting utilities: the libjpeg-turbo code base is an
excellent test bed, because AFAICT, it breaks every single one of the
utilities that are currently available.
- The legacy (MMX, SSE, 3DNow!) assembly code for i386 has been
formatted to match the SSE2 code (refer to
ff5685d5344273df321eb63a005eaae19d2496e3.) I hadn't intended to
bother with this, but the Loongson MMI implementation demonstrated
that there is still academic value to the MMX implementation, as an
algorithmic model for other 64-bit vector implementations. Thus, it
is desirable to improve its readability in the same manner as that of
the SSE2 implementation.
2018-03-08 10:55:20 -06:00
|
|
|
#define JMESSAGE(code, string) code,
|
1994-09-24 00:00:00 +00:00
|
|
|
|
1994-12-07 00:00:00 +00:00
|
|
|
#endif /* JMAKE_ENUM_LIST */
|
1994-09-24 00:00:00 +00:00
|
|
|
|
Improve code formatting consistency
With rare exceptions ...
- Always separate line continuation characters by one space from
preceding code.
- Always use two-space indentation. Never use tabs.
- Always use K&R-style conditional blocks.
- Always surround operators with spaces, except in raw assembly code.
- Always put a space after, but not before, a comma.
- Never put a space between type casts and variables/function calls.
- Never put a space between the function name and the argument list in
function declarations and prototypes.
- Always surround braces ('{' and '}') with spaces.
- Always surround statements (if, for, else, catch, while, do, switch)
with spaces.
- Always attach pointer symbols ('*' and '**') to the variable or
function name.
- Always precede pointer symbols ('*' and '**') by a space in type
casts.
- Use the MIN() macro from jpegint.h within the libjpeg and TurboJPEG
API libraries (using min() from tjutil.h is still necessary for
TJBench.)
- Where it makes sense (particularly in the TurboJPEG code), put a blank
line after variable declaration blocks.
- Always separate statements in one-liners by two spaces.
The purpose of this was to ease maintenance on my part and also to make
it easier for contributors to figure out how to format patch
submissions. This was admittedly confusing (even to me sometimes) when
we had 3 or 4 different style conventions in the same source tree. The
new convention is more consistent with the formatting of other OSS code
bases.
This commit corrects deviations from the chosen formatting style in the
libjpeg API code and reformats the TurboJPEG API code such that it
conforms to the same standard.
NOTES:
- Although it is no longer necessary for the function name in function
declarations to begin in Column 1 (this was historically necessary
because of the ansi2knr utility, which allowed libjpeg to be built
with non-ANSI compilers), we retain that formatting for the libjpeg
code because it improves readability when using libjpeg's function
attribute macros (GLOBAL(), etc.)
- This reformatting project was accomplished with the help of AStyle and
Uncrustify, although neither was completely up to the task, and thus
a great deal of manual tweaking was required. Note to developers of
code formatting utilities: the libjpeg-turbo code base is an
excellent test bed, because AFAICT, it breaks every single one of the
utilities that are currently available.
- The legacy (MMX, SSE, 3DNow!) assembly code for i386 has been
formatted to match the SSE2 code (refer to
ff5685d5344273df321eb63a005eaae19d2496e3.) I hadn't intended to
bother with this, but the Loongson MMI implementation demonstrated
that there is still academic value to the MMX implementation, as an
algorithmic model for other 64-bit vector implementations. Thus, it
is desirable to improve its readability in the same manner as that of
the SSE2 implementation.
2018-03-08 10:55:20 -06:00
|
|
|
JMESSAGE(JMSG_FIRSTADDONCODE = 1000, NULL) /* Must be first entry! */
|
1994-09-24 00:00:00 +00:00
|
|
|
|
|
|
|
|
JMESSAGE(JERR_BMP_BADCMAP, "Unsupported BMP colormap format")
|
2018-01-14 00:00:00 +00:00
|
|
|
JMESSAGE(JERR_BMP_BADDEPTH, "Only 8-, 24-, and 32-bit BMP files are supported")
|
1994-09-24 00:00:00 +00:00
|
|
|
JMESSAGE(JERR_BMP_BADHEADER, "Invalid BMP file: bad header length")
|
|
|
|
|
JMESSAGE(JERR_BMP_BADPLANES, "Invalid BMP file: biPlanes not equal to 1")
|
|
|
|
|
JMESSAGE(JERR_BMP_COLORSPACE, "BMP output must be grayscale or RGB")
|
|
|
|
|
JMESSAGE(JERR_BMP_COMPRESSED, "Sorry, compressed BMPs not yet supported")
|
2010-01-10 00:00:00 +00:00
|
|
|
JMESSAGE(JERR_BMP_EMPTY, "Empty BMP image")
|
1994-09-24 00:00:00 +00:00
|
|
|
JMESSAGE(JERR_BMP_NOT, "Not a BMP file - does not start with BM")
|
2018-07-20 17:21:36 -05:00
|
|
|
JMESSAGE(JERR_BMP_OUTOFRANGE, "Numeric value out of range in BMP file")
|
2018-01-14 00:00:00 +00:00
|
|
|
JMESSAGE(JTRC_BMP, "%ux%u %d-bit BMP image")
|
1994-09-24 00:00:00 +00:00
|
|
|
JMESSAGE(JTRC_BMP_MAPPED, "%ux%u 8-bit colormapped BMP image")
|
2018-01-14 00:00:00 +00:00
|
|
|
JMESSAGE(JTRC_BMP_OS2, "%ux%u %d-bit OS2 BMP image")
|
1994-09-24 00:00:00 +00:00
|
|
|
JMESSAGE(JTRC_BMP_OS2_MAPPED, "%ux%u 8-bit colormapped OS2 BMP image")
|
|
|
|
|
|
|
|
|
|
JMESSAGE(JERR_GIF_BUG, "GIF output got confused")
|
|
|
|
|
JMESSAGE(JERR_GIF_CODESIZE, "Bogus GIF codesize %d")
|
|
|
|
|
JMESSAGE(JERR_GIF_COLORSPACE, "GIF output must be grayscale or RGB")
|
2021-01-14 18:35:15 -06:00
|
|
|
JMESSAGE(JERR_GIF_EMPTY, "Empty GIF image")
|
1994-09-24 00:00:00 +00:00
|
|
|
JMESSAGE(JERR_GIF_IMAGENOTFOUND, "Too few images in GIF file")
|
|
|
|
|
JMESSAGE(JERR_GIF_NOT, "Not a GIF file")
|
|
|
|
|
JMESSAGE(JTRC_GIF, "%ux%ux%d GIF image")
|
|
|
|
|
JMESSAGE(JTRC_GIF_BADVERSION,
|
2014-05-09 18:00:32 +00:00
|
|
|
"Warning: unexpected GIF version number '%c%c%c'")
|
1994-09-24 00:00:00 +00:00
|
|
|
JMESSAGE(JTRC_GIF_EXTENSION, "Ignoring GIF extension block of type 0x%02x")
|
|
|
|
|
JMESSAGE(JTRC_GIF_NONSQUARE, "Caution: nonsquare pixels in input")
|
|
|
|
|
JMESSAGE(JWRN_GIF_BADDATA, "Corrupt data in GIF file")
|
|
|
|
|
JMESSAGE(JWRN_GIF_CHAR, "Bogus char 0x%02x in GIF file, ignoring")
|
|
|
|
|
JMESSAGE(JWRN_GIF_ENDCODE, "Premature end of GIF image")
|
|
|
|
|
JMESSAGE(JWRN_GIF_NOMOREDATA, "Ran out of GIF bits")
|
|
|
|
|
|
|
|
|
|
JMESSAGE(JERR_PPM_COLORSPACE, "PPM output must be grayscale or RGB")
|
|
|
|
|
JMESSAGE(JERR_PPM_NONNUMERIC, "Nonnumeric data in PPM file")
|
1998-03-27 00:00:00 +00:00
|
|
|
JMESSAGE(JERR_PPM_NOT, "Not a PPM/PGM file")
|
2018-07-20 17:21:36 -05:00
|
|
|
JMESSAGE(JERR_PPM_OUTOFRANGE, "Numeric value out of range in PPM file")
|
2024-06-21 10:58:17 -04:00
|
|
|
JMESSAGE(JTRC_PGM, "%ux%u PGM image (maximum color value = %u)")
|
|
|
|
|
JMESSAGE(JTRC_PGM_TEXT, "%ux%u text PGM image (maximum color value = %u)")
|
|
|
|
|
JMESSAGE(JTRC_PPM, "%ux%u PPM image (maximum color value = %u)")
|
|
|
|
|
JMESSAGE(JTRC_PPM_TEXT, "%ux%u text PPM image (maximum color value = %u)")
|
1994-09-24 00:00:00 +00:00
|
|
|
|
|
|
|
|
JMESSAGE(JERR_TGA_BADCMAP, "Unsupported Targa colormap format")
|
|
|
|
|
JMESSAGE(JERR_TGA_BADPARMS, "Invalid or unsupported Targa file")
|
|
|
|
|
JMESSAGE(JERR_TGA_COLORSPACE, "Targa output must be grayscale or RGB")
|
|
|
|
|
JMESSAGE(JTRC_TGA, "%ux%u RGB Targa image")
|
|
|
|
|
JMESSAGE(JTRC_TGA_GRAY, "%ux%u grayscale Targa image")
|
|
|
|
|
JMESSAGE(JTRC_TGA_MAPPED, "%ux%u colormapped Targa image")
|
|
|
|
|
JMESSAGE(JERR_TGA_NOTCOMP, "Targa support was not compiled")
|
|
|
|
|
|
|
|
|
|
JMESSAGE(JERR_BAD_CMAP_FILE,
|
2014-05-09 18:00:32 +00:00
|
|
|
"Color map file is invalid or of unsupported format")
|
1994-09-24 00:00:00 +00:00
|
|
|
JMESSAGE(JERR_TOO_MANY_COLORS,
|
2014-05-09 18:00:32 +00:00
|
|
|
"Output file format cannot handle %d colormap entries")
|
1994-09-24 00:00:00 +00:00
|
|
|
JMESSAGE(JERR_UNGETC_FAILED, "ungetc failed")
|
|
|
|
|
#ifdef TARGA_SUPPORTED
|
|
|
|
|
JMESSAGE(JERR_UNKNOWN_FORMAT,
|
2014-05-09 18:00:32 +00:00
|
|
|
"Unrecognized input file format --- perhaps you need -targa")
|
1994-09-24 00:00:00 +00:00
|
|
|
#else
|
|
|
|
|
JMESSAGE(JERR_UNKNOWN_FORMAT, "Unrecognized input file format")
|
|
|
|
|
#endif
|
|
|
|
|
JMESSAGE(JERR_UNSUPPORTED_FORMAT, "Unsupported output file format")
|
|
|
|
|
|
1994-12-07 00:00:00 +00:00
|
|
|
#ifdef JMAKE_ENUM_LIST
|
1994-09-24 00:00:00 +00:00
|
|
|
|
|
|
|
|
JMSG_LASTADDONCODE
|
|
|
|
|
} ADDON_MESSAGE_CODE;
|
|
|
|
|
|
1994-12-07 00:00:00 +00:00
|
|
|
#undef JMAKE_ENUM_LIST
|
|
|
|
|
#endif /* JMAKE_ENUM_LIST */
|
1994-09-24 00:00:00 +00:00
|
|
|
|
1994-12-07 00:00:00 +00:00
|
|
|
/* Zap JMESSAGE macro so that future re-inclusions do nothing by default */
|
1994-09-24 00:00:00 +00:00
|
|
|
#undef JMESSAGE
|