If you go to the URL in this bug report using Nav 4.51 on either Mac OS or Windows, the page is correctly displayed using Japanese characters. Using seamonkey, however, it's displayed in mojibake instead (ie bad characters). Selecting Shift_JIS doesn't visibly do anything - but when you do that, the Connect: goes crazy, repeatedly connecting to the server without any visible results.

Works for me using Mar190805 build on US NT using MS Gothic.

Doesn't work for me using MS Gothic on NT 4 SP 4. Do I need to do anything to apprunner to get it to work (ie edit a prefs file) or should I just expect it to work? I'm now using the March 19 build and the same behavior is happening (loads page with Western encoding instead of shift_jis, changing encodings results in endless contacting of the host).

I try it. It work, it will try to continusly connect to the server. But I think it is a client pull or server push of the imgage (not sure) The text display w/o problem (after reload). cpratt, please drop the file: http://warp/u/ftang/test/prefs_js.txt into the same folder as the appruner (for Window only) and rename it into prefs.js . In your case (if you are using US window and the Japanese font name is "MS Gothic", you shold change the prefs.js and change two lines to "MS Gothic". Please contact teruko or momoi if you need help. Thanks. Leave it as New for now. cpratt, please mark it as invalid if it work for you. Thanaks.

ftang, thanks for the prefs.js file. It works just fine after changing the mojibake in the file to 'MS Gothic'. As to the other issue, I will close this as invalid and open a new bug if and when I can pin down the problem I was seeing at this URI. Thanks for your help!