FONT: eliminate hyphen INFILEPs for font lookup #2405
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
\FINDFONTFILE does its own directory searching, avoiding the hyphen-processing of FINDFILE, as discussed in #2404 .
Looking up a non-existent display font with 2 directories and 2 extensions does 8 INFILEP's, 4 for the directory/extension combination times 2 for the charset/no-charset.
Before it did 32, because of parsing the family off as also a subdirectory.
Other devices, with single directories and single extensions (HTML?), should only do 2.
With more thought, we could also build in a little more knowledge (another FONTDEVICEPROP) about whether it is worth probing for the charset subdirectories c0>.