New line added in PPT export for <style> tags (HTML tags such as <i></i> as well)

Using aspose.slides.jasperreports.library-18.1 to export Jasper report into PPT.
Most of the text boxes in my Jasper report design use Styled markup.
For example: “normal italic normal”
It results in “normal italic normal” text.

When exported to PPT using Aspose.Slides, “italic” text is correctly displayed in Italic format but there is a new line before and after each tag (closing and opening tags).
“normal
italic
normal”

Any advice?
thank you

@gzwierzy,

I have observed your comments. Can you please share sample file, generated result along with environment details so that we may further investigate to help you out.

Thank you for a reply.
I created sample, basic file to demonstrate the problem.

  1. test1.jrxml - Jasper design file, using Jasper 6.0, design file created using Jasper Studio
  2. report.rtf - test1.jrxml exported into RTF using Jasper built-in exporting capabilities
  3. report.ppt - same Jasper file, test1.jrxml exported into PPT using Aspose.Slides (aspose.slides.jasperreports.library-18.1.jar)
    Export is done using Java Servlet (JRE 1.8).
    Let me know please if you have any additional questions.
    Looking forward to your reply.

new-line-problem.zip (35.8 KB)

@gzwierzy,

I have observed your comments. An issue with ID SLIDESJR-33292 has been created in our issue tracking system to further investigate and resolve the issue. This thread has been linked with the issue so that you may be automatically notified once the issue will be fixed.

thanks, looking forward to the fix

@gzwierzy,

Your very welcome. We will share good news with you soon.

Hello, wondering if there is any update on the issue?
thanks

@gzwierzy,

I have verified the issue status from our issue tracking system and like to share that it has been marked as resolved in upcoming Aspose.Slides for Jasper Reports 18.2. We will share the automatic notification with you as soon as the product will be shared online.

great news! much appreciated

The issues you have found earlier (filed as SLIDESJR-33292) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by mudassir.fayyaz

Hello,
I downloaded Aspose.Slides for JasperReports 18.2.
It throws runtime exception when generating PPT report.
Note that same Jasper report (JRXML) / Java code works fine aspose.slides.jasperreports.library-18.1.jar.
Could you please check it out.
thank you
Exception


Problem accessing /portal/report. Reason:

INTERNAL_SERVER_ERROR

Caused by:

java.lang.ExceptionInInitializerError
at com.aspose.slides.jasperreports._jri.gy3.(Unknown Source)
at com.aspose.slides.jasperreports._jri.gy3.(Unknown Source)
at com.aspose.slides.jasperreports._jri.da.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.qt.(Unknown Source)
at com.aspose.slides.jasperreports._jri.gwy.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.gwy.(Unknown Source)
at com.aspose.slides.jasperreports._jri.gwz.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.gwz.(Unknown Source)
at com.aspose.slides.jasperreports.ASPptExporter.do(Unknown Source)
at com.aspose.slides.jasperreports.ASAbstractExporter.exportReport(Unknown Source)
at ca.qtqi.portal.reports.ReportServlet.generatePPTOutput(ReportServlet.java:414)
at ca.qtqi.portal.reports.ReportServlet.generateReport(ReportServlet.java:178)
at ca.qtqi.portal.reports.ReportServlet.doPost(ReportServlet.java:114)
at ca.qtqi.portal.reports.ReportServlet.doGet(ReportServlet.java:103)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
at org.apache.wicket.protocol.http.servlet.WicketSessionFilter.doFilter(WicketSessionFilter.java:159)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:263)
at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: java.lang.IllegalStateException: Resource file templates.zip not found in assembly.
at com.aspose.slides.jasperreports._jri.aps.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.aps.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.p2.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.p2.(Unknown Source)
… 38 more

Caused by:

java.lang.IllegalStateException: Resource file templates.zip not found in assembly.
at com.aspose.slides.jasperreports._jri.aps.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.aps.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.p2.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.p2.(Unknown Source)
at com.aspose.slides.jasperreports._jri.gy3.(Unknown Source)
at com.aspose.slides.jasperreports._jri.gy3.(Unknown Source)
at com.aspose.slides.jasperreports._jri.da.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.qt.(Unknown Source)
at com.aspose.slides.jasperreports._jri.gwy.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.gwy.(Unknown Source)
at com.aspose.slides.jasperreports._jri.gwz.do(Unknown Source)
at com.aspose.slides.jasperreports._jri.gwz.(Unknown Source)
at com.aspose.slides.jasperreports.ASPptExporter.do(Unknown Source)
at com.aspose.slides.jasperreports.ASAbstractExporter.exportReport(Unknown Source)
at ca.qtqi.portal.reports.ReportServlet.generatePPTOutput(ReportServlet.java:414)
at ca.qtqi.portal.reports.ReportServlet.generateReport(ReportServlet.java:178)
at ca.qtqi.portal.reports.ReportServlet.doPost(ReportServlet.java:114)
at ca.qtqi.portal.reports.ReportServlet.doGet(ReportServlet.java:103)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
at org.apache.wicket.protocol.http.servlet.WicketSessionFilter.doFilter(WicketSessionFilter.java:159)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:263)
at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)


@gzwierzy,

I have observed the feedback shared by you and request you to please share the JRXML file that is reproducing the issue on your end (if some new one has been used). Please share the requested information so that I may consult our product team further in this regard.

Same JRXML, already shared, has been used in test (test1.jrxml).
Run-time exception occurs only with 18.2 product version, not with 18.1
thank you

@gzwierzy,

Please accept my apology for inconvenience on your end. An issue with ID SLIDESJR-33295 has been created in our issue tracking system to further investigate the issue and we will share the good news with you as soon as the issue will be fixed.

Hello,
Is there ETA for the fix? We are about to purchase Aspose.Slides OEM license but would like to make sure that latest product version works fine first.
thank you!

@gzwierzy,

I have observed your comments. I like to share that this issue is going to be resolved tentatively in Aspose.Slides 18.3. We will share good news with you soon.

Is there ETA for the fix? thank you

@gzwierzy,

I have verified the issue status from our issue tracking system and like to share that the concerned issues has been marked as resolved in upcoming Aspose.Slides for Jasper Reports 18.3. We will share the good news with you as soon as the product will be shared online.

Hello, Is there ETA for 18.3 release? thank you

@gzwierzy,

The concerned product release shall be shared online in coming week most likely.