ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "George N. White III" <gnwiii@gmail.com>
Subject: Re: pdfetex 1.40.1 + ghosscript problem? More findings
Date: Sat, 20 Jan 2007 16:37:18 -0400	[thread overview]
Message-ID: <22af238a0701201237t29c30988s258b8ccab560e4ed@mail.gmail.com> (raw)
In-Reply-To: <45B27018.2050301@econ.muni.cz>

On 1/20/07, Michal Kvasnicka <quasar@econ.muni.cz> wrote:
> Good evening.
>
> I found some more puzzling things. I write them here fore anybody who
> may be interested. :-)
>
> I tried to typeset a document using two font families: TrueType Gentium
> by SIL, and Adobe OpenType Myriad. First I converted Myriad to Type1
> using fontforge, then I prepared metrics for all fonts with TeXFont
> using ec-lm encoding. I found this:
>
> (1) Any ConTeXt document produced by pdfetex 1.40.1 (even this one:
>     \setupoutput[pdf]
>     \starttext
>     \input tufte
>     \stoptext
> makes my GhostScript (gs Ghostscript 8.15.3 under SuSE Linux 10.1) die
> with this error:
>    **** 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
> etc.

There was a gs bug (#688787 /undefined in /BXlevel) for this error,
but in that case the pdf file really was corrupt although the user
said it worked with Adobe Reader.

I tried your first test on Fedora Core 5 with TL2007 (test inst iso
from 20070115) which also has a gs-8.15 version, and don't get an
error.

[gwhite@cerberus TL2007]$ cat cont-try.tex
\setupoutput[pdf]
\starttext
\input tufte
\stoptext
[gwhite@cerberus TL2007]$ texmfstart texexec cont-try
[...]
This is pdfTeXk, Version 3.141592-1.40.1 (Web2C 7.5.6)
 \write18 enabled.
 %&-line parsing enabled.
 (/mnt/hdb/opt/tex/texlive/2005/texmf/web2c/natural.tcx)
entering extended mode
(./cont-try.tex

ConTeXt  ver: 2006.08.08 21:51  fmt: 2007.1.14  int: english  mes: english
[...]

[gwhite@cerberus TL2007]$ pdffonts cont-try.pdf
name                                 type         emb sub uni object ID
------------------------------------ ------------ --- --- --- ---------
ORKXYQ+LMRoman12-Regular             Type 1       yes yes yes      5  0

[gwhite@cerberus TL2007]$ pdfinfo cont-try.pdf
Title:          cont-try
Subject:
Keywords:
Author:
Creator:        ConTeXt - 2006.08.08 21:51
Producer:       pdfTeX-1.40.1
CreationDate:   Sat Jan 20 15:29:21 2007
ModDate:        20070120
Tagged:         no
Pages:          1
Encrypted:      no
Page size:      595.276 x 841.89 pts (A4)
File size:      26205 bytes
Optimized:      no
PDF version:    1.5

-- 
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia

  reply	other threads:[~2007-01-20 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 20:18 pdfetex 1.40.1 + ghosscript problem? Michal Kvasnicka
2007-01-18 23:59 ` Martin Schröder
2007-01-19  0:21   ` Hartmut Henkel
2007-01-19  9:01     ` Hans Hagen
2007-01-20 19:40       ` pdfetex 1.40.1 + ghosscript problem? More findings Michal Kvasnicka
2007-01-20 20:37         ` George N. White III [this message]
2007-01-21 23:00         ` Hans Hagen

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=22af238a0701201237t29c30988s258b8ccab560e4ed@mail.gmail.com \
    --to=gnwiii@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).