Rendering HTML string in to the Aspose Word document using Linq Reporting Engine

Hi Team,
We want to render HTML content string in to the document using Linq Reporting Engine.
We found expression i.e. <<[html_text] -html>>, which is working fine for some of the tags like bold, Italic and so on.
But Some of the formatting styles (e.g. hyperlink) are getting changed during merge processing.
Do we have any other way or switches similar to -html which we van use for rendering HTML text in to the document using Linq Reporting Engine with proper style and formatting.
Sample HTML which we tried:

<p style=\"text-align: right;\"><strong style=\"font-size: 11pt; font-family: Calibri, sans-serif;\">Video provides a powerful way to help you prove your point</strong><span style=\"font-size: 11pt; font-family: Calibri, sans-serif;\">. </span></p><ol><li><strong style=\"color: rgb(244, 0, 0); font-size: 14px; font-family: courier;\">When you click Online Video, </strong></li><li><strong style=\"color: rgb(244, 0, 0); font-size: 14px; font-family: courier;\">you can paste in the embed code for</strong></li><li><strong style=\"color: rgb(244, 0, 0); font-size: 14px; font-family: courier;\"> the video you want to add.</strong><strong style=\"font-size: 11pt; font-family: Calibri, sans-serif;\"> </strong></li><li><a href=\"https://forum.aspose.com/t/list-of-tags-available-in-linq-reporting-engine/236715/2\">https://forum.aspose.com/t/list-of-tags-available-in-linq-reporting-engine/236715/2</a></li></ol><p><img src=\"https://conga.com/themes/custom/themekit/images/branding/logo-conga-2022.svg\" alt=\"OIP.jfif\"></img></p>

Addition to above issue, We have issue during rendering of the anchor tag
Google Page doesn’t maintain a proper hyperlink style post merge.

@Rajmal
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-25117

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

Thanks for acknowledging the issue and creating a ticket…
Any update regarding the issue now.

@Rajmal We have completed analyzing the issue and put it into the list of issues that are planned for development. But currently it is not yet scheduled for a concrete version of Aspose.Words, so at the moment there is no estimate. We will keep you updated and let you know once the issue is resolved or we have more information for you.

@alexey.noskov @ivan.lyagin Any update regarding the above hyperlink color issue. Is it resolved now?

Thanks,
Rajmal

@Rajmal Unfortunately, the issue is not resolved yet. Currently it is under development. We will be sure to let you know once it is resolved.

Thanks @alexey for the quick response. For your information I am part of ‘Conga’ organization and we already have a paid/enterprise license for this product.
Please look into this on priority, we have to deliver this feature asap.

Thanks,
Rajmal

@Rajmal You should escalate the issue in the paid support helpdesk. Then my colleagues from paid support will rise priority in our defect tracking system.

Hi @alexey.noskov I have logged in through the official email id on the Aspose portal then also I can’t create issue in the paid support.

Can you please let us know how do will get access to the paid support? or if possible please share the details with paid support internally and provide us resolution asap.

Thanks

@Rajmal The issue is already resolved in the current codebase. The fix will be included into the next 23.6 (June 2023) version of Aspose.Words. We will let you know once it is released.

1 Like

Hi @alexey,

Can we get some tentative date for the June release, we have our release planned this month and before that we want to verify changes from our side with latest Aspose release to make sure everything is working as expected.

Let us know.

Thanks

@Rajmal Aspose.Words 23.6 version will be released within a week. We will be sure to let you know once it is available.

1 Like

The issues you have found earlier (filed as WORDSNET-25117) have been fixed in this Aspose.Words for .NET 23.6 update also available on NuGet.

1 Like

@Rajmal

We have introduced the html tag to provide more options on dynamic HTML insertion. For your scenario, please use the following template syntax:

<<html [html_text_expession] -sourceStyles>>
1 Like

Thank you… :slight_smile:

1 Like

@Rajmal

The complete article describing the feature can be found at Inserting HTML Dynamically.

Hi Team,

This issue was started working when we had updated to Aspose.Words to 23.6 but now again we are getting similar issue with 23.6 also.

Below I have shared the screenshot of current behavior in case of hyperlink tag inside html (Template syntax <<html [html_text_expession] -sourceStyles>>).
Please let us know if anything else is changed.

Thank you.

@RajmalConga Could you please share the problematic HTML snippet here for testing? We will check the issue and provide you more information.

I have shared the sample html below.

string htmlStringSample = @"<html>
             <head>
                 <meta charset=utf-8/>
                 <title> Href Attribute Example</title>
             </head>
             <body>

              <h1><span style=\color:#0000ff; font-family: Arial;\>Hello World!</span></h1>

              <p>        
                 To make your document look professionally produced, Word provides header, footer, cover page, and text box designs that complement each other. For example, you can add a matching cover page, header, and sidebar. Click Insert and then choose the elements you want from the different galleries.
              </p>
              <span style=\color: green; font-family: Old English Text MT; font-size:small;\>
                 <a href=\https://www.freecodecamp.org/contribute/\>The freeCodeCamp Contribution Page</a> shows you how and where you can contribute to freeCodeCamp's community and growth.
              </span>
              </body>
            </html>";