Dirk Cleenwerck wrote: > From what I understood, the RTF Import feature only supports the > features of the StyledText Class. > [New] [All] StyledText: A new read/write property "RTFData as String" > which allows cross-platform RTF generation and parsing. > The > parser only supports features found in the StyledText > class. > (Feedback ID: ggtkegot) > > So what I think is happening is that when you use a StyledText > Field and > export that to RTF, you should not have any problems loading the RTF > file back into the StyledText field. What will most likely not work is > loading a random RTF File. For that you need a full RTF parser, and > from > what I gather from the release notes, this is not a full parser, > but a > subset. If anyone has ever looked at the full specs for RTF, it is > easy > to understand why Real started with a subset. Maybe they'll expand > on it > in the future.
This is incorrect reasoning. I have written a full fledged RTF parser for the FTC and the one thing you HAVE to do is ignore tags that are not used by your application, otherwise you will see crashing and freezing like the RB implementation does. This is a potential land mine waiting for unsuspecting developers who will release applications not knowing there is a potential for a crash. Only supporting the StyledText attributes means it should ignore all the other features of RTF and the RB implementation does not do that. Like I said previously, if you don't know who produced the RTF data, then don't input it into the edit field unless you like handling support calls from your customers. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
