Community
Participate
Working Groups
Error date & time, in the error log view, are not displayed correctly when running eclipse on Arabic locale "ar_EG.utf8" (error date is always set to 01-01-1970, error time is always set to 02:00:00; although the system clock was set correctly before running this scenario). When using the same workspace but on English locale ("en_US.utf8"); error timestamp were displayed correctly according to the system clock.
Created attachment 63392 [details] screenshot of the problem when running eclipse on Arabic locale
Created attachment 63393 [details] screenshot of error timestamp when running eclipse on English locale
Can you please provide a log file with the Arabic timestamps? Thanks.
Created attachment 65732 [details] Error log file
As per your request, I am attaching the error log file. Please notice that this is just a display problem (for error log view), i.e if you exported the error log and viewed its content using any text editor, you will find that date is displayed correctly according to the system clock! (please refer to attached error log).
Hi Ahmed, I was not able to reproduce this bug using the following configuration: * Windows XP Service Pack 2 * 3.3 RC1 * 3.2.1 Bidi SDK language pack for Arabic & Hebrew * Sun JDK 1.4.2 rev 14 I am going to have to try to reproduce it on Linux. I noticed in your error log that you are using IBM JDK 1.5.0 J9. In the past, I've noticed some Eclipse related / JVM related bugs while using an IBM JDK. If possible, could you try using Sun JDK 1.4.2 and see if you still see the same problem? Just want to rule out those possibilities.
(In reply to comment #6) Mike, I am still facing the same problem using Sun JDK 1.4.2 on RHEL V5.0 Please notice that this problem was only encountered on Linux (as mentioned above in the bug description).
Created attachment 154922 [details] Date is displayed correctly from the snapshot attached ,the date is displayed correctly.. I used build 3.5.1 Thu, 17 Sep 2009.
Closing, since the bug has been resolved....
Changing to WORKSFORME as there was no code change involved.