Re: [FrameSGML] Upgrading an EDD to Version 7

["Lynne A. Price" <lprice@xxxxxxxxxxxx>]

At 09:32 PM 7/4/02 -0700, Dan Emory wrote:
>At 03:57 PM 7/4/02 -0700, Lynne A. Price wrote:
>
>>Dan,
>>   As long as you're using the English version of FM 7.0, all you have to do
>>is open the FM+SGML 6.0 EDD in FM 7.0 and import its element definitions into
>>a document. FM 7.0 will make the necessary changes.
>
>By necessary changes, I assume you mean the required changes to the FM6.0 
>EDD, and in particular changing the value in the Version element.

Dan,
  The Version element is actually empty; the text "EDD Version is xxx" is
a prefix, so there's nothing for you to change there. Again, once the
FM 7.0 element definitions are imported, the only change that I remember
must be made to a 6.0 EDD is to change SGMLApplication to StructuredApplication.
There are a few things available in FM 7.0 EDDs that aren't available in
6.0 EDDs--in particular, running header/footer variables 5 thru 12--but
they won't occur in your 6.0 EDDs so that's not a problem.

>As I 
>recall, the action you describe above was the way it worked in FM+SGML 5.5, 
>but taking that same action in FM+SGML 6 did not produce that outcome.

Since there were no functional EDD changes from 5.5.6 to 6.0, FM+SGML 6.0
was quite happy to process 5.5.6 EDDs and there was no need to change them.
Because of the two changes mentioned above, FM 7.0 cannot process a 6.0
EDD without updating it.

 
>...the problem is that the FM+SGML6 EDD uses your version of the 
>Meta EDD for FM+SGML6, thus the auto-update performed by FM7 would corrupt 
>my EDD, wouldn't it? 

The automatic process won't corrupt your EDD, but it's likely to result
in an invalid EDD since Comments will only be allowed at the start and
end of an element definition and List, Note, etc. won't be defined. So
you'll need to import element definitions from my 7.0 meta-EDD.


>And if that is the case, have you released your 
>version of the Meta EDD for FM7?

Yes, it's available at www.txstruct.com in the Tools and Tips section.
There's a formatting change from the 5.5.6/6.0 version: it repeats
the rule number on "else" and "else if" clauses, using successive letters
to distinguish the clauses. Since numbering every clause means numbers no 
longer identify the beginning of a rule, it marks the beginning of each rule 
with a bullet. This formatting should make it easier for a reader to see which 
"if" clause matches a particular "else" clause in a long element definition with 
deeply nested format rules. The following example provides a skeleton of a typical 
set of text format rules:

. 1(a)  In all contexts ...
. 2(a)  If context is ...
  2(b)  Else, if ...
  2(c)  Else, if ...
        2.1(a) If context is ...
               2.1.1(a) If context is ...
               2.1.1(b) Else ...
        2.1(b) Else, if context is ...
               2.1.2(a) If context is ...
               2.1.2(b) Else ...
. 3(a)  If context is ...
  3(b)  Else, if context is ...
  3(c)  Else ...

	--Lynne

Lynne A. Price
Text Structure Consulting, Inc.
Specializing in FrameMaker+SGML consulting and training
lprice@txstruct.com
http://www.txstruct.com
voice/fax: (510) 583-1505
cell phone: (510) 421-2284


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **