CRLF added in content.htm

[olape]

I open the local server (easyphp devserver), I open the local site, go to the admin and modify the template then record the action.

The Local Template.htm file is immediately transformed into CRLF.

This would be correct if you are working under Windows.

The content.htm file previously converted to LF is with an LF/CRLF mix because the part concerned by the article modified to all its lines ended by CRLF.

That is not correct, I think so.
We have not yet observed this or noticed it. I will try it out when I get the chance.

I wonder if we can configure something for a local server -In a Windows environment- to work like a UNIX server

I can't answer that. That would have to be researched.

[ludovicam]

I confirm that I work under Windows 10. I have no other way.

[olape]

I will try it out when I get the chance.

- Original content.htm is delivered with LF.
- local changes under Windows / xampp result in a mix of LF and CRLF
CRLF is only set in the content, not in the Pagedata part and only for the page that was edited.

- however, a CORRECT transfer with Filezilla (ascii mode) corrects that again.
on a Linux server, EVERYTHING arrives with LF.
Conversely, if I then download the file again in ascii mode on a Windows OS, EVERYTHING is CRLF.

Correct FTP transfer cannot be the solution, but it does alleviate the problem considerably.

[ludovicam]

The author of this post deemed useful to delete it.

[ludovicam]

I found a small solution that requires modifying a native function. I therefore do not publish it in case it could lead to "other problems". We never know.

[olape]

This is the simplest path I have found.

OK, let's remember that for now.
So far, apart from you, we are not aware of anyone who has experienced this problem.
This will inevitably be a long-term test for you.

I hope to hear again in the future whether your solution might cause other problems.

[ludovicam]

I hope to hear again in the future whether your solution might cause other problems.

We all hope.
the subject is closed.

[Michael_G]

Hi,

maybe this link can also help:
https://superuser.com/questions/545461/ ... in-notepad

Or short and BTW my experience for years:
Standard line endings: macOS/Unix (LF)

Real good text editors like Notepad++ for Windows and CotEditor for macOS support to choose between:
– macOS / Unix (LF)
– Windows (CRLF)

Every Webmaster using a Linux web server should set this to macOS/Unix (LF) to avoid problems.
Good luck!

[olape]

Real good text editors like Notepad++ for Windows and CotEditor for macOS support to choose between:
– macOS / Unix (LF)
– Windows (CRLF)

Although this is true, it is of no use if someone uses the XH editor to edit page content.

Every Webmaster using a Linux web server should set this to macOS/Unix (LF) to avoid problems.

Linux servers always use LF by default.

There is indeed a problem here at XH, but it doesn't seem to have come into play anywhere yet. In any case, I didn't know anything about it yet.

[Michael_G]

Hi olape,

yes, XH seems to mix “LF” and “CRLF” above a certain content.htm size.

I use macOS and the excellent CotEditor and have often been surprised by its message that the loaded content.htm file complains about "inconsistent line endings" and then always offers to correct them.
I did this and everything worked fine.

But even if I ignored this message from my editor, I had no problems in XH.
My texts were not affected by these incorrect line endings.

I have just loaded the content.htm files (DE|EN) of my small website into CotEditor as a test (â 66 KB)
and then the two content.htm files (DE|EN) of my large website (DE+EN each about 3 MB in size).

* Edit:
Conclusion: all online within XH edited content.htm files are partially modified by XH with unwanted “CRLF”.
I have not yet recognised any logic in this.