<?php
include_once $_SERVER['DOCUMENT_ROOT'] . '/include/shared-manual.inc';
$TOC = array();
$TOC_DEPRECATED = array();
$PARENTS = array();
include_once dirname(__FILE__) ."/toc/book.ps.inc";
$setup = array (
  'home' => 
  array (
    0 => 'index.php',
    1 => 'PHP Manual',
  ),
  'head' => 
  array (
    0 => 'UTF-8',
    1 => 'uk',
  ),
  'this' => 
  array (
    0 => 'intro.ps.php',
    1 => 'Вступ',
    2 => 'Вступ',
  ),
  'up' => 
  array (
    0 => 'book.ps.php',
    1 => 'PS',
  ),
  'prev' => 
  array (
    0 => 'book.ps.php',
    1 => 'PS',
  ),
  'next' => 
  array (
    0 => 'ps.setup.php',
    1 => 'Встановлення/налаштування',
  ),
  'alternatives' => 
  array (
  ),
  'source' => 
  array (
    'lang' => 'en',
    'path' => 'reference/ps/book.xml',
  ),
  'history' => 
  array (
  ),
);
$setup["toc"] = $TOC;
$setup["toc_deprecated"] = $TOC_DEPRECATED;
$setup["parents"] = $PARENTS;
manual_setup($setup);

contributors($setup);

?>
<div id="intro.ps" class="preface">
  <h1 class="title">Вступ</h1>
  <p class="para">
   This module allows to create PostScript documents. It has many
   similarities with the pdf extension. Actually the API is almost
   identical and one can in many cases just replace the prefix of
   each function from pdf_ to ps_. This also works for functions which
   has no meaning in the PostScript document (like adding hyperlinks)
   but will have an effect if the document is converted to PDF.
  </p>
  <p class="para">Documents created by this extension are sometimes even superior
   to documents created with the pdf extension, because pslib&#039;s text
   rendering functions can handle kerning, hyphenation and ligatures
   which results in much better output of boxed text.
  </p>
 </div><?php manual_footer($setup); ?>