Skip to content

Fix UTF-16LE line endings in dni/ini files #708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
mike-clark-8192 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix UTF-16LE line endings in dni/ini files #708

mike-clark-8192 wants to merge 1 commit into from

Conversation

@mike-clark-8192
Copy link

@mike-clark-8192 mike-clark-8192 commented Jan 9, 2026

  • Three files had corrupted single-byte CRLF (0d 0a) mixed with UTF-16LE content, breaking git's working-tree-encoding conversion
  • Corrected to proper UTF-16LE CRLF (0d 00 0a 00) so files round-trip correctly through git

@mike-clark-8192
Fix UTF-16LE line endings in dni/ini files
bf5ae67 
- Three files had corrupted single-byte CRLF (0d 0a) mixed with UTF-16LE content, breaking git's working-tree-encoding conversion
- Corrected to proper UTF-16LE CRLF (0d 00 0a 00) so files round-trip correctly through git
@RamonUnch
Copy link
Owner

RamonUnch commented Jan 17, 2026

I cannot find the single word 0D0A in AltSnap.dni file nor in fr_FR.ini, However ko_KR.ini seems to be utf-8 encoded.

It seems you are actually converting to UTF-8 some files?

I do not understant what github is doing with encoding, maybe I should remove the .gitattributes flags, and treat those files like binary blobs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mike-clark-8192 @RamonUnch