You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Tobias Hinnerup <to...@hinnerup.net> on 2008/01/04 15:37:10 UTC
RE: National characters in authz-db path entries
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!
Regards,
Tobias Hinnerup
Hinnerup Net ApS
Mob: (+45) 20 32 90 02
E-mail: tobias@hinnerup.net
Web: www.hinnerup.net
-----Original Message-----
From: Branko Čibej [mailto:brane@xbc.nu]
Sent: 31. december 2007 13:10
To: Tobias Hinnerup
Cc: dev@subversion.tigris.org
Subject: Re: National characters in authz-db path entries
Tobias Hinnerup wrote:
>
>
>
> It appears that national characters are not handled correctly in
> authz-db path entries. The example below gives the user User2 the file
> NationalØ.txt but not the file NationalOE.txt. The behavior is a best
> inconsistent and the most logical behavior would, as I see it, be that
> none of the two files are given to User2, but both of them to User1.
>
Try saving your authzdb file in UTF-8.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: National characters in authz-db path entries
Posted by Julian Foad <ju...@btopenworld.com>.
Branko Čibej wrote:
> Erik Huelsmann wrote:
>>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.
I've raised Issue #3082
<http://subversion.tigris.org/issues/show_bug.cgi?id=3082>, enhancement, "Allow
a Byte Order Mark (BOM) in UTF-8 input files".
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: National characters in authz-db path entries
Posted by Branko Čibej <br...@xbc.nu>.
Erik Huelsmann wrote:
> On 1/4/08, Tobias Hinnerup <to...@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@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: National characters in authz-db path entries
Posted by Erik Huelsmann <eh...@gmail.com>.
On 1/4/08, Tobias Hinnerup <to...@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?
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org