-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
3.3.0, 3.5.1, 3.11.4, 4.5.2
-
14
-
Severity 3 - Minor
-
5
-
Problem description:
In some cases, based on the file content (aka file encoding), Bitbucket server displays the Umlaut and other non-ASCII characters as either a diamond <?> or another character found in the Russian alphabet. The <?> is usually seen when a non UTF-8 file encoding such as Latin 1 is used without diff transcoding. The incorrect character is normally seen when diff transcoding is on.
How to reproduce:
Push the attached repo to bitbucket server and view the diff between master and the german-changes branch.
Things to be mindful of
- Git offers a RAW mode for some commands which can simplify line ending problems
- Encoding detection should be done once per file
- I had to pass iconv the '-c' option to force it to skip conversion of the euro sign in the file.
- is duplicated by
-
BSERV-8501 Bitbucket has trouble viewing files with UTF-16
- Closed
- is related to
-
BSERV-7871 BitBucket Server (Stash) isn't able to transcode non UTF-8 specifically on README file
- Gathering Impact
-
BSERV-8799 PDF files not always handled as binary files
- Gathering Interest