Hilmar Preusse [EMAIL PROTECTED] wrote:
Unfortunately I don't even
know the purpose of ebb.
, ebb(1)
| NAME
|ebb - extract a bounding box from JPEG, PNG, and PDF files
|
| SYNOPSIS
|ebb [ -v | -b ] graphic_file
|
| DESCRIPTION
|ebb extracts the bounding box
On 31.08.05 Jin-Hwan Cho ([EMAIL PROTECTED]) wrote:
On Aug 31, 2005, at 4:33 PM, Frank Küster wrote:
Hi,
The only person who can fix the bug is the author of DVIPDFM.
Of course. Can dvipdfmx be used as a drop-in-replacement for
dvipdfm, even if you don't process CJK files? Are there any
to drop dvipdfm in favor of dvipdfmx!
Regards,
Hilmar
- Forwarded message from [EMAIL PROTECTED] -
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Bug#322713: dvipdfm doesn't understand gs anymore
Date: Fri, 12 Aug 2005 13:56:27 +0200
Please consider to drop dvipdfm in favor of dvipdfmx!
Funny thing. I asked the fmx maintainers the same thing, about
completely dropping fm in favor of fmx in TL, and they advised me not
to do so. fm had additional programs (ebb and something else), and
different behavior in some cases.
On Sep 5, 2005, at 4:56 PM, Hilmar Preusse wrote:
Great! Just a short question: Do you know about
http://bugs.debian.org/291438 and is it eventually fixed in DVIPDFMx?
I've just read the bug report. The first report from Prabhu Ramachandran
(on Jan 22 15:31:54 +0530) was related to cmp_dest()
On 05.09.05 Jin-Hwan Cho ([EMAIL PROTECTED]) wrote:
On Sep 5, 2005, at 4:56 PM, Hilmar Preusse wrote:
Hi all,
Great! Just a short question: Do you know about
http://bugs.debian.org/291438 and is it eventually fixed in
DVIPDFMx?
I've just read the bug report. The first report from Prabhu
Ralf Stubner [EMAIL PROTECTED] wrote:
For more than 3 years, DVIPDFMx have been extensively tested by many
users. There might be some bugs which are not found yet. But the authors
of DVIPDFMx try to fix immediately if reported to them.
Sounds good. Maybe we should contact Thomas Esser and
Jin-Hwan Cho wrote:
On Sep 1, 2005, at 12:13 AM, Ralf Stubner wrote:
If you have the source code of DVIPDFM, check the file pdfobj.c.
In the line 631, the function pdf_check_name() checks the validity
of the character #. However, the variable valid_chars does not
contain #.
Thanks a lot!
Jin-Hwan Cho [EMAIL PROTECTED] wrote:
On Aug 24, 2005, at 3:17 AM, Hilmar Preusse wrote:
I'm sending this E-Mail to the author of dvipdfm and of dvipdfmx as
dvipdfm seems to be dead actually (the latest version is from 2001
and in the Mail archive got 3 Mails in 2004 and none in 2005).
The
Frank Küster wrote:
Jin-Hwan Cho [EMAIL PROTECTED] wrote:
On Aug 24, 2005, at 3:17 AM, Hilmar Preusse wrote:
I'm sending this E-Mail to the author of dvipdfm and of dvipdfmx as
dvipdfm seems to be dead actually (the latest version is from 2001
and in the Mail archive got 3 Mails in 2004
On Aug 31, 2005, at 4:33 PM, Frank Küster wrote:
The only person who can fix the bug is the author of DVIPDFM.
Of course. Can dvipdfmx be used as a drop-in-replacement for dvipdfm,
even if you don't process CJK files? Are there any disadvantages?
Surely DVIPDFMx can do that because
On Sep 1, 2005, at 12:13 AM, Ralf Stubner wrote:
Well, the /ideal/ person to fix this bug would be the author of
dvipdfm.
However, dvipdfm is licensed under GPL, so it is possible to fix this
bug, if one knows what has to be done. I have no idea what is causing
these problems, though. :-(
On Aug 24, 2005, at 3:17 AM, Hilmar Preusse wrote:
I'm sending this E-Mail to the author of dvipdfm and of dvipdfmx as
dvipdfm seems to be dead actually (the latest version is from 2001
and in the Mail archive got 3 Mails in 2004 and none in 2005).
The following bug was submitted here at the
PROTECTED], [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Bug#322713: dvipdfm doesn't understand gs anymore
Date: Fri, 12 Aug 2005 13:56:27 +0200
Message-ID: [EMAIL PROTECTED]
User-Agent: Mutt/1.5.6+20040907i
X-Mailing-List: debian-tetex-maint@lists.debian.org archive/latest/12542
Package: tetex
Frank Küster [EMAIL PROTECTED] wrote:
Hilmar Preusse [EMAIL PROTECTED] wrote:
On 17.08.05 Frank Küster ([EMAIL PROTECTED]) wrote:
[EMAIL PROTECTED] wrote:
Hi,
If I modify (HKS 43 K) into (HKS43K) in the eps, everything
works again. So it is a problem of the Space characters,
the way
Hilmar Preusse [EMAIL PROTECTED] wrote:
On 17.08.05 Frank Küster ([EMAIL PROTECTED]) wrote:
[EMAIL PROTECTED] wrote:
Hi,
If I modify (HKS 43 K) into (HKS43K) in the eps, everything
works again. So it is a problem of the Space characters,
the way gs convertes them, and dvipdfm not
On 17.08.05 Frank Küster ([EMAIL PROTECTED]) wrote:
[EMAIL PROTECTED] wrote:
Hi,
If I modify (HKS 43 K) into (HKS43K) in the eps, everything
works again. So it is a problem of the Space characters,
the way gs convertes them, and dvipdfm not understanding them.
It seems it is rather a
Hi Hadmut,
wir müssen leider nochmal nachfragen.
[EMAIL PROTECTED] wrote:
I have tracked this down to:
- The EPS contains a command like
1 0.75 0 0 (HKS 43 K) false newcmykcustomcolor
- dvipdfm calls gs to convert included EPS into
PDF. Latest version of gs-eps produces a PDF file
[EMAIL PROTECTED] wrote:
I have tracked this down to:
- The EPS contains a command like
1 0.75 0 0 (HKS 43 K) false newcmykcustomcolor
Meanwhile, Hadmut has sent me the eps file in private (it cannot be
published), thanks for that.
I can reproduce the bug in sid, but not in sarge. The
On 12.08.05 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
Hi,
I am producing some reports using latex and dvipdfm. They all
include the same EPS graphics, and it worked well for years.
But since last debian upgrade, dvipdfm terminates with this
error message:
Package: tetex-bin
Version: 2.0.2-31
Hi,
I am producing some reports using latex and dvipdfm. They all include
the same EPS graphics, and it worked well for years.
But since last debian upgrade, dvipdfm terminates with this
error message:
[1(../../../../Common/Doku/logo4c.epsPSInvalid PDF
21 matches
Mail list logo
