Error while reading pdf file having image and text

Questions
1

I am getting below error while reading pdf files having image and text.

Warning: fetchStandardFontData: failed to fetch file “FoxitSerif.pfb” with “UnknownErrorException: The standard font “baseUrl” parameter must be specified, ensure that the “standardFontDataUrl” API parameter is provided.”.
Warning: fetchStandardFontData: failed to fetch file “FoxitSansItalic.pfb” with “UnknownErrorException: The standard font “baseUrl” parameter must be specified, ensure that the “standardFontDataUrl” API parameter is provided.”.
Warning: fetchStandardFontData: failed to fetch file “FoxitSansBold.pfb” with “UnknownErrorException: The standard font “baseUrl” parameter must be specified, ensure that the “standardFontDataUrl” API parameter is provided.”.
Warning: fetchStandardFontData: failed to fetch file “FoxitSansBoldItalic.pfb” with “UnknownErrorException: The standard font “baseUrl” parameter must be specified, ensure that the “standardFontDataUrl” API parameter is provided.”.
Warning: fetchStandardFontData: failed to fetch file “FoxitSans.pfb” with “UnknownErrorException: The standard font “baseUrl” parameter must be specified, ensure that the “standardFontDataUrl” API parameter is provided.”.
Warning: TT: undefined function: 32

Information on your n8n setup

  • n8n version: 1.83
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: mac os
2

Where does that error occur in your workflow tho? Kinda weird, its indicating a failure because of no fonts found? Not sure if I have enough information to assist. Anything else you could provide? Screenshots?

Actually maybe the setup is right, and the issue is the PDF is using custom fonts, that you may need to install on the n8n instance? I am not confident of that either, as to my knowledge PDFs don’t render fonts, its just drawn elements and the elements are tied to characters “behind the scenes” if there was character mapping/OCR done.

3

Since I’m running n8n in a Docker container, these warnings appeared in the terminal. The PDF contains a textual image—could that be causing the issue? If so, how can this be resolved?

4

In the terminal? Of chrome/browser console? Or of the host server console/docker output?

Is there an actual error in the workflow itself that is occurring, preventing the flow from completing? Could you show that?

5

The Warning is from Docker console output.
No, there is no error inthe workflow or UI.

6

So the workflow fails and the errors are in the docker output? Or the workflow works and there are errors? If it works, they should be able to be ignored.

7

The workflow is working as I have added one more step to convert the pdf to image and extract data from the image using vision models.

1 Like
8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.