Games often alter “wrapping”: it would normally be on for a window holding running text but off for a status-line window, which is why window 0 has “wrapping” on by default but all other windows have “wrapping” off by default.
But §8.8.3.3 states:
Window 0 initially has attribute 1 off and 2, 3 and 4 on (scrolling, copy to printer transcript, buffering). Windows 1 to 7 initially have attribute 4 (buffering) on, and the other attributes off.
which contradicts the former’s statement that Window 0 initially has attribute 1 (wrapping) on.
The former is obviously correct, as confirmed by the Infocom YZIP documentation (section “Windows”), the behavior of Frotz, and the behavior of the Infocom Macintosh YZIP interpreter (see function INITWB in mx1.a). §8.8.3.3 should be changed to read “Window 0 initially has all attributes on.”
§8.8.3.1.2.2 states:
Games often alter “wrapping”: it would normally be on for a window holding running text but off for a status-line window, which is why window 0 has “wrapping” on by default but all other windows have “wrapping” off by default.But §8.8.3.3 states:
Window 0 initially has attribute 1 off and 2, 3 and 4 on (scrolling, copy to printer transcript, buffering). Windows 1 to 7 initially have attribute 4 (buffering) on, and the other attributes off.which contradicts the former’s statement that Window 0 initially has attribute 1 (wrapping) on.
The former is obviously correct, as confirmed by the Infocom YZIP documentation (section “Windows”), the behavior of Frotz, and the behavior of the Infocom Macintosh YZIP interpreter (see function INITWB in mx1.a). §8.8.3.3 should be changed to read “Window 0 initially has all attributes on.”