TextEdit files corrupted on MacBook Air

hi

Another technical question I've never faced before.


Why are plain or rtf texts corrupted within TextEdit?

This has been an ongoing problem as I've found many archived folders the same; and now on MacBook Air docs Ive created in the last twelve months also get 'the rot'.


The meta sometimes shows the proper English type, or in this example a French extract I made for further research- when opening the file the text is (from trying to use the inbuilt translator) Chinese?


Thanks

D~ rhone1


MacBook Air, macOS 15.7

Posted on Feb 5, 2026 7:00 PM

Reply
Question marked as Top-ranking reply

Posted on Feb 6, 2026 2:22 PM

rhone1 wrote:


The supposition of error in translation is just plain wrong sorry.

I was referring to encoding, not translation. "Chinese" (it's just nonsense, not actual chinese language) can happen when a document encoded as UTF-8 is opened by a reading app as if it were encoded in UTF-16. I can create your Chinese by opening the original French in BBEdit with the encoding set to UTF-16LE.


I'm now sure exactly what will fix this at your end. When you use Text Edit in plain text mode to open your document, try going to the bottom where it says Show Options and set the Plain Text Encoding to UTF-8.



6 replies
Question marked as Top-ranking reply

Feb 6, 2026 2:22 PM in response to rhone1

rhone1 wrote:


The supposition of error in translation is just plain wrong sorry.

I was referring to encoding, not translation. "Chinese" (it's just nonsense, not actual chinese language) can happen when a document encoded as UTF-8 is opened by a reading app as if it were encoded in UTF-16. I can create your Chinese by opening the original French in BBEdit with the encoding set to UTF-16LE.


I'm now sure exactly what will fix this at your end. When you use Text Edit in plain text mode to open your document, try going to the bottom where it says Show Options and set the Plain Text Encoding to UTF-8.



Feb 6, 2026 6:39 PM in response to rhone1

Hey Tom,

I don't have a 'Show Options' at the bottom [of page].


I followed your advice and it's a fail- now can't open -

"1-The document “misc.txt” could not be opened. Text encoding Unicode (UTF-8) isn’t applicable.

2- The file may have been saved using a different text encoding, or it may not be a text file."


I alternately use plain txt and RTF- the latter when I have intensive links and/ or illustrations that, if not included, fail context.


NB-- 1221hrs

In fact that change caused all txt to fail with that mode.

I hobbled back to TxE and opened the app without a file first- under Settings reversed what we'd done. In fact I tried Automatic and its worked perfectly.


Every old file I have, yet to check archives, opens in plain text all ok- either English (I sometimes pre-translate before moving to various apps, or French, German or Russian originals. I sometimes find the Apple translations don't work very well- and why oh why it has to re-re- download languages over and over is annoying as ****. Literally from the same site, same language (ie not old French or German) and yet it keeps repeating that.


Anyway, case closed until it happens, another way, I guess!

Thanks,

Dave

Feb 6, 2026 1:47 PM in response to Tom Gewecke

Thanks Tom,

I knew I'd have to but got other work out of the way first.

I'm an historian/ researcher amateur in a special niche and deal now, with an M2 that helps immensely with translation and holding notes for subsequent articles or informational briefings.


The supposition of error in translation is just plain wrong sorry. This file is representative of several archives dating back a decade or more; multiple backups held off-disk but getting 'damaged' on my MB is completely new. I'd previously used Tex-Edit but it no longer supports M hardware.


Meta for txt doc via preview_ Scrx 2026_


  • -

Opened txt doc- Scrx 2026_


So there's the scenario- utility has been corrupted by ???


BTW, neither Malwarebytes nor Bitdefender have flagged any malicious activity or code aimed at the rtf or plain text files.


Thanks for any suggestions.

Dave


Feb 6, 2026 3:15 PM in response to Tom Gewecke

Hey Tom,

I don't have a 'Show Options' at the bottom [of page].


I followed your advice and it's a fail- now can't open -

"1-The document “misc.txt” could not be opened. Text encoding Unicode (UTF-8) isn’t applicable.

2- The file may have been saved using a different text encoding, or it may not be a text file."


I alternately use plain txt and RTF- the latter when I have intensive links and/ or illustrations that, if not included, fail context.

Dave


TextEdit files corrupted on MacBook Air

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.