> One problem with RTF is MS has different versions of the > specification, generally released when a new version of MSO comes out. > If your software > does not read the newer versions, which I believe is the default for > the latest MSO version you may get garbled importing on occasion. I truly and completely sympathize with your plight because I myself am NOT a [C/Java] Application Developer. When I have a problem with an application, I am at the mercy of the developer(s) to correctly address the issue.
GOOD NEWS for every wana-be RTF User (and there are more than you think)! Miklos Vajna claims to have the agenda to correct Libre Office's implementation of RTF: For (1) simple but important example of an RTF issue that just should have NEVER been: see FreeDesktop Bugzilla – Bug 38786 \nofpages \chpgn ignored and rejected: treated as step children. This example (bug 38786) is the basis the following quote (Sean Burke in RTF Pocket Guide): "For no really good reason, support for these RTF character sets is perfect in some word processors, almost perfect in others..., and shoddy in others..." When a software application [claims to have RTF functionality] and has problems read or writing RTF files (or crashes), the fault is with the reader/writer (hence application developer(s)) and (NOT / NEVER) the RTF Specification (see long quote below). I do NOT expected developers to be perfect and never make mistakes: that's why we have Bugzilla and not EnhanceZilla. Tracey *** Here's a long RTF Specification quote (from June 1992): Destinations added after the 1987 RTF Specification may be preceded by the control symbol \* (backslash asterisk). This control symbol identifies destinations whose related text should be ignored if the RTF reader does not recognize the destination control word. RTF writers should follow the convention of using this control symbol when adding new destinations or groups. Destinations whose related text should be inserted into the document even if the RTF reader does not recognize the destination should not use \*. Jay Lozier [via Document Foundation Mail Archive] wrote: > Hi On Wed, 2011-06-29 at 06:33 -0700, tracey002 wrote: > > > Johnny Rosenberg wrote: > > Since then I always make sure no RTF > files comes near me ever. > > I have all due respect for your opinion > and choice and I am glad you have > the option to do that. > > I had > never thought of saving all documents in RTF (maybe not a bad idea), > > but I do find RTF very useful for the purpose for which it was > designed: > portability. > I have used RTF to send Documents and > Data/Reports to recipients with > diverse Office-Applications that did > NOT have a choice with the > Office-Application they were using (so I > have successfully used RTF for > portability). > > > Sean Burke in RTF > Pocket Guide wrote: > > For no really good reason, support for these > RTF character sets is > > perfiect in some word processors, almost > perfect in others..., and shoddy > > in others... > > The capability > of applications that state or imply RTF functionality is not > a > reflection of RTF, but on the competence (hence professionalism) of > the > developers that implement the Open/Import and Save-As/Export > routines. > > This is true of *all* software: that includes the > Microsoft Word Veiwer 2003 > that has problems correctly displaying > the Word2002RTFSpec.doc. > > Just FYI, Tracey > I normally do NOT use > a screw driver as a substitute for a hammer, but I > have used a heavy > duty screw driver to pound the lid back on a paint can. > I am not > upset that screwdrivers are not hammers. > > > -- > View this message > in context: > http://nabble.documentfoundation.org/RTF-support-tp3114703p3121621.html > > Sent from the Users mailing list archive at Nabble.com. > > One problem with RTF is MS has different versions of the > specification, generally released when a new version of MSO comes out. > If your software does not read the newer versions, which I believe is > the default for the latest MSO version you may get garbled importing > on occasion. -- Jay Lozier [hidden email] > </user/SendEmail.jtp?type=node&node=3126067&i=0> -- Unsubscribe > instructions: E-mail to [hidden email] > </user/SendEmail.jtp?type=node&node=3126067&i=1> In case of problems > unsubscribing, write to [hidden email] > </user/SendEmail.jtp?type=node&node=3126067&i=2> Posting guidelines + > more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/global/users/ > All messages sent to this list will be publicly archived and cannot be > deleted > ------------------------------------------------------------------------ > If you reply to this email, your message will be added to the > discussion below: > http://nabble.documentfoundation.org/RTF-support-tp3114703p3126067.html > To unsubscribe from RTF support, click here > <http://nabble.documentfoundation.org/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3114703&code=d3BpaXNAZ3RlLm5ldHwzMTE0NzAzfDg1NDMxMTYz>. > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.901 / Virus Database: 271.1.1/3734 - Release Date: 06/29/11 > 13:34:00 > > No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.901 / Virus Database: 271.1.1/3734 - Release Date: 06/29/11 13:34:00 -- View this message in context: http://nabble.documentfoundation.org/RTF-support-tp3114703p3126799.html Sent from the Users mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to users+h...@global.libreoffice.org In case of problems unsubscribing, write to postmas...@documentfoundation.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
