X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h=
	reply-to:subject:to:references:from:message-id:date:mime-version
	:in-reply-to:content-type; s=fm1; bh=jNxXThTaQZftTpxapj/DBlz5rSx
	9A4d9cCUnMZuRpoI=; b=ifrQwsgzeDqZRljtIIYDDP/tw7AdgfzImk3w00DG7cR
	RpjeMwB9o+WsWV0wNRXGW9++V5WyNi5XElkrj/awNDv1n55CS88YJYmv3x2Z6THk
	hOMz/jzfY3pKo1eVL5kAaMkqb99ynjox04AwUv9GMXFcH7S1rzby1oilMAg4mHuJ
	jUO+tMOmsVIEwOpRLQ1XYrWErMELpGVuW44/53sfrvN7r+9VL5+P9q6vuhV8IOJB
	65pUA9mEA1fSz9+tL6ct6vgowJqXxGm6yAAY2sGu3pvXA8bQeMbTZUQFCOeDuX6V
	z/P9yX8uGzRqWlZtxP9cwPZ36oFiePEnY5oRtMnhONw==
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-type:date:from:in-reply-to
	:message-id:mime-version:references:reply-to:subject:to
	:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=
	fm1; bh=jNxXThTaQZftTpxapj/DBlz5rSx9A4d9cCUnMZuRpoI=; b=I3xmnv9/
	QhABNdOdFFXxtLa8li+qfagywUeoqIkuR01vnJ+M7D014AmTfZy3BRqTlzSvOCUu
	cnWRL40Cpj85FmiyCiZfVl4rBt/r/WawQ0pXVP1TuCNt645Y6Oss+UoPEC+CgaeW
	7jhIuo7Rso/BLtX8Z4S0vouJXJF9UfP9ZNQ4mJem50CAvob+BfKrj9r7FtGIamII
	zV1pPt8Ke9rugwCSuEO0ziMdSxUb1jK0HH2Wts6QS3x0fxdfxAQ+PQkgktmrMTdY
	0psS4Nk+8yoWeUirU9USIrk8tM+QhTDh7rpFxKm8pRNxP6TbtEM01XZd9fy2poqt
	d2ZA5s/p171olQ==
X-ME-Sender: <xms:rMu8XUcOPCeX9GDuhhcFNPw-R98tTS6JBXqz4AjkpwRUykzSJu84yw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddtkedgudelucetufdoteggodetrfdotf
    fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
    uceurghilhhouhhtmecufedttdenucenucfjughrpehruffvfhfhkffffgggjggtsegrtd
    erredtfeejnecuhfhrohhmpefiihhrvhhinhcujfgvrhhruceoghhhvghrrhhlsehfrghs
    thhmrghilhdrtghomheqnecukfhppedutdekrddvudehrdduleehrddvtdehnecurfgrrh
    grmhepmhgrihhlfhhrohhmpehghhgvrhhrlhesfhgrshhtmhgrihhlrdgtohhmnecuvehl
    uhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:rMu8XUvLw6T8rj8avSBj8NmLu5vdzLLuR7LP-qr2FMDPQVuqd7iaLw>
    <xmx:rMu8Xd7mHOz9JHEhey_qnUcXqv1rCGEDARlny6iP4O4wpg0Cm6MRfQ>
    <xmx:rMu8XbzUpDfJUvXoqjxQQuA1N94npy-zF-Ui89og-CcHo74vUUAkHg>
    <xmx:rMu8Xa0gbiT-OhMSg1Oqea_wDthU89OUs4HRU8ixv2zUWTDWXgHing>
Subject: Re: [geda-user] gschem PostScript print-to-file output failing -
 SOLVED
To: geda-user AT delorie DOT com
References: <a3d5103b-dd29-94f9-d6a6-f09a88132bc9 AT fastmail DOT com>
From: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <7ef8d0ee-a011-84fb-0785-60c4d7ca5113@fastmail.com>
Date: Fri, 1 Nov 2019 17:13:45 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <a3d5103b-dd29-94f9-d6a6-f09a88132bc9@fastmail.com>
Content-Type: multipart/alternative;
 boundary="------------2C7D8F32A2F6832574215E31"
Content-Language: en-US
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

This is a multi-part message in MIME format.
--------------2C7D8F32A2F6832574215E31
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 10/31/19 12:14 PM, Girvin Herr (gherrl AT fastmail DOT com) [via 
geda-user AT delorie DOT com] wrote:
>
> Greetings,
>
> I am using gEDA gschem 1.8.2 (g875406c) and GhostScript 9.26 on 
> Slackware Linux 14.2.
>
> What I am trying to do is export my gschem drawing and import it into 
> QCAD. I "printed" the drawing to a PostScript file and tried to use 
> pstoedit to convert the PostScript file to a DXF file which QCAD will 
> import. This has worked well on a PCB eps exported file. In fact I 
> tested it today and it still is working. However, pstoedit seems to 
> fail. Rather, it seems to be GhostScript that is failing when it 
> encounters a "findfont" name in the gschem PostScript file. I am 
> pretty sure this process worked for me in the past (years ago) when I 
> had to convert a gschem drawing to a DXF file. Something since then 
> has changed and I expect that to have been GhostScript, since it has 
> been updated twice since I may have used it. The gs versions I have 
> had installed in the past are 9.19, 9.25, and now 9.26. According to 
> my research on pstoedit, the pstoedit failures started with the 9.2x 
> series, if that helps.
>
> snip 8x---
>
> It looks like maybe "findfont" was a PostScript key word or function 
> at one time, but now GhostScript is no longer supporting it. I am not 
> a Postscript guru.
>
> Two questions:
>
>  1. Is this problem known and is there a work-around?
>
>  2. Is there another gschem process I can use to get a workable
>     PostScript, Encapsulated PostScript, or DXF-directly output file
>     which I can import into QCAD?
>
> Thanks.
>
> Girvin Herr
>
>
Greetings,

I got a process that works. I am really surprised no one on this list 
suggested gaf export! gaf comes with gEDA/gaf 1.10.0. Using the export 
option converts an sch file directly into Postscript (PS), Encapsulated 
Postscript (EPS) or Portable Document Format (PDF), as well as a few 
others outside the scope of my task.

Today, I have been doing a lot of testing of the different formats and 
how pstoedit reacts to them. I successfully created DXF files from PS 
and EPS files generated by gaf, but not PDF. It seems pstoedit still has 
font problems with PDF input, even though it is supposed to accept it. 
However, I now have a work-around to continue working on my task.

BTW: I really like the look and feel of gschem 1.10.0. Kudos to all the 
devs who worked on it. I still need to get familiar with the new look 
and commands, but I think it is a major productivity improvement.

Thanks to all who responded to my problem.

Girvin



--------------2C7D8F32A2F6832574215E31
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 10/31/19 12:14 PM, Girvin Herr
      (<a class="moz-txt-link-abbreviated" href="mailto:gherrl AT fastmail DOT com">gherrl AT fastmail DOT com</a>) [via <a class="moz-txt-link-abbreviated" href="mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:a3d5103b-dd29-94f9-d6a6-f09a88132bc9 AT fastmail DOT com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <p>Greetings,</p>
      <p>I am using gEDA gschem 1.8.2 (g875406c) and GhostScript 9.26 on
        Slackware Linux 14.2.</p>
      <p>What I am trying to do is export my gschem drawing and import
        it into QCAD. I "printed" the drawing to a PostScript file and
        tried to use pstoedit to convert the PostScript file to a DXF
        file which QCAD will import. This has worked well on a PCB eps
        exported file. In fact I tested it today and it still is
        working. However, pstoedit seems to fail. Rather, it seems to be
        GhostScript that is failing when it encounters a "findfont" name
        in the gschem PostScript file. I am pretty sure this process
        worked for me in the past (years ago) when I had to convert a
        gschem drawing to a DXF file. Something since then has changed
        and I expect that to have been GhostScript, since it has been
        updated twice since I may have used it. The gs versions I have
        had installed in the past are 9.19, 9.25, and now 9.26.
        According to my research on pstoedit, the pstoedit failures
        started with the 9.2x series, if that helps.<br>
      </p>
      snip 8x---
      <p>It looks like maybe "findfont" was a PostScript key word or
        function at one time, but now GhostScript is no longer
        supporting it. I am not a Postscript guru.<br>
      </p>
      <p>Two questions:<br>
      </p>
      <ol>
        <li>Is this problem known and is there a work-around?<br>
          <br>
        </li>
        <li>Is there another gschem process I can use to get a workable
          PostScript, Encapsulated PostScript, or DXF-directly output
          file which I can import into QCAD?<br>
        </li>
      </ol>
      Thanks.<br>
      <p>Girvin Herr</p>
      <p><br>
      </p>
    </blockquote>
    <p>Greetings,</p>
    <p>I got a process that works. I am really surprised no one on this
      list suggested gaf export! gaf comes with gEDA/gaf 1.10.0. Using
      the export option converts an sch file directly into Postscript
      (PS), Encapsulated Postscript (EPS) or Portable Document Format
      (PDF), as well as a few others outside the scope of my task.</p>
    <p>Today, I have been doing a lot of testing of the different
      formats and how pstoedit reacts to them. I successfully created
      DXF files from PS and EPS files generated by gaf, but not PDF. It
      seems pstoedit still has font problems with PDF input, even though
      it is supposed to accept it. However, I now have a work-around to
      continue working on my task.</p>
    <p>BTW: I really like the look and feel of gschem 1.10.0. Kudos to
      all the devs who worked on it. I still need to get familiar with
      the new look and commands, but I think it is a major productivity
      improvement.<br>
    </p>
    <p>Thanks to all who responded to my problem.</p>
    <p>Girvin</p>
    <p><br>
    </p>
  </body>
</html>

--------------2C7D8F32A2F6832574215E31--