brian@ut-sally.UUCP (Brian H. Powell) (07/12/85)
These are the patches to apply to rmaker.1 and rmaker.doc so they
will comply with the patches that GvR made to rmaker.c
Sorry I didn't get this ironed out before we released rmaker last week.
Brian
# This is a shell archive. Remove anything before this line,
# then unpack it by saving it in a file and typing "sh file".
#
# Wrapped by ut-sally!brian on Fri Jul 12 00:26:32 CDT 1985
# Contents: rmaker.1.patch rmaker.doc.patch
echo x - rmaker.1.patch
sed 's/^@//' > "rmaker.1.patch" <<'@//E*O*F rmaker.1.patch//'
*** oldrmaker.1 Sun Jul 7 00:26:20 1985
--- rmaker.1 Fri Jul 12 00:06:25 1985
***************
*** 27,39
See the BUGS section below for exceptions.
.PP
The optional \-d (debug) switch will list out in hex the contents
of all resources matching that four letter type.
.PP
! The usual backslash escape sequences are allowed in strings (\\[bfnrt] and
! \\ooo where the "o"'s are octal digits.) Also, \\xhh is allowed where "h" is
! a hexadecimal digit.
.SH SEE ALSO
"Putting Together a Macintosh Application"
(note: this manual is no longer part of Inside Macintosh)
.PP
"Format of the SUMacC Resource Compiler Input File" (basically
--- 27,38 -----
See the BUGS section below for exceptions.
.PP
The optional \-d (debug) switch will list out in hex the contents
of all resources matching that four letter type.
.PP
! Backslash escape sequences are allowed in strings in the form \\hh where
! "hh" are two hexadecimal digits.
.SH SEE ALSO
"Putting Together a Macintosh Application"
(note: this manual is no longer part of Inside Macintosh)
.PP
"Format of the SUMacC Resource Compiler Input File" (basically
@//E*O*F rmaker.1.patch//
chmod u=r,g=r,o=r rmaker.1.patch
echo x - rmaker.doc.patch
sed 's/^@//' > "rmaker.doc.patch" <<'@//E*O*F rmaker.doc.patch//'
*** oldrmaker.doc Fri Jul 12 00:05:48 1985
--- rmaker.doc Fri Jul 12 00:24:47 1985
***************
*** 1,8
_______________________________________________________________________________
FORMAT OF THE SUMACC RESOURCE COMPILER INPUT FILE
! last modified 7/1/85 by Brian Powell
_______________________________________________________________________________
You'll need to create a resource file for your application. This is
done with the Resource Compiler, and you'll have among your working
files an input file to the Resource Compiler. *** In the future,
--- 1,9 -----
_______________________________________________________________________________
FORMAT OF THE SUMACC RESOURCE COMPILER INPUT FILE
! Modified 07/01/85 by Brian Powell Adapt for SUMacC
! 07/11/85 Brian Powell mention backslash escapes
_______________________________________________________________________________
You'll need to create a resource file for your application. This is
done with the Resource Compiler, and you'll have among your working
files an input file to the Resource Compiler. *** In the future,
***************
*** 95,104
- All numbers are base 10 except where hexadecimal is indicated.
- The Type statements must be grouped by type in the input file.
Type WIND Window template
,1 Resource ID
Status Report Window title
40 80 120 300 BoundsRect (top left bottom right)
--- 96,107 -----
- All numbers are base 10 except where hexadecimal is indicated.
- The Type statements must be grouped by type in the input file.
+ - In general, all strings may include backslash escape characters.
+ (\XX where X is a hexadecimal digit.)
Type WIND Window template
,1 Resource ID
Status Report Window title
***************
*** 96,105
- All numbers are base 10 except where hexadecimal is indicated.
- The Type statements must be grouped by type in the input file.
Type WIND Window template
,1 Resource ID
Status Report Window title
40 80 120 300 BoundsRect (top left bottom right)
Visible GoAway For FALSE, use Invisible or NoGoAway
--- 99,109 -----
- The Type statements must be grouped by type in the input file.
- In general, all strings may include backslash escape characters.
(\XX where X is a hexadecimal digit.)
+
Type WIND Window template
,1 Resource ID
Status Report Window title
40 80 120 300 BoundsRect (top left bottom right)
Visible GoAway For FALSE, use Invisible or NoGoAway
***************
*** 215,225
Type CODE Application code segments
samp.o,0 Linker output file name, resource ID
[ SEE NOTE 3 BELOW ]
Type POST Postscript resource
,1 Resource ID
- 4 Number of strings
This is string one The strings...
This is string two
Third string
Bench warmer Apple's joke, not mine.
--- 219,228 -----
Type CODE Application code segments
samp.o,0 Linker output file name, resource ID
[ SEE NOTE 3 BELOW ]
Type POST Postscript resource
,1 Resource ID
This is string one The strings...
This is string two
Third string
Bench warmer Apple's joke, not mine.
***************
*** 223,233
Third string
Bench warmer Apple's joke, not mine.
Notes:
! 1. The Resource Compiler adds a NUL character (ACII code 0) at the
beginning of the name you specify for a 'DRVR' type of resource
if it doesn't begin with a period ('.'). Therefore, device drivers
should start with a '.', and desk accessories with any other character.
This inclusion of a nonprinting character avoids confilict with
file names that are the same as the names of desk accessories.
--- 226,236 -----
Third string
Bench warmer Apple's joke, not mine.
Notes:
! 1. The Resource Compiler adds a NUL character (ASCII code 0) at the
beginning of the name you specify for a 'DRVR' type of resource
if it doesn't begin with a period ('.'). Therefore, device drivers
should start with a '.', and desk accessories with any other character.
This inclusion of a nonprinting character avoids confilict with
file names that are the same as the names of desk accessories.
@//E*O*F rmaker.doc.patch//
chmod u=r,g=r,o=r rmaker.doc.patch
exit 0