This contains runnable examples for our commercial PDF library, ReportLab PLUS. It should help you get up and running and creating your own PDF document layouts quickly.
We strongly suggest you start by skimming through the RML User Guide:
https://www.reportlab.com/software/documentation/
Current contents: - Fundfacts Tutorial - Graphic Card Tutorial - Invoice Tutorial - Long Document Tutorial - Retrofitzero Tutorial - Product Catalogue Tutorial - Error Handling - RML test suite
Install a virtual environment run pip install -r requirements
Run:
$ cd rml_tests && rml2pdf *.rml
and look at the .pdf files and their corresponding .rml files within the /rml folder.
We include a full copy of our own internal RML test suite. These files can also be seen, with their output, on our own web site:
https://docs.reportlab.com/rmlsamples/
You should be able to convert any of them with the installed 'rml2pdf' command. For example:
$ rml2pdf test_001_hello.rml test_001_hello.pdf
Preppy is ReportLab's templating system. It has been in continuous production use since 2000.
It was released as open source code but never evangelized. We are putting it out on PyPI now because many of our solutions depend on it, and this makes it a lot easier to install (e.g. with a pip requirements file).
Preppy is a single Python module which should be placed directly on the path (i.e. you access it with 'import preppy'). The setup script does this, but it's just as effective to grab it from the repo and drop it into your project.
Preppy aims to be absolutely minimal. You embed Python expressions and control structures in your template. It compiles the template into a .pyc file. A preppy template is exactly equivalent to a Python function which accepts parameters and returns text output. We don't both with include functions, block nesting, filters or any other fancy stuff, because we already have a perfectly good language to do that in.
Preppy is just Python, so you get proper Python tracebacks, with the original line number in the .prep file; you can happily debug through calls to python, preppy, python and more preppy.
Report Markup LanguageTM (RML) is ReportLab's direct-to-PDF document formatting solution. We defined a Markup Language which describes the exact appearance of a printed document; and a software component, RML2PDF, which converts RML into PDF files. Report Markup Language describes the precise layout of a printed document, and RML2PDF converts this to a finished document in one step.
A RML file will in most cases contain the following three sections: a template, a stylesheet and a story.
The template tells rml2pdf what should be on the page: headers, footers, any graphic elements you use as a background. It is the section where the layout of a document is set out - both for the whole document and for individual pages within it.
The stylesheet is where the styles for a document are set. This tells the parser what fonts to use for paragraphs and paragraph headers, how to format tables and other things of that nature.
The story is where the "meat" of the document is. Just like in a newspaper, the story is the bit you want people to read, as opposed to design elements or page markup. As such, this is where headers, paragraphs and the actual text is contained.
<!DOCTYPE document SYSTEM "rml.dtd"> <document filename="example_2.pdf">
- <template>
- <pageTemplate id="main">
- <frame id="first" x1="72" y1="72" width="451" height="698"/>
</pageTemplate>
- </template>
<stylesheet>
- <paraStyle name="h1"
- fontName="Courier-Bold" fontSize="12" spaceBefore="0.5 cm" />
</stylesheet> <!-- The story starts below this comment --> <story>
- <para style="h1">
- This is the "story". This is the part of the RML document where your text is placed.
</para> <para>
It should be enclosed in "para" and "/para" tags to turn it into
- paragraphs.
</para>
</story>
</document>
RML allows you to use comments in the RML code. These are not displayed in the output PDF file. Just like in HTML, they start with a "<!--" and are terminated with a "-->". Unlike other tags, comments cannot be nested. In fact, you can't even have the characters "--" inside the <!-- --> section.
<template> allows you to set options for the whole document. The <pageTemplate> tag allows you to set options for individual pages. You can have more than one<pageTemplate> inside the template section. This allows you to have different pageTemplates for each page that requires a different structure. For example, the title page of a report could have a number of graphics on it while the rest of the pages are more text-orientated.
Just like in a word processor, RML allows you to define a stylesheet at the start of your document, and then apply it to paragraphs later on. This means that you can define a complicated mixture of settings that you want to apply to paragraphs, only define it in one place, and refer to it with a simple name at the start of each paragraph rather than having to type or cut-and-paste large blocks of text over and over for each paragraph.
For more info, please take a look at the official documentation