- Joined
- Dec 14, 2012
- Messages
- 10
- Reaction score
- 0
- Points
- 1
I'm a fairly light 'home user' of fonts so I'd be most comfortable just using Font Book as my font manager, simply because it comes with the OS and I'd expect it to do the job. I hear tell there are more robust and complex font managers out there but if Font Book does what little I need it for then I'd like to stick with it.
However... there are a couple of 'workflow' issues that i keep running into. Nothing wrong with the actual software itself but i just don't get how the way some of it works would actually sensibly fit into a workflow... so what i'm looking for is either (a) an option to alter the priorities FontBook uses (which i don't think you can 'cos the preferences menu is pretty basic) or (b) could someone suggest an alternative workflow method that would make more sense??
Ok here's my gripe... If I have 2 font collections, lets call them SetA and SetB, that have some overlapping fonts, then if I have SetA enabled and SetB disabled I'd expect all the fonts in SetA to be enabled and all the fonts in SetB to be disabled except for the one's that it has in common with SetA.
This isn't the case as fonts that are common to the 2 sets remain disabled in SetA. ie FontBook seems to give precedence to disabling fonts rather than enabling them. No matter how I look at it this seems to be the wrong way round.
My inclination is to want to enable all of the font collections that i want access to - not discover that i then have to enable individual fonts within that collection afterwards because they are also in a font collection that is disabled.
Have I got this right - or am i missing something fundamental about how FontBook prioritises its enabling/disabling functions?
However... there are a couple of 'workflow' issues that i keep running into. Nothing wrong with the actual software itself but i just don't get how the way some of it works would actually sensibly fit into a workflow... so what i'm looking for is either (a) an option to alter the priorities FontBook uses (which i don't think you can 'cos the preferences menu is pretty basic) or (b) could someone suggest an alternative workflow method that would make more sense??
Ok here's my gripe... If I have 2 font collections, lets call them SetA and SetB, that have some overlapping fonts, then if I have SetA enabled and SetB disabled I'd expect all the fonts in SetA to be enabled and all the fonts in SetB to be disabled except for the one's that it has in common with SetA.
This isn't the case as fonts that are common to the 2 sets remain disabled in SetA. ie FontBook seems to give precedence to disabling fonts rather than enabling them. No matter how I look at it this seems to be the wrong way round.
My inclination is to want to enable all of the font collections that i want access to - not discover that i then have to enable individual fonts within that collection afterwards because they are also in a font collection that is disabled.
Have I got this right - or am i missing something fundamental about how FontBook prioritises its enabling/disabling functions?