| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
We decided to follow the ObjectFilter subclass device's naming convention
for objects that are not Image or Text. This patch makes them all the same.
NOTE: The GS9_Color_Management.pdf document also needs to change since we
are changing the external names as well. Before going 'live' with this non-
backward compatible change (admittedly to something that has probably not
been widely used) we may consider issuing a warning for the previous option
names, or even a warning with automatic use of the new name.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 14c70d4e9 was, unfortunately, insufficient for the new PDF
interpreter. The gs_lib_ctx pointer does not give us access back to the
interpreter context, only to the *PostScript* interpreter name table.
So instead we now pass a graphics state pointer to
gs_get_colorname_string(). This is only used for halftones currently,
and even future use seems likely to be limited to objects like colour
spaces, which are of course contained in a graphics state, so this
seems relatviely future proof.
For PostScript the graphics state contains a memory_t pointer which we
can use to get to the PostScript name table. For the PDF interpreter
we already store some state in the 'client_data' of the graphics state
and we will extend that to include a pointer to the interpreter context
which will allow us to get the string from its name table.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This function is supplied to a couple of places, and stored. Its
purpose is to retrieve a string for a colour plane, given an 'index'.
The index is an entry in the interpreter's name table.
The implementations of get_colorname_string take a memory_t pointer
and then use that to get a pointer to the interpreter, which they need
because the interpreter context is where the name table is stored.
The problem with the existing usage is that we were supplying the
device's memory_t pointer. However, if the halftone or colour space had
been created by a different interpreter to the device (which can happen
if we are running the PDF interpreter inside the PostScript interpreter)
then the interpreter context would be incorrect.
We can solve this easily enough by using the colour space or halftone
memory pointer. This is much safer since we can reasonably assume that
the interpreter which created the object is the same one which stored
the colour name in its name table.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change how gstate initialisation is done:
Previously we relied on the imager state being a subset of the gstate (thus
assigning an imager state to a graphics state over wrote to the entries
common to both, and didn't overwrite any already set graphics state specific
entries).
Making the imager and graphics states the same means that approach doesn't work,
so this changes it to initialise the entries individually.
Renames gsistate.c->gsgstate.c and gxistate.h->gxgstate.h
Cleanup and fix the gs_state gc stuff.
Uses different check for pre/post clist pdf14 device
Previously, the code used "is_gstate" in the imager/graphics state object
to determine if the code was being called pre or post clist (post clist would
only ever have had an imager_state so is_gstate = false).
With no imager state any more, that test would no longer work (and I am dubious
about whether it was really safe, anyway). Other places check for the presence
of a clist reader device in the pdf14 device structure - so use that here
too.
Adds initial (NULL) value for show_gstate pointer in gs_state.
Removes the now pointless macro for the contents of the graphics state
Changes function names that had "imager" to use "gstate"
Removes the redundant 'is_state' flag
Cleans up gs_(g)state_putdeviceparams():
Previously we had to similar routines: one took a graphics state, and used the
device from the graphics state, the other took an imager state and the device
as an explicit parameter.
With the removal of the imager state, "merge" those two functions
Replaces gs_state with gs_gstate
It makes for less confusion as it really is a g(raphics)state
|
|
|
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.
|
