Atomik Xport SE: Reference > Chapter 8 Content Proofing << >>

8.1 The Proofing Log

This Proofing Log will list all content from the layout which was not extracted. There are several possible situations where content may not have been extracted:

‘Matched Rules invalid in XML Context’

The first is where a rule exists for the style but the content was not extracted. This occurs when the resulting element would have been invalid in the context, in other words your DTD did not permit the element to appear at that point in the XML structure. In these cases the text will be listed in the Proofing Log with the description ‘Matched Rules invalid in XML Context’ For example if you had a project with a style named ‘01. Author’, assuming you wanted to extract this content, in the ruleset there would be a rule that related the ‘01. Author’ style sheet to the Author element. If for any reason there is text on the page that is styled with the ‘01. Author’ style sheet but this text is not extracted, it is safe to assume that this was not what the user intended to happen. Therefore the text that was styled with the ‘01. Author’ style sheet and wasn’t included in the extraction will instead be listed in the Proofing Log. By viewing the Proofing Log after a layout has been added to the XML Preview, you can immediately see if there is content in this file that should be in the XML.

‘Image found but invalid in XML Context’

In this case, an image was not extracted despite there being an image element declared in the DTD. The image was not extracted because the DTD did not allow an image element to occur at that point in the XML structure.

‘No Rules Match Style’

The second case is where a rule did not exist for content and hence the content was not extracted. In summary, this is everything else that you most likely didn’t want including in your XML. For example page numbers or headers and footers. However when you are initially configuring your rulesets, this file is useful for spotting content that you should have included in the ruleset but did not.

‘Image found but no Image element in DTD’

The image was not extracted because the DTD does not contain a declaration for an image element. Note that you should specify your designated image element in the Element Roles dialog, accessible from the DTD tab of the Ruleset Editor.

‘Image set to be Excluded’

The image was not extracted because the picture box containing the image was manually set to be excluded. This setting can be toggled from the Atomik Tools

‘Box set to be Excluded’

The text was not extracted because the box containing the text was manually set to be excluded. This setting can be toggled from the Atomik Tools.

Identifying the listed content on the page

The Proofing Log lists the page number against each item of content that hasn’t been extracted. It can go further in helping you identify the listed content, however, because it can also select the content on the page and scroll it into view. To find the content on the page, simply double-click on the entry in the Proofing Log. You will then find that the relevant page is displayed and the corresponding text has been highlighted. If the content listed in the Proofing Log is an image rather than text, then the picture box will be selected.

Note, you may need to move the palette to view the highlighted text if the text is hidden by the palette. If the referenced content is in overmatter then it will not be selected on the page, but its textbox will be selected.