Check font extension on both original and canonicalized paths#84
Check font extension on both original and canonicalized paths#84wmedrano wants to merge 1 commit intoRazrFalcon:masterfrom
Conversation
3d08173 to
b630380
Compare
|
Hello. Can you prove an example of what exactly this change does/fixes? Also, this project is currently has no maintainers, so no releases are planned. |
IssueI ran into this when trying to upgrade some uses of resvg within my company. In some test setups, the system uses uuid-like file names and constructs the environment from symlinks. Reproduction
No releasesAck, I can do some manual stuff for my usage of this package. |
|
So the issue is that we always check the file extension? Also, I guess checking the file's magic would be a more correct approach, but I'm not sure how much it would affect performance. |
Checking both paths ensures that symlinks with font extensions are correctly identified even if their targets have non-standard names.
|
Oh, yeah, that's simpler and still fixes my issue. Done. Reading the magic bytes seems like it could be bad for performance on systems with slow IO. |
Checking both paths ensures that symlinks with font extensions are correctly identified even if their targets have non-standard names.