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 t
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
Dear all,
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 Debian Bug Tracking
system. There is an examp
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 De
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 200
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
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 DVIPDFM
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. :-(
If
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 "#".
Tha
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 Ess
Hi Thomas, hi TeX Live team,
the following bug we got here down in the Debian Bug Tracking system.
During the discussion it came to our attention, that the dvipdfm
development has stalled and the upstream can assumed to be dead (last
version was released in 2001, the ML of the project got 3 mails
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
13 matches
Mail list logo
