On Fri, May 13, 2011 at 10:26 AM, Richard Hipp 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
> Od: "Martin Gagnon"
> Komu: fossil-users@lists.fossil-scm.org
> Datum: 20.05.2011 17:25
> Předmět: Re: [fossil-users] Pre-built binary for I18N windows
>For wrong character display on console, have you try to change you codepage
>to utf-8 (using: chcp 65001). It&#
sil-users@lists.fossil-scm.org
> > Datum: 20.05.2011 13:43
> > Předmět: Re: [fossil-users] Pre-built binary for I18N windows
> >
> >Please try again with the latest code:
> >
> > http://www.fossil-scm.org/download/fossil-w32-20110520113920.zip
> >
> >Let
> Od: "Richard Hipp"
> Komu: fossil-users@lists.fossil-scm.org
> Datum: 20.05.2011 13:43
> Předmět: Re: [fossil-users] Pre-built binary for I18N windows
>
>Please try again with the latest code:
>
> http://www.fossil-scm.org/download/fossil-w32-2011052011392
Seems to work well now for most of the test I've made with latest version.
Only one small thing still cause problem.. When I commit without specifying
-m, with no external editor defined, I cannot have accented character on
the commit message. It will see the commit like empty.
--%<-
Please try again with the latest code:
http://www.fossil-scm.org/download/fossil-w32-20110520113920.zip
Let me know what you find, either way. Thanks! And not just Martin, but
all windows users, if you can give the snapshot above a try and then report
your results to me via private email, t
On Sun, May 15, 2011 at 8:22 AM, Martin Gagnon wrote:
> On Sun, May 15, 2011 at 7:53 AM, Martin Gagnon <
> eme...@gmail.com> wrote:
>
>> Correction on my last test.. when I did the: status --sha1sum command, I
>> use the wrong fossil executable.. (I have both version on my path, the trunk
>> ver
On Sun, May 15, 2011 at 7:53 AM, Martin Gagnon wrote:
Correction on my last test.. when I did the: status --sha1sum command, I use
the wrong fossil executable.. (I have both version on my path, the trunk
version and the windows-i18n)
Finally, with --sha1sum, it show exactly the same as without
Correction on my last test.. when I did the: status --sha1sum command, I use
the wrong fossil executable.. (I have both version on my path, the trunk
version and the windows-i18n)
Finally, with --sha1sum, it show exactly the same as without it.
--%<
On Fri, May 13, 2011 at 2:07 PM, Richard Hipp wrote:
>
>
> On Fri, May 13, 2011 at 1:27 PM, Martin Gagnon wrote:
>
>> On Fri, May 13, 2011 at 1:15 PM, Richard Hipp wrote:
>> >
>> >
>> > On Fri, May 13, 2011 at 1:05 PM, Martin Gagnon
>> wrote:
>> >>
>> >> This particular problem occur since fos
On Fri, May 13, 2011 at 1:27 PM, Martin Gagnon wrote:
> On Fri, May 13, 2011 at 1:15 PM, Richard Hipp wrote:
> >
> >
> > On Fri, May 13, 2011 at 1:05 PM, Martin Gagnon wrote:
> >>
> >> This particular problem occur since fossil set the codepage to 65001.
> >> Since this, echo to console all wo
On Fri, May 13, 2011 at 1:15 PM, Richard Hipp wrote:
>
>
> On Fri, May 13, 2011 at 1:05 PM, Martin Gagnon wrote:
>>
>> This particular problem occur since fossil set the codepage to 65001.
>> Since this, echo to console all work, but now I have this problem when I
>> commit.
>
> Please try this
On Fri, May 13, 2011 at 1:05 PM, Martin Gagnon wrote:
> This particular problem occur since fossil set the codepage to 65001.
>
> Since this, echo to console all work, but now I have this problem when I
> commit.
>
Please try this new build:
fossil-w32-20110513171338.zip
Let me know how i
This particular problem occur since fossil set the codepage to 65001.
Since this, echo to console all work, but now I have this problem when I
commit.
--
Martin
Le 2011-05-13 à 12:45, Richard Hipp a écrit :
>
>
> On Fri, May 13, 2011 at 12:41 PM, Martin Gagnon wrote:
>
> I got same resu
On Fri, May 13, 2011 at 12:41 PM, Martin Gagnon wrote:
>
> I got same result as my last test with previous version:
>
Do I understand correctly that the windows-i18n branch is working for you?
Or is there some issue in the text below that I have overlooked?
>
>
> --%<-
On Fri, May 13, 2011 at 11:49 AM, Richard Hipp wrote:
> 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() prio
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
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 co
18 matches
Mail list logo
