Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <4231ECB4.6030004@apache.org>
Date: Fri, 11 Mar 2005 14:08:36 -0500
From: Stefano Mazzocchi <stefano@apache.org>
Organization: Apache Software Foundation
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Flowscript encoding weirdness and a solution
References: <4231EBE0.5050101@apache.org>
In-Reply-To: <4231EBE0.5050101@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sylvain Wallez wrote:
> Hi all,
> 
> I encountered some weird things with a flowscript containing strings 
> with accented characters, saved in UTF-8. This is because the flow 
> interpreter uses the platform's default encoding to read script files. 
> And of course this default encoding isn't the same on Windows and Mac...
> 
> To solve this, I added the possibility to specify the file's encoding as 
> a comment in the very first line of the script, e.g.
> 
>  // encoding = UTF-8
>  function blah()
>  ...
> 
> If no special comment exists, we fall back to the platform's default 
> encoding as of today.
> 
> This works beautifully, and I'm thinking of adding this to 2.1 even if 
> (or especially because) the release is coming soon.

how about

  //@ encoding = UTF-8

instead? so that we can discriminate between comments and 'metadata 
comments'?

-- 
Stefano.