Community
Participate
Working Groups
Build ID: 2_3_1-N20080815 Following https://bugs.eclipse.org/bugs/show_bug.cgi?id=185957#c8, we need to make text alignment consistent with the text direction in BIRT Designer. A similar bug was filed against Report Engine: bug 244375.
Created attachment 110167 [details] Proposed patch The patch contains a number of pretty trivial changes to link between text direction and text alignment in report designer GUI, some minor cleanup.
(In reply to comment #1) > ... in report designer GUI, some minor cleanup. Sorry, missed a word: The patch contains a number of pretty trivial changes to link between text direction and text alignment in report designer GUI, *and* some minor cleanup.
Created attachment 110171 [details] Report design for manual test
I'm not sure about this change. Is this a requirement to swap the text alignment setting when in RTL direction? Actually from CSS spec, if the "text-align" property is set explicitly, it will always follow the actual setting regardless the direction. Only when "text-align" property is not set, it will use "right" for "RTL" and "left" for "LTR". That being said, if direction is "RTL", text-align is "left", the visual effect for text alignment is still "left". I think both Firefox and IE follow this rule, if we take a different approach, would it be confusing for user?
This change was supposed to conform to the spec and applies to 2 cases: (1) when text-align is not set explicitly (and follows text direction); in other words, the default 'text-align' depends now on the text direction - as opposed to the report orientation, as at present, (2) when text align is set to 'justify' (in such a case the last line follows text direction). All explicit alignment types (other than 'justify') are visualized identically in both directions. Sorry for not stressing this point.
Ok, I see, so the default text alignment is based on direction property on text item itself, not report design.
UI code need the BidiAlignmentResolver class change, so depend on the 244375.
Fixed.Follow the new engine API.