On 3/8/06, Philip Martin <philip@codematters.co.uk> wrote:
> "Jim Blandy" <jimb@red-bean.com> writes:
>
> > it would make sense to me if Subversion read its configuration files
> > in the system locale.
>
> Except that httpd doesn't do setlocale() so mod_authz_svn cannot do
> native to UTF8 conversions (apart from trivial conversions for ASCII
> strings). At present paths within an AuthzSVNAccessFile need to be
> UTF8 encoded and changing that to native isn't possible since
> mod_authz_svn won't be able to convert such paths to UTF8 as required
> by the Subversion filesystem. The svnserve equivalent is the authz-db
> file, and it's presently also UTF8. I suppose svnserve could do
> things differently, but that doesn't seem like a good idea to me.
The server and the client are different situations, I think. I should
have said, "the Subversion client [should] read its configuration
files in the current locale."
Unless I'm missing something, it's easy for the Subversion server code
to work in UTF-8, even though httpd can't call setlocale. As long as
we use the byte input/output functions (i.e., not the wide character
ones), we'll get direct byte values from the files, which we can then
just use as UTF-8, perhaps after checking that they're a well-formed
sequence of UTF-8 characters.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 8 22:52:46 2006