Ok, so I tried dropping in those snippets into the opsusual file (opusualwp-v5_0.xsl), and it ran, did not correct anything (still no pagination effects), but kicked some errors about finding the processing instructions in multiple locations or something, which led me to (a) remove the snippet, and (b) look inside the 'pi-v5_0.xsl' file, where I find that there are allowances made for (what appears to be) Arbortext touch up commands like newpage, etc.
So, now I think I'm going to say uncle at this point. Maybe I'm causing problems by not sticking to the PTC/Arbortext/custom/doctypes/catalog file structure. Quite awhile back (working with multiple Mil-Stds and stylesheets), I started simply dropping a copy of the DTD and stylesheet files co-located with the XML that I was working on (seemed to make it easier at that time.)
Now I'm wondering if I simply go back to a standard catalog/dtd/stylesheet file structure setup.... if this problem may simply resolve itself. If that doesn't work, I'm game to try something else.
I take it that because this would (obviously) be a (use of/setup for) LOGSA stylesheet related issue, that PTC/Arbortext tech support would be unlikely to help, yes? no?
Thanks for the help all.
Regards,
Bob W
Bristol RI