Platform: Tapestry 4 beta 5 Problem Description:
While using Tapestry 4, beta 5, extended ASCII character 149 is NOT being encoded as the string •. Interestingly, Tapestry 3.0.3 DOES encode the ASCII 149 character correctly. I am interested in knowing if anyone else has encountered this issue. Scenario sample code is available if needed. Lastly, other extended ASCII codes were also tested, some are properly encoded and some are not; I am focusing on the ASCII 149 due to an application specific need. All comments, suggestions & resolutions are welcomed and encouraged. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
