On 28 November 2012 20:56, Richard Hipp <d...@sqlite.org> wrote: > > > On Wed, Nov 28, 2012 at 2:50 PM, Frans van Dunné <fr...@southshield.net> > wrote: >> >> >> Is this a configuration issue? Or can fossil not handle special >> characters in file and folder names? > > > Fossil is suppose to handle non-ASCII characters in filenames correctly. If > it does not, that is a bug. What version of Fossil are you running? Can > you send in a detailed bug report with steps to reproduce the issue?
I guess this issue stems from different Unicode handling on the OS level. While Ubuntu stores whatever you write OS X normalizes (decomposes?) Unicode on HFS. Then what you write as file name on Ubuntu will be transferred to the Mac, there normalized by the OS to a (possibly) different string that looks the same and on subsequent transfer to Ubuntu a new file or directory with seemingly same name may be created. Since OS X also conflates case by default you can model this somewhat more visibly by transferring a file to OS X and there changing the case of the file name. You will have to actually move the file twice because just changing the case fails as any move to itself does. Thanks Michal _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
