These are JSON escaped characters. /r is the return (U+10) character. /n is the newline character (U+13). It would probably be easiest to replace them with the LiveCode return and linefeed characters.
Peter > On 11 Nov 2014, at 13:49, Brahmanathaswami <bra...@hindu.org> wrote: > > Can someone enlighten me on the > > /r/n/r/n > > that appear in the unicode string that is being delivered (by a PHP database > access lib/api that we post to from this desktop app) > > These are obviously two new lines, the break between verses of the song... > but how do they mix and match with the unicode? Understood somehow as > "low-level" unicode? If I unescape the whole string... (remove all the > slashes) I think I need to leave this in... right? > >> On 10 Nov 2014, at 10:26 pm, Peter W A Wood<peterwaw...@gmail.com> wrote: >> >>>> That is unless mergJSON “de-escapes" the JSON for you. >> >> It should but Brahmanathaswami wasn't using it. mergJSON handles UTF8 though >> so there's no need to have all the escapes. The only char it doesn't like is >> null. >> >> Cheers >> >> Monte > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
