>>>>Sooo this is for curious people :-D
>>>>
>>>>I'm building text that will go in an email. It's very important that all the CHR(10) are functioning properly.
>>>
>>>Then the question is, was the LF char in the output at all? Else it is a problem of the program browsing.
>>>
>>>AAAND do not use TEXT TO with data holding LF only. This is a cool way to loose the information. See https://github.com/VFPX/GoFish/issues/27#issuecomment-1308245572
>>
>>The (in)famous case of crlf is the one case when multiple cooks on the same pot don't necessarily mean you end up with too much salt. The result may contain no salt at all.
>
>No is the safe solution. giggle

If there's no salt, there's nothing to dissolve. So you got solvent but nothing solvable, so no solution. Ask any chemist.
>Anyway, since computers text is an offspring of typewriters, it's logical to have LF and CR separated. :)

Not directly, lineage goes through teleprinters. There you didn't have a single lever which did both (LF by three sprockets on the cogwheel under the lever, CR by pushing the whole drum to the left), but rather two electromagnetic things, one to roll the drum by one line (LF) the other to push it to the left (return the carriage, please). Most of the lower 32 characters of the ASCII set also originate from teleprinters - chr(7) actually rang a physical bell.