Thus, the long-save saves the document as a single pristine piece. Bug in piece table handling = corrupted file ![]()
#How to move a piece of text to the right margin in word full#It also means that if the piece table is some how messed up, and you keep editing that file, every time you try and do the full save, it'll break. I thought I was going to have an interesting technical discussion about data structure serialization or some other nerdy topic. It also explains weird quirks with word, like why sometimes an edit would have different formatting depending on where it was placed in the document. #How to move a piece of text to the right margin in word verification#If the user manages to split at an inopportune location, rebuilding the original intended file may not work, unless there is some active verification of the edit. In my mind, this explains how files would break, because you're constantly splitting the file up into pieces, without verifying that your split location doesn't break additional formatting. While you are working, you generate the piece table, so if you save, close word, and re-open, you won't be able to undo operations. Regular save traverses the piece table, and thus takes a long time to do. So, even if fast-save were disabled and the piece-table was corrupted, word would still corrupt the file. The piece table is used even if you turn off fast-save because that's how undo redo and editing works.
0 Comments
Leave a Reply. |
AuthorKim ArchivesCategories |