Solved: Arbortext Editor 6.0 Build 040 Completeness Checke...

RobertWilliams · ‎Jun 13, 2012

Hi all,

Having just updated one of our standalone workstations to Arbortext Editor 6.0 Build 040, we've noticed that the Completeness Checker now gives us errors for empty tags - which is a problem. (We've still got other stations running 6.0 Build r60m010 without this problem).

Background - We're a small shop doing DoD Military XML Tech Manuals using US Army LOGSA DTDs and Stylesheet filesets. During tech manual development, many of our tags (particularly parts data) have empty tags (immature parts data during TM development cycle), but the tags themselves (and some attributes) are required by the DTD.

We try to have everyone here diligently use the completeness checker, to ensure that our content is tagged as error free as possible. This is particularly helpful with newer, inexperienced TM developers. Everything runs cleaner that way, from our end and gov't receipt - almost singing Kum-bah-ya.

Problem: With Arbortext Editor 6.0 Build 040, the Completeness checker is now flagging hundreds (if not thousands) of errors for empty tags in our parts data areas, which gums up our ability to find and fix real tagging problems. Until this latest change, we were able to deliver draft TMs of upwards of 1300 pages with zero parsing or completeness errors that we could detect. Until today. We were smiley happy people... until now. What do we do?

Questions:

1. Has anyone else experienced a similar problem? (and found a sane, painless way around it, mayhaps?)

2. Is there a way to 'tune' the completeness checker to have it iggy empty tags?

3. Any ideas? Any at all?

Thanks in advance for reading. Any and all insights greatly appreciated (particularly by the newbie XML TM developers here.)

Respectfully,

Bob Williams

Tech Research Group

(a tiny little tech manual shop in)

East Providence, Rhode Island

TEL 401.434.4680 (Office)

EMAIL robert.williams@techresearchgroup.com

Pushpinder_Toor · ‎Jun 13, 2012

Hi Bob,

I would suggest you review how to do this by finding the Online Help topic titled "Disabling warnings about empty tags", This topic walks you through the steps to modify the correct categories in your DCF .

In a nutshell, you can simply open your DCF file in Editor and modify the correct options. Basically, there is an attribute- warnAboutEmptyElements - that we added to the <DocumentTypeConfiguration> element. By default it is set to "yes", change this to "no". See screenshot below. It is simliar steps to do this on an element by element basis and not globally for the whole document type.

Pushpinder

View solution in original post

Pushpinder_Toor · ‎Jun 13, 2012

Hi Bob,

This feature was added in M040 based on customer requests that they have their empty tags flagged as warnings (not errors).

However, you can turn this warning off at either the document type level or on an element by element basis, via the DCF (.dcf) file. By default, the warning is always shown.

Pushpinder

RobertWilliams · ‎Jun 13, 2012

Thanks for replying. However, our DTD is locked by the customer (DoD - Military, US Army LOGSA), and we (simple, humble users) have no DCF file expertise. I have a DCF file that one of your folks at Arbortext (Jerry Tippie) created for us, quite a long time ago.

If anyone out there has further advice on how to mod our DCF file to turn off this empty tags warning in a (or 'our') DCF file, we're all ears here.

(DCF file contents below)

Regards and thanks,

Bob Williams

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE DocumentTypeConfiguration PUBLIC "-//Arbortext//DTD Document Type Configuration 2.0//EN"

"dcfdtd.dtd">

<Options allowApplicationToolbar="yes" allowComposeStylesheetList="yes"

allowFosiMod="yes" allowTouchup="yes" protected="no"></Options>

<Graphic element="graphic" entity="boardno" filename=""

horizScale="hscale" reproDepth="reprodep" reproWidth="reprowid"

scaleToFit="scalefit" vertScale="vscale"/>

<Graphic element="authent" entity="boardno" filename=""

reproDepth="reprodep" reproWidth="reprowid"/>

<Graphic element="back" entity="boardno" reproDepth="reprodep"

reproWidth="reprowid"/>

<Graphic element="inlinegraphic" entity="boardno" horizScale="hscale"

reproDepth="reprodep" reproWidth="reprowid" scaleToFit="scalefit"/>

<Graphic element="symbol" entity="boardno" horizScale="hscale"

vertScale="vscale"/>

<Graphic element="icon-set" entity="boardno" reproDepth="reprodep"

reproWidth="reprowid"/>

<Graphic element="da2028" entity="boardno" reproDepth="reprodep"

reproWidth="reprowid"/></Specials><?Pub Caret -1?>

</DocumentTypeConfiguration>

<?Pub *0000030896 0?>

Pushpinder_Toor · ‎Jun 13, 2012

Hi Bob,

I would suggest you review how to do this by finding the Online Help topic titled "Disabling warnings about empty tags", This topic walks you through the steps to modify the correct categories in your DCF .

In a nutshell, you can simply open your DCF file in Editor and modify the correct options. Basically, there is an attribute- warnAboutEmptyElements - that we added to the <DocumentTypeConfiguration> element. By default it is set to "yes", change this to "no". See screenshot below. It is simliar steps to do this on an element by element basis and not globally for the whole document type.

Pushpinder

RobertWilliams · ‎Jun 13, 2012

1 problem solved, 1 remaining:

Adding the warnAboutEmptyElements="no" to the DCF file <options> did indeed stop the hundreds of empty elements warnings when a Completeness Check was selected from the toolbar - thanks.

However - we still get a single 'on load' markup error warning, which shows up as a Completeness Checker Errors dialog box (emptyElements) and when clicked on, yields " _comment " and " 1 " in the results dialog.

No location can be found - Suggestions?

Obviously, we appreciate the assist - this is great progress. However, if possible, we'd like to continue to pursue a clean result (which we had before the erstwhile 'upgrade' to build 040.

Thanks,

Bob Williams

TRG Inc.

Pushpinder_Toor · ‎Jun 18, 2012

Bob,

An _comment is an XML comment that's been added to your document. This was most likely done via the Insert> Comment menu in Editor.

I'm not sure what you mean when you say that no location was found. When you click on the warning in the Completeness Check dialog, it should open the Empty Elements dialog.

Then you click on the result in the Empty Elements dialog, it should take your cursor to the location in the document where that comment exists.

Hope this helps,

Pushpinder

Arbortext Editor 6.0 Build 040 Completeness Checker - Empty Tag Errors

Arbortext Editor 6.0 Build 040 Completeness Checker - Empty Tag Errors