🚀 go-pugleaf

In article <20614@agate.BERKELEY.EDU> ladasky@codon2.berkeley.edu.UUCP (John Ladasky) writes:
>	If I understand this correctly, this document has indicated that it
>requires the Sonata font for printing.  The prolog of the file sonata.txt, if
>I am reading it correctly, appears to identify itself as the Sonata font (sor-
>ry about the funny formatting and hyphenation, but there was no way that I
>could discover to read the contents of this file {apparently a single string!}
>except to pipe it through nroff):
>
>	%!PS-AdobeFont-1.0%%CreationDate:  Sun  Mar    8   17:24:49   PST
>	(etc.)
>
>	Unless there's something important that I've missed, I see no reason
>why the following command would not work:
>
>	cat sonata.txt harmony1.eps | lpr

The key to your problem, I think, is the "funny formatting and
hypenation" that you mentioned.  I think that there are two problems.
The first is that the sonata.txt file appears to have only carriage
returns and no line feeds.  This is common for PC files; Unix files
require linefeeds as the line terminators.  The net result of this is
probably that the entire file is "commented out", since the first
character is a comment character and it appears to be only one line
long because of the line endings.  You should feed it through a filter
to change CR to LF (you can use the Unix utility "tr" for this).  The
second problem is that it appears that somebody hyphenated the file.
You should probably go back to the PC version and start over, making
sure that whatever software you use to transfer the file does not
change the linebreaking, but perhaps does convert the line ending
characters.

You're right that in theory the "cat sonata.txt harmony1.eps | lpr"
should work, and I think your analysis of the EPS file header is correct.

Glenn Reid
Adobe Systems
Developer Tools & Strategies