Correspondence, troubleshooting, and bug reports


Welcome     Gallery     Handbook


Manual page for Correspondence,_troubleshooting,_and_bug_reports(PL)

DEBIAN CORRESPONDENCE

If you have problems with the Debian package, please use the Debian Bug Tracking System, as usual. You may also email me at jpenny@debian.org jpenny@debian.org You may also use the addresses below. But, if you think it is purely a Debian problem, please contact me first.

CORRESPONDENCE

Steve Grubb is the author of ploticus.

You can reach me by email at scg@jax.org , or by posting to the ploticus news group (you don't have to join the newsgroup to post or browse). I reserve the right to use your message in the user feedback page or FAQ . If you have interesting examples or web sites that use ploticus, please send the URLs or script files.


TROUBLESHOOTING

Here are some troubleshooting tips and common snafus:
  • Unix users should download gzip tar files. Zip files are intended only for PC environments (text files have CR/LF line terminators).

  • Before compiling, review the Makefile and follow the simple 3-step installation guide.

  • An ANSI-compliant C compiler such as gcc is required to compile the source code.

  • After building, do a quick test. From within the src directory type ploticus stock.htm. For further testing see pltestsuite , or run some gallery examples.

  • If you get this error: ploticus error 4899: No PLOTICUS_PREFABS env var (or hardcoded Makefile PREFABS_DIR) found, it indicates that no default prefabs directory was specified at build time and that each user must have the PLOTICUS_PREFABS environment variable set and exported. It must contain the full pathname of the directory where ploticus prefabs reside, as included in the download.

  • Be sure you know which version you are executing (you might have earlier ploticus versions on your system and not realize it). Use ploticus -version to print the ploticus version; use the unix command which pl to print the file that you are actually executing when you type ploticus.

  • Unix builds do not read native PC text files. This problem occurs if ploticus is compiled on a unix machine and you feed it native PC text files, either as scripts or data files. Symptoms may include truncated multi-line text items, or garbage characters appearing at the end of text items.

  • If an image result contains blank areas at the top or side, it is probably because the image is larger than 8" x 8" in one or both dimensions. To generate images larger than 8" x 8" a sufficient pagesize must be specified, either on the command line or via proc page.


BUG REPORTS

Much of the incremental improvement in this package has been due to the careful bug reports that have been sent in by attentive users. Thanks! Bug reports should be sent to scg@jax.org .. If reporting a problem, please:
  • Check the release notes first, where known bugs are listed.
  • Indicate the environment where you invoked ploticus (eg. linux, solaris, windows/NT, etc.)
  • Supply your ploticus version number (type ploticus -version to find out).
  • Describe how you invoke ploticus (eg. from the command line, via PHP system(), etc.) If you are using a ploticus config file please attach it.
  • A self-contained example that demonstrates the problem is usually very helpful.


data display engine  
Copyright Steve Grubb


Markup created by unroff 1.0,    February 23, 2002.