The issue is with other non-printing characters.
Windows, Mac & Windows deals with this differently.
Some only add <carriage return>, <New Line> or Both of them at the end of each line.
"\n" will only get <carriage return>
You can UUEncode the text to get all of the problem characters, then run a SearchandReplace() for each one then decode the text. it is not pretty but it works.
This also work to find and remove Non-printing ASCII, Unicode & emoji Characters which can cause problems.
NOTE: Quickbase HTML processing will modify what is displays on the view form, to see what is actually in the field you must EDIT the record and get the data from the field.
I hope this will point you to the correct information.
