Hi Frank,
please have a look.

Target this one for beta2.

FL->Jack: I guess we had this issue already in the past. Was it the
setup application inserting empty paragraphs when using CTRL and LF
why we chose to use LF only?

Nils, as I'm not sure if Jack still works on that, I re-assign this
one to you.

NF->DV: I need some clarification on this. Is it the case that setup
is only able to deal with unix line ends? In this case, I am not able
to change the behaviour before setup supports dos line ends. 

The setup uses the class MultiLineEdit to display the readme/licence
text and that class should support all kinds of lineends.

Jack, do you know why we have done the implementation of the XSLT this
way? Asd Frank mentioned, it is some kind of feature that we deal with
Unix line ends on windows.
Is it (and when yes, how) possible to change the behaviour?

JW-> Unix line end has to be set because the setup routine could not 
handle dos line ends, the setup routine makes blank lines with dos 
CR/LF

NF->DV: As the root cause for the change is within setup
functionality, this issue to you. To support native text formats,
setup has to deal with dos line ends if executed on windows.

Hi Nils,

I've checked the setup again and the setup application still displays
the readme/license text right in both versions whether the files use
lf or crlf. I've modified a readme file in the output directory of the
readme project, delivered it, created an installation set and still
everything looks ok to me.

Hi, may be it's time to change the target...
Greetings, Stefan

Jörg, can you please take a look on this? On windows, the line ends
have to be dos copatible. Maybe Bernd can help out working on the XSLT?

Hi Bernd,

please modify the readme.xsl as discussed.

I modified XSLT script, next build should include fix.

Any hint to test this would be helpfull.

For the license files a perl script has been integrated into the 
build process to modify line ends. 

OF: to check use a text editor that displays wether unix or dos line 
ends are used and load the license.txt and readme.txt file with that 
editor to verify that DOS lineends are used. Additionally you can 
check wether the setup Application can still display the files 
correctly.

OF: reassigned to you for testing

Looks good in CWS readlic

Verified

Is ok in current build.