3 ms·
Indeed. The conceptual model of a WordPerfect document is a single stream of text, interspersed with formatting instructions. That meant, for example, that, af
by Someone 6y ago
Indeed. The conceptual model of a WordPerfect document is a single stream of text, interspersed with formatting instructions.
That meant, for example, that, after backspacing over a return, you could end up with a paragraph of text with, somewhere in the middle, a “set left margin to 3 cm” instruction, or with multiple conflicting instructions (I think neither was supposed to happen, but all software is buggy). I didn’t use WP, so I wouldn’t know what that meant for the paragraph being laid out. It might have been applied starting at entire paragraph that contained the instruction, at the next paragraph, or immediately.
The ‘raw view’ didn’t only allow you to see the (potential) mess of formatting instructions, but also to edit it.
So, if you knew your way around there, you could fix any problem with documents.
IMO, if WP were less buggy, it probably wouldn’t have needed that mode. I also think its existence put less pressure on WP to fix bugs.
- unilynx 6y agoMy question was whether MS Word indeed had something similar at some point As for WP, it's been a long time, but I don't remember having had such paragraph formatting issues needing the raw view. The raw view was mostly useful as WP wasn't really WYSIWYG (but there was some sort of print preview in DOS in 5.1) and there's only so much formatting you can show in text mode.
- Someone 6y agoAFAIK Word (but I never used MS DOS Word, and mostly used Word for Mac) never had something similar. It could, and still can, show invisibles, but that’s a very far cry from showing all formatting instructions. And as you said, its model is completely different. It doesn’t do formatting instructions inline (WordPerfect:Word is a bit similar to html without any css and html with only css)
- lukasb 6y ago"I also think its existence put less pressure on WP to fix bugs." IMO this is not a good reason to deny users an escape hatch to make fixing problems at least possible. To be fair it depends on what kind of users you care about - if you're building a tool for professionals, I think this should be considered table stakes.