Configuring a Different Charset in Fisheye/Crucible
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When browsing source files in Fisheye/Crucible you may find that some characters, usually those written in languages other than English, come through as squares, or unknown characters.
Cause
The default character encoding in Fisheye/Crucible is UTF-8, so if your file is using a different type of encoding than UTF-8 then some characters may not render.
Resolution
Fisheye currently supports changing the file encoding for Perforce, SVN, and CVS.
An improvement request for adding this support for Git and Mercurial can be found at:
FE-3623 - Add option to set default charset encoding for file content for Git repositories
FE-7075 - Support setting Mercurial repository's encoding in the FishEye config
The charset for the repository will need to be changed.
For SVN repositories:
Go to
Administration > Repository Settings > RepositoriesClick on the repository name.
Go to
SCM DetailsIn "Charset" select the character set for your repository and "Save"
This will restart the repository, a re-index will need to be performed manually.
To determine the character encoding of the files the Linux command file <filename> can be used.
Was this helpful?