Is anyone still using ghostscript?  I have a build of 9.02 I'd like to 
have a couple of folks try out.  I am also wondering if anyone still 
wants this done as a PCSI kit or if a simple ZIP of the necessary files 
(which are fewer in number than they were before) is sufficient.

Here is the output of -h showing current capability:

GPL Ghostscript 9.02 (2011-03-30)
Copyright (C) 2010 Artifex Software, Inc.  All rights reserved.
Usage: gs [switches] [file1.ps file2.ps ...]
Most frequently used switches: (you can use # in place of =)
  -dNOPAUSE           no pause after page | -q  `quiet', fewer messages
  -g<width>x<height>  page size in pixels | -r<res> pixels/inch resolution
  -sDEVICE=<devname>  select device       | -dBATCH  exit after last file
  -sOutputFile=<file> select output file: - for stdout, |command for pipe,
                                          embed %d or %ld for page #
Input formats: PostScript PostScriptLevel1 PostScriptLevel2 
PostScriptLevel3 PDF
Default output device: x11
Available devices:
    alc1900 alc2000 alc4000 alc4100 alc8500 alc8600 alc9100 bbox bit bitcmyk
    bitrgb bj10e bj200 bjc600 bjc800 bjc880j bjccmyk bjccolor bjcgray 
bjcmono
    bmp16 bmp16m bmp256 bmp32b bmpgray bmpmono bmpsep1 bmpsep8 cdeskjet
    cdj1600 cdj550 cdj670 cdj850 cdj880 cdj890 cdj970 cdjcolor cdjmono
    cdnj500 chp2200 cljet5 cljet5c deskjet devicen djet500 dl2100 epl2050
    epl2050p epl2120 epl2500 epl2750 epl5800 epl5900 epl6100 epl6200 
eplcolor
    eplmono eps9high eps9mid epson epsonc epswrite faxg3 faxg32d faxg4 gdi
    hl1240 hl1250 hpdj1120c hpdj310 hpdj320 hpdj340 hpdj400 hpdj500 hpdj500c
    hpdj510 hpdj520 hpdj540 hpdj550c hpdj560c hpdj600 hpdj660c hpdj670c
    hpdj680c hpdj690c hpdj850c hpdj855c hpdj870c hpdj890c hpdjplus
    hpdjportable ibmpro jpeg jpegcmyk jpeggray la50 la70 la75 la75plus
    laserjet lex2050 lex3200 lex5700 lex7000 lips2p lips4 lips4v lj5gray
    lj5mono ljet2p ljet3 ljet3d ljet4 ljet4d ljetplus ln03 lp1800 lp1900
    lp2200 lp2400 lp2500 lp3000c lp7500 lp7700 lp7900 lp8000c lp8100 lp8200c
    lp8300c lp8300f lp8400f lp8500c lp8600 lp8600f lp8700 lp8800c lp8900
    lp9000b lp9000c lp9100 lp9200b lp9200c lp9300 lp9400 lp9500c lp9600
    lp9600s lp9800c lps4500 lps6500 lx5000 lxm3200 md2k md5k nullpage oki4w
    omni oprp opvp pamcmyk32 pamcmyk4 pbm pbmraw pcl3 pcx16 pcx24b pcx256
    pcxcmyk pcxgray pcxmono pdfwrite pgm pgmraw pgnm pgnmraw pj pjxl pjxl300
    pkm pkmraw pksm pksmraw png16 png16m png256 pngalpha pnggray pngmono pnm
    pnmraw ppm ppmraw ps2write psdcmyk psdrgb psgray psmono psrgb pswrite
    pxlcolor pxlmono samsunggdi spotcmyk stcolor tiff12nc tiff24nc tiff32nc
    tiff48nc tiff64nc tiffcrle tiffg3 tiffg32d tiffg4 tiffgray tifflzw
    tiffpack tiffscaled tiffsep tiffsep1 txtwrite uniprint x11 x11alpha
    x11cmyk x11gray2 x11gray4 x11mono xcf xes
Search path:
    %rom%Resource/Init/ , %rom%lib/ , GS_LIB
Initialization files are compiled into the executable.
For more information, see GS_DOC:Use.htm.
Please report bugs to bugs.ghostscript.com.

Mark Berryman

--- Posted via news://freenews.netfront.net/ - Complaints to news@netfront.net ---

In article <iusrlv$27t6$1@adenine.netfront.net>, Mark Berryman <mark@theberrymans.com> writes:
>Is anyone still using ghostscript?  I have a build of 9.02 I'd like to 
>have a couple of folks try out.  I am also wondering if anyone still 
>wants this done as a PCSI kit or if a simple ZIP of the necessary files 
>(which are fewer in number than they were before) is sufficient.

I use it ever since display postscript was yanked out from DECWindows and
I have a client that uses it to convert PS forms to PDF for emailingtheir
customers.

A PCSI kit would be nice but don't sweat it if you can't see fit to do it.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.

On 4-7-2011 19:01, Mark Berryman wrote:
> Is anyone still using ghostscript? I have a build of 9.02 I'd like to
> have a couple of folks try out. I am also wondering if anyone still
> wants this done as a PCSI kit or if a simple ZIP of the necessary files
> (which are fewer in number than they were before) is sufficient.

Yes, I still use it.  That's great, by the way, good work (also on PHP,
which you announced recently, although I unfortunately haven't had the
chance to try it yet).

As for the delivery, PCSI kit or ZIP file: It shouldn't have to matter
for me.  Maybe both?  (I tend to download ZIP files, to try things out
quickly.)

  - MG

On 07/04/2011 10:01 AM, Mark Berryman wrote:
> Is anyone still using ghostscript? I have a build of 9.02 I'd like to
> have a couple of folks try out. I am also wondering if anyone still
> wants this done as a PCSI kit or if a simple ZIP of the necessary files
> (which are fewer in number than they were before) is sufficient.
>
--

I would be very happy to test a new version of Ghostscript. The latest 
that I have gotten to build is 8.51. Either a ZIP or PCSI kit would be 
great.

Jeff Coffield
www.digitalsynergyinc.com

In article <iusrlv$27t6$1@adenine.netfront.net>, Mark Berryman
<mark@theberrymans.com> writes: 

> Is anyone still using ghostscript?  

Yes.  And GV.  IIRC, GV uses GS or something like that.

> I have a build of 9.02 I'd like to 
> have a couple of folks try out.  

Yes, please.  Contact me via email.

> I am also wondering if anyone still 
> wants this done as a PCSI kit or if a simple ZIP of the necessary files 
> (which are fewer in number than they were before) is sufficient.

I tend to prefer to distinguish between DEC stuff (OS, layered products 
and similar stuff like Rdb) (PCSI or VMSINSTAL, goes to the system disk) 
and third-party products (ZIP, OSU web server, LaTeX etc) (ZIP archive, 
unpack it, read the README, build it---I put this on a non-system disk 
dedicated to such software).  The reason is that I like to have more 
transparency and control over stuff which is not closely tied to the OS; 
it also keeps the system disk small.

A couple of months ago, I used my very old version quite a bit:

   Aladdin Ghostscript 4.03 (1996-9-23)

   "X11_ROOT" = "DSA520:[GHOST.GHOSTVIEW343.]" (LNM$PROCESS_TABLE)

I hadn't used it in a long time and was surprised to find that it had 
problems finding fonts, whereas it definitely worked in the past (with 
the same program generating the PostScript---a Fortran program unchanged 
since the mid-1990s).  I resorted to bitmapping the output (on another 
machine) and could then view the files locally (the original files 
printed fine on a PostScript printer (from HP, as it happens)).

Considering the antiquity of my present version and the fact that it 
doesn't work anyway, it's probably better to start over from scratch.

(I must admit that I have never understood what actually goes on under
the hood involving font selection etc, which fonts I have to install
where, if and if so how font substitution happens if a font is missing
etc.) 

I like the packaging which SMS uses for ZIP, UNZIP, WGET etc.

I have 7.3-2 but hope to upgrade to 8.3 within the next couple of
months.  Generally, I like compiling and linking, rather than going with 
pre-built executables, but the latter are OK (especially if they work 
out of the box).

Compaq C V6.2-008 on OpenVMS Alpha V7.3-2

Now that I no longer have patch access (even though I am willing to pay 
a reasonable fee for it), I am a bit hesitant about upgrading software 
and also don't want to maintain multiple versions of stuff to fall back 
on.  So, if your kit will build with what I have, so much the better, 
but I'm happy to test pre-built stuff providing that it works (which 
presumably means built on 7.3-2 or earlier).

Of all the things I need to upgrade, this is the most urgent (since I 
haven't upgraded it for longer than for most other packages and also 
since a lot has changed in the meantime).  I actually plan to be doing a 
lot of stuff with PostScript and PDF in the near future, generated from 
a variety of sources, and am willing to test things quite extensively, 
hoping any bugs will be fixed.  :-)

In article <iutd30$4kg$1@online.de>, helbig@astro.multiCLOTHESvax.de
(Phillip Helbig---undress to reply) writes: 

> I hadn't used it in a long time and was surprised to find that it had 
> problems finding fonts, whereas it definitely worked in the past (with 
> the same program generating the PostScript---a Fortran program unchanged 
> since the mid-1990s).  I resorted to bitmapping the output (on another 
> machine) and could then view the files locally (the original files 
> printed fine on a PostScript printer (from HP, as it happens)).
> 
> Considering the antiquity of my present version and the fact that it 
> doesn't work anyway, it's probably better to start over from scratch.
> 
> (I must admit that I have never understood what actually goes on under
> the hood involving font selection etc, which fonts I have to install
> where, if and if so how font substitution happens if a font is missing
> etc.) 

Could this problem be related to the disappearance of Display PostScript 
with 7.2 or whenever it was?

On 7/4/2011 1:01 PM, Mark Berryman wrote:
> Is anyone still using ghostscript? I have a build of 9.02 I'd like to
> have a couple of folks try out. I am also wondering if anyone still
> wants this done as a PCSI kit or if a simple ZIP of the necessary files
> (which are fewer in number than they were before) is sufficient.

I have not used GV/GS for years.

In general I think the preference should be:
* simple apps => distribute a ZIP where people can @link or @build
* stuff that really need to be installed => PCSI

(I believe GS is in the first category)

Arne

On 4 jul, 19:01, Mark Berryman <m...@theberrymans.com> wrote:
> Is anyone still using ghostscript? =A0I have a build of 9.02 I'd like to
> have a couple of folks try out. =A0I am also wondering if anyone still
> wants this done as a PCSI kit or if a simple ZIP of the necessary files
> (which are fewer in number than they were before) is sufficient.
>
> Here is the output of -h showing current capability:
>
> GPL Ghostscript 9.02 (2011-03-30)
> Copyright (C) 2010 Artifex Software, Inc. =A0All rights reserved.
> Usage: gs [switches] [file1.ps file2.ps ...]
> Most frequently used switches: (you can use # in place of =3D)
> =A0 -dNOPAUSE =A0 =A0 =A0 =A0 =A0 no pause after page | -q =A0`quiet', fe=
wer messages
> =A0 -g<width>x<height> =A0page size in pixels | -r<res> pixels/inch resol=
ution
> =A0 -sDEVICE=3D<devname> =A0select device =A0 =A0 =A0 | -dBATCH =A0exit a=
fter last file
> =A0 -sOutputFile=3D<file> select output file: - for stdout, |command for =
pipe,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 embed %d or %ld for page #
> Input formats: PostScript PostScriptLevel1 PostScriptLevel2
> PostScriptLevel3 PDF
> Default output device: x11
> Available devices:
> =A0 =A0 alc1900 alc2000 alc4000 alc4100 alc8500 alc8600 alc9100 bbox bit =
bitcmyk
> =A0 =A0 bitrgb bj10e bj200 bjc600 bjc800 bjc880j bjccmyk bjccolor bjcgray
> bjcmono
> =A0 =A0 bmp16 bmp16m bmp256 bmp32b bmpgray bmpmono bmpsep1 bmpsep8 cdeskj=
et
> =A0 =A0 cdj1600 cdj550 cdj670 cdj850 cdj880 cdj890 cdj970 cdjcolor cdjmon=
o
> =A0 =A0 cdnj500 chp2200 cljet5 cljet5c deskjet devicen djet500 dl2100 epl=
2050
> =A0 =A0 epl2050p epl2120 epl2500 epl2750 epl5800 epl5900 epl6100 epl6200
> eplcolor
> =A0 =A0 eplmono eps9high eps9mid epson epsonc epswrite faxg3 faxg32d faxg=
4 gdi
> =A0 =A0 hl1240 hl1250 hpdj1120c hpdj310 hpdj320 hpdj340 hpdj400 hpdj500 h=
pdj500c
> =A0 =A0 hpdj510 hpdj520 hpdj540 hpdj550c hpdj560c hpdj600 hpdj660c hpdj67=
0c
> =A0 =A0 hpdj680c hpdj690c hpdj850c hpdj855c hpdj870c hpdj890c hpdjplus
> =A0 =A0 hpdjportable ibmpro jpeg jpegcmyk jpeggray la50 la70 la75 la75plu=
s
> =A0 =A0 laserjet lex2050 lex3200 lex5700 lex7000 lips2p lips4 lips4v lj5g=
ray
> =A0 =A0 lj5mono ljet2p ljet3 ljet3d ljet4 ljet4d ljetplus ln03 lp1800 lp1=
900
> =A0 =A0 lp2200 lp2400 lp2500 lp3000c lp7500 lp7700 lp7900 lp8000c lp8100 =
lp8200c
> =A0 =A0 lp8300c lp8300f lp8400f lp8500c lp8600 lp8600f lp8700 lp8800c lp8=
900
> =A0 =A0 lp9000b lp9000c lp9100 lp9200b lp9200c lp9300 lp9400 lp9500c lp96=
00
> =A0 =A0 lp9600s lp9800c lps4500 lps6500 lx5000 lxm3200 md2k md5k nullpage=
 oki4w
> =A0 =A0 omni oprp opvp pamcmyk32 pamcmyk4 pbm pbmraw pcl3 pcx16 pcx24b pc=
x256
> =A0 =A0 pcxcmyk pcxgray pcxmono pdfwrite pgm pgmraw pgnm pgnmraw pj pjxl =
pjxl300
> =A0 =A0 pkm pkmraw pksm pksmraw png16 png16m png256 pngalpha pnggray pngm=
ono pnm
> =A0 =A0 pnmraw ppm ppmraw ps2write psdcmyk psdrgb psgray psmono psrgb psw=
rite
> =A0 =A0 pxlcolor pxlmono samsunggdi spotcmyk stcolor tiff12nc tiff24nc ti=
ff32nc
> =A0 =A0 tiff48nc tiff64nc tiffcrle tiffg3 tiffg32d tiffg4 tiffgray tifflz=
w
> =A0 =A0 tiffpack tiffscaled tiffsep tiffsep1 txtwrite uniprint x11 x11alp=
ha
> =A0 =A0 x11cmyk x11gray2 x11gray4 x11mono xcf xes
> Search path:
> =A0 =A0 %rom%Resource/Init/ , %rom%lib/ , GS_LIB
> Initialization files are compiled into the executable.
> For more information, see GS_DOC:Use.htm.
> Please report bugs to bugs.ghostscript.com.
>
> Mark Berryman
>
> --- Posted via news://freenews.netfront.net/ - Complaints to n...@netfron=
t.net ---

Yes, Ghostscript is still in use at my place. Lots of documentation
was available in that format.
I'd prefer a .ZIP file. A PCSI kit is fine when files must be copied
in predefined directories.
Hans

In article <iusrlv$27t6$1@adenine.netfront.net>, Mark Berryman <mark@theberrymans.com> writes:
>Is anyone still using ghostscript?

Yes, from time to time it is quite handy.

>I am also wondering if anyone still wants this done as a PCSI kit or if a
>simple ZIP of the necessary files (which are fewer in number than they were
>before) is sufficient.

PCSI is easier to use. But a ZIP archive would be ok as well.

Regards,
   Christoph Gartmann

-- 
 Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -80464
 Immunbiologie und Epigenetik
 Postfach 1169                 Internet: gartmann@immunbio dot mpg dot de
 D-79011  Freiburg, Germany
               http://www.immunbio.mpg.de/home/menue.html

On Jul 5, 2:57=A0am, gartm...@nonsense.immunbio.mpg.de (Christoph
Gartmann) wrote:
> In article <iusrlv$27t...@adenine.netfront.net>, Mark Berryman <m...@theb=
errymans.com> writes:
> >Is anyone still using ghostscript?
>
> Yes, from time to time it is quite handy.
>
> >I am also wondering if anyone still wants this done as a PCSI kit or if =
a
> >simple ZIP of the necessary files (which are fewer in number than they w=
ere
> >before) is sufficient.
>
> PCSI is easier to use. But a ZIP archive would be ok as well.
>
> Regards,
> =A0 =A0Christoph Gartmann
>
> --
> =A0Max-Planck-Institut fuer =A0 =A0 =A0Phone =A0 : +49-761-5108-464 =A0 F=
ax: -80464
> =A0Immunbiologie und Epigenetik
> =A0Postfach 1169 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Internet: gartmann@immun=
bio dot mpg dot de
> =A0D-79011 =A0Freiburg, Germany
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0http://www.immunbio.mpg.de/home/menue.html

Mark,

Yes, we use GhostScript here at the company I work at for manipulation
of PostScript and PDF files. For version 6.5, I just downloaded the
zip file and built from the sources. I remember the build being very
simple. So, if building the PCSI kit cuts into you valuable time, I
wouldn't worry about it and just provide the zip file. I would be
happy to be a guinea pig for GhostScript V9.02 for OpenVMS. Thanks for
your efforts to actively maintain it for OpenVMS!

Eric

On 7/4/11 11:01 AM, Mark Berryman wrote:
> Is anyone still using ghostscript?  I have a build of 9.02 I'd like to
> have a couple of folks try out. I am also wondering if anyone still
> wants this done as a PCSI kit or if a simple ZIP of the necessary files
> (which are fewer in number than they were before) is sufficient.
>
 > [snip]

Ok.  I need to put together an actual download page on my web server 
but, for now, a copy of this distribution can be found from the same 
place where I make my PHP kits available.  You can download this file at 
http://www.theberrymans.com/php_kits/ghostscript_9_2.zip

Note that this is not a source kit.  It simply contains everything you 
need to run Ghostscript on VMS.

Comments regarding the build or the distribution kit are welcome and 
appreciated.

Mark Berryman

--- Posted via news://freenews.netfront.net/ - Complaints to news@netfront.net ---

Phillip Helbig---undress to reply wrote:
> In article <iutd30$4kg$1@online.de>, helbig@astro.multiCLOTHESvax.de
> (Phillip Helbig---undress to reply) writes: 
> 
>> I hadn't used it in a long time and was surprised to find that it had 
>> problems finding fonts, whereas it definitely worked in the past (with 
>> the same program generating the PostScript---a Fortran program unchanged 
>> since the mid-1990s).  I resorted to bitmapping the output (on another 
>> machine) and could then view the files locally (the original files 
>> printed fine on a PostScript printer (from HP, as it happens)).
>>
>> Considering the antiquity of my present version and the fact that it 
>> doesn't work anyway, it's probably better to start over from scratch.
>>
>> (I must admit that I have never understood what actually goes on under
>> the hood involving font selection etc, which fonts I have to install
>> where, if and if so how font substitution happens if a font is missing
>> etc.) 
> 
> Could this problem be related to the disappearance of Display PostScript 
> with 7.2 or whenever it was?

Yes.

By default, GS used the Display Postscript fonts.

There is a FONTMAP option that allows you to instruct GS to use 
different fonts.  Unfortunately, I don't remember how it works just now.

-- 
-----------------------------------------------------------------------
Chris Scheers, Applied Synergy, Inc.

Voice: 817-237-3360            Internet: chris@applied-synergy.com
   Fax: 817-237-3074

Mark Berryman wrote:
> On 7/4/11 11:01 AM, Mark Berryman wrote:
>> Is anyone still using ghostscript?  I have a build of 9.02 I'd like to
>> have a couple of folks try out. I am also wondering if anyone still
>> wants this done as a PCSI kit or if a simple ZIP of the necessary files
>> (which are fewer in number than they were before) is sufficient.
>>
>  > [snip]
> 
> Ok.  I need to put together an actual download page on my web server 
> but, for now, a copy of this distribution can be found from the same 
> place where I make my PHP kits available.  You can download this file at 
> http://www.theberrymans.com/php_kits/ghostscript_9_2.zip
> 
> Note that this is not a source kit.  It simply contains everything you 
> need to run Ghostscript on VMS.
> 
> Comments regarding the build or the distribution kit are welcome and 
> appreciated.
> 
> Mark Berryman
> 
> --- Posted via news://freenews.netfront.net/ - Complaints to 
> news@netfront.net ---
Thanks Mark
   I'll try it.

   Good to have a recent ghostview again (I had a few tries myself, but 
got stuck into a crash in one of the .ps files, not having enough 
PostScript knowledge and time to debug the problem)

            Jouk

In article <4E136A42.6090000@applied-synergy.com>, Chris Scheers
<chris@applied-synergy.com> writes: 

> >> (I must admit that I have never understood what actually goes on under
> >> the hood involving font selection etc, which fonts I have to install
> >> where, if and if so how font substitution happens if a font is missing
> >> etc.) 
> > 
> > Could this problem be related to the disappearance of Display PostScript 
> > with 7.2 or whenever it was?
> 
> Yes.
> 
> By default, GS used the Display Postscript fonts.
> 
> There is a FONTMAP option that allows you to instruct GS to use 
> different fonts.  Unfortunately, I don't remember how it works just now.

In that case, do I need to get them from somewhere, or does GS have its 
own fonts?  It's really a pain when package A requires package B, which 
in turn requires package C etc.

Mark Berryman wrote:
> On 7/4/11 11:01 AM, Mark Berryman wrote:
>> Is anyone still using ghostscript?  I have a build of 9.02 I'd like to
>> have a couple of folks try out. I am also wondering if anyone still
>> wants this done as a PCSI kit or if a simple ZIP of the necessary files
>> (which are fewer in number than they were before) is sufficient.
>>
>  > [snip]
> 
> Ok.  I need to put together an actual download page on my web server 
> but, for now, a copy of this distribution can be found from the same 
> place where I make my PHP kits available.  You can download this file at 
> http://www.theberrymans.com/php_kits/ghostscript_9_2.zip
> 
> Note that this is not a source kit.  It simply contains everything you 
> need to run Ghostscript on VMS.
> 
> Comments regarding the build or the distribution kit are welcome and 
> appreciated.
> 
> Mark Berryman
> 
> --- Posted via news://freenews.netfront.net/ - Complaints to 
> news@netfront.net ---
Tested and it worked. Still I had to set the gs symbol (i.e. needed by 
GhostView) manually. It would be handy if this was done by setup.com
Thanks for the porting effort.

Mark, are you planning to make also a source-code distribution, or (even 
better) merge your changes into the "official" ghostscript 
distributions? My experience in the past was that the ghostscript 
developers were willing to include the changes for OpenVMS.

               Jouk

On 7/7/11 2:28 AM, JOUKJ wrote:
> Mark Berryman wrote:
>> On 7/4/11 11:01 AM, Mark Berryman wrote:
>>> Is anyone still using ghostscript? I have a build of 9.02 I'd like to
>>> have a couple of folks try out. I am also wondering if anyone still
>>> wants this done as a PCSI kit or if a simple ZIP of the necessary files
>>> (which are fewer in number than they were before) is sufficient.
>>>
>> > [snip]
>>
>> Ok. I need to put together an actual download page on my web server
>> but, for now, a copy of this distribution can be found from the same
>> place where I make my PHP kits available. You can download this file
>> at http://www.theberrymans.com/php_kits/ghostscript_9_2.zip
>>
>> Note that this is not a source kit. It simply contains everything you
>> need to run Ghostscript on VMS.
>>
>> Comments regarding the build or the distribution kit are welcome and
>> appreciated.
>>
>> Mark Berryman
>>
>> --- Posted via news://freenews.netfront.net/ - Complaints to
>> news@netfront.net ---
> Tested and it worked. Still I had to set the gs symbol (i.e. needed by
> GhostView) manually. It would be handy if this was done by setup.com
> Thanks for the porting effort.

Do you have a version of GhostView that works with this version of 
Ghostscript?  The one I could find, GV v3.5.8, does not work at all, 
either with the current GhostScript (it can't give GS a simple file 
name) or with VMS V8.4 (the file selection window does not paint 
anything until you mouse over where the files are supposed to be listed).

> Mark, are you planning to make also a source-code distribution, or (even
> better) merge your changes into the "official" ghostscript
> distributions? My experience in the past was that the ghostscript
> developers were willing to include the changes for OpenVMS.

I'll be including a backup save set of the source code when I release 
the PCSI kit.  The code changes would probably be easy enough to get 
into the official release.  However, I had to make several changes to 
the .mak files, in some cases completely rewriting them.  The changes 
are not compatible with the Unix versions.

For example, all of the .mak files use $(D) as the path separator, 
defined as / for unix and \ windows and it is null for VMS.  That is 
because you cannot simply concatenate things together to build a path on 
VMS.  As long as the reference in question is simply $(DIR)$(D)filename, 
this is not a problem.  However, when the reference needs to go more 
than one level deep, i.e. $(DIR1)$(D)$(DIR2)$(D)$(DIR3)($D)filename, 
everything breaks.  There are a number of such instances in the build 
files.  I simply edited them for VMS when doing the build.  We'd need to 
come up with a way to fix the issue that doesn't break the build file 
for other platforms in order to submit it.

Mark Berryman

--- Posted via news://freenews.netfront.net/ - Complaints to news@netfront.net ---

Mark Berryman wrote:

[snip]
> 
> Do you have a version of GhostView that works with this version of 
> Ghostscript?  The one I could find, GV v3.5.8, does not work at all, 
> either with the current GhostScript (it can't give GS a simple file 
> name) or with VMS V8.4 (the file selection window does not paint 
> anything until you mouse over where the files are supposed to be listed).

Seems I have the same version (I only have Alpha machines). It is "old" 
and I compiled it more than 10 years ago. I'm running VMS v8.4 and when 
I select "open" the file dialog seems to be normal to me.
Also "gv file.ps" works. Be sure that the symbol gs is defined as the 
command to run ghostscript.

If you are interested I can zip-up the directory containing Ghostview 
and put it on my web-site.

[snip]

> I'll be including a backup save set of the source code when I release 
> the PCSI kit.  The code changes would probably be easy enough to get 
Thanks, please keep me informed.

> into the official release.  However, I had to make several changes to 
> the .mak files, in some cases completely rewriting them.  The changes 
> are not compatible with the Unix versions.
> 
> For example, all of the .mak files use $(D) as the path separator, 
> defined as / for unix and \ windows and it is null for VMS.  That is 
> because you cannot simply concatenate things together to build a path on 
> VMS.  As long as the reference in question is simply $(DIR)$(D)filename, 
> this is not a problem.  However, when the reference needs to go more 
> than one level deep, i.e. $(DIR1)$(D)$(DIR2)$(D)$(DIR3)($D)filename, 
> everything breaks.  There are a number of such instances in the build 
> files.  I simply edited them for VMS when doing the build.  We'd need to 
> come up with a way to fix the issue that doesn't break the build file 
> for other platforms in order to submit it.
> 
I know. In the past I made several changes to them. I would have 
preferred "separate" makefile for OpenVMS, but this was the way the 
GhostScript developers liked it.
The problem of $(D) should be solved in the same way as some other 
macros i.e.  $(I_) and $(_I) which were introduced for the specific 
naming in OpenVMS. So $(D) should be split into 2 or three macros 
depending it is the first, middle of end occurrence (i.e. $(_D) $(D) and 
$(D_)), which are different for OpenVMS but the same for other OS's.


                     Jouk

On Jul 5, 2:00=A0pm, Mark Berryman <m...@theberrymans.com> wrote:
> On 7/4/11 11:01 AM, Mark Berryman wrote:> Is anyone still using ghostscri=
pt? =A0I have a build of 9.02 I'd like to
> > have a couple of folks try out. I am also wondering if anyone still
> > wants this done as a PCSI kit or if a simple ZIP of the necessary files
> > (which are fewer in number than they were before) is sufficient.
>
> =A0> [snip]
>
> Ok. =A0I need to put together an actual download page on my web server
> but, for now, a copy of this distribution can be found from the same
> place where I make my PHP kits available. =A0You can download this file a=
thttp://www.theberrymans.com/php_kits/ghostscript_9_2.zip
>
> Note that this is not a source kit. =A0It simply contains everything you
> need to run Ghostscript on VMS.
>
> Comments regarding the build or the distribution kit are welcome and
> appreciated.
>
> Mark Berryman
>
> --- Posted via news://freenews.netfront.net/ - Complaints to n...@netfron=
t.net ---

Hi Mark.  A few weeks ago I posted in ITRC asking whether anyone was
working on this.   I didn't get a response so I started doing it.  I
meant to resubmit the sources back to gnu.  I got sidetracked though
because one of my co-workers went on extended medical leave and I had
to pick up his work.  Thanks for doing this, but I think it would be
great to update the sources and resubmit as they've been talking about
dropping support for OpenVMS.

On 7/13/11 7:29 AM, Edgar wrote:
> On Jul 5, 2:00 pm, Mark Berryman<m...@theberrymans.com>  wrote:
>> On 7/4/11 11:01 AM, Mark Berryman wrote:>  Is anyone still using ghostscript?  I have a build of 9.02 I'd like to
>>> have a couple of folks try out. I am also wondering if anyone still
>>> wants this done as a PCSI kit or if a simple ZIP of the necessary files
>>> (which are fewer in number than they were before) is sufficient.
>>
>>   >  [snip]
>>
>> Ok.  I need to put together an actual download page on my web server
>> but, for now, a copy of this distribution can be found from the same
>> place where I make my PHP kits available.  You can download this file athttp://www.theberrymans.com/php_kits/ghostscript_9_2.zip
>>
>> Note that this is not a source kit.  It simply contains everything you
>> need to run Ghostscript on VMS.
>>
>> Comments regarding the build or the distribution kit are welcome and
>> appreciated.
>>
>> Mark Berryman
>>
>> --- Posted via news://freenews.netfront.net/ - Complaints to n...@netfront.net ---
>
> Hi Mark.  A few weeks ago I posted in ITRC asking whether anyone was
> working on this.   I didn't get a response so I started doing it.  I
> meant to resubmit the sources back to gnu.  I got sidetracked though
> because one of my co-workers went on extended medical leave and I had
> to pick up his work.  Thanks for doing this, but I think it would be
> great to update the sources and resubmit as they've been talking about
> dropping support for OpenVMS.

No problem.  If you or Jouk wants to contact me offline, we can see what 
it would take to get the changes submitted.  All told, I made changes to 
less than 20 files to get this to work.

Mark Berryman

--- Posted via news://freenews.netfront.net/ - Complaints to news@netfront.net ---

On 5/07/11 2:31 AM, Mark Berryman wrote:
> Is anyone still using ghostscript? I have a build of 9.02 I'd like to
> have a couple of folks try out. I am also wondering if anyone still
> wants this done as a PCSI kit or if a simple ZIP of the necessary files
> (which are fewer in number than they were before) is sufficient.

WASD uses Ghostscript to convert DECdocument PostScript output to the 
PDF documentation included in the distribution.  Just tried the new kits 
and all looks OK.  Thanks Mark.

$ cc /ver
HP C V7.3-009 on OpenVMS Alpha V8.3
$ gs -v
GPL Ghostscript 9.02 (2011-03-30)
Copyright (C) 2010 Artifex Software, Inc.  All rights reserved.

> Here is the output of -h showing current capability:
>
> GPL Ghostscript 9.02 (2011-03-30)
> Copyright (C) 2010 Artifex Software, Inc. All rights reserved.
> Usage: gs [switches] [file1.ps file2.ps ...]
> Most frequently used switches: (you can use # in place of =)
> -dNOPAUSE no pause after page | -q `quiet', fewer messages
> -g<width>x<height> page size in pixels | -r<res> pixels/inch resolution
> -sDEVICE=<devname> select device | -dBATCH exit after last file
> -sOutputFile=<file> select output file: - for stdout, |command for pipe,
> embed %d or %ld for page #
> Input formats: PostScript PostScriptLevel1 PostScriptLevel2
> PostScriptLevel3 PDF
> Default output device: x11
> Available devices:
> alc1900 alc2000 alc4000 alc4100 alc8500 alc8600 alc9100 bbox bit bitcmyk
> bitrgb bj10e bj200 bjc600 bjc800 bjc880j bjccmyk bjccolor bjcgray bjcmono
> bmp16 bmp16m bmp256 bmp32b bmpgray bmpmono bmpsep1 bmpsep8 cdeskjet
> cdj1600 cdj550 cdj670 cdj850 cdj880 cdj890 cdj970 cdjcolor cdjmono
> cdnj500 chp2200 cljet5 cljet5c deskjet devicen djet500 dl2100 epl2050
> epl2050p epl2120 epl2500 epl2750 epl5800 epl5900 epl6100 epl6200 eplcolor
> eplmono eps9high eps9mid epson epsonc epswrite faxg3 faxg32d faxg4 gdi
> hl1240 hl1250 hpdj1120c hpdj310 hpdj320 hpdj340 hpdj400 hpdj500 hpdj500c
> hpdj510 hpdj520 hpdj540 hpdj550c hpdj560c hpdj600 hpdj660c hpdj670c
> hpdj680c hpdj690c hpdj850c hpdj855c hpdj870c hpdj890c hpdjplus
> hpdjportable ibmpro jpeg jpegcmyk jpeggray la50 la70 la75 la75plus
> laserjet lex2050 lex3200 lex5700 lex7000 lips2p lips4 lips4v lj5gray
> lj5mono ljet2p ljet3 ljet3d ljet4 ljet4d ljetplus ln03 lp1800 lp1900
> lp2200 lp2400 lp2500 lp3000c lp7500 lp7700 lp7900 lp8000c lp8100 lp8200c
> lp8300c lp8300f lp8400f lp8500c lp8600 lp8600f lp8700 lp8800c lp8900
> lp9000b lp9000c lp9100 lp9200b lp9200c lp9300 lp9400 lp9500c lp9600
> lp9600s lp9800c lps4500 lps6500 lx5000 lxm3200 md2k md5k nullpage oki4w
> omni oprp opvp pamcmyk32 pamcmyk4 pbm pbmraw pcl3 pcx16 pcx24b pcx256
> pcxcmyk pcxgray pcxmono pdfwrite pgm pgmraw pgnm pgnmraw pj pjxl pjxl300
> pkm pkmraw pksm pksmraw png16 png16m png256 pngalpha pnggray pngmono pnm
> pnmraw ppm ppmraw ps2write psdcmyk psdrgb psgray psmono psrgb pswrite
> pxlcolor pxlmono samsunggdi spotcmyk stcolor tiff12nc tiff24nc tiff32nc
> tiff48nc tiff64nc tiffcrle tiffg3 tiffg32d tiffg4 tiffgray tifflzw
> tiffpack tiffscaled tiffsep tiffsep1 txtwrite uniprint x11 x11alpha
> x11cmyk x11gray2 x11gray4 x11mono xcf xes
> Search path:
> %rom%Resource/Init/ , %rom%lib/ , GS_LIB
> Initialization files are compiled into the executable.
> For more information, see GS_DOC:Use.htm.
> Please report bugs to bugs.ghostscript.com.
>
> Mark Berryman
>
> --- Posted via news://freenews.netfront.net/ - Complaints to
> news@netfront.net ---