Printing out change tracking

[ashah]

Hello Everybody,

I administer Epic 5.3 and the editors in my company use change tracking a lot. The indexers use this to look at the amended documents.

The problem is that when the indexers print out a large chunk of a file, the change tracking will be displayed in some parts of the file but not in others.

Is this an Epic bug?

Thanks,

Ali Shah.

[ebenton]

I'm not claiming to know the answer to this, but I think we will need a little more information from you. Are these XML or SGML documents? Change tracking is done differently in each. SGML uses Processing Instructions (PI) and XML uses namespace elements.

[ashah]

Hi Ed,

This is an SGML doctype. I can send you sample data if you wish.

Thanks,

Ali.

[ebenton]

Like I said, I do not know much about change tracking and I don't use it. However, I believe that change tracking is supposed to be used mainly for editing. If you are trying to print out a composed view of files with change tracking, any change tracking stuff that prints out at all would seem to me to be serendipity. If you are not already doing this, try printing the document using File-Print Editor View.
If that doesn't show everything you want, then I have no clue.

[naglists]

Hi Ali,

I'm still not sure we've totally understood what it is you are trying to
achieve. Here are some additional questions that might further clarify what
it is you're trying to do. (Note that I don't work with SGML change
tracking, so if there may be differences between that and the XML change
tracking I'm familiar with ... Ed already alluded to this a bit, but just to
be clear.)

Do your indexers want to see the red- and green-lining in order to know what
changes have been made so they can modify their indexing work?

Are you saying they see the red- and green-lining in some locations and not
others?

Or, re your indexers seeing the added content but not the deleted content?
Arbortext's default behavior is to output the "Changes Applied" version of
your content but not red- or green-lining.

I believe 5.4 supports publishing the red- and green-lining but I have not
worked with this yet. I think the default behavior is the same, though.


OR are you talking about change bars ... not the actual change tracking
(red- and green-lining) ... but the stylesheet created change bars that run
vertically alongside the content, not within the content, usually on the
right (or outside) side of the page?

[ashah]

Hi Paul,

Thanks for looking at this. I am talking about the actual red/green-lining.

The indexers print out the parts of the file containing redlining/greenlining. They do this from File, Print Editor View.

They want to see both deletions and additions to the file in the printouts in order to modify the indexes.

The sections mostly print out the additions and deletions but some sections get missed out and will appear as normal text (i.e. without showing additions or deletions) and this is the problem area.

Thanks,

Ali.

[naglists]

Ok, now we're on track!

We ran into an odd problem where Editor places a processing instruction in
the XML specifying whether to show content as Before, Highlighted, or After
(not the actual terms, I don't have Editor open right now). This PI will
override interface settings. I'm writing from memory, not my call to PTC
Support that eventually helped us figure this out, so ... I might have the
specifics wrong, but the idea is, I think, solid.

I am going to guess that you are using a content management system. The
interaction between authoring components and this changetrackingresolved
(I'm making up that name, but I think there is one like it) result in some
components Print Editor View-ing as expected while others fail.

Hmmmm. Maybe it is a namespaced element, not processing instruction. Try
looking in the files that fail for the string (using a text editor, not
Editor ... or Editor in text-mode):
<atict:<br/>
<atict:info might=" be=" it.=" there=" might=" be=" an=" attribute=" on=" it=" that=" causes=" this.<br="/>Delete the whole thing (unless you are using this element for part of your
process / lifecycle!).

Good luck!