We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Gibberish/garbage characters

We are using Aspose.Words and Aspose.Pdf to generate documents.

We encountered an error while trying to generate a table out of a comma-separated list of items.

The following SQL query converts the comma-separated list into individual lines.

WITH DATA AS ( SELECT :id12 as str FROM dual ) SELECT trim(regexp_substr(str, ‘[^,]+’, 1, LEVEL)) AS r1 FROM DATA CONNECT BY regexp_substr(str , ‘[^,]+’, 1, LEVEL) IS NOT NULL

where :id12 is the comma-separated list.

The following example illustrates the issue we are experiencing.

Comma-separated list (:id12)

(see image1)

After the code is executed, the result of the template field replacement is:

(see image2)

Note: The GLASTONBURY is part of a different field in the document.

After restarting the server, the field is correctly generated (no code has changed).

(see image3)

Please advise.

Hi there,

Thanks for your inquiry. To ensure a timely and accurate response, please attach the following resources here for testing:

  • Your input Word document.
  • Please attach the output Word file that shows the undesired behavior.
  • Please create a standalone console application (source code without compilation errors) that helps us to reproduce your problem on our end and attach it here for testing.

As soon as you get these pieces of information ready, we'll start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip them and Click 'Reply' button that will bring you to the 'reply page' and there at the bottom you can include any attachments with that post by clicking the 'Add/Update' button.

Thank you for your prompt response.

We believe that a standalone application will not help. This behavior is observed only within an app pool on the website and does not happen on a single run consistently. It goes away after the app pool is restarted.

Have you experienced this before and do you have another idea of how we can reproduce and show you the issue?

thank you

Hi there,

Thanks for your inquiry.

I am afraid, it is difficult to say what is the problem without code and document. Please create a simple web application (source code without compilation errors) that helps us reproduce your problem on our end and attach it here for testing. Thanks for your cooperation.