Community
Participate
Working Groups
<response_by> Gaby Pelleg at 2010.05.10.16.26.04 </response_by> Build: 20100509 Language: Hebrew Component: GEF Steps: 1) The Logic Example should now be open with a complex drawing on it. 2) Display the property sheet from the Window menu (Window. -> Show View > Other? -> General -> Properties). 3) Click on the LED at the bottom that is displaying "10". 4) It has 3 properties that should be translated: Location, Size and Value Problem: The properties sheet for the LED displays the value point(x,y), but "point" is not translated and I can't find it in the files. Since the Value field is RTL, the parentheses are garbled. Should this string be translated? where is it coming from? it may be better to leave in English but set the Value field LTR , which would also accommodate negative values (if any). See attached screen shot. <response_by> igultek at 2010.05.11.09.02.51 </response_by> This article was reassigned from Category:''TVT/Testing,Inbox''.
Created attachment 167924 [details] 12.000.080_bidi_point.jpg
<cde:tctdetail> Testcase: 12.000.080 Project: WSW36 Component: Xfer - GEF/GEF Priority: 3 Subject: Heb: English string + bidi problem Article ID: 225 Originator: gpelleg@il.ibm.com </cde:tctdetail>
<response_by> Gaby Pelleg at 2010.05.13.19.03.33 </response_by> Same problem with "Dimension" for Size, see screen shot.
Created attachment 168493 [details] 12.000.080_bidi_dimension.jpg
<response_by> Gaby Pelleg at 2010.05.14.07.28.06 </response_by> Last day of phase I for GMF - anyone? don't know if this a PII fix or not.
Anthony, looks like the string "Point" and "Dimension" are not externalized. We cannot fix that by adding the LRM (left-to-right mark) in the Bidi translations.
(In reply to comment #6) > Anthony, looks like the string "Point" and "Dimension" are not externalized. We > cannot fix that by adding the LRM (left-to-right mark) in the Bidi > translations. No plan to fix for IES 3.6 / Helios, we can fix in the next release.
<response_by> Gaby Pelleg at 2010.05.14.18.21.45 </response_by> Since it appears this will not be fixed now, should I mark this ER "Permfail"?
<response_by> Kathy Li at 2010.05.17.16.41.10 </response_by> Hi Gaby, Yes, please mark it as Permfail for now. We have bug filed to track this problem. It'll be fixed in the future release. Thanks Kathy