 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
12 messages in org.w3.public-evangelistjapanese encoding nightmare| From | Sent On | Attachments |
|---|---|---|
| Paul Arenson | Nov 12, 2006 5:50 pm | |
| Karl Dubost | Nov 13, 2006 5:21 am | |
| Paul Arenson | Nov 13, 2006 6:25 am | |
| Paul Arenson | Nov 13, 2006 6:58 am | |
| Daniel Barclay | Nov 13, 2006 10:14 am | |
| Mike Schinkel | Nov 13, 2006 3:10 pm | |
| David Dorward | Nov 13, 2006 3:17 pm | |
| Paul Arenson | Nov 13, 2006 6:06 pm | |
| Daniel Barclay | Nov 16, 2006 11:13 am | |
| Richard Ishida | Nov 23, 2006 2:15 am | |
| Tex Texin | Nov 23, 2006 9:03 am | |
| Paul Arenson | Dec 5, 2006 8:07 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | japanese encoding nightmare | Actions... |
|---|---|---|
| From: | Paul Arenson (pa...@tokyoprogressive.org) | |
| Date: | Nov 12, 2006 5:50:22 pm | |
| List: | org.w3.public-evangelist | |
Hello
I came here via http://www.webstandards.org/learn/articles/askw3c/dec2002/
For a long time I have used Mozilla to create (or adapt other) web pages.
It has worked. I went back and was surprised that it worked DESPITE different encodings I inadvertantly used.
But recently tried to make pages that did NOT work!!!! Am not sure why. And so I am wriiting.
UNSUCCESSFUL EXAMPLE (Looks ok on desktop but not on server) http://tokyoprogressive.org/why.html
CODE <meta content="text/html; charset=UTF-8" http-equiv="content-type">
here are successful example from the past: - - - - - - - - - - - - -
SUCCESSFUL EXAMPLE ONE (JAPANESE COMES OUT RIGHT) http://www.tokyoprogressive.org/index/weblog/print/april-entries/
This was made via EXPRESSION ENGINE
I note I have both xml: lang and uft-8. I also note I am confused about differences between character encoding and language, but anyway, it works.
CODE <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="ja" lang="ja"> <head> <title>April entries</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- - - - - - - - - - - - -
SUCCESSFUL EXAMPLE TWO http://tokyoprogressive.org/indexoct2006.html
THIS WAS MADE BY HAND USING a CSS TEMPLATE.
I THOUGHT I did this in UFT-8, but no. Mozilla even says it is UFT-8, but as you can see the code is western. In other words, why does it work?
CODE <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- - - - - - - - - - - - -
SUCCESSFUL EXAMPLE THREE http://tokyoprogressive.org/indexnov2006.html Now here is one where I specified uft-8 and it too is ok!
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
SUCCESSUL EXAMPLE FOUR (most bizarre?) I even forgot to add the meta tag!!!
http://tokyoprogressive.org/ - - - - - - - - - - - - -
PROBLEMS STARTED APPEARING WITH NEW PAGES
EXPERIMENT:
Method
Make a page in several encodings http://tokyoprogressive.org/a.html <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-2022-JP"
LOOKS OK ONLINE - - - - - - - - - - - - -
http://tokyoprogressive.org/b.html <meta content="text/html; charset=UTF-8" http-equiv="content-type"> DOES NOT LOOK OK ONLINE - - - - - - - - - - - - - http://tokyoprogressive.org/c.html <meta content="text/html; charset=Shift_JIS" http-equiv="content- type"> DOES NOT LOOK OK ONLINE - - - - - - - - - - - - - http://tokyoprogressive.org/d.html <meta content="text/html; charset=EUC-JP" http-equiv="content-type"> DOES NOT LOOK OK ONLINE - - - - - - - - - - - - -
CONCLUSION:
Can anyone tell me what is going on?
Thanks!
__/__/__/__/__/__/__/__/__/__/ Paul Arenson
EMAIL pa...@tokyoprogressive.org
__/__/__/__/__/__/__/__/__/__/