It appears that the problem may be caused by GitHub. Its default is to
change line endings to suit the platform. The behavior can be modified with
a .gitattributes file so we are fiddling with that now.
We switched to it last week because BitBucket/SourceTree became unusable on
Windows. They didn
On Sun, 15 May 2022 at 07:24, Turtle Creek Software
wrote:
>
> We just started moving a Mac project to Windows.
>
> When reading text resources into a QString, the Win version automatically
> replaces all /n line endings with /r/n. That screws up our line parsing.
Shouldn't it be the other way
We just started moving a Mac project to Windows.
When reading text resources into a QString, the Win version automatically
replaces all /n line endings with /r/n. That screws up our line parsing.
The code creates a QString from QFile:readAll(), and the change happens
somewhere in that constructo
