Community
Participate
Working Groups
Environment: On build 515, in Simplified Chinese, running NL fragments built on 5-30. Description: Corrupt quotation characters in first page of new plugin project wizard. Corruption appears as a skinny, solid, tall rectangle in the banner section around com.example.xyz. To replicate: 1) File>New>Plugin Project 2) on first page, in banner, corrupt quotes wrap around com.example.xyz
One more thing: we have tried a multitude of fonts to alleviate this problem and it doesn't appear to be sensitive to font changes in XP. On Win2k font changes actually have an effect.
Cannot replicate in build F2 on a Chinese XP machine with GB18030 installed. The fonts used by the banner on wizards is the same as the Banner Font and Header Font preferences of the Workbench preferences - changing an OS setting will not make any difference. Your current settings with be Tahoma as we currently only supply English fonts. As there is no NL version of this fonts file currently available the way to see if this is actually a problem is to select Preferences-Fonts-Banner Font and Header Font and change this to values that are valid on your machine (e.g. to one of the GB18030 fonts) and try again. Reassigning to Platform-UI and myself as this is a Platform-UI not PDE issue.
I originally had tried modifying those settings within the workbench. Only when they had no effect did I attempt working through display properties for Windows. I haven't had the opportunity to try on anything later than 515, with NL fragments, as we are currently awaiting translations based off of F1. Will update when I can test with a more recent build.
Testing with the F# build and the 20020610 fragments on a Chinese XP machine with GB18030 support I do not get this. My Header font is ËÎÌå regular 10 - which one did you get on the machine with the problem?
Problem was reported in build 515 + fragment. When testing again with build F2 + fragment, problem disappeared.
Marking as fixed after verification by Cam-Thu Le.
Marking closed
*** Bug 149375 has been marked as a duplicate of this bug. ***