AU

I was able to reproduce it on one system, but on another it works as expected. In the following env everything works quickly: ``` # Name Version Build Channel alabaster...

It indeed had 0.4. Upgrading to 0.5.1 solved the issue.

Then it is likely an ABI compatibility issue. conda-forge avoids this by having a well defined toolchain. That is not the case for pip, everyone can choose a different compiler/flags.

You could try compiling all packages yourself. I don't think this is a gmsh or ocp packaging bug.

@openvmp thanks, what is the background of this fix? How can I reproduce the issue and can a test be added?

Could you share this model as a `.brep` file?

I agree, approximate equality check sounds like a good solution.

@jmwright what is the conclusion actually? You wrote above that specifying the font path does not solve the issue, but your PR does specify a path. Is the PR using...

Indeed, you are right.

For OCP the script is here: https://github.com/CadQuery/OCP/blob/master/dump_symbols.py . For a general case you'd need to write your own.