Description: I did editing changes and tracked them and saved the file in RTF format. But now I don't think RTF format supports tracking edits. And it ended up corrupting and destroying the file. If RTF format doesn't support tracking changes, it shouldn't let the user do it. Maybe just a simple check when a person saves a file (1 - Does it have tracked editing changes, 2 - Is he saving it in a file format that doesn't support those changes), that would trigger a Warning to the user. Steps to Reproduce: 1.Make word processing file with added text, copied text, deleted text, and track changes in editing mode. 2.Save file. 3.Close and open it. It may be corrupted so and barely usable. Actual Results: The text remains but the tracked changes confuses it, and thinks some of the text was added or substracted and it is hopelessly corrupted. Expected Results: If saving the file ruins the file, then people shouldn't be allowed to save it in that format. Or at the very least, a warning should be issued ("You are tracking editing changes. Warning, if you save in RTF format you may destroy your file") Reproducible: Always User Profile Reset: No Additional Info: .
Tracked changes being lost after RTF is working as intended, so that part is NOTABUG. But you are also requesting for a warning before saving a file as a certain file format, so I am changing this bug report into an enhancement request.