Context Navigation

Changes between Initial Version and Version 1 of Ticket #943, comment 4

-                      initial
+                      v1
 Therefore, the potential data loss can be fixed by checking whether any of the destination links are the same as the link that is to be moved. This should match the expectations of users accustomed to Unix {{{mv}}} or moving files in a Windows filesystem, which would fail in the same situation. Note that we are '''not''' enforcing that it is impossible to create loops using {{{tahoe mv}}} -- that's not necessary to fix this bug.
 The link to be moved must be from a mutable directory, therefore it has an SI. So, the definition of "same as" for links can be "same parent directory SI, and same child name" (comparing child names as Unicode strings without normalization).
+The link to be moved must be from a mutable directory, therefore it has an SI. So, the definition of "same as" for links can be "same parent directory SI, and same child name" (comparing child names as Unicode strings with~~out~~ normalization).
 The later {{{mv}}}s reporting OK is a separate issue that we haven't investigated yet.
+[edit: I think when this comment was written, names were not normalized. Now they are, so the comparison should be with NFC normalization.]