Return-Path: 
 <cocoon-dev-return-38529-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 11467 invoked by uid 500); 16 Mar 2003 23:38:30 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 11428 invoked from network); 16 Mar 2003 23:38:30 -0000
Received: from out005pub.verizon.net (HELO out005.verizon.net)
 (206.46.170.143)
  by daedalus.apache.org with SMTP; 16 Mar 2003 23:38:30 -0000
Received: from verizon.net ([141.156.47.107]) by out005.verizon.net
          (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP
          id <20030316233836.LHXX6910.out005.verizon.net@verizon.net>
          for <cocoon-dev@xml.apache.org>; Sun, 16 Mar 2003 17:38:36 -0600
Message-ID: <3E750AFC.5040601@verizon.net>
Date: Sun, 16 Mar 2003 18:38:36 -0500
From: Vadim Gritsenko <vadim.gritsenko@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [proposal] fixing the encoding problems
References: <3E747E84.8030801@apache.org> <3E74C4F7.8010905@verizon.net>
 <3E74D8BE.6030201@apache.org>
In-Reply-To: <3E74D8BE.6030201@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from
 [141.156.47.107] at Sun, 16 Mar 2003 17:38:36 -0600
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Stefano Mazzocchi wrote:
<snip/>

>> And, any of these are totally independent from the 
>> internationalization. Internationalization affects language used to 
>> produce output, but not how the text in this language is encoded 
>> (UTF8, UTF16, ISO-1859-1, what-have-you).
>
>
> true. but you can't have chinese text in US-ASCII, right? 


Even if you can not that anybody will be able to read it ;-)
So yes, right.


> my point is that having globally-balanced hooks for encoding will 
> allow cocoon to be even more friendly for non-latin-charset needs. I 
> used i18n out of context here, sorry. 


<snip/>


> I didn't propose that, where did you get that impression? 


Your original email was kind of short:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104782195022862&w=2
So I guessed things up a bit.


>> But I am not convinced that it's sitemap's responsibility to worry 
>> about encoding (from SoC POV).
>
>
> I restate:
>
> 1) I want a way for serializers to indicate to the pipeline what is 
> the encoding they will be using, so that the pipeline can set the 
> right HTTP header for it.


+-0, I'm not sure (yet) on this one...


> 2) also, i want a way to overwrite the sitemap-wide behavior of every 
> single serializers, locally, such as
>
>  <map:serialize encoding="UTF-8"/>
>
> when the global serializer configurations state they will be using 
> something else.


But this one is Ok with me and, more over, in line with earlier decision:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=101826371615914&w=2


> Is the proposal clear enough?


Clearer, yes :)

Vadim


> Stefano.