| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A lot of the FAPI methods made no account for errors (i.e. a call to return an
unsigned 16 bit value would return an unsigned short int). In various places
that meant we ended up using unlikely (in practice, impossible, yet still
"valid") values to indicate an error condition.
This commit changes those calls to have a conventional Ghostscript "int"
return value and (mostly) take pointer to the storage into which they should
write their value. We can now return meaninful error codes.
Secondly, in several places, the FAPI methods and code used integers to store
character codes, cids, gids etc. This is less than ideal because we potentially
have to handle 4 byte codes (especially for gids), and we also use some
special 64 bit values (when available) for specific meanings. There were
several workarounds for that, in various places.
This commit also changes the FAPI API and code to the gs_glyph type for all
such values, removing the need for those workarounds
|
| |
|
| |
|
|
|
|
|
| |
Fixes:
MEMENTO_FAILAT=22 LD_LIBRARY_PATH=../libbacktrace/.libs ./membin/gpdl -sDEVICE=bit -o /dev/null examples/tiger.eps
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The FAPI API didn't really handle the possibility that multiple master fonts
could change (via setweightvector) without a call to definefont/setfont etc.
We now allow two ways for FAPI to handle this: if the scaler in force allows it,
we'll set the new weight vector, and carry on as before.
If the scaler does *not* allow us to change the weight vector "on the fly",
we'll destroy the scaler's font object and related data, and recreate it with
the new weight vector in the font dictionary.
|
|
|
|
|
|
|
|
| |
Use a cleaner check to ensure UFST only gets passed Microtype fonts (from .fco
font collections).
Not sure what I was thinking when I wrote the original check, but it was clearly
a bad code day!
|
|
|
|
|
|
|
|
|
| |
Also update copyright dates.
Remove gs_cmdl.ps as we no longer use it, and remove its entry from
psfiles.htm.
Remove xfonts.htm as this feature (xfont support) is long, long gone.
|
|
|
|
|
|
|
| |
cppcheck reckoned the pointer to the memory allocator (cmem) could possibly be
a NULL pointer dereference (in fact, that's not true).
But a simple tweak to how cmem is initialized can prevent the error arising.
|
|
|
|
|
| |
Ensure that we always return_error(gs_error_blah) rather than just
return gs_error_blah.
|
|
|
|
|
|
|
|
| |
The FAPI/UFST code was returning a "limitcheck" error when no glyph raster was
available, when it should have been "unregistered".
This caused problems when I added the return code checks to address some
Coverity warnings.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to limits of the fixed point arithmetic in the UFST, we have to balance
various scale factors at extreme scales (scale matrix, font size, "resolution")
to ensure varaibles don't over/under flow.
It looks like there was a typo, or just a mistake in how two of the factors
were being scaled relative each other which could cause *extremely* small
scale factors to end up as *extremely* large scale factors.
No cluster differences.
|
|
|
|
|
|
|
|
|
|
|
| |
The stream API in GS is defined as *always* opening files in binary mode,
where applicable, so there is no need for the API clients to specify binary
mode.
This is previously been benign, and thus ignored, but reportedly ending up with
a duplicate 'b' character in the mode causes a crash on Windows 10.
No cluster differences.
|
|
Squashed into one commit (see branch for details of the evolution of the
branch).
This brings gpcl6 and gxps into the Ghostscript build system, and a shared
set of graphics library object files for all the interpreters.
Also, brings the same configuration options to the pcl and xps products as we
have for Ghostscript.
|