[BUG] Simple xsl:fo crashes pdf component


#1

Hi, could you explain to me why this xsl:fo crashes the pdf generator?
Tested with 17.12.0. Works with other components

<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
<fo:layout-master-set>
	<fo:simple-page-master master-name="A4" page-width="210mm" page-height="297mm">
		<fo:region-body/>
	</fo:simple-page-master>
</fo:layout-master-set>
<fo:page-sequence master-reference="A4">
	<fo:flow flow-name="xsl-region-body">
		<fo:block white-space-collapse="false" white-space-treatment="preserve" linefeed-treatment="preserve">
			<fo:block text-align="center">
				<fo:inline>Part II</fo:inline>
			</fo:block>
		</fo:block>
	</fo:flow>
</fo:page-sequence>
</fo:root>

Thanks
Martin


#2

@Martin_Osterberg,

An online XSL - FO validator shows the parsing error as follows: image.png (1.4 KB). Please review the XSL-FO content, and then let us know if Aspose.Pdf API does not recognize a valid XSL-FO file.


#3

@imran.rafique

Hi Imran,

The validator you used is for xslt, this is xsl:fo.
You can use this validator at the bottom of the page:
http://www.utilities-online.info/foprender/#.Wjd06d-nGbg

The xsl:fo is valid according to this.

Best regards
Martin


#4

@Martin_Osterberg,

We have logged an investigation under the ticket ID PDFNET-43900 in our bug tracking system. We have linked your post to this ticket and will keep you informed regarding any available updates.


#5

Great!, thanks.


#6

Any update on this issue?
Thanks


#7

@Martin_Osterberg,

The linked ticket ID PDFNET-43900 is pending for the analysis and not resolved yet. We will investigate as per development schedules, and let you know once a significant progress has been made in this regard.


#8

Any news on this? This is getting frustrating.


#9

@Martin_Osterberg

Thank you for getting back to us.

We are afraid this ticket is still pending for investigations owing to previously logged tickets. We have increased the priority of this ticket to next level and will schedule it soon. We appreciate your patience and comprehension in this regard.

However, we also offer Paid Support, where issues are used to be investigated with higher priority. Our customers, who have paid support subscription, report their issue there which are meant to be investigated urgently. In case your reported issue is a blocker, you may please consider subscribing for Paid Support. For further information, please visit Paid Support FAQs.


#10

Thanks for giving this more attention.
Regarding paid support, spending $10k on a pdf component one would think it should be able to handle centered text while also preserving multiple spaces without crashing.


#11

@Martin_Osterberg

We definitely value your concerns and realize the significance of the issue. Please note that we provide resolution against every issue reported by our customers - however, issues logged under free support model are resolved on first come first serve basis, which we believe, is the fairest policy. We will let you know as soon as there will be any significant update regarding this ticket.