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 22683 - I18N - MonitorBundle.properties is not included in l10n.lit
Summary: I18N - MonitorBundle.properties is not included in l10n.lit
Status: CLOSED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: HTTP Monitor (show other bugs)
Version: -FFJ-
Hardware: All All
: P3 blocker (vote)
Assignee: Ana.von Klopp
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2002-04-23 03:49 UTC by jf4jbug
Modified: 2003-02-22 17:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jf4jbug 2002-04-23 03:49:31 UTC
tomcat401/lib/httpmonitor.jar and
j2sdkee1.3.1/lib/system/httpmonitor.jar has
the following localized file.

org/netbeans/modules/web/monitor/server/MonitorBundle_ja.properties

However, this base file is not included in
l10n.list.

If this file is localizable, please add the
following entry to l10n.lit.

monitor/src/org/netbeans/modules/web/monitor/server/MonitorBundle.properties

If not, these files should no be included in .jar
files.
Comment 1 Ken Frank 2002-04-23 04:35:24 UTC
The text of this file says it should not be localized or on l10n.list.

So if not, I  do agree with request of this bug to remove it from the
build.

 Even in english only build, this jar file,
and the httpmonitor.jar file in modules/ext, has both the ja and non
ja
Bundle.properties and this MonitorBundle.properties_ja.jar translated.

Can the build of English only have just the Bundle.properties files of
httpmonitor.jar  just like
all other jar files in FFJ from nb or ffj  in any case, and not the
_ja.properties files ?

ken.frank@sun.com
04./22/2002
Comment 2 Ana.von Klopp 2002-04-23 17:14:16 UTC
The MonitorBundle.properties file contains a set 
of standard status messages that servers generate
as a result of processing a request. The appropriate
message is included with the HTTP headers in the 
response. We did some investigation of this when I
started working on the monitor and we discovered that
these messages typically are not localized. For this
reason we decided not to localize them also, since 
doing so would probably would not be helpful (users
would not be familiar with translated versions of 
these). 

One of these will appear on the request pane on the 
monitor, in the exit status field. If all goes well, 
it is set to 200: OK. You can use lynx and set the 
flag to show the header to connect to a bunch of 
servers around the world, you will find that the 
HTTP status header typically returns English messages. 

IMHO this is not a bug. The file should be included 
in the jar file and should not be translated, so the 
i18n list is correct as it is. It's the localized 
version that should be taken out. 

We should revise this discussion if we find that 
servers have started to translate these messages. 
I would be grateful if Ken and the submitter of this
bug could add a message here to indicate whether you
are OK with this. If so, please remove the localized
file and close the bug. 
Comment 3 Ken Frank 2002-04-23 18:11:15 UTC
The explanation below is ok with me. Please wait for the
localization center who filed it to comment later tonite.

Separately, I'm asking RE to remove the _ja.properties
from the jar files in the english only build, but that is not
really related to this issue.

ken.frank@sun.com
04/23/2002
Comment 4 Ana.von Klopp 2002-05-22 17:46:21 UTC
Still no comment from Japan. I assume we have agreed on 
this now. 
Comment 5 jf4jbug 2002-05-23 01:12:21 UTC
I am sorry for the late reply.
We are ok, so pleare remove _ja.properties from .jar.
Thanks,
Yuko
Comment 6 Jesse Glick 2002-12-23 16:37:00 UTC
Consistent use of the I18N keyword.