Context Checking All Files in a Map at once?

Hi Clay,

I tried that before posting, as I too thought it might be the solution. The result is that the Editor happily adds opening/closing elements without reporting a problem. It also simply shows invalid tags in red, instead of reporting them. Requiring someone to carefully scroll through the whole document to find them. I would expect to see a "Parser Messages" window with the errors after the warning that context rules are off. It only shows me this error window when I open the file itself, not when I Edit the Resolved Document, and only for some context errors, not all.

Some context errors trigger this behavior (like an extra <topic> element) but other errors do not trigger a warning, like a malformed element such as<note type="attention">attention<sometext note="> or an extra

2 different translation vendors are returning invalid files to us, and we need an easy way to check a file set before production.

Thanks for the help!

Thanks David,

Setting theparsevalidate option to off helped the problem, and appears to have the same or a similar effect as turning allowinvalidmarkup to off. Both of these options contribute to elements getting balanced automatically, and other auto-edits.

off appears to stop the automatic insertion of elements when editing, for example, when adding a

• element, the Editor automatically adds the first
• element, which is desirable behavior.
  
  
  
  

  " target="_BLANK">mailto:David.S.Taylor@nrc-cnrc.gc.ca>
  
  
  

Hi Clay,

The manual workaround is:

1. 
   
2. to off
3. 
   
4. Do a Completeness Check, so the warnings window displays all of the errors.
5. 
   

But your code snippet below is more like the behavior for which I'm looking. THANK YOU. I look forward to playing with this. If I can figure out how to automatically run this whenever someone opens a map or bookmap, I will have the ideal solution.

Cheers,

Bill

In Reply to Clay Helberg:

Hi Bill--

Hmm, that's weird. Well, if that doesn't work, you ought to be able to do something via ACL. You can use the check_completeness command to do a check of an individual file, so then it's mainly a matter of iterating over the files referenced in a map. As a start, you could use something like this:

# WARNING: Untested code; debugging is left as an exercise
function cc_all() {
local $refs[], $ref;
oid_find_children(oid_null(), $refs, "topicref");
for ($ref in $refs) {
local $fname = oid_attr($refs[$ref],"href");
local doc = doc_open($fname, 0x20); # 0x20 = no warnings on file open
current_doc(doc);
eval "----------------------------------\nDocument $fname:\n" output=>log.txt;
cc -full output=>log.txt;
doc_close(doc);
}
}

Load your map, run this function, and it should generate a log.txt file with info about context errors in the topic files. You'll probably need to beef it up to properly handle references to submaps, keydefs, and maybe a few other things, but hopefully this gives you enough to build on to get to where you want to go.

--Clay

Hi Bill,

For further checking, you can also use Schematron. If you aren't familiar, Schematron allows for a deeper completeness checking for certain conditions that are reported back to the user.

-Jeff

In Reply to David Taylor:

Hi Bill,
Take a look at addrequiredtags, I believe this is the option that will prevent Editor from injecting missing tags into an out-of-context file.

We had problems like this in the past.

Cheers,

David

Hi Jeff,

I found schematron.acl in the AE directory structure, and looking at the comments, it appears to have the kind of function for which I'm looking. Are you aware of any references or instructions for how one might leverage this function? I didn't find much in the Customizing or Admin guides.

Thanks for the post!

Bill