• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 1888 views
  • Users 0 members are here
Options
Related

Working with Idiom-converted package files in Japanese

Yukihiko Okada

I have an agency that gives me Trados packages (wszx and sdlppx) converted from Idiom WorldServer packages (xlz). I use tow computers running Windows 7 and 10, and two Japanese input editors (Microsoft IME and ATOK 2013). I have been having mysterial issues as I describe below.

With Win7 machine, when predictive typing (type the first part of a word and M-IME or ATOK suggests a whole word) kicks in, an error occurs. With Microsoft IME, I can use it as long as I ignore the "prediction" and keep typing till the end of a word. With ATOK, an error happens and I need to click OK to continue. 

Either case, once the error occurs, kitting the End key takes the cursor to one character before the end of the line, not at the very end of the line.

With Win10 machine, I can type when I first use a package file. However, as soon as an error occurs, I can do nothing with Trados. The only thing I can do is to use TaskManager to end Trados. Once this happens, after I re-launch Trados, as soon as I hit any key to type, the error occurs and I need to end Trados using TaskManager. 

The error message is: Attempted to read or write to protected memory. This is often an indication that other memory is corrupt.

So, in short, I can work with Win7 + Microsoft IME with some inconvenience. Nothing else works. 

My Trados works fine with any other file. The only problematic files are those converted from Idiom.

Does anyone know a solution?

Thank you.

Yuki

 

 
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hello Yukihiko Okada (YukihikoOkada),

     

    First of all I would manually check that your Windows versions are both up to date and that the updates have been applied.

    And then check that the correct language packs have been installed (sometimes the error message maybe thrown because of an unsupported font type- so worth checking).

    I seem to recall some issues with Windows language packs and the ISO coding that may be behind this problem.

    blogs.technet.microsoft.com/.../

    Next... is to ensure that both Studio and MultiTerm are both up to date

     

     

    Then Add Studio to your AntiVirus exclusion list (example as follows)

    https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0030929t

     

    Now reboot the PC and restart Studio.

    Has this now resolved the problem?

    Lydia Simplicio | RWS Group

    _______
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Lydia Simplicio
    Hi Steven,

    Thank you for your reply. Not many people are in this situation and I was almost giving up hope.

    Now, everything is up to date. However, I need some more clarification and instructions on what you mean by correct language pack and how to check it. My Win7 is Professional, and Win10 is Home. If I enable Japanese and I can type it, is it not enough? (I know I needed some additional setting to let some Japanese applications display Japanese in their UI for Win7. I still have to do it for my Win10 machine as some applications display garbled characters.)

    Your link to "Add Studio to your AntiVirus exclusion list" was outdated (no page exists). But I found a similar (I think) information on McAfee that I use:
    service.mcafee.com/.../articleview

    I found Trados Studio so I Edited to Open to all devices.

    I tested the Trados behavior on Win7 machine. I entered Japanese to an already translated package and no problem happened. I will see it again with a fresh package when one comes.

    With my Win10 machine, I opened a package that I already had the problem. I started to enter Japanese and the same problem still occurred immediately.

    I then opened a new package and entered Japanese. No problem for the first two segments. I will see how it goes as I work on a new package later.

    Could you explain what I am doing by editing the McAfee firewall permission list for Trados Studio to Open to all devices? I hope I am not exposing my machine to possible attacks.

    Yuki
  • 0 in reply to Yukihiko Okada
    Hello @Yuki,

    It would be good to know how you get on with the new projects and whether the problem persists or is now indeed eliminated.
    If problems still occur, can you let me know the exact version of WorldServer/Studio you and your client are using please.
    Also please provide the 'error stack' as this can help us locate where the issue lies.

    When you add Studio (and MultiTerm) to the AV 'whitelist'- you are just confirming that these specific programs are safe to use and that the AV does not assume a certain file/command/exe contained within is a 'danger'.
    The AV will still continue to function as normal with anything that is not Studio related etc.

    Lydia Simplicio | RWS Group

    _______
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Lydia Simplicio

    Hi Steven,

    Thank you. A new, small package came from my client and I just worked on it on my Win10 machine.

    I first used ATOK. It was going all right in the beginning. However, I got an error and I could no longer type anything using ATOK. One thing that is different than before was I could close the error message, and I did not need TaskManager to close it and Studio.

    I was able to switch to Microsoft IME and keep typing. It again was going all right for a while but I encountered the same error. I was able to close it, and I was able to switch back to ATOK. It was near the end of the file, and I was able to complete it.

    I saved the error messages as xml but I did not record its location and cannot find them now (it is a default location so I can retrieve it if you let me know). The message was the same as the one I first reported. 

    Where do I find the error stack that you mentioned?

    I added Trados Studio to McAfee whitelist, but I do not find Multiterm. What exactly should I add? Is it the Multiterm.exe file under Program Files (x86)?

    Should I also add ATOK and Microsoft IME?

    My Trados Studio version is 2017 SR1 - 14.1.100009.15268

    My Idiom version: 9.0.1.60

    I am asking my client about their Idiom version.

    Regards,

    Yuki
  • 0 in reply to Yukihiko Okada
    Hi Steven,

    Two more packages came from the same client and I tried one of them on Win10 machine with your fix applied. Errors occurred with Microsoft IME and ATOK. I could not type anything.

    I then rebuilt a new project using the components from the package-based project that is almost translated (I used sdlxliff and sdltm). This approach worked before when I used a fresh package (no error occurred). This time, however, the rebuilt project also generated the error and I could not type anything.

    This was the same with project with sdlxliff files from the US_en folder (source) or with sdlxliff files from the JP_ja folder (target).

    So, I ended up translating the same package all over again on my Win7 machine.

    What does this tell you?

    Yuki
Reply
  • 0 in reply to Yukihiko Okada
    Hi Steven,

    Two more packages came from the same client and I tried one of them on Win10 machine with your fix applied. Errors occurred with Microsoft IME and ATOK. I could not type anything.

    I then rebuilt a new project using the components from the package-based project that is almost translated (I used sdlxliff and sdltm). This approach worked before when I used a fresh package (no error occurred). This time, however, the rebuilt project also generated the error and I could not type anything.

    This was the same with project with sdlxliff files from the US_en folder (source) or with sdlxliff files from the JP_ja folder (target).

    So, I ended up translating the same package all over again on my Win7 machine.

    What does this tell you?

    Yuki
Children
No Data