Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343349

Summary:

DBCS4.1: Javadoc generated within Eclipse containing DBCS characters cannot be viewed properly using internal browser

Product:

[Eclipse Project] Platform

Reporter:

Dani Megert <daniel_megert>

Component:

SWT

Assignee:

Grant Gayed <grant_gayed>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

camle, daniel_megert, eclipse.felipe, harendra, kennoji, kitlo, markus.kell.r, pwebster, remy.suen

Version:

3.7

Target Milestone:

3.7 M7

Hardware:

OS:

Linux-GTK

Whiteboard:

Attachments:

Description	Flags
patch	none

Description Dani Megert

2011-04-20 04:10:30 EDT

+++ This bug was initially created as a clone of Bug #342925 +++

Build Identifier: I20110407-2200

Eclipse version:I20110407-2200
OS: Ubuntu Linux 10.10
Java Version: JRE 1.6.0 IBM Linux build pxi3260sr9fp1-20110208_03 (SR9 FP1)
Locale: ja_JP.utf8

Reproducible: Always

Steps to Reproduce:
1.Import the attached project or create a project with either the class or the method name containing DBCS characters.
2.Click on the project, Project->Generate Javadocs.
3.Go to Window->Preferences->General->Webbrowser and select Use internal web browser radio button and check "Default system web browser".
4. Now click on the class name containing dbcs character in Java editor.
5. Click Navigate->Open Attached Javadoc.
6. The text will be shown all garbled.
This could be due to the fact that the Javadoc does not have a meta tag that
specifies the document is encoded in UTF-8. The project had encoding set to UTF-8. This bug however has a workaround. If you set your browser to External web browser and choose Firefox, the text will be displayed correctly.

Comment 1 Dani Megert

2011-04-20 04:14:05 EDT

According to Harendra (see bug 342925) It works in 3.6 but not 3.7 and 4.1 builds. I suspect that the problem is caused by the switch to WebKitGTK+.

Comment 2 Grant Gayed

2011-04-26 14:08:44 EDT

Created attachment 194084 [details]
patch

The default encoding was not being set for WebKitGTK, the fix is similar to what the Browser's Mozilla implementation does.

Comment 3 Grant Gayed

2011-04-26 14:10:41 EDT

fixed > 20110426