🚀 go-pugleaf

Richard Kooijman writes:

> I tried to move a style off code in my document yesterday, and everything
> seemed to have worked fine.
> Until I noticed that all my other styles in the document after the moved one
> were screwed up.

You can move an open style or an on/off pair of styles, but not just the
style-on or style-off.  

What happens is this:  

	When you move only the style-on code, WP cancels the ending style-off
	code.
	
	When you move only the style-off code, WP cancels the beginning 
	style-on code.
	
	Except, it's not quite that simple.
	
Think of a style as a subroutine where the style-on call is the CALL 
statement and the style-off code is the return statement -- the actual 
section of the document is stored that way -- the style-on code points
to an out-of-line piece of the document.  When the out-of-line piece ends,
you return to the main section.  Of course, you can have styles-within-styles,
etc., so it's sort of recursive nesting.

If you delete  either style-code (which a move does), WP eliminates the 
other code.  If you do home, home, home, up and then home, home, down, you 
will find them both gone.  If you just look at reveal codes after the move,
they may appear to still be there, but that's just because the reveal codes
is now out-of-sync with reality.

If you want to have lots of fun, include a block protect in a paired style
and then insert a hard page inside the block.  WP will generate block protect
on and off codes all over the place and things really won't work right.

Good luck

Jim Winer -- jwi@mtfme.att.com -- Opinions not represent employer.
------------------------------------------------------------------
"No, no: the purpose of language
	is to cast spells on other people ..."
					Lisa S Chabot