🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: adobe.framemaker
Article #22657

Re: FM Conditional Text, Management and Control thereof

#22657
From: Ian Burton
Date: Sat, 21 Dec 2002 10:40
18 lines
3060 bytes
Hello,
My advice to everyone is avoid conditional text. Not because of any difficulty with the FM implementation, but rather because of the inability of humans to define significant names and associated meanings for conditions.

There's the standard condition "comments" - a good name with an unambiguous meaning. You can either hide them or show them. Now consider "Bill's comment" as a condition. At first glance it's just like the standard "comments". What if someone decides to apply the condition to a piece of text that should be in the manual because Bill commented that the particular text should be in the manual.

Now there's confusion, because some "comments" need to be shown and others hidden for final publication.

Therein lies the fundamental problem of conditional text. Not the FM feature but getting a group of people to react identically to a number of alternatives.

I am working on a document just now that has been prepared by a committee of engineers to be published as an industry standard. I have found one line that has so many conditions on it that the condition names run of the edge of the status line bottom left of the screen. The document actually contains such conditions as "Bill's comment" and "Sean's suggestions". In all there are 37 user defined conditions and, above all, nobody ever documented decisions to invent another decision. Basically this Frame document is useless to anyone except the committee secretary who has now left the role and is unreachable.

Someone in this forum, a few weeks ago came up with the idea of defining and documenting all conditions in a chapter attached to the template or manual. That way anyone can see and try out the significance of show and hide for a given condition. I have always used a readme.txt file that contained decisions about the contents of a manual until I heard about this better idea.

So conditional text has a number of positive advantages. But it is the swiftest way to foul up the content, short of encrypting the file and thowing away the key, if conditions are not unique in their name and interpretation, applied uniquely to any particular part of a document, agreed by the team, and documented unambiguously.

Can this be so difficult for wordsmiths?
Cheers
Ian
Technical Details
Message-ID: <1de71700.2@WebX.la2eafNXanI>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-09!supernews.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!proxad.net!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebX
References: <1de71700.-1@WebX.la2eafNXanI>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fd315,aa87813c2e086b29
X-Google-Attributes: gidfd315,public
X-Google-ArrivalTime: 2002-12-21 03:07:28 PST
From: "Ian Burton" <iburton@noos.fr>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-09!supernews.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!proxad.net!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebX
Newsgroups: adobe.framemaker
Subject: Re: FM Conditional Text, Management and Control thereof
Message-ID: <1de71700.2@WebX.la2eafNXanI>
Date: Sat, 21 Dec 2002 02:40:29 -0800
References: <1de71700.-1@WebX.la2eafNXanI>
Lines: 46
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit