Bug 77293 - lack of ttmkfdir documentation or man page
Summary: lack of ttmkfdir documentation or man page
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-11-04 19:01 UTC by Gene Czarcinski
Modified: 2007-04-18 16:48 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-11-04 19:02:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Gene Czarcinski 2002-11-04 19:01:56 UTC
Description of Problem:
The mkfontscale man page refers to the ttmkfdir man page.  There is a complete
lack of when/why/what/who information available for ttmkfdir.

Furthermore, ttmkfdir is not even used consistantly. It is used by the
XFree86-truetype-fonts package but not by the openoffice package for its
truetype fonts.

Comment 1 Mike A. Harris 2002-11-05 10:42:13 UTC
There's no compelling reason to create a ttmkfdir manpage at this point,
as ttmkfdir has been deprecated, and will be replaced by mkfontscale in
the future.  Even though mkfontscale might still refer to the ttmkfdir
page, if we're not shipping ttmkfdir, we wont be shipping or creating
a manpage for it either.

If ttmkfdir is not used consistently, please file bug reports against the
specific packages that are not using it consistently.  The XFree86
packaging is the official Red Hat defacto way of using ttmkfdir, and if
any other packages aren't following my standard, they are wrong and
broken.  I've babysat a few other font packages in the past, but can't
keep up with everyone elses packages.  They need to take some responsibility
and call ttmkfdir properly like it is in XFree86 packaging.  That includes
openoffice.

However, if you report bugs against these packages, please note in the
bug report that ttmkfdir is disappearing also.  It'll help save me
some effort later on.

Thanks.


Note You need to log in before you can comment on or make changes to this bug.