Received: by 10.115.116.7 with SMTP id t7mr528385wam.25.1257011282117;
        Sat, 31 Oct 2009 10:48:02 -0700 (PDT)
Received: by 10.115.116.7 with SMTP id t7mr528384wam.25.1257011282093;
        Sat, 31 Oct 2009 10:48:02 -0700 (PDT)
Return-Path: <3UXjsShAKBQEdpeftjuf-opsfqmzhpphmf.dpnfrelqhpphmfhspvqt....@codesite.bounces.google.com>
Received: from mail-pz0-f206.google.com (mail-pz0-f206.google.com [209.85.222.206])
        by gmr-mx.google.com with ESMTP id 25si515142pzk.3.2009.10.31.10.48.01;
        Sat, 31 Oct 2009 10:48:01 -0700 (PDT)
Received-SPF: pass (google.com: domain of 3UXjsShAKBQEdpeftjuf-opsfqmzhpphmf.dpnfrelqhpphmfhspvqt....@codesite.bounces.google.com designates 209.85.222.206 as permitted sender) client-ip=209.85.222.206;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of 3UXjsShAKBQEdpeftjuf-opsfqmzhpphmf.dpnfrelqhpphmfhspvqt....@codesite.bounces.google.com designates 209.85.222.206 as permitted sender) smtp.mail=3UXjsShAKBQEdpeftjuf-opsfqmzhpphmf.dpnfrelqhpphmfhspvqt....@codesite.bounces.google.com; dkim=pass (test mode) header...@google.com
Received: by pzk19 with SMTP id 19so6719pzk.4
        for <eqdkp@googlegroups.com>; Sat, 31 Oct 2009 10:48:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=beta;
        h=domainkey-signature:mime-version:x-generated-by
         :x-googlecode-project:x-googlecode-issue-id:references:in-reply-to
         :received:message-id:date:subject:from:to:content-type;
        bh=WxUU+zdRnLycNdMaj69Brbnqo2rgCmXFU9ao/MiItws=;
        b=sNzMwkpuE6SiQtUh0GRLtDpyNuHO6ZuLRQppDf/caVn2pI8tai9D0Owg7fTf4f26eS
         pIwGVEcWOel2E0cJs6DA==
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=google.com; s=beta;
        h=mime-version:x-generated-by:x-googlecode-project
         :x-googlecode-issue-id:references:in-reply-to:message-id:date
         :subject:from:to:content-type;
        b=QbHM+YvUMEhlZiXgJtIvuUj7c5beRawVJ4IviUKWsxBSbtM2Y1y/lIiUZ3tnWAi2YC
         QJVAvuakAGDbg6sKmz0A==
MIME-Version: 1.0
X-Generated-By: Google Code
X-GoogleCode-Project: eqdkp
X-GoogleCode-Issue-Id: 52
References: <0-11653744027451173639-7876475066170176940-codesite-noreply=google....@googlecode.com>
In-Reply-To: <0-11653744027451173639-7876475066170176940-codesite-noreply=google....@googlecode.com>
Received: by 10.115.84.39 with SMTP id m39mr524581wal.26.1257011281044; Sat, 
	31 Oct 2009 10:48:01 -0700 (PDT)
Message-ID: <0-11653744027451173639-7876475066170176940-codesite-noreply=google....@googlecode.com>
Date: Sat, 31 Oct 2009 17:48:01 +0000
Subject: Issue 52 in eqdkp: http header charset encoding may differ from 
	encoding used in page
From: codesite-nore...@google.com
To: eqdkp@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 52 by garrettehunter: http header charset encoding may differ  
from encoding used in page
http://code.google.com/p/eqdkp/issues/detail?id=52

I changed the ENCODING value in the english lang_main.php file to UTF-8 and
found that the HTTP header was hardcoded to ISO-8859-1 in eqdkp.php.

In the page_header() function would it be better to change both occurrences
of "@header('Content-Type: text/html; charset=iso-8859-1')" to
"@header('Content-Type: text/html; charset='.$user->lang['ENCODING'])"


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings