8-bit acorn software: other • Re: Saving the text on screen to a file

At the point of capture, you have to know the intended purpose, to be able to prepare the output accordingly:

• All the text on screen, or just the current text window
• Plain text* (eg for sharing here, < ASCII 127) or with user defined chars (>=128)
• With preamble§ defining window, user characters, palette, or without

* But if you’re on a Master, does 128-255 also count as plain text? Would you then need a host utility to translate the top bit set chars to Unicode equivalents?

§ for a text window your preamble would need to change depending on the area of screen originally captured:

• For a full screen including a window, VDU26, print screen of text, redefine text window
• For just a text window: VDU26, define text window, print text

You could argue something similar for a graphics dump:

• The whole screen, or just the current graphics window
• With preamble defining mode, window, palette, or just a *SAVE

Edit. I suppose you could simply save everything: mode, palette, udc, text, window and that could be *TYPED to recreate the original. But with an additional utility that extracts from that file what you want; just the text in the window? The character definitions? The plain text? For everything other than the plain text, output could be raw or BASIC VDU format.

Statistics: Posted by james — Mon Nov 25, 2024 6:53 am

---