Bug 40686 - I18N - request to add feature to set <page-encoding> from GUI
I18N - request to add feature to set <page-encoding> from GUI
Status: NEW
Product: javaee
Classification: Unclassified
Component: Code
3.x
Sun SunOS
: P2 with 1 vote (vote)
: TBD
Assigned To: Petr Pisl
issues@javaee
: I18N
Depends on: 34399
Blocks:
  Show dependency treegraph
 
Reported: 2004-03-02 14:21 UTC by Keiichi Oono
Modified: 2006-12-04 22:09 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 Keiichi Oono 2004-03-02 14:21:31 UTC
NetBeans Q-Build 200402241900

I would like to request that 'WEB-INF' icon or
'web.xml' icon has a property to set
<page-encoding> element from IDE GUI.

When I create JSP with "pageEncoding=EUC-JP" or
with "contentType="text/html; charset=EUC-JP".
That page is saved correctly by specified
encoding. But when I create JSP which does not
have these property in same web module, it's saved
as ISO-8859-1 encoding because default web.xml has
not <page-encoding> property.

I think it's better if the user can set the
page-encoding property from GUI. The current
'WEB-INF' icon and 'web.xml' icon does not have
properties which related the element in web.xml. I
guess it's removed for some reason. But when user
does not set <page-encoding> property, the  no
ISO-8859-1 characters in user's page are lost.

I think the initial web.xml should not have
<page-encoding> element, and ISO-8859-1 should be
used as default. But I would like to request to
add a feature to generate <jsp-config> element
which includes <page-encoding> element.

Would you give me your any thoughts for this?
Comment 1 Keiichi Oono 2004-03-02 14:24:16 UTC
Add I18N keyword, and I've changed from ENHANCEMENT from DEFECT
because user's edited contents are lost in worst case.
Comment 2 Petr Pisl 2004-03-04 18:10:50 UTC
I think this is enhancement. We can not add this feature now. We need
more complex solution, then just add one property. This property is
not so simple. There can be various mapping for jsp files. Every
mapping can have different encoding (this is purpose of this). We need
support both specification JSP 2.0 and the older one as well. So there
are a lot of open questions and we are not able to solve it now into 3.6 .

Comment 3 Ken Frank 2004-03-05 17:06:15 UTC
Petr,

We want to make the point, whether for this issue or others that could
be filed,
that providing user a UI way to set encoding is necessary, and is not
an enhancement
request, but an issue since its not there and we feel that ide not
providing these ways
is an issue; ide provides so many UI/properties ways to set things,
this would just be
others.

I realize that there are various encodings and scenarios - but would
like to file
one or more issues on these relating to that UI way of setting them is
not available.
(not talking here about how modules process or handle encodings, just
about UI ways
to set them)

But if your team feels that any such request is an rfe and will change
any bug filed
on it into an rfe, which in past have not been implemented for long
time, it doesnt make
sense for us to do this without more discussion.

Please give me your thoughts on this.

ken.frank@sun.com
03/05/2004


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