Subversion Repositories planix.SVN

Rev

Rev 2 | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
2 - 1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2
<html>
3
<head>
4
<title>Ghostscript problem report form</title>
5
<!-- $Id: Bug-form.htm,v 1.49 2005/10/20 19:46:23 ray Exp $ -->
6
<!-- Originally: bug-form.txt -->
7
<link rel="stylesheet" type="text/css" href="gs.css" title="Ghostscript Style">
8
</head>
9
 
10
<body>
11
<!-- [1.0 begin visible header] ============================================ -->
12
 
13
<!-- [1.1 begin headline] ================================================== -->
14
 
15
<h1>Ghostscript problem report form</h1>
16
 
17
<!-- [1.1 end headline] ==================================================== -->
18
 
19
<!-- [1.0 end visible header] ============================================== -->
20
 
21
<!-- [2.0 begin contents] ================================================== -->
22
 
23
<p>
24
Before using this form, please read the <a
25
href="Bug-info.htm">instructions</a> for reporting problems. If you are
26
running a developer or beta version of Ghostscript, and you are an
27
experienced tester (for example, if you have been testing Ghostscript
28
for more than a year, or you have already submitted at least two problem
29
reports that we accepted for investigation), you can send an informal report
30
to the place indicated below. Otherwise, please fill out this form
31
completely. Fill out <strong>all</strong> applicable items in this form.
32
 
33
<p>
34
Most importantly, you <strong>must</strong> include all data (PostScript files,
35
PDF files, batch/script files, and/or fonts) required to reproduce the problem,
36
either
37
by giving a URL from which we can download the data, or by including the
38
data with the report itself. If you don't include this information, we can't
39
investigate the problem. Please note that the bug reports are publicly
40
archived, so the information you provide will be generally available. If the
41
test data absolutely must remain confidential, please so indicate on the form
42
below and provide an address we may contact privately for the file. 
43
 
44
<p>
45
Once you have prepared the report, go to <a
46
href="http://bugs.ghostscript.com" 
47
class="offsite">http://bugs.ghostscript.com</a>. 
48
and follow the instructions there. Data files can be attached to the 
49
bug report after the bug is submitted. 
50
Use the completed problem reporting form as 
51
the body of the Bugzilla submission. If by some reason the Bugzilla doesn't
52
work for you, bugs can be submitted as follows:
53
 
54
<ul>
55
 
56
<li>If you are running MS-DOS, MS Windows, or OS/2, and you are reasonably
57
sure that the problem is specific to your platform, mail to <a
58
href="mailto:bug-gswin@ghostscript.com">bug-gswin@ghostscript.com</a>.
59
 
60
<li>If you are running MacOS, and you are reasonably sure that the problem
61
is specific to the Mac, mail to <a
62
href="mailto:mac-gs@ghostscript.com">mac-gs@ghostscript.com</a>.
63
 
64
<li>Otherwise, mail to <a
65
href="mailto:bug-gs@ghostscript.com">bug-gs@ghostscript.com</a>.
66
 
67
</ul>
68
 
69
<p>
70
Fully completed problem reports help us improve Ghostscript.  Thanks in
71
advance.
72
 
73
<pre>
74
------------------------------------------------------------------------
75
Symptoms:
76
 
77
 
78
 
79
------------------------------------------------------------------------
80
Ghostscript version (or include output from "gs -h"):
81
 
82
------------------------------------------------------------------------
83
Where you got Ghostscript:
84
 
85
------------------------------------------------------------------------
86
Hardware system you are using (including printer model if the problem
87
involves printing):
88
 
89
------------------------------------------------------------------------
90
Operating system you are using:
91
 
92
------------------------------------------------------------------------
93
If you are using X Windows, and your problem involved output to the
94
screen, the output from running xdpyinfo and xwininfo:
95
 
96
------------------------------------------------------------------------
97
C compiler you are using, including its version, if you compiled
98
Ghostscript yourself:
99
 
100
------------------------------------------------------------------------
101
If you compiled Ghostscript yourself, changes you made to the makefiles:
102
 
103
------------------------------------------------------------------------
104
Environment variables:
105
 
106
	GS_DEVICE
107
 
108
	GS_FONTPATH
109
 
110
	GS_LIB
111
 
112
	GS_OPTIONS
113
 
114
------------------------------------------------------------------------
115
Command line:
116
 
117
------------------------------------------------------------------------
118
URL or FTP location of test files (include the data at the end of this
119
form if 500K or less):
120
 
121
 
122
------------------------------------------------------------------------
123
Suggested fix, if any:
124
 
125
 
126
 
127
------------------------------------------------------------------------
128
Other comments:
129
 
130
 
131
 
132
</pre>
133
 
134
<!-- [2.0 end contents] ==================================================== -->
135
 
136
<!-- [3.0 begin visible trailer] =========================================== -->
137
<hr>
138
 
139
<p>
140
<small>Copyright &copy; 1996, 2001 artofcode LLC.  All rights
141
reserved.</small>
142
 
143
<p>
144
<small>This file is part of AFPL Ghostscript.  See the <a
145
href="Public.htm">Aladdin Free Public License</a> (the "License") for full
146
details of the terms of using, copying, modifying, and redistributing AFPL
147
Ghostscript.</small>
148
 
149
<p>
150
<small>Ghostscript version 8.53, 20 October 2005
151
 
152
<!-- [3.0 end visible trailer] ============================================= -->
153
 
154
</body>
155
</html>