| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
Spotted by valgrinding the file/command line from bug 704692. Sadly,
this doesn't fix the actual problem though.
|
| |
|
|
|
|
|
|
|
| |
The manufacturer, version and build date entries in the
pl_interp_characteristics_t were never really used except for version, which
was just set to the GS_VERSION.
Remove the pointless entries, and use a more direct approach to version
reporting.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this instance 'RESOURCES' means fonts, macros, symbol sets etc.
This applies to PCL (and maybe others), but not Postscript
resources.
Default (and setting this to 0) gives the behaviour where resources
are never reset based upon job language changes.
Setting this to 1 causes resources to be reset between jobs (whenever
we return to PJL).
Setting this to 2 causes resources to be reset whenever we "change
language". For this setting, we do not count returning to PJL and
reentering the same language as being a language change.
(Includes fixes and code from Henry Stiles).
|
| | |
|
| | |
|
| |
|
|
| |
Never used.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
According to the JBIG2 specification segments numbers are 32 bit unsigned
integer. Previously any segment numbers larger than INT32_MAX would be passed
as negative numbers.
Some parts of the decoder do not yet know, or do not have access to the
currently decoded segment number, and this needs to be specially indicated.
Therefore jbig2dec appropriates the unlikely segment number 0xffffffff to
indicate an unknown segment number.
This is a change of the public API.
|
| |
|
