Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | User can't figure out how to add fonts with spadmin | ||
---|---|---|---|
Product: | General | Reporter: | dankegel <dank> |
Component: | ui | Assignee: | ulf.stroehler |
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@framework <issues> |
Severity: | Trivial | ||
Priority: | P2 | CC: | issues, xslf |
Version: | OOo 1.1 RC3 | ||
Target Milestone: | OOo 1.1.1 | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
dankegel
2003-08-20 23:50:58 UTC
Setting target to 1.1.1 on the assumption that other people aren't seeing this, so it's not a showstopper for 1.1.0. But if other people can reproduce this, maybe it *is* a showstopper... TM->US: Please have a look, thanks ! Still happening in build 645m17 8683 More details: OS is Red Hat 9. I get the "Add Fonts" dialog, then click on the ellipsis button, and navigate to /mnt/winnt/fonts, a directory in a VFAT partition mounted read-write, containing 98 font files ending in .ttf and 110 font files ending in .TTF. The dialog box "Select path" has "/mnt/winnt/fonts/" in the Path: field, but nothing in the list of files. I guess it's just a usability issue. I expect to be shown fonts -- but the UI is very confusing, and shows me a blank list! Clicking "Select" at that point brings me back to the "Add Fonts" which does seem to have the fonts there, but it's really hard to say. And when I click "OK", it beeps and says "0 new fonts added". How annoying! So the real problem is that there are two dialog boxes where I expected one, and the dialog boxes are poorly designed. I can't wait for fontconfig support, at which point I'll be able to use Linux's tools for font management, and not this spadmin piece of cr*p. WFM. User error. Works as designed. Submit an Enhancement (and weigh your words:-) if the dialog should be changed. Indeed the behaviour is a bit unorthodox. Closing Issue. Yes, I agree, it's broken-as-designed. I think OpenOffice 2.0 is scheduled to fix this. |