How can I preserve the whitespace formatting when migrating a ReqPro baseline to Doors NG?
![](http://jazz.net/_images/myphoto/1760c4aa208ca1bee0161b381428cdf2.jpg)
Hi,
I am assisting a customer to migrate their RequisitePro project to Doors NG.
They have a lot of requirements in which the Primary Text has formatting using whitespaces (i.e. Tabs and Mulitple blank spaces) - for example they have psuedo code:
Also, I have noticed that with DNG 5.0.1, the CR/LF is also lost, and so the above code appears on a single line.
However, with 5.0.2, the CR/LF is at least preserved, which makes it a little easier to read.
I have experimented a bit with the encoding of the ReqPro baseline XML files, and have found the following:
I am assisting a customer to migrate their RequisitePro project to Doors NG.
They have a lot of requirements in which the Primary Text has formatting using whitespaces (i.e. Tabs and Mulitple blank spaces) - for example they have psuedo code:
When migrating to DNG Rich Text, all the whitespaces are condenced into a single space, and when printing this to a Word Document Report, it becomes difficult to read without the formatting.IF Condition is TRUE [space][space] AND Another Condition is FALSE
[tab]THEN Do Something
[tab][tab] ELSE Do Something Else
Also, I have noticed that with DNG 5.0.1, the CR/LF is also lost, and so the above code appears on a single line.
However, with 5.0.2, the CR/LF is at least preserved, which makes it a little easier to read.
I have experimented a bit with the encoding of the ReqPro baseline XML files, and have found the following:
- Encoding multiple space sequence with the ascii code ( ) preserves the sequence of spaces in DNG
- Encoding tabs with its ascii code (	) does NOT preserve the tab in DNG (I presume because it is not a supported char in DNG Rich Text?)
- Converting the tab characters to muliple ascii encoded spaces, improves the result but does not comletely preserve the indents from ReqPro
My question is: Is there any way that we can preserve all the formatting during the migration without having to post-process the Baseline XML's?
A second question would be: Is it possible to instert Tab characters in DNG Rich Text, or do we have to use multiple spaces?
Thanks,
Sudheer
Accepted answer
![](http://jazz.net/_images/myphoto/1760c4aa208ca1bee0161b381428cdf2.jpg)
Did you try to apply iFix005 for 5.0.2 which should also take care of the space issue:
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=91981
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=91981
Comments
![](http://jazz.net/_images/myphoto/1760c4aa208ca1bee0161b381428cdf2.jpg)
Hi Håkan,
Thanks for the quick response!
I did not try iFix 005, will do so now.
Regards,
Sudheer
![](http://jazz.net/_images/myphoto/1760c4aa208ca1bee0161b381428cdf2.jpg)
The iFix005 did the trick!
Although, the text that had tab characters still does not look 100%, but it is nonetheless still readable.
![](http://jazz.net/_images/myphoto/2a15e9d3f97c62c87a3e9aaf1f249bf6.jpg)
We are having the same issue in DNG 6.0.2, only we are importing primary text from Excel, not ReqPro. All leading spaces are getting stripped out on upload.
Do we need to open a PMR on this?