Bug 26196 - I18N - BeanInfo editor is not internationalization/bundle-friendly
I18N - BeanInfo editor is not internationalization/bundle-friendly
Status: NEW
Product: java
Classification: Unclassified
Component: Beans
3.x
PC Linux
: P3 with 1 vote (vote)
: TBD
Assigned To: Jan Becicka
issues@java
: I18N
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2002-08-01 17:52 UTC by _ tboudreau
Modified: 2010-09-23 08:30 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2002-08-01 17:52:26 UTC
It is nearly impossible to use the BeanInfo editor
to generate an
internationalized BeanInfo class - it hard-codes
strings for all
of the descriptions.  It should offer the option
of automatically
generating a bundle (including generating keys) or
adding them to an
existing bundle.  This would make it much more
useful - as it is,
you have to generate the BeanInfo and then
manually remove the 
//GEN-BEGIN, etc. comments and hand edit it to use
bundles.
Comment 1 Ken Frank 2002-10-12 19:29:45 UTC
Changing to defect after consulation with nb QA and comments from nb
strategy that some i18n rfes could actually be viewed as defects. We
think this
one is more like a defect so am changing it to that. 
Let me know if more details are needed.
ken.frank@sun.com
Comment 2 Jesse Glick 2002-12-23 16:37:47 UTC
Consistent use of the I18N keyword.
Comment 3 Svata Dedic 2003-01-07 15:40:59 UTC
I do not agree this is a defect; the user *is* able to produce I18Ned
beaninfo - by using e.g. bundle.getString("") instead of plain "".
What you are asking for is rather a quite large feature/rewrite than a
bugfix.


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