Hi Alexander,

This definitely looks like a JUnit issue! Could you post a message on
the junit mailing-list as we can't help you here. Maybe it is fixed in
JUnit 3.8?

Thanks
-Vincent

> -----Original Message-----
> From: Alexander Lepekhine [mailto:[EMAIL PROTECTED]]
> Sent: 26 August 2002 13:02
> To: Cactus User List
> Subject: National chars in assertEquals
> 
> Hi, all!
> May be this is junit problem rather then cactus.
> I got different messages in log4j and cactus reports:
> 
> logger.info(string)
> 
> gives string in my local encoding (windows-1251), but
> 
> assertEquals("no errors", string)
> 
> gives question marks instead of localized
> string characters in junit text report.
> How to improve it?
> Alexander
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:cactus-user-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:cactus-user-
> [EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to