[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: National characters in authz-db path entries

From: Branko ─îibej <brane_at_xbc.nu>
Date: Fri, 04 Jan 2008 21:24:04 +0100

Erik Huelsmann wrote:
> On 1/4/08, Tobias Hinnerup <tobias_at_hinnerup.net> wrote:
>
>> Hello Branko and Erik
>>
>> Until your replies, the authz file was saved in ANSI encoding.
>>
>> Converting the authz file to UTF-8 with a BOM results in an error when accessing/checking out the repo: ":1 Section header expected" - a behavior that seems buggy?
>>
>> Using UTF-8 without a BOM works perfectly - thank you very much for the suggestion!
>>
>
> Hi Tobias,
>
> It's great to hear it's working without a BOM. Although we might need
> to ignore the BOM, it's not very logical to include a BOM in a UTF-8
> file since it doesn't have endian-issues (AFAIK), it being an 8-bit
> format.
>
> Having said that, Branko, how about ignoring a BOM to any input file
> we expect to be UTF-8?
>

I think we should. Some popular text editors on Windows use the
initial-BOM byte sequence to distinguish between UTF-8 and "other"
encodings in text files (and of course the equivalent sequence to detect
UTF-16-BE/LE, but that's off-topic). I'm surprised we don't get more
reports about this.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-04 21:24:52 CET

This is an archived mail posted to the Subversion Dev mailing list.