Hi,

Von: Stefan Sperling [mailto:s...@elego.de] 
> On Sun, Jan 29, 2012 at 07:38:44PM +0900, Hiroaki Nakamura wrote:
>> I read the note about unicode compositions for filenames 
>> http://svn.apache.org/repos/asf/subversion/trunk/notes/unicode-composition-for-filenames
>>  and would like to drive the discussion.
[...]
> We could also open the parent directory, read all the filenames within it, 
> normalise them all, and then search the resulting list. This works, expect if 
> a name exists twice, once in NFC form and once in NFD form. We'd somehow have 
> to solve the name collision in the filesystem.

This sounds astonishingly similar to the lower/upper case problem of UN*X vs. 
Mac/Win.

> But it gets worse. Recall the filesystem name collision problem mentioned 
> above. This problem can also happen in the repository filesystem! For 
> instance, assume that in the repository there already exist two filenames, 
> one NFD, the other NFC, but they both are actually the same name.

The same here. So whatever solution is found for one of those problems could 
also help to solve (or mitigate) the other problem.

> These are the questions which we'll need to answer to solve this issue.
> I honestly do not have good answers. I hope that you will find ways of 
> solving these problems.

Maybe the best solution to this issue is a client-only solution, in a similar 
way the case sensitivity problem is tackled.


Best regards

Markus Schaber
-- 
___________________________
We software Automation.

3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax 
+49-831-54031-50

Email: m.scha...@3s-software.com | Web: http://www.3s-software.com 
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects: 
http://www.3s-software.com/index.shtml?sample_projects

Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade 
register: Kempten HRB 6186 | Tax ID No.: DE 167014915 


-----Ursprüngliche Nachricht-----

Reply via email to