Document Templates Clause Samples
The Document Templates clause establishes the use of standardized forms or templates for creating documents related to the agreement. It typically specifies which templates must be used, how they are accessed, and any requirements for their completion or modification. By mandating consistent formats, this clause ensures uniformity, reduces errors, and streamlines the preparation and review of documents, ultimately promoting efficiency and clarity in contractual processes.
Document Templates. As with style sheets, you can choose to make use of a template provided by rinohtype and optionally customize it or you can create a custom template from scratch. This section discusses how you can configure an existing template. See Chapter 6 on how to create a custom template.
Document Templates. When it is not possible to achieve a particular document style using one of the existing templates and a custom template configuration, you can create a new template. A new template is programmed in Python and therefor it is required that you are familiar with Python, or at least with general object-oriented programming.
Document Templates. All document templates can be found on the management website In all document templates, the Author is the lead beneficiary responsible for the document delivery. The Author is a person only for publications The following templates are available to produce any document: For official correspondence: A official paper letter (Word format): only on request to the PMT For general purposes: General Purpose Document (Word format) Presentation Template (Power Point format) For meetings: Meeting Agenda (Word format) Meeting Minutes (Word format) General Assembly Evaluation (Word format) For reporting: Deliverable Template (Word format) For financial follow-up: the following templates will be completed by each beneficiary Costs per Work Package (Excel format) Use of resources (Word format) If needed, this list could be updated during the Project life.
Document Templates. Client will provide list of document templates, including samples and specifications. • Client and JTI will configure the document templates. • Client will test configuration meets the requirements and report issues where the configuration does not meet the requirements within 15 workdays. If no issues are reported within 15 days, then the system configuration will be deemed to be accepted. • Client and JTI will fix any issues and the Client will test again. • There will be a maximum of 3 iterations for testing.
Document Templates. In order to achieve uniformity in the presentation of colMOOC deliverables, internal documents and presentations, the Coordination team has provided separate templates for each type of document. The following templates are available in the project wiki: (please not than in order to have access to the files you have to login first to the project wiki) • Document deliverables template in MS Word (docx file) • Presentations template in MS Powerpoint (.pptx) • Meeting minutes template in MS Word (.docx) • Review Form template in MS Word (.docx)
Document Templates. As with style sheets, you can choose to make use of a template provided by rinohtype and optionally customize it or you can create a custom template from scratch. This section discusses how you can configure an existing template. See Chapter 6 on how to create a custom template.
4.2.1 Configuring a Template rinohtype provides a number of standard_templates. These can be customized by means of a template configuration file; a plain text file in the INI1 format with the .rtt extension. Here is an example configuration for the article template: name = my article configuration template = article parts = title ;front_matter contents stylesheet = sphinx_base14 language = fr abstract_location = title contents = 'Contents' caution = 'Careful!' warning = 'Please be warned' paper_size = A5 page_number_format = lowercase roman end_at_page = left page_number_format = number top_margin = 2cm The TEMPLATE_CONFIGURATION sections collects global template options. Set name to provide a short label for your template configuration. template identifies the document template to configure. All document templates consist of a number of document parts. The Article template defines three parts: title, front_matter and contents. The order of these parts can be changed (although that makes little sense for the article template), and individual parts can optionally be hidden by setting the parts configuration option. The configuration above hides the front matter part (commented out using a semicolon), for example. The template configuration also specifies which style sheet is used for styling document elements. The DocumentTemplate.stylesheet option takes the name of an installed style sheet (see rinoh --list-stylesheets) or the filename of a stylesheet file (.rts). The language option sets the default language for the document. It determines which language is used for standard document strings such as section and admonition titles. The Article template defines two custom template options. The abstract_location option determines where the (optional) article abstract is placed, on the title page or in the front matter part. table_of_contents allows hiding the table of contents section. Empty document parts will not be included in the document. When the table of contents section is suppressed and there is no abstract in the input document or abstract_location is set to title, the front matter document part will not appear in the PDF. The standard document strings configured by the language option des...
Document Templates. Frequently Asked Questions Below is the start of a list of commonly encountered problems and solutions to them. You can also find answers to usage questions on rinohtype on StackOverflow. Old versions of some PDF viewers do not support the way rinohtype embeds fonts in a PDF (see issue 2). PDF viewers that are known to be affected are: • pre-37.0 Firefox’s built-in PDF viewer (pdf.js) • pre-0.41 poppler-based applications such as Evince 32 Chapter 7 Frequently Asked Questions Contributing Thank you for considering contributing to rinohtype! This document contains some general information with respect to contributions. Please refer to DEVELOPING.rst for specific informa- tion on running tests etc.
8.1 Contributor License Agreement Please send your contributions by creating a pull request on GitHub. You will be asked to agree to the contributor license agreement. Why, you might ask? In the past, I had plans to sell a commercial version of rinohtype. This version would basically be the same as the open source version, but with the addition of a closed-source frontend for the DITA format. While I’m no longer actively pursuing these plans at this point, I would like to keep this option open. In combination with the Affero GPL, the CLA allows me to include contributions by others in this commercial version while preventing others from releasing commercial closed-source versions of rinohtype. Additionally, the CLA protects the project from legal risks. Since I’m no legal expert, I adapted the contributor license agreement from Project Harmony. You can find a quick summary and a detailed walkthrough of the license in the guide.
Document Templates. Frequently Asked Questions Below is the start of a list of commonly encountered problems and solutions to them. You can also find answers to usage questions on rinohtype on StackOverflow. Old versions of some PDF viewers do not support the way rinohtype embeds fonts in a PDF (see issue 2). PDF viewers that are known to be affected are: • pre-37.0 Firefox’s built-in PDF viewer (pdf.js) • pre-0.41 poppler-based applications such as Evince 32 Chapter 7 Frequently Asked Questions Contributing Thank you for considering contributing to rinohtype! This document contains some general information with respect to contributions. Please refer to DEVELOPING.rst for specific informa- tion on running tests etc.
Document Templates. JTI will convert document templates as a part of the data conversion process using JTI’s conversion tool. • Client will test and report issues where the configuration of the new document templates does not match the existing document templates within 15 workdays. If no issues are reported within 15 days, then the system configuration will be deemed to be accepted. • Client and JTI will fix any issues and the Client will test again. • There will be a maximum of 3 iterations for testing.