sdozono:

That's interesting. I have created several websites in Japanese but I
always use UTF-8 and it comes out all right.

I just have to make sure that the <head> tags contain:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="Content-Language" content="JA" />

I had trouble before with garbage characteds in UTF-8 if I don't set
the Content-Language tags. But after I set the Content-Language tag
everythiing seems to work fine.

I will try using SHIFT_JIS tomorrow and see what happens.

Thanks everyone for your help.

On Oct 6, 9:39 pm, sdozono <[EMAIL PROTECTED]> wrote:
> hello from Japan.
> I tested this case at my Japanese environment.
>
> I saved your text in a text file with Shift-JIS format. (Japanese
> Windows common charset)
> After I opened the file in "UTF-8" charset, I got the same kind a
> garbage character.
>
> Hope that helps.
>
> *Original and saved in Shift-JIS format.*
> オーストラリア大使館のカルチャーセンター - ようこそ
>
> *Opened the file in UTF-8*
> I[XgAgق̃J`[Z^[ - 悤
>
> *Opened the file in UTF-7*
> ƒI [ƒXƒgƒ‰ƒŠƒA‘åŽgŠÙ‚̃Jƒ‹ƒ`ƒƒ [ƒZƒ“ƒ^ [ - ‚悤‚±‚»
>
> *Opened the file in EUC*
> オーストラリア代.g茅"磨Jルチャーセンター - ゅ€・・
>
> Shun Dozono @ cakephp.jp
>
> exo_duz のメッセージ:
>
> > In the title string  the front bit before "-" is from po file and the
> > end bit which is the problematic area is the one from $this-
> > >pageTitle:
>
> > <title> ` ȥ ꥢ ʹ ^ Υ e ` 󥿩` - </title>
>
> > This is the broken characters " ", it is supposed to say 褦 .
>
> > Somehow from all these problems I figure that CakePHP hasn't got
> > Internationalization quite figured out yet IMO.
>
> > On Oct 6, 8:24 pm, exo_duz <[EMAIL PROTECTED]> wrote:
> > > Yeah to my knowledge it shouldn't make a diff but this issue is really
> > > baffling me.
>
> > > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /
>
> > > >    <meta http-equiv="Content-Language" content="JA" />
>
> > >     <meta name='description' content="Welcome to the Australian
> > > Government in Japan's web site dedicated to Australian arts in Japan
> > > and Australia-Japan artistic collaboration. Whether you are an artist
> > > or fan, you will find plenty of information about upcoming events in
> > > Japan, e-newsletters and useful links." />
> > >     <meta name='keywords' content='Arts, Culture, Australia, Australia
> > > Web, Australian, Sydney, Perth, Melbourne, Brisbane, Cairns, Adelaide,
> > > Hobart, Darwin, Canberra' />
> > >     <meta name='author' content='Robin Roy Julius' />
> > >     <meta name='copyright' content='Australian Embassy Tokyo' />
>
> > >         <title> ` ȥ ꥢ ʹ ^ Υ e ` 󥿩` - </title>
>
> > > That is the HTML source from Firefox 3.
>
> > > This issue is really baffling me as to why it is happening. I have
> > > tested it out on Firefox, IE, Chrome and Safari on Windows and Firefox
> > > and Safari on OSX and it is still happening.
>
> > > On Oct 6, 7:41 pm, "David C. Zentgraf" <[EMAIL PROTECTED]> wrote:
>
> > > > On 6 Oct 2008, at 17:47, grigri wrote:
>
> > > > > Make sure that your charset meta-tag is BEFORE the title tag. In an
> > > > > older version of cake, the default layout had the reverse (title
> > > > > first) which meant that it wasn't parsed as UTF-8.
>
> > > > This shouldn't be the case.
> > > > An HTML document is not evaluated by the browser line-by-line in the
> > > > same way PHP is. At least no modern browser should do that (do I need
> > > > to look in your direction IE?). A quick test on OS X Safari confirms
> > > > that it makes no difference where the UTF8 tag is, only that it needs
> > > > to be somewhere in the header.
>
> > > > If it does make a difference in other browsers, please let me know
> > > > (honest request).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to