Invalid text data when exporting as binary files - text mode
Your hex view shows the ASCII value for each byte in the file. However, the file appears to be saved as Unicode (it starts with FF FE, which is a Unicode specification). Usually text editors will correctly identify this specification (Notepad does the same as Notepad ++, I'm not familiar with Textpad).
Note that hex viewers are almost universally used. a character representing a byte value that cannot be displayed as an ASCII character (or a character from the OEM user set).
The actual encoding looks like unicode for example. 33 00 and 36 00 are numeric digits, although they represent 36 not 78, so the ASCII representation on the right in your question does not actually match the byte values ββon the left.
Line: - "78,45, N" when saved as a Litte-endian unicode file will look like hexadecimal: -
FF FE 37 00 38 00 2C 00 34 00 35 00 2C 00 4E 00..7.8., 4.5., N.
Hence, either the content saver is very strange and messes up the encoding, or the Textpad just doesn't handle it correctly (or you're not using the Textpad on the right). Open the file in notepad, does it look ok?
source to share