Re: [Pagekit-users] trouble setting content-type

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi Evan,

sorry for the delay, I had no chance to read the list lately. Are you sure the 
page is delivered in the wrong charset? It looks to me, that your client 
preferes another charset, or is only able to serve the default (iso-8859-1). 
You setup look correct to me.

All clients told the server what charset they can handle. If this header is 
not present iso-8859-1 is assumed. If pagekit is able to convert the page to 
a charset that the client can handle, it does that. That might explain why 
you end up with a charset iso-8859-1.

Here is a little  prove:

The page http://eg.2bz.de/charset includes char that are handled different for 
iso-8859-1 and utf8.

I download the page with wget:

  wget --header='Accept-Charset: iso-8859-1' http://eg.2bz.de/charset

and a second time with

  wget --header='Accept-Charset:utf-8' http://eg.2bz.de/charset

this result in two files, delivered in different charsets as the client 
requests.

-rw-r--r--  1 boris users 121 2005-05-24 23:54 charset
-rw-r--r--  1 boris users 146 2005-05-24 23:54 charset.1

  0000: 3c 68 74 6d 6c 3e 0a 3c 62 6f 64 79 3e 0a 3c 68  <html>.<body>.<h
  0010: 31 3e 69 6e 64 65 78 2e 74 6d 70 6c 3a 20 73 74  1>index.tmpl: st
  0020: 72 61 26 23 32 32 33 3b 65 20 20 20 73 74 72 61  ra&#223;e   stra
  0030: df 65 20 f6 f6 e4 f6 fc e4 fc f6 fc fc 20 20 3c  .e ..........  <
  0040: 2f 68 31 3e 0a 3c 62 72 3e 0a 3c 68 31 3e 73 74  /h1>.<br>.<h1>st
  0050: 72 61 df 65 20 df df f6 e4 f6 e4 f6 fc e4 f6 e4  ra.e ...........
  0060: fc fc 20 3c 2f 68 31 3e 0a 3c 2f 62 6f 64 79 3e  .. </h1>.</body>
  0070: 0a 3c 2f 68 74 6d 6c 3e 0a                       .</html>.       

  0000: 3c 68 74 6d 6c 3e 0a 3c 62 6f 64 79 3e 0a 3c 68  <html>.<body>.<h
  0010: 31 3e 69 6e 64 65 78 2e 74 6d 70 6c 3a 20 73 74  1>index.tmpl: st
  0020: 72 61 26 23 32 32 33 3b 65 20 20 20 73 74 72 61  ra&#223;e   stra
  0030: c3 9f 65 20 c3 b6 c3 b6 c3 a4 c3 b6 c3 bc c3 a4  ..e ............
  0040: c3 bc c3 b6 c3 bc c3 bc 20 20 3c 2f 68 31 3e 0a  ........  </h1>.
  0050: 3c 62 72 3e 0a 3c 68 31 3e 73 74 72 61 c3 9f 65  <br>.<h1>stra..e
  0060: 20 c3 9f c3 9f c3 b6 c3 a4 c3 b6 c3 a4 c3 b6 c3   ...............
  0070: bc c3 a4 c3 b6 c3 a4 c3 bc c3 bc 20 3c 2f 68 31  ........... </h1
  0080: 3e 0a 3c 2f 62 6f 64 79 3e 0a 3c 2f 68 74 6d 6c  >.</body>.</html
  0090: 3e 0a                                            >.              

I guess your testclient does not include a header or prefere iso-8859-1 and 
pagekit kindly provide that ;-)

Am Dienstag, 10. Mai 2005 06:12 schrieb Evan Miller:
> Hello,
>
> I am trying to have the server declare UTF-8 as the charset when it
> serves up a page, but I can't get it to change from ISO-8859-1. Here is
> the relevant part of my Config.xml:
>
>    <GLOBAL
>          default_page="index"
>          gzip_output = "static"
>          login_page="login1"
>          model_base_class="WSOKit::Common"
>          model_dispatch_prefix="WSOKit::Model"
>          recent_login_timeout="10"
>          session_expires="+1y"
>          default_input_charset="utf-8"
>          default_output_charset="utf-8"
>          />
>
> I've also tried "utf8" for the charset name, as well as the capitalized
> forms, but no luck. Even when I set Apache's default character set to
> UTF-8, PageKit pages are still served as ISO-8859-1. Any ideas?
>
> Evan
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> Pagekit-users mailing list
> Pag...@li...
> https://lists.sourceforge.net/lists/listinfo/pagekit-users

-- 
Boris

-- 
Boris