[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 michael changed: What|Removed |Added Version Fixed In|1.9.4 |1.9.5 --- Comment #6 from michael --- Full fix in 1.9.5 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 --- Comment #5 from Brendon Higgins --- Also noticed (just now) kdiff3 fails to detect the line encoding if the file is UTF-16 with DOS lines. Maybe something is wrong with how this "skipBytes" parameter is handled? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 --- Comment #4 from Brendon Higgins --- I'm tearing my hair out trying to understand why I still see this sometimes. Looks like UTF byte order marks screw up the automatic detection, and the line ending is (incorrectly) assumed to be Unix in that case. If I make two text files with DOS line ending and no BOM, and diff them in kdiff3, it detects those just fine, but if I add BOM to either one, it guesses Unix for that file. So this bug is only partially fixed? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 michael changed: What|Removed |Added Version Fixed In||1.9.4 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/commit/4d6c22c0cf2cc |kdiff3/commit/2b86217c32ed5 |037f08373e12558ce8e49ac836b |15d3a8b308e6194062b4d76be87 --- Comment #3 from michael --- Git commit 2b86217c32ed515d3a8b308e6194062b4d76be87 by Michael Reeves. Committed on 25/10/2021 at 17:43. Pushed by mreeves into branch 'master'. Fix DOS end of line detection FIXE-IN:1.9.4 M +2-3src/SourceData.cpp https://invent.kde.org/sdk/kdiff3/commit/2b86217c32ed515d3a8b308e6194062b4d76be87 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 michael changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/commit/4d6c22c0cf2cc ||037f08373e12558ce8e49ac836b Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from michael --- Git commit 4d6c22c0cf2cc037f08373e12558ce8e49ac836b by Michael Reeves. Committed on 25/10/2021 at 18:09. Pushed by mreeves into branch '1.9'. Fix DOS end of line detection FIXE-IN:1.9.4 M +2-3src/SourceData.cpp https://invent.kde.org/sdk/kdiff3/commit/4d6c22c0cf2cc037f08373e12558ce8e49ac836b -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 michael changed: What|Removed |Added Status|CONFIRMED |ASSIGNED Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 michael changed: What|Removed |Added Version|1.9.0 |1.9.3 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 michael changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442199] DOS line endings are not correctly detected
https://bugs.kde.org/show_bug.cgi?id=442199 Brendon Higgins changed: What|Removed |Added CC||[email protected] --- Comment #1 from Brendon Higgins --- I observe this behaviour also on Linux builds (Debian unstable packages, v1.9.3). Apart from blank lines between every line, I also notice some corruption tends to happen around the second/third/fourth lines (maybe others). -- You are receiving this mail because: You are watching all bug changes.
