Unicode text distorted in PDF export from web viewer

Unicode text distorted in PDF export from web viewer

Posted by: hbkelkar on 13 March 2018, 7:09 am EST

• 

  hbkelkar

  • Post Options:
  • Link
    Copy

  Posted 13 March 2018, 7:09 am EST

  Hello AR Team,

  I am facing trouble in showing Unicode text while exporting to PDF from Web Viewer (AR 11 Professional, VS 2012, Web Viewer PDF Export).

  I have set the textbox font to ‘Tunga’ and the text is correctly displayed in Designer view where as when run on web page , PDF Export distorts the text.

  Please advise solution to this issue.

  Thanks
  
  Hemanth

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 13 March 2018, 6:10 pm EST

  Hello Hemanth,

  Could you please share the following information with us:-

  1. Are you using SectionReport or PageReport
  2. Are you preview the report in “AcrobatReader” viewertype of WebViewer. Or write some code to export the report into PDF format.If yes, please share the ‘PDF Export’ code with us.
  3. Please share the screenshot of the issue.
  4. Please share the exact version of AR that you are using.
     
     5.If possible, could you please share the report with us.

  This will be very helpful for us to replicate the issue at our end.

  Thanks,
  
  Mohit

• 

  hbkelkar

  • Post Options:
  • Link
    Copy

  Posted 13 March 2018, 8:11 pm EST

  Hello, Mohit,

  1. I am Using Section Report.

  2. Showing the report as PDF in viewer page. (Code included here)
     
     Following code is available on the “Page Load” event of the web page , containing web viewer
     
     Viewer Type : RawHtml
     
     Note : Have also checked by setting Viewer Type as : Acrobat Reader , but that dosent show the text at all.

  Dim rpt As New rptRegistrationForm

          rpt.DataSource = dtTable
          rpt.Run(False)
  
          Dim pdf As New PdfExport
          Dim memStream As New System.IO.MemoryStream()
  
          Response.ContentType = "application/pdf"
          Response.Clear()
          Response.AddHeader("content-disposition", "inline;filename=MyPDF.PDF")
  
          pdf.Export(rpt.Document, memStream)
          Response.BinaryWrite(memStream.ToArray)
  
          Response.End()
  

  
  3. Screenshots are shared.
       a. Correct view in Design View of Section Report
       b. Distorted view in Output PDF view in web viewer page.
  
  4. AR Version : 11 Professional , running on Visual Studio 2012.
  
  5. Will redesign the report for testing and share, if still required.
  
  Thanks in Advance.
  
  
  [img]public\uploads\ba4a8e6ca31a086c9742481394d921e71521018703432.jpeg[/img]

• 

  hbkelkar

  • Post Options:
  • Link
    Copy

  Posted 13 March 2018, 8:14 pm EST

  Attachment Missed

  1. Correct text to be displayed as
• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 13 March 2018, 9:16 pm EST

  Hello,

  Thanks for the information.

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

  Thanks
  
  Mohit

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 13 March 2018, 10:07 pm EST

  Hello Hemanth,

  This is the limitation of AR.

  Sorry for the inconvenience caused to you.

  Thanks,
  
  Mohit

• 

  hbkelkar

  • Post Options:
  • Link
    Copy

  Posted 14 March 2018, 4:13 am EST

  Hello Mohit,

  Ok !!
  
  Is there any fix for this issue now or any fix in immediate future. Because I am stuck in a project where AR is must but this is stopping me to publish the project online.

  Waiting for any solution.

  Thanks
  
  Hemanth Kelkar

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 14 March 2018, 10:02 pm EST

  Hello Hemanth,

  We are sorry to mention that there is no workaround for this issue. Also, there is no future plan to get rid of this limitation. I am also discussed with our developer team but we can’t provide any workaround for this. We understand how you feel, it is not possible to fix this issue. It would require a lot of code changes in the exporting engine and might break other things which is currently not feasible.

  Once again, we’re deeply sorry about the issue.

  Thanks,
  
  Mohit