Internet Explorer 6 Forum

Hi, since I can't post it on the support forums when I'm using the demo, I will post it here.

I am running Leopard on my Macbook Pro, and I'm running internet explorer 6 on a win98 bottle. On Tiger, the Japanese characters will display correctly when I run CrossOver with "LANG=ja_JP.UTF-8 open -a CrossOver". Now when I run CrossOver with such command on Leopard, the Japanese characters will display as '~' when I go to any site with Japanese characters. Is there any workaround/fix for this?

We are not seeing this issue in our testing on Leopard. There is a different issue, which is that Apple's Japanese input methods are not working with CrossOver. Some third-party input methods might work. We are hard at work on addressing this issue.

If a web site or application is trying to display Japanese characters, then that should work. It's possible that the "LANG=ja_JP.UTF-8 open -a CrossOver" trick no longer works. If you set your system language preference so that Japanese is first in the list (in the International pane of System Preferences), and restart Internet Explorer, does the Japanese then display correctly?

If you use the Run Command dialog to run notepad, does it display its menus in Japanese?

Changing the language order from International panel does work, but that would mean my whole system language changes to Japanese, which is not what I want. I do hope there will be a solution for this.

Also, Korean locale support seems to be broken, which is far more important to me. Changing the language order to Korean on top results in broken characters '~' when visiting a Korean site. Ironically, being in a English locale (or in a Japanese locale) allows Korean language to display correctly, although ugly.

Based on this, I would like to see Korean locale support in a near future, as well as the way to run only crossover with Japanese locale on demand in Leopard, ala the command line way that used to work in Tiger.

For the Japanese locale support, try the following:

LANG=ja_JP.UTF-8 /Appliations/CrossOver.app/Contents/MacOS/CrossOver &

You might also try the third option of this FAQ, although that may also affect some Unix-style programs other than CrossOver: http://www.codeweavers.com/support/docs/crossover-mac/faq#id2501520

We are aware that Korean input support is broken. It's the same bug as what's preventing Japanese input. Leopard changed the way that input methods work, and we're working with Apple to try to figure out a way to get CrossOver to work with them again.

The input was broken on Tiger as well, not just Leopard.

I deleted CrossOver and went back to boot camping at the moment, so I couldn't test out that command. There's just too many problems for me to consistently use, and I am not willing to go back to Tiger. But it does show a lot of promise. I will wait for the next version. Keep up the good work!

I'll install the demo again and try out the command later.

Another note: I noticed that CrossOver 6.2 is currently based on wine 0.9.34, while the latest wine version when 6.2 was released was 0.9.46, and currently the latest version is 0.9.49. Was there a reason why you didn't use the latest version of wine? No significant improvements or too many problems to merit the use?

UPDATE: I just ran CrossOver with the above command and displaying Japanese characters on Internet explorer, as well as Japanese programs, still doesn't work correctly ('~' charcters on Japanese characters). Same goes for Korean characters as well when LANG is set as ko_KR.UTF-8. Here is the output that I got:

jwnotebook:~ jaewkim84$ 2007-11-19 10:04:26.269 CrossOver[2167:10b] Setting DYLD_FALLBACK_LIBRARY_PATH=/Applications/CrossOver.app/Contents/SharedSupport/X11/lib:/Users/jaewkim84/lib:/usr/local/lib:/lib:/usr/lib
2007-11-19 10:04:31.862 CrossOver[2167:10b]
6.2

Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Mac OS X Apple Computer, Inc.
Current Operating System: Darwin jwnotebook.local 9.1.0 Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386 i386
Before reporting problems, check http://www.codeweavers.com/support/
to make sure that you have the latest version.
Could not find keymapping file USA.keymapping.
Reading keymap from the system.
XSERVTransmkdir: Owner of /tmp/.CrossOver should be set to root
Loading GLX bundle glxCGL.bundle (using Apple's OpenGL)
Display mode: Rootless Quartz -- Xplugin implementation
PseudoramiX screen 0 added: 1440x879 @ (0,21).
PseudoramiX screen 0 placed at X11 coordinate (0,0).
[DRI] screen 0 installation complete
Screen 0 added: 1440x879 @ (0,21)
Screen 0 placed at X11 coordinate (0,0).
dyld: warning, DYLD setting caused circular dependency in /Applications/CrossOver.app/Contents/SharedSupport/X11/lib/libGL.dylib

The third option of setting the environment file on /.MacOSX/environment didn't work as well with same results.

Just to let you know, I have installed some patches from http://www.x.org/wiki/XDarwin site. I also installed xterm with unicode support on that site. None of them made any difference with stock X11 stuff.

Everything used to worked as intended on Tiger when LANG environment variable was set. So my only suspicion is with Leopard's X11. I don't know how much it is affecting CrossOver as you are implementing your own X11 solution, but Leopard's X11 is quite broken if I dare to say so, and it seems like it is affecting CrossOver as well to some extent.

solgae wrote:

The input was broken on Tiger as well, not just Leopard.

Hmm. Input using Japanese and Korean (and Chinese) input methods should work with CrossOver 6.2 and Tiger. Japanese is especially important to us, because we have a major distributor in that market.

Another note: I noticed that CrossOver 6.2 is currently based on
wine 0.9.34, while the latest wine version when 6.2 was released was
0.9.46, and currently the latest version is 0.9.49. Was there a
reason why you didn't use the latest version of wine? No significant
improvements or too many problems to merit the use?

Wine changes frequently. One would hope that the changes would always be for the better, but it isn't always so. Since we have to offer support, we need a stable baseline to test and tweak to maximize our level of compatibility. If we were to keep constantly up-to-date with Wine, all of our testing would be invalidated every two weeks, and we would never quite be sure what exactly we were shipping to our customers with a promise of support.

We have been following a pattern of staying on one version of Wine for two of our releases, then jumping forward to current Wine as we work on the next release. As we come closer to finalizing our next release, we'll have to freeze our version of Wine again, so it will not quite be totally cutting edge when we release, but it will be a lot further along than our current Wine.

So, 6.1 and 6.2 were both based off of 0.9.34. Don't think though, that we made no changes to Wine between those two releases. We pull in important fixes on an individual basis. Since we're some of the primary contributors to Wine, a great deal of the Wine changes between 0.9.34 and 0.9.49 were fixes we developed for 6.2 and committed to Wine along the way. CrossOver 7.0, which we hope to release in January, will be based on some version of Wine that's roughly current. We don't know exactly when we'll freeze the Wine which we'll include.

UPDATE: I just ran CrossOver with the above command and displaying
Japanese characters on Internet explorer, as well as Japanese
programs, still doesn't work correctly ('~' charcters on Japanese
characters). Same goes for Korean characters as well when LANG is
set as ko_KR.UTF-8. Here is the output that I got:

[... snip ...]

Did you try the experiment with running Notepad using the Run Command item of the Programs menu?

I had a thought as to why the command-line setting of LANG does not work, but setting your language in the International pane does. In fact, I think it explains all of your symptoms. There have been two relatively recent changes:

First, CrossOver 6.2 introduced our enhanced Dock icons for your Windows programs. This means that CrossOver no longer is the immediate parent of the Wine process which is running your Windows program. Instead, CrossOver asks the Launch Services subsystem of the OS to launch the helper application, and that application is the parent of the Wine process.

Second, Leopard changes the behavior of Launch Services. The newly launched application is not a child process of the CrossOver application process. Instead, Leopard's Launch Services communicates the launch request to a different process (launchd) and that process is the parent. One of the consequences of this change is that the new application does not inherit its environment from CrossOver. It gets a fresh, plain environment inherited from launchd, which does not include your LANG setting. (This is also why setting LANG and then invoking the "open" command won't work. The open command uses Launch Services, too.)

So, here's my new theory about what will work: if you launch CrossOver with the LANG variable, and then only use Run Command to execute Windows programs, that should work. Alternatively, you should be able to do something like:

LANG=ja_JP.UTF-8 ~/Applications/CrossOver/Internet\ Explorer.app/Contents/MacOS/CrossOver\ Helper\ with\ Feedback &

In other words, you would launch the helper application with the LANG variable directly, not CrossOver.app.

The third option of setting the environment file on
/.MacOSX/environment didn't work as well with same results.

The one thing that my new theory doesn't explain is why setting LANG in ~/.MacOSX/environment.plist didn't work. Two things: 1) I notice that you did not include "~", above. (You are not missing ".plist". That should not be included in the command from the FAQ.) 2) Did you log out and back in, after setting the variable?

Just to let you know, I have installed some patches from
http://www.x.org/wiki/XDarwin site. I also installed xterm with
unicode support on that site. None of them made any difference with
stock X11 stuff.

Everything used to worked as intended on Tiger when LANG environment
variable was set. So my only suspicion is with Leopard's X11. I
don't know how much it is affecting CrossOver as you are
implementing your own X11 solution, but Leopard's X11 is quite
broken if I dare to say so, and it seems like it is affecting
CrossOver as well to some extent.

I am aware of the problems with Leopard's X11, and that Wiki page. I've been tracking all of the issues with Leopard's X11 closely, because some of the same issues affect CrossOver. I have even worked a bit with Ben Byer of Apple to help fix stuff.

Anyway, I really doubt that Leopard's X11 is having an adverse effect on CrossOver. We ship an X11 implementation which is almost entirely self-contained, by very conscious design. The only Apple components on which we rely are quartz-wm and libXplugin, neither of which would play a role in what you're seeing. I really think my Launch Services theory is the proper explanation. Let me know what you find. Once we're sure we understand what's going on, I'll have to update the FAQ.

Just to let you know, I've always been running my Japanese programs with 'Run command' option.

For the environment file, I forgot to include the "~" when I was writing, so I meant it to be ~/.MacOSX/environment. And yes, I logged out and logged back in after changing it.

Now here's where it starts getting interesting: I neglected to tell you that setting the Japanese on the top of the list in the International pane, then logging out and back in, then launching Japanese programs still doesn't display the Japanese characters correctly.

Then when I run CrossOver via Terminal with LANG variable set, then run the program via "Run Command...", then voila. The characters display properly now.

So it seems like if I want to run my Japanese programs, I have to set the Japanese on top of the list at the International pane, then run CrossOver via terminal with LANG variable set. I assume it'll work the same way for Korean as well, though I haven't tested it.

It's not a feasible solution for me, since I want the rest of the stuff (Finder, menu, etc.) to be English. But at least, it's something.

As for Internet Explorer, it seems like whatever I did somehow fixed the issue of displaying Japanese/Korean characters. It now displays them correctly for some reason, though I don't know why. This is when I run CrossOver either in English locale or run it via terminal with the command on the FAQ or the one that you posted here. How?? I deleted the ~/.MacOSX/environment.plist file and the directory and restarted.