Skip to content

Reimplement type3 font rendering for the Arthur backend

The new implementation uses beginType3Char/endType3Char. It is much simpler than the previous implementation. However, it does not do any caching, and it may therefore be slower. Unfortunately I do not have the means to do thorough benchmarking, and I am asking for help.

This patch does not remove the old implementation. You can switch between the two by setting the return value of the method interpretType3Chars (true: new implementation, false: old implementation).

This is the patch originally posted in #206

Merge request reports