Bold Segment Breaks Words

Aspose.PDF Product Family
1

Hi

I am using Visual Studio 2010, .NET 4.0, with Aspose PDF Generator 8.8 (I believe that’s the latest version as of this posting).
I have discovered a bug when rendering a paragraph that contains a segment with the IsTrueTypeFontBold attribute set to true. If the segment is positioned within the text so that it would not have wrapped if the bold attribute was set to false, it will break the last word when the bold attribute is set to true.
See the attached file for an example. In the sample, when the segment “Environment and Communications” is bold, the “s” on the end of Communications is rendered on the next line, whereas, if it is not bold, it is all rendered on the one line.
It would be preferable to render the whole word on the next line when bold in this circumstance.
The IsAutoHyphenated attribute has no apparent effect in this case.

Thanks
Chris Fairall
2

Hi Chris,


Thanks for contacting support.

I have tested the scenario and I am able to
notice the same problem. For the sake of correction, I have logged this problem
as PDFNEWNET-36347 in our issue tracking system. We will further
look into the details of this problem and will keep you updated on the status
of correction. Please be patient and spare us little time. We are sorry for
this inconvenience.
3

Hi

I have some further information regarding this issue. I was doing some experimenting with another sample, and I’ve discovered that the problem seems to have nothing to do with the formatting of the second segment. It seems to be a problem when the first word of the segment is the one that should have wrapped to the next line. If an additional segment contains more than one word before a line break, everything seems to be fine.
See my attached example for some sample paragraphs.
This is also a problem within table cells.

Could you please provide some idea of time frame for this, and the other issues I have raised to be looked at? I don’t mean to be pushy, but it has been more than six months since the original issue (http://www.aspose.com/community/forums/526096/paragraph-indenting-with-isfirstparagraph-and-iskeptwithnext/showthread.aspx#526096) was raised, and we do have commercial imperatives to deal with.

Thanks
Chris Fairall.

4
Hi Chris

ChrisFairall:
Hi
I have some further information regarding this issue. I was doing some experimenting with another sample, and I've discovered that the problem seems to have nothing to do with the formatting of the second segment. It seems to be a problem when the first word of the segment is the one that should have wrapped to the next line. If an additional segment contains more than one word before a line break, everything seems to be fine.
See my attached example for some sample paragraphs.
This is also a problem within table cells.

Thanks for your findings. We have shared your observation and sample document with the development team. Definitely it will help us to resolve the issue. We will keep you updated about the issue resolution via this forum thread.

ChrisFairall:
Could you please provide some idea of time frame for this, and the other issues I have raised to be looked at? I don't mean to be pushy, but it has been more than six months since the original issue (http://www.aspose.com/community/forums/526096/paragraph-indenting-with-isfirstparagraph-and-iskeptwithnext/showthread.aspx#526096) was raised, and we do have commercial imperatives to deal with.

Moreover in reference to your update request of your other logged issues, We are looking into these and will update in respective thread.

We are sorry for the inconvenience caused.

Best Regards,
5

Hi

Could you provide an update as to the progress of this issue? It has been almost 18 months since I originally raised it.

Thanks
Chris Fairall.
6

Hi Chris,


Thanks for your patience.

As requested in other forum thread, I am afraid the issue reported earlier is not yet resolved. However I have requested the development team to share the possible ETA. As soon as we have some further updates, we will let you know.