[CLOSED] "Find Glyph" fails when only a single character is entered

Post your bug reports here. Include information that helps us to understand and reproduce the bug.
Post Reply
nabsltd
Posts: 131
Joined: Tue Oct 18, 2016 12:35 am

[CLOSED] "Find Glyph" fails when only a single character is entered

Post by nabsltd » Tue Jul 24, 2018 6:28 pm

In FontCreator 11.5.0.2427, 64-bit:

Entering something like "O" in the "Find Glyph" finds only an exact match, even if "Exact match" is not checked.

I was trying to find all the various accented "O" characters in a font (because some were composite and some were not, and I wanted to fix that), but only the uppercase "O" is found. Regardless of the single character entered, the same sort of thing happens.

Although this may be a design decision to keep too many results from being found, because the "Exact match" checkbox exists, the behavior should be changed to always find all matches unless that checkbox is checked.

Bhikkhu Pesala
Top Typographer
Top Typographer
Posts: 7470
Joined: Tue Oct 29, 2002 5:28 am
Location: Seven Kings, London UK
Contact:

Re: "Find Glyph" fails when only a single character is entered

Post by Bhikkhu Pesala » Tue Jul 24, 2018 8:03 pm

Search for O*

Finding Glyphs
My FontsReviews: MainTypeFont CreatorHelpFC11.5 Pro + MT8.0 @ Win10 1803 build 17134.345

nabsltd
Posts: 131
Joined: Tue Oct 18, 2016 12:35 am

Re: [CLOSED] "Find Glyph" fails when only a single character is entered

Post by nabsltd » Thu Jul 26, 2018 12:38 am

Again, regardless of this being a design decision, it's not intuitive when there is are "exact match" and "case sensitive" check boxes.

Also, this means there is no way to disable the rudimentary wildcard support, which can be a problem because an asterisk is a perfectly valid character to be contained in a glyph name. Now there is no way to find such glyphs, because there is no way to escape the asterisk. There is also no way to find glyphs with names that contain a specific character in the middle, as "X*" looks at the beginning and "*X" looks at the end. "*X*" finds nothing.

It would be much better to include a "regex" checkbox that enabled that sort of feature, and allow the checkboxes to do what they say, just like every other application.

Post Reply