Community
Participate
Working Groups
<response_by> Enric Arau Elias at 2008.05.20.19.02.04 </response_by> Description: OS: Linux Build date: 0519 Component/Function name: WTP Testcase number: 3.003760 Blocking: NO Language: Spanish Tester Name: Enric Arau When I start any server, in this case Tomcat v5.5, I see one corrupted character in the Console. The character is the accented O (?) of the word INFORMACI?N. I am attaching a screen capture. Please check and advise, Enric Arau Elias Spanish Tester <response_by> Matthew Mazaika at 2008.05.21.14.03.20 </response_by> Any server? Or just versions of Tomcat? <response_by> Enric Arau Elias at 2008.05.22.19.16.45 </response_by> I only tried with versions of tomcat. I have also tried on Windows and the corruption is still there. Please see the screen capture for more details. Enric Arau Elias Spanish Tester <response_by> John Ryding at 2008.05.23.08.53.01 </response_by> This article was reassigned from Category:''TVT/Testing,Inbox''.
Created attachment 101736 [details] WTP_3.003760b.JPG
<cde:tctdetail> Testcase: 3.003760 Project: WSW34 Component: Xfer - Web Tools/jst.server Priority: 3 Subject: ES: Corrupted character in Console Article ID: 467 Originator: enric_arau@es.ibm.com </cde:tctdetail>
WTP is just launching Tomcat as a regular Java app (using JDT API) - is it possible that the OS charset is not being picked up or the current font doesn't support this character?
<response_by> Enric Arau Elias at 2008.05.27.14.37.19 </response_by> I checked the japanese version and it is ok. I believe the string is in ASCII codepage and the console displays it in ANSI codepage, hence the corruption. The problem is we cannot find this string in our translation memories, so there is nothing we can do to fix. This could be a code problem, not using the right encoding for the Spanish language.
Does the WTP launcher specify a console encoding and system property (-Dfile.encoding property) that match? A console encoding can be specified via an ILanuch property (get/setProperty()), using the DebugPlugin.ATTR_CONSOLE_ENCODING attribute key. And a vmarg can be added to the command line when launching (-Dfile.encoding).
See comment #3. JDT does add a file encoding (-Dfile.encoding=Cp1252 on my machine), but I don't see any evidence of DebugPlugin.ATTR_CONSOLE_ENCODING being used (at least by default) in Java launches.
<cde:tctdetail> Testcase: 3.003760 Project: Component: Xfer - Web Tools/jst.server Priority: 3 Subject: ES: Corrupted character in Console Article ID: 467 Originator: enric_arau@es.ibm.com </cde:tctdetail>
<response_by> Matthew Mazaika at 2008.06.12.11.44.33 </response_by> This bug has been deferred. It will be considered for the 3.4.1 service pack.
Does this still happen? If so, which JRE are you using? If you use an IBM JRE it might be a duplicate of bug 349465.
Created attachment 198149 [details] Tomcat I think the message is from Tomcat. I started a Tomcat server from outside Eclipse. I saw the same problem.
OK, but that's not the Eclipse console. It looks like a Windows command shell. Does that console have the correct code page and a font that can render the corresponding characters?
Created attachment 198268 [details] 233677-Spanish.png Not sure if I'm missing anything in the setup. I only see the "INFO" prefix in the console. Anyway, the Spanish "ó" character is displaying okay in the console. The console should have the correct code page and font to render the Spanish characters properly.
>Anyway, the Spanish "ó" character is displaying okay in the >console. In that case we can close this bug or move to some other component that opens the command console?
Attachment 198149 [details] shows that the "ó" character does not display correctly even outside Eclipse. I think this is a problem in the Tomcat translations. We probably should resolve this as "NOT_ECLIPSE".
(In reply to comment #15) > Attachment 198149 [details] shows that the "ó" character does not display correctly even > outside Eclipse. I think this is a problem in the Tomcat translations. We > probably should resolve this as "NOT_ECLIPSE". How did you get the command console? Was it opened by Eclipse? If so, the plug-in that opens it could fix the problem by setting the correct code page.
The command console for attachment 198149 [details] was started from outside Eclipse by launching "tomcat\bin\startup.bat".
(In reply to comment #17) > The command console for attachment 198149 [details] was started from outside Eclipse by > launching "tomcat\bin\startup.bat". Thanks for the info.
