On Mon, May 9, 2011 at 6:21 PM, Richard Hipp <[email protected]> wrote:
> > > On Mon, May 9, 2011 at 5:22 PM, Konstantin Khomoutov < > [email protected]> wrote: > >> The console in Cyrillic Windows does really use two completely different >> code pages for input and output. >> Supposedly they are different for any l10n of Windows, as the OP stated, >> just for some code pages like Latin-1 this makes no difference. >> > > Can you suggest changes to the fossil_utf8_to_mbcs() and > fossil_mbcs_to_utf8() functions that will get Fossil working correctly on > windows with Cyrillic? > Perhaps my windows i18n strategy is wrong. Perhaps I should only convert from utf8 to mbcs before making system calls (fopen(), unlink(), opendir(), etc) and should not try to do mbcs-to-utf8 conversion for command line input or utf8-to-mbcs conversion for command-line output. Instead, of converting input and output, simply ask the user to run "chcp 65001" prior to running Fossil? Or, perhaps the command-line is just hopelessly broken on windows and we should simply ignore this problem all together? Just say that Fossil works in all languages on unix and in English for windows? > > >> >> _______________________________________________ >> fossil-users mailing list >> [email protected] >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > > > > -- > 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
