Newline should be added after "\n" in test data

[yanne]

Originally submitted to Google Code by janne.t.... on 27 Aug 2008

In order to achieve this, "\n " should be replaced with "\n\n". Currently, this is done for documentation in a hackish manner.

[yanne]

Originally submitted to Google Code by pekka.klarck on 26 Jan 2009

The main focus of 0.13 release is enhancing support for variables. These our out of the scope.

[yanne]

Originally submitted to Google Code by pekka.klarck on 12 Mar 2009

The original documentation isn't that clear so I clarify it here. The idea is that if test data has a literal '\n', a newline is added after it automatically. This should be done both when the data is shown in the UI and when it is written into file, and applied both for keyword arguments and settings like documentation.

For example, instead of having

Hello\nworld!

there should be

Hello\n world!

[yanne]

Originally submitted to Google Code by vesa.kur... on 20 Mar 2009

I pumped into propably this same issue when creating test data with RIDE ? I created: first test [Documentation] | first row\n2nd row
second test [Documentation] | first row\n\n2nd row third test [Documentation] | first row 2ndrow

And none of them worked. All of them was created with Robot IDE and it just shows the \n literals in two first ones. No new lines to outline documentation more better. Third one, when created looks nice in RIDE, but when opening created tsv file again "2ndrow" is interpreted as keyword :-)

Is this caused by this same issue or is this new one. I have tens of keywords which I'm creating dynamically with python into tsv file, as a template for users to edit them and documentation for each keyword is wuite long and I want to outline it more clearly with linefeeds.

[yanne]

Originally submitted to Google Code by janne.t.... on 20 May 2009

A partial (at least) solution is committed in r346. This works by inserting <br> after each newline, both when shown in IDE or serialized.

I am not quite sure is there a way to support this in tsv?

[yanne]

Originally submitted to Google Code by pekka.klarck on 22 May 2009

This cannot be done in TSV when it is saved because our parser expects real newlines always to be row separators. But newline should be shown after \n in the UI regardless the data format.

[yanne]

Originally submitted to Google Code by janne.t.... on 22 May 2009

Well, this issue is then done.