Share via

Scrambled sentences in Word doc?

Anonymous
2017-10-30T22:28:41+00:00

I've been working on revisions for my novel (I'm an author and these edits are for my publisher), and I noticed that MS Word will sometimes scramble my words and sentences. It's not all the time or on every page, but I haven't figured out what triggers it (maybe it's where my editor left "tracked changes" comment balloons, which I later deleted, or maybe it is where I have some apostrophes that Word did not like, or maybe it happens whenever I work on a file using the mobile app for iPhone, or maybe it is just random). In any event, I noticed the problem about a month or so ago, and I didn't know how to recover the document. Fortunately, I had the original document my publisher sent me, so when it came time to do revisions and I came to a wonky part of the text, I just copied the text over from the clean document and used that for my revisions.

Well, now that I am mostly done with revising my document, I've noticed that Word is STILL corrupting/scrambling my sentences. The problem now, though, is that it's doing it to my revised document, so it's hard to track a version of the document that has unscrambled text. I've got a bunch of saved files that should theoretically help me, but I feel like when I open them, the same paragraphs are all getting corrupted. I can go back to the clean doc from my publisher, but then I lose all the revisions I made (which is not an option). How do I clean my document and stop it from getting corrupted again in the future? I can't work like this!!!

-Justin

Office 365 for Mac

Here's an example, by the way, of what I am dealing with:

Clean/original paragraph:

Kenton nodded. ‘It wasn’t too hard. I held it and thought about how thirsty I was.’

‘That’s not so bad, I guess. What’d you fill it with?’

‘Honeywine. Dorstal drank it when he reallised.’

 ‘So maybe you could use a common artifact,’ Annev said, trying to draw the attention back to the mission, ‘which the rod probably is, if Janak used it on Dorstal. So we should concentrate on finding the rod first.’ He wheeled his horse around. ‘C’mon. Let’s find a spot to tie these horses up.’

First time it got corrupted:

Kenton nodded. ‘It wasn’t too hard. I held it and thought about how thirsty I was.’

‘Thatgrunted.thought about how thirsty I was.ne could’

‘.oneywine. Dorstal drank it when he reallised.’

‘So maybe you could use a common artifact,’ Annev said, trying to draw the attention back to the mission, ‘which the rod probably is, if Janak used it on Dorstal. So we should concentrate on finding the rod first.’ He wheeled his horse around. ‘Ce wheeled his horse around.  o kill Duvarekt Do’

My revised (clean) paragraph:

(Can't find a clean version, because this crap happened...)

Most recent wonky/corrupted paragraph:

Kenton nodded. ‘It wasn’t too hard. I just held it and thought about how thirsty I was.’

‘Huh, it and thou‘That’s . . . not so bad. What’d you fill it with??

‘Honeywine,neywinel it with?? abo. ‘Dorstal drank it when he realised.’ The trio laughed at that and Annev felt encouraged by the admission. He wheeled his horse about. ‘C’mon. Let’s find a spot to tie up these horses.’

UPDATE #1:

I did some testing by highlighting the problem fields and saving multiples instances of the document (some with revisions and some without), and it appears that those files are becoming corrupted whenever I use "Save As" to create a new version of the document (a common practice when I sometimes need to go back to a previous version of the document, so I name each document with a new version number). If I just save the document and close it, things seem to be unchanged, but whenever I use "Save As" things go haywire. Thoughts, suggestions, or solutions?

UPDATE #2:

After some further testing, I've come to the conclusion that none of the new text is being corrupted (only the old paragraphs that needed to be revised). It also seems that the scrambled sentences have exactly the same number of characters (and appear in the exact same locations) as the original documet. Consequently, I have a work-around solution to the problem, which is this: manually type an exact duplicate of the text that is getting scrambled (before it gets scrambled) then delete the old/corrupted text so it no longer appears in your document. If you do that, the problem appears to go away (it does not repeat itself with the new text you manually typed, so long as you didn't enter it directly into the corrupted paragraph). If you do that, the new/uncorrupted text can effectively take the place of the corrupted text (thereby preventing future sentences from getting scrambled). It's a bit of a hassle, but it works for now. Also, if you can identify the exact characters that get mixed up when you use "Save As," you can type just those characters into a normal part of your document (the part that is not corrupted), and then you can copy-paste your clean text over the spaces that keep getting scrambled. Once I've done that for all the corrupted portions of my document, I should theoretically be cured of this problem (yay!). If someone comes up with a better solution, though (or can explain exactly why this is happening), I'd love to hear your thoughts.

***Moved from: Office / Word / Microsoft Office Programming / Office 365 Home ***

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2017-11-06T11:46:39+00:00

    Hi Justin,

    Please use Word for Mac 15.39 as the issue doesn't occur in this version. It's recommended that we should keep our Office applications up to date.

    If the issue occurs again, please let us know.

    Regards,

    James

    0 comments No comments

8 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-10-31T19:40:27+00:00

    Update #4:

    I've copied and pasted the text of my novel into a new document. In the process, I lost a lot of the tracked changes (basically, the only thing that transferred over were the comment balloons in the side bar), but that's fine since I can always share the old version with my publisher if they want to see what changes I made prior to cleaning the file by dumping my text into a new document.

    It's still a bit early in the process, but I've been fixing the corrupted text (I've lost two days of writing on this by now, not counting the time I've spent fixing this same problem on other days), and I'm hoping that these changes will be permanent. One thing that may help is always saving the current version of my document (with revisions) before I use "save as" to create a new version of my document, because then I will have a previous version to revert back to that has all of my edits prior to getting corrupted (when I do revisions and then immediately use "save as," I risk losing those revisions through a repeat of the aforementioned text-scrambling-corrupted-file problem). Hopefully, updating to the latest version of Word and pasting my text into a clean (uncorrupted) document will prevent further problems from occurring...because I would really, really, hate to have this problem reoccur in a few weeks when I am turning in my revised book to my publisher and they notice my document has a score or more of paragraphs that look like I was typing while inebriated. :(

    0 comments No comments
  2. Anonymous
    2017-10-31T10:56:40+00:00

    UPDATE #3:

    The new edits that I made in the updated version of Word (to test whether v15.39 has this problem) did not get corrupted. This surprised (and delighted) me, but then I noticed some previous text (that I thought I had fixed) had become corrupted again. I wasn't sure if this was the result of something that had happened recently (in v15.39) or something I did not catch last night when I was doing revisions (in v.15.37, when I thought that I had found a viable solution to the problem), so I went back a few versions and, sure enough, my changes (from writing in a different part of the document and then copying and pasting that "clean text" into the same space once occupied by the "corrupted text") were only temporary.

    Having said that, it appears that, in one instance where I previously had four corrupted paragraphs of text, I now only have a single paragraph of corrupted text. So perhaps it did work, but I had left a corrupted character somewhere in that paragraph (a space or a quotation mark or something less noticeable), and that single corrupted character corrupted the entire paragraph (but not the other three, which I apparently edited correctly).

    In any event, I did a quick minor revision to my text to see if I still needed to copy and paste "clean characters" from a "clean paragraph" if I wanted the changes to persist and not revert or get corrupted again, and it appears that the revisions/edits in v.15.39 are persisting and remain uncorrupted. I'll see about copy and pasting the text of the whole document into a new document and then I'll test to see if any issues persist.

    0 comments No comments
  3. Anonymous
    2017-10-31T10:30:37+00:00

    Thanks, James. This morning, I downloaded the most recent version of word, so this is what version I had been using before (v. 15.37):

    And this is I am now using now v.15.39:

    I'll do a quick test with this new version to see if the problem persists. If so, I'll try copying and pasting the text from my novel into a new .docx file.

    0 comments No comments
  4. Anonymous
    2017-10-31T09:03:56+00:00

    Hi Justin,

    As you mentioned "After some further testing, I've come to the conclusion that none of the new text is being corrupted (only the old paragraphs that needed to be revised).", if the issue doesn't affect new documents, please copy the contents to a new document to check whether the issue remains.

    Meanwhile, please provide a screenshot of your Word version number (click on "Word" tab > "About Word").

    Regards,

    James

    0 comments No comments