| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
- Adds GPDL to TOC and tweaks Home icon CSS.
- A better TOC, updated copyright header.
- Adds headers in Use.rst for basic use examples.
|
| |
|
| |
|
|
|
|
| |
And set the ending copyright date automatically.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Product family, date docs version for 10.01.0 RC 1
Update News.htm for 10.01.0
Version and dates in man pages
Dates and product string for 10.01.0rc2
Dates and product string for 10.01.0 release
|
| |
|
|
|
|
|
|
| |
- Adds new version number to conf.py
- Removes -dOLDSAFER & old language-bindings folder.
- Updates PDF version
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Fixes favicon, updates docs with further device parameters for pdfwrite.
- Removes translated man pages for German.
- Adds a header to the documentation for all pages.
Header includes:
- Discord link.
- Page feedback link.
- Updates Make.rst with more make commands & moves meta data snippet into header.rst.
- Explicity sets sphinx version for readthedocs in requirements.txt.
- Removes refs to "-dNEWPDF=".
|
|
|
|
| |
interpreted plus some general indentation issues.
|
|
|
|
|
| |
scroll.
<log></log>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Adds -dNO_PDFMARK_OUTLINES switch
to high level devices (VectorDevices.rst).
- Updates PDF to be built from Latex.
- Updates HowToBuildTheDocs.txt with info
around the building the PDF with Latex.
- Fixes the rendering of the unicode >=
character for the Latex PDF output.
- Fixes some broken links in the
language bindings section.
- Fixes a syntax warning around the
layout of a header within the
color management section.
- Updates the Ghostscript.pdf to reflect changes
|
|
|
|
| |
<log></log>
|
|
|
|
|
|
|
| |
- Removes "Indices & Tables" from the TOC
- Updates copyright notice in RST file headers
- Removes "language-bindings" folder in "doc"
- Removes Adobe section & fixes link for News in Readme.rst
<log></log>
|
|
|
|
|
| |
Updates doc/src/conf.py to point to the toc file to ensure
that everything is built for the PDF.
<log></log>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sphinx docs exemplar
Adds a source folder with a README to redo the docs
with Sphinx.
More Sphinx updates - added main skeleton htm pages
gitignore also removes .buildinfo & .doctrees
<log></log>
More Sphinx docs work
Sphinx updates for API page
Sphinx docs: some tidy up start of Use.htm
Sphinx docs: mostly more on Use.htm
Sphinx docs: Completes Use.rst, starts some other pages
Sphinx docs: Completes Devices.rst
Sphinx docs: Start of VectorDevices.rst
Sphinx docs: Completes VectorDevices.rst
Sphinx docs: Start of Drivers.rst
Sphinx docs: Completes Drivers.rst
Sphinx docs: Corrects some links in API.rst
Sphinx docs: Completes Make.rst section
Sphinx docs: Completes Install.rst section
Sphinx docs: Completes Lib.rst and adds footer to all rst files
Sphinx docs: Completes C-style.rst, changes description for "iff"
Sphinx docs: Completes P-style.rst
Sphinx docs: Starts Language.rst and tweaks some other rst files
Sphinx docs: Completes Language.rst and adds "title" directive to all rst files
Sphinx docs: completes Unix-lpr.rst, Fonts.rst, PS-files.rst, News.rst, third-party.rst
Also updates the title header layout for all the rst files
Sphinx docs: Deprecated.rst -> UnsupportedDevices.rst
Sphinx docs: Completes Source.rst
Sphinx docs: Multiple updates across many RST files
Sphinx docs: Completes Develop.rst
Sphinx docs: Fixes build errors and warnings
Sphinx docs: Some tidy up and start of UnsupportedDevices.rst
Sphinx docs: More updates to UnsupportedDevices.rst
Sphinx docs: More tidy up, adds the readthedocs.yaml
<log></log>
Sphinx docs: tidy up language-bindings favicon reference
<log></log>
Sphinx docs: more conf tidy up, fixes a link in Devices.rst
<log></log>
Sphinx docs: Updates News.rst to include News.htm
Updates News.htm to include just the body HTML ready
for insertion into the RST docs or to view standalone.
Updates README to add advice on editing & publishing docs
<log></log>
Sphinx docs: Removes old .htm files and any other seemingly redundant files in "doc"
Sphinx docs: Removes the built output from Sphinx as it is not required
<log></log>
Sphinx docs: Updates devices keywords to be styled with :title: tag
- This wraps these keywords with <cite> at the HTML level
- Also added a requirements.txt file for the .readthedocs.yaml
to use
Sphinx docs: Includes index.htm with prospective readthedocs website redirect
<log></log>
Sphinx docs: Removes README.md and moves info over into HowToBuildTheDocs.txt
Also tidies up a header underline which was too short
in UnsupportedDevices.rst
<log></log>
Sphinx docs: Removes Release.rst
Sphinx docs: Devices.rst - Add bbox notes from earlier 10.0.0 branch commit
See: - add a note about precision of bbox device commit
7f2719bff1d50e151918cf505fa695edc65e936f
Also indents some properties which were children of
a dictionary to make it more understandable.
<log></log>
Sphinx docs: Updates News.htm to reflect recent changes
<log></log>
Sphinx docs: Adds the generated Ghostscript documentation PDF
Generated via sphinx-build
<log></log>
Sphinx docs: Removes redundant link from Install.htm
<log></log>
Sphinx docs: Adds standalone TOC, start of Language Bindings docs
GhostAPI completed here for C sharp.
<log></log>
Sphinx docs: Adds GhostNET documentation
<log></log>
Sphinx docs: Completes the C# documentation
<log></log>
Sphinx docs: Completes Java Language Bindings introduction
<log></log>
Sphinx docs: Completes Java Language Bindings docs
Also fixes a syntax error in API.rst
Sphinx docs: Completes the Python Language Bindings docs
<log></log>
Sphinx docs: Republishes PDF version of docs
Now includes Language Bindings
<log><log>
Sphinx docs: Move language binding "Building GS" section to reference sections in Make.rst
<log></log>
Sphinx docs: Fixes bullet point syntax, and some other tweaks.
Also includes:
Putting "build" before "install" in the left nav
Some small syntax tweaks and improvments.
Sphinx docs: Updates reference: IRC channel -> Discord channel
Sphinx docs: Updates Python Language Bindings with links to C docs and other fixes
<log></log>
Sphinx docs: Completes tweaks for Python section and publishes amended PDF
<log></log>
Sphinx docs: Final tweak to Python section
<log></log>
|
|
|
|
| |
Bug #705830 "imprecise bbox of PDF"
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 7d6d69ff17c43664482fe0dc34676a46ba551d93 accidentally broke
PSPageOptions with multi-page input, because the array of strings was
freed on every page.
This commit fixes that problem; note you cannot change PSPageOptions
once it has been set, except by restoring back to the point before the
device was opened.
Also the documentation formatting was slightly broken, fix that at the
same time.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The gray profiles were not getting set properly when we set the option
to NONE in the SourceObjectICC file for Text, Graphics and Images.
Note that the interaction of -sSourceObjectICC and -dDeviceGrayToK=true/false
is as follows:
If no gray settings are made in SourceObjectICC, and there is DeviceGray
content present in the source file, -dDeviceGrayToK=true/false will be honored.
If the gray objects in SourceObjectICC are set to None, which implies that
ICC color management is not to be applied to these objects, then they
are treated as DeviceGray and always mapped to K values in a CMYK target device,
regardless of the settings of -dDeviceGrayToK (i.e. there is no color
management).
If instead, the gray objects in SourceObjectICC are set to a specific ICC
profile, then they are no longer DeviceGray but are ICC colors. They will
be color managed, regardless of the setting of -dDeviceGrayToK.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Supports out-of-order ranges (if the parser allows it and disables the
PageHandler, i.e., flp device). Also adds support for ranges appended
to the "even" and "odd" keyword following a ":".
As before a trailing "-" in a range implies the last page, and as was
supported by the previous 'gxps' code, a leading "-" also is the last page.
For example, with XPS or PDF: -sPageList=odd:3-7,even:4-8,1-,-1,9
prints pages: 3, 5, 7, 4, 6, 8, 1, 2, ..., last, last, last-1, ..., 1, 9
The PageList string is parsed using C code into an array that consists of
an initial int that is > 0 if the list is ordered, followed by sets of
3 integers per range, even/odd flag (odd=1, even=2), start, end. The
final 3 ints are 0,0,0 as a marker.
The initial int is used by 'pagelist_test_printed' as an index to the next
range to be processed when the PageList is used for languages that can only
be processed sequentially (e.g. PS and PCL) and is updated when the page
passes the end of the current range. A value of -1 means the ranges are
not ordered (not strctly increasing).
The flp_fillpage is changed to ignore errors from processing the PageList
performed by ParsePageList (called from SkipPage) when PageCount is 0
so that parsers that support out of order processing (PDF and XPS) can
continue until later. This should have little or no performance impact
since it is limited to PageCount == 0.
Note that the new PDF parser also uses the C code parser and then uses
the array of ranges returned by ".PDFparsePageList". The old PostScript
based parser has not been updated, although it is easy to do so.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 0abc209b8460396cdece8fc824c053a2662c4cbf altered the default
MaxStripSize from 8KB to 1MB, for all Tiff devices, even though it seems
that only fax readers have a problem with multiple strip TIFF files.
It also did not update the documentation which still stated the default
was 8KB.
After some discussion, it seems wrong that the default should have been
altered, when the documentation points to the recommendation in the TIFF
specification. Additionally the change was to a size of 1MB in the
'hope' that no fax page size would exceed that. Which is not a great way
to handle the problem.
This commit alters just the fax devices to have a default MaxStripSize
of 0, which means the output will be written to a single strip, no
matter how large, thus fulfilling the requirement to support poor fax
reading software, but without affecting the non-fax devices, and more
reliably because it doesn't matter how large the media is, even if it
exceeds 1MB output we will still only get a single strip..
If the reader can't cope with a single huge strip, and wants multiple
strips then the user can override the default by specifying
MaxStripSize on the command line in order to restore multiple-strip
output for fax devices.
Updated the documentation to reflect this.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A customer requested that we make pdf_info.ps work with the new
PDF interpreter, and generate the same information.
This commit modifies the way we extract information on a
page-by-page basis to potentially include the names of spot inks
and information about fonts used on the page.
This is now returned to the PostScript environment using a PDF
dictionary instead of a C structure. The pdf_info.ps program has
been updated so that it use the new information in broadly the
same way as the information from the old PDF interpreter.
There are differences; pdf_info.ps extracts font information
itself, rather than having the interpreter do it. This is not
possible with the new interpreter which is why we have the
PDF interpreter do it for us. In addition the pdf_info.ps
program only descended to the page level whereas the new PDF
interpreter evaluates all objects on the page, potentially
meaning that more fonts (and technically spot inks) might be
detected.
We now have an additional PostScript operator '.PDFPageInfoExt'
which returns 'extended' information about a page. This is the
same as .PDFPageInfo but includes the font and spot ink
information.
Running with -dPDFINFO using either Ghostscript or GhostPDF will
print more information than before, including the spot inks and
considerably more information about fonts than the pdf_info.ps
program emits, including embedding status, descendant fonts
(and their membedding status) and the presence of ToUnicode
CMaps.
Updated documentation for all of the above.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding in the following command line options to provide more flexibility.
-dBlackThresholdL=float /* Luminance threshold */
-dBlackThresholdC=float /* Chrominance threshold */
Where anything above or equal to a BlackThresholdL in terms of Luminance will
be mapped to white. Everything below will be mapped to black. So if
someone wants all colors to go to black (even white ones) they can set
-dBlackThresholdL=101 since all colors will have an L* less than this. If
they want all the colors to go to white, they can set -dBlackThresholdL=-1
since all colors will have an L* greater than this. If they want only pure
white colors to remain white, a value of 100 should work, but I suspect that
could be fraught with rounding errors.
The BlackThresholdC only comes into play with BlackThresholdL < 100. If for
example you have BlackThresholdL = 95 and dBlackThresholdC=10 then only those
colors that have an L* >= 95 and are within a distance of 10 in terms of a*
AND b* values from the neutral axis will be mapped to white. All others
will be mapped to black. So we have a cuboid cut out in CIELAB space
centered on the neutral axis to which we can specify the L* height and the
chroma width. Colors within this cuboid get mapped to white. All
others are mapped to black.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update strings, dates and versions for 9.56.0 release branch
And initial changelog/news entries
Update copyright year in doc files.
Fix GS_PRODUCT string (missing space)
Update release notes: thread safety PSD/ICC profiles
Corrections to release notes.
Date for 9.56.0 RC1
Dates etc for 9.56.0 RC2
Dates and product string for 9.56.0 release
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug #704846 "Optionally omit CreatingTime in PDF output for reproducibility"
Some content in a PDF file is created using the system time, and will
vary depending on the precise time the file is created. This is entirely
correct and we are not prepared to alter this behaviour.
However said content is also often optional, but there was no way to
prevent pdfwrite creating it.
This commit adds three new controls; OmitDateInfo, OmitXMP and OmitID
which direct pdfwrite not to create and include the CreationDate and
ModDate in the /Info dict and Metadata (OmitInfoDate), the file ID in
the trailer dictionary (OmitID) and the XMP Metadata included in the
Catalog dictionary (OmitXMP).
There are, however, other considerations. XMP metadata is required for a
valid PDF/A file, /ID is required for PDF 2.0, and for encrypted files
and CreationDate is required for PDF/X-3.
As a result if you try to set these controls with one of those other
features, it will raise a warning and ignore the control.
|
|
|
|
|
|
|
|
|
| |
Add a new device 'pclm8' which outputs in DeviceGray, for use with
'WiFi Direct Print' enabled monochrome printers.
While the printer is supposed to be able to accept RGB, and print to
gray, it's quicker to send Gray instead of RGB when we know it is
required.
|
|
|
|
|
|
|
| |
This is a clone of the pngalpha device, with antialiasing disabled
by default. People should use this, together with the DownScaleFactor
parameter to acheive antialiasing without the nasty effects given
in some cases by GraphicsAlphaBits.
|
| |
|
| |
|
| |
|
|
|
|
| |
was THIRDPARTY.htm
|
|
|
|
| |
fixes HTML markup on some pages to address accessibility issues.
|
|
|
|
| |
pdfi cannot support Postscript operators in Fontmap and cidfmap
|
| |
|
|
|
|
| |
navigation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some devices within Ghostscript (currently the x11 devices,
uniprint and opvp/oprp) use non const static variables, so cannot
be run in multiple instances at a time.
We now maintain a core "count" of how many non-threadsafe devices are
being used at any time. This value can be atomically adjusted by calls
to gs_lib_ctx_nts_adjust.
Non threadsafe devices now call gx_init_non_threadsafe_device either
as or as part of their initialise_device proc. This function attempts
to increment the non-threadsafe count and fails to init if there is
already a non-threadsafe device running.
On success, the device finalize method is modified so that it will
decrement the count at the end.
The known non-threadsafe devices are updated to call this.
In order to have somewhere safe to store this count, we introduce
a gs_globals structure, shared between instances. Setting this up
without race conditions requires some new gp_ functions that can
make use of platform specific threading primitives. We have these
implemented for both windows and pthread based platforms. On other
platforms, we drop back to the old unsafe mechanism for counting
instances.
While we do this work, we take the opportunity to push the
gs_memory_t pointer used for non-threadsafe debug printing into thread
local storage.
This enables us to remove the remaining GS_THREADSAFE guarded
compilation from the source code. What is left is broadly down to
allowing debugging collection for statistics, and these are now
controlled by specific COLLECT_STATS_XXX defines. It is assumed
that anyone wanting to collect such stats is smart enough to not
try to do so while using Ghostscript in a multi-instance environment.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that we can pass marked content from the input to the pdfwrite
device we need to be able to control it (this can significantly increase
the size of a PDF file).
This commit adds a new control to GhostPDF '-dPreserveMarkedContent'
which defaults to true. If false then marked content is not passed to
the pdfwrite device.
Add documentation for the parameter, fix formatting of the
PreserveAnnots and PreserveAnnotTypes while we're here.
Finally, when processing optional content, do not emit an EMC if it is
associated with optional content.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
dates, docs etc.
Update dates etc for 9.55.0 RC 1
Updates for the first 9.55.0 release candidate
Updates and corrections for the release highlights
Dates and product string for 9.55.0 release
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug #698881 "Problem with spot color with same name of master color (CMJK) "
In this case the separation is named "YELLOW" which is not the same as
"Yellow" as far as PostScript is concerned because ink names are case-
sensitive.
However, when added to the output filename, not all OS's (in particular
Windows) differentiate filenames based on case, leading to the file
being overwritten.
This commit checks the separation name to see if it matches any of the
process inks (ignoring case) and if it does, it appends the separation
number to the ink name for the purpose of creating the filename.
|
| |
|
|
|
|
| |
Some of the ICC profiles were copyrighted and with no license information.
|