Mauro, thanks again for the very verbose explanation. It confirms some of the errors others reported.
> To sum this up: the suggestion given by Markus Kling seems to work > perfectly in our environment. The only problem we still have with commit > comments issued by Linux clients is not due to Scmbug. > > __UPDATE:__ I just discovered how to configure Eclipse to use the > ISO-8859-1 encoding when interacting with the CVS server: now our Linux > developers can commit changes with comments with non-corrupted non-ASCII > characters, too! :-) This confirms once more that Scmbug is working > perfectly in our environment now. Are the machine Scmbug runs on and the machine Bugzilla runs on different machines? > The only thing is not clear to me is the following: what if we were > using another charset as the one used for our sources? That is, what > would happen if we stored the sources in the CVS server in UTF-8 too? I think the solution is for Scmbug to dynamically detect the charset during the post-commit activity, and then have the glue supply that charset information over to the daemon. > All may work correctly anyway, or some corruptions may occur (for > instance: the notification e-mail is sent in ISO-8859-1 charset, so > would a conversion from UTF-8 occur?). To reply to this question I would > need a deep knowledge of Perl, Scmbug and all of the components involved > in the whole process, but unfortunately I don't. However, I hope this > helps you in some way. It is very helpful. Thanks again for the feedback.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
