I am trying to add a place of signature at the bottom of my documents, one place for my company and another for the client.
I tried adding the entity “&emsp” to generate mutiple spaces between texts on the same line of a custom field title, but when I generate a PDF, the white space between them is gone. See the screen shot below:
Is there a way to force the PDF document to keep the white space between them? if not, is there a way to insert two custom themes on the same line separated by white space?
hey Tut, thank you for your quick response and help.
If I can ask you another thing, which I could not on the forums.
In the custom field, I underline the text as seen below in the screenshot. The underlying is showed with the print option but when I generate a PDF the text will show normal without underlying.
Is there a way to stop the PDF generator from rendering out added style? It seems that the PDF generator ignored a lot of added styles, in both custom field or the theme itself.
I am sorry If my question sounded wrong and I asked for coding instructions. Let me rephrase my question Please.
When I use the internal-PDF generator of the software, the generator ignores style attributes that I have added. The documents will be generated without certain styles. How can I force the PDF-generator to keep the styles that I have added? The generator appear to only include styles added in theme table, but every style outside the Table is ignored or overlooked.
That is not the problem. The internal PDF generator simply doesn’t process the underscore <u> nor the italic <i> tag, even when inserted as style such as text-decoration: underline. @lubos, can the PDF generator’s behaviour be modified?
@Taha_El_Zein you can use the print button and print as PDF. And to answer your question in your first post: search the forum for Signature.
Hey Mark, thanks for your reply, you addressed my issue well.
I am trying to keep print as PDF a last resort since it does not repeat the table head on extra pages.
I am asking for this one as I have several related issues that can be fixed all together with this.
You simply cannot. The internal pdf generator only use a subset of HTML. So if you use unsupported tags you will see them on the screen thanks to your browser rendering engine but you will get a different output if you create directly pdf. Since I don’t think that @lubos will ever change the pdf renderer, the only solution is to print to PDF as already suggested.
