Thanks Thomas but as I said in my post "... the only preference I can find (General -> Workspace) that is related says to use the Windows default for new files." So the user already has Windows set.
Also the preference says "... for new files ... " so it shouldn't have any impact anyway should it?
On Feb 24, 2020, at 12:56 PM, Tools/400 <thomas.raddatz@xxxxxxxxxxx> wrote:
Let the client check his workspace preferences in RDi on page "Preferences - General - Workspace". Most likely the client selected "Unix" for the "New text file line delimiter".
Unix uses LF whereas Windows uses CRLF. Notepad does not understand LF. Notepad++ understands both settings.
Am 24.02.2020 um 18:09 schrieb Jon Paris:
Client reported a situation to me today that I have not encountered before.
They have a number of HTML templates in the IFS that were created/maintained by a combination of Notepad and Notepad++
These files have a code page of 1252 (Windows basic).
Client has just started using RDi and when they opened an HTML file it worked fine. They edited the file and saved it back to the IFS.
Later they needed to use Notepad to edit the file, but it now just shows up as one huge line. If they use Notepad++ it looks normal.
Due to the nature of their work they are forced to use Notepad on some customer systems and this creates a barrier to them using RDi.
I know that Win 10 has recently fixed the issue in that it now recognizes multiple line end combinations (as does Notepad++).
What I don't understand is why RDi is apparently changing the line end characters during edit - particularly since the only preference I can find (General -> Workspace) that is related says to use the Windows default for new files.
Anyone seen this or have any idea why it happens and how to prevent it?
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.