Return-Path: Delivered-To: apmail-cocoon-users-fr-archive@www.apache.org Received: (qmail 99349 invoked from network); 14 Apr 2006 12:48:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Apr 2006 12:48:46 -0000 Received: (qmail 46469 invoked by uid 500); 14 Apr 2006 12:48:45 -0000 Mailing-List: contact users-fr-help@cocoon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users-fr@cocoon.apache.org Delivered-To: mailing list users-fr@cocoon.apache.org Received: (qmail 46458 invoked by uid 99); 14 Apr 2006 12:48:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Apr 2006 05:48:45 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [84.96.21.10] (HELO mail.anyware-tech.com) (84.96.21.10) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Apr 2006 05:48:43 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.anyware-tech.com (Postfix) with ESMTP id 1AD1033B29 for ; Fri, 14 Apr 2006 14:48:20 +0200 (CEST) Received: from mail.anyware-tech.com ([127.0.0.1]) by localhost (trinity [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19517-06 for ; Fri, 14 Apr 2006 14:48:03 +0200 (CEST) Received: from [10.0.1.27] (poukram.anyware [10.0.1.27]) by mail.anyware-tech.com (Postfix) with ESMTP id 4436033A9C for ; Fri, 14 Apr 2006 14:48:01 +0200 (CEST) Message-ID: <443F99F8.4010609@apache.org> Date: Fri, 14 Apr 2006 14:47:52 +0200 From: Sylvain Wallez User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: users-fr@cocoon.apache.org Subject: Re: eclaircisssements sur l'encoding? References: <443E83C7.20307@gmail.com> <20060413171651.GJ44484@vision.anyware> <443F6999.20607@gmail.com> <20060414103148.GB54479@vision.anyware> In-Reply-To: <20060414103148.GB54479@vision.anyware> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at anyware-tech.com X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Jean-Baptiste Quenot wrote: > * philguillard: > > >> Declarer l'encoding dans le serializer est-til une declarattion >> pour la future prise en compte du document (html) >> > > Si tu imbriques un �l�ment fils dans la d�claration du > serializer, cet encoding sera utilis� pour la s�rialisation XML du > document. Yep. > Il faut �galement penser � indiquer l'encoding dans > l'en-t�te HTTP de la r�ponse. Pour cela, indiquer > mime-type="text/html; charset=UTF-8" par exemple sur la > d�claration du serializer. > C'est le serializer qui se charge de �a. Le serializer HTML se charge aussi de mettre le tag > Attention, si on passe par Apache, Apache va compl�ter l'en-t�te > Content-Type en rajoutant le jeu de caract�res par d�faut d'Apache > s'il n'est pas indiqu�. > > Si on n'indique pas le jeu de caract�res dans l'en-t�te HTTP > Content-Type, le navigateur cherchera un �l�ment > pour d�terminer le jeu de > caract�res. > Et bien que th�oriquement l'ent�te Content-Type l'emporte sur le , ce n'est pas toujours le cas, selon les navigateurs... Sylvain -- Sylvain Wallez http://bluxte.net Apache Software Foundation Member --------------------------------------------------------------------- Liste francophone Apache Cocoon -- http://cocoon.apache.org/fr/ Pour vous desinscrire : mailto:users-fr-unsubscribe@cocoon.apache.org Autres commandes : mailto:users-fr-help@cocoon.apache.org