Tagsets.rtf page breaking algorithm?

[2seconds]

First of all can the 'automated' pagination be disabled somehow if using tagsets.rtf? The reason for this is that I want full control over the pagination, since the automation is just not working. However even I have pagebreaks defined in the data and in proc report I have page break after page, then the tagsets.rtf still breaks some pages insanely stupidly. There also does not seem to have any logic, only thing I could figure out is that it somehow calculates the average number of rows per page and then breaks the page even if it would fit the page, but has just more rows than others?

Also it seems that tagsets.rtf does not follow the orders defined in proc reports define statement (just=left for example has no effect). 

I still would like to use tagsets over the normal rtf since in traditional ods rtf generates multiple redundant rows taking a lot of space from the output (which is even more fun is that those paragraphs has font times new roman 12pt, even all the fonts in every template has been defined to be Courier New (monospace)).

It is extremely frustrating that it is not possible to generate desired outputs, and just disable all the 'automation' off.

Also modifying the tagsets itself is as fun as taking cyanide but I guess that would be the only way?

[SASJedi]

Have you tried the STARTPAGE=NO option (see RTF ODS Docs) Also, if you post sample code illustrating your problem - preferably using a SASHELP dataset - it's easier to help. Something like this would work:

ods rtf file="test.rtf" STARTPAGE= BYGROUP;
proc print data=sashelp.cars;
	by Make;
	var Model MSRP MPG:; 
run;
ods rtf close;