Bug 108321 - I18N - javadoc not generated for file with mbyte in class or project name
I18N - javadoc not generated for file with mbyte in class or project name
Status: RESOLVED INVALID
Product: java
Classification: Unclassified
Component: Freeform
6.x
All All
: P2 (vote)
: 6.x
Assigned To: Milan Kubec
issues@java
: I18N
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-27 18:54 UTC by Ken Frank
Modified: 2007-06-27 20:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments
image (53.96 KB, image/gif)
2007-06-27 18:55 UTC, Ken Frank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2007-06-27 18:54:40 UTC
using ja locale on solaris, j2se project - the default project encoding is utf-8 although user can use characters
from the locale they are in and do not need to change project default encoding to do so.

create j2se  or othere freeform project with mbyte in its name and a class with mbyte in its name.
choose to create java doc - there are syntax errors related to encoding - the errors are in japanese since
javadoc  error msgs have been translated to japanese, but the clue is in the words EUC_JP_SOLARIS

see attached gif of output window errors - the gif is from the same bug on j2se project but the error msgs are the same.

now change the project encoding property to euc-jp, which is the default encoding of solaris ja locale,
and create another java class with mbyte in its name.

now choose to create javadoc - there are no syntax errors associated with this newly created file, but still
errors on the previous file that was created when project encoding was utf-8

NOTE - see 106944 for more information and about solution - that one is on j2se project.
Comment 1 Ken Frank 2007-06-27 18:55:22 UTC
Created attachment 44478 [details]
image
Comment 2 Jesse Glick 2007-06-27 20:01:08 UTC
If it's a freeform project, it's your responsibility to pass the correct encoding to <javadoc>.
Comment 3 Ken Frank 2007-06-27 20:38:12 UTC
please clarify about this and why user would need to pass encoding arg to javadoc -
there is the project encoding value for freeform projects now so why would user need
to pass an argument - wouldnt it use the feq value ? 

also, where in project props or other would this argument be passed ?


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