SN Printing Under WIN/NT

[Syd Polk]

At 04:26 PM 10/4/00 -0400, Berek wrote:
>Lot's of problems printing hierarchy and cross reference charts under NT. I
>have SN installed on 1/2 dozen PC's. Some use Postscript drivers, others
>PCL, some use both. All have same results printing on 1/2 dozen networked
>printers. Basically, printing is garbled: letters, symbols, and lines
>overlaying each other. Have to resort to doing NT alt-print screen and
>pasting into MS Word, then printing from Word.

The real problem is that there are no font preferences that just apply to 
printing, and the fonts for screen and printing don't match very well. We 
need to do some work at some point cleaning this up, as well as an overall 
preferences rewrite.


>In Class view, C++ class members that are "private" have symbol (transparent
>diamond) for "public". Private members should have no symbol at all. Both
>public and private have the public symbol.
>
>I'm concerned about comments made by SN Development (Syd Polk?) about
>priority given to Perl parser. I know of more than 1/2 dozen companies in my
>area that have been forced to scale back use of SN because of many problems
>with C++ parser: 3Com, Lucent, Cienna, Concord Communications, Broadband
>Access Systems, Cisco, Fidelity... Unless C++ parsing bugs are fixed, SN
>cannot be relied upon as a development tool. We desparately need accurate
>cross references. Those of us that us SN are forced to fall back on grep's.
>Please review your priorities.

C++ parser is a high priority; we use it internally.

Thanks for your feedback; it really is appreciated.

Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.