This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | I18N - AS localized log messages don't display correctly in output window | ||
---|---|---|---|
Product: | serverplugins | Reporter: | Ken Frank <kfrank> |
Component: | Sun Appserver 8 | Assignee: | issues@serverplugins <issues> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | jf4jbug |
Priority: | P2 | Keywords: | I18N |
Version: | 4.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | server log from ja AS |
Description
Ken Frank
2005-01-06 16:28:58 UTC
if you did not really test this on nb4.1 I would close the bug... The code between nb anf studio ia really different. Guessing is not enough there. Ludo, I don't know about guessing; but would appreciate more information - how do you handle the encoding processing for things sent to output window ? I do realize things need to be tested but also specs and details it seems should be provided to those doing the testing. I don't think thats an unusual approach, and as part of test preparations will be asking for other such information; Just testing without knowing details and then seeing if a bug or not does not seem to me to be most efficient approach. Thanks - Ken the plugin opens the server.log file as a a stream with utf-8: filestream = new FileInputStream(fileName); ins = new BufferedReader(new InputStreamReader(filestream,"UTF-8"));//NOI18N Would that be enough? 4736624 is marked as fixed and verified so I think the fix is there in nb 4.1, unless you see another issue. was fixed in 2002 the recent problem, filed as bt issue 6214692, is that now AS emits log in encoding of system locale (or locale as specified in server.xml) - so if the filestream = new FileInputStream(fileName); ins = new BufferedReader(new InputStreamReader(filestream,"UTF-8"));//NOI18N does not take that into account, then the issue may be in plugin code here as it seems to be now with closed src one in jse. BTW, I did get pointers to the in process localized pkgs for the AS we use in nb4.1 so once those are installed, this kind of testing will be easier; Also, on the other issue about verifier output - will see what Vela says if AS verifier output is localized wrt that window. I don't know if verifier output that shows in the area where output window resides uses that output window or is its own window, but I don't think it matters as to the encoding part. ken.frank@sun.com Can you send me a log file that would show this behaviour? gif of output window attached - this is from user running jse bow but if the same encoding is being used (utf-8) by the nb4.1 and the as plugin for bow, then it could be valid; I still need to set up the localized situation for AS for AS 8.1 for nb4.1 I will also ask for text file of the log file. the dots and random ascii seen in the gif seems to the kind of chars that could be seen when utf-8 was being used when the encoding is the system default in this case ja (but it could be any encoding set in server.xml) ken.frank@sun.com Created attachment 19540 [details]
server log from ja AS
new / invalid |