Okay, so let’s debug this then together into several steps
Step 1
Create a new text template in a company, and use the exact same result tags but nothing more. So something like:
{{ period.reconciliations.recon_a.results.var_a }}
{{ period.reconciliations.recon_b.results.var_b }}
{{ period.reconciliations.recon_c.results.var_c }}
and print that in a PDF export.
Is the issue still there? Go to step 3
Is the issue not there anymore? Go to step 2
Step 2
The test proved it’s not related to the specific result tags, so that leaves one option only: it is related to other coding in that text template.
For example: if some other text is being coded with <font size="8.5">{{ some_var }}</font>
in that same text template, it can already cause the issue you are experiencing.
It’s important to note that the HTML tags (font size) cannot be used anywhere, so if this indeed a text that gathers a lot of other information, you need to be sure nowhere those HTML tag are being used. Not even in a result tag if that result tag holds a capture with that font size being used in it.
Use {::font size="l"}Some text{:/font}
instead
So check all related templates, and the use of font sizes
Step 3
So it is related to one of these result tags. Again, we need to debug those results and how they are being made.
Obviously, I don’t have any insight into that, so what you’ll need to do, is investigate the reconciliations where those results are made, and look if those HTML tags are part of the reconciliation (even if they are related to text you don’t use in your text template).
Again, I’ve seen this behaviour before with font sizes not being respected in export and it was related to the use of HTML tags, which we don’t support.
Only these are supported:
Could you give this a try @svalais ? This is extra work I know, but that’s debugging I’m afraid
It cannot be related to detail text of a style either, as that impacts the export of details of account and reconciliation templates only, so that’s already we can cross off our list