[Do...] Posted January 20 Share Posted January 20 Hi all, We have a few sites overseas and are collaborating with them on a data collection project for MSM parts. We typically use the characteristic file generated by Calypso for our analysis internally. With this project, however, we are encountering errors pertaining to their respective languages (Korean and Japanese). It appears that either Calypso, Windows or Excel are having trouble populating text entries in the correct language format. The issue is currently twofold. Our sister site provided us a copy of both a CMM report and a characteristic file. The Korean font is legible on the CMM report, but is converted into symbols within the characteristic file. When trying to generate a similar report here in the U.S. (having changed both Calypso and Windows to Korean and installed the language pack), neither one of the files have a legible font and both are converted to symbols. Is there something I am missing or is this a known issue without resolution? Cheers, Don Link to comment Share on other sites More sharing options...
[Ky...] Posted January 23 Share Posted January 23 When you say a "Characteristic file", do you mean the characteristic table file? If so then likely whatever text viewer you are using is having issues with the Unicode used for the Korean or Japanese scripts. How you would handle that would be dependent on the program you are using to view it and you (read "your IT") will have to figure it out. The CMM Report (PiWeb?) is probably working since it's probably a PDF file. If the characteristic file you are talking about is a CALYPSO inspection program, Then I think Calypso should be able to handle Unicode. I'm pretty sure I've seen it work before on some programs. There is a translation license you can get, depending on the version, but that's for translating the UI, not the individual features or characteristics, etc. Let me know what you mean exactly. If you can show an image or something of what you are seeing, that might be helpful. Link to comment Share on other sites More sharing options...
[Do...] Posted January 24 Author Share Posted January 24 Hi Kyle, You are correct, we are using the characteristic table files in this case. These are normally viewed via Excel which is set to the default Unicode setting. By changing this setting to ECU-KR we are able to view the Korean characters just fine. Also to clarify, the CMM report that had been sent to us was the default Excel report from Calypso as well. It seems that for some reason Excel or Calypso encodes these files differently behind the scenes. With that said I think we are able to move forward having figured out the encoding differences. Thanks for your help! Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in