Export to PDF RTL language problem

Posted by: ilia on 27 April 2018, 6:34 pm EST

    • Post Options:
    • Link

    Posted 27 April 2018, 6:34 pm EST - Updated 30 September 2022, 9:05 am EST

    I use last version of AR 12.1.

    I use Hebrew language in my section report. I some cases I need to set RightToLeft property of TextBox as False. It works in the Viewer, but does not when Export to Pdf (the text render as right-to-left instead of left-to-right).

    Example attached.

  • Posted 27 April 2018, 6:36 pm EST

  • Posted 7 May 2018, 12:44 am EST

    Hello,

    It is a “limitation” in PDF export. PDF export ignores the state of RightToLeft property of the control when receives RTL text.

    Sorry for the inconvenience caused.

    Thanks,

    Mohit

  • Posted 10 May 2018, 8:41 pm EST

    It is not “limitation” in PDF export. PDF export does not ignore the state of RightToLeft property of the control when receives RTL text.

  • Posted 10 May 2018, 8:53 pm EST - Updated 30 September 2022, 9:06 am EST

    It is not “limitation” in PDF export. PDF export does not ignore the state of RightToLeft property of the control when receives RTL text.

    It is PdfExport issue.

  • Posted 13 May 2018, 8:40 pm EST

    Hello,

    Yes, it is a limitation of our “PDFExport” feature. When text contains some bi-directional text with the non-bi-directional then bi-directional text being export incorrectly.

    Hope it clarifies.

    Thanks,

    Mohit

  • Posted 13 May 2018, 10:52 pm EST

    It is your “PDFExport” bug: when text contains some bi-directional text without English characters and RightToLeft = False (as you defined “non-bi-directional”) then “PDFExport” exports the text incorrectly.

  • Posted 15 May 2018, 12:51 am EST

    Hello Ilia,

    We understand this is a bug in our PDF Export, however, fixing of this lead to many bugs that’s why we treated this as a limitation. Also, I have raised your concerned to our developer team.

    Hope you understand.

    Thanks,

    Mohit

  • Posted 16 May 2018, 3:59 pm EST

    I found workaround. It slows down export.

  • Posted 16 May 2018, 4:02 pm EST

    I found workaround. It slows down export.

  • Posted 17 May 2018, 1:14 am EST

    Hello Ilia,

    Sorry for the confusion,

    It is the limitation of RTL text(even with numbers).

    Thanks,

    Mohit

  • Posted 17 May 2018, 1:16 am EST

    Hello,

    Thanks for the information.

    I am able to replicate the problem at our end. I have escalated this to the development team(257723) and will revert you back once have any information from them.

    Thanks

    Mohit

  • Posted 8 June 2018, 5:56 pm EST - Updated 30 September 2022, 9:06 am EST

    How do you do Mohit,

    First, It is not the limitation of RTL text(even with numbers).

    Second, Here is sample with my workaround.

  • Posted 8 June 2018, 6:02 pm EST

    Second, Here is sample with my workaround. SectionReportApplication2.zip

    Can you open change request to fix this AR12 limitation?

    I am sure you can find the way better than my workaround.

  • Posted 10 June 2018, 7:58 pm EST

    Hello Ilia,

    I have created workaround the existing sample. Please refer the attached sample. Could you please confirm if this workaround is acceptable for you.

    Thanks,

    Mohit

  • Posted 10 June 2018, 11:11 pm EST

    I do not see attached sample.

  • Posted 11 June 2018, 12:14 am EST

    Hello,

    Please refer the attached sample.

    thanks,

    ModifiedSample.zip

  • Posted 11 June 2018, 7:28 am EST

    Your workaround is not acceptable for me. Because unable to cut part of bidirectional text in all cases.

    Please refer the attached sample.

    ModifiedModifiedSample.zip[img]https://gccontent.blob.core.windows.net/forum-uploads/file-9b9c72ed-523d-41d3-9cef-78430ecb93d9.png[/img]

  • Posted 11 June 2018, 4:07 pm EST

    Hello Ilia,

    Could you use “Microsoft Print to PDF” driver to print the report in PDF format instead of exporting the report into the PDF format? If yes, please use the following line of code:

    
      Dim rpt As SectionReport1 = New SectionReport1()
    
            rpt.Run(True)
    
            rpt.Document.Printer.PrinterName = "Microsoft Print to PDF"
            rpt.Document.Printer.PrinterSettings.PrintToFile = True
            rpt.Document.Printer.PrinterSettings.PrintFileName = "444.pdf"
            rpt.Document.Print(False, False, False)
    
    
            Process.Start("444.pdf")
    
    
    

    Note: Import the “GrapeCity.ActiveReports” namespace to use the “Print” function.

    Hope it helps.

    Thanks,

    Mohit

  • Posted 11 June 2018, 10:11 pm EST

    1. “Microsoft Print to PDF” printer driver unavailable in Windows 7, Windows 8, Windows Server 2012.
    2. Works slowler 10 times than AR12.Export.Pdf.
    3. By your sample creates two pages instead of one.
    4. With “Microsoft Print to PDF” unable to sign PDF File.

      I ask. Can you open change request or not?
  • Posted 12 June 2018, 7:49 pm EST

    HEllo Ilia,

    I have raised your issue to our concerned team and will update you once I get any information from them.

    Thanks,

  • Posted 13 June 2018, 5:03 pm EST

    Hello ,

    the limitation mentioned in this ticket has been introduced 10 years ago in ActiveReports 6 per the request from our customer and we did not receive the complaints about this since its implementation. we can’t simply remove it, because it will be a breaking change.

    perhaps you could replace the TextBox control by RichTextBox as workaround in case of RTL text with numbers?

    Thanks,

    Sergey Romanov.

  • Posted 13 June 2018, 8:42 pm EST - Updated 30 September 2022, 9:06 am EST

    How do you do Sergey and Mohitg,

    It seem when TextBox.Text contains only Hebrew you always export as RightToLeft, when TextBox.Text contains only English or Numbers you always export as LeftToRight, when both languages you export by TextBox.RightToLeft property.

    Can you add to GrapeCity.ActiveReports.Export.Pdf.Section.PdfExport

    property to close manually this limitation (close default reading order)?

    This limitation das not allow me to use ActiveReports 12 for 30000 our customers.

    There are some another problems with Export to PDF in both cases (RightToLeft/LeftToRight reading orders) with Numbers and without Numbers.

    The samlpe attached.

    SectionReportApplication2.zip

    P.S. RichTextBox das not have RightToLeft and Alignment properties.

  • Posted 13 June 2018, 10:16 pm EST

    Hello Ilia,

    i have forwarded your reply to PMs team. i will update this ticket when i get any news.

    Thanks,

    Sergey Romanov.

  • Posted 13 June 2018, 11:14 pm EST

    I need to export to pdf as well as in the Viewer now by TextBox.RightToLeft property

  • Posted 17 June 2018, 4:08 pm EST

    Hello Ilia ,

    please open the support ticket here:

    https://www.grapecity.com/en/support/contact

    Thanks,

    Sergey Romanov.

  • Posted 19 June 2018, 6:15 pm EST - Updated 30 September 2022, 9:05 am EST

    How do you do Sergey,

    I tried without success to open the support ticket.

  • Posted 19 June 2018, 7:52 pm EST

    Hello Ilia ,

    could you please try it again? i do not see any certificate issues on my side.

    Thanks,

    Sergey Romanov.

  • Posted 20 June 2018, 12:48 am EST - Updated 30 September 2022, 9:05 am EST

    Windows 10 and Chrome with last updates.

  • Posted 20 June 2018, 3:09 am EST

    Hello Ilia ,

    it is not a problem anymore. as far as i can see the developers team already took the change request. probably you will get a hotfix soon.

    Thanks,

    Sergey Romanov.

  • Posted 26 June 2018, 5:50 pm EST

    Hello Ilia,

    I am glad to tell you that your issue has been fixed now. You can download the latest hotifix from the following link:

    http://cdn.grapecity.com/ActiveReports/ar12/hotfixes/ActiveReports-v12.1.13655.0.msi

    Thanks,

    Mohit

  • Posted 27 June 2018, 2:18 am EST

    How do you do Sergey and Mohit,

    After installing v12.1.13655.0.msi, this problem is fixed.

    It seems that now, when the TextBox.Text contains Hebrew, you are exporting according to the TextBox.RightToLeft property.

  • Posted 27 June 2018, 6:03 pm EST

    Hello Ilia,

    We are fine. We are glad that your issue has been resolved now.

    Thanks,

    Mohit

  • Posted 20 August 2018, 3:13 pm EST

    How do you do Sergei and Mohit,

    After installing v12.2.13986.0, it seems that you export TextBox.Text to PDF according to the TextBox.RightToLeft property in all cases of Bidirectional Text.

    Is my guess correct?

    That a “bidirectional text” limitation of your “PDFExport” is canceled finally?

  • Posted 20 August 2018, 10:01 pm EST

    Hello Ilia,

    Fine, thank you. And you?

    Yes Ilia, but we can’t say that we have overcome all limitations of the “bidirectional text”. You can post the issue if you find any I am more than happy to assist you.

    Thanks

  • Posted 21 August 2018, 2:47 pm EST

    Hello Mohit,

    You do not understand me. I wrote now about “PDFExport” limitations (not bugs), because there are changes in “PDFExport” in v12.2 compared to the last hotfix v12.1, which was not reported anywhere (the case of RightToLeft = True and non-Hebrew text). This change does not make me problems.

  • Posted 22 August 2018, 5:17 pm EST

    Hi Ilia,

    Technically, we just got rid of the inconsistency, between WinViewer and PDF export output, related to the bidirectional text that were reported in a few change requests.

    Thanks,

  • Posted 22 August 2018, 6:56 pm EST

    2XXXXX: Resolved issue with English characters becoming left to right when exporting to PDF.

    257723: Resolved issue with Hebrew characters becoming right to left when exporting to PDF.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels