Hi, I'm trying to export right-to-left string into PDF using your export component (Documents.Report). I'm adding a text field with text like 'abc 123' and the output appear as 'abc 321', while the abc part if in a right-to-left language (Hebrew). Is there a solution for this issue? does the PDF exporter supports rtl languages?
the code is very simple, something like band.AddText(), and text.AddContent(...)
bad news.
any plan to solve this?
maybe the documents component used in WPF has this support, or any other solution you may offer?
Hi,
My apologies for the confusion. I looked into this some more and the fix I was thinking of is not related to Right-To-Left. It had to do with unicode characters in certain languages where multiple characters combine into a single character in the document and these were not being combined correctly and came out in reverse.
Right-To-Left is not currently supported by the Infragistics Winforms control or the documents engine.
Attach a code section, with rtl text + number (like 'abc 123') which is written to pdf as 'abc 321')
Please advise. thanks!
_report = new Report();
string textToExport = "בדיקה 123 מה המצב";
Infragistics.Documents.Reports.Report.Section.ISection section = _report.AddSection();
Infragistics.Documents.Reports.Report.Band.IBand band = section.AddBand();
//add text content
Infragistics.Documents.Reports.Report.Text.IText text = band.AddText();
text.AddContent(textToExport);
string fileName = Path.GetTempFileName().Replace(".tmp", ".pdf");
_report.Publish(fileName, Infragistics.Documents.Reports.Report.FileFormat.PDF);
//to open the saved pdf file after export is done
System.Diagnostics.Process proc = new System.Diagnostics.Process();
proc.StartInfo.FileName = fileName;
proc.Start();
Hm, the issue I am thinking of was resolved long before the 2012 release, so my guess is that either the fix we implemented doesn't work in your case for some other reason or else it's just not supported by the current Documents engine.
Could you post a small sample project demonstrating the issue so we can check it out?
I'm using 2081 version (2012q1).
when was this issue resolved?