I have a UTF-8 source file with Japanese text in a 3rd-party SCM supported by a LightSCM plugin.
When it is rendered in Crucible, it is displayed with CP windows-1252, so all the text is garbled.
Is there any way in the Crucible plugin framework to control the file (or repository's) character set?
I fetch the source file and write it out as UTF-8 to the OutputStream in com.atlassian.crucible.scm.SCMRepository.getFileAsString
The file also has the UTF-8 BOM 0xEF,0xBB,0xBF.
I'm using 4.5.3 (64-bit) and even tried this old solution to no avail: https://community.atlassian.com/t5/Fisheye-Crucible-questions/UTF-8-support-in-Crucible/qaq-p/448381
Hi @Joseph Koral,
If you did not try this already, can you try setting the sun.jnu.encoding explicitly to UTF-8 in the $FISHEYE_OPTS Environment variables?
This would be the syntax:
We have an open feature request to have this setting enabled by default:
Caterina - Atlassian
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events