%PDF-
%PDF-
Mini Shell
Mini Shell
<html>
<head>
<title>Ghostscript problem report form</title>
<!-- $Id: Bug-form.htm,v 1.9.2.3 2000/12/02 22:15:04 raph Exp $ -->
<!-- Originally: bug-form.txt -->
</head>
<body>
<!-- [1.0 begin visible header] ============================================ -->
<!-- [1.1 begin headline] ================================================== -->
<table width="100%" border="0">
<tr><th align="center" bgcolor="#CCCC00"><font size=6>
Ghostscript problem report form
</font>
</table>
<!-- [1.1 end headline] ==================================================== -->
<!-- [1.0 end visible header] ============================================== -->
<!-- [2.0 begin contents] ================================================== -->
<p>
Before using this form, please read the <a
href="Bug-info.htm">instructions</a> for reporting problems. If you are
running a developer or beta version of Ghostscript, and you are an
experienced tester (for example, if you have been testing Ghostscript since
before January 1, 2000, or you have already submitted at least two problem
reports that we accepted for investigation), you can send an informal report
to the place indicated below. Otherwise, please fill out this form
completely. Fill out <strong>all</strong> applicable items in this form.
In particular, you <strong>must</strong> include all data (PostScript files,
PDF files, batch/script files, and/or fonts) involved in the problem, either
by giving a URL from which we can download the data, or by including the
data with the report itself. If you don't include this information, we
can't investigate the problem.
<p>
Once you have prepared the report, if you are reporting a problem in a
stable release of AFPL Ghostscript, and you do not need to attach any files
to the report, go to <a
href="http://sourceforge.net/bugs/?func=addbug&group_id=1897">
http://sourceforge.net/bugs/?func=addbug&group_id=1897</a>and follow the
instructions there. Use the completed problem reporting form as the body of
the Bug Tracker submission. Otherwise (i.e., if you are reporting a problem
in a developer or beta fileset, or you need to attach files to the report),
e-mail the form, with any attached files, as follows:
<ul>
<li>If the problem is in a developer fileset, mail to <a
href="mailto:bug-gs-dev@ghostscript.com">bug-gs-dev@ghostscript.com</a>.
<li>If the problem is in a beta fileset, mail to <a
href="mailto:bug-gs-beta@ghostscript.com">bug-gs-beta@ghostscript.com</a>.
<li>Otherwise (the problem is in a stable fileset):
<ul>
<li>If you are running MS-DOS, MS Windows, or OS/2, and you are reasonably
sure that the problem is specific to your platform, mail to <a
href="mailto:bug-gswin@ghostscript.com">bug-gswin@ghostscript.com</a>.
<li>If you are running MacOS, and you are reasonably sure that the problem
is specific to the Mac, mail to <a
href="mailto:mac-gs-bugs@ghostscript.com">mac-gs-bugs@ghostscript.com</a>.
<li>Otherwise, mail to <a
href="mailto:bug-gs@ghostscript.com">bug-gs@ghostscript.com</a>.
</ul>
</ul>
<p>
Fully completed problem reports help us improve Ghostscript. Thanks in
advance.
<font size="+1"><pre>
------------------------------------------------------------------------
Symptoms:
------------------------------------------------------------------------
Ghostscript version (or include output from "gs -h"):
------------------------------------------------------------------------
Where you got Ghostscript:
------------------------------------------------------------------------
Hardware system you are using (including printer model if the problem
involves printing):
------------------------------------------------------------------------
Operating system you are using:
------------------------------------------------------------------------
If you are using X Windows, and your problem involved output to the
screen, the output from running xdpyinfo and xwininfo:
------------------------------------------------------------------------
C compiler you are using, including its version, if you compiled
Ghostscript yourself:
------------------------------------------------------------------------
If you compiled Ghostscript yourself, changes you made to the makefiles:
------------------------------------------------------------------------
Environment variables:
GS_DEVICE
GS_FONTPATH
GS_LIB
GS_OPTIONS
------------------------------------------------------------------------
Command line:
------------------------------------------------------------------------
URL or FTP location of test files (include the data at the end of this
form if 500K or less):
------------------------------------------------------------------------
Suggested fix, if any:
------------------------------------------------------------------------
Visibility of report to the public (change the answers if you want):
May we make this problem report public? yes
May we include your e-mail address in a public report? no
May we make the test data (if longer than about 20 lines) public? no
Other preferences about visibility:
------------------------------------------------------------------------
Other comments:
</pre></font>
<!-- [2.0 end contents] ==================================================== -->
<!-- [3.0 begin visible trailer] =========================================== -->
<hr>
<font size=2>
<p>Copyright © 1996, 2000 Aladdin Enterprises. All rights reserved.
<p>This file is part of AFPL Ghostscript. See the <a
href="Public.htm">Aladdin Free Public License</a> (the "License") for full
details of the terms of using, copying, modifying, and redistributing AFPL
Ghostscript.
<p>
Ghostscript version 6.50, 2 December 2000
</font>
<!-- [3.0 end visible trailer] ============================================= -->
</body>
</html>
Zerion Mini Shell 1.0