[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#322713: marked as done (dvipdfm doesn't understand gs anymore)

Your message dated Sun, 4 Aug 2019 16:11:17 +0200
with message-id <e18902eb-a62a-d31d-20dc-ac62a55946dd@web.de>
and subject line Re: Bug#322713: [tex-live] (fwd) Bug#322713: dvipdfm doesn't understand gs anymore
has caused the Debian Bug report #322713,
regarding dvipdfm doesn't understand gs anymore
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
322713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322713
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin 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.eps<PS>Invalid PDF name
"HKS#2043#20K"

pdf_new_name:  invalid PDF name



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 
  with 

  [/Separation
  /HKS#2043#20K
  /DeviceCMYK
  9 0 R]endobj
  10 0 obj


  That HKS#2043#20K name is understood by every pdf application 
  except dvipdfm. 



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.

regards
Hadmut

--- End Message ---
--- Begin Message --- 
Version: 2016.20160513.41080.dfsg-2

Am 17.09.2005 um 18:18 teilte Karl Berry mit:

>     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.  They hoped to make it completely
> compatible soon, so we could drop fm next time around.  At least that
> was my understanding ...
> 
Meanwhile

hille@debian-ost:~$ ls -l /usr/bin/*dvipdfm*
lrwxrwxrwx 1 root root      9 Sep 19  2018 /usr/bin/dvipdfm -> xdvipdfmx
lrwxrwxrwx 1 root root      9 Sep 19  2018 /usr/bin/dvipdfmx -> xdvipdfmx
-rwxr-xr-x 1 root root 767048 Sep 19  2018 /usr/bin/xdvipdfmx

dvipdfm has been replaced by a link to dvipdfmx. ebb/extractbb seems to
be developed by DVIPDFMx project team.

So, this issue can be closed.

H.
-- 
sigfault
#206401 http://counter.li.org

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: