On Thu, Jan 17, 2008 at 07:09:43PM +0100, Mark Junker wrote:No, the encoding was the same -- UTF-8. MacOSX converts one sequence of Unicode characters to *another* sequence, which are canonical equivalent, but being canonical equivalent does not mean they are the same characters. In the same way, as being compatible equivalent does not mean being the same. As well as, being case-insensitive equivalent does not mean being the same... Do you remember DOS? It stored all filenames in upper-case, so they original and stored names are case-insensitive equivalent, but they are not the same! Dmitry - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| jjohansen | [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Andrew Morton | 2.6.23-rc6-mm1 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Evgeniy Polyakov | Re: [BUG] New Kernel Bugs |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
