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

Re: Let's discuss about unicode compositions for filenames!

From: Hiroaki Nakamura <hnakamur_at_gmail.com>
Date: Fri, 3 Feb 2012 05:28:40 +0900

2012/2/3 Branko Čibej <brane_at_xbc.nu>:
> On 02.02.2012 20:59, Hiroaki Nakamura wrote:
>> So we need to change servers too. When servers read filenames from
>> repositories, they first convert to NFC and then process commands.
> That won't work. You have to do the initial lookup in a
> normalization-agnostic way, and neither BDB nor FSFS makes that possible
> wihout scanning whole directories.

OK, then do scan whole directories. If you do not want that,
we force users to convert existing repositories. I think we must
choose one of the two. Tough choices, but I cannot think of a
better way at least right now.

>> We also need to changes servers in order to deal with existing 1.x
>> clients. We convert filenames to NFC when web_dav_svn and svnserve
>> receive filenames from clients, they must first convert filenames to NFC.
> Actually, libsvn_repos; this has to work with ra_local as well. And it
> would have to maintain a table for converting results back to how the
> client knows them. This is the hard part to get right; imagine:
>    $ svn up
>    U čombe
> How will the server know if the client represents the "č" in the same
> encoding that the now-normalizing server sends? Will the client scan the
> directory and normalize the names to find the local file that needs
> updating?

Yes, without upgrading working copies, we must do that.

If there is a better way, I would like to know.
Please give us better solution if you have an idea > all.

)Hiroaki Nakamura) hnakamur_at_gmail.com
Received on 2012-02-02 21:29:12 CET

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