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 14502 - i18n - XML and DTD files can not handle full-size alphanumeric character.
Summary: i18n - XML and DTD files can not handle full-size alphanumeric character.
Status: CLOSED WORKSFORME
Alias: None
Product: xml
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: _ pkuzel
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2001-08-17 05:12 UTC by Masafumi Matsuda
Modified: 2007-09-25 01:31 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
screen shot (35.58 KB, image/png)
2001-08-17 05:14 UTC, Masafumi Matsuda 		Details
I attached zipped XML documents. (500 bytes, application/octet-stream)
2001-09-10 05:16 UTC, Masafumi Matsuda 		Details
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 Masafumi Matsuda 2001-08-17 05:12:52 UTC 
Please see attached image file.
i18n - XML and DTD files can not handle full-size alphanumeric character.

How to reproduce
1.file-->new-->select XML with DTD or DTD Entity.
2.Push Next button. step2 dialog is displayed.
3.Push Finish button. Crated xml file or dtd file.
4.Right click on the files, select "Edit". Source Editer is displayed. 
5.Add full-size alphanumeric character (not Japanese) on Source Editer.
6.It saved the files.
7."Parse fatal error..." is displayed on Explorer.

OS:Windows2000 (Japanese),Solaris8 SPARC
Build No:010810
JDK:JDK1.3.1
Locale:ja
Comment 1 Masafumi Matsuda 2001-08-17 05:14:06 UTC 
Created attachment 2206 [details]
screen shot
Comment 2 _ pkuzel 2001-09-07 17:04:32 UTC 
Hello Masafumi,

could you attach zipped XML documents that produced bugs you attached
as the screen shot? Please zip it to avoid some unintentional
conversions.

Thanks
Comment 3 Masafumi Matsuda 2001-09-10 05:16:30 UTC 
Created attachment 2468 [details]
I attached zipped XML documents.
Comment 4 _ pkuzel 2001-11-02 19:51:46 UTC 
According to spec http://www.w3.org/TR/REC-xml#NT-doctypedecl
DOCTYPE declaration must be followed by Name consisting of NameChars.
0xFF11, 0xFF12, and 0xFF13 are not valid NameCharacters. It is
according to the spec a fatal error and it is reported so.
Comment 5 _ pkuzel 2001-11-05 16:08:13 UTC 
Going to patch it, no invalid document created form template is
allowed.
Comment 6 _ pkuzel 2001-11-05 16:10:40 UTC 
If invalid XMLName appears as file name it is automatically replaced
by valid "root" in document content.
Comment 7 hiroshiy 2001-12-03 10:31:45 UTC 
Hi Petr,

In the following environment, same error is reappears as the first
comment
in this page. 

    Solaris8 on Sparc, JDK 1.3.1, ja locale.
    NetBeans IDE, Release 3.3 Beta 6 (Build 200111271845)

Please make it confirm it one more time, or please tell me the process
not
to make it reappears.

Thank you.
- Hiroshi
Comment 8 _ pkuzel 2001-12-03 11:22:35 UTC 
Could you specify XML module version? If in doubt autoupdate XML
module Beta1 from NetBeans Update Center. REOPEN if it appears there.
Comment 9 hiroshiy 2001-12-13 04:19:26 UTC 
I installed "XML Beta1 Modules", and I verified my test environment
carefully.
But, this problem was reproduced.
Please investigate again.
Comment 10 _ lkramolis 2001-12-13 09:08:17 UTC 
Petr, look at TreeUtilities, if there is not too aggressive (and
wrong) check method.
Comment 11 _ pkuzel 2001-12-13 13:25:28 UTC 
I still can not reproduce it. 

Are not there in your system some old XML templates? 
Try to use IDE with empty user dir by starting it with -userdir
nonexisting_directory_name switch.

Are you able to reproduce it for another invalid XML names e.g. "123"?
Comment 12 hiroshiy 2001-12-28 03:55:01 UTC 
I agree with your modification.
Though I was sorry, it was in confusion.
Comment 13 Jesse Glick 2002-12-23 16:36:21 UTC 
Consistent use of the I18N keyword.
Comment 14 Quality Engineering 2003-07-02 08:40:55 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.