951      iPhone_iPad_Mac_apple

Series of bugs in Font Book 7.0?

This particular instance is for Font Book 7.0 (302.1) running on an iMac 27" mid 2011 with 12Gb RAM on Sierra 10.12.6.

Font Book is one of those Apple Apps I want to like but Apple makes that extremely difficult.

I am covering ground I have noticed over several versions of Font Book.

This was kicked off by a poster in the Pages forum reporting fonts opened in Font Book appeared in Keynote but not Pages.

In investigating the problem, I decided it was time to list everything else that is wrong in Font Book.

1. Fonts not importing the first time. Often it takes several shots to get double clicked fonts in Finder to be listed in Font Book. Sometimes they stubbornly do not import, without explanation.

2. Extreme lag in importing fonts. They can appear to not be listed but will be listed at a much later time.

3. That leads to the subsequent issue of multiple installations. Because of the delay in listing the User tries again and Font Book double installs fonts.

4. Incomplete family installations. Some fonts install and not others, or again with much delay.

5. Search doesn't work. You can click in the Search field, it is selected, you can choose from search options in the drop down menu in Search, but can't type anything into the Search field.

6. Mouse scrolling (Magic Mouse) doesn't work in Font Book, works everywhere else, and I am forced to use the scroll bar.

7. You can not view a Collection and All Fonts (there aren't list columns for each) at the same time so have to flick between both, trying to remember what is in the collections list or write lists on paper to build up a collection.

8. Every time you switch between a collection and All Fonts, Font Book loses its place and you have to scroll all over again with the "won't use mouse scrolling" problem.

As with most recent Apple software, Apple goes into a project half-arsed with seemingly good intentions but glaringly naïve UI faux pas, and then after adding it to macOS neglects it and never fixes it.

Font handling is one of those essential system operations that really should be tidied up. I dream of the good old days of the Classic System and ATM, plus other Font Managers of the day, which were quick, accurate, extremely user friendly, flexible, reliable and worked with huge collections of fonts.

Is anyone else out there having similar issues or found anything I missed?

Peter

最後更新：2017-10-12 09:48:10

  上一篇： Can we add the Quokka emoji please?

  下一篇： mail can't verify the identity...