Re: NSTextStorage (actually, RTF) problem, with patch

[Nicola Pero]

Hi Jeff,

thanks - good spot! :-) - I applied your patch - well with some changes
around because of a pitfall - if the caller is NSAttributedString (or a
non-mutable subclass), then the RTF consumer need to create a
NSMutableAttributedString (mutable so that it can write things to it),
then copy it into an NSAttributedString just before returning it.

I tested it quickly - but not extensively - so please let me know if I
broke something in the patch in the process. :-)

Thanks for contributing! :-)

> Because of the class cluster architecture, RTF consumers need to vary
> their return type based on what class is asking for data. Attached is a
> (trivial, really) patch implementing this.
> 
> I left the current methods defined in the protocol, for binary
> compatibility. This may or may not be important, so I leave that up to
> you. :)
> 
> This solves most of TextEdit's problems. There's still another one
> somewhere else in the text network, which surfaces when an app has to
> create the layout manager itself.