The text TOP docs discuss that instead of using \n you should use python syntax, but instead of an example, gives a link to a long doc about unicode escaping.
I tried all sorts of stuff from that - U+000D, \u000d etc etc but nothing worked.
Do you mean the parameter called Legacy Parsing? It’s worded funny but says you should use
\t and \n in Python strings, and that the previous [] and {} syntax should be in a specification dat now.
Yep. I was on Mac at the time though - it may be a 099 or Mac thing if that’s how it’s meant to work. But still - the docs seem to imply that if
Legacy parsing is off there’s another method and the \n won’t work. If they are meant to work the docs still need a tweak.