Community
Participate
Working Groups
when using the __rtl=true parameter the viewer export options (pdf/word) aren't generated in this same __rtl=true manner - this causes a report to be displayed properly in the viewer as HTML but not properly as PDF. This parameter should be passed on to all exports as well.
Reassign to engine to check whether support this feature.
rtl is only supported in HTML.
Is this an issue to be developed in the near future or is this not on the work plan at all ? This issue is a problematic issue to anyone who needs the __rtl=true option (when using laguages that are written from right to left chars like a period ,parenthisis or question mark that are at the end of the sentence will appear at the begining of the sentence - [1]XXX-YYY will become 1]XXX-YYY[ ? AAA BBB will become AAA BBB ? (needs to be read from right to left) only the __rtl parameter solves this.. (In reply to comment #2) > rtl is only supported in HTML.
Created attachment 93208 [details] Example for chars being placed wrongly without the __rtl option
with the enhancement from 225536, BIRT viewer should be able to support RTL output for PDF, and other non-html formats.
The "__rtl" value from the URL is already passed by the viewer to the engine through the render options. The engine must now use this value when exporting to non-HTML formats. Reassigning to engine team.
For __rtl=true passed from render option, Engine makes it take the same effect as <property name="bidiLayoutOrientation">ltr</property> in design file. In this case, Assaf also need to set "Bidi text direction" to specify the base level for bidi text. Fixed.
