Can you explain a full example? imo if you want to resolve symlinks this should be done on the path to the fontforge binary itself instead of the folder containing fontforge (like there is a potential difference resolving /a/b/c vs /a/b/c/fontforge).

Can you explain a full example? imo if you want to resolve symlinks this should be done on the path to the fontforge binary itself instead of the folder containing fontforge (like there is a potential difference resolving /a/b/c vs /a/b/c/fontforge).

This could happen in many Linux distro where /bin/ is a symlink to /usr/bin. The fontforge will look for resource files in /share in this case, which is incorrect. This fix will hopefully resolve such issue.

Regarding your concern with the path resolution, I will change my patch to resolve the path to the binary.

Which distro is this? Sounds more like a problem that if you symlink /bin to /usr/bin, then so too should /share to /usr/share

@liushuyu, just pinging regarding what @jtanx said.