Apache OpenOffice (AOO) Bugzilla – Issue 102652
Fonts in directory with name having underscore character in it, are not found
Last modified: 2009-06-16 12:24:55 UTC
On Fedora 10 (up to date) (Sorry if the subcategory is wrong; not shure of where this belongs.) I had a subdirectory in /usr/share/fonts that had a name with underscore characters as word separators. The fonts in it did not show up in OO Writer. Permissions and SELinux contexts were the same for both directory and files as for other directories and fontfiles that did show up in the fontlist. I did restart Writer each time I made a change to permissions or contexts, but nothing changed. After I removed the underscore characters from the directory name, the fonts showed up in OO Writer after a restart. The names of the files in that directory also have underscore characters in them, but it does not prevent them from being included in the list. Normal behaviour would be that the underscore character did not cause directories to be skipped, as it is one of the allowed characters.
Sorry for the double posting. I got several "fatal errors" on the submission confirmation page, so I posted it again. It was just my forgetting to allow scripts from www-cdn.sun.com. I'll close this issue, use 102653 instead Again: I'm sorry for the inconvenience.
*** Issue 102653 has been marked as a duplicate of this issue. ***
Please, try to rebuild font cache with fc-cache.
I reverted the name of the directory to it's old one, including underscore characters. As before, OO Writer didn't show those fonts. Then I ran fc-cache as my normal user. The fonts now show up as they should. The problem is solved. I don't understand, though, why I can add a directory without underscore characters in the name, and the fonts in it are found, whereas directories _with_ underscore in their names are not read. Should this still be considered a bug? If so, is it a Fedora or OOo bug? Thanks for the help in solving my problem.
> Should this still be considered a bug? If so, is it a Fedora or OOo bug? Looks like an issue for fontconfig. A very low priority issue though because fontconfig has the very reasonable expectation that fc-cache gets run whenever its directory structure or directory contents were changed. Not an issue for OOo though => adjusting status accordingly
closed