Crucible third-party SCM plugin renders file incorrectly

[Joseph Koral]

Hi,

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 

[Caterina Curti]

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:

-Dsun.jnu.encoding=UTF-8

We have an open feature request to have this setting enabled by default:

- FE-6908 - Set sun.jnu.encoding to UTF-8 by default

Cheers,

Caterina - Atlassian

[Joseph Koral]

Thanks @Caterina Curti, I have tried that option, without any luck.