ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "luigi scarso" <luigi.scarso@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Flaky pdf file.
Date: Fri, 26 Sep 2008 20:45:14 +0200	[thread overview]
Message-ID: <fe8d59da0809261145xa6ca8a8iab08a4fc8956e824@mail.gmail.com> (raw)
In-Reply-To: <200809261400.46983.john@wexfordpress.com>


[-- Attachment #1.1: Type: text/plain, Size: 1733 bytes --]

On Fri, Sep 26, 2008 at 8:00 PM, John Culleton <john@wexfordpress.com>wrote:

> Recent texlive 2008 installed on Linux Slackware 12.0 system.
>
> I have a file that I can process via texexec and which shows up fine
> on my Acrobat Reader, kpdf or xpdf. However another person using
> (probably) Windows  keeps getting corrupt file errors when he tries
> to read it.   And when I try to run the output pdf through pdf2ps it
> blows up with this message:
>
> ---------------------------------------------------------------------------------
>  **** Warning:  An error occurred while reading an XREF table.
>   **** The file has been damaged.  This may have been caused
>   **** by a problem while converting or transfering the file.
>   **** Ghostscript will attempt to recover the data.
> ERROR: /undefined in /BXlevel
> Operand stack:
>   1   --dict:6/6(ro)(G)--   8¬­ÎµÈ¶dm
> Execution stack:
>   %interp_exit   .runexec2   --nostringval--   --nostringval--
> --nostringval--
> 2   %stopped_push   --nostringval--   --nostringval--   --nostringval--
> false   1   %stopped_push   1   3   %oparray_pop   1
> 3   %oparray_pop   1
> 3   %oparray_pop   --nostringval--   --nostringval--   --nostringval--
> --nostringval--   --nostringval--   --nostringval--
> false
> 1   %stopped_push   --nostringval--   %loop_continue   --nostringval--
> Dictionary stack:
>   --dict:1119/1686(ro)(G)--   --dict:0/20(G)--   --dict:107/200
> (L)--   --dict:107/200(L)--   --dict:104/127(ro)
> (G)--   --dict:241/347(ro)(G)--   --dict:18/24(L)--
>


> Current allocation mode is local
> ESP Ghostscript 815.04: Unrecoverable error, exit code 1
>
maybe gs is too old.
you can try with 8.61 or  8.62  or 8.63 (and cross the fingers ...)
-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 2485 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2008-09-26 18:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 18:00 John Culleton
2008-09-26 18:45 ` luigi scarso [this message]
2008-09-26 21:29   ` John Culleton
2008-09-26 21:47     ` luigi scarso
2008-09-26 21:53     ` Taco Hoekwater
2008-09-26 22:15       ` luigi scarso
2008-09-26 23:10       ` John Culleton
2008-09-26 23:49         ` John Culleton
2008-09-27  7:30           ` Taco Hoekwater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fe8d59da0809261145xa6ca8a8iab08a4fc8956e824@mail.gmail.com \
    --to=luigi.scarso@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).