Issue 18663 - Permit Font Categories
Summary: Permit Font Categories
Status: UNCONFIRMED
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: OOo 1.1 RC3
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-26 02:34 UTC by rblackeagle
Modified: 2013-02-07 22:42 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description rblackeagle 2003-08-26 02:34:48 UTC 
I believe it would help some of us to be able to have font categories so we
could choose the types of fonts we want to look at.  A few come to mind: Grunge
fonts, business fonts, Headline fonts, Caps only fonts.  To be effective, the
font categories probably should be left to the user to choose (with maybe a few
put in to illustrate some categories).  Full implementation would not permit
deletion of a category that contained fonts.

In any case, as a > later goal, I think this would be something worthwhile,
especially for those of us with many hundreds of fonts.
Comment 1 dnwilson 2003-08-26 08:12:22 UTC 
My issue 15422 may be a duplicate of this, if not it is similar.
Comment 2 Olaf Felka 2003-08-26 09:27:16 UTC 
Please have a look.
Comment 3 rblackeagle 2003-08-26 16:02:05 UTC 
Not quite a duplicate, but another way of approaching the same thing.
 In my way, you could have "preferred fonts" but list them as, say
"Preferred Text Fonts," "Preferred Headline Fonts" and so on.  In my
case, while that would work well, I would like to be able to put all
Script fonts in one grouping, all Grunge fonts in another, Caps only
fonts in another and Text fonts in another.  I would also have three
other categories for some special effects fonts.  That would make
navigating to and finding an appropriate font much faster.

I'm not sure it would be a duplicate, but it is somewhat similar.  If
developers want to look at them as a single issue, I'm for it.
Comment 4 rblackeagle 2004-03-05 20:02:47 UTC 
Any ideas on how this might be implemented?
Comment 5 ace_dent 2008-05-16 02:14:33 UTC 
OpenOffice.org Issue Tracker - Feedback Request.

The Issue you raised is currently 'Unconfirmed' pending review, but has not been
updated within the last 3 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version: http://download.openoffice.org/index.html
or consider trying the new OOo 3 BETA (still in testing):
http://download.openoffice.org/3.0beta/
 
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
http://www.openoffice.org/issues/query.cgi
 
Many thanks,
Andrew
 
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 6 bettina.haberer 2010-05-21 15:04:12 UTC 
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".