🚀 go-pugleaf

In article <9328@watdragon.waterloo.edu> wsflinn@violet.waterloo.edu (Scott Flinn) writes:
>
>   The trick is that the picture is enhanced by printing each line
>3 times, which produces many overstruck characters.  My own naive
>attempt to print this picture (basically using fgetc() and fputc(),
>or fgets() and fputs(), Bconout(), etc.) fails miserably.  It prints the
>first pass of the line, some x's at the right and left margin, and
>ignores the remaining characters.  Each line in the file has >200
>characters ... the characters which are overstruck on each line
>are simply separated by spaces (ascii 32's), not '\r's ... and each
>line ends with '\n'.  What are the printing programs doing with
>these lines.  Are they breaking them into 3 smaller '\r' separated
>lines (how do they know the line length)?  I'm lost ... help.


Just a guess, but I'd say the file I/O functions in your compiler's library
are stripping out all carriage returns.  Atari compilers usually do this to
convert text files from Atari format (Which ends each line with a
carriage-return/line-feed pair) to Unix format (which ends each line with just
a carriage-return) so that programs can be ported from UNIX to the ST more
easily.

You're going to have to disable this conversion by openning the file as a
"binary" file.  With the old Megamax compiler, this is done by beginning the
file mode string with a 'b', as in:

        fp = fopen("STARTREK.PIC", "br");

                                    ^-- Notice the 'b'

Hope that helps.

		-- Steve Kirkendall