Bug 98897 - I18N - editable encoding property needs to be implemented in jsp files property editor
I18N - editable encoding property needs to be implemented in jsp files proper...
Status: NEW
Product: obsolete
Classification: Unclassified
Component: visualweb
5.x
PC Windows XP
: P3 (vote)
: TBD
Assigned To: _ potingwu
issues@obsolete
: I18N
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-26 01:48 UTC by bugbridge
Modified: 2007-03-27 18:57 UTC (History)
2 users (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 bugbridge 2007-03-26 01:48:59 UTC
Original status: 1-Dispatched; Suggested Status: NEW


Original submitter: sunlit

Description:
this is connected with  CR 6260484  fde I18N - jsp 
> file does not have encoding property as before which was fixed by adding a
read-only property

so now we have a read-only encoding property of jsp files, 
I am aware that this is how it is in NB, but in Creator it is advisable that
this be changed to R/W with the view of our customers working in other locales,
and remembering  that in previous releases encoding properties of files were
editable from property editors. It would be consistent with property editor that
appears when user clicks on an empty design area of a web-page - there the
encoding property is editable.


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