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.
Summary: | I18N: garbled characters in JSP and Design editor when opening VWP551 project on NB6.0 | ||
---|---|---|---|
Product: | obsolete | Reporter: | Masaki Katakai <masaki> |
Component: | visualweb | Assignee: | Quy Nguyen <quynguyen> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | jf4jbug, kaa, kfrank |
Priority: | P2 | Keywords: | I18N |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
screen shot
vwp551 project, try to open this project on NB6.0 in Japanese Windows |
Description
Masaki Katakai
2007-09-26 01:12:01 UTC
Created attachment 49525 [details]
screen shot
Please, provide additional info. What do you mean by "the text is garbled"? Is the text in the view not the one you've entered? Also does this happen in 5.5.1 only? I.e. whether it works fine on 6.0 Thanks. Created attachment 49528 [details]
vwp551 project, try to open this project on NB6.0 in Japanese Windows
Hi, > What do you mean by "the text is garbled"? Is the text in the view not the one you've entered? Yes. See screenshot and sample project. > Also does this happen in 5.5.1 only? I.e. whether it works fine on 6.0 I'm sorry I haven't tried yet. I just tried to open VWP551 project on NB6.0. I think it can be happening in other encoding. Thanks. Masaki, what is the encoding tags in the page1.jsp in nb 6 ? we've had some recent fixes so that the seeding of encoding tag in jsp is same as project encoding, which in case of nb551 project, should be encoding of locale user is in, which i think is ok since win-31j is same as ms932 ? so this might be encoding handling problem in this case due to incorrect in page1.jsp or it could be some other encoding handling situation ? --> can you change project encoding to utf-8 and see what happens ? (or to 932 if different than 31-j) ? or change encoding of page1.jsp tags ? ken.frank@sun.com This seems to be about encoding the text into file. Passing to insync, please pass to editor if it belongs there. I think this may be related to the FileEncodingQuery which is (or should be) implemented in the DataLoader/DataObject. Assigning to Quy for further investigation. Note for Quy: You may want to talk to Petr Pisl about FileEncodingQuery. He implemented it in his JSFLoader. He is here in Menlo Park this week. see also 100178 on feq implementation - I've asked for some scenarios in that issue of what is impacted so can focus for testing but don't have response to it - please provide if possible. also see 108682 for templates encoding seeding. Also suggest wait to hear from Masaki if changing the encoding in page1.jsp and/or the project properties helps in this case as sometimes that can give clue related to feq handling. ken.frank@sun.com I tried the latest one 200709250000 build. Sometimes design view is OK, but still JSP editor displays garbled characters. > what is the encoding tags in the page1.jsp in nb 6 ? I'm seeing UTF-8 in header, because the file is generated by 5.5.1. Does NB try to open it as Windows-31J? > --> can you change project encoding to utf-8 and see what happens ? When I changed the project encoding to UTF-8 *before* I open the JSP, JSP looks OK. However, .java files already contains native characters (in this case Windows-31J) so it does not help. > (or to 932 if different than 31-j) ? MS932 and Windows-31J are the same. As you may know, there is no "MS932" listed on the property dialog. I understand you can try this scenario easily on your environment by using Solaris EUC or SJIS locale. Please try. When I tried Solaris ja EUC locale, Design view shows "Source File Error". It seems that JSP file can not be parsed due to the encoding issue. Fixed jsp file encoding by providing a FileOwnerQueryImplementation as suggested above. /cvs/visualweb/project/jsfloader/nbproject/project.xml,v <-- project.xml new revision: 1.9; previous revision: 1.8 done Checking in src/org/netbeans/modules/visualweb/project/jsfloader/JsfJavaDataObject.java; /cvs/visualweb/project/jsfloader/src/org/netbeans/modules/visualweb/project/jsfloader/JsfJavaDataObject.java,v <-- JsfJavaDataObject.java new revision: 1.6; previous revision: 1.5 done Checking in src/org/netbeans/modules/visualweb/project/jsfloader/JsfJspDataObject.java; /cvs/visualweb/project/jsfloader/src/org/netbeans/modules/visualweb/project/jsfloader/JsfJspDataObject.java,v <-- JsfJspDataObject.java new revision: 1.15; previous revision: 1.14 verified: build 0927 was verification done using a nb551 project, as original issue was based on this scenario ? if not,then this should not be considered verified until that is done. ken.frank@sun.com I verified with the attached projected |