-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge 11.3.1.6 and 11.3.4.4 #1477
Comments
Part of the intended restructuring of chapter 11, see #1427. |
What confuses me is the prose within 11.3.4.4 which refers to restore as a "simple case where a simple deletion is marked as having been subsequently cancelled", whereas the actual definition of restore is that it "indicates restoration of text to an earlier state by cancellation of an editorial or authorial marking or instruction." That means that restore cannot only be used for restoring deleted text, but also for other marks like circled or underlined text, etc. Might one say that restore is used for restoring a "single" intervention and undo for a "sequence" of related interventions? Has anyone a clear distinction of these two elements? |
I think the syntax is the key to understanding the difference:
So, the (previously deleted) text is restored, while the previous alteration is undone. |
Council discussed this and we agree with Gerrit's explanation here. Go ahead and implement the revision (which helps toward general revision of Ch. 11). |
Asked the MS-SIG for examples (already got responses) |
The question of |
As discussed with Gerrit Brüning in late October, the issue will be postponed and implemented as part of the restructuring of Chapter 11. |
The content of 11.3.1.6 may be combined with the content of 11.3.4.4.
In particular, it seems to me that the fictitious use case could as well be handled with
<restore>
:I think it’s up to the individual encoder what he or she considers a “comparatively simple case”. Instead, the usage of
<restore>
or<undo>
may more or less be a matter of style. One encoder might like pointer mechanisms, while another encoder might find nested elements, easier to encode, to read, and to process.The text was updated successfully, but these errors were encountered: