From fedora-docs-commits at redhat.com Wed Jun 10 15:29:04 2015 Content-Type: multipart/mixed; boundary="===============2712312104326950986==" MIME-Version: 1.0 From: fedora-docs-commits at redhat.com To: docs-commits at lists.fedoraproject.org Subject: example-tutorial example-tutorial-it.xml,NONE,1.1 Date: Sun, 20 Nov 2005 10:28:24 -0500 Message-ID: <200511201528.jAKFSOT0017187@cvs-int.fedora.redhat.com> --===============2712312104326950986== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 --- %FEDORA-ENTITIES-EN; ]>
Example Tutorial 2003, 2005 &FORMAL-RHI; Tammy Fox Fox Tammy Frields Paul W. &LEGALNOTICE; 0.13 2005-09-18 PaulWFrields Add revision history.
Some Section Index term This is an example section. You should not use sect1, sect2, etc., si= nce those tags will make sections less modular — that is, harder to relocate without changing a lot of other markup. Keep text within the title tags on the same line a= s the tags. Nesting the title on a separate line from the enclosing tags re= sults in extra spaces in HTML rendering. Warning Example of an admonition. 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: rpm -ivh pkgname-version.arch.rpm Notice that the screen section is entirely left-justified with no preceding indent. This is necessary to ensure proper rendering in PDFs. Also notice that the entire command has been surrounded by userinput since the user types this command. Computer output would be enclosed in computeroutput tags, as in the following sample. grep snmptrap /etc/services snmptrap 162/udp snmp-trap # Traps for= SNMP Lines should be broken exactly as they are on-screen. Also, note that spaces inside screen ta= gs are automatically treated as non-breaking. Fill modes and <command>screen</command> tags Using automatic or manual fill commands in Emacs/PSGML will sometimes mangle screen sections. Use care when performing fill operations, and check the results.
Callout Example Line 1 Line 2 Line 3 Line 4 Here is a callout. The second callout.
--===============2712312104326950986==--