8 Replies Latest reply on Aug 10, 2007 2:03 PM by Newsgroup_User

    HTML is suddenly all Japanese!

    ltoews73
      My Dreamweaver 8 has suddenly started showing all html files in Japanese (or maybe Chinese? I'm not sure.), on both the code and design views. No idea why, not a clue as to how to fix it.

      Click here for a screenshot (89 KB)

      Lorin
        • 1. Re: HTML is suddenly all Japanese!
          Level 7
          Post a link to the page, please.
          --
          Murray --- ICQ 71997575
          Adobe Community Expert
          (If you *MUST* email me, don't LAUGH when you do so!)
          ==================
          http://www.dreamweavermx-templates.com - Template Triage!
          http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
          http://www.dwfaq.com - DW FAQs, Tutorials & Resources
          http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
          ==================


          "ltoews73" <webforumsuser@macromedia.com> wrote in message
          news:f9i947$jua$1@forums.macromedia.com...
          > My Dreamweaver 8 has suddenly started showing all html files in Japanese,
          > on
          > both the code and design views. No idea why, not a clue as to how to fix
          > it.
          >
          > http://kool.sd73.bc.ca/Graphics/dw_***.jpg
          >
          > Lorin
          >


          • 2. Re: HTML is suddenly all Japanese!
            ltoews73 Level 1
            Murray,

            I haven't tried publishing anything since this happened for fear that it will screw things up. I'll try a test page to see what happens.

            My immediate concern is that the development environment won't show existing pages correctly. Did you see the link to the screenshot in my initial post?

            Lorin
            • 3. Re: HTML is suddenly all Japanese!
              Level 7
              Yes, but screenshots are pretty useless for diagnostics in cases like this.

              --
              Murray --- ICQ 71997575
              Adobe Community Expert
              (If you *MUST* email me, don't LAUGH when you do so!)
              ==================
              http://www.dreamweavermx-templates.com - Template Triage!
              http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
              http://www.dwfaq.com - DW FAQs, Tutorials & Resources
              http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
              ==================


              "ltoews73" <webforumsuser@macromedia.com> wrote in message
              news:f9ibma$mst$1@forums.macromedia.com...
              > Murray,
              >
              > I haven't tried publishing anything since this happened for fear that it
              > will
              > screw things up. I'll try a test page to see what happens.
              >
              > My immediate concern is that the development environment won't show
              > existing
              > pages correctly. Did you see the link to the screenshot in my initial
              > post?
              >
              > Lorin
              >


              • 4. Re: HTML is suddenly all Japanese!
                Level 7
                ltoews73 wrote:
                > My Dreamweaver 8 has suddenly started showing all html files in Japanese, on
                > both the code and design views. No idea why, not a clue as to how to fix it.

                It's no consolation to you, but that ain't Japanese. It's Chinese
                characters with some random symbols thrown in.

                What does the Content-type meta tag in the head of the document say? On
                Dreamweaver 8, it should normally be this:

                <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

                --
                David Powers, Adobe Community Expert
                Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
                Author, "PHP Solutions" (friends of ED)
                http://foundationphp.com/
                • 5. Re: HTML is suddenly all Japanese!
                  ltoews73 Level 1
                  After my initial panic, I discovered that not every HTML file on my computer is having this problem. The afflicted files were all downloaded from a WebCT course that was developed by someone else, and they all have the following meta tag:

                  <META http-equiv="Content-Type" content="text/html; charset=UTF-16" />

                  The charset value is clearly different from what David tells me it should normally be.

                  I suspect that these files were originally created on a Mac. Could that have anything to do with it?

                  Lorin
                  • 6. Re: HTML is suddenly all Japanese!
                    Level 7
                    No. UTF-16 is specifically for those languages that require 2 bytes per
                    character. No doubt the server from which you downloaded the files was
                    overriding that setting, while your server/local environment is not. I
                    think.

                    --
                    Murray --- ICQ 71997575
                    Adobe Community Expert
                    (If you *MUST* email me, don't LAUGH when you do so!)
                    ==================
                    http://www.dreamweavermx-templates.com - Template Triage!
                    http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
                    http://www.dwfaq.com - DW FAQs, Tutorials & Resources
                    http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
                    ==================


                    "ltoews73" <webforumsuser@macromedia.com> wrote in message
                    news:f9idcs$ors$1@forums.macromedia.com...
                    > After my initial panic, I discovered that not every HTML file on my
                    > computer is
                    > having this problem. The afflicted files were all downloaded from a WebCT
                    > course that was developed by someone else, and they all have the following
                    > meta
                    > tag:
                    >
                    > <META http-equiv="Content-Type" content="text/html; charset=UTF-16" />
                    >
                    > The charset value is clearly different from what David tells me it should
                    > normally be.
                    >
                    > I suspect that these files were originally created on a Mac. Could that
                    > have
                    > anything to do with it?
                    >
                    > Lorin
                    >


                    • 7. Re: HTML is suddenly all Japanese!
                      Level 7
                      As a side note, that's probably Chinese not Japanese. If it's Japanese,
                      it's missing the Hiragana and Katakana characters.

                      Murray *ACE* wrote:
                      > No. UTF-16 is specifically for those languages that require 2 bytes per
                      > character. No doubt the server from which you downloaded the files was
                      > overriding that setting, while your server/local environment is not. I
                      > think.
                      >
                      • 8. Re: HTML is suddenly all Japanese!
                        Level 7
                        Looks like others have already noticed that.

                        Lee wrote:
                        > As a side note, that's probably Chinese not Japanese. If it's Japanese,
                        > it's missing the Hiragana and Katakana characters.
                        >
                        > Murray *ACE* wrote:
                        >> No. UTF-16 is specifically for those languages that require 2 bytes
                        >> per character. No doubt the server from which you downloaded the
                        >> files was overriding that setting, while your server/local environment
                        >> is not. I think.
                        >>