On 2014-08-27 18:49, maxwell wrote:
On 2014-08-27 18:16, Jonathan Kew wrote:
I'm curious why Ghostscript is being run at all. Is it trying to
convert a PostScript or EPS graphic, when you intended to use a PDF
directly? Maybe one of the users has a different version of the
graphics package, or e
On 2014-08-27 18:16, Jonathan Kew wrote:
I'm curious why Ghostscript is being run at all. Is it trying to
convert a PostScript or EPS graphic, when you intended to use a PDF
directly? Maybe one of the users has a different version of the
graphics package, or even just a configuration file, in a p
In the past I experimented with postscript. I used to write PS code
directly in my text editor and interpret it by ghostscript so I know
how the error messages look like.
2014-08-28 0:16 GMT+02:00 maxwell :
> On 2014-08-27 17:51, Ross Moore wrote:
>>
>> The problem looks to be with Ghostscript.
>>
On 27/8/14 22:51, Ross Moore wrote:
Hi Mike,
On 28/08/2014, at 7:27 AM, maxwell wrote:
One of our people is getting a crash in xetex, which I can't reproduce. It's
very odd, since afaik we're both using the same input files, the same instance
of xetex, the same TeXLive 2014 files, and so fo
On 2014-08-27 17:51, Ross Moore wrote:
The problem looks to be with Ghostscript.
You may be using different versions, so check that first.
Thanks! (and to Zdenek for the similar suggestion)
That certainly makes sense. We do have two versions of ghostscript on
our linux machine, 8.70 and 9.06
The problem is that unlike TeX, postscript error messages show the
contents of the stack but not the operator that triggered the error
message. You can see that the top of the stac contains font related
objects. The font itself is a dictionary (--dict--) and it contains
other dictionaries. /rangech
Hi Mike,
On 28/08/2014, at 7:27 AM, maxwell wrote:
> One of our people is getting a crash in xetex, which I can't reproduce. It's
> very odd, since afaik we're both using the same input files, the same
> instance of xetex, the same TeXLive 2014 files, and so forth, and running on
> the same m
It may be so, it looks like a postscript error message and run is a
postscript operator that executes a file contents.
2014-08-27 23:27 GMT+02:00 maxwell :
> One of our people is getting a crash in xetex, which I can't reproduce.
> It's very odd, since afaik we're both using the same input files,
One of our people is getting a crash in xetex, which I can't reproduce.
It's very odd, since afaik we're both using the same input files, the
same instance of xetex, the same TeXLive 2014 files, and so forth, and
running on the same machine. Clearly s.t. is different, but I'm not
sure what, a
