Only a Cosmetic issue, but we could certainly fix that. It looks like the issue was introduced way back in 2011 when our Chinese developer used Visual Studio to re-save the resource file which caused a bogus conversion from English encoding to Chinese encoding.
|