example-tutorial example-tutorial-it.xml,NONE,1.1

[Paul W. Frields (pfrields)]

Author: pfrields

Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17171

Added Files:
	example-tutorial-it.xml 
Log Message:
Created bogus new i18n file for testing; don\'t waste time translating this.


--- NEW FILE example-tutorial-it.xml ---
<!-- $Id: -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

 <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;

<!ENTITY BOOKNAME "example-tutorial">
<!ENTITY BOOKVERSION "0.14"> <!-- change version here -->
<!ENTITY BOOKDATE "2005-09-18"> <!-- change revision date here -->
<!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)">
<!ENTITY BUG-NUM "000000"> <!-- use this only while in draft stage -->

]>

<!-- This file is just a copy of the English version, only here for testing -->
<!-- Makefile locale capabilities.  Nobody really needs to translate this -->
<!-- yet. -->


<article id="example-tutorial" lang="it">
  <articleinfo>
    <title>Example Tutorial</title>
    <copyright>
      <year>2003, 2005</year>
      <holder>&FORMAL-RHI;</holder>
      <holder>Tammy Fox</holder>
    </copyright>
    <authorgroup>
      <author>
  <surname>Fox</surname>
  <firstname>Tammy</firstname>
      </author>
      <editor>
  <surname>Frields</surname>
  <firstname>Paul</firstname>
  <othername role="mi">W.</othername>
      </editor>
    </authorgroup>
    &LEGALNOTICE;
    <revhistory>
      <revision>
	<revnumber>0.13</revnumber>
	<date>2005-09-18</date>
	<authorinitials>PaulWFrields</authorinitials>
	<revdescription>
	  <para>
	    Add revision history.
	  </para>
	</revdescription>
      </revision>
    </revhistory>
  </articleinfo>

  <section id="sn-some-section">
    <title>Some Section</title>

    <indexterm>
      <primary>Index term</primary>
    </indexterm>

    <para>
      This is an example section. You should not use sect1, sect2, etc., since
      those tags will make sections less modular — that is, harder to
      relocate without changing a lot of other markup.
    </para>
    <para>
      Keep text within the <command>title</command> tags on the same line as the
      tags. Nesting the title on a separate line from the enclosing tags results
      in extra spaces in HTML rendering.
    </para>

    <warning>
      <title>Warning</title>
      <para>
        Example of an admonition.
      </para>
    </warning>

    <para>
      This paragraph illustrates the use of command syntax to accomplish a
      task. Note that specific filenames denoting versions should be
      avoided. To install any RPM package, use the following syntax:
    </para>
<screen>
<userinput><command>rpm -ivh <replaceable>pkgname</replaceable>-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</command></userinput>
</screen>
    <para>
      Notice that the <command>screen</command> section is entirely
      left-justified with no preceding indent. This is necessary to ensure
      proper rendering in PDFs. Also notice that the entire
      <command>command</command> has been surrounded by
      <command>userinput</command> since the user types this
      command. Computer output would be enclosed in
      <command>computeroutput</command> tags, as in the following
      sample.
    </para>
<screen>
<userinput><command>grep snmptrap /etc/services</command></userinput>
<computeroutput>snmptrap        162/udp         snmp-trap       # Traps for SNMP</computeroutput>
</screen>
    <para>
      Lines should be broken <emphasis>exactly</emphasis> as they are
      on-screen. Also, note that spaces inside <command>screen</command> tags
      are automatically treated as non-breaking.
    </para>
    <tip>
      <title>Fill modes and <command>screen</command> tags</title>
      <para>
  Using automatic or manual fill commands in Emacs/PSGML will sometimes
  mangle <command>screen</command> sections. Use care when performing fill
  operations, and check the results.
      </para>
    </tip>
  </section>

  <section>
    <title>Callout Example</title>
      <programlisting id="pl-callout">
Line 1 <co id="pl-callout-L1"/>
Line 2
Line 3
Line 4 <co id="pl-callout-L4"/>
      </programlisting>
      <calloutlist>
        <callout arearefs="pl-callout-L1">
          <para>
            Here is a callout.
          </para>
        </callout>
        <callout arearefs="pl-callout-L4">
          <para>
            The second callout.
          </para>
        </callout>
      </calloutlist>
  </section>

<index id="generated-index"></index>
</article>

<!--
Local variables:
mode: xml
End:
-->