Detecting language please wait for.......
I have a md file to translate, I'm using Trados2019sr2, so I can process md files, the md file is in Chinese, and when I open the editor and click the preview button, all the chinese characters are garbled;
BTW: It shows the right chinese characters in File - Print & View - View In - Web Browser as Source & Web Browser as Target
Heres some screenshots:
The md file is UTF-8.
It also seems to have the wrong chars compared to the source. For example:
Can we see the source file? You can send this to email@example.com if it's ok to share it.
Just send it via email. thanks.
Thanks Xiang Li
So I think we can rule out a general problem in Studio:
I'm not sure what could cause this to be honest as I don't know what technology we use for previewing MD files (will find out though!). In the meantime perhaps Adrian Maniu might have some idea if he has time to review this thread. Otherwise I'll have to come back to you after the weekend.
I have spoken to the filetype manager responsible for the development of this and the only thing he could add is that he thinks it's an encoding issue and he doesn't know where else to look.
I think we know it's an encoding issue, but we don't know why it's affecting you and not me. If you're using a different UI language can you try switching it to English and see if this makes any difference?
Can you tell me if you're using a specific language pack with Windows rather than English?
Can you also make sure you have the latest versions of Internet Explorer installed on your machine?
I'm really guessing I'm afraid. I was hoping the developer might be able to give me something to help diagnose this problem you're having.
The UI of Trados2019 is in Chinese, the chars still garbled in English Windows.
I'm using the Windows 10 and I have instlled the latest version of chrome. the version of IE is 11.
I also think it's an encoding issue, but no matter how I change the encoding, the issue still shows.
Xiang Li, can you clarify the Studio version (Help > About SDL Trados Studio)? We had a defect about similar issues which was solved in SR2 CU4: