I stopped using MT because of how fonts were handled. I found myself getting too frustrated with fonts that it either would not display due to complexity, fonts that I had “deleted” from MT still showing up at times or once added back in (the whole font creation cycle thing) not being able to be activated, etc., etc. I spent too much time rebuilding, uninstalling/reinstalling, etc., to make it worth while to me.
Before I fully left MT (but had installed another FM), I believe I wrote a request for a different means of dealing with the database. Without being able to actually remove something from a database, there is no DB management. Which defeats the purpose of a DB. But it shouldn’t end with just the deletion. I have no idea the structure of the database, but most need to be able to be optimized once in a while for efficient indexing.
4 years on and MainType is much better. I returned to using it once this issue was (supposedly) resolved. I am so disappointed that it still has problems deleting fonts.
I have over 50,000 fonts and periodically cleanout old versions.
Option 1 on the Delete Fonts panel states:
Delete the selected font(s) from all known file system locations and from your MainType library. The font(s) will no longer be available.
Nah, it doesn’t. Yes, it removes them from the database, great, that was the tricky part that you have done very well to achieve, but it doesn’t delete them from the file system. The next time you do a Library Refresh you have them back in the database. I have to manually delete the font file. That may not seem like a big deal but it is when you are managing a large collection. Fonts are located on a network drive with full user permissions.
Is there something I am missing? I would have thought this would have been tested so it’s got to be something at my end not right.
We’ve just released MainType 9.0.0.1199 which comes with several bug fixes and improvements, so please give it a try and let us know your results.
We’ve tested it and it works just fine, but if it continues to fail on your system and it is reproducible, we should be able to find the cause and a way to solve the problem.
Thanks for that. Still a problem though. I noticed the font folders had been given the Read Only attribute so ok I removed that, tried a Library Refresh and the Read Only tag was back. This is only on network folders (NTFS). As an experiment I copied some fonts to a local drive and was able to successfully delete them through MainType.
Is there something in MT setting the fonts to Read Only on network locations?
Some more testing… the Read Only tagging is not caused by MainType but it’s a Windows thing I will have to investigate a bit. Having said that, MainType should still be able to delete these files depending on what access rights it assigns itself. If it is using the user’s rights it should be fine.