Context matching for element but formatting like text color, indent not reflecting in published PDF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Context matching for element but formatting like text color, indent not reflecting in published PDF
I have applied a condition to a context of the 'p' element in Arbortext Styler. And when I point to the text in editor it highlights this context and the sub-condition correctly.
But when I publish the pdf the styling defined for the condition like text color, size, indent, etc., don't reflect in the published PDF.
How can I debug this issue to find out where is the styling coming from for this element and how can I change it?
Here's a snap of the mentioned context and condition with the document structure in editor in the background:
Solved! Go to Solution.
- Labels:
-
Arbortext Content Delivery
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I am no styler expert, but from what I understand the lowest context that turns green is the one that is used. So the changes need to be on the context below the one you have selected in the above screen shot.
I would probably change the disclaimer to use the output class element to trigger the change. Then create a property set that has the styling changes you want in it. Then you can assign the property set to the context, giving you maximum reusability.
Bryon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I am no styler expert, but from what I understand the lowest context that turns green is the one that is used. So the changes need to be on the context below the one you have selected in the above screen shot.
I would probably change the disclaimer to use the output class element to trigger the change. Then create a property set that has the styling changes you want in it. Then you can assign the property set to the context, giving you maximum reusability.
Bryon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello @PV_12583628,
It looks like you have some responses from some community members. If any of these replies helped you solve your question please mark the appropriate reply as the Accepted Solution.
Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.
Thanks,
Vivek N.
Community Moderation Team.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
@bfriesen and @manpsingh Thanks for the reply.
@bfriesen This way of having an output class did help. So I am accepting it as a solution. But unfortunately, I can't have that as a possibility in the input.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello Dear,
From the above snapshot, it'll only take the effect wherever the condition lies for <p> everywhere else.
Just to double check, <p> element for which you are expecting to behave correctly should not be the part rest of the <p> element condition. I hope it works for you. Thank you
Regards,
Manpreet Singh
