bugs in winedt 7.0 calling ps2pdf

Timm Riesen <[email protected]>
Newsgroups gmane.comp.tex.miktex
Message-ID <[email protected]>
Hi,
First of all, I do understand that is the miktex-user list and and not 
directly winedt related.
However, I hope that some of you might have similar issues and a 
possible work around.

Installation:
Miktext 2.9 on Windows 7 (64bit) with WinEdt 7.0 (gsv50w64 and gsv50w64 
also installed).
Everything is set up with default configurations.
I will describe 2 bugs, of which bug 2 is the real one that I don't 
understand.
Any insight or help would be much appreciated.
I will contact WinEdt about this too, but I've heard that here were the 
real geeks :-)

Cheers,
Timm Riesen


Bug 1
=====

WinEdt: Options -> Execution Modes -> ps2pdf -> paper size and 
orientation: Changing the setting away from "Default" will break calling 
ps2pdf:

------ console output bug 1 
----------------------------------------------------------------------------------------
Command Line:   ps2pdf.exe -sPAPERSIZE=a4 "test.ps"
Startup Folder: C:\Users\riesen\Documents\blah

Unknown paper size: ().
Error: /undefinedfilename in (a4)
Operand stack:

Execution stack:
    %interp_exit   .runexec2   --nostringval--   --nostringval-- 
--nostringval--   2   %stopped_push   --nostringval-- --nostringval--   
--nostringval--   false   1   %stopped_push
Dictionary stack:
    --dict:1157/1684(ro)(G)--   --dict:0/20(G)--   --dict:77/200(L)--
Current allocation mode is local
Last OS error: No such file or directory
MiKTeX GPL Ghostscript  9.00: Unrecoverable error, exit code 1
--------- EOF console output 
-------------------------------------------------------------------------------------

In addition to the abort of the script, the ps file that ps2pdf was 
supposed to act on gets
DESTROYED (Reduced from 29K to 3K in my tests). This part I do not 
understand.

Cause
======
For Windows versions of ps2pdf, the correct syntax would be
-sPAPERSIZE#a4 (instead of -sPAPERSIZE=a4) so WinEdt seems to call 
wrong, but why
the input file gets destroyed might be another issue (maybe even MikTek?).


Succesful test in normal console:
==============================
I then decided to test directly in a cmd console (outside the WinEdt)
ps2pdf.exe -sPAPERSIZE#a4  test.ps test.pdf works perfectly, same for 
other page formats.



Bug 2
=====
(paper size radio button was reset back to "Default" prior to this test)
WinEdt: Options -> Execution Modes -> ps2pdf -> Command Line: Switches

We directly specify
-sPAPERSIZE#a4 as a command line switch within WinEdt.

------ console output bug 2 
--------------------------------------------------------------------------------------
Command Line:   ps2pdf.exe -sPAPERSIZE#a4 "blankform.ps"
Startup Folder: C:\Users\riesen\Documents\blah\

Error: /undefinedfilename in (-sPAPERSIZE#a4)
Operand stack:

Execution stack:
    %interp_exit   .runexec2   --nostringval--   --nostringval-- 
--nostringval--   2   %stopped_push   --nostringval-- --nostringval--   
--nostringval--   false   1   %stopped_push
Dictionary stack:
    --dict:1159/1684(ro)(G)--   --dict:0/20(G)--   --dict:77/200(L)--
Current allocation mode is local
Last OS error: No such file or directory
MiKTeX GPL Ghostscript  9.00: Unrecoverable error, exit code 1
--------- EOF console output 
-------------------------------------------------------------------------------------

Cause
=====
Unknown.  The command that is reported in the first line of the console 
output is sound, i.e. copy-pasting it to an outside
console and running ps2pdf complete with no error.

As in bug 1, the input ps file gets destroyed.
















------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.