ゆうちょのATMは9時からだったので、それまで待ってからお金おろして帰りますね
--
2012/2/17 Vincent Lefevre :
> On 2012-02-17 13:54:35 +0900, Hiroaki Nakamura wrote:
>> Actually, whether filename is in NFC or NFD depends on the way of
>> inputting filenames.
>> If you type all characters, it is in NFC.
>
> No, or actually, perhaps this depends on th
se shell filename completion by hitting tab key, it is in NFD.
I tried with Japanese filenames and confirmed this.
So, it is HFS+ which returns the filenames in NFD.
--
)Hiroaki Nakamura) hnaka...@gmail.com
2012/2/11 Branko Čibej :
> On 11.02.2012 13:05, Hiroaki Nakamura wrote:
>> 2012/2/9 Markus Schaber :
>>> Von: Stefan Sperling [mailto:s...@elego.de]
>>> On Thu, Feb 09, 2012 at 12:20:14AM +0900, Hiroaki Nakamura wrote:
>>>>> [Upgrade options / ba
st let users to choose whether filenames are normalized or not
per repository.
--
)Hiroaki Nakamura) hnaka...@gmail.com
2012/2/9 Markus Schaber :
> Hi,
>
> Von: Stefan Sperling [mailto:s...@elego.de]
>
> On Thu, Feb 09, 2012 at 12:20:14AM +0900, Hiroaki Nakamura wrote:
>> > [Upgrade options / backwards compatibility for proposed unicode
>> > normalization fix]
>
>> - Need
rily.
>
> Anything else? I cannot think of more questions but there might
> be more things to consider here.
--
)Hiroaki Nakamura) hnaka...@gmail.com
lized to NFC.
- NFD: input paths are normalized to NFD.
For compatibility, repositories which don't have this config are treated as
'none' specified.
Clients have to look this config and will normalize paths appropriately.
--
)Hiroaki Nakamura) hnaka...@gmail.com
2012/2/7 Branko Čibej :
> On 06.02.2012 22:26, Hiroaki Nakamura wrote:
>> The Unicode Standard says canonical equivalent sequences should be
>> interpreted the same way.
>> * 1.1 Canonical and Compatibility Equivalence
>> http://unicode.org/reports/tr15/#Cano
2012/2/6 Stefan Sperling :
> On Mon, Feb 06, 2012 at 02:28:40PM +0100, Branko Čibej wrote:
>> On 06.02.2012 14:10, Hiroaki Nakamura wrote:
>> > Hi, all.
>> >
>> > It seems there is no further discussion.
>> >
>> > I think the conclusion for th
update my patch and post it to
http://subversion.tigris.org/issues/show_bug.cgi?id=2464
Best regards,
--
)Hiroaki Nakamura) hnaka...@gmail.com
put buffer.
>
> That statement seems to be talking about converting between NFC and NFD, not
> from un-normalized to normalized.
Yes, indeed.
So, we need to normalize input paths before processing.
We choose NFC as normalization form.
--
)Hiroaki Nakamura) hnaka...@gmail.com
27; with subversion 1.7 client on wc created by 1.6,
I see these message and cannot use it with 1.7.
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: Working copy '/your/wc/path/here' is too old (format 10,
created by Subversion 1.6)
--
)Hiroaki Nakamura) hnaka...@gmail.com
2012/2/3 Peter Samuelson :
>
> [Hiroaki Nakamura]
>> Existing repositories, I think it would be better to convert them too using
>> svndump/svnload. And we change svnload to convert filenames to NFC.
>> However in reality we cannot force users to convert every existing
2012/2/3 Daniel Shahaf :
> Branko Čibej wrote on Thu, Feb 02, 2012 at 21:03:47 +0100:
>> On 02.02.2012 20:22, Peter Samuelson wrote:
>> > [Hiroaki Nakamura]
>> >> In option (2), we do n12n on all clients on all platforms, and we
>> >> include web_dav_svn i
2012/2/3 Branko Čibej :
> 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
2012/2/3 Peter Samuelson :
>
> [Hiroaki Nakamura]
>> In option (2), we do n12n on all clients on all platforms, and we
>> include web_dav_svn in "clients". So we convert all input paths to
>> the "server encoding", which is NFC.
>
> Indeed. But th
em and we will be happy ever after!
--
)Hiroaki Nakamura) hnaka...@gmail.com
subversion-1.7.2-NFC.diff
diff -ruN subversion-1.7.2.orig/subversion/include/svn_utf.h
subversion-1.7.2/subversion/include/svn_utf.h
--- subversion-1.7.2.orig/subversion/include/svn_utf.h 2009-11-17
04:07:17.00
18 matches
Mail list logo
