public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Frantisek Hanzlik <franta@hanzlici.cz>
To: Vedran Vucic <vedran.vucic@gmail.com>
Cc: linux-msdos <linux-msdos@vger.kernel.org>
Subject: Re: printing
Date: Sun, 28 Nov 2010 03:20:42 +0100	[thread overview]
Message-ID: <4CF1BC7A.2030306@hanzlici.cz> (raw)
In-Reply-To: <AANLkTikUv3YdRLdub0KoVTUMSPUd1DFNYBzkXzok=A7J@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4595 bytes --]

Vedran Vucic wrote:
> Hello,
> 
> Please find attached output of my DOS application.
> Fonts are in /usr/local/ghostpdl-8.71/urwfonts
> 
> I am not sure that pcl6 is aware oftheirlocation.
> 
> I still have the same error message.
> 
> Thanks,
> 
> vedran
> 
> 
> 
> 
> On Sat, Nov 27, 2010 at 9:08 PM, Frantisek Hanzlik <franta@hanzlici.cz> wrote:
>> Vedran Vucic wrote:
>>> Hello,
>>>
>>> I installed ghostpdl properly.
>>> When I do:
>>> $_lpt1='cat >/tmp/x.pcl'
>>> I get in /tmp folder file that is output from the program and it is
>>> actually text file.
>>>
>>> When I do other command:
>>> pcl6 -sDEVICE=pswrite -sPAPERSIZE=a4 -sOutputFile=x.ps x.pcl
>>> I got the following error message:
>>> Warning interpreter exited with error code -1
>>> Flushing to end of job
>>>
>>> Obviously interpreter is an issue.
>>>
>>> I think that we are very close to the solution. DO you have any idea
>>> about -1 error code of interpreter?
>>>
>>> Thanks,
>>>
>>> Vedran
>>>
>>>
>>> On Sat, Nov 27, 2010 at 6:44 PM, Frantisek Hanzlik <franta@hanzlici.cz> wrote:
>>>> Vedran Vucic wrote:
>>>>> Hello,
>>>>>
>>>>> When I corrected as  you mentioned dosemu started normally. I entered
>>>>> my DOS application and tried toprint, but in terminal I have seen
>>>>> error message that pcl6 command is not found.
>>>>> Any suggestion? Any link or slink needed for that purpose?  Is there
>>>>> any path tweaking required?
>>>>
>>>> You wrote before You build ghostpdl package itself.
>>>> Was compiled properly?
>>>>
>>>> Was properly installed?
>>>>
>>>> Is pcl6 binary runnable?
>>>>
>>>> Is pcl6 binary in PATH in dosemu environment? (when no, you can specify
>>>> absolute path, e.g. $_lpt1='/my/path/pcl6 ...
>>>>
>>>> You should probably in this phase tune both things, dosemu and
>>>> pcl6/ghostpdl, separately:
>>>>
>>>> 1) in dosemu.conf lpt specification configure output to normal file:
>>>>
>>>> $_lpt1='cat >/tmp/x.pcl'
>>>>
>>>> and verify that file "/tmp/x.pcl" is rightly created and is in PCL format.
>>>>
>>>>
>>>> 2) verify that pcl6 command work right by manually creating postscript
>>>> file from previous PCL:
>>>>
>>>> pcl6 -sDEVICE=pswrite -sPAPERSIZE=a4 -sOutputFile=x.ps x.pcl
>>>>
>>>> and again verify that file "/tmp/x.pcl" is rightly created and is in
>>>> postscript format
>>>>
>>>>
>>>> 3) verify this postscript file printing:
>>>>
>>>> lpr -P Laserprinter x.ps
>>>>
>>>>
>>>> When all this steps works, You can set final "$_lpt1='....'" command in
>>>> dosemu.conf, as you have now.
>>>>
>>>> !!ATTENTION!! Sorry for mistake in all my previous mails: I incorrectly
>>>> specify "-sDEVICE=" parameter to "pdfwrite", which is obviously bad (I
>>>> clipboard copy this from my cfg, where I use pcl6 to create PDF
>>>> documents from DOS print output).
>>>> Right parameter value should be "pswrite":
>>>>
>>>> $_lpt1='pcl6 -sDEVICE=pswrite -dNOPAUSE -sPAPERSIZE=a4
>>>> -sOutputFile="|lpr -P YourPrinter1" -'
>>>>
>>>> FH
>>
>> I never got with ghostpdl to any bigger problems and not sure how
>> diagnose your.
>>
>> You can try some pcl6 (gs) debug switches, here is their doc:
>> http://svn.ghostscript.com/ghostscript/trunk/gs/doc/Use.htm#Debug_switches
>> You can study ghostpdl source code.
>>
>> Can you send me (or past somewhere for download) your PCL output from
>> DOS app? I can probe convert it with my ghostpdl build.
>>
>> Have you installed and rightly configured URW TTF fonts? ghostpdl
>> package require them.

My pcl6 works likely OK (see its output at:
http://www.hanzlici.cz/tmp/x.ps.bz2
), there is probably some wrong in your ghostpdl package.

Regarding TTF fonts location - problem may be there, you should correct
their path, this which is defined in ghostpdl source codes seems
appropriate for windos build.

I have located fonts in "/usr/share/fonts/urw-ttf/", then I patched
"pl/pjparse.c" as you can see in attached patch (there are some other
smaller patches, as I want use zlib and png system shared libraries
etc., and use some paths as conventional in my distro (Fedora).

SPEC file, which describe how I build ghostpdl and font RPM packages, is
contained in source rpm
(http://www.hanzlici.cz/packages/fedora/ghostpdl/14/ghostpdl-8.71-2.fc14.src.rpm)
or i got it for you to
http://www.hanzlici.cz/tmp/ghostpdl-8.71-fc14.spec
Notice instaled libpaper-devel, freeglut-devel, expat-devel,
libjpeg-devel, libpng-devel and zlib-devel packages.

At http://www.hanzlici.cz/packages/fedora/ghostpdl/14/ are my ghostpdl
RPM packages for current Fedora version (14; I have at this site dosemu
RPM packages as well)

Hope this help.
Franta Hanzlik

[-- Attachment #2: ghostpdl-fedora-8.71.patch.gz --]
[-- Type: application/x-gzip, Size: 1163 bytes --]

  reply	other threads:[~2010-11-28  2:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 23:18 printing Vedran Vucic
2010-11-18 23:52 ` printing Ivan Baldo
2010-11-19  0:02   ` printing Vedran Vucic
2010-11-19  0:14     ` printing Ivan Baldo
     [not found]       ` <AANLkTin8-qGJ12--1RdfPT-sFB9=dS6Qx11SayLUda+a@mail.gmail.com>
2010-11-20 12:49         ` printing Ivan Baldo
2010-11-20 20:38           ` printing Vedran Vucic
2010-11-22 11:17             ` printing Paul Crawford
     [not found]           ` <AANLkTimV3u_wcGxv+p=aBRqEtkfgyXpkgiTS8H3srAWC@mail.gmail.com>
2010-11-22 23:32             ` printing Ivan Baldo
2010-11-22 23:54               ` printing Mike McCarty
2010-11-23  7:30               ` printing Vedran Vucic
2010-11-23  8:54                 ` printing Andrew Joakimsen
2010-11-23 18:36                   ` printing Vedran Vucic
2010-11-23 19:58                     ` printing Mike McCarty
2010-11-23 22:48                       ` printing Vedran Vucic
2010-11-26  1:15                         ` printing Andrew Joakimsen
2010-11-26  7:56                           ` printing Vedran Vucic
2010-11-26 10:31                             ` printing Frantisek Hanzlik
2010-11-27  7:42                               ` printing Vedran Vucic
2010-11-27 15:44                                 ` printing Frantisek Hanzlik
2010-11-27 16:10                                 ` printing Frantisek Hanzlik
2010-11-27 16:37                                   ` printing Vedran Vucic
2010-11-27 17:44                                     ` printing Frantisek Hanzlik
2010-11-27 18:53                                       ` printing Vedran Vucic
2010-11-27 20:08                                         ` printing Frantisek Hanzlik
2010-11-27 21:12                                           ` printing Vedran Vucic
2010-11-28  2:20                                             ` Frantisek Hanzlik [this message]
2010-11-29  6:10                                               ` printing Vedran Vucic
2010-11-29  7:09                                                 ` printing Frantisek Hanzlik
2010-11-19  7:11 ` printing Andrew Joakimsen
2010-11-19 11:35   ` printing Vedran Vucic
2010-11-29 18:39 ` printing Ken Heard

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=4CF1BC7A.2030306@hanzlici.cz \
    --to=franta@hanzlici.cz \
    --cc=linux-msdos@vger.kernel.org \
    --cc=vedran.vucic@gmail.com \
    /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