You can browse the text content of the file online, but you cannot view the diff of the file.

[yangyangdaji]

Description

When viewing files with certain extensions (e.g. .reg), attempting to view diffs would trigger a "Binary file not shown" warning, indicating that binary file diff rendering is not supported. however, these same files display their text-based contents normally when viewed directly online.

Example

https://gitea.com/yangyangdaji/PeaZip/src/branch/sources/peazip-sources/res/share/lang-wincontext/chs.reg

Diff Warning Screenshot

Screenshot of Text Content View

Gitea Version

1.24.0+dev-319-gbc29c02e26

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

https://demo.gitea.com

Database

None

[yangyangdaji]

@lunny 抱歉打扰你，我尝试过都失败了，好失落。GitHub 不支持， 导致仓库维护者也不接收。peazip/PeaZip#156 我觉得 Gitea 我也不知道从何下手，因为这是 Git 原生的问题

即使有好心人帮忙，我也没法完成这个事，你可以看看这个：sourcegit-scm/sourcegit#1652 Git 本身不接受这东西，你可以看这里： git-for-windows/git#5078

所以作为 Gitea 用户，我希望 Gitea 可以解决这个痛点。我当时用的是英语机翻（没有 AI 翻译），可能语气不太好，你可以随意更改。

[lunny]

Please speak English.
Can it work after add working-tree-encoding=UTF-16LE-BOM to .gitattributes file?

[yangyangdaji]

Please speak English. Can it work after add working-tree-encoding=UTF-16LE-BOM to .gitattributes file?

no see yangyangdaji/PeaZip@6746ec0

He destroyed the file

Some won't even show

https://github.com/yangyangdaji/PeaZip/blob/6746ec0b008eb5ec06e6c2d7a895d6af2009262f/peazip-sources/res/share/lang-wincontext/chs.reg

[yangyangdaji]

Please speak English. Can it work after add working-tree-encoding=UTF-16LE-BOM to .gitattributes file?

no see yangyangdaji/PeaZip@6746ec0

He destroyed the file

Some won't even show

https://github.com/yangyangdaji/PeaZip/blob/6746ec0b008eb5ec06e6c2d7a895d6af2009262f/peazip-sources/res/share/lang-wincontext/chs.reg

To fix these problems, need to re-add the original files.

[yangyangdaji]

If you submit a PR, this is what happens: you can’t merge it, or you use git merge. But I’m not an admin, not push upstream, I'm not sure why Git is behaving this way.

[yangyangdaji]

Reinstalled Git and redid the process. Files work fine now, but git diff won't show up.

yangyangdaji/PeaZip@ba0b761

If unchanged, it still reports as binary.

There are some additional tests. Please ignore them. aka sv.reg

[yangyangdaji]

Reinstalled Git and redid the process. Files work fine now, but git diff won't show up.

yangyangdaji/PeaZip@ba0b761

If unchanged, it still reports as binary.

There are some additional tests. Please ignore them. aka sv.reg

If this issue ain't fixed, I'm honestly too chicken to send a PR. Tried once, got revert; second time, got the boot. Now I'm just freaking out about it. see peazip/PeaZip#156

[yangyangdaji]

@lunny I set up a test repository. Here are the files before any operations were performed:
https://github.com/yangyangdaji/git-reg-test

I noticed that if you add a configuration file and enable this configuration, it might not take effect for all files (git diff shows no file differences).

yangyangdaji/git-reg-test@7651d1a

On top of that, changes made to specific files won’t show up either:
yangyangdaji/git-reg-test@1491ad0

Locally, I used git reset --hard to forcefully roll back to the state of the last commit, and something really strange happened. I use SourceGit (a Git GUI tool), and it prompted me that there was a local file with uncommitted changes. It turned out to be 2.reg. I tried to commit it, but ran into issues. Then I tried to discard the changes, and that failed too.

Log:
 

$ git add .
fatal: failed to encode 'git-after/1.reg' from UTF-16LE-BOM to UTF-8

$ git restore --worktree --recurse-submodules --pathspec-from-file="C:\Users\my\AppData\Local\Temp\tmp033wvz.tmp"
error: failed to encode 'git-after/2.reg' from UTF-8 to UTF-16LE-BOM

Here’s the link to the files related to this issue:
https://github.com/yangyangdaji/git-reg-test/blob/main/git-problem/git-problem-reg-files.7z

I have no idea why Git is acting like this. I see the previous issue still hasn’t been fixed to—could you take a look?

[yangyangdaji]

git-for-windows/git#5078 (comment) can solve this fixed. But why isn't Git configured by default, no manual says this.and this bug hasn't been no fix for about a year?