Link to home
Start Free TrialLog in
Avatar of birenshukla
birenshukla

asked on

Problem with Microsoft IME on Published Microsoft Word 2010

Hello,

We have a Windows 2008 R2 Application Server running Citrix XenApp 6.5 Rollup 1 with Microsoft Office 2010 32-bit.

One of the users need to type in Japanese using regular IME conversion. This feature works perfectly in Excel, PowerPoint, Notepad, or any other application but Microsoft Word. In Outlook, this works perfectly in any field you type but, of course, not when you create a new message since Word is the default editor.

When I say the feature doesn't work perfectly, I mean that it doesn't happen in a seamless way. Every time you type in Word using IME a gray sidebar appears with the japanese characters being converted. When you press ENTER, the characters are transferred to the document.

This only happens in Word and only in the published app window. If I log on the server and use Word locally, this doesn't happen and the typing is seamless. Word is installed with full feature set.

These are screenshots showing the problem:

1. Published App
http://gyazo.com/1a89fe4a78da820b74df67f09fda580c
 
2. Local Environment
http://gyazo.com/50118605ff1507abc64d2b9bd80860a0


Any ideas on what this can be related to?

Thank you!
Avatar of Ayman Bakr
Ayman Bakr
Flag of United Arab Emirates image

It looks like there is a kind of setting that can toggle this on/off.

I found this link that might be helpful on the issue:
http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/japanese-ime-with-windows-7/5917ab33-00a1-498e-ba5f-6b51a8afce6b
Avatar of birenshukla
birenshukla

ASKER

Mutawadi,

Thank you for your reply. I can change the input type without any issues - and actually what I was using was Hiragana. The problem is that side bar that appears while I am typing. This only happens on the published app window. If I log on locally on the server with the same user it works perfectly fine. And, again, it is only in Microsoft Word.
If you have set a TS profile, then logging on locally with the same user, will actually log with a different profile. I am sure, there is a setting within the profile which is causing this behaviour. The side bar should be programmatically developed, otherwise it will never appear that way; i.e. it is not a kind of error. Hence, when I said that there must be a setting which can toggle it on/off. Perhaps you can check it as follows (I am not sure because I don't have it):

On the IME Language Bar click on Tools > Properties > On the IME properties go to the 'Editing' tab and check for any setting that can toggle this off. If you can't find it, then check it in the 'Conversion' tab (basically check all tabs).
Mutawadi,

Thank you again for your reply. In our environment, both Profile and RDS Profile point to the same profile folder. We did, however, copy the local profile to make sure this wasn't profile related. We double checked all settings on IME to match exactly the same settings we have when it works properly.

I may be wrong, but if this was related to IME shouldn't it happen to all the applications instead of only Microsoft Word?

Again, thank you!
I may be wrong, but if this was related to IME shouldn't it happen to all the applications instead of only Microsoft Word?
That might seem logical, however you need to consider how the IME is working in the background (perhaps keeping different setting customizations for different applications!); or maybe there might be a kind of conflict with a certain application causing the 'ill-behaviour'.

I can't be of more assistance. Hope somebody might come with a valuable input.
Over the past weeks we could narrow down exactly where the problem was. The responsible for displaying the "Finalize String" box is the Language Bar, not Microsoft Office. The reason it only happens on Microsoft Word is unclear.

We were able to reproduce the problem on a test account, which was fixed after the profile was created again from scratch and the Japansese language was added to Word 2010 after the Keyboard and IME are added. However, performing the same steps on the user's account did not work.

We contacted Microsoft and I will provide updates here as we make progress.
Just as I expected; Word was not to be blamed here. Good luck in your quest!.
ASKER CERTIFIED SOLUTION
Avatar of birenshukla
birenshukla

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Microsoft assisted answer.