2013/4/8 Stefan Bellon <sbel...@sbellon.de>
> On Sun, 07 Apr, Richard Hipp wrote:
>
> > Huh. Turns out if you redirect output into a file, rather than
> > trying to display it on a console, it works.
> [...]
> > (1) Work around the issue by redirecting lengthy outputs into a file
> > rather than trying to show them on the console.
>
> It's not about "showing", it's about automating. But yes, that might be
> the solution for the moment, writing to a file and reading that instead
> of just piping the output. Might be a bit slower, but at least it
> should work.
>
> Thanks for the quick and precise analysis and workaround hints!
>
There's also an option (5)
(5) Just automate it, doing nothing special.
If the consile output is redirected, no matter where to
(a file or a pipe), the output will be done as-is. When
not re-directed, the console code assumes that
it is in UTF-8, converts it to unicode, and writes that
to the console. The 'bug' is in this conversion, but
if stdout is redirected this conversion doesn't take
place at all.
So, don't be fooled by this console output. When
automating this, everything should work OK.
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
