Just a quick FYI: the default encoding for text files on a Mac is UTF-8 with no byte-order-marker, with each line terminated by the ASCII NL character (0x10); this has been true for many years. I say this because Microsoft Word is still incapable of opening a UTF8-encoded text file without turning it into garbage, even if I explicitly override the default (wrong) encoding in the dialog. Outlook does some goofy text-molesting as well.
I can, at least, override the default (wrong) encoding in the save dialog, and it will write out the file in UTF-8, but then it will add a byte-order-marker for no good reason, which then has to be edited out. Quoting:
UTF-8 always has the same byte order. An initial BOM is only used as a signature — an indication that an otherwise unmarked text file is in UTF-8. Note that some recipients of UTF-8 encoded data do not expect a BOM. Where UTF-8 is used transparently in 8-bit environments, the use of a BOM will interfere with any protocol or file format that expects specific ASCII characters at the beginning, such as the use of “#!” of at the beginning of Unix shell scripts.
Ironically, the best way to get Unicode text files into Word is to convert them to HTML first…