Carriage Return Being Removed From Paragraph, Bug or Functionality


#1

Hi Team,

We’ve recently upgraded Aspose Versions and noticed a slight deviation in the way carriage returns are output on the documents. The old functionality used to work by counting a carriage return if it was by itself in a paragraph (within quotation marks), however it’s now not being recognised within Aspose to do this and just ignores the carriage return.

Worked example of the word document:

First line.
{IF {Condition} = true "

Print This Line Out!
" "(Carriage Return is here, the only thing in this paragraph)
" }
Second Line.

Now the old functionality would print this out as:

First Line.

Print This Line Out!

Second Line.

But the current functionality now disregards the carriage return within the final paragraph, so it looks like this:

First Line.

Print This Line Out!
Second Line.

Hopefully the worked examples above are clear enough. I’m not sure why the template was originally created like this as the first carriage return isn’t in it’s own paragraph but the final one is, but it’s the way the current templates look and used to function, correctly.

Questions:

  1. Does the new version of Aspose (or a recent version upgrade, as we had updated from an older version) change the way carriage returns are used or recognised?

  2. Is there no longer functionality to produce a carriage return within its own paragraph?

  3. Assuming that this is the current functionality and not a bug, at what point did this become used (version number) and what’s the likelihood that it’ll be reverting back? This question is because we have several template documents that use the carriage return syntax as mentioned above and changing them would be a considerable amount of time.

Thanks,
Lloyd


#2

@LloydDavies

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 will start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip and upload them.


#3

Hi,

It appears it was a local environment issue in one of our many lines of code. Sorry for wasting your time!

Thanks,

Lloyd


#4

@LloydDavies

Please feel free to ask if you have any question about Aspose.Words, we will be happy to help you.