I believe a BOM is only a BOM if it's at the beginning of the file. So I think 
Falcon is correct to complain and the files should be fixed.

- Gordon

-----Original Message-----
From: Cyrill Zadra [mailto:cyrill.za...@gmail.com] 
Sent: Friday, November 16, 2012 1:58 AM
To: flex-dev@incubator.apache.org
Subject: Re: [FALCON] Problem with \uFEFF chararcters in mustella files

I may have found the problem. It looks like there are files where the BOM isn't 
at the beginning of a file and thats the case where falcon can run into 
problems.

ActionScript Example

////////////////////////////////////////////////////////////////////////////////
//
//  Apache License Header
//
////////////////////////////////////////////////////////////////////////////////
BOMpackage ...
{

}

cyrill

On Thu, Nov 15, 2012 at 10:44 PM, Cyrill Zadra <cyrill.za...@gmail.com> wrote:
> Thanks Alex. Just looked into falcon code and found.a few places where 
> it already ignore the BOM. So it must be a rare exception. I'll take a 
> look into that and try to find out in which exception it fails.
>
> cyrill
>
> On Thu, Nov 15, 2012 at 9:03 PM, Alex Harui <aha...@adobe.com> wrote:
>>
>>
>>
>> On 11/15/12 8:22 PM, "Cyrill Zadra" <cyrill.za...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> In the mustella tests there are files that contains \uFEFF (just 
>>> before the package declaration) and in some cases falcon has problem 
>>> with this character and ends with the error:
>>>
>>> [java] Error: Unexpected character. '?' is not allowed here [java] 
>>> ?package assets.styleTest
>>>
>>> Following command searches for non-ascii chars and if executed in 
>>> mustella folder it returns quite a big result.
>>>
>>> grep --color='auto' -I -R -P -n "^[\x80-\xFF]" *
>>>
>>> Are those characters really supposed to be there?
>>
>> See [1].  Falcon will have to learn to ignore them.
>>
>> [1] 
>> http://www.rgagnon.com/javadetails/java-handle-utf8-file-with-bom.htm
>> l
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>

Reply via email to