diff options
| author | Chris Liddell <chris.liddell@artifex.com> | 2012-02-01 10:59:52 +0000 |
|---|---|---|
| committer | Chris Liddell <chris.liddell@artifex.com> | 2012-02-01 11:06:22 +0000 |
| commit | 5f1a49cb3b05b5fed23e7eab99d6e036f16921dd (patch) | |
| tree | de1df2c6f8537da5c422a781b6d2e34dc027031a | |
| parent | ffca2758193c517edf1d20c6af17acd85f8d5f99 (diff) | |
| download | ghostpdl-5f1a49cb3b05b5fed23e7eab99d6e036f16921dd.tar.gz | |
Update docs for 9.05 release candidate.
CLUSTER_UNTESTED
| -rw-r--r-- | gs/doc/History9.htm | 1645 |
1 files changed, 1245 insertions, 400 deletions
diff --git a/gs/doc/History9.htm b/gs/doc/History9.htm index 584ea526e..b2979d190 100644 --- a/gs/doc/History9.htm +++ b/gs/doc/History9.htm @@ -78,9 +78,22 @@ TrueType font to automatically substitute for missing CIDFonts. Whilst it is and most accurate output, the ability to make an automatic substitution will be valuable for those merely viewing or proofing such files. </li> - +<li><p>This release includes support for a proofing ICC profile. The command option +is specified using -sProofProfile=filename. With this option, the color output will +emulate what would be obtained had the source file been rendered on a device defined +by the proofing profile. +(See <a href="GS9_Color_Management.pdf">GS9_Color_Management.pdf</a> for details. +</li> +<li><p>This release includes support for a device link ICC profile. The command option +is specified using -sDeviceLinkProfile=filename. With this option, the device link profile +is added to the end of the link transform from source to destination. In this case, one can +include a command line option like "-sDevice=tiff32nc -sOutputICCProfile=srgb.icc +-sDeviceLinkProfile=linkRGBtoCMYK.icc" and source colors will be mapped through sRGB +and through the device link profile to CMYK values for the device. +(See <a href="GS9_Color_Management.pdf">GS9_Color_Management.pdf</a> for details. +</li> <li><p>Ghostscript now supports "unmanaged color transformations" for source DeviceXXX -colors (in other words, they use a simple conversion, rather than the ICC profile +colors (in other words, they use a simplistic conversion, rather than the ICC profile based color workflow). This is beneficial in uses where performance takes precedence over ultimate color fidelity (the command line parameter -dUseFastColor enables this). </li> @@ -95,13 +108,17 @@ in the output file. </li> <li><p>Ghostscript now ships modified OpenJPEG sources for JPEG2000 decoding (replacing JasPer - although JasPer is still included for this release). Performance, reliability -and memory use whilst decoding JPX streams are all improved +and memory use whilst decoding JPX streams are all improved (in many cases, significantly). </li> -<li><p>jbig2dec now has simple halftone region support +<li><p>jbig2dec now has simple halftone region support. </li> <li><p>The ps2write device has had a large number of output quality and stability improvements. </li> +<li><p>The txtwrite output was modified so that it more closely matches the output from +MuPDF, if requested. Note that the algorithms used by the two products are not +identical and may return slightly differing results. +<br>(See <a href="Devices.htm#TXT">Devices.htm</a> for details) <p> <br> <p>For a list of open issues, or to report problems, @@ -111,6 +128,281 @@ please visit <a href="http://bugs.ghostscript.com/">bugs.ghostscript.com</a>. <p> No recorded incompatible changes. +<h3><a name="9.05_Changelog"></a>Changelog</h3> +<p><strong>2012-01-31 12:55:34 -0800 +</strong> +<br>Michael Vrhel <michael.vrhel@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=ffca2758193c517edf1d20c6af17acd85f8d5f99">ffca2758193c517edf1d20c6af17acd85f8d5f99</a> +<blockquote> +<p> + Device Link and Proof Profile fix<br> +<br> + If a proofing profile or a device link profile are<br> + specified, the link transform is more than likely not going<br> + to be identity. This fix ensures that the transform<br> + is properly applied.<br> +<br> +gs/base/gsicc_cache.c<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-30 15:28:05 -0800 +</strong> +<br>Michael Vrhel <michael.vrhel@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=dbf3d3403bc928c183b0674aa5adbb6263d56e42">dbf3d3403bc928c183b0674aa5adbb6263d56e42</a> +<blockquote> +<p> + Make device link profile work with lcms2. Also update documentation and add error handling.<br> +<br> + The device link profile handling was put in place when we had lcms 1.8 but was not ported<br> + over to the 2.0 interface.<br> +<br> +gs/base/gsicc.c<br> +gs/base/gsicc_lcms2.c<br> +gs/doc/Use.htm<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-31 18:04:01 +0000 +</strong> +<br>Chris Liddell <chris.liddell@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=55049debcc22152c42a62b1fc350eb087125be5a">55049debcc22152c42a62b1fc350eb087125be5a</a> +<blockquote> +<p> + Have gitlog2changelog.py use html code for "quote" char<br> +<br> + CLUSTER_UNTESTED<br> +<br> +gs/toolbin/gitlog2changelog.py<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-31 17:49:42 +0000 +</strong> +<br>Robin Watts <robin.watts@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=6123f6bc89a9c682dd0e0b8cb62d526fdca1b50a">6123f6bc89a9c682dd0e0b8cb62d526fdca1b50a</a> +<blockquote> +<p> + Add new "WhatIsGS.htm" document<br> +<br> + This explains how Ghostscript, GhostPCL, GhostXPS, etc are related.<br> +<br> +gs/doc/Readme.htm<br> +gs/doc/WhatIsGS.htm<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-31 11:26:31 -0500 +</strong> +<br>Alex Cherepanov <alex.cherepanov@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=1216fd5e30a1a09b8b381d4e43d795728a030cc8">1216fd5e30a1a09b8b381d4e43d795728a030cc8</a> +<blockquote> +<p> + Bug 691483: Fix access to PDF collections.<br> +<br> + Fix a bug in enumeration of a name tree that prevented acceaa to some<br> + files in the PDF file collection when the name tree was more than<br> + one level deep.<br> +<br> +gs/Resource/Init/pdf_main.ps<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-31 08:12:14 +0000 +</strong> +<br>Ken Sharp <ken.sharp@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0a549a4395c169a547e95a2905650dbc05388794">0a549a4395c169a547e95a2905650dbc05388794</a> +<blockquote> +<p> + ps2write - silence a benign compiler warning<br> +<br> + Picked up by scan-build; presumably this only gets run for commits, not<br> + for regular cluster tests as it didn't show up previously.<br> +<br> +gs/base/gdevpdfc.c<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-31 12:01:53 +0000 +</strong> +<br>Chris Liddell <chris.liddell@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=4003b18b598c81df02d3d2c043276d54e7de7c6d">4003b18b598c81df02d3d2c043276d54e7de7c6d</a> +<blockquote> +<p> + Have plver.mak use Ghostscript version.mak version number<br> +<br> + No (significant) cluster differences.<br> +<br> +common/msvc_top.mak<br> +pl/pl.mak<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-30 20:39:29 +0000 +</strong> +<br>Chris Liddell <chris.liddell@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=613b796e44ad8e29d9b4f8166a8b19796f1a024c">613b796e44ad8e29d9b4f8166a8b19796f1a024c</a> +<blockquote> +<p> + Change a couple of '&' to &amp;<br> +<br> + CLUSTER_UNTESTED<br> +<br> +gs/doc/History9.htm<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-30 20:26:30 +0000 +</strong> +<br>Chris Liddell <chris.liddell@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=f58e15f60683f2be163e0a64ef1a86141a0d45c3">f58e15f60683f2be163e0a64ef1a86141a0d45c3</a> +<blockquote> +<p> + gitlog2changelog.py use html sequence for '&'<br> +<br> + Thanks to SaGS for pointing it out.<br> +<br> + CLUSTER_UNTESTED<br> +<br> +gs/toolbin/gitlog2changelog.py<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-30 18:14:22 +0000 +</strong> +<br>Chris Liddell <chris.liddell@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=7a9e90a4710a90ce3d12da590280e91166eb2dc5">7a9e90a4710a90ce3d12da590280e91166eb2dc5</a> +<blockquote> +<p> + Tweak gitlog2changelog.py to avoid trailing whitespace<br> +<br> + CLUSTER_UNTESTED<br> +<br> +gs/toolbin/gitlog2changelog.py<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-30 18:00:23 +0000 +</strong> +<br>Chris Liddell <chris.liddell@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=4aaa5f1594df678db91e3e9e913d1b27d5f7cd05">4aaa5f1594df678db91e3e9e913d1b27d5f7cd05</a> +<blockquote> +<p> + Update docs in prep for 9.05 release candidate<br> +<br> + CLUSTER_UNTESTED<br> +<br> +gs/doc/API.htm<br> +gs/doc/C-style.htm<br> +gs/doc/Commprod.htm<br> +gs/doc/DLL.htm<br> +gs/doc/Deprecated.htm<br> +gs/doc/Details8.htm<br> +gs/doc/Details9.htm<br> +gs/doc/Develop.htm<br> +gs/doc/Devices.htm<br> +gs/doc/Drivers.htm<br> +gs/doc/Fonts.htm<br> +gs/doc/Helpers.htm<br> +gs/doc/History1.htm<br> +gs/doc/History2.htm<br> +gs/doc/History3.htm<br> +gs/doc/History4.htm<br> +gs/doc/History5.htm<br> +gs/doc/History6.htm<br> +gs/doc/History7.htm<br> +gs/doc/History8.htm<br> +gs/doc/History9.htm<br> +gs/doc/Install.htm<br> +gs/doc/Issues.htm<br> +gs/doc/Language.htm<br> +gs/doc/Lib.htm<br> +gs/doc/Make.htm<br> +gs/doc/News.htm<br> +gs/doc/Projects.htm<br> +gs/doc/Ps-style.htm<br> +gs/doc/Ps2epsi.htm<br> +gs/doc/Ps2pdf.htm<br> +gs/doc/Ps2ps2.htm<br> +gs/doc/Psfiles.htm<br> +gs/doc/Readme.htm<br> +gs/doc/Release.htm<br> +gs/doc/Source.htm<br> +gs/doc/Unix-lpr.htm<br> +gs/doc/Use.htm<br> +gs/doc/Xfonts.htm<br> +gs/doc/gs-vms.hlp<br> +gs/doc/thirdparty.htm<br> +gs/man/dvipdf.1<br> +gs/man/font2c.1<br> +gs/man/gs.1<br> +gs/man/gslp.1<br> +gs/man/gsnd.1<br> +gs/man/pdf2dsc.1<br> +gs/man/pdf2ps.1<br> +gs/man/pdfopt.1<br> +gs/man/pf2afm.1<br> +gs/man/pfbtopfa.1<br> +gs/man/printafm.1<br> +gs/man/ps2ascii.1<br> +gs/man/ps2epsi.1<br> +gs/man/ps2pdf.1<br> +gs/man/ps2pdfwr.1<br> +gs/man/ps2ps.1<br> +gs/man/wftopfa.1<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-30 17:59:49 +0000 +</strong> +<br>Chris Liddell <chris.liddell@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=60ef9ebafb60f60cb709f7cb48ff15b94bad45fe">60ef9ebafb60f60cb709f7cb48ff15b94bad45fe</a> +<blockquote> +<p> + Change product string in prep for 9.05 release candidate<br> +<br> + CLUSTER_UNTESTED<br> +<br> +gs/base/version.mak<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-30 17:46:27 +0000 +</strong> +<br>Chris Liddell <chris.liddell@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=16195b5e1c104405e095753bc1343597cad32a28">16195b5e1c104405e095753bc1343597cad32a28</a> +<blockquote> +<p> + Move the JPEG XR code to a separate section......<br> +<br> + ... for non-GPL compatible, open source licensed code.<br> +<br> + CLUSTER_UNTESTED<br> +<br> +gs/doc/thirdparty.htm<br> +<p> +</blockquote> +<hr> +<p><strong>2012-01-30 17:41:35 +0000 +</strong> +<br>Chris Liddell <chris.liddell@artifex.com><br> +<a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=4961e763aeb795e7dc91dc64575837d170cca367">4961e763aeb795e7dc91dc64575837d170cca367</a> +<blockquote> +<p> + Improve the html output of the changelog generator.<br> +<br> + There were some compatibility problems with the html from the git log to<br> + html changelog generator - such as including '<' and '>' characters in<br> + text to be displayed.<br> +<br> + Also, improve the actual formatting slightly.<br> +<br> + CLUSTER_UNTESTED<br> +<br> +gs/toolbin/gitlog2changelog.py<br> +<p> +</blockquote> +<hr> <p><strong>2012-01-30 13:32:05 +0000 </strong> <br>Ken Sharp <ken.sharp@artifex.com><br> @@ -371,19 +663,19 @@ gs/lib/opdfread.ps <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=043a20124c63ee48f874e8a9d869098d099c6d19">043a20124c63ee48f874e8a9d869098d099c6d19</a> <blockquote> <p> - Have the "configure" build cope with missing "contrib" + Have the "configure" build cope with missing "contrib" <br> <br> For the Artifex commercial release, we remove the files from the contrib <br> - directory. This meant a successful build had to be "configured" with the + directory. This meant a successful build had to be "configured" with the <br> --without-contrib option. <br> <br> - Now, configure looks for a specific file in "contrib", and if it is not there + Now, configure looks for a specific file in "contrib", and if it is not there <br> the contributed drivers are automatically disabled. <br> @@ -572,7 +864,7 @@ gs/doc/thirdparty.htm <br> with image = NULL. This cures a problem in mupdf where it SEGVs <br> - when called on "1239 - skip invalid content streams.pdf" from the + when called on "1239 - skip invalid content streams.pdf" from the <br> sumatra test set. <br> @@ -622,7 +914,7 @@ gs/doc/Make.htm <br> Add information to the cidfmap section of Use.htm mentioning the ability to <br> - use "getenv" to influence paths to font files in cidfmap. + use "getenv" to influence paths to font files in cidfmap. <br> <br> @@ -672,7 +964,7 @@ gs/base/configure.ac <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=1f3469404c599093df2e6c8157ac70111b0c80e2">1f3469404c599093df2e6c8157ac70111b0c80e2</a> <blockquote> <p> - Revert "Addition of objects to support the output intent." + Revert "Addition of objects to support the output intent." <br> <br> @@ -880,7 +1172,7 @@ gs/doc/Make.htm <br> gs -sDEVICE=pdfwrite -o tiger.pdf examples/tiger.eps \ <br> - -c "<< /OutputFile (colorcir.pdf) >> setpagedevice" \ + -c "<< /OutputFile (colorcir.pdf) >> setpagedevice" \ <br> -f examples/colorcir.ps <br> @@ -913,17 +1205,17 @@ gs/doc/Use.htm <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=7d0f46b66b275c794dd87525e066e84ccabb4f96">7d0f46b66b275c794dd87525e066e84ccabb4f96</a> <blockquote> <p> - Bug 692801: Fix build with shared lcms2 and "so" target + Bug 692801: Fix build with shared lcms2 and "so" target <br> <br> The targets for the lcms2 integration were mixed up, meaning the shared <br> - lib build had a couple of dependencies on our "local" lcms2 source files. + lib build had a couple of dependencies on our "local" lcms2 source files. <br> <br> - The "so" target failed because the compiler for the lcms2 integration + The "so" target failed because the compiler for the lcms2 integration <br> code used the wrong compiler variable (and consequently dropped some <br> @@ -1043,9 +1335,9 @@ pl/pllfont.c <br> <br> - The PJL resolution variable is now properly supported, for example "PJL + The PJL resolution variable is now properly supported, for example "PJL <br> - SET RESOLUTION = 300" will see the resolution for the next job to 300 + SET RESOLUTION = 300" will see the resolution for the next job to 300 <br> but will be overridden if -r is given directly on the command line. <br> @@ -1109,7 +1401,7 @@ pl/pllfont.c <br> fix cannot be right, something must have been wrong with the analysis, <br> - unfortunately the, referenced test file from the logs ("sprinkler") + unfortunately the, referenced test file from the logs ("sprinkler") <br> seems to be gone. <br> @@ -1190,15 +1482,15 @@ pl/plmain.c <br> <br> - pcl6 -lRTL -J"@PJL DEFAULT PLOTSIZEOVERRIDE=ON;\ + pcl6 -lRTL -J"@PJL DEFAULT PLOTSIZEOVERRIDE=ON;\ <br> - @PJL DEFAULT PLOTSIZE1=10000;@PJL DEFAULT PLOTSIZE2=8000" + @PJL DEFAULT PLOTSIZE1=10000;@PJL DEFAULT PLOTSIZE2=8000" <br> <br> Unfortunately, the odd behavior of HP's PJL parser does not allow <br> - whitespace before "@PJL" which should start a new command each on a + whitespace before "@PJL" which should start a new command each on a <br> different line, similarly there can be no leading white space at the <br> @@ -1273,7 +1565,7 @@ gs/base/echogs.c <br> <br> - pdfwrite provides it's own "low level" stringwidth code, which includes code to + pdfwrite provides it's own "low level" stringwidth code, which includes code to <br> convert the resulting coordinates into user space. Unexplicably, this <br> @@ -1308,9 +1600,9 @@ gs/base/gdevpdte.c <br> As a legacy of the old Text rendering mode code there is an optimisation in <br> - pdfwrite which detects sequences such as "true charpath gsave fill grestore + pdfwrite which detects sequences such as "true charpath gsave fill grestore <br> - stroke" and converts them to Text rendering mode 2. + stroke" and converts them to Text rendering mode 2. <br> <br> @@ -2174,7 +2466,7 @@ pcl/pcpage.c <br> for standalone mode (GL only). So we have to save the entry operand <br> - to the "Enter HPGL/2 command" in the state so it can be used when the + to the "Enter HPGL/2 command" in the state so it can be used when the <br> transformation matrices are recalculated. <br> @@ -2467,7 +2759,7 @@ gs/base/gxblend.h <br> <br> - Revise the example using "getenv" to correcly account for the return values of getenv. + Revise the example using "getenv" to correcly account for the return values of getenv. <br> <br> @@ -2490,7 +2782,7 @@ gs/Resource/Init/cidfmap <br> <br> - Another case where our "internal" SHA symbols could clash with the "real" + Another case where our "internal" SHA symbols could clash with the "real" <br> OpenSSL ones if libgs is being statically linked. As before, trivial rename <br> @@ -3261,11 +3553,11 @@ gs/base/configure.ac <br> <br> - When we have to substitute for a "Light" style CIDFont which has been made + When we have to substitute for a "Light" style CIDFont which has been made <br> bold, don't apply artificial emboldening unless the substitute font is <br> - also a "Light". + also a "Light". <br> <br> @@ -3324,7 +3616,7 @@ gs/Resource/Init/pdf_draw.ps <br> <br> - Revert to using the "pristine" URW fonts. + Revert to using the "pristine" URW fonts. <br> <br> @@ -3419,7 +3711,7 @@ gs/Resource/Font/URWPalladioL-Roma <br> revision handles substition by modifying the CIDFont resource .map dictionary. <br> - This means that the "fake" CIDFont is created with the requested parameters + This means that the "fake" CIDFont is created with the requested parameters <br> from the start. <br> @@ -3726,9 +4018,9 @@ gs/base/gdevpdtt.c <br> content streams, and image the text they contain, rather than skipping <br> - them. NOTE: this does not make the output from Bug692320.pdf "correct", but + them. NOTE: this does not make the output from Bug692320.pdf "correct", but <br> - arguably makes it "less wrong". + arguably makes it "less wrong". <br> <br> @@ -3773,7 +4065,7 @@ gs/psi/psromfs.mak <br> Non-marking operations (such as stringwidth) sometimes require FAPI to produce <br> - a bitmap. We were taking the "slegdehammer" approach of always producing a + a bitmap. We were taking the "slegdehammer" approach of always producing a <br> bitmap, and throwing it away when not required. <br> @@ -3864,7 +4156,7 @@ gs/ghostscript.vcproj <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=9a2555a91fbc2fa73a6e2f8f4035b58b4ff5ae57">9a2555a91fbc2fa73a6e2f8f4035b58b4ff5ae57</a> <blockquote> <p> - Bug 692686: use same scan conversion settings for "clip" as for "fill" + Bug 692686: use same scan conversion settings for "clip" as for "fill" <br> <br> @@ -3882,7 +4174,7 @@ gs/ghostscript.vcproj <br> text modes in PDF, however, we still used the default fill_adjust, which <br> - resulted in an overly "bold" clip path. + resulted in an overly "bold" clip path. <br> <br> @@ -4018,7 +4310,7 @@ gs/ghostscript.vcproj <br> <br> - This introduces a CMM that can hand back "links" to gs where the + This introduces a CMM that can hand back "links" to gs where the <br> links in this case contain pointers to the simple procedures that <br> @@ -4138,7 +4430,7 @@ gs/doc/Drivers.htm <br> Finally, a fix so configure doesn't assume pkgconfig availability (although it <br> - is widely available, it is not "standard"). + is widely available, it is not "standard"). <br> <br> @@ -4465,15 +4757,15 @@ gs/jbig2dec/jbig2_text.c <br> When image data does not land exactly on the necessary alignment for SSE2 <br> - optimisations, we handle the "left over" samples on their own, before the + optimisations, we handle the "left over" samples on their own, before the <br> suitably aligned samples. When we come to copy the halftoned data to the <br> - target device, we first handle the "left over" samples, and then the + target device, we first handle the "left over" samples, and then the <br> - SSE2 aligned samples in separate calls to copy_mono/copy_plane. The "left + SSE2 aligned samples in separate calls to copy_mono/copy_plane. The "left <br> - over" samples never number more than 16. + over" samples never number more than 16. <br> <br> @@ -4756,13 +5048,13 @@ gs/base/gdevpdfu.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=3f99f9c568fa7a93ce4ca5acdc0c8fed6cf505bd">3f99f9c568fa7a93ce4ca5acdc0c8fed6cf505bd</a> <blockquote> <p> - Add a "dummy" call to validate UFST font. + Add a "dummy" call to validate UFST font. <br> <br> It turns out that UFST's CGIFfont() call does little or no validation of the <br> - font for which it is creating an object. So, add a "dummy" call to + font for which it is creating an object. So, add a "dummy" call to <br> CGIFfont_metrics() which will return an error if, for example, a request <br> @@ -4803,7 +5095,7 @@ gs/psi/fapiufst.c <br> <br> - Images are not supposed to use the "any part of a pixel" rule, where + Images are not supposed to use the "any part of a pixel" rule, where <br> vectors are, but the fact this file works in acrobat would seem to <br> @@ -4879,9 +5171,9 @@ gs/base/gdevpdtd.c <br> <br> - We will now do as Distiller and convert to name objects, unless we are in "CPSI + We will now do as Distiller and convert to name objects, unless we are in "CPSI <br> - compatibility mode", when we will throw an error. + compatibility mode", when we will throw an error. <br> <br> @@ -5419,7 +5711,7 @@ pl/pjtop.h <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=fc3aa53aafc7b73ae9703d253ae4040658e22b74">fc3aa53aafc7b73ae9703d253ae4040658e22b74</a> <blockquote> <p> - The "wide a4" state variable could be used unitialized when using + The "wide a4" state variable could be used unitialized when using <br> custom paper sizes. <br> @@ -5507,7 +5799,7 @@ pl/plsrgb.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=aef9ee68391088d1c7e371a6f1e3fa4092688eae">aef9ee68391088d1c7e371a6f1e3fa4092688eae</a> <blockquote> <p> - Revert "Embedding of device ICC profile into JPEG output device" + Revert "Embedding of device ICC profile into JPEG output device" <br> <br> @@ -5600,7 +5892,7 @@ gs/base/gdevtsep.c <br> which uses the Ghostscript file API to access the data. We generally prefer <br> - to operate that way anyway, and (more importantly) this allows FT "direct" + to operate that way anyway, and (more importantly) this allows FT "direct" <br> acccess to font files stored in our ROM filesystem. <br> @@ -5629,7 +5921,7 @@ gs/psi/fapi_ft.c <br> when building the rom filesystem, we need a wildcardm, so it ends up <br> - as "Resource/CIDFont/*" + as "Resource/CIDFont/*" <br> <br> @@ -5809,7 +6101,7 @@ pxl/pxgstate.c <br> <br> - This incorporates changes from Michael to the new "fast threshold" image + This incorporates changes from Michael to the new "fast threshold" image <br> halftoning code to make it use the new copy_planes operation. <br> @@ -5950,7 +6242,7 @@ gs/base/gxfcopy.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=ed8664ed1a8a797d949270d707966aadefb3b9e8">ed8664ed1a8a797d949270d707966aadefb3b9e8</a> <blockquote> <p> - Renamed the PXL CUPS filter from "pstopxl" to "gstopxl", as like "gstoraster" + Renamed the PXL CUPS filter from "pstopxl" to "gstopxl", as like "gstoraster" <br> it understands both PostScript and PDF as input. <br> @@ -6025,7 +6317,7 @@ tools/pxldis.py <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=d53286dbb42db66166b7af2f68a63baf7da43791">d53286dbb42db66166b7af2f68a63baf7da43791</a> <blockquote> <p> - Fix 690417 - new PCL command "set logical page". This allows the user + Fix 690417 - new PCL command "set logical page". This allows the user <br> to provide arbitrary width, height and offsets which are then <br> @@ -6521,7 +6813,7 @@ gs/psi/zmisc.c <br> <br> - Bug #692670 "Ghostscript uses 2 gigs of memory reading file". When writing + Bug #692670 "Ghostscript uses 2 gigs of memory reading file". When writing <br> images a JPEG the pdfwrite code creates a memory device temporarily. It <br> @@ -6837,9 +7129,9 @@ gs/toolbin/localcluster/clusterpush.pl <br> <br> - XPS renders with the "pixel centres covered" rule, rather than the + XPS renders with the "pixel centres covered" rule, rather than the <br> - "any part of a pixel" rule. As such fill_adjust is 0. This exposes + "any part of a pixel" rule. As such fill_adjust is 0. This exposes <br> limitations in ghostscripts pattern tile handling code. <br> @@ -7011,7 +7303,7 @@ gs/base/gsstate.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c4e3f9c1d245e374eb30cc179e27bdcd2746812c">c4e3f9c1d245e374eb30cc179e27bdcd2746812c</a> <blockquote> <p> - Bug 692661: setup dict and op stacks for executing a "charproc" + Bug 692661: setup dict and op stacks for executing a "charproc" <br> <br> @@ -7116,9 +7408,9 @@ gs/base/gsptype1.c <br> On Linux (at least) the locale affects the behaviour of sscanf(): certain <br> - languages use a comma (",") for the decimal point, rather than a full stop + languages use a comma (",") for the decimal point, rather than a full stop <br> - ("."). Setting one of those locales (such as Spanish) causes sscanf() to fail + ("."). Setting one of those locales (such as Spanish) causes sscanf() to fail <br> when parsing a number with a fractional component in the CFF interpreter. <br> @@ -7521,7 +7813,7 @@ gs/Resource/Init/pdf_base.ps <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=d8089a9dcf0971a1131f8391049c602a61852f65">d8089a9dcf0971a1131f8391049c602a61852f65</a> <blockquote> <p> - Bug 692634: handle skipping "cached" outline glyphs + Bug 692634: handle skipping "cached" outline glyphs <br> <br> @@ -7811,7 +8103,7 @@ gs/base/gdevtxtw.c <br> Actually two problems showed up after the previous commit related to this bug. A crash <br> - could occur (or cause "Object not in any chunk") because the pdf14 device did not use + could occur (or cause "Object not in any chunk") because the pdf14 device did not use <br> stable_memory for separation names. The second issue was a VMerror when the decision <br> @@ -8514,7 +8806,7 @@ gs/base/gxp1fill.c <br> <br> - ps3cet/11-20.PS now runs without a "Font Renderer Plugin .... error" + ps3cet/11-20.PS now runs without a "Font Renderer Plugin .... error" <br> <br> @@ -8566,7 +8858,7 @@ gs/toolbin/color/halftone/halfttoning/halftone.c <br> exceeds the threshold, we don't need to really do anything when a job requests GC. <br> - Change "internal" (infrequent) interpreter uses to use '2 .vmreclaim'. Speeds up the + Change "internal" (infrequent) interpreter uses to use '2 .vmreclaim'. Speeds up the <br> file from the bug by 79X ! <br> @@ -8933,11 +9225,11 @@ gs/psi/fapi_ft.c <br> <br> - We'll now apply the "non-squareness" scaling in the matrix, rather in the + We'll now apply the "non-squareness" scaling in the matrix, rather in the <br> resution which we pass to Freetype. We have to do this because Freetype <br> - treats the resolution as being in "glyph space", which means it is "incorrect" + treats the resolution as being in "glyph space", which means it is "incorrect" <br> for any rotated/sheared glyph. <br> @@ -9035,9 +9327,9 @@ gs/base/gxclbits.c <br> <br> - I changed the MT fonts to use a "conventional" Type 1 font matrix to + I changed the MT fonts to use a "conventional" Type 1 font matrix to <br> - make a Quality Logic file "work" as expected - it's a daft test which + make a Quality Logic file "work" as expected - it's a daft test which <br> makes the invalid assumption that the fonts in the standard font set <br> @@ -9629,13 +9921,13 @@ gs/base/gsdparam.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=b39b7cbfcf8719b9f41153ccf6172fbf8f800642">b39b7cbfcf8719b9f41153ccf6172fbf8f800642</a> <blockquote> <p> - Some tweaks to allow "make so" to build in Mac OSX. + Some tweaks to allow "make so" to build in Mac OSX. <br> <br> - The change still results in a ".so" object file, rather than usual Mac + The change still results in a ".so" object file, rather than usual Mac <br> - ".dylib" file, but other than the name, they are internally identical. + ".dylib" file, but other than the name, they are internally identical. <br> <br> @@ -9693,7 +9985,7 @@ gs/base/configure.ac <br> In setshowstate we have to work around buggy PDFs in a manner which <br> - means we "show" the text in question, but then rely on a charpath + means we "show" the text in question, but then rely on a charpath <br> operation to update the current point accurately. The problem was <br> @@ -9968,7 +10260,7 @@ gs/base/gzstate.h <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=02bdba18be7f2b78ca03d3f4126cef830eab28eb">02bdba18be7f2b78ca03d3f4126cef830eab28eb</a> <blockquote> <p> - Fixes 692544, an "off by one" error in the parser caused a pcl data + Fixes 692544, an "off by one" error in the parser caused a pcl data <br> scanning command at the end of a stream to be skipped. No expected <br> @@ -10535,7 +10827,7 @@ gs/base/gdevdrop.c <br> at Postscript CIDFont files that are outside the normal resource search <br> - path (i.e. not in "Resource/CIDFont"). + path (i.e. not in "Resource/CIDFont"). <br> <br> @@ -10659,7 +10951,7 @@ gs/base/siscale.c <br> <br> - 2) "Side-port" changes from the integration project for customer 532. + 2) "Side-port" changes from the integration project for customer 532. <br> <br> @@ -10808,7 +11100,7 @@ gs/psi/zfimscale.c <br> The XCFLAGS and XLDFLAGS should be available to be specified as parameters to <br> - "make", but they were being used by the autoconf tools. This change moves the + "make", but they were being used by the autoconf tools. This change moves the <br> autconf set flags into their own variables, leaving XCFLAGS and XLDFLAGS for <br> @@ -11050,7 +11342,7 @@ gs/Resource/Init/pdf_main.ps <br> It turns out that when we right the tile raster for the clist we don't <br> - really know what the "true" target of the pattern is only the final + really know what the "true" target of the pattern is only the final <br> target device. In this particular situation, the target for the pattern <br> @@ -11390,7 +11682,7 @@ xps/xps_msvc.mak <br> <br> - If the metrics don't exist in a CID font, we attempt to derive "sane" + If the metrics don't exist in a CID font, we attempt to derive "sane" <br> metrics from the bounding box information. This is problematic since a <br> @@ -11404,7 +11696,7 @@ xps/xps_msvc.mak <br> writing font when we're using a Truetype font as a substitute for a <br> - "real" CIDFont. + "real" CIDFont. <br> <br> @@ -12015,9 +12307,9 @@ gs/toolbin/bmpcmp.c <br> state processing. This patch does the following: <br> - - drops "W" in the sequence 'W Q" + - drops "W" in the sequence 'W Q" <br> - - ignores graphic state changes, e.g. in "W 0 G" + - ignores graphic state changes, e.g. in "W 0 G" <br> - takes into account possible presence of non-graphic-state <br> @@ -12325,7 +12617,7 @@ gs/base/gxpcmap.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=f215836c60865eaa2da4bed711215eae2b906c49">f215836c60865eaa2da4bed711215eae2b906c49</a> <blockquote> <p> - Revert "Fix for Bug 687695." Fixes Bug 692454 + Revert "Fix for Bug 687695." Fixes Bug 692454 <br> <br> @@ -12727,11 +13019,11 @@ gs/base/gximag3x.c <br> As cups_set_color_info() now does things that can fail, it has to return <br> - an error value (getting rid of the "code set but never used" warning). + an error value (getting rid of the "code set but never used" warning). <br> <br> - Also, add a "default:" case to a switch to get rid of the warning about + Also, add a "default:" case to a switch to get rid of the warning about <br> enum values not handled in a switch - the default case does nothing, so <br> @@ -13002,7 +13294,7 @@ gs/cups/gdevcups.c <br> If no output profile is supplied by the user via <br> - "-sOutputICCProfile=...", set a default profile appropriate to the + "-sOutputICCProfile=...", set a default profile appropriate to the <br> selected color space (RGBish additive, CMYKish subtractive, or <br> @@ -13057,7 +13349,7 @@ gs/base/gdevprn.c <br> <br> - The CUPS Raster output device ("cups") has an RGBW output color + The CUPS Raster output device ("cups") has an RGBW output color <br> space. This was intended to produce standard RGB plus an extra channel <br> @@ -13217,7 +13509,7 @@ gs/base/lib.mak <br> <br> - We only need the "library" part, not the example apps and third party + We only need the "library" part, not the example apps and third party <br> libraries (only used by the example apps), and they add up to a lot of space. <br> @@ -13446,7 +13738,7 @@ gs/contrib/lips4/gdevl4v.c <br> <br> - Fix for lcms definition of "LCMS_INLINE" on the HP compiler. + Fix for lcms definition of "LCMS_INLINE" on the HP compiler. <br> <br> @@ -13577,7 +13869,7 @@ gs/base/configure.ac <br> <br> - By adding a gs_memory_t argument to the object "finalize" method, we can + By adding a gs_memory_t argument to the object "finalize" method, we can <br> dispense with the pointer-pun hackery that stores the memory context <br> @@ -13589,7 +13881,7 @@ gs/base/configure.ac <br> Although primarily addresses one hack, this commit touches a number of files <br> - because it affects every object with a "finalize" method. + because it affects every object with a "finalize" method. <br> <br> @@ -14041,7 +14333,7 @@ gs/psi/zicc.c <br> <br> - Build gs with Memento enabled: make debug XCFLAGS="-DMEMENTO" + Build gs with Memento enabled: make debug XCFLAGS="-DMEMENTO" <br> <br> @@ -14106,7 +14398,7 @@ gs/toolbin/squeeze2html.pl <br> <br> - "Bring the changelog up to date since the RC, and revise the date." + "Bring the changelog up to date since the RC, and revise the date." <br> <br> @@ -14241,7 +14533,7 @@ gs/man/wftopfa.1 <br> <br> - "Update the docs, version numbers, and dates for 9.04 rc1" + "Update the docs, version numbers, and dates for 9.04 rc1" <br> <br> @@ -14650,7 +14942,7 @@ gs/psi/psromfs.mak <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c0040ecf8553bdd9f8028fe5f816af24e5070d29">c0040ecf8553bdd9f8028fe5f816af24e5070d29</a> <blockquote> <p> - Backout accidental commit of bbb8f98; "Alexs patch." + Backout accidental commit of bbb8f98; "Alexs patch." <br> <br> @@ -14708,7 +15000,7 @@ gs/cups/gstoraster.c <br> <br> - Avoid warnings given on some platforms about "unreachable code" by + Avoid warnings given on some platforms about "unreachable code" by <br> using an informative #define. <br> @@ -14757,7 +15049,7 @@ gs/cups/gdevcups.c <br> <br> - To ignore this RIP_MAX_CACHE we simply add a "return" right at the + To ignore this RIP_MAX_CACHE we simply add a "return" right at the <br> beginning of this function. It will be removed when a real fix gets <br> @@ -14837,7 +15129,7 @@ gs/Resource/Init/pdf_draw.ps <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=6c5f9661790b886a681b8926126875e6df59cbb1">6c5f9661790b886a681b8926126875e6df59cbb1</a> <blockquote> <p> - Added "-dNOINTERPOLATE" to the Ghostscript command lines of the CUPS filters + Added "-dNOINTERPOLATE" to the Ghostscript command lines of the CUPS filters <br> <br> @@ -14976,7 +15268,7 @@ gs/psi/psromfs.mak <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=217f9712df606e4dedc8afe1220e6b30df627516">217f9712df606e4dedc8afe1220e6b30df627516</a> <blockquote> <p> - Increment version number for "master". + Increment version number for "master". <br> <br> @@ -15144,15 +15436,15 @@ gs/base/gxclrast.c <br> gcc 3.4.6 SPARC (possibly versions/ports) when compiling: <br> - "psc->feof(psc->file)" seems to be unable to differentiate between + "psc->feof(psc->file)" seems to be unable to differentiate between <br> - "feof" element in the structure, and "feof()" function from the + "feof" element in the structure, and "feof()" function from the <br> std library, and as a result gives a syntax error. <br> <br> - So I've renamed the structure entry "peof", and the other two file + So I've renamed the structure entry "peof", and the other two file <br> handling function pointers similarly. <br> @@ -15317,7 +15609,7 @@ gs/base/gdevpx.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=6ab36cb4256fbd9aa005b79e317ff0993f4acf3e">6ab36cb4256fbd9aa005b79e317ff0993f4acf3e</a> <blockquote> <p> - Fixes on the "pstopxl" CUPS filter + Fixes on the "pstopxl" CUPS filter <br> <br> @@ -15327,11 +15619,11 @@ gs/base/gdevpx.c <br> <br> - 2. Switch the Ghostscript output device "pxlmono" if the "pxlcolor" is + 2. Switch the Ghostscript output device "pxlmono" if the "pxlcolor" is <br> - used but "Gray" chosen as "ColorModel" setting. Monochrome + used but "Gray" chosen as "ColorModel" setting. Monochrome <br> - "BitsPerPixel" settings do not work with "pxlcolor". + "BitsPerPixel" settings do not work with "pxlcolor". <br> <br> @@ -15667,7 +15959,7 @@ gs/base/mkromfs.c <br> <br> - Also resolves Bug #688709 "Updated Adobe Glyph List" + Also resolves Bug #688709 "Updated Adobe Glyph List" <br> <br> @@ -15816,9 +16108,9 @@ gs/base/configure.ac <br> Introduces a --with-cups-install option to configure. To include the <br> - cups tools and associated data files in Ghostscript's "install" target + cups tools and associated data files in Ghostscript's "install" target <br> - you will have to specify "--with-cups-install" at configure time. + you will have to specify "--with-cups-install" at configure time. <br> <br> @@ -15965,7 +16257,7 @@ gs/cups/gdevcups.c <br> <br> - Remove the "RELEASE CANDIDATE" string, bring the changelog up to date since + Remove the "RELEASE CANDIDATE" string, bring the changelog up to date since <br> the RC, and revise the date. <br> @@ -16255,7 +16547,7 @@ gs/psi/msvc.mak <br> <br> - Avoid warnings given on some platforms about "unreachable code" by + Avoid warnings given on some platforms about "unreachable code" by <br> using an informative #define. <br> @@ -16304,7 +16596,7 @@ gs/cups/gdevcups.c <br> <br> - To ignore this RIP_MAX_CACHE we simply add a "return" right at the + To ignore this RIP_MAX_CACHE we simply add a "return" right at the <br> beginning of this function. It will be removed when a real fix gets <br> @@ -16327,7 +16619,7 @@ gs/cups/gdevcups.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=83abb6ca67829a1273ed4fdfc894a6af44c5c5ad">83abb6ca67829a1273ed4fdfc894a6af44c5c5ad</a> <blockquote> <p> - Added "-dNOINTERPOLATE" to the Ghostscript command lines of the CUPS filters + Added "-dNOINTERPOLATE" to the Ghostscript command lines of the CUPS filters <br> <br> @@ -16821,7 +17113,7 @@ gs/base/gdevpx.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=d6e940a92e47f0110438cf2f9bd6ebffa2f9e211">d6e940a92e47f0110438cf2f9bd6ebffa2f9e211</a> <blockquote> <p> - Fixes on the "pstopxl" CUPS filter + Fixes on the "pstopxl" CUPS filter <br> <br> @@ -16831,11 +17123,11 @@ gs/base/gdevpx.c <br> <br> - 2. Switch the Ghostscript output device "pxlmono" if the "pxlcolor" is + 2. Switch the Ghostscript output device "pxlmono" if the "pxlcolor" is <br> - used but "Gray" chosen as "ColorModel" setting. Monochrome + used but "Gray" chosen as "ColorModel" setting. Monochrome <br> - "BitsPerPixel" settings do not work with "pxlcolor". + "BitsPerPixel" settings do not work with "pxlcolor". <br> <br> @@ -16998,9 +17290,9 @@ gs/lib/pv.sh <br> Introduces a --with-cups-install option to configure. To include the <br> - cups tools and associated data files in Ghostscript's "install" target + cups tools and associated data files in Ghostscript's "install" target <br> - you will have to specify "--with-cups-install" at configure time. + you will have to specify "--with-cups-install" at configure time. <br> <br> @@ -17249,6 +17541,7 @@ has now been fully removed. <p> No other recorded incompatible changes. +<h3><a name="9.04_Changelog"></a>Changelog</h3> <p><strong>2011-08-04 14:40:12 +0100 </strong> <br>Chris Liddell <chris.liddell@artifex.com><br> @@ -17408,7 +17701,7 @@ gs/psi/msvc.mak <br> <br> - Avoid warnings given on some platforms about "unreachable code" by + Avoid warnings given on some platforms about "unreachable code" by <br> using an informative #define. <br> @@ -17457,7 +17750,7 @@ gs/cups/gdevcups.c <br> <br> - To ignore this RIP_MAX_CACHE we simply add a "return" right at the + To ignore this RIP_MAX_CACHE we simply add a "return" right at the <br> beginning of this function. It will be removed when a real fix gets <br> @@ -17480,7 +17773,7 @@ gs/cups/gdevcups.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=83abb6ca67829a1273ed4fdfc894a6af44c5c5ad">83abb6ca67829a1273ed4fdfc894a6af44c5c5ad</a> <blockquote> <p> - Added "-dNOINTERPOLATE" to the Ghostscript command lines of the CUPS filters + Added "-dNOINTERPOLATE" to the Ghostscript command lines of the CUPS filters <br> <br> @@ -17974,7 +18267,7 @@ gs/base/gdevpx.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=d6e940a92e47f0110438cf2f9bd6ebffa2f9e211">d6e940a92e47f0110438cf2f9bd6ebffa2f9e211</a> <blockquote> <p> - Fixes on the "pstopxl" CUPS filter + Fixes on the "pstopxl" CUPS filter <br> <br> @@ -17984,11 +18277,11 @@ gs/base/gdevpx.c <br> <br> - 2. Switch the Ghostscript output device "pxlmono" if the "pxlcolor" is + 2. Switch the Ghostscript output device "pxlmono" if the "pxlcolor" is <br> - used but "Gray" chosen as "ColorModel" setting. Monochrome + used but "Gray" chosen as "ColorModel" setting. Monochrome <br> - "BitsPerPixel" settings do not work with "pxlcolor". + "BitsPerPixel" settings do not work with "pxlcolor". <br> <br> @@ -18151,9 +18444,9 @@ gs/lib/pv.sh <br> Introduces a --with-cups-install option to configure. To include the <br> - cups tools and associated data files in Ghostscript's "install" target + cups tools and associated data files in Ghostscript's "install" target <br> - you will have to specify "--with-cups-install" at configure time. + you will have to specify "--with-cups-install" at configure time. <br> <br> @@ -18180,7 +18473,7 @@ gs/cups/cups.mak <br> <br> - Add "finalize" methods for gs_name_table, io_device_table and + Add "finalize" methods for gs_name_table, io_device_table and <br> font_dir tables which ensure that the pointers in the lib <br> @@ -18380,7 +18673,7 @@ pl/dwimg.c <br> <br> - Check return code from "get_profile" dev_proc in gs_nulldevice.c and get rid of the + Check return code from "get_profile" dev_proc in gs_nulldevice.c and get rid of the <br> implicit declaration for gdev_mem_set_planar. <br> @@ -18852,7 +19145,7 @@ gs/toolbin/bmpcmp.c <br> <br> - This does not really "fix" Bug 692357, but renders it pointless. + This does not really "fix" Bug 692357, but renders it pointless. <br> <br> @@ -19089,11 +19382,11 @@ gs/base/gdevpng.c <br> <br> - VS treats the "char" type as signed by default. When extended characters are promoted + VS treats the "char" type as signed by default. When extended characters are promoted <br> to ints, the values are negative in the range -128 to -1. These values (except -1 <br> - which conflicts with EOF) are not valid for the "is*()" family of functions. + which conflicts with EOF) are not valid for the "is*()" family of functions. <br> <br> @@ -19526,7 +19819,7 @@ gs/base/gdevvec.c <br> <br> - Also, add a "flush" at the end of each message to ensure they don't get + Also, add a "flush" at the end of each message to ensure they don't get <br> mangled by later, high priority messages. <br> @@ -19551,7 +19844,7 @@ gs/Resource/Init/pdf_font.ps <br> <br> - Visual C 7 (Visual Studio 2003) and earlier do not have all the "wide char" + Visual C 7 (Visual Studio 2003) and earlier do not have all the "wide char" <br> related library functions needed for the Windows Unicode path and <br> @@ -19601,9 +19894,9 @@ gs/toolbin/color/src_color/cmyk_src_renderintent.icc <br> <br> - I often have seen this message get garbled by having other messages on stderr "jump in" + I often have seen this message get garbled by having other messages on stderr "jump in" <br> - so that the message on stdout gets split up. The "flush" prevents that. + so that the message on stdout gets split up. The "flush" prevents that. <br> <br> @@ -20413,9 +20706,9 @@ gs/base/gximag3x.c <br> This also meant moving the ICC manager initialization to before the <br> - device "open" call in gs_setdevice_no_erase() because the device set + device "open" call in gs_setdevice_no_erase() because the device set <br> - can also open another device (in this case, pswrite's "open" has the + can also open another device (in this case, pswrite's "open" has the <br> effect, via the vector device, of setting a bbox device instance, so <br> @@ -20600,7 +20893,7 @@ gs/base/gxccman.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=e5a37634a8e15a945e7f5ea4aca68ab8e1e34d3a">e5a37634a8e15a945e7f5ea4aca68ab8e1e34d3a</a> <blockquote> <p> - Bug 692318: Ensure that compiler flags are used for the "aux" files. + Bug 692318: Ensure that compiler flags are used for the "aux" files. <br> <br> @@ -20957,7 +21250,7 @@ gs/base/memento.c <br> always be the last dependency listed. Unix builds define this to <br> - "| directories", windows builds leave it blank. + "| directories", windows builds leave it blank. <br> <br> @@ -21893,7 +22186,7 @@ xps/xpstop.c <br> This uses 'creative engineering' (aka a blatant hack) to allow copy_color <br> - to be implemented in the "rop source" device. + to be implemented in the "rop source" device. <br> <br> @@ -22700,7 +22993,7 @@ gs/ghostscript.vcproj <br> <br> - Simply add a #include "stdint_.h" to the top of a file; breakage + Simply add a #include "stdint_.h" to the top of a file; breakage <br> presumably caused by the dependency changes done earlier. <br> @@ -23289,7 +23582,7 @@ gs/base/gdevpdfe.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=45663bbeb798d7a851546a4d6ccf8954e16696ae">45663bbeb798d7a851546a4d6ccf8954e16696ae</a> <blockquote> <p> - (pdfwrite) Bug #692280 "Incorrect ToUnicode CMap when the input is a PDF with a 2-byte ToUnicode" + (pdfwrite) Bug #692280 "Incorrect ToUnicode CMap when the input is a PDF with a 2-byte ToUnicode" <br> <br> @@ -23370,7 +23663,7 @@ gs/psi/zcolor.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0b7cd7ca121ac440d5607cc6795ba8bcd7c20c85">0b7cd7ca121ac440d5607cc6795ba8bcd7c20c85</a> <blockquote> <p> - (pdfwrite) Bug #692268 "pdfwrite sets xapMM:DocumentID incorrectly" + (pdfwrite) Bug #692268 "pdfwrite sets xapMM:DocumentID incorrectly" <br> <br> @@ -25287,7 +25580,7 @@ gs/base/gdevpdtt.c <br> export MEMENTO_SQUEEZEAT=1 then run the app, and it will do some magic <br> - with repeated forks to test the "failure to allocate" paths through the code. + with repeated forks to test the "failure to allocate" paths through the code. <br> <br> @@ -27021,7 +27314,7 @@ gs/base/gsicc.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c9de3e70e4027fb86dde6079a48b29cfd6825c72">c9de3e70e4027fb86dde6079a48b29cfd6825c72</a> <blockquote> <p> - Revert "MSVC changes plus gitignore for patt_trans_clist" + Revert "MSVC changes plus gitignore for patt_trans_clist" <br> <br> @@ -28578,7 +28871,7 @@ main/pcl6_msvc.mak <br> <br> - The nullpage device previously used a 1"x1" default page size, this changes it + The nullpage device previously used a 1"x1" default page size, this changes it <br> to use the same default setting as other page devices (this can be Letter or <br> @@ -29259,9 +29552,9 @@ gs/base/errors.h <br> <br> - Use %s if the argument is not literal to address the warning "format + Use %s if the argument is not literal to address the warning "format <br> - not a string literal and no format arguments". + not a string literal and no format arguments". <br> <br> @@ -29459,7 +29752,7 @@ gs/base/gdevpng.c <br> smaller blocks to stay within the limits of various PS constricts and <br> - speed up operand stack manipulation, esp. "counttomark -3 roll". Bug 691908. + speed up operand stack manipulation, esp. "counttomark -3 roll". Bug 691908. <br> <br> @@ -34085,7 +34378,7 @@ gs/toolbin/pdf_info.ps <br> <br> - Bug #692116 "gs crash while executing stop operator" + Bug #692116 "gs crash while executing stop operator" <br> <br> @@ -34152,7 +34445,7 @@ gs/psi/zcolor.c <br> <br> - The GS_LIB registry entry was missing the "lib" directory. + The GS_LIB registry entry was missing the "lib" directory. <br> <br> @@ -34537,7 +34830,7 @@ gs/psi/nsisinst.nsi <br> <br> - Bug #692119 "Cannot copy text from Ghostscript generated PDF/A document" + Bug #692119 "Cannot copy text from Ghostscript generated PDF/A document" <br> <br> @@ -34914,7 +35207,7 @@ gs/lib/opdfread.ps <p> Bug 689093 #21/ HTML compatibility: <br> - Do not use SHORTTAGS (the "<tag ... />" form) in HTML. + Do not use SHORTTAGS (the "<tag ... />" form) in HTML. <br> <br> @@ -35081,7 +35374,7 @@ gs/doc/gs.css <br> of the file comes from the last CVS version available; the copy in the 1st SVN <br> - checkout I have is already damaged. Note the "/CreationDate" inside the pdf is the + checkout I have is already damaged. Note the "/CreationDate" inside the pdf is the <br> same as in the current (damaged) version and the last change to this file is very <br> @@ -35106,17 +35399,17 @@ gs/ijs/ijs_spec.pdf <p> Bug 689093 #18/ SVN damage: <br> - Protect text-"$Id$" from expansion, part #2/2: fix existing files + Protect text-"$Id$" from expansion, part #2/2: fix existing files <br> <br> - This patch changes files that contain "$Id..." as text in order to + This patch changes files that contain "$Id..." as text in order to <br> protect the apparent keyword from being expanded by SubVersion. The <br> methods used are as follows: <br> - - for HTML: use the numeric entity "$" instead of "$". + - for HTML: use the numeric entity "$" instead of "$". <br> - for C and Python: if the parser finds 2 consecutive string <br> @@ -35211,9 +35504,9 @@ gs/toolbin/split_changelog.py <br> displayed differs. This patch extends the substitutions done for <br> - character entities to include "$" => "$"; there won't be any + character entities to include "$" => "$"; there won't be any <br> - "$"-as-text, and thus no "$Keyword..$"-as-text, anymore. + "$"-as-text, and thus no "$Keyword..$"-as-text, anymore. <br> <br> @@ -35240,7 +35533,7 @@ gs/toolbin/split_changelog.py <br> toolbin\split_changelog.py encodes text coming from log messages as <br> - utf-8. The patch changes it to output a "<meta/>" element specifying + utf-8. The patch changes it to output a "<meta/>" element specifying <br> the charset used, otherwise browsers that are not set for utf-8 by <br> @@ -35295,7 +35588,7 @@ gs/toolbin/split_changelog.py <br> This patch also contains a small change not related to HTML-conformance: <br> - a missing space in doc\Language.htm ("... for[NO SPACE HERE]1-, ..."). + a missing space in doc\Language.htm ("... for[NO SPACE HERE]1-, ..."). <br> <br> @@ -35320,13 +35613,13 @@ gs/doc/Ps2pdf.htm <p> Bug 689093 #13/ HTML conformance: <br> - 'align="middle"' should be 'align="center"' + 'align="middle"' should be 'align="center"' <br> <br> - "Middle" is only for vertical alignment ("valign="); for the + "Middle" is only for vertical alignment ("valign="); for the <br> - horizontal alignment use "center". + horizontal alignment use "center". <br> <br> @@ -35877,7 +36170,7 @@ xps/xpstop.c <br> full page was not. For color spaces in images we never actually call <br> - "setcolorspace" so the image type was not being set to icc, we do this + "setcolorspace" so the image type was not being set to icc, we do this <br> now explicitly in the PCL/XL code now. <br> @@ -36531,7 +36824,7 @@ pxl/pximage.c <a href="http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=91b7f320484904d60e8cf017611f5a8da4a6c685">91b7f320484904d60e8cf017611f5a8da4a6c685</a> <blockquote> <p> - Fixes 692109, the "no argument case" of the HPGL/2 INPUT RELATIVE + Fixes 692109, the "no argument case" of the HPGL/2 INPUT RELATIVE <br> command did not properly initialized the operands to their defaults. <br> @@ -36653,7 +36946,7 @@ gs/base/gxclpath.c <br> where ligatures were used. A (2:1) cluster map for the ligature <br> - "fi" has two characters (f, i) and one glyph (fi). We showed it + "fi" has two characters (f, i) and one glyph (fi). We showed it <br> as two glyphs (fi, i) instead of skipping the second character <br> @@ -36734,9 +37027,9 @@ gs/doc/Drivers.htm <br> <br> - The call effectively says "Copy this pixmap into the specified plane of this + The call effectively says "Copy this pixmap into the specified plane of this <br> - device". It is envisaged that it will only be defined for planar devices. + device". It is envisaged that it will only be defined for planar devices. <br> <br> @@ -36928,9 +37221,7 @@ gs/base/gxpcmap.c gs/base/gxshade6.c <br> gs/psi/zpcolor.c -<br> xps/xpstile.c -<br> <p> </blockquote> <hr> @@ -36940,8 +37231,8 @@ xps/xpstile.c <p>This is the third release in the stable 9.x series. -<p>This is an "out of order" release, primarily to ensure the -GPL Ghostscript release remains in version "lock-step" with the +<p>This is an "out of order" release, primarily to ensure the +GPL Ghostscript release remains in version "lock-step" with the Artifex commercial release. <p> Highlights in this release include: @@ -36965,8 +37256,7 @@ please visit <a href="http://bugs.ghostscript.com/">bugs.ghostscript.com</a>. <p> No recorded incompatible changes. - - +<h3><a name="9.02_Changelog"></a>Changelog</h3> <p><strong><a name="2011-03-30T064801.334550Z"></a> 2011-03-30T06:48:01.334550Z chrisl</strong></p> <blockquote> @@ -37611,13 +37901,24 @@ to avoid interferance from PS files that redefine them. Bug 692041. <pre> Fix for bug 692038. -This fixes 3 issues when using a CIELAB based profile for the output device ICC profile. +This fixes 3 issues when using a CIELAB based profile for the output device +ICC profile. -One was a problem when handling separation color spaces when they had the ALL entry and we were going to an additive device. AR does a 1-INK level for the device values and no color management. We were doing the same, but this approach will not work if our destination color space is CIELAB. Now if we are headed toward CIELAB we do the 1-INK to RGB and then transform to CIELAB. +One was a problem when handling separation color spaces when they had the ALL +entry and we were going to an additive device. AR does a 1-INK level for the +device values and no color management. We were doing the same, but this approach +will not work if our destination color space is CIELAB. Now if we are headed toward +CIELAB we do the 1-INK to RGB and then transform to CIELAB. -Another was that transparency blending should never be done in CIELAB or similar type color spaces. With transparency, the PDF14 device inherits the profile for the target device and if the transparency groups don't specify a color space we would end up blending in CIELAB. The solution was to detect this situation and use the defaultRGB profile for blending. Conversion to CIELAB occurs during the pdf14 put image operation. +Another was that transparency blending should never be done in CIELAB or similar type +color spaces. With transparency, the PDF14 device inherits the profile for the target +device and if the transparency groups don't specify a color space we would end up blending +in CIELAB. The solution was to detect this situation and use the defaultRGB profile for blending. +Conversion to CIELAB occurs during the pdf14 put image operation. -Finally, with shading in transparency, we need to make sure to pass along the transparency device through the shading parameters whenever we have a color mismatch between the pdf14 device and the target device so that the shading will occur in the proper color space. +Finally, with shading in transparency, we need to make sure to pass along the transparency device +through the shading parameters whenever we have a color mismatch between the pdf14 device and the +target device so that the shading will occur in the proper color space. These changes are all related to a non-tested cluster case when we have -sOutputICCProfile=lab.icc</pre> <p>[base/gdevp14.c base/gxcmap.c base/gstrans.c base/gxclist.h base/gdevtfnx.c base/gsfunc0.c base/devs.mak base/gsicc.c]</p> @@ -37738,7 +38039,8 @@ changes. 2011-03-07T22:19:29.253652Z Michael Vrhel</strong></p> <blockquote> <pre> -Initialize ht landscape structure to zero when in portrait case. There is a conditional test on the value later.</pre> +Initialize ht landscape structure to zero when in portrait case. There is +a conditional test on the value later.</pre> <p>[base/gximono.c]</p> </blockquote> @@ -37793,7 +38095,9 @@ CLUSTER_UNTESTED 2011-03-07T18:58:08.149818Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for improper indexing of reversed portrait image line. We were off by one byte and ended up with one byte not set. Def. a source of indeterminism. Thanks to Robin for tracking this down.</pre> +Fix for improper indexing of reversed portrait image line. We were off +by one byte and ended up with one byte not set. Def. a source of +indeterminism. Thanks to Robin for tracking this down.</pre> <p>[base/gximono.c]</p> </blockquote> @@ -37899,7 +38203,12 @@ were left unreferenced by the free of the pdf14 device. 2011-03-06T16:52:19.765042Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix to use proper DDA incrementation for interpolation. We still maintain special loops for when there is no scaling or for when it is 2x. This should fix the intdeterminism issues. Tested performance on customer files and no significant difference was observed. About 1500 cluster differences will be reported with this fix.</pre> +Fix to use proper DDA incrementation for interpolation. +We still maintain special loops for when there is no scalin +or for when it is 2x. This should fix the intdeterminism issues. +Tested performance on customer files and no significant difference +was observed. About 1500 cluster differences will be reported with +this fix.</pre> <p>[base/lib.mak base/gximono.c]</p> </blockquote> @@ -38037,7 +38346,12 @@ No cluster differences expected as this code isn't tested.</pre> 2011-03-03T17:51:48.590954Z Michael Vrhel</strong></p> <blockquote> <pre> -Enabling of thresholding code as default image rendering of monochrome/indexed images for monochrome devices. This will result in about 2432 differences reported. I stepped through them in a bmpcmp to check for serious issues. The minor halftone differences were due to the fact that we step in the device space for pixel replication in the threshold code but step in source space for the rect fill code. Enabling this code now will make it easier to track issues as we expand the use of the thresholding code.</pre> +Enabling of thresholding code as default image rendering of monochrome/indexed +images for monochrome devices. This will result in about 2432 differences reported. +I stepped through them in a bmpcmp to check for serious issues. The minor halftone +differences were due to the fact that we step in the device space for pixel replication +in the threshold code but step in source space for the rect fill code. Enabling this +code now will make it easier to track issues as we expand the use of the thresholding code.</pre> <p>[base/gximono.c]</p> </blockquote> @@ -38126,7 +38440,15 @@ previous message. 2011-03-02T18:51:23.645025Z Michael Vrhel</strong></p> <blockquote> <pre> -Introduction of a member variable in gs_image1_t, which will let us know the original source type of the image. For example if, the parent source were type3 this spawns two type1 images. One for the mask and one for the image data. The mask is rendered using image render simple. If the image is monochrome or indexed, it is rendered with the renderer in gximono.c . If we are going to a halftone monochrome device, we end up using the fast threshold based renderer which has its interpolation stepping in device space as opposed to source space. This causes very minor differences between the mask and the image data. To avoid this, we use the old rect_fill code for the image type3 data to ensure a more exact spatial match.</pre> +Introduction of a member variable in gs_image1_t, which will let us know the +original source type of the image. For example if, the parent source were type3 +this spawns two type1 images. One for the mask and one for the image data. The +mask is rendered using image render simple. If the image is monochrome or indexed, +it is rendered with the renderer in gximono.c . If we are going to a halftone +monochrome device, we end up using the fast threshold based renderer which has its +interpolation stepping in device space as opposed to source space. This causes very +minor differences between the mask and the image data. To avoid this, we use the old +rect_fill code for the image type3 data to ensure a more exact spatial match.</pre> <p>[base/gximono.c base/gximage1.c base/gximage2.c base/gximage3.c base/gximage4.c base/gximage.h base/gximag3x.c base/gsiparam.h]</p> </blockquote> @@ -38165,7 +38487,8 @@ Remove DOS line endings from .gitignore files.</pre> 2011-03-01T17:18:30.158752Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for error introduced in non-SSE2 code when I removed the inclusion of the transfer function into the threshold values.</pre> +Fix for error introduced in non-SSE2 code when I removed the inclusion +of the transfer function into the threshold values.</pre> <p>[base/gximono.c]</p> </blockquote> @@ -38238,7 +38561,8 @@ Silence a compiler (scan-build) warning about a variable never being used.</pre> 2011-02-28T05:23:46.157854Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for mis-scale on decode for render mono cache. Fixes improper rendering of 148-11.ps with new halftone code.</pre> +Fix for mis-scale on decode for render mono cache. Fixes improper rendering +of 148-11.ps with new halftone code.</pre> <p>[base/gxipixel.c]</p> </blockquote> @@ -38246,7 +38570,9 @@ Fix for mis-scale on decode for render mono cache. Fixes improper rendering of 2011-02-27T23:26:10.406657Z Michael Vrhel</strong></p> <blockquote> <pre> -Removal (or inactivation) of code to include inverse of transfer function in the threshold values. Also minor fix for scaling issue in halftone code in portrait mode. Code is inactive so no regression diffs expected.</pre> +Removal (or inactivation) of code to include inverse of transfer function in +the threshold values. Also minor fix for scaling issue in halftone code in +portrait mode. Code is inactive so no regression diffs expected.</pre> <p>[base/gximono.c base/gsht.c]</p> </blockquote> @@ -38254,7 +38580,14 @@ Removal (or inactivation) of code to include inverse of transfer function in the 2011-02-27T23:23:30.287293Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for a bug that was introduced with the ICC branch. This was causing a mismatch between banded an unbanded rendering and in particular had rendering errors in banded mode when rendering PS and PDF files that had a non identity transfer function. Minor progression diffs in many files with very visible progressions in 246-01.ps, 258-01.ps as examples. What was happening is that when running in clist mode, we were not recognizing that a transfer function was present when doing the ICC branch. Stumble upon this working the transfer function in with the new threshold based halftoning code.</pre> +Fix for a bug that was introduced with the ICC branch. This was causing a +mismatch between banded an unbanded rendering and in particular had rendering +errors in banded mode when rendering PS and PDF files that had a non identity +transfer function. Minor progression diffs in many files with very visible +progressions in 246-01.ps, 258-01.ps as examples. What was happening is that +when running in clist mode, we were not recognizing that a transfer function was +present when doing the ICC branch. Stumble upon this working the transfer function +in with the new threshold based halftoning code.</pre> <p>[base/gxipixel.c]</p> </blockquote> @@ -38332,7 +38665,8 @@ A quick experiment in adding 0.5 rather than epsilon shows worse results. 2011-02-25T19:49:39.160812Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that we only do the fast code if we are in portrait or landscape mode. Skewed objects will have to use the rect fill method.</pre> +Fix so that we only do the fast code if we are in portrait or landscape mode. +Skewed objects will have to use the rect fill method.</pre> <p>[base/gximono.c]</p> </blockquote> @@ -38340,7 +38674,11 @@ Fix so that we only do the fast code if we are in portrait or landscape mode. S 2011-02-25T19:33:55.727547Z Michael Vrhel</strong></p> <blockquote> <pre> -Addition of code to incorporate the inverse of the transfer curve into the threshold matrix. If the curve is an inverting type (e.g. 0 to 1 and 1 to 0) then a the thresholding comparison is switched. Also, if the curve is not monotonic, it can not be inverted and we revert to the old rect fill method. This commit has the code disabled so there should not be any regressions.</pre> +Addition of code to incorporate the inverse of the transfer curve into the +threshold matrix. If the curve is an inverting type (e.g. 0 to 1 and 1 to 0) +then a the thresholding comparison is switched. Also, if the curve is not +monotonic, it can not be inverted and we revert to the old rect fill method. +This commit has the code disabled so there should not be any regressions.</pre> <p>[base/lib.mak base/gximono.c base/gzht.h base/gxdht.h base/gsht.c]</p> </blockquote> @@ -38529,7 +38867,9 @@ Forgot this file inthe last commit. Sorry! 2011-02-22T19:52:43.275685Z Michael Vrhel</strong></p> <blockquote> <pre> -Merge of halftone branch into the trunk. The new rendering code is actually disabled with this commit. As such, there should not be any testing differences.</pre> +Merge of halftone branch into the trunk. The new rendering code is actually +disabled with this commit. As such, there should not be any testing +differences.</pre> <p>[base/gxipixel.c base/lib.mak base/Makefile.in base/gxcie.h /trunk/gs base/gsht.c base/gxcmap.c psi/msvc.mak ghostscript.vcproj base/gximono.c base/gzht.h base/gxidata.c base/configure.ac base/gxdht.h base/gxcmap.h base/gxicolor.c base/gximage.h base/gsciemap.c]</p> </blockquote> @@ -39012,7 +39352,7 @@ please visit <a href="http://bugs.ghostscript.com/">bugs.ghostscript.com</a>. <p> No recorded incompatible changes. -<h3><a name="9.01_changelog"></a>Changelog</h3> +<h3><a name="9.01_Changelog"></a>Changelog</h3> <p><strong><a name="2011-02-07T141027.833602Z"></a> 2011-02-07T14:10:27.833602Z Chris Liddell</strong></p> @@ -39957,14 +40297,18 @@ Cluster testing shows no changes. <pre> Fix for a number of issues found by Ray with the halftone creation tool. -These include a crash for a divide by zero in the gcd function (caused failure at 0 degree screen generation) +These include a crash for a divide by zero in the gcd function (caused failure +at 0 degree screen generation) Fix so that the Holladay screen is no longer created as an output option. Fix in ppm output header. Fix in how the lpi is selected. Fix for when we have a screen that has essentially one dot (also caused a crash). Addition of a ReadMe. -A lot more testing is needed, in particular, the dithering of the dots in the macro-screens needs additional testing and the relationship between the desired number of quantization levels and the size of the screen needs to be properly computed. There is a list of features that need to be added described in the ReadMe. </pre> +A lot more testing is needed, in particular, the dithering of the dots in the +macro-screens needs additional testing and the relationship between the desired +number of quantization levels and the size of the screen needs to be properly +computed. There is a list of features that need to be added described in the ReadMe. </pre> <p>[toolbin/color/halftone/halfttoning/halfttoning.vcproj toolbin/color/halftone/README toolbin/color/halftone/halfttoning/halftone.c]</p> </blockquote> @@ -39993,7 +40337,13 @@ the problems. 2011-01-11T00:49:20.559732Z Michael Vrhel</strong></p> <blockquote> <pre> -Hopefully a fix for indeterminism introduced in rev 12005. The source of this was that the cups and psdcmyk device are now using the older slower color image rendering function due to the fact that they have non-standard color mapping procedures. Missing parenthesis were introduced when the ICC branch was merged into the trunk which was the source of the issue. This was causing a check for color range mask testing even when the image was not a type 4.</pre> +Hopefully a fix for indeterminism introduced in rev 12005. The +source of this was that the cups and psdcmyk device are now using +the older slower color image rendering function due to the fact that +they have non-standard color mapping procedures. Missing parenthesis +were introduced when the ICC branch was merged into the trunk which was +the source of the issue. This was causing a check for color range mask +testing even when the image was not a type 4.</pre> <p>[base/gxicolor.c]</p> </blockquote> @@ -40115,7 +40465,8 @@ CUPS Raster device: Some clean-up. 2011-01-08T10:36:56.827100Z Till Kamppeter</strong></p> <blockquote> <pre> -CUPS Raster: Another approach to fix both bug #691733 and #690435: Set _old values at the beginning of the cups_put_params() function. +CUPS Raster: Another approach to fix both bug #691733 and #690435: Set _old +values at the beginning of the cups_put_params() function. </pre> <p>[cups/gdevcups.c]</p> </blockquote> @@ -40124,7 +40475,8 @@ CUPS Raster: Another approach to fix both bug #691733 and #690435: Set _old valu 2011-01-07T23:33:17.663910Z Till Kamppeter</strong></p> <blockquote> <pre> -CUPS Raster output device: Use positive values (1) as dummy values to mark that the color depth has changed and therefore memory needs to get rallocated +CUPS Raster output device: Use positive values (1) as dummy values to mark +that the color depth has changed and therefore memory needs to get rallocated WEith this both bug #691733 and bug #690435 get fixed, but this is not necessarily he right and best solution. @@ -40146,7 +40498,16 @@ Fixed search-and-replace error in "cups" output device, bug 691871. 2011-01-07T04:49:42.455234Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that we do not do the ICC optimized flow for color images when our target device does not have standard color mapping procedures. This occurs for example, in the case for the CUPs device where the color mapping procedures map CMYK, RGB and Gray to the current CUPs device color space. For standard gray, RGB and CMYK devices these procedures are avoided as the CMM performs all the required mappings. This commit will show differences in the files for the cups device as well as the psdcmyk device, which also should be using the non-optimized flow due to the use of CMYK + spot colorants, which will not be managed correctly by the CMM in general. The differences int the psdcmyk files that do not have extra spot colorants are tiny. This should fix bug 691760.</pre> +Fix so that we do not do the ICC optimized flow for color images when our +target device does not have standard color mapping procedures. This occurs +for example, in the case for the CUPs device where the color mapping procedures +map CMYK, RGB and Gray to the current CUPs device color space. For standard +gray, RGB and CMYK devices these procedures are avoided as the CMM performs +all the required mappings. This commit will show differences in the files for the +cups device as well as the psdcmyk device, which also should be using the non-optimized +flow due to the use of CMYK + spot colorants, which will not be managed correctly by +the CMM in general. The differences int the psdcmyk files that do not have extra spot +colorants are tiny. This should fix bug 691760.</pre> <p>[base/gxi12bit.c base/gdevp14.c base/lib.mak base/gxcmap.c base/gxiscale.c base/gdevnfwd.c base/gxcmap.h base/gxicolor.c]</p> </blockquote> @@ -40206,7 +40567,8 @@ Fix three compiler warnings in revision 11997 2011-01-05T15:28:39.325806Z Till Kamppeter</strong></p> <blockquote> <pre> -Use the "x11" output device as default output device for an X-enabled Ghostscript, as "x11alpha" is too buggy +Use the "x11" output device as default output device for an X-enabled +Ghostscript, as "x11alpha" is too buggy The simple call "gs <file>" is a common call to check a PostScript file when debugging printing problems. Unfortunately, this call uses @@ -40253,7 +40615,14 @@ the patch. Bug 691863. 2011-01-04T18:19:41.129921Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that the presence of source black and white are properly detected with the ICC color management changes. This detection is useful for the optimization of certain ROPs. Previously black and white were detected from looking at the device color. This was a problem since the device black color is usually not pure for a CMYK printer with the ICC changes. This fix updates the detection function so that it looks at the source color and maps it to the default RGB color space where black and white are well defined. +Fix so that the presence of source black and white are properly detected +with the ICC color management changes. This detection is useful for the +optimization of certain ROPs. Previously black and white were detected +from looking at the device color. This was a problem since the device +black color is usually not pure for a CMYK printer with the ICC changes. +This fix updates the detection function so that it looks at the source +color and maps it to the default RGB color space where black and white +are well defined. </pre> <p>[base/gxipixel.c base/lib.mak]</p> </blockquote> @@ -40547,7 +40916,19 @@ No differences expected. 2010-12-22T18:48:13.456231Z Michael Vrhel</strong></p> <blockquote> <pre> -Initial commit of code for creating halftone screens. This code needs additional debugging, especially in the case of edge parameters. It will currently create threshold arrays based upon desired lpi, angle, quantization levels, and device resolution. The method is restricted to angles that are the arctangent of rational numbers. Every attempt is made to achieve the requested lpi by using the rational angle that achieves an lpi over the requested value. Since there is a trade off between lpi and quantization levels, the requested quantization levels are obtained through dithering of the dot cells within the supercell. Essentially, the dots within the supercell do not all take on the same values and can grow at different rates in a visually pleasing manner. There is still a bit of work to do still on this dithering as well as controlling the rate of growth for the dots.</pre> +Initial commit of code for creating halftone screens. This code needs +additional debugging, especially in the case of edge parameters. It +will currently create threshold arrays based upon desired lpi, angle, +quantization levels, and device resolution. The method is restricted +to angles that are the arctangent of rational numbers. Every attempt is +made to achieve the requested lpi by using the rational angle that achieves +an lpi over the requested value. Since there is a trade off between lpi +and quantization levels, the requested quantization levels are obtained +through dithering of the dot cells within the supercell. Essentially, the +dots within the supercell do not all take on the same values and can grow at +different rates in a visually pleasing manner. There is still a bit of work +to do still on this dithering as well as controlling the rate of growth for +the dots.</pre> <p>[toolbin/color/halftone toolbin/color/halftone/halfttoning.sln toolbin/color/halftone/halfttoning/halfttoning.vcproj toolbin/color/halftone/halfttoning toolbin/color/halftone/halfttoning/halftone.c]</p> </blockquote> @@ -40896,7 +41277,8 @@ Thanks to ubitux@gmail.com for analysis of the problem. Bug 691831. 2010-12-10T19:50:53.800825Z Michael Vrhel</strong></p> <blockquote> <pre> -Removal of Smask_is_CIE flag in the code as well as removal of code that is no longer used in the soft mask rendering.</pre> +Removal of Smask_is_CIE flag in the code as well as removal of code that +is no longer used in the soft mask rendering.</pre> <p>[base/gdevp14.c base/gdevp14.h base/gstrans.c base/gstparam.h base/gxblend.c base/gstrans.h base/gxblend.h]</p> </blockquote> @@ -40947,7 +41329,8 @@ so far is DSC-compliant as-is. 2010-12-10T03:06:40.558274Z Michael Vrhel</strong></p> <blockquote> <pre> -Apply proper alpha blending to compute luminosity of mask per the PDF specification. Fixes bug 691822</pre> +Apply proper alpha blending to compute luminosity of mask per the PDF +specification. Fixes bug 691822</pre> <p>[base/gdevp14.c]</p> </blockquote> @@ -41046,7 +41429,8 @@ so far is DSC-compliant as-is. <pre> pdfwrite enhancement : more work towards DSC compliant ps2write output -This should now output pages in the correct order, with %%Page:/%%PageTrailer comments. +This should now output pages in the correct order, with %%Page:/%%PageTrailer +comments. Still need to address Resource comments and definitions. Committed so that a user can try out the code. No differences expected. @@ -41058,7 +41442,10 @@ Committed so that a user can try out the code. No differences expected. 2010-12-06T20:30:42.463413Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for bug 691466. Problem was caused by the DeviceN alternate color space being Lab and the color values not being properly decoded to enable use of the lab ICC profile. A few progressions in the cluster data base with this commit.</pre> +Fix for bug 691466. Problem was caused by the DeviceN alternate color +space being Lab and the color values not being properly decoded to enable +use of the lab ICC profile. A few progressions in the cluster data base +with this commit.</pre> <p>[base/gscdevn.c base/gdevp14.c base/gsicc.c]</p> </blockquote> @@ -41084,7 +41471,8 @@ tests for low values of bits per plane. Bug 691816, customer 532. 2010-12-06T16:07:30.222320Z regression</strong></p> <blockquote> <pre> -Limit clusterpush.pl bmpcmp jobs to 10 megs of changes per file in addition to the 100 changes per file limit. +Limit clusterpush.pl bmpcmp jobs to 10 megs of changes per file in addition +to the 100 changes per file limit. </pre> <p>[toolbin/localcluster/checkSize.pl toolbin/localcluster/clustermonitor.pl toolbin/localcluster/clustermaster.pl toolbin/localcluster/build.pl toolbin/localcluster/run.pl]</p> </blockquote> @@ -41093,7 +41481,11 @@ Limit clusterpush.pl bmpcmp jobs to 10 megs of changes per file in addition to t 2010-12-04T21:12:37.349224Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for bug 691724. The issue was due to a bug in the code that creates equivalent ICC profiles from CIEABC types. This has a pile of progressions in the cluster data base. I stepped through them with bmpcmp and they appeared to be correct to me. I also altered the DefaultRGB PS color space to by in-sync with the D50 ICC sRGB based default that we are currently using. </pre> +Fix for bug 691724. The issue was due to a bug in the code that creates +equivalent ICC profiles from CIEABC types. This has a pile of progressions +in the cluster data base. I stepped through them with bmpcmp and they +appeared to be correct to me. I also altered the DefaultRGB PS color space +to by in-sync with the D50 ICC sRGB based default that we are currently using. </pre> <p>[base/gsicc_create.c Resource/ColorSpace/DefaultRGB]</p> </blockquote> @@ -41169,7 +41561,14 @@ Remove unused variable.</pre> 2010-12-02T17:09:45.886919Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for bug 691803. This provides a fix for cases where we have soft masks embedded within other soft masks. Such rare cases are detected and when they occur and the soft mask type is luminosity, the alpha channel of the soft mask buffer is pre-blended with the luminosity data to give the proper mask values. There appears to a be change in fts_33xx.xps from this commit. However, it appears to me that this file was not being rendered properly, compared to the windows xps viewer, prior to the commit either. I will file a bug related to this issue.</pre> +Fix for bug 691803. This provides a fix for cases where we have soft masks +embedded within other soft masks. Such rare cases are detected and when they +occur and the soft mask type is luminosity, the alpha channel of the soft +mask buffer is pre-blended with the luminosity data to give the proper mask +values. There appears to a be change in fts_33xx.xps from this commit. +However, it appears to me that this file was not being rendered properly, +compared to the windows xps viewer, prior to the commit either. I will file +a bug related to this issue.</pre> <p>[base/gdevp14.c base/gdevp14.h base/gxblend.c base/gxblend.h]</p> </blockquote> @@ -41200,9 +41599,14 @@ Additional debug code to help in soft mask problems.</pre> 2010-12-01T05:16:55.267986Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that the blend compositor actions are only removed from the clist compositor queue if they are completely over-ridden by a subsequent compositor action. Previously no check was made to see that the same settings were being up-dated by the new action. +Fix so that the blend compositor actions are only removed from the clist +compositor queue if they are completely over-ridden by a subsequent compositor +action. Previously no check was made to see that the same settings were being +up-dated by the new action. -This fixes two P1 customer bugs and has several progressions in the test suite but one file Bug691783.pdf has both regressions and progressions. I will get the page 18 regressions into a bug.</pre> +This fixes two P1 customer bugs and has several progressions in the test suite +but one file Bug691783.pdf has both regressions and progressions. I will get +the page 18 regressions into a bug.</pre> <p>[base/gdevp14.c base/gxclimag.c base/gxcldev.h]</p> </blockquote> @@ -41210,7 +41614,11 @@ This fixes two P1 customer bugs and has several progressions in the test suite b 2010-11-29T21:12:32.441057Z regression</strong></p> <blockquote> <pre> -Additonal improvement in the cluster's ability to be able to recover from machines going down late in the run. Machines are put into a standby state when there are no jobs left to send and they have processed all of their jobs until all machines are in the standby state, then all the machines are released from standby and can upload their logs +Additonal improvement in the cluster's ability to be able to recover from +machines going down late in the run. Machines are put into a standby state +when there are no jobs left to send and they have processed all of their jobs +until all machines are in the standby state, then all the machines are released +from standby and can upload their logs </pre> <p>[toolbin/localcluster/clustermaster.pl toolbin/localcluster/run.pl]</p> </blockquote> @@ -41219,7 +41627,11 @@ Additonal improvement in the cluster's ability to be able to recover from machin 2010-11-29T18:55:03.883221Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for issues with the default ICC directory. The PS interpreter now checks if the default name is OK before setting to LIBPATH/iccprofiles . Also, the current name is first tested before we prepend with the directory name, to avoid doing double applications of the profile directory. Thanks to Ray for the fixes in gs_lev2.ps</pre> +Fix for issues with the default ICC directory. The PS interpreter now checks +if the default name is OK before setting to LIBPATH/iccprofiles . Also, the +current name is first tested before we prepend with the directory name, to avoid +doing double applications of the profile directory. Thanks to Ray for the fixes +in gs_lev2.ps</pre> <p>[base/gsicc_manage.c Resource/Init/gs_lev2.ps]</p> </blockquote> @@ -41227,7 +41639,12 @@ Fix for issues with the default ICC directory. The PS interpreter now checks if 2010-11-29T18:30:38.060525Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for bug 691748. The idle optimizations for the softmask are not really valid since we have since created the proper bounding box for the soft mask in a previous commit. In the cluster push testing, some files came back as having problems with the psdcmyk device. Checking, it appears that these issues are not related to this fix but are another bug. I am working on this now and will submit a bug.</pre> +Fix for bug 691748. The idle optimizations for the softmask are not +really valid since we have since created the proper bounding box for +the soft mask in a previous commit. In the cluster push testing, some +files came back as having problems with the psdcmyk device. Checking, +it appears that these issues are not related to this fix but are another +bug. I am working on this now and will submit a bug.</pre> <p>[base/gdevp14.c]</p> </blockquote> @@ -41370,7 +41787,20 @@ Style clean up of gdevp14.c for white space, comments, long lines and dead code. 2010-11-24T17:44:39.808162Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that we handle the \B command properly when we have transparency. The stroke should be drawn in a knock-out fashion rather than blended with the fill. This was achieved by adding in the push of a knockout transparency group for the stroke operation. The opacity for that group had to be 1 rather than what ever the current graphic state was (otherwise you end up with the opacity applied twice). That change revealed an issue in the clist when a transparency group is pushed where the opacity for the pdf14 clist device was being altered without having the information passed into the clist. Fixing that required a few changes to make sure that the blend parameter changes for the transparency group end up written in the same bands as the group push rather than all bands like the normal blend parameter change compositor action does. A few changes were needed in the clist compositor writing code to make sure that this special blend parameter change did not push a new cropping item on the cropping stack. This commit results in a lot of progressions. However, the cluster push revealed a couple files fts_06_0608.pdf.pdf.ppmraw for example, which may have an issue. These are being checked and if found to be an issue a new bug report will be filed.</pre> +Fix so that we handle the \B command properly when we have transparency. The stroke +should be drawn in a knock-out fashion rather than blended with the fill. This was +achieved by adding in the push of a knockout transparency group for the stroke operation. +The opacity for that group had to be 1 rather than what ever the current graphic state was +(otherwise you end up with the opacity applied twice). That change revealed an issue in the +clist when a transparency group is pushed where the opacity for the pdf14 clist device was +being altered without having the information passed into the clist. Fixing that required a +few changes to make sure that the blend parameter changes for the transparency group end up +written in the same bands as the group push rather than all bands like the normal blend parameter +change compositor action does. A few changes were needed in the clist compositor writing code to +make sure that this special blend parameter change did not push a new cropping item on the cropping +stack. This commit results in a lot of progressions. However, the cluster push revealed a couple +files fts_06_0608.pdf.pdf.ppmraw for example, which may have an issue. These are being checked and +if found to be an issue a new bug report will be filed.</pre> <p>[Resource/Init/pdf_ops.ps base/gdevp14.c base/gxclimag.c base/gxblend.c base/gstrans.h base/gxblend.h]</p> </blockquote> @@ -41576,7 +42006,20 @@ lj*.prn files did not show this problem. 2010-11-16T14:48:31.620067Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that the initial gray color spaces in the graphic state are properly color managed. Previously, if we immediately started drawing in the document with a gray color space, the initial un-managed color space in the graphic state was used and this was not associated with the specified gray source profile. With this fix we initialize the stroking and filling color spaces to be ICC color spaces associated with the profile for default_gray in the icc manager. Also a fix for an issue in littleCMS. When merging profiles, littleCMS will often do an optimization where it approximates 1-D LUTs with an exponent operation for use during merging and interpolation of the profile structures. If the curve is very steep, as in like a step function, it should not do this approximation. This was an issue when we had profiles that provided thresholding operations with their 1-D LUTs. I spoke with Marti about this issue a couple weeks ago. This commit will create over 6000 differences in the regression test. I reviewed many of these and they all are minor differences in gray colors as expected. These are differences where we were drawing unmanaged colors.</pre> +Fix so that the initial gray color spaces in the graphic state are properly color +managed. Previously, if we immediately started drawing in the document with a gray +color space, the initial un-managed color space in the graphic state was used +and this was not associated with the specified gray source profile. With this +fix we initialize the stroking and filling color spaces to be ICC color spaces +associated with the profile for default_gray in the icc manager. Also a fix for +an issue in littleCMS. When merging profiles, littleCMS will often do an optimization +where it approximates 1-D LUTs with an exponent operation for use during merging and +interpolation of the profile structures. If the curve is very steep, as in like a step +function, it should not do this approximation. This was an issue when we had profiles +that provided thresholding operations with their 1-D LUTs. I spoke with Marti about +this issue a couple weeks ago. This commit will create over 6000 differences in the +regression test. I reviewed many of these and they all are minor differences in gray +colors as expected. These are differences where we were drawing unmanaged colors.</pre> <p>[base/gsicc_manage.c psi/zusparam.c base/gsicc_manage.h lcms/src/cmsgmt.c]</p> </blockquote> @@ -41685,7 +42128,11 @@ Make a macro for the default ICC profile name and set it in the proper locations 2010-11-06T15:36:18.568592Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for a string handling bug that occurred when the device ICC profile name was smaller than the default device profile name. Also, additional code to ensure that the ICC path and the device profile name are properly combined when needed. Finally, if the device profile name is given as an absolute name the icc directory is not added to it.</pre> +Fix for a string handling bug that occurred when the device ICC profile name +was smaller than the default device profile name. Also, additional code to +ensure that the ICC path and the device profile name are properly combined +when needed. Finally, if the device profile name is given as an absolute +name the icc directory is not added to it.</pre> <p>[base/lib.mak base/gsdparam.c base/gsicc_manage.c]</p> </blockquote> @@ -41693,7 +42140,8 @@ Fix for a string handling bug that occurred when the device ICC profile name was 2010-11-05T22:12:05.617541Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that when compositing with tags, the tos tag data has no effect on the nos tag data if the pixel alpha value is 0. Fixes Bug 691752.</pre> +Fix so that when compositing with tags, the tos tag data has no effect on +the nos tag data if the pixel alpha value is 0. Fixes Bug 691752.</pre> <p>[base/gxblend1.c]</p> </blockquote> @@ -41729,7 +42177,8 @@ Bug 691750. 2010-11-04T19:13:08.201769Z Michael Vrhel</strong></p> <blockquote> <pre> -Increase in curve size to enable sharper cut offs (i.e. no interpolation of curve points) for thresholding profiles. </pre> +Increase in curve size to enable sharper cut offs (i.e. no interpolation of +curve points) for thresholding profiles. </pre> <p>[toolbin/color/icc_creator/ICC_Creator/icc_create.cpp]</p> </blockquote> @@ -41737,7 +42186,8 @@ Increase in curve size to enable sharper cut offs (i.e. no interpolation of curv 2010-11-03T20:44:07.993086Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix to avoid potential crash instead of error if an improper file name is given for the device ICC profile.</pre> +Fix to avoid potential crash instead of error if an improper file name +is given for the device ICC profile.</pre> <p>[base/gsicc_manage.c]</p> </blockquote> @@ -41760,7 +42210,8 @@ No cluster differences expected. 2010-11-01T23:59:27.933765Z Michael Vrhel</strong></p> <blockquote> <pre> -Performance fix so that the md5 code is not used to hash the rendering conditions for the icc link. </pre> +Performance fix so that the md5 code is not used to hash the rendering +conditions for the icc link. </pre> <p>[base/gsicc_cache.c base/gscms.h]</p> </blockquote> @@ -41792,7 +42243,11 @@ Bug 691740, customer 384. 2010-10-29T23:40:30.279741Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that the image clues array is dynamically allocate only when needed as opposed to being a static array in gx_image_enum. clues is used only in the case of monochrome or indexed with bps <= 8 and masked images. Another optimization to do is to make it allocate only 2 entries for the masked case rather than all 256.</pre> +Fix so that the image clues array is dynamically allocate only when needed +as opposed to being a static array in gx_image_enum. clues is used only +in the case of monochrome or indexed with bps <= 8 and masked images. +Another optimization to do is to make it allocate only 2 entries for the +masked case rather than all 256.</pre> <p>[base/gxipixel.c base/gxidata.c base/gximage.h]</p> </blockquote> @@ -41845,7 +42300,8 @@ No differences expected. 2010-10-28T20:41:14.761110Z Michael Vrhel</strong></p> <blockquote> <pre> -Addition in profile creation tool to create Gray ICC profiles with abrupt thresholds. Needed for solution to bug 691737</pre> +Addition in profile creation tool to create Gray ICC profiles with +abrupt thresholds. Needed for solution to bug 691737</pre> <p>[toolbin/color/icc_creator/ICC_Creator/icc_create.h toolbin/color/icc_creator/ICC_Creator/ICC_CreatorDlg.h toolbin/color/icc_creator/ICC_Creator/resource.h toolbin/color/icc_creator/ICC_Creator/ICC_Creator.rc toolbin/color/icc_creator/ICC_Creator/icc_create.cpp toolbin/color/icc_creator/ICC_Creator/ICC_CreatorDlg.cpp]</p> </blockquote> @@ -41853,7 +42309,8 @@ Addition in profile creation tool to create Gray ICC profiles with abrupt thresh 2010-10-28T19:57:51.569853Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for issues that arise when the embedded icc profile is the same as one of the default icc profiles and we are using pdfwrite. This should fix 691731.</pre> +Fix for issues that arise when the embedded icc profile is the same as one +of the default icc profiles and we are using pdfwrite. This should fix 691731.</pre> <p>[base/gsicc_create.c base/gsicc_manage.c base/gscms.h base/gsciemap.c]</p> </blockquote> @@ -41903,7 +42360,14 @@ Bug 691700. 2010-10-28T06:12:53.429268Z Michael Vrhel</strong></p> <blockquote> <pre> -Code to speed up cases where a file contains a lot of small images that are embedded in the clist as high level images. Previously, for every high level image, the serialized ICC source data was read out of the clist at a different clist file location, which required a fseek, a fread and then another fseek. This occurred even if all the images shared the same profile. The cost of file i/o for this can become significant if we have a lot of images. With this commit, the reading of the profile data is delayed and will only occur if a link using that profile does not already exist in the link cache. </pre> +Code to speed up cases where a file contains a lot of small images that are +embedded in the clist as high level images. Previously, for every high level +image, the serialized ICC source data was read out of the clist at a different +clist file location, which required a fseek, a fread and then another fseek. +This occurred even if all the images shared the same profile. The cost of +file i/o for this can become significant if we have a lot of images. With +this commit, the reading of the profile data is delayed and will only occur +if a link using that profile does not already exist in the link cache. </pre> <p>[base/gxclpath.c base/gxclimag.c base/gxclist.h base/gxclrast.c]</p> </blockquote> @@ -42042,7 +42506,9 @@ Removal of accidental commit of my own path for the wts halftone planes. 2010-10-26T18:50:49.267717Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that wtsimidi device works again. I had the device using the wrong structure for maintaining its device link that maps the contone RGB data to CMYK.</pre> +Fix so that wtsimidi device works again. I had the device using the wrong +structure for maintaining its device link that maps the contone RGB data to +CMYK.</pre> <p>[base/gdevwts.c]</p> </blockquote> @@ -42742,7 +43208,17 @@ new code. I'll add this to the test repo shortly. 2010-10-12T05:52:16.851470Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for a large memory leak that can occur when a pattern cache entry is freed and a transparency buffer exists in the entry. A problem was that the pdf14 device, which contains pointers to the buffer, had its close device procedure set to forward due to the device being set in a disabled state during pattern_paint_finish. The close device proc for the pdf14 device contains the calls to actually free the buffers so this was not occurring (instead we were forwarding to another device). In addition, the pdf14 device itself was not being destroyed. With this commit, when the pattern entry is freed, the pdf14 device is now closed, which frees the buffers, and the pdf14 device is properly reference count decremented to result in the device itself getting freed. Regression run revealed no problems.</pre> +Fix for a large memory leak that can occur when a pattern cache entry +is freed and a transparency buffer exists in the entry. A problem was +that the pdf14 device, which contains pointers to the buffer, had its +close device procedure set to forward due to the device being set in a +disabled state during pattern_paint_finish. The close device proc for +the pdf14 device contains the calls to actually free the buffers so this +was not occurring (instead we were forwarding to another device). In addition, +the pdf14 device itself was not being destroyed. With this commit, when the +pattern entry is freed, the pdf14 device is now closed, which frees the buffers, +and the pdf14 device is properly reference count decremented to result in the +device itself getting freed. Regression run revealed no problems.</pre> <p>[psi/zpcolor.c base/gxpcmap.c]</p> </blockquote> @@ -43048,7 +43524,9 @@ Clean up of a few comments about device profiles</pre> 2010-10-05T20:18:10.046358Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for error in detecting the presence of a device profile set in the command line. Unfortunately, the device was not being reset from the default profile based upon the setting.</pre> +Fix for error in detecting the presence of a device profile set in the +command line. Unfortunately, the device was not being reset from the +default profile based upon the setting.</pre> <p>[base/gsicc_manage.c]</p> </blockquote> @@ -43311,7 +43789,21 @@ Removal of debug code that was accidentally committed.</pre> 2010-09-23T19:45:27.249371Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that objects tag information makes it through transparency rendering AND the clist. An issue was that the pdf14 encode and decode procedures are used as opposed to the target device encode and decode procedures and it is through a value in the color index that we currently communicate the object type through the clist. When we are in page rendering mode, it is easy to get the current object from mem->gs_lib_ctx->BITTAG, but this is not set correctly in clist rendering if for example a glyph is stored in the clist as a mask fill. Instead the information about the object is extracted from the color index. So, to make this work, we had to introduce an encode method for the pdf14 device that incorporates the tag information and also make sure that the bit depth for the pdf14 color info value is incremented appropriately so that the extra byte is stored and extracted from the clist. The object type is then recovered during the pdf14 mark fill rect procedure. This was tested with the updated bitrgbtags device using a custom file that has overlapping text, image and path objects with varying transparency amounts. </pre> +Fix so that objects tag information makes it through transparency rendering +AND the clist. An issue was that the pdf14 encode and decode procedures are +used as opposed to the target device encode and decode procedures and it is +through a value in the color index that we currently communicate the object +type through the clist. When we are in page rendering mode, it is easy to +get the current object from mem->gs_lib_ctx->BITTAG, but this is not set +correctly in clist rendering if for example a glyph is stored in the clist as a +mask fill. Instead the information about the object is extracted from the color +index. So, to make this work, we had to introduce an encode method for the +pdf14 device that incorporates the tag information and also make sure that the bit +depth for the pdf14 color info value is incremented appropriately so that the extra +byte is stored and extracted from the clist. The object type is then recovered +during the pdf14 mark fill rect procedure. This was tested with the updated +bitrgbtags device using a custom file that has overlapping text, image and path +objects with varying transparency amounts. </pre> <p>[base/gdevp14.c base/gsimage.c base/gsutil.h base/gstext.c base/gsdps1.c base/gdevbit.c base/gdevmem.c base/gxblend1.c base/gspaint.c base/gdevddrw.c base/gsutil.c base/gxclrast.c base/gxblend.h]</p> </blockquote> @@ -43478,7 +43970,28 @@ Removal of unused variable introduced in last commit.</pre> 2010-09-17T05:40:48.428712Z Michael Vrhel</strong></p> <blockquote> <pre> -Addition of support to enable persistence of objects tag information through transparency rendering. In the current code base, transparency blending erases all knowledge about the objects that were drawn and blended, setting the entire object to image type. With this commit, the tag information is retained through blending by doing a bit-wise or of the tag values. When a device supports tags, the pdf14 device will create an additional plane to maintain the tag data information. Blending of the tag information occurs in pdf14_mark_fill_rectangle, pdf14_mark_fill_rectangle_ko_simple and pdf14_compose_group. A new device procedure called put_image is added. This is called by the pdf14_put_image operation, which enables the communication of the tag information to the target device. pdf14_put_image will first attempt to pass the alpha channel and the image data not scaled by the alpha channel and the tag data to the target device. The planar offset location of the alpha and tag data is communicated in the put_image procedure interface. If the target device cannot handle this form of the data, it should return 0. The pdf14_put_image operation will then blend the alpha data and attempt the put_image again but this time with an alpha offset of 0 to indicate that there is no alpha data. Note that the alpha data remains valid for those devices that still want the alpha but also want to have the graphics library do a premultiplcation of the alpha with the data. Details of this interface will be added to the documentation. In addition, the bitrgbtags device is being updated to demonstrate the use of the put_image procedure.</pre> +Addition of support to enable persistence of objects tag information through +transparency rendering. In the current code base, transparency blending +erases all knowledge about the objects that were drawn and blended, setting +the entire object to image type. With this commit, the tag information is +retained through blending by doing a bit-wise or of the tag values. When a +evice supports tags, the pdf14 device will create an additional plane to +maintain the tag data information. Blending of the tag information occurs +in pdf14_mark_fill_rectangle, pdf14_mark_fill_rectangle_ko_simple and +pdf14_compose_group. A new device procedure called put_image is added. +This is called by the pdf14_put_image operation, which enables the communication +of the tag information to the target device. pdf14_put_image will first attempt +to pass the alpha channel and the image data not scaled by the alpha channel and +the tag data to the target device. The planar offset location of the alpha and +tag data is communicated in the put_image procedure interface. If the target +device cannot handle this form of the data, it should return 0. The +pdf14_put_image operation will then blend the alpha data and attempt the +put_image again but this time with an alpha offset of 0 to indicate that there +is no alpha data. Note that the alpha data remains valid for those devices that +still want the alpha but also want to have the graphics library do a premultiplcation +of the alpha with the data. Details of this interface will be added to the documentation. +In addition, the bitrgbtags device is being updated to demonstrate the use of the +put_image procedure.</pre> <p>[base/gdevp14.c base/gxdevcli.h base/gxclist.c base/gdevp14.h base/gdevbbox.c cups/gdevcups.c base/gsovrc.c base/gxblend.c base/gxblend1.c base/gdevprn.c base/gsutil.c base/gxblend.h]</p> </blockquote> @@ -43685,7 +44198,7 @@ please visit <a href="http://bugs.ghostscript.com/">bugs.ghostscript.com</a>. <p> No recorded incompatible changes. -<h3><a name="9.00_changelog"></a>Changelog</h3> +<h3><a name="9.00_Changelog"></a>Changelog</h3> <p><strong><a name="2010-09-13T150940.310889Z"></a> 2010-09-13T15:09:40.310889Z Chris Liddell</strong></p> @@ -43790,7 +44303,15 @@ Fix for compiler complaint from commit of rev 11700</pre> 2010-09-08T23:20:36.969829Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix to enable proper mask filling with patterns that have transparency. Major change is in gdevp14.c where begin_type_image and mask_fill procedures now will (if we are filling with a pattern that has transparency) push a transparency group. When we are finished processing the image, the group is popped which enables proper blending. There remains an issue with a special file that Ken created when it is run in c-list mode. A new bug will be opened for this issue. Thanks to Ray for helping with this project and finding a bounding box issue in the creation of the transparency group during c-list reading.</pre> +Fix to enable proper mask filling with patterns that have transparency. +Major change is in gdevp14.c where begin_type_image and mask_fill procedures +now will (if we are filling with a pattern that has transparency) push a +transparency group. When we are finished processing the image, the group is +popped which enables proper blending. There remains an issue with a special +file that Ken created when it is run in c-list mode. A new bug will be opened +for this issue. Thanks to Ray for helping with this project and finding a +bounding box issue in the creation of the transparency group during c-list +reading.</pre> <p>[base/gdevp14.c base/gxclimag.c base/gsptype1.c base/lib.mak base/gxpcmap.c base/gdevpdfb.c base/gsptype1.h base/gstrans.c base/gxpcolor.h base/gxblend1.c base/gxp1fill.c base/gxp1impl.h base/gdevpdfi.c]</p> </blockquote> @@ -44075,7 +44596,13 @@ parameters are not used in these functions. 2010-09-01T06:08:51.456140Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix to avoid issues with subtractive monochrome devices when we have transparency. The gray device pdf14 prototype is used in this case. VERY limited testing indicates that this fixes a crash with the cups device with its default settings and gives proper rendering. More complete testing is required to ensure that proper blending is being performed and to investigate the other process color models that the cups device supports (e.g. cmy). </pre> +Fix to avoid issues with subtractive monochrome devices when we have +transparency. The gray device pdf14 prototype is used in this case. +VERY limited testing indicates that this fixes a crash with the cups +device with its default settings and gives proper rendering. More +complete testing is required to ensure that proper blending is being +performed and to investigate the other process color models that the +cups device supports (e.g. cmy). </pre> <p>[base/gdevp14.c]</p> </blockquote> @@ -44083,7 +44610,15 @@ Fix to avoid issues with subtractive monochrome devices when we have transparenc 2010-08-31T23:21:15.562664Z Michael Vrhel</strong></p> <blockquote> <pre> -Revert back to having pdfwrite handle what to do with PS color spaces instead of using the V4 profile that gsicc_create generates. Also, fix a few issues that existed with pdfwrites handling of those spaces, in particular adjustments are made for non D50 white points. D50 is the required white point for the ICC profile. About 189 pdfwrite test files will report differences. I went through them with bmpcmp. Since the profiles that were generated differ between gsicc_create and pdfwrite minor color differences exist. In addition, there were some regressions that existed, which this revision will fix. </pre> +Revert back to having pdfwrite handle what to do with PS color spaces +instead of using the V4 profile that gsicc_create generates. Also, fix a +few issues that existed with pdfwrites handling of those spaces, in particular +adjustments are made for non D50 white points. D50 is the required white point +for the ICC profile. About 189 pdfwrite test files will report differences. +I went through them with bmpcmp. Since the profiles that were generated +differ between gsicc_create and pdfwrite minor color differences exist. In +addition, there were some regressions that existed, which this revision will +fix. </pre> <p>[psi/zcolor.c base/gdevpdfk.c psi/zimage.c base/gdevpdfc.c base/gsciemap.c]</p> </blockquote> @@ -44450,7 +44985,8 @@ Added support for regression testing of the cups device. 2010-08-12T02:55:40.283339Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix to handle case where the profiledir is NOT set AND there is a change in the process color model for the device AFTER a profile had already been set. </pre> +Fix to handle case where the profiledir is NOT set AND there is a change in +the process color model for the device AFTER a profile had already been set. </pre> <p>[base/gsicc_manage.c]</p> </blockquote> @@ -44468,7 +45004,8 @@ Bug 691536, customer 532. 2010-08-11T23:31:48.385487Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for indeterminism issue that was introduced with changes in 16bit image handling. Last subpixel element was not getting unpacked properly. </pre> +Fix for indeterminism issue that was introduced with changes in 16bit image +handling. Last subpixel element was not getting unpacked properly. </pre> <p>[base/gxi16bit.c]</p> </blockquote> @@ -44500,7 +45037,13 @@ Fix so that if the device process color model changes the profile is updated acc 2010-08-11T16:17:45.421152Z Henry Stiles</strong></p> <blockquote> <pre> -Fix bug # 691532. Do not attempt to clone an image that does not exist, each completed page should have an associated image. We'd like to handle this corrupt file with a better fix, for example the absence of an end page segement is clearly a problem with respect to the specification, but Adobe and Artifex have chosen to support other "off spec" streams so more subtle and less obvious error checking is needed. Thanks to Tim Waugh for analysis on this problem. +Fix bug # 691532. Do not attempt to clone an image that does not exist, +each completed page should have an associated image. We'd like to handle +this corrupt file with a better fix, for example the absence of an end page +segement is clearly a problem with respect to the specification, but Adobe and +Artifex have chosen to support other "off spec" streams so more subtle +and less obvious error checking is needed. Thanks to Tim Waugh for analysis on +this problem. </pre> <p>[jbig2dec/jbig2_page.c]</p> </blockquote> @@ -44541,7 +45084,11 @@ the tests_private/pdf/PDF_1.7_FTS repository was added 2010-08-10T16:20:19.775613Z Michael Vrhel</strong></p> <blockquote> <pre> -Commit to move the ICC profile for the device within the device structure. This will make it easier to handle dynamic changes that may occur to the process color model for the device. Also a move of device profiles into non gc memory and removal of any references to profiles to the GC. A few progressions occur with this commit including Bug689918.pdf testpage.pdf. </pre> +Commit to move the ICC profile for the device within the device structure. +This will make it easier to handle dynamic changes that may occur to the +process color model for the device. Also a move of device profiles into non gc +memory and removal of any references to profiles to the GC. A few progressions +occur with this commit including Bug689918.pdf testpage.pdf. </pre> <p>[base/gxi12bit.c base/gsdevice.c base/gdevpdfk.c base/gxpcmap.c base/gxdevice.h /trunk/ghostpdl/xps/xpsgradient.c base/gdevprn.c base/gdevpsdi.c base/gscsepr.c base/gscpixel.c base/gxcmap.c base/gdevbit.c base/gxclip.c base/gxicolor.c base/gximag3x.c base/gscspace.c base/gsicc.c base/gscdevn.c base/gscolor2.c base/lib.mak base/gxiscale.c base/gsicc_manage.c base/gxcspace.h base/gscicach.c base/gdevnfwd.c base/gxdevcli.h base/gdevp14.c psi/zdevice.c base/gsicc_create.c base/gsicc_cache.c base/gdevp14.h base/gsicc_cache.h base/gxccman.c base/gscms.h base/gxclist.h psi/zusparam.c base/gxshade.c base/gxblend.c base/gsequivc.c base/gsciemap.c]</p> </blockquote> @@ -45070,9 +45617,17 @@ should be "genarch" instead. <pre> Fix for bug 691488. -This commit fixes the issues that we are seeing with the JPEG2000 images in the FTS files EXCEPT for the issues related to SmaskInData. Those images will be addressed in a separate commit and will now be handled in bug 691470. - -With this commit, support is in place for faster 16 bit image rendering due to the improved ICC support, which lets us avoid the multiple conversions from 16 bit to frac to float to unsigned short to byte which occurred in the old flow. Also, the jasper interface will now, when it encounters a 16 bit or 12 bit image, use the higher bit depth renderer and pass the data along. Previously, we were truncating to 8bits in our jasper interface. These changes have been regression tested and checked with bmpcmp. +This commit fixes the issues that we are seeing with the JPEG2000 images in +the FTS files EXCEPT for the issues related to SmaskInData. Those images +will be addressed in a separate commit and will now be handled in bug +691470. +With this commit, support is in place for faster 16 bit image rendering due +to the improved ICC support, which lets us avoid the multiple conversions from +16 bit to frac to float to unsigned short to byte which occurred in the old +flow. Also, the jasper interface will now, when it encounters a 16 bit or +12 bit image, use the higher bit depth renderer and pass the data along. +Previously, we were truncating to 8bits in our jasper interface. These +changes have been regression tested and checked with bmpcmp. </pre> @@ -45101,9 +45656,16 @@ rollback to revision 11564, 11565 broke the build</pre> <pre> Fix for bug 691488. -This commit fixes the issues that we are seeing with the JPEG2000 images in the FTS files EXCEPT for the issues related to SmaskInData. Those images will be addressed in a separate commit and will now be handled in bug 691470. - -With this commit, support is in place for faster 16 bit image rendering due to the improved ICC support, which lets us avoid the multiple conversions from 16 bit to frac to float to unsigned short to byte which occurred in the old flow. Also, the jasper interface will now, when it encounters a 16 bit or 12 bit image, use the higher bit depth renderer and pass the data along. Previously, we were truncating to 8bits in our jasper interface. These changes have been regression tested and checked with bmpcmp. +This commit fixes the issues that we are seeing with the JPEG2000 images +in the FTS files EXCEPT for the issues related to SmaskInData. Those images +will be addressed in a separate commit and will now be handled in bug 691470. +With this commit, support is in place for faster 16 bit image rendering due to +the improved ICC support, which lets us avoid the multiple conversions from 16 +bit to frac to float to unsigned short to byte which occurred in the old flow. +Also, the jasper interface will now, when it encounters a 16 bit or 12 bit image, +use the higher bit depth renderer and pass the data along. Previously, we were +truncating to 8bits in our jasper interface. These changes have been regression +tested and checked with bmpcmp. </pre> @@ -45602,7 +46164,19 @@ configuration dictionary has /BaseState attribute equal /OFF. Mark all OCGs <pre> Fix for bug 691478 -Note that string objects that are maintained as user params must be either allocated in non-gc memory or be a constant in the executable. The problem stems from the way userparams are retained during garbage collection in a param_list (collected by currentuserparams). For some reason this param_list does not get the pointers to strings relocated during the GC. Note that the param_dict itself is correctly updated by reloc, it is just the pointers to the strings in the param_list that are not traced and updated. In this particular case, ICCProfilesDir sets a string in the icc_manager. When a reclaim occurs, the string is relocated (when in non-gc memory and when it is noted to the gc with the proper object descriptor). Then if a set_icc_directory occurs, the user params pointer has NOT been updated and validation problems will occur. Fix for this was to make the string not known to the GC and to allocate in non-gc memory. When icc manager is deallocated, the string is also deallocated.</pre> +Note that string objects that are maintained as user params must be either +allocated in non-gc memory or be a constant in the executable. The problem stems +from the way userparams are retained during garbage collection in a param_list +(collected by currentuserparams). For some reason this param_list does not get +the pointers to strings relocated during the GC. Note that the param_dict itself +is correctly updated by reloc, it is just the pointers to the strings in the +param_list that are not traced and updated. In this particular case, ICCProfilesDir +sets a string in the icc_manager. When a reclaim occurs, the string is relocated +(when in non-gc memory and when it is noted to the gc with the proper object +descriptor). Then if a set_icc_directory occurs, the user params pointer has NOT +been updated and validation problems will occur. Fix for this was to make the string +not known to the GC and to allocate in non-gc memory. When icc manager is deallocated, +the string is also deallocated.</pre> <p>[base/gsicc_manage.c psi/zusparam.c]</p> </blockquote> @@ -45610,7 +46184,10 @@ Note that string objects that are maintained as user params must be either alloc 2010-07-21T00:03:16.900862Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that non-isolated transparency groups are rendered correctly. This fixes a rendering issue with fts_25_2524 and with a few in the test suite. A future optimization will be to avoid the extra buffer push if the blend mode is normal, since in that case we can draw directly into the parent buffer.</pre> +Fix so that non-isolated transparency groups are rendered correctly. This fixes a +rendering issue with fts_25_2524 and with a few in the test suite. A future optimization +will be to avoid the extra buffer push if the blend mode is normal, since in that case we +can draw directly into the parent buffer.</pre> <p>[base/gdevp14.c]</p> </blockquote> @@ -45695,7 +46272,8 @@ No visible difference expected. 2010-07-20T05:56:04.938511Z Michael Vrhel</strong></p> <blockquote> <pre> -Remove noisy warnings if embedded icc profile is not valid. In those cases, we use the default and move on. </pre> +Remove noisy warnings if embedded icc profile is not valid. In those +cases, we use the default and move on. </pre> <p>[psi/zicc.c]</p> </blockquote> @@ -45703,7 +46281,12 @@ Remove noisy warnings if embedded icc profile is not valid. In those cases, we 2010-07-19T21:22:35.957060Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for Bug691474. Source of error was due to icc hash code being read from clist after the transfer function. It should have been read prior to the transfer function. This was the first file we have seen that had a soft mask with a transfer function. Also fix for rendering of this file. The softmasks only uses the alpha channel as opposed to the luminosity of the object. Progression with CityMap-evnice.pdf in test suite. That file must have a alpha style softmask.</pre> +Fix for Bug691474. Source of error was due to icc hash code being read from clist +after the transfer function. It should have been read prior to the transfer function. +This was the first file we have seen that had a soft mask with a transfer function. +Also fix for rendering of this file. The softmasks only uses the alpha channel as +opposed to the luminosity of the object. Progression with CityMap-evnice.pdf in test +suite. That file must have a alpha style softmask.</pre> <p>[base/gdevp14.c base/gstparam.h]</p> </blockquote> @@ -45792,7 +46375,14 @@ This is a partial fix for bug 691408. 2010-07-16T19:58:03.971410Z Michael Vrhel</strong></p> <blockquote> <pre> -Prepend icc directory to device profile name if the default name is used so that we have it during clist reading. This is a fix for the iccprofiles/ problem in 691408 when compile inits is not used. Also, fix so that the profile name is allocated in non-gc memory. This was a source of issues with the userparams dict not seeming to be traced or at least not getting its members relocated if a profile in the icc manager was relocated. This fixes the breaking of the psdcmyk device in rev 11499. Also removal of spurious warning messages.</pre> +Prepend icc directory to device profile name if the default name is +used so that we have it during clist reading. This is a fix for the +iccprofiles/ problem in 691408 when compile inits is not used. Also, +fix so that the profile name is allocated in non-gc memory. This was +a source of issues with the userparams dict not seeming to be traced +or at least not getting its members relocated if a profile in the icc +manager was relocated. This fixes the breaking of the psdcmyk device +in rev 11499. Also removal of spurious warning messages.</pre> <p>[base/gsicc_manage.c]</p> </blockquote> @@ -45863,7 +46453,8 @@ Thanks to Hin-Tak for the patch. Bug 691449. 2010-07-14T21:25:33.726848Z Till Kamppeter</strong></p> <blockquote> <pre> -Allow the CUPS Raster backend alternatively output compressed (version 2) CUPS Raster data (bug #689885). +Allow the CUPS Raster backend alternatively output compressed (version 2) +CUPS Raster data (bug #689885). </pre> <p>[cups/gdevcups.c]</p> </blockquote> @@ -45872,7 +46463,9 @@ Allow the CUPS Raster backend alternatively output compressed (version 2) CUPS R 2010-07-13T18:30:29.088597Z Chris Liddell</strong></p> <blockquote> <pre> -Ensure the local variable into which we read Truetype cmap table data (platform ID, encoding ID etc) is actually large enough to hold all the data we read into it. +Ensure the local variable into which we read Truetype cmap table data +(platform ID, encoding ID etc) is actually large enough to hold all +the data we read into it. Bug 691452 (part 1) @@ -45897,7 +46490,12 @@ Also made some minor syntax changes in PDF/A and PDF/X documentation for greater 2010-07-13T07:04:59.625768Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for Bug 691444. Issue was introduced when interpolation max output range was set to be 65535 so that the output could be fed directly into CMM. Problem was for HT output devices like pbmraw the interpolation filter ignored the max range setting and used a max value of the frac range as output. This fixes a number of files that had regressions. Files checked with bmpcmp.</pre> +Fix for Bug 691444. Issue was introduced when interpolation max output range +was set to be 65535 so that the output could be fed directly into CMM. +Problem was for HT output devices like pbmraw the interpolation filter +ignored the max range setting and used a max value of the frac range as +output. This fixes a number of files that had regressions. Files checked +with bmpcmp.</pre> <p>[base/sidscale.c]</p> </blockquote> @@ -45905,7 +46503,9 @@ Fix for Bug 691444. Issue was introduced when interpolation max output range wa 2010-07-13T01:20:10.578834Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for bug 691445. pdf14 mapping procs were not paying attention to the trans device in the imager state. bmpcmp showed that this fixed several files.</pre> +Fix for bug 691445. pdf14 mapping procs were not paying attention to the +trans device in the imager state. bmpcmp showed that this fixed several +files.</pre> <p>[base/gdevp14.c]</p> </blockquote> @@ -45913,7 +46513,8 @@ Fix for bug 691445. pdf14 mapping procs were not paying attention to the trans 2010-07-12T15:03:57.186505Z Chris Liddell</strong></p> <blockquote> <pre> -In the event the FAPI code has to replace the FontBBox array, make sure the new array is marked executable. +In the event the FAPI code has to replace the FontBBox array, make sure the new +array is marked executable. No cluster differences expected.</pre> <p>[psi/zfapi.c]</p> @@ -45923,7 +46524,14 @@ No cluster differences expected.</pre> 2010-07-11T15:26:14.804339Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for overprint regressions introduced with icc branch merge. Review of bmp compares reveals that this fixes a number of issues hence the large number of differences with the commit. There is one regression introduced with this commit, which is IA3Z0302.pdf.pdf.pkmraw.300 page 2 a bug will be opened for this. Also, review of Atona_Technical_1v1_x3.pdf.pam.72 reveals there some overprint issues may still exist with bitmap and halftone image overprinting on top of spotcolors when Overprint is true and and Overprint mode is set to On. This issue may have existed prior to the icc commit. Will open a bug to investigate.</pre> +Fix for overprint regressions introduced with icc branch merge. Review of bmp +compares reveals that this fixes a number of issues hence the large number of +differences with the commit. There is one regression introduced with this commit, +which is IA3Z0302.pdf.pdf.pkmraw.300 page 2 a bug will be opened for this. Also, +review of Atona_Technical_1v1_x3.pdf.pam.72 reveals there some overprint issues may +still exist with bitmap and halftone image overprinting on top of spotcolors when +Overprint is true and and Overprint mode is set to On. This issue may have existed +prior to the icc commit. Will open a bug to investigate.</pre> <p>[base/gsicc_create.c base/gxcspace.h base/gscspace.c base/gsicc.c]</p> </blockquote> @@ -46163,7 +46771,10 @@ latter appears to be ignored by Acrobat, and so may be wrong. Bug 691426. 2010-07-05T01:23:43.139942Z Hin-Tak Leung</strong></p> <blockquote> <pre> -test for emptiness of HAVE_FONTCONFIG is better than non-yes-ness of enable_fontconfig; fine-tuning of r11448 to --disable-cairo when fontconfig is not available or user-disabled</pre> +test for emptiness of HAVE_FONTCONFIG is better than non-yes-ness of +enable_fontconfig; +fine-tuning of r11448 to --disable-cairo when fontconfig is not available or +user-disabled</pre> <p>[base/configure.ac]</p> </blockquote> @@ -46171,7 +46782,8 @@ test for emptiness of HAVE_FONTCONFIG is better than non-yes-ness of enable_font 2010-07-05T01:18:30.861454Z Hin-Tak Leung</strong></p> <blockquote> <pre> -new/renamed documentation file libpng-1.2.44.txt missed in r11482 for libpng 1.2.42->1.2.44 upgrade</pre> +new/renamed documentation file libpng-1.2.44.txt missed in r11482 for +libpng 1.2.42->1.2.44 upgrade</pre> <p>[libpng/libpng-1.2.44.txt]</p> </blockquote> @@ -46180,7 +46792,9 @@ new/renamed documentation file libpng-1.2.44.txt missed in r11482 for libpng 1.2 <blockquote> <pre> Reaplly Hin-Tak's patch, rev. 11453, which was rolled back by the rev. 11462. -Apply diff between stock 1.2.42 <-> 1.2.44 to upgrade to libpng 1.2.44 - bug + +Apply diff between stock 1.2.42 <-> 1.2.44 to upgrade to libpng 1.2.44 +- bug fixes - CVE-2010-1205. Bug 691438. </pre> <p>[libpng/pngrtran.c libpng/scripts/makefile.gcmmx libpng/contrib/pngminim/encoder/gather.sh libpng/scripts/makefile.sgi libpng/scripts/makefile.sco libpng/scripts/makefile.hpgcc libpng/KNOWNBUG libpng/projects/xcode/libpng.xcodeproj/project.pbxproj libpng/scripts/pngos2.def libpng/scripts/makefile.nommx libpng/scripts/makefile.linux libpng/pngmem.c libpng/png.c libpng/contrib/pngminim/decoder/gather.sh libpng/scripts/makefile.64sunu libpng/scripts/makefile.elf libpng/scripts/libpng-config-head.in libpng/png.h libpng/CMakeLists.txt libpng/pngrio.c libpng/pngpread.c libpng/Y2KINFO libpng/scripts/makefile.netbsd libpng/pngwio.c libpng/pngrutil.c libpng/scripts/makefile.hpux libpng/scripts/makefile.darwin libpng/scripts/makefile.sggcc libpng/README libpng/contrib/pngminim/decoder/makefile libpng/scripts/makefile.32sunu libpng/libpngpf.3 libpng/scripts/makefile.solaris-x86 libpng/libpng-1.2.42.txt libpng/contrib/pngminim/preader/makefile libpng/scripts/makefile.solaris libpng/pngwtran.c libpng/contrib/pngminim/preader/gather.sh libpng/scripts/makefile.mingw libpng/scripts/makefile.aix libpng/scripts/makefile.hp64 libpng/scripts/png32ce.def libpng/scripts/makefile.beos libpng/scripts/makefile.ne12bsd libpng/pngread.c libpng/scripts/pngw32.def libpng/pngget.c libpng/INSTALL libpng/scripts/makefile.cegcc libpng/CHANGES libpng/contrib/pngminim/encoder/makefile libpng/projects/wince.txt libpng/libpng.3 libpng/example.c libpng/scripts/makefile.so9 libpng/pngwrite.c libpng/pngconf.h libpng/pngset.c libpng/LICENSE libpng/png.5 libpng/pngwutil.c libpng/scripts/makefile.openbsd libpng/scripts/makefile.dec libpng/scripts/README.txt libpng/scripts/makefile.cygwin libpng/pngtest.c libpng/ANNOUNCE libpng/scripts/libpng.pc.in]</p> @@ -46190,7 +46804,8 @@ fixes - CVE-2010-1205. Bug 691438. 2010-07-03T00:29:40.754683Z Hin-Tak Leung</strong></p> <blockquote> <pre> -missed linker defines needed to build under 64-bit windows in a previous commit r11388 for bug 691302</pre> +missed linker defines needed to build under 64-bit windows in a +previous commit r11388 for bug 691302</pre> <p>[psi/msvc32.mak]</p> </blockquote> @@ -46236,7 +46851,12 @@ No differences expected. 2010-07-01T17:14:23.564053Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for Bug 691431. This was caused by a PS CIE color space being used for a transparency group color space. That really should not be allowed since those color spaces are unidirectional. They are installed though when -dUseCIEColor is used with a PDF file that has transparency. Solution is to use the default ICC profiles for the group color space when this occurs.</pre> +Fix for Bug 691431. This was caused by a PS CIE color space being +used for a transparency group color space. That really should not +be allowed since those color spaces are unidirectional. They are +installed though when -dUseCIEColor is used with a PDF file that has +transparency. Solution is to use the default ICC profiles for the group +color space when this occurs.</pre> <p>[base/gstrans.c]</p> </blockquote> @@ -46295,7 +46915,8 @@ reapply r11455 - see original commit log for details</pre> 2010-06-30T23:34:11.835858Z Hin-Tak Leung</strong></p> <blockquote> <pre> -security patch from Werner Fink, to disable loading init files from group/world-writable directories - bug 691350</pre> +security patch from Werner Fink, to disable loading init files from +group/world-writable directories - bug 691350</pre> <p>[psi/zfile.c]</p> </blockquote> @@ -46303,9 +46924,8 @@ security patch from Werner Fink, to disable loading init files from group/world- 2010-06-30T22:12:02.295636Z Michael Vrhel</strong></p> <blockquote> <pre> -Initialize profile member variables that are part of serialization. Fix for Bug 691433 - - +Initialize profile member variables that are part of serialization. +Fix for Bug 691433 </pre> <p>[base/gsicc_manage.c]</p> </blockquote> @@ -46332,7 +46952,9 @@ revert back to 11450. 2010-06-29T07:08:29.009258Z Hin-Tak Leung</strong></p> <blockquote> <pre> -more cygwin/mingw-related patches from Jan Nieuwenhuizen (lilypond/gub) ; this one depends on features of GNU make, so it is added as comments to avoid breaking build with non-GNU make</pre> +more cygwin/mingw-related patches from Jan Nieuwenhuizen (lilypond/gub) ; this +one depends on features of GNU make, so it is added as comments to avoid +breaking build with non-GNU make</pre> <p>[base/unix-dll.mak]</p> </blockquote> @@ -46340,7 +46962,8 @@ more cygwin/mingw-related patches from Jan Nieuwenhuizen (lilypond/gub) ; this o 2010-06-29T07:05:45.877229Z Hin-Tak Leung</strong></p> <blockquote> <pre> -avoid re-define _Windows if it is already defined; one of the cygwin/mingw-related patches from Jan Nieuwenhuizen (lilypond/gub)</pre> +avoid re-define _Windows if it is already defined; one of the cygwin/mingw-related +patches from Jan Nieuwenhuizen (lilypond/gub)</pre> <p>[base/gs_dll_call.h]</p> </blockquote> @@ -46348,7 +46971,9 @@ avoid re-define _Windows if it is already defined; one of the cygwin/mingw-relat 2010-06-29T07:04:25.796552Z Hin-Tak Leung</strong></p> <blockquote> <pre> -cygwin is one platform which uses the unix file name interface but is sensitive to binary/text mode; one of the cygwin/mingw-related patches from Jan Nieuwenhuizen (lilypond/gub)</pre> +cygwin is one platform which uses the unix file name interface but is +sensitive to binary/text mode; one of the cygwin/mingw-related patches from +Jan Nieuwenhuizen (lilypond/gub)</pre> <p>[base/gp_unifn.c]</p> </blockquote> @@ -46373,7 +46998,8 @@ down the wrong code path. These are quite rare so it took 7 years for the bug 2010-06-29T06:05:26.121392Z Hin-Tak Leung</strong></p> <blockquote> <pre> -updating jpeg config.sub config.guess to that from libpng 1.2.44; bug 690486</pre> +updating jpeg config.sub config.guess to that from +libpng 1.2.44; bug 690486</pre> <p>[jpeg/config.guess jpeg/config.sub]</p> </blockquote> @@ -46381,7 +47007,8 @@ updating jpeg config.sub config.guess to that from libpng 1.2.44; bug 690486</pr 2010-06-29T05:30:19.407679Z Hin-Tak Leung</strong></p> <blockquote> <pre> -apply diff between stock 1.2.42 <-> 1.2.44 to upgrade to libpng 1.2.44 - bug fixes - CVE-2010-1205</pre> +apply diff between stock 1.2.42 <-> 1.2.44 to upgrade to +libpng 1.2.44 - bug fixes - CVE-2010-1205</pre> <p>[libpng/pngrtran.c libpng/scripts/makefile.gcmmx libpng/contrib/pngminim/encoder/gather.sh libpng/scripts/makefile.sgi libpng/scripts/makefile.sco libpng/scripts/makefile.hpgcc libpng/KNOWNBUG libpng/projects/xcode/libpng.xcodeproj/project.pbxproj libpng/scripts/pngos2.def libpng/scripts/makefile.nommx libpng/scripts/makefile.linux libpng/pngmem.c libpng/png.c libpng/contrib/pngminim/decoder/gather.sh libpng/scripts/makefile.64sunu libpng/scripts/makefile.elf libpng/scripts/libpng-config-head.in libpng/png.h libpng/CMakeLists.txt libpng/pngrio.c libpng/pngpread.c libpng/Y2KINFO libpng/scripts/makefile.netbsd libpng/pngwio.c libpng/pngrutil.c libpng/scripts/makefile.hpux libpng/scripts/makefile.darwin libpng/scripts/makefile.sggcc libpng/README libpng/contrib/pngminim/decoder/makefile libpng/scripts/makefile.32sunu libpng/libpngpf.3 libpng/scripts/makefile.solaris-x86 libpng/libpng-1.2.42.txt libpng/libpng-1.2.44.txt libpng/contrib/pngminim/preader/makefile libpng/scripts/makefile.solaris libpng/pngwtran.c libpng/contrib/pngminim/preader/gather.sh libpng/scripts/makefile.mingw libpng/scripts/makefile.aix libpng/scripts/makefile.hp64 libpng/scripts/png32ce.def libpng/scripts/makefile.beos libpng/scripts/makefile.ne12bsd libpng/pngread.c libpng/scripts/pngw32.def libpng/pngget.c libpng/INSTALL libpng/scripts/makefile.cegcc libpng/CHANGES libpng/contrib/pngminim/encoder/makefile libpng/libpng.3 libpng/projects/wince.txt libpng/example.c libpng/scripts/makefile.so9 libpng/pngwrite.c libpng/pngconf.h libpng/pngset.c libpng/LICENSE libpng/png.5 libpng/pngwutil.c libpng/scripts/makefile.openbsd libpng/scripts/makefile.dec libpng/scripts/README.txt libpng/scripts/makefile.cygwin libpng/pngtest.c libpng/ANNOUNCE libpng/scripts/libpng.pc.in]</p> </blockquote> @@ -46389,7 +47016,8 @@ apply diff between stock 1.2.42 <-> 1.2.44 to upgrade to libpng 1.2.44 - b 2010-06-29T05:25:07.282125Z Hin-Tak Leung</strong></p> <blockquote> <pre> -change documentation as --enable-dynamics is no longer required for "make so" to work</pre> +change documentation as --enable-dynamics is no longer required +for "make so" to work</pre> <p>[doc/Make.htm]</p> </blockquote> @@ -46397,7 +47025,8 @@ change documentation as --enable-dynamics is no longer required for "make s 2010-06-29T05:20:09.043972Z Hin-Tak Leung</strong></p> <blockquote> <pre> -split lcms code build into arch-specific targets; try to make both windows inline assembly and unix "make so" work simultaneously; bug 691427</pre> +split lcms code build into arch-specific targets; try to make both windows +inline assembly and unix "make so" work simultaneously; bug 691427</pre> <p>[base/watclib.mak base/lib.mak base/bcwin32.mak base/openvms.mak base/ugcclib.mak base/macosx.mak base/watcw32.mak base/Makefile.in base/unix-gcc.mak base/unixansi.mak psi/msvc32.mak base/macos-mcp.mak base/msvclib.mak]</p> </blockquote> @@ -46405,7 +47034,9 @@ split lcms code build into arch-specific targets; try to make both windows inlin 2010-06-29T05:16:38.524502Z Hin-Tak Leung</strong></p> <blockquote> <pre> -move the DYNAMIC_* defines out of the --enable-dynamic condition so that it applies generally; try to "make so" work with just ./configure ; many bugs ask for make so to work</pre> +move the DYNAMIC_* defines out of the --enable-dynamic condition so that it +applies generally; try to "make so" work with just +./configure ; many bugs ask for make so to work</pre> <p>[base/configure.ac]</p> </blockquote> @@ -46413,7 +47044,9 @@ move the DYNAMIC_* defines out of the --enable-dynamic condition so that it appl 2010-06-29T04:34:10.440639Z Hin-Tak Leung</strong></p> <blockquote> <pre> -switch autoconf png test away from testing for a soon-to-be-obsolete routine to one we actually use, to smooth over the libpng 1.2.x to 1.4.x transition; bug 691111</pre> +switch autoconf png test away from testing for a soon-to-be-obsolete routine +to one we actually use, to smooth over the libpng 1.2.x to 1.4.x +transition; bug 691111</pre> <p>[jbig2dec/configure.ac base/configure.ac]</p> </blockquote> @@ -46513,7 +47146,11 @@ Warnings of problems within lcms only occur now in debug mode. Fix for Bug 6914 2010-06-28T05:16:59.820980Z Michael Vrhel</strong></p> <blockquote> <pre> -Interface with lcms so that the memory allocators make use of ghostscript's allocator. This required fixing a few bugs in littlecms where he was using free instead of _cmsFree and also having lcms.h provide the prototypes if the external mem alloc is defined. Performed cluster push with no problem. Thanks to Henry for helping me track down a 64 bit issue.</pre> +Interface with lcms so that the memory allocators make use of ghostscript's +allocator. This required fixing a few bugs in littlecms where he was using +free instead of _cmsFree and also having lcms.h provide the prototypes if the +external mem alloc is defined. Performed cluster push with no problem. Thanks +to Henry for helping me track down a 64 bit issue.</pre> <p>[lcms/include/lcms.h base/lib.mak lcms/src/cmslut.c base/lcms.mak lcms/src/cmsio1.c base/gsicc_littlecms.c]</p> </blockquote> @@ -46545,9 +47182,13 @@ not compile without this change. 2010-06-25T12:00:50.643763Z Chris Liddell</strong></p> <blockquote> <pre> -Provide more robust behaviour when FT fails to render a glyph. Inistead of silently continuing when FT errors on a glyph, we'll now attempt to use the notdef, if the notdef triggers an error, we signal the error to the GS world. This ensures that any time we expect processing to continue there is valid glyph information available to the cache and other downstream devices. - -This causes one regression difference with 34_all.PS, where an extra TTF notdef is rendered. +Provide more robust behaviour when FT fails to render a glyph. Inistead +of silently continuing when FT errors on a glyph, we'll now attempt to use +the notdef, if the notdef triggers an error, we signal the error to the GS +world. This ensures that any time we expect processing to continue there is +valid glyph information available to the cache and other downstream devices. +This causes one regression difference with 34_all.PS, where an extra TTF +notdef is rendered. Bug 691416</pre> <p>[psi/fapi_ft.c]</p> @@ -46591,7 +47232,8 @@ This may be too limited and may require further work in future. 2010-06-23T14:33:08.852324Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for bug691415. When equivalent ICC profile is already created we should just use it. Thanks to Ken for getting the details together.</pre> +Fix for bug691415. When equivalent ICC profile is already created we +should just use it. Thanks to Ken for getting the details together.</pre> <p>[base/gscsepr.c]</p> </blockquote> @@ -46601,9 +47243,19 @@ Fix for bug691415. When equivalent ICC profile is already created we should jus <pre> Fix for 691359. Problem tracked down by Alex. -What lcms is trying to do is to figure out the best prelinearization for the incoming data prior to doing the CLUT interpolation. In the case when the input is RGB based and the output Gray, lcms was using uninitialized data in constructing is prelinearization. - -Tangentially related, there could still be problems with what lcms is doing here if the number of Input channels is 1 and the number of Output channels is 3. In that case, it is possible (but not likely) that I could have radically different gamma behavior in each of the RGB channels. Trans in such a case would be constructed based upon only one curve based on the red channel. In the real world, this is probably not a problem but ideally it would be optimal to use something that provides the best prelinearization in all three channels. That is an optimization for Marti to do and perhaps is already in lcms2.</pre> +What lcms is trying to do is to figure out the best prelinearization +for the incoming data prior to doing the CLUT interpolation. In the +case when the input is RGB based and the output Gray, lcms was using +uninitialized data in constructing is prelinearization. +Tangentially related, there could still be problems with what lcms is +doing here if the number of Input channels is 1 and the number of Output +channels is 3. In that case, it is possible (but not likely) that I could +have radically different gamma behavior in each of the RGB channels. Trans +in such a case would be constructed based upon only one curve based on the +red channel. In the real world, this is probably not a problem but ideally +it would be optimal to use something that provides the best prelinearization +in all three channels. That is an optimization for Marti to do and perhaps +is already in lcms2.</pre> <p>[lcms/src/cmsgmt.c]</p> </blockquote> @@ -46698,7 +47350,8 @@ PostScript can make use of it for high-level pattern support. 2010-06-21T01:14:18.832712Z Hin-Tak Leung</strong></p> <blockquote> <pre> -auto-detect host as *BSD and use a differently named obj directory; no effect on non-*BSDs. fixes bug 687214</pre> +auto-detect host as *BSD and use a differently named obj directory; +no effect on non-*BSDs. fixes bug 687214</pre> <p>[base/Makefile.in base/configure.ac]</p> </blockquote> @@ -46730,7 +47383,9 @@ nsis-based installer script, makefile adaptation, documentation update; bug 6913 2010-06-20T23:38:47.757390Z Hin-Tak Leung</strong></p> <blockquote> <pre> -borland build fix (bug 691400): borland defines P_tmpdir but not _P_tmpdir; similiar difference between borlandc and msvc has been seen with setmode/_setmode in the ijs code in ijs/ijs_server.c</pre> +borland build fix (bug 691400): borland defines P_tmpdir but not +_P_tmpdir; similiar difference between borlandc and msvc has been +seen with setmode/_setmode in the ijs code in ijs/ijs_server.c</pre> <p>[jasper/src/libjasper/base/jas_stream.c]</p> </blockquote> @@ -46738,7 +47393,8 @@ borland build fix (bug 691400): borland defines P_tmpdir but not _P_tmpdir; simi 2010-06-20T23:32:24.162240Z Hin-Tak Leung</strong></p> <blockquote> <pre> -borland build fix (bug 691400): update and complete documentation on working around for too-many-warnings-equal-error problem of borland c++</pre> +borland build fix (bug 691400): update and complete documentation on +working around for too-many-warnings-equal-error problem of borland c++</pre> <p>[doc/Make.htm]</p> </blockquote> @@ -46746,7 +47402,8 @@ borland build fix (bug 691400): update and complete documentation on working aro 2010-06-20T23:29:34.775566Z Hin-Tak Leung</strong></p> <blockquote> <pre> -borland fix (bug 691400): Borland c++ does not support c99 LL nor ULL, but use i64/ui64 like MSVC for 64-bit integer literals</pre> +borland fix (bug 691400): Borland c++ does not support c99 LL nor +ULL, but use i64/ui64 like MSVC for 64-bit integer literals</pre> <p>[base/sha2.c]</p> </blockquote> @@ -46778,7 +47435,10 @@ borland build does not create the obj and bin directories. part of borland build 2010-06-20T22:57:32.647408Z Hin-Tak Leung</strong></p> <blockquote> <pre> -defines a unix target, since win32 requires specific compiler flags; HP-UX make/MS nmake both issues a warning and borland make issues an error for duplicate targets; fixes bug 691337, and also part of the problems with borland build (bug 691400)</pre> +defines a unix target, since win32 requires specific compiler flags; +HP-UX make/MS nmake both issues a warning and borland make issues an +error for duplicate targets; fixes bug 691337, and also part of the +problems with borland build (bug 691400)</pre> <p>[base/libtiff.mak]</p> </blockquote> @@ -46806,7 +47466,8 @@ warnings and spurious hash value differences. 2010-06-18T23:59:23.662717Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that when the CIE color spaces are released, the icc equivalent space is also rc decremented as is the profile.</pre> +Fix so that when the CIE color spaces are released, the icc equivalent +space is also rc decremented as is the profile.</pre> <p>[base/gscscie.c]</p> </blockquote> @@ -46833,7 +47494,8 @@ work around the bug 691005 in a few cases. 2010-06-17T20:23:33.279930Z Hin-Tak Leung</strong></p> <blockquote> <pre> -adjust self-reference of bswin32.mak to correct location. Part 1 of fix to bug 691400</pre> +adjust self-reference of bswin32.mak to correct location. +Part 1 of fix to bug 691400</pre> <p>[base/bcwin32.mak]</p> </blockquote> @@ -46841,7 +47503,8 @@ adjust self-reference of bswin32.mak to correct location. Part 1 of fix to bug 6 2010-06-17T20:03:30.325885Z Hin-Tak Leung</strong></p> <blockquote> <pre> -mentioning -P-/-P and further reference to the INITIALIZATION FILES and Use.htm in the man page. bug 691350</pre> +mentioning -P-/-P and further reference to the INITIALIZATION FILES and +Use.htm in the man page. bug 691350</pre> <p>[man/gs.1]</p> </blockquote> @@ -46857,7 +47520,8 @@ add missing type def for gsicc_create_mashed_clut</pre> 2010-06-17T19:38:39.362075Z Hin-Tak Leung</strong></p> <blockquote> <pre> -split make_filelist functionality out of setupgs, to allow UAC restriction during packaging of the installer. Bug 691302</pre> +split make_filelist functionality out of setupgs, to allow UAC restriction +during packaging of the installer. Bug 691302</pre> <p>[psi/dwsetup.cpp psi/winint.mak psi/msvc32.mak psi/mkfilelt.cpp]</p> </blockquote> @@ -46873,7 +47537,8 @@ add info about silent batch installation; bug 691268</pre> 2010-06-17T19:28:20.229863Z Michael Vrhel</strong></p> <blockquote> <pre> -rc_decrement any icc objects that may exist in the imager state that was created for handling the conversion from PS CIE objects to ICC profiles.</pre> +rc_decrement any icc objects that may exist in the imager state that was +created for handling the conversion from PS CIE objects to ICC profiles.</pre> <p>[base/gscie.c]</p> </blockquote> @@ -46889,7 +47554,11 @@ Free up tag list when done creating icc profile from PDF cal type.</pre> 2010-06-17T17:13:34.616951Z Michael Vrhel</strong></p> <blockquote> <pre> -Change to help track down any memory leaks related to the new icc code. Also fix so that gs_init_iccmanager copies the null character from the default profile string names. There was a mismatch between what happened here and what happens when the default user params are set. This was causing the profiles to reset in the manager when they did not need to be.</pre> +Change to help track down any memory leaks related to the new icc code. +Also fix so that gs_init_iccmanager copies the null character from the default +profile string names. There was a mismatch between what happened here and what +happens when the default user params are set. This was causing the profiles to +reset in the manager when they did not need to be.</pre> <p>[base/gsicc_manage.c]</p> </blockquote> @@ -46919,7 +47588,9 @@ a few more CRLF eol and svn property corrections</pre> 2010-06-15T17:17:15.944441Z Michael Vrhel</strong></p> <blockquote> <pre> -Rename of a few functions to match documentation, update of gdevwts.c to use new color architecture, addition of minor utility functions for use in gxps. This should not generate regressions.</pre> +Rename of a few functions to match documentation, update of gdevwts.c to +use new color architecture, addition of minor utility functions for use in gxps. +This should not generate regressions.</pre> <p>[base/lib.mak base/gsicc_littlecms.h base/gsicc_cache.h base/gsicc_manage.c base/gscms.h base/gdevwts.c base/gsicc_manage.h base/gsicc_littlecms.c]</p> </blockquote> @@ -46955,7 +47626,8 @@ spec and irks Valgrind. Bug 691394. 2010-06-14T18:07:49.834071Z Chris Liddell</strong></p> <blockquote> <pre> -Remove the "<font> is being rendered with FAPI=<renderer>" messages. But leave a warning if we fall back to the old GS renderer.</pre> +Remove the "<font> is being rendered with FAPI=<renderer>" +messages. But leave a warning if we fall back to the old GS renderer.</pre> <p>[Resource/Init/gs_fapi.ps]</p> </blockquote> @@ -47044,12 +47716,12 @@ memory. 2010-06-11T17:24:06.899434Z Chris Liddell</strong></p> <blockquote> <pre> -In the event of a FreeType error when scaling a font face, don't clean up the FT data, but leave it to the garbage collector -to call the font object's "finalize" function, which will then clean up the FT data. - -Secondly, add code to deal with very low resolutions underflowing some of FT's fixed point code (similar to code for small -scale factors). - +In the event of a FreeType error when scaling a font face, don't clean +up the FT data, but leave it to the garbage collector +to call the font object's "finalize" function, which will then +clean up the FT data. +Secondly, add code to deal with very low resolutions underflowing some of FT's +fixed point code (similar to code for small scale factors). Bug 691381 </pre> <p>[psi/fapi_ft.c]</p> @@ -47081,13 +47753,13 @@ produce complete PDF files. 2010-06-10T16:11:08.241878Z Chris Liddell</strong></p> <blockquote> <pre> -When extracting a path from the FAPI world (for a charpath, for example), only close the path if it has been "opened". - -This prevents empty paths from non-marking glyphs resulting in a point being rendered on the page. - +When extracting a path from the FAPI world (for a charpath, for example), +only close the path if it has been "opened". +This prevents empty paths from non-marking glyphs resulting in a point being +rendered on the page. Another part of Bug 691252. - -This change causes ~195 differences to be reported on the cluster, but they are all progressions. +This change causes ~195 differences to be reported on the cluster, but they +are all progressions. </pre> <p>[psi/zfapi.c]</p> @@ -47097,10 +47769,10 @@ This change causes ~195 differences to be reported on the cluster, but they are 2010-06-10T14:06:40.549557Z Chris Liddell</strong></p> <blockquote> <pre> -Make the rendering of the Truetype notdef glyph optional with the FAPI interface (as per the previous behaviour). - -A few cluster differences are expected as we have test files which use the TTF notdef, I have checked all the differences, and they are correct. - +Make the rendering of the Truetype notdef glyph optional with the FAPI interface +(as per the previous behaviour). +A few cluster differences are expected as we have test files which use the TTF notdef, +I have checked all the differences, and they are correct. This is part of Bug 691252 </pre> @@ -47127,7 +47799,10 @@ Error values are now always in brackets, on a red background. 2010-06-08T16:20:39.058317Z Chris Liddell</strong></p> <blockquote> <pre> -In bytes_copy_rectangle() clamp the length of each row to be copied to the stride of the raster. This takes care of problems copying bitmaps from FT (or potentially other font libraries) which use different alignment to the "internal" rasters. Bug 691328.</pre> +In bytes_copy_rectangle() clamp the length of each row to be copied to the +stride of the raster. This takes care of problems copying bitmaps from FT +(or potentially other font libraries) which use different alignment to +the "internal" rasters. Bug 691328.</pre> <p>[base/gsbitops.c]</p> </blockquote> @@ -47149,7 +47824,12 @@ font has /Encoding. Bug 691311. <pre> Fix for Bug 691368. -lcms appears not to check its handles of link transforms when a profile is released, to clear out xform->InputProfile. Probably due to the fact that lcms may not expect a change of the formatters after the link is created. That would imply that we would need to create links based upon data types, which is not so efficient. Disable this check in lcms since it is only related to named color profiles, which we will not run into. Will kick this up to Marti.</pre> +lcms appears not to check its handles of link transforms when a profile is +released, to clear out xform->InputProfile. Probably due to the fact that +lcms may not expect a change of the formatters after the link is created. +That would imply that we would need to create links based upon data types, +which is not so efficient. Disable this check in lcms since it is only related +to named color profiles, which we will not run into. Will kick this up to Marti.</pre> <p>[lcms/src/cmspack.c]</p> </blockquote> @@ -47157,7 +47837,9 @@ lcms appears not to check its handles of link transforms when a profile is relea 2010-06-06T18:00:36.332831Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for Bug 691367. Seg fault should no longer occur. If an attempt is made to set a color space in the graphic state and the ICC manager's profiles have not yet been initialized, it will be taken care of. </pre> +Fix for Bug 691367. Seg fault should no longer occur. If an attempt is +made to set a color space in the graphic state and the ICC manager's +profiles have not yet been initialized, it will be taken care of. </pre> <p>[base/gsicc_manage.c base/gscspace.c]</p> </blockquote> @@ -47174,7 +47856,11 @@ Don't copy memory block into itself; clear a Valgrind warning. 2010-06-05T19:20:40.615579Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for indeterminisms in some PS files where the alternate tint transform color space for a DeviceN or Separation color space is CIE based. Previously we were returning either CMYK, or RGB based based upon the channel count for the CIE space. Now we are returning an equivalent ICC based color space. Also minor fix for uninitialized memory in generated profile.</pre> +Fix for indeterminisms in some PS files where the alternate tint transform +color space for a DeviceN or Separation color space is CIE based. Previously +we were returning either CMYK, or RGB based based upon the channel count for +the CIE space. Now we are returning an equivalent ICC based color space. Also +minor fix for uninitialized memory in generated profile.</pre> <p>[base/gscdevn.c base/gsicc_create.c base/gscsepr.c]</p> </blockquote> @@ -47270,7 +47956,10 @@ we are rendering a pattern inside a form, nested inside at least one other form. 2010-06-01T17:41:20.224359Z Michael Vrhel</strong></p> <blockquote> <pre> -Rename of gsicccache.c/h to gsicc_cache.c/h and gsiccmanage.c/h to gsicc_manage.c/h to fall in line with the name space of the other files that came from the icc branch. Currently working on the documentation and it is clear that this is needed (and I wish I had done it earlier).</pre> +Rename of gsicccache.c/h to gsicc_cache.c/h and gsiccmanage.c/h to +gsicc_manage.c/h to fall in line with the name space of the other files +that came from the icc branch. Currently working on the documentation +and it is clear that this is needed (and I wish I had done it earlier).</pre> <p>[/trunk/ghostpdl/pxl/pxpthr.c /trunk/ghostpdl/pxl/pxl.mak /trunk/ghostpdl/xps/ghostxps.h base/gsiccmanage.c base/gxshade1.c base/gsiccmanage.h base/gscsepr.c base/gxshade4.c base/gxshade6.c /trunk/ghostpdl/pxl/pxtop.c base/gxcmap.c ghostscript.vcproj base/gsistate.c /trunk/ghostpdl/pcl/pcl.mak base/gdevrinkj.c base/gdevwts.c base/gdevxcf.c base/gxicolor.c base/devs.mak base/gsicc.c base/gdevimdi.c base/gscdevn.c base/gxclread.c base/gdevpsd.c base/lib.mak base/gxiscale.c base/gsicc_manage.c psi/int.mak /trunk/ghostpdl/pxl/pxgstate.c /trunk/ghostpdl/pcl/pctop.c base/gsicc_manage.h psi/zicc.c psi/zdevice.c base/gdevp14.c base/gsstate.c base/gsicc_cache.c base/gsicc_create.c psi/zcie.c base/gsicccache.c base/gxclist.c base/gsicc_cache.h base/gsicccache.h base/gstrans.c base/gscms.h base/gxidata.c base/gdevpdfc.c base/gxblend.c base/gxshade.c psi/zusparam.c base/gdevpdfg.c base/gxp1fill.c base/gxclrast.c base/gsciemap.c]</p> </blockquote> @@ -47278,7 +47967,9 @@ Rename of gsicccache.c/h to gsicc_cache.c/h and gsiccmanage.c/h to gsicc_manage 2010-05-31T14:49:14.514014Z Hin-Tak Leung</strong></p> <blockquote> <pre> -for "ln -s base/unix-gcc.mak Makefile; make" builds, do not modularize X, nor build most of the modularzed linux modules, since they depend on the linux GNU linker</pre> +for "ln -s base/unix-gcc.mak Makefile; make" builds, do +not modularize X, nor build most of the modularzed linux modules, +since they depend on the linux GNU linker</pre> <p>[base/unix-gcc.mak]</p> </blockquote> @@ -47286,7 +47977,8 @@ for "ln -s base/unix-gcc.mak Makefile; make" builds, do not modularize 2010-05-31T14:41:08.956692Z Hin-Tak Leung</strong></p> <blockquote> <pre> -another attempt to make "ln -s base/unix-gcc.mak Makefile; make" to work; libtiff really want configure so we hook it in</pre> +another attempt to make "ln -s base/unix-gcc.mak Makefile; make" +to work; libtiff really want configure so we hook it in</pre> <p>[base/libtiff.mak]</p> </blockquote> @@ -47294,7 +47986,8 @@ another attempt to make "ln -s base/unix-gcc.mak Makefile; make" to wo 2010-05-31T09:58:14.532526Z Hin-Tak Leung</strong></p> <blockquote> <pre> -more icc branch merge related change to make "make -f base/unix-gcc.mak" and other targets work"</pre> +more icc branch merge related change to make +"make -f base/unix-gcc.mak" and other targets work"</pre> <p>[base/unix-gcc.mak base/unixansi.mak]</p> </blockquote> @@ -47314,7 +48007,11 @@ from the same source table. 2010-05-27T21:02:21.460781Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix so that shading strokes that go through the clist transparency code communicate the transparency device so that the proper color information is used as opposed to the color information related to the final target device. This should fix the indeterminism with bug688807.pdf when going out to a monochrome device.</pre> +Fix so that shading strokes that go through the clist transparency code +communicate the transparency device so that the proper color information +is used as opposed to the color information related to the final target +device. This should fix the indeterminism with bug688807.pdf when going +out to a monochrome device.</pre> <p>[base/gdevp14.c base/gxshade.c]</p> </blockquote> @@ -47332,7 +48029,10 @@ the header file instead of the c file. 2010-05-27T00:44:57.701730Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for indeterminism when using psdcmyk device and interpolated images. For cases where the device profile has fewer components than the actual number of device colorants we need to use the slower interpolation code. Otherwise we end up encoding uninitialized memory. </pre> +Fix for indeterminism when using psdcmyk device and interpolated images. +For cases where the device profile has fewer components than the actual +number of device colorants we need to use the slower interpolation code. +Otherwise we end up encoding uninitialized memory. </pre> <p>[base/gxiscale.c]</p> </blockquote> @@ -47340,7 +48040,13 @@ Fix for indeterminism when using psdcmyk device and interpolated images. For ca 2010-05-26T22:01:50.106123Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for bug690218. For clist reader the pdf14 device was getting its color information set based upon the number of spot colorants in the page. The real number should be based upon the number of actual components the device is capable of handling. This occurs when using separation device with a limited set of colorants invoked via a command like -c "<< /SeparationColorNames [ /Cyan /Magenta /Yellow /Black ] +Fix for bug690218. For clist reader the pdf14 device was getting its color +information set based upon the number of spot colorants in the page. The real +number should be based upon the number of actual components the device is capable +of handling. This occurs when using separation device with a limited set of +colorants invoked via a command like +-c "<< /SeparationColorNames [ /Cyan /Magenta /Yellow /Black ] + /SeparationOrder [ /Cyan /Magenta /Yellow /Black ] >> setpagedevice"</pre> <p>[base/gdevp14.c]</p> </blockquote> @@ -47349,7 +48055,8 @@ Fix for bug690218. For clist reader the pdf14 device was getting its color inf 2010-05-26T18:16:52.113331Z Michael Vrhel</strong></p> <blockquote> <pre> -Improvements and fixes in icc search path description and bolder alert with respect to Windows delimiter \" interpretation . Thanks to Ray.</pre> +Improvements and fixes in icc search path description and bolder alert with +respect to Windows delimiter \" interpretation . Thanks to Ray.</pre> <p>[doc/Use.htm]</p> </blockquote> @@ -47369,7 +48076,8 @@ where gs_abort() is replaced with return, fixes bug #691340. 2010-05-26T03:07:02.463936Z Michael Vrhel</strong></p> <blockquote> <pre> -Addition of lcms and new icc files to Visual studio solution. Also did a little organizing of the files in the explorer window base folder.</pre> +Addition of lcms and new icc files to Visual studio solution. Also did a +little organizing of the files in the explorer window base folder.</pre> <p>[ghostscript.vcproj]</p> </blockquote> @@ -47385,7 +48093,11 @@ Update of documentation, clarifying the search methods used for finding the icc 2010-05-25T19:38:23.177347Z Michael Vrhel</strong></p> <blockquote> <pre> -Removal of iccprofiles/ from default icc profile names and post-pend %rom% with iccprofiles/ . This is in preparation for having the ps init code initialize a default value for ICCProfilesDir (which will be ./iccprofiles/ ) so that code works with COMPILE_INITS=0 when not in the base directory and when -sICCProfilesDir is not specified on the command line.</pre> +Removal of iccprofiles/ from default icc profile names and post-pend %rom% +with iccprofiles/ . This is in preparation for having the ps init code +initialize a default value for ICCProfilesDir (which will be ./iccprofiles/ ) +so that code works with COMPILE_INITS=0 when not in the base directory and +when -sICCProfilesDir is not specified on the command line.</pre> <p>[base/gsiccmanage.c base/gsiccmanage.h]</p> </blockquote> @@ -47435,7 +48147,9 @@ related to the ICC branch merge.</pre> 2010-05-25T10:22:09.642632Z Chris Liddell</strong></p> <blockquote> <pre> -Bug 691336: Resolve some confusion between the original global variable removal changes, and subsequent changes, that could result in warning emprintf calls using a memory pointer that could not exist at that stage. +Bug 691336: Resolve some confusion between the original global variable +removal changes, and subsequent changes, that could result in warning emprintf +calls using a memory pointer that could not exist at that stage. </pre> <p>[psi/fapiufst.c]</p> </blockquote> @@ -47455,8 +48169,14 @@ Silence a couple of gcc compiler warnings introduced with the ICC merge. <pre> Another bunch of CRLF to LF's. -find . -type f | grep -v 'svn-base' | xargs file | grep CRLF | grep -v -E '\.(dsp|dsw|sln|rc):' | grep -v -E '(cbuilder5|masm|dotzlib|vstudio|BorlandC_5.5|visualc6)' | cut -d ':' -f 1 | xargs -n 1 svn propset svn:eol-style native -find . -type f | grep -v 'svn-base' | xargs file | grep CRLF | grep -v -E '\.(dsp|dsw|sln|rc):' | grep -v -E '(cbuilder5|masm|dotzlib|vstudio|BorlandC_5.5|visualc6)' | cut -d ':' -f 1 | xargs dos2unix +find . -type f | grep -v 'svn-base' | xargs file | grep CRLF | \ +grep -v -E '\.(dsp|dsw|sln|rc):' | grep -v -E \ +'(cbuilder5|masm|dotzlib|vstudio|BorlandC_5.5|visualc6)' | cut -d ':' -f 1 | \ +xargs -n 1 svn propset svn:eol-style native +find . -type f | grep -v 'svn-base' | xargs file | grep CRLF | \ +grep -v -E '\.(dsp|dsw|sln|rc):' | grep -v -E \ +'(cbuilder5|masm|dotzlib|vstudio|BorlandC_5.5|visualc6)' | cut -d ':' -f 1 | \ +xargs dos2unix </pre> <p>[tiff/nmake.opt psi/zcolor.h toolbin/color/icc_creator/ICC_Creator/stdafx.h lib/cat.ps toolbin/color/icc_creator/ICC_Creator/ICC_CreatorDlg.cpp toolbin/color/icc_creator/example/cielab_values.txt toolbin/color/icc_creator/ICC_Creator/icc34.h contrib/lxm3200-tweaked/LICENSE toolbin/color/icc_creator/README.txt toolbin/color/icc_creator/ICC_Creator/ICC_Creator.cpp toolbin/color/named_color/named_color_table.txt zlib/contrib/testzlib/testzlib.txt lib/Fontmap.URW-136.T1 toolbin/color/icc_creator/example/tritone_names.txt zlib/contrib/testzlib/testzlib.c toolbin/color/icc_creator/ICC_Creator/CIELAB.h toolbin/color/icc_creator/ICC_Creator/icc_create.h base/gsicc_profilecache.c toolbin/color/icc_creator/ICC_Creator/stdafx.cpp toolbin/color/icc_creator/ICC_Creator/resource.h base/gsicc_profilecache.h toolbin/color/icc_creator/example/tritone_cielab.txt base/gsicc_create.c toolbin/color/icc_creator/ICC_Creator/targetver.h toolbin/color/icc_creator/ICC_Creator/ICC_CreatorDlg.h toolbin/color/icc_creator/ICC_Creator/res/ICC_Creator.rc2 psi/zcie.h psi/write_t2.c base/gsicc_create.h toolbin/color/icc_creator/example/color_names.txt base/gscms.h toolbin/color/icc_creator/ICC_Creator/icc_create.cpp toolbin/color/icc_creator/ICC_Creator/ICC_Creator.h psi/fapibstm.c lib/Fontmap.URW-136.TT]</p> @@ -47468,8 +48188,11 @@ find . -type f | grep -v 'svn-base' | xargs file | grep CRLF | grep -v -E '\.(ds <pre> remove some more CR's and more eol-style native. -find . -type f -exec file {} \; |grep 'CRLF' | grep -v '/Projects' | grep -v 'svn-base' | cut -f 1 -d ':' | xargs -n 1 svn propset svn:eol-style native -find . -type f -exec file {} \; |grep 'CRLF' | grep -v '/Projects' | grep -v 'svn-base' | cut -f 1 -d ':' | xargs -n 1 dos2unix +find . -type f -exec file {} \; |grep 'CRLF' | grep -v '/Projects' | \ +grep -v 'svn-base' | cut -f 1 -d ':' | xargs -n 1 svn propset \ +svn:eol-style native +find . -type f -exec file {} \; |grep 'CRLF' | grep -v '/Projects' | \ +grep -v 'svn-base' | cut -f 1 -d ':' | xargs -n 1 dos2unix </pre> <p>[lcms/Delphi/delphidemo.dof lcms/src/makefile.simple lcms/Delphi/demo1.pas lcms/python/testbed/srgb2xyz.py lcms/Delphi/Samples/create.pas lcms/python/testbed/srgb2lab.py lcms/Delphi/delphidemo.dpr lcms/python/testbed/cam02.py lcms/makefile.simple lcms/samples/makefile.simple lcms/Delphi/Samples/TEST.PAS lcms/Delphi/delphidemo.cfg lcms/python/testbed/createmsh.py lcms/python/testbed/lab2adobe.py lcms/Delphi/Samples/testfrm.pas lcms/Delphi/Samples/testwp.pas lcms/src/lcms.def lcms/Delphi/Samples/getxyz.pas]</p> @@ -47491,8 +48214,16 @@ manually fixing the last few files which escaped fileutils' identification. <pre> Changes c/c++/shell script/english text to native text and strip off CR. -find . -type f -exec grep -l '\r\n' {} \; | grep -v 'svn-base' | grep -v '\.vcproj' | grep -v '/Projects' | xargs -n 1 file | grep -E '(ASCII C\+\+ program text|ISO\-8859 English text|ASCII C program text|shell script text executable)' | cut -f 1 -d ':' | xargs dos2unix -find . -type f -exec grep -l '\r\n' {} \; | grep -v 'svn-base' | grep -v '\.vcproj' | grep -v '/Projects' | xargs -n 1 file | grep -E '(ASCII C\+\+ program text|ISO\-8859 English text|ASCII C program text|shell script text executable)' | cut -f 1 -d ':' | xargs svn propset svn:eol-style native +find . -type f -exec grep -l '\r\n' {} \; | grep -v 'svn-base' | \ +grep -v '\.vcproj' | grep -v '/Projects' | xargs -n 1 file | \ +grep -E '(ASCII C\+\+ program text|ISO\-8859 English text|ASCII \ +C program text|shell script text executable)' | cut -f 1 -d ':' |\ +xargs dos2unix +find . -type f -exec grep -l '\r\n' {} \; | grep -v 'svn-base' | \ +grep -v '\.vcproj' | grep -v '/Projects' | xargs -n 1 file | grep -E \ +'(ASCII C\+\+ program text|ISO\-8859 English text|ASCII C program text|\ +shell script text executable)' | cut -f 1 -d ':' | xargs svn propset \ +svn:eol-style native </pre> @@ -47544,24 +48275,37 @@ because MSVC 6 requires this. <blockquote> <pre> Merge of icc_work branch into trunk. - -These changes make the color architecture of the graphics library ICC-based. All colors are now managed in terms of ICC profiles including PS CIE color spaces, for which equivalent ICC profiles are created. A big feature of this change is that it makes it very easy to interface a color management module (CMM) to ghostscript. The default CMM is now littleCMS and the interface to littleCMS is contained in gsicc_littlecms.c . - -New member variables were added to the imager state including an ICC manager, which stores the default ICC profiles; a link cache, which reduces the cost of creating links between ICC profiles, and a profile cache which stores color spaces created from PS CIE, PDF CalRGB and PDF CalGray colors spaces. - -A new directory named iccprofiles has been added. It contains the default ICC profiles used if none are specified in the command line. If COMPILE_INITS=1, these will be included in the ROM file system. The new command line options related to ICC profiles are described in the Use.htm documentation. - -For c-list based rendering, all ICC profiles used in the rendering are stored in the c-list. During multi-threaded c-list reading, a link cache is associated with the primary reader device and is shared amongst the various threads. - -Efficiency improvements were made in the handling of soft mask groups, shading smoothness calculations, and color image rendering. - -For details on the branch, please see the commits that were made within the branch. There remain indeterminisms to fix. The files affected include Bug688807.pdf, Bug688845.eps, Bug690208.pdf, 09-34.PS, CATX0988.pdf, CATX1028.pdf, CATX1101.pdf, CATX5529.pdf. - -Rendering issues to investigate include Bug689830.pdf, fts43xx.xps (page 3) (shopping cart image), Bug689880.pdf, Bug691002.pdf, Bug689968.pdf, Bug688584.ps (page 4), catx4949.pdf. - -Note that the number of differences generated with the merge amounts to pretty much every file. - -Thanks to everyone who helped and provided input in this work, especially Ray Johnston. +These changes make the color architecture of the graphics library ICC-based. +All colors are now managed in terms of ICC profiles including PS CIE color +spaces, for which equivalent ICC profiles are created. A big feature of +this change is that it makes it very easy to interface a color management +module (CMM) to ghostscript. The default CMM is now littleCMS and the +interface to littleCMS is contained in gsicc_littlecms.c . +New member variables were added to the imager state including an ICC manager, +which stores the default ICC profiles; a link cache, which reduces the cost of +creating links between ICC profiles, and a profile cache which stores color +spaces created from PS CIE, PDF CalRGB and PDF CalGray colors spaces. +A new directory named iccprofiles has been added. It contains the default +ICC profiles used if none are specified in the command line. If +COMPILE_INITS=1, these will be included in the ROM file system. The new +command line options related to ICC profiles are described in the Use.htm +documentation. +For c-list based rendering, all ICC profiles used in the rendering are stored in +the c-list. During multi-threaded c-list reading, a link cache is associated with +the primary reader device and is shared amongst the various threads. +Efficiency improvements were made in the handling of soft mask groups, shading +smoothness calculations, and color image rendering. +For details on the branch, please see the commits that were made within the +branch. There remain indeterminisms to fix. The files affected include +Bug688807.pdf, Bug688845.eps, Bug690208.pdf, 09-34.PS, CATX0988.pdf, +CATX1028.pdf, CATX1101.pdf, CATX5529.pdf. +Rendering issues to investigate include Bug689830.pdf, fts43xx.xps (page 3) +(shopping cart image), Bug689880.pdf, Bug691002.pdf, Bug689968.pdf, +Bug688584.ps (page 4), catx4949.pdf. +Note that the number of differences generated with the merge amounts to +pretty much every file. +Thanks to everyone who helped and provided input in this work, especially +Ray Johnston. </pre> <p>[base/gdevpdfk.c base/gxclimag.c doc/Use.htm base/gdevdflt.c psi/icie.h base/gxpcmap.c base/gxpcolor.h lcms base/gscsepr.c base/gxshade4.c base/gxclthrd.c base/gxcmap.c base/gscscie.c base/gdevwts.c base/gsistate.c base/msvclib.mak base/gxclpage.c base/gscolor2.c base/gsicc_profilecache.c base/gxistate.h base/gscolor2.h base/gsicc_profilecache.h iccprofiles base/gdevp14.c base/gsicc_create.c base/gdevp14.h base/gsicc_create.h psi/write_t2.c psi/zusparam.c base/gdevpbm.c psi/zcolor.c psi/ztrans.c base/gdevpdft.c base/gxshade1.c /trunk/gs base/gdevpsdi.c psi/ireclaim.c psi/os2.mak base/watclib.mak Resource/Init/gs_lev2.ps base/gdevpsdu.c base/gscie.c base/gxclutil.c base/gscolor3.c base/gdevpsd.c base/gscie.h base/gxiscale.c base/gxcldev.h Resource/Init/gs_res.ps base/gxifast.c base/gxdevcli.h base/openvms.mak base/watcw32.mak base/gscms.h psi/msvc32.mak base/gsalloc.c base/lcms.mak base/gxp1fill.c base/gximage.h base/gsciemap.c base/gdevpx.c psi/zcsdevn.c base/ugcclib.mak base/unix-gcc.mak base/gsovrc.c base/gxcie.h base/macos-mcp.mak base/gxshade6.c base/macosx.mak base/gsccolor.h base/gdevrinkj.c base/unixansi.mak base/devs.mak base/gsicc.c base/gxipixel.c base/lib.mak psi/zimage.c base/gsicc.h psi/dxmain.c psi/dxmainc.c Resource/Init/pdf_draw.ps base/gscolor.c Resource/Init/pdf_ops.ps psi/zdevice.c psi/zcie.c psi/zdpnext.c base/gxclist.c psi/zcie.h base/gximono.c base/gxidata.c base/gstrans.c psi/iimage.h base/gdevpdfb.c base/gxclist.h base/gxshade.c base/gstrans.h base/gxclrast.c psi/zncdummy.c base/gxshade.h toolbin/color base/gsiccmanage.c base/Makefile.in base/gdevpdfv.c base/gsiccmanage.h base/gsicc_littlecms.c base/gxclpath.c base/gsicc_littlecms.h psi/icontext.c base/gxclpath.h base/gsstruct.h base/gdevxcf.c base/gxicolor.c base/gscspace.c base/gdevimdi.c base/gscdevn.c base/gscolor1.c base/gxclread.c base/gscspace.h base/bcwin32.mak base/gsdparam.c base/gs.mak psi/zshade.c base/gdevbbox.c psi/int.mak base/gxcspace.h psi/zicc.c base/gsstate.c base/winlib.mak base/gsicccache.c psi/zicc.h psi/zimage3.c base/gsicccache.h base/gdevpdfc.c base/gstparam.h base/gxblend.c base/gdevpdfg.c base/gxblend.h]</p> </blockquote> @@ -47777,7 +48521,8 @@ Related bug: 691304 & 691312.</pre> 2010-05-18T22:40:39.023883Z Hin-Tak Leung</strong></p> <blockquote> <pre> -define -DHAVE_CONFIG_H and run jbig2dec/configure from top-level configure. The fixes some portability issues seen on opensolaris; further follow-up to bug 691304</pre> +define -DHAVE_CONFIG_H and run jbig2dec/configure from top-level configure. +The fixes some portability issues seen on opensolaris; further follow-up to bug 691304</pre> <p>[base/Makefile.in base/configure.ac]</p> </blockquote> @@ -47816,7 +48561,10 @@ Disabling compiler warnings for discarding 'const'. 2010-05-18T08:55:18.202611Z Chris Liddell</strong></p> <blockquote> <pre> -Bug 691313: remove the IBM Omni driver from the default build on Linux. Previously it could be excluded by giving configure "--without-omni", this revision reverses the logic, so Omni can be include by giving configure "--with-omni".</pre> +Bug 691313: remove the IBM Omni driver from the default build on Linux. +Previously it could be excluded by giving configure "--without-omni", +this revision reverses the logic, so Omni can be include by giving +configure "--with-omni".</pre> <p>[base/configure.ac]</p> </blockquote> @@ -47824,7 +48572,8 @@ Bug 691313: remove the IBM Omni driver from the default build on Linux. Previous 2010-05-18T04:32:25.607601Z Marcos H. Woehrmann</strong></p> <blockquote> <pre> -Change the order in which jobs that take too long are killed on the cluster nodes to prevent leftover jobs when running bmpcmp. +Change the order in which jobs that take too long are killed on the cluster +nodes to prevent leftover jobs when running bmpcmp. </pre> <p>[toolbin/localcluster/run.pl]</p> </blockquote> @@ -48020,7 +48769,9 @@ use CC_ instead of CC like everywhere else, to make the "so" target wo 2010-05-15T06:30:20.380857Z Hin-Tak Leung</strong></p> <blockquote> <pre> -"-shared" is a linker flag and not a compiler (object code generation) flag; another piece of trying to make "make -f base/unix-gcc.mak" work</pre> +"-shared" is a linker flag and not a compiler (object code +generation) flag; another piece of trying to +make "make -f base/unix-gcc.mak" work</pre> <p>[base/unix-gcc.mak]</p> </blockquote> @@ -48041,7 +48792,8 @@ generic unix values here. 2010-05-15T06:23:35.840946Z Hin-Tak Leung</strong></p> <blockquote> <pre> -correct documentation on how make so should work - ./configure --enable-dynamic is required</pre> +correct documentation on how make so should work - +./configure --enable-dynamic is required</pre> <p>[doc/Make.htm]</p> </blockquote> @@ -48057,7 +48809,8 @@ adding new header dependencies from the recent remove-globals effort</pre> 2010-05-15T03:13:49.664716Z Hin-Tak Leung</strong></p> <blockquote> <pre> -adding a needed include to silent a compiler warning introduced by the recent remove-globals effort</pre> +adding a needed include to silent a compiler warning introduced by the +recent remove-globals effort</pre> <p>[base/gslibctx.c]</p> </blockquote> @@ -48108,7 +48861,9 @@ nobody has noticed since the merge (8.57-8.60) until now. 2010-05-15T02:58:14.802157Z Hin-Tak Leung</strong></p> <blockquote> <pre> -freetype2 dependency in base/unixansi.mak to make "make -f base/unixansi.mak" work; another part for bug 691306</pre> +freetype2 dependency in base/unixansi.mak to +make "make -f base/unixansi.mak" work; +another part for bug 691306</pre> <p>[base/unixansi.mak]</p> </blockquote> @@ -48116,7 +48871,8 @@ freetype2 dependency in base/unixansi.mak to make "make -f base/unixansi.ma 2010-05-15T02:57:22.770443Z Hin-Tak Leung</strong></p> <blockquote> <pre> -freetype2 dependency in base/unix-gcc.mak to make "make -f base/unix-gcc.mak" work; bug 691306</pre> +freetype2 dependency in base/unix-gcc.mak to +make "make -f base/unix-gcc.mak" work; bug 691306</pre> <p>[base/unix-gcc.mak]</p> </blockquote> @@ -48164,7 +48920,8 @@ Fixes Bug 691301. 2010-05-14T04:23:14.678757Z Hin-Tak Leung</strong></p> <blockquote> <pre> -remove one extra tab introduced in r10994; non-GNU Make on Tru64 and HP-UX is picky. Bug 688184 and bug 691299</pre> +remove one extra tab introduced in r10994; non-GNU Make on Tru64 and HP-UX is +picky. Bug 688184 and bug 691299</pre> <p>[psi/psromfs.mak]</p> </blockquote> @@ -48172,7 +48929,8 @@ remove one extra tab introduced in r10994; non-GNU Make on Tru64 and HP-UX is pi 2010-05-14T04:20:29.682174Z Hin-Tak Leung</strong></p> <blockquote> <pre> -HP compiler quirk - apparently the same workaround is needed for SUN Pro C and GCC 1.x (see a few lines before this change) ; bug 688184</pre> +HP compiler quirk - apparently the same workaround is needed for SUN Pro C and +GCC 1.x (see a few lines before this change) ; bug 688184</pre> <p>[contrib/opvp/opvp.h]</p> </blockquote> @@ -48315,7 +49073,10 @@ to increment the imagecount when images were loaded. Fixed here. 2010-05-11T17:25:01.376580Z Chris Liddell</strong></p> <blockquote> <pre> -Bugs 690356 and 690832: have the colour space object take a copy of string data associated with an indexed colour space lookup table. This prevents the colour space finalising code (gx_final_Indexed) freeing the contents of a Postscript object which may still be in use.</pre> +Bugs 690356 and 690832: have the colour space object take a copy of string +data associated with an indexed colour space lookup table. This prevents the +colour space finalising code (gx_final_Indexed) freeing the contents of a +Postscript object which may still be in use.</pre> <p>[psi/zcolor.c]</p> </blockquote> @@ -48345,9 +49106,11 @@ expected. 2010-05-11T14:34:32.672494Z Chris Liddell</strong></p> <blockquote> <pre> -Revise the UFST interface code for PCL/PXL and GS to work with the changes to eliminate global variables in the Artifex code base. - -NOTE: the UFST_REENTRANT configuration was broken, and still is (it has been since the creation of gxfapiu.[ch] files. To be resolved in the future. At this time, therefore, no build integrating UFST can be thread safe. +Revise the UFST interface code for PCL/PXL and GS to work with the changes to +eliminate global variables in the Artifex code base. +NOTE: the UFST_REENTRANT configuration was broken, and still is (it has been +since the creation of gxfapiu.[ch] files. To be resolved in the future. At +this time, therefore, no build integrating UFST can be thread safe. </pre> @@ -48373,7 +49136,8 @@ it protects us from making the same mistake in future. 2010-05-11T12:41:44.704781Z Hin-Tak Leung</strong></p> <blockquote> <pre> -replace "/*" by "<slash><star>" to avoid compiler warning about comments inside comment </pre> +replace "/*" by "<slash><star>" to avoid +compiler warning about comments inside comment </pre> <p>[base/mkromfs.c]</p> </blockquote> @@ -48381,7 +49145,11 @@ replace "/*" by "<slash><star>" to avoid compile 2010-05-11T11:55:10.416074Z Michael Vrhel</strong></p> <blockquote> <pre> -Debug code for helping in debug of 689737. The pattern that is created is 1 bpp. With this code the pattern bit map is dumped for opening with photoshop as a raw 8bit image. The source of the problem appears to be incorrect creation of the pattern bit map when GraphicAlphaBits is set to greater than 1.</pre> +Debug code for helping in debug of 689737. The pattern that is created is 1 +bpp. With this code the pattern bit map is dumped for opening with photoshop +as a raw 8bit image. The source of the problem appears to be incorrect +creation of the pattern bit map when GraphicAlphaBits is set to greater than +1.</pre> <p>[base/gxpcmap.c]</p> </blockquote> @@ -48430,7 +49198,12 @@ which actually use the OtherSubrs to set the point. 2010-05-10T12:29:09.676516Z Michael Vrhel</strong></p> <blockquote> <pre> -Retry of fix for Bug 69048 (this one actually builds...) Again this should only be a factor when using GraphicsAlphaBits. The fix was to make sure that when GraphicsAlphaBits is used we initialize the pattern bits buffer. Otherwise the get_bits operation used during the gx_default_copy_alpha grabs uninitialized memory. Since we do not test with GraphicsAlphabits in the regression testing I don't expect there to be any differences.</pre> +Retry of fix for Bug 69048 (this one actually builds...) Again this should +only be a factor when using GraphicsAlphaBits. The fix was to make sure +that when GraphicsAlphaBits is used we initialize the pattern bits buffer. +Otherwise the get_bits operation used during the gx_default_copy_alpha grabs +uninitialized memory. Since we do not test with GraphicsAlphabits in the +regression testing I don't expect there to be any differences.</pre> <p>[base/lib.mak base/gxpcmap.c base/gxdevmem.h base/gdevabuf.c base/gspaint.c]</p> </blockquote> @@ -48446,7 +49219,12 @@ Reversion to 11210 until I figure out what went wrong...</pre> 2010-05-09T23:10:59.799862Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for Bug 690487. This should only be a factor when using GraphicsAlphaBits. The fix was to make sure that when GraphicsAlphaBits is used we initialize the pattern bits buffer. Otherwise the get_bits operation used during the gx_default_copy_alpha grabs uninitialized memory. Since we do not test with GraphicsAlphabits in the regression testing I don't expect there to be any differences.</pre> +Fix for Bug 690487. This should only be a factor when using GraphicsAlphaBits. +The fix was to make sure that when GraphicsAlphaBits is used we initialize the +pattern bits buffer. Otherwise the get_bits operation used during the +gx_default_copy_alpha grabs uninitialized memory. Since we do not test with +GraphicsAlphabits in the regression testing I don't expect there to be any +differences.</pre> <p>[base/gsutil.h base/lib.mak base/gxpcmap.c base/gspaint.c base/gsutil.c]</p> </blockquote> @@ -48527,7 +49305,9 @@ Really, properly, silence the gcc compiler this time....</pre> 2010-05-07T14:30:08.276765Z Ray Johnston</strong></p> <blockquote> <pre> -Fix clist_band_height to use the macro defined in gxband.h as other code does to prevent future bitrot. Also use macros for the clist_ cfname, cfile, bfname, bfile.</pre> +Fix clist_band_height to use the macro defined in gxband.h as other +code does to prevent future bitrot. Also use macros for the clist_ cfname, +cfile, bfname, bfile.</pre> <p>[base/gxclist.h]</p> </blockquote> @@ -48535,7 +49315,8 @@ Fix clist_band_height to use the macro defined in gxband.h as other code does to 2010-05-07T14:23:18.978837Z Ray Johnston</strong></p> <blockquote> <pre> -Fix number of elements in the BAND_PARAMS_INITIAL initializer macro to correspond to the size of gx_band_params_t (needed since rev 5751).</pre> +Fix number of elements in the BAND_PARAMS_INITIAL initializer macro to +correspond to the size of gx_band_params_t (needed since rev 5751).</pre> <p>[base/gxband.h]</p> </blockquote> @@ -49169,7 +49950,9 @@ Add back in a call removed in (a merging) error in my previous commit (11137).</ 2010-04-27T14:53:14.939131Z Chris Liddell</strong></p> <blockquote> <pre> -Bug 691260: make the FAPI and Freetype related warning messages debug only, and depend on -Zm for the FAPI warnings or -Z1 for the Freetype warnings. Also address compiler warnings in fapi_ft.c.</pre> +Bug 691260: make the FAPI and Freetype related warning messages debug only, +and depend on -Zm for the FAPI warnings or -Z1 for the Freetype warnings. +Also address compiler warnings in fapi_ft.c.</pre> <p>[psi/fapi_ft.c psi/zfapi.c]</p> </blockquote> @@ -49191,7 +49974,8 @@ currently broken). 2010-04-27T09:56:26.779813Z Till Kamppeter</strong></p> <blockquote> <pre> -Made the CUPS Raster output device working in a multi-threaded mode, removing all global variables. Thanks to James Cloos for the patch. Fixes bug #691241. +Made the CUPS Raster output device working in a multi-threaded mode, removing all +global variables. Thanks to James Cloos for the patch. Fixes bug #691241. </pre> <p>[cups/gdevcups.c]</p> </blockquote> @@ -49220,7 +50004,12 @@ Ensure that the BuildChar object is not the null object before trying access its 2010-04-26T05:58:46.519692Z Michael Vrhel</strong></p> <blockquote> <pre> -Change so that when a graphic state is restored, the overprint compositor action only occurs if there is a change from the current overprint state. This fixes a problem in one of the files associated with bug 691014. In the particular file, overprint compositor actions were getting placed into a pattern clist. The file in fact had no overprint settings. Ran regression test, no differences expected.</pre> +Change so that when a graphic state is restored, the overprint compositor +action only occurs if there is a change from the current overprint state. +This fixes a problem in one of the files associated with bug 691014. In +the particular file, overprint compositor actions were getting placed into +a pattern clist. The file in fact had no overprint settings. +Ran regression test, no differences expected.</pre> <p>[base/gsstate.c]</p> </blockquote> @@ -49276,11 +50065,25 @@ during regression testing. Bug 691240. 2010-04-25T00:41:40.540207Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix for Bug 691014. Problem was caused by the fact that we had a soft mask present and a pattern with no transparency. This means the PDF14 device is installed and more importantly that transparency state pushes and pops occur to keep the softmask in sync with the graphic state. This particular files pattern is installed as a clist, which happens to not have any transparency. The transparency state pushes and pops were getting placed into the pattern clist when the Q and q operations occurred in the pattern, which was causing problems since the pattern clist device had no pdf14 device installed to handle such commands. - -The solution is to check, when a transparency compositor action is to occur, if the current device is a pattern accumulator or a pattern-clist device. If it is, then the pattern instance is checked to see if it has transparency. If it does not, then the transparency state chance is ignored. This all occurs on the clist writing phase in the gs_trans functions. - -In addition, a fix was made so that the pdf14custom device sets up it's color information correctly. For subtractive devices that do not have cmyk process colorants the custompdf14 device is installed. This pdf14 device was obtaining its color_info from the target device. The pdf14 device must be continuous tone even if the target device is not. +Fix for Bug 691014. Problem was caused by the fact that we had a soft +mask present and a pattern with no transparency. This means the PDF14 +device is installed and more importantly that transparency state pushes +and pops occur to keep the softmask in sync with the graphic state. This +particular files pattern is installed as a clist, which happens to not have +any transparency. The transparency state pushes and pops were getting placed +into the pattern clist when the Q and q operations occurred in the pattern, which +was causing problems since the pattern clist device had no pdf14 device installed to +handle such commands. +The solution is to check, when a transparency compositor action is to occur, if the +current device is a pattern accumulator or a pattern-clist device. If it is, then +the pattern instance is checked to see if it has transparency. If it does not, then +the transparency state chance is ignored. This all occurs on the clist writing phase +in the gs_trans functions. + +In addition, a fix was made so that the pdf14custom device sets up it's color information +correctly. For subtractive devices that do not have cmyk process colorants the custompdf14 +device is installed. This pdf14 device was obtaining its color_info from the target device. +The pdf14 device must be continuous tone even if the target device is not. Ran a regression test and saw no differences.</pre> <p>[base/gdevp14.c base/lib.mak base/gstrans.c]</p> @@ -49301,7 +50104,8 @@ representation of 'cmap' table doesn't need this. Bug 691253, customer 780. 2010-04-23T12:56:00.372874Z Chris Liddell</strong></p> <blockquote> <pre> -Resolve issues with the language_switch Ghostscript build for Windows, since Freetype enabled became the default for the normal GS build. +Resolve issues with the language_switch Ghostscript build for Windows, since +Freetype enabled became the default for the normal GS build. </pre> <p>[/trunk/ghostpdl/common/msvc_top.mak /trunk/ghostpdl/language_switch/pspcl6_msvc.mak /trunk/ghostpdl/psi/psitop.c psi/msvc32.mak]</p> </blockquote> @@ -49310,7 +50114,10 @@ Resolve issues with the language_switch Ghostscript build for Windows, since Fre 2010-04-23T04:10:50.732099Z Michael Vrhel</strong></p> <blockquote> <pre> -Fix of minor memory leak found by Ray. maskbuf entry of transparency ctx object was not getting freed. The large mask buffer, which is a member variable of maskbuf was getting freed but not this 12 byte structure. No expected differences.</pre> +Fix of minor memory leak found by Ray. maskbuf entry of transparency ctx +object was not getting freed. The large mask buffer, which is a member +variable of maskbuf was getting freed but not this 12 byte structure. +No expected differences.</pre> <p>[base/gdevp14.c]</p> </blockquote> @@ -49706,7 +50513,9 @@ No expected differences. 2010-04-14T16:25:11.391305Z Chris Liddell</strong></p> <blockquote> <pre> -Reverse the previous build options for Freetype integration: now --disable-freetype for configure on Unix type systems or pass FT_BRIDGE=0 to nmake on Windows if you do not want to integrate Freetype. +Reverse the previous build options for Freetype integration: now +--disable-freetype for configure on Unix type systems or pass FT_BRIDGE=0 +to nmake on Windows if you do not want to integrate Freetype. </pre> <p>[base/configure.ac psi/msvc32.mak]</p> </blockquote> @@ -49764,7 +50573,8 @@ a few more comments about some microsoft CJK fonts</pre> 2010-04-14T02:31:58.209185Z Masaki Ushizaka</strong></p> <blockquote> <pre> -Fixed jbig2dec command getopt() parameter for -v option. Not used by ghostscript itself but worth for standalone debugging.</pre> +Fixed jbig2dec command getopt() parameter for -v option. Not used by +ghostscript itself but worth for standalone debugging.</pre> <p>[jbig2dec/jbig2dec.c]</p> </blockquote> @@ -49856,8 +50666,11 @@ No differences shown by localcluster testing. <pre> A fix for 691081, 691206, and part of 690094. -From r9769, jbig2dec wasn't capable of decoding some JBIG2 files and throwing a error "jbig2dec FATAL ERROR runlength too large in export symbol table (XXX > XX - XX) (segment 0xXX)". -This was caused by accidentaly bound checking export symbol table size with number of non-export symbol. This fixes it. +From r9769, jbig2dec wasn't capable of decoding some JBIG2 files and throwing +a error "jbig2dec FATAL ERROR runlength too large in export symbol table +(XXX > XX - XX) (segment 0xXX)". +This was caused by accidentaly bound checking export symbol table size with +number of non-export symbol. This fixes it. No differences expected, other than JBIG2 files suffered from this problem. </pre> <p>[jbig2dec/jbig2_symbol_dict.c]</p> @@ -49867,7 +50680,8 @@ No differences expected, other than JBIG2 files suffered from this problem. 2010-04-13T09:38:22.017180Z Chris Liddell</strong></p> <blockquote> <pre> -Minor revision to FAPI code to better ensure GS errors in callbacks survive through the font renderer library.</pre> +Minor revision to FAPI code to better ensure GS errors in callbacks +survive through the font renderer library.</pre> <p>[psi/fapi_ft.c psi/zfapi.c psi/ifapi.h psi/fapiufst.c]</p> </blockquote> @@ -49885,7 +50699,9 @@ confused with global modifiable data. 2010-04-12T10:44:43.428786Z Chris Liddell</strong></p> <blockquote> <pre> -Remove the hardcoded identity matrix in the Type 1 serialization code in favour of the new FAPI call allowing the interface code to dictate the matrix to be used.</pre> +Remove the hardcoded identity matrix in the Type 1 serialization code in +favour of the new FAPI call allowing the interface code to dictate the matrix +to be used.</pre> <p>[psi/zfapi.c]</p> </blockquote> @@ -50158,7 +50974,8 @@ No expected differences. 2010-04-07T13:23:37.938542Z Chris Liddell</strong></p> <blockquote> <pre> -Revise the interface code and the use of FT so that both use GS managed memory, rather than the stdlib memory routines (malloc/free and co.).</pre> +Revise the interface code and the use of FT so that both use GS managed +memory, rather than the stdlib memory routines (malloc/free and co.).</pre> <p>[psi/fapi_ft.c]</p> </blockquote> @@ -50203,7 +51020,9 @@ bmpcmp and found to be acceptable. 2010-04-06T17:15:54.520182Z Michael Vrhel</strong></p> <blockquote> <pre> -Update of fuzzy to report average and max color errors. This is useful for continuous tone images only. If the max error reaches the largest possible, the calculations for these values are not performed.</pre> +Update of fuzzy to report average and max color errors. This is useful +for continuous tone images only. If the max error reaches the largest +possible, the calculations for these values are not performed.</pre> <p>[toolbin/tests/fuzzy.c]</p> </blockquote> @@ -50331,7 +51150,8 @@ Update the to latest FT code from the FT git repository.</pre> 2010-04-05T10:03:59.155794Z Chris Liddell</strong></p> <blockquote> <pre> -Fix the FAPI implementation of finding the appropriate bytes for a given character code from an array of strings representing a CMap.</pre> +Fix the FAPI implementation of finding the appropriate bytes for a given +character code from an array of strings representing a CMap.</pre> <p>[psi/zfapi.c]</p> </blockquote> @@ -50356,7 +51176,9 @@ ia3z3519.pdf and the incorrectly scaled outline in womanface.pdf. 2010-04-02T09:19:23.286738Z Chris Liddell</strong></p> <blockquote> <pre> -Extend Ken's change to avoid using FT's "synthetic" vertical metrics for Type42 fonts to cover all fonts using TTF outlines (so CIDType 2 fonts, as well).</pre> +Extend Ken's change to avoid using FT's "synthetic" vertical metrics +for Type42 fonts to cover all fonts using TTF outlines (so CIDType 2 fonts, as +well).</pre> <p>[psi/fapi_ft.c]</p> </blockquote> @@ -50411,7 +51233,10 @@ Correct a logical error/typo in the fallback to non-hinted condition.</pre> 2010-03-31T13:22:01.442343Z Chris Liddell</strong></p> <blockquote> <pre> -Prevent applying the nominalWidthX for T2 fonts, when FT already applies it for us. Previously, the code was actually erroneously adding the defaultWidthX. Since this use of nominalWidthX *may* be renderer dependent, it is now controlled by the can_replace_metrics() call.</pre> +Prevent applying the nominalWidthX for T2 fonts, when FT already applies +it for us. Previously, the code was actually erroneously adding the +defaultWidthX. Since this use of nominalWidthX *may* be renderer dependent, +it is now controlled by the can_replace_metrics() call.</pre> <p>[psi/zfapi.c]</p> </blockquote> @@ -50419,7 +51244,8 @@ Prevent applying the nominalWidthX for T2 fonts, when FT already applies it for 2010-03-31T13:16:41.790764Z Chris Liddell</strong></p> <blockquote> <pre> -In the even a glyph name is not found in the CharStrings dictionary, fall back to using the .notdef (instead of returning an error).</pre> +In the even a glyph name is not found in the CharStrings dictionary, fall +back to using the .notdef (instead of returning an error).</pre> <p>[psi/zfapi.c]</p> </blockquote> @@ -50427,7 +51253,8 @@ In the even a glyph name is not found in the CharStrings dictionary, fall back t 2010-03-31T13:07:44.152960Z Chris Liddell</strong></p> <blockquote> <pre> -For certain errors from FT, retry interpretting the glyph without hinting - this more closely matches the existing behaviour.</pre> +For certain errors from FT, retry interpretting the glyph without hinting - this more +closely matches the existing behaviour.</pre> <p>[psi/fapi_ft.c]</p> </blockquote> @@ -50550,7 +51377,9 @@ sfnts glyfs strings. Bug 691221. 2010-03-29T07:52:49.284823Z Chris Liddell</strong></p> <blockquote> <pre> -Change the FT interface code so we always use metrics retrieved from Freetype, rather than attempting to "fabricate" metrics (which have already been handled correctly by FT).</pre> +Change the FT interface code so we always use metrics retrieved from Freetype, +rather than attempting to "fabricate" metrics (which have already +been handled correctly by FT).</pre> <p>[psi/fapi_ft.c]</p> </blockquote> @@ -50647,7 +51476,9 @@ bitmap. Fixed by choosing sizes more smartly. 2010-03-23T09:02:16.120692Z Till Kamppeter</strong></p> <blockquote> <pre> -CUPS Raster output device: Error out correctly with the return_error() macro and not with "gs_exit(); exit()", force banding mode as there are files which do not render otherwise (Bug #691170). +CUPS Raster output device: Error out correctly with the return_error() macro +and not with "gs_exit(); exit()", force banding mode as there are +files which do not render otherwise (Bug #691170). </pre> <p>[cups/gdevcups.c]</p> </blockquote> @@ -50656,7 +51487,8 @@ CUPS Raster output device: Error out correctly with the return_error() macro and 2010-03-23T00:06:59.853037Z Till Kamppeter</strong></p> <blockquote> <pre> -Code clean-ups in the "cups" output device to fix the segfaults in bug #691170 and bug #691014 (but does not fix the bugs yet). +Code clean-ups in the "cups" output device to fix the segfaults +in bug #691170 and bug #691014 (but does not fix the bugs yet). </pre> <p>[cups/gdevcups.c]</p> </blockquote> @@ -50956,7 +51788,10 @@ current image. With this fix we correctly keep searching to the end. 2010-03-10T15:05:57.116970Z Chris Liddell</strong></p> <blockquote> <pre> -Change how we derive the glyph metrics from FT: we now interpret the glyph description only once, scaled and hinted, and then calculate the metrics from that. It's more accurate, accounts for hints that extend the glyph outline, and should be a worthwhile speed improvement.</pre> +Change how we derive the glyph metrics from FT: we now interpret the glyph +description only once, scaled and hinted, and then calculate the metrics +from that. It's more accurate, accounts for hints that extend the glyph outline +and should be a worthwhile speed improvement.</pre> <p>[psi/fapi_ft.c]</p> </blockquote> @@ -51166,7 +52001,9 @@ updating windows CJK font substitution list for more commonly found MS CJK fonts 2010-03-08T21:47:15.240330Z Hin-Tak Leung</strong></p> <blockquote> <pre> -revert to r8185 version of the korean example - it was removed in r8190 and a corrupted version r9325 was subsequently checked in; found during fixing bug 688437 (incompete font substitution list)</pre> +revert to r8185 version of the korean example - it was removed in r8190 and a +corrupted version r9325 was subsequently checked in; found during fixing bug +688437 (incompete font substitution list)</pre> <p>[examples/cjk/gscjk_ak.ps]</p> </blockquote> @@ -51224,7 +52061,9 @@ code instead. 2010-03-08T09:28:49.484133Z Chris Liddell</strong></p> <blockquote> <pre> -Latest improvements to the FAPI/FT bridge code. This code resolves the issues with font matrices which do more than just scale. It is not yet "finished", but is too big a step forward to risk losing.</pre> +Latest improvements to the FAPI/FT bridge code. This code resolves the +issues with font matrices which do more than just scale. It is not yet +"finished", but is too big a step forward to risk losing.</pre> <p>[psi/fapi_ft.c psi/zfapi.c]</p> </blockquote> @@ -51605,7 +52444,8 @@ in the Subversion repository. 2010-02-25T11:04:59.765077Z Chris Liddell</strong></p> <blockquote> <pre> -add quotes around the expansion of DEVSTUDIO variable when it's used for the recursive nmake call for debug targets - in case it has white space in it.</pre> +add quotes around the expansion of DEVSTUDIO variable when it's used for +the recursive nmake call for debug targets - in case it has white space in it.</pre> <p>[psi/msvc32.mak]</p> </blockquote> @@ -51613,7 +52453,10 @@ add quotes around the expansion of DEVSTUDIO variable when it's used for the rec 2010-02-25T08:21:46.259499Z Masaki Ushizaka</strong></p> <blockquote> <pre> -Fix for bug 691103. The pdfwrite device now considers FDArray fonts' FontMatrix and writes correct W/W2/DW/DW2 widths for CIDFont with unusual FontMatrix. This also fixes a problem gs_font::orig_FontMatrix not being initialized for CIDFont. +Fix for bug 691103. The pdfwrite device now considers FDArray fonts' +FontMatrix and writes correct W/W2/DW/DW2 widths for CIDFont with unusual +FontMatrix. This also fixes a problem gs_font::orig_FontMatrix not being +initialized for CIDFont. Bug687832.pdf and Bug690834.ps will show differences which are improvements. </pre> <p>[Resource/Init/gs_cidfn.ps base/gdevpdtt.c]</p> @@ -51769,7 +52612,9 @@ terminated when : 2010-02-22T11:45:33.943563Z Chris Liddell</strong></p> <blockquote> <pre> -resolve inappropriate variable type (signed vs unsigned) and comparisons with the wrong variable when writing the local subrs info to the serialized T2 Private dictionary.</pre> +resolve inappropriate variable type (signed vs unsigned) and comparisons with +the wrong variable when writing the local subrs info to the serialized T2 Private +dictionary.</pre> <p>[psi/write_t2.c]</p> </blockquote> |