SSuite Free Office Software

Providers of Safe and Trusted Software with Pure Visual Simplicity™


Why We Only Use The Rich Text Document Format - *.rtf ...

Posted on August 29, 2015 at 9:05 AM

Only use RTF documents from SSuite Office!We only support fully compatible document formats like the RTF ( Rich Text Format - (*.rtf) ) and the Excel spreadsheet document format. The RTF document format is compatible with any operating system (Apple Mac, Linux, and Windows) and office suite, unlike Microsoft's Word document format (docx/xlsx) and OpenOffice's Open document format (odf /odt).

The RTF format was designed from the start to be an exchangeable document format. If opened in a plain text editor you will see that it resembles html. This document format is the most supported and most compatible format to use, no matter what word processor and even operating system you use. And just for your information, most software applications that claim compatibility with Microsoft's docx and xlsx formats, uses a cracked and unlicensed version of these document formats, so they are also not 100% compatible.SSuite Office Software only supports fully compatible document formats like the RTF (Rich Text Document Format) and the Excel spreadsheet document format. The RTF document format is compatible with any operating system (Apple Mac, Linux, and Windows) and office suite. The RTF document format was designed from the start to be an exchangeable document format. If opened in a plain text editor you will see that it resembles html. This document format is the most supported and most compatible format to use, no matter what word processor and even operating system you use. Free SSuite Office Software and Suites.

The RTF format is the only available format that is 100% compatible across all software applications. Office suites and word processors on the other hand that uses and creates closed document formats e.g. docx, xlsx etc, can only open these formats because their developers have paid the exorbitant license fees(in the millions) to read and write Microsoft's proprietary document formats, for example - Star Office and other offspring, which you also have to purchase. (Also needs Java Virtual Machine to run).

Independent office suite developers have to create their own proprietary format, or go with the Open Rich Text Document format. As most people do not know, RTF documents can hold the same contents as any Word document, and is also much smaller in size when being created. It is only the extension and inner record keeping that is different.

I have recently discovered that OpenOffice's Open Document format (*.odf / *.odt) is just rich text dumped inside their own Open Document format wrapper {XML representing RTF data}. So do not get caught out with vendor lock in, not even from the open source community.

So switch today to our excellent free office suites that support true compatible document standards!

Only use RTF documents from SSuite Office!Please read the following articles on why you should be using the Rich Text Document format:

Primary Article     Secondary Article

Article 1        Article 2


Free SSuite Software To Open RTF Document Files...


End this madness and say NO to proprietary document formats...


Free Word Processors from SSuite Office!You may have noticed that there are no docx or xlsx document formats supported in our applications. This is because in order to support any MS Office document format, we require a very expensive license { the million$...} from Microsoft for each format.

The reason for this is that they are all proprietary patented formats. You may ask us this then - "...but what about the other open source office suites that do?...". Well, their document formats are all cracked versions of the original format and are not 100% compatible with the original MS Office document formats.

OpenOffice's own document formats are also not even compatible with other open source document formats of the same type. This is because the open source community never set a fixed technical specification's guide for their own document formats. So their formats odf / odt are also not 100% compatible with software supporting these formats.


If you need to create and exchange MS Word documents(*.doc) as a rule, then there is another way in staying completely compatible with everybody, no matter what software they use. This format is the most compatible document format currently available next to the rich text document format.

Simply save all your documents in MS Word or SSuite WordGraph in the following manner:

Only use RTF documents from SSuite Office!  When you save your documents, use this format...    Word 97-2003 & 6.0/95 - RTF (*.doc).

To simplify this procedure in MS Word, simply go to the "Tools >> Options..." menu item, and under the "Save" tab item, select your default document type as the above mentioned document type. This will ensure that all your documents will stay compatible no matter where you need to use them, either in MS Word or SSuite Office's WordGraph word processor. This procedure may also be used in Word 95 up to Word 2007.


Categories: None

Post a Comment


Oops, you forgot something.


The words you entered did not match the given text. Please try again.

Already a member? Sign In


Reply Online Presence
10:36 PM on September 10, 2015 
Sorry, but nearly all of the content in this blog post is simply not true, and is purely FUD. For starters, RTF is a *PROPRIETARY MICROSOFT* format as well. MS owns RTF. It is not 100% compatible across all software applications. There are a dozen different not-quite-compatible RTF revisions. Next, the docx/xlsx formats, while being "proprietary Microsoft formats" (in the very same way that RTF is a proprietary Microsoft format), are released as recognized international standards, originally as Ecma standard, and later ratified by the International Standards Organization, and can be used by anyone (including yourselves) without paying licensing fees. The other projects which support the docx format don't use "cracked" versions. They use the ECMA standard or the ISO/IEC (International Standards Organization) standard.
Reply SSuite Admin
5:54 AM on September 11, 2015 
Thank you so much for your comments and feedback. I am glad that someone is reading my blog posts.

First of, I did not say that RTF was not a proprietary format, but simply an open format that Microsoft purchased back in the 80's for their own office suites.

They made the technical specifications available to all the major players back then. It only later dawned on them that this openness was a competitive disadvantage.

This is how the document format wars started. When Microsoft created the doc format and later the docx format, which is now being used, it left everyone in the business of office suites out in the cold.

This then also created the clone start-ups whom are doing their best to recreate the document formats for staying compatible with Microsoft, e.g. StarOffice, OpenOffice, LibreOffice etc.

You mentioned that the docx/xlsx specifications have been published as an ISO standard which anyone can download and implement in their software. If this is true, then why did StarOffice and Google go out of their way to purchase licenses from Microsoft, of the documents formats docx, xlsx and ppx, in order to stay more compatible with Microsoft?

This only means that the published specifications are only the most basic of guidelines or that not everything was released. Which brings me to the circumstantial evidence shown by another blog-post that I made, which you may find and read here:

Please read this blog-post carefully, as it describes the complete mess that awaits anyone that tries to use open source software.

This is not my opinion, but the end result of an incomplete ISO spec and the incompetence on the side of open source programmers.
Reply Susan Lane
4:51 PM on May 26, 2017 
I learned here: about .rtf file and I use it to work with them .rtf because it supports all versions of .rtf files and it is very easy to use
Reply shadowking
9:58 AM on June 10, 2017 
Your claims of 100% rtf compatibility between apps / platforms is without merit. In fact the opposite is true. The idea of 'interoperability' (at the time - if such a thing was even conceived) was nothing more than being able to OPEN / VIEW /SAVE *something* and various degrees of lossiness was expected depending on the RTF version / implementation. This WAS much better than typical closed binary formats I'll give it that but no one ever said anything about near-perfect quality or data integrity. This remains valid even today. Try anything beyond simple paragraphs, common fonts, with light mark-up between platforms / apps and you will see.

The whole 'interoperability' thing with rtf is really a one-way street to the MS -WORD app and the MS Windows platform (not the other way). Everything other than Windows apps that use MS formats / infrastructures *by default as native format* usually produce less reliable rtf exports as what is seen on screen won't necessarily be saved to file.

Refer to Jarte website:

"At the heart of Jarte sits the same word processing engine used by Windows' WordPad. ..... The significance of this fact is that Jarte users are secure in the knowledge that Jarte is making use of the same reliable, time tested editing engine used by millions of other Windows users all over the world. If you have tried other alternative word processors and found them to be unstable that may be in part due to their use of unreliable, home grown editing engines."

This is unlike ODF , HTML or other standards that aren't tied to a platform as the advantage is clearly favouring MS-Windows, MS-apps and similar rtf editors like ssuite, jarte, atlantis, polyedit etc as they are dependent on the MS Windows eco-system (although probably can be used on WINE etc..)

Your claim of open-source lock-in is also misleading and bordering FUD. A simple document created with latest openoffice 4.1.3 opens just fine with old version 1.1.5 from 2002 and also ms wordpad. Most odt files render quite alright even in ms-wordpad. That support has been there since 2009, not to mention many 3rd parts app , viewers for all platforms. There can be quirks there are different ODF versions around but even current OO / LO can write the old 1.0/1.1 spec if needed.