🚀 go-pugleaf

In article <1992Nov11.134125.20716@sei.cmu.edu>, bjz@sei.cmu.edu (Barbara Zayas) writes:
|> 
|> I'm running 3.1X on a Sun4.
|> 
|> Very often when I use keyboard commands (ctrl-v, esc-v) to
|> scroll through the Paragraph Format window, when I pass over
|> the Numbering sheet, although I've not made ANY changes to
|> that sheet (or any of the surrounding sheets a lot of the
|> time), FM prompts me as to whether the changes should be
|> applied or not before moving me from the Numbering sheet onto
|> the next (or previous) sheet.


Thanks to Alan Koch for discovering the cause of this problem:

>After some investigation we have discovered that this ALWAYS happens when:
>1.  There is an autonumber format displayed AND
>2.  The format includes any building block (\t, \b, or anything in <>'s), AND
>3.  The format was defined in FrameMaker 2, AND
>4.  The Numbering Property Sheet for that paragraph has never been applied
>    under FrameMaker 3.

>If you answer "Apply" to the dialog, it will never happen on that paragraph
>again.  

>If you save an offending document to MIF, then open the MIF, this STILL
>happens, so I examined the MIF and discovered a difference between the way
>FrameMaker 2 and 3 specify autonumbers.  (See below.)  Clearly, it is this
>difference which is causing the problem.

== Paragraph that the Numbering Property Sheet does NOT complain about =======
 <Para 
  <PgfTag `bu'>
  <Pgf 
   <PgfNumFormat `B:n\t'>
  > # end of Pgf
  <PgfNumString `n\t'>
  <ParaLine 
   <String `Start FrameMaker.'>
  >
 > # end of Para
== Paragraph that the Numbering Property Sheet DOES complain about ===========
 <Para 
  <PgfTag `bu'>
  <PgfNumString `n\t'>
  <ParaLine 
   <String `Move FrameMaker windows.'>
  >
 > # end of Para
== End of samples ============================================================






Barbara Zayas				Software Engineering Institute
Information Management			Carnegie Mellon University
bjz@sei.cmu.edu				(412) 268-6378