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.
Check out the above link, showing archives of the Chinese discussion list. You can see that the subject lines are garbled, displaying the raw ASCII of the Subject header. If you open the message, e.g. http://www.netbeans.org/servlets/ReadMsg?msgId=636212&listName=nbdiscuss_zh then the contents are garbled too. Here the character encoding GB2312 was specified for both the subject line (note the RFC-compliant "=?GB2312?Q?"...."?=" marker for this purpose) and the body text (note Content-Type header). Yet the archive page shows garbage. The reader servlet should set UTF-8 encoding on the page it returns, interpret encoding markers in both the message body(ies) using Content-Type as well as the message headers using the RFC designed for this purpose (don't have RFC# offhand), internally load everything in Unicode (it is a Java servlet after all! this should not be hard) and print it all in UTF-8 for correct display in any Unicode-enabled browser.
Verified the issue and filed an internal issue 24605 for the engineers to look at. Will update here as soon as i get the update from them. Thanks, priya
Engineer updated that this is fixed in 2.6.x -- that version is properly unicode aware. Once the upgrade is done , new messages will be handled correctly. - Priya
As this is fixed in 2.6.x, an upgrade version for NB, closing this as resolved and review again once the upgrade is done.
The subject is still garbled. The body looks fine. Reopening this issue
Followin up this internally.
The message in the attachment is dated in 2003. Existing messages will require re-indexing or re-archiving which is a pretty expensive task. New messages will archive and index properly. If you can find a recent message with an improperly handled subject, that should help us to check whether this is still an issue. If you need the old messages to be indexed to find a time when we can reindex their mailing lists. But to re-archive the entire site, which might take quite some time in NB and it is an expensive task. Let us know your feedback on it. -Priya
We have an option to index a few old messages by setting up indexer queue. This will index the message in the queue during the incremental rebuild. Still i think there will be quite a lot of messages existing. As mentioned above, re- archiving is an expensive task.
jglick: Hi, any updates on how do you want to go furhter on this?
I don't think we care much about existing messages, if it's fixed for new messages.
Yup, The new messages are fixed, if you happen to see any message with a garbled characters it could be a old one. If you happen to see any new messages with this kind please reopen the issue.
closing..
We recently moved out from Collabnet's infrastructure