On Tue, Aug 29, 2017 at 8:19 AM, Tim Ward <t...@brettward.co.uk> wrote:
> Entering a newline in a comment as "\n" via the XMLRPC plugin doesn't work > - the comment fails to appear in the ticket (and so far as I can see there > are no error messages in any logs anywhere). > > So I tried the various other ways of entering newlines, such as "[[BR]]", > with weird results. A two line comment with the lines separated by "[[BR]]" > sometimes appears as two lines in the Trac browser UI, and sometimes > appears as a single line with the text "[[BR]]" in the middle. (I didn't > get anything noticeably different, so far as I recall, with "[[br]]" or > "\\".) > > I haven't been able to determine what decides the "sometimes", although it > may have something to do with what string immediately precedes the > "[[BR]]". Eventually I found that putting a space first, so " [[BR]]" > worked insofar as that consistently gives two separate lines in the comment > as displayed in the Trac browser UI ... > > ... but I now discover it sometimes (at least) gives a single line with " > [[BR]]" in the middle in the notification email. > > How, please, can I consistently and correctly > > (1) add a multi-line comment to a ticket via the XMLRPC plugin > (2) so that it displays as multiple lines in the Trac browser UI > (3) and also displays as multiple lines in the notification email > > ? > A code snippet showing the method calls you are using may help with identifying the issue. - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
