On Fri, 2005-12-23 at 11:29 +0100, Lele Gaifax wrote:
> David Houghton ha scritto:
> > Am I right to understand that the problem is an sequence of bytes in the
> > rlog output that are not parsable as utf8? And does anyone have any
> > suggestions for how to fix this? I'm afraid I don't know Python.
>
> Yes, you are right. Are you sure that the upstream CVS repo uses UTF-8
> as encoding? There's an option "encoding-errors-policy" that you can set
> to "ignore", instead of the default "strict" that raises the error you
> experienced.
Ah, great! This is perfect.
I'm fairly certain the CVS repository uses ASCII or UTF-8, and the
latter should accomodate the former. I tried this in a UTF-8 terminal:
cvs -f
-d :pserver:[EMAIL PROTECTED]:/streamsage/cvsroot
rlog -N -r:HEAD java 2>&1 | tr -d '[:alnum:][:blank:][:punct:]'
| sort -c
I thought this would filter out all but the bad characters, but it
filtered out everything.
Thanks for writing this great program! It saves me a lot of effort and
makes me look more talented than I am.
David
>
> hope this help,
> ciao, lele.
> _______________________________________________
> Tailor mailing list
> [email protected]
> http://lists.zooko.com/mailman/listinfo/tailor
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
