XAML print module vs batch processor

[jonz]

OK I have a basic question: Why can't I paste XALM that works from the batch processor to the print module? It seems like what works in one should work in the other.

[Mario]

It would help if you would provide an example of the XAML you use. The error messages you see in Design & Print etc.

Not much we can work with so far...

[jonz]

From batch processor text overlay:

<Run FontFamily='Arial Narrow' FontSize='45px' FontWeight='Bold' Foreground='#474747'>{File.MD.XMP::dc\title\Title\0}</Run><Run FontFamily='Arial Narrow' FontSize='45px' FontWeight='Light' Foreground='#474747'>  {File.MD.XMP::dc\description\Description\0}</Run>

Very hard to read the error message in Design & Print, but I believe it says:

Markup Error: 'CXTPMarkupRun' object cannot be added to 'CXTPMarkupCollection". Object cannot be converted to type 'CXTPMarkupUIElement'

This is when placing in text properties box with "interpret as XAML Markup" checked.

[Mario]

A <Run> cannot exist on its own.
You need to wrap your markup in a <TextBlock></<TextBlock>

The Batch Processor does this implicit, but D&P gives you more freedom.
Please see the markup examples in the D&P help topic for more info.

[jonz]

OK, I will. Thank you for the clarification. Could you please correct the title so this can be searched?