Apache OpenOffice (AOO) Bugzilla – Issue 12619
spadmin does not remove fonts from $USER/OOo/user/psprint/pspfontcache
Last modified: 2003-04-01 15:34:22 UTC
When spadmin is used to remove fonts that is added it shows that the fonts have been removed however the fonts are still opened when soffice runs. The user's pspfontcache does not change when spadmin is used to remove fonts. The file still lists the removed fonts although the spadmin GUI doesn't show them. I have seen this when I truss soffice. It read the names from my pspfontcache then xstats the full list. I added a lot of fonts just to see what happened, decided I didn't like them (too much in the font menus!) so removed them but they still get look at and prolongs startup needlessly.
TM->JA: Please have a look, thanks !
JA: as discussed with a developer this behaviour is not a bug and as a performance issue I cannot accept this because performance tuning of the font list is already work in progress...so please stay tuned...closing this issue as invalid
JA: closing issue
Sorry, I don't understand the comments. You have "discussed with the developer"; would you kindly expand so the dumb user who has to wait while this product starts up can understand. Are you saying that "bloatware" is acceptable? I add fonts, I ask for them to be removed, they are not. Why is this correct? If you are saying that this problem has already been fixed in another way, or exists due to a bug in another system, or that it will be fixed becasue the whole font system is due for change then fine, but that is different from telling me that this doesn't happen or is correct.
JA->PL: could you please clearify this ? Reassigned to you...
The problem is fixed 2 ways: 1) the behaviour was intended since the font cache (that is the C++ object behind the file pspfontcache) is supposed to check its consistency; therefore it checks for files inside the cache and removes them from the cache if either they are not available anymore or the have changed modification times 2) the above method of updating was not deemed fast enough and therefore the cache code was rewritten (see issue 12889) so that the font cache invalidates itself when a cached directory changes. Hope that helps *** This issue has been marked as a duplicate of 12889 ***
closed duplicate