Community
Participate
Working Groups
Created attachment 95166 [details] Extra Tchinese string Build ID: I20080324-1005 GEF version: GEF-SDK-I200803111830.zip ===== Steps To Reproduce ===== 1.Create a simple project in the workspace. 2.Go to File -> New -> Example… -> Logic Diagram and hit “Next.” 3.In the dialog that pops up, you should be able to edit the project and file names. 4.Go ahead and create an empty model file (to be used for the next test case). 5. Create a label in the logic editor that opens up (by dragging a label – under components – from the palette). If a palette is not visible, open the Palette View (Window -> Show View -> Other… -> Basic -> Palette). 6.Create a file using the WYSIWYG example file wizard. 7.Open Editor ===== Expected Result ===== Editor should display normally without extra string. ===== Actual Result ===== Editor display extra TChinese string or space in the square bracket. More information: ==== Environment ===== Build Level: I20080324-1005 Platform: Windows XP Affected Locale(s): TChinese
Created attachment 95171 [details] Extra bracklet in English locale
The Chinese text is just something we added for testing purposes. What's wrong with that? It's interesting that the Chinese text does not appear in the English locale. It works for me. Perhaps you need that language to be installed?
Created attachment 95311 [details] Screenshot from GEF testcase
Hi Pratik, we didn't see Chinese text in GEF testcase screenshot, so we think it's a defect. If this is the correct behavior, we can ignore it. And I guess the Hebrew string in the bottom is also for testing purpose, right?
Yes, the Arabic text is also for testing purposes. Marking as invalid.
Hi Pratik, the extra text for testing purpose is still exit in build I20080413. Will Dev take it away? If no, I can mark this bug close. If yes, could you please tell me which build will it be took away? then I can verify again. Thanks.
Reopening (In reply to comment #6) > Will Dev take it away? > > If no, I can mark this bug close. We are not removing the test string. We will reopen this bugzilla to investigate the issue in the future, but given this is an example, it does not block any DBCS3.4 testing.
