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.

Bug 102370 - I18N - validation messages in output window weren't localized
Summary: I18N - validation messages in output window weren't localized
Status: RESOLVED WONTFIX
Alias: None
Product: xml
Classification: Unclassified
Component: Validation (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Sonali Kochar
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2007-04-24 16:56 UTC by kaa
Modified: 2007-08-22 23:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
xml validation output (71.60 KB, application/octet-stream)
2007-04-24 16:57 UTC, kaa 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kaa 2007-04-24 16:56:59 UTC 
Some of XML validation messages in output window were without pseudo.
This log is visible to a user thus should be localized.I'm running in the ja
locale, using a pseudo localized netbeans and the given message does not come
from the pseudo localized jar file.
Comment 1 kaa 2007-04-24 16:57:34 UTC 
Created attachment 41566 [details]
xml validation output
Comment 2 Sonali Kochar 2007-08-21 19:56:46 UTC 
The validation messages (the ones not localized) are coming from
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.java

This code is from apache and apache.org does not localizing the error messages. Since the code is outside the netbeans
code base, I am not sure on how to fix these messages. Please advice on how to proceed on this bug
Comment 3 Sonali Kochar 2007-08-22 23:07:15 UTC 
The code gets an org.xml.sax.SAXParseException. This class is from the J2SE code base. We do
SAXParseException.getLocalizedMessage() and then display the localized message. I looked at SAXParseException source
code and they do not localize the exception message. Since the exception msg is from jdk, there isnt much we can do here.