13 Apr 22:36 2016

pxl "Staple" patch?

Sorry if this is a dupe. I sent it from the wrong account earlier.

********

Does anybody know when/if

"Bug 696314 [1] - Add PJL to staple documents":
http://bugs.ghostscript.com/show_bug.cgi?id=696314

would appear in a release?

It enables a "staple" option for printers that have a stapler.

(http://bugs.ghostscript.com/attachment.cgi?id=12348&action=diff), but I
can't figure out from Bugzilla or Git what happens next or where it
would appear.

Thanks!

Terry

--

--
http://bupkis.org
If you're not here, you haven't got bupkis!

30 Mar 19:45 2016

Re: Wrong architecture on 64 bit build?

genarch.exe creates arch.h, in this case, by copying
arch\windows-x64-msvc.h into obj\arch.h.

The best I can suggest here is to make sure that the obj and obj64
directories are deleted before trying again.

Chris

On 30 March 2016 at 14:55,  <terry <at> cnysupport.com> wrote:
> Well, it's different now.
>
> I took the command line from the VS "build" command and ran it in the 64 bit
> VS command window and got this:
>
> .\obj64\aux_\genarch.exe .\obj64\arch.h .\base\..\arch\windows-x64-msvc.h
> NMAKE : fatal error U1045: spawn failed : Invalid argument
>
> .\obj64\arch.h does indeed, not exist and I don't see it in any of the
> directories.
>
> Do you have any idea what creates it or where it's hiding?
>
> I appreciate the help. I'm just trying to make a tiny change, but it's being
> uncooperative.
>
> When I get this working, I'll submit a patch so "ARCHAIC" is a switch in the
> epson device, not a #define. It's used with some old Epson-compatible
> printers.
>
> Thanks,


30 Mar 02:18 2016

Wrong architecture on 64 bit build?

I compiled the latest GS source on 32 Bit Windows w/Visual Studio 2010,
and targeted a 64 Bit environment.

Everything seemed to work, however I get a message on the 64 bit machine
about it being a 32 bit DLL, even though it's named GSDLL64.DLL, and I

All I need to do is set the "ARCHAIC" switch in the epson device and
recompile, but it's not cooperating.

Does anybody have any suggestions?

Thanks!

Terry

25 Mar 15:30 2016

gsapi_set_stdio() and -OutputFile=-

HI,

I'm the developer of python-ghostscript, an interface to use the
ghostscript api from Python. ATM I try to complete a test-suite. And I'm
failing to redirect stdout using gsapi_set_stdIO(). Unfortunatly
gsapi_set_stdIo is not well documented.

The output-device I'm using is bmp16.

If passing -OutputFile=-, the image data is written to the stdout
instead of being passed to the stdout-function I've set with
gsapi_set_stdio().

And when leaving -Outputfile away, I get the error:
GPL Ghostscript 9.14: Could not open the file .
GPL Ghostscript 9.14: Unrecoverable error, exit code 1

> That doesn't entirely surprise me.

> This is *not* my area really, but I thought that the purpose of the
stdout redirection was so you could redirect the backchannel stuff from
postscript.

> When you use -OutputFile=- that's an instruction to the device, so a
different kettle of monkeys.

So is there some way to make the bmp16-device to use the stdout_fn?
Or which other device should I use?


23 Mar 15:37 2016

Re: Ghostscript and GhostPDL 9.19 release

I've added the files, but I was contemplating doing away with them,

Anyone any thoughts on that?

Chris

On 23/03/16 14:31, Johannes Meixner wrote:
>
> Hello Chris,
>
> On Mar 23 11:38 Chris Liddell wrote (excerpt):
>> Get it here:
>>
>
> On
> near the bottom both links to
>   MD5 Checksums
>   SHA1 Checksums
>
>
> Kind Regards
> Johannes Meixner

23 Mar 12:38 2016

Ghostscript and GhostPDL 9.19 release


Artifex Software, Inc. is happy to announce the release of GPL
Ghostscript 9.19 and GhostPDL 9.19.

Get it here:

For a release summary see:

http://www.ghostscript.com/doc/9.19/News.htm

Thanks to everyone whose hard work made this release possible!

Regards,

Chris

17 Mar 23:07 2016

ps2pdf: Embedded files are removed

Hi

I am trying to convert a pdf file containing an embedded office file to PDF/A(-1 or -2) – I know that this is
not allowed by these versions of PDF/A – with the following command:

gs -dPDFA -dBATCH -dNOPAUSE -dNOOUTERSAVE -dPDFSETTINGS=/printer -dSubsetFonts=true
-dEmbedAllFonts=true -dPDFACompatibilityPolicy=2
-sColorConversionStrategy=/UseDeviceIndependentColor -sProcessColorModel=DeviceRGB
-sDEVICE=pdfwrite -sOutputFile=out.pdf PDFA_def.ps input.pdf

The thing that I would expect is that depending on the -dPDFACompatibilityPolicy switch I would receive
different results. However, the resulting documents are currently always the same, regardless of this
switch, and none of the output files contain the originally embedded office file anymore. How can I get the
expected behaviour for -dPDFACompatibilityPolicy=2 (i.e. an error message) and
-dPDFACompatibilityPolicy=0 (i.e. output is a regular pdf file still containing the embedded file)?

Any ideas are greatly appreciated,

Andreas
_______________________________________________
gs-devel mailing list
gs-devel <at> ghostscript.com
http://ghostscript.com/cgi-bin/mailman/listinfo/gs-devel
16 Mar 09:34 2016

Re: Fwd: Extra Blank page being printed

At 07:58 16/03/2016 +0000, Ken Sharp wrote:

>The system converts PDFs to PostScript which are concatenated and then
>printed. An extra "image" is printing after the fourth "page", making the
>duplex printing out of sequence. Can anyone suggest why? This question is
>a desperation move...

Firstly this is not a forum for support but for programming questions
relating to developing software which interfaces to the Ghostscript internals.

If you think you have uncovered a bug you may open a bug report at
bugs.ghostscript.com don't forget to include an example file, and command
line required to reproduce the problem.

>It prints in Duplex, so if I say "page" here, I mean 2 images, one front
>and one back on a sheet of paper. Usually the back one is blank
>The application generates "User Letters" that are two pages, a Coversheet
>and a "User Document" concatenated together using a Byte copy.

PostScript is a programming language, PostScript files are programs.
Effectively you are concatenating two programs together, do you think this
is likely to work ?

While it will, for some cases, especially simple cases, in general
concatenating PostScript programs is well known to fail, sometimes
spectacularly. This is not a sensible approach to whatever your problem is.

>The Coversheet is a generic PostScript (mostly static) file created by
>Microsoft Word.
>The User Document is converted from PDF to PostScript with GhostScript.


16 Mar 02:13 2016

Help in using gsapi_set_stdio() to capture stdout into a memory buffer

Hi,

I am trying to learn how to capture the raster conversion of a PS file
into memory but it's not being easy.
The following example (adapted from one posted here before) correctly
prints in stdout a png version of the small PS embedded in code. I know
it's correct because I save it into a file I see it is. But my goal is to
save it in a memory buffer so, as an intermediate step, I wanted to save
it in file via gsapi_set_stdio.

If I compile it as is than I get this warning that I don't understand

cl gstest.c -Ighostpdl\psi -Ighostpdl\base ghostpdl\debugbin\gsdll64.lib
/nologo
gstest.c
gstest.c(102) : warning C4047: 'function' : 'int (__cdecl *)(void *,const
char *,int)' differs in levels of indirection from 'int'
gstest.c(102) : warning C4024: 'gsapi_set_stdio' : different types for
formal and actual parameter 3

but It saves the PS test string in the "CRAP.txt" file. But it's not this
that I want. What I want is to capture what is actually printed to stdout
(because I choose to do "-sOutputFile=-") and have no idea on how to do it.
If gsapi_set_stdio() allows redirecting stdout, why is the result still
printed to stdout?

Thanks for any help

Joaquim
Attachment (gstest.c): application/octet-stream, 3584 bytes

15 Mar 20:59 2016

Extra Blank page being printed

The system converts PDFs to PostScript which are concatenated and then printed. An extra "image" is printing after the fourth "page", making the duplex printing out of sequence. Can anyone suggest why? This question is a desperation move...

Details:

It prints in Duplex, so if I say "page" here, I mean 2 images, one front and one back on a sheet of paper. Usually the back one is blank
The application generates "User Letters" that are two pages, a Coversheet and a "User Document" concatenated together using a Byte copy.
The Coversheet is a generic PostScript (mostly static) file created by Microsoft Word.
The User Document is converted from PDF to PostScript with GhostScript.
%%Creator: GPL Ghostscript GIT PRERELEASE 908 (ps2write)

It has a duplex command inserted thus above the BeginProlog statement.:
<< /Duplex true >> setpagedevice
%%BeginProlog

Before printing, 100 PostScript documents are concatenated, then printed. That means 50 User Letters composed of  a Coversheet and a User Document.

After the second letter (that is after the second User Document) a blank image seems to be inserted. So on the first page that should be the Coversheet, is a blank image and the Coversheet text is printed on the back. Then there is a blank page before the User Document is printed normally again. That blank page probably represents the blank image that should be the back of the CoverSheet

The image seems to be added following every User Document after the Second one. THe blank "image" seems to be inserted before the fifth page.

The GhostScript created PostScript says it is a 2 Page Document - %%Pages: 2
The page structure looks correct for two pages. The second page ends with %%EOF before the next document starts with %!PS-Adobe-3.0 Nothing seems to be inserted between them.

If converted to PDF from PostScript, the User Letter is always 2 pages. There is no blank image.

If 10 Coversheets or 10 User Documents are concatenated together and printed, it does not happen.  There is no blank image.

I have tried many other variations on it.

... Maybe it is the printer...  Thank you for any suggestions, Michael

_______________________________________________
gs-devel mailing list
gs-devel <at> ghostscript.com
http://ghostscript.com/cgi-bin/mailman/listinfo/gs-devel
14 Mar 12:59 2016

Ghostrscript/GhostPDL 9.19 Release Candidate 1

I have created archives (and Ghostscript Windows installers) for the
first release candidates for Ghostscript and GhostPDL 9.19, and they are
available here:

Please give them a try on your system if you're interested in helping
test the release-in-progress. Your feedback is appreciated.

All the best,

Chris


Gmane