| Title: | Languages |
| Notice: | Speaking In Tongues |
| Moderator: | TLE::TOKLAS::FELDMAN |
| Created: | Sat Jan 25 1986 |
| Last Modified: | Wed May 21 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 394 |
| Total number of notes: | 2683 |
I decided to check into COCKTAIL because of the suggestion
given in 351.5 by BHAJEE::JAERVINEN. I've run into
some minor problems. Is this conference the right
place to ask these questions ?
1. BEGMANUAL.PS.Z
I copied this file and uncompressed it. When I attempt
to print on my local PrintServer 20 the following
error condition is displayed:
%LPS-W-SYNERR, syntaxerror: Input ended in string or procedure
body - offending command is --nostringval--
%LPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored
2. README
The README file is screwed up as far as CR/LF characters are
concerned:
and installation of the tools
doc.ps documentation in postscript format
doc.me documentation in troff format, me ma
cros
man manual pages in troff format, man macros
rex Scanner Generator
lalr LALR(1) Parser Generat
or
ell LL(1) Recursive Descent Parser Generator
bnf Transforms Grammars from Extended BNF to Plain BNF
This does'nt give me warm and fuzzy feelings if I can't even
print the beginner's manual or read the README file.
Is there someone within Digital supporting this software ?
Ed
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 355.1 | AUSSIE::GARSON | nouveau pauvre | Thu Apr 29 1993 19:38 | 22 | |
re .0
>%LPS-W-SYNERR, syntaxerror: Input ended in string or procedure
>body - offending command is --nostringval--
>%LPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored
Try printing on a DEClaser 2xxx. I have seen a number of PS files that
fail on the LPSxx but work on the former. Of course it could be that
your PS file is missing its tail. You didn't run out of diskquota or
something during the decompress?
>The README file is screwed up as far as CR/LF characters are
>concerned:
Probably fixable with CONVERT/FDL. If you can't suss it out then post a
pointer to the file.
>This doesn't give me warm and fuzzy feelings if I can't even
>print the beginner's manual or read the README file.
Sounds to me as if this software was not developed under VMS. If that's
the case, welcome to the world of interoperability.
| |||||
| 355.2 | BHAJEE::JAERVINEN | Client-cerveza architecture wins | Mon May 03 1993 08:33 | 26 | |
For support, you should probably contact the author (the mail address
is in the documentation).
Yes, the software is mainly intended for Unix (runs fine on Ultrix, I
haven't tried VMS). It's written in Modula-2, and the distribution
contains the sources in C as well (created by a Modula-2 to C
translator). There are makefiles also - as I said, I didn't have any
problems building the stuff on Ultrix.
As to the little problems: copying text files from Ultrix to VMS often
doeasn't work too well. There's a little utility to fix this, called
'bilf'. Install it as a foreign command and say "bilf l readme.txt" and
the file is fine. You can get bilf e.g. from
TARKIN::DASH2:[LIN.PUBLIC.VMSTOOLS]BILF.EXE
As I happened to still have the readme file online, I put it on
BHAJEE::COCKTAIL_README.TXT. Feel free to grab it if you can't make
yours readable.
I don't recall having any problems printing the postscript
documentation on LPS-20 or LN03R. Because they're just text files, you
should perhaps bilf them too before printing I think (I don't remember
whether I did, it's quite some time ago).
| |||||