We are currently using GroupDocs.Conversion version 26.1 to convert docx (and many other types) to PDF files. An issue we’re encountering is that if a symbol on the source document does not exist in a font in the executing (Linux docker container) environment, the output PDF renders that symbol as a box.
When searching this forum, the common refrain seems to be that the environment needs to have the fonts for the source document installed in order to render them properly in the output PDF file.
In our application, we expect to be ingesting document files with an unknown combination of fonts and symbols. It is my current understanding that when running conversion, it will try to do Font replacement based on the WordProcessingLoadOptions properties, and the fonts available on the environment that the code is executing on.
Is there any mechanism for which we can be notified of a warning or failure during font replacement during conversion when these symbols are failing to find a match? Or do you have any guidance or recommendations on handling files of varied fonts and symbols?
We’ve currently tried to add a trace logger to the created ConverterSettings, but there did not seem to be any feedback with regards to fonts in the output.