
Some of those attributes are, but may not be limited to, the use of: The first conversion from RTF to HTML can very easily introduce formatting problems if there are any attributes contained within the RTF document that don’t convert to HTML well. To be blunt, let’s just say the process described above, that of converting documents from RTF to HTML, signing them, then converting them to PDF, is a less than perfect process.

Why are documents poorly formatted once signed, or not signed at all due to the formatting problems?
#Rich text file pdf#
This PDF document is the one this is permanently store, and distributed electronically to all the attorneys of record on the case.
#Rich text file software#
In doing so, the software performs another conversion of the document from HTML to a final PDF. The software then processes the document to record it on the record and prepare for permanent storage in the Court’s document management system. Once the clerk or judge has reviewed and approved your document, they use this software to place a signature stamp on the document. What the clerk or judge is viewing when they are reviewing your document is your RTF document already converted to HTML. rtf document to the clerk or judge, and provide them the tools within the browser they need to possibly edit, then sign the document, the Court must first convert the document from Rich Text Format to an HTML format. This software is browser based (viewed using a web browser like Internet Explorer, Firefox, Chrome) and allows the clerk or judge to view your document from within the browser. The Court has developed its own software for use by court clerks and judges for the purpose of reviewing documents requiring their signature, signing those documents, and filing or docketing them on the case. How are documents submitted as Rich Text Format processed by the Court? The Court does not want to require attorneys to use Word, or WordPerfect … so by requiring documents be submitted as Rich Text Format the Court has allowed attorneys to continue to use whatever word processing software they are most comfortable with.

rtf, it doesn’t require that attorney to use a specific word processing software. By requiring attorneys to submit these documents in. Rich Text Format documents are a universal file format that can be generated or viewed by most any word processing platform (Word, WordPerfect, WordPad, NotePad, OpenOffice, etc…). Why Rich Text Format (.rtf), and not Word (.doc /. In addition, upon reviewing and approving these documents, the Court is able to place a signature stamp on the RTF document using their judicial signature software. If these documents were submitted as PDF, then they would not have any option to edit them. The reason the Court requires they be submitted as Rich Text Formatted (.rtf) documents is so that they may retain the ability to edit these documents, prior to signing, within their judicial review and signature software.

Some sample documents that fit this description are things such as: The Court requires Rich Text Format (.rtf) typically for those documents that the court clerk or Judge are required to sign and process. Why does the Court require Rich Text Format (.rtf) documents for some documents filed?
#Rich text file how to#
Before we describe these issues, and how to correct them, let us provide some understanding of why the Court requires Rich Text Format documents and how these formatting issues arise. The Utah Courts, however, don’t work with your Rich Text Format documents like most would, and therefore have introduced formatting issues and require the filer to correct. Let us start by saying, that as the filer you are likely creating Rich Text Format documents that to most of the world are perfectly acceptable documents easily read with any word processing software. By far the most common support issue we assist with is helping attorneys and staff format their documents required to be submitted in Rich Text Format (.rtf) in a way that the Court’s system can process smoothly.
