There’s a special circle of hell for the “This file contains ambigious Unicode characters” overlay on @Codeberg
No, it doesn’t, it uses proper curly quotes and other typographically-correct punctuation in comments and strings.
Thought we’d fixed this in Forgejo but apparently not?
Really making me not want to link to my source code on Codeberg and I don’t want to migrate elsewhere right now when everything else is working so well.
e.g., see https://codeberg.org/kitten/app/src/branch/parameter-objects/examples/markdown-preview/index.page.js
@aral @Codeberg https://codeberg.org/forgejo/forgejo/pulls/2427 is the partial result of the discussion we had internally. Codeberg is only going do this detection in the pull request diff and commit view.