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 71006 - NetBeans 4.1 does not support pageEncoding attribute of <%@page %> directive in JSP editor
Summary: NetBeans 4.1 does not support pageEncoding attribute of <%@page %> directive ...
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP Parser (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Petr Pisl
URL:
Keywords:
Depends on: 42638
Blocks:
  Show dependency tree
 
Reported: 2006-01-04 16:21 UTC by javese
Modified: 2006-01-06 16:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description javese 2006-01-04 16:21:24 UTC 
In NetBeans 4.1, JSP editor doesn't support code like :

<%@page pageEncoding="GB18030" %>
... some text in charset GB18030...


The chinese characters encoded in charset GB18030 cannot be shown correctly, as
if they were parsed as charset UTF-8.

The same bug also exists in Sun Java Studio Enterprise 8 which was built from NB
4.1. However, it doesn't exist in NB4.0 & NB5.0beta2.
Comment 1 Petr Pisl 2006-01-05 10:22:08 UTC 
We did some fixes in this area. We also improve handling encoding for pages,
which are not located under web document base. Where are your pages located? 

You wrote that this work in NB5.0. If this is true, than the issue should be
nmarked as fixed in 5.0.

Adding JSE keyword, because this issue is in the Sun Java Studio 8.
Comment 2 javese 2006-01-06 13:57:35 UTC 
Thanks very much!

The pages are under the sub folders of web application base.

Another problem is that in JSP fragment (.jspf) files there is no page encoding
directive, so NetBeans would be unable to handle them correctly if they
contained characters in different encodings. I suggest that NB should allow the
user to specify an charset encoding after opening the document. At present the
user may open the properties dialog of the document to check the file encoding
but cannot change it.
Comment 3 Petr Pisl 2006-01-06 15:04:21 UTC 
There is missing general approach, how to handle encoding and store outside the
file. See issue #42638. We need to convince guys form core to build this A/SPI.
Comment 4 javese 2006-01-06 15:25:23 UTC 
ok, marked as fixed in 5.0
Comment 5 Petr Pisl 2006-01-06 16:50:57 UTC 
I set the version 4.1 and set that this issue depends on #42638