Support adding custom fonts to DW2PDF including the extra configuration needed for mpdf library

[nd1976]

How Can I change the font family to use the CI one and not the created "DejaVu Sans Condensed"

I tried it with a template in the tpl folder and I wrote in the Fontface in the CSS file. But it does not change anything.

[Klap-in]

Extra fonts should be also configured in the mpdf library, this should be done in the DokuPDF.class.php or action.php.
See https://mpdf.github.io/fonts-languages/fonts-in-mpdf-7-x.html

Proposals welcome as pull request.

[Klap-in]

Similar as #402

[Klap-in]

Example for the fontawesome font: https://stackoverflow.com/a/58702825/1043588

I'm wondering what is practical manner to implement. Add a default font folder for extra fonts to the dw2pdf folder, and let in the config add the names of the fonts to configure? Probably just looping over the names is not nuanced enough.
Define a e.g. font.php file in the pdf-template folder that add the right fonts? With enough examples in the manual?

[mstumberger]

@Klap-in thanks for the tip, I'we tried this but got an arror saying that font is not supported...
I used this font:
https://www.cdnpkg.com/line-awesome/file/fa-solid-900.ttf/

[Klap-in]

I have no time to help you debugging, sorry. Further no suggestions yet.

[LouisOuellet]

Example for the fontawesome font: https://stackoverflow.com/a/58702825/1043588

I'm wondering what is practical manner to implement. Add a default font folder for extra fonts to the dw2pdf folder, and let in the config add the names of the fonts to configure? Probably just looping over the names is not nuanced enough. Define a e.g. font.php file in the pdf-template folder that add the right fonts? With enough examples in the manual?

@Klap-in Any progress on this feature request? I would love to be able to add support for my template's fonts along with bootstrap-icons.

I think setting up a hook to access mPDF prior to the final rendering would be ideal. That way it can be extended in various other ways. mPDF already provide access to FPDI. Ideally a hook for plugins, templates and a hook for the user as well.

If you can provide access to the object it would be ideal.

I worked with mPDF in the past and there are many useful options that are not available through a generic file generation such as dw2pdf. For exemple, mPDF can be extended using SetaSign's FPDI. Licensing can later be added to support signatures, encryptions. Additionally, someone could extend dw2pdf to add support for password protection or write protection. Another could add support for watermarks.

Also I'd suggest something like dw2pdf or mpdf.php for the name of the hook.

[LouisOuellet]

Was reading the existing documentation, there is an existing hook dokuwiki/lib/plugins/dw2pdf/mpdf/config.php. Considering that this files gets overwritten everytime the plugin is updated, I feel like this is not the right approach. Especially for production sites. I think, maybe this would be a good place to create a hook instead to provide access to mpdf configurations.

• dokuwiki/lib/[plugins|tpl]/[name]/dw2pdf/config.php: Hook to access mPDF's configuration.
• dokuwiki/conf/dw2pdf/config.php: Hook to access mPDF's configuration for user customization.

Not sure yet (Still looking into the code and documentations), but if the mPDF object can be accessed from there, then theme fonts could be implemented in there.

[LouisOuellet]

Well, nevermind. It looks like this hook (dokuwiki/lib/plugins/dw2pdf/mpdf/config.php) no longer exist. Tried with a simple file creation to test and tested the password protection in the official documentation.

Also while digging into the plugin's code. I could not find any indication of its existence. Probably got removed in a previous commit.