| Author |
 Topic  |
|
seahorse
Senior Member
USA
1075 Posts |
 Posted - 04 November 2002 : 23:55:27
|
quote:
Originally posted by downdogWoof
Hi All,
on my local machine, Win2kPro (Japanese OS) with IIS5.0, the Japanese characters show fine in IE5.5 & Opera 6.05, both English versions, automatically detecting the correct encoding (Shift-JIS), but, the exact same set up on my live server (EnglishWindows2000Server), language pack installed, they don't, it's all mumbo-jumbo....any thoughts, anyone...?...cheers...
What's the encoding on your Win2K Server's browser set to?< |
Ken
===============
Worldwide Partner Group
Microsoft |
 |
|
|
seahorse
Senior Member
USA
1075 Posts |
Posted - 05 November 2002 : 00:15:01
|
quote:
Originally posted by LeoRat
First, Lang1041 Japanese was originally authored by Seahorse. I have done updating/changes and additional translations which pretty much ended up in a file you have which is sort of my modified version. So, the credit goes to Seahorse.
I think LeoRat is being generous with his comment. I'm not a Japanese native. My initial translation was "ballpark". I think the credit for the more polished version you're seeing now goes to LeoRat, who has really taken over from where I left off.
< |
Ken
===============
Worldwide Partner Group
Microsoft |
|
|
|
downdogWoof
Junior Member
124 Posts |
Posted - 05 November 2002 : 06:50:55
|
Hi All,
sorry for the confusion, I viewed the forum hosted on a Win2k Server from the same Laptop (Japanese OS) that I use for local testing...both browsers (IE5.5 & Opera6.05) are set to Japanese Auto Detect. Could it be the code in my global.asa file..? Japanese on other pages is fine. Did notice something quite odd, though. Leorat's signature sometimes is mumbo-jumbo on his site with encoding set to Shift-JIS (EDIT that should be, set to Japanese Auto Detect) and at other times it's not. On Snitz's site, his signature is sometimes mumbo-jumbo and at times it's fine...of course, with his site, if I set the encoding to UTF-8 then it's fine.
<SCRIPT LANGUAGE='VBScript' RUNAT='Server'>
Sub Session_onStart
Session.Codepage=932
end sub
</SCRIPT>
EDIT: Perhaps a URL might be useful... www.easyboarder.com/ForumInternational/default.asp
cheers.
< |
TIA,
downdogWoof...
Yeah, K, Who Stole The Soggy Biscuits...? |
Edited by - downdogWoof on 05 November 2002 20:00:32 |
|
|
|
seahorse
Senior Member
USA
1075 Posts |
Posted - 05 November 2002 : 20:44:17
|
quote:
Originally posted by downdogWoof
Hi All,
EDIT: Perhaps a URL might be useful... www.easyboarder.com/ForumInternational/default.asp
I've looked at your site. I could be wrong, but it seems like only the elements from certain include files are showing up corrupted. Double check and make sure that you have saved the include files in the proper encoding format.
I had a similar problem with my utf-8 includes. The main page file was saved as utf-8, but the includes were saved as shift-jis. When the browser displayed the entire page, it selected utf-8 encoding which meant that the shift-jis includes appeared corrupted.
You can use notepad to open and resave the files as utf-8. I had problems using Visual Studio to save in uft-8 format. Notepad should do it correctly.
< |
Ken
===============
Worldwide Partner Group
Microsoft |
|
|
|
n/a
deleted
593 Posts |
Posted - 05 November 2002 : 23:17:57
|
You cannot mix and match encoding schemes anywhere... if you are to use Shift-JIS, you use Shift-JIS on client (HTML) and server sides (ASP)...This is a golden rule. Unless you have a converter/mapper of sort in a process to automatically convert charsets/fonts from one type to another encoding scheme...
I see you set your server codepage to 932, Shift-JIS and HTML is set to 932 (which means that you have set LAng1041 encoding to 932/Shift-JIS) also in your default page....but looking at corrupted charsets, it looks like UTF8 charsets/fonts are rendered in Shift-JIS or when the original file was either re-id'd with 932, you opened the file in a wrong encoding format or saved it in a wrong encoding format...not clear which version of Lang1041 you used...
LCID is only an id code for locale/region.
Codepage is a particular encoding scheme id. By itself or changing this from UTF-8 to Shift-JIS or whatever, does not make that "file" font types/charsets to Shift-JIS or other. You have to convert file to an appropriate encoding format. That's why I had both Shift-JIS and UTF8.
All I see is Lang1041 (most likely UTF8 formatted) corrupted in a source file and not rendering in either Shift-JIS nor UTF8.
My sig is in utf8 Japanese/English. So if you access the posts here which is defaulted to Western European (Windows), you will see it corrupted in rendering as browser encoding and text string encoding fonts are not the same... the same problem in your case.
< |
Taku
|
Edited by - n/a on 05 November 2002 23:22:30 |
|
|
|
downdogWoof
Junior Member
124 Posts |
Posted - 06 November 2002 : 11:47:47
|
Hi All,
all my pages on my site are in Shift-JIS.
quote:
I see you set your server codepage to 932, Shift-JIS and HTML is set to 932 (which means that you have set LAng1041 encoding to 932/Shift-JIS) also in your default page....but looking at corrupted charsets, it looks like UTF8 charsets/fonts are rendered in Shift-JIS or when the original file was either re-id'd with 932, you opened the file in a wrong encoding format or saved it in a wrong encoding format...not clear which version of Lang1041 you used...
Not too sure I follow you here...I used the Shift-JIS Language file Lang1041.asp that was from your site. I opened it in my WYSIWYG Editor, UltraDev4 which is set to Shift-JIS auto code set in preferences. The thing that strikes me here, is, it works fine on my local testing machine, IBM R30 Laptop with Japanese OS Win2kPro running IIS5.0. I was even successful in editing the Lang1041.asp file to allow the admin text to be in English. I'm at a loss here.
quote:
I've looked at your site. I could be wrong, but it seems like only the elements from certain include files are showing up corrupted. Double check and make sure that you have saved the include files in the proper encoding format.
Ken, which include files would that be..? I haven't altered any include files whatsoever...
Big thanx to you both for trying to help me out here...truly appreciated...< |
TIA,
downdogWoof...
Yeah, K, Who Stole The Soggy Biscuits...? |
|
|
|
n/a
deleted
593 Posts |
Posted - 06 November 2002 : 15:06:54
|
quote:
Originally posted by downdogWoof
Hi All,
all my pages on my site are in Shift-JIS.
quote:
I see you set your server codepage to 932, Shift-JIS and HTML is set to 932 (which means that you have set LAng1041 encoding to 932/Shift-JIS) also in your default page....but looking at corrupted charsets, it looks like UTF8 charsets/fonts are rendered in Shift-JIS or when the original file was either re-id'd with 932, you opened the file in a wrong encoding format or saved it in a wrong encoding format...not clear which version of Lang1041 you used...
Not too sure I follow you here...I used the Shift-JIS Language file Lang1041.asp that was from your site. I opened it in my WYSIWYG Editor, UltraDev4 which is set to Shift-JIS auto code set in preferences. The thing that strikes me here, is, it works fine on my local testing machine, IBM R30 Laptop with Japanese OS Win2kPro running IIS5.0. I was even successful in editing the Lang1041.asp file to allow the admin text to be in English. I'm at a loss here.
Seems like your server is not processing Shift-JIS encoding correctly.... Believe Ken has better experience in handling Japanese and non-Japanese server enviornments...
quote:
I opened it in my WYSIWYG Editor, UltraDev4 which is set to Shift-JIS auto code set in preferences. The thing that strikes me here, is, it works fine on my local testing machine, IBM R30 Laptop with Japanese OS Win2kPro running IIS5.0. I was even successful in editing the Lang1041.asp file to allow the admin text to be in English. I'm at a loss here.
I don't have an experience with UltraDev4 (I believe Seahorse has). (and also I am not a fan of using WYSIWYG editor in handling texts but rather use a straight forward text editor....)Yes, Shift-JIS or Japanese in ISO encoding has basic ASCII as a core base or subset, so you can handle "English" in that charset group. There are basically two possible errors - one is with an error in charset encoding setting in LangNNNN.asp itself where you may not have saved the file (thus text strings) in the appropriate encoding charsets (thus require to have your file saved in Shift-JIS encoding format.) or your server not handling Shift-JIS encoding in processing ASP files or your DB is not handling it properly. Did you open Lang1041ShiftJIS and edited in Shift-JIS enabled mode and saved the edited file in Shift-JIS encoding format?
Either case, you need to check (1)html encoding/codepage setting in LANG1041.asp and forum asp files, and Lang1041 itself for encoding format of the file saved, (2) server side encoding handling esp. related to Shift-JIS, and (3) database handling of Shift-JIS
What I mean by you have to have one encoding is across all these different layers (Presentation, Application/Business Logic, and Database - to borrow some techie jargons) you have to have one consistent encoding scheme or a process to be able to handle a unified encoding format throughout...otherwise, you will have encoding mismatch and data entity corruptions (fonts, texts, charsets, etc.) somewhere in a process of PRESENTATION<>APPLICATION<>DATA..... Browser encoding matches with what is defined/formatted in PRESENTATION...and font types used for an encoding scheme may differ from one browser to another. For example, I think IE6 uses MSGothic for Japanese font style while Netscape 7 uses MS Mincho... different rendering of Japanese in each browser. Am not sure about Opera as I haven't touched on it.
< |
Taku
|
Edited by - n/a on 06 November 2002 19:38:46 |
|
|
|
n/a
deleted
593 Posts |
Posted - 06 November 2002 : 15:21:41
|
Alternatively, contact the following V4b03.x implemented forums in Shift-JIS only:
Sun One Asp User Forums
Deployed in Shift-JIS only - Environments:Cobalt RaQ4j?ASun ONE ASP v3.6.2?A?@?f?[?^?x?[?X mySQL ?A???ꠃV?t?g JIS?@?ʼnғ????Ă??܂??B(V4b03.03 compatible Shift-JIS Lang1041 deployed - the same lang1041 Shift-JIS you have.) If you read Japanese, it explains in detail how he did installation and how he fixed some mySQL related issues in handling Japanese email etc.
OCRonPDF
Deployed in Shift-JIS and English. Uses the first draft of Lang1041.asp Shift-JIS version. Believe his DB is Access on English/US server somewhere....in terms of Lang1041, only difference is that he uses the very first version with his changes in Japanese...
These two are known Snitz Forum 2000 deployments in Shift-JIS (non-intranet forums) that I have involved and helping out...
You may inquire their experience and kind of knowledgebase in handling the issues that you are facing.
Also, issues you are facing are not "Japanese-specific"...you can check other posts, especially dealing with Chinese locale Windows system as you have Win2k JA version...
Good luck.< |
Taku
|
Edited by - n/a on 06 November 2002 19:47:04 |
|
|
|
n/a
deleted
593 Posts |
Posted - 06 November 2002 : 20:04:13
|
quote:
Originally posted by seahorse
quote:
Originally posted by LeoRat
First, Lang1041 Japanese was originally authored by Seahorse. I have done updating/changes and additional translations which pretty much ended up in a file you have which is sort of my modified version. So, the credit goes to Seahorse.
I think LeoRat is being generous with his comment. I'm not a Japanese native. My initial translation was "ballpark". I think the credit for the more polished version you're seeing now goes to LeoRat, who has really taken over from where I left off.
I believe my involvement and task in finishing up Lang1041 for V4b03.x was done. And there should be a new group to heading up Lang1041 for v4.4 - which will require most likely locale machine/windows enviornment etc. so a future is up to a new group - hopefully current in-country resident native speakers and ASP experts.< |
Taku
|
|
|
|
seahorse
Senior Member
USA
1075 Posts |
Posted - 07 November 2002 : 03:35:28
|
quote:
Originally posted by LeoRat
Believe Ken has better experience in handling Japanese and non-Japanese server enviornments...
That's a good one!  Truth be told, I've got more experience in being unable to handle Japanese web sites on non-Japanese server environments  
< |
Ken
===============
Worldwide Partner Group
Microsoft |
|
|
|
seahorse
Senior Member
USA
1075 Posts |
Posted - 07 November 2002 : 04:00:54
|
Hi Woof,
My first guess is that you have the wrong lang1041.asp file. The encoding on your forum is set to shift-jis. If you're using the utf-8 encoded lang1041.asp file, the browser is expecting shift-jis encoding and it will turn all the utf-8 encoded Japanese into junk like it appears on your site right now.
If you still have LeoRat's zipped lang1041.asp file, unzip another copy, open it in notepad, under the R[h(E) pulldown menu, select ANSI and save. Reload the lang1041.asp file to your website and take another look at your forum.
< |
Ken
===============
Worldwide Partner Group
Microsoft |
Edited by - seahorse on 07 November 2002 04:52:21 |
|
|
|
seahorse
Senior Member
USA
1075 Posts |
Posted - 07 November 2002 : 04:30:13
|
quote:
Originally posted by downdogWoof
quote:
I've looked at your site. I could be wrong, but it seems like only the elements from certain include files are showing up corrupted. Double check and make sure that you have saved the include files in the proper encoding format.
Ken, which include files would that be..? I haven't altered any include files whatsoever...
Big thanx to you both for trying to help me out here...truly appreciated...
The Lang1041.asp file is an include file. If you've changed the admin related text to English, the file encoding might have changed when you saved.
< |
Ken
===============
Worldwide Partner Group
Microsoft |
Edited by - seahorse on 07 November 2002 04:36:28 |
|
|
|
downdogWoof
Junior Member
124 Posts |
Posted - 08 November 2002 : 17:37:19
|
Hi All,
guys, thanx for the help and your individual patience....a Mr. Akai at this site,
http://www.airwork.jp/forum/ supplied by Leorat
was unbelievably helpful..he actually went into my server, with my permission of course, and set it up for me...now, how is that for niceness...if only the world could stop and just help and instead of, well, you know, we'd be much better off...thank you Mr. Akai..cheers all..
P.S. Apparently most of the pages required this code at the top,
<@LANGUAGE="VBSCRIPT" CODEPAGE="932">..
even though I had this is in a global file,
<SCRIPT LANGUAGE='VBScript' RUNAT='Server'>
Sub Session_onStart
Session.Codepage=932
end sub
</SCRIPT>
The only problem I seem to be experiencing now, is, the login won't recognise Japanese character based Usernames...< |
TIA,
downdogWoof...
Yeah, K, Who Stole The Soggy Biscuits...? |
|
|
|
n/a
deleted
593 Posts |
Posted - 08 November 2002 : 19:14:19
|
Glad to hear that Akai-san could help... he is very very good.
I believe you can change your login name into Shift-JIS if everything is consistently in shift-Jis...but may encounter some problems with db tables...not sure. Alternatively, you can leave a language selector "Japanese" as "Japanese" in English.....or create a graphic button for Japanese. But if you are using only in Shift-JIS, assume that it should work. (This probably is less critical than the problems that you fixed...)
Take care.< |
Taku
|
Edited by - n/a on 08 November 2002 20:25:31 |
|
|
|
seahorse
Senior Member
USA
1075 Posts |
Posted - 09 November 2002 : 22:22:49
|
quote:
Originally posted by downdogWoof
The only problem I seem to be experiencing now, is, the login won't recognise Japanese character based Usernames...
Don't recommend using Japanese user names. Too much trouble for what they are worth. You have to keep the user to a single byte password anyway becuase of the way the pw field is setup. Why bother making them switch to single byte just to enter their user name.
< |
Ken
===============
Worldwide Partner Group
Microsoft |
|
|
|
Topic |
|
|
|
Forum Locked
