disagreement on overrides

[Art Campbell]

Well, I'm with you and your approach simply because it makes it much
easier to work on and to ensure consistency, because only the person
who created them knows what the override is supposed to do.

There's also the possibility that the override will be interpreted
somewhat differently than its intention in PDF, but I think it only
makes a BIG difference when you start supporting more output formats
or some of the overrides don't work as intended.

Output and conversion filters, in general, don't like overrides, so
something is going to fall out of the document and not get translated.
And then there's going to be some fast shuffling, on deadline, to make
it all work again. And that can be avoided if you impose some controls
via para and character tags early on.

Getting a writer who doesn't see the value in this, or who doesn't
want to comply, is the problem, and that's a human relations problem.
If you're peers, and management isn't setting a course that makes
fewer overrides a logical way to do things.... If you have some
authority to set things up that makes it slightly easier and
different.

Art

On Thu, Jun 12, 2008 at 5:26 PM, Milan Davidovic <milan.lists at gmail.com> wrote:
> The way I've been "brought up" as a Frame user was to avoid overrides
> wherever possible. I'm now working with a writer who is much more
> liberal about overrides than I am. We currently work only on
> unstructured Frame documents; output is PDF (to print from or for use
> onscreen). Right now, we're the only two writers working on the doc
> set in question.
>
> Have any of you been on either side of such a difference in approach,
> and how did you go about resolving it?
>
> Thanks.
>
> --
> Milan Davidovic
> http://altmilan.blogspot.com

-- 
Art Campbell art.campbell at gmail.com
 "... In my opinion, there's nothing in this world beats a '52 Vincent
and a redheaded girl." -- Richard Thompson
 No disclaimers apply.
 DoD 358