| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=9a55cb
|
|
CLUSTER_UNTESTED
|
|
0xFFFFFFFF is used in a calculation to see how close we are to the 4G limit in
a tiff file. Problem was this was cast as a long which, in a 32 bit
system ends up being -1.
|
|
As of commit d0371d9 the actual device parameter was changed to be an int.
This change detects if it is defined as a boolean and sets it to 1 if so.
|
|
The previous commit for PDF/A prcoessing did not properly check the PDF/A
level in the PostScript handlers, and treated any setting as being PDF/A.
In fact only settings greater than 0 shuold be checked, 0 means 'not PDF/A'
Add code in gdev_pdf_put_params to ensure that PDFA has a permitted value
(0->2) and signal rangecheck if not.
No differences expected.
|
|
This is the first part of making it possible to produce PDF/A-2b output from
pdfwrite.
The PDFA switch has changed from a boolean to an integer, where the value gives
the level of PDF/A compatibility. This has knock-on effects throughout the
C and PostScript code which has been revised to expect an integer instead
of boolean value.
When PDFA has the value 2 we no longer flatten transparency, and we write
'2' in the pdfaid field in the XMP metadata.
PDF/A-1b output still seems to work correctly, but it is unlikely that the
work so far is sufficient for correct PDF/A-2 output.
No differences expected as the cluster does not test PDF/A output.
|
|
Implement a missing case of Luratech JPX with components > 1, and
bps < 8. Also fix incorrect bit shift calculation in OpenJpeg
part.
|
|
This reverts commit 93bf2df8f6a6b2ed60a8c3f5037865b8646243db.
|
|
|
|
separations.
Previous to this commit the tiffsep device would always write out
an uncompressed composite file; the separation files were lzw
compressed by default and this could be changed via the -sCompression=
option. Now the compression of the composite file is the same as
that of the separation files.
Fixes Bug 692907.
|
|
HPGL handles paths slightly differently to the postscript imaging model.
When a path is filled, successive moveto's are treated as linetos.
(i.e. the 'place we close the path to' is left at the first moveto,
and the area remains fillable). Stroking is unaffected however.
To model this in Ghostscript we add a new path segment type 's_gap'.
The filling code treats this as a lineto. The stroking code is updated
to not stroke such edges (and not to break the subpath at this point).
We add a new parameter to the imager state (hpgl_fill_mode), new
accessor functions (gs_sethpglfillmode, gs_currenthpglfillmode),
and new postscript operators (.sethpglfillmode and .currenthpglfillmode).
If hpgl fill mode is set to a non-zero value, then path construction
treats movetos in an open subpath as gaptos.
Still to do:
* Double check the output from this code matches HPGL.
* Update the clist code to send hpgl fill mode changes.
* Update PDF write to spot such paths and to convert them as
appropriate when writing out.
|
|
Committed before VS had saved out. Sorry.
CLUSTER_UNTESTED.
|
|
Bring in Memento from MuPDF (where it has had some more tweaks
added). Fix the nested display code. Add hack to ignore prev/next
pointers in chunk blocks.
CLUSTER_UNTESTED.
|
|
Windows makefiles were failing to pass the MEMENTO flag down due
to some makefile wackiness.
CLUSTER_UNTESTED.
|
|
Bug #692884 "Empty Spotcolor Name in generated PDF"
The ink name wasn't being marked as 'in use' by the colour space structure
and so was being freed by a garbage collection, resulting in an empty name.
Robin Watts supplied this patch which allows us to *much* more easily mark
names as in use, and also kindly updated the colour handling as well.
No differences expected.
|
|
the imager state.
|
|
No difference to builds, but may make intellisense work better
for Memento builds.
|
|
Cope with -r command. Add /Q flag to erase call (so it doesn't prompt
before deleting).
|
|
From investigations of a problem reported by customer 532.
When imaging a cached glyph, if the glyph bitmap cannot be inserted into the
clist tile cache, we'd normally resort to degenerating the glyph bitmap into
rectangles, and writing those to the clist. When the glyph is filled with a
tiling (Type 1) pattern, this means going through the pattern tiling code.
The problem is when transparency is involved (i.e. if the pattern is in a trans
group, or contains a transparency group) the tiling code cannot reliably
degerate to rectangles at this stage. This usually just works due to the various
fallbacks in the clist writing code and the glyph imaging code, but
occasionally glyphs can either disappear, or other problems occur.
This change makes us use that "fallback" route for all glyphs when we're
filling a glyph with a type 1 pattern, with transprency involved and we're
writing to a clist device.
NOTE: this is analogous to what the FAPI does in similar circumstances for
uncached glyphs.
No cluster differences.
|
|
e954dd4683c35dbd66de3e045d979ebbf20c4d72
Henry pointed out that my e954dd4683c35dbd66de3e045d979ebbf20c4d72
fix was incomplete; this commit replaces the remaining max_long
references with 2^32-1.
|
|
|
|
The TIFF spec limits files to 4 Gigs. The code to detect attempts
to write files that were larger than this in gdevtsep.c was broken
on systems were a long != 32 bit.
Fixes Bug 692896.
|
|
If the user params end up getting set during a vmreclaim
while we are in a swapped icc profile situation when
processing a softmask we were ending up freeing profiles
that should not have been freed. This issue was masked
by a check that was disallowing profiling settings in
the manager once they were already set. Also discovered
issues with a corner case where we have a softmask that
includes a pattern with a softmask.
|
|
When resetting the hpgl/2 page parameters we were setting scaling to
its default value overriding any setting in the PCL job. HP does not
reset the scaling as might be expected.
|
|
This is a case of the current code emulating undocumented behavior
incorrectly. It appears the HP printers resets the print direction
upon receiving a new page size command. Previously we tried to emulate
this by not resetting the logical page orientation which is incorrect
but happened to print the tests we had correctly.
|
|
|
|
Improve the distclean target so that the Memento obj and bin directory
contents are deleted and also remove the debug, pg, memento, and
production obj and bin directories.
|
|
When linking with a shared libjpeg library, don't include the non-public
libjpeg API hack to replace it's low level memory manager with Ghostscript's.
But still do so when using our "local" libjpeg source.
No cluster differences.
|
|
...so it uses the $(D_) and $(_D_) variables instead of -D directly.
No cluster differences.
|
|
Bug #692629. PCL TrueType fonts are missing some important tables for the
purposes of pdfwrite. In particular the CMAP table, which makes it impossible
to create glyph names.
This causes an error which *should* have resulted in pdfwrite falling back to
bitmaps. In the case of a single glyph, or a string where the fiirst glyph fails,
this did work correctly, but when one or more initial glyphs did work, the
calling code did not expect an error from TrueType fonts and failed to cope
properly by continuing to process the remaining glyphs.
Added TrueType fonts to the list which may error in this fashion.
Expected Differences:
AS40AOJ3.BIN
LW97DOJ2.BIN
SW108OJ2.BIN
VerdanaItalic.prn
bug689100.xl
bug689905.xl
All exhibit significant progressions (text was previously missing)
|
|
Slight revision to the previous change, again from jrnieder@gmail.com.
CLUSTER_UNTESTED
|
|
patch courtesy of Jonathan Nieder ( jrnieder@gmail.com ).
CLUSTER_UNTESTED
|
|
This reverts commit 43f3cdae4bdf00c09fdd69c53c03fb99d0b4aca1.
This caused unexpected changes in many postscript files. Reverting
until I can figure out why.
|
|
The XMP metadata Modification date was being written using the Creation
date instead of the Modification date.
No differences expected, metadata is not checked by regression tests
|
|
|
|
HPGL handles paths slightly differently to the postscript imaging model.
When a path is filled, successive moveto's are treated as linetos.
(i.e. the 'place we close the path to' is left at the first moveto,
and the area remains fillable). Stroking is unaffected however.
To model this in Ghostscript we add a new path segment type 's_gap'.
The filling code treats this as a lineto. The stroking code is updated
to not stroke such edges (and not to break the subpath at this point).
We add a new parameter to the imager state (hpgl_path_mode), new
accessor functions (gs_sethpglpathmode, gs_currenthpglpathmode),
and new postscript operators (.sethpglpathmode and .currenthpglpathmode).
If hpgl path mode is set to a non-zero value, then path construction
treats movetos in an open subpath as gaptos.
Still to do:
* Update PDF write to spot such paths and to convert them as
appropriate when writing out.
|
|
The code that set the system/user params related to ICC profiles was
contained in the zusparam.c file. This file is not used with the
other languages (e.g. xps and pcl). The functions that do the actual
work have been moved to gsicc_manage reducing any code duplication for
the other languages.
|
|
Improve the revision 3de55841eefb38c751772ac767c5abab155d7d91.
Convert Type 4 images with invalid /Mask attribute to Type 1
images. Previous version used the mask [1 0] in such cases,
which was not compatible with pdfwrite.
|
|
The flags used for the Windows display device were incorrect and caused
at least some rasterops not to display correctly.
No expetced differences, the display device, and Windows builds, are not
cluster tested.
|
|
Add a new form of -I option similar to -o, where the directory list
is taken from the next parameter. This form is more convenient to use
on UN*X command line with tilda expansion.
|
|
Run l, c, v, y in a stopped context. When they fail (presumably
with /nocurrentpoint), ignore the operator and continue.
|
|
The XPS interpreter was still using Device color spaces for its default
color spaces. This fix has it use ICC color spaces by default which
is required by the spec. This revealed an issue with the color space
handling of the opacity masks. These were getting drawn in sRGB color
space but the transparency group is linear gray. Since we are drawing
the opacity mask as a luminosity mask that is gray we ended up
mapping through a nonlinearity.
|
|
Reject setcachedevice arguments that are too big and, probably, invalid.
The threshold, 32000, is arbitrary. Normal fonts have the values about 1000.
|
|
Enumerate PDF subfiles in PDF collection (=portfolio) and apply
the old pdf_info.ps to every component.
|
|
Fix packing of multi-component color values with bps < 8 into the
output stream. This results in progressions on Bug691843.pdf, and
minor differences in Bug690147.pdf
|
|
Thanks to Peter Skarpetis for finding this.
|
|
Following AR9 implementation, add special processing for
repairing a broken /Mask attribute of 1 bpc indexed images.
Ignore the whole Mask if its first element is out of range.
Replace the second component with 1 when it's out of range.
|
|
|
|
The image code makes a call to 'image_render' for each line of the Height. This defeats the joining
of any same color pixels into a larger rectangle and also creates extra overhead. Problem analyzed
with profiles from cust 532 file "PWTTQ1CC.pdf". Regression testing shows some single pixel differences
presumably due to rounding, but no obvious problems.
|
