I18N windows users: please try this version:
http://www.fossil-scm.org/download/fossil-w32-20110513154610.zip
This newer version translates the UTF8 used internally by Fossil into the
code page obtained from GetConsoleCP() prior to displaying the text.
Formerly, the UTF8 was being translated into the CP_ACP code page, which is
the code page used for filenames passed to system calls. The two are
different, it seems. I think with this change, we might be close to fixing
the I18N problems. Please try it out and let me know.
Rebuild from sources if you are able. Thanks!
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
>
> 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
