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.
based on email with Sheryl: We still have problems with multi-char in project name and diagram name, but it's a separate issue, don't know if we had a bug already, I guess we need to escape the url when generating the page. part of this is related to browser, at least mozilla, needing path to url to be escaped rather than using actual multibyte or other non ascii characters. I don't know if there is also problem with how to handle the encoding of the project name or diagram name, since those are not from bundle file, nor are they from the localized html files or from the internal data of the actual diagram, at least for the project name.
project name and diagram name are used to construct url, we will need special url String handling to fix the issue. *** This issue has been marked as a duplicate of 89250 ***
reopen it, changed summary to indicate it's about multi-type char in package and diagram names, different issue from 89250
Browsers on Solaris is such a pain to deal with when it comes to encoding. It does not take mbyte string specified in href tag when it's encoded in a different charset than the system default one. In our case, we generate page using utf-8 with link reference to other pages encoded in utf-8, in system other than utf-8, it will not find the page for the mbyte link. One possible solution is to encode url string when generating href value, and the charset to encode url has to be system default one. The drawback is encoded html source in href value. Another option is to generate page using system default encoding, so we don't need to process href value. JavaDoc uses system default encoding to generate pages, I think we should just follow the model, implementation has been changed to use default encoding, no special handling of url path is required. Furthermore, to simplify localization settings, I made changes to avoid mixing static and dynamic content, now the only html template files that should be localized are index.html and help.html ( they should be localized in the charset specified in metadata ), l10n.list is updated. Localized jar must be updated before testing. I tested on various zh and ja locales on Solaris, mbyte in package and diagram name seems to be fine now. I did find a minor issue on one ja locale, when encoding charset is not picked up by browser (encoding string returned from System.getProperty("file.encoding") has a suffix "-open") if auto detect encoding is turned off, so user has to manually set display encoding on browser view->character encoding, but the page navigation with mbyte path is OK.
verified, but please read comment in this issue about if auto detect is turned off. ken.frank@sun.com
*** Issue 98285 has been marked as a duplicate of this issue. ***