On Fri, May 13, 2011 at 10:26 AM, Richard Hipp <[email protected]> wrote:
> If you are using Fossil on windows with a non-ASCII character set, and > especially if you are having trouble, please consider using the windows-i18n > branch build that can be downloaded from > > http://www.fossil-scm.org/download/fossil-w32-20110513142012.zip > Thanks for the testing, everyone! Bug fixes have been applied. A new build can be found at: http://www.fossil-scm.org/download/fossil-w32-20110520153145.zip Please try out this new one and let me know if you encounter any difficulties, especially with non-ASCII filenames. > > Getting command-line programs to work correctly on windows is a real > problem. I have yet to find anybody who can explain how to do it. But if > we keep plugging at the problem, perhaps we'll eventually get it right. > Your feedback is important. If you are able to run Fossil in a debugger and > provide clues about how we could do windows I18N better, that would be even > better. > > Anyone with ideas on how to get a command-line program working reliably on > I18N windows, please speak up. > > -- > D. Richard Hipp > [email protected] > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
