Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 60506 - I18N - i18n support for JSF/JSP
I18N - i18n support for JSF/JSP
Product: java
Classification: Unclassified
Component: I18N
All All
: P2 with 1 vote (vote)
: 6.x
Assigned To: Ralph Ruijs
: I18N
Depends on:
  Show dependency treegraph
Reported: 2005-06-24 23:01 UTC by ieising
Modified: 2011-11-28 09:21 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description ieising 2005-06-24 23:01:27 UTC

I would like to see NB be able to internationalize JSF pages as well as other
Java code.
Now it is really tedious to do this all by hand, ever so more when you know that
any Swing app can be handled in the blink of an eye.

Comment 1 Marian Petras 2005-06-27 12:28:29 UTC
Accepted. However, we do not have enough resources (people) currently to make
this happen for NB 4.2 (and probably for the next release either).
Comment 2 Ken Frank 2006-05-04 17:59:41 UTC
moving to p2 as with more functionality in webapps and j2ee, this seems like
an important feature and one that can complement the existing functionality
for java.
Comment 3 Pavel Buzek 2006-05-15 19:58:52 UTC
i18n is pretty simple in jsf:

<f:loadBundle basename="filename" var="aaa">

and then use #{}

It would be useful to have code completion for filename (a file in source
packages with ext "properties") and then have the variable aaa in code
completion with completion for keys in bundle -- values for various locales (or
at least default locale) can be shown in javadoc area for the code completion.

Support for i18n action in Tools menu would be even nicer (to detect strings).
Currently it insers java code, it should insert jsf code. It cannot detect
strings in jsf that need to be localized (maybe not easy?). There is some
support in i18n but seems very poor. 

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo