JP Character Set

liunx · Jan 10, 2008

W3C says I'm not using the correct character set and thus cannot validate or read my page for that matter. 
 
LEGEND: 
Orange = Correct if wrong (please) 
 
My code: 
 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> 
<html> 
<head> 
<title>Our Site</title> 
<meta http-equiv="content-type" content="text/html; charset="iso-2022-jp"> 
<meta http-equiv="content-language" content="iso-2022-jp"> 
<meta name="keywords" content="blah, blah, blah"> 
<meta name="author" content="blah, blah, blah"> 
<meta name="description" content="blah blah blah."> 
<meta name="robots" content="all"> 
<meta name="rating" content="general"> 
<meta name="revisit" content="10"> 
<link href=http://www.htmlforums.com/archive/index.php/"abc.css" rel="stylesheet" type="text/css"> 
</head> 
 
 
Copy from W3C validation results: 
 
 
Doctype: 
Encoding: 
 
I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to validate the document. The sources I tried are: 
 
The HTTP Content-Type field. 
The XML Declaration. 
The HTML "META" element. 
And I even tried to autodetect it using the algorithm defined in Appendix F of the XML 1.0 Recommendation. 
 
Since none of these sources yielded any usable information, I will not be able to validate this document. Sorry. Please make sure you specify the character encoding in use. 
 
IANA maintains the list of official names for character sets. 
 
 
Thanks, 
Gandalf

I've come to the conclusion that there are several different sub-char's under a character set and I have no idea which one to use... 
 
Any helpful comment would be appreciated, since the research I have done was useful. 
 
Ty, 
Gandalf

The version HTML 4.0 should be HTML 4.01 
 
 
...charset="iso-2022-jp"> -- well, what character set are you using? and the iso should be in capitals ISO instead (as well as the jp I expect, too). 
 
 
<meta http-equiv="content-language" content="iso-2022-jp"> Hmm, iso-2022-jp should be just the two letters ja as well.Still not working... 
 
Browsing some Japanese sites to see what they did. 
 
G

I found this in two different sites: 
 
<META http-equiv="Content-Type" content="text/html; charset=Shift_JIS"> 
<META http-equiv="Content-Language" content="ja"> 
 
However, mimicing this in my code, W3C still didn't recognize the page. 
 
This wouldn't have anything to do with the page being uploaded as opposed to using a URI would it?? 
 
Thanks, 
G

Please don't let my replies to my own thread here give you the impression that I've figure out the answer to my problem. 
 
The following is simply for note, as from time to time I come back to my posting for reference. But the following is also for the benefit of the reader if nothing more than the mere novelty of it. 
 
Posted from: 
<a class="postlink" href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a> 
 
 
207 kubota 1.5 ISO-2022-JP-2 (RFC 1554) is a subset of 7bit version 
208 of ISO 2022 and superset of ISO-2022-JP. Difference between ISO-2022-JP 
209 and ISO-2022-JP-2 is that ISO-2022-JP-2 has more coded character sets 
210 than ISO-2022-JP. Character sets included in ISO-2022-JP-2 are: 
 
 
211 kubota 1.2 <list> 
212 <item>ASCII (ESC 0x28 0x42) 
213 <item>JIS X 0201-1976 Roman (ESC 0x28 0x4a), 
214 <item>JIS X 0208-1978 (old JIS) (ESC 0x24 0x40), 
215 <item>JIS X 0208-1983 (new JIS) (ESC 0x24 0x42), 
216 <item>GB2312-80 (simplified Chinese) (ESC 0x24 0x41), 
217 <item>KS C 5601 (Korean) (ESC 0x24 0x28 0x43), 
218 <item>JIS X 0212-1990 (ESC 0x24 0x28 0x44), 
219 <item>ISO 8859-1 (Latin-1) (ESC 0x2e 0x41), and 
220 <item>ISO 8859-7 (Greek) (ESC 0x2e 0x46). 
221 </list> 
 
 
 
 
Gandalf 
Question: 
 
What in the heck does this mean in English: 
Line 8, column 70: an attribute value literal can occur in an attribute specification list only after a VI delimiter 
...nt-type" content="text/html; charset="Shift_JIS"> 
 
 
By the way, I finally got the W3C Validator to read my code after I forced a DOCTYPE, since for some reason it wasn't reading mine which is: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">. Though I think this problem will fix itself once we get this CHARset stuff taken care of along with the other page errors. 
 
Second Question: 
In this line, [ ...nt-type" content="text/html; charset="Shift_JIS"> ] does the charset need to be as is or does case matter? Can I write it in all lower case letters and get the same result? 
 
I really hope we get this problem taken care of soon... 
 
Thanks, 
Gandalf 
I already said above to change the HTML 4.0 to be HTML 4.01 instead; right there in the DOCTYPE. 
 
The Content-Type MUST be in capital letters, or exactly as per the W3C example, so ISO-2022-JP is valid and all others iso-2022-jp, etc, are not. 
 
 
Post the URL of the page so I can take a look at what is going on. It really should not be this difficult. 
 
 
 
 
 
Umm, dude, you changed TWO things in your version. You fixed one thing and broke something else at the same time. 
 
You posted an example with: 
 
content="text/html; charset=Shift_JIS" 
 
Now you are saying you have: 
 
content="text/html; charset="Shift_JIS" 
 
 
Look carefully at how many quote marks you have in the last one. That one is wrong. The first one has the correct number of "quotes" in it. 
 
The error about attribute specification list and delimiters is warning you about the incorrect number of quote marks; the validator thinks you are trying to do a list of attribute values not just one value. 
 
About the only time you can have a list of attribute values is when you say something like and so on. There are very few other places where an attribute can have a list of allowed values, and the incorrect quoting makes the validator think that that is what you are trying to do. 
 
 
 
.

JP Character Set

liunx

Guest