Summary: | GC.drawString/Text() is inconsistent | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Pratik Shah <ppshah> |
Component: | SWT | Assignee: | Felipe Heidrich <eclipse.felipe> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | eclipse.felipe, slubicki, steve_northover, Tod_Creasey |
Version: | 3.1 | Keywords: | needinfo |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Pratik Shah
2005-05-10 15:50:46 EDT
According to the 3.1 plan, a style of RIGHT_TO_LEFT is only supported on win32. So, the relevant part of this bug is the difference between my XP output and Pratik's XP output. It is worth noting that Pratik attempted to install the Arabic language pack on his machine, and the installation failed. So he has less Arabic support than I have. He may also have corrupted windows, but it is worth testing on a plain English XP install. Steve, you have a plain English XP install, can you test this ? In my machine, arabic enabled, I got ".Done". I tried this on my English-only XP machine at home and I got ".Done" as well. The Linux bug is not a supported RTL platform. Marking as INVALID until we find some win32 box which shows the problem but does not have a failed Arabic installation. Reopen (anyone) if you find such a box. I reproduced this on another co-worker's machine. He has a brand new T42; never attempted to install Arabic. What is a T42 ? any service pack installed ? uniscribe dll version ? T42 is an IBM Thinkpad. It has the "approved" coorporate version of XP installed, along with other "standard client software". It is not setup for IME. Felipe, how do I find out the uniscribe dll version? Select this file C:\WINDOWS\system32\usp10.dll and press ALT+ENTER You can also use WINDOWS_KEY+PRINT_SCREEN_KEY to get system info, it will tell either or not service pack is install. 1.0409.2600.1106 (xpsp1.020828-1920) on my computer It doesn't seem to be the problem. I have version 1.0409.2600.1106 of USP10.dll and I couldn't reproduce the problem. closing as works for me. |