Bug 136075 - Bidi3.2: Arabic data is not correctly displayed in the generated Javadoc
Summary: Bidi3.2: Arabic data is not correctly displayed in the generated Javadoc
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux-GTK
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-04-11 05:35 EDT by Ahmed Farrag CLA
Modified: 2009-08-30 02:09 EDT (History)
8 users (show)

See Also:

Attachments
fig1 (54.29 KB, image/jpeg)
2006-04-11 05:36 EDT, Ahmed Farrag CLA 		no flags Details
View All 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 Ahmed Farrag CLA 2006-04-11 05:35:59 EDT 
Build date: 31/03/06
OS: RHEL 4.0

Steps to recreate the problem:

1) Create Java project.
2) Create Arabic named Java class.
3) Generate Javadoc for this new class.

Expected output:

Arabic data should be correctly displayed in all generated html files.

Actual output:

Arabic data is displayed as accented characters in generated html files.
See fig1 for more illustration.
Comment 1 Ahmed Farrag CLA 2006-04-11 05:36:33 EDT 
Created attachment 38267 [details]
fig1
Comment 2 Martin Aeschlimann CLA 2006-04-11 06:25:04 EDT 
I assume this isn't a bug against the documentation of Platform/JDT as we probably don't have arabic named classes in our source.

Moving to JDT/UI and the Javadoc wizard. Please object if I'm wrong.
Comment 3 Martin Aeschlimann CLA 2006-04-11 06:29:37 EDT 
The Javadoc wizard uses the default Javadoc command from the JDK. Maybe we miss some command line arguments when call it, although all the arguments are controlled by the user (in the wizard) and the new process should automatically get the locale configured in the system.

Can you try if you can generate correct Javadoc documenatation using the Javadoc command (from the command line) and find out what we're missing?
If this isn't diffenet, then this is a bug of the Javadoc command.
Comment 4 Ahmed Farrag CLA 2006-04-16 03:47:35 EDT 
(In reply to comment #3)

I have tried generating Javadoc documenatation from the command line and I got the same results, so as you said this is a bug of the Javadoc command.
Comment 5 Ahmed Farrag CLA 2006-05-28 12:13:08 EDT 
closing...
Comment 6 Denis Roy CLA 2009-08-30 02:09:10 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.