ASC parsing bug?
stejohns at adobe.com
Mon Jun 16 15:32:56 PDT 2008
Having a tool like ASC try to guess the proper encoding sounds like a recipe
for long-term pain to me. (Hey, browser guys, how much fun is it to guess
the encoding of poorly-marked HTML? :-)
IMHO, if the encoding isn't either (1) explicitly specified, or (2)
absolutely clear from a BOM, ASC should fail.
Perhaps we could tell ASC: "if no BOM specified, assume encoding=XXX"
On 6/16/08 3:01 PM, "Mike Shaver" <mike.shaver at gmail.com> wrote:
> On Mon, Jun 16, 2008 at 5:33 PM, Michael Daumling <mdaeumli at adobe.com> wrote:
>> If possible, asc should IMHO assume UTF-8, and if UTF-8 decoding fails, retry
>> with the default system encoding (a.k.a CP-1252 on English Windows).
> I think that would be confusing behaviour, since ASC would work fine
> compiling a file on one system, but the same ASC invocation method
> might fail on another machine (with different default system
> I think it should probably take UTF-8 by default, and provide an
> explicit command-line argument for using a different encoding instead.
> Maybe there are historic compatibility needs that prevent that,
More information about the Tamarin-devel