Thanks @Aklapper for renaming the task and adding it to a project!

Found this thread (luckily its cached as the original doesn't seem to exist, so I've archived it as well..) — of note is:

For anyone else who comes across this, I ended up figuring out that calling rsvg directly would load fonts from the local home directory. Example: /var/www/.fonts/truetype/google/anton.tff would be automatically loaded. Then you can run exec("rsvg-convert $svgFile > $pngFile");. You have to manually download the fonts from Google, but at least it works. On Heroku I was able to just add rsvg-convert to the application and call that version. It did not need any other libraries to be loaded.

Are the missing fonts due to them not being in the Toolforge php7.4 image? Because perhaps the fix here is to make sure that that image matches whatever Wikimedia production has (i.e. what is able to be rendered by rsvg in prod)?

Hi @bd808 ! I'm currently trying to fix a font issue with our SVG Translate tool and I came across a patch related to this that was created a couple of years ago. What is the best way to address this font issue? The tool is not currently using grid, should we run the service using the grid or should we submit a patch so that the image include the needed fonts? Your help is greatly appreciated.

In T310435#8288654, @HMonroy wrote:

Hi @bd808 ! I'm currently trying to fix a font issue with our SVG Translate tool and I came across a patch related to this that was created a couple of years ago. What is the best way to address this font issue? The tool is not currently using grid, should we run the service using the grid or should we submit a patch so that the image include the needed fonts? Your help is greatly appreciated.

This is basically the same issue as T213669: [BUG] Fonts missing for some languages on SVG Translate tool was when this same tool tried to use Kubernetes before. @Samwilson had proposed a patch to add the missing fonts to the php7.2 image, and I eventually convinced him to just revert to running the tool on the grid engine instead.

Time passes, and people can learn & grow. ;) I would like to test to see how much bigger the php7.4 image is with the same font packages installed as are installed on the grid engine, but I think that we can afford to add the fonts to support this tool.

If a quick fix is needed, I think reverting to running on the grid engine is your best bet. That will make @komla and @nskaggs sad though so if you can give me a day I'll try to unblock you with php7.4 on the Kubernetes cluster.

Change 838939 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):

[operations/docker-images/toollabs-images@master] php74: add many TTF fonts

https://gerrit.wikimedia.org/r/838939

Change 838939 merged by jenkins-bot:

[operations/docker-images/toollabs-images@master] php74: add many TTF fonts

https://gerrit.wikimedia.org/r/838939

Mentioned in SAL (#wikimedia-cloud) [2022-10-06T00:04:21Z] <bd808> Building new php74-sssd-base & web images (T310435)

Mentioned in SAL (#wikimedia-cloud) [2022-10-06T00:14:10Z] <wm-bot> <root> Restart to pick up new php7.4 container with added fonts (T310435)

Thanks @bd808!

Follow-up for this: T320224

This issue was happening in the Japanese text too. This fix helps us so much. Thank you!