Community
Participate
Working Groups
Language: Korean Priority:2 Build driver: wswb-SDK-M20030604-linux-gtk.zip Reporter: Korean tester OS:RedHat8.0+GTK 2.2 Description: Panel "templates" from the Java editor has missing buttons on the Korean machine. To fix the problem we need to have the Dialog font externalized in the Jfacefonts_linux_gtk.properties. Then this Dialog font would be set to gothic font for the Korean station to be able to display all 7 buttons in the templates panel. Today only 3 fonts are being externalized: they are header font, text font and banner font. Steps to recreate problem: 1-Windows->preferences->Java->editor->templates 2-If Dialog font is set to the default font (sans font), you will get missing buttons on the templates panel (see sans-font.gif). 3- If you manually change the Dialog font to gothic font and redisplayed the templates panel, you will get all 7 buttons displayed.(see gothic_font.gif). We need to have the Dialog font externalized in the Jface font for font update. This way when the product is launched, Korean language will come up with the correct number of buttons for the screen. In case you need the NL fragment, please contact Tod Crasey.
Created attachment 5102 [details] sans-font.gif
Created attachment 5103 [details] gothic_font.gif
Cannot replicate on Redhat 9. The dialog font is by default the defualt font of the OS. This should not change on any platform. My default font on Red Hat 9 is Sans 10. It looks to me like you are using a much larger font as the scaling is huge on your buttons. Please check what your system font is and let us know. Please also select "Use System Defaults" when you set the dialog font and then recheck.
Just rechecked on RedHat 8 and it was also fine. It look like your default font has a very large vertical point size and that it is your particular setup that is causing this problem.
Renaming problem report. This problem is due to a default font that is too high.
Update problem to critical and to be fixed in 2.1.1.
Can you please check the following 1) Your GTK default font (from the OS check this using the Entry in the Preferences -> Font menu)and the settings you have chosen. 2) What is the theme you are using (if any). Several themes have font problems
In Redhat 8.0 I am gettingthe following warnings: (process:1297): Gdk-WARNING **: locale not supported by C library (process:1297): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale.
Also cannot replicate using the Red Hat 8.0 machine with gtk 2.2 we have hear in the lab.
Created attachment 5162 [details] Preference page with sans 10 Here is what the same dialog looks like to use with the default font.
Cam-Thu Le or Hwa, Please, run the command "rpm -qa | grep fonts" in your system and paste the output here.
XFree86-truetype-fonts-4.2.0-72 ttfonts-zh_TW-2.11-15 XFree86-75dpi-fonts-4.2.0-72 taipeifonts-1.2-20 XFree86-base-fonts-4.2.0-72 ttfonts-ja-1.2-16 ttfonts-ko-1.0.11-21 ttfonts-zh_CN-2.11-29 urw-fonts-2.0-26 fonts-ja-8.0-4 kon2-fonts-0.3.9b-13 ghostscript-fonts-5.50-7 XFree86-100dpi-fonts-4.2.0-72 bitmap-fonts-0.2-2
I tried to recreate this problem on: RedHat 9 / Gtk 2.2.1 RedHat 8 / Gtk 2.2.1 RedHat 8 / Gtk 2.0.6 They all work fine. (Tod, I added ko_KR locale to the lib C so the error message 'locale not support' is fixed). I worked with Hwa today and we confirm that he was actually running on Gtk 2.2.0, after updating his machine to Gtk 2.2.1 the problem disappear.
There has been alot of confusion around this bug. At the core of the problem is a default font size which is too high on 2.2.0. The problem can be resolved by manually setting the default font size. Various tests have shown that the problem does not occur on GTK "2.2.1". While this is true, moving to GTK 2.2.1 is not feasible as there are other, quite significant, problems in the 2.2.1 available on gtk.org (e.g., tree widget that causes Eclipse to hang). To further confuse the issue, the 2.2.1 that comes in RedHat 9.0 has a set of patches which fixes many of these problems. The 2.2.1 release available on gtk.org does not. Since the good version of 2.2.1 is not generally available, users would be unable to create a suitable execution environment. Further, the bulk of the TVT work has been done on GTK 2.2.0. While 2.2.1 (the one from RH9.0) has been used in various development scenarios, it has not undergone the rigors of TVT. Summary: We should clarify the Eclipse runtime environment to spec GTK 2.2.0 and readme this particular problem to tell users to manually set the default font to something with a reasonable size.
Slight clarification.... TVT team: We need confirmation that this bug is a general problem on Korean rather than just a problem with this particular Korean machine. Please verify that the problem happens on a different Korean machine. If it does, then we will be able to add a readme. If it cannot be reproduced then it is likely a machine-specific problem.
We have been able to reproduce this on several TVT machines we have setup here.
This is the readme for Korean - GTK 2.2.0 font problem: Users who download and compile new versions of GTK, for example to gain DBCS support in GTK 2.2.0 on RedHat 8.0, will experience font related problems for the Korean translation. For example, some of the text font may get clipped at the top, or windows may resize out of viewable area. To circumvent the problem, we recommend user to set high screen resolution, for example 1280x1024. User also needs to manually set the dialog font and banner font to gothic font. To execute, go to Window -> Preferences. Expand Workbench -> Font. Select Dialog Font. Click Change button and select gothic font. Click Apply. Repeat for the Banner Font.
Added the following to the R2.1.1 readme. Font problems in Korean translation on GTK 2.2.0 (Linux GTK only) Users who download and compile new versions of GTK, for example to gain DBCS support in GTK 2.2.0 on RedHat 8.0, will experience font related problems for the Korean translation. For example, some of the text font may get clipped at the top, or windows may resize out of the viewable area. To circumvent the problem, we recommend setting a high screen resolution, for example 1280x1024, and setting the Dialog Font and Banner Font to a gothic font. The latter can be done in the Workbench > Fonts preference page.
Fixed.
That is, this PR is closed because the problem is documented in the readme.
Marking as closed.
