From f6d5af1ecfe2740dbc7c659f7a4d3188ec13d60a Mon Sep 17 00:00:00 2001 From: Sven Neumann Date: Mon, 13 Apr 1998 11:44:11 +0000 Subject: [PATCH] Fixed some typos and updated the man-page. Could someone please check for a way to install the man-page by default ?!? --Sven --- ChangeLog | 4 ++++ docs/gimp.1 | 52 ++++++++++++++++++++++++++++++++-------------------- 2 files changed, 36 insertions(+), 20 deletions(-) diff --git a/ChangeLog b/ChangeLog index 6385570c39..367a018e3c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +Mon Apr 13 13:40:50 MEST 1998 Sven Neumann + + *docs/gimp.1: fixes and updates to the man-page + Mon Apr 13 13:00:20 MEST 1998 Sven Neumann * gimp_tips.txt: more tips and nicer line wrap diff --git a/docs/gimp.1 b/docs/gimp.1 index a0abbe5204..405d38dae2 100644 --- a/docs/gimp.1 +++ b/docs/gimp.1 @@ -1,4 +1,4 @@ -.TH GIMP 1 "19 Feb 1998" Version 1.0 +.TH GIMP 1 "13 Apr 1998" Version 1.0 .SH NAME Gimp - an image manipulation and paint program. .SH SYNOPSIS @@ -82,7 +82,7 @@ to get the name of a resource file that overrides the global resources stored in the RESOURCE_MANAGER property. .SH FILES - Most gimp configuration is read in from the users init file, +Most gimp configuration is read in from the users init file, \fB$HOME\fP/.gimp/gimprc. The sytem wide equivalent is in \fB$PREFIX\fP/share/gimp/gimprc. The system wide file is parsed first and the user gimprc can override the sytem @@ -101,21 +101,25 @@ such as widget color and fonts sizes can be set here. \fB$HOME\fP/.gimp/plug-ins - location of user installed plugins. \fB$HOME\fP/.gimp/pluginrc - plugin initialization values are stored -here. This file is parsed onstartup and regenerated if need be. +here. This file is parsed on startup and regenerated if need be. \fB$HOME\fP/.gimp/tmp - default location that gimp uses as temporary space. - Gimp's data files are stored in \fB$PREFIX\fP/share/gimp where +Gimp's data files are stored in \fB$PREFIX\fP/share/gimp where \fB$PREFIX\fP is set on install, but is typically /usr/local. \fB$PREFIX\fP/share/gimp/brushes - system wide brush files. -\fB$HOME\fP/.gimp/palettes - user created and installed brush +\fB$HOME\fP/.gimp/brushes - user created and installed brush files. This files are in the .gbr (gimp brush) format. -\fB$PREFIX\fP/share/gimp/palettes - the system wide palette files. +\fB$PREFIX\fP/share/gimp/palettes - the system wide palette files. The +files are copied to the user palettes directory when gimp is first ran +to allow the user to modify the palettes. This directory is not searched +for palettes by default. -\fB$HOME\fP/.gimp/palettes - user created and modified palette files. +\fB$HOME\fP/.gimp/palettes - copies of the system palette files as well as +user created and modified palette files. \fB$PREFIX\fP/share/gimp/patterns - basic set of patterns for use in gimp. @@ -172,29 +176,37 @@ both that copyright notice and this permission notice appear in supporting documentation. .SH SUGGESTIONS AND BUG REPORTS - Any bugs found should be reported to the Gimp Developer mailing list -at gimp-developer@scam.xcf.berkeley.edu. Before reporting bugs, please -check to see if the bug is mentioned in the FAQ's or the mailing list -archive. See the section on Other Info for locations of these. - When supporting Gimp bugs, it is important to include a -reliable way to reproduce the bug, verison number of Gimp (and -probabaly GTK), OS name and verison, and any relevant hardware -specs. It is also very important to include as much info about the -Xserver the problem was found on as possible including at least server +Any bugs found should be reported to the Gimp Developer mailing list +at gimp-developer@scam.xcf.berkeley.edu or you may want to make use +of the online bug-tracking system available on the web at +http://www.wilberworks.com/bugs.html. + +Before reporting bugs, please check to see if the bug is mentioned +in the FAQ's or the mailing list archive. See the section on Other +Info for locations of these. + +When reporting Gimp bugs, it is important to include a +reliable way to reproduce the bug, version number of Gimp (and +probably GTK), OS name and verison, and any relevant hardware +specs. It is also very important to include as much info aas possible +about the Xserver the problem was found on including at least server name, the visual, and the bit depth. - If a bug is causing a crash, it is very useful if a stack trace + +If a bug is causing a crash, it is very useful if a stack trace can be provided. And of course, patches to rectify the bug are even better. .SH OTHER INFO - The cannonical place to find GIMP info is at http://www.gimp.org. +The cannonical place to find GIMP info is at http://www.gimp.org. Here you can find links to just about every other gimp site, tutorials, data sets, mailing list archives, and more. - There is also a Gimp User Manual available at + +There is also a Gimp User Manual available at http://www.dtek.chalmers.se/~d95olofs/manual/ that goes into much more detail about the interactive use of Gimp. - The latest version of Gimp and the gtk libs is always available at + +The latest version of Gimp and the gtk libs is always available at ftp://ftp.gimp.org. .SH AUTHORS