Your Mac problems solved by Luis
I wish to share files stored on my NAS between my Mac and a Windows PC. When I use TextEdit (set to plain text) to view text files made in Windows there are no problems, but that's not the case when looking at files made on the Mac in a Windows text editor.
The best compromise on the PC is to use WordPad. Notepad really upsets the formatting and you can see many of the operators that shouldn't be visible, so it’s almost unusable. WordPad also shows some of these operators. For example, double spaces (or more) and £ symbols are preceded by A with a circumflex; apostrophes are three unwanted symbols but there’s no apostrophe; and there may be others. Does TextEdit have some (maybe not so obvious) settings that would improve its compatibility with Windows text editors, or should I switch to something else? Stephen Bishop I’ve spent an hour now trying to reproduce this phenomenon, with no success. I can create files in TextEdit with plain text formatting and, whether I save them using UTF-8, UTF-16 or Windows Latin, they display just fine in Notepad. You probably have some strange encoding in your original source files on the Mac. I’m betting this doesn’t happen if you just create a new plain text document in TextEdit and then open it in Notepad.
The challenge is to find a simple way to strip the hidden formatting from your existing files. Have you tried opening them in WordPad and then saving them as plain text? Do you actually need them to be in such a primitive file format? If this is just a question of compatibility, RTF (rich text format) is well-supported on both systems.
email@example.com Macs don’t need third-party security apps, and generally run better without them. Rich text format maintains basic text formatting when moving between Mac and PC.