To solve this, we would pretty much have to totally reformat the design synopsis. We're running up against some basic limitations of our rich text representation. Even if we fixed it to work with larger designs, you would still be limited to a single output format. That's why I would prefer people use customized XSL with the Tools / DXL Utilities / Transformer menu to generate reports that contain design information in the format that is most useful to them.
If some XSL-savvy person would contribute a sample XSL file that displayed all the design information, I would make it my mission to get it added to the product.

Andre, I understand that it might be a challenge to fix synopsis. And I also agree with the DXL/XSLT approach and its versatility. I have even written my own "design extractor" which generates HTML and XML based upon DXL output. I mainly use this as a target for my desktop search tool, which at the time being is X1 (www.x1.com). The idea is that the excellent search capabilities (heavy boolean and proximity searches) in X1 and similar tools, make it easier to search for all my Notes related code directly from the desktop.
However, since the synopsis is built right into the Designer, and because of its excellent speed, I would like to see that synopsis overcame this limitation. That would make many tools redundant, even my own :-)

@Andre
surely it is just a matter of trading off the size of the paragraphs against the number of paragraphs? At the moment it looks like every line is a new paragraph. Maybe just use a full paragraph break at the end of every design element? This will break the first-line indent that is being used at the moment, but a bunch of tab settings would give the equivalent layout.

Surely the simple answer is to create a document in the Synopsis database per design element ... or has TeamStudio Analyser got a patent on this idea?