Re: [fossil-users] Is there a setting to make fossil handle UTF-8 correctly in file names and folder names?
On Wed, Nov 28, 2012 at 5:32 PM, Konstantin Khomoutov flatw...@users.sourceforge.net wrote: On Wed, Nov 28, 2012 at 02:56:09PM -0500, Richard Hipp 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'm just handwaving, but Git's code base recently received some modifications to specifically deal with issues a native Mac OS X filesystem have with regard to UTF-8. AFAIK the deal was about that filesystem pefrorming one of standard UTF-8 normalizations either when writing or when reading (or both) so that when you create a directory entry and then read it back, you might get an octet string different from that you wrote. See the extensive commit message in [1] and [2] in general. 1. https://github.com/git/git/commit/76759c7dff53e8c84e975b88cb8245587c14c7ba 2. http://en.wikipedia.org/wiki/HFS_Plus ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Checkin [ca728447a6] breaks fossil on WinXP SP3 32 bit compiled under MINGW32. Lots of compilation warnings but compile creates fossil.exe. Checkin [3527aa4474] still compiles and runs fine. Here are some attempts at running the compiled checkin [ca728447a6] (fo is an alias for fossil). 11:26:07 $ fo Usage: `A?A COMMAND ... or: `A?A help -- for a list of common commands or: `A?A help COMMMAND -- for help with the named command 11:27:21 $ fossil Usage: `??A COMMAND ... or: `??A help -- for a list of common commands or: `??A help COMMMAND -- for help with the named command 11:27:29 $ fossil help ??: ??: unknown command: ?? ??: use help for more information ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is there a setting to make fossil handle UTF-8 correctly in file names and folder names?
On Thu, Nov 29, 2012 at 12:36 PM, John Smith johnqzm...@gmail.com wrote: Checkin [ca728447a6] breaks fossil on WinXP SP3 32 bit compiled under MINGW32. Lots of compilation warnings but compile creates fossil.exe. Fixed now. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is there a setting to make fossil handle UTF-8 correctly in file names and folder names?
On Thu, Nov 29, 2012 at 12:22 PM, Richard Hipp d...@sqlite.org wrote: Fixed now. Still getting multiple compile warnings, but it's working. Thanks for the quick fix. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is there a setting to make fossil handle UTF-8 correctly in file names and folder names?
On Thu, Nov 29, 2012 at 12:22 PM, Richard Hipp d...@sqlite.org wrote: Fixed now. Warnings all gone after updating to [9eb2df37ef]. Awesome job. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is there a setting to make fossil handle UTF-8 correctly in file names and folder names?
On Wed, Nov 28, 2012 at 2:50 PM, Frans van Dunné fr...@southshield.netwrote: 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? The wiki pagenames do not handle special characters gracefully either. I have not come accross any issues at all with the content of files or wikipages. Only with the names. Wiki pagenames should also handle non-ascii characters. If they do not, that is also a bug. Please send in a bug report with steps to reproduce the problem and the specific version of fossil that demonstrates the problem. Thanks! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is there a setting to make fossil handle UTF-8 correctly in file names and folder names?
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
Re: [fossil-users] Is there a setting to make fossil handle UTF-8 correctly in file names and folder names?
On Wed, Nov 28, 2012 at 02:56:09PM -0500, Richard Hipp 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'm just handwaving, but Git's code base recently received some modifications to specifically deal with issues a native Mac OS X filesystem have with regard to UTF-8. AFAIK the deal was about that filesystem pefrorming one of standard UTF-8 normalizations either when writing or when reading (or both) so that when you create a directory entry and then read it back, you might get an octet string different from that you wrote. See the extensive commit message in [1] and [2] in general. 1. https://github.com/git/git/commit/76759c7dff53e8c84e975b88cb8245587c14c7ba 2. http://en.wikipedia.org/wiki/HFS_Plus ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
