Herbie wrote:
>  Evidently, the non-function of Apple's constant "kTXNRichTextFormatData"
>  is annoying but isn't your styled text available as a file anyway? Why
>  do you have to stick with old-fashioned resources in the resource fork?
>  Why not use a bundled application in which your text would be accessible
>  as rtf by -- I guess -- one of the above mentioned calls?

I am still using FB4 for my project development work and initial bug
fixes, and I make the code FBtoC compatible for eventual release. I am
just so used to the error presentation in FB4, and also to the slightly
shorter compile times (about 1.4 Seconds in FB4 for my current project,
vs 16 Seconds for the first time in FB5.1.5 and about 3 Seconds after
that). I do think that FBtoC is GREAT, and it is the future of FB -
thanks to all who have worked on it.  So maybe I'm just a an old fogey
who is a little too resistant to change, but for now I still like to be
as compatible with FB4 as I can. And I have a client (with several major
programs) who is not willing to spend the money to convert these to
FBtoC.

>  As far as I know, a bundled application may even consist of a mix of
>  old-fashioned resources in the resource fork and bundled resources, but
>  I may be wrong.

You are correct.

>  Hope to learn more

Usually a good thing

Best.

Walter

-- 

===========================================
Walter Lenk    Cambridge Ma    617-547-7781
===========================================