[documentation-guide] Adding old Documentation Guide
Eric Christensen
sparks at fedoraproject.org
Wed Jun 15 01:17:31 UTC 2011
commit caea01923a723cb9c998bea0c0c124c35cf41191
Author: Eric H Christensen <eric at christensenplace.us>
Date: Tue Jun 14 21:16:04 2011 -0400
Adding old Documentation Guide
old-documentation-guide/.cvsignore,v | 26 +
.../Attic/acknowledgments-en.xml,v | 220 +
.../Attic/acknowledgments-zh_CN.xml,v | 62 +
.../Attic/acknowledgments.xml,v | 75 +
.../Attic/docs-converting-en.xml,v | 63 +
.../Attic/docs-converting-zh_CN.xml,v | 51 +
.../Attic/docs-converting.xml,v | 60 +
old-documentation-guide/Attic/docs-emacs-en.xml,v | 787 +
.../Attic/docs-emacs-nxml-en.xml,v | 627 +
.../Attic/docs-emacs-nxml-zh_CN.xml,v | 160 +
.../Attic/docs-emacs-zh_CN.xml,v | 586 +
old-documentation-guide/Attic/docs-emacs.xml,v | 737 +
.../Attic/docs-getting-files-en.xml,v | 737 +
.../Attic/docs-getting-files-zh_CN.xml,v | 378 +
.../Attic/docs-getting-files.xml,v | 101 +
old-documentation-guide/Attic/docs-intro-en.xml,v | 120 +
.../Attic/docs-intro-zh_CN.xml,v | 77 +
old-documentation-guide/Attic/docs-intro.xml,v | 80 +
.../Attic/docs-rh-guidelines-en.xml,v | 647 +
.../Attic/docs-rh-guidelines-zh_CN.xml,v | 468 +
.../Attic/docs-rh-guidelines.xml,v | 426 +
old-documentation-guide/Attic/docs-style-en.xml,v | 5831 ++++
.../Attic/docs-style-zh_CN.xml,v | 1084 +
.../Attic/docs-tutorial-en.xml,v | 311 +
.../Attic/docs-tutorial-zh_CN.xml,v | 144 +
old-documentation-guide/Attic/docs-tutorial.xml,v | 138 +
old-documentation-guide/Attic/docs-vim-en.xml,v | 223 +
old-documentation-guide/Attic/docs-vim-zh_CN.xml,v | 140 +
.../Attic/docs-xml-tags-en.xml,v | 2953 ++
.../Attic/docs-xml-tags-zh_CN.xml,v | 1669 +
old-documentation-guide/Attic/docs-xml-tags.xml,v | 2510 ++
.../Attic/documentation-guide-en.xml,v | 605 +
.../Attic/documentation-guide-zh_CN.xml,v | 120 +
.../Attic/documentation-guide.xml,v | 135 +
old-documentation-guide/Makefile,v | 461 +
.../en_US/Attic/docs-emacs-nxml.xml,v | 377 +
.../en_US/Attic/docs-emacs.xml,v | 792 +
.../en_US/Attic/docs-getting-files.xml,v | 503 +
.../en_US/Attic/docs-intro.xml,v | 163 +
.../en_US/Attic/docs-module-struct.xml,v | 752 +
.../en_US/Attic/docs-rh-guidelines.xml,v | 1203 +
.../en_US/Attic/docs-style.xml,v | 2028 ++
.../en_US/Attic/docs-tutorial.xml,v | 165 +
old-documentation-guide/en_US/Attic/docs-vim.xml,v | 213 +
.../en_US/Attic/docs-xml-tags.xml,v | 2610 ++
old-documentation-guide/en_US/Attic/fdp-info.xml,v | 95 +
.../en_US/acknowledgments.xml,v | 190 +
.../en_US/documentation-guide.xml,v | 345 +
old-documentation-guide/en_US/emacs-nxml.xml,v | 416 +
old-documentation-guide/en_US/emacs.xml,v | 1519 +
old-documentation-guide/en_US/getting-files.xml,v | 476 +
old-documentation-guide/en_US/intro.xml,v | 148 +
old-documentation-guide/en_US/l10n.xml,v | 187 +
old-documentation-guide/en_US/module-struct.xml,v | 833 +
old-documentation-guide/en_US/publishing.xml,v | 311 +
old-documentation-guide/en_US/rpm-info.xml,v | 323 +
old-documentation-guide/en_US/style.xml,v | 2015 ++
old-documentation-guide/en_US/tutorial.xml,v | 277 +
old-documentation-guide/en_US/vim.xml,v | 222 +
.../en_US/writing-guidelines.xml,v | 1397 +
old-documentation-guide/en_US/xml-tags.xml,v | 3060 ++
old-documentation-guide/po/LINGUAS,v | 60 +
old-documentation-guide/po/de.po,v | 7971 +++++
.../po/documentation-guide.pot,v | 4962 +++
old-documentation-guide/po/it.po,v | 6464 ++++
old-documentation-guide/po/ms.po,v | 6552 ++++
old-documentation-guide/po/pt.po,v |35838 ++++++++++++++++++++
old-documentation-guide/po/pt_BR.po,v |11873 +++++++
old-documentation-guide/po/zh_CN.po,v |11106 ++++++
69 files changed, 128258 insertions(+), 0 deletions(-)
---
diff --git a/old-documentation-guide/.cvsignore,v b/old-documentation-guide/.cvsignore,v
new file mode 100644
index 0000000..90e4a5b
--- /dev/null
+++ b/old-documentation-guide/.cvsignore,v
@@ -0,0 +1,26 @@
+head 1.1;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.1
+ LIVE:1.1;
+locks; strict;
+comment @# @;
+
+
+1.1
+date 2005.05.15.17.04.35; author jtr; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.1
+log
+ at Ignorables
+@
+text
+ at documentation-guide-en
+@
diff --git a/old-documentation-guide/Attic/acknowledgments-en.xml,v b/old-documentation-guide/Attic/acknowledgments-en.xml,v
new file mode 100644
index 0000000..7b30330
--- /dev/null
+++ b/old-documentation-guide/Attic/acknowledgments-en.xml,v
@@ -0,0 +1,220 @@
+head 1.10;
+access;
+symbols
+ LIVE:1.7
+ VERSION-0_2:1.3;
+locks; strict;
+comment @# @;
+
+
+1.10
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.9;
+
+1.9
+date 2005.12.13.21.56.24; author jtr; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2004.09.13.02.14.06; author tfox; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2004.08.31.17.26.50; author tfox; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2004.08.31.15.45.29; author tfox; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2004.03.18.21.18.35; author tfox; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2004.03.18.20.25.02; author tfox; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2004.01.19.23.14.46; author tfox; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2003.11.10.15.12.15; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.10.15.18.11.01; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.10
+log
+ at Remove old files in en locale
+@
+text
+@ <chapter id="acknowledgments">
+ <title>Acknowledgments</title>
+
+ <para>
+ This document is based on the a document started by Tammy Fox (tfox at
+ redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and
+ Johnray Fuller (jrfuller at redhat.com).
+ </para>
+
+ <para>
+ A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to
+ fix a few typos and explain that anonymous CVS access does not allow
+ commits.
+ </para>
+
+ <para>
+ Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied
+ to add the trailing slashes to the <command>figure</command> tag example
+ in <filename>docs-xml-tags.xml</filename> and to add <xref
+ linkend="ch-emacs-nxml"></xref>.
+ </para>
+
+ <para>
+ A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been
+ applied to add <xref linkend="ch-vim"></xref>.
+ </para>
+
+ <para>
+ A patch from Karsten Wade (kwade at redhat.com) has been applied to add
+ <xref linkend="s1-screenshots"></xref>. It was edited by Paul
+ W. Frields (stickstr5 at hotmail.com).
+ </para>
+
+ <para>
+ A patch from Paul W. Frields (stickstr5 at hotmail.com) has been applied
+ to add more explanation of the <command>screen</command> tag set to <xref
+ linkend="s1-xml-tags-screen"></xref>.
+ </para>
+
+ <para>
+ A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been
+ applied to more fully explaing the document building system.
+ </para>
+
+ </chapter>
+@
+
+
+1.9
+log
+ at Added documentation about the document building system. Dropped the
+one-line "converting" chapter by creating a "Prerequisites" section
+in the "getting-files" section.
+@
+text
+@@
+
+
+1.8
+log
+ at add ack of Paul's patch
+@
+text
+ at d40 5
+@
+
+
+1.7
+log
+ at fix name
+@
+text
+ at d17 4
+a20 8
+ A patch from Gavin Henry (ghenry at suretecsystems.com) has been applied to
+ <filename>docs-xml-tags.xml</filename> to add the trailing slashes to the
+ figure tag example.
+ </para>
+
+ <para>
+ A patch from Gavin Henry (ghenry at suretecsystems.com) has been applied to
+ add <xref linkend="ch-emacs-nxml"></xref>.
+d33 6
+@
+
+
+1.6
+log
+ at add instructions for screenshots
+@
+text
+ at d35 1
+a35 1
+ W. Friends (stickstr5 at hotmail.com).
+@
+
+
+1.5
+log
+ at forgot ()
+@
+text
+ at d24 1
+a24 1
+ add the <xref linkend="ch-emacs-nxml"></xref>.
+d29 1
+a29 1
+ applied to add the <xref linkend="ch-vim"></xref>.
+d31 6
+@
+
+
+1.4
+log
+ at add chapter on VIM
+@
+text
+ at d28 1
+a28 1
+ A patch from Joshua Daniel Franklin joshuadfranklin at yahoo.com has been
+@
+
+
+1.3
+log
+ at add Gavin's patch for nxml
+@
+text
+ at d27 5
+@
+
+
+1.2
+log
+ at change gavin's email address per his request
+@
+text
+ at d22 5
+@
+
+
+1.1
+log
+ at fix example figure tag, add ack chapter
+@
+text
+ at d17 1
+a17 1
+ A patch from Gavin Henry (gavin.henry at magicfx.co.uk) has been applied to
+@
+
diff --git a/old-documentation-guide/Attic/acknowledgments-zh_CN.xml,v b/old-documentation-guide/Attic/acknowledgments-zh_CN.xml,v
new file mode 100644
index 0000000..d1023c3
--- /dev/null
+++ b/old-documentation-guide/Attic/acknowledgments-zh_CN.xml,v
@@ -0,0 +1,62 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.17.13.28.38; author bbbush; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<chapter id="acknowledgments">
+ <title>致谢</title>
+ <para>本文档基于 Tammy Fox (tfox at redhat.com) 起草的一篇文档，并得到了 Sandra Moore (smoore at redhat.com) 和 Johnray Fuller (jrfuller at redhat.com) 的协助。</para>
+ <para>Roozbeh Pournader (roozbeh at sharif.edu) 的补丁已被合并，修正了一些拼写错误，解释了匿名 CVS 访问时禁止提交的情况。</para>
+ <para>Gavin Henry (ghenry at suretecsystems.com) 的补丁已被合并，向 <filename>docs-xml-tags.xml</filename> 中的 <command>figure</command> 标记范例添加尾部斜线，以及添加 <xref linkend="ch-emacs-nxml"/>。</para>
+ <para>Joshua Daniel Franklin (joshuadfranklin at yahoo.com) 的补丁已被合并，添加 <xref linkend="ch-vim"/>。</para>
+ <para>Karsten Wade (kwade at redhat.com) 的补丁已被合并，添加 <xref linkend="s1-screenshots"/>。它为 Paul W. Frields (stickstr5 at hotmail.com) 编辑。</para>
+ <para>Paul W. Frields (stickstr5 at hotmail.com) 的补丁已被合并，向 <xref linkend="s1-xml-tags-screen"/> 中的 <command>screen</command> 标记集合添加更多解释。</para>
+ <para>合并了 Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) 的补丁，详细解释文档构建系统。</para>
+</chapter>
+@
+
+
+1.2
+log
+ at update build part
+@
+text
+@@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+ at d10 1
+@
+
diff --git a/old-documentation-guide/Attic/acknowledgments.xml,v b/old-documentation-guide/Attic/acknowledgments.xml,v
new file mode 100644
index 0000000..b3fdb8b
--- /dev/null
+++ b/old-documentation-guide/Attic/acknowledgments.xml,v
@@ -0,0 +1,75 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2004.01.19.23.11.26; author tfox; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2003.11.10.15.12.15; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.10.15.18.11.01; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at renamed with -en
+@
+text
+@ <chapter id="acknowledgments">
+ <title>Acknowledgments</title>
+
+ <para>
+ This document is based on the a document started by Tammy Fox (tfox at
+ redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and
+ Johnray Fuller (jrfuller at redhat.com).
+ </para>
+
+ <para>
+ A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to
+ fix a few typos and explain that anonymous CVS access does not allow
+ commits.
+ </para>
+
+ <para>
+ A patch from Gavin Henry (ghenry at suretecsystems.com) has been applied to
+ <filename>docs-xml-tags.xml</filename> to add the trailing slashes to the
+ figure tag example.
+ </para>
+
+ </chapter>
+@
+
+
+1.2
+log
+ at change gavin's email address per his request
+@
+text
+@@
+
+
+1.1
+log
+ at fix example figure tag, add ack chapter
+@
+text
+ at d17 1
+a17 1
+ A patch from Gavin Henry (gavin.henry at magicfx.co.uk) has been applied to
+@
+
diff --git a/old-documentation-guide/Attic/docs-converting-en.xml,v b/old-documentation-guide/Attic/docs-converting-en.xml,v
new file mode 100644
index 0000000..c7d58d8
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-converting-en.xml,v
@@ -0,0 +1,63 @@
+head 1.2;
+access;
+symbols
+ VERSION-0_2:1.1;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2005.12.13.21.56.24; author jtr; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at Added documentation about the document building system. Dropped the
+one-line "converting" chapter by creating a "Prerequisites" section
+in the "getting-files" section.
+@
+text
+@<!-- $Id: docs-converting-en.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+
+<chapter id="ch-converting">
+ <title>Converting to HTML and PDF</title>
+
+ <para>
+ Each directory containing a document also has a Makefile. In the directory,
+ run the command <command>make html</command> to build the HTML version and
+ <command>make pdf</command> to build the PDF version.
+ </para>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ The PDF production is somewhat fragile right now. It may or may not
+ work.
+ </para>
+ </warning>
+
+</chapter>
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-converting.xml,v 1.2 2003/07/18 01:11:23 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/Attic/docs-converting-zh_CN.xml,v b/old-documentation-guide/Attic/docs-converting-zh_CN.xml,v
new file mode 100644
index 0000000..f66c5b8
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-converting-zh_CN.xml,v
@@ -0,0 +1,51 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2005.12.13.21.56.24; author jtr; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at Added documentation about the document building system. Dropped the
+one-line "converting" chapter by creating a "Prerequisites" section
+in the "getting-files" section.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id: docs-converting-zh_CN.xml,v 1.1 2005/12/09 15:28:54 bbbush Exp $ --><chapter id="ch-converting">
+ <title>生成 HTML 及 PDF</title>
+ <para>每个包含文档的目录都有一个 Makefile。在这个目录下，运行命令 <command>make html</command> 来生成 HTML 版本，运行 <command>make pdf</command> 来生成 PDF 版本。</para>
+ <warning>
+ <title>警告</title>
+ <para>PDF 的生成仍然不完善，可能无法工作。</para>
+ </warning>
+</chapter>
+@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: docs-converting-en.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ --><chapter id="ch-converting">
+@
+
diff --git a/old-documentation-guide/Attic/docs-converting.xml,v b/old-documentation-guide/Attic/docs-converting.xml,v
new file mode 100644
index 0000000..6bb5357
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-converting.xml,v
@@ -0,0 +1,60 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2003.11.21.22.40.39; author tfox; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at change filenames to end with -en.xml
+@
+text
+@<!-- $Id: docs-converting.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+
+<chapter id="ch-converting">
+ <title>Converting to HTML and PDF</title>
+
+ <para>
+ Each directory containing a document also has a Makefile. In the directory,
+ run the command <command>make html</command> to build the HTML version and
+ <command>make pdf</command> to build the PDF version.
+ </para>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ The PDF production is somewhat fragile right now. It may or may not
+ work.
+ </para>
+ </warning>
+
+</chapter>
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-converting.xml,v 1.2 2003/07/18 01:11:23 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/Attic/docs-emacs-en.xml,v b/old-documentation-guide/Attic/docs-emacs-en.xml,v
new file mode 100644
index 0000000..0505d40
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-emacs-en.xml,v
@@ -0,0 +1,787 @@
+head 1.3;
+access;
+symbols
+ VERSION-0_2:1.1;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2004.08.13.15.35.41; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old files in en locale
+@
+text
+@<!-- $Id: docs-emacs-en.xml,v 1.2 2004/08/13 15:35:41 tfox Exp $ -->
+
+ <chapter id="ch-emacs">
+ <title>Emacs and PSGML Mode</title>
+
+ <indexterm>
+ <primary>PSGML</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>PSGML mode</secondary>
+ </indexterm>
+
+ <para>
+ You can use the PSGML mode available for Emacs to make it easier to write
+ in XML format. PSGML mode provides syntax-highlighting, tag completion,
+ and more.
+ </para>
+
+ <sect1 id="s1-emacs-file">
+ <title>Setting Up Your <filename>.emacs</filename> File</title>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>configuration file</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.emacs</filename></primary>
+ </indexterm>
+
+ <para>
+ For Emacs to parse your DocBook documents correctly, you must have a
+ <filename>.emacs</filename> file. Cut and paste the following into your
+ existing <filename>.emacs</filename> file or create a new one that
+ contains the following lines:
+
+<screen>
+<computeroutput>
+;; turn on auto-fill in `text-mode' and derived modes
+;;(mail, news, etc)
+(add-hook 'text-mode-hook 'turn-on-auto-fill)
+
+;;
+;;MODES
+;;
+
+(setq auto-mode-alist (cons '("\\.sgml$" . sgml-mode) auto-mode-alist))
+(setq auto-mode-alist (cons '("\\.sgm$" . sgml-mode) auto-mode-alist))
+
+;;
+;;XML!!
+;;
+;;#############################################################
+
+;;
+;;PSGML mode stuff
+;;
+
+(autoload 'sgml-mode "psgml" "My Most Major Mode" t)
+
+(setq sgml-mode-hook '(lambda () "Defaults for XML mode." (turn-on-auto-fill)
+(setq fill-column 80)))
+
+(defun My-XML-keymap ()
+ (local-set-key [(alt i)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt l)]
+ '(lambda ()
+ (interactive)
+ (sgml-insert-element 'list)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt p)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'para)
+ (sgml-indent-line)))
+ (local-set-key [(alt -)]
+ '(lambda ()
+ (interactive)
+ (insert "—"))))
+
+(add-hook 'sgml-mode-hook 'My-XML-keymap)
+
+;;
+;; Fix up indentation of data...
+;;
+
+(setq-default sgml-indent-data t)
+
+;;
+;; XML markup faces.
+;;
+
+(setq-default sgml-set-face t)
+
+
+(make-face 'sgml-comment-face)
+(make-face 'sgml-doctype-face)
+(make-face 'sgml-end-tag-face)
+(make-face 'sgml-entity-face)
+(make-face 'sgml-ignored-face)
+(make-face 'sgml-ms-end-face)
+(make-face 'sgml-ms-start-face)
+(make-face 'sgml-pi-face)
+(make-face 'sgml-sgml-face)
+(make-face 'sgml-short-ref-face)
+(make-face 'sgml-start-tag-face)
+
+(set-face-foreground 'sgml-comment-face "maroon")
+(set-face-foreground 'sgml-doctype-face "dark green")
+(set-face-foreground 'sgml-end-tag-face "blue2")
+(set-face-foreground 'sgml-entity-face "red2")
+(set-face-foreground 'sgml-ignored-face "maroon")
+(set-face-background 'sgml-ignored-face "gray90")
+(set-face-foreground 'sgml-ms-end-face "maroon")
+(set-face-foreground 'sgml-ms-start-face "maroon")
+(set-face-foreground 'sgml-pi-face "maroon")
+(set-face-foreground 'sgml-sgml-face "maroon")
+(set-face-foreground 'sgml-short-ref-face "goldenrod")
+(set-face-foreground 'sgml-start-tag-face "blue2")
+
+(setq-default sgml-markup-faces
+ '((comment . sgml-comment-face)
+ (doctype . sgml-doctype-face)
+ (end-tag . sgml-end-tag-face)
+ (entity . sgml-entity-face)
+ (ignored . sgml-ignored-face)
+ (ms-end . sgml-ms-end-face)
+ (ms-start . sgml-ms-start-face)
+ (pi . sgml-pi-face)
+ (sgml . sgml-sgml-face)
+ (short-ref . sgml-short-ref-face)
+ (start-tag . sgml-start-tag-face)))
+
+
+(defun docbook-mode ()
+ (sgml-mode)
+ )
+
+
+
+;;
+;;END XML STUFF
+;;
+;;##################################################################
+
+;PO mode stuff
+
+(setq auto-mode-alist
+ (cons '("\\.pox?\\'" . po-mode) auto-mode-alist))
+(autoload 'po-mode "po-mode")
+
+
+ (global-set-key [(f1)] (lambda () (interactive) (manual-
+ entry (current-word))))
+
+</computeroutput>
+</screen>
+
+ </para>
+
+ <para>
+ Do you have a cool wheel mouse? If so, you can add the following to your
+ <filename>.emacs</filename> file so your wheel will work in
+ <application>Emacs</application> (must be
+ <application>Emacs</application> version 21):
+ </para>
+
+<screen>
+<computeroutput>
+;; Enable wheelmouse support by default for emacs 21
+(cond (window-system
+(mwheel-install)
+))
+</computeroutput>
+</screen>
+
+ <para>
+ If you are using the older version 20 of
+ <application>Emacs</application>, add the following instead:
+ </para>
+
+<screen>
+<computeroutput>
+;; Enable wheelmouse support by default
+(require 'mwheel)
+</computeroutput>
+</screen>
+
+<!-- bug #125757 in NEEDINFO state
+ <para>
+ If you have a mouse, you can also add the following. It adds popup menus
+ when the cursor is either on a start tag or in a region where elements
+ are allowed.
+ </para>
+
+<screen>
+<computeroutput>
+;; Mouse Bindings: right-click to generate context-aware
+;; elements/attributes popup menu.
+(define-key sgml-mode-map [mouse-3] 'sgml-tags-menu)
+</computeroutput>
+</screen>
+
+-->
+
+ </sect1>
+
+
+ <sect1 id="s1-emacs-colors">
+ <title>Customizing Emacs</title>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>customizing</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.Xresources</filename></primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>colors</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>font</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>geometry</secondary>
+ </indexterm>
+
+ <para>
+ The colors, font, and geometry (default size of window) for Emacs in your
+ <filename>~/.Xresources</filename> file. The format for the settings is
+ <computeroutput>emacs.keyword:value</computeroutput>
+ </para>
+
+ <para>
+ The following is a sample <filename>~/.Xresources</filename> file.
+ </para>
+ <note>
+ <title>Note</title>
+ <para>If you have other settings in your
+ <filename>~/.Xresources</filename>, add the following to the end of
+ the file.
+ </para>
+ </note>
+
+<screen>
+<userinput>
+emacs.background: light gray
+emacs.foreground: black
+emacs.pointerColor: blue
+emacs.cursorColor: blue
+emacs.bitmapIcon: on
+emacs.font: fixed
+emacs.geometry: 90x25
+</userinput>
+</screen>
+ <para>
+ After modifying this file, you must execute the command
+ </para>
+<screen>
+<command>xrdb -merge ~/.Xresources</command>
+</screen>
+ <para>
+ and restart <application>Emacs</application> for the changes to take
+ place.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-cedfile">
+ <title>Create Recompiled DTD Subset</title>
+
+ <para>
+ Emacs will perform syntax highlighting and indent correctly on
+ DocBook XML files if you provide it with the proper Document Type
+ Declarations (DTD) file. These two features will make your XML file
+ look pretty and help you spot errors.
+ </para>
+
+ <para>
+ To create a loadable Parsed DTD file:
+ <orderedlist>
+ <listitem>
+ <para>Find the parent file for the group of DocBook files. You will
+ recognize this file by the header <filename><!DOCTYPE article
+ PUBLIC "-//OASIS//DTD DocBook V4.1//EN"</filename>. An easy way
+ to find this parent file is to use the command <command>grep
+ DocBook *.xml</command>. Once you find the parent file, open it
+ in Emacs with the command <command>emacs
+ <replaceable><parentfile></replaceable>.xml</command> (where
+ <replaceable><parentfile></replaceable>.xml is the parent
+ file you found.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Choose <command>DTD -> Parse DTD</command> from the pulldown
+ menu.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>You will know the parsing is finished when you see the message
+ <computeroutput>Fontifying...done</computeroutput> at the bottom
+ of your screen. Save the parsed DTD to a file by choosing
+ <command>DTD -> Save Parsed DTD</command> from the pulldown menu.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Press <keycap>Enter</keycap> to save the file to the default
+ filename or rename the file keeping the <filename>.ced</filename>
+ extension. It can be useful to name it something generic such as
+ <filename>docbook.ced</filename> so you can refer to it when
+ opening all DocBook files. This file can also be copied from
+ directory to directory to be loaded.
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </para>
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ You can also use the Emacs command <command>Meta-x
+ sgml-parse-prolog</command> to parse the file, and then use the
+ command <command>Meta-x sgml-save-dtd</command> to save the parsed DTD
+ to a <filename>.ced</filename> file.
+ </para>
+ </tip>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-loadced">
+ <title>Load the Parsed DTD</title>
+
+ <para>
+ Now that you have saved the DTD settings, you can load the
+ <filename>.ced</filename> file and see the syntax highlighting for your
+ <filename>.sgml</filename> files.
+ </para>
+
+ <para>
+ To load a parsed DTD file:
+ <orderedlist>
+ <listitem>
+ <para>Open an XML file in Emacs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Choose <command>DTD -> Load DTD</command> from the pulldown menu
+ and choose the file you saved from the previous step. For
+ instance, choose <filename>docbook.ced</filename>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>You will know it is finished when you see the message
+ <computeroutput>Fontifying...done</computeroutput> at the bottom
+ of your screen. Loading the parsed DTD might take a long time.
+ You can start editing the file before it finishes.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ You can also use the Emacs command <command>Meta-x
+ sgml-load-dtd</command> to load the parsed DTD.
+ </para>
+ </tip>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-basic-commands">
+ <title>Basic Emacs Commands</title>
+
+ <para>
+ The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key.
+ </para>
+
+ <table frame="all" rowsep="1" colsep="1" id="tb-emacs-commands">
+ <title>Emacs Commands</title>
+ <tgroup rowsep="1" colsep="1" cols="2">
+ <colspec colnum="1" colname="shortcut" colwidth="170"/>
+ <colspec colnum="2" colname="description" colwidth="300"/>
+
+ <thead>
+ <row>
+ <entry rowsep="1" colsep="1">Shortcut</entry>
+ <entry rowsep="1" colsep="1">Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry rowsep="1" colsep="1"><keycombo>
+ <keycap>Meta</keycap><keycap>x</keycap></keycombo>
+ sgml-parse-prolog, <keycap>Enter</keycap></entry>
+ <entry>Parse DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-save-dtd, <keycap>Enter</keycap></entry>
+ <entry>Save the Parse DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo> <keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-load-dtd, <keycap>Enter</keycap></entry>
+ <entry>Load DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo> <keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap></keycap></keycombo>, <keycap>Tab</keycap></entry>
+ <entry>Display list of valid tags</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap></keycap> </keycombo>, type beginning of tag,
+ <keycap>Tab</keycap></entry>
+ <entry>Complete the tag</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>g</keycap>
+ </keycombo></entry>
+ <entry>Cancel a command in the minibuffer</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycap>/</keycap></entry>
+ <entry>Close tag</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>a</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to beginning of line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>e</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the end of the line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>Home</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the beginning of the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>End</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the end of the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>k</keycap>
+ </keycombo></entry>
+ <entry>Cut line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>y</keycap>
+ </keycombo></entry>
+ <entry>Paste line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>s</keycap>
+ </keycombo></entry>
+ <entry>Search forward in the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>r</keycap>
+ </keycombo></entry>
+ <entry>Search backwards in the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>$</keycap>
+ </keycombo></entry>
+ <entry>Check spelling of current word</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-word, <keycap>Enter</keycap></entry>
+ <entry>Check spelling of current word</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-buffer, <keycap>Enter</keycap></entry>
+ <entry>Check spelling of current buffer</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap>
+ </keycombo></entry>
+ <entry>Open file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap>
+ </keycombo></entry>
+ <entry>Save file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></entry>
+ <entry>Exit <application>Emacs</application> and prompt to save
+ files if necessary</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap> <keycap>q</keycap>
+ </keycombo></entry>
+ <entry>Fill paragraph</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>a</keycap>
+ </keycombo></entry>
+ <entry>Edit attributes for a tag (for example, you can edit the
+ <computeroutput>url</computeroutput> attribute of the
+ <computeroutput>ulink</computeroutput> tag)</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>,
+ <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></entry>
+ <entry>Exit edit attributes</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-examples">
+ <title>Examples</title>
+
+ <para>
+ The table or reference card of Emacs and PSGML commands can be confusing
+ for beginners. This section provides some examples of how to use them.
+ </para>
+
+ <sect2 id="s2-emacs-tag-completion">
+ <title>Tag Completion</title>
+
+ <note>
+ <title>Note</title>
+ <para>This section assumes that you have already loaded the DTD file
+ (<filename>.ced</filename>).
+ </para>
+ </note>
+
+ <para>
+ Instead of typing a tag each time you need to use it, use
+ the key combination <keycap>Ctrl</keycap>-<keycap>c</keycap>,
+ followed by <keycap><</keycap>. At the bottom of the
+ <application>Emacs</application> window, you will see:
+ </para>
+<screen>
+<computeroutput>Tag: <</computeroutput>
+</screen>
+
+ <para>
+ To view a list of available tags, use either the <keycap>Tab</keycap>
+ or <keycap>?</keycap>. Or, if you know the first few letters of a tag,
+ you can enter them followed by <keycap>Tab</keycap> for a complete
+ list of available tags beginning with those letters or for a tag
+ completion.
+ </para>
+
+ <para>
+ Try the following: Type <keycap>Ctrl</keycap>-<keycap>c</keycap>
+ followed by <keycap><</keycap>. Then enter the letter
+ <keycap>k</keycap>, followed by <keycap>Tab</keycap>. You may have to
+ use the <keycap>Tab</keycap> key several times to get a complete list.
+ </para>
+
+ <para>
+ The output should look similar to the example below:
+ </para>
+
+<screen>
+<computeroutput>
+Click mouse-2 on a completion to select it.
+In this buffer, type RET to select the completion near point.
+
+Possible completions are:
+<keycap> <keycode>
+<keycombo> <keysym>
+</computeroutput>
+</screen>
+
+ </sect2>
+ <sect2 id="s2-emacs-tag-closing">
+ <title>Tag Closure</title>
+
+ <para>
+ Once you have started the tag of choice, you must close it. The easiest
+ way to close an open tag is to use the keycombo
+ <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by
+ <keycap>/</keycap>. This will close the closest open tag you have.
+ </para>
+
+ </sect2>
+
+ <sect2 id="s2-emacs-other">
+ <title>Other Emacs Tasks</title>
+
+ <para>
+ <guilabel>Working with one window</guilabel>: Sometimes in
+ <application>Emacs</application> the window becomes split (with tags
+ completions or other text in the bottom window). The easiest way to
+ get it back so that only your XML and text appear on one screen is to
+ use the keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap>, followed by
+ <keycap>1</keycap>.
+ </para>
+
+ <para>
+ <guilabel>Saving your work</guilabel>: To save your work, use the
+ following keycombo, <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>s</keycap>.
+ </para>
+
+ <para>
+ <guilabel>The "clear/quit" command</guilabel>: I have found on some
+ occasions that I have gotten too far into the tag completion process and
+ need to just exit back out to my text. The easiest way to do this is the
+ keycombo <keycap>Ctrl</keycap>-<keycap>g</keycap>. This command quits
+ what you have been doing within the file, without quitting the file
+ itself.
+ </para>
+
+ <para>
+ <guilabel>Opening a new file</guilabel>: To open a new file, use the
+ keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>f</keycap>. At the bottom of the emacs
+ window, you will be able to enter in the file name (using
+ <keycap>Tab</keycap> completion if needed) of the file you wish to
+ open.
+ </para>
+
+ <para>
+ <guilabel>Closing emacs</guilabel>: The easiest way to close
+ <application>emacs</application> is to use the keycombo
+ <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>c</keycap>. If you have not saved your work,
+ it will prompt you to save the file, otherwise it will just quit the
+ current emacs session you have been working with.
+ </para>
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-additional-resources">
+ <title>Additional Resources</title>
+
+ <para> Additional Emacs and PSGML references are available at the
+ following locations:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink>
+ — <citetitle>Emacs Quick Reference Guide</citetitle>
+ </para>
+ </listitem>
+ <listitem> <para>Emacs reference card that comes with the
+ <filename>emacs</filename> package. You can print it out as a
+ reference. —
+ <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Read <citetitle>Editing XML with Emacs and PSGML</citetitle>
+ in <filename>/usr/share/doc/psgml-<replaceable><version></replaceable>/psgml.ps</filename>. </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://www.snee.com/bob/sgmlfree/psgmqref.html">http://www.snee.com/bob/sgmlfree/psgmqref.html</ulink>
+ — <citetitle>Emacs/PSGML Quick Reference</citetitle> is a
+ reference table of Emacs commands for PSGML mode.
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://www.snee.com/bob/sgmlfree/emcspsgm.html">http://www.snee.com/bob/sgmlfree/emcspsgm.html</ulink>
+ — <citetitle>PSGML Tricks</citetitle></para>
+ </listitem>
+ </itemizedlist>
+
+ </sect1>
+ </chapter>
+
+
+
+
+
+
+
+
+
+@
+
+
+1.2
+log
+ at add psgml links per bug #125757
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-emacs-en.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-emacs.xml,v 1.4 2003/09/16 19:26:26 tfox Exp $ -->
+d194 1
+d202 17
+d702 12
+@
+
diff --git a/old-documentation-guide/Attic/docs-emacs-nxml-en.xml,v b/old-documentation-guide/Attic/docs-emacs-nxml-en.xml,v
new file mode 100644
index 0000000..4f1affd
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-emacs-nxml-en.xml,v
@@ -0,0 +1,627 @@
+head 1.5;
+access;
+symbols
+ VERSION-0_2:1.2;
+locks; strict;
+comment @# @;
+
+
+1.5
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.4;
+
+1.4
+date 2004.08.13.15.39.46; author tfox; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2004.08.13.01.00.25; author tfox; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2004.01.20.15.02.28; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2004.01.19.23.14.46; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.5
+log
+ at Remove old files in en locale
+@
+text
+@ <chapter id="ch-emacs-nxml">
+ <title>Emacs and nXML Mode</title>
+
+ <indexterm>
+ <primary>nXML</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>nXML mode</secondary>
+ </indexterm>
+
+ <para>
+ You can also use the nXML mode available for
+ <application>Emacs</application> to make it even easier to write in
+ DocBook XML format. nXML mode provides context-sensitive editing using
+ completion, real time validity error checking, syntax highlighting and
+ indentation. All you need to do is install an RPM!!
+ </para>
+
+ <note>
+ <title>Early stages</title>
+ <para>
+ Please be aware the nxml-mode for <application>Emacs</application> is
+ quite new, so there are a few things that the advanced user might notice
+ when using it with other documents types. If you keep an eye on the
+ mailing-list, you can keep up to date with these, as well as ask
+ questions. For more details, check out <xref
+ linkend="s1-emacs-nxml-readme"></xref>.
+ </para>
+ </note>
+
+
+ <sect1 id="s1-nxml-rpm">
+ <title>Getting the nXML RPM</title>
+
+ <indexterm>
+ <primary>nXML</primary>
+ <secondary>RPM</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>nXML RPM</primary>
+ </indexterm>
+
+ <para>
+ To use nXML mode with emacs, you will need to install the nXML RPM
+ available from <ulink
+ url="http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/">Tim
+ Waugh's</ulink> website or the source from <ulink
+ url="http://www.thaiopensource.com/download/">http://www.thaiopensource.com/download/</ulink>. The
+ source requires a lot more work to setup, therefore we will only be
+ concentrating on the RPM version.
+ </para>
+
+ <para>
+ Information on where to get the source is available in <xref
+ linkend="s1-emacs-additional-resources"></xref>.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-nxml-examples">
+ <title>Examples</title>
+
+ <para>
+ Compared to PSGML mode there are only couple of commands that you
+ need. This speeds up writing with <application>Emacs</application>
+ considerably, which means you can concentrate more on the content of
+ your article.
+ </para>
+
+ <sect2 id="s2-nxml-commands">
+ <title>Commands</title>
+
+ <para>
+ To create a tag, type <userinput><</userinput> and then type the
+ keyword. To complete the keyword, press <command>Ctrl-Ret</command>,
+ then add the last <userinput>></userinput>. To close a tag, type
+ <userinput></</userinput>.
+ </para>
+
+ <important>
+ <title>Important</title>
+ <para>
+ When you open a document that doesn't have a DOCTYPE declaration at
+ the top of the file, you will get this message and tag completion
+ won't work because nXML will not know what format you are writing.
+ </para>
+ </important>
+
+ <para>
+ To load the schema, type <command>Ctrl-c</command>, then
+ <command>Ctrl-s</command> and navigate to
+ <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> and
+ load
+ <filename>docbook.rnc</filename>. <application>Emacs</application>
+ will then prompt you to save it in the current working directory.
+ </para>
+
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ The commands already discussed are the only differences between
+ using <application>Emacs</application> with PSGML mode and
+ <application>Emacs</application> with nXML mode. You will still need
+ to use all the same commands as discussed in <xref
+ linkend="s1-emacs-basic-commands"></xref>.
+ </para>
+ </tip>
+ </sect2>
+ </sect1>
+
+ <sect1 id="s1-emacs-nxml-additional-resources">
+ <title>Additional Resources</title>
+
+ <para>
+ Additional Emacs and nXML references are available at the following
+ locations:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://www.thaiopensource.com/download/">http://www.thaiopensource.com/download/</ulink>
+ — <citetitle>Author's download area</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink>
+ — <citetitle>Emacs Quick Reference Guide</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Emacs reference card that comes with the
+ <filename>emacs</filename> package. You can print it out as a
+ reference. —
+ <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </sect1>
+
+ <sect1 id="s1-emacs-nxml-readme">
+ <title>nXML README File</title>
+
+ <note>
+ <title>Note</title>
+ <para>
+ This file can be found in the directory you extracted the source
+ into, or in
+ <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename>
+ if you installed the RPM.
+ </para>
+ </note>
+
+ <para>README file:</para>
+
+ <para>
+ This is a new major mode for GNU Emacs for editing XML documents. It
+ supports editing well-formed XML documents and also provides
+ schema-sensitive editing of XML documents using RELAX NG Compact
+ Syntax.
+ </para>
+
+ <para>
+ To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU
+ Emacs version 20 will not work properly, nor will XEmacs.
+ To get started, do the following:
+ </para>
+
+<screen>
+<command>M-x load-file RET rng-auto.el RET</command>
+</screen>
+
+ <para>
+ This defines the necessary autoloads. Now, visit a file containing
+ an XML document, and do the following:
+ </para>
+
+<screen>
+<command>M-x nxml-mode</command>
+</screen>
+
+ <para>
+ Now do
+ </para>
+
+<screen>
+<command>C-h m</command>
+</screen>
+
+ <para>
+ For information on how to use nxml-mode. The beginnings of a manual are
+ in nxml-mode.info. You can read this using:
+ </para>
+
+<screen>
+<command>C-u M-x info RET nxml-mode.info RET</command>
+</screen>
+
+ <para>
+ It's also installed as an entry at the end of the top-level info
+ directory. So you can read it with <command>C-h i</command> as usual.
+ </para>
+
+ <para>
+ You can use <filename>test.valid.xml</filename> and
+ <filename>test.invalid.xml</filename> as examples of valid and invalid
+ XML documents.
+ </para>
+
+ <para>
+ To get things automatically loaded each time you start Emacs, add:
+ </para>
+
+<screen>
+<computeroutput>
+(load "~/nxml-mode-200YMMDD/rng-auto.el")
+</computeroutput>
+</screen>
+
+ <para>
+ to your <filename>.emacs</filename>, where
+ <computeroutput>~/nxml-mode-200YMMDD</computeroutput> is the directory
+ containing the <filename>.elc</filename> files. Note that
+ <filename>rng-auto.el</filename> does not load all of the nxml-mode
+ code; it merely sets things up so that all the features of nxml-mode
+ will be autoloaded properly. You should not try to autoload
+ <filename>rng-auto.el</filename> itself.
+ </para>
+
+ <para>
+ To use nxml-mode automatically for files with an extension of
+ <filename>xml</filename>, <filename>xsl</filename>,
+ <filename>rng</filename> or <filename>xhtml</filename>, add the
+ following to your <filename>.emacs</filename> file:
+ </para>
+
+<screen>
+<computeroutput>
+(setq auto-mode-alist
+ (cons '("\\.\\(xml\\|xsl\\|rng\\|xhtml\\)\\'" . nxml-mode)
+ auto-mode-alist))
+</computeroutput>
+</screen>
+
+ <para>
+ If you edit XML using iso-8859-N encodings other than iso-8859-1 and you
+ are running Emacs 21.3 or later, then I recommend enabling
+ unify-8859-on-decoding-mode, by adding the following to your
+ <filename>.emacs</filename> file:
+ </para>
+
+<screen>
+<computeroutput>(unify-8859-on-decoding-mode)</computeroutput>
+</screen>
+
+ <para>
+ To get validation and schema-sensitive editing, you need a RELAX NG
+ Compact Syntax (RNC) schema for you document. The schema directory
+ includes some schemas for popular document types.
+ </para>
+
+ <para>
+ For more on RELAX NG, refer to <ulink
+ url="http://relaxng.org/">http://relaxng.org/</ulink>.
+ </para>
+
+ <para>
+ For a tutorial on RELAX NG Compact Syntax, refer to <ulink
+ url="http://relaxng.org/compact-tutorial.html">http://relaxng.org/compact-tutorial.html</ulink>
+ </para>
+
+ <para>
+ For automatically creating RNC schemas, I recommend my Trang program:
+ <ulink
+ url="http://www.thaiopensource.com/relaxng/trang.html">http://eee.thaiopensource.com/relaxng/trang.html"</ulink>
+ </para>
+
+ <para>
+ You can use this to
+
+<itemizedlist>
+ <listitem>
+ <para>
+ Infer an RNC schema from an instance document
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Convert a DTD to an RNC schema
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Convert a RELAX NG XML syntax schema to an RNC schema
+ </para>
+ </listitem>
+</itemizedlist>
+ </para>
+
+ <para>
+ To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can
+ also use the XSLT stylesheet from <ulink
+ url="http://www.pantor.com/download.html">http://www.pantor.com/download.html"</ulink>.
+ </para>
+
+ <para>
+ To convert a W3C XML Schema to an RNC schema, you need first to convert
+ it to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv
+ (built on top of MSV). Refer to <ulink
+ url="https://msv.dev.java.net/">https://www.dev.java.net/</ulink>.
+ </para>
+
+ <para>
+ The file <filename>NEWS</filename> describes recent changes.
+ </para>
+
+ <para>
+ Please use the list <ulink
+ url="http://groups.yahoo.com/group/emacs-nxml-mode/">http://groups.yahoo.com/group/emacs-nxml-mode</ulink>
+ for bug reports, discussion. I will announce all new versions there.
+ </para>
+
+ <para>
+ James Clark
+ </para>
+ <para>
+ jjc@@thaiopensource.com
+ </para>
+ </sect1>
+ </chapter>
+@
+
+
+1.4
+log
+ at fix typo per bug #126101
+@
+text
+@@
+
+
+1.3
+log
+ at general tag and style cleanup
+@
+text
+ at d20 1
+a20 1
+ DockBook XML format. nXML mode provides context-sensitive editing using
+@
+
+
+1.2
+log
+ at capitalize RPM, misuse of application tag
+@
+text
+ at d18 5
+a22 3
+ You can also use the nXML mode available for <application>Emacs</application> to make it even easier to write
+ in DockBook XML format. nXML mode provides context-sensitive editing using completion, real time validity error checking,
+ syntax highlighting and indentation. All you need to do is install an RPM!!
+d28 6
+a33 1
+ Please be aware the nxml-mode for <application>Emacs</application> is quite new, so there are a few things that the advanced user might notice when using it with other documents types. If you keep an eye on the mailing-list, you can keep up to date with these, as well as ask questions. For more details, check out <xref linkend="s1-emacs-nxml-readme"></xref>
+d51 7
+a57 1
+ In order to use nXML mode with emacs, you will need to install the nXML RPM available from <ulink url="http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/">Tim Waugh's</ulink> website or the source from <ulink url="http://www.thaiopensource.com/download/">www.thaiopensource.com/download/</ulink>. The source requires a lot more work to setup, therefore we will only be concentrating on the RPM version.
+d61 3
+a63 2
+ Information on where to get the source is available in <xref linkend="s1-emacs-additional-resources"></xref>
+ </para>
+d71 4
+a74 1
+ Compared to PSGML mode there are only couple of commands that you need. This speeds up writing with Emacs considerably, which means you can concentrate more on the content of your article.
+d81 4
+a84 1
+ To create a tag, just type <userinput><</userinput> and then type the keyword. To complete the keyword, press <command>Ctrl-Ret</command>, then add the last <userinput>></userinput>. To close a tag, type <userinput></</userinput>.
+d88 5
+a92 2
+ <title>Using vacuous schema</title>
+ <para>When you open a document that doesn't have a DOCTYPE declaration at the top of the file, you will get this message and tag completion won't work because nXML will not know what format you are writing.
+d97 6
+a102 1
+ To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/schema</filename> and load <filename>docbook.rnc</filename>. <application>Emacs</application> will then prompt you to save it in the current working directory.
+d107 1
+a107 1
+ <title>Don't forget</title>
+d109 5
+a113 1
+ The commands already discussed are the only differences between using <application>Emacs</application> with PSGML mode and <application>Emacs</application> with nXML mode. You will still need to use all the same commands as discussed in <xref linkend="s1-emacs-basic-commands"></xref>.
+d122 3
+a124 2
+ <para> Additional Emacs and nXML references are available at the
+ following locations:
+d129 3
+a131 1
+ <para><ulink url="http://www.thaiopensource.com/download/">http://www.thaiopensource.com/download/</ulink> — <citetitle>Author's download area</citetitle>
+d135 2
+a136 2
+ <para>
+ <ulink url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink>
+d140 5
+a144 4
+ <listitem> <para>Emacs reference card that comes with the
+ <filename>emacs</filename> package. You can print it out as a
+ reference. —
+ <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>
+d151 1
+a151 1
+ <title>nXML README file</title>
+d154 7
+a160 3
+ <para>
+ This file can be found in the directory you extracted the source into, or in <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename> if you installed the RPM.
+ </para>
+d163 1
+a163 1
+<para>README file:</para>
+d175 1
+a175 1
+ To get started, do
+d178 3
+a180 3
+ <para>
+ <command> M-x load-file RET rng-auto.el RET</command>
+ </para>
+d184 1
+a184 1
+ an XML document, and do
+d187 3
+a189 3
+ <para>
+ <command>M-x nxml-mode</command>
+ </para>
+d195 3
+a197 3
+ <para>
+ <command>C-h m</command>
+ </para>
+d200 2
+a201 2
+ For information on how to use nxml-mode.
+ The beginnings of a manual are in nxml-mode.info. You can read this using
+d204 3
+d209 2
+a210 1
+ <command>C-u M-x info RET nxml-mode.info RET</command>
+d214 3
+a216 2
+ It's also installed as an entry at the end of the top-level info
+ directory. So you can read it with <computeroutput>C-h i</computeroutput> as usual.
+d218 1
+d220 1
+a220 2
+ You can use test.valid.xml and test.invalid.xml as examples of valid
+ and invalid XML documents.
+d223 2
+a224 5
+ <para>
+ To get things automatically loaded each time you start Emacs, add
+
+ <screen>
+ <computeroutput>
+d226 2
+a227 2
+ </computeroutput>
+ </screen>
+d229 8
+a236 5
+ to your .emacs, where ~/nxml-mode-200YMMDD is the directory containing
+the <filename>.elc</filename> files. Note that <filename>rng-auto.el</filename> does not load all of the
+nxml-mode code; it merely sets things up so that all the features of
+nxml-mode will be autoloaded properly. You should not try to autoload
+<filename>rng-auto.el</filename> itself.
+d240 4
+a243 2
+To use nxml-mode automatically for files with an extension of xml,
+xsl, rng or xhtml, add
+d246 2
+a247 2
+ <screen>
+ <computeroutput>
+d251 2
+a252 11
+ </computeroutput>
+ </screen>
+ <para>
+ to your .emacs.
+ </para>
+
+ <para>
+ If you edit XML using iso-8859-N encodings other than iso-8859-1 and
+ you are running Emacs 21.3 or later, then I recommend enabling
+ unify-8859-on-decoding-mode, by adding
+ </para>
+d255 4
+a258 1
+ <command>(unify-8859-on-decoding-mode)</command>
+d261 3
+a263 3
+ <para>
+ to your <filename>.emacs.</filename>
+ </para>
+d272 2
+a273 1
+ For more on RELAX NG, see <ulink url="http://relaxng.org">http://relaxng.org</ulink>
+d277 2
+a278 1
+ For a tutorial on RELAX NG Compact Syntax, see <ulink url="http://relaxng.org/compact-tutorial.html">http://relaxng.org/compact-tutorial.html</ulink>
+d282 3
+a284 1
+ For automatically creating RNC schemas, I recommend my Trang program: <ulink url="http://www.thaiopensource.com/relaxng/trang.html">http://eee.thaiopensource.com/relaxng/trang.html"</ulink>
+d293 1
+a293 1
+ infer an RNC schema from an instance document;
+d298 1
+a298 1
+ convert a DTD to an RNC schema;
+d303 1
+a303 1
+ convert a RELAX NG XML syntax schema to an RNC schema.
+d310 3
+a312 2
+ To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you
+ can also use the XSLT stylesheet from <ulink url="http://www.pantor.com/download.html">http://www.pantor.com/download.html"</ulink>
+d316 4
+a319 3
+ To convert a W3C XML Schema to an RNC schema, you need first to
+ convert it to RELAX NG XML syntax using Sun's RELAX NG converter tool
+ rngconv (built on top of MSV). See <ulink url="https://msv.dev.java.net/">https://www.dev.java.net/</ulink>
+d323 1
+a323 1
+ The file NEWS describes recent changes.
+d327 2
+a328 1
+ Please use the list <ulink url="http://groups.yahoo.com/group/emacs-nxml-mode/">http://groups.yahoo.com/group/emacs-nxml-mode</ulink>
+a339 9
+
+
+
+
+
+
+
+
+
+@
+
+
+1.1
+log
+ at add Gavin's patch for nxml
+@
+text
+ at d20 1
+a20 1
+ syntax highlighting and indentation. All you need to do is install an rpm!!
+d32 1
+a32 1
+ <title>Getting the <application>nXML rpm</application></title>
+d36 1
+a36 1
+ <secondary>rpm</secondary>
+d40 1
+a40 1
+ <primary><application>nXML rpm</application></primary>
+d44 1
+a44 1
+ In order to use nXML mode with emacs, you will need to install the nXML rpm available from <ulink url="http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/">Tim Waugh's</ulink> website or the source from <ulink url="http://www.thaiopensource.com/download/">www.thaiopensource.com/download</ulink>. The source requires a lot more work to setup, therefore we will only be concentrating on the rpm version.
+d119 1
+a119 1
+ This file can be found in the directory you extracted the source into, or in <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename> if you installed the rpm
+@
+
diff --git a/old-documentation-guide/Attic/docs-emacs-nxml-zh_CN.xml,v b/old-documentation-guide/Attic/docs-emacs-nxml-zh_CN.xml,v
new file mode 100644
index 0000000..170a065
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-emacs-nxml-zh_CN.xml,v
@@ -0,0 +1,160 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<chapter id="ch-emacs-nxml">
+ <title>Emacs 与 nXML 模式</title>
+ <indexterm>
+ <primary>nXML</primary>
+ </indexterm>
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>nXML 模式</secondary>
+ </indexterm>
+ <para>您可以使用 <application>Emacs</application> 的 nXML 模式，使撰写 DocBook XML 格式更加简单。nXML 模式提供了上下文敏感的编辑模式，包括补全、实时的有效性检测、语法高亮和缩进。为此您只要安装一个 RPM 软件包！</para>
+ <note>
+ <title>开发早期</title>
+ <para>需要注意的是，<application>Emacs</application> 的 nXML 模式尚不完善，因此在编辑一些文档时，高级用户可能会注意到一些问题。如果您略微关注一下邮件列表，就可以获得相关信息，也可以问问题。请参考 <xref linkend="s1-emacs-nxml-readme"/>。</para>
+ </note>
+ <sect1 id="s1-nxml-rpm">
+ <title>下载 nXML RPM</title>
+ <indexterm>
+ <primary>nXML</primary>
+ <secondary>RPM</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>nXML RPM</primary>
+ </indexterm>
+ <para>要在 emacs 中使用 nXML 模式，您需要安装 <ulink url="http://people.redhat.com/twaugh/ftp/docbook/nxml-modee/"> Tim Waugh <ulink> 网站上的 nXML RPM，或者下载 <ulink url="http://www.thaiopensource.com/download/">http://www.thaiopensource.com/download/</ulink> 的源代码。源代码需要花工夫来配置，因此这里只考虑 RPM 版本。</ulink></ulink></para>
+ <para>关于下载源代码请参考 <xref linkend="s1-emacs-additional-resources"/>。</para>
+ </sect1>
+ <sect1 id="s1-nxml-examples">
+ <title>范例</title>
+ <para>与 PSGML 模式相比，您只需有数几个命令。这样使用 <application>Emacs</application> 编辑就快捷多了，您可以更多地关注文章的内容。</para>
+ <sect2 id="s2-nxml-commands">
+ <title>命令</title>
+ <para>要创建一个标记，输入 <userinput><</userinput> 然后输入关键字。要完成这个关键字，按下 <command>Ctrl-Ret</command>，然后添加随后的 <userinput>></userinput>。要关闭一个标记，输入 <userinput></</userinput>。</para>
+ <important>
+ <title>注意</title>
+ <para>当您打开不包含首部 DOCTYPE 声明的文件时，将看到如下信息，标记补全也无法实现，因为 nXML 不知道您在编辑的文件格式。</para>
+ </important>
+ <para>要加载 schema，按下 <command>Ctrl-c</command>，然后按 <command>Ctrl-s</command> 然后浏览 <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> 并加载 <filename>docbook.rnc</filename>。<application>Emacs</application> 将提示您将它保存到工作目录。</para>
+ <tip>
+ <title>技巧</title>
+ <para>已描述过的命令只是 <application>Emacs</application> PSGML 模式与 <application>Emacs</application> nXML 模式的不同之处。您仍然需要使用 <xref linkend="s1-emacs-basic-commands"/> 中描述的命令。</para>
+ </tip>
+ </sect2>
+ </sect1>
+ <sect1 id="s1-emacs-nxml-additional-resources">
+ <title>其他资源</title>
+ <para>其他的 Emacs 与 nXML 帮助可以在下列位置找到：</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://www.thaiopensource.com/download/">http://www.thaiopensource.com/download/</ulink> — <citetitle>Author's download area</citetitle></para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink> — <citetitle>Emacs Quick Reference Guide</citetitle></para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>emacs</filename> 软件包附带了 Emacs 参考卡片。您可以打印一份，作为参考。— <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename></para>
+ </listitem>
+ </itemizedlist>
+ </sect1>
+ <sect1 id="s1-emacs-nxml-readme">
+ <title>nXML README 文件</title>
+ <note>
+ <title>注意</title>
+ <para>这个文件可以在您解压的源代码中找到，如果安装了 RPM，它的位置是 <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename>。</para>
+ </note>
+ <para>README 文件：</para>
+ <para>这是 GNU Emacs 的一种新的主模式。它支持格式良好的 XML 文档，也为采用 RELAX NG Compact Syntax 的 XML 文档提供了 schema-sensitive 编辑模式。</para>
+ <para>要使用它，您需要 GNU Emacs 21.x 版本，推荐 21.3。GNU Emacs 20 版本中无法正常运作，XEmacs 也不行。要开始编辑，输入命令：</para>
+ <screen>
+ <command>M-x load-file RET rng-auto.el RET</command>
+ </screen>
+ <para>这样定义了必需的 autoloads。然后，打开一个包含 XML 文档的文件，执行命令：</para>
+ <screen>
+ <command>M-x nxml-mode</command>
+ </screen>
+ <para>然后执行</para>
+ <screen>
+ <command>C-h m</command>
+ </screen>
+ <para>来查看 nXML 模式的使用帮助。手册的起始页在 nxml-mode.info 中，可以这样阅读它：</para>
+ <screen>
+ <command>C-u M-x info RET nxml-mode.info RET</command>
+ </screen>
+ <para>它也在顶层 info 目录最后添加了自己的一项，因此您可以和平常一样，用 <command>C-h i</command> 开始阅读。</para>
+ <para>您可以用 <filename>test.valid.xml</filename> 和 <filename>test.invalid.xml</filename> 作为正确和不正确的 XML 文档范例。</para>
+ <para>要在 Emacs 启动时自动加载这些，将下列内容加入您的 <filename>.emacs</filename>：</para>
+ <screen>
+ <computeroutput>
+(load "~/nxml-mode-200YMMDD/rng-auto.el")
+</computeroutput>
+ </screen>
+ <para>这里 <computeroutput>~/nxml-mode-200YMMDD</computeroutput> 是包含 <filename>.elc</filename> 文件的目录。注意 <filename>rng-auto.el</filename> 不会加载所有 nXML 模式的代码；它仅仅设置环境，使得 nXML 模式的所有特性得以正确地自动加载。您不应尝试自动加载 <filename>rng-auto.el</filename> 本身。</para>
+ <para>要在加载扩展名是 <filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> 或 <filename>xhtml</filename> 的文件时自动切换到 nXML 模式，将下列内容加入您的 <filename>.emacs</filename>：</para>
+ <screen>
+ <computeroutput>
+(setq auto-mode-alist
+ (cons '("\\.\\(xml\\|xsl\\|rng\\|xhtml\\)\\'" . nxml-mode)
+ auto-mode-alist))
+</computeroutput>
+ </screen>
+ <para>如果您编辑 iso-8859-N 编码的 XML，而不是 iso-8859-1，并且您运行的是 Emacs 21.3 或更新版本，那么最好打开 unify-8859-on-decoding-mode，将下列内容加入您的 <filename>.emacs</filename>：</para>
+ <screen>
+ <computeroutput>(unify-8859-on-decoding-mode)</computeroutput>
+ </screen>
+ <para>要使用验证以及 schema-sensitive 编辑模式，您需要文档的 RELAX NG Compact Syntax (RNC) schema 文件。schema 目录包含了常用文档类型的 schema。</para>
+ <para>关于 RELAX NG 请参考 <ulink url="http://relaxng.org/">http://relaxng.org/</ulink>。</para>
+ <para>关于 RELAX NG Compact NG 的教程请参考 <ulink url="http://relaxng.org/compact-tutorial.html">http://relaxng.org/compact-tutorial.html</ulink></para>
+ <para>关于自动创建 RNC schema，推荐使用 Trang 程序：<ulink url="http://www.thaiopensource.com/relaxng/trang.html">http://eee.thaiopensource.com/relaxng/trang.html"</ulink></para>
+ <para>您可以使用它来 <itemizedlist><listitem><para>从已有文档得出 RNC schema</para></listitem><listitem><para>将 DTD 转换为 RNC schema</para></listitem><listitem><para>将 RELAX NG XML syntax schema 转换为 RNC schema</para></listitem></itemizedlist></para>
+ <para>要将 RELAX NG XML syntax (.rng) schema 转换为 RNC schema，您也可以使用 <ulink url="http://www.pantor.com/download.html">http://www.pantor.com/download.html"</ulink> 的 XSLT 样式表。</para>
+ <para>要将 W3C XML Schema 转换为 RNC schema，您需要首先将它转换为 RELAX NG XML syntax，使用 Sun 的 RELAX NG 转换工具 rngconv (基于 MSV)。请参考 <ulink url="https://msv.dev.java.net/">https://www.dev.java.net/</ulink>。</para>
+ <para>文件 <filename>NEWS</filename> 描述了最近的更改。</para>
+ <para>请访问邮件列表 <ulink url="http://groups.yahoo.com/group/emacs-nxml-mode/">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> 来提交 bug 和参与讨论。我将在那里发布新版本。</para>
+ <para>James Clark</para>
+ <para>jjc@@thaiopensource.com</para>
+ </sect1>
+</chapter>
+@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+@@
+
diff --git a/old-documentation-guide/Attic/docs-emacs-zh_CN.xml,v b/old-documentation-guide/Attic/docs-emacs-zh_CN.xml,v
new file mode 100644
index 0000000..9410bde
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-emacs-zh_CN.xml,v
@@ -0,0 +1,586 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.17.13.28.38; author bbbush; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id: docs-emacs-zh_CN.xml,v 1.2 2005/12/17 13:28:38 bbbush Exp $ --><chapter id="ch-emacs">
+ <title>Emacs 与 PSGML 模式</title>
+ <indexterm>
+ <primary>PSGML</primary>
+ </indexterm>
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>PSGML 模式</secondary>
+ </indexterm>
+ <para>您可以利用 Emacs 的 PSGML 模式以使编辑 XML 格式更容易。PSGML 模式提供了语法高亮，标记补全等功能。</para>
+ <sect1 id="s1-emacs-file">
+ <title>设置您的 <filename>.emacs</filename></title>
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>配置文件</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>
+ <filename>.emacs</filename>
+ </primary>
+ </indexterm>
+ <para>为使 Emacs 可以正确解析您的 DocBook 文档，您必须定制一个 <filename>.emacs</filename> 文件。将下列内容复制并粘贴到您已有的 <filename>.emacs</filename> 文件中，或者创建一个包含下列内容的新文件：<screen><computeroutput>
+;; turn on auto-fill in `text-mode' and derived modes
+;;(mail, news, etc)
+(add-hook 'text-mode-hook 'turn-on-auto-fill)
+
+;;
+;;MODES
+;;
+
+(setq auto-mode-alist (cons '("\\.sgml$" . sgml-mode) auto-mode-alist))
+(setq auto-mode-alist (cons '("\\.sgm$" . sgml-mode) auto-mode-alist))
+
+;;
+;;XML!!
+;;
+;;#############################################################
+
+;;
+;;PSGML mode stuff
+;;
+
+(autoload 'sgml-mode "psgml" "My Most Major Mode" t)
+
+(setq sgml-mode-hook '(lambda () "Defaults for XML mode." (turn-on-auto-fill)
+(setq fill-column 80)))
+
+(defun My-XML-keymap ()
+ (local-set-key [(alt i)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt l)]
+ '(lambda ()
+ (interactive)
+ (sgml-insert-element 'list)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt p)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'para)
+ (sgml-indent-line)))
+ (local-set-key [(alt -)]
+ '(lambda ()
+ (interactive)
+ (insert "—"))))
+
+(add-hook 'sgml-mode-hook 'My-XML-keymap)
+
+;;
+;; Fix up indentation of data...
+;;
+
+(setq-default sgml-indent-data t)
+
+;;
+;; XML markup faces.
+;;
+
+(setq-default sgml-set-face t)
+
+
+(make-face 'sgml-comment-face)
+(make-face 'sgml-doctype-face)
+(make-face 'sgml-end-tag-face)
+(make-face 'sgml-entity-face)
+(make-face 'sgml-ignored-face)
+(make-face 'sgml-ms-end-face)
+(make-face 'sgml-ms-start-face)
+(make-face 'sgml-pi-face)
+(make-face 'sgml-sgml-face)
+(make-face 'sgml-short-ref-face)
+(make-face 'sgml-start-tag-face)
+
+(set-face-foreground 'sgml-comment-face "maroon")
+(set-face-foreground 'sgml-doctype-face "dark green")
+(set-face-foreground 'sgml-end-tag-face "blue2")
+(set-face-foreground 'sgml-entity-face "red2")
+(set-face-foreground 'sgml-ignored-face "maroon")
+(set-face-background 'sgml-ignored-face "gray90")
+(set-face-foreground 'sgml-ms-end-face "maroon")
+(set-face-foreground 'sgml-ms-start-face "maroon")
+(set-face-foreground 'sgml-pi-face "maroon")
+(set-face-foreground 'sgml-sgml-face "maroon")
+(set-face-foreground 'sgml-short-ref-face "goldenrod")
+(set-face-foreground 'sgml-start-tag-face "blue2")
+
+(setq-default sgml-markup-faces
+ '((comment . sgml-comment-face)
+ (doctype . sgml-doctype-face)
+ (end-tag . sgml-end-tag-face)
+ (entity . sgml-entity-face)
+ (ignored . sgml-ignored-face)
+ (ms-end . sgml-ms-end-face)
+ (ms-start . sgml-ms-start-face)
+ (pi . sgml-pi-face)
+ (sgml . sgml-sgml-face)
+ (short-ref . sgml-short-ref-face)
+ (start-tag . sgml-start-tag-face)))
+
+
+(defun docbook-mode ()
+ (sgml-mode)
+ )
+
+
+
+;;
+;;END XML STUFF
+;;
+;;##################################################################
+
+;PO mode stuff
+
+(setq auto-mode-alist
+ (cons '("\\.pox?\\'" . po-mode) auto-mode-alist))
+(autoload 'po-mode "po-mode")
+
+
+ (global-set-key [(f1)] (lambda () (interactive) (manual-
+ entry (current-word))))
+
+</computeroutput></screen></para>
+ <para>您是否有一个滚轮鼠标？如果是，那么可以将下列内容加入您的 <filename>.emacs</filename>，这样您的滚轮将可以用在 <application>Emacs</application> 中 (适于 <application>Emacs</application> 版本 21)：</para>
+ <screen>
+ <computeroutput>
+;; Enable wheelmouse support by default for emacs 21
+(cond (window-system
+(mwheel-install)
+))
+</computeroutput>
+ </screen>
+ <para>如果您使用旧的 20 版本，应添加下列内容：</para>
+ <screen>
+ <computeroutput>
+;; Enable wheelmouse support by default
+(require 'mwheel)
+</computeroutput>
+ </screen>
+
+
+<!-- bug #125757 in NEEDINFO state
+ <para>
+ If you have a mouse, you can also add the following. It adds popup menus
+ when the cursor is either on a start tag or in a region where elements
+ are allowed.
+ </para>
+
+<screen>
+<computeroutput>
+;; Mouse Bindings: right-click to generate context-aware
+;; elements/attributes popup menu.
+(define-key sgml-mode-map [mouse-3] 'sgml-tags-menu)
+</computeroutput>
+</screen>
+
+-->
+
+ </sect1>
+ <sect1 id="s1-emacs-colors">
+ <title>定制 Emacs</title>
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>定制</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>
+ <filename>.Xresources</filename>
+ </primary>
+ </indexterm>
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>colors</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>font</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>geometry</secondary>
+ </indexterm>
+ <para>在您的 <filename>~/.Xresources</filename> 中配置 Emacs 的颜色，字体和默认窗口大小。设置的格式是 <computeroutput>emacs.keyword:value</computeroutput></para>
+ <para>下面是一个 <filename>~/.Xresources</filename> 文件范例。</para>
+ <note>
+ <title>注意</title>
+ <para>如果您的 <filename>~/.Xresources</filename> 中包含其他设置，就将下列内容添加到文件结尾。</para>
+ </note>
+ <screen>
+ <userinput>
+emacs.background: light gray
+emacs.foreground: black
+emacs.pointerColor: blue
+emacs.cursorColor: blue
+emacs.bitmapIcon: on
+emacs.font: fixed
+emacs.geometry: 90x25
+</userinput>
+ </screen>
+ <para>修改文件后，您必须执行命令</para>
+ <screen>
+ <command>xrdb -merge ~/.Xresources</command>
+ </screen>
+ <para>并且重新运行 <application>Emacs</application> 以使改变生效。</para>
+ </sect1>
+ <sect1 id="s1-emacs-cedfile">
+ <title>创建重编译的 DTD 子集</title>
+ <para>如果给出了正确的文档类型声明 (DTD) 文件，Emacs 可以对 DocBook XML 文件进行正确的语法高亮和缩进。这些特性将使您的 XML 文件易于阅读，帮助您发现错误。</para>
+ <para>要创建一个可加载的已解析的 DTD 文件：<orderedlist><listitem><para>找到一组 DocBook 文件的主控文件。您可以通过头部是否包含 <filename><!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN"</filename> 来找到它。最简单的办法，是运行命令 <command>grep DocBook *.xml</command>。找到主控文件后，在 Emacs 中打开它，命令是 <command>emacs <replaceable><parentfile></replaceable>.xml</command> (这里 <replaceable><parentfile></replaceable>.xml 是你找到的主控文件)。</para></listitem><listitem><para>在下拉菜单中选择 <command>DTD -> Parse DTD</command>。</para></listitem><listitem><para>当您看到屏幕下方的 <computeroutput>Fontifying...done</computeroutput> 信息时，解析就完成了。将已解析的 DTD 保存为文件，方法是在下拉菜单中选择 <command>DTD -> Save Parsed DTD</command>。</para></listitem><listitem><para>按下 <keycap>Enter</
keycap> 来保存为默认文件名，或者修改文件名，但应保留 <filename>.ced</filename> 扩展名。可以将它命名为 <filename>docbook.ced</filename> 这样很通用的名字，这样您在打开所有 DocBook 文件的时候都可以引用它。这个文件也可以复制到要加载的目录中。</para></listitem></orderedlist></para>
+ <tip>
+ <title>技巧</title>
+ <para>您也可以使用 Emacs 命令 <command>Meta-x sgml-parse-prolog</command> 来解析这个文件，然后用命令 <command>Meta-x sgml-save-dtd</command> 来保存已解析的 DTD 到 <filename>.ced</filename> 文件中。</para>
+ </tip>
+ </sect1>
+ <sect1 id="s1-emacs-loadced">
+ <title>加载已解析的 DTD</title>
+ <para>现在您已保存了 DTD 设置，您可以加载这个 <filename>.ced</filename> 文件，看看 <filename>.sgml</filename> 文件语法高亮的效果。</para>
+ <para>要加载已解析的 DTD 文件：<orderedlist><listitem><para>在 Emacs 中打开 XML 文件</para></listitem><listitem><para>在下拉菜单中选择 <command>DTD -> Load DTD</command> 然后选择您在上一步保存的文件。例如，选择 <filename>docbook.ced</filename>。</para></listitem><listitem><para>当您看到屏幕下方的 <computeroutput>Fontifying...done</computeroutput> 信息时，就加载完毕了。加载已解析的 DTD 可能需要很久。您可以在加载完毕前就开始编辑。</para></listitem></orderedlist></para>
+ <tip>
+ <title>技巧</title>
+ <para>您也可以使用 Emacs 命令 <command>Meta-x sgml-load-dtd</command> 来加载已翻译的 DTD。</para>
+ </tip>
+ </sect1>
+ <sect1 id="s1-emacs-basic-commands">
+ <title>基本的 Emacs 命令</title>
+ <para>
+ <keycap>Meta</keycap> 键通常指的是 <keycap>Alt</keycap> 键。</para>
+ <table colsep="1" frame="all" id="tb-emacs-commands" rowsep="1">
+ <title>Emacs 命令</title>
+ <tgroup cols="2" colsep="1" rowsep="1">
+ <colspec colname="shortcut" colnum="1" colwidth="170"/>
+ <colspec colname="description" colnum="2" colwidth="300"/>
+ <thead>
+ <row>
+ <entry colsep="1" rowsep="1">快捷方式</entry>
+ <entry colsep="1" rowsep="1">描述</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry colsep="1" rowsep="1">
+ <keycombo>
+ <keycap>Meta</keycap>
+ <keycap>x</keycap>
+ </keycombo> sgml-parse-prolog, <keycap>Enter</keycap></entry>
+ <entry>解析 DTD</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Meta</keycap>
+ <keycap>x</keycap>
+ </keycombo>sgml-save-dtd, <keycap>Enter</keycap></entry>
+ <entry>保存已解析的 DTD</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Meta</keycap>
+ <keycap>x</keycap>
+ </keycombo>sgml-load-dtd, <keycap>Enter</keycap></entry>
+ <entry>加载 DTD</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>c</keycap>
+ </keycombo>, <keycombo><keycap>Shift</keycap><keycap/></keycombo>, <keycap>Tab</keycap></entry>
+ <entry>显示有效标记的列表</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>c</keycap>
+ </keycombo>, <keycombo><keycap>Shift</keycap><keycap/></keycombo>, type beginning of tag, <keycap>Tab</keycap></entry>
+ <entry>补全标记</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap> <keycap>g</keycap></keycombo>
+ </entry>
+ <entry>取消 minibuffer 中的命令</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>c</keycap>
+ </keycombo>, <keycap>/</keycap></entry>
+ <entry>关闭标记</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap> <keycap>a</keycap></keycombo>
+ </entry>
+ <entry>将光标移动到行首</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>e</keycap>
+ </keycombo>
+ </entry>
+ <entry>将光标移动到行尾</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>Home</keycap>
+ </keycombo>
+ </entry>
+ <entry>将光标移动到文件开始</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>End</keycap>
+ </keycombo>
+ </entry>
+ <entry>将光标移动到文件结束</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>k</keycap>
+ </keycombo>
+ </entry>
+ <entry>剪切一行</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap> <keycap>y</keycap></keycombo>
+ </entry>
+ <entry>粘贴一行</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap> <keycap>s</keycap></keycombo>
+ </entry>
+ <entry>在文件中向前搜索</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>r</keycap>
+ </keycombo>
+ </entry>
+ <entry>在文件中向后搜索</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Meta</keycap>
+ <keycap>$</keycap>
+ </keycombo>
+ </entry>
+ <entry>检查当前单词的拼写</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Meta</keycap>
+ <keycap>x</keycap>
+ </keycombo> ispell-word, <keycap>Enter</keycap></entry>
+ <entry>检查当前单词的拼写</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Meta</keycap>
+ <keycap>x</keycap>
+ </keycombo> ispell-buffer, <keycap>Enter</keycap></entry>
+ <entry>检测当前 buffer 的拼写</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap></keycombo></entry>
+ <entry>打开文件</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo></entry>
+ <entry>保存文件</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo></entry>
+ <entry>退出 <application>Emacs</application>，在需要时提示保存文件</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Meta</keycap> <keycap>q</keycap></keycombo>
+ </entry>
+ <entry>段落重排</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>c</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>a</keycap></keycombo></entry>
+ <entry>编辑标记的属性 (例如，您可以编辑 <computeroutput>ulink</computeroutput> 标记的 <computeroutput>url</computeroutput> 属性)</entry>
+ </row>
+ <row>
+ <entry>
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>c</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo></entry>
+ <entry>结束编辑属性</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </sect1>
+ <sect1 id="s1-emacs-examples">
+ <title>范例</title>
+ <para>Emacs 和 PSGML 的命令表 (参考卡片) 对于新手来说有些难。本节有一些例子，讲解如何使用它们。</para>
+ <sect2 id="s2-emacs-tag-completion">
+ <title>标记补全</title>
+ <note>
+ <title>注意</title>
+ <para>本节假设您已经加载了 DTD 文件 (<filename>.ced</filename>)。</para>
+ </note>
+ <para>需要插入标记时，不要输入它。按下组合键 <keycap>Ctrl</keycap>-<keycap>c</keycap>, 然后按下 <keycap><</keycap>。在 <application>Emacs</application> 窗口的下方，您将看到：</para>
+ <screen>
+ <computeroutput>Tag: <</computeroutput>
+ </screen>
+ <para>要查看所有标记的列表，按下 <keycap>Tab</keycap> 或 <keycap>?</keycap>。如果您知道标记的首字母，可以按下它们，然后按 <keycap>Tab</keycap>，就可以看到有同样首字母的所有标记的列表。</para>
+ <para>尝试这样：按下 <keycap>Ctrl</keycap>-<keycap>c</keycap> 然后按 <keycap><</keycap>，然后按下字母 <keycap>k</keycap>，然后按 <keycap>Tab</keycap>。为了得到完整的列表，您可能需要多次按下 <keycap>Tab</keycap>。</para>
+ <para>输出应当与下面类似：</para>
+ <screen>
+ <computeroutput>
+Click mouse-2 on a completion to select it.
+In this buffer, type RET to select the completion near point.
+
+Possible completions are:
+<keycap> <keycode>
+<keycombo> <keysym>
+</computeroutput>
+ </screen>
+ </sect2>
+ <sect2 id="s2-emacs-tag-closing">
+ <title>标记关闭</title>
+ <para>当您开始了一个标记后，您必须关闭它。按下组合键 <keycap>Ctrl</keycap>-<keycap>c</keycap>，然后按 <keycap>/</keycap>。这样将关闭最近一个开放的标记。</para>
+ </sect2>
+ <sect2 id="s2-emacs-other">
+ <title>其他 Emacs 任务</title>
+ <para>
+ <guilabel>恢复单个窗口</guilabel>: 有时 <application>Emacs</application> 窗口被划分 (下方的窗口有标记补全等内容)。要恢复到只有您的 XML 文本全屏显示的状态，最简单的办法是按下 <keycap>Ctrl</keycap>-<keycap>x</keycap>，然后按 <keycap>1</keycap>。</para>
+ <para>
+ <guilabel>保存作品</guilabel>: 要保存编辑结果，按下 <keycap>Ctrl</keycap>-<keycap>x</keycap> 然后按 <keycap>Ctrl</keycap>-<keycap>s</keycap>。</para>
+ <para>
+ <guilabel>"清除/返回"命令</guilabel>:有时，在标记补全中玩得太多，需要直接返回编辑时，按下 <keycap>Ctrl</keycap>-<keycap>g</keycap>。这个命令将放弃当前动作，而不会关闭文件本身。</para>
+ <para>
+ <guilabel>打开文件</guilabel>: 要打开一个新文件，按下 <keycap>Ctrl</keycap>-<keycap>x</keycap> 然后按 <keycap>Ctrl</keycap>-<keycap>f</keycap>。在窗口下方，可以输入要打开文件名 (这里也可以使用 <keycap>Tab</keycap> 补全)。</para>
+ <para>
+ <guilabel>关闭 emacs</guilabel>: 要关闭 <application>emacs</application>，按下 <keycap>Ctrl</keycap>-<keycap>x</keycap> 然后按 <keycap>Ctrl</keycap>-<keycap>c</keycap>。如果您尚未保存，它将提示，否则它会简单地退出。</para>
+ </sect2>
+ </sect1>
+ <sect1 id="s1-emacs-additional-resources">
+ <title>其他资源</title>
+ <para>其他 Emacs 和 PSGML 参考可以在这里找到：</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink> — <citetitle>Emacs Quick Reference Guide</citetitle></para>
+ </listitem>
+ <listitem> <para><filename>emacs</filename> 软件包附带了 Emacs 参考卡片。您可以打印一份，作为参考。— <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename></para></listitem>
+ <listitem>
+ <para>
+ <filename>/usr/share/doc/psgml-<replaceable><version></replaceable>/psgml.ps</filename> 中的 <citetitle>Editing XML with Emacs and PSGML</citetitle>。</para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://www.snee.com/bob/sgmlfree/psgmqref.html">http://www.snee.com/bob/sgmlfree/psgmqref.html</ulink> — <citetitle>Emacs/PSGML Quick Reference</citetitle> 是一个 Emacs PSGML 模式的索引表。</para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://www.snee.com/bob/sgmlfree/emcspsgm.html">http://www.snee.com/bob/sgmlfree/emcspsgm.html</ulink> — <citetitle>PSGML Tricks</citetitle></para>
+ </listitem>
+ </itemizedlist>
+ </sect1>
+</chapter>
+@
+
+
+1.2
+log
+ at update build part
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: docs-emacs-en.xml,v 1.2 2004/08/13 15:35:41 tfox Exp $ --><chapter id="ch-emacs">
+@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+@@
+
diff --git a/old-documentation-guide/Attic/docs-emacs.xml,v b/old-documentation-guide/Attic/docs-emacs.xml,v
new file mode 100644
index 0000000..1e62dd9
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-emacs.xml,v
@@ -0,0 +1,737 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2003.11.21.22.40.39; author tfox; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at change filenames to end with -en.xml
+@
+text
+@<!-- $Id: docs-emacs.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+
+ <chapter id="ch-emacs">
+ <title>Emacs and PSGML Mode</title>
+
+ <indexterm>
+ <primary>PSGML</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>PSGML mode</secondary>
+ </indexterm>
+
+ <para>
+ You can use the PSGML mode available for Emacs to make it easier to write
+ in XML format. PSGML mode provides syntax-highlighting, tag completion,
+ and more.
+ </para>
+
+ <sect1 id="s1-emacs-file">
+ <title>Setting Up Your <filename>.emacs</filename> File</title>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>configuration file</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.emacs</filename></primary>
+ </indexterm>
+
+ <para>
+ For Emacs to parse your DocBook documents correctly, you must have a
+ <filename>.emacs</filename> file. Cut and paste the following into your
+ existing <filename>.emacs</filename> file or create a new one that
+ contains the following lines:
+
+<screen>
+<computeroutput>
+;; turn on auto-fill in `text-mode' and derived modes
+;;(mail, news, etc)
+(add-hook 'text-mode-hook 'turn-on-auto-fill)
+
+;;
+;;MODES
+;;
+
+(setq auto-mode-alist (cons '("\\.sgml$" . sgml-mode) auto-mode-alist))
+(setq auto-mode-alist (cons '("\\.sgm$" . sgml-mode) auto-mode-alist))
+
+;;
+;;XML!!
+;;
+;;#############################################################
+
+;;
+;;PSGML mode stuff
+;;
+
+(autoload 'sgml-mode "psgml" "My Most Major Mode" t)
+
+(setq sgml-mode-hook '(lambda () "Defaults for XML mode." (turn-on-auto-fill)
+(setq fill-column 80)))
+
+(defun My-XML-keymap ()
+ (local-set-key [(alt i)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt l)]
+ '(lambda ()
+ (interactive)
+ (sgml-insert-element 'list)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt p)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'para)
+ (sgml-indent-line)))
+ (local-set-key [(alt -)]
+ '(lambda ()
+ (interactive)
+ (insert "—"))))
+
+(add-hook 'sgml-mode-hook 'My-XML-keymap)
+
+;;
+;; Fix up indentation of data...
+;;
+
+(setq-default sgml-indent-data t)
+
+;;
+;; XML markup faces.
+;;
+
+(setq-default sgml-set-face t)
+
+
+(make-face 'sgml-comment-face)
+(make-face 'sgml-doctype-face)
+(make-face 'sgml-end-tag-face)
+(make-face 'sgml-entity-face)
+(make-face 'sgml-ignored-face)
+(make-face 'sgml-ms-end-face)
+(make-face 'sgml-ms-start-face)
+(make-face 'sgml-pi-face)
+(make-face 'sgml-sgml-face)
+(make-face 'sgml-short-ref-face)
+(make-face 'sgml-start-tag-face)
+
+(set-face-foreground 'sgml-comment-face "maroon")
+(set-face-foreground 'sgml-doctype-face "dark green")
+(set-face-foreground 'sgml-end-tag-face "blue2")
+(set-face-foreground 'sgml-entity-face "red2")
+(set-face-foreground 'sgml-ignored-face "maroon")
+(set-face-background 'sgml-ignored-face "gray90")
+(set-face-foreground 'sgml-ms-end-face "maroon")
+(set-face-foreground 'sgml-ms-start-face "maroon")
+(set-face-foreground 'sgml-pi-face "maroon")
+(set-face-foreground 'sgml-sgml-face "maroon")
+(set-face-foreground 'sgml-short-ref-face "goldenrod")
+(set-face-foreground 'sgml-start-tag-face "blue2")
+
+(setq-default sgml-markup-faces
+ '((comment . sgml-comment-face)
+ (doctype . sgml-doctype-face)
+ (end-tag . sgml-end-tag-face)
+ (entity . sgml-entity-face)
+ (ignored . sgml-ignored-face)
+ (ms-end . sgml-ms-end-face)
+ (ms-start . sgml-ms-start-face)
+ (pi . sgml-pi-face)
+ (sgml . sgml-sgml-face)
+ (short-ref . sgml-short-ref-face)
+ (start-tag . sgml-start-tag-face)))
+
+
+(defun docbook-mode ()
+ (sgml-mode)
+ )
+
+
+
+;;
+;;END XML STUFF
+;;
+;;##################################################################
+
+;PO mode stuff
+
+(setq auto-mode-alist
+ (cons '("\\.pox?\\'" . po-mode) auto-mode-alist))
+(autoload 'po-mode "po-mode")
+
+
+ (global-set-key [(f1)] (lambda () (interactive) (manual-
+ entry (current-word))))
+
+</computeroutput>
+</screen>
+
+ </para>
+
+ <para>
+ Do you have a cool wheel mouse? If so, you can add the following to your
+ <filename>.emacs</filename> file so your wheel will work in
+ <application>Emacs</application> (must be
+ <application>Emacs</application> version 21):
+ </para>
+
+<screen>
+<computeroutput>
+;; Enable wheelmouse support by default for emacs 21
+(cond (window-system
+(mwheel-install)
+))
+</computeroutput>
+</screen>
+
+ <para>
+ If you are using the older version 20 of
+ <application>Emacs</application>, add the following instead:
+ </para>
+<screen>
+<computeroutput>
+;; Enable wheelmouse support by default
+(require 'mwheel)
+</computeroutput>
+</screen>
+
+ </sect1>
+
+
+ <sect1 id="s1-emacs-colors">
+ <title>Customizing Emacs</title>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>customizing</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.Xresources</filename></primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>colors</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>font</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>geometry</secondary>
+ </indexterm>
+
+ <para>
+ The colors, font, and geometry (default size of window) for Emacs in your
+ <filename>~/.Xresources</filename> file. The format for the settings is
+ <computeroutput>emacs.keyword:value</computeroutput>
+ </para>
+
+ <para>
+ The following is a sample <filename>~/.Xresources</filename> file.
+ </para>
+ <note>
+ <title>Note</title>
+ <para>If you have other settings in your
+ <filename>~/.Xresources</filename>, add the following to the end of
+ the file.
+ </para>
+ </note>
+
+<screen>
+<userinput>
+emacs.background: light gray
+emacs.foreground: black
+emacs.pointerColor: blue
+emacs.cursorColor: blue
+emacs.bitmapIcon: on
+emacs.font: fixed
+emacs.geometry: 90x25
+</userinput>
+</screen>
+ <para>
+ After modifying this file, you must execute the command
+ </para>
+<screen>
+<command>xrdb -merge ~/.Xresources</command>
+</screen>
+ <para>
+ and restart <application>Emacs</application> for the changes to take
+ place.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-cedfile">
+ <title>Create Recompiled DTD Subset</title>
+
+ <para>
+ Emacs will perform syntax highlighting and indent correctly on
+ DocBook XML files if you provide it with the proper Document Type
+ Declarations (DTD) file. These two features will make your XML file
+ look pretty and help you spot errors.
+ </para>
+
+ <para>
+ To create a loadable Parsed DTD file:
+ <orderedlist>
+ <listitem>
+ <para>Find the parent file for the group of DocBook files. You will
+ recognize this file by the header <filename><!DOCTYPE article
+ PUBLIC "-//OASIS//DTD DocBook V4.1//EN"</filename>. An easy way
+ to find this parent file is to use the command <command>grep
+ DocBook *.xml</command>. Once you find the parent file, open it
+ in Emacs with the command <command>emacs
+ <replaceable><parentfile></replaceable>.xml</command> (where
+ <replaceable><parentfile></replaceable>.xml is the parent
+ file you found.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Choose <command>DTD -> Parse DTD</command> from the pulldown
+ menu.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>You will know the parsing is finished when you see the message
+ <computeroutput>Fontifying...done</computeroutput> at the bottom
+ of your screen. Save the parsed DTD to a file by choosing
+ <command>DTD -> Save Parsed DTD</command> from the pulldown menu.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Press <keycap>Enter</keycap> to save the file to the default
+ filename or rename the file keeping the <filename>.ced</filename>
+ extension. It can be useful to name it something generic such as
+ <filename>docbook.ced</filename> so you can refer to it when
+ opening all DocBook files. This file can also be copied from
+ directory to directory to be loaded.
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </para>
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ You can also use the Emacs command <command>Meta-x
+ sgml-parse-prolog</command> to parse the file, and then use the
+ command <command>Meta-x sgml-save-dtd</command> to save the parsed DTD
+ to a <filename>.ced</filename> file.
+ </para>
+ </tip>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-loadced">
+ <title>Load the Parsed DTD</title>
+
+ <para>
+ Now that you have saved the DTD settings, you can load the
+ <filename>.ced</filename> file and see the syntax highlighting for your
+ <filename>.sgml</filename> files.
+ </para>
+
+ <para>
+ To load a parsed DTD file:
+ <orderedlist>
+ <listitem>
+ <para>Open an XML file in Emacs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Choose <command>DTD -> Load DTD</command> from the pulldown menu
+ and choose the file you saved from the previous step. For
+ instance, choose <filename>docbook.ced</filename>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>You will know it is finished when you see the message
+ <computeroutput>Fontifying...done</computeroutput> at the bottom
+ of your screen. Loading the parsed DTD might take a long time.
+ You can start editing the file before it finishes.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ You can also use the Emacs command <command>Meta-x
+ sgml-load-dtd</command> to load the parsed DTD.
+ </para>
+ </tip>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-basic-commands">
+ <title>Basic Emacs Commands</title>
+
+ <para>
+ The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key.
+ </para>
+
+ <table frame="all" rowsep="1" colsep="1" id="tb-emacs-commands">
+ <title>Emacs Commands</title>
+ <tgroup rowsep="1" colsep="1" cols="2">
+ <colspec colnum="1" colname="shortcut" colwidth="170"/>
+ <colspec colnum="2" colname="description" colwidth="300"/>
+
+ <thead>
+ <row>
+ <entry rowsep="1" colsep="1">Shortcut</entry>
+ <entry rowsep="1" colsep="1">Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry rowsep="1" colsep="1"><keycombo>
+ <keycap>Meta</keycap><keycap>x</keycap></keycombo>
+ sgml-parse-prolog, <keycap>Enter</keycap></entry>
+ <entry>Parse DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-save-dtd, <keycap>Enter</keycap></entry>
+ <entry>Save the Parse DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo> <keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-load-dtd, <keycap>Enter</keycap></entry>
+ <entry>Load DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo> <keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap></keycap></keycombo>, <keycap>Tab</keycap></entry>
+ <entry>Display list of valid tags</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap></keycap> </keycombo>, type beginning of tag,
+ <keycap>Tab</keycap></entry>
+ <entry>Complete the tag</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>g</keycap>
+ </keycombo></entry>
+ <entry>Cancel a command in the minibuffer</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycap>/</keycap></entry>
+ <entry>Close tag</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>a</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to beginning of line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>e</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the end of the line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>Home</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the beginning of the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>End</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the end of the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>k</keycap>
+ </keycombo></entry>
+ <entry>Cut line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>y</keycap>
+ </keycombo></entry>
+ <entry>Paste line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>s</keycap>
+ </keycombo></entry>
+ <entry>Search forward in the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>r</keycap>
+ </keycombo></entry>
+ <entry>Search backwards in the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>$</keycap>
+ </keycombo></entry>
+ <entry>Check spelling of current word</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-word, <keycap>Enter</keycap></entry>
+ <entry>Check spelling of current word</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-buffer, <keycap>Enter</keycap></entry>
+ <entry>Check spelling of current buffer</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap>
+ </keycombo></entry>
+ <entry>Open file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap>
+ </keycombo></entry>
+ <entry>Save file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></entry>
+ <entry>Exit <application>Emacs</application> and prompt to save
+ files if necessary</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap> <keycap>q</keycap>
+ </keycombo></entry>
+ <entry>Fill paragraph</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>a</keycap>
+ </keycombo></entry>
+ <entry>Edit attributes for a tag (for example, you can edit the
+ <computeroutput>url</computeroutput> attribute of the
+ <computeroutput>ulink</computeroutput> tag)</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>,
+ <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></entry>
+ <entry>Exit edit attributes</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-examples">
+ <title>Examples</title>
+
+ <para>
+ The table or reference card of Emacs and PSGML commands can be confusing
+ for beginners. This section provides some examples of how to use them.
+ </para>
+
+ <sect2 id="s2-emacs-tag-completion">
+ <title>Tag Completion</title>
+
+ <note>
+ <title>Note</title>
+ <para>This section assumes that you have already loaded the DTD file
+ (<filename>.ced</filename>).
+ </para>
+ </note>
+
+ <para>
+ Instead of typing a tag each time you need to use it, use
+ the key combination <keycap>Ctrl</keycap>-<keycap>c</keycap>,
+ followed by <keycap><</keycap>. At the bottom of the
+ <application>Emacs</application> window, you will see:
+ </para>
+<screen>
+<computeroutput>Tag: <</computeroutput>
+</screen>
+
+ <para>
+ To view a list of available tags, use either the <keycap>Tab</keycap>
+ or <keycap>?</keycap>. Or, if you know the first few letters of a tag,
+ you can enter them followed by <keycap>Tab</keycap> for a complete
+ list of available tags beginning with those letters or for a tag
+ completion.
+ </para>
+
+ <para>
+ Try the following: Type <keycap>Ctrl</keycap>-<keycap>c</keycap>
+ followed by <keycap><</keycap>. Then enter the letter
+ <keycap>k</keycap>, followed by <keycap>Tab</keycap>. You may have to
+ use the <keycap>Tab</keycap> key several times to get a complete list.
+ </para>
+
+ <para>
+ The output should look similar to the example below:
+ </para>
+
+<screen>
+<computeroutput>
+Click mouse-2 on a completion to select it.
+In this buffer, type RET to select the completion near point.
+
+Possible completions are:
+<keycap> <keycode>
+<keycombo> <keysym>
+</computeroutput>
+</screen>
+
+ </sect2>
+ <sect2 id="s2-emacs-tag-closing">
+ <title>Tag Closure</title>
+
+ <para>
+ Once you have started the tag of choice, you must close it. The easiest
+ way to close an open tag is to use the keycombo
+ <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by
+ <keycap>/</keycap>. This will close the closest open tag you have.
+ </para>
+
+ </sect2>
+
+ <sect2 id="s2-emacs-other">
+ <title>Other Emacs Tasks</title>
+
+ <para>
+ <guilabel>Working with one window</guilabel>: Sometimes in
+ <application>Emacs</application> the window becomes split (with tags
+ completions or other text in the bottom window). The easiest way to
+ get it back so that only your XML and text appear on one screen is to
+ use the keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap>, followed by
+ <keycap>1</keycap>.
+ </para>
+
+ <para>
+ <guilabel>Saving your work</guilabel>: To save your work, use the
+ following keycombo, <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>s</keycap>.
+ </para>
+
+ <para>
+ <guilabel>The "clear/quit" command</guilabel>: I have found on some
+ occasions that I have gotten too far into the tag completion process and
+ need to just exit back out to my text. The easiest way to do this is the
+ keycombo <keycap>Ctrl</keycap>-<keycap>g</keycap>. This command quits
+ what you have been doing within the file, without quitting the file
+ itself.
+ </para>
+
+ <para>
+ <guilabel>Opening a new file</guilabel>: To open a new file, use the
+ keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>f</keycap>. At the bottom of the emacs
+ window, you will be able to enter in the file name (using
+ <keycap>Tab</keycap> completion if needed) of the file you wish to
+ open.
+ </para>
+
+ <para>
+ <guilabel>Closing emacs</guilabel>: The easiest way to close
+ <application>emacs</application> is to use the keycombo
+ <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>c</keycap>. If you have not saved your work,
+ it will prompt you to save the file, otherwise it will just quit the
+ current emacs session you have been working with.
+ </para>
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-additional-resources">
+ <title>Additional Resources</title>
+
+ <para> Additional Emacs and PSGML references are available at the
+ following locations:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink>
+ — <citetitle>Emacs Quick Reference Guide</citetitle>
+ </para>
+ </listitem>
+ <listitem> <para>Emacs reference card that comes with the
+ <filename>emacs</filename> package. You can print it out as a
+ reference. —
+ <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Read <citetitle>Editing XML with Emacs and PSGML</citetitle>
+ in <filename>/usr/share/doc/psgml-<replaceable><version></replaceable>/psgml.ps</filename>. </para>
+ </listitem>
+ </itemizedlist>
+
+ </sect1>
+ </chapter>
+
+
+
+
+
+
+
+
+
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-emacs.xml,v 1.4 2003/09/16 19:26:26 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/Attic/docs-getting-files-en.xml,v b/old-documentation-guide/Attic/docs-getting-files-en.xml,v
new file mode 100644
index 0000000..7131822
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-getting-files-en.xml,v
@@ -0,0 +1,737 @@
+head 1.11;
+access;
+symbols
+ VERSION-0_2:1.1;
+locks; strict;
+comment @# @;
+
+
+1.11
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.10;
+
+1.10
+date 2005.12.14.15.55.34; author jtr; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2005.12.13.21.56.24; author jtr; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2005.09.19.00.00.31; author pfrields; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2005.08.24.19.41.55; author pfrields; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2005.08.24.12.36.25; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2005.08.24.12.33.05; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2005.08.24.12.30.26; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2005.05.14.20.00.15; author jtr; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2005.05.03.18.45.19; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.11
+log
+ at Remove old files in en locale
+@
+text
+@<!-- $Id: -->
+<!--
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+
+<!ENTITY BOILERPLATE "This header makes editing XML easier" >
+<!ENTITY FDPX "Fedora Docs Project" >
+<!ENTITY FED "Fedora" >
+
+]>
+-->
+<chapter id="ch-getting-files">
+ <title>Prerequisites</title>
+
+ <para>
+ Before you being working with the &FED; documents, you must have certain tools and packages installed on your system.
+ The directions below will help you configure your setup.
+ </para>
+
+ <section id="ch-getting-files-system-packages">
+ <title>System Packages</title>
+ <para>
+ To start working on the Docs Project, you will need the appropriate DocBook XML files, stylesheets, and scripts.
+ The following packages are required:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>xmlto</filename> — for producing HTML and PDF outputs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>docbook-style-xsl</filename> — for the default XSLT stylesheets we build on.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>docbook-dtds</filename> — XML versions of the DocBook DTD
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ You can verify these packages are on your system by:
+ </para>
+
+ <screen>
+ <userinput>
+rpm -q xmlto
+rpm -q docbook-style-xsl
+rpm -q docbook-dtds
+</userinput>
+ </screen>
+
+ <para>
+ Any missing package can be installed using <application>yum(8)</application> this way:
+ </para>
+
+ <screen>
+ <userinput>
+su -c 'yum install xmlto'
+su -c 'yum install docbook-style-xsl'
+su -c 'yum install docbook-dtds'
+</userinput>
+ </screen>
+ </section>
+ <section id="ch-getting-files-fdp">
+ <title>Fedora Documentation Tools</title>
+
+ <para>
+ You need perform these steps only once.
+ These files are common to all the &FDPX; documents.
+ </para>
+
+ <para>
+ The custom scripts and stylesheets used are all stored in CVS on the <computeroutput>cvs.fedora.redhat.com</computeroutput> CVS server.
+ You need to check them out along with the DocBook XML files for the existing docs.
+ </para>
+
+ <para>
+ When you see the password prompt, press the <keycap>Enter</keycap> key.
+ In the example below, we also show how to obtain a copy of an existing &FDPX; document.
+ </para>
+
+ <screen>
+<userinput>mkdir my-fedora-docs-sandbox
+cd my-fedora-docs-sandbox
+export CVSROOT=:pserver:anonymous@@cvs.fedora.redhat.com:/cvs/docs
+cvs login
+cvs co docs-common
+cvs co example-tutorial</userinput>
+</screen>
+ </section>
+ <section id="ch-getting-files-filenames">
+ <title>Filename Conventions</title>
+ <para>
+ &FDPX; provides the tools, scripts, and stylesheets to transform your <abbrev>XML</abbrev> documents into either <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev> output formats.
+ In addition, your document can automatically be built into an <abbrev>RPM</abbrev> package.
+ </para>
+ <para>
+ To take advantage of these services, you should follow our conventions for naming your files.
+ While you may choose whatever filenames you like, adopting our practices will make your life simpler.
+ Of course, if you are bringing your own document into our building system, changing hundreds of filenames may seem quite a burden; relax, we can use your filenames with just a little work on your part.
+ Read on to find out how.
+ </para>
+ <section id="ch-getting-files-filenames-doc">
+ <title>Document Filenames</title>
+ <para>
+ Each document lives in a peer directory to the <filename>docs-common</filename> directory you extracted from the &FED; archive earlier.
+ Name your document directory something related to its subject, just avoid any name already taken.
+ The <userinput>cvs co -c</userinput> command mentioned earlier will show you the names already taken.
+ </para>
+ </section>
+ <section id="ch-getting-files-i18n">
+ <title>Anticipating I18N Translation</title>
+ <para>
+ The &FDPX; includes an active translation team.
+ Project documents are often translated into several languages.
+ By convention, the translated files share the directory with the original files; filenames must be unique.
+ </para>
+ <para>
+ &FDPX; filenames are constructed appending a dash followed by the <abbrev>ISO</abbrev> language symbol before any file extention.
+ For example, a file whose language content is <abbrev>US</abbrev> English could be named <filename>mydoc-en.xml</filename>; the file containing its Chinese translation would then be named <filename>mydoc-zh_CN.xml</filename>, and so on.
+ </para>
+ <para>
+ To assist this effort, the document build system assumes that each file is tagged with its <abbrev>I18N</abbrev> locale.
+ Our filename convention is shown in <xref linkend="ch-getting-files-i18n-table"/>
+ </para>
+ <table id="ch-getting-files-i18n-table">
+ <title>&FDPX; Filename Conventions</title>
+ <tgroup cols="2">
+ <colspec align="right" colnum="1" colwidth="*1"/>
+ <colspec colnum="2" colwidth="*5"/>
+ <thead>
+ <row>
+ <entry>
+ <phrase>Compoment</phrase>
+ </entry>
+ <entry>
+ <phrase>Description</phrase>
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <phrase><replaceable>anything_but_dash</replaceable></phrase>
+ </entry>
+ <entry>
+ <para>
+ The initial portion of a filename can be anything, as long as <emphasis>no dash</emphasis> is used.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase><filename>-</filename></phrase>
+ </entry>
+ <entry>
+ <para>
+ A dash (<filename>-</filename>) is to be used only to introduce the <systemitem class="macro">${LANG}</systemitem> filename component.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase><systemitem class="macro">${LANG}</systemitem></phrase>
+ </entry>
+ <entry>
+ <para>
+ The <systemitem class="macro">${LANG}</systemitem> component identifies the <wordasword>locale</wordasword> for the file content.
+ </para>
+ <para>
+ In addition to helping classify files according to their language content, we also use the <systemitem class="macro">${LANG}</systemitem> value as an <abbrev>UTF-8</abbrev> locale when rendering the document.
+ For example, the document <filename>mydoc-it.xml</filename>will be rendered using <systemitem class="resource">it.UTF-8</systemitem> as the language environment.
+ </para>
+ <para>
+ For more information on <abbrev>I18N</abbrev> localization, visit the <ulink url="http://www.openi18n.org"/> web site.
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <warning>
+ <title>Document Filenames Are Special</title>
+ <para>
+ The main file in your document <emphasis>must</emphasis> follow the file naming convention or the document building system cannot find it.
+ </para>
+ </warning>
+ </section>
+ </section>
+ <section id="ch-getting-files-build-system">
+ <title>The Document Build System</title>
+ <para>
+ Common tasks such as rendering the document into either <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev> can be performed easily using the document building system.
+ </para>
+ <para>
+ The building system heavily leverages the <application>make(1)</application> tool and shell scripts to automate these activities, but authors need <emphasis>no</emphasis> prior experience with either shell scripts or a <filename>Makefile</filename>.
+ While individual documents do have their own <filename>Makefile</filename>, it is only a few lines long and very simple.
+ The document <filename>Makefile</filename> content is designed for cut'n paste.
+ </para>
+ <para>
+ As an example, <xref linkend="ch-getting-files-build-system-makefile"/> shows the whole <filename>Makefile</filename> for a simple document having only one file and one language.
+ </para>
+ <example id="ch-getting-files-build-system-makefile">
+ <title>Sample Document Makefile</title>
+<programlisting width="60">
+DOCBASE = mydoc
+LANGUAGES = en
+XMLEXTRAFILES-en=
+include ../docs-common/Makefile.common
+</programlisting>
+</example>
+ <para>
+ Our main <abbrev>XML</abbrev> file is <filename>mydoc-en.xml</filename>; no translation has been done yet.
+ </para>
+ <para>
+ The <systemitem class="macro">LANGUAGES</systemitem> definition lists the English locale <literal>en</literal>; when other translations become available, their locale will just be appended to this definition.
+ </para>
+ <para>
+ Our document has only the main file <filename>mydoc-en.xml</filename>, but other documents may be split over several files.
+ The <systemitem class="macro">XMLEXTRAFILES-en</systemitem> definition catalogs these additional files so that the document building system can watch them for changes and rebuild the document when necesssary.
+ This definition is just a simple list of files.
+ </para>
+ <para>
+ The final line, beginning with <literal>include</literal>, references the main <filename>Makefile</filename> for the build system.
+ The <filename>Makefile.common</filename> file contains all the <application>make(1)</application> targets and rules to actually build the document and the various archives.
+ </para>
+ <para>
+ Add new document translations by:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Add the translated document files to the document directory.
+ Be sure to use the proper <systemitem class="macro">${LANG}</systemitem> filename component to keep the filenames similar, but unique.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Edit the <filename>Makefile</filename> to append the new <systemitem class="macro">${LANG}</systemitem> to the <systemitem class="macro">LANGUAGES</systemitem> definition.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Create a new <systemitem class="macro">XMLEXTRAFILES-${LANG}</systemitem> definition that references any document files other than the base file.
+ </para>
+ </listitem>
+ </orderedlist>
+ <section id="ch-getting-files-build-system-targets">
+ <title>Build System Actions</title>
+ <para>
+ To render the <abbrev>XML</abbrev> document into <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev> the command: <userinput>make html</userinput>,
+ <userinput>make html-nochunk</userinput>, or <userinput>make pdf</userinput> may be used.
+ </para>
+ <para>
+ <xref linkend="ch-getting-files-build-system-targets-table"/> lists the defined build system targets.
+ </para>
+ <table id="ch-getting-files-build-system-targets-table">
+ <title>Document Building Targets</title>
+ <tgroup cols="2">
+ <colspec align="right" colnum="1" colwidth="*1"/>
+ <colspec colnum="2" colwidth="*5"/>
+ <thead>
+ <row>
+ <entry><phrase>Target</phrase></entry>
+ <entry><phrase>Description</phrase></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><phrase><filename>all</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds the <abbrev>HTML</abbrev>, and the <abbrev>PDF</abbrev> forms of the document in all its defined translations.
+ </para>
+ <para>
+ Also builds the archives, such as <application>tar(1)</application> and <application>rpm(8)</application>.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>tarball</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <application>tar(1)</application> archive for all document languages.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>pdf</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <abbrev>PDF</abbrev> document for all document languages.
+ </para>
+ <para>
+ Currently, <abbrev>PDF</abbrev> production is problematic and probably will not work for your document.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>html</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <abbrev>HTML</abbrev> document for each defined translation.
+ Output is placed in a separate directory:
+ <systemitem class="macro">${DOCBASE}</systemitem><filename>-</filename><systemitem class="macro">${LANG}</systemitem><filename>/</filename>; each document section is given its own file within that directory.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>html-nochunks</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <abbrev>HTML</abbrev> document for each defined translation.
+ Output is placed in a single file:
+ <systemitem class="macro">${DOCBASE}</systemitem><filename>-</filename><systemitem class="macro">${LANG}</systemitem><filename>.html</filename>; no other files are created.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>clean</filename></phrase></entry>
+ <entry>
+ <para>
+ Deletes any temporary, or generated files.
+ Does <emphasis>not</emphasis> erase any <abbrev>HTML</abbrev>, <abbrev>PDF</abbrev>, or archive files.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>distclean</filename></phrase></entry>
+ <entry>
+ <para>
+ Erases all <abbrev>HTML</abbrev>, <abbrev>PDF</abbrev>, and archive files.
+ Automatically invokes the <filename>clean</filename> target as well.
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>
+ You can add your own special targets and rules by placing them at the bottom of the document <filename>Makefile</filename>, below the <literal>include</literal> line.
+ </para>
+ <para>
+ Be sure to follow your target definitions with a double colon, not just one.
+ This will allow you to supply extra steps for the defined targets.
+ </para>
+ </section>
+ <section id="ch-getting-files-build-system-images">
+ <title>Using Document Image Files</title>
+ <para>
+ Image files, such as <filename>.PNG</filename>, are often used in documents.
+ While your image files may be placed anywhere you like, we recommend that you store your image files in a <filename>figs/</filename> subdirectory within your document directory.
+ In other words, place your image <filename>picture.png</filename> in the <filename>mydoc/figs/picture.png</filename> file.
+ </para>
+ <note>
+ <title>Use PNG Images, Not JPG</title>
+ <para>
+ Depending on the output media, sometimes images may be scaled,
+ streteched, or squashed.
+ To minimize any distortions, we recommend that you use only
+ <wordasword>PDF</wordasword> images and avoid <wordasword>JPG</wordasword> files.
+ </para>
+ <para>
+ You may find the <systemitem class="filesystem">convert(1)</systemitem> program, from the <application>ImageMagick</application> <abbrev>RPM</abbrev> package, provides a convenient way to reformat any <wordasword>JPG</wordasword> images you already have.
+ </para>
+ </note>
+ <para>
+ You may organize your image files into as many subdirectories under <filename>figs/</filename> as you choose.
+ The document building system will recreate your image subdirectory structure in the output documents.
+ </para>
+ <para>
+ In addition, we recommend that you follow our convention on naming the image.
+ For example, an image often contains a caption or other text.
+ This text should be translated along with the document content, so keeping <filename>words-en.png</filename> separate from <filename>words-ru.png</filename> is a good practice.
+ An image file with no text can be named just <filename>picture.png</filename>, for example.
+ </para>
+ <para>
+ Sometimes, a document may require images that do not follow the naming convention.
+ You may still use these images with the document building system, but it requires that you create an ordinary text file containing the image filenames you want to use.
+ This file must be named <filename>figs/Manifest-</filename><systemitem class="macro">${LANG}</systemitem> so that the build system can find it as the search for image filenames begins.
+ </para>
+ <para>
+ An easy way to create the <filename>figs/Manifest-</filename><systemitem class="macro">${LANG}</systemitem> file is shown in <xref linkend="ch-getting-files-build-system-manifest"/>.
+ </para>
+ <example id="ch-getting-files-build-system-manifest">
+ <title>Building A Manifest</title>
+<programlisting>
+rm -f figs/Manifest-en
+find figs -print >/tmp/manifest
+mv /tmp/manifest figs/Manifest-en
+vi figs/Manifest-en
+</programlisting>
+</example>
+
+ </section>
+ </section>
+</chapter>
+@
+
+
+1.10
+log
+ at Fixed minor typo's. Added admonition about preferring PNG to JPG.
+@
+text
+@@
+
+
+1.9
+log
+ at Added documentation about the document building system. Dropped the
+one-line "converting" chapter by creating a "Prerequisites" section
+in the "getting-files" section.
+@
+text
+ at d203 1
+a203 1
+ The document <filename>Makefile</filename> content is designed for cut's paste.
+d354 1
+a354 1
+ <title>Finding Document Image Files</title>
+d360 12
+d380 1
+@
+
+
+1.8
+log
+ at Fix CVS guidance for publication
+@
+text
+ at d4 1
+a4 1
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+d6 3
+a8 1
+ <!ENTITY BOILERPLATE "This header makes editing XML easier" >
+d13 1
+a13 1
+ <title>Getting the Files</title>
+d15 7
+d23 3
+a25 4
+ To start working on the Docs Project, you will need the appropriate
+ DocBook XML files, stylesheets, and scripts. The following packages are
+ required:
+ </para>
+d29 3
+a31 1
+ <para><filename>xmlto</filename> — for producing HTML and PDF outputs</para>
+d34 3
+a36 2
+ <para><filename>docbook-style-xsl</filename> — for the default XSLT stylesheets we
+ build on</para>
+d39 3
+a41 1
+ <para><filename>docbook-dtds</filename> — XML versions of the DocBook DTD</para>
+d46 30
+a75 5
+ The custom scripts and stylesheets used are all stored in CVS on the
+ <computeroutput>cvs.fedora.redhat.com</computeroutput> CVS server.
+ You need to check them out along with the DocBook XML files for the
+ existing docs.
+ </para>
+d78 3
+a80 4
+ You should perform these steps only once, when you first make a checkout
+ from docs CVS. When you see the password prompt, press the
+ <keycap>Enter</keycap> key.
+ </para>
+d82 8
+a89 3
+<screen>
+<userinput>mkdir my-fedora-docs
+cd my-fedora-docs
+d95 125
+a219 1
+
+d221 1
+a221 6
+ When you perform an anonymous CVS checkout, you can view the files and
+ retreive the latest versions. You cannot add (commit) any updates or new
+ files back to the repository. To commit changes to CVS, you must have
+ <abbrev>CVS</abbrev> write access. Refer to <ulink
+ url="http://fedoraproject.org/wiki/DocsProject/NewWriters"/> to learn
+ about getting write access to <abbrev>CVS</abbrev>.
+a222 1
+
+d224 3
+a226 1
+ To see a list of the available documents:
+a227 3
+
+<screen><userinput>cvs co -c</userinput></screen>
+
+d229 2
+a230 1
+ Pick your document of interest and then download it to your working directory:
+a231 3
+
+<screen><userinput>cvs co example-tutorial</userinput></screen>
+
+d233 1
+a233 5
+ Except for the <citetitle>&IG;</citetitle>, all documentation in CVS must
+ be tutorials written in DocBook XML article format using the template in
+ the <filename>example-tutorial</filename> directory. Each tutorial
+ <emphasis>must</emphasis> be in its own directory. No XML files should be
+ in the root directory.
+d235 155
+a389 2
+
+ </chapter>
+@
+
+
+1.7
+log
+ at Oops, fix one other extraneous prompt... sorry quaid
+@
+text
+ at d50 2
+a51 1
+cvs co docs-setup</userinput>
+@
+
+
+1.6
+log
+ at Ugh, stupid spelling error
+@
+text
+ at d66 1
+a66 1
+<screen><prompt>$ </prompt><command>cvs co -c</command></screen>
+@
+
+
+1.5
+log
+ at Trivial style change, remove superfluous adverb
+@
+text
+ at d55 1
+a55 1
+ retreive the latest versions. You can not add (commit) any updates or new
+@
+
+
+1.4
+log
+ at Clean up CVS instructions a bit, removing excess tagging in screens, some style changes
+@
+text
+ at d41 1
+a41 1
+ from docs CVS. When you see the password prompt, just press the
+@
+
+
+1.3
+log
+ at 1) Changed to reflect the updated CVS arrangement with modules as "top-level"
+ objects.
+
+2) Changed URL for :pserver: CVS access.
+
+3) Added short section on :ext: CVS access with reference to the WIKI doc.
+@
+text
+ at a34 3
+ </para>
+
+ <para>
+d40 3
+a42 2
+ Get started by following these once-only steps.
+ When asked for a <abbrev>CVS</abbrev> password, just press the <guibutton>ENTER</guibutton> key.
+d46 5
+a50 6
+<prompt>$ </prompt><command>mkdir my-fedora-docs</command>
+<prompt>$ </prompt><command>cd my-fedora-docs</command>
+<prompt>$ </prompt><command>export CVSROOT=:pserver:anonymous@@cvs.fedora.redhat.com:/cvs/docs</command>
+<prompt>$ </prompt><command>cvs login</command>
+<enter>
+<prompt>$ </prompt><command>cvs co docs-setup</command>
+d54 6
+a59 6
+ Checking the files out anonymously means that you can view them and
+ retreive the latest versions, but you can not add (commit) any updates or
+ new files back to the repository.
+ You need <abbrev>CVS</abbrev> write access for that; check with the
+ <ulink url="http://fedoraproject.org/wiki/DocsProject/NewWriters"><filename>http://fedoraproject.org/wiki/DocsProject/NewWriters</filename></ulink>
+ site to learn about getting write access to <abbrev>CVS</abbrev>.
+d72 1
+a72 1
+<screen><prompt>$ </prompt><command>cvs co example-tutorial</command></screen>
+d75 3
+a77 3
+ Except for the <citetitle>&IG;</citetitle>, all docs must be tutorials
+ written in DocBook XML article format using the template in the
+ <filename>example-tutorial</filename> directory. Each tutorial
+@
+
+
+1.2
+log
+ at Updated CVS instructions to use new server location
+@
+text
+ at d1 10
+a10 3
+<!-- $Id: docs-getting-files-en.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+
+ <chapter id="ch-getting-files">
+d21 1
+a21 1
+ <para><filename>xmlto</filename> — for producing HTML and PDF outputs</para>
+d24 2
+a25 2
+ <para><filename>docbook-style-xsl</filename> — for the default XSLT stylesheets we
+ build on</para>
+d28 1
+a28 1
+ <para><filename>docbook-dtds</filename> — XML versions of the DocBook DTD</para>
+d34 1
+a34 1
+ <computeroutput>rhlinux.redhat.com</computeroutput> CVS server.
+d43 2
+a44 1
+ To check out the scripts anonymously:
+d48 6
+a53 3
+<command>export CVSROOT=:pserver:anonymous@@cvs.fedora.redhat.com:/cvs/docs</command>
+<command>cvs -z3 login</command>
+<command>cvs -z3 co fedora-docs</command>
+d60 3
+d66 12
+d82 1
+a82 3
+ in the root directory except for files shared by all documents such
+ <filename>legalnotice.xml</filename>, which must be included in all docs
+ so that the FDL is used for all docs.
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-getting-files.xml,v 1.4 2003/09/16 19:26:26 tfox Exp $ -->
+d40 1
+a40 1
+<command>export CVSROOT=:pserver:anonymous@@rhlinux.redhat.com:/usr/local/CVS</command>
+@
+
diff --git a/old-documentation-guide/Attic/docs-getting-files-zh_CN.xml,v b/old-documentation-guide/Attic/docs-getting-files-zh_CN.xml,v
new file mode 100644
index 0000000..e32bd28
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-getting-files-zh_CN.xml,v
@@ -0,0 +1,378 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.17.13.28.38; author bbbush; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id: --><!--
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+
+<!ENTITY BOILERPLATE "This header makes editing XML easier" >
+<!ENTITY FDPX "Fedora Docs Project" >
+<!ENTITY FED "Fedora" >
+
+]>
+--><chapter id="ch-getting-files">
+ <title>先决要求</title>
+ <para>在操作 &FED; 文档之前，您必须安装合适的工具和软件包。下面的步骤将帮您配置系统。</para>
+ <section id="ch-getting-files-system-packages">
+ <title>系统软件包</title>
+ <para>要开始为 Docs Project 贡献力量，您需要适当的 DocBook XML 文件，样式表以及一些脚本。需要安装下列软件包：</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>xmlto</filename> — 生成 HTML 和 PDF 输出。</para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>docbook-style-xsl</filename> — 我们构建时默认的 XSLT 样式单。</para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>docbook-dtds</filename> — DocBook DTD 针对 XML 的版本</para>
+ </listitem>
+ </itemizedlist>
+ <para>您可以这样检查系统中的软件包，运行命令：</para>
+ <screen>
+ <userinput>
+rpm -q xmlto
+rpm -q docbook-style-xsl
+rpm -q docbook-dtds
+</userinput>
+ </screen>
+ <para>如果缺少什么软件包，就用 <application>yum(8)</application> 来安装：</para>
+ <screen>
+ <userinput>
+su -c 'yum install xmlto'
+su -c 'yum install docbook-style-xsl'
+su -c 'yum install docbook-dtds'
+</userinput>
+ </screen>
+ </section>
+ <section id="ch-getting-files-fdp">
+ <title>Fedora 文档工具</title>
+ <para>您只需执行这些步骤一次。这些文件对所有 &FDPX; 文档都是一致的。</para>
+ <para>常用的脚本和样式表都存放在 <computeroutput>cvs.fedora.redhat.com</computeroutput> CVS 服务器的仓库中。您需要将它们以及已有文档的 DocBook XML 文件检出。</para>
+ <para>当您看到密码提示时，按下 <keycap>Enter</keycap> 键。在下面的例子中，我们演示了如何获取一份已有的 &FDPX; 文档的复本。</para>
+ <screen>
+ <userinput>mkdir my-fedora-docs-sandbox
+cd my-fedora-docs-sandbox
+export CVSROOT=:pserver:anonymous@@cvs.fedora.redhat.com:/cvs/docs
+cvs login
+cvs co docs-common
+cvs co example-tutorial</userinput>
+ </screen>
+ </section>
+ <section id="ch-getting-files-filenames">
+ <title>文件名约定</title>
+ <para>&FDPX; 提供了工具、脚本和样式单来将您的 <abbrev>XML</abbrev> 文档转换为 <abbrev>HTML</abbrev> 和 <abbrev>PDF</abbrev> 输出格式。另外，您的文档还可以被自动构建为 <abbrev>RPM</abbrev> 软件包。</para>
+ <para>要利用这些服务，您应当遵循为文件命名的规范。无论选择什么名字，采用我们的建议将使事情简单许多。当然，如果您将自己的文档导入我们的构建系统，修改数以百计的文件名字也许过于繁杂；请放松，只要稍作修改就可以满足要求了。请继续阅读。</para>
+ <section id="ch-getting-files-filenames-doc">
+ <title>文档文件名</title>
+ <para>每个文档有单独的目录，与先前从 &FED; 文档中检出的 <filename>docs-common</filename> 目录并列。将您的文档目录命名为与内容相关的名字，避免使用已有的名称。前面提到的 <userinput>cvs co -c</userinput> 命令可以显示已有的名称。</para>
+ </section>
+ <section id="ch-getting-files-i18n">
+ <title>与 I18N 国际化翻译组合作</title>
+ <para>&FDPX; 包括一支活跃的翻译团队。项目文档被译为多种语言。根据约定，译文与原始文档处于同一目录；文件名必须唯一。</para>
+ <para>&FDPX; 文件名的扩展名前面，必须是一个连字符加上 <abbrev>ISO</abbrev> 语言名称。例如，如果文件内容是 <abbrev>US</abbrev>(美国英语)，可以命名为 <filename>mydoc-en.xml</filename>；而它的简体中文译文将命名为 <filename>mydoc-zh_CN.xml</filename>，以此类推。</para>
+ <para>为了促进这种努力，文档构建系统假定每个文件都包含了 <abbrev>I18N</abbrev> 国际化语言环境标记。我们的文件名约定在 <xref linkend="ch-getting-files-i18n-table"/> 中讲述</para>
+ <table id="ch-getting-files-i18n-table">
+ <title>&FDPX; 文件名约定</title>
+ <tgroup cols="2">
+ <colspec align="right" colnum="1" colwidth="*1"/>
+ <colspec colnum="2" colwidth="*5"/>
+ <thead>
+ <row>
+ <entry>
+ <phrase>组件</phrase>
+ </entry>
+ <entry>
+ <phrase>描述</phrase>
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <phrase>
+ <replaceable>除连字符外的其他字符</replaceable>
+ </phrase>
+ </entry>
+ <entry>
+ <para>文件名的第一部分可以是各种字符，只要<emphasis>不使用连字符(dash)</emphasis>。</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase>
+ <filename>-</filename>
+ </phrase>
+ </entry>
+ <entry>
+ <para>连字符 (<filename>-</filename>) 用来引入 <systemitem class="macro">${LANG}</systemitem> 文件名组件。</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase>
+ <systemitem class="macro">${LANG}</systemitem>
+ </phrase>
+ </entry>
+ <entry>
+ <para>
+ <systemitem class="macro">${LANG}</systemitem> 组件区分了文件内容的 <wordasword>locale</wordasword>(语言环境)。</para>
+ <para>除了根据语言区分文件外，我们还用 <systemitem class="macro">${LANG}</systemitem> 的值作为输出文档时的 <abbrev>UTF-8</abbrev> 语言环境。例如，文档 <filename>mydoc-it.xml</filename> 在渲染时会使用 <systemitem class="resource">it.UTF-8</systemitem> 作为语言环境。</para>
+ <para>有关更多 <abbrev>I18N</abbrev> 本地化的信息请访问 <ulink url="http://www.openi18n.org"/> 网站。</para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <warning>
+ <title>文档文件名是特别的</title>
+ <para>文档的主控文件 <emphasis>必须</emphasis> 依据文件命名约定，否则构建系统无法找到它。</para>
+ </warning>
+ </section>
+ </section>
+ <section id="ch-getting-files-build-system">
+ <title>文档构建系统</title>
+ <para>一般的工作，类似将文档渲染为 <abbrev>HTML</abbrev> 或 <abbrev>PDF</abbrev> 可以很容易地用文档构建系统实现。</para>
+ <para>构建系统依赖于 <application>make(1)</application> 工具和 shell 脚本的强大功能，来自动完成这些工作。但是，作为作者，<emphasis>无须</emphasis> 有使用 shell 脚本或 <filename>Makefile</filename> 的经验。尽管每篇文档都拥有自己的 <filename>Makefile</filename>，它通常只有几行的长度，非常简单。文件 <filename>Makefile</filename> 的内容被设计为可以拷贝 'n 粘贴。</para>
+ <para>例如，<xref linkend="ch-getting-files-build-system-makefile"/> 显示了一个简单文档(只有一个文件，且只有一种语言)的完整 <filename>Makefile</filename>。</para>
+ <example id="ch-getting-files-build-system-makefile">
+ <title>示例文档 Makefile(编译控制文件)</title>
+ <programlisting width="60">
+DOCBASE = mydoc
+LANGUAGES = en
+XMLEXTRAFILES-en=
+include ../docs-common/Makefile.common
+</programlisting>
+ </example>
+ <para>我们的主控 <abbrev>XML</abbrev> 文件是 <filename>mydoc-en.xml</filename>；尚未添加翻译。</para>
+ <para>
+ <systemitem class="macro">LANGUAGES</systemitem> 定义列出了英语的语言环境 <literal>en</literal>；如果出现了其他翻译，只要将它们的语言环境追加在这个定义中。</para>
+ <para>这份文档只包括主控文件 <filename>mydoc-en.xml</filename>，但是其他文档也许被划分为多个文件。 <systemitem class="macro">XMLEXTRAFILES-en</systemitem> 定义可以记录附加文件，这样在文件被改动时，构建系统就会注意到，并且在需要的时候重新构建文档。这个定义只是简单的文件列表。</para>
+ <para>最后一行，以 <literal>include</literal>(包含)开始，引用了主控的构建系统的 <filename>Makefile</filename>。<filename>Makefile.common</filename> 文件包含了所有 <application>make(1)</application> 目标以及规则，用来实际地构建文档以及各种文件。</para>
+ <para>添加新的文档翻译：</para>
+ <orderedlist>
+ <listitem>
+ <para>将已翻译的文件添加到文档目录。一定要用正确的 <systemitem class="macro">${LANG}</systemitem> 文件名组件，使文件名相似而唯一。</para>
+ </listitem>
+ <listitem>
+ <para>编辑 <filename>Makefile</filename>，追加新的 <systemitem class="macro">${LANG}</systemitem> 到 <systemitem class="macro">LANGUAGES</systemitem> 定义中。</para>
+ </listitem>
+ <listitem>
+ <para>创建新的 <systemitem class="macro">XMLEXTRAFILES-${LANG}</systemitem> 定义，以引用除了主控文件之外的所有其他受影响的文档文件。</para>
+ </listitem>
+ </orderedlist>
+ <section id="ch-getting-files-build-system-targets">
+ <title>构建系统动作</title>
+ <para>要将 <abbrev>XML</abbrev> 文旦渲染为 <abbrev>HTML</abbrev> 或 <abbrev>PDF</abbrev>，运行命令： <userinput>make html</userinput>, <userinput>make html-nochunk</userinput>, 或 <userinput>make pdf</userinput>。</para>
+ <para>
+ <xref linkend="ch-getting-files-build-system-targets-table"/> 列出了已定义的构建系统目标。</para>
+ <table id="ch-getting-files-build-system-targets-table">
+ <title>文档构建目标</title>
+ <tgroup cols="2">
+ <colspec align="right" colnum="1" colwidth="*1"/>
+ <colspec colnum="2" colwidth="*5"/>
+ <thead>
+ <row>
+ <entry>
+ <phrase>目标</phrase>
+ </entry>
+ <entry>
+ <phrase>描述</phrase>
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <phrase>
+ <filename>all</filename>
+ </phrase>
+ </entry>
+ <entry>
+ <para>构建 <abbrev>HTML</abbrev>, 和 <abbrev>PDF</abbrev> 格式的文档，包括所有的译本。</para>
+ <para>同时构建打包，包括 <application>tar(1)</application> 和 <application>rpm(8)</application>。</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase>
+ <filename>tarball</filename>
+ </phrase>
+ </entry>
+ <entry>
+ <para>只构建 <application>tar(1)</application> 打包，针对所有文档语言。</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase>
+ <filename>pdf</filename>
+ </phrase>
+ </entry>
+ <entry>
+ <para>只构建 <abbrev>PDF</abbrev> 文档，针对所有文档语言。</para>
+ <para>当前，<abbrev>PDF</abbrev> 生成还有问题，可能无法使用。</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase>
+ <filename>html</filename>
+ </phrase>
+ </entry>
+ <entry>
+ <para>只构建 <abbrev>HTML</abbrev> 文档，针对每种翻译。输出被放在单独的目录中：<systemitem class="macro">${DOCBASE}</systemitem><filename>-</filename><systemitem class="macro">${LANG}</systemitem><filename>/</filename>；每一节在那个目录中都有对应的文件。</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase>
+ <filename>html-nochunks</filename>
+ </phrase>
+ </entry>
+ <entry>
+ <para>只构建 <abbrev>HTML</abbrev> 文档，针对每种翻译。输出是一个单独的文件：<systemitem class="macro">${DOCBASE}</systemitem><filename>-</filename><systemitem class="macro">${LANG}</systemitem><filename>.html</filename>；不会创建其他文件。</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase>
+ <filename>clean</filename>
+ </phrase>
+ </entry>
+ <entry>
+ <para>删除所有临时文件和生成的文件。<emphasis>不会</emphasis> 删除任何 <abbrev>HTML</abbrev>, <abbrev>PDF</abbrev>, 或文件打包。</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase>
+ <filename>distclean</filename>
+ </phrase>
+ </entry>
+ <entry>
+ <para>删除所有 <abbrev>HTML</abbrev>, <abbrev>PDF</abbrev>, 和文件打包。同时自动执行 <filename>clean</filename> 目标。</para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>您可以添加自己特定的目标和规则，只要将它们添加在文件 <filename>Makefile</filename> 的最后，在 <literal>include</literal> 一行的下面。</para>
+ <para>在您的目标定义后面一定要用双冒号，不能只用一个。这样，您就可以为已定义的目标添加步骤了。</para>
+ </section>
+ <section id="ch-getting-files-build-system-images">
+ <title>使用文档图象文件</title>
+ <para>图象文件，例如 <filename>.PNG</filename>，通常会在文档中用到。尽管文档可以存放在任何地方，我们建议您将图象文件存放在文档目录的 <filename>figs/</filename> 子目录中。换句话说，图象 <filename>picture.png</filename> 应该是 <filename>mydoc/figs/picture.png</filename> 文件。</para>
+ <note>
+ <title>使用 PNG 图象，不要用 JPG</title>
+ <para>根据输出媒介不同，有时图象会被缩放，拉伸或压缩。为了减少变形，我们建议您只使用 <wordasword>PNG</wordasword> 图象，避免 <wordasword>JPG</wordasword> 文件。</para>
+ <para>您会发现 <systemitem class="filesystem">convert(1)</systemitem> 程序，来自 <application>ImageMagick</application><abbrev>RPM</abbrev> 软件包，提供了转换已有的 <wordasword>JPG</wordasword> 文件的好办法。</para>
+ </note>
+ <para>您可以将图象文件组织为 <filename>figs/</filename> 目录下的子目录。文档构建系统会在输出文档中复制图象子目录的结构。</para>
+ <para>另外，我们建议您遵循文件名命名的约定。例如，一幅图象经常会包含标题或其他文本。这些文本应当像文档内容一样被翻译，因此区分 <filename>words-en.png</filename> 与 <filename>words-ru.png</filename> 是个好主意。不包含文本的图象文件可以简单地命名为 <filename>picture.png</filename> 之类。</para>
+ <para>有时，文档需要使用不遵循命名约定的图象。您可以在文档构建系统中使用这些图象，但是您必须创建一个文本文件，列出要使用的图象文件名。这个文件必须命名为 <filename>figs/Manifest-</filename><systemitem class="macro">${LANG}</systemitem>，这样构建系统就可以在搜索图象文件名时找到它。</para>
+ <para>创建 <filename>figs/Manifest-</filename><systemitem class="macro">${LANG}</systemitem> 文件的简单办法是 <xref linkend="ch-getting-files-build-system-manifest"/>。</para>
+ <example id="ch-getting-files-build-system-manifest">
+ <title>构建一份清单(Manifest)</title>
+ <programlisting>
+rm -f figs/Manifest-en
+find figs -print >/tmp/manifest
+mv /tmp/manifest figs/Manifest-en
+vi figs/Manifest-en
+</programlisting>
+ </example>
+ </section>
+ </section>
+</chapter>
+@
+
+
+1.2
+log
+ at update build part
+@
+text
+@@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+ at d4 1
+a4 1
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+d6 3
+a8 1
+ <!ENTITY BOILERPLATE "This header makes editing XML easier" >
+d12 44
+a55 21
+ <title>下载文件</title>
+ <para>要开始为 Docs Project 贡献力量，您需要适当的 DocBook XML 文件，样式表以及一些脚本。需要安装下列软件包：</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>xmlto</filename> — 生成 HTML 和 PDF 版本的输出</para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>docbook-style-xsl</filename> — 我们默认使用的 XSLT 样式表</para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>docbook-dtds</filename> — DocBook DTD 针对 XML 的版本</para>
+ </listitem>
+ </itemizedlist>
+ <para>常用的脚本和样式表都存放在 <computeroutput>cvs.fedora.redhat.com</computeroutput> CVS 服务器的仓库中。您需要将它们以及已有文档的 DocBook XML 文件检出。</para>
+ <para>您应当只在第一次从 docs CVS 检出时，做这些动作。当您看到密码提示时，按下 <keycap>Enter</keycap>。</para>
+ <screen>
+ <userinput>mkdir my-fedora-docs
+cd my-fedora-docs
+d60 226
+a285 11
+ </screen>
+ <para>当您进行匿名 CVS 检出时，您可以检视文件并获取更新的版本。您不可以添加或提交更新到服务器中。要提交修改，必须有 <abbrev>CVS</abbrev> 写权限。关于获取 <abbrev>CVS</abbrev> 写权限请参考 <ulink url="http://fedoraproject.org/wiki/DocsProject/NewWriters"/>。</para>
+ <para>要查看已有文档的列表：</para>
+ <screen>
+ <userinput>cvs co -c</userinput>
+ </screen>
+ <para>选择您感兴趣的文档，然后下载到工作目录：</para>
+ <screen>
+ <userinput>cvs co example-tutorial</userinput>
+ </screen>
+ <para>除了 <citetitle>&IG;</citetitle> 之外，CVS 中所有文档必须是 DocBook XML article 格式，使用 <filename>example-tutorial</filename> 目录中的模板。每个文档 <emphasis>必须</emphasis> 有自己的目录。根目录中不允许有 XML 文件。</para>
+@
+
diff --git a/old-documentation-guide/Attic/docs-getting-files.xml,v b/old-documentation-guide/Attic/docs-getting-files.xml,v
new file mode 100644
index 0000000..5a925fd
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-getting-files.xml,v
@@ -0,0 +1,101 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2003.11.21.22.40.39; author tfox; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at change filenames to end with -en.xml
+@
+text
+@<!-- $Id: docs-getting-files.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+
+ <chapter id="ch-getting-files">
+ <title>Getting the Files</title>
+
+ <para>
+ To start working on the Docs Project, you will need the appropriate
+ DocBook XML files, stylesheets, and scripts. The following packages are
+ required:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><filename>xmlto</filename> — for producing HTML and PDF outputs</para>
+ </listitem>
+ <listitem>
+ <para><filename>docbook-style-xsl</filename> — for the default XSLT stylesheets we
+ build on</para>
+ </listitem>
+ <listitem>
+ <para><filename>docbook-dtds</filename> — XML versions of the DocBook DTD</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The custom scripts and stylesheets used are all stored in CVS on the
+ <computeroutput>rhlinux.redhat.com</computeroutput> CVS server.
+ </para>
+
+ <para>
+ You need to check them out along with the DocBook XML files for the
+ existing docs.
+ </para>
+
+ <para>
+ To check out the scripts anonymously:
+ </para>
+
+<screen>
+<command>export CVSROOT=:pserver:anonymous@@rhlinux.redhat.com:/usr/local/CVS</command>
+<command>cvs -z3 login</command>
+<command>cvs -z3 co fedora-docs</command>
+</screen>
+
+ <para>
+ Checking the files out anonymously means that you can view them and
+ retreive the latest versions, but you can not add (commit) any updates or
+ new files back to the repository.
+ </para>
+
+ <para>
+ Except for the <citetitle>&IG;</citetitle>, all docs must be tutorials
+ written in DocBook XML article format using the template in the
+ <filename>example-tutorial</filename> directory. Each tutorial
+ <emphasis>must</emphasis> be in its own directory. No XML files should be
+ in the root directory except for files shared by all documents such
+ <filename>legalnotice.xml</filename>, which must be included in all docs
+ so that the FDL is used for all docs.
+ </para>
+
+ </chapter>
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-getting-files.xml,v 1.4 2003/09/16 19:26:26 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/Attic/docs-intro-en.xml,v b/old-documentation-guide/Attic/docs-intro-en.xml,v
new file mode 100644
index 0000000..196ace6
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-intro-en.xml,v
@@ -0,0 +1,120 @@
+head 1.4;
+access;
+symbols
+ VERSION-0_2:1.2;
+locks; strict;
+comment @# @;
+
+
+1.4
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.3;
+
+1.3
+date 2004.08.13.16.08.48; author tfox; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2004.01.19.23.14.46; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.4
+log
+ at Remove old files in en locale
+@
+text
+@<!-- $Id: docs-intro-en.xml,v 1.3 2004/08/13 16:08:48 tfox Exp $ -->
+
+ <preface id="ch-intro">
+ <title>Introduction</title>
+
+ <para>
+ The goal of the Docs Project is to create easy-to-follow, task-based
+ documentation for &FC; users and developers. Other than the
+ <citetitle>&IG;</citetitle>, each tutorial should be in DocBook XML
+ article format, with one article per topic. This way, writers can
+ contribute documentation about a specific topic without having to worry
+ about how it fits into a manual or how it flows with other topics.
+ </para>
+
+ <para>
+ The following tools are used:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>DocBook XML v4.1</para>
+ </listitem>
+ <listitem>
+ <para>Custom XSLT stylesheets for both print and HTML versions</para>
+ </listitem>
+ <listitem>
+ <para>Custom scripts to generate PDF and HTML output (use <command>xmlto</command>)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs with PSGML mode (optional, but recommended)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs with nXML mode (optional, but also recommended)</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The purpose of this document is to explain the tools used by the Docs
+ Project as well as to provide writing and tagging guidelines so that the
+ documentation is consistent and easy-to-follow.
+ </para>
+
+ </preface>
+@
+
+
+1.3
+log
+ at use common entities file
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-intro-en.xml,v 1.2 2004/01/19 23:14:46 tfox Exp $ -->
+@
+
+
+1.2
+log
+ at add Gavin's patch for nxml
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-intro-en.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+d8 1
+a8 1
+ documentation for &DISTRO; users and developers. Other than the
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-intro.xml,v 1.3 2003/09/16 19:26:26 tfox Exp $ -->
+d31 3
+@
+
diff --git a/old-documentation-guide/Attic/docs-intro-zh_CN.xml,v b/old-documentation-guide/Attic/docs-intro-zh_CN.xml,v
new file mode 100644
index 0000000..d2512ce
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-intro-zh_CN.xml,v
@@ -0,0 +1,77 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.17.13.28.38; author bbbush; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id: docs-intro-zh_CN.xml,v 1.2 2005/12/17 13:28:38 bbbush Exp $ --><preface id="ch-intro">
+ <title>介绍</title>
+ <para>Docs Project 的目标是为 &FC; 用户和开发者创建易于维护，基于任务的文档。除了 <citetitle>&IG;</citetitle> 之外，所有文档必须是 DocBook XML article 格式，每个主题一篇文章。这样，作者就可以专注于撰写一个主题，不必考虑它如何排版为一个手册，或如何与其他主题协调。</para>
+ <para>要用到的工具：</para>
+ <itemizedlist>
+ <listitem>
+ <para>DocBook XML v4.1</para>
+ </listitem>
+ <listitem>
+ <para>自定义的打印版本和 HTML 版本的 XSLT 样式表</para>
+ </listitem>
+ <listitem>
+ <para>自定义的脚本，以生成 PDF 版本和 HTML 版本的输出 (使用 <command>xmlto</command>)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs PSGML 模式 (可选，推荐使用)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs nXML 模式 (可选，同样推荐使用)</para>
+ </listitem>
+ </itemizedlist>
+ <para>本文档的目的是解释 Docs Project 使用的工具，同时提供写作约定和标记约定，使文档一致且易于维护。</para>
+</preface>
+@
+
+
+1.2
+log
+ at update build part
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: docs-intro-en.xml,v 1.3 2004/08/13 16:08:48 tfox Exp $ --><preface id="ch-intro">
+@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+@@
+
diff --git a/old-documentation-guide/Attic/docs-intro.xml,v b/old-documentation-guide/Attic/docs-intro.xml,v
new file mode 100644
index 0000000..d79b878
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-intro.xml,v
@@ -0,0 +1,80 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2003.11.21.22.40.39; author tfox; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at change filenames to end with -en.xml
+@
+text
+@<!-- $Id: docs-intro.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+
+ <preface id="ch-intro">
+ <title>Introduction</title>
+
+ <para>
+ The goal of the Docs Project is to create easy-to-follow, task-based
+ documentation for &DISTRO; users and developers. Other than the
+ <citetitle>&IG;</citetitle>, each tutorial should be in DocBook XML
+ article format, with one article per topic. This way, writers can
+ contribute documentation about a specific topic without having to worry
+ about how it fits into a manual or how it flows with other topics.
+ </para>
+
+ <para>
+ The following tools are used:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>DocBook XML v4.1</para>
+ </listitem>
+ <listitem>
+ <para>Custom XSLT stylesheets for both print and HTML versions</para>
+ </listitem>
+ <listitem>
+ <para>Custom scripts to generate PDF and HTML output (use <command>xmlto</command>)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs with PSGML mode (optional, but recommended)</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The purpose of this document is to explain the tools used by the Docs
+ Project as well as to provide writing and tagging guidelines so that the
+ documentation is consistent and easy-to-follow.
+ </para>
+
+ </preface>
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-intro.xml,v 1.3 2003/09/16 19:26:26 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/Attic/docs-rh-guidelines-en.xml,v b/old-documentation-guide/Attic/docs-rh-guidelines-en.xml,v
new file mode 100644
index 0000000..eb7e1fd
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-rh-guidelines-en.xml,v
@@ -0,0 +1,647 @@
+head 1.3;
+access;
+symbols
+ VERSION-0_2:1.1;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2004.08.31.15.45.29; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old files in en locale
+@
+text
+@ <chapter id="ch-rh-guidelines">
+ <title>&RH; Documentation Guidelines</title>
+
+ <indexterm>
+ <primary>recursion</primary>
+ <see>recursion</see>
+ </indexterm>
+
+ <indexterm>
+ <primary>RTFM</primary>
+ <secondary>read the f*'ing manual</secondary>
+ <seealso>humor</seealso>
+ </indexterm>
+
+ <indexterm>
+ <primary>humor</primary>
+ <secondary>RTFM</secondary>
+ </indexterm>
+
+ <para>Please read this chapter carefully. This chapter describes the
+ guidelines that must be followed such as naming conventions.
+ </para>
+
+ <sect1 id="s1-xml-guidelines-naming">
+ <title>ID Naming Conventions</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>naming conventions</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>naming conventions</primary>
+ </indexterm>
+
+ <para>You will see certain ID names referred to below and this will
+ help to explain how we come up with those names. For example:
+ </para>
+
+<screen>
+<computeroutput>
+<chapter id="ch-uniquename">
+
+<sect3="s3-install-make-disks">
+
+<figure id="fig-redhat-config-kickstart-basic">
+</computeroutput>
+</screen>
+
+ <para>IDs are unique identifiers, allowing DocBook XML to know where to
+ cross-reference a section or chapter or the like.
+ </para>
+
+ <para>The general rules for defining an ID are:</para>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>naming conventions</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+
+ <itemizedlist>
+ <listitem>
+ <para>Keep it 32 characters or under (this is counted as
+ everything between the quotation marks)</para>
+ </listitem>
+ <listitem>
+ <para>Keep it as short and simple as possible</para>
+ </listitem>
+ <listitem>
+ <para>Make sure the name is relevant to the information (make it
+ recognizable)</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>Some examples are <command>"ch-uniquename"</command> (with 13
+ characters) and <command>"s3-install-make-disks"</command> (with 21
+ characters).
+ </para>
+
+ <para>A section within a particular chapter always uses the chapter
+ name (minus the <command>"ch-"</command>) in its ID. For example, you
+ are working with the <command>"ch-intro"</command> chapter and need to
+ create your first section on disk partitions. That section ID would look
+ similar to <command>"s1-intro-partition"</command> which contains the
+ section number, the main chapter ID, and a unique ID for that section.
+ </para>
+
+ <table id="tb-xml-namingconventions">
+ <title>Naming Conventions</title>
+
+ <tgroup cols="2">
+ <colspec colnum="1" colname="tag" colwidth="100"/>
+ <colspec colnum="2" colname="prefix" colwidth="100"/>
+ <thead>
+ <row>
+ <entry>Tag</entry>
+ <entry>Prefix</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><command>preface</command></entry>
+ <entry><computeroutput>pr-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>chapter</command></entry>
+ <entry><computeroutput>ch-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>section</command></entry>
+ <entry><computeroutput>sn-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect1</command></entry>
+ <entry><computeroutput>s1-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect2</command></entry>
+ <entry><computeroutput>s2-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect3</command></entry>
+ <entry><computeroutput>s3-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect4</command></entry>
+ <entry><computeroutput>s4-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>figure</command></entry>
+ <entry><computeroutput>fig-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>table</command></entry>
+ <entry><computeroutput>tb-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>appendix</command></entry>
+ <entry><computeroutput>ap-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>part</command></entry>
+ <entry><computeroutput>pt-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>example</command></entry>
+ <entry><computeroutput>ex-</computeroutput></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect1>
+
+ <sect1 id="s1-xml-guidelines-header">
+ <title>File Header</title>
+
+ <para>
+ All the files must contain the CVS Id header.
+ </para>
+
+ <para>
+ If you create a new file, the first line must be:
+ </para>
+<screen>
+<computeroutput>
+<!-- $Id: -->
+</computeroutput>
+</screen>
+
+ <para>
+ The first time it is committed to CVS (and every time it is committed to
+ CVS) the line is updated automatically to include information about the
+ file. For example:
+ </para>
+
+<screen>
+<computeroutput>
+<!-- $Id: docs-rh-guidelines-en.xml,v 1.2 2004/08/31 15:45:29 tfox Exp $ -->
+</computeroutput>
+</screen>
+
+ </sect1>
+
+ <sect1 id="s1-xml-admon">
+ <title>Admonitions</title>
+
+ <indexterm>
+ <primary>admonitions</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>warning</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>tip</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>caution</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>important</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>warning</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>tip</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>note</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>caution</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>important</tertiary>
+ </indexterm>
+
+ <para>There are five types of admonitions in DocBook: Caution, Important,
+ Note, Tip, and Warning.</para>
+
+ <para>All of the admonitions have the same structure: an optional Title
+ followed by paragraph-level elements. The DocBook DTD does not impose any
+ specific semantics on the individual admonitions. For example, DocBook
+ does not mandate that Warnings be reserved for cases where bodily harm can
+ result.</para>
+
+
+ <sect2 id="s2-xml-notesetc">
+ <title>Creating Notes, Tips, Cautions, Importants, and Warnings</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>tip</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>caution</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>important</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>warning</secondary>
+ </indexterm>
+
+ <para>There are several ways to bring attention to text within a
+ document. A <emphasis>Note</emphasis> is used to bring additional
+ information to the users' attention. A <emphasis>Tip</emphasis> is
+ used to show the user helpful information or another way to do
+ something. A <emphasis>Caution</emphasis> is used to show the user
+ they must be careful when attempting a certain step. An
+ <emphasis>Important</emphasis> tag set can be used to show the user a
+ piece of information that should not be overlooked. While this
+ information may not change anything the user is doing, it should show
+ the user that this piece of information could be vital. A
+ <emphasis>Warning</emphasis> is used to show the reader that their
+ current setup will change or be altered, such as files being removed,
+ and they should not choose this operation unless they are alright with
+ the consequences.</para>
+
+ <para>The following lines of code will show the basic setup for each
+ case as mentioned above, along with an example of how it would be
+ displayed in the HTML.</para>
+
+
+<screen>
+<computeroutput>
+<note>
+<title>Note</title>
+<para>Body of text goes here.</para>
+</note>
+</computeroutput>
+</screen>
+
+ <note>
+ <title>Note</title> <para>Body of text goes here.</para>
+ </note>
+
+
+<screen>
+<computeroutput>
+<tip>
+<title>Tip</title>
+<para>Body of text goes here.</para>
+</tip>
+</computeroutput>
+</screen>
+
+ <tip>
+ <title>Tip</title>
+ <para>Body of text goes here</para>
+ </tip>
+
+<screen>
+<computeroutput>
+<caution>
+<title>Caution</title>
+<para>Body of text goes here.</para>
+</caution>
+</computeroutput>
+</screen>
+
+ <caution>
+ <title>Caution</title> <para>Body of text goes here.</para>
+ </caution>
+
+
+<screen>
+<computeroutput>
+<important>
+<title>Important</title>
+<para>Body of text goes here.</para>
+</important>
+</computeroutput>
+</screen>
+
+ <important>
+ <title>Important</title>
+ <para>Body of text goes here.</para>
+ </important>
+
+<screen>
+<computeroutput>
+<warning>
+<title>Warning</title>
+<para>Body of text goes here.</para>
+</warning>
+</computeroutput>
+</screen>
+
+ <warning>
+ <title>Warning</title> <para>Body of text goes here.</para>
+ </warning>
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-screenshots">
+ <title>Screenshots</title>
+
+ <indexterm>
+ <primary>screenshots</primary>
+ <secondary>how to take</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>screen captures</primary>
+ <see>screenshots</see>
+ </indexterm>
+ <indexterm>
+ <primary>screen grabs</primary>
+ <see>screenshots</see>
+ </indexterm>
+
+ <para>
+ There are two types of screenshots: graphical and textual. The
+ philosophy on using these two types is <firstterm>rely on text over
+ graphics</firstterm>. This means, if you can say it in text instead of
+ showing a graphic, do so. A graphical screenshot of a GUI can create a good
+ setting of objects to then describe textually, but you don't want to create
+ a screenshot for each graphical step.
+ </para>
+ <para>
+ The main reason for this preference is that a block of text can usually
+ convey more meaning than the same physical space of graphics. This is
+ highly dependent on the graphic; obviously, a photographic image of a
+ scene can convey more than 1000 words can. A GUI screenshot is usually
+ full of blank space with a few elements that can just as easily be
+ described or listed.
+ </para>
+ <para>
+ The steps for taking a graphical screenshot illustrate how using text to
+ describe a procedure is more concise than a series of screenshots.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Graphical Screenshot</term>
+ <listitem>
+ <procedure>
+ <step>
+ <para>
+ Set the theme to Bluecurve defaults. This gives a look that
+ is familiar to most readers, and makes &FDP; documents
+ consistent. From the panel menu, choose
+ <guimenu>Preferences</guimenu>,
+ <guimenuitem>Theme</guimenuitem> and select
+ <guimenuitem>Bluecurve</guimenuitem> from the theme list.
+ </para>
+ </step>
+ <step>
+ <para>
+ Set fonts to Bluecurve defaults as well. From the panel menu,
+ choose <guimenu>Preferences</guimenu>,
+ <guimenuitem>Fonts</guimenuitem>. Set the
+ <guilabel>Application font</guilabel> and the
+ <guilabel>Desktop font</guilabel> to Sans Regular 10. Set the
+ <guilabel>Window Title font</guilabel> to Sans Bold 10. Set
+ the <guilabel>Terminal font</guilabel> to Monospace Regular
+ 10.
+ </para>
+ </step>
+ <step>
+ <para>
+ Before taking the screenshot, try to resize the targeted GUI
+ element(s) to the smallest possible size they can be. Your
+ target is an image of 500 pixels or less. If you are doing a
+ screenshot of more than one GUI element, you may need to
+ resize the screenshot in a following step.
+ </para>
+ </step>
+ <step>
+ <para>
+ To take the screenshot, select the GUI element with your
+ mouse, bringing it to the forefront, or otherwise arranging
+ the elements. Press <keycombo> <keycap>Alt</keycap>
+ <keycap>Print Screen</keycap> </keycombo> to capture a single
+ GUI window. For capturing the entire desktop use
+ <keycap>Print Screen</keycap>. If you are taking a shot of
+ multiple elements and have grouped them closely together, you
+ can crop the resulting image in <application>The
+ GIMP</application>. The image will be in the PNG format.
+ </para>
+ </step>
+ <step>
+ <para>
+ If you need to, you can resize using <application>The
+ GIMP</application>. With the image open, right-click on it
+ and choose <guimenu>Image</guimenu> -> <guimenuitem>Scale
+ Image...</guimenuitem>. With the chain symbol intact, set the
+ <guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>,
+ and click <guibutton>OK</guibutton>. Be sure to <keycombo>
+ <keycap>Ctrl</keycap> <keycap>s</keycap> </keycombo> to save
+ your changes to your PNG before converting to EPS.
+ </para>
+ </step>
+ <step>
+ <para>
+ With the image open in <application>The GIMP</application>,
+ right-click on the image, selecting <guimenu>File</guimenu>
+ -> <guimenuitem>Save As...</guimenuitem>. Under
+ <guimenu>Determine File Type:</guimenu>, select
+ <guimenuitem>PostScript</guimenuitem>, then click
+ <guibutton>OK</guibutton>. Allow flattening of the image by
+ clicking <guibutton>Export</guibutton>.
+ </para>
+ <para>
+ In the <guilabel>Save as PostScript</guilabel> window, select
+ <guilabel>Encapsulated PostScript</guilabel>, and click
+ <guibutton>OK</guibutton>.
+ </para>
+ </step>
+ </procedure>
+ <para>
+ For more information about calling the images from the XML, refer
+ to <xref linkend="s1-xml-tags-figure"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Text Screenshot</term>
+ <listitem>
+ <para>Textual screen information is also useful for readers. If you
+ use a graphical screenshot to illustrate a function, and the
+ textual mode has identical functions, you should not include
+ both, unless omitting either would make your description
+ unclear. You should make your information generic over specific.
+ Omit the username and machine information, and separate what the
+ user types from sample command output. Also, in
+ <command>screen</command> tags, what the user types should be in
+ <command>userinput</command> tags, and what the user is shown as
+ output should be in <command>computeroutput</command> tags.
+ For example, the usage in
+ <xref linkend="ex-text-screenshot-bad"/> should look like <xref
+ linkend="ex-text-screenshot-good"/>.
+ </para>
+ <example id="ex-text-screenshot-bad">
+ <title>Incorrect Textual Screenshot</title>
+ <screen>
+<userinput>ps ax | grep ssh</userinput>
+<computeroutput>
+ 2564 ? S 0:23 /usr/sbin/sshd
+ 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
+ 8235 ? S 0:00 ssh -Nf rocky@@philadelphia.net -L 6667:localhost
+17223 pts/0 S 0:00 ssh rbalboa@@core-router7
+17227 pts/2 S 0:10 ssh rbalboa@@smbshare2
+21113 pts/7 S 1:19 ssh rocky@@xxx.private
+</computeroutput>
+ </screen>
+ </example>
+ <example id="ex-text-screenshot-good">
+ <title>Correct Textual Screenshot</title>
+ <para>
+ To find all the currently active ssh sessions, execute the
+ following command:
+ </para>
+<screen>
+<command>ps ax | grep ssh</command>
+</screen>
+
+ <para>
+ The output will appear similar to:
+ </para>
+
+ <screen>
+<computeroutput>
+ 2564 ? S 0:23 /usr/sbin/sshd
+ 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
+ 8032 pts/0 S 0:00 ssh user@@host.example.com
+ 8032 pts/1 S 0:00 ssh root@@backup.example.com
+</computeroutput>
+ </screen>
+ </example>
+ <para>
+ For more information about using screen, refer to <xref
+ linkend="s1-xml-tags-screen"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect1>
+
+ <sect1 id="s1-diagrams-images">
+ <title>Diagrams and Images</title>
+
+ <indexterm>
+ <primary>images</primary>
+ </indexterm>
+ <indexterm>
+ <primary>diagrams</primary>
+ <secondary>creating</secondary>
+ </indexterm>
+
+ <para>
+ To be written
+ </para>
+
+ </sect1>
+
+ </chapter>
+
+
+
+
+@
+
+
+1.2
+log
+ at add instructions for screenshots
+@
+text
+ at d184 1
+a184 1
+<!-- $Id: docs-rh-guidelines-en.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d184 1
+a184 1
+<!-- $Id: docs-rh-guidelines.xml,v 1.3 2003/09/16 19:26:26 tfox Exp $ -->
+d191 1
+a191 1
+ <title>Working with Admonitions</title>
+d381 200
+@
+
diff --git a/old-documentation-guide/Attic/docs-rh-guidelines-zh_CN.xml,v b/old-documentation-guide/Attic/docs-rh-guidelines-zh_CN.xml,v
new file mode 100644
index 0000000..0e3feb7
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-rh-guidelines-zh_CN.xml,v
@@ -0,0 +1,468 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.17.13.28.38; author bbbush; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<chapter id="ch-rh-guidelines">
+ <title>&RH; 文档撰写约定</title>
+ <indexterm>
+ <primary>recursion</primary>
+ <see>recursion</see>
+ </indexterm>
+ <indexterm>
+ <primary>RTFM</primary>
+ <secondary>read the f*'ing manual</secondary>
+ <seealso>humor</seealso>
+ </indexterm>
+ <indexterm>
+ <primary>humor</primary>
+ <secondary>RTFM</secondary>
+ </indexterm>
+ <para>请仔细阅读本章。本章描述了必须遵循的约定，例如命名约定。</para>
+ <sect1 id="s1-xml-guidelines-naming">
+ <title>ID 命名约定</title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>命名约定</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>命名约定</primary>
+ </indexterm>
+ <para>后面您将看到这样的 ID 命名。它们有助于理解这些命名的含义。例如：</para>
+ <screen>
+ <computeroutput>
+<chapter id="ch-uniquename">
+
+<sect3="s3-install-make-disks">
+
+<figure id="fig-redhat-config-kickstart-basic">
+</computeroutput>
+ </screen>
+ <para>ID 是独一无二的标识符，使得 DocBook XML 得知如何交叉参考章、节等等。</para>
+ <para>定义 ID 的一般规则如下：</para>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>定义 ID 的规则</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>命名约定</primary>
+ <secondary>定义 ID 的规则</secondary>
+ </indexterm>
+ <itemizedlist>
+ <listitem>
+ <para>至多使用 32 个字母 (这里指的是引号中所有内容)</para>
+ </listitem>
+ <listitem>
+ <para>尽量短小而简单</para>
+ </listitem>
+ <listitem>
+ <para>确保命名与内容相关 (使它可辨识)</para>
+ </listitem>
+ </itemizedlist>
+ <para>例如，<command>"ch-uniquename"</command> (有 13 个字母) 以及 <command>"s3-install-make-disks"</command> (有 21 个字母)。</para>
+ <para>特定一章中的小节应当在 ID 中包含这一章的名称 (这一章的 ID 去掉 <command>"ch-"</command>)。例如，您在撰写 <command>"ch-intro"</command> 一章，需要将有关磁盘分区的内容作为第一节时，小节 ID 将类似于 <command>"s1-intro-partition"</command>，它包含了小节编号，这一章的 ID 以及这一节的独一无二的 ID。</para>
+ <table id="tb-xml-namingconventions">
+ <title>命名约定</title>
+ <tgroup cols="2">
+ <colspec colname="tag" colnum="1" colwidth="100"/>
+ <colspec colname="prefix" colnum="2" colwidth="100"/>
+ <thead>
+ <row>
+ <entry>标记</entry>
+ <entry>前缀</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <command>前言</command>
+ </entry>
+ <entry>
+ <computeroutput>pr-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>chapter</command>
+ </entry>
+ <entry>
+ <computeroutput>ch-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>节</command>
+ </entry>
+ <entry>
+ <computeroutput>sn-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>第一节</command>
+ </entry>
+ <entry>
+ <computeroutput>s1-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>第二节</command>
+ </entry>
+ <entry>
+ <computeroutput>s2-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>第三节</command>
+ </entry>
+ <entry>
+ <computeroutput>s3-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>第四节</command>
+ </entry>
+ <entry>
+ <computeroutput>s4-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>figure</command>
+ </entry>
+ <entry>
+ <computeroutput>fig-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>table</command>
+ </entry>
+ <entry>
+ <computeroutput>tb-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>附录</command>
+ </entry>
+ <entry>
+ <computeroutput>ap-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>part</command>
+ </entry>
+ <entry>
+ <computeroutput>pt-</computeroutput>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <command>example</command>
+ </entry>
+ <entry>
+ <computeroutput>ex-</computeroutput>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </sect1>
+ <sect1 id="s1-xml-guidelines-header">
+ <title>文件头</title>
+ <para>所有文件必须包含 CVS Id 头部。</para>
+ <para>如果您创建了一个新文件，第一行必须是：</para>
+ <screen>
+ <computeroutput>
+<!-- $Id: -->
+</computeroutput>
+ </screen>
+ <para>它被提交到 CVS 中时 (在每次提交时)，这一行都会自动更新，以包含关于文件的信息。例如：</para>
+ <screen>
+ <computeroutput>
+<!-- $Id: -->
+</computeroutput>
+ </screen>
+ </sect1>
+ <sect1 id="s1-xml-admon">
+ <title>创建提示</title>
+ <indexterm>
+ <primary>提示</primary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>警告</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>技巧</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>注意</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>小心</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>重要</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>提示</secondary>
+ <tertiary>警告</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>提示</secondary>
+ <tertiary>技巧</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>提示</secondary>
+ <tertiary>注意</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>提示</secondary>
+ <tertiary>小心</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>提示</secondary>
+ <tertiary>重要</tertiary>
+ </indexterm>
+ <para>DocBook 中有五种提示类型：小心，重要，注意，技巧和警告。</para>
+ <para>所有提示都有类似的结构：可选的标题，随后是段落级的元素。DocBook DTD 没有定义每种提示的特殊语义。例如，DocBook 并未规定警告必须用于可能造成重大损失的情况。</para>
+ <sect2 id="s2-xml-notesetc">
+ <title>创建技巧，注意，小心，重要和警告提示</title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>注意</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>技巧</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>小心</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>重要</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>警告</secondary>
+ </indexterm>
+ <para>有很多方法来使文档中的文本引人注意。<emphasis>Note</emphasis> 用于显示附加信息。<emphasis>Tip</emphasis> 用于显示完成任务的其他方法。<emphasis>Caution</emphasis> 用于告诫用户在尝试某一步时必须小心。<emphasis>Important</emphasis> 用于提醒用户不可忽视的信息，尽管用户动作不受影响，但是必须提醒用户信息的重要性。<emphasis>Warning</emphasis> 用于提醒读者，他们的设置将被修改或变动，例如文件将被删除，如果他们在意这一后果，就不应继续动作。</para>
+ <para>下列代码将展示上面每种情况的写法，同时也展示了 HTML 显示效果。</para>
+ <screen>
+ <computeroutput>
+<note>
+<title>注意</title>
+<para>文本内容</para>
+</note>
+</computeroutput>
+ </screen>
+ <note>
+ <title>注意</title> <para>文本内容</para></note>
+ <screen>
+ <computeroutput>
+<tip>
+<title>技巧</title>
+<para>文本内容</para>
+</tip>
+</computeroutput>
+ </screen>
+ <tip>
+ <title>技巧</title>
+ <para>文本内容</para>
+ </tip>
+ <screen>
+ <computeroutput>
+<caution>
+<title>小心</title>
+<para>文本内容</para>
+</caution>
+</computeroutput>
+ </screen>
+ <caution>
+ <title>小心</title> <para>文本内容</para></caution>
+ <screen>
+ <computeroutput>
+<important>
+<title>重要</title>
+<para>文本内容</para>
+</important>
+</computeroutput>
+ </screen>
+ <important>
+ <title>注意</title>
+ <para>文本内容</para>
+ </important>
+ <screen>
+ <computeroutput>
+<warning>
+<title>警告</title>
+<para>文本内容</para>
+</warning>
+</computeroutput>
+ </screen>
+ <warning>
+ <title>警告</title> <para>文本内容</para></warning>
+ </sect2>
+ </sect1>
+ <sect1 id="s1-screenshots">
+ <title>屏幕截图</title>
+ <indexterm>
+ <primary>屏幕截图</primary>
+ <secondary>如何截取</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>屏幕快照</primary>
+ <see>屏幕截图</see>
+ </indexterm>
+ <indexterm>
+ <primary>屏幕抓图</primary>
+ <see>屏幕截图</see>
+ </indexterm>
+ <para>有两种类型的屏幕截图：图象和文本。选择它们的原则是 <firstterm>尽量使用文本截图</firstterm>。这意味着，如果您可以用文本而不是图象来表达，那么就用文本。GUI 的图象截图可以首先引入一些对象，然后用文字加以描述，但是您不会总是为每一步都创建一副截图。</para>
+ <para>这样选择的主要目的是文本块通常比占据相同空间的图象包含更多信息。这和具体图象有关，某个场景的准确的截图也许抵得上一千字的效果。GUI 的截图通常有很大空白，只包含很少元素，这样便于描述或列举。</para>
+ <para>截取图象的步骤本身表明了，使用文字来描述一个过程比起一系列的屏幕截图要精确许多。</para>
+ <variablelist>
+ <varlistentry>
+ <term>图象截图</term>
+ <listitem>
+ <procedure>
+ <step>
+ <para>设置主题为默认主题。这样读者会熟悉这一外观，也使得 &FDP; 文档显得一致。从菜单中，选择 <guimenu>Preferences</guimenu>, <guimenuitem>Theme</guimenuitem> 然后选 <guimenuitem>Bluecurve</guimenuitem> (&FC; 4 不再使用 Bluecurve)。</para>
+ </step>
+ <step>
+ <para>设置字体为默认值。从菜单中，选择 <guimenu>Preferences</guimenu>, <guimenuitem>Fonts</guimenuitem>. 然后设置 <guilabel>Application font</guilabel> 和 <guilabel>Desktop font</guilabel> 为 Sans Regular 10。设置 <guilabel>Window Title font</guilabel> 为 Sans Bold 10。设置 <guilabel>Terminal font</guilabel> 为 Monospace Regular 10。</para>
+ </step>
+ <step>
+ <para>在截图之前，试着将目标 GUI 元素调整到尽可能小。您的目标应当是 500 像素或更小。如果您需要截取超过一个 GUI 元素，可以按照下面的步骤来缩放图象。</para>
+ </step>
+ <step>
+ <para>要截取图象，使用鼠标选择 GUI 元素，将它放到最前，或者调整元素排列。按下 <keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> 来截取单个 GUI 窗口。要抓去整个桌面，按下 <keycap>Print Screen</keycap>。如果您要截取包含很多元素的图象，并已将它们靠近，那么还可以在 <application>The GIMP</application> 中裁减结果图象到适当大小。截取的图象将是 PNG 格式。</para>
+ </step>
+ <step>
+ <para>如果需要，您可以使用 <application>The GIMP</application> 缩放图象。打开图象，在图象上点击右键，选择 <guimenu>Image</guimenu> -> <guimenuitem>Scale Image...</guimenuitem>。保持长宽比不变，设置 <guilabel>New Width</guilabel> 为 <guilabel>500 px</guilabel>，然后点击 <guibutton>OK</guibutton>。记住在转换为 EPS 之前按下 <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo> 保存图象。</para>
+ </step>
+ <step>
+ <para>仍使用 <application>The GIMP</application> 编辑图象，在图象上点击右键，选择 <guimenu>File</guimenu> -> <guimenuitem>Save As...</guimenuitem>。在 <guimenu>Determine File Type:</guimenu> 列表中，选择 <guimenuitem>PostScript</guimenuitem>，然后点击 <guibutton>OK</guibutton>。点击 <guibutton>Export</guibutton>，允许平整图象。</para>
+ <para>在 <guilabel>Save as PostScript</guilabel> 窗口，选择 <guilabel>Encapsulated PostScript</guilabel>，然后点击 <guibutton>OK</guibutton>。</para>
+ </step>
+ </procedure>
+ <para>关于如何在 XML 中调用图象，请参考 <xref linkend="s1-xml-tags-figure"/>。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>文本截图</term>
+ <listitem>
+ <para>文本的屏幕信息对读者也很有用。如果您可以同时用图象和文本截图描述某个功能，就不要同时包含它们，除非忽略任何一个都将使描述不清楚。您应当使得信息更加通用。忽略用户名和主机名信息，区分用户的输入与示例的输出。在 <command>screen</command> 标记中，用户输入应当包含在 <command>userinput</command> 标记内，而用户看到的输出应当包含在 <command>computeroutput</command> 标记内。例如，<xref linkend="ex-text-screenshot-bad"/> 的用法应该改为这样 <xref linkend="ex-text-screenshot-good"/></para>
+ <example id="ex-text-screenshot-bad">
+ <title>不正确的文本截图</title>
+ <screen>
+ <userinput>ps ax | grep ssh</userinput>
+ <computeroutput>
+ 2564 ? S 0:23 /usr/sbin/sshd
+ 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
+ 8235 ? S 0:00 ssh -Nf rocky@@philadelphia.net -L 6667:localhost
+17223 pts/0 S 0:00 ssh rbalboa@@core-router7
+17227 pts/2 S 0:10 ssh rbalboa@@smbshare2
+21113 pts/7 S 1:19 ssh rocky@@xxx.private
+</computeroutput>
+ </screen>
+ </example>
+ <example id="ex-text-screenshot-good">
+ <title>正确的文本截图</title>
+ <para>要显示所有当前活动的 ssh 会话，执行下列命令：</para>
+ <screen>
+ <command>ps ax | grep ssh</command>
+ </screen>
+ <para>输出将类似于：</para>
+ <screen>
+ <computeroutput>
+ 2564 ? S 0:23 /usr/sbin/sshd
+ 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
+ 8032 pts/0 S 0:00 ssh user@@host.example.com
+ 8032 pts/1 S 0:00 ssh root@@backup.example.com
+</computeroutput>
+ </screen>
+ </example>
+ <para>关于 screen 标记，请参考 <xref linkend="s1-xml-tags-screen"/>。</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect1>
+ <sect1 id="s1-diagrams-images">
+ <title>图表和图象</title>
+ <indexterm>
+ <primary>images</primary>
+ </indexterm>
+ <indexterm>
+ <primary>图表</primary>
+ <secondary>创建</secondary>
+ </indexterm>
+ <para>待编辑</para>
+ </sect1>
+</chapter>
+@
+
+
+1.2
+log
+ at update build part
+@
+text
+@@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+ at d184 1
+a184 1
+<!-- $Id: docs-rh-guidelines-en.xml,v 1.2 2004/08/31 15:45:29 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/Attic/docs-rh-guidelines.xml,v b/old-documentation-guide/Attic/docs-rh-guidelines.xml,v
new file mode 100644
index 0000000..4d721d7
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-rh-guidelines.xml,v
@@ -0,0 +1,426 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2003.11.21.22.40.39; author tfox; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at change filenames to end with -en.xml
+@
+text
+@ <chapter id="ch-rh-guidelines">
+ <title>&RH; Documentation Guidelines</title>
+
+ <indexterm>
+ <primary>recursion</primary>
+ <see>recursion</see>
+ </indexterm>
+
+ <indexterm>
+ <primary>RTFM</primary>
+ <secondary>read the f*'ing manual</secondary>
+ <seealso>humor</seealso>
+ </indexterm>
+
+ <indexterm>
+ <primary>humor</primary>
+ <secondary>RTFM</secondary>
+ </indexterm>
+
+ <para>Please read this chapter carefully. This chapter describes the
+ guidelines that must be followed such as naming conventions.
+ </para>
+
+ <sect1 id="s1-xml-guidelines-naming">
+ <title>ID Naming Conventions</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>naming conventions</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>naming conventions</primary>
+ </indexterm>
+
+ <para>You will see certain ID names referred to below and this will
+ help to explain how we come up with those names. For example:
+ </para>
+
+<screen>
+<computeroutput>
+<chapter id="ch-uniquename">
+
+<sect3="s3-install-make-disks">
+
+<figure id="fig-redhat-config-kickstart-basic">
+</computeroutput>
+</screen>
+
+ <para>IDs are unique identifiers, allowing DocBook XML to know where to
+ cross-reference a section or chapter or the like.
+ </para>
+
+ <para>The general rules for defining an ID are:</para>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>naming conventions</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+
+ <itemizedlist>
+ <listitem>
+ <para>Keep it 32 characters or under (this is counted as
+ everything between the quotation marks)</para>
+ </listitem>
+ <listitem>
+ <para>Keep it as short and simple as possible</para>
+ </listitem>
+ <listitem>
+ <para>Make sure the name is relevant to the information (make it
+ recognizable)</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>Some examples are <command>"ch-uniquename"</command> (with 13
+ characters) and <command>"s3-install-make-disks"</command> (with 21
+ characters).
+ </para>
+
+ <para>A section within a particular chapter always uses the chapter
+ name (minus the <command>"ch-"</command>) in its ID. For example, you
+ are working with the <command>"ch-intro"</command> chapter and need to
+ create your first section on disk partitions. That section ID would look
+ similar to <command>"s1-intro-partition"</command> which contains the
+ section number, the main chapter ID, and a unique ID for that section.
+ </para>
+
+ <table id="tb-xml-namingconventions">
+ <title>Naming Conventions</title>
+
+ <tgroup cols="2">
+ <colspec colnum="1" colname="tag" colwidth="100"/>
+ <colspec colnum="2" colname="prefix" colwidth="100"/>
+ <thead>
+ <row>
+ <entry>Tag</entry>
+ <entry>Prefix</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><command>preface</command></entry>
+ <entry><computeroutput>pr-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>chapter</command></entry>
+ <entry><computeroutput>ch-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>section</command></entry>
+ <entry><computeroutput>sn-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect1</command></entry>
+ <entry><computeroutput>s1-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect2</command></entry>
+ <entry><computeroutput>s2-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect3</command></entry>
+ <entry><computeroutput>s3-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect4</command></entry>
+ <entry><computeroutput>s4-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>figure</command></entry>
+ <entry><computeroutput>fig-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>table</command></entry>
+ <entry><computeroutput>tb-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>appendix</command></entry>
+ <entry><computeroutput>ap-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>part</command></entry>
+ <entry><computeroutput>pt-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>example</command></entry>
+ <entry><computeroutput>ex-</computeroutput></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect1>
+
+ <sect1 id="s1-xml-guidelines-header">
+ <title>File Header</title>
+
+ <para>
+ All the files must contain the CVS Id header.
+ </para>
+
+ <para>
+ If you create a new file, the first line must be:
+ </para>
+<screen>
+<computeroutput>
+<!-- $Id: -->
+</computeroutput>
+</screen>
+
+ <para>
+ The first time it is committed to CVS (and every time it is committed to
+ CVS) the line is updated automatically to include information about the
+ file. For example:
+ </para>
+
+<screen>
+<computeroutput>
+<!-- $Id: docs-rh-guidelines.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+</computeroutput>
+</screen>
+
+ </sect1>
+
+ <sect1 id="s1-xml-admon">
+ <title>Working with Admonitions</title>
+
+ <indexterm>
+ <primary>admonitions</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>warning</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>tip</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>caution</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>important</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>warning</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>tip</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>note</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>caution</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>important</tertiary>
+ </indexterm>
+
+ <para>There are five types of admonitions in DocBook: Caution, Important,
+ Note, Tip, and Warning.</para>
+
+ <para>All of the admonitions have the same structure: an optional Title
+ followed by paragraph-level elements. The DocBook DTD does not impose any
+ specific semantics on the individual admonitions. For example, DocBook
+ does not mandate that Warnings be reserved for cases where bodily harm can
+ result.</para>
+
+
+ <sect2 id="s2-xml-notesetc">
+ <title>Creating Notes, Tips, Cautions, Importants, and Warnings</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>tip</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>caution</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>important</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>warning</secondary>
+ </indexterm>
+
+ <para>There are several ways to bring attention to text within a
+ document. A <emphasis>Note</emphasis> is used to bring additional
+ information to the users' attention. A <emphasis>Tip</emphasis> is
+ used to show the user helpful information or another way to do
+ something. A <emphasis>Caution</emphasis> is used to show the user
+ they must be careful when attempting a certain step. An
+ <emphasis>Important</emphasis> tag set can be used to show the user a
+ piece of information that should not be overlooked. While this
+ information may not change anything the user is doing, it should show
+ the user that this piece of information could be vital. A
+ <emphasis>Warning</emphasis> is used to show the reader that their
+ current setup will change or be altered, such as files being removed,
+ and they should not choose this operation unless they are alright with
+ the consequences.</para>
+
+ <para>The following lines of code will show the basic setup for each
+ case as mentioned above, along with an example of how it would be
+ displayed in the HTML.</para>
+
+
+<screen>
+<computeroutput>
+<note>
+<title>Note</title>
+<para>Body of text goes here.</para>
+</note>
+</computeroutput>
+</screen>
+
+ <note>
+ <title>Note</title> <para>Body of text goes here.</para>
+ </note>
+
+
+<screen>
+<computeroutput>
+<tip>
+<title>Tip</title>
+<para>Body of text goes here.</para>
+</tip>
+</computeroutput>
+</screen>
+
+ <tip>
+ <title>Tip</title>
+ <para>Body of text goes here</para>
+ </tip>
+
+<screen>
+<computeroutput>
+<caution>
+<title>Caution</title>
+<para>Body of text goes here.</para>
+</caution>
+</computeroutput>
+</screen>
+
+ <caution>
+ <title>Caution</title> <para>Body of text goes here.</para>
+ </caution>
+
+
+<screen>
+<computeroutput>
+<important>
+<title>Important</title>
+<para>Body of text goes here.</para>
+</important>
+</computeroutput>
+</screen>
+
+ <important>
+ <title>Important</title>
+ <para>Body of text goes here.</para>
+ </important>
+
+<screen>
+<computeroutput>
+<warning>
+<title>Warning</title>
+<para>Body of text goes here.</para>
+</warning>
+</computeroutput>
+</screen>
+
+ <warning>
+ <title>Warning</title> <para>Body of text goes here.</para>
+ </warning>
+ </sect2>
+
+ </sect1>
+
+ </chapter>
+
+
+
+
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d184 1
+a184 1
+<!-- $Id: docs-rh-guidelines.xml,v 1.3 2003/09/16 19:26:26 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/Attic/docs-style-en.xml,v b/old-documentation-guide/Attic/docs-style-en.xml,v
new file mode 100644
index 0000000..5f37f7a
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-style-en.xml,v
@@ -0,0 +1,5831 @@
+head 1.8;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.8
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.7;
+
+1.7
+date 2006.11.07.22.41.20; author kwade; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2005.05.01.19.35.20; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2005.04.29.19.10.27; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2005.04.29.18.33.42; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2005.04.28.10.35.41; author kwade; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2005.04.28.09.20.15; author kwade; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.04.28.08.55.41; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.8
+log
+ at Remove old files in en locale
+@
+text
+@<!-- $Id: -->
+
+<chapter id="ch-style">
+
+ <title>Style</title>
+
+ <para>
+ Writing good technical documentation is not simply reproducing
+ command lines and instruction sets. Good documentation is easy to
+ read, understand, and translate, and presents a concise logical
+ progression of concepts. Good documentation can also be defined by
+ what it does <emphasis>not</emphasis> contain. Your tutorial should
+ avoid:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Excessive wordiness
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Unnecessary or undefined jargon
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Grammatical or spelling errors
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ References to yourself or your experiences
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Remarks which might offend or confuse any reader
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ This chapter contains style rules and guidelines for writing &FED;
+ documentation. Guidelines are not the same as rules. It is
+ acceptable to violate a guideline when it makes your material easier
+ to understand. Follow guidelines whenever possible, but follow
+ rules at all times. Assume any advice is a guideline unless
+ identified otherwise.
+ </para>
+
+ <section id="sn-intro-to-style">
+
+ <title>Why Style Is Important</title>
+
+ <para>
+ Writing well comes naturally to almost no one. It is a skill that
+ professional writers, even famous ones, must practice constantly.
+ <firstterm>Style</firstterm>
+ <indexterm><primary>style</primary></indexterm> is the quality
+ that separates elegant writing from the merely functional.
+ </para>
+ <para>
+ Elegance comes in many forms. In prose and poetry, elegant
+ writing may not follow some (or any) common rules of grammar,
+ syntax, or spelling. A good example is Episode 18, "Penelope," in
+ James Joyce's novel <citetitle>Ulysses</citetitle><footnote
+ id='fn-ulysses'>
+ <para>
+ For example, refer to. <ulink
+ url="http://www.online-literature.com/james_joyce/ulysses/18/">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>.
+ Please note that this example contains some mature themes and
+ language, and is not suitable for all readers.
+ </para>
+ </footnote>. There, Joyce uses long streams of words without
+ punctuation to simulate a character's internal consciousness. By
+ violating basic rules of grammar and syntax, Joyce simulates the
+ disorganized but loosely connected thought patterns of the
+ narrator.
+ </para>
+ <para>
+ Technical documentation, however, should always respect these
+ rules. The more a document departs from standard language usage,
+ the more difficult the material becomes for the reader. For
+ example, readers may not be native speakers of the language used,
+ or they might be reading a translation. If the writer uses slang,
+ idioms, or jargon, a reader or translator may easily become
+ confused. The following example compares two different written
+ executions of the same idea:
+ </para>
+ <example>
+ <title>Incorrect style</title>
+
+ <!-- I prefer "incorrect," because I think terms such as
+ "problematic" are mealy-mouthed. They remind me of the late
+ 1980's English textbook trend toward the politically correct yet
+ wholly unhelpful "standard/nonstandard." But then, I tend to be
+ dogmatic; it's probably my Catholic upbringing. [PWF] -->
+
+ <para>
+ So you made the changes I showed you in the last section. What's
+ the next thing you should do? Just pop your thumb drive onto
+ your system and read the <filename>messages</filename> log. When
+ you see "USB device found," then Bob's your uncle.
+ </para>
+ </example>
+ <example>
+ <title>Correct style</title>
+
+ <!-- I prefer "correct." See above. [PWF] -->
+
+ <para>
+ After you complete the configuration changes above, attach the
+ USB removable media to your system. Use the
+ <command>dmesg</command> command to examine the kernel message
+ log. The message <computeroutput>USB device
+ found</computeroutput> indicates that your device was
+ installed successfully.
+ </para>
+ </example>
+ <para>
+ The first example is more conversational English, which is not
+ appropriate for official written documentation. The second
+ example is more formal, but as a result it is easier to
+ comprehend, both for native readers and translators.
+ </para>
+ <para>
+ Following style rules and guidelines also makes readers more
+ comfortable with a set of documents. Consistent style enhances
+ the professional appearance of documentation, and its perceived
+ value. On the other hand, lapses in punctuation or poor grammar
+ negatively affect a reader's reaction to written material. A
+ reader can feel that an otherwise correct technical document is
+ lacking in authority, simply because it is poorly written. Readers
+ feel at ease when they do not have to struggle to understand an
+ author's use of language.
+ </para>
+ <para>
+ This chapter cannot possibly cover enough material to make every
+ reader a good writer. Some manuals devoted entirely to writing
+ style are themselves hundreds of pages long. This chapter
+ provides enough guidelines for intermediate writers to understand
+ style usage in technical documentation.
+ </para>
+ <para>
+ If you are not a practiced writer, whether of technical
+ documentation or otherwise, you may benefit from other style
+ resources. The following list is far from comprehensive, but
+ provides a starting point:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <citetitle>The Elements of Style</citetitle>, by William
+ Strunk. Basic rules and links to online versions can be found
+ at: <ulink
+ url="http://en.wikipedia.org/wiki/The_Elements_of_Style">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>
+ </para>
+ </listitem>
+<!-- placeholder for when it's ready
+ <para>
+ <citetitle>The Elements of Style</citetitle>, by William
+ Strunk. Fedora Docs Project version: <ulink
+ url="http://fedora.redhat.com/docs/eos-guide-en/">http://fedora.redhat.com/docs/eos-guide-en/</ulink>
+ </para>
+-->
+ <listitem>
+ <para>
+ <citetitle>The Chicago Manual of Style</citetitle>, by the
+ University of Chicago Press. Online version: <ulink
+ url="http://www.chicagomanualofstyle.org/">http://www.chicagomanualofstyle.org/</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <citetitle>Paradigm Online Writing Assistant</citetitle>,
+ maintained by Chuck Guilford, Ph.D. Online only: <ulink
+ url="http://www.powa.org/">http://www.powa.org/</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ There are many free software documentation projects which have
+ developed their own style guidelines. This chapter, in fact,
+ draws heavily on the <citetitle>GNOME Documentation Style
+ Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may
+ read the original <citetitle>GDSG</citetitle> at <ulink
+ url='http://developer.gnome.org/documents/style-guide/'>http://developer.gnome.org/documents/style-guide/</ulink>.
+ </para>
+
+ </section>
+
+ <section id="sn-tech-docs-fundamentals">
+
+ <title>Fundamental Concepts of Technical Documentation</title>
+
+ <note>
+ <title>Bibliographic Information</title>
+ <para>
+ This section is drawn primarily from the
+ <citetitle>GDSG</citetitle>.
+ </para>
+ </note>
+
+ <!-- This section will reproduce mostly what is in Chapter 1 of
+ the GDSG. There may be minor changes. FIXME: Make sure the
+ appropriate front matter of the Documentation Guide includes
+ attribution as required by the GNU FDL. -->
+
+ <para>
+ This chapter provides a brief introduction to writing technical
+ documentation.
+ </para>
+
+ <section id="sn-fundamentals-1">
+ <title>General Style Requirements</title>
+ <para>
+ Technical writing for the &FP; imposes special constraints
+ beyond the basic requirements of good prose. Good &FED;
+ technical documentation has the following characteristics:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Comprehensive</term>
+ <listitem>
+ <para>
+ Describe all of the functionality of a product. Do not
+ omit functionality that you regard as irrelevant for the
+ user.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Conforming</term> <!-- I'm having issues with the
+ sketchy definition of this non-dictionary word and the
+ associated text. Not wrong, per se, just wishing for
+ something better. This note shall remind us! - kwade -->
+ <!-- Hopefully this change helps. Makes sense according to the
+ gdict tool in Core, at least. - PWF -->
+ <listitem>
+ <para>
+ Describe what you see. Do not describe what you want to
+ see. Present your information in the order that users
+ experience the subject matter.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Clear</term>
+ <listitem>
+ <para>
+ Read <citetitle>The Elements of Style</citetitle> (<ulink
+ url="http://en.wikipedia.org/wiki/The_Elements_of_Style">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>)
+ to help make your writing clear.
+ </para>
+<!-- placeholder for when this is published:
+ <para>
+ Read <citetitle>The Elements of Style</citetitle>
+ &FED;-version (<ulink
+ url="http://fedora.redhat.com/docs/eos-guide-en/">http://fedora.redhat.com/docs/eos-guide-en/</ulink>)
+ to help make your writing clear.
+ </para>
+-->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Consistent</term>
+ <listitem>
+ <para>
+ Use agreed vocabulary throughout your documentation. Use
+ the same vocabulary as other writers who are working on
+ related documentation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Concise</term>
+ <listitem>
+ <para>
+ Review your work frequently as you write your document.
+ Ask yourself which words you can take out. Refer to <xref
+ linkend="sn-fundamentals-2"/> for specific guidelines.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-2">
+ <title>Golden Rules</title>
+ <para>
+ This section contains some basic style guidelines. Subsequent
+ sections in this chapter expand on these guidelines to give more
+ detailed guidance.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Golden Rule 1: Be brief</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Limit each sentence to fewer than 25 words.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each procedure step to 23 words.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-1-wrong">
+ <title>Incorrect: Too long</title>
+ <para> Under normal operating conditions, the kernel does
+ not always immediately write file data to the disks,
+ storing it in a memory buffer and then periodically
+ writing to the disks to speed up operations.
+ </para>
+ </example>
+ <example id="ex-golden-rule-1-right">
+ <title>Correct: Less wordy</title>
+ <para>
+ Normally, the kernel stores the data in memory prior to
+ periodically writing the data to the disk.
+ </para>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Golden Rule 2: Be organized</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Limit each paragraph to one topic.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each sentence to one idea.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each procedure step to one action.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-2-wrong">
+ <title>Incorrect: Disorganized topics</title>
+ <para>
+ The <application>Workspace Switcher</application> applet
+ helps you navigate all of the virtual desktops available
+ on your system. The X Window system, working in hand
+ with a piece of software called a <emphasis>window
+ manager</emphasis>, allows you to create more than one
+ virtual desktop, known as
+ <emphasis>workspaces</emphasis>, to organize your work,
+ with different applications running in each workspace.
+ The <application>Workspace Switcher</application> applet
+ is a navigational tool to get around the various
+ workspaces, providing a miniature road map in the GNOME
+ panel showing all your workspaces and allowing you to
+ switch easily between them.
+ </para>
+ </example>
+ <example id="ex-golden-rule-2-right">
+ <title>Correct: Organized topics</title>
+ <para>
+ Use the <application>Workspace Switcher</application> to
+ add new <emphasis>workspaces</emphasis> to the GNOME
+ Desktop. You can run different applications in each
+ workspace. The <application>Workspace
+ Switcher</application> applet provides a miniature map
+ that shows all of your workspaces. You can use the
+ <application>Workspace Switcher</application> applet to
+ switch between workspaces.
+ </para>
+ </example>
+ <tip>
+ <para>
+ Plan the order of paragraphs before you start writing.
+ Decide which topic you want to cover in each paragraph.
+ </para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Golden Rule 3: Be demonstrative</term>
+ <listitem>
+ <para>
+ Use explicit examples to demonstrate how an application
+ works. Provide instructions rather than descriptions.
+ </para>
+ <example id="ex-golden-rule-3-wrong">
+ <title>Incorrect: Describes but does not
+ demonstrate</title>
+ <para>
+ There is a text box that you can use to find out the
+ definition of a word.
+ </para>
+ </example>
+ <example id="ex-golden-rule-3-right">
+ <title>Correct: Demonstrates usage</title>
+ <para>
+ To request a definition of a word, type the word in the
+ text box, then select <guilabel>Lookup</guilabel>.
+ </para>
+ </example>
+ <tip>
+ <para>
+ Do not apply this guideline too rigidly. Sometimes you
+ must explain how software works to support your how-to
+ examples.
+ </para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-golden-rule-4">
+ <term>Golden Rule 4: Be objective</term>
+ <listitem>
+ <para>
+ Write in a neutral tone.
+ </para>
+ <example id="ex-golden-rule-4-wrong">
+ <title>Incorrect: Sentence takes sides</title>
+ <para>
+ The applet is a handy little screen grabber.
+ </para>
+ </example>
+ <example id="ex-golden-rule-4-right">
+ <title>Correct: Sentence is objective</title>
+ <para>
+ Use the applet to take screenshots.
+ </para>
+ </example>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="sn-fundamentals-3">
+
+ <title>Tone</title>
+ <para>
+ Inappropriate tone hinders reader access to information. A
+ neutral tone free of opinion or personal flavor improves the
+ reader's comprehension. Neutral tone helps writers to work in
+ parallel on a large technical documentation project.
+ Furthermore, additional writers may join the project at any
+ time. Use of a neutral tone helps to achieve consistency across
+ a documentation set, and thereby facilitates user access to
+ information. The best way to achieve a common, neutral tone is
+ to apply the following principles:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Avoid humor</term>
+ <listitem>
+ <para>
+ Humor distracts from the information you are trying to
+ provide. Humor also makes documentation difficult to
+ translate. Stay factual.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid personal opinions</term>
+ <listitem>
+ <para>
+ Whether you think a function is useful or woeful is
+ irrelevant. Report the function to the user, with
+ instructions about how to use the function. Stay
+ accurate.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid colloquial language</term>
+ <listitem>
+ <para>
+ Colloquial language is difficult to translate and usually
+ culture-specific. Stay neutral.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid topical expressions</term>
+ <listitem>
+ <para>
+ An expression that is in common use today might convey
+ something completely different tomorrow. Stay technical.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid aspirational statements</term>
+ <listitem>
+ <para>
+ Statements about the future developments of a product do
+ not belong in technical documentation. Write about what
+ you see right now. Stay real.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-4">
+ <title>Reaching the Right Audience</title>
+ <para>
+ All of the decisions that you make about the structure and
+ content of a manual follow from an understanding of the
+ audience. Consider how the audience accesses the documentation,
+ what sort of information the audience needs, and the experience
+ level of the audience. Usually, you need to create
+ documentation that is suitable for different audiences. The
+ following sections introduce some of the audience-related topics
+ you need to consider.
+ </para>
+ </section>
+ <section id="sn-fundamentals-6">
+ <title>User Motivation</title>
+ <para>
+ Do not waste the time of the user who looks for information in
+ your documentation. Users do not read technical documentation
+ for entertainment. Users usually have specific questions. You
+ need to give clear answers to those questions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-7">
+ <title>New Users</title>
+ <para>
+ New users to &FC; are likely to consult online tutorials for
+ guidance about unfamiliar applications or functionality. Each
+ tutorial should contain enough introductory information to tell
+ new users how to start using the relevant functions. Each
+ tutorial should also contain enough usage instructions to tell
+ users the different actions that they can perform with the
+ command or function. Keep these instructions task-oriented. Do
+ not describe GUI screens, dialogs, and dialog elements in a
+ tutorial, unless there is an unusual feature that affects your
+ instructions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-8">
+ <title>Experienced Users</title>
+ <para>
+ Experienced users are more likely to use documentation as a
+ reference. The documentation therefore needs to be complete,
+ well-organized, and in the case of printed manuals,
+ well-indexed.
+ </para>
+ </section>
+ <section id="sn-fundamentals-9">
+ <title>Do Not Offend Your Audience</title>
+ <para>
+ To avoid offending your readers, apply the following guidelines
+ to your documentation:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Avoid insider language</term>
+ <listitem>
+ <para>
+ Insider language includes both undefined jargon and the
+ tendency of the computer community to shorten words. For
+ example, use the term <literal>documentation</literal>
+ instead of the term <literal>docs</literal>. A term may
+ be jargon if it fails all the following conditions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The term does not appear in the <citetitle>&FED;
+ Jargon Buster</citetitle> (<ulink
+ url="http://fedora.redhat.com/docs/jargon-buster/">http://fedora.redhat.com/docs/jargon-buster/</ulink>).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The term does not appear in the <citetitle>American
+ Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/
+ </ulink>).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The term does not appear in the glossary of the manual
+ that you are writing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The term is not defined in the body text of the manual
+ that you are writing.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid gender-specific language</term>
+ <listitem>
+ <para>
+ Pronoun constructions such as <literal>his/her</literal>
+ or <literal>s/he</literal> do not exist. There is no need
+ to identify gender in your instructions.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid culture-specific language</term>
+ <listitem>
+ <para>
+ There is little point in giving an example that everyone
+ in your town knows about, but is a complete mystery to
+ everyone else in the world.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid talking down to your reader</term>
+ <listitem>
+ <para>
+ There are few experiences more irritating for a user than
+ documentation that says an action is easy or quick, when
+ in fact the user cannot complete the action. Do not
+ qualify or prejudge actions.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Other parts of this guide discuss in more detail tone and
+ language usage that can cause offense.
+ </para>
+
+ </section>
+
+ </section>
+
+ <section id="sn-grammar-and-usage">
+
+ <title>Grammar and Usage Guidelines</title>
+
+ <note>
+ <title>Bibliographical Information</title>
+ <para>
+ This section is drawn partly from the
+ <citetitle>GDSG</citetitle>, and partly from <citetitle>The
+ Elements of Style</citetitle>, updated as necessary for the
+ needs of 21st-century technical documentation writers.
+ </para>
+ </note>
+
+ <!-- FIXME: Again, check attribution viz. GNU FDL. This will be more work
+ than the previous section. -->
+
+ <para>
+ This section contains an alphabetical list of grammar and usage
+ guidelines for use in &FED; documentation. Many of these
+ guidelines are only applicable to English-language usage, refer to
+ the <citetitle>American Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ and the <citetitle>Chicago Manual of Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Abbreviations</term>
+ <listitem>
+ <para>
+ A shortened form of a word or phrase that takes the place of
+ the full word or phrase, such as <literal>Dr.</literal>,
+ <literal>a.m.</literal>, <literal>p.m.</literal>, and so on.
+ Apply the following rules when you use abbreviations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Avoid creating new abbreviations. Unfamiliar
+ abbreviations can confuse rather than clarify a concept.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not explain or expand familiar abbreviations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not include familiar abbreviations in the glossary of
+ your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ For abbreviations of phrases, such as
+ <literal>i.e.</literal> for "in other words" and
+ <literal>e.g.</literal> for "for example", do not use the
+ abbreviation. Spell out the entire phrase.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adjectives</term>
+ <listitem>
+ <para>
+ Use adjectives with caution. If an adjective is necessary
+ to differentiate between items, then use adjectives. In all
+ cases, test whether the phrase can stand alone without the
+ adjective.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Acronyms</term>
+ <listitem>
+ <para>
+ A term that represents a multi-word term. Typically,
+ acronyms are formed in the following ways:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ From the first letters of each word in a compound term,
+ for example Table of Contents (TOC).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ From recognizable parts of a compound term, such as GNU
+ Object Model Environment (GNOME).
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Apply the following rules when you use acronyms:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ On the first occurrence of an acronym, spell out the
+ full term, with the acronym in parentheses.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not spell out the full compound for well-known
+ acronyms, unless you think the information is useful for
+ readers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Avoid creating new acronyms. Unfamiliar acronyms can
+ confuse rather than clarify a concept.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Write the acronym in uppercase letters, unless there is
+ a compelling case for lowercase.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Include the acronym and the full term in the glossary of
+ your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adverbs</term>
+ <listitem>
+ <para>
+ Use adverbs with caution. If an adverb is necessary to
+ qualify the function of a component, then use an adverb. In
+ all cases, test whether the phrase can stand alone without
+ the adverb. Classic superfluous adverbs
+ <literal>simply</literal>, <literal>easily</literal>,
+ <literal>quickly</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Anthropomorphism</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not apply emotions, desires, or opinions to software
+ applications.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not apply a sense of location or dimension to a
+ software application. A user can not be "in" a text
+ editor.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Articles</term>
+ <listitem>
+ <para>
+ Do not use the definite article <literal>the</literal> to
+ begin any of the following items:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Manual titles
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter titles
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Headings
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Figure captions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Table captions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Callouts
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Apostrophe</term>
+ <listitem>
+ <para>
+ Do not use apostrophes except where absolutely required
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote possession.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote contractions.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote plurals.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-apostrophe-wrong">
+ <title>Incorrect: Apostrophes</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <guimenu>Main Menu's</guimenu>
+ <guimenuitem>Help</guimenuitem> option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ don't use the default option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ several SCSI disk's
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-apostrophe-right">
+ <title>Correct: No apostrophes</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <guimenuitem>Help</guimenuitem> option on the
+ <guimenu>Main Menu</guimenu>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ do not use the default option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ several SCSI disks
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Brackets</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not use brackets [such as these] as a substitute for
+ parentheses (such as these).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use brackets for optional command line entries.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use angle brackets to indicate variables in text,
+ instead use the <sgmltag
+ class="starttag">replaceable</sgmltag> tag. Refer to
+ <xref linkend="s1-xml-tags-replaceable"/> for
+ information about using this tag.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Capitalization</term>
+ <listitem>
+ <para>
+ Capitalize in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ All letters in acronyms, unless the acronym is a
+ well-known exception
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of the first word in a list
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of the first word in a callout
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a key name, such as the
+ <keycap>Shift</keycap> key
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a sentence
+ </para>
+ <note>
+ <title>Command Names</title>
+ <para>
+ Avoid starting a sentence with a command name or
+ application name that has a lowercase initial letter.
+ </para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a complete sentence after a colon
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not capitalize in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ A compound term that is followed by an abbreviation or
+ an acronym
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When you want to emphasize something
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Variable names
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The initial letter of an incomplete sentence after a
+ colon
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Captions</term>
+ <listitem>
+ <para>
+ Use the same rules as for headings, for all captions
+ accompanying figures and tables. Do not put a period at the
+ end of a caption.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Colon</term>
+ <listitem>
+ <para>
+ Use a colon in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To introduce a list
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Before an explanation
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ After an introduction
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use a colon in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To introduce a figure or a table
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To introduce headings
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ At the end of an introduction to a procedure
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Column headings</term>
+ <listitem>
+ <para>
+ Use the same rules as for headings.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Comma</term>
+ <listitem>
+ <para>
+ Use commas in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To separate items in a series
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To separate the parts of a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To separate nonrestrictive phrases
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Instead of dashes to set off appositives
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With <emphasis>for example</emphasis> and similar
+ expressions
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use commas in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ In a series of adjectives used as one modifier
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Between two short independent clauses
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Commands</term>
+ <listitem>
+ <para>
+ Do not use commands as verbs.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-contractions">
+ <term>Contractions</term>
+ <listitem>
+ <para>
+ Do not use contractions such as <emphasis>can't</emphasis>,
+ <emphasis>don't</emphasis>, or <emphasis>isn't</emphasis>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Dash</term>
+ <listitem>
+ <para>
+ Do not use the em dash or the en dash. Use a paragraph
+ break or a colon instead, where you want to create an
+ introductory piece of text. If you have several items that
+ you want to introduce, then you can use a variable list.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Ellipsis</term>
+ <listitem>
+ <para>
+ Use an ellipsis in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To show that you have omitted something from a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To indicate a pause when you quote displayed text
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Fractions</term>
+ <listitem>
+ <para>
+ Follow these rules when using fractions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use numerals for fractions in tables and in units of
+ measurement, but spell out fractions in prose.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use a space between a numeral and a related fraction, if
+ there is a possible ambiguity. For example: 1 1/2
+ instead of 11/2.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If a fraction is used in a compound modifier, insert a
+ hyphen between the fraction and the unit of measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Gender</term>
+ <listitem>
+ <para>
+ Refer to <xref linkend="sn-fundamentals-9"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Grammar</term>
+ <listitem>
+ <para>
+ Use standard American English grammar rules, refer to the
+ <citetitle>Chicago Manual of Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">
+ http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Headings</term>
+ <listitem>
+ <para>
+ Use the following capitalization rules in headings:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Initial uppercase letter of the first word
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for all nouns, adjectives, and
+ verbs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All lowercase letters for conjunctions, articles, and
+ prepositions of fewer than four letters
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for prepositions of four
+ letters or longer
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for conjunctions of four
+ letters or longer
+ </para>
+ </listitem>
+ </itemizedlist>
+ <!-- <para> See <xref linkend="infodesign-2"/> for more
+ information about headings. </para> -->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Hyphen</term>
+ <listitem>
+ <para>
+ Use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para> With a numeral in a compound modifier
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To prevent ambiguity
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With some standard prefixes and suffixes. Use the
+ <citetitle>American Heritage Dictionary</citetitle>
+ (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ for guidance
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In spelled-out fractions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In variable names of two or more words, such as
+ <replaceable>directory-name</replaceable>. Note:
+ <replaceable>filename</replaceable> is an exception.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ For industry-accepted terms
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To construct verbs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With an adverb ending in <emphasis>ly</emphasis>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With numerals as single modifiers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With a word that is listed as unhyphenated in the
+ <citetitle>American Heritage Dictionary</citetitle>
+ (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>),
+ and that uses a common prefix
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With trademarked terms
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Latin terms</term>
+ <listitem>
+ <para>
+ Do not use Latin terms. Use an equivalent English term
+ instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Like</term>
+ <listitem>
+ <para>
+ Do not use the term <emphasis>like</emphasis> to denote
+ equivalence or similarity.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Lists</term>
+ <listitem>
+ <para>
+ Introduce a list with a complete sentence that ends with a
+ colon.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numbers</term>
+ <listitem>
+ <para>
+ Spell out numbers in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para> Numbers from zero through nine unless the number is
+ part of a measurement
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Approximations
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Extreme values such as <emphasis>million</emphasis>, but
+ precede the value with a numeral
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Any number that begins a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A number that is immediately followed by a numeral, for
+ example: <literal>two 10 MB files</literal>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numerals</term>
+ <listitem>
+ <para>
+ Use numerals in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The number 10 or greater
+ </para>
+ </listitem>
+ <listitem>
+ <para> Negative numbers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Most fractions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Percentages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Decimals
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Measurements
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Units of time smaller than one second
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ References to bits and bytes
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Parentheses</term>
+ <listitem>
+ <para>
+ Use parentheses in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To contain the abbreviation of a term on the first
+ occurrence of the full term
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In man page references, specifically the section number
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Period</term>
+ <listitem>
+ <para>
+ Use a period in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To end a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In file and directory names
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In abbreviations that can be mistaken for words, such as
+ a.m. and U.S.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation</term>
+ <listitem>
+ <para>
+ Use standard American English punctuation rules. In
+ addition to the specific points of punctuation in this
+ section, refer also to the <citetitle>Chicago Manual of
+ Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation in numbers</term>
+ <listitem>
+ <para>
+ Do not use a comma in numerals of four digits. Use a comma
+ in numerals of more than four digits.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Quotation marks</term>
+ <listitem>
+ <para>
+ Use quotation marks to indicate material that is taken
+ verbatim from another source. Do not use quotation marks to
+ excuse terms from legitimacy. If the term is not
+ legitimate, then use another term. If you must use that
+ term, declare the term in the glossary and make the term
+ legitimate.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>See v. Refer to</term>
+ <listitem>
+ <para>
+ When referring a user to another resource, use "refer to"
+ instead of "see", and "refer also to" instead of "see also".
+ This differentiates from the <sgmltag
+ class="starttag">see</sgmltag> and <sgmltag
+ class="starttag">seealso</sgmltag> tags that are used in
+ indexing. These tags create special links in the index. To
+ be consistent throughout the document, we reserve the
+ special words "see" and "see also" for hyperlinked index
+ references, and use "refer to" and "refer also to" for
+ non-hyperlinked and non-indexed references.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Semicolon</term>
+ <listitem>
+ <para>
+ Do not use semicolons.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Slash</term>
+ <listitem>
+ <para>
+ Except where required as part of a filename, do not use
+ slashes "/" in your writing. The construction
+ <literal>and/or</literal>, for example, does not exist. Use
+ one or the other term instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Spelling</term>
+ <listitem>
+ <para>
+ Use standard American English spelling rules, refer to the
+ <citetitle>American Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ for guidelines.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Titles</term>
+ <listitem>
+ <para>
+ For manual titles use the same rules as for headings.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Units</term>
+ <listitem>
+ <para>
+ Follow these rules when using units:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use standard abbreviations for units of measurements, do
+ not invent your own abbreviations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!-- See <xref linkend="units"/> for a list of units
+ relevant to the GNOME Desktop. --> For further
+ guidelines, refer to the <citetitle>IEEE Standard
+ Dictionary of Electrical and Electronics
+ Terms</citetitle>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use periods for abbreviated units that might be mistaken
+ for a word.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Most standard abbreviations of units account for both
+ singular and plural usage.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Insert a space between the numeral and the unit of
+ measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="sn-composition-tips">
+
+ <title>Composition Tips</title>
+
+<!--
+
+ This section will collect miscellanea and advice for specific
+ situations that the FDP editors encounter. I hope they will feel
+ free to e-mail me sticky situations or particularly interesting
+ examples of work they've beautified. Hopefully not too much will be
+ drawn from my own work! - PWF.
+
+-->
+
+ <para>
+ This section contains usage tips based on situations the &FDP;
+ editors have encountered in the past. You should read and
+ understand these examples to improve your own documentation. The
+ &FDP; editors welcome additional examples.
+ </para>
+
+ <section id="sn-misc-active-voice">
+ <title>Active Voice</title>
+ <para>
+ Always use active voice, except when it is awkward to do so. The
+ tutorial tells the user how to accomplish a task, and should
+ give instructions clearly and concisely. Avoid using "must,"
+ "need to," and the like. These words are redundant in a
+ tutorial, since the reader assumes you are outlining necessary
+ steps to accomplish a task. Also avoid using "maybe," "might,"
+ and other words that indicate you are unsure about the subject
+ matter. Your tutorial should cover a subject authoritatively.
+ The reader should never be concerned about unknown effects of
+ following the tutorial.
+ </para>
+ <example id="ex-misc-passive-voice">
+ <title>Incorrect: Passive voice</title>
+ <para>
+ The <command>yum update</command> command must be run.
+ </para>
+ <para>
+ You might want to run the <command>yum update</command>
+ command.
+ </para>
+ </example>
+ <example id="ex-misc-active-voice">
+ <title>Correct: Active voice</title>
+ <para>
+ Run the <command>yum update</command> command.
+ </para>
+ </example>
+ </section>
+
+ <section id="sn-present-tense">
+ <title>Present Tense</title>
+ <para>
+ Write in the present tense. A good rule of thumb is that the
+ words "will" and "shall" are almost never needed in describing
+ what the user should do or see. They add unnecessary length to
+ sentences and can confuse translators. They are also often
+ indicators of passive voice; refer also to <xref
+ linkend="sn-misc-active-voice"/>.
+ </para>
+ <example id="ex-misc-future-tense">
+ <title>Incorrect: Future tense</title>
+ <para>
+ The application will display a list of target files.
+ </para>
+ <para>
+ A list of target files will be displayed by the application.
+ </para>
+ </example>
+ <example id="ex-misc-present-tense">
+ <title>Correct: Present tense</title>
+ <para>
+ The application displays a list of target files.
+ </para>
+ </example>
+ </section>
+
+ <section id="sn-narrative-voice">
+ <title>Narrative Voice</title>
+ <para>
+ Do not use the first person "I," "we," or "us" to refer to
+ yourself the writer (whether including the reader or not), the
+ &FDP;, the &FED; community, or any other group. Do not refer to
+ users with a third person pronoun ("he," "she," or "he or she")
+ or the word "one." It is acceptable to refer to the reader with
+ the second person pronoun "you."
+ </para>
+ <example id="ex-misc-wrong-person">
+ <title>Incorrect: First or third person</title>
+ <para>
+ As described in the last section, I always run
+ <command>up2date</command> before configuring the Samba
+ server.
+ </para>
+ <para>
+ If the user needs to back up his or her files, s/he should use
+ the <command>tar</command> or <command>cpio</command> command.
+ </para>
+ </example>
+ <example id="ex-misc-correct-person">
+ <title>Correct: Second (or no) person</title>
+ <para>
+ Refer to the section on <command>up2date</command> before
+ configuring the Samba server.
+ </para>
+ <para>
+ If necessary, users can back up files with the
+ <command>tar</command> or <command>cpio</command> command.
+ </para>
+ </example>
+ </section>
+
+ <section id="sn-misc-negative">
+ <title>Negative Words</title>
+ <para>
+ Avoid negative words when possible, since they give
+ documentation an overly dogmatic tone. The word "avoid" is
+ useful for this purpose. Note that contractions are often used
+ for negative words such as <emphasis>don't</emphasis> or
+ <emphasis>can't</emphasis>. Refer to <xref
+ linkend="vle-contractions" />.
+ </para>
+ </section>
+
+ <section id="sn-misc-uncertainty">
+ <title>Uncertainty</title>
+ <para>
+ Avoid overuse of "typically," "usually," "most of," "many," and
+ the like. While occasional use of these constructions is
+ acceptable, overuse reduces the authority of your documentation.
+ The documentation should adequately cover a stock installation
+ of &FC;. It is impossible for a tutorial-length document to
+ cover every possible configuration scenario. Address the most
+ common scenarios and note discrepancies only as required.
+ </para>
+ </section>
+
+ <section id="sn-misc-offtopic">
+ <title>Redundant Coverage</title>
+ <para>
+ Avoid covering redundant material, such as how to update a &FC;
+ system. These overarching topics may be covered in other
+ tutorials. Writers frequently violate this guideline because
+ they feel their tutorial is not long enough. Keep your tutorial
+ from wandering off-topic. Instead, refer the reader to a
+ separate tutorial whenever possible for complete coverage of
+ that topic.
+ </para>
+ </section>
+
+ <section id="sn-misc-importance">
+ <title>Self-referential Value Judgments</title>
+ <para>
+ Avoid statements such as "One of the most important things to do
+ is <replaceable>XYZ</replaceable>." If the procedure is
+ important, the reader already expects it to be in your tutorial.
+ The converse is also true: If a procedure appears in your
+ tutorial, the reader expects it is important. This is
+ especially true if you use a whole section for the procedure in
+ question. Merely state, "Do <replaceable>XYZ</replaceable>."
+ Then elaborate as required. If the whole section concerns how
+ to do <replaceable>XYZ</replaceable>, leave this sentence out
+ entirely. Refer also to <xref linkend="vle-golden-rule-4" />.
+ </para>
+ </section>
+
+ <section id="sn-misc-precision">
+ <title>Precision of Language</title>
+ <para>
+ Use precise words for actions users should take. Do not
+ instruct users to "go" to a selection, or "find" a menu.
+ </para>
+ <example id="ex-precision-wrong">
+ <title>Incorrect: Imprecise wording</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Go to the <guimenu>Main Menu</guimenu> ->
+ <guimenuitem>Foobar</guimenuitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Find the option labeled <guilabel>Search</guilabel>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-precision-right">
+ <title>Correct: Precise wording</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ From the <guimenu>Main Menu</guimenu>, select
+ <guimenuitem>Foobar</guimenuitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select the <guilabel>Search</guilabel> option
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <important>
+ <title>Do Not Discriminate Against Non-GUI Users</title>
+ <para>
+ If you are writing about a GUI-only application, you may use
+ "click" freely. If you are writing about an application that
+ has a text-mode interface, use "select" instead as shown
+ above.
+ </para>
+ </important>
+
+ </section>
+
+ <section id="sn-misc-docbook-tips">
+ <title>DocBook Tips</title>
+ <para>
+ This section contains tips on how to use DocBook tags more
+ effectively in your documentation.
+ </para>
+
+ <section id="sn-misc-admonitions">
+ <title>Admonitions</title>
+ <para>
+ Avoid overuse of admonitions. Keep admonitions short and
+ effective by using only the most important material inside the
+ admonition. Move any background material required to explain
+ the admonition statements outside the admonition. Use a short
+ but descriptive title for an admonition. Use title case for
+ the admonition title.
+ </para>
+ <example id="ex-misc-ineffective-admonition">
+ <title>Incorrect: Lengthy admonition</title>
+ <para>
+ <warning>
+ <title>Use <command>sfdisk</command> to check input</title>
+ <para>
+ The <command>sfdisk</command> command accepts a script
+ file as standard input to set up partitions on a hard
+ disk. Sometimes <command>sfdisk</command> will simply
+ reject an erroneous input file. In other cases, it will
+ use the input verbatim, writing an incorrect partition
+ table to your disk. Always use the <command>sfdisk
+ -n</command> command to check your input file before
+ writing to the disk.
+ </para>
+ </warning>
+ </para>
+ </example>
+ <example id="ex-misc-good-admonition">
+ <title>Correct: Brief admonition</title>
+ <para>
+ The <command>sfdisk</command> command accepts a script
+ file as standard input to set up partitions on a hard disk.
+ Sometimes <command>sfdisk</command> will simply reject an
+ erroneous input file. In other cases, it will use the input
+ verbatim, writing an incorrect partition table to your disk.
+ <warning>
+ <title>Check Input</title>
+ <para>
+ Always use the <command>sfdisk -n</command> command to
+ check your input file before writing to the disk.
+ </para>
+ </warning>
+ </para>
+ </example>
+ <para>
+ Avoid punctuation in titles for sections or admonitions,
+ except for commas only where demanded. Use a title that says
+ something about the admonition comment, such as "Reboot
+ Required," instead of simply using the admonition type for a
+ title ("Note").
+ </para>
+ <para>
+ Follow the capitalization rules for headings in the title of
+ an admonition.
+ </para>
+ </section>
+
+ <section id="sn-misc-replaceable">
+ <title>The <sgmltag class="starttag">replaceable</sgmltag>
+ Tag</title>
+ <para>
+ If your documentation formally states a specific value will be
+ used as a convention, do not use the <sgmltag
+ class="starttag">replaceable</sgmltag> tag in your text or
+ examples.
+ </para>
+ </section>
+
+ <section id="sn-misc-entities">
+ <title>XML Entities</title>
+ <para>
+ Use the entities provided by the &FDP;. These entities are
+ found in the <filename>common/</filename> folder in the
+ <filename>fedora-docs</filename> distribution. (Refer also to
+ <xref linkend="ch-getting-files"/>.) For instance, do not use
+ abbreviations such as "FC2." Instead, use the predefined
+ entities "&FC; &FCVER;," which produces the text "&FC;
+ &FCVER;."
+ </para>
+ </section>
+
+ </section>
+
+ </section>
+
+</chapter>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: xml
+sgml-parent-document:("documentation-guide-en.xml" "book" "chapter")
+fill-column: 72
+End:
+-->
+@
+
+
+1.7
+log
+ at linking to a more neutral source for EoS
+@
+text
+@@
+
+
+1.6
+log
+ at Extra information about admonition style
+@
+text
+ at d154 3
+a156 2
+ Strunk. Online version: <ulink
+ url="http://bartleby.com/141/">http://bartleby.com/141/</ulink>
+d252 1
+a252 1
+ url="http://www.bartleby.com/141/">http://www.bartleby.com/141/</ulink>)
+@
+
+
+1.5
+log
+ at Corrected dumb comment error
+@
+text
+ at d1876 3
+a1878 1
+ the admonition statements outside the admonition.
+d1884 1
+a1884 1
+ <title>Using <command>sfdisk</command></title>
+d1901 1
+a1901 1
+ The <command>sfdisk</command> command accepts a script
+d1906 2
+a1907 2
+ <warning>
+ <title>Using <command>sfdisk</command></title>
+d1912 1
+a1912 1
+ </warning>
+@
+
+
+1.4
+log
+ at Added Id tag, cleanup, and additional editing to eliminate inconsistency
+@
+text
+ at d1654 1
+a1654 1
+ drawn from my own work! -- PWF.
+@
+
+
+1.3
+log
+ at Complete grammatical and technical edit of new Style chapter, sufficient to post these changes live.
+@
+text
+ at d1 2
+d4 1
+a4 10
+
+ <!--
+
+ To ensure code readability, please use a fill-width of 72 in
+ Emacs. To set fill width in Emacs, use "C-u 72 C-x f".
+
+ [PWF]
+
+ -->
+
+d9 1
+a9 1
+ command lines and instruction sets. Good documentation is easy to
+d11 2
+a12 2
+ progression of concepts. Good documentation can also be defined by
+ what it does <emphasis>not</emphasis> contain. Your tutorial should
+d43 5
+a47 5
+ In this chapter, you will find style rules and guidelines for
+ writing &FED; documentation. Guidelines are not the same as rules.
+ It is acceptable to violate a guideline when it makes your material
+ easier to understand. Follow guidelines whenever possible, but
+ follow rules at all times. Assume any advice is a guideline unless
+d52 1
+a52 1
+
+d54 1
+a54 1
+
+d56 1
+a56 1
+ Writing well comes naturally to almost no one. It is a skill that
+d60 1
+a60 1
+ that separates elegant writing from the merely functional.
+d63 5
+a67 5
+ Elegance comes in many forms. In prose and poetry,
+ elegant writing may not follow some (or any) common rules of
+ grammar, syntax, or spelling. A good example is Episode 18,
+ "Penelope," in James Joyce's novel
+ <citetitle>Ulysses</citetitle><footnote id='fn-ulysses'>
+d70 3
+a72 3
+ url="http://www.online-literature.com/james_joyce/ulysses/18/">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>.
+ Please note that this example contains some mature themes and
+ language, and is not suitable for all readers.
+d74 2
+a75 2
+ </footnote>. There, Joyce uses long streams of words without
+ punctuation to simulate a character's internal consciousness. By
+d77 1
+a77 1
+ disorganized but loosely connected thought patterns of his
+d82 2
+a83 2
+ rules. The more a document departs from standard language usage,
+ the more difficult the material becomes for the reader. For
+d85 1
+a85 1
+ or they might be reading a translation. If the writer uses slang,
+d87 2
+a88 2
+ confused. Take the following example, which compares two different
+ written executions of the same idea:
+d91 1
+a91 1
+ <title>Incorrect style</title>
+d94 1
+a94 1
+ "problematic" are mealy-mouthed. They remind me of the late
+d101 3
+a103 3
+ the next thing you should do? Just pop your thumb drive onto
+ your system and read the <filename>messages</filename> log. When
+ you see "USB device found," then Bob's your uncle.
+d107 1
+a107 1
+ <title>Correct style</title>
+d113 19
+a131 15
+ USB removable media to your system. Use the
+ <command>dmesg</command> command to examine the kernel message
+ log. The message <computeroutput>USB device
+ found</computeroutput> indicates that your device was
+ installed successfully.
+ </para>
+ </example> <para> The first example is more conversational English,
+ which is not appropriate for official written documentation. The
+ second example is more formal, but as a result it is easier to
+ comprehend, both for native readers and translators. </para>
+ <para> Following style rules and guidelines also makes readers more
+ comfortable with a set of documents. Consistent style enhances the
+ professional appearance of documentation, and its perceived value.
+ On the other hand, lapses in punctuation or poor grammar
+ negatively affect a reader's reaction to written material. A
+d135 6
+a140 4
+ author's use of language. </para>
+ <para> This chapter cannot possibly cover enough material to make
+ every reader a good writer. Some manuals devoted entirely to
+ writing style are themselves hundreds of pages long. This chapter
+d142 8
+a149 5
+ style usage in technical documentation. </para> <para> If you are
+ not a practiced writer, whether of technical documentation or
+ otherwise, you may benefit from other style resources. The
+ following list is far from comprehensive, but provides a starting
+ point: </para>
+d154 2
+a155 2
+ Strunk. Online version: <ulink
+ url="http://bartleby.com/141/">http://bartleby.com/141/</ulink>
+d164 1
+a164 8
+-->
+ <!-- KWade/TFox: Please check citation below, since I don't have
+ a copy. Thanks! And, um, I'm not sure if I should be using a
+ formal citation style below. /me is embarrassed. [PWF] -->
+
+ <!-- this is the way to do it, you are correct. - kwade -->
+ <!-- comments may now be self-destructed -->
+
+d168 2
+a169 2
+ University of Chicago Press. Online version: <ulink
+ url="http://www.chicagomanualofstyle.org/">http://www.chicagomanualofstyle.org/</ulink>
+d175 2
+a176 2
+ maintained by Chuck Guilford, Ph.D. Online only: <ulink
+ url="http://www.powa.org/">http://www.powa.org/</ulink>
+d182 3
+a184 3
+ developed their own style guidelines. This chapter, in fact, draws
+ heavily on the <citetitle>GNOME Documentation Style
+ Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may
+d186 1
+a186 1
+ url='http://developer.gnome.org/documents/style-guide/'>http://developer.gnome.org/documents/style-guide/</ulink>.
+d188 1
+a188 1
+
+d190 1
+a190 1
+
+d192 1
+a192 1
+
+d194 1
+a194 1
+
+d199 1
+a199 1
+ <citetitle>GDSG</citetitle>.
+d202 1
+a202 1
+
+d204 1
+a204 1
+ the GDSG. There may be minor changes. FIXME: Make sure the
+d217 2
+a218 2
+ beyond the basic requirements of good prose. Good &FED;
+ technical documentation has the following characteristics:
+d225 3
+a227 3
+ Describe all of the functionality of a product. Do not
+ omit functionality that you regard as irrelevant for the
+ user.
+d231 2
+a232 2
+ <varlistentry>
+ <term>Conformant</term> <!-- I'm having issues with the
+d236 2
+d240 9
+a248 9
+ Describe what you see. Do not describe what you want to
+ see. Present your information in the order that users
+ experience the subject matter.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Clear</term>
+ <listitem>
+d251 2
+a252 2
+ url="http://www.bartleby.com/141/">http://www.bartleby.com/141/</ulink>)
+ to help make your writing clear.
+d258 1
+a258 1
+ url="http://fedora.redhat.com/docs/eos-guide-en/">http://fedora.redhat.com/docs/eos-guide-en/</ulink>)
+d262 15
+a276 15
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Consistent</term>
+ <listitem>
+ <para>
+ Use agreed vocabulary throughout your documentation. Use
+ the same vocabulary as other writers who are working on
+ related documentation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Concise</term>
+ <listitem>
+d279 1
+a279 1
+ Ask yourself which words you can take out. Refer to <xref
+d281 11
+a291 11
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-2">
+ <title>Golden Rules</title>
+ <para>
+ This section contains some basic style guidelines. Subsequent
+ sections in this chapter expand on these guidelines to give more
+ detailed guidance.
+d312 3
+a314 3
+ not always immediately write file data to the disks,
+ storing it in a memory buffer and then periodically
+ writing to the disks to speed up operations.
+d321 1
+a321 1
+ periodically writing the data to the disk.
+d333 3
+a335 3
+ </para>
+ </listitem>
+ <listitem>
+d338 3
+a340 3
+ </para>
+ </listitem>
+ <listitem>
+d343 2
+a344 2
+ </para>
+ </listitem>
+d350 12
+a361 12
+ helps you navigate all of the virtual desktops available
+ on your system. The X Window system, working in hand
+ with a piece of software called a <emphasis>window
+ manager</emphasis>, allows you to create more than one
+ virtual desktop, known as
+ <emphasis>workspaces</emphasis>, to organize your work,
+ with different applications running in each workspace.
+ The <application>Workspace Switcher</application> applet
+ is a navigational tool to get around the various
+ workspaces, providing a miniature road map in the GNOME
+ panel showing all your workspaces and allowing you to
+ switch easily between them.
+d367 8
+a374 9
+ You can use the <application>Workspace
+ Switcher</application> to add new
+ <emphasis>workspaces</emphasis> to the GNOME Desktop.
+ You can run different applications in each workspace.
+ The <application>Workspace Switcher</application> applet
+ provides a miniature map that shows all of your
+ workspaces. You can use the <application>Workspace
+ Switcher</application> applet to switch between
+ workspaces.
+d380 1
+a380 1
+ Decide which topic you want to cover in each paragraph.
+d390 1
+a390 1
+ works. Provide instructions rather than descriptions.
+d394 1
+a394 1
+ demonstrate</title>
+d397 1
+a397 1
+ definition of a word.
+d404 1
+a404 1
+ text box, then click on the Lookup button.
+d409 3
+a411 3
+ Do not apply this guideline too rigidly. Sometimes you
+ must explain how software works to support your how-to
+ examples.
+d420 1
+a420 1
+ Write in a neutral tone.
+d425 1
+a425 1
+ The applet is a handy little screen grabber.
+d438 1
+a438 1
+ </section>
+d440 1
+a440 1
+ <section id="sn-fundamentals-3">
+d442 1
+a442 1
+ <title>Tone</title>
+d444 14
+a457 15
+ Inappropriate tone can hinder reader access to information. A
+ neutral tone free of opinion or personal flavor reduces the
+ processing load for the reader to understand the information.
+ Another benefit of a neutral tone is that several writers can
+ work in parallel on a large technical documentation project.
+ Furthermore, different writers can join the project at different
+ times. The use of a neutral tone helps to achieve consistency
+ across a documentation set, and thereby facilitates user access
+ to information. The best way to achieve a common, neutral tone
+ is to apply the following principles:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Avoid humor</term>
+ <listitem>
+d460 8
+a467 8
+ provide. Humor also makes documentation difficult to
+ translate. Stay factual.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid personal opinions</term>
+ <listitem>
+d470 9
+a478 8
+ irrelevant. Report the function to the user, with
+ instructions about how to use the function. Stay accurate.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid colloquial language</term>
+ <listitem>
+d481 7
+a487 7
+ culture-specific. Stay neutral.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid topical expressions</term>
+ <listitem>
+d490 7
+a496 7
+ something completely different tomorrow. Stay technical.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid aspirational statements</term>
+ <listitem>
+d499 5
+a503 5
+ not belong in technical documentation. Write about what
+ you see right now. Stay real.
+ </para>
+ </listitem>
+ </varlistentry>
+d505 3
+a507 3
+ </section>
+ <section id="sn-fundamentals-4">
+ <title>Reaching the Right Audience</title>
+d510 8
+a517 8
+ content of a manual follow from an understanding of the
+ audience. You need to think about how the audience accesses the
+ documentation, what sort of information the audience needs, and
+ the experience level of the audience. Usually, you need to
+ create documentation that is suitable for different audiences.
+ The following sections introduce some of the audience-related
+ topics you need to consider.
+ </para>
+d519 2
+a520 2
+ <section id="sn-fundamentals-6">
+ <title>User Motivation</title>
+d523 7
+a529 7
+ your documentation. Users do not read technical documentation
+ for entertainment. Users usually have specific questions. You
+ need to give clear answers to those questions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-7">
+ <title>New Users</title>
+d532 13
+a544 13
+ guidance about unfamiliar applications or functionality. Each
+ tutorial should contain enough introductory information to tell
+ new users how to start using the relevant functions. Each
+ tutorial should also contain enough usage instructions to tell
+ users the different actions that they can perform with the
+ command or function. Keep these instructions task-oriented. You
+ do not need to describe GUI screens, dialogs, and dialog
+ elements in a tutorial, unless there is an unusual feature that
+ affects your instructions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-8">
+ <title>Experienced Users</title>
+d547 7
+a553 7
+ reference. The documentation therefore needs to be complete,
+ well-organized, and in the case of printed manuals,
+ well-indexed.
+ </para>
+ </section>
+ <section id="sn-fundamentals-9">
+ <title>Do Not Offend Your Audience</title>
+d556 1
+a556 1
+ to your documentation:
+d558 4
+a561 4
+ <variablelist>
+ <varlistentry>
+ <term>Avoid insider language</term>
+ <listitem>
+d564 4
+a567 5
+ tendency of the computer community to shorten words. For
+ example, use the term <emphasis>documentation</emphasis>
+ instead of the term <emphasis>docs</emphasis>. You can
+ identify jargon if terminology fails the following
+ conditions:
+d569 2
+a570 2
+ <itemizedlist>
+ <listitem>
+d572 6
+a577 6
+ A term does not appear in the <citetitle>&FED; Jargon
+ Buster</citetitle> (<ulink
+ url="http://fedora.redhat.com/docs/jargon-buster/">http://fedora.redhat.com/docs/jargon-buster/</ulink>).
+ </para>
+ </listitem>
+ <listitem>
+d579 7
+a585 7
+ A term does not appear in the <citetitle>American
+ Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/
+ </ulink>).
+ </para>
+ </listitem>
+ <listitem>
+d587 5
+a591 5
+ A term does not appear in the glossary of the manual
+ that you are writing.
+ </para>
+ </listitem>
+ <listitem>
+d593 4
+a596 4
+ A term is not defined in the body text of the manual
+ that you are writing.
+ </para>
+ </listitem>
+d598 15
+a612 15
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid gender-specific language</term>
+ <listitem>
+ <para>
+ Pronoun constructions such as <emphasis>his/her</emphasis>
+ or <emphasis>s/he</emphasis> do not exist. There is no
+ need to identify gender in your instructions.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid culture-specific language</term>
+ <listitem>
+d615 8
+a622 8
+ in your town knows about, but is a complete mystery to
+ everyone else in the world.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid talking down to your reader</term>
+ <listitem>
+d625 6
+a630 6
+ documentation that says an action is easy or quick, when
+ in fact the user cannot complete the action. Do not
+ qualify or prejudge actions.
+ </para>
+ </listitem>
+ </varlistentry>
+d634 2
+a635 2
+ language usage that can cause offense.
+ </para>
+d637 1
+a637 1
+ </section>
+d639 1
+a639 1
+ </section>
+d649 3
+a651 3
+ <citetitle>GDSG</citetitle>, and partly from <citetitle>The
+ Elements of Style</citetitle>, updated as necessary for the
+ needs of 21st-century technical documentation writers.
+d655 1
+a655 1
+ <!-- FIXME: Again, check attribution viz. GNU FDL. This will be more work
+d660 1
+a660 1
+ guidelines for use in &FED; documentation. Many of these
+d663 1
+a663 1
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+d665 6
+a670 6
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Abbreviations</term>
+ <listitem>
+d673 12
+a684 11
+ the full word or phrase, for example Dr., a.m., p.m., and so
+ on. Apply the following rules when you use abbreviations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Avoid creating new abbreviations. Unfamiliar
+ abbreviations can confuse rather than clarify a concept.
+ </para>
+ </listitem>
+ <listitem>
+d687 3
+a689 3
+ </para>
+ </listitem>
+ <listitem>
+d692 32
+a723 31
+ your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ For abbreviations of phrases, such as i.e. for "in other
+ words" and e.g. for "for example", do not use the
+ abbreviation. Spell out the entire phrase.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adjectives</term>
+ <listitem>
+ <para>
+ Use adjectives with caution. If an adjective is necessary to
+ differentiate between items, then use adjectives. In all
+ cases, test whether the phrase can stand alone without the
+ adjective.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Acronyms</term>
+ <listitem>
+ <para>
+ A term that represents a multi-word term. Typically,
+ acronyms are formed in the following ways:
+ </para>
+ <itemizedlist>
+ <listitem>
+d726 4
+a729 4
+ for example Table of Contents (TOC).
+ </para>
+ </listitem>
+ <listitem>
+d732 3
+a734 3
+ Object Model Environment (GNOME).
+ </para>
+ </listitem>
+d738 3
+a740 3
+ </para>
+ <itemizedlist>
+ <listitem>
+d743 4
+a746 4
+ full term, with the acronym in parentheses.
+ </para>
+ </listitem>
+ <listitem>
+d749 11
+a759 11
+ acronyms, unless you think the information is useful for
+ readers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Avoid creating new acronyms. Unfamiliar acronyms can
+ confuse rather than clarify a concept.
+ </para>
+ </listitem>
+ <listitem>
+d762 4
+a765 4
+ a compelling case for lowercase.
+ </para>
+ </listitem>
+ <listitem>
+d768 24
+a791 23
+ your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adverbs</term>
+ <listitem>
+ <para>
+ Use adverbs with caution. If an adverb is necessary to
+ qualify the function of a component, then use an adverb. In
+ all cases, test whether the phrase can stand alone without
+ the adverb. Classic superfluous adverbs are:
+ <emphasis>simply, easily, quickly</emphasis>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Anthropomorphism</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+d794 4
+a797 4
+ applications.
+ </para>
+ </listitem>
+ <listitem>
+d800 16
+a815 16
+ software application. You can not be
+ <emphasis>in</emphasis> a text editor.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Articles</term>
+ <listitem>
+ <para>
+ Do not use the definite article <emphasis>the</emphasis> to
+ begin any of the following items:
+ </para>
+ <itemizedlist>
+ <listitem>
+d818 3
+a820 3
+ </para>
+ </listitem>
+ <listitem>
+d823 3
+a825 3
+ </para>
+ </listitem>
+ <listitem>
+d828 3
+a830 3
+ </para>
+ </listitem>
+ <listitem>
+d833 3
+a835 3
+ </para>
+ </listitem>
+ <listitem>
+d838 3
+a840 3
+ </para>
+ </listitem>
+ <listitem>
+d843 2
+a844 2
+ </para>
+ </listitem>
+d846 5
+a850 5
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Apostrophe</term>
+ <listitem>
+d858 3
+a860 3
+ </para>
+ </listitem>
+ <listitem>
+d863 3
+a865 3
+ </para>
+ </listitem>
+ <listitem>
+d868 2
+a869 2
+ </para>
+ </listitem>
+d877 1
+a877 1
+ <guimenuitem>Help</guimenuitem> option
+d898 1
+a898 1
+ <guimenu>Main Menu</guimenu>
+d914 6
+a919 6
+ </varlistentry>
+ <varlistentry>
+ <term>Brackets</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+d922 4
+a925 4
+ parentheses (such as these).
+ </para>
+ </listitem>
+ <listitem>
+d928 3
+a930 3
+ </para>
+ </listitem>
+ <listitem>
+d933 12
+a944 12
+ instead use the
+ <replaceable><replaceable></replaceable> tag.
+ Refer to <xref linkend="s1-xml-tags-replaceable"/> for
+ information about using this tag.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Capitalization</term>
+ <listitem>
+d948 2
+a949 2
+ <itemizedlist>
+ <listitem>
+d952 4
+a955 4
+ well-known exception
+ </para>
+ </listitem>
+ <listitem>
+d958 3
+a960 3
+ </para>
+ </listitem>
+ <listitem>
+d963 3
+a965 3
+ </para>
+ </listitem>
+ <listitem>
+d968 16
+a983 11
+ <keycap>Shift</keycap> key
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a sentence. Avoid starting a sentence
+ with a command name or application name that has a
+ lowercase initial letter
+ </para>
+ </listitem>
+ <listitem>
+d986 3
+a988 3
+ </para>
+ </listitem>
+ </itemizedlist>
+d990 1
+a990 1
+ Do not capitalize in the following situations:
+d992 2
+a993 2
+ <itemizedlist>
+ <listitem>
+d996 4
+a999 4
+ an acronym
+ </para>
+ </listitem>
+ <listitem>
+d1002 3
+a1004 3
+ </para>
+ </listitem>
+ <listitem>
+d1007 14
+a1020 14
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The initial letter of the first word following a colon,
+ if the word is part of an incomplete sentence
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Captions</term>
+ <listitem>
+d1023 8
+a1030 8
+ accompanying figures and tables. Do not put a period at the
+ end of a caption.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Colon</term>
+ <listitem>
+d1032 1
+a1032 1
+ Use a colon in the following situations:
+d1071 5
+a1075 5
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Column headings</term>
+ <listitem>
+d1078 6
+a1083 6
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Comma</term>
+ <listitem>
+d1085 1
+a1085 1
+ Use commas in the following situations:
+d1087 2
+a1088 2
+ <itemizedlist>
+ <listitem>
+d1091 3
+a1093 3
+ </para>
+ </listitem>
+ <listitem>
+d1096 3
+a1098 3
+ </para>
+ </listitem>
+ <listitem>
+d1101 3
+a1103 3
+ </para>
+ </listitem>
+ <listitem>
+d1106 3
+a1108 3
+ </para>
+ </listitem>
+ <listitem>
+d1111 3
+a1113 3
+ expressions
+ </para>
+ </listitem>
+d1116 1
+a1116 1
+ Do not use commas in the following situations:
+d1118 2
+a1119 2
+ <itemizedlist>
+ <listitem>
+d1122 3
+a1124 3
+ </para>
+ </listitem>
+ <listitem>
+d1127 2
+a1128 2
+ </para>
+ </listitem>
+d1130 13
+a1142 13
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Commands</term>
+ <listitem>
+ <para>
+ Do not use commands as verbs.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-contractions">
+ <term>Contractions</term>
+ <listitem>
+d1145 1
+a1145 1
+ <emphasis>don't</emphasis>, or <emphasis>isn't</emphasis>.
+d1147 16
+a1162 16
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Dash</term>
+ <listitem>
+ <para>
+ Do not use the em dash or the en dash. Use a paragraph break
+ or a colon instead, where you want to create an introductory
+ piece of text. If you have several items that you want to
+ introduce, then you can use a variable list.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Ellipsis</term>
+ <listitem>
+d1165 8
+a1172 8
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To show that you have omitted something from a sentence
+ </para>
+ </listitem>
+ <listitem>
+d1175 2
+a1176 2
+ </para>
+ </listitem>
+d1178 5
+a1182 5
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Fractions</term>
+ <listitem>
+d1186 2
+a1187 2
+ <itemizedlist>
+ <listitem>
+d1190 4
+a1193 4
+ measurement, but spell out fractions in prose.
+ </para>
+ </listitem>
+ <listitem>
+d1196 5
+a1200 5
+ there is a possible ambiguity. For example: 1 1/2
+ instead of 11/2.
+ </para>
+ </listitem>
+ <listitem>
+d1203 9
+a1211 9
+ hyphen between the fraction and the unit of measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Gender</term>
+ <listitem>
+d1215 5
+a1219 5
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Grammar</term>
+ <listitem>
+d1222 9
+a1230 9
+ <citetitle>Chicago Manual of Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">
+ http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Headings</term>
+ <listitem>
+d1233 3
+a1235 3
+ </para>
+ <itemizedlist>
+ <listitem>
+d1239 2
+a1240 2
+ </listitem>
+ <listitem>
+d1243 4
+a1246 4
+ verbs.
+ </para>
+ </listitem>
+ <listitem>
+d1249 4
+a1252 4
+ prepositions of fewer than four letters
+ </para>
+ </listitem>
+ <listitem>
+d1255 4
+a1258 4
+ letters or longer
+ </para>
+ </listitem>
+ <listitem>
+d1261 5
+a1265 5
+ letters or longer
+ </para>
+ </listitem>
+ </itemizedlist>
+ <!-- <para> See <xref linkend="infodesign-2"/> for more
+d1267 14
+a1280 14
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Hyphen</term>
+ <listitem>
+ <para>
+ Use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para> With a numeral in a compound modifier
+ </para>
+ </listitem>
+ <listitem>
+d1283 17
+a1299 17
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With some standard prefixes and suffixes. Use the
+ <citetitle>American Heritage Dictionary</citetitle>
+ (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ for guidance
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In spelled-out fractions
+ </para>
+ </listitem>
+ <listitem>
+d1302 4
+a1305 4
+ <replaceable>directory-name</replaceable>. Note:
+ <replaceable>filename</replaceable> is an exception.
+ </para>
+ </listitem>
+d1308 4
+a1311 4
+ Do not use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+d1314 3
+a1316 3
+ </para>
+ </listitem>
+ <listitem>
+d1319 3
+a1321 3
+ </para>
+ </listitem>
+ <listitem>
+d1324 8
+a1331 8
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With numerals as single modifiers
+ </para>
+ </listitem>
+ <listitem>
+d1334 7
+a1340 7
+ <citetitle>American Heritage Dictionary</citetitle>
+ (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>),
+ and that uses a common prefix
+ </para>
+ </listitem>
+ <listitem>
+d1343 17
+a1359 17
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Latin terms</term>
+ <listitem>
+ <para>
+ Do not use Latin terms. Use an equivalent English term
+ instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Like</term>
+ <listitem>
+d1362 1
+a1362 1
+ equivalence or similarity.
+d1364 5
+a1368 5
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Lists</term>
+ <listitem>
+d1371 1
+a1371 1
+ colon.
+d1373 5
+a1377 5
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numbers</term>
+ <listitem>
+d1381 2
+a1382 2
+ <itemizedlist>
+ <listitem>
+d1384 4
+a1387 4
+ part of a measurement
+ </para>
+ </listitem>
+ <listitem>
+d1390 3
+a1392 3
+ </para>
+ </listitem>
+ <listitem>
+d1395 9
+a1403 9
+ precede the value with a numeral
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Any number that begins a sentence
+ </para>
+ </listitem>
+ <listitem>
+d1406 9
+a1414 9
+ example: two 10 MB files
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numerals</term>
+ <listitem>
+d1417 3
+a1419 3
+ </para>
+ <itemizedlist>
+ <listitem>
+d1422 7
+a1428 7
+ </para>
+ </listitem>
+ <listitem>
+ <para> Negative numbers
+ </para>
+ </listitem>
+ <listitem>
+d1431 3
+a1433 3
+ </para>
+ </listitem>
+ <listitem>
+d1436 3
+a1438 3
+ </para>
+ </listitem>
+ <listitem>
+d1441 8
+a1448 8
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Measurements
+ </para>
+ </listitem>
+ <listitem>
+d1451 3
+a1453 3
+ </para>
+ </listitem>
+ <listitem>
+d1456 8
+a1463 8
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Parentheses</term>
+ <listitem>
+d1466 3
+a1468 3
+ </para>
+ <itemizedlist>
+ <listitem>
+d1471 14
+a1484 14
+ occurrence of the full term
+ </para>
+ </listitem>
+ <listitem>
+ <para> In man page references, specifically the section
+ number
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Period</term>
+ <listitem>
+d1487 3
+a1489 3
+ </para>
+ <itemizedlist>
+ <listitem>
+d1492 3
+a1494 3
+ </para>
+ </listitem>
+ <listitem>
+d1497 3
+a1499 3
+ </para>
+ </listitem>
+ <listitem>
+d1502 30
+a1531 30
+ a.m. and U.S.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation</term>
+ <listitem>
+ <para>
+ Use standard American English punctuation rules. In addition
+ to the specific points of punctuation in this section, refer
+ also to the <citetitle>Chicago Manual of Style</citetitle>
+ (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation in numbers</term>
+ <listitem>
+ <para>
+ Do not use a comma in numerals of four digits. Use a comma
+ in numerals of more than four digits.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Quotation marks</term>
+ <listitem>
+d1534 8
+a1541 7
+ verbatim from another source. Do not use quotation marks to
+ excuse terms from legitimacy. If the term is not legitimate,
+ then use another term. If you must use that term, declare
+ the term in the glossary and make the term legitimate.
+ </para>
+ </listitem>
+ </varlistentry>
+d1543 1
+a1543 1
+ <term>See v. Refer to</term>
+d1547 9
+a1555 9
+ instead of "see", and "refer also to" instead of "see also".
+ This differentiates from the
+ <computeroutput><see></computeroutput> and
+ <computeroutput><seealso></computeroutput> tags that
+ are used in indexing. These tags create special links in
+ the index. To be consistent throughout the document, we
+ reserve the special words "see" and "see also" for
+ hyperlinked index references, and use "refer to" and "refer
+ also to" for non-hyperlinked and non-indexed references.
+d1559 3
+a1561 3
+ <varlistentry>
+ <term>Semicolon</term>
+ <listitem>
+d1563 1
+a1563 1
+ Do not use semicolons.
+d1565 2
+a1566 2
+ </listitem>
+ </varlistentry>
+d1572 3
+a1574 3
+ slashes "/" in your writing. The construction
+ "and/or," for example, does not exist. Use one or the
+ other term instead.
+d1578 3
+a1580 3
+ <varlistentry>
+ <term>Spelling</term>
+ <listitem>
+d1583 9
+a1591 9
+ <citetitle>American Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ for guidelines.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Titles</term>
+ <listitem>
+d1594 6
+a1599 6
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Units</term>
+ <listitem>
+d1603 2
+a1604 2
+ <itemizedlist>
+ <listitem>
+d1607 13
+a1619 11
+ not invent your own abbreviations.
+ </para>
+ </listitem>
+ <listitem>
+ <para> <!-- See <xref linkend="units"/> for a list of
+ units relevant to the GNOME Desktop. --> For further
+ guidelines, refer to the <citetitle>IEEE Standard Dictionary
+ of Electrical and Electronics Terms</citetitle>.
+ </para>
+ </listitem>
+ <listitem>
+d1622 4
+a1625 4
+ for a word.
+ </para>
+ </listitem>
+ <listitem>
+d1628 4
+a1631 4
+ singular and plural usage.
+ </para>
+ </listitem>
+ <listitem>
+d1634 7
+a1640 7
+ measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+d1650 5
+a1654 5
+ This section will collect miscellanea and advice for specific situations
+ that the &FDP; editors encounter. I hope they will feel free to e-mail
+ me sticky situations or particularly interesting examples of work
+ they've beautified. Hopefully not too much will be drawn from my own
+ work!
+d1660 2
+a1661 2
+ editors have encountered in the past. You should read and
+ understand these examples to improve your own documentation. The
+d1669 9
+a1677 9
+ tutorial tells the user how to accomplish a task, and should
+ give instructions clearly and concisely. Avoid using "must,"
+ "need to," and the like. These words are redundant in a
+ tutorial, since the reader assumes you are outlining necessary
+ steps to accomplish a task. Also avoid using "should," "might,"
+ and other words that indicate you are unsure about the subject
+ matter. Your tutorial should cover a subject authoritatively.
+ The reader should never be concerned about unknown effects of
+ following the tutorial.
+d1685 2
+a1686 1
+ You should run the <command>yum update</command> command.
+d1700 6
+a1705 7
+ Write in the present tense. A good rule of thumb is that the
+ words "will" and "shall" are almost never needed in describing
+ what the user should do or see. They add unnecessary length to
+ sentences and can confuse translators. They are also often
+ indicators of passive voice; refer also to
+ <xref
+ linkend="sn-misc-active-voice"/>.
+d1723 1
+a1723 1
+
+d1728 5
+a1732 5
+ yourself the writer (whether including the reader or not), the
+ &FDP;, the &FED; community, or any other group. Do not refer to
+ users with a third person pronoun ("he," "she," or "he or she")
+ or the word "one." It is acceptable to refer to the reader with
+ the second person pronoun "you."
+d1738 2
+a1739 2
+ <command>up2date</command> before configuring the Samba
+ server.
+d1743 1
+a1743 1
+ the <command>tar</command> or <command>cpio</command> command.
+d1750 1
+a1750 1
+ configuring the Samba server.
+d1753 2
+a1754 2
+ Users can back up files with the <command>tar</command> or
+ <command>cpio</command> command.
+d1762 6
+a1767 6
+ Avoid negative words when possible, since they give documentation
+ an overly dogmatic tone. The word "avoid" is useful for this
+ purpose. Note that contractions are often used for negative
+ words such as <emphasis>don't</emphasis> or
+ <emphasis>can't</emphasis>. Refer to <xref
+ linkend="vle-contractions" />.
+d1775 6
+a1780 6
+ the like. While occasional use of these constructions is
+ acceptable, overuse reduces the authority of your documentation.
+ The documentation should adequately cover a stock installation
+ of &FC;. It is impossible for a tutorial-length document to
+ cover every possible configuration scenario. Address the most
+ common scenarios and note discrepancies only as required.
+d1788 6
+a1793 6
+ system. These overarching topics may be covered in other
+ tutorials. Writers frequently violate this guideline because
+ they feel their tutorial is not long enough. Keep your tutorial
+ from wandering off-topic. Instead, refer the reader to a
+ separate tutorial whenever possible for complete coverage of
+ that topic.
+d1800 10
+a1809 10
+ Avoid statements like "One of the most important things to do is
+ <replaceable>XYZ</replaceable>." If the procedure is important,
+ the reader already expects it to be in your tutorial. The
+ converse is also true: if a procedure appears in your tutorial,
+ the reader expects it is important. This is especially true if
+ you use a whole section for the procedure in question. Merely
+ state, "Do <replaceable>XYZ</replaceable>." Then elaborate as
+ required. If the whole section concerns how to do
+ <replaceable>XYZ</replaceable>, leave this sentence out
+ entirely. Refer also to <xref linkend="vle-golden-rule-4" />.
+d1816 2
+a1817 2
+ Use precise words for actions users should take. Do not instruct
+ users to "go" to a selection, or "find" a menu.
+d1825 1
+a1825 1
+ <guimenuitem>Foobar</guimenuitem>
+d1841 1
+a1841 1
+ <guimenuitem>Foobar</guimenuitem>
+d1855 3
+a1857 3
+ "click" freely. If you are writing about an application that
+ has a text-mode interface, use "select" instead as shown
+ above.
+d1862 1
+a1862 1
+
+d1867 1
+a1867 1
+ effectively in your documentation.
+d1873 4
+a1876 5
+ Avoid overuse of admonitions. Use only the most important
+ material inside the admonition. Doing so will keep
+ admonitions short and effective. Any background material
+ required to explain the most important admonition statements
+ should be moved outside the admonition.
+d1885 7
+a1891 7
+ file as standard input to set up partitions on a hard
+ disk. Sometimes <command>sfdisk</command> will simply
+ reject an erroneous input file. In other cases, it will
+ use the input verbatim, writing an incorrect partition
+ table to your disk. Always use the <command>sfdisk
+ -n</command> command to check your input file before
+ writing to the disk.
+d1899 5
+a1903 5
+ The <command>sfdisk</command> command accepts a script file
+ as standard input to set up partitions on a hard disk.
+ Sometimes <command>sfdisk</command> will simply reject an
+ erroneous input file. In other cases, it will use the input
+ verbatim, writing an incorrect partition table to your disk.
+d1908 1
+a1908 1
+ check your input file before writing to the disk.
+d1915 4
+a1918 4
+ except for commas only where demanded. Use a title that says
+ something about the admonition comment, such as "Reboot
+ required," instead of simply using the admonition type for a
+ title ("Note").
+d1920 4
+d1927 2
+a1928 1
+ <title>The <replaceable> Tag</title>
+d1931 3
+a1933 2
+ used as a convention, do not use the <replaceable> tag
+ in your text or examples.
+d1940 7
+a1946 8
+ Use the entities provided by the &FDP;. These entities are found
+ in the <filename>common/</filename> folder in the
+ <filename>fedora-docs</filename> distribution. (Refer also to
+ <xref
+ linkend="ch-getting-files"/>.) For instance, do not use
+ abbreviations such as "FC2." Instead, use the predefined
+ entities "&FC; &FCVER;," which produces the text "&FC;
+ &FCVER;."
+d1951 1
+a1951 1
+
+d1953 1
+a1953 1
+
+d1955 1
+d1960 1
+a1962 1
+
+@
+
+
+1.2
+log
+ at These changes only reflect the inclusion of the local variables and the associate adjusting of indenting.
+@
+text
+ at d4 1
+a4 1
+
+d25 1
+a25 1
+ excessive wordiness
+d30 1
+a30 1
+ unnecessary or undefined jargon
+d35 1
+a35 1
+ grammatical or spelling errors
+d40 1
+a40 1
+ references to yourself or your experiences
+d45 1
+a45 1
+ remarks which might offend or confuse any reader
+d63 1
+a63 1
+ Writing well comes naturally to almost no one. It is a skill that
+d67 4
+a70 2
+ that separates elegant writing from the merely functional.
+ </para> <para> Elegance comes in many forms. In prose and poetry,
+d72 1
+a72 1
+ grammar, syntax or spelling. A good example is Episode 18,
+d74 3
+a76 2
+ <citetitle>Ulysses</citetitle><footnote id='fn-ulysses'> <para>
+ See, e.g. <ulink
+d79 2
+a80 1
+ language, and is not suitable for all readers. </para>
+d93 1
+a93 1
+ idiom, or jargon, a reader or translator may easily become
+d95 1
+a95 1
+ written executions of the same idea:
+d126 5
+a130 9
+ </example>
+ <para>
+ The first example is more conversational English, which is not
+ appropriate for official written documentation. The second example
+ is more formal, but as a result it is easier to comprehend, both
+ for native readers and translators.
+ </para>
+ <para>
+ Following style rules and guidelines also makes readers more
+d138 10
+a147 15
+ author's use of language.
+ </para>
+ <para>
+ This chapter cannot possibly cover enough material to make every
+ reader a good writer. Some manuals devoted entirely to writing
+ style are themselves hundreds of pages long. This chapter provides
+ enough guidelines for intermediate writers to understand style
+ usage in technical documentation.
+ </para>
+ <para>
+ If you are not a practiced writer, whether of technical
+ documentation or otherwise, you may benefit from other style
+ resources. The following list is far from comprehensive, but
+ provides a starting point:
+ </para>
+d152 1
+a152 1
+ Strunk. Online version: <ulink
+d156 10
+d167 2
+a168 3
+ <!-- KWade/TFox: Please check citation below, since I don't have
+ a copy. Thanks! And, um, I'm not sure if I should be using a
+ formal citation style below. /me is embarrassed. [PWF] -->
+d237 4
+a240 1
+ <term>Conformant</term>
+d253 12
+a264 5
+ Read <ulink
+ url="http://www.bartleby.com/141/"><citetitle>The
+ Elements of Style</citetitle></ulink> to help make
+ your writing clear.
+ </para>
+d281 3
+a283 3
+ Review your work frequently as you write your document. Ask
+ yourself which words you can take out. See <xref
+ linkend="sn-fundamentals-2"/> for a specific guideline.
+d298 1
+a298 1
+ <term>Golden Rule 1: Be brief.</term>
+d303 1
+a303 1
+ Limit each sentence to less than 25 words.
+d330 1
+a330 1
+ <term>Golden Rule 2: Be organized.</term>
+d390 1
+a390 1
+ <term>Golden Rule 3: Be demonstrative.</term>
+d421 1
+a421 1
+ <term>Golden Rule 4: Be objective.</term>
+d577 3
+a579 1
+ A term does not appear in the &FED; Jargon Guide.
+d584 4
+a587 4
+ A term does not appear in the <ulink
+ url="http://www.bartleby.com/61/">
+ <citetitle>American Heritage
+ Dictionary</citetitle></ulink>.
+d666 5
+a670 5
+ guidelines are only applicable to English-language usage, see the
+ <ulink url="http://www.bartleby.com/61/"> <citetitle>American
+ Heritage Dictionary </citetitle></ulink> and the <ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">
+ <citetitle>Chicago Manual of Style</citetitle></ulink>.
+d700 5
+d935 4
+a938 1
+ instead use the <emphasis>replaceable</emphasis> tag.
+d1209 2
+a1210 1
+ <para> See <xref linkend="sn-fundamentals-9"/>.
+d1218 2
+a1219 1
+ Use standard American English grammar rules, see the <ulink
+d1221 1
+a1221 1
+ <citetitle>Chicago Manual of Style</citetitle></ulink>.
+d1246 1
+a1246 1
+ prepositions of less than four letters
+d1284 5
+a1288 3
+ With some standard prefixes and suffixes. Use the <ulink
+ url="http://www.bartleby.com/61/"> <citetitle>American
+ Heritage Dictionary</citetitle></ulink> for guidance
+d1299 1
+a1299 1
+ <replaceable> directory-name</replaceable>. Note:
+d1330 5
+a1334 4
+ With a word that is listed as unhyphenated in the <ulink
+ url="http://www.bartleby.com/61/"> <citetitle>American
+ Heritage Dictionary</citetitle></ulink>, and that
+ uses a common prefix
+d1510 4
+a1513 4
+ to the specific points of punctuation in this section, see
+ also the <ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">
+ <citetitle>Chicago Manual of Style</citetitle></ulink>.
+d1538 17
+d1578 4
+a1581 3
+ Use standard American English spelling rules, see the <ulink
+ url="http://www.bartleby.com/61/"> <citetitle>American
+ Heritage Dictionary</citetitle></ulink> for guidelines.
+d1609 1
+a1609 1
+ guidelines, see the <citetitle>IEEE Standard Dictionary
+d1697 1
+a1697 1
+ indicators of passive voice; see also
+d1760 1
+a1760 1
+ <emphasis>can't</emphasis>. See <xref
+d1803 1
+a1803 2
+ entirely. See also <xref linkend="vle-golden-rule-4"
+ />.
+d1931 1
+a1931 1
+ <filename>fedora-docs</filename> distribution. (See also
+d1941 1
+a1941 1
+
+d1943 1
+a1943 1
+
+d1951 1
+@
+
+
+1.1
+log
+ at This represents that state of the Doc Guide with Paul's Style chapter included, prior to _any_ editing from me.
+@
+text
+ at d1 1
+a1 1
+ <chapter id="ch-style">
+d12 1
+a12 1
+ <title>Style</title>
+d14 48
+d63 19
+a81 6
+ Writing good technical documentation is not simply reproducing
+ command lines and instruction sets. Good documentation is easy to
+ read, understand, and translate, and presents a concise logical
+ progression of concepts. Good documentation can also be defined by
+ what it does <emphasis>not</emphasis> contain. Your tutorial
+ should avoid:
+a82 27
+ <itemizedlist>
+ <listitem>
+ <para>
+ excessive wordiness
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ unnecessary or undefined jargon
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ grammatical or spelling errors
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ references to yourself or your experiences
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ remarks which might offend or confuse any reader
+ </para>
+ </listitem>
+ </itemizedlist>
+d84 8
+a91 6
+ In this chapter, you will find style rules and guidelines for
+ writing &FED; documentation. Guidelines are not the same as
+ rules. It is acceptable to violate a guideline when it makes your
+ material easier to understand. Follow guidelines whenever
+ possible, but follow rules at all times. Assume any advice is a
+ guideline unless identified otherwise.
+d93 2
+a94 42
+
+ <section id="sn-intro-to-style">
+
+ <title>Why Style Is Important</title>
+
+ <para>
+ Writing well comes naturally to almost no one. It is a skill
+ that professional writers, even famous ones, must practice
+ constantly. <firstterm>Style</firstterm>
+ <indexterm><primary>style</primary></indexterm> is the quality
+ that separates elegant writing from the merely functional.
+ </para>
+ <para>
+ Elegance comes in many forms. In prose and poetry, elegant
+ writing may not follow some (or any) common rules of grammar,
+ syntax or spelling. A good example is Episode 18, "Penelope," in
+ James Joyce's novel <citetitle>Ulysses</citetitle><footnote
+ id='fn-ulysses'>
+ <para>
+ See, e.g. <ulink
+ url="http://www.online-literature.com/james_joyce/ulysses/18/">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>.
+ Please note that this example contains some mature themes
+ and language, and is not suitable for all readers.
+ </para>
+ </footnote>. There, Joyce uses long streams of words without
+ punctuation to simulate a character's internal consciousness. By
+ violating basic rules of grammar and syntax, Joyce simulates the
+ disorganized but loosely connected thought patterns of his
+ narrator.
+ </para>
+ <para>
+ Technical documentation, however, should always respect these
+ rules. The more a document departs from standard language usage,
+ the more difficult the material becomes for the reader. For
+ example, readers may not be native speakers of the language
+ used, or they might be reading a translation. If the writer uses
+ slang, idiom, or jargon, a reader or translator may easily
+ become confused. Take the following example, which compares two
+ different written executions of the same idea:
+ </para>
+ <example>
+ <title>Incorrect style</title>
+d102 9
+a110 9
+ <para>
+ So you made the changes I showed you in the last section.
+ What's the next thing you should do? Just pop your thumb drive
+ onto your system and read the <filename>messages</filename>
+ log. When you see "USB device found," then Bob's your uncle.
+ </para>
+ </example>
+ <example>
+ <title>Correct style</title>
+a113 9
+ <para>
+ After you complete the configuration changes above, attach the
+ USB removable media to your system. Use the
+ <command>dmesg</command> command to examine the kernel message
+ log. The message <computeroutput>USB device
+ found</computeroutput> indicates that your device was
+ installed successfully.
+ </para>
+ </example>
+d115 46
+a160 37
+ The first example is more conversational English, which is not
+ appropriate for official written documentation. The second
+ example is more formal, but as a result it is easier to
+ comprehend, both for native readers and translators.
+ </para>
+ <para>
+ Following style rules and guidelines also makes readers more
+ comfortable with a set of documents. Consistent style enhances
+ the professional appearance of documentation, and its perceived
+ value. On the other hand, lapses in punctuation or poor grammar
+ negatively affect a reader's reaction to written material. A
+ reader can feel that an otherwise correct technical document is
+ lacking in authority, simply because it is poorly
+ written. Readers feel at ease when they do not have to struggle
+ to understand an author's use of language.
+ </para>
+ <para>
+ This chapter cannot possibly cover enough material to make every
+ reader a good writer. Some manuals devoted entirely to writing
+ style are themselves hundreds of pages long. This chapter
+ provides enough guidelines for intermediate writers to
+ understand style usage in technical documentation.
+ </para>
+ <para>
+ If you are not a practiced writer, whether of technical
+ documentation or otherwise, you may benefit from other style
+ resources. The following list is far from comprehensive, but
+ provides a starting point:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <citetitle>The Elements of Style</citetitle>, by William
+ Strunk. Online version: <ulink
+ url="http://bartleby.com/141/">http://bartleby.com/141/</ulink>
+ </para>
+ </listitem>
+d166 23
+a188 23
+ <listitem>
+ <para>
+ <citetitle>The Chicago Manual of Style</citetitle>, by the
+ University of Chicago Press. Online version: <ulink
+ url="http://www.chicagomanualofstyle.org/">http://www.chicagomanualofstyle.org/</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <citetitle>Paradigm Online Writing Assistant</citetitle>,
+ maintained by Chuck Guilford, Ph.D. Online only: <ulink
+ url="http://www.powa.org/">http://www.powa.org/</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ There are many free software documentation projects which have
+ developed their own style guidelines. This chapter, in fact,
+ draws heavily on the <citetitle>GNOME Documentation Style
+ Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may
+ read the original <citetitle>GDSG</citetitle> at <ulink
+ url='http://developer.gnome.org/documents/style-guide/'>http://developer.gnome.org/documents/style-guide/</ulink>.
+ </para>
+d190 1
+a190 1
+ </section>
+d192 1
+a192 1
+ <section id="sn-tech-docs-fundamentals">
+d194 1
+a194 1
+ <title>Fundamental Concepts of Technical Documentation</title>
+d196 7
+a202 7
+ <note>
+ <title>Bibliographic Information</title>
+ <para>
+ This section is drawn primarily from the
+ <citetitle>GDSG</citetitle>.
+ </para>
+ </note>
+d209 68
+d278 3
+a280 2
+ This chapter provides a brief introduction to writing technical
+ documentation.
+d282 145
+d428 1
+a428 418
+ <section id="sn-fundamentals-1">
+ <title>General Style Requirements</title>
+ <para>
+ Technical writing for the &FP; imposes special constraints
+ beyond the basic requirements of good prose. Good &FED;
+ technical documentation has the following characteristics:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Comprehensive</term>
+ <listitem>
+ <para>
+ Describe all of the functionality of a product. Do not
+ omit functionality that you regard as irrelevant for the
+ user.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Conformant</term>
+ <listitem>
+ <para>
+ Describe what you see. Do not describe what you want to
+ see. Present your information in the order that users
+ experience the subject matter.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Clear</term>
+ <listitem>
+ <para>
+ Read <ulink
+ url="http://www.bartleby.com/141/"><citetitle>The
+ Elements of Style</citetitle></ulink> to help make
+ your writing clear.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Consistent</term>
+ <listitem>
+ <para>
+ Use agreed vocabulary throughout your documentation. Use
+ the same vocabulary as other writers who are working on
+ related documentation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Concise</term>
+ <listitem>
+ <para>
+ Review your work frequently as you write your document.
+ Ask yourself which words you can take out. See <xref
+ linkend="sn-fundamentals-2"/> for a specific
+ guideline.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-2">
+ <title>Golden Rules</title>
+ <para>
+ This section contains some basic style guidelines. Subsequent
+ sections in this chapter expand on these guidelines to give
+ more detailed guidance.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Golden Rule 1: Be brief.</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Limit each sentence to less than 25 words.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each procedure step to 23 words.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-1-wrong">
+ <title>Incorrect: Too long</title>
+ <para>
+ Under normal operating conditions, the kernel does not
+ always immediately write file data to the disks,
+ storing it in a memory buffer and then periodically
+ writing to the disks to speed up operations.
+ </para>
+ </example>
+ <example id="ex-golden-rule-1-right">
+ <title>Correct: Less wordy</title>
+ <para>
+ Normally, the kernel stores the data in memory prior
+ to periodically writing the data to the disk.
+ </para>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Golden Rule 2: Be organized.</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Limit each paragraph to one topic.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each sentence to one idea.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each procedure step to one action.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-2-wrong">
+ <title>Incorrect: Disorganized topics</title>
+ <para>
+ The <application>Workspace Switcher</application>
+ applet helps you navigate all of the virtual desktops
+ available on your system. The X Window system, working
+ in hand with a piece of software called a
+ <emphasis>window manager</emphasis>, allows you to
+ create more than one virtual desktop, known as
+ <emphasis>workspaces</emphasis>, to organize your
+ work, with different applications running in each
+ workspace. The <application>Workspace
+ Switcher</application> applet is a navigational tool
+ to get around the various workspaces, providing a
+ miniature road map in the GNOME panel showing all your
+ workspaces and allowing you to switch easily between
+ them.
+ </para>
+ </example>
+ <example id="ex-golden-rule-2-right">
+ <title>Correct: Organized topics</title>
+ <para>
+ You can use the <application>Workspace
+ Switcher</application> to add new
+ <emphasis>workspaces</emphasis> to the GNOME Desktop.
+ You can run different applications in each workspace.
+ The <application>Workspace Switcher</application>
+ applet provides a miniature map that shows all of your
+ workspaces. You can use the <application>Workspace
+ Switcher</application> applet to switch between
+ workspaces.
+ </para>
+ </example>
+ <tip>
+ <para>
+ Plan the order of paragraphs before you start writing.
+ Decide which topic you want to cover in each
+ paragraph.
+ </para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Golden Rule 3: Be demonstrative.</term>
+ <listitem>
+ <para>
+ Use explicit examples to demonstrate how an application
+ works. Provide instructions rather than descriptions.
+ </para>
+ <example id="ex-golden-rule-3-wrong">
+ <title>Incorrect: Describes but does not
+ demonstrate</title>
+ <para>
+ There is a text box that you can use to find out the
+ definition of a word.
+ </para>
+ </example>
+ <example id="ex-golden-rule-3-right">
+ <title>Correct: Demonstrates usage</title>
+ <para>
+ To request a definition of a word, type the word in
+ the text box, then click on the Lookup button.
+ </para>
+ </example>
+ <tip>
+ <para>
+ Do not apply this guideline too rigidly. Sometimes you
+ must explain how software works to support your how-to
+ examples.
+ </para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-golden-rule-4">
+ <term>Golden Rule 4: Be objective.</term>
+ <listitem>
+ <para>
+ Write in a neutral tone.
+ </para>
+ <example id="ex-golden-rule-4-wrong">
+ <title>Incorrect: Sentence takes sides</title>
+ <para>
+ The applet is a handy little screen grabber.
+ </para>
+ </example>
+ <example id="ex-golden-rule-4-right">
+ <title>Correct: Sentence is objective</title>
+ <para>
+ Use the applet to take screenshots.
+ </para>
+ </example>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="sn-fundamentals-3">
+
+ <title>Tone</title>
+ <para>
+ Inappropriate tone can hinder reader access to information. A
+ neutral tone free of opinion or personal flavor reduces the
+ processing load for the reader to understand the information.
+ Another benefit of a neutral tone is that several writers can
+ work in parallel on a large technical documentation project.
+ Furthermore, different writers can join the project at
+ different times. The use of a neutral tone helps to achieve
+ consistency across a documentation set, and thereby
+ facilitates user access to information. The best way to
+ achieve a common, neutral tone is to apply the following
+ principles:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Avoid humor</term>
+ <listitem>
+ <para>
+ Humor distracts from the information you are trying to
+ provide. Humor also makes documentation difficult to
+ translate. Stay factual.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid personal opinions</term>
+ <listitem>
+ <para>
+ Whether you think a function is useful or woeful is
+ irrelevant. Report the function to the user, with
+ instructions about how to use the function. Stay
+ accurate.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid colloquial language</term>
+ <listitem>
+ <para>
+ Colloquial language is difficult to translate and
+ usually culture-specific. Stay neutral.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid topical expressions</term>
+ <listitem>
+ <para>
+ An expression that is in common use today might convey
+ something completely different tomorrow. Stay technical.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid aspirational statements</term>
+ <listitem>
+ <para>
+ Statements about the future developments of a product do
+ not belong in technical documentation. Write about what
+ you see right now. Stay real.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-4">
+ <title>Reaching the Right Audience</title>
+ <para>
+ All of the decisions that you make about the structure and
+ content of a manual follow from an understanding of the
+ audience. You need to think about how the audience accesses
+ the documentation, what sort of information the audience
+ needs, and the experience level of the audience. Usually, you
+ need to create documentation that is suitable for different
+ audiences. The following sections introduce some of the
+ audience-related topics you need to consider.
+ </para>
+ </section>
+ <section id="sn-fundamentals-6">
+ <title>User Motivation</title>
+ <para>
+ Do not waste the time of the user who looks for information in
+ your documentation. Users do not read technical documentation
+ for entertainment. Users usually have specific questions. You
+ need to give clear answers to those questions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-7">
+ <title>New Users</title>
+ <para>
+ New users to &FC; are likely to consult online tutorials for
+ guidance about unfamiliar applications or functionality. Each
+ tutorial should contain enough introductory information to
+ tell new users how to start using the relevant functions. Each
+ tutorial should also contain enough usage instructions to tell
+ users the different actions that they can perform with the
+ command or function. Keep these instructions task-oriented.
+ You do not need to describe GUI screens, dialogs, and dialog
+ elements in a tutorial, unless there is an unusual feature
+ that affects your instructions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-8">
+ <title>Experienced Users</title>
+ <para>
+ Experienced users are more likely to use documentation as a
+ reference. The documentation therefore needs to be complete,
+ well-organized, and in the case of printed manuals,
+ well-indexed.
+ </para>
+ </section>
+ <section id="sn-fundamentals-9">
+ <title>Do Not Offend Your Audience</title>
+ <para>
+ To avoid offending your readers, apply the following
+ guidelines to your documentation:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Avoid insider language</term>
+ <listitem>
+ <para>
+ Insider language includes both undefined jargon and the
+ tendency of the computer community to shorten words. For
+ example, use the term <emphasis>documentation</emphasis>
+ instead of the term <emphasis>docs</emphasis>. You can
+ identify jargon if terminology fails the following
+ conditions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ A term does not appear in the &FED; Jargon Guide.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A term does not appear in the <ulink
+ url="http://www.bartleby.com/61/">
+ <citetitle>American Heritage
+ Dictionary</citetitle></ulink>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A term does not appear in the glossary of the manual
+ that you are writing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A term is not defined in the body text of the manual
+ that you are writing.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid gender-specific language</term>
+ <listitem>
+ <para>
+ Pronoun constructions such as
+ <emphasis>his/her</emphasis> or
+ <emphasis>s/he</emphasis> do not exist. There is no need
+ to identify gender in your instructions.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid culture-specific language</term>
+ <listitem>
+ <para>
+ There is little point in giving an example that everyone
+ in your town knows about, but is a complete mystery to
+ everyone else in the world.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid talking down to your reader</term>
+ <listitem>
+ <para>
+ There are few experiences more irritating for a user
+ than documentation that says an action is easy or quick,
+ when in fact the user cannot complete the action. Do not
+ qualify or prejudge actions.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Other parts of this guide discuss in more detail tone and
+ language usage that can cause offense.
+ </para>
+d430 1
+a430 1
+ </section>
+d432 63
+d496 129
+d626 5
+a630 1
+ <section id="sn-grammar-and-usage">
+d632 1
+a632 1
+ <title>Grammar and Usage Guidelines</title>
+d634 9
+a642 9
+ <note>
+ <title>Bibliographical Information</title>
+ <para>
+ This section is drawn partly from the <citetitle>GDSG</citetitle>, and
+ partly from <citetitle>The Elements of Style</citetitle>, updated as
+ necessary for the needs of 21st-century technical documentation
+ writers.
+ </para>
+ </note>
+d647 589
+a1235 598
+ <para>
+ This section contains an alphabetical list of grammar and usage
+ guidelines for use in &FED; documentation. Many of these guidelines are
+ only applicable to English-language usage, see the <ulink
+ url="http://www.bartleby.com/61/"> <citetitle>American Heritage
+ Dictionary </citetitle></ulink> and the <ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">
+ <citetitle>Chicago Manual of Style</citetitle></ulink>.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Abbreviations</term>
+ <listitem>
+ <para>
+ A shortened form of a word or phrase that takes the place
+ of the full word or phrase, for example Dr., a.m., p.m.,
+ and so on. Apply the following rules when you use
+ abbreviations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Avoid creating new abbreviations. Unfamiliar
+ abbreviations can confuse rather than clarify a
+ concept.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not explain or expand familiar abbreviations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not include familiar abbreviations in the glossary
+ of your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adjectives</term>
+ <listitem>
+ <para>
+ Use adjectives with caution. If an adjective is necessary
+ to differentiate between items, then use adjectives. In
+ all cases, test whether the phrase can stand alone without
+ the adjective.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Acronyms</term>
+ <listitem>
+ <para>
+ A term that represents a multi-word term. Typically,
+ acronyms are formed in the following ways:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ From the first letters of each word in a compound
+ term, for example Table of Contents (TOC).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ From recognizable parts of a compound term, such as
+ GNU Object Model Environment (GNOME).
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Apply the following rules when you use acronyms:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ On the first occurrence of an acronym, spell out the
+ full term, with the acronym in parentheses.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not spell out the full compound for well-known
+ acronyms, unless you think the information is useful
+ for readers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Avoid creating new acronyms. Unfamiliar acronyms can
+ confuse rather than clarify a concept.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Write the acronym in uppercase letters, unless there
+ is a compelling case for lowercase.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Include the acronym and the full term in the glossary
+ of your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adverbs</term>
+ <listitem>
+ <para>
+ Use adverbs with caution. If an adverb is necessary to
+ qualify the function of a component, then use an adverb.
+ In all cases, test whether the phrase can stand alone
+ without the adverb. Classic superfluous adverbs are:
+ <emphasis>simply, easily, quickly</emphasis>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Anthropomorphism</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not apply emotions, desires, or opinions to
+ software applications.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not apply a sense of location or dimension to a
+ software application. You can not be
+ <emphasis>in</emphasis> a text editor.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Articles</term>
+ <listitem>
+ <para>
+ Do not use the definite article <emphasis>the</emphasis>
+ to begin any of the following items:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Manual titles
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter titles
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Headings
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Figure captions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Table captions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Callouts
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Apostrophe</term>
+ <listitem>
+ <para>
+ Do not use apostrophes except where absolutely
+ required
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote possession.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote contractions.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote plurals.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-apostrophe-wrong">
+ <title>Incorrect: Apostrophes</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <guimenu>Main Menu's</guimenu>
+ <guimenuitem>Help</guimenuitem> option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ don't use the default option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ several SCSI disk's
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-apostrophe-right">
+ <title>Correct: No apostrophes</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <guimenuitem>Help</guimenuitem> option on the
+ <guimenu>Main Menu</guimenu>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ do not use the default option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ several SCSI disks
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Brackets</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not use brackets [such as these] as a substitute
+ for parentheses (such as these).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use brackets for optional command line entries.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use angle brackets to indicate variables in
+ text, instead use the <emphasis>replaceable</emphasis>
+ tag.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Capitalization</term>
+ <listitem>
+ <para>
+ Capitalize in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ All letters in acronyms, unless the acronym is a
+ well-known exception
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of the first word in a list
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of the first word in a callout
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a key name, such as the
+ <keycap>Shift</keycap> key
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a sentence. Avoid starting a
+ sentence with a command name or application name that
+ has a lowercase initial letter
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a complete sentence after a colon
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not capitalize in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ A compound term that is followed by an abbreviation or
+ an acronym
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When you want to emphasize something
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Variable names
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The initial letter of the first word following a
+ colon, if the word is part of an incomplete sentence
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Captions</term>
+ <listitem>
+ <para>
+ Use the same rules as for headings, for all captions
+ accompanying figures and tables. Do not put a period at
+ the end of a caption.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Colon</term>
+ <listitem>
+ <para>
+ Use a colon in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To introduce a list
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Before an explanation
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ After an introduction
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use a colon in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To introduce a figure or a table
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To introduce headings
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ At the end of an introduction to a procedure
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Column headings</term>
+ <listitem>
+ <para>
+ Use the same rules as for headings.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Comma</term>
+ <listitem>
+ <para>
+ Use commas in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To separate items in a series
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To separate the parts of a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To separate nonrestrictive phrases
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Instead of dashes to set off appositives
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With <emphasis>for example</emphasis> and similar
+ expressions
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use commas in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ In a series of adjectives used as one modifier
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Between two short independent clauses
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Commands</term>
+ <listitem>
+ <para>
+ Do not use commands as verbs.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-contractions">
+ <term>Contractions</term>
+ <listitem>
+ <para>
+ Do not use contractions such as
+ <emphasis>can't</emphasis>, <emphasis>don't</emphasis>, or
+ <emphasis>isn't</emphasis>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Dash</term>
+ <listitem>
+ <para>
+ Do not use the em dash or the en dash. Use a paragraph
+ break or a colon instead, where you want to create an
+ introductory piece of text. If you have several items that
+ you want to introduce, then you can use a variable list.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Ellipsis</term>
+ <listitem>
+ <para>
+ Use an ellipsis in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To show that you have omitted something from a
+ sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To indicate a pause when you quote displayed text
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Fractions</term>
+ <listitem>
+ <para>
+ Follow these rules when using fractions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use numerals for fractions in tables and in units of
+ measurement, but spell out fractions in prose.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use a space between a numeral and a related fraction,
+ if there is a possible ambiguity. For example: 1
+ 1/2 instead of 11/2.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If a fraction is used in a compound modifier, insert a
+ hyphen between the fraction and the unit of
+ measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Gender</term>
+ <listitem>
+ <para>
+ See <xref linkend="sn-fundamentals-9"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Grammar</term>
+ <listitem>
+ <para>
+ Use standard American English grammar rules, see the
+ <ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">
+ <citetitle>Chicago Manual of Style</citetitle></ulink>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Headings</term>
+ <listitem>
+ <para>
+ Use the following capitalization rules in headings:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Initial uppercase letter of the first word
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for all nouns, adjectives,
+ and verbs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All lowercase letters for conjunctions, articles, and
+ prepositions of less than four letters
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for prepositions of four
+ letters or longer
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for conjunctions of four
+ letters or longer
+ </para>
+ </listitem>
+ </itemizedlist>
+d1238 350
+a1587 359
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Hyphen</term>
+ <listitem>
+ <para>
+ Use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ With a numeral in a compound modifier
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To prevent ambiguity
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With some standard prefixes and suffixes. Use the
+ <ulink url="http://www.bartleby.com/61/">
+ <citetitle>American Heritage
+ Dictionary</citetitle></ulink> for guidance
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In spelled-out fractions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In variable names of two or more words, such as
+ <replaceable> directory-name</replaceable>. Note:
+ <replaceable>filename</replaceable> is an exception.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ For industry-accepted terms
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To construct verbs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With an adverb ending in <emphasis>ly</emphasis>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With numerals as single modifiers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With a word that is listed as unhyphenated in the
+ <ulink url="http://www.bartleby.com/61/">
+ <citetitle>American Heritage
+ Dictionary</citetitle></ulink>, and that uses a
+ common prefix
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With trademarked terms
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Latin terms</term>
+ <listitem>
+ <para>
+ Do not use Latin terms. Use an equivalent English term
+ instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Like</term>
+ <listitem>
+ <para>
+ Do not use the term <emphasis>like</emphasis> to
+ denote equivalence or similarity.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Lists</term>
+ <listitem>
+ <para>
+ Introduce a list with a complete sentence that ends with a
+ colon.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numbers</term>
+ <listitem>
+ <para>
+ Spell out numbers in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Numbers from zero through nine unless the number
+ is part of a measurement
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Approximations
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Extreme values such as <emphasis>million</emphasis>,
+ but precede the value with a numeral
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Any number that begins a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A number that is immediately followed by a numeral,
+ for example: two 10 MB files
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numerals</term>
+ <listitem>
+ <para>
+ Use numerals in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The number 10 or greater
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Negative numbers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Most fractions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Percentages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Decimals
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Measurements
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Units of time smaller than one second
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ References to bits and bytes
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Parentheses</term>
+ <listitem>
+ <para>
+ Use parentheses in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To contain the abbreviation of a term on the first
+ occurrence of the full term
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In man page references, specifically the section
+ number
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Period</term>
+ <listitem>
+ <para>
+ Use a period in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To end a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In file and directory names
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In abbreviations that can be mistaken for words, such
+ as a.m. and U.S.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation</term>
+ <listitem>
+ <para>
+ Use standard American English punctuation rules. In
+ addition to the specific points of punctuation in this
+ section, see also the <ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">
+ <citetitle>Chicago Manual of Style</citetitle></ulink>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation in numbers</term>
+ <listitem>
+ <para>
+ Do not use a comma in numerals of four digits. Use a comma
+ in numerals of more than four digits.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Quotation marks</term>
+ <listitem>
+ <para>
+ Use quotation marks to indicate material that is taken
+ verbatim from another source. Do not use quotation marks
+ to excuse terms from legitimacy. If the term is not
+ legitimate, then use another term. If you must use that
+ term, declare the term in the glossary and make the term
+ legitimate.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Semicolon</term>
+ <listitem>
+ <para>
+ Do not use semicolons.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Slash</term>
+ <listitem>
+ <para>
+ Except where required as part of a filename, do not use
+ slashes "/" in your writing. The construction
+ "and/or," for example, does not exist. Use one or the
+ other term instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Spelling</term>
+ <listitem>
+ <para>
+ Use standard American English spelling rules, see the
+ <ulink url="http://www.bartleby.com/61/">
+ <citetitle>American Heritage
+ Dictionary</citetitle></ulink> for guidelines.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Titles</term>
+ <listitem>
+ <para>
+ For manual titles use the same rules as for headings.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Units</term>
+ <listitem>
+ <para>
+ Follow these rules when using units:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use standard abbreviations for units of measurements,
+ do not invent your own abbreviations.
+ </para>
+ </listitem>
+ <listitem>
+ <para> <!-- See <xref linkend="units"/> for a list of
+ units relevant to the GNOME Desktop. --> For further
+ guidelines, see the <citetitle>IEEE Standard
+ Dictionary of Electrical and Electronics
+ Terms</citetitle>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use periods for abbreviated units that might be
+ mistaken for a word.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Most standard abbreviations of units account for both
+ singular and plural usage.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Insert a space between the numeral and the unit of
+ measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+d1589 1
+a1589 1
+ </section>
+d1591 1
+a1591 1
+ <section id="sn-composition-tips">
+d1593 1
+a1593 1
+ <title>Composition Tips</title>
+d1605 9
+d1615 27
+a1641 36
+ This section contains usage tips based on situations the &FDP;
+ editors have encountered in the past. You should read and
+ understand these examples to improve your own documentation. The
+ &FDP; editors welcome additional examples.
+ </para>
+
+ <section id="sn-misc-active-voice">
+ <title>Active Voice</title>
+ <para>
+ Always use active voice, except when it is awkward to do so.
+ The tutorial tells the user how to accomplish a task, and
+ should give instructions clearly and concisely. Avoid using
+ "must," "need to," and the like. These words are redundant in
+ a tutorial, since the reader assumes you are outlining
+ necessary steps to accomplish a task. Also avoid using
+ "should," "might," and other words that indicate you are
+ unsure about the subject matter. Your tutorial should cover a
+ subject authoritatively. The reader should never be concerned
+ about unknown effects of following the tutorial.
+ </para>
+ <example id="ex-misc-passive-voice">
+ <title>Incorrect: Passive voice</title>
+ <para>
+ The <command>yum update</command> command must be run.
+ </para>
+ <para>
+ You should run the <command>yum update</command> command.
+ </para>
+ </example>
+ <example id="ex-misc-active-voice">
+ <title>Correct: Active voice</title>
+ <para>
+ Run the <command>yum update</command> command.
+ </para>
+ </example>
+ </section>
+d1643 3
+a1645 3
+ <section id="sn-present-tense">
+ <title>Present Tense</title>
+ <para>
+d1647 4
+a1650 4
+ words "will" and "shall" are almost never needed in describing
+ what the user should do or see. They add unnecessary length to
+ sentences and can confuse translators. They are also often
+ indicators of passive voice; see also
+d1653 17
+a1669 17
+ </para>
+ <example id="ex-misc-future-tense">
+ <title>Incorrect: Future tense</title>
+ <para>
+ The application will display a list of target files.
+ </para>
+ <para>
+ A list of target files will be displayed by the application.
+ </para>
+ </example>
+ <example id="ex-misc-present-tense">
+ <title>Correct: Present tense</title>
+ <para>
+ The application displays a list of target files.
+ </para>
+ </example>
+ </section>
+d1671 34
+a1704 35
+ <section id="sn-narrative-voice">
+ <title>Narrative Voice</title>
+ <para>
+ Do not use the first person "I," "we," or "us" to refer to
+ yourself the writer (whether including the reader or not), the
+ &FDP;, the &FED; community, or any other group. Do not refer
+ to users with a third person pronoun ("he," "she," or "he or
+ she") or the word "one." It is acceptable to refer to the
+ reader with the second person pronoun "you."
+ </para>
+ <example id="ex-misc-wrong-person">
+ <title>Incorrect: First or third person</title>
+ <para>
+ As described in the last section, I always run
+ <command>up2date</command> before configuring the Samba
+ server.
+ </para>
+ <para>
+ If the user needs to back up his or her files, s/he should
+ use the <command>tar</command> or <command>cpio</command>
+ command.
+ </para>
+ </example>
+ <example id="ex-misc-correct-person">
+ <title>Correct: Second (or no) person</title>
+ <para>
+ Refer to the section on <command>up2date</command> before
+ configuring the Samba server.
+ </para>
+ <para>
+ Users can back up files with the <command>tar</command> or
+ <command>cpio</command> command.
+ </para>
+ </example>
+ </section>
+d1706 8
+a1713 8
+ <section id="sn-misc-negative">
+ <title>Negative Words</title>
+ <para>
+ Avoid negative words when possible, since they give
+ documentation an overly dogmatic tone. The word "avoid" is
+ useful for this purpose. Note that contractions are often
+ used for negative words such as <emphasis>don't</emphasis> or
+ <emphasis>can't</emphasis>. See <xref
+d1715 2
+a1716 2
+ </para>
+ </section>
+d1718 12
+a1729 13
+ <section id="sn-misc-uncertainty">
+ <title>Uncertainty</title>
+ <para>
+ Avoid overuse of "typically," "usually," "most of," "many,"
+ and the like. While occasional use of these constructions is
+ acceptable, overuse reduces the authority of your
+ documentation. The documentation should adequately cover a
+ stock installation of &FC;. It is impossible for a
+ tutorial-length document to cover every possible configuration
+ scenario. Address the most common scenarios and note
+ discrepancies only as required.
+ </para>
+ </section>
+d1731 12
+a1742 12
+ <section id="sn-misc-offtopic">
+ <title>Redundant Coverage</title>
+ <para>
+ Avoid covering redundant material, such as how to update a
+ &FC; system. These overarching topics may be covered in other
+ tutorials. Writers frequently violate this guideline because
+ they feel their tutorial is not long enough. Keep your
+ tutorial from wandering off-topic. Instead, refer the reader
+ to a separate tutorial whenever possible for complete coverage
+ of that topic.
+ </para>
+ </section>
+d1744 16
+a1759 16
+ <section id="sn-misc-importance">
+ <title>Self-referential Value Judgments</title>
+ <para>
+ Avoid statements like "One of the most important things to do
+ is <replaceable>XYZ</replaceable>." If the procedure is
+ important, the reader already expects it to be in your
+ tutorial. The converse is also true: if a procedure appears in
+ your tutorial, the reader expects it is important. This is
+ especially true if you use a whole section for the procedure
+ in question. Merely state, "Do
+ <replaceable>XYZ</replaceable>." Then elaborate as required.
+ If the whole section concerns how to do
+ <replaceable>XYZ</replaceable>, leave this sentence out
+ entirely. See also <xref linkend="vle-golden-rule-4" />.
+ </para>
+ </section>
+d1761 47
+a1807 47
+ <section id="sn-misc-precision">
+ <title>Precision of Language</title>
+ <para>
+ Use precise words for actions users should take. Do not
+ instruct users to "go" to a selection, or "find" a menu.
+ </para>
+ <example id="ex-precision-wrong">
+ <title>Incorrect: Imprecise wording</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Go to the <guimenu>Main Menu</guimenu> ->
+ <guimenuitem>Foobar</guimenuitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Find the option labeled <guilabel>Search</guilabel>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-precision-right">
+ <title>Correct: Precise wording</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ From the <guimenu>Main Menu</guimenu>, select
+ <guimenuitem>Foobar</guimenuitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select the <guilabel>Search</guilabel> option
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <important>
+ <title>Do Not Discriminate Against Non-GUI Users</title>
+ <para>
+ If you are writing about a GUI-only application, you may use
+ "click" freely. If you are writing about an application that
+ has a text-mode interface, use "select" instead as shown
+ above.
+ </para>
+ </important>
+d1809 1
+a1809 1
+ </section>
+d1811 19
+a1829 19
+ <section id="sn-misc-docbook-tips">
+ <title>DocBook Tips</title>
+ <para>
+ This section contains tips on how to use DocBook tags more
+ effectively in your documentation.
+ </para>
+
+ <section id="sn-misc-admonitions">
+ <title>Admonitions</title>
+ <para>
+ Avoid overuse of admonitions. Use only the most important
+ material inside the admonition. Doing so will keep
+ admonitions short and effective. Any background material
+ required to explain the most important admonition statements
+ should be moved outside the admonition.
+ </para>
+ <example id="ex-misc-ineffective-admonition">
+ <title>Incorrect: Lengthy admonition</title>
+ <para>
+d1831 11
+a1841 11
+ <title>Using <command>sfdisk</command></title>
+ <para>
+ The <command>sfdisk</command> command accepts a script
+ file as standard input to set up partitions on a hard
+ disk. Sometimes <command>sfdisk</command> will simply
+ reject an erroneous input file. In other cases, it
+ will use the input verbatim, writing an incorrect
+ partition table to your disk. Always use the
+ <command>sfdisk -n</command> command to check your
+ input file before writing to the disk.
+ </para>
+d1843 10
+a1852 11
+ </para>
+ </example>
+ <example id="ex-misc-good-admonition">
+ <title>Correct: Brief admonition</title>
+ <para>
+ The <command>sfdisk</command> command accepts a script
+ file as standard input to set up partitions on a hard
+ disk. Sometimes <command>sfdisk</command> will simply
+ reject an erroneous input file. In other cases, it will
+ use the input verbatim, writing an incorrect partition
+ table to your disk.
+d1854 5
+a1858 5
+ <title>Using <command>sfdisk</command></title>
+ <para>
+ Always use the <command>sfdisk -n</command> command to
+ check your input file before writing to the disk.
+ </para>
+d1860 26
+a1885 26
+ </para>
+ </example>
+ <para>
+ Avoid punctuation in titles for sections or admonitions,
+ except for commas only where demanded. Use a title that says
+ something about the admonition comment, such as "Reboot
+ required," instead of simply using the admonition type for a
+ title ("Note").
+ </para>
+ </section>
+
+ <section id="sn-misc-replaceable">
+ <title>The <replaceable> Tag</title>
+ <para>
+ If your documentation formally states a specific value will
+ be used as a convention, do not use the <replaceable>
+ tag in your text or examples.
+ </para>
+ </section>
+
+ <section id="sn-misc-entities">
+ <title>XML Entities</title>
+ <para>
+ Use the entities provided by the &FDP;. These entities are
+ found in the <filename>common/</filename> folder in the
+ <filename>fedora-docs</filename> distribution. (See also
+d1888 5
+a1892 5
+ abbreviations such as "FC2." Instead, use the predefined
+ entities "&FC; &FCVER;," which produces the text
+ "&FC; &FCVER;."
+ </para>
+ </section>
+d1894 1
+a1894 1
+ </section>
+d1896 1
+a1896 1
+ </section>
+d1898 7
+a1904 1
+ </chapter>
+@
+
diff --git a/old-documentation-guide/Attic/docs-style-zh_CN.xml,v b/old-documentation-guide/Attic/docs-style-zh_CN.xml,v
new file mode 100644
index 0000000..6ba69b7
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-style-zh_CN.xml,v
@@ -0,0 +1,1084 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id: --><chapter id="ch-style">
+ <title>写作风格</title>
+ <para>撰写完善的技术文档不仅仅指展示命令行和指令集。好文档应当容易阅读、理解、翻译，表达准确的概念间的逻辑关系。好文档也可以用 <emphasis>不应当做的</emphasis> 事情来定义。您的文档应当避免：</para>
+ <itemizedlist>
+ <listitem>
+ <para>冗长</para>
+ </listitem>
+ <listitem>
+ <para>多余的，不加解释的行话</para>
+ </listitem>
+ <listitem>
+ <para>语法或拼写错误</para>
+ </listitem>
+ <listitem>
+ <para>对个人经历的引证</para>
+ </listitem>
+ <listitem>
+ <para>可能触犯或迷惑用户的评论</para>
+ </listitem>
+ </itemizedlist>
+ <para>这一章包含了 &FED; 文档写作风格的规则和准则。准则与规则不同，即使违反了准则，如果您的文章更加易于理解，那么没有关系。尽量遵循准则，总是遵循规则。如果没有明确表明，一个建议就是一个准则。</para>
+ <section id="sn-intro-to-style">
+ <title>为何写作风格很重要</title>
+ <para>优秀的写作不是天生的。它是一种技术，即使专业的作者，甚至有名的作家，也必须时常练习。 <firstterm>写作风格</firstterm><indexterm><primary>style</primary></indexterm> 是将优秀的作品与平直的描述区分开的特性。</para>
+ <para>优秀的作品有多种形式。对于诗歌和散文，优秀的作品不会遵循一定的语法、句法或拼写规则。一个著名的例子是 James Joyce 的小说 <citetitle>Ulysses</citetitle> 中的 Episode 18, "Penelope," <footnote id="fn-ulysses"><para><ulink url="http://www.online-literature.com/james_joyce/ulysses/18/">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>。请注意这个例子包含一些成人内容，因此不适于所有用户。</para></footnote>。那里，Joyce 使用长串的词汇，不加标点，来摹拟角色的内心意识。虽然违反了语法和句法的基本规则，Joyce 描绘了叙述者无组织却又松散联系的思考方式。</para>
+ <para>技术文档却必须遵循这些规则。文档与标准语法偏差越大，读者就会觉得越难理解。例如，读者也许并不以文档语言为母语，或者正在阅读译本。这时，如果作者使用方言、习语或者行话，读者和译者会很容易被迷惑。下面的例子比较了表达同样含义的不同做法：</para>
+ <example>
+ <title>不正确的风格</title>
+ <!-- I prefer "incorrect," because I think terms such as
+ "problematic" are mealy-mouthed. They remind me of the late
+ 1980's English textbook trend toward the politically correct yet
+ wholly unhelpful "standard/nonstandard." But then, I tend to be
+ dogmatic; it's probably my Catholic upbringing. [PWF] -->
+ <para>So you made the changes I showed you in the last section. What's the next thing you should do? Just pop your thumb drive onto your system and read the <filename>messages</filename> log. When you see "USB device found," then Bob's your uncle.</para>
+ </example>
+ <example>
+ <title>正确的风格</title>
+ <!-- I prefer "correct." See above. [PWF] -->
+ <para>After you complete the configuration changes above, attach the USB removable media to your system. Use the <command>dmesg</command> command to examine the kernel message log. The message <computeroutput>USB device
+ found</computeroutput> indicates that your device was installed successfully.</para>
+ </example>
+ <para>第一个例子是更口语化的英语，它不适于正式的文档。第二个例子更加正式，但是无论是对英语用户还是译者，它都更容易理解。</para>
+ <para>遵守写作风格规则和准则，可以使读者阅读大量文档时更轻松。一致的风格有助于增强文档的专业性和价值认同。另一方面，忽略标点或语法错误将使读者对文档产生抵触。读者会认为基本正确的一篇文档不够权威，因为它写得很差。读者不必为理解作者的语言而头疼时才会放松下来。</para>
+ <para>这一章不可能包含足够的内容，使每个读过的人变成一个好作者。一些专门讲述写作风格的手册可能会有几百页。这一章为中级作者理解技术文档的写作风格提供了足够的准则。</para>
+ <para>如果您不是有经验的作者，无论技术文档还是其他，您还可以从其他资源中学到很多。下面的列表仍不够完善，但是提供了一个起点：</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <citetitle>The Elements of Style</citetitle>, 作者 William Strunk. 在线阅读: <ulink url="http://bartleby.com/141/">http://bartleby.com/141/</ulink></para>
+ </listitem>
+ <!-- placeholder for when it's ready
+ <para>
+ <citetitle>The Elements of Style</citetitle>, by William
+ Strunk. Fedora Docs Project version: <ulink
+ url="http://fedora.redhat.com/docs/eos-guide-en/">http://fedora.redhat.com/docs/eos-guide-en/</ulink>
+ </para>
+-->
+ <listitem>
+ <para>
+ <citetitle>The Chicago Manual of Style</citetitle>, 作者 the University of Chicago Press. 在线阅读: <ulink url="http://www.chicagomanualofstyle.org/">http://www.chicagomanualofstyle.org/</ulink></para>
+ </listitem>
+ <listitem>
+ <para>
+ <citetitle>Paradigm Online Writing Assistant</citetitle>, 维护者 Chuck Guilford, Ph.D. 在线阅读: <ulink url="http://www.powa.org/">http://www.powa.org/</ulink></para>
+ </listitem>
+ </itemizedlist>
+ <para>很多自由软件的文档计划有自己的文档风格准则。实际上，这一章很多内容来自 <citetitle>GNOME Documentation Style Guidelines</citetitle> (<firstterm>GDSG</firstterm>)。您可以看到本来的 <citetitle>GDSG</citetitle>，位置是 <ulink url="http://developer.gnome.org/documents/style-guide/">http://developer.gnome.org/documents/style-guide/</ulink>。</para>
+ </section>
+ <section id="sn-tech-docs-fundamentals">
+ <title>技术文档的基本概念</title>
+ <note>
+ <title>参考书目信息</title>
+ <para>这一节来自 <citetitle>GDSG</citetitle>。</para>
+ </note>
+ <!-- This section will reproduce mostly what is in Chapter 1 of
+ the GDSG. There may be minor changes. FIXME: Make sure the
+ appropriate front matter of the Documentation Guide includes
+ attribution as required by the GNU FDL. -->
+ <para>这一章提供了写作技术文档的简要介绍。</para>
+ <section id="sn-fundamentals-1">
+ <title>写作风格一般要求</title>
+ <para>&FP; 技术文档写作在一般要求的基础上，有特殊的约束。好的 &FED; 技术文档应当有下列特点：</para>
+ <variablelist>
+ <varlistentry>
+ <term>完备</term>
+ <listitem>
+ <para>描述一个产品的全部功能。不可忽略个人认为对用户没有用处的功能。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>一致</term>
+ <!-- I'm having issues with the
+ sketchy definition of this non-dictionary word and the
+ associated text. Not wrong, per se, just wishing for
+ something better. This note shall remind us! - kwade -->
+ <!-- Hopefully this change helps. Makes sense according to the
+ gdict tool in Core, at least. - PWF -->
+ <listitem>
+ <para>描述看到的内容。不要描述想要看到的内容。将信息以用户切身经历的顺序表达出来。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>清楚</term>
+ <listitem>
+ <para>阅读 <citetitle>The Elements of Style</citetitle> (<ulink url="http://www.bartleby.com/141/">http://www.bartleby.com/141/</ulink>) 来撰写清楚的文档。</para>
+
+<!-- placeholder for when this is published:
+ <para>
+ Read <citetitle>The Elements of Style</citetitle>
+ &FED;-version (<ulink
+ url="http://fedora.redhat.com/docs/eos-guide-en/">http://fedora.redhat.com/docs/eos-guide-en/</ulink>)
+ to help make your writing clear.
+ </para>
+-->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>连贯</term>
+ <listitem>
+ <para>在文档中使用约定俗成的词汇。如果其他作者在撰写相关的文档，那么使用相同的词汇。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>简明</term>
+ <listitem>
+ <para>写作时多检视作品，问问自己哪些可以删减。请参考 <xref linkend="sn-fundamentals-2"/>。</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-2">
+ <title>原则</title>
+ <para>这一节包含了一些基本的风格准则。本章的后续小节将展开详述这些准则。</para>
+ <variablelist>
+ <varlistentry>
+ <term>原则一：简短</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>将每句话限制到 25 个词以下。</para>
+ </listitem>
+ <listitem>
+ <para>将每步过程限制到 23 个词以下。</para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-1-wrong">
+ <title>不正确：过长</title>
+ <para>Under normal operating conditions, the kernel does not always immediately write file data to the disks, storing it in a memory buffer and then periodically writing to the disks to speed up operations.</para>
+ </example>
+ <example id="ex-golden-rule-1-right">
+ <title>正确：短句</title>
+ <para>Normally, the kernel stores the data in memory prior to periodically writing the data to the disk.</para>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>原则二：有条理</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>每段讲述一个主题。</para>
+ </listitem>
+ <listitem>
+ <para>每句话表达一个意思。</para>
+ </listitem>
+ <listitem>
+ <para>每步操作只包含一个动作。</para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-2-wrong">
+ <title>不正确：没有条理</title>
+ <para>The <application>Workspace Switcher</application> applet helps you navigate all of the virtual desktops available on your system. The X Window system, working in hand with a piece of software called a <emphasis>window manager</emphasis>, allows you to create more than one virtual desktop, known as <emphasis>workspaces</emphasis>, to organize your work, with different applications running in each workspace. The <application>Workspace Switcher</application> applet is a navigational tool to get around the various workspaces, providing a miniature road map in the GNOME panel showing all your workspaces and allowing you to switch easily between them.</para>
+ </example>
+ <example id="ex-golden-rule-2-right">
+ <title>正确：有条理</title>
+ <para>Use the <application>Workspace Switcher</application> to add new <emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different applications in each workspace. The <application>Workspace Switcher</application> applet provides a miniature map that shows all of your workspaces. You can use the <application>Workspace Switcher</application> applet to switch between workspaces.</para>
+ </example>
+ <tip>
+ <para>在撰写前规划段落的顺序。决定在每段应当涵盖的主题。</para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>原则三：使用指示</term>
+ <listitem>
+ <para>使用例子来演示如何操作。提供指示，而不是描述。</para>
+ <example id="ex-golden-rule-3-wrong">
+ <title>不正确：描述而不指示</title>
+ <para>There is a text box that you can use to find out the definition of a word.</para>
+ </example>
+ <example id="ex-golden-rule-3-right">
+ <title>正确：指示用法</title>
+ <para>To request a definition of a word, type the word in the text box, then select <guilabel>Lookup</guilabel>.</para>
+ </example>
+ <tip>
+ <para>不要过于教条。有时您需要解释，以说明那些范例。</para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-golden-rule-4">
+ <term>原则四：客观</term>
+ <listitem>
+ <para>以中立的语气写作。</para>
+ <example id="ex-golden-rule-4-wrong">
+ <title>不正确：偏倚一方</title>
+ <para>The applet is a handy little screen grabber.</para>
+ </example>
+ <example id="ex-golden-rule-4-right">
+ <title>正确：客观陈述</title>
+ <para>Use the applet to take screenshots.</para>
+ </example>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-3">
+ <title>语气</title>
+ <para>不合适的语气会妨碍读者获取信息。中立的，不带个人好恶选择的语气可以促进读者的理解。中立的语气使较大的文档项目中的作者可以并行写作。另外，新的作者可以随时加入。中立的语气可以在系列文档之间实现一致，便于用户获得信息。要达到共同的中立的语气，最好的办法是采用下列原则：</para>
+ <variablelist>
+ <varlistentry>
+ <term>避免幽默</term>
+ <listitem>
+ <para>幽默使注意力从您的信息中移开。幽默也使文档难以翻译。保持直白。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>避免个人好恶选择</term>
+ <listitem>
+ <para>无论您认为某个功能是否好坏都不重要。将功能展示给用户，包含如何使用这些功能的指示。保持准确。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>避免口语</term>
+ <listitem>
+ <para>口语难以翻译，通常是与文化相关的。保持中立。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>避免一时的论断</term>
+ <listitem>
+ <para>一个论断在今天被认同，在明天就可能被推翻。保持技术化。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>避免展望将来</term>
+ <listitem>
+ <para>关于某个产品的将来，这不属于技术文档。只撰写您现在看到的东西。要实际。</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-4">
+ <title>面向正确的用户</title>
+ <para>您对文档的结构和内容的定夺应当基于对读者的理解。考虑读者如何获取文档，需要哪些信息，曾经的经验等等。通常，您需要创建适合不同群体的文档。下面几节包含了您需要考虑的与读者相关的主题。</para>
+ </section>
+ <section id="sn-fundamentals-6">
+ <title>用户的动机</title>
+ <para>不要浪费想在文档中获取信息的读者的时间。用户阅读技术文档不是为了取乐。用户通常带有特定的问题。您需要对这些问题作出明确的回答。</para>
+ </section>
+ <section id="sn-fundamentals-7">
+ <title>新用户</title>
+ <para>&FC; 的新用户遇到不熟悉的应用程序或功能时，通常会查阅在线教程。每个教程应当包含足够的介绍信息，告诉新用户如何使用相关的功能。每个教程还应当包含足够的使用说明，告诉用户他们可以用这个命令或功能作出的种种动作。使这些说明面向任务。在教程中不要描述 GUI 屏幕、对话框和对话框元素，除非某个特性影响了您的说明。</para>
+ </section>
+ <section id="sn-fundamentals-8">
+ <title>有经验的用户</title>
+ <para>有经验的用户通常将文档作为参考。文档需要完备，组织合理，如果是打印的方式，还需要索引。</para>
+ </section>
+ <section id="sn-fundamentals-9">
+ <title>不要触犯读者</title>
+ <para>为避免触犯读者，文档应遵循下列准则：</para>
+ <variablelist>
+ <varlistentry>
+ <term>避免内部用语</term>
+ <listitem>
+ <para>内部用语包括行话和计算机社群中常见的缩写风气。例如，使用<literal>docs</literal> 而不是 <literal>documentation</literal>。一个词如果满足下面的条件，就是一句行话：</para>
+ <itemizedlist>
+ <listitem>
+ <para>这个词没有包含在 <citetitle>&FED; Jargon Buster</citetitle> (<ulink url="http://fedora.redhat.com/docs/jargon-buster/">http://fedora.redhat.com/docs/jargon-buster/</ulink>) 中。</para>
+ </listitem>
+ <listitem>
+ <para>这个词没有包含在 <citetitle>American Heritage Dictionary</citetitle> (<ulink url="http://www.bartleby.com/61/">http://www.bartleby.com/61/ </ulink>) 中。</para>
+ </listitem>
+ <listitem>
+ <para>这个词没有出现在您撰写的文档的词汇表中。</para>
+ </listitem>
+ <listitem>
+ <para>这个词也没有在您撰写的文档中定义。</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>避免性别相关的语言</term>
+ <listitem>
+ <para>不要出现代词 <literal>他的/她的</literal> 或 <literal>他/她</literal>。在指令中不必区分性别。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>避免特定文化的语言</term>
+ <listitem>
+ <para>如果您的范例只能让您周围方圆百里的人看懂，那么它没有意义。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>不要用高人一等的口气</term>
+ <listitem>
+ <para>如果文档中说，一个动作很容易或很快，而实际上用户无法完成，那没有比这更能让读者郁闷的了。不要评价和判断动作。</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>准则的其他部分是对可能造成触犯的语气和语言用法的详细说明。</para>
+ </section>
+ </section>
+ <section id="sn-grammar-and-usage">
+ <title>语法和用法准则</title>
+ <note>
+ <title>参考书目信息</title>
+ <para>这一节部分来自 <citetitle>GDSG</citetitle>，部分来自 <citetitle>The Elements of Style</citetitle>，为二十一世纪的技术文档作者进行了更新。</para>
+ </note>
+ <!-- FIXME: Again, check attribution viz. GNU FDL. This will be more work
+ than the previous section. -->
+ <para>这一节包含了字母序排列的语法和用法准则，用于 &FED; 文档。很多准则只适用于英语，请参考 <citetitle>American Heritage Dictionary</citetitle> (<ulink url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>) 和 <citetitle>Chicago Manual of Style</citetitle> (<ulink url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>)。</para>
+ <variablelist>
+ <varlistentry>
+ <term>缩写</term>
+ <listitem>
+ <para>词或短语的简写形式，可以代替原来的词使用，例如 <literal>Dr.</literal>, <literal>a.m.</literal>, <literal>p.m.</literal> 等等。在使用缩写时，遵循下列规则：</para>
+ <itemizedlist>
+ <listitem>
+ <para>避免创造新的缩写。不熟悉的缩写造成混淆，无法表明一个概念。</para>
+ </listitem>
+ <listitem>
+ <para>不要解释或展开众所周知的缩写。</para>
+ </listitem>
+ <listitem>
+ <para>不要在文档的词汇表中包含众所周知的缩写。</para>
+ </listitem>
+ </itemizedlist>
+ <para>对于短语的缩写，例如 <literal>i.e.</literal> ("in other words", 换句话说) 和 <literal>e.g.</literal> ("for example", 例如)，不要使用缩写。拼写出整个短语。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>形容词</term>
+ <listitem>
+ <para>小心使用形容词。在必须使用形容词来区分对象时再用。无论合适，检查是否可以把形容词去掉。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>首字母组合词</term>
+ <listitem>
+ <para>用来表达一个由多个词组成的概念。通常，首字母组合词是这样构造的：</para>
+ <itemizedlist>
+ <listitem>
+ <para>From the first letters of each word in a compound term, for example Table of Contents (TOC).</para>
+ </listitem>
+ <listitem>
+ <para>From recognizable parts of a compound term, such as GNU Object Model Environment (GNOME).</para>
+ </listitem>
+ </itemizedlist>
+ <para>在使用首字母组合词的时候，遵循下列规则：</para>
+ <itemizedlist>
+ <listitem>
+ <para>在第一次使用时，拼写完整的名称，在括号中包含组合词。</para>
+ </listitem>
+ <listitem>
+ <para>不要拼写出众所周知的首字母组合，除非您认为这对读者有用。</para>
+ </listitem>
+ <listitem>
+ <para>不要创建新的首字母组合。不熟悉的组合将造成混淆，无法表达清楚。</para>
+ </listitem>
+ <listitem>
+ <para>用大写表示，除非必须用小写。</para>
+ </listitem>
+ <listitem>
+ <para>在文档的词汇表中包含首字母组合和全称。</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>副词</term>
+ <listitem>
+ <para>小心使用副词。在必须用副词修饰组件的功能时再用。无论合适，检测是否可以去掉副词。经典的冗余副词包括 <literal>容易地</literal>，<literal>简单地</literal> 和 <literal>迅速地</literal>。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>拟人</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>不要让应用程序软件充满情绪、欲望或意见。</para>
+ </listitem>
+ <listitem>
+ <para>不要让应用程序软件产生位置、维度的感觉。用户不会 "处在" 一个文本编辑器里。</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>冠词</term>
+ <listitem>
+ <para>不要在下列对象前面使用定冠词 <literal>the</literal>：</para>
+ <itemizedlist>
+ <listitem>
+ <para>文章标题</para>
+ </listitem>
+ <listitem>
+ <para>段的标题</para>
+ </listitem>
+ <listitem>
+ <para>标题</para>
+ </listitem>
+ <listitem>
+ <para>图象说明</para>
+ </listitem>
+ <listitem>
+ <para>表格说明</para>
+ </listitem>
+ <listitem>
+ <para>列表</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>撇号</term>
+ <listitem>
+ <para>尽可能不要使用撇号</para>
+ <itemizedlist>
+ <listitem>
+ <para>不要用撇号来表达从属和拥有的关系</para>
+ </listitem>
+ <listitem>
+ <para>不要用撇号来表达缩写</para>
+ </listitem>
+ <listitem>
+ <para>不要用撇号来表达复数</para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-apostrophe-wrong">
+ <title>不正确的撇号</title>
+ <itemizedlist>
+ <listitem>
+ <para>the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option</para>
+ </listitem>
+ <listitem>
+ <para>don't use the default option</para>
+ </listitem>
+ <listitem>
+ <para>several SCSI disk's</para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-apostrophe-right">
+ <title>正确：不使用撇号</title>
+ <itemizedlist>
+ <listitem>
+ <para>the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</guimenu></para>
+ </listitem>
+ <listitem>
+ <para>do not use the default option</para>
+ </listitem>
+ <listitem>
+ <para>several SCSI disks</para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>方括号</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>不要使用方括号 [就像这样] 替换圆括号 (就像这样)</para>
+ </listitem>
+ <listitem>
+ <para>使用方括号表达可选的命令行参数</para>
+ </listitem>
+ <listitem>
+ <para>不要使用尖括号表达文本中的变量，应使用 <sgmltag class="starttag">replaceable</sgmltag> 标记。标记用法请参考 <xref linkend="s1-xml-tags-replaceable"/>。</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>大写</term>
+ <listitem>
+ <para>下列情况下大写：</para>
+ <itemizedlist>
+ <listitem>
+ <para>首字母缩写中的所有字母，除非是众所周知的特例</para>
+ </listitem>
+ <listitem>
+ <para>列表中第一个词的第一个字母</para>
+ </listitem>
+ <listitem>
+ <para>顺序列表中第一个词的第一个字母</para>
+ </listitem>
+ <listitem>
+ <para>按键名称的第一个字母，例如 <keycap>Shift</keycap></para>
+ </listitem>
+ <listitem>
+ <para>句子的第一个字母</para>
+ <note>
+ <title>命令名</title>
+ <para>避免在句首使用命令名或应用程序名称，如果它们的首字母是小写的话。</para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>冒号后面完整句子的首字母</para>
+ </listitem>
+ </itemizedlist>
+ <para>下列情况下不要大写：</para>
+ <itemizedlist>
+ <listitem>
+ <para>组合的名词，后面是缩写或首字母组合</para>
+ </listitem>
+ <listitem>
+ <para>如果要强调一些内容</para>
+ </listitem>
+ <listitem>
+ <para>变量名</para>
+ </listitem>
+ <listitem>
+ <para>冒号后面，不完整句子的首字母</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>标题</term>
+ <listitem>
+ <para>对于标题，以及图象和表格的说明，使用相同的规则。不要在标题最后加上句号。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>冒号</term>
+ <listitem>
+ <para>在下列情况下，使用冒号：</para>
+ <itemizedlist>
+ <listitem>
+ <para>引入列表</para>
+ </listitem>
+ <listitem>
+ <para>在解释的前面</para>
+ </listitem>
+ <listitem>
+ <para>在介绍之后</para>
+ </listitem>
+ </itemizedlist>
+ <para>下列情况下，不要使用冒号：</para>
+ <itemizedlist>
+ <listitem>
+ <para>要引入图象或表格</para>
+ </listitem>
+ <listitem>
+ <para>介绍标题</para>
+ </listitem>
+ <listitem>
+ <para>介绍一个过程之后</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>表栏标题</term>
+ <listitem>
+ <para>使用与标题相同的规则</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>逗号</term>
+ <listitem>
+ <para>下列情况下，使用逗号：</para>
+ <itemizedlist>
+ <listitem>
+ <para>区分系列中的对象</para>
+ </listitem>
+ <listitem>
+ <para>区分句子的部分</para>
+ </listitem>
+ <listitem>
+ <para>区分非限制性的短语</para>
+ </listitem>
+ <listitem>
+ <para>与破折号类似，表达同位语</para>
+ </listitem>
+ <listitem>
+ <para>在 <emphasis>例如，</emphasis> 和类似的表达中</para>
+ </listitem>
+ </itemizedlist>
+ <para>下列情况下，不要使用逗号：</para>
+ <itemizedlist>
+ <listitem>
+ <para>一系列形容词修饰一个对象时</para>
+ </listitem>
+ <listitem>
+ <para>两个短的独立子句间</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>命令</term>
+ <listitem>
+ <para>不要将命令作为动词。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-contractions">
+ <term>缩写</term>
+ <listitem>
+ <para>不要使用缩写，类似 <emphasis>can't</emphasis>, <emphasis>don't</emphasis>, 或 <emphasis>isn't</emphasis>。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>破折号</term>
+ <listitem>
+ <para>不要使用破折号或连接号。使用分段或冒号，如果是介绍性文字的话。如果有很多内容要介绍，那么使用一个列表。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>省略号</term>
+ <listitem>
+ <para>下列情况下，使用省略号：</para>
+ <itemizedlist>
+ <listitem>
+ <para>要表示忽略了句子的一部分</para>
+ </listitem>
+ <listitem>
+ <para>要表示引用文本的间断</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>分数</term>
+ <listitem>
+ <para>使用分数时，遵循这些规则：</para>
+ <itemizedlist>
+ <listitem>
+ <para>在表格中，以及度量单位中，使用分数的数字形式，在正文中使用文本形式。</para>
+ </listitem>
+ <listitem>
+ <para>数字和相连的分数间添加空格，以防混淆。例如：1 1/2 而不是 11/2。</para>
+ </listitem>
+ <listitem>
+ <para>如果分数用作复合的修饰，在分数和度量单位间添加连字符。</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>性别</term>
+ <listitem>
+ <para>请参考 <xref linkend="sn-fundamentals-9"/>。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>语法</term>
+ <listitem>
+ <para>标准的英语语法规则，请参考 <citetitle>Chicago Manual of Style</citetitle> (<ulink url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html"> http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>)。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>标题</term>
+ <listitem>
+ <para>在标题中使用下面的大写规则：</para>
+ <itemizedlist>
+ <listitem>
+ <para>第一个词的首字母大写</para>
+ </listitem>
+ <listitem>
+ <para>名词，形容词和动词的首字母大写</para>
+ </listitem>
+ <listitem>
+ <para>连词，冠词和少于四个字母的介词都应小写</para>
+ </listitem>
+ <listitem>
+ <para>四个字母的介词或更多时首字母大写</para>
+ </listitem>
+ <listitem>
+ <para>四个字母的连词或更多时大写</para>
+ </listitem>
+ </itemizedlist>
+
+ <!-- <para> See <xref linkend="infodesign-2"/> for more
+ information about headings. </para> -->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>连字符</term>
+ <listitem>
+ <para>下列情况下，使用连字符：</para>
+ <itemizedlist>
+ <listitem>
+ <para>组合修饰中的数字</para>
+ </listitem>
+ <listitem>
+ <para>避免混淆</para>
+ </listitem>
+ <listitem>
+ <para>在标准的前缀和后缀中。请参考 <citetitle>American Heritage Dictionary</citetitle> (<ulink url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)。</para>
+ </listitem>
+ <listitem>
+ <para>在拼写的分数中</para>
+ </listitem>
+ <listitem>
+ <para>在由两个或多个单词构成的变量名中，类似 <replaceable>directory-name</replaceable>。注意： <replaceable>filename</replaceable> 是特例。</para>
+ </listitem>
+ </itemizedlist>
+ <para>下列情况下，不要使用连字符：</para>
+ <itemizedlist>
+ <listitem>
+ <para>对于行话</para>
+ </listitem>
+ <listitem>
+ <para>对于动词</para>
+ </listitem>
+ <listitem>
+ <para>以 <emphasis>ly</emphasis> 结尾的副词</para>
+ </listitem>
+ <listitem>
+ <para>数字作为单一修饰时</para>
+ </listitem>
+ <listitem>
+ <para>
+ <citetitle>American Heritage Dictionary</citetitle> (<ulink url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>) 列为不需连字符的单词，以及有共同前缀的词</para>
+ </listitem>
+ <listitem>
+ <para>商标</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>拉丁文名称</term>
+ <listitem>
+ <para>不要使用拉丁文名称。使用相应的英文名称。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>像</term>
+ <listitem>
+ <para>不要使用 <emphasis>像</emphasis> 来表达等价或相似。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>列表</term>
+ <listitem>
+ <para>使用以冒号结尾的完整的句子引入列表。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>数字</term>
+ <listitem>
+ <para>下列情况下，拼写出数字：</para>
+ <itemizedlist>
+ <listitem>
+ <para>从 0 到 9 的数字，除非数字是测度的一部分</para>
+ </listitem>
+ <listitem>
+ <para>估计</para>
+ </listitem>
+ <listitem>
+ <para>极端情况，类似 <emphasis>百万</emphasis>，但要在前面加上一个数字。</para>
+ </listitem>
+ <listitem>
+ <para>出现在句子开头的数字</para>
+ </listitem>
+ <listitem>
+ <para>后面紧接一个数的数字。例如：<literal>两个 10 MB 的文件</literal></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>数字形式</term>
+ <listitem>
+ <para>下列情况下，使用数字：</para>
+ <itemizedlist>
+ <listitem>
+ <para>数字 10 或更大</para>
+ </listitem>
+ <listitem>
+ <para>负数</para>
+ </listitem>
+ <listitem>
+ <para>大多数分数</para>
+ </listitem>
+ <listitem>
+ <para>百分数</para>
+ </listitem>
+ <listitem>
+ <para>小数</para>
+ </listitem>
+ <listitem>
+ <para>测度</para>
+ </listitem>
+ <listitem>
+ <para>小于一秒的时间单位</para>
+ </listitem>
+ <listitem>
+ <para>对位和字节的引用</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>圆括号</term>
+ <listitem>
+ <para>下列情况下，使用圆括号：</para>
+ <itemizedlist>
+ <listitem>
+ <para>要包含第一次出现的名称的缩写</para>
+ </listitem>
+ <listitem>
+ <para>在手册页的引用中，指明章节号</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>句点</term>
+ <listitem>
+ <para>下列情况下，使用句号：</para>
+ <itemizedlist>
+ <listitem>
+ <para>结束句子</para>
+ </listitem>
+ <listitem>
+ <para>文件和目录名中</para>
+ </listitem>
+ <listitem>
+ <para>可能被误认为单词的缩写中，类似 a.m. 和 U.S.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>标点</term>
+ <listitem>
+ <para>使用标准的英语标点规则。请参考 <citetitle>Chicago Manual of Style</citetitle> (<ulink url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>)。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>数字中的标点</term>
+ <listitem>
+ <para>不要在四位的数字中使用逗号。如果超过四位，那么使用逗号。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>引号</term>
+ <listitem>
+ <para>使用引号来表示内容是不变地从其他来源复制的。不要使用引号来区分不合适的用词。如果用词不合适，换一个别的。如果必须用这个词，就在词汇表中解释它，使这种用法变得合理。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>See v. Refer to</term>
+ <listitem>
+ <para>向用户提供参考资源时，使用 "refer to" 而不是 "see"，使用 "refer also to" 而不是 "see also"。这样可以与索引用到的 <sgmltag class="starttag">see</sgmltag> 和 <sgmltag class="starttag">seealso</sgmltag> 标记区分开。 这些标记用于在索引中创建特殊的链接。为了在文档中保持一致，我们保留关键字 "see" 和 "see also" 用作超链接的索引引用，使用 "refer to" 和 "refer also to" 表达非超链接的，非索引的引用。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>分号</term>
+ <listitem>
+ <para>不要使用分号。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>斜线</term>
+ <listitem>
+ <para>除了用作文件名的一部分之外，不要使用斜线 "/"。不能包含 <literal>and/or</literal> 这样的内容，应该换成其中任何一个。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>拼写</term>
+ <listitem>
+ <para>使用标准的英语拼写规则，请参考 <citetitle>American Heritage Dictionary</citetitle> (<ulink url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>书名</term>
+ <listitem>
+ <para>对于文档的名称，使用与标题相同的规则。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>单位</term>
+ <listitem>
+ <para>使用单位时，遵循下列规则：</para>
+ <itemizedlist>
+ <listitem>
+ <para>使用标准的单位缩写，不要自行创造缩写。</para>
+ </listitem>
+ <listitem>
+ <para>请参考 <citetitle>IEEE Standard Dictionary of Electrical and Electronics Terms</citetitle>。</para>
+ </listitem>
+ <listitem>
+ <para>在缩写的可能被误解为单词的单位中使用句点。</para>
+ </listitem>
+ <listitem>
+ <para>大多数标准的缩写单位都同时适于单数和复数。</para>
+ </listitem>
+ <listitem>
+ <para>在数字和单位之间加上空格。</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-composition-tips">
+ <title>行文技巧</title>
+ <!--
+
+ This section will collect miscellanea and advice for specific
+ situations that the FDP editors encounter. I hope they will feel
+ free to e-mail me sticky situations or particularly interesting
+ examples of work they've beautified. Hopefully not too much will be
+ drawn from my own work! - PWF.
+
+-->
+ <para>本节包含了一些技巧提示，来自 &FDP; 作者们曾遇到的情况。您应理解运用它们，来改善自己的文档。&FDP; 作者乐于接受新的范例。</para>
+ <section id="sn-misc-active-voice">
+ <title>主动语态</title>
+ <para>总是使用主动语态，除非这样很别扭。文档告诉用户如何完成一项任务，应当给出清楚简明的指令。避免使用"必须", "需要"之类的词。这些词在文档中是多余的，因为读者期望看到您给出必要的步骤来完成任务。同样，避免使用"可能," "也许"等等，表示您对问题不很确定的词。您的文档应当权威地描述一个主题。读者不应担心按照文档做会有莫名奇妙的效果。</para>
+ <example id="ex-misc-passive-voice">
+ <title>不正确：被动语态</title>
+ <para>命令 <command>yum update</command> 必须被运行。</para>
+ <para>您也许想运行 <command>yum update</command> 命令。</para>
+ </example>
+ <example id="ex-misc-active-voice">
+ <title>正确：主动语态</title>
+ <para>运行 <command>yum update</command> 命令。</para>
+ </example>
+ </section>
+ <section id="sn-present-tense">
+ <title>一般现在时态</title>
+ <para>以一般现在时态写作。最好的经验，是不需用 "将要" 来描述用户将要做或看到的内容。它们没有意义，并可能混淆翻译者。它们也通常与被动语态有关，请参考 <xref linkend="sn-misc-active-voice"/>。</para>
+ <example id="ex-misc-future-tense">
+ <title>不正确：将来时态</title>
+ <para>应用程序将要显示目标文件的列表。</para>
+ <para>目标文件的列表将要被应用程序显示出来。</para>
+ </example>
+ <example id="ex-misc-present-tense">
+ <title>正确：一般现在时态</title>
+ <para>应用程序显示目标文件的列表。</para>
+ </example>
+ </section>
+ <section id="sn-narrative-voice">
+ <title>叙述的语气</title>
+ <para>不要用第一人称"我" "我们" 来引用作者自己 (无论是否包含读者)，&FDP;，&FED; 社群或任何群体。不要用第三人称指代用户 ("他" "她" 或 "他或她") 或者 "某人"。使用第二人称 "您" 来指代读者是可以的。</para>
+ <example id="ex-misc-wrong-person">
+ <title>不正确：第一或第三人称</title>
+ <para>正如上文所述，我通常在配置 Samba 服务器之前运行 <command>up2date</command>。</para>
+ <para>如果用户需要备份他的或她的文件，他或她应当使用 <command>tar</command> 或 <command>cpio</command> 命令。</para>
+ </example>
+ <example id="ex-misc-correct-person">
+ <title>正确：第二人称，或不使用代词</title>
+ <para>配置 Samba 服务器之前，请参考关于 <command>up2date</command> 的小节。</para>
+ <para>如果需要，用户可以使用 <command>tar</command> 或 <command>cpio</command> 命令来备份文件。</para>
+ </example>
+ </section>
+ <section id="sn-misc-negative">
+ <title>否定的用词</title>
+ <para>避免说不，因为它使教程显得武断。可以使用"避免"来代替。注意否定的词通常使用缩写，例如 <emphasis>don't</emphasis> 或 <emphasis>can't</emphasis>。请参考 <xref linkend="vle-contractions"/>。</para>
+ </section>
+ <section id="sn-misc-uncertainty">
+ <title>不确定</title>
+ <para>避免过度使用 "典型的"，"通常地"，"大多数时候"，"许多"等诸如此类的词。</para>
+ </section>
+ <section id="sn-misc-offtopic">
+ <title>多余的内容</title>
+ <para>避免涉及多余的内容，例如如何更新 &FC; 系统。这些关键的主题在其他教程中已有讲述。作者们经常违反这个准则，因为觉得自己的教程不够长。但是，不要偏离您的主题。如果其他教程可以完整的覆盖那些主题，那么指引读者阅读那些文档。</para>
+ </section>
+ <section id="sn-misc-importance">
+ <title>自行评估价值</title>
+ <para>避免类似 "最重要的是应该做 <replaceable>XYZ</replaceable>" 的表述。如果这个过程很重要，读者一定希望在您的文档中看到。反过来说，如果您的文档中出现了某个过程，作者一定会觉得那很重要，尤其是当这个过程占用了整整一节的时候。其实只要说 "做 <replaceable>XYZ</replaceable>"，然后详细说明就可以了。如果整整一节都是对如何做 <replaceable>XYZ</replaceable> 的说明，就干脆不要说这句话。请参考 <xref linkend="vle-golden-rule-4"/>。</para>
+ </section>
+ <section id="sn-misc-precision">
+ <title>明确的语言</title>
+ <para>对于用户应当做出的动作，使用明确的词汇。不要让读者 "去" 选择，或者让读者在菜单里 "找"。</para>
+ <example id="ex-precision-wrong">
+ <title>不正确：不明确的用词</title>
+ <itemizedlist>
+ <listitem>
+ <para>转到 <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</guimenuitem></para>
+ </listitem>
+ <listitem>
+ <para>找到标记 <guilabel>Search</guilabel> 的选项</para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-precision-right">
+ <title>正确：明确的用词</title>
+ <itemizedlist>
+ <listitem>
+ <para>在 <guimenu>Main Menu</guimenu> 菜单中，选择 <guimenuitem>Foobar</guimenuitem></para>
+ </listitem>
+ <listitem>
+ <para>选择 <guilabel>Search</guilabel> 选项。</para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <important>
+ <title>不要区别对待非图形界面用户</title>
+ <para>如果您的文档是关于纯图形界面程序的，那么可以随意使用 "点击"。如果应用程序有字符界面，那么可以使用 "选择"，像上面那样。</para>
+ </important>
+ </section>
+ <section id="sn-misc-docbook-tips">
+ <title>DocBook 技巧</title>
+ <para>这一节包含关于如何在文档中更有效地使用 DocBook 标记的技巧。</para>
+ <section id="sn-misc-admonitions">
+ <title>创建提示</title>
+ <para>避免过分使用提示。在提示中只包含最重要的内容，使提示尽可能短。将用来解释的背景说明移到提示之外。使用简短的描述性的标题。标题的大小写规则与正文标题一致。</para>
+ <example id="ex-misc-ineffective-admonition">
+ <title>不正确：过长的提示</title>
+ <para>
+ <warning>
+ <title>使用 <command>sfdisk</command> 检测输入</title>
+ <para>
+ <command>sfdisk</command> 命令接受一个脚本文件作为标准输入，来设置硬盘的分区。<command>sfdisk</command> 有些情况下拒绝一个有错的输入文件。在另一些情况下，它将无保留的执行输入，在硬盘上写入错误的分区。在写入磁盘前，总是用 <command>sfdisk -n</command> 命令检测输入文件。</para>
+ </warning>
+ </para>
+ </example>
+ <example id="ex-misc-good-admonition">
+ <title>正确：简短的提示</title>
+ <para>
+ <command>sfdisk</command> 命令接受一个脚本文件作为标准输入，来设置硬盘的分区。<command>sfdisk</command> 有些情况下拒绝一个有错的输入文件。在另一些情况下，它将无保留的执行输入，在硬盘上写入错误的分区。<warning><title>检测输入</title><para>在写入磁盘前，总是用 <command>sfdisk -n</command> 命令检测输入文件。</para></warning></para>
+ </example>
+ <para>避免在章节或提示的标题中使用标点，除非必须使用逗号。在标题中包含与提示相关的内容，例如 "需要重启"，而不是简单地使用提示类型作为标题 ("警告")。</para>
+ <para>提示的标题应使用与正文标题相同的大小写规则。</para>
+ </section>
+ <section id="sn-misc-replaceable">
+ <title>
+ <sgmltag class="starttag">replaceable</sgmltag> 标记</title>
+ <para>如果您的文档表述了作为约定的一个特定的值，那么不要在文中或示例中使用 <sgmltag class="starttag">replaceable</sgmltag> 标记。</para>
+ </section>
+ <section id="sn-misc-entities">
+ <title>XML 实体</title>
+ <para>使用 &FDP; 提供的实体。这些实体可以在 <filename>fedora-docs</filename> 的 <filename>common/</filename> 目录找到。(请参考 <xref linkend="ch-getting-files"/>。) 例如，不要使用缩写 "FC2"，应当使用预定义的实体 "&FC; &FCVER;"，这样将生成文本 "&FC; &FCVER;"。</para>
+ </section>
+ </section>
+ </section>
+</chapter>
+@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+@@
+
diff --git a/old-documentation-guide/Attic/docs-tutorial-en.xml,v b/old-documentation-guide/Attic/docs-tutorial-en.xml,v
new file mode 100644
index 0000000..7138eee
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-tutorial-en.xml,v
@@ -0,0 +1,311 @@
+head 1.9;
+access;
+symbols
+ VERSION-0_2:1.4;
+locks; strict;
+comment @# @;
+
+
+1.9
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.8;
+
+1.8
+date 2005.12.28.00.40.27; author pfrields; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2004.08.31.15.45.53; author tfox; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2004.08.13.16.08.48; author tfox; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2004.08.12.21.17.05; author tfox; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2004.02.24.21.30.01; author tfox; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2004.02.24.17.13.00; author tfox; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2004.01.30.19.43.27; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.9
+log
+ at Remove old files in en locale
+@
+text
+@<!-- $Id: docs-tutorial-en.xml,v 1.8 2005/12/28 00:40:27 pfrields Exp $ -->
+ <chapter id="ch-tutorial">
+ <title>The Layout of a Tutorial</title>
+
+ <para>
+ In this chapter, you will find an example of a &PROJECT; documentation
+ parent file. This example is specific to the way the Docs Project uses
+ DocBook XML. The parent file contains the main structural format of the
+ book, a link to the entities file that contain common entities that should
+ be used, and an entity to change the version and date of the tutorial.
+ </para>
+
+ <sect1 id="s1-tutorial-parent">
+ <title>The Parent File</title>
+
+ <para>
+ Below is a sample parent file:
+ </para>
+
+<screen>
+<computeroutput>
+<!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 "../common/fedora-entities-en.xml">
+%FEDORA-ENTITIES-EN;
+
+<!ENTITY VERSION "0.1"> <!-- change version of tutorial here -->
+
+<!ENTITY DOCID "example-tutorial-&VERSION; (2003-07-07)"> <!-- change last modified date here -->
+
+<!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice-en.xml">
+
+
+]>
+
+<article id="example-tutorial" lang="en">
+ <articleinfo>
+ <title>Example Tutorial</title>
+ <copyright>
+ <year>2003</year>
+ <holder>&FORMAL-RHI;</holder>
+ <holder>Tammy Fox</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ </authorgroup>
+ &LEGALNOTICE;
+ </articleinfo>
+
+ <section id="some-section">
+ <title>Some Section</title>
+
+ <para>
+ This is an example section. You can also use sect1, sect2, etc.
+ </para>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ Example of an admonition.
+ </para>
+ </warning>
+
+ </section>
+
+<index id="generated-index"></index>
+</article>
+</computeroutput>
+</screen>
+
+ </sect1>
+
+ <sect1 id="s1-tutorial-license">
+ <title>Including the License Information</title>
+
+ <indexterm>
+ <primary>tutorial layout</primary>
+ <secondary>license</secondary>
+ </indexterm>
+
+ <para>
+ All &PROJECT; manuals <emphasis>must</emphasis> contain the file
+ <filename>legalnotice.xml</filename>. This file makes the license for
+ the file the GNU Free Documentation License (FDL).
+ </para>
+
+ <para>
+ The sample parent file shows how it is included.
+ </para>
+
+ </sect1>
+
+ </chapter>
+
+
+@
+
+
+1.8
+log
+ at Update to use new entity standards
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial-en.xml,v 1.7 2004/08/31 15:45:53 tfox Exp $ -->
+@
+
+
+1.7
+log
+ at fix indentation
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial-en.xml,v 1.6 2004/08/13 16:08:48 tfox Exp $ -->
+d30 1
+a30 1
+<!ENTITY BOOKID "example-tutorial-&VERSION; (2003-07-07)"> <!-- change last modified date here -->
+@
+
+
+1.6
+log
+ at use common entities file
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial-en.xml,v 1.5 2004/08/12 21:17:05 tfox Exp $ -->
+d13 6
+a18 6
+ <sect1 id="s1-tutorial-parent">
+ <title>The Parent File</title>
+
+ <para>
+ Below is a sample parent file:
+ </para>
+d75 1
+a75 1
+ </sect1>
+d77 2
+a78 2
+ <sect1 id="s1-tutorial-license">
+ <title>Including the License Information</title>
+d80 16
+a95 14
+ <indexterm>
+ <primary>tutorial layout</primary>
+ <secondary>license</secondary>
+ </indexterm>
+
+ <para>
+ All &PROJECT; manuals <emphasis>must</emphasis> contain the file
+ <filename>legalnotice.xml</filename>. This file makes the license for
+ the file the GNU Free Documentation License (FDL).
+ </para>
+
+ <para>
+ The sample parent file shows how it is included.
+ </para>
+a96 2
+ </sect1>
+
+@
+
+
+1.5
+log
+ at fix DocBook declaration and sync with example-tutorial-en.xml in CVS
+@
+text
+ at d1 1
+a1 2
+<!-- $Id: docs-tutorial-en.xml,v 1.4 2004/02/24 21:30:01 tfox Exp $ -->
+
+d9 2
+a10 1
+ book, entities that should be used for this book specifically and more.
+d25 6
+a30 6
+<!ENTITY RH "Red Hat"> <!--The generic term "Red Hat" -->
+<!ENTITY FORMAL-RHI "&RH;, Inc."> <!--The generic term "Red Hat, Inc. -->
+<!ENTITY PROJECT "Fedora project"> <!-- Set the project name -->
+<!ENTITY NAME-TITLE "Fedora Project"> <!-- Set the project name, use for titles -->
+<!ENTITY DISTRO "Fedora Core"> <!-- Set the distro name -->
+<!ENTITY BOOKID "example-tutorial-0.1 (2003-07-07)"> <!-- change version of manual and date here -->
+@
+
+
+1.4
+log
+ at change index tag to include static id
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial-en.xml,v 1.3 2004/02/24 17:13:00 tfox Exp $ -->
+d22 1
+a22 1
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
+@
+
+
+1.3
+log
+ at add end index tag to example parent file
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial-en.xml,v 1.2 2004/01/30 19:43:27 tfox Exp $ -->
+d70 1
+a70 1
+<index/>
+@
+
+
+1.2
+log
+ at update location of legalnotice XML file
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial-en.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+d70 1
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial.xml,v 1.6 2003/09/16 19:26:26 tfox Exp $ -->
+d32 1
+a32 1
+<!ENTITY LEGALNOTICE SYSTEM "../legalnotice.xml">
+@
+
diff --git a/old-documentation-guide/Attic/docs-tutorial-zh_CN.xml,v b/old-documentation-guide/Attic/docs-tutorial-zh_CN.xml,v
new file mode 100644
index 0000000..daaa625
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-tutorial-zh_CN.xml,v
@@ -0,0 +1,144 @@
+head 1.4;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.4
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.3;
+
+1.3
+date 2005.12.28.00.40.27; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.17.13.28.38; author bbbush; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.4
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id: docs-tutorial-zh_CN.xml,v 1.3 2005/12/28 00:40:27 pfrields Exp $ --><chapter id="ch-tutorial">
+ <title>文档的布局</title>
+ <para>在本章您将看到 &PROJECT; 文档中，主控文件的示例。这个示例与 Docs Project 处理 DocBook XML 的方式相关。主控文件包含文档的主要结构，以及到定义公共实体的文件的链接，还包括定义文档版本和日期的实体。</para>
+ <sect1 id="s1-tutorial-parent">
+ <title>主控文件</title>
+ <para>下面是一个简单的主控文件</para>
+ <screen>
+ <computeroutput>
+<!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 "../common/fedora-entities-en.xml">
+%FEDORA-ENTITIES-EN;
+
+<!ENTITY VERSION "0.1"> <!-- change version of tutorial here -->
+
+<!ENTITY DOCID "example-tutorial-&VERSION; (2003-07-07)"> <!-- change last modified date here -->
+
+<!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice-en.xml">
+
+
+]>
+
+<article id="example-tutorial" lang="en">
+ <articleinfo>
+ <title>Example Tutorial</title>
+ <copyright>
+ <year>2003</year>
+ <holder>&FORMAL-RHI;</holder>
+ <holder>Tammy Fox</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ </authorgroup>
+ &LEGALNOTICE;
+ </articleinfo>
+
+ <section id="some-section">
+ <title>Some Section</title>
+
+ <para>
+ This is an example section. You can also use sect1, sect2, etc.
+ </para>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ Example of an admonition.
+ </para>
+ </warning>
+
+ </section>
+
+<index id="generated-index"></index>
+</article>
+</computeroutput>
+ </screen>
+ </sect1>
+ <sect1 id="s1-tutorial-license">
+ <title>包含许可信息</title>
+ <indexterm>
+ <primary>文档版式</primary>
+ <secondary>许可</secondary>
+ </indexterm>
+ <para>所有 &PROJECT; 手册 <emphasis>必须</emphasis> 包含文件 <filename>legalnotice.xml</filename>。这个文件包含了 GNU Free Documentation License (FDL) 的文本。</para>
+ <para>示例主控文件显示了如何包含它们。</para>
+ </sect1>
+</chapter>
+@
+
+
+1.3
+log
+ at Update to use new entity standards
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: docs-tutorial-zh_CN.xml,v 1.2 2005/12/17 13:28:38 bbbush Exp $ --><chapter id="ch-tutorial">
+@
+
+
+1.2
+log
+ at update build part
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: docs-tutorial-en.xml,v 1.7 2004/08/31 15:45:53 tfox Exp $ --><chapter id="ch-tutorial">
+d18 1
+a18 1
+<!ENTITY BOOKID "example-tutorial-&VERSION; (2003-07-07)"> <!-- change last modified date here -->
+@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+@@
+
diff --git a/old-documentation-guide/Attic/docs-tutorial.xml,v b/old-documentation-guide/Attic/docs-tutorial.xml,v
new file mode 100644
index 0000000..a875d0a
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-tutorial.xml,v
@@ -0,0 +1,138 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2003.11.21.22.40.39; author tfox; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at change filenames to end with -en.xml
+@
+text
+@<!-- $Id: docs-tutorial.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+
+ <chapter id="ch-tutorial">
+ <title>The Layout of a Tutorial</title>
+
+ <para>
+ In this chapter, you will find an example of a &PROJECT; documentation
+ parent file. This example is specific to the way the Docs Project uses
+ DocBook XML. The parent file contains the main structural format of the
+ book, entities that should be used for this book specifically and more.
+ </para>
+
+ <sect1 id="s1-tutorial-parent">
+ <title>The Parent File</title>
+
+ <para>
+ Below is a sample parent file:
+ </para>
+
+<screen>
+<computeroutput>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+
+<!ENTITY RH "Red Hat"> <!--The generic term "Red Hat" -->
+<!ENTITY FORMAL-RHI "&RH;, Inc."> <!--The generic term "Red Hat, Inc. -->
+<!ENTITY PROJECT "Fedora project"> <!-- Set the project name -->
+<!ENTITY NAME-TITLE "Fedora Project"> <!-- Set the project name, use for titles -->
+<!ENTITY DISTRO "Fedora Core"> <!-- Set the distro name -->
+<!ENTITY BOOKID "example-tutorial-0.1 (2003-07-07)"> <!-- change version of manual and date here -->
+
+<!ENTITY LEGALNOTICE SYSTEM "../legalnotice.xml">
+
+
+]>
+
+<article id="example-tutorial" lang="en">
+ <articleinfo>
+ <title>Example Tutorial</title>
+ <copyright>
+ <year>2003</year>
+ <holder>&FORMAL-RHI;</holder>
+ <holder>Tammy Fox</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ </authorgroup>
+ &LEGALNOTICE;
+ </articleinfo>
+
+ <section id="some-section">
+ <title>Some Section</title>
+
+ <para>
+ This is an example section. You can also use sect1, sect2, etc.
+ </para>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ Example of an admonition.
+ </para>
+ </warning>
+
+ </section>
+
+</article>
+</computeroutput>
+</screen>
+
+ </sect1>
+
+ <sect1 id="s1-tutorial-license">
+ <title>Including the License Information</title>
+
+ <indexterm>
+ <primary>tutorial layout</primary>
+ <secondary>license</secondary>
+ </indexterm>
+
+ <para>
+ All &PROJECT; manuals <emphasis>must</emphasis> contain the file
+ <filename>legalnotice.xml</filename>. This file makes the license for
+ the file the GNU Free Documentation License (FDL).
+ </para>
+
+ <para>
+ The sample parent file shows how it is included.
+ </para>
+
+ </sect1>
+
+ </chapter>
+
+
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial.xml,v 1.6 2003/09/16 19:26:26 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/Attic/docs-vim-en.xml,v b/old-documentation-guide/Attic/docs-vim-en.xml,v
new file mode 100644
index 0000000..fb3f53c
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-vim-en.xml,v
@@ -0,0 +1,223 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.23.22.57.30; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2004.03.18.20.25.02; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old files in en locale
+@
+text
+@<!-- $Id: docs-vim-en.xml,v 1.2 2005/12/23 22:57:30 pfrields Exp $ -->
+
+ <chapter id="ch-vim">
+ <title>VIM and DocBook</title>
+
+ <indexterm>
+ <primary>VIM</primary>
+ </indexterm>
+
+ <para>
+ VIM has many features to help you write XML content such as DocBook,
+ including syntax highlighting and customizable key bindings.
+ Additionally, one can easily use external programs from VIM for features
+ such as spell-checking.
+ This chapter assumes you already know generally how to use VIM; if you
+ want to learn how, try the <command>vimtutor</command> or by typing
+ <userinput>:help tutor</userinput> from inside VIM.
+ </para>
+
+ <sect1 id="s1-vimrc-file">
+ <title>Setting Up Your <filename>.vimrc</filename> File</title>
+
+ <indexterm>
+ <primary>VIM</primary>
+ <secondary>configuration file</secondary>
+ </indexterm>
+
+ <para>
+ Below is a short sample <filename>.vimrc</filename> file that turns on
+ some VIM features useful for editing SGML or XML content such as
+ DocBook:
+<screen>
+<computeroutput>" Turn off vi compatibility settings like limited undo
+set nocompatible
+" Syntax highlighting based on file extension
+syntax on
+" Automatically insert newlines after 80 characters
+set textwidth=80
+" Automatically indent
+set autoindent
+" Match SGML tags with %
+source $VIMRUNTIME/macros/matchit.vim</computeroutput>
+</screen>
+ </para>
+ <note>
+ <para>
+ Some of these features require the <filename>vim-enhanced</filename>
+ package to be installed. If you are using or the
+ <filename>vim-minimal</filename> package, or if you are using an older
+ version of VIM, you may not have the
+ <filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still
+ download <ulink
+ url="http://vim.org/scripts/script.php?script_id=39">matchit.zip from
+ Vim.org</ulink> and load it separately.
+ </para>
+ </note>
+ </sect1>
+
+ <sect1 id="s1-vim-keymapping">
+ <title>Keymapping with VIM</title>
+
+ <para>
+ VIM can speed up your DocBook creation by mapping frequently typed tags
+ (or any words or phrases) onto short key combinations. By default, the
+ keymap leader is the backslash (<literal>\</literal>), but it can be
+ redefined with a command like <userinput>let mapleader =
+ ","</userinput>. There are two ways to use the following example;
+ you can put it directly in your <filename>.vimrc</filename>, or you
+ can save it in a separate file and load it with a
+ <userinput>source</userinput> command in your
+ <filename>.vimrc</filename>.
+<screen>
+<![CDATA[let mapleader = ","
+
+" skip ahead to after next tag without leaving insert mode
+imap <leader>e <esc>/><cr>:nohlsearch<cr>a
+
+" common tags that start a new text block
+imap<leader>pa <para><cr></para><esc>O
+imap<leader>s1 <sect1 id=""><cr><para><esc>jo</sect1><esc>O
+imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i
+imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i
+
+" common tags that are placed inline
+" use <esc>F>a
+imap<leader>en <envar></envar><esc>F>a
+imap<leader>fi <filename></filename><esc>F>a
+imap<leader>lt <literal></literal><esc>F>a
+imap<leader>re <replaceable></replaceable><esc>F>a
+imap<leader>ui <userinput></userinput><esc>F>a
+imap<leader>ul <ulink url=""></ulink><esc>F>a
+imap<leader>si <systemitem></systemitem><esc>F>a
+imap<leader>us <systemitem class="username"></systemitem><esc>F>a
+imap<leader>sy <systemitem class="systemname"></systemitem><esc>F>a
+imap<leader>cm <command></command><esc>F>a
+" entities
+imap <leader>> >
+imap <leader>< <]]>
+</screen>
+ </para>
+ <para>
+ Unfortunately, there is not currently a complete macro set for all
+ DocBook commands, so you will need to define them yourself or customize
+ the definitions in the examples from <xref
+ linkend="s1-vim-additional-resources"></xref>.
+ </para>
+ </sect1>
+
+ <sect1 id="s1-vim-additional-resources">
+ <title>Additional VIM Resources</title>
+
+ <para>
+ Additional information about VIM may be found from:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink url=
+ "http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC">
+ Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to
+ Vi Improved (VIM)</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para>The <ulink url="http://tnerual.eriogerg.free.fr/vim.html">VIM
+ Quick Reference Card</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://www.pinkjuice.com/howto/vimxml/">Vim as XML
+ Editor</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with
+ the <filename>vim-common</filename> package —
+ <filename>/usr/share/vim/<replaceable><version></replaceable>/doc/intro.txt</filename>
+ or type <userinput>:help intro</userinput> from within VIM
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect1>
+ </chapter>
+@
+
+
+1.2
+log
+ at Fix alignment and eliminate invalid tag
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-vim-en.xml,v 1.1 2004/03/18 20:25:02 tfox Exp $ -->
+@
+
+
+1.1
+log
+ at add chapter on VIM
+@
+text
+ at d1 1
+a1 1
+<!-- $Id$ -->
+d33 1
+a33 2
+<computeroutput>
+" Turn off vi compatibility settings like limited undo
+d42 1
+a42 2
+source $VIMRUNTIME/macros/matchit.vim
+</computeroutput>
+d72 2
+a73 4
+ <screen>
+ <programlisting>
+ <![CDATA[
+let mapleader = ","
+d98 2
+a99 4
+imap <leader>< <
+]]>
+ </programlisting>
+ </screen>
+@
+
diff --git a/old-documentation-guide/Attic/docs-vim-zh_CN.xml,v b/old-documentation-guide/Attic/docs-vim-zh_CN.xml,v
new file mode 100644
index 0000000..cee98cb
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-vim-zh_CN.xml,v
@@ -0,0 +1,140 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.17.13.28.38; author bbbush; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id: docs-vim-zh_CN.xml,v 1.2 2005/12/17 13:28:38 bbbush Exp $ --><chapter id="ch-vim">
+ <title>VIM 与 DocBook</title>
+ <indexterm>
+ <primary>VIM</primary>
+ </indexterm>
+ <para>VIM 有很多特性，有助于撰写类似 DocBook 的 XML 文档，包括语法高亮和可定制的按键绑定。另外，还可以用外部程序辅助 VIM 完成拼写检查等操作。本章假定您已知悉 VIM 一般用法；如果您要学习一般用法，执行 <command>vimtutor</command> 或在 VIM 中执行 <userinput>:help tutor</userinput>。</para>
+ <sect1 id="s1-vimrc-file">
+ <title>设置 <filename>.vimrc</filename> 文件</title>
+ <indexterm>
+ <primary>VIM</primary>
+ <secondary>配置文件</secondary>
+ </indexterm>
+ <para>下面是一个示例 <filename>.vimrc</filename> 文件，打开了一些 VIM 特性，便于编辑类似 DocBook 的 SGML 或 XML 文档： <screen><computeroutput>
+" 关闭 vi 兼容特性，类似有限的撤销
+set nocompatible
+" 基于文件扩展名的语法高亮
+syntax on
+" 在 80 个字符后面自动插入新行
+set textwidth=80
+" 自动缩进
+set autoindent
+" 使用 % 匹配 SGML 标记
+source $VIMRUNTIME/macros/matchit.vim
+</computeroutput></screen></para>
+ <note>
+ <para>一些特性需要安装 <filename>vim-enhanced</filename>。如果您使用的是 <filename>vim-minimal</filename>，或者是旧版本的 VIM，可能不包含 <filename>$VIMRUNTIME/macros/matchit.vim</filename> 文件，那么可以在 Vim.org 下载 <ulink url="http://vim.org/scripts/script.php?script_id=39">matchit.zip</ulink> 并加载。</para>
+ </note>
+ </sect1>
+ <sect1 id="s1-vim-keymapping">
+ <title>VIM 中的按键映射</title>
+ <para>VIM 可以使创建 DocBook 文档更加快捷，只要将经常使用的标记 (或任何词汇短语) 定义为快捷键。默认情况下，键盘映射以反斜线 (<literal>\</literal>) 开始，但是也可以用命令定义，类似 <userinput>let mapleader =
+ ","</userinput>。有两种方式来使用下面的例子；您可以将它写在 <filename>.vimrc</filename> 文件中，或者将它保存为单独的文件，并在 <filename>.vimrc</filename> 文件中以 <userinput>source</userinput> 命令加载。<screen><programlisting><![CDATA[
+let mapleader = ","
+
+" skip ahead to after next tag without leaving insert mode
+imap <leader>e <esc>/><cr>:nohlsearch<cr>a
+
+" common tags that start a new text block
+imap<leader>pa <para><cr></para><esc>O
+imap<leader>s1 <sect1 id=""><cr><para><esc>jo</sect1><esc>O
+imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i
+imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i
+
+" common tags that are placed inline
+" use <esc>F>a
+imap<leader>en <envar></envar><esc>F>a
+imap<leader>fi <filename></filename><esc>F>a
+imap<leader>lt <literal></literal><esc>F>a
+imap<leader>re <replaceable></replaceable><esc>F>a
+imap<leader>ui <userinput></userinput><esc>F>a
+imap<leader>ul <ulink url=""></ulink><esc>F>a
+imap<leader>si <systemitem></systemitem><esc>F>a
+imap<leader>us <systemitem class="username"></systemitem><esc>F>a
+imap<leader>sy <systemitem class="systemname"></systemitem><esc>F>a
+imap<leader>cm <command></command><esc>F>a
+" entities
+imap <leader>> >
+imap <leader>< <
+]]></programlisting></screen></para>
+ <para>不幸的是，这不是所有 DocBook 命令的完整集合，因此您需要自行定义，或定制 <xref linkend="s1-vim-additional-resources"/> 范例中的定义。</para>
+ </sect1>
+ <sect1 id="s1-vim-additional-resources">
+ <title>其他 VIM 资源</title>
+ <para>其他 VIM 相关的资源可以在这里找到：</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC"> 示例 sgml-vimrc</ulink>，来自 <citetitle>Beginner's guide to Vi Improved (VIM)</citetitle></para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://tnerual.eriogerg.free.fr/vim.html">VIM Quick Reference Card</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://www.pinkjuice.com/howto/vimxml/">Vim 作为 XML 编辑器</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <citetitle>VIM REFERENCE MANUAL</citetitle>，包含在 <filename>vim-common</filename> 软件包中 — <filename>/usr/share/vim/<replaceable><version></replaceable>/doc/intro.txt</filename>，可以在 VIM 中执行 <userinput>:help intro</userinput> 查看。</para>
+ </listitem>
+ </itemizedlist>
+ </sect1>
+</chapter>
+@
+
+
+1.2
+log
+ at update build part
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: docs-vim-en.xml,v 1.1 2004/03/18 20:25:02 tfox Exp $ --><chapter id="ch-vim">
+@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+@@
+
diff --git a/old-documentation-guide/Attic/docs-xml-tags-en.xml,v b/old-documentation-guide/Attic/docs-xml-tags-en.xml,v
new file mode 100644
index 0000000..876804e
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-xml-tags-en.xml,v
@@ -0,0 +1,2953 @@
+head 1.13;
+access;
+symbols
+ VERSION-0_2:1.3;
+locks; strict;
+comment @# @;
+
+
+1.13
+date 2006.11.23.20.32.31; author pfrields; state dead;
+branches;
+next 1.12;
+
+1.12
+date 2004.09.30.14.25.36; author tfox; state Exp;
+branches;
+next 1.11;
+
+1.11
+date 2004.09.13.02.02.12; author tfox; state Exp;
+branches;
+next 1.10;
+
+1.10
+date 2004.08.31.15.46.17; author tfox; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2004.08.13.16.08.48; author tfox; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2004.08.12.21.33.45; author tfox; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2004.08.12.21.07.03; author tfox; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2004.08.12.21.01.19; author tfox; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2004.08.12.20.49.58; author tfox; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2004.08.12.20.48.40; author tfox; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2004.02.24.21.30.14; author tfox; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2003.10.15.18.11.01; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.13
+log
+ at Remove old files in en locale
+@
+text
+@<!-- $Id: docs-xml-tags-en.xml,v 1.12 2004/09/30 14:25:36 tfox Exp $ -->
+
+ <chapter id="ch-xml-tags">
+ <title>DocBook XML Tags</title>
+
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>tags</secondary>
+ <see>XML tags</see>
+ </indexterm>
+
+ <para>Please read this chapter carefully. This chapter describes the tags
+ used by the Docs Project. Some of the rules described are specific to the
+ project.
+ </para>
+
+ <para>If these tags are used appropriately, document searches will provide
+ meaningful results. These tags help search engines identify the
+ information relevant to the search request. Another benefit is that all
+ &PROJECT; documents will have a similar look and feel (however, they will have
+ some differences depending upon the output format).
+ </para>
+
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>general tag information</secondary>
+ </indexterm>
+
+ <para>All tags in XML must have an opening and closing tag Additionally,
+ proper XML conventions say that there must be a unique identifier for
+ sections, chapters, figures, tables, and so on, so that they may be
+ correctly identified, and cross referenced if needed.</para>
+
+ <para>Although XML is capable of handling many document types, the format
+ discussed here is the article format.</para>
+
+ <para>
+ This chapter only discusses tags used for documentation for the &PROJECT;,
+ not all available DocBook XML tags. For the complete list, refer to:
+ </para>
+<screen>
+<computeroutput>
+<ulink url="http://www.docbook.org/tdg/en/html/docbook.html">http://www.docbook.org/tdg/en/html/docbook.html</ulink>
+</computeroutput>
+</screen>
+
+ <sect1 id="s1-xml-tags-caveats">
+ <title>Tags and Entities Caveats</title>
+
+ <indexterm>
+ <primary>xml tags</primary>
+ <secondary>caveats</secondary>
+ </indexterm>
+
+ <para>
+ It is very important that you remember the caveats in this section. Even
+ though they are more strict than valid DocBook XML, these rules exist
+ so that both the HTML and PDF outputs look proper.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>Do Not Use Trademark Entities</term>
+ <listitem>
+ <para>Do not use the trademark entities &trade;, &copy;, or
+ &reg; because the do not produce HTML output that works for all
+ charsets. The HTML output produces by these entities are declared in
+ the DTD and cannot be changed via the stylesheet.</para>
+ <para>Instead, use the <command>trademark</command> tag and its
+ associates classes as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><trademark>trademark symbol after me</trademark>
+ </para>
+ </listitem>
+ <listitem>
+ <para><trademark class="registered">registered trademark symbol after me</trademark>
+ </para>
+ </listitem>
+ <listitem>
+ <para><trademark class="copyright">copyright symbol after me</trademark></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <command>para</command> tags</term>
+ <listitem>
+ <para>Do not use <command>para</command> tags around anything other
+ than a simple paragraph. Doing so will create additional white space
+ within the text itself in the PDF version.
+ </para>
+ <para>Specifically, do not use <command>para</command> tags around
+ the following (or, to put this another way, do not embed the
+ following within <command>para</command> tags):
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><screen></para>
+ </listitem>
+ <listitem>
+ <para><itemizedlist></para>
+ </listitem>
+ <listitem>
+ <para><orderedlist></para>
+ </listitem>
+ <listitem>
+ <para><variablelist></para>
+ </listitem>
+ <listitem>
+ <para><table></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <command>para</command> tags within
+ <command>listitem</command> tags</term>
+ <listitem>
+ <para>Content inside <command>para</command> tags within
+ <command>listitem</command> tags <emphasis>must</emphasis> start
+ immediately after the beginning <para> tag to avoid extra
+ white space in the PDF version.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <command>screen</command> tags</term>
+ <listitem>
+ <para>The <command>screen</command> tags (<screen> and
+ </screen>) <emphasis>must</emphasis> be flush left in the
+ XML file, and all the content inside the
+ <command>screen</command> tags must be flush left as well unless
+ the white space in intentional; otherwise, the extraneous
+ whitespace will appear in the HTML version.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-application">
+ <title><command>application</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>application</secondary>
+ </indexterm>
+
+ <para>An application is the name of a GUI software program. A command is
+ the name of an executable (text) program or a software command.</para>
+
+ <para>The <command><application></command> and
+ <command></application></command> tags allow you to refer to an
+ application or program. For example, the following XML:
+ </para>
+
+<screen>
+<computeroutput>
+To view the Web in Linux, you can use
+<application>Mozilla</application> or
+<application>lynx</application> if you only want a text-based
+browser.
+</computeroutput>
+</screen>
+
+ <para>
+ produces the following output:
+ </para>
+
+ <para>
+ To view the Web in Linux, you can use <application>Mozilla</application>
+ or <application>lynx</application> if you only want a text-based browser.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-chapter">
+ <title><command>chapter</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>chapter</secondary>
+ </indexterm>
+
+ <para>
+ A DocBook book can be divided into chapters such as:
+ </para>
+
+<screen>
+<computeroutput>
+<!--$Id: docs-xml-tags-en.xml,v 1.12 2004/09/30 14:25:36 tfox Exp $ -->
+
+ <chapter id="ch-sample">
+ <title>Sample Chapter</title>
+
+ <para>This is a sample chapter, showing you the XML tags used to create a
+ chapter, sections, and subsections.</para>
+
+ </chapter>
+</computeroutput>
+</screen>
+
+ <para>
+ The chapter can also be further divided into sections
+ (<command>sect1</command>, <command>sect2</command>,
+ <command>sect3</command>, etc.). Refer to <xref
+ linkend="s1-xml-tags-sections"></xref> for details.
+ </para>
+
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-citetitle">
+ <title><command>citetitle</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>citetitle</secondary>
+ </indexterm>
+
+
+ <para>
+ The <command><citetitle></command> tag provides formatting for a
+ specific references (title can be manually typed out or if already
+ defined within your document set, given as an entity<footnote><para>An
+ entity is a short hand way of referring to another manual or guide. It
+ can be defined within the parent document or within a set of files that
+ your DTD references for your specific documentation set.</para>
+ </footnote>
+ ).</para>
+
+ <para>
+ For example:
+ </para>
+<screen>
+<computeroutput>
+<citetitle>IG;</citetitle>.
+</computeroutput>
+</screen>
+ <para>
+ The output looks like <citetitle>&IG;</citetitle> because &IG; is an
+ entity.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-command">
+ <title><command>command</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>command</secondary>
+ </indexterm>
+
+ <para>An application is the name of a GUI software program. A command is
+ the name of an executable (text) program or a software command. Any
+ program that is a command line or text-based only tool is marked with
+ <command>command</command> tags. </para>
+
+
+ <para>If you have text that is a command, use the
+ <command><command></command> and
+ <command></command></command> tags such as:
+ </para>
+
+
+
+<screen>
+<computeroutput>
+To change your keyboard after installation, become root
+and use the <command>redhat-config-keyboard</command> command,
+or you can type <command>setup</command> at the root prompt.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+ <para>
+ To change your keyboard after installation, become root and use
+ the <command>redhat-config-keyboard</command> command, or you can type
+ <command>setup</command> at the root prompt.
+ </para>
+
+ <para>Another example would be:</para>
+
+<screen>
+<computeroutput>
+<command>MAILNOVIOLATIONS</command> — If set
+to <command>true</command> this option tells Tripwire to
+email a report at a regular interval regardless of whether or not
+any violations have occured. The default value is
+<command>true</command>.
+</computeroutput>
+</screen>
+
+ <para>
+ with the output:
+ </para>
+
+ <para>
+ <command>MAILNOVIOLATIONS</command> — If set to
+ <command>true</command> this variable tells Tripwire to email a report
+ at a regular interval regardless of whether or not any violations have
+ occured. The default value is <command>true</command>.
+ </para>
+
+ <note>
+ <title>Note</title> <para>In this example, the option value (true) is
+ defined with a <command> tag set. Because a option is a
+ configuration file option (command line options which would use the
+ <option> tag set), and because there is no configuration file
+ option tag available to use, we are extending the <command> tag
+ set to define options in a configuration file.</para>
+ </note>
+
+ <para>
+ Terms marked with <command>command</command> tags because there aren't
+ exact tags for them:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Options in configuration files such as Apache directives</para>
+ </listitem>
+ <listitem>
+ <para>daemon names</para>
+ </listitem>
+ </itemizedlist>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-compoutput">
+ <title><command>computeroutput</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>computeroutput</secondary>
+ </indexterm>
+
+ <para>
+ To show computer output use the following tags:
+ </para>
+<screen>
+<computeroutput>
+<computeroutput>Do you want to delete this file? y n</computeroutput>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+ <para>
+ <computeroutput>Do you really want to delete this file? y n</computeroutput>
+ </para>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-emphasis">
+ <title><command>emphasis</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>emphasis</secondary>
+ </indexterm>
+
+ <para>
+ To emphasis content, use the <command><emphasis></command> and
+ <command></emphasis></command> tags. For example:
+ </para>
+<screen>
+<computeroutput>
+This installation <emphasis>will remove all</emphasis> existing
+Linux partitions on <emphasis>all</emphasis> hard drives in your
+system; non-Linux partitions will not be removed.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ This installation <emphasis>will remove all</emphasis> existing Linux
+ partitions on <emphasis>all</emphasis> hard drives in your system;
+ non-Linux partitions will not be removed.
+ </para>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-example">
+ <title><command>example</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>example</secondary>
+ </indexterm>
+
+ <para>The <command><example></command> and
+ <command></example></command> tags are used to format text within a
+ document and is great for adding emphasis to show examples of code,
+ exercises, and more. </para>
+
+ <para>The <command><example></command> tag set should be given an ID
+ and title:</para>
+
+<screen>
+ <example id="static-ip">
+ <title>Static IP Address using DHCP</title>
+
+<screen width=60>
+<computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+<computeroutput>
+</screen>
+
+ </example>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <example id="static-ip">
+ <title>Static IP Address using DHCP</title>
+
+<screen>
+<computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+</computeroutput>
+</screen>
+ </example>
+
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-filename">
+ <title><command>filename</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>filename</secondary>
+ </indexterm>
+
+ <para>
+ The <command><filename></command> and
+ <command></filename></command> tags define a filename or path to a
+ file. Since directories are just special files, they are marked with the
+ <command>filename</command> tags as well. For example:
+ </para>
+<screen>
+Edit the <filename>/home/smoore/sam.xml</filename> file to make
+changes or add comments.
+</screen>
+ <para>
+ The output:
+ </para>
+ <para>
+ Edit the <filename>/home/smoore/sam.xml</filename> file to make changes
+ or add comments.
+ </para>
+
+ <para>
+ They are also used to markup an RPM package name. For example:
+ </para>
+<screen>
+To use the <application>Keyboard Configuration Tool</application>, the
+<filename>system-config-keyboard</filename> RPM package must be installed.
+</screen>
+ <para>
+ The output:
+ </para>
+ <para>
+ To use the <application>Keyboard Configuration Tool</application>, the
+ <command>redhat-config-keyboard</command> RPM package must be installed.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ Directory names must end with a forward slash
+ (<computeroutput>/</computeroutput>) to distinguish them from file
+ names.
+ </para>
+ </note>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-firstterm">
+ <title><command>firstterm</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>firstterm</secondary>
+ </indexterm>
+
+ <para>
+ The <command><firstterm></command> and
+ <command></firstterm></command> tags helps to define a word that
+ may be unfamiliar to the user, but that will be seen commonly throughout
+ the text. For example:
+ </para>
+<screen>
+<computeroutput>
+Nearly every modern-day operating system uses <firstterm>disk
+partitions</firstterm>, and &FC; is no exception.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Nearly every modern-day operating system uses <firstterm>disk
+ partitions</firstterm>, and &FC; is no exception.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-footnote">
+ <title><command>footnote</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>footnote</secondary>
+ </indexterm>
+
+ <para>
+ If you need to make a footnote, use the following example:
+ </para>
+<screen>
+<computeroutput>
+For those of you who need to perform a server-class
+<footnote>
+<para>
+A server-class installation sets up a typical server
+environment. Note, no graphical environment is
+installed during a server-class installation.
+</para>
+</footnote> installation, refer to the <citetitle>Installation Guide</citetitle>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ For those of you who need to perform a server-class <footnote> <para>A
+ server-class installation sets up a typical server environment. Please note, no
+ graphical environment is installed during a server-class installation.</para>
+ </footnote> installation, refer to the
+ <citetitle>Installation Guide</citetitle>.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-figure">
+ <title><command>figure</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>figure</secondary>
+ </indexterm>
+
+ <important>
+ <title>Important</title>
+ <para>
+ Order matters! The EPS file <emphasis>must</emphasis> be declared
+ first.
+ </para>
+ </important>
+
+ <para>
+ An example figure declaration:
+ </para>
+
+<screen>
+<computeroutput>
+<figure id="fig-ksconfig-basic">
+ <title>Basic Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.eps"
+ format="EPS"/>
+ </imageobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.png"
+ format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>
+ Some text description of this image
+ </phrase>
+ </textobject>
+ </mediaobject>
+</figure>
+</computeroutput>
+</screen>
+
+ <para>
+ The following describes what needs to be edited:
+ </para>
+
+<screen>
+<figure id="fig-ksconfig-basic"> <emphasis>==> id="" would be edited</emphasis>
+
+<title>Basic Configuration</title> <emphasis>==> title would be edited</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.eps"> <emphasis>==> .eps location would be edited</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.png"> <emphasis>==> .png location would be edited</emphasis>
+
+<phrase>Some text description of this image</phrase> <emphasis>==> "Some text..." would be edited</emphasis>
+</screen>
+
+ <para>
+ For more information on taking screenshots, refer to <xref
+ linkend="s1-screenshots"/>.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-gui">
+ <title>GUI Tags</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ </indexterm>
+
+ <sect2 id="s2-xml-tags-guilabel">
+ <title><command>guilabel</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guilabel</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guilabel</secondary>
+ </indexterm>
+
+ <para>
+ Use the <command><guilabel></command> and
+ <command></guilabel></command> tags as a default for GUI
+ descriptions, like a screen name or screen title. For example:
+ </para>
+<screen>
+<computeroutput>
+The <guilabel>Authentication Configuration</guilabel> screen
+shows you how to make your system more secure.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ The <guilabel>Authentication Configuration</guilabel> screen shows you how to
+ make your system more secure.
+ </para>
+ </sect2>
+
+ <sect2 id="s2-xml-tags-guibutton">
+ <title><command>guibutton</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guibutton</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guibutton</secondary>
+ </indexterm>
+
+ <para>
+ Use the <command><guibutton></command> and
+ <command></guibutton></command> tags to denote a button on a screen or
+ menu. For example:
+ </para>
+<screen>
+<computeroutput>
+Check the <guibutton>Activate on boot</guibutton> button
+to have the X Window System start automatically.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Check the <guibutton>Activate on boot</guibutton> button to have the X
+ Window System start automatically.
+ </para>
+ </sect2>
+
+ <sect2 id="s2-xml-tags-guiicon">
+ <title><command>guiicon</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guiicon</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guiicon</secondary>
+ </indexterm>
+
+ <para>
+ The <command><guiicon></command> and <command></guiicon></command>
+ tags are used to denote a panel or desktop icon. For example:
+ </para>
+<screen>
+<computeroutput>
+Double-click the <guiicon>Start Here</guiicon> icon on the desktop.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Double-click the <guiicon>Start Here</guiicon> icon on the desktop.
+ </para>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-guimenu">
+ <title><command>guimenu</command> and
+ <command>guimenuitem</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guimenu</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guimenu</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guimenuitem</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guimenuitem</secondary>
+ </indexterm>
+
+ <para>
+ To note a menu (like in the installation program or within the control panel),
+ use the <command><guimenu></command> and
+ <command></guimenu></command> tags.
+ </para>
+
+ <para>
+ To note submenu items, use the <command><guimenuitem></command> and
+ <command></guimenuitem></command> tags. (Please note that there should not
+ be any breaks between these commands, but for printing purposes breaks have been
+ inserted). For example:
+ </para>
+<screen>
+<computeroutput>
+Select
+<guimenu>Main Menu</guimenu> =>
+ <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> to start the
+<application>Emacs</application> text editor.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ From the control panel, click on <guimenu>Main Menu</guimenu> =>
+ <guimenuitem>Programming</guimenuitem> =>
+ <guimenuitem>Emacs</guimenuitem> to start the
+ <application>Emacs</application> text editor.
+ </para>
+ </sect2>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-keycap">
+ <title><command>keycap</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>keycap</secondary>
+ </indexterm>
+
+ <para>
+ To denote a specific key, you will need to use the
+ <command><keycap></command> and <command></keycap></command>
+ tags. Brackets are automatically added around the keycap, so do not add
+ them in your XML code. For example:
+ </para>
+<screen>
+<computeroutput>
+To make your selection, press the <keycap>Enter</keycap> key.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ To make your selection, press the <keycap>Enter</keycap> key.
+ </para>
+
+ <sect2 id="s2-xml-tags-menuchoice">
+ <title><command>menuchoice</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>menuchoice</secondary>
+ </indexterm>
+
+ <para>
+ Often using a mouse is tedious for common tasks. Therefore,
+ programmers often build in keyboard-shortcuts to simplify their
+ program. These should be described using the shortcut tag as a wrapper
+ for the keyboard tags. The shortcut tag must be wrapped inside the
+ menuchoice tag. For example:
+ </para>
+
+<screen>
+<computeroutput>
+Go to the menu bar and choose:
+ <menuchoice>
+ <shortcut>
+ <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
+ </shortcut>
+ <guimenu><accel>F</accel>ile</guimenu>
+ <guimenuitem><accel>S</accel>ave</guimenuitem>
+ </menuchoice>.
+</computeroutput>
+</screen>
+
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Go to the menu bar and choose:
+ <menuchoice>
+ <shortcut>
+ <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
+ </shortcut>
+ <guimenu><accel>F</accel>ile</guimenu>
+ <guimenuitem><accel>S</accel>ave</guimenuitem>
+ </menuchoice>.
+ </para>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-keycombo">
+ <title><command>keycombo</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>keycombo</secondary>
+ </indexterm>
+
+ <para>
+ To illustrate a key combination, you need to use the
+ <command><keycombo></command> and
+ <command></keycombo></command>,
+ <command><keycap></command> and
+ <command></keycap></command> tags. For example:
+ </para>
+<screen>
+<computeroutput>
+To reboot your system, press <keycombo>
+<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>
+</keycombo>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ To reboot your system, press
+ <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>
+ </keycombo>.
+ </para>
+
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-lists">
+ <title>Lists</title>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary>creating</secondary>
+ </indexterm>
+
+ <para>There are several types of lists you can create using XML. You
+ can have a itemized (bulleted) list, a ordered (numbered) list, or a
+ variable list (presents a term and then a separate paragraph).</para>
+
+ <para>There is also a list format for tables and for for creating a
+ list of glossary terms and their definitions.</para>
+
+ <para>The sections below will discuss the proper uses for the various
+ list and how to create them.</para>
+
+ <sect2 id="s2-xml-tags-itemizedlist">
+ <title><command>itemizedlist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>itemizedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>itemizedlist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>itemizedlist</command></secondary>
+ </indexterm>
+
+ <para>An <command>ItemizedList</command> is best used to present
+ information that is important for the reader to know, but that does
+ not need to be in a specific order. It is shorter than a
+ <command>VariableList</command> and presents the information in a
+ very simple way.</para>
+
+ <para>To create an <command>ItemizedList</command> (otherwise known as
+ bulleted list), use the following command sequence:</para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command>
+ tags. If you do not do this, you will find extra whitespace in
+ your lists where the text does not line up correctly. This is most
+ noticeable when you have a series of list items that consist of
+ multiple lines of text. This whitespace is not as noticeable in
+ the HTML output as it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<itemizedlist>
+ <listitem>
+ <para>Getting familiar with the installation program's user interface</para>
+ </listitem>
+
+ <listitem>
+ <para>Starting the installation program</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting an installation method</para>
+ </listitem>
+</itemizedlist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Getting familiar with the installation program's user interface</para>
+ </listitem>
+
+ <listitem>
+ <para>Starting the installation program</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting an installation method</para>
+ </listitem>
+ </itemizedlist>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-orderedlist">
+ <title><command>OrderedList</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>orderedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>orderedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>orderedlist</tertiary>
+ </indexterm>
+
+ <para>An <command>orderedlist</command> is best used to present
+ information that is important for the reader to know in a specific
+ order. <command>orderedlist</command>s are a good way to convey
+ step-by-step senarios to the audience you are writing for.</para>
+
+ <para>
+ To create an <command>orderedlist</command> (numbered list), use the
+ following XML code sequence:
+ </para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command>
+ tags. If you do not do this, you will find extra whitespace in
+ your lists where the text does not line up correctly. This is most
+ noticeable when you have a series of list items that consist of
+ multiple lines of text. This whitespace is not as noticeable in
+ the HTML output as it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<orderedlist>
+ <listitem>
+ <para>Online &mdash; http://www.redhat.com/support/errata; supplies errata
+ you can read online, and you can download diskette images
+ easily.</para>
+ </listitem>
+
+ <listitem>
+ <para>Email &mdash; By sending an empty mail message to errata@@redhat.com,
+ you will receive an email containing a text listing of the
+ complete errata of the installation program and related software
+ (if errata exist at that time). Also included are URLs to each
+ updated package and diskette image in the errata. Using these
+ URLs, you can download any necessary diskette images. Please
+ note: use binary mode when transferring a diskette image.</para>
+ </listitem>
+</orderedlist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <orderedlist>
+ <listitem>
+ <para>Online — http://www.redhat.com/support/errata; supplies errata
+ you can read online, and you can download diskette images
+ easily.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Email — By sending an empty mail message to
+ errata@@redhat.com, you will receive an email containing a text
+ listing of the complete errata of the installation program and
+ related software (if errata exist at that time). Also included
+ are URLs to each updated package and diskette image in the
+ errata. Using these URLs, you can download any necessary
+ diskette images. Please note: use binary mode when transferring
+ a diskette image.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-varlist">
+ <title><command>Variablelist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>variablelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>variablelist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>variablelist</command></secondary>
+ </indexterm>
+
+ <para>A <command>variablelist</command> best represents a list of
+ terms and definitions or descriptions for those terms.</para>
+
+ <para>To create a <command>variablelist</command>, use the following
+ command sequence:
+ </para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command> tags. If
+ you do not do this, you will find extra whitespace in your lists
+ where the text does not line up correctly. This is most noticeable
+ when you have a series of list items that consist of multiple lines
+ of text. This whitespace is not as noticeable in the HTML output as
+ it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<variablelist>
+ <varlistentry>
+ <term> New Multi-CD Install </term>
+ <listitem>
+ <para>As the installation program continues to grow, Red Hat has developed
+ an installation program capable of installing from
+ multiple CD-ROMs.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>XFree 4.0 </term>
+ <listitem>
+ <para>Configuration of your X Window System during the installation has
+ never been more thorough. From choosing your monitor and its correct
+ settings, to video card probing, to testing your desired X setup,
+ Xconfigurator will help you set everything just right.</para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <variablelist>
+ <varlistentry>
+ <term>New Multi-CD Install</term> <listitem> <para>As the
+ installation program continues to grow, Red Hat has developed an
+ installation program capable of installing from
+ multiple CD-ROMs.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term> XFree 4.0</term>
+ <listitem>
+ <para>Configuration of your X Window System during the
+ installation has never been more thorough. From choosing your
+ monitor and its correct settings, to video card probing, to
+ testing your desired X setup, Xconfigurator will help you set
+ everything just right.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ Do <emphasis>not</emphasis> specify the
+ <computeroutput>frame</computeroutput> attribute to the table. Doing
+ so breaks PDF production.
+ </para>
+ </warning>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-simplelist">
+ <title>Creating a List Within a Table Using <command>Simplelist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>simplelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>simplelist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>simplelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>tables</primary>
+ <secondary>creating a list within a table</secondary>
+ <tertiary><command>simplelist</command></tertiary>
+ </indexterm>
+
+ <para>A <command>simplelist</command> is an unadorned list of
+ items. <command>simplelist</command>s can be inline or arranged in
+ columns.</para>
+
+ <para>We use <command>simplelist</command> to add separate paragraphs
+ of text within a table element. A regular list, such as
+ <command>itemizedlist</command>, cannot be embedded within a table.</para>
+
+ <para>The XML commands for a table look like:</para>
+
+<screen>
+<computeroutput>
+ <table id="tb-hwinfo-hostbus">
+ <title>Host Bus Adapter Features and Configuration Requirements</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="HostBus" colwidth="33"/>
+ <colspec colnum="2" colname="Features" colwidth="34"/>
+ <colspec colnum="3" colname="Single" colwidth="33"/>
+
+ <thead>
+ <row>
+ <entry>Host Bus Adapter</entry>
+ <entry>Features</entry>
+ <entry>Single-Initiator Configuration</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is
+ off.</member>
+ </simplelist></entry>
+
+ <entry><simplelist>
+ <member>Set the onboard termination to automatic (the
+ default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ <row>
+ <entry>Qlogic QLA1080</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is off,
+ unless jumpers are used to enforce termination.</member>
+ </simplelist></entry>
+
+
+ <entry><simplelist>
+ <member>Set the onboard termination to
+ automatic (the default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <table id="tb-hwinfo-hostbus">
+ <title>Host Bus Adapter Features and Configuration Requirements</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="HostBus" colwidth="33"/>
+ <colspec colnum="2" colname="Features" colwidth="34"/>
+ <colspec colnum="3" colname="Single" colwidth="33"/>
+
+ <thead>
+ <row>
+ <entry>Host Bus Adapter</entry>
+ <entry>Features</entry>
+ <entry>Single-Initiator Configuration</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is
+ off.</member>
+ </simplelist></entry>
+
+ <entry><simplelist>
+ <member>Set the onboard termination to automatic (the
+ default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ <row>
+ <entry>Qlogic QLA1080</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is off,
+ unless jumpers are used to enforce termination.</member>
+ </simplelist></entry>
+
+
+ <entry><simplelist>
+ <member>Set the onboard termination to
+ automatic (the default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+ <note>
+ <title>Note</title>
+ <para>Notice how the <command>SimpleList</command> tags are
+ used. The <entry> and <simplelist> tags must be aligned
+ beside one another, otherwise you will receive a parsing error.</para>
+ </note>
+
+ <para>For each paragraph or list item to be added within a
+ <command>SimpleList</command>, the <member> tag set must be
+ added around that particular text item.</para>
+ </sect2>
+
+ <sect2 id="s2-xml-tags-glossary">
+ <title><command>glosslist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>glosslist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>glosslist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>glosslist</command></secondary>
+ </indexterm>
+
+ <para>Use the <command>glosslist</command> command set to create a
+ list of glossary terms and their definitions.</para>
+
+
+ <para>In XML, an example looks like the following:</para>
+
+<screen>
+<computeroutput>
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>A small application, usually a utility or other
+ simple program.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>The design for organization and integration of
+ components within a computer or computer system.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>To transfer files into storage for the purpose of
+ saving space and/or organization.</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+</computeroutput>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>A small application, usually a utility or other simple program.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>The design for organization and integration of components
+ within a computer or computer system.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>To transfer files into storage for the purpose of saving
+ space and/or organization.</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+
+ </sect2>
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-option">
+ <title><command>option</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>option</secondary>
+ </indexterm>
+
+ <para>If you have a command that offers an option or a flag, use the
+ <command><option></command> and
+ <command></option></command> tags.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>The <option> tag set is only meant to be used for command
+ line options, not options in configuration files.</para>
+ </note>
+
+ <para>In XML, specifying an option would look like the
+ following:</para>
+
+<screen>
+<computeroutput>
+For example, with the command <command>ls</command> you can
+specify an option such as <option>-la</option>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>For example, with the command <command>ls</command> you can
+ specify an option such as <option>-la</option>.</para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-indexing">
+ <title>Index Entries</title>
+
+ <indexterm>
+ <primary>indexing</primary>
+ </indexterm>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>indexing</secondary>
+ </indexterm>
+
+ <para>The following command sequence shows you the code inserted into
+ the body of the text to add an index entry to your document:
+ </para>
+
+<screen>
+<computeroutput>
+<indexterm> <-- indicates a term to be placed in the index
+<primary>foo</primary> <-- indicates that "foo" is the first term
+<secondary>bar</secondary> <-- "bar" will be listed under "foo"
+</indexterm> <-- closes this index entry
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>foo</primary>
+ <secondary>bar</secondary>
+ </indexterm>
+
+
+ <para>The <command><seealso></command> tag allows you to
+ reference another index entry or refer to another manual. Make sure
+ the <command><seealso></command> reference you are pointing to
+ has its own entry. For example:
+ </para>
+
+ <indexterm>
+ <primary>indexing</primary>
+ <secondary>seealso tag</secondary>
+ </indexterm>
+
+<screen>
+<computeroutput>
+<indexterm>
+<primary>SWAK</primary>
+<seealso>salutations</seealso>
+</indexterm>
+
+
+<indexterm>
+<primary>salutations</primary>
+</indexterm>
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>SWAK</primary>
+ <seealso>Salutations</seealso>
+ </indexterm>
+
+ <indexterm>
+ <primary>Salutations</primary>
+ </indexterm>
+
+ <para>
+ The <command><see></command> tag allows you to reference to
+ another index entry entirely. For example:
+ </para>
+ <indexterm>
+ <primary>indexing</primary>
+ <secondary>see tag</secondary>
+ </indexterm>
+
+
+<screen>
+<computeroutput>
+<indexterm>
+<primary>Guinness</primary>
+<see>beer</see> <-- beer will be listed under
+the Guinness entry, but you must make sure beer also has its
+own entry to refer to.
+</indexterm>
+
+<indexterm>
+<primary>beer</primary>
+</indexterm>
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>Guinness</primary>
+ <see>Beer</see>
+ </indexterm>
+
+ <indexterm>
+ <primary>Beer</primary>
+ </indexterm>
+
+ <para>To view the HTML output of the index entries shown here, refer
+ to the <filename>generated-index.html</filename> file at the end of
+ this document.</para>
+
+ <para>How does the index get generated? If indexterms exist in the
+ document and the beginning and ending index tags exist before the end
+ tag for the book or article, an index is created because of the
+ <command>generate.index</command> stylesheet parameter, which is set to
+ true by default.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-para">
+ <title><command>para</command></title>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>para</secondary>
+ </indexterm>
+
+ <para>For any paragraph, the <command><para></command> and
+ <command></para></command> tags must open and close that
+ particular paragraph.
+ </para>
+
+ <para>Do not use para tags around anything other than a simple
+ paragraph. Doing so will create additional white space within
+ the text itself.</para>
+
+ <para>Do not use <command><para></command> tags around the
+ following (or, to put this another way, do not embed the
+ following within <command><para></command> tags):</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><command><screen></command></para>
+ </listitem>
+ <listitem>
+ <para><command><itemizedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><orderedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><variablelist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><table></command></para>
+ </listitem>
+ </itemizedlist>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-part">
+ <title><command>part</command></title>
+
+ <indexterm>
+ <primary>parts</primary>
+ </indexterm>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>part</secondary>
+ </indexterm>
+
+ <para>
+ In the parent file, you can separate the chapters into parts to divide
+ them into logical groups. For example, in the parent file, the
+ <command>part</command> tags surround the chapter entities:
+ </para>
+<screen>
+<computeroutput>
+<part id="pt-foo">
+ <partintro>
+ <para>Some text for the part intro</para>
+ &CHAPTER;
+
+ &ANOTHER-CHAPTER;
+</part>
+</computeroutput>
+</screen>
+
+ <para>
+ If you create a part, include a part introduction describing the
+ contents of the part. For example:
+ </para>
+
+<screen>
+<computeroutput>
+ <part id="pt-setup">
+ <title>Getting Setup</title>
+ <partintro>
+ <para>This section contains information you will need when you first join
+ the Docs group. You might need to refer to this part again for
+ information such as installing &FC;.</para>
+ </partintro>
+</computeroutput>
+</screen>
+
+ <para>
+ In the HTML output, a separate HTML page is generated with the part
+ number, title, introduction, and TOC. In the PDF output, the same
+ information about the part is on a separate page.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-prompt">
+ <title><command>prompt</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>prompt</secondary>
+ </indexterm>
+
+ <para>
+ To show a prompt, such as a root or DOS prompt, use the
+ <command><prompt></command> and <command></prompt></command>
+ commands. For example:
+ </para>
+<screen>
+<computeroutput>
+At the <prompt>LILO:</prompt> boot prompt, type linux to
+boot into your Linux partition.
+
+At the <prompt>C:\></prompt> prompt, type ....
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ At the <prompt>LILO:</prompt> boot prompt, type linux to boot into your
+ Linux partition.
+ </para>
+ <para>
+ At the <prompt>C:\></prompt> prompt, type ....
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ When showing example computer output (usually in
+ <command>screen</command> tags), do not include the prompt or command
+ (unless the command or prompt is the actually computer output you want
+ to show).</para>
+ </note>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-replaceable">
+ <title><command>replaceable</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>replaceable</secondary>
+ </indexterm>
+
+ <para>
+ To create replaceable text, use the tags
+ <command><replaceable></command> and
+ <command></replaceable></command> around the text you want to use as a
+ variable.
+ </para>
+ <para>
+ This example demonstrates how to use the <command>replaceable</command>
+ tags when referencing the name of an RPM file:
+ </para>
+<screen>
+foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+<screen>
+foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm
+</screen>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-screen">
+ <title><command>screen</command></title>
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>screen</secondary>
+ </indexterm>
+
+ <para>
+ The <command><screen></command> command is used to format text
+ within a document and is great for adding emphasis to show examples of
+ code, computer output, and more. In HTML with the Fedora CSS file, this
+ appears in box with a grey background. To use this command you only need
+ the opening <command><screen></command> and closing
+ <command></screen></command> tags around the text you are
+ emphasizing.
+ </para>
+
+ <important>
+ <title>Important</title>
+ <para>
+ When using the <command><screen></command> tag, you must set
+ everything within that screen, including the
+ <command><screen></command> tags themselves, to flush left. This
+ must be done so that when it is converted to HTML, it will not have
+ extra blank space in front of it inside the gray background.
+ </para>
+ </important>
+
+ <para>
+ The <command><screen></command> tag set may contain other inline
+ tags, such as <command><computeroutput></command>,
+ <command><userinput></command>, or
+ <command><replaceable></command>. Additional inline tags are not
+ required by definition. The <command><screen></command> tags by
+ themselves may provide sufficient context, especially for simple examples
+ or file listings. Consider the context of the example, and use inline tags
+ if they are helpful to the reader.
+ </para>
+
+ <para>
+ If you use inline tags, remember that line breaks inside
+ <command><screen></command> tags create line breaks in any rendered
+ output. Place any inline tags <emphasis>on the same line</emphasis> as
+ their content. Do not overuse tagging within a
+ <command><screen></command> tag set.
+ </para>
+
+ <para>
+ An example of <command><screen></command> is the following:
+ </para>
+
+<screen>
+<computeroutput><screen>
+This is an example of a screen. You do not need &lt;para&gt; tags
+within this command.
+</screen></computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+<screen>
+This is an example of a screen. You do not need <para> tags
+within this command.
+</screen>
+
+ <sect2 id="s2-xml-tags-screen-inline-tags">
+ <title>Using Inline Tags with <command>screen</command></title>
+ <para>
+ If you choose to use inline tags inside a
+ <command><screen></command> section, follow these guidelines for
+ consistency. If the content in the screen is a listing of a
+ configuration file or the output of a program, use the
+ <command><computeroutput></command> tag set around the entire
+ output. If the user should type the example on the command line or in
+ a configuration file, use the <command><userinput></command> tag
+ set. Separate input and output with a short sentence of narrative, as
+ below:
+ </para>
+
+<screen>
+ <command><para></command>
+ Type the following command:
+ <command></para></command>
+
+<command><screen></command>
+<command><userinput></command>command -sw file1<command></userinput></command>
+<command></screen></command>
+
+ <command><para></command>
+ You should see the following output:
+ <command></para></command>
+
+<command><screen></command>
+<command><computeroutput></command>Completed, time = 0.12 sec<command></computeroutput></command>
+<command></screen></command>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <para>
+ Type the following command:
+ </para>
+
+<screen>
+<userinput>command -sw file1</userinput>
+</screen>
+
+ <para>
+ You should see the following output:
+ </para>
+
+<screen>
+<computeroutput>Completed, time = 0.12 sec</computeroutput>
+</screen>
+
+ <note>
+ <title>Note</title>
+ <para>
+ When showing a command or series of commands inside
+ <command>screen</command> tags, do not show the prompt.
+ </para>
+ </note>
+
+ <para>
+ If the <command><screen></command> shows the reader how to
+ change only <emphasis>part</emphasis> of a line, mark the change with
+ an inline <command><userinput></command> tag set. You may use
+ the <command><userinput></command> tag set inside a larger area
+ that is already marked inline with
+ <command><computeroutput></command>. Do not include any extra
+ lines of context in this case, unless excluding them would confuse the
+ reader. The following example illustrates these guidelines:
+ </para>
+
+<screen>
+ <command><para></command>
+ Edit the <command><filename></command>/etc/sysconfig/init<command></filename></command> file as follows:
+ <command></para></command>
+
+<command><screen></command>
+GRAPHICAL=<command><userinput></command>yes<command></userinput></command>
+<command></screen></command>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <para>
+ Edit the <filename>/etc/sysconfig/init</filename> file as follows:
+ </para>
+
+<screen>
+GRAPHICAL=<userinput>yes</userinput>
+</screen>
+
+ <para>
+ For an explanation of how to use the <command>replaceable</command>
+ tags within a set of <command>screen</command> tags, refer to <xref
+ linkend="s1-xml-tags-replaceable"></xref>.
+ </para>
+
+ </sect2>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-sections">
+ <title>Sections</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>sections</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>sections</primary>
+ </indexterm>
+
+ <para>Within an article (or chapter if it is a DocBook XML book like the
+ <citetitle>&IG;</citetitle>), you can have sections and
+ subsections. <command><sect1></command> is always the highest
+ section and you cannot have two sections of the same level within one
+ another (a section 2 can be created within a section 1, but section 1
+ has to be closed before another section 1 can be created). The general
+ layout follows:</para>
+
+<screen>
+<computeroutput>
+<sect1 id="s1-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+
+ <sect2 id="s2-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+ <sect3 id="s3-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+ </sect3>
+
+ </sect2>
+
+</sect1>
+</computeroutput>
+</screen>
+
+ <para>
+ If you only need one level of sections in a DocBook article, you can use
+ the <command>section</command> tag. For example:
+ </para>
+
+<screen>
+<computeroutput>
+<section id="sn-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+</section>
+<section id="sn-anothername">
+ <title>Insert Title Here</title>
+ <para>
+ More body text goes here.
+ </para>
+</section>
+</computeroutput>
+</screen>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-table">
+ <title><command>table</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>table</secondary>
+ </indexterm>
+
+ <para>
+ The following is an example of creating a table.
+ </para>
+
+<screen>
+<table id="tb-mockup-before-begin">
+ <emphasis>This tells XML that you will be creating a table
+ and the ID name is <command>"tb-mockup-before-begin."</command></emphasis>
+
+<title>Available Features of GNOME and KDE</title>
+
+<tgroup cols="3">
+ <emphasis>This tells XML that you are creating a table
+ with three columns.</emphasis>
+
+<colspec colnum="1" colname="Features" colwidth="3"/>
+ <emphasis><command>colspec</command> says that you are giving information
+ about the column to XML</emphasis> <emphasis><command>colnum="1"</command>
+ says that you are giving specifications for the first column.</emphasis>
+
+ <emphasis><command>colname="Features"</command> says that the title for this
+ column will be "Features."</emphasis>
+
+ <emphasis><command>colwidth="3"</command> specifies the width of the
+ column. This can be more tricky: such as two columns with
+ widths of 1 and 2,the 1 is one-half the width of the 2, in
+ respect to the page size. But, what if you need the 1 to be a
+ little more than half of the 2, using a larger number ratio,
+ such as 10 to 20 would accomplish this. You could then change the
+ 10 to an 11 or a 12 to make it a little more than half of the
+ second column of 20. In no value is given, a value of 1 is
+ assumed.</emphasis>
+
+<colspec colnum="2" colname="GNOME" colwidth="2"/>
+<colspec colnum="3" colname="KDE" colwidth="2"/>
+
+<thead>
+ <emphasis>Contains one or more table row elements.</emphasis>
+
+<row>
+ <emphasis>Contains one or more table cell (entry) elements.</emphasis>
+
+<entry>Features</entry>
+ <emphasis>Table cell element, one of several in a row element, defining
+ columns within the row.</emphasis>
+
+<entry>GNOME</entry>
+<entry>KDE</entry>
+</row>
+</thead>
+
+<tbody>
+ <emphasis>Contains one or more row elements, for the main text
+ of the table.</emphasis>
+
+<row>
+<entry>highly configurable</entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>multiple window managers </entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>Internet applications</entry>
+<entry>yes </entry>
+<entry>yes </entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+</screen>
+
+ <table id="tb-mockup-before-begin">
+ <title>Available Features of GNOME and KDE</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="Features" colwidth="3"/>
+ <colspec colnum="2" colname="GNOME" colwidth="2"/>
+ <colspec colnum="3" colname="KDE" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Features </entry>
+ <entry>GNOME</entry>
+ <entry>KDE</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry>highly configurable</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>multiple window managers </entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>Internet applications</entry>
+ <entry>yes </entry>
+ <entry>yes </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <sect2 id="s2-xml-tags-listintable">
+ <title>Creating a List Within a Table</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>table</secondary>
+ <tertiary>list within a table</tertiary>
+ </indexterm>
+
+
+ <para>Creating a list within a table can be a difficult task. It
+ requires strict formatting and a set of commands that are not
+ available for command completion in
+ <application>Emacs</application>.</para>
+
+ <para>The tags you will need to use are
+ <command><simplelist></command> and
+ <command><member></command>.</para>
+
+ <para>The following example will show you the proper formatting for
+ creating a list within a table.</para>
+
+
+<screen>
+<computeroutput>
+<table id="tb-hardware-powerswitch">
+ <title>Power Switch Hardware Table</title>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="Hardware" colwidth="2"/>
+ <colspec colnum="2" colname="Quantity" colwidth="2"/>
+ <colspec colnum="3" colname="Description" colwidth="6"/>
+ <colspec colnum="4" colname="Required" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>Description</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Serial power switches</entry>
+
+ <entry>Two</entry>
+
+ <entry><simplelist> <member>Power switches enable each cluster system
+ to power-cycle the other cluster system. Note that clusters are
+ configured with either serial or network attached power switches and
+ not both.</member>
+
+ <member>The following serial attached power switch has been
+ fully tested:</member>
+
+ <member>RPS-10 (model M/HD in the US, and model M/EC in
+ Europe) </member>
+
+ <member>Latent support is provided for the following serial
+ attached power switch. This switch has not yet been fully
+ tested:</member>
+
+ <member>APC Serial On/Off Switch (partAP9211), <ulink
+ url="http://www.apc.com/">http://www.apc.com/</ulink></member>
+ </simplelist></entry>
+
+ <entry>Strongly recommended for data integrity under all failure
+ conditions</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+</table>
+</computeroutput>
+</screen>
+
+ <para>Notice how the <command><simplelist></command> tag must be
+ beside the <command><entry></command> tag? If you do not format
+ this properly, it will not parse cleanly.</para>
+
+ <para>The above example will look like the following:</para>
+
+ <table id="tb-hardware-powerswitch">
+ <title>Power Switch Hardware Table</title>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="Hardware" colwidth="2"/>
+ <colspec colnum="2" colname="Quantity" colwidth="2"/>
+ <colspec colnum="3" colname="Description" colwidth="6"/>
+ <colspec colnum="4" colname="Required" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>Description</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Serial power switches</entry>
+
+ <entry>Two</entry>
+
+ <entry><simplelist> <member>Power switches enable each cluster
+ system to power-cycle the other cluster system. Note
+ that clusters are configured with either serial or
+ network attached power switches and not both.</member>
+
+ <member>The following serial attached power switch has been
+ fully tested:</member>
+
+ <member>RPS-10 (model M/HD in the US, and model M/EC in
+ Europe) </member>
+
+ <member>Latent support is provided for the following
+ serial attached power switch. This switch has not yet
+ been fully tested:</member>
+
+ <member>APC Serial On/Off Switch (partAP9211), <ulink
+ url="http://www.apc.com/">http://www.apc.com/</ulink></member>
+ </simplelist></entry>
+
+ <entry>Strongly recommended for data integrity under all failure
+ conditions</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-trademark">
+ <title><command>trademark</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>trademark</command></secondary>
+ </indexterm>
+
+
+ <para>Do not use the trademark entities &trade;, &copy;, or
+ &reg; because the do not produce HTML output that works for all
+ charsets. The HTML output produces by these entities are declared in
+ the DTD and cannot be changed via the stylesheet.</para>
+
+ <para>Instead, use the <command>trademark</command> tag and its
+ associates classes as follows:
+ </para>
+
+<screen>
+<computeroutput>
+<trademark>trademark symbol after me</trademark>
+<trademark class="registered">registered trademark symbol after me</trademark>
+<trademark class="copyright">copyright symbol after me</trademark>
+</computeroutput>
+</screen>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-userinput">
+ <title><command>userinput</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>userinput</command></secondary>
+ </indexterm>
+
+ <para>
+ To show what a user would type, use the <command>userinput</command>
+ tag. For example:
+ </para>
+<screen>
+<computeroutput>
+At the prompt, type:
+
+<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ At the prompt, type:
+ </para>
+
+ <para>
+ <userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+ </para>
+ </sect1>
+
+
+<!-- <sect1 id="s1-xml-tags-mouse">
+ <title><command>mousebutton</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>mousebutton</secondary>
+ </indexterm>
+ <para>
+Describe mouse actions with the mousebutton tag. Below is an example of its use.
+</para>
+
+<screen>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+</screen>
+
+ <para>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+ </para>
+
+ </sect1> -->
+
+ <sect1 id="s1-xml-tag-sulink">
+ <title><command>ulink</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>ulink</secondary>
+ </indexterm>
+
+ <para>
+ To create a URL link within your text, use the following example:
+ </para>
+<screen>
+<computeroutput>
+Online &mdash; <ulink url="http://www.redhat.com/support/errata/">
+http://www.redhat.com/support/errata/</ulink>; supplies errata
+you can read online, and you can download diskette images easily.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Online — <ulink url="http://www.redhat.com/support/errata/">
+ http://www.redhat.com/support/errata/</ulink>; supplies errata
+ you can read online, and you can download diskette images easily.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ If the URL does not end in a filename, it must end in a slash
+ (<computeroutput>/</computeroutput>) to be a properly formed URL. For
+ example, <ulink
+ url="http://www.redhat.com/">http://www.redhat.com/</ulink>.
+ </para>
+ </note>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-wordasword">
+ <title><command>wordasword</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>wordasword</secondary>
+ </indexterm>
+
+ <para>The <wordasword> tag set is used to define a word meant
+ specifically as a word and not representing anything else.</para>
+
+ <para>A lot of technical documentation contains words that have overloaded
+ meanings. Sometimes it is useful to be able to use a word without invoking
+ its technical meaning. The <wordasword> element identifies a word or
+ phrase that might otherwise be interpreted in some specific way, and
+ asserts that it should be interpreted simply as a word.</para>
+
+ <para>It is unlikely that the presentation of this element will be able to
+ help readers understand the variation in meaning; good writing will have
+ to achieve that goal. The real value of <wordasword> lies in the
+ fact that full-text searching and indexing tools can use it to avoid
+ false-positives.</para>
+
+ <para>For example:</para>
+
+<screen>
+<computeroutput>To use <command>grep</command> to search for the word
+<wordasword>linux</wordasword>, use the command
+<command>grep linux</command>.</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>To use <command>grep</command> to search for the word
+ <wordasword>linux</wordasword>, use the command <command>grep
+ linux</command>.</para>
+
+ <para>In the example, the word "linux" is just a word. It is not
+ meant to convey anything about Linux as a subject, or to add relevance or
+ meaning to the content. It can be replaced with any other word without
+ losing any of the context.</para>
+
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-xref">
+ <title><command>xref</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>xref</secondary>
+ </indexterm>
+
+ <para>
+ To refer to other sections or chapters within a manual, use the
+ <command><xref></command> tag.
+ </para>
+
+ <para>
+ The output of this displays the title of the section or chapter you are
+ pointing the user to. For example:
+ </para>
+<screen>
+<computeroutput>
+For more information about the parent file, refer to
+<xref linkend="ch-tutorial"></xref> and <xref linkend="s1-tutorial-parent"></xref>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ For more information about the parent file, refer to <xref linkend="ch-tutorial"></xref>
+ and <xref linkend="s1-tutorial-parent"></xref>.
+ </para>
+ </sect1>
+
+ </chapter>
+@
+
+
+1.12
+log
+ at fix missing end tag per bug #134202
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.11 2004/09/13 02:02:12 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.11 2004/09/13 02:02:12 tfox Exp $ -->
+@
+
+
+1.11
+log
+ at more explanation of screen tag per bug #131647, tweak replaceable entry
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.10 2004/08/31 15:46:17 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.10 2004/08/31 15:46:17 tfox Exp $ -->
+d2477 1
+a2477 1
+<xref linkend="ch-tutorial"><xref> and <xref linkend="s1-tutorial-parent"></xref>
+@
+
+
+1.10
+log
+ at add link to screenshot section
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.9 2004/08/13 16:08:48 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.9 2004/08/13 16:08:48 tfox Exp $ -->
+d1750 1
+a1750 1
+ <command>screen</command> tags), do you include the prompt or command
+d1765 1
+a1765 1
+ To create replaceable text, you use the tags
+d1771 2
+a1772 1
+ This example shows the ISBN of our boxed sets with variables:
+d1775 1
+a1775 3
+<computeroutput>
+1-58569-<replaceable>xx</replaceable>-<replaceable>y</replaceable>
+</computeroutput>
+d1782 3
+a1784 3
+ <para>
+ 1-58569-<replaceable>xx</replaceable>-<replaceable>y</replaceable>
+ </para>
+d1794 12
+d1807 5
+a1811 7
+ The <command><screen></command> command is used to format text
+ within a document and is great for adding emphasis to show examples of
+ code, computer output, and more. In HTML, this appears in a grey
+ background. To use this command you only need the opening
+ <command><screen></command> and closing
+ <command></screen></command> tags around the text you are
+ emphasizing.
+d1813 1
+d1815 18
+a1832 8
+ <important>
+ <title>Important</title> <para>When using the
+ <command><screen></command> tag, you must set everything within
+ that screen, including the <command><screen></command> tags
+ themselves, to flush left. This must be done so that when it is
+ converted to HTML, it will not have extra blank space in front of it
+ inside the gray background.</para>
+ </important>
+d1834 3
+a1837 3
+ <para>
+ An example of <command><screen></command> is the following:
+ </para>
+d1839 2
+a1840 4
+<computeroutput>
+<screen>
+<computeroutput>
+This is an example of a screen. You do not need <para> tags
+d1842 1
+a1842 3
+</computeroutput>
+</screen>
+</computeroutput>
+d1845 11
+d1857 9
+a1865 1
+ The output:
+d1869 15
+a1883 4
+<computeroutput>
+This is an example of a screen. You do not need <command><para></command>
+tags within this command.
+</computeroutput>
+d1886 8
+a1893 9
+ <note>
+ <title>Note</title> <para>To properly use the
+ <command><screen></command> tag set, you also need to properly
+ tag the content within the screen. If the content in the screen is a
+ configuration file or the output of a program, it needs the
+ <command><computeroutput></command> tag set. If it is a command,
+ it needs the <command><command></command> tag set. If it is a
+ command with user input, it may require a construction like the one
+ below:</para>
+d1895 1
+a1895 1
+<command><command></command>command <command><userinput></command>input<command></userinput></command><command></command></command>
+d1899 1
+a1899 1
+ The output looks like:
+d1903 1
+a1903 1
+<command>command <userinput>input</userinput></command>
+d1905 7
+d1914 40
+@
+
+
+1.9
+log
+ at use common entities file
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.8 2004/08/12 21:33:45 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.8 2004/08/12 21:33:45 tfox Exp $ -->
+d625 6
+@
+
+
+1.8
+log
+ at remove rule about justifying para tags inspired by bug #125754
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.7 2004/08/12 21:07:03 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.7 2004/08/12 21:07:03 tfox Exp $ -->
+d514 1
+a514 1
+partitions</firstterm>, and &DISTRO; is no exception.
+d524 1
+a524 1
+ partitions</firstterm>, and &DISTRO; is no exception.
+d1693 1
+a1693 1
+ information such as installing &DISTRO;.</para>
+@
+
+
+1.7
+log
+ at change redhat- to system- per bug #123267
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.6 2004/08/12 21:01:19 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.6 2004/08/12 21:01:19 tfox Exp $ -->
+d1623 3
+a1625 19
+ <sect2 id="s2-xml-tags-para">
+ <title>Additional Rules for the <command><para></command> Tag
+ Set</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>para</secondary>
+ <tertiary>additional rules</tertiary>
+ </indexterm>
+
+ <variablelist>
+ <varlistentry>
+ <term>Proper formatting of <command><para></command> tag and
+ text</term>
+ <listitem>
+ <para>Additionally, the <command><para></command> tags
+ should be justified around the paragraph so that the opening
+ <command><para></command> tag and the first word of that
+ paragraph are side by side. For example:</para>
+d1627 3
+a1629 6
+<screen>
+<computeroutput>
+<para>This paragraph demonstrates using the <para>
+tag correctly.<para>
+</computeroutput>
+</screen>
+d1631 17
+a1647 36
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Where not to use <command><para></command> tags</term>
+ <listitem>
+ <para>Do not use para tags around anything other than a simple
+ paragraph. Doing so will create additional white space within
+ the text itself.</para>
+
+ <para>Do not use <command><para></command> tags around the
+ following (or, to put this another way, do not embed the
+ following within <command><para></command> tags):</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><command><screen></command></para>
+ </listitem>
+ <listitem>
+ <para><command><itemizedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><orderedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><variablelist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><table></command></para>
+ </listitem>
+ </itemizedlist>
+
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect2>
+@
+
+
+1.6
+log
+ at forgot to remove all command tags
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.5 2004/08/12 20:49:58 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.5 2004/08/12 20:49:58 tfox Exp $ -->
+d476 1
+a476 1
+<filename>redhat-config-keyboard</filename> RPM package must be installed.
+@
+
+
+1.5
+log
+ at package names should be in filename tags
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.4 2004/08/12 20:48:40 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.4 2004/08/12 20:48:40 tfox Exp $ -->
+d1645 2
+a1646 2
+<para></command>This paragraph demonstrates using the <para>
+tag correctly.<command><para>
+@
+
+
+1.4
+log
+ at fix grammar per bug #123258
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.3 2004/02/24 21:30:14 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.3 2004/02/24 21:30:14 tfox Exp $ -->
+d476 1
+a476 1
+<command>redhat-config-keyboard</command> RPM package must be installed.
+@
+
+
+1.3
+log
+ at remove comment
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.2 2003/10/15 18:11:01 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags-en.xml,v 1.2 2003/10/15 18:11:01 tfox Exp $ -->
+d1645 2
+a1646 2
+<command><para></command>This paragraph talk about using the <para>
+tag correctly.<command><para></command>
+@
+
+
+1.2
+log
+ at fix example figure tag, add ack chapter
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+d1600 5
+a1604 6
+<!--
+ <tip>
+ <title>Tip</title>
+ <para>
+ To learn more about the rules of indexing, refer to <xref
+ linkend="ch-indexing"></xref>.
+d1606 1
+a1606 2
+ </tip>
+-->
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags.xml,v 1.4 2003/09/16 19:26:26 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags.xml,v 1.4 2003/09/16 19:26:26 tfox Exp $ -->
+d594 1
+a594 1
+ format="eps">
+d598 1
+a598 1
+ format="png">
+d601 1
+a601 1
+ <para>
+d603 1
+a603 1
+ </para>
+d623 1
+a623 1
+<para>Some text description of this image</para> <emphasis>==> "Some text..." would be edited</emphasis>
+@
+
diff --git a/old-documentation-guide/Attic/docs-xml-tags-zh_CN.xml,v b/old-documentation-guide/Attic/docs-xml-tags-zh_CN.xml,v
new file mode 100644
index 0000000..b1e1777
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-xml-tags-zh_CN.xml,v
@@ -0,0 +1,1669 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.17.13.28.38; author bbbush; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id: docs-xml-tags-zh_CN.xml,v 1.2 2005/12/17 13:28:38 bbbush Exp $ --><chapter id="ch-xml-tags">
+ <title>DocBook XML 标记</title>
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>标记</secondary>
+ <see>XML 标记</see>
+ </indexterm>
+ <para>请仔细阅读这一章。这一章描述了 Docs Project 使用的标记。一些规则是 Docs Project 特定的。</para>
+ <para>如果这些标记运用合适，搜索文档时可以得到有意义的结果。这些标记帮助搜索引擎确认与搜索条件相关的信息。另一个好处是使 &PROJECT; 文档拥有相同的外观。(不过，由于输出格式不同，外观仍然会有一些区别。)</para>
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>标记概要</secondary>
+ </indexterm>
+ <para>XML 中所有标记必须有开标记和闭标记。另外，按照惯例，章、节、图象、表格等必须有唯一的标识符，这样可以被正确标识，需要的话也可以交叉引用。</para>
+ <para>尽管 XML 可以处理很多文档形式，这里介绍的只是 article 一种。</para>
+ <para>本章只介绍 &PROJECT; 文档使用的标记，并不是所有可用的 DocBook XML 标记。完整的列表请参考：</para>
+ <screen>
+ <computeroutput>
+ <ulink url="http://www.docbook.org/tdg/en/html/docbook.html">http://www.docbook.org/tdg/en/html/docbook.html</ulink>
+ </computeroutput>
+ </screen>
+ <sect1 id="s1-xml-tags-caveats">
+ <title>标记和实体警告</title>
+ <indexterm>
+ <primary>xml 标记</primary>
+ <secondary>警告</secondary>
+ </indexterm>
+ <para>应当牢记本节的警告。它们比有效的 DocBook XML 更加严格，这些规则的存在，是为了使 HTML 和 PDF 输出看起来更合适。</para>
+ <variablelist>
+ <varlistentry>
+ <term>不要使用商标实体</term>
+ <listitem>
+ <para>不要使用商标实体 &trade;, &copy;, 或 &reg; 因为它们无法为所有字符集产生 HTML 输出。这些实体产生的 HTML 输出定义在 DTD 中，无法通过样式表改变。</para>
+ <para>应当使用 <command>trademark</command> 标记以及相关类别，如下所示：</para>
+ <itemizedlist>
+ <listitem>
+ <para><trademark>其后是商标符号</trademark></para>
+ </listitem>
+ <listitem>
+ <para><trademark class="registered">其后是注册商标符号</trademark></para>
+ </listitem>
+ <listitem>
+ <para><trademark class="copyright">其后是版权符号</trademark></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <command>para</command> 标记中的内容</term>
+ <listitem>
+ <para>除非是文本段落，否则不要使用 <command>para</command>。这个标记在 PDF 中，会使其间的文本包含多余的空白。</para>
+ <para>特别的，在下列标记之外不要使用 <command>para</command> (换句话说，不要把下列标记包含在 <command>para</command> 中)：</para>
+ <itemizedlist>
+ <listitem>
+ <para><screen></para>
+ </listitem>
+ <listitem>
+ <para><itemizedlist></para>
+ </listitem>
+ <listitem>
+ <para><orderedlist></para>
+ </listitem>
+ <listitem>
+ <para><variablelist></para>
+ </listitem>
+ <listitem>
+ <para><table></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>包含在 <command>para</command> 标记中的 <command>listitem</command></term>
+ <listitem>
+ <para>包含在 <command>para</command> 中的 <command>listitem</command> 标记 <emphasis>必须</emphasis> 紧挨 <para> 的开始标记，以避免 PDF 中的多余空白。</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>包含在 <command>screen</command> 标记中的内容</term>
+ <listitem>
+ <para>XML 文件中，<command>screen</command> 标记 (<screen> 和 </screen>) <emphasis>必须</emphasis> 靠左对齐，<command>screen</command> 包含的内容必须同样靠左对齐，除非有意留出空白。否则，多余的空白将出现在 HTML 中。</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect1>
+ <sect1 id="s1-xml-tags-application">
+ <title>
+ <command>application</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>application</secondary>
+ </indexterm>
+ <para>application 是图形界面应用程序的名字。command 是一个可执行的程序，或者运行应用程序的命令。</para>
+ <para>
+ <command><application></command> 和 <command></application></command> 标记使您可以引用应用程序。例如，下面的 XML：</para>
+ <screen>
+ <computeroutput>
+要在 Linux 中访问 Web，您可以使用
+<application>Mozilla</application> 或
+<application>lynx</application>，如果您只需要字符界面的话。
+</computeroutput>
+ </screen>
+ <para>产生如下输出：</para>
+ <para>要在 Linux 中访问 Web，您可以使用
+<application>Mozilla</application> 或
+<application>lynx</application>，如果您只需要字符界面的话。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-chapter">
+ <title>
+ <command>chapter</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>chapter</secondary>
+ </indexterm>
+ <para>一篇 DocBook 文档可以划分为多章，类似：</para>
+ <screen>
+ <computeroutput>
+ <chapter id="ch-sample">
+ <title>示例章</title>
+
+ <para>这是示例章，显示了用于创建章、节和小节的 XML 标记。</para>
+
+ </chapter>
+</computeroutput>
+ </screen>
+ <para>chapter 还可以进一步划分为节 (<command>sect1</command>, <command>sect2</command>, <command>sect3</command> 等等)。请参考 <xref linkend="s1-xml-tags-sections"/>。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-citetitle">
+ <title>
+ <command>citetitle</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>citetitle</secondary>
+ </indexterm>
+ <para>
+ <command><citetitle></command>标记用来格式化一个特别的引用 (引用标题可以自行输入，也可以使用实体<footnote><para>实体是引用其他手册或教程的快捷方式。它可以在主控文档中定义，对于特定的文档集合，也可以在 DTD 引用的文件中定义。</para></footnote>，如果在文档中已经定义的话)。</para>
+ <para>例如：</para>
+ <screen>
+ <computeroutput>
+<citetitle>IG;</citetitle>.
+</computeroutput>
+ </screen>
+ <para>输出类似于 <citetitle>&IG;</citetitle>，因为 &IG; 是已定义的实体。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-command">
+ <title>
+ <command>command</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>command</secondary>
+ </indexterm>
+ <para>application 是图形界面应用程序的名字。command 是一个可执行的程序，或者运行应用程序的命令。任何命令行程序，或是只有字符界面的工具都应以 <command>command</command> 标记。</para>
+ <para>如果某些文本是一个命令，那就用 <command><command></command> 和 <command></command></command> 标记：</para>
+ <screen>
+ <computeroutput>
+要在安装后改变键盘设置，切换为 root 并使用 <command>redhat-config-keyboard</command> 命令，或者在 root 提示符下输入 <command>setup</command>。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>要在安装后改变键盘设置，切换为 root 并使用 <command>redhat-config-keyboard</command> 命令，或者在 root 提示符下输入 <command>setup</command>。</para>
+ <para>另一个例子：</para>
+ <screen>
+ <computeroutput>
+<command>MAILNOVIOLATIONS</command> — 如果设置为 <command>true</command>，这个选项使得 Tripwire 定时发送邮件报告，无论是否出现了越权操作。默认值是 <command>true</command>。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>
+ <command>MAILNOVIOLATIONS</command> — 如果设置为 <command>true</command>，这个选项使得 Tripwire 定时发送邮件报告，无论是否出现了越权操作。默认值是 <command>true</command>。</para>
+ <note>
+ <title>注意</title> <para>本例中，选项值 (true) 被标记为 <command>。由于选项是出现在配置文件中的，(命令行选项应当使用 <option> 标记，)并且由于没有为配置文件选项定义什么标记，我们约定使用 <command> 标记配置文件中的选项。</para></note>
+ <para>名词也标记为 <command>command</command>，因为没有其他合适的标记：</para>
+ <itemizedlist>
+ <listitem>
+ <para>配置文件中的选项，类似 Apache 指令</para>
+ </listitem>
+ <listitem>
+ <para>守护进程名称</para>
+ </listitem>
+ </itemizedlist>
+ </sect1>
+ <sect1 id="s1-xml-tags-compoutput">
+ <title>
+ <command>computeroutput</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>computeroutput</secondary>
+ </indexterm>
+ <para>要显示屏幕输出，使用这个标记：</para>
+ <screen>
+ <computeroutput>
+<computeroutput>您是否要删除文件? y n</computeroutput>
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>
+ <computeroutput>您是否要删除文件? y n</computeroutput>
+ </para>
+ </sect1>
+ <sect1 id="s1-xml-tags-emphasis">
+ <title>
+ <command>emphasis</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>emphasis</secondary>
+ </indexterm>
+ <para>要强调的内容，使用 <command><emphasis></command> 和 <command></emphasis></command> 标记。例如：</para>
+ <screen>
+ <computeroutput>
+安装过程将 <emphasis>删除所有</emphasis> 硬盘上的 <emphasis>所有</emphasis> 已有 Linux 分区，非 Linux 分区不会被删除。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>安装过程将 <emphasis>删除所有</emphasis> 硬盘上的 <emphasis>所有</emphasis> 已有 Linux 分区，非 Linux 分区不会被删除。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-example">
+ <title>
+ <command>example</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>example</secondary>
+ </indexterm>
+ <para>
+ <command><example></command> 和 <command></example></command> 标记用来格式化某个文档中的文本，适于显示代码示例等。</para>
+ <para>
+ <command><example></command> 标记应当有一个 ID 和标题：</para>
+ <screen>
+ <example id="static-ip">
+ <title>使用 DHCP 的静态 IP 地址</title>
+
+<screen width=60>
+<computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+<computeroutput>
+</screen>
+
+ </example>
+</screen>
+ <para>输出：</para>
+ <example id="static-ip">
+ <title>使用 DHCP 的静态 IP 地址</title>
+ <screen>
+ <computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+</computeroutput>
+ </screen>
+ </example>
+ </sect1>
+ <sect1 id="s1-xml-tags-filename">
+ <title>
+ <command>filename</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>filename</secondary>
+ </indexterm>
+ <para>
+ <command><filename></command> 和 <command></filename></command> 标记定义文件名和路径。由于目录是特殊的文件，因此也使用 <command>filename</command> 标记。例如：</para>
+ <screen>
+编辑 <filename>/home/smoore/sam.xml</filename> 文件，修改它或加注释。
+</screen>
+ <para>输出：</para>
+ <para>编辑 <filename>/home/smoore/sam.xml</filename> 文件，修改它或加注释。</para>
+ <para>它们也用来标记 RPM 软件包名称。例如：</para>
+ <screen>
+要使用 <application>Keyboard Configuration Tool</application>，必须安装 <filename>system-config-keyboard</filename> 软件包。
+</screen>
+ <para>输出：</para>
+ <para>要使用 <application>Keyboard Configuration Tool</application>，必须安装 <command>redhat-config-keyboard</command> 软件包。</para>
+ <note>
+ <title>注意</title>
+ <para>目录名必须以斜线 (<computeroutput>/</computeroutput>) 结尾，以与文件名区分。</para>
+ </note>
+ </sect1>
+ <sect1 id="s1-xml-tags-firstterm">
+ <title>
+ <command>firstterm</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>firstterm</secondary>
+ </indexterm>
+ <para>
+ <command><firstterm></command> 和 <command></firstterm></command> 标记用来定义一个用户不熟悉，但将频繁出现的词。例如：</para>
+ <screen>
+ <computeroutput>
+几乎所有现代操作系统都使用 <firstterm>disk
+partitions</firstterm>(磁盘分区)，&FC; 也不例外。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>几乎所有现代操作系统都使用 <firstterm>disk partitions</firstterm>(磁盘分区)，&FC; 也不例外。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-footnote">
+ <title>
+ <command>footnote</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>footnote</secondary>
+ </indexterm>
+ <para>如果您需要添加脚注，可以这样：</para>
+ <screen>
+ <computeroutput>
+如果您想进行服务器级
+<footnote>
+<para>
+服务器级安装用于安装典型的服务器环境。注意，服务器级安装不会安装图形界面。
+</para>
+</footnote> 安装，请参考 <citetitle>Installation Guide</citetitle>。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>如果您想进行服务器级 <footnote><para>服务器级安装用于安装典型的服务器环境。注意，服务器级安装不会安装图形界面。</para></footnote> 安装，请参考 <citetitle>Installation Guide</citetitle>。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-figure">
+ <title>
+ <command>figure</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>figure</secondary>
+ </indexterm>
+ <important>
+ <title>注意</title>
+ <para>顺序很重要！EPS 文件 <emphasis>必须</emphasis> 首先声明。</para>
+ </important>
+ <para>示例图象声明：</para>
+ <screen>
+ <computeroutput>
+<figure id="fig-ksconfig-basic">
+ <title>基本设置</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.eps"
+ format="EPS"/>
+ </imageobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.png"
+ format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>
+ 一些关于图象的文本描述
+ </phrase>
+ </textobject>
+ </mediaobject>
+</figure>
+</computeroutput>
+ </screen>
+ <para>下面列出了需要修改的内容：</para>
+ <screen>
+<figure id="fig-ksconfig-basic"> <emphasis>==> id="" 可以修改</emphasis>
+
+<title>基本设置</title> <emphasis>==> 标题可以修改</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.eps"> <emphasis>==> .eps 位置可以修改</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.png"> <emphasis>==> .png 位置可以修改</emphasis>
+
+<phrase>一些关于图象的文本描述</phrase> <emphasis>==> "一些关于..." 可以修改</emphasis></screen>
+ <para>关于获取屏幕截图，请参考 <xref linkend="s1-screenshots"/>。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-gui">
+ <title>图形用户界面标记</title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>GUI 标记</secondary>
+ </indexterm>
+ <sect2 id="s2-xml-tags-guilabel">
+ <title>
+ <command>guilabel</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>GUI 标记</secondary>
+ <tertiary>guilabel</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>guilabel</secondary>
+ </indexterm>
+ <para>使用 <command><guilabel></command> 和 <command></guilabel></command> 作为描述 GUI 时的默认标记，类似窗体名称或窗体标题。例如：</para>
+ <screen>
+ <computeroutput>
+<guilabel>Authentication Configuration</guilabel> 屏幕指引您如何配置更安全的系统。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>
+ <guilabel>Authentication Configuration</guilabel> 屏幕指引您如何配置更安全的系统。</para>
+ </sect2>
+ <sect2 id="s2-xml-tags-guibutton">
+ <title>
+ <command>guibutton</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>GUI 标记</secondary>
+ <tertiary>guibutton</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>guibutton</secondary>
+ </indexterm>
+ <para>使用 <command><guibutton></command> 和 <command></guibutton></command> 标记表示屏幕或菜单中的按钮。例如：</para>
+ <screen>
+ <computeroutput>
+选择 <guibutton>Activate on boot</guibutton> 按钮，配置 X 窗口系统自动启动。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>选择 <guibutton>Activate on boot</guibutton> 按钮，配置 X 窗口系统自动启动。</para>
+ </sect2>
+ <sect2 id="s2-xml-tags-guiicon">
+ <title>
+ <command>guiicon</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>GUI 标记</secondary>
+ <tertiary>guiicon</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>guiicon</secondary>
+ </indexterm>
+ <para>
+ <command><guiicon></command> 和 <command></guiicon></command> 标记用来表示面板或桌面图标。例如：</para>
+ <screen>
+ <computeroutput>
+双击桌面上的 <guiicon>Start Here</guiicon> 图标。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>双击桌面上的 <guiicon>Start Here</guiicon> 图标。</para>
+ </sect2>
+ <sect2 id="s2-xml-tags-guimenu">
+ <title>
+ <command>guimenu</command> 和 <command>guimenuitem</command></title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>GUI 标记</secondary>
+ <tertiary>guimenu</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>guimenu</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>GUI 标记</secondary>
+ <tertiary>guimenuitem</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>guimenuitem</secondary>
+ </indexterm>
+ <para>要表示一个菜单 (安装程序或控制面板中的菜单)，使用 <command><guimenu></command> 和 <command></guimenu></command> 标记。</para>
+ <para>要表示子菜单，使用 <command><guimenuitem></command> 和 <command></guimenuitem></command> 标记。(请注意示例中为了输出需要，插入了一些换行。)例如：</para>
+ <screen>
+ <computeroutput>
+选择 <guimenu>Main Menu</guimenu> =>
+ <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> 来启动
+<application>Emacs</application> 编辑器。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>选择 <guimenu>Main Menu</guimenu> => <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> 来启动 <application>Emacs</application> 编辑器。</para>
+ </sect2>
+ </sect1>
+ <sect1 id="s1-xml-tags-keycap">
+ <title>
+ <command>keycap</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>keycap</secondary>
+ </indexterm>
+ <para>要表示某个按键，应当使用 <command><keycap></command> 和 <command></keycap></command> 标记。按键会自动加上尖括号，因此不要在 XML 代码中再加一次。例如：</para>
+ <screen>
+ <computeroutput>
+要作出选择，按下 <keycap>Enter</keycap> 键。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>要作出选择，按下 <keycap>Enter</keycap> 键。</para>
+ <sect2 id="s2-xml-tags-menuchoice">
+ <title>
+ <command>menuchoice</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>menuchoice</secondary>
+ </indexterm>
+ <para>通常，使用鼠标对于频繁的操作过于繁琐。因此，程序员在程序中设置了快捷键来简化使用。应当使用 <command>shortcut</command> 标记包含 <command>keycap</command> 标记，然后再整个包含在 <command>menuchoice</command> 标记中，来表示快捷键。例如：</para>
+ <screen>
+ <computeroutput>
+打开菜单并选择：
+ <menuchoice>
+ <shortcut>
+ <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
+ </shortcut>
+ <guimenu><accel>F</accel>ile</guimenu>
+ <guimenuitem><accel>S</accel>ave</guimenuitem>
+ </menuchoice>.
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>打开菜单并选择：<menuchoice><shortcut><keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo></shortcut><guimenu><accel>F</accel>ile</guimenu><guimenuitem><accel>S</accel>ave</guimenuitem></menuchoice>.</para>
+ </sect2>
+ <sect2 id="s2-xml-tags-keycombo">
+ <title>
+ <command>keycombo</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>keycombo</secondary>
+ </indexterm>
+ <para>要描述按键组合，使用 <command><keycombo></command> 和 <command></keycombo></command>, <command><keycap></command> 和 <command></keycap></command> 标记。例如：</para>
+ <screen>
+ <computeroutput>
+要重启系统，按下 <keycombo>
+<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>
+</keycombo>.
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>要重启系统，按下 <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo>.</para>
+ </sect2>
+ </sect1>
+ <sect1 id="s1-xml-tags-lists">
+ <title>列表</title>
+ <indexterm>
+ <primary>列表</primary>
+ <secondary>创建</secondary>
+ </indexterm>
+ <para>您可以用 XML 创建多种列表。您可以创建无序的枚举，有序的编号列表，或是变量表 (先是一个词，然后是单独的一段话)。</para>
+ <para>还有一种列表适于表格，最后一种是用于定义词汇解释的列表。</para>
+ <para>下面各节描述了各种列表，以及如何创建。</para>
+ <sect2 id="s2-xml-tags-itemizedlist">
+ <title>
+ <command>itemizedlist</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>
+ <command>itemizedlist</command>
+ </secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>列表</secondary>
+ <tertiary>itemizedlist</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>列表</primary>
+ <secondary>
+ <command>itemizedlist</command>
+ </secondary>
+ </indexterm>
+ <para>
+ <command>itemizedlist</command> 适于向读者呈现重要的信息，而信息是无序的。它比 <command>variablelist</command> 更短，也简单一点。</para>
+ <para>要创建 <command>itemizedlist</command> (也称为枚举列表)，可以这样：</para>
+ <note>
+ <title>注意</title> <para>下面列表中的文本是直接包含在 <command>para</command> 标记中的。如果您使用列表，不要用这个标记，否则列表中会包含多余空白，无法对齐。如果多个列表项是多行文本，空白会更加明显。HTML 版本不会像 PDF 版本那样明显。</para></note>
+ <screen>
+ <computeroutput>
+<itemizedlist>
+ <listitem>
+ <para>熟悉安装程序的界面</para>
+ </listitem>
+
+ <listitem>
+ <para>开始安装程序</para>
+ </listitem>
+
+ <listitem>
+ <para>选择安装方法</para>
+ </listitem>
+</itemizedlist>
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <itemizedlist>
+ <listitem>
+ <para>熟悉安装程序的界面</para>
+ </listitem>
+ <listitem>
+ <para>开始安装程序</para>
+ </listitem>
+ <listitem>
+ <para>选择安装方法</para>
+ </listitem>
+ </itemizedlist>
+ </sect2>
+ <sect2 id="s2-xml-tags-orderedlist">
+ <title>
+ <command>orderedlist</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>
+ <command>orderedlist</command>
+ </secondary>
+ </indexterm>
+ <indexterm>
+ <primary>列表</primary>
+ <secondary>
+ <command>orderedlist</command>
+ </secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>列表</secondary>
+ <tertiary>orderedlist</tertiary>
+ </indexterm>
+ <para>
+ <command>orderedlist</command> 适于向读者显示必须以一定顺序出现的信息。<command>orderedlist</command> 用来向读者描述一步一步的场景转换很不错。</para>
+ <para>要创建 <command>orderedlist</command> (有序列表) 可以这样：</para>
+ <note>
+ <title>注意</title> <para>下面列表中的文本是直接包含在 <command>para</command> 标记中的。如果您使用列表，不要用这个标记，否则列表中会包含多余空白，无法对齐。如果多个列表项是多行文本，空白会更加明显。HTML 版本不会像 PDF 版本那样明显。</para></note>
+ <screen>
+ <computeroutput>
+<orderedlist>
+ <listitem>
+ <para>在线 &mdash; http://www.redhat.com/support/errata; 提供
+ 可以在线阅读的更正，您也可以下载光盘镜像。
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>电子邮件 &mdash; 发送空白邮件到 errata@@redhat.com,
+ 您将收到完整的包含安装程序和相关软件 (如果有的话) 的更正说明。
+ 同时还包括软件更新以及光盘镜像的 URL。通过这些 URL 来下载
+ 镜像。请注意：下载时使用二进制模式。</para>
+ </listitem>
+</orderedlist>
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <orderedlist>
+ <listitem>
+ <para>在线 — http://www.redhat.com/support/errata; 提供可以在线阅读的更正，您也可以下载光盘镜像。</para>
+ </listitem>
+ <listitem>
+ <para>电子邮件 — 发送空白邮件到 errata@@redhat.com, 您将收到完整的包含安装程序和相关软件 (如果有的话) 的更正说明。同时还包括软件更新以及的光盘镜像的 URL。通过这些 URL 来下载镜像。请注意：下载时使用二进制模式。</para>
+ </listitem>
+ </orderedlist>
+ </sect2>
+ <sect2 id="s2-xml-tags-varlist">
+ <title>
+ <command>variablelist</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>
+ <command>variablelist</command>
+ </secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>列表</secondary>
+ <tertiary>variablelist</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>列表</primary>
+ <secondary>
+ <command>variablelist</command>
+ </secondary>
+ </indexterm>
+ <para>
+ <command>variablelist</command> 适于表现一个词以及相关的解释和描述。</para>
+ <para>要创建 <command>variablelist</command> 可以这样：</para>
+ <note>
+ <title>注意</title> <para>下面列表中的文本是直接包含在 <command>para</command> 标记中的。如果您使用列表，不要用这个标记，否则列表中会包含多余空白，无法对齐。如果多个列表项是多行文本，空白会更加明显。HTML 版本不会像 PDF 版本那样明显。</para></note>
+ <screen>
+ <computeroutput>
+<variablelist>
+ <varlistentry>
+ <term> 新的多介质安装过程 </term>
+ <listitem>
+ <para>由于安装程序越来越大，RedHat 开发了
+ 可以处理多张 CD-ROM 介质的安装程序。</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>XFree 4.0 </term>
+ <listitem>
+ <para>X 窗口系统的配置从来没有如此简单。
+ 从选择显示器及其设置，到显卡探测，以及测试您期望的 X 窗口设置，
+ Xconfigurator 可以搞定一切。</para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <variablelist>
+ <varlistentry>
+ <term>新的多介质安装过程</term> <listitem> <para>由于安装程序越来越大，RedHat 开发了可以处理多张 CD-ROM 介质的安装程序。</para></listitem></varlistentry>
+ <varlistentry>
+ <term>XFree 4.0</term>
+ <listitem>
+ <para>X 窗口系统的配置从来没有如此简单。从选择显示器及其设置，到显卡探测，以及测试您期望的 X 窗口设置，Xconfigurator 可以搞定一切。</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <warning>
+ <title>警告</title>
+ <para>
+ <emphasis>不要</emphasis> 设置表格的 <computeroutput>frame</computeroutput> 属性，否则 PDF 生成会失败。</para>
+ </warning>
+ </sect2>
+ <sect2 id="s2-xml-tags-simplelist">
+ <title>在表格中创建列表，使用 <command>simplelist</command></title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>
+ <command>simplelist</command>
+ </secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>列表</secondary>
+ <tertiary>simplelist</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>列表</primary>
+ <secondary>
+ <command>simplelist</command>
+ </secondary>
+ </indexterm>
+ <indexterm>
+ <primary>表格</primary>
+ <secondary>在表格中创建列表</secondary>
+ <tertiary>
+ <command>simplelist</command>
+ </tertiary>
+ </indexterm>
+ <para>
+ <command>simplelist</command> 是无修饰的列表。<command>simplelist</command> 可以内联或按列对齐。</para>
+ <para>使用 <command>simplelist</command> 在表格内添加分离的文本段落。通常的列表，例如 <command>itemizedlist</command>，不能嵌入在表格内。</para>
+ <para>XML 代码如下：</para>
+ <screen>
+ <computeroutput>
+ <table id="tb-hwinfo-hostbus">
+ <title>主机总线适配器特性及配置要求</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="HostBus" colwidth="33"/>
+ <colspec colnum="2" colname="Features" colwidth="34"/>
+ <colspec colnum="3" colname="Single" colwidth="33"/>
+
+ <thead>
+ <row>
+ <entry>主机总线适配器</entry>
+ <entry>特性</entry>
+ <entry>Single-Initiator 配置</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is
+ off.</member>
+ </simplelist></entry>
+
+ <entry><simplelist>
+ <member>Set the onboard termination to automatic (the
+ default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ <row>
+ <entry>Qlogic QLA1080</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is off,
+ unless jumpers are used to enforce termination.</member>
+ </simplelist></entry>
+
+
+ <entry><simplelist>
+ <member>Set the onboard termination to
+ automatic (the default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <table id="tb-hwinfo-hostbus">
+ <title>主机总线适配器特性及配置要求</title>
+ <tgroup cols="3">
+ <colspec colname="HostBus" colnum="1" colwidth="33"/>
+ <colspec colname="Features" colnum="2" colwidth="34"/>
+ <colspec colname="Single" colnum="3" colwidth="33"/>
+ <thead>
+ <row>
+ <entry>主机总线适配器</entry>
+ <entry>特性</entry>
+ <entry>Single-Initiator 配置</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+ <entry>
+ <simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS utility.</member>
+ <member>Onboard termination is disabled when the power is off.</member>
+ </simplelist>
+ </entry>
+ <entry>
+ <simplelist>
+ <member>Set the onboard termination to automatic (the default).</member>
+ <member>Use the internal SCSI connector for private (non-cluster) storage.</member>
+ </simplelist>
+ </entry>
+ </row>
+ <row>
+ <entry>Qlogic QLA1080</entry>
+ <entry>
+ <simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS utility.</member>
+ <member>Onboard termination is disabled when the power is off, unless jumpers are used to enforce termination.</member>
+ </simplelist>
+ </entry>
+ <entry>
+ <simplelist>
+ <member>Set the onboard termination to automatic (the default).</member>
+ <member>Use the internal SCSI connector for private (non-cluster) storage.</member>
+ </simplelist>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <note>
+ <title>注意</title>
+ <para>注意 <command>simplelist</command> 标记的用法。<entry> 和 <simplelist> 标记必须靠紧，否则将产生解析错误。</para>
+ </note>
+ <para>每个要加入 <command>simplelist</command> 的段落或列表项应当包含在 <member> 标记中。</para>
+ </sect2>
+ <sect2 id="s2-xml-tags-glossary">
+ <title>
+ <command>glosslist</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>
+ <command>glosslist</command>
+ </secondary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>列表</secondary>
+ <tertiary>glosslist</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>列表</primary>
+ <secondary>
+ <command>glosslist</command>
+ </secondary>
+ </indexterm>
+ <para>使用 <command>glosslist</command> 来创建词汇表和解释。</para>
+ <para>XML 代码如下：</para>
+ <screen>
+ <computeroutput>
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>一个小程序，通常是实用工具或简单程序。</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>计算机或计算机系统中，
+ 组件的组织和整合的设计。</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>将文件传送到存储设备，以节省空间和/或
+ 加以组织。</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>一个小程序，通常是实用工具或简单程序。</para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>计算机或计算机系统中，组件的组织和整合的设计。</para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>将文件传送到存储设备，以节省空间和/或加以组织。</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+ </sect2>
+ </sect1>
+ <sect1 id="s1-xml-tags-option">
+ <title>
+ <command>option</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>option</secondary>
+ </indexterm>
+ <para>如果您的命令需要选项或设置标志，使用 <command><option></command> 和 <command></option></command> 标记。</para>
+ <note>
+ <title>注意</title>
+ <para><option> 标记只用于命令行选项，不用于配置文件。</para>
+ </note>
+ <para>指定选项的 XML 代码如下：</para>
+ <screen>
+ <computeroutput>
+例如，运行命令 <command>ls</command> 时可以指定选项 <option>-la</option>。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>例如，运行命令 <command>ls</command> 时可以指定选项 <option>-la</option>。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-indexing">
+ <title>索引节点</title>
+ <indexterm>
+ <primary>创建索引</primary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>创建索引</secondary>
+ </indexterm>
+ <para>下面的命令序列展示了如何向文档中添加一个索引项的代码：</para>
+ <screen>
+ <computeroutput>
+<indexterm> <-- 这是要在索引中添加的词汇
+<primary>foo</primary> <-- 表示 "foo" 是首要条目
+<secondary>bar</secondary> <-- "bar" 将列在 "foo" 条目之下
+</indexterm> <-- 关闭索引项
+</computeroutput>
+ </screen>
+ <indexterm>
+ <primary>foo</primary>
+ <secondary>bar</secondary>
+ </indexterm>
+ <para>
+ <command><seealso></command> 标记允许您引用另一个索引项或其他手册。应确保您指向的 <command><seealso></command> 引用有自己的节点。例如：</para>
+ <indexterm>
+ <primary>创建索引</primary>
+ <secondary>seealso 标记</secondary>
+ </indexterm>
+ <screen>
+ <computeroutput>
+<indexterm>
+<primary>SWAK</primary>
+<seealso>salutations</seealso>
+</indexterm>
+
+
+<indexterm>
+<primary>salutations</primary>
+</indexterm>
+</computeroutput>
+ </screen>
+ <indexterm>
+ <primary>SWAK</primary>
+ <seealso>Salutations</seealso>
+ </indexterm>
+ <indexterm>
+ <primary>Salutations</primary>
+ </indexterm>
+ <para>
+ <command><see></command> 标记允许您引用一个完整的索引节点。例如：</para>
+ <indexterm>
+ <primary>创建索引</primary>
+ <secondary>see 标记</secondary>
+ </indexterm>
+ <screen>
+ <computeroutput>
+<indexterm>
+<primary>Guinness</primary>
+<see>beer</see> <-- "beer" 将被列在 "Guinness" 条目下，但是应确保所引用的 "beer" 有自己的索引节点。
+</indexterm>
+
+<indexterm>
+<primary>beer</primary>
+</indexterm>
+</computeroutput>
+ </screen>
+ <indexterm>
+ <primary>Guinness</primary>
+ <see>Beer</see>
+ </indexterm>
+ <indexterm>
+ <primary>Beer</primary>
+ </indexterm>
+ <para>要查看这里的索引节点的 HTML 输出，请参考文档最后的 <filename>generated-index.html</filename> 文件。</para>
+ <para>索引是如何生成的? 如果文档中包含 indexterm，并且开标记和闭标记出现在文档或文章的结束标记之前，就创建索引，因为样式表参数 <command>generate.index</command> 的默认值是真。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-para">
+ <title>
+ <command>para</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>para</secondary>
+ </indexterm>
+ <para>对于任意一段，<command><para></command> 和 <command></para></command> 标记必须作为这一段的开始和结束。</para>
+ <para>不要在除了简单段落之外使用 <command>para</command> 标记。否则，文本内部会产生多余的空白。</para>
+ <para>在下列标记周围不要使用 <command><para></command> (换句话说，不要把下列标记放在 <command><para></command> 标记中)：</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <command><screen></command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command><itemizedlist></command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command><orderedlist></command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command><variablelist></command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command><table></command>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </sect1>
+ <sect1 id="s1-xml-tags-part">
+ <title>
+ <command>part</command>
+ </title>
+ <indexterm>
+ <primary>parts</primary>
+ </indexterm>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>part</secondary>
+ </indexterm>
+ <para>在主控文件中，可以将章划分为部，以表示逻辑分组。例如，在主控文件中，以 <command>part</command> 标签包含章的实体：</para>
+ <screen>
+ <computeroutput>
+<part id="pt-foo">
+ <partintro>
+ <para>一些文本，对这一部分的介绍</para>
+ &CHAPTER;
+
+ &ANOTHER-CHAPTER;
+</part>
+</computeroutput>
+ </screen>
+ <para>如果您创建了一个 part，应当对内容作一些介绍。例如：</para>
+ <screen>
+ <computeroutput>
+ <part id="pt-setup">
+ <title>设置环境</title>
+ <partintro>
+ <para>本节讲述当您刚加入 Docs Group 时需要的信息。
+ 您也许会再参考本节中，有关安装 &FC; 的信息。</para>
+ </partintro>
+</computeroutput>
+ </screen>
+ <para>在 HTML 输出中，会生成单独的 HTML 页面，包含这一部的编号、标题、介绍和目录。在 PDF 输出中，这些信息会出现在单独的一页上。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-prompt">
+ <title>
+ <command>prompt</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>prompt</secondary>
+ </indexterm>
+ <para>要显示提示符，类似 root 提示符或 DOS 提示符，使用 <command><prompt></command> 和 <command></prompt></command> 标记。例如：</para>
+ <screen>
+ <computeroutput>
+在 <prompt>LILO:</prompt> 启动提示符下，输入 linux 来启动到 Linux 分区。
+
+在 <prompt>C:\></prompt> 提示符下，输入...
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>在 <prompt>LILO:</prompt> 启动提示符下，输入 linux 来启动到 Linux 分区。</para>
+ <para>在 <prompt>C:\></prompt> 提示符下，输入...</para>
+ <note>
+ <title>注意</title>
+ <para>在显示计算机输出的范例时 (通常是在 <command>screen</command> 标记中)，不要包含提示符或命令 (除非命令或提示符是您意图显示的计算机输出)。</para>
+ </note>
+ </sect1>
+ <sect1 id="s1-xml-tags-replaceable">
+ <title>
+ <command>replaceable</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>replaceable</secondary>
+ </indexterm>
+ <para>要创建可替换的文本，使用 <command><replaceable></command> 和 <command></replaceable></command> 标记包围您用作可变值的文本。</para>
+ <para>这个例子演示了在引用 RPM 文件时如何使用 <command>replaceable</command> 标记。</para>
+ <screen>
+foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm
+</screen>
+ <para>输出：</para>
+ <screen>
+foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm
+</screen>
+ </sect1>
+ <sect1 id="s1-xml-tags-screen">
+ <title>
+ <command>screen</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>screen</secondary>
+ </indexterm>
+ <para>
+ <command><screen></command> 标记用来格式化文档中的文本，适于用来添加代码示例，计算机输出等等。在 HTML 中，使用 Fedora CSS 文件，可以显示为灰色背景的方框。需要这种效果时，只要将开标记 <command><screen></command> 和闭标记 <command></screen></command> 包围在需要强调的文本前后。</para>
+ <important>
+ <title>注意</title>
+ <para>使用 <command><screen></command> 标记时，必须设置所包含的所有内容，包括 <command><screen></command> 标记本身为左对齐。这样，在转化为 HTML 时，在灰色背景内部文字之前不会出现多余的空白。</para>
+ </important>
+ <para>
+ <command><screen></command> 标记可能包含其他内联标记，类似 <command><computeroutput></command>, <command><userinput></command>, 或 <command><replaceable></command> 等等。其他内联标记未作要求。<command><screen></command> 标记本身可以提供足够的上下文，尤其对于简单的范例或列举文件而言。考虑范例的上下文，如果内联标记有助于阅读，那么就使用它。</para>
+ <para>如果您使用内联标记，牢记 <command><screen></command> 标记中的换行会在任何输出中生成换行。将标记与内容 <emphasis>放在同一行</emphasis>。不要在 <command><screen></command> 的内容中过分使用标记。</para>
+ <para>
+ <command><screen></command> 示例如下：</para>
+ <screen>
+ <computeroutput><screen>
+这是 screen 的示例。其中无须使用 &lt;para&gt; 标记。
+</screen></computeroutput>
+ </screen>
+ <para>输出：</para>
+ <screen>
+这是 screen 的示例。其中无须使用 <para> 标记。
+</screen>
+ <sect2 id="s2-xml-tags-screen-inline-tags">
+ <title>在 <command>screen</command> 中使用内联标记</title>
+ <para>如果您在 <command><screen></command> 中使用内联标记，遵循下列准则以保持一致。如果 screen 的内容是配置文件的清单或程序的输出，使用 <command><computeroutput></command> 标记包含整个输出。如果用户应当在命令行照范例输入，或是配置文件，使用 <command><userinput></command> 标记。用简短的叙述性的话来区分输入和输出，如下所示：</para>
+ <screen>
+ <command><para></command>
+ 输入下面的命令：
+ <command></para></command><command><screen></command><command><userinput></command>command -sw file1<command></userinput></command><command></screen></command><command><para></command>
+ 可以看到下列输出：
+ <command></para></command><command><screen></command><command><computeroutput></command>Completed, time = 0.12 sec<command></computeroutput></command><command></screen></command></screen>
+ <para>输出：</para>
+ <para>输入下面的命令：</para>
+ <screen>
+ <userinput>command -sw file1</userinput>
+ </screen>
+ <para>可以看到下列输出：</para>
+ <screen>
+ <computeroutput>Completed, time = 0.12 sec</computeroutput>
+ </screen>
+ <note>
+ <title>注意</title>
+ <para>在 <command>screen</command> 标记中显示一条命令或命令序列时，不要显示提示符。</para>
+ </note>
+ <para>如果 <command><screen></command> 向读者显示如何修改文本的 <emphasis>一部分</emphasis>，可以将修改部分以内联的 <command><userinput></command> 标记。您可以在大块内联的 <command><computeroutput></command> 文本中使用 <command><userinput></command>。这时不要包含更多上下文，除非必须这么做。下面的示例演示了这些准则：</para>
+ <screen>
+ <command><para></command>
+ 编辑 <command><filename></command>/etc/sysconfig/init<command></filename></command> 文件，如下所示：
+ <command></para></command><command><screen></command>
+GRAPHICAL=<command><userinput></command>yes<command></userinput></command><command></screen></command></screen>
+ <para>输出：</para>
+ <para>编辑 <filename>/etc/sysconfig/init</filename> 文件，如下所示：</para>
+ <screen>
+GRAPHICAL=<userinput>yes</userinput></screen>
+ <para>对于如何在 <command>screen</command> 标记中使用 <command>replaceable</command> 标记，请参考 <xref linkend="s1-xml-tags-replaceable"/>。</para>
+ </sect2>
+ </sect1>
+ <sect1 id="s1-xml-tags-sections">
+ <title>section</title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>节</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>节</primary>
+ </indexterm>
+ <para>在文章中 (或者在 chapter 中，如果是 DocBook XML book 样式的话，类似 <citetitle>&IG;</citetitle>)，可以细分为节和小节。<command><sect1></command> 总是最顶层的节。如果两个 section 级别相同，那么一个不能包含另一个 (section 2 可以包含在 section 1 里面，但是如果再创建新的 section 1，必须先关闭当前的 section 1)。大致的布局如下：</para>
+ <screen>
+ <computeroutput>
+<sect1 id="s1-uniquename">
+ <title>插入标题</title>
+ <para>
+ 内容文本。
+ </para>
+
+
+ <sect2 id="s2-uniquename">
+ <title>插入标题</title>
+ <para>
+ 内容文本。
+ </para>
+
+ <sect3 id="s3-uniquename">
+ <title>插入标题</title>
+ <para>
+ 内容文本。
+ </para>
+
+ </sect3>
+
+ </sect2>
+
+</sect1>
+</computeroutput>
+ </screen>
+ <para>在 DocBook article 样式中，如果您只需要一级 section，可以使用 <command>section</command> 标记。例如：</para>
+ <screen>
+ <computeroutput>
+<section id="sn-uniquename">
+ <title>插入标题</title>
+ <para>
+ 内容文本。
+ </para>
+</section>
+<section id="sn-anothername">
+ <title>插入标题</title>
+ <para>
+ 内容文本。
+ </para>
+</section>
+</computeroutput>
+ </screen>
+ </sect1>
+ <sect1 id="s1-xml-tags-table">
+ <title>
+ <command>table</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>table</secondary>
+ </indexterm>
+ <para>下面是创建表格的范例。</para>
+ <screen>
+<table id="tb-mockup-before-begin">
+ <emphasis>这在 XML 中声明了一个表格，ID 是 <command>"tb-mockup-before-begin"</command>。</emphasis>
+
+<title>Available Features of GNOME and KDE</title>
+
+<tgroup cols="3">
+ <emphasis>这在 XML 中声明了一个表格，包含三列。</emphasis>
+
+<colspec colnum="1" colname="Features" colwidth="3"/>
+ <emphasis><command>colspec</command> 表示您向 XML 声明的表格列信息。</emphasis> <emphasis><command>colnum="1"</command> 表示您对第一列的设定。</emphasis><emphasis><command>colname="Features"</command> 表示本列的标题是 "Features"。</emphasis><emphasis><command>colwidth="3"</command> 指定列宽。这里有些机关：如果两列的列宽分别是 1 和 2，那么 1 占据的页宽就是 2 的一半。但是，如果您需要让第一列比第二列的一半稍微宽一点，那么就用一个更大的数值，例如指定列宽分别为 10 和 20，然后把 10 增加到 11 或 12，这样就比第二列的 20 的一半大一点了。如果没有给定任何值，默认就是 1。</emphasis>
+
+<colspec colnum="2" colname="GNOME" colwidth="2"/>
+<colspec colnum="3" colname="KDE" colwidth="2"/>
+
+<thead>
+ <emphasis>包含一个或多个表格行。</emphasis>
+
+<row>
+ <emphasis>包含一个或多个表格单元。</emphasis>
+
+<entry>Features</entry>
+ <emphasis>表格单元元素，一列表格单元中的一个，定义了行内的列。</emphasis>
+
+<entry>GNOME</entry>
+<entry>KDE</entry>
+</row>
+</thead>
+
+<tbody>
+ <emphasis>包含一个或多个表格行，作为表格的主体。</emphasis>
+
+<row>
+<entry>高度可定制</entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>多种窗口管理器</entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>互联网程序</entry>
+<entry>yes </entry>
+<entry>yes </entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+</screen>
+ <table id="tb-mockup-before-begin">
+ <title>Available Features of GNOME and KDE</title>
+ <tgroup cols="3">
+ <colspec colname="Features" colnum="1" colwidth="3"/>
+ <colspec colname="GNOME" colnum="2" colwidth="2"/>
+ <colspec colname="KDE" colnum="3" colwidth="2"/>
+ <thead>
+ <row>
+ <entry>特性</entry>
+ <entry>GNOME</entry>
+ <entry>KDE</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>高度可定制</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>多种窗口管理器</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>互联网程序</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <sect2 id="s2-xml-tags-listintable">
+ <title>在表格中创建列表</title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>table</secondary>
+ <tertiary>表格中的列表</tertiary>
+ </indexterm>
+ <para>在表格中创建列表比较困难，它要求严格的格式化以及一些 <application>Emacs</application> 无法完成的命令补全。</para>
+ <para>需要使用的标记是 <command><simplelist></command> 和 <command><member></command>。</para>
+ <para>下面是在表格中创建列表的例子。</para>
+ <screen>
+ <computeroutput>
+<table id="tb-hardware-powerswitch">
+ <title>不间断电源硬件</title>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="Hardware" colwidth="2"/>
+ <colspec colnum="2" colname="Quantity" colwidth="2"/>
+ <colspec colnum="3" colname="Description" colwidth="6"/>
+ <colspec colnum="4" colname="Required" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>Description</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Serial power switches</entry>
+
+ <entry>Two</entry>
+
+ <entry><simplelist> <member>Power switches enable each cluster system
+ to power-cycle the other cluster system. Note that clusters are
+ configured with either serial or network attached power switches and
+ not both.</member>
+
+ <member>The following serial attached power switch has been
+ fully tested:</member>
+
+ <member>RPS-10 (model M/HD in the US, and model M/EC in
+ Europe) </member>
+
+ <member>Latent support is provided for the following serial
+ attached power switch. This switch has not yet been fully
+ tested:</member>
+
+ <member>APC Serial On/Off Switch (partAP9211), <ulink
+ url="http://www.apc.com/">http://www.apc.com/</ulink></member>
+ </simplelist></entry>
+
+ <entry>Strongly recommended for data integrity under all failure
+ conditions</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+</table>
+</computeroutput>
+ </screen>
+ <para>
+ <command><simplelist></command> 标记必须紧挨 <command><entry></command> 标记。如果不这样，就无法成功解析。</para>
+ <para>上面的示例看起来象这样：</para>
+ <table id="tb-hardware-powerswitch">
+ <title>不间断电源硬件</title>
+ <tgroup cols="4">
+ <colspec colname="Hardware" colnum="1" colwidth="2"/>
+ <colspec colname="Quantity" colnum="2" colwidth="2"/>
+ <colspec colname="Description" colnum="3" colwidth="6"/>
+ <colspec colname="Required" colnum="4" colwidth="2"/>
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>描述</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Serial power switches</entry>
+ <entry>Two</entry>
+ <entry>
+ <simplelist> <member>Power switches enable each cluster system to power-cycle the other cluster system. Note that clusters are configured with either serial or network attached power switches and not both.</member><member>The following serial attached power switch has been fully tested:</member><member>RPS-10 (model M/HD in the US, and model M/EC in Europe)</member><member>Latent support is provided for the following serial attached power switch. This switch has not yet been fully tested:</member><member>APC Serial On/Off Switch (partAP9211), <ulink url="http://www.apc.com/">http://www.apc.com/</ulink></member></simplelist>
+ </entry>
+ <entry>Strongly recommended for data integrity under all failure conditions</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </sect2>
+ </sect1>
+ <sect1 id="s1-xml-tags-trademark">
+ <title>
+ <command>trademark</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>
+ <command>trademark</command>
+ </secondary>
+ </indexterm>
+ <para>不要使用商标实体 &trade;, &copy;, 或 &reg; 因为它们无法为所有字符集产生 HTML 输出。这些实体产生的 HTML 输出定义在 DTD 中，无法通过样式表改变。</para>
+ <para>应当使用 <command>trademark</command> 标记以及相关类别，如下所示：</para>
+ <screen>
+ <computeroutput>
+<trademark>其后是商标符号</trademark>
+<trademark class="registered">其后是注册商标符号</trademark>
+<trademark class="copyright">其后是版权符号</trademark>
+</computeroutput>
+ </screen>
+ </sect1>
+ <sect1 id="s1-xml-tags-userinput">
+ <title>
+ <command>userinput</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>
+ <command>userinput</command>
+ </secondary>
+ </indexterm>
+ <para>要显示用户将输入的内容，使用 <command>userinput</command> 标记。例如：</para>
+ <screen>
+ <computeroutput>
+在提示符下，输入：
+
+<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>在提示符下，输入：</para>
+ <para>
+ <userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+ </para>
+ </sect1>
+ <!-- <sect1 id="s1-xml-tags-mouse">
+ <title><command>mousebutton</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>mousebutton</secondary>
+ </indexterm>
+ <para>
+Describe mouse actions with the mousebutton tag. Below is an example of its use.
+</para>
+
+<screen>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+</screen>
+
+ <para>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+ </para>
+
+ </sect1> -->
+ <sect1 id="s1-xml-tag-sulink">
+ <title>
+ <command>ulink</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>ulink</secondary>
+ </indexterm>
+ <para>要在文本中创建 URL，如下：</para>
+ <screen>
+ <computeroutput>
+在线 &mdash; <ulink url="http://www.redhat.com/support/errata/">
+http://www.redhat.com/support/errata/</ulink>; 提供可以在线阅读的更正，您也可以下载光盘镜像。
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>在线 — <ulink url="http://www.redhat.com/support/errata/"> http://www.redhat.com/support/errata/</ulink>; 提供可以在线阅读的更正，您也可以下载光盘镜像。</para>
+ <note>
+ <title>注意</title>
+ <para>如果 URL 不是以文件名结尾，必须以斜线结束 (<computeroutput>/</computeroutput>)，才是格式正确的 URL，例如 <ulink url="http://www.redhat.com/">http://www.redhat.com/</ulink>。</para>
+ </note>
+ </sect1>
+ <sect1 id="s1-xml-tags-wordasword">
+ <title>
+ <command>wordasword</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>wordasword</secondary>
+ </indexterm>
+ <para><wordasword> 标记用来定义一个词只作为语法单位，不代表其他含义。</para>
+ <para>许多技术文档使用了有丰富意义的词汇。有时又需要用到不带技术意味的这个词。<wordasword> 标记这样的词，指示这个词应当简单地理解为一个词而不是其他东西。</para>
+ <para>使用这个标记不会帮助读者理解其中的意义差别；好文档应当做到这一点。实际上 <wordasword> 的价值在于全文搜索和索引工具可以用它来减少虚假结果。</para>
+ <para>例如：</para>
+ <screen>
+ <computeroutput>要使用 <command>grep</command> 搜索单词
+<wordasword>linux</wordasword>，使用命令
+<command>grep linux</command>。</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>要使用 <command>grep</command> 搜索单词 <wordasword>linux</wordasword>，使用命令 <command>grep linux</command>。</para>
+ <para>这个例子中，"linux" 仅仅是一个单词。文档不是以 Linux 为主题，这个词也不为内容添加任何相关含义，可以替换为其他任何词。</para>
+ </sect1>
+ <sect1 id="s1-xml-tags-xref">
+ <title>
+ <command>xref</command>
+ </title>
+ <indexterm>
+ <primary>XML 标记</primary>
+ <secondary>xref</secondary>
+ </indexterm>
+ <para>要引用手册中其他章节，使用 <command><xref></command> 标记。</para>
+ <para>它的输出是您向读者指引的章节的标题。例如：</para>
+ <screen>
+ <computeroutput>
+关于主控文件，请参考
+<xref linkend="ch-tutorial"></xref> 和 <xref linkend="s1-tutorial-parent"></xref>
+</computeroutput>
+ </screen>
+ <para>输出：</para>
+ <para>关于主控文件，请参考 <xref linkend="ch-tutorial"/> 和 <xref linkend="s1-tutorial-parent"/>。</para>
+ </sect1>
+</chapter>
+@
+
+
+1.2
+log
+ at update build part
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: docs-xml-tags-en.xml,v 1.12 2004/09/30 14:25:36 tfox Exp $ --><chapter id="ch-xml-tags">
+@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+ at a121 2
+<!--$Id: docs-xml-tags-en.xml,v 1.12 2004/09/30 14:25:36 tfox Exp $ -->
+
+@
+
diff --git a/old-documentation-guide/Attic/docs-xml-tags.xml,v b/old-documentation-guide/Attic/docs-xml-tags.xml,v
new file mode 100644
index 0000000..708029f
--- /dev/null
+++ b/old-documentation-guide/Attic/docs-xml-tags.xml,v
@@ -0,0 +1,2510 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2003.11.21.22.40.39; author tfox; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2003.10.15.18.11.01; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at change filenames to end with -en.xml
+@
+text
+@<!-- $Id: docs-xml-tags.xml,v 1.2 2003/10/15 18:11:01 tfox Exp $ -->
+
+ <chapter id="ch-xml-tags">
+ <title>DocBook XML Tags</title>
+
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>tags</secondary>
+ <see>XML tags</see>
+ </indexterm>
+
+ <para>Please read this chapter carefully. This chapter describes the tags
+ used by the Docs Project. Some of the rules described are specific to the
+ project.
+ </para>
+
+ <para>If these tags are used appropriately, document searches will provide
+ meaningful results. These tags help search engines identify the
+ information relevant to the search request. Another benefit is that all
+ &PROJECT; documents will have a similar look and feel (however, they will have
+ some differences depending upon the output format).
+ </para>
+
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>general tag information</secondary>
+ </indexterm>
+
+ <para>All tags in XML must have an opening and closing tag Additionally,
+ proper XML conventions say that there must be a unique identifier for
+ sections, chapters, figures, tables, and so on, so that they may be
+ correctly identified, and cross referenced if needed.</para>
+
+ <para>Although XML is capable of handling many document types, the format
+ discussed here is the article format.</para>
+
+ <para>
+ This chapter only discusses tags used for documentation for the &PROJECT;,
+ not all available DocBook XML tags. For the complete list, refer to:
+ </para>
+<screen>
+<computeroutput>
+<ulink url="http://www.docbook.org/tdg/en/html/docbook.html">http://www.docbook.org/tdg/en/html/docbook.html</ulink>
+</computeroutput>
+</screen>
+
+ <sect1 id="s1-xml-tags-caveats">
+ <title>Tags and Entities Caveats</title>
+
+ <indexterm>
+ <primary>xml tags</primary>
+ <secondary>caveats</secondary>
+ </indexterm>
+
+ <para>
+ It is very important that you remember the caveats in this section. Even
+ though they are more strict than valid DocBook XML, these rules exist
+ so that both the HTML and PDF outputs look proper.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>Do Not Use Trademark Entities</term>
+ <listitem>
+ <para>Do not use the trademark entities &trade;, &copy;, or
+ &reg; because the do not produce HTML output that works for all
+ charsets. The HTML output produces by these entities are declared in
+ the DTD and cannot be changed via the stylesheet.</para>
+ <para>Instead, use the <command>trademark</command> tag and its
+ associates classes as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><trademark>trademark symbol after me</trademark>
+ </para>
+ </listitem>
+ <listitem>
+ <para><trademark class="registered">registered trademark symbol after me</trademark>
+ </para>
+ </listitem>
+ <listitem>
+ <para><trademark class="copyright">copyright symbol after me</trademark></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <command>para</command> tags</term>
+ <listitem>
+ <para>Do not use <command>para</command> tags around anything other
+ than a simple paragraph. Doing so will create additional white space
+ within the text itself in the PDF version.
+ </para>
+ <para>Specifically, do not use <command>para</command> tags around
+ the following (or, to put this another way, do not embed the
+ following within <command>para</command> tags):
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><screen></para>
+ </listitem>
+ <listitem>
+ <para><itemizedlist></para>
+ </listitem>
+ <listitem>
+ <para><orderedlist></para>
+ </listitem>
+ <listitem>
+ <para><variablelist></para>
+ </listitem>
+ <listitem>
+ <para><table></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <command>para</command> tags within
+ <command>listitem</command> tags</term>
+ <listitem>
+ <para>Content inside <command>para</command> tags within
+ <command>listitem</command> tags <emphasis>must</emphasis> start
+ immediately after the beginning <para> tag to avoid extra
+ white space in the PDF version.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <command>screen</command> tags</term>
+ <listitem>
+ <para>The <command>screen</command> tags (<screen> and
+ </screen>) <emphasis>must</emphasis> be flush left in the
+ XML file, and all the content inside the
+ <command>screen</command> tags must be flush left as well unless
+ the white space in intentional; otherwise, the extraneous
+ whitespace will appear in the HTML version.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-application">
+ <title><command>application</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>application</secondary>
+ </indexterm>
+
+ <para>An application is the name of a GUI software program. A command is
+ the name of an executable (text) program or a software command.</para>
+
+ <para>The <command><application></command> and
+ <command></application></command> tags allow you to refer to an
+ application or program. For example, the following XML:
+ </para>
+
+<screen>
+<computeroutput>
+To view the Web in Linux, you can use
+<application>Mozilla</application> or
+<application>lynx</application> if you only want a text-based
+browser.
+</computeroutput>
+</screen>
+
+ <para>
+ produces the following output:
+ </para>
+
+ <para>
+ To view the Web in Linux, you can use <application>Mozilla</application>
+ or <application>lynx</application> if you only want a text-based browser.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-chapter">
+ <title><command>chapter</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>chapter</secondary>
+ </indexterm>
+
+ <para>
+ A DocBook book can be divided into chapters such as:
+ </para>
+
+<screen>
+<computeroutput>
+<!--$Id: docs-xml-tags.xml,v 1.2 2003/10/15 18:11:01 tfox Exp $ -->
+
+ <chapter id="ch-sample">
+ <title>Sample Chapter</title>
+
+ <para>This is a sample chapter, showing you the XML tags used to create a
+ chapter, sections, and subsections.</para>
+
+ </chapter>
+</computeroutput>
+</screen>
+
+ <para>
+ The chapter can also be further divided into sections
+ (<command>sect1</command>, <command>sect2</command>,
+ <command>sect3</command>, etc.). Refer to <xref
+ linkend="s1-xml-tags-sections"></xref> for details.
+ </para>
+
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-citetitle">
+ <title><command>citetitle</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>citetitle</secondary>
+ </indexterm>
+
+
+ <para>
+ The <command><citetitle></command> tag provides formatting for a
+ specific references (title can be manually typed out or if already
+ defined within your document set, given as an entity<footnote><para>An
+ entity is a short hand way of referring to another manual or guide. It
+ can be defined within the parent document or within a set of files that
+ your DTD references for your specific documentation set.</para>
+ </footnote>
+ ).</para>
+
+ <para>
+ For example:
+ </para>
+<screen>
+<computeroutput>
+<citetitle>IG;</citetitle>.
+</computeroutput>
+</screen>
+ <para>
+ The output looks like <citetitle>&IG;</citetitle> because &IG; is an
+ entity.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-command">
+ <title><command>command</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>command</secondary>
+ </indexterm>
+
+ <para>An application is the name of a GUI software program. A command is
+ the name of an executable (text) program or a software command. Any
+ program that is a command line or text-based only tool is marked with
+ <command>command</command> tags. </para>
+
+
+ <para>If you have text that is a command, use the
+ <command><command></command> and
+ <command></command></command> tags such as:
+ </para>
+
+
+
+<screen>
+<computeroutput>
+To change your keyboard after installation, become root
+and use the <command>redhat-config-keyboard</command> command,
+or you can type <command>setup</command> at the root prompt.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+ <para>
+ To change your keyboard after installation, become root and use
+ the <command>redhat-config-keyboard</command> command, or you can type
+ <command>setup</command> at the root prompt.
+ </para>
+
+ <para>Another example would be:</para>
+
+<screen>
+<computeroutput>
+<command>MAILNOVIOLATIONS</command> — If set
+to <command>true</command> this option tells Tripwire to
+email a report at a regular interval regardless of whether or not
+any violations have occured. The default value is
+<command>true</command>.
+</computeroutput>
+</screen>
+
+ <para>
+ with the output:
+ </para>
+
+ <para>
+ <command>MAILNOVIOLATIONS</command> — If set to
+ <command>true</command> this variable tells Tripwire to email a report
+ at a regular interval regardless of whether or not any violations have
+ occured. The default value is <command>true</command>.
+ </para>
+
+ <note>
+ <title>Note</title> <para>In this example, the option value (true) is
+ defined with a <command> tag set. Because a option is a
+ configuration file option (command line options which would use the
+ <option> tag set), and because there is no configuration file
+ option tag available to use, we are extending the <command> tag
+ set to define options in a configuration file.</para>
+ </note>
+
+ <para>
+ Terms marked with <command>command</command> tags because there aren't
+ exact tags for them:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Options in configuration files such as Apache directives</para>
+ </listitem>
+ <listitem>
+ <para>daemon names</para>
+ </listitem>
+ </itemizedlist>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-compoutput">
+ <title><command>computeroutput</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>computeroutput</secondary>
+ </indexterm>
+
+ <para>
+ To show computer output use the following tags:
+ </para>
+<screen>
+<computeroutput>
+<computeroutput>Do you want to delete this file? y n</computeroutput>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+ <para>
+ <computeroutput>Do you really want to delete this file? y n</computeroutput>
+ </para>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-emphasis">
+ <title><command>emphasis</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>emphasis</secondary>
+ </indexterm>
+
+ <para>
+ To emphasis content, use the <command><emphasis></command> and
+ <command></emphasis></command> tags. For example:
+ </para>
+<screen>
+<computeroutput>
+This installation <emphasis>will remove all</emphasis> existing
+Linux partitions on <emphasis>all</emphasis> hard drives in your
+system; non-Linux partitions will not be removed.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ This installation <emphasis>will remove all</emphasis> existing Linux
+ partitions on <emphasis>all</emphasis> hard drives in your system;
+ non-Linux partitions will not be removed.
+ </para>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-example">
+ <title><command>example</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>example</secondary>
+ </indexterm>
+
+ <para>The <command><example></command> and
+ <command></example></command> tags are used to format text within a
+ document and is great for adding emphasis to show examples of code,
+ exercises, and more. </para>
+
+ <para>The <command><example></command> tag set should be given an ID
+ and title:</para>
+
+<screen>
+ <example id="static-ip">
+ <title>Static IP Address using DHCP</title>
+
+<screen width=60>
+<computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+<computeroutput>
+</screen>
+
+ </example>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <example id="static-ip">
+ <title>Static IP Address using DHCP</title>
+
+<screen>
+<computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+</computeroutput>
+</screen>
+ </example>
+
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-filename">
+ <title><command>filename</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>filename</secondary>
+ </indexterm>
+
+ <para>
+ The <command><filename></command> and
+ <command></filename></command> tags define a filename or path to a
+ file. Since directories are just special files, they are marked with the
+ <command>filename</command> tags as well. For example:
+ </para>
+<screen>
+Edit the <filename>/home/smoore/sam.xml</filename> file to make
+changes or add comments.
+</screen>
+ <para>
+ The output:
+ </para>
+ <para>
+ Edit the <filename>/home/smoore/sam.xml</filename> file to make changes
+ or add comments.
+ </para>
+
+ <para>
+ They are also used to markup an RPM package name. For example:
+ </para>
+<screen>
+To use the <application>Keyboard Configuration Tool</application>, the
+<command>redhat-config-keyboard</command> RPM package must be installed.
+</screen>
+ <para>
+ The output:
+ </para>
+ <para>
+ To use the <application>Keyboard Configuration Tool</application>, the
+ <command>redhat-config-keyboard</command> RPM package must be installed.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ Directory names must end with a forward slash
+ (<computeroutput>/</computeroutput>) to distinguish them from file
+ names.
+ </para>
+ </note>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-firstterm">
+ <title><command>firstterm</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>firstterm</secondary>
+ </indexterm>
+
+ <para>
+ The <command><firstterm></command> and
+ <command></firstterm></command> tags helps to define a word that
+ may be unfamiliar to the user, but that will be seen commonly throughout
+ the text. For example:
+ </para>
+<screen>
+<computeroutput>
+Nearly every modern-day operating system uses <firstterm>disk
+partitions</firstterm>, and &DISTRO; is no exception.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Nearly every modern-day operating system uses <firstterm>disk
+ partitions</firstterm>, and &DISTRO; is no exception.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-footnote">
+ <title><command>footnote</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>footnote</secondary>
+ </indexterm>
+
+ <para>
+ If you need to make a footnote, use the following example:
+ </para>
+<screen>
+<computeroutput>
+For those of you who need to perform a server-class
+<footnote>
+<para>
+A server-class installation sets up a typical server
+environment. Note, no graphical environment is
+installed during a server-class installation.
+</para>
+</footnote> installation, refer to the <citetitle>Installation Guide</citetitle>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ For those of you who need to perform a server-class <footnote> <para>A
+ server-class installation sets up a typical server environment. Please note, no
+ graphical environment is installed during a server-class installation.</para>
+ </footnote> installation, refer to the
+ <citetitle>Installation Guide</citetitle>.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-figure">
+ <title><command>figure</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>figure</secondary>
+ </indexterm>
+
+ <important>
+ <title>Important</title>
+ <para>
+ Order matters! The EPS file <emphasis>must</emphasis> be declared
+ first.
+ </para>
+ </important>
+
+ <para>
+ An example figure declaration:
+ </para>
+
+<screen>
+<computeroutput>
+<figure id="fig-ksconfig-basic">
+ <title>Basic Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.eps"
+ format="EPS"/>
+ </imageobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.png"
+ format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>
+ Some text description of this image
+ </phrase>
+ </textobject>
+ </mediaobject>
+</figure>
+</computeroutput>
+</screen>
+
+ <para>
+ The following describes what needs to be edited:
+ </para>
+
+<screen>
+<figure id="fig-ksconfig-basic"> <emphasis>==> id="" would be edited</emphasis>
+
+<title>Basic Configuration</title> <emphasis>==> title would be edited</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.eps"> <emphasis>==> .eps location would be edited</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.png"> <emphasis>==> .png location would be edited</emphasis>
+
+<phrase>Some text description of this image</phrase> <emphasis>==> "Some text..." would be edited</emphasis>
+</screen>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-gui">
+ <title>GUI Tags</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ </indexterm>
+
+ <sect2 id="s2-xml-tags-guilabel">
+ <title><command>guilabel</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guilabel</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guilabel</secondary>
+ </indexterm>
+
+ <para>
+ Use the <command><guilabel></command> and
+ <command></guilabel></command> tags as a default for GUI
+ descriptions, like a screen name or screen title. For example:
+ </para>
+<screen>
+<computeroutput>
+The <guilabel>Authentication Configuration</guilabel> screen
+shows you how to make your system more secure.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ The <guilabel>Authentication Configuration</guilabel> screen shows you how to
+ make your system more secure.
+ </para>
+ </sect2>
+
+ <sect2 id="s2-xml-tags-guibutton">
+ <title><command>guibutton</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guibutton</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guibutton</secondary>
+ </indexterm>
+
+ <para>
+ Use the <command><guibutton></command> and
+ <command></guibutton></command> tags to denote a button on a screen or
+ menu. For example:
+ </para>
+<screen>
+<computeroutput>
+Check the <guibutton>Activate on boot</guibutton> button
+to have the X Window System start automatically.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Check the <guibutton>Activate on boot</guibutton> button to have the X
+ Window System start automatically.
+ </para>
+ </sect2>
+
+ <sect2 id="s2-xml-tags-guiicon">
+ <title><command>guiicon</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guiicon</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guiicon</secondary>
+ </indexterm>
+
+ <para>
+ The <command><guiicon></command> and <command></guiicon></command>
+ tags are used to denote a panel or desktop icon. For example:
+ </para>
+<screen>
+<computeroutput>
+Double-click the <guiicon>Start Here</guiicon> icon on the desktop.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Double-click the <guiicon>Start Here</guiicon> icon on the desktop.
+ </para>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-guimenu">
+ <title><command>guimenu</command> and
+ <command>guimenuitem</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guimenu</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guimenu</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guimenuitem</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guimenuitem</secondary>
+ </indexterm>
+
+ <para>
+ To note a menu (like in the installation program or within the control panel),
+ use the <command><guimenu></command> and
+ <command></guimenu></command> tags.
+ </para>
+
+ <para>
+ To note submenu items, use the <command><guimenuitem></command> and
+ <command></guimenuitem></command> tags. (Please note that there should not
+ be any breaks between these commands, but for printing purposes breaks have been
+ inserted). For example:
+ </para>
+<screen>
+<computeroutput>
+Select
+<guimenu>Main Menu</guimenu> =>
+ <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> to start the
+<application>Emacs</application> text editor.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ From the control panel, click on <guimenu>Main Menu</guimenu> =>
+ <guimenuitem>Programming</guimenuitem> =>
+ <guimenuitem>Emacs</guimenuitem> to start the
+ <application>Emacs</application> text editor.
+ </para>
+ </sect2>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-keycap">
+ <title><command>keycap</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>keycap</secondary>
+ </indexterm>
+
+ <para>
+ To denote a specific key, you will need to use the
+ <command><keycap></command> and <command></keycap></command>
+ tags. Brackets are automatically added around the keycap, so do not add
+ them in your XML code. For example:
+ </para>
+<screen>
+<computeroutput>
+To make your selection, press the <keycap>Enter</keycap> key.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ To make your selection, press the <keycap>Enter</keycap> key.
+ </para>
+
+ <sect2 id="s2-xml-tags-menuchoice">
+ <title><command>menuchoice</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>menuchoice</secondary>
+ </indexterm>
+
+ <para>
+ Often using a mouse is tedious for common tasks. Therefore,
+ programmers often build in keyboard-shortcuts to simplify their
+ program. These should be described using the shortcut tag as a wrapper
+ for the keyboard tags. The shortcut tag must be wrapped inside the
+ menuchoice tag. For example:
+ </para>
+
+<screen>
+<computeroutput>
+Go to the menu bar and choose:
+ <menuchoice>
+ <shortcut>
+ <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
+ </shortcut>
+ <guimenu><accel>F</accel>ile</guimenu>
+ <guimenuitem><accel>S</accel>ave</guimenuitem>
+ </menuchoice>.
+</computeroutput>
+</screen>
+
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Go to the menu bar and choose:
+ <menuchoice>
+ <shortcut>
+ <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
+ </shortcut>
+ <guimenu><accel>F</accel>ile</guimenu>
+ <guimenuitem><accel>S</accel>ave</guimenuitem>
+ </menuchoice>.
+ </para>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-keycombo">
+ <title><command>keycombo</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>keycombo</secondary>
+ </indexterm>
+
+ <para>
+ To illustrate a key combination, you need to use the
+ <command><keycombo></command> and
+ <command></keycombo></command>,
+ <command><keycap></command> and
+ <command></keycap></command> tags. For example:
+ </para>
+<screen>
+<computeroutput>
+To reboot your system, press <keycombo>
+<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>
+</keycombo>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ To reboot your system, press
+ <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>
+ </keycombo>.
+ </para>
+
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-lists">
+ <title>Lists</title>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary>creating</secondary>
+ </indexterm>
+
+ <para>There are several types of lists you can create using XML. You
+ can have a itemized (bulleted) list, a ordered (numbered) list, or a
+ variable list (presents a term and then a separate paragraph).</para>
+
+ <para>There is also a list format for tables and for for creating a
+ list of glossary terms and their definitions.</para>
+
+ <para>The sections below will discuss the proper uses for the various
+ list and how to create them.</para>
+
+ <sect2 id="s2-xml-tags-itemizedlist">
+ <title><command>itemizedlist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>itemizedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>itemizedlist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>itemizedlist</command></secondary>
+ </indexterm>
+
+ <para>An <command>ItemizedList</command> is best used to present
+ information that is important for the reader to know, but that does
+ not need to be in a specific order. It is shorter than a
+ <command>VariableList</command> and presents the information in a
+ very simple way.</para>
+
+ <para>To create an <command>ItemizedList</command> (otherwise known as
+ bulleted list), use the following command sequence:</para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command>
+ tags. If you do not do this, you will find extra whitespace in
+ your lists where the text does not line up correctly. This is most
+ noticeable when you have a series of list items that consist of
+ multiple lines of text. This whitespace is not as noticeable in
+ the HTML output as it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<itemizedlist>
+ <listitem>
+ <para>Getting familiar with the installation program's user interface</para>
+ </listitem>
+
+ <listitem>
+ <para>Starting the installation program</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting an installation method</para>
+ </listitem>
+</itemizedlist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Getting familiar with the installation program's user interface</para>
+ </listitem>
+
+ <listitem>
+ <para>Starting the installation program</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting an installation method</para>
+ </listitem>
+ </itemizedlist>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-orderedlist">
+ <title><command>OrderedList</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>orderedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>orderedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>orderedlist</tertiary>
+ </indexterm>
+
+ <para>An <command>orderedlist</command> is best used to present
+ information that is important for the reader to know in a specific
+ order. <command>orderedlist</command>s are a good way to convey
+ step-by-step senarios to the audience you are writing for.</para>
+
+ <para>
+ To create an <command>orderedlist</command> (numbered list), use the
+ following XML code sequence:
+ </para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command>
+ tags. If you do not do this, you will find extra whitespace in
+ your lists where the text does not line up correctly. This is most
+ noticeable when you have a series of list items that consist of
+ multiple lines of text. This whitespace is not as noticeable in
+ the HTML output as it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<orderedlist>
+ <listitem>
+ <para>Online &mdash; http://www.redhat.com/support/errata; supplies errata
+ you can read online, and you can download diskette images
+ easily.</para>
+ </listitem>
+
+ <listitem>
+ <para>Email &mdash; By sending an empty mail message to errata@@redhat.com,
+ you will receive an email containing a text listing of the
+ complete errata of the installation program and related software
+ (if errata exist at that time). Also included are URLs to each
+ updated package and diskette image in the errata. Using these
+ URLs, you can download any necessary diskette images. Please
+ note: use binary mode when transferring a diskette image.</para>
+ </listitem>
+</orderedlist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <orderedlist>
+ <listitem>
+ <para>Online — http://www.redhat.com/support/errata; supplies errata
+ you can read online, and you can download diskette images
+ easily.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Email — By sending an empty mail message to
+ errata@@redhat.com, you will receive an email containing a text
+ listing of the complete errata of the installation program and
+ related software (if errata exist at that time). Also included
+ are URLs to each updated package and diskette image in the
+ errata. Using these URLs, you can download any necessary
+ diskette images. Please note: use binary mode when transferring
+ a diskette image.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-varlist">
+ <title><command>Variablelist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>variablelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>variablelist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>variablelist</command></secondary>
+ </indexterm>
+
+ <para>A <command>variablelist</command> best represents a list of
+ terms and definitions or descriptions for those terms.</para>
+
+ <para>To create a <command>variablelist</command>, use the following
+ command sequence:
+ </para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command> tags. If
+ you do not do this, you will find extra whitespace in your lists
+ where the text does not line up correctly. This is most noticeable
+ when you have a series of list items that consist of multiple lines
+ of text. This whitespace is not as noticeable in the HTML output as
+ it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<variablelist>
+ <varlistentry>
+ <term> New Multi-CD Install </term>
+ <listitem>
+ <para>As the installation program continues to grow, Red Hat has developed
+ an installation program capable of installing from
+ multiple CD-ROMs.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>XFree 4.0 </term>
+ <listitem>
+ <para>Configuration of your X Window System during the installation has
+ never been more thorough. From choosing your monitor and its correct
+ settings, to video card probing, to testing your desired X setup,
+ Xconfigurator will help you set everything just right.</para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <variablelist>
+ <varlistentry>
+ <term>New Multi-CD Install</term> <listitem> <para>As the
+ installation program continues to grow, Red Hat has developed an
+ installation program capable of installing from
+ multiple CD-ROMs.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term> XFree 4.0</term>
+ <listitem>
+ <para>Configuration of your X Window System during the
+ installation has never been more thorough. From choosing your
+ monitor and its correct settings, to video card probing, to
+ testing your desired X setup, Xconfigurator will help you set
+ everything just right.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ Do <emphasis>not</emphasis> specify the
+ <computeroutput>frame</computeroutput> attribute to the table. Doing
+ so breaks PDF production.
+ </para>
+ </warning>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-simplelist">
+ <title>Creating a List Within a Table Using <command>Simplelist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>simplelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>simplelist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>simplelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>tables</primary>
+ <secondary>creating a list within a table</secondary>
+ <tertiary><command>simplelist</command></tertiary>
+ </indexterm>
+
+ <para>A <command>simplelist</command> is an unadorned list of
+ items. <command>simplelist</command>s can be inline or arranged in
+ columns.</para>
+
+ <para>We use <command>simplelist</command> to add separate paragraphs
+ of text within a table element. A regular list, such as
+ <command>itemizedlist</command>, cannot be embedded within a table.</para>
+
+ <para>The XML commands for a table look like:</para>
+
+<screen>
+<computeroutput>
+ <table id="tb-hwinfo-hostbus">
+ <title>Host Bus Adapter Features and Configuration Requirements</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="HostBus" colwidth="33"/>
+ <colspec colnum="2" colname="Features" colwidth="34"/>
+ <colspec colnum="3" colname="Single" colwidth="33"/>
+
+ <thead>
+ <row>
+ <entry>Host Bus Adapter</entry>
+ <entry>Features</entry>
+ <entry>Single-Initiator Configuration</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is
+ off.</member>
+ </simplelist></entry>
+
+ <entry><simplelist>
+ <member>Set the onboard termination to automatic (the
+ default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ <row>
+ <entry>Qlogic QLA1080</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is off,
+ unless jumpers are used to enforce termination.</member>
+ </simplelist></entry>
+
+
+ <entry><simplelist>
+ <member>Set the onboard termination to
+ automatic (the default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <table id="tb-hwinfo-hostbus">
+ <title>Host Bus Adapter Features and Configuration Requirements</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="HostBus" colwidth="33"/>
+ <colspec colnum="2" colname="Features" colwidth="34"/>
+ <colspec colnum="3" colname="Single" colwidth="33"/>
+
+ <thead>
+ <row>
+ <entry>Host Bus Adapter</entry>
+ <entry>Features</entry>
+ <entry>Single-Initiator Configuration</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is
+ off.</member>
+ </simplelist></entry>
+
+ <entry><simplelist>
+ <member>Set the onboard termination to automatic (the
+ default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ <row>
+ <entry>Qlogic QLA1080</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is off,
+ unless jumpers are used to enforce termination.</member>
+ </simplelist></entry>
+
+
+ <entry><simplelist>
+ <member>Set the onboard termination to
+ automatic (the default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+ <note>
+ <title>Note</title>
+ <para>Notice how the <command>SimpleList</command> tags are
+ used. The <entry> and <simplelist> tags must be aligned
+ beside one another, otherwise you will receive a parsing error.</para>
+ </note>
+
+ <para>For each paragraph or list item to be added within a
+ <command>SimpleList</command>, the <member> tag set must be
+ added around that particular text item.</para>
+ </sect2>
+
+ <sect2 id="s2-xml-tags-glossary">
+ <title><command>glosslist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>glosslist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>glosslist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>glosslist</command></secondary>
+ </indexterm>
+
+ <para>Use the <command>glosslist</command> command set to create a
+ list of glossary terms and their definitions.</para>
+
+
+ <para>In XML, an example looks like the following:</para>
+
+<screen>
+<computeroutput>
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>A small application, usually a utility or other
+ simple program.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>The design for organization and integration of
+ components within a computer or computer system.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>To transfer files into storage for the purpose of
+ saving space and/or organization.</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+</computeroutput>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>A small application, usually a utility or other simple program.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>The design for organization and integration of components
+ within a computer or computer system.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>To transfer files into storage for the purpose of saving
+ space and/or organization.</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+
+ </sect2>
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-option">
+ <title><command>option</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>option</secondary>
+ </indexterm>
+
+ <para>If you have a command that offers an option or a flag, use the
+ <command><option></command> and
+ <command></option></command> tags.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>The <option> tag set is only meant to be used for command
+ line options, not options in configuration files.</para>
+ </note>
+
+ <para>In XML, specifying an option would look like the
+ following:</para>
+
+<screen>
+<computeroutput>
+For example, with the command <command>ls</command> you can
+specify an option such as <option>-la</option>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>For example, with the command <command>ls</command> you can
+ specify an option such as <option>-la</option>.</para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-indexing">
+ <title>Index Entries</title>
+
+ <indexterm>
+ <primary>indexing</primary>
+ </indexterm>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>indexing</secondary>
+ </indexterm>
+
+ <para>The following command sequence shows you the code inserted into
+ the body of the text to add an index entry to your document:
+ </para>
+
+<screen>
+<computeroutput>
+<indexterm> <-- indicates a term to be placed in the index
+<primary>foo</primary> <-- indicates that "foo" is the first term
+<secondary>bar</secondary> <-- "bar" will be listed under "foo"
+</indexterm> <-- closes this index entry
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>foo</primary>
+ <secondary>bar</secondary>
+ </indexterm>
+
+
+ <para>The <command><seealso></command> tag allows you to
+ reference another index entry or refer to another manual. Make sure
+ the <command><seealso></command> reference you are pointing to
+ has its own entry. For example:
+ </para>
+
+ <indexterm>
+ <primary>indexing</primary>
+ <secondary>seealso tag</secondary>
+ </indexterm>
+
+<screen>
+<computeroutput>
+<indexterm>
+<primary>SWAK</primary>
+<seealso>salutations</seealso>
+</indexterm>
+
+
+<indexterm>
+<primary>salutations</primary>
+</indexterm>
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>SWAK</primary>
+ <seealso>Salutations</seealso>
+ </indexterm>
+
+ <indexterm>
+ <primary>Salutations</primary>
+ </indexterm>
+
+ <para>
+ The <command><see></command> tag allows you to reference to
+ another index entry entirely. For example:
+ </para>
+ <indexterm>
+ <primary>indexing</primary>
+ <secondary>see tag</secondary>
+ </indexterm>
+
+
+<screen>
+<computeroutput>
+<indexterm>
+<primary>Guinness</primary>
+<see>beer</see> <-- beer will be listed under
+the Guinness entry, but you must make sure beer also has its
+own entry to refer to.
+</indexterm>
+
+<indexterm>
+<primary>beer</primary>
+</indexterm>
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>Guinness</primary>
+ <see>Beer</see>
+ </indexterm>
+
+ <indexterm>
+ <primary>Beer</primary>
+ </indexterm>
+
+ <para>To view the HTML output of the index entries shown here, refer
+ to the <filename>generated-index.html</filename> file at the end of
+ this document.</para>
+
+<!--
+ <tip>
+ <title>Tip</title>
+ <para>
+ To learn more about the rules of indexing, refer to <xref
+ linkend="ch-indexing"></xref>.
+ </para>
+ </tip>
+-->
+ </sect1>
+
+ <sect1 id="s1-xml-tags-para">
+ <title><command>para</command></title>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>para</secondary>
+ </indexterm>
+
+ <para>For any paragraph, the <command><para></command> and
+ <command></para></command> tags must open and close that
+ particular paragraph.
+ </para>
+
+ <sect2 id="s2-xml-tags-para">
+ <title>Additional Rules for the <command><para></command> Tag
+ Set</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>para</secondary>
+ <tertiary>additional rules</tertiary>
+ </indexterm>
+
+ <variablelist>
+ <varlistentry>
+ <term>Proper formatting of <command><para></command> tag and
+ text</term>
+ <listitem>
+ <para>Additionally, the <command><para></command> tags
+ should be justified around the paragraph so that the opening
+ <command><para></command> tag and the first word of that
+ paragraph are side by side. For example:</para>
+
+<screen>
+<computeroutput>
+<command><para></command>This paragraph talk about using the <para>
+tag correctly.<command><para></command>
+</computeroutput>
+</screen>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Where not to use <command><para></command> tags</term>
+ <listitem>
+ <para>Do not use para tags around anything other than a simple
+ paragraph. Doing so will create additional white space within
+ the text itself.</para>
+
+ <para>Do not use <command><para></command> tags around the
+ following (or, to put this another way, do not embed the
+ following within <command><para></command> tags):</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><command><screen></command></para>
+ </listitem>
+ <listitem>
+ <para><command><itemizedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><orderedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><variablelist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><table></command></para>
+ </listitem>
+ </itemizedlist>
+
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-part">
+ <title><command>part</command></title>
+
+ <indexterm>
+ <primary>parts</primary>
+ </indexterm>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>part</secondary>
+ </indexterm>
+
+ <para>
+ In the parent file, you can separate the chapters into parts to divide
+ them into logical groups. For example, in the parent file, the
+ <command>part</command> tags surround the chapter entities:
+ </para>
+<screen>
+<computeroutput>
+<part id="pt-foo">
+ <partintro>
+ <para>Some text for the part intro</para>
+ &CHAPTER;
+
+ &ANOTHER-CHAPTER;
+</part>
+</computeroutput>
+</screen>
+
+ <para>
+ If you create a part, include a part introduction describing the
+ contents of the part. For example:
+ </para>
+
+<screen>
+<computeroutput>
+ <part id="pt-setup">
+ <title>Getting Setup</title>
+ <partintro>
+ <para>This section contains information you will need when you first join
+ the Docs group. You might need to refer to this part again for
+ information such as installing &DISTRO;.</para>
+ </partintro>
+</computeroutput>
+</screen>
+
+ <para>
+ In the HTML output, a separate HTML page is generated with the part
+ number, title, introduction, and TOC. In the PDF output, the same
+ information about the part is on a separate page.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-prompt">
+ <title><command>prompt</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>prompt</secondary>
+ </indexterm>
+
+ <para>
+ To show a prompt, such as a root or DOS prompt, use the
+ <command><prompt></command> and <command></prompt></command>
+ commands. For example:
+ </para>
+<screen>
+<computeroutput>
+At the <prompt>LILO:</prompt> boot prompt, type linux to
+boot into your Linux partition.
+
+At the <prompt>C:\></prompt> prompt, type ....
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ At the <prompt>LILO:</prompt> boot prompt, type linux to boot into your
+ Linux partition.
+ </para>
+ <para>
+ At the <prompt>C:\></prompt> prompt, type ....
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ When showing example computer output (usually in
+ <command>screen</command> tags), do you include the prompt or command
+ (unless the command or prompt is the actually computer output you want
+ to show).</para>
+ </note>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-replaceable">
+ <title><command>replaceable</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>replaceable</secondary>
+ </indexterm>
+
+ <para>
+ To create replaceable text, you use the tags
+ <command><replaceable></command> and
+ <command></replaceable></command> around the text you want to use as a
+ variable.
+ </para>
+ <para>
+ This example shows the ISBN of our boxed sets with variables:
+ </para>
+<screen>
+<computeroutput>
+1-58569-<replaceable>xx</replaceable>-<replaceable>y</replaceable>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ 1-58569-<replaceable>xx</replaceable>-<replaceable>y</replaceable>
+ </para>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-screen">
+ <title><command>screen</command></title>
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>screen</secondary>
+ </indexterm>
+
+ <para>
+ The <command><screen></command> command is used to format text
+ within a document and is great for adding emphasis to show examples of
+ code, computer output, and more. In HTML, this appears in a grey
+ background. To use this command you only need the opening
+ <command><screen></command> and closing
+ <command></screen></command> tags around the text you are
+ emphasizing.
+ </para>
+
+ <important>
+ <title>Important</title> <para>When using the
+ <command><screen></command> tag, you must set everything within
+ that screen, including the <command><screen></command> tags
+ themselves, to flush left. This must be done so that when it is
+ converted to HTML, it will not have extra blank space in front of it
+ inside the gray background.</para>
+ </important>
+
+
+ <para>
+ An example of <command><screen></command> is the following:
+ </para>
+<screen>
+<computeroutput>
+<screen>
+<computeroutput>
+This is an example of a screen. You do not need <para> tags
+within this command.
+</computeroutput>
+</screen>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+<screen>
+<computeroutput>
+This is an example of a screen. You do not need <command><para></command>
+tags within this command.
+</computeroutput>
+</screen>
+
+ <note>
+ <title>Note</title> <para>To properly use the
+ <command><screen></command> tag set, you also need to properly
+ tag the content within the screen. If the content in the screen is a
+ configuration file or the output of a program, it needs the
+ <command><computeroutput></command> tag set. If it is a command,
+ it needs the <command><command></command> tag set. If it is a
+ command with user input, it may require a construction like the one
+ below:</para>
+<screen>
+<command><command></command>command <command><userinput></command>input<command></userinput></command><command></command></command>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+<screen>
+<command>command <userinput>input</userinput></command>
+</screen>
+ </note>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-sections">
+ <title>Sections</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>sections</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>sections</primary>
+ </indexterm>
+
+ <para>Within an article (or chapter if it is a DocBook XML book like the
+ <citetitle>&IG;</citetitle>), you can have sections and
+ subsections. <command><sect1></command> is always the highest
+ section and you cannot have two sections of the same level within one
+ another (a section 2 can be created within a section 1, but section 1
+ has to be closed before another section 1 can be created). The general
+ layout follows:</para>
+
+<screen>
+<computeroutput>
+<sect1 id="s1-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+
+ <sect2 id="s2-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+ <sect3 id="s3-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+ </sect3>
+
+ </sect2>
+
+</sect1>
+</computeroutput>
+</screen>
+
+ <para>
+ If you only need one level of sections in a DocBook article, you can use
+ the <command>section</command> tag. For example:
+ </para>
+
+<screen>
+<computeroutput>
+<section id="sn-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+</section>
+<section id="sn-anothername">
+ <title>Insert Title Here</title>
+ <para>
+ More body text goes here.
+ </para>
+</section>
+</computeroutput>
+</screen>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-table">
+ <title><command>table</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>table</secondary>
+ </indexterm>
+
+ <para>
+ The following is an example of creating a table.
+ </para>
+
+<screen>
+<table id="tb-mockup-before-begin">
+ <emphasis>This tells XML that you will be creating a table
+ and the ID name is <command>"tb-mockup-before-begin."</command></emphasis>
+
+<title>Available Features of GNOME and KDE</title>
+
+<tgroup cols="3">
+ <emphasis>This tells XML that you are creating a table
+ with three columns.</emphasis>
+
+<colspec colnum="1" colname="Features" colwidth="3"/>
+ <emphasis><command>colspec</command> says that you are giving information
+ about the column to XML</emphasis> <emphasis><command>colnum="1"</command>
+ says that you are giving specifications for the first column.</emphasis>
+
+ <emphasis><command>colname="Features"</command> says that the title for this
+ column will be "Features."</emphasis>
+
+ <emphasis><command>colwidth="3"</command> specifies the width of the
+ column. This can be more tricky: such as two columns with
+ widths of 1 and 2,the 1 is one-half the width of the 2, in
+ respect to the page size. But, what if you need the 1 to be a
+ little more than half of the 2, using a larger number ratio,
+ such as 10 to 20 would accomplish this. You could then change the
+ 10 to an 11 or a 12 to make it a little more than half of the
+ second column of 20. In no value is given, a value of 1 is
+ assumed.</emphasis>
+
+<colspec colnum="2" colname="GNOME" colwidth="2"/>
+<colspec colnum="3" colname="KDE" colwidth="2"/>
+
+<thead>
+ <emphasis>Contains one or more table row elements.</emphasis>
+
+<row>
+ <emphasis>Contains one or more table cell (entry) elements.</emphasis>
+
+<entry>Features</entry>
+ <emphasis>Table cell element, one of several in a row element, defining
+ columns within the row.</emphasis>
+
+<entry>GNOME</entry>
+<entry>KDE</entry>
+</row>
+</thead>
+
+<tbody>
+ <emphasis>Contains one or more row elements, for the main text
+ of the table.</emphasis>
+
+<row>
+<entry>highly configurable</entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>multiple window managers </entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>Internet applications</entry>
+<entry>yes </entry>
+<entry>yes </entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+</screen>
+
+ <table id="tb-mockup-before-begin">
+ <title>Available Features of GNOME and KDE</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="Features" colwidth="3"/>
+ <colspec colnum="2" colname="GNOME" colwidth="2"/>
+ <colspec colnum="3" colname="KDE" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Features </entry>
+ <entry>GNOME</entry>
+ <entry>KDE</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry>highly configurable</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>multiple window managers </entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>Internet applications</entry>
+ <entry>yes </entry>
+ <entry>yes </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <sect2 id="s2-xml-tags-listintable">
+ <title>Creating a List Within a Table</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>table</secondary>
+ <tertiary>list within a table</tertiary>
+ </indexterm>
+
+
+ <para>Creating a list within a table can be a difficult task. It
+ requires strict formatting and a set of commands that are not
+ available for command completion in
+ <application>Emacs</application>.</para>
+
+ <para>The tags you will need to use are
+ <command><simplelist></command> and
+ <command><member></command>.</para>
+
+ <para>The following example will show you the proper formatting for
+ creating a list within a table.</para>
+
+
+<screen>
+<computeroutput>
+<table id="tb-hardware-powerswitch">
+ <title>Power Switch Hardware Table</title>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="Hardware" colwidth="2"/>
+ <colspec colnum="2" colname="Quantity" colwidth="2"/>
+ <colspec colnum="3" colname="Description" colwidth="6"/>
+ <colspec colnum="4" colname="Required" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>Description</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Serial power switches</entry>
+
+ <entry>Two</entry>
+
+ <entry><simplelist> <member>Power switches enable each cluster system
+ to power-cycle the other cluster system. Note that clusters are
+ configured with either serial or network attached power switches and
+ not both.</member>
+
+ <member>The following serial attached power switch has been
+ fully tested:</member>
+
+ <member>RPS-10 (model M/HD in the US, and model M/EC in
+ Europe) </member>
+
+ <member>Latent support is provided for the following serial
+ attached power switch. This switch has not yet been fully
+ tested:</member>
+
+ <member>APC Serial On/Off Switch (partAP9211), <ulink
+ url="http://www.apc.com/">http://www.apc.com/</ulink></member>
+ </simplelist></entry>
+
+ <entry>Strongly recommended for data integrity under all failure
+ conditions</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+</table>
+</computeroutput>
+</screen>
+
+ <para>Notice how the <command><simplelist></command> tag must be
+ beside the <command><entry></command> tag? If you do not format
+ this properly, it will not parse cleanly.</para>
+
+ <para>The above example will look like the following:</para>
+
+ <table id="tb-hardware-powerswitch">
+ <title>Power Switch Hardware Table</title>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="Hardware" colwidth="2"/>
+ <colspec colnum="2" colname="Quantity" colwidth="2"/>
+ <colspec colnum="3" colname="Description" colwidth="6"/>
+ <colspec colnum="4" colname="Required" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>Description</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Serial power switches</entry>
+
+ <entry>Two</entry>
+
+ <entry><simplelist> <member>Power switches enable each cluster
+ system to power-cycle the other cluster system. Note
+ that clusters are configured with either serial or
+ network attached power switches and not both.</member>
+
+ <member>The following serial attached power switch has been
+ fully tested:</member>
+
+ <member>RPS-10 (model M/HD in the US, and model M/EC in
+ Europe) </member>
+
+ <member>Latent support is provided for the following
+ serial attached power switch. This switch has not yet
+ been fully tested:</member>
+
+ <member>APC Serial On/Off Switch (partAP9211), <ulink
+ url="http://www.apc.com/">http://www.apc.com/</ulink></member>
+ </simplelist></entry>
+
+ <entry>Strongly recommended for data integrity under all failure
+ conditions</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-trademark">
+ <title><command>trademark</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>trademark</command></secondary>
+ </indexterm>
+
+
+ <para>Do not use the trademark entities &trade;, &copy;, or
+ &reg; because the do not produce HTML output that works for all
+ charsets. The HTML output produces by these entities are declared in
+ the DTD and cannot be changed via the stylesheet.</para>
+
+ <para>Instead, use the <command>trademark</command> tag and its
+ associates classes as follows:
+ </para>
+
+<screen>
+<computeroutput>
+<trademark>trademark symbol after me</trademark>
+<trademark class="registered">registered trademark symbol after me</trademark>
+<trademark class="copyright">copyright symbol after me</trademark>
+</computeroutput>
+</screen>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-userinput">
+ <title><command>userinput</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>userinput</command></secondary>
+ </indexterm>
+
+ <para>
+ To show what a user would type, use the <command>userinput</command>
+ tag. For example:
+ </para>
+<screen>
+<computeroutput>
+At the prompt, type:
+
+<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ At the prompt, type:
+ </para>
+
+ <para>
+ <userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+ </para>
+ </sect1>
+
+
+<!-- <sect1 id="s1-xml-tags-mouse">
+ <title><command>mousebutton</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>mousebutton</secondary>
+ </indexterm>
+ <para>
+Describe mouse actions with the mousebutton tag. Below is an example of its use.
+</para>
+
+<screen>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+</screen>
+
+ <para>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+ </para>
+
+ </sect1> -->
+
+ <sect1 id="s1-xml-tag-sulink">
+ <title><command>ulink</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>ulink</secondary>
+ </indexterm>
+
+ <para>
+ To create a URL link within your text, use the following example:
+ </para>
+<screen>
+<computeroutput>
+Online &mdash; <ulink url="http://www.redhat.com/support/errata/">
+http://www.redhat.com/support/errata/</ulink>; supplies errata
+you can read online, and you can download diskette images easily.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Online — <ulink url="http://www.redhat.com/support/errata/">
+ http://www.redhat.com/support/errata/</ulink>; supplies errata
+ you can read online, and you can download diskette images easily.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ If the URL does not end in a filename, it must end in a slash
+ (<computeroutput>/</computeroutput>) to be a properly formed URL. For
+ example, <ulink
+ url="http://www.redhat.com/">http://www.redhat.com/</ulink>.
+ </para>
+ </note>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-wordasword">
+ <title><command>wordasword</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>wordasword</secondary>
+ </indexterm>
+
+ <para>The <wordasword> tag set is used to define a word meant
+ specifically as a word and not representing anything else.</para>
+
+ <para>A lot of technical documentation contains words that have overloaded
+ meanings. Sometimes it is useful to be able to use a word without invoking
+ its technical meaning. The <wordasword> element identifies a word or
+ phrase that might otherwise be interpreted in some specific way, and
+ asserts that it should be interpreted simply as a word.</para>
+
+ <para>It is unlikely that the presentation of this element will be able to
+ help readers understand the variation in meaning; good writing will have
+ to achieve that goal. The real value of <wordasword> lies in the
+ fact that full-text searching and indexing tools can use it to avoid
+ false-positives.</para>
+
+ <para>For example:</para>
+
+<screen>
+<computeroutput>To use <command>grep</command> to search for the word
+<wordasword>linux</wordasword>, use the command
+<command>grep linux</command>.</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>To use <command>grep</command> to search for the word
+ <wordasword>linux</wordasword>, use the command <command>grep
+ linux</command>.</para>
+
+ <para>In the example, the word "linux" is just a word. It is not
+ meant to convey anything about Linux as a subject, or to add relevance or
+ meaning to the content. It can be replaced with any other word without
+ losing any of the context.</para>
+
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-xref">
+ <title><command>xref</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>xref</secondary>
+ </indexterm>
+
+ <para>
+ To refer to other sections or chapters within a manual, use the
+ <command><xref></command> tag.
+ </para>
+
+ <para>
+ The output of this displays the title of the section or chapter you are
+ pointing the user to. For example:
+ </para>
+<screen>
+<computeroutput>
+For more information about the parent file, refer to
+<xref linkend="ch-tutorial"><xref> and <xref linkend="s1-tutorial-parent"></xref>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ For more information about the parent file, refer to <xref linkend="ch-tutorial"></xref>
+ and <xref linkend="s1-tutorial-parent"></xref>.
+ </para>
+ </sect1>
+
+ </chapter>
+@
+
+
+1.2
+log
+ at fix example figure tag, add ack chapter
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags.xml,v 1.4 2003/09/16 19:26:26 tfox Exp $ -->
+d194 1
+a194 1
+<!--$Id: docs-xml-tags.xml,v 1.4 2003/09/16 19:26:26 tfox Exp $ -->
+d594 1
+a594 1
+ format="eps">
+d598 1
+a598 1
+ format="png">
+d601 1
+a601 1
+ <para>
+d603 1
+a603 1
+ </para>
+d623 1
+a623 1
+<para>Some text description of this image</para> <emphasis>==> "Some text..." would be edited</emphasis>
+@
+
diff --git a/old-documentation-guide/Attic/documentation-guide-en.xml,v b/old-documentation-guide/Attic/documentation-guide-en.xml,v
new file mode 100644
index 0000000..3097cf8
--- /dev/null
+++ b/old-documentation-guide/Attic/documentation-guide-en.xml,v
@@ -0,0 +1,605 @@
+head 1.24;
+access;
+symbols
+ VERSION-0_2:1.8;
+locks; strict;
+comment @# @;
+
+
+1.24
+date 2006.11.23.20.36.46; author pfrields; state dead;
+branches;
+next 1.23;
+
+1.23
+date 2005.12.28.00.40.27; author pfrields; state Exp;
+branches;
+next 1.22;
+
+1.22
+date 2005.12.13.21.56.24; author jtr; state Exp;
+branches;
+next 1.21;
+
+1.21
+date 2005.09.19.00.00.31; author pfrields; state Exp;
+branches;
+next 1.20;
+
+1.20
+date 2005.08.24.20.37.35; author kwade; state Exp;
+branches;
+next 1.19;
+
+1.19
+date 2005.06.28.21.46.45; author pfrields; state Exp;
+branches;
+next 1.18;
+
+1.18
+date 2005.05.03.18.52.42; author kwade; state Exp;
+branches;
+next 1.17;
+
+1.17
+date 2005.04.28.08.55.41; author kwade; state Exp;
+branches;
+next 1.16;
+
+1.16
+date 2004.09.13.02.03.22; author tfox; state Exp;
+branches;
+next 1.15;
+
+1.15
+date 2004.09.04.09.39.20; author kwade; state Exp;
+branches;
+next 1.14;
+
+1.14
+date 2004.08.31.15.45.29; author tfox; state Exp;
+branches;
+next 1.13;
+
+1.13
+date 2004.08.13.16.08.48; author tfox; state Exp;
+branches;
+next 1.12;
+
+1.12
+date 2004.08.13.15.35.53; author tfox; state Exp;
+branches;
+next 1.11;
+
+1.11
+date 2004.08.12.21.04.10; author tfox; state Exp;
+branches;
+next 1.10;
+
+1.10
+date 2004.03.18.20.25.16; author tfox; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2004.03.11.17.30.39; author tfox; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2004.02.24.19.06.50; author tfox; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2004.02.24.17.17.31; author tfox; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2004.02.24.17.03.35; author tfox; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2004.01.19.23.14.46; author tfox; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2003.11.25.21.03.40; author tfox; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2003.11.21.22.40.39; author tfox; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2003.10.15.18.11.01; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.24
+log
+ at Remove old en locale parent file too
+@
+text
+@<!-- $Id: documentation-guide-en.xml,v 1.23 2005/12/28 00:40:27 pfrields Exp $ -->
+<!-- breaks the build ... <?xml version="1.0" encoding="utf-8"?> -->
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
+%FEDORA-ENTITIES-EN;
+
+<!ENTITY VERSION "0.2.6.3"> <!-- version for this document -->
+
+<!ENTITY DOCID "documentation-guide-&VERSION; (2005-09-18)"> <!-- change date here and VERSION entity everytime a change is made-->
+
+<!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
+
+<!ENTITY INTRODUCTION SYSTEM "docs-intro-en.xml">
+
+<!ENTITY GETTINGFILES SYSTEM "docs-getting-files-en.xml">
+<!ENTITY GUIDELINES SYSTEM "docs-rh-guidelines-en.xml">
+<!ENTITY EMACS SYSTEM "docs-emacs-en.xml">
+<!ENTITY EMACS-NXML SYSTEM "docs-emacs-nxml-en.xml">
+<!ENTITY VIM SYSTEM "docs-vim-en.xml">
+<!ENTITY TAGS SYSTEM "docs-xml-tags-en.xml">
+<!ENTITY TUTORIAL SYSTEM "docs-tutorial-en.xml">
+<!ENTITY CVS SYSTEM "../docs-common/common/cvs-en.xml">
+<!ENTITY ACKNOWLEDGMENTS SYSTEM "acknowledgments-en.xml">
+<!ENTITY STYLE SYSTEM "docs-style-en.xml">
+
+]>
+
+<book id="documentation-guide" lang="en">
+ <bookinfo>
+ <title>&FP; Documentation Guide</title>
+ <subtitle>Version &VERSION;</subtitle>
+ <copyright>
+ <year>2003,2004,2005</year>
+ <holder>&FORMAL-RHI;</holder>
+ <holder>Tammy Fox</holder>
+ <holder>Johnray Fuller</holder>
+ <holder>Sandra Moore</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ <author>
+ <surname>Fuller</surname>
+ <firstname>Johnray</firstname>
+ </author>
+ <author>
+ <surname>Moore</surname>
+ <firstname>Sandra</firstname>
+ </author>
+ </authorgroup>
+ &LEGALNOTICE;
+ </bookinfo>
+
+
+ &INTRODUCTION;
+
+ &GETTINGFILES;
+
+ &GUIDELINES;
+
+ &EMACS;
+
+ &EMACS-NXML;
+
+ &VIM;
+
+ &TAGS;
+
+ &TUTORIAL;
+
+ &STYLE;
+
+ &CVS;
+
+ &ACKNOWLEDGMENTS;
+
+ <index id="generated-index"></index>
+</book>
+@
+
+
+1.23
+log
+ at Update to use new entity standards
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.22 2005/12/13 21:56:24 jtr Exp $ -->
+@
+
+
+1.22
+log
+ at Added documentation about the document building system. Dropped the
+one-line "converting" chapter by creating a "Prerequisites" section
+in the "getting-files" section.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.21 2005/09/19 00:00:31 pfrields Exp $ -->
+d12 1
+a12 1
+<!ENTITY BOOKID "documentation-guide-&VERSION; (2005-09-18)"> <!-- change date here and VERSION entity everytime a change is made-->
+@
+
+
+1.21
+log
+ at Fix CVS guidance for publication
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.20 2005/08/24 20:37:35 kwade Exp $ -->
+a24 1
+<!ENTITY CONVERTING SYSTEM "docs-converting-en.xml">
+a77 2
+ &CONVERTING;
+
+@
+
+
+1.20
+log
+ at Rolling version.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.19 2005/06/28 21:46:45 pfrields Exp $ -->
+d10 1
+a10 1
+<!ENTITY VERSION "0.2.6.2"> <!-- version for this document -->
+d12 1
+a12 1
+<!ENTITY BOOKID "documentation-guide-&VERSION; (2005-08-24)"> <!-- change date here and VERSION entity everytime a change is made-->
+@
+
+
+1.19
+log
+ at Fixed entity file references and Makefile
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.18 2005/05/03 18:52:42 kwade Exp $ -->
+d10 1
+a10 1
+<!ENTITY VERSION "0.2.6"> <!-- version for this document -->
+d12 1
+a12 1
+<!ENTITY BOOKID "documentation-guide-&VERSION; (2005-05-03)"> <!-- change date here and VERSION entity everytime a change is made-->
+d37 1
+a37 1
+ <year>2003,2004</year>
+@
+
+
+1.18
+log
+ at Updating version and date.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.17 2005/04/28 08:55:41 kwade Exp $ -->
+d7 1
+a7 1
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../common/fedora-entities-en.xml">
+d14 1
+a14 1
+<!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice-en.xml">
+d26 1
+a26 1
+<!ENTITY CVS SYSTEM "../common/cvs-en.xml">
+@
+
+
+1.17
+log
+ at This represents that state of the Doc Guide with Paul's Style chapter included, prior to _any_ editing from me.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.16 2004/09/13 02:03:22 tfox Exp $ -->
+d10 1
+a10 1
+<!ENTITY VERSION "0.2.5"> <!-- version for this document -->
+d12 1
+a12 1
+<!ENTITY BOOKID "documentation-guide-&VERSION; (2004-09-12)"> <!-- change date here and VERSION entity everytime a change is made-->
+d85 1
+a85 1
+<index id="generated-index"></index>
+@
+
+
+1.16
+log
+ at bump version and date
+@
+text
+ at d1 2
+a2 2
+<!-- $Id: documentation-guide-en.xml,v 1.15 2004/09/04 09:39:20 kwade Exp $ -->
+
+d6 1
+d28 1
+a28 1
+
+d77 2
+@
+
+
+1.15
+log
+ at DOCTYPE header missing the declaration of what type of DocBook is being called; bug # 131775.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.14 2004/08/31 15:45:29 tfox Exp $ -->
+d9 1
+a9 1
+<!ENTITY VERSION "0.2.4"> <!-- version for this document -->
+d11 1
+a11 1
+<!ENTITY BOOKID "documentation-guide-&VERSION; (2004-08-31)"> <!-- change date here and VERSION entity everytime a change is made-->
+@
+
+
+1.14
+log
+ at add instructions for screenshots
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.13 2004/08/13 16:08:48 tfox Exp $ -->
+d3 1
+a3 1
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
+@
+
+
+1.13
+log
+ at use common entities file
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.12 2004/08/13 15:35:53 tfox Exp $ -->
+d9 1
+a9 1
+<!ENTITY VERSION "0.2.3"> <!-- version for this document -->
+d11 1
+a11 1
+<!ENTITY BOOKID "documentation-guide-&VERSION; (2004-08-13)"> <!-- change date here and VERSION entity everytime a change is made-->
+@
+
+
+1.12
+log
+ at bump version and date
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.11 2004/08/12 21:04:10 tfox Exp $ -->
+d6 2
+a7 6
+<!ENTITY RH "Red Hat"> <!--The generic term "Red Hat" -->
+<!ENTITY FORMAL-RHI "&RH;, Inc."> <!--The generic term "Red Hat, Inc. -->
+<!ENTITY PROJECT "Fedora project"> <!-- Set the project name -->
+<!ENTITY NAME-TITLE "Fedora Project"> <!-- Set the project name, use for titles -->
+<!ENTITY DISTRO "Fedora Core"> <!-- Set the distro name -->
+<!ENTITY IG "&DISTRO; Installation Guide"> <!-- Always use for Installation Guide -->
+d33 1
+a33 1
+ <title>&NAME-TITLE; Documentation Guide</title>
+@
+
+
+1.11
+log
+ at add version entity and add version as subtitle
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.10 2004/03/18 20:25:16 tfox Exp $ -->
+d13 1
+a13 1
+<!ENTITY VERSION "0.2.2"> <!-- version for this document -->
+d15 1
+a15 1
+<!ENTITY BOOKID "documentation-guide-&VERSION; (2004-08-12)"> <!-- change date here and VERSION entity everytime a change is made-->
+@
+
+
+1.10
+log
+ at update bookdate and bump version after adding VIM
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.9 2004/03/11 17:30:39 tfox Exp $ -->
+d13 3
+a15 1
+<!ENTITY BOOKID "documentation-guide-0.2.1 (2004-03-18)"> <!-- change version of manual and date here -->
+d38 1
+@
+
+
+1.9
+log
+ at both should say 4.2
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.8 2004/02/24 19:06:50 tfox Exp $ -->
+d13 1
+a13 1
+<!ENTITY BOOKID "documentation-guide-0.2 (2004-02-24)"> <!-- change version of manual and date here -->
+d23 1
+d70 2
+@
+
+
+1.8
+log
+ at bump version
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.7 2004/02/24 17:17:31 tfox Exp $ -->
+d3 1
+a3 1
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
+@
+
+
+1.7
+log
+ at give generated index a static id
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.6 2004/02/24 17:03:35 tfox Exp $ -->
+d13 1
+a13 1
+<!ENTITY BOOKID "documentation-guide-0.1.1 (2004-01-19)"> <!-- change version of manual and date here -->
+@
+
+
+1.6
+log
+ at add end index tag so index is auto generated
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.5 2004/01/19 23:14:46 tfox Exp $ -->
+d80 1
+a80 1
+<index/>
+@
+
+
+1.5
+log
+ at add Gavin's patch for nxml
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.4 2003/11/25 21:03:40 tfox Exp $ -->
+d80 1
+@
+
+
+1.4
+log
+ at move legalnotice file into common dir
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.3 2003/11/21 22:40:39 tfox Exp $ -->
+d13 1
+a13 1
+<!ENTITY BOOKID "documentation-guide-0.1.1 (2003-09-16)"> <!-- change version of manual and date here -->
+d22 1
+d36 1
+a36 1
+ <year>2003</year>
+d67 2
+@
+
+
+1.3
+log
+ at change filenames to end with -en.xml
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide-en.xml,v 1.2 2003/10/15 18:11:01 tfox Exp $ -->
+d15 1
+a15 1
+<!ENTITY LEGALNOTICE SYSTEM "../legalnotice-en.xml">
+@
+
+
+1.2
+log
+ at fix example figure tag, add ack chapter
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+d15 1
+a15 1
+<!ENTITY LEGALNOTICE SYSTEM "../legalnotice.xml">
+d17 1
+a17 1
+<!ENTITY INTRODUCTION SYSTEM "docs-intro.xml">
+d19 8
+a26 8
+<!ENTITY GETTINGFILES SYSTEM "docs-getting-files.xml">
+<!ENTITY GUIDELINES SYSTEM "docs-rh-guidelines.xml">
+<!ENTITY EMACS SYSTEM "docs-emacs.xml">
+<!ENTITY TAGS SYSTEM "docs-xml-tags.xml">
+<!ENTITY TUTORIAL SYSTEM "docs-tutorial.xml">
+<!ENTITY CONVERTING SYSTEM "docs-converting.xml">
+<!ENTITY CVS SYSTEM "../common/cvs.xml">
+<!ENTITY ACKNOWLEDGMENTS SYSTEM "acknowledgments.xml">
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide.xml,v 1.9 2003/09/16 19:26:26 tfox Exp $ -->
+d26 1
+d74 2
+@
+
diff --git a/old-documentation-guide/Attic/documentation-guide-zh_CN.xml,v b/old-documentation-guide/Attic/documentation-guide-zh_CN.xml,v
new file mode 100644
index 0000000..a719d2c
--- /dev/null
+++ b/old-documentation-guide/Attic/documentation-guide-zh_CN.xml,v
@@ -0,0 +1,120 @@
+head 1.4;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.4
+date 2007.03.11.21.33.23; author pfrields; state dead;
+branches;
+next 1.3;
+
+1.3
+date 2005.12.28.00.40.27; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2005.12.17.13.28.38; author bbbush; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2005.12.09.15.28.54; author bbbush; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.4
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-zh_CN.ent">
+%FEDORA-ENTITIES-EN;
+<!ENTITY VERSION "0.2.6.3">
+<!ENTITY DOCID "documentation-guide-&VERSION; (2005-09-18)">
+<!ENTITY INTRODUCTION SYSTEM "docs-intro-zh_CN.xml" >
+<!ENTITY GETTINGFILES SYSTEM "docs-getting-files-zh_CN.xml" >
+<!ENTITY GUIDELINES SYSTEM "docs-rh-guidelines-zh_CN.xml" >
+<!ENTITY EMACS SYSTEM "docs-emacs-zh_CN.xml" >
+<!ENTITY EMACS-NXML SYSTEM "docs-emacs-nxml-zh_CN.xml" >
+<!ENTITY VIM SYSTEM "docs-vim-zh_CN.xml" >
+<!ENTITY TAGS SYSTEM "docs-xml-tags-zh_CN.xml" >
+<!ENTITY TUTORIAL SYSTEM "docs-tutorial-zh_CN.xml" >
+<!ENTITY CVS SYSTEM "../docs-common/common/cvs-zh_CN.xml" >
+<!ENTITY ACKNOWLEDGMENTS SYSTEM "acknowledgments-zh_CN.xml" >
+<!ENTITY STYLE SYSTEM "docs-style-zh_CN.xml" >
+]>
+<book id="documentation-guide" lang="zh_CN">
+ <bookinfo>
+ <title>&FP; 文档撰写准则</title>
+ <subtitle>版本 &VERSION;</subtitle>
+ <copyright>
+ <year>2003,2004,2005</year>
+ <holder>&FORMAL-RHI;</holder>
+ <holder>Tammy Fox</holder>
+ <holder>Johnray Fuller</holder>
+ <holder>Sandra Moore</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ <author>
+ <surname>Fuller</surname>
+ <firstname>Johnray</firstname>
+ </author>
+ <author>
+ <surname>Moore</surname>
+ <firstname>Sandra</firstname>
+ </author>
+ </authorgroup> &LEGALNOTICE;</bookinfo> &INTRODUCTION; &GETTINGFILES; &GUIDELINES; &EMACS; &EMACS-NXML; &VIM; &TAGS; &TUTORIAL; &STYLE; &CVS; &ACKNOWLEDGMENTS; <index id="generated-index"/></book>
+@
+
+
+1.3
+log
+ at Update to use new entity standards
+@
+text
+@@
+
+
+1.2
+log
+ at update build part
+@
+text
+ at d7 1
+a7 1
+<!ENTITY BOOKID "documentation-guide-&VERSION; (2005-09-18)">
+@
+
+
+1.1
+log
+@*** empty log message ***
+@
+text
+ at d4 1
+a4 1
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
+a5 1
+
+a15 1
+<!ENTITY CONVERTING SYSTEM "docs-converting-zh_CN.xml" >
+d44 1
+a44 1
+ </authorgroup> &LEGALNOTICE;</bookinfo> &INTRODUCTION; &GETTINGFILES; &GUIDELINES; &EMACS; &EMACS-NXML; &VIM; &TAGS; &TUTORIAL; &STYLE; &CONVERTING; &CVS; &ACKNOWLEDGMENTS; <index id="generated-index"/></book>
+@
+
diff --git a/old-documentation-guide/Attic/documentation-guide.xml,v b/old-documentation-guide/Attic/documentation-guide.xml,v
new file mode 100644
index 0000000..254c1aa
--- /dev/null
+++ b/old-documentation-guide/Attic/documentation-guide.xml,v
@@ -0,0 +1,135 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2003.11.21.22.40.39; author tfox; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2003.10.15.18.11.01; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at change filenames to end with -en.xml
+@
+text
+@<!-- $Id: documentation-guide.xml,v 1.2 2003/10/15 18:11:01 tfox Exp $ -->
+
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+
+<!ENTITY RH "Red Hat"> <!--The generic term "Red Hat" -->
+<!ENTITY FORMAL-RHI "&RH;, Inc."> <!--The generic term "Red Hat, Inc. -->
+<!ENTITY PROJECT "Fedora project"> <!-- Set the project name -->
+<!ENTITY NAME-TITLE "Fedora Project"> <!-- Set the project name, use for titles -->
+<!ENTITY DISTRO "Fedora Core"> <!-- Set the distro name -->
+<!ENTITY IG "&DISTRO; Installation Guide"> <!-- Always use for Installation Guide -->
+
+<!ENTITY BOOKID "documentation-guide-0.1.1 (2003-09-16)"> <!-- change version of manual and date here -->
+
+<!ENTITY LEGALNOTICE SYSTEM "../legalnotice.xml">
+
+<!ENTITY INTRODUCTION SYSTEM "docs-intro.xml">
+
+<!ENTITY GETTINGFILES SYSTEM "docs-getting-files.xml">
+<!ENTITY GUIDELINES SYSTEM "docs-rh-guidelines.xml">
+<!ENTITY EMACS SYSTEM "docs-emacs.xml">
+<!ENTITY TAGS SYSTEM "docs-xml-tags.xml">
+<!ENTITY TUTORIAL SYSTEM "docs-tutorial.xml">
+<!ENTITY CONVERTING SYSTEM "docs-converting.xml">
+<!ENTITY CVS SYSTEM "../common/cvs.xml">
+<!ENTITY ACKNOWLEDGMENTS SYSTEM "acknowledgments.xml">
+
+
+]>
+
+<book id="documentation-guide" lang="en">
+ <bookinfo>
+ <title>&NAME-TITLE; Documentation Guide</title>
+ <copyright>
+ <year>2003</year>
+ <holder>&FORMAL-RHI;</holder>
+ <holder>Tammy Fox</holder>
+ <holder>Johnray Fuller</holder>
+ <holder>Sandra Moore</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ <author>
+ <surname>Fuller</surname>
+ <firstname>Johnray</firstname>
+ </author>
+ <author>
+ <surname>Moore</surname>
+ <firstname>Sandra</firstname>
+ </author>
+ </authorgroup>
+ &LEGALNOTICE;
+ </bookinfo>
+
+
+ &INTRODUCTION;
+
+ &GETTINGFILES;
+
+ &GUIDELINES;
+
+ &EMACS;
+
+ &TAGS;
+
+ &TUTORIAL;
+
+ &CONVERTING;
+
+ &CVS;
+
+ &ACKNOWLEDGMENTS;
+
+</book>
+@
+
+
+1.2
+log
+ at fix example figure tag, add ack chapter
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide.xml,v 1.1 2003/09/22 16:34:23 tfox Exp $ -->
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: documentation-guide.xml,v 1.9 2003/09/16 19:26:26 tfox Exp $ -->
+d26 1
+d74 2
+@
+
diff --git a/old-documentation-guide/Makefile,v b/old-documentation-guide/Makefile,v
new file mode 100644
index 0000000..563df41
--- /dev/null
+++ b/old-documentation-guide/Makefile,v
@@ -0,0 +1,461 @@
+head 1.21;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.20
+ LIVE:1.17
+ VERSION-0_2:1.5;
+locks; strict;
+comment @# @;
+
+
+1.21
+date 2008.04.10.02.34.36; author pfrields; state Exp;
+branches;
+next 1.20;
+
+1.20
+date 2007.08.03.16.42.14; author pfrields; state Exp;
+branches;
+next 1.19;
+
+1.19
+date 2007.07.28.22.02.46; author pfrields; state Exp;
+branches;
+next 1.18;
+
+1.18
+date 2007.07.28.22.01.01; author pfrields; state Exp;
+branches;
+next 1.17;
+
+1.17
+date 2007.05.05.14.30.54; author pfrields; state Exp;
+branches;
+next 1.16;
+
+1.16
+date 2007.04.27.20.20.33; author diegobz; state Exp;
+branches;
+next 1.15;
+
+1.15
+date 2007.04.27.20.07.41; author pfrields; state Exp;
+branches;
+next 1.14;
+
+1.14
+date 2007.03.12.01.10.33; author pfrields; state Exp;
+branches;
+next 1.13;
+
+1.13
+date 2007.02.18.14.25.01; author pfrields; state Exp;
+branches;
+next 1.12;
+
+1.12
+date 2006.11.23.02.24.37; author pfrields; state Exp;
+branches;
+next 1.11;
+
+1.11
+date 2005.12.13.21.56.24; author jtr; state Exp;
+branches;
+next 1.10;
+
+1.10
+date 2005.12.10.20.21.04; author bbbush; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2005.09.18.22.45.54; author pfrields; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2005.06.29.14.45.43; author pfrields; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2005.06.29.13.02.27; author pfrields; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2005.06.28.21.46.45; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2004.02.24.19.14.14; author tfox; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2003.11.21.22.40.39; author tfox; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2003.10.02.16.39.57; author tfox; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2003.10.01.18.57.05; author tfox; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2003.09.22.16.34.23; author tfox; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.21
+log
+ at Add L10n chapter to DocGuide (#441190)
+@
+text
+@#######################################################################
+# Makefile for Fedora Documentation Project
+# License: GPL
+# Copyright 2003-2006 Tammy Fox, Red Hat, Inc., Tommy Reynolds,
+# Paul W. Frields
+#######################################################################
+
+PRI_LANG = en_US
+DOCBASE = documentation-guide
+
+define XMLFILES_template
+XMLFILES-${1}= ${1}/acknowledgments.xml \
+ ${1}/emacs-nxml.xml \
+ ${1}/emacs.xml \
+ ${1}/getting-files.xml \
+ ${1}/intro.xml \
+ ${1}/module-struct.xml \
+ ${1}/writing-guidelines.xml \
+ ${1}/style.xml \
+ ${1}/tutorial.xml \
+ ${1}/vim.xml \
+ ${1}/publishing.xml \
+ ${1}/l10n.xml \
+ ${1}/${DOCBASE}.xml
+endef
+
+
+######################################################
+define find-makefile-common
+for d in docs-common ../docs-common ../../docs-common; do \
+if [ -f $$d/Makefile.common ]; then echo "$$d/Makefile.common"; break; fi; done
+endef
+include $(shell $(find-makefile-common))
+######################################################
+@
+
+
+1.20
+log
+ at Update Makefile to include new content file
+@
+text
+ at d23 1
+@
+
+
+1.19
+log
+ at Remove unnecessary chapter on XML tags. DocBook: The Definitive Guide
+has all the information we need about tags, and if there is specific
+usage needed beyond DocBook XML 4.4, we should only provide that here.
+@
+text
+ at d22 1
+@
+
+
+1.18
+log
+ at Convert DocGuide to use po/LINGUAS instead of Makefile $OTHERS
+@
+text
+ at d22 1
+a22 2
+ ${1}/xml-tags.xml \
+ ${1}/documentation-guide.xml
+@
+
+
+1.17
+log
+ at The pt version builds OK these days.
+@
+text
+ at a8 1
+OTHERS = pt # pt_BR zh_CN
+@
+
+
+1.16
+log
+@
+
+Take off pt_BR in OTHERS - Makefile
+Added only for test by Paul
+-
+@
+text
+ at d9 1
+a9 1
+OTHERS = zh_CN
+@
+
+
+1.15
+log
+ at This fix is required for people using FC5. Apparently FC6's version
+of make fixes a bug that doesn't read multiline template commands like
+this. Or maybe it's just my boo-boo, either way....
+@
+text
+ at d9 1
+a9 1
+OTHERS = zh_CN pt_BR
+@
+
+
+1.14
+log
+ at Update all Makefiles to use the new required macro for including the Makefile.common. This will work whether you check out the entire repository at one time or a single module with an included docs-common.
+@
+text
+ at d9 1
+a9 1
+OTHERS = zh_CN
+d30 1
+a30 1
+for d in docs-common ../docs-common ../../docs-common; do
+@
+
+
+1.13
+log
+ at Update list of XML files so document will validate and build
+@
+text
+ at d29 5
+a33 1
+include ../docs-common/Makefile.common
+@
+
+
+1.12
+log
+ at Fix Makefile to use new standards
+@
+text
+ at d14 10
+a23 9
+ ${1}/docs-emacs-nxml.xml \
+ ${1}/docs-emacs.xml \
+ ${1}/docs-getting-files.xml \
+ ${1}/docs-intro.xml \
+ ${1}/docs-rh-guidelines.xml \
+ ${1}/docs-style.xml \
+ ${1}/docs-tutorial.xml \
+ ${1}/docs-vim.xml \
+ ${1}/docs-xml-tags.xml \
+@
+
+
+1.11
+log
+ at Added documentation about the document building system. Dropped the
+one-line "converting" chapter by creating a "Prerequisites" section
+in the "getting-files" section.
+@
+text
+ at d2 1
+a2 4
+# Makefile for RHLP docs project
+# Created by: Tammy Fox <tfox@@redhat.com>
+# Last edited by: Tammy Fox <tfox@@redhat.com>
+# WARNING: need passivetex 1.24 for pdf generation to work
+d4 2
+a5 1
+# Copyright 2003 Tammy Fox, Red Hat, Inc.
+d8 2
+a9 1
+LANGUAGES = en zh_CN
+d11 15
+a25 5
+XMLEXTRAFILES-en=acknowledgments-en.xml docs-emacs-en.xml \
+ docs-emacs-nxml-en.xml docs-getting-files-en.xml \
+ docs-intro-en.xml docs-rh-guidelines-en.xml docs-style-en.xml \
+ docs-tutorial-en.xml docs-vim-en.xml docs-xml-tags-en.xml \
+ documentation-guide-en.xml
+@
+
+
+1.10
+log
+ at add zh_CN to build target
+@
+text
+ at d1 1
+a1 1
+###############################################################################
+d8 1
+a8 1
+###############################################################################
+d12 5
+a16 1
+XMLEXTRAFILES-en =
+@
+
+
+1.9
+log
+ at Update Makefile to new standards
+@
+text
+ at d10 1
+a10 1
+LANGUAGES = en
+@
+
+
+1.8
+log
+ at Add XSL declaration to support nochunks
+@
+text
+ at d10 3
+a12 6
+XSLPDF = ../docs-common/xsl/main-pdf.xsl
+XSLHTML = ../docs-common/xsl/main-html.xsl
+XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl
+LANG = en
+DOCNAME = documentation-guide-$(LANG)
+XMLFILE = $(DOCNAME).xml
+@
+
+
+1.7
+log
+ at Subscribe to new Makefile.common functions
+@
+text
+ at d10 6
+a15 5
+XSLPDF = ../docs-common/xsl/main-pdf.xsl
+XSLHTML = ../docs-common/xsl/main-html.xsl
+LANG = en
+DOCNAME = documentation-guide-$(LANG)
+XMLFILE = $(DOCNAME).xml
+@
+
+
+1.6
+log
+ at Fixed entity file references and Makefile
+@
+text
+ at a18 13
+html:
+ @@xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
+ @@mkdir -p $(DOCNAME)/stylesheet-images
+ @@cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
+ @@cp ../docs-common/css/fedora.css $(DOCNAME)
+
+
+pdf:
+ @@xmlto pdf -x $(XSLPDF) $(XMLFILE)
+######################################################
+
+clean:
+ @@rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz
+@
+
+
+1.5
+log
+ at fix pdf target name
+@
+text
+ at d10 2
+a11 2
+XSLPDF = ../xsl/main-pdf.xsl
+XSLHTML = ../xsl/main-html.xsl
+d17 2
+d22 2
+a23 2
+ @@cp ../stylesheet-images/*.png $(DOCNAME)/stylesheet-images
+ @@cp ../css/fedora.css $(DOCNAME)
+d31 1
+a31 1
+ @@rm -rfv *.html *.pdf *.tex $(DOCNAME)
+@
+
+
+1.4
+log
+ at change filenames to end with -en.xml
+@
+text
+ at d24 1
+a24 1
+pdf-%:
+@
+
+
+1.3
+log
+ at use variables, copy over css and stylesheet-images
+@
+text
+ at d13 1
+a13 1
+DOCNAME = documentation-guide
+@
+
+
+1.2
+log
+ at add license and copyright info
+@
+text
+ at d2 1
+a2 1
+# Makefile for community charter
+d12 3
+d16 6
+a21 1
+all: html pdf
+a22 2
+html: documentation-guide.xml
+ @@xmlto html -x $(XSLHTML) -o documentation-guide $<
+d24 3
+a26 2
+pdf: documentation-guide.xml
+ @@xmlto pdf -x $(XSLPDF) $<
+d29 1
+a29 1
+ @@rm -rfv *.html *.pdf *.tex documentation-guide/
+@
+
+
+1.1
+log
+ at add docs guide
+@
+text
+ at d6 2
+@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-emacs-nxml.xml,v b/old-documentation-guide/en_US/Attic/docs-emacs-nxml.xml,v
new file mode 100644
index 0000000..b63a665
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-emacs-nxml.xml,v
@@ -0,0 +1,377 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+ <chapter id="ch-emacs-nxml">
+ <title>Emacs and nXML Mode</title>
+
+ <indexterm>
+ <primary>nXML</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>nXML mode</secondary>
+ </indexterm>
+
+ <para>
+ You can also use the nXML mode available for
+ <application>Emacs</application> to make it even easier to write in DocBook
+ XML format. nXML mode provides context-sensitive editing using completion,
+ real time validity error checking, syntax highlighting and indentation. All
+ you need to do is install an RPM!!
+ </para>
+
+ <note>
+ <title>Early stages</title>
+ <para>
+ Please be aware the nxml-mode for <application>Emacs</application> is
+ quite new, so there are a few things that the advanced user might notice
+ when using it with other documents types. If you keep an eye on the
+ mailing-list, you can keep up to date with these, as well as ask
+ questions. For more details, check out <xref
+ linkend="s1-emacs-nxml-readme"></xref>.
+ </para>
+ </note>
+
+
+ <sect1 id="s1-nxml-rpm">
+ <title>Getting the nXML RPM</title>
+
+ <indexterm>
+ <primary>nXML</primary>
+ <secondary>RPM</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>nXML RPM</primary>
+ </indexterm>
+
+ <para>
+ To use nXML mode with emacs, you will need to install the nXML RPM
+ available from <ulink
+ url="http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/">Tim
+ Waugh's</ulink> website or the source from <ulink
+ url="http://www.thaiopensource.com/download/">http://www.thaiopensource.com/download/</ulink>.
+ The source requires a lot more work to setup, therefore we will only be
+ concentrating on the RPM version.
+ </para>
+
+ <para>
+ Information on where to get the source is available in <xref
+ linkend="s1-emacs-additional-resources"></xref>.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-nxml-examples">
+ <title>Examples</title>
+
+ <para>
+ Compared to PSGML mode there are only couple of commands that you need.
+ This speeds up writing with <application>Emacs</application> considerably,
+ which means you can concentrate more on the content of your article.
+ </para>
+
+ <sect2 id="s2-nxml-commands">
+ <title>Commands</title>
+
+ <para>
+ To create a tag, type <userinput><</userinput> and then type the
+ keyword. To complete the keyword, press <command>Ctrl-Ret</command>,
+ then add the last <userinput>></userinput>. To close a tag, type
+ <userinput></</userinput>.
+ </para>
+
+ <important>
+ <title>Important</title>
+ <para>
+ When you open a document that doesn't have a DOCTYPE declaration at
+ the top of the file, you will get this message and tag completion
+ won't work because nXML will not know what format you are writing.
+ </para>
+ </important>
+
+ <para>
+ To load the schema, type <command>Ctrl-c</command>, then
+ <command>Ctrl-s</command> and navigate to
+ <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> and
+ load <filename>docbook.rnc</filename>. <application>Emacs</application>
+ will then prompt you to save it in the current working directory.
+ </para>
+
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ The commands already discussed are the only differences between
+ using <application>Emacs</application> with PSGML mode and
+ <application>Emacs</application> with nXML mode. You will still need
+ to use all the same commands as discussed in <xref
+ linkend="s1-emacs-basic-commands"></xref>.
+ </para>
+ </tip>
+ </sect2>
+ </sect1>
+
+ <sect1 id="s1-emacs-nxml-additional-resources">
+ <title>Additional Resources</title>
+
+ <para> Additional Emacs and nXML references are available at the following
+ locations:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://www.thaiopensource.com/download/">http://www.thaiopensource.com/download/</ulink>
+ — <citetitle>Author's download area</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink>
+ — <citetitle>Emacs Quick Reference Guide</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Emacs reference card that comes with the
+ <filename>emacs</filename> package. You can print it out as a
+ reference. —
+ <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </sect1>
+
+ <sect1 id="s1-emacs-nxml-readme">
+ <title>nXML README File</title>
+
+ <note>
+ <title>Note</title>
+ <para>
+ This file can be found in the directory you extracted the source into,
+ or in
+ <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename>
+ if you installed the RPM.
+ </para>
+ </note>
+
+ <para>README file:</para>
+
+ <para>
+ This is a new major mode for GNU Emacs for editing XML documents. It
+ supports editing well-formed XML documents and also provides
+ schema-sensitive editing of XML documents using RELAX NG Compact Syntax.
+ </para>
+
+ <para>
+ To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs
+ version 20 will not work properly, nor will XEmacs. To get started, do the
+ following:
+ </para>
+
+ <screen>
+ <command>M-x load-file RET rng-auto.el RET</command>
+ </screen>
+
+ <para>
+ This defines the necessary autoloads. Now, visit a file containing an XML
+ document, and do the following:
+ </para>
+
+ <screen> <command>M-x nxml-mode</command>
+ </screen>
+
+ <para>
+ Now do
+ </para>
+
+ <screen>
+ <command>C-h m</command>
+ </screen>
+
+ <para>
+ For information on how to use nxml-mode. The beginnings of a manual are
+ in nxml-mode.info. You can read this using:
+ </para>
+
+ <screen>
+ <command>C-u M-x info RET nxml-mode.info RET</command>
+ </screen>
+
+ <para>
+ It's also installed as an entry at the end of the top-level info
+ directory. So you can read it with <command>C-h i</command> as usual.
+ </para>
+
+ <para>
+ You can use <filename>test.valid.xml</filename> and
+ <filename>test.invalid.xml</filename> as examples of valid and invalid XML
+ documents.
+ </para>
+
+ <para>
+ To get things automatically loaded each time you start Emacs, add:
+ </para>
+
+ <screen>
+ <computeroutput> (load "~/nxml-mode-200YMMDD/rng-auto.el")
+ </computeroutput>
+ </screen>
+
+ <para>
+ to your <filename>.emacs</filename>, where
+ <computeroutput>~/nxml-mode-200YMMDD</computeroutput> is the directory
+ containing the <filename>.elc</filename> files. Note that
+ <filename>rng-auto.el</filename> does not load all of the nxml-mode code;
+ it merely sets things up so that all the features of nxml-mode will be
+ autoloaded properly. You should not try to autoload
+ <filename>rng-auto.el</filename> itself.
+ </para>
+
+ <para>
+ To use nxml-mode automatically for files with an extension of
+ <filename>xml</filename>, <filename>xsl</filename>,
+ <filename>rng</filename> or <filename>xhtml</filename>, add the following
+ to your <filename>.emacs</filename> file:
+ </para>
+
+ <screen>
+ <computeroutput> (setq auto-mode-alist (cons
+ '("\\.\\(xml\\|xsl\\|rng\\|xhtml\\)\\'" . nxml-mode) auto-mode-alist))
+ </computeroutput>
+ </screen>
+
+ <para>
+ If you edit XML using iso-8859-N encodings other than iso-8859-1 and you
+ are running Emacs 21.3 or later, then I recommend enabling
+ unify-8859-on-decoding-mode, by adding the following to your
+ <filename>.emacs</filename> file:
+ </para>
+
+ <screen>
+ <computeroutput>(unify-8859-on-decoding-mode)</computeroutput>
+ </screen>
+
+ <para>
+ To get validation and schema-sensitive editing, you need a RELAX NG
+ Compact Syntax (RNC) schema for you document. The schema directory
+ includes some schemas for popular document types.
+ </para>
+
+ <para>
+ For more on RELAX NG, refer to <ulink
+ url="http://relaxng.org/">http://relaxng.org/</ulink>.
+ </para>
+
+ <para>
+ For a tutorial on RELAX NG Compact Syntax, refer to <ulink
+ url="http://relaxng.org/compact-tutorial.html">http://relaxng.org/compact-tutorial.html</ulink>
+ </para>
+
+ <para>
+ For automatically creating RNC schemas, I recommend my Trang program:
+ <ulink
+ url="http://www.thaiopensource.com/relaxng/trang.html">http://eee.thaiopensource.com/relaxng/trang.html"</ulink>
+ </para>
+
+ <para>
+ You can use this to
+
+<itemizedlist>
+ <listitem>
+ <para>
+ Infer an RNC schema from an instance document
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Convert a DTD to an RNC schema
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Convert a RELAX NG XML syntax schema to an RNC schema
+ </para>
+ </listitem>
+</itemizedlist>
+ </para>
+
+ <para>
+ To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can
+ also use the XSLT stylesheet from <ulink
+ url="http://www.pantor.com/download.html">http://www.pantor.com/download.html"</ulink>.
+ </para>
+
+ <para>
+ To convert a W3C XML Schema to an RNC schema, you need first to convert it
+ to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built
+ on top of MSV). Refer to <ulink
+ url="https://msv.dev.java.net/">https://www.dev.java.net/</ulink>.
+ </para>
+
+ <para>
+ The file <filename>NEWS</filename> describes recent changes.
+ </para>
+
+ <para>
+ Please use the list <ulink
+ url="http://groups.yahoo.com/group/emacs-nxml-mode/">http://groups.yahoo.com/group/emacs-nxml-mode</ulink>
+ for bug reports, discussion. I will announce all new versions there.
+ </para>
+
+ <para>
+ James Clark
+ </para>
+ <para>
+ jjc@@thaiopensource.com
+ </para>
+ </sect1>
+ </chapter>
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+@@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-emacs.xml,v b/old-documentation-guide/en_US/Attic/docs-emacs.xml,v
new file mode 100644
index 0000000..6459075
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-emacs.xml,v
@@ -0,0 +1,792 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2006.12.17.00.41.55; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!-- $Id: docs-emacs.xml,v 1.2 2006/12/17 00:41:55 pfrields Exp $ -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+ <chapter id="ch-emacs">
+ <title>Emacs and PSGML Mode</title>
+
+ <indexterm>
+ <primary>PSGML</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>PSGML mode</secondary>
+ </indexterm>
+
+ <para>
+ You can use the PSGML mode available for Emacs to make it easier to write
+ in XML format. PSGML mode provides syntax-highlighting, tag completion,
+ and more.
+ </para>
+
+ <sect1 id="s1-emacs-file">
+ <title>Setting Up Your <filename>.emacs</filename> File</title>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>configuration file</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.emacs</filename></primary>
+ </indexterm>
+
+ <para>
+ For Emacs to parse your DocBook documents correctly, you must have a
+ <filename>.emacs</filename> file. Cut and paste the following into your
+ existing <filename>.emacs</filename> file or create a new one that
+ contains the following lines:
+
+<screen>
+<computeroutput>
+;; turn on auto-fill in `text-mode' and derived modes
+;;(mail, news, etc)
+(add-hook 'text-mode-hook 'turn-on-auto-fill)
+
+;;
+;;MODES
+;;
+
+(setq auto-mode-alist (cons '("\\.sgml$" . sgml-mode) auto-mode-alist))
+(setq auto-mode-alist (cons '("\\.sgm$" . sgml-mode) auto-mode-alist))
+
+;;
+;;XML!!
+;;
+;;#############################################################
+
+;;
+;;PSGML mode stuff
+;;
+
+(autoload 'sgml-mode "psgml" "My Most Major Mode" t)
+
+(setq sgml-mode-hook '(lambda () "Defaults for XML mode." (turn-on-auto-fill)
+(setq fill-column 80)))
+
+(defun My-XML-keymap ()
+ (local-set-key [(alt i)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt l)]
+ '(lambda ()
+ (interactive)
+ (sgml-insert-element 'list)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt p)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'para)
+ (sgml-indent-line)))
+ (local-set-key [(alt -)]
+ '(lambda ()
+ (interactive)
+ (insert "—"))))
+
+(add-hook 'sgml-mode-hook 'My-XML-keymap)
+
+;;
+;; Fix up indentation of data...
+;;
+
+(setq-default sgml-indent-data t)
+
+;;
+;; XML markup faces.
+;;
+
+(setq-default sgml-set-face t)
+
+
+(make-face 'sgml-comment-face)
+(make-face 'sgml-doctype-face)
+(make-face 'sgml-end-tag-face)
+(make-face 'sgml-entity-face)
+(make-face 'sgml-ignored-face)
+(make-face 'sgml-ms-end-face)
+(make-face 'sgml-ms-start-face)
+(make-face 'sgml-pi-face)
+(make-face 'sgml-sgml-face)
+(make-face 'sgml-short-ref-face)
+(make-face 'sgml-start-tag-face)
+
+(set-face-foreground 'sgml-comment-face "maroon")
+(set-face-foreground 'sgml-doctype-face "dark green")
+(set-face-foreground 'sgml-end-tag-face "blue2")
+(set-face-foreground 'sgml-entity-face "red2")
+(set-face-foreground 'sgml-ignored-face "maroon")
+(set-face-background 'sgml-ignored-face "gray90")
+(set-face-foreground 'sgml-ms-end-face "maroon")
+(set-face-foreground 'sgml-ms-start-face "maroon")
+(set-face-foreground 'sgml-pi-face "maroon")
+(set-face-foreground 'sgml-sgml-face "maroon")
+(set-face-foreground 'sgml-short-ref-face "goldenrod")
+(set-face-foreground 'sgml-start-tag-face "blue2")
+
+(setq-default sgml-markup-faces
+ '((comment . sgml-comment-face)
+ (doctype . sgml-doctype-face)
+ (end-tag . sgml-end-tag-face)
+ (entity . sgml-entity-face)
+ (ignored . sgml-ignored-face)
+ (ms-end . sgml-ms-end-face)
+ (ms-start . sgml-ms-start-face)
+ (pi . sgml-pi-face)
+ (sgml . sgml-sgml-face)
+ (short-ref . sgml-short-ref-face)
+ (start-tag . sgml-start-tag-face)))
+
+
+(defun docbook-mode ()
+ (sgml-mode)
+ )
+
+
+
+;;
+;;END XML STUFF
+;;
+;;##################################################################
+
+;PO mode stuff
+
+(setq auto-mode-alist
+ (cons '("\\.pox?\\'" . po-mode) auto-mode-alist))
+(autoload 'po-mode "po-mode")
+
+
+ (global-set-key [(f1)] (lambda () (interactive) (manual-
+ entry (current-word))))
+
+</computeroutput>
+</screen>
+
+ </para>
+
+ <para>
+ Do you have a cool wheel mouse? If so, you can add the following to your
+ <filename>.emacs</filename> file so your wheel will work in
+ <application>Emacs</application> (must be
+ <application>Emacs</application> version 21):
+ </para>
+
+<screen>
+<computeroutput>
+;; Enable wheelmouse support by default for emacs 21
+(cond (window-system
+(mwheel-install)
+))
+</computeroutput>
+</screen>
+
+ <para>
+ If you are using the older version 20 of
+ <application>Emacs</application>, add the following instead:
+ </para>
+
+<screen>
+<computeroutput>
+;; Enable wheelmouse support by default
+(require 'mwheel)
+</computeroutput>
+</screen>
+
+<!-- bug #125757 in NEEDINFO state
+ <para>
+ If you have a mouse, you can also add the following. It adds popup menus
+ when the cursor is either on a start tag or in a region where elements
+ are allowed.
+ </para>
+
+<screen>
+<computeroutput>
+;; Mouse Bindings: right-click to generate context-aware
+;; elements/attributes popup menu.
+(define-key sgml-mode-map [mouse-3] 'sgml-tags-menu)
+</computeroutput>
+</screen>
+
+-->
+
+ </sect1>
+
+
+ <sect1 id="s1-emacs-colors">
+ <title>Customizing Emacs</title>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>customizing</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.Xresources</filename></primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>colors</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>font</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>geometry</secondary>
+ </indexterm>
+
+ <para>
+ The colors, font, and geometry (default size of window) for Emacs in your
+ <filename>~/.Xresources</filename> file. The format for the settings is
+ <computeroutput>emacs.keyword:value</computeroutput>
+ </para>
+
+ <para>
+ The following is a sample <filename>~/.Xresources</filename> file.
+ </para>
+ <note>
+ <title>Note</title>
+ <para>If you have other settings in your
+ <filename>~/.Xresources</filename>, add the following to the end of
+ the file.
+ </para>
+ </note>
+
+<screen>
+<userinput>
+emacs.background: light gray
+emacs.foreground: black
+emacs.pointerColor: blue
+emacs.cursorColor: blue
+emacs.bitmapIcon: on
+emacs.font: fixed
+emacs.geometry: 90x25
+</userinput>
+</screen>
+ <para>
+ After modifying this file, you must execute the command
+ </para>
+<screen>
+<command>xrdb -merge ~/.Xresources</command>
+</screen>
+ <para>
+ and restart <application>Emacs</application> for the changes to take
+ place.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-cedfile">
+ <title>Create Recompiled DTD Subset</title>
+
+ <para>
+ Emacs will perform syntax highlighting and indent correctly on
+ DocBook XML files if you provide it with the proper Document Type
+ Declarations (DTD) file. These two features will make your XML file
+ look pretty and help you spot errors.
+ </para>
+
+ <para>
+ To create a loadable Parsed DTD file:
+ <orderedlist>
+ <listitem>
+ <para>Find the parent file for the group of DocBook files. You will
+ recognize this file by the header <filename><!DOCTYPE article
+ PUBLIC "-//OASIS//DTD DocBook V4.1//EN"</filename>. An easy way
+ to find this parent file is to use the command <command>grep
+ DocBook *.xml</command>. Once you find the parent file, open it
+ in Emacs with the command <command>emacs
+ <replaceable><parentfile></replaceable>.xml</command> (where
+ <replaceable><parentfile></replaceable>.xml is the parent
+ file you found.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Choose <command>DTD -> Parse DTD</command> from the pulldown
+ menu.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>You will know the parsing is finished when you see the message
+ <computeroutput>Fontifying...done</computeroutput> at the bottom
+ of your screen. Save the parsed DTD to a file by choosing
+ <command>DTD -> Save Parsed DTD</command> from the pulldown menu.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Press <keycap>Enter</keycap> to save the file to the default
+ filename or rename the file keeping the <filename>.ced</filename>
+ extension. It can be useful to name it something generic such as
+ <filename>docbook.ced</filename> so you can refer to it when
+ opening all DocBook files. This file can also be copied from
+ directory to directory to be loaded.
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </para>
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ You can also use the Emacs command <command>Meta-x
+ sgml-parse-prolog</command> to parse the file, and then use the
+ command <command>Meta-x sgml-save-dtd</command> to save the parsed DTD
+ to a <filename>.ced</filename> file.
+ </para>
+ </tip>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-loadced">
+ <title>Load the Parsed DTD</title>
+
+ <para>
+ Now that you have saved the DTD settings, you can load the
+ <filename>.ced</filename> file and see the syntax highlighting for your
+ <filename>.sgml</filename> files.
+ </para>
+
+ <para>
+ To load a parsed DTD file:
+ <orderedlist>
+ <listitem>
+ <para>Open an XML file in Emacs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Choose <command>DTD -> Load DTD</command> from the pulldown menu
+ and choose the file you saved from the previous step. For
+ instance, choose <filename>docbook.ced</filename>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>You will know it is finished when you see the message
+ <computeroutput>Fontifying...done</computeroutput> at the bottom
+ of your screen. Loading the parsed DTD might take a long time.
+ You can start editing the file before it finishes.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ You can also use the Emacs command <command>Meta-x
+ sgml-load-dtd</command> to load the parsed DTD.
+ </para>
+ </tip>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-basic-commands">
+ <title>Basic Emacs Commands</title>
+
+ <para>
+ The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key.
+ </para>
+
+ <table frame="all" rowsep="1" colsep="1" id="tb-emacs-commands">
+ <title>Emacs Commands</title>
+ <tgroup rowsep="1" colsep="1" cols="2">
+ <colspec colnum="1" colname="shortcut" colwidth="170"/>
+ <colspec colnum="2" colname="description" colwidth="300"/>
+
+ <thead>
+ <row>
+ <entry rowsep="1" colsep="1">Shortcut</entry>
+ <entry rowsep="1" colsep="1">Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry rowsep="1" colsep="1"><keycombo>
+ <keycap>Meta</keycap><keycap>x</keycap></keycombo>
+ sgml-parse-prolog, <keycap>Enter</keycap></entry>
+ <entry>Parse DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-save-dtd, <keycap>Enter</keycap></entry>
+ <entry>Save the Parse DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo> <keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-load-dtd, <keycap>Enter</keycap></entry>
+ <entry>Load DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo> <keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap></keycap></keycombo>, <keycap>Tab</keycap></entry>
+ <entry>Display list of valid tags</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap></keycap> </keycombo>, type beginning of tag,
+ <keycap>Tab</keycap></entry>
+ <entry>Complete the tag</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>g</keycap>
+ </keycombo></entry>
+ <entry>Cancel a command in the minibuffer</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycap>/</keycap></entry>
+ <entry>Close tag</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>a</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to beginning of line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>e</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the end of the line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>Home</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the beginning of the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>End</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the end of the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>k</keycap>
+ </keycombo></entry>
+ <entry>Cut line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>y</keycap>
+ </keycombo></entry>
+ <entry>Paste line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>s</keycap>
+ </keycombo></entry>
+ <entry>Search forward in the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>r</keycap>
+ </keycombo></entry>
+ <entry>Search backwards in the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>$</keycap>
+ </keycombo></entry>
+ <entry>Check spelling of current word</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-word, <keycap>Enter</keycap></entry>
+ <entry>Check spelling of current word</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-buffer, <keycap>Enter</keycap></entry>
+ <entry>Check spelling of current buffer</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap>
+ </keycombo></entry>
+ <entry>Open file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap>
+ </keycombo></entry>
+ <entry>Save file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></entry>
+ <entry>Exit <application>Emacs</application> and prompt to save
+ files if necessary</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap> <keycap>q</keycap>
+ </keycombo></entry>
+ <entry>Fill paragraph</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>a</keycap>
+ </keycombo></entry>
+ <entry>Edit attributes for a tag (for example, you can edit the
+ <computeroutput>url</computeroutput> attribute of the
+ <computeroutput>ulink</computeroutput> tag)</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>,
+ <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></entry>
+ <entry>Exit edit attributes</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-examples">
+ <title>Examples</title>
+
+ <para>
+ The table or reference card of Emacs and PSGML commands can be confusing
+ for beginners. This section provides some examples of how to use them.
+ </para>
+
+ <sect2 id="s2-emacs-tag-completion">
+ <title>Tag Completion</title>
+
+ <note>
+ <title>Note</title>
+ <para>This section assumes that you have already loaded the DTD file
+ (<filename>.ced</filename>).
+ </para>
+ </note>
+
+ <para>
+ Instead of typing a tag each time you need to use it, use
+ the key combination <keycap>Ctrl</keycap>-<keycap>c</keycap>,
+ followed by <keycap><</keycap>. At the bottom of the
+ <application>Emacs</application> window, you will see:
+ </para>
+<screen>
+<computeroutput>Tag: <</computeroutput>
+</screen>
+
+ <para>
+ To view a list of available tags, use either the <keycap>Tab</keycap>
+ or <keycap>?</keycap>. Or, if you know the first few letters of a tag,
+ you can enter them followed by <keycap>Tab</keycap> for a complete
+ list of available tags beginning with those letters or for a tag
+ completion.
+ </para>
+
+ <para>
+ Try the following: Type <keycap>Ctrl</keycap>-<keycap>c</keycap>
+ followed by <keycap><</keycap>. Then enter the letter
+ <keycap>k</keycap>, followed by <keycap>Tab</keycap>. You may have to
+ use the <keycap>Tab</keycap> key several times to get a complete list.
+ </para>
+
+ <para>
+ The output should look similar to the example below:
+ </para>
+
+<screen>
+<computeroutput>
+Click mouse-2 on a completion to select it.
+In this buffer, type RET to select the completion near point.
+
+Possible completions are:
+<keycap> <keycode>
+<keycombo> <keysym>
+</computeroutput>
+</screen>
+
+ </sect2>
+ <sect2 id="s2-emacs-tag-closing">
+ <title>Tag Closure</title>
+
+ <para>
+ Once you have started the tag of choice, you must close it. The easiest
+ way to close an open tag is to use the keycombo
+ <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by
+ <keycap>/</keycap>. This will close the closest open tag you have.
+ </para>
+
+ </sect2>
+
+ <sect2 id="s2-emacs-other">
+ <title>Other Emacs Tasks</title>
+
+ <para>
+ <guilabel>Working with one window</guilabel>: Sometimes in
+ <application>Emacs</application> the window becomes split (with tags
+ completions or other text in the bottom window). The easiest way to
+ get it back so that only your XML and text appear on one screen is to
+ use the keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap>, followed by
+ <keycap>1</keycap>.
+ </para>
+
+ <para>
+ <guilabel>Saving your work</guilabel>: To save your work, use the
+ following keycombo, <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>s</keycap>.
+ </para>
+
+ <para>
+ <guilabel>The "clear/quit" command</guilabel>: I have found on some
+ occasions that I have gotten too far into the tag completion process and
+ need to just exit back out to my text. The easiest way to do this is the
+ keycombo <keycap>Ctrl</keycap>-<keycap>g</keycap>. This command quits
+ what you have been doing within the file, without quitting the file
+ itself.
+ </para>
+
+ <para>
+ <guilabel>Opening a new file</guilabel>: To open a new file, use the
+ keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>f</keycap>. At the bottom of the emacs
+ window, you will be able to enter in the file name (using
+ <keycap>Tab</keycap> completion if needed) of the file you wish to
+ open.
+ </para>
+
+ <para>
+ <guilabel>Closing emacs</guilabel>: The easiest way to close
+ <application>emacs</application> is to use the keycombo
+ <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>c</keycap>. If you have not saved your work,
+ it will prompt you to save the file, otherwise it will just quit the
+ current emacs session you have been working with.
+ </para>
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-emacs-additional-resources">
+ <title>Additional Resources</title>
+
+ <para> Additional Emacs and PSGML references are available at the
+ following locations:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink>
+ — <citetitle>Emacs Quick Reference Guide</citetitle>
+ </para>
+ </listitem>
+ <listitem> <para>Emacs reference card that comes with the
+ <filename>emacs</filename> package. You can print it out as a
+ reference. —
+ <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Read <citetitle>Editing XML with Emacs and PSGML</citetitle>
+ in <filename>/usr/share/doc/psgml-<replaceable><version></replaceable>/psgml.ps</filename>. </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://www.snee.com/bob/sgmlfree/psgmqref.html">http://www.snee.com/bob/sgmlfree/psgmqref.html</ulink>
+ — <citetitle>Emacs/PSGML Quick Reference</citetitle> is a
+ reference table of Emacs commands for PSGML mode.
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://www.snee.com/bob/sgmlfree/emcspsgm.html">http://www.snee.com/bob/sgmlfree/emcspsgm.html</ulink>
+ — <citetitle>PSGML Tricks</citetitle></para>
+ </listitem>
+ </itemizedlist>
+
+ </sect1>
+ </chapter>
+
+
+
+
+
+
+
+
+
+@
+
+
+1.2
+log
+ at Ha, I know a lot more about why this book caused me so much pain when I first started learning DocBook and XML. Take that, crummy DOCTYPEs\!
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-emacs.xml,v 1.1 2006/11/23 02:24:17 pfrields Exp $ -->
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d1 2
+a2 2
+<!-- $Id: docs-emacs-en.xml,v 1.2 2004/08/13 15:35:41 tfox Exp $ -->
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-getting-files.xml,v b/old-documentation-guide/en_US/Attic/docs-getting-files.xml,v
new file mode 100644
index 0000000..599fd58
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-getting-files.xml,v
@@ -0,0 +1,503 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2006.11.29.22.18.53; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!-- $Id: -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<chapter id="ch-getting-files">
+ <title>Prerequisites</title>
+
+ <para>
+ To work on official &FED; documentation you need to install the required
+ tools. Follow the directions below to configure your system.
+ </para>
+
+ <section id="ch-getting-files-system-packages">
+ <title>System Packages</title>
+
+ <para>
+ Install the "Authoring and Publishing" package group, which contains
+ required DocBook XML files, stylesheets and scripts:
+ </para>
+
+<screen>
+<userinput>su -c 'yum groupinstall "Authoring and Publishing"'</userinput>
+</screen>
+
+ <para>
+ Next, install the <filename>cvs</filename> package, which is used to
+ handle revision control on files in the official repository:
+ </para>
+
+<screen>
+<userinput>su -c 'yum install cvs'</userinput>
+</screen>
+
+ </section>
+
+ <section id="ch-getting-files-fdp">
+ <title>Fedora Documentation Tools</title>
+
+ <para>
+ The &FDP;'s custom scripts and stylesheets are stored in CVS on the
+ <systemitem class="fqdomainname">cvs.fedoraproject.org</systemitem> CVS
+ server. Check them out along with the DocBook XML files for the existing
+ docs.
+ </para>
+
+<screen>
+<userinput>mkdir <replaceable>my-fedora-docs-sandbox</replaceable>
+cd <replaceable>my-fedora-docs-sandbox</replaceable>
+export CVSROOT=:ext:<replaceable>username</replaceable>@@cvs.fedora.redhat.com:/cvs/docs
+cvs login
+cvs co docs-common</userinput>
+</screen>
+
+ <para>
+ At the password prompt, press the <keycap>Enter</keycap> key.
+ </para>
+
+ <note>
+ <title>Common Files</title>
+ <para>
+ You need to perform this "checkout" step only once, although you may
+ need to update the files later. These files are common to all the
+ official documentation.
+ </para>
+ </note>
+
+ <para>
+ To work on existing documents in CVS, refer to <xref linkend="ch-cvs"/>.
+ </para>
+
+ </section>
+
+ <section id="ch-getting-files-filenames">
+ <title>Filename Conventions</title>
+ <para>
+ &FDP; provides the tools, scripts, and stylesheets to transform your
+ <abbrev>XML</abbrev> documents into other output formats such as
+ <abbrev>HTML</abbrev>. In addition, these tools can build your document
+ into a <abbrev>RPM</abbrev> package. To take advantage of these
+ services, you must follow conventions for naming your files.
+ </para>
+ <section id="ch-getting-files-filenames-doc">
+ <title>Document Filenames</title>
+ <para>
+ Each document lives in a peer directory to the
+ <filename>docs-common</filename> directory you extracted from the &FED;
+ archive earlier. On the CVS server, these directories are called
+ <firstterm>modules</firstterm>. Choose a module name that accurately
+ reflects your document's subject, but avoid any name already taken. Use
+ the <command>cvs co -c</command> command to view existing module names.
+ </para>
+ <important>
+ <title>Avoid Redundancy</title>
+ <para>
+ Do not use the word <wordasword>&FED;</wordasword> in your module
+ name. Since all documents in the repository are &FED; documentation,
+ using this term creates unnecessary confusion.
+ </para>
+ </important>
+ </section>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.2
+log
+ at Exclude nxml chapter for now, and reorganize first chapter
+@
+text
+@@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d2 1
+a2 1
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+d16 1
+a16 1
+ tools. The directions below will help you configure your setup.
+d47 1
+a47 1
+ <systemitem class="fqdomainname">cvs.fedora.redhat.com</systemitem> CVS
+d55 1
+a55 1
+export CVSROOT=:pserver:anonymous@@cvs.fedora.redhat.com:/cvs/docs
+d67 3
+a69 2
+ You need to perform these steps only once. These files are common to
+ all the official documentation.
+a78 4
+ <!-- Starting here, the information is EXTREMELY useful but goes way outside
+ the scope of the chapter. This stuff needs to be relocated in the redesigned
+ DocGuide. [PWF, 2006-01-03] -->
+
+d83 4
+a86 4
+ <abbrev>XML</abbrev> documents into either <abbrev>HTML</abbrev> or
+ <abbrev>PDF</abbrev> output formats. In addition, these tools can build
+ your document into an <abbrev>RPM</abbrev> package. To take advantage of
+ these services, you must follow conventions for naming your files.
+d103 1
+a103 1
+ using it creates unnecessary confusion.
+a106 303
+ <section id="ch-getting-files-i18n">
+ <title>Anticipating I18N Translation</title>
+ <para>
+ The &FDP; includes an active translation team. Project documents are
+ often translated into several languages. By convention, the translated
+ files share the directory with the original files. Therefore, filenames
+ must be unique.
+ </para>
+ <para>
+ To construct a filename, append a dash followed by the
+ <abbrev>ISO</abbrev> language symbol before any file extension. For
+ example, a file whose language content is <abbrev>U.S.</abbrev> English
+ might be named <filename>mydoc-en.xml</filename>, its Chinese
+ translation named <filename>mydoc-zh_CN.xml</filename>, and so on.
+ </para>
+ <para>
+ To assist this effort, the document build system assumes that each file
+ is tagged with its <abbrev>I18N</abbrev> locale. Our filename
+ convention is shown in <xref linkend="ch-getting-files-i18n-table"/>.
+ </para>
+ <table id="ch-getting-files-i18n-table">
+ <title>&FDP; Filename Conventions</title>
+ <tgroup cols="2">
+ <colspec align="right" colnum="1" colwidth="*1"/>
+ <colspec colnum="2" colwidth="*5"/>
+ <thead>
+ <row>
+ <entry>
+ <phrase>Compoment</phrase>
+ </entry>
+ <entry>
+ <phrase>Description</phrase>
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <phrase><replaceable>anything_but_dash</replaceable></phrase>
+ </entry>
+ <entry>
+ <para>
+ The initial portion of a filename can be anything, as long as
+ <emphasis>no dash</emphasis> is used.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase><filename>-</filename></phrase>
+ </entry>
+ <entry>
+ <para>
+ A dash (<filename>-</filename>) is to be used only to
+ introduce the <systemitem class="macro">${LANG}</systemitem>
+ filename component.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <phrase><systemitem class="macro">${LANG}</systemitem></phrase>
+ </entry>
+ <entry>
+ <para>
+ The <systemitem class="macro">${LANG}</systemitem> component
+ identifies the <wordasword>locale</wordasword> for the file
+ content.
+ </para>
+ <para>
+ In addition to helping classify files according to their
+ language content, we also use the <systemitem
+ class="macro">${LANG}</systemitem> value as an
+ <abbrev>UTF-8</abbrev> locale when rendering the document.
+ For example, the document
+ <filename>mydoc-it.xml</filename>will be rendered using
+ <systemitem class="resource">it.UTF-8</systemitem> as the
+ language environment.
+ </para>
+ <para>
+ For more information on <abbrev>I18N</abbrev> localization,
+ visit the <ulink url="http://www.openi18n.org"/> web site.
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <warning>
+ <title>Document Filenames Are Special</title>
+ <para>
+ The main file in your document <emphasis>must</emphasis> follow the
+ file naming convention or the document building system cannot find it.
+ </para>
+ </warning>
+ </section>
+ </section>
+ <section id="ch-getting-files-build-system">
+ <title>The Document Build System</title>
+ <para>
+ Common tasks such as rendering the document into either <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev> can be performed easily using the document building system.
+ </para>
+ <para>
+ The building system heavily leverages the <application>make(1)</application> tool and shell scripts to automate these activities, but authors need <emphasis>no</emphasis> prior experience with either shell scripts or a <filename>Makefile</filename>.
+ While individual documents do have their own <filename>Makefile</filename>, it is only a few lines long and very simple.
+ The document <filename>Makefile</filename> content is designed for cut'n paste.
+ </para>
+ <para>
+ As an example, <xref linkend="ch-getting-files-build-system-makefile"/> shows the whole <filename>Makefile</filename> for a simple document having only one file and one language.
+ </para>
+ <example id="ch-getting-files-build-system-makefile">
+ <title>Sample Document Makefile</title>
+<programlisting width="60">
+DOCBASE = mydoc
+LANGUAGES = en
+XMLEXTRAFILES-en=
+include ../docs-common/Makefile.common
+</programlisting>
+</example>
+ <para>
+ Our main <abbrev>XML</abbrev> file is <filename>mydoc-en.xml</filename>; no translation has been done yet.
+ </para>
+ <para>
+ The <systemitem class="macro">LANGUAGES</systemitem> definition lists the English locale <literal>en</literal>; when other translations become available, their locale will just be appended to this definition.
+ </para>
+ <para>
+ Our document has only the main file <filename>mydoc-en.xml</filename>, but other documents may be split over several files.
+ The <systemitem class="macro">XMLEXTRAFILES-en</systemitem> definition catalogs these additional files so that the document building system can watch them for changes and rebuild the document when necesssary.
+ This definition is just a simple list of files.
+ </para>
+ <para>
+ The final line, beginning with <literal>include</literal>, references the main <filename>Makefile</filename> for the build system.
+ The <filename>Makefile.common</filename> file contains all the <application>make(1)</application> targets and rules to actually build the document and the various archives.
+ </para>
+ <para>
+ Add new document translations by:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Add the translated document files to the document directory.
+ Be sure to use the proper <systemitem class="macro">${LANG}</systemitem> filename component to keep the filenames similar, but unique.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Edit the <filename>Makefile</filename> to append the new <systemitem class="macro">${LANG}</systemitem> to the <systemitem class="macro">LANGUAGES</systemitem> definition.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Create a new <systemitem class="macro">XMLEXTRAFILES-${LANG}</systemitem> definition that references any document files other than the base file.
+ </para>
+ </listitem>
+ </orderedlist>
+ <section id="ch-getting-files-build-system-targets">
+ <title>Build System Actions</title>
+ <para>
+ To render the <abbrev>XML</abbrev> document into <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev> the command: <userinput>make html</userinput>,
+ <userinput>make html-nochunk</userinput>, or <userinput>make pdf</userinput> may be used.
+ </para>
+ <para>
+ <xref linkend="ch-getting-files-build-system-targets-table"/> lists the defined build system targets.
+ </para>
+ <table id="ch-getting-files-build-system-targets-table">
+ <title>Document Building Targets</title>
+ <tgroup cols="2">
+ <colspec align="right" colnum="1" colwidth="*1"/>
+ <colspec colnum="2" colwidth="*5"/>
+ <thead>
+ <row>
+ <entry><phrase>Target</phrase></entry>
+ <entry><phrase>Description</phrase></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><phrase><filename>all</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds the <abbrev>HTML</abbrev>, and the <abbrev>PDF</abbrev> forms of the document in all its defined translations.
+ </para>
+ <para>
+ Also builds the archives, such as <application>tar(1)</application> and <application>rpm(8)</application>.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>tarball</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <application>tar(1)</application> archive for all document languages.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>pdf</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <abbrev>PDF</abbrev> document for all document languages.
+ </para>
+ <para>
+ Currently, <abbrev>PDF</abbrev> production is problematic and probably will not work for your document.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>html</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <abbrev>HTML</abbrev> document for each defined translation.
+ Output is placed in a separate directory:
+ <systemitem class="macro">${DOCBASE}</systemitem><filename>-</filename><systemitem class="macro">${LANG}</systemitem><filename>/</filename>; each document section is given its own file within that directory.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>html-nochunks</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <abbrev>HTML</abbrev> document for each defined translation.
+ Output is placed in a single file:
+ <systemitem class="macro">${DOCBASE}</systemitem><filename>-</filename><systemitem class="macro">${LANG}</systemitem><filename>.html</filename>; no other files are created.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>clean</filename></phrase></entry>
+ <entry>
+ <para>
+ Deletes any temporary, or generated files.
+ Does <emphasis>not</emphasis> erase any <abbrev>HTML</abbrev>, <abbrev>PDF</abbrev>, or archive files.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>distclean</filename></phrase></entry>
+ <entry>
+ <para>
+ Erases all <abbrev>HTML</abbrev>, <abbrev>PDF</abbrev>, and archive files.
+ Automatically invokes the <filename>clean</filename> target as well.
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>
+ You can add your own special targets and rules by placing them at the bottom of the document <filename>Makefile</filename>, below the <literal>include</literal> line.
+ </para>
+ <para>
+ Be sure to follow your target definitions with a double colon, not just one.
+ This will allow you to supply extra steps for the defined targets.
+ </para>
+ </section>
+ <section id="ch-getting-files-build-system-images">
+ <title>Using Document Image Files</title>
+ <para>
+ Image files, such as <filename>.PNG</filename>, are often used in documents.
+ While your image files may be placed anywhere you like, we recommend that you store your image files in a <filename>figs/</filename> subdirectory within your document directory.
+ In other words, place your image <filename>picture.png</filename> in the <filename>mydoc/figs/picture.png</filename> file.
+ </para>
+ <note>
+ <title>Use PNG Images, Not JPG</title>
+ <para>
+ Depending on the output media, sometimes images may be scaled,
+ streteched, or squashed.
+ To minimize any distortions, we recommend that you use only
+ <wordasword>PDF</wordasword> images and avoid <wordasword>JPG</wordasword> files.
+ </para>
+ <para>
+ You may find the <systemitem class="filesystem">convert(1)</systemitem> program, from the <application>ImageMagick</application> <abbrev>RPM</abbrev> package, provides a convenient way to reformat any <wordasword>JPG</wordasword> images you already have.
+ </para>
+ </note>
+ <para>
+ You may organize your image files into as many subdirectories under <filename>figs/</filename> as you choose.
+ The document building system will recreate your image subdirectory structure in the output documents.
+ </para>
+ <para>
+ In addition, we recommend that you follow our convention on naming the image.
+ For example, an image often contains a caption or other text.
+ This text should be translated along with the document content, so keeping <filename>words-en.png</filename> separate from <filename>words-ru.png</filename> is a good practice.
+ An image file with no text can be named just <filename>picture.png</filename>, for example.
+ </para>
+ <para>
+ Sometimes, a document may require images that do not follow the naming convention.
+ You may still use these images with the document building system, but it requires that you create an ordinary text file containing the image filenames you want to use.
+ This file must be named <filename>figs/Manifest-</filename><systemitem class="macro">${LANG}</systemitem> so that the build system can find it as the search for image filenames begins.
+ </para>
+ <para>
+ An easy way to create the <filename>figs/Manifest-</filename><systemitem class="macro">${LANG}</systemitem> file is shown in <xref linkend="ch-getting-files-build-system-manifest"/>.
+ </para>
+ <example id="ch-getting-files-build-system-manifest">
+ <title>Building A Manifest</title>
+<programlisting>
+rm -f figs/Manifest-en
+find figs -print >/tmp/manifest
+mv /tmp/manifest figs/Manifest-en
+vi figs/Manifest-en
+</programlisting>
+</example>
+
+ </section>
+d113 1
+a113 2
+sgml-parent-document: ("documentation-guide-en.xml" "book" "chapter")
+fill-column: 80
+@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-intro.xml,v b/old-documentation-guide/en_US/Attic/docs-intro.xml,v
new file mode 100644
index 0000000..8aba8c4
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-intro.xml,v
@@ -0,0 +1,163 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2006.12.16.22.55.41; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!-- $Id: docs-intro.xml,v 1.2 2006/12/16 22:55:41 pfrields Exp $ -->
+<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+
+<preface id="ch-intro">
+ <title>Introduction</title>
+
+ <para>
+ The goal of the &FDP; is to create easy-to-follow, task-based
+ documentation for &FED; users and developers. Other than the
+ <citetitle>&IG;</citetitle>, each tutorial should be in DocBook XML
+ article format, with one article per topic. This way, writers can
+ contribute documentation about a specific topic without having to
+ worry about how it fits into a manual or how it flows with other
+ topics.
+ </para>
+
+ <para>
+ The following tools are used:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>DocBook XML v4.4</para>
+ </listitem>
+ <listitem>
+ <para>Custom XSLT stylesheets for both print and HTML
+ versions</para>
+ </listitem>
+ <listitem>
+ <para>Custom scripts to generate HTML output (use
+ <command>xmlto</command>)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs with PSGML mode (optional, but recommended)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs with nXML mode (optional)</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ This document explains the tools used by the &FDP; and provides
+ writing and tagging guidelines to make &FED; documentation is
+ consistent and easy-to-follow.
+ </para>
+
+</preface>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.2
+log
+ at Slightly reorganize and improve module chapter, including more information on rpm-info and customizing a module.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-intro.xml,v 1.1 2006/11/23 02:24:17 pfrields Exp $ -->
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d1 2
+a2 2
+<!-- $Id: docs-intro-en.xml,v 1.3 2004/08/13 16:08:48 tfox Exp $ -->
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+d12 2
+a13 2
+ <preface id="ch-intro">
+ <title>Introduction</title>
+d15 48
+a62 38
+ <para>
+ The goal of the Docs Project is to create easy-to-follow, task-based
+ documentation for &FC; users and developers. Other than the
+ <citetitle>&IG;</citetitle>, each tutorial should be in DocBook XML
+ article format, with one article per topic. This way, writers can
+ contribute documentation about a specific topic without having to worry
+ about how it fits into a manual or how it flows with other topics.
+ </para>
+
+ <para>
+ The following tools are used:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>DocBook XML v4.1</para>
+ </listitem>
+ <listitem>
+ <para>Custom XSLT stylesheets for both print and HTML versions</para>
+ </listitem>
+ <listitem>
+ <para>Custom scripts to generate PDF and HTML output (use <command>xmlto</command>)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs with PSGML mode (optional, but recommended)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs with nXML mode (optional, but also recommended)</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The purpose of this document is to explain the tools used by the Docs
+ Project as well as to provide writing and tagging guidelines so that the
+ documentation is consistent and easy-to-follow.
+ </para>
+
+ </preface>
+@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-module-struct.xml,v b/old-documentation-guide/en_US/Attic/docs-module-struct.xml,v
new file mode 100644
index 0000000..04bc057
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-module-struct.xml,v
@@ -0,0 +1,752 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2006.12.16.22.55.41; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.29.22.18.53; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!-- $Id: -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<chapter id="ch-how-modules-work">
+ <title>How Modules Work</title>
+ <para>Documentation modules have a specific structure that enables the
+ preconfigured tools to work correctly. Follow this structure exactly or you
+ may have problems building your module. The &FDP; build tools locate
+ resources in the module and use them to build new output such as HTML or RPM
+ packages.</para>
+ <section id="sn-module-struct">
+ <title>Structure of a Module</title>
+ <para><xref linkend="ex-module-structure"/> shows a directory tree
+ of an example module, excluding any <filename
+ class="directory">CVS</filename> folders:</para>
+ <example id="ex-module-structure">
+ <title>Example Module Structure</title>
+ <screen><computeroutput><![CDATA[example-doc/
+ |
+ |-- en_US/
+ | |-- example-doc.xml
+ | |-- para.xml
+ | |-- doc-entities.xml
+ | `-- rpm-info.xml
+ |
+ |-- figs/
+ | |-- fedora-logo-sprite.eps
+ | `-- fedora-logo-sprite.png
+ |
+ |-- po/
+ | |-- de.po
+ | |-- example-doc.pot
+ | `-- pt.po
+ |
+ `-- Makefile]]></computeroutput></screen>
+ </example>
+ <formalpara>
+ <title>Primary language directory (required)</title>
+ <para>This is the only directory absolutely required. It is named for the
+ original language of the document, such as <filename
+ class="directory">en_US</filename> (US English). The primary language
+ does not have to be US English; all languages are supported. This
+ directory contains all the XML source for the actual document, as well
+ as XML source for document-specific
+ <firstterm>entities</firstterm><footnote>
+ <para>Think of an XML entity as a predefined snippet of information.
+ It can represent a chunk of XML source, or simply a word or
+ character. If the information changes, it need be replaced only
+ once, in the definition, to fix all usage.</para>
+ </footnote>.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Graphics directory (optional)</title>
+ <para>The <filename class="directory">figs/</filename> directory is an
+ optional directory where graphics for the document should be stored. If
+ graphics are screenshots that are particular to a language, the
+ <filename class="directory">figs/</filename> directory can and should be
+ stored in a language directory.</para>
+ </formalpara>
+ <formalpara>
+ <title>Translation (PO) directory (optional)</title>
+ <para>The <filename class="directory">po/</filename> directory contains
+ specially formatted files created and used by translators. The &FDP;
+ build tools use these files to create translated versions of documents.
+ The translated documents are not stored in CVS; they are created as
+ needed from these PO files.</para>
+ </formalpara>
+ <formalpara>
+ <title>Makefile (required)</title>
+ <para>The <filename>Makefile</filename> controls the build process. Its
+ content is discussed in <xref linkend="ex-makefile"/>.</para>
+ </formalpara>
+ <formalpara>
+ <title><filename>rpm-info.xml</filename> (required)</title>
+ <para>The <filename>rpm-info.xml</filename> file contains document
+ specific metadata</para>
+ </formalpara>
+ </section>
+ <section id="ch-getting-files-build-system">
+ <title>The Document Build System</title>
+ <para>
+ The build system can render the document into another format such
+ as <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using
+ <command>make(1)</command> and shell scripts. Authors need
+ <emphasis>no</emphasis> prior experience with either shell scripts
+ or a <command>make(1)</command>.
+ </para>
+ <section id="sn-makefile">
+ <title>The Document <filename>Makefile</filename></title>
+ <para>
+ Each individual document has its own
+ <filename>Makefile</filename>, which only needs to be a few
+ lines long. The document <filename>Makefile</filename> content
+ is designed for cut and paste operations.
+ </para>
+ <para>
+ <xref linkend="ex-makefile"/> below shows the whole
+ <filename>Makefile</filename> for a simple document with two
+ files and two translations.
+ </para>
+ <example id="ex-makefile">
+ <title>Sample Document Makefile</title>
+ <programlisting><![CDATA[DOCBASE = example-doc
+PRI_LANG = en_US
+OTHERS = de pt
+DOC_ENTITIES = doc-entities
+
+define XMLFILES_template
+XMLFILES-${1} = ${1}/example-doc.xml \
+ ${1}/para.xml
+endef
+
+include ../docs-common/Makefile.common]]></programlisting>
+ </example>
+ <para>
+ Do not be concerned with some of the more complicated syntax
+ such as the <command>XMLFILES_template</command> stanza. An
+ explanation for this template appears a few paragraphs
+ below.</para>
+ <formalpara>
+ <title><systemitem class="macro">DOCBASE</systemitem></title>
+ <para>This variable contains the name for the main (parent) XML
+ document. Follow convention by naming your document after the
+ module name.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">PRI_LANG</systemitem></title>
+ <para>This variable contains the ISO code for the original
+ version of the document, such as
+ <systemitem>en_US</systemitem>.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">OTHERS</systemitem></title>
+ <para>This variable contains a listing of ISO codes for any
+ other versions into which the document has been translated.
+ The module must contain a <filename
+ class="directory">po/</filename> directory and a PO file for
+ any indicated additional languages.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">DOC_ENTITIES</systemitem></title>
+ <para>This variable contains a listing of any files containing
+ entity definitions. The &FDP; uses a special XML format to
+ record document-specific entities, so they can be translated and
+ built on the fly like any other XML document. An example is
+ shown later in this guide. <!-- need xref here --></para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem
+ class="macro">XMLFILES_template</systemitem></title>
+ <para>This template allows the build tools to work with the
+ document in multiple languages once it is translated. The
+ <systemitem class="macro">${1}</systemitem> marking is a
+ variable used to substitute the appropriate language. This
+ template is not terribly complicated. For a new module,
+ duplicate this section exactly except for the actual
+ filenames. Prepend the text <systemitem
+ class="macro">${1}/</systemitem>, in place of the language
+ code directory name, to each filename in your document.
+ </para>
+ </formalpara>
+ <important>
+ <title>Files Exempt From Listing</title>
+ <para>Do not include the document-specific entities XML file or
+ the <filename>rpm-info.xml</filename> file, which will be
+ discussed later in this guide.<!-- include xref --></para>
+ </important>
+ <para>
+ The final line, beginning with <literal>include</literal>,
+ references the main <filename>Makefile</filename> for the build
+ system. This <filename>Makefile.common</filename> file contains
+ all the <application>make(1)</application> targets and rules to
+ actually build the document and the various archives.
+ </para>
+ </section>
+ <section>
+ <title>The Document <filename>rpm-info.xml</filename></title>
+ <para>Each document module's primary language directory contains a
+ file called <filename>rpm-info.xml</filename>. This file
+ contains document-specific metadata used to generate revision
+ history, copyright, and contributor information. It follows a
+ DTD specification included with the rest of the build system
+ tools.</para>
+ <para><xref linkend="ex-rpminfo"/> illustrates the content of
+ this file:</para>
+ <example id="ex-rpminfo">
+ <title>Example <filename>rpm-info.xml</filename> File</title>
+ <programlisting><![CDATA[<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE rpm-info SYSTEM "../../docs-common/packaging/rpm-info.dtd">
+
+<rpm-info>
+ <colophon>
+ <worker surname="Smith" firstname="John" othername="Q."
+ id="JohnSmith" email="jsmith@@example.com"
+ wholename="John Q. Smith" initials="JS"/>
+ </colophon>
+ <author worker="JohnSmith"/>
+ <license>
+ <rights>OPL</rights>
+ <version>1.0</version>
+ </license>
+ <copyright>
+ <year>2006</year>
+ <holder>John Q. Smith</holder>
+ </copyright>
+ <title>My Tutorial</title>
+ <desc>A tutorial about something important</desc>
+ <changelog order="newest-first">
+ <revision date="2006-06-01" number="0.1" role="doc">
+ <author worker="JohnSmith"/>
+ <details>First draft</details>
+ </revision>
+ </changelog>
+</rpm-info>]]></programlisting>
+ </example>
+ <para>If you are not familiar with XML editing, copy and paste
+ this file from an existing module and then edit the values for
+ the various elements as appropriate. Consult &FDP; members and
+ help channels for more assistance if needed.</para>
+ </section>
+ </section>
+ <section id="ch-getting-files-build-system-targets">
+ <title>Build System Actions</title>
+ <para>
+ To render the <abbrev>XML</abbrev> document into another format,
+ use one of the following <command>make</command> targets:
+ </para>
+ <formalpara>
+ <title><systemitem class="macro">html</systemitem></title>
+ <para>This target builds the "chunked" <abbrev>HTML</abbrev>
+ document for each defined translation. Output is placed in a
+ separate directory named <filename class="directory"><systemitem
+ class="macro">${DOCBASE}</systemitem>-<systemitem
+ class="macro">${LANG}</systemitem>/</filename>. Each
+ document section is a separate file within that
+ directory.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem
+ class="macro">html-nochunks</systemitem></title>
+ <para>This target builds the "non-chunked" <abbrev>HTML</abbrev>
+ document for each defined translation. Output is placed in a
+ single file: <filename><systemitem
+ class="macro">${DOCBASE}</systemitem>-<systemitem
+ class="macro">${LANG}</systemitem>.html</filename>; no other
+ files are created.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">pdf</systemitem></title>
+ <para>This target builds only the <abbrev>PDF</abbrev> document
+ for all document languages. <abbrev>PDF</abbrev> production is
+ currently erratic and may not work for your document.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">tarball</systemitem></title>
+ <para>This target builds only the <command>tar(1)</command>
+ archive for all document languages.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">all</systemitem></title>
+ <para>This target builds all targets listed above.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">clean</systemitem></title>
+ <para>This target deletes any temporary, or generated files, but
+ does <emphasis>not</emphasis> erase any <abbrev>HTML</abbrev>,
+ <abbrev>PDF</abbrev>, or archive files.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">distclean</systemitem></title>
+ <para>This target erases all <abbrev>HTML</abbrev>,
+ <abbrev>PDF</abbrev>, and archive files. This target
+ automatically invokes the <filename>clean</filename> target as
+ well.</para>
+ </formalpara>
+ <section>
+ <title>Adding or Changing Targets</title>
+ <para>
+ To add a new target and rules, place them at the bottom of the
+ document <filename>Makefile</filename>, below the
+ <literal>include</literal> line. Follow your target definitions
+ with a double colon, not a single colon. The double colon
+ allows you to specify additional rules for existing targets, or
+ to write rules for a new target.
+ </para>
+ <para>
+ For more information on using <command>make(1)</command>,
+ consult the online documentation with the command <command>info
+ make</command> in a terminal.
+ </para>
+ </section>
+ <section id="ch-getting-files-build-system-images">
+ <title>Using Document Image Files</title>
+ <para>
+ Tutorial documents often make use of images such as <filename
+ class="extension">.PNG</filename> files. Store image files in
+ a <filename class="directory">figs/</filename> folder in the
+ main module directory, as shown in <xref
+ linkend="ex-module-structure"/>.
+ </para>
+ <para>
+ Depending on the output media, sometimes images may be scaled,
+ streteched, or squashed. To minimize any distortions, we
+ recommend that you use only <filename
+ class="extension">.PNG</filename> images. Avoid <filename
+ class="extension">.JPG</filename> files. The
+ <command>convert(1)</command> program, from the <package
+ role="rpm">ImageMagick</package> <abbrev>RPM</abbrev> package,
+ provides a convenient way to reformat <filename
+ class="extension">.JPG</filename> images into <filename
+ class="extension">.PNG</filename> format. For more information
+ on formatting images such as screenshots, refer to <xref
+ linkend="s1-screenshots"/>.
+ </para>
+ <para>
+ Image files may be organized into subdirectories under
+ <filename>figs/</filename> if necessary. The document building
+ system recreates the image subdirectory structure in the output
+ documents.
+ </para>
+ <para>
+ Images often contain labels or other text which may need to be
+ localized. A screenshot of a program, for example, may require
+ a version for each translated language. Name language-dependent
+ image files such as program screenshots by adding the language
+ code to the filename, such as
+ <filename>menu-en_US.png</filename>. Language-independent
+ images, such as <filename>icon.png</filename>, do not need
+ language codes.
+ </para>
+ <para>
+ Sometimes, a document may require images that do not follow the
+ naming convention. To use these images with the document
+ building system, create an ordinary text file containing the
+ image filenames. This file must be named
+ <filename>figs/Manifest-</filename><systemitem
+ class="macro">${LANG}</systemitem> so the build system finds
+ it when searching for image filenames.
+ </para>
+ <para>
+ <xref linkend="ch-getting-files-build-system-manifest"/>
+ demonstrates one way to create this
+ <filename>Manifest</filename> file.
+ </para>
+ <example id="ch-getting-files-build-system-manifest">
+ <title>Building A Manifest</title>
+ <programlisting><![CDATA[rm -f figs/Manifest-en
+find figs -print >/tmp/manifest
+mv /tmp/manifest figs/Manifest-en]]></programlisting>
+ </example>
+ </section>
+ <section>
+ <title>Adding a New DocBook XML File</title>
+ <para>To add a new DocBook XML file to an existing document,
+ follow these steps:</para>
+ <procedure>
+ <step>
+ <para>Place the new DocBook XML file in the primary language
+ directory.</para>
+ </step>
+ <step>
+ <para>Edit the <filename>Makefile</filename> and add the
+ filename to the <varname>XMLFILES-${1}</varname> listing.
+ Append a <keycap>\</keycap> to the last existing line, and
+ on the next line add an entry for the new file. Remember to
+ add the <literal>${1}/</literal> prefix as a substitute for
+ the language directory name.</para>
+ </step>
+ </procedure>
+ </section>
+ <section>
+ <title>Adding a Translation</title>
+ <para>Translations are stored as PO (portable object) files, which
+ the toolchain transforms into translated documents. Each PO
+ file is based on the POT (PO template) for the document and
+ translated by the &FED; Translation Project. To add a
+ translation, follow these steps:</para>
+ <procedure>
+ <step>
+ <para>If the <filename class="directory">po/</filename>
+ directory does not exist, create it and add it to
+ CVS:</para>
+ <screen><![CDATA[mkdir po && cvs add po/]]></screen>
+ </step>
+ <step>
+ <para>If it does not exist, create the POT file:</para>
+ <screen><![CDATA[make pot]]></screen>
+ </step>
+ <step>
+ <para>Add the new translation language to the
+ <varname>OTHERS</varname> listing in the
+ <filename>Makefile</filename>.</para>
+ </step>
+ <step>
+ <para>Although translators often copy the POT manually to
+ create the new PO file, the following command also
+ works:</para>
+ <screen>make po/<replaceable>lang</replaceable>.po</screen>
+ </step>
+ </procedure>
+ </section>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.2
+log
+ at Slightly reorganize and improve module chapter, including more information on rpm-info and customizing a module.
+@
+text
+@@
+
+
+1.1
+log
+ at Exclude nxml chapter for now, and reorganize first chapter
+@
+text
+ at d20 7
+a26 4
+ <para>The following listing shows a directory tree of an example module,
+ excluding any <filename class="directory">CVS</filename> folders:</para>
+
+ <screen><computeroutput><![CDATA[example-doc/
+d28 5
+a32 4
+ |-- example-doc.xml
+ |-- para.xml
+ |-- doc-entities.xml
+ |-- rpm-info.xml
+d34 3
+a36 2
+ |-- fedora-logo-sprite.eps
+ |-- fedora-logo-sprite.png
+d38 6
+a43 5
+ |-- de.po
+ |-- example-doc.pot
+ |-- pt.po
+ |-- Makefile]]></computeroutput></screen>
+
+d79 6
+a84 1
+ content is discussed below. <!-- include xref here --></para>
+d90 3
+a92 5
+ Common tasks such as rendering the document into either
+ <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev> can be performed
+ easily using the document building system. The building system
+ heavily leverages the <application>make(1)</application> tool and
+ shell scripts to automate these activities, but authors need
+d94 1
+a94 5
+ or a <filename>Makefile</filename>. While individual documents do
+ have their own <filename>Makefile</filename>, it is only a few
+ lines long and very simple. The document
+ <filename>Makefile</filename> content is designed for cut and
+ paste operations.
+d96 16
+a111 11
+ <para>
+ <xref
+ linkend="ch-getting-files-build-system-makefile"/> below shows the
+ whole <filename>Makefile</filename> for a simple document having
+ only two files and one language.
+ </para>
+ <example id="ch-getting-files-build-system-makefile">
+ <title>Sample Document Makefile</title>
+ <programlisting>
+<![CDATA[
+DOCBASE = example-doc
+d121 111
+a231 53
+include ../docs-common/Makefile.common
+]]>
+ </programlisting>
+ </example>
+ <para>
+ Do not be concerned with some of the more complicated syntax (in
+ particular, the <command>XMLFILES_template</command> stanza). An
+ explanation for this template appears a few paragraphs
+ below.</para>
+ <formalpara>
+ <title><varname>DOCBASE</varname></title>
+ <para>This variable contains the name for the main (parent) XML document.
+ Follow convention by naming your document after the module name.</para>
+ </formalpara>
+ <formalpara>
+ <title><varname>PRI_LANG</varname></title>
+ <para>This variable contains the ISO code for the original version of the
+ document, such as <systemitem>en_US</systemitem>.</para>
+ </formalpara>
+ <formalpara>
+ <title><varname>OTHERS</varname></title>
+ <para>This variable contains a listing of ISO codes for any other versions
+ into which the document has been translated. The module must contain a
+ <filename class="directory">po/</filename> directory and a PO file for
+ any indicated additional languages.</para>
+ </formalpara>
+ <formalpara>
+ <title><varname>DOC_ENTITIES</varname></title>
+ <para>This variable contains a listing of any files containing entity
+ definitions. The &FDP; uses a special XML format to record
+ document-specific entities, so they can be translated and built on the
+ fly like any other XML document. An example is shown later in this
+ guide. <!-- need xref here --></para>
+ </formalpara>
+ <formalpara>
+ <title><varname>XMLFILES_template</varname></title>
+ <para>This template allows the build tools to work with the
+ document in multiple languages once it is translated. The
+ <varname>${1}</varname> marking is a variable used to substitute
+ the appropriate language. This template is not terribly
+ complicated. For a new module, duplicate this section exactly
+ except for the actual filenames. Prepend the text
+ <varname>${1}/</varname>, in place of the language code
+ directory name, to each filename in your document.
+ </para>
+ </formalpara>
+ <important>
+ <title>Files Exempt From Listing</title>
+ <para>Do not include the document-specific entities XML file or the
+ <filename>rpm-info.xml</filename> file, which will be discussed later in
+ this guide.<!-- include xref --></para>
+ </important>
+ <!-- TEMP MARKER - PWF finished here Nov 28 2006 -->
+d233 2
+a234 5
+ The final line, beginning with <literal>include</literal>, references the
+ main <filename>Makefile</filename> for the build system. This
+ <filename>Makefile.common</filename> file contains all the
+ <application>make(1)</application> targets and rules to actually build the
+ document and the various archives.
+d236 50
+a285 113
+ <para>
+ Add new document translations by:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Add the translated document files to the document directory.
+ Be sure to use the proper <systemitem class="macro">${LANG}</systemitem> filename component to keep the filenames similar, but unique.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Edit the <filename>Makefile</filename> to append the new <systemitem class="macro">${LANG}</systemitem> to the <systemitem class="macro">LANGUAGES</systemitem> definition.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Create a new <systemitem class="macro">XMLEXTRAFILES-${LANG}</systemitem> definition that references any document files other than the base file.
+ </para>
+ </listitem>
+ </orderedlist>
+ <section id="ch-getting-files-build-system-targets">
+ <title>Build System Actions</title>
+ <para>
+ To render the <abbrev>XML</abbrev> document into <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev> the command: <userinput>make html</userinput>,
+ <userinput>make html-nochunk</userinput>, or <userinput>make pdf</userinput> may be used.
+ </para>
+ <para>
+ <xref linkend="ch-getting-files-build-system-targets-table"/> lists the defined build system targets.
+ </para>
+ <table id="ch-getting-files-build-system-targets-table">
+ <title>Document Building Targets</title>
+ <tgroup cols="2">
+ <colspec align="right" colnum="1" colwidth="*1"/>
+ <colspec colnum="2" colwidth="*5"/>
+ <thead>
+ <row>
+ <entry><phrase>Target</phrase></entry>
+ <entry><phrase>Description</phrase></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><phrase><filename>all</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds the <abbrev>HTML</abbrev>, and the <abbrev>PDF</abbrev> forms of the document in all its defined translations.
+ </para>
+ <para>
+ Also builds the archives, such as <application>tar(1)</application> and <application>rpm(8)</application>.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>tarball</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <application>tar(1)</application> archive for all document languages.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>pdf</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <abbrev>PDF</abbrev> document for all document languages.
+ </para>
+ <para>
+ Currently, <abbrev>PDF</abbrev> production is problematic and probably will not work for your document.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>html</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <abbrev>HTML</abbrev> document for each defined translation.
+ Output is placed in a separate directory:
+ <systemitem class="macro">${DOCBASE}</systemitem><filename>-</filename><systemitem class="macro">${LANG}</systemitem><filename>/</filename>; each document section is given its own file within that directory.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>html-nochunks</filename></phrase></entry>
+ <entry>
+ <para>
+ Builds only the <abbrev>HTML</abbrev> document for each defined translation.
+ Output is placed in a single file:
+ <systemitem class="macro">${DOCBASE}</systemitem><filename>-</filename><systemitem class="macro">${LANG}</systemitem><filename>.html</filename>; no other files are created.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>clean</filename></phrase></entry>
+ <entry>
+ <para>
+ Deletes any temporary, or generated files.
+ Does <emphasis>not</emphasis> erase any <abbrev>HTML</abbrev>, <abbrev>PDF</abbrev>, or archive files.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry><phrase><filename>distclean</filename></phrase></entry>
+ <entry>
+ <para>
+ Erases all <abbrev>HTML</abbrev>, <abbrev>PDF</abbrev>, and archive files.
+ Automatically invokes the <filename>clean</filename> target as well.
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+d287 6
+a292 1
+ You can add your own special targets and rules by placing them at the bottom of the document <filename>Makefile</filename>, below the <literal>include</literal> line.
+d295 3
+a297 2
+ Be sure to follow your target definitions with a double colon, not just one.
+ This will allow you to supply extra steps for the defined targets.
+d303 5
+a307 30
+ Image files, such as <filename>.PNG</filename>, are often used in documents.
+ While your image files may be placed anywhere you like, we recommend that you store your image files in a <filename>figs/</filename> subdirectory within your document directory.
+ In other words, place your image <filename>picture.png</filename> in the <filename>mydoc/figs/picture.png</filename> file.
+ </para>
+ <note>
+ <title>Use PNG Images, Not JPG</title>
+ <para>
+ Depending on the output media, sometimes images may be scaled,
+ streteched, or squashed.
+ To minimize any distortions, we recommend that you use only
+ <wordasword>PDF</wordasword> images and avoid <wordasword>JPG</wordasword> files.
+ </para>
+ <para>
+ You may find the <systemitem class="filesystem">convert(1)</systemitem> program, from the <application>ImageMagick</application> <abbrev>RPM</abbrev> package, provides a convenient way to reformat any <wordasword>JPG</wordasword> images you already have.
+ </para>
+ </note>
+ <para>
+ You may organize your image files into as many subdirectories under <filename>figs/</filename> as you choose.
+ The document building system will recreate your image subdirectory structure in the output documents.
+ </para>
+ <para>
+ In addition, we recommend that you follow our convention on naming the image.
+ For example, an image often contains a caption or other text.
+ This text should be translated along with the document content, so keeping <filename>words-en.png</filename> separate from <filename>words-ru.png</filename> is a good practice.
+ An image file with no text can be named just <filename>picture.png</filename>, for example.
+ </para>
+ <para>
+ Sometimes, a document may require images that do not follow the naming convention.
+ You may still use these images with the document building system, but it requires that you create an ordinary text file containing the image filenames you want to use.
+ This file must be named <filename>figs/Manifest-</filename><systemitem class="macro">${LANG}</systemitem> so that the build system can find it as the search for image filenames begins.
+d310 42
+a351 1
+ An easy way to create the <filename>figs/Manifest-</filename><systemitem class="macro">${LANG}</systemitem> file is shown in <xref linkend="ch-getting-files-build-system-manifest"/>.
+d354 2
+a355 3
+ <title>Building A Manifest</title>
+<programlisting>
+rm -f figs/Manifest-en
+d357 52
+a408 5
+mv /tmp/manifest figs/Manifest-en
+vi figs/Manifest-en
+</programlisting>
+</example>
+
+@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-rh-guidelines.xml,v b/old-documentation-guide/en_US/Attic/docs-rh-guidelines.xml,v
new file mode 100644
index 0000000..f46bae8
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-rh-guidelines.xml,v
@@ -0,0 +1,1203 @@
+head 1.4;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.4
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.3;
+
+1.3
+date 2006.12.23.23.49.59; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2006.12.17.00.41.55; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.4
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<chapter id="ch-rh-guidelines">
+ <title>&RH; Documentation Guidelines</title>
+
+ <indexterm>
+ <primary>recursion</primary>
+ <see>recursion</see>
+ </indexterm>
+
+ <indexterm>
+ <primary>RTFM</primary>
+ <secondary>read the f*'ing manual</secondary>
+ <seealso>humor</seealso>
+ </indexterm>
+
+ <indexterm>
+ <primary>humor</primary>
+ <secondary>RTFM</secondary>
+ </indexterm>
+
+ <para>Please read this chapter carefully. This chapter describes the
+ guidelines that must be followed such as naming conventions.</para>
+
+ <sect1 id="s1-xml-guidelines-naming">
+ <title>ID Naming Conventions</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>naming conventions</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>naming conventions</primary>
+ </indexterm>
+
+ <para>You will see certain ID names referred to below and this will
+ help to explain how we come up with those names. For
+ example:</para>
+
+ <screen><![CDATA[<chapter id="ch-uniquename">
+
+<section id="sn-install-make-disks">
+
+<figure id="fig-redhat-config-kickstart-basic">]]></screen>
+
+ <para>IDs are unique identifiers, allowing DocBook XML to know where
+ to cross-reference a section or chapter or the like. The
+ following general rules apply to IDs:</para>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>naming conventions</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+
+ <itemizedlist>
+ <listitem>
+ <para>Restrict the ID name, which is everything between the
+ quotation marks, to 32 characters or fewer</para>
+ </listitem>
+ <listitem>
+ <para>Keep it as short and simple as possible</para>
+ </listitem>
+ <listitem>
+ <para>Make sure the name is recognizable and relevant to the
+ information</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>Some examples are <command>"ch-uniquename"</command> (13
+ characters) and <command>"sn-install-make-disks"</command> (21
+ characters).</para>
+
+ <para>A section within a particular chapter always uses the chapter
+ name (minus the <command>"ch-"</command>) in its ID. For example,
+ you are working with the <command>"ch-intro"</command> chapter and
+ need to create your first section on disk partitions. That section
+ ID would look similar to <command>"s1-intro-partition"</command>
+ which contains the section number, the main chapter ID, and a
+ unique ID for that section.</para>
+
+ <table id="tb-xml-namingconventions">
+ <title>Naming Conventions</title>
+
+ <tgroup cols="2">
+ <colspec colnum="1" colname="tag" colwidth="100"/>
+ <colspec colnum="2" colname="prefix" colwidth="100"/>
+ <thead>
+ <row>
+ <entry>Tag</entry>
+ <entry>Prefix</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><command>preface</command></entry>
+ <entry><computeroutput>pr-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>chapter</command></entry>
+ <entry><computeroutput>ch-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>section</command></entry>
+ <entry><computeroutput>sn-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect1</command></entry>
+ <entry><computeroutput>s1-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect2</command></entry>
+ <entry><computeroutput>s2-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect3</command></entry>
+ <entry><computeroutput>s3-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect4</command></entry>
+ <entry><computeroutput>s4-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>figure</command></entry>
+ <entry><computeroutput>fig-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>table</command></entry>
+ <entry><computeroutput>tb-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>appendix</command></entry>
+ <entry><computeroutput>ap-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>part</command></entry>
+ <entry><computeroutput>pt-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>example</command></entry>
+ <entry><computeroutput>ex-</computeroutput></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect1>
+
+ <sect1 id="s1-xml-guidelines-header">
+ <title>File Header</title>
+
+ <para>All the files must contain the CVS Id header. If you create a
+ new file, the first line must be:</para>
+
+ <screen><![CDATA[<!-- $Id: -->]]></screen>
+
+ <para>The first time it is committed to CVS (and every time it is
+ committed to CVS) the line is updated automatically to include
+ information about the file. For example:</para>
+
+ <screen><![CDATA[<!-- $Id: docs-rh-guidelines.xml,v 1.3 2006/12/23 23:49:59 pfrields Exp $ -->]]></screen>
+
+ </sect1>
+
+ <sect1 id="s1-xml-admon">
+ <title>Admonitions</title>
+
+ <indexterm>
+ <primary>admonitions</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>warning</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>tip</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>caution</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>important</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>warning</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>tip</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>note</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>caution</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>important</tertiary>
+ </indexterm>
+
+ <para>There are five types of admonitions in DocBook: Caution,
+ Important, Note, Tip, and Warning. All of the admonitions have
+ the same structure: an optional Title followed by paragraph-level
+ elements. The DocBook DTD does not impose any specific semantics
+ on the individual admonitions. For example, DocBook does not
+ mandate that Warnings be reserved for cases where bodily harm can
+ result.</para>
+
+ <sect2 id="s2-xml-notesetc">
+ <title>Creating Notes, Tips, Cautions, Importants, and
+ Warnings</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>tip</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>caution</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>important</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>warning</secondary>
+ </indexterm>
+
+ <para>There are several ways to bring attention to text within a
+ document. A <emphasis>Note</emphasis> is used to bring
+ additional information to the users' attention. A
+ <emphasis>Tip</emphasis> is used to show the user helpful
+ information or another way to do something. A
+ <emphasis>Caution</emphasis> is used to show the user they must
+ be careful when attempting a certain step. An
+ <emphasis>Important</emphasis> tag set can be used to show the
+ user a piece of information that should not be overlooked. While
+ this information may not change anything the user is doing, it
+ should show the user that this piece of information could be
+ vital. A <emphasis>Warning</emphasis> is used to show the reader
+ that their current setup will change or be altered, such as
+ files being removed, and they should not choose this operation
+ unless they are alright with the consequences.</para>
+
+ <para>The following lines of code will show the basic setup for
+ each case as mentioned above, along with an example of how it
+ would be displayed in the HTML.</para>
+
+ <screen><![CDATA[<note>
+ <title>Note</title>
+ <para>Body of text goes here.</para>
+</note>]]></screen>
+
+ <note>
+ <title>Note</title>
+ <para>Body of text goes here.</para>
+ </note>
+
+ <screen><![CDATA[<tip>
+ <title>Tip</title>
+ <para>Body of text goes here.</para>
+</tip>]]></screen>
+
+ <tip>
+ <title>Tip</title>
+ <para>Body of text goes here</para>
+ </tip>
+
+ <screen><![CDATA[<caution>
+ <title>Caution</title>
+ <para>Body of text goes here.</para>
+</caution>]]></screen>
+
+ <caution>
+ <title>Caution</title>
+ <para>Body of text goes here.</para>
+ </caution>
+
+ <screen><![CDATA[<important>
+ <title>Important</title>
+ <para>Body of text goes here.</para>
+</important>]]></screen>
+
+ <important>
+ <title>Important</title>
+ <para>Body of text goes here.</para>
+ </important>
+
+ <screen><![CDATA[<warning>
+ <title>Warning</title>
+ <para>Body of text goes here.</para>
+</warning>]]></screen>
+
+ <warning>
+ <title>Warning</title>
+ <para>Body of text goes here.</para>
+ </warning>
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-screenshots">
+ <title>Screenshots</title>
+
+ <indexterm>
+ <primary>screenshots</primary>
+ <secondary>how to take</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>screen captures</primary>
+ <see>screenshots</see>
+ </indexterm>
+ <indexterm>
+ <primary>screen grabs</primary>
+ <see>screenshots</see>
+ </indexterm>
+
+ <para>There are two types of screenshots: graphical and textual.
+ The philosophy on using these two types is <firstterm>rely on text
+ over graphics</firstterm>. This means, if you can say it in
+ text instead of showing a graphic, do so. A graphical screenshot
+ of a GUI can create a good setting of objects to then describe
+ textually, but you don't want to create a screenshot for each
+ graphical step.</para>
+ <para>The main reason for this preference is that a block of text
+ can usually convey more meaning than the same physical space of
+ graphics. This is highly dependent on the graphic; obviously, a
+ photographic image of a scene can convey more than 1000 words can.
+ A GUI screenshot is usually full of blank space with a few
+ elements that can just as easily be described or listed.</para>
+ <para>The steps for taking a graphical screenshot illustrate how
+ using text to describe a procedure is more concise than a series
+ of screenshots.</para>
+ <variablelist>
+ <varlistentry>
+ <term>Graphical Screenshot</term>
+ <listitem>
+ <procedure>
+ <step>
+ <para>Set the theme to Bluecurve defaults. This gives a look
+ that is familiar to most readers, and makes &FDP;
+ documents consistent. From the panel menu, choose
+ <guimenu>Preferences</guimenu>,
+ <guimenuitem>Theme</guimenuitem> and select
+ <guimenuitem>Bluecurve</guimenuitem> from the theme
+ list.</para>
+ </step>
+ <step>
+ <para>Set fonts to Bluecurve defaults as well. From the
+ panel menu, choose <guimenu>Preferences</guimenu>,
+ <guimenuitem>Fonts</guimenuitem>. Set the
+ <guilabel>Application font</guilabel> and the
+ <guilabel>Desktop font</guilabel> to Sans Regular 10.
+ Set the <guilabel>Window Title font</guilabel> to Sans
+ Bold 10. Set the <guilabel>Terminal font</guilabel> to
+ Monospace Regular 10.</para>
+ </step>
+ <step>
+ <para>Before taking the screenshot, try to resize the
+ targeted GUI element(s) to the smallest possible size
+ they can be. Your target is an image of 500 pixels or
+ less. If you are doing a screenshot of more than one
+ GUI element, you may need to resize the screenshot in a
+ following step.</para>
+ </step>
+ <step>
+ <para>To take the screenshot, select the GUI element with
+ your mouse, bringing it to the forefront, or otherwise
+ arranging the elements. Press <keycombo>
+ <keycap>Alt</keycap>
+ <keycap>Print Screen</keycap> </keycombo> to capture a
+ single GUI window. For capturing the entire desktop use
+ <keycap>Print Screen</keycap>. If you are taking a shot
+ of multiple elements and have grouped them closely
+ together, you can crop the resulting image in
+ <application>The GIMP</application>. The image will be
+ in the PNG format.</para>
+ </step>
+ <step>
+ <para>If you need to, you can resize using
+ <application>The GIMP</application>. With the image
+ open, right-click on it and choose
+ <guimenu>Image</guimenu> -> <guimenuitem>Scale
+ Image...</guimenuitem>. With the chain symbol intact,
+ set the <guilabel>New Width</guilabel> to <guilabel>500
+ px</guilabel>, and click <guibutton>OK</guibutton>.
+ Be sure to <keycombo>
+ <keycap>Ctrl</keycap> <keycap>s</keycap> </keycombo>
+ to save your changes to your PNG before converting to
+ EPS.</para>
+ </step>
+ <step>
+ <para>
+ With the image open in <application>The
+ GIMP</application>, right-click on the image,
+ selecting <guimenu>File</guimenu> ->
+ <guimenuitem>Save As...</guimenuitem>. Under
+ <guimenu>Determine File Type:</guimenu>, select
+ <guimenuitem>PostScript</guimenuitem>, then click
+ <guibutton>OK</guibutton>. Allow flattening of the image
+ by clicking <guibutton>Export</guibutton>.</para>
+ <para>In the <guilabel>Save as PostScript</guilabel>
+ window, select <guilabel>Encapsulated
+ PostScript</guilabel>, and click
+ <guibutton>OK</guibutton>.</para>
+ </step>
+ </procedure>
+ <para>For more information about calling the images from the
+ XML, refer to <xref linkend="s1-xml-tags-figure"/>.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Text Screenshot</term>
+ <listitem>
+ <para>Textual screen information is also useful for readers.
+ If you use a graphical screenshot to illustrate a function,
+ and the textual mode has identical functions, you should not
+ include both, unless omitting either would make your
+ description unclear. You should make your information
+ generic over specific. Omit the username and machine
+ information, and separate what the user types from sample
+ command output. Also, in <command>screen</command> tags,
+ what the user types should be in
+ <command>userinput</command> tags, and what the user is
+ shown as output should be in
+ <command>computeroutput</command> tags. For example, the
+ usage in
+ <xref linkend="ex-text-screenshot-bad"/> should look like
+ <xref
+ linkend="ex-text-screenshot-good"/>.
+ </para>
+ <example id="ex-text-screenshot-bad">
+ <title>Incorrect Textual Screenshot</title>
+ <screen><userinput>ps ax | grep ssh</userinput>
+<computeroutput> 2564 ? S 0:23 /usr/sbin/sshd
+ 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
+ 8235 ? S 0:00 ssh -Nf rocky@@philadelphia.net -L 6667:localhost
+17223 pts/0 S 0:00 ssh rbalboa@@core-router7
+17227 pts/2 S 0:10 ssh rbalboa@@smbshare2
+21113 pts/7 S 1:19 ssh rocky@@xxx.private</computeroutput></screen>
+ </example>
+ <example id="ex-text-screenshot-good">
+ <title>Correct Textual Screenshot</title>
+ <para>To find all the currently active ssh sessions, execute the
+ following command:</para>
+ <screen><command>ps ax | grep ssh</command></screen>
+
+ <para>The output will appear similar to:</para>
+
+ <screen><computeroutput> 2564 ? S 0:23 /usr/sbin/sshd
+ 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
+ 8032 pts/0 S 0:00 ssh user@@host.example.com
+ 8032 pts/1 S 0:00 ssh root@@backup.example.com</computeroutput></screen>
+ </example>
+ <para>For more information about using screen, refer to <xref
+ linkend="s1-xml-tags-screen"/>.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect1>
+
+<!--
+ <sect1 id="s1-diagrams-images">
+ <title>Diagrams and Images</title>
+
+ <indexterm>
+ <primary>images</primary>
+ </indexterm>
+ <indexterm>
+ <primary>diagrams</primary>
+ <secondary>creating</secondary>
+ </indexterm>
+
+ <para>
+ To be written
+ </para>
+
+ </sect1>
+-->
+
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.3
+log
+ at Minor changes, major reformatting. Sorry about the noise.
+@
+text
+ at d173 1
+a173 1
+ <screen><![CDATA[<!-- $Id: docs-rh-guidelines.xml,v 1.2 2006/12/17 00:41:55 pfrields Exp $ -->]]></screen>
+@
+
+
+1.2
+log
+ at Ha, I know a lot more about why this book caused me so much pain when I first started learning DocBook and XML. Take that, crummy DOCTYPEs\!
+@
+text
+ at d10 2
+a11 2
+ <chapter id="ch-rh-guidelines">
+ <title>&RH; Documentation Guidelines</title>
+d13 21
+a33 4
+ <indexterm>
+ <primary>recursion</primary>
+ <see>recursion</see>
+ </indexterm>
+d36 2
+a37 3
+ <primary>RTFM</primary>
+ <secondary>read the f*'ing manual</secondary>
+ <seealso>humor</seealso>
+d41 1
+a41 2
+ <primary>humor</primary>
+ <secondary>RTFM</secondary>
+d44 3
+a46 3
+ <para>Please read this chapter carefully. This chapter describes the
+ guidelines that must be followed such as naming conventions.
+ </para>
+d48 1
+a48 2
+ <sect1 id="s1-xml-guidelines-naming">
+ <title>ID Naming Conventions</title>
+d50 1
+a50 4
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>naming conventions</secondary>
+ </indexterm>
+d52 1
+a52 3
+ <indexterm>
+ <primary>naming conventions</primary>
+ </indexterm>
+d54 3
+a56 3
+ <para>You will see certain ID names referred to below and this will
+ help to explain how we come up with those names. For example:
+ </para>
+d58 4
+a61 13
+<screen>
+<computeroutput>
+<chapter id="ch-uniquename">
+
+<sect3="s3-install-make-disks">
+
+<figure id="fig-redhat-config-kickstart-basic">
+</computeroutput>
+</screen>
+
+ <para>IDs are unique identifiers, allowing DocBook XML to know where to
+ cross-reference a section or chapter or the like.
+ </para>
+d63 4
+a66 6
+ <para>The general rules for defining an ID are:</para>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+d68 13
+a80 4
+ <indexterm>
+ <primary>naming conventions</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+d82 86
+a167 18
+ <itemizedlist>
+ <listitem>
+ <para>Keep it 32 characters or under (this is counted as
+ everything between the quotation marks)</para>
+ </listitem>
+ <listitem>
+ <para>Keep it as short and simple as possible</para>
+ </listitem>
+ <listitem>
+ <para>Make sure the name is relevant to the information (make it
+ recognizable)</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>Some examples are <command>"ch-uniquename"</command> (with 13
+ characters) and <command>"s3-install-make-disks"</command> (with 21
+ characters).
+ </para>
+d169 3
+a171 7
+ <para>A section within a particular chapter always uses the chapter
+ name (minus the <command>"ch-"</command>) in its ID. For example, you
+ are working with the <command>"ch-intro"</command> chapter and need to
+ create your first section on disk partitions. That section ID would look
+ similar to <command>"s1-intro-partition"</command> which contains the
+ section number, the main chapter ID, and a unique ID for that section.
+ </para>
+d173 1
+a173 2
+ <table id="tb-xml-namingconventions">
+ <title>Naming Conventions</title>
+d175 1
+a175 61
+ <tgroup cols="2">
+ <colspec colnum="1" colname="tag" colwidth="100"/>
+ <colspec colnum="2" colname="prefix" colwidth="100"/>
+ <thead>
+ <row>
+ <entry>Tag</entry>
+ <entry>Prefix</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><command>preface</command></entry>
+ <entry><computeroutput>pr-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>chapter</command></entry>
+ <entry><computeroutput>ch-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>section</command></entry>
+ <entry><computeroutput>sn-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect1</command></entry>
+ <entry><computeroutput>s1-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect2</command></entry>
+ <entry><computeroutput>s2-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect3</command></entry>
+ <entry><computeroutput>s3-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect4</command></entry>
+ <entry><computeroutput>s4-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>figure</command></entry>
+ <entry><computeroutput>fig-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>table</command></entry>
+ <entry><computeroutput>tb-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>appendix</command></entry>
+ <entry><computeroutput>ap-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>part</command></entry>
+ <entry><computeroutput>pt-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>example</command></entry>
+ <entry><computeroutput>ex-</computeroutput></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+d177 2
+a178 1
+ </sect1>
+d180 3
+a182 2
+ <sect1 id="s1-xml-guidelines-header">
+ <title>File Header</title>
+d184 4
+a187 3
+ <para>
+ All the files must contain the CVS Id header.
+ </para>
+d189 4
+a192 14
+ <para>
+ If you create a new file, the first line must be:
+ </para>
+<screen>
+<computeroutput>
+<!-- $Id: -->
+</computeroutput>
+</screen>
+
+ <para>
+ The first time it is committed to CVS (and every time it is committed to
+ CVS) the line is updated automatically to include information about the
+ file. For example:
+ </para>
+d194 20
+a213 5
+<screen>
+<computeroutput>
+<!-- $Id: docs-rh-guidelines.xml,v 1.1 2006/11/23 02:24:17 pfrields Exp $ -->
+</computeroutput>
+</screen>
+d215 17
+a231 1
+ </sect1>
+d233 5
+a237 2
+ <sect1 id="s1-xml-admon">
+ <title>Admonitions</title>
+d239 11
+a249 3
+ <indexterm>
+ <primary>admonitions</primary>
+ </indexterm>
+d253 1
+a253 1
+ <secondary>warning</secondary>
+a262 5
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+d273 1
+a273 26
+ <secondary>admonitions</secondary>
+ <tertiary>warning</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>tip</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>note</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>caution</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>important</tertiary>
+d276 59
+a334 113
+ <para>There are five types of admonitions in DocBook: Caution, Important,
+ Note, Tip, and Warning.</para>
+
+ <para>All of the admonitions have the same structure: an optional Title
+ followed by paragraph-level elements. The DocBook DTD does not impose any
+ specific semantics on the individual admonitions. For example, DocBook
+ does not mandate that Warnings be reserved for cases where bodily harm can
+ result.</para>
+
+
+ <sect2 id="s2-xml-notesetc">
+ <title>Creating Notes, Tips, Cautions, Importants, and Warnings</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>tip</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>caution</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>important</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>warning</secondary>
+ </indexterm>
+
+ <para>There are several ways to bring attention to text within a
+ document. A <emphasis>Note</emphasis> is used to bring additional
+ information to the users' attention. A <emphasis>Tip</emphasis> is
+ used to show the user helpful information or another way to do
+ something. A <emphasis>Caution</emphasis> is used to show the user
+ they must be careful when attempting a certain step. An
+ <emphasis>Important</emphasis> tag set can be used to show the user a
+ piece of information that should not be overlooked. While this
+ information may not change anything the user is doing, it should show
+ the user that this piece of information could be vital. A
+ <emphasis>Warning</emphasis> is used to show the reader that their
+ current setup will change or be altered, such as files being removed,
+ and they should not choose this operation unless they are alright with
+ the consequences.</para>
+
+ <para>The following lines of code will show the basic setup for each
+ case as mentioned above, along with an example of how it would be
+ displayed in the HTML.</para>
+
+
+<screen>
+<computeroutput>
+<note>
+<title>Note</title>
+<para>Body of text goes here.</para>
+</note>
+</computeroutput>
+</screen>
+
+ <note>
+ <title>Note</title> <para>Body of text goes here.</para>
+ </note>
+
+
+<screen>
+<computeroutput>
+<tip>
+<title>Tip</title>
+<para>Body of text goes here.</para>
+</tip>
+</computeroutput>
+</screen>
+
+ <tip>
+ <title>Tip</title>
+ <para>Body of text goes here</para>
+ </tip>
+
+<screen>
+<computeroutput>
+<caution>
+<title>Caution</title>
+<para>Body of text goes here.</para>
+</caution>
+</computeroutput>
+</screen>
+
+ <caution>
+ <title>Caution</title> <para>Body of text goes here.</para>
+ </caution>
+
+
+<screen>
+<computeroutput>
+<important>
+<title>Important</title>
+<para>Body of text goes here.</para>
+</important>
+</computeroutput>
+</screen>
+
+ <important>
+ <title>Important</title>
+ <para>Body of text goes here.</para>
+ </important>
+d336 10
+a345 13
+<screen>
+<computeroutput>
+<warning>
+<title>Warning</title>
+<para>Body of text goes here.</para>
+</warning>
+</computeroutput>
+</screen>
+
+ <warning>
+ <title>Warning</title> <para>Body of text goes here.</para>
+ </warning>
+ </sect2>
+d347 1
+a347 1
+ </sect1>
+d349 2
+a350 2
+ <sect1 id="s1-screenshots">
+ <title>Screenshots</title>
+d352 12
+a363 12
+ <indexterm>
+ <primary>screenshots</primary>
+ <secondary>how to take</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>screen captures</primary>
+ <see>screenshots</see>
+ </indexterm>
+ <indexterm>
+ <primary>screen grabs</primary>
+ <see>screenshots</see>
+ </indexterm>
+d365 60
+a424 34
+ <para>
+ There are two types of screenshots: graphical and textual. The
+ philosophy on using these two types is <firstterm>rely on text over
+ graphics</firstterm>. This means, if you can say it in text instead of
+ showing a graphic, do so. A graphical screenshot of a GUI can create a good
+ setting of objects to then describe textually, but you don't want to create
+ a screenshot for each graphical step.
+ </para>
+ <para>
+ The main reason for this preference is that a block of text can usually
+ convey more meaning than the same physical space of graphics. This is
+ highly dependent on the graphic; obviously, a photographic image of a
+ scene can convey more than 1000 words can. A GUI screenshot is usually
+ full of blank space with a few elements that can just as easily be
+ described or listed.
+ </para>
+ <para>
+ The steps for taking a graphical screenshot illustrate how using text to
+ describe a procedure is more concise than a series of screenshots.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Graphical Screenshot</term>
+ <listitem>
+ <procedure>
+ <step>
+ <para>
+ Set the theme to Bluecurve defaults. This gives a look that
+ is familiar to most readers, and makes &FDP; documents
+ consistent. From the panel menu, choose
+ <guimenu>Preferences</guimenu>,
+ <guimenuitem>Theme</guimenuitem> and select
+ <guimenuitem>Bluecurve</guimenuitem> from the theme list.
+ </para>
+d427 50
+a476 83
+ <para>
+ Set fonts to Bluecurve defaults as well. From the panel menu,
+ choose <guimenu>Preferences</guimenu>,
+ <guimenuitem>Fonts</guimenuitem>. Set the
+ <guilabel>Application font</guilabel> and the
+ <guilabel>Desktop font</guilabel> to Sans Regular 10. Set the
+ <guilabel>Window Title font</guilabel> to Sans Bold 10. Set
+ the <guilabel>Terminal font</guilabel> to Monospace Regular
+ 10.
+ </para>
+ </step>
+ <step>
+ <para>
+ Before taking the screenshot, try to resize the targeted GUI
+ element(s) to the smallest possible size they can be. Your
+ target is an image of 500 pixels or less. If you are doing a
+ screenshot of more than one GUI element, you may need to
+ resize the screenshot in a following step.
+ </para>
+ </step>
+ <step>
+ <para>
+ To take the screenshot, select the GUI element with your
+ mouse, bringing it to the forefront, or otherwise arranging
+ the elements. Press <keycombo> <keycap>Alt</keycap>
+ <keycap>Print Screen</keycap> </keycombo> to capture a single
+ GUI window. For capturing the entire desktop use
+ <keycap>Print Screen</keycap>. If you are taking a shot of
+ multiple elements and have grouped them closely together, you
+ can crop the resulting image in <application>The
+ GIMP</application>. The image will be in the PNG format.
+ </para>
+ </step>
+ <step>
+ <para>
+ If you need to, you can resize using <application>The
+ GIMP</application>. With the image open, right-click on it
+ and choose <guimenu>Image</guimenu> -> <guimenuitem>Scale
+ Image...</guimenuitem>. With the chain symbol intact, set the
+ <guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>,
+ and click <guibutton>OK</guibutton>. Be sure to <keycombo>
+ <keycap>Ctrl</keycap> <keycap>s</keycap> </keycombo> to save
+ your changes to your PNG before converting to EPS.
+ </para>
+ </step>
+ <step>
+ <para>
+ With the image open in <application>The GIMP</application>,
+ right-click on the image, selecting <guimenu>File</guimenu>
+ -> <guimenuitem>Save As...</guimenuitem>. Under
+ <guimenu>Determine File Type:</guimenu>, select
+ <guimenuitem>PostScript</guimenuitem>, then click
+ <guibutton>OK</guibutton>. Allow flattening of the image by
+ clicking <guibutton>Export</guibutton>.
+ </para>
+ <para>
+ In the <guilabel>Save as PostScript</guilabel> window, select
+ <guilabel>Encapsulated PostScript</guilabel>, and click
+ <guibutton>OK</guibutton>.
+ </para>
+ </step>
+ </procedure>
+ <para>
+ For more information about calling the images from the XML, refer
+ to <xref linkend="s1-xml-tags-figure"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Text Screenshot</term>
+ <listitem>
+ <para>Textual screen information is also useful for readers. If you
+ use a graphical screenshot to illustrate a function, and the
+ textual mode has identical functions, you should not include
+ both, unless omitting either would make your description
+ unclear. You should make your information generic over specific.
+ Omit the username and machine information, and separate what the
+ user types from sample command output. Also, in
+ <command>screen</command> tags, what the user types should be in
+ <command>userinput</command> tags, and what the user is shown as
+ output should be in <command>computeroutput</command> tags.
+ For example, the usage in
+ <xref linkend="ex-text-screenshot-bad"/> should look like <xref
+d478 5
+a482 7
+ </para>
+ <example id="ex-text-screenshot-bad">
+ <title>Incorrect Textual Screenshot</title>
+ <screen>
+<userinput>ps ax | grep ssh</userinput>
+<computeroutput>
+ 2564 ? S 0:23 /usr/sbin/sshd
+d487 7
+a493 13
+21113 pts/7 S 1:19 ssh rocky@@xxx.private
+</computeroutput>
+ </screen>
+ </example>
+ <example id="ex-text-screenshot-good">
+ <title>Correct Textual Screenshot</title>
+ <para>
+ To find all the currently active ssh sessions, execute the
+ following command:
+ </para>
+<screen>
+<command>ps ax | grep ssh</command>
+</screen>
+d495 1
+a495 3
+ <para>
+ The output will appear similar to:
+ </para>
+d497 1
+a497 3
+ <screen>
+<computeroutput>
+ 2564 ? S 0:23 /usr/sbin/sshd
+d500 20
+a519 15
+ 8032 pts/1 S 0:00 ssh root@@backup.example.com
+</computeroutput>
+ </screen>
+ </example>
+ <para>
+ For more information about using screen, refer to <xref
+ linkend="s1-xml-tags-screen"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect1>
+
+ <sect1 id="s1-diagrams-images">
+ <title>Diagrams and Images</title>
+d521 1
+a521 9
+ <indexterm>
+ <primary>images</primary>
+ </indexterm>
+ <indexterm>
+ <primary>diagrams</primary>
+ <secondary>creating</secondary>
+ </indexterm>
+
+ <para>
+d526 1
+d528 1
+a528 2
+ </chapter>
+
+d530 6
+a535 2
+
+
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d1 1
+a1 1
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+d193 1
+a193 1
+<!-- $Id: docs-rh-guidelines-en.xml,v 1.2 2004/08/31 15:45:29 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-style.xml,v b/old-documentation-guide/en_US/Attic/docs-style.xml,v
new file mode 100644
index 0000000..6ee898e
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-style.xml,v
@@ -0,0 +1,2028 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2006.12.17.00.41.55; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!-- $Id: -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+
+<chapter id="ch-style">
+
+ <title>Style</title>
+
+ <para>
+ Writing good technical documentation is not simply reproducing
+ command lines and instruction sets. Good documentation is easy to
+ read, understand, and translate, and presents a concise logical
+ progression of concepts. Good documentation can also be defined by
+ what it does <emphasis>not</emphasis> contain. Your tutorial should
+ avoid:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Excessive wordiness
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Unnecessary or undefined jargon
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Grammatical or spelling errors
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ References to yourself or your experiences
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Remarks which might offend or confuse any reader
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ This chapter contains style rules and guidelines for writing &FED;
+ documentation. Guidelines are not the same as rules. It is
+ acceptable to violate a guideline when it makes your material easier
+ to understand. Follow guidelines whenever possible, but follow
+ rules at all times. Assume any advice is a guideline unless
+ identified otherwise.
+ </para>
+
+ <section id="sn-intro-to-style">
+
+ <title>Why Style Is Important</title>
+
+ <para>
+ Writing well comes naturally to almost no one. It is a skill that
+ professional writers, even famous ones, must practice constantly.
+ <firstterm>Style</firstterm>
+ <indexterm><primary>style</primary></indexterm> is the quality
+ that separates elegant writing from the merely functional.
+ </para>
+ <para>
+ Elegance comes in many forms. In prose and poetry, elegant
+ writing may not follow some (or any) common rules of grammar,
+ syntax, or spelling. A good example is Episode 18, "Penelope," in
+ James Joyce's novel <citetitle>Ulysses</citetitle><footnote
+ id='fn-ulysses'>
+ <para>
+ For example, refer to. <ulink
+ url="http://www.online-literature.com/james_joyce/ulysses/18/">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>.
+ Please note that this example contains some mature themes and
+ language, and is not suitable for all readers.
+ </para>
+ </footnote>. There, Joyce uses long streams of words without
+ punctuation to simulate a character's internal consciousness. By
+ violating basic rules of grammar and syntax, Joyce simulates the
+ disorganized but loosely connected thought patterns of the
+ narrator.
+ </para>
+ <para>
+ Technical documentation, however, should always respect these
+ rules. The more a document departs from standard language usage,
+ the more difficult the material becomes for the reader. For
+ example, readers may not be native speakers of the language used,
+ or they might be reading a translation. If the writer uses slang,
+ idioms, or jargon, a reader or translator may easily become
+ confused. The following example compares two different written
+ executions of the same idea:
+ </para>
+ <example>
+ <title>Incorrect style</title>
+
+ <!-- I prefer "incorrect," because I think terms such as
+ "problematic" are mealy-mouthed. They remind me of the late
+ 1980's English textbook trend toward the politically correct yet
+ wholly unhelpful "standard/nonstandard." But then, I tend to be
+ dogmatic; it's probably my Catholic upbringing. [PWF] -->
+
+ <para>
+ So you made the changes I showed you in the last section. What's
+ the next thing you should do? Just pop your thumb drive onto
+ your system and read the <filename>messages</filename> log. When
+ you see "USB device found," then Bob's your uncle.
+ </para>
+ </example>
+ <example>
+ <title>Correct style</title>
+
+ <!-- I prefer "correct." See above. [PWF] -->
+
+ <para>
+ After you complete the configuration changes above, attach the
+ USB removable media to your system. Use the
+ <command>dmesg</command> command to examine the kernel message
+ log. The message <computeroutput>USB device
+ found</computeroutput> indicates that your device was
+ installed successfully.
+ </para>
+ </example>
+ <para>
+ The first example is more conversational English, which is not
+ appropriate for official written documentation. The second
+ example is more formal, but as a result it is easier to
+ comprehend, both for native readers and translators.
+ </para>
+ <para>
+ Following style rules and guidelines also makes readers more
+ comfortable with a set of documents. Consistent style enhances
+ the professional appearance of documentation, and its perceived
+ value. On the other hand, lapses in punctuation or poor grammar
+ negatively affect a reader's reaction to written material. A
+ reader can feel that an otherwise correct technical document is
+ lacking in authority, simply because it is poorly written. Readers
+ feel at ease when they do not have to struggle to understand an
+ author's use of language.
+ </para>
+ <para>
+ This chapter cannot possibly cover enough material to make every
+ reader a good writer. Some manuals devoted entirely to writing
+ style are themselves hundreds of pages long. This chapter
+ provides enough guidelines for intermediate writers to understand
+ style usage in technical documentation.
+ </para>
+ <para>
+ If you are not a practiced writer, whether of technical
+ documentation or otherwise, you may benefit from other style
+ resources. The following list is far from comprehensive, but
+ provides a starting point:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <citetitle>The Elements of Style</citetitle>, by William
+ Strunk. Basic rules and links to online versions can be found
+ at: <ulink
+ url="http://en.wikipedia.org/wiki/The_Elements_of_Style">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>
+ </para>
+ </listitem>
+<!-- placeholder for when it's ready
+ <para>
+ <citetitle>The Elements of Style</citetitle>, by William
+ Strunk. Fedora Docs Project version: <ulink
+ url="http://fedora.redhat.com/docs/eos-guide-en/">http://fedora.redhat.com/docs/eos-guide-en/</ulink>
+ </para>
+-->
+ <listitem>
+ <para>
+ <citetitle>The Chicago Manual of Style</citetitle>, by the
+ University of Chicago Press. Online version: <ulink
+ url="http://www.chicagomanualofstyle.org/">http://www.chicagomanualofstyle.org/</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <citetitle>Paradigm Online Writing Assistant</citetitle>,
+ maintained by Chuck Guilford, Ph.D. Online only: <ulink
+ url="http://www.powa.org/">http://www.powa.org/</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ There are many free software documentation projects which have
+ developed their own style guidelines. This chapter, in fact,
+ draws heavily on the <citetitle>GNOME Documentation Style
+ Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may
+ read the original <citetitle>GDSG</citetitle> at <ulink
+ url='http://developer.gnome.org/documents/style-guide/'>http://developer.gnome.org/documents/style-guide/</ulink>.
+ </para>
+
+ </section>
+
+ <section id="sn-tech-docs-fundamentals">
+
+ <title>Fundamental Concepts of Technical Documentation</title>
+
+ <note>
+ <title>Bibliographic Information</title>
+ <para>
+ This section is drawn primarily from the
+ <citetitle>GDSG</citetitle>.
+ </para>
+ </note>
+
+ <!-- This section will reproduce mostly what is in Chapter 1 of
+ the GDSG. There may be minor changes. FIXME: Make sure the
+ appropriate front matter of the Documentation Guide includes
+ attribution as required by the GNU FDL. -->
+
+ <para>
+ This chapter provides a brief introduction to writing technical
+ documentation.
+ </para>
+
+ <section id="sn-fundamentals-1">
+ <title>General Style Requirements</title>
+ <para>
+ Technical writing for the &FP; imposes special constraints
+ beyond the basic requirements of good prose. Good &FED;
+ technical documentation has the following characteristics:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Comprehensive</term>
+ <listitem>
+ <para>
+ Describe all of the functionality of a product. Do not
+ omit functionality that you regard as irrelevant for the
+ user.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Conforming</term> <!-- I'm having issues with the
+ sketchy definition of this non-dictionary word and the
+ associated text. Not wrong, per se, just wishing for
+ something better. This note shall remind us! - kwade -->
+ <!-- Hopefully this change helps. Makes sense according to the
+ gdict tool in Core, at least. - PWF -->
+ <listitem>
+ <para>
+ Describe what you see. Do not describe what you want to
+ see. Present your information in the order that users
+ experience the subject matter.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Clear</term>
+ <listitem>
+ <para>
+ Read <citetitle>The Elements of Style</citetitle> (<ulink
+ url="http://en.wikipedia.org/wiki/The_Elements_of_Style">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>)
+ to help make your writing clear.
+ </para>
+<!-- placeholder for when this is published:
+ <para>
+ Read <citetitle>The Elements of Style</citetitle>
+ &FED;-version (<ulink
+ url="http://fedora.redhat.com/docs/eos-guide-en/">http://fedora.redhat.com/docs/eos-guide-en/</ulink>)
+ to help make your writing clear.
+ </para>
+-->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Consistent</term>
+ <listitem>
+ <para>
+ Use agreed vocabulary throughout your documentation. Use
+ the same vocabulary as other writers who are working on
+ related documentation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Concise</term>
+ <listitem>
+ <para>
+ Review your work frequently as you write your document.
+ Ask yourself which words you can take out. Refer to <xref
+ linkend="sn-fundamentals-2"/> for specific guidelines.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-2">
+ <title>Golden Rules</title>
+ <para>
+ This section contains some basic style guidelines. Subsequent
+ sections in this chapter expand on these guidelines to give more
+ detailed guidance.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Golden Rule 1: Be brief</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Limit each sentence to fewer than 25 words.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each procedure step to 23 words.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-1-wrong">
+ <title>Incorrect: Too long</title>
+ <para> Under normal operating conditions, the kernel does
+ not always immediately write file data to the disks,
+ storing it in a memory buffer and then periodically
+ writing to the disks to speed up operations.
+ </para>
+ </example>
+ <example id="ex-golden-rule-1-right">
+ <title>Correct: Less wordy</title>
+ <para>
+ Normally, the kernel stores the data in memory prior to
+ periodically writing the data to the disk.
+ </para>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Golden Rule 2: Be organized</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Limit each paragraph to one topic.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each sentence to one idea.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each procedure step to one action.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-2-wrong">
+ <title>Incorrect: Disorganized topics</title>
+ <para>
+ The <application>Workspace Switcher</application> applet
+ helps you navigate all of the virtual desktops available
+ on your system. The X Window system, working in hand
+ with a piece of software called a <emphasis>window
+ manager</emphasis>, allows you to create more than one
+ virtual desktop, known as
+ <emphasis>workspaces</emphasis>, to organize your work,
+ with different applications running in each workspace.
+ The <application>Workspace Switcher</application> applet
+ is a navigational tool to get around the various
+ workspaces, providing a miniature road map in the GNOME
+ panel showing all your workspaces and allowing you to
+ switch easily between them.
+ </para>
+ </example>
+ <example id="ex-golden-rule-2-right">
+ <title>Correct: Organized topics</title>
+ <para>
+ Use the <application>Workspace Switcher</application> to
+ add new <emphasis>workspaces</emphasis> to the GNOME
+ Desktop. You can run different applications in each
+ workspace. The <application>Workspace
+ Switcher</application> applet provides a miniature map
+ that shows all of your workspaces. You can use the
+ <application>Workspace Switcher</application> applet to
+ switch between workspaces.
+ </para>
+ </example>
+ <tip>
+ <para>
+ Plan the order of paragraphs before you start writing.
+ Decide which topic you want to cover in each paragraph.
+ </para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Golden Rule 3: Be demonstrative</term>
+ <listitem>
+ <para>
+ Use explicit examples to demonstrate how an application
+ works. Provide instructions rather than descriptions.
+ </para>
+ <example id="ex-golden-rule-3-wrong">
+ <title>Incorrect: Describes but does not
+ demonstrate</title>
+ <para>
+ There is a text box that you can use to find out the
+ definition of a word.
+ </para>
+ </example>
+ <example id="ex-golden-rule-3-right">
+ <title>Correct: Demonstrates usage</title>
+ <para>
+ To request a definition of a word, type the word in the
+ text box, then select <guilabel>Lookup</guilabel>.
+ </para>
+ </example>
+ <tip>
+ <para>
+ Do not apply this guideline too rigidly. Sometimes you
+ must explain how software works to support your how-to
+ examples.
+ </para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-golden-rule-4">
+ <term>Golden Rule 4: Be objective</term>
+ <listitem>
+ <para>
+ Write in a neutral tone.
+ </para>
+ <example id="ex-golden-rule-4-wrong">
+ <title>Incorrect: Sentence takes sides</title>
+ <para>
+ The applet is a handy little screen grabber.
+ </para>
+ </example>
+ <example id="ex-golden-rule-4-right">
+ <title>Correct: Sentence is objective</title>
+ <para>
+ Use the applet to take screenshots.
+ </para>
+ </example>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="sn-fundamentals-3">
+
+ <title>Tone</title>
+ <para>
+ Inappropriate tone hinders reader access to information. A
+ neutral tone free of opinion or personal flavor improves the
+ reader's comprehension. Neutral tone helps writers to work in
+ parallel on a large technical documentation project.
+ Furthermore, additional writers may join the project at any
+ time. Use of a neutral tone helps to achieve consistency across
+ a documentation set, and thereby facilitates user access to
+ information. The best way to achieve a common, neutral tone is
+ to apply the following principles:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Avoid humor</term>
+ <listitem>
+ <para>
+ Humor distracts from the information you are trying to
+ provide. Humor also makes documentation difficult to
+ translate. Stay factual.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid personal opinions</term>
+ <listitem>
+ <para>
+ Whether you think a function is useful or woeful is
+ irrelevant. Report the function to the user, with
+ instructions about how to use the function. Stay
+ accurate.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid colloquial language</term>
+ <listitem>
+ <para>
+ Colloquial language is difficult to translate and usually
+ culture-specific. Stay neutral.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid topical expressions</term>
+ <listitem>
+ <para>
+ An expression that is in common use today might convey
+ something completely different tomorrow. Stay technical.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid aspirational statements</term>
+ <listitem>
+ <para>
+ Statements about the future developments of a product do
+ not belong in technical documentation. Write about what
+ you see right now. Stay real.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-4">
+ <title>Reaching the Right Audience</title>
+ <para>
+ All of the decisions that you make about the structure and
+ content of a manual follow from an understanding of the
+ audience. Consider how the audience accesses the documentation,
+ what sort of information the audience needs, and the experience
+ level of the audience. Usually, you need to create
+ documentation that is suitable for different audiences. The
+ following sections introduce some of the audience-related topics
+ you need to consider.
+ </para>
+ </section>
+ <section id="sn-fundamentals-6">
+ <title>User Motivation</title>
+ <para>
+ Do not waste the time of the user who looks for information in
+ your documentation. Users do not read technical documentation
+ for entertainment. Users usually have specific questions. You
+ need to give clear answers to those questions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-7">
+ <title>New Users</title>
+ <para>
+ New users to &FC; are likely to consult online tutorials for
+ guidance about unfamiliar applications or functionality. Each
+ tutorial should contain enough introductory information to tell
+ new users how to start using the relevant functions. Each
+ tutorial should also contain enough usage instructions to tell
+ users the different actions that they can perform with the
+ command or function. Keep these instructions task-oriented. Do
+ not describe GUI screens, dialogs, and dialog elements in a
+ tutorial, unless there is an unusual feature that affects your
+ instructions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-8">
+ <title>Experienced Users</title>
+ <para>
+ Experienced users are more likely to use documentation as a
+ reference. The documentation therefore needs to be complete,
+ well-organized, and in the case of printed manuals,
+ well-indexed.
+ </para>
+ </section>
+ <section id="sn-fundamentals-9">
+ <title>Do Not Offend Your Audience</title>
+ <para>
+ To avoid offending your readers, apply the following guidelines
+ to your documentation:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Avoid insider language</term>
+ <listitem>
+ <para>
+ Insider language includes both undefined jargon and the
+ tendency of the computer community to shorten words. For
+ example, use the term <literal>documentation</literal>
+ instead of the term <literal>docs</literal>. A term may
+ be jargon if it fails all the following conditions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The term does not appear in the <citetitle>&FED;
+ Jargon Buster</citetitle> (<ulink
+ url="http://fedora.redhat.com/docs/jargon-buster/">http://fedora.redhat.com/docs/jargon-buster/</ulink>).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The term does not appear in the <citetitle>American
+ Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/
+ </ulink>).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The term does not appear in the glossary of the manual
+ that you are writing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The term is not defined in the body text of the manual
+ that you are writing.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid gender-specific language</term>
+ <listitem>
+ <para>
+ Pronoun constructions such as <literal>his/her</literal>
+ or <literal>s/he</literal> do not exist. There is no need
+ to identify gender in your instructions.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid culture-specific language</term>
+ <listitem>
+ <para>
+ There is little point in giving an example that everyone
+ in your town knows about, but is a complete mystery to
+ everyone else in the world.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid talking down to your reader</term>
+ <listitem>
+ <para>
+ There are few experiences more irritating for a user than
+ documentation that says an action is easy or quick, when
+ in fact the user cannot complete the action. Do not
+ qualify or prejudge actions.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Other parts of this guide discuss in more detail tone and
+ language usage that can cause offense.
+ </para>
+
+ </section>
+
+ </section>
+
+ <section id="sn-grammar-and-usage">
+
+ <title>Grammar and Usage Guidelines</title>
+
+ <note>
+ <title>Bibliographical Information</title>
+ <para>
+ This section is drawn partly from the
+ <citetitle>GDSG</citetitle>, and partly from <citetitle>The
+ Elements of Style</citetitle>, updated as necessary for the
+ needs of 21st-century technical documentation writers.
+ </para>
+ </note>
+
+ <!-- FIXME: Again, check attribution viz. GNU FDL. This will be more work
+ than the previous section. -->
+
+ <para>
+ This section contains an alphabetical list of grammar and usage
+ guidelines for use in &FED; documentation. Many of these
+ guidelines are only applicable to English-language usage, refer to
+ the <citetitle>American Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ and the <citetitle>Chicago Manual of Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Abbreviations</term>
+ <listitem>
+ <para>
+ A shortened form of a word or phrase that takes the place of
+ the full word or phrase, such as <literal>Dr.</literal>,
+ <literal>a.m.</literal>, <literal>p.m.</literal>, and so on.
+ Apply the following rules when you use abbreviations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Avoid creating new abbreviations. Unfamiliar
+ abbreviations can confuse rather than clarify a concept.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not explain or expand familiar abbreviations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not include familiar abbreviations in the glossary of
+ your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ For abbreviations of phrases, such as
+ <literal>i.e.</literal> for "in other words" and
+ <literal>e.g.</literal> for "for example", do not use the
+ abbreviation. Spell out the entire phrase.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adjectives</term>
+ <listitem>
+ <para>
+ Use adjectives with caution. If an adjective is necessary
+ to differentiate between items, then use adjectives. In all
+ cases, test whether the phrase can stand alone without the
+ adjective.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Acronyms</term>
+ <listitem>
+ <para>
+ A term that represents a multi-word term. Typically,
+ acronyms are formed in the following ways:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ From the first letters of each word in a compound term,
+ for example Table of Contents (TOC).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ From recognizable parts of a compound term, such as GNU
+ Object Model Environment (GNOME).
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Apply the following rules when you use acronyms:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ On the first occurrence of an acronym, spell out the
+ full term, with the acronym in parentheses.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not spell out the full compound for well-known
+ acronyms, unless you think the information is useful for
+ readers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Avoid creating new acronyms. Unfamiliar acronyms can
+ confuse rather than clarify a concept.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Write the acronym in uppercase letters, unless there is
+ a compelling case for lowercase.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Include the acronym and the full term in the glossary of
+ your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adverbs</term>
+ <listitem>
+ <para>
+ Use adverbs with caution. If an adverb is necessary to
+ qualify the function of a component, then use an adverb. In
+ all cases, test whether the phrase can stand alone without
+ the adverb. Classic superfluous adverbs
+ <literal>simply</literal>, <literal>easily</literal>,
+ <literal>quickly</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Anthropomorphism</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not apply emotions, desires, or opinions to software
+ applications.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not apply a sense of location or dimension to a
+ software application. A user can not be "in" a text
+ editor.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Articles</term>
+ <listitem>
+ <para>
+ Do not use the definite article <literal>the</literal> to
+ begin any of the following items:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Manual titles
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter titles
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Headings
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Figure captions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Table captions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Callouts
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Apostrophe</term>
+ <listitem>
+ <para>
+ Do not use apostrophes except where absolutely required
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote possession.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote contractions.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote plurals.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-apostrophe-wrong">
+ <title>Incorrect: Apostrophes</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <guimenu>Main Menu's</guimenu>
+ <guimenuitem>Help</guimenuitem> option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ don't use the default option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ several SCSI disk's
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-apostrophe-right">
+ <title>Correct: No apostrophes</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <guimenuitem>Help</guimenuitem> option on the
+ <guimenu>Main Menu</guimenu>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ do not use the default option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ several SCSI disks
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Brackets</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not use brackets [such as these] as a substitute for
+ parentheses (such as these).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use brackets for optional command line entries.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use angle brackets to indicate variables in text,
+ instead use the <sgmltag
+ class="starttag">replaceable</sgmltag> tag. Refer to
+ <xref linkend="s1-xml-tags-replaceable"/> for
+ information about using this tag.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Capitalization</term>
+ <listitem>
+ <para>
+ Capitalize in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ All letters in acronyms, unless the acronym is a
+ well-known exception
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of the first word in a list
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of the first word in a callout
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a key name, such as the
+ <keycap>Shift</keycap> key
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a sentence
+ </para>
+ <note>
+ <title>Command Names</title>
+ <para>
+ Avoid starting a sentence with a command name or
+ application name that has a lowercase initial letter.
+ </para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a complete sentence after a colon
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not capitalize in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ A compound term that is followed by an abbreviation or
+ an acronym
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When you want to emphasize something
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Variable names
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The initial letter of an incomplete sentence after a
+ colon
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Captions</term>
+ <listitem>
+ <para>
+ Use the same rules as for headings, for all captions
+ accompanying figures and tables. Do not put a period at the
+ end of a caption.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Colon</term>
+ <listitem>
+ <para>
+ Use a colon in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To introduce a list
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Before an explanation
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ After an introduction
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use a colon in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To introduce a figure or a table
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To introduce headings
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ At the end of an introduction to a procedure
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Column headings</term>
+ <listitem>
+ <para>
+ Use the same rules as for headings.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Comma</term>
+ <listitem>
+ <para>
+ Use commas in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To separate items in a series
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To separate the parts of a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To separate nonrestrictive phrases
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Instead of dashes to set off appositives
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With <emphasis>for example</emphasis> and similar
+ expressions
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use commas in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ In a series of adjectives used as one modifier
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Between two short independent clauses
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Commands</term>
+ <listitem>
+ <para>
+ Do not use commands as verbs.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-contractions">
+ <term>Contractions</term>
+ <listitem>
+ <para>
+ Do not use contractions such as <emphasis>can't</emphasis>,
+ <emphasis>don't</emphasis>, or <emphasis>isn't</emphasis>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Dash</term>
+ <listitem>
+ <para>
+ Do not use the em dash or the en dash. Use a paragraph
+ break or a colon instead, where you want to create an
+ introductory piece of text. If you have several items that
+ you want to introduce, then you can use a variable list.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Ellipsis</term>
+ <listitem>
+ <para>
+ Use an ellipsis in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To show that you have omitted something from a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To indicate a pause when you quote displayed text
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Fractions</term>
+ <listitem>
+ <para>
+ Follow these rules when using fractions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use numerals for fractions in tables and in units of
+ measurement, but spell out fractions in prose.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use a space between a numeral and a related fraction, if
+ there is a possible ambiguity. For example: 1 1/2
+ instead of 11/2.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If a fraction is used in a compound modifier, insert a
+ hyphen between the fraction and the unit of measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Gender</term>
+ <listitem>
+ <para>
+ Refer to <xref linkend="sn-fundamentals-9"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Grammar</term>
+ <listitem>
+ <para>
+ Use standard American English grammar rules, refer to the
+ <citetitle>Chicago Manual of Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">
+ http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Headings</term>
+ <listitem>
+ <para>
+ Use the following capitalization rules in headings:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Initial uppercase letter of the first word
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for all nouns, adjectives, and
+ verbs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All lowercase letters for conjunctions, articles, and
+ prepositions of fewer than four letters
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for prepositions of four
+ letters or longer
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for conjunctions of four
+ letters or longer
+ </para>
+ </listitem>
+ </itemizedlist>
+ <!-- <para> See <xref linkend="infodesign-2"/> for more
+ information about headings. </para> -->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Hyphen</term>
+ <listitem>
+ <para>
+ Use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para> With a numeral in a compound modifier
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To prevent ambiguity
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With some standard prefixes and suffixes. Use the
+ <citetitle>American Heritage Dictionary</citetitle>
+ (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ for guidance
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In spelled-out fractions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In variable names of two or more words, such as
+ <replaceable>directory-name</replaceable>. Note:
+ <replaceable>filename</replaceable> is an exception.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ For industry-accepted terms
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To construct verbs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With an adverb ending in <emphasis>ly</emphasis>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With numerals as single modifiers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With a word that is listed as unhyphenated in the
+ <citetitle>American Heritage Dictionary</citetitle>
+ (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>),
+ and that uses a common prefix
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With trademarked terms
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Latin terms</term>
+ <listitem>
+ <para>
+ Do not use Latin terms. Use an equivalent English term
+ instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Like</term>
+ <listitem>
+ <para>
+ Do not use the term <emphasis>like</emphasis> to denote
+ equivalence or similarity.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Lists</term>
+ <listitem>
+ <para>
+ Introduce a list with a complete sentence that ends with a
+ colon.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numbers</term>
+ <listitem>
+ <para>
+ Spell out numbers in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para> Numbers from zero through nine unless the number is
+ part of a measurement
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Approximations
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Extreme values such as <emphasis>million</emphasis>, but
+ precede the value with a numeral
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Any number that begins a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A number that is immediately followed by a numeral, for
+ example: <literal>two 10 MB files</literal>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numerals</term>
+ <listitem>
+ <para>
+ Use numerals in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The number 10 or greater
+ </para>
+ </listitem>
+ <listitem>
+ <para> Negative numbers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Most fractions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Percentages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Decimals
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Measurements
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Units of time smaller than one second
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ References to bits and bytes
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Parentheses</term>
+ <listitem>
+ <para>
+ Use parentheses in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To contain the abbreviation of a term on the first
+ occurrence of the full term
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In man page references, specifically the section number
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Period</term>
+ <listitem>
+ <para>
+ Use a period in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To end a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In file and directory names
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In abbreviations that can be mistaken for words, such as
+ a.m. and U.S.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation</term>
+ <listitem>
+ <para>
+ Use standard American English punctuation rules. In
+ addition to the specific points of punctuation in this
+ section, refer also to the <citetitle>Chicago Manual of
+ Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation in numbers</term>
+ <listitem>
+ <para>
+ Do not use a comma in numerals of four digits. Use a comma
+ in numerals of more than four digits.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Quotation marks</term>
+ <listitem>
+ <para>
+ Use quotation marks to indicate material that is taken
+ verbatim from another source. Do not use quotation marks to
+ excuse terms from legitimacy. If the term is not
+ legitimate, then use another term. If you must use that
+ term, declare the term in the glossary and make the term
+ legitimate.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>See v. Refer to</term>
+ <listitem>
+ <para>
+ When referring a user to another resource, use "refer to"
+ instead of "see", and "refer also to" instead of "see also".
+ This differentiates from the <sgmltag
+ class="starttag">see</sgmltag> and <sgmltag
+ class="starttag">seealso</sgmltag> tags that are used in
+ indexing. These tags create special links in the index. To
+ be consistent throughout the document, we reserve the
+ special words "see" and "see also" for hyperlinked index
+ references, and use "refer to" and "refer also to" for
+ non-hyperlinked and non-indexed references.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Semicolon</term>
+ <listitem>
+ <para>
+ Do not use semicolons.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Slash</term>
+ <listitem>
+ <para>
+ Except where required as part of a filename, do not use
+ slashes "/" in your writing. The construction
+ <literal>and/or</literal>, for example, does not exist. Use
+ one or the other term instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Spelling</term>
+ <listitem>
+ <para>
+ Use standard American English spelling rules, refer to the
+ <citetitle>American Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ for guidelines.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Titles</term>
+ <listitem>
+ <para>
+ For manual titles use the same rules as for headings.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Units</term>
+ <listitem>
+ <para>
+ Follow these rules when using units:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use standard abbreviations for units of measurements, do
+ not invent your own abbreviations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!-- See <xref linkend="units"/> for a list of units
+ relevant to the GNOME Desktop. --> For further
+ guidelines, refer to the <citetitle>IEEE Standard
+ Dictionary of Electrical and Electronics
+ Terms</citetitle>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use periods for abbreviated units that might be mistaken
+ for a word.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Most standard abbreviations of units account for both
+ singular and plural usage.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Insert a space between the numeral and the unit of
+ measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="sn-composition-tips">
+
+ <title>Composition Tips</title>
+
+<!--
+
+ This section will collect miscellanea and advice for specific
+ situations that the FDP editors encounter. I hope they will feel
+ free to e-mail me sticky situations or particularly interesting
+ examples of work they've beautified. Hopefully not too much will be
+ drawn from my own work! - PWF.
+
+-->
+
+ <para>
+ This section contains usage tips based on situations the &FDP;
+ editors have encountered in the past. You should read and
+ understand these examples to improve your own documentation. The
+ &FDP; editors welcome additional examples.
+ </para>
+
+ <section id="sn-misc-active-voice">
+ <title>Active Voice</title>
+ <para>
+ Always use active voice, except when it is awkward to do so. The
+ tutorial tells the user how to accomplish a task, and should
+ give instructions clearly and concisely. Avoid using "must,"
+ "need to," and the like. These words are redundant in a
+ tutorial, since the reader assumes you are outlining necessary
+ steps to accomplish a task. Also avoid using "maybe," "might,"
+ and other words that indicate you are unsure about the subject
+ matter. Your tutorial should cover a subject authoritatively.
+ The reader should never be concerned about unknown effects of
+ following the tutorial.
+ </para>
+ <example id="ex-misc-passive-voice">
+ <title>Incorrect: Passive voice</title>
+ <para>
+ The <command>yum update</command> command must be run.
+ </para>
+ <para>
+ You might want to run the <command>yum update</command>
+ command.
+ </para>
+ </example>
+ <example id="ex-misc-active-voice">
+ <title>Correct: Active voice</title>
+ <para>
+ Run the <command>yum update</command> command.
+ </para>
+ </example>
+ </section>
+
+ <section id="sn-present-tense">
+ <title>Present Tense</title>
+ <para>
+ Write in the present tense. A good rule of thumb is that the
+ words "will" and "shall" are almost never needed in describing
+ what the user should do or see. They add unnecessary length to
+ sentences and can confuse translators. They are also often
+ indicators of passive voice; refer also to <xref
+ linkend="sn-misc-active-voice"/>.
+ </para>
+ <example id="ex-misc-future-tense">
+ <title>Incorrect: Future tense</title>
+ <para>
+ The application will display a list of target files.
+ </para>
+ <para>
+ A list of target files will be displayed by the application.
+ </para>
+ </example>
+ <example id="ex-misc-present-tense">
+ <title>Correct: Present tense</title>
+ <para>
+ The application displays a list of target files.
+ </para>
+ </example>
+ </section>
+
+ <section id="sn-narrative-voice">
+ <title>Narrative Voice</title>
+ <para>
+ Do not use the first person "I," "we," or "us" to refer to
+ yourself the writer (whether including the reader or not), the
+ &FDP;, the &FED; community, or any other group. Do not refer to
+ users with a third person pronoun ("he," "she," or "he or she")
+ or the word "one." It is acceptable to refer to the reader with
+ the second person pronoun "you."
+ </para>
+ <example id="ex-misc-wrong-person">
+ <title>Incorrect: First or third person</title>
+ <para>
+ As described in the last section, I always run
+ <command>up2date</command> before configuring the Samba
+ server.
+ </para>
+ <para>
+ If the user needs to back up his or her files, s/he should use
+ the <command>tar</command> or <command>cpio</command> command.
+ </para>
+ </example>
+ <example id="ex-misc-correct-person">
+ <title>Correct: Second (or no) person</title>
+ <para>
+ Refer to the section on <command>up2date</command> before
+ configuring the Samba server.
+ </para>
+ <para>
+ If necessary, users can back up files with the
+ <command>tar</command> or <command>cpio</command> command.
+ </para>
+ </example>
+ </section>
+
+ <section id="sn-misc-negative">
+ <title>Negative Words</title>
+ <para>
+ Avoid negative words when possible, since they give
+ documentation an overly dogmatic tone. The word "avoid" is
+ useful for this purpose. Note that contractions are often used
+ for negative words such as <emphasis>don't</emphasis> or
+ <emphasis>can't</emphasis>. Refer to <xref
+ linkend="vle-contractions" />.
+ </para>
+ </section>
+
+ <section id="sn-misc-uncertainty">
+ <title>Uncertainty</title>
+ <para>
+ Avoid overuse of "typically," "usually," "most of," "many," and
+ the like. While occasional use of these constructions is
+ acceptable, overuse reduces the authority of your documentation.
+ The documentation should adequately cover a stock installation
+ of &FC;. It is impossible for a tutorial-length document to
+ cover every possible configuration scenario. Address the most
+ common scenarios and note discrepancies only as required.
+ </para>
+ </section>
+
+ <section id="sn-misc-offtopic">
+ <title>Redundant Coverage</title>
+ <para>
+ Avoid covering redundant material, such as how to update a &FC;
+ system. These overarching topics may be covered in other
+ tutorials. Writers frequently violate this guideline because
+ they feel their tutorial is not long enough. Keep your tutorial
+ from wandering off-topic. Instead, refer the reader to a
+ separate tutorial whenever possible for complete coverage of
+ that topic.
+ </para>
+ </section>
+
+ <section id="sn-misc-importance">
+ <title>Self-referential Value Judgments</title>
+ <para>
+ Avoid statements such as "One of the most important things to do
+ is <replaceable>XYZ</replaceable>." If the procedure is
+ important, the reader already expects it to be in your tutorial.
+ The converse is also true: If a procedure appears in your
+ tutorial, the reader expects it is important. This is
+ especially true if you use a whole section for the procedure in
+ question. Merely state, "Do <replaceable>XYZ</replaceable>."
+ Then elaborate as required. If the whole section concerns how
+ to do <replaceable>XYZ</replaceable>, leave this sentence out
+ entirely. Refer also to <xref linkend="vle-golden-rule-4" />.
+ </para>
+ </section>
+
+ <section id="sn-misc-precision">
+ <title>Precision of Language</title>
+ <para>
+ Use precise words for actions users should take. Do not
+ instruct users to "go" to a selection, or "find" a menu.
+ </para>
+ <example id="ex-precision-wrong">
+ <title>Incorrect: Imprecise wording</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Go to the <guimenu>Main Menu</guimenu> ->
+ <guimenuitem>Foobar</guimenuitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Find the option labeled <guilabel>Search</guilabel>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-precision-right">
+ <title>Correct: Precise wording</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ From the <guimenu>Main Menu</guimenu>, select
+ <guimenuitem>Foobar</guimenuitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select the <guilabel>Search</guilabel> option
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <important>
+ <title>Do Not Discriminate Against Non-GUI Users</title>
+ <para>
+ If you are writing about a GUI-only application, you may use
+ "click" freely. If you are writing about an application that
+ has a text-mode interface, use "select" instead as shown
+ above.
+ </para>
+ </important>
+
+ </section>
+
+ <section id="sn-misc-docbook-tips">
+ <title>DocBook Tips</title>
+ <para>
+ This section contains tips on how to use DocBook tags more
+ effectively in your documentation.
+ </para>
+
+ <section id="sn-misc-admonitions">
+ <title>Admonitions</title>
+ <para>
+ Avoid overuse of admonitions. Keep admonitions short and
+ effective by using only the most important material inside the
+ admonition. Move any background material required to explain
+ the admonition statements outside the admonition. Use a short
+ but descriptive title for an admonition. Use title case for
+ the admonition title.
+ </para>
+ <example id="ex-misc-ineffective-admonition">
+ <title>Incorrect: Lengthy admonition</title>
+ <para>
+ <warning>
+ <title>Use <command>sfdisk</command> to check input</title>
+ <para>
+ The <command>sfdisk</command> command accepts a script
+ file as standard input to set up partitions on a hard
+ disk. Sometimes <command>sfdisk</command> will simply
+ reject an erroneous input file. In other cases, it will
+ use the input verbatim, writing an incorrect partition
+ table to your disk. Always use the <command>sfdisk
+ -n</command> command to check your input file before
+ writing to the disk.
+ </para>
+ </warning>
+ </para>
+ </example>
+ <example id="ex-misc-good-admonition">
+ <title>Correct: Brief admonition</title>
+ <para>
+ The <command>sfdisk</command> command accepts a script
+ file as standard input to set up partitions on a hard disk.
+ Sometimes <command>sfdisk</command> will simply reject an
+ erroneous input file. In other cases, it will use the input
+ verbatim, writing an incorrect partition table to your disk.
+ <warning>
+ <title>Check Input</title>
+ <para>
+ Always use the <command>sfdisk -n</command> command to
+ check your input file before writing to the disk.
+ </para>
+ </warning>
+ </para>
+ </example>
+ <para>
+ Avoid punctuation in titles for sections or admonitions,
+ except for commas only where demanded. Use a title that says
+ something about the admonition comment, such as "Reboot
+ Required," instead of simply using the admonition type for a
+ title ("Note").
+ </para>
+ <para>
+ Follow the capitalization rules for headings in the title of
+ an admonition.
+ </para>
+ </section>
+
+ <section id="sn-misc-replaceable">
+ <title>The <sgmltag class="starttag">replaceable</sgmltag>
+ Tag</title>
+ <para>
+ If your documentation formally states a specific value will be
+ used as a convention, do not use the <sgmltag
+ class="starttag">replaceable</sgmltag> tag in your text or
+ examples.
+ </para>
+ </section>
+
+ <section id="sn-misc-entities">
+ <title>XML Entities</title>
+ <para>
+ Use the entities provided by the &FDP;. These entities are
+ found in the <filename>common/</filename> folder in the
+ <filename>fedora-docs</filename> distribution. (Refer also to
+ <xref linkend="ch-getting-files"/>.) For instance, do not use
+ abbreviations such as "FC2." Instead, use the predefined
+ entities "&FC; &FCVER;," which produces the text "&FC;
+ &FCVER;."
+ </para>
+ </section>
+
+ </section>
+
+ </section>
+
+</chapter>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.2
+log
+ at Ha, I know a lot more about why this book caused me so much pain when I first started learning DocBook and XML. Take that, crummy DOCTYPEs\!
+@
+text
+@@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d2 1
+a2 1
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+a1970 1
+sgml-parent-document:("documentation-guide-en.xml" "book" "chapter")
+@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-tutorial.xml,v b/old-documentation-guide/en_US/Attic/docs-tutorial.xml,v
new file mode 100644
index 0000000..320f79a
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-tutorial.xml,v
@@ -0,0 +1,165 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2006.12.17.00.41.55; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!-- $Id: docs-tutorial.xml,v 1.2 2006/12/17 00:41:55 pfrields Exp $ -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+ <chapter id="ch-tutorial">
+ <title>The Layout of a Tutorial</title>
+
+ <para>
+ In this chapter, you will find an example of a &PROJECT; documentation
+ parent file. This example is specific to the way the Docs Project uses
+ DocBook XML. The parent file contains the main structural format of the
+ book, a link to the entities file that contain common entities that should
+ be used, and an entity to change the version and date of the tutorial.
+ </para>
+
+ <sect1 id="s1-tutorial-parent">
+ <title>The Parent File</title>
+
+ <para>
+ Below is a sample parent file:
+ </para>
+
+<screen>
+<computeroutput>
+<!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 "../common/fedora-entities-en.xml">
+%FEDORA-ENTITIES-EN;
+
+<!ENTITY VERSION "0.1"> <!-- change version of tutorial here -->
+
+<!ENTITY DOCID "example-tutorial-&VERSION; (2003-07-07)"> <!-- change last modified date here -->
+
+<!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice-en.xml">
+
+
+]>
+
+<article id="example-tutorial" lang="en">
+ <articleinfo>
+ <title>Example Tutorial</title>
+ <copyright>
+ <year>2003</year>
+ <holder>&FORMAL-RHI;</holder>
+ <holder>Tammy Fox</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ </authorgroup>
+ &LEGALNOTICE;
+ </articleinfo>
+
+ <section id="some-section">
+ <title>Some Section</title>
+
+ <para>
+ This is an example section. You can also use sect1, sect2, etc.
+ </para>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ Example of an admonition.
+ </para>
+ </warning>
+
+ </section>
+
+<index id="generated-index"></index>
+</article>
+</computeroutput>
+</screen>
+
+ </sect1>
+
+ <sect1 id="s1-tutorial-license">
+ <title>Including the License Information</title>
+
+ <indexterm>
+ <primary>tutorial layout</primary>
+ <secondary>license</secondary>
+ </indexterm>
+
+ <para>
+ All &PROJECT; manuals <emphasis>must</emphasis> contain the file
+ <filename>legalnotice.xml</filename>. This file makes the license for
+ the file the GNU Free Documentation License (FDL).
+ </para>
+
+ <para>
+ The sample parent file shows how it is included.
+ </para>
+
+ </sect1>
+
+ </chapter>
+
+
+@
+
+
+1.2
+log
+ at Ha, I know a lot more about why this book caused me so much pain when I first started learning DocBook and XML. Take that, crummy DOCTYPEs\!
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial.xml,v 1.1 2006/11/23 02:24:17 pfrields Exp $ -->
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d1 2
+a2 2
+<!-- $Id: docs-tutorial-en.xml,v 1.8 2005/12/28 00:40:27 pfrields Exp $ -->
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-vim.xml,v b/old-documentation-guide/en_US/Attic/docs-vim.xml,v
new file mode 100644
index 0000000..62c077e
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-vim.xml,v
@@ -0,0 +1,213 @@
+head 1.3;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.2;
+
+1.2
+date 2006.12.17.00.41.55; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!-- $Id: docs-vim.xml,v 1.2 2006/12/17 00:41:55 pfrields Exp $ -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+
+ <chapter id="ch-vim">
+ <title>VIM and DocBook</title>
+
+ <indexterm>
+ <primary>VIM</primary>
+ </indexterm>
+
+ <para>
+ VIM has many features to help you write XML content such as DocBook,
+ including syntax highlighting and customizable key bindings.
+ Additionally, one can easily use external programs from VIM for features
+ such as spell-checking.
+ This chapter assumes you already know generally how to use VIM; if you
+ want to learn how, try the <command>vimtutor</command> or by typing
+ <userinput>:help tutor</userinput> from inside VIM.
+ </para>
+
+ <sect1 id="s1-vimrc-file">
+ <title>Setting Up Your <filename>.vimrc</filename> File</title>
+
+ <indexterm>
+ <primary>VIM</primary>
+ <secondary>configuration file</secondary>
+ </indexterm>
+
+ <para>
+ Below is a short sample <filename>.vimrc</filename> file that turns on
+ some VIM features useful for editing SGML or XML content such as
+ DocBook:
+<screen>
+<computeroutput>" Turn off vi compatibility settings like limited undo
+set nocompatible
+" Syntax highlighting based on file extension
+syntax on
+" Automatically insert newlines after 80 characters
+set textwidth=80
+" Automatically indent
+set autoindent
+" Match SGML tags with %
+source $VIMRUNTIME/macros/matchit.vim</computeroutput>
+</screen>
+ </para>
+ <note>
+ <para>
+ Some of these features require the <filename>vim-enhanced</filename>
+ package to be installed. If you are using or the
+ <filename>vim-minimal</filename> package, or if you are using an older
+ version of VIM, you may not have the
+ <filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still
+ download <ulink
+ url="http://vim.org/scripts/script.php?script_id=39">matchit.zip from
+ Vim.org</ulink> and load it separately.
+ </para>
+ </note>
+ </sect1>
+
+ <sect1 id="s1-vim-keymapping">
+ <title>Keymapping with VIM</title>
+
+ <para>
+ VIM can speed up your DocBook creation by mapping frequently typed tags
+ (or any words or phrases) onto short key combinations. By default, the
+ keymap leader is the backslash (<literal>\</literal>), but it can be
+ redefined with a command like <userinput>let mapleader =
+ ","</userinput>. There are two ways to use the following example;
+ you can put it directly in your <filename>.vimrc</filename>, or you
+ can save it in a separate file and load it with a
+ <userinput>source</userinput> command in your
+ <filename>.vimrc</filename>.
+<screen>
+<![CDATA[let mapleader = ","
+
+" skip ahead to after next tag without leaving insert mode
+imap <leader>e <esc>/><cr>:nohlsearch<cr>a
+
+" common tags that start a new text block
+imap<leader>pa <para><cr></para><esc>O
+imap<leader>s1 <sect1 id=""><cr><para><esc>jo</sect1><esc>O
+imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i
+imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i
+
+" common tags that are placed inline
+" use <esc>F>a
+imap<leader>en <envar></envar><esc>F>a
+imap<leader>fi <filename></filename><esc>F>a
+imap<leader>lt <literal></literal><esc>F>a
+imap<leader>re <replaceable></replaceable><esc>F>a
+imap<leader>ui <userinput></userinput><esc>F>a
+imap<leader>ul <ulink url=""></ulink><esc>F>a
+imap<leader>si <systemitem></systemitem><esc>F>a
+imap<leader>us <systemitem class="username"></systemitem><esc>F>a
+imap<leader>sy <systemitem class="systemname"></systemitem><esc>F>a
+imap<leader>cm <command></command><esc>F>a
+" entities
+imap <leader>> >
+imap <leader>< <]]>
+</screen>
+ </para>
+ <para>
+ Unfortunately, there is not currently a complete macro set for all
+ DocBook commands, so you will need to define them yourself or customize
+ the definitions in the examples from <xref
+ linkend="s1-vim-additional-resources"></xref>.
+ </para>
+ </sect1>
+
+ <sect1 id="s1-vim-additional-resources">
+ <title>Additional VIM Resources</title>
+
+ <para>
+ Additional information about VIM may be found from:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink url=
+ "http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC">
+ Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to
+ Vi Improved (VIM)</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para>The <ulink url="http://tnerual.eriogerg.free.fr/vim.html">VIM
+ Quick Reference Card</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://www.pinkjuice.com/howto/vimxml/">Vim as XML
+ Editor</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with
+ the <filename>vim-common</filename> package —
+ <filename>/usr/share/vim/<replaceable><version></replaceable>/doc/intro.txt</filename>
+ or type <userinput>:help intro</userinput> from within VIM
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect1>
+ </chapter>
+@
+
+
+1.2
+log
+ at Ha, I know a lot more about why this book caused me so much pain when I first started learning DocBook and XML. Take that, crummy DOCTYPEs\!
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-vim.xml,v 1.1 2006/11/23 02:24:17 pfrields Exp $ -->
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d1 2
+a2 2
+<!-- $Id: docs-vim-en.xml,v 1.2 2005/12/23 22:57:30 pfrields Exp $ -->
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+@
+
diff --git a/old-documentation-guide/en_US/Attic/docs-xml-tags.xml,v b/old-documentation-guide/en_US/Attic/docs-xml-tags.xml,v
new file mode 100644
index 0000000..8d8798f
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/docs-xml-tags.xml,v
@@ -0,0 +1,2610 @@
+head 1.4;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.4
+date 2007.02.03.22.21.58; author kwade; state dead;
+branches;
+next 1.3;
+
+1.3
+date 2006.12.23.23.49.59; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2006.12.17.00.41.55; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.4
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@<!-- $Id: docs-xml-tags.xml,v 1.3 2006/12/23 23:49:59 pfrields Exp $ -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+
+ <chapter id="ch-xml-tags">
+ <title>DocBook XML Tags</title>
+
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>tags</secondary>
+ <see>XML tags</see>
+ </indexterm>
+
+ <para>Please read this chapter carefully. This chapter describes the tags
+ used by the Docs Project. Some of the rules described are specific to the
+ project.
+ </para>
+
+ <para>If these tags are used appropriately, document searches will provide
+ meaningful results. These tags help search engines identify the
+ information relevant to the search request. Another benefit is that all
+ &PROJECT; documents will have a similar look and feel (however, they will have
+ some differences depending upon the output format).
+ </para>
+
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>general tag information</secondary>
+ </indexterm>
+
+ <para>Most tags in XML must have an opening and closing tag. A few
+ tags, such as <sgmltag class="emptytag">xref</sgmltag>, have no
+ content and close themselves. Additionally,
+ proper XML conventions say that there must be a unique identifier for
+ sections, chapters, figures, tables, and so on, so that they may be
+ correctly identified, and cross referenced if needed.</para>
+
+ <para>Although XML is capable of handling many document types, the format
+ discussed here is the article format.</para>
+
+ <para>
+ This chapter only discusses tags used for documentation for the &PROJECT;,
+ not all available DocBook XML tags. For the complete list, refer to:
+ </para>
+<screen>
+<computeroutput>
+<ulink url="http://www.docbook.org/tdg/en/html/docbook.html">http://www.docbook.org/tdg/en/html/docbook.html</ulink>
+</computeroutput>
+</screen>
+
+ <sect1 id="s1-xml-tags-caveats">
+ <title>Tags and Entities Caveats</title>
+
+ <indexterm>
+ <primary>xml tags</primary>
+ <secondary>caveats</secondary>
+ </indexterm>
+
+ <para>
+ It is very important that you remember the caveats in this section. Even
+ though they are more strict than valid DocBook XML, these rules exist
+ so that both the HTML and PDF outputs look proper.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>Do Not Use Trademark Entities</term>
+ <listitem>
+ <para>Do not use the trademark entities &trade;, &copy;, or
+ &reg; because the do not produce HTML output that works for all
+ charsets. The HTML output produces by these entities are declared in
+ the DTD and cannot be changed via the stylesheet.</para>
+ <para>Instead, use the <command>trademark</command> tag and its
+ associates classes as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><trademark>trademark symbol after me</trademark>
+ </para>
+ </listitem>
+ <listitem>
+ <para><trademark class="registered">registered trademark symbol after me</trademark>
+ </para>
+ </listitem>
+ <listitem>
+ <para><trademark class="copyright">copyright symbol after me</trademark></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <command>para</command> tags</term>
+ <listitem>
+ <para>Do not use <command>para</command> tags around anything other
+ than a simple paragraph. Doing so will create additional white space
+ within the text itself in the PDF version.
+ </para>
+ <para>Specifically, do not use <command>para</command> tags around
+ the following (or, to put this another way, do not embed the
+ following within <command>para</command> tags):
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><screen></para>
+ </listitem>
+ <listitem>
+ <para><itemizedlist></para>
+ </listitem>
+ <listitem>
+ <para><orderedlist></para>
+ </listitem>
+ <listitem>
+ <para><variablelist></para>
+ </listitem>
+ <listitem>
+ <para><table></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <command>para</command> tags within
+ <command>listitem</command> tags</term>
+ <listitem>
+ <para>Content inside <command>para</command> tags within
+ <command>listitem</command> tags <emphasis>must</emphasis> start
+ immediately after the beginning <para> tag to avoid extra
+ white space in the PDF version.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <command>screen</command> tags</term>
+ <listitem>
+ <para>The content inside <command>screen</command> tags
+ (<screen> and </screen>)
+ <emphasis>must</emphasis> be flush left in the XML file;
+ otherwise, the extraneous whitespace will appear in the HTML
+ version.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-application">
+ <title><command>application</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>application</secondary>
+ </indexterm>
+
+ <para>An application is the name of a GUI software program. A command is
+ the name of an executable (text) program or a software command.</para>
+
+ <para>The <command><application></command> and
+ <command></application></command> tags allow you to refer to an
+ application or program. For example, the following XML:
+ </para>
+
+<screen>
+<computeroutput>
+To view the Web in Linux, you can use
+<application>Mozilla</application> or
+<application>lynx</application> if you only want a text-based
+browser.
+</computeroutput>
+</screen>
+
+ <para>
+ produces the following output:
+ </para>
+
+ <para>
+ To view the Web in Linux, you can use <application>Mozilla</application>
+ or <application>lynx</application> if you only want a text-based browser.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-chapter">
+ <title><command>chapter</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>chapter</secondary>
+ </indexterm>
+
+ <para>
+ A DocBook book can be divided into chapters such as:
+ </para>
+
+<screen>
+<computeroutput>
+<!--$Id: docs-xml-tags.xml,v 1.3 2006/12/23 23:49:59 pfrields Exp $ -->
+
+ <chapter id="ch-sample">
+ <title>Sample Chapter</title>
+
+ <para>This is a sample chapter, showing you the XML tags used to create a
+ chapter, sections, and subsections.</para>
+
+ </chapter>
+</computeroutput>
+</screen>
+
+ <para>
+ The chapter can also be further divided into sections
+ (<command>sect1</command>, <command>sect2</command>,
+ <command>sect3</command>, etc.). Refer to <xref
+ linkend="s1-xml-tags-sections"></xref> for details.
+ </para>
+
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-citetitle">
+ <title><command>citetitle</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>citetitle</secondary>
+ </indexterm>
+
+
+ <para>
+ The <command><citetitle></command> tag provides formatting for a
+ specific references (title can be manually typed out or if already
+ defined within your document set, given as an entity<footnote><para>An
+ entity is a short hand way of referring to another manual or guide. It
+ can be defined within the parent document or within a set of files that
+ your DTD references for your specific documentation set.</para>
+ </footnote>
+ ).</para>
+
+ <para>
+ For example:
+ </para>
+<screen>
+<computeroutput>
+<citetitle>IG;</citetitle>.
+</computeroutput>
+</screen>
+ <para>
+ The output looks like <citetitle>&IG;</citetitle> because &IG; is an
+ entity.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-command">
+ <title><command>command</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>command</secondary>
+ </indexterm>
+
+ <para>An application is the name of a GUI software program. A command is
+ the name of an executable (text) program or a software command. Any
+ program that is a command line or text-based only tool is marked with
+ <command>command</command> tags. </para>
+
+
+ <para>If you have text that is a command, use the
+ <command><command></command> and
+ <command></command></command> tags such as:
+ </para>
+
+
+
+<screen>
+<computeroutput>
+To change your keyboard after installation, become root
+and use the <command>redhat-config-keyboard</command> command,
+or you can type <command>setup</command> at the root prompt.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+ <para>
+ To change your keyboard after installation, become root and use
+ the <command>redhat-config-keyboard</command> command, or you can type
+ <command>setup</command> at the root prompt.
+ </para>
+
+ <para>Another example would be:</para>
+
+<screen>
+<computeroutput>
+<command>MAILNOVIOLATIONS</command> — If set
+to <command>true</command> this option tells Tripwire to
+email a report at a regular interval regardless of whether or not
+any violations have occured. The default value is
+<command>true</command>.
+</computeroutput>
+</screen>
+
+ <para>
+ with the output:
+ </para>
+
+ <para>
+ <command>MAILNOVIOLATIONS</command> — If set to
+ <command>true</command> this variable tells Tripwire to email a report
+ at a regular interval regardless of whether or not any violations have
+ occured. The default value is <command>true</command>.
+ </para>
+
+ <note>
+ <title>Note</title> <para>In this example, the option value (true) is
+ defined with a <command> tag set. Because a option is a
+ configuration file option (command line options which would use the
+ <option> tag set), and because there is no configuration file
+ option tag available to use, we are extending the <command> tag
+ set to define options in a configuration file.</para>
+ </note>
+
+ <para>
+ Terms marked with <command>command</command> tags because there aren't
+ exact tags for them:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Options in configuration files such as Apache directives</para>
+ </listitem>
+ <listitem>
+ <para>daemon names</para>
+ </listitem>
+ </itemizedlist>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-compoutput">
+ <title><command>computeroutput</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>computeroutput</secondary>
+ </indexterm>
+
+ <para>
+ To show computer output use the following tags:
+ </para>
+<screen>
+<computeroutput>
+<computeroutput>Do you want to delete this file? y n</computeroutput>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+ <para>
+ <computeroutput>Do you really want to delete this file? y n</computeroutput>
+ </para>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-emphasis">
+ <title><command>emphasis</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>emphasis</secondary>
+ </indexterm>
+
+ <para>
+ To emphasis content, use the <command><emphasis></command> and
+ <command></emphasis></command> tags. For example:
+ </para>
+<screen>
+<computeroutput>
+This installation <emphasis>will remove all</emphasis> existing
+Linux partitions on <emphasis>all</emphasis> hard drives in your
+system; non-Linux partitions will not be removed.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ This installation <emphasis>will remove all</emphasis> existing Linux
+ partitions on <emphasis>all</emphasis> hard drives in your system;
+ non-Linux partitions will not be removed.
+ </para>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-example">
+ <title><command>example</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>example</secondary>
+ </indexterm>
+
+ <para>The <command><example></command> and
+ <command></example></command> tags are used to format text within a
+ document and is great for adding emphasis to show examples of code,
+ exercises, and more. </para>
+
+ <para>The <command><example></command> tag set should be given an ID
+ and title:</para>
+
+<screen>
+ <example id="static-ip">
+ <title>Static IP Address using DHCP</title>
+
+<screen width=60>
+<computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+<computeroutput>
+</screen>
+
+ </example>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <example id="static-ip">
+ <title>Static IP Address using DHCP</title>
+
+<screen>
+<computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+</computeroutput>
+</screen>
+ </example>
+
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-filename">
+ <title><command>filename</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>filename</secondary>
+ </indexterm>
+
+ <para>
+ The <command><filename></command> and
+ <command></filename></command> tags define a filename or path to a
+ file. Since directories are just special files, they are marked with the
+ <command>filename</command> tags as well. For example:
+ </para>
+<screen>
+Edit the <filename>/home/smoore/sam.xml</filename> file to make
+changes or add comments.
+</screen>
+ <para>
+ The output:
+ </para>
+ <para>
+ Edit the <filename>/home/smoore/sam.xml</filename> file to make changes
+ or add comments.
+ </para>
+
+ <para>
+ They are also used to markup an RPM package name. For example:
+ </para>
+<screen>
+To use the <application>Keyboard Configuration Tool</application>, the
+<filename>system-config-keyboard</filename> RPM package must be installed.
+</screen>
+ <para>
+ The output:
+ </para>
+ <para>
+ To use the <application>Keyboard Configuration Tool</application>, the
+ <command>redhat-config-keyboard</command> RPM package must be installed.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ Directory names must end with a forward slash
+ (<computeroutput>/</computeroutput>) to distinguish them from file
+ names.
+ </para>
+ </note>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-firstterm">
+ <title><command>firstterm</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>firstterm</secondary>
+ </indexterm>
+
+ <para>
+ The <command><firstterm></command> and
+ <command></firstterm></command> tags helps to define a word that
+ may be unfamiliar to the user, but that will be seen commonly throughout
+ the text. For example:
+ </para>
+<screen>
+<computeroutput>
+Nearly every modern-day operating system uses <firstterm>disk
+partitions</firstterm>, and &FC; is no exception.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Nearly every modern-day operating system uses <firstterm>disk
+ partitions</firstterm>, and &FC; is no exception.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-footnote">
+ <title><command>footnote</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>footnote</secondary>
+ </indexterm>
+
+ <para>
+ If you need to make a footnote, use the following example:
+ </para>
+<screen>
+<computeroutput>
+For those of you who need to perform a server-class
+<footnote>
+<para>
+A server-class installation sets up a typical server
+environment. Note, no graphical environment is
+installed during a server-class installation.
+</para>
+</footnote> installation, refer to the <citetitle>Installation Guide</citetitle>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ For those of you who need to perform a server-class <footnote> <para>A
+ server-class installation sets up a typical server environment. Please note, no
+ graphical environment is installed during a server-class installation.</para>
+ </footnote> installation, refer to the
+ <citetitle>Installation Guide</citetitle>.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-figure">
+ <title><command>figure</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>figure</secondary>
+ </indexterm>
+
+ <important>
+ <title>Important</title>
+ <para>
+ Order matters! The EPS file <emphasis>must</emphasis> be declared
+ first.
+ </para>
+ </important>
+
+ <para>
+ An example figure declaration:
+ </para>
+
+<screen>
+<computeroutput>
+<figure id="fig-ksconfig-basic">
+ <title>Basic Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.eps"
+ format="EPS"/>
+ </imageobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.png"
+ format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>
+ Some text description of this image
+ </phrase>
+ </textobject>
+ </mediaobject>
+</figure>
+</computeroutput>
+</screen>
+
+ <para>
+ The following describes what needs to be edited:
+ </para>
+
+<screen>
+<figure id="fig-ksconfig-basic"> <emphasis>==> id="" would be edited</emphasis>
+
+<title>Basic Configuration</title> <emphasis>==> title would be edited</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.eps"> <emphasis>==> .eps location would be edited</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.png"> <emphasis>==> .png location would be edited</emphasis>
+
+<phrase>Some text description of this image</phrase> <emphasis>==> "Some text..." would be edited</emphasis>
+</screen>
+
+ <para>
+ For more information on taking screenshots, refer to <xref
+ linkend="s1-screenshots"/>.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-gui">
+ <title>GUI Tags</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ </indexterm>
+
+ <sect2 id="s2-xml-tags-guilabel">
+ <title><command>guilabel</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guilabel</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guilabel</secondary>
+ </indexterm>
+
+ <para>
+ Use the <command><guilabel></command> and
+ <command></guilabel></command> tags as a default for GUI
+ descriptions, like a screen name or screen title. For example:
+ </para>
+<screen>
+<computeroutput>
+The <guilabel>Authentication Configuration</guilabel> screen
+shows you how to make your system more secure.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ The <guilabel>Authentication Configuration</guilabel> screen shows you how to
+ make your system more secure.
+ </para>
+ </sect2>
+
+ <sect2 id="s2-xml-tags-guibutton">
+ <title><command>guibutton</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guibutton</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guibutton</secondary>
+ </indexterm>
+
+ <para>
+ Use the <command><guibutton></command> and
+ <command></guibutton></command> tags to denote a button on a screen or
+ menu. For example:
+ </para>
+<screen>
+<computeroutput>
+Check the <guibutton>Activate on boot</guibutton> button
+to have the X Window System start automatically.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Check the <guibutton>Activate on boot</guibutton> button to have the X
+ Window System start automatically.
+ </para>
+ </sect2>
+
+ <sect2 id="s2-xml-tags-guiicon">
+ <title><command>guiicon</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guiicon</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guiicon</secondary>
+ </indexterm>
+
+ <para>
+ The <command><guiicon></command> and <command></guiicon></command>
+ tags are used to denote a panel or desktop icon. For example:
+ </para>
+<screen>
+<computeroutput>
+Double-click the <guiicon>Start Here</guiicon> icon on the desktop.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Double-click the <guiicon>Start Here</guiicon> icon on the desktop.
+ </para>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-guimenu">
+ <title><command>guimenu</command> and
+ <command>guimenuitem</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guimenu</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guimenu</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guimenuitem</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guimenuitem</secondary>
+ </indexterm>
+
+ <para>
+ To note a menu (like in the installation program or within the control panel),
+ use the <command><guimenu></command> and
+ <command></guimenu></command> tags.
+ </para>
+
+ <para>
+ To note submenu items, use the <command><guimenuitem></command> and
+ <command></guimenuitem></command> tags. (Please note that there should not
+ be any breaks between these commands, but for printing purposes breaks have been
+ inserted). For example:
+ </para>
+<screen>
+<computeroutput>
+Select
+<guimenu>Main Menu</guimenu> =>
+ <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> to start the
+<application>Emacs</application> text editor.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ From the control panel, click on <guimenu>Main Menu</guimenu> =>
+ <guimenuitem>Programming</guimenuitem> =>
+ <guimenuitem>Emacs</guimenuitem> to start the
+ <application>Emacs</application> text editor.
+ </para>
+ </sect2>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-keycap">
+ <title><command>keycap</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>keycap</secondary>
+ </indexterm>
+
+ <para>
+ To denote a specific key, you will need to use the
+ <command><keycap></command> and <command></keycap></command>
+ tags. Brackets are automatically added around the keycap, so do not add
+ them in your XML code. For example:
+ </para>
+<screen>
+<computeroutput>
+To make your selection, press the <keycap>Enter</keycap> key.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ To make your selection, press the <keycap>Enter</keycap> key.
+ </para>
+
+ <sect2 id="s2-xml-tags-menuchoice">
+ <title><command>menuchoice</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>menuchoice</secondary>
+ </indexterm>
+
+ <para>
+ Often using a mouse is tedious for common tasks. Therefore,
+ programmers often build in keyboard-shortcuts to simplify their
+ program. These should be described using the shortcut tag as a wrapper
+ for the keyboard tags. The shortcut tag must be wrapped inside the
+ menuchoice tag. For example:
+ </para>
+
+<screen>
+<computeroutput>
+Go to the menu bar and choose:
+ <menuchoice>
+ <shortcut>
+ <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
+ </shortcut>
+ <guimenu><accel>F</accel>ile</guimenu>
+ <guimenuitem><accel>S</accel>ave</guimenuitem>
+ </menuchoice>.
+</computeroutput>
+</screen>
+
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Go to the menu bar and choose:
+ <menuchoice>
+ <shortcut>
+ <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
+ </shortcut>
+ <guimenu><accel>F</accel>ile</guimenu>
+ <guimenuitem><accel>S</accel>ave</guimenuitem>
+ </menuchoice>.
+ </para>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-keycombo">
+ <title><command>keycombo</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>keycombo</secondary>
+ </indexterm>
+
+ <para>
+ To illustrate a key combination, you need to use the
+ <command><keycombo></command> and
+ <command></keycombo></command>,
+ <command><keycap></command> and
+ <command></keycap></command> tags. For example:
+ </para>
+<screen>
+<computeroutput>
+To reboot your system, press <keycombo>
+<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>
+</keycombo>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ To reboot your system, press
+ <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>
+ </keycombo>.
+ </para>
+
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-lists">
+ <title>Lists</title>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary>creating</secondary>
+ </indexterm>
+
+ <para>There are several types of lists you can create using XML. You
+ can have a itemized (bulleted) list, a ordered (numbered) list, or a
+ variable list (presents a term and then a separate paragraph).</para>
+
+ <para>There is also a list format for tables and for for creating a
+ list of glossary terms and their definitions.</para>
+
+ <para>The sections below will discuss the proper uses for the various
+ list and how to create them.</para>
+
+ <sect2 id="s2-xml-tags-itemizedlist">
+ <title><command>itemizedlist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>itemizedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>itemizedlist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>itemizedlist</command></secondary>
+ </indexterm>
+
+ <para>An <command>ItemizedList</command> is best used to present
+ information that is important for the reader to know, but that does
+ not need to be in a specific order. It is shorter than a
+ <command>VariableList</command> and presents the information in a
+ very simple way.</para>
+
+ <para>To create an <command>ItemizedList</command> (otherwise known as
+ bulleted list), use the following command sequence:</para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command>
+ tags. If you do not do this, you will find extra whitespace in
+ your lists where the text does not line up correctly. This is most
+ noticeable when you have a series of list items that consist of
+ multiple lines of text. This whitespace is not as noticeable in
+ the HTML output as it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<itemizedlist>
+ <listitem>
+ <para>Getting familiar with the installation program's user interface</para>
+ </listitem>
+
+ <listitem>
+ <para>Starting the installation program</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting an installation method</para>
+ </listitem>
+</itemizedlist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Getting familiar with the installation program's user interface</para>
+ </listitem>
+
+ <listitem>
+ <para>Starting the installation program</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting an installation method</para>
+ </listitem>
+ </itemizedlist>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-orderedlist">
+ <title><command>OrderedList</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>orderedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>orderedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>orderedlist</tertiary>
+ </indexterm>
+
+ <para>An <command>orderedlist</command> is best used to present
+ information that is important for the reader to know in a specific
+ order. <command>orderedlist</command>s are a good way to convey
+ step-by-step senarios to the audience you are writing for.</para>
+
+ <para>
+ To create an <command>orderedlist</command> (numbered list), use the
+ following XML code sequence:
+ </para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command>
+ tags. If you do not do this, you will find extra whitespace in
+ your lists where the text does not line up correctly. This is most
+ noticeable when you have a series of list items that consist of
+ multiple lines of text. This whitespace is not as noticeable in
+ the HTML output as it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<orderedlist>
+ <listitem>
+ <para>Online &mdash; http://www.redhat.com/support/errata; supplies errata
+ you can read online, and you can download diskette images
+ easily.</para>
+ </listitem>
+
+ <listitem>
+ <para>Email &mdash; By sending an empty mail message to errata@@redhat.com,
+ you will receive an email containing a text listing of the
+ complete errata of the installation program and related software
+ (if errata exist at that time). Also included are URLs to each
+ updated package and diskette image in the errata. Using these
+ URLs, you can download any necessary diskette images. Please
+ note: use binary mode when transferring a diskette image.</para>
+ </listitem>
+</orderedlist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <orderedlist>
+ <listitem>
+ <para>Online — http://www.redhat.com/support/errata; supplies errata
+ you can read online, and you can download diskette images
+ easily.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Email — By sending an empty mail message to
+ errata@@redhat.com, you will receive an email containing a text
+ listing of the complete errata of the installation program and
+ related software (if errata exist at that time). Also included
+ are URLs to each updated package and diskette image in the
+ errata. Using these URLs, you can download any necessary
+ diskette images. Please note: use binary mode when transferring
+ a diskette image.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-varlist">
+ <title><command>Variablelist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>variablelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>variablelist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>variablelist</command></secondary>
+ </indexterm>
+
+ <para>A <command>variablelist</command> best represents a list of
+ terms and definitions or descriptions for those terms.</para>
+
+ <para>To create a <command>variablelist</command>, use the following
+ command sequence:
+ </para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command> tags. If
+ you do not do this, you will find extra whitespace in your lists
+ where the text does not line up correctly. This is most noticeable
+ when you have a series of list items that consist of multiple lines
+ of text. This whitespace is not as noticeable in the HTML output as
+ it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<variablelist>
+ <varlistentry>
+ <term> New Multi-CD Install </term>
+ <listitem>
+ <para>As the installation program continues to grow, Red Hat has developed
+ an installation program capable of installing from
+ multiple CD-ROMs.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>XFree 4.0 </term>
+ <listitem>
+ <para>Configuration of your X Window System during the installation has
+ never been more thorough. From choosing your monitor and its correct
+ settings, to video card probing, to testing your desired X setup,
+ Xconfigurator will help you set everything just right.</para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <variablelist>
+ <varlistentry>
+ <term>New Multi-CD Install</term> <listitem> <para>As the
+ installation program continues to grow, Red Hat has developed an
+ installation program capable of installing from
+ multiple CD-ROMs.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term> XFree 4.0</term>
+ <listitem>
+ <para>Configuration of your X Window System during the
+ installation has never been more thorough. From choosing your
+ monitor and its correct settings, to video card probing, to
+ testing your desired X setup, Xconfigurator will help you set
+ everything just right.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ Do <emphasis>not</emphasis> specify the
+ <computeroutput>frame</computeroutput> attribute to the table. Doing
+ so breaks PDF production.
+ </para>
+ </warning>
+
+ </sect2>
+
+ <sect2 id="s2-xml-tags-simplelist">
+ <title>Creating a List Within a Table Using <command>Simplelist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>simplelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>simplelist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>simplelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>tables</primary>
+ <secondary>creating a list within a table</secondary>
+ <tertiary><command>simplelist</command></tertiary>
+ </indexterm>
+
+ <para>A <command>simplelist</command> is an unadorned list of
+ items. <command>simplelist</command>s can be inline or arranged in
+ columns.</para>
+
+ <para>We use <command>simplelist</command> to add separate paragraphs
+ of text within a table element. A regular list, such as
+ <command>itemizedlist</command>, cannot be embedded within a table.</para>
+
+ <para>The XML commands for a table look like:</para>
+
+<screen>
+<computeroutput>
+ <table id="tb-hwinfo-hostbus">
+ <title>Host Bus Adapter Features and Configuration Requirements</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="HostBus" colwidth="33"/>
+ <colspec colnum="2" colname="Features" colwidth="34"/>
+ <colspec colnum="3" colname="Single" colwidth="33"/>
+
+ <thead>
+ <row>
+ <entry>Host Bus Adapter</entry>
+ <entry>Features</entry>
+ <entry>Single-Initiator Configuration</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is
+ off.</member>
+ </simplelist></entry>
+
+ <entry><simplelist>
+ <member>Set the onboard termination to automatic (the
+ default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ <row>
+ <entry>Qlogic QLA1080</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is off,
+ unless jumpers are used to enforce termination.</member>
+ </simplelist></entry>
+
+
+ <entry><simplelist>
+ <member>Set the onboard termination to
+ automatic (the default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <table id="tb-hwinfo-hostbus">
+ <title>Host Bus Adapter Features and Configuration Requirements</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="HostBus" colwidth="33"/>
+ <colspec colnum="2" colname="Features" colwidth="34"/>
+ <colspec colnum="3" colname="Single" colwidth="33"/>
+
+ <thead>
+ <row>
+ <entry>Host Bus Adapter</entry>
+ <entry>Features</entry>
+ <entry>Single-Initiator Configuration</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is
+ off.</member>
+ </simplelist></entry>
+
+ <entry><simplelist>
+ <member>Set the onboard termination to automatic (the
+ default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ <row>
+ <entry>Qlogic QLA1080</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is off,
+ unless jumpers are used to enforce termination.</member>
+ </simplelist></entry>
+
+
+ <entry><simplelist>
+ <member>Set the onboard termination to
+ automatic (the default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+ <note>
+ <title>Note</title>
+ <para>Notice how the <command>SimpleList</command> tags are
+ used. The <entry> and <simplelist> tags must be aligned
+ beside one another, otherwise you will receive a parsing error.</para>
+ </note>
+
+ <para>For each paragraph or list item to be added within a
+ <command>SimpleList</command>, the <member> tag set must be
+ added around that particular text item.</para>
+ </sect2>
+
+ <sect2 id="s2-xml-tags-glossary">
+ <title><command>glosslist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>glosslist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>glosslist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>glosslist</command></secondary>
+ </indexterm>
+
+ <para>Use the <command>glosslist</command> command set to create a
+ list of glossary terms and their definitions.</para>
+
+
+ <para>In XML, an example looks like the following:</para>
+
+<screen>
+<computeroutput>
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>A small application, usually a utility or other
+ simple program.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>The design for organization and integration of
+ components within a computer or computer system.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>To transfer files into storage for the purpose of
+ saving space and/or organization.</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+</computeroutput>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>A small application, usually a utility or other simple program.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>The design for organization and integration of components
+ within a computer or computer system.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>To transfer files into storage for the purpose of saving
+ space and/or organization.</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+
+ </sect2>
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-option">
+ <title><command>option</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>option</secondary>
+ </indexterm>
+
+ <para>If you have a command that offers an option or a flag, use the
+ <command><option></command> and
+ <command></option></command> tags.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>The <option> tag set is only meant to be used for command
+ line options, not options in configuration files.</para>
+ </note>
+
+ <para>In XML, specifying an option would look like the
+ following:</para>
+
+<screen>
+<computeroutput>
+For example, with the command <command>ls</command> you can
+specify an option such as <option>-la</option>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>For example, with the command <command>ls</command> you can
+ specify an option such as <option>-la</option>.</para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-indexing">
+ <title>Index Entries</title>
+
+ <indexterm>
+ <primary>indexing</primary>
+ </indexterm>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>indexing</secondary>
+ </indexterm>
+
+ <para>The following command sequence shows you the code inserted into
+ the body of the text to add an index entry to your document:
+ </para>
+
+<screen>
+<computeroutput>
+<indexterm> <-- indicates a term to be placed in the index
+<primary>foo</primary> <-- indicates that "foo" is the first term
+<secondary>bar</secondary> <-- "bar" will be listed under "foo"
+</indexterm> <-- closes this index entry
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>foo</primary>
+ <secondary>bar</secondary>
+ </indexterm>
+
+
+ <para>The <command><seealso></command> tag allows you to
+ reference another index entry or refer to another manual. Make sure
+ the <command><seealso></command> reference you are pointing to
+ has its own entry. For example:
+ </para>
+
+ <indexterm>
+ <primary>indexing</primary>
+ <secondary>seealso tag</secondary>
+ </indexterm>
+
+<screen>
+<computeroutput>
+<indexterm>
+<primary>SWAK</primary>
+<seealso>salutations</seealso>
+</indexterm>
+
+
+<indexterm>
+<primary>salutations</primary>
+</indexterm>
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>SWAK</primary>
+ <seealso>Salutations</seealso>
+ </indexterm>
+
+ <indexterm>
+ <primary>Salutations</primary>
+ </indexterm>
+
+ <para>
+ The <command><see></command> tag allows you to reference to
+ another index entry entirely. For example:
+ </para>
+ <indexterm>
+ <primary>indexing</primary>
+ <secondary>see tag</secondary>
+ </indexterm>
+
+
+<screen>
+<computeroutput>
+<indexterm>
+<primary>Guinness</primary>
+<see>beer</see> <-- beer will be listed under
+the Guinness entry, but you must make sure beer also has its
+own entry to refer to.
+</indexterm>
+
+<indexterm>
+<primary>beer</primary>
+</indexterm>
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>Guinness</primary>
+ <see>Beer</see>
+ </indexterm>
+
+ <indexterm>
+ <primary>Beer</primary>
+ </indexterm>
+
+ <para>To view the HTML output of the index entries shown here, refer
+ to the <filename>generated-index.html</filename> file at the end of
+ this document.</para>
+
+ <para>How does the index get generated? If indexterms exist in the
+ document and the beginning and ending index tags exist before the end
+ tag for the book or article, an index is created because of the
+ <command>generate.index</command> stylesheet parameter, which is set to
+ true by default.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-para">
+ <title><command>para</command></title>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>para</secondary>
+ </indexterm>
+
+ <para>For any paragraph, the <command><para></command> and
+ <command></para></command> tags must open and close that
+ particular paragraph.
+ </para>
+
+ <para>Do not use para tags around anything other than a simple
+ paragraph. Doing so will create additional white space within
+ the text itself.</para>
+
+ <para>Do not use <command><para></command> tags around the
+ following (or, to put this another way, do not embed the
+ following within <command><para></command> tags):</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><command><screen></command></para>
+ </listitem>
+ <listitem>
+ <para><command><itemizedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><orderedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><variablelist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><table></command></para>
+ </listitem>
+ </itemizedlist>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-part">
+ <title><command>part</command></title>
+
+ <indexterm>
+ <primary>parts</primary>
+ </indexterm>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>part</secondary>
+ </indexterm>
+
+ <para>
+ In the parent file, you can separate the chapters into parts to divide
+ them into logical groups. For example, in the parent file, the
+ <command>part</command> tags surround the chapter entities:
+ </para>
+<screen>
+<computeroutput>
+<part id="pt-foo">
+ <partintro>
+ <para>Some text for the part intro</para>
+ &CHAPTER;
+
+ &ANOTHER-CHAPTER;
+</part>
+</computeroutput>
+</screen>
+
+ <para>
+ If you create a part, include a part introduction describing the
+ contents of the part. For example:
+ </para>
+
+<screen>
+<computeroutput>
+ <part id="pt-setup">
+ <title>Getting Setup</title>
+ <partintro>
+ <para>This section contains information you will need when you first join
+ the Docs group. You might need to refer to this part again for
+ information such as installing &FC;.</para>
+ </partintro>
+</computeroutput>
+</screen>
+
+ <para>
+ In the HTML output, a separate HTML page is generated with the part
+ number, title, introduction, and TOC. In the PDF output, the same
+ information about the part is on a separate page.
+ </para>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-prompt">
+ <title><command>prompt</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>prompt</secondary>
+ </indexterm>
+
+ <para>
+ To show a prompt, such as a root or DOS prompt, use the
+ <command><prompt></command> and <command></prompt></command>
+ commands. For example:
+ </para>
+<screen>
+<computeroutput>
+At the <prompt>LILO:</prompt> boot prompt, type linux to
+boot into your Linux partition.
+
+At the <prompt>C:\></prompt> prompt, type ....
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ At the <prompt>LILO:</prompt> boot prompt, type linux to boot into your
+ Linux partition.
+ </para>
+ <para>
+ At the <prompt>C:\></prompt> prompt, type ....
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ When showing example computer output (usually in
+ <command>screen</command> tags), do not include the prompt or command
+ (unless the command or prompt is the actually computer output you want
+ to show).</para>
+ </note>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-replaceable">
+ <title><command>replaceable</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>replaceable</secondary>
+ </indexterm>
+
+ <para>
+ To create replaceable text, use the tags
+ <command><replaceable></command> and
+ <command></replaceable></command> around the text you want to use as a
+ variable.
+ </para>
+ <para>
+ This example demonstrates how to use the <command>replaceable</command>
+ tags when referencing the name of an RPM file:
+ </para>
+<screen>
+foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+<screen>
+foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm
+</screen>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-screen">
+ <title><command>screen</command></title>
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>screen</secondary>
+ </indexterm>
+
+ <para>
+ The <command><screen></command> command is used to format text
+ within a document and is great for adding emphasis to show examples of
+ code, computer output, and more. In HTML with the Fedora CSS file, this
+ appears in box with a grey background. To use this command you only need
+ the opening <command><screen></command> and closing
+ <command></screen></command> tags around the text you are
+ emphasizing.
+ </para>
+
+ <important>
+ <title>Important</title>
+ <para>
+ When using the <command><screen></command> tag, set
+ everything within that screen to flush left. The contents of
+ the <sgmltag class="starttag">screen</sgmltag> element are
+ rendered exactly as is, including any indentation. Using flush
+ left prevents extra blank space in front of the text inside the
+ gray background when the content is converted to HTML.
+ </para>
+ </important>
+
+ <para>
+ The <command><screen></command> tag set may contain other inline
+ tags, such as <command><computeroutput></command>,
+ <command><userinput></command>, or
+ <command><replaceable></command>. Additional inline tags are not
+ required by definition. The <command><screen></command> tags by
+ themselves may provide sufficient context, especially for simple examples
+ or file listings. Consider the context of the example, and use inline tags
+ if they are helpful to the reader.
+ </para>
+
+ <para>
+ If you use inline tags, remember that line breaks inside
+ <command><screen></command> tags create line breaks in any rendered
+ output. Place any inline tags <emphasis>on the same line</emphasis> as
+ their content. Do not overuse tagging within a
+ <command><screen></command> tag set.
+ </para>
+
+ <para>
+ An example of <command><screen></command> is the following:
+ </para>
+
+<screen>
+<computeroutput><screen>
+This is an example of a screen. You do not need &lt;para&gt; tags
+within this command.
+</screen></computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+<screen>
+This is an example of a screen. You do not need <para> tags
+within this command.
+</screen>
+
+ <sect2 id="s2-xml-tags-screen-inline-tags">
+ <title>Using Inline Tags with <command>screen</command></title>
+ <para>
+ If you choose to use inline tags inside a
+ <command><screen></command> section, follow these guidelines for
+ consistency. If the content in the screen is a listing of a
+ configuration file or the output of a program, use the
+ <command><computeroutput></command> tag set around the entire
+ output. If the user should type the example on the command line or in
+ a configuration file, use the <command><userinput></command> tag
+ set. Separate input and output with a short sentence of narrative, as
+ below:
+ </para>
+
+<screen>
+ <command><para></command>
+ Type the following command:
+ <command></para></command>
+
+<command><screen></command>
+<command><userinput></command>command -sw file1<command></userinput></command>
+<command></screen></command>
+
+ <command><para></command>
+ You should see the following output:
+ <command></para></command>
+
+<command><screen></command>
+<command><computeroutput></command>Completed, time = 0.12 sec<command></computeroutput></command>
+<command></screen></command>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <para>
+ Type the following command:
+ </para>
+
+<screen>
+<userinput>command -sw file1</userinput>
+</screen>
+
+ <para>
+ You should see the following output:
+ </para>
+
+<screen>
+<computeroutput>Completed, time = 0.12 sec</computeroutput>
+</screen>
+
+ <note>
+ <title>Note</title>
+ <para>
+ When showing a command or series of commands inside
+ <command>screen</command> tags, do not show the prompt.
+ </para>
+ </note>
+
+ <para>
+ If the <command><screen></command> shows the reader how to
+ change only <emphasis>part</emphasis> of a line, mark the change with
+ an inline <command><userinput></command> tag set. You may use
+ the <command><userinput></command> tag set inside a larger area
+ that is already marked inline with
+ <command><computeroutput></command>. Do not include any extra
+ lines of context in this case, unless excluding them would confuse the
+ reader. The following example illustrates these guidelines:
+ </para>
+
+<screen>
+ <command><para></command>
+ Edit the <command><filename></command>/etc/sysconfig/init<command></filename></command> file as follows:
+ <command></para></command>
+
+<command><screen></command>
+GRAPHICAL=<command><userinput></command>yes<command></userinput></command>
+<command></screen></command>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <para>
+ Edit the <filename>/etc/sysconfig/init</filename> file as follows:
+ </para>
+
+<screen>
+GRAPHICAL=<userinput>yes</userinput>
+</screen>
+
+ <para>
+ For an explanation of how to use the <command>replaceable</command>
+ tags within a set of <command>screen</command> tags, refer to <xref
+ linkend="s1-xml-tags-replaceable"></xref>.
+ </para>
+
+ </sect2>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-sections">
+ <title>Sections</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>sections</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>sections</primary>
+ </indexterm>
+
+ <para>Within an article (or chapter if it is a DocBook XML book like the
+ <citetitle>&IG;</citetitle>), you can have sections and
+ subsections. <command><sect1></command> is always the highest
+ section and you cannot have two sections of the same level within one
+ another (a section 2 can be created within a section 1, but section 1
+ has to be closed before another section 1 can be created). The general
+ layout follows:</para>
+
+<screen>
+<computeroutput>
+<sect1 id="s1-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+
+ <sect2 id="s2-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+ <sect3 id="s3-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+ </sect3>
+
+ </sect2>
+
+</sect1>
+</computeroutput>
+</screen>
+
+ <para>
+ If you only need one level of sections in a DocBook article, you can use
+ the <command>section</command> tag. For example:
+ </para>
+
+<screen>
+<computeroutput>
+<section id="sn-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+</section>
+<section id="sn-anothername">
+ <title>Insert Title Here</title>
+ <para>
+ More body text goes here.
+ </para>
+</section>
+</computeroutput>
+</screen>
+ </sect1>
+
+ <sect1 id="s1-xml-tags-table">
+ <title><command>table</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>table</secondary>
+ </indexterm>
+
+ <para>
+ The following is an example of creating a table.
+ </para>
+
+<screen>
+<table id="tb-mockup-before-begin">
+ <emphasis>This tells XML that you will be creating a table
+ and the ID name is <command>"tb-mockup-before-begin."</command></emphasis>
+
+<title>Available Features of GNOME and KDE</title>
+
+<tgroup cols="3">
+ <emphasis>This tells XML that you are creating a table
+ with three columns.</emphasis>
+
+<colspec colnum="1" colname="Features" colwidth="3"/>
+ <emphasis><command>colspec</command> says that you are giving information
+ about the column to XML</emphasis> <emphasis><command>colnum="1"</command>
+ says that you are giving specifications for the first column.</emphasis>
+
+ <emphasis><command>colname="Features"</command> says that the title for this
+ column will be "Features."</emphasis>
+
+ <emphasis><command>colwidth="3"</command> specifies the width of the
+ column. This can be more tricky: such as two columns with
+ widths of 1 and 2,the 1 is one-half the width of the 2, in
+ respect to the page size. But, what if you need the 1 to be a
+ little more than half of the 2, using a larger number ratio,
+ such as 10 to 20 would accomplish this. You could then change the
+ 10 to an 11 or a 12 to make it a little more than half of the
+ second column of 20. In no value is given, a value of 1 is
+ assumed.</emphasis>
+
+<colspec colnum="2" colname="GNOME" colwidth="2"/>
+<colspec colnum="3" colname="KDE" colwidth="2"/>
+
+<thead>
+ <emphasis>Contains one or more table row elements.</emphasis>
+
+<row>
+ <emphasis>Contains one or more table cell (entry) elements.</emphasis>
+
+<entry>Features</entry>
+ <emphasis>Table cell element, one of several in a row element, defining
+ columns within the row.</emphasis>
+
+<entry>GNOME</entry>
+<entry>KDE</entry>
+</row>
+</thead>
+
+<tbody>
+ <emphasis>Contains one or more row elements, for the main text
+ of the table.</emphasis>
+
+<row>
+<entry>highly configurable</entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>multiple window managers </entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>Internet applications</entry>
+<entry>yes </entry>
+<entry>yes </entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+</screen>
+
+ <table id="tb-mockup-before-begin">
+ <title>Available Features of GNOME and KDE</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="Features" colwidth="3"/>
+ <colspec colnum="2" colname="GNOME" colwidth="2"/>
+ <colspec colnum="3" colname="KDE" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Features </entry>
+ <entry>GNOME</entry>
+ <entry>KDE</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry>highly configurable</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>multiple window managers </entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>Internet applications</entry>
+ <entry>yes </entry>
+ <entry>yes </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <sect2 id="s2-xml-tags-listintable">
+ <title>Creating a List Within a Table</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>table</secondary>
+ <tertiary>list within a table</tertiary>
+ </indexterm>
+
+
+ <para>Creating a list within a table can be a difficult task. It
+ requires strict formatting and a set of commands that are not
+ available for command completion in
+ <application>Emacs</application>.</para>
+
+ <para>The tags you will need to use are
+ <command><simplelist></command> and
+ <command><member></command>.</para>
+
+ <para>The following example will show you the proper formatting for
+ creating a list within a table.</para>
+
+
+<screen>
+<computeroutput>
+<table id="tb-hardware-powerswitch">
+ <title>Power Switch Hardware Table</title>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="Hardware" colwidth="2"/>
+ <colspec colnum="2" colname="Quantity" colwidth="2"/>
+ <colspec colnum="3" colname="Description" colwidth="6"/>
+ <colspec colnum="4" colname="Required" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>Description</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Serial power switches</entry>
+
+ <entry>Two</entry>
+
+ <entry><simplelist> <member>Power switches enable each cluster system
+ to power-cycle the other cluster system. Note that clusters are
+ configured with either serial or network attached power switches and
+ not both.</member>
+
+ <member>The following serial attached power switch has been
+ fully tested:</member>
+
+ <member>RPS-10 (model M/HD in the US, and model M/EC in
+ Europe) </member>
+
+ <member>Latent support is provided for the following serial
+ attached power switch. This switch has not yet been fully
+ tested:</member>
+
+ <member>APC Serial On/Off Switch (partAP9211), <ulink
+ url="http://www.apc.com/">http://www.apc.com/</ulink></member>
+ </simplelist></entry>
+
+ <entry>Strongly recommended for data integrity under all failure
+ conditions</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+</table>
+</computeroutput>
+</screen>
+
+ <para>Notice how the <command><simplelist></command> tag must be
+ beside the <command><entry></command> tag? If you do not format
+ this properly, it will not parse cleanly.</para>
+
+ <para>The above example will look like the following:</para>
+
+ <table id="tb-hardware-powerswitch">
+ <title>Power Switch Hardware Table</title>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="Hardware" colwidth="2"/>
+ <colspec colnum="2" colname="Quantity" colwidth="2"/>
+ <colspec colnum="3" colname="Description" colwidth="6"/>
+ <colspec colnum="4" colname="Required" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>Description</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Serial power switches</entry>
+
+ <entry>Two</entry>
+
+ <entry><simplelist> <member>Power switches enable each cluster
+ system to power-cycle the other cluster system. Note
+ that clusters are configured with either serial or
+ network attached power switches and not both.</member>
+
+ <member>The following serial attached power switch has been
+ fully tested:</member>
+
+ <member>RPS-10 (model M/HD in the US, and model M/EC in
+ Europe) </member>
+
+ <member>Latent support is provided for the following
+ serial attached power switch. This switch has not yet
+ been fully tested:</member>
+
+ <member>APC Serial On/Off Switch (partAP9211), <ulink
+ url="http://www.apc.com/">http://www.apc.com/</ulink></member>
+ </simplelist></entry>
+
+ <entry>Strongly recommended for data integrity under all failure
+ conditions</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-trademark">
+ <title><command>trademark</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>trademark</command></secondary>
+ </indexterm>
+
+
+ <para>Do not use the trademark entities &trade;, &copy;, or
+ &reg; because the do not produce HTML output that works for all
+ charsets. The HTML output produces by these entities are declared in
+ the DTD and cannot be changed via the stylesheet.</para>
+
+ <para>Instead, use the <command>trademark</command> tag and its
+ associates classes as follows:
+ </para>
+
+<screen>
+<computeroutput>
+<trademark>trademark symbol after me</trademark>
+<trademark class="registered">registered trademark symbol after me</trademark>
+<trademark class="copyright">copyright symbol after me</trademark>
+</computeroutput>
+</screen>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-userinput">
+ <title><command>userinput</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>userinput</command></secondary>
+ </indexterm>
+
+ <para>
+ To show what a user would type, use the <command>userinput</command>
+ tag. For example:
+ </para>
+<screen>
+<computeroutput>
+At the prompt, type:
+
+<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ At the prompt, type:
+ </para>
+
+ <para>
+ <userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+ </para>
+ </sect1>
+
+
+<!-- <sect1 id="s1-xml-tags-mouse">
+ <title><command>mousebutton</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>mousebutton</secondary>
+ </indexterm>
+ <para>
+Describe mouse actions with the mousebutton tag. Below is an example of its use.
+</para>
+
+<screen>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+</screen>
+
+ <para>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+ </para>
+
+ </sect1> -->
+
+ <sect1 id="s1-xml-tag-sulink">
+ <title><command>ulink</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>ulink</secondary>
+ </indexterm>
+
+ <para>
+ To create a URL link within your text, use the following example:
+ </para>
+<screen>
+<computeroutput>
+Online &mdash; <ulink url="http://www.redhat.com/support/errata/">
+http://www.redhat.com/support/errata/</ulink>; supplies errata
+you can read online, and you can download diskette images easily.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Online — <ulink url="http://www.redhat.com/support/errata/">
+ http://www.redhat.com/support/errata/</ulink>; supplies errata
+ you can read online, and you can download diskette images easily.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ If the URL does not end in a filename, it must end in a slash
+ (<computeroutput>/</computeroutput>) to be a properly formed URL. For
+ example, <ulink
+ url="http://www.redhat.com/">http://www.redhat.com/</ulink>.
+ </para>
+ </note>
+
+ </sect1>
+
+ <sect1 id="s1-xml-tags-wordasword">
+ <title><command>wordasword</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>wordasword</secondary>
+ </indexterm>
+
+ <para>The <wordasword> tag set is used to define a word meant
+ specifically as a word and not representing anything else.</para>
+
+ <para>A lot of technical documentation contains words that have overloaded
+ meanings. Sometimes it is useful to be able to use a word without invoking
+ its technical meaning. The <wordasword> element identifies a word or
+ phrase that might otherwise be interpreted in some specific way, and
+ asserts that it should be interpreted simply as a word.</para>
+
+ <para>It is unlikely that the presentation of this element will be able to
+ help readers understand the variation in meaning; good writing will have
+ to achieve that goal. The real value of <wordasword> lies in the
+ fact that full-text searching and indexing tools can use it to avoid
+ false-positives.</para>
+
+ <para>For example:</para>
+
+<screen>
+<computeroutput>To use <command>grep</command> to search for the word
+<wordasword>linux</wordasword>, use the command
+<command>grep linux</command>.</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>To use <command>grep</command> to search for the word
+ <wordasword>linux</wordasword>, use the command <command>grep
+ linux</command>.</para>
+
+ <para>In the example, the word "linux" is just a word. It is not
+ meant to convey anything about Linux as a subject, or to add relevance or
+ meaning to the content. It can be replaced with any other word without
+ losing any of the context.</para>
+
+ </sect1>
+
+
+ <sect1 id="s1-xml-tags-xref">
+ <title><command>xref</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>xref</secondary>
+ </indexterm>
+
+ <para>
+ To refer to other sections or chapters within a manual, use the
+ <command><xref></command> tag.
+ </para>
+
+ <para>
+ The output of this displays the title of the section or chapter you are
+ pointing the user to. For example:
+ </para>
+<screen>
+<computeroutput>
+For more information about the parent file, refer to
+<xref linkend="ch-tutorial"></xref> and <xref linkend="s1-tutorial-parent"></xref>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ For more information about the parent file, refer to <xref linkend="ch-tutorial"></xref>
+ and <xref linkend="s1-tutorial-parent"></xref>.
+ </para>
+ </sect1>
+
+ </chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.3
+log
+ at Minor changes, major reformatting. Sorry about the noise.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags.xml,v 1.2 2006/12/17 00:41:55 pfrields Exp $ -->
+d204 1
+a204 1
+<!--$Id: docs-xml-tags.xml,v 1.2 2006/12/17 00:41:55 pfrields Exp $ -->
+@
+
+
+1.2
+log
+ at Ha, I know a lot more about why this book caused me so much pain when I first started learning DocBook and XML. Take that, crummy DOCTYPEs\!
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags.xml,v 1.1 2006/11/23 02:24:17 pfrields Exp $ -->
+d38 3
+a40 1
+ <para>All tags in XML must have an opening and closing tag Additionally,
+d142 5
+a146 6
+ <para>The <command>screen</command> tags (<screen> and
+ </screen>) <emphasis>must</emphasis> be flush left in the
+ XML file, and all the content inside the
+ <command>screen</command> tags must be flush left as well unless
+ the white space in intentional; otherwise, the extraneous
+ whitespace will appear in the HTML version.
+d204 1
+a204 1
+<!--$Id: docs-xml-tags.xml,v 1.1 2006/11/23 02:24:17 pfrields Exp $ -->
+d1817 6
+a1822 5
+ When using the <command><screen></command> tag, you must set
+ everything within that screen, including the
+ <command><screen></command> tags themselves, to flush left. This
+ must be done so that when it is converted to HTML, it will not have
+ extra blank space in front of it inside the gray background.
+d2503 7
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d1 2
+a2 2
+<!-- $Id: docs-xml-tags-en.xml,v 1.12 2004/09/30 14:25:36 tfox Exp $ -->
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+d203 1
+a203 1
+<!--$Id: docs-xml-tags-en.xml,v 1.12 2004/09/30 14:25:36 tfox Exp $ -->
+@
+
diff --git a/old-documentation-guide/en_US/Attic/fdp-info.xml,v b/old-documentation-guide/en_US/Attic/fdp-info.xml,v
new file mode 100644
index 0000000..da95ad3
--- /dev/null
+++ b/old-documentation-guide/en_US/Attic/fdp-info.xml,v
@@ -0,0 +1,95 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2007.02.18.14.22.00; author pfrields; state dead;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at Whoops, this must have been inadvertently committed while we were working at FUDCon. Return to your homes, nothing to see here....
+@
+text
+@<?xml version="1.0" encoding="UTF-8"?>
+
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+
+<!--
+ Warning! Warning! Danger, Will Robinson!
+ This is a generated file, produced from information in
+ the "rpm-info.xml" file.
+
+ DO NOT EDIT THIS FILE DIRECTLY!
+ Edit "rpm-info.xml" to change this information.
+ -->
+
+<bookinfo>
+ <title>Fedora Documentation Guide</title>
+ <copyright>
+ <year>2003</year>
+ <year>2004</year>
+ <year>2005</year>
+ <year>2006</year>
+ <holder>Red Hat, Inc.</holder>
+ <holder>Tammy Fox</holder>
+ <holder>Johnray Fuller</holder>
+ <holder>Sandra Moore</holder>
+ <holder>Paul W. Frields</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ <author>
+ <surname>Fuller</surname>
+ <firstname>Johnray</firstname>
+ </author>
+ <author>
+ <surname>Moore</surname>
+ <firstname>Sandra</firstname>
+ </author>
+ <author>
+ <surname>Frields</surname>
+ <firstname>Paul</firstname>
+ </author>
+ </authorgroup>
+ <revhistory id="rv-revhistory">
+ <revision>
+ <revnumber>0.2.6.3</revnumber>
+ <date>2005-09-18</date>
+ <authorinitials/>
+ <revdescription>
+ <para>
+ Update to new build requirements
+ </para>
+ </revdescription>
+ </revision>
+ </revhistory>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="/home/kwade/Documents/projects/fedora/cvs-docs/documentation-guide/../docs-common/common/legalnotice-opl-en_US.xml"/>
+</bookinfo>
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+@@
+
diff --git a/old-documentation-guide/en_US/acknowledgments.xml,v b/old-documentation-guide/en_US/acknowledgments.xml,v
new file mode 100644
index 0000000..61f8aac
--- /dev/null
+++ b/old-documentation-guide/en_US/acknowledgments.xml,v
@@ -0,0 +1,190 @@
+head 1.7;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.7
+ LIVE:1.6;
+locks; strict;
+comment @# @;
+
+
+1.7
+date 2007.07.29.23.55.25; author pfrields; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.06.23.05.24.16; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.02.03.22.29.37; author kwade; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2006.12.17.00.41.55; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2006.11.29.22.18.53; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2006.11.29.00.29.48; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.7
+log
+@* 0.3.0.3:
+ - Add information on po/LINGUAS
+
+* 0.3.0.2:
+ - Delete unnecessary tags section and references
+@
+text
+@<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+ <chapter id="acknowledgments">
+ <title>Acknowledgments</title>
+
+ <para>
+ This document is based on a document started by Tammy Fox (tfox at
+ redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and
+ Johnray Fuller (jrfuller at redhat.com).
+ </para>
+
+ <para>
+ A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to
+ fix a few typos and explain that anonymous CVS access does not allow
+ commits.
+ </para>
+
+ <para>
+ Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied
+ to add the trailing slashes to the <command>figure</command> tag example
+ in <filename>docs-xml-tags.xml</filename><!-- and to add <xref
+ linkend="ch-emacs-nxml"></xref>-->.
+ </para>
+
+ <para>
+ A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been
+ applied to add <xref linkend="ch-vim"></xref>.
+ </para>
+
+ <para>
+ A patch from Karsten Wade (kwade at redhat.com) has been applied to add
+ <xref linkend="sn-screenshots"></xref>. It was edited by Paul
+ W. Frields (stickster at gmail.com).
+ </para>
+
+ <!-- This section has been removed.
+ <para>
+ A patch from Paul W. Frields (stickster at gmail.com) has been applied
+ to add more explanation of the <command>screen</command> tag set to <xref
+ linkend="sn-xml-tags-screen"></xref>.
+ </para> -->
+
+ <para>
+ A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been
+ applied to more fully explaing the document building system.
+ </para>
+
+ </chapter>
+@
+
+
+1.6
+log
+ at This is finally being updated; I hope to finish this in the next week.
+@
+text
+ at d43 1
+d48 1
+a48 1
+ </para>
+@
+
+
+1.5
+log
+ at updating all section usage and associated ID tags
+@
+text
+ at d14 1
+a14 1
+ This document is based on the a document started by Tammy Fox (tfox at
+d40 1
+a40 1
+ W. Frields (stickstr5 at hotmail.com).
+d44 1
+a44 1
+ A patch from Paul W. Frields (stickstr5 at hotmail.com) has been applied
+@
+
+
+1.4
+log
+ at Ha, I know a lot more about why this book caused me so much pain when I first started learning DocBook and XML. Take that, crummy DOCTYPEs\!
+@
+text
+ at d39 1
+a39 1
+ <xref linkend="s1-screenshots"></xref>. It was edited by Paul
+d46 1
+a46 1
+ linkend="s1-xml-tags-screen"></xref>.
+@
+
+
+1.3
+log
+ at Exclude nxml chapter for now, and reorganize first chapter
+@
+text
+ at d1 1
+a1 1
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+@
+
+
+1.2
+log
+ at Now with 100% extra validation
+@
+text
+ at d28 2
+a29 2
+ in <filename>docs-xml-tags.xml</filename> and to add <xref
+ linkend="ch-emacs-nxml"></xref>.
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d1 9
+@
+
diff --git a/old-documentation-guide/en_US/documentation-guide.xml,v b/old-documentation-guide/en_US/documentation-guide.xml,v
new file mode 100644
index 0000000..918d74c
--- /dev/null
+++ b/old-documentation-guide/en_US/documentation-guide.xml,v
@@ -0,0 +1,345 @@
+head 1.10;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.9
+ LIVE:1.7;
+locks; strict;
+comment @# @;
+
+
+1.10
+date 2008.04.10.02.34.37; author pfrields; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2007.08.03.16.38.15; author pfrields; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2007.07.28.22.02.46; author pfrields; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2007.04.26.20.35.58; author pfrields; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.02.18.14.24.33; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2006.12.17.00.41.55; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2006.11.29.22.18.53; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2006.11.29.00.29.48; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.10
+log
+ at Add L10n chapter to DocGuide (#441190)
+@
+text
+@<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: documentation-guide.xml,v 1.9 2007/08/03 16:38:15 pfrields Exp $ -->
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<book id="documentation-guide" lang="en_US">
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="fdp-info.xml" />
+
+ <!-- INTRODUCTION -->
+ <xi:include href="intro.xml" xpointer="element(ch-intro)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- GETTINGFILES -->
+ <xi:include href="getting-files.xml" xpointer="element(ch-getting-files)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- HOWMODULESWORK -->
+ <xi:include href="module-struct.xml"
+ xpointer="element(ch-how-modules-work)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- GUIDELINES -->
+ <xi:include href="writing-guidelines.xml"
+ xpointer="element(ch-writing-guidelines)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- EMACS -->
+ <xi:include href="emacs.xml" xpointer="element(ch-emacs)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- EMACS-NXML -->
+ <!-- This chapter needs editing, so we're excluding it now. -->
+ <!--
+ <xi:include href="emacs-nxml.xml" xpointer="element(ch-emacs-nxml)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ -->
+
+ <!-- VIM -->
+ <xi:include href="vim.xml" xpointer="element(ch-vim)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- TAGS -->
+ <!-- Removing this chapter, since it isn't helpful beyond TDG.
+ <xi:include href="xml-tags.xml" xpointer="element(ch-xml-tags)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ -->
+
+ <!-- TUTORIAL -->
+ <xi:include href="tutorial.xml" xpointer="element(ch-tutorial)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- PUBLISHING -->
+ <xi:include href="publishing.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- CVS -->
+ <xi:include href="cvs-en_US.xml" xml:base="&FDPCOMMONDIR;/common"
+ xpointer="element(ch-cvs)" xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- L10N -->
+ <xi:include href="l10n.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <!-- ACKNOWLEDGMENTS -->
+ <xi:include href="acknowledgments.xml" xpointer="element(acknowledgments)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ <index id="generated-index"/>
+</book>
+@
+
+
+1.9
+log
+@* 0.3.1:
+ - Add new publishing chapter
+ - Include new chapter in book
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: documentation-guide.xml,v 1.8 2007/07/28 22:02:46 pfrields Exp $ -->
+a9 4
+<!ENTITY VERSION "0.2.6.3"> <!-- version for this document -->
+
+<!ENTITY DOCID "documentation-guide-&VERSION; (2005-09-18)"> <!-- change date here and VERSION entity everytime a change is made-->
+
+d66 4
+@
+
+
+1.8
+log
+ at Remove unnecessary chapter on XML tags. DocBook: The Definitive Guide
+has all the information we need about tags, and if there is specific
+usage needed beyond DocBook XML 4.4, we should only provide that here.
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: documentation-guide.xml,v 1.7 2007/04/26 20:35:58 pfrields Exp $ -->
+d62 4
+@
+
+
+1.7
+log
+ at Fix xinclude of common snippet. This is how common snippets should
+now be referenced, which means they will work no matter where the
+"docs-common" folder is located (current dir, parent, parent of
+parent...)
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: documentation-guide.xml,v 1.6 2007/02/18 14:24:33 pfrields Exp $ -->
+d53 1
+d56 1
+@
+
+
+1.6
+log
+ at Remove RH from this particular equation
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: documentation-guide.xml,v 1.5 2007/02/03 22:21:58 kwade Exp $ -->
+d61 1
+a61 1
+ <xi:include href="../../docs-common/common/cvs-en_US.xml"
+@
+
+
+1.5
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: documentation-guide.xml,v 1.4 2006/12/17 00:41:55 pfrields Exp $ -->
+d33 2
+a34 1
+ <xi:include href="rh-guidelines.xml" xpointer="element(ch-rh-guidelines)"
+@
+
+
+1.4
+log
+ at Ha, I know a lot more about why this book caused me so much pain when I first started learning DocBook and XML. Take that, crummy DOCTYPEs\!
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: documentation-guide.xml,v 1.3 2006/11/29 22:18:53 pfrields Exp $ -->
+d20 1
+a20 1
+ <xi:include href="docs-intro.xml" xpointer="element(ch-intro)"
+d24 1
+a24 1
+ <xi:include href="docs-getting-files.xml" xpointer="element(ch-getting-files)"
+d28 1
+a28 1
+ <xi:include href="docs-module-struct.xml"
+d33 1
+a33 1
+ <xi:include href="docs-rh-guidelines.xml" xpointer="element(ch-rh-guidelines)"
+d37 1
+a37 1
+ <xi:include href="docs-emacs.xml" xpointer="element(ch-emacs)"
+d43 1
+a43 1
+ <xi:include href="docs-emacs-nxml.xml" xpointer="element(ch-emacs-nxml)"
+d48 1
+a48 1
+ <xi:include href="docs-vim.xml" xpointer="element(ch-vim)"
+d52 1
+a52 1
+ <xi:include href="docs-xml-tags.xml" xpointer="element(ch-xml-tags)"
+d56 1
+a56 1
+ <xi:include href="docs-tutorial.xml" xpointer="element(ch-tutorial)"
+@
+
+
+1.3
+log
+ at Exclude nxml chapter for now, and reorganize first chapter
+@
+text
+ at d2 1
+a2 2
+<!-- $Id: documentation-guide.xml,v 1.2 2006/11/29 00:29:48 pfrields Exp $ -->
+<!-- breaks the build ... <?xml version="1.0" encoding="utf-8"?> -->
+@
+
+
+1.2
+log
+ at Now with 100% extra validation
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: documentation-guide.xml,v 1.1 2006/11/23 02:24:17 pfrields Exp $ -->
+d28 5
+d42 2
+a43 1
+ <!-- This chapter needs editing, but we can't exclude it now. -->
+d46 1
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d1 2
+a2 1
+<!-- $Id: documentation-guide-en.xml,v 1.23 2005/12/28 00:40:27 pfrields Exp $ -->
+d4 2
+a5 2
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+d17 2
+a18 34
+<book id="documentation-guide" lang="en">
+ <bookinfo>
+ <title>&FP; Documentation Guide</title>
+ <subtitle>Version &VERSION;</subtitle>
+ <copyright>
+ <year>2003</year>
+ <year>2004</year>
+ <year>2005</year>
+ <holder>&FORMAL-RHI;</holder>
+ <holder>Tammy Fox</holder>
+ <holder>Johnray Fuller</holder>
+ <holder>Sandra Moore</holder>
+ <holder>Paul W. Frields</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ <author>
+ <surname>Fuller</surname>
+ <firstname>Johnray</firstname>
+ </author>
+ <author>
+ <surname>Moore</surname>
+ <firstname>Sandra</firstname>
+ </author>
+ <author>
+ <surname>Frields</surname>
+ <firstname>Paul</firstname>
+ <othername role="mi">W.</othername>
+ </author>
+ </authorgroup>
+ </bookinfo>
+d37 3
+a39 3
+ <!-- This chapter needs editing, exclude it for now. -->
+ <!-- <xi:include href="docs-emacs-nxml.xml" xpointer="element(ch-emacs-nxml)"
+ xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+@
+
diff --git a/old-documentation-guide/en_US/emacs-nxml.xml,v b/old-documentation-guide/en_US/emacs-nxml.xml,v
new file mode 100644
index 0000000..971753c
--- /dev/null
+++ b/old-documentation-guide/en_US/emacs-nxml.xml,v
@@ -0,0 +1,416 @@
+head 1.2;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.2
+ LIVE:1.2;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2007.02.03.22.29.37; author kwade; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at updating all section usage and associated ID tags
+@
+text
+@<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+ <chapter id="ch-emacs-nxml">
+ <title>Emacs and nXML Mode</title>
+
+ <indexterm>
+ <primary>nXML</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>nXML mode</secondary>
+ </indexterm>
+
+ <para>
+ You can also use the nXML mode available for
+ <application>Emacs</application> to make it even easier to write in DocBook
+ XML format. nXML mode provides context-sensitive editing using completion,
+ real time validity error checking, syntax highlighting and indentation. All
+ you need to do is install an RPM!!
+ </para>
+
+ <note>
+ <title>Early stages</title>
+ <para>
+ Please be aware the nxml-mode for <application>Emacs</application> is
+ quite new, so there are a few things that the advanced user might notice
+ when using it with other documents types. If you keep an eye on the
+ mailing-list, you can keep up to date with these, as well as ask
+ questions. For more details, check out <xref
+ linkend="sn-emacs-nxml-readme"></xref>.
+ </para>
+ </note>
+
+
+ <section id="sn-nxml-rpm">
+ <title>Getting the nXML RPM</title>
+
+ <indexterm>
+ <primary>nXML</primary>
+ <secondary>RPM</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>nXML RPM</primary>
+ </indexterm>
+
+ <para>
+ To use nXML mode with emacs, you will need to install the nXML RPM
+ available from <ulink
+ url="http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/">Tim
+ Waugh's</ulink> website or the source from <ulink
+ url="http://www.thaiopensource.com/download/">http://www.thaiopensource.com/download/</ulink>.
+ The source requires a lot more work to setup, therefore we will only be
+ concentrating on the RPM version.
+ </para>
+
+ <para>
+ Information on where to get the source is available in <xref
+ linkend="sn-emacs-additional-resources"></xref>.
+ </para>
+
+ </section>
+
+ <section id="sn-nxml-examples">
+ <title>Examples</title>
+
+ <para>
+ Compared to PSGML mode there are only couple of commands that you need.
+ This speeds up writing with <application>Emacs</application> considerably,
+ which means you can concentrate more on the content of your article.
+ </para>
+
+ <section id="sn-nxml-commands">
+ <title>Commands</title>
+
+ <para>
+ To create a tag, type <userinput><</userinput> and then type the
+ keyword. To complete the keyword, press <command>Ctrl-Ret</command>,
+ then add the last <userinput>></userinput>. To close a tag, type
+ <userinput></</userinput>.
+ </para>
+
+ <important>
+ <title>Important</title>
+ <para>
+ When you open a document that doesn't have a DOCTYPE declaration at
+ the top of the file, you will get this message and tag completion
+ won't work because nXML will not know what format you are writing.
+ </para>
+ </important>
+
+ <para>
+ To load the schema, type <command>Ctrl-c</command>, then
+ <command>Ctrl-s</command> and navigate to
+ <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> and
+ load <filename>docbook.rnc</filename>. <application>Emacs</application>
+ will then prompt you to save it in the current working directory.
+ </para>
+
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ The commands already discussed are the only differences between
+ using <application>Emacs</application> with PSGML mode and
+ <application>Emacs</application> with nXML mode. You will still need
+ to use all the same commands as discussed in <xref
+ linkend="sn-emacs-basic-commands"></xref>.
+ </para>
+ </tip>
+ </section>
+ </section>
+
+ <section id="sn-emacs-nxml-additional-resources">
+ <title>Additional Resources</title>
+
+ <para> Additional Emacs and nXML references are available at the following
+ locations:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://www.thaiopensource.com/download/">http://www.thaiopensource.com/download/</ulink>
+ — <citetitle>Author's download area</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink>
+ — <citetitle>Emacs Quick Reference Guide</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Emacs reference card that comes with the
+ <filename>emacs</filename> package. You can print it out as a
+ reference. —
+ <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="sn-emacs-nxml-readme">
+ <title>nXML README File</title>
+
+ <note>
+ <title>Note</title>
+ <para>
+ This file can be found in the directory you extracted the source into,
+ or in
+ <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename>
+ if you installed the RPM.
+ </para>
+ </note>
+
+ <para>README file:</para>
+
+ <para>
+ This is a new major mode for GNU Emacs for editing XML documents. It
+ supports editing well-formed XML documents and also provides
+ schema-sensitive editing of XML documents using RELAX NG Compact Syntax.
+ </para>
+
+ <para>
+ To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs
+ version 20 will not work properly, nor will XEmacs. To get started, do the
+ following:
+ </para>
+
+ <screen>
+ <command>M-x load-file RET rng-auto.el RET</command>
+ </screen>
+
+ <para>
+ This defines the necessary autoloads. Now, visit a file containing an XML
+ document, and do the following:
+ </para>
+
+ <screen> <command>M-x nxml-mode</command>
+ </screen>
+
+ <para>
+ Now do
+ </para>
+
+ <screen>
+ <command>C-h m</command>
+ </screen>
+
+ <para>
+ For information on how to use nxml-mode. The beginnings of a manual are
+ in nxml-mode.info. You can read this using:
+ </para>
+
+ <screen>
+ <command>C-u M-x info RET nxml-mode.info RET</command>
+ </screen>
+
+ <para>
+ It's also installed as an entry at the end of the top-level info
+ directory. So you can read it with <command>C-h i</command> as usual.
+ </para>
+
+ <para>
+ You can use <filename>test.valid.xml</filename> and
+ <filename>test.invalid.xml</filename> as examples of valid and invalid XML
+ documents.
+ </para>
+
+ <para>
+ To get things automatically loaded each time you start Emacs, add:
+ </para>
+
+ <screen>
+ <computeroutput> (load "~/nxml-mode-200YMMDD/rng-auto.el")
+ </computeroutput>
+ </screen>
+
+ <para>
+ to your <filename>.emacs</filename>, where
+ <computeroutput>~/nxml-mode-200YMMDD</computeroutput> is the directory
+ containing the <filename>.elc</filename> files. Note that
+ <filename>rng-auto.el</filename> does not load all of the nxml-mode code;
+ it merely sets things up so that all the features of nxml-mode will be
+ autoloaded properly. You should not try to autoload
+ <filename>rng-auto.el</filename> itself.
+ </para>
+
+ <para>
+ To use nxml-mode automatically for files with an extension of
+ <filename>xml</filename>, <filename>xsl</filename>,
+ <filename>rng</filename> or <filename>xhtml</filename>, add the following
+ to your <filename>.emacs</filename> file:
+ </para>
+
+ <screen>
+ <computeroutput> (setq auto-mode-alist (cons
+ '("\\.\\(xml\\|xsl\\|rng\\|xhtml\\)\\'" . nxml-mode) auto-mode-alist))
+ </computeroutput>
+ </screen>
+
+ <para>
+ If you edit XML using iso-8859-N encodings other than iso-8859-1 and you
+ are running Emacs 21.3 or later, then I recommend enabling
+ unify-8859-on-decoding-mode, by adding the following to your
+ <filename>.emacs</filename> file:
+ </para>
+
+ <screen>
+ <computeroutput>(unify-8859-on-decoding-mode)</computeroutput>
+ </screen>
+
+ <para>
+ To get validation and schema-sensitive editing, you need a RELAX NG
+ Compact Syntax (RNC) schema for you document. The schema directory
+ includes some schemas for popular document types.
+ </para>
+
+ <para>
+ For more on RELAX NG, refer to <ulink
+ url="http://relaxng.org/">http://relaxng.org/</ulink>.
+ </para>
+
+ <para>
+ For a tutorial on RELAX NG Compact Syntax, refer to <ulink
+ url="http://relaxng.org/compact-tutorial.html">http://relaxng.org/compact-tutorial.html</ulink>
+ </para>
+
+ <para>
+ For automatically creating RNC schemas, I recommend my Trang program:
+ <ulink
+ url="http://www.thaiopensource.com/relaxng/trang.html">http://eee.thaiopensource.com/relaxng/trang.html"</ulink>
+ </para>
+
+ <para>
+ You can use this to
+
+<itemizedlist>
+ <listitem>
+ <para>
+ Infer an RNC schema from an instance document
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Convert a DTD to an RNC schema
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Convert a RELAX NG XML syntax schema to an RNC schema
+ </para>
+ </listitem>
+</itemizedlist>
+ </para>
+
+ <para>
+ To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can
+ also use the XSLT stylesheet from <ulink
+ url="http://www.pantor.com/download.html">http://www.pantor.com/download.html"</ulink>.
+ </para>
+
+ <para>
+ To convert a W3C XML Schema to an RNC schema, you need first to convert it
+ to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built
+ on top of MSV). Refer to <ulink
+ url="https://msv.dev.java.net/">https://www.dev.java.net/</ulink>.
+ </para>
+
+ <para>
+ The file <filename>NEWS</filename> describes recent changes.
+ </para>
+
+ <para>
+ Please use the list <ulink
+ url="http://groups.yahoo.com/group/emacs-nxml-mode/">http://groups.yahoo.com/group/emacs-nxml-mode</ulink>
+ for bug reports, discussion. I will announce all new versions there.
+ </para>
+
+ <para>
+ James Clark
+ </para>
+ <para>
+ jjc@@thaiopensource.com
+ </para>
+ </section>
+ </chapter>
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d42 1
+a42 1
+ linkend="s1-emacs-nxml-readme"></xref>.
+d47 1
+a47 1
+ <sect1 id="s1-nxml-rpm">
+d71 1
+a71 1
+ linkend="s1-emacs-additional-resources"></xref>.
+d74 1
+a74 1
+ </sect1>
+d76 1
+a76 1
+ <sect1 id="s1-nxml-examples">
+d85 1
+a85 1
+ <sect2 id="s2-nxml-commands">
+d120 1
+a120 1
+ linkend="s1-emacs-basic-commands"></xref>.
+d123 2
+a124 2
+ </sect2>
+ </sect1>
+d126 1
+a126 1
+ <sect1 id="s1-emacs-nxml-additional-resources">
+d154 1
+a154 1
+ </sect1>
+d156 1
+a156 1
+ <sect1 id="s1-emacs-nxml-readme">
+d339 1
+a339 1
+ </sect1>
+@
+
diff --git a/old-documentation-guide/en_US/emacs.xml,v b/old-documentation-guide/en_US/emacs.xml,v
new file mode 100644
index 0000000..4e72a20
--- /dev/null
+++ b/old-documentation-guide/en_US/emacs.xml,v
@@ -0,0 +1,1519 @@
+head 1.9;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.9
+ LIVE:1.5;
+locks; strict;
+comment @# @;
+
+
+1.9
+date 2007.08.02.02.33.21; author pfrields; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2007.07.01.18.17.29; author pfrields; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2007.07.01.17.49.52; author pfrields; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.07.01.17.47.42; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.06.23.04.37.29; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.03.08.03.00.44; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.02.06.01.09.59; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.02.03.22.29.37; author kwade; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.9
+log
+ at Correct/simplify keycombo
+@
+text
+@<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: emacs.xml,v 1.8 2007/07/01 18:17:29 pfrields Exp $ -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<chapter id="ch-emacs">
+ <title>Emacs and PSGML Mode</title>
+
+ <indexterm>
+ <primary>PSGML</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>PSGML mode</secondary>
+ </indexterm>
+
+ <para>
+ You can use the PSGML mode available for Emacs to make it easier to
+ write in XML format. PSGML mode provides syntax-highlighting, tag
+ completion, and more.
+ </para>
+
+ <section id="sn-installing-psgml">
+ <title>Installing PSGML</title>
+ <para>To install PSGML, use the <command>yum</command> command:</para>
+ <screen><userinput>yum install psgml</userinput></screen>
+ </section>
+ <section id="sn-emacs-file">
+ <title>Setting Up Your <filename>.emacs</filename> File</title>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>configuration file</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.emacs</filename></primary>
+ </indexterm>
+
+ <para>
+ For Emacs to parse your DocBook documents correctly, you must have
+ a <filename>.emacs</filename> file. Cut and paste the following
+ into your existing <filename>.emacs</filename> file or create a
+ new one that contains the following lines:
+ </para>
+ <screen><![CDATA[;; turn on auto-fill in `text-mode' and derived modes
+;;(mail, news, etc)
+(add-hook 'text-mode-hook 'turn-on-auto-fill)
+
+;;
+;;MODES
+;;
+
+(setq auto-mode-alist (cons '("\\.sgml$" . sgml-mode) auto-mode-alist))
+(setq auto-mode-alist (cons '("\\.sgm$" . sgml-mode) auto-mode-alist))
+
+;;
+;;XML!!
+;;
+;;#############################################################
+
+;;
+;;PSGML mode stuff
+;;
+
+(autoload 'sgml-mode "psgml" "My Most Major Mode" t)
+
+(setq sgml-mode-hook '(lambda () "Defaults for XML mode." (turn-on-auto-fill)
+(setq fill-column 80)))
+
+(defun My-XML-keymap ()
+ (local-set-key [(alt i)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt l)]
+ '(lambda ()
+ (interactive)
+ (sgml-insert-element 'list)
+ (sgml-insert-element 'item)
+ (sgml-indent-line)))
+ (local-set-key [(alt p)]
+ '(lambda ()
+ (interactive)
+ (sgml-indent-line)
+ (sgml-insert-element 'para)
+ (sgml-indent-line)))
+ (local-set-key [(alt -)]
+ '(lambda ()
+ (interactive)
+ (insert "—"))))
+
+(add-hook 'sgml-mode-hook 'My-XML-keymap)
+
+;;
+;; Fix up indentation of data...
+;;
+
+(setq-default sgml-indent-data t)
+
+;;
+;; XML markup faces.
+;;
+
+(setq-default sgml-set-face t)
+
+
+(make-face 'sgml-comment-face)
+(make-face 'sgml-doctype-face)
+(make-face 'sgml-end-tag-face)
+(make-face 'sgml-entity-face)
+(make-face 'sgml-ignored-face)
+(make-face 'sgml-ms-end-face)
+(make-face 'sgml-ms-start-face)
+(make-face 'sgml-pi-face)
+(make-face 'sgml-sgml-face)
+(make-face 'sgml-short-ref-face)
+(make-face 'sgml-start-tag-face)
+
+(set-face-foreground 'sgml-comment-face "maroon")
+(set-face-foreground 'sgml-doctype-face "dark green")
+(set-face-foreground 'sgml-end-tag-face "blue2")
+(set-face-foreground 'sgml-entity-face "red2")
+(set-face-foreground 'sgml-ignored-face "maroon")
+(set-face-background 'sgml-ignored-face "gray90")
+(set-face-foreground 'sgml-ms-end-face "maroon")
+(set-face-foreground 'sgml-ms-start-face "maroon")
+(set-face-foreground 'sgml-pi-face "maroon")
+(set-face-foreground 'sgml-sgml-face "maroon")
+(set-face-foreground 'sgml-short-ref-face "goldenrod")
+(set-face-foreground 'sgml-start-tag-face "blue2")
+
+(setq-default sgml-markup-faces
+ '((comment . sgml-comment-face)
+ (doctype . sgml-doctype-face)
+ (end-tag . sgml-end-tag-face)
+ (entity . sgml-entity-face)
+ (ignored . sgml-ignored-face)
+ (ms-end . sgml-ms-end-face)
+ (ms-start . sgml-ms-start-face)
+ (pi . sgml-pi-face)
+ (sgml . sgml-sgml-face)
+ (short-ref . sgml-short-ref-face)
+ (start-tag . sgml-start-tag-face)))
+
+
+(defun docbook-mode ()
+ (sgml-mode)
+ )
+
+
+
+;;
+;;END XML STUFF
+;;
+;;##################################################################
+
+;PO mode stuff
+
+(setq auto-mode-alist
+ (cons '("\\.pox?\\'" . po-mode) auto-mode-alist))
+(autoload 'po-mode "po-mode")
+
+
+ (global-set-key [(f1)] (lambda () (interactive) (manual-
+ entry (current-word))))]]></screen>
+
+ <para>
+ If you have a wheel mouse and are using Emacs version 21, you can
+ add the following to your <filename>.emacs</filename> file so your
+ wheel will work in <application>Emacs</application>:
+ </para>
+
+ <screen><![CDATA[;; Enable wheelmouse support by default for emacs 21
+(cond (window-system
+(mwheel-install)
+))]]></screen>
+
+ <para>
+ If you are using the older version 20 of
+ <application>Emacs</application>, add the following instead:
+ </para>
+
+ <screen><![CDATA[;; Enable wheelmouse support by default
+(require 'mwheel)]]></screen>
+
+<!-- bug #125757 in NEEDINFO state
+ <para>
+ If you have a mouse, you can also add the following. It adds popup menus
+ when the cursor is either on a start tag or in a region where elements
+ are allowed.
+ </para>
+
+<screen>
+<computeroutput>
+;; Mouse Bindings: right-click to generate context-aware
+;; elements/attributes popup menu.
+(define-key sgml-mode-map [mouse-3] 'sgml-tags-menu)
+</computeroutput>
+</screen>
+
+-->
+
+ </section>
+
+
+ <section id="sn-emacs-colors">
+ <title>Customizing Emacs</title>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>customizing</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.Xresources</filename></primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>colors</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>font</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>geometry</secondary>
+ </indexterm>
+
+ <para>
+ The colors, font, and geometry (default size of window) for Emacs
+ in your <filename>~/.Xresources</filename> file. The format for
+ the settings is <userinput>emacs.keyword:value</userinput>.
+ </para>
+
+ <para>
+ The following is a sample <filename>~/.Xresources</filename> file.
+ </para>
+ <note>
+ <title>Note</title>
+ <para>If you have other settings in your
+ <filename>~/.Xresources</filename>, add the following to the end
+ of the file.
+ </para>
+ <screen><![CDATA[emacs.background: light gray
+emacs.foreground: black
+emacs.pointerColor: blue
+emacs.cursorColor: blue
+emacs.bitmapIcon: on
+emacs.font: fixed
+emacs.geometry: 90x25]]></screen>
+ </note>
+ <para>
+ After modifying this file, execute the following command:
+ </para>
+ <screen><command>xrdb -merge ~/.Xresources</command></screen>
+ <para>
+ Then restart <application>Emacs</application> to apply the
+ changes.
+ </para>
+ </section>
+
+<!-- This is not required if your DTD is correct. [PWF 2007-06-23]
+
+ <section id="sn-emacs-cedfile">
+ <title>Create Recompiled DTD Subset</title>
+
+ <para>
+ Emacs will perform syntax highlighting and indent correctly on
+ DocBook XML files if you provide it with the proper Document Type
+ Declarations (DTD) file. These two features will make your XML file
+ look pretty and help you spot errors.
+ </para>
+
+ <para>
+ To create a loadable Parsed DTD file:
+ <orderedlist>
+ <listitem>
+ <para>Find the parent file for the group of DocBook files. You will
+ recognize this file by the header <filename><!DOCTYPE article
+ PUBLIC "-//OASIS//DTD DocBook V4.1//EN"</filename>. An easy way
+ to find this parent file is to use the command <command>grep
+ DocBook *.xml</command>. Once you find the parent file, open it
+ in Emacs with the command <command>emacs
+ <replaceable><parentfile></replaceable>.xml</command> (where
+ <replaceable><parentfile></replaceable>.xml is the parent
+ file you found.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Choose <command>DTD -> Parse DTD</command> from the pulldown
+ menu.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>You will know the parsing is finished when you see the message
+ <computeroutput>Fontifying...done</computeroutput> at the bottom
+ of your screen. Save the parsed DTD to a file by choosing
+ <command>DTD -> Save Parsed DTD</command> from the pulldown menu.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Press <keycap>Enter</keycap> to save the file to the default
+ filename or rename the file keeping the <filename>.ced</filename>
+ extension. It can be useful to name it something generic such as
+ <filename>docbook.ced</filename> so you can refer to it when
+ opening all DocBook files. This file can also be copied from
+ directory to directory to be loaded.
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </para>
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ You can also use the Emacs command <command>Meta-x
+ sgml-parse-prolog</command> to parse the file, and then use the
+ command <command>Meta-x sgml-save-dtd</command> to save the parsed DTD
+ to a <filename>.ced</filename> file.
+ </para>
+ </tip>
+
+ </section>
+
+ <section id="sn-emacs-loadced">
+ <title>Load the Parsed DTD</title>
+
+ <para>
+ Now that you have saved the DTD settings, you can load the
+ <filename>.ced</filename> file and see the syntax highlighting for your
+ <filename>.sgml</filename> files.
+ </para>
+
+ <para>
+ To load a parsed DTD file:
+ <orderedlist>
+ <listitem>
+ <para>Open an XML file in Emacs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Choose <command>DTD -> Load DTD</command> from the pulldown menu
+ and choose the file you saved from the previous step. For
+ instance, choose <filename>docbook.ced</filename>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>You will know it is finished when you see the message
+ <computeroutput>Fontifying...done</computeroutput> at the bottom
+ of your screen. Loading the parsed DTD might take a long time.
+ You can start editing the file before it finishes.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ </para>
+
+ <tip>
+ <title>Tip</title>
+ <para>
+ You can also use the Emacs command <command>Meta-x
+ sgml-load-dtd</command> to load the parsed DTD.
+ </para>
+ </tip>
+
+ </section>
+-->
+
+ <section id="sn-emacs-basic-commands">
+ <title>Basic Emacs Commands</title>
+
+ <para>
+ The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap>
+ key.
+ </para>
+
+ <segmentedlist id="tb-emacs-commands">
+ <title>Emacs Commands</title>
+ <segtitle>Shortcut</segtitle>
+ <segtitle>Description</segtitle>
+ <seglistitem>
+ <seg><keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>c</keycap>
+ </keycombo>,
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>p</keycap>
+ </keycombo></seg>
+ <seg>Parse DTD</seg>
+ </seglistitem>
+ <!-- These commands not necessary with proper validation [PWF
+ 2007-07-01]...
+ <seglistitem>
+ <seg><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-save-dtd, <keycap>Enter</keycap></seg>
+ <seg>Save the Parse DTD</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo> <keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-load-dtd, <keycap>Enter</keycap></seg>
+ <seg>Load DTD</seg>
+ </seglistitem> -->
+ <seglistitem>
+ <seg><keycombo> <keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap>,</keycap></keycombo>, <keycap>Tab</keycap></seg>
+ <seg>Display list of valid tags</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap>,</keycap> </keycombo>, type beginning of tag,
+ <keycap>Tab</keycap></seg>
+ <seg>Complete the tag</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap> <keycap>g</keycap>
+ </keycombo></seg>
+ <seg>Cancel a command in the minibuffer</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycap>/</keycap></seg>
+ <seg>Close tag</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap> <keycap>a</keycap>
+ </keycombo></seg>
+ <seg>Move cursor to beginning of line</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap><keycap>e</keycap>
+ </keycombo></seg>
+ <seg>Move cursor to the end of the line</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap><keycap>Home</keycap>
+ </keycombo></seg>
+ <seg>Move cursor to the beginning of the file</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap><keycap>End</keycap>
+ </keycombo></seg>
+ <seg>Move cursor to the end of the file</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap><keycap>k</keycap>
+ </keycombo></seg>
+ <seg>Cut line</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap> <keycap>y</keycap>
+ </keycombo></seg>
+ <seg>Paste line</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap> <keycap>s</keycap>
+ </keycombo></seg>
+ <seg>Search forward in the file</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap><keycap>r</keycap>
+ </keycombo></seg>
+ <seg>Search backwards in the file</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Meta</keycap><keycap>$</keycap>
+ </keycombo></seg>
+ <seg>Check spelling of current word</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-word, <keycap>Enter</keycap></seg>
+ <seg>Check spelling of current word</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-buffer, <keycap>Enter</keycap></seg>
+ <seg>Check spelling of current buffer</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap>
+ </keycombo></seg>
+ <seg>Open file</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap>
+ </keycombo></seg>
+ <seg>Save file</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></seg>
+ <seg>Exit <application>Emacs</application> and prompt to save
+ files if necessary</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Meta</keycap> <keycap>q</keycap>
+ </keycombo></seg>
+ <seg>Fill paragraph</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>a</keycap>
+ </keycombo></seg>
+ <seg>Edit attributes for a tag (for example, you can edit the
+ <computeroutput>url</computeroutput> attribute of the
+ <computeroutput>ulink</computeroutput> tag)</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>,
+ <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></seg>
+ <seg>Exit edit attributes</seg>
+ </seglistitem>
+ </segmentedlist>
+ </section>
+
+ <section id="sn-emacs-examples">
+ <title>Examples</title>
+
+ <para>
+ The table or reference card of Emacs and PSGML commands can be
+ confusing for beginners. This section provides some examples of
+ how to use them.
+ </para>
+
+ <section id="sn-emacs-tag-completion">
+ <title>Tag Completion</title>
+
+ <note>
+ <title>Note</title>
+ <para>This section assumes that you have already parsed the DTD
+ file.</para>
+ </note>
+
+ <para>
+ To avoid having to type a tag repeatedly, use the key
+ combination <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed
+ by <keycap><</keycap>. At the bottom of the
+ <application>Emacs</application> window, the following prompt
+ appears:
+ </para>
+ <screen><prompt>Tag: <</prompt></screen>
+
+ <para>
+ To view a list of available tags, use either the
+ <keycap>Tab</keycap> or <keycap>?</keycap>. If you know the
+ first few letters of a tag, enter them, followed by
+ <keycap>Tab</keycap>. If the letters uniquely identify a tag,
+ that tag appears. If more than one completion exists, a
+ complete list of possible tags appears.
+ </para>
+
+ <para>
+ If you hit <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>c</keycap>
+ </keycombo>, <keycap><</keycap>, <keycap>k</keycap>, a prompt
+ appears similar to the example below:
+ </para>
+
+ <screen><![CDATA[Click mouse-2 on a completion to select it.
+In this buffer, type RET to select the completion near point.
+
+Possible completions are:
+<keycap> <keycode>
+<keycombo> <keysym>]]></screen>
+
+ </section>
+ <section id="sn-emacs-tag-closing">
+ <title>Tag Closure</title>
+
+ <para>
+ After you open a tag, you must close it. The easiest way to
+ close an open tag is to use the key sequence
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>c</keycap>
+ </keycombo>, <keycap>/</keycap>. This sequence closes the most
+ recently opened tag.
+ </para>
+ </section>
+
+ <section id="sn-emacs-other">
+ <title>Other Emacs Tasks</title>
+
+ <section id="sn-emacs-other-one-window">
+ <title>Working with One Window</title>
+ <para>Sometimes in <application>Emacs</application>, the window
+ becomes split, with tags completions or other text in an
+ alternate window. To return to a single window, use the key
+ sequence <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>x</keycap>
+ </keycombo>, <keycap>1</keycap>.</para>
+ </section>
+
+ <section id="sn-emacs-other-save">
+ <title>Saving Work</title>
+ <para>To save your work, use the key sequence
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>x</keycap>
+ </keycombo>, <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>s</keycap>
+ </keycombo>.</para>
+ </section>
+
+ <section id="sn-emacs-other-clearquit">
+ <title>The "Clear/Quit" Command</title>
+ <para>If the tag completion process becomes unwieldy or
+ confusing, use the keysequence <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>g</keycap>
+ </keycombo> to exit back to the text.
+ <application>Emacs</application> clears any prompts and returns
+ to the buffer text.</para>
+ </section>
+
+ <section id="sn-emacs-other-open">
+ <title>Opening a new file</title>
+ <para>To open a new file, use the key sequence
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>x</keycap>
+ </keycombo>, <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>f</keycap>
+ </keycombo>. A prompt appears at the bottom of the
+ <application>Emacs</application> window. Enter the file name,
+ using <keycap>Tab</keycap> completion if desired, of the file
+ you wish to open.</para>
+ </section>
+
+ <section id="sn-emacs-other-close">
+ <title>Closing <application>Emacs</application></title>
+ <para>To close <application>Emacs</application> use the key
+ sequence
+ <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>x</keycap>
+ </keycombo>, <keycombo>
+ <keycap>Ctrl</keycap>
+ <keycap>c</keycap>
+ </keycombo>. If you have not saved your work,
+ <application>Emacs</application> prompts you to save any
+ changed files.</para>
+ </section>
+
+ </section>
+
+ </section>
+
+ <section id="sn-emacs-additional-resources">
+ <title>Additional Resources</title>
+
+ <para> Additional Emacs and PSGML references are available at the
+ following locations:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html"/>
+ — <citetitle>Emacs Quick Reference Guide</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Emacs reference card that comes with the
+ <filename>emacs</filename> package. You can print it out as a
+ reference. —
+ <filename>/usr/share/emacs/<replaceable>version</replaceable>/etc/refcard.ps</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Read <citetitle>Editing XML with Emacs and
+ PSGML</citetitle> in
+ <filename>/usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://www.snee.com/bob/sgmlfree/psgmqref.html"/>
+ — <citetitle>Emacs/PSGML Quick Reference</citetitle> is
+ a reference table of Emacs commands for PSGML mode.
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://www.snee.com/bob/sgmlfree/emcspsgm.html"/>
+ — <citetitle>PSGML Tricks</citetitle></para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+ </chapter>
+
+
+
+
+
+
+
+
+
+@
+
+
+1.8
+log
+ at Clean up the chapter but good!
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: emacs.xml,v 1.7 2007/07/01 17:49:52 pfrields Exp $ -->
+d408 7
+a414 2
+ <keycap>Meta</keycap><keycap>x</keycap></keycombo>
+ sgml-parse-prolog, <keycap>Enter</keycap></seg>
+@
+
+
+1.7
+log
+ at Fix admonition and a bit of dodgy language. I'm pretty sure this whole
+section needs to be gone over with a fine-toothed comb.
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: emacs.xml,v 1.6 2007/07/01 17:47:42 pfrields Exp $ -->
+d12 2
+a13 10
+ <chapter id="ch-emacs">
+ <title>Emacs and PSGML Mode</title>
+
+ <indexterm>
+ <primary>PSGML</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ </indexterm>
+d15 18
+a32 10
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>PSGML mode</secondary>
+ </indexterm>
+
+ <para>
+ You can use the PSGML mode available for Emacs to make it easier to write
+ in XML format. PSGML mode provides syntax-highlighting, tag completion,
+ and more.
+ </para>
+d39 2
+a40 2
+ <section id="sn-emacs-file">
+ <title>Setting Up Your <filename>.emacs</filename> File</title>
+d42 4
+a45 8
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>configuration file</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.emacs</filename></primary>
+ </indexterm>
+d47 11
+a57 8
+ <para>
+ For Emacs to parse your DocBook documents correctly, you must have a
+ <filename>.emacs</filename> file. Cut and paste the following into your
+ existing <filename>.emacs</filename> file or create a new one that
+ contains the following lines:
+
+ <screen><computeroutput><![CDATA[
+;; turn on auto-fill in `text-mode' and derived modes
+d179 1
+a179 4
+ entry (current-word))))
+]]></computeroutput></screen>
+
+ </para>
+d182 3
+a184 3
+ If you have a wheel mouse and are using Emacs version 21, you can add the
+ following to your <filename>.emacs</filename> file so your wheel will work
+ in <application>Emacs</application>:
+d187 1
+a187 2
+ <screen><computeroutput><![CDATA[
+;; Enable wheelmouse support by default for emacs 21
+d190 1
+a190 2
+))
+]]></computeroutput></screen>
+d192 4
+a195 4
+ <para>
+ If you are using the older version 20 of
+ <application>Emacs</application>, add the following instead:
+ </para>
+d197 2
+a198 4
+ <screen><computeroutput><![CDATA[
+;; Enable wheelmouse support by default
+(require 'mwheel)
+]]></computeroutput></screen>
+d217 1
+a217 1
+ </section>
+d220 2
+a221 2
+ <section id="sn-emacs-colors">
+ <title>Customizing Emacs</title>
+d223 4
+a226 23
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>customizing</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><filename>.Xresources</filename></primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>colors</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>font</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Emacs</primary>
+ <secondary>geometry</secondary>
+ </indexterm>
+d228 24
+a251 5
+ <para>
+ The colors, font, and geometry (default size of window) for Emacs in your
+ <filename>~/.Xresources</filename> file. The format for the settings is
+ <computeroutput>emacs.keyword:value</computeroutput>
+ </para>
+d253 8
+a260 2
+ <para>
+ The following is a sample <filename>~/.Xresources</filename> file.
+d262 1
+a262 10
+ <note>
+ <title>Note</title>
+ <para>If you have other settings in your
+ <filename>~/.Xresources</filename>, add the following to the end of
+ the file.
+ </para>
+ </note>
+
+ <screen><userinput><![CDATA[
+emacs.background: light gray
+d268 5
+a272 7
+emacs.geometry: 90x25
+]]></userinput></screen>
+
+ <para>
+ After modifying this file, you must execute the command
+ </para>
+
+d274 5
+a278 6
+ <para>
+ and restart <application>Emacs</application> for the changes to take
+ place.
+ </para>
+
+ </section>
+d394 2
+a395 2
+ <section id="sn-emacs-basic-commands">
+ <title>Basic Emacs Commands</title>
+d397 4
+a400 3
+ <para>
+ The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key.
+ </para>
+d402 1
+a402 1
+ <segmentedlist id="tb-emacs-commands">
+d541 5
+a545 1
+ </segmentedlist>
+d547 5
+a551 1
+ </section>
+d553 8
+a560 2
+ <section id="sn-emacs-examples">
+ <title>Examples</title>
+d563 5
+a567 2
+ The table or reference card of Emacs and PSGML commands can be confusing
+ for beginners. This section provides some examples of how to use them.
+d569 1
+d571 7
+a577 26
+ <section id="sn-emacs-tag-completion">
+ <title>Tag Completion</title>
+
+ <note>
+ <title>Note</title>
+ <para>This section assumes that you have already parsed the
+ DTD file.</para>
+ </note>
+
+ <para>
+ Instead of typing a tag each time you need to use it, use
+ the key combination <keycap>Ctrl</keycap>-<keycap>c</keycap>,
+ followed by <keycap><</keycap>. At the bottom of the
+ <application>Emacs</application> window, the following prompt
+ appears:
+ </para>
+<screen>
+<computeroutput>Tag: <</computeroutput>
+</screen>
+
+ <para>
+ To view a list of available tags, use either the <keycap>Tab</keycap>
+ or <keycap>?</keycap>. Or, if you know the first few letters of a tag,
+ you can enter them followed by <keycap>Tab</keycap> for a complete
+ list of available tags beginning with those letters or for a tag
+ completion.
+a579 7
+ <para>
+ Try the following: Type <keycap>Ctrl</keycap>-<keycap>c</keycap>
+ followed by <keycap><</keycap>. Then enter the letter
+ <keycap>k</keycap>, followed by <keycap>Tab</keycap>. You may have to
+ use the <keycap>Tab</keycap> key several times to get a complete list.
+ </para>
+
+d581 5
+a585 1
+ The output should look similar to the example below:
+d588 1
+a588 3
+<screen>
+<computeroutput>
+Click mouse-2 on a completion to select it.
+d592 2
+a593 4
+<keycap> <keycode>
+<keycombo> <keysym>
+</computeroutput>
+</screen>
+d595 3
+a597 3
+ </section>
+ <section id="sn-emacs-tag-closing">
+ <title>Tag Closure</title>
+d599 8
+a606 5
+ <para>
+ Once you have started the tag of choice, you must close it. The easiest
+ way to close an open tag is to use the keycombo
+ <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by
+ <keycap>/</keycap>. This will close the closest open tag you have.
+d608 1
+a608 2
+
+ </section>
+d610 2
+a611 2
+ <section id="sn-emacs-other">
+ <title>Other Emacs Tasks</title>
+d613 10
+a622 8
+ <para>
+ <guilabel>Working with one window</guilabel>: Sometimes in
+ <application>Emacs</application> the window becomes split (with tags
+ completions or other text in the bottom window). The easiest way to
+ get it back so that only your XML and text appear on one screen is to
+ use the keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap>, followed by
+ <keycap>1</keycap>.
+ </para>
+d624 11
+a634 5
+ <para>
+ <guilabel>Saving your work</guilabel>: To save your work, use the
+ following keycombo, <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>s</keycap>.
+ </para>
+d636 10
+a645 8
+ <para>
+ <guilabel>The "clear/quit" command</guilabel>: I have found on some
+ occasions that I have gotten too far into the tag completion process and
+ need to just exit back out to my text. The easiest way to do this is the
+ keycombo <keycap>Ctrl</keycap>-<keycap>g</keycap>. This command quits
+ what you have been doing within the file, without quitting the file
+ itself.
+ </para>
+d647 14
+a660 8
+ <para>
+ <guilabel>Opening a new file</guilabel>: To open a new file, use the
+ keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>f</keycap>. At the bottom of the emacs
+ window, you will be able to enter in the file name (using
+ <keycap>Tab</keycap> completion if needed) of the file you wish to
+ open.
+ </para>
+d662 13
+a674 8
+ <para>
+ <guilabel>Closing emacs</guilabel>: The easiest way to close
+ <application>emacs</application> is to use the keycombo
+ <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by
+ <keycap>Ctrl</keycap>-<keycap>c</keycap>. If you have not saved your work,
+ it will prompt you to save the file, otherwise it will just quit the
+ current emacs session you have been working with.
+ </para>
+d676 2
+d679 1
+a679 1
+ </section>
+d681 2
+a682 2
+ <section id="sn-emacs-additional-resources">
+ <title>Additional Resources</title>
+d684 3
+a686 3
+ <para> Additional Emacs and PSGML references are available at the
+ following locations:
+ </para>
+d688 4
+a691 4
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://wks.uts.ohio-state.edu/unix_course/intro-135.html">http://wks.uts.ohio-state.edu/unix_course/intro-135.html</ulink>
+d693 4
+a696 3
+ </para>
+ </listitem>
+ <listitem> <para>Emacs reference card that comes with the
+d699 22
+a720 20
+ <filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Read <citetitle>Editing XML with Emacs and PSGML</citetitle>
+ in <filename>/usr/share/doc/psgml-<replaceable><version></replaceable>/psgml.ps</filename>. </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://www.snee.com/bob/sgmlfree/psgmqref.html">http://www.snee.com/bob/sgmlfree/psgmqref.html</ulink>
+ — <citetitle>Emacs/PSGML Quick Reference</citetitle> is a
+ reference table of Emacs commands for PSGML mode.
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink
+ url="http://www.snee.com/bob/sgmlfree/emcspsgm.html">http://www.snee.com/bob/sgmlfree/emcspsgm.html</ulink>
+ — <citetitle>PSGML Tricks</citetitle></para>
+ </listitem>
+ </itemizedlist>
+@
+
+
+1.6
+log
+ at - Fix some keycombos
+- Manual DTD parsing not needed when you use the right prolog
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: emacs.xml,v 1.5 2007/06/23 04:37:29 pfrields Exp $ -->
+d571 2
+a572 3
+ <para>This section assumes that you have already loaded the DTD file
+ (<filename>.ced</filename>).
+ </para>
+d579 2
+a580 1
+ <application>Emacs</application> window, you will see:
+@
+
+
+1.5
+log
+ at Remove errant secitons. You don't need to parse and load DTD subsets
+if your DTD is correct for DocBook XML.
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: emacs.xml,v 1.4 2007/03/08 03:00:44 pfrields Exp $ -->
+d425 2
+d436 1
+a436 1
+ </seglistitem>
+d440 1
+a440 1
+ <keycap></keycap></keycombo>, <keycap>Tab</keycap></seg>
+d446 1
+a446 1
+ <keycap></keycap> </keycombo>, type beginning of tag,
+@
+
+
+1.4
+log
+ at Use segmentedlist instead of tables -- separating appearance from content, yay DocBook!
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: emacs.xml,v 1.3 2007/02/06 01:09:59 pfrields Exp $ -->
+d293 2
+d406 1
+@
+
+
+1.3
+log
+ at - Add XML header
+- Add section for installing PSGML
+- Add CDATA tags to protect content that might be entity-expanded
+@
+text
+ at d2 1
+a2 1
+<!-- $Id: emacs.xml,v 1.2 2007/02/03 22:29:37 kwade Exp $ -->
+d412 132
+a543 141
+ <table frame="all" rowsep="1" colsep="1" id="tb-emacs-commands">
+ <title>Emacs Commands</title>
+ <tgroup rowsep="1" colsep="1" cols="2">
+ <colspec colnum="1" colname="shortcut" colwidth="170"/>
+ <colspec colnum="2" colname="description" colwidth="300"/>
+
+ <thead>
+ <row>
+ <entry rowsep="1" colsep="1">Shortcut</entry>
+ <entry rowsep="1" colsep="1">Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry rowsep="1" colsep="1"><keycombo>
+ <keycap>Meta</keycap><keycap>x</keycap></keycombo>
+ sgml-parse-prolog, <keycap>Enter</keycap></entry>
+ <entry>Parse DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-save-dtd, <keycap>Enter</keycap></entry>
+ <entry>Save the Parse DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo> <keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo>sgml-load-dtd, <keycap>Enter</keycap></entry>
+ <entry>Load DTD</entry>
+ </row>
+ <row>
+ <entry><keycombo> <keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap></keycap></keycombo>, <keycap>Tab</keycap></entry>
+ <entry>Display list of valid tags</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycombo> <keycap>Shift</keycap>
+ <keycap></keycap> </keycombo>, type beginning of tag,
+ <keycap>Tab</keycap></entry>
+ <entry>Complete the tag</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>g</keycap>
+ </keycombo></entry>
+ <entry>Cancel a command in the minibuffer</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+ </keycombo>, <keycap>/</keycap></entry>
+ <entry>Close tag</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>a</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to beginning of line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>e</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the end of the line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>Home</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the beginning of the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>End</keycap>
+ </keycombo></entry>
+ <entry>Move cursor to the end of the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>k</keycap>
+ </keycombo></entry>
+ <entry>Cut line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>y</keycap>
+ </keycombo></entry>
+ <entry>Paste line</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>s</keycap>
+ </keycombo></entry>
+ <entry>Search forward in the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>r</keycap>
+ </keycombo></entry>
+ <entry>Search backwards in the file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>$</keycap>
+ </keycombo></entry>
+ <entry>Check spelling of current word</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-word, <keycap>Enter</keycap></entry>
+ <entry>Check spelling of current word</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap><keycap>x</keycap>
+ </keycombo> ispell-buffer, <keycap>Enter</keycap></entry>
+ <entry>Check spelling of current buffer</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap>
+ </keycombo></entry>
+ <entry>Open file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap>
+ </keycombo></entry>
+ <entry>Save file</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>x</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></entry>
+ <entry>Exit <application>Emacs</application> and prompt to save
+ files if necessary</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Meta</keycap> <keycap>q</keycap>
+ </keycombo></entry>
+ <entry>Fill paragraph</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>a</keycap>
+ </keycombo></entry>
+ <entry>Edit attributes for a tag (for example, you can edit the
+ <computeroutput>url</computeroutput> attribute of the
+ <computeroutput>ulink</computeroutput> tag)</entry>
+ </row>
+ <row>
+ <entry><keycombo><keycap>Ctrl</keycap> <keycap>c</keycap>
+d545 5
+a549 7
+ <keycombo><keycap>Ctrl</keycap><keycap>c</keycap>
+ </keycombo></entry>
+ <entry>Exit edit attributes</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+@
+
+
+1.2
+log
+ at updating all section usage and associated ID tags
+@
+text
+ at d1 2
+a2 1
+<!-- $Id: emacs.xml,v 1.1 2007/02/03 22:21:58 kwade Exp $ -->
+d34 5
+d57 1
+a57 2
+<screen>
+<computeroutput>
+d181 1
+a181 3
+
+</computeroutput>
+</screen>
+d185 5
+a189 6
+ <para>
+ Do you have a cool wheel mouse? If so, you can add the following to your
+ <filename>.emacs</filename> file so your wheel will work in
+ <application>Emacs</application> (must be
+ <application>Emacs</application> version 21):
+ </para>
+d191 1
+a191 2
+<screen>
+<computeroutput>
+d196 1
+a196 2
+</computeroutput>
+</screen>
+d203 1
+a203 2
+<screen>
+<computeroutput>
+d206 1
+a206 2
+</computeroutput>
+</screen>
+d272 1
+a272 2
+<screen>
+<userinput>
+d279 3
+a281 3
+emacs.geometry: 90x25
+</userinput>
+</screen>
+d285 2
+a286 3
+<screen>
+<command>xrdb -merge ~/.Xresources</command>
+</screen>
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-emacs.xml,v 1.2 2006/12/17 00:41:55 pfrields Exp $ -->
+d33 1
+a33 1
+ <sect1 id="s1-emacs-file">
+d227 1
+a227 1
+ </sect1>
+d230 1
+a230 1
+ <sect1 id="s1-emacs-colors">
+d296 1
+a296 1
+ </sect1>
+d298 1
+a298 1
+ <sect1 id="s1-emacs-cedfile">
+d361 1
+a361 1
+ </sect1>
+d363 1
+a363 1
+ <sect1 id="s1-emacs-loadced">
+d407 1
+a407 1
+ </sect1>
+d409 1
+a409 1
+ <sect1 id="s1-emacs-basic-commands">
+d566 1
+a566 1
+ </sect1>
+d568 1
+a568 1
+ <sect1 id="s1-emacs-examples">
+d576 1
+a576 1
+ <sect2 id="s2-emacs-tag-completion">
+d626 2
+a627 2
+ </sect2>
+ <sect2 id="s2-emacs-tag-closing">
+d637 1
+a637 1
+ </sect2>
+d639 1
+a639 1
+ <sect2 id="s2-emacs-other">
+d683 1
+a683 1
+ </sect2>
+d685 1
+a685 1
+ </sect1>
+d687 1
+a687 1
+ <sect1 id="s1-emacs-additional-resources">
+d725 1
+a725 1
+ </sect1>
+@
+
diff --git a/old-documentation-guide/en_US/getting-files.xml,v b/old-documentation-guide/en_US/getting-files.xml,v
new file mode 100644
index 0000000..30c6c0b
--- /dev/null
+++ b/old-documentation-guide/en_US/getting-files.xml,v
@@ -0,0 +1,476 @@
+head 1.9;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.8
+ LIVE:1.4;
+locks; strict;
+comment @# @;
+
+
+1.9
+date 2007.12.15.21.58.16; author pfrields; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2007.11.15.02.06.47; author pfrields; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2007.07.01.18.20.12; author pfrields; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.06.29.01.31.29; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.06.29.00.10.59; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.06.26.01.28.46; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.06.09.05.33.02; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.03.03.00.03.49; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.9
+log
+ at Add section @@id attributes
+@
+text
+@<!-- $Id: -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<chapter id="ch-getting-files">
+ <title>Prerequisites</title>
+
+ <para>
+ To work on official &FED; documentation you need to install the required
+ tools. Follow the directions below to configure your system.
+ </para>
+
+ <section id="sn-system-packages">
+ <title>System Packages</title>
+
+ <para>
+ Install the "Authoring and Publishing" package group, which contains
+ required DocBook XML files, stylesheets and scripts:
+ </para>
+
+<screen>
+<userinput>su -c 'yum groupinstall "Authoring and Publishing"'</userinput>
+</screen>
+
+ <para>
+ Next, install the <filename>cvs</filename> package, which is used to
+ handle revision control on files in the official repository:
+ </para>
+
+<screen>
+<userinput>su -c 'yum install cvs'</userinput>
+</screen>
+
+ <para>If you plan to use <application>Emacs</application> to edit
+ DocBook XML documentation, install <package>psgml</package>, which
+ adds helpful and time-saving functionality to maximize editing
+ efficiency:</para>
+ <screen><userinput>su -c 'yum install psgml'</userinput></screen>
+ </section>
+
+ <section id="ch-getting-files-fdp">
+ <title>Fedora Documentation Tools</title>
+
+ <para>
+ The &FDP;'s custom scripts and stylesheets are stored in CVS on the
+ <systemitem class="fqdomainname">cvs.fedoraproject.org</systemitem> CVS
+ server. When you check out a document module from CVS, the tools
+ are included in the module inside the <filename
+ class="directory">docs-common/</filename> directory.
+ To work on existing documents in CVS, refer to <xref
+ linkend="ch-cvs"/>.
+ </para>
+ <para>The most powerful component in the &FDP; toolbox is
+ <firstterm>DocBook XML</firstterm>. DocBook XML is a specific
+ scheme for authoring technical documentation using
+ <firstterm>Extensible Markup Language</firstterm>, or
+ <acronym>XML</acronym>. XML allows authors to mark pieces of
+ content with descriptive tags. The following output is an example
+ of DocBook XML:</para>
+ <screen><![CDATA[<article>
+ <title>A Very Short Article</title>
+ <para>This very short article is a
+ demonstration of DocBook XML in
+ its simplest form. Notice how the
+ tags <emphasis>describe</emphasis>
+ the content they surround, and how
+ that content fits into the meaning
+ of the text as a written work.</para>
+</article>]]></screen>
+ <para>This example article, entitled <citetitle>A Very Short
+ Article</citetitle>, consists of only a single paragraph. The
+ tags, or markup, surround elements of content to define the sense
+ in which they are used. A paragraph, for example, is marked with
+ <sgmltag>para</sgmltag> tags. Text that requires emphasis is
+ marked with <sgmltag>emphasis</sgmltag> tags. The author does not
+ worry about the visual formatting such as italics or font size.
+ &FDP; build tools automatically perform all formatting
+ tasks.</para>
+ <para>The custom tools built by the &FDP; render DocBook source into
+ a variety of formats for publication and distribution. They also
+ allow translators to create localized versions of the XML
+ documents for &DISTRO; users around the world. The flexibility of
+ XML allows for a single document to be used many times for many
+ purposes, like reusable code for a programmer.</para>
+ <para>DocBook is itself very well documented. For more information
+ about DocBook, visit <ulink url="http://www.docbook.org/"/>. The
+ DocBook site also features complete copies of <citetitle>DocBook:
+ The Definitive Guide</citetitle> to browse and download, the
+ canonical source for DocBook information.</para>
+ <note>
+ <title>DocBook XML Versions</title>
+ <para>DocBook XML, like a computer program, has version numbers.
+ The version used by &FDP; right now is &DBVER;. The DocBook web
+ site may document a slightly newer version, but the majority of
+ the schema still applies.</para>
+ </note>
+ <para>Contributors who use the Microsoft Windows operating system
+ can still make use of DocBook tools. For more information, refer
+ to <ulink
+ url="http://www.codeproject.com/winhelp/docbook_howto.asp"/>.</para>
+ </section>
+
+ <section id="sn-getting-files-names">
+ <title>Naming Conventions</title>
+ <para>
+ The &FDP; provides the tools, scripts, and stylesheets to
+ transform your <abbrev>XML</abbrev> documents into other output
+ formats such as <abbrev>HTML</abbrev>. In addition, these tools
+ can build your document into a <abbrev>RPM</abbrev> package. To
+ take advantage of these services, follow the conventions in this
+ section to name your files.
+ </para>
+ <para>On the CVS server, directories that contain document files are
+ called <firstterm>modules</firstterm>. Each module represents a
+ single document. Each document may consist of several
+ <firstterm>branches</firstterm> if that document changes with each
+ release of &DISTRO;. Contributors can check out single branches
+ of these modules or the entire module. Each document or branch
+ may contain multiple XML source files.</para>
+ <para>Use the <command>cvs co -c</command> command to view existing
+ module names.</para>
+ <example>
+ <title>Partial List of CVS Modules</title>
+ <screen><userinput>cd ~/localrepo/fedora-docs/</userinput>
+<computeroutput><![CDATA[about-fedora about-fedora &docs-common
+about-fedora-F-7 &about-fedora-F-7-dir &docs-common
+about-fedora-F-7-dir -d about-fedora about-fedora/F-7
+about-fedora-devel &about-fedora-devel-dir &docs-common
+about-fedora-devel-dir -d about-fedora about-fedora/devel
+build-docs infrastructure/build-docs &docs-common
+cvsroot CVSROOT
+desktop-up2date desktop-up2date &docs-common
+desktop-user-guide desktop-user-guide &docs-common
+desktop-user-guide-FC-6 &desktop-user-guide-FC-6-dir &docs-common
+desktop-user-guide-FC-6-dir -d desktop-user-guide desktop-user-guide/FC-6
+desktop-user-guide-devel &desktop-user-guide-devel-dir &docs-common
+desktop-user-guide-devel-dir -d desktop-user-guide desktop-user-guide/devel
+developer-guide developer-guide &docs-common
+docs .
+docs-common docs-common
+documentation-guide documentation-guide &docs-common]]></computeroutput></screen>
+ </example>
+ <para>The leftmost entry in each line is the name of a module you
+ can check out from CVS. The rest of the line ensures that
+ checkouts include the proper branch of a document and the common
+ build tools. For more information on CVS, refer to <xref
+ linkend="ch-cvs"/>.</para>
+ <para>Note in the listing above that the
+ <systemitem>about-fedora</systemitem> module has two branches
+ available. One branch is for &DISTRO; 7 and one is for forward
+ development to match the current work of developers. On the other
+ hand, the <systemitem>documentation-guide</systemitem> module is
+ not branched.</para>
+ <tip>
+ <title>Modules Labeled <filename>-dir</filename></title>
+ <para>Modules ending with the suffix <filename>-dir</filename> are
+ not usually helpful to checkout directly. These modules do not
+ include the common build tools and thus do not provide many of
+ the functions contributors require.</para>
+ </tip>
+ <section id="ch-getting-files-naming-modules">
+ <title>Module Names</title>
+ <para>Choose a module name that accurately reflects your
+ document's subject, but avoid any name already taken. The
+ document title without any use of the word
+ <wordasword>&FEDLC;</wordasword> is a reasonable choice in most
+ cases. Use the length descriptors
+ <wordasword>tutorial</wordasword> or
+ <wordasword>guide</wordasword> in the module name where
+ appropriate.</para>
+ <important>
+ <title>Avoid Redundancy</title>
+ <para>
+ Do not use the word <wordasword>&FEDLC;</wordasword> to name
+ modules in the &FDP; CVS repository.
+ </para>
+ </important>
+ <segmentedlist id="sl-correct-module-naming">
+ <title>Correct Module Naming</title>
+ <segtitle>Document Name</segtitle>
+ <segtitle>CVS Module Name</segtitle>
+ <seglistitem>
+ <seg>Desktop User Guide</seg>
+ <seg>desktop-user-guide</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Software Management with
+ <application>Yum</application></seg>
+ <seg>yum-guide</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Using <application>Pup</application></seg>
+ <seg>pup-tutorial</seg>
+ </seglistitem>
+ </segmentedlist>
+ </section>
+ <section id="sn-file-naming">
+ <title>File Names</title>
+ <para>Follow these guidelines for naming files to make
+ collaboration and document reuse easy:</para>
+ <itemizedlist>
+ <listitem>
+ <para>As with module names, avoid using the word
+ <wordasword>&FEDLC;</wordasword> in file names since it is
+ redundant.</para>
+ </listitem>
+ <listitem>
+ <para>If the document is comprised of many XML files, avoid
+ repeating the name of the document when naming the
+ constituent files.</para>
+ </listitem>
+ <listitem>
+ <para>Avoid numbering files to show order, since editors and
+ authors often rearrange documents or reuse their files in
+ other documents.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.8
+log
+ at Add link for DocBook tools in Windows.
+@
+text
+ at d203 1
+a203 1
+ <section>
+@
+
+
+1.7
+log
+ at Additional upgrades and changes; this will go to publication ASAP.
+@
+text
+ at d103 4
+@
+
+
+1.6
+log
+ at More content updates
+@
+text
+ at d91 1
+a91 1
+ <para>DocBook is iself very well documented. For more information
+d93 3
+a95 3
+ DocBook site also features complete browseable and downloadable
+ copies of <citetitle>DocBook: The Definitive Guide</citetitle>,
+ the canonical source for DocBook information.</para>
+d98 1
+a98 1
+ <para>DocBook XML, like a computer progam, has version numbers.
+d152 1
+a152 1
+ avalable. One branch is for &DISTRO; 7 and one is for forward
+d156 7
+@
+
+
+1.5
+log
+ at Some content updates, push new bugfix rev 0.3.0.1, no publishing needed yet
+@
+text
+ at d59 44
+a102 1
+
+@
+
+
+1.4
+log
+ at - No need to check out common tools separately
+- Correct server location to fp.o
+@
+text
+ at d19 1
+a19 1
+ <section id="ch-getting-files-system-packages">
+d62 2
+a63 2
+ <section id="ch-getting-files-filenames">
+ <title>Filename Conventions</title>
+d65 6
+a70 5
+ The &FDP; provides the tools, scripts, and stylesheets to transform your
+ <abbrev>XML</abbrev> documents into other output formats such as
+ <abbrev>HTML</abbrev>. In addition, these tools can build your document
+ into a <abbrev>RPM</abbrev> package. To take advantage of these
+ services, you must follow conventions for naming your files.
+d72 26
+a97 13
+ <section id="ch-getting-files-filenames-doc">
+ <title>Document Filenames</title>
+ <para>
+ Each document lives in a peer directory to the
+ <filename>docs-common</filename> directory you extracted from the &FED;
+ archive earlier. On the CVS server, these directories are called
+ <firstterm>modules</firstterm>. Use
+ the <command>cvs co -c</command> command to view existing module names.
+ </para>
+ <example>
+ <title>Partial List of CVS Modules</title>
+ <screen><userinput>cd ~/localrepo/fedora-docs/</userinput>
+<computeroutput>developer-guide developer-guide
+d100 15
+a114 3
+documentation-guide documentation-guide
+example-tutorial example-tutorial</computeroutput></screen>
+ </example>
+d116 7
+a122 1
+ document's subject, but avoid any name already taken.</para>
+d126 1
+a126 1
+ Do not use the word <wordasword>&FED;</wordasword> to name
+d130 40
+@
+
+
+1.3
+log
+ at Add bit about installing psgml
+@
+text
+ at d53 5
+a57 27
+ server. Check them out along with the DocBook XML files for the existing
+ docs.
+ </para>
+
+<screen>
+<userinput>mkdir <replaceable>my-fedora-docs-sandbox</replaceable>
+cd <replaceable>my-fedora-docs-sandbox</replaceable>
+export CVSROOT=:ext:<replaceable>username</replaceable>@@cvs.fedora.redhat.com:/cvs/docs
+cvs login
+cvs co docs-common</userinput>
+</screen>
+
+ <para>
+ At the password prompt, press the <keycap>Enter</keycap> key.
+ </para>
+
+ <note>
+ <title>Common Files</title>
+ <para>
+ You need to perform this "checkout" step only once, although you may
+ need to update the files later. These files are common to all the
+ official documentation.
+ </para>
+ </note>
+
+ <para>
+ To work on existing documents in CVS, refer to <xref linkend="ch-cvs"/>.
+d83 1
+a83 4
+<computeroutput>build-docs infrastructure/build-docs
+cvsroot CVSROOT
+desktop-up2date desktop-up2date
+developer-guide developer-guide
+@
+
+
+1.2
+log
+ at Better hinting for choosing module names; caution about using distro name redundantly
+@
+text
+ at d40 5
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d82 1
+a82 1
+ &FDP; provides the tools, scripts, and stylesheets to transform your
+d94 1
+a94 2
+ <firstterm>modules</firstterm>. Choose a module name that accurately
+ reflects your document's subject, but avoid any name already taken. Use
+d97 14
+d114 2
+a115 3
+ Do not use the word <wordasword>&FED;</wordasword> in your module
+ name. Since all documents in the repository are &FED; documentation,
+ using this term creates unnecessary confusion.
+@
+
diff --git a/old-documentation-guide/en_US/intro.xml,v b/old-documentation-guide/en_US/intro.xml,v
new file mode 100644
index 0000000..cc62b16
--- /dev/null
+++ b/old-documentation-guide/en_US/intro.xml,v
@@ -0,0 +1,148 @@
+head 1.4;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.4
+ LIVE:1.2;
+locks; strict;
+comment @# @;
+
+
+1.4
+date 2007.08.02.00.12.32; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.06.29.01.31.29; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.02.05.22.06.10; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.4
+log
+ at Correct grammatical error
+@
+text
+@<!-- $Id: intro.xml,v 1.3 2007/06/29 01:31:29 pfrields Exp $ -->
+<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+
+<preface id="ch-intro">
+ <title>Introduction</title>
+
+ <para>
+ The goal of the &FDP; is to create easy-to-follow, task-based
+ documentation for &FED; users and developers. The &FDP; uses the
+ following tools:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>DocBook XML v4.4</para>
+ </listitem>
+ <listitem>
+ <para>Custom XSLT stylesheets for both print and HTML
+ versions</para>
+ </listitem>
+ <listitem>
+ <para>Custom scripts to generate HTML output (use
+ <command>xmlto</command>)</para>
+ </listitem>
+ <listitem>
+ <para>Emacs with PSGML mode (optional, but recommended)</para>
+ </listitem>
+<!-- We've clipped this out for now.
+ <listitem>
+ <para>Emacs with nXML mode (optional)</para>
+ </listitem>
+-->
+ </itemizedlist>
+
+ <para>
+ This document explains the tools used by the &FDP;. It provides
+ writing and tagging guidelines to ensure &FED; documentation is
+ consistent and easy-to-follow.
+ </para>
+
+</preface>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.3
+log
+ at More content updates
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: intro.xml,v 1.2 2007/02/05 22:06:10 pfrields Exp $ -->
+d44 2
+a45 2
+ This document explains the tools used by the &FDP; and provides
+ writing and tagging guidelines to make &FED; documentation is
+@
+
+
+1.2
+log
+ at Clip out nxml bit for now.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: intro.xml,v 1.1 2007/02/03 22:21:58 kwade Exp $ -->
+d17 2
+a18 10
+ documentation for &FED; users and developers. Other than the
+ <citetitle>&IG;</citetitle>, each tutorial should be in DocBook XML
+ article format, with one article per topic. This way, writers can
+ contribute documentation about a specific topic without having to
+ worry about how it fits into a manual or how it flows with other
+ topics.
+ </para>
+
+ <para>
+ The following tools are used:
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-intro.xml,v 1.2 2006/12/16 22:55:41 pfrields Exp $ -->
+d44 1
+d48 1
+@
+
diff --git a/old-documentation-guide/en_US/l10n.xml,v b/old-documentation-guide/en_US/l10n.xml,v
new file mode 100644
index 0000000..d7e7350
--- /dev/null
+++ b/old-documentation-guide/en_US/l10n.xml,v
@@ -0,0 +1,187 @@
+head 1.1;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.1
+date 2008.04.10.02.34.37; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.1
+log
+ at Add L10n chapter to DocGuide (#441190)
+@
+text
+@<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id: -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<chapter id="ch-l10n">
+ <title>Localization (L10n)</title>
+ <para>
+ This chapter discusses how translations are provided in &DISTRO;
+ documentation.
+ </para>
+ <section id="sn-l10n-po-files">
+ <title>PO Files</title>
+ <para>
+ The cornerstone of translation when using XML files such as
+ DocBook is the <firstterm>Portable Object</firstterm> or
+ <acronym>PO</acronym> file. PO files provide a way for
+ independent individuals or teams to translate documents. The
+ &FDP; toolchain includes rules for creating, updating, and
+ maintaining these PO files.
+ </para>
+ <para>
+ PO files are usually found in two forms:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <filename class="extension">.pot</filename> file, or
+ <firstterm>PO Template</firstterm> (<acronym>POT</acronym>)
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <filename class="extension">.po</filename> file, or
+ translation file (<acronym>PO</acronym>)
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ A POT is, as the name suggests, a blank template for new
+ translations. It contains some header information and a list of
+ strings based on the content of the original XML file from which
+ it was created. Translators do not alter the POT. The POT
+ should only be changed after changes are made to the original
+ XML file from which it is derived.
+ </para>
+ <para>
+ A translator who wishes to start working on a new language
+ copies the POT to a locale-specific PO file. Then the
+ translator uses any of a number of command-line or graphical
+ tools to translate each of the strings in the list. A single
+ POT is used to create many POs, one for each locale. These
+ files are normally named for their locale code, such as
+ <filename>de.po</filename>, <filename>it.po</filename>, and so
+ on.
+ </para>
+ </section>
+ <section id="sn-l10n-make-pot">
+ <title>Creating or Updating a POT</title>
+ <para>
+ The POT is named after the document from which it is derived.
+ If document named in the <filename>Makefile</filename>) is
+ <filename>foo-tutorial.xml</filename>, the POT is named
+ <filename>foo-tutorial.pot</filename>.
+ </para>
+ <para>
+ To create a new POT, use the following command:
+ </para>
+ <screen><![CDATA[make pot]]></screen>
+ <para>
+ The same command is used to update the POT when the original XML
+ sources change.
+ </para>
+ <important>
+ <title>Keep POT Fresh</title>
+ <para>
+ Update the POT whenever the original XML changes. Many
+ translators' tools automatically notify them of the change so
+ they can update translations quickly.
+ </para>
+ </important>
+ </section>
+ <section id="sn-l10n-make-po">
+ <title>Updating PO Files</title>
+ <para>
+ The translation files are created by the individual translators,
+ and document maintainers do not normally need to create them.
+ Translators update a list of locales in the
+ <filename>po/LINGUAS</filename> file which defines all the
+ locales for which translations exist.
+ </para>
+ <para>
+ Whenever the source XML files are updated, the maintainer must
+ at least update the POT. It is helpful, however, to also merge
+ these changes with the existing translations for those
+ translators who are not automatically notified of changes.
+ </para>
+ <important>
+ <title>Staying Current</title>
+ <para>
+ Always make sure your local copy of PO is fresh, using the CVS
+ "update" command:
+ </para>
+ <screen><![CDATA[cvs up]]></screen>
+ </important>
+ <para>
+ To merge new changes into the existing PO translations, use the
+ following command:
+ </para>
+ <screen><![CDATA[make po]]></screen>
+ </section>
+ <section id="sn-l10n-postat">
+ <title>Checking Statistics</title>
+ <para>
+ PO strings fall into three categories:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ <firstterm>translated</firstterm>, meaning the string has
+ been handled by a translator and its source has not changed
+ since then
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <firstterm>fuzzy</firstterm>, meaning the string has changed
+ since it was last handled by a translator
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <firstterm>untranslated</firstterm>, meaning no translation
+ has yet been provided for this string, or it is brand new
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>
+ To see a rough statistical tally of the string handling inside
+ the PO for a module, use the following command:
+ </para>
+ <screen><![CDATA[make postat]]></screen>
+ <para>
+ For each locale in the list, a count is shown of translated,
+ fuzzy, and untranslated strings in that order. Tallies that
+ only provide two numerals are usually translated followed by
+ untranslated. Tallies with only one numeral are usually fully
+ translated.
+ </para>
+ <para>
+ To see only a specific locale, append a dash and the locale code
+ to the <command>postat</command> target:
+ </para>
+ <screen><![CDATA[make postat-de]]></screen>
+ </section>
+</chapter>
+@
diff --git a/old-documentation-guide/en_US/module-struct.xml,v b/old-documentation-guide/en_US/module-struct.xml,v
new file mode 100644
index 0000000..940cdad
--- /dev/null
+++ b/old-documentation-guide/en_US/module-struct.xml,v
@@ -0,0 +1,833 @@
+head 1.10;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.8
+ LIVE:1.5;
+locks; strict;
+comment @# @;
+
+
+1.10
+date 2007.12.15.21.58.16; author pfrields; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2007.12.15.21.50.02; author pfrields; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2007.07.29.23.55.25; author pfrields; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2007.07.01.18.20.12; author pfrields; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.06.29.00.10.59; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.06.23.05.24.16; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.03.12.01.25.56; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.03.09.01.16.05; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.02.03.22.29.37; author kwade; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.10
+log
+ at Add section @@id attributes
+@
+text
+@<!-- $Id: -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<chapter id="ch-how-modules-work">
+ <title>How Modules Work</title>
+ <para>Documentation modules have a specific structure that enables the
+ preconfigured tools to work correctly. Follow this structure exactly or you
+ may have problems building your module. The &FDP; build tools locate
+ resources in the module and use them to build new output such as HTML or RPM
+ packages.</para>
+ <section id="sn-module-struct">
+ <title>Structure of a Module</title>
+ <para><xref linkend="ex-module-structure"/> shows a directory tree
+ of an example module, excluding any <filename
+ class="directory">CVS</filename> folders. Note that this
+ example document does not have branches.</para>
+ <example id="ex-module-structure">
+ <title>Example Module Structure</title>
+ <screen><computeroutput><![CDATA[example-doc/
+ |
+ |-- en_US/
+ | |-- example-doc.xml
+ | |-- para.xml
+ | |-- doc-entities.xml
+ | `-- rpm-info.xml
+ |
+ |-- figs/
+ | |-- fedora-logo-sprite.eps
+ | `-- fedora-logo-sprite.png
+ |
+ |-- po/
+ | |-- LINGUAS
+ | |-- de.po
+ | |-- example-doc.pot
+ | `-- pt.po
+ |
+ `-- Makefile]]></computeroutput></screen>
+ </example>
+ <segmentedlist id="sg-module-contents">
+ <title>CVS Module Contents</title>
+ <segtitle>Component</segtitle>
+ <segtitle>Type</segtitle>
+ <segtitle>Usage Notes</segtitle>
+ <seglistitem>
+ <seg>Primary language directory</seg>
+ <seg>required</seg>
+ <seg>This is the only directory absolutely required. It is named
+ for the original language of the document, such as <filename
+ class="directory">en_US</filename> (US English). The
+ primary language does not have to be US English; all languages
+ are supported. This directory contains all the XML source for
+ the actual document, as well as XML source for
+ document-specific <firstterm>entities</firstterm><footnote>
+ <para>Think of an XML entity as a predefined snippet of
+ information. It can represent a chunk of XML source, or
+ simply a word or character. If the information changes, it
+ need be replaced only once, in the definition, to fix all
+ usage.</para>
+ </footnote>.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Graphics directory</seg>
+ <seg>optional</seg>
+ <seg>The <filename class="directory">figs/</filename> directory
+ is an optional directory where graphics for the document
+ should be stored. If graphics are screenshots that are
+ particular to a language, the <filename
+ class="directory">figs/</filename> directory can and should
+ be stored in a language directory.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Translation (PO) directory</seg>
+ <seg>optional</seg>
+ <seg>The <filename class="directory">po/</filename> directory
+ contains specially formatted Portable Object, or
+ <acronym>PO</acronym>, files created and used by translators.
+ The &FDP; build tools use these files to create translated
+ versions of documents. The translated documents are not stored
+ in CVS; they are created as needed from these PO files. The
+ <filename class="directory">po/</filename> directory also
+ contains the <filename>LINGUAS</filename> file, which lists
+ the active translation <firstterm>locales</firstterm>, or
+ languages.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Makefile</seg>
+ <seg>required</seg>
+ <seg>The <filename>Makefile</filename> controls the build
+ process. Its content is discussed in <xref
+ linkend="ex-makefile"/>.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename>rpm-info.xml</filename></seg>
+ <seg>required</seg>
+ <seg>The <filename>rpm-info.xml</filename> file contains
+ document specific metadata</seg>
+ </seglistitem>
+ </segmentedlist>
+ <important>
+ <title>Common Build Tools</title>
+ <para>Never add the <systemitem>docs-common</systemitem> build
+ tools directory to an individual module. Special formatting in
+ the module list downloads these tools when a user checks out a
+ document module. For more information, refer to <xref
+ linkend="ch-getting-files-naming-modules"/>.</para>
+ </important>
+ </section>
+ <section id="sn-build-system">
+ <title>The Document Build System</title>
+ <para>
+ The build system can render the document into another format such
+ as <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using
+ <command>make(1)</command><footnote>
+ <para>In Linux and &DISTRO; documentation, references to
+ commands often include a number inside parentheses. This
+ number represents the section of
+ <firstterm>manpages</firstterm> that includes documentation
+ for that command. To read the manpage for
+ <command>make(1)</command>, use the command <command>man 1
+ make</command>.</para>
+ </footnote> and shell scripts. Authors need
+ <emphasis>no</emphasis> prior experience with either shell scripts
+ or a <command>make(1)</command>.
+ </para>
+ <section id="sn-makefile">
+ <title>The Document <filename>Makefile</filename></title>
+ <para>
+ Each individual document has its own
+ <filename>Makefile</filename>, which only needs to be a few
+ lines long. The document <filename>Makefile</filename> content
+ is designed for cut and paste operations.
+ </para>
+ <para>
+ <xref linkend="ex-makefile"/> below shows the whole
+ <filename>Makefile</filename> for a simple document with two
+ files and two translations.
+ </para>
+ <example id="ex-makefile">
+ <title>Sample Document Makefile</title>
+ <screen><![CDATA[DOCBASE = example-doc
+PRI_LANG = en_US
+DOC_ENTITIES = doc-entities
+
+define XMLFILES_template
+XMLFILES-${1} = ${1}/example-doc.xml \
+ ${1}/para.xml
+endef
+
+define find-makefile-common
+for d in docs-common ../docs-common ../../docs-common; do
+if [ -f $$d/Makefile.common ]; then echo "$$d/Makefile.common"; break; fi; done
+endef
+include $(shell $(find-makefile-common))]]></screen>
+ </example>
+ <para>
+ Do not be concerned with some of the more complicated syntax
+ such as the <command>XMLFILES_template</command> stanza. An
+ explanation for this template appears a few paragraphs
+ below.</para>
+ <segmentedlist id="sg-makefile-variables">
+ <title>Makefile Variables</title>
+ <segtitle>Variable</segtitle>
+ <segtitle>Explanation</segtitle>
+ <seglistitem>
+ <seg><systemitem class="macro">DOCBASE</systemitem></seg>
+ <seg>This variable contains the name for the main (parent) XML
+ document. Follow convention by naming your document after
+ the module name.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">PRI_LANG</systemitem></seg>
+ <seg>This variable contains the ISO code for the original
+ version of the document, such as
+ <systemitem>en_US</systemitem>.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">DOC_ENTITIES</systemitem></seg>
+ <seg>This variable contains a listing of any files containing
+ entity definitions. The &FDP; uses a special XML format to
+ record document-specific entities, so they can be translated
+ and built on the fly like any other XML document. An
+ example is shown later in this guide. <!-- need xref here
+ --></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem
+ class="macro">XMLFILES_template</systemitem></seg>
+ <seg>This template allows the build tools to work with the
+ document in multiple languages once it is translated. The
+ <systemitem class="macro">${1}</systemitem> marking is a
+ variable used to substitute the appropriate language. This
+ template is not terribly complicated. For a new module,
+ duplicate this section exactly except for the actual
+ filenames. Prepend the text <systemitem
+ class="macro">${1}/</systemitem>, in place of the language
+ code directory name, to each filename in your document.
+ </seg>
+ </seglistitem>
+ </segmentedlist>
+ <important>
+ <title>Files Exempt From Listing</title>
+ <para>Do not include the document-specific entities XML file or
+ the <filename>rpm-info.xml</filename> file, which will be
+ discussed later in this guide.<!-- include xref --></para>
+ </important>
+ <para>
+ The final section, beginning with <literal>define</literal>,
+ locates the main <filename>Makefile.common</filename> for the
+ build system. This <filename>Makefile.common</filename> file
+ contains all the <application>make(1)</application> targets and
+ rules to actually build the document and the various archives.
+ </para>
+ </section>
+ <section id="sn-rpm-info">
+ <title>The Document <filename>rpm-info.xml</filename></title>
+ <para>Each document module's primary language directory contains a
+ file called <filename>rpm-info.xml</filename>. This file
+ contains document-specific metadata used to generate revision
+ history, copyright, and contributor information. It follows a
+ DTD specification included with the rest of the build system
+ tools.</para>
+ </section>
+ </section>
+ <section id="ch-getting-files-build-system-targets">
+ <title>Build System Actions</title>
+ <para>
+ To render the <abbrev>XML</abbrev> document into another format,
+ use one of the following <command>make</command> targets:
+ </para>
+ <segmentedlist>
+ <title>Build Targets</title>
+ <segtitle>Target</segtitle>
+ <segtitle>Explanation</segtitle>
+ <seglistitem>
+ <seg><systemitem class="macro">help</systemitem></seg>
+ <seg>This target prints a list of available targets and
+ their descriptions.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">validate-xml</systemitem></seg>
+ <seg>This target <firstterm>validates</firstterm> the XML files
+ to make sure they are not only well-formed, but follow the
+ DTD. Some viewers of XML documents may not work correctly
+ until you run this target. This target includes copying
+ required entity files so that validating XML viewers work
+ properly</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">html</systemitem></seg>
+ <seg>This target builds the "chunked" <abbrev>HTML</abbrev>
+ document for each defined translation. Output is placed in a
+ separate directory named <filename
+ class="directory"><systemitem
+ class="macro">${DOCBASE}</systemitem>-<systemitem
+ class="macro">${LANG}</systemitem>/</filename>. Each
+ document section is a separate file within that
+ directory.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">html-nochunks</systemitem></seg>
+ <seg>This target builds the "non-chunked" <abbrev>HTML</abbrev>
+ document for each defined translation. Output is placed in a
+ single file: <filename><systemitem
+ class="macro">${DOCBASE}</systemitem>-<systemitem
+ class="macro">${LANG}</systemitem>.html</filename>; no
+ other files are created.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">pdf</systemitem></seg>
+ <seg>This target builds only the <abbrev>PDF</abbrev> document
+ for all document languages. <abbrev>PDF</abbrev> production is
+ currently erratic and may not work for your document.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">tarball</systemitem></seg>
+ <seg>This target builds only the <command>tar(1)</command>
+ archive for all document languages.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">all</systemitem></seg>
+ <seg>This target builds all targets listed above.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">clean</systemitem></seg>
+ <seg>This target deletes any temporary, or generated files, but
+ does <emphasis>not</emphasis> erase any <abbrev>HTML</abbrev>,
+ <abbrev>PDF</abbrev>, or archive files.</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><systemitem class="macro">distclean</systemitem></seg>
+ <seg>This target erases all <abbrev>HTML</abbrev>,
+ <abbrev>PDF</abbrev>, and archive files. This target
+ automatically invokes the <filename>clean</filename> target as
+ well.</seg>
+ </seglistitem>
+ </segmentedlist>
+ <note>
+ <title>PDF Generation is Erratic</title>
+ <para><abbrev>PDF</abbrev> production is currently erratic and may
+ not work for your document.</para>
+ </note>
+ </section>
+ <section id="sn-module-adding-targets">
+ <title>Adding or Changing Targets</title>
+ <para>
+ To add a new target and rules, place them at the bottom of the
+ document <filename>Makefile</filename>, below the
+ <literal>include</literal> line. Follow your target definitions
+ with a double colon, not a single colon. The double colon
+ allows you to specify additional rules for existing targets, or
+ to write rules for a new target.
+ </para>
+ <para>
+ For more information on using <command>make(1)</command>,
+ consult the online documentation with the command <command>info
+ make</command> in a terminal.
+ </para>
+ </section>
+ <section id="ch-getting-files-build-system-images">
+ <title>Using Document Image Files</title>
+ <para>
+ Tutorial documents often make use of images such as <filename
+ class="extension">.PNG</filename> files. Store image files in
+ a <filename class="directory">figs/</filename> folder in the
+ main module directory, as shown in <xref
+ linkend="ex-module-structure"/>.
+ </para>
+ <para>
+ Depending on the output media, sometimes images may be scaled,
+ streteched, or squashed. To minimize any distortions, we
+ recommend that you use only <filename
+ class="extension">.PNG</filename> images. Avoid <filename
+ class="extension">.JPG</filename> files. The
+ <command>convert(1)</command> program, from the <package
+ role="rpm">ImageMagick</package> <abbrev>RPM</abbrev> package,
+ provides a convenient way to reformat <filename
+ class="extension">.JPG</filename> images into <filename
+ class="extension">.PNG</filename> format. For more information
+ on formatting images such as screenshots, refer to <xref
+ linkend="sn-screenshots"/>.
+ </para>
+ <para>
+ Image files may be organized into subdirectories under
+ <filename>figs/</filename> if necessary. The document building
+ system recreates the image subdirectory structure in the output
+ documents.
+ </para>
+ <para>
+ Images often contain labels or other text which may need to be
+ localized. A screenshot of a program, for example, may require
+ a version for each translated language. Name language-dependent
+ image files such as program screenshots by adding the language
+ code to the filename, such as
+ <filename>menu-en_US.png</filename>. Language-independent
+ images, such as <filename>icon.png</filename>, do not need
+ language codes.
+ </para>
+ <para>
+ Sometimes, a document may require images that do not follow the
+ naming convention. To use these images with the document
+ building system, create an ordinary text file containing the
+ image filenames. This file must be named
+ <filename>figs/Manifest-</filename><systemitem
+ class="macro">${LANG}</systemitem> so the build system finds
+ it when searching for image filenames.
+ </para>
+ <para>
+ <xref linkend="ch-getting-files-build-system-manifest"/>
+ demonstrates one way to create this
+ <filename>Manifest</filename> file.
+ </para>
+ <example id="ch-getting-files-build-system-manifest">
+ <title>Building A Manifest</title>
+ <programlisting><![CDATA[rm -f figs/Manifest-en
+find figs -print >/tmp/manifest
+mv /tmp/manifest figs/Manifest-en]]></programlisting>
+ </example>
+ </section>
+ <section id="sn-adding-docbook-file">
+ <title>Adding a New DocBook XML File</title>
+ <para>To add a new DocBook XML file to an existing document,
+ follow these steps:</para>
+ <procedure>
+ <step>
+ <para>Place the new DocBook XML file in the primary language
+ directory.</para>
+ </step>
+ <step>
+ <para>Edit the <filename>Makefile</filename> and add the
+ filename to the <varname>XMLFILES-${1}</varname> listing.
+ Append a <keycap>\</keycap> to the last existing line, and
+ on the next line add an entry for the new file. Remember to
+ add the <literal>${1}/</literal> prefix as a substitute for
+ the language directory name.</para>
+ </step>
+ </procedure>
+ </section>
+ <section id="sn-adding-translation">
+ <title>Adding a Translation</title>
+ <para>Translations are stored as PO (portable object) files, which
+ the toolchain transforms into translated documents. Each PO
+ file is based on the POT (PO template) for the document and
+ translated by the &FED; Translation Project. To add a
+ translation, follow these steps:</para>
+ <procedure>
+ <step>
+ <para>If the <filename class="directory">po/</filename>
+ directory does not exist, create it and add it to
+ CVS:</para>
+ <screen><![CDATA[mkdir po && cvs add po/]]></screen>
+ </step>
+ <step>
+ <para>If it does not exist, create the POT file:</para>
+ <screen><![CDATA[make pot]]></screen>
+ </step>
+ <step>
+ <para>Add the new translation language to the
+ <varname>OTHERS</varname> listing in the
+ <filename>Makefile</filename>.</para>
+ </step>
+ <step>
+ <para>Although translators often copy the POT manually to
+ create the new PO file, the following command also
+ works:</para>
+ <screen>make po/<replaceable>lang</replaceable>.po</screen>
+ </step>
+ </procedure>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.9
+log
+ at Add missing targets (#371531)
+@
+text
+ at d310 1
+a310 1
+ <section>
+d386 1
+a386 1
+ <section>
+d405 1
+a405 1
+ <section>
+@
+
+
+1.8
+log
+@* 0.3.0.3:
+ - Add information on po/LINGUAS
+
+* 0.3.0.2:
+ - Delete unnecessary tags section and references
+@
+text
+ at d242 14
+d309 1
+a435 1
+ </section>
+@
+
+
+1.7
+log
+ at Additional upgrades and changes; this will go to publication ASAP.
+@
+text
+ at d39 1
+d86 5
+a90 1
+ in CVS; they are created as needed from these PO files.</seg>
+a148 1
+OTHERS = de pt
+a183 8
+ <seg><systemitem class="macro">OTHERS</systemitem></seg>
+ <seg>This variable contains a listing of ISO codes for any
+ other versions into which the document has been translated.
+ The module must contain a <filename
+ class="directory">po/</filename> directory and a PO file
+ for any indicated additional languages.</seg>
+ </seglistitem>
+ <seglistitem>
+@
+
+
+1.6
+log
+ at Some content updates, push new bugfix rev 0.3.0.1, no publishing needed yet
+@
+text
+ at d294 5
+@
+
+
+1.5
+log
+ at This is finally being updated; I hope to finish this in the next week.
+@
+text
+ at d22 2
+a23 1
+ class="directory">CVS</filename> folders:</para>
+d81 5
+a85 5
+ contains specially formatted files created and used by
+ translators. The &FDP; build tools use these files to create
+ translated versions of documents. The translated documents are
+ not stored in CVS; they are created as needed from these PO
+ files.</seg>
+d101 8
+d115 9
+a123 1
+ <command>make(1)</command> and shell scripts. Authors need
+@
+
+
+1.4
+log
+ at Update module information to match new include statement for Makefile.common
+@
+text
+ at d101 1
+a101 1
+ <section id="ch-getting-files-build-system">
+d208 1
+a208 1
+ <section>
+a215 36
+ <para><xref linkend="ex-rpminfo"/> illustrates the content of
+ this file:</para>
+ <example id="ex-rpminfo">
+ <title>Example <filename>rpm-info.xml</filename> File</title>
+ <programlisting><![CDATA[<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE rpm-info SYSTEM "../../docs-common/packaging/rpm-info.dtd">
+
+<rpm-info>
+ <colophon>
+ <worker surname="Smith" firstname="John" othername="Q."
+ id="JohnSmith" email="jsmith@@example.com"
+ wholename="John Q. Smith" initials="JS"/>
+ </colophon>
+ <author worker="JohnSmith"/>
+ <license>
+ <rights>OPL</rights>
+ <version>1.0</version>
+ </license>
+ <copyright>
+ <year>2006</year>
+ <holder>John Q. Smith</holder>
+ </copyright>
+ <title>My Tutorial</title>
+ <desc>A tutorial about something important</desc>
+ <changelog order="newest-first">
+ <revision date="2006-06-01" number="0.1" role="doc">
+ <author worker="JohnSmith"/>
+ <details>First draft</details>
+ </revision>
+ </changelog>
+</rpm-info>]]></programlisting>
+ </example>
+ <para>If you are not familiar with XML editing, copy and paste
+ this file from an existing module and then edit the values for
+ the various elements as appropriate. Consult &FDP; members and
+ help channels for more assistance if needed.</para>
+@
+
+
+1.3
+log
+ at Yay, segmentedlists for everyone!
+@
+text
+ at d125 1
+a125 1
+ <programlisting><![CDATA[DOCBASE = example-doc
+d135 5
+a139 1
+include ../docs-common/Makefile.common]]></programlisting>
+d201 5
+a205 5
+ The final line, beginning with <literal>include</literal>,
+ references the main <filename>Makefile</filename> for the build
+ system. This <filename>Makefile.common</filename> file contains
+ all the <application>make(1)</application> targets and rules to
+ actually build the document and the various archives.
+@
+
+
+1.2
+log
+ at updating all section usage and associated ID tags
+@
+text
+ at d44 56
+a99 42
+ <formalpara>
+ <title>Primary language directory (required)</title>
+ <para>This is the only directory absolutely required. It is named for the
+ original language of the document, such as <filename
+ class="directory">en_US</filename> (US English). The primary language
+ does not have to be US English; all languages are supported. This
+ directory contains all the XML source for the actual document, as well
+ as XML source for document-specific
+ <firstterm>entities</firstterm><footnote>
+ <para>Think of an XML entity as a predefined snippet of information.
+ It can represent a chunk of XML source, or simply a word or
+ character. If the information changes, it need be replaced only
+ once, in the definition, to fix all usage.</para>
+ </footnote>.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Graphics directory (optional)</title>
+ <para>The <filename class="directory">figs/</filename> directory is an
+ optional directory where graphics for the document should be stored. If
+ graphics are screenshots that are particular to a language, the
+ <filename class="directory">figs/</filename> directory can and should be
+ stored in a language directory.</para>
+ </formalpara>
+ <formalpara>
+ <title>Translation (PO) directory (optional)</title>
+ <para>The <filename class="directory">po/</filename> directory contains
+ specially formatted files created and used by translators. The &FDP;
+ build tools use these files to create translated versions of documents.
+ The translated documents are not stored in CVS; they are created as
+ needed from these PO files.</para>
+ </formalpara>
+ <formalpara>
+ <title>Makefile (required)</title>
+ <para>The <filename>Makefile</filename> controls the build process. Its
+ content is discussed in <xref linkend="ex-makefile"/>.</para>
+ </formalpara>
+ <formalpara>
+ <title><filename>rpm-info.xml</filename> (required)</title>
+ <para>The <filename>rpm-info.xml</filename> file contains document
+ specific metadata</para>
+ </formalpara>
+d126 1
+a126 1
+PRI_LANG = en_US
+d142 48
+a189 42
+ <formalpara>
+ <title><systemitem class="macro">DOCBASE</systemitem></title>
+ <para>This variable contains the name for the main (parent) XML
+ document. Follow convention by naming your document after the
+ module name.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">PRI_LANG</systemitem></title>
+ <para>This variable contains the ISO code for the original
+ version of the document, such as
+ <systemitem>en_US</systemitem>.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">OTHERS</systemitem></title>
+ <para>This variable contains a listing of ISO codes for any
+ other versions into which the document has been translated.
+ The module must contain a <filename
+ class="directory">po/</filename> directory and a PO file for
+ any indicated additional languages.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">DOC_ENTITIES</systemitem></title>
+ <para>This variable contains a listing of any files containing
+ entity definitions. The &FDP; uses a special XML format to
+ record document-specific entities, so they can be translated and
+ built on the fly like any other XML document. An example is
+ shown later in this guide. <!-- need xref here --></para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem
+ class="macro">XMLFILES_template</systemitem></title>
+ <para>This template allows the build tools to work with the
+ document in multiple languages once it is translated. The
+ <systemitem class="macro">${1}</systemitem> marking is a
+ variable used to substitute the appropriate language. This
+ template is not terribly complicated. For a new module,
+ duplicate this section exactly except for the actual
+ filenames. Prepend the text <systemitem
+ class="macro">${1}/</systemitem>, in place of the language
+ code directory name, to each filename in your document.
+ </para>
+ </formalpara>
+d256 53
+a308 48
+ <formalpara>
+ <title><systemitem class="macro">html</systemitem></title>
+ <para>This target builds the "chunked" <abbrev>HTML</abbrev>
+ document for each defined translation. Output is placed in a
+ separate directory named <filename class="directory"><systemitem
+ class="macro">${DOCBASE}</systemitem>-<systemitem
+ class="macro">${LANG}</systemitem>/</filename>. Each
+ document section is a separate file within that
+ directory.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem
+ class="macro">html-nochunks</systemitem></title>
+ <para>This target builds the "non-chunked" <abbrev>HTML</abbrev>
+ document for each defined translation. Output is placed in a
+ single file: <filename><systemitem
+ class="macro">${DOCBASE}</systemitem>-<systemitem
+ class="macro">${LANG}</systemitem>.html</filename>; no other
+ files are created.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">pdf</systemitem></title>
+ <para>This target builds only the <abbrev>PDF</abbrev> document
+ for all document languages. <abbrev>PDF</abbrev> production is
+ currently erratic and may not work for your document.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">tarball</systemitem></title>
+ <para>This target builds only the <command>tar(1)</command>
+ archive for all document languages.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">all</systemitem></title>
+ <para>This target builds all targets listed above.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">clean</systemitem></title>
+ <para>This target deletes any temporary, or generated files, but
+ does <emphasis>not</emphasis> erase any <abbrev>HTML</abbrev>,
+ <abbrev>PDF</abbrev>, or archive files.</para>
+ </formalpara>
+ <formalpara>
+ <title><systemitem class="macro">distclean</systemitem></title>
+ <para>This target erases all <abbrev>HTML</abbrev>,
+ <abbrev>PDF</abbrev>, and archive files. This target
+ automatically invokes the <filename>clean</filename> target as
+ well.</para>
+ </formalpara>
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d321 1
+a321 1
+ linkend="s1-screenshots"/>.
+@
+
diff --git a/old-documentation-guide/en_US/publishing.xml,v b/old-documentation-guide/en_US/publishing.xml,v
new file mode 100644
index 0000000..e333c6e
--- /dev/null
+++ b/old-documentation-guide/en_US/publishing.xml,v
@@ -0,0 +1,311 @@
+head 1.4;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.3;
+locks; strict;
+comment @# @;
+
+
+1.4
+date 2009.07.09.01.12.46; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.09.16.19.05.20; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.08.03.16.41.12; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.08.03.16.38.15; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.4
+log
+ at Correct trivial caps error
+@
+text
+@<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.docbook.org/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+<chapter id="ch-publishing">
+ <title>Publishing Official Documentation</title>
+ <para>This chapter shows how to publish official &FDP; work to the
+ <systemitem class="fqdomainname">docs.fedoraproject.org</systemitem>
+ website. To publish official documentation, you must be approved to
+ write to the web repository in CVS. Access for publishing is
+ limited to contributors who have demonstrated capacity for working
+ with CVS and other project tools. Once you have acquired and are
+ comfortable with these skills, contributions as a publisher are
+ welcome.</para>
+ <section id="sn-how-site-works">
+ <title>How the Site Works</title>
+ <para>The <systemitem
+ class="fqdomainname">docs.fedoraproject.org</systemitem> website
+ is a set of PHP files and scripts. Publishers maintain these
+ files in a CVS repository, and the website host retrieves them
+ hourly to refresh the site. The host does not automatically use
+ the newest content for the website. Instead, it pulls files with
+ the CVS tag <systemitem>LIVE</systemitem> to populate the
+ website.</para>
+ <para>Each publisher sets up a local testing website on an available
+ &DISTRO; system. This site, sometimes called a
+ <firstterm>sandbox</firstterm>, allows the publisher to test and
+ view changes to documents, and ensure stability on the public
+ site.</para>
+ </section>
+ <section id="sn-sandbox-setup">
+ <title>Setting Up a Web Sandbox</title>
+ <para>To test document publishing, first set up a web sandbox on a
+ local &DISTRO; system.</para>
+ <procedure>
+ <step>
+ <para>Install the "Web Server" package group:</para>
+ <screen>su -c 'yum groupinstall "Web Server"'</screen>
+ </step>
+ <step>
+ <para>Create a folder for the web server to access the site
+ files.</para>
+ <screen>su -c 'mkdir /var/www/fedora'</screen>
+ </step>
+ <step>
+ <para>Change the permissions on this directory to make it
+ easier to access for your normal user account.</para>
+ <screen>su -c 'chown <replaceable>username</replaceable> /var/www/fedora'</screen>
+ </step>
+ <step>
+ <para>Link to the new directory from your home directory.</para>
+ <screen>ln -s /var/www/fedora ~/fedora</screen>
+ </step>
+ <step>
+ <para>Retrieve the web module from CVS.</para>
+ <screen>cd ~/fedora
+cvs -d :ext:<replaceable>username</replaceable>@@cvs.fedoraproject.org:/cvs/fedora co web</screen>
+ <note>
+ <title>Web CVS Access</title>
+ <para>You must have access to the
+ <systemitem>cvsweb</systemitem> module through the Fedora
+ Account System to check in changes. If you do not have
+ access, you can use
+ <userinput><![CDATA[:pserver:anonymous]]></userinput> in
+ place of <userinput><![CDATA[:ext:username]]></userinput>
+ above. Visit the Fedora Account System at <ulink
+ url="http://admin.fedoraproject.org/accounts/"/> for more
+ information.</para>
+ </note>
+ </step>
+ <step>
+ <para>Edit the <filename>/etc/hosts</filename> file and add the
+ following line <emphasis>after</emphasis> all other
+ lines:</para>
+ <screen>127.0.0.1 docs.localhost.localdomain</screen>
+ </step>
+ <step>
+ <para>Create a file
+ <filename>/etc/httpd/conf.d/fpo.conf</filename> with the
+ following content:</para>
+ <screen><![CDATA[NameVirtualHost *:80
+<VirtualHost *:80>
+ ServerName docs.localhost.localdomain
+ DocumentRoot /var/www/fedora/web/html/docs
+ Alias /images /var/www/fedora/web/html/images
+ Alias /css /var/www/fedora/web/html/css
+ Alias /include /var/www/fedora/web/include
+ Options Indexes FollowSymLinks
+</VirtualHost>]]></screen>
+ </step>
+ <step>
+ <para>Create a file <filename>/etc/php.d/fpo.ini</filename> with
+ the following content:</para>
+ <screen>include_path = ".:/var/www/fedora/web/include"</screen>
+ </step>
+ <step>
+ <para>Start the web server using the following command:</para>
+ <screen>su -c '/sbin/service httpd start'</screen>
+ <para>To have the web server start at every boot, use the
+ following command:</para>
+ <screen>su -c '/sbin/chkconfig httpd on'</screen>
+ </step>
+ </procedure>
+ <para>To test the new sandbox site, open a Web browser and point it
+ at the URL <uri>http://docs.localhost.localdomain</uri>.</para>
+ </section>
+ <section id="sn-creating-new-pub">
+ <title>Creating a New Publication</title>
+ <section id="sn-creating-new-pub-prepdirs">
+ <title>General Guidelines</title>
+ <para>Follow these guidelines to ensure maintainability and ease
+ of use for all publishers.</para>
+ <itemizedlist>
+ <listitem>
+ <para>Use a short, descriptive name for the document
+ directory. The module name from its Docs CVS location is
+ usually appropriate. Good examples include <filename
+ class="directory">install-guide/</filename> or <filename
+ class="directory">example-tutorial/</filename>.</para>
+ </listitem>
+ <listitem>
+ <para>Under the document directory, include a branch directory
+ if the document references specific features of a particular
+ &DISTRO; release.</para>
+ </listitem>
+ <listitem>
+ <para>Under the branch directory (or document directory if no
+ branches are necessary), make at least a <filename
+ class="directory">en_US/</filename> directory. Make an
+ additional directory for each locale that has been fully
+ translated.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="sn-creating-new-pub-content">
+ <title>Adding Content</title>
+ <para>To add content, follow the procedure below. The following
+ commands show an example of adding content for a new document
+ called the <citetitle>Foobar Tutorial</citetitle>. This document
+ includes a translation for the "zz_XX" locale and follows
+ specifics of each &DISTRO; release.</para>
+ <procedure>
+ <step>
+ <para>Make the required directory structure.</para>
+ <screen>cd ~/fedora/web/html/docs/
+mkdir foobar-tutorial
+mkdir foobar-tutorial/f7
+mkdir foobar-tutorial/f7/{en_US,zz_XX}</screen>
+ </step>
+ <step>
+ <para>Build the HTML version of each translation of the
+ document from Docs CVS.</para>
+ <screen>cd <replaceable>~/my-docs/foobar-tutorial/F-7/</replaceable>
+make html-en_US html-zz_XX</screen>
+ </step>
+ <step>
+ <para>Copy the HTML content to the web sandbox.</para>
+ <screen>cd ~/fedora/web/html/docs/foobar-tutorial/f7/
+cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/
+cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/</screen>
+ </step>
+ <step>
+ <para>Convert the HTML in each directory to PHP using the
+ provided <filename>docbookhtml2php.py</filename>
+ script.</para>
+ <screen><![CDATA[cd en_US/
+~/fedora/web/scripts/docbookhtml2php.py *html && rm -f *html
+cd ../zz_XX/
+~/fedora/web/scripts/docbookhtml2php.py *html && rm -f *html]]></screen>
+ </step>
+ <step>
+ <para>Create any necessary <filename>index.php</filename>
+ files for the overall directories. Each document and branch
+ directory must have an <filename>index.php</filename> file
+ directing users to appropriate content. In this example,
+ the necessary files are
+ <filename>foobar-tutorial/index.php</filename> and
+ <filename>foobar-tutorial/f7/index.php</filename>. You do
+ not need to write these files from scratch. Copy an existing
+ file from another document, and change it as needed to suit
+ the new document.</para>
+ <para>Depending on content, publication may include changing
+ a higher-level <filename>index.php</filename> file.</para>
+ </step>
+ <step>
+ <para>To test the changes in your sandbox, open a web browser
+ and point it at
+ <uri>http://docs.localhost.localdomain/</uri>.</para>
+ <important>
+ <title>Always Test Changes</title>
+ <para><emphasis>Do not proceed further until you test all
+ changes.</emphasis> Check that all links and index
+ pages work.</para>
+ </important>
+ </step>
+ </procedure>
+ </section>
+ <section id="creating-new-pub-push">
+ <title>Pushing Content to the Web</title>
+ <para>To push your new content to the web site, follow this
+ procedure:</para>
+ <procedure>
+ <step>
+ <para>Add all the new file content to CVS.</para>
+ <screen>cd ~/fedora/web/html/docs/
+cvs add foobar-tutorial
+cd foobar-tutorial
+cvs add f7
+cd f7
+cvs add en_US/ zz_XX/
+cvs add en_US/*php en_US/stylesheet-images/
+cvs add zz_XX/*php zz_XX/stylesheet-images/
+cvs add en_US/stylesheet-images/*png
+cvs add zz_XX/stylesheet-images/*png
+cd ../../
+cvs add foobar-tutorial/index.php
+cvs add foobar-tutorial/f7/index.php
+</screen>
+ </step>
+ <step>
+ <para>Commit the changes to CVS. Use a message that describes
+ the document being committed.</para>
+ <screen>cvs ci -m '<replaceable>message about document</replaceable>' foobar-tutorial/</screen>
+ </step>
+ <step>
+ <para>Tag the content <systemitem>LIVE</systemitem> in
+ CVS.</para>
+ <screen>cvs tag -F LIVE foobar-tutorial/</screen>
+ </step>
+ </procedure>
+ </section>
+ </section>
+</chapter>
+@
+
+
+1.3
+log
+ at Make note about cvsweb access requirement for publishing.
+@
+text
+ at d94 1
+a94 1
+</Virtualhost>]]></screen>
+@
+
+
+1.2
+log
+ at Fix typo
+@
+text
+ at d63 12
+@
+
+
+1.1
+log
+@* 0.3.1:
+ - Add new publishing chapter
+ - Include new chapter in book
+@
+text
+ at d23 1
+a23 1
+ class="fqdomainname">dos.fedoraproject.org</systemitem> website
+@
+
diff --git a/old-documentation-guide/en_US/rpm-info.xml,v b/old-documentation-guide/en_US/rpm-info.xml,v
new file mode 100644
index 0000000..0cae894
--- /dev/null
+++ b/old-documentation-guide/en_US/rpm-info.xml,v
@@ -0,0 +1,323 @@
+head 1.14;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.12
+ LIVE:1.5;
+locks; strict;
+comment @# @;
+
+
+1.14
+date 2008.04.10.02.34.37; author pfrields; state Exp;
+branches;
+next 1.13;
+
+1.13
+date 2007.12.15.21.51.46; author pfrields; state Exp;
+branches;
+next 1.12;
+
+1.12
+date 2007.11.15.02.07.47; author pfrields; state Exp;
+branches;
+next 1.11;
+
+1.11
+date 2007.09.16.19.14.24; author pfrields; state Exp;
+branches;
+next 1.10;
+
+1.10
+date 2007.08.03.16.38.15; author pfrields; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2007.07.29.23.55.25; author pfrields; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2007.07.28.22.06.16; author pfrields; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2007.07.01.18.20.12; author pfrields; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.06.29.00.10.59; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.06.23.05.40.57; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.06.23.05.24.16; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2006.11.29.00.29.48; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2006.11.23.20.40.05; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2006.11.23.02.24.17; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.14
+log
+ at Add L10n chapter to DocGuide (#441190)
+@
+text
+@<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE rpm-info PUBLIC "-//Fedora//DTD Docs RPM-INFO V1.0//EN"
+"http://docs.fedoraproject.org/dtds/rpm-info.dtd">
+<rpm-info>
+ <colophon>
+ <worker id="TammyFox" wholename="Tammy Fox" email="tfox@@redhat.com"
+ surname="Fox" firstname="Tammy" initials="TF"/>
+ <worker id="JohnrayFuller" wholename="Johnray Fuller"
+ email="jfuller@@redhat.com" surname="Fuller" firstname="Johnray"
+ initials="JF"/>
+ <worker id="SandraMoore" wholename="Sandra Moore" email="smoore@@redhat.com"
+ surname="Moore" firstname="Sandra" initials="SM"/>
+ <worker id="PaulWFrields" wholename="Paul W. Frields"
+ email="stickster@@gmail.com" surname="Frields" firstname="Paul"
+ othername="W." initials="PWF"/>
+ <worker id="FDP" wholename="Fedora Documentation project"
+ email="docs@@fedoraproject.org" surname="Project" firstname="Fedora
+ Documentation" initials="FDP"/>
+ </colophon>
+ <author worker="FDP"/>
+ <license>
+ <rights>OPL</rights>
+ <version>1.0</version>
+ </license>
+ <copyright>
+ <year>2003</year>
+ <year>2004</year>
+ <year>2005</year>
+ <year>2006</year>
+ <year>2007</year>
+ <year>2008</year>
+ <holder>Red Hat, Inc. and others</holder>
+ </copyright>
+ <title>Fedora Documentation Guide</title>
+ <desc>Guidelines and procedures for producing documentation for Fedora</desc>
+ <changelog order="newest-first">
+ <revision date="2008-04-09" number="0.4">
+ <author worker="PaulWFrields"/>
+ <details>Add L10n chapter (#441190)</details>
+ </revision>
+ <revision date="2007-12-15" number="0.3.3">
+ <author worker="PaulWFrields"/>
+ <details>Fix some organization and missing targets (#371531)</details>
+ </revision>
+ <revision date="2007-11-14" number="0.3.2.1">
+ <author worker="PaulWFrields"/>
+ <details>Add link to DocBook XML help for Windows</details>
+ </revision>
+ <revision date="2007-09-16" number="0.3.2">
+ <author worker="PaulWFrields"/>
+ <details>Add guidance on CVS web access and previewing work</details>
+ </revision>
+ <revision date="2007-08-03" number="0.3.1">
+ <author worker="PaulWFrields"/>
+ <details>Add new chapter on publishing</details>
+ </revision>
+ <revision date="2007-07-29" number="0.3.0.3">
+ <author worker="PaulWFrields"/>
+ <details>Include information on LINGUAS usage</details>
+ </revision>
+ <revision date="2007-07-28" number="0.3.0.2">
+ <author worker="PaulWFrields"/>
+ <details>Remove unnecessary chapter on XML tags</details>
+ </revision>
+ <revision date="2007-07-01" number="0.3.0.1">
+ <author worker="PaulWFrields"/>
+ <details>Assorted fixes to reflect newer version of reality</details>
+ </revision>
+ <revision date="2007-06-23" number="0.3.0">
+ <author worker="PaulWFrields"/>
+ <author worker="TammyFox"/>
+ <author worker="JohnrayFuller"/>
+ <author worker="SandraMoore"/>
+ <details>Update to new content and build requirements</details>
+ </revision>
+ </changelog>
+</rpm-info>
+@
+
+
+1.13
+log
+ at Update metadata
+@
+text
+ at d31 1
+d37 4
+@
+
+
+1.12
+log
+ at Update metadata
+@
+text
+ at d36 4
+@
+
+
+1.11
+log
+ at Update metadata and bump to 0.3.2
+@
+text
+ at d36 4
+@
+
+
+1.10
+log
+@* 0.3.1:
+ - Add new publishing chapter
+ - Include new chapter in book
+@
+text
+ at d36 4
+@
+
+
+1.9
+log
+@* 0.3.0.3:
+ - Add information on po/LINGUAS
+
+* 0.3.0.2:
+ - Delete unnecessary tags section and references
+@
+text
+ at d36 4
+@
+
+
+1.8
+log
+ at Update document metadata
+@
+text
+ at d36 4
+@
+
+
+1.7
+log
+ at Additional upgrades and changes; this will go to publication ASAP.
+@
+text
+ at d36 4
+@
+
+
+1.6
+log
+ at Some content updates, push new bugfix rev 0.3.0.1, no publishing needed yet
+@
+text
+ at d36 1
+a36 1
+ <revision date="2007-06-28" number="0.3.0.1">
+@
+
+
+1.5
+log
+ at Revise to remove overly long authorship list
+@
+text
+ at d36 4
+@
+
+
+1.4
+log
+ at This is finally being updated; I hope to finish this in the next week.
+@
+text
+ at d14 5
+a18 1
+ email="stickster@@gmail.com" surname="Frields" firstname="Paul" initials="W."/>
+d20 1
+a20 4
+ <author worker="TammyFox"/>
+ <author worker="JohnrayFuller"/>
+ <author worker="SandraMoore"/>
+ <author worker="PaulWFrields"/>
+d31 1
+a31 5
+ <holder>Red Hat, Inc.</holder>
+ <holder>Tammy Fox</holder>
+ <holder>Johnray Fuller</holder>
+ <holder>Sandra Moore</holder>
+ <holder>Paul W. Frields</holder>
+@
+
+
+1.3
+log
+ at Now with 100% extra validation
+@
+text
+ at d2 2
+a3 1
+<!DOCTYPE rpm-info SYSTEM "../../docs-common/packaging/rpm-info.dtd">
+d29 1
+d39 1
+a39 1
+ <revision date="2005-09-18" number="0.2.6.3">
+d44 1
+a44 1
+ <details>Update to new build requirements</details>
+@
+
+
+1.2
+log
+ at Don't use undeclared entities
+@
+text
+ at d35 10
+a44 2
+ <desc>Guidelines and procedures for producing documentation for &FED;</desc>
+ <changelog order="newest-first"/>
+@
+
+
+1.1
+log
+ at Add en_US directory, new file structures
+@
+text
+ at d28 1
+a28 1
+ <holder>&FORMAL-RHI;</holder>
+@
+
diff --git a/old-documentation-guide/en_US/style.xml,v b/old-documentation-guide/en_US/style.xml,v
new file mode 100644
index 0000000..79c1c9a
--- /dev/null
+++ b/old-documentation-guide/en_US/style.xml,v
@@ -0,0 +1,2015 @@
+head 1.2;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.2
+ LIVE:1.2;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2007.02.03.22.29.37; author kwade; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at updating all section usage and associated ID tags
+@
+text
+@<!-- $Id: -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+
+<chapter id="ch-style">
+
+ <title>Style</title>
+
+ <para>
+ Writing good technical documentation is not simply reproducing
+ command lines and instruction sets. Good documentation is easy to
+ read, understand, and translate, and presents a concise logical
+ progression of concepts. Good documentation can also be defined by
+ what it does <emphasis>not</emphasis> contain. Your tutorial should
+ avoid:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Excessive wordiness
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Unnecessary or undefined jargon
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Grammatical or spelling errors
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ References to yourself or your experiences
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Remarks which might offend or confuse any reader
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ This chapter contains style rules and guidelines for writing &FED;
+ documentation. Guidelines are not the same as rules. It is
+ acceptable to violate a guideline when it makes your material easier
+ to understand. Follow guidelines whenever possible, but follow
+ rules at all times. Assume any advice is a guideline unless
+ identified otherwise.
+ </para>
+
+ <section id="sn-intro-to-style">
+
+ <title>Why Style Is Important</title>
+
+ <para>
+ Writing well comes naturally to almost no one. It is a skill that
+ professional writers, even famous ones, must practice constantly.
+ <firstterm>Style</firstterm>
+ <indexterm><primary>style</primary></indexterm> is the quality
+ that separates elegant writing from the merely functional.
+ </para>
+ <para>
+ Elegance comes in many forms. In prose and poetry, elegant
+ writing may not follow some (or any) common rules of grammar,
+ syntax, or spelling. A good example is Episode 18, "Penelope," in
+ James Joyce's novel <citetitle>Ulysses</citetitle><footnote
+ id='fn-ulysses'>
+ <para>
+ For example, refer to. <ulink
+ url="http://www.online-literature.com/james_joyce/ulysses/18/">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>.
+ Please note that this example contains some mature themes and
+ language, and is not suitable for all readers.
+ </para>
+ </footnote>. There, Joyce uses long streams of words without
+ punctuation to simulate a character's internal consciousness. By
+ violating basic rules of grammar and syntax, Joyce simulates the
+ disorganized but loosely connected thought patterns of the
+ narrator.
+ </para>
+ <para>
+ Technical documentation, however, should always respect these
+ rules. The more a document departs from standard language usage,
+ the more difficult the material becomes for the reader. For
+ example, readers may not be native speakers of the language used,
+ or they might be reading a translation. If the writer uses slang,
+ idioms, or jargon, a reader or translator may easily become
+ confused. The following example compares two different written
+ executions of the same idea:
+ </para>
+ <example>
+ <title>Incorrect style</title>
+
+ <!-- I prefer "incorrect," because I think terms such as
+ "problematic" are mealy-mouthed. They remind me of the late
+ 1980's English textbook trend toward the politically correct yet
+ wholly unhelpful "standard/nonstandard." But then, I tend to be
+ dogmatic; it's probably my Catholic upbringing. [PWF] -->
+
+ <para>
+ So you made the changes I showed you in the last section. What's
+ the next thing you should do? Just pop your thumb drive onto
+ your system and read the <filename>messages</filename> log. When
+ you see "USB device found," then Bob's your uncle.
+ </para>
+ </example>
+ <example>
+ <title>Correct style</title>
+
+ <!-- I prefer "correct." See above. [PWF] -->
+
+ <para>
+ After you complete the configuration changes above, attach the
+ USB removable media to your system. Use the
+ <command>dmesg</command> command to examine the kernel message
+ log. The message <computeroutput>USB device
+ found</computeroutput> indicates that your device was
+ installed successfully.
+ </para>
+ </example>
+ <para>
+ The first example is more conversational English, which is not
+ appropriate for official written documentation. The second
+ example is more formal, but as a result it is easier to
+ comprehend, both for native readers and translators.
+ </para>
+ <para>
+ Following style rules and guidelines also makes readers more
+ comfortable with a set of documents. Consistent style enhances
+ the professional appearance of documentation, and its perceived
+ value. On the other hand, lapses in punctuation or poor grammar
+ negatively affect a reader's reaction to written material. A
+ reader can feel that an otherwise correct technical document is
+ lacking in authority, simply because it is poorly written. Readers
+ feel at ease when they do not have to struggle to understand an
+ author's use of language.
+ </para>
+ <para>
+ This chapter cannot possibly cover enough material to make every
+ reader a good writer. Some manuals devoted entirely to writing
+ style are themselves hundreds of pages long. This chapter
+ provides enough guidelines for intermediate writers to understand
+ style usage in technical documentation.
+ </para>
+ <para>
+ If you are not a practiced writer, whether of technical
+ documentation or otherwise, you may benefit from other style
+ resources. The following list is far from comprehensive, but
+ provides a starting point:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <citetitle>The Elements of Style</citetitle>, by William
+ Strunk. Basic rules and links to online versions can be found
+ at: <ulink
+ url="http://en.wikipedia.org/wiki/The_Elements_of_Style">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>
+ </para>
+ </listitem>
+<!-- placeholder for when it's ready
+ <para>
+ <citetitle>The Elements of Style</citetitle>, by William
+ Strunk. Fedora Docs Project version: <ulink
+ url="http://fedora.redhat.com/docs/eos-guide-en/">http://fedora.redhat.com/docs/eos-guide-en/</ulink>
+ </para>
+-->
+ <listitem>
+ <para>
+ <citetitle>The Chicago Manual of Style</citetitle>, by the
+ University of Chicago Press. Online version: <ulink
+ url="http://www.chicagomanualofstyle.org/">http://www.chicagomanualofstyle.org/</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <citetitle>Paradigm Online Writing Assistant</citetitle>,
+ maintained by Chuck Guilford, Ph.D. Online only: <ulink
+ url="http://www.powa.org/">http://www.powa.org/</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ There are many free software documentation projects which have
+ developed their own style guidelines. This chapter, in fact,
+ draws heavily on the <citetitle>GNOME Documentation Style
+ Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may
+ read the original <citetitle>GDSG</citetitle> at <ulink
+ url='http://developer.gnome.org/documents/style-guide/'>http://developer.gnome.org/documents/style-guide/</ulink>.
+ </para>
+
+ </section>
+
+ <section id="sn-tech-docs-fundamentals">
+
+ <title>Fundamental Concepts of Technical Documentation</title>
+
+ <note>
+ <title>Bibliographic Information</title>
+ <para>
+ This section is drawn primarily from the
+ <citetitle>GDSG</citetitle>.
+ </para>
+ </note>
+
+ <!-- This section will reproduce mostly what is in Chapter 1 of
+ the GDSG. There may be minor changes. FIXME: Make sure the
+ appropriate front matter of the Documentation Guide includes
+ attribution as required by the GNU FDL. -->
+
+ <para>
+ This chapter provides a brief introduction to writing technical
+ documentation.
+ </para>
+
+ <section id="sn-fundamentals-1">
+ <title>General Style Requirements</title>
+ <para>
+ Technical writing for the &FP; imposes special constraints
+ beyond the basic requirements of good prose. Good &FED;
+ technical documentation has the following characteristics:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Comprehensive</term>
+ <listitem>
+ <para>
+ Describe all of the functionality of a product. Do not
+ omit functionality that you regard as irrelevant for the
+ user.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Conforming</term> <!-- I'm having issues with the
+ sketchy definition of this non-dictionary word and the
+ associated text. Not wrong, per se, just wishing for
+ something better. This note shall remind us! - kwade -->
+ <!-- Hopefully this change helps. Makes sense according to the
+ gdict tool in Core, at least. - PWF -->
+ <listitem>
+ <para>
+ Describe what you see. Do not describe what you want to
+ see. Present your information in the order that users
+ experience the subject matter.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Clear</term>
+ <listitem>
+ <para>
+ Read <citetitle>The Elements of Style</citetitle> (<ulink
+ url="http://en.wikipedia.org/wiki/The_Elements_of_Style">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>)
+ to help make your writing clear.
+ </para>
+<!-- placeholder for when this is published:
+ <para>
+ Read <citetitle>The Elements of Style</citetitle>
+ &FED;-version (<ulink
+ url="http://fedora.redhat.com/docs/eos-guide-en/">http://fedora.redhat.com/docs/eos-guide-en/</ulink>)
+ to help make your writing clear.
+ </para>
+-->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Consistent</term>
+ <listitem>
+ <para>
+ Use agreed vocabulary throughout your documentation. Use
+ the same vocabulary as other writers who are working on
+ related documentation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Concise</term>
+ <listitem>
+ <para>
+ Review your work frequently as you write your document.
+ Ask yourself which words you can take out. Refer to <xref
+ linkend="sn-fundamentals-2"/> for specific guidelines.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-2">
+ <title>Golden Rules</title>
+ <para>
+ This section contains some basic style guidelines. Subsequent
+ sections in this chapter expand on these guidelines to give more
+ detailed guidance.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Golden Rule 1: Be brief</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Limit each sentence to fewer than 25 words.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each procedure step to 23 words.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-1-wrong">
+ <title>Incorrect: Too long</title>
+ <para> Under normal operating conditions, the kernel does
+ not always immediately write file data to the disks,
+ storing it in a memory buffer and then periodically
+ writing to the disks to speed up operations.
+ </para>
+ </example>
+ <example id="ex-golden-rule-1-right">
+ <title>Correct: Less wordy</title>
+ <para>
+ Normally, the kernel stores the data in memory prior to
+ periodically writing the data to the disk.
+ </para>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Golden Rule 2: Be organized</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Limit each paragraph to one topic.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each sentence to one idea.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit each procedure step to one action.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-golden-rule-2-wrong">
+ <title>Incorrect: Disorganized topics</title>
+ <para>
+ The <application>Workspace Switcher</application> applet
+ helps you navigate all of the virtual desktops available
+ on your system. The X Window system, working in hand
+ with a piece of software called a <emphasis>window
+ manager</emphasis>, allows you to create more than one
+ virtual desktop, known as
+ <emphasis>workspaces</emphasis>, to organize your work,
+ with different applications running in each workspace.
+ The <application>Workspace Switcher</application> applet
+ is a navigational tool to get around the various
+ workspaces, providing a miniature road map in the GNOME
+ panel showing all your workspaces and allowing you to
+ switch easily between them.
+ </para>
+ </example>
+ <example id="ex-golden-rule-2-right">
+ <title>Correct: Organized topics</title>
+ <para>
+ Use the <application>Workspace Switcher</application> to
+ add new <emphasis>workspaces</emphasis> to the GNOME
+ Desktop. You can run different applications in each
+ workspace. The <application>Workspace
+ Switcher</application> applet provides a miniature map
+ that shows all of your workspaces. You can use the
+ <application>Workspace Switcher</application> applet to
+ switch between workspaces.
+ </para>
+ </example>
+ <tip>
+ <para>
+ Plan the order of paragraphs before you start writing.
+ Decide which topic you want to cover in each paragraph.
+ </para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Golden Rule 3: Be demonstrative</term>
+ <listitem>
+ <para>
+ Use explicit examples to demonstrate how an application
+ works. Provide instructions rather than descriptions.
+ </para>
+ <example id="ex-golden-rule-3-wrong">
+ <title>Incorrect: Describes but does not
+ demonstrate</title>
+ <para>
+ There is a text box that you can use to find out the
+ definition of a word.
+ </para>
+ </example>
+ <example id="ex-golden-rule-3-right">
+ <title>Correct: Demonstrates usage</title>
+ <para>
+ To request a definition of a word, type the word in the
+ text box, then select <guilabel>Lookup</guilabel>.
+ </para>
+ </example>
+ <tip>
+ <para>
+ Do not apply this guideline too rigidly. Sometimes you
+ must explain how software works to support your how-to
+ examples.
+ </para>
+ </tip>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-golden-rule-4">
+ <term>Golden Rule 4: Be objective</term>
+ <listitem>
+ <para>
+ Write in a neutral tone.
+ </para>
+ <example id="ex-golden-rule-4-wrong">
+ <title>Incorrect: Sentence takes sides</title>
+ <para>
+ The applet is a handy little screen grabber.
+ </para>
+ </example>
+ <example id="ex-golden-rule-4-right">
+ <title>Correct: Sentence is objective</title>
+ <para>
+ Use the applet to take screenshots.
+ </para>
+ </example>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="sn-fundamentals-3">
+
+ <title>Tone</title>
+ <para>
+ Inappropriate tone hinders reader access to information. A
+ neutral tone free of opinion or personal flavor improves the
+ reader's comprehension. Neutral tone helps writers to work in
+ parallel on a large technical documentation project.
+ Furthermore, additional writers may join the project at any
+ time. Use of a neutral tone helps to achieve consistency across
+ a documentation set, and thereby facilitates user access to
+ information. The best way to achieve a common, neutral tone is
+ to apply the following principles:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Avoid humor</term>
+ <listitem>
+ <para>
+ Humor distracts from the information you are trying to
+ provide. Humor also makes documentation difficult to
+ translate. Stay factual.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid personal opinions</term>
+ <listitem>
+ <para>
+ Whether you think a function is useful or woeful is
+ irrelevant. Report the function to the user, with
+ instructions about how to use the function. Stay
+ accurate.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid colloquial language</term>
+ <listitem>
+ <para>
+ Colloquial language is difficult to translate and usually
+ culture-specific. Stay neutral.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid topical expressions</term>
+ <listitem>
+ <para>
+ An expression that is in common use today might convey
+ something completely different tomorrow. Stay technical.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid aspirational statements</term>
+ <listitem>
+ <para>
+ Statements about the future developments of a product do
+ not belong in technical documentation. Write about what
+ you see right now. Stay real.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-fundamentals-4">
+ <title>Reaching the Right Audience</title>
+ <para>
+ All of the decisions that you make about the structure and
+ content of a manual follow from an understanding of the
+ audience. Consider how the audience accesses the documentation,
+ what sort of information the audience needs, and the experience
+ level of the audience. Usually, you need to create
+ documentation that is suitable for different audiences. The
+ following sections introduce some of the audience-related topics
+ you need to consider.
+ </para>
+ </section>
+ <section id="sn-fundamentals-6">
+ <title>User Motivation</title>
+ <para>
+ Do not waste the time of the user who looks for information in
+ your documentation. Users do not read technical documentation
+ for entertainment. Users usually have specific questions. You
+ need to give clear answers to those questions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-7">
+ <title>New Users</title>
+ <para>
+ New users to &FC; are likely to consult online tutorials for
+ guidance about unfamiliar applications or functionality. Each
+ tutorial should contain enough introductory information to tell
+ new users how to start using the relevant functions. Each
+ tutorial should also contain enough usage instructions to tell
+ users the different actions that they can perform with the
+ command or function. Keep these instructions task-oriented. Do
+ not describe GUI screens, dialogs, and dialog elements in a
+ tutorial, unless there is an unusual feature that affects your
+ instructions.
+ </para>
+ </section>
+ <section id="sn-fundamentals-8">
+ <title>Experienced Users</title>
+ <para>
+ Experienced users are more likely to use documentation as a
+ reference. The documentation therefore needs to be complete,
+ well-organized, and in the case of printed manuals,
+ well-indexed.
+ </para>
+ </section>
+ <section id="sn-fundamentals-9">
+ <title>Do Not Offend Your Audience</title>
+ <para>
+ To avoid offending your readers, apply the following guidelines
+ to your documentation:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Avoid insider language</term>
+ <listitem>
+ <para>
+ Insider language includes both undefined jargon and the
+ tendency of the computer community to shorten words. For
+ example, use the term <literal>documentation</literal>
+ instead of the term <literal>docs</literal>. A term may
+ be jargon if it fails all the following conditions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The term does not appear in the <citetitle>&FED;
+ Jargon Buster</citetitle> (<ulink
+ url="http://fedora.redhat.com/docs/jargon-buster/">http://fedora.redhat.com/docs/jargon-buster/</ulink>).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The term does not appear in the <citetitle>American
+ Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/
+ </ulink>).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The term does not appear in the glossary of the manual
+ that you are writing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The term is not defined in the body text of the manual
+ that you are writing.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid gender-specific language</term>
+ <listitem>
+ <para>
+ Pronoun constructions such as <literal>his/her</literal>
+ or <literal>s/he</literal> do not exist. There is no need
+ to identify gender in your instructions.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid culture-specific language</term>
+ <listitem>
+ <para>
+ There is little point in giving an example that everyone
+ in your town knows about, but is a complete mystery to
+ everyone else in the world.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Avoid talking down to your reader</term>
+ <listitem>
+ <para>
+ There are few experiences more irritating for a user than
+ documentation that says an action is easy or quick, when
+ in fact the user cannot complete the action. Do not
+ qualify or prejudge actions.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Other parts of this guide discuss in more detail tone and
+ language usage that can cause offense.
+ </para>
+
+ </section>
+
+ </section>
+
+ <section id="sn-grammar-and-usage">
+
+ <title>Grammar and Usage Guidelines</title>
+
+ <note>
+ <title>Bibliographical Information</title>
+ <para>
+ This section is drawn partly from the
+ <citetitle>GDSG</citetitle>, and partly from <citetitle>The
+ Elements of Style</citetitle>, updated as necessary for the
+ needs of 21st-century technical documentation writers.
+ </para>
+ </note>
+
+ <!-- FIXME: Again, check attribution viz. GNU FDL. This will be more work
+ than the previous section. -->
+
+ <para>
+ This section contains an alphabetical list of grammar and usage
+ guidelines for use in &FED; documentation. Many of these
+ guidelines are only applicable to English-language usage, refer to
+ the <citetitle>American Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ and the <citetitle>Chicago Manual of Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Abbreviations</term>
+ <listitem>
+ <para>
+ A shortened form of a word or phrase that takes the place of
+ the full word or phrase, such as <literal>Dr.</literal>,
+ <literal>a.m.</literal>, <literal>p.m.</literal>, and so on.
+ Apply the following rules when you use abbreviations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Avoid creating new abbreviations. Unfamiliar
+ abbreviations can confuse rather than clarify a concept.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not explain or expand familiar abbreviations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not include familiar abbreviations in the glossary of
+ your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ For abbreviations of phrases, such as
+ <literal>i.e.</literal> for "in other words" and
+ <literal>e.g.</literal> for "for example", do not use the
+ abbreviation. Spell out the entire phrase.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adjectives</term>
+ <listitem>
+ <para>
+ Use adjectives with caution. If an adjective is necessary
+ to differentiate between items, then use adjectives. In all
+ cases, test whether the phrase can stand alone without the
+ adjective.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Acronyms</term>
+ <listitem>
+ <para>
+ A term that represents a multi-word term. Typically,
+ acronyms are formed in the following ways:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ From the first letters of each word in a compound term,
+ for example Table of Contents (TOC).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ From recognizable parts of a compound term, such as GNU
+ Object Model Environment (GNOME).
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Apply the following rules when you use acronyms:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ On the first occurrence of an acronym, spell out the
+ full term, with the acronym in parentheses.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not spell out the full compound for well-known
+ acronyms, unless you think the information is useful for
+ readers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Avoid creating new acronyms. Unfamiliar acronyms can
+ confuse rather than clarify a concept.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Write the acronym in uppercase letters, unless there is
+ a compelling case for lowercase.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Include the acronym and the full term in the glossary of
+ your manual.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Adverbs</term>
+ <listitem>
+ <para>
+ Use adverbs with caution. If an adverb is necessary to
+ qualify the function of a component, then use an adverb. In
+ all cases, test whether the phrase can stand alone without
+ the adverb. Classic superfluous adverbs
+ <literal>simply</literal>, <literal>easily</literal>,
+ <literal>quickly</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Anthropomorphism</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not apply emotions, desires, or opinions to software
+ applications.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not apply a sense of location or dimension to a
+ software application. A user can not be "in" a text
+ editor.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Articles</term>
+ <listitem>
+ <para>
+ Do not use the definite article <literal>the</literal> to
+ begin any of the following items:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Manual titles
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chapter titles
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Headings
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Figure captions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Table captions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Callouts
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Apostrophe</term>
+ <listitem>
+ <para>
+ Do not use apostrophes except where absolutely required
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote possession.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote contractions.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use apostrophes to denote plurals.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example id="ex-apostrophe-wrong">
+ <title>Incorrect: Apostrophes</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <guimenu>Main Menu's</guimenu>
+ <guimenuitem>Help</guimenuitem> option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ don't use the default option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ several SCSI disk's
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-apostrophe-right">
+ <title>Correct: No apostrophes</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <guimenuitem>Help</guimenuitem> option on the
+ <guimenu>Main Menu</guimenu>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ do not use the default option
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ several SCSI disks
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Brackets</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Do not use brackets [such as these] as a substitute for
+ parentheses (such as these).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use brackets for optional command line entries.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use angle brackets to indicate variables in text,
+ instead use the <sgmltag
+ class="starttag">replaceable</sgmltag> tag. Refer to
+ <xref linkend="sn-xml-tags-replaceable"/> for
+ information about using this tag.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Capitalization</term>
+ <listitem>
+ <para>
+ Capitalize in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ All letters in acronyms, unless the acronym is a
+ well-known exception
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of the first word in a list
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of the first word in a callout
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a key name, such as the
+ <keycap>Shift</keycap> key
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a sentence
+ </para>
+ <note>
+ <title>Command Names</title>
+ <para>
+ Avoid starting a sentence with a command name or
+ application name that has a lowercase initial letter.
+ </para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>
+ Initial letter of a complete sentence after a colon
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not capitalize in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ A compound term that is followed by an abbreviation or
+ an acronym
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When you want to emphasize something
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Variable names
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The initial letter of an incomplete sentence after a
+ colon
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Captions</term>
+ <listitem>
+ <para>
+ Use the same rules as for headings, for all captions
+ accompanying figures and tables. Do not put a period at the
+ end of a caption.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Colon</term>
+ <listitem>
+ <para>
+ Use a colon in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To introduce a list
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Before an explanation
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ After an introduction
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use a colon in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To introduce a figure or a table
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To introduce headings
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ At the end of an introduction to a procedure
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Column headings</term>
+ <listitem>
+ <para>
+ Use the same rules as for headings.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Comma</term>
+ <listitem>
+ <para>
+ Use commas in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To separate items in a series
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To separate the parts of a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To separate nonrestrictive phrases
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Instead of dashes to set off appositives
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With <emphasis>for example</emphasis> and similar
+ expressions
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use commas in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ In a series of adjectives used as one modifier
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Between two short independent clauses
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Commands</term>
+ <listitem>
+ <para>
+ Do not use commands as verbs.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry id="vle-contractions">
+ <term>Contractions</term>
+ <listitem>
+ <para>
+ Do not use contractions such as <emphasis>can't</emphasis>,
+ <emphasis>don't</emphasis>, or <emphasis>isn't</emphasis>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Dash</term>
+ <listitem>
+ <para>
+ Do not use the em dash or the en dash. Use a paragraph
+ break or a colon instead, where you want to create an
+ introductory piece of text. If you have several items that
+ you want to introduce, then you can use a variable list.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Ellipsis</term>
+ <listitem>
+ <para>
+ Use an ellipsis in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To show that you have omitted something from a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To indicate a pause when you quote displayed text
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Fractions</term>
+ <listitem>
+ <para>
+ Follow these rules when using fractions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use numerals for fractions in tables and in units of
+ measurement, but spell out fractions in prose.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use a space between a numeral and a related fraction, if
+ there is a possible ambiguity. For example: 1 1/2
+ instead of 11/2.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If a fraction is used in a compound modifier, insert a
+ hyphen between the fraction and the unit of measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Gender</term>
+ <listitem>
+ <para>
+ Refer to <xref linkend="sn-fundamentals-9"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Grammar</term>
+ <listitem>
+ <para>
+ Use standard American English grammar rules, refer to the
+ <citetitle>Chicago Manual of Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">
+ http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Headings</term>
+ <listitem>
+ <para>
+ Use the following capitalization rules in headings:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Initial uppercase letter of the first word
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for all nouns, adjectives, and
+ verbs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All lowercase letters for conjunctions, articles, and
+ prepositions of fewer than four letters
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for prepositions of four
+ letters or longer
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Initial uppercase letter for conjunctions of four
+ letters or longer
+ </para>
+ </listitem>
+ </itemizedlist>
+ <!-- <para> See <xref linkend="infodesign-2"/> for more
+ information about headings. </para> -->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Hyphen</term>
+ <listitem>
+ <para>
+ Use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para> With a numeral in a compound modifier
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To prevent ambiguity
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With some standard prefixes and suffixes. Use the
+ <citetitle>American Heritage Dictionary</citetitle>
+ (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ for guidance
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In spelled-out fractions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In variable names of two or more words, such as
+ <replaceable>directory-name</replaceable>. Note:
+ <replaceable>filename</replaceable> is an exception.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Do not use hyphens in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ For industry-accepted terms
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To construct verbs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With an adverb ending in <emphasis>ly</emphasis>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With numerals as single modifiers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With a word that is listed as unhyphenated in the
+ <citetitle>American Heritage Dictionary</citetitle>
+ (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>),
+ and that uses a common prefix
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ With trademarked terms
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Latin terms</term>
+ <listitem>
+ <para>
+ Do not use Latin terms. Use an equivalent English term
+ instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Like</term>
+ <listitem>
+ <para>
+ Do not use the term <emphasis>like</emphasis> to denote
+ equivalence or similarity.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Lists</term>
+ <listitem>
+ <para>
+ Introduce a list with a complete sentence that ends with a
+ colon.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numbers</term>
+ <listitem>
+ <para>
+ Spell out numbers in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para> Numbers from zero through nine unless the number is
+ part of a measurement
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Approximations
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Extreme values such as <emphasis>million</emphasis>, but
+ precede the value with a numeral
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Any number that begins a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A number that is immediately followed by a numeral, for
+ example: <literal>two 10 MB files</literal>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Numerals</term>
+ <listitem>
+ <para>
+ Use numerals in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The number 10 or greater
+ </para>
+ </listitem>
+ <listitem>
+ <para> Negative numbers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Most fractions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Percentages
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Decimals
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Measurements
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Units of time smaller than one second
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ References to bits and bytes
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Parentheses</term>
+ <listitem>
+ <para>
+ Use parentheses in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To contain the abbreviation of a term on the first
+ occurrence of the full term
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In man page references, specifically the section number
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Period</term>
+ <listitem>
+ <para>
+ Use a period in the following situations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To end a sentence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In file and directory names
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In abbreviations that can be mistaken for words, such as
+ a.m. and U.S.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation</term>
+ <listitem>
+ <para>
+ Use standard American English punctuation rules. In
+ addition to the specific points of punctuation in this
+ section, refer also to the <citetitle>Chicago Manual of
+ Style</citetitle> (<ulink
+ url="http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Punctuation in numbers</term>
+ <listitem>
+ <para>
+ Do not use a comma in numerals of four digits. Use a comma
+ in numerals of more than four digits.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Quotation marks</term>
+ <listitem>
+ <para>
+ Use quotation marks to indicate material that is taken
+ verbatim from another source. Do not use quotation marks to
+ excuse terms from legitimacy. If the term is not
+ legitimate, then use another term. If you must use that
+ term, declare the term in the glossary and make the term
+ legitimate.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>See v. Refer to</term>
+ <listitem>
+ <para>
+ When referring a user to another resource, use "refer to"
+ instead of "see", and "refer also to" instead of "see also".
+ This differentiates from the <sgmltag
+ class="starttag">see</sgmltag> and <sgmltag
+ class="starttag">seealso</sgmltag> tags that are used in
+ indexing. These tags create special links in the index. To
+ be consistent throughout the document, we reserve the
+ special words "see" and "see also" for hyperlinked index
+ references, and use "refer to" and "refer also to" for
+ non-hyperlinked and non-indexed references.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Semicolon</term>
+ <listitem>
+ <para>
+ Do not use semicolons.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Slash</term>
+ <listitem>
+ <para>
+ Except where required as part of a filename, do not use
+ slashes "/" in your writing. The construction
+ <literal>and/or</literal>, for example, does not exist. Use
+ one or the other term instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Spelling</term>
+ <listitem>
+ <para>
+ Use standard American English spelling rules, refer to the
+ <citetitle>American Heritage Dictionary</citetitle> (<ulink
+ url="http://www.bartleby.com/61/">http://www.bartleby.com/61/</ulink>)
+ for guidelines.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Titles</term>
+ <listitem>
+ <para>
+ For manual titles use the same rules as for headings.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Units</term>
+ <listitem>
+ <para>
+ Follow these rules when using units:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use standard abbreviations for units of measurements, do
+ not invent your own abbreviations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!-- See <xref linkend="units"/> for a list of units
+ relevant to the GNOME Desktop. --> For further
+ guidelines, refer to the <citetitle>IEEE Standard
+ Dictionary of Electrical and Electronics
+ Terms</citetitle>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use periods for abbreviated units that might be mistaken
+ for a word.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Most standard abbreviations of units account for both
+ singular and plural usage.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Insert a space between the numeral and the unit of
+ measurement.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="sn-composition-tips">
+
+ <title>Composition Tips</title>
+
+<!--
+
+ This section will collect miscellanea and advice for specific
+ situations that the FDP editors encounter. I hope they will feel
+ free to e-mail me sticky situations or particularly interesting
+ examples of work they've beautified. Hopefully not too much will be
+ drawn from my own work! - PWF.
+
+-->
+
+ <para>
+ This section contains usage tips based on situations the &FDP;
+ editors have encountered in the past. You should read and
+ understand these examples to improve your own documentation. The
+ &FDP; editors welcome additional examples.
+ </para>
+
+ <section id="sn-misc-active-voice">
+ <title>Active Voice</title>
+ <para>
+ Always use active voice, except when it is awkward to do so. The
+ tutorial tells the user how to accomplish a task, and should
+ give instructions clearly and concisely. Avoid using "must,"
+ "need to," and the like. These words are redundant in a
+ tutorial, since the reader assumes you are outlining necessary
+ steps to accomplish a task. Also avoid using "maybe," "might,"
+ and other words that indicate you are unsure about the subject
+ matter. Your tutorial should cover a subject authoritatively.
+ The reader should never be concerned about unknown effects of
+ following the tutorial.
+ </para>
+ <example id="ex-misc-passive-voice">
+ <title>Incorrect: Passive voice</title>
+ <para>
+ The <command>yum update</command> command must be run.
+ </para>
+ <para>
+ You might want to run the <command>yum update</command>
+ command.
+ </para>
+ </example>
+ <example id="ex-misc-active-voice">
+ <title>Correct: Active voice</title>
+ <para>
+ Run the <command>yum update</command> command.
+ </para>
+ </example>
+ </section>
+
+ <section id="sn-present-tense">
+ <title>Present Tense</title>
+ <para>
+ Write in the present tense. A good rule of thumb is that the
+ words "will" and "shall" are almost never needed in describing
+ what the user should do or see. They add unnecessary length to
+ sentences and can confuse translators. They are also often
+ indicators of passive voice; refer also to <xref
+ linkend="sn-misc-active-voice"/>.
+ </para>
+ <example id="ex-misc-future-tense">
+ <title>Incorrect: Future tense</title>
+ <para>
+ The application will display a list of target files.
+ </para>
+ <para>
+ A list of target files will be displayed by the application.
+ </para>
+ </example>
+ <example id="ex-misc-present-tense">
+ <title>Correct: Present tense</title>
+ <para>
+ The application displays a list of target files.
+ </para>
+ </example>
+ </section>
+
+ <section id="sn-narrative-voice">
+ <title>Narrative Voice</title>
+ <para>
+ Do not use the first person "I," "we," or "us" to refer to
+ yourself the writer (whether including the reader or not), the
+ &FDP;, the &FED; community, or any other group. Do not refer to
+ users with a third person pronoun ("he," "she," or "he or she")
+ or the word "one." It is acceptable to refer to the reader with
+ the second person pronoun "you."
+ </para>
+ <example id="ex-misc-wrong-person">
+ <title>Incorrect: First or third person</title>
+ <para>
+ As described in the last section, I always run
+ <command>up2date</command> before configuring the Samba
+ server.
+ </para>
+ <para>
+ If the user needs to back up his or her files, s/he should use
+ the <command>tar</command> or <command>cpio</command> command.
+ </para>
+ </example>
+ <example id="ex-misc-correct-person">
+ <title>Correct: Second (or no) person</title>
+ <para>
+ Refer to the section on <command>up2date</command> before
+ configuring the Samba server.
+ </para>
+ <para>
+ If necessary, users can back up files with the
+ <command>tar</command> or <command>cpio</command> command.
+ </para>
+ </example>
+ </section>
+
+ <section id="sn-misc-negative">
+ <title>Negative Words</title>
+ <para>
+ Avoid negative words when possible, since they give
+ documentation an overly dogmatic tone. The word "avoid" is
+ useful for this purpose. Note that contractions are often used
+ for negative words such as <emphasis>don't</emphasis> or
+ <emphasis>can't</emphasis>. Refer to <xref
+ linkend="vle-contractions" />.
+ </para>
+ </section>
+
+ <section id="sn-misc-uncertainty">
+ <title>Uncertainty</title>
+ <para>
+ Avoid overuse of "typically," "usually," "most of," "many," and
+ the like. While occasional use of these constructions is
+ acceptable, overuse reduces the authority of your documentation.
+ The documentation should adequately cover a stock installation
+ of &FC;. It is impossible for a tutorial-length document to
+ cover every possible configuration scenario. Address the most
+ common scenarios and note discrepancies only as required.
+ </para>
+ </section>
+
+ <section id="sn-misc-offtopic">
+ <title>Redundant Coverage</title>
+ <para>
+ Avoid covering redundant material, such as how to update a &FC;
+ system. These overarching topics may be covered in other
+ tutorials. Writers frequently violate this guideline because
+ they feel their tutorial is not long enough. Keep your tutorial
+ from wandering off-topic. Instead, refer the reader to a
+ separate tutorial whenever possible for complete coverage of
+ that topic.
+ </para>
+ </section>
+
+ <section id="sn-misc-importance">
+ <title>Self-referential Value Judgments</title>
+ <para>
+ Avoid statements such as "One of the most important things to do
+ is <replaceable>XYZ</replaceable>." If the procedure is
+ important, the reader already expects it to be in your tutorial.
+ The converse is also true: If a procedure appears in your
+ tutorial, the reader expects it is important. This is
+ especially true if you use a whole section for the procedure in
+ question. Merely state, "Do <replaceable>XYZ</replaceable>."
+ Then elaborate as required. If the whole section concerns how
+ to do <replaceable>XYZ</replaceable>, leave this sentence out
+ entirely. Refer also to <xref linkend="vle-golden-rule-4" />.
+ </para>
+ </section>
+
+ <section id="sn-misc-precision">
+ <title>Precision of Language</title>
+ <para>
+ Use precise words for actions users should take. Do not
+ instruct users to "go" to a selection, or "find" a menu.
+ </para>
+ <example id="ex-precision-wrong">
+ <title>Incorrect: Imprecise wording</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Go to the <guimenu>Main Menu</guimenu> ->
+ <guimenuitem>Foobar</guimenuitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Find the option labeled <guilabel>Search</guilabel>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <example id="ex-precision-right">
+ <title>Correct: Precise wording</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ From the <guimenu>Main Menu</guimenu>, select
+ <guimenuitem>Foobar</guimenuitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select the <guilabel>Search</guilabel> option
+ </para>
+ </listitem>
+ </itemizedlist>
+ </example>
+ <important>
+ <title>Do Not Discriminate Against Non-GUI Users</title>
+ <para>
+ If you are writing about a GUI-only application, you may use
+ "click" freely. If you are writing about an application that
+ has a text-mode interface, use "select" instead as shown
+ above.
+ </para>
+ </important>
+
+ </section>
+
+ <section id="sn-misc-docbook-tips">
+ <title>DocBook Tips</title>
+ <para>
+ This section contains tips on how to use DocBook tags more
+ effectively in your documentation.
+ </para>
+
+ <section id="sn-misc-admonitions">
+ <title>Admonitions</title>
+ <para>
+ Avoid overuse of admonitions. Keep admonitions short and
+ effective by using only the most important material inside the
+ admonition. Move any background material required to explain
+ the admonition statements outside the admonition. Use a short
+ but descriptive title for an admonition. Use title case for
+ the admonition title.
+ </para>
+ <example id="ex-misc-ineffective-admonition">
+ <title>Incorrect: Lengthy admonition</title>
+ <para>
+ <warning>
+ <title>Use <command>sfdisk</command> to check input</title>
+ <para>
+ The <command>sfdisk</command> command accepts a script
+ file as standard input to set up partitions on a hard
+ disk. Sometimes <command>sfdisk</command> will simply
+ reject an erroneous input file. In other cases, it will
+ use the input verbatim, writing an incorrect partition
+ table to your disk. Always use the <command>sfdisk
+ -n</command> command to check your input file before
+ writing to the disk.
+ </para>
+ </warning>
+ </para>
+ </example>
+ <example id="ex-misc-good-admonition">
+ <title>Correct: Brief admonition</title>
+ <para>
+ The <command>sfdisk</command> command accepts a script
+ file as standard input to set up partitions on a hard disk.
+ Sometimes <command>sfdisk</command> will simply reject an
+ erroneous input file. In other cases, it will use the input
+ verbatim, writing an incorrect partition table to your disk.
+ <warning>
+ <title>Check Input</title>
+ <para>
+ Always use the <command>sfdisk -n</command> command to
+ check your input file before writing to the disk.
+ </para>
+ </warning>
+ </para>
+ </example>
+ <para>
+ Avoid punctuation in titles for sections or admonitions,
+ except for commas only where demanded. Use a title that says
+ something about the admonition comment, such as "Reboot
+ Required," instead of simply using the admonition type for a
+ title ("Note").
+ </para>
+ <para>
+ Follow the capitalization rules for headings in the title of
+ an admonition.
+ </para>
+ </section>
+
+ <section id="sn-misc-replaceable">
+ <title>The <sgmltag class="starttag">replaceable</sgmltag>
+ Tag</title>
+ <para>
+ If your documentation formally states a specific value will be
+ used as a convention, do not use the <sgmltag
+ class="starttag">replaceable</sgmltag> tag in your text or
+ examples.
+ </para>
+ </section>
+
+ <section id="sn-misc-entities">
+ <title>XML Entities</title>
+ <para>
+ Use the entities provided by the &FDP;. These entities are
+ found in the <filename>common/</filename> folder in the
+ <filename>fedora-docs</filename> distribution. (Refer also to
+ <xref linkend="ch-getting-files"/>.) For instance, do not use
+ abbreviations such as "FC2." Instead, use the predefined
+ entities "&FC; &FCVER;," which produces the text "&FC;
+ &FCVER;."
+ </para>
+ </section>
+
+ </section>
+
+ </section>
+
+</chapter>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d945 1
+a945 1
+ <xref linkend="s1-xml-tags-replaceable"/> for
+@
+
diff --git a/old-documentation-guide/en_US/tutorial.xml,v b/old-documentation-guide/en_US/tutorial.xml,v
new file mode 100644
index 0000000..44f84e5
--- /dev/null
+++ b/old-documentation-guide/en_US/tutorial.xml,v
@@ -0,0 +1,277 @@
+head 1.3;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.3
+ LIVE:1.3;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.06.23.05.24.16; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.02.03.22.29.37; author kwade; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at This is finally being updated; I hope to finish this in the next week.
+@
+text
+@<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: tutorial.xml,v 1.2 2007/02/03 22:29:37 kwade Exp $ -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<chapter id="ch-tutorial">
+ <title>The Layout of a Tutorial</title>
+ <para>In this chapter, you will find an example of a very short tutorial
+ as used by the &FDP;. This example is specific to the way the Docs
+ Project uses DocBook XML. The example consists of a set of files
+ used to hold the content and metadata for the tutorial.</para>
+ <section id="sn-tutorial-article">
+ <title>The Article</title>
+ <indexterm>
+ <primary>tutorial layout</primary>
+ <secondary>article</secondary>
+ </indexterm>
+ <para>Below is a sample article:</para>
+ <screen><![CDATA[<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+]>
+
+<article id="sample-tutorial" lang="en_US">
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="fdp-info.xml"/>
+ <section id="some-section">
+ <title>Some Section</title>
+ <para>
+ This is an example section. You can nest sections or make
+ additional sections as needed.
+ </para>
+ <warning>
+ <title>Warning</title>
+ <para>
+ Example of an admonition.
+ </para>
+ </warning>
+ </section>
+<index id="generated-index"/>
+</article>
+]]></screen>
+ </section>
+ <section id="sn-tutorial-metadata">
+ <title>The Metadata</title>
+ <indexterm>
+ <primary>tutorial layout</primary>
+ <secondary>metadata</secondary>
+ </indexterm>
+ <para>The <filename>rpm-info.xml</filename> file contains all the
+ required metadata for the document. This metadata includes title,
+ authorship, licensing, and revision history. <xref
+ linkend="ex-rpminfo"/> illustrates the content of this
+ file:</para>
+ <example id="ex-rpminfo">
+ <title>Example <filename>rpm-info.xml</filename> File</title>
+ <programlisting><![CDATA[<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE rpm-info PUBLIC "-//Fedora//DTD Docs RPM-INFO V1.0//EN"
+ "http://docs.fedoraproject.org/dtds/rpm-info.dtd">
+
+<rpm-info>
+ <colophon>
+ <worker surname="Smith" firstname="John" othername="Q."
+ id="JohnSmith" email="jsmith@@example.com"
+ wholename="John Q. Smith" initials="JS"/>
+ </colophon>
+ <author worker="JohnSmith"/>
+ <license>
+ <rights>OPL</rights>
+ <version>1.0</version>
+ </license>
+ <copyright>
+ <year>2006</year>
+ <holder>John Q. Smith</holder>
+ </copyright>
+ <title>My Tutorial</title>
+ <desc>A tutorial about something important</desc>
+ <changelog order="newest-first">
+ <revision date="2006-06-01" number="0.1" role="doc">
+ <author worker="JohnSmith"/>
+ <details>First draft</details>
+ </revision>
+ </changelog>
+</rpm-info>]]></programlisting>
+ </example>
+ <para>If you are not familiar with XML editing, copy and paste this
+ file from an existing module and then edit the values for the
+ various elements as appropriate. Consult &FDP; members and help
+ channels for more assistance if needed.</para>
+ </section>
+</chapter>
+@
+
+
+1.2
+log
+ at updating all section usage and associated ID tags
+@
+text
+ at d1 2
+a2 1
+<!-- $Id: tutorial.xml,v 1.1 2007/02/03 22:21:58 kwade Exp $ -->
+d12 15
+a26 22
+ <chapter id="ch-tutorial">
+ <title>The Layout of a Tutorial</title>
+
+ <para>
+ In this chapter, you will find an example of a &PROJECT; documentation
+ parent file. This example is specific to the way the Docs Project uses
+ DocBook XML. The parent file contains the main structural format of the
+ book, a link to the entities file that contain common entities that should
+ be used, and an entity to change the version and date of the tutorial.
+ </para>
+
+ <section id="sn-tutorial-parent">
+ <title>The Parent File</title>
+
+ <para>
+ Below is a sample parent file:
+ </para>
+
+<screen>
+<computeroutput>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+d28 2
+a29 2
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../common/fedora-entities-en.xml">
+%FEDORA-ENTITIES-EN;
+d31 1
+a31 1
+<!ENTITY VERSION "0.1"> <!-- change version of tutorial here -->
+d33 12
+a44 34
+<!ENTITY DOCID "example-tutorial-&VERSION; (2003-07-07)"> <!-- change last modified date here -->
+
+<!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice-en.xml">
+
+
+]>
+
+<article id="example-tutorial" lang="en">
+ <articleinfo>
+ <title>Example Tutorial</title>
+ <copyright>
+ <year>2003</year>
+ <holder>&FORMAL-RHI;</holder>
+ <holder>Tammy Fox</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Fox</surname>
+ <firstname>Tammy</firstname>
+ </author>
+ </authorgroup>
+ &LEGALNOTICE;
+ </articleinfo>
+
+ <section id="some-section">
+ <title>Some Section</title>
+
+ <para>
+ This is an example section. You can also use section, section, etc.
+ </para>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+a45 28
+ </para>
+ </warning>
+
+ </section>
+
+<index id="generated-index"></index>
+</article>
+</computeroutput>
+</screen>
+
+ </section>
+
+ <section id="sn-tutorial-license">
+ <title>Including the License Information</title>
+
+ <indexterm>
+ <primary>tutorial layout</primary>
+ <secondary>license</secondary>
+ </indexterm>
+
+ <para>
+ All &PROJECT; manuals <emphasis>must</emphasis> contain the file
+ <filename>legalnotice.xml</filename>. This file makes the license for
+ the file the GNU Free Documentation License (FDL).
+ </para>
+
+ <para>
+ The sample parent file shows how it is included.
+d47 54
+a100 6
+
+ </section>
+
+ </chapter>
+
+
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-tutorial.xml,v 1.2 2006/12/17 00:41:55 pfrields Exp $ -->
+d22 1
+a22 1
+ <sect1 id="s1-tutorial-parent">
+d67 1
+a67 1
+ This is an example section. You can also use sect1, sect2, etc.
+d84 1
+a84 1
+ </sect1>
+d86 1
+a86 1
+ <sect1 id="s1-tutorial-license">
+d104 1
+a104 1
+ </sect1>
+@
+
diff --git a/old-documentation-guide/en_US/vim.xml,v b/old-documentation-guide/en_US/vim.xml,v
new file mode 100644
index 0000000..40ce404
--- /dev/null
+++ b/old-documentation-guide/en_US/vim.xml,v
@@ -0,0 +1,222 @@
+head 1.2;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.2
+ LIVE:1.2;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2007.02.03.22.29.37; author kwade; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at updating all section usage and associated ID tags
+@
+text
+@<!-- $Id: vim.xml,v 1.1 2007/02/03 22:21:58 kwade Exp $ -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+
+ <chapter id="ch-vim">
+ <title>VIM and DocBook</title>
+
+ <indexterm>
+ <primary>VIM</primary>
+ </indexterm>
+
+ <para>
+ VIM has many features to help you write XML content such as DocBook,
+ including syntax highlighting and customizable key bindings.
+ Additionally, one can easily use external programs from VIM for features
+ such as spell-checking.
+ This chapter assumes you already know generally how to use VIM; if you
+ want to learn how, try the <command>vimtutor</command> or by typing
+ <userinput>:help tutor</userinput> from inside VIM.
+ </para>
+
+ <section id="sn-vimrc-file">
+ <title>Setting Up Your <filename>.vimrc</filename> File</title>
+
+ <indexterm>
+ <primary>VIM</primary>
+ <secondary>configuration file</secondary>
+ </indexterm>
+
+ <para>
+ Below is a short sample <filename>.vimrc</filename> file that turns on
+ some VIM features useful for editing SGML or XML content such as
+ DocBook:
+<screen>
+<computeroutput>" Turn off vi compatibility settings like limited undo
+set nocompatible
+" Syntax highlighting based on file extension
+syntax on
+" Automatically insert newlines after 80 characters
+set textwidth=80
+" Automatically indent
+set autoindent
+" Match SGML tags with %
+source $VIMRUNTIME/macros/matchit.vim</computeroutput>
+</screen>
+ </para>
+ <note>
+ <para>
+ Some of these features require the <filename>vim-enhanced</filename>
+ package to be installed. If you are using or the
+ <filename>vim-minimal</filename> package, or if you are using an older
+ version of VIM, you may not have the
+ <filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still
+ download <ulink
+ url="http://vim.org/scripts/script.php?script_id=39">matchit.zip from
+ Vim.org</ulink> and load it separately.
+ </para>
+ </note>
+ </section>
+
+ <section id="sn-vim-keymapping">
+ <title>Keymapping with VIM</title>
+
+ <para>
+ VIM can speed up your DocBook creation by mapping frequently typed tags
+ (or any words or phrases) onto short key combinations. By default, the
+ keymap leader is the backslash (<literal>\</literal>), but it can be
+ redefined with a command like <userinput>let mapleader =
+ ","</userinput>. There are two ways to use the following example;
+ you can put it directly in your <filename>.vimrc</filename>, or you
+ can save it in a separate file and load it with a
+ <userinput>source</userinput> command in your
+ <filename>.vimrc</filename>.
+<screen>
+<![CDATA[let mapleader = ","
+
+" skip ahead to after next tag without leaving insert mode
+imap <leader>e <esc>/><cr>:nohlsearch<cr>a
+
+" common tags that start a new text block
+imap<leader>pa <para><cr></para><esc>O
+imap<leader>sn <section id=""><cr><para><esc>jo</section><esc>O
+imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i
+imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i
+
+" common tags that are placed inline
+" use <esc>F>a
+imap<leader>en <envar></envar><esc>F>a
+imap<leader>fi <filename></filename><esc>F>a
+imap<leader>lt <literal></literal><esc>F>a
+imap<leader>re <replaceable></replaceable><esc>F>a
+imap<leader>ui <userinput></userinput><esc>F>a
+imap<leader>ul <ulink url=""></ulink><esc>F>a
+imap<leader>si <systemitem></systemitem><esc>F>a
+imap<leader>us <systemitem class="username"></systemitem><esc>F>a
+imap<leader>sy <systemitem class="systemname"></systemitem><esc>F>a
+imap<leader>cm <command></command><esc>F>a
+" entities
+imap <leader>> >
+imap <leader>< <]]>
+</screen>
+ </para>
+ <para>
+ Unfortunately, there is not currently a complete macro set for all
+ DocBook commands, so you will need to define them yourself or customize
+ the definitions in the examples from <xref
+ linkend="sn-vim-additional-resources"></xref>.
+ </para>
+ </section>
+
+ <section id="sn-vim-additional-resources">
+ <title>Additional VIM Resources</title>
+
+ <para>
+ Additional information about VIM may be found from:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink url=
+ "http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC">
+ Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to
+ Vi Improved (VIM)</citetitle>
+ </para>
+ </listitem>
+ <listitem>
+ <para>The <ulink url="http://tnerual.eriogerg.free.fr/vim.html">VIM
+ Quick Reference Card</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://www.pinkjuice.com/howto/vimxml/">Vim as XML
+ Editor</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with
+ the <filename>vim-common</filename> package —
+ <filename>/usr/share/vim/<replaceable><version></replaceable>/doc/intro.txt</filename>
+ or type <userinput>:help intro</userinput> from within VIM
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+ </chapter>
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-vim.xml,v 1.2 2006/12/17 00:41:55 pfrields Exp $ -->
+d29 1
+a29 1
+ <sect1 id="s1-vimrc-file">
+d66 1
+a66 1
+ </sect1>
+d68 1
+a68 1
+ <sect1 id="s1-vim-keymapping">
+d89 1
+a89 1
+imap<leader>s1 <sect1 id=""><cr><para><esc>jo</sect1><esc>O
+d114 1
+a114 1
+ linkend="s1-vim-additional-resources"></xref>.
+d116 1
+a116 1
+ </sect1>
+d118 1
+a118 1
+ <sect1 id="s1-vim-additional-resources">
+d155 1
+a155 1
+ </sect1>
+@
+
diff --git a/old-documentation-guide/en_US/writing-guidelines.xml,v b/old-documentation-guide/en_US/writing-guidelines.xml,v
new file mode 100644
index 0000000..357a49c
--- /dev/null
+++ b/old-documentation-guide/en_US/writing-guidelines.xml,v
@@ -0,0 +1,1397 @@
+head 1.11;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.11
+ LIVE:1.7;
+locks; strict;
+comment @# @;
+
+
+1.11
+date 2007.09.16.19.12.38; author pfrields; state Exp;
+branches;
+next 1.10;
+
+1.10
+date 2007.09.16.19.11.27; author pfrields; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2007.07.01.17.30.32; author pfrields; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2007.06.29.00.10.59; author pfrields; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2007.03.08.03.00.44; author pfrields; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.02.18.22.59.19; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.02.18.14.24.33; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.02.05.00.33.47; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.02.04.13.57.23; author kwade; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.02.03.22.29.37; author kwade; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.11
+log
+ at Include one more bit of helpful information for n00bs.
+@
+text
+@<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+<chapter id="ch-writing-guidelines">
+ <title>&FED; Documentation Guidelines</title>
+
+ <indexterm>
+ <primary>recursion</primary>
+ <see>recursion</see>
+ </indexterm>
+
+ <indexterm>
+ <primary>RTFM</primary>
+ <secondary>read the fine manual</secondary>
+ <seealso>humor</seealso>
+ </indexterm>
+
+ <indexterm>
+ <primary>humor</primary>
+ <secondary>RTFM</secondary>
+ </indexterm>
+
+ <para>Please read this chapter carefully. This chapter describes the
+ guidelines that must be followed such as naming conventions.</para>
+
+ <para>This chapter only discusses tags used for documentation for the &PROJECT;,
+ not all available DocBook XML tags. For the complete list, refer to
+ <ulink url="http://www.docbook.org/tdg/en/html/docbook.html"/>.
+ </para>
+
+ <section id="sn-xml-guidelines-header">
+ <title>File Header</title>
+ <section id="sn-xml-header-xml">
+ <title>XML Header</title>
+ <para>In accordance with good XML practices, the first line in any
+ DocBook XML source files should identify the file as XML. Use
+ the following line as the first line of any new XML file:</para>
+ <screen><![CDATA[<?xml version="1.0" encoding="UTF-8"?>]]></screen>
+ </section>
+ <section id="sn-xml-header-cvs">
+ <title>CVS Id Header</title>
+ <para>All the files must contain the CVS Id header. Use the
+ following line as the second line of any new XML file:</para>
+ <screen><![CDATA[<!-- $Id: -->]]></screen>
+ <para>Any time the file is committed to CVS, the line is updated
+ automatically to include information about the file. For
+ example:</para>
+ <screen><![CDATA[<!-- $Id: writing-guidelines.xml,v 1.10 2007/09/16 19:11:27 pfrields Exp $ -->]]></screen>
+ </section>
+ </section>
+ <section id="sn-id-naming-conventions">
+ <title>ID Naming Conventions</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>naming conventions</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>naming conventions</primary>
+ </indexterm>
+
+ <para>This section explains the ID naming convention. IDs are
+ unique identifiers that allow DocBook XML to cross-reference a
+ section, chapter, or other element.</para>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>naming conventions</primary>
+ <secondary>rules for defining an ID</secondary>
+ </indexterm>
+
+ <para>The following general rules apply to IDs:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Keep an ID as short and simple as possible.</para>
+ </listitem>
+ <listitem>
+ <para>Start the ID with the special short two-character label.
+ This makes URLs and other references to this ID human
+ readable, by self-identifying the XML container type.</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ <xref linkend="ex-id-usage"/> demonstrates some example ID
+ attributes used properly.
+ </para>
+
+ <example id="ex-id-usage">
+ <title>Proper ID Usage</title>
+ <screen><![CDATA[<chapter id="ch-unique-name-of-chapter">
+
+<section id="sn-install-make-disks">
+
+<figure id="fig-redhat-config-kickstart-basic">]]></screen>
+ </example>
+
+ <segmentedlist id="sg-id-two-char-naming-conventions">
+ <title>Two-Character Naming Conventions</title>
+ <segtitle>Tag</segtitle>
+ <segtitle>Prefix</segtitle>
+ <seglistitem>
+ <seg><sgmltag class="element">preface</sgmltag></seg>
+ <seg><literal>pr-</literal></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><sgmltag class="element">chapter</sgmltag></seg>
+ <seg><literal>ch-</literal></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><sgmltag class="element">section</sgmltag></seg>
+ <seg><literal>sn-</literal></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><sgmltag class="element">figure</sgmltag></seg>
+ <seg><literal>fig-</literal></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><sgmltag class="element">table</sgmltag></seg>
+ <seg><literal>tb-</literal></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><sgmltag class="element">appendix</sgmltag></seg>
+ <seg><literal>ap-</literal></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><sgmltag class="element">part</sgmltag></seg>
+ <seg><literal>pt-</literal></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><sgmltag class="element">example</sgmltag></seg>
+ <seg><literal>ex-</literal></seg>
+ </seglistitem>
+ </segmentedlist>
+
+ <para>Use the title of the item as the ID. Make your titles unique
+ within a document to prevent conflicts. For example:</para>
+
+ <screen><![CDATA[<chapter id="ch-how-to-fold-laundry">
+ <title>How To Fold Laundry</title>
+ <section id="sn-folding-shirts">
+ <title>Folding Shirts</title>]]></screen>
+ </section>
+ <section id="sn-xml-tags">
+ <title>XML Tags</title>
+ <indexterm>
+ <primary>xml tags</primary>
+ <secondary>caveats</secondary>
+ </indexterm>
+
+ <para>
+ It is very important that you remember the caveats in this
+ section. These are learned suggestions or rules that make your
+ XML experience better.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>Do Not Use Trademark Entities</term>
+ <listitem>
+ <para>Do not use the trademark entities <sgmltag
+ class="genentity">trade</sgmltag>, <sgmltag
+ class="genentity">copy</sgmltag>, or <sgmltag
+ class="genentity">reg</sgmltag> because the do not produce
+ HTML output that works for all charsets. The HTML output
+ produces by these entities are declared in the DTD and
+ cannot be changed via the stylesheet.</para>
+
+ <para>Instead, use the <sgmltag>trademark</sgmltag> tag and its
+ associates classes as follows:</para>
+ <segmentedlist>
+ <segtitle>DocBook XML source</segtitle>
+ <segtitle>Rendered content</segtitle>
+ <seglistitem>
+ <seg><code><![CDATA[<trademark>trademark symbol after
+ me</trademark>]]></code></seg>
+ <seg><trademark>trademark symbol after
+ me</trademark></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><code><![CDATA[<trademark
+ class="registered">registered trademark symbol after
+ me</trademark>]]></code></seg>
+ <seg><trademark class="registered">registered trademark
+ symbol after me</trademark></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><code><![CDATA[<trademark class="copyright">copyright
+ symbol after me</trademark>]]></code></seg>
+ <seg><trademark class="copyright">copyright symbol after
+ me</trademark></seg>
+ </seglistitem>
+ </segmentedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <sgmltag>para</sgmltag> tags</term>
+ <listitem>
+ <para>In general, use <sgmltag>para</sgmltag> tags
+ around anything other than a simple paragraph. Doing so will
+ create additional white space within the text itself in the
+ PDF version.
+ </para>
+ <para>Specifically, do not use <sgmltag>para</sgmltag> tags
+ around the following (or, to put this another way, do not
+ embed the following within <sgmltag
+ class="element">para</sgmltag> elements):
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><sgmltag class="element">screen</sgmltag></para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="element">itemizedlist</sgmltag></para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="element">orderedlist</sgmltag></para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="element">variablelist</sgmltag></para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="element">table</sgmltag></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <sgmltag class="element">para</sgmltag> elements within
+ <sgmltag>listitem</sgmltag> tags</term>
+ <listitem>
+ <para>Content inside <sgmltag class="element">para</sgmltag>
+ elements within <sgmltag class="element">listitem</sgmltag>
+ elements <emphasis>must</emphasis> start immediately after
+ the beginning <sgmltag class="starttag">para</sgmltag> tag
+ to avoid extra white space in the PDF version.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <sgmltag>screen</sgmltag> tags</term>
+ <listitem>
+ <para>The content inside <sgmltag>screen</sgmltag> tags
+ (<sgmltag class="starttag">screen</sgmltag> and <sgmltag
+ class="endtag">screen</sgmltag>)
+ <emphasis>must</emphasis> be flush left in the XML file;
+ otherwise, the extraneous whitespace will appear in the HTML
+ version.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="sn-xml-admon">
+ <title>Admonitions</title>
+
+ <indexterm>
+ <primary>admonitions</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>warning</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>tip</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>caution</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>important</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>warning</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>tip</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>note</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>caution</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>admonitions</secondary>
+ <tertiary>important</tertiary>
+ </indexterm>
+
+ <para>There are five types of admonitions in DocBook: <sgmltag
+ class="element">caution</sgmltag>, <sgmltag
+ class="element">important</sgmltag>, <sgmltag
+ class="element">note</sgmltag>, <sgmltag
+ class="element">tip</sgmltag>, and <sgmltag
+ class="element">warning</sgmltag>. All of the admonitions have
+ the same structure: an optional <sgmltag
+ class="element">title</sgmltag> followed by paragraph-level
+ elements. The DocBook DTD does not impose any specific semantics
+ on the individual admonitions. For example, DocBook does not
+ mandate that a <sgmltag class="element">warning</sgmltag> is
+ reserved for cases where bodily harm can result.</para>
+
+ <section id="sn-xml-notesetc">
+ <title>Creating a <sgmltag class="element">note</sgmltag>,
+ <sgmltag class="element">tip</sgmltag>, <sgmltag
+ class="element">caution</sgmltag>, <sgmltag
+ class="element">important</sgmltag>, or <sgmltag
+ class="element">warning</sgmltag></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>note</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>tip</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>caution</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>important</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>warning</secondary>
+ </indexterm>
+
+ <para>There are several ways to bring attention to text within a
+ document. A <emphasis><sgmltag
+ class="element">note</sgmltag></emphasis> is used to bring
+ additional information to the users' attention. A
+ <emphasis><sgmltag class="element">tip</sgmltag></emphasis> is
+ used to show the user helpful information or another way to do
+ something. A <emphasis><sgmltag
+ class="element">caution</sgmltag></emphasis> is used to show
+ the user they must be careful when attempting a certain step. An
+ <emphasis><sgmltag
+ class="element">important</sgmltag></emphasis> tag set can
+ be used to show the user a piece of information that should not
+ be overlooked. While this information may not change anything
+ the user is doing, it should show the user that this piece of
+ information could be vital. A <emphasis><sgmltag
+ class="element">warning</sgmltag></emphasis> is used to show
+ the reader that their current setup will change or be altered,
+ such as files being removed, and they should not choose this
+ operation unless they are alright with the consequences.</para>
+
+ <para>The following lines of code show the basic setup for each
+ case mentioned above, along with its appearance in HTML.</para>
+
+ <screen><![CDATA[<note>
+ <title>Note</title>
+ <para>Body of text goes here.</para>
+</note>]]></screen>
+
+ <note>
+ <title>Note</title>
+ <para>Body of text goes here.</para>
+ </note>
+
+ <screen><![CDATA[<tip>
+ <title>Tip</title>
+ <para>Body of text goes here.</para>
+</tip>]]></screen>
+
+ <tip>
+ <title>Tip</title>
+ <para>Body of text goes here</para>
+ </tip>
+
+ <screen><![CDATA[<caution>
+ <title>Caution</title>
+ <para>Body of text goes here.</para>
+</caution>]]></screen>
+
+ <caution>
+ <title>Caution</title>
+ <para>Body of text goes here.</para>
+ </caution>
+
+ <screen><![CDATA[<important>
+ <title>Important</title>
+ <para>Body of text goes here.</para>
+</important>]]></screen>
+
+ <important>
+ <title>Important</title>
+ <para>Body of text goes here.</para>
+ </important>
+
+ <screen><![CDATA[<warning>
+ <title>Warning</title>
+ <para>Body of text goes here.</para>
+</warning>]]></screen>
+
+ <warning>
+ <title>Warning</title>
+ <para>Body of text goes here.</para>
+ </warning>
+ </section>
+
+ </section>
+
+ <section id="sn-screenshots">
+ <title>Screenshots</title>
+
+ <indexterm>
+ <primary>screenshots</primary>
+ <secondary>how to take</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>screen captures</primary>
+ <see>screenshots</see>
+ </indexterm>
+ <indexterm>
+ <primary>screen grabs</primary>
+ <see>screenshots</see>
+ </indexterm>
+
+ <para>Screenshots are illustrations that show the state of a display
+ the user may encounter. Screenshots can be either graphical or
+ textual. However, screenshots use a great deal of space in a text
+ document to convey relatively small amounts of information. The
+ same space in the document can hold a greater amount of more
+ descriptive and helpful information. Therefore, authors should
+ avoid screenshots whenever possible in favor of descriptive
+ text.</para>
+ <para>One of the isolated instances in which screenshots are useful
+ is to demonstrate a physical screen layout that is unfamiliar to a
+ reader. <emphasis>This does not mean that illustrations of dialog
+ boxes are good uses of screenshots.</emphasis> On the contrary,
+ dialogs are simply instances of a user interface element with
+ which a reader is already familiar. An annotated diagram in
+ certain cases, however, explains to the reader where to find
+ functional landmarks on the screen such as menu bars.</para>
+ <para>The steps for taking a graphical screenshot illustrate how
+ using text to describe a procedure is more concise than a series
+ of screenshots.</para>
+ <variablelist>
+ <varlistentry>
+ <term>Graphical Screenshot</term>
+ <listitem>
+ <procedure>
+ <step>
+ <para>Create a new user account to make screenshots. The
+ new account uses the distribution default theme, fonts,
+ and element sizes. The resulting screenshot has an
+ appearance familiar to the largest number of readers,
+ and makes &FDP; documents consistent.</para>
+ </step>
+ <step>
+ <para>Before taking the screenshot, if possible, resize
+ the targeted GUI element(s) to the smallest possible
+ size. The target image should be 500 pixels wide or
+ less. If the screenshot includes more than one GUI
+ element, you may need to resize the screenshot in a
+ following step.</para>
+ </step>
+ <step>
+ <para>To take the screenshot, select the GUI element with
+ the mouse to bring it to the forefront, or otherwise
+ arrange the elements. Press <keycombo>
+ <keycap>Alt</keycap>
+ <keycap>Print Screen</keycap></keycombo> to capture a
+ single GUI window. For capturing the entire desktop use
+ <keycap>Print Screen</keycap>. If the shot includes
+ multiple elements grouped closely together, crop the
+ resulting PNG format image in <application>The
+ GIMP</application>.</para>
+ </step>
+ <step>
+ <para>If necessary, resize the image using
+ <application>The GIMP</application>. Open the image,
+ then right-click on it and choose
+ <menuchoice>
+ <guimenu>Image</guimenu>
+ <guimenuitem>Scale Image...</guimenuitem>
+ </menuchoice>. With the chain symbol intact, set the
+ <guilabel>New Width</guilabel> to <guilabel>500
+ px</guilabel>, and click <guibutton>OK</guibutton>.
+ Choose <menuchoice>
+ <guimenu>File</guimenu>
+ <guimenuitem>Save</guimenuitem>
+ </menuchoice> to save changes to the image before
+ converting it.</para>
+ </step>
+ <step>
+ <para>
+ With the image open in <application>The
+ GIMP</application>, right-click the image, and select
+ <menuchoice>
+ <guimenu>File</guimenu>
+ <guimenuitem>Save As...</guimenuitem>
+ </menuchoice>. Under <guimenu>Determine File
+ Type:</guimenu>, select
+ <guimenuitem>PostScript</guimenuitem>, then click
+ <guibutton>OK</guibutton>. Allow flattening of the image
+ by clicking <guibutton>Export</guibutton>.</para>
+ <para>A <guilabel>Save as PostScript</guilabel> window
+ appears. Select <guilabel>Encapsulated
+ PostScript</guilabel>, and click
+ <guibutton>OK</guibutton>.</para>
+ </step>
+ </procedure>
+ <!-- This section is dropped, right? [PWF] -->
+<!--
+ <para>For more information about calling the images from the
+ XML, refer to <xref linkend="sn-xml-tags-figure"/>.</para>
+-->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Text Screenshot</term>
+ <listitem>
+ <para>Textual screen information is also useful for readers.
+ Follow these guidelines for textual screenshots:</para>
+ <itemizedlist>
+ <listitem>
+ <para>If a graphical screenshot illustrates a function,
+ and the textual mode has identical functions, do not
+ include both, unless omitting either would make your
+ description unclear.</para>
+ </listitem>
+ <listitem>
+ <para>Make the information generic over specific, and omit
+ any username and machine information if possible. Do not
+ include the shell prompt unless it is vital to the
+ demonstration.</para>
+ </listitem>
+ <listitem>
+ <para>Separate what the user types from sample command
+ output.</para>
+ </listitem>
+ <listitem>
+ <para>When using <sgmltag class="element">screen</sgmltag>
+ to demonstrate a procedure, use <sgmltag
+ class="element">userinput</sgmltag> tags to show what
+ the user types, and use <sgmltag
+ class="element">computeroutput</sgmltag> tags to show
+ the resulting output.</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ <xref linkend="ex-text-screenshot-good"/> is an example of
+ textual screenshot usage.
+ </para>
+ <example id="ex-text-screenshot-good">
+ <title>Correct Textual Screenshot (XML Source and
+ HTML)</title>
+ <screen><![CDATA[<example id="ex-text-screenshot-good">
+ <title>Correct Textual Screenshot</title>
+ <para>To find all the currently active ssh sessions,
+ execute the following command:</para>
+ <screen><userinput>ps ax | grep ssh</userinput></screen>
+ <para>Output appears similar to the following:</para>
+ <screen><computeroutput> 2564 ? S 0:23 /usr/sbin/sshd
+ 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
+ 8032 pts/0 S 0:00 ssh user@@host.example.com
+ 8032 pts/1 S 0:00 ssh root@@backup.example.com</computeroutput></screen>
+</example>]]></screen>
+ <para>To find all the currently active ssh sessions, execute the
+ following command:</para>
+ <screen><userinput>ps ax | grep ssh</userinput></screen>
+
+ <para>Output appears similar to the following:</para>
+
+ <screen><computeroutput> 2564 ? S 0:23 /usr/sbin/sshd
+ 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients
+ 8032 pts/0 S 0:00 ssh user@@host.example.com
+ 8032 pts/1 S 0:00 ssh root@@backup.example.com</computeroutput></screen>
+ </example>
+ <!-- This section is dropped, right? [PWF] -->
+<!--
+ <para>For more information about using screen, refer to <xref
+ linkend="sn-xml-tags-screen"/>.</para>
+-->
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+<!--
+ <section id="sn-diagrams-images">
+ <title>Diagrams and Images</title>
+
+ <indexterm>
+ <primary>images</primary>
+ </indexterm>
+ <indexterm>
+ <primary>diagrams</primary>
+ <secondary>creating</secondary>
+ </indexterm>
+
+ <para>
+ To be written
+ </para>
+
+ </section>
+-->
+
+ <section id="sn-live-previews">
+ <title>Previewing Your Work</title>
+ <para>The GNOME <application>Help</application> browser, also known
+ as <command>yelp</command>, and the KDE
+ <application>Khelp</application> documentation browser can render
+ DocBook XML information as needed. Use these applications to
+ preview your work if you prefer reading your work in a
+ browser-like environment. Run the following command:</para>
+ <screen><![CDATA[yelp file:///path/to/parent-file.xml]]></screen>
+ <para>Make sure to point the preferred help browser at the top
+ parent file of your XML document. Once the document loads, you
+ can add a bookmark for it for ease of use later.</para>
+ <tip>
+ <title>Using Bookmarks</title>
+ <para>Keeping your documents in the same place for every checkout
+ session makes help browser bookmarks more effective.</para>
+ </tip>
+ <para>Once you have a bookmark stored, it will appear in the help
+ browser at every use. You can now hit <keycap>F1</keycap> during
+ any GUI session to launch the help browser. Then choose your
+ bookmark from the menu to preview your document at any
+ time.</para>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.10
+log
+ at Give advice on previewing work.
+@
+text
+ at d54 1
+a54 1
+ <screen><![CDATA[<!-- $Id: writing-guidelines.xml,v 1.9 2007/07/01 17:30:32 pfrields Exp $ -->]]></screen>
+d664 5
+@
+
+
+1.9
+log
+ at Clean up and improve screenshot guidelines
+@
+text
+ at d54 1
+a54 1
+ <screen><![CDATA[<!-- $Id: writing-guidelines.xml,v 1.8 2007/06/29 00:10:59 pfrields Exp $ -->]]></screen>
+d647 18
+@
+
+
+1.8
+log
+ at Some content updates, push new bugfix rev 0.3.0.1, no publishing needed yet
+@
+text
+ at d54 1
+a54 1
+ <screen><![CDATA[<!-- $Id: writing-guidelines.xml,v 1.7 2007/03/08 03:00:44 pfrields Exp $ -->]]></screen>
+d466 16
+a481 13
+ <para>There are two types of screenshots: graphical and textual.
+ The philosophy on using these two types is <firstterm>rely on text
+ over graphics</firstterm>. This means, if you can say it in
+ text instead of showing a graphic, do so. A graphical screenshot
+ of a GUI can create a good setting of objects to then describe
+ textually, but you don't want to create a screenshot for each
+ graphical step.</para>
+ <para>The main reason for this preference is that a block of text
+ can usually convey more meaning than the same physical space of
+ graphics. This is highly dependent on the graphic; obviously, a
+ photographic image of a scene can convey more than 1000 words can.
+ A GUI screenshot is usually full of blank space with a few
+ elements that can just as easily be described or listed.</para>
+d491 5
+a495 7
+ <para>Set the theme to Bluecurve defaults. This gives a look
+ that is familiar to most readers, and makes &FDP;
+ documents consistent. From the panel menu, choose
+ <guimenu>Preferences</guimenu>,
+ <guimenuitem>Theme</guimenuitem> and select
+ <guimenuitem>Bluecurve</guimenuitem> from the theme
+ list.</para>
+d498 5
+a502 15
+ <para>Set fonts to Bluecurve defaults as well. From the
+ panel menu, choose <guimenu>Preferences</guimenu>,
+ <guimenuitem>Fonts</guimenuitem>. Set the
+ <guilabel>Application font</guilabel> and the
+ <guilabel>Desktop font</guilabel> to Sans Regular 10.
+ Set the <guilabel>Window Title font</guilabel> to Sans
+ Bold 10. Set the <guilabel>Terminal font</guilabel> to
+ Monospace Regular 10.</para>
+ </step>
+ <step>
+ <para>Before taking the screenshot, try to resize the
+ targeted GUI element(s) to the smallest possible size
+ they can be. Your target is an image of 500 pixels or
+ less. If you are doing a screenshot of more than one
+ GUI element, you may need to resize the screenshot in a
+d507 2
+a508 2
+ your mouse, bringing it to the forefront, or otherwise
+ arranging the elements. Press <keycombo>
+d510 1
+a510 1
+ <keycap>Print Screen</keycap> </keycombo> to capture a
+d512 4
+a515 5
+ <keycap>Print Screen</keycap>. If you are taking a shot
+ of multiple elements and have grouped them closely
+ together, you can crop the resulting image in
+ <application>The GIMP</application>. The image will be
+ in the PNG format.</para>
+d518 8
+a525 6
+ <para>If you need to, you can resize using
+ <application>The GIMP</application>. With the image
+ open, right-click on it and choose
+ <guimenu>Image</guimenu> -> <guimenuitem>Scale
+ Image...</guimenuitem>. With the chain symbol intact,
+ set the <guilabel>New Width</guilabel> to <guilabel>500
+d527 5
+a531 4
+ Be sure to <keycombo>
+ <keycap>Ctrl</keycap> <keycap>s</keycap> </keycombo>
+ to save your changes to your PNG before converting to
+ EPS.</para>
+d536 6
+a541 4
+ GIMP</application>, right-click on the image,
+ selecting <guimenu>File</guimenu> ->
+ <guimenuitem>Save As...</guimenuitem>. Under
+ <guimenu>Determine File Type:</guimenu>, select
+d545 2
+a546 2
+ <para>In the <guilabel>Save as PostScript</guilabel>
+ window, select <guilabel>Encapsulated
+d565 4
+a568 4
+ <para>If you use a graphical screenshot to illustrate a
+ function, and the textual mode has identical functions,
+ do not include both, unless omitting either would make
+ your description unclear.</para>
+d571 4
+a574 4
+ <para>Make your information generic over specific, and
+ omit any username and machine information if possible.
+ Do not include the shell prompt unless it is vital to
+ the demonstration.</para>
+@
+
+
+1.7
+log
+ at Use segmentedlist instead of tables -- separating appearance from content, yay DocBook!
+@
+text
+ at d37 20
+d155 3
+a157 1
+
+d182 25
+a206 22
+ associates classes as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><sgmltag
+ class="starttag">trademark</sgmltag>trademark symbol after
+ me<sgmltag class="endtag">trademark</sgmltag>
+ </para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="starttag">trademark
+ class="registered"</sgmltag>registered trademark symbol
+ after me<sgmltag class="endtag">trademark</sgmltag>
+ </para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="starttag">trademark
+ class="copyright"</sgmltag>copyright symbol after
+ me<sgmltag class="endtag">trademark</sgmltag></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+a266 16
+ <section id="sn-xml-guidelines-header">
+ <title>File Header</title>
+
+ <para>All the files must contain the CVS Id header. If you create a
+ new file, the first line must be:</para>
+
+ <screen><![CDATA[<!-- $Id: -->]]></screen>
+
+ <para>The first time it is committed to CVS (and every time it is
+ committed to CVS) the line is updated automatically to include
+ information about the file. For example:</para>
+
+ <screen><![CDATA[<!-- $Id: writing-guidelines.xml,v 1.6 2007/02/18 22:59:19 pfrields Exp $ -->]]></screen>
+
+ </section>
+
+@
+
+
+1.6
+log
+ at Some retagging and deconfusification
+@
+text
+ at d90 1
+a90 1
+ <table id="tb-id-two-char-naming-conventions">
+d92 35
+a126 46
+
+ <tgroup cols="2">
+ <colspec colnum="1" colname="tag"/>
+ <colspec colnum="2" colname="prefix"/>
+ <thead>
+ <row>
+ <entry>Tag</entry>
+ <entry>Prefix</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><sgmltag class="element">preface</sgmltag></entry>
+ <entry><literal>pr-</literal></entry>
+ </row>
+ <row>
+ <entry><sgmltag class="element">chapter</sgmltag></entry>
+ <entry><literal>ch-</literal></entry>
+ </row>
+ <row>
+ <entry><sgmltag class="element">section</sgmltag></entry>
+ <entry><literal>sn-</literal></entry>
+ </row>
+ <row>
+ <entry><sgmltag class="element">figure</sgmltag></entry>
+ <entry><literal>fig-</literal></entry>
+ </row>
+ <row>
+ <entry><sgmltag class="element">table</sgmltag></entry>
+ <entry><literal>tb-</literal></entry>
+ </row>
+ <row>
+ <entry><sgmltag class="element">appendix</sgmltag></entry>
+ <entry><literal>ap-</literal></entry>
+ </row>
+ <row>
+ <entry><sgmltag class="element">part</sgmltag></entry>
+ <entry><literal>pt-</literal></entry>
+ </row>
+ <row>
+ <entry><sgmltag class="element">example</sgmltag></entry>
+ <entry><literal>ex-</literal></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+d254 1
+a254 1
+ <screen><![CDATA[<!-- $Id: writing-guidelines.xml,v 1.5 2007/02/18 14:24:33 pfrields Exp $ -->]]></screen>
+@
+
+
+1.5
+log
+ at Remove RH from this particular equation
+@
+text
+ at d49 3
+a51 12
+ <para>This section explains the ID naming convention. For
+ example:</para>
+
+ <screen><![CDATA[<chapter id="ch-unique-name-of-chapter">
+
+<section id="sn-install-make-disks">
+
+<figure id="fig-redhat-config-kickstart-basic">]]></screen>
+
+ <para>IDs are unique identifiers, allowing DocBook XML to know where
+ to cross-reference a section, chapter, or other element. The
+ following general rules apply to IDs:</para>
+a61 2
+
+ <para>Keep it as short and simple as possible.</para>
+d63 26
+a88 3
+ <para>Start the ID with the special short two-character label. This
+ makes URLs and other references to this ID human readable, by
+ self-identifying the XML container type.</para>
+d94 2
+a95 2
+ <colspec colnum="1" colname="tag" colwidth="100"/>
+ <colspec colnum="2" colname="prefix" colwidth="100"/>
+d139 2
+a140 5
+ <para>Use the title of the item as the ID. If your title is not
+ unique, there is either a problem you need to fix (titles should
+ be unique within a document), or it is part of a template and
+ should reflect the containing chapter/section of the template. For
+ example:</para>
+d143 3
+a145 4
+<title>How To Fold Laundry</title>]]></screen>
+
+ <screen><![CDATA[<section id="sn-folding-shirts">
+<title>Folding Shirts</title>]]></screen>
+d265 1
+a265 1
+ <screen><![CDATA[<!-- $Id: writing-guidelines.xml,v 1.4 2007/02/05 00:33:47 pfrields Exp $ -->]]></screen>
+d331 8
+a338 3
+ <para>There are five types of admonitions in DocBook: Caution,
+ Important, Note, Tip, and Warning. All of the admonitions have
+ the same structure: an optional Title followed by paragraph-level
+d341 2
+a342 2
+ mandate that Warnings be reserved for cases where bodily harm can
+ result.</para>
+d345 5
+a349 2
+ <title>Creating Notes, Tips, Cautions, Importants, and
+ Warnings</title>
+d377 2
+a378 1
+ document. A <emphasis>Note</emphasis> is used to bring
+d380 18
+a397 16
+ <emphasis>Tip</emphasis> is used to show the user helpful
+ information or another way to do something. A
+ <emphasis>Caution</emphasis> is used to show the user they must
+ be careful when attempting a certain step. An
+ <emphasis>Important</emphasis> tag set can be used to show the
+ user a piece of information that should not be overlooked. While
+ this information may not change anything the user is doing, it
+ should show the user that this piece of information could be
+ vital. A <emphasis>Warning</emphasis> is used to show the reader
+ that their current setup will change or be altered, such as
+ files being removed, and they should not choose this operation
+ unless they are alright with the consequences.</para>
+
+ <para>The following lines of code will show the basic setup for
+ each case as mentioned above, along with an example of how it
+ would be displayed in the HTML.</para>
+d569 30
+a598 15
+ If you use a graphical screenshot to illustrate a function,
+ and the textual mode has identical functions, you should not
+ include both, unless omitting either would make your
+ description unclear. You should make your information
+ generic over specific. Omit the username and machine
+ information, and separate what the user types from sample
+ command output. Also, in <command>screen</command> tags,
+ what the user types should be in
+ <command>userinput</command> tags, and what the user is
+ shown as output should be in
+ <command>computeroutput</command> tags. For example, the
+ usage in
+ <xref linkend="ex-text-screenshot-bad"/> should look like
+ <xref
+ linkend="ex-text-screenshot-good"/>.
+d600 10
+a609 4
+ <example id="ex-text-screenshot-bad">
+ <title>Incorrect Textual Screenshot</title>
+ <screen><userinput>ps ax | grep ssh</userinput>
+<computeroutput> 2564 ? S 0:23 /usr/sbin/sshd
+d611 3
+a613 7
+ 8235 ? S 0:00 ssh -Nf rocky@@philadelphia.net -L 6667:localhost
+17223 pts/0 S 0:00 ssh rbalboa@@core-router7
+17227 pts/2 S 0:10 ssh rbalboa@@smbshare2
+21113 pts/7 S 1:19 ssh rocky@@xxx.private</computeroutput></screen>
+ </example>
+ <example id="ex-text-screenshot-good">
+ <title>Correct Textual Screenshot</title>
+d616 1
+a616 1
+ <screen><command>ps ax | grep ssh</command></screen>
+d618 1
+a618 1
+ <para>The output will appear similar to:</para>
+@
+
+
+1.4
+log
+ at Retagged some elements to make things more DocBooky. Use sgmltag to
+advantage, cool!
+@
+text
+ at d10 1
+a10 1
+<chapter id="ch-rh-guidelines">
+d257 1
+a257 1
+ <screen><![CDATA[<!-- $Id: writing-guidelines.xml,v 1.3 2007/02/04 13:57:23 kwade Exp $ -->]]></screen>
+@
+
+
+1.3
+log
+ at the latest stuff I did :)
+@
+text
+ at d20 1
+a20 1
+ <secondary>read the f*'ing manual</secondary>
+d33 2
+a34 3
+ not all available DocBook XML tags. For the complete list, refer to:</para>
+ <para>
+ <ulink url="http://www.docbook.org/tdg/en/html/docbook.html">http://www.docbook.org/tdg/en/html/docbook.html</ulink>
+d59 1
+a59 1
+ to cross-reference a section or chapter or the like. The
+d76 1
+a76 1
+ self-identifying what the XML container type is.</para>
+d92 2
+a93 2
+ <entry><command>preface</command></entry>
+ <entry><computeroutput>pr-</computeroutput></entry>
+d96 2
+a97 2
+ <entry><command>chapter</command></entry>
+ <entry><computeroutput>ch-</computeroutput></entry>
+d100 2
+a101 2
+ <entry><command>section</command></entry>
+ <entry><computeroutput>sn-</computeroutput></entry>
+d104 2
+a105 2
+ <entry><command>figure</command></entry>
+ <entry><computeroutput>fig-</computeroutput></entry>
+d108 2
+a109 2
+ <entry><command>table</command></entry>
+ <entry><computeroutput>tb-</computeroutput></entry>
+d112 2
+a113 2
+ <entry><command>appendix</command></entry>
+ <entry><computeroutput>ap-</computeroutput></entry>
+d116 2
+a117 2
+ <entry><command>part</command></entry>
+ <entry><computeroutput>pt-</computeroutput></entry>
+d120 2
+a121 2
+ <entry><command>example</command></entry>
+ <entry><computeroutput>ex-</computeroutput></entry>
+d154 7
+a160 4
+ <para>Do not use the trademark entities &trade;, &copy;, or
+ &reg; because the do not produce HTML output that works for all
+ charsets. The HTML output produces by these entities are declared in
+ the DTD and cannot be changed via the stylesheet.</para>
+d162 1
+a162 1
+ <para>Instead, use the <command>trademark</command> tag and its
+d167 3
+a169 1
+ <para><trademark>trademark symbol after me</trademark>
+d173 3
+a175 1
+ <para><trademark class="registered">registered trademark symbol after me</trademark>
+d179 3
+a181 1
+ <para><trademark class="copyright">copyright symbol after me</trademark></para>
+d187 1
+a187 1
+ <term>Content inside <command>para</command> tags</term>
+d189 1
+a189 1
+ <para>In general, use <command>para</command> tags
+d194 4
+a197 3
+ <para>Specifically, do not use <command>para</command> tags around
+ the following (or, to put this another way, do not embed the
+ following within <command>para</command> tags):
+d201 1
+a201 1
+ <para><screen></para>
+d204 1
+a204 1
+ <para><itemizedlist></para>
+d207 1
+a207 1
+ <para><orderedlist></para>
+d210 1
+a210 1
+ <para><variablelist></para>
+d213 1
+a213 1
+ <para><table></para>
+d219 8
+a226 11
+ <term>Content inside <command>para</command> tags within
+ <command>listitem</command> tags</term>
+ <listitem> <sect id="sn-xml-tags-caveats">
+ <title>Tags and Entities Caveats</title>
+
+
+ <para>Content inside <command>para</command> tags within
+ <command>listitem</command> tags <emphasis>must</emphasis> start
+ immediately after the beginning <para> tag to avoid extra
+ white space in the PDF version.
+ </para>
+d230 1
+a230 1
+ <term>Content inside <command>screen</command> tags</term>
+d232 3
+a234 2
+ <para>The content inside <command>screen</command> tags
+ (<screen> and </screen>)
+d257 1
+a257 1
+ <screen><![CDATA[<!-- $Id: writing-guidelines.xml,v 1.1 2007/02/03 22:21:58 kwade Exp $ -->]]></screen>
+d311 1
+a311 1
+ <Indexterm>
+d539 2
+d543 1
+d589 2
+d593 1
+@
+
+
+1.2
+log
+ at updating all section usage and associated ID tags
+@
+text
+ at d11 1
+a11 1
+ <title>&RH; Documentation Guidelines</title>
+d32 7
+a38 1
+ <section id="sn-xml-guidelines-naming">
+d50 1
+a50 2
+ <para>You will see certain ID names referred to below and this will
+ help to explain how we come up with those names. For
+d53 1
+a53 1
+ <screen><![CDATA[<chapter id="ch-uniquename">
+d72 6
+a77 26
+
+ <itemizedlist>
+ <listitem>
+ <para>Restrict the ID name, which is everything between the
+ quotation marks, to 32 characters or fewer</para>
+ </listitem>
+ <listitem>
+ <para>Keep it as short and simple as possible</para>
+ </listitem>
+ <listitem>
+ <para>Make sure the name is recognizable and relevant to the
+ information</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>Some examples are <command>"ch-uniquename"</command> (13
+ characters) and <command>"sn-install-make-disks"</command> (21
+ characters).</para>
+
+ <para>A section within a particular chapter always uses the chapter
+ name (minus the <command>"ch-"</command>) in its ID. For example,
+ you are working with the <command>"ch-intro"</command> chapter and
+ need to create your first section on disk partitions. That section
+ ID would look similar to <command>"sn-intro-partition"</command>
+ which contains the section number, the main chapter ID, and a
+ unique ID for that section.</para>
+d79 2
+a80 2
+ <table id="tb-xml-namingconventions">
+ <title>Naming Conventions</title>
+a104 16
+ <entry><command>section</command></entry>
+ <entry><computeroutput>sn-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>section</command></entry>
+ <entry><computeroutput>sn-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect3</command></entry>
+ <entry><computeroutput>s3-</computeroutput></entry>
+ </row>
+ <row>
+ <entry><command>sect4</command></entry>
+ <entry><computeroutput>s4-</computeroutput></entry>
+ </row>
+ <row>
+d128 108
+d304 1
+a304 1
+ <indexterm>
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d32 1
+a32 1
+ <sect1 id="s1-xml-guidelines-naming">
+d90 1
+a90 1
+ ID would look similar to <command>"s1-intro-partition"</command>
+d120 2
+a121 2
+ <entry><command>sect1</command></entry>
+ <entry><computeroutput>s1-</computeroutput></entry>
+d124 2
+a125 2
+ <entry><command>sect2</command></entry>
+ <entry><computeroutput>s2-</computeroutput></entry>
+d159 1
+a159 1
+ </sect1>
+d161 1
+a161 1
+ <sect1 id="s1-xml-guidelines-header">
+d173 1
+a173 1
+ <screen><![CDATA[<!-- $Id: docs-rh-guidelines.xml,v 1.3 2006/12/23 23:49:59 pfrields Exp $ -->]]></screen>
+d175 1
+a175 1
+ </sect1>
+d177 1
+a177 1
+ <sect1 id="s1-xml-admon">
+d247 1
+a247 1
+ <sect2 id="s2-xml-notesetc">
+d345 1
+a345 1
+ </sect2>
+d347 1
+a347 1
+ </sect1>
+d349 1
+a349 1
+ <sect1 id="s1-screenshots">
+d456 1
+a456 1
+ XML, refer to <xref linkend="s1-xml-tags-figure"/>.</para>
+d503 1
+a503 1
+ linkend="s1-xml-tags-screen"/>.</para>
+d507 1
+a507 1
+ </sect1>
+d510 1
+a510 1
+ <sect1 id="s1-diagrams-images">
+d525 1
+a525 1
+ </sect1>
+@
+
diff --git a/old-documentation-guide/en_US/xml-tags.xml,v b/old-documentation-guide/en_US/xml-tags.xml,v
new file mode 100644
index 0000000..ed15b94
--- /dev/null
+++ b/old-documentation-guide/en_US/xml-tags.xml,v
@@ -0,0 +1,3060 @@
+head 1.6;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.6
+ LIVE:1.6;
+locks; strict;
+comment @# @;
+
+
+1.6
+date 2007.06.23.05.25.29; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.02.04.14.55.28; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.02.04.14.46.04; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.02.04.13.42.58; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.02.03.22.29.37; author kwade; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.02.03.22.21.58; author kwade; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.6
+log
+ at Small xref error
+@
+text
+@<!-- $Id: xml-tags.xml,v 1.5 2007/02/04 14:55:28 pfrields Exp $ -->
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- *************** Bring in Fedora entities *************** -->
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES-EN;
+
+]>
+
+
+ <chapter id="ch-xml-tags">
+ <title>DocBook XML Tags</title>
+
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>tags</secondary>
+ <see>XML tags</see>
+ </indexterm>
+
+ <para>Please read this chapter carefully. This chapter describes the tags
+ used by the Docs Project. Some of the rules described are specific to the
+ project.
+ </para>
+
+ <para>If these tags are used appropriately, document searches will provide
+ meaningful results. These tags help search engines identify the
+ information relevant to the search request. Another benefit is that all
+ &PROJECT; documents will have a similar look and feel (however, they will have
+ some differences depending upon the output format).
+ </para>
+
+ <indexterm>
+ <primary>XML</primary>
+ <secondary>general tag information</secondary>
+ </indexterm>
+
+ <para>Most tags in XML must have an opening and closing tag. A few
+ tags, such as <sgmltag class="emptytag">xref</sgmltag>, have no
+ content and close themselves. Additionally,
+ proper XML conventions say that there must be a unique identifier for
+ sections, chapters, figures, tables, and so on, so that they may be
+ correctly identified, and cross referenced if needed.</para>
+
+ <para>Although XML is capable of handling many document types, the format
+ discussed here is the article format.</para>
+
+ <para>
+ This chapter only discusses tags used for documentation for the
+ &PROJECT;, not all available DocBook XML tags. For the complete
+ list, refer to <ulink
+ url="http://www.docbook.org/tdg/en/html/docbook.html"/>.
+ </para>
+
+ <section id="sn-xml-tags-caveats">
+ <title>Tags and Entities Caveats</title>
+
+ <indexterm>
+ <primary>xml tags</primary>
+ <secondary>caveats</secondary>
+ </indexterm>
+
+ <para>
+ It is very important that you remember the caveats in this section. Even
+ though they are more strict than valid DocBook XML, these rules exist
+ so that both the HTML and PDF outputs look proper.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>Do Not Use Trademark Entities</term>
+ <listitem>
+ <para>Do not use the trademark entities <sgmltag
+ class="genentity">trade</sgmltag>, <sgmltag
+ class="genentity">copy</sgmltag>, or <sgmltag
+ class="genentity">reg</sgmltag> because they do not produce
+ HTML output that works for all charsets. The HTML output
+ produces by these entities are declared in the DTD and
+ cannot be changed via the stylesheet.</para>
+ <para>Instead, use the <sgmltag class="element">trademark</sgmltag> tag and its
+ associates classes as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><sgmltag
+ class="starttag">trademark</sgmltag>trademark symbol after
+ me<sgmltag class="endtag">trademark</sgmltag>
+ </para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="starttag">trademark
+ class="registered"</sgmltag>registered trademark symbol
+ after me<sgmltag class="endtag">trademark</sgmltag>
+ </para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="starttag">trademark
+ class="copyright"</sgmltag>copyright symbol after
+ me<sgmltag class="endtag">trademark</sgmltag></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <sgmltag>para</sgmltag> tags</term>
+ <listitem>
+ <para>Do not use <sgmltag>para</sgmltag> tags around
+ anything other than a simple paragraph. Doing so will create
+ additional white space within the text itself in the PDF
+ version.
+ </para>
+ <para>Specifically, do not use <sgmltag>para</sgmltag> tags
+ around the following (or, to put this another way, do not
+ embed the following within <sgmltag>para</sgmltag> tags):
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><sgmltag class="element">screen</sgmltag></para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="element">itemizedlist</sgmltag></para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="element">orderedlist</sgmltag></para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="element">variablelist</sgmltag></para>
+ </listitem>
+ <listitem>
+ <para><sgmltag class="element">table</sgmltag></para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <sgmltag>para</sgmltag> tags within
+ <sgmltag>listitem</sgmltag> tags</term>
+ <listitem>
+ <para>Content inside <sgmltag>para</sgmltag> tags within
+ <sgmltag>listitem</sgmltag> tags <emphasis>must</emphasis>
+ start immediately after the beginning <sgmltag
+ class="starttag">para</sgmltag> tag to avoid extra white
+ space in the PDF version.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Content inside <sgmltag>screen</sgmltag> tags</term>
+ <listitem>
+ <para>The content inside <sgmltag>screen</sgmltag> tags
+ (<sgmltag class="starttag">screen</sgmltag> and <sgmltag
+ class="endtag">screen</sgmltag>)
+ <emphasis>must</emphasis> be flush left in the XML file;
+ otherwise, the extraneous whitespace will appear in the HTML
+ version.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="sn-xml-tags-application">
+ <title><sgmltag>application</sgmltag></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>application</secondary>
+ </indexterm>
+
+ <para>An application is the name of a GUI software program. A command is
+ the name of an executable (text) program or a software command.</para>
+
+ <para>The <sgmltag class="starttag">application</sgmltag> and
+ <sgmltag class="endtag">application</sgmltag> tags allow you to refer to an
+ application or program. For example, the following XML:
+ </para>
+
+<screen>
+<computeroutput>
+To view the Web in Linux, you can use
+<sgmltag class="starttag">application</sgmltag>Mozilla<sgmltag
+ class="endtag">application</sgmltag>
+or <sgmltag class="starttag">application</sgmltag>lynx<sgmltag
+ class="endtag">application</sgmltag> if
+you only want a text-based browser.
+</computeroutput>
+</screen>
+
+ <para>
+ produces the following output:
+ </para>
+
+ <para>
+ To view the Web in Linux, you can use <application>Mozilla</application>
+ or <application>lynx</application> if you only want a text-based browser.
+ </para>
+
+ </section>
+
+ <section id="sn-xml-tags-chapter">
+ <title><sgmltag>chapter</sgmltag></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>chapter</secondary>
+ </indexterm>
+
+ <para>
+ A DocBook book can be divided into chapters such as:
+ </para>
+
+<screen>
+<computeroutput>
+<!--$Id: xml-tags.xml,v 1.5 2007/02/04 14:55:28 pfrields Exp $ -->
+
+ <chapter id="ch-sample">
+ <title>Sample Chapter</title>
+
+ <para>This is a sample chapter, showing you the XML tags used to create a
+ chapter, sections, and subsections.</para>
+
+ </chapter>
+</computeroutput>
+</screen>
+
+ <para>
+ The chapter can also be further divided into sections
+ (<sgmltag>section</sgmltag>, <sgmltag>section</sgmltag>,
+ <sgmltag>sect3</sgmltag>, etc.). Refer to <xref
+ linkend="sn-xml-tags-sections"/> for details.
+ </para>
+
+ </section>
+
+
+ <section id="sn-xml-tags-citetitle">
+ <title><sgmltag>citetitle</sgmltag></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>citetitle</secondary>
+ </indexterm>
+
+
+ <para>
+ The <sgmltag>citetitle</sgmltag> tag provides formatting for a
+ specific references (title can be manually typed out or if already
+ defined within your document set, given as an entity<footnote><para>An
+ entity is a short hand way of referring to some predefined
+ content, such as a title or name. It
+ can be defined within the parent document or within a set of files that
+ your DTD references for your specific documentation set.</para>
+ </footnote>
+ ).</para>
+
+ <para>
+ For example:
+ </para>
+<screen>
+<computeroutput>
+<sgmltag class="starttag">citetitle</sgmltag><sgmltag class="genentity">IG</sgmltag><sgmltag class="endtag">citetitle</sgmltag>.
+</computeroutput>
+</screen>
+ <para>
+ The output looks like <citetitle>&IG;</citetitle> because <sgmltag
+ class="genentity">IG</sgmltag> is an entity.
+ </para>
+
+ </section>
+
+ <section id="sn-xml-tags-command">
+ <title><sgmltag>command</sgmltag></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>command</secondary>
+ </indexterm>
+
+ <para>An application is the name of a GUI software program. A command is
+ the name of an executable (text) program or a software command. Any
+ program that is a command line or text-based only tool is marked with
+ <sgmltag>command</sgmltag> tags.</para>
+
+
+ <para>If you have text that is a command, use the
+ <sgmltag class="starttag">command</sgmltag> and
+ <sgmltag class="endtag">command</sgmltag> tags such as:
+ </para>
+
+
+
+<screen>
+<computeroutput>
+To change your keyboard after installation, become root
+and use the <command>redhat-config-keyboard</command> command,
+or you can type <command>setup</command> at the root prompt.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+ <para>
+ To change your keyboard after installation, become root and use
+ the <command>redhat-config-keyboard</command> command, or you can type
+ <command>setup</command> at the root prompt.
+ </para>
+
+ <para>Another example would be:</para>
+
+<screen>
+<computeroutput>
+<command>MAILNOVIOLATIONS</command> — If set
+to <command>true</command> this option tells Tripwire to
+email a report at a regular interval regardless of whether or not
+any violations have occured. The default value is
+<command>true</command>.
+</computeroutput>
+</screen>
+
+ <para>
+ with the output:
+ </para>
+
+ <para>
+ <command>MAILNOVIOLATIONS</command> — If set to
+ <command>true</command> this variable tells Tripwire to email a report
+ at a regular interval regardless of whether or not any violations have
+ occured. The default value is <command>true</command>.
+ </para>
+
+ <note>
+ <title>Note</title> <para>In this example, the option value (true) is
+ defined with a <command> tag set. Because a option is a
+ configuration file option (command line options which would use the
+ <option> tag set), and because there is no configuration file
+ option tag available to use, we are extending the <command> tag
+ set to define options in a configuration file.</para>
+ </note>
+
+ <para>
+ Terms marked with <command>command</command> tags because there aren't
+ exact tags for them:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Options in configuration files such as Apache directives</para>
+ </listitem>
+ <listitem>
+ <para>daemon names</para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+
+ <section id="sn-xml-tags-compoutput">
+ <title><command>computeroutput</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>computeroutput</secondary>
+ </indexterm>
+
+ <para>
+ To show computer output use the following tags:
+ </para>
+<screen>
+<computeroutput>
+<computeroutput>Do you want to delete this file? y n</computeroutput>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+ <para>
+ <computeroutput>Do you really want to delete this file? y n</computeroutput>
+ </para>
+ </section>
+
+ <section id="sn-xml-tags-emphasis">
+ <title><command>emphasis</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>emphasis</secondary>
+ </indexterm>
+
+ <para>
+ To emphasis content, use the <command><emphasis></command> and
+ <command></emphasis></command> tags. For example:
+ </para>
+<screen>
+<computeroutput>
+This installation <emphasis>will remove all</emphasis> existing
+Linux partitions on <emphasis>all</emphasis> hard drives in your
+system; non-Linux partitions will not be removed.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ This installation <emphasis>will remove all</emphasis> existing Linux
+ partitions on <emphasis>all</emphasis> hard drives in your system;
+ non-Linux partitions will not be removed.
+ </para>
+ </section>
+
+ <section id="sn-xml-tags-example">
+ <title><command>example</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>example</secondary>
+ </indexterm>
+
+ <para>The <command><example></command> and
+ <command></example></command> tags are used to format text within a
+ document and is great for adding emphasis to show examples of code,
+ exercises, and more. </para>
+
+ <para>The <command><example></command> tag set should be given an ID
+ and title:</para>
+
+<screen>
+ <example id="static-ip">
+ <title>Static IP Address using DHCP</title>
+
+<screen width=60>
+<computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+<computeroutput>
+</screen>
+
+ </example>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <example id="static-ip">
+ <title>Static IP Address using DHCP</title>
+
+<screen>
+<computeroutput>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+</computeroutput>
+</screen>
+ </example>
+
+ </section>
+
+
+ <section id="sn-xml-tags-filename">
+ <title><command>filename</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>filename</secondary>
+ </indexterm>
+
+ <para>
+ The <command><filename></command> and
+ <command></filename></command> tags define a filename or path to a
+ file. Since directories are just special files, they are marked with the
+ <command>filename</command> tags as well. For example:
+ </para>
+<screen>
+Edit the <filename>/home/smoore/sam.xml</filename> file to make
+changes or add comments.
+</screen>
+ <para>
+ The output:
+ </para>
+ <para>
+ Edit the <filename>/home/smoore/sam.xml</filename> file to make changes
+ or add comments.
+ </para>
+
+ <para>
+ They are also used to markup an RPM package name. For example:
+ </para>
+<screen>
+To use the <application>Keyboard Configuration Tool</application>, the
+<filename>system-config-keyboard</filename> RPM package must be installed.
+</screen>
+ <para>
+ The output:
+ </para>
+ <para>
+ To use the <application>Keyboard Configuration Tool</application>, the
+ <command>redhat-config-keyboard</command> RPM package must be installed.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ Directory names must end with a forward slash
+ (<computeroutput>/</computeroutput>) to distinguish them from file
+ names.
+ </para>
+ </note>
+
+ </section>
+
+ <section id="sn-xml-tags-firstterm">
+ <title><command>firstterm</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>firstterm</secondary>
+ </indexterm>
+
+ <para>
+ The <command><firstterm></command> and
+ <command></firstterm></command> tags helps to define a word that
+ may be unfamiliar to the user, but that will be seen commonly throughout
+ the text. For example:
+ </para>
+<screen>
+<computeroutput>
+Nearly every modern-day operating system uses <firstterm>disk
+partitions</firstterm>, and &FC; is no exception.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Nearly every modern-day operating system uses <firstterm>disk
+ partitions</firstterm>, and &FC; is no exception.
+ </para>
+
+ </section>
+
+ <section id="sn-xml-tags-footnote">
+ <title><command>footnote</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>footnote</secondary>
+ </indexterm>
+
+ <para>
+ If you need to make a footnote, use the following example:
+ </para>
+<screen>
+<computeroutput>
+For those of you who need to perform a server-class
+<footnote>
+<para>
+A server-class installation sets up a typical server
+environment. Note, no graphical environment is
+installed during a server-class installation.
+</para>
+</footnote> installation, refer to the <citetitle>Installation Guide</citetitle>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ For those of you who need to perform a server-class <footnote> <para>A
+ server-class installation sets up a typical server environment. Please note, no
+ graphical environment is installed during a server-class installation.</para>
+ </footnote> installation, refer to the
+ <citetitle>Installation Guide</citetitle>.
+ </para>
+
+ </section>
+
+ <section id="sn-xml-tags-figure">
+ <title><command>figure</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>figure</secondary>
+ </indexterm>
+
+ <important>
+ <title>Important</title>
+ <para>
+ Order matters! The EPS file <emphasis>must</emphasis> be declared
+ first.
+ </para>
+ </important>
+
+ <para>
+ An example figure declaration:
+ </para>
+
+<screen>
+<computeroutput>
+<figure id="fig-ksconfig-basic">
+ <title>Basic Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.eps"
+ format="EPS"/>
+ </imageobject>
+ <imageobject>
+ <imagedata fileref="./figs/ksconfig/ksconfig-basic.png"
+ format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>
+ Some text description of this image
+ </phrase>
+ </textobject>
+ </mediaobject>
+</figure>
+</computeroutput>
+</screen>
+
+ <para>
+ The following describes what needs to be edited:
+ </para>
+
+<screen>
+<figure id="fig-ksconfig-basic"> <emphasis>==> id="" would be edited</emphasis>
+
+<title>Basic Configuration</title> <emphasis>==> title would be edited</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.eps"> <emphasis>==> .eps location would be edited</emphasis>
+
+fileref="./figs/ksconfig/ksconfig-basics.png"> <emphasis>==> .png location would be edited</emphasis>
+
+<phrase>Some text description of this image</phrase> <emphasis>==> "Some text..." would be edited</emphasis>
+</screen>
+
+ <para>
+ For more information on taking screenshots, refer to <xref
+ linkend="sn-screenshots"/>.
+ </para>
+
+ </section>
+
+ <section id="sn-xml-tags-gui">
+ <title>GUI Tags</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ </indexterm>
+
+ <section id="sn-xml-tags-guilabel">
+ <title><command>guilabel</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guilabel</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guilabel</secondary>
+ </indexterm>
+
+ <para>
+ Use the <command><guilabel></command> and
+ <command></guilabel></command> tags as a default for GUI
+ descriptions, like a screen name or screen title. For example:
+ </para>
+<screen>
+<computeroutput>
+The <guilabel>Authentication Configuration</guilabel> screen
+shows you how to make your system more secure.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ The <guilabel>Authentication Configuration</guilabel> screen shows you how to
+ make your system more secure.
+ </para>
+ </section>
+
+ <section id="sn-xml-tags-guibutton">
+ <title><command>guibutton</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guibutton</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guibutton</secondary>
+ </indexterm>
+
+ <para>
+ Use the <command><guibutton></command> and
+ <command></guibutton></command> tags to denote a button on a screen or
+ menu. For example:
+ </para>
+<screen>
+<computeroutput>
+Check the <guibutton>Activate on boot</guibutton> button
+to have the X Window System start automatically.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Check the <guibutton>Activate on boot</guibutton> button to have the X
+ Window System start automatically.
+ </para>
+ </section>
+
+ <section id="sn-xml-tags-guiicon">
+ <title><command>guiicon</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guiicon</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guiicon</secondary>
+ </indexterm>
+
+ <para>
+ The <command><guiicon></command> and <command></guiicon></command>
+ tags are used to denote a panel or desktop icon. For example:
+ </para>
+<screen>
+<computeroutput>
+Double-click the <guiicon>Start Here</guiicon> icon on the desktop.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Double-click the <guiicon>Start Here</guiicon> icon on the desktop.
+ </para>
+
+ </section>
+
+ <section id="sn-xml-tags-guimenu">
+ <title><command>guimenu</command> and
+ <command>guimenuitem</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guimenu</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guimenu</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>GUI tags</secondary>
+ <tertiary>guimenuitem</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>guimenuitem</secondary>
+ </indexterm>
+
+ <para>
+ To note a menu (like in the installation program or within the control panel),
+ use the <command><guimenu></command> and
+ <command></guimenu></command> tags.
+ </para>
+
+ <para>
+ To note submenu items, use the <command><guimenuitem></command> and
+ <command></guimenuitem></command> tags. (Please note that there should not
+ be any breaks between these commands, but for printing purposes breaks have been
+ inserted). For example:
+ </para>
+<screen>
+<computeroutput>
+Select
+<guimenu>Main Menu</guimenu> =>
+ <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> to start the
+<application>Emacs</application> text editor.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ From the control panel, click on <guimenu>Main Menu</guimenu> =>
+ <guimenuitem>Programming</guimenuitem> =>
+ <guimenuitem>Emacs</guimenuitem> to start the
+ <application>Emacs</application> text editor.
+ </para>
+ </section>
+ </section>
+
+ <section id="sn-xml-tags-keycap">
+ <title><command>keycap</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>keycap</secondary>
+ </indexterm>
+
+ <para>
+ To denote a specific key, you will need to use the
+ <command><keycap></command> and <command></keycap></command>
+ tags. Brackets are automatically added around the keycap, so do not add
+ them in your XML code. For example:
+ </para>
+<screen>
+<computeroutput>
+To make your selection, press the <keycap>Enter</keycap> key.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ To make your selection, press the <keycap>Enter</keycap> key.
+ </para>
+
+ <section id="sn-xml-tags-menuchoice">
+ <title><command>menuchoice</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>menuchoice</secondary>
+ </indexterm>
+
+ <para>
+ Often using a mouse is tedious for common tasks. Therefore,
+ programmers often build in keyboard-shortcuts to simplify their
+ program. These should be described using the shortcut tag as a wrapper
+ for the keyboard tags. The shortcut tag must be wrapped inside the
+ menuchoice tag. For example:
+ </para>
+
+<screen>
+<computeroutput>
+Go to the menu bar and choose:
+ <menuchoice>
+ <shortcut>
+ <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
+ </shortcut>
+ <guimenu><accel>F</accel>ile</guimenu>
+ <guimenuitem><accel>S</accel>ave</guimenuitem>
+ </menuchoice>.
+</computeroutput>
+</screen>
+
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Go to the menu bar and choose:
+ <menuchoice>
+ <shortcut>
+ <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
+ </shortcut>
+ <guimenu><accel>F</accel>ile</guimenu>
+ <guimenuitem><accel>S</accel>ave</guimenuitem>
+ </menuchoice>.
+ </para>
+
+ </section>
+
+ <section id="sn-xml-tags-keycombo">
+ <title><command>keycombo</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>keycombo</secondary>
+ </indexterm>
+
+ <para>
+ To illustrate a key combination, you need to use the
+ <command><keycombo></command> and
+ <command></keycombo></command>,
+ <command><keycap></command> and
+ <command></keycap></command> tags. For example:
+ </para>
+<screen>
+<computeroutput>
+To reboot your system, press <keycombo>
+<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>
+</keycombo>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ To reboot your system, press
+ <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>
+ </keycombo>.
+ </para>
+
+ </section>
+
+ </section>
+
+ <section id="sn-xml-tags-lists">
+ <title>Lists</title>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary>creating</secondary>
+ </indexterm>
+
+ <para>There are several types of lists you can create using XML. You
+ can have a itemized (bulleted) list, a ordered (numbered) list, or a
+ variable list (presents a term and then a separate paragraph).</para>
+
+ <para>There is also a list format for tables and for for creating a
+ list of glossary terms and their definitions.</para>
+
+ <para>The sections below will discuss the proper uses for the various
+ list and how to create them.</para>
+
+ <section id="sn-xml-tags-itemizedlist">
+ <title><command>itemizedlist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>itemizedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>itemizedlist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>itemizedlist</command></secondary>
+ </indexterm>
+
+ <para>An <command>ItemizedList</command> is best used to present
+ information that is important for the reader to know, but that does
+ not need to be in a specific order. It is shorter than a
+ <command>VariableList</command> and presents the information in a
+ very simple way.</para>
+
+ <para>To create an <command>ItemizedList</command> (otherwise known as
+ bulleted list), use the following command sequence:</para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command>
+ tags. If you do not do this, you will find extra whitespace in
+ your lists where the text does not line up correctly. This is most
+ noticeable when you have a series of list items that consist of
+ multiple lines of text. This whitespace is not as noticeable in
+ the HTML output as it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<itemizedlist>
+ <listitem>
+ <para>Getting familiar with the installation program's user interface</para>
+ </listitem>
+
+ <listitem>
+ <para>Starting the installation program</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting an installation method</para>
+ </listitem>
+</itemizedlist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Getting familiar with the installation program's user interface</para>
+ </listitem>
+
+ <listitem>
+ <para>Starting the installation program</para>
+ </listitem>
+
+ <listitem>
+ <para>Selecting an installation method</para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+
+ <section id="sn-xml-tags-orderedlist">
+ <title><command>OrderedList</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>orderedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>orderedlist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>orderedlist</tertiary>
+ </indexterm>
+
+ <para>An <command>orderedlist</command> is best used to present
+ information that is important for the reader to know in a specific
+ order. <command>orderedlist</command>s are a good way to convey
+ step-by-step senarios to the audience you are writing for.</para>
+
+ <para>
+ To create an <command>orderedlist</command> (numbered list), use the
+ following XML code sequence:
+ </para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command>
+ tags. If you do not do this, you will find extra whitespace in
+ your lists where the text does not line up correctly. This is most
+ noticeable when you have a series of list items that consist of
+ multiple lines of text. This whitespace is not as noticeable in
+ the HTML output as it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<orderedlist>
+ <listitem>
+ <para>Online &mdash; http://www.redhat.com/support/errata; supplies errata
+ you can read online, and you can download diskette images
+ easily.</para>
+ </listitem>
+
+ <listitem>
+ <para>Email &mdash; By sending an empty mail message to errata@@redhat.com,
+ you will receive an email containing a text listing of the
+ complete errata of the installation program and related software
+ (if errata exist at that time). Also included are URLs to each
+ updated package and diskette image in the errata. Using these
+ URLs, you can download any necessary diskette images. Please
+ note: use binary mode when transferring a diskette image.</para>
+ </listitem>
+</orderedlist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <orderedlist>
+ <listitem>
+ <para>Online — http://www.redhat.com/support/errata; supplies errata
+ you can read online, and you can download diskette images
+ easily.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Email — By sending an empty mail message to
+ errata@@redhat.com, you will receive an email containing a text
+ listing of the complete errata of the installation program and
+ related software (if errata exist at that time). Also included
+ are URLs to each updated package and diskette image in the
+ errata. Using these URLs, you can download any necessary
+ diskette images. Please note: use binary mode when transferring
+ a diskette image.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ </section>
+
+ <section id="sn-xml-tags-varlist">
+ <title><command>Variablelist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>variablelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>variablelist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>variablelist</command></secondary>
+ </indexterm>
+
+ <para>A <command>variablelist</command> best represents a list of
+ terms and definitions or descriptions for those terms.</para>
+
+ <para>To create a <command>variablelist</command>, use the following
+ command sequence:
+ </para>
+
+ <note>
+ <title>Note</title> <para>Notice below that the text for the list
+ item is directly surrounded by the <command>para</command> tags. If
+ you do not do this, you will find extra whitespace in your lists
+ where the text does not line up correctly. This is most noticeable
+ when you have a series of list items that consist of multiple lines
+ of text. This whitespace is not as noticeable in the HTML output as
+ it is in the PDFs.</para>
+ </note>
+
+<screen>
+<computeroutput>
+<variablelist>
+ <varlistentry>
+ <term> New Multi-CD Install </term>
+ <listitem>
+ <para>As the installation program continues to grow, Red Hat has developed
+ an installation program capable of installing from
+ multiple CD-ROMs.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>XFree 4.0 </term>
+ <listitem>
+ <para>Configuration of your X Window System during the installation has
+ never been more thorough. From choosing your monitor and its correct
+ settings, to video card probing, to testing your desired X setup,
+ Xconfigurator will help you set everything just right.</para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <variablelist>
+ <varlistentry>
+ <term>New Multi-CD Install</term> <listitem> <para>As the
+ installation program continues to grow, Red Hat has developed an
+ installation program capable of installing from
+ multiple CD-ROMs.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term> XFree 4.0</term>
+ <listitem>
+ <para>Configuration of your X Window System during the
+ installation has never been more thorough. From choosing your
+ monitor and its correct settings, to video card probing, to
+ testing your desired X setup, Xconfigurator will help you set
+ everything just right.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <warning>
+ <title>Warning</title>
+ <para>
+ Do <emphasis>not</emphasis> specify the
+ <computeroutput>frame</computeroutput> attribute to the table. Doing
+ so breaks PDF production.
+ </para>
+ </warning>
+
+ </section>
+
+ <section id="sn-xml-tags-simplelist">
+ <title>Creating a List Within a Table Using <command>Simplelist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>simplelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>simplelist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>simplelist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>tables</primary>
+ <secondary>creating a list within a table</secondary>
+ <tertiary><command>simplelist</command></tertiary>
+ </indexterm>
+
+ <para>A <command>simplelist</command> is an unadorned list of
+ items. <command>simplelist</command>s can be inline or arranged in
+ columns.</para>
+
+ <para>We use <command>simplelist</command> to add separate paragraphs
+ of text within a table element. A regular list, such as
+ <command>itemizedlist</command>, cannot be embedded within a table.</para>
+
+ <para>The XML commands for a table look like:</para>
+
+<screen>
+<computeroutput>
+ <table id="tb-hwinfo-hostbus">
+ <title>Host Bus Adapter Features and Configuration Requirements</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="HostBus" colwidth="33"/>
+ <colspec colnum="2" colname="Features" colwidth="34"/>
+ <colspec colnum="3" colname="Single" colwidth="33"/>
+
+ <thead>
+ <row>
+ <entry>Host Bus Adapter</entry>
+ <entry>Features</entry>
+ <entry>Single-Initiator Configuration</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is
+ off.</member>
+ </simplelist></entry>
+
+ <entry><simplelist>
+ <member>Set the onboard termination to automatic (the
+ default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ <row>
+ <entry>Qlogic QLA1080</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is off,
+ unless jumpers are used to enforce termination.</member>
+ </simplelist></entry>
+
+
+ <entry><simplelist>
+ <member>Set the onboard termination to
+ automatic (the default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+</computeroutput>
+</screen>
+
+ <para>The output looks like:</para>
+
+ <table id="tb-hwinfo-hostbus">
+ <title>Host Bus Adapter Features and Configuration Requirements</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="HostBus" colwidth="33"/>
+ <colspec colnum="2" colname="Features" colwidth="34"/>
+ <colspec colnum="3" colname="Single" colwidth="33"/>
+
+ <thead>
+ <row>
+ <entry>Host Bus Adapter</entry>
+ <entry>Features</entry>
+ <entry>Single-Initiator Configuration</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Adaptec 2940U2W</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD.</member>
+ <member>HD68 external connector.</member>
+ <member>One channel, with two bus segments.</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is
+ off.</member>
+ </simplelist></entry>
+
+ <entry><simplelist>
+ <member>Set the onboard termination to automatic (the
+ default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ <row>
+ <entry>Qlogic QLA1080</entry>
+
+ <entry><simplelist>
+ <member>Ultra2, wide, LVD</member>
+ <member>VHDCI external connector</member>
+ <member>One channel</member>
+ <member>Set the onboard termination by using the BIOS
+ utility.</member>
+ <member>Onboard termination is disabled when the power is off,
+ unless jumpers are used to enforce termination.</member>
+ </simplelist></entry>
+
+
+ <entry><simplelist>
+ <member>Set the onboard termination to
+ automatic (the default).</member>
+ <member>Use the internal SCSI connector for private
+ (non-cluster) storage.</member>
+ </simplelist></entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+ <note>
+ <title>Note</title>
+ <para>Notice how the <command>SimpleList</command> tags are
+ used. The <entry> and <simplelist> tags must be aligned
+ beside one another, otherwise you will receive a parsing error.</para>
+ </note>
+
+ <para>For each paragraph or list item to be added within a
+ <command>SimpleList</command>, the <member> tag set must be
+ added around that particular text item.</para>
+ </section>
+
+ <section id="sn-xml-tags-glossary">
+ <title><command>glosslist</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>glosslist</command></secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>lists</secondary>
+ <tertiary>glosslist</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>lists</primary>
+ <secondary><command>glosslist</command></secondary>
+ </indexterm>
+
+ <para>Use the <command>glosslist</command> command set to create a
+ list of glossary terms and their definitions.</para>
+
+
+ <para>In XML, an example looks like the following:</para>
+
+<screen>
+<computeroutput>
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>A small application, usually a utility or other
+ simple program.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>The design for organization and integration of
+ components within a computer or computer system.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>To transfer files into storage for the purpose of
+ saving space and/or organization.</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+</computeroutput>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <glosslist>
+ <glossentry>
+ <glossterm>applet</glossterm>
+ <glossdef>
+ <para>A small application, usually a utility or other simple program.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>architecture</glossterm>
+ <glossdef>
+ <para>The design for organization and integration of components
+ within a computer or computer system.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>archive</glossterm>
+ <glossdef>
+ <para>To transfer files into storage for the purpose of saving
+ space and/or organization.</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+
+ </section>
+ </section>
+
+
+ <section id="sn-xml-tags-option">
+ <title><command>option</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>option</secondary>
+ </indexterm>
+
+ <para>If you have a command that offers an option or a flag, use the
+ <command><option></command> and
+ <command></option></command> tags.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>The <option> tag set is only meant to be used for command
+ line options, not options in configuration files.</para>
+ </note>
+
+ <para>In XML, specifying an option would look like the
+ following:</para>
+
+<screen>
+<computeroutput>
+For example, with the command <command>ls</command> you can
+specify an option such as <option>-la</option>.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>For example, with the command <command>ls</command> you can
+ specify an option such as <option>-la</option>.</para>
+
+ </section>
+
+ <section id="sn-xml-tags-indexing">
+ <title>Index Entries</title>
+
+ <indexterm>
+ <primary>indexing</primary>
+ </indexterm>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>indexing</secondary>
+ </indexterm>
+
+ <para>The following command sequence shows you the code inserted into
+ the body of the text to add an index entry to your document:
+ </para>
+
+<screen>
+<computeroutput>
+<indexterm> <-- indicates a term to be placed in the index
+<primary>foo</primary> <-- indicates that "foo" is the first term
+<secondary>bar</secondary> <-- "bar" will be listed under "foo"
+</indexterm> <-- closes this index entry
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>foo</primary>
+ <secondary>bar</secondary>
+ </indexterm>
+
+
+ <para>The <command><seealso></command> tag allows you to
+ reference another index entry or refer to another manual. Make sure
+ the <command><seealso></command> reference you are pointing to
+ has its own entry. For example:
+ </para>
+
+ <indexterm>
+ <primary>indexing</primary>
+ <secondary>seealso tag</secondary>
+ </indexterm>
+
+<screen>
+<computeroutput>
+<indexterm>
+<primary>SWAK</primary>
+<seealso>salutations</seealso>
+</indexterm>
+
+
+<indexterm>
+<primary>salutations</primary>
+</indexterm>
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>SWAK</primary>
+ <seealso>Salutations</seealso>
+ </indexterm>
+
+ <indexterm>
+ <primary>Salutations</primary>
+ </indexterm>
+
+ <para>
+ The <command><see></command> tag allows you to reference to
+ another index entry entirely. For example:
+ </para>
+ <indexterm>
+ <primary>indexing</primary>
+ <secondary>see tag</secondary>
+ </indexterm>
+
+
+<screen>
+<computeroutput>
+<indexterm>
+<primary>Guinness</primary>
+<see>beer</see> <-- beer will be listed under
+the Guinness entry, but you must make sure beer also has its
+own entry to refer to.
+</indexterm>
+
+<indexterm>
+<primary>beer</primary>
+</indexterm>
+</computeroutput>
+</screen>
+
+ <indexterm>
+ <primary>Guinness</primary>
+ <see>Beer</see>
+ </indexterm>
+
+ <indexterm>
+ <primary>Beer</primary>
+ </indexterm>
+
+ <para>To view the HTML output of the index entries shown here, refer
+ to the <filename>generated-index.html</filename> file at the end of
+ this document.</para>
+
+ <para>How does the index get generated? If indexterms exist in the
+ document and the beginning and ending index tags exist before the end
+ tag for the book or article, an index is created because of the
+ <command>generate.index</command> stylesheet parameter, which is set to
+ true by default.
+ </para>
+
+ </section>
+
+ <section id="sn-xml-tags-para">
+ <title><command>para</command></title>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>para</secondary>
+ </indexterm>
+
+ <para>For any paragraph, the <command><para></command> and
+ <command></para></command> tags must open and close that
+ particular paragraph.
+ </para>
+
+ <para>Do not use para tags around anything other than a simple
+ paragraph. Doing so will create additional white space within
+ the text itself.</para>
+
+ <para>Do not use <command><para></command> tags around the
+ following (or, to put this another way, do not embed the
+ following within <command><para></command> tags):</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><command><screen></command></para>
+ </listitem>
+ <listitem>
+ <para><command><itemizedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><orderedlist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><variablelist></command></para>
+ </listitem>
+ <listitem>
+ <para><command><table></command></para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+
+ <section id="sn-xml-tags-part">
+ <title><command>part</command></title>
+
+ <indexterm>
+ <primary>parts</primary>
+ </indexterm>
+
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>part</secondary>
+ </indexterm>
+
+ <para>
+ In the parent file, you can separate the chapters into parts to divide
+ them into logical groups. For example, in the parent file, the
+ <command>part</command> tags surround the chapter entities:
+ </para>
+<screen>
+<computeroutput>
+<part id="pt-foo">
+ <partintro>
+ <para>Some text for the part intro</para>
+ &CHAPTER;
+
+ &ANOTHER-CHAPTER;
+</part>
+</computeroutput>
+</screen>
+
+ <para>
+ If you create a part, include a part introduction describing the
+ contents of the part. For example:
+ </para>
+
+<screen>
+<computeroutput>
+ <part id="pt-setup">
+ <title>Getting Setup</title>
+ <partintro>
+ <para>This section contains information you will need when you first join
+ the Docs group. You might need to refer to this part again for
+ information such as installing &FC;.</para>
+ </partintro>
+</computeroutput>
+</screen>
+
+ <para>
+ In the HTML output, a separate HTML page is generated with the part
+ number, title, introduction, and TOC. In the PDF output, the same
+ information about the part is on a separate page.
+ </para>
+
+ </section>
+
+ <section id="sn-xml-tags-prompt">
+ <title><command>prompt</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>prompt</secondary>
+ </indexterm>
+
+ <para>
+ To show a prompt, such as a root or DOS prompt, use the
+ <command><prompt></command> and <command></prompt></command>
+ commands. For example:
+ </para>
+<screen>
+<computeroutput>
+At the <prompt>LILO:</prompt> boot prompt, type linux to
+boot into your Linux partition.
+
+At the <prompt>C:\></prompt> prompt, type ....
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ At the <prompt>LILO:</prompt> boot prompt, type linux to boot into your
+ Linux partition.
+ </para>
+ <para>
+ At the <prompt>C:\></prompt> prompt, type ....
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ When showing example computer output (usually in
+ <command>screen</command> tags), do not include the prompt or command
+ (unless the command or prompt is the actually computer output you want
+ to show).</para>
+ </note>
+ </section>
+
+ <section id="sn-xml-tags-replaceable">
+ <title><command>replaceable</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>replaceable</secondary>
+ </indexterm>
+
+ <para>
+ To create replaceable text, use the tags
+ <command><replaceable></command> and
+ <command></replaceable></command> around the text you want to use as a
+ variable.
+ </para>
+ <para>
+ This example demonstrates how to use the <command>replaceable</command>
+ tags when referencing the name of an RPM file:
+ </para>
+<screen>
+foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+<screen>
+foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm
+</screen>
+ </section>
+
+ <section id="sn-xml-tags-screen">
+ <title><command>screen</command></title>
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>screen</secondary>
+ </indexterm>
+
+ <para>
+ The <command><screen></command> command is used to format text
+ within a document and is great for adding emphasis to show examples of
+ code, computer output, and more. In HTML with the Fedora CSS file, this
+ appears in box with a grey background. To use this command you only need
+ the opening <command><screen></command> and closing
+ <command></screen></command> tags around the text you are
+ emphasizing.
+ </para>
+
+ <important>
+ <title>Important</title>
+ <para>
+ When using the <command><screen></command> tag, set
+ everything within that screen to flush left. The contents of
+ the <sgmltag class="starttag">screen</sgmltag> element are
+ rendered exactly as is, including any indentation. Using flush
+ left prevents extra blank space in front of the text inside the
+ gray background when the content is converted to HTML.
+ </para>
+ </important>
+
+ <para>
+ The <command><screen></command> tag set may contain other inline
+ tags, such as <command><computeroutput></command>,
+ <command><userinput></command>, or
+ <command><replaceable></command>. Additional inline tags are not
+ required by definition. The <command><screen></command> tags by
+ themselves may provide sufficient context, especially for simple examples
+ or file listings. Consider the context of the example, and use inline tags
+ if they are helpful to the reader.
+ </para>
+
+ <para>
+ If you use inline tags, remember that line breaks inside
+ <command><screen></command> tags create line breaks in any rendered
+ output. Place any inline tags <emphasis>on the same line</emphasis> as
+ their content. Do not overuse tagging within a
+ <command><screen></command> tag set.
+ </para>
+
+ <para>
+ An example of <command><screen></command> is the following:
+ </para>
+
+<screen>
+<computeroutput><screen>
+This is an example of a screen. You do not need &lt;para&gt; tags
+within this command.
+</screen></computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+<screen>
+This is an example of a screen. You do not need <para> tags
+within this command.
+</screen>
+
+ <section id="sn-xml-tags-screen-inline-tags">
+ <title>Using Inline Tags with <command>screen</command></title>
+ <para>
+ If you choose to use inline tags inside a
+ <command><screen></command> section, follow these guidelines for
+ consistency. If the content in the screen is a listing of a
+ configuration file or the output of a program, use the
+ <command><computeroutput></command> tag set around the entire
+ output. If the user should type the example on the command line or in
+ a configuration file, use the <command><userinput></command> tag
+ set. Separate input and output with a short sentence of narrative, as
+ below:
+ </para>
+
+<screen>
+ <command><para></command>
+ Type the following command:
+ <command></para></command>
+
+<command><screen></command>
+<command><userinput></command>command -sw file1<command></userinput></command>
+<command></screen></command>
+
+ <command><para></command>
+ You should see the following output:
+ <command></para></command>
+
+<command><screen></command>
+<command><computeroutput></command>Completed, time = 0.12 sec<command></computeroutput></command>
+<command></screen></command>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <para>
+ Type the following command:
+ </para>
+
+<screen>
+<userinput>command -sw file1</userinput>
+</screen>
+
+ <para>
+ You should see the following output:
+ </para>
+
+<screen>
+<computeroutput>Completed, time = 0.12 sec</computeroutput>
+</screen>
+
+ <note>
+ <title>Note</title>
+ <para>
+ When showing a command or series of commands inside
+ <command>screen</command> tags, do not show the prompt.
+ </para>
+ </note>
+
+ <para>
+ If the <command><screen></command> shows the reader how to
+ change only <emphasis>part</emphasis> of a line, mark the change with
+ an inline <command><userinput></command> tag set. You may use
+ the <command><userinput></command> tag set inside a larger area
+ that is already marked inline with
+ <command><computeroutput></command>. Do not include any extra
+ lines of context in this case, unless excluding them would confuse the
+ reader. The following example illustrates these guidelines:
+ </para>
+
+<screen>
+ <command><para></command>
+ Edit the <command><filename></command>/etc/sysconfig/init<command></filename></command> file as follows:
+ <command></para></command>
+
+<command><screen></command>
+GRAPHICAL=<command><userinput></command>yes<command></userinput></command>
+<command></screen></command>
+</screen>
+
+ <para>
+ The output looks like:
+ </para>
+
+ <para>
+ Edit the <filename>/etc/sysconfig/init</filename> file as follows:
+ </para>
+
+<screen>
+GRAPHICAL=<userinput>yes</userinput>
+</screen>
+
+ <para>
+ For an explanation of how to use the <command>replaceable</command>
+ tags within a set of <command>screen</command> tags, refer to <xref
+ linkend="sn-xml-tags-replaceable"></xref>.
+ </para>
+
+ </section>
+ </section>
+
+ <section id="sn-xml-tags-sections">
+ <title>Sections</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>sections</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>sections</primary>
+ </indexterm>
+
+ <para>Within an article (or chapter if it is a DocBook XML book like the
+ <citetitle>&IG;</citetitle>), you can have sections and
+ subsections. <command><section></command> is always the highest
+ section and you cannot have two sections of the same level within one
+ another (a section 2 can be created within a section 1, but section 1
+ has to be closed before another section 1 can be created). The general
+ layout follows:</para>
+
+<screen>
+<computeroutput>
+<section id="sn-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+
+ <section id="sn-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+ <sect3 id="s3-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+
+ </sect3>
+
+ </section>
+
+</section>
+</computeroutput>
+</screen>
+
+ <para>
+ If you only need one level of sections in a DocBook article, you can use
+ the <command>section</command> tag. For example:
+ </para>
+
+<screen>
+<computeroutput>
+<section id="sn-uniquename">
+ <title>Insert Title Here</title>
+ <para>
+ Body text goes here.
+ </para>
+</section>
+<section id="sn-anothername">
+ <title>Insert Title Here</title>
+ <para>
+ More body text goes here.
+ </para>
+</section>
+</computeroutput>
+</screen>
+ </section>
+
+ <section id="sn-xml-tags-table">
+ <title><command>table</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>table</secondary>
+ </indexterm>
+
+ <para>
+ The following is an example of creating a table.
+ </para>
+
+<screen>
+<table id="tb-mockup-before-begin">
+ <emphasis>This tells XML that you will be creating a table
+ and the ID name is <command>"tb-mockup-before-begin."</command></emphasis>
+
+<title>Available Features of GNOME and KDE</title>
+
+<tgroup cols="3">
+ <emphasis>This tells XML that you are creating a table
+ with three columns.</emphasis>
+
+<colspec colnum="1" colname="Features" colwidth="3"/>
+ <emphasis><command>colspec</command> says that you are giving information
+ about the column to XML</emphasis> <emphasis><command>colnum="1"</command>
+ says that you are giving specifications for the first column.</emphasis>
+
+ <emphasis><command>colname="Features"</command> says that the title for this
+ column will be "Features."</emphasis>
+
+ <emphasis><command>colwidth="3"</command> specifies the width of the
+ column. This can be more tricky: such as two columns with
+ widths of 1 and 2,the 1 is one-half the width of the 2, in
+ respect to the page size. But, what if you need the 1 to be a
+ little more than half of the 2, using a larger number ratio,
+ such as 10 to 20 would accomplish this. You could then change the
+ 10 to an 11 or a 12 to make it a little more than half of the
+ second column of 20. In no value is given, a value of 1 is
+ assumed.</emphasis>
+
+<colspec colnum="2" colname="GNOME" colwidth="2"/>
+<colspec colnum="3" colname="KDE" colwidth="2"/>
+
+<thead>
+ <emphasis>Contains one or more table row elements.</emphasis>
+
+<row>
+ <emphasis>Contains one or more table cell (entry) elements.</emphasis>
+
+<entry>Features</entry>
+ <emphasis>Table cell element, one of several in a row element, defining
+ columns within the row.</emphasis>
+
+<entry>GNOME</entry>
+<entry>KDE</entry>
+</row>
+</thead>
+
+<tbody>
+ <emphasis>Contains one or more row elements, for the main text
+ of the table.</emphasis>
+
+<row>
+<entry>highly configurable</entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>multiple window managers </entry>
+<entry>yes</entry>
+<entry>yes</entry>
+</row>
+<row>
+<entry>Internet applications</entry>
+<entry>yes </entry>
+<entry>yes </entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+</screen>
+
+ <table id="tb-mockup-before-begin">
+ <title>Available Features of GNOME and KDE</title>
+
+ <tgroup cols="3">
+ <colspec colnum="1" colname="Features" colwidth="3"/>
+ <colspec colnum="2" colname="GNOME" colwidth="2"/>
+ <colspec colnum="3" colname="KDE" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Features </entry>
+ <entry>GNOME</entry>
+ <entry>KDE</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry>highly configurable</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>multiple window managers </entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ </row>
+ <row>
+ <entry>Internet applications</entry>
+ <entry>yes </entry>
+ <entry>yes </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <section id="sn-xml-tags-listintable">
+ <title>Creating a List Within a Table</title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>table</secondary>
+ <tertiary>list within a table</tertiary>
+ </indexterm>
+
+
+ <para>Creating a list within a table can be a difficult task. It
+ requires strict formatting and a set of commands that are not
+ available for command completion in
+ <application>Emacs</application>.</para>
+
+ <para>The tags you will need to use are
+ <command><simplelist></command> and
+ <command><member></command>.</para>
+
+ <para>The following example will show you the proper formatting for
+ creating a list within a table.</para>
+
+
+<screen>
+<computeroutput>
+<table id="tb-hardware-powerswitch">
+ <title>Power Switch Hardware Table</title>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="Hardware" colwidth="2"/>
+ <colspec colnum="2" colname="Quantity" colwidth="2"/>
+ <colspec colnum="3" colname="Description" colwidth="6"/>
+ <colspec colnum="4" colname="Required" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>Description</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Serial power switches</entry>
+
+ <entry>Two</entry>
+
+ <entry><simplelist> <member>Power switches enable each cluster system
+ to power-cycle the other cluster system. Note that clusters are
+ configured with either serial or network attached power switches and
+ not both.</member>
+
+ <member>The following serial attached power switch has been
+ fully tested:</member>
+
+ <member>RPS-10 (model M/HD in the US, and model M/EC in
+ Europe) </member>
+
+ <member>Latent support is provided for the following serial
+ attached power switch. This switch has not yet been fully
+ tested:</member>
+
+ <member>APC Serial On/Off Switch (partAP9211), <ulink
+ url="http://www.apc.com/">http://www.apc.com/</ulink></member>
+ </simplelist></entry>
+
+ <entry>Strongly recommended for data integrity under all failure
+ conditions</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+</table>
+</computeroutput>
+</screen>
+
+ <para>Notice how the <command><simplelist></command> tag must be
+ beside the <command><entry></command> tag? If you do not format
+ this properly, it will not parse cleanly.</para>
+
+ <para>The above example will look like the following:</para>
+
+ <table id="tb-hardware-powerswitch">
+ <title>Power Switch Hardware Table</title>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="Hardware" colwidth="2"/>
+ <colspec colnum="2" colname="Quantity" colwidth="2"/>
+ <colspec colnum="3" colname="Description" colwidth="6"/>
+ <colspec colnum="4" colname="Required" colwidth="2"/>
+
+ <thead>
+ <row>
+ <entry>Hardware</entry>
+ <entry>Quantity</entry>
+ <entry>Description</entry>
+ <entry>Required</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>Serial power switches</entry>
+
+ <entry>Two</entry>
+
+ <entry><simplelist> <member>Power switches enable each cluster
+ system to power-cycle the other cluster system. Note
+ that clusters are configured with either serial or
+ network attached power switches and not both.</member>
+
+ <member>The following serial attached power switch has been
+ fully tested:</member>
+
+ <member>RPS-10 (model M/HD in the US, and model M/EC in
+ Europe) </member>
+
+ <member>Latent support is provided for the following
+ serial attached power switch. This switch has not yet
+ been fully tested:</member>
+
+ <member>APC Serial On/Off Switch (partAP9211), <ulink
+ url="http://www.apc.com/">http://www.apc.com/</ulink></member>
+ </simplelist></entry>
+
+ <entry>Strongly recommended for data integrity under all failure
+ conditions</entry>
+
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </section>
+
+ </section>
+
+ <section id="sn-xml-tags-trademark">
+ <title><command>trademark</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>trademark</command></secondary>
+ </indexterm>
+
+
+ <para>Do not use the trademark entities &trade;, &copy;, or
+ &reg; because the do not produce HTML output that works for all
+ charsets. The HTML output produces by these entities are declared in
+ the DTD and cannot be changed via the stylesheet.</para>
+
+ <para>Instead, use the <command>trademark</command> tag and its
+ associates classes as follows:
+ </para>
+
+<screen>
+<computeroutput>
+<trademark>trademark symbol after me</trademark>
+<trademark class="registered">registered trademark symbol after me</trademark>
+<trademark class="copyright">copyright symbol after me</trademark>
+</computeroutput>
+</screen>
+
+ </section>
+
+ <section id="sn-xml-tags-userinput">
+ <title><command>userinput</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary><command>userinput</command></secondary>
+ </indexterm>
+
+ <para>
+ To show what a user would type, use the <command>userinput</command>
+ tag. For example:
+ </para>
+<screen>
+<computeroutput>
+At the prompt, type:
+
+<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ At the prompt, type:
+ </para>
+
+ <para>
+ <userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>
+ </para>
+ </section>
+
+
+<!-- <section id="sn-xml-tags-mouse">
+ <title><command>mousebutton</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>mousebutton</secondary>
+ </indexterm>
+ <para>
+Describe mouse actions with the mousebutton tag. Below is an example of its use.
+</para>
+
+<screen>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+</screen>
+
+ <para>
+<mousebutton>Right click</mousebutton> on the image and a new menu will appear.
+ </para>
+
+ </section> -->
+
+ <section id="sn-xml-tag-sulink">
+ <title><command>ulink</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>ulink</secondary>
+ </indexterm>
+
+ <para>
+ To create a URL link within your text, use the following example:
+ </para>
+<screen>
+<computeroutput>
+Online &mdash; <ulink url="http://www.redhat.com/support/errata/">
+http://www.redhat.com/support/errata/</ulink>; supplies errata
+you can read online, and you can download diskette images easily.
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ Online — <ulink url="http://www.redhat.com/support/errata/">
+ http://www.redhat.com/support/errata/</ulink>; supplies errata
+ you can read online, and you can download diskette images easily.
+ </para>
+
+ <note>
+ <title>Note</title>
+ <para>
+ If the URL does not end in a filename, it must end in a slash
+ (<computeroutput>/</computeroutput>) to be a properly formed URL. For
+ example, <ulink
+ url="http://www.redhat.com/">http://www.redhat.com/</ulink>.
+ </para>
+ </note>
+
+ </section>
+
+ <section id="sn-xml-tags-wordasword">
+ <title><command>wordasword</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>wordasword</secondary>
+ </indexterm>
+
+ <para>The <wordasword> tag set is used to define a word meant
+ specifically as a word and not representing anything else.</para>
+
+ <para>A lot of technical documentation contains words that have overloaded
+ meanings. Sometimes it is useful to be able to use a word without invoking
+ its technical meaning. The <wordasword> element identifies a word or
+ phrase that might otherwise be interpreted in some specific way, and
+ asserts that it should be interpreted simply as a word.</para>
+
+ <para>It is unlikely that the presentation of this element will be able to
+ help readers understand the variation in meaning; good writing will have
+ to achieve that goal. The real value of <wordasword> lies in the
+ fact that full-text searching and indexing tools can use it to avoid
+ false-positives.</para>
+
+ <para>For example:</para>
+
+<screen>
+<computeroutput>To use <command>grep</command> to search for the word
+<wordasword>linux</wordasword>, use the command
+<command>grep linux</command>.</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>To use <command>grep</command> to search for the word
+ <wordasword>linux</wordasword>, use the command <command>grep
+ linux</command>.</para>
+
+ <para>In the example, the word "linux" is just a word. It is not
+ meant to convey anything about Linux as a subject, or to add relevance or
+ meaning to the content. It can be replaced with any other word without
+ losing any of the context.</para>
+
+ </section>
+
+
+ <section id="sn-xml-tags-xref">
+ <title><command>xref</command></title>
+
+ <indexterm>
+ <primary>XML tags</primary>
+ <secondary>xref</secondary>
+ </indexterm>
+
+ <para>
+ To refer to other sections or chapters within a manual, use the
+ <command><xref></command> tag.
+ </para>
+
+ <para>
+ The output of this displays the title of the section or chapter you are
+ pointing the user to. For example:
+ </para>
+<screen>
+<computeroutput>
+For more information about the parent file, refer to
+<xref linkend="ch-tutorial"></xref> and <xref linkend="sn-tutorial-article"></xref>
+</computeroutput>
+</screen>
+
+ <para>
+ The output:
+ </para>
+
+ <para>
+ For more information about the parent file, refer to <xref linkend="ch-tutorial"></xref>
+ and <xref linkend="sn-tutorial-article"></xref>.
+ </para>
+ </section>
+
+ </chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+@
+
+
+1.5
+log
+ at Some more tag corrections. I know we may be losing part of these
+sections, but just in case we retain any of these we should at least
+have them properly tagged.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: xml-tags.xml,v 1.4 2007/02/04 14:46:04 pfrields Exp $ -->
+d215 1
+a215 1
+<!--$Id: xml-tags.xml,v 1.4 2007/02/04 14:46:04 pfrields Exp $ -->
+d2500 1
+a2500 1
+<xref linkend="ch-tutorial"></xref> and <xref linkend="sn-tutorial-parent"></xref>
+d2510 1
+a2510 1
+ and <xref linkend="sn-tutorial-parent"></xref>.
+@
+
+
+1.4
+log
+ at Start correcting tagging to reflect sgmltag instead of command for all
+tags, elements, etc.
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: xml-tags.xml,v 1.3 2007/02/04 13:42:58 pfrields Exp $ -->
+d215 1
+a215 1
+<!--$Id: xml-tags.xml,v 1.3 2007/02/04 13:42:58 pfrields Exp $ -->
+d229 3
+a231 3
+ (<command>section</command>, <command>section</command>,
+ <command>sect3</command>, etc.). Refer to <xref
+ linkend="sn-xml-tags-sections"></xref> for details.
+d238 1
+a238 1
+ <title><command>citetitle</command></title>
+d247 1
+a247 1
+ The <command><citetitle></command> tag provides formatting for a
+d250 2
+a251 1
+ entity is a short hand way of referring to another manual or guide. It
+d262 1
+a262 1
+<citetitle>IG;</citetitle>.
+d266 2
+a267 2
+ The output looks like <citetitle>&IG;</citetitle> because &IG; is an
+ entity.
+d273 1
+a273 1
+ <title><command>command</command></title>
+d283 1
+a283 1
+ <command>command</command> tags. </para>
+d287 2
+a288 2
+ <command><command></command> and
+ <command></command></command> tags such as:
+@
+
+
+1.3
+log
+ at Remove unnecessary screen section
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: xml-tags.xml,v 1.2 2007/02/03 22:29:37 kwade Exp $ -->
+d66 1
+a66 1
+ so that both the HTML and PDF outputs look proper.
+d73 8
+a80 5
+ <para>Do not use the trademark entities &trade;, &copy;, or
+ &reg; because the do not produce HTML output that works for all
+ charsets. The HTML output produces by these entities are declared in
+ the DTD and cannot be changed via the stylesheet.</para>
+ <para>Instead, use the <command>trademark</command> tag and its
+d85 3
+a87 1
+ <para><trademark>trademark symbol after me</trademark>
+d91 3
+a93 1
+ <para><trademark class="registered">registered trademark symbol after me</trademark>
+d97 3
+a99 1
+ <para><trademark class="copyright">copyright symbol after me</trademark></para>
+d105 1
+a105 1
+ <term>Content inside <command>para</command> tags</term>
+d107 4
+a110 3
+ <para>Do not use <command>para</command> tags around anything other
+ than a simple paragraph. Doing so will create additional white space
+ within the text itself in the PDF version.
+d112 3
+a114 3
+ <para>Specifically, do not use <command>para</command> tags around
+ the following (or, to put this another way, do not embed the
+ following within <command>para</command> tags):
+d118 1
+a118 1
+ <para><screen></para>
+d121 1
+a121 1
+ <para><itemizedlist></para>
+d124 1
+a124 1
+ <para><orderedlist></para>
+d127 1
+a127 1
+ <para><variablelist></para>
+d130 1
+a130 1
+ <para><table></para>
+d136 2
+a137 2
+ <term>Content inside <command>para</command> tags within
+ <command>listitem</command> tags</term>
+d139 5
+a143 4
+ <para>Content inside <command>para</command> tags within
+ <command>listitem</command> tags <emphasis>must</emphasis> start
+ immediately after the beginning <para> tag to avoid extra
+ white space in the PDF version.
+d148 1
+a148 1
+ <term>Content inside <command>screen</command> tags</term>
+d150 3
+a152 2
+ <para>The content inside <command>screen</command> tags
+ (<screen> and </screen>)
+d164 1
+a164 1
+ <title><command>application</command></title>
+d174 2
+a175 2
+ <para>The <command><application></command> and
+ <command></application></command> tags allow you to refer to an
+d182 5
+a186 3
+<application>Mozilla</application> or
+<application>lynx</application> if you only want a text-based
+browser.
+d202 1
+a202 1
+ <title><command>chapter</command></title>
+d210 1
+a210 1
+ A DocBook book can be divided into chapters such as:
+d215 1
+a215 1
+<!--$Id: xml-tags.xml,v 1.2 2007/02/03 22:29:37 kwade Exp $ -->
+@
+
+
+1.2
+log
+ at updating all section usage and associated ID tags
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: xml-tags.xml,v 1.1 2007/02/03 22:21:58 kwade Exp $ -->
+d48 6
+a53 9
+ <para>
+ This chapter only discusses tags used for documentation for the &PROJECT;,
+ not all available DocBook XML tags. For the complete list, refer to:
+ </para>
+<screen>
+<computeroutput>
+<ulink url="http://www.docbook.org/tdg/en/html/docbook.html">http://www.docbook.org/tdg/en/html/docbook.html</ulink>
+</computeroutput>
+</screen>
+d201 1
+a201 1
+<!--$Id: xml-tags.xml,v 1.1 2007/02/03 22:21:58 kwade Exp $ -->
+@
+
+
+1.1
+log
+ at renaming rh-guidelines to writing-guidelines
+@
+text
+ at d1 1
+a1 1
+<!-- $Id: docs-xml-tags.xml,v 1.3 2006/12/23 23:49:59 pfrields Exp $ -->
+d58 1
+a58 1
+ <sect1 id="s1-xml-tags-caveats">
+d152 1
+a152 1
+ </sect1>
+d154 1
+a154 1
+ <sect1 id="s1-xml-tags-application">
+d188 1
+a188 1
+ </sect1>
+d190 1
+a190 1
+ <sect1 id="s1-xml-tags-chapter">
+d204 1
+a204 1
+<!--$Id: docs-xml-tags.xml,v 1.3 2006/12/23 23:49:59 pfrields Exp $ -->
+d218 1
+a218 1
+ (<command>sect1</command>, <command>sect2</command>,
+d220 1
+a220 1
+ linkend="s1-xml-tags-sections"></xref> for details.
+d223 1
+a223 1
+ </sect1>
+d226 1
+a226 1
+ <sect1 id="s1-xml-tags-citetitle">
+d258 1
+a258 1
+ </sect1>
+d260 1
+a260 1
+ <sect1 id="s1-xml-tags-command">
+d343 1
+a343 1
+ </sect1>
+d345 1
+a345 1
+ <sect1 id="s1-xml-tags-compoutput">
+d368 1
+a368 1
+ </sect1>
+d370 1
+a370 1
+ <sect1 id="s1-xml-tags-emphasis">
+d399 1
+a399 1
+ </sect1>
+d401 1
+a401 1
+ <sect1 id="s1-xml-tags-example">
+d452 1
+a452 1
+ </sect1>
+d455 1
+a455 1
+ <sect1 id="s1-xml-tags-filename">
+d505 1
+a505 1
+ </sect1>
+d507 1
+a507 1
+ <sect1 id="s1-xml-tags-firstterm">
+d537 1
+a537 1
+ </sect1>
+d539 1
+a539 1
+ <sect1 id="s1-xml-tags-footnote">
+d575 1
+a575 1
+ </sect1>
+d577 1
+a577 1
+ <sect1 id="s1-xml-tags-figure">
+d638 1
+a638 1
+ linkend="s1-screenshots"/>.
+d641 1
+a641 1
+ </sect1>
+d643 1
+a643 1
+ <sect1 id="s1-xml-tags-gui">
+d651 1
+a651 1
+ <sect2 id="s2-xml-tags-guilabel">
+d685 1
+a685 1
+ </sect2>
+d687 1
+a687 1
+ <sect2 id="s2-xml-tags-guibutton">
+d721 1
+a721 1
+ </sect2>
+d723 1
+a723 1
+ <sect2 id="s2-xml-tags-guiicon">
+d755 1
+a755 1
+ </sect2>
+d757 1
+a757 1
+ <sect2 id="s2-xml-tags-guimenu">
+d814 2
+a815 2
+ </sect2>
+ </sect1>
+d817 1
+a817 1
+ <sect1 id="s1-xml-tags-keycap">
+d845 1
+a845 1
+ <sect2 id="s2-xml-tags-menuchoice">
+d890 1
+a890 1
+ </sect2>
+d892 1
+a892 1
+ <sect2 id="s2-xml-tags-keycombo">
+d925 1
+a925 1
+ </sect2>
+d927 1
+a927 1
+ </sect1>
+d929 1
+a929 1
+ <sect1 id="s1-xml-tags-lists">
+d947 1
+a947 1
+ <sect2 id="s2-xml-tags-itemizedlist">
+d1019 1
+a1019 1
+ </sect2>
+d1021 1
+a1021 1
+ <sect2 id="s2-xml-tags-orderedlist">
+d1106 1
+a1106 1
+ </sect2>
+d1108 1
+a1108 1
+ <sect2 id="s2-xml-tags-varlist">
+d1201 1
+a1201 1
+ </sect2>
+d1203 1
+a1203 1
+ <sect2 id="s2-xml-tags-simplelist">
+d1384 1
+a1384 1
+ </sect2>
+d1386 1
+a1386 1
+ <sect2 id="s2-xml-tags-glossary">
+d1470 2
+a1471 2
+ </sect2>
+ </sect1>
+d1474 1
+a1474 1
+ <sect1 id="s1-xml-tags-option">
+d1510 1
+a1510 1
+ </sect1>
+d1512 1
+a1512 1
+ <sect1 id="s1-xml-tags-indexing">
+d1623 1
+a1623 1
+ </sect1>
+d1625 1
+a1625 1
+ <sect1 id="s1-xml-tags-para">
+d1665 1
+a1665 1
+ </sect1>
+d1667 1
+a1667 1
+ <sect1 id="s1-xml-tags-part">
+d1720 1
+a1720 1
+ </sect1>
+d1722 1
+a1722 1
+ <sect1 id="s1-xml-tags-prompt">
+d1764 1
+a1764 1
+ </sect1>
+d1766 1
+a1766 1
+ <sect1 id="s1-xml-tags-replaceable">
+d1795 1
+a1795 1
+ </sect1>
+d1797 1
+a1797 1
+ <sect1 id="s1-xml-tags-screen">
+d1865 1
+a1865 1
+ <sect2 id="s2-xml-tags-screen-inline-tags">
+d1961 1
+a1961 1
+ linkend="s1-xml-tags-replaceable"></xref>.
+d1964 2
+a1965 2
+ </sect2>
+ </sect1>
+d1967 1
+a1967 1
+ <sect1 id="s1-xml-tags-sections">
+d1981 1
+a1981 1
+ subsections. <command><sect1></command> is always the highest
+d1989 1
+a1989 1
+<sect1 id="s1-uniquename">
+d1996 1
+a1996 1
+ <sect2 id="s2-uniquename">
+d2010 1
+a2010 1
+ </sect2>
+d2012 1
+a2012 1
+</sect1>
+d2037 1
+a2037 1
+ </sect1>
+d2039 1
+a2039 1
+ <sect1 id="s1-xml-tags-table">
+d2158 1
+a2158 1
+ <sect2 id="s2-xml-tags-listintable">
+d2293 1
+a2293 1
+ </sect2>
+d2295 1
+a2295 1
+ </sect1>
+d2297 1
+a2297 1
+ <sect1 id="s1-xml-tags-trademark">
+d2323 1
+a2323 1
+ </sect1>
+d2325 1
+a2325 1
+ <sect1 id="s1-xml-tags-userinput">
+d2356 1
+a2356 1
+ </sect1>
+d2359 1
+a2359 1
+<!-- <sect1 id="s1-xml-tags-mouse">
+d2378 1
+a2378 1
+ </sect1> -->
+d2380 1
+a2380 1
+ <sect1 id="s1-xml-tag-sulink">
+d2419 1
+a2419 1
+ </sect1>
+d2421 1
+a2421 1
+ <sect1 id="s1-xml-tags-wordasword">
+d2465 1
+a2465 1
+ </sect1>
+d2468 1
+a2468 1
+ <sect1 id="s1-xml-tags-xref">
+d2488 1
+a2488 1
+<xref linkend="ch-tutorial"></xref> and <xref linkend="s1-tutorial-parent"></xref>
+d2498 1
+a2498 1
+ and <xref linkend="s1-tutorial-parent"></xref>.
+d2500 1
+a2500 1
+ </sect1>
+@
+
diff --git a/old-documentation-guide/po/LINGUAS,v b/old-documentation-guide/po/LINGUAS,v
new file mode 100644
index 0000000..9d09168
--- /dev/null
+++ b/old-documentation-guide/po/LINGUAS,v
@@ -0,0 +1,60 @@
+head 1.3;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.2;
+locks; strict;
+comment @# @;
+
+
+1.3
+date 2007.12.22.16.10.43; author szaman; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.08.10.18.34.11; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.07.28.22.01.03; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.3
+log
+ at Added new file and updated Malay translation
+@
+text
+@# Add languages in alphabetical order.
+ms
+pt
+pt_BR
+zh_CN
+@
+
+
+1.2
+log
+ at Remove dummy comment
+@
+text
+ at d2 1
+@
+
+
+1.1
+log
+ at Convert DocGuide to use po/LINGUAS instead of Makefile $OTHERS
+@
+text
+ at d2 1
+a2 1
+pt # try this!
+@
+
diff --git a/old-documentation-guide/po/de.po,v b/old-documentation-guide/po/de.po,v
new file mode 100755
index 0000000..a650987
--- /dev/null
+++ b/old-documentation-guide/po/de.po,v
@@ -0,0 +1,7971 @@
+head 1.5;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.5;
+locks; strict;
+comment @# @;
+
+
+1.5
+date 2007.10.21.12.02.25; author fab; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.08.16.09.13.12; author petreu; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.08.15.09.34.11; author petreu; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.08.04.11.20.20; author fab; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.08.02.16.57.34; author fab; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.5
+log
+ at some strings done
+@
+text
+@# translation of de.po to German
+#
+# Fabian Affolter <fab@@fedoraproject.org>, 2007.
+# Peter Reuschlein <petreu@@fedoraproject.org>, 2007.
+msgid ""
+msgstr ""
+"Project-Id-Version: de\n"
+"POT-Creation-Date: 2007-07-28 18:10-0400\n"
+"PO-Revision-Date: 2007-10-21 14:01+0100\n"
+"Last-Translator: Fabian Affolter <fab@@fedoraproject.org>\n"
+"Language-Team: German <fedora-trans-de@@redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Poedit-Language: German\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#: en_US/rpm-info.xml:22(rights)
+msgid "OPL"
+msgstr "OPL"
+
+#: en_US/rpm-info.xml:23(version)
+msgid "1.0"
+msgstr "1.0"
+
+#: en_US/rpm-info.xml:26(year)
+msgid "2003"
+msgstr "2003"
+
+#: en_US/rpm-info.xml:27(year)
+msgid "2004"
+msgstr "2004"
+
+#: en_US/rpm-info.xml:28(year)
+msgid "2005"
+msgstr "2005"
+
+#: en_US/rpm-info.xml:29(year)
+msgid "2006"
+msgstr "2006"
+
+#: en_US/rpm-info.xml:30(year)
+msgid "2007"
+msgstr "2007"
+
+#: en_US/rpm-info.xml:31(holder)
+msgid "Red Hat, Inc. and others"
+msgstr "Red Hat, Inc. und andere"
+
+#: en_US/rpm-info.xml:33(title)
+msgid "Fedora Documentation Guide"
+msgstr "Fedora Dokumentations-Anleitung"
+
+#: en_US/rpm-info.xml:34(desc)
+msgid "Guidelines and procedures for producing documentation for Fedora"
+msgstr "Richtlinien und Wege um Dokumentationen für Fedora zu erstellen."
+
+#: en_US/rpm-info.xml:38(details)
+msgid "Add new chapter on publishing"
+msgstr "Ein neues Kapitel bei Veröffentlichungen hinzufügen"
+
+#: en_US/rpm-info.xml:42(details)
+msgid "Include information on LINGUAS usage"
+msgstr "Inklusive Informationen zur LINGUAS Benutzung"
+
+#: en_US/rpm-info.xml:46(details)
+msgid "Remove unnecessary chapter on XML tags"
+msgstr "Entferne unnötige Kapitel in den XML Tags"
+
+#: en_US/rpm-info.xml:50(details)
+msgid "Assorted fixes to reflect newer version of reality"
+msgstr "Assortierte Korrekturen zum Wiederspiegeln der neuen Version der Realität"
+
+#: en_US/rpm-info.xml:57(details)
+msgid "Update to new content and build requirements"
+msgstr "Auf neue Inhalts- und Build-Voraussetzungen aktualisieren."
+
+#: en_US/publishing.xml:11(title)
+msgid "Publishing Official Documentation"
+msgstr "Veröffentlichen der offiziellen Dokumentation"
+
+#: en_US/publishing.xml:12(para)
+msgid "This chapter shows how to publish official Fedora Documentation Project work to the <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> website. To publish official documentation, you must be approved to write to the web repository in CVS. Access for publishing is limited to contributors who have demonstrated capacity for working with CVS and other project tools. Once you have acquired and are comfortable with these skills, contributions as a publisher are welcome."
+msgstr ""
+
+#: en_US/publishing.xml:21(title)
+msgid "How the Site Works"
+msgstr "Wie die Seite arbeitet"
+
+#: en_US/publishing.xml:22(para)
+msgid "The <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> website is a set of PHP files and scripts. Publishers maintain these files in a CVS repository, and the website host retrieves them hourly to refresh the site. The host does not automatically use the newest content for the website. Instead, it pulls files with the CVS tag <systemitem>LIVE</systemitem> to populate the website."
+msgstr ""
+
+#: en_US/publishing.xml:30(para)
+msgid "Each publisher sets up a local testing website on an available Fedora system. This site, sometimes called a <firstterm>sandbox</firstterm>, allows the publisher to test and view changes to documents, and ensure stability on the public site."
+msgstr ""
+
+#: en_US/publishing.xml:37(title)
+msgid "Setting Up a Web Sandbox"
+msgstr "Einrichten eines Web-Sandkastens"
+
+#: en_US/publishing.xml:38(para)
+msgid "To test document publishing, first set up a web sandbox on a local Fedora system."
+msgstr ""
+
+#: en_US/publishing.xml:42(para)
+msgid "Install the \"Web Server\" package group:"
+msgstr "Installieren der \"Web Server\" Paketgruppe:"
+
+#: en_US/publishing.xml:43(screen)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Web Server\"'"
+msgstr "su -c 'yum groupinstall \"Web Server\"'"
+
+#: en_US/publishing.xml:46(para)
+msgid "Create a folder for the web server to access the site files."
+msgstr "Erzeuge ein Verzeichnis für den Web-Server zum Zugriff auf die Seiten-Dateien."
+
+#: en_US/publishing.xml:48(screen)
+#, no-wrap
+msgid "su -c 'mkdir /var/www/fedora'"
+msgstr "su -c 'mkdir /var/www/fedora'"
+
+#: en_US/publishing.xml:51(para)
+msgid "Change the permissions on this directory to make it easier to access for your normal user account."
+msgstr "Ändern Sie die Berechtigung dieses Verzeichnises, um dem Zugriff für normale Benutzer zu Vereinfachen."
+
+#: en_US/publishing.xml:53(replaceable)
+#: en_US/publishing.xml:62(replaceable)
+msgid "username"
+msgstr "Benutzername"
+
+#: en_US/publishing.xml:53(screen)
+#, no-wrap
+msgid "su -c 'chown <placeholder-1/> /var/www/fedora'"
+msgstr "su -c 'chown <placeholder-1/> /var/www/fedora'"
+
+#: en_US/publishing.xml:56(para)
+msgid "Link to the new directory from your home directory."
+msgstr "Verknüpfen Sie das neue Verzeichnis von Ihrem Home-Verzeichnis."
+
+#: en_US/publishing.xml:57(screen)
+#, no-wrap
+msgid "ln -s /var/www/fedora ~/fedora"
+msgstr "Name des Zielordners (z. B. /var/www)"
+
+#: en_US/publishing.xml:60(para)
+msgid "Retrieve the web module from CVS."
+msgstr "Beziehe das web Modul vom CVS."
+
+#: en_US/publishing.xml:61(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora\n"
+"cvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+msgstr ""
+"cd ~/fedora\n"
+"cvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+
+#: en_US/publishing.xml:65(para)
+msgid "Edit the <filename>/etc/hosts</filename> file and add the following line <emphasis>after</emphasis> all other lines:"
+msgstr "Ändern sie die <filename>/etc/hosts</filename> Datei und fügen sie folgende Zeile <emphasis>after</emphasis> nach allen anderen Zeilen ein:"
+
+#: en_US/publishing.xml:68(screen)
+#, no-wrap
+msgid "127.0.0.1 docs.localhost.localdomain"
+msgstr "127.0.0.1 docs.localhost.localdomain"
+
+#: en_US/publishing.xml:71(para)
+msgid "Create a file <filename>/etc/httpd/conf.d/fpo.conf</filename> with the following content:"
+msgstr "Erstellen Sie die Datei <filename>/etc/httpd/conf.d/fpo.conf</filename> mit folgendem Inhalt:"
+
+#: en_US/publishing.xml:85(para)
+msgid "Create a file <filename>/etc/php.d/fpo.ini</filename> with the following content:"
+msgstr "Errstellen sie die Datei <filename>/etc/php.d/fpo.ini</filename> mit folgendem Inhalt:"
+
+#: en_US/publishing.xml:87(screen)
+#, no-wrap
+msgid "include_path = \".:/var/www/fedora/web/include\""
+msgstr "include_path = \".:/var/www/fedora/web/include\""
+
+#: en_US/publishing.xml:90(para)
+msgid "Start the web server using the following command:"
+msgstr "Starten Sie den Web-Server mit dem folgenden Befehl:"
+
+#: en_US/publishing.xml:91(screen)
+#, no-wrap
+msgid "su -c '/sbin/service httpd start'"
+msgstr "su·-c·'/sbin/service·syslog·restart'"
+
+#: en_US/publishing.xml:92(para)
+msgid "To have the web server start at every boot, use the following command:"
+msgstr "Um den Web-Server bei jedem Systemstart zu starten, benutzen Sie folgenden Befehl:"
+
+#: en_US/publishing.xml:94(screen)
+#, no-wrap
+msgid "su -c '/sbin/chkconfig httpd on'"
+msgstr "su -c '/sbin/chkconfig httpd on'"
+
+#: en_US/publishing.xml:97(para)
+msgid "To test the new sandbox site, open a Web browser and point it at the URL <uri>http://docs.localhost.localdomain</uri>."
+msgstr "Um die neue Sandbox Seite zu testen, öffnen Sie einen Web-Browser mit der URL <uri>http://docs.localhost.localdomain</uri>."
+
+#: en_US/publishing.xml:101(title)
+msgid "Creating a New Publication"
+msgstr "Erzeugen einer neuen Publikation"
+
+#: en_US/publishing.xml:103(title)
+msgid "General Guidelines"
+msgstr "Allgemeine Richtlinien"
+
+#: en_US/publishing.xml:104(para)
+msgid "Follow these guidelines to ensure maintainability and ease of use for all publishers."
+msgstr "Folgen Sie diesen Richtlinien um die Wartbarkeit und einfache Benutzung für alle Herausgeber zu gewährleisten."
+
+#: en_US/publishing.xml:108(para)
+msgid "Use a short, descriptive name for the document directory. The module name from its Docs CVS location is usually appropriate. Good examples include <filename class=\"directory\">install-guide/</filename> or <filename class=\"directory\">example-tutorial/</filename>."
+msgstr ""
+
+#: en_US/publishing.xml:115(para)
+msgid "Under the document directory, include a branch directory if the document references specific features of a particular Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:120(para)
+msgid "Under the branch directory (or document directory if no branches are necessary), make at least a <filename class=\"directory\">en_US/</filename> directory. Make an additional directory for each locale that has been fully translated."
+msgstr ""
+
+#: en_US/publishing.xml:129(title)
+msgid "Adding Content"
+msgstr "Inhalt hinzufügen"
+
+#: en_US/publishing.xml:130(para)
+msgid "To add content, follow the procedure below. The following commands show an example of adding content for a new document called the <citetitle>Foobar Tutorial</citetitle>. This document includes a translation for the \"zz_XX\" locale and follows specifics of each Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:137(para)
+msgid "Make the required directory structure."
+msgstr "Erzeuge die benötigte Ordnerstruktur."
+
+#: en_US/publishing.xml:138(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"mkdir foobar-tutorial\n"
+"mkdir foobar-tutorial/f7\n"
+"mkdir foobar-tutorial/f7/{en_US,zz_XX}"
+msgstr ""
+"cd ~/fedora/web/html/docs/\n"
+"mkdir foobar-tutorial\n"
+"mkdir foobar-tutorial/f7\n"
+"mkdir foobar-tutorial/f7/{en_US,zz_XX}"
+
+#: en_US/publishing.xml:144(para)
+msgid "Build the HTML version of each translation of the document from Docs CVS."
+msgstr ""
+
+#: en_US/publishing.xml:146(replaceable)
+msgid "~/my-docs/foobar-tutorial/F-7/"
+msgstr "~/my-docs/foobar-tutorial/F-7/"
+
+#: en_US/publishing.xml:146(screen)
+#, no-wrap
+msgid ""
+"cd <placeholder-1/>\n"
+"make html-en_US html-zz_XX"
+msgstr ""
+"cd <placeholder-1/>\n"
+"make html-en_US html-zz_XX"
+
+#: en_US/publishing.xml:150(para)
+msgid "Copy the HTML content to the web sandbox."
+msgstr "Kopieren sie den HTML Inhalt in die Web Sandbox."
+
+#: en_US/publishing.xml:151(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/foobar-tutorial/f7/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/"
+msgstr ""
+"cd ~/fedora/web/html/docs/foobar-tutorial/f7/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/"
+
+#: en_US/publishing.xml:156(para)
+#, fuzzy
+msgid "Convert the HTML in each directory to PHP using the provided <filename>docbookhtml2php.py</filename> script."
+msgstr "Konvertieren sie mit dem <filename>docbookhtml2php.py</filename> Script das HTML in jedem Verzeichnis in PHP."
+
+#: en_US/publishing.xml:165(para)
+msgid "Create any necessary <filename>index.php</filename> files for the overall directories. Each document and branch directory must have an <filename>index.php</filename> file directing users to appropriate content. In this example, the necessary files are <filename>foobar-tutorial/index.php</filename> and <filename>foobar-tutorial/f7/index.php</filename>. You do not need to write these files from scratch. Copy an existing file from another document, and change it as needed to suit the new document."
+msgstr ""
+
+#: en_US/publishing.xml:175(para)
+msgid "Depending on content, publication may include changing a higher-level <filename>index.php</filename> file."
+msgstr ""
+
+#: en_US/publishing.xml:179(para)
+msgid "To test the changes in your sandbox, open a web browser and point it at <uri>http://docs.localhost.localdomain/</uri>."
+msgstr ""
+
+#: en_US/publishing.xml:183(title)
+msgid "Always Test Changes"
+msgstr "Prüfe Änderungen immer"
+
+#: en_US/publishing.xml:184(para)
+msgid "<emphasis>Do not proceed further until you test all changes.</emphasis> Check that all links and index pages work."
+msgstr ""
+
+#: en_US/publishing.xml:192(title)
+msgid "Pushing Content to the Web"
+msgstr "Den Inhalt im Web eröffentlichen"
+
+#: en_US/publishing.xml:193(para)
+#, fuzzy
+msgid "To push your new content to the web site, follow this procedure:"
+msgstr "Um ihren neuen Inhalt auf die Webseite zu bringen folgen Sie dieser Prozedur:"
+
+#: en_US/publishing.xml:197(para)
+msgid "Add all the new file content to CVS."
+msgstr "Füge alle neuen Dateien zum CVS hinzu."
+
+#: en_US/publishing.xml:198(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"cvs add foobar-tutorial\n"
+"cd foobar-tutorial\n"
+"cvs add f7\n"
+"cd f7\n"
+"cvs add en_US/ zz_XX/\n"
+"cvs add en_US/*php en_US/stylesheet-images/\n"
+"cvs add zz_XX/*php zz_XX/stylesheet-images/\n"
+"cvs add en_US/stylesheet-images/*png\n"
+"cvs add zz_XX/stylesheet-images/*png\n"
+"cd ../../\n"
+"cvs add foobar-tutorial/index.php\n"
+"cvs add foobar-tutorial/f7/index.php\n"
+msgstr ""
+"cd ~/fedora/web/html/docs/\n"
+"cvs add foobar-tutorial\n"
+"cd foobar-tutorial\n"
+"cvs add f7\n"
+"cd f7\n"
+"cvs add en_US/ zz_XX/\n"
+"cvs add en_US/*php en_US/stylesheet-images/\n"
+"cvs add zz_XX/*php zz_XX/stylesheet-images/\n"
+"cvs add en_US/stylesheet-images/*png\n"
+"cvs add zz_XX/stylesheet-images/*png\n"
+"cd ../../\n"
+"cvs add foobar-tutorial/index.php\n"
+"cvs add foobar-tutorial/f7/index.php\n"
+
+#: en_US/publishing.xml:214(para)
+#, fuzzy
+msgid "Commit the changes to CVS. Use a message that describes the document being committed."
+msgstr "Committen sie die Änderungen in das CVS. Benutzen sie dabei eine Nachricht die das Dokument welches Sie committet haben beschreibt."
+
+#: en_US/publishing.xml:216(replaceable)
+msgid "message about document"
+msgstr "Mitteilung über dieses Dokument"
+
+#: en_US/publishing.xml:216(screen)
+#, no-wrap
+msgid "cvs ci -m '<placeholder-1/>' foobar-tutorial/"
+msgstr "cvs ci -m '<placeholder-1/>' foobar-tutorial/"
+
+#: en_US/publishing.xml:219(para)
+msgid "Tag the content <systemitem>LIVE</systemitem> in CVS."
+msgstr "Markiere den Inhalt als <systemitem>LIVE</systemitem> im CVS."
+
+#: en_US/publishing.xml:221(screen)
+#, no-wrap
+msgid "cvs tag -F LIVE foobar-tutorial/"
+msgstr "cvs tag -F LIVE foobar-tutorial/"
+
+#: en_US/vim.xml:13(title)
+msgid "VIM and DocBook"
+msgstr "VIM und DocBook"
+
+#: en_US/vim.xml:16(primary)
+#: en_US/vim.xml:33(primary)
+msgid "VIM"
+msgstr "VIM"
+
+#: en_US/vim.xml:19(para)
+msgid "VIM has many features to help you write XML content such as DocBook, including syntax highlighting and customizable key bindings. Additionally, one can easily use external programs from VIM for features such as spell-checking. This chapter assumes you already know generally how to use VIM; if you want to learn how, try the <command>vimtutor</command> or by typing <userinput>:help tutor</userinput> from inside VIM."
+msgstr "VIM hat viele Eigenschaften, welche Ihnen helfen XML Inhalt wie DocBook zu schreiben, inklusive Syntax Highlighting und benutzerdefinierte Tastatur-Belegungen. Zusätzlich können sehr einfach von VIM aus externe Programme benutzt werden für die Rechschreibe-Kontrolle. Dieses Kapitel stetzt voraus, dass Sie mit den Grundlagen von VIM vertraut sind. Wenn Sie lernen wollen, benutzen Sie <command>vimtutor</command> oder geben Sie <userinput>:help tutor</userinput> innerhalb von VIM ein."
+
+#: en_US/vim.xml:30(title)
+msgid "Setting Up Your <filename>.vimrc</filename> File"
+msgstr "Konfigurieren Sie die <filename>.vimrc</filename> Datei"
+
+#: en_US/vim.xml:34(secondary)
+#: en_US/emacs.xml:44(secondary)
+msgid "configuration file"
+msgstr "Konfigurationsdatei"
+
+#: en_US/vim.xml:37(para)
+msgid ""
+"Below is a short sample <filename>.vimrc</filename> file that turns on some VIM features useful for editing SGML or XML content such as DocBook: <screen>\n"
+"<computeroutput>\" Turn off vi compatibility settings like limited undo\n"
+"set nocompatible\n"
+"\" Syntax highlighting based on file extension\n"
+"syntax on\n"
+"\" Automatically insert newlines after 80 characters\n"
+"set textwidth=80\n"
+"\" Automatically indent\n"
+"set autoindent\n"
+"\" Match SGML tags with %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+msgstr ""
+
+#: en_US/vim.xml:55(para)
+msgid "Some of these features require the <filename>vim-enhanced</filename> package to be installed. If you are using or the <filename>vim-minimal</filename> package, or if you are using an older version of VIM, you may not have the <filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still download <ulink url=\"http://vim.org/scripts/script.php?script_id=39\">matchit.zip from Vim.org</ulink> and load it separately."
+msgstr ""
+
+#: en_US/vim.xml:69(title)
+msgid "Keymapping with VIM"
+msgstr "Tastaturmapping mit VIM"
+
+#: en_US/vim.xml:71(para)
+msgid ""
+"VIM can speed up your DocBook creation by mapping frequently typed tags (or any words or phrases) onto short key combinations. By default, the keymap leader is the backslash (<literal>\\</literal>), but it can be redefined with a command like <userinput>let mapleader =\n"
+" \",\"</userinput>. There are two ways to use the following example; you can put it directly in your <filename>.vimrc</filename>, or you can save it in a separate file and load it with a <userinput>source</userinput> command in your <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\n"
+"\" skip ahead to after next tag without leaving insert mode\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\n"
+"\" common tags that start a new text block\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\n"
+"\" common tags that are placed inline\n"
+"\" use <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></command><esc>F>a \n"
+"\" entities\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+msgstr ""
+
+#: en_US/vim.xml:110(para)
+msgid "Unfortunately, there is not currently a complete macro set for all DocBook commands, so you will need to define them yourself or customize the definitions in the examples from <xref linkend=\"sn-vim-additional-resources\"/>."
+msgstr ""
+
+#: en_US/vim.xml:119(title)
+msgid "Additional VIM Resources"
+msgstr "Weitere VIM Ressourcen"
+
+#: en_US/vim.xml:121(para)
+msgid "Additional information about VIM may be found from:"
+msgstr "Weitere Informationen zu VIM können sie unter folgender Seite bekommen:"
+
+#: en_US/vim.xml:127(para)
+msgid "<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to Vi Improved (VIM)</citetitle>"
+msgstr "<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC\">Beispiel sgml-vimrc</ulink> aus dem <citetitle>Beginner's guide to Vi Improved (VIM)</citetitle>"
+
+#: en_US/vim.xml:134(para)
+msgid "The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick Reference Card</ulink>"
+msgstr "Die <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick Referenz Karte</ulink>"
+
+#: en_US/vim.xml:140(ulink)
+msgid "Vim as XML Editor"
+msgstr "Vim als XML Editor"
+
+#: en_US/vim.xml:145(para)
+msgid "The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the <filename>vim-common</filename> package —<filename>/usr/share/vim/<replaceable><version></replaceable>/doc/intro.txt</filename> or type <userinput>:help intro</userinput> from within VIM"
+msgstr ""
+
+#: en_US/tutorial.xml:13(title)
+msgid "The Layout of a Tutorial"
+msgstr "Das Layout eines Tutorials"
+
+#: en_US/tutorial.xml:14(para)
+msgid "In this chapter, you will find an example of a very short tutorial as used by the Fedora Documentation Project. This example is specific to the way the Docs Project uses DocBook XML. The example consists of a set of files used to hold the content and metadata for the tutorial."
+msgstr ""
+
+#: en_US/tutorial.xml:19(title)
+msgid "The Article"
+msgstr "Der Artikel"
+
+#: en_US/tutorial.xml:21(primary)
+#: en_US/tutorial.xml:56(primary)
+msgid "tutorial layout"
+msgstr "Tutorial-Layout"
+
+#: en_US/tutorial.xml:22(secondary)
+msgid "article"
+msgstr "Artikel"
+
+#: en_US/tutorial.xml:24(para)
+msgid "Below is a sample article:"
+msgstr "Unten ist ein Beispiel-Artikel:"
+
+#: en_US/tutorial.xml:54(title)
+msgid "The Metadata"
+msgstr "Die Metadaten"
+
+#: en_US/tutorial.xml:57(secondary)
+msgid "metadata"
+msgstr "Metadaten"
+
+#: en_US/tutorial.xml:59(para)
+msgid "The <filename>rpm-info.xml</filename> file contains all the required metadata for the document. This metadata includes title, authorship, licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates the content of this file:"
+msgstr ""
+
+#: en_US/tutorial.xml:65(title)
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr "Beispiel <filename>rpm-info.xml</filename> Datei"
+
+#: en_US/tutorial.xml:95(para)
+msgid "If you are not familiar with XML editing, copy and paste this file from an existing module and then edit the values for the various elements as appropriate. Consult Fedora Documentation Project members and help channels for more assistance if needed."
+msgstr ""
+
+#: en_US/style.xml:14(title)
+msgid "Style"
+msgstr "Stil"
+
+#: en_US/style.xml:16(para)
+msgid "Writing good technical documentation is not simply reproducing command lines and instruction sets. Good documentation is easy to read, understand, and translate, and presents a concise logical progression of concepts. Good documentation can also be defined by what it does <emphasis>not</emphasis> contain. Your tutorial should avoid:"
+msgstr ""
+
+#: en_US/style.xml:26(para)
+msgid "Excessive wordiness"
+msgstr "Exzessiv viele Wörter"
+
+#: en_US/style.xml:31(para)
+msgid "Unnecessary or undefined jargon"
+msgstr "Nicht nötiges oder nicht definiertes Jargon"
+
+#: en_US/style.xml:36(para)
+msgid "Grammatical or spelling errors"
+msgstr "Grammatische oder Sprachliche Fehler"
+
+#: en_US/style.xml:41(para)
+msgid "References to yourself or your experiences"
+msgstr ""
+
+#: en_US/style.xml:46(para)
+msgid "Remarks which might offend or confuse any reader"
+msgstr ""
+
+#: en_US/style.xml:51(para)
+msgid "This chapter contains style rules and guidelines for writing Fedora documentation. Guidelines are not the same as rules. It is acceptable to violate a guideline when it makes your material easier to understand. Follow guidelines whenever possible, but follow rules at all times. Assume any advice is a guideline unless identified otherwise."
+msgstr ""
+
+#: en_US/style.xml:62(title)
+msgid "Why Style Is Important"
+msgstr "Wieso Stil wichtig ist"
+
+#: en_US/style.xml:64(para)
+msgid "Writing well comes naturally to almost no one. It is a skill that professional writers, even famous ones, must practice constantly. <firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> is the quality that separates elegant writing from the merely functional."
+msgstr ""
+
+#: en_US/style.xml:77(para)
+msgid "For example, refer to. <ulink url=\"http://www.online-literature.com/james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>. Please note that this example contains some mature themes and language, and is not suitable for all readers."
+msgstr ""
+
+#: en_US/style.xml:71(para)
+msgid "Elegance comes in many forms. In prose and poetry, elegant writing may not follow some (or any) common rules of grammar, syntax, or spelling. A good example is Episode 18, \"Penelope,\" in James Joyce's novel <citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long streams of words without punctuation to simulate a character's internal consciousness. By violating basic rules of grammar and syntax, Joyce simulates the disorganized but loosely connected thought patterns of the narrator."
+msgstr ""
+
+#: en_US/style.xml:89(para)
+msgid "Technical documentation, however, should always respect these rules. The more a document departs from standard language usage, the more difficult the material becomes for the reader. For example, readers may not be native speakers of the language used, or they might be reading a translation. If the writer uses slang, idioms, or jargon, a reader or translator may easily become confused. The following example compares two different written executions of the same idea:"
+msgstr ""
+
+#: en_US/style.xml:100(title)
+msgid "Incorrect style"
+msgstr "Unkorrekter Stil"
+
+#. I prefer "incorrect," because I think terms such as
+#. "problematic" are mealy-mouthed. They remind me of the late
+#. 1980's English textbook trend toward the politically correct yet
+#. wholly unhelpful "standard/nonstandard." But then, I tend to be
+#. dogmatic; it's probably my Catholic upbringing. [PWF]
+#: en_US/style.xml:108(para)
+msgid "So you made the changes I showed you in the last section. What's the next thing you should do? Just pop your thumb drive onto your system and read the <filename>messages</filename> log. When you see \"USB device found,\" then Bob's your uncle."
+msgstr ""
+
+#: en_US/style.xml:116(title)
+msgid "Correct style"
+msgstr "Korrekter Stil"
+
+#. I prefer "correct." See above. [PWF]
+#: en_US/style.xml:120(para)
+msgid ""
+"After you complete the configuration changes above, attach the USB removable media to your system. Use the <command>dmesg</command> command to examine the kernel message log. The message <computeroutput>USB device\n"
+"\t found</computeroutput> indicates that your device was installed successfully."
+msgstr ""
+
+#: en_US/style.xml:129(para)
+msgid "The first example is more conversational English, which is not appropriate for official written documentation. The second example is more formal, but as a result it is easier to comprehend, both for native readers and translators."
+msgstr ""
+
+#: en_US/style.xml:135(para)
+msgid "Following style rules and guidelines also makes readers more comfortable with a set of documents. Consistent style enhances the professional appearance of documentation, and its perceived value. On the other hand, lapses in punctuation or poor grammar negatively affect a reader's reaction to written material. A reader can feel that an otherwise correct technical document is lacking in authority, simply because it is poorly written. Readers feel at ease when they do not have to struggle to understand an author's use of language."
+msgstr ""
+
+#: en_US/style.xml:146(para)
+msgid "This chapter cannot possibly cover enough material to make every reader a good writer. Some manuals devoted entirely to writing style are themselves hundreds of pages long. This chapter provides enough guidelines for intermediate writers to understand style usage in technical documentation."
+msgstr ""
+
+#: en_US/style.xml:153(para)
+msgid "If you are not a practiced writer, whether of technical documentation or otherwise, you may benefit from other style resources. The following list is far from comprehensive, but provides a starting point:"
+msgstr ""
+
+#: en_US/style.xml:161(para)
+msgid "<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules and links to online versions can be found at: <ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+msgstr ""
+
+#: en_US/style.xml:176(para)
+msgid "<citetitle>The Chicago Manual of Style</citetitle>, by the University of Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle.org/\">http://www.chicagomanualofstyle.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:183(para)
+msgid "<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/\">http://www.powa.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:190(para)
+msgid "There are many free software documentation projects which have developed their own style guidelines. This chapter, in fact, draws heavily on the <citetitle>GNOME Documentation Style Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr ""
+
+#: en_US/style.xml:203(title)
+msgid "Fundamental Concepts of Technical Documentation"
+msgstr "Fundamentale Konzepte für technische Dokumentationen"
+
+#: en_US/style.xml:206(title)
+msgid "Bibliographic Information"
+msgstr "Bibliographische Informationen"
+
+#: en_US/style.xml:207(para)
+msgid "This section is drawn primarily from the <citetitle>GDSG</citetitle>."
+msgstr ""
+
+#. This section will reproduce mostly what is in Chapter 1 of
+#. the GDSG. There may be minor changes. FIXME: Make sure the
+#. appropriate front matter of the Documentation Guide includes
+#. attribution as required by the GNU FDL.
+#: en_US/style.xml:218(para)
+msgid "This chapter provides a brief introduction to writing technical documentation."
+msgstr ""
+
+#: en_US/style.xml:224(title)
+msgid "General Style Requirements"
+msgstr "Allgemeine Stil-Anforderungen"
+
+#: en_US/style.xml:225(para)
+msgid "Technical writing for the Fedora Project imposes special constraints beyond the basic requirements of good prose. Good Fedora technical documentation has the following characteristics:"
+msgstr ""
+
+#: en_US/style.xml:232(term)
+msgid "Comprehensive"
+msgstr "umfangreich"
+
+#: en_US/style.xml:234(para)
+msgid "Describe all of the functionality of a product. Do not omit functionality that you regard as irrelevant for the user."
+msgstr ""
+
+#: en_US/style.xml:242(term)
+msgid "Conforming"
+msgstr "Konform"
+
+#: en_US/style.xml:249(para)
+msgid "Describe what you see. Do not describe what you want to see. Present your information in the order that users experience the subject matter."
+msgstr ""
+
+#: en_US/style.xml:257(term)
+msgid "Clear"
+msgstr "Lösche"
+
+#: en_US/style.xml:259(para)
+msgid "Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>) to help make your writing clear."
+msgstr ""
+
+#: en_US/style.xml:275(term)
+msgid "Consistent"
+msgstr "Kosistent"
+
+#: en_US/style.xml:277(para)
+msgid "Use agreed vocabulary throughout your documentation. Use the same vocabulary as other writers who are working on related documentation."
+msgstr ""
+
+#: en_US/style.xml:285(term)
+msgid "Concise"
+msgstr "Präzis"
+
+#: en_US/style.xml:287(para)
+msgid "Review your work frequently as you write your document. Ask yourself which words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for specific guidelines."
+msgstr ""
+
+#: en_US/style.xml:297(title)
+msgid "Golden Rules"
+msgstr "Goldene Regeln"
+
+#: en_US/style.xml:298(para)
+msgid "This section contains some basic style guidelines. Subsequent sections in this chapter expand on these guidelines to give more detailed guidance."
+msgstr ""
+
+#: en_US/style.xml:305(term)
+msgid "Golden Rule 1: Be brief"
+msgstr "Goldene Regel 1: Sei kurz"
+
+#: en_US/style.xml:309(para)
+msgid "Limit each sentence to fewer than 25 words."
+msgstr ""
+
+#: en_US/style.xml:314(para)
+msgid "Limit each procedure step to 23 words."
+msgstr ""
+
+#: en_US/style.xml:320(title)
+msgid "Incorrect: Too long"
+msgstr "Unkorrekt: zu lang"
+
+#: en_US/style.xml:321(para)
+msgid "Under normal operating conditions, the kernel does not always immediately write file data to the disks, storing it in a memory buffer and then periodically writing to the disks to speed up operations."
+msgstr ""
+
+#: en_US/style.xml:328(title)
+msgid "Correct: Less wordy"
+msgstr "Korrekt: weniger Wörter"
+
+#: en_US/style.xml:329(para)
+msgid "Normally, the kernel stores the data in memory prior to periodically writing the data to the disk."
+msgstr ""
+
+#: en_US/style.xml:337(term)
+msgid "Golden Rule 2: Be organized"
+msgstr "Goldene Regel 2: Sei organisiert "
+
+#: en_US/style.xml:341(para)
+msgid "Limit each paragraph to one topic."
+msgstr ""
+
+#: en_US/style.xml:346(para)
+msgid "Limit each sentence to one idea."
+msgstr ""
+
+#: en_US/style.xml:351(para)
+msgid "Limit each procedure step to one action."
+msgstr ""
+
+#: en_US/style.xml:357(title)
+msgid "Incorrect: Disorganized topics"
+msgstr "Unkorrekt: Disorganized topics"
+
+#: en_US/style.xml:358(para)
+msgid "The <application>Workspace Switcher</application> applet helps you navigate all of the virtual desktops available on your system. The X Window system, working in hand with a piece of software called a <emphasis>window manager</emphasis>, allows you to create more than one virtual desktop, known as <emphasis>workspaces</emphasis>, to organize your work, with different applications running in each workspace. The <application>Workspace Switcher</application> applet is a navigational tool to get around the various workspaces, providing a miniature road map in the GNOME panel showing all your workspaces and allowing you to switch easily between them."
+msgstr ""
+
+#: en_US/style.xml:375(title)
+msgid "Correct: Organized topics"
+msgstr "Korrekt: Organisierte Themen"
+
+#: en_US/style.xml:376(para)
+msgid "Use the <application>Workspace Switcher</application> to add new <emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different applications in each workspace. The <application>Workspace Switcher</application> applet provides a miniature map that shows all of your workspaces. You can use the <application>Workspace Switcher</application> applet to switch between workspaces."
+msgstr ""
+
+#: en_US/style.xml:388(para)
+msgid "Plan the order of paragraphs before you start writing. Decide which topic you want to cover in each paragraph."
+msgstr ""
+
+#: en_US/style.xml:396(term)
+msgid "Golden Rule 3: Be demonstrative"
+msgstr "Goldene Regel 3: Sei anschaulich "
+
+#: en_US/style.xml:398(para)
+msgid "Use explicit examples to demonstrate how an application works. Provide instructions rather than descriptions."
+msgstr ""
+
+#: en_US/style.xml:403(title)
+msgid "Incorrect: Describes but does not demonstrate"
+msgstr ""
+
+#: en_US/style.xml:405(para)
+msgid "There is a text box that you can use to find out the definition of a word."
+msgstr ""
+
+#: en_US/style.xml:411(title)
+msgid "Correct: Demonstrates usage"
+msgstr "Korrekt: Demonstriert Benutzung"
+
+#: en_US/style.xml:412(para)
+msgid "To request a definition of a word, type the word in the text box, then select <guilabel>Lookup</guilabel>."
+msgstr ""
+
+#: en_US/style.xml:418(para)
+msgid "Do not apply this guideline too rigidly. Sometimes you must explain how software works to support your how-to examples."
+msgstr ""
+
+#: en_US/style.xml:427(term)
+msgid "Golden Rule 4: Be objective"
+msgstr "Goldene Regel 4: Sei objektiv "
+
+#: en_US/style.xml:429(para)
+msgid "Write in a neutral tone."
+msgstr "Schreibe in einem neutralen Ton"
+
+#: en_US/style.xml:433(title)
+#, fuzzy
+msgid "Incorrect: Sentence takes sides"
+msgstr "Unkorrekt: Sätze ..."
+
+#: en_US/style.xml:434(para)
+msgid "The applet is a handy little screen grabber."
+msgstr ""
+
+#: en_US/style.xml:439(title)
+msgid "Correct: Sentence is objective"
+msgstr "Korrekt: Der Satz ist objektiv"
+
+#: en_US/style.xml:440(para)
+msgid "Use the applet to take screenshots."
+msgstr ""
+
+#: en_US/style.xml:452(title)
+msgid "Tone"
+msgstr "Ton"
+
+#: en_US/style.xml:453(para)
+msgid "Inappropriate tone hinders reader access to information. A neutral tone free of opinion or personal flavor improves the reader's comprehension. Neutral tone helps writers to work in parallel on a large technical documentation project. Furthermore, additional writers may join the project at any time. Use of a neutral tone helps to achieve consistency across a documentation set, and thereby facilitates user access to information. The best way to achieve a common, neutral tone is to apply the following principles:"
+msgstr ""
+
+#: en_US/style.xml:466(term)
+msgid "Avoid humor"
+msgstr "Vermeide Humor"
+
+#: en_US/style.xml:468(para)
+msgid "Humor distracts from the information you are trying to provide. Humor also makes documentation difficult to translate. Stay factual."
+msgstr ""
+
+#: en_US/style.xml:476(term)
+msgid "Avoid personal opinions"
+msgstr "Vermeide persönliche Meinungen"
+
+#: en_US/style.xml:478(para)
+msgid "Whether you think a function is useful or woeful is irrelevant. Report the function to the user, with instructions about how to use the function. Stay accurate."
+msgstr ""
+
+#: en_US/style.xml:487(term)
+msgid "Avoid colloquial language"
+msgstr "Vermeide kollegiale Sprache"
+
+#: en_US/style.xml:489(para)
+msgid "Colloquial language is difficult to translate and usually culture-specific. Stay neutral."
+msgstr ""
+
+#: en_US/style.xml:496(term)
+msgid "Avoid topical expressions"
+msgstr "Vermeide tropische Ausdrücke"
+
+#: en_US/style.xml:498(para)
+msgid "An expression that is in common use today might convey something completely different tomorrow. Stay technical."
+msgstr ""
+
+#: en_US/style.xml:505(term)
+msgid "Avoid aspirational statements"
+msgstr "Vermeide luftige Statements"
+
+#: en_US/style.xml:507(para)
+msgid "Statements about the future developments of a product do not belong in technical documentation. Write about what you see right now. Stay real."
+msgstr ""
+
+#: en_US/style.xml:517(title)
+msgid "Reaching the Right Audience"
+msgstr "erreichen des richtigen Publikum"
+
+#: en_US/style.xml:518(para)
+msgid "All of the decisions that you make about the structure and content of a manual follow from an understanding of the audience. Consider how the audience accesses the documentation, what sort of information the audience needs, and the experience level of the audience. Usually, you need to create documentation that is suitable for different audiences. The following sections introduce some of the audience-related topics you need to consider."
+msgstr ""
+
+#: en_US/style.xml:530(title)
+msgid "User Motivation"
+msgstr "Benutzer-Motivation"
+
+#: en_US/style.xml:531(para)
+msgid "Do not waste the time of the user who looks for information in your documentation. Users do not read technical documentation for entertainment. Users usually have specific questions. You need to give clear answers to those questions."
+msgstr ""
+
+#: en_US/style.xml:539(title)
+msgid "New Users"
+msgstr "Neue Benutzer"
+
+#: en_US/style.xml:540(para)
+msgid "New users to Fedora are likely to consult online tutorials for guidance about unfamiliar applications or functionality. Each tutorial should contain enough introductory information to tell new users how to start using the relevant functions. Each tutorial should also contain enough usage instructions to tell users the different actions that they can perform with the command or function. Keep these instructions task-oriented. Do not describe GUI screens, dialogs, and dialog elements in a tutorial, unless there is an unusual feature that affects your instructions."
+msgstr ""
+
+#: en_US/style.xml:554(title)
+msgid "Experienced Users"
+msgstr "Erfahrene Benutzer"
+
+#: en_US/style.xml:555(para)
+msgid "Experienced users are more likely to use documentation as a reference. The documentation therefore needs to be complete, well-organized, and in the case of printed manuals, well-indexed."
+msgstr ""
+
+#: en_US/style.xml:563(title)
+msgid "Do Not Offend Your Audience"
+msgstr ""
+
+#: en_US/style.xml:564(para)
+msgid "To avoid offending your readers, apply the following guidelines to your documentation:"
+msgstr ""
+
+#: en_US/style.xml:570(term)
+msgid "Avoid insider language"
+msgstr "Vermeide Insider-Sprache"
+
+#: en_US/style.xml:572(para)
+msgid "Insider language includes both undefined jargon and the tendency of the computer community to shorten words. For example, use the term <literal>documentation</literal> instead of the term <literal>docs</literal>. A term may be jargon if it fails all the following conditions:"
+msgstr ""
+
+#: en_US/style.xml:581(para)
+msgid "The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> (<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora.redhat.com/docs/jargon-buster/</ulink>)."
+msgstr ""
+
+#: en_US/style.xml:588(para)
+msgid "The term does not appear in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/ </ulink>)."
+msgstr ""
+
+#: en_US/style.xml:596(para)
+msgid "The term does not appear in the glossary of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:602(para)
+msgid "The term is not defined in the body text of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:611(term)
+msgid "Avoid gender-specific language"
+msgstr ""
+
+#: en_US/style.xml:613(para)
+msgid "Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</literal> do not exist. There is no need to identify gender in your instructions."
+msgstr ""
+
+#: en_US/style.xml:621(term)
+msgid "Avoid culture-specific language"
+msgstr "Vermeide kulturbezogene Ausdruckweisen"
+
+#: en_US/style.xml:623(para)
+msgid "There is little point in giving an example that everyone in your town knows about, but is a complete mystery to everyone else in the world."
+msgstr ""
+
+#: en_US/style.xml:631(term)
+msgid "Avoid talking down to your reader"
+msgstr ""
+
+#: en_US/style.xml:633(para)
+msgid "There are few experiences more irritating for a user than documentation that says an action is easy or quick, when in fact the user cannot complete the action. Do not qualify or prejudge actions."
+msgstr ""
+
+#: en_US/style.xml:642(para)
+msgid "Other parts of this guide discuss in more detail tone and language usage that can cause offense."
+msgstr ""
+
+#: en_US/style.xml:653(title)
+msgid "Grammar and Usage Guidelines"
+msgstr "Grammatik- und Benutzungs-Richtlinien"
+
+#: en_US/style.xml:656(title)
+msgid "Bibliographical Information"
+msgstr "Bibliograpfische Informationen"
+
+#: en_US/style.xml:657(para)
+msgid "This section is drawn partly from the <citetitle>GDSG</citetitle>, and partly from <citetitle>The Elements of Style</citetitle>, updated as necessary for the needs of 21st-century technical documentation writers."
+msgstr ""
+
+#. FIXME: Again, check attribution viz. GNU FDL. This will be more work
+#. than the previous section.
+#: en_US/style.xml:668(para)
+msgid "This section contains an alphabetical list of grammar and usage guidelines for use in Fedora documentation. Many of these guidelines are only applicable to English-language usage, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:679(term)
+msgid "Abbreviations"
+msgstr "Abkürzungen"
+
+#: en_US/style.xml:681(para)
+msgid "A shortened form of a word or phrase that takes the place of the full word or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, <literal>p.m.</literal>, and so on. Apply the following rules when you use abbreviations:"
+msgstr ""
+
+#: en_US/style.xml:689(para)
+msgid "Avoid creating new abbreviations. Unfamiliar abbreviations can confuse rather than clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:695(para)
+msgid "Do not explain or expand familiar abbreviations."
+msgstr ""
+
+#: en_US/style.xml:700(para)
+msgid "Do not include familiar abbreviations in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:706(para)
+msgid "For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other words\" and <literal>e.g.</literal> for \"for example\", do not use the abbreviation. Spell out the entire phrase."
+msgstr ""
+
+#: en_US/style.xml:715(term)
+msgid "Adjectives"
+msgstr "Adjektive"
+
+#: en_US/style.xml:717(para)
+msgid "Use adjectives with caution. If an adjective is necessary to differentiate between items, then use adjectives. In all cases, test whether the phrase can stand alone without the adjective."
+msgstr ""
+
+#: en_US/style.xml:726(term)
+msgid "Acronyms"
+msgstr "Akronyme"
+
+#: en_US/style.xml:728(para)
+msgid "A term that represents a multi-word term. Typically, acronyms are formed in the following ways:"
+msgstr ""
+
+#: en_US/style.xml:734(para)
+msgid "From the first letters of each word in a compound term, for example Table of Contents (TOC)."
+msgstr ""
+
+#: en_US/style.xml:740(para)
+msgid "From recognizable parts of a compound term, such as GNU Object Model Environment (GNOME)."
+msgstr ""
+
+#: en_US/style.xml:746(para)
+msgid "Apply the following rules when you use acronyms:"
+msgstr ""
+
+#: en_US/style.xml:751(para)
+msgid "On the first occurrence of an acronym, spell out the full term, with the acronym in parentheses."
+msgstr ""
+
+#: en_US/style.xml:757(para)
+msgid "Do not spell out the full compound for well-known acronyms, unless you think the information is useful for readers."
+msgstr ""
+
+#: en_US/style.xml:764(para)
+msgid "Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:770(para)
+msgid "Write the acronym in uppercase letters, unless there is a compelling case for lowercase."
+msgstr ""
+
+#: en_US/style.xml:776(para)
+msgid "Include the acronym and the full term in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:785(term)
+msgid "Adverbs"
+msgstr "Adverben"
+
+#: en_US/style.xml:787(para)
+msgid "Use adverbs with caution. If an adverb is necessary to qualify the function of a component, then use an adverb. In all cases, test whether the phrase can stand alone without the adverb. Classic superfluous adverbs <literal>simply</literal>, <literal>easily</literal>, <literal>quickly</literal>."
+msgstr ""
+
+#: en_US/style.xml:798(term)
+msgid "Anthropomorphism"
+msgstr ""
+
+#: en_US/style.xml:802(para)
+msgid "Do not apply emotions, desires, or opinions to software applications."
+msgstr ""
+
+#: en_US/style.xml:808(para)
+msgid "Do not apply a sense of location or dimension to a software application. A user can not be \"in\" a text editor."
+msgstr ""
+
+#: en_US/style.xml:818(term)
+msgid "Articles"
+msgstr "Artikel"
+
+#: en_US/style.xml:820(para)
+msgid "Do not use the definite article <literal>the</literal> to begin any of the following items:"
+msgstr ""
+
+#: en_US/style.xml:826(para)
+msgid "Manual titles"
+msgstr "Manuelle Titel"
+
+#: en_US/style.xml:831(para)
+msgid "Chapter titles"
+msgstr "Kapitel Titel"
+
+#: en_US/style.xml:836(para)
+#: en_US/style.xml:1239(term)
+msgid "Headings"
+msgstr "Überschriften"
+
+#: en_US/style.xml:841(para)
+msgid "Figure captions"
+msgstr "Zeichnungs-Beschreibung"
+
+#: en_US/style.xml:846(para)
+msgid "Table captions"
+msgstr "Tabelle-Beschriftungen"
+
+#: en_US/style.xml:851(para)
+msgid "Callouts"
+msgstr "Ausrufe"
+
+#: en_US/style.xml:859(term)
+msgid "Apostrophe"
+msgstr "Apostroph"
+
+#: en_US/style.xml:861(para)
+msgid "Do not use apostrophes except where absolutely required"
+msgstr ""
+
+#: en_US/style.xml:866(para)
+msgid "Do not use apostrophes to denote possession."
+msgstr ""
+
+#: en_US/style.xml:871(para)
+msgid "Do not use apostrophes to denote contractions."
+msgstr ""
+
+#: en_US/style.xml:876(para)
+msgid "Do not use apostrophes to denote plurals."
+msgstr ""
+
+#: en_US/style.xml:882(title)
+msgid "Incorrect: Apostrophes"
+msgstr "Inkorrekt: Apostrophs"
+
+#: en_US/style.xml:885(para)
+msgid "the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+msgstr ""
+
+#: en_US/style.xml:891(para)
+msgid "don't use the default option"
+msgstr "benutze nicht die Standard-Option"
+
+#: en_US/style.xml:896(para)
+msgid "several SCSI disk's"
+msgstr "Diverse SCSI Disks"
+
+#: en_US/style.xml:903(title)
+msgid "Correct: No apostrophes"
+msgstr "Korrekt: Keine Apostrophs"
+
+#: en_US/style.xml:906(para)
+msgid "the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</guimenu>"
+msgstr ""
+
+#: en_US/style.xml:912(para)
+msgid "do not use the default option"
+msgstr "benutze nicht die Standard-Option"
+
+#: en_US/style.xml:917(para)
+msgid "several SCSI disks"
+msgstr "diverse SCSI Disks"
+
+#: en_US/style.xml:926(term)
+msgid "Brackets"
+msgstr "Klammern"
+
+#: en_US/style.xml:930(para)
+msgid "Do not use brackets [such as these] as a substitute for parentheses (such as these)."
+msgstr ""
+
+#: en_US/style.xml:936(para)
+msgid "Use brackets for optional command line entries."
+msgstr ""
+
+#: en_US/style.xml:941(para)
+msgid "Do not use angle brackets to indicate variables in text, instead use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+msgstr ""
+
+#: en_US/style.xml:953(term)
+msgid "Capitalization"
+msgstr "Grossschreibung"
+
+#: en_US/style.xml:955(para)
+msgid "Capitalize in the following situations:"
+msgstr "Grossschreibung in folgenden Situationen"
+
+#: en_US/style.xml:960(para)
+msgid "All letters in acronyms, unless the acronym is a well-known exception"
+msgstr ""
+
+#: en_US/style.xml:966(para)
+msgid "Initial letter of the first word in a list"
+msgstr ""
+
+#: en_US/style.xml:971(para)
+msgid "Initial letter of the first word in a callout"
+msgstr ""
+
+#: en_US/style.xml:976(para)
+msgid "Initial letter of a key name, such as the <keycap>Shift</keycap> key"
+msgstr ""
+
+#: en_US/style.xml:982(para)
+msgid "Initial letter of a sentence"
+msgstr "Erster Buchstaben eines Satzes"
+
+#: en_US/style.xml:986(title)
+msgid "Command Names"
+msgstr "Befehlsnamen"
+
+#: en_US/style.xml:987(para)
+msgid "Avoid starting a sentence with a command name or application name that has a lowercase initial letter."
+msgstr ""
+
+#: en_US/style.xml:994(para)
+msgid "Initial letter of a complete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:999(para)
+msgid "Do not capitalize in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1004(para)
+msgid "A compound term that is followed by an abbreviation or an acronym"
+msgstr ""
+
+#: en_US/style.xml:1010(para)
+msgid "When you want to emphasize something"
+msgstr ""
+
+#: en_US/style.xml:1015(para)
+msgid "Variable names"
+msgstr "Variabel-Namen"
+
+#: en_US/style.xml:1020(para)
+msgid "The initial letter of an incomplete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:1029(term)
+msgid "Captions"
+msgstr "Untertitel"
+
+#: en_US/style.xml:1031(para)
+msgid "Use the same rules as for headings, for all captions accompanying figures and tables. Do not put a period at the end of a caption."
+msgstr ""
+
+#: en_US/style.xml:1039(term)
+msgid "Colon"
+msgstr "Doppelpunkt"
+
+#: en_US/style.xml:1041(para)
+#, fuzzy
+msgid "Use a colon in the following situations:"
+msgstr "Folgende für Klassen in generiertem Quelltext verwenden:"
+
+#: en_US/style.xml:1046(para)
+#, fuzzy
+msgid "To introduce a list"
+msgstr "Hinzufügen"
+
+#: en_US/style.xml:1051(para)
+msgid "Before an explanation"
+msgstr "Vor einer Erklärung"
+
+#: en_US/style.xml:1056(para)
+msgid "After an introduction"
+msgstr "Nach einer Einleitung"
+
+#: en_US/style.xml:1061(para)
+#, fuzzy
+msgid "Do not use a colon in the following situations:"
+msgstr "Der Name '%s' enthält einen Doppelpunkt. Bitte keine solchen im Namen verwenden."
+
+#: en_US/style.xml:1066(para)
+msgid "To introduce a figure or a table"
+msgstr "Um eine Tabelle oder eine Zeichnung zu beschreiben"
+
+#: en_US/style.xml:1071(para)
+msgid "To introduce headings"
+msgstr "Um Überschriften einzufügen"
+
+#: en_US/style.xml:1076(para)
+#, fuzzy
+msgid "At the end of an introduction to a procedure"
+msgstr "Veraltet: GOTO bei %L springt zum ENDe des Konstrukts bei %L"
+
+#: en_US/style.xml:1084(term)
+msgid "Column headings"
+msgstr "Spaltenkopf"
+
+#: en_US/style.xml:1086(para)
+msgid "Use the same rules as for headings."
+msgstr "Benutze die gleichen Regeln wie für die Überschriften"
+
+#: en_US/style.xml:1092(term)
+msgid "Comma"
+msgstr "Komma"
+
+#: en_US/style.xml:1094(para)
+msgid "Use commas in the following situations:"
+msgstr "Benutze Kommas in den folgenden Situationen:"
+
+#: en_US/style.xml:1099(para)
+#, fuzzy
+msgid "To separate items in a series"
+msgstr "Wann die Anzahl der Objekte in einem Ordner angezeigt werden soll"
+
+#: en_US/style.xml:1104(para)
+#, fuzzy
+msgid "To separate the parts of a sentence"
+msgstr "<p>Springt zum nächsten Satz im Auftrag.</p>"
+
+#: en_US/style.xml:1109(para)
+#, fuzzy
+msgid "To separate nonrestrictive phrases"
+msgstr "beschränkt auf 8, getrennt durch Kommas"
+
+#: en_US/style.xml:1114(para)
+msgid "Instead of dashes to set off appositives"
+msgstr ""
+
+#: en_US/style.xml:1119(para)
+msgid "With <emphasis>for example</emphasis> and similar expressions"
+msgstr ""
+
+#: en_US/style.xml:1125(para)
+msgid "Do not use commas in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1130(para)
+msgid "In a series of adjectives used as one modifier"
+msgstr ""
+
+#: en_US/style.xml:1135(para)
+msgid "Between two short independent clauses"
+msgstr ""
+
+#: en_US/style.xml:1143(term)
+#: en_US/emacs-nxml.xml:86(title)
+msgid "Commands"
+msgstr "Befehle "
+
+#: en_US/style.xml:1145(para)
+msgid "Do not use commands as verbs."
+msgstr "Benutze Befehle nicht als Verben."
+
+#: en_US/style.xml:1151(term)
+msgid "Contractions"
+msgstr "Verkürzungen"
+
+#: en_US/style.xml:1153(para)
+msgid "Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</emphasis>, or <emphasis>isn't</emphasis>."
+msgstr ""
+
+#: en_US/style.xml:1160(term)
+msgid "Dash"
+msgstr "Strich"
+
+#: en_US/style.xml:1162(para)
+msgid "Do not use the em dash or the en dash. Use a paragraph break or a colon instead, where you want to create an introductory piece of text. If you have several items that you want to introduce, then you can use a variable list."
+msgstr ""
+
+#: en_US/style.xml:1171(term)
+msgid "Ellipsis"
+msgstr "Auslassungspunkte"
+
+#: en_US/style.xml:1173(para)
+msgid "Use an ellipsis in the following situations:"
+msgstr "Benutze eine Auslassung in folgenden Situationen:"
+
+#: en_US/style.xml:1178(para)
+msgid "To show that you have omitted something from a sentence"
+msgstr ""
+
+#: en_US/style.xml:1183(para)
+msgid "To indicate a pause when you quote displayed text"
+msgstr ""
+
+#: en_US/style.xml:1191(term)
+msgid "Fractions"
+msgstr "Brüche"
+
+#: en_US/style.xml:1193(para)
+msgid "Follow these rules when using fractions:"
+msgstr ""
+
+#: en_US/style.xml:1198(para)
+msgid "Use numerals for fractions in tables and in units of measurement, but spell out fractions in prose."
+msgstr ""
+
+#: en_US/style.xml:1204(para)
+msgid "Use a space between a numeral and a related fraction, if there is a possible ambiguity. For example: 1 1/2 instead of 11/2."
+msgstr ""
+
+#: en_US/style.xml:1211(para)
+msgid "If a fraction is used in a compound modifier, insert a hyphen between the fraction and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1220(term)
+msgid "Gender"
+msgstr "Geschlecht"
+
+#: en_US/style.xml:1222(para)
+msgid "Refer to <xref linkend=\"sn-fundamentals-9\"/>."
+msgstr ""
+
+#: en_US/style.xml:1228(term)
+msgid "Grammar"
+msgstr "Grammatik"
+
+#: en_US/style.xml:1230(para)
+msgid "Use standard American English grammar rules, refer to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1241(para)
+msgid "Use the following capitalization rules in headings:"
+msgstr ""
+
+#: en_US/style.xml:1246(para)
+#, fuzzy
+msgid "Initial uppercase letter of the first word"
+msgstr "Den ersten Buchstaben aller markierten Wörter in Großschreibung überführen"
+
+#: en_US/style.xml:1251(para)
+msgid "Initial uppercase letter for all nouns, adjectives, and verbs."
+msgstr ""
+
+#: en_US/style.xml:1257(para)
+msgid "All lowercase letters for conjunctions, articles, and prepositions of fewer than four letters"
+msgstr ""
+
+#: en_US/style.xml:1263(para)
+msgid "Initial uppercase letter for prepositions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1269(para)
+msgid "Initial uppercase letter for conjunctions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1280(term)
+msgid "Hyphen"
+msgstr "Bindestrich"
+
+#: en_US/style.xml:1282(para)
+msgid "Use hyphens in the following situations:"
+msgstr "Benutze Bindestriche in folgenden Situationen:"
+
+#: en_US/style.xml:1287(para)
+msgid "With a numeral in a compound modifier"
+msgstr ""
+
+#: en_US/style.xml:1291(para)
+msgid "To prevent ambiguity"
+msgstr "To prevent ambiguity"
+
+#: en_US/style.xml:1296(para)
+msgid "With some standard prefixes and suffixes. Use the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidance"
+msgstr ""
+
+#: en_US/style.xml:1305(para)
+#, fuzzy
+msgid "In spelled-out fractions"
+msgstr "In einem Raster anordnen"
+
+#: en_US/style.xml:1310(para)
+msgid "In variable names of two or more words, such as <replaceable>directory-name</replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+msgstr ""
+
+#: en_US/style.xml:1317(para)
+msgid "Do not use hyphens in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1322(para)
+msgid "For industry-accepted terms"
+msgstr ""
+
+#: en_US/style.xml:1327(para)
+#, fuzzy
+msgid "To construct verbs"
+msgstr "Konstruiert eine Gerade parallel zu dieser"
+
+#: en_US/style.xml:1332(para)
+msgid "With an adverb ending in <emphasis>ly</emphasis>"
+msgstr ""
+
+#: en_US/style.xml:1337(para)
+msgid "With numerals as single modifiers"
+msgstr ""
+
+#: en_US/style.xml:1342(para)
+msgid "With a word that is listed as unhyphenated in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+msgstr ""
+
+#: en_US/style.xml:1351(para)
+msgid "With trademarked terms"
+msgstr "Mit Trademark Bedingungen"
+
+#: en_US/style.xml:1359(term)
+#, fuzzy
+msgid "Latin terms"
+msgstr "Zahlungsbedingungen"
+
+#: en_US/style.xml:1361(para)
+msgid "Do not use Latin terms. Use an equivalent English term instead."
+msgstr ""
+
+#: en_US/style.xml:1368(term)
+msgid "Like"
+msgstr "Wie"
+
+#: en_US/style.xml:1370(para)
+msgid "Do not use the term <emphasis>like</emphasis> to denote equivalence or similarity."
+msgstr ""
+
+#: en_US/style.xml:1377(term)
+msgid "Lists"
+msgstr "Liste"
+
+#: en_US/style.xml:1379(para)
+msgid "Introduce a list with a complete sentence that ends with a colon."
+msgstr ""
+
+#: en_US/style.xml:1386(term)
+msgid "Numbers"
+msgstr "Nummern"
+
+#: en_US/style.xml:1388(para)
+msgid "Spell out numbers in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1393(para)
+msgid "Numbers from zero through nine unless the number is part of a measurement"
+msgstr ""
+
+#: en_US/style.xml:1398(para)
+msgid "Approximations"
+msgstr "Annäherung"
+
+#: en_US/style.xml:1403(para)
+msgid "Extreme values such as <emphasis>million</emphasis>, but precede the value with a numeral"
+msgstr ""
+
+#: en_US/style.xml:1409(para)
+msgid "Any number that begins a sentence"
+msgstr ""
+
+#: en_US/style.xml:1414(para)
+msgid "A number that is immediately followed by a numeral, for example: <literal>two 10 MB files</literal>"
+msgstr ""
+
+#: en_US/style.xml:1423(term)
+msgid "Numerals"
+msgstr "»Ziffern"
+
+#: en_US/style.xml:1425(para)
+msgid "Use numerals in the following situations:"
+msgstr "Benutze Ziffern in folgenden Situationen:"
+
+#: en_US/style.xml:1430(para)
+msgid "The number 10 or greater"
+msgstr "Die Zahl 10 oder grösser"
+
+#: en_US/style.xml:1435(para)
+msgid "Negative numbers"
+msgstr "Negative Zahlen"
+
+#: en_US/style.xml:1439(para)
+#, fuzzy
+msgid "Most fractions"
+msgstr "Termanzahl"
+
+#: en_US/style.xml:1444(para)
+msgid "Percentages"
+msgstr "Prozente"
+
+#: en_US/style.xml:1449(para)
+msgid "Decimals"
+msgstr "Dezimalen"
+
+#: en_US/style.xml:1454(para)
+msgid "Measurements"
+msgstr "Masse"
+
+#: en_US/style.xml:1459(para)
+msgid "Units of time smaller than one second"
+msgstr ""
+
+#: en_US/style.xml:1464(para)
+msgid "References to bits and bytes"
+msgstr "Referenzen zu Bits und Bytes"
+
+#: en_US/style.xml:1472(term)
+msgid "Parentheses"
+msgstr "Einklammern"
+
+#: en_US/style.xml:1474(para)
+msgid "Use parentheses in the following situations:"
+msgstr "Benutze Klammern in folgenden Situationen:"
+
+#: en_US/style.xml:1479(para)
+msgid "To contain the abbreviation of a term on the first occurrence of the full term"
+msgstr ""
+
+#: en_US/style.xml:1485(para)
+msgid "In man page references, specifically the section number"
+msgstr ""
+
+#: en_US/style.xml:1493(term)
+msgid "Period"
+msgstr "Periode"
+
+#: en_US/style.xml:1495(para)
+msgid "Use a period in the following situations:"
+msgstr "Benutze eine Periode in folgenden Situationen:"
+
+#: en_US/style.xml:1500(para)
+msgid "To end a sentence"
+msgstr "Um einen Satz zu beenden"
+
+#: en_US/style.xml:1505(para)
+msgid "In file and directory names"
+msgstr "In Datei- und Verzeichnisnamen"
+
+#: en_US/style.xml:1510(para)
+msgid "In abbreviations that can be mistaken for words, such as a.m. and U.S."
+msgstr ""
+
+#: en_US/style.xml:1519(term)
+msgid "Punctuation"
+msgstr "Interpunktion"
+
+#: en_US/style.xml:1521(para)
+msgid "Use standard American English punctuation rules. In addition to the specific points of punctuation in this section, refer also to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1531(term)
+msgid "Punctuation in numbers"
+msgstr "Interpunktion in Zahlen"
+
+#: en_US/style.xml:1533(para)
+msgid "Do not use a comma in numerals of four digits. Use a comma in numerals of more than four digits."
+msgstr ""
+
+#: en_US/style.xml:1540(term)
+msgid "Quotation marks"
+msgstr "Anführungszeichen"
+
+#: en_US/style.xml:1542(para)
+msgid "Use quotation marks to indicate material that is taken verbatim from another source. Do not use quotation marks to excuse terms from legitimacy. If the term is not legitimate, then use another term. If you must use that term, declare the term in the glossary and make the term legitimate."
+msgstr ""
+
+#: en_US/style.xml:1553(term)
+msgid "See v. Refer to"
+msgstr "Sehe gegen verweisen zu"
+
+#: en_US/style.xml:1555(para)
+msgid "When referring a user to another resource, use \"refer to\" instead of \"see\", and \"refer also to\" instead of \"see also\". This differentiates from the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag\">seealso</sgmltag> tags that are used in indexing. These tags create special links in the index. To be consistent throughout the document, we reserve the special words \"see\" and \"see also\" for hyperlinked index references, and use \"refer to\" and \"refer also to\" for non-hyperlinked and non-indexed references."
+msgstr ""
+
+#: en_US/style.xml:1570(term)
+msgid "Semicolon"
+msgstr "Semikolon"
+
+#: en_US/style.xml:1572(para)
+msgid "Do not use semicolons."
+msgstr "Benutze keine Semikolons."
+
+#: en_US/style.xml:1578(term)
+msgid "Slash"
+msgstr "Slash"
+
+#: en_US/style.xml:1580(para)
+msgid "Except where required as part of a filename, do not use slashes \"/\" in your writing. The construction <literal>and/or</literal>, for example, does not exist. Use one or the other term instead."
+msgstr ""
+
+#: en_US/style.xml:1589(term)
+msgid "Spelling"
+msgstr "Rechtschreibung"
+
+#: en_US/style.xml:1591(para)
+msgid "Use standard American English spelling rules, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+msgstr ""
+
+#: en_US/style.xml:1600(term)
+msgid "Titles"
+msgstr "Titel"
+
+#: en_US/style.xml:1602(para)
+msgid "For manual titles use the same rules as for headings."
+msgstr ""
+
+#: en_US/style.xml:1608(term)
+msgid "Units"
+msgstr "Einheiten"
+
+#: en_US/style.xml:1610(para)
+msgid "Follow these rules when using units:"
+msgstr ""
+
+#: en_US/style.xml:1615(para)
+msgid "Use standard abbreviations for units of measurements, do not invent your own abbreviations."
+msgstr ""
+
+#: en_US/style.xml:1621(para)
+msgid "For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of Electrical and Electronics Terms</citetitle>."
+msgstr ""
+
+#: en_US/style.xml:1630(para)
+msgid "Use periods for abbreviated units that might be mistaken for a word."
+msgstr ""
+
+#: en_US/style.xml:1636(para)
+msgid "Most standard abbreviations of units account for both singular and plural usage."
+msgstr ""
+
+#: en_US/style.xml:1642(para)
+msgid "Insert a space between the numeral and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1656(title)
+msgid "Composition Tips"
+msgstr "Erstellungs-Tipps"
+
+#. This section will collect miscellanea and advice for specific
+#. situations that the FDP editors encounter. I hope they will feel
+#. free to e-mail me sticky situations or particularly interesting
+#. examples of work they've beautified. Hopefully not too much will be
+#. drawn from my own work! - PWF.
+#: en_US/style.xml:1668(para)
+msgid "This section contains usage tips based on situations the Fedora Documentation Project editors have encountered in the past. You should read and understand these examples to improve your own documentation. The Fedora Documentation Project editors welcome additional examples."
+msgstr ""
+
+#: en_US/style.xml:1676(title)
+msgid "Active Voice"
+msgstr "Aktive Sprache"
+
+#: en_US/style.xml:1677(para)
+msgid "Always use active voice, except when it is awkward to do so. The tutorial tells the user how to accomplish a task, and should give instructions clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. These words are redundant in a tutorial, since the reader assumes you are outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" \"might,\" and other words that indicate you are unsure about the subject matter. Your tutorial should cover a subject authoritatively. The reader should never be concerned about unknown effects of following the tutorial."
+msgstr ""
+
+#: en_US/style.xml:1690(title)
+msgid "Incorrect: Passive voice"
+msgstr "Unkorrekt: Passive Sätze"
+
+#: en_US/style.xml:1691(para)
+msgid "The <command>yum update</command> command must be run."
+msgstr ""
+
+#: en_US/style.xml:1694(para)
+msgid "You might want to run the <command>yum update</command> command."
+msgstr ""
+
+#: en_US/style.xml:1700(title)
+msgid "Correct: Active voice"
+msgstr "Korrekt: Aktive Sätze "
+
+#: en_US/style.xml:1701(para)
+msgid "Run the <command>yum update</command> command."
+msgstr "Führe den Befehl <command>yum update</command> aus."
+
+#: en_US/style.xml:1708(title)
+msgid "Present Tense"
+msgstr "Präsens Zeit"
+
+#: en_US/style.xml:1709(para)
+msgid "Write in the present tense. A good rule of thumb is that the words \"will\" and \"shall\" are almost never needed in describing what the user should do or see. They add unnecessary length to sentences and can confuse translators. They are also often indicators of passive voice; refer also to <xref linkend=\"sn-misc-active-voice\"/>."
+msgstr ""
+
+#: en_US/style.xml:1718(title)
+msgid "Incorrect: Future tense"
+msgstr "Unkorrekt: Zukunft"
+
+#: en_US/style.xml:1719(para)
+msgid "The application will display a list of target files."
+msgstr "Diese Anwendung zeigt eine Liste mit den Ziel-Dateien an."
+
+#: en_US/style.xml:1722(para)
+msgid "A list of target files will be displayed by the application."
+msgstr ""
+
+#: en_US/style.xml:1727(title)
+msgid "Correct: Present tense"
+msgstr "Korrekt: Präsens"
+
+#: en_US/style.xml:1728(para)
+msgid "The application displays a list of target files."
+msgstr ""
+
+#: en_US/style.xml:1735(title)
+msgid "Narrative Voice"
+msgstr "Erzählende Stimme"
+
+#: en_US/style.xml:1736(para)
+msgid "Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself the writer (whether including the reader or not), the Fedora Documentation Project, the Fedora community, or any other group. Do not refer to users with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word \"one.\" It is acceptable to refer to the reader with the second person pronoun \"you.\""
+msgstr ""
+
+#: en_US/style.xml:1745(title)
+msgid "Incorrect: First or third person"
+msgstr "Inkorrekt: Erste oder dritte Person"
+
+#: en_US/style.xml:1746(para)
+msgid "As described in the last section, I always run <command>up2date</command> before configuring the Samba server."
+msgstr ""
+
+#: en_US/style.xml:1751(para)
+msgid "If the user needs to back up his or her files, s/he should use the <command>tar</command> or <command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1757(title)
+msgid "Correct: Second (or no) person"
+msgstr "Korrekt: Zweite (oder keine) Person"
+
+#: en_US/style.xml:1758(para)
+msgid "Refer to the section on <command>up2date</command> before configuring the Samba server."
+msgstr ""
+
+#: en_US/style.xml:1762(para)
+msgid "If necessary, users can back up files with the <command>tar</command> or <command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1770(title)
+msgid "Negative Words"
+msgstr "Negative Worten"
+
+#: en_US/style.xml:1771(para)
+msgid "Avoid negative words when possible, since they give documentation an overly dogmatic tone. The word \"avoid\" is useful for this purpose. Note that contractions are often used for negative words such as <emphasis>don't</emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-contractions\"/>."
+msgstr ""
+
+#: en_US/style.xml:1782(title)
+msgid "Uncertainty"
+msgstr "Unsicherheit"
+
+#: en_US/style.xml:1783(para)
+msgid "Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the like. While occasional use of these constructions is acceptable, overuse reduces the authority of your documentation. The documentation should adequately cover a stock installation of Fedora. It is impossible for a tutorial-length document to cover every possible configuration scenario. Address the most common scenarios and note discrepancies only as required."
+msgstr ""
+
+#: en_US/style.xml:1795(title)
+msgid "Redundant Coverage"
+msgstr "Redundante Abdeckung"
+
+#: en_US/style.xml:1796(para)
+msgid "Avoid covering redundant material, such as how to update a Fedora system. These overarching topics may be covered in other tutorials. Writers frequently violate this guideline because they feel their tutorial is not long enough. Keep your tutorial from wandering off-topic. Instead, refer the reader to a separate tutorial whenever possible for complete coverage of that topic."
+msgstr ""
+
+#: en_US/style.xml:1808(title)
+msgid "Self-referential Value Judgments"
+msgstr ""
+
+#: en_US/style.xml:1809(para)
+msgid "Avoid statements such as \"One of the most important things to do is <replaceable>XYZ</replaceable>.\" If the procedure is important, the reader already expects it to be in your tutorial. The converse is also true: If a procedure appears in your tutorial, the reader expects it is important. This is especially true if you use a whole section for the procedure in question. Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as required. If the whole section concerns how to do <replaceable>XYZ</replaceable>, leave this sentence out entirely. Refer also to <xref linkend=\"vle-golden-rule-4\"/>."
+msgstr ""
+
+#: en_US/style.xml:1824(title)
+msgid "Precision of Language"
+msgstr "Präzise Sprache"
+
+#: en_US/style.xml:1825(para)
+msgid "Use precise words for actions users should take. Do not instruct users to \"go\" to a selection, or \"find\" a menu."
+msgstr ""
+
+#: en_US/style.xml:1830(title)
+msgid "Incorrect: Imprecise wording"
+msgstr "Unkorrekt: Unpräzise Ausdrücke"
+
+#: en_US/style.xml:1833(para)
+msgid "Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</guimenuitem>"
+msgstr ""
+
+#: en_US/style.xml:1839(para)
+msgid "Find the option labeled <guilabel>Search</guilabel>"
+msgstr ""
+
+#: en_US/style.xml:1846(title)
+msgid "Correct: Precise wording"
+msgstr "Korrekt: Präzise Sprache"
+
+#: en_US/style.xml:1849(para)
+msgid "From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</guimenuitem>"
+msgstr "Selektieren sie <guimenuitem>Foobar</guimenuitem> vom <guimenu>Main Menu</guimenu>."
+
+#: en_US/style.xml:1855(para)
+msgid "Select the <guilabel>Search</guilabel> option"
+msgstr "Wähle die <guilabel>Such</guilabel> Option"
+
+#: en_US/style.xml:1862(title)
+msgid "Do Not Discriminate Against Non-GUI Users"
+msgstr ""
+
+#: en_US/style.xml:1863(para)
+msgid "If you are writing about a GUI-only application, you may use \"click\" freely. If you are writing about an application that has a text-mode interface, use \"select\" instead as shown above."
+msgstr ""
+
+#: en_US/style.xml:1874(title)
+msgid "DocBook Tips"
+msgstr "DocBook Tipps"
+
+#: en_US/style.xml:1875(para)
+msgid "This section contains tips on how to use DocBook tags more effectively in your documentation."
+msgstr "Dieses Kapitel enthält Tips wie sie die Docbook Tags in ihrer Dokumentation viel effektiver nutzen können. "
+
+#: en_US/style.xml:1881(title)
+#: en_US/writing-guidelines.xml:268(title)
+msgid "Admonitions"
+msgstr "Warnungen"
+
+#: en_US/style.xml:1882(para)
+msgid "Avoid overuse of admonitions. Keep admonitions short and effective by using only the most important material inside the admonition. Move any background material required to explain the admonition statements outside the admonition. Use a short but descriptive title for an admonition. Use title case for the admonition title."
+msgstr ""
+
+#: en_US/style.xml:1891(title)
+msgid "Incorrect: Lengthy admonition"
+msgstr "Inkorrekt: Lange Mahnung"
+
+#: en_US/style.xml:1894(title)
+msgid "Use <command>sfdisk</command> to check input"
+msgstr "Benutzen sie den <command>sfdisk</command> Befehl um die Eingabe zu überprüfen."
+
+#: en_US/style.xml:1895(para)
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1909(title)
+msgid "Correct: Brief admonition"
+msgstr "Korrekt: Kurze Mahnung"
+
+#: en_US/style.xml:1917(title)
+msgid "Check Input"
+msgstr "Eingabe-Methoden"
+
+#: en_US/style.xml:1918(para)
+msgid "Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1910(para)
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. <placeholder-1/>"
+msgstr ""
+
+#: en_US/style.xml:1925(para)
+msgid "Avoid punctuation in titles for sections or admonitions, except for commas only where demanded. Use a title that says something about the admonition comment, such as \"Reboot Required,\" instead of simply using the admonition type for a title (\"Note\")."
+msgstr ""
+
+#: en_US/style.xml:1932(para)
+msgid "Follow the capitalization rules for headings in the title of an admonition."
+msgstr ""
+
+#: en_US/style.xml:1939(title)
+msgid "The <sgmltag class=\"starttag\">replaceable</sgmltag> Tag"
+msgstr ""
+
+#: en_US/style.xml:1941(para)
+msgid "If your documentation formally states a specific value will be used as a convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag in your text or examples."
+msgstr ""
+
+#: en_US/style.xml:1950(title)
+msgid "XML Entities"
+msgstr "XML-Entität"
+
+#: en_US/style.xml:1951(para)
+msgid "Use the entities provided by the Fedora Documentation Project. These entities are found in the <filename>common/</filename> folder in the <filename>fedora-docs</filename> distribution. (Refer also to <xref linkend=\"ch-getting-files\"/>.) For instance, do not use abbreviations such as \"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" which produces the text \"Fedora 7.\""
+msgstr ""
+
+#: en_US/writing-guidelines.xml:11(title)
+msgid "Fedora Documentation Guidelines"
+msgstr "Fedora Dokumentation Anleitung"
+
+#: en_US/writing-guidelines.xml:14(primary)
+#: en_US/writing-guidelines.xml:15(see)
+msgid "recursion"
+msgstr "Rekursion"
+
+#: en_US/writing-guidelines.xml:19(primary)
+#: en_US/writing-guidelines.xml:26(secondary)
+msgid "RTFM"
+msgstr "RTFM"
+
+#: en_US/writing-guidelines.xml:20(secondary)
+msgid "read the fine manual"
+msgstr "Lesen das Handbuch"
+
+#: en_US/writing-guidelines.xml:21(seealso)
+#: en_US/writing-guidelines.xml:25(primary)
+msgid "humor"
+msgstr "Humor"
+
+#: en_US/writing-guidelines.xml:29(para)
+msgid "Please read this chapter carefully. This chapter describes the guidelines that must be followed such as naming conventions."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:32(para)
+msgid "This chapter only discusses tags used for documentation for the Fedora Project, not all available DocBook XML tags. For the complete list, refer to <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:38(title)
+msgid "File Header"
+msgstr "Datei Header"
+
+#: en_US/writing-guidelines.xml:40(title)
+msgid "XML Header"
+msgstr "XML Header"
+
+#: en_US/writing-guidelines.xml:41(para)
+msgid "In accordance with good XML practices, the first line in any DocBook XML source files should identify the file as XML. Use the following line as the first line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:47(title)
+msgid "CVS Id Header"
+msgstr "CVS Id Header"
+
+#: en_US/writing-guidelines.xml:48(para)
+msgid "All the files must contain the CVS Id header. Use the following line as the second line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:51(para)
+msgid "Any time the file is committed to CVS, the line is updated automatically to include information about the file. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:58(title)
+msgid "ID Naming Conventions"
+msgstr "ID Benennungs-Konventionen"
+
+#: en_US/writing-guidelines.xml:61(primary)
+#: en_US/writing-guidelines.xml:74(primary)
+#: en_US/writing-guidelines.xml:275(primary)
+#: en_US/writing-guidelines.xml:280(primary)
+#: en_US/writing-guidelines.xml:285(primary)
+#: en_US/writing-guidelines.xml:290(primary)
+#: en_US/writing-guidelines.xml:295(primary)
+#: en_US/writing-guidelines.xml:300(primary)
+#: en_US/writing-guidelines.xml:306(primary)
+#: en_US/writing-guidelines.xml:312(primary)
+#: en_US/writing-guidelines.xml:318(primary)
+#: en_US/writing-guidelines.xml:324(primary)
+#: en_US/writing-guidelines.xml:350(primary)
+#: en_US/writing-guidelines.xml:355(primary)
+#: en_US/writing-guidelines.xml:360(primary)
+#: en_US/writing-guidelines.xml:365(primary)
+#: en_US/writing-guidelines.xml:370(primary)
+msgid "XML tags"
+msgstr "XML Tags"
+
+#: en_US/writing-guidelines.xml:62(secondary)
+#: en_US/writing-guidelines.xml:66(primary)
+#: en_US/writing-guidelines.xml:79(primary)
+msgid "naming conventions"
+msgstr "Benennungs-Konventionen"
+
+#: en_US/writing-guidelines.xml:69(para)
+msgid "This section explains the ID naming convention. IDs are unique identifiers that allow DocBook XML to cross-reference a section, chapter, or other element."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:75(secondary)
+#: en_US/writing-guidelines.xml:80(secondary)
+msgid "rules for defining an ID"
+msgstr "Regeln zum Definieren der ID"
+
+#: en_US/writing-guidelines.xml:83(para)
+msgid "The following general rules apply to IDs:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:87(para)
+msgid "Keep an ID as short and simple as possible."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:90(para)
+msgid "Start the ID with the special short two-character label. This makes URLs and other references to this ID human readable, by self-identifying the XML container type."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:96(para)
+msgid "<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used properly."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:102(title)
+msgid "Proper ID Usage"
+msgstr "Saubere ID Benutzung"
+
+#: en_US/writing-guidelines.xml:111(title)
+#, fuzzy
+msgid "Two-Character Naming Conventions"
+msgstr "Zwei Zeichen Namens Konvention"
+
+#: en_US/writing-guidelines.xml:112(segtitle)
+msgid "Tag"
+msgstr "Tag"
+
+#: en_US/writing-guidelines.xml:113(segtitle)
+msgid "Prefix"
+msgstr "Prefix"
+
+#: en_US/writing-guidelines.xml:115(sgmltag)
+msgid "preface"
+msgstr "Vorwort"
+
+#: en_US/writing-guidelines.xml:116(literal)
+msgid "pr-"
+msgstr "pr-"
+
+#: en_US/writing-guidelines.xml:119(sgmltag)
+msgid "chapter"
+msgstr "Kapitel"
+
+#: en_US/writing-guidelines.xml:120(literal)
+msgid "ch-"
+msgstr "ch-"
+
+#: en_US/writing-guidelines.xml:123(sgmltag)
+msgid "section"
+msgstr "Abschnitt"
+
+#: en_US/writing-guidelines.xml:124(literal)
+msgid "sn-"
+msgstr "sn-"
+
+#: en_US/writing-guidelines.xml:127(sgmltag)
+msgid "figure"
+msgstr "Zeichnung"
+
+#: en_US/writing-guidelines.xml:128(literal)
+msgid "fig-"
+msgstr "fig-"
+
+#: en_US/writing-guidelines.xml:131(sgmltag)
+#: en_US/writing-guidelines.xml:235(sgmltag)
+msgid "table"
+msgstr "Tabelle"
+
+#: en_US/writing-guidelines.xml:132(literal)
+msgid "tb-"
+msgstr "tb-"
+
+#: en_US/writing-guidelines.xml:135(sgmltag)
+msgid "appendix"
+msgstr "Anhang"
+
+#: en_US/writing-guidelines.xml:136(literal)
+msgid "ap-"
+msgstr "ap-"
+
+#: en_US/writing-guidelines.xml:139(sgmltag)
+msgid "part"
+msgstr "Teil"
+
+#: en_US/writing-guidelines.xml:140(literal)
+msgid "pt-"
+msgstr "pt-"
+
+#: en_US/writing-guidelines.xml:143(sgmltag)
+msgid "example"
+msgstr "Beispiel"
+
+#: en_US/writing-guidelines.xml:144(literal)
+msgid "ex-"
+msgstr "ex-"
+
+#: en_US/writing-guidelines.xml:148(para)
+msgid "Use the title of the item as the ID. Make your titles unique within a document to prevent conflicts. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:157(title)
+msgid "XML Tags"
+msgstr "XML Tags"
+
+#: en_US/writing-guidelines.xml:159(primary)
+msgid "xml tags"
+msgstr "xml Tags"
+
+#: en_US/writing-guidelines.xml:160(secondary)
+msgid "caveats"
+msgstr "Vorbehalte"
+
+#: en_US/writing-guidelines.xml:163(para)
+msgid "It is very important that you remember the caveats in this section. These are learned suggestions or rules that make your XML experience better."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:171(term)
+#, fuzzy
+msgid "Do Not Use Trademark Entities"
+msgstr "Benutze keine Trademark Entitäten"
+
+#: en_US/writing-guidelines.xml:173(para)
+msgid "Do not use the trademark entities <sgmltag class=\"genentity\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class=\"genentity\">reg</sgmltag> because the do not produce HTML output that works for all charsets. The HTML output produces by these entities are declared in the DTD and cannot be changed via the stylesheet."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:181(para)
+msgid "Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes as follows:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:184(segtitle)
+msgid "DocBook XML source"
+msgstr "DocBook XML Quelle"
+
+#: en_US/writing-guidelines.xml:185(segtitle)
+msgid "Rendered content"
+msgstr "Gerenderter Inhalt"
+
+#: en_US/writing-guidelines.xml:189(trademark)
+msgid "trademark symbol after me"
+msgstr "Trademark-Symbol nach mir"
+
+#: en_US/writing-guidelines.xml:196(trademark)
+msgid "registered trademark symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:202(trademark)
+msgid "copyright symbol after me"
+msgstr "Copyright-Symbol nach mir"
+
+#: en_US/writing-guidelines.xml:209(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr "Inhalt innerhalb <sgmltag>para</sgmltag> Tags"
+
+#: en_US/writing-guidelines.xml:211(para)
+msgid "In general, use <sgmltag>para</sgmltag> tags around anything other than a simple paragraph. Doing so will create additional white space within the text itself in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:216(para)
+msgid "Specifically, do not use <sgmltag>para</sgmltag> tags around the following (or, to put this another way, do not embed the following within <sgmltag class=\"element\">para</sgmltag> elements):"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:223(sgmltag)
+msgid "screen"
+msgstr "Bildschirm"
+
+#: en_US/writing-guidelines.xml:226(sgmltag)
+msgid "itemizedlist"
+msgstr "itemizedlist"
+
+#: en_US/writing-guidelines.xml:229(sgmltag)
+msgid "orderedlist"
+msgstr "orderedlist"
+
+#: en_US/writing-guidelines.xml:232(sgmltag)
+msgid "variablelist"
+msgstr "variablelist"
+
+#: en_US/writing-guidelines.xml:241(term)
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag>listitem</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:244(para)
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</emphasis> start immediately after the beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:252(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:254(para)
+msgid "The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) <emphasis>must</emphasis> be flush left in the XML file; otherwise, the extraneous whitespace will appear in the HTML version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:301(secondary)
+#: en_US/writing-guidelines.xml:307(secondary)
+#: en_US/writing-guidelines.xml:313(secondary)
+#: en_US/writing-guidelines.xml:319(secondary)
+#: en_US/writing-guidelines.xml:325(secondary)
+msgid "admonitions"
+msgstr "Warnungen"
+
+#: en_US/writing-guidelines.xml:276(secondary)
+#: en_US/writing-guidelines.xml:302(tertiary)
+#: en_US/writing-guidelines.xml:371(secondary)
+msgid "warning"
+msgstr "Warnung"
+
+#: en_US/writing-guidelines.xml:281(secondary)
+#: en_US/writing-guidelines.xml:308(tertiary)
+#: en_US/writing-guidelines.xml:356(secondary)
+msgid "tip"
+msgstr "Tipp"
+
+#: en_US/writing-guidelines.xml:286(secondary)
+#: en_US/writing-guidelines.xml:314(tertiary)
+#: en_US/writing-guidelines.xml:351(secondary)
+msgid "note"
+msgstr "Notiz"
+
+#: en_US/writing-guidelines.xml:291(secondary)
+#: en_US/writing-guidelines.xml:320(tertiary)
+#: en_US/writing-guidelines.xml:361(secondary)
+msgid "caution"
+msgstr "Vorsicht"
+
+#: en_US/writing-guidelines.xml:296(secondary)
+#: en_US/writing-guidelines.xml:326(tertiary)
+#: en_US/writing-guidelines.xml:366(secondary)
+msgid "important"
+msgstr "wichtig"
+
+#: en_US/writing-guidelines.xml:329(para)
+msgid "There are five types of admonitions in DocBook: <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the admonitions have the same structure: an optional <sgmltag class=\"element\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD does not impose any specific semantics on the individual admonitions. For example, DocBook does not mandate that a <sgmltag class=\"element\">warning</sgmltag> is reserved for cases where bodily harm can result."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:343(title)
+msgid "Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element\">warning</sgmltag>"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:374(para)
+msgid "There are several ways to bring attention to text within a document. A <emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to bring additional information to the users' attention. A <emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful information or another way to do something. A <emphasis><sgmltag class=\"element\">caution</sgmltag></emphasis> is used to show the user they must be careful when attempting a certain step. An <emphasis><sgmltag class=\"element\">important</sgmltag></emphasis> tag set can be used to show the user a piece of information that should not be overlooked. While this information may not change anything the user is doing, it should show the user that this piece of information could be vital. A <emphasis><sgmltag class=\"element\">warning</sgmltag></emphasis> is used to show the reader that their current setup will change or be altered, such as files being removed, and they should not c
hoose this operation unless they are alright with the consequences."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:394(para)
+msgid "The following lines of code show the basic setup for each case mentioned above, along with its appearance in HTML."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:403(title)
+#: en_US/emacs.xml:257(title)
+#: en_US/emacs.xml:562(title)
+#: en_US/emacs-nxml.xml:160(title)
+msgid "Note"
+msgstr "Notiz"
+
+#: en_US/writing-guidelines.xml:404(para)
+#: en_US/writing-guidelines.xml:424(para)
+#: en_US/writing-guidelines.xml:434(para)
+#: en_US/writing-guidelines.xml:444(para)
+msgid "Body of text goes here."
+msgstr "Hierher kommt der Textkörper"
+
+#: en_US/writing-guidelines.xml:413(title)
+#: en_US/emacs-nxml.xml:114(title)
+msgid "Tip"
+msgstr "Tipp"
+
+#: en_US/writing-guidelines.xml:414(para)
+msgid "Body of text goes here"
+msgstr "Hierher kommt der Textkörper"
+
+#: en_US/writing-guidelines.xml:423(title)
+msgid "Caution"
+msgstr "Vorsicht"
+
+#: en_US/writing-guidelines.xml:433(title)
+#: en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr "Wichtig"
+
+#: en_US/writing-guidelines.xml:443(title)
+msgid "Warning"
+msgstr "Warnung"
+
+#: en_US/writing-guidelines.xml:451(title)
+msgid "Screenshots"
+msgstr "Screenshots"
+
+#: en_US/writing-guidelines.xml:454(primary)
+#: en_US/writing-guidelines.xml:459(see)
+#: en_US/writing-guidelines.xml:463(see)
+msgid "screenshots"
+msgstr "Screenshots"
+
+#: en_US/writing-guidelines.xml:455(secondary)
+msgid "how to take"
+msgstr "wie nehmen?"
+
+#: en_US/writing-guidelines.xml:458(primary)
+msgid "screen captures"
+msgstr "Bildschirmfotos"
+
+#: en_US/writing-guidelines.xml:462(primary)
+msgid "screen grabs"
+msgstr "Bildschirm-Abzüge"
+
+#: en_US/writing-guidelines.xml:466(para)
+msgid "Screenshots are illustrations that show the state of a display the user may encounter. Screenshots can be either graphical or textual. However, screenshots use a great deal of space in a text document to convey relatively small amounts of information. The same space in the document can hold a greater amount of more descriptive and helpful information. Therefore, authors should avoid screenshots whenever possible in favor of descriptive text."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:474(para)
+msgid "One of the isolated instances in which screenshots are useful is to demonstrate a physical screen layout that is unfamiliar to a reader. <emphasis>This does not mean that illustrations of dialog boxes are good uses of screenshots.</emphasis> On the contrary, dialogs are simply instances of a user interface element with which a reader is already familiar. An annotated diagram in certain cases, however, explains to the reader where to find functional landmarks on the screen such as menu bars."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:482(para)
+msgid "The steps for taking a graphical screenshot illustrate how using text to describe a procedure is more concise than a series of screenshots."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:487(term)
+msgid "Graphical Screenshot"
+msgstr "Graphisches Bildschirmfoto"
+
+#: en_US/writing-guidelines.xml:491(para)
+msgid "Create a new user account to make screenshots. The new account uses the distribution default theme, fonts, and element sizes. The resulting screenshot has an appearance familiar to the largest number of readers, and makes Fedora Documentation Project documents consistent."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:498(para)
+msgid "Before taking the screenshot, if possible, resize the targeted GUI element(s) to the smallest possible size. The target image should be 500 pixels wide or less. If the screenshot includes more than one GUI element, you may need to resize the screenshot in a following step."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:506(para)
+msgid "To take the screenshot, select the GUI element with the mouse to bring it to the forefront, or otherwise arrange the elements. Press <keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to capture a single GUI window. For capturing the entire desktop use <keycap>Print Screen</keycap>. If the shot includes multiple elements grouped closely together, crop the resulting PNG format image in <application>The GIMP</application>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:518(para)
+msgid "If necessary, resize the image using <application>The GIMP</application>. Open the image, then right-click on it and choose <menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</guimenuitem></menuchoice>. With the chain symbol intact, set the <guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click <guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the image before converting it."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:534(para)
+msgid "With the image open in <application>The GIMP</application>, right-click the image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As...</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</guibutton>. Allow flattening of the image by clicking <guibutton>Export</guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:545(para)
+msgid "A <guilabel>Save as PostScript</guilabel> window appears. Select <guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:559(term)
+msgid "Text Screenshot"
+msgstr "Text-Bildschirmfoto"
+
+#: en_US/writing-guidelines.xml:561(para)
+msgid "Textual screen information is also useful for readers. Follow these guidelines for textual screenshots:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:565(para)
+msgid "If a graphical screenshot illustrates a function, and the textual mode has identical functions, do not include both, unless omitting either would make your description unclear."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:571(para)
+msgid "Make the information generic over specific, and omit any username and machine information if possible. Do not include the shell prompt unless it is vital to the demonstration."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:577(para)
+#, fuzzy
+msgid "Separate what the user types from sample command output."
+msgstr "Seperieren sie die Usertypen von der Ausgabe des Beispiel Befehls."
+
+#: en_US/writing-guidelines.xml:581(para)
+msgid "When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show what the user types, and use <sgmltag class=\"element\">computeroutput</sgmltag> tags to show the resulting output."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:589(para)
+msgid "<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual screenshot usage."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:594(title)
+msgid "Correct Textual Screenshot (XML Source and HTML)"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:607(para)
+msgid "To find all the currently active ssh sessions, execute the following command:"
+msgstr "Um alle derzeit aktiven SSH Sessions zu finden führen sie den folgenden Befehl aus:"
+
+#: en_US/writing-guidelines.xml:609(userinput)
+#, no-wrap
+msgid "ps ax | grep ssh"
+msgstr "ps ax | grep ssh"
+
+#: en_US/writing-guidelines.xml:611(para)
+msgid "Output appears similar to the following:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:613(computeroutput)
+#, no-wrap
+msgid ""
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh user@@host.example.com\n"
+" 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+msgstr ""
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh user@@host.example.com\n"
+" 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+
+#: en_US/module-struct.xml:12(title)
+msgid "How Modules Work"
+msgstr "Wie Module arbeiten"
+
+#: en_US/module-struct.xml:13(para)
+msgid "Documentation modules have a specific structure that enables the preconfigured tools to work correctly. Follow this structure exactly or you may have problems building your module. The Fedora Documentation Project build tools locate resources in the module and use them to build new output such as HTML or RPM packages."
+msgstr ""
+
+#: en_US/module-struct.xml:19(title)
+msgid "Structure of a Module"
+msgstr "Struktur eines Moduls"
+
+#: en_US/module-struct.xml:20(para)
+msgid "<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example module, excluding any <filename class=\"directory\">CVS</filename> folders. Note that this example document does not have branches."
+msgstr ""
+
+#: en_US/module-struct.xml:25(title)
+msgid "Example Module Structure"
+msgstr "Beispiel Modul Struktur"
+
+#: en_US/module-struct.xml:47(title)
+msgid "CVS Module Contents"
+msgstr "CVS Modul Inhalte"
+
+#: en_US/module-struct.xml:48(segtitle)
+msgid "Component"
+msgstr "Komponente"
+
+#: en_US/module-struct.xml:49(segtitle)
+msgid "Type"
+msgstr "Typ"
+
+#: en_US/module-struct.xml:50(segtitle)
+msgid "Usage Notes"
+msgstr "Benutze Notizen"
+
+#: en_US/module-struct.xml:52(seg)
+msgid "Primary language directory"
+msgstr "Primäres Sprach-Verzeichnis"
+
+#: en_US/module-struct.xml:53(seg)
+#: en_US/module-struct.xml:94(seg)
+#: en_US/module-struct.xml:101(seg)
+msgid "required"
+msgstr "benötigt"
+
+#: en_US/module-struct.xml:56(filename)
+#: en_US/module-struct.xml:181(systemitem)
+msgid "en_US"
+msgstr "en_US"
+
+#: en_US/module-struct.xml:60(firstterm)
+msgid "entities"
+msgstr "Entitäten"
+
+#: en_US/module-struct.xml:61(para)
+msgid "Think of an XML entity as a predefined snippet of information. It can represent a chunk of XML source, or simply a word or character. If the information changes, it need be replaced only once, in the definition, to fix all usage."
+msgstr ""
+
+#: en_US/module-struct.xml:54(seg)
+msgid "This is the only directory absolutely required. It is named for the original language of the document, such as <placeholder-1/> (US English). The primary language does not have to be US English; all languages are supported. This directory contains all the XML source for the actual document, as well as XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr ""
+
+#: en_US/module-struct.xml:69(seg)
+msgid "Graphics directory"
+msgstr "Grafiken-Verzeichnis"
+
+#: en_US/module-struct.xml:70(seg)
+#: en_US/module-struct.xml:80(seg)
+msgid "optional"
+msgstr "optional"
+
+#: en_US/module-struct.xml:71(filename)
+#: en_US/module-struct.xml:75(filename)
+msgid "figs/"
+msgstr "figs/"
+
+#: en_US/module-struct.xml:71(seg)
+msgid "The <placeholder-1/> directory is an optional directory where graphics for the document should be stored. If graphics are screenshots that are particular to a language, the <placeholder-2/> directory can and should be stored in a language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:79(seg)
+msgid "Translation (PO) directory"
+msgstr "Übersetzung (PO) Verzeichnis"
+
+#: en_US/module-struct.xml:81(filename)
+#: en_US/module-struct.xml:87(filename)
+msgid "po/"
+msgstr "po/"
+
+#: en_US/module-struct.xml:83(acronym)
+msgid "PO"
+msgstr "PO"
+
+#: en_US/module-struct.xml:88(filename)
+msgid "LINGUAS"
+msgstr "LINGUAS"
+
+#: en_US/module-struct.xml:89(firstterm)
+msgid "locales"
+msgstr "Regionen"
+
+#: en_US/module-struct.xml:81(seg)
+msgid "The <placeholder-1/> directory contains specially formatted Portable Object, or <placeholder-2/>, files created and used by translators. The Fedora Documentation Project build tools use these files to create translated versions of documents. The translated documents are not stored in CVS; they are created as needed from these PO files. The <placeholder-3/> directory also contains the <placeholder-4/> file, which lists the active translation <placeholder-5/>, or languages."
+msgstr ""
+
+#: en_US/module-struct.xml:93(seg)
+#: en_US/module-struct.xml:95(filename)
+msgid "Makefile"
+msgstr "Makefile"
+
+#: en_US/module-struct.xml:95(seg)
+msgid "The <placeholder-1/> controls the build process. Its content is discussed in <xref linkend=\"ex-makefile\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:100(filename)
+#: en_US/module-struct.xml:102(filename)
+msgid "rpm-info.xml"
+msgstr "rpm-info.xml"
+
+#: en_US/module-struct.xml:102(seg)
+msgid "The <placeholder-1/> file contains document specific metadata"
+msgstr ""
+
+#: en_US/module-struct.xml:107(title)
+msgid "Common Build Tools"
+msgstr "Allgemeine Build Werkzeuge"
+
+#: en_US/module-struct.xml:108(para)
+msgid "Never add the <systemitem>docs-common</systemitem> build tools directory to an individual module. Special formatting in the module list downloads these tools when a user checks out a document module. For more information, refer to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:116(title)
+msgid "The Document Build System"
+msgstr "Das Dokument Build System"
+
+#: en_US/module-struct.xml:121(para)
+msgid "In Linux and Fedora documentation, references to commands often include a number inside parentheses. This number represents the section of <firstterm>manpages</firstterm> that includes documentation for that command. To read the manpage for <command>make(1)</command>, use the command <command>man 1 make</command>."
+msgstr ""
+
+#: en_US/module-struct.xml:117(para)
+msgid "The build system can render the document into another format such as <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</command><placeholder-1/> and shell scripts. Authors need <emphasis>no</emphasis> prior experience with either shell scripts or a <command>make(1)</command>."
+msgstr ""
+
+#: en_US/module-struct.xml:133(title)
+msgid "The Document <filename>Makefile</filename>"
+msgstr "Das Dokument <filename>Makefile</filename>"
+
+#: en_US/module-struct.xml:134(para)
+msgid "Each individual document has its own <filename>Makefile</filename>, which only needs to be a few lines long. The document <filename>Makefile</filename> content is designed for cut and paste operations."
+msgstr ""
+
+#: en_US/module-struct.xml:140(para)
+msgid "<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</filename> for a simple document with two files and two translations."
+msgstr ""
+
+#: en_US/module-struct.xml:146(title)
+msgid "Sample Document Makefile"
+msgstr "Beispiel Dokument Makefile"
+
+#: en_US/module-struct.xml:162(para)
+msgid "Do not be concerned with some of the more complicated syntax such as the <command>XMLFILES_template</command> stanza. An explanation for this template appears a few paragraphs below."
+msgstr ""
+
+#: en_US/module-struct.xml:168(title)
+msgid "Makefile Variables"
+msgstr "Makefile Variablen"
+
+#: en_US/module-struct.xml:169(segtitle)
+msgid "Variable"
+msgstr "Variable"
+
+#: en_US/module-struct.xml:170(segtitle)
+#: en_US/module-struct.xml:240(segtitle)
+msgid "Explanation"
+msgstr "Erklärung"
+
+#: en_US/module-struct.xml:172(systemitem)
+msgid "DOCBASE"
+msgstr "DOCBASE"
+
+#: en_US/module-struct.xml:173(seg)
+msgid "This variable contains the name for the main (parent) XML document. Follow convention by naming your document after the module name."
+msgstr ""
+
+#: en_US/module-struct.xml:178(systemitem)
+msgid "PRI_LANG"
+msgstr "PRI_LANG"
+
+#: en_US/module-struct.xml:179(seg)
+msgid "This variable contains the ISO code for the original version of the document, such as <placeholder-1/>."
+msgstr ""
+
+#: en_US/module-struct.xml:184(systemitem)
+msgid "DOC_ENTITIES"
+msgstr "DOC_ENTITIES"
+
+#: en_US/module-struct.xml:185(seg)
+msgid "This variable contains a listing of any files containing entity definitions. The Fedora Documentation Project uses a special XML format to record document-specific entities, so they can be translated and built on the fly like any other XML document. An example is shown later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:194(systemitem)
+msgid "XMLFILES_template"
+msgstr "XMLFILES_template"
+
+#: en_US/module-struct.xml:197(systemitem)
+msgid "${1}"
+msgstr "${1}"
+
+#: en_US/module-struct.xml:202(systemitem)
+msgid "${1}/"
+msgstr "${1}/"
+
+#: en_US/module-struct.xml:195(seg)
+msgid "This template allows the build tools to work with the document in multiple languages once it is translated. The <placeholder-1/> marking is a variable used to substitute the appropriate language. This template is not terribly complicated. For a new module, duplicate this section exactly except for the actual filenames. Prepend the text <placeholder-2/>, in place of the language code directory name, to each filename in your document."
+msgstr ""
+
+#: en_US/module-struct.xml:208(title)
+#, fuzzy
+msgid "Files Exempt From Listing"
+msgstr "Aufrug: %s von nach Dateien...\n"
+
+#: en_US/module-struct.xml:209(para)
+msgid "Do not include the document-specific entities XML file or the <filename>rpm-info.xml</filename> file, which will be discussed later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:213(para)
+msgid "The final section, beginning with <literal>define</literal>, locates the main <filename>Makefile.common</filename> for the build system. This <filename>Makefile.common</filename> file contains all the <application>make(1)</application> targets and rules to actually build the document and the various archives."
+msgstr ""
+
+#: en_US/module-struct.xml:222(title)
+msgid "The Document <filename>rpm-info.xml</filename>"
+msgstr ""
+
+#: en_US/module-struct.xml:223(para)
+msgid "Each document module's primary language directory contains a file called <filename>rpm-info.xml</filename>. This file contains document-specific metadata used to generate revision history, copyright, and contributor information. It follows a DTD specification included with the rest of the build system tools."
+msgstr ""
+
+#: en_US/module-struct.xml:232(title)
+msgid "Build System Actions"
+msgstr "Build-System Aktionen"
+
+#: en_US/module-struct.xml:233(para)
+msgid "To render the <abbrev>XML</abbrev> document into another format, use one of the following <command>make</command> targets:"
+msgstr ""
+
+#: en_US/module-struct.xml:238(title)
+msgid "Build Targets"
+msgstr "Build Ziel"
+
+#: en_US/module-struct.xml:239(segtitle)
+msgid "Target"
+msgstr "Ziel"
+
+#: en_US/module-struct.xml:242(systemitem)
+msgid "html"
+msgstr "html"
+
+#: en_US/module-struct.xml:243(abbrev)
+#: en_US/module-struct.xml:254(abbrev)
+#: en_US/module-struct.xml:279(abbrev)
+#: en_US/module-struct.xml:284(abbrev)
+msgid "HTML"
+msgstr "HTML"
+
+#: en_US/module-struct.xml:247(systemitem)
+#: en_US/module-struct.xml:257(systemitem)
+msgid "${DOCBASE}"
+msgstr "${DOCBASE}"
+
+#: en_US/module-struct.xml:248(systemitem)
+#: en_US/module-struct.xml:258(systemitem)
+msgid "${LANG}"
+msgstr "${LANG}"
+
+#: en_US/module-struct.xml:246(filename)
+msgid "<placeholder-1/>-<placeholder-2/>/"
+msgstr "<placeholder-1/>-<placeholder-2/>/"
+
+#: en_US/module-struct.xml:243(seg)
+msgid "This target builds the \"chunked\" <placeholder-1/> document for each defined translation. Output is placed in a separate directory named <placeholder-2/>. Each document section is a separate file within that directory."
+msgstr ""
+
+#: en_US/module-struct.xml:253(systemitem)
+msgid "html-nochunks"
+msgstr "html-nochunks"
+
+#: en_US/module-struct.xml:256(filename)
+msgid "<placeholder-1/>-<placeholder-2/>.html"
+msgstr "<placeholder-1/>-<placeholder-2/>.html"
+
+#: en_US/module-struct.xml:254(seg)
+msgid "This target builds the \"non-chunked\" <placeholder-1/> document for each defined translation. Output is placed in a single file: <placeholder-2/>; no other files are created."
+msgstr ""
+
+#: en_US/module-struct.xml:262(systemitem)
+msgid "pdf"
+msgstr "pdf"
+
+#: en_US/module-struct.xml:263(abbrev)
+#: en_US/module-struct.xml:264(abbrev)
+#: en_US/module-struct.xml:280(abbrev)
+#: en_US/module-struct.xml:285(abbrev)
+msgid "PDF"
+msgstr "PDF"
+
+#: en_US/module-struct.xml:263(seg)
+msgid "This target builds only the <placeholder-1/> document for all document languages. <placeholder-2/> production is currently erratic and may not work for your document."
+msgstr ""
+
+#: en_US/module-struct.xml:268(systemitem)
+msgid "tarball"
+msgstr "tarball"
+
+#: en_US/module-struct.xml:269(command)
+msgid "tar(1)"
+msgstr "tar(1)"
+
+#: en_US/module-struct.xml:269(seg)
+msgid "This target builds only the <placeholder-1/> archive for all document languages."
+msgstr ""
+
+#: en_US/module-struct.xml:273(systemitem)
+msgid "all"
+msgstr "all"
+
+#: en_US/module-struct.xml:274(seg)
+#, fuzzy
+msgid "This target builds all targets listed above."
+msgstr "Dieses Ziel baut alle Ziele die darüber gelistet sind."
+
+#: en_US/module-struct.xml:277(systemitem)
+#: en_US/module-struct.xml:286(filename)
+msgid "clean"
+msgstr "sauber"
+
+#: en_US/module-struct.xml:279(emphasis)
+msgid "not"
+msgstr "not"
+
+#: en_US/module-struct.xml:278(seg)
+msgid "This target deletes any temporary, or generated files, but does <placeholder-1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr ""
+
+#: en_US/module-struct.xml:283(systemitem)
+msgid "distclean"
+msgstr "distclean"
+
+#: en_US/module-struct.xml:284(seg)
+msgid "This target erases all <placeholder-1/>, <placeholder-2/>, and archive files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr ""
+
+#: en_US/module-struct.xml:291(title)
+#, fuzzy
+msgid "PDF Generation is Erratic"
+msgstr "Das Erstellen von PDFs wird nicht unterstützt"
+
+#: en_US/module-struct.xml:292(para)
+msgid "<abbrev>PDF</abbrev> production is currently erratic and may not work for your document."
+msgstr ""
+
+#: en_US/module-struct.xml:296(title)
+msgid "Adding or Changing Targets"
+msgstr "Hinzufügen oder Ändern von Zielen"
+
+#: en_US/module-struct.xml:297(para)
+msgid "To add a new target and rules, place them at the bottom of the document <filename>Makefile</filename>, below the <literal>include</literal> line. Follow your target definitions with a double colon, not a single colon. The double colon allows you to specify additional rules for existing targets, or to write rules for a new target."
+msgstr ""
+
+#: en_US/module-struct.xml:305(para)
+msgid "For more information on using <command>make(1)</command>, consult the online documentation with the command <command>info make</command> in a terminal."
+msgstr ""
+
+#: en_US/module-struct.xml:312(title)
+msgid "Using Document Image Files"
+msgstr "Benutze Dokument Abbild-Dateien"
+
+#: en_US/module-struct.xml:313(para)
+msgid "Tutorial documents often make use of images such as <filename class=\"extension\">.PNG</filename> files. Store image files in a <filename class=\"directory\">figs/</filename> folder in the main module directory, as shown in <xref linkend=\"ex-module-structure\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:320(para)
+msgid "Depending on the output media, sometimes images may be scaled, streteched, or squashed. To minimize any distortions, we recommend that you use only <filename class=\"extension\">.PNG</filename> images. Avoid <filename class=\"extension\">.JPG</filename> files. The <command>convert(1)</command> program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</abbrev> package, provides a convenient way to reformat <filename class=\"extension\">.JPG</filename> images into <filename class=\"extension\">.PNG</filename> format. For more information on formatting images such as screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:334(para)
+msgid "Image files may be organized into subdirectories under <filename>figs/</filename> if necessary. The document building system recreates the image subdirectory structure in the output documents."
+msgstr ""
+
+#: en_US/module-struct.xml:340(para)
+msgid "Images often contain labels or other text which may need to be localized. A screenshot of a program, for example, may require a version for each translated language. Name language-dependent image files such as program screenshots by adding the language code to the filename, such as <filename>menu-en_US.png</filename>. Language-independent images, such as <filename>icon.png</filename>, do not need language codes."
+msgstr ""
+
+#: en_US/module-struct.xml:350(para)
+msgid "Sometimes, a document may require images that do not follow the naming convention. To use these images with the document building system, create an ordinary text file containing the image filenames. This file must be named <filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</systemitem> so the build system finds it when searching for image filenames."
+msgstr ""
+
+#: en_US/module-struct.xml:359(para)
+msgid "<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one way to create this <filename>Manifest</filename> file."
+msgstr ""
+
+#: en_US/module-struct.xml:365(title)
+msgid "Building A Manifest"
+msgstr "Bauen eines Manifests"
+
+#: en_US/module-struct.xml:372(title)
+msgid "Adding a New DocBook XML File"
+msgstr "Hinzufügen einer neuen DocBook XML Datei"
+
+#: en_US/module-struct.xml:373(para)
+msgid "To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:377(para)
+msgid "Place the new DocBook XML file in the primary language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:381(para)
+msgid "Edit the <filename>Makefile</filename> and add the filename to the <varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to the last existing line, and on the next line add an entry for the new file. Remember to add the <literal>${1}/</literal> prefix as a substitute for the language directory name."
+msgstr ""
+
+#: en_US/module-struct.xml:391(title)
+msgid "Adding a Translation"
+msgstr "Eine Übersetzung hinzufügen"
+
+#: en_US/module-struct.xml:392(para)
+msgid "Translations are stored as PO (portable object) files, which the toolchain transforms into translated documents. Each PO file is based on the POT (PO template) for the document and translated by the Fedora Translation Project. To add a translation, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:399(para)
+msgid "If the <filename class=\"directory\">po/</filename> directory does not exist, create it and add it to CVS:"
+msgstr ""
+
+#: en_US/module-struct.xml:405(para)
+msgid "If it does not exist, create the POT file:"
+msgstr "Wenn es nicht exisitiert, erzeuge die POT Datei"
+
+#: en_US/module-struct.xml:409(para)
+msgid "Add the new translation language to the <varname>OTHERS</varname> listing in the <filename>Makefile</filename>."
+msgstr ""
+
+#: en_US/module-struct.xml:414(para)
+msgid "Although translators often copy the POT manually to create the new PO file, the following command also works:"
+msgstr ""
+
+#: en_US/module-struct.xml:417(replaceable)
+msgid "lang"
+msgstr "lang"
+
+#: en_US/module-struct.xml:417(screen)
+#, no-wrap
+msgid "make po/<placeholder-1/>.po"
+msgstr "<placeholder-1/> oder <keycombo><placeholder-2/><placeholder-3/></keycombo>"
+
+#: en_US/intro.xml:13(title)
+msgid "Introduction"
+msgstr "Einleitung"
+
+#: en_US/intro.xml:15(para)
+msgid "The goal of the Fedora Documentation Project is to create easy-to-follow, task-based documentation for Fedora users and developers. The Fedora Documentation Project uses the following tools:"
+msgstr ""
+
+#: en_US/intro.xml:23(para)
+msgid "DocBook XML v4.4"
+msgstr "DocBook XML v4.4"
+
+#: en_US/intro.xml:26(para)
+msgid "Custom XSLT stylesheets for both print and HTML versions"
+msgstr ""
+
+#: en_US/intro.xml:30(para)
+msgid "Custom scripts to generate HTML output (use <command>xmlto</command>)"
+msgstr ""
+
+#: en_US/intro.xml:34(para)
+msgid "Emacs with PSGML mode (optional, but recommended)"
+msgstr ""
+
+#: en_US/intro.xml:43(para)
+msgid "This document explains the tools used by the Fedora Documentation Project. It provides writing and tagging guidelines to ensure Fedora documentation is consistent and easy-to-follow."
+msgstr ""
+
+#: en_US/getting-files.xml:12(title)
+msgid "Prerequisites"
+msgstr "Voraussetzungen"
+
+#: en_US/getting-files.xml:14(para)
+msgid "To work on official Fedora documentation you need to install the required tools. Follow the directions below to configure your system."
+msgstr "Um an den Offiziellen Dokumentationen von Fedora zu arbeiten müssen die verwendeten Werkzeuge installieren. Folgen sie den Anleitungen um ihr System zu konfigurieren."
+
+#: en_US/getting-files.xml:20(title)
+msgid "System Packages"
+msgstr "System Pakete"
+
+#: en_US/getting-files.xml:22(para)
+msgid "Install the \"Authoring and Publishing\" package group, which contains required DocBook XML files, stylesheets and scripts:"
+msgstr ""
+
+#: en_US/getting-files.xml:28(userinput)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+msgstr "su -c 'yum groupinstall \"Schreiben und Publizieren\"'"
+
+#: en_US/getting-files.xml:31(para)
+msgid "Next, install the <filename>cvs</filename> package, which is used to handle revision control on files in the official repository:"
+msgstr ""
+
+#: en_US/getting-files.xml:37(userinput)
+#, no-wrap
+msgid "su -c 'yum install cvs'"
+msgstr "su -c 'yum install cvs'"
+
+#: en_US/getting-files.xml:40(para)
+msgid "If you plan to use <application>Emacs</application> to edit DocBook XML documentation, install <package>psgml</package>, which adds helpful and time-saving functionality to maximize editing efficiency:"
+msgstr ""
+
+#: en_US/getting-files.xml:44(userinput)
+#, no-wrap
+msgid "su -c 'yum install psgml'"
+msgstr "su -c 'yum install psgml'"
+
+#: en_US/getting-files.xml:48(title)
+msgid "Fedora Documentation Tools"
+msgstr "Fedora Dokumentation Werkzeuge"
+
+#: en_US/getting-files.xml:50(para)
+msgid "The Fedora Documentation Project's custom scripts and stylesheets are stored in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</systemitem> CVS server. When you check out a document module from CVS, the tools are included in the module inside the <filename class=\"directory\">docs-common/</filename> directory. To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:59(para)
+msgid "The most powerful component in the Fedora Documentation Project toolbox is <firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for authoring technical documentation using <firstterm>Extensible Markup Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark pieces of content with descriptive tags. The following output is an example of DocBook XML:"
+msgstr ""
+
+#: en_US/getting-files.xml:76(para)
+msgid "This example article, entitled <citetitle>A Very Short Article</citetitle>, consists of only a single paragraph. The tags, or markup, surround elements of content to define the sense in which they are used. A paragraph, for example, is marked with <sgmltag>para</sgmltag> tags. Text that requires emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does not worry about the visual formatting such as italics or font size. Fedora Documentation Project build tools automatically perform all formatting tasks."
+msgstr ""
+
+#: en_US/getting-files.xml:85(para)
+msgid "The custom tools built by the Fedora Documentation Project render DocBook source into a variety of formats for publication and distribution. They also allow translators to create localized versions of the XML documents for Fedora users around the world. The flexibility of XML allows for a single document to be used many times for many purposes, like reusable code for a programmer."
+msgstr ""
+
+#: en_US/getting-files.xml:91(para)
+msgid "DocBook is itself very well documented. For more information about DocBook, visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also features complete copies of <citetitle>DocBook: The Definitive Guide</citetitle> to browse and download, the canonical source for DocBook information."
+msgstr ""
+
+#: en_US/getting-files.xml:97(title)
+msgid "DocBook XML Versions"
+msgstr "DocBook XML Versionen"
+
+#: en_US/getting-files.xml:98(para)
+msgid "DocBook XML, like a computer program, has version numbers. The version used by Fedora Documentation Project right now is 4.4. The DocBook web site may document a slightly newer version, but the majority of the schema still applies."
+msgstr ""
+
+#: en_US/getting-files.xml:106(title)
+msgid "Naming Conventions"
+msgstr "Benennungs-Konventionen"
+
+#: en_US/getting-files.xml:107(para)
+msgid "The Fedora Documentation Project provides the tools, scripts, and stylesheets to transform your <abbrev>XML</abbrev> documents into other output formats such as <abbrev>HTML</abbrev>. In addition, these tools can build your document into a <abbrev>RPM</abbrev> package. To take advantage of these services, follow the conventions in this section to name your files."
+msgstr ""
+
+#: en_US/getting-files.xml:115(para)
+msgid "On the CVS server, directories that contain document files are called <firstterm>modules</firstterm>. Each module represents a single document. Each document may consist of several <firstterm>branches</firstterm> if that document changes with each release of Fedora. Contributors can check out single branches of these modules or the entire module. Each document or branch may contain multiple XML source files."
+msgstr ""
+
+#: en_US/getting-files.xml:122(para)
+msgid "Use the <command>cvs co -c</command> command to view existing module names."
+msgstr ""
+
+#: en_US/getting-files.xml:125(title)
+msgid "Partial List of CVS Modules"
+msgstr "Partielle Liste der CVS Module"
+
+#: en_US/getting-files.xml:126(userinput)
+#, no-wrap
+msgid "cd ~/localrepo/fedora-docs/"
+msgstr "cd ~/localrepo/fedora-docs/"
+
+#: en_US/getting-files.xml:145(para)
+msgid "The leftmost entry in each line is the name of a module you can check out from CVS. The rest of the line ensures that checkouts include the proper branch of a document and the common build tools. For more information on CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:150(para)
+msgid "Note in the listing above that the <systemitem>about-fedora</systemitem> module has two branches available. One branch is for Fedora 7 and one is for forward development to match the current work of developers. On the other hand, the <systemitem>documentation-guide</systemitem> module is not branched."
+msgstr ""
+
+#: en_US/getting-files.xml:157(title)
+msgid "Modules Labeled <filename>-dir</filename>"
+msgstr ""
+
+#: en_US/getting-files.xml:158(para)
+msgid "Modules ending with the suffix <filename>-dir</filename> are not usually helpful to checkout directly. These modules do not include the common build tools and thus do not provide many of the functions contributors require."
+msgstr ""
+
+#: en_US/getting-files.xml:164(title)
+msgid "Module Names"
+msgstr "Modul Namen"
+
+#: en_US/getting-files.xml:165(para)
+msgid "Choose a module name that accurately reflects your document's subject, but avoid any name already taken. The document title without any use of the word <wordasword>fedora</wordasword> is a reasonable choice in most cases. Use the length descriptors <wordasword>tutorial</wordasword> or <wordasword>guide</wordasword> in the module name where appropriate."
+msgstr ""
+
+#: en_US/getting-files.xml:174(title)
+msgid "Avoid Redundancy"
+msgstr "Vermeide Redundanz"
+
+#: en_US/getting-files.xml:175(para)
+msgid "Do not use the word <wordasword>fedora</wordasword> to name modules in the Fedora Documentation Project CVS repository."
+msgstr ""
+
+#: en_US/getting-files.xml:181(title)
+msgid "Correct Module Naming"
+msgstr "Korrekte Modul-Namesgebung"
+
+#: en_US/getting-files.xml:182(segtitle)
+msgid "Document Name"
+msgstr "Dokument Name"
+
+#: en_US/getting-files.xml:183(segtitle)
+msgid "CVS Module Name"
+msgstr "CVS Modul Name"
+
+#: en_US/getting-files.xml:185(seg)
+msgid "Desktop User Guide"
+msgstr "Desktop Benutzer Anleitung"
+
+#: en_US/getting-files.xml:186(seg)
+msgid "desktop-user-guide"
+msgstr "desktop-user-guide"
+
+#: en_US/getting-files.xml:190(application)
+msgid "Yum"
+msgstr "Yum"
+
+#: en_US/getting-files.xml:189(seg)
+msgid "Software Management with <placeholder-1/>"
+msgstr "Software-Management mit <placeholder-1/>"
+
+#: en_US/getting-files.xml:191(seg)
+msgid "yum-guide"
+msgstr "yum-guide"
+
+#: en_US/getting-files.xml:194(application)
+msgid "Pup"
+msgstr "Pup"
+
+#: en_US/getting-files.xml:194(seg)
+msgid "Using <placeholder-1/>"
+msgstr "Benutze <placeholder-1/>"
+
+#: en_US/getting-files.xml:195(seg)
+msgid "pup-tutorial"
+msgstr "pup-tutorial"
+
+#: en_US/getting-files.xml:200(title)
+msgid "File Names"
+msgstr "Datei-Namen"
+
+#: en_US/getting-files.xml:201(para)
+msgid "Follow these guidelines for naming files to make collaboration and document reuse easy:"
+msgstr ""
+
+#: en_US/getting-files.xml:205(para)
+msgid "As with module names, avoid using the word <wordasword>fedora</wordasword> in file names since it is redundant."
+msgstr ""
+
+#: en_US/getting-files.xml:210(para)
+msgid "If the document is comprised of many XML files, avoid repeating the name of the document when naming the constituent files."
+msgstr ""
+
+#: en_US/getting-files.xml:215(para)
+msgid "Avoid numbering files to show order, since editors and authors often rearrange documents or reuse their files in other documents."
+msgstr ""
+
+#: en_US/emacs.xml:13(title)
+msgid "Emacs and PSGML Mode"
+msgstr "Emacs und PSGML Modus"
+
+#: en_US/emacs.xml:16(primary)
+msgid "PSGML"
+msgstr "PSGML"
+
+#: en_US/emacs.xml:20(primary)
+#: en_US/emacs.xml:24(primary)
+#: en_US/emacs.xml:43(primary)
+#: en_US/emacs.xml:224(primary)
+#: en_US/emacs.xml:233(primary)
+#: en_US/emacs.xml:238(primary)
+#: en_US/emacs.xml:243(primary)
+#: en_US/emacs.xml:523(application)
+#: en_US/emacs-nxml.xml:18(primary)
+#: en_US/emacs-nxml.xml:22(primary)
+msgid "Emacs"
+msgstr "Emacs"
+
+#: en_US/emacs.xml:25(secondary)
+msgid "PSGML mode"
+msgstr "PSGML Modus"
+
+#: en_US/emacs.xml:28(para)
+msgid "You can use the PSGML mode available for Emacs to make it easier to write in XML format. PSGML mode provides syntax-highlighting, tag completion, and more."
+msgstr ""
+
+#: en_US/emacs.xml:35(title)
+msgid "Installing PSGML"
+msgstr "Installiere PSGML"
+
+#: en_US/emacs.xml:36(para)
+msgid "To install PSGML, use the <command>yum</command> command:"
+msgstr "Zum Installieren von PSGML, benutze den <command>yum</command> Befehl:"
+
+#: en_US/emacs.xml:37(userinput)
+#, no-wrap
+msgid "yum install psgml"
+msgstr "yum install psgml"
+
+#: en_US/emacs.xml:40(title)
+msgid "Setting Up Your <filename>.emacs</filename> File"
+msgstr ""
+
+#: en_US/emacs.xml:48(filename)
+msgid ".emacs"
+msgstr ".emacs"
+
+#: en_US/emacs.xml:51(para)
+msgid "For Emacs to parse your DocBook documents correctly, you must have a <filename>.emacs</filename> file. Cut and paste the following into your existing <filename>.emacs</filename> file or create a new one that contains the following lines:"
+msgstr ""
+
+#: en_US/emacs.xml:181(para)
+msgid "If you have a wheel mouse and are using Emacs version 21, you can add the following to your <filename>.emacs</filename> file so your wheel will work in <application>Emacs</application>:"
+msgstr ""
+
+#: en_US/emacs.xml:192(para)
+msgid "If you are using the older version 20 of <application>Emacs</application>, add the following instead:"
+msgstr ""
+
+#: en_US/emacs.xml:221(title)
+msgid "Customizing Emacs"
+msgstr "Personalisieren Emacs "
+
+#: en_US/emacs.xml:225(secondary)
+msgid "customizing"
+msgstr "benutzerdefinierte"
+
+#: en_US/emacs.xml:229(filename)
+msgid ".Xresources"
+msgstr ".Xresources"
+
+#: en_US/emacs.xml:234(secondary)
+msgid "colors"
+msgstr "Farben"
+
+#: en_US/emacs.xml:239(secondary)
+msgid "font"
+msgstr "Schrift"
+
+#: en_US/emacs.xml:244(secondary)
+msgid "geometry"
+msgstr "Geometrie"
+
+#: en_US/emacs.xml:247(para)
+msgid "The colors, font, and geometry (default size of window) for Emacs in your <filename>~/.Xresources</filename> file. The format for the settings is <userinput>emacs.keyword:value</userinput>."
+msgstr ""
+
+#: en_US/emacs.xml:253(para)
+msgid "The following is a sample <filename>~/.Xresources</filename> file."
+msgstr "Folgende Datei, <filename>~/.Xresources</filename>, ist ein Beispiel."
+
+#: en_US/emacs.xml:258(para)
+#, fuzzy
+msgid "If you have other settings in your <filename>~/.Xresources</filename>, add the following to the end of the file."
+msgstr "Wenn Sie andere Einstellungen in ihrer <filename>~/.Xresources</filename> Datei haben, fügen sie das folgende an das Ende der Datei."
+
+#: en_US/emacs.xml:270(para)
+#, fuzzy
+msgid "After modifying this file, execute the following command:"
+msgstr "Nach dem ändern dieser Datei führen Sie bitte folgenden Befehl aus:"
+
+#: en_US/emacs.xml:273(command)
+msgid "xrdb -merge ~/.Xresources"
+msgstr "Schlüssel importieren/kombinieren"
+
+#: en_US/emacs.xml:274(para)
+msgid "Then restart <application>Emacs</application> to apply the changes."
+msgstr "Um die Änderungen zu aktivieren die <application>Emacs</application> Applikation neu starten."
+
+#: en_US/emacs.xml:395(title)
+msgid "Basic Emacs Commands"
+msgstr "Basis Emacs Befehle"
+
+#: en_US/emacs.xml:397(para)
+#, fuzzy
+msgid "The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key."
+msgstr "Die <keycap>Meta</keycap> Taste ist normalerweise die <keycap>Alt</keycap> Taste."
+
+#: en_US/emacs.xml:403(title)
+msgid "Emacs Commands"
+msgstr "Emacs Befehle"
+
+#: en_US/emacs.xml:404(segtitle)
+msgid "Shortcut"
+msgstr "Lesezeichen"
+
+#: en_US/emacs.xml:405(segtitle)
+msgid "Description"
+msgstr "Beschreibung"
+
+#: en_US/emacs.xml:408(keycap)
+#: en_US/emacs.xml:412(keycap)
+#: en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:443(keycap)
+#: en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:458(keycap)
+#: en_US/emacs.xml:463(keycap)
+#: en_US/emacs.xml:468(keycap)
+#: en_US/emacs.xml:473(keycap)
+#: en_US/emacs.xml:478(keycap)
+#: en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:508(keycap)
+#: en_US/emacs.xml:509(keycap)
+#: en_US/emacs.xml:514(keycap)
+#: en_US/emacs.xml:515(keycap)
+#: en_US/emacs.xml:520(keycap)
+#: en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:533(keycap)
+#: en_US/emacs.xml:540(keycap)
+#: en_US/emacs.xml:542(keycap)
+msgid "Ctrl"
+msgstr "Strg"
+
+#: en_US/emacs.xml:409(keycap)
+#: en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:540(keycap)
+#: en_US/emacs.xml:542(keycap)
+msgid "c"
+msgstr "c"
+
+#: en_US/emacs.xml:413(keycap)
+msgid "p"
+msgstr "p"
+
+#: en_US/emacs.xml:407(seg)
+#: en_US/emacs.xml:508(seg)
+#: en_US/emacs.xml:514(seg)
+#: en_US/emacs.xml:520(seg)
+#: en_US/emacs.xml:532(seg)
+#: en_US/emacs.xml:540(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+
+#: en_US/emacs.xml:415(seg)
+msgid "Parse DTD"
+msgstr "Parse DTD"
+
+#: en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:437(keycap)
+msgid "Shift"
+msgstr "Shift"
+
+#: en_US/emacs.xml:432(keycap)
+#: en_US/emacs.xml:438(keycap)
+msgid ","
+msgstr ","
+
+#: en_US/emacs.xml:432(keycap)
+#: en_US/emacs.xml:439(keycap)
+msgid "Tab"
+msgstr "Seitenreiter"
+
+#: en_US/emacs.xml:430(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+
+#: en_US/emacs.xml:433(seg)
+msgid "Display list of valid tags"
+msgstr "Anzeigen einer Liste von gültigen Tags"
+
+#: en_US/emacs.xml:436(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of tag, <placeholder-5/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, gebe Tag-Beginn ein, <placeholder-5/>"
+
+#: en_US/emacs.xml:440(seg)
+msgid "Complete the tag"
+msgstr "Vervollständige den Tag"
+
+#: en_US/emacs.xml:443(keycap)
+msgid "g"
+msgstr "g"
+
+#: en_US/emacs.xml:445(seg)
+#, fuzzy
+msgid "Cancel a command in the minibuffer"
+msgstr "Befehl in einem Terminal ausführen"
+
+#: en_US/emacs.xml:449(keycap)
+msgid "/"
+msgstr "/"
+
+#: en_US/emacs.xml:448(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+
+#: en_US/emacs.xml:450(seg)
+msgid "Close tag"
+msgstr "Close Tag"
+
+#: en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:533(keycap)
+msgid "a"
+msgstr "a"
+
+#: en_US/emacs.xml:455(seg)
+msgid "Move cursor to beginning of line"
+msgstr "Bewege Maus-Cursor zum Beginn der Linie"
+
+#: en_US/emacs.xml:458(keycap)
+msgid "e"
+msgstr "e"
+
+#: en_US/emacs.xml:460(seg)
+msgid "Move cursor to the end of the line"
+msgstr "Bewege Maus-Cursor zum Ende der Linie"
+
+#: en_US/emacs.xml:463(keycap)
+msgid "Home"
+msgstr "Home"
+
+#: en_US/emacs.xml:465(seg)
+msgid "Move cursor to the beginning of the file"
+msgstr "Bewege Maus-Cursor zum Beginn der Datei"
+
+#: en_US/emacs.xml:468(keycap)
+msgid "End"
+msgstr "Ende"
+
+#: en_US/emacs.xml:470(seg)
+msgid "Move cursor to the end of the file"
+msgstr "Bewege Maus-Cursor zum Ende der Datei"
+
+#: en_US/emacs.xml:473(keycap)
+msgid "k"
+msgstr "k"
+
+#: en_US/emacs.xml:475(seg)
+msgid "Cut line"
+msgstr "Zeile ausschneiden"
+
+#: en_US/emacs.xml:478(keycap)
+msgid "y"
+msgstr "y"
+
+#: en_US/emacs.xml:480(seg)
+msgid "Paste line"
+msgstr "Zeile einfügen"
+
+#: en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:515(keycap)
+msgid "s"
+msgstr "s"
+
+#: en_US/emacs.xml:485(seg)
+msgid "Search forward in the file"
+msgstr "Suche vorwärts in der Datei"
+
+#: en_US/emacs.xml:488(keycap)
+msgid "r"
+msgstr "r"
+
+#: en_US/emacs.xml:490(seg)
+msgid "Search backwards in the file"
+msgstr "Suche rückwärts in der Datei"
+
+#: en_US/emacs.xml:493(keycap)
+#: en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:527(keycap)
+msgid "Meta"
+msgstr "Meta"
+
+#: en_US/emacs.xml:493(keycap)
+msgid "$"
+msgstr "$"
+
+#: en_US/emacs.xml:495(seg)
+#: en_US/emacs.xml:500(seg)
+#, fuzzy
+msgid "Check spelling of current word"
+msgstr "Das momentan geöffnete Dokument auf eine fehlerhafte Rechtschreibung prüfen"
+
+#: en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:508(keycap)
+#: en_US/emacs.xml:514(keycap)
+#: en_US/emacs.xml:520(keycap)
+msgid "x"
+msgstr "x"
+
+#: en_US/emacs.xml:499(keycap)
+#: en_US/emacs.xml:504(keycap)
+msgid "Enter"
+msgstr "Enter"
+
+#: en_US/emacs.xml:498(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, <placeholder-3/>"
+
+#: en_US/emacs.xml:503(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, <placeholder-3/>"
+
+#: en_US/emacs.xml:505(seg)
+#, fuzzy
+msgid "Check spelling of current buffer"
+msgstr "Das momentan geöffnete Dokument auf eine fehlerhafte Rechtschreibung prüfen"
+
+#: en_US/emacs.xml:509(keycap)
+msgid "f"
+msgstr "f"
+
+#: en_US/emacs.xml:511(seg)
+msgid "Open file"
+msgstr "Datei öffnen"
+
+#: en_US/emacs.xml:517(seg)
+msgid "Save file"
+msgstr "Datei sichern"
+
+#: en_US/emacs.xml:523(seg)
+msgid "Exit <placeholder-1/> and prompt to save files if necessary"
+msgstr "<placeholder-1/> verlassen und wenn nötig nach einer Speicherung der Daten fragen."
+
+#: en_US/emacs.xml:527(keycap)
+msgid "q"
+msgstr "q"
+
+#: en_US/emacs.xml:529(seg)
+msgid "Fill paragraph"
+msgstr "Paragraph füllen"
+
+#: en_US/emacs.xml:536(computeroutput)
+#, no-wrap
+msgid "url"
+msgstr "url"
+
+#: en_US/emacs.xml:537(computeroutput)
+#, no-wrap
+msgid "ulink"
+msgstr "ulink"
+
+#: en_US/emacs.xml:535(seg)
+msgid "Edit attributes for a tag (for example, you can edit the <placeholder-1/> attribute of the <placeholder-2/> tag)"
+msgstr ""
+
+#: en_US/emacs.xml:544(seg)
+#, fuzzy
+msgid "Exit edit attributes"
+msgstr "Kanaleigenschaften bearbeiten"
+
+#: en_US/emacs.xml:550(title)
+#: en_US/emacs-nxml.xml:77(title)
+msgid "Examples"
+msgstr "Beispiele"
+
+#: en_US/emacs.xml:552(para)
+msgid "The table or reference card of Emacs and PSGML commands can be confusing for beginners. This section provides some examples of how to use them."
+msgstr ""
+
+#: en_US/emacs.xml:559(title)
+msgid "Tag Completion"
+msgstr "Tag Vervollständigung"
+
+#: en_US/emacs.xml:563(para)
+#, fuzzy
+msgid "This section assumes that you have already parsed the DTD file."
+msgstr "Dieser Teil setzt voraus, dass Sie schon die DTD Dateien geparsed haben."
+
+#: en_US/emacs.xml:567(para)
+msgid "To avoid having to type a tag repeatedly, use the key combination <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. At the bottom of the <application>Emacs</application> window, the following prompt appears:"
+msgstr ""
+
+#: en_US/emacs.xml:574(prompt)
+msgid "Tag: <"
+msgstr "Tag: <"
+
+#: en_US/emacs.xml:576(para)
+msgid "To view a list of available tags, use either the <keycap>Tab</keycap> or <keycap>?</keycap>. If you know the first few letters of a tag, enter them, followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, that tag appears. If more than one completion exists, a complete list of possible tags appears."
+msgstr ""
+
+#: en_US/emacs.xml:585(para)
+msgid "If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, <keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the example below:"
+msgstr ""
+
+#: en_US/emacs.xml:602(title)
+msgid "Tag Closure"
+msgstr "Tag Abschluss"
+
+#: en_US/emacs.xml:604(para)
+msgid "After you open a tag, you must close it. The easiest way to close an open tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most recently opened tag."
+msgstr ""
+
+#: en_US/emacs.xml:616(title)
+msgid "Other Emacs Tasks"
+msgstr "Andere Emacs Tasks"
+
+#: en_US/emacs.xml:619(title)
+msgid "Working with One Window"
+msgstr "Arbeiten mit einem Fenster"
+
+#: en_US/emacs.xml:620(para)
+msgid "Sometimes in <application>Emacs</application>, the window becomes split, with tags completions or other text in an alternate window. To return to a single window, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+msgstr ""
+
+#: en_US/emacs.xml:630(title)
+msgid "Saving Work"
+msgstr "Sichere Arbeit"
+
+#: en_US/emacs.xml:631(para)
+msgid "To save your work, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>."
+msgstr ""
+
+#: en_US/emacs.xml:642(title)
+msgid "The \"Clear/Quit\" Command"
+msgstr "Der \"Clear/Quit\" Befehl"
+
+#: en_US/emacs.xml:643(para)
+msgid "If the tag completion process becomes unwieldy or confusing, use the keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to exit back to the text. <application>Emacs</application> clears any prompts and returns to the buffer text."
+msgstr ""
+
+#: en_US/emacs.xml:653(title)
+msgid "Opening a new file"
+msgstr "Öffne neue Datei"
+
+#: en_US/emacs.xml:654(para)
+msgid "To open a new file, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the <application>Emacs</application> window. Enter the file name, using <keycap>Tab</keycap> completion if desired, of the file you wish to open."
+msgstr ""
+
+#: en_US/emacs.xml:668(title)
+msgid "Closing <application>Emacs</application>"
+msgstr "Schliessen von <application>Emacs</application>"
+
+#: en_US/emacs.xml:669(para)
+msgid "To close <application>Emacs</application> use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have not saved your work, <application>Emacs</application> prompts you to save any changed files."
+msgstr ""
+
+#: en_US/emacs.xml:687(title)
+#: en_US/emacs-nxml.xml:127(title)
+msgid "Additional Resources"
+msgstr "Zusätzliche Ressourcen"
+
+#: en_US/emacs.xml:689(para)
+#, fuzzy
+msgid "Additional Emacs and PSGML references are available at the following locations:"
+msgstr "Zusätzlich stehen EMacs und PSGML Referenzen hier zur verfügung:"
+
+#: en_US/emacs.xml:697(citetitle)
+#: en_US/emacs-nxml.xml:143(citetitle)
+msgid "Emacs Quick Reference Guide"
+msgstr "Emacs Quick Reference Guide"
+
+#: en_US/emacs.xml:701(para)
+msgid "Emacs reference card that comes with the <filename>emacs</filename> package. You can print it out as a reference. —<filename>/usr/share/emacs/<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs.xml:708(para)
+msgid "Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+msgstr ""
+
+#: en_US/emacs.xml:714(para)
+msgid "<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of Emacs commands for PSGML mode."
+msgstr ""
+
+#: en_US/emacs.xml:723(citetitle)
+msgid "PSGML Tricks"
+msgstr "PSGML Tricks"
+
+#: en_US/emacs-nxml.xml:11(title)
+msgid "Emacs and nXML Mode"
+msgstr "Emacs und nXML Modus"
+
+#: en_US/emacs-nxml.xml:14(primary)
+#: en_US/emacs-nxml.xml:51(primary)
+msgid "nXML"
+msgstr "nXML"
+
+#: en_US/emacs-nxml.xml:23(secondary)
+msgid "nXML mode"
+msgstr "nXML Modus"
+
+#: en_US/emacs-nxml.xml:26(para)
+msgid "You can also use the nXML mode available for <application>Emacs</application> to make it even easier to write in DocBook XML format. nXML mode provides context-sensitive editing using completion, real time validity error checking, syntax highlighting and indentation. All you need to do is install an RPM!!"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:35(title)
+msgid "Early stages"
+msgstr "Frühe Version"
+
+#: en_US/emacs-nxml.xml:36(para)
+msgid "Please be aware the nxml-mode for <application>Emacs</application> is quite new, so there are a few things that the advanced user might notice when using it with other documents types. If you keep an eye on the mailing-list, you can keep up to date with these, as well as ask questions. For more details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:48(title)
+msgid "Getting the nXML RPM"
+msgstr "Beziehen des nXML RPM"
+
+#: en_US/emacs-nxml.xml:52(secondary)
+msgid "RPM"
+msgstr "RPM"
+
+#: en_US/emacs-nxml.xml:56(primary)
+msgid "nXML RPM"
+msgstr "nXML RPM"
+
+#: en_US/emacs-nxml.xml:59(para)
+msgid "To use nXML mode with emacs, you will need to install the nXML RPM available from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www.thaiopensource.com/download/\">http://www.thaiopensource.com/download/</ulink>. The source requires a lot more work to setup, therefore we will only be concentrating on the RPM version."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:69(para)
+msgid "Information on where to get the source is available in <xref linkend=\"sn-emacs-additional-resources\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:79(para)
+msgid "Compared to PSGML mode there are only couple of commands that you need. This speeds up writing with <application>Emacs</application> considerably, which means you can concentrate more on the content of your article."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:88(para)
+msgid "To create a tag, type <userinput><</userinput> and then type the keyword. To complete the keyword, press <command>Ctrl-Ret</command>, then add the last <userinput>></userinput>. To close a tag, type <userinput></</userinput>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:97(para)
+msgid "When you open a document that doesn't have a DOCTYPE declaration at the top of the file, you will get this message and tag completion won't work because nXML will not know what format you are writing."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:104(para)
+msgid "To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> and load <filename>docbook.rnc</filename>. <application>Emacs</application> will then prompt you to save it in the current working directory."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:115(para)
+msgid "The commands already discussed are the only differences between using <application>Emacs</application> with PSGML mode and <application>Emacs</application> with nXML mode. You will still need to use all the same commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:129(para)
+msgid "Additional Emacs and nXML references are available at the following locations:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:136(ulink)
+msgid "http://www.thaiopensource.com/download/"
+msgstr "http://www.thaiopensource.com/download/"
+
+#: en_US/emacs-nxml.xml:137(citetitle)
+msgid "Author's download area"
+msgstr "Download-Bereich des Authors"
+
+#: en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+
+#: en_US/emacs-nxml.xml:147(para)
+msgid "Emacs reference card that comes with the <filename>emacs</filename> package. You can print it out as a reference. —<filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:157(title)
+msgid "nXML README File"
+msgstr "nXML LIESMICH Datei"
+
+#: en_US/emacs-nxml.xml:161(para)
+msgid "This file can be found in the directory you extracted the source into, or in <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename> if you installed the RPM."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:169(para)
+msgid "README file:"
+msgstr "LIESMICH Datei:"
+
+#: en_US/emacs-nxml.xml:171(para)
+msgid "This is a new major mode for GNU Emacs for editing XML documents. It supports editing well-formed XML documents and also provides schema-sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:177(para)
+msgid "To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs version 20 will not work properly, nor will XEmacs. To get started, do the following:"
+msgstr "Um es zu nutzen brauchen Sie GNU Emacs Version 21.x, bevorzugt wird 21.3. GNU Emacs in der Version 20 und XEmacs werden nicht richtig funktionieren. Um anzufangen tun Sie folgendes:"
+
+#: en_US/emacs-nxml.xml:184(command)
+msgid "M-x load-file RET rng-auto.el RET"
+msgstr "M-x load-file RET rng-auto.el RET"
+
+#: en_US/emacs-nxml.xml:187(para)
+msgid "This defines the necessary autoloads. Now, visit a file containing an XML document, and do the following:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:192(command)
+msgid "M-x nxml-mode"
+msgstr "M-x nxml-mode"
+
+#: en_US/emacs-nxml.xml:195(para)
+msgid "Now do"
+msgstr "Mache jetzt"
+
+#: en_US/emacs-nxml.xml:200(command)
+msgid "C-h m"
+msgstr "C-h m"
+
+#: en_US/emacs-nxml.xml:203(para)
+msgid "For information on how to use nxml-mode. The beginnings of a manual are in nxml-mode.info. You can read this using:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:209(command)
+msgid "C-u M-x info RET nxml-mode.info RET"
+msgstr "C-u M-x info RET nxml-mode.info RET"
+
+#: en_US/emacs-nxml.xml:212(para)
+msgid "It's also installed as an entry at the end of the top-level info directory. So you can read it with <command>C-h i</command> as usual."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:217(para)
+msgid "You can use <filename>test.valid.xml</filename> and <filename>test.invalid.xml</filename> as examples of valid and invalid XML documents."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:223(para)
+msgid "To get things automatically loaded each time you start Emacs, add:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:228(computeroutput)
+#, no-wrap
+msgid ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+msgstr ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+
+#: en_US/emacs-nxml.xml:232(para)
+msgid "to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-200YMMDD</computeroutput> is the directory containing the <filename>.elc</filename> files. Note that <filename>rng-auto.el</filename> does not load all of the nxml-mode code; it merely sets things up so that all the features of nxml-mode will be autoloaded properly. You should not try to autoload <filename>rng-auto.el</filename> itself."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:242(para)
+msgid "To use nxml-mode automatically for files with an extension of <filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> or <filename>xhtml</filename>, add the following to your <filename>.emacs</filename> file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:250(computeroutput)
+#, no-wrap
+msgid ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+msgstr ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+
+#: en_US/emacs-nxml.xml:255(para)
+msgid "If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are running Emacs 21.3 or later, then I recommend enabling unify-8859-on-decoding-mode, by adding the following to your <filename>.emacs</filename> file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:263(computeroutput)
+#, no-wrap
+msgid "(unify-8859-on-decoding-mode)"
+msgstr "(unify-8859-on-decoding-mode)"
+
+#: en_US/emacs-nxml.xml:266(para)
+msgid "To get validation and schema-sensitive editing, you need a RELAX NG Compact Syntax (RNC) schema for you document. The schema directory includes some schemas for popular document types."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:272(para)
+msgid "For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://relaxng.org/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:277(para)
+msgid "For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial.html</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:282(para)
+msgid "For automatically creating RNC schemas, I recommend my Trang program: <ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee.thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:293(para)
+msgid "Infer an RNC schema from an instance document"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:298(para)
+msgid "Convert a DTD to an RNC schema"
+msgstr "Konvertiere ein DTD in ein RNC Schema"
+
+#: en_US/emacs-nxml.xml:303(para)
+#, fuzzy
+msgid "Convert a RELAX NG XML syntax schema to an RNC schema"
+msgstr "Konvertiert ein RELAX NG XML Syntax Schema in ein RNC Schema"
+
+#: en_US/emacs-nxml.xml:288(para)
+msgid "You can use this to <placeholder-1/>"
+msgstr "Sie können dies benutzen zu <placeholder-1/>"
+
+#: en_US/emacs-nxml.xml:310(para)
+msgid "To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html\">http://www.pantor.com/download.html\"</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:316(para)
+msgid "To convert a W3C XML Schema to an RNC schema, you need first to convert it to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:323(para)
+msgid "The file <filename>NEWS</filename> describes recent changes."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:327(para)
+msgid "Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug reports, discussion. I will announce all new versions there."
+msgstr "Bitte benutzen Sie für Fehler Berichte und Diskussionen die Liste <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> Ich werde dort alle neuen Versionen bekanntgeben."
+
+#: en_US/emacs-nxml.xml:333(para)
+msgid "James Clark"
+msgstr "James Clark"
+
+#: en_US/emacs-nxml.xml:336(para)
+msgid "jjc@@thaiopensource.com"
+msgstr "jjc@@thaiopensource.com"
+
+#: en_US/acknowledgments.xml:11(title)
+msgid "Acknowledgments"
+msgstr "Danksagungen"
+
+#: en_US/acknowledgments.xml:13(para)
+msgid "This document is based on a document started by Tammy Fox (tfox at redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray Fuller (jrfuller at redhat.com)."
+msgstr ""
+
+#: en_US/acknowledgments.xml:19(para)
+msgid "A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr ""
+
+#: en_US/acknowledgments.xml:25(para)
+msgid "Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to add the trailing slashes to the <command>figure</command> tag example in <filename>docs-xml-tags.xml</filename>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:32(para)
+msgid "A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been applied to add <xref linkend=\"ch-vim\"/>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:37(para)
+msgid "A patch from Karsten Wade (kwade at redhat.com) has been applied to add <xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields (stickster at gmail.com)."
+msgstr ""
+
+#. This section has been removed.
+#. <para>
+#. A patch from Paul W. Frields (stickster at gmail.com) has been applied
+#. to add more explanation of the <command>screen</command> tag set to <xref
+#. linkend="sn-xml-tags-screen"></xref>.
+#. </para>
+#: en_US/acknowledgments.xml:50(para)
+msgid "A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been applied to more fully explaing the document building system."
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: en_US/acknowledgments.xml:0(None)
+msgid "translator-credits"
+msgstr "Fabian Affolter <fab@@fedoraproject.org>, 2007."
+
+@
+
+
+1.4
+log
+ at some more strings translated proofreading needed
+@
+text
+ at d9 2
+a10 2
+"PO-Revision-Date: 2007-08-16 11:11+0200\n"
+"Last-Translator: Peter Reuschlein <petreu@@fedoraproject.org>\n"
+a58 1
+#, fuzzy
+d60 1
+a60 1
+msgstr "Ein neues Kapitel bei Veröffentlichungen hinzufügen."
+d72 1
+a72 1
+msgstr ""
+a74 1
+#, fuzzy
+d76 1
+a76 1
+msgstr "Auf neue Inhalts und Build Voraussetzungen aktualisieren."
+d108 1
+a108 1
+msgstr ""
+d117 1
+a117 1
+msgstr ""
+a182 1
+#, fuzzy
+a191 1
+#, fuzzy
+d193 1
+a193 1
+msgstr "Um den Web-Server bei jedem Systemstart zu starten benutzen Sie folgenden Befehl:"
+a200 1
+#, fuzzy
+d202 1
+a202 1
+msgstr "Um die neue Sandbox Seite zu Testen öffnen Sie einen Web-Browser mit der URL <uri>http://docs.localhost.localdomain</uri>."
+a212 1
+#, fuzzy
+a270 1
+#, fuzzy
+d543 1
+a543 1
+msgstr ""
+a1185 1
+#, fuzzy
+d1187 1
+a1187 1
+msgstr "ungültiges Zeichen hinter %s in „%s“"
+a1381 1
+#, fuzzy
+d1777 1
+a1777 1
+msgstr ""
+d2211 1
+a2211 1
+msgstr ""
+a2362 1
+#, fuzzy
+d2364 1
+a2364 1
+msgstr "Bildschirm-Abzug"
+d2828 1
+a2828 1
+msgstr ""
+d2964 1
+a2964 1
+#, fuzzy, no-wrap
+d2966 1
+a2966 1
+msgstr "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+a3018 1
+#, fuzzy
+d3020 1
+a3020 1
+msgstr "Typographische Konventionen für %1"
+a3500 1
+#, fuzzy
+@
+
+
+1.3
+log
+ at proofreading needed
+@
+text
+ at d9 1
+a9 1
+"PO-Revision-Date: 2007-08-15 11:32+0200\n"
+d56 1
+a56 1
+msgstr ""
+d59 1
+d61 1
+a61 1
+msgstr ""
+d76 1
+d78 1
+a78 1
+msgstr ""
+d1890 1
+a1890 1
+msgstr ""
+d1910 1
+a1910 1
+msgstr ""
+d1927 1
+a1927 1
+msgstr ""
+d2088 1
+d2090 1
+a2090 1
+msgstr ""
+d2433 1
+d2435 1
+a2435 1
+msgstr ""
+d2451 1
+a2451 1
+msgstr ""
+d2802 1
+d2804 1
+a2804 1
+msgstr ""
+d2963 1
+a2963 1
+msgstr ""
+d3242 1
+a3242 1
+msgstr ""
+d3245 1
+d3247 1
+a3247 1
+msgstr ""
+d3250 1
+d3252 1
+a3252 1
+msgstr ""
+d3260 1
+a3260 1
+msgstr ""
+d3267 1
+d3269 1
+a3269 1
+msgstr ""
+d3512 1
+d3514 1
+a3514 1
+msgstr ""
+d3557 1
+d3559 1
+a3559 1
+msgstr ""
+d3635 1
+d3637 1
+a3637 1
+msgstr ""
+d3763 1
+a3763 1
+msgstr ""
+d3867 1
+d3869 1
+a3869 1
+msgstr ""
+d3889 1
+a3889 1
+msgstr ""
+@
+
+
+1.2
+log
+ at 447 translated messages, 25 fuzzy translations, 423 untranslated messages
+@
+text
+ at d1 2
+d4 1
+a4 1
+#
+d7 1
+a7 1
+"Project-Id-Version: documentation guide\n"
+d9 2
+a10 2
+"PO-Revision-Date: 2007-08-04 13:17+0100\n"
+"Last-Translator: Fabian Affolter <fab@@fedoraproject.org>\n"
+d16 1
+d162 1
+a162 1
+msgstr ""
+d171 1
+a171 1
+msgstr ""
+d175 1
+a175 1
+msgstr ""
+d183 1
+d185 1
+a185 1
+msgstr ""
+d193 1
+d195 1
+a195 1
+msgstr ""
+d203 1
+d205 1
+a205 1
+msgstr ""
+d216 1
+d218 1
+a218 1
+msgstr ""
+d275 1
+d277 1
+a277 1
+msgstr ""
+d291 1
+d293 1
+a293 1
+msgstr ""
+d320 1
+d322 1
+a322 1
+msgstr ""
+d360 1
+d362 1
+a362 1
+msgstr ""
+d471 1
+a471 1
+msgstr ""
+@
+
+
+1.1
+log
+ at initial version
+@
+text
+ at d7 1
+a7 1
+"PO-Revision-Date: 2007-08-02 18:55+0100\n"
+d15 1
+a15 2
+#: en_US/rpm-info.xml:22
+#: (rights)
+d19 1
+a19 2
+#: en_US/rpm-info.xml:23
+#: (version)
+d23 1
+a23 2
+#: en_US/rpm-info.xml:26
+#: (year)
+d27 1
+a27 2
+#: en_US/rpm-info.xml:27
+#: (year)
+d31 1
+a31 2
+#: en_US/rpm-info.xml:28
+#: (year)
+d35 1
+a35 2
+#: en_US/rpm-info.xml:29
+#: (year)
+d39 1
+a39 2
+#: en_US/rpm-info.xml:30
+#: (year)
+d43 1
+a43 2
+#: en_US/rpm-info.xml:31
+#: (holder)
+d47 1
+a47 2
+#: en_US/rpm-info.xml:33
+#: (title)
+d51 1
+a51 2
+#: en_US/rpm-info.xml:34
+#: (desc)
+d55 9
+a63 2
+#: en_US/rpm-info.xml:38
+#: (details)
+d67 1
+a67 2
+#: en_US/rpm-info.xml:42
+#: (details)
+d71 1
+a71 2
+#: en_US/rpm-info.xml:49
+#: (details)
+d75 297
+a371 2
+#: en_US/vim.xml:13
+#: (title)
+d375 2
+a376 2
+#: en_US/vim.xml:16
+#: (primary) en_US/vim.xml:33
+d380 1
+a380 2
+#: en_US/vim.xml:19
+#: (para)
+d384 1
+a384 2
+#: en_US/vim.xml:30
+#: (title)
+d388 2
+a389 2
+#: en_US/vim.xml:34
+#: (secondary) en_US/emacs.xml:44
+d393 1
+a393 2
+#: en_US/vim.xml:37
+#: (para)
+d409 1
+a409 2
+#: en_US/vim.xml:55
+#: (para)
+d413 1
+a413 2
+#: en_US/vim.xml:69
+#: (title)
+d417 1
+a417 2
+#: en_US/vim.xml:71
+#: (para)
+d450 1
+a450 2
+#: en_US/vim.xml:110
+#: (para)
+d454 1
+a454 2
+#: en_US/vim.xml:119
+#: (title)
+d458 1
+a458 2
+#: en_US/vim.xml:121
+#: (para)
+d462 1
+a462 2
+#: en_US/vim.xml:127
+#: (para)
+d466 1
+a466 2
+#: en_US/vim.xml:134
+#: (para)
+d470 1
+a470 2
+#: en_US/vim.xml:140
+#: (ulink)
+d474 1
+a474 2
+#: en_US/vim.xml:145
+#: (para)
+d478 1
+a478 2
+#: en_US/tutorial.xml:13
+#: (title)
+d482 1
+a482 2
+#: en_US/tutorial.xml:14
+#: (para)
+d486 1
+a486 2
+#: en_US/tutorial.xml:19
+#: (title)
+d490 2
+a491 2
+#: en_US/tutorial.xml:21
+#: (primary) en_US/tutorial.xml:56
+d495 1
+a495 2
+#: en_US/tutorial.xml:22
+#: (secondary)
+d499 1
+a499 2
+#: en_US/tutorial.xml:24
+#: (para)
+d503 1
+a503 2
+#: en_US/tutorial.xml:54
+#: (title)
+d507 1
+a507 2
+#: en_US/tutorial.xml:57
+#: (secondary)
+d511 1
+a511 2
+#: en_US/tutorial.xml:59
+#: (para)
+d515 1
+a515 2
+#: en_US/tutorial.xml:65
+#: (title)
+d519 1
+a519 2
+#: en_US/tutorial.xml:95
+#: (para)
+d523 1
+a523 2
+#: en_US/style.xml:14
+#: (title)
+d527 1
+a527 2
+#: en_US/style.xml:16
+#: (para)
+d531 1
+a531 2
+#: en_US/style.xml:26
+#: (para)
+d533 1
+a533 1
+msgstr ""
+d535 1
+a535 2
+#: en_US/style.xml:31
+#: (para)
+d539 1
+a539 2
+#: en_US/style.xml:36
+#: (para)
+d543 1
+a543 2
+#: en_US/style.xml:41
+#: (para)
+d547 1
+a547 2
+#: en_US/style.xml:46
+#: (para)
+d551 1
+a551 2
+#: en_US/style.xml:51
+#: (para)
+d555 1
+a555 2
+#: en_US/style.xml:62
+#: (title)
+d559 1
+a559 2
+#: en_US/style.xml:64
+#: (para)
+d563 1
+a563 2
+#: en_US/style.xml:77
+#: (para)
+d567 1
+a567 2
+#: en_US/style.xml:71
+#: (para)
+d571 1
+a571 2
+#: en_US/style.xml:89
+#: (para)
+d575 1
+a575 2
+#: en_US/style.xml:100
+#: (title)
+d584 1
+a584 2
+#: en_US/style.xml:108
+#: (para)
+d588 1
+a588 2
+#: en_US/style.xml:116
+#: (title)
+d593 1
+a593 2
+#: en_US/style.xml:120
+#: (para)
+d599 1
+a599 2
+#: en_US/style.xml:129
+#: (para)
+d603 1
+a603 2
+#: en_US/style.xml:135
+#: (para)
+d607 1
+a607 2
+#: en_US/style.xml:146
+#: (para)
+d611 1
+a611 2
+#: en_US/style.xml:153
+#: (para)
+d615 1
+a615 2
+#: en_US/style.xml:161
+#: (para)
+d619 1
+a619 2
+#: en_US/style.xml:176
+#: (para)
+d623 1
+a623 2
+#: en_US/style.xml:183
+#: (para)
+d627 1
+a627 2
+#: en_US/style.xml:190
+#: (para)
+d631 1
+a631 2
+#: en_US/style.xml:203
+#: (title)
+d633 1
+a633 1
+msgstr ""
+d635 1
+a635 2
+#: en_US/style.xml:206
+#: (title)
+d639 1
+a639 2
+#: en_US/style.xml:207
+#: (para)
+d647 1
+a647 2
+#: en_US/style.xml:218
+#: (para)
+d651 1
+a651 2
+#: en_US/style.xml:224
+#: (title)
+d655 1
+a655 2
+#: en_US/style.xml:225
+#: (para)
+d659 1
+a659 2
+#: en_US/style.xml:232
+#: (term)
+d661 1
+a661 1
+msgstr ""
+d663 1
+a663 2
+#: en_US/style.xml:234
+#: (para)
+d667 1
+a667 2
+#: en_US/style.xml:242
+#: (term)
+d669 1
+a669 1
+msgstr ""
+d671 1
+a671 2
+#: en_US/style.xml:249
+#: (para)
+d675 1
+a675 2
+#: en_US/style.xml:257
+#: (term)
+d679 1
+a679 2
+#: en_US/style.xml:259
+#: (para)
+d683 1
+a683 2
+#: en_US/style.xml:275
+#: (term)
+d685 1
+a685 1
+msgstr ""
+d687 1
+a687 2
+#: en_US/style.xml:277
+#: (para)
+d691 1
+a691 2
+#: en_US/style.xml:285
+#: (term)
+d693 1
+a693 1
+msgstr ""
+d695 1
+a695 2
+#: en_US/style.xml:287
+#: (para)
+d699 1
+a699 2
+#: en_US/style.xml:297
+#: (title)
+d703 1
+a703 2
+#: en_US/style.xml:298
+#: (para)
+d707 1
+a707 2
+#: en_US/style.xml:305
+#: (term)
+d711 1
+a711 2
+#: en_US/style.xml:309
+#: (para)
+d715 1
+a715 2
+#: en_US/style.xml:314
+#: (para)
+d719 1
+a719 2
+#: en_US/style.xml:320
+#: (title)
+d723 1
+a723 2
+#: en_US/style.xml:321
+#: (para)
+d727 1
+a727 2
+#: en_US/style.xml:328
+#: (title)
+d731 1
+a731 2
+#: en_US/style.xml:329
+#: (para)
+d735 1
+a735 2
+#: en_US/style.xml:337
+#: (term)
+d739 1
+a739 2
+#: en_US/style.xml:341
+#: (para)
+d743 1
+a743 2
+#: en_US/style.xml:346
+#: (para)
+d747 1
+a747 2
+#: en_US/style.xml:351
+#: (para)
+d751 1
+a751 2
+#: en_US/style.xml:357
+#: (title)
+d755 1
+a755 2
+#: en_US/style.xml:358
+#: (para)
+d759 1
+a759 2
+#: en_US/style.xml:375
+#: (title)
+d763 1
+a763 2
+#: en_US/style.xml:376
+#: (para)
+d767 1
+a767 2
+#: en_US/style.xml:388
+#: (para)
+d771 1
+a771 2
+#: en_US/style.xml:396
+#: (term)
+d775 1
+a775 2
+#: en_US/style.xml:398
+#: (para)
+d779 1
+a779 2
+#: en_US/style.xml:403
+#: (title)
+d783 1
+a783 2
+#: en_US/style.xml:405
+#: (para)
+d787 1
+a787 2
+#: en_US/style.xml:411
+#: (title)
+d791 1
+a791 2
+#: en_US/style.xml:412
+#: (para)
+d795 1
+a795 2
+#: en_US/style.xml:418
+#: (para)
+d799 1
+a799 2
+#: en_US/style.xml:427
+#: (term)
+d803 1
+a803 2
+#: en_US/style.xml:429
+#: (para)
+d805 1
+a805 1
+msgstr ""
+d807 1
+a807 2
+#: en_US/style.xml:433
+#: (title)
+d812 1
+a812 2
+#: en_US/style.xml:434
+#: (para)
+d816 1
+a816 2
+#: en_US/style.xml:439
+#: (title)
+d820 1
+a820 2
+#: en_US/style.xml:440
+#: (para)
+d824 1
+a824 3
+#: en_US/style.xml:452
+#: (title)
+#, fuzzy
+d828 1
+a828 2
+#: en_US/style.xml:453
+#: (para)
+d832 1
+a832 2
+#: en_US/style.xml:466
+#: (term)
+d836 1
+a836 2
+#: en_US/style.xml:468
+#: (para)
+d840 1
+a840 2
+#: en_US/style.xml:476
+#: (term)
+d844 1
+a844 2
+#: en_US/style.xml:478
+#: (para)
+d848 1
+a848 2
+#: en_US/style.xml:487
+#: (term)
+d852 1
+a852 2
+#: en_US/style.xml:489
+#: (para)
+d856 1
+a856 2
+#: en_US/style.xml:496
+#: (term)
+d860 1
+a860 2
+#: en_US/style.xml:498
+#: (para)
+d864 1
+a864 2
+#: en_US/style.xml:505
+#: (term)
+d868 1
+a868 2
+#: en_US/style.xml:507
+#: (para)
+d872 1
+a872 2
+#: en_US/style.xml:517
+#: (title)
+d876 1
+a876 2
+#: en_US/style.xml:518
+#: (para)
+d880 1
+a880 2
+#: en_US/style.xml:530
+#: (title)
+d884 1
+a884 2
+#: en_US/style.xml:531
+#: (para)
+d888 1
+a888 2
+#: en_US/style.xml:539
+#: (title)
+d892 1
+a892 2
+#: en_US/style.xml:540
+#: (para)
+d896 1
+a896 2
+#: en_US/style.xml:554
+#: (title)
+d900 1
+a900 2
+#: en_US/style.xml:555
+#: (para)
+d904 1
+a904 2
+#: en_US/style.xml:563
+#: (title)
+d908 1
+a908 2
+#: en_US/style.xml:564
+#: (para)
+d912 1
+a912 2
+#: en_US/style.xml:570
+#: (term)
+d916 1
+a916 2
+#: en_US/style.xml:572
+#: (para)
+d920 1
+a920 2
+#: en_US/style.xml:581
+#: (para)
+d924 1
+a924 2
+#: en_US/style.xml:588
+#: (para)
+d928 1
+a928 2
+#: en_US/style.xml:596
+#: (para)
+d932 1
+a932 2
+#: en_US/style.xml:602
+#: (para)
+d936 1
+a936 2
+#: en_US/style.xml:611
+#: (term)
+d940 1
+a940 2
+#: en_US/style.xml:613
+#: (para)
+d944 1
+a944 2
+#: en_US/style.xml:621
+#: (term)
+d946 1
+a946 1
+msgstr ""
+d948 1
+a948 2
+#: en_US/style.xml:623
+#: (para)
+d952 1
+a952 2
+#: en_US/style.xml:631
+#: (term)
+d956 1
+a956 2
+#: en_US/style.xml:633
+#: (para)
+d960 1
+a960 2
+#: en_US/style.xml:642
+#: (para)
+d964 1
+a964 2
+#: en_US/style.xml:653
+#: (title)
+d966 1
+a966 1
+msgstr ""
+d968 1
+a968 2
+#: en_US/style.xml:656
+#: (title)
+d972 1
+a972 2
+#: en_US/style.xml:657
+#: (para)
+d978 1
+a978 2
+#: en_US/style.xml:668
+#: (para)
+d982 1
+a982 2
+#: en_US/style.xml:679
+#: (term)
+d984 1
+a984 1
+msgstr ""
+d986 1
+a986 2
+#: en_US/style.xml:681
+#: (para)
+d990 1
+a990 2
+#: en_US/style.xml:689
+#: (para)
+d994 1
+a994 2
+#: en_US/style.xml:695
+#: (para)
+d998 1
+a998 2
+#: en_US/style.xml:700
+#: (para)
+d1002 1
+a1002 2
+#: en_US/style.xml:706
+#: (para)
+d1006 1
+a1006 2
+#: en_US/style.xml:715
+#: (term)
+d1010 1
+a1010 2
+#: en_US/style.xml:717
+#: (para)
+d1014 1
+a1014 2
+#: en_US/style.xml:726
+#: (term)
+d1018 1
+a1018 2
+#: en_US/style.xml:728
+#: (para)
+d1022 1
+a1022 2
+#: en_US/style.xml:734
+#: (para)
+d1026 1
+a1026 2
+#: en_US/style.xml:740
+#: (para)
+d1030 1
+a1030 2
+#: en_US/style.xml:746
+#: (para)
+d1034 1
+a1034 2
+#: en_US/style.xml:751
+#: (para)
+d1038 1
+a1038 2
+#: en_US/style.xml:757
+#: (para)
+d1042 1
+a1042 2
+#: en_US/style.xml:764
+#: (para)
+d1046 1
+a1046 2
+#: en_US/style.xml:770
+#: (para)
+d1050 1
+a1050 2
+#: en_US/style.xml:776
+#: (para)
+d1054 1
+a1054 2
+#: en_US/style.xml:785
+#: (term)
+d1056 1
+a1056 1
+msgstr ""
+d1058 1
+a1058 2
+#: en_US/style.xml:787
+#: (para)
+d1062 1
+a1062 2
+#: en_US/style.xml:798
+#: (term)
+d1066 1
+a1066 2
+#: en_US/style.xml:802
+#: (para)
+d1070 1
+a1070 2
+#: en_US/style.xml:808
+#: (para)
+d1074 1
+a1074 2
+#: en_US/style.xml:818
+#: (term)
+d1078 1
+a1078 2
+#: en_US/style.xml:820
+#: (para)
+d1082 1
+a1082 2
+#: en_US/style.xml:826
+#: (para)
+d1086 1
+a1086 2
+#: en_US/style.xml:831
+#: (para)
+d1090 2
+a1091 3
+#: en_US/style.xml:836
+#: (para) en_US/style.xml:1239
+#: (term)
+d1093 1
+a1093 1
+msgstr ""
+d1095 1
+a1095 2
+#: en_US/style.xml:841
+#: (para)
+d1097 1
+a1097 1
+msgstr ""
+d1099 1
+a1099 2
+#: en_US/style.xml:846
+#: (para)
+d1103 1
+a1103 2
+#: en_US/style.xml:851
+#: (para)
+d1105 1
+a1105 1
+msgstr ""
+d1107 1
+a1107 2
+#: en_US/style.xml:859
+#: (term)
+d1111 1
+a1111 2
+#: en_US/style.xml:861
+#: (para)
+d1115 1
+a1115 2
+#: en_US/style.xml:866
+#: (para)
+d1119 1
+a1119 2
+#: en_US/style.xml:871
+#: (para)
+d1123 1
+a1123 2
+#: en_US/style.xml:876
+#: (para)
+d1127 1
+a1127 2
+#: en_US/style.xml:882
+#: (title)
+d1131 1
+a1131 2
+#: en_US/style.xml:885
+#: (para)
+d1135 1
+a1135 2
+#: en_US/style.xml:891
+#: (para)
+d1139 1
+a1139 2
+#: en_US/style.xml:896
+#: (para)
+d1143 1
+a1143 2
+#: en_US/style.xml:903
+#: (title)
+d1147 1
+a1147 2
+#: en_US/style.xml:906
+#: (para)
+d1151 1
+a1151 2
+#: en_US/style.xml:912
+#: (para)
+d1155 1
+a1155 2
+#: en_US/style.xml:917
+#: (para)
+d1159 1
+a1159 2
+#: en_US/style.xml:926
+#: (term)
+d1161 1
+a1161 1
+msgstr ""
+d1163 1
+a1163 2
+#: en_US/style.xml:930
+#: (para)
+d1167 1
+a1167 2
+#: en_US/style.xml:936
+#: (para)
+d1171 1
+a1171 2
+#: en_US/style.xml:941
+#: (para)
+d1175 1
+a1175 2
+#: en_US/style.xml:953
+#: (term)
+d1177 1
+a1177 1
+msgstr ""
+d1179 2
+a1180 2
+#: en_US/style.xml:955
+#: (para)
+d1182 1
+a1182 1
+msgstr ""
+d1184 1
+a1184 2
+#: en_US/style.xml:960
+#: (para)
+d1188 1
+a1188 2
+#: en_US/style.xml:966
+#: (para)
+d1192 1
+a1192 2
+#: en_US/style.xml:971
+#: (para)
+d1196 1
+a1196 2
+#: en_US/style.xml:976
+#: (para)
+d1200 1
+a1200 2
+#: en_US/style.xml:982
+#: (para)
+d1204 1
+a1204 2
+#: en_US/style.xml:986
+#: (title)
+d1208 1
+a1208 2
+#: en_US/style.xml:987
+#: (para)
+d1212 1
+a1212 2
+#: en_US/style.xml:994
+#: (para)
+d1216 1
+a1216 2
+#: en_US/style.xml:999
+#: (para)
+d1220 1
+a1220 2
+#: en_US/style.xml:1004
+#: (para)
+d1224 1
+a1224 2
+#: en_US/style.xml:1010
+#: (para)
+d1228 1
+a1228 2
+#: en_US/style.xml:1015
+#: (para)
+d1232 1
+a1232 2
+#: en_US/style.xml:1020
+#: (para)
+d1236 1
+a1236 2
+#: en_US/style.xml:1029
+#: (term)
+d1238 1
+a1238 1
+msgstr ""
+d1240 1
+a1240 2
+#: en_US/style.xml:1031
+#: (para)
+d1244 1
+a1244 2
+#: en_US/style.xml:1039
+#: (term)
+d1246 1
+a1246 1
+msgstr ""
+d1248 2
+a1249 2
+#: en_US/style.xml:1041
+#: (para)
+d1251 1
+a1251 1
+msgstr ""
+d1253 1
+a1253 2
+#: en_US/style.xml:1046
+#: (para)
+d1256 1
+a1256 1
+msgstr "Um ein Verzeichnis hinzufügen"
+d1258 1
+a1258 2
+#: en_US/style.xml:1051
+#: (para)
+d1262 1
+a1262 2
+#: en_US/style.xml:1056
+#: (para)
+d1266 2
+a1267 2
+#: en_US/style.xml:1061
+#: (para)
+d1269 1
+a1269 1
+msgstr ""
+d1271 1
+a1271 2
+#: en_US/style.xml:1066
+#: (para)
+d1273 1
+a1273 1
+msgstr ""
+d1275 1
+a1275 2
+#: en_US/style.xml:1071
+#: (para)
+d1279 2
+a1280 2
+#: en_US/style.xml:1076
+#: (para)
+d1282 1
+a1282 1
+msgstr ""
+d1284 1
+a1284 2
+#: en_US/style.xml:1084
+#: (term)
+d1288 1
+a1288 2
+#: en_US/style.xml:1086
+#: (para)
+d1290 1
+a1290 1
+msgstr ""
+d1292 1
+a1292 2
+#: en_US/style.xml:1092
+#: (term)
+d1296 1
+a1296 2
+#: en_US/style.xml:1094
+#: (para)
+d1298 1
+a1298 1
+msgstr ""
+d1300 2
+a1301 2
+#: en_US/style.xml:1099
+#: (para)
+d1303 1
+a1303 1
+msgstr ""
+d1305 2
+a1306 2
+#: en_US/style.xml:1104
+#: (para)
+d1308 1
+a1308 1
+msgstr ""
+d1310 2
+a1311 2
+#: en_US/style.xml:1109
+#: (para)
+d1313 1
+a1313 1
+msgstr ""
+d1315 1
+a1315 2
+#: en_US/style.xml:1114
+#: (para)
+d1319 1
+a1319 2
+#: en_US/style.xml:1119
+#: (para)
+d1323 1
+a1323 2
+#: en_US/style.xml:1125
+#: (para)
+d1327 1
+a1327 2
+#: en_US/style.xml:1130
+#: (para)
+d1331 1
+a1331 2
+#: en_US/style.xml:1135
+#: (para)
+d1335 2
+a1336 3
+#: en_US/style.xml:1143
+#: (term) en_US/emacs-nxml.xml:86
+#: (title)
+d1340 1
+a1340 2
+#: en_US/style.xml:1145
+#: (para)
+d1342 1
+a1342 1
+msgstr ""
+d1344 1
+a1344 2
+#: en_US/style.xml:1151
+#: (term)
+d1346 1
+a1346 1
+msgstr ""
+d1348 1
+a1348 2
+#: en_US/style.xml:1153
+#: (para)
+d1352 1
+a1352 3
+#: en_US/style.xml:1160
+#: (term)
+#, fuzzy
+d1354 1
+a1354 1
+msgstr "Muster der Strichlinien"
+d1356 1
+a1356 2
+#: en_US/style.xml:1162
+#: (para)
+d1360 1
+a1360 2
+#: en_US/style.xml:1171
+#: (term)
+d1362 1
+a1362 1
+msgstr ""
+d1364 1
+a1364 2
+#: en_US/style.xml:1173
+#: (para)
+d1366 1
+a1366 1
+msgstr ""
+d1368 1
+a1368 2
+#: en_US/style.xml:1178
+#: (para)
+d1372 1
+a1372 2
+#: en_US/style.xml:1183
+#: (para)
+d1376 2
+a1377 2
+#: en_US/style.xml:1191
+#: (term)
+d1379 1
+a1379 1
+msgstr ""
+d1381 1
+a1381 2
+#: en_US/style.xml:1193
+#: (para)
+d1385 1
+a1385 2
+#: en_US/style.xml:1198
+#: (para)
+d1389 1
+a1389 2
+#: en_US/style.xml:1204
+#: (para)
+d1393 1
+a1393 2
+#: en_US/style.xml:1211
+#: (para)
+d1397 1
+a1397 2
+#: en_US/style.xml:1220
+#: (term)
+d1401 1
+a1401 2
+#: en_US/style.xml:1222
+#: (para)
+d1405 1
+a1405 2
+#: en_US/style.xml:1228
+#: (term)
+d1409 1
+a1409 2
+#: en_US/style.xml:1230
+#: (para)
+d1413 1
+a1413 2
+#: en_US/style.xml:1241
+#: (para)
+d1417 2
+a1418 2
+#: en_US/style.xml:1246
+#: (para)
+d1420 1
+a1420 1
+msgstr ""
+d1422 1
+a1422 2
+#: en_US/style.xml:1251
+#: (para)
+d1426 1
+a1426 2
+#: en_US/style.xml:1257
+#: (para)
+d1430 1
+a1430 2
+#: en_US/style.xml:1263
+#: (para)
+d1434 1
+a1434 2
+#: en_US/style.xml:1269
+#: (para)
+d1438 1
+a1438 2
+#: en_US/style.xml:1280
+#: (term)
+d1442 1
+a1442 2
+#: en_US/style.xml:1282
+#: (para)
+d1444 1
+a1444 1
+msgstr ""
+d1446 1
+a1446 2
+#: en_US/style.xml:1287
+#: (para)
+d1450 1
+a1450 3
+#: en_US/style.xml:1291
+#: (para)
+#, fuzzy
+d1452 1
+a1452 1
+msgstr "&Zu Telefonbuch hinzufügen..."
+d1454 1
+a1454 2
+#: en_US/style.xml:1296
+#: (para)
+d1458 1
+a1458 2
+#: en_US/style.xml:1305
+#: (para)
+d1461 1
+a1461 1
+msgstr "Zoomfaktor vergrößern oder verringern"
+d1463 1
+a1463 2
+#: en_US/style.xml:1310
+#: (para)
+d1467 1
+a1467 2
+#: en_US/style.xml:1317
+#: (para)
+d1471 1
+a1471 2
+#: en_US/style.xml:1322
+#: (para)
+d1475 1
+a1475 2
+#: en_US/style.xml:1327
+#: (para)
+d1478 1
+a1478 1
+msgstr "&Zu Telefonbuch hinzufügen..."
+d1480 1
+a1480 2
+#: en_US/style.xml:1332
+#: (para)
+d1484 1
+a1484 2
+#: en_US/style.xml:1337
+#: (para)
+d1488 1
+a1488 2
+#: en_US/style.xml:1342
+#: (para)
+d1492 1
+a1492 3
+#: en_US/style.xml:1351
+#: (para)
+#, fuzzy
+d1494 1
+a1494 1
+msgstr "Chat mit Kontakt"
+d1496 2
+a1497 2
+#: en_US/style.xml:1359
+#: (term)
+d1499 1
+a1499 1
+msgstr ""
+d1501 1
+a1501 2
+#: en_US/style.xml:1361
+#: (para)
+d1505 1
+a1505 2
+#: en_US/style.xml:1368
+#: (term)
+d1509 1
+a1509 2
+#: en_US/style.xml:1370
+#: (para)
+d1513 1
+a1513 2
+#: en_US/style.xml:1377
+#: (term)
+d1517 1
+a1517 2
+#: en_US/style.xml:1379
+#: (para)
+d1521 1
+a1521 2
+#: en_US/style.xml:1386
+#: (term)
+d1525 1
+a1525 2
+#: en_US/style.xml:1388
+#: (para)
+d1529 1
+a1529 2
+#: en_US/style.xml:1393
+#: (para)
+d1533 1
+a1533 2
+#: en_US/style.xml:1398
+#: (para)
+d1535 1
+a1535 1
+msgstr ""
+d1537 1
+a1537 2
+#: en_US/style.xml:1403
+#: (para)
+d1541 1
+a1541 2
+#: en_US/style.xml:1409
+#: (para)
+d1545 1
+a1545 2
+#: en_US/style.xml:1414
+#: (para)
+d1549 1
+a1549 2
+#: en_US/style.xml:1423
+#: (term)
+d1551 1
+a1551 1
+msgstr ""
+d1553 1
+a1553 2
+#: en_US/style.xml:1425
+#: (para)
+d1555 1
+a1555 1
+msgstr ""
+d1557 1
+a1557 2
+#: en_US/style.xml:1430
+#: (para)
+d1561 1
+a1561 2
+#: en_US/style.xml:1435
+#: (para)
+d1565 2
+a1566 2
+#: en_US/style.xml:1439
+#: (para)
+d1568 1
+a1568 1
+msgstr ""
+d1570 1
+a1570 2
+#: en_US/style.xml:1444
+#: (para)
+d1574 1
+a1574 2
+#: en_US/style.xml:1449
+#: (para)
+d1578 1
+a1578 2
+#: en_US/style.xml:1454
+#: (para)
+d1582 1
+a1582 2
+#: en_US/style.xml:1459
+#: (para)
+d1586 1
+a1586 2
+#: en_US/style.xml:1464
+#: (para)
+d1588 1
+a1588 1
+msgstr ""
+d1590 1
+a1590 2
+#: en_US/style.xml:1472
+#: (term)
+d1592 1
+a1592 1
+msgstr ""
+d1594 1
+a1594 2
+#: en_US/style.xml:1474
+#: (para)
+d1596 1
+a1596 1
+msgstr ""
+d1598 1
+a1598 2
+#: en_US/style.xml:1479
+#: (para)
+d1602 1
+a1602 2
+#: en_US/style.xml:1485
+#: (para)
+d1606 1
+a1606 2
+#: en_US/style.xml:1493
+#: (term)
+d1610 1
+a1610 2
+#: en_US/style.xml:1495
+#: (para)
+d1612 1
+a1612 1
+msgstr ""
+d1614 1
+a1614 2
+#: en_US/style.xml:1500
+#: (para)
+d1618 1
+a1618 2
+#: en_US/style.xml:1505
+#: (para)
+d1620 1
+a1620 1
+msgstr ""
+d1622 1
+a1622 2
+#: en_US/style.xml:1510
+#: (para)
+d1626 1
+a1626 2
+#: en_US/style.xml:1519
+#: (term)
+d1628 1
+a1628 1
+msgstr ""
+d1630 1
+a1630 2
+#: en_US/style.xml:1521
+#: (para)
+d1634 1
+a1634 3
+#: en_US/style.xml:1531
+#: (term)
+#, fuzzy
+d1636 1
+a1636 1
+msgstr "Zeige als Zahlenwerte"
+d1638 1
+a1638 2
+#: en_US/style.xml:1533
+#: (para)
+d1642 1
+a1642 2
+#: en_US/style.xml:1540
+#: (term)
+d1644 1
+a1644 1
+msgstr ""
+d1646 1
+a1646 2
+#: en_US/style.xml:1542
+#: (para)
+d1650 1
+a1650 2
+#: en_US/style.xml:1553
+#: (term)
+d1654 1
+a1654 2
+#: en_US/style.xml:1555
+#: (para)
+d1658 1
+a1658 2
+#: en_US/style.xml:1570
+#: (term)
+d1662 1
+a1662 2
+#: en_US/style.xml:1572
+#: (para)
+d1666 1
+a1666 2
+#: en_US/style.xml:1578
+#: (term)
+d1670 1
+a1670 2
+#: en_US/style.xml:1580
+#: (para)
+d1674 1
+a1674 2
+#: en_US/style.xml:1589
+#: (term)
+d1676 1
+a1676 1
+msgstr ""
+d1678 1
+a1678 2
+#: en_US/style.xml:1591
+#: (para)
+d1682 1
+a1682 2
+#: en_US/style.xml:1600
+#: (term)
+d1686 1
+a1686 2
+#: en_US/style.xml:1602
+#: (para)
+d1690 1
+a1690 2
+#: en_US/style.xml:1608
+#: (term)
+d1694 1
+a1694 2
+#: en_US/style.xml:1610
+#: (para)
+d1698 1
+a1698 2
+#: en_US/style.xml:1615
+#: (para)
+d1702 1
+a1702 2
+#: en_US/style.xml:1621
+#: (para)
+d1706 1
+a1706 2
+#: en_US/style.xml:1630
+#: (para)
+d1710 1
+a1710 2
+#: en_US/style.xml:1636
+#: (para)
+d1714 1
+a1714 2
+#: en_US/style.xml:1642
+#: (para)
+d1718 1
+a1718 3
+#: en_US/style.xml:1656
+#: (title)
+#, fuzzy
+d1720 1
+a1720 1
+msgstr "Komponier-Tipps"
+d1727 1
+a1727 2
+#: en_US/style.xml:1668
+#: (para)
+d1731 1
+a1731 2
+#: en_US/style.xml:1676
+#: (title)
+d1735 1
+a1735 2
+#: en_US/style.xml:1677
+#: (para)
+d1739 1
+a1739 2
+#: en_US/style.xml:1690
+#: (title)
+d1743 1
+a1743 2
+#: en_US/style.xml:1691
+#: (para)
+d1747 1
+a1747 2
+#: en_US/style.xml:1694
+#: (para)
+d1751 1
+a1751 2
+#: en_US/style.xml:1700
+#: (title)
+d1755 1
+a1755 2
+#: en_US/style.xml:1701
+#: (para)
+d1757 1
+a1757 1
+msgstr ""
+d1759 1
+a1759 2
+#: en_US/style.xml:1708
+#: (title)
+d1761 1
+a1761 1
+msgstr ""
+d1763 1
+a1763 2
+#: en_US/style.xml:1709
+#: (para)
+d1767 1
+a1767 2
+#: en_US/style.xml:1718
+#: (title)
+d1771 1
+a1771 2
+#: en_US/style.xml:1719
+#: (para)
+d1775 1
+a1775 2
+#: en_US/style.xml:1722
+#: (para)
+d1779 1
+a1779 2
+#: en_US/style.xml:1727
+#: (title)
+d1783 1
+a1783 2
+#: en_US/style.xml:1728
+#: (para)
+d1787 1
+a1787 2
+#: en_US/style.xml:1735
+#: (title)
+d1789 1
+a1789 1
+msgstr ""
+d1791 1
+a1791 2
+#: en_US/style.xml:1736
+#: (para)
+d1795 1
+a1795 2
+#: en_US/style.xml:1745
+#: (title)
+d1799 1
+a1799 2
+#: en_US/style.xml:1746
+#: (para)
+d1803 1
+a1803 2
+#: en_US/style.xml:1751
+#: (para)
+d1807 1
+a1807 2
+#: en_US/style.xml:1757
+#: (title)
+d1809 1
+a1809 1
+msgstr ""
+d1811 1
+a1811 2
+#: en_US/style.xml:1758
+#: (para)
+d1815 1
+a1815 2
+#: en_US/style.xml:1762
+#: (para)
+d1819 1
+a1819 2
+#: en_US/style.xml:1770
+#: (title)
+d1823 1
+a1823 2
+#: en_US/style.xml:1771
+#: (para)
+d1827 1
+a1827 2
+#: en_US/style.xml:1782
+#: (title)
+d1829 1
+a1829 1
+msgstr ""
+d1831 1
+a1831 2
+#: en_US/style.xml:1783
+#: (para)
+d1835 1
+a1835 2
+#: en_US/style.xml:1795
+#: (title)
+d1839 1
+a1839 2
+#: en_US/style.xml:1796
+#: (para)
+d1843 1
+a1843 2
+#: en_US/style.xml:1808
+#: (title)
+d1847 1
+a1847 2
+#: en_US/style.xml:1809
+#: (para)
+d1851 1
+a1851 2
+#: en_US/style.xml:1824
+#: (title)
+d1855 1
+a1855 2
+#: en_US/style.xml:1825
+#: (para)
+d1859 1
+a1859 2
+#: en_US/style.xml:1830
+#: (title)
+d1863 1
+a1863 2
+#: en_US/style.xml:1833
+#: (para)
+d1867 1
+a1867 2
+#: en_US/style.xml:1839
+#: (para)
+d1871 1
+a1871 2
+#: en_US/style.xml:1846
+#: (title)
+d1875 1
+a1875 2
+#: en_US/style.xml:1849
+#: (para)
+d1879 1
+a1879 2
+#: en_US/style.xml:1855
+#: (para)
+d1881 1
+a1881 1
+msgstr ""
+d1883 1
+a1883 2
+#: en_US/style.xml:1862
+#: (title)
+d1887 1
+a1887 2
+#: en_US/style.xml:1863
+#: (para)
+d1891 1
+a1891 2
+#: en_US/style.xml:1874
+#: (title)
+d1895 1
+a1895 2
+#: en_US/style.xml:1875
+#: (para)
+d1899 2
+a1900 2
+#: en_US/style.xml:1881
+#: (title) en_US/writing-guidelines.xml:268
+d1902 1
+a1902 1
+msgstr ""
+d1904 1
+a1904 2
+#: en_US/style.xml:1882
+#: (para)
+d1908 1
+a1908 2
+#: en_US/style.xml:1891
+#: (title)
+d1912 1
+a1912 2
+#: en_US/style.xml:1894
+#: (title)
+d1916 1
+a1916 2
+#: en_US/style.xml:1895
+#: (para)
+d1920 1
+a1920 2
+#: en_US/style.xml:1909
+#: (title)
+d1924 1
+a1924 2
+#: en_US/style.xml:1917
+#: (title)
+d1928 1
+a1928 2
+#: en_US/style.xml:1918
+#: (para)
+d1932 1
+a1932 2
+#: en_US/style.xml:1910
+#: (para)
+d1936 1
+a1936 2
+#: en_US/style.xml:1925
+#: (para)
+d1940 1
+a1940 2
+#: en_US/style.xml:1932
+#: (para)
+d1944 1
+a1944 2
+#: en_US/style.xml:1939
+#: (title)
+d1948 1
+a1948 2
+#: en_US/style.xml:1941
+#: (para)
+d1952 1
+a1952 2
+#: en_US/style.xml:1950
+#: (title)
+d1956 1
+a1956 2
+#: en_US/style.xml:1951
+#: (para)
+d1960 1
+a1960 2
+#: en_US/writing-guidelines.xml:11
+#: (title)
+d1964 2
+a1965 3
+#: en_US/writing-guidelines.xml:14
+#: (primary) en_US/writing-guidelines.xml:15
+#: (see)
+d1967 1
+a1967 1
+msgstr ""
+d1969 2
+a1970 3
+#: en_US/writing-guidelines.xml:19
+#: (primary) en_US/writing-guidelines.xml:26
+#: (secondary)
+d1974 1
+a1974 2
+#: en_US/writing-guidelines.xml:20
+#: (secondary)
+d1978 2
+a1979 3
+#: en_US/writing-guidelines.xml:21
+#: (seealso) en_US/writing-guidelines.xml:25
+#: (primary)
+d1981 1
+a1981 1
+msgstr ""
+d1983 1
+a1983 2
+#: en_US/writing-guidelines.xml:29
+#: (para)
+d1987 1
+a1987 2
+#: en_US/writing-guidelines.xml:32
+#: (para)
+d1991 1
+a1991 2
+#: en_US/writing-guidelines.xml:38
+#: (title)
+d1995 1
+a1995 2
+#: en_US/writing-guidelines.xml:40
+#: (title)
+d1999 1
+a1999 2
+#: en_US/writing-guidelines.xml:41
+#: (para)
+d2003 1
+a2003 2
+#: en_US/writing-guidelines.xml:47
+#: (title)
+d2007 1
+a2007 2
+#: en_US/writing-guidelines.xml:48
+#: (para)
+d2011 1
+a2011 2
+#: en_US/writing-guidelines.xml:51
+#: (para)
+d2015 1
+a2015 2
+#: en_US/writing-guidelines.xml:58
+#: (title)
+d2019 17
+a2035 17
+#: en_US/writing-guidelines.xml:61
+#: (primary) en_US/writing-guidelines.xml:74
+#: en_US/writing-guidelines.xml:275
+#: en_US/writing-guidelines.xml:280
+#: en_US/writing-guidelines.xml:285
+#: en_US/writing-guidelines.xml:290
+#: en_US/writing-guidelines.xml:295
+#: en_US/writing-guidelines.xml:300
+#: en_US/writing-guidelines.xml:306
+#: en_US/writing-guidelines.xml:312
+#: en_US/writing-guidelines.xml:318
+#: en_US/writing-guidelines.xml:324
+#: en_US/writing-guidelines.xml:350
+#: en_US/writing-guidelines.xml:355
+#: en_US/writing-guidelines.xml:360
+#: en_US/writing-guidelines.xml:365
+#: en_US/writing-guidelines.xml:370
+d2039 3
+a2041 3
+#: en_US/writing-guidelines.xml:62
+#: (secondary) en_US/writing-guidelines.xml:66
+#: (primary) en_US/writing-guidelines.xml:79
+d2043 1
+a2043 1
+msgstr ""
+d2045 1
+a2045 2
+#: en_US/writing-guidelines.xml:69
+#: (para)
+d2049 2
+a2050 2
+#: en_US/writing-guidelines.xml:75
+#: (secondary) en_US/writing-guidelines.xml:80
+d2054 1
+a2054 2
+#: en_US/writing-guidelines.xml:83
+#: (para)
+d2058 1
+a2058 2
+#: en_US/writing-guidelines.xml:87
+#: (para)
+d2062 1
+a2062 2
+#: en_US/writing-guidelines.xml:90
+#: (para)
+d2066 1
+a2066 2
+#: en_US/writing-guidelines.xml:96
+#: (para)
+d2070 1
+a2070 2
+#: en_US/writing-guidelines.xml:102
+#: (title)
+d2074 1
+a2074 2
+#: en_US/writing-guidelines.xml:111
+#: (title)
+d2078 1
+a2078 2
+#: en_US/writing-guidelines.xml:112
+#: (segtitle)
+d2082 1
+a2082 2
+#: en_US/writing-guidelines.xml:113
+#: (segtitle)
+d2086 1
+a2086 2
+#: en_US/writing-guidelines.xml:115
+#: (sgmltag)
+d2088 1
+a2088 1
+msgstr ""
+d2090 1
+a2090 2
+#: en_US/writing-guidelines.xml:116
+#: (literal)
+d2094 1
+a2094 2
+#: en_US/writing-guidelines.xml:119
+#: (sgmltag)
+d2098 1
+a2098 2
+#: en_US/writing-guidelines.xml:120
+#: (literal)
+d2102 1
+a2102 2
+#: en_US/writing-guidelines.xml:123
+#: (sgmltag)
+d2106 1
+a2106 2
+#: en_US/writing-guidelines.xml:124
+#: (literal)
+d2110 1
+a2110 2
+#: en_US/writing-guidelines.xml:127
+#: (sgmltag)
+d2112 1
+a2112 1
+msgstr ""
+d2114 1
+a2114 2
+#: en_US/writing-guidelines.xml:128
+#: (literal)
+d2118 2
+a2119 2
+#: en_US/writing-guidelines.xml:131
+#: (sgmltag) en_US/writing-guidelines.xml:235
+d2123 1
+a2123 2
+#: en_US/writing-guidelines.xml:132
+#: (literal)
+d2127 1
+a2127 2
+#: en_US/writing-guidelines.xml:135
+#: (sgmltag)
+d2129 1
+a2129 1
+msgstr ""
+d2131 1
+a2131 2
+#: en_US/writing-guidelines.xml:136
+#: (literal)
+d2135 1
+a2135 2
+#: en_US/writing-guidelines.xml:139
+#: (sgmltag)
+d2139 1
+a2139 2
+#: en_US/writing-guidelines.xml:140
+#: (literal)
+d2143 1
+a2143 2
+#: en_US/writing-guidelines.xml:143
+#: (sgmltag)
+d2147 1
+a2147 2
+#: en_US/writing-guidelines.xml:144
+#: (literal)
+d2151 1
+a2151 2
+#: en_US/writing-guidelines.xml:148
+#: (para)
+d2155 1
+a2155 2
+#: en_US/writing-guidelines.xml:157
+#: (title)
+d2159 1
+a2159 2
+#: en_US/writing-guidelines.xml:159
+#: (primary)
+d2163 1
+a2163 2
+#: en_US/writing-guidelines.xml:160
+#: (secondary)
+d2165 1
+a2165 1
+msgstr ""
+d2167 1
+a2167 2
+#: en_US/writing-guidelines.xml:163
+#: (para)
+d2171 2
+a2172 2
+#: en_US/writing-guidelines.xml:171
+#: (term)
+d2174 1
+a2174 1
+msgstr ""
+d2176 1
+a2176 2
+#: en_US/writing-guidelines.xml:173
+#: (para)
+d2180 1
+a2180 2
+#: en_US/writing-guidelines.xml:181
+#: (para)
+d2184 1
+a2184 2
+#: en_US/writing-guidelines.xml:184
+#: (segtitle)
+d2188 1
+a2188 2
+#: en_US/writing-guidelines.xml:185
+#: (segtitle)
+d2192 1
+a2192 2
+#: en_US/writing-guidelines.xml:189
+#: (trademark)
+d2194 1
+a2194 1
+msgstr ""
+d2196 1
+a2196 2
+#: en_US/writing-guidelines.xml:196
+#: (trademark)
+d2200 1
+a2200 2
+#: en_US/writing-guidelines.xml:202
+#: (trademark)
+d2202 1
+a2202 1
+msgstr ""
+d2204 1
+a2204 2
+#: en_US/writing-guidelines.xml:209
+#: (term)
+d2208 1
+a2208 2
+#: en_US/writing-guidelines.xml:211
+#: (para)
+d2212 1
+a2212 2
+#: en_US/writing-guidelines.xml:216
+#: (para)
+d2216 1
+a2216 2
+#: en_US/writing-guidelines.xml:223
+#: (sgmltag)
+d2220 1
+a2220 2
+#: en_US/writing-guidelines.xml:226
+#: (sgmltag)
+d2224 1
+a2224 2
+#: en_US/writing-guidelines.xml:229
+#: (sgmltag)
+d2228 1
+a2228 2
+#: en_US/writing-guidelines.xml:232
+#: (sgmltag)
+d2232 1
+a2232 2
+#: en_US/writing-guidelines.xml:241
+#: (term)
+d2236 1
+a2236 2
+#: en_US/writing-guidelines.xml:244
+#: (para)
+d2240 1
+a2240 2
+#: en_US/writing-guidelines.xml:252
+#: (term)
+d2244 1
+a2244 2
+#: en_US/writing-guidelines.xml:254
+#: (para)
+d2248 6
+a2253 6
+#: en_US/writing-guidelines.xml:271
+#: (primary) en_US/writing-guidelines.xml:301
+#: (secondary) en_US/writing-guidelines.xml:307
+#: en_US/writing-guidelines.xml:313
+#: en_US/writing-guidelines.xml:319
+#: en_US/writing-guidelines.xml:325
+d2255 1
+a2255 1
+msgstr ""
+d2257 3
+a2259 5
+#: en_US/writing-guidelines.xml:276
+#: (secondary)
+#: en_US/writing-guidelines.xml:302
+#: (tertiary)
+#: en_US/writing-guidelines.xml:371
+d2263 3
+a2265 5
+#: en_US/writing-guidelines.xml:281
+#: (secondary)
+#: en_US/writing-guidelines.xml:308
+#: (tertiary)
+#: en_US/writing-guidelines.xml:356
+d2269 3
+a2271 5
+#: en_US/writing-guidelines.xml:286
+#: (secondary)
+#: en_US/writing-guidelines.xml:314
+#: (tertiary)
+#: en_US/writing-guidelines.xml:351
+d2275 3
+a2277 5
+#: en_US/writing-guidelines.xml:291
+#: (secondary)
+#: en_US/writing-guidelines.xml:320
+#: (tertiary)
+#: en_US/writing-guidelines.xml:361
+d2281 3
+a2283 5
+#: en_US/writing-guidelines.xml:296
+#: (secondary)
+#: en_US/writing-guidelines.xml:326
+#: (tertiary)
+#: en_US/writing-guidelines.xml:366
+d2287 1
+a2287 2
+#: en_US/writing-guidelines.xml:329
+#: (para)
+d2291 1
+a2291 2
+#: en_US/writing-guidelines.xml:343
+#: (title)
+d2295 1
+a2295 2
+#: en_US/writing-guidelines.xml:374
+#: (para)
+d2299 1
+a2299 2
+#: en_US/writing-guidelines.xml:394
+#: (para)
+d2303 4
+a2306 4
+#: en_US/writing-guidelines.xml:403
+#: (title) en_US/emacs.xml:257
+#: en_US/emacs.xml:557
+#: en_US/emacs-nxml.xml:160
+d2310 4
+a2313 4
+#: en_US/writing-guidelines.xml:404
+#: (para) en_US/writing-guidelines.xml:424
+#: en_US/writing-guidelines.xml:434
+#: en_US/writing-guidelines.xml:444
+d2315 1
+a2315 1
+msgstr ""
+d2317 2
+a2318 2
+#: en_US/writing-guidelines.xml:413
+#: (title) en_US/emacs-nxml.xml:114
+d2322 1
+a2322 2
+#: en_US/writing-guidelines.xml:414
+#: (para)
+d2324 1
+a2324 1
+msgstr ""
+d2326 1
+a2326 2
+#: en_US/writing-guidelines.xml:423
+#: (title)
+d2330 2
+a2331 2
+#: en_US/writing-guidelines.xml:433
+#: (title) en_US/emacs-nxml.xml:96
+d2335 1
+a2335 2
+#: en_US/writing-guidelines.xml:443
+#: (title)
+d2339 1
+a2339 2
+#: en_US/writing-guidelines.xml:451
+#: (title)
+d2343 3
+a2345 3
+#: en_US/writing-guidelines.xml:454
+#: (primary) en_US/writing-guidelines.xml:459
+#: (see) en_US/writing-guidelines.xml:463
+d2349 1
+a2349 2
+#: en_US/writing-guidelines.xml:455
+#: (secondary)
+d2353 1
+a2353 2
+#: en_US/writing-guidelines.xml:458
+#: (primary)
+d2357 1
+a2357 2
+#: en_US/writing-guidelines.xml:462
+#: (primary)
+d2360 1
+a2360 1
+msgstr "Bildschirm-Input"
+d2362 1
+a2362 2
+#: en_US/writing-guidelines.xml:466
+#: (para)
+d2366 1
+a2366 2
+#: en_US/writing-guidelines.xml:474
+#: (para)
+d2370 1
+a2370 2
+#: en_US/writing-guidelines.xml:482
+#: (para)
+d2374 1
+a2374 2
+#: en_US/writing-guidelines.xml:487
+#: (term)
+d2378 1
+a2378 2
+#: en_US/writing-guidelines.xml:491
+#: (para)
+d2382 1
+a2382 2
+#: en_US/writing-guidelines.xml:498
+#: (para)
+d2386 1
+a2386 2
+#: en_US/writing-guidelines.xml:506
+#: (para)
+d2390 1
+a2390 2
+#: en_US/writing-guidelines.xml:518
+#: (para)
+d2394 1
+a2394 2
+#: en_US/writing-guidelines.xml:534
+#: (para)
+d2398 1
+a2398 2
+#: en_US/writing-guidelines.xml:545
+#: (para)
+d2402 1
+a2402 2
+#: en_US/writing-guidelines.xml:559
+#: (term)
+d2406 1
+a2406 2
+#: en_US/writing-guidelines.xml:561
+#: (para)
+d2410 1
+a2410 2
+#: en_US/writing-guidelines.xml:565
+#: (para)
+d2414 1
+a2414 2
+#: en_US/writing-guidelines.xml:571
+#: (para)
+d2418 1
+a2418 2
+#: en_US/writing-guidelines.xml:577
+#: (para)
+d2422 1
+a2422 2
+#: en_US/writing-guidelines.xml:581
+#: (para)
+d2426 1
+a2426 2
+#: en_US/writing-guidelines.xml:589
+#: (para)
+d2430 1
+a2430 2
+#: en_US/writing-guidelines.xml:594
+#: (title)
+d2434 1
+a2434 2
+#: en_US/writing-guidelines.xml:607
+#: (para)
+d2438 1
+a2438 2
+#: en_US/writing-guidelines.xml:609
+#: (userinput)
+d2443 1
+a2443 2
+#: en_US/writing-guidelines.xml:611
+#: (para)
+d2447 1
+a2447 2
+#: en_US/writing-guidelines.xml:613
+#: (computeroutput)
+d2460 1
+a2460 2
+#: en_US/module-struct.xml:12
+#: (title)
+d2464 1
+a2464 2
+#: en_US/module-struct.xml:13
+#: (para)
+d2468 1
+a2468 2
+#: en_US/module-struct.xml:19
+#: (title)
+d2472 1
+a2472 2
+#: en_US/module-struct.xml:20
+#: (para)
+d2476 1
+a2476 2
+#: en_US/module-struct.xml:25
+#: (title)
+d2480 1
+a2480 2
+#: en_US/module-struct.xml:46
+#: (title)
+d2484 1
+a2484 2
+#: en_US/module-struct.xml:47
+#: (segtitle)
+d2488 1
+a2488 2
+#: en_US/module-struct.xml:48
+#: (segtitle)
+d2492 1
+a2492 2
+#: en_US/module-struct.xml:49
+#: (segtitle)
+d2496 1
+a2496 2
+#: en_US/module-struct.xml:51
+#: (seg)
+d2500 3
+a2502 3
+#: en_US/module-struct.xml:52
+#: (seg) en_US/module-struct.xml:89
+#: en_US/module-struct.xml:96
+d2506 2
+a2507 3
+#: en_US/module-struct.xml:55
+#: (filename) en_US/module-struct.xml:177
+#: (systemitem)
+d2511 1
+a2511 2
+#: en_US/module-struct.xml:59
+#: (firstterm)
+d2515 1
+a2515 2
+#: en_US/module-struct.xml:60
+#: (para)
+d2519 1
+a2519 2
+#: en_US/module-struct.xml:53
+#: (seg)
+d2523 1
+a2523 2
+#: en_US/module-struct.xml:68
+#: (seg)
+d2527 2
+a2528 2
+#: en_US/module-struct.xml:69
+#: (seg) en_US/module-struct.xml:79
+d2532 2
+a2533 2
+#: en_US/module-struct.xml:70
+#: (filename) en_US/module-struct.xml:74
+d2537 1
+a2537 2
+#: en_US/module-struct.xml:70
+#: (seg)
+d2541 1
+a2541 2
+#: en_US/module-struct.xml:78
+#: (seg)
+d2545 2
+a2546 2
+#: en_US/module-struct.xml:80
+#: (filename) en_US/module-struct.xml:184
+d2550 1
+a2550 2
+#: en_US/module-struct.xml:82
+#: (acronym)
+d2554 10
+a2563 3
+#: en_US/module-struct.xml:80
+#: (seg)
+msgid "The <placeholder-1/> directory contains specially formatted Portable Object, or <placeholder-2/>, files created and used by translators. The Fedora Documentation Project build tools use these files to create translated versions of documents. The translated documents are not stored in CVS; they are created as needed from these PO files."
+d2566 2
+a2567 3
+#: en_US/module-struct.xml:88
+#: (seg) en_US/module-struct.xml:90
+#: (filename)
+d2571 1
+a2571 2
+#: en_US/module-struct.xml:90
+#: (seg)
+d2575 2
+a2576 2
+#: en_US/module-struct.xml:95
+#: (filename) en_US/module-struct.xml:97
+d2580 1
+a2580 2
+#: en_US/module-struct.xml:97
+#: (seg)
+d2584 1
+a2584 2
+#: en_US/module-struct.xml:102
+#: (title)
+d2588 1
+a2588 2
+#: en_US/module-struct.xml:103
+#: (para)
+d2592 1
+a2592 2
+#: en_US/module-struct.xml:111
+#: (title)
+d2596 1
+a2596 2
+#: en_US/module-struct.xml:116
+#: (para)
+d2600 1
+a2600 2
+#: en_US/module-struct.xml:112
+#: (para)
+d2604 1
+a2604 2
+#: en_US/module-struct.xml:128
+#: (title)
+d2608 1
+a2608 2
+#: en_US/module-struct.xml:129
+#: (para)
+d2612 1
+a2612 2
+#: en_US/module-struct.xml:135
+#: (para)
+d2616 1
+a2616 2
+#: en_US/module-struct.xml:141
+#: (title)
+d2620 1
+a2620 2
+#: en_US/module-struct.xml:158
+#: (para)
+d2624 1
+a2624 2
+#: en_US/module-struct.xml:164
+#: (title)
+d2628 1
+a2628 2
+#: en_US/module-struct.xml:165
+#: (segtitle)
+d2632 2
+a2633 2
+#: en_US/module-struct.xml:166
+#: (segtitle) en_US/module-struct.xml:244
+d2637 1
+a2637 2
+#: en_US/module-struct.xml:168
+#: (systemitem)
+d2641 1
+a2641 2
+#: en_US/module-struct.xml:169
+#: (seg)
+d2645 1
+a2645 2
+#: en_US/module-struct.xml:174
+#: (systemitem)
+d2649 1
+a2649 2
+#: en_US/module-struct.xml:175
+#: (seg)
+d2653 1
+a2653 12
+#: en_US/module-struct.xml:180
+#: (systemitem)
+msgid "OTHERS"
+msgstr "OTHERS"
+
+#: en_US/module-struct.xml:181
+#: (seg)
+msgid "This variable contains a listing of ISO codes for any other versions into which the document has been translated. The module must contain a <placeholder-1/> directory and a PO file for any indicated additional languages."
+msgstr ""
+
+#: en_US/module-struct.xml:188
+#: (systemitem)
+d2657 1
+a2657 2
+#: en_US/module-struct.xml:189
+#: (seg)
+d2661 1
+a2661 2
+#: en_US/module-struct.xml:198
+#: (systemitem)
+d2665 1
+a2665 2
+#: en_US/module-struct.xml:201
+#: (systemitem)
+d2669 1
+a2669 2
+#: en_US/module-struct.xml:206
+#: (systemitem)
+d2673 1
+a2673 2
+#: en_US/module-struct.xml:199
+#: (seg)
+d2677 2
+a2678 2
+#: en_US/module-struct.xml:212
+#: (title)
+d2680 1
+a2680 1
+msgstr ""
+d2682 1
+a2682 2
+#: en_US/module-struct.xml:213
+#: (para)
+d2686 1
+a2686 2
+#: en_US/module-struct.xml:217
+#: (para)
+d2690 1
+a2690 2
+#: en_US/module-struct.xml:226
+#: (title)
+d2694 1
+a2694 2
+#: en_US/module-struct.xml:227
+#: (para)
+d2698 1
+a2698 2
+#: en_US/module-struct.xml:236
+#: (title)
+d2702 1
+a2702 2
+#: en_US/module-struct.xml:237
+#: (para)
+d2706 1
+a2706 2
+#: en_US/module-struct.xml:242
+#: (title)
+d2710 1
+a2710 2
+#: en_US/module-struct.xml:243
+#: (segtitle)
+d2714 1
+a2714 2
+#: en_US/module-struct.xml:246
+#: (systemitem)
+d2718 4
+a2721 4
+#: en_US/module-struct.xml:247
+#: (abbrev) en_US/module-struct.xml:258
+#: en_US/module-struct.xml:283
+#: en_US/module-struct.xml:288
+d2725 2
+a2726 2
+#: en_US/module-struct.xml:251
+#: (systemitem) en_US/module-struct.xml:261
+d2730 2
+a2731 2
+#: en_US/module-struct.xml:252
+#: (systemitem) en_US/module-struct.xml:262
+d2735 1
+a2735 2
+#: en_US/module-struct.xml:250
+#: (filename)
+d2739 1
+a2739 2
+#: en_US/module-struct.xml:247
+#: (seg)
+d2743 1
+a2743 2
+#: en_US/module-struct.xml:257
+#: (systemitem)
+d2747 1
+a2747 2
+#: en_US/module-struct.xml:260
+#: (filename)
+d2751 1
+a2751 2
+#: en_US/module-struct.xml:258
+#: (seg)
+d2755 1
+a2755 2
+#: en_US/module-struct.xml:266
+#: (systemitem)
+d2759 4
+a2762 4
+#: en_US/module-struct.xml:267
+#: (abbrev) en_US/module-struct.xml:268
+#: en_US/module-struct.xml:284
+#: en_US/module-struct.xml:289
+d2766 1
+a2766 2
+#: en_US/module-struct.xml:267
+#: (seg)
+d2770 1
+a2770 2
+#: en_US/module-struct.xml:272
+#: (systemitem)
+d2774 1
+a2774 2
+#: en_US/module-struct.xml:273
+#: (command)
+d2778 1
+a2778 2
+#: en_US/module-struct.xml:273
+#: (seg)
+d2782 1
+a2782 2
+#: en_US/module-struct.xml:277
+#: (systemitem)
+d2786 1
+a2786 2
+#: en_US/module-struct.xml:278
+#: (seg)
+d2790 2
+a2791 3
+#: en_US/module-struct.xml:281
+#: (systemitem) en_US/module-struct.xml:290
+#: (filename)
+d2795 1
+a2795 2
+#: en_US/module-struct.xml:283
+#: (emphasis)
+d2799 1
+a2799 2
+#: en_US/module-struct.xml:282
+#: (seg)
+d2803 1
+a2803 2
+#: en_US/module-struct.xml:287
+#: (systemitem)
+d2807 1
+a2807 2
+#: en_US/module-struct.xml:288
+#: (seg)
+d2811 2
+a2812 2
+#: en_US/module-struct.xml:295
+#: (title)
+d2814 1
+a2814 1
+msgstr ""
+d2816 1
+a2816 2
+#: en_US/module-struct.xml:296
+#: (para)
+d2820 1
+a2820 2
+#: en_US/module-struct.xml:300
+#: (title)
+d2824 1
+a2824 2
+#: en_US/module-struct.xml:301
+#: (para)
+d2828 1
+a2828 2
+#: en_US/module-struct.xml:309
+#: (para)
+d2832 1
+a2832 2
+#: en_US/module-struct.xml:316
+#: (title)
+d2834 1
+a2834 1
+msgstr ""
+d2836 1
+a2836 2
+#: en_US/module-struct.xml:317
+#: (para)
+d2840 1
+a2840 2
+#: en_US/module-struct.xml:324
+#: (para)
+d2844 1
+a2844 2
+#: en_US/module-struct.xml:338
+#: (para)
+d2848 1
+a2848 2
+#: en_US/module-struct.xml:344
+#: (para)
+d2852 1
+a2852 2
+#: en_US/module-struct.xml:354
+#: (para)
+d2856 1
+a2856 2
+#: en_US/module-struct.xml:363
+#: (para)
+d2860 1
+a2860 2
+#: en_US/module-struct.xml:369
+#: (title)
+d2864 1
+a2864 2
+#: en_US/module-struct.xml:376
+#: (title)
+d2868 1
+a2868 2
+#: en_US/module-struct.xml:377
+#: (para)
+d2872 1
+a2872 2
+#: en_US/module-struct.xml:381
+#: (para)
+d2876 1
+a2876 2
+#: en_US/module-struct.xml:385
+#: (para)
+d2880 1
+a2880 2
+#: en_US/module-struct.xml:395
+#: (title)
+d2884 1
+a2884 2
+#: en_US/module-struct.xml:396
+#: (para)
+d2888 1
+a2888 2
+#: en_US/module-struct.xml:403
+#: (para)
+d2892 1
+a2892 2
+#: en_US/module-struct.xml:409
+#: (para)
+d2896 1
+a2896 2
+#: en_US/module-struct.xml:413
+#: (para)
+d2900 1
+a2900 2
+#: en_US/module-struct.xml:418
+#: (para)
+d2904 1
+a2904 2
+#: en_US/module-struct.xml:421
+#: (replaceable)
+d2908 1
+a2908 2
+#: en_US/module-struct.xml:421
+#: (screen)
+d2913 1
+a2913 2
+#: en_US/intro.xml:13
+#: (title)
+d2917 1
+a2917 2
+#: en_US/intro.xml:15
+#: (para)
+d2921 1
+a2921 2
+#: en_US/intro.xml:23
+#: (para)
+d2925 1
+a2925 2
+#: en_US/intro.xml:26
+#: (para)
+d2929 1
+a2929 2
+#: en_US/intro.xml:30
+#: (para)
+d2933 1
+a2933 2
+#: en_US/intro.xml:34
+#: (para)
+d2937 2
+a2938 3
+#: en_US/intro.xml:43
+#: (para)
+msgid "This document explains the tools used by the Fedora Documentation Project and provides writing and tagging guidelines to make Fedora documentation is consistent and easy-to-follow."
+d2941 1
+a2941 2
+#: en_US/getting-files.xml:12
+#: (title)
+d2943 1
+a2943 1
+msgstr ""
+d2945 1
+a2945 2
+#: en_US/getting-files.xml:14
+#: (para)
+d2949 1
+a2949 2
+#: en_US/getting-files.xml:20
+#: (title)
+d2953 1
+a2953 2
+#: en_US/getting-files.xml:22
+#: (para)
+d2957 1
+a2957 2
+#: en_US/getting-files.xml:28
+#: (userinput)
+d2962 1
+a2962 2
+#: en_US/getting-files.xml:31
+#: (para)
+d2966 1
+a2966 2
+#: en_US/getting-files.xml:37
+#: (userinput)
+d2971 1
+a2971 2
+#: en_US/getting-files.xml:40
+#: (para)
+d2975 1
+a2975 2
+#: en_US/getting-files.xml:44
+#: (userinput)
+d2980 1
+a2980 2
+#: en_US/getting-files.xml:48
+#: (title)
+d2984 1
+a2984 2
+#: en_US/getting-files.xml:50
+#: (para)
+d2988 1
+a2988 2
+#: en_US/getting-files.xml:59
+#: (para)
+d2992 1
+a2992 2
+#: en_US/getting-files.xml:76
+#: (para)
+d2996 1
+a2996 2
+#: en_US/getting-files.xml:85
+#: (para)
+d3000 1
+a3000 2
+#: en_US/getting-files.xml:91
+#: (para)
+d3004 1
+a3004 2
+#: en_US/getting-files.xml:97
+#: (title)
+d3008 1
+a3008 2
+#: en_US/getting-files.xml:98
+#: (para)
+d3012 2
+a3013 2
+#: en_US/getting-files.xml:106
+#: (title)
+d3015 1
+a3015 1
+msgstr ""
+d3017 1
+a3017 2
+#: en_US/getting-files.xml:107
+#: (para)
+d3021 1
+a3021 2
+#: en_US/getting-files.xml:115
+#: (para)
+d3025 1
+a3025 2
+#: en_US/getting-files.xml:122
+#: (para)
+d3029 1
+a3029 2
+#: en_US/getting-files.xml:125
+#: (title)
+d3033 1
+a3033 2
+#: en_US/getting-files.xml:126
+#: (userinput)
+d3038 1
+a3038 2
+#: en_US/getting-files.xml:145
+#: (para)
+d3042 1
+a3042 2
+#: en_US/getting-files.xml:150
+#: (para)
+d3046 1
+a3046 2
+#: en_US/getting-files.xml:157
+#: (title)
+d3050 1
+a3050 2
+#: en_US/getting-files.xml:158
+#: (para)
+d3054 1
+a3054 2
+#: en_US/getting-files.xml:164
+#: (title)
+d3058 1
+a3058 2
+#: en_US/getting-files.xml:165
+#: (para)
+d3062 1
+a3062 2
+#: en_US/getting-files.xml:174
+#: (title)
+d3064 1
+a3064 1
+msgstr ""
+d3066 1
+a3066 2
+#: en_US/getting-files.xml:175
+#: (para)
+d3070 1
+a3070 2
+#: en_US/getting-files.xml:181
+#: (title)
+d3074 1
+a3074 2
+#: en_US/getting-files.xml:182
+#: (segtitle)
+d3078 1
+a3078 2
+#: en_US/getting-files.xml:183
+#: (segtitle)
+d3082 1
+a3082 2
+#: en_US/getting-files.xml:185
+#: (seg)
+d3086 1
+a3086 2
+#: en_US/getting-files.xml:186
+#: (seg)
+d3090 1
+a3090 2
+#: en_US/getting-files.xml:190
+#: (application)
+d3094 1
+a3094 2
+#: en_US/getting-files.xml:189
+#: (seg)
+d3096 1
+a3096 1
+msgstr ""
+d3098 1
+a3098 2
+#: en_US/getting-files.xml:191
+#: (seg)
+d3102 1
+a3102 2
+#: en_US/getting-files.xml:194
+#: (application)
+d3106 1
+a3106 2
+#: en_US/getting-files.xml:194
+#: (seg)
+d3110 1
+a3110 2
+#: en_US/getting-files.xml:195
+#: (seg)
+d3114 1
+a3114 2
+#: en_US/getting-files.xml:200
+#: (title)
+d3118 1
+a3118 2
+#: en_US/getting-files.xml:201
+#: (para)
+d3122 1
+a3122 2
+#: en_US/getting-files.xml:205
+#: (para)
+d3126 1
+a3126 2
+#: en_US/getting-files.xml:210
+#: (para)
+d3130 1
+a3130 2
+#: en_US/getting-files.xml:215
+#: (para)
+d3134 1
+a3134 2
+#: en_US/emacs.xml:13
+#: (title)
+d3138 1
+a3138 2
+#: en_US/emacs.xml:16
+#: (primary)
+d3142 10
+a3151 11
+#: en_US/emacs.xml:20
+#: (primary) en_US/emacs.xml:24
+#: en_US/emacs.xml:43
+#: en_US/emacs.xml:224
+#: en_US/emacs.xml:233
+#: en_US/emacs.xml:238
+#: en_US/emacs.xml:243
+#: en_US/emacs.xml:518
+#: (application)
+#: en_US/emacs-nxml.xml:18
+#: en_US/emacs-nxml.xml:22
+d3155 1
+a3155 2
+#: en_US/emacs.xml:25
+#: (secondary)
+d3159 1
+a3159 2
+#: en_US/emacs.xml:28
+#: (para)
+d3163 1
+a3163 2
+#: en_US/emacs.xml:35
+#: (title)
+d3167 1
+a3167 2
+#: en_US/emacs.xml:36
+#: (para)
+d3171 1
+a3171 2
+#: en_US/emacs.xml:37
+#: (userinput)
+d3176 1
+a3176 2
+#: en_US/emacs.xml:40
+#: (title)
+d3180 1
+a3180 2
+#: en_US/emacs.xml:48
+#: (filename)
+d3184 1
+a3184 2
+#: en_US/emacs.xml:51
+#: (para)
+d3188 1
+a3188 2
+#: en_US/emacs.xml:181
+#: (para)
+d3192 1
+a3192 2
+#: en_US/emacs.xml:192
+#: (para)
+d3196 1
+a3196 2
+#: en_US/emacs.xml:221
+#: (title)
+d3198 1
+a3198 1
+msgstr ""
+d3200 1
+a3200 2
+#: en_US/emacs.xml:225
+#: (secondary)
+d3202 1
+a3202 1
+msgstr ""
+d3204 1
+a3204 2
+#: en_US/emacs.xml:229
+#: (filename)
+d3208 1
+a3208 2
+#: en_US/emacs.xml:234
+#: (secondary)
+d3212 1
+a3212 2
+#: en_US/emacs.xml:239
+#: (secondary)
+d3216 1
+a3216 2
+#: en_US/emacs.xml:244
+#: (secondary)
+d3220 1
+a3220 2
+#: en_US/emacs.xml:247
+#: (para)
+d3224 1
+a3224 2
+#: en_US/emacs.xml:253
+#: (para)
+d3228 1
+a3228 2
+#: en_US/emacs.xml:258
+#: (para)
+d3232 1
+a3232 2
+#: en_US/emacs.xml:270
+#: (para)
+d3236 1
+a3236 2
+#: en_US/emacs.xml:273
+#: (command)
+d3240 1
+a3240 2
+#: en_US/emacs.xml:274
+#: (para)
+d3244 1
+a3244 2
+#: en_US/emacs.xml:395
+#: (title)
+d3248 1
+a3248 2
+#: en_US/emacs.xml:397
+#: (para)
+d3252 1
+a3252 2
+#: en_US/emacs.xml:403
+#: (title)
+d3256 1
+a3256 2
+#: en_US/emacs.xml:404
+#: (segtitle)
+d3260 1
+a3260 2
+#: en_US/emacs.xml:405
+#: (segtitle)
+d3264 26
+a3289 7
+#: en_US/emacs.xml:408
+#: (keycap) en_US/emacs.xml:488
+#: en_US/emacs.xml:493
+#: en_US/emacs.xml:498
+#: en_US/emacs.xml:522
+msgid "Meta"
+msgstr "Meta"
+d3291 10
+a3300 8
+#: en_US/emacs.xml:408
+#: (keycap) en_US/emacs.xml:493
+#: en_US/emacs.xml:498
+#: en_US/emacs.xml:503
+#: en_US/emacs.xml:509
+#: en_US/emacs.xml:515
+msgid "x"
+msgstr "x"
+d3302 12
+a3313 5
+#: en_US/emacs.xml:409
+#: (keycap) en_US/emacs.xml:494
+#: en_US/emacs.xml:499
+msgid "Enter"
+msgstr "Enter"
+d3315 1
+a3315 7
+#: en_US/emacs.xml:407
+#: (seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, <placeholder-3/>"
+
+#: en_US/emacs.xml:410
+#: (seg)
+d3319 2
+a3320 37
+#: en_US/emacs.xml:425
+#: (keycap) en_US/emacs.xml:431
+#: en_US/emacs.xml:438
+#: en_US/emacs.xml:443
+#: en_US/emacs.xml:448
+#: en_US/emacs.xml:453
+#: en_US/emacs.xml:458
+#: en_US/emacs.xml:463
+#: en_US/emacs.xml:468
+#: en_US/emacs.xml:473
+#: en_US/emacs.xml:478
+#: en_US/emacs.xml:483
+#: en_US/emacs.xml:503
+#: en_US/emacs.xml:504
+#: en_US/emacs.xml:509
+#: en_US/emacs.xml:510
+#: en_US/emacs.xml:515
+#: en_US/emacs.xml:516
+#: en_US/emacs.xml:527
+#: en_US/emacs.xml:528
+#: en_US/emacs.xml:535
+#: en_US/emacs.xml:537
+msgid "Ctrl"
+msgstr "Strg"
+
+#: en_US/emacs.xml:425
+#: (keycap) en_US/emacs.xml:431
+#: en_US/emacs.xml:443
+#: en_US/emacs.xml:516
+#: en_US/emacs.xml:527
+#: en_US/emacs.xml:535
+#: en_US/emacs.xml:537
+msgid "c"
+msgstr "c"
+
+#: en_US/emacs.xml:426
+#: (keycap) en_US/emacs.xml:432
+d3324 2
+a3325 2
+#: en_US/emacs.xml:427
+#: (keycap) en_US/emacs.xml:433
+d3329 2
+a3330 2
+#: en_US/emacs.xml:427
+#: (keycap) en_US/emacs.xml:434
+d3334 1
+a3334 2
+#: en_US/emacs.xml:425
+#: (seg)
+d3338 1
+a3338 2
+#: en_US/emacs.xml:428
+#: (seg)
+d3340 1
+a3340 1
+msgstr ""
+d3342 1
+a3342 2
+#: en_US/emacs.xml:431
+#: (seg)
+d3346 1
+a3346 2
+#: en_US/emacs.xml:435
+#: (seg)
+d3350 1
+a3350 2
+#: en_US/emacs.xml:438
+#: (keycap)
+d3354 2
+a3355 2
+#: en_US/emacs.xml:440
+#: (seg)
+d3357 1
+a3357 1
+msgstr ""
+d3359 1
+a3359 2
+#: en_US/emacs.xml:444
+#: (keycap)
+d3363 1
+a3363 2
+#: en_US/emacs.xml:443
+#: (seg)
+d3367 1
+a3367 2
+#: en_US/emacs.xml:445
+#: (seg)
+d3371 2
+a3372 2
+#: en_US/emacs.xml:448
+#: (keycap) en_US/emacs.xml:528
+d3376 1
+a3376 2
+#: en_US/emacs.xml:450
+#: (seg)
+d3380 1
+a3380 2
+#: en_US/emacs.xml:453
+#: (keycap)
+d3384 1
+a3384 2
+#: en_US/emacs.xml:455
+#: (seg)
+d3388 1
+a3388 2
+#: en_US/emacs.xml:458
+#: (keycap)
+d3392 1
+a3392 2
+#: en_US/emacs.xml:460
+#: (seg)
+d3396 1
+a3396 2
+#: en_US/emacs.xml:463
+#: (keycap)
+d3400 1
+a3400 2
+#: en_US/emacs.xml:465
+#: (seg)
+d3404 1
+a3404 2
+#: en_US/emacs.xml:468
+#: (keycap)
+d3408 1
+a3408 2
+#: en_US/emacs.xml:470
+#: (seg)
+d3412 1
+a3412 2
+#: en_US/emacs.xml:473
+#: (keycap)
+d3416 1
+a3416 2
+#: en_US/emacs.xml:475
+#: (seg)
+d3420 2
+a3421 2
+#: en_US/emacs.xml:478
+#: (keycap) en_US/emacs.xml:510
+d3425 1
+a3425 2
+#: en_US/emacs.xml:480
+#: (seg)
+d3429 1
+a3429 2
+#: en_US/emacs.xml:483
+#: (keycap)
+d3433 1
+a3433 2
+#: en_US/emacs.xml:485
+#: (seg)
+d3437 8
+a3444 2
+#: en_US/emacs.xml:488
+#: (keycap)
+d3448 3
+a3450 2
+#: en_US/emacs.xml:490
+#: (seg) en_US/emacs.xml:495
+d3452 14
+a3465 1
+msgstr ""
+d3467 1
+a3467 2
+#: en_US/emacs.xml:493
+#: (seg)
+d3471 1
+a3471 2
+#: en_US/emacs.xml:498
+#: (seg)
+d3475 2
+a3476 2
+#: en_US/emacs.xml:500
+#: (seg)
+d3478 1
+a3478 1
+msgstr ""
+d3480 1
+a3480 2
+#: en_US/emacs.xml:504
+#: (keycap)
+d3484 1
+a3484 10
+#: en_US/emacs.xml:503
+#: (seg) en_US/emacs.xml:509
+#: en_US/emacs.xml:515
+#: en_US/emacs.xml:527
+#: en_US/emacs.xml:535
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+
+#: en_US/emacs.xml:506
+#: (seg)
+d3488 1
+a3488 2
+#: en_US/emacs.xml:512
+#: (seg)
+d3492 1
+a3492 2
+#: en_US/emacs.xml:518
+#: (seg)
+d3496 1
+a3496 2
+#: en_US/emacs.xml:522
+#: (keycap)
+d3500 1
+a3500 2
+#: en_US/emacs.xml:524
+#: (seg)
+d3504 1
+a3504 2
+#: en_US/emacs.xml:531
+#: (computeroutput)
+d3509 1
+a3509 2
+#: en_US/emacs.xml:532
+#: (computeroutput)
+d3514 1
+a3514 2
+#: en_US/emacs.xml:530
+#: (seg)
+d3518 1
+a3518 2
+#: en_US/emacs.xml:539
+#: (seg)
+d3521 1
+a3521 1
+msgstr "_Aktuelle Matrix bearbeiten"
+d3523 2
+a3524 2
+#: en_US/emacs.xml:545
+#: (title) en_US/emacs-nxml.xml:77
+d3528 1
+a3528 2
+#: en_US/emacs.xml:547
+#: (para)
+d3532 1
+a3532 3
+#: en_US/emacs.xml:554
+#: (title)
+#, fuzzy
+d3534 1
+a3534 1
+msgstr "Vervollständigungsmodell"
+d3536 1
+a3536 2
+#: en_US/emacs.xml:558
+#: (para)
+d3540 1
+a3540 2
+#: en_US/emacs.xml:562
+#: (para)
+d3544 1
+a3544 2
+#: en_US/emacs.xml:569
+#: (prompt)
+d3548 1
+a3548 2
+#: en_US/emacs.xml:571
+#: (para)
+d3552 1
+a3552 2
+#: en_US/emacs.xml:580
+#: (para)
+d3556 1
+a3556 3
+#: en_US/emacs.xml:597
+#: (title)
+#, fuzzy
+d3558 1
+a3558 1
+msgstr "Kürzelausdruck"
+d3560 1
+a3560 2
+#: en_US/emacs.xml:599
+#: (para)
+d3564 1
+a3564 2
+#: en_US/emacs.xml:611
+#: (title)
+d3568 1
+a3568 2
+#: en_US/emacs.xml:614
+#: (title)
+d3572 1
+a3572 2
+#: en_US/emacs.xml:615
+#: (para)
+d3576 1
+a3576 2
+#: en_US/emacs.xml:625
+#: (title)
+d3580 1
+a3580 2
+#: en_US/emacs.xml:626
+#: (para)
+d3584 1
+a3584 2
+#: en_US/emacs.xml:637
+#: (title)
+d3588 1
+a3588 2
+#: en_US/emacs.xml:638
+#: (para)
+d3592 1
+a3592 2
+#: en_US/emacs.xml:648
+#: (title)
+d3596 1
+a3596 2
+#: en_US/emacs.xml:649
+#: (para)
+d3600 1
+a3600 2
+#: en_US/emacs.xml:663
+#: (title)
+d3604 1
+a3604 2
+#: en_US/emacs.xml:664
+#: (para)
+d3608 2
+a3609 2
+#: en_US/emacs.xml:682
+#: (title) en_US/emacs-nxml.xml:127
+d3613 1
+a3613 2
+#: en_US/emacs.xml:684
+#: (para)
+d3617 2
+a3618 2
+#: en_US/emacs.xml:692
+#: (citetitle) en_US/emacs-nxml.xml:143
+d3622 1
+a3622 2
+#: en_US/emacs.xml:696
+#: (para)
+d3626 1
+a3626 2
+#: en_US/emacs.xml:703
+#: (para)
+d3630 1
+a3630 2
+#: en_US/emacs.xml:709
+#: (para)
+d3634 1
+a3634 2
+#: en_US/emacs.xml:718
+#: (citetitle)
+d3638 1
+a3638 2
+#: en_US/emacs-nxml.xml:11
+#: (title)
+d3642 2
+a3643 2
+#: en_US/emacs-nxml.xml:14
+#: (primary) en_US/emacs-nxml.xml:51
+d3647 1
+a3647 2
+#: en_US/emacs-nxml.xml:23
+#: (secondary)
+d3651 1
+a3651 2
+#: en_US/emacs-nxml.xml:26
+#: (para)
+d3655 1
+a3655 2
+#: en_US/emacs-nxml.xml:35
+#: (title)
+d3657 1
+a3657 1
+msgstr ""
+d3659 1
+a3659 2
+#: en_US/emacs-nxml.xml:36
+#: (para)
+d3663 1
+a3663 2
+#: en_US/emacs-nxml.xml:48
+#: (title)
+d3667 1
+a3667 2
+#: en_US/emacs-nxml.xml:52
+#: (secondary)
+d3671 1
+a3671 2
+#: en_US/emacs-nxml.xml:56
+#: (primary)
+d3675 1
+a3675 2
+#: en_US/emacs-nxml.xml:59
+#: (para)
+d3679 1
+a3679 2
+#: en_US/emacs-nxml.xml:69
+#: (para)
+d3683 1
+a3683 2
+#: en_US/emacs-nxml.xml:79
+#: (para)
+d3687 1
+a3687 2
+#: en_US/emacs-nxml.xml:88
+#: (para)
+d3691 1
+a3691 2
+#: en_US/emacs-nxml.xml:97
+#: (para)
+d3695 1
+a3695 2
+#: en_US/emacs-nxml.xml:104
+#: (para)
+d3699 1
+a3699 2
+#: en_US/emacs-nxml.xml:115
+#: (para)
+d3703 1
+a3703 2
+#: en_US/emacs-nxml.xml:129
+#: (para)
+d3707 1
+a3707 2
+#: en_US/emacs-nxml.xml:136
+#: (ulink)
+d3711 1
+a3711 2
+#: en_US/emacs-nxml.xml:137
+#: (citetitle)
+d3715 1
+a3715 2
+#: en_US/emacs-nxml.xml:142
+#: (ulink)
+d3719 1
+a3719 2
+#: en_US/emacs-nxml.xml:147
+#: (para)
+d3723 1
+a3723 2
+#: en_US/emacs-nxml.xml:157
+#: (title)
+d3727 1
+a3727 2
+#: en_US/emacs-nxml.xml:161
+#: (para)
+d3731 1
+a3731 2
+#: en_US/emacs-nxml.xml:169
+#: (para)
+d3735 1
+a3735 2
+#: en_US/emacs-nxml.xml:171
+#: (para)
+d3739 1
+a3739 2
+#: en_US/emacs-nxml.xml:177
+#: (para)
+d3743 1
+a3743 2
+#: en_US/emacs-nxml.xml:184
+#: (command)
+d3747 1
+a3747 2
+#: en_US/emacs-nxml.xml:187
+#: (para)
+d3751 1
+a3751 2
+#: en_US/emacs-nxml.xml:192
+#: (command)
+d3755 1
+a3755 2
+#: en_US/emacs-nxml.xml:195
+#: (para)
+d3759 1
+a3759 2
+#: en_US/emacs-nxml.xml:200
+#: (command)
+d3763 1
+a3763 2
+#: en_US/emacs-nxml.xml:203
+#: (para)
+d3767 1
+a3767 2
+#: en_US/emacs-nxml.xml:209
+#: (command)
+d3771 1
+a3771 2
+#: en_US/emacs-nxml.xml:212
+#: (para)
+d3775 1
+a3775 2
+#: en_US/emacs-nxml.xml:217
+#: (para)
+d3779 1
+a3779 2
+#: en_US/emacs-nxml.xml:223
+#: (para)
+d3783 1
+a3783 2
+#: en_US/emacs-nxml.xml:228
+#: (computeroutput)
+d3792 1
+a3792 2
+#: en_US/emacs-nxml.xml:232
+#: (para)
+d3796 1
+a3796 2
+#: en_US/emacs-nxml.xml:242
+#: (para)
+d3800 1
+a3800 2
+#: en_US/emacs-nxml.xml:250
+#: (computeroutput)
+d3811 1
+a3811 2
+#: en_US/emacs-nxml.xml:255
+#: (para)
+d3815 1
+a3815 2
+#: en_US/emacs-nxml.xml:263
+#: (computeroutput)
+d3820 1
+a3820 2
+#: en_US/emacs-nxml.xml:266
+#: (para)
+d3824 1
+a3824 2
+#: en_US/emacs-nxml.xml:272
+#: (para)
+d3828 1
+a3828 2
+#: en_US/emacs-nxml.xml:277
+#: (para)
+d3832 1
+a3832 2
+#: en_US/emacs-nxml.xml:282
+#: (para)
+d3836 1
+a3836 2
+#: en_US/emacs-nxml.xml:293
+#: (para)
+d3840 1
+a3840 2
+#: en_US/emacs-nxml.xml:298
+#: (para)
+d3844 1
+a3844 2
+#: en_US/emacs-nxml.xml:303
+#: (para)
+d3848 1
+a3848 2
+#: en_US/emacs-nxml.xml:288
+#: (para)
+d3850 1
+a3850 1
+msgstr ""
+d3852 1
+a3852 2
+#: en_US/emacs-nxml.xml:310
+#: (para)
+d3856 1
+a3856 2
+#: en_US/emacs-nxml.xml:316
+#: (para)
+d3860 1
+a3860 2
+#: en_US/emacs-nxml.xml:323
+#: (para)
+d3864 1
+a3864 2
+#: en_US/emacs-nxml.xml:327
+#: (para)
+d3868 1
+a3868 2
+#: en_US/emacs-nxml.xml:333
+#: (para)
+d3872 1
+a3872 2
+#: en_US/emacs-nxml.xml:336
+#: (para)
+d3876 1
+a3876 2
+#: en_US/acknowledgments.xml:11
+#: (title)
+d3878 1
+a3878 1
+msgstr ""
+d3880 1
+a3880 2
+#: en_US/acknowledgments.xml:13
+#: (para)
+d3884 1
+a3884 2
+#: en_US/acknowledgments.xml:19
+#: (para)
+d3888 1
+a3888 2
+#: en_US/acknowledgments.xml:25
+#: (para)
+d3892 1
+a3892 2
+#: en_US/acknowledgments.xml:32
+#: (para)
+d3896 1
+a3896 2
+#: en_US/acknowledgments.xml:37
+#: (para)
+d3900 7
+a3906 7
+#: en_US/acknowledgments.xml:43
+#: (para)
+msgid "A patch from Paul W. Frields (stickster at gmail.com) has been applied to add more explanation of the <command>screen</command> tag set to <xref linkend=\"sn-xml-tags-screen\"/>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:49
+#: (para)
+d3911 1
+a3911 2
+#: en_US/acknowledgments.xml:0
+#: (None)
+@
+
diff --git a/old-documentation-guide/po/documentation-guide.pot,v b/old-documentation-guide/po/documentation-guide.pot,v
new file mode 100644
index 0000000..6441457
--- /dev/null
+++ b/old-documentation-guide/po/documentation-guide.pot,v
@@ -0,0 +1,4962 @@
+head 1.7;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.5;
+locks; strict;
+comment @# @;
+
+
+1.7
+date 2008.05.12.06.13.11; author mdious; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.12.15.21.52.11; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.11.15.02.12.48; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.08.03.16.42.44; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.08.03.16.39.22; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.07.29.23.25.11; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.07.28.22.05.13; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.7
+log
+ at updating pot and po files for noriko
+@
+text
+ at msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2008-05-13 02:06+1000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: en_US/rpm-info.xml:22(rights)
+msgid "OPL"
+msgstr ""
+
+#: en_US/rpm-info.xml:23(version)
+msgid "1.0"
+msgstr ""
+
+#: en_US/rpm-info.xml:26(year)
+msgid "2003"
+msgstr ""
+
+#: en_US/rpm-info.xml:27(year)
+msgid "2004"
+msgstr ""
+
+#: en_US/rpm-info.xml:28(year)
+msgid "2005"
+msgstr ""
+
+#: en_US/rpm-info.xml:29(year)
+msgid "2006"
+msgstr ""
+
+#: en_US/rpm-info.xml:30(year)
+msgid "2007"
+msgstr ""
+
+#: en_US/rpm-info.xml:31(year)
+msgid "2008"
+msgstr ""
+
+#: en_US/rpm-info.xml:32(holder)
+msgid "Red Hat, Inc. and others"
+msgstr ""
+
+#: en_US/rpm-info.xml:34(title)
+msgid "Fedora Documentation Guide"
+msgstr ""
+
+#: en_US/rpm-info.xml:35(desc)
+msgid "Guidelines and procedures for producing documentation for Fedora"
+msgstr ""
+
+#: en_US/rpm-info.xml:39(details)
+msgid "Add L10n chapter (#441190)"
+msgstr ""
+
+#: en_US/rpm-info.xml:43(details)
+msgid "Fix some organization and missing targets (#371531)"
+msgstr ""
+
+#: en_US/rpm-info.xml:47(details)
+msgid "Add link to DocBook XML help for Windows"
+msgstr ""
+
+#: en_US/rpm-info.xml:51(details)
+msgid "Add guidance on CVS web access and previewing work"
+msgstr ""
+
+#: en_US/rpm-info.xml:55(details)
+msgid "Add new chapter on publishing"
+msgstr ""
+
+#: en_US/rpm-info.xml:59(details)
+msgid "Include information on LINGUAS usage"
+msgstr ""
+
+#: en_US/rpm-info.xml:63(details)
+msgid "Remove unnecessary chapter on XML tags"
+msgstr ""
+
+#: en_US/rpm-info.xml:67(details)
+msgid "Assorted fixes to reflect newer version of reality"
+msgstr ""
+
+#: en_US/rpm-info.xml:74(details)
+msgid "Update to new content and build requirements"
+msgstr ""
+
+#: en_US/l10n.xml:13(title)
+msgid "Localization (L10n)"
+msgstr ""
+
+#: en_US/l10n.xml:14(para)
+msgid "This chapter discusses how translations are provided in Fedora documentation."
+msgstr ""
+
+#: en_US/l10n.xml:19(title)
+msgid "PO Files"
+msgstr ""
+
+#: en_US/l10n.xml:20(para)
+msgid "The cornerstone of translation when using XML files such as DocBook is the <firstterm>Portable Object</firstterm> or <acronym>PO</acronym> file. PO files provide a way for independent individuals or teams to translate documents. The Fedora Documentation Project toolchain includes rules for creating, updating, and maintaining these PO files."
+msgstr ""
+
+#: en_US/l10n.xml:28(para)
+msgid "PO files are usually found in two forms:"
+msgstr ""
+
+#: en_US/l10n.xml:33(para)
+msgid "the <filename class=\"extension\">.pot</filename> file, or <firstterm>PO Template</firstterm> (<acronym>POT</acronym>)"
+msgstr ""
+
+#: en_US/l10n.xml:41(para)
+msgid "the <filename class=\"extension\">.po</filename> file, or translation file (<acronym>PO</acronym>)"
+msgstr ""
+
+#: en_US/l10n.xml:47(para)
+msgid "A POT is, as the name suggests, a blank template for new translations. It contains some header information and a list of strings based on the content of the original XML file from which it was created. Translators do not alter the POT. The POT should only be changed after changes are made to the original XML file from which it is derived."
+msgstr ""
+
+#: en_US/l10n.xml:55(para)
+msgid "A translator who wishes to start working on a new language copies the POT to a locale-specific PO file. Then the translator uses any of a number of command-line or graphical tools to translate each of the strings in the list. A single POT is used to create many POs, one for each locale. These files are normally named for their locale code, such as <filename>de.po</filename>, <filename>it.po</filename>, and so on."
+msgstr ""
+
+#: en_US/l10n.xml:67(title)
+msgid "Creating or Updating a POT"
+msgstr ""
+
+#: en_US/l10n.xml:68(para)
+msgid "The POT is named after the document from which it is derived. If document named in the <filename>Makefile</filename>) is <filename>foo-tutorial.xml</filename>, the POT is named <filename>foo-tutorial.pot</filename>."
+msgstr ""
+
+#: en_US/l10n.xml:74(para)
+msgid "To create a new POT, use the following command:"
+msgstr ""
+
+#: en_US/l10n.xml:78(para)
+msgid "The same command is used to update the POT when the original XML sources change."
+msgstr ""
+
+#: en_US/l10n.xml:83(title)
+msgid "Keep POT Fresh"
+msgstr ""
+
+#: en_US/l10n.xml:84(para)
+msgid "Update the POT whenever the original XML changes. Many translators' tools automatically notify them of the change so they can update translations quickly."
+msgstr ""
+
+#: en_US/l10n.xml:92(title)
+msgid "Updating PO Files"
+msgstr ""
+
+#: en_US/l10n.xml:93(para)
+msgid "The translation files are created by the individual translators, and document maintainers do not normally need to create them. Translators update a list of locales in the <filename>po/LINGUAS</filename> file which defines all the locales for which translations exist."
+msgstr ""
+
+#: en_US/l10n.xml:100(para)
+msgid "Whenever the source XML files are updated, the maintainer must at least update the POT. It is helpful, however, to also merge these changes with the existing translations for those translators who are not automatically notified of changes."
+msgstr ""
+
+#: en_US/l10n.xml:107(title)
+msgid "Staying Current"
+msgstr ""
+
+#: en_US/l10n.xml:108(para)
+msgid "Always make sure your local copy of PO is fresh, using the CVS \"update\" command:"
+msgstr ""
+
+#: en_US/l10n.xml:114(para)
+msgid "To merge new changes into the existing PO translations, use the following command:"
+msgstr ""
+
+#: en_US/l10n.xml:121(title)
+msgid "Checking Statistics"
+msgstr ""
+
+#: en_US/l10n.xml:122(para)
+msgid "PO strings fall into three categories:"
+msgstr ""
+
+#: en_US/l10n.xml:127(para)
+msgid "<firstterm>translated</firstterm>, meaning the string has been handled by a translator and its source has not changed since then"
+msgstr ""
+
+#: en_US/l10n.xml:134(para)
+msgid "<firstterm>fuzzy</firstterm>, meaning the string has changed since it was last handled by a translator"
+msgstr ""
+
+#: en_US/l10n.xml:140(para)
+msgid "<firstterm>untranslated</firstterm>, meaning no translation has yet been provided for this string, or it is brand new"
+msgstr ""
+
+#: en_US/l10n.xml:146(para)
+msgid "To see a rough statistical tally of the string handling inside the PO for a module, use the following command:"
+msgstr ""
+
+#: en_US/l10n.xml:151(para)
+msgid "For each locale in the list, a count is shown of translated, fuzzy, and untranslated strings in that order. Tallies that only provide two numerals are usually translated followed by untranslated. Tallies with only one numeral are usually fully translated."
+msgstr ""
+
+#: en_US/l10n.xml:158(para)
+msgid "To see only a specific locale, append a dash and the locale code to the <command>postat</command> target:"
+msgstr ""
+
+#: en_US/publishing.xml:11(title)
+msgid "Publishing Official Documentation"
+msgstr ""
+
+#: en_US/publishing.xml:12(para)
+msgid "This chapter shows how to publish official Fedora Documentation Project work to the <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> website. To publish official documentation, you must be approved to write to the web repository in CVS. Access for publishing is limited to contributors who have demonstrated capacity for working with CVS and other project tools. Once you have acquired and are comfortable with these skills, contributions as a publisher are welcome."
+msgstr ""
+
+#: en_US/publishing.xml:21(title)
+msgid "How the Site Works"
+msgstr ""
+
+#: en_US/publishing.xml:22(para)
+msgid "The <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> website is a set of PHP files and scripts. Publishers maintain these files in a CVS repository, and the website host retrieves them hourly to refresh the site. The host does not automatically use the newest content for the website. Instead, it pulls files with the CVS tag <systemitem>LIVE</systemitem> to populate the website."
+msgstr ""
+
+#: en_US/publishing.xml:30(para)
+msgid "Each publisher sets up a local testing website on an available Fedora system. This site, sometimes called a <firstterm>sandbox</firstterm>, allows the publisher to test and view changes to documents, and ensure stability on the public site."
+msgstr ""
+
+#: en_US/publishing.xml:37(title)
+msgid "Setting Up a Web Sandbox"
+msgstr ""
+
+#: en_US/publishing.xml:38(para)
+msgid "To test document publishing, first set up a web sandbox on a local Fedora system."
+msgstr ""
+
+#: en_US/publishing.xml:42(para)
+msgid "Install the \"Web Server\" package group:"
+msgstr ""
+
+#: en_US/publishing.xml:43(screen)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Web Server\"'"
+msgstr ""
+
+#: en_US/publishing.xml:46(para)
+msgid "Create a folder for the web server to access the site files."
+msgstr ""
+
+#: en_US/publishing.xml:48(screen)
+#, no-wrap
+msgid "su -c 'mkdir /var/www/fedora'"
+msgstr ""
+
+#: en_US/publishing.xml:51(para)
+msgid "Change the permissions on this directory to make it easier to access for your normal user account."
+msgstr ""
+
+#: en_US/publishing.xml:53(replaceable) en_US/publishing.xml:62(replaceable)
+msgid "username"
+msgstr ""
+
+#: en_US/publishing.xml:53(screen)
+#, no-wrap
+msgid "su -c 'chown <placeholder-1/> /var/www/fedora'"
+msgstr ""
+
+#: en_US/publishing.xml:56(para)
+msgid "Link to the new directory from your home directory."
+msgstr ""
+
+#: en_US/publishing.xml:57(screen)
+#, no-wrap
+msgid "ln -s /var/www/fedora ~/fedora"
+msgstr ""
+
+#: en_US/publishing.xml:60(para)
+msgid "Retrieve the web module from CVS."
+msgstr ""
+
+#: en_US/publishing.xml:61(screen)
+#, no-wrap
+msgid "cd ~/fedora\ncvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+msgstr ""
+
+#: en_US/publishing.xml:64(title)
+msgid "Web CVS Access"
+msgstr ""
+
+#: en_US/publishing.xml:65(para)
+msgid "You must have access to the <systemitem>cvsweb</systemitem> module through the Fedora Account System to check in changes. If you do not have access, you can use <userinput><![CDATA[:pserver:anonymous]]></userinput> in place of <userinput><![CDATA[:ext:username]]></userinput> above. Visit the Fedora Account System at <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> for more information."
+msgstr ""
+
+#: en_US/publishing.xml:77(para)
+msgid "Edit the <filename>/etc/hosts</filename> file and add the following line <emphasis>after</emphasis> all other lines:"
+msgstr ""
+
+#: en_US/publishing.xml:80(screen)
+#, no-wrap
+msgid "127.0.0.1 docs.localhost.localdomain"
+msgstr ""
+
+#: en_US/publishing.xml:83(para)
+msgid "Create a file <filename>/etc/httpd/conf.d/fpo.conf</filename> with the following content:"
+msgstr ""
+
+#: en_US/publishing.xml:97(para)
+msgid "Create a file <filename>/etc/php.d/fpo.ini</filename> with the following content:"
+msgstr ""
+
+#: en_US/publishing.xml:99(screen)
+#, no-wrap
+msgid "include_path = \".:/var/www/fedora/web/include\""
+msgstr ""
+
+#: en_US/publishing.xml:102(para)
+msgid "Start the web server using the following command:"
+msgstr ""
+
+#: en_US/publishing.xml:103(screen)
+#, no-wrap
+msgid "su -c '/sbin/service httpd start'"
+msgstr ""
+
+#: en_US/publishing.xml:104(para)
+msgid "To have the web server start at every boot, use the following command:"
+msgstr ""
+
+#: en_US/publishing.xml:106(screen)
+#, no-wrap
+msgid "su -c '/sbin/chkconfig httpd on'"
+msgstr ""
+
+#: en_US/publishing.xml:109(para)
+msgid "To test the new sandbox site, open a Web browser and point it at the URL <uri>http://docs.localhost.localdomain</uri>."
+msgstr ""
+
+#: en_US/publishing.xml:113(title)
+msgid "Creating a New Publication"
+msgstr ""
+
+#: en_US/publishing.xml:115(title)
+msgid "General Guidelines"
+msgstr ""
+
+#: en_US/publishing.xml:116(para)
+msgid "Follow these guidelines to ensure maintainability and ease of use for all publishers."
+msgstr ""
+
+#: en_US/publishing.xml:120(para)
+msgid "Use a short, descriptive name for the document directory. The module name from its Docs CVS location is usually appropriate. Good examples include <filename class=\"directory\">install-guide/</filename> or <filename class=\"directory\">example-tutorial/</filename>."
+msgstr ""
+
+#: en_US/publishing.xml:127(para)
+msgid "Under the document directory, include a branch directory if the document references specific features of a particular Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:132(para)
+msgid "Under the branch directory (or document directory if no branches are necessary), make at least a <filename class=\"directory\">en_US/</filename> directory. Make an additional directory for each locale that has been fully translated."
+msgstr ""
+
+#: en_US/publishing.xml:141(title)
+msgid "Adding Content"
+msgstr ""
+
+#: en_US/publishing.xml:142(para)
+msgid "To add content, follow the procedure below. The following commands show an example of adding content for a new document called the <citetitle>Foobar Tutorial</citetitle>. This document includes a translation for the \"zz_XX\" locale and follows specifics of each Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:149(para)
+msgid "Make the required directory structure."
+msgstr ""
+
+#: en_US/publishing.xml:150(screen)
+#, no-wrap
+msgid "cd ~/fedora/web/html/docs/\nmkdir foobar-tutorial\nmkdir foobar-tutorial/f7\nmkdir foobar-tutorial/f7/{en_US,zz_XX}"
+msgstr ""
+
+#: en_US/publishing.xml:156(para)
+msgid "Build the HTML version of each translation of the document from Docs CVS."
+msgstr ""
+
+#: en_US/publishing.xml:158(replaceable)
+msgid "~/my-docs/foobar-tutorial/F-7/"
+msgstr ""
+
+#: en_US/publishing.xml:158(screen)
+#, no-wrap
+msgid "cd <placeholder-1/>\nmake html-en_US html-zz_XX"
+msgstr ""
+
+#: en_US/publishing.xml:162(para)
+msgid "Copy the HTML content to the web sandbox."
+msgstr ""
+
+#: en_US/publishing.xml:163(screen)
+#, no-wrap
+msgid "cd ~/fedora/web/html/docs/foobar-tutorial/f7/\ncp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/\ncp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/"
+msgstr ""
+
+#: en_US/publishing.xml:168(para)
+msgid "Convert the HTML in each directory to PHP using the provided <filename>docbookhtml2php.py</filename> script."
+msgstr ""
+
+#: en_US/publishing.xml:177(para)
+msgid "Create any necessary <filename>index.php</filename> files for the overall directories. Each document and branch directory must have an <filename>index.php</filename> file directing users to appropriate content. In this example, the necessary files are <filename>foobar-tutorial/index.php</filename> and <filename>foobar-tutorial/f7/index.php</filename>. You do not need to write these files from scratch. Copy an existing file from another document, and change it as needed to suit the new document."
+msgstr ""
+
+#: en_US/publishing.xml:187(para)
+msgid "Depending on content, publication may include changing a higher-level <filename>index.php</filename> file."
+msgstr ""
+
+#: en_US/publishing.xml:191(para)
+msgid "To test the changes in your sandbox, open a web browser and point it at <uri>http://docs.localhost.localdomain/</uri>."
+msgstr ""
+
+#: en_US/publishing.xml:195(title)
+msgid "Always Test Changes"
+msgstr ""
+
+#: en_US/publishing.xml:196(para)
+msgid "<emphasis>Do not proceed further until you test all changes.</emphasis> Check that all links and index pages work."
+msgstr ""
+
+#: en_US/publishing.xml:204(title)
+msgid "Pushing Content to the Web"
+msgstr ""
+
+#: en_US/publishing.xml:205(para)
+msgid "To push your new content to the web site, follow this procedure:"
+msgstr ""
+
+#: en_US/publishing.xml:209(para)
+msgid "Add all the new file content to CVS."
+msgstr ""
+
+#: en_US/publishing.xml:210(screen)
+#, no-wrap
+msgid "cd ~/fedora/web/html/docs/\ncvs add foobar-tutorial\ncd foobar-tutorial\ncvs add f7\ncd f7\ncvs add en_US/ zz_XX/\ncvs add en_US/*php en_US/stylesheet-images/\ncvs add zz_XX/*php zz_XX/stylesheet-images/\ncvs add en_US/stylesheet-images/*png\ncvs add zz_XX/stylesheet-images/*png\ncd ../../\ncvs add foobar-tutorial/index.php\ncvs add foobar-tutorial/f7/index.php\n"
+msgstr ""
+
+#: en_US/publishing.xml:226(para)
+msgid "Commit the changes to CVS. Use a message that describes the document being committed."
+msgstr ""
+
+#: en_US/publishing.xml:228(replaceable)
+msgid "message about document"
+msgstr ""
+
+#: en_US/publishing.xml:228(screen)
+#, no-wrap
+msgid "cvs ci -m '<placeholder-1/>' foobar-tutorial/"
+msgstr ""
+
+#: en_US/publishing.xml:231(para)
+msgid "Tag the content <systemitem>LIVE</systemitem> in CVS."
+msgstr ""
+
+#: en_US/publishing.xml:233(screen)
+#, no-wrap
+msgid "cvs tag -F LIVE foobar-tutorial/"
+msgstr ""
+
+#: en_US/vim.xml:13(title)
+msgid "VIM and DocBook"
+msgstr ""
+
+#: en_US/vim.xml:16(primary) en_US/vim.xml:33(primary)
+msgid "VIM"
+msgstr ""
+
+#: en_US/vim.xml:19(para)
+msgid "VIM has many features to help you write XML content such as DocBook, including syntax highlighting and customizable key bindings. Additionally, one can easily use external programs from VIM for features such as spell-checking. This chapter assumes you already know generally how to use VIM; if you want to learn how, try the <command>vimtutor</command> or by typing <userinput>:help tutor</userinput> from inside VIM."
+msgstr ""
+
+#: en_US/vim.xml:30(title)
+msgid "Setting Up Your <filename>.vimrc</filename> File"
+msgstr ""
+
+#: en_US/vim.xml:34(secondary) en_US/emacs.xml:44(secondary)
+msgid "configuration file"
+msgstr ""
+
+#: en_US/vim.xml:37(para)
+msgid "Below is a short sample <filename>.vimrc</filename> file that turns on some VIM features useful for editing SGML or XML content such as DocBook: <screen>\n<computeroutput>\" Turn off vi compatibility settings like limited undo\nset nocompatible\n\" Syntax highlighting based on file extension\nsyntax on\n\" Automatically insert newlines after 80 characters\nset textwidth=80\n\" Automatically indent\nset autoindent\n\" Match SGML tags with %\nsource $VIMRUNTIME/macros/matchit.vim</computeroutput>\n</screen>"
+msgstr ""
+
+#: en_US/vim.xml:55(para)
+msgid "Some of these features require the <filename>vim-enhanced</filename> package to be installed. If you are using or the <filename>vim-minimal</filename> package, or if you are using an older version of VIM, you may not have the <filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still download <ulink url=\"http://vim.org/scripts/script.php?script_id=39\">matchit.zip from Vim.org</ulink> and load it separately."
+msgstr ""
+
+#: en_US/vim.xml:69(title)
+msgid "Keymapping with VIM"
+msgstr ""
+
+#: en_US/vim.xml:71(para)
+msgid "VIM can speed up your DocBook creation by mapping frequently typed tags (or any words or phrases) onto short key combinations. By default, the keymap leader is the backslash (<literal>\\</literal>), but it can be redefined with a command like <userinput>let mapleader =\n \",\"</userinput>. There are two ways to use the following example; you can put it directly in your <filename>.vimrc</filename>, or you can save it in a separate file and load it with a <userinput>source</userinput> command in your <filename>.vimrc</filename>. <screen>\n<![CDATA[let mapleader = \",\"\n\n\" skip ahead to after next tag without leaving insert mode\nimap <leader>e <esc>/><cr>:nohlsearch<cr>a\n\n\" common tags that start a new text block\nimap<leader>pa <para><cr></para><esc>O\nimap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\nimap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\nimap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n\n\" common
tags that are placed inline\n\" use <esc>F>a\nimap<leader>en <envar></envar><esc>F>a\nimap<leader>fi <filename></filename><esc>F>a\nimap<leader>lt <literal></literal><esc>F>a\nimap<leader>re <replaceable></replaceable><esc>F>a\nimap<leader>ui <userinput></userinput><esc>F>a\nimap<leader>ul <ulink url=\"\"></ulink><esc>F>a\nimap<leader>si <systemitem></systemitem><esc>F>a\nimap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\nimap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\nimap<leader>cm <command></command><esc>F>a \n\" entities\nimap <leader>> >\nimap <leader>< <]]>\n</screen>"
+msgstr ""
+
+#: en_US/vim.xml:110(para)
+msgid "Unfortunately, there is not currently a complete macro set for all DocBook commands, so you will need to define them yourself or customize the definitions in the examples from <xref linkend=\"sn-vim-additional-resources\"/>."
+msgstr ""
+
+#: en_US/vim.xml:119(title)
+msgid "Additional VIM Resources"
+msgstr ""
+
+#: en_US/vim.xml:121(para)
+msgid "Additional information about VIM may be found from:"
+msgstr ""
+
+#: en_US/vim.xml:127(para)
+msgid "<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to Vi Improved (VIM)</citetitle>"
+msgstr ""
+
+#: en_US/vim.xml:134(para)
+msgid "The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick Reference Card</ulink>"
+msgstr ""
+
+#: en_US/vim.xml:140(ulink)
+msgid "Vim as XML Editor"
+msgstr ""
+
+#: en_US/vim.xml:145(para)
+msgid "The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the <filename>vim-common</filename> package —<filename>/usr/share/vim/<replaceable><version></replaceable>/doc/intro.txt</filename> or type <userinput>:help intro</userinput> from within VIM"
+msgstr ""
+
+#: en_US/tutorial.xml:13(title)
+msgid "The Layout of a Tutorial"
+msgstr ""
+
+#: en_US/tutorial.xml:14(para)
+msgid "In this chapter, you will find an example of a very short tutorial as used by the Fedora Documentation Project. This example is specific to the way the Docs Project uses DocBook XML. The example consists of a set of files used to hold the content and metadata for the tutorial."
+msgstr ""
+
+#: en_US/tutorial.xml:19(title)
+msgid "The Article"
+msgstr ""
+
+#: en_US/tutorial.xml:21(primary) en_US/tutorial.xml:56(primary)
+msgid "tutorial layout"
+msgstr ""
+
+#: en_US/tutorial.xml:22(secondary)
+msgid "article"
+msgstr ""
+
+#: en_US/tutorial.xml:24(para)
+msgid "Below is a sample article:"
+msgstr ""
+
+#: en_US/tutorial.xml:54(title)
+msgid "The Metadata"
+msgstr ""
+
+#: en_US/tutorial.xml:57(secondary)
+msgid "metadata"
+msgstr ""
+
+#: en_US/tutorial.xml:59(para)
+msgid "The <filename>rpm-info.xml</filename> file contains all the required metadata for the document. This metadata includes title, authorship, licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates the content of this file:"
+msgstr ""
+
+#: en_US/tutorial.xml:65(title)
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr ""
+
+#: en_US/tutorial.xml:95(para)
+msgid "If you are not familiar with XML editing, copy and paste this file from an existing module and then edit the values for the various elements as appropriate. Consult Fedora Documentation Project members and help channels for more assistance if needed."
+msgstr ""
+
+#: en_US/style.xml:14(title)
+msgid "Style"
+msgstr ""
+
+#: en_US/style.xml:16(para)
+msgid "Writing good technical documentation is not simply reproducing command lines and instruction sets. Good documentation is easy to read, understand, and translate, and presents a concise logical progression of concepts. Good documentation can also be defined by what it does <emphasis>not</emphasis> contain. Your tutorial should avoid:"
+msgstr ""
+
+#: en_US/style.xml:26(para)
+msgid "Excessive wordiness"
+msgstr ""
+
+#: en_US/style.xml:31(para)
+msgid "Unnecessary or undefined jargon"
+msgstr ""
+
+#: en_US/style.xml:36(para)
+msgid "Grammatical or spelling errors"
+msgstr ""
+
+#: en_US/style.xml:41(para)
+msgid "References to yourself or your experiences"
+msgstr ""
+
+#: en_US/style.xml:46(para)
+msgid "Remarks which might offend or confuse any reader"
+msgstr ""
+
+#: en_US/style.xml:51(para)
+msgid "This chapter contains style rules and guidelines for writing Fedora documentation. Guidelines are not the same as rules. It is acceptable to violate a guideline when it makes your material easier to understand. Follow guidelines whenever possible, but follow rules at all times. Assume any advice is a guideline unless identified otherwise."
+msgstr ""
+
+#: en_US/style.xml:62(title)
+msgid "Why Style Is Important"
+msgstr ""
+
+#: en_US/style.xml:64(para)
+msgid "Writing well comes naturally to almost no one. It is a skill that professional writers, even famous ones, must practice constantly. <firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> is the quality that separates elegant writing from the merely functional."
+msgstr ""
+
+#: en_US/style.xml:77(para)
+msgid "For example, refer to. <ulink url=\"http://www.online-literature.com/james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>. Please note that this example contains some mature themes and language, and is not suitable for all readers."
+msgstr ""
+
+#: en_US/style.xml:71(para)
+msgid "Elegance comes in many forms. In prose and poetry, elegant writing may not follow some (or any) common rules of grammar, syntax, or spelling. A good example is Episode 18, \"Penelope,\" in James Joyce's novel <citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long streams of words without punctuation to simulate a character's internal consciousness. By violating basic rules of grammar and syntax, Joyce simulates the disorganized but loosely connected thought patterns of the narrator."
+msgstr ""
+
+#: en_US/style.xml:89(para)
+msgid "Technical documentation, however, should always respect these rules. The more a document departs from standard language usage, the more difficult the material becomes for the reader. For example, readers may not be native speakers of the language used, or they might be reading a translation. If the writer uses slang, idioms, or jargon, a reader or translator may easily become confused. The following example compares two different written executions of the same idea:"
+msgstr ""
+
+#: en_US/style.xml:100(title)
+msgid "Incorrect style"
+msgstr ""
+
+#. I prefer "incorrect," because I think terms such as
+#. "problematic" are mealy-mouthed. They remind me of the late
+#. 1980's English textbook trend toward the politically correct yet
+#. wholly unhelpful "standard/nonstandard." But then, I tend to be
+#. dogmatic; it's probably my Catholic upbringing. [PWF]
+#: en_US/style.xml:108(para)
+msgid "So you made the changes I showed you in the last section. What's the next thing you should do? Just pop your thumb drive onto your system and read the <filename>messages</filename> log. When you see \"USB device found,\" then Bob's your uncle."
+msgstr ""
+
+#: en_US/style.xml:116(title)
+msgid "Correct style"
+msgstr ""
+
+#. I prefer "correct." See above. [PWF]
+#: en_US/style.xml:120(para)
+msgid "After you complete the configuration changes above, attach the USB removable media to your system. Use the <command>dmesg</command> command to examine the kernel message log. The message <computeroutput>USB device\n\t found</computeroutput> indicates that your device was installed successfully."
+msgstr ""
+
+#: en_US/style.xml:129(para)
+msgid "The first example is more conversational English, which is not appropriate for official written documentation. The second example is more formal, but as a result it is easier to comprehend, both for native readers and translators."
+msgstr ""
+
+#: en_US/style.xml:135(para)
+msgid "Following style rules and guidelines also makes readers more comfortable with a set of documents. Consistent style enhances the professional appearance of documentation, and its perceived value. On the other hand, lapses in punctuation or poor grammar negatively affect a reader's reaction to written material. A reader can feel that an otherwise correct technical document is lacking in authority, simply because it is poorly written. Readers feel at ease when they do not have to struggle to understand an author's use of language."
+msgstr ""
+
+#: en_US/style.xml:146(para)
+msgid "This chapter cannot possibly cover enough material to make every reader a good writer. Some manuals devoted entirely to writing style are themselves hundreds of pages long. This chapter provides enough guidelines for intermediate writers to understand style usage in technical documentation."
+msgstr ""
+
+#: en_US/style.xml:153(para)
+msgid "If you are not a practiced writer, whether of technical documentation or otherwise, you may benefit from other style resources. The following list is far from comprehensive, but provides a starting point:"
+msgstr ""
+
+#: en_US/style.xml:161(para)
+msgid "<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules and links to online versions can be found at: <ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+msgstr ""
+
+#: en_US/style.xml:176(para)
+msgid "<citetitle>The Chicago Manual of Style</citetitle>, by the University of Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle.org/\">http://www.chicagomanualofstyle.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:183(para)
+msgid "<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/\">http://www.powa.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:190(para)
+msgid "There are many free software documentation projects which have developed their own style guidelines. This chapter, in fact, draws heavily on the <citetitle>GNOME Documentation Style Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr ""
+
+#: en_US/style.xml:203(title)
+msgid "Fundamental Concepts of Technical Documentation"
+msgstr ""
+
+#: en_US/style.xml:206(title)
+msgid "Bibliographic Information"
+msgstr ""
+
+#: en_US/style.xml:207(para)
+msgid "This section is drawn primarily from the <citetitle>GDSG</citetitle>."
+msgstr ""
+
+#. This section will reproduce mostly what is in Chapter 1 of
+#. the GDSG. There may be minor changes. FIXME: Make sure the
+#. appropriate front matter of the Documentation Guide includes
+#. attribution as required by the GNU FDL.
+#: en_US/style.xml:218(para)
+msgid "This chapter provides a brief introduction to writing technical documentation."
+msgstr ""
+
+#: en_US/style.xml:224(title)
+msgid "General Style Requirements"
+msgstr ""
+
+#: en_US/style.xml:225(para)
+msgid "Technical writing for the Fedora Project imposes special constraints beyond the basic requirements of good prose. Good Fedora technical documentation has the following characteristics:"
+msgstr ""
+
+#: en_US/style.xml:232(term)
+msgid "Comprehensive"
+msgstr ""
+
+#: en_US/style.xml:234(para)
+msgid "Describe all of the functionality of a product. Do not omit functionality that you regard as irrelevant for the user."
+msgstr ""
+
+#: en_US/style.xml:242(term)
+msgid "Conforming"
+msgstr ""
+
+#: en_US/style.xml:249(para)
+msgid "Describe what you see. Do not describe what you want to see. Present your information in the order that users experience the subject matter."
+msgstr ""
+
+#: en_US/style.xml:257(term)
+msgid "Clear"
+msgstr ""
+
+#: en_US/style.xml:259(para)
+msgid "Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>) to help make your writing clear."
+msgstr ""
+
+#: en_US/style.xml:275(term)
+msgid "Consistent"
+msgstr ""
+
+#: en_US/style.xml:277(para)
+msgid "Use agreed vocabulary throughout your documentation. Use the same vocabulary as other writers who are working on related documentation."
+msgstr ""
+
+#: en_US/style.xml:285(term)
+msgid "Concise"
+msgstr ""
+
+#: en_US/style.xml:287(para)
+msgid "Review your work frequently as you write your document. Ask yourself which words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for specific guidelines."
+msgstr ""
+
+#: en_US/style.xml:297(title)
+msgid "Golden Rules"
+msgstr ""
+
+#: en_US/style.xml:298(para)
+msgid "This section contains some basic style guidelines. Subsequent sections in this chapter expand on these guidelines to give more detailed guidance."
+msgstr ""
+
+#: en_US/style.xml:305(term)
+msgid "Golden Rule 1: Be brief"
+msgstr ""
+
+#: en_US/style.xml:309(para)
+msgid "Limit each sentence to fewer than 25 words."
+msgstr ""
+
+#: en_US/style.xml:314(para)
+msgid "Limit each procedure step to 23 words."
+msgstr ""
+
+#: en_US/style.xml:320(title)
+msgid "Incorrect: Too long"
+msgstr ""
+
+#: en_US/style.xml:321(para)
+msgid "Under normal operating conditions, the kernel does not always immediately write file data to the disks, storing it in a memory buffer and then periodically writing to the disks to speed up operations."
+msgstr ""
+
+#: en_US/style.xml:328(title)
+msgid "Correct: Less wordy"
+msgstr ""
+
+#: en_US/style.xml:329(para)
+msgid "Normally, the kernel stores the data in memory prior to periodically writing the data to the disk."
+msgstr ""
+
+#: en_US/style.xml:337(term)
+msgid "Golden Rule 2: Be organized"
+msgstr ""
+
+#: en_US/style.xml:341(para)
+msgid "Limit each paragraph to one topic."
+msgstr ""
+
+#: en_US/style.xml:346(para)
+msgid "Limit each sentence to one idea."
+msgstr ""
+
+#: en_US/style.xml:351(para)
+msgid "Limit each procedure step to one action."
+msgstr ""
+
+#: en_US/style.xml:357(title)
+msgid "Incorrect: Disorganized topics"
+msgstr ""
+
+#: en_US/style.xml:358(para)
+msgid "The <application>Workspace Switcher</application> applet helps you navigate all of the virtual desktops available on your system. The X Window system, working in hand with a piece of software called a <emphasis>window manager</emphasis>, allows you to create more than one virtual desktop, known as <emphasis>workspaces</emphasis>, to organize your work, with different applications running in each workspace. The <application>Workspace Switcher</application> applet is a navigational tool to get around the various workspaces, providing a miniature road map in the GNOME panel showing all your workspaces and allowing you to switch easily between them."
+msgstr ""
+
+#: en_US/style.xml:375(title)
+msgid "Correct: Organized topics"
+msgstr ""
+
+#: en_US/style.xml:376(para)
+msgid "Use the <application>Workspace Switcher</application> to add new <emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different applications in each workspace. The <application>Workspace Switcher</application> applet provides a miniature map that shows all of your workspaces. You can use the <application>Workspace Switcher</application> applet to switch between workspaces."
+msgstr ""
+
+#: en_US/style.xml:388(para)
+msgid "Plan the order of paragraphs before you start writing. Decide which topic you want to cover in each paragraph."
+msgstr ""
+
+#: en_US/style.xml:396(term)
+msgid "Golden Rule 3: Be demonstrative"
+msgstr ""
+
+#: en_US/style.xml:398(para)
+msgid "Use explicit examples to demonstrate how an application works. Provide instructions rather than descriptions."
+msgstr ""
+
+#: en_US/style.xml:403(title)
+msgid "Incorrect: Describes but does not demonstrate"
+msgstr ""
+
+#: en_US/style.xml:405(para)
+msgid "There is a text box that you can use to find out the definition of a word."
+msgstr ""
+
+#: en_US/style.xml:411(title)
+msgid "Correct: Demonstrates usage"
+msgstr ""
+
+#: en_US/style.xml:412(para)
+msgid "To request a definition of a word, type the word in the text box, then select <guilabel>Lookup</guilabel>."
+msgstr ""
+
+#: en_US/style.xml:418(para)
+msgid "Do not apply this guideline too rigidly. Sometimes you must explain how software works to support your how-to examples."
+msgstr ""
+
+#: en_US/style.xml:427(term)
+msgid "Golden Rule 4: Be objective"
+msgstr ""
+
+#: en_US/style.xml:429(para)
+msgid "Write in a neutral tone."
+msgstr ""
+
+#: en_US/style.xml:433(title)
+msgid "Incorrect: Sentence takes sides"
+msgstr ""
+
+#: en_US/style.xml:434(para)
+msgid "The applet is a handy little screen grabber."
+msgstr ""
+
+#: en_US/style.xml:439(title)
+msgid "Correct: Sentence is objective"
+msgstr ""
+
+#: en_US/style.xml:440(para)
+msgid "Use the applet to take screenshots."
+msgstr ""
+
+#: en_US/style.xml:452(title)
+msgid "Tone"
+msgstr ""
+
+#: en_US/style.xml:453(para)
+msgid "Inappropriate tone hinders reader access to information. A neutral tone free of opinion or personal flavor improves the reader's comprehension. Neutral tone helps writers to work in parallel on a large technical documentation project. Furthermore, additional writers may join the project at any time. Use of a neutral tone helps to achieve consistency across a documentation set, and thereby facilitates user access to information. The best way to achieve a common, neutral tone is to apply the following principles:"
+msgstr ""
+
+#: en_US/style.xml:466(term)
+msgid "Avoid humor"
+msgstr ""
+
+#: en_US/style.xml:468(para)
+msgid "Humor distracts from the information you are trying to provide. Humor also makes documentation difficult to translate. Stay factual."
+msgstr ""
+
+#: en_US/style.xml:476(term)
+msgid "Avoid personal opinions"
+msgstr ""
+
+#: en_US/style.xml:478(para)
+msgid "Whether you think a function is useful or woeful is irrelevant. Report the function to the user, with instructions about how to use the function. Stay accurate."
+msgstr ""
+
+#: en_US/style.xml:487(term)
+msgid "Avoid colloquial language"
+msgstr ""
+
+#: en_US/style.xml:489(para)
+msgid "Colloquial language is difficult to translate and usually culture-specific. Stay neutral."
+msgstr ""
+
+#: en_US/style.xml:496(term)
+msgid "Avoid topical expressions"
+msgstr ""
+
+#: en_US/style.xml:498(para)
+msgid "An expression that is in common use today might convey something completely different tomorrow. Stay technical."
+msgstr ""
+
+#: en_US/style.xml:505(term)
+msgid "Avoid aspirational statements"
+msgstr ""
+
+#: en_US/style.xml:507(para)
+msgid "Statements about the future developments of a product do not belong in technical documentation. Write about what you see right now. Stay real."
+msgstr ""
+
+#: en_US/style.xml:517(title)
+msgid "Reaching the Right Audience"
+msgstr ""
+
+#: en_US/style.xml:518(para)
+msgid "All of the decisions that you make about the structure and content of a manual follow from an understanding of the audience. Consider how the audience accesses the documentation, what sort of information the audience needs, and the experience level of the audience. Usually, you need to create documentation that is suitable for different audiences. The following sections introduce some of the audience-related topics you need to consider."
+msgstr ""
+
+#: en_US/style.xml:530(title)
+msgid "User Motivation"
+msgstr ""
+
+#: en_US/style.xml:531(para)
+msgid "Do not waste the time of the user who looks for information in your documentation. Users do not read technical documentation for entertainment. Users usually have specific questions. You need to give clear answers to those questions."
+msgstr ""
+
+#: en_US/style.xml:539(title)
+msgid "New Users"
+msgstr ""
+
+#: en_US/style.xml:540(para)
+msgid "New users to Fedora are likely to consult online tutorials for guidance about unfamiliar applications or functionality. Each tutorial should contain enough introductory information to tell new users how to start using the relevant functions. Each tutorial should also contain enough usage instructions to tell users the different actions that they can perform with the command or function. Keep these instructions task-oriented. Do not describe GUI screens, dialogs, and dialog elements in a tutorial, unless there is an unusual feature that affects your instructions."
+msgstr ""
+
+#: en_US/style.xml:554(title)
+msgid "Experienced Users"
+msgstr ""
+
+#: en_US/style.xml:555(para)
+msgid "Experienced users are more likely to use documentation as a reference. The documentation therefore needs to be complete, well-organized, and in the case of printed manuals, well-indexed."
+msgstr ""
+
+#: en_US/style.xml:563(title)
+msgid "Do Not Offend Your Audience"
+msgstr ""
+
+#: en_US/style.xml:564(para)
+msgid "To avoid offending your readers, apply the following guidelines to your documentation:"
+msgstr ""
+
+#: en_US/style.xml:570(term)
+msgid "Avoid insider language"
+msgstr ""
+
+#: en_US/style.xml:572(para)
+msgid "Insider language includes both undefined jargon and the tendency of the computer community to shorten words. For example, use the term <literal>documentation</literal> instead of the term <literal>docs</literal>. A term may be jargon if it fails all the following conditions:"
+msgstr ""
+
+#: en_US/style.xml:581(para)
+msgid "The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> (<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora.redhat.com/docs/jargon-buster/</ulink>)."
+msgstr ""
+
+#: en_US/style.xml:588(para)
+msgid "The term does not appear in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/ </ulink>)."
+msgstr ""
+
+#: en_US/style.xml:596(para)
+msgid "The term does not appear in the glossary of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:602(para)
+msgid "The term is not defined in the body text of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:611(term)
+msgid "Avoid gender-specific language"
+msgstr ""
+
+#: en_US/style.xml:613(para)
+msgid "Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</literal> do not exist. There is no need to identify gender in your instructions."
+msgstr ""
+
+#: en_US/style.xml:621(term)
+msgid "Avoid culture-specific language"
+msgstr ""
+
+#: en_US/style.xml:623(para)
+msgid "There is little point in giving an example that everyone in your town knows about, but is a complete mystery to everyone else in the world."
+msgstr ""
+
+#: en_US/style.xml:631(term)
+msgid "Avoid talking down to your reader"
+msgstr ""
+
+#: en_US/style.xml:633(para)
+msgid "There are few experiences more irritating for a user than documentation that says an action is easy or quick, when in fact the user cannot complete the action. Do not qualify or prejudge actions."
+msgstr ""
+
+#: en_US/style.xml:642(para)
+msgid "Other parts of this guide discuss in more detail tone and language usage that can cause offense."
+msgstr ""
+
+#: en_US/style.xml:653(title)
+msgid "Grammar and Usage Guidelines"
+msgstr ""
+
+#: en_US/style.xml:656(title)
+msgid "Bibliographical Information"
+msgstr ""
+
+#: en_US/style.xml:657(para)
+msgid "This section is drawn partly from the <citetitle>GDSG</citetitle>, and partly from <citetitle>The Elements of Style</citetitle>, updated as necessary for the needs of 21st-century technical documentation writers."
+msgstr ""
+
+#. FIXME: Again, check attribution viz. GNU FDL. This will be more work
+#. than the previous section.
+#: en_US/style.xml:668(para)
+msgid "This section contains an alphabetical list of grammar and usage guidelines for use in Fedora documentation. Many of these guidelines are only applicable to English-language usage, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:679(term)
+msgid "Abbreviations"
+msgstr ""
+
+#: en_US/style.xml:681(para)
+msgid "A shortened form of a word or phrase that takes the place of the full word or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, <literal>p.m.</literal>, and so on. Apply the following rules when you use abbreviations:"
+msgstr ""
+
+#: en_US/style.xml:689(para)
+msgid "Avoid creating new abbreviations. Unfamiliar abbreviations can confuse rather than clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:695(para)
+msgid "Do not explain or expand familiar abbreviations."
+msgstr ""
+
+#: en_US/style.xml:700(para)
+msgid "Do not include familiar abbreviations in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:706(para)
+msgid "For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other words\" and <literal>e.g.</literal> for \"for example\", do not use the abbreviation. Spell out the entire phrase."
+msgstr ""
+
+#: en_US/style.xml:715(term)
+msgid "Adjectives"
+msgstr ""
+
+#: en_US/style.xml:717(para)
+msgid "Use adjectives with caution. If an adjective is necessary to differentiate between items, then use adjectives. In all cases, test whether the phrase can stand alone without the adjective."
+msgstr ""
+
+#: en_US/style.xml:726(term)
+msgid "Acronyms"
+msgstr ""
+
+#: en_US/style.xml:728(para)
+msgid "A term that represents a multi-word term. Typically, acronyms are formed in the following ways:"
+msgstr ""
+
+#: en_US/style.xml:734(para)
+msgid "From the first letters of each word in a compound term, for example Table of Contents (TOC)."
+msgstr ""
+
+#: en_US/style.xml:740(para)
+msgid "From recognizable parts of a compound term, such as GNU Object Model Environment (GNOME)."
+msgstr ""
+
+#: en_US/style.xml:746(para)
+msgid "Apply the following rules when you use acronyms:"
+msgstr ""
+
+#: en_US/style.xml:751(para)
+msgid "On the first occurrence of an acronym, spell out the full term, with the acronym in parentheses."
+msgstr ""
+
+#: en_US/style.xml:757(para)
+msgid "Do not spell out the full compound for well-known acronyms, unless you think the information is useful for readers."
+msgstr ""
+
+#: en_US/style.xml:764(para)
+msgid "Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:770(para)
+msgid "Write the acronym in uppercase letters, unless there is a compelling case for lowercase."
+msgstr ""
+
+#: en_US/style.xml:776(para)
+msgid "Include the acronym and the full term in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:785(term)
+msgid "Adverbs"
+msgstr ""
+
+#: en_US/style.xml:787(para)
+msgid "Use adverbs with caution. If an adverb is necessary to qualify the function of a component, then use an adverb. In all cases, test whether the phrase can stand alone without the adverb. Classic superfluous adverbs <literal>simply</literal>, <literal>easily</literal>, <literal>quickly</literal>."
+msgstr ""
+
+#: en_US/style.xml:798(term)
+msgid "Anthropomorphism"
+msgstr ""
+
+#: en_US/style.xml:802(para)
+msgid "Do not apply emotions, desires, or opinions to software applications."
+msgstr ""
+
+#: en_US/style.xml:808(para)
+msgid "Do not apply a sense of location or dimension to a software application. A user can not be \"in\" a text editor."
+msgstr ""
+
+#: en_US/style.xml:818(term)
+msgid "Articles"
+msgstr ""
+
+#: en_US/style.xml:820(para)
+msgid "Do not use the definite article <literal>the</literal> to begin any of the following items:"
+msgstr ""
+
+#: en_US/style.xml:826(para)
+msgid "Manual titles"
+msgstr ""
+
+#: en_US/style.xml:831(para)
+msgid "Chapter titles"
+msgstr ""
+
+#: en_US/style.xml:836(para) en_US/style.xml:1239(term)
+msgid "Headings"
+msgstr ""
+
+#: en_US/style.xml:841(para)
+msgid "Figure captions"
+msgstr ""
+
+#: en_US/style.xml:846(para)
+msgid "Table captions"
+msgstr ""
+
+#: en_US/style.xml:851(para)
+msgid "Callouts"
+msgstr ""
+
+#: en_US/style.xml:859(term)
+msgid "Apostrophe"
+msgstr ""
+
+#: en_US/style.xml:861(para)
+msgid "Do not use apostrophes except where absolutely required"
+msgstr ""
+
+#: en_US/style.xml:866(para)
+msgid "Do not use apostrophes to denote possession."
+msgstr ""
+
+#: en_US/style.xml:871(para)
+msgid "Do not use apostrophes to denote contractions."
+msgstr ""
+
+#: en_US/style.xml:876(para)
+msgid "Do not use apostrophes to denote plurals."
+msgstr ""
+
+#: en_US/style.xml:882(title)
+msgid "Incorrect: Apostrophes"
+msgstr ""
+
+#: en_US/style.xml:885(para)
+msgid "the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+msgstr ""
+
+#: en_US/style.xml:891(para)
+msgid "don't use the default option"
+msgstr ""
+
+#: en_US/style.xml:896(para)
+msgid "several SCSI disk's"
+msgstr ""
+
+#: en_US/style.xml:903(title)
+msgid "Correct: No apostrophes"
+msgstr ""
+
+#: en_US/style.xml:906(para)
+msgid "the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</guimenu>"
+msgstr ""
+
+#: en_US/style.xml:912(para)
+msgid "do not use the default option"
+msgstr ""
+
+#: en_US/style.xml:917(para)
+msgid "several SCSI disks"
+msgstr ""
+
+#: en_US/style.xml:926(term)
+msgid "Brackets"
+msgstr ""
+
+#: en_US/style.xml:930(para)
+msgid "Do not use brackets [such as these] as a substitute for parentheses (such as these)."
+msgstr ""
+
+#: en_US/style.xml:936(para)
+msgid "Use brackets for optional command line entries."
+msgstr ""
+
+#: en_US/style.xml:941(para)
+msgid "Do not use angle brackets to indicate variables in text, instead use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+msgstr ""
+
+#: en_US/style.xml:953(term)
+msgid "Capitalization"
+msgstr ""
+
+#: en_US/style.xml:955(para)
+msgid "Capitalize in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:960(para)
+msgid "All letters in acronyms, unless the acronym is a well-known exception"
+msgstr ""
+
+#: en_US/style.xml:966(para)
+msgid "Initial letter of the first word in a list"
+msgstr ""
+
+#: en_US/style.xml:971(para)
+msgid "Initial letter of the first word in a callout"
+msgstr ""
+
+#: en_US/style.xml:976(para)
+msgid "Initial letter of a key name, such as the <keycap>Shift</keycap> key"
+msgstr ""
+
+#: en_US/style.xml:982(para)
+msgid "Initial letter of a sentence"
+msgstr ""
+
+#: en_US/style.xml:986(title)
+msgid "Command Names"
+msgstr ""
+
+#: en_US/style.xml:987(para)
+msgid "Avoid starting a sentence with a command name or application name that has a lowercase initial letter."
+msgstr ""
+
+#: en_US/style.xml:994(para)
+msgid "Initial letter of a complete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:999(para)
+msgid "Do not capitalize in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1004(para)
+msgid "A compound term that is followed by an abbreviation or an acronym"
+msgstr ""
+
+#: en_US/style.xml:1010(para)
+msgid "When you want to emphasize something"
+msgstr ""
+
+#: en_US/style.xml:1015(para)
+msgid "Variable names"
+msgstr ""
+
+#: en_US/style.xml:1020(para)
+msgid "The initial letter of an incomplete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:1029(term)
+msgid "Captions"
+msgstr ""
+
+#: en_US/style.xml:1031(para)
+msgid "Use the same rules as for headings, for all captions accompanying figures and tables. Do not put a period at the end of a caption."
+msgstr ""
+
+#: en_US/style.xml:1039(term)
+msgid "Colon"
+msgstr ""
+
+#: en_US/style.xml:1041(para)
+msgid "Use a colon in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1046(para)
+msgid "To introduce a list"
+msgstr ""
+
+#: en_US/style.xml:1051(para)
+msgid "Before an explanation"
+msgstr ""
+
+#: en_US/style.xml:1056(para)
+msgid "After an introduction"
+msgstr ""
+
+#: en_US/style.xml:1061(para)
+msgid "Do not use a colon in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1066(para)
+msgid "To introduce a figure or a table"
+msgstr ""
+
+#: en_US/style.xml:1071(para)
+msgid "To introduce headings"
+msgstr ""
+
+#: en_US/style.xml:1076(para)
+msgid "At the end of an introduction to a procedure"
+msgstr ""
+
+#: en_US/style.xml:1084(term)
+msgid "Column headings"
+msgstr ""
+
+#: en_US/style.xml:1086(para)
+msgid "Use the same rules as for headings."
+msgstr ""
+
+#: en_US/style.xml:1092(term)
+msgid "Comma"
+msgstr ""
+
+#: en_US/style.xml:1094(para)
+msgid "Use commas in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1099(para)
+msgid "To separate items in a series"
+msgstr ""
+
+#: en_US/style.xml:1104(para)
+msgid "To separate the parts of a sentence"
+msgstr ""
+
+#: en_US/style.xml:1109(para)
+msgid "To separate nonrestrictive phrases"
+msgstr ""
+
+#: en_US/style.xml:1114(para)
+msgid "Instead of dashes to set off appositives"
+msgstr ""
+
+#: en_US/style.xml:1119(para)
+msgid "With <emphasis>for example</emphasis> and similar expressions"
+msgstr ""
+
+#: en_US/style.xml:1125(para)
+msgid "Do not use commas in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1130(para)
+msgid "In a series of adjectives used as one modifier"
+msgstr ""
+
+#: en_US/style.xml:1135(para)
+msgid "Between two short independent clauses"
+msgstr ""
+
+#: en_US/style.xml:1143(term) en_US/emacs-nxml.xml:86(title)
+msgid "Commands"
+msgstr ""
+
+#: en_US/style.xml:1145(para)
+msgid "Do not use commands as verbs."
+msgstr ""
+
+#: en_US/style.xml:1151(term)
+msgid "Contractions"
+msgstr ""
+
+#: en_US/style.xml:1153(para)
+msgid "Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</emphasis>, or <emphasis>isn't</emphasis>."
+msgstr ""
+
+#: en_US/style.xml:1160(term)
+msgid "Dash"
+msgstr ""
+
+#: en_US/style.xml:1162(para)
+msgid "Do not use the em dash or the en dash. Use a paragraph break or a colon instead, where you want to create an introductory piece of text. If you have several items that you want to introduce, then you can use a variable list."
+msgstr ""
+
+#: en_US/style.xml:1171(term)
+msgid "Ellipsis"
+msgstr ""
+
+#: en_US/style.xml:1173(para)
+msgid "Use an ellipsis in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1178(para)
+msgid "To show that you have omitted something from a sentence"
+msgstr ""
+
+#: en_US/style.xml:1183(para)
+msgid "To indicate a pause when you quote displayed text"
+msgstr ""
+
+#: en_US/style.xml:1191(term)
+msgid "Fractions"
+msgstr ""
+
+#: en_US/style.xml:1193(para)
+msgid "Follow these rules when using fractions:"
+msgstr ""
+
+#: en_US/style.xml:1198(para)
+msgid "Use numerals for fractions in tables and in units of measurement, but spell out fractions in prose."
+msgstr ""
+
+#: en_US/style.xml:1204(para)
+msgid "Use a space between a numeral and a related fraction, if there is a possible ambiguity. For example: 1 1/2 instead of 11/2."
+msgstr ""
+
+#: en_US/style.xml:1211(para)
+msgid "If a fraction is used in a compound modifier, insert a hyphen between the fraction and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1220(term)
+msgid "Gender"
+msgstr ""
+
+#: en_US/style.xml:1222(para)
+msgid "Refer to <xref linkend=\"sn-fundamentals-9\"/>."
+msgstr ""
+
+#: en_US/style.xml:1228(term)
+msgid "Grammar"
+msgstr ""
+
+#: en_US/style.xml:1230(para)
+msgid "Use standard American English grammar rules, refer to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1241(para)
+msgid "Use the following capitalization rules in headings:"
+msgstr ""
+
+#: en_US/style.xml:1246(para)
+msgid "Initial uppercase letter of the first word"
+msgstr ""
+
+#: en_US/style.xml:1251(para)
+msgid "Initial uppercase letter for all nouns, adjectives, and verbs."
+msgstr ""
+
+#: en_US/style.xml:1257(para)
+msgid "All lowercase letters for conjunctions, articles, and prepositions of fewer than four letters"
+msgstr ""
+
+#: en_US/style.xml:1263(para)
+msgid "Initial uppercase letter for prepositions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1269(para)
+msgid "Initial uppercase letter for conjunctions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1280(term)
+msgid "Hyphen"
+msgstr ""
+
+#: en_US/style.xml:1282(para)
+msgid "Use hyphens in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1287(para)
+msgid "With a numeral in a compound modifier"
+msgstr ""
+
+#: en_US/style.xml:1291(para)
+msgid "To prevent ambiguity"
+msgstr ""
+
+#: en_US/style.xml:1296(para)
+msgid "With some standard prefixes and suffixes. Use the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidance"
+msgstr ""
+
+#: en_US/style.xml:1305(para)
+msgid "In spelled-out fractions"
+msgstr ""
+
+#: en_US/style.xml:1310(para)
+msgid "In variable names of two or more words, such as <replaceable>directory-name</replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+msgstr ""
+
+#: en_US/style.xml:1317(para)
+msgid "Do not use hyphens in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1322(para)
+msgid "For industry-accepted terms"
+msgstr ""
+
+#: en_US/style.xml:1327(para)
+msgid "To construct verbs"
+msgstr ""
+
+#: en_US/style.xml:1332(para)
+msgid "With an adverb ending in <emphasis>ly</emphasis>"
+msgstr ""
+
+#: en_US/style.xml:1337(para)
+msgid "With numerals as single modifiers"
+msgstr ""
+
+#: en_US/style.xml:1342(para)
+msgid "With a word that is listed as unhyphenated in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+msgstr ""
+
+#: en_US/style.xml:1351(para)
+msgid "With trademarked terms"
+msgstr ""
+
+#: en_US/style.xml:1359(term)
+msgid "Latin terms"
+msgstr ""
+
+#: en_US/style.xml:1361(para)
+msgid "Do not use Latin terms. Use an equivalent English term instead."
+msgstr ""
+
+#: en_US/style.xml:1368(term)
+msgid "Like"
+msgstr ""
+
+#: en_US/style.xml:1370(para)
+msgid "Do not use the term <emphasis>like</emphasis> to denote equivalence or similarity."
+msgstr ""
+
+#: en_US/style.xml:1377(term)
+msgid "Lists"
+msgstr ""
+
+#: en_US/style.xml:1379(para)
+msgid "Introduce a list with a complete sentence that ends with a colon."
+msgstr ""
+
+#: en_US/style.xml:1386(term)
+msgid "Numbers"
+msgstr ""
+
+#: en_US/style.xml:1388(para)
+msgid "Spell out numbers in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1393(para)
+msgid "Numbers from zero through nine unless the number is part of a measurement"
+msgstr ""
+
+#: en_US/style.xml:1398(para)
+msgid "Approximations"
+msgstr ""
+
+#: en_US/style.xml:1403(para)
+msgid "Extreme values such as <emphasis>million</emphasis>, but precede the value with a numeral"
+msgstr ""
+
+#: en_US/style.xml:1409(para)
+msgid "Any number that begins a sentence"
+msgstr ""
+
+#: en_US/style.xml:1414(para)
+msgid "A number that is immediately followed by a numeral, for example: <literal>two 10 MB files</literal>"
+msgstr ""
+
+#: en_US/style.xml:1423(term)
+msgid "Numerals"
+msgstr ""
+
+#: en_US/style.xml:1425(para)
+msgid "Use numerals in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1430(para)
+msgid "The number 10 or greater"
+msgstr ""
+
+#: en_US/style.xml:1435(para)
+msgid "Negative numbers"
+msgstr ""
+
+#: en_US/style.xml:1439(para)
+msgid "Most fractions"
+msgstr ""
+
+#: en_US/style.xml:1444(para)
+msgid "Percentages"
+msgstr ""
+
+#: en_US/style.xml:1449(para)
+msgid "Decimals"
+msgstr ""
+
+#: en_US/style.xml:1454(para)
+msgid "Measurements"
+msgstr ""
+
+#: en_US/style.xml:1459(para)
+msgid "Units of time smaller than one second"
+msgstr ""
+
+#: en_US/style.xml:1464(para)
+msgid "References to bits and bytes"
+msgstr ""
+
+#: en_US/style.xml:1472(term)
+msgid "Parentheses"
+msgstr ""
+
+#: en_US/style.xml:1474(para)
+msgid "Use parentheses in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1479(para)
+msgid "To contain the abbreviation of a term on the first occurrence of the full term"
+msgstr ""
+
+#: en_US/style.xml:1485(para)
+msgid "In man page references, specifically the section number"
+msgstr ""
+
+#: en_US/style.xml:1493(term)
+msgid "Period"
+msgstr ""
+
+#: en_US/style.xml:1495(para)
+msgid "Use a period in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1500(para)
+msgid "To end a sentence"
+msgstr ""
+
+#: en_US/style.xml:1505(para)
+msgid "In file and directory names"
+msgstr ""
+
+#: en_US/style.xml:1510(para)
+msgid "In abbreviations that can be mistaken for words, such as a.m. and U.S."
+msgstr ""
+
+#: en_US/style.xml:1519(term)
+msgid "Punctuation"
+msgstr ""
+
+#: en_US/style.xml:1521(para)
+msgid "Use standard American English punctuation rules. In addition to the specific points of punctuation in this section, refer also to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1531(term)
+msgid "Punctuation in numbers"
+msgstr ""
+
+#: en_US/style.xml:1533(para)
+msgid "Do not use a comma in numerals of four digits. Use a comma in numerals of more than four digits."
+msgstr ""
+
+#: en_US/style.xml:1540(term)
+msgid "Quotation marks"
+msgstr ""
+
+#: en_US/style.xml:1542(para)
+msgid "Use quotation marks to indicate material that is taken verbatim from another source. Do not use quotation marks to excuse terms from legitimacy. If the term is not legitimate, then use another term. If you must use that term, declare the term in the glossary and make the term legitimate."
+msgstr ""
+
+#: en_US/style.xml:1553(term)
+msgid "See v. Refer to"
+msgstr ""
+
+#: en_US/style.xml:1555(para)
+msgid "When referring a user to another resource, use \"refer to\" instead of \"see\", and \"refer also to\" instead of \"see also\". This differentiates from the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag\">seealso</sgmltag> tags that are used in indexing. These tags create special links in the index. To be consistent throughout the document, we reserve the special words \"see\" and \"see also\" for hyperlinked index references, and use \"refer to\" and \"refer also to\" for non-hyperlinked and non-indexed references."
+msgstr ""
+
+#: en_US/style.xml:1570(term)
+msgid "Semicolon"
+msgstr ""
+
+#: en_US/style.xml:1572(para)
+msgid "Do not use semicolons."
+msgstr ""
+
+#: en_US/style.xml:1578(term)
+msgid "Slash"
+msgstr ""
+
+#: en_US/style.xml:1580(para)
+msgid "Except where required as part of a filename, do not use slashes \"/\" in your writing. The construction <literal>and/or</literal>, for example, does not exist. Use one or the other term instead."
+msgstr ""
+
+#: en_US/style.xml:1589(term)
+msgid "Spelling"
+msgstr ""
+
+#: en_US/style.xml:1591(para)
+msgid "Use standard American English spelling rules, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+msgstr ""
+
+#: en_US/style.xml:1600(term)
+msgid "Titles"
+msgstr ""
+
+#: en_US/style.xml:1602(para)
+msgid "For manual titles use the same rules as for headings."
+msgstr ""
+
+#: en_US/style.xml:1608(term)
+msgid "Units"
+msgstr ""
+
+#: en_US/style.xml:1610(para)
+msgid "Follow these rules when using units:"
+msgstr ""
+
+#: en_US/style.xml:1615(para)
+msgid "Use standard abbreviations for units of measurements, do not invent your own abbreviations."
+msgstr ""
+
+#: en_US/style.xml:1621(para)
+msgid "For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of Electrical and Electronics Terms</citetitle>."
+msgstr ""
+
+#: en_US/style.xml:1630(para)
+msgid "Use periods for abbreviated units that might be mistaken for a word."
+msgstr ""
+
+#: en_US/style.xml:1636(para)
+msgid "Most standard abbreviations of units account for both singular and plural usage."
+msgstr ""
+
+#: en_US/style.xml:1642(para)
+msgid "Insert a space between the numeral and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1656(title)
+msgid "Composition Tips"
+msgstr ""
+
+#. This section will collect miscellanea and advice for specific
+#. situations that the FDP editors encounter. I hope they will feel
+#. free to e-mail me sticky situations or particularly interesting
+#. examples of work they've beautified. Hopefully not too much will be
+#. drawn from my own work! - PWF.
+#: en_US/style.xml:1668(para)
+msgid "This section contains usage tips based on situations the Fedora Documentation Project editors have encountered in the past. You should read and understand these examples to improve your own documentation. The Fedora Documentation Project editors welcome additional examples."
+msgstr ""
+
+#: en_US/style.xml:1676(title)
+msgid "Active Voice"
+msgstr ""
+
+#: en_US/style.xml:1677(para)
+msgid "Always use active voice, except when it is awkward to do so. The tutorial tells the user how to accomplish a task, and should give instructions clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. These words are redundant in a tutorial, since the reader assumes you are outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" \"might,\" and other words that indicate you are unsure about the subject matter. Your tutorial should cover a subject authoritatively. The reader should never be concerned about unknown effects of following the tutorial."
+msgstr ""
+
+#: en_US/style.xml:1690(title)
+msgid "Incorrect: Passive voice"
+msgstr ""
+
+#: en_US/style.xml:1691(para)
+msgid "The <command>yum update</command> command must be run."
+msgstr ""
+
+#: en_US/style.xml:1694(para)
+msgid "You might want to run the <command>yum update</command> command."
+msgstr ""
+
+#: en_US/style.xml:1700(title)
+msgid "Correct: Active voice"
+msgstr ""
+
+#: en_US/style.xml:1701(para)
+msgid "Run the <command>yum update</command> command."
+msgstr ""
+
+#: en_US/style.xml:1708(title)
+msgid "Present Tense"
+msgstr ""
+
+#: en_US/style.xml:1709(para)
+msgid "Write in the present tense. A good rule of thumb is that the words \"will\" and \"shall\" are almost never needed in describing what the user should do or see. They add unnecessary length to sentences and can confuse translators. They are also often indicators of passive voice; refer also to <xref linkend=\"sn-misc-active-voice\"/>."
+msgstr ""
+
+#: en_US/style.xml:1718(title)
+msgid "Incorrect: Future tense"
+msgstr ""
+
+#: en_US/style.xml:1719(para)
+msgid "The application will display a list of target files."
+msgstr ""
+
+#: en_US/style.xml:1722(para)
+msgid "A list of target files will be displayed by the application."
+msgstr ""
+
+#: en_US/style.xml:1727(title)
+msgid "Correct: Present tense"
+msgstr ""
+
+#: en_US/style.xml:1728(para)
+msgid "The application displays a list of target files."
+msgstr ""
+
+#: en_US/style.xml:1735(title)
+msgid "Narrative Voice"
+msgstr ""
+
+#: en_US/style.xml:1736(para)
+msgid "Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself the writer (whether including the reader or not), the Fedora Documentation Project, the Fedora community, or any other group. Do not refer to users with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word \"one.\" It is acceptable to refer to the reader with the second person pronoun \"you.\""
+msgstr ""
+
+#: en_US/style.xml:1745(title)
+msgid "Incorrect: First or third person"
+msgstr ""
+
+#: en_US/style.xml:1746(para)
+msgid "As described in the last section, I always run <command>up2date</command> before configuring the Samba server."
+msgstr ""
+
+#: en_US/style.xml:1751(para)
+msgid "If the user needs to back up his or her files, s/he should use the <command>tar</command> or <command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1757(title)
+msgid "Correct: Second (or no) person"
+msgstr ""
+
+#: en_US/style.xml:1758(para)
+msgid "Refer to the section on <command>up2date</command> before configuring the Samba server."
+msgstr ""
+
+#: en_US/style.xml:1762(para)
+msgid "If necessary, users can back up files with the <command>tar</command> or <command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1770(title)
+msgid "Negative Words"
+msgstr ""
+
+#: en_US/style.xml:1771(para)
+msgid "Avoid negative words when possible, since they give documentation an overly dogmatic tone. The word \"avoid\" is useful for this purpose. Note that contractions are often used for negative words such as <emphasis>don't</emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-contractions\"/>."
+msgstr ""
+
+#: en_US/style.xml:1782(title)
+msgid "Uncertainty"
+msgstr ""
+
+#: en_US/style.xml:1783(para)
+msgid "Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the like. While occasional use of these constructions is acceptable, overuse reduces the authority of your documentation. The documentation should adequately cover a stock installation of Fedora. It is impossible for a tutorial-length document to cover every possible configuration scenario. Address the most common scenarios and note discrepancies only as required."
+msgstr ""
+
+#: en_US/style.xml:1795(title)
+msgid "Redundant Coverage"
+msgstr ""
+
+#: en_US/style.xml:1796(para)
+msgid "Avoid covering redundant material, such as how to update a Fedora system. These overarching topics may be covered in other tutorials. Writers frequently violate this guideline because they feel their tutorial is not long enough. Keep your tutorial from wandering off-topic. Instead, refer the reader to a separate tutorial whenever possible for complete coverage of that topic."
+msgstr ""
+
+#: en_US/style.xml:1808(title)
+msgid "Self-referential Value Judgments"
+msgstr ""
+
+#: en_US/style.xml:1809(para)
+msgid "Avoid statements such as \"One of the most important things to do is <replaceable>XYZ</replaceable>.\" If the procedure is important, the reader already expects it to be in your tutorial. The converse is also true: If a procedure appears in your tutorial, the reader expects it is important. This is especially true if you use a whole section for the procedure in question. Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as required. If the whole section concerns how to do <replaceable>XYZ</replaceable>, leave this sentence out entirely. Refer also to <xref linkend=\"vle-golden-rule-4\"/>."
+msgstr ""
+
+#: en_US/style.xml:1824(title)
+msgid "Precision of Language"
+msgstr ""
+
+#: en_US/style.xml:1825(para)
+msgid "Use precise words for actions users should take. Do not instruct users to \"go\" to a selection, or \"find\" a menu."
+msgstr ""
+
+#: en_US/style.xml:1830(title)
+msgid "Incorrect: Imprecise wording"
+msgstr ""
+
+#: en_US/style.xml:1833(para)
+msgid "Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</guimenuitem>"
+msgstr ""
+
+#: en_US/style.xml:1839(para)
+msgid "Find the option labeled <guilabel>Search</guilabel>"
+msgstr ""
+
+#: en_US/style.xml:1846(title)
+msgid "Correct: Precise wording"
+msgstr ""
+
+#: en_US/style.xml:1849(para)
+msgid "From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</guimenuitem>"
+msgstr ""
+
+#: en_US/style.xml:1855(para)
+msgid "Select the <guilabel>Search</guilabel> option"
+msgstr ""
+
+#: en_US/style.xml:1862(title)
+msgid "Do Not Discriminate Against Non-GUI Users"
+msgstr ""
+
+#: en_US/style.xml:1863(para)
+msgid "If you are writing about a GUI-only application, you may use \"click\" freely. If you are writing about an application that has a text-mode interface, use \"select\" instead as shown above."
+msgstr ""
+
+#: en_US/style.xml:1874(title)
+msgid "DocBook Tips"
+msgstr ""
+
+#: en_US/style.xml:1875(para)
+msgid "This section contains tips on how to use DocBook tags more effectively in your documentation."
+msgstr ""
+
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:268(title)
+msgid "Admonitions"
+msgstr ""
+
+#: en_US/style.xml:1882(para)
+msgid "Avoid overuse of admonitions. Keep admonitions short and effective by using only the most important material inside the admonition. Move any background material required to explain the admonition statements outside the admonition. Use a short but descriptive title for an admonition. Use title case for the admonition title."
+msgstr ""
+
+#: en_US/style.xml:1891(title)
+msgid "Incorrect: Lengthy admonition"
+msgstr ""
+
+#: en_US/style.xml:1894(title)
+msgid "Use <command>sfdisk</command> to check input"
+msgstr ""
+
+#: en_US/style.xml:1895(para)
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1909(title)
+msgid "Correct: Brief admonition"
+msgstr ""
+
+#: en_US/style.xml:1917(title)
+msgid "Check Input"
+msgstr ""
+
+#: en_US/style.xml:1918(para)
+msgid "Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1910(para)
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. <placeholder-1/>"
+msgstr ""
+
+#: en_US/style.xml:1925(para)
+msgid "Avoid punctuation in titles for sections or admonitions, except for commas only where demanded. Use a title that says something about the admonition comment, such as \"Reboot Required,\" instead of simply using the admonition type for a title (\"Note\")."
+msgstr ""
+
+#: en_US/style.xml:1932(para)
+msgid "Follow the capitalization rules for headings in the title of an admonition."
+msgstr ""
+
+#: en_US/style.xml:1939(title)
+msgid "The <sgmltag class=\"starttag\">replaceable</sgmltag> Tag"
+msgstr ""
+
+#: en_US/style.xml:1941(para)
+msgid "If your documentation formally states a specific value will be used as a convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag in your text or examples."
+msgstr ""
+
+#: en_US/style.xml:1950(title)
+msgid "XML Entities"
+msgstr ""
+
+#: en_US/style.xml:1951(para)
+msgid "Use the entities provided by the Fedora Documentation Project. These entities are found in the <filename>common/</filename> folder in the <filename>fedora-docs</filename> distribution. (Refer also to <xref linkend=\"ch-getting-files\"/>.) For instance, do not use abbreviations such as \"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" which produces the text \"Fedora 9.\""
+msgstr ""
+
+#: en_US/writing-guidelines.xml:11(title)
+msgid "Fedora Documentation Guidelines"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:14(primary) en_US/writing-guidelines.xml:15(see)
+msgid "recursion"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:19(primary) en_US/writing-guidelines.xml:26(secondary)
+msgid "RTFM"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:20(secondary)
+msgid "read the fine manual"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:21(seealso) en_US/writing-guidelines.xml:25(primary)
+msgid "humor"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:29(para)
+msgid "Please read this chapter carefully. This chapter describes the guidelines that must be followed such as naming conventions."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:32(para)
+msgid "This chapter only discusses tags used for documentation for the Fedora Project, not all available DocBook XML tags. For the complete list, refer to <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:38(title)
+msgid "File Header"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:40(title)
+msgid "XML Header"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:41(para)
+msgid "In accordance with good XML practices, the first line in any DocBook XML source files should identify the file as XML. Use the following line as the first line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:47(title)
+msgid "CVS Id Header"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:48(para)
+msgid "All the files must contain the CVS Id header. Use the following line as the second line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:51(para)
+msgid "Any time the file is committed to CVS, the line is updated automatically to include information about the file. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:58(title)
+msgid "ID Naming Conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:61(primary) en_US/writing-guidelines.xml:74(primary) en_US/writing-guidelines.xml:275(primary) en_US/writing-guidelines.xml:280(primary) en_US/writing-guidelines.xml:285(primary) en_US/writing-guidelines.xml:290(primary) en_US/writing-guidelines.xml:295(primary) en_US/writing-guidelines.xml:300(primary) en_US/writing-guidelines.xml:306(primary) en_US/writing-guidelines.xml:312(primary) en_US/writing-guidelines.xml:318(primary) en_US/writing-guidelines.xml:324(primary) en_US/writing-guidelines.xml:350(primary) en_US/writing-guidelines.xml:355(primary) en_US/writing-guidelines.xml:360(primary) en_US/writing-guidelines.xml:365(primary) en_US/writing-guidelines.xml:370(primary)
+msgid "XML tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:62(secondary) en_US/writing-guidelines.xml:66(primary) en_US/writing-guidelines.xml:79(primary)
+msgid "naming conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:69(para)
+msgid "This section explains the ID naming convention. IDs are unique identifiers that allow DocBook XML to cross-reference a section, chapter, or other element."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:75(secondary) en_US/writing-guidelines.xml:80(secondary)
+msgid "rules for defining an ID"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:83(para)
+msgid "The following general rules apply to IDs:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:87(para)
+msgid "Keep an ID as short and simple as possible."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:90(para)
+msgid "Start the ID with the special short two-character label. This makes URLs and other references to this ID human readable, by self-identifying the XML container type."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:96(para)
+msgid "<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used properly."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:102(title)
+msgid "Proper ID Usage"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:111(title)
+msgid "Two-Character Naming Conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:112(segtitle)
+msgid "Tag"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:113(segtitle)
+msgid "Prefix"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:115(sgmltag)
+msgid "preface"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:116(literal)
+msgid "pr-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:119(sgmltag)
+msgid "chapter"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:120(literal)
+msgid "ch-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:123(sgmltag)
+msgid "section"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:124(literal)
+msgid "sn-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:127(sgmltag)
+msgid "figure"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:128(literal)
+msgid "fig-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:131(sgmltag) en_US/writing-guidelines.xml:235(sgmltag)
+msgid "table"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:132(literal)
+msgid "tb-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:135(sgmltag)
+msgid "appendix"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:136(literal)
+msgid "ap-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:139(sgmltag)
+msgid "part"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:140(literal)
+msgid "pt-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:143(sgmltag)
+msgid "example"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:144(literal)
+msgid "ex-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:148(para)
+msgid "Use the title of the item as the ID. Make your titles unique within a document to prevent conflicts. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:157(title)
+msgid "XML Tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:159(primary)
+msgid "xml tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:160(secondary)
+msgid "caveats"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:163(para)
+msgid "It is very important that you remember the caveats in this section. These are learned suggestions or rules that make your XML experience better."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:171(term)
+msgid "Do Not Use Trademark Entities"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:173(para)
+msgid "Do not use the trademark entities <sgmltag class=\"genentity\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class=\"genentity\">reg</sgmltag> because the do not produce HTML output that works for all charsets. The HTML output produces by these entities are declared in the DTD and cannot be changed via the stylesheet."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:181(para)
+msgid "Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes as follows:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:184(segtitle)
+msgid "DocBook XML source"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:185(segtitle)
+msgid "Rendered content"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:189(trademark)
+msgid "trademark symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:196(trademark)
+msgid "registered trademark symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:202(trademark)
+msgid "copyright symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:209(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:211(para)
+msgid "In general, use <sgmltag>para</sgmltag> tags around anything other than a simple paragraph. Doing so will create additional white space within the text itself in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:216(para)
+msgid "Specifically, do not use <sgmltag>para</sgmltag> tags around the following (or, to put this another way, do not embed the following within <sgmltag class=\"element\">para</sgmltag> elements):"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:223(sgmltag)
+msgid "screen"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:226(sgmltag)
+msgid "itemizedlist"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:229(sgmltag)
+msgid "orderedlist"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:232(sgmltag)
+msgid "variablelist"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:241(term)
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag>listitem</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:244(para)
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</emphasis> start immediately after the beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:252(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:254(para)
+msgid "The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) <emphasis>must</emphasis> be flush left in the XML file; otherwise, the extraneous whitespace will appear in the HTML version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:271(primary) en_US/writing-guidelines.xml:301(secondary) en_US/writing-guidelines.xml:307(secondary) en_US/writing-guidelines.xml:313(secondary) en_US/writing-guidelines.xml:319(secondary) en_US/writing-guidelines.xml:325(secondary)
+msgid "admonitions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:276(secondary) en_US/writing-guidelines.xml:302(tertiary) en_US/writing-guidelines.xml:371(secondary)
+msgid "warning"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:281(secondary) en_US/writing-guidelines.xml:308(tertiary) en_US/writing-guidelines.xml:356(secondary)
+msgid "tip"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:286(secondary) en_US/writing-guidelines.xml:314(tertiary) en_US/writing-guidelines.xml:351(secondary)
+msgid "note"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:291(secondary) en_US/writing-guidelines.xml:320(tertiary) en_US/writing-guidelines.xml:361(secondary)
+msgid "caution"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:296(secondary) en_US/writing-guidelines.xml:326(tertiary) en_US/writing-guidelines.xml:366(secondary)
+msgid "important"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:329(para)
+msgid "There are five types of admonitions in DocBook: <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the admonitions have the same structure: an optional <sgmltag class=\"element\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD does not impose any specific semantics on the individual admonitions. For example, DocBook does not mandate that a <sgmltag class=\"element\">warning</sgmltag> is reserved for cases where bodily harm can result."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:343(title)
+msgid "Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element\">warning</sgmltag>"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:374(para)
+msgid "There are several ways to bring attention to text within a document. A <emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to bring additional information to the users' attention. A <emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful information or another way to do something. A <emphasis><sgmltag class=\"element\">caution</sgmltag></emphasis> is used to show the user they must be careful when attempting a certain step. An <emphasis><sgmltag class=\"element\">important</sgmltag></emphasis> tag set can be used to show the user a piece of information that should not be overlooked. While this information may not change anything the user is doing, it should show the user that this piece of information could be vital. A <emphasis><sgmltag class=\"element\">warning</sgmltag></emphasis> is used to show the reader that their current setup will change or be altered, such as files being removed, and they should not c
hoose this operation unless they are alright with the consequences."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:394(para)
+msgid "The following lines of code show the basic setup for each case mentioned above, along with its appearance in HTML."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:403(title) en_US/emacs.xml:257(title) en_US/emacs.xml:562(title) en_US/emacs-nxml.xml:160(title)
+msgid "Note"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:404(para) en_US/writing-guidelines.xml:424(para) en_US/writing-guidelines.xml:434(para) en_US/writing-guidelines.xml:444(para)
+msgid "Body of text goes here."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:413(title) en_US/emacs-nxml.xml:114(title)
+msgid "Tip"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:414(para)
+msgid "Body of text goes here"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:423(title)
+msgid "Caution"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:433(title) en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:443(title)
+msgid "Warning"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:451(title)
+msgid "Screenshots"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:454(primary) en_US/writing-guidelines.xml:459(see) en_US/writing-guidelines.xml:463(see)
+msgid "screenshots"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:455(secondary)
+msgid "how to take"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:458(primary)
+msgid "screen captures"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:462(primary)
+msgid "screen grabs"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:466(para)
+msgid "Screenshots are illustrations that show the state of a display the user may encounter. Screenshots can be either graphical or textual. However, screenshots use a great deal of space in a text document to convey relatively small amounts of information. The same space in the document can hold a greater amount of more descriptive and helpful information. Therefore, authors should avoid screenshots whenever possible in favor of descriptive text."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:474(para)
+msgid "One of the isolated instances in which screenshots are useful is to demonstrate a physical screen layout that is unfamiliar to a reader. <emphasis>This does not mean that illustrations of dialog boxes are good uses of screenshots.</emphasis> On the contrary, dialogs are simply instances of a user interface element with which a reader is already familiar. An annotated diagram in certain cases, however, explains to the reader where to find functional landmarks on the screen such as menu bars."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:482(para)
+msgid "The steps for taking a graphical screenshot illustrate how using text to describe a procedure is more concise than a series of screenshots."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:487(term)
+msgid "Graphical Screenshot"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:491(para)
+msgid "Create a new user account to make screenshots. The new account uses the distribution default theme, fonts, and element sizes. The resulting screenshot has an appearance familiar to the largest number of readers, and makes Fedora Documentation Project documents consistent."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:498(para)
+msgid "Before taking the screenshot, if possible, resize the targeted GUI element(s) to the smallest possible size. The target image should be 500 pixels wide or less. If the screenshot includes more than one GUI element, you may need to resize the screenshot in a following step."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:506(para)
+msgid "To take the screenshot, select the GUI element with the mouse to bring it to the forefront, or otherwise arrange the elements. Press <keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to capture a single GUI window. For capturing the entire desktop use <keycap>Print Screen</keycap>. If the shot includes multiple elements grouped closely together, crop the resulting PNG format image in <application>The GIMP</application>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:518(para)
+msgid "If necessary, resize the image using <application>The GIMP</application>. Open the image, then right-click on it and choose <menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</guimenuitem></menuchoice>. With the chain symbol intact, set the <guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click <guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the image before converting it."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:534(para)
+msgid "With the image open in <application>The GIMP</application>, right-click the image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As...</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</guibutton>. Allow flattening of the image by clicking <guibutton>Export</guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:545(para)
+msgid "A <guilabel>Save as PostScript</guilabel> window appears. Select <guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:559(term)
+msgid "Text Screenshot"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:561(para)
+msgid "Textual screen information is also useful for readers. Follow these guidelines for textual screenshots:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:565(para)
+msgid "If a graphical screenshot illustrates a function, and the textual mode has identical functions, do not include both, unless omitting either would make your description unclear."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:571(para)
+msgid "Make the information generic over specific, and omit any username and machine information if possible. Do not include the shell prompt unless it is vital to the demonstration."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:577(para)
+msgid "Separate what the user types from sample command output."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:581(para)
+msgid "When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show what the user types, and use <sgmltag class=\"element\">computeroutput</sgmltag> tags to show the resulting output."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:589(para)
+msgid "<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual screenshot usage."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:594(title)
+msgid "Correct Textual Screenshot (XML Source and HTML)"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:607(para)
+msgid "To find all the currently active ssh sessions, execute the following command:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:609(userinput)
+#, no-wrap
+msgid "ps ax | grep ssh"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:611(para)
+msgid "Output appears similar to the following:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:613(computeroutput)
+#, no-wrap
+msgid " 2564 ? S 0:23 /usr/sbin/sshd\n 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n 8032 pts/0 S 0:00 ssh user@@host.example.com\n 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:648(title)
+msgid "Previewing Your Work"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:649(para)
+msgid "The GNOME <application>Help</application> browser, also known as <command>yelp</command>, and the KDE <application>Khelp</application> documentation browser can render DocBook XML information as needed. Use these applications to preview your work if you prefer reading your work in a browser-like environment. Run the following command:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:656(para)
+msgid "Make sure to point the preferred help browser at the top parent file of your XML document. Once the document loads, you can add a bookmark for it for ease of use later."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:660(title)
+msgid "Using Bookmarks"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:661(para)
+msgid "Keeping your documents in the same place for every checkout session makes help browser bookmarks more effective."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:664(para)
+msgid "Once you have a bookmark stored, it will appear in the help browser at every use. You can now hit <keycap>F1</keycap> during any GUI session to launch the help browser. Then choose your bookmark from the menu to preview your document at any time."
+msgstr ""
+
+#: en_US/module-struct.xml:12(title)
+msgid "How Modules Work"
+msgstr ""
+
+#: en_US/module-struct.xml:13(para)
+msgid "Documentation modules have a specific structure that enables the preconfigured tools to work correctly. Follow this structure exactly or you may have problems building your module. The Fedora Documentation Project build tools locate resources in the module and use them to build new output such as HTML or RPM packages."
+msgstr ""
+
+#: en_US/module-struct.xml:19(title)
+msgid "Structure of a Module"
+msgstr ""
+
+#: en_US/module-struct.xml:20(para)
+msgid "<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example module, excluding any <filename class=\"directory\">CVS</filename> folders. Note that this example document does not have branches."
+msgstr ""
+
+#: en_US/module-struct.xml:25(title)
+msgid "Example Module Structure"
+msgstr ""
+
+#: en_US/module-struct.xml:47(title)
+msgid "CVS Module Contents"
+msgstr ""
+
+#: en_US/module-struct.xml:48(segtitle)
+msgid "Component"
+msgstr ""
+
+#: en_US/module-struct.xml:49(segtitle)
+msgid "Type"
+msgstr ""
+
+#: en_US/module-struct.xml:50(segtitle)
+msgid "Usage Notes"
+msgstr ""
+
+#: en_US/module-struct.xml:52(seg)
+msgid "Primary language directory"
+msgstr ""
+
+#: en_US/module-struct.xml:53(seg) en_US/module-struct.xml:94(seg) en_US/module-struct.xml:101(seg)
+msgid "required"
+msgstr ""
+
+#: en_US/module-struct.xml:56(filename) en_US/module-struct.xml:181(systemitem)
+msgid "en_US"
+msgstr ""
+
+#: en_US/module-struct.xml:60(firstterm)
+msgid "entities"
+msgstr ""
+
+#: en_US/module-struct.xml:61(para)
+msgid "Think of an XML entity as a predefined snippet of information. It can represent a chunk of XML source, or simply a word or character. If the information changes, it need be replaced only once, in the definition, to fix all usage."
+msgstr ""
+
+#: en_US/module-struct.xml:54(seg)
+msgid "This is the only directory absolutely required. It is named for the original language of the document, such as <placeholder-1/> (US English). The primary language does not have to be US English; all languages are supported. This directory contains all the XML source for the actual document, as well as XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr ""
+
+#: en_US/module-struct.xml:69(seg)
+msgid "Graphics directory"
+msgstr ""
+
+#: en_US/module-struct.xml:70(seg) en_US/module-struct.xml:80(seg)
+msgid "optional"
+msgstr ""
+
+#: en_US/module-struct.xml:71(filename) en_US/module-struct.xml:75(filename)
+msgid "figs/"
+msgstr ""
+
+#: en_US/module-struct.xml:71(seg)
+msgid "The <placeholder-1/> directory is an optional directory where graphics for the document should be stored. If graphics are screenshots that are particular to a language, the <placeholder-2/> directory can and should be stored in a language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:79(seg)
+msgid "Translation (PO) directory"
+msgstr ""
+
+#: en_US/module-struct.xml:81(filename) en_US/module-struct.xml:87(filename)
+msgid "po/"
+msgstr ""
+
+#: en_US/module-struct.xml:83(acronym)
+msgid "PO"
+msgstr ""
+
+#: en_US/module-struct.xml:88(filename)
+msgid "LINGUAS"
+msgstr ""
+
+#: en_US/module-struct.xml:89(firstterm)
+msgid "locales"
+msgstr ""
+
+#: en_US/module-struct.xml:81(seg)
+msgid "The <placeholder-1/> directory contains specially formatted Portable Object, or <placeholder-2/>, files created and used by translators. The Fedora Documentation Project build tools use these files to create translated versions of documents. The translated documents are not stored in CVS; they are created as needed from these PO files. The <placeholder-3/> directory also contains the <placeholder-4/> file, which lists the active translation <placeholder-5/>, or languages."
+msgstr ""
+
+#: en_US/module-struct.xml:93(seg) en_US/module-struct.xml:95(filename)
+msgid "Makefile"
+msgstr ""
+
+#: en_US/module-struct.xml:95(seg)
+msgid "The <placeholder-1/> controls the build process. Its content is discussed in <xref linkend=\"ex-makefile\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:100(filename) en_US/module-struct.xml:102(filename)
+msgid "rpm-info.xml"
+msgstr ""
+
+#: en_US/module-struct.xml:102(seg)
+msgid "The <placeholder-1/> file contains document specific metadata"
+msgstr ""
+
+#: en_US/module-struct.xml:107(title)
+msgid "Common Build Tools"
+msgstr ""
+
+#: en_US/module-struct.xml:108(para)
+msgid "Never add the <systemitem>docs-common</systemitem> build tools directory to an individual module. Special formatting in the module list downloads these tools when a user checks out a document module. For more information, refer to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:116(title)
+msgid "The Document Build System"
+msgstr ""
+
+#: en_US/module-struct.xml:121(para)
+msgid "In Linux and Fedora documentation, references to commands often include a number inside parentheses. This number represents the section of <firstterm>manpages</firstterm> that includes documentation for that command. To read the manpage for <command>make(1)</command>, use the command <command>man 1 make</command>."
+msgstr ""
+
+#: en_US/module-struct.xml:117(para)
+msgid "The build system can render the document into another format such as <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</command><placeholder-1/> and shell scripts. Authors need <emphasis>no</emphasis> prior experience with either shell scripts or a <command>make(1)</command>."
+msgstr ""
+
+#: en_US/module-struct.xml:133(title)
+msgid "The Document <filename>Makefile</filename>"
+msgstr ""
+
+#: en_US/module-struct.xml:134(para)
+msgid "Each individual document has its own <filename>Makefile</filename>, which only needs to be a few lines long. The document <filename>Makefile</filename> content is designed for cut and paste operations."
+msgstr ""
+
+#: en_US/module-struct.xml:140(para)
+msgid "<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</filename> for a simple document with two files and two translations."
+msgstr ""
+
+#: en_US/module-struct.xml:146(title)
+msgid "Sample Document Makefile"
+msgstr ""
+
+#: en_US/module-struct.xml:162(para)
+msgid "Do not be concerned with some of the more complicated syntax such as the <command>XMLFILES_template</command> stanza. An explanation for this template appears a few paragraphs below."
+msgstr ""
+
+#: en_US/module-struct.xml:168(title)
+msgid "Makefile Variables"
+msgstr ""
+
+#: en_US/module-struct.xml:169(segtitle)
+msgid "Variable"
+msgstr ""
+
+#: en_US/module-struct.xml:170(segtitle) en_US/module-struct.xml:240(segtitle)
+msgid "Explanation"
+msgstr ""
+
+#: en_US/module-struct.xml:172(systemitem)
+msgid "DOCBASE"
+msgstr ""
+
+#: en_US/module-struct.xml:173(seg)
+msgid "This variable contains the name for the main (parent) XML document. Follow convention by naming your document after the module name."
+msgstr ""
+
+#: en_US/module-struct.xml:178(systemitem)
+msgid "PRI_LANG"
+msgstr ""
+
+#: en_US/module-struct.xml:179(seg)
+msgid "This variable contains the ISO code for the original version of the document, such as <placeholder-1/>."
+msgstr ""
+
+#: en_US/module-struct.xml:184(systemitem)
+msgid "DOC_ENTITIES"
+msgstr ""
+
+#: en_US/module-struct.xml:185(seg)
+msgid "This variable contains a listing of any files containing entity definitions. The Fedora Documentation Project uses a special XML format to record document-specific entities, so they can be translated and built on the fly like any other XML document. An example is shown later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:194(systemitem)
+msgid "XMLFILES_template"
+msgstr ""
+
+#: en_US/module-struct.xml:197(systemitem)
+msgid "${1}"
+msgstr ""
+
+#: en_US/module-struct.xml:202(systemitem)
+msgid "${1}/"
+msgstr ""
+
+#: en_US/module-struct.xml:195(seg)
+msgid "This template allows the build tools to work with the document in multiple languages once it is translated. The <placeholder-1/> marking is a variable used to substitute the appropriate language. This template is not terribly complicated. For a new module, duplicate this section exactly except for the actual filenames. Prepend the text <placeholder-2/>, in place of the language code directory name, to each filename in your document."
+msgstr ""
+
+#: en_US/module-struct.xml:208(title)
+msgid "Files Exempt From Listing"
+msgstr ""
+
+#: en_US/module-struct.xml:209(para)
+msgid "Do not include the document-specific entities XML file or the <filename>rpm-info.xml</filename> file, which will be discussed later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:213(para)
+msgid "The final section, beginning with <literal>define</literal>, locates the main <filename>Makefile.common</filename> for the build system. This <filename>Makefile.common</filename> file contains all the <application>make(1)</application> targets and rules to actually build the document and the various archives."
+msgstr ""
+
+#: en_US/module-struct.xml:222(title)
+msgid "The Document <filename>rpm-info.xml</filename>"
+msgstr ""
+
+#: en_US/module-struct.xml:223(para)
+msgid "Each document module's primary language directory contains a file called <filename>rpm-info.xml</filename>. This file contains document-specific metadata used to generate revision history, copyright, and contributor information. It follows a DTD specification included with the rest of the build system tools."
+msgstr ""
+
+#: en_US/module-struct.xml:232(title)
+msgid "Build System Actions"
+msgstr ""
+
+#: en_US/module-struct.xml:233(para)
+msgid "To render the <abbrev>XML</abbrev> document into another format, use one of the following <command>make</command> targets:"
+msgstr ""
+
+#: en_US/module-struct.xml:238(title)
+msgid "Build Targets"
+msgstr ""
+
+#: en_US/module-struct.xml:239(segtitle)
+msgid "Target"
+msgstr ""
+
+#: en_US/module-struct.xml:242(systemitem)
+msgid "help"
+msgstr ""
+
+#: en_US/module-struct.xml:243(seg)
+msgid "This target prints a list of available targets and their descriptions."
+msgstr ""
+
+#: en_US/module-struct.xml:247(systemitem)
+msgid "validate-xml"
+msgstr ""
+
+#: en_US/module-struct.xml:248(firstterm)
+msgid "validates"
+msgstr ""
+
+#: en_US/module-struct.xml:248(seg)
+msgid "This target <placeholder-1/> the XML files to make sure they are not only well-formed, but follow the DTD. Some viewers of XML documents may not work correctly until you run this target. This target includes copying required entity files so that validating XML viewers work properly"
+msgstr ""
+
+#: en_US/module-struct.xml:256(systemitem)
+msgid "html"
+msgstr ""
+
+#: en_US/module-struct.xml:257(abbrev) en_US/module-struct.xml:268(abbrev) en_US/module-struct.xml:293(abbrev) en_US/module-struct.xml:298(abbrev)
+msgid "HTML"
+msgstr ""
+
+#: en_US/module-struct.xml:261(systemitem) en_US/module-struct.xml:271(systemitem)
+msgid "${DOCBASE}"
+msgstr ""
+
+#: en_US/module-struct.xml:262(systemitem) en_US/module-struct.xml:272(systemitem)
+msgid "${LANG}"
+msgstr ""
+
+#: en_US/module-struct.xml:260(filename)
+msgid "<placeholder-1/>-<placeholder-2/>/"
+msgstr ""
+
+#: en_US/module-struct.xml:257(seg)
+msgid "This target builds the \"chunked\" <placeholder-1/> document for each defined translation. Output is placed in a separate directory named <placeholder-2/>. Each document section is a separate file within that directory."
+msgstr ""
+
+#: en_US/module-struct.xml:267(systemitem)
+msgid "html-nochunks"
+msgstr ""
+
+#: en_US/module-struct.xml:270(filename)
+msgid "<placeholder-1/>-<placeholder-2/>.html"
+msgstr ""
+
+#: en_US/module-struct.xml:268(seg)
+msgid "This target builds the \"non-chunked\" <placeholder-1/> document for each defined translation. Output is placed in a single file: <placeholder-2/>; no other files are created."
+msgstr ""
+
+#: en_US/module-struct.xml:276(systemitem)
+msgid "pdf"
+msgstr ""
+
+#: en_US/module-struct.xml:277(abbrev) en_US/module-struct.xml:278(abbrev) en_US/module-struct.xml:294(abbrev) en_US/module-struct.xml:299(abbrev)
+msgid "PDF"
+msgstr ""
+
+#: en_US/module-struct.xml:277(seg)
+msgid "This target builds only the <placeholder-1/> document for all document languages. <placeholder-2/> production is currently erratic and may not work for your document."
+msgstr ""
+
+#: en_US/module-struct.xml:282(systemitem)
+msgid "tarball"
+msgstr ""
+
+#: en_US/module-struct.xml:283(command)
+msgid "tar(1)"
+msgstr ""
+
+#: en_US/module-struct.xml:283(seg)
+msgid "This target builds only the <placeholder-1/> archive for all document languages."
+msgstr ""
+
+#: en_US/module-struct.xml:287(systemitem)
+msgid "all"
+msgstr ""
+
+#: en_US/module-struct.xml:288(seg)
+msgid "This target builds all targets listed above."
+msgstr ""
+
+#: en_US/module-struct.xml:291(systemitem) en_US/module-struct.xml:300(filename)
+msgid "clean"
+msgstr ""
+
+#: en_US/module-struct.xml:293(emphasis)
+msgid "not"
+msgstr ""
+
+#: en_US/module-struct.xml:292(seg)
+msgid "This target deletes any temporary, or generated files, but does <placeholder-1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr ""
+
+#: en_US/module-struct.xml:297(systemitem)
+msgid "distclean"
+msgstr ""
+
+#: en_US/module-struct.xml:298(seg)
+msgid "This target erases all <placeholder-1/>, <placeholder-2/>, and archive files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr ""
+
+#: en_US/module-struct.xml:305(title)
+msgid "PDF Generation is Erratic"
+msgstr ""
+
+#: en_US/module-struct.xml:306(para)
+msgid "<abbrev>PDF</abbrev> production is currently erratic and may not work for your document."
+msgstr ""
+
+#: en_US/module-struct.xml:311(title)
+msgid "Adding or Changing Targets"
+msgstr ""
+
+#: en_US/module-struct.xml:312(para)
+msgid "To add a new target and rules, place them at the bottom of the document <filename>Makefile</filename>, below the <literal>include</literal> line. Follow your target definitions with a double colon, not a single colon. The double colon allows you to specify additional rules for existing targets, or to write rules for a new target."
+msgstr ""
+
+#: en_US/module-struct.xml:320(para)
+msgid "For more information on using <command>make(1)</command>, consult the online documentation with the command <command>info make</command> in a terminal."
+msgstr ""
+
+#: en_US/module-struct.xml:327(title)
+msgid "Using Document Image Files"
+msgstr ""
+
+#: en_US/module-struct.xml:328(para)
+msgid "Tutorial documents often make use of images such as <filename class=\"extension\">.PNG</filename> files. Store image files in a <filename class=\"directory\">figs/</filename> folder in the main module directory, as shown in <xref linkend=\"ex-module-structure\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:335(para)
+msgid "Depending on the output media, sometimes images may be scaled, streteched, or squashed. To minimize any distortions, we recommend that you use only <filename class=\"extension\">.PNG</filename> images. Avoid <filename class=\"extension\">.JPG</filename> files. The <command>convert(1)</command> program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</abbrev> package, provides a convenient way to reformat <filename class=\"extension\">.JPG</filename> images into <filename class=\"extension\">.PNG</filename> format. For more information on formatting images such as screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:349(para)
+msgid "Image files may be organized into subdirectories under <filename>figs/</filename> if necessary. The document building system recreates the image subdirectory structure in the output documents."
+msgstr ""
+
+#: en_US/module-struct.xml:355(para)
+msgid "Images often contain labels or other text which may need to be localized. A screenshot of a program, for example, may require a version for each translated language. Name language-dependent image files such as program screenshots by adding the language code to the filename, such as <filename>menu-en_US.png</filename>. Language-independent images, such as <filename>icon.png</filename>, do not need language codes."
+msgstr ""
+
+#: en_US/module-struct.xml:365(para)
+msgid "Sometimes, a document may require images that do not follow the naming convention. To use these images with the document building system, create an ordinary text file containing the image filenames. This file must be named <filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</systemitem> so the build system finds it when searching for image filenames."
+msgstr ""
+
+#: en_US/module-struct.xml:374(para)
+msgid "<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one way to create this <filename>Manifest</filename> file."
+msgstr ""
+
+#: en_US/module-struct.xml:380(title)
+msgid "Building A Manifest"
+msgstr ""
+
+#: en_US/module-struct.xml:387(title)
+msgid "Adding a New DocBook XML File"
+msgstr ""
+
+#: en_US/module-struct.xml:388(para)
+msgid "To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:392(para)
+msgid "Place the new DocBook XML file in the primary language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:396(para)
+msgid "Edit the <filename>Makefile</filename> and add the filename to the <varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to the last existing line, and on the next line add an entry for the new file. Remember to add the <literal>${1}/</literal> prefix as a substitute for the language directory name."
+msgstr ""
+
+#: en_US/module-struct.xml:406(title)
+msgid "Adding a Translation"
+msgstr ""
+
+#: en_US/module-struct.xml:407(para)
+msgid "Translations are stored as PO (portable object) files, which the toolchain transforms into translated documents. Each PO file is based on the POT (PO template) for the document and translated by the Fedora Translation Project. To add a translation, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:414(para)
+msgid "If the <filename class=\"directory\">po/</filename> directory does not exist, create it and add it to CVS:"
+msgstr ""
+
+#: en_US/module-struct.xml:420(para)
+msgid "If it does not exist, create the POT file:"
+msgstr ""
+
+#: en_US/module-struct.xml:424(para)
+msgid "Add the new translation language to the <varname>OTHERS</varname> listing in the <filename>Makefile</filename>."
+msgstr ""
+
+#: en_US/module-struct.xml:429(para)
+msgid "Although translators often copy the POT manually to create the new PO file, the following command also works:"
+msgstr ""
+
+#: en_US/module-struct.xml:432(replaceable)
+msgid "lang"
+msgstr ""
+
+#: en_US/module-struct.xml:432(screen)
+#, no-wrap
+msgid "make po/<placeholder-1/>.po"
+msgstr ""
+
+#: en_US/intro.xml:13(title)
+msgid "Introduction"
+msgstr ""
+
+#: en_US/intro.xml:15(para)
+msgid "The goal of the Fedora Documentation Project is to create easy-to-follow, task-based documentation for Fedora users and developers. The Fedora Documentation Project uses the following tools:"
+msgstr ""
+
+#: en_US/intro.xml:23(para)
+msgid "DocBook XML v4.4"
+msgstr ""
+
+#: en_US/intro.xml:26(para)
+msgid "Custom XSLT stylesheets for both print and HTML versions"
+msgstr ""
+
+#: en_US/intro.xml:30(para)
+msgid "Custom scripts to generate HTML output (use <command>xmlto</command>)"
+msgstr ""
+
+#: en_US/intro.xml:34(para)
+msgid "Emacs with PSGML mode (optional, but recommended)"
+msgstr ""
+
+#: en_US/intro.xml:43(para)
+msgid "This document explains the tools used by the Fedora Documentation Project. It provides writing and tagging guidelines to ensure Fedora documentation is consistent and easy-to-follow."
+msgstr ""
+
+#: en_US/getting-files.xml:12(title)
+msgid "Prerequisites"
+msgstr ""
+
+#: en_US/getting-files.xml:14(para)
+msgid "To work on official Fedora documentation you need to install the required tools. Follow the directions below to configure your system."
+msgstr ""
+
+#: en_US/getting-files.xml:20(title)
+msgid "System Packages"
+msgstr ""
+
+#: en_US/getting-files.xml:22(para)
+msgid "Install the \"Authoring and Publishing\" package group, which contains required DocBook XML files, stylesheets and scripts:"
+msgstr ""
+
+#: en_US/getting-files.xml:28(userinput)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+msgstr ""
+
+#: en_US/getting-files.xml:31(para)
+msgid "Next, install the <filename>cvs</filename> package, which is used to handle revision control on files in the official repository:"
+msgstr ""
+
+#: en_US/getting-files.xml:37(userinput)
+#, no-wrap
+msgid "su -c 'yum install cvs'"
+msgstr ""
+
+#: en_US/getting-files.xml:40(para)
+msgid "If you plan to use <application>Emacs</application> to edit DocBook XML documentation, install <package>psgml</package>, which adds helpful and time-saving functionality to maximize editing efficiency:"
+msgstr ""
+
+#: en_US/getting-files.xml:44(userinput)
+#, no-wrap
+msgid "su -c 'yum install psgml'"
+msgstr ""
+
+#: en_US/getting-files.xml:48(title)
+msgid "Fedora Documentation Tools"
+msgstr ""
+
+#: en_US/getting-files.xml:50(para)
+msgid "The Fedora Documentation Project's custom scripts and stylesheets are stored in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</systemitem> CVS server. When you check out a document module from CVS, the tools are included in the module inside the <filename class=\"directory\">docs-common/</filename> directory. To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:59(para)
+msgid "The most powerful component in the Fedora Documentation Project toolbox is <firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for authoring technical documentation using <firstterm>Extensible Markup Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark pieces of content with descriptive tags. The following output is an example of DocBook XML:"
+msgstr ""
+
+#: en_US/getting-files.xml:76(para)
+msgid "This example article, entitled <citetitle>A Very Short Article</citetitle>, consists of only a single paragraph. The tags, or markup, surround elements of content to define the sense in which they are used. A paragraph, for example, is marked with <sgmltag>para</sgmltag> tags. Text that requires emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does not worry about the visual formatting such as italics or font size. Fedora Documentation Project build tools automatically perform all formatting tasks."
+msgstr ""
+
+#: en_US/getting-files.xml:85(para)
+msgid "The custom tools built by the Fedora Documentation Project render DocBook source into a variety of formats for publication and distribution. They also allow translators to create localized versions of the XML documents for Fedora users around the world. The flexibility of XML allows for a single document to be used many times for many purposes, like reusable code for a programmer."
+msgstr ""
+
+#: en_US/getting-files.xml:91(para)
+msgid "DocBook is itself very well documented. For more information about DocBook, visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also features complete copies of <citetitle>DocBook: The Definitive Guide</citetitle> to browse and download, the canonical source for DocBook information."
+msgstr ""
+
+#: en_US/getting-files.xml:97(title)
+msgid "DocBook XML Versions"
+msgstr ""
+
+#: en_US/getting-files.xml:98(para)
+msgid "DocBook XML, like a computer program, has version numbers. The version used by Fedora Documentation Project right now is 4.4. The DocBook web site may document a slightly newer version, but the majority of the schema still applies."
+msgstr ""
+
+#: en_US/getting-files.xml:103(para)
+msgid "Contributors who use the Microsoft Windows operating system can still make use of DocBook tools. For more information, refer to <ulink url=\"http://www.codeproject.com/winhelp/docbook_howto.asp\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:110(title)
+msgid "Naming Conventions"
+msgstr ""
+
+#: en_US/getting-files.xml:111(para)
+msgid "The Fedora Documentation Project provides the tools, scripts, and stylesheets to transform your <abbrev>XML</abbrev> documents into other output formats such as <abbrev>HTML</abbrev>. In addition, these tools can build your document into a <abbrev>RPM</abbrev> package. To take advantage of these services, follow the conventions in this section to name your files."
+msgstr ""
+
+#: en_US/getting-files.xml:119(para)
+msgid "On the CVS server, directories that contain document files are called <firstterm>modules</firstterm>. Each module represents a single document. Each document may consist of several <firstterm>branches</firstterm> if that document changes with each release of Fedora. Contributors can check out single branches of these modules or the entire module. Each document or branch may contain multiple XML source files."
+msgstr ""
+
+#: en_US/getting-files.xml:126(para)
+msgid "Use the <command>cvs co -c</command> command to view existing module names."
+msgstr ""
+
+#: en_US/getting-files.xml:129(title)
+msgid "Partial List of CVS Modules"
+msgstr ""
+
+#: en_US/getting-files.xml:130(userinput)
+#, no-wrap
+msgid "cd ~/localrepo/fedora-docs/"
+msgstr ""
+
+#: en_US/getting-files.xml:149(para)
+msgid "The leftmost entry in each line is the name of a module you can check out from CVS. The rest of the line ensures that checkouts include the proper branch of a document and the common build tools. For more information on CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:154(para)
+msgid "Note in the listing above that the <systemitem>about-fedora</systemitem> module has two branches available. One branch is for Fedora 7 and one is for forward development to match the current work of developers. On the other hand, the <systemitem>documentation-guide</systemitem> module is not branched."
+msgstr ""
+
+#: en_US/getting-files.xml:161(title)
+msgid "Modules Labeled <filename>-dir</filename>"
+msgstr ""
+
+#: en_US/getting-files.xml:162(para)
+msgid "Modules ending with the suffix <filename>-dir</filename> are not usually helpful to checkout directly. These modules do not include the common build tools and thus do not provide many of the functions contributors require."
+msgstr ""
+
+#: en_US/getting-files.xml:168(title)
+msgid "Module Names"
+msgstr ""
+
+#: en_US/getting-files.xml:169(para)
+msgid "Choose a module name that accurately reflects your document's subject, but avoid any name already taken. The document title without any use of the word <wordasword>fedora</wordasword> is a reasonable choice in most cases. Use the length descriptors <wordasword>tutorial</wordasword> or <wordasword>guide</wordasword> in the module name where appropriate."
+msgstr ""
+
+#: en_US/getting-files.xml:178(title)
+msgid "Avoid Redundancy"
+msgstr ""
+
+#: en_US/getting-files.xml:179(para)
+msgid "Do not use the word <wordasword>fedora</wordasword> to name modules in the Fedora Documentation Project CVS repository."
+msgstr ""
+
+#: en_US/getting-files.xml:185(title)
+msgid "Correct Module Naming"
+msgstr ""
+
+#: en_US/getting-files.xml:186(segtitle)
+msgid "Document Name"
+msgstr ""
+
+#: en_US/getting-files.xml:187(segtitle)
+msgid "CVS Module Name"
+msgstr ""
+
+#: en_US/getting-files.xml:189(seg)
+msgid "Desktop User Guide"
+msgstr ""
+
+#: en_US/getting-files.xml:190(seg)
+msgid "desktop-user-guide"
+msgstr ""
+
+#: en_US/getting-files.xml:194(application)
+msgid "Yum"
+msgstr ""
+
+#: en_US/getting-files.xml:193(seg)
+msgid "Software Management with <placeholder-1/>"
+msgstr ""
+
+#: en_US/getting-files.xml:195(seg)
+msgid "yum-guide"
+msgstr ""
+
+#: en_US/getting-files.xml:198(application)
+msgid "Pup"
+msgstr ""
+
+#: en_US/getting-files.xml:198(seg)
+msgid "Using <placeholder-1/>"
+msgstr ""
+
+#: en_US/getting-files.xml:199(seg)
+msgid "pup-tutorial"
+msgstr ""
+
+#: en_US/getting-files.xml:204(title)
+msgid "File Names"
+msgstr ""
+
+#: en_US/getting-files.xml:205(para)
+msgid "Follow these guidelines for naming files to make collaboration and document reuse easy:"
+msgstr ""
+
+#: en_US/getting-files.xml:209(para)
+msgid "As with module names, avoid using the word <wordasword>fedora</wordasword> in file names since it is redundant."
+msgstr ""
+
+#: en_US/getting-files.xml:214(para)
+msgid "If the document is comprised of many XML files, avoid repeating the name of the document when naming the constituent files."
+msgstr ""
+
+#: en_US/getting-files.xml:219(para)
+msgid "Avoid numbering files to show order, since editors and authors often rearrange documents or reuse their files in other documents."
+msgstr ""
+
+#: en_US/emacs.xml:13(title)
+msgid "Emacs and PSGML Mode"
+msgstr ""
+
+#: en_US/emacs.xml:16(primary)
+msgid "PSGML"
+msgstr ""
+
+#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary) en_US/emacs.xml:43(primary) en_US/emacs.xml:224(primary) en_US/emacs.xml:233(primary) en_US/emacs.xml:238(primary) en_US/emacs.xml:243(primary) en_US/emacs.xml:523(application) en_US/emacs-nxml.xml:18(primary) en_US/emacs-nxml.xml:22(primary)
+msgid "Emacs"
+msgstr ""
+
+#: en_US/emacs.xml:25(secondary)
+msgid "PSGML mode"
+msgstr ""
+
+#: en_US/emacs.xml:28(para)
+msgid "You can use the PSGML mode available for Emacs to make it easier to write in XML format. PSGML mode provides syntax-highlighting, tag completion, and more."
+msgstr ""
+
+#: en_US/emacs.xml:35(title)
+msgid "Installing PSGML"
+msgstr ""
+
+#: en_US/emacs.xml:36(para)
+msgid "To install PSGML, use the <command>yum</command> command:"
+msgstr ""
+
+#: en_US/emacs.xml:37(userinput)
+#, no-wrap
+msgid "yum install psgml"
+msgstr ""
+
+#: en_US/emacs.xml:40(title)
+msgid "Setting Up Your <filename>.emacs</filename> File"
+msgstr ""
+
+#: en_US/emacs.xml:48(filename)
+msgid ".emacs"
+msgstr ""
+
+#: en_US/emacs.xml:51(para)
+msgid "For Emacs to parse your DocBook documents correctly, you must have a <filename>.emacs</filename> file. Cut and paste the following into your existing <filename>.emacs</filename> file or create a new one that contains the following lines:"
+msgstr ""
+
+#: en_US/emacs.xml:181(para)
+msgid "If you have a wheel mouse and are using Emacs version 21, you can add the following to your <filename>.emacs</filename> file so your wheel will work in <application>Emacs</application>:"
+msgstr ""
+
+#: en_US/emacs.xml:192(para)
+msgid "If you are using the older version 20 of <application>Emacs</application>, add the following instead:"
+msgstr ""
+
+#: en_US/emacs.xml:221(title)
+msgid "Customizing Emacs"
+msgstr ""
+
+#: en_US/emacs.xml:225(secondary)
+msgid "customizing"
+msgstr ""
+
+#: en_US/emacs.xml:229(filename)
+msgid ".Xresources"
+msgstr ""
+
+#: en_US/emacs.xml:234(secondary)
+msgid "colors"
+msgstr ""
+
+#: en_US/emacs.xml:239(secondary)
+msgid "font"
+msgstr ""
+
+#: en_US/emacs.xml:244(secondary)
+msgid "geometry"
+msgstr ""
+
+#: en_US/emacs.xml:247(para)
+msgid "The colors, font, and geometry (default size of window) for Emacs in your <filename>~/.Xresources</filename> file. The format for the settings is <userinput>emacs.keyword:value</userinput>."
+msgstr ""
+
+#: en_US/emacs.xml:253(para)
+msgid "The following is a sample <filename>~/.Xresources</filename> file."
+msgstr ""
+
+#: en_US/emacs.xml:258(para)
+msgid "If you have other settings in your <filename>~/.Xresources</filename>, add the following to the end of the file."
+msgstr ""
+
+#: en_US/emacs.xml:270(para)
+msgid "After modifying this file, execute the following command:"
+msgstr ""
+
+#: en_US/emacs.xml:273(command)
+msgid "xrdb -merge ~/.Xresources"
+msgstr ""
+
+#: en_US/emacs.xml:274(para)
+msgid "Then restart <application>Emacs</application> to apply the changes."
+msgstr ""
+
+#: en_US/emacs.xml:395(title)
+msgid "Basic Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:397(para)
+msgid "The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key."
+msgstr ""
+
+#: en_US/emacs.xml:403(title)
+msgid "Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:404(segtitle)
+msgid "Shortcut"
+msgstr ""
+
+#: en_US/emacs.xml:405(segtitle)
+msgid "Description"
+msgstr ""
+
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:412(keycap) en_US/emacs.xml:430(keycap) en_US/emacs.xml:436(keycap) en_US/emacs.xml:443(keycap) en_US/emacs.xml:448(keycap) en_US/emacs.xml:453(keycap) en_US/emacs.xml:458(keycap) en_US/emacs.xml:463(keycap) en_US/emacs.xml:468(keycap) en_US/emacs.xml:473(keycap) en_US/emacs.xml:478(keycap) en_US/emacs.xml:483(keycap) en_US/emacs.xml:488(keycap) en_US/emacs.xml:508(keycap) en_US/emacs.xml:509(keycap) en_US/emacs.xml:514(keycap) en_US/emacs.xml:515(keycap) en_US/emacs.xml:520(keycap) en_US/emacs.xml:521(keycap) en_US/emacs.xml:532(keycap) en_US/emacs.xml:533(keycap) en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "Ctrl"
+msgstr ""
+
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:430(keycap) en_US/emacs.xml:436(keycap) en_US/emacs.xml:448(keycap) en_US/emacs.xml:521(keycap) en_US/emacs.xml:532(keycap) en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "c"
+msgstr ""
+
+#: en_US/emacs.xml:413(keycap)
+msgid "p"
+msgstr ""
+
+#: en_US/emacs.xml:407(seg) en_US/emacs.xml:508(seg) en_US/emacs.xml:514(seg) en_US/emacs.xml:520(seg) en_US/emacs.xml:532(seg) en_US/emacs.xml:540(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+
+#: en_US/emacs.xml:415(seg)
+msgid "Parse DTD"
+msgstr ""
+
+#: en_US/emacs.xml:431(keycap) en_US/emacs.xml:437(keycap)
+msgid "Shift"
+msgstr ""
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:438(keycap)
+msgid ","
+msgstr ""
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:439(keycap)
+msgid "Tab"
+msgstr ""
+
+#: en_US/emacs.xml:430(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+msgstr ""
+
+#: en_US/emacs.xml:433(seg)
+msgid "Display list of valid tags"
+msgstr ""
+
+#: en_US/emacs.xml:436(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of tag, <placeholder-5/>"
+msgstr ""
+
+#: en_US/emacs.xml:440(seg)
+msgid "Complete the tag"
+msgstr ""
+
+#: en_US/emacs.xml:443(keycap)
+msgid "g"
+msgstr ""
+
+#: en_US/emacs.xml:445(seg)
+msgid "Cancel a command in the minibuffer"
+msgstr ""
+
+#: en_US/emacs.xml:449(keycap)
+msgid "/"
+msgstr ""
+
+#: en_US/emacs.xml:448(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:450(seg)
+msgid "Close tag"
+msgstr ""
+
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:533(keycap)
+msgid "a"
+msgstr ""
+
+#: en_US/emacs.xml:455(seg)
+msgid "Move cursor to beginning of line"
+msgstr ""
+
+#: en_US/emacs.xml:458(keycap)
+msgid "e"
+msgstr ""
+
+#: en_US/emacs.xml:460(seg)
+msgid "Move cursor to the end of the line"
+msgstr ""
+
+#: en_US/emacs.xml:463(keycap)
+msgid "Home"
+msgstr ""
+
+#: en_US/emacs.xml:465(seg)
+msgid "Move cursor to the beginning of the file"
+msgstr ""
+
+#: en_US/emacs.xml:468(keycap)
+msgid "End"
+msgstr ""
+
+#: en_US/emacs.xml:470(seg)
+msgid "Move cursor to the end of the file"
+msgstr ""
+
+#: en_US/emacs.xml:473(keycap)
+msgid "k"
+msgstr ""
+
+#: en_US/emacs.xml:475(seg)
+msgid "Cut line"
+msgstr ""
+
+#: en_US/emacs.xml:478(keycap)
+msgid "y"
+msgstr ""
+
+#: en_US/emacs.xml:480(seg)
+msgid "Paste line"
+msgstr ""
+
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:515(keycap)
+msgid "s"
+msgstr ""
+
+#: en_US/emacs.xml:485(seg)
+msgid "Search forward in the file"
+msgstr ""
+
+#: en_US/emacs.xml:488(keycap)
+msgid "r"
+msgstr ""
+
+#: en_US/emacs.xml:490(seg)
+msgid "Search backwards in the file"
+msgstr ""
+
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap) en_US/emacs.xml:527(keycap)
+msgid "Meta"
+msgstr ""
+
+#: en_US/emacs.xml:493(keycap)
+msgid "$"
+msgstr ""
+
+#: en_US/emacs.xml:495(seg) en_US/emacs.xml:500(seg)
+msgid "Check spelling of current word"
+msgstr ""
+
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap) en_US/emacs.xml:508(keycap) en_US/emacs.xml:514(keycap) en_US/emacs.xml:520(keycap)
+msgid "x"
+msgstr ""
+
+#: en_US/emacs.xml:499(keycap) en_US/emacs.xml:504(keycap)
+msgid "Enter"
+msgstr ""
+
+#: en_US/emacs.xml:498(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, <placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:503(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, <placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:505(seg)
+msgid "Check spelling of current buffer"
+msgstr ""
+
+#: en_US/emacs.xml:509(keycap)
+msgid "f"
+msgstr ""
+
+#: en_US/emacs.xml:511(seg)
+msgid "Open file"
+msgstr ""
+
+#: en_US/emacs.xml:517(seg)
+msgid "Save file"
+msgstr ""
+
+#: en_US/emacs.xml:523(seg)
+msgid "Exit <placeholder-1/> and prompt to save files if necessary"
+msgstr ""
+
+#: en_US/emacs.xml:527(keycap)
+msgid "q"
+msgstr ""
+
+#: en_US/emacs.xml:529(seg)
+msgid "Fill paragraph"
+msgstr ""
+
+#: en_US/emacs.xml:536(computeroutput)
+#, no-wrap
+msgid "url"
+msgstr ""
+
+#: en_US/emacs.xml:537(computeroutput)
+#, no-wrap
+msgid "ulink"
+msgstr ""
+
+#: en_US/emacs.xml:535(seg)
+msgid "Edit attributes for a tag (for example, you can edit the <placeholder-1/> attribute of the <placeholder-2/> tag)"
+msgstr ""
+
+#: en_US/emacs.xml:544(seg)
+msgid "Exit edit attributes"
+msgstr ""
+
+#: en_US/emacs.xml:550(title) en_US/emacs-nxml.xml:77(title)
+msgid "Examples"
+msgstr ""
+
+#: en_US/emacs.xml:552(para)
+msgid "The table or reference card of Emacs and PSGML commands can be confusing for beginners. This section provides some examples of how to use them."
+msgstr ""
+
+#: en_US/emacs.xml:559(title)
+msgid "Tag Completion"
+msgstr ""
+
+#: en_US/emacs.xml:563(para)
+msgid "This section assumes that you have already parsed the DTD file."
+msgstr ""
+
+#: en_US/emacs.xml:567(para)
+msgid "To avoid having to type a tag repeatedly, use the key combination <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. At the bottom of the <application>Emacs</application> window, the following prompt appears:"
+msgstr ""
+
+#: en_US/emacs.xml:574(prompt)
+msgid "Tag: <"
+msgstr ""
+
+#: en_US/emacs.xml:576(para)
+msgid "To view a list of available tags, use either the <keycap>Tab</keycap> or <keycap>?</keycap>. If you know the first few letters of a tag, enter them, followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, that tag appears. If more than one completion exists, a complete list of possible tags appears."
+msgstr ""
+
+#: en_US/emacs.xml:585(para)
+msgid "If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, <keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the example below:"
+msgstr ""
+
+#: en_US/emacs.xml:602(title)
+msgid "Tag Closure"
+msgstr ""
+
+#: en_US/emacs.xml:604(para)
+msgid "After you open a tag, you must close it. The easiest way to close an open tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most recently opened tag."
+msgstr ""
+
+#: en_US/emacs.xml:616(title)
+msgid "Other Emacs Tasks"
+msgstr ""
+
+#: en_US/emacs.xml:619(title)
+msgid "Working with One Window"
+msgstr ""
+
+#: en_US/emacs.xml:620(para)
+msgid "Sometimes in <application>Emacs</application>, the window becomes split, with tags completions or other text in an alternate window. To return to a single window, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+msgstr ""
+
+#: en_US/emacs.xml:630(title)
+msgid "Saving Work"
+msgstr ""
+
+#: en_US/emacs.xml:631(para)
+msgid "To save your work, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>."
+msgstr ""
+
+#: en_US/emacs.xml:642(title)
+msgid "The \"Clear/Quit\" Command"
+msgstr ""
+
+#: en_US/emacs.xml:643(para)
+msgid "If the tag completion process becomes unwieldy or confusing, use the keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to exit back to the text. <application>Emacs</application> clears any prompts and returns to the buffer text."
+msgstr ""
+
+#: en_US/emacs.xml:653(title)
+msgid "Opening a new file"
+msgstr ""
+
+#: en_US/emacs.xml:654(para)
+msgid "To open a new file, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the <application>Emacs</application> window. Enter the file name, using <keycap>Tab</keycap> completion if desired, of the file you wish to open."
+msgstr ""
+
+#: en_US/emacs.xml:668(title)
+msgid "Closing <application>Emacs</application>"
+msgstr ""
+
+#: en_US/emacs.xml:669(para)
+msgid "To close <application>Emacs</application> use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have not saved your work, <application>Emacs</application> prompts you to save any changed files."
+msgstr ""
+
+#: en_US/emacs.xml:687(title) en_US/emacs-nxml.xml:127(title)
+msgid "Additional Resources"
+msgstr ""
+
+#: en_US/emacs.xml:689(para)
+msgid "Additional Emacs and PSGML references are available at the following locations:"
+msgstr ""
+
+#: en_US/emacs.xml:697(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+msgid "Emacs Quick Reference Guide"
+msgstr ""
+
+#: en_US/emacs.xml:701(para)
+msgid "Emacs reference card that comes with the <filename>emacs</filename> package. You can print it out as a reference. —<filename>/usr/share/emacs/<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs.xml:708(para)
+msgid "Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+msgstr ""
+
+#: en_US/emacs.xml:714(para)
+msgid "<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of Emacs commands for PSGML mode."
+msgstr ""
+
+#: en_US/emacs.xml:723(citetitle)
+msgid "PSGML Tricks"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:11(title)
+msgid "Emacs and nXML Mode"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:14(primary) en_US/emacs-nxml.xml:51(primary)
+msgid "nXML"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:23(secondary)
+msgid "nXML mode"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:26(para)
+msgid "You can also use the nXML mode available for <application>Emacs</application> to make it even easier to write in DocBook XML format. nXML mode provides context-sensitive editing using completion, real time validity error checking, syntax highlighting and indentation. All you need to do is install an RPM!!"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:35(title)
+msgid "Early stages"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:36(para)
+msgid "Please be aware the nxml-mode for <application>Emacs</application> is quite new, so there are a few things that the advanced user might notice when using it with other documents types. If you keep an eye on the mailing-list, you can keep up to date with these, as well as ask questions. For more details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:48(title)
+msgid "Getting the nXML RPM"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:52(secondary)
+msgid "RPM"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:56(primary)
+msgid "nXML RPM"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:59(para)
+msgid "To use nXML mode with emacs, you will need to install the nXML RPM available from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www.thaiopensource.com/download/\">http://www.thaiopensource.com/download/</ulink>. The source requires a lot more work to setup, therefore we will only be concentrating on the RPM version."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:69(para)
+msgid "Information on where to get the source is available in <xref linkend=\"sn-emacs-additional-resources\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:79(para)
+msgid "Compared to PSGML mode there are only couple of commands that you need. This speeds up writing with <application>Emacs</application> considerably, which means you can concentrate more on the content of your article."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:88(para)
+msgid "To create a tag, type <userinput><</userinput> and then type the keyword. To complete the keyword, press <command>Ctrl-Ret</command>, then add the last <userinput>></userinput>. To close a tag, type <userinput></</userinput>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:97(para)
+msgid "When you open a document that doesn't have a DOCTYPE declaration at the top of the file, you will get this message and tag completion won't work because nXML will not know what format you are writing."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:104(para)
+msgid "To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> and load <filename>docbook.rnc</filename>. <application>Emacs</application> will then prompt you to save it in the current working directory."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:115(para)
+msgid "The commands already discussed are the only differences between using <application>Emacs</application> with PSGML mode and <application>Emacs</application> with nXML mode. You will still need to use all the same commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:129(para)
+msgid "Additional Emacs and nXML references are available at the following locations:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:136(ulink)
+msgid "http://www.thaiopensource.com/download/"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:137(citetitle)
+msgid "Author's download area"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:147(para)
+msgid "Emacs reference card that comes with the <filename>emacs</filename> package. You can print it out as a reference. —<filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:157(title)
+msgid "nXML README File"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:161(para)
+msgid "This file can be found in the directory you extracted the source into, or in <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename> if you installed the RPM."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:169(para)
+msgid "README file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:171(para)
+msgid "This is a new major mode for GNU Emacs for editing XML documents. It supports editing well-formed XML documents and also provides schema-sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:177(para)
+msgid "To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs version 20 will not work properly, nor will XEmacs. To get started, do the following:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:184(command)
+msgid "M-x load-file RET rng-auto.el RET"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:187(para)
+msgid "This defines the necessary autoloads. Now, visit a file containing an XML document, and do the following:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:192(command)
+msgid "M-x nxml-mode"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:195(para)
+msgid "Now do"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:200(command)
+msgid "C-h m"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:203(para)
+msgid "For information on how to use nxml-mode. The beginnings of a manual are in nxml-mode.info. You can read this using:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:209(command)
+msgid "C-u M-x info RET nxml-mode.info RET"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:212(para)
+msgid "It's also installed as an entry at the end of the top-level info directory. So you can read it with <command>C-h i</command> as usual."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:217(para)
+msgid "You can use <filename>test.valid.xml</filename> and <filename>test.invalid.xml</filename> as examples of valid and invalid XML documents."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:223(para)
+msgid "To get things automatically loaded each time you start Emacs, add:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:228(computeroutput)
+#, no-wrap
+msgid " (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n "
+msgstr ""
+
+#: en_US/emacs-nxml.xml:232(para)
+msgid "to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-200YMMDD</computeroutput> is the directory containing the <filename>.elc</filename> files. Note that <filename>rng-auto.el</filename> does not load all of the nxml-mode code; it merely sets things up so that all the features of nxml-mode will be autoloaded properly. You should not try to autoload <filename>rng-auto.el</filename> itself."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:242(para)
+msgid "To use nxml-mode automatically for files with an extension of <filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> or <filename>xhtml</filename>, add the following to your <filename>.emacs</filename> file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:250(computeroutput)
+#, no-wrap
+msgid " (setq auto-mode-alist (cons\n\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n "
+msgstr ""
+
+#: en_US/emacs-nxml.xml:255(para)
+msgid "If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are running Emacs 21.3 or later, then I recommend enabling unify-8859-on-decoding-mode, by adding the following to your <filename>.emacs</filename> file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:263(computeroutput)
+#, no-wrap
+msgid "(unify-8859-on-decoding-mode)"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:266(para)
+msgid "To get validation and schema-sensitive editing, you need a RELAX NG Compact Syntax (RNC) schema for you document. The schema directory includes some schemas for popular document types."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:272(para)
+msgid "For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://relaxng.org/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:277(para)
+msgid "For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial.html</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:282(para)
+msgid "For automatically creating RNC schemas, I recommend my Trang program: <ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee.thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:293(para)
+msgid "Infer an RNC schema from an instance document"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:298(para)
+msgid "Convert a DTD to an RNC schema"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:303(para)
+msgid "Convert a RELAX NG XML syntax schema to an RNC schema"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:288(para)
+msgid "You can use this to <placeholder-1/>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:310(para)
+msgid "To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html\">http://www.pantor.com/download.html\"</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:316(para)
+msgid "To convert a W3C XML Schema to an RNC schema, you need first to convert it to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:323(para)
+msgid "The file <filename>NEWS</filename> describes recent changes."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:327(para)
+msgid "Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug reports, discussion. I will announce all new versions there."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:333(para)
+msgid "James Clark"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:336(para)
+msgid "jjc@@thaiopensource.com"
+msgstr ""
+
+#: en_US/acknowledgments.xml:11(title)
+msgid "Acknowledgments"
+msgstr ""
+
+#: en_US/acknowledgments.xml:13(para)
+msgid "This document is based on a document started by Tammy Fox (tfox at redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray Fuller (jrfuller at redhat.com)."
+msgstr ""
+
+#: en_US/acknowledgments.xml:19(para)
+msgid "A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr ""
+
+#: en_US/acknowledgments.xml:25(para)
+msgid "Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to add the trailing slashes to the <command>figure</command> tag example in <filename>docs-xml-tags.xml</filename>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:32(para)
+msgid "A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been applied to add <xref linkend=\"ch-vim\"/>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:37(para)
+msgid "A patch from Karsten Wade (kwade at redhat.com) has been applied to add <xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields (stickster at gmail.com)."
+msgstr ""
+
+#. This section has been removed.
+#. <para>
+#. A patch from Paul W. Frields (stickster at gmail.com) has been applied
+#. to add more explanation of the <command>screen</command> tag set to <xref
+#. linkend="sn-xml-tags-screen"></xref>.
+#. </para>
+#: en_US/acknowledgments.xml:50(para)
+msgid "A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been applied to more fully explaing the document building system."
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: en_US/acknowledgments.xml:0(None)
+msgid "translator-credits"
+msgstr ""
+
+@
+
+
+1.6
+log
+ at Update POT and PO
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-12-15 16:51-0500\n"
+d40 5
+a44 1
+#: en_US/rpm-info.xml:31(holder)
+d48 1
+a48 1
+#: en_US/rpm-info.xml:33(title)
+d52 1
+a52 1
+#: en_US/rpm-info.xml:34(desc)
+d56 5
+a60 1
+#: en_US/rpm-info.xml:38(details)
+d64 1
+a64 1
+#: en_US/rpm-info.xml:42(details)
+d68 1
+a68 1
+#: en_US/rpm-info.xml:46(details)
+d72 1
+a72 1
+#: en_US/rpm-info.xml:50(details)
+d76 1
+a76 1
+#: en_US/rpm-info.xml:54(details)
+d80 1
+a80 1
+#: en_US/rpm-info.xml:58(details)
+d84 1
+a84 1
+#: en_US/rpm-info.xml:62(details)
+d88 1
+a88 1
+#: en_US/rpm-info.xml:69(details)
+d92 116
+d1985 1
+a1985 1
+msgid "Use the entities provided by the Fedora Documentation Project. These entities are found in the <filename>common/</filename> folder in the <filename>fedora-docs</filename> distribution. (Refer also to <xref linkend=\"ch-getting-files\"/>.) For instance, do not use abbreviations such as \"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" which produces the text \"Fedora 8.\""
+@
+
+
+1.5
+log
+ at Update POT/PO files for DocGuide, minor changes
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-11-14 21:12-0500\n"
+d53 4
+d60 1
+a60 1
+#: en_US/rpm-info.xml:42(details)
+d64 1
+a64 1
+#: en_US/rpm-info.xml:46(details)
+d68 1
+a68 1
+#: en_US/rpm-info.xml:50(details)
+d72 1
+a72 1
+#: en_US/rpm-info.xml:54(details)
+d76 1
+a76 1
+#: en_US/rpm-info.xml:58(details)
+d80 1
+a80 1
+#: en_US/rpm-info.xml:65(details)
+d2575 20
+d2598 1
+a2598 1
+#: en_US/module-struct.xml:243(abbrev) en_US/module-struct.xml:254(abbrev) en_US/module-struct.xml:279(abbrev) en_US/module-struct.xml:284(abbrev)
+d2602 1
+a2602 1
+#: en_US/module-struct.xml:247(systemitem) en_US/module-struct.xml:257(systemitem)
+d2606 1
+a2606 1
+#: en_US/module-struct.xml:248(systemitem) en_US/module-struct.xml:258(systemitem)
+d2610 1
+a2610 1
+#: en_US/module-struct.xml:246(filename)
+d2614 1
+a2614 1
+#: en_US/module-struct.xml:243(seg)
+d2618 1
+a2618 1
+#: en_US/module-struct.xml:253(systemitem)
+d2622 1
+a2622 1
+#: en_US/module-struct.xml:256(filename)
+d2626 1
+a2626 1
+#: en_US/module-struct.xml:254(seg)
+d2630 1
+a2630 1
+#: en_US/module-struct.xml:262(systemitem)
+d2634 1
+a2634 1
+#: en_US/module-struct.xml:263(abbrev) en_US/module-struct.xml:264(abbrev) en_US/module-struct.xml:280(abbrev) en_US/module-struct.xml:285(abbrev)
+d2638 1
+a2638 1
+#: en_US/module-struct.xml:263(seg)
+d2642 1
+a2642 1
+#: en_US/module-struct.xml:268(systemitem)
+d2646 1
+a2646 1
+#: en_US/module-struct.xml:269(command)
+d2650 1
+a2650 1
+#: en_US/module-struct.xml:269(seg)
+d2654 1
+a2654 1
+#: en_US/module-struct.xml:273(systemitem)
+d2658 1
+a2658 1
+#: en_US/module-struct.xml:274(seg)
+d2662 1
+a2662 1
+#: en_US/module-struct.xml:277(systemitem) en_US/module-struct.xml:286(filename)
+d2666 1
+a2666 1
+#: en_US/module-struct.xml:279(emphasis)
+d2670 1
+a2670 1
+#: en_US/module-struct.xml:278(seg)
+d2674 1
+a2674 1
+#: en_US/module-struct.xml:283(systemitem)
+d2678 1
+a2678 1
+#: en_US/module-struct.xml:284(seg)
+d2682 1
+a2682 1
+#: en_US/module-struct.xml:291(title)
+d2686 1
+a2686 1
+#: en_US/module-struct.xml:292(para)
+d2690 1
+a2690 1
+#: en_US/module-struct.xml:296(title)
+d2694 1
+a2694 1
+#: en_US/module-struct.xml:297(para)
+d2698 1
+a2698 1
+#: en_US/module-struct.xml:305(para)
+d2702 1
+a2702 1
+#: en_US/module-struct.xml:312(title)
+d2706 1
+a2706 1
+#: en_US/module-struct.xml:313(para)
+d2710 1
+a2710 1
+#: en_US/module-struct.xml:320(para)
+d2714 1
+a2714 1
+#: en_US/module-struct.xml:334(para)
+d2718 1
+a2718 1
+#: en_US/module-struct.xml:340(para)
+d2722 1
+a2722 1
+#: en_US/module-struct.xml:350(para)
+d2726 1
+a2726 1
+#: en_US/module-struct.xml:359(para)
+d2730 1
+a2730 1
+#: en_US/module-struct.xml:365(title)
+d2734 1
+a2734 1
+#: en_US/module-struct.xml:372(title)
+d2738 1
+a2738 1
+#: en_US/module-struct.xml:373(para)
+d2742 1
+a2742 1
+#: en_US/module-struct.xml:377(para)
+d2746 1
+a2746 1
+#: en_US/module-struct.xml:381(para)
+d2750 1
+a2750 1
+#: en_US/module-struct.xml:391(title)
+d2754 1
+a2754 1
+#: en_US/module-struct.xml:392(para)
+d2758 1
+a2758 1
+#: en_US/module-struct.xml:399(para)
+d2762 1
+a2762 1
+#: en_US/module-struct.xml:405(para)
+d2766 1
+a2766 1
+#: en_US/module-struct.xml:409(para)
+d2770 1
+a2770 1
+#: en_US/module-struct.xml:414(para)
+d2774 1
+a2774 1
+#: en_US/module-struct.xml:417(replaceable)
+d2778 1
+a2778 1
+#: en_US/module-struct.xml:417(screen)
+@
+
+
+1.4
+log
+ at Push new 0.3.1 POT and update PO - ERRATA, this time with new content file
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-08-03 12:42-0400\n"
+d53 8
+d64 1
+a64 1
+#: en_US/rpm-info.xml:42(details)
+d68 1
+a68 1
+#: en_US/rpm-info.xml:46(details)
+d72 1
+a72 1
+#: en_US/rpm-info.xml:50(details)
+d76 1
+a76 1
+#: en_US/rpm-info.xml:57(details)
+d157 4
+d162 4
+d169 1
+a169 1
+#: en_US/publishing.xml:68(screen)
+d174 1
+a174 1
+#: en_US/publishing.xml:71(para)
+d178 1
+a178 1
+#: en_US/publishing.xml:85(para)
+d182 1
+a182 1
+#: en_US/publishing.xml:87(screen)
+d187 1
+a187 1
+#: en_US/publishing.xml:90(para)
+d191 1
+a191 1
+#: en_US/publishing.xml:91(screen)
+d196 1
+a196 1
+#: en_US/publishing.xml:92(para)
+d200 1
+a200 1
+#: en_US/publishing.xml:94(screen)
+d205 1
+a205 1
+#: en_US/publishing.xml:97(para)
+d209 1
+a209 1
+#: en_US/publishing.xml:101(title)
+d213 1
+a213 1
+#: en_US/publishing.xml:103(title)
+d217 1
+a217 1
+#: en_US/publishing.xml:104(para)
+d221 1
+a221 1
+#: en_US/publishing.xml:108(para)
+d225 1
+a225 1
+#: en_US/publishing.xml:115(para)
+d229 1
+a229 1
+#: en_US/publishing.xml:120(para)
+d233 1
+a233 1
+#: en_US/publishing.xml:129(title)
+d237 1
+a237 1
+#: en_US/publishing.xml:130(para)
+d241 1
+a241 1
+#: en_US/publishing.xml:137(para)
+d245 1
+a245 1
+#: en_US/publishing.xml:138(screen)
+d250 1
+a250 1
+#: en_US/publishing.xml:144(para)
+d254 1
+a254 1
+#: en_US/publishing.xml:146(replaceable)
+d258 1
+a258 1
+#: en_US/publishing.xml:146(screen)
+d263 1
+a263 1
+#: en_US/publishing.xml:150(para)
+d267 1
+a267 1
+#: en_US/publishing.xml:151(screen)
+d272 1
+a272 1
+#: en_US/publishing.xml:156(para)
+d276 1
+a276 1
+#: en_US/publishing.xml:165(para)
+d280 1
+a280 1
+#: en_US/publishing.xml:175(para)
+d284 1
+a284 1
+#: en_US/publishing.xml:179(para)
+d288 1
+a288 1
+#: en_US/publishing.xml:183(title)
+d292 1
+a292 1
+#: en_US/publishing.xml:184(para)
+d296 1
+a296 1
+#: en_US/publishing.xml:192(title)
+d300 1
+a300 1
+#: en_US/publishing.xml:193(para)
+d304 1
+a304 1
+#: en_US/publishing.xml:197(para)
+d308 1
+a308 1
+#: en_US/publishing.xml:198(screen)
+d313 1
+a313 1
+#: en_US/publishing.xml:214(para)
+d317 1
+a317 1
+#: en_US/publishing.xml:216(replaceable)
+d321 1
+a321 1
+#: en_US/publishing.xml:216(screen)
+d326 1
+a326 1
+#: en_US/publishing.xml:219(para)
+d330 1
+a330 1
+#: en_US/publishing.xml:221(screen)
+d1857 1
+a1857 1
+msgid "Use the entities provided by the Fedora Documentation Project. These entities are found in the <filename>common/</filename> folder in the <filename>fedora-docs</filename> distribution. (Refer also to <xref linkend=\"ch-getting-files\"/>.) For instance, do not use abbreviations such as \"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" which produces the text \"Fedora 7.\""
+d2302 24
+d2858 5
+a2862 1
+#: en_US/getting-files.xml:106(title)
+d2866 1
+a2866 1
+#: en_US/getting-files.xml:107(para)
+d2870 1
+a2870 1
+#: en_US/getting-files.xml:115(para)
+d2874 1
+a2874 1
+#: en_US/getting-files.xml:122(para)
+d2878 1
+a2878 1
+#: en_US/getting-files.xml:125(title)
+d2882 1
+a2882 1
+#: en_US/getting-files.xml:126(userinput)
+d2887 1
+a2887 1
+#: en_US/getting-files.xml:145(para)
+d2891 1
+a2891 1
+#: en_US/getting-files.xml:150(para)
+d2895 1
+a2895 1
+#: en_US/getting-files.xml:157(title)
+d2899 1
+a2899 1
+#: en_US/getting-files.xml:158(para)
+d2903 1
+a2903 1
+#: en_US/getting-files.xml:164(title)
+d2907 1
+a2907 1
+#: en_US/getting-files.xml:165(para)
+d2911 1
+a2911 1
+#: en_US/getting-files.xml:174(title)
+d2915 1
+a2915 1
+#: en_US/getting-files.xml:175(para)
+d2919 1
+a2919 1
+#: en_US/getting-files.xml:181(title)
+d2923 1
+a2923 1
+#: en_US/getting-files.xml:182(segtitle)
+d2927 1
+a2927 1
+#: en_US/getting-files.xml:183(segtitle)
+d2931 1
+a2931 1
+#: en_US/getting-files.xml:185(seg)
+d2935 1
+a2935 1
+#: en_US/getting-files.xml:186(seg)
+d2939 1
+a2939 1
+#: en_US/getting-files.xml:190(application)
+d2943 1
+a2943 1
+#: en_US/getting-files.xml:189(seg)
+d2947 1
+a2947 1
+#: en_US/getting-files.xml:191(seg)
+d2951 1
+a2951 1
+#: en_US/getting-files.xml:194(application)
+d2955 1
+a2955 1
+#: en_US/getting-files.xml:194(seg)
+d2959 1
+a2959 1
+#: en_US/getting-files.xml:195(seg)
+d2963 1
+a2963 1
+#: en_US/getting-files.xml:200(title)
+d2967 1
+a2967 1
+#: en_US/getting-files.xml:201(para)
+d2971 1
+a2971 1
+#: en_US/getting-files.xml:205(para)
+d2975 1
+a2975 1
+#: en_US/getting-files.xml:210(para)
+d2979 1
+a2979 1
+#: en_US/getting-files.xml:215(para)
+@
+
+
+1.3
+log
+ at Push new 0.3.1 POT and update PO
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-08-03 12:38-0400\n"
+d72 247
+@
+
+
+1.2
+log
+ at Update POT and PO with new metadata strings
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-07-28 18:10-0400\n"
+d53 8
+d64 1
+a64 1
+#: en_US/rpm-info.xml:42(details)
+d68 1
+a68 1
+#: en_US/rpm-info.xml:49(details)
+d1901 1
+a1901 1
+#: en_US/writing-guidelines.xml:403(title) en_US/emacs.xml:257(title) en_US/emacs.xml:557(title) en_US/emacs-nxml.xml:160(title)
+d2059 1
+a2059 1
+#: en_US/module-struct.xml:46(title)
+d2063 1
+a2063 1
+#: en_US/module-struct.xml:47(segtitle)
+d2067 1
+a2067 1
+#: en_US/module-struct.xml:48(segtitle)
+d2071 1
+a2071 1
+#: en_US/module-struct.xml:49(segtitle)
+d2075 1
+a2075 1
+#: en_US/module-struct.xml:51(seg)
+d2079 1
+a2079 1
+#: en_US/module-struct.xml:52(seg) en_US/module-struct.xml:89(seg) en_US/module-struct.xml:96(seg)
+d2083 1
+a2083 1
+#: en_US/module-struct.xml:55(filename) en_US/module-struct.xml:177(systemitem)
+d2087 1
+a2087 1
+#: en_US/module-struct.xml:59(firstterm)
+d2091 1
+a2091 1
+#: en_US/module-struct.xml:60(para)
+d2095 1
+a2095 1
+#: en_US/module-struct.xml:53(seg)
+d2099 1
+a2099 1
+#: en_US/module-struct.xml:68(seg)
+d2103 1
+a2103 1
+#: en_US/module-struct.xml:69(seg) en_US/module-struct.xml:79(seg)
+d2107 1
+a2107 1
+#: en_US/module-struct.xml:70(filename) en_US/module-struct.xml:74(filename)
+d2111 1
+a2111 1
+#: en_US/module-struct.xml:70(seg)
+d2115 1
+a2115 1
+#: en_US/module-struct.xml:78(seg)
+d2119 1
+a2119 1
+#: en_US/module-struct.xml:80(filename) en_US/module-struct.xml:184(filename)
+d2123 1
+a2123 1
+#: en_US/module-struct.xml:82(acronym)
+d2127 10
+a2136 2
+#: en_US/module-struct.xml:80(seg)
+msgid "The <placeholder-1/> directory contains specially formatted Portable Object, or <placeholder-2/>, files created and used by translators. The Fedora Documentation Project build tools use these files to create translated versions of documents. The translated documents are not stored in CVS; they are created as needed from these PO files."
+d2139 1
+a2139 1
+#: en_US/module-struct.xml:88(seg) en_US/module-struct.xml:90(filename)
+d2143 1
+a2143 1
+#: en_US/module-struct.xml:90(seg)
+d2147 1
+a2147 1
+#: en_US/module-struct.xml:95(filename) en_US/module-struct.xml:97(filename)
+d2151 1
+a2151 1
+#: en_US/module-struct.xml:97(seg)
+d2155 1
+a2155 1
+#: en_US/module-struct.xml:102(title)
+d2159 1
+a2159 1
+#: en_US/module-struct.xml:103(para)
+d2163 1
+a2163 1
+#: en_US/module-struct.xml:111(title)
+d2167 1
+a2167 1
+#: en_US/module-struct.xml:116(para)
+d2171 1
+a2171 1
+#: en_US/module-struct.xml:112(para)
+d2175 1
+a2175 1
+#: en_US/module-struct.xml:128(title)
+d2179 1
+a2179 1
+#: en_US/module-struct.xml:129(para)
+d2183 1
+a2183 1
+#: en_US/module-struct.xml:135(para)
+d2187 1
+a2187 1
+#: en_US/module-struct.xml:141(title)
+d2191 1
+a2191 1
+#: en_US/module-struct.xml:158(para)
+d2195 1
+a2195 1
+#: en_US/module-struct.xml:164(title)
+d2199 1
+a2199 1
+#: en_US/module-struct.xml:165(segtitle)
+d2203 1
+a2203 1
+#: en_US/module-struct.xml:166(segtitle) en_US/module-struct.xml:244(segtitle)
+d2207 1
+a2207 1
+#: en_US/module-struct.xml:168(systemitem)
+d2211 1
+a2211 1
+#: en_US/module-struct.xml:169(seg)
+d2215 1
+a2215 1
+#: en_US/module-struct.xml:174(systemitem)
+d2219 1
+a2219 1
+#: en_US/module-struct.xml:175(seg)
+d2223 1
+a2223 9
+#: en_US/module-struct.xml:180(systemitem)
+msgid "OTHERS"
+msgstr ""
+
+#: en_US/module-struct.xml:181(seg)
+msgid "This variable contains a listing of ISO codes for any other versions into which the document has been translated. The module must contain a <placeholder-1/> directory and a PO file for any indicated additional languages."
+msgstr ""
+
+#: en_US/module-struct.xml:188(systemitem)
+d2227 1
+a2227 1
+#: en_US/module-struct.xml:189(seg)
+d2231 1
+a2231 1
+#: en_US/module-struct.xml:198(systemitem)
+d2235 1
+a2235 1
+#: en_US/module-struct.xml:201(systemitem)
+d2239 1
+a2239 1
+#: en_US/module-struct.xml:206(systemitem)
+d2243 1
+a2243 1
+#: en_US/module-struct.xml:199(seg)
+d2247 1
+a2247 1
+#: en_US/module-struct.xml:212(title)
+d2251 1
+a2251 1
+#: en_US/module-struct.xml:213(para)
+d2255 1
+a2255 1
+#: en_US/module-struct.xml:217(para)
+d2259 1
+a2259 1
+#: en_US/module-struct.xml:226(title)
+d2263 1
+a2263 1
+#: en_US/module-struct.xml:227(para)
+d2267 1
+a2267 1
+#: en_US/module-struct.xml:236(title)
+d2271 1
+a2271 1
+#: en_US/module-struct.xml:237(para)
+d2275 1
+a2275 1
+#: en_US/module-struct.xml:242(title)
+d2279 1
+a2279 1
+#: en_US/module-struct.xml:243(segtitle)
+d2283 1
+a2283 1
+#: en_US/module-struct.xml:246(systemitem)
+d2287 1
+a2287 1
+#: en_US/module-struct.xml:247(abbrev) en_US/module-struct.xml:258(abbrev) en_US/module-struct.xml:283(abbrev) en_US/module-struct.xml:288(abbrev)
+d2291 1
+a2291 1
+#: en_US/module-struct.xml:251(systemitem) en_US/module-struct.xml:261(systemitem)
+d2295 1
+a2295 1
+#: en_US/module-struct.xml:252(systemitem) en_US/module-struct.xml:262(systemitem)
+d2299 1
+a2299 1
+#: en_US/module-struct.xml:250(filename)
+d2303 1
+a2303 1
+#: en_US/module-struct.xml:247(seg)
+d2307 1
+a2307 1
+#: en_US/module-struct.xml:257(systemitem)
+d2311 1
+a2311 1
+#: en_US/module-struct.xml:260(filename)
+d2315 1
+a2315 1
+#: en_US/module-struct.xml:258(seg)
+d2319 1
+a2319 1
+#: en_US/module-struct.xml:266(systemitem)
+d2323 1
+a2323 1
+#: en_US/module-struct.xml:267(abbrev) en_US/module-struct.xml:268(abbrev) en_US/module-struct.xml:284(abbrev) en_US/module-struct.xml:289(abbrev)
+d2327 1
+a2327 1
+#: en_US/module-struct.xml:267(seg)
+d2331 1
+a2331 1
+#: en_US/module-struct.xml:272(systemitem)
+d2335 1
+a2335 1
+#: en_US/module-struct.xml:273(command)
+d2339 1
+a2339 1
+#: en_US/module-struct.xml:273(seg)
+d2343 1
+a2343 1
+#: en_US/module-struct.xml:277(systemitem)
+d2347 1
+a2347 1
+#: en_US/module-struct.xml:278(seg)
+d2351 1
+a2351 1
+#: en_US/module-struct.xml:281(systemitem) en_US/module-struct.xml:290(filename)
+d2355 1
+a2355 1
+#: en_US/module-struct.xml:283(emphasis)
+d2359 1
+a2359 1
+#: en_US/module-struct.xml:282(seg)
+d2363 1
+a2363 1
+#: en_US/module-struct.xml:287(systemitem)
+d2367 1
+a2367 1
+#: en_US/module-struct.xml:288(seg)
+d2371 1
+a2371 1
+#: en_US/module-struct.xml:295(title)
+d2375 1
+a2375 1
+#: en_US/module-struct.xml:296(para)
+d2379 1
+a2379 1
+#: en_US/module-struct.xml:300(title)
+d2383 1
+a2383 1
+#: en_US/module-struct.xml:301(para)
+d2387 1
+a2387 1
+#: en_US/module-struct.xml:309(para)
+d2391 1
+a2391 1
+#: en_US/module-struct.xml:316(title)
+d2395 1
+a2395 1
+#: en_US/module-struct.xml:317(para)
+d2399 1
+a2399 1
+#: en_US/module-struct.xml:324(para)
+d2403 1
+a2403 1
+#: en_US/module-struct.xml:338(para)
+d2407 1
+a2407 1
+#: en_US/module-struct.xml:344(para)
+d2411 1
+a2411 1
+#: en_US/module-struct.xml:354(para)
+d2415 1
+a2415 1
+#: en_US/module-struct.xml:363(para)
+d2419 1
+a2419 1
+#: en_US/module-struct.xml:369(title)
+d2423 1
+a2423 1
+#: en_US/module-struct.xml:376(title)
+d2427 1
+a2427 1
+#: en_US/module-struct.xml:377(para)
+d2431 1
+a2431 1
+#: en_US/module-struct.xml:381(para)
+d2435 1
+a2435 1
+#: en_US/module-struct.xml:385(para)
+d2439 1
+a2439 1
+#: en_US/module-struct.xml:395(title)
+d2443 1
+a2443 1
+#: en_US/module-struct.xml:396(para)
+d2447 1
+a2447 1
+#: en_US/module-struct.xml:403(para)
+d2451 1
+a2451 1
+#: en_US/module-struct.xml:409(para)
+d2455 1
+a2455 1
+#: en_US/module-struct.xml:413(para)
+d2459 1
+a2459 1
+#: en_US/module-struct.xml:418(para)
+d2463 1
+a2463 1
+#: en_US/module-struct.xml:421(replaceable)
+d2467 1
+a2467 1
+#: en_US/module-struct.xml:421(screen)
+d2497 1
+a2497 1
+msgid "This document explains the tools used by the Fedora Documentation Project and provides writing and tagging guidelines to make Fedora documentation is consistent and easy-to-follow."
+d2700 1
+a2700 1
+#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary) en_US/emacs.xml:43(primary) en_US/emacs.xml:224(primary) en_US/emacs.xml:233(primary) en_US/emacs.xml:238(primary) en_US/emacs.xml:243(primary) en_US/emacs.xml:518(application) en_US/emacs-nxml.xml:18(primary) en_US/emacs-nxml.xml:22(primary)
+d2813 2
+a2814 2
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:488(keycap) en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap) en_US/emacs.xml:522(keycap)
+msgid "Meta"
+d2817 2
+a2818 2
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap) en_US/emacs.xml:509(keycap) en_US/emacs.xml:515(keycap)
+msgid "x"
+d2821 2
+a2822 2
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:494(keycap) en_US/emacs.xml:499(keycap)
+msgid "Enter"
+d2825 2
+a2826 2
+#: en_US/emacs.xml:407(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, <placeholder-3/>"
+d2829 1
+a2829 1
+#: en_US/emacs.xml:410(seg)
+d2833 1
+a2833 9
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap) en_US/emacs.xml:438(keycap) en_US/emacs.xml:443(keycap) en_US/emacs.xml:448(keycap) en_US/emacs.xml:453(keycap) en_US/emacs.xml:458(keycap) en_US/emacs.xml:463(keycap) en_US/emacs.xml:468(keycap) en_US/emacs.xml:473(keycap) en_US/emacs.xml:478(keycap) en_US/emacs.xml:483(keycap) en_US/emacs.xml:503(keycap) en_US/emacs.xml:504(keycap) en_US/emacs.xml:509(keycap) en_US/emacs.xml:510(keycap) en_US/emacs.xml:515(keycap) en_US/emacs.xml:516(keycap) en_US/emacs.xml:527(keycap) en_US/emacs.xml:528(keycap) en_US/emacs.xml:535(keycap) en_US/emacs.xml:537(keycap)
+msgid "Ctrl"
+msgstr ""
+
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap) en_US/emacs.xml:443(keycap) en_US/emacs.xml:516(keycap) en_US/emacs.xml:527(keycap) en_US/emacs.xml:535(keycap) en_US/emacs.xml:537(keycap)
+msgid "c"
+msgstr ""
+
+#: en_US/emacs.xml:426(keycap) en_US/emacs.xml:432(keycap)
+d2837 1
+a2837 1
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:433(keycap)
+d2841 1
+a2841 1
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:434(keycap)
+d2845 1
+a2845 1
+#: en_US/emacs.xml:425(seg)
+d2849 1
+a2849 1
+#: en_US/emacs.xml:428(seg)
+d2853 1
+a2853 1
+#: en_US/emacs.xml:431(seg)
+d2857 1
+a2857 1
+#: en_US/emacs.xml:435(seg)
+d2861 1
+a2861 1
+#: en_US/emacs.xml:438(keycap)
+d2865 1
+a2865 1
+#: en_US/emacs.xml:440(seg)
+d2869 1
+a2869 1
+#: en_US/emacs.xml:444(keycap)
+d2873 1
+a2873 1
+#: en_US/emacs.xml:443(seg)
+d2877 1
+a2877 1
+#: en_US/emacs.xml:445(seg)
+d2881 1
+a2881 1
+#: en_US/emacs.xml:448(keycap) en_US/emacs.xml:528(keycap)
+d2885 1
+a2885 1
+#: en_US/emacs.xml:450(seg)
+d2889 1
+a2889 1
+#: en_US/emacs.xml:453(keycap)
+d2893 1
+a2893 1
+#: en_US/emacs.xml:455(seg)
+d2897 1
+a2897 1
+#: en_US/emacs.xml:458(keycap)
+d2901 1
+a2901 1
+#: en_US/emacs.xml:460(seg)
+d2905 1
+a2905 1
+#: en_US/emacs.xml:463(keycap)
+d2909 1
+a2909 1
+#: en_US/emacs.xml:465(seg)
+d2913 1
+a2913 1
+#: en_US/emacs.xml:468(keycap)
+d2917 1
+a2917 1
+#: en_US/emacs.xml:470(seg)
+d2921 1
+a2921 1
+#: en_US/emacs.xml:473(keycap)
+d2925 1
+a2925 1
+#: en_US/emacs.xml:475(seg)
+d2929 1
+a2929 1
+#: en_US/emacs.xml:478(keycap) en_US/emacs.xml:510(keycap)
+d2933 1
+a2933 1
+#: en_US/emacs.xml:480(seg)
+d2937 1
+a2937 1
+#: en_US/emacs.xml:483(keycap)
+d2941 1
+a2941 1
+#: en_US/emacs.xml:485(seg)
+d2945 5
+a2949 1
+#: en_US/emacs.xml:488(keycap)
+d2953 1
+a2953 1
+#: en_US/emacs.xml:490(seg) en_US/emacs.xml:495(seg)
+d2957 9
+a2965 1
+#: en_US/emacs.xml:493(seg)
+d2969 1
+a2969 1
+#: en_US/emacs.xml:498(seg)
+d2973 1
+a2973 1
+#: en_US/emacs.xml:500(seg)
+d2977 1
+a2977 1
+#: en_US/emacs.xml:504(keycap)
+d2981 1
+a2981 5
+#: en_US/emacs.xml:503(seg) en_US/emacs.xml:509(seg) en_US/emacs.xml:515(seg) en_US/emacs.xml:527(seg) en_US/emacs.xml:535(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+
+#: en_US/emacs.xml:506(seg)
+d2985 1
+a2985 1
+#: en_US/emacs.xml:512(seg)
+d2989 1
+a2989 1
+#: en_US/emacs.xml:518(seg)
+d2993 1
+a2993 1
+#: en_US/emacs.xml:522(keycap)
+d2997 1
+a2997 1
+#: en_US/emacs.xml:524(seg)
+d3001 1
+a3001 1
+#: en_US/emacs.xml:531(computeroutput)
+d3006 1
+a3006 1
+#: en_US/emacs.xml:532(computeroutput)
+d3011 1
+a3011 1
+#: en_US/emacs.xml:530(seg)
+d3015 1
+a3015 1
+#: en_US/emacs.xml:539(seg)
+d3019 1
+a3019 1
+#: en_US/emacs.xml:545(title) en_US/emacs-nxml.xml:77(title)
+d3023 1
+a3023 1
+#: en_US/emacs.xml:547(para)
+d3027 1
+a3027 1
+#: en_US/emacs.xml:554(title)
+d3031 1
+a3031 1
+#: en_US/emacs.xml:558(para)
+d3035 1
+a3035 1
+#: en_US/emacs.xml:562(para)
+d3039 1
+a3039 1
+#: en_US/emacs.xml:569(prompt)
+d3043 1
+a3043 1
+#: en_US/emacs.xml:571(para)
+d3047 1
+a3047 1
+#: en_US/emacs.xml:580(para)
+d3051 1
+a3051 1
+#: en_US/emacs.xml:597(title)
+d3055 1
+a3055 1
+#: en_US/emacs.xml:599(para)
+d3059 1
+a3059 1
+#: en_US/emacs.xml:611(title)
+d3063 1
+a3063 1
+#: en_US/emacs.xml:614(title)
+d3067 1
+a3067 1
+#: en_US/emacs.xml:615(para)
+d3071 1
+a3071 1
+#: en_US/emacs.xml:625(title)
+d3075 1
+a3075 1
+#: en_US/emacs.xml:626(para)
+d3079 1
+a3079 1
+#: en_US/emacs.xml:637(title)
+d3083 1
+a3083 1
+#: en_US/emacs.xml:638(para)
+d3087 1
+a3087 1
+#: en_US/emacs.xml:648(title)
+d3091 1
+a3091 1
+#: en_US/emacs.xml:649(para)
+d3095 1
+a3095 1
+#: en_US/emacs.xml:663(title)
+d3099 1
+a3099 1
+#: en_US/emacs.xml:664(para)
+d3103 1
+a3103 1
+#: en_US/emacs.xml:682(title) en_US/emacs-nxml.xml:127(title)
+d3107 1
+a3107 1
+#: en_US/emacs.xml:684(para)
+d3111 1
+a3111 1
+#: en_US/emacs.xml:692(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+d3115 1
+a3115 1
+#: en_US/emacs.xml:696(para)
+d3119 1
+a3119 1
+#: en_US/emacs.xml:703(para)
+d3123 1
+a3123 1
+#: en_US/emacs.xml:709(para)
+d3127 1
+a3127 1
+#: en_US/emacs.xml:718(citetitle)
+d3382 7
+a3388 5
+#: en_US/acknowledgments.xml:43(para)
+msgid "A patch from Paul W. Frields (stickster at gmail.com) has been applied to add more explanation of the <command>screen</command> tag set to <xref linkend=\"sn-xml-tags-screen\"/>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:49(para)
+@
+
+
+1.1
+log
+ at Wow, I had no idea it had been that long since we worked on this
+guide. There wasn't even a POT file here? Weird. Well, there is now!
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-07-28 18:02-0400\n"
+d53 4
+d60 1
+a60 1
+#: en_US/rpm-info.xml:45(details)
+@
+
diff --git a/old-documentation-guide/po/it.po,v b/old-documentation-guide/po/it.po,v
new file mode 100644
index 0000000..49e661f
--- /dev/null
+++ b/old-documentation-guide/po/it.po,v
@@ -0,0 +1,6464 @@
+head 1.1;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.1
+date 2009.03.23.22.50.33; author transif; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.1
+log
+ at Sending translation for documentation-guide/po/it.po
+@
+text
+@#
+#
+# mario_santagiuliana <mario at marionline.it>, 2009.
+# Silvio Pierro <perplesso82 at gmail.com>, 2009.
+msgid ""
+msgstr ""
+"Project-Id-Version: documentation-guide.HEAD.it\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2008-05-13 02:06+1000\n"
+"PO-Revision-Date: 2009-03-07 15:04+0100\n"
+"Last-Translator: mario_santagiuliana <mario at marionline.it>\n"
+"Language-Team: Italian <fedora-trans-it at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);X-Generator: Lokalize 0.3\n"
+"X-Generator: Lokalize 0.3\n"
+
+#: en_US/rpm-info.xml:22(rights)
+msgid "OPL"
+msgstr "OPL"
+
+#: en_US/rpm-info.xml:23(version)
+msgid "1.0"
+msgstr "1.0"
+
+#: en_US/rpm-info.xml:26(year)
+msgid "2003"
+msgstr "2003"
+
+#: en_US/rpm-info.xml:27(year)
+msgid "2004"
+msgstr "2004"
+
+#: en_US/rpm-info.xml:28(year)
+msgid "2005"
+msgstr "2005"
+
+#: en_US/rpm-info.xml:29(year)
+msgid "2006"
+msgstr "2006"
+
+#: en_US/rpm-info.xml:30(year)
+msgid "2007"
+msgstr "2007"
+
+#: en_US/rpm-info.xml:31(year)
+msgid "2008"
+msgstr "2008"
+
+#: en_US/rpm-info.xml:32(holder)
+msgid "Red Hat, Inc. and others"
+msgstr "Red Hat, Inc. and others"
+
+#: en_US/rpm-info.xml:34(title)
+msgid "Fedora Documentation Guide"
+msgstr "Guida alla Documentazione Fedora"
+
+#: en_US/rpm-info.xml:35(desc)
+msgid "Guidelines and procedures for producing documentation for Fedora"
+msgstr "Linee guida e procedure per la creazione della documentazione di Fedora"
+
+#: en_US/rpm-info.xml:39(details)
+msgid "Add L10n chapter (#441190)"
+msgstr "Aggiunto capitolo L10n (#441190)"
+
+#: en_US/rpm-info.xml:43(details)
+msgid "Fix some organization and missing targets (#371531)"
+msgstr "Risolta l'organizzazione e alcuni obiettivi mancanti (#371531)"
+
+#: en_US/rpm-info.xml:47(details)
+msgid "Add link to DocBook XML help for Windows"
+msgstr "Aggiunti collegamenti d'aiuto XML al DocBook per Windows"
+
+#: en_US/rpm-info.xml:51(details)
+msgid "Add guidance on CVS web access and previewing work"
+msgstr "Aggiunti l'orientamento sull'accesso web al CVS e l'anteprima del lavoro"
+
+#: en_US/rpm-info.xml:55(details)
+msgid "Add new chapter on publishing"
+msgstr "Aggiunto nuovo capitolo sulla pubblicazione"
+
+#: en_US/rpm-info.xml:59(details)
+msgid "Include information on LINGUAS usage"
+msgstr "Incluse informazioni sull'uso di LINGUAS"
+
+#: en_US/rpm-info.xml:63(details)
+msgid "Remove unnecessary chapter on XML tags"
+msgstr "Rimosso capitolo non necessario sui tag XML"
+
+#: en_US/rpm-info.xml:67(details)
+msgid "Assorted fixes to reflect newer version of reality"
+msgstr "Varie correzioni per rispecchiare la nuova versione della realtà"
+
+#: en_US/rpm-info.xml:74(details)
+msgid "Update to new content and build requirements"
+msgstr "Aggiornamenti di nuovi contenuti e requisiti di struttura"
+
+#: en_US/l10n.xml:13(title)
+msgid "Localization (L10n)"
+msgstr "Localizzazione (L10n)"
+
+#: en_US/l10n.xml:14(para)
+msgid "This chapter discusses how translations are provided in Fedora documentation."
+msgstr ""
+"Questo capitolo spiega come sono fornite le traduzioni nella documentazione "
+"di Fedora."
+
+#: en_US/l10n.xml:19(title)
+msgid "PO Files"
+msgstr "File PO"
+
+#: en_US/l10n.xml:20(para)
+msgid ""
+"The cornerstone of translation when using XML files such as DocBook is the "
+"<firstterm>Portable Object</firstterm> or <acronym>PO</acronym> file. PO "
+"files provide a way for independent individuals or teams to translate "
+"documents. The Fedora Documentation Project toolchain includes rules for "
+"creating, updating, and maintaining these PO files."
+msgstr ""
+"La pietra angolare della traduzione quando si usa un file XML, come un "
+"DocBook, sono i <firstterm>Portable Object</firstterm> o i file <acronym>PO</"
+"acronym>. I file PO offrono la possibilità a individui indipendenti o ai "
+"team di tradurre documenti. Il Fedora Documentation Project toolchain "
+"include regole per creare, aggiornare e mantenere questi file PO."
+
+#: en_US/l10n.xml:28(para)
+msgid "PO files are usually found in two forms:"
+msgstr "I file PO si trovano abitualmente in due forme:"
+
+#: en_US/l10n.xml:33(para)
+msgid ""
+"the <filename class=\"extension\">.pot</filename> file, or <firstterm>PO "
+"Template</firstterm> (<acronym>POT</acronym>)"
+msgstr ""
+"il file <filename class=\"extension\">.pot</filename>, o <firstterm>PO "
+"Template</firstterm> (<acronym>POT</acronym>)"
+
+#: en_US/l10n.xml:41(para)
+msgid ""
+"the <filename class=\"extension\">.po</filename> file, or translation file "
+"(<acronym>PO</acronym>)"
+msgstr ""
+"il file <filename class=\"extension\">.po</filename>, o file tradotto "
+"(<acronym>PO</acronym>)"
+
+#: en_US/l10n.xml:47(para)
+msgid ""
+"A POT is, as the name suggests, a blank template for new translations. It "
+"contains some header information and a list of strings based on the content "
+"of the original XML file from which it was created. Translators do not alter "
+"the POT. The POT should only be changed after changes are made to the "
+"original XML file from which it is derived."
+msgstr ""
+"Un POT è, come il nome suggerisce, un template bianco per le nuove "
+"traduzioni. Contiene alcune informazioni di intestazione e una lista di stringhe basata sul contenuto "
+"del file XML originale da cui esso è stato creato. Il traduttore non deve "
+"alterare il file POT. Le modifiche al file POT dovrebbero essere fatte solo "
+"dopo le modifiche del file XML originale da cui è derivato."
+
+#: en_US/l10n.xml:55(para)
+msgid ""
+"A translator who wishes to start working on a new language copies the POT to "
+"a locale-specific PO file. Then the translator uses any of a number of "
+"command-line or graphical tools to translate each of the strings in the "
+"list. A single POT is used to create many POs, one for each locale. These "
+"files are normally named for their locale code, such as <filename>de.po</"
+"filename>, <filename>it.po</filename>, and so on."
+msgstr ""
+"Un traduttore che vuole iniziare a lavorare su una nuova lingua deve fare "
+"una specifica copia locale di un file PO dal file POT. Poi il traduttore può "
+"usare un qualsiasi strumento grafico o da riga di comando per tradurre ogni "
+"stringa della lista. Un singolo file POT è usato per creare molti file PO, "
+"uno per ogni lingua. Questi file normalmente prendono il nome dal codice "
+"della lingua, ad esempio <filename>de.po</filename>, <filename>it.po</"
+"filename> e così via."
+
+#: en_US/l10n.xml:67(title)
+msgid "Creating or Updating a POT"
+msgstr "Creare o aggiornare un POT"
+
+#: en_US/l10n.xml:68(para)
+msgid ""
+"The POT is named after the document from which it is derived. If document "
+"named in the <filename>Makefile</filename>) is <filename>foo-tutorial.xml</"
+"filename>, the POT is named <filename>foo-tutorial.pot</filename>."
+msgstr ""
+"Il file POT è nominato dopo il documento da cui è derivato. Se il documento "
+"nel <filename>Makefile</filename> ha nome <filename>foo-tutorial.xml</"
+"filename>, il file POT è nominato <filename>foo-tutorial.pot</filename>."
+
+#: en_US/l10n.xml:74(para)
+msgid "To create a new POT, use the following command:"
+msgstr "Per creare un nuovo file POT, usare le seguenti istruzioni:"
+
+#: en_US/l10n.xml:78(para)
+msgid ""
+"The same command is used to update the POT when the original XML sources "
+"change."
+msgstr ""
+"Lo stesso comando è usato per aggiornare il file POT quando il sorgente "
+"originale XML cambia."
+
+#: en_US/l10n.xml:83(title)
+msgid "Keep POT Fresh"
+msgstr "Mantenere aggiornato il file POT"
+
+#: en_US/l10n.xml:84(para)
+msgid ""
+"Update the POT whenever the original XML changes. Many translators' tools "
+"automatically notify them of the change so they can update translations "
+"quickly."
+msgstr ""
+"Aggiornare il POT ogni volta che cambia l'XML originale. Alcuni strumenti di "
+"traduzione notificano automaticamente il traduttore dei cambiamenti così il "
+"traduttore può aggiornare velocemente la traduzione."
+
+#: en_US/l10n.xml:92(title)
+msgid "Updating PO Files"
+msgstr "Aggionare i file PO"
+
+#: en_US/l10n.xml:93(para)
+msgid ""
+"The translation files are created by the individual translators, and "
+"document maintainers do not normally need to create them. Translators update "
+"a list of locales in the <filename>po/LINGUAS</filename> file which defines "
+"all the locales for which translations exist."
+msgstr ""
+"I file tradotti sono creati da traduttori indipendenti e i manutentori dei "
+"documenti normalmente non hanno bisogno di crearli. I traduttori aggiornano "
+"una lista di locazioni nei file <filename>po/LINGUAS</filename> dove "
+"definiscono tutte le locazioni per ogni traduzione esistente."
+
+#: en_US/l10n.xml:100(para)
+msgid ""
+"Whenever the source XML files are updated, the maintainer must at least "
+"update the POT. It is helpful, however, to also merge these changes with the "
+"existing translations for those translators who are not automatically "
+"notified of changes."
+msgstr ""
+"Ogni volta che il sorgente XML è aggiornato, i manutentori devono aggiornare "
+"il POT. E' utile, comunque, fare l'unione dei cambiamenti con le traduzioni "
+"esistenti per quei traduttori che non sono automaticamente avvertiti dei "
+"cambiamenti."
+
+#: en_US/l10n.xml:107(title)
+msgid "Staying Current"
+msgstr "Stare Aggiornati"
+
+#: en_US/l10n.xml:108(para)
+msgid ""
+"Always make sure your local copy of PO is fresh, using the CVS \"update\" "
+"command:"
+msgstr ""
+"Assicurare sempre che la copia locale del file PO sia aggiornata, usando il "
+"comando CVS \"update\" "
+
+#: en_US/l10n.xml:114(para)
+msgid ""
+"To merge new changes into the existing PO translations, use the following "
+"command:"
+msgstr ""
+"Per fare l'unione dei nuovi cambiamenti con le traduzioni PO esistenti, usare il "
+"seguente comando:"
+
+#: en_US/l10n.xml:121(title)
+msgid "Checking Statistics"
+msgstr "Controllare le Statistiche"
+
+#: en_US/l10n.xml:122(para)
+msgid "PO strings fall into three categories:"
+msgstr "Le stringhe dei file PO cadono in tre categorie:"
+
+#: en_US/l10n.xml:127(para)
+msgid ""
+"<firstterm>translated</firstterm>, meaning the string has been handled by a "
+"translator and its source has not changed since then"
+msgstr ""
+"<firstterm>tradotte (translated)</firstterm>, significa la stringa è stata "
+"maneggiata da un traduttore e il suo sorgente non ha subito "
+"modifiche da allora"
+
+#: en_US/l10n.xml:134(para)
+msgid ""
+"<firstterm>fuzzy</firstterm>, meaning the string has changed since it was "
+"last handled by a translator"
+msgstr ""
+"<firstterm>fuzzy</firstterm>, significa che la stringa è stata "
+"cambiata dall'ultima modifica del traduttore"
+
+#: en_US/l10n.xml:140(para)
+msgid ""
+"<firstterm>untranslated</firstterm>, meaning no translation has yet been "
+"provided for this string, or it is brand new"
+msgstr ""
+"<firstterm>non tradotte</firstterm>, significa che non è stata fatta nessuna "
+"traduzione per queste stringe, o sono marcate come nuove"
+
+#: en_US/l10n.xml:146(para)
+msgid ""
+"To see a rough statistical tally of the string handling inside the PO for a "
+"module, use the following command:"
+msgstr ""
+"Per vedere una statistica rudimentale della gestione delle stringhe "
+"all'interno del PO per un modulo, usare il seguente comando:"
+
+#: en_US/l10n.xml:151(para)
+msgid ""
+"For each locale in the list, a count is shown of translated, fuzzy, and "
+"untranslated strings in that order. Tallies that only provide two numerals "
+"are usually translated followed by untranslated. Tallies with only one "
+"numeral are usually fully translated."
+msgstr ""
+"Per ogni locale in lista, viene visualizzato un conteggio di stringhe tradotte, "
+"fuzzy e non tradotte in tale ordine. Le corrispondenze che "
+"forniscono due numeri sono di solito tradotte seguite da non tradotte. Le "
+"corrispondenze con un solo numero sono di solito sono completamente tradotte."
+
+#: en_US/l10n.xml:158(para)
+msgid ""
+"To see only a specific locale, append a dash and the locale code to the "
+"<command>postat</command> target:"
+msgstr ""
+"Per vedere solo una specifica localizzazione, aggiungere una linea e il "
+"codice di localizzazione al campo <command>postat</command>:"
+
+#: en_US/publishing.xml:11(title)
+msgid "Publishing Official Documentation"
+msgstr "Pubblicare la Documentazione Ufficiale"
+
+#: en_US/publishing.xml:12(para)
+msgid ""
+"This chapter shows how to publish official Fedora Documentation Project work "
+"to the <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem> website. To publish official documentation, you must be approved "
+"to write to the web repository in CVS. Access for publishing is limited to "
+"contributors who have demonstrated capacity for working with CVS and other "
+"project tools. Once you have acquired and are comfortable with these skills, "
+"contributions as a publisher are welcome."
+msgstr ""
+"Questo capitolo mostra come pubblicare la Documentazione ufficiale del Fedora "
+"Project sul sito <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem>. Per pubblicare la documentazione ufficiale bisogna avere "
+"l'approvazione per scrivere sui repository web in CVS. L'accesso alla "
+"pubblicazione è limitato ai contributori che hanno dimostrato capacità "
+"lavorative con CVS e altri strumenti di progetto. Quando si acquisiscono e ci si rende "
+"familiari con queste abilità, contributi come pubblicatori sono "
+"benvenuti."
+
+#: en_US/publishing.xml:21(title)
+msgid "How the Site Works"
+msgstr "Come lavora il Sito"
+
+#: en_US/publishing.xml:22(para)
+msgid ""
+"The <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> "
+"website is a set of PHP files and scripts. Publishers maintain these files "
+"in a CVS repository, and the website host retrieves them hourly to refresh "
+"the site. The host does not automatically use the newest content for the "
+"website. Instead, it pulls files with the CVS tag <systemitem>LIVE</"
+"systemitem> to populate the website."
+msgstr ""
+"Il sito <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem> è una serie di file e script PHP. I pubblicatori mantengono "
+"questi file nei repository CVS e l'host del sito web restituisce loro il sito "
+"aggiornato ogni ora. L'host non usa automaticamente i contenuti per il sito "
+"web più nuovi. Usa file nel CVS targati <systemitem>LIVE</systemitem> per "
+"popolare il sito."
+
+#: en_US/publishing.xml:30(para)
+msgid ""
+"Each publisher sets up a local testing website on an available Fedora "
+"system. This site, sometimes called a <firstterm>sandbox</firstterm>, allows "
+"the publisher to test and view changes to documents, and ensure stability on "
+"the public site."
+msgstr ""
+"Ogni pubblicatore imposta un sito web di test in locale su un sistema Fedora "
+"disponibile. Questo sito, a volte chiamato <firstterm>sandbox</firstterm>, "
+"permette ai pubblicatori di testare e vedere i cambiamenti ai documenti e "
+"di assicurare la stabilità al sito web pubblico."
+
+#: en_US/publishing.xml:37(title)
+msgid "Setting Up a Web Sandbox"
+msgstr "Impostare un Web Sandbox"
+
+#: en_US/publishing.xml:38(para)
+msgid ""
+"To test document publishing, first set up a web sandbox on a local Fedora "
+"system."
+msgstr ""
+"Per testare documenti da pubblicare, innanzitutto impostare un sito web "
+"sandbox su un sistema locale Fedora."
+
+#: en_US/publishing.xml:42(para)
+msgid "Install the \"Web Server\" package group:"
+msgstr "Installare il gruppo di pacchetti \"Web Server\":"
+
+#: en_US/publishing.xml:43(screen)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Web Server\"'"
+msgstr "su -c 'yum groupinstall \"Web Server\"'"
+
+#: en_US/publishing.xml:46(para)
+msgid "Create a folder for the web server to access the site files."
+msgstr "Creare una cartella per l'accesso ai file del sito al web server."
+
+#: en_US/publishing.xml:48(screen)
+#, no-wrap
+msgid "su -c 'mkdir /var/www/fedora'"
+msgstr "su -c 'mkdir /var/www/fedora'"
+
+#: en_US/publishing.xml:51(para)
+msgid ""
+"Change the permissions on this directory to make it easier to access for "
+"your normal user account."
+msgstr ""
+"Cambiare i permessi su questa cartella per permettere un accesso facilitato "
+"all'account degli utenti normali."
+
+#: en_US/publishing.xml:53(replaceable) en_US/publishing.xml:62(replaceable)
+msgid "username"
+msgstr "nome utente"
+
+#: en_US/publishing.xml:53(screen)
+#, no-wrap
+msgid "su -c 'chown <placeholder-1/> /var/www/fedora'"
+msgstr "su -c 'chown <placeholder-1/> /var/www/fedora'"
+
+#: en_US/publishing.xml:56(para)
+msgid "Link to the new directory from your home directory."
+msgstr "Collegare la nuova cartella alla cartella home."
+
+#: en_US/publishing.xml:57(screen)
+#, no-wrap
+msgid "ln -s /var/www/fedora ~/fedora"
+msgstr "ln -s /var/www/fedora ~/fedora"
+
+#: en_US/publishing.xml:60(para)
+msgid "Retrieve the web module from CVS."
+msgstr "Recuperare il modulo web da CVS."
+
+#: en_US/publishing.xml:61(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora\n"
+"cvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+msgstr ""
+"cd ~/fedora\n"
+"cvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+
+#: en_US/publishing.xml:64(title)
+msgid "Web CVS Access"
+msgstr "Accesso Web CVS"
+
+#: en_US/publishing.xml:65(para)
+msgid ""
+"You must have access to the <systemitem>cvsweb</systemitem> module through "
+"the Fedora Account System to check in changes. If you do not have access, "
+"you can use <userinput><![CDATA[:pserver:anonymous]]></userinput> in place "
+"of <userinput><![CDATA[:ext:username]]></userinput> above. Visit the Fedora "
+"Account System at <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> "
+"for more information."
+msgstr ""
+"Si dovrebbe avere accesso al modulo <systemitem>cvsweb</systemitem> "
+"attraverso il Fedora Account System per controllare i cambiamenti. Se non si "
+"ha l'accesso, usare <userinput><![CDATA[:pserver:anonymous]]></userinput> al "
+"posto del seguente <userinput><![CDATA[:ext:username]]></userinput>. Visitare "
+"il Fedora Account System <ulink url=\"http://admin.fedoraproject.org/"
+"accounts/\"/> per maggiori informazioni."
+
+#: en_US/publishing.xml:77(para)
+msgid ""
+"Edit the <filename>/etc/hosts</filename> file and add the following line "
+"<emphasis>after</emphasis> all other lines:"
+msgstr ""
+"Modificare il file <filename>/etc/hosts</filename> e aggiungere la seguente "
+"riga <emphasis>dopo</emphasis> le altre:"
+
+#: en_US/publishing.xml:80(screen)
+#, no-wrap
+msgid "127.0.0.1 docs.localhost.localdomain"
+msgstr "127.0.0.1 docs.localhost.localdomain"
+
+#: en_US/publishing.xml:83(para)
+msgid ""
+"Create a file <filename>/etc/httpd/conf.d/fpo.conf</filename> with the "
+"following content:"
+msgstr ""
+"Creare un file <filename>/etc/httpd/conf.d/fpo.conf</filename> con il "
+"seguente contenuto:"
+
+#: en_US/publishing.xml:97(para)
+msgid ""
+"Create a file <filename>/etc/php.d/fpo.ini</filename> with the following "
+"content:"
+msgstr ""
+"Creare un file <filename>/etc/php.d/fpo.ini</filename> con il seguente "
+"contenuto:"
+
+#: en_US/publishing.xml:99(screen)
+#, no-wrap
+msgid "include_path = \".:/var/www/fedora/web/include\""
+msgstr "include_path = \".:/var/www/fedora/web/include\""
+
+#: en_US/publishing.xml:102(para)
+msgid "Start the web server using the following command:"
+msgstr "Avviare il web server usando il seguente comando:"
+
+#: en_US/publishing.xml:103(screen)
+#, no-wrap
+msgid "su -c '/sbin/service httpd start'"
+msgstr "su -c '/sbin/service httpd start'"
+
+#: en_US/publishing.xml:104(para)
+msgid "To have the web server start at every boot, use the following command:"
+msgstr "Per avere l'avvio del server web ad ogni boot, usare il seguente comando:"
+
+#: en_US/publishing.xml:106(screen)
+#, no-wrap
+msgid "su -c '/sbin/chkconfig httpd on'"
+msgstr "su -c '/sbin/chkconfig httpd on'"
+
+#: en_US/publishing.xml:109(para)
+msgid ""
+"To test the new sandbox site, open a Web browser and point it at the URL "
+"<uri>http://docs.localhost.localdomain</uri>."
+msgstr ""
+"Per testare il nuovo sito sandbox, aprire un broswer web e puntare "
+"all'indirizzo URL <uri>http://docs.localhost.localdomain</uri>."
+
+#: en_US/publishing.xml:113(title)
+msgid "Creating a New Publication"
+msgstr "Creare una Nuova Pubblicazione"
+
+#: en_US/publishing.xml:115(title)
+msgid "General Guidelines"
+msgstr "Linee Guida Generali"
+
+#: en_US/publishing.xml:116(para)
+msgid ""
+"Follow these guidelines to ensure maintainability and ease of use for all "
+"publishers."
+msgstr ""
+"Seguire queste linee guida per assicurare la mantenibilità e la facilità d'uso per tutti i pubblicatori."
+
+#: en_US/publishing.xml:120(para)
+msgid ""
+"Use a short, descriptive name for the document directory. The module name "
+"from its Docs CVS location is usually appropriate. Good examples include "
+"<filename class=\"directory\">install-guide/</filename> or <filename class="
+"\"directory\">example-tutorial/</filename>."
+msgstr ""
+"Usare nomi corti e descrittivi per le cartelle dei documenti. Il nome del "
+"modulo dalla localizzazione Docs CVS solitamente è appropriato. Un buon "
+"esempio <filename class=\"directory\">install-guide/</filename> o <filename "
+"class=\"directory\">example-tutorial/</filename>."
+
+#: en_US/publishing.xml:127(para)
+msgid ""
+"Under the document directory, include a branch directory if the document "
+"references specific features of a particular Fedora release."
+msgstr ""
+"Sotto la cartella del documento, includere una sottocartella se il documento "
+"si riferisce ad una caratteristica di una particolare versione di Fedora."
+
+#: en_US/publishing.xml:132(para)
+msgid ""
+"Under the branch directory (or document directory if no branches are "
+"necessary), make at least a <filename class=\"directory\">en_US/</filename> "
+"directory. Make an additional directory for each locale that has been fully "
+"translated."
+msgstr ""
+"Nella sottocartella (o nella cartella del documento se non sono necessarie "
+"sottocartelle), creare almento una cartella <filename class=\"directory"
+"\">en_US/</filename>. Creare una cartella aggiuntiva per ogni localizzazione "
+"che è stata completamente tradotta."
+
+#: en_US/publishing.xml:141(title)
+msgid "Adding Content"
+msgstr "Contenuti aggiuntivi"
+
+#: en_US/publishing.xml:142(para)
+msgid ""
+"To add content, follow the procedure below. The following commands show an "
+"example of adding content for a new document called the <citetitle>Foobar "
+"Tutorial</citetitle>. This document includes a translation for the \"zz_XX\" "
+"locale and follows specifics of each Fedora release."
+msgstr ""
+"Per aggiungere contenuti, seguire la procedura seguente. I seguenti comandi "
+"mostrano un esempio di aggiunta di contenuti per un nuovo documento chiamato "
+"<citetitle>Foobar Tutorial</citetitle>. Questo documento include una "
+"traduzione locale \"zz_XX\" e segue le specifiche per ogni versione di "
+"Fedora."
+
+#: en_US/publishing.xml:149(para)
+msgid "Make the required directory structure."
+msgstr "Creare la struttura delle cartelle richiesta."
+
+#: en_US/publishing.xml:150(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"mkdir foobar-tutorial\n"
+"mkdir foobar-tutorial/f7\n"
+"mkdir foobar-tutorial/f7/{en_US,zz_XX}"
+msgstr ""
+"cd ~/fedora/web/html/docs/\n"
+"mkdir foobar-tutorial\n"
+"mkdir foobar-tutorial/f7\n"
+"mkdir foobar-tutorial/f7/{en_US,zz_XX}"
+
+#: en_US/publishing.xml:156(para)
+msgid "Build the HTML version of each translation of the document from Docs CVS."
+msgstr "Creare la versione HTML di ogni traduzione del documento da Docs CVS."
+
+#: en_US/publishing.xml:158(replaceable)
+msgid "~/my-docs/foobar-tutorial/F-7/"
+msgstr "~/my-docs/foobar-tutorial/F-7/"
+
+#: en_US/publishing.xml:158(screen)
+#, no-wrap
+msgid ""
+"cd <placeholder-1/>\n"
+"make html-en_US html-zz_XX"
+msgstr ""
+"cd <placeholder-1/>\n"
+"make html-en_US html-zz_XX"
+
+#: en_US/publishing.xml:162(para)
+msgid "Copy the HTML content to the web sandbox."
+msgstr "Copiare il contenuto HTML sul sito web sandbox."
+
+#: en_US/publishing.xml:163(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/foobar-tutorial/f7/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/"
+msgstr ""
+"cd ~/fedora/web/html/docs/foobar-tutorial/f7/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/"
+
+#: en_US/publishing.xml:168(para)
+msgid ""
+"Convert the HTML in each directory to PHP using the provided "
+"<filename>docbookhtml2php.py</filename> script."
+msgstr ""
+"Convertire l'HTML di ogni cartella in PHP usando lo script fornito "
+"<filename>docbookhtml2php.py</filename>."
+
+#: en_US/publishing.xml:177(para)
+msgid ""
+"Create any necessary <filename>index.php</filename> files for the overall "
+"directories. Each document and branch directory must have an <filename>index."
+"php</filename> file directing users to appropriate content. In this example, "
+"the necessary files are <filename>foobar-tutorial/index.php</filename> and "
+"<filename>foobar-tutorial/f7/index.php</filename>. You do not need to write "
+"these files from scratch. Copy an existing file from another document, and "
+"change it as needed to suit the new document."
+msgstr ""
+"Creare i file <filename>index.php</filename> necessari per ogni cartella. "
+"Ogni documento e sotto cartella deve avere un file <filename>index.php</"
+"filename> per orientare gli utenti ai contenuti appropriati. In questo "
+"esempio, i file necessari sono <filename>foobar-tutorial/index.php</"
+"filename> e <filename>foobar-tutorial/f7/index.php</filename>. Non è "
+"necessario scrivere questi file da zero. Copiare un file esistente da un "
+"altro documento e apportare le modifice necessarie al nuovo documento."
+
+#: en_US/publishing.xml:187(para)
+msgid ""
+"Depending on content, publication may include changing a higher-level "
+"<filename>index.php</filename> file."
+msgstr ""
+"In dipendenza dal contenuto, la pubblicazione dovrebbe includere cambiamenti "
+"di alto livello al file <filename>index.php</filename>."
+
+#: en_US/publishing.xml:191(para)
+msgid ""
+"To test the changes in your sandbox, open a web browser and point it at "
+"<uri>http://docs.localhost.localdomain/</uri>."
+msgstr ""
+"Per testare i cambiamenti nel nuovo sito sandbox, aprire un broswer web e puntare "
+"all'indirizzo URL <uri>http://docs.localhost.localdomain</uri>."
+
+#: en_US/publishing.xml:195(title)
+msgid "Always Test Changes"
+msgstr "Controllare Sempre le Modifiche"
+
+#: en_US/publishing.xml:196(para)
+msgid ""
+"<emphasis>Do not proceed further until you test all changes.</emphasis> "
+"Check that all links and index pages work."
+msgstr ""
+"<emphasis>Non procedere oltre fino a che non si sono testati i cambiamenti.</"
+"emphasis> Controllare che tutti i collegamenti e le pagine di indice funzionano."
+
+#: en_US/publishing.xml:204(title)
+msgid "Pushing Content to the Web"
+msgstr "Mettere i Contenuti sul Web"
+
+#: en_US/publishing.xml:205(para)
+msgid "To push your new content to the web site, follow this procedure:"
+msgstr "Per mettere i nuovi contenuti sul sito web, seguire questa procedura:"
+
+#: en_US/publishing.xml:209(para)
+msgid "Add all the new file content to CVS."
+msgstr "Aggiungere tutti i nuovi file al CVS."
+
+#: en_US/publishing.xml:210(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"cvs add foobar-tutorial\n"
+"cd foobar-tutorial\n"
+"cvs add f7\n"
+"cd f7\n"
+"cvs add en_US/ zz_XX/\n"
+"cvs add en_US/*php en_US/stylesheet-images/\n"
+"cvs add zz_XX/*php zz_XX/stylesheet-images/\n"
+"cvs add en_US/stylesheet-images/*png\n"
+"cvs add zz_XX/stylesheet-images/*png\n"
+"cd ../../\n"
+"cvs add foobar-tutorial/index.php\n"
+"cvs add foobar-tutorial/f7/index.php\n"
+msgstr ""
+"cd ~/fedora/web/html/docs/\n"
+"cvs add foobar-tutorial\n"
+"cd foobar-tutorial\n"
+"cvs add f7\n"
+"cd f7\n"
+"cvs add en_US/ zz_XX/\n"
+"cvs add en_US/*php en_US/stylesheet-images/\n"
+"cvs add zz_XX/*php zz_XX/stylesheet-images/\n"
+"cvs add en_US/stylesheet-images/*png\n"
+"cvs add zz_XX/stylesheet-images/*png\n"
+"cd ../../\n"
+"cvs add foobar-tutorial/index.php\n"
+"cvs add foobar-tutorial/f7/index.php\n"
+
+#: en_US/publishing.xml:226(para)
+msgid ""
+"Commit the changes to CVS. Use a message that describes the document being "
+"committed."
+msgstr ""
+"Eseguire il commit dei cambiamenti al CVS. Usare un messaggio che descriva "
+"l'inizio del commit."
+
+#: en_US/publishing.xml:228(replaceable)
+msgid "message about document"
+msgstr "messaggio a proposito del documento"
+
+#: en_US/publishing.xml:228(screen)
+#, no-wrap
+msgid "cvs ci -m '<placeholder-1/>' foobar-tutorial/"
+msgstr "cvs ci -m '<placeholder-1/>' foobar-tutorial/"
+
+#: en_US/publishing.xml:231(para)
+msgid "Tag the content <systemitem>LIVE</systemitem> in CVS."
+msgstr "Targare il contenuto come <systemitem>LIVE</systemitem> nel CVS."
+
+#: en_US/publishing.xml:233(screen)
+#, no-wrap
+msgid "cvs tag -F LIVE foobar-tutorial/"
+msgstr "cvs tag -F LIVE foobar-tutorial/"
+
+#: en_US/vim.xml:13(title)
+msgid "VIM and DocBook"
+msgstr "VIM e DocBook"
+
+#: en_US/vim.xml:16(primary) en_US/vim.xml:33(primary)
+msgid "VIM"
+msgstr "VIM"
+
+#: en_US/vim.xml:19(para)
+msgid ""
+"VIM has many features to help you write XML content such as DocBook, "
+"including syntax highlighting and customizable key bindings. Additionally, "
+"one can easily use external programs from VIM for features such as spell-"
+"checking. This chapter assumes you already know generally how to use VIM; if "
+"you want to learn how, try the <command>vimtutor</command> or by typing "
+"<userinput>:help tutor</userinput> from inside VIM."
+msgstr ""
+"VIM ha alcune caratteristiche che aiutano a scrivere contenuti XML come "
+"DocBook, inclusa la sintassi a colori e un controllo dei tasti personalizzabile. In più si può "
+"utilizzare un programma esterno da VIM per altre caratteristiche come il "
+"controllo delle parole. Questo capitolo presume una buona conoscenza dell'uso "
+"di VIM; per imparare come usare VIM provare "
+"<command>vimtutor</command> o utilizzare <userinput>:help tutor</userinput> "
+"da VIM."
+
+#: en_US/vim.xml:30(title)
+msgid "Setting Up Your <filename>.vimrc</filename> File"
+msgstr "Configurare il file <filename>.vimrc</filename>."
+
+#: en_US/vim.xml:34(secondary) en_US/emacs.xml:44(secondary)
+msgid "configuration file"
+msgstr "file di configurazione"
+
+#: en_US/vim.xml:37(para)
+msgid ""
+"Below is a short sample <filename>.vimrc</filename> file that turns on some "
+"VIM features useful for editing SGML or XML content such as DocBook: "
+"<screen>\n"
+"<computeroutput>\" Turn off vi compatibility settings like limited undo\n"
+"set nocompatible\n"
+"\" Syntax highlighting based on file extension\n"
+"syntax on\n"
+"\" Automatically insert newlines after 80 characters\n"
+"set textwidth=80\n"
+"\" Automatically indent\n"
+"set autoindent\n"
+"\" Match SGML tags with %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+msgstr ""
+"Di seguito un semplice file <filename>.vimrc</filename> di esempio che attiva alcune "
+"caratteristiche di VIM utili per la modifica di contenuti SGML o XML come "
+"DocBook: <screen>\n"
+"<computeroutput>\" disattivare le impostazioni di compatibilità di vi per le "
+"caratterstiche limitate come undo\n"
+"set nocompatible\n"
+"\" Sintassi a colori basata sull'estensione del file\n"
+"syntax on\n"
+"\" Inserimento automatico di nuove righe dopo 80 caratteri\n"
+"set textwidth=80\n"
+"\" Indentazione automatica\n"
+"set autoindent\n"
+"\" Marcare i tag SGML con %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+
+#: en_US/vim.xml:55(para)
+msgid ""
+"Some of these features require the <filename>vim-enhanced</filename> package "
+"to be installed. If you are using or the <filename>vim-minimal</filename> "
+"package, or if you are using an older version of VIM, you may not have the "
+"<filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still "
+"download <ulink url=\"http://vim.org/scripts/script.php?script_id=39"
+"\">matchit.zip from Vim.org</ulink> and load it separately."
+msgstr ""
+"Alcune di queste caratteristiche richiedono che il pacchetto <filename>vim-"
+"enhanced</filename> sia installato. Se si sta usando il pacchetto <filename>vim-"
+"minimal</filename> o una vecchia versione di VIM non bisogna avere <filename>"
+"$VIMRUNTIME/macros/matchit.vim</filename> nel file. Scaricare <ulink url="
+"\"http://vim.org/scripts/script.php?script_id=39\">matchit.zip da Vim.org</"
+"ulink> e caricarlo separatamente."
+
+#: en_US/vim.xml:69(title)
+msgid "Keymapping with VIM"
+msgstr "Keymapping con VIM"
+
+#: en_US/vim.xml:71(para)
+msgid ""
+"VIM can speed up your DocBook creation by mapping frequently typed tags (or "
+"any words or phrases) onto short key combinations. By default, the keymap "
+"leader is the backslash (<literal>\\</literal>), but it can be redefined "
+"with a command like <userinput>let mapleader =\n"
+" \",\"</userinput>. There are two ways to use the following example; "
+"you can put it directly in your <filename>.vimrc</filename>, or you can save "
+"it in a separate file and load it with a <userinput>source</userinput> "
+"command in your <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\n"
+"\" skip ahead to after next tag without leaving insert mode\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\n"
+"\" common tags that start a new text block\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\n"
+"\" common tags that are placed inline\n"
+"\" use <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+"\" entities\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+msgstr ""
+"VIM può velocizzare la creazione del DocBook con una mappatura frequente dei "
+"tipi di tag (oppure ogni parola o frase) in corte combinazioni di tasti. Di "
+"base, il tasto principale è il backslash (<literal>\\</literal>), ma può "
+"essere ridefinito con un comando come <userinput>let mapleader =\n"
+" \",\"</userinput>. Ci sono due modi di usare il seguente esempio; si "
+"può mettere direttamente nel <filename>.vimrc</filename>, o si può salvare "
+"in un file separato e caricato con un comando <userinput>source</"
+"userinput> in <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\n"
+"\" salta avanti al tag successivo senza uscire dalla modalità inserisci\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\n"
+"\" tag comuni che iniziano un nuovo blocco di testo\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\n"
+"\" tag frequenti che si trovano all'interno del testo\n"
+"\" usare <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+"\" entities\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+
+#: en_US/vim.xml:110(para)
+msgid ""
+"Unfortunately, there is not currently a complete macro set for all DocBook "
+"commands, so you will need to define them yourself or customize the "
+"definitions in the examples from <xref linkend=\"sn-vim-additional-resources"
+"\"/>."
+msgstr ""
+"Sfortunatamente non c'è ad oggi una macro completa per impostare tutti i "
+"comandi per DocBook, così bisogna impostarli da soli o personalizzare le "
+"definizioni dall'esempio <xref linkend=\"sn-vim-additional-resources\"/>."
+
+#: en_US/vim.xml:119(title)
+msgid "Additional VIM Resources"
+msgstr "Ulteriori Risorse VIM"
+
+#: en_US/vim.xml:121(para)
+msgid "Additional information about VIM may be found from:"
+msgstr "Ulteriori informazioni su VIM possono essere trovate su:"
+
+#: en_US/vim.xml:127(para)
+msgid ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to "
+"Vi Improved (VIM)</citetitle>"
+msgstr ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> Esempio sgml-vimrc</ulink> dalla <citetitle>Beginner's guide di Vi "
+"Improved (VIM)</citetitle>"
+
+#: en_US/vim.xml:134(para)
+msgid ""
+"The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick "
+"Reference Card</ulink>"
+msgstr ""
+"Il <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick "
+"Reference Card</ulink>"
+
+#: en_US/vim.xml:140(ulink)
+msgid "Vim as XML Editor"
+msgstr "Vim come Editor XML"
+
+#: en_US/vim.xml:145(para)
+msgid ""
+"The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the "
+"<filename>vim-common</filename> package —<filename>/usr/share/vim/"
+"<replaceable><version></replaceable>/doc/intro.txt</filename> or type "
+"<userinput>:help intro</userinput> from within VIM"
+msgstr ""
+"Il <citetitle>VIM REFERENCE MANUAL</citetitle>, che è assieme al pacchetto "
+"<filename>vim-common</filename> package —<filename>/usr/share/vim/"
+"<replaceable><version></replaceable>/doc/intro.txt</filename> oppure digitare "
+"<userinput>:help intro</userinput> da VIM"
+
+#: en_US/tutorial.xml:13(title)
+msgid "The Layout of a Tutorial"
+msgstr "La Struttura di un Tutorial"
+
+#: en_US/tutorial.xml:14(para)
+msgid ""
+"In this chapter, you will find an example of a very short tutorial as used "
+"by the Fedora Documentation Project. This example is specific to the way the "
+"Docs Project uses DocBook XML. The example consists of a set of files used "
+"to hold the content and metadata for the tutorial."
+msgstr ""
+"In questo capitolo si può trovare un esempio di un piccolo tutorial usato "
+"dal Fedora Documentation Project. Questo esempio è specifico per il modo in cui il progetto "
+"Docs usa i DocBook XML. L'esempio consiste in una serie di file usati per "
+"mantenere contenuti e metadata per il tutorial."
+
+#: en_US/tutorial.xml:19(title)
+msgid "The Article"
+msgstr "L'Articolo"
+
+#: en_US/tutorial.xml:21(primary) en_US/tutorial.xml:56(primary)
+msgid "tutorial layout"
+msgstr "struttura tutorial"
+
+#: en_US/tutorial.xml:22(secondary)
+msgid "article"
+msgstr "articolo"
+
+#: en_US/tutorial.xml:24(para)
+msgid "Below is a sample article:"
+msgstr "Di seguito un esempio di articolo:"
+
+#: en_US/tutorial.xml:54(title)
+msgid "The Metadata"
+msgstr "I Metadata"
+
+#: en_US/tutorial.xml:57(secondary)
+msgid "metadata"
+msgstr "metadata"
+
+#: en_US/tutorial.xml:59(para)
+msgid ""
+"The <filename>rpm-info.xml</filename> file contains all the required "
+"metadata for the document. This metadata includes title, authorship, "
+"licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates "
+"the content of this file:"
+msgstr ""
+"Il file <filename>rpm-info.xml</filename> contiene tutti i metadata "
+"richiesti per i documenti. Questo metadata include titolo, autore, licenza "
+"e cronologia revisione. <xref linkend=\"ex-rpminfo\"/> illustra i "
+"contenuti del file:"
+
+#: en_US/tutorial.xml:65(title)
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr "File Esempio<filename>rpm-info.xml</filename>"
+
+#: en_US/tutorial.xml:95(para)
+msgid ""
+"If you are not familiar with XML editing, copy and paste this file from an "
+"existing module and then edit the values for the various elements as "
+"appropriate. Consult Fedora Documentation Project members and help channels "
+"for more assistance if needed."
+msgstr ""
+"Se non si è familiari con la modifica di XML, copiare e incollare questo file da "
+"un modulo esistente e poi modificare appropriatamente i valori dei vari "
+"elementi. Se necessario consultare i membri del Fedora Documentation Project e i canali di "
+"aiuto per maggiore assistenza."
+
+#: en_US/style.xml:14(title)
+msgid "Style"
+msgstr "Stile"
+
+#: en_US/style.xml:16(para)
+msgid ""
+"Writing good technical documentation is not simply reproducing command lines "
+"and instruction sets. Good documentation is easy to read, understand, and "
+"translate, and presents a concise logical progression of concepts. Good "
+"documentation can also be defined by what it does <emphasis>not</emphasis> "
+"contain. Your tutorial should avoid:"
+msgstr ""
+"Scrivere buona documentazione tecnica non è una semplice riproduzione di "
+"comandi e istruzioni. Una buona documentazione è facile da leggere, capire, "
+"tradurre e presenta una progressione logica e concisa di concetti. Una buona "
+"documentazione può essere definita anche da cosa <emphasis>non</emphasis> "
+"contiene. Il tutorial dovrebbe evitare:"
+
+#: en_US/style.xml:26(para)
+msgid "Excessive wordiness"
+msgstr "Ecessive parole"
+
+#: en_US/style.xml:31(para)
+msgid "Unnecessary or undefined jargon"
+msgstr "Dialettismi non necessari e indefiniti"
+
+#: en_US/style.xml:36(para)
+msgid "Grammatical or spelling errors"
+msgstr "Errori di grammatica o scrittura"
+
+#: en_US/style.xml:41(para)
+msgid "References to yourself or your experiences"
+msgstr "Referenze a se stessi o alla propria esperienza"
+
+#: en_US/style.xml:46(para)
+msgid "Remarks which might offend or confuse any reader"
+msgstr "Rimarcare cose che possono offendere o confondere i lettori"
+
+#: en_US/style.xml:51(para)
+msgid ""
+"This chapter contains style rules and guidelines for writing Fedora "
+"documentation. Guidelines are not the same as rules. It is acceptable to "
+"violate a guideline when it makes your material easier to understand. Follow "
+"guidelines whenever possible, but follow rules at all times. Assume any "
+"advice is a guideline unless identified otherwise."
+msgstr ""
+"Questo capitolo contiene regole di stile e linee guida per scrivere "
+"documentazione Fedora. Le linee guida non sono regole. E' accettabile "
+"violare una linea guida per rendere il proprio materiale piu facile da capire. "
+"Seguire le linee guida quando possibile ma seguire sempre le regole. "
+"Assumere ogni avvertimento come linea guida se non diversamente specificato."
+
+#: en_US/style.xml:62(title)
+msgid "Why Style Is Important"
+msgstr "Perchè lo Stile è importante"
+
+#: en_US/style.xml:64(para)
+msgid ""
+"Writing well comes naturally to almost no one. It is a skill that "
+"professional writers, even famous ones, must practice constantly. "
+"<firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> "
+"is the quality that separates elegant writing from the merely functional."
+msgstr ""
+"Scrivere bene non risulta naturale quasi a nessuno. E' una abilità che gli "
+"scrittori professionisti, anche famosi, devono esercitare costantemente. "
+"<firstterm>Stile</firstterm><indexterm><primary>stile</primary></indexterm> "
+"è la qualità che distingue la scrittura elegante da quella puramente "
+"funzionale."
+
+#: en_US/style.xml:77(para)
+msgid ""
+"For example, refer to. <ulink url=\"http://www.online-literature.com/"
+"james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/"
+"ulysses/18/</ulink>. Please note that this example contains some mature "
+"themes and language, and is not suitable for all readers."
+msgstr ""
+"Per esempio, fare riferimento a <ulink url=\"http://www.online-literature."
+"com/james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/"
+"ulysses/18/</ulink>. Notare che questo esempio contiene alcuni temi e "
+"linguaggi maturi e non è accessibile a tutti i lettori."
+
+#: en_US/style.xml:71(para)
+msgid ""
+"Elegance comes in many forms. In prose and poetry, elegant writing may not "
+"follow some (or any) common rules of grammar, syntax, or spelling. A good "
+"example is Episode 18, \"Penelope,\" in James Joyce's novel "
+"<citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long "
+"streams of words without punctuation to simulate a character's internal "
+"consciousness. By violating basic rules of grammar and syntax, Joyce "
+"simulates the disorganized but loosely connected thought patterns of the "
+"narrator."
+msgstr ""
+"L'eleganza arriva in molte forme. In prosa e poesia, una scrittura elegante "
+"può non seguire alcune regole grammaticali e sintattiche. Un buon esempio è "
+"l'Episodio 18, \"Penelope,\" di James Joyce's nell'<citetitle>Ulisse</"
+"citetitle><placeholder-1/>. Qui, Joyce usa una lunga serie di parole senza "
+"punteggiatura per simulare il flusso di coscienza. Violando le regole basilari "
+"della grammatica e della sintassi, Joyce simula la disorganizzazione ma "
+"perde la connessione dello stile della narrazione."
+
+#: en_US/style.xml:89(para)
+msgid ""
+"Technical documentation, however, should always respect these rules. The "
+"more a document departs from standard language usage, the more difficult the "
+"material becomes for the reader. For example, readers may not be native "
+"speakers of the language used, or they might be reading a translation. If "
+"the writer uses slang, idioms, or jargon, a reader or translator may easily "
+"become confused. The following example compares two different written "
+"executions of the same idea:"
+msgstr ""
+"La documentazione tecnica, comunque, dovrebbe seguire e rispettare sempre "
+"queste regole. Più un documento si stacca dagli standard della lingua usata, "
+"più il materiale diventa difficile per il lettore. Per esempio, i lettori "
+"possono non essere madrelingua del linguaggio usato o potrebbero leggere una "
+"traduzione. Se gli scrittori usano dialetto, idiomi o gerghi, un lettore o "
+"un traduttore può facilmente confondersi. Il seguente esempio compara due "
+"differenti scritture della stessa idea:"
+
+#: en_US/style.xml:100(title)
+msgid "Incorrect style"
+msgstr "Stile non corretto"
+
+#. I prefer "incorrect," because I think terms such as
+#. "problematic" are mealy-mouthed. They remind me of the late
+#. 1980's English textbook trend toward the politically correct yet
+#. wholly unhelpful "standard/nonstandard." But then, I tend to be
+#. dogmatic; it's probably my Catholic upbringing. [PWF]
+#: en_US/style.xml:108(para)
+msgid ""
+"So you made the changes I showed you in the last section. What's the next "
+"thing you should do? Just pop your thumb drive onto your system and read the "
+"<filename>messages</filename> log. When you see \"USB device found,\" then "
+"Bob's your uncle."
+msgstr ""
+"Così sono stati fatti i cambiamenti mostrati nell'ultima sezione. Cos'è la "
+"prossima cosa che si dovrebbe fare? Inserire la memoria di massa nel sistema "
+"e leggere i <filename>messaggi</filename> di log. Quando si legge \"USB "
+"device found,\" si è a cavallo."
+
+#: en_US/style.xml:116(title)
+msgid "Correct style"
+msgstr "Stile Corretto"
+
+#. I prefer "correct." See above. [PWF]
+#: en_US/style.xml:120(para)
+msgid ""
+"After you complete the configuration changes above, attach the USB removable "
+"media to your system. Use the <command>dmesg</command> command to examine "
+"the kernel message log. The message <computeroutput>USB device\n"
+"\t found</computeroutput> indicates that your device was installed "
+"successfully."
+msgstr ""
+"Dopo aver completato le seguenti modifiche alla configurazione, collegare "
+"al sistema il disco rimovibile USB. Usare il comando <command>dmesg</"
+"command> per esaminare i messaggi log del kernel. Il messaggio "
+"<computeroutput>USB device\n"
+"\t found</computeroutput> indica che il dispositivo è stato installato "
+"correttamente."
+
+#: en_US/style.xml:129(para)
+msgid ""
+"The first example is more conversational English, which is not appropriate "
+"for official written documentation. The second example is more formal, but "
+"as a result it is easier to comprehend, both for native readers and "
+"translators."
+msgstr ""
+"Il primo esempio ha un linguaggio più confidenziale, non è appropriato per "
+"la scrittura di un documento ufficiale. Il secondo esempio è più formale ma "
+"risulta più semplice nella comprensione, sia per i lettori della lingua "
+"madre sia per i traduttori."
+
+#: en_US/style.xml:135(para)
+msgid ""
+"Following style rules and guidelines also makes readers more comfortable "
+"with a set of documents. Consistent style enhances the professional "
+"appearance of documentation, and its perceived value. On the other hand, "
+"lapses in punctuation or poor grammar negatively affect a reader's reaction "
+"to written material. A reader can feel that an otherwise correct technical "
+"document is lacking in authority, simply because it is poorly written. "
+"Readers feel at ease when they do not have to struggle to understand an "
+"author's use of language."
+msgstr ""
+"Seguire le regole di stile e le linee guida permette ai lettori di avere più "
+"familiarità con una serie di documenti. Uno stile ordinato dà "
+"professionalità e maggior valore al documento. Dall'altra parte, la mancanza "
+"di punteggiatura o di grammatica influenzano negativamente la reazione del "
+"lettore al materiale scritto. Un lettore può sentire che un documento tecnico"
+" poco corretto possa perdere di autorità, semplicemente perchè è "
+"scritto in maniera povera. I lettori si sentono rilassati quando non devono "
+"sforzarsi a capire il linguaggio usato dall'autore."
+
+#: en_US/style.xml:146(para)
+msgid ""
+"This chapter cannot possibly cover enough material to make every reader a "
+"good writer. Some manuals devoted entirely to writing style are themselves "
+"hundreds of pages long. This chapter provides enough guidelines for "
+"intermediate writers to understand style usage in technical documentation."
+msgstr ""
+"Questo capitolo non copre abbastanza materiale per rendere ogni lettore un "
+"ottimo scrittore. Alcuni manuali dedicati interamente allo stile di "
+"scrittura sono lunghi centinaia di pagine. Questo capitolo offre alcune "
+"linee guida sufficienti per far capire ad uno scrittore intermedio lo stile "
+"usato nella documentazione tecnica."
+
+#: en_US/style.xml:153(para)
+msgid ""
+"If you are not a practiced writer, whether of technical documentation or "
+"otherwise, you may benefit from other style resources. The following list is "
+"far from comprehensive, but provides a starting point:"
+msgstr ""
+"Se non si ha pratica con la scrittura di documentazione tecnica o altro, si "
+"può beneficiare delle risorse di altri stili. La lista seguente è lontana "
+"dall'essere comprensiva ma offre un punto di partenza:"
+
+#: en_US/style.xml:161(para)
+msgid ""
+"<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules "
+"and links to online versions can be found at: <ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>"
+msgstr ""
+"<citetitle>The Elements of Style</citetitle>, di William Strunk. Regole basi "
+"e collegamenti alla versione online possono essere trovati a questo "
+"indirizzo: <ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style"
+"\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+
+#: en_US/style.xml:176(para)
+msgid ""
+"<citetitle>The Chicago Manual of Style</citetitle>, by the University of "
+"Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle."
+"org/\">http://www.chicagomanualofstyle.org/</ulink>"
+msgstr ""
+"<citetitle>The Chicago Manual of Style</citetitle>, dalla University of "
+"Chicago Press. Versione online: <ulink url=\"http://www.chicagomanualofstyle."
+"org/\">http://www.chicagomanualofstyle.org/</ulink>"
+
+#: en_US/style.xml:183(para)
+msgid ""
+"<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by "
+"Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/"
+"\">http://www.powa.org/</ulink>"
+msgstr ""
+"<citetitle>Paradigm Online Writing Assistant</citetitle>, mantenuto da Chuck "
+"Guilford, Ph.D. Solo online: <ulink url=\"http://www.powa.org/\">http://www."
+"powa.org/</ulink>"
+
+#: en_US/style.xml:190(para)
+msgid ""
+"There are many free software documentation projects which have developed "
+"their own style guidelines. This chapter, in fact, draws heavily on the "
+"<citetitle>GNOME Documentation Style Guidelines</citetitle> "
+"(<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</"
+"citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/"
+"\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr ""
+"Ci sono alcuni progetti di documentazione di software libero che hanno "
+"sviluppato le proprie linee guida. Questo capitolo, infatti, è preso dal "
+"<citetitle>GNOME Documentation Style Guidelines</citetitle> "
+"(<firstterm>GDSG</firstterm>). Si può leggere l'originale <citetitle>GDSG</"
+"citetitle> a questo indirizzo <ulink url=\"http://developer.gnome.org/"
+"documents/style-guide/\">http://developer.gnome.org/documents/style-guide/</"
+"ulink>."
+
+#: en_US/style.xml:203(title)
+msgid "Fundamental Concepts of Technical Documentation"
+msgstr "Concetti Fondamentali della Documentazione Tecnica"
+
+#: en_US/style.xml:206(title)
+msgid "Bibliographic Information"
+msgstr "Informazioni Bibliografiche"
+
+#: en_US/style.xml:207(para)
+msgid "This section is drawn primarily from the <citetitle>GDSG</citetitle>."
+msgstr "Questa sezione è presa principalmente da <citetitle>GDSG</citetitle>."
+
+#. This section will reproduce mostly what is in Chapter 1 of
+#. the GDSG. There may be minor changes. FIXME: Make sure the
+#. appropriate front matter of the Documentation Guide includes
+#. attribution as required by the GNU FDL.
+#: en_US/style.xml:218(para)
+msgid ""
+"This chapter provides a brief introduction to writing technical "
+"documentation."
+msgstr ""
+"Questo capitolo offre una breve introduzione alla scrittura della "
+"documentazione tecnica."
+
+#: en_US/style.xml:224(title)
+msgid "General Style Requirements"
+msgstr "Requisiti di Stile Generali"
+
+#: en_US/style.xml:225(para)
+msgid ""
+"Technical writing for the Fedora Project imposes special constraints beyond "
+"the basic requirements of good prose. Good Fedora technical documentation "
+"has the following characteristics:"
+msgstr ""
+"Le scritture tecniche per il Fedora Project impongono delle restrizioni "
+"speciali lontane da quelle basi richieste per la buona prosa. La buona "
+"documentazione tecnica per Fedora ha le seguenti caratteristiche:"
+
+#: en_US/style.xml:232(term)
+msgid "Comprehensive"
+msgstr "Comprensiva"
+
+#: en_US/style.xml:234(para)
+msgid ""
+"Describe all of the functionality of a product. Do not omit functionality "
+"that you regard as irrelevant for the user."
+msgstr ""
+"Descrive tutto il funzionamento del prodotto. Non omette funzionalità che "
+"sono considerate irrilevanti per gli utenti."
+
+#: en_US/style.xml:242(term)
+msgid "Conforming"
+msgstr "Conforme"
+
+#: en_US/style.xml:249(para)
+msgid ""
+"Describe what you see. Do not describe what you want to see. Present your "
+"information in the order that users experience the subject matter."
+msgstr ""
+"Descrive cosa si vede. Non descrive cosa si vuole vedere. Presenta "
+"l'informazione in ordine d'esperienza dell'utente."
+
+#: en_US/style.xml:257(term)
+msgid "Clear"
+msgstr "Chiara"
+
+#: en_US/style.xml:259(para)
+msgid ""
+"Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>) to help make your writing clear."
+msgstr ""
+"Leggere <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>) per aiutarsi in una scrittura chiara."
+
+#: en_US/style.xml:275(term)
+msgid "Consistent"
+msgstr "Consistente"
+
+#: en_US/style.xml:277(para)
+msgid ""
+"Use agreed vocabulary throughout your documentation. Use the same vocabulary "
+"as other writers who are working on related documentation."
+msgstr ""
+"Usare lo stesso vocabolario in tutta la documentazione. Usare lo stesso "
+"vocabolario adottato da altri scrittori che lavorano a documenti correlati."
+
+#: en_US/style.xml:285(term)
+msgid "Concise"
+msgstr "Concisa"
+
+#: en_US/style.xml:287(para)
+msgid ""
+"Review your work frequently as you write your document. Ask yourself which "
+"words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for "
+"specific guidelines."
+msgstr ""
+"Rivedere il proprio lavoro frequentemente durante la scrittura del documento."
+" Chiedersi quali parole usare. Fare riferimento a <xref linkend=\"sn-fundamentals-2\"/>"
+" per le linee guida specifiche."
+
+#: en_US/style.xml:297(title)
+msgid "Golden Rules"
+msgstr "Regole d'oro"
+
+#: en_US/style.xml:298(para)
+msgid ""
+"This section contains some basic style guidelines. Subsequent sections in "
+"this chapter expand on these guidelines to give more detailed guidance."
+msgstr ""
+"Questa sezione contiene alcune linee guida di base per lo stile. Le sottosezioni "
+"di questo capitolo approfondiscono queste linee guida per dare ulteriori "
+"dettagli."
+
+#: en_US/style.xml:305(term)
+msgid "Golden Rule 1: Be brief"
+msgstr "Regola d'oro 1: Essere brevi"
+
+#: en_US/style.xml:309(para)
+msgid "Limit each sentence to fewer than 25 words."
+msgstr "Limitare ogni frase a meno di 25 parole."
+
+#: en_US/style.xml:314(para)
+msgid "Limit each procedure step to 23 words."
+msgstr "Lomitare ogni procedura a 23 parole."
+
+#: en_US/style.xml:320(title)
+msgid "Incorrect: Too long"
+msgstr "Non corretta: Troppo lungha"
+
+#: en_US/style.xml:321(para)
+msgid ""
+"Under normal operating conditions, the kernel does not always immediately "
+"write file data to the disks, storing it in a memory buffer and then "
+"periodically writing to the disks to speed up operations."
+msgstr ""
+"Nelle condizioni normali di operatività, il kernel non sempre scrive immediatamente "
+"le informazioni sul disco, le immagazzina in una memoria buffer e "
+"periodicamente scrive sul disco per velocizzare le operazioni."
+
+#: en_US/style.xml:328(title)
+msgid "Correct: Less wordy"
+msgstr "Corretto: Meno parole"
+
+#: en_US/style.xml:329(para)
+msgid ""
+"Normally, the kernel stores the data in memory prior to periodically writing "
+"the data to the disk."
+msgstr ""
+"Normalmente, il kernel immagazzina le informazioni nella memoria principale "
+"e periodicamente le scrive sul disco."
+
+#: en_US/style.xml:337(term)
+msgid "Golden Rule 2: Be organized"
+msgstr "Regole d'oro 2: Essere organizzati"
+
+#: en_US/style.xml:341(para)
+msgid "Limit each paragraph to one topic."
+msgstr "Limitare ogni paragrafo ad un argomento."
+
+#: en_US/style.xml:346(para)
+msgid "Limit each sentence to one idea."
+msgstr "Limitare ogni frase ad una idea."
+
+#: en_US/style.xml:351(para)
+msgid "Limit each procedure step to one action."
+msgstr "Lomitare ogni procedura ad una azione."
+
+#: en_US/style.xml:357(title)
+msgid "Incorrect: Disorganized topics"
+msgstr "Non corretta: Argomenti disorganizzati"
+
+#: en_US/style.xml:358(para)
+msgid ""
+"The <application>Workspace Switcher</application> applet helps you navigate "
+"all of the virtual desktops available on your system. The X Window system, "
+"working in hand with a piece of software called a <emphasis>window manager</"
+"emphasis>, allows you to create more than one virtual desktop, known as "
+"<emphasis>workspaces</emphasis>, to organize your work, with different "
+"applications running in each workspace. The <application>Workspace Switcher</"
+"application> applet is a navigational tool to get around the various "
+"workspaces, providing a miniature road map in the GNOME panel showing all "
+"your workspaces and allowing you to switch easily between them."
+msgstr ""
+"L'applet <application>Selettore area di lavoro</application> aiuta a navigare sui "
+"desktop virtuali presenti sul sistema. Il sistema X Window, lavora con un "
+"pezzo di software chiamato <emphasis>window manager</emphasis>, esso "
+"permette di creare più desktop virtuali, chiamate <emphasis>aree di lavoro</emphasis>"
+", per organizzare il proprio lavoro, con differenti applicazioni lanciate in ogni area di lavoro. L'appelt "
+"<application>Selettore area di lavoro</application> è uno strumento di navigazione "
+"per muoversi tra le varie aree di lavoro, offre delle miniature nel pannello di "
+"GNOME che mostrano le aree di lavoro e ne permette la navigazione tra di "
+"esse."
+
+#: en_US/style.xml:375(title)
+msgid "Correct: Organized topics"
+msgstr "Corretto: Argomenti organizzati"
+
+#: en_US/style.xml:376(para)
+msgid ""
+"Use the <application>Workspace Switcher</application> to add new "
+"<emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different "
+"applications in each workspace. The <application>Workspace Switcher</"
+"application> applet provides a miniature map that shows all of your "
+"workspaces. You can use the <application>Workspace Switcher</application> "
+"applet to switch between workspaces."
+msgstr ""
+"Usare il <application>Selettore area di lavoro</application> per aggiungere nuove "
+"<emphasis>aree di lavoro (workspaces)</emphasis> al Desktop GNOME. Si "
+"possono avviare differenti applicazioni in ogni area di lavoro. L'applet "
+"<application>Selettore area di lavoro</application> offre delle miniature per "
+"mostrare tutte le aree di lavoro. Si può usare l'applet <application>Selettore area"
+" di lavoro</application> per muoversi tra le varie aree di lavoro."
+
+#: en_US/style.xml:388(para)
+msgid ""
+"Plan the order of paragraphs before you start writing. Decide which topic "
+"you want to cover in each paragraph."
+msgstr ""
+"Pianificare l'ordine dei paragrafi prima di iniziare a scrivere. Decidere "
+"quali argomenti trattare in ogni paragrafo."
+
+#: en_US/style.xml:396(term)
+msgid "Golden Rule 3: Be demonstrative"
+msgstr "Regole d'oro 3: Essere dimostrativi"
+
+#: en_US/style.xml:398(para)
+msgid ""
+"Use explicit examples to demonstrate how an application works. Provide "
+"instructions rather than descriptions."
+msgstr ""
+"Usare esempi specifici per dimostrare come funziona una applicazione. Fornire "
+"istruzioni piuttosto che descrizioni."
+
+#: en_US/style.xml:403(title)
+msgid "Incorrect: Describes but does not demonstrate"
+msgstr "Non corretto: Descrivere ma non dimostrare"
+
+#: en_US/style.xml:405(para)
+msgid "There is a text box that you can use to find out the definition of a word."
+msgstr "C'è un campo testo che si può usare per trovare la definizione di una parola."
+
+#: en_US/style.xml:411(title)
+msgid "Correct: Demonstrates usage"
+msgstr "Corretto: Dimostrare l'uso"
+
+#: en_US/style.xml:412(para)
+msgid ""
+"To request a definition of a word, type the word in the text box, then "
+"select <guilabel>Lookup</guilabel>."
+msgstr ""
+"Per richiedere la definizione di una parola, scrivere la parola nel campo "
+"testo, poi selezionare <guilabel>Trova</guilabel>."
+
+#: en_US/style.xml:418(para)
+msgid ""
+"Do not apply this guideline too rigidly. Sometimes you must explain how "
+"software works to support your how-to examples."
+msgstr ""
+"Non applicare queste linee guida troppo rigidamente. A volte bisogna "
+"spiegare come lavora un software negli esempi del proprio how-to."
+
+#: en_US/style.xml:427(term)
+msgid "Golden Rule 4: Be objective"
+msgstr "Regola d'oro 4: Essere obiettivi"
+
+#: en_US/style.xml:429(para)
+msgid "Write in a neutral tone."
+msgstr "Usare un tono neutrale."
+
+#: en_US/style.xml:433(title)
+msgid "Incorrect: Sentence takes sides"
+msgstr "Non corretto: Esprimere propri giudizi"
+
+#: en_US/style.xml:434(para)
+msgid "The applet is a handy little screen grabber."
+msgstr "L'applicazione è un piccolo cattura schermata maneggevole."
+
+#: en_US/style.xml:439(title)
+msgid "Correct: Sentence is objective"
+msgstr "Corretto: Giudizio obiettivo"
+
+#: en_US/style.xml:440(para)
+msgid "Use the applet to take screenshots."
+msgstr "Usare l'applet per fare uno screenshot."
+
+#: en_US/style.xml:452(title)
+msgid "Tone"
+msgstr "Tono"
+
+#: en_US/style.xml:453(para)
+msgid ""
+"Inappropriate tone hinders reader access to information. A neutral tone free "
+"of opinion or personal flavor improves the reader's comprehension. Neutral "
+"tone helps writers to work in parallel on a large technical documentation "
+"project. Furthermore, additional writers may join the project at any time. "
+"Use of a neutral tone helps to achieve consistency across a documentation "
+"set, and thereby facilitates user access to information. The best way to "
+"achieve a common, neutral tone is to apply the following principles:"
+msgstr ""
+"Un tono inappropriato blocca l'accesso all'informazione ai lettori. Un tono "
+"neutrale, privo di opinioni e sentimenti personali, migliora la "
+"comprensione del lettore. Un tono neutrale aiuta gli scrittori a lavorare in "
+"parallelo su un grande progetto di documentazione tecnica. In più, altri "
+"scrittori possono partecipare al progetto in ogni momento. Usare un tono "
+"neutrale aiuta a mantenere coerenza tra una serie di documenti e aiuta gli "
+"utenti nell'accesso all'informazione. Il modo migliore per mantenere un tono "
+"neutrale e familiare è applicare i seguenti principi:"
+
+#: en_US/style.xml:466(term)
+msgid "Avoid humor"
+msgstr "Evitare l'humor"
+
+#: en_US/style.xml:468(para)
+msgid ""
+"Humor distracts from the information you are trying to provide. Humor also "
+"makes documentation difficult to translate. Stay factual."
+msgstr ""
+"L'umorismo distrae dalle informazioni che si vogliono fornire. L'umorismo inoltre "
+"rende la documentazione difficile da tradurre. Rimanere realisti."
+
+#: en_US/style.xml:476(term)
+msgid "Avoid personal opinions"
+msgstr "Evitare opinioni personali"
+
+#: en_US/style.xml:478(para)
+msgid ""
+"Whether you think a function is useful or woeful is irrelevant. Report the "
+"function to the user, with instructions about how to use the function. Stay "
+"accurate."
+msgstr ""
+"Se si pensa che una funzione sia utile o no è irrilevante. Riportare le "
+"funzioni agli utenti, con le istruzioni su come usare la funzione. Restare "
+"accurati."
+
+#: en_US/style.xml:487(term)
+msgid "Avoid colloquial language"
+msgstr "Evitare un linguaggio colloquiale"
+
+#: en_US/style.xml:489(para)
+msgid ""
+"Colloquial language is difficult to translate and usually culture-specific. "
+"Stay neutral."
+msgstr ""
+"Un linguaggio colloquiale è difficile da tradurre e solitamente è specifico "
+"per una cultura. Restare neutrali."
+
+#: en_US/style.xml:496(term)
+msgid "Avoid topical expressions"
+msgstr "Evitare espressioni comuni"
+
+#: en_US/style.xml:498(para)
+msgid ""
+"An expression that is in common use today might convey something completely "
+"different tomorrow. Stay technical."
+msgstr ""
+"Una espressione che è usata comunemente oggi potrebbe non essere più "
+"convenzionale un domani. Rimanere sul tecnico."
+
+#: en_US/style.xml:505(term)
+msgid "Avoid aspirational statements"
+msgstr "Evitare affermazioni sul futuro"
+
+#: en_US/style.xml:507(para)
+msgid ""
+"Statements about the future developments of a product do not belong in "
+"technical documentation. Write about what you see right now. Stay real."
+msgstr ""
+"Affermazioni sullo sviluppo futuro di un prodotto non dovrebbero esserci "
+"nella documentazione tecnica. Scrivere cosa si vede ora. Rimanere realisti."
+
+#: en_US/style.xml:517(title)
+msgid "Reaching the Right Audience"
+msgstr "Muoversi verso il giusto pubblico"
+
+#: en_US/style.xml:518(para)
+msgid ""
+"All of the decisions that you make about the structure and content of a "
+"manual follow from an understanding of the audience. Consider how the "
+"audience accesses the documentation, what sort of information the audience "
+"needs, and the experience level of the audience. Usually, you need to create "
+"documentation that is suitable for different audiences. The following "
+"sections introduce some of the audience-related topics you need to consider."
+msgstr ""
+"Tutte le decisioni sulla struttura e i contenuti del manuale seguono la "
+"comprensione del pubblico. Considerare come i lettori accedono alla "
+"documentazione, di che tipo di informazioni hanno bisogno e il livello di "
+"esperienza. Di solito c'è la necessità di creare documentazione che sia "
+"accessibile ad un pubblico differente. La seguente sezione introduce alcuni "
+"argomenti da tenere in considerazione in relazione al pubblico."
+
+#: en_US/style.xml:530(title)
+msgid "User Motivation"
+msgstr "Motivazione dell'utente"
+
+#: en_US/style.xml:531(para)
+msgid ""
+"Do not waste the time of the user who looks for information in your "
+"documentation. Users do not read technical documentation for entertainment. "
+"Users usually have specific questions. You need to give clear answers to "
+"those questions."
+msgstr ""
+"Non far perdere tempo all'utente che cerca informazioni nella "
+"documentazione. Gli utenti non leggono la documentazione tecnica per "
+"intrattenimento. Gli utenti di solito hanno una specifica richiesta. Bisogna "
+"dare risposte chiare alle domande."
+
+#: en_US/style.xml:539(title)
+msgid "New Users"
+msgstr "Nuovi Utenti"
+
+#: en_US/style.xml:540(para)
+msgid ""
+"New users to Fedora are likely to consult online tutorials for guidance "
+"about unfamiliar applications or functionality. Each tutorial should contain "
+"enough introductory information to tell new users how to start using the "
+"relevant functions. Each tutorial should also contain enough usage "
+"instructions to tell users the different actions that they can perform with "
+"the command or function. Keep these instructions task-oriented. Do not "
+"describe GUI screens, dialogs, and dialog elements in a tutorial, unless "
+"there is an unusual feature that affects your instructions."
+msgstr ""
+"I nuovi utenti di Fedora sono contenti di consultare guide online sulle "
+"applicazioni e funzioni non familiari. Ogni tutorial dovrebbe contenere "
+"delle informazioni introduttive per spiegare ai nuovi utenti come iniziare "
+"ad usare le funzioni più importanti. Ogni guida dovrebbe anche contenere "
+"sufficienti informazioni introduttive per spiegare agli utenti le differenti azioni che "
+"possono compiere con il comando o la funzione. Mantenere queste istruzioni raggruppate "
+"per argomento. Non descrivere le interfaccie grafiche (GUI), i messaggi, "
+"e gli elementi di dialogo nel tutorial, a meno che non sia indispensabile "
+"per le istruzioni."
+
+#: en_US/style.xml:554(title)
+msgid "Experienced Users"
+msgstr "Utenti Avanzati"
+
+#: en_US/style.xml:555(para)
+msgid ""
+"Experienced users are more likely to use documentation as a reference. The "
+"documentation therefore needs to be complete, well-organized, and in the "
+"case of printed manuals, well-indexed."
+msgstr ""
+"Gli utenti avanzati preferiscono usare la documentazione come riferimento. "
+"La documentazione necessita di essere completa, ben organizzata e, in caso "
+"di stampa, indicizzata."
+
+#: en_US/style.xml:563(title)
+msgid "Do Not Offend Your Audience"
+msgstr "Non offendere i lettori"
+
+#: en_US/style.xml:564(para)
+msgid ""
+"To avoid offending your readers, apply the following guidelines to your "
+"documentation:"
+msgstr ""
+"Per evitare di offendere i lettori, usare le seguenti linee guida per la "
+"documentazione:"
+
+#: en_US/style.xml:570(term)
+msgid "Avoid insider language"
+msgstr "Evitare un linguaggio specialistico"
+
+#: en_US/style.xml:572(para)
+msgid ""
+"Insider language includes both undefined jargon and the tendency of the "
+"computer community to shorten words. For example, use the term "
+"<literal>documentation</literal> instead of the term <literal>docs</"
+"literal>. A term may be jargon if it fails all the following conditions:"
+msgstr ""
+"Un linguaggio specialistico include sia dialetti indefiniti e sia la "
+"tendenza ad accorciare le parole. Per esempio, usare il termine "
+"<literal>documentazione</literal> invece di <literal>docs</literal>. Un "
+"termine può essere dialettale se cade nelle seguenti condizioni:"
+
+#: en_US/style.xml:581(para)
+msgid ""
+"The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> "
+"(<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora."
+"redhat.com/docs/jargon-buster/</ulink>)."
+msgstr ""
+"Il termine non appare nel <citetitle>Fedora Jargon Buster</citetitle> "
+"(<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora."
+"redhat.com/docs/jargon-buster/</ulink>)."
+
+#: en_US/style.xml:588(para)
+msgid ""
+"The term does not appear in the <citetitle>American Heritage Dictionary</"
+"citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby."
+"com/61/ </ulink>)."
+msgstr ""
+"Il termine non appare nell'<citetitle>American Heritage Dictionary</"
+"citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby."
+"com/61/ </ulink>)."
+
+#: en_US/style.xml:596(para)
+msgid "The term does not appear in the glossary of the manual that you are writing."
+msgstr "Il termine non appare nel glossario del manuale che si sta scrivendo."
+
+#: en_US/style.xml:602(para)
+msgid "The term is not defined in the body text of the manual that you are writing."
+msgstr "Il termine non è definito nel testo del manuale che si sta scrivendo."
+
+#: en_US/style.xml:611(term)
+msgid "Avoid gender-specific language"
+msgstr "Evitare un linguaggio genere-specifico"
+
+#: en_US/style.xml:613(para)
+msgid ""
+"Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</"
+"literal> do not exist. There is no need to identify gender in your "
+"instructions."
+msgstr ""
+"Pronomi costruiti come <literal>his/her</literal> o <literal>s/he</literal> "
+"non esistono. Non c'è bisogno di identificare il genere nelle istruzioni."
+
+#: en_US/style.xml:621(term)
+msgid "Avoid culture-specific language"
+msgstr "Evitare un linguaggio specifico alla cultura"
+
+#: en_US/style.xml:623(para)
+msgid ""
+"There is little point in giving an example that everyone in your town knows "
+"about, but is a complete mystery to everyone else in the world."
+msgstr ""
+"Può esserci una piccola spiegazione per dare un esempio che tutti nel "
+"proprio paese conoscono ma è completamente sconosciuta al resto del mondo."
+
+#: en_US/style.xml:631(term)
+msgid "Avoid talking down to your reader"
+msgstr "Evitare di parlare male al proprio lettore"
+
+#: en_US/style.xml:633(para)
+msgid ""
+"There are few experiences more irritating for a user than documentation that "
+"says an action is easy or quick, when in fact the user cannot complete the "
+"action. Do not qualify or prejudge actions."
+msgstr ""
+"Alcune esperienze molto irritanti per un utente è quando la documentazione "
+"riporta che una azione è semplice e veloce, mentre di fatto l'utente non "
+"riesce a completarla. Non commentare o pregiudicare le istruzioni."
+
+#: en_US/style.xml:642(para)
+msgid ""
+"Other parts of this guide discuss in more detail tone and language usage "
+"that can cause offense."
+msgstr ""
+"Altre parti di questa guida discutono più dettagliatamente il tono e il "
+"linguaggio che possono risultare offensivi."
+
+#: en_US/style.xml:653(title)
+msgid "Grammar and Usage Guidelines"
+msgstr "Linee guida generali di grammatica"
+
+#: en_US/style.xml:656(title)
+msgid "Bibliographical Information"
+msgstr "Informazioni Bibliografiche"
+
+#: en_US/style.xml:657(para)
+msgid ""
+"This section is drawn partly from the <citetitle>GDSG</citetitle>, and "
+"partly from <citetitle>The Elements of Style</citetitle>, updated as "
+"necessary for the needs of 21st-century technical documentation writers."
+msgstr ""
+"Questa sezione è presa parzialmente dal <citetitle>GDSG</citetitle> e "
+"parzialmente da <citetitle>The Elements of Style</citetitle>, aggiornate "
+"alle necessità degli scrittori del 21° secolo di documentazione tecnica."
+
+#. FIXME: Again, check attribution viz. GNU FDL. This will be more work
+#. than the previous section.
+#: en_US/style.xml:668(para)
+msgid ""
+"This section contains an alphabetical list of grammar and usage guidelines "
+"for use in Fedora documentation. Many of these guidelines are only "
+"applicable to English-language usage, refer to the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of "
+"Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/"
+"cmosfaq.html</ulink>.)"
+msgstr ""
+"Questa sezione contiene una lista alfabetica di linee guida di grammatica "
+"per la documentazione di Fedora. Alcune di queste linee guida sono "
+"applicabili solo alla lingua Inglese, riferimenti ad <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) e al <citetitle>Chicago Manual of "
+"Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/"
+"cmosfaq.html</ulink>.)"
+
+#: en_US/style.xml:679(term)
+msgid "Abbreviations"
+msgstr "Abbreviazioni"
+
+#: en_US/style.xml:681(para)
+msgid ""
+"A shortened form of a word or phrase that takes the place of the full word "
+"or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, "
+"<literal>p.m.</literal>, and so on. Apply the following rules when you use "
+"abbreviations:"
+msgstr ""
+"Forme abbreviate di parole o frasi possono essere <literal>Dr.</literal>, "
+"<literal>a.m.</literal>, <literal>p.m.</literal> e così via. Applicare le "
+"seguenti regole quando si usano abbreviazioni:"
+
+#: en_US/style.xml:689(para)
+msgid ""
+"Avoid creating new abbreviations. Unfamiliar abbreviations can confuse "
+"rather than clarify a concept."
+msgstr ""
+"Evitare di creare nuove abbreviazioni. Abbreviazioni non familiari possono "
+"confondere invece di chiarire un concetto."
+
+#: en_US/style.xml:695(para)
+msgid "Do not explain or expand familiar abbreviations."
+msgstr "Non spiegare o espandere le abbreviazioni comuni."
+
+#: en_US/style.xml:700(para)
+msgid "Do not include familiar abbreviations in the glossary of your manual."
+msgstr "Non includere abbreviazioni familiari nel glossario del manuale."
+
+#: en_US/style.xml:706(para)
+msgid ""
+"For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other "
+"words\" and <literal>e.g.</literal> for \"for example\", do not use the "
+"abbreviation. Spell out the entire phrase."
+msgstr ""
+"Per le abbreviazioni di frasi come <literal>i.e.</literal> per \"in other "
+"words\" e <literal>e.g.</literal> for \"for example\", non usare "
+"l'abbreviazione. Usare l'intera frase."
+
+#: en_US/style.xml:715(term)
+msgid "Adjectives"
+msgstr "Aggettivi"
+
+#: en_US/style.xml:717(para)
+msgid ""
+"Use adjectives with caution. If an adjective is necessary to differentiate "
+"between items, then use adjectives. In all cases, test whether the phrase "
+"can stand alone without the adjective."
+msgstr ""
+"Usare gli aggettivi con cautela. Se un aggettivo è necessario per "
+"differenziare i termini, allora si può usare. In tutti i casi, provare a creare la "
+"frase senza aggettivi."
+
+#: en_US/style.xml:726(term)
+msgid "Acronyms"
+msgstr "Acronimi"
+
+#: en_US/style.xml:728(para)
+msgid ""
+"A term that represents a multi-word term. Typically, acronyms are formed in "
+"the following ways:"
+msgstr ""
+"Un termine che rappresenta più parole. Tipicamente gli acronimi sono così "
+"formati:"
+
+#: en_US/style.xml:734(para)
+msgid ""
+"From the first letters of each word in a compound term, for example Table of "
+"Contents (TOC)."
+msgstr ""
+"Dalla prima lettera di ogni parola che compone il termine, per esempio Table "
+"of Contents (TOC)."
+
+#: en_US/style.xml:740(para)
+msgid ""
+"From recognizable parts of a compound term, such as GNU Object Model "
+"Environment (GNOME)."
+msgstr ""
+"Per riconoscere parte di un termine composto, come GNU Object Model "
+"Environment (GNOME)."
+
+#: en_US/style.xml:746(para)
+msgid "Apply the following rules when you use acronyms:"
+msgstr "Applicare le seguenti regole quando si usano acronimi:"
+
+#: en_US/style.xml:751(para)
+msgid ""
+"On the first occurrence of an acronym, spell out the full term, with the "
+"acronym in parentheses."
+msgstr ""
+"Alla prima occorrenza di un acronimo, specificare l'intero termine con "
+"l'acronimo in frase."
+
+#: en_US/style.xml:757(para)
+msgid ""
+"Do not spell out the full compound for well-known acronyms, unless you think "
+"the information is useful for readers."
+msgstr ""
+"Non mettere l'intero contenuto di un acronimo per esteso a meno che non si "
+"pensa che l'informazione sia utile al lettore."
+
+#: en_US/style.xml:764(para)
+msgid ""
+"Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than "
+"clarify a concept."
+msgstr ""
+"Evitare di creare nuovi acronimi. Acronimi non familiari possono "
+"confonredere invece di chiarire il concetto."
+
+#: en_US/style.xml:770(para)
+msgid ""
+"Write the acronym in uppercase letters, unless there is a compelling case "
+"for lowercase."
+msgstr ""
+"Scrivere l'acronimo a lettere maiuscole, a meno che non comprende delle "
+"lettere minuscole."
+
+#: en_US/style.xml:776(para)
+msgid "Include the acronym and the full term in the glossary of your manual."
+msgstr "Includere l'acronimo e il suo significato nel glossario del manuale."
+
+#: en_US/style.xml:785(term)
+msgid "Adverbs"
+msgstr "Avverbi"
+
+#: en_US/style.xml:787(para)
+msgid ""
+"Use adverbs with caution. If an adverb is necessary to qualify the function "
+"of a component, then use an adverb. In all cases, test whether the phrase "
+"can stand alone without the adverb. Classic superfluous adverbs "
+"<literal>simply</literal>, <literal>easily</literal>, <literal>quickly</"
+"literal>."
+msgstr ""
+"Usare gli avverbi con cautela. Se un avverbio è necessario per qualificare "
+"la funzione di un componente, allora usare l'avverbio. In tutti i casi, provare "
+"a creare la frase senza avverbi. Avverbi superflui classici "
+"<literal>semplicemente</literal>, <literal>facilmente</literal>, "
+"<literal>velocemente</literal>."
+
+#: en_US/style.xml:798(term)
+msgid "Anthropomorphism"
+msgstr "Antropomorfismo"
+
+#: en_US/style.xml:802(para)
+msgid "Do not apply emotions, desires, or opinions to software applications."
+msgstr "Non applicare emozioni, desideri o opinioni alle applicazioni."
+
+#: en_US/style.xml:808(para)
+msgid ""
+"Do not apply a sense of location or dimension to a software application. A "
+"user can not be \"in\" a text editor."
+msgstr ""
+"Non applicare un senso di locazione o dimensione ad un software. Un utente "
+"non può essere \"dentro\" ad un editor di testo."
+
+#: en_US/style.xml:818(term)
+msgid "Articles"
+msgstr "Articoli"
+
+#: en_US/style.xml:820(para)
+msgid ""
+"Do not use the definite article <literal>the</literal> to begin any of the "
+"following items:"
+msgstr ""
+"Non usare gli articoli definiti <literal>il/lo/la (the)</literal> per "
+"iniziare una delle seguenti frasi:"
+
+#: en_US/style.xml:826(para)
+msgid "Manual titles"
+msgstr "Titoli di manuali"
+
+#: en_US/style.xml:831(para)
+msgid "Chapter titles"
+msgstr "Titoli di capitoli"
+
+#: en_US/style.xml:836(para) en_US/style.xml:1239(term)
+msgid "Headings"
+msgstr "Testate"
+
+#: en_US/style.xml:841(para)
+msgid "Figure captions"
+msgstr "Legende di figure"
+
+#: en_US/style.xml:846(para)
+msgid "Table captions"
+msgstr "Legende di tabelle"
+
+#: en_US/style.xml:851(para)
+msgid "Callouts"
+msgstr "Callouts"
+
+#: en_US/style.xml:859(term)
+msgid "Apostrophe"
+msgstr "Apostrofi"
+
+#: en_US/style.xml:861(para)
+msgid "Do not use apostrophes except where absolutely required"
+msgstr "Non usare apostrofi se non strettamente necessari"
+
+#: en_US/style.xml:866(para)
+msgid "Do not use apostrophes to denote possession."
+msgstr "Non usare apostrofi per denotare la possessione."
+
+#: en_US/style.xml:871(para)
+msgid "Do not use apostrophes to denote contractions."
+msgstr "Non usare apostrofi per denotare la contrazione."
+
+#: en_US/style.xml:876(para)
+msgid "Do not use apostrophes to denote plurals."
+msgstr "Non usare apostrofi per definire plurali."
+
+#: en_US/style.xml:882(title)
+msgid "Incorrect: Apostrophes"
+msgstr "Non corretto: Apostrofi"
+
+#: en_US/style.xml:885(para)
+msgid "the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+msgstr "the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+
+#: en_US/style.xml:891(para)
+msgid "don't use the default option"
+msgstr "don't use the default option"
+
+#: en_US/style.xml:896(para)
+msgid "several SCSI disk's"
+msgstr "several SCSI disk's"
+
+#: en_US/style.xml:903(title)
+msgid "Correct: No apostrophes"
+msgstr "Corretto: Niente apostrofi"
+
+#: en_US/style.xml:906(para)
+msgid ""
+"the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</"
+"guimenu>"
+msgstr ""
+"the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</"
+"guimenu>"
+
+#: en_US/style.xml:912(para)
+msgid "do not use the default option"
+msgstr "do not use the default option"
+
+#: en_US/style.xml:917(para)
+msgid "several SCSI disks"
+msgstr "several SCSI disks"
+
+#: en_US/style.xml:926(term)
+msgid "Brackets"
+msgstr "Parentesi"
+
+#: en_US/style.xml:930(para)
+msgid ""
+"Do not use brackets [such as these] as a substitute for parentheses (such as "
+"these)."
+msgstr "Non usare parentesi [come queste] in sostituzione di (queste)."
+
+#: en_US/style.xml:936(para)
+msgid "Use brackets for optional command line entries."
+msgstr "Usare le parentesi per le opzioni ai comandi."
+
+#: en_US/style.xml:941(para)
+msgid ""
+"Do not use angle brackets to indicate variables in text, instead use the "
+"<sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref "
+"linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+msgstr ""
+"Non usare parentesi quadrate per indicare variabili nel testo, invece di "
+"usare tag <sgmltag class=\"starttag\">sostituibili</sgmltag>. Fare "
+"riferimento a <xref linkend=\"sn-xml-tags-replaceable\"/> per maggiori "
+"infirmazioni."
+
+#: en_US/style.xml:953(term)
+msgid "Capitalization"
+msgstr "Capitalizzare"
+
+#: en_US/style.xml:955(para)
+msgid "Capitalize in the following situations:"
+msgstr "Scrivere in maiuscolo nelle seguenti situazioni:"
+
+#: en_US/style.xml:960(para)
+msgid "All letters in acronyms, unless the acronym is a well-known exception"
+msgstr ""
+"Tutte le lettere in un acronimo, a meno che l'acronimo sia una eccezzione "
+"conosciuta"
+
+#: en_US/style.xml:966(para)
+msgid "Initial letter of the first word in a list"
+msgstr "La lettera iniziale della prima parola in una lista"
+
+#: en_US/style.xml:971(para)
+msgid "Initial letter of the first word in a callout"
+msgstr "La lettera iniziale della prima parola in una espressione"
+
+#: en_US/style.xml:976(para)
+msgid "Initial letter of a key name, such as the <keycap>Shift</keycap> key"
+msgstr ""
+"La lettera iniziale del nome di un tasto, come il tasto <keycap>Shift</"
+"keycap>"
+
+#: en_US/style.xml:982(para)
+msgid "Initial letter of a sentence"
+msgstr "La lettera iniziale di una domanda"
+
+#: en_US/style.xml:986(title)
+msgid "Command Names"
+msgstr "Nomi di Comandi"
+
+#: en_US/style.xml:987(para)
+msgid ""
+"Avoid starting a sentence with a command name or application name that has a "
+"lowercase initial letter."
+msgstr ""
+"Evitare di iniziare una frase con il nome di un comando o di una "
+"applicazione che ha la lettera iniziale minuscola."
+
+#: en_US/style.xml:994(para)
+msgid "Initial letter of a complete sentence after a colon"
+msgstr "La lettera iniziale di una frase completa dopo i due punti"
+
+#: en_US/style.xml:999(para)
+msgid "Do not capitalize in the following situations:"
+msgstr "Non capitalizzare nelle seguenti situazioni:"
+
+#: en_US/style.xml:1004(para)
+msgid "A compound term that is followed by an abbreviation or an acronym"
+msgstr "Un termine complesso che è seguito da una abbreviazione o un acronimo"
+
+#: en_US/style.xml:1010(para)
+msgid "When you want to emphasize something"
+msgstr "Quando si vuole enfatizzare qualcosa"
+
+#: en_US/style.xml:1015(para)
+msgid "Variable names"
+msgstr "Nomi di variabili"
+
+#: en_US/style.xml:1020(para)
+msgid "The initial letter of an incomplete sentence after a colon"
+msgstr "La lettera iniziale di una sentenza incompleta dopo due punti"
+
+#: en_US/style.xml:1029(term)
+msgid "Captions"
+msgstr "Legende"
+
+#: en_US/style.xml:1031(para)
+msgid ""
+"Use the same rules as for headings, for all captions accompanying figures "
+"and tables. Do not put a period at the end of a caption."
+msgstr ""
+"Usare le stesse regole per le intestazioni, per tutte le legende che accompagnano "
+"le figure e le tabelle. Non mettere un punto alla fine della legenda."
+
+#: en_US/style.xml:1039(term)
+msgid "Colon"
+msgstr "Due punti"
+
+#: en_US/style.xml:1041(para)
+msgid "Use a colon in the following situations:"
+msgstr "Usare i due punti nelle seguenti situazioni:"
+
+#: en_US/style.xml:1046(para)
+msgid "To introduce a list"
+msgstr "Per introdurre una lista"
+
+#: en_US/style.xml:1051(para)
+msgid "Before an explanation"
+msgstr "Prima di una spiegazione"
+
+#: en_US/style.xml:1056(para)
+msgid "After an introduction"
+msgstr "Dopo una introduzione"
+
+#: en_US/style.xml:1061(para)
+msgid "Do not use a colon in the following situations:"
+msgstr "Non usare i due punti nelle seguenti situazioni:"
+
+#: en_US/style.xml:1066(para)
+msgid "To introduce a figure or a table"
+msgstr "Per introdurre una figura o una tabella"
+
+#: en_US/style.xml:1071(para)
+msgid "To introduce headings"
+msgstr "Per introdurre intestazioni"
+
+#: en_US/style.xml:1076(para)
+msgid "At the end of an introduction to a procedure"
+msgstr "Alla fine di una introduzione ad una procedura"
+
+#: en_US/style.xml:1084(term)
+msgid "Column headings"
+msgstr "Intestazioni di colonne"
+
+#: en_US/style.xml:1086(para)
+msgid "Use the same rules as for headings."
+msgstr "Usare le stesse regole delle intestazioni."
+
+#: en_US/style.xml:1092(term)
+msgid "Comma"
+msgstr "Virgola"
+
+#: en_US/style.xml:1094(para)
+msgid "Use commas in the following situations:"
+msgstr "Usare le virgole nelle seguenti situazioni:"
+
+#: en_US/style.xml:1099(para)
+msgid "To separate items in a series"
+msgstr "Per separare parole in una serie"
+
+#: en_US/style.xml:1104(para)
+msgid "To separate the parts of a sentence"
+msgstr "Per separare le parti di un periodo"
+
+#: en_US/style.xml:1109(para)
+msgid "To separate nonrestrictive phrases"
+msgstr "Per separare frasi non restrittive"
+
+#: en_US/style.xml:1114(para)
+msgid "Instead of dashes to set off appositives"
+msgstr "Invece dei trattini per disattivare le apposizioni"
+
+#: en_US/style.xml:1119(para)
+msgid "With <emphasis>for example</emphasis> and similar expressions"
+msgstr "Con <emphasis>per esempio</emphasis> ed espressioni simili"
+
+#: en_US/style.xml:1125(para)
+msgid "Do not use commas in the following situations:"
+msgstr "Non usare le virgole nelle seguenti situazioni:"
+
+#: en_US/style.xml:1130(para)
+msgid "In a series of adjectives used as one modifier"
+msgstr "In una serie di aggettivi usati come dei modificatori"
+
+#: en_US/style.xml:1135(para)
+msgid "Between two short independent clauses"
+msgstr "Tra due piccole clausole indipendenti"
+
+#: en_US/style.xml:1143(term) en_US/emacs-nxml.xml:86(title)
+msgid "Commands"
+msgstr "Comandi"
+
+#: en_US/style.xml:1145(para)
+msgid "Do not use commands as verbs."
+msgstr "Non usare comandi come verbi."
+
+#: en_US/style.xml:1151(term)
+msgid "Contractions"
+msgstr "Contrazioni"
+
+#: en_US/style.xml:1153(para)
+msgid ""
+"Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</"
+"emphasis>, or <emphasis>isn't</emphasis>."
+msgstr ""
+"Non usare contrazioni come <emphasis>can't</emphasis>, <emphasis>don't</"
+"emphasis>, o <emphasis>isn't</emphasis>."
+
+#: en_US/style.xml:1160(term)
+msgid "Dash"
+msgstr "Lineetta"
+
+#: en_US/style.xml:1162(para)
+msgid ""
+"Do not use the em dash or the en dash. Use a paragraph break or a colon "
+"instead, where you want to create an introductory piece of text. If you have "
+"several items that you want to introduce, then you can use a variable list."
+msgstr ""
+"Non usare i \"em dash\" o \"en dash\". Utilizzare invece una interruzione "
+"di paragrafo o due punti, dove si desidera creare un pezzo di "
+"testo introduttivo. Se si dispone di più elementi che si vogliono "
+"introdurre, allora si può utilizzare una lista."
+
+#: en_US/style.xml:1171(term)
+msgid "Ellipsis"
+msgstr "Ellissi"
+
+#: en_US/style.xml:1173(para)
+msgid "Use an ellipsis in the following situations:"
+msgstr "Usare una ellisse nelle seguenti situazioni:"
+
+#: en_US/style.xml:1178(para)
+msgid "To show that you have omitted something from a sentence"
+msgstr "Per mostrare che si è omesso qualcosa di una frase"
+
+#: en_US/style.xml:1183(para)
+msgid "To indicate a pause when you quote displayed text"
+msgstr "Per indicare una pausa quando si cita un testo visualizzato"
+
+#: en_US/style.xml:1191(term)
+msgid "Fractions"
+msgstr "Frazioni"
+
+#: en_US/style.xml:1193(para)
+msgid "Follow these rules when using fractions:"
+msgstr "Seguire queste regole quando si usano frazioni:"
+
+#: en_US/style.xml:1198(para)
+msgid ""
+"Use numerals for fractions in tables and in units of measurement, but spell "
+"out fractions in prose."
+msgstr ""
+"Usare numerazioni per frazioni in tabelle e in unità di misura ma scrivere "
+"le frazioni per esteso."
+
+#: en_US/style.xml:1204(para)
+msgid ""
+"Use a space between a numeral and a related fraction, if there is a possible "
+"ambiguity. For example: 1 1/2 instead of 11/2."
+msgstr ""
+"Usare uno spazio fra un numero e una frazione correlata, se c'è una "
+"possibilità di ambiguità. Per esempio: 1 1/2 invece di 11/2."
+
+#: en_US/style.xml:1211(para)
+msgid ""
+"If a fraction is used in a compound modifier, insert a hyphen between the "
+"fraction and the unit of measurement."
+msgstr ""
+"Se una frazione è usata in una serie di modifiche, inserire un punto "
+"esclamativo tra la frazione e l'unità di misura."
+
+#: en_US/style.xml:1220(term)
+msgid "Gender"
+msgstr "Genere"
+
+#: en_US/style.xml:1222(para)
+msgid "Refer to <xref linkend=\"sn-fundamentals-9\"/>."
+msgstr "Fare riferimento a <xref linkend=\"sn-fundamentals-9\"/>."
+
+#: en_US/style.xml:1228(term)
+msgid "Grammar"
+msgstr "Grammatica"
+
+#: en_US/style.xml:1230(para)
+msgid ""
+"Use standard American English grammar rules, refer to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+"Usare le regole standard Inglesi Americane, fare riferimento a <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+
+#: en_US/style.xml:1241(para)
+msgid "Use the following capitalization rules in headings:"
+msgstr "Usare le seguenti regole di capitalizzazione nelle intestazioni:"
+
+#: en_US/style.xml:1246(para)
+msgid "Initial uppercase letter of the first word"
+msgstr "Lettera iniziale maiuscola della prima parola"
+
+#: en_US/style.xml:1251(para)
+msgid "Initial uppercase letter for all nouns, adjectives, and verbs."
+msgstr "Lettera iniziale maiuscola per tutti i nomi, aggettivi e verbi."
+
+#: en_US/style.xml:1257(para)
+msgid ""
+"All lowercase letters for conjunctions, articles, and prepositions of fewer "
+"than four letters"
+msgstr ""
+"Tutte lettere minuscole per congiunzioni, articoli e preposizioni inferiori "
+"di quattro lettere"
+
+#: en_US/style.xml:1263(para)
+msgid "Initial uppercase letter for prepositions of four letters or longer"
+msgstr "Lettera iniziale maiuscola per preposizioni di quattro lettere o più"
+
+#: en_US/style.xml:1269(para)
+msgid "Initial uppercase letter for conjunctions of four letters or longer"
+msgstr "Lettera iniziale maiuscola per congiunzioni di quattro lettere o più"
+
+#: en_US/style.xml:1280(term)
+msgid "Hyphen"
+msgstr "Trattino"
+
+#: en_US/style.xml:1282(para)
+msgid "Use hyphens in the following situations:"
+msgstr "Usare i trattini nelle seguenti situazioni:"
+
+#: en_US/style.xml:1287(para)
+msgid "With a numeral in a compound modifier"
+msgstr "Con una serie in un modificatore composto"
+
+#: en_US/style.xml:1291(para)
+msgid "To prevent ambiguity"
+msgstr "Per prevenire ambiguità"
+
+#: en_US/style.xml:1296(para)
+msgid ""
+"With some standard prefixes and suffixes. Use the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) for guidance"
+msgstr ""
+"Con alcuni prefissi e suffissi standard. Usare <citetitle>American Heritage "
+"Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://"
+"www.bartleby.com/61/</ulink>) come guida"
+
+#: en_US/style.xml:1305(para)
+msgid "In spelled-out fractions"
+msgstr "In frazioni da spiegare"
+
+#: en_US/style.xml:1310(para)
+msgid ""
+"In variable names of two or more words, such as <replaceable>directory-name</"
+"replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+msgstr ""
+"In nomi variabili con due o più parole, come <replaceable>directory-name</"
+"replaceable>. Nota: <replaceable>filename</replaceable> è una eccezzione."
+
+#: en_US/style.xml:1317(para)
+msgid "Do not use hyphens in the following situations:"
+msgstr "Non usare i trattini nelle seguenti situazioni:"
+
+#: en_US/style.xml:1322(para)
+msgid "For industry-accepted terms"
+msgstr "Per termini accettati"
+
+#: en_US/style.xml:1327(para)
+msgid "To construct verbs"
+msgstr "Per costruire verbi"
+
+#: en_US/style.xml:1332(para)
+msgid "With an adverb ending in <emphasis>ly</emphasis>"
+msgstr "Con una modifica di avverbi in <emphasis>ly</emphasis>"
+
+#: en_US/style.xml:1337(para)
+msgid "With numerals as single modifiers"
+msgstr "Con numerazioni come singole modifiche"
+
+#: en_US/style.xml:1342(para)
+msgid ""
+"With a word that is listed as unhyphenated in the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+msgstr ""
+"In una parola che è elencata come \"unhyphenated\" nel <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) e che usa un prefisso comune"
+
+#: en_US/style.xml:1351(para)
+msgid "With trademarked terms"
+msgstr "Con termini di marchi"
+
+#: en_US/style.xml:1359(term)
+msgid "Latin terms"
+msgstr "Termini Latini"
+
+#: en_US/style.xml:1361(para)
+msgid "Do not use Latin terms. Use an equivalent English term instead."
+msgstr "Non usare termini Latini. Usare invece un termine Inglese equivalente."
+
+#: en_US/style.xml:1368(term)
+msgid "Like"
+msgstr "Come"
+
+#: en_US/style.xml:1370(para)
+msgid ""
+"Do not use the term <emphasis>like</emphasis> to denote equivalence or "
+"similarity."
+msgstr ""
+"Non usare il termine <emphasis>like</emphasis> per denotare una "
+"equivalenza o similarità."
+
+#: en_US/style.xml:1377(term)
+msgid "Lists"
+msgstr "Liste"
+
+#: en_US/style.xml:1379(para)
+msgid "Introduce a list with a complete sentence that ends with a colon."
+msgstr "Introdurre una lista con una frase completa che finisce con due punti."
+
+#: en_US/style.xml:1386(term)
+msgid "Numbers"
+msgstr "Numeri"
+
+#: en_US/style.xml:1388(para)
+msgid "Spell out numbers in the following situations:"
+msgstr "Mettere per esteso i numeri nelle seguenti situazioni:"
+
+#: en_US/style.xml:1393(para)
+msgid "Numbers from zero through nine unless the number is part of a measurement"
+msgstr "Numeri da zero a nove a meno che il numero è parte di una misurazione"
+
+#: en_US/style.xml:1398(para)
+msgid "Approximations"
+msgstr "Approssimazioni"
+
+#: en_US/style.xml:1403(para)
+msgid ""
+"Extreme values such as <emphasis>million</emphasis>, but precede the value "
+"with a numeral"
+msgstr ""
+"Valori estremi come <emphasis>millione</emphasis>, ma precedere il valore "
+"con un numero"
+
+#: en_US/style.xml:1409(para)
+msgid "Any number that begins a sentence"
+msgstr "Qualsiasi numero che inizia una frase"
+
+#: en_US/style.xml:1414(para)
+msgid ""
+"A number that is immediately followed by a numeral, for example: "
+"<literal>two 10 MB files</literal>"
+msgstr ""
+"Un numero che è immediatamente seguito da un numero, per esempio: "
+"<literal>due 10 MB files</literal>"
+
+#: en_US/style.xml:1423(term)
+msgid "Numerals"
+msgstr "Numerazioni"
+
+#: en_US/style.xml:1425(para)
+msgid "Use numerals in the following situations:"
+msgstr "Usare numerazioni nelle seguenti situazioni:"
+
+#: en_US/style.xml:1430(para)
+msgid "The number 10 or greater"
+msgstr "Il numero 10 o superiore"
+
+#: en_US/style.xml:1435(para)
+msgid "Negative numbers"
+msgstr "Numeri negativi"
+
+#: en_US/style.xml:1439(para)
+msgid "Most fractions"
+msgstr "La maggior parte delle frazioni"
+
+#: en_US/style.xml:1444(para)
+msgid "Percentages"
+msgstr "Percentuali"
+
+#: en_US/style.xml:1449(para)
+msgid "Decimals"
+msgstr "Decimali"
+
+#: en_US/style.xml:1454(para)
+msgid "Measurements"
+msgstr "Misure"
+
+#: en_US/style.xml:1459(para)
+msgid "Units of time smaller than one second"
+msgstr "Unità di tempo inferiori al secondo"
+
+#: en_US/style.xml:1464(para)
+msgid "References to bits and bytes"
+msgstr "Riferimenti a bit e byte"
+
+#: en_US/style.xml:1472(term)
+msgid "Parentheses"
+msgstr "Parentesi"
+
+#: en_US/style.xml:1474(para)
+msgid "Use parentheses in the following situations:"
+msgstr "Usare parentesi nelle seguenti situazioni:"
+
+#: en_US/style.xml:1479(para)
+msgid ""
+"To contain the abbreviation of a term on the first occurrence of the full "
+"term"
+msgstr ""
+"Per contenere le abbreviazioni di un termine sulla prima occorrenza del "
+"termine completo"
+
+#: en_US/style.xml:1485(para)
+msgid "In man page references, specifically the section number"
+msgstr "Nei riferimenti nelle pagine di manuale, specificamente il numero di sezione"
+
+#: en_US/style.xml:1493(term)
+msgid "Period"
+msgstr "Punto di fine"
+
+#: en_US/style.xml:1495(para)
+msgid "Use a period in the following situations:"
+msgstr "Usare un punto di fine nelle seguenti situazioni:"
+
+#: en_US/style.xml:1500(para)
+msgid "To end a sentence"
+msgstr "Per finire una frase"
+
+#: en_US/style.xml:1505(para)
+msgid "In file and directory names"
+msgstr "Nei file e nei nomi delle cartelle"
+
+#: en_US/style.xml:1510(para)
+msgid "In abbreviations that can be mistaken for words, such as a.m. and U.S."
+msgstr "In abbreviazioni che possono essere confuse con parole, come a.m. e U.S."
+
+#: en_US/style.xml:1519(term)
+msgid "Punctuation"
+msgstr "Punteggiatura"
+
+#: en_US/style.xml:1521(para)
+msgid ""
+"Use standard American English punctuation rules. In addition to the specific "
+"points of punctuation in this section, refer also to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+"Usare le regole standard dell' Inglese Americano. In aggiunta ai punti "
+"specifici di questa sezione, fare riferimento anche al <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+
+#: en_US/style.xml:1531(term)
+msgid "Punctuation in numbers"
+msgstr "Punteggiatura in numeri"
+
+#: en_US/style.xml:1533(para)
+msgid ""
+"Do not use a comma in numerals of four digits. Use a comma in numerals of "
+"more than four digits."
+msgstr ""
+"Non usare la virgola in numeri di quattro cifre. Usare la virgola in numeri "
+"superiori a quattro cifre."
+
+#: en_US/style.xml:1540(term)
+msgid "Quotation marks"
+msgstr "Virgolette"
+
+#: en_US/style.xml:1542(para)
+msgid ""
+"Use quotation marks to indicate material that is taken verbatim from another "
+"source. Do not use quotation marks to excuse terms from legitimacy. If the "
+"term is not legitimate, then use another term. If you must use that term, "
+"declare the term in the glossary and make the term legitimate."
+msgstr ""
+"Usare le virgolette per indicare che il materiale è citato da un'altra "
+"fonte. Non utilizzare le virgolette per scusare termini illegittimi. Se il "
+"termine non è legittimo, utilizzare un altro termine. Se si deve usare "
+"questo termine, dichiarare il termine nel glossario e rendere legittimo il "
+"termine."
+
+#: en_US/style.xml:1553(term)
+msgid "See v. Refer to"
+msgstr "Vedere v. Riferimento a"
+
+#: en_US/style.xml:1555(para)
+msgid ""
+"When referring a user to another resource, use \"refer to\" instead of \"see"
+"\", and \"refer also to\" instead of \"see also\". This differentiates from "
+"the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag"
+"\">seealso</sgmltag> tags that are used in indexing. These tags create "
+"special links in the index. To be consistent throughout the document, we "
+"reserve the special words \"see\" and \"see also\" for hyperlinked index "
+"references, and use \"refer to\" and \"refer also to\" for non-hyperlinked "
+"and non-indexed references."
+msgstr ""
+"Quando si fa riferire un utente ad un'altra risorsa, usare \"fare riferimento a "
+"\" invece di \"vedere\", e \"fare riferimento anche a \" invece di \"vedere anche\". "
+"Questi differiscono dai tag <sgmltag class=\"starttag\">see</sgmltag> e <sgmltag class="
+"\"starttag\">seealso</sgmltag> che sono usati nell'indicizzazione. Questi tag "
+"creano collegamenti speciali negli indici. Da considerare nel documento, si "
+"riservano le parole speciali \"see\" e \"see also\" per i collegamenti agli "
+"indici di riferimento, usare \"refer to\" e \"refer also to\" per i riferimenti non "
+"collegati e non indicizzati."
+
+#: en_US/style.xml:1570(term)
+msgid "Semicolon"
+msgstr "Punto e virgla"
+
+#: en_US/style.xml:1572(para)
+msgid "Do not use semicolons."
+msgstr "Non usare punti e virgola."
+
+#: en_US/style.xml:1578(term)
+msgid "Slash"
+msgstr "Slash"
+
+#: en_US/style.xml:1580(para)
+msgid ""
+"Except where required as part of a filename, do not use slashes \"/\" in "
+"your writing. The construction <literal>and/or</literal>, for example, does "
+"not exist. Use one or the other term instead."
+msgstr ""
+"Eccetto quando richiesto come parte di un nome del file, non usare la slash "
+"\"/\" nella scrittura. I costrutti come ad esempio <literal>e/o</literal> "
+"non esistono. Usare invece un altro termine."
+
+#: en_US/style.xml:1589(term)
+msgid "Spelling"
+msgstr "Spelling"
+
+#: en_US/style.xml:1591(para)
+msgid ""
+"Use standard American English spelling rules, refer to the "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+msgstr ""
+"Usare le regole di spelling dell'Inglese Americano, fare riferimento a <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) per una guida."
+
+#: en_US/style.xml:1600(term)
+msgid "Titles"
+msgstr "Titoli"
+
+#: en_US/style.xml:1602(para)
+msgid "For manual titles use the same rules as for headings."
+msgstr "Per titoli dei manuali usare le stesse regole delle intestazioni."
+
+#: en_US/style.xml:1608(term)
+msgid "Units"
+msgstr "Unità"
+
+#: en_US/style.xml:1610(para)
+msgid "Follow these rules when using units:"
+msgstr "Seguire queste regole quando si usano unità:"
+
+#: en_US/style.xml:1615(para)
+msgid ""
+"Use standard abbreviations for units of measurements, do not invent your own "
+"abbreviations."
+msgstr ""
+"Usare le abbreviazioni standard per unità di misura, non invertire le "
+"abbreviazioni."
+
+#: en_US/style.xml:1621(para)
+msgid ""
+"For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of "
+"Electrical and Electronics Terms</citetitle>."
+msgstr ""
+"Per maggiori informazioni fare riferimento a <citetitle>IEEE Standard "
+"Dictionary of Electrical and Electronics Terms</citetitle>."
+
+#: en_US/style.xml:1630(para)
+msgid "Use periods for abbreviated units that might be mistaken for a word."
+msgstr ""
+"Usare frasi per le unità abbreviate che possono essere confuse con una "
+"parola."
+
+#: en_US/style.xml:1636(para)
+msgid ""
+"Most standard abbreviations of units account for both singular and plural "
+"usage."
+msgstr ""
+"La maggior parte delle abbreviazioni standard di unità vanno bene per l'uso "
+"singolare o plurale."
+
+#: en_US/style.xml:1642(para)
+msgid "Insert a space between the numeral and the unit of measurement."
+msgstr "Inserire uno spazio tra il numero e l'unità di misurazione."
+
+#: en_US/style.xml:1656(title)
+msgid "Composition Tips"
+msgstr "Suggerimenti alla composizione"
+
+#. This section will collect miscellanea and advice for specific
+#. situations that the FDP editors encounter. I hope they will feel
+#. free to e-mail me sticky situations or particularly interesting
+#. examples of work they've beautified. Hopefully not too much will be
+#. drawn from my own work! - PWF.
+#: en_US/style.xml:1668(para)
+msgid ""
+"This section contains usage tips based on situations the Fedora "
+"Documentation Project editors have encountered in the past. You should read "
+"and understand these examples to improve your own documentation. The Fedora "
+"Documentation Project editors welcome additional examples."
+msgstr ""
+"Questa sezione contiene suggerimenti su situazioni che i redattori del "
+"Fedora Documentation Project hanno incontrato in passato. Si consiglia di "
+"leggere e capire questi esempi per migliorare la propria documentazione. I "
+"redattori del Fedora Documentation Project accettano volentieri ulteriori "
+"esempi."
+
+#: en_US/style.xml:1676(title)
+msgid "Active Voice"
+msgstr "Forma attiva"
+
+#: en_US/style.xml:1677(para)
+msgid ""
+"Always use active voice, except when it is awkward to do so. The tutorial "
+"tells the user how to accomplish a task, and should give instructions "
+"clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. "
+"These words are redundant in a tutorial, since the reader assumes you are "
+"outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" "
+"\"might,\" and other words that indicate you are unsure about the subject "
+"matter. Your tutorial should cover a subject authoritatively. The reader "
+"should never be concerned about unknown effects of following the tutorial."
+msgstr ""
+"Usare sempre la forma attiva, eccetto quando è sconveniente. Il tutorial "
+"spiega come l'utente deve compiere una missione e dovrebbe dare istruzioni "
+"chiare e concise. Evitare l'uso di \"si deve\", \"è necessario\" e simili. "
+"Queste parole sono ridondanti in un tutorial, in quanto il lettore "
+"presuppone che si sta delineando le misure necessarie per realizzare un "
+"compito. Inoltre, evitare l'uso di \"forse\", \"potrebbe\" e altre parole "
+"che indicano che non si è sicuri circa l'oggetto. Il tutorial dovrebbe "
+"coprire un soggetto autorevolmente. Il lettore non deve mai essere "
+"preoccupato per gli effetti sconosciuti di seguire il tutorial."
+
+#: en_US/style.xml:1690(title)
+msgid "Incorrect: Passive voice"
+msgstr "Non corretto: forma passiva"
+
+#: en_US/style.xml:1691(para)
+msgid "The <command>yum update</command> command must be run."
+msgstr "Il comando <command>yum update</command> deve essere lanciato."
+
+#: en_US/style.xml:1694(para)
+msgid "You might want to run the <command>yum update</command> command."
+msgstr "Si dovrebbe lanciare il comando <command>yum update</command>."
+
+#: en_US/style.xml:1700(title)
+msgid "Correct: Active voice"
+msgstr "Corretto: forma attiva"
+
+#: en_US/style.xml:1701(para)
+msgid "Run the <command>yum update</command> command."
+msgstr "Lanciare il comando <command>yum update</command>."
+
+#: en_US/style.xml:1708(title)
+msgid "Present Tense"
+msgstr "Tempo presente"
+
+#: en_US/style.xml:1709(para)
+msgid ""
+"Write in the present tense. A good rule of thumb is that the words \"will\" "
+"and \"shall\" are almost never needed in describing what the user should do "
+"or see. They add unnecessary length to sentences and can confuse "
+"translators. They are also often indicators of passive voice; refer also to "
+"<xref linkend=\"sn-misc-active-voice\"/>."
+msgstr ""
+"Scrivere nel tempo presente. Una buona regola generale è che le parole \"will"
+"\" e \"shall\" non sono quasi mai necessarie per descrivere ciò che l'utente "
+"debba fare o vedere. Essi aggiungono lunghezza inutile e possono confondere i "
+"traduttori. Essi sono spesso anche degli indicatori della voce passiva; "
+"fare riferimento anche alle <xref linkend=\"sn-misc-active-voice\"/>."
+
+#: en_US/style.xml:1718(title)
+msgid "Incorrect: Future tense"
+msgstr "Non corretto: tempo futuro"
+
+#: en_US/style.xml:1719(para)
+msgid "The application will display a list of target files."
+msgstr "L'applicazione dovrebbe visualizzare una lista di file."
+
+#: en_US/style.xml:1722(para)
+msgid "A list of target files will be displayed by the application."
+msgstr "Una lista di file dovrebbe essere visualizzata dall'applicazione."
+
+#: en_US/style.xml:1727(title)
+msgid "Correct: Present tense"
+msgstr "Corretto: tempo presente"
+
+#: en_US/style.xml:1728(para)
+msgid "The application displays a list of target files."
+msgstr "L'applicazione visualizza una lista di file."
+
+#: en_US/style.xml:1735(title)
+msgid "Narrative Voice"
+msgstr "Voce narrativa"
+
+#: en_US/style.xml:1736(para)
+msgid ""
+"Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself "
+"the writer (whether including the reader or not), the Fedora Documentation "
+"Project, the Fedora community, or any other group. Do not refer to users "
+"with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word "
+"\"one.\" It is acceptable to refer to the reader with the second person "
+"pronoun \"you.\""
+msgstr ""
+"Non usare la prima persona \"Io\", \"noi\" o \"nostro\" per far riferimento "
+"a se stessi (volendo includere il lettore o no), al Fedora Documentation "
+"Project, alla comunità Fedora o qualsiasi altro gruppo. Non fare riferimento "
+"all'utente con la terza persona (\"lui\", \"lei\" o \"lui o lei\") o la "
+"parola \"qualcuno\". E' accettabile fare riferimento al lettore con la "
+"seconda persona \"you\" (N.d.T per la lingua inglese)."
+
+#: en_US/style.xml:1745(title)
+msgid "Incorrect: First or third person"
+msgstr "Non corretto: prima o terza persona"
+
+#: en_US/style.xml:1746(para)
+msgid ""
+"As described in the last section, I always run <command>up2date</command> "
+"before configuring the Samba server."
+msgstr ""
+"Come descritto nella prima sezione, io lancio sempre <command>up2date</"
+"command> prima di configurare Samba server."
+
+#: en_US/style.xml:1751(para)
+msgid ""
+"If the user needs to back up his or her files, s/he should use the "
+"<command>tar</command> or <command>cpio</command> command."
+msgstr ""
+"Se l'utente necessita di salvare il suo o i suoi files, esso/a dovrebbe usare "
+"il comando <command>tar</command> o <command>cpio</command>."
+
+#: en_US/style.xml:1757(title)
+msgid "Correct: Second (or no) person"
+msgstr "Corretto: Seconda (o no) persona"
+
+#: en_US/style.xml:1758(para)
+msgid ""
+"Refer to the section on <command>up2date</command> before configuring the "
+"Samba server."
+msgstr ""
+"Fare riferimento alla sezione <command>up2date</command> prima di "
+"configurare Samba server."
+
+#: en_US/style.xml:1762(para)
+msgid ""
+"If necessary, users can back up files with the <command>tar</command> or "
+"<command>cpio</command> command."
+msgstr ""
+"Se necessario, l'utente può salvare i file con i comandi <command>tar</"
+"command> o <command>cpio</command>."
+
+#: en_US/style.xml:1770(title)
+msgid "Negative Words"
+msgstr "Negazioni"
+
+#: en_US/style.xml:1771(para)
+msgid ""
+"Avoid negative words when possible, since they give documentation an overly "
+"dogmatic tone. The word \"avoid\" is useful for this purpose. Note that "
+"contractions are often used for negative words such as <emphasis>don't</"
+"emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-"
+"contractions\"/>."
+msgstr ""
+"Evitare le negazioni quando possibile, che possono dare un tono dogmatico "
+"alla documentazione. La parola \"evitare\" è utile a questo scopo. Notare "
+"che le contrazioni sono spesso usate per parole negative come "
+"<emphasis>don't</emphasis> or <emphasis>can't</emphasis>. Fare riferimento a "
+"<xref linkend=\"vle-contractions\"/>."
+
+#: en_US/style.xml:1782(title)
+msgid "Uncertainty"
+msgstr "Incertezza"
+
+#: en_US/style.xml:1783(para)
+msgid ""
+"Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the "
+"like. While occasional use of these constructions is acceptable, overuse "
+"reduces the authority of your documentation. The documentation should "
+"adequately cover a stock installation of Fedora. It is impossible for a "
+"tutorial-length document to cover every possible configuration scenario. "
+"Address the most common scenarios and note discrepancies only as required."
+msgstr ""
+"Evitare l'uso improprio di \"tipicamente\", \"usualmente\", \"spesso\", "
+"\"alcuni\" o simili. Mentre l'uso occasionale è accettabile, l'uso improprio "
+"riduce la serietà del documento. La documentazione dovrebbe coprire "
+"adeguatamente una installazione standard di Fedora. E' impossibile per un "
+"documento stile guida coprire tutti i possibili scenari di configurazioni. Specificare "
+"gli scenari piu comuni e annotare le discrepanze se richiesto."
+
+#: en_US/style.xml:1795(title)
+msgid "Redundant Coverage"
+msgstr "Copertura Rindondante"
+
+#: en_US/style.xml:1796(para)
+msgid ""
+"Avoid covering redundant material, such as how to update a Fedora system. "
+"These overarching topics may be covered in other tutorials. Writers "
+"frequently violate this guideline because they feel their tutorial is not "
+"long enough. Keep your tutorial from wandering off-topic. Instead, refer the "
+"reader to a separate tutorial whenever possible for complete coverage of "
+"that topic."
+msgstr ""
+"Evitare la ridondanza di materiale, come ad esempio il modo di aggiornare un "
+"sistema Fedora. Questi temi generali possono essere oggetto di altri "
+"tutorial. Gli scrittori spesso violano questo orientamento, poiché ritengono che "
+"la loro guida non è abbastanza lunga. Evitare di andare fuori argomento. "
+"Invece, fare riferire i lettori a guide separate, ove possibile, per "
+"completare la copertura di tale argomento."
+
+#: en_US/style.xml:1808(title)
+msgid "Self-referential Value Judgments"
+msgstr "Giudizi Autoreferenziali"
+
+#: en_US/style.xml:1809(para)
+msgid ""
+"Avoid statements such as \"One of the most important things to do is "
+"<replaceable>XYZ</replaceable>.\" If the procedure is important, the reader "
+"already expects it to be in your tutorial. The converse is also true: If a "
+"procedure appears in your tutorial, the reader expects it is important. This "
+"is especially true if you use a whole section for the procedure in question. "
+"Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as "
+"required. If the whole section concerns how to do <replaceable>XYZ</"
+"replaceable>, leave this sentence out entirely. Refer also to <xref linkend="
+"\"vle-golden-rule-4\"/>."
+msgstr ""
+"Evitare le dichiarazioni come \"Una delle cose più importanti da fare è "
+"<replaceable> XYZ </ replaceable>\". Se la procedura è importante, il "
+"lettore si aspetta già che sia nel tutorial. La discussione è anche vera: Se "
+"una procedura compare nel tuo tutorial, il lettore si aspetta sia "
+"importante. Ciò è particolarmente vero se si usa una intera sezione per la "
+"procedura in questione. Si limita a indicare \"Fare <replaceable> XYZ </ "
+"replaceable>\". Allora elaborare come richiesto. Se l'intera sezione "
+"riguarda il modo di fare <replaceable> XYZ </ replaceable>, lasciare questa "
+"frase interamente. Si veda anche il <xref linkend=\"vle-golden-rule-4\"/>."
+
+#: en_US/style.xml:1824(title)
+msgid "Precision of Language"
+msgstr "Precisione del Linguaggio"
+
+#: en_US/style.xml:1825(para)
+msgid ""
+"Use precise words for actions users should take. Do not instruct users to "
+"\"go\" to a selection, or \"find\" a menu."
+msgstr ""
+"Usare parole precise per le azioni che gli utenti devono compiere. Non "
+"istruire l'utente con \"vai\" ad una sezione, o \"trova\" un menu."
+
+#: en_US/style.xml:1830(title)
+msgid "Incorrect: Imprecise wording"
+msgstr "Non corretto: Parole imprecise"
+
+#: en_US/style.xml:1833(para)
+msgid ""
+"Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+"Andare al <guimenu>Menu Principale</guimenu> -> <guimenuitem>Foobar</"
+"guimenuitem>"
+
+#: en_US/style.xml:1839(para)
+msgid "Find the option labeled <guilabel>Search</guilabel>"
+msgstr "Trovare l'opzione chiamata <guilabel>Trova</guilabel>"
+
+#: en_US/style.xml:1846(title)
+msgid "Correct: Precise wording"
+msgstr "Corretto: Parole precise"
+
+#: en_US/style.xml:1849(para)
+msgid ""
+"From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+"Dal <guimenu>Menu Principale</guimenu>, selezionare <guimenuitem>Foobar</"
+"guimenuitem>"
+
+#: en_US/style.xml:1855(para)
+msgid "Select the <guilabel>Search</guilabel> option"
+msgstr "Selezionare l'opzione <guilabel>Cerca</guilabel>"
+
+#: en_US/style.xml:1862(title)
+msgid "Do Not Discriminate Against Non-GUI Users"
+msgstr "Non discriminare chi non usa le GUI"
+
+#: en_US/style.xml:1863(para)
+msgid ""
+"If you are writing about a GUI-only application, you may use \"click\" "
+"freely. If you are writing about an application that has a text-mode "
+"interface, use \"select\" instead as shown above."
+msgstr ""
+"Se si sta scrivendo di una applicazione solamente grafica (GUI), si dovrebbe "
+"usare \"click\". Se si sta scrivendo di una applicazione che ha una "
+"interfaccia testuale, usare \"selezionare\" invece di come mostrato sopra."
+
+#: en_US/style.xml:1874(title)
+msgid "DocBook Tips"
+msgstr "Suggerimenti per DocBook"
+
+#: en_US/style.xml:1875(para)
+msgid ""
+"This section contains tips on how to use DocBook tags more effectively in "
+"your documentation."
+msgstr ""
+"Questa sezione contiene suggerimenti su come usare i tag DocBook più "
+"efficacemente nella documentazione."
+
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:268(title)
+msgid "Admonitions"
+msgstr "Ammonizioni"
+
+#: en_US/style.xml:1882(para)
+msgid ""
+"Avoid overuse of admonitions. Keep admonitions short and effective by using "
+"only the most important material inside the admonition. Move any background "
+"material required to explain the admonition statements outside the "
+"admonition. Use a short but descriptive title for an admonition. Use title "
+"case for the admonition title."
+msgstr ""
+"Evitare l'uso eccessivo di ammonizioni. Mantenere le ammonizioni brevi ed "
+"efficaci usando solo le parti più importanti nell'ammonizione. Spostare qualsiasi materiale "
+"utile a spiegare l'ammonizione fuori dell'avvertimento. Usare un titolo "
+"corto ma descrittivo dell'ammonizione. Usare caratteri maiuscoli per il "
+"titolo dell'ammonizione."
+
+#: en_US/style.xml:1891(title)
+msgid "Incorrect: Lengthy admonition"
+msgstr "Non corretto: Avvertimenti prolissi"
+
+#: en_US/style.xml:1894(title)
+msgid "Use <command>sfdisk</command> to check input"
+msgstr "Usare <command>sfdisk</command> per controllare l'input"
+
+#: en_US/style.xml:1895(para)
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+"Il comando <command>sfdisk</command> accetta un file di script come input "
+"standard per impostare le partizioni dell'hard disk. A volte "
+"<command>sfdisk</command> rifiuterà semplicemente un file di input "
+"scorretto. In altri casi, userà lo stesso input, scrivendo una tavola di "
+"partizione scorretta sul disco. Usare sempre il comando <command>sfdisk -n</"
+"command> per controllare il file di input prima di scrivere sul disco."
+
+#: en_US/style.xml:1909(title)
+msgid "Correct: Brief admonition"
+msgstr "Corretto: Ammonizioni brevi"
+
+#: en_US/style.xml:1917(title)
+msgid "Check Input"
+msgstr "Controllare l'input"
+
+#: en_US/style.xml:1918(para)
+msgid ""
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+"Usare sempre il comando <command>sfdisk -n</command> per controllare il file "
+"di input prima di scrivere sul disco."
+
+#: en_US/style.xml:1910(para)
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"<placeholder-1/>"
+msgstr ""
+"Il comando <command>sfdisk</command> accetta un file di script come input "
+"standard per impostare le partizioni dell'hard disk. A volte "
+"<command>sfdisk</command> rifiuterà semplicemente un file di input "
+"scorretto. In altri casi, userà lo stesso input, scrivendo una tavola di "
+"partizione scorretta sul disco. <placeholder-1/>"
+
+#: en_US/style.xml:1925(para)
+msgid ""
+"Avoid punctuation in titles for sections or admonitions, except for commas "
+"only where demanded. Use a title that says something about the admonition "
+"comment, such as \"Reboot Required,\" instead of simply using the admonition "
+"type for a title (\"Note\")."
+msgstr ""
+"Evitare la punteggiatura nei titoli di sezioni o ammonizioni, fatta "
+"eccezione per le virgole dove richiesto. Utilizzare un titolo che dice "
+"qualcosa circa l'ammonizione, come \"Riavvio richiesto\", invece di un "
+"semplice monito per un titolo (\"Nota\")."
+
+#: en_US/style.xml:1932(para)
+msgid "Follow the capitalization rules for headings in the title of an admonition."
+msgstr ""
+"Seguire le regole di capitalizzazione per le intestazioni nei titoli delle "
+"ammonizioni."
+
+#: en_US/style.xml:1939(title)
+msgid "The <sgmltag class=\"starttag\">replaceable</sgmltag> Tag"
+msgstr "Il tag <sgmltag class=\"starttag\">replaceable</sgmltag>"
+
+#: en_US/style.xml:1941(para)
+msgid ""
+"If your documentation formally states a specific value will be used as a "
+"convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> "
+"tag in your text or examples."
+msgstr ""
+"Se la documentazione afferma formalmente uno specifico valore verrà "
+"utilizzato come una convenzione, non utilizzare il tag<sgmltag class="
+"\"starttag\">replaceable</ sgmltag> nel testo o negli esempi."
+
+#: en_US/style.xml:1950(title)
+msgid "XML Entities"
+msgstr "Entità XML"
+
+#: en_US/style.xml:1951(para)
+msgid ""
+"Use the entities provided by the Fedora Documentation Project. These "
+"entities are found in the <filename>common/</filename> folder in the "
+"<filename>fedora-docs</filename> distribution. (Refer also to <xref linkend="
+"\"ch-getting-files\"/>.) For instance, do not use abbreviations such as "
+"\"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" "
+"which produces the text \"Fedora 9.\""
+msgstr ""
+"Usare le entità fornite dal Progetto Documentazione Fedora. Queste entità si "
+"trovano nella cartella <filename>common/</filename> nella distribuzione "
+"<filename>fedora-docs</filename>. (Fare riferimento anche a <xref linkend=\"ch-"
+"getting-files\"/>). Per istanza, non usare abbreviazioni con \"FC2\". "
+"Invece, usare le entità predefinite \"&FC; &FCVER;,\" che produce il "
+"testo \"Fedora 9\"."
+
+#: en_US/writing-guidelines.xml:11(title)
+msgid "Fedora Documentation Guidelines"
+msgstr "Linee Guida alla Documentazione Fedora"
+
+#: en_US/writing-guidelines.xml:14(primary)
+#: en_US/writing-guidelines.xml:15(see)
+msgid "recursion"
+msgstr "ricorsioni"
+
+#: en_US/writing-guidelines.xml:19(primary)
+#: en_US/writing-guidelines.xml:26(secondary)
+msgid "RTFM"
+msgstr "RTFM"
+
+#: en_US/writing-guidelines.xml:20(secondary)
+msgid "read the fine manual"
+msgstr "leggere il manuale"
+
+#: en_US/writing-guidelines.xml:21(seealso)
+#: en_US/writing-guidelines.xml:25(primary)
+msgid "humor"
+msgstr "humor"
+
+#: en_US/writing-guidelines.xml:29(para)
+msgid ""
+"Please read this chapter carefully. This chapter describes the guidelines "
+"that must be followed such as naming conventions."
+msgstr ""
+"Leggere questo capitolo attentamente. Questo capitolo descrive le linee guida "
+"che devono essere seguite come convenzioni sui nomi."
+
+#: en_US/writing-guidelines.xml:32(para)
+msgid ""
+"This chapter only discusses tags used for documentation for the Fedora "
+"Project, not all available DocBook XML tags. For the complete list, refer to "
+"<ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr ""
+"Questo capitolo tratta solo i tag usati per la documentazione del Fedora "
+"Project, non tutti i tag disponibili per DocBook XML. Per una lista "
+"completa fare riferimento a <ulink url=\"http://www.docbook.org/tdg/en/html/"
+"docbook.html\"/>."
+
+#: en_US/writing-guidelines.xml:38(title)
+msgid "File Header"
+msgstr "Intestazione file"
+
+#: en_US/writing-guidelines.xml:40(title)
+msgid "XML Header"
+msgstr "Intestazione XML"
+
+#: en_US/writing-guidelines.xml:41(para)
+msgid ""
+"In accordance with good XML practices, the first line in any DocBook XML "
+"source files should identify the file as XML. Use the following line as the "
+"first line of any new XML file:"
+msgstr ""
+"In accordo con le buone pratiche di XML, la prima riga in ogni file sorgente "
+"DocBook XML dovrebbe individuare il file come XML. Utilizzare la seguente "
+"riga come la prima linea di ogni nuovo file XML:"
+
+#: en_US/writing-guidelines.xml:47(title)
+msgid "CVS Id Header"
+msgstr "Intestazione CVS Id"
+
+#: en_US/writing-guidelines.xml:48(para)
+msgid ""
+"All the files must contain the CVS Id header. Use the following line as the "
+"second line of any new XML file:"
+msgstr ""
+"Tutti i file devono contenere l'intestazione CVS Id. Utilizzare la seguente "
+"riga come seconda riga di ogni nuovo file XML:"
+
+#: en_US/writing-guidelines.xml:51(para)
+msgid ""
+"Any time the file is committed to CVS, the line is updated automatically to "
+"include information about the file. For example:"
+msgstr ""
+"Ogni volta che i file sono inviati in CVS, la linea è aggiornata "
+"automaticamente per includere le informazioni sul file. Per esempio:"
+
+#: en_US/writing-guidelines.xml:58(title)
+msgid "ID Naming Conventions"
+msgstr "Convenzione ID Nomi"
+
+#: en_US/writing-guidelines.xml:61(primary)
+#: en_US/writing-guidelines.xml:74(primary)
+#: en_US/writing-guidelines.xml:275(primary)
+#: en_US/writing-guidelines.xml:280(primary)
+#: en_US/writing-guidelines.xml:285(primary)
+#: en_US/writing-guidelines.xml:290(primary)
+#: en_US/writing-guidelines.xml:295(primary)
+#: en_US/writing-guidelines.xml:300(primary)
+#: en_US/writing-guidelines.xml:306(primary)
+#: en_US/writing-guidelines.xml:312(primary)
+#: en_US/writing-guidelines.xml:318(primary)
+#: en_US/writing-guidelines.xml:324(primary)
+#: en_US/writing-guidelines.xml:350(primary)
+#: en_US/writing-guidelines.xml:355(primary)
+#: en_US/writing-guidelines.xml:360(primary)
+#: en_US/writing-guidelines.xml:365(primary)
+#: en_US/writing-guidelines.xml:370(primary)
+msgid "XML tags"
+msgstr "Tag XML"
+
+#: en_US/writing-guidelines.xml:62(secondary)
+#: en_US/writing-guidelines.xml:66(primary)
+#: en_US/writing-guidelines.xml:79(primary)
+msgid "naming conventions"
+msgstr "convenzioni dei nomi"
+
+#: en_US/writing-guidelines.xml:69(para)
+msgid ""
+"This section explains the ID naming convention. IDs are unique identifiers "
+"that allow DocBook XML to cross-reference a section, chapter, or other "
+"element."
+msgstr ""
+"Questa sezione spiega la convenzione dei nomi ID. Gli ID sono degli "
+"identificatori univoci che permettono a DocBook XML di referenziare sezioni, "
+"capitoli o altri elementi."
+
+#: en_US/writing-guidelines.xml:75(secondary)
+#: en_US/writing-guidelines.xml:80(secondary)
+msgid "rules for defining an ID"
+msgstr "regole per definire un ID"
+
+#: en_US/writing-guidelines.xml:83(para)
+msgid "The following general rules apply to IDs:"
+msgstr "Le seguenti regole generali sono applicate agli ID:"
+
+#: en_US/writing-guidelines.xml:87(para)
+msgid "Keep an ID as short and simple as possible."
+msgstr "Tenere un ID il più corto e semplice possibile."
+
+#: en_US/writing-guidelines.xml:90(para)
+msgid ""
+"Start the ID with the special short two-character label. This makes URLs and "
+"other references to this ID human readable, by self-identifying the XML "
+"container type."
+msgstr ""
+"Iniziare l'ID con una ettichettatura speciale breve di due caratteri. Questo "
+"rende gli URL e altri riferimenti a questo ID leggibili, con auto-"
+"individuazione del tipo di contenitore XML."
+
+#: en_US/writing-guidelines.xml:96(para)
+msgid ""
+"<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used "
+"properly."
+msgstr ""
+"<xref linkend=\"ex-id-usage\"/> dimostra alcuni esempi di attributi ID "
+"usati correttamente."
+
+#: en_US/writing-guidelines.xml:102(title)
+msgid "Proper ID Usage"
+msgstr "Uso proprio dell'ID"
+
+#: en_US/writing-guidelines.xml:111(title)
+msgid "Two-Character Naming Conventions"
+msgstr "Due caratteri di Convenzione nomi"
+
+#: en_US/writing-guidelines.xml:112(segtitle)
+msgid "Tag"
+msgstr "Tag"
+
+#: en_US/writing-guidelines.xml:113(segtitle)
+msgid "Prefix"
+msgstr "Prefisso"
+
+#: en_US/writing-guidelines.xml:115(sgmltag)
+msgid "preface"
+msgstr "prefazione"
+
+#: en_US/writing-guidelines.xml:116(literal)
+msgid "pr-"
+msgstr "pr-"
+
+#: en_US/writing-guidelines.xml:119(sgmltag)
+msgid "chapter"
+msgstr "capitolo"
+
+#: en_US/writing-guidelines.xml:120(literal)
+msgid "ch-"
+msgstr "ch-"
+
+#: en_US/writing-guidelines.xml:123(sgmltag)
+msgid "section"
+msgstr "sezione"
+
+#: en_US/writing-guidelines.xml:124(literal)
+msgid "sn-"
+msgstr "sn-"
+
+#: en_US/writing-guidelines.xml:127(sgmltag)
+msgid "figure"
+msgstr "figura"
+
+#: en_US/writing-guidelines.xml:128(literal)
+msgid "fig-"
+msgstr "fig-"
+
+#: en_US/writing-guidelines.xml:131(sgmltag)
+#: en_US/writing-guidelines.xml:235(sgmltag)
+msgid "table"
+msgstr "tabella"
+
+#: en_US/writing-guidelines.xml:132(literal)
+msgid "tb-"
+msgstr "tb-"
+
+#: en_US/writing-guidelines.xml:135(sgmltag)
+msgid "appendix"
+msgstr "appendice"
+
+#: en_US/writing-guidelines.xml:136(literal)
+msgid "ap-"
+msgstr "ap-"
+
+#: en_US/writing-guidelines.xml:139(sgmltag)
+msgid "part"
+msgstr "parte"
+
+#: en_US/writing-guidelines.xml:140(literal)
+msgid "pt-"
+msgstr "pt-"
+
+#: en_US/writing-guidelines.xml:143(sgmltag)
+msgid "example"
+msgstr "esempio"
+
+#: en_US/writing-guidelines.xml:144(literal)
+msgid "ex-"
+msgstr "ex-"
+
+#: en_US/writing-guidelines.xml:148(para)
+msgid ""
+"Use the title of the item as the ID. Make your titles unique within a "
+"document to prevent conflicts. For example:"
+msgstr ""
+"Usare il titolo dell'oggetto come ID. Rendere i propri titoli unici "
+"all'interno di un documento per la prevenzione dei conflitti. Ad esempio:"
+
+#: en_US/writing-guidelines.xml:157(title)
+msgid "XML Tags"
+msgstr "Tag XML"
+
+#: en_US/writing-guidelines.xml:159(primary)
+msgid "xml tags"
+msgstr "tag xml"
+
+#: en_US/writing-guidelines.xml:160(secondary)
+msgid "caveats"
+msgstr "avvertimenti"
+
+#: en_US/writing-guidelines.xml:163(para)
+msgid ""
+"It is very important that you remember the caveats in this section. These "
+"are learned suggestions or rules that make your XML experience better."
+msgstr ""
+"E' molto importante ricordare gli ammonimenti in questa sezione. Questi sono "
+"suggerimenti o regole che migliorano l'esperienza con XML."
+
+#: en_US/writing-guidelines.xml:171(term)
+msgid "Do Not Use Trademark Entities"
+msgstr "Non usare entità di marchi"
+
+#: en_US/writing-guidelines.xml:173(para)
+msgid ""
+"Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+"\"genentity\">reg</sgmltag> because the do not produce HTML output that "
+"works for all charsets. The HTML output produces by these entities are "
+"declared in the DTD and cannot be changed via the stylesheet."
+msgstr ""
+"Non usare entità di marchi <sgmltag class=\"genentity\">trade</sgmltag>, "
+"<sgmltag class=\"genentity\">copy</sgmltag> o <sgmltag class=\"genentity"
+"\">reg</sgmltag> perchè non produce un output HTML che lavora con tutti i "
+"tipi di caratteri. Gli output HTML prodotti da queste entità sono dichiarati "
+"nel DTD e non possono essere cambiati con i fogli di stile."
+
+#: en_US/writing-guidelines.xml:181(para)
+msgid ""
+"Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes "
+"as follows:"
+msgstr ""
+"Invece, usare i tag <sgmltag>trademark</sgmltag> e le classi associate come "
+"segue:"
+
+#: en_US/writing-guidelines.xml:184(segtitle)
+msgid "DocBook XML source"
+msgstr "Sorgente DocBook XML"
+
+#: en_US/writing-guidelines.xml:185(segtitle)
+msgid "Rendered content"
+msgstr "Contenuto reso"
+
+#: en_US/writing-guidelines.xml:189(trademark)
+msgid "trademark symbol after me"
+msgstr "simbolo marchio successivo"
+
+#: en_US/writing-guidelines.xml:196(trademark)
+msgid "registered trademark symbol after me"
+msgstr "simbolo marchio registrato successivo"
+
+#: en_US/writing-guidelines.xml:202(trademark)
+msgid "copyright symbol after me"
+msgstr "simbolo copyright successivo"
+
+#: en_US/writing-guidelines.xml:209(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr "Contenuto all'interno dei tag <sgmltag>para</sgmltag>"
+
+#: en_US/writing-guidelines.xml:211(para)
+msgid ""
+"In general, use <sgmltag>para</sgmltag> tags around anything other than a "
+"simple paragraph. Doing so will create additional white space within the "
+"text itself in the PDF version."
+msgstr ""
+"In generale, usare i tag <sgmltag>para</sgmltag> solo per i semplici "
+"paragrafi. Facendo questo si creeranno degli spazi bianchi nel testo nelle "
+"versioni in PDF."
+
+#: en_US/writing-guidelines.xml:216(para)
+msgid ""
+"Specifically, do not use <sgmltag>para</sgmltag> tags around the following "
+"(or, to put this another way, do not embed the following within <sgmltag "
+"class=\"element\">para</sgmltag> elements):"
+msgstr ""
+"Specialmente, non usare i tag <sgmltag>para</sgmltag> nelle seguenti situazioni "
+"(o, per metterla in un altro modo, non incorporare con gli elementi <sgmltag "
+"class=\"element\">para</sgmltag>):"
+
+#: en_US/writing-guidelines.xml:223(sgmltag)
+msgid "screen"
+msgstr "schermo"
+
+#: en_US/writing-guidelines.xml:226(sgmltag)
+msgid "itemizedlist"
+msgstr "liste dettagliate"
+
+#: en_US/writing-guidelines.xml:229(sgmltag)
+msgid "orderedlist"
+msgstr "liste ordinate"
+
+#: en_US/writing-guidelines.xml:232(sgmltag)
+msgid "variablelist"
+msgstr "liste variabili"
+
+#: en_US/writing-guidelines.xml:241(term)
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag>listitem</sgmltag> tags"
+msgstr ""
+"Contenuto all'interno di elementi <sgmltag class=\"element\">para</sgmltag> "
+"con tag <sgmltag>listitem</sgmltag>"
+
+#: en_US/writing-guidelines.xml:244(para)
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</"
+"emphasis> start immediately after the beginning <sgmltag class=\"starttag"
+"\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr ""
+"I contenuti all'interno di elementi <sgmltag class=\"element\">para</sgmltag> "
+"con <sgmltag class=\"element\">listitem</sgmltag> <emphasis>devono</"
+"emphasis> iniziare immediatamente dopo l'inizio del tag <sgmltag class="
+"\"starttag\">para</sgmltag> per evitare spazi bianchi in più nella versione "
+"PDF."
+
+#: en_US/writing-guidelines.xml:252(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr "Contenuto all'interno dei tag <sgmltag>screen</sgmltag>"
+
+#: en_US/writing-guidelines.xml:254(para)
+msgid ""
+"The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag"
+"\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis> be flush left in the XML file; otherwise, the "
+"extraneous whitespace will appear in the HTML version."
+msgstr ""
+"Il contenuto all'interno dei tag <sgmltag>screen</sgmltag> (<sgmltag class="
+"\"starttag\">screen</sgmltag> o <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>devono</emphasis> essere allineati a sinistra nel file XML, "
+"altrimenti spazi bianchi estranei verranno visualizzati nella versione HTML."
+
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:301(secondary)
+#: en_US/writing-guidelines.xml:307(secondary)
+#: en_US/writing-guidelines.xml:313(secondary)
+#: en_US/writing-guidelines.xml:319(secondary)
+#: en_US/writing-guidelines.xml:325(secondary)
+msgid "admonitions"
+msgstr "ammonizioni"
+
+#: en_US/writing-guidelines.xml:276(secondary)
+#: en_US/writing-guidelines.xml:302(tertiary)
+#: en_US/writing-guidelines.xml:371(secondary)
+msgid "warning"
+msgstr "warning"
+
+#: en_US/writing-guidelines.xml:281(secondary)
+#: en_US/writing-guidelines.xml:308(tertiary)
+#: en_US/writing-guidelines.xml:356(secondary)
+msgid "tip"
+msgstr "tip"
+
+#: en_US/writing-guidelines.xml:286(secondary)
+#: en_US/writing-guidelines.xml:314(tertiary)
+#: en_US/writing-guidelines.xml:351(secondary)
+msgid "note"
+msgstr "note"
+
+#: en_US/writing-guidelines.xml:291(secondary)
+#: en_US/writing-guidelines.xml:320(tertiary)
+#: en_US/writing-guidelines.xml:361(secondary)
+msgid "caution"
+msgstr "caution"
+
+#: en_US/writing-guidelines.xml:296(secondary)
+#: en_US/writing-guidelines.xml:326(tertiary)
+#: en_US/writing-guidelines.xml:366(secondary)
+msgid "important"
+msgstr "important"
+
+#: en_US/writing-guidelines.xml:329(para)
+msgid ""
+"There are five types of admonitions in DocBook: <sgmltag class=\"element"
+"\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, "
+"<sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</"
+"sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the "
+"admonitions have the same structure: an optional <sgmltag class=\"element"
+"\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD "
+"does not impose any specific semantics on the individual admonitions. For "
+"example, DocBook does not mandate that a <sgmltag class=\"element\">warning</"
+"sgmltag> is reserved for cases where bodily harm can result."
+msgstr ""
+"Ci sono cinque tipi di ammonizioni in DocBook: <sgmltag class=\"element"
+"\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, "
+"<sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</"
+"sgmltag>, e <sgmltag class=\"element\">warning</sgmltag>. Tutte le "
+"ammonizioni hanno la stessa struttura: un elemento <sgmltag class=\"element"
+"\">title</sgmltag> opzionale seguito dagli elementi paragrafi. Il DocBook "
+"DTD non impone una specifica semantica sulle singole ammonizioni. Per "
+"esempio, DocBook non impone che <sgmltag class=\"element\">warning</sgmltag> "
+"sia riservato a casi che possano provocare danni."
+
+#: en_US/writing-guidelines.xml:343(title)
+msgid ""
+"Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class="
+"\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, "
+"<sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element"
+"\">warning</sgmltag>"
+msgstr ""
+"Crezione di un <sgmltag class=\"element\">note</sgmltag>, <sgmltag class="
+"\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, "
+"<sgmltag class=\"element\">important</sgmltag>, o <sgmltag class=\"element"
+"\">warning</sgmltag>"
+
+#: en_US/writing-guidelines.xml:374(para)
+msgid ""
+"There are several ways to bring attention to text within a document. A "
+"<emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to "
+"bring additional information to the users' attention. A <emphasis><sgmltag "
+"class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful "
+"information or another way to do something. A <emphasis><sgmltag class="
+"\"element\">caution</sgmltag></emphasis> is used to show the user they must "
+"be careful when attempting a certain step. An <emphasis><sgmltag class="
+"\"element\">important</sgmltag></emphasis> tag set can be used to show the "
+"user a piece of information that should not be overlooked. While this "
+"information may not change anything the user is doing, it should show the "
+"user that this piece of information could be vital. A <emphasis><sgmltag "
+"class=\"element\">warning</sgmltag></emphasis> is used to show the reader "
+"that their current setup will change or be altered, such as files being "
+"removed, and they should not choose this operation unless they are alright "
+"with the consequences."
+msgstr ""
+"Ci sono diversi modi per portare attenzione al testo di un documento. Una "
+"<emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> viene usata per "
+"dare maggiori informazioni all'attenzione degli utenti. Un "
+"<emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> viene usato per "
+"mostrare all'utente informazioni utili o un'altro modo per fare qualcosa. "
+"Un <emphasis><sgmltag class=\"element\">caution</sgmltag></emphasis> viene "
+"usato per mostrare all'utente che deve stare attento nel compiere una determinata "
+"operazione. Un tag <emphasis><sgmltag class=\"element\">important</sgmltag></"
+"emphasis> può essere usato per mostrare all'utente un pezzo di informazione "
+"che non deve essere sorvolato. Questa informazione può non "
+"cambiare niente in ciò che fa l'utente, poichè essa deve mostrare all'utente "
+"che questo pezzo di informazione può essere vitale. Un "
+"<emphasis><sgmltag class=\"element\">warning</sgmltag></emphasis> viene usato "
+"per mostrare al lettore che l'impostazione attuale può cambiare o "
+"può essere alterata, come la rimozione di un file, e non deve scegliere questa "
+"operazione a meno che non sia d'accordo con le conseguenze."
+
+#: en_US/writing-guidelines.xml:394(para)
+msgid ""
+"The following lines of code show the basic setup for each case mentioned "
+"above, along with its appearance in HTML."
+msgstr ""
+"Le seguenti righe di codice mostrano l'installazione base per ogni caso "
+"menzionato sopra, insieme con il suo aspetto in HTML."
+
+#: en_US/writing-guidelines.xml:403(title) en_US/emacs.xml:257(title)
+#: en_US/emacs.xml:562(title) en_US/emacs-nxml.xml:160(title)
+msgid "Note"
+msgstr "Note"
+
+#: en_US/writing-guidelines.xml:404(para)
+#: en_US/writing-guidelines.xml:424(para)
+#: en_US/writing-guidelines.xml:434(para)
+#: en_US/writing-guidelines.xml:444(para)
+msgid "Body of text goes here."
+msgstr "Corpo del testo va qui."
+
+#: en_US/writing-guidelines.xml:413(title) en_US/emacs-nxml.xml:114(title)
+msgid "Tip"
+msgstr "Tip"
+
+#: en_US/writing-guidelines.xml:414(para)
+msgid "Body of text goes here"
+msgstr "Corpo del testo va qui."
+
+#: en_US/writing-guidelines.xml:423(title)
+msgid "Caution"
+msgstr "Caution"
+
+#: en_US/writing-guidelines.xml:433(title) en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr "Important"
+
+#: en_US/writing-guidelines.xml:443(title)
+msgid "Warning"
+msgstr "Warning"
+
+#: en_US/writing-guidelines.xml:451(title)
+msgid "Screenshots"
+msgstr "Screenshots"
+
+#: en_US/writing-guidelines.xml:454(primary)
+#: en_US/writing-guidelines.xml:459(see) en_US/writing-guidelines.xml:463(see)
+msgid "screenshots"
+msgstr "screenshots"
+
+#: en_US/writing-guidelines.xml:455(secondary)
+msgid "how to take"
+msgstr "come prendere"
+
+#: en_US/writing-guidelines.xml:458(primary)
+msgid "screen captures"
+msgstr "catturare lo schermo"
+
+#: en_US/writing-guidelines.xml:462(primary)
+msgid "screen grabs"
+msgstr "afferrare lo schermo"
+
+#: en_US/writing-guidelines.xml:466(para)
+msgid ""
+"Screenshots are illustrations that show the state of a display the user may "
+"encounter. Screenshots can be either graphical or textual. However, "
+"screenshots use a great deal of space in a text document to convey "
+"relatively small amounts of information. The same space in the document can "
+"hold a greater amount of more descriptive and helpful information. "
+"Therefore, authors should avoid screenshots whenever possible in favor of "
+"descriptive text."
+msgstr ""
+"Gli screenshot sono delle illustrazioni che mostrano lo stato di una "
+"schermata che l'utente può incontrare. Gli screenshot possono essere sia "
+"grafici che testuali. Come sempre, gli screenshot usano molto spazio nel "
+"testo di un documento per trasmettere relativamente piccole quantità di "
+"informazioni. Lo stesso spazio in un documento può contenere una grande "
+"quantità di informazioni molto più descrittive e utili. Perciò, gli autori "
+"dovrebbero evitare gli screenshot quando possibile in favore di descrizioni "
+"testuali."
+
+#: en_US/writing-guidelines.xml:474(para)
+msgid ""
+"One of the isolated instances in which screenshots are useful is to "
+"demonstrate a physical screen layout that is unfamiliar to a reader. "
+"<emphasis>This does not mean that illustrations of dialog boxes are good "
+"uses of screenshots.</emphasis> On the contrary, dialogs are simply "
+"instances of a user interface element with which a reader is already "
+"familiar. An annotated diagram in certain cases, however, explains to the "
+"reader where to find functional landmarks on the screen such as menu bars."
+msgstr ""
+"Uno dei pochi casi in cui gli screenshot sono utili è per dimostrare la "
+"struttura fisica di una schermata che non è familiare al lettore. "
+"<emphasis>Questo non significa che l'illustrazione di finestre di dialogo "
+"sia un buon uso degli screenshot.</emphasis> Al contrario, queste finestre sono "
+"semplici istanze di una interfaccia utente con cui il lettore è già "
+"familiare. Un diagramma annotato in certi casi, come sempre, espone al "
+"lettore dove trovare funzioni di riferimento sullo schermo come le barre dei "
+"menu."
+
+#: en_US/writing-guidelines.xml:482(para)
+msgid ""
+"The steps for taking a graphical screenshot illustrate how using text to "
+"describe a procedure is more concise than a series of screenshots."
+msgstr ""
+"I passaggi per prendere una schermata grafica illustra come usare il testo "
+"per descrivere una procedura più concisa rispetto ad una serie di schermate."
+
+#: en_US/writing-guidelines.xml:487(term)
+msgid "Graphical Screenshot"
+msgstr "Screenshot Grafico"
+
+#: en_US/writing-guidelines.xml:491(para)
+msgid ""
+"Create a new user account to make screenshots. The new account uses the "
+"distribution default theme, fonts, and element sizes. The resulting "
+"screenshot has an appearance familiar to the largest number of readers, and "
+"makes Fedora Documentation Project documents consistent."
+msgstr ""
+"Creare un nuovo account utente per fare gli screenshot. Il nuovo account usa i "
+"temi, i font e le dimensioni degli elementi di base della distribuzione. La schermata "
+"risultate avrà una apparenza familiare con la maggior parte dei "
+"lettori e da consistenza al Fedora Documentation Project."
+
+#: en_US/writing-guidelines.xml:498(para)
+msgid ""
+"Before taking the screenshot, if possible, resize the targeted GUI element"
+"(s) to the smallest possible size. The target image should be 500 pixels "
+"wide or less. If the screenshot includes more than one GUI element, you may "
+"need to resize the screenshot in a following step."
+msgstr ""
+"Prima di catturare una schermata, se possibile, ridimensionare le dimensioni "
+"della GUI alla dimenzione più piccola possibile. Le immagini finali "
+"dovrebbero essere più o meno di 500 pixel. Se la schermata include più di "
+"una GUI, si dovrebbe ridimensionare la schermata come nel passaggio "
+"sucessivo."
+
+#: en_US/writing-guidelines.xml:506(para)
+msgid ""
+"To take the screenshot, select the GUI element with the mouse to bring it to "
+"the forefront, or otherwise arrange the elements. Press "
+"<keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to "
+"capture a single GUI window. For capturing the entire desktop use "
+"<keycap>Print Screen</keycap>. If the shot includes multiple elements "
+"grouped closely together, crop the resulting PNG format image in "
+"<application>The GIMP</application>."
+msgstr ""
+"Per catturare la schermata, selezionare l'elemento GUI con il mouse per "
+"metterlo in primo piano, o sistemare gli altri elementi. Premere "
+"<keycombo><keycap>Alt</keycap><keycap>Stamp</keycap></keycombo> per "
+"catturare una singola finestra GUI. Per catturare l'intero desktop usare "
+"<keycap>Stamp</keycap>. Se la schermata include più elementi "
+"raggruppati assieme, ritagliare il file PNG così ottenuto con "
+"<application>The GIMP</application>."
+
+#: en_US/writing-guidelines.xml:518(para)
+msgid ""
+"If necessary, resize the image using <application>The GIMP</application>. "
+"Open the image, then right-click on it and choose "
+"<menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</"
+"guimenuitem></menuchoice>. With the chain symbol intact, set the "
+"<guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click "
+"<guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</"
+"guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the "
+"image before converting it."
+msgstr ""
+"Se necessario, ridimensionare l'immagine usanto <application>The GIMP</"
+"application>. Aprire l'immagine, poi click-tasto destro su di esso e "
+"scegliere <menuchoice><guimenu>Immagine</guimenu><guimenuitem>Scala Immagine...</"
+"guimenuitem></menuchoice>. Con il simbolo catena premuto, impostare "
+"<guilabel>Larghezza</guilabel> a <guilabel>500 px</guilabel> e fare click su "
+"<guibutton>OK</guibutton>. Selezionare <menuchoice><guimenu>File</"
+"guimenu><guimenuitem>Salva</guimenuitem></menuchoice> per salvare i "
+"cambiamenti dell'immagine prima di convertirla."
+
+#: en_US/writing-guidelines.xml:534(para)
+msgid ""
+"With the image open in <application>The GIMP</application>, right-click the "
+"image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As..."
+"</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, "
+"select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</"
+"guibutton>. Allow flattening of the image by clicking <guibutton>Export</"
+"guibutton>."
+msgstr ""
+"Con l'immagine aperta in <application>The GIMP</application>, fare click con il "
+"tasto destro sull'immagine e selezionare <menuchoice><guimenu>File</"
+"guimenu><guimenuitem>Salva come...</guimenuitem></menuchoice>. Sotto "
+"<guimenu>Seleziona tipo di file:</guimenu>, selezionare "
+"<guimenuitem>Documento PostScript</guimenuitem>, poi click su <guibutton>OK</"
+"guibutton>. Permettere l'appiattimento dell'immagine facendo click su "
+"<guibutton>Esporta</guibutton>."
+
+#: en_US/writing-guidelines.xml:545(para)
+msgid ""
+"A <guilabel>Save as PostScript</guilabel> window appears. Select "
+"<guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</"
+"guibutton>."
+msgstr ""
+"Apparirà una finestra per <guilabel>Salva come PostScript</guilabel>. Selezionare "
+"<guilabel>PostScript Incapsulato</guilabel> e fare click su <guibutton>OK</"
+"guibutton>."
+
+#: en_US/writing-guidelines.xml:559(term)
+msgid "Text Screenshot"
+msgstr "Screenshot testuale"
+
+#: en_US/writing-guidelines.xml:561(para)
+msgid ""
+"Textual screen information is also useful for readers. Follow these "
+"guidelines for textual screenshots:"
+msgstr ""
+"Le informazioni testuali sono anche utili al lettore. Seguire queste linee "
+"guida per uno screenshot testuale:"
+
+#: en_US/writing-guidelines.xml:565(para)
+msgid ""
+"If a graphical screenshot illustrates a function, and the textual mode has "
+"identical functions, do not include both, unless omitting either would make "
+"your description unclear."
+msgstr ""
+"Se uno screenshot grafico illustra una funzione e la modalità testuale ha la "
+"stessa identica funzione, non metterle entrambe, a meno che omettendone una "
+"si rende la descrizione poco chiara."
+
+#: en_US/writing-guidelines.xml:571(para)
+msgid ""
+"Make the information generic over specific, and omit any username and "
+"machine information if possible. Do not include the shell prompt unless it "
+"is vital to the demonstration."
+msgstr ""
+"Rendere l'informazione generica più che specifica e omettere qualsiasi nome "
+"utente e informazioni sulla macchina se possibile. Non includere il prompt "
+"della shell a meno che non sia vitale."
+
+#: en_US/writing-guidelines.xml:577(para)
+msgid "Separate what the user types from sample command output."
+msgstr "Separare ciò che l'utente digita dal semplice output del comando."
+
+#: en_US/writing-guidelines.xml:581(para)
+msgid ""
+"When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a "
+"procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show "
+"what the user types, and use <sgmltag class=\"element\">computeroutput</"
+"sgmltag> tags to show the resulting output."
+msgstr ""
+"Quando si usa <sgmltag class=\"element\">screen</sgmltag> per dimostrare una "
+"procedura, usare i tag <sgmltag class=\"element\">userinput</sgmltag> per "
+"mostrare cosa digitano gli utenti e usare i tag <sgmltag class=\"element"
+"\">computeroutput</sgmltag> per mostrare i risultati."
+
+#: en_US/writing-guidelines.xml:589(para)
+msgid ""
+"<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual "
+"screenshot usage."
+msgstr ""
+"<xref linkend=\"ex-text-screenshot-good\"/> è un esempio di uso di "
+"screenshot testuale."
+
+#: en_US/writing-guidelines.xml:594(title)
+msgid "Correct Textual Screenshot (XML Source and HTML)"
+msgstr "Screenshot testuale Corretto (Sorgente XML e HTML)"
+
+#: en_US/writing-guidelines.xml:607(para)
+msgid "To find all the currently active ssh sessions, execute the following command:"
+msgstr ""
+"Per trovare tutte le sessioni ssh correntemente attive, eseguire il seguente "
+"comando:"
+
+#: en_US/writing-guidelines.xml:609(userinput)
+#, no-wrap
+msgid "ps ax | grep ssh"
+msgstr "ps ax | grep ssh"
+
+#: en_US/writing-guidelines.xml:611(para)
+msgid "Output appears similar to the following:"
+msgstr "L'output appare simile a quanto segue:"
+
+#: en_US/writing-guidelines.xml:613(computeroutput)
+#, no-wrap
+msgid ""
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh user@@host.example.com\n"
+" 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+msgstr ""
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh user@@host.example.com\n"
+" 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+
+#: en_US/writing-guidelines.xml:648(title)
+msgid "Previewing Your Work"
+msgstr "Anteprima del proprio lavoro"
+
+#: en_US/writing-guidelines.xml:649(para)
+msgid ""
+"The GNOME <application>Help</application> browser, also known as "
+"<command>yelp</command>, and the KDE <application>Khelp</application> "
+"documentation browser can render DocBook XML information as needed. Use "
+"these applications to preview your work if you prefer reading your work in a "
+"browser-like environment. Run the following command:"
+msgstr ""
+"Il browser GNOME per l'<application>Aiuto</application>, conosciuto anche "
+"come <command>yelp</command> e per KDE <application>Khelp</application> "
+"possono rendere le informazioni DocBook XML come necessarie. Usare queste "
+"applicazioni per l'anteprima del proprio lavoro se si preferisce leggere il "
+"lavoro in un ambiente simile ad un browser. Eseguire il seguente comando:"
+
+#: en_US/writing-guidelines.xml:656(para)
+msgid ""
+"Make sure to point the preferred help browser at the top parent file of your "
+"XML document. Once the document loads, you can add a bookmark for it for "
+"ease of use later."
+msgstr ""
+"Assicurarsi di puntare il l'help browser preferito all'inizio del file del "
+"proprio documento XML. Quando il documento è caricato si può aggiungere un "
+"segnalibro per una successiva migliore facilità d'uso."
+
+#: en_US/writing-guidelines.xml:660(title)
+msgid "Using Bookmarks"
+msgstr "Usare i Segnalibri"
+
+#: en_US/writing-guidelines.xml:661(para)
+msgid ""
+"Keeping your documents in the same place for every checkout session makes "
+"help browser bookmarks more effective."
+msgstr ""
+"Mantere la propria documentazione nello stesso posto per ogni sessione di "
+"controllo, permette ai segnalibri dell'help browser di essere più effettivi."
+
+#: en_US/writing-guidelines.xml:664(para)
+msgid ""
+"Once you have a bookmark stored, it will appear in the help browser at every "
+"use. You can now hit <keycap>F1</keycap> during any GUI session to launch "
+"the help browser. Then choose your bookmark from the menu to preview your "
+"document at any time."
+msgstr ""
+"Quando si ha un segnalibro salvato, esso apparirà nell'help browser ad ogni "
+"utilizzo. Si può premere <keycap>F1</keycap> durante ogni sessione della GUI "
+"per lanciare l'help browser. Poi scegliere il proprio segnalibro dal menu "
+"per l'anteprima del documento ad ogni momento."
+
+#: en_US/module-struct.xml:12(title)
+msgid "How Modules Work"
+msgstr "Come lavorano i Moduli"
+
+#: en_US/module-struct.xml:13(para)
+msgid ""
+"Documentation modules have a specific structure that enables the "
+"preconfigured tools to work correctly. Follow this structure exactly or you "
+"may have problems building your module. The Fedora Documentation Project "
+"build tools locate resources in the module and use them to build new output "
+"such as HTML or RPM packages."
+msgstr ""
+"I moduli di documentazione hanno una struttura specifica che permette "
+"a strumenti preconfigurati di lavorare correttamente. Seguire queste "
+"strutture o si possono incorrere in problemi di creazione dei moduli. Gli "
+"strumenti di creazione del Fedora Documentation Project individuano le "
+"risorse del modulo e li usano per creare nuovi output come un HTML o "
+"pacchetti RPM."
+
+#: en_US/module-struct.xml:19(title)
+msgid "Structure of a Module"
+msgstr "Struttura di un Modulo"
+
+#: en_US/module-struct.xml:20(para)
+msgid ""
+"<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example "
+"module, excluding any <filename class=\"directory\">CVS</filename> folders. "
+"Note that this example document does not have branches."
+msgstr ""
+"<xref linkend=\"ex-module-structure\"/> mostra una struttura di cartelle di un "
+"modulo di esempio, escludendo qualsiasi cartella <filename class=\"directory"
+"\">CVS</filename>. Notare che questo documento di esempio non ha branche."
+
+#: en_US/module-struct.xml:25(title)
+msgid "Example Module Structure"
+msgstr "Esempio di struttura di un Modulo"
+
+#: en_US/module-struct.xml:47(title)
+msgid "CVS Module Contents"
+msgstr "Contenuti Moduli CVS"
+
+#: en_US/module-struct.xml:48(segtitle)
+msgid "Component"
+msgstr "Componente"
+
+#: en_US/module-struct.xml:49(segtitle)
+msgid "Type"
+msgstr "Tipo"
+
+#: en_US/module-struct.xml:50(segtitle)
+msgid "Usage Notes"
+msgstr "Note d'uso"
+
+#: en_US/module-struct.xml:52(seg)
+msgid "Primary language directory"
+msgstr "Directory lingua primaria"
+
+#: en_US/module-struct.xml:53(seg) en_US/module-struct.xml:94(seg)
+#: en_US/module-struct.xml:101(seg)
+msgid "required"
+msgstr "richiesto"
+
+#: en_US/module-struct.xml:56(filename)
+#: en_US/module-struct.xml:181(systemitem)
+msgid "en_US"
+msgstr "en_US"
+
+#: en_US/module-struct.xml:60(firstterm)
+msgid "entities"
+msgstr "entità"
+
+#: en_US/module-struct.xml:61(para)
+msgid ""
+"Think of an XML entity as a predefined snippet of information. It can "
+"represent a chunk of XML source, or simply a word or character. If the "
+"information changes, it need be replaced only once, in the definition, to "
+"fix all usage."
+msgstr ""
+"Pensare ad una entità XML come una breve informazione predefinita. Può "
+"rappresentare un grosso pezzo di sorgente XML o semplicemente una parola o "
+"un carattere. Se le informazioni cambiano, è necessario fare la "
+"sostituzione solo una volta, nelle definizioni per risolvere tutte le occorrenze."
+
+#: en_US/module-struct.xml:54(seg)
+msgid ""
+"This is the only directory absolutely required. It is named for the original "
+"language of the document, such as <placeholder-1/> (US English). The primary "
+"language does not have to be US English; all languages are supported. This "
+"directory contains all the XML source for the actual document, as well as "
+"XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr ""
+"Questa è la sola cartella assolutamente necessaria. E' nominata per la "
+"lingua originale del documento, come <placeholder-1/> (US English). La prima "
+"lingua non deve essere per forza US English; sono supportate tutte le lingue. "
+"La cartella contiene tutto il sorgente XML per il documento "
+"attuale, come una sorgente XML per la documentazione specifica <placeholder-2/"
+"><placeholder-3/>."
+
+#: en_US/module-struct.xml:69(seg)
+msgid "Graphics directory"
+msgstr "cartella Graphics"
+
+#: en_US/module-struct.xml:70(seg) en_US/module-struct.xml:80(seg)
+msgid "optional"
+msgstr "opzionale"
+
+#: en_US/module-struct.xml:71(filename) en_US/module-struct.xml:75(filename)
+msgid "figs/"
+msgstr "figs/"
+
+#: en_US/module-struct.xml:71(seg)
+msgid ""
+"The <placeholder-1/> directory is an optional directory where graphics for "
+"the document should be stored. If graphics are screenshots that are "
+"particular to a language, the <placeholder-2/> directory can and should be "
+"stored in a language directory."
+msgstr ""
+"La directory <placeholder-1/> è una cartella opzionale dove dovrebbero "
+"essere salvate le grafiche per i documenti. Se le grafiche sono schermate per "
+"una lingua particolare, la cartella <placeholder-2/> può e dovrebbe essere "
+"salvata nella cartella della lingua."
+
+#: en_US/module-struct.xml:79(seg)
+msgid "Translation (PO) directory"
+msgstr "Tradurre directory (PO)"
+
+#: en_US/module-struct.xml:81(filename) en_US/module-struct.xml:87(filename)
+msgid "po/"
+msgstr "po/"
+
+#: en_US/module-struct.xml:83(acronym)
+msgid "PO"
+msgstr "PO"
+
+#: en_US/module-struct.xml:88(filename)
+msgid "LINGUAS"
+msgstr "LINGUAS"
+
+#: en_US/module-struct.xml:89(firstterm)
+msgid "locales"
+msgstr "locales"
+
+#: en_US/module-struct.xml:81(seg)
+msgid ""
+"The <placeholder-1/> directory contains specially formatted Portable Object, "
+"or <placeholder-2/>, files created and used by translators. The Fedora "
+"Documentation Project build tools use these files to create translated "
+"versions of documents. The translated documents are not stored in CVS; they "
+"are created as needed from these PO files. The <placeholder-3/> directory "
+"also contains the <placeholder-4/> file, which lists the active translation "
+"<placeholder-5/>, or languages."
+msgstr ""
+"La cartella <placeholder-1/> contiene degli speciali Portable Object "
+"formattati, o <placeholder-2/>, file creati e usati dai traduttori. Gli "
+"strumenti di creazione del Fedora Documentation Project usano questi file "
+"per creare versioni tradotte dei documenti. I documenti tradotti non sono "
+"immagazzinati in CVS; essi sono creati se necessari dai file PO. La "
+"cartella <placeholder-3/> contiene anche il file <placeholder-4/>, che "
+"elenca la traduzione attiva <placeholder-5/>, o i linguaggi."
+
+#: en_US/module-struct.xml:93(seg) en_US/module-struct.xml:95(filename)
+msgid "Makefile"
+msgstr "Makefile"
+
+#: en_US/module-struct.xml:95(seg)
+msgid ""
+"The <placeholder-1/> controls the build process. Its content is discussed in "
+"<xref linkend=\"ex-makefile\"/>."
+msgstr ""
+"Il <placeholder-1/> controlla il processo di creazione. Il suo contenuto è "
+"discusso in <xref linkend=\"ex-makefile\"/>."
+
+#: en_US/module-struct.xml:100(filename) en_US/module-struct.xml:102(filename)
+msgid "rpm-info.xml"
+msgstr "rpm-info.xml"
+
+#: en_US/module-struct.xml:102(seg)
+msgid "The <placeholder-1/> file contains document specific metadata"
+msgstr "Il file <placeholder-1/> contiene metadata specifica per la documentazione"
+
+#: en_US/module-struct.xml:107(title)
+msgid "Common Build Tools"
+msgstr "Strumenti Comuni di Creazione"
+
+#: en_US/module-struct.xml:108(para)
+msgid ""
+"Never add the <systemitem>docs-common</systemitem> build tools directory to "
+"an individual module. Special formatting in the module list downloads these "
+"tools when a user checks out a document module. For more information, refer "
+"to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+msgstr ""
+"Non aggiungere mai la cartella strumenti di creazione <systemitem>docs-"
+"common</systemitem> su un modulo individuale. La formattazione speciale "
+"nell'elenco del modulo scarica questi strumenti quando un utente controlla "
+"un modulo di documento. Per più informazioni, fare riferimento a <xref linkend="
+"\"ch-getting-files-naming-modules\"/>."
+
+#: en_US/module-struct.xml:116(title)
+msgid "The Document Build System"
+msgstr "Il Sistema di Creazione del Documento"
+
+#: en_US/module-struct.xml:121(para)
+msgid ""
+"In Linux and Fedora documentation, references to commands often include a "
+"number inside parentheses. This number represents the section of "
+"<firstterm>manpages</firstterm> that includes documentation for that "
+"command. To read the manpage for <command>make(1)</command>, use the command "
+"<command>man 1 make</command>."
+msgstr ""
+"In Linux e nella documentazione Fedora, riferimenti ai comanti includono "
+"numeri all'interno di parentesi. Questi numeri rappresentano le sezionioni "
+"delle <firstterm>manpages</firstterm> che includono la documentazione per il "
+"comando. Per leggere la pagina di man per <command>make(1)</command>, usare "
+"il comando <command>man 1 make</command>."
+
+#: en_US/module-struct.xml:117(para)
+msgid ""
+"The build system can render the document into another format such as "
+"<abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</"
+"command><placeholder-1/> and shell scripts. Authors need <emphasis>no</"
+"emphasis> prior experience with either shell scripts or a <command>make(1)</"
+"command>."
+msgstr ""
+"Il sistema di creazione può rendere il documento in un altro formato come "
+"<abbrev>HTML</abbrev> o <abbrev>PDF</abbrev>, usando <command>make(1)</"
+"command><placeholder-1/> e script shell. Gli autori <emphasis>non</"
+"emphasis> necessitano di esperienza con gli script shell o un <command>make"
+"(1)</command>."
+
+#: en_US/module-struct.xml:133(title)
+msgid "The Document <filename>Makefile</filename>"
+msgstr "Il Documento <filename>Makefile</filename>"
+
+#: en_US/module-struct.xml:134(para)
+msgid ""
+"Each individual document has its own <filename>Makefile</filename>, which "
+"only needs to be a few lines long. The document <filename>Makefile</"
+"filename> content is designed for cut and paste operations."
+msgstr ""
+"Ogni singolo documento ha il proprio <filename>Makefile</filename>, che "
+"necessita solo di alcune lunge linee. Il contenuto del documento <filename>Makefile</"
+"filename> è disegnato per operazioni di taglia e incolla."
+
+#: en_US/module-struct.xml:140(para)
+msgid ""
+"<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</"
+"filename> for a simple document with two files and two translations."
+msgstr ""
+"<xref linkend=\"ex-makefile\"/> di seguito viene mostrato l'intero "
+"<filename>Makefile</filename> per un semplice documento con due file e due "
+"traduzioni."
+
+#: en_US/module-struct.xml:146(title)
+msgid "Sample Document Makefile"
+msgstr "Esempio di Documento Makefile"
+
+#: en_US/module-struct.xml:162(para)
+msgid ""
+"Do not be concerned with some of the more complicated syntax such as the "
+"<command>XMLFILES_template</command> stanza. An explanation for this "
+"template appears a few paragraphs below."
+msgstr ""
+"Non preoccuparsi per alcune sintassi complicate come la strofa "
+"<command>XMLFILES_template</command>. Una spiegazione per questo template "
+"appare alcuni paragrafi più sotto."
+
+#: en_US/module-struct.xml:168(title)
+msgid "Makefile Variables"
+msgstr "Variabili del Makefile"
+
+#: en_US/module-struct.xml:169(segtitle)
+msgid "Variable"
+msgstr "Variabile"
+
+#: en_US/module-struct.xml:170(segtitle) en_US/module-struct.xml:240(segtitle)
+msgid "Explanation"
+msgstr "Spiegazione"
+
+#: en_US/module-struct.xml:172(systemitem)
+msgid "DOCBASE"
+msgstr "DOCBASE"
+
+#: en_US/module-struct.xml:173(seg)
+msgid ""
+"This variable contains the name for the main (parent) XML document. Follow "
+"convention by naming your document after the module name."
+msgstr ""
+"La variabile contiene il nome per la documentazione XML principale (parent). "
+"Seguire la convenzione per nominare il documento dopo il nome del modulo."
+
+#: en_US/module-struct.xml:178(systemitem)
+msgid "PRI_LANG"
+msgstr "PRI_LANG"
+
+#: en_US/module-struct.xml:179(seg)
+msgid ""
+"This variable contains the ISO code for the original version of the "
+"document, such as <placeholder-1/>."
+msgstr ""
+"Questa variabile contiene il codice ISO per la versione originale del "
+"documento, come <placeholder-1/>."
+
+#: en_US/module-struct.xml:184(systemitem)
+msgid "DOC_ENTITIES"
+msgstr "DOC_ENTITIES"
+
+#: en_US/module-struct.xml:185(seg)
+msgid ""
+"This variable contains a listing of any files containing entity definitions. "
+"The Fedora Documentation Project uses a special XML format to record "
+"document-specific entities, so they can be translated and built on the fly "
+"like any other XML document. An example is shown later in this guide."
+msgstr ""
+"Questa variabile contiene un elenco di file contenenti definizioni di "
+"entità. Il Fedora Documentation Project usa un formato speciale XML per "
+"registrare entità specifiche di documentazione, così possono essere tradotte e "
+"costruite al volo come qualsiasi altro documento XML. Un esempio è mostrato "
+"più avanti in questa guida."
+
+#: en_US/module-struct.xml:194(systemitem)
+msgid "XMLFILES_template"
+msgstr "XMLFILES_template"
+
+#: en_US/module-struct.xml:197(systemitem)
+msgid "${1}"
+msgstr "${1}"
+
+#: en_US/module-struct.xml:202(systemitem)
+msgid "${1}/"
+msgstr "${1}/"
+
+#: en_US/module-struct.xml:195(seg)
+msgid ""
+"This template allows the build tools to work with the document in multiple "
+"languages once it is translated. The <placeholder-1/> marking is a variable "
+"used to substitute the appropriate language. This template is not terribly "
+"complicated. For a new module, duplicate this section exactly except for the "
+"actual filenames. Prepend the text <placeholder-2/>, in place of the "
+"language code directory name, to each filename in your document."
+msgstr ""
+"Questo modello permette agli strumenti di creazione di lavorare con il "
+"documento in più lingue quando viene tradotto. La marcatura <placeholder-1/> "
+"è una variabile usata per sostituire la lingua appropriata. Questo modello "
+"non è così complicato. Per un nuovo modulo, duplicare esattamente questa sezione "
+"ad eccezzione del nome del file attuale. Anteporre il testo <placeholder-2/"
+">, al posto del nome della directory della lingua, per ogni nome del file "
+"nel documento."
+
+#: en_US/module-struct.xml:208(title)
+msgid "Files Exempt From Listing"
+msgstr "Files Esente dall'Elenco"
+
+#: en_US/module-struct.xml:209(para)
+msgid ""
+"Do not include the document-specific entities XML file or the <filename>rpm-"
+"info.xml</filename> file, which will be discussed later in this guide."
+msgstr ""
+"Non includere entità file XML specifiche al documento oppure file <filename>rpm-info."
+"xml</filename>, che saranno discussi più avanti in questa guida."
+
+#: en_US/module-struct.xml:213(para)
+msgid ""
+"The final section, beginning with <literal>define</literal>, locates the "
+"main <filename>Makefile.common</filename> for the build system. This "
+"<filename>Makefile.common</filename> file contains all the <application>make"
+"(1)</application> targets and rules to actually build the document and the "
+"various archives."
+msgstr ""
+"La sezione finale, inizia con <literal>define</literal>, localizza il "
+"<filename>Makefile.common</filename> principale per costruire il sistema. "
+"Questo file <filename>Makefile.common</filename> contiene tutti gli obiettivi e "
+"le regole di <application>make(1)</application> per creare il documento e i "
+"vari archivi."
+
+#: en_US/module-struct.xml:222(title)
+msgid "The Document <filename>rpm-info.xml</filename>"
+msgstr "Il Documento <filename>rpm-info.xml</filename>"
+
+#: en_US/module-struct.xml:223(para)
+msgid ""
+"Each document module's primary language directory contains a file called "
+"<filename>rpm-info.xml</filename>. This file contains document-specific "
+"metadata used to generate revision history, copyright, and contributor "
+"information. It follows a DTD specification included with the rest of the "
+"build system tools."
+msgstr ""
+"Ogni modulo di documento della cartella della lingua primaria contiene un file "
+"chiamato <filename>rpm-info.xml</filename>. Questo file contiene metadata "
+"specifici di documento usati per generare la sotoria di revisione, "
+"copyright e informazioni sui contributori. Esso segue una specifica DTD "
+"inclusa con il resto degli strumenti di creazione."
+
+#: en_US/module-struct.xml:232(title)
+msgid "Build System Actions"
+msgstr "Creare Azioni di Sistema"
+
+#: en_US/module-struct.xml:233(para)
+msgid ""
+"To render the <abbrev>XML</abbrev> document into another format, use one of "
+"the following <command>make</command> targets:"
+msgstr ""
+"Per rendere un documento <abbrev>XML</abbrev> in un altro formato, usare uno "
+"dei seguenti obiettivi <command>make</command>:"
+
+#: en_US/module-struct.xml:238(title)
+msgid "Build Targets"
+msgstr "Creare Obiettivi"
+
+#: en_US/module-struct.xml:239(segtitle)
+msgid "Target"
+msgstr "Obiettivo"
+
+#: en_US/module-struct.xml:242(systemitem)
+msgid "help"
+msgstr "aiuto"
+
+#: en_US/module-struct.xml:243(seg)
+msgid "This target prints a list of available targets and their descriptions."
+msgstr ""
+"Questo obiettivo mostra un elenco di obiettivi disponibili e la loro "
+"descrizione."
+
+#: en_US/module-struct.xml:247(systemitem)
+msgid "validate-xml"
+msgstr "validate-xml"
+
+#: en_US/module-struct.xml:248(firstterm)
+msgid "validates"
+msgstr "convalida"
+
+#: en_US/module-struct.xml:248(seg)
+msgid ""
+"This target <placeholder-1/> the XML files to make sure they are not only "
+"well-formed, but follow the DTD. Some viewers of XML documents may not work "
+"correctly until you run this target. This target includes copying required "
+"entity files so that validating XML viewers work properly"
+msgstr ""
+"Questo obiettivo <placeholder-1/> i file XML per assicurarsi che essi non "
+"solo siano ben formattati ma seguano la DTD. Alcuni visualizzatori di "
+"documenti XML potrebbero non funzionare correttamente finché non si esegue "
+"questo obiettivo. Questo obiettivo comprende la copia dei file entità "
+"necessari in modo che la validazione di visualizzatori XML funzioni correttamente"
+
+#: en_US/module-struct.xml:256(systemitem)
+msgid "html"
+msgstr "html"
+
+#: en_US/module-struct.xml:257(abbrev) en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:293(abbrev) en_US/module-struct.xml:298(abbrev)
+msgid "HTML"
+msgstr "HTML"
+
+#: en_US/module-struct.xml:261(systemitem)
+#: en_US/module-struct.xml:271(systemitem)
+msgid "${DOCBASE}"
+msgstr "${DOCBASE}"
+
+#: en_US/module-struct.xml:262(systemitem)
+#: en_US/module-struct.xml:272(systemitem)
+msgid "${LANG}"
+msgstr "${LANG}"
+
+#: en_US/module-struct.xml:260(filename)
+msgid "<placeholder-1/>-<placeholder-2/>/"
+msgstr "<placeholder-1/>-<placeholder-2/>/"
+
+#: en_US/module-struct.xml:257(seg)
+msgid ""
+"This target builds the \"chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a separate directory named "
+"<placeholder-2/>. Each document section is a separate file within that "
+"directory."
+msgstr ""
+"Questi obiettivi del documento creano <placeholder-1/> \"spezzettata\" per ogni "
+"traduzione definita. L'output è messo in una cartella separata "
+"nominata <placeholder-2/>. Ogni sezione del documento è un file separato in questa cartella."
+
+#: en_US/module-struct.xml:267(systemitem)
+msgid "html-nochunks"
+msgstr "html-nochunks"
+
+#: en_US/module-struct.xml:270(filename)
+msgid "<placeholder-1/>-<placeholder-2/>.html"
+msgstr "<placeholder-1/>-<placeholder-2/>.html"
+
+#: en_US/module-struct.xml:268(seg)
+msgid ""
+"This target builds the \"non-chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a single file: <placeholder-2/>; no "
+"other files are created."
+msgstr ""
+"Questo obiettivo crea il documento \"non-spezzettato\" <placeholder-1/> per "
+"ogni traduzione. L'output è messo in un singolo file: <placeholder-2/>; non "
+"vengono creati altri file."
+
+#: en_US/module-struct.xml:276(systemitem)
+msgid "pdf"
+msgstr "pdf"
+
+#: en_US/module-struct.xml:277(abbrev) en_US/module-struct.xml:278(abbrev)
+#: en_US/module-struct.xml:294(abbrev) en_US/module-struct.xml:299(abbrev)
+msgid "PDF"
+msgstr "PDF"
+
+#: en_US/module-struct.xml:277(seg)
+msgid ""
+"This target builds only the <placeholder-1/> document for all document "
+"languages. <placeholder-2/> production is currently erratic and may not work "
+"for your document."
+msgstr ""
+"Questo obiettivo crea solo il documento <placeholder-1/> per tutte le lingue "
+"del documento. La produzione di <placeholder-2/> è attualmente errata e "
+"potrebbe non funzionare con il proprio documento."
+
+#: en_US/module-struct.xml:282(systemitem)
+msgid "tarball"
+msgstr "tarball"
+
+#: en_US/module-struct.xml:283(command)
+msgid "tar(1)"
+msgstr "tar(1)"
+
+#: en_US/module-struct.xml:283(seg)
+msgid ""
+"This target builds only the <placeholder-1/> archive for all document "
+"languages."
+msgstr ""
+"Questo obiettivo costruisce solo l'archivio <placeholder-1/> per tutte le "
+"lingue dei documenti."
+
+#: en_US/module-struct.xml:287(systemitem)
+msgid "all"
+msgstr "all"
+
+#: en_US/module-struct.xml:288(seg)
+msgid "This target builds all targets listed above."
+msgstr "Questo obiettivo costruisce tutti gli obiettivi elencati sotto."
+
+#: en_US/module-struct.xml:291(systemitem)
+#: en_US/module-struct.xml:300(filename)
+msgid "clean"
+msgstr "clean"
+
+#: en_US/module-struct.xml:293(emphasis)
+msgid "not"
+msgstr "not"
+
+#: en_US/module-struct.xml:292(seg)
+msgid ""
+"This target deletes any temporary, or generated files, but does <placeholder-"
+"1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr ""
+"Questo obiettivo elimina qualsiasi file temporaneo o generato ma non "
+"<placeholder-1/> cancella nessun <placeholder-2/>, <placeholder-3/>, o "
+"archivio di file."
+
+#: en_US/module-struct.xml:297(systemitem)
+msgid "distclean"
+msgstr "distclean"
+
+#: en_US/module-struct.xml:298(seg)
+msgid ""
+"This target erases all <placeholder-1/>, <placeholder-2/>, and archive "
+"files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr ""
+"Questo obiettivo elimina tutti <placeholder-1/>, <placeholder-2/>e archivi "
+"di file. Questo target invoca automaticamente l'obiettivo <placeholder-3/>."
+
+#: en_US/module-struct.xml:305(title)
+msgid "PDF Generation is Erratic"
+msgstr "Generazione PDF è irregolare"
+
+#: en_US/module-struct.xml:306(para)
+msgid ""
+"<abbrev>PDF</abbrev> production is currently erratic and may not work for "
+"your document."
+msgstr ""
+"la produzione di <abbrev>PDF</abbrev> è attualmente irregolare e può non "
+"funzionare per il proprio documento."
+
+#: en_US/module-struct.xml:311(title)
+msgid "Adding or Changing Targets"
+msgstr "Aggiungere o Cambiare Obiettivi"
+
+#: en_US/module-struct.xml:312(para)
+msgid ""
+"To add a new target and rules, place them at the bottom of the document "
+"<filename>Makefile</filename>, below the <literal>include</literal> line. "
+"Follow your target definitions with a double colon, not a single colon. The "
+"double colon allows you to specify additional rules for existing targets, or "
+"to write rules for a new target."
+msgstr ""
+"Per aggiungere una nuova regola e un nuovo obiettivo, metterli in fondo al "
+"documento <filename>Makefile</filename>, dopo la linea <literal>include</"
+"literal>. Seguire la definizione del proprio obiettivo con due colonne, non "
+"una singola. Le doppie colonne permettono di specificare regole aggiuntive "
+"per gli obiettivi esistenti o scrivere regole per un nuovo obiettivo."
+
+#: en_US/module-struct.xml:320(para)
+msgid ""
+"For more information on using <command>make(1)</command>, consult the online "
+"documentation with the command <command>info make</command> in a terminal."
+msgstr ""
+"Per maggiori informazioni sull'uso di <command>make(1)</command>, consulatre la "
+"documentazione online con il comando <command>info make</command> in un "
+"terminale."
+
+#: en_US/module-struct.xml:327(title)
+msgid "Using Document Image Files"
+msgstr "Usare File Immagini Documenti"
+
+#: en_US/module-struct.xml:328(para)
+msgid ""
+"Tutorial documents often make use of images such as <filename class="
+"\"extension\">.PNG</filename> files. Store image files in a <filename class="
+"\"directory\">figs/</filename> folder in the main module directory, as shown "
+"in <xref linkend=\"ex-module-structure\"/>."
+msgstr ""
+"I documenti Tutorial fanno anche uso di immagini come file <filename class="
+"\"extension\">.PNG</filename>. Salvare i file immagine in una cartella "
+"<filename class=\"directory\">figs/</filename> nella directory principale "
+"del modulo, come mostrato nella <xref linkend=\"ex-module-structure\"/>."
+
+#: en_US/module-struct.xml:335(para)
+msgid ""
+"Depending on the output media, sometimes images may be scaled, streteched, "
+"or squashed. To minimize any distortions, we recommend that you use only "
+"<filename class=\"extension\">.PNG</filename> images. Avoid <filename class="
+"\"extension\">.JPG</filename> files. The <command>convert(1)</command> "
+"program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</"
+"abbrev> package, provides a convenient way to reformat <filename class="
+"\"extension\">.JPG</filename> images into <filename class=\"extension\">."
+"PNG</filename> format. For more information on formatting images such as "
+"screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr ""
+"Dipende dal media di output, a volte le immagini possono essere scalate, "
+"stirate o schiacciate. Per minimizzare le distorsioni si raccomanda di usare "
+"solo immagini <filename class=\"extension\">.PNG</filename>. Evitare file "
+"<filename class=\"extension\">.JPG</filename>. Il programma <command>convert"
+"(1)</command>, dal pacchetto <abbrev>RPM</abbrev><package role=\"rpm"
+"\">ImageMagick</package>, fornisce un modo conveniente per riformattare "
+"immagini <filename class=\"extension\">.JPG</filename> nel formato <filename "
+"class=\"extension\">.PNG</filename>. Per maggiori informazioni sulla "
+"formattazione delle immagini come screenshot, fare riferimento a <xref "
+"linkend=\"sn-screenshots\"/>."
+
+#: en_US/module-struct.xml:349(para)
+msgid ""
+"Image files may be organized into subdirectories under <filename>figs/</"
+"filename> if necessary. The document building system recreates the image "
+"subdirectory structure in the output documents."
+msgstr ""
+"I file immagine potrebbero essere organizzati in sottocartelle sotto "
+"<filename>figs/</filename> se necessario. Il sistema di creazione del "
+"documento ricrea la struttura delle sottocartelle nell'output del documento."
+
+#: en_US/module-struct.xml:355(para)
+msgid ""
+"Images often contain labels or other text which may need to be localized. A "
+"screenshot of a program, for example, may require a version for each "
+"translated language. Name language-dependent image files such as program "
+"screenshots by adding the language code to the filename, such as "
+"<filename>menu-en_US.png</filename>. Language-independent images, such as "
+"<filename>icon.png</filename>, do not need language codes."
+msgstr ""
+"Le immagini spesso contengono ettichette o altro testo che necessita di essere "
+"localizzato. La schermata di un programma, per esempio, può richiedere una "
+"versione per ogni lingua tradotta. Nominare i file come le schermate di programmi "
+"in dipendenza della lingua con l'aggiunta del codice della lingua al "
+"nome del file, come <filename>menu-en_US.png</filename>. Le immagini non "
+"dipendenti dalla lingua, come <filename>icon.png</filename>, non necessitano del "
+"codice lingua."
+
+#: en_US/module-struct.xml:365(para)
+msgid ""
+"Sometimes, a document may require images that do not follow the naming "
+"convention. To use these images with the document building system, create an "
+"ordinary text file containing the image filenames. This file must be named "
+"<filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</"
+"systemitem> so the build system finds it when searching for image filenames."
+msgstr ""
+"A volte, un documento può richiedere immagini che non seguono la convenzione "
+"dei nomi. Usare queste immagini con il sistema di creazione del documento, "
+"creare un file di testo ordinario contenente i nomi dei file immagine. "
+"Questo file deve essere nominato <filename>figs/Manifest-</"
+"filename><systemitem class=\"macro\">${LANG}</systemitem> così il sistema di "
+"creazione li troverà quando cercherà i nomi dei file immagini."
+
+#: en_US/module-struct.xml:374(para)
+msgid ""
+"<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one "
+"way to create this <filename>Manifest</filename> file."
+msgstr ""
+"<xref linkend=\"ch-getting-files-build-system-manifest\"/> dimostra un modo "
+"per creare questo file <filename>Manifest</filename>."
+
+#: en_US/module-struct.xml:380(title)
+msgid "Building A Manifest"
+msgstr "Creare un Manifesto"
+
+#: en_US/module-struct.xml:387(title)
+msgid "Adding a New DocBook XML File"
+msgstr "Aggiungere un nuovo file DocBook XML"
+
+#: en_US/module-struct.xml:388(para)
+msgid "To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr ""
+"Per aggiungere un nuovo file DocBook XML ad un documento esistente, seguire "
+"questi passaggi:"
+
+#: en_US/module-struct.xml:392(para)
+msgid "Place the new DocBook XML file in the primary language directory."
+msgstr "Mettere il nuovo file DocBook XML nella cartella della lingua primaria."
+
+#: en_US/module-struct.xml:396(para)
+msgid ""
+"Edit the <filename>Makefile</filename> and add the filename to the "
+"<varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to "
+"the last existing line, and on the next line add an entry for the new file. "
+"Remember to add the <literal>${1}/</literal> prefix as a substitute for the "
+"language directory name."
+msgstr ""
+"Modificare il <filename>Makefile</filename> e aggiungere il nome del file "
+"all'elenco <varname>XMLFILES-${1}</varname>. Aggiungere <keycap>\\</keycap> "
+"all'ultima linea esistente e sulla linea successiva aggiungere una voce per "
+"il nuovo file. Ricordare di aggiungere il prefisso <literal>${1}/</literal> "
+"come sostituto per il nome della cartella della lingua."
+
+#: en_US/module-struct.xml:406(title)
+msgid "Adding a Translation"
+msgstr "Aggiungere una Traduzione"
+
+#: en_US/module-struct.xml:407(para)
+msgid ""
+"Translations are stored as PO (portable object) files, which the toolchain "
+"transforms into translated documents. Each PO file is based on the POT (PO "
+"template) for the document and translated by the Fedora Translation Project. "
+"To add a translation, follow these steps:"
+msgstr ""
+"Le traduzioni vengono salvate come file PO (portable object), che vengono "
+"trasformati dai toolchain in documenti tradotti. Ogni file PO è basato su un POT "
+"(PO template) per il documento e tradotto dal Fedora Translation Project. "
+"Per aggiungere una traduzione, seguire questi passaggi:"
+
+#: en_US/module-struct.xml:414(para)
+msgid ""
+"If the <filename class=\"directory\">po/</filename> directory does not "
+"exist, create it and add it to CVS:"
+msgstr ""
+"Se la cartella <filename class=\"directory\">po/</filename> non esiste, "
+"crearla e aggiungerla nel CVS:"
+
+#: en_US/module-struct.xml:420(para)
+msgid "If it does not exist, create the POT file:"
+msgstr "Se non esiste, creare un file POT:"
+
+#: en_US/module-struct.xml:424(para)
+msgid ""
+"Add the new translation language to the <varname>OTHERS</varname> listing in "
+"the <filename>Makefile</filename>."
+msgstr ""
+"Aggiungere la nuova lingua di traduzione all'elenco <varname>OTHERS</"
+"varname> nel <filename>Makefile</filename>."
+
+#: en_US/module-struct.xml:429(para)
+msgid ""
+"Although translators often copy the POT manually to create the new PO file, "
+"the following command also works:"
+msgstr ""
+"Sebbene i traduttori spesso copiano i POT manualmente per creare un nuovo "
+"file PO, funziona anche il seguente comando:"
+
+#: en_US/module-struct.xml:432(replaceable)
+msgid "lang"
+msgstr "lang"
+
+#: en_US/module-struct.xml:432(screen)
+#, no-wrap
+msgid "make po/<placeholder-1/>.po"
+msgstr "make po/<placeholder-1/>.po"
+
+#: en_US/intro.xml:13(title)
+msgid "Introduction"
+msgstr "Introduzione"
+
+#: en_US/intro.xml:15(para)
+msgid ""
+"The goal of the Fedora Documentation Project is to create easy-to-follow, "
+"task-based documentation for Fedora users and developers. The Fedora "
+"Documentation Project uses the following tools:"
+msgstr ""
+"L'obiettivo del Fedora Documentation Project è di creare una documentazione "
+"a compiti e facile da seguire per gli utenti Fedora e gli sviluppatori. Il Fedora "
+"Documentation Project usa i seguenti strumenti:"
+
+#: en_US/intro.xml:23(para)
+msgid "DocBook XML v4.4"
+msgstr "DocBook XML v4.4"
+
+#: en_US/intro.xml:26(para)
+msgid "Custom XSLT stylesheets for both print and HTML versions"
+msgstr "Foglio di stile XSLT modificato sia per la versione stampa sia HTML"
+
+#: en_US/intro.xml:30(para)
+msgid "Custom scripts to generate HTML output (use <command>xmlto</command>)"
+msgstr "Script modificati per generare output HTML (usando <command>xmlto</command>)"
+
+#: en_US/intro.xml:34(para)
+msgid "Emacs with PSGML mode (optional, but recommended)"
+msgstr "Emacs con modo PSGML (opzionale ma raccomandato)"
+
+#: en_US/intro.xml:43(para)
+msgid ""
+"This document explains the tools used by the Fedora Documentation Project. "
+"It provides writing and tagging guidelines to ensure Fedora documentation is "
+"consistent and easy-to-follow."
+msgstr ""
+"Questo documento espone gli strumenti usati dal Fedora Documentation "
+"Project. Esso fornisce linee guida per la scrittura e il tagging per "
+"assicuare che la documentazione Fedora sia consistente e facile da seguire."
+
+#: en_US/getting-files.xml:12(title)
+msgid "Prerequisites"
+msgstr "Prerequisiti"
+
+#: en_US/getting-files.xml:14(para)
+msgid ""
+"To work on official Fedora documentation you need to install the required "
+"tools. Follow the directions below to configure your system."
+msgstr ""
+"Per lavorare sulla documentazione ufficiale di Fedora è necessario aver "
+"installato gli strumenti richiesti. Seguire le seguenti direttive per "
+"configurare il proprio sistema."
+
+#: en_US/getting-files.xml:20(title)
+msgid "System Packages"
+msgstr "Pacchetti di sistema"
+
+#: en_US/getting-files.xml:22(para)
+msgid ""
+"Install the \"Authoring and Publishing\" package group, which contains "
+"required DocBook XML files, stylesheets and scripts:"
+msgstr ""
+"Installare il gruppo di pacchetti \"Authoring and Publishing\", che contiene "
+"i files DocBook XML richiesti, fogli di stile e script:"
+
+#: en_US/getting-files.xml:28(userinput)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+msgstr "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+
+#: en_US/getting-files.xml:31(para)
+msgid ""
+"Next, install the <filename>cvs</filename> package, which is used to handle "
+"revision control on files in the official repository:"
+msgstr ""
+"Poi, installare il pacchetto <filename>cvs</filename>, che è usato per "
+"maneggiare il controllo delle revisioni sui file nei repository ufficiali:"
+
+#: en_US/getting-files.xml:37(userinput)
+#, no-wrap
+msgid "su -c 'yum install cvs'"
+msgstr "su -c 'yum install cvs'"
+
+#: en_US/getting-files.xml:40(para)
+msgid ""
+"If you plan to use <application>Emacs</application> to edit DocBook XML "
+"documentation, install <package>psgml</package>, which adds helpful and time-"
+"saving functionality to maximize editing efficiency:"
+msgstr ""
+"Se si pensa di usare <application>Emacs</application> per modificare la "
+"documentazione DocBook XML, installare <package>psgml</package>, che "
+"aggiunge funzioni utili e salvataggi automatici per migliorare l'efficienza "
+"della modifica:"
+
+#: en_US/getting-files.xml:44(userinput)
+#, no-wrap
+msgid "su -c 'yum install psgml'"
+msgstr "su -c 'yum install psgml'"
+
+#: en_US/getting-files.xml:48(title)
+msgid "Fedora Documentation Tools"
+msgstr "Strumenti Documentazione Fedora"
+
+#: en_US/getting-files.xml:50(para)
+msgid ""
+"The Fedora Documentation Project's custom scripts and stylesheets are stored "
+"in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</"
+"systemitem> CVS server. When you check out a document module from CVS, the "
+"tools are included in the module inside the <filename class=\"directory"
+"\">docs-common/</filename> directory. To work on existing documents in CVS, "
+"refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+"Gli script personalizzati e i fogli di stile del Fedora Documentation Project sono salvati "
+"in CVS sul server CVS <systemitem class=\"fqdomainname\">cvs.fedoraproject."
+"org</systemitem>. Quando si fa il controllo di un modulo di un documento da "
+"CVS, gli strumenti sono inclusi all'interno del modulo nella cartella "
+"<filename class=\"directory\">docs-common/</filename>. Per lavorare su "
+"documenti esistenti in CVS fare riferimento a <xref linkend=\"ch-cvs\"/"
+">."
+
+#: en_US/getting-files.xml:59(para)
+msgid ""
+"The most powerful component in the Fedora Documentation Project toolbox is "
+"<firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for "
+"authoring technical documentation using <firstterm>Extensible Markup "
+"Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark "
+"pieces of content with descriptive tags. The following output is an example "
+"of DocBook XML:"
+msgstr ""
+"Il componente più potente del Fedora Documentation Project è "
+"<firstterm>DocBook XML</firstterm>. DocBook XML è uno schema specifico per "
+"la documentazione tecnica che usa <firstterm>Extensible Markup Language</"
+"firstterm> o <acronym>XML</acronym>. XML permette agli autori di marcare "
+"pezzi di contenuti con tag descrittivi. Il seguente output è un esempio di "
+"DocBook XML:"
+
+#: en_US/getting-files.xml:76(para)
+msgid ""
+"This example article, entitled <citetitle>A Very Short Article</citetitle>, "
+"consists of only a single paragraph. The tags, or markup, surround elements "
+"of content to define the sense in which they are used. A paragraph, for "
+"example, is marked with <sgmltag>para</sgmltag> tags. Text that requires "
+"emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does "
+"not worry about the visual formatting such as italics or font size. Fedora "
+"Documentation Project build tools automatically perform all formatting tasks."
+msgstr ""
+"Questo articolo d'esempio, intitolato <citetitle>A Very Short Article</"
+"citetitle>, consiste solo di un singolo paragrafo. I tag, o markup, "
+"circondano gli elementi del contenuto per definire in che senso vengono usati. "
+"Un paragrafo, per esempio, è marcato con tag <sgmltag>para</sgmltag>. Il "
+"testo che deve essere enfatizzato è marcato con i tag <sgmltag>emphasis</"
+"sgmltag>. Gli autori non si devono preoccupare della formattazione visiva "
+"come corsivo o la dimensione dei caratteri. Gli strumenti di creazione del "
+"Fedora Documentation Project eseguono automaticamente tutti i compiti di formattazione."
+
+#: en_US/getting-files.xml:85(para)
+msgid ""
+"The custom tools built by the Fedora Documentation Project render DocBook "
+"source into a variety of formats for publication and distribution. They also "
+"allow translators to create localized versions of the XML documents for "
+"Fedora users around the world. The flexibility of XML allows for a single "
+"document to be used many times for many purposes, like reusable code for a "
+"programmer."
+msgstr ""
+"Gli strumenti personalizzati dal Fedora Documentation Project eseguono il render del "
+"sorgente DocBook in una varietà di formati per la pubblicazione e "
+"distribuzione. Essi inoltre permettono ai traduttori di creare versioni "
+"localizzate di un documento XML per gli utenti Fedora di tutto il mondo. La "
+"flessibilità di XML permette a singoli documenti di essere usati in diverse "
+"occasioni e scopi, come il codice riusabile di un programmatore."
+
+#: en_US/getting-files.xml:91(para)
+msgid ""
+"DocBook is itself very well documented. For more information about DocBook, "
+"visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also "
+"features complete copies of <citetitle>DocBook: The Definitive Guide</"
+"citetitle> to browse and download, the canonical source for DocBook "
+"information."
+msgstr ""
+"Già in sè stesso DocBook è ben documentato. Per maggiori informazioni su Docbook, "
+"visitare <ulink url=\"http://www.docbook.org/\"/>. Il sito web DocBook "
+"inoltre, fornisce copie complete di <citetitle>DocBook: The Definitive Guide</"
+"citetitle> da navigare o scaricare, il sorgente canonico per le informazioni "
+"DocBook."
+
+#: en_US/getting-files.xml:97(title)
+msgid "DocBook XML Versions"
+msgstr "Versioni DocBook XML"
+
+#: en_US/getting-files.xml:98(para)
+msgid ""
+"DocBook XML, like a computer program, has version numbers. The version used "
+"by Fedora Documentation Project right now is 4.4. The DocBook web site may "
+"document a slightly newer version, but the majority of the schema still "
+"applies."
+msgstr ""
+"DocBook XML, come un programma per computer, ha dei numeri di versione. La "
+"versione attualmente usata dal Fedora Documentation Project è la 4.4. Il sito web "
+"DocBook potrebbe documentare una nuova versione ma in linea di massima si "
+"può applicare lo stesso schema."
+
+#: en_US/getting-files.xml:103(para)
+msgid ""
+"Contributors who use the Microsoft Windows operating system can still make "
+"use of DocBook tools. For more information, refer to <ulink url=\"http://www."
+"codeproject.com/winhelp/docbook_howto.asp\"/>."
+msgstr ""
+"I contributori che usano il sistema operativo Microsoft Windows possono "
+"usare gli strumenti di DocBook. Per maggiori informazioni fare riferimento a "
+"<ulink url=\"http://www.codeproject.com/winhelp/docbook_howto.asp\"/>."
+
+#: en_US/getting-files.xml:110(title)
+msgid "Naming Conventions"
+msgstr "Convenzione dei nomi"
+
+#: en_US/getting-files.xml:111(para)
+msgid ""
+"The Fedora Documentation Project provides the tools, scripts, and "
+"stylesheets to transform your <abbrev>XML</abbrev> documents into other "
+"output formats such as <abbrev>HTML</abbrev>. In addition, these tools can "
+"build your document into a <abbrev>RPM</abbrev> package. To take advantage "
+"of these services, follow the conventions in this section to name your files."
+msgstr ""
+"Il Fedora Documentation Project fornisce strumenti, script e fogli di stile "
+"per trasformare il documento <abbrev>XML</abbrev> in altri formati come "
+"<abbrev>HTML</abbrev>. In aggiunta, questi strumenti possono creare "
+"il documento all'interno di un pacchetto <abbrev>RPM</abbrev>. Per avere "
+"vantaggi da questi servizi, seguire le convenzioni in questa sezione sui "
+"nomi dei propri file."
+
+#: en_US/getting-files.xml:119(para)
+msgid ""
+"On the CVS server, directories that contain document files are called "
+"<firstterm>modules</firstterm>. Each module represents a single document. "
+"Each document may consist of several <firstterm>branches</firstterm> if that "
+"document changes with each release of Fedora. Contributors can check out "
+"single branches of these modules or the entire module. Each document or "
+"branch may contain multiple XML source files."
+msgstr ""
+"Sul server CVS, le cartelle che contengono file di documenti sono "
+"chiamate <firstterm>moduli</firstterm>. Ogni modulo rappresenta un singolo "
+"documento. Ogni documento può consistere in una serie di "
+"<firstterm>branche</firstterm> se questo documento cambia con ogni "
+"versione di Fedora. I contributori possono controllore la propria "
+"branca del modulo o il modulo intero. Ogni documento o branca può contenere "
+"diversi file sorgenti XML."
+
+#: en_US/getting-files.xml:126(para)
+msgid "Use the <command>cvs co -c</command> command to view existing module names."
+msgstr ""
+"Usare il comando <command>cvs co -c</command> per vedere i nomi dei moduli "
+"esistenti."
+
+#: en_US/getting-files.xml:129(title)
+msgid "Partial List of CVS Modules"
+msgstr "Lista parziale dei moduli CVS"
+
+#: en_US/getting-files.xml:130(userinput)
+#, no-wrap
+msgid "cd ~/localrepo/fedora-docs/"
+msgstr "cd ~/localrepo/fedora-docs/"
+
+#: en_US/getting-files.xml:149(para)
+msgid ""
+"The leftmost entry in each line is the name of a module you can check out "
+"from CVS. The rest of the line ensures that checkouts include the proper "
+"branch of a document and the common build tools. For more information on "
+"CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+"La parola più a sinistra di ogni riga è il nome di un modulo che si può "
+"controllare da CVS. Il resto della linea assicura che i controlli "
+"includono la corretta branca del documento e gli strumenti di creazione "
+"comuni. Per maggiori informazioni su CVS fare riferimento a <xref linkend=\"ch-cvs"
+"\"/>."
+
+#: en_US/getting-files.xml:154(para)
+msgid ""
+"Note in the listing above that the <systemitem>about-fedora</systemitem> "
+"module has two branches available. One branch is for Fedora 7 and one is for "
+"forward development to match the current work of developers. On the other "
+"hand, the <systemitem>documentation-guide</systemitem> module is not "
+"branched."
+msgstr ""
+"Notare che nella lista qui sotto il modulo <systemitem>about-fedora</"
+"systemitem> ha due branche disponibili. Una branca è per Fedora 7 e una è "
+"per lo sviluppo futuro in accordo con il lavoro corrente di sviluppo. "
+"Invece, il modulo <systemitem>documentation-guide</systemitem> non ha "
+"branche."
+
+#: en_US/getting-files.xml:161(title)
+msgid "Modules Labeled <filename>-dir</filename>"
+msgstr "Moduli etichettati <filename>-dir</filename>"
+
+#: en_US/getting-files.xml:162(para)
+msgid ""
+"Modules ending with the suffix <filename>-dir</filename> are not usually "
+"helpful to checkout directly. These modules do not include the common build "
+"tools and thus do not provide many of the functions contributors require."
+msgstr ""
+"I moduli che finiscono con il suffisso <filename>-dir</filename> in genere non "
+"sono di aiuto per il controllo diretto. Questi moduli non includono i "
+"comuni strumenti di creazione e non forniscono alcune delle funzioni richieste dai "
+"collaboratori."
+
+#: en_US/getting-files.xml:168(title)
+msgid "Module Names"
+msgstr "Nomi Moduli"
+
+#: en_US/getting-files.xml:169(para)
+msgid ""
+"Choose a module name that accurately reflects your document's subject, but "
+"avoid any name already taken. The document title without any use of the word "
+"<wordasword>fedora</wordasword> is a reasonable choice in most cases. Use "
+"the length descriptors <wordasword>tutorial</wordasword> or "
+"<wordasword>guide</wordasword> in the module name where appropriate."
+msgstr ""
+"Scegliere un nome per il modulo che rifletta il soggetto del documento ma "
+"eviti nomi già esistenti. Il titolo del documento senza la parola "
+"<wordasword>fedora</wordasword> è una scelta ragionevole per la maggior "
+"parte dei casi. Usare l'intera descrizione <wordasword>tutorial</wordasword> "
+"o <wordasword>guide</wordasword> nel nome del modulo dove appropriato."
+
+#: en_US/getting-files.xml:178(title)
+msgid "Avoid Redundancy"
+msgstr "Evitare rindondanza"
+
+#: en_US/getting-files.xml:179(para)
+msgid ""
+"Do not use the word <wordasword>fedora</wordasword> to name modules in the "
+"Fedora Documentation Project CVS repository."
+msgstr ""
+"Non usare la parola <wordasword>fedora</wordasword> per nominare i moduli "
+"nei repository CVS del Fedora Documentation Project."
+
+#: en_US/getting-files.xml:185(title)
+msgid "Correct Module Naming"
+msgstr "Nomenclatura del modulo corretta"
+
+#: en_US/getting-files.xml:186(segtitle)
+msgid "Document Name"
+msgstr "Nome Documento"
+
+#: en_US/getting-files.xml:187(segtitle)
+msgid "CVS Module Name"
+msgstr "Nome Modulo CVS"
+
+#: en_US/getting-files.xml:189(seg)
+msgid "Desktop User Guide"
+msgstr "Guida Utente Desktop"
+
+#: en_US/getting-files.xml:190(seg)
+msgid "desktop-user-guide"
+msgstr "desktop-user-guide"
+
+#: en_US/getting-files.xml:194(application)
+msgid "Yum"
+msgstr "Yum"
+
+#: en_US/getting-files.xml:193(seg)
+msgid "Software Management with <placeholder-1/>"
+msgstr "Amministrazione Software con <placeholder-1/>"
+
+#: en_US/getting-files.xml:195(seg)
+msgid "yum-guide"
+msgstr "yum-guide"
+
+#: en_US/getting-files.xml:198(application)
+msgid "Pup"
+msgstr "Pup"
+
+#: en_US/getting-files.xml:198(seg)
+msgid "Using <placeholder-1/>"
+msgstr "Usando <placeholder-1/>"
+
+#: en_US/getting-files.xml:199(seg)
+msgid "pup-tutorial"
+msgstr "pup-tutorial"
+
+#: en_US/getting-files.xml:204(title)
+msgid "File Names"
+msgstr "Nomi File"
+
+#: en_US/getting-files.xml:205(para)
+msgid ""
+"Follow these guidelines for naming files to make collaboration and document "
+"reuse easy:"
+msgstr ""
+"Seguire queste linee guida per nominare file per rendere facile la collaborazione "
+"e il riutilizzo del documento:"
+
+#: en_US/getting-files.xml:209(para)
+msgid ""
+"As with module names, avoid using the word <wordasword>fedora</wordasword> "
+"in file names since it is redundant."
+msgstr ""
+"Come con i nomi dei moduli, evitare di usare la parola <wordasword>fedora</"
+"wordasword> nei nomi dei file dal momento che fa rindondanza."
+
+#: en_US/getting-files.xml:214(para)
+msgid ""
+"If the document is comprised of many XML files, avoid repeating the name of "
+"the document when naming the constituent files."
+msgstr ""
+"Se il documento è compreso di una serie di file XML, evitare di ripetere il "
+"nome del documento quando si nominano i file costituenti."
+
+#: en_US/getting-files.xml:219(para)
+msgid ""
+"Avoid numbering files to show order, since editors and authors often "
+"rearrange documents or reuse their files in other documents."
+msgstr ""
+"Evitare la numerazione dei file per visualizzare un ordine, dal momento che "
+"gli editori e gli autori spesso riarrangiano i documenti o riusano i loro "
+"file in altri documenti."
+
+#: en_US/emacs.xml:13(title)
+msgid "Emacs and PSGML Mode"
+msgstr "Emacs e Modalità PSGML"
+
+#: en_US/emacs.xml:16(primary)
+msgid "PSGML"
+msgstr "PSGML"
+
+#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary)
+#: en_US/emacs.xml:43(primary) en_US/emacs.xml:224(primary)
+#: en_US/emacs.xml:233(primary) en_US/emacs.xml:238(primary)
+#: en_US/emacs.xml:243(primary) en_US/emacs.xml:523(application)
+#: en_US/emacs-nxml.xml:18(primary) en_US/emacs-nxml.xml:22(primary)
+msgid "Emacs"
+msgstr "Emacs"
+
+#: en_US/emacs.xml:25(secondary)
+msgid "PSGML mode"
+msgstr "modalità PSGML"
+
+#: en_US/emacs.xml:28(para)
+msgid ""
+"You can use the PSGML mode available for Emacs to make it easier to write in "
+"XML format. PSGML mode provides syntax-highlighting, tag completion, and "
+"more."
+msgstr ""
+"Si può usare la modalità PSGML disponibile per Emacs per rendere più facile "
+"la scrittura in formato XML. La modalità PSGML fornisce una sintassi "
+"colorata, completamento dei tag e altro."
+
+#: en_US/emacs.xml:35(title)
+msgid "Installing PSGML"
+msgstr "Installare PSGML"
+
+#: en_US/emacs.xml:36(para)
+msgid "To install PSGML, use the <command>yum</command> command:"
+msgstr "Per installare PSGML, usare il comando <command>yum</command>:"
+
+#: en_US/emacs.xml:37(userinput)
+#, no-wrap
+msgid "yum install psgml"
+msgstr "yum install psgml"
+
+#: en_US/emacs.xml:40(title)
+msgid "Setting Up Your <filename>.emacs</filename> File"
+msgstr "Configurare il file <filename>.emacs</filename>."
+
+#: en_US/emacs.xml:48(filename)
+msgid ".emacs"
+msgstr ".emacs"
+
+#: en_US/emacs.xml:51(para)
+msgid ""
+"For Emacs to parse your DocBook documents correctly, you must have a "
+"<filename>.emacs</filename> file. Cut and paste the following into your "
+"existing <filename>.emacs</filename> file or create a new one that contains "
+"the following lines:"
+msgstr ""
+"Per analizzare correttamente i propri documenti DocBook con Emacs, bisogna "
+"avere un file <filename>.emacs</filename>. Copiare e incollare le seguenti "
+"righe nel proprio file <filename>.emacs</filename> esistente o crearne uno "
+"nuovo che contiene le seguenti righe:"
+
+#: en_US/emacs.xml:181(para)
+msgid ""
+"If you have a wheel mouse and are using Emacs version 21, you can add the "
+"following to your <filename>.emacs</filename> file so your wheel will work "
+"in <application>Emacs</application>:"
+msgstr ""
+"Se si ha la rotella nel mouse e si sta usanto la versione 21 di Emacs, si "
+"può aggiungere nel file <filename>.emacs</filename> le rige seguenti così la "
+"rotella funzionerà in <application>Emacs</application>:"
+
+#: en_US/emacs.xml:192(para)
+msgid ""
+"If you are using the older version 20 of <application>Emacs</application>, "
+"add the following instead:"
+msgstr ""
+"Se invece si sta usando una versione precedente alla 20 di <application>Emacs</"
+"application>, aggiungere queste righe:"
+
+#: en_US/emacs.xml:221(title)
+msgid "Customizing Emacs"
+msgstr "Personalizzare Emacs"
+
+#: en_US/emacs.xml:225(secondary)
+msgid "customizing"
+msgstr "personalizzare"
+
+#: en_US/emacs.xml:229(filename)
+msgid ".Xresources"
+msgstr ".Xresources"
+
+#: en_US/emacs.xml:234(secondary)
+msgid "colors"
+msgstr "colori"
+
+#: en_US/emacs.xml:239(secondary)
+msgid "font"
+msgstr "font"
+
+#: en_US/emacs.xml:244(secondary)
+msgid "geometry"
+msgstr "geometria"
+
+#: en_US/emacs.xml:247(para)
+msgid ""
+"The colors, font, and geometry (default size of window) for Emacs in your "
+"<filename>~/.Xresources</filename> file. The format for the settings is "
+"<userinput>emacs.keyword:value</userinput>."
+msgstr ""
+"I colori, font e la geometria (dimensioni di base delle finestre) per Emacs "
+"sono nel file <filename>~/.Xresources</filename>. Il formato per le "
+"impostazioni è <userinput>emacs.keyword:value</userinput>."
+
+#: en_US/emacs.xml:253(para)
+msgid "The following is a sample <filename>~/.Xresources</filename> file."
+msgstr "Il seguente è un file di esempio <filename>~/.Xresources</filename>."
+
+#: en_US/emacs.xml:258(para)
+msgid ""
+"If you have other settings in your <filename>~/.Xresources</filename>, add "
+"the following to the end of the file."
+msgstr ""
+"Se si hanno altre impostazioni nel proprio <filename>~/.Xresources</"
+"filename>, aggiungere le seguenti righe in fondo al file."
+
+#: en_US/emacs.xml:270(para)
+msgid "After modifying this file, execute the following command:"
+msgstr "Dopo aver modificato questo file, eseguire il seguente comando:"
+
+#: en_US/emacs.xml:273(command)
+msgid "xrdb -merge ~/.Xresources"
+msgstr "xrdb -merge ~/.Xresources"
+
+#: en_US/emacs.xml:274(para)
+msgid "Then restart <application>Emacs</application> to apply the changes."
+msgstr "Poi riavviare <application>Emacs</application> per applicare i cambiamenti."
+
+#: en_US/emacs.xml:395(title)
+msgid "Basic Emacs Commands"
+msgstr "Comandi base Emacs"
+
+#: en_US/emacs.xml:397(para)
+msgid "The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key."
+msgstr "Il tasto <keycap>Meta</keycap> è di solito il tasto <keycap>Alt</keycap>."
+
+#: en_US/emacs.xml:403(title)
+msgid "Emacs Commands"
+msgstr "Comandi Emacs"
+
+#: en_US/emacs.xml:404(segtitle)
+msgid "Shortcut"
+msgstr "Scorciatoia"
+
+#: en_US/emacs.xml:405(segtitle)
+msgid "Description"
+msgstr "Descrizione"
+
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:412(keycap)
+#: en_US/emacs.xml:430(keycap) en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:443(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:458(keycap)
+#: en_US/emacs.xml:463(keycap) en_US/emacs.xml:468(keycap)
+#: en_US/emacs.xml:473(keycap) en_US/emacs.xml:478(keycap)
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:509(keycap)
+#: en_US/emacs.xml:514(keycap) en_US/emacs.xml:515(keycap)
+#: en_US/emacs.xml:520(keycap) en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap) en_US/emacs.xml:533(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "Ctrl"
+msgstr "Ctrl"
+
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:521(keycap) en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "c"
+msgstr "c"
+
+#: en_US/emacs.xml:413(keycap)
+msgid "p"
+msgstr "p"
+
+#: en_US/emacs.xml:407(seg) en_US/emacs.xml:508(seg) en_US/emacs.xml:514(seg)
+#: en_US/emacs.xml:520(seg) en_US/emacs.xml:532(seg) en_US/emacs.xml:540(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+
+#: en_US/emacs.xml:415(seg)
+msgid "Parse DTD"
+msgstr "Analizzare DTD"
+
+#: en_US/emacs.xml:431(keycap) en_US/emacs.xml:437(keycap)
+msgid "Shift"
+msgstr "Shift"
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:438(keycap)
+msgid ","
+msgstr ","
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:439(keycap)
+msgid "Tab"
+msgstr "Tab"
+
+#: en_US/emacs.xml:430(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+
+#: en_US/emacs.xml:433(seg)
+msgid "Display list of valid tags"
+msgstr "Visualizzare la lista dei tag validi"
+
+#: en_US/emacs.xml:436(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of "
+"tag, <placeholder-5/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, inserire inizio del tag, "
+"<placeholder-5/>"
+
+#: en_US/emacs.xml:440(seg)
+msgid "Complete the tag"
+msgstr "Completare il tag"
+
+#: en_US/emacs.xml:443(keycap)
+msgid "g"
+msgstr "g"
+
+#: en_US/emacs.xml:445(seg)
+msgid "Cancel a command in the minibuffer"
+msgstr "Cancellare un comando nel minibuffer"
+
+#: en_US/emacs.xml:449(keycap)
+msgid "/"
+msgstr "/"
+
+#: en_US/emacs.xml:448(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+
+#: en_US/emacs.xml:450(seg)
+msgid "Close tag"
+msgstr "Chiudere il tag"
+
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:533(keycap)
+msgid "a"
+msgstr "a"
+
+#: en_US/emacs.xml:455(seg)
+msgid "Move cursor to beginning of line"
+msgstr "Muovere il cursore all'inizio della riga"
+
+#: en_US/emacs.xml:458(keycap)
+msgid "e"
+msgstr "e"
+
+#: en_US/emacs.xml:460(seg)
+msgid "Move cursor to the end of the line"
+msgstr "Muovere il cursore alla fine della riga"
+
+#: en_US/emacs.xml:463(keycap)
+msgid "Home"
+msgstr "Home"
+
+#: en_US/emacs.xml:465(seg)
+msgid "Move cursor to the beginning of the file"
+msgstr "Muovere il cursore all'inizio del file"
+
+#: en_US/emacs.xml:468(keycap)
+msgid "End"
+msgstr "Fine"
+
+#: en_US/emacs.xml:470(seg)
+msgid "Move cursor to the end of the file"
+msgstr "Muovere il cursore alla fine del file"
+
+#: en_US/emacs.xml:473(keycap)
+msgid "k"
+msgstr "k"
+
+#: en_US/emacs.xml:475(seg)
+msgid "Cut line"
+msgstr "Tagliare la riga"
+
+#: en_US/emacs.xml:478(keycap)
+msgid "y"
+msgstr "y"
+
+#: en_US/emacs.xml:480(seg)
+msgid "Paste line"
+msgstr "Copiare la riga"
+
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:515(keycap)
+msgid "s"
+msgstr "s"
+
+#: en_US/emacs.xml:485(seg)
+msgid "Search forward in the file"
+msgstr "Cercare in avanti nel file"
+
+#: en_US/emacs.xml:488(keycap)
+msgid "r"
+msgstr "r"
+
+#: en_US/emacs.xml:490(seg)
+msgid "Search backwards in the file"
+msgstr "Cercare indietro nel file"
+
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap) en_US/emacs.xml:527(keycap)
+msgid "Meta"
+msgstr "Meta"
+
+#: en_US/emacs.xml:493(keycap)
+msgid "$"
+msgstr "$"
+
+#: en_US/emacs.xml:495(seg) en_US/emacs.xml:500(seg)
+msgid "Check spelling of current word"
+msgstr "Controllare l'ortografia della parola corrente"
+
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:514(keycap)
+#: en_US/emacs.xml:520(keycap)
+msgid "x"
+msgstr "x"
+
+#: en_US/emacs.xml:499(keycap) en_US/emacs.xml:504(keycap)
+msgid "Enter"
+msgstr "Invio"
+
+#: en_US/emacs.xml:498(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, "
+"<placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, "
+"<placeholder-3/>"
+
+#: en_US/emacs.xml:503(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, "
+"<placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, "
+"<placeholder-3/>"
+
+#: en_US/emacs.xml:505(seg)
+msgid "Check spelling of current buffer"
+msgstr "Controllare l'ortografia del buffer corrente"
+
+#: en_US/emacs.xml:509(keycap)
+msgid "f"
+msgstr "f"
+
+#: en_US/emacs.xml:511(seg)
+msgid "Open file"
+msgstr "Aprire file"
+
+#: en_US/emacs.xml:517(seg)
+msgid "Save file"
+msgstr "Salvare file"
+
+#: en_US/emacs.xml:523(seg)
+msgid "Exit <placeholder-1/> and prompt to save files if necessary"
+msgstr "Uscita <placeholder-1/> e prompt per salvare i file se necessario"
+
+#: en_US/emacs.xml:527(keycap)
+msgid "q"
+msgstr "q"
+
+#: en_US/emacs.xml:529(seg)
+msgid "Fill paragraph"
+msgstr "Riempire un paragrafo"
+
+#: en_US/emacs.xml:536(computeroutput)
+#, no-wrap
+msgid "url"
+msgstr "url"
+
+#: en_US/emacs.xml:537(computeroutput)
+#, no-wrap
+msgid "ulink"
+msgstr "ulink"
+
+#: en_US/emacs.xml:535(seg)
+msgid ""
+"Edit attributes for a tag (for example, you can edit the <placeholder-1/> "
+"attribute of the <placeholder-2/> tag)"
+msgstr ""
+"Modificare gli attributi per un tag (per esempio, si può modificare "
+"l'attributo <placeholder-1/> del tag <placeholder-2/>)"
+
+#: en_US/emacs.xml:544(seg)
+msgid "Exit edit attributes"
+msgstr "Uscita da modifica attributi"
+
+#: en_US/emacs.xml:550(title) en_US/emacs-nxml.xml:77(title)
+msgid "Examples"
+msgstr "Esempi"
+
+#: en_US/emacs.xml:552(para)
+msgid ""
+"The table or reference card of Emacs and PSGML commands can be confusing for "
+"beginners. This section provides some examples of how to use them."
+msgstr ""
+"La tabella o la carta di referenza per i comandi Emacs e PSGML può "
+"confondere i principianti. Questa sezione fornisce alcuni esempi su come "
+"usarli."
+
+#: en_US/emacs.xml:559(title)
+msgid "Tag Completion"
+msgstr "Completamento Tag"
+
+#: en_US/emacs.xml:563(para)
+msgid "This section assumes that you have already parsed the DTD file."
+msgstr "Questa sezione presume che si è già controllato il file DTD."
+
+#: en_US/emacs.xml:567(para)
+msgid ""
+"To avoid having to type a tag repeatedly, use the key combination "
+"<keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. "
+"At the bottom of the <application>Emacs</application> window, the following "
+"prompt appears:"
+msgstr ""
+"Per evitare di scrivere un tag ripetutamente, usare la combinazione di "
+"tasti <keycap>Ctrl</keycap>-<keycap>c</keycap>, seguita da <keycap><</"
+"keycap>. In fondo alla finestra di <application>Emacs</application>, apparirà il "
+"seguente prompt:"
+
+#: en_US/emacs.xml:574(prompt)
+msgid "Tag: <"
+msgstr "Tag: <"
+
+#: en_US/emacs.xml:576(para)
+msgid ""
+"To view a list of available tags, use either the <keycap>Tab</keycap> or "
+"<keycap>?</keycap>. If you know the first few letters of a tag, enter them, "
+"followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, "
+"that tag appears. If more than one completion exists, a complete list of "
+"possible tags appears."
+msgstr ""
+"Per vedere una lista di tag disponibili, usare o <keycap>Tab</keycap> o "
+"<keycap>?</keycap>. Se si conoscono le prime lettere del tag, inserirle, "
+"pigiare poi <keycap>Tab</keycap>. Se le lettere identificano unicamente un "
+"tag, verrà visualizzato questo tag. Se esiste più di un completamento, apparirà "
+"una lista completa di possibili tag."
+
+#: en_US/emacs.xml:585(para)
+msgid ""
+"If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, "
+"<keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the "
+"example below:"
+msgstr ""
+"Se si preme <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, "
+"<keycap><</keycap>, <keycap>k</keycap>, apparirà un prompt simile all'esempio qui "
+"sotto:"
+
+#: en_US/emacs.xml:602(title)
+msgid "Tag Closure"
+msgstr "Chiusura Tag"
+
+#: en_US/emacs.xml:604(para)
+msgid ""
+"After you open a tag, you must close it. The easiest way to close an open "
+"tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</"
+"keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most "
+"recently opened tag."
+msgstr ""
+"Dopo aver aperto un tag bisogna chiuderlo. Il modo più semplice per chiudere "
+"un tag aperto è usare la sequenza di tasti <keycombo><keycap>Ctrl</"
+"keycap><keycap>c</keycap></keycombo>, <keycap>/</keycap>. Questa sequenza "
+"chiude il tag aperto più recentemente."
+
+#: en_US/emacs.xml:616(title)
+msgid "Other Emacs Tasks"
+msgstr "Altri Compiti Emacs"
+
+#: en_US/emacs.xml:619(title)
+msgid "Working with One Window"
+msgstr "Lavorare con una finestra"
+
+#: en_US/emacs.xml:620(para)
+msgid ""
+"Sometimes in <application>Emacs</application>, the window becomes split, "
+"with tags completions or other text in an alternate window. To return to a "
+"single window, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+msgstr ""
+"A volte con <application>Emacs</application>, le finestre si dividono, "
+"con il completamento dei tag o altri testi in finestre alternate. Per "
+"ritornare in una singola finestra, usare la sequenza di tasti "
+"<keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycap>1</"
+"keycap>."
+
+#: en_US/emacs.xml:630(title)
+msgid "Saving Work"
+msgstr "Salvare il lavoro"
+
+#: en_US/emacs.xml:631(para)
+msgid ""
+"To save your work, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>s</keycap></keycombo>."
+msgstr ""
+"Per salvare il proprio lavoro usare la sequenza di tasti "
+"<keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, "
+"<keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>."
+
+#: en_US/emacs.xml:642(title)
+msgid "The \"Clear/Quit\" Command"
+msgstr "Il comando \"Clear/Quit\""
+
+#: en_US/emacs.xml:643(para)
+msgid ""
+"If the tag completion process becomes unwieldy or confusing, use the "
+"keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to "
+"exit back to the text. <application>Emacs</application> clears any prompts "
+"and returns to the buffer text."
+msgstr ""
+"Se il processo di completamento del tag diventa ingombrante o confuso, usare "
+"la scorciatoia <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> "
+"per tornare al testo. <application>Emacs</application> pulirà qualsiasi "
+"prompt e ritornerà sul buffer del testo."
+
+#: en_US/emacs.xml:653(title)
+msgid "Opening a new file"
+msgstr "Aprire un nuovo file"
+
+#: en_US/emacs.xml:654(para)
+msgid ""
+"To open a new file, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the "
+"<application>Emacs</application> window. Enter the file name, using "
+"<keycap>Tab</keycap> completion if desired, of the file you wish to open."
+msgstr ""
+"Per aprire un nuovo file, usare la sequenza di tasti <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>f</keycap></keycombo>. Apparirà un prompt in fondo alla "
+"finestra di <application>Emacs</application>. Inserire il nome del file, "
+"usare il completamento del file che si desidera aprire con <keycap>Tab</keycap>, "
+"se desiderato."
+
+#: en_US/emacs.xml:668(title)
+msgid "Closing <application>Emacs</application>"
+msgstr "Chiudere <application>Emacs</application>"
+
+#: en_US/emacs.xml:669(para)
+msgid ""
+"To close <application>Emacs</application> use the key sequence "
+"<keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, "
+"<keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have "
+"not saved your work, <application>Emacs</application> prompts you to save "
+"any changed files."
+msgstr ""
+"Per chiudere <application>Emacs</application> usare la scorciatoia "
+"<keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, "
+"<keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. Se non si è "
+"salvato il lavoro, <application>Emacs</application> avvisa di salvare "
+"qualsiasi file modificato."
+
+#: en_US/emacs.xml:687(title) en_US/emacs-nxml.xml:127(title)
+msgid "Additional Resources"
+msgstr "Risorse Aggiuntive"
+
+#: en_US/emacs.xml:689(para)
+msgid ""
+"Additional Emacs and PSGML references are available at the following "
+"locations:"
+msgstr ""
+"Riferimenti aggiuntivi ad Emacs e PSGML sono disponibili alle seguenti "
+"locazioni:"
+
+#: en_US/emacs.xml:697(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+msgid "Emacs Quick Reference Guide"
+msgstr "Guida rapida di riferimento a Emacs"
+
+#: en_US/emacs.xml:701(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+"La carta delle referenze di Emacs è allegata al pacchetto <filename>emacs</"
+"filename>. Si può stampare come referenza. —<filename>/usr/share/emacs/"
+"<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+
+#: en_US/emacs.xml:708(para)
+msgid ""
+"Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/"
+"usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+msgstr ""
+"Leggere <citetitle>Editing XML with Emacs and PSGML</citetitle> in "
+"<filename>/usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</"
+"filename>."
+
+#: en_US/emacs.xml:714(para)
+msgid ""
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—"
+"<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of "
+"Emacs commands for PSGML mode."
+msgstr ""
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—"
+"<citetitle>Emacs/PSGML Quick Reference</citetitle> è una tabella di "
+"riferimento dei comandi Emacs per la modalità PSGML."
+
+#: en_US/emacs.xml:723(citetitle)
+msgid "PSGML Tricks"
+msgstr "Trucchi PSGML"
+
+#: en_US/emacs-nxml.xml:11(title)
+msgid "Emacs and nXML Mode"
+msgstr "Emacs e modalità nXML"
+
+#: en_US/emacs-nxml.xml:14(primary) en_US/emacs-nxml.xml:51(primary)
+msgid "nXML"
+msgstr "nXML"
+
+#: en_US/emacs-nxml.xml:23(secondary)
+msgid "nXML mode"
+msgstr "modalità nXML"
+
+#: en_US/emacs-nxml.xml:26(para)
+msgid ""
+"You can also use the nXML mode available for <application>Emacs</"
+"application> to make it even easier to write in DocBook XML format. nXML "
+"mode provides context-sensitive editing using completion, real time validity "
+"error checking, syntax highlighting and indentation. All you need to do is "
+"install an RPM!!"
+msgstr ""
+"Si può anche usare la modalità nXML disponibile per <application>Emacs</"
+"application> che rende più facile scrivere nel formato DocBook XML. La "
+"modalità nXML fornisce modifiche sensibili al contesto usanto "
+"l'autocompletamento, controllo in tempo reale della validità di controllo errori, "
+"sintassi colorata e indentazione. Si necessita solo di installare un RPM!!"
+
+#: en_US/emacs-nxml.xml:35(title)
+msgid "Early stages"
+msgstr "Stadi iniziali"
+
+#: en_US/emacs-nxml.xml:36(para)
+msgid ""
+"Please be aware the nxml-mode for <application>Emacs</application> is quite "
+"new, so there are a few things that the advanced user might notice when "
+"using it with other documents types. If you keep an eye on the mailing-list, "
+"you can keep up to date with these, as well as ask questions. For more "
+"details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr ""
+"Per favore fare attenzione, la modalità nxml per <application>Emacs</"
+"application> è abbastanza nuova, quindi ci sono alcune cose che gli utenti "
+"avanzati potrebbero notare usandolo con altri tipi di documenti. "
+"Se si da una occhiata alla mailing-list, ci si può tenere aggiornati "
+"sull'argomento, come anche fare domande. Per maggiori dettagli, controllare "
+"<xref linkend=\"sn-emacs-nxml-readme\"/>."
+
+#: en_US/emacs-nxml.xml:48(title)
+msgid "Getting the nXML RPM"
+msgstr "Ottenere l'RPM di nXML"
+
+#: en_US/emacs-nxml.xml:52(secondary)
+msgid "RPM"
+msgstr "RPM"
+
+#: en_US/emacs-nxml.xml:56(primary)
+msgid "nXML RPM"
+msgstr "RPM di nXML"
+
+#: en_US/emacs-nxml.xml:59(para)
+msgid ""
+"To use nXML mode with emacs, you will need to install the nXML RPM available "
+"from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/"
+"\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www."
+"thaiopensource.com/download/\">http://www.thaiopensource.com/download/</"
+"ulink>. The source requires a lot more work to setup, therefore we will only "
+"be concentrating on the RPM version."
+msgstr ""
+"Per usare la modalità nXML con emacs, è necessario installare l'RPM di nXML "
+"disponibile dal sito web di <ulink url=\"http://people.redhat.com/twaugh/ftp/"
+"docbook/nxml-mode/\">Tim Waugh's</ulink> o dal sorgente <ulink url=\"http://"
+"www.thaiopensource.com/download/\">http://www.thaiopensource.com/download/</"
+"ulink>. Il sorgente richiede più lavoro per l'installazione, perciò ci si "
+"concentrerà solo sulla versione RPM."
+
+#: en_US/emacs-nxml.xml:69(para)
+msgid ""
+"Information on where to get the source is available in <xref linkend=\"sn-"
+"emacs-additional-resources\"/>."
+msgstr ""
+"Informazioni su dove ottenere il sorgente sono disponibili su <xref linkend="
+"\"sn-emacs-additional-resources\"/>."
+
+#: en_US/emacs-nxml.xml:79(para)
+msgid ""
+"Compared to PSGML mode there are only couple of commands that you need. This "
+"speeds up writing with <application>Emacs</application> considerably, which "
+"means you can concentrate more on the content of your article."
+msgstr ""
+"Rispetto alla modalità PSGML ci sono solo pochi comandi necessari. "
+"Questo aumenta notevolmente la velocità di scrittura con "
+"<application>Emacs</application>, ciò significa che ci si può concentrare "
+"maggiormente sui contenuti dell'articolo."
+
+#: en_US/emacs-nxml.xml:88(para)
+msgid ""
+"To create a tag, type <userinput><</userinput> and then type the keyword. "
+"To complete the keyword, press <command>Ctrl-Ret</command>, then add the "
+"last <userinput>></userinput>. To close a tag, type <userinput></</"
+"userinput>."
+msgstr ""
+"Per creare un tag, digitare <userinput><</userinput> e poi and inserire la "
+"parola chiave. Per completare la parola chiave, premere <command>Ctrl-Ret</"
+"command>, poi aggiungere l'ultimo <userinput>></userinput>. Per chiudere "
+"un tag, digitare <userinput></</userinput>."
+
+#: en_US/emacs-nxml.xml:97(para)
+msgid ""
+"When you open a document that doesn't have a DOCTYPE declaration at the top "
+"of the file, you will get this message and tag completion won't work because "
+"nXML will not know what format you are writing."
+msgstr ""
+"Quando si apre un documento che non ha una dichiarazione DOCTYPE all'inizio "
+"del file, si avrà questo messaggio e il completamento dei tag non funzionerà "
+"perchè nXML non sa in quale formato si sta scrivendo."
+
+#: en_US/emacs-nxml.xml:104(para)
+msgid ""
+"To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</"
+"command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/"
+"schema/</filename> and load <filename>docbook.rnc</filename>. "
+"<application>Emacs</application> will then prompt you to save it in the "
+"current working directory."
+msgstr ""
+"Per caricare lo schema, inserire <command>Ctrl-c</command>, poi <command>Ctrl-"
+"s</command> e navigare fino a <filename>/usr/share/emacs/site-lisp/nxml-mode/"
+"schema/</filename> e caricare <filename>docbook.rnc</filename>. "
+"<application>Emacs</application> indicherà di salvarlo nella cartella di lavoro corrente."
+
+#: en_US/emacs-nxml.xml:115(para)
+msgid ""
+"The commands already discussed are the only differences between using "
+"<application>Emacs</application> with PSGML mode and <application>Emacs</"
+"application> with nXML mode. You will still need to use all the same "
+"commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr ""
+"I comandi appena discussi sono le uniche differenze tra l'uso di "
+"<application>Emacs</application> in modalità PSGML e <application>Emacs</"
+"application> in modalità nXML. Si avrà ancora bisogno di usare gli stessi "
+"comandi discussi in <xref linkend=\"sn-emacs-basic-commands\"/>."
+
+#: en_US/emacs-nxml.xml:129(para)
+msgid ""
+"Additional Emacs and nXML references are available at the following "
+"locations:"
+msgstr "Ulteriori riferimenti ad Emacs e nXML sono disponibili ai seguenti indirizzi:"
+
+#: en_US/emacs-nxml.xml:136(ulink)
+msgid "http://www.thaiopensource.com/download/"
+msgstr "http://www.thaiopensource.com/download/"
+
+#: en_US/emacs-nxml.xml:137(citetitle)
+msgid "Author's download area"
+msgstr "Area download dell'autore"
+
+#: en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+
+#: en_US/emacs-nxml.xml:147(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+"La carta delle referenze di Emacs è allegata al pacchetto <filename>emacs</"
+"filename>. Si può stampare come referenza. —<filename>/usr/share/emacs/"
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+
+#: en_US/emacs-nxml.xml:157(title)
+msgid "nXML README File"
+msgstr "File README nXML"
+
+#: en_US/emacs-nxml.xml:161(para)
+msgid ""
+"This file can be found in the directory you extracted the source into, or in "
+"<filename>/usr/share/doc/nxml-mode-<replaceable><version></"
+"replaceable>/</filename> if you installed the RPM."
+msgstr ""
+"Questo file può essere trovato nella cartella dove si è estratto il "
+"sorgente, o in <filename>/usr/share/doc/nxml-mode-<replaceable><"
+"version></replaceable>/</filename> se si è installato l'RPM."
+
+#: en_US/emacs-nxml.xml:169(para)
+msgid "README file:"
+msgstr "file README:"
+
+#: en_US/emacs-nxml.xml:171(para)
+msgid ""
+"This is a new major mode for GNU Emacs for editing XML documents. It "
+"supports editing well-formed XML documents and also provides schema-"
+"sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr ""
+"Questo è un nuovo modo per le modifiche dei documenti XML con GNU Emacs. "
+"Esso supporta modifiche ben formate di documenti XML e inoltre fornisce una "
+"modifica sensibile allo schema dei documenti XML usando RELAX NG Compact Syntax."
+
+#: en_US/emacs-nxml.xml:177(para)
+msgid ""
+"To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs "
+"version 20 will not work properly, nor will XEmacs. To get started, do the "
+"following:"
+msgstr ""
+"Per usarlo, è necessaria la versione 21.x di GNU Emacs, preferibilmente "
+"21.3. La versione 20 di GNU Emacs non lavora correttamente, neppure XEmacs. Per "
+"iniziare, fare ciò che segue:"
+
+#: en_US/emacs-nxml.xml:184(command)
+msgid "M-x load-file RET rng-auto.el RET"
+msgstr "M-x load-file RET rng-auto.el RET"
+
+#: en_US/emacs-nxml.xml:187(para)
+msgid ""
+"This defines the necessary autoloads. Now, visit a file containing an XML "
+"document, and do the following:"
+msgstr ""
+"Questo definisce i caricamenti automatici necessari. Ora, aprire un file "
+"contente un documento XML e fare ciò che segue:"
+
+#: en_US/emacs-nxml.xml:192(command)
+msgid "M-x nxml-mode"
+msgstr "M-x nxml-mode"
+
+#: en_US/emacs-nxml.xml:195(para)
+msgid "Now do"
+msgstr "Ora fare"
+
+#: en_US/emacs-nxml.xml:200(command)
+msgid "C-h m"
+msgstr "C-h m"
+
+#: en_US/emacs-nxml.xml:203(para)
+msgid ""
+"For information on how to use nxml-mode. The beginnings of a manual are in "
+"nxml-mode.info. You can read this using:"
+msgstr ""
+"Per informazioni su come usare nxml-mode. L'inizio di un manuale è in nxml-"
+"mode.info. Si può leggere usando:"
+
+#: en_US/emacs-nxml.xml:209(command)
+msgid "C-u M-x info RET nxml-mode.info RET"
+msgstr "C-u M-x info RET nxml-mode.info RET"
+
+#: en_US/emacs-nxml.xml:212(para)
+msgid ""
+"It's also installed as an entry at the end of the top-level info directory. "
+"So you can read it with <command>C-h i</command> as usual."
+msgstr ""
+"E' inoltre installato come una voce alla fine del livello più alto della "
+"cartella info. Si può leggerlo con <command>C-h i</command> come sempre."
+
+#: en_US/emacs-nxml.xml:217(para)
+msgid ""
+"You can use <filename>test.valid.xml</filename> and <filename>test.invalid."
+"xml</filename> as examples of valid and invalid XML documents."
+msgstr ""
+"Si può usare <filename>test.valid.xml</filename> e <filename>test.invalid."
+"xml</filename> come esempi di un documento XML valido o non valido."
+
+#: en_US/emacs-nxml.xml:223(para)
+msgid "To get things automatically loaded each time you start Emacs, add:"
+msgstr ""
+"Per avere qualcosa caricata automaticamente ogni volta che si avvia Emacs, "
+"aggiungere:"
+
+#: en_US/emacs-nxml.xml:228(computeroutput)
+#, no-wrap
+msgid ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+msgstr ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+
+#: en_US/emacs-nxml.xml:232(para)
+msgid ""
+"to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-"
+"200YMMDD</computeroutput> is the directory containing the <filename>.elc</"
+"filename> files. Note that <filename>rng-auto.el</filename> does not load "
+"all of the nxml-mode code; it merely sets things up so that all the features "
+"of nxml-mode will be autoloaded properly. You should not try to autoload "
+"<filename>rng-auto.el</filename> itself."
+msgstr ""
+"al proprio <filename>.emacs</filename>, dove <computeroutput>~/nxml-mode-"
+"200YMMDD</computeroutput> è la cartella contente i file <filename>.elc</"
+"filename>. Notare che <filename>rng-auto.el</filename> non carica tutto il "
+"codice nxml-mode; imposta solamente le cose in modo che tutte le funzionalità della "
+"modalità nxml venganno autocaricate propriamente. Non si dovrebbe provare a "
+"caricare automaticamente <filename>rng-auto.el</filename> da soli."
+
+#: en_US/emacs-nxml.xml:242(para)
+msgid ""
+"To use nxml-mode automatically for files with an extension of <filename>xml</"
+"filename>, <filename>xsl</filename>, <filename>rng</filename> or "
+"<filename>xhtml</filename>, add the following to your <filename>.emacs</"
+"filename> file:"
+msgstr ""
+"Per usare automaticamente nxml-mode per i file con una estensione di "
+"<filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> "
+"o <filename>xhtml</filename>, aggiungere quanto segue al proprio file "
+"<filename>.emacs</filename>:"
+
+#: en_US/emacs-nxml.xml:250(computeroutput)
+#, no-wrap
+msgid ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+msgstr ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+
+#: en_US/emacs-nxml.xml:255(para)
+msgid ""
+"If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are "
+"running Emacs 21.3 or later, then I recommend enabling unify-8859-on-"
+"decoding-mode, by adding the following to your <filename>.emacs</filename> "
+"file:"
+msgstr ""
+"Se si modifica XML usando la codifica iso-8859-N invece che iso-8859-1 e si "
+"sta usando Emacs 21.3 o sucessivo, allora si raccomanda di abilitare unify-"
+"8859-on-decoding-mode, aggiungendo la seguente riga nel file <filename>."
+"emacs</filename>:"
+
+#: en_US/emacs-nxml.xml:263(computeroutput)
+#, no-wrap
+msgid "(unify-8859-on-decoding-mode)"
+msgstr "(unify-8859-on-decoding-mode)"
+
+#: en_US/emacs-nxml.xml:266(para)
+msgid ""
+"To get validation and schema-sensitive editing, you need a RELAX NG Compact "
+"Syntax (RNC) schema for you document. The schema directory includes some "
+"schemas for popular document types."
+msgstr ""
+"Per avere la validazione e la modifica schema-sensibile, si necessita uno "
+"schema RELAX NG Compact Syntax (RNC) per il documento. La cartella di "
+"schema include alcuni schemi per tipi popolari di documenti."
+
+#: en_US/emacs-nxml.xml:272(para)
+msgid ""
+"For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://"
+"relaxng.org/</ulink>."
+msgstr ""
+"Per maggiori informazioni su RELAX NG, fare riferimento a <ulink url=\"http://relaxng."
+"org/\">http://relaxng.org/</ulink>."
+
+#: en_US/emacs-nxml.xml:277(para)
+msgid ""
+"For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://"
+"relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial."
+"html</ulink>"
+msgstr ""
+"Per un tutorial su RELAX NG Compact Syntax, fare riferimento a <ulink url="
+"\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-"
+"tutorial.html</ulink>"
+
+#: en_US/emacs-nxml.xml:282(para)
+msgid ""
+"For automatically creating RNC schemas, I recommend my Trang program: <ulink "
+"url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee."
+"thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr ""
+"Per creare automanticamente schemi RNC, si raccomanda il programma Trang: "
+"<ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee."
+"thaiopensource.com/relaxng/trang.html\"</ulink>"
+
+#: en_US/emacs-nxml.xml:293(para)
+msgid "Infer an RNC schema from an instance document"
+msgstr "Dedurre uno schema RNC da un documento istanza"
+
+#: en_US/emacs-nxml.xml:298(para)
+msgid "Convert a DTD to an RNC schema"
+msgstr "Convertire uno schema DTD a uno RNC"
+
+#: en_US/emacs-nxml.xml:303(para)
+msgid "Convert a RELAX NG XML syntax schema to an RNC schema"
+msgstr "Convertire una sintassi dallo schema RELAX NG XML ad uno schema RNC"
+
+#: en_US/emacs-nxml.xml:288(para)
+msgid "You can use this to <placeholder-1/>"
+msgstr "Si può usare queto <placeholder-1/>"
+
+#: en_US/emacs-nxml.xml:310(para)
+msgid ""
+"To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also "
+"use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html"
+"\">http://www.pantor.com/download.html\"</ulink>."
+msgstr ""
+"Per convertire uno schema RELAX NG XML syntax (.rng) in uno schema RNC, si "
+"può usare il foglio di stile XSLT da <ulink url=\"http://www.pantor.com/"
+"download.html\">http://www.pantor.com/download.html\"</ulink>."
+
+#: en_US/emacs-nxml.xml:316(para)
+msgid ""
+"To convert a W3C XML Schema to an RNC schema, you need first to convert it "
+"to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on "
+"top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www."
+"dev.java.net/</ulink>."
+msgstr ""
+"Per convertire uno schema W3C XML in uno schema RNC, si deve prima "
+"convertire nella sintassi RELAX NG XML usando il convertitore di Sun RELAX "
+"NG rngconv (creato all'inizio di MSV). Fare riferimento a <ulink url=\"https://"
+"msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+
+#: en_US/emacs-nxml.xml:323(para)
+msgid "The file <filename>NEWS</filename> describes recent changes."
+msgstr "Il file <filename>NEWS</filename> descrive i cambiamenti recenti."
+
+#: en_US/emacs-nxml.xml:327(para)
+msgid ""
+"Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-"
+"mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug "
+"reports, discussion. I will announce all new versions there."
+msgstr ""
+"Per favore, usare la lista <ulink url=\"http://groups.yahoo.com/group/emacs-"
+"nxml-mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> per "
+"riportare bug e discussioni. Tutte le nuove versioni vengono annunciate qui."
+
+#: en_US/emacs-nxml.xml:333(para)
+msgid "James Clark"
+msgstr "James Clark"
+
+#: en_US/emacs-nxml.xml:336(para)
+msgid "jjc@@thaiopensource.com"
+msgstr "jjc@@thaiopensource.com"
+
+#: en_US/acknowledgments.xml:11(title)
+msgid "Acknowledgments"
+msgstr "Citazioni"
+
+#: en_US/acknowledgments.xml:13(para)
+msgid ""
+"This document is based on a document started by Tammy Fox (tfox at redhat."
+"com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray "
+"Fuller (jrfuller at redhat.com)."
+msgstr ""
+"Questo documento è basato su un documento iniziato da Tammy Fox (tfox at "
+"redhat.com) e dal contributo di Sandra Moore (smoore at redhat.com) e "
+"Johnray Fuller (jrfuller at redhat.com)."
+
+#: en_US/acknowledgments.xml:19(para)
+msgid ""
+"A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to "
+"fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr ""
+"Una patch da Roozbeh Pournader (roozbeh at sharif.edu) è stata applicata per "
+"risolvere alcuni errori e per spiegare che l'accesso CVS anonimo non "
+"permette commit."
+
+#: en_US/acknowledgments.xml:25(para)
+msgid ""
+"Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to "
+"add the trailing slashes to the <command>figure</command> tag example in "
+"<filename>docs-xml-tags.xml</filename>."
+msgstr ""
+"Patch da Gavin Henry (ghenry at suretecsystems.com) sono state applicate "
+"per aggiungere l'inseguimento degli slash ai tag di esempio<command>figure</"
+"command> in <filename>docs-xml-tags.xml</filename>."
+
+#: en_US/acknowledgments.xml:32(para)
+msgid ""
+"A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been "
+"applied to add <xref linkend=\"ch-vim\"/>."
+msgstr ""
+"Una patch da Joshua Daniel Franklin (joshuadfranklin at yahoo.com) è stata "
+"applicata per aggiungere <xref linkend=\"ch-vim\"/>."
+
+#: en_US/acknowledgments.xml:37(para)
+msgid ""
+"A patch from Karsten Wade (kwade at redhat.com) has been applied to add "
+"<xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields "
+"(stickster at gmail.com)."
+msgstr ""
+"Una patch da Karsten Wade (kwade at redhat.com) è stata applicata per "
+"aggiungere <xref linkend=\"sn-screenshots\"/>. E' stata modificata da Paul "
+"W. Frields (stickster at gmail.com)."
+
+#. This section has been removed.
+#. <para>
+#. A patch from Paul W. Frields (stickster at gmail.com) has been applied
+#. to add more explanation of the <command>screen</command> tag set to <xref
+#. linkend="sn-xml-tags-screen"></xref>.
+#. </para>
+#: en_US/acknowledgments.xml:50(para)
+msgid ""
+"A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been "
+"applied to more fully explaing the document building system."
+msgstr ""
+"Una patch da Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) è stata "
+"applicata per rendere il documento di costruzione del sistema più chiaro."
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: en_US/acknowledgments.xml:0(None)
+msgid "translator-credits"
+msgstr ""
+"Mario Santagiuliana <mario at marionline.it>, 2009."
+"Silvio Pierro <perplesso82 at gmail.com>, 2009."
+
+
+@
diff --git a/old-documentation-guide/po/ms.po,v b/old-documentation-guide/po/ms.po,v
new file mode 100644
index 0000000..6b02a2f
--- /dev/null
+++ b/old-documentation-guide/po/ms.po,v
@@ -0,0 +1,6552 @@
+head 1.2;
+access;
+symbols;
+locks; strict;
+comment @# @;
+
+
+1.2
+date 2008.05.12.06.13.11; author mdious; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.12.22.16.10.43; author szaman; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.2
+log
+ at updating pot and po files for noriko
+@
+text
+ at msgid ""
+msgstr ""
+"Project-Id-Version: documentation-guide\n"
+"POT-Creation-Date: 2008-05-13 02:06+1000\n"
+"PO-Revision-Date: 2007-12-23 00:10+0800\n"
+"Last-Translator: Sharuzzaman Ahmat Raslan <sharuzzaman@@myrealbox.com>\n"
+"Language-Team: Malay <translation-team-ms@@lists.sourceforge.net>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: en_US/rpm-info.xml:22(rights)
+msgid "OPL"
+msgstr ""
+
+#: en_US/rpm-info.xml:23(version)
+msgid "1.0"
+msgstr ""
+
+#: en_US/rpm-info.xml:26(year)
+msgid "2003"
+msgstr ""
+
+#: en_US/rpm-info.xml:27(year)
+msgid "2004"
+msgstr ""
+
+#: en_US/rpm-info.xml:28(year)
+msgid "2005"
+msgstr ""
+
+#: en_US/rpm-info.xml:29(year)
+msgid "2006"
+msgstr ""
+
+#: en_US/rpm-info.xml:30(year)
+msgid "2007"
+msgstr ""
+
+#: en_US/rpm-info.xml:31(year)
+msgid "2008"
+msgstr ""
+
+#: en_US/rpm-info.xml:32(holder)
+msgid "Red Hat, Inc. and others"
+msgstr ""
+
+#: en_US/rpm-info.xml:34(title)
+msgid "Fedora Documentation Guide"
+msgstr ""
+
+#: en_US/rpm-info.xml:35(desc)
+msgid "Guidelines and procedures for producing documentation for Fedora"
+msgstr ""
+
+#: en_US/rpm-info.xml:39(details)
+msgid "Add L10n chapter (#441190)"
+msgstr ""
+
+#: en_US/rpm-info.xml:43(details)
+msgid "Fix some organization and missing targets (#371531)"
+msgstr ""
+
+#: en_US/rpm-info.xml:47(details)
+msgid "Add link to DocBook XML help for Windows"
+msgstr ""
+
+#: en_US/rpm-info.xml:51(details)
+msgid "Add guidance on CVS web access and previewing work"
+msgstr ""
+
+#: en_US/rpm-info.xml:55(details)
+msgid "Add new chapter on publishing"
+msgstr ""
+
+#: en_US/rpm-info.xml:59(details)
+msgid "Include information on LINGUAS usage"
+msgstr ""
+
+#: en_US/rpm-info.xml:63(details)
+msgid "Remove unnecessary chapter on XML tags"
+msgstr ""
+
+#: en_US/rpm-info.xml:67(details)
+msgid "Assorted fixes to reflect newer version of reality"
+msgstr ""
+
+#: en_US/rpm-info.xml:74(details)
+msgid "Update to new content and build requirements"
+msgstr ""
+
+#: en_US/l10n.xml:13(title)
+msgid "Localization (L10n)"
+msgstr ""
+
+#: en_US/l10n.xml:14(para)
+msgid ""
+"This chapter discusses how translations are provided in Fedora documentation."
+msgstr ""
+
+#: en_US/l10n.xml:19(title)
+msgid "PO Files"
+msgstr ""
+
+#: en_US/l10n.xml:20(para)
+msgid ""
+"The cornerstone of translation when using XML files such as DocBook is the "
+"<firstterm>Portable Object</firstterm> or <acronym>PO</acronym> file. PO "
+"files provide a way for independent individuals or teams to translate "
+"documents. The Fedora Documentation Project toolchain includes rules for "
+"creating, updating, and maintaining these PO files."
+msgstr ""
+
+#: en_US/l10n.xml:28(para)
+msgid "PO files are usually found in two forms:"
+msgstr ""
+
+#: en_US/l10n.xml:33(para)
+msgid ""
+"the <filename class=\"extension\">.pot</filename> file, or <firstterm>PO "
+"Template</firstterm> (<acronym>POT</acronym>)"
+msgstr ""
+
+#: en_US/l10n.xml:41(para)
+msgid ""
+"the <filename class=\"extension\">.po</filename> file, or translation file "
+"(<acronym>PO</acronym>)"
+msgstr ""
+
+#: en_US/l10n.xml:47(para)
+msgid ""
+"A POT is, as the name suggests, a blank template for new translations. It "
+"contains some header information and a list of strings based on the content "
+"of the original XML file from which it was created. Translators do not alter "
+"the POT. The POT should only be changed after changes are made to the "
+"original XML file from which it is derived."
+msgstr ""
+
+#: en_US/l10n.xml:55(para)
+msgid ""
+"A translator who wishes to start working on a new language copies the POT to "
+"a locale-specific PO file. Then the translator uses any of a number of "
+"command-line or graphical tools to translate each of the strings in the "
+"list. A single POT is used to create many POs, one for each locale. These "
+"files are normally named for their locale code, such as <filename>de.po</"
+"filename>, <filename>it.po</filename>, and so on."
+msgstr ""
+
+#: en_US/l10n.xml:67(title)
+msgid "Creating or Updating a POT"
+msgstr ""
+
+#: en_US/l10n.xml:68(para)
+msgid ""
+"The POT is named after the document from which it is derived. If document "
+"named in the <filename>Makefile</filename>) is <filename>foo-tutorial.xml</"
+"filename>, the POT is named <filename>foo-tutorial.pot</filename>."
+msgstr ""
+
+#: en_US/l10n.xml:74(para)
+msgid "To create a new POT, use the following command:"
+msgstr ""
+
+#: en_US/l10n.xml:78(para)
+msgid ""
+"The same command is used to update the POT when the original XML sources "
+"change."
+msgstr ""
+
+#: en_US/l10n.xml:83(title)
+msgid "Keep POT Fresh"
+msgstr ""
+
+#: en_US/l10n.xml:84(para)
+msgid ""
+"Update the POT whenever the original XML changes. Many translators' tools "
+"automatically notify them of the change so they can update translations "
+"quickly."
+msgstr ""
+
+#: en_US/l10n.xml:92(title)
+msgid "Updating PO Files"
+msgstr ""
+
+#: en_US/l10n.xml:93(para)
+msgid ""
+"The translation files are created by the individual translators, and "
+"document maintainers do not normally need to create them. Translators update "
+"a list of locales in the <filename>po/LINGUAS</filename> file which defines "
+"all the locales for which translations exist."
+msgstr ""
+
+#: en_US/l10n.xml:100(para)
+msgid ""
+"Whenever the source XML files are updated, the maintainer must at least "
+"update the POT. It is helpful, however, to also merge these changes with the "
+"existing translations for those translators who are not automatically "
+"notified of changes."
+msgstr ""
+
+#: en_US/l10n.xml:107(title)
+msgid "Staying Current"
+msgstr ""
+
+#: en_US/l10n.xml:108(para)
+msgid ""
+"Always make sure your local copy of PO is fresh, using the CVS \"update\" "
+"command:"
+msgstr ""
+
+#: en_US/l10n.xml:114(para)
+msgid ""
+"To merge new changes into the existing PO translations, use the following "
+"command:"
+msgstr ""
+
+#: en_US/l10n.xml:121(title)
+msgid "Checking Statistics"
+msgstr ""
+
+#: en_US/l10n.xml:122(para)
+msgid "PO strings fall into three categories:"
+msgstr ""
+
+#: en_US/l10n.xml:127(para)
+msgid ""
+"<firstterm>translated</firstterm>, meaning the string has been handled by a "
+"translator and its source has not changed since then"
+msgstr ""
+
+#: en_US/l10n.xml:134(para)
+msgid ""
+"<firstterm>fuzzy</firstterm>, meaning the string has changed since it was "
+"last handled by a translator"
+msgstr ""
+
+#: en_US/l10n.xml:140(para)
+msgid ""
+"<firstterm>untranslated</firstterm>, meaning no translation has yet been "
+"provided for this string, or it is brand new"
+msgstr ""
+
+#: en_US/l10n.xml:146(para)
+msgid ""
+"To see a rough statistical tally of the string handling inside the PO for a "
+"module, use the following command:"
+msgstr ""
+
+#: en_US/l10n.xml:151(para)
+msgid ""
+"For each locale in the list, a count is shown of translated, fuzzy, and "
+"untranslated strings in that order. Tallies that only provide two numerals "
+"are usually translated followed by untranslated. Tallies with only one "
+"numeral are usually fully translated."
+msgstr ""
+
+#: en_US/l10n.xml:158(para)
+msgid ""
+"To see only a specific locale, append a dash and the locale code to the "
+"<command>postat</command> target:"
+msgstr ""
+
+#: en_US/publishing.xml:11(title)
+msgid "Publishing Official Documentation"
+msgstr ""
+
+#: en_US/publishing.xml:12(para)
+msgid ""
+"This chapter shows how to publish official Fedora Documentation Project work "
+"to the <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem> website. To publish official documentation, you must be approved "
+"to write to the web repository in CVS. Access for publishing is limited to "
+"contributors who have demonstrated capacity for working with CVS and other "
+"project tools. Once you have acquired and are comfortable with these skills, "
+"contributions as a publisher are welcome."
+msgstr ""
+
+#: en_US/publishing.xml:21(title)
+msgid "How the Site Works"
+msgstr ""
+
+#: en_US/publishing.xml:22(para)
+msgid ""
+"The <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> "
+"website is a set of PHP files and scripts. Publishers maintain these files "
+"in a CVS repository, and the website host retrieves them hourly to refresh "
+"the site. The host does not automatically use the newest content for the "
+"website. Instead, it pulls files with the CVS tag <systemitem>LIVE</"
+"systemitem> to populate the website."
+msgstr ""
+
+#: en_US/publishing.xml:30(para)
+msgid ""
+"Each publisher sets up a local testing website on an available Fedora "
+"system. This site, sometimes called a <firstterm>sandbox</firstterm>, allows "
+"the publisher to test and view changes to documents, and ensure stability on "
+"the public site."
+msgstr ""
+
+#: en_US/publishing.xml:37(title)
+msgid "Setting Up a Web Sandbox"
+msgstr ""
+
+#: en_US/publishing.xml:38(para)
+msgid ""
+"To test document publishing, first set up a web sandbox on a local Fedora "
+"system."
+msgstr ""
+
+#: en_US/publishing.xml:42(para)
+msgid "Install the \"Web Server\" package group:"
+msgstr ""
+
+#: en_US/publishing.xml:43(screen)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Web Server\"'"
+msgstr ""
+
+#: en_US/publishing.xml:46(para)
+msgid "Create a folder for the web server to access the site files."
+msgstr ""
+
+#: en_US/publishing.xml:48(screen)
+#, no-wrap
+msgid "su -c 'mkdir /var/www/fedora'"
+msgstr ""
+
+#: en_US/publishing.xml:51(para)
+msgid ""
+"Change the permissions on this directory to make it easier to access for "
+"your normal user account."
+msgstr ""
+
+#: en_US/publishing.xml:53(replaceable) en_US/publishing.xml:62(replaceable)
+#, fuzzy
+msgid "username"
+msgstr "Namapengguna:"
+
+#: en_US/publishing.xml:53(screen)
+#, no-wrap
+msgid "su -c 'chown <placeholder-1/> /var/www/fedora'"
+msgstr ""
+
+#: en_US/publishing.xml:56(para)
+msgid "Link to the new directory from your home directory."
+msgstr ""
+
+#: en_US/publishing.xml:57(screen)
+#, no-wrap
+msgid "ln -s /var/www/fedora ~/fedora"
+msgstr ""
+
+#: en_US/publishing.xml:60(para)
+msgid "Retrieve the web module from CVS."
+msgstr ""
+
+#: en_US/publishing.xml:61(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora\n"
+"cvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+msgstr ""
+
+#: en_US/publishing.xml:64(title)
+#, fuzzy
+msgid "Web CVS Access"
+msgstr "&Dalam pelayar web"
+
+#: en_US/publishing.xml:65(para)
+msgid ""
+"You must have access to the <systemitem>cvsweb</systemitem> module through "
+"the Fedora Account System to check in changes. If you do not have access, "
+"you can use <userinput><![CDATA[:pserver:anonymous]]></userinput> in place "
+"of <userinput><![CDATA[:ext:username]]></userinput> above. Visit the Fedora "
+"Account System at <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> "
+"for more information."
+msgstr ""
+
+#: en_US/publishing.xml:77(para)
+msgid ""
+"Edit the <filename>/etc/hosts</filename> file and add the following line "
+"<emphasis>after</emphasis> all other lines:"
+msgstr ""
+
+#: en_US/publishing.xml:80(screen)
+#, no-wrap
+msgid "127.0.0.1 docs.localhost.localdomain"
+msgstr ""
+
+#: en_US/publishing.xml:83(para)
+msgid ""
+"Create a file <filename>/etc/httpd/conf.d/fpo.conf</filename> with the "
+"following content:"
+msgstr ""
+
+#: en_US/publishing.xml:97(para)
+msgid ""
+"Create a file <filename>/etc/php.d/fpo.ini</filename> with the following "
+"content:"
+msgstr ""
+
+#: en_US/publishing.xml:99(screen)
+#, no-wrap
+msgid "include_path = \".:/var/www/fedora/web/include\""
+msgstr ""
+
+#: en_US/publishing.xml:102(para)
+msgid "Start the web server using the following command:"
+msgstr ""
+
+#: en_US/publishing.xml:103(screen)
+#, no-wrap
+msgid "su -c '/sbin/service httpd start'"
+msgstr ""
+
+#: en_US/publishing.xml:104(para)
+msgid "To have the web server start at every boot, use the following command:"
+msgstr ""
+
+#: en_US/publishing.xml:106(screen)
+#, no-wrap
+msgid "su -c '/sbin/chkconfig httpd on'"
+msgstr ""
+
+#: en_US/publishing.xml:109(para)
+msgid ""
+"To test the new sandbox site, open a Web browser and point it at the URL "
+"<uri>http://docs.localhost.localdomain</uri>."
+msgstr ""
+
+#: en_US/publishing.xml:113(title)
+#, fuzzy
+msgid "Creating a New Publication"
+msgstr "Baru me&nggunakan Template"
+
+#: en_US/publishing.xml:115(title)
+msgid "General Guidelines"
+msgstr ""
+
+#: en_US/publishing.xml:116(para)
+msgid ""
+"Follow these guidelines to ensure maintainability and ease of use for all "
+"publishers."
+msgstr ""
+
+#: en_US/publishing.xml:120(para)
+msgid ""
+"Use a short, descriptive name for the document directory. The module name "
+"from its Docs CVS location is usually appropriate. Good examples include "
+"<filename class=\"directory\">install-guide/</filename> or <filename class="
+"\"directory\">example-tutorial/</filename>."
+msgstr ""
+
+#: en_US/publishing.xml:127(para)
+msgid ""
+"Under the document directory, include a branch directory if the document "
+"references specific features of a particular Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:132(para)
+msgid ""
+"Under the branch directory (or document directory if no branches are "
+"necessary), make at least a <filename class=\"directory\">en_US/</filename> "
+"directory. Make an additional directory for each locale that has been fully "
+"translated."
+msgstr ""
+
+#: en_US/publishing.xml:141(title)
+msgid "Adding Content"
+msgstr ""
+
+#: en_US/publishing.xml:142(para)
+msgid ""
+"To add content, follow the procedure below. The following commands show an "
+"example of adding content for a new document called the <citetitle>Foobar "
+"Tutorial</citetitle>. This document includes a translation for the \"zz_XX\" "
+"locale and follows specifics of each Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:149(para)
+msgid "Make the required directory structure."
+msgstr ""
+
+#: en_US/publishing.xml:150(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"mkdir foobar-tutorial\n"
+"mkdir foobar-tutorial/f7\n"
+"mkdir foobar-tutorial/f7/{en_US,zz_XX}"
+msgstr ""
+
+#: en_US/publishing.xml:156(para)
+msgid ""
+"Build the HTML version of each translation of the document from Docs CVS."
+msgstr ""
+
+#: en_US/publishing.xml:158(replaceable)
+msgid "~/my-docs/foobar-tutorial/F-7/"
+msgstr ""
+
+#: en_US/publishing.xml:158(screen)
+#, no-wrap
+msgid ""
+"cd <placeholder-1/>\n"
+"make html-en_US html-zz_XX"
+msgstr ""
+
+#: en_US/publishing.xml:162(para)
+msgid "Copy the HTML content to the web sandbox."
+msgstr ""
+
+#: en_US/publishing.xml:163(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/foobar-tutorial/f7/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/"
+msgstr ""
+
+#: en_US/publishing.xml:168(para)
+msgid ""
+"Convert the HTML in each directory to PHP using the provided "
+"<filename>docbookhtml2php.py</filename> script."
+msgstr ""
+
+#: en_US/publishing.xml:177(para)
+msgid ""
+"Create any necessary <filename>index.php</filename> files for the overall "
+"directories. Each document and branch directory must have an <filename>index."
+"php</filename> file directing users to appropriate content. In this example, "
+"the necessary files are <filename>foobar-tutorial/index.php</filename> and "
+"<filename>foobar-tutorial/f7/index.php</filename>. You do not need to write "
+"these files from scratch. Copy an existing file from another document, and "
+"change it as needed to suit the new document."
+msgstr ""
+
+#: en_US/publishing.xml:187(para)
+msgid ""
+"Depending on content, publication may include changing a higher-level "
+"<filename>index.php</filename> file."
+msgstr ""
+
+#: en_US/publishing.xml:191(para)
+msgid ""
+"To test the changes in your sandbox, open a web browser and point it at "
+"<uri>http://docs.localhost.localdomain/</uri>."
+msgstr ""
+
+#: en_US/publishing.xml:195(title)
+#, fuzzy
+msgid "Always Test Changes"
+msgstr "Urus perubahan dalam dokumen"
+
+#: en_US/publishing.xml:196(para)
+msgid ""
+"<emphasis>Do not proceed further until you test all changes.</emphasis> "
+"Check that all links and index pages work."
+msgstr ""
+
+#: en_US/publishing.xml:204(title)
+msgid "Pushing Content to the Web"
+msgstr ""
+
+#: en_US/publishing.xml:205(para)
+msgid "To push your new content to the web site, follow this procedure:"
+msgstr ""
+
+#: en_US/publishing.xml:209(para)
+msgid "Add all the new file content to CVS."
+msgstr ""
+
+#: en_US/publishing.xml:210(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"cvs add foobar-tutorial\n"
+"cd foobar-tutorial\n"
+"cvs add f7\n"
+"cd f7\n"
+"cvs add en_US/ zz_XX/\n"
+"cvs add en_US/*php en_US/stylesheet-images/\n"
+"cvs add zz_XX/*php zz_XX/stylesheet-images/\n"
+"cvs add en_US/stylesheet-images/*png\n"
+"cvs add zz_XX/stylesheet-images/*png\n"
+"cd ../../\n"
+"cvs add foobar-tutorial/index.php\n"
+"cvs add foobar-tutorial/f7/index.php\n"
+msgstr ""
+
+#: en_US/publishing.xml:226(para)
+msgid ""
+"Commit the changes to CVS. Use a message that describes the document being "
+"committed."
+msgstr ""
+
+#: en_US/publishing.xml:228(replaceable)
+#, fuzzy
+msgid "message about document"
+msgstr "Cipta dokumen baru"
+
+#: en_US/publishing.xml:228(screen)
+#, no-wrap
+msgid "cvs ci -m '<placeholder-1/>' foobar-tutorial/"
+msgstr ""
+
+#: en_US/publishing.xml:231(para)
+msgid "Tag the content <systemitem>LIVE</systemitem> in CVS."
+msgstr ""
+
+#: en_US/publishing.xml:233(screen)
+#, no-wrap
+msgid "cvs tag -F LIVE foobar-tutorial/"
+msgstr ""
+
+#: en_US/vim.xml:13(title)
+#, fuzzy
+msgid "VIM and DocBook"
+msgstr "&Pengepala dan Footer"
+
+#: en_US/vim.xml:16(primary) en_US/vim.xml:33(primary)
+msgid "VIM"
+msgstr ""
+
+#: en_US/vim.xml:19(para)
+msgid ""
+"VIM has many features to help you write XML content such as DocBook, "
+"including syntax highlighting and customizable key bindings. Additionally, "
+"one can easily use external programs from VIM for features such as spell-"
+"checking. This chapter assumes you already know generally how to use VIM; if "
+"you want to learn how, try the <command>vimtutor</command> or by typing "
+"<userinput>:help tutor</userinput> from inside VIM."
+msgstr ""
+
+#: en_US/vim.xml:30(title)
+msgid "Setting Up Your <filename>.vimrc</filename> File"
+msgstr ""
+
+#: en_US/vim.xml:34(secondary) en_US/emacs.xml:44(secondary)
+#, fuzzy
+msgid "configuration file"
+msgstr "Extension &fail:"
+
+#: en_US/vim.xml:37(para)
+msgid ""
+"Below is a short sample <filename>.vimrc</filename> file that turns on some "
+"VIM features useful for editing SGML or XML content such as DocBook: "
+"<screen>\n"
+"<computeroutput>\" Turn off vi compatibility settings like limited undo\n"
+"set nocompatible\n"
+"\" Syntax highlighting based on file extension\n"
+"syntax on\n"
+"\" Automatically insert newlines after 80 characters\n"
+"set textwidth=80\n"
+"\" Automatically indent\n"
+"set autoindent\n"
+"\" Match SGML tags with %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+msgstr ""
+
+#: en_US/vim.xml:55(para)
+msgid ""
+"Some of these features require the <filename>vim-enhanced</filename> package "
+"to be installed. If you are using or the <filename>vim-minimal</filename> "
+"package, or if you are using an older version of VIM, you may not have the "
+"<filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still "
+"download <ulink url=\"http://vim.org/scripts/script.php?script_id=39"
+"\">matchit.zip from Vim.org</ulink> and load it separately."
+msgstr ""
+
+#: en_US/vim.xml:69(title)
+#, fuzzy
+msgid "Keymapping with VIM"
+msgstr "Aksara (dengan ruang):"
+
+#: en_US/vim.xml:71(para)
+msgid ""
+"VIM can speed up your DocBook creation by mapping frequently typed tags (or "
+"any words or phrases) onto short key combinations. By default, the keymap "
+"leader is the backslash (<literal>\\</literal>), but it can be redefined "
+"with a command like <userinput>let mapleader =\n"
+" \",\"</userinput>. There are two ways to use the following example; "
+"you can put it directly in your <filename>.vimrc</filename>, or you can save "
+"it in a separate file and load it with a <userinput>source</userinput> "
+"command in your <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\n"
+"\" skip ahead to after next tag without leaving insert mode\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\n"
+"\" common tags that start a new text block\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\n"
+"\" common tags that are placed inline\n"
+"\" use <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+"\" entities\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+msgstr ""
+
+#: en_US/vim.xml:110(para)
+msgid ""
+"Unfortunately, there is not currently a complete macro set for all DocBook "
+"commands, so you will need to define them yourself or customize the "
+"definitions in the examples from <xref linkend=\"sn-vim-additional-resources"
+"\"/>."
+msgstr ""
+
+#: en_US/vim.xml:119(title)
+msgid "Additional VIM Resources"
+msgstr ""
+
+#: en_US/vim.xml:121(para)
+msgid "Additional information about VIM may be found from:"
+msgstr ""
+
+#: en_US/vim.xml:127(para)
+msgid ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to "
+"Vi Improved (VIM)</citetitle>"
+msgstr ""
+
+#: en_US/vim.xml:134(para)
+msgid ""
+"The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick "
+"Reference Card</ulink>"
+msgstr ""
+
+#: en_US/vim.xml:140(ulink)
+#, fuzzy
+msgid "Vim as XML Editor"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/vim.xml:145(para)
+msgid ""
+"The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the "
+"<filename>vim-common</filename> package —<filename>/usr/share/vim/"
+"<replaceable><version></replaceable>/doc/intro.txt</filename> or type "
+"<userinput>:help intro</userinput> from within VIM"
+msgstr ""
+
+#: en_US/tutorial.xml:13(title)
+#, fuzzy
+msgid "The Layout of a Tutorial"
+msgstr "Kunci susunatur"
+
+#: en_US/tutorial.xml:14(para)
+msgid ""
+"In this chapter, you will find an example of a very short tutorial as used "
+"by the Fedora Documentation Project. This example is specific to the way the "
+"Docs Project uses DocBook XML. The example consists of a set of files used "
+"to hold the content and metadata for the tutorial."
+msgstr ""
+
+#: en_US/tutorial.xml:19(title)
+msgid "The Article"
+msgstr ""
+
+#: en_US/tutorial.xml:21(primary) en_US/tutorial.xml:56(primary)
+#, fuzzy
+msgid "tutorial layout"
+msgstr "Kunci susunatur"
+
+#: en_US/tutorial.xml:22(secondary)
+msgid "article"
+msgstr ""
+
+#: en_US/tutorial.xml:24(para)
+msgid "Below is a sample article:"
+msgstr ""
+
+#: en_US/tutorial.xml:54(title)
+msgid "The Metadata"
+msgstr ""
+
+#: en_US/tutorial.xml:57(secondary)
+msgid "metadata"
+msgstr ""
+
+#: en_US/tutorial.xml:59(para)
+msgid ""
+"The <filename>rpm-info.xml</filename> file contains all the required "
+"metadata for the document. This metadata includes title, authorship, "
+"licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates "
+"the content of this file:"
+msgstr ""
+
+#: en_US/tutorial.xml:65(title)
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr ""
+
+#: en_US/tutorial.xml:95(para)
+msgid ""
+"If you are not familiar with XML editing, copy and paste this file from an "
+"existing module and then edit the values for the various elements as "
+"appropriate. Consult Fedora Documentation Project members and help channels "
+"for more assistance if needed."
+msgstr ""
+
+#: en_US/style.xml:14(title)
+#, fuzzy
+msgid "Style"
+msgstr "Gaya"
+
+#: en_US/style.xml:16(para)
+msgid ""
+"Writing good technical documentation is not simply reproducing command lines "
+"and instruction sets. Good documentation is easy to read, understand, and "
+"translate, and presents a concise logical progression of concepts. Good "
+"documentation can also be defined by what it does <emphasis>not</emphasis> "
+"contain. Your tutorial should avoid:"
+msgstr ""
+
+#: en_US/style.xml:26(para)
+msgid "Excessive wordiness"
+msgstr ""
+
+#: en_US/style.xml:31(para)
+msgid "Unnecessary or undefined jargon"
+msgstr ""
+
+#: en_US/style.xml:36(para)
+#, fuzzy
+msgid "Grammatical or spelling errors"
+msgstr "&Sembunyi kesalahan ejaan dalam dokumen"
+
+#: en_US/style.xml:41(para)
+msgid "References to yourself or your experiences"
+msgstr ""
+
+#: en_US/style.xml:46(para)
+msgid "Remarks which might offend or confuse any reader"
+msgstr ""
+
+#: en_US/style.xml:51(para)
+msgid ""
+"This chapter contains style rules and guidelines for writing Fedora "
+"documentation. Guidelines are not the same as rules. It is acceptable to "
+"violate a guideline when it makes your material easier to understand. Follow "
+"guidelines whenever possible, but follow rules at all times. Assume any "
+"advice is a guideline unless identified otherwise."
+msgstr ""
+
+#: en_US/style.xml:62(title)
+msgid "Why Style Is Important"
+msgstr ""
+
+#: en_US/style.xml:64(para)
+msgid ""
+"Writing well comes naturally to almost no one. It is a skill that "
+"professional writers, even famous ones, must practice constantly. "
+"<firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> "
+"is the quality that separates elegant writing from the merely functional."
+msgstr ""
+
+#: en_US/style.xml:77(para)
+msgid ""
+"For example, refer to. <ulink url=\"http://www.online-literature.com/"
+"james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/"
+"ulysses/18/</ulink>. Please note that this example contains some mature "
+"themes and language, and is not suitable for all readers."
+msgstr ""
+
+#: en_US/style.xml:71(para)
+msgid ""
+"Elegance comes in many forms. In prose and poetry, elegant writing may not "
+"follow some (or any) common rules of grammar, syntax, or spelling. A good "
+"example is Episode 18, \"Penelope,\" in James Joyce's novel "
+"<citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long "
+"streams of words without punctuation to simulate a character's internal "
+"consciousness. By violating basic rules of grammar and syntax, Joyce "
+"simulates the disorganized but loosely connected thought patterns of the "
+"narrator."
+msgstr ""
+
+#: en_US/style.xml:89(para)
+msgid ""
+"Technical documentation, however, should always respect these rules. The "
+"more a document departs from standard language usage, the more difficult the "
+"material becomes for the reader. For example, readers may not be native "
+"speakers of the language used, or they might be reading a translation. If "
+"the writer uses slang, idioms, or jargon, a reader or translator may easily "
+"become confused. The following example compares two different written "
+"executions of the same idea:"
+msgstr ""
+
+#: en_US/style.xml:100(title)
+#, fuzzy
+msgid "Incorrect style"
+msgstr "Gaya Butang"
+
+#. I prefer "incorrect," because I think terms such as
+#. "problematic" are mealy-mouthed. They remind me of the late
+#. 1980's English textbook trend toward the politically correct yet
+#. wholly unhelpful "standard/nonstandard." But then, I tend to be
+#. dogmatic; it's probably my Catholic upbringing. [PWF]
+#: en_US/style.xml:108(para)
+msgid ""
+"So you made the changes I showed you in the last section. What's the next "
+"thing you should do? Just pop your thumb drive onto your system and read the "
+"<filename>messages</filename> log. When you see \"USB device found,\" then "
+"Bob's your uncle."
+msgstr ""
+
+#: en_US/style.xml:116(title)
+#, fuzzy
+msgid "Correct style"
+msgstr "Gaya Butang"
+
+#. I prefer "correct." See above. [PWF]
+#: en_US/style.xml:120(para)
+msgid ""
+"After you complete the configuration changes above, attach the USB removable "
+"media to your system. Use the <command>dmesg</command> command to examine "
+"the kernel message log. The message <computeroutput>USB device\n"
+"\t found</computeroutput> indicates that your device was installed "
+"successfully."
+msgstr ""
+
+#: en_US/style.xml:129(para)
+msgid ""
+"The first example is more conversational English, which is not appropriate "
+"for official written documentation. The second example is more formal, but "
+"as a result it is easier to comprehend, both for native readers and "
+"translators."
+msgstr ""
+
+#: en_US/style.xml:135(para)
+msgid ""
+"Following style rules and guidelines also makes readers more comfortable "
+"with a set of documents. Consistent style enhances the professional "
+"appearance of documentation, and its perceived value. On the other hand, "
+"lapses in punctuation or poor grammar negatively affect a reader's reaction "
+"to written material. A reader can feel that an otherwise correct technical "
+"document is lacking in authority, simply because it is poorly written. "
+"Readers feel at ease when they do not have to struggle to understand an "
+"author's use of language."
+msgstr ""
+
+#: en_US/style.xml:146(para)
+msgid ""
+"This chapter cannot possibly cover enough material to make every reader a "
+"good writer. Some manuals devoted entirely to writing style are themselves "
+"hundreds of pages long. This chapter provides enough guidelines for "
+"intermediate writers to understand style usage in technical documentation."
+msgstr ""
+
+#: en_US/style.xml:153(para)
+msgid ""
+"If you are not a practiced writer, whether of technical documentation or "
+"otherwise, you may benefit from other style resources. The following list is "
+"far from comprehensive, but provides a starting point:"
+msgstr ""
+
+#: en_US/style.xml:161(para)
+msgid ""
+"<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules "
+"and links to online versions can be found at: <ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>"
+msgstr ""
+
+#: en_US/style.xml:176(para)
+msgid ""
+"<citetitle>The Chicago Manual of Style</citetitle>, by the University of "
+"Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle."
+"org/\">http://www.chicagomanualofstyle.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:183(para)
+msgid ""
+"<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by "
+"Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/"
+"\">http://www.powa.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:190(para)
+msgid ""
+"There are many free software documentation projects which have developed "
+"their own style guidelines. This chapter, in fact, draws heavily on the "
+"<citetitle>GNOME Documentation Style Guidelines</citetitle> "
+"(<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</"
+"citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/"
+"\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr ""
+
+#: en_US/style.xml:203(title)
+msgid "Fundamental Concepts of Technical Documentation"
+msgstr ""
+
+#: en_US/style.xml:206(title)
+msgid "Bibliographic Information"
+msgstr ""
+
+#: en_US/style.xml:207(para)
+msgid "This section is drawn primarily from the <citetitle>GDSG</citetitle>."
+msgstr ""
+
+#. This section will reproduce mostly what is in Chapter 1 of
+#. the GDSG. There may be minor changes. FIXME: Make sure the
+#. appropriate front matter of the Documentation Guide includes
+#. attribution as required by the GNU FDL.
+#: en_US/style.xml:218(para)
+msgid ""
+"This chapter provides a brief introduction to writing technical "
+"documentation."
+msgstr ""
+
+#: en_US/style.xml:224(title)
+#, fuzzy
+msgid "General Style Requirements"
+msgstr "Tidak boleh buang gaya ini"
+
+#: en_US/style.xml:225(para)
+msgid ""
+"Technical writing for the Fedora Project imposes special constraints beyond "
+"the basic requirements of good prose. Good Fedora technical documentation "
+"has the following characteristics:"
+msgstr ""
+
+#: en_US/style.xml:232(term)
+msgid "Comprehensive"
+msgstr ""
+
+#: en_US/style.xml:234(para)
+msgid ""
+"Describe all of the functionality of a product. Do not omit functionality "
+"that you regard as irrelevant for the user."
+msgstr ""
+
+#: en_US/style.xml:242(term)
+msgid "Conforming"
+msgstr ""
+
+#: en_US/style.xml:249(para)
+msgid ""
+"Describe what you see. Do not describe what you want to see. Present your "
+"information in the order that users experience the subject matter."
+msgstr ""
+
+#: en_US/style.xml:257(term)
+#, fuzzy
+msgid "Clear"
+msgstr "Padam"
+
+#: en_US/style.xml:259(para)
+msgid ""
+"Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>) to help make your writing clear."
+msgstr ""
+
+#: en_US/style.xml:275(term)
+msgid "Consistent"
+msgstr ""
+
+#: en_US/style.xml:277(para)
+msgid ""
+"Use agreed vocabulary throughout your documentation. Use the same vocabulary "
+"as other writers who are working on related documentation."
+msgstr ""
+
+#: en_US/style.xml:285(term)
+msgid "Concise"
+msgstr ""
+
+#: en_US/style.xml:287(para)
+msgid ""
+"Review your work frequently as you write your document. Ask yourself which "
+"words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for "
+"specific guidelines."
+msgstr ""
+
+#: en_US/style.xml:297(title)
+msgid "Golden Rules"
+msgstr ""
+
+#: en_US/style.xml:298(para)
+msgid ""
+"This section contains some basic style guidelines. Subsequent sections in "
+"this chapter expand on these guidelines to give more detailed guidance."
+msgstr ""
+
+#: en_US/style.xml:305(term)
+msgid "Golden Rule 1: Be brief"
+msgstr ""
+
+#: en_US/style.xml:309(para)
+msgid "Limit each sentence to fewer than 25 words."
+msgstr ""
+
+#: en_US/style.xml:314(para)
+msgid "Limit each procedure step to 23 words."
+msgstr ""
+
+#: en_US/style.xml:320(title)
+#, fuzzy
+msgid "Incorrect: Too long"
+msgstr "Semak dokumen untuk kesalahan ejaan"
+
+#: en_US/style.xml:321(para)
+msgid ""
+"Under normal operating conditions, the kernel does not always immediately "
+"write file data to the disks, storing it in a memory buffer and then "
+"periodically writing to the disks to speed up operations."
+msgstr ""
+
+#: en_US/style.xml:328(title)
+msgid "Correct: Less wordy"
+msgstr ""
+
+#: en_US/style.xml:329(para)
+msgid ""
+"Normally, the kernel stores the data in memory prior to periodically writing "
+"the data to the disk."
+msgstr ""
+
+#: en_US/style.xml:337(term)
+msgid "Golden Rule 2: Be organized"
+msgstr ""
+
+#: en_US/style.xml:341(para)
+msgid "Limit each paragraph to one topic."
+msgstr ""
+
+#: en_US/style.xml:346(para)
+msgid "Limit each sentence to one idea."
+msgstr ""
+
+#: en_US/style.xml:351(para)
+msgid "Limit each procedure step to one action."
+msgstr ""
+
+#: en_US/style.xml:357(title)
+#, fuzzy
+msgid "Incorrect: Disorganized topics"
+msgstr "Semak dokumen untuk kesalahan ejaan"
+
+#: en_US/style.xml:358(para)
+msgid ""
+"The <application>Workspace Switcher</application> applet helps you navigate "
+"all of the virtual desktops available on your system. The X Window system, "
+"working in hand with a piece of software called a <emphasis>window manager</"
+"emphasis>, allows you to create more than one virtual desktop, known as "
+"<emphasis>workspaces</emphasis>, to organize your work, with different "
+"applications running in each workspace. The <application>Workspace Switcher</"
+"application> applet is a navigational tool to get around the various "
+"workspaces, providing a miniature road map in the GNOME panel showing all "
+"your workspaces and allowing you to switch easily between them."
+msgstr ""
+
+#: en_US/style.xml:375(title)
+msgid "Correct: Organized topics"
+msgstr ""
+
+#: en_US/style.xml:376(para)
+msgid ""
+"Use the <application>Workspace Switcher</application> to add new "
+"<emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different "
+"applications in each workspace. The <application>Workspace Switcher</"
+"application> applet provides a miniature map that shows all of your "
+"workspaces. You can use the <application>Workspace Switcher</application> "
+"applet to switch between workspaces."
+msgstr ""
+
+#: en_US/style.xml:388(para)
+msgid ""
+"Plan the order of paragraphs before you start writing. Decide which topic "
+"you want to cover in each paragraph."
+msgstr ""
+
+#: en_US/style.xml:396(term)
+msgid "Golden Rule 3: Be demonstrative"
+msgstr ""
+
+#: en_US/style.xml:398(para)
+msgid ""
+"Use explicit examples to demonstrate how an application works. Provide "
+"instructions rather than descriptions."
+msgstr ""
+
+#: en_US/style.xml:403(title)
+msgid "Incorrect: Describes but does not demonstrate"
+msgstr ""
+
+#: en_US/style.xml:405(para)
+msgid ""
+"There is a text box that you can use to find out the definition of a word."
+msgstr ""
+
+#: en_US/style.xml:411(title)
+msgid "Correct: Demonstrates usage"
+msgstr ""
+
+#: en_US/style.xml:412(para)
+msgid ""
+"To request a definition of a word, type the word in the text box, then "
+"select <guilabel>Lookup</guilabel>."
+msgstr ""
+
+#: en_US/style.xml:418(para)
+msgid ""
+"Do not apply this guideline too rigidly. Sometimes you must explain how "
+"software works to support your how-to examples."
+msgstr ""
+
+#: en_US/style.xml:427(term)
+msgid "Golden Rule 4: Be objective"
+msgstr ""
+
+#: en_US/style.xml:429(para)
+msgid "Write in a neutral tone."
+msgstr ""
+
+#: en_US/style.xml:433(title)
+msgid "Incorrect: Sentence takes sides"
+msgstr ""
+
+#: en_US/style.xml:434(para)
+msgid "The applet is a handy little screen grabber."
+msgstr ""
+
+#: en_US/style.xml:439(title)
+msgid "Correct: Sentence is objective"
+msgstr ""
+
+#: en_US/style.xml:440(para)
+msgid "Use the applet to take screenshots."
+msgstr ""
+
+#: en_US/style.xml:452(title)
+msgid "Tone"
+msgstr ""
+
+#: en_US/style.xml:453(para)
+msgid ""
+"Inappropriate tone hinders reader access to information. A neutral tone free "
+"of opinion or personal flavor improves the reader's comprehension. Neutral "
+"tone helps writers to work in parallel on a large technical documentation "
+"project. Furthermore, additional writers may join the project at any time. "
+"Use of a neutral tone helps to achieve consistency across a documentation "
+"set, and thereby facilitates user access to information. The best way to "
+"achieve a common, neutral tone is to apply the following principles:"
+msgstr ""
+
+#: en_US/style.xml:466(term)
+msgid "Avoid humor"
+msgstr ""
+
+#: en_US/style.xml:468(para)
+msgid ""
+"Humor distracts from the information you are trying to provide. Humor also "
+"makes documentation difficult to translate. Stay factual."
+msgstr ""
+
+#: en_US/style.xml:476(term)
+msgid "Avoid personal opinions"
+msgstr ""
+
+#: en_US/style.xml:478(para)
+msgid ""
+"Whether you think a function is useful or woeful is irrelevant. Report the "
+"function to the user, with instructions about how to use the function. Stay "
+"accurate."
+msgstr ""
+
+#: en_US/style.xml:487(term)
+#, fuzzy
+msgid "Avoid colloquial language"
+msgstr "Bahasa Antaramuka Pengguna"
+
+#: en_US/style.xml:489(para)
+msgid ""
+"Colloquial language is difficult to translate and usually culture-specific. "
+"Stay neutral."
+msgstr ""
+
+#: en_US/style.xml:496(term)
+msgid "Avoid topical expressions"
+msgstr ""
+
+#: en_US/style.xml:498(para)
+msgid ""
+"An expression that is in common use today might convey something completely "
+"different tomorrow. Stay technical."
+msgstr ""
+
+#: en_US/style.xml:505(term)
+msgid "Avoid aspirational statements"
+msgstr ""
+
+#: en_US/style.xml:507(para)
+msgid ""
+"Statements about the future developments of a product do not belong in "
+"technical documentation. Write about what you see right now. Stay real."
+msgstr ""
+
+#: en_US/style.xml:517(title)
+#, fuzzy
+msgid "Reaching the Right Audience"
+msgstr "Jajar kanan perenggan"
+
+#: en_US/style.xml:518(para)
+msgid ""
+"All of the decisions that you make about the structure and content of a "
+"manual follow from an understanding of the audience. Consider how the "
+"audience accesses the documentation, what sort of information the audience "
+"needs, and the experience level of the audience. Usually, you need to create "
+"documentation that is suitable for different audiences. The following "
+"sections introduce some of the audience-related topics you need to consider."
+msgstr ""
+
+#: en_US/style.xml:530(title)
+#, fuzzy
+msgid "User Motivation"
+msgstr "Antaramuka Pengguna"
+
+#: en_US/style.xml:531(para)
+msgid ""
+"Do not waste the time of the user who looks for information in your "
+"documentation. Users do not read technical documentation for entertainment. "
+"Users usually have specific questions. You need to give clear answers to "
+"those questions."
+msgstr ""
+
+#: en_US/style.xml:539(title)
+#, fuzzy
+msgid "New Users"
+msgstr "&Tetingkap Baru"
+
+#: en_US/style.xml:540(para)
+msgid ""
+"New users to Fedora are likely to consult online tutorials for guidance "
+"about unfamiliar applications or functionality. Each tutorial should contain "
+"enough introductory information to tell new users how to start using the "
+"relevant functions. Each tutorial should also contain enough usage "
+"instructions to tell users the different actions that they can perform with "
+"the command or function. Keep these instructions task-oriented. Do not "
+"describe GUI screens, dialogs, and dialog elements in a tutorial, unless "
+"there is an unusual feature that affects your instructions."
+msgstr ""
+
+#: en_US/style.xml:554(title)
+msgid "Experienced Users"
+msgstr ""
+
+#: en_US/style.xml:555(para)
+msgid ""
+"Experienced users are more likely to use documentation as a reference. The "
+"documentation therefore needs to be complete, well-organized, and in the "
+"case of printed manuals, well-indexed."
+msgstr ""
+
+#: en_US/style.xml:563(title)
+msgid "Do Not Offend Your Audience"
+msgstr ""
+
+#: en_US/style.xml:564(para)
+msgid ""
+"To avoid offending your readers, apply the following guidelines to your "
+"documentation:"
+msgstr ""
+
+#: en_US/style.xml:570(term)
+#, fuzzy
+msgid "Avoid insider language"
+msgstr "Bahasa Antaramuka Pengguna"
+
+#: en_US/style.xml:572(para)
+msgid ""
+"Insider language includes both undefined jargon and the tendency of the "
+"computer community to shorten words. For example, use the term "
+"<literal>documentation</literal> instead of the term <literal>docs</"
+"literal>. A term may be jargon if it fails all the following conditions:"
+msgstr ""
+
+#: en_US/style.xml:581(para)
+msgid ""
+"The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> "
+"(<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora."
+"redhat.com/docs/jargon-buster/</ulink>)."
+msgstr ""
+
+#: en_US/style.xml:588(para)
+msgid ""
+"The term does not appear in the <citetitle>American Heritage Dictionary</"
+"citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby."
+"com/61/ </ulink>)."
+msgstr ""
+
+#: en_US/style.xml:596(para)
+msgid ""
+"The term does not appear in the glossary of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:602(para)
+msgid ""
+"The term is not defined in the body text of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:611(term)
+msgid "Avoid gender-specific language"
+msgstr ""
+
+#: en_US/style.xml:613(para)
+msgid ""
+"Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</"
+"literal> do not exist. There is no need to identify gender in your "
+"instructions."
+msgstr ""
+
+#: en_US/style.xml:621(term)
+msgid "Avoid culture-specific language"
+msgstr ""
+
+#: en_US/style.xml:623(para)
+msgid ""
+"There is little point in giving an example that everyone in your town knows "
+"about, but is a complete mystery to everyone else in the world."
+msgstr ""
+
+#: en_US/style.xml:631(term)
+msgid "Avoid talking down to your reader"
+msgstr ""
+
+#: en_US/style.xml:633(para)
+msgid ""
+"There are few experiences more irritating for a user than documentation that "
+"says an action is easy or quick, when in fact the user cannot complete the "
+"action. Do not qualify or prejudge actions."
+msgstr ""
+
+#: en_US/style.xml:642(para)
+msgid ""
+"Other parts of this guide discuss in more detail tone and language usage "
+"that can cause offense."
+msgstr ""
+
+#: en_US/style.xml:653(title)
+msgid "Grammar and Usage Guidelines"
+msgstr ""
+
+#: en_US/style.xml:656(title)
+msgid "Bibliographical Information"
+msgstr ""
+
+#: en_US/style.xml:657(para)
+msgid ""
+"This section is drawn partly from the <citetitle>GDSG</citetitle>, and "
+"partly from <citetitle>The Elements of Style</citetitle>, updated as "
+"necessary for the needs of 21st-century technical documentation writers."
+msgstr ""
+
+#. FIXME: Again, check attribution viz. GNU FDL. This will be more work
+#. than the previous section.
+#: en_US/style.xml:668(para)
+msgid ""
+"This section contains an alphabetical list of grammar and usage guidelines "
+"for use in Fedora documentation. Many of these guidelines are only "
+"applicable to English-language usage, refer to the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of "
+"Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/"
+"cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:679(term)
+msgid "Abbreviations"
+msgstr ""
+
+#: en_US/style.xml:681(para)
+msgid ""
+"A shortened form of a word or phrase that takes the place of the full word "
+"or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, "
+"<literal>p.m.</literal>, and so on. Apply the following rules when you use "
+"abbreviations:"
+msgstr ""
+
+#: en_US/style.xml:689(para)
+msgid ""
+"Avoid creating new abbreviations. Unfamiliar abbreviations can confuse "
+"rather than clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:695(para)
+msgid "Do not explain or expand familiar abbreviations."
+msgstr ""
+
+#: en_US/style.xml:700(para)
+msgid "Do not include familiar abbreviations in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:706(para)
+msgid ""
+"For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other "
+"words\" and <literal>e.g.</literal> for \"for example\", do not use the "
+"abbreviation. Spell out the entire phrase."
+msgstr ""
+
+#: en_US/style.xml:715(term)
+msgid "Adjectives"
+msgstr ""
+
+#: en_US/style.xml:717(para)
+msgid ""
+"Use adjectives with caution. If an adjective is necessary to differentiate "
+"between items, then use adjectives. In all cases, test whether the phrase "
+"can stand alone without the adjective."
+msgstr ""
+
+#: en_US/style.xml:726(term)
+msgid "Acronyms"
+msgstr ""
+
+#: en_US/style.xml:728(para)
+msgid ""
+"A term that represents a multi-word term. Typically, acronyms are formed in "
+"the following ways:"
+msgstr ""
+
+#: en_US/style.xml:734(para)
+msgid ""
+"From the first letters of each word in a compound term, for example Table of "
+"Contents (TOC)."
+msgstr ""
+
+#: en_US/style.xml:740(para)
+msgid ""
+"From recognizable parts of a compound term, such as GNU Object Model "
+"Environment (GNOME)."
+msgstr ""
+
+#: en_US/style.xml:746(para)
+msgid "Apply the following rules when you use acronyms:"
+msgstr ""
+
+#: en_US/style.xml:751(para)
+msgid ""
+"On the first occurrence of an acronym, spell out the full term, with the "
+"acronym in parentheses."
+msgstr ""
+
+#: en_US/style.xml:757(para)
+msgid ""
+"Do not spell out the full compound for well-known acronyms, unless you think "
+"the information is useful for readers."
+msgstr ""
+
+#: en_US/style.xml:764(para)
+msgid ""
+"Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than "
+"clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:770(para)
+msgid ""
+"Write the acronym in uppercase letters, unless there is a compelling case "
+"for lowercase."
+msgstr ""
+
+#: en_US/style.xml:776(para)
+msgid "Include the acronym and the full term in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:785(term)
+msgid "Adverbs"
+msgstr ""
+
+#: en_US/style.xml:787(para)
+msgid ""
+"Use adverbs with caution. If an adverb is necessary to qualify the function "
+"of a component, then use an adverb. In all cases, test whether the phrase "
+"can stand alone without the adverb. Classic superfluous adverbs "
+"<literal>simply</literal>, <literal>easily</literal>, <literal>quickly</"
+"literal>."
+msgstr ""
+
+#: en_US/style.xml:798(term)
+msgid "Anthropomorphism"
+msgstr ""
+
+#: en_US/style.xml:802(para)
+msgid "Do not apply emotions, desires, or opinions to software applications."
+msgstr ""
+
+#: en_US/style.xml:808(para)
+msgid ""
+"Do not apply a sense of location or dimension to a software application. A "
+"user can not be \"in\" a text editor."
+msgstr ""
+
+#: en_US/style.xml:818(term)
+msgid "Articles"
+msgstr ""
+
+#: en_US/style.xml:820(para)
+msgid ""
+"Do not use the definite article <literal>the</literal> to begin any of the "
+"following items:"
+msgstr ""
+
+#: en_US/style.xml:826(para)
+msgid "Manual titles"
+msgstr ""
+
+#: en_US/style.xml:831(para)
+#, fuzzy
+msgid "Chapter titles"
+msgstr "Heading Bab"
+
+#: en_US/style.xml:836(para) en_US/style.xml:1239(term)
+msgid "Headings"
+msgstr ""
+
+#: en_US/style.xml:841(para)
+msgid "Figure captions"
+msgstr ""
+
+#: en_US/style.xml:846(para)
+#, fuzzy
+msgid "Table captions"
+msgstr "&Automuat Jadual"
+
+#: en_US/style.xml:851(para)
+msgid "Callouts"
+msgstr ""
+
+#: en_US/style.xml:859(term)
+msgid "Apostrophe"
+msgstr ""
+
+#: en_US/style.xml:861(para)
+msgid "Do not use apostrophes except where absolutely required"
+msgstr ""
+
+#: en_US/style.xml:866(para)
+msgid "Do not use apostrophes to denote possession."
+msgstr ""
+
+#: en_US/style.xml:871(para)
+msgid "Do not use apostrophes to denote contractions."
+msgstr ""
+
+#: en_US/style.xml:876(para)
+msgid "Do not use apostrophes to denote plurals."
+msgstr ""
+
+#: en_US/style.xml:882(title)
+#, fuzzy
+msgid "Incorrect: Apostrophes"
+msgstr "Katalaluan Tidak Betul"
+
+#: en_US/style.xml:885(para)
+msgid ""
+"the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+msgstr ""
+
+#: en_US/style.xml:891(para)
+msgid "don't use the default option"
+msgstr ""
+
+#: en_US/style.xml:896(para)
+msgid "several SCSI disk's"
+msgstr ""
+
+#: en_US/style.xml:903(title)
+#, fuzzy
+msgid "Correct: No apostrophes"
+msgstr "(tiada cadangan ejaan)"
+
+#: en_US/style.xml:906(para)
+msgid ""
+"the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</"
+"guimenu>"
+msgstr ""
+
+#: en_US/style.xml:912(para)
+msgid "do not use the default option"
+msgstr ""
+
+#: en_US/style.xml:917(para)
+msgid "several SCSI disks"
+msgstr ""
+
+#: en_US/style.xml:926(term)
+msgid "Brackets"
+msgstr ""
+
+#: en_US/style.xml:930(para)
+msgid ""
+"Do not use brackets [such as these] as a substitute for parentheses (such as "
+"these)."
+msgstr ""
+
+#: en_US/style.xml:936(para)
+msgid "Use brackets for optional command line entries."
+msgstr ""
+
+#: en_US/style.xml:941(para)
+msgid ""
+"Do not use angle brackets to indicate variables in text, instead use the "
+"<sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref "
+"linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+msgstr ""
+
+#: en_US/style.xml:953(term)
+msgid "Capitalization"
+msgstr ""
+
+#: en_US/style.xml:955(para)
+msgid "Capitalize in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:960(para)
+msgid "All letters in acronyms, unless the acronym is a well-known exception"
+msgstr ""
+
+#: en_US/style.xml:966(para)
+msgid "Initial letter of the first word in a list"
+msgstr ""
+
+#: en_US/style.xml:971(para)
+msgid "Initial letter of the first word in a callout"
+msgstr ""
+
+#: en_US/style.xml:976(para)
+msgid "Initial letter of a key name, such as the <keycap>Shift</keycap> key"
+msgstr ""
+
+#: en_US/style.xml:982(para)
+#, fuzzy
+msgid "Initial letter of a sentence"
+msgstr "Nilai Notaakhir permulaan"
+
+#: en_US/style.xml:986(title)
+#, fuzzy
+msgid "Command Names"
+msgstr "Arahan pencetak: "
+
+#: en_US/style.xml:987(para)
+msgid ""
+"Avoid starting a sentence with a command name or application name that has a "
+"lowercase initial letter."
+msgstr ""
+
+#: en_US/style.xml:994(para)
+msgid "Initial letter of a complete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:999(para)
+msgid "Do not capitalize in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1004(para)
+msgid "A compound term that is followed by an abbreviation or an acronym"
+msgstr ""
+
+#: en_US/style.xml:1010(para)
+msgid "When you want to emphasize something"
+msgstr ""
+
+#: en_US/style.xml:1015(para)
+#, fuzzy
+msgid "Variable names"
+msgstr "Sharuzzaman Ahmat Raslan"
+
+#: en_US/style.xml:1020(para)
+msgid "The initial letter of an incomplete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:1029(term)
+msgid "Captions"
+msgstr ""
+
+#: en_US/style.xml:1031(para)
+msgid ""
+"Use the same rules as for headings, for all captions accompanying figures "
+"and tables. Do not put a period at the end of a caption."
+msgstr ""
+
+#: en_US/style.xml:1039(term)
+msgid "Colon"
+msgstr ""
+
+#: en_US/style.xml:1041(para)
+msgid "Use a colon in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1046(para)
+#, fuzzy
+msgid "To introduce a list"
+msgstr "Terap kepada Senarai Semasa"
+
+#: en_US/style.xml:1051(para)
+#, fuzzy
+msgid "Before an explanation"
+msgstr "Tiada sebelum"
+
+#: en_US/style.xml:1056(para)
+#, fuzzy
+msgid "After an introduction"
+msgstr "&Pengenalan Bantuan"
+
+#: en_US/style.xml:1061(para)
+msgid "Do not use a colon in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1066(para)
+msgid "To introduce a figure or a table"
+msgstr ""
+
+#: en_US/style.xml:1071(para)
+#, fuzzy
+msgid "To introduce headings"
+msgstr "&Lompat ke hiperlink"
+
+#: en_US/style.xml:1076(para)
+msgid "At the end of an introduction to a procedure"
+msgstr ""
+
+#: en_US/style.xml:1084(term)
+#, fuzzy
+msgid "Column headings"
+msgstr "&Putus lajur"
+
+#: en_US/style.xml:1086(para)
+msgid "Use the same rules as for headings."
+msgstr ""
+
+#: en_US/style.xml:1092(term)
+msgid "Comma"
+msgstr ""
+
+#: en_US/style.xml:1094(para)
+msgid "Use commas in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1099(para)
+msgid "To separate items in a series"
+msgstr ""
+
+#: en_US/style.xml:1104(para)
+msgid "To separate the parts of a sentence"
+msgstr ""
+
+#: en_US/style.xml:1109(para)
+msgid "To separate nonrestrictive phrases"
+msgstr ""
+
+#: en_US/style.xml:1114(para)
+msgid "Instead of dashes to set off appositives"
+msgstr ""
+
+#: en_US/style.xml:1119(para)
+msgid "With <emphasis>for example</emphasis> and similar expressions"
+msgstr ""
+
+#: en_US/style.xml:1125(para)
+msgid "Do not use commas in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1130(para)
+msgid "In a series of adjectives used as one modifier"
+msgstr ""
+
+#: en_US/style.xml:1135(para)
+msgid "Between two short independent clauses"
+msgstr ""
+
+#: en_US/style.xml:1143(term) en_US/emacs-nxml.xml:86(title)
+msgid "Commands"
+msgstr ""
+
+#: en_US/style.xml:1145(para)
+msgid "Do not use commands as verbs."
+msgstr ""
+
+#: en_US/style.xml:1151(term)
+msgid "Contractions"
+msgstr ""
+
+#: en_US/style.xml:1153(para)
+msgid ""
+"Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</"
+"emphasis>, or <emphasis>isn't</emphasis>."
+msgstr ""
+
+#: en_US/style.xml:1160(term)
+msgid "Dash"
+msgstr ""
+
+#: en_US/style.xml:1162(para)
+msgid ""
+"Do not use the em dash or the en dash. Use a paragraph break or a colon "
+"instead, where you want to create an introductory piece of text. If you have "
+"several items that you want to introduce, then you can use a variable list."
+msgstr ""
+
+#: en_US/style.xml:1171(term)
+msgid "Ellipsis"
+msgstr ""
+
+#: en_US/style.xml:1173(para)
+msgid "Use an ellipsis in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1178(para)
+msgid "To show that you have omitted something from a sentence"
+msgstr ""
+
+#: en_US/style.xml:1183(para)
+msgid "To indicate a pause when you quote displayed text"
+msgstr ""
+
+#: en_US/style.xml:1191(term)
+msgid "Fractions"
+msgstr ""
+
+#: en_US/style.xml:1193(para)
+msgid "Follow these rules when using fractions:"
+msgstr ""
+
+#: en_US/style.xml:1198(para)
+msgid ""
+"Use numerals for fractions in tables and in units of measurement, but spell "
+"out fractions in prose."
+msgstr ""
+
+#: en_US/style.xml:1204(para)
+msgid ""
+"Use a space between a numeral and a related fraction, if there is a possible "
+"ambiguity. For example: 1 1/2 instead of 11/2."
+msgstr ""
+
+#: en_US/style.xml:1211(para)
+msgid ""
+"If a fraction is used in a compound modifier, insert a hyphen between the "
+"fraction and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1220(term)
+msgid "Gender"
+msgstr ""
+
+#: en_US/style.xml:1222(para)
+msgid "Refer to <xref linkend=\"sn-fundamentals-9\"/>."
+msgstr ""
+
+#: en_US/style.xml:1228(term)
+#, fuzzy
+msgid "Grammar"
+msgstr "Semakan Tatabahasa Automatik"
+
+#: en_US/style.xml:1230(para)
+msgid ""
+"Use standard American English grammar rules, refer to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1241(para)
+msgid "Use the following capitalization rules in headings:"
+msgstr ""
+
+#: en_US/style.xml:1246(para)
+msgid "Initial uppercase letter of the first word"
+msgstr ""
+
+#: en_US/style.xml:1251(para)
+msgid "Initial uppercase letter for all nouns, adjectives, and verbs."
+msgstr ""
+
+#: en_US/style.xml:1257(para)
+msgid ""
+"All lowercase letters for conjunctions, articles, and prepositions of fewer "
+"than four letters"
+msgstr ""
+
+#: en_US/style.xml:1263(para)
+msgid "Initial uppercase letter for prepositions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1269(para)
+msgid "Initial uppercase letter for conjunctions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1280(term)
+msgid "Hyphen"
+msgstr ""
+
+#: en_US/style.xml:1282(para)
+msgid "Use hyphens in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1287(para)
+msgid "With a numeral in a compound modifier"
+msgstr ""
+
+#: en_US/style.xml:1291(para)
+#, fuzzy
+msgid "To prevent ambiguity"
+msgstr "&Lompat ke hiperlink"
+
+#: en_US/style.xml:1296(para)
+msgid ""
+"With some standard prefixes and suffixes. Use the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) for guidance"
+msgstr ""
+
+#: en_US/style.xml:1305(para)
+msgid "In spelled-out fractions"
+msgstr ""
+
+#: en_US/style.xml:1310(para)
+msgid ""
+"In variable names of two or more words, such as <replaceable>directory-name</"
+"replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+msgstr ""
+
+#: en_US/style.xml:1317(para)
+msgid "Do not use hyphens in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1322(para)
+msgid "For industry-accepted terms"
+msgstr ""
+
+#: en_US/style.xml:1327(para)
+#, fuzzy
+msgid "To construct verbs"
+msgstr "&Lompat ke hiperlink"
+
+#: en_US/style.xml:1332(para)
+msgid "With an adverb ending in <emphasis>ly</emphasis>"
+msgstr ""
+
+#: en_US/style.xml:1337(para)
+msgid "With numerals as single modifiers"
+msgstr ""
+
+#: en_US/style.xml:1342(para)
+msgid ""
+"With a word that is listed as unhyphenated in the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+msgstr ""
+
+#: en_US/style.xml:1351(para)
+#, fuzzy
+msgid "With trademarked terms"
+msgstr "Aksara (dengan ruang):"
+
+#: en_US/style.xml:1359(term)
+#, fuzzy
+msgid "Latin terms"
+msgstr "Latin (Renaissance)"
+
+#: en_US/style.xml:1361(para)
+msgid "Do not use Latin terms. Use an equivalent English term instead."
+msgstr ""
+
+#: en_US/style.xml:1368(term)
+msgid "Like"
+msgstr ""
+
+#: en_US/style.xml:1370(para)
+msgid ""
+"Do not use the term <emphasis>like</emphasis> to denote equivalence or "
+"similarity."
+msgstr ""
+
+#: en_US/style.xml:1377(term)
+#, fuzzy
+msgid "Lists"
+msgstr "Senarai untuk"
+
+#: en_US/style.xml:1379(para)
+msgid "Introduce a list with a complete sentence that ends with a colon."
+msgstr ""
+
+#: en_US/style.xml:1386(term)
+#, fuzzy
+msgid "Numbers"
+msgstr "Nombor"
+
+#: en_US/style.xml:1388(para)
+msgid "Spell out numbers in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1393(para)
+msgid ""
+"Numbers from zero through nine unless the number is part of a measurement"
+msgstr ""
+
+#: en_US/style.xml:1398(para)
+msgid "Approximations"
+msgstr ""
+
+#: en_US/style.xml:1403(para)
+msgid ""
+"Extreme values such as <emphasis>million</emphasis>, but precede the value "
+"with a numeral"
+msgstr ""
+
+#: en_US/style.xml:1409(para)
+msgid "Any number that begins a sentence"
+msgstr ""
+
+#: en_US/style.xml:1414(para)
+msgid ""
+"A number that is immediately followed by a numeral, for example: "
+"<literal>two 10 MB files</literal>"
+msgstr ""
+
+#: en_US/style.xml:1423(term)
+msgid "Numerals"
+msgstr ""
+
+#: en_US/style.xml:1425(para)
+msgid "Use numerals in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1430(para)
+msgid "The number 10 or greater"
+msgstr ""
+
+#: en_US/style.xml:1435(para)
+#, fuzzy
+msgid "Negative numbers"
+msgstr "Nombor Halaman"
+
+#: en_US/style.xml:1439(para)
+msgid "Most fractions"
+msgstr ""
+
+#: en_US/style.xml:1444(para)
+msgid "Percentages"
+msgstr ""
+
+#: en_US/style.xml:1449(para)
+msgid "Decimals"
+msgstr ""
+
+#: en_US/style.xml:1454(para)
+msgid "Measurements"
+msgstr ""
+
+#: en_US/style.xml:1459(para)
+msgid "Units of time smaller than one second"
+msgstr ""
+
+#: en_US/style.xml:1464(para)
+msgid "References to bits and bytes"
+msgstr ""
+
+#: en_US/style.xml:1472(term)
+msgid "Parentheses"
+msgstr ""
+
+#: en_US/style.xml:1474(para)
+msgid "Use parentheses in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1479(para)
+msgid ""
+"To contain the abbreviation of a term on the first occurrence of the full "
+"term"
+msgstr ""
+
+#: en_US/style.xml:1485(para)
+msgid "In man page references, specifically the section number"
+msgstr ""
+
+#: en_US/style.xml:1493(term)
+#, fuzzy
+msgid "Period"
+msgstr "Sela masa (saat): "
+
+#: en_US/style.xml:1495(para)
+msgid "Use a period in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1500(para)
+#, fuzzy
+msgid "To end a sentence"
+msgstr "&Lompat ke hiperlink"
+
+#: en_US/style.xml:1505(para)
+msgid "In file and directory names"
+msgstr ""
+
+#: en_US/style.xml:1510(para)
+msgid "In abbreviations that can be mistaken for words, such as a.m. and U.S."
+msgstr ""
+
+#: en_US/style.xml:1519(term)
+msgid "Punctuation"
+msgstr ""
+
+#: en_US/style.xml:1521(para)
+msgid ""
+"Use standard American English punctuation rules. In addition to the specific "
+"points of punctuation in this section, refer also to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1531(term)
+#, fuzzy
+msgid "Punctuation in numbers"
+msgstr "&Sembunyi nombor baris"
+
+#: en_US/style.xml:1533(para)
+msgid ""
+"Do not use a comma in numerals of four digits. Use a comma in numerals of "
+"more than four digits."
+msgstr ""
+
+#: en_US/style.xml:1540(term)
+#, fuzzy
+msgid "Quotation marks"
+msgstr "Tanda Susunatur Tidak Ke&lihatan"
+
+#: en_US/style.xml:1542(para)
+msgid ""
+"Use quotation marks to indicate material that is taken verbatim from another "
+"source. Do not use quotation marks to excuse terms from legitimacy. If the "
+"term is not legitimate, then use another term. If you must use that term, "
+"declare the term in the glossary and make the term legitimate."
+msgstr ""
+
+#: en_US/style.xml:1553(term)
+#, fuzzy
+msgid "See v. Refer to"
+msgstr "&Lompat ke hiperlink"
+
+#: en_US/style.xml:1555(para)
+msgid ""
+"When referring a user to another resource, use \"refer to\" instead of \"see"
+"\", and \"refer also to\" instead of \"see also\". This differentiates from "
+"the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag"
+"\">seealso</sgmltag> tags that are used in indexing. These tags create "
+"special links in the index. To be consistent throughout the document, we "
+"reserve the special words \"see\" and \"see also\" for hyperlinked index "
+"references, and use \"refer to\" and \"refer also to\" for non-hyperlinked "
+"and non-indexed references."
+msgstr ""
+
+#: en_US/style.xml:1570(term)
+msgid "Semicolon"
+msgstr ""
+
+#: en_US/style.xml:1572(para)
+msgid "Do not use semicolons."
+msgstr ""
+
+#: en_US/style.xml:1578(term)
+msgid "Slash"
+msgstr ""
+
+#: en_US/style.xml:1580(para)
+msgid ""
+"Except where required as part of a filename, do not use slashes \"/\" in "
+"your writing. The construction <literal>and/or</literal>, for example, does "
+"not exist. Use one or the other term instead."
+msgstr ""
+
+#: en_US/style.xml:1589(term)
+#, fuzzy
+msgid "Spelling"
+msgstr "Ejaan"
+
+#: en_US/style.xml:1591(para)
+msgid ""
+"Use standard American English spelling rules, refer to the "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+msgstr ""
+
+#: en_US/style.xml:1600(term)
+msgid "Titles"
+msgstr ""
+
+#: en_US/style.xml:1602(para)
+msgid "For manual titles use the same rules as for headings."
+msgstr ""
+
+#: en_US/style.xml:1608(term)
+#, fuzzy
+msgid "Units"
+msgstr "&Unit:"
+
+#: en_US/style.xml:1610(para)
+msgid "Follow these rules when using units:"
+msgstr ""
+
+#: en_US/style.xml:1615(para)
+msgid ""
+"Use standard abbreviations for units of measurements, do not invent your own "
+"abbreviations."
+msgstr ""
+
+#: en_US/style.xml:1621(para)
+msgid ""
+"For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of "
+"Electrical and Electronics Terms</citetitle>."
+msgstr ""
+
+#: en_US/style.xml:1630(para)
+msgid "Use periods for abbreviated units that might be mistaken for a word."
+msgstr ""
+
+#: en_US/style.xml:1636(para)
+msgid ""
+"Most standard abbreviations of units account for both singular and plural "
+"usage."
+msgstr ""
+
+#: en_US/style.xml:1642(para)
+msgid "Insert a space between the numeral and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1656(title)
+msgid "Composition Tips"
+msgstr ""
+
+#. This section will collect miscellanea and advice for specific
+#. situations that the FDP editors encounter. I hope they will feel
+#. free to e-mail me sticky situations or particularly interesting
+#. examples of work they've beautified. Hopefully not too much will be
+#. drawn from my own work! - PWF.
+#: en_US/style.xml:1668(para)
+msgid ""
+"This section contains usage tips based on situations the Fedora "
+"Documentation Project editors have encountered in the past. You should read "
+"and understand these examples to improve your own documentation. The Fedora "
+"Documentation Project editors welcome additional examples."
+msgstr ""
+
+#: en_US/style.xml:1676(title)
+#, fuzzy
+msgid "Active Voice"
+msgstr "Aktifkan Plugin"
+
+#: en_US/style.xml:1677(para)
+msgid ""
+"Always use active voice, except when it is awkward to do so. The tutorial "
+"tells the user how to accomplish a task, and should give instructions "
+"clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. "
+"These words are redundant in a tutorial, since the reader assumes you are "
+"outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" "
+"\"might,\" and other words that indicate you are unsure about the subject "
+"matter. Your tutorial should cover a subject authoritatively. The reader "
+"should never be concerned about unknown effects of following the tutorial."
+msgstr ""
+
+#: en_US/style.xml:1690(title)
+#, fuzzy
+msgid "Incorrect: Passive voice"
+msgstr "Semak dokumen untuk kesalahan ejaan"
+
+#: en_US/style.xml:1691(para)
+msgid "The <command>yum update</command> command must be run."
+msgstr ""
+
+#: en_US/style.xml:1694(para)
+msgid "You might want to run the <command>yum update</command> command."
+msgstr ""
+
+#: en_US/style.xml:1700(title)
+#, fuzzy
+msgid "Correct: Active voice"
+msgstr "Banding dokumen aktif dengan dokumen lain"
+
+#: en_US/style.xml:1701(para)
+msgid "Run the <command>yum update</command> command."
+msgstr ""
+
+#: en_US/style.xml:1708(title)
+msgid "Present Tense"
+msgstr ""
+
+#: en_US/style.xml:1709(para)
+msgid ""
+"Write in the present tense. A good rule of thumb is that the words \"will\" "
+"and \"shall\" are almost never needed in describing what the user should do "
+"or see. They add unnecessary length to sentences and can confuse "
+"translators. They are also often indicators of passive voice; refer also to "
+"<xref linkend=\"sn-misc-active-voice\"/>."
+msgstr ""
+
+#: en_US/style.xml:1718(title)
+#, fuzzy
+msgid "Incorrect: Future tense"
+msgstr "Semak dokumen untuk kesalahan ejaan"
+
+#: en_US/style.xml:1719(para)
+msgid "The application will display a list of target files."
+msgstr ""
+
+#: en_US/style.xml:1722(para)
+msgid "A list of target files will be displayed by the application."
+msgstr ""
+
+#: en_US/style.xml:1727(title)
+msgid "Correct: Present tense"
+msgstr ""
+
+#: en_US/style.xml:1728(para)
+msgid "The application displays a list of target files."
+msgstr ""
+
+#: en_US/style.xml:1735(title)
+msgid "Narrative Voice"
+msgstr ""
+
+#: en_US/style.xml:1736(para)
+msgid ""
+"Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself "
+"the writer (whether including the reader or not), the Fedora Documentation "
+"Project, the Fedora community, or any other group. Do not refer to users "
+"with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word "
+"\"one.\" It is acceptable to refer to the reader with the second person "
+"pronoun \"you.\""
+msgstr ""
+
+#: en_US/style.xml:1745(title)
+msgid "Incorrect: First or third person"
+msgstr ""
+
+#: en_US/style.xml:1746(para)
+msgid ""
+"As described in the last section, I always run <command>up2date</command> "
+"before configuring the Samba server."
+msgstr ""
+
+#: en_US/style.xml:1751(para)
+msgid ""
+"If the user needs to back up his or her files, s/he should use the "
+"<command>tar</command> or <command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1757(title)
+msgid "Correct: Second (or no) person"
+msgstr ""
+
+#: en_US/style.xml:1758(para)
+msgid ""
+"Refer to the section on <command>up2date</command> before configuring the "
+"Samba server."
+msgstr ""
+
+#: en_US/style.xml:1762(para)
+msgid ""
+"If necessary, users can back up files with the <command>tar</command> or "
+"<command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1770(title)
+#, fuzzy
+msgid "Negative Words"
+msgstr "Abaikan Perkataan"
+
+#: en_US/style.xml:1771(para)
+msgid ""
+"Avoid negative words when possible, since they give documentation an overly "
+"dogmatic tone. The word \"avoid\" is useful for this purpose. Note that "
+"contractions are often used for negative words such as <emphasis>don't</"
+"emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-"
+"contractions\"/>."
+msgstr ""
+
+#: en_US/style.xml:1782(title)
+msgid "Uncertainty"
+msgstr ""
+
+#: en_US/style.xml:1783(para)
+msgid ""
+"Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the "
+"like. While occasional use of these constructions is acceptable, overuse "
+"reduces the authority of your documentation. The documentation should "
+"adequately cover a stock installation of Fedora. It is impossible for a "
+"tutorial-length document to cover every possible configuration scenario. "
+"Address the most common scenarios and note discrepancies only as required."
+msgstr ""
+
+#: en_US/style.xml:1795(title)
+msgid "Redundant Coverage"
+msgstr ""
+
+#: en_US/style.xml:1796(para)
+msgid ""
+"Avoid covering redundant material, such as how to update a Fedora system. "
+"These overarching topics may be covered in other tutorials. Writers "
+"frequently violate this guideline because they feel their tutorial is not "
+"long enough. Keep your tutorial from wandering off-topic. Instead, refer the "
+"reader to a separate tutorial whenever possible for complete coverage of "
+"that topic."
+msgstr ""
+
+#: en_US/style.xml:1808(title)
+msgid "Self-referential Value Judgments"
+msgstr ""
+
+#: en_US/style.xml:1809(para)
+msgid ""
+"Avoid statements such as \"One of the most important things to do is "
+"<replaceable>XYZ</replaceable>.\" If the procedure is important, the reader "
+"already expects it to be in your tutorial. The converse is also true: If a "
+"procedure appears in your tutorial, the reader expects it is important. This "
+"is especially true if you use a whole section for the procedure in question. "
+"Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as "
+"required. If the whole section concerns how to do <replaceable>XYZ</"
+"replaceable>, leave this sentence out entirely. Refer also to <xref linkend="
+"\"vle-golden-rule-4\"/>."
+msgstr ""
+
+#: en_US/style.xml:1824(title)
+#, fuzzy
+msgid "Precision of Language"
+msgstr "Tetapan bahasa"
+
+#: en_US/style.xml:1825(para)
+msgid ""
+"Use precise words for actions users should take. Do not instruct users to "
+"\"go\" to a selection, or \"find\" a menu."
+msgstr ""
+
+#: en_US/style.xml:1830(title)
+#, fuzzy
+msgid "Incorrect: Imprecise wording"
+msgstr "Semak dokumen untuk kesalahan ejaan"
+
+#: en_US/style.xml:1833(para)
+msgid ""
+"Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+
+#: en_US/style.xml:1839(para)
+msgid "Find the option labeled <guilabel>Search</guilabel>"
+msgstr ""
+
+#: en_US/style.xml:1846(title)
+msgid "Correct: Precise wording"
+msgstr ""
+
+#: en_US/style.xml:1849(para)
+msgid ""
+"From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+
+#: en_US/style.xml:1855(para)
+msgid "Select the <guilabel>Search</guilabel> option"
+msgstr ""
+
+#: en_US/style.xml:1862(title)
+msgid "Do Not Discriminate Against Non-GUI Users"
+msgstr ""
+
+#: en_US/style.xml:1863(para)
+msgid ""
+"If you are writing about a GUI-only application, you may use \"click\" "
+"freely. If you are writing about an application that has a text-mode "
+"interface, use \"select\" instead as shown above."
+msgstr ""
+
+#: en_US/style.xml:1874(title)
+msgid "DocBook Tips"
+msgstr ""
+
+#: en_US/style.xml:1875(para)
+msgid ""
+"This section contains tips on how to use DocBook tags more effectively in "
+"your documentation."
+msgstr ""
+
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:268(title)
+msgid "Admonitions"
+msgstr ""
+
+#: en_US/style.xml:1882(para)
+msgid ""
+"Avoid overuse of admonitions. Keep admonitions short and effective by using "
+"only the most important material inside the admonition. Move any background "
+"material required to explain the admonition statements outside the "
+"admonition. Use a short but descriptive title for an admonition. Use title "
+"case for the admonition title."
+msgstr ""
+
+#: en_US/style.xml:1891(title)
+#, fuzzy
+msgid "Incorrect: Lengthy admonition"
+msgstr "Semak dokumen untuk kesalahan ejaan"
+
+#: en_US/style.xml:1894(title)
+msgid "Use <command>sfdisk</command> to check input"
+msgstr ""
+
+#: en_US/style.xml:1895(para)
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1909(title)
+msgid "Correct: Brief admonition"
+msgstr ""
+
+#: en_US/style.xml:1917(title)
+#, fuzzy
+msgid "Check Input"
+msgstr "Cara Masukan"
+
+#: en_US/style.xml:1918(para)
+msgid ""
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1910(para)
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"<placeholder-1/>"
+msgstr ""
+
+#: en_US/style.xml:1925(para)
+msgid ""
+"Avoid punctuation in titles for sections or admonitions, except for commas "
+"only where demanded. Use a title that says something about the admonition "
+"comment, such as \"Reboot Required,\" instead of simply using the admonition "
+"type for a title (\"Note\")."
+msgstr ""
+
+#: en_US/style.xml:1932(para)
+msgid ""
+"Follow the capitalization rules for headings in the title of an admonition."
+msgstr ""
+
+#: en_US/style.xml:1939(title)
+msgid "The <sgmltag class=\"starttag\">replaceable</sgmltag> Tag"
+msgstr ""
+
+#: en_US/style.xml:1941(para)
+msgid ""
+"If your documentation formally states a specific value will be used as a "
+"convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> "
+"tag in your text or examples."
+msgstr ""
+
+#: en_US/style.xml:1950(title)
+#, fuzzy
+msgid "XML Entities"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/style.xml:1951(para)
+msgid ""
+"Use the entities provided by the Fedora Documentation Project. These "
+"entities are found in the <filename>common/</filename> folder in the "
+"<filename>fedora-docs</filename> distribution. (Refer also to <xref linkend="
+"\"ch-getting-files\"/>.) For instance, do not use abbreviations such as "
+"\"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" "
+"which produces the text \"Fedora 9.\""
+msgstr ""
+
+#: en_US/writing-guidelines.xml:11(title)
+msgid "Fedora Documentation Guidelines"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:14(primary)
+#: en_US/writing-guidelines.xml:15(see)
+msgid "recursion"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:19(primary)
+#: en_US/writing-guidelines.xml:26(secondary)
+msgid "RTFM"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:20(secondary)
+msgid "read the fine manual"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:21(seealso)
+#: en_US/writing-guidelines.xml:25(primary)
+msgid "humor"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:29(para)
+msgid ""
+"Please read this chapter carefully. This chapter describes the guidelines "
+"that must be followed such as naming conventions."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:32(para)
+msgid ""
+"This chapter only discusses tags used for documentation for the Fedora "
+"Project, not all available DocBook XML tags. For the complete list, refer to "
+"<ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:38(title)
+#, fuzzy
+msgid "File Header"
+msgstr "Sunting Pengepala"
+
+#: en_US/writing-guidelines.xml:40(title)
+#, fuzzy
+msgid "XML Header"
+msgstr "Sunting Pengepala"
+
+#: en_US/writing-guidelines.xml:41(para)
+msgid ""
+"In accordance with good XML practices, the first line in any DocBook XML "
+"source files should identify the file as XML. Use the following line as the "
+"first line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:47(title)
+#, fuzzy
+msgid "CVS Id Header"
+msgstr "&Pengepala dan Footer"
+
+#: en_US/writing-guidelines.xml:48(para)
+msgid ""
+"All the files must contain the CVS Id header. Use the following line as the "
+"second line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:51(para)
+msgid ""
+"Any time the file is committed to CVS, the line is updated automatically to "
+"include information about the file. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:58(title)
+msgid "ID Naming Conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:61(primary)
+#: en_US/writing-guidelines.xml:74(primary)
+#: en_US/writing-guidelines.xml:275(primary)
+#: en_US/writing-guidelines.xml:280(primary)
+#: en_US/writing-guidelines.xml:285(primary)
+#: en_US/writing-guidelines.xml:290(primary)
+#: en_US/writing-guidelines.xml:295(primary)
+#: en_US/writing-guidelines.xml:300(primary)
+#: en_US/writing-guidelines.xml:306(primary)
+#: en_US/writing-guidelines.xml:312(primary)
+#: en_US/writing-guidelines.xml:318(primary)
+#: en_US/writing-guidelines.xml:324(primary)
+#: en_US/writing-guidelines.xml:350(primary)
+#: en_US/writing-guidelines.xml:355(primary)
+#: en_US/writing-guidelines.xml:360(primary)
+#: en_US/writing-guidelines.xml:365(primary)
+#: en_US/writing-guidelines.xml:370(primary)
+#, fuzzy
+msgid "XML tags"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/writing-guidelines.xml:62(secondary)
+#: en_US/writing-guidelines.xml:66(primary)
+#: en_US/writing-guidelines.xml:79(primary)
+msgid "naming conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:69(para)
+msgid ""
+"This section explains the ID naming convention. IDs are unique identifiers "
+"that allow DocBook XML to cross-reference a section, chapter, or other "
+"element."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:75(secondary)
+#: en_US/writing-guidelines.xml:80(secondary)
+msgid "rules for defining an ID"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:83(para)
+msgid "The following general rules apply to IDs:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:87(para)
+msgid "Keep an ID as short and simple as possible."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:90(para)
+msgid ""
+"Start the ID with the special short two-character label. This makes URLs and "
+"other references to this ID human readable, by self-identifying the XML "
+"container type."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:96(para)
+msgid ""
+"<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used "
+"properly."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:102(title)
+msgid "Proper ID Usage"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:111(title)
+msgid "Two-Character Naming Conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:112(segtitle)
+#, fuzzy
+msgid "Tag"
+msgstr "Tag"
+
+#: en_US/writing-guidelines.xml:113(segtitle)
+msgid "Prefix"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:115(sgmltag)
+msgid "preface"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:116(literal)
+#, fuzzy
+msgid "pr-"
+msgstr "K&eutamaan"
+
+#: en_US/writing-guidelines.xml:119(sgmltag)
+#, fuzzy
+msgid "chapter"
+msgstr "Heading Bab"
+
+#: en_US/writing-guidelines.xml:120(literal)
+msgid "ch-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:123(sgmltag)
+#, fuzzy
+msgid "section"
+msgstr "&Seksyen RTL"
+
+#: en_US/writing-guidelines.xml:124(literal)
+msgid "sn-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:127(sgmltag)
+msgid "figure"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:128(literal)
+msgid "fig-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:131(sgmltag)
+#: en_US/writing-guidelines.xml:235(sgmltag)
+#, fuzzy
+msgid "table"
+msgstr "&Jadual"
+
+#: en_US/writing-guidelines.xml:132(literal)
+msgid "tb-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:135(sgmltag)
+msgid "appendix"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:136(literal)
+msgid "ap-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:139(sgmltag)
+msgid "part"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:140(literal)
+#, fuzzy
+msgid "pt-"
+msgstr "pt_BR"
+
+#: en_US/writing-guidelines.xml:143(sgmltag)
+#, fuzzy
+msgid "example"
+msgstr "Contoh:"
+
+#: en_US/writing-guidelines.xml:144(literal)
+#, fuzzy
+msgid "ex-"
+msgstr "Ex. skrip"
+
+#: en_US/writing-guidelines.xml:148(para)
+msgid ""
+"Use the title of the item as the ID. Make your titles unique within a "
+"document to prevent conflicts. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:157(title)
+#, fuzzy
+msgid "XML Tags"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/writing-guidelines.xml:159(primary)
+#, fuzzy
+msgid "xml tags"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/writing-guidelines.xml:160(secondary)
+msgid "caveats"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:163(para)
+msgid ""
+"It is very important that you remember the caveats in this section. These "
+"are learned suggestions or rules that make your XML experience better."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:171(term)
+msgid "Do Not Use Trademark Entities"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:173(para)
+msgid ""
+"Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+"\"genentity\">reg</sgmltag> because the do not produce HTML output that "
+"works for all charsets. The HTML output produces by these entities are "
+"declared in the DTD and cannot be changed via the stylesheet."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:181(para)
+msgid ""
+"Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes "
+"as follows:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:184(segtitle)
+#, fuzzy
+msgid "DocBook XML source"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/writing-guidelines.xml:185(segtitle)
+msgid "Rendered content"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:189(trademark)
+msgid "trademark symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:196(trademark)
+msgid "registered trademark symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:202(trademark)
+msgid "copyright symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:209(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:211(para)
+msgid ""
+"In general, use <sgmltag>para</sgmltag> tags around anything other than a "
+"simple paragraph. Doing so will create additional white space within the "
+"text itself in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:216(para)
+msgid ""
+"Specifically, do not use <sgmltag>para</sgmltag> tags around the following "
+"(or, to put this another way, do not embed the following within <sgmltag "
+"class=\"element\">para</sgmltag> elements):"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:223(sgmltag)
+#, fuzzy
+msgid "screen"
+msgstr "Skrin Pen&uh"
+
+#: en_US/writing-guidelines.xml:226(sgmltag)
+msgid "itemizedlist"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:229(sgmltag)
+msgid "orderedlist"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:232(sgmltag)
+msgid "variablelist"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:241(term)
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag>listitem</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:244(para)
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</"
+"emphasis> start immediately after the beginning <sgmltag class=\"starttag"
+"\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:252(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:254(para)
+msgid ""
+"The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag"
+"\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis> be flush left in the XML file; otherwise, the "
+"extraneous whitespace will appear in the HTML version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:301(secondary)
+#: en_US/writing-guidelines.xml:307(secondary)
+#: en_US/writing-guidelines.xml:313(secondary)
+#: en_US/writing-guidelines.xml:319(secondary)
+#: en_US/writing-guidelines.xml:325(secondary)
+msgid "admonitions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:276(secondary)
+#: en_US/writing-guidelines.xml:302(tertiary)
+#: en_US/writing-guidelines.xml:371(secondary)
+msgid "warning"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:281(secondary)
+#: en_US/writing-guidelines.xml:308(tertiary)
+#: en_US/writing-guidelines.xml:356(secondary)
+msgid "tip"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:286(secondary)
+#: en_US/writing-guidelines.xml:314(tertiary)
+#: en_US/writing-guidelines.xml:351(secondary)
+#, fuzzy
+msgid "note"
+msgstr "&Notakaki"
+
+#: en_US/writing-guidelines.xml:291(secondary)
+#: en_US/writing-guidelines.xml:320(tertiary)
+#: en_US/writing-guidelines.xml:361(secondary)
+msgid "caution"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:296(secondary)
+#: en_US/writing-guidelines.xml:326(tertiary)
+#: en_US/writing-guidelines.xml:366(secondary)
+msgid "important"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:329(para)
+msgid ""
+"There are five types of admonitions in DocBook: <sgmltag class=\"element"
+"\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, "
+"<sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</"
+"sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the "
+"admonitions have the same structure: an optional <sgmltag class=\"element"
+"\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD "
+"does not impose any specific semantics on the individual admonitions. For "
+"example, DocBook does not mandate that a <sgmltag class=\"element\">warning</"
+"sgmltag> is reserved for cases where bodily harm can result."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:343(title)
+msgid ""
+"Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class="
+"\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, "
+"<sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element"
+"\">warning</sgmltag>"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:374(para)
+msgid ""
+"There are several ways to bring attention to text within a document. A "
+"<emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to "
+"bring additional information to the users' attention. A <emphasis><sgmltag "
+"class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful "
+"information or another way to do something. A <emphasis><sgmltag class="
+"\"element\">caution</sgmltag></emphasis> is used to show the user they must "
+"be careful when attempting a certain step. An <emphasis><sgmltag class="
+"\"element\">important</sgmltag></emphasis> tag set can be used to show the "
+"user a piece of information that should not be overlooked. While this "
+"information may not change anything the user is doing, it should show the "
+"user that this piece of information could be vital. A <emphasis><sgmltag "
+"class=\"element\">warning</sgmltag></emphasis> is used to show the reader "
+"that their current setup will change or be altered, such as files being "
+"removed, and they should not choose this operation unless they are alright "
+"with the consequences."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:394(para)
+msgid ""
+"The following lines of code show the basic setup for each case mentioned "
+"above, along with its appearance in HTML."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:403(title) en_US/emacs.xml:257(title)
+#: en_US/emacs.xml:562(title) en_US/emacs-nxml.xml:160(title)
+#, fuzzy
+msgid "Note"
+msgstr "&Notakaki"
+
+#: en_US/writing-guidelines.xml:404(para)
+#: en_US/writing-guidelines.xml:424(para)
+#: en_US/writing-guidelines.xml:434(para)
+#: en_US/writing-guidelines.xml:444(para)
+msgid "Body of text goes here."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:413(title) en_US/emacs-nxml.xml:114(title)
+msgid "Tip"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:414(para)
+msgid "Body of text goes here"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:423(title)
+msgid "Caution"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:433(title) en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:443(title)
+msgid "Warning"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:451(title)
+msgid "Screenshots"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:454(primary)
+#: en_US/writing-guidelines.xml:459(see) en_US/writing-guidelines.xml:463(see)
+msgid "screenshots"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:455(secondary)
+#, fuzzy
+msgid "how to take"
+msgstr "&Lompat ke hiperlink"
+
+#: en_US/writing-guidelines.xml:458(primary)
+#, fuzzy
+msgid "screen captures"
+msgstr "Skrin Pen&uh"
+
+#: en_US/writing-guidelines.xml:462(primary)
+#, fuzzy
+msgid "screen grabs"
+msgstr "Skrin Pen&uh"
+
+#: en_US/writing-guidelines.xml:466(para)
+msgid ""
+"Screenshots are illustrations that show the state of a display the user may "
+"encounter. Screenshots can be either graphical or textual. However, "
+"screenshots use a great deal of space in a text document to convey "
+"relatively small amounts of information. The same space in the document can "
+"hold a greater amount of more descriptive and helpful information. "
+"Therefore, authors should avoid screenshots whenever possible in favor of "
+"descriptive text."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:474(para)
+msgid ""
+"One of the isolated instances in which screenshots are useful is to "
+"demonstrate a physical screen layout that is unfamiliar to a reader. "
+"<emphasis>This does not mean that illustrations of dialog boxes are good "
+"uses of screenshots.</emphasis> On the contrary, dialogs are simply "
+"instances of a user interface element with which a reader is already "
+"familiar. An annotated diagram in certain cases, however, explains to the "
+"reader where to find functional landmarks on the screen such as menu bars."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:482(para)
+msgid ""
+"The steps for taking a graphical screenshot illustrate how using text to "
+"describe a procedure is more concise than a series of screenshots."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:487(term)
+msgid "Graphical Screenshot"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:491(para)
+msgid ""
+"Create a new user account to make screenshots. The new account uses the "
+"distribution default theme, fonts, and element sizes. The resulting "
+"screenshot has an appearance familiar to the largest number of readers, and "
+"makes Fedora Documentation Project documents consistent."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:498(para)
+msgid ""
+"Before taking the screenshot, if possible, resize the targeted GUI element"
+"(s) to the smallest possible size. The target image should be 500 pixels "
+"wide or less. If the screenshot includes more than one GUI element, you may "
+"need to resize the screenshot in a following step."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:506(para)
+msgid ""
+"To take the screenshot, select the GUI element with the mouse to bring it to "
+"the forefront, or otherwise arrange the elements. Press "
+"<keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to "
+"capture a single GUI window. For capturing the entire desktop use "
+"<keycap>Print Screen</keycap>. If the shot includes multiple elements "
+"grouped closely together, crop the resulting PNG format image in "
+"<application>The GIMP</application>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:518(para)
+msgid ""
+"If necessary, resize the image using <application>The GIMP</application>. "
+"Open the image, then right-click on it and choose "
+"<menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</"
+"guimenuitem></menuchoice>. With the chain symbol intact, set the "
+"<guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click "
+"<guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</"
+"guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the "
+"image before converting it."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:534(para)
+msgid ""
+"With the image open in <application>The GIMP</application>, right-click the "
+"image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As..."
+"</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, "
+"select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</"
+"guibutton>. Allow flattening of the image by clicking <guibutton>Export</"
+"guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:545(para)
+msgid ""
+"A <guilabel>Save as PostScript</guilabel> window appears. Select "
+"<guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</"
+"guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:559(term)
+#, fuzzy
+msgid "Text Screenshot"
+msgstr "&Teks Tersembunyi"
+
+#: en_US/writing-guidelines.xml:561(para)
+msgid ""
+"Textual screen information is also useful for readers. Follow these "
+"guidelines for textual screenshots:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:565(para)
+msgid ""
+"If a graphical screenshot illustrates a function, and the textual mode has "
+"identical functions, do not include both, unless omitting either would make "
+"your description unclear."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:571(para)
+msgid ""
+"Make the information generic over specific, and omit any username and "
+"machine information if possible. Do not include the shell prompt unless it "
+"is vital to the demonstration."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:577(para)
+msgid "Separate what the user types from sample command output."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:581(para)
+msgid ""
+"When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a "
+"procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show "
+"what the user types, and use <sgmltag class=\"element\">computeroutput</"
+"sgmltag> tags to show the resulting output."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:589(para)
+msgid ""
+"<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual "
+"screenshot usage."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:594(title)
+msgid "Correct Textual Screenshot (XML Source and HTML)"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:607(para)
+msgid ""
+"To find all the currently active ssh sessions, execute the following command:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:609(userinput)
+#, no-wrap
+msgid "ps ax | grep ssh"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:611(para)
+msgid "Output appears similar to the following:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:613(computeroutput)
+#, no-wrap
+msgid ""
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh user@@host.example.com\n"
+" 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:648(title)
+#, fuzzy
+msgid "Previewing Your Work"
+msgstr "Pasukan Mandriva Anda."
+
+#: en_US/writing-guidelines.xml:649(para)
+msgid ""
+"The GNOME <application>Help</application> browser, also known as "
+"<command>yelp</command>, and the KDE <application>Khelp</application> "
+"documentation browser can render DocBook XML information as needed. Use "
+"these applications to preview your work if you prefer reading your work in a "
+"browser-like environment. Run the following command:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:656(para)
+msgid ""
+"Make sure to point the preferred help browser at the top parent file of your "
+"XML document. Once the document loads, you can add a bookmark for it for "
+"ease of use later."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:660(title)
+#, fuzzy
+msgid "Using Bookmarks"
+msgstr "Baru me&nggunakan Template"
+
+#: en_US/writing-guidelines.xml:661(para)
+msgid ""
+"Keeping your documents in the same place for every checkout session makes "
+"help browser bookmarks more effective."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:664(para)
+msgid ""
+"Once you have a bookmark stored, it will appear in the help browser at every "
+"use. You can now hit <keycap>F1</keycap> during any GUI session to launch "
+"the help browser. Then choose your bookmark from the menu to preview your "
+"document at any time."
+msgstr ""
+
+#: en_US/module-struct.xml:12(title)
+msgid "How Modules Work"
+msgstr ""
+
+#: en_US/module-struct.xml:13(para)
+msgid ""
+"Documentation modules have a specific structure that enables the "
+"preconfigured tools to work correctly. Follow this structure exactly or you "
+"may have problems building your module. The Fedora Documentation Project "
+"build tools locate resources in the module and use them to build new output "
+"such as HTML or RPM packages."
+msgstr ""
+
+#: en_US/module-struct.xml:19(title)
+msgid "Structure of a Module"
+msgstr ""
+
+#: en_US/module-struct.xml:20(para)
+msgid ""
+"<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example "
+"module, excluding any <filename class=\"directory\">CVS</filename> folders. "
+"Note that this example document does not have branches."
+msgstr ""
+
+#: en_US/module-struct.xml:25(title)
+msgid "Example Module Structure"
+msgstr ""
+
+#: en_US/module-struct.xml:47(title)
+#, fuzzy
+msgid "CVS Module Contents"
+msgstr "Papar Kandungan Bantuan"
+
+#: en_US/module-struct.xml:48(segtitle)
+msgid "Component"
+msgstr ""
+
+#: en_US/module-struct.xml:49(segtitle)
+#, fuzzy
+msgid "Type"
+msgstr "Jenis"
+
+#: en_US/module-struct.xml:50(segtitle)
+msgid "Usage Notes"
+msgstr ""
+
+#: en_US/module-struct.xml:52(seg)
+#, fuzzy
+msgid "Primary language directory"
+msgstr "Bahasa Antaramuka Pengguna"
+
+#: en_US/module-struct.xml:53(seg) en_US/module-struct.xml:94(seg)
+#: en_US/module-struct.xml:101(seg)
+msgid "required"
+msgstr ""
+
+#: en_US/module-struct.xml:56(filename)
+#: en_US/module-struct.xml:181(systemitem)
+#, fuzzy
+msgid "en_US"
+msgstr "obsoletenotice-en_US.xml"
+
+#: en_US/module-struct.xml:60(firstterm)
+msgid "entities"
+msgstr ""
+
+#: en_US/module-struct.xml:61(para)
+msgid ""
+"Think of an XML entity as a predefined snippet of information. It can "
+"represent a chunk of XML source, or simply a word or character. If the "
+"information changes, it need be replaced only once, in the definition, to "
+"fix all usage."
+msgstr ""
+
+#: en_US/module-struct.xml:54(seg)
+msgid ""
+"This is the only directory absolutely required. It is named for the original "
+"language of the document, such as <placeholder-1/> (US English). The primary "
+"language does not have to be US English; all languages are supported. This "
+"directory contains all the XML source for the actual document, as well as "
+"XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr ""
+
+#: en_US/module-struct.xml:69(seg)
+#, fuzzy
+msgid "Graphics directory"
+msgstr "Direktori '%s' adalah dihalang-tulis."
+
+#: en_US/module-struct.xml:70(seg) en_US/module-struct.xml:80(seg)
+msgid "optional"
+msgstr ""
+
+#: en_US/module-struct.xml:71(filename) en_US/module-struct.xml:75(filename)
+msgid "figs/"
+msgstr ""
+
+#: en_US/module-struct.xml:71(seg)
+msgid ""
+"The <placeholder-1/> directory is an optional directory where graphics for "
+"the document should be stored. If graphics are screenshots that are "
+"particular to a language, the <placeholder-2/> directory can and should be "
+"stored in a language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:79(seg)
+#, fuzzy
+msgid "Translation (PO) directory"
+msgstr "Direktori '%s' adalah dihalang-tulis."
+
+#: en_US/module-struct.xml:81(filename) en_US/module-struct.xml:87(filename)
+msgid "po/"
+msgstr ""
+
+#: en_US/module-struct.xml:83(acronym)
+msgid "PO"
+msgstr ""
+
+#: en_US/module-struct.xml:88(filename)
+msgid "LINGUAS"
+msgstr ""
+
+#: en_US/module-struct.xml:89(firstterm)
+msgid "locales"
+msgstr ""
+
+#: en_US/module-struct.xml:81(seg)
+msgid ""
+"The <placeholder-1/> directory contains specially formatted Portable Object, "
+"or <placeholder-2/>, files created and used by translators. The Fedora "
+"Documentation Project build tools use these files to create translated "
+"versions of documents. The translated documents are not stored in CVS; they "
+"are created as needed from these PO files. The <placeholder-3/> directory "
+"also contains the <placeholder-4/> file, which lists the active translation "
+"<placeholder-5/>, or languages."
+msgstr ""
+
+#: en_US/module-struct.xml:93(seg) en_US/module-struct.xml:95(filename)
+msgid "Makefile"
+msgstr ""
+
+#: en_US/module-struct.xml:95(seg)
+msgid ""
+"The <placeholder-1/> controls the build process. Its content is discussed in "
+"<xref linkend=\"ex-makefile\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:100(filename) en_US/module-struct.xml:102(filename)
+#, fuzzy
+msgid "rpm-info.xml"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/module-struct.xml:102(seg)
+msgid "The <placeholder-1/> file contains document specific metadata"
+msgstr ""
+
+#: en_US/module-struct.xml:107(title)
+#, fuzzy
+msgid "Common Build Tools"
+msgstr "Hidupkan Alatan Memf&ormat"
+
+#: en_US/module-struct.xml:108(para)
+msgid ""
+"Never add the <systemitem>docs-common</systemitem> build tools directory to "
+"an individual module. Special formatting in the module list downloads these "
+"tools when a user checks out a document module. For more information, refer "
+"to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:116(title)
+#, fuzzy
+msgid "The Document Build System"
+msgstr "Cipta dokumen baru"
+
+#: en_US/module-struct.xml:121(para)
+msgid ""
+"In Linux and Fedora documentation, references to commands often include a "
+"number inside parentheses. This number represents the section of "
+"<firstterm>manpages</firstterm> that includes documentation for that "
+"command. To read the manpage for <command>make(1)</command>, use the command "
+"<command>man 1 make</command>."
+msgstr ""
+
+#: en_US/module-struct.xml:117(para)
+msgid ""
+"The build system can render the document into another format such as "
+"<abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</"
+"command><placeholder-1/> and shell scripts. Authors need <emphasis>no</"
+"emphasis> prior experience with either shell scripts or a <command>make(1)</"
+"command>."
+msgstr ""
+
+#: en_US/module-struct.xml:133(title)
+#, fuzzy
+msgid "The Document <filename>Makefile</filename>"
+msgstr "Cipta dokumen baru"
+
+#: en_US/module-struct.xml:134(para)
+msgid ""
+"Each individual document has its own <filename>Makefile</filename>, which "
+"only needs to be a few lines long. The document <filename>Makefile</"
+"filename> content is designed for cut and paste operations."
+msgstr ""
+
+#: en_US/module-struct.xml:140(para)
+msgid ""
+"<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</"
+"filename> for a simple document with two files and two translations."
+msgstr ""
+
+#: en_US/module-struct.xml:146(title)
+#, fuzzy
+msgid "Sample Document Makefile"
+msgstr "Cipta dokumen baru"
+
+#: en_US/module-struct.xml:162(para)
+msgid ""
+"Do not be concerned with some of the more complicated syntax such as the "
+"<command>XMLFILES_template</command> stanza. An explanation for this "
+"template appears a few paragraphs below."
+msgstr ""
+
+#: en_US/module-struct.xml:168(title)
+msgid "Makefile Variables"
+msgstr ""
+
+#: en_US/module-struct.xml:169(segtitle)
+msgid "Variable"
+msgstr ""
+
+#: en_US/module-struct.xml:170(segtitle) en_US/module-struct.xml:240(segtitle)
+msgid "Explanation"
+msgstr ""
+
+#: en_US/module-struct.xml:172(systemitem)
+msgid "DOCBASE"
+msgstr ""
+
+#: en_US/module-struct.xml:173(seg)
+msgid ""
+"This variable contains the name for the main (parent) XML document. Follow "
+"convention by naming your document after the module name."
+msgstr ""
+
+#: en_US/module-struct.xml:178(systemitem)
+msgid "PRI_LANG"
+msgstr ""
+
+#: en_US/module-struct.xml:179(seg)
+msgid ""
+"This variable contains the ISO code for the original version of the "
+"document, such as <placeholder-1/>."
+msgstr ""
+
+#: en_US/module-struct.xml:184(systemitem)
+msgid "DOC_ENTITIES"
+msgstr ""
+
+#: en_US/module-struct.xml:185(seg)
+msgid ""
+"This variable contains a listing of any files containing entity definitions. "
+"The Fedora Documentation Project uses a special XML format to record "
+"document-specific entities, so they can be translated and built on the fly "
+"like any other XML document. An example is shown later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:194(systemitem)
+#, fuzzy
+msgid "XMLFILES_template"
+msgstr "Buka Template"
+
+#: en_US/module-struct.xml:197(systemitem)
+msgid "${1}"
+msgstr ""
+
+#: en_US/module-struct.xml:202(systemitem)
+msgid "${1}/"
+msgstr ""
+
+#: en_US/module-struct.xml:195(seg)
+msgid ""
+"This template allows the build tools to work with the document in multiple "
+"languages once it is translated. The <placeholder-1/> marking is a variable "
+"used to substitute the appropriate language. This template is not terribly "
+"complicated. For a new module, duplicate this section exactly except for the "
+"actual filenames. Prepend the text <placeholder-2/>, in place of the "
+"language code directory name, to each filename in your document."
+msgstr ""
+
+#: en_US/module-struct.xml:208(title)
+msgid "Files Exempt From Listing"
+msgstr ""
+
+#: en_US/module-struct.xml:209(para)
+msgid ""
+"Do not include the document-specific entities XML file or the <filename>rpm-"
+"info.xml</filename> file, which will be discussed later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:213(para)
+msgid ""
+"The final section, beginning with <literal>define</literal>, locates the "
+"main <filename>Makefile.common</filename> for the build system. This "
+"<filename>Makefile.common</filename> file contains all the <application>make"
+"(1)</application> targets and rules to actually build the document and the "
+"various archives."
+msgstr ""
+
+#: en_US/module-struct.xml:222(title)
+msgid "The Document <filename>rpm-info.xml</filename>"
+msgstr ""
+
+#: en_US/module-struct.xml:223(para)
+msgid ""
+"Each document module's primary language directory contains a file called "
+"<filename>rpm-info.xml</filename>. This file contains document-specific "
+"metadata used to generate revision history, copyright, and contributor "
+"information. It follows a DTD specification included with the rest of the "
+"build system tools."
+msgstr ""
+
+#: en_US/module-struct.xml:232(title)
+msgid "Build System Actions"
+msgstr ""
+
+#: en_US/module-struct.xml:233(para)
+msgid ""
+"To render the <abbrev>XML</abbrev> document into another format, use one of "
+"the following <command>make</command> targets:"
+msgstr ""
+
+#: en_US/module-struct.xml:238(title)
+#, fuzzy
+msgid "Build Targets"
+msgstr "Id Bina."
+
+#: en_US/module-struct.xml:239(segtitle)
+#, fuzzy
+msgid "Target"
+msgstr "Sasaran Bina"
+
+#: en_US/module-struct.xml:242(systemitem)
+#, fuzzy
+msgid "help"
+msgstr "B&antuan"
+
+#: en_US/module-struct.xml:243(seg)
+msgid "This target prints a list of available targets and their descriptions."
+msgstr ""
+
+#: en_US/module-struct.xml:247(systemitem)
+#, fuzzy
+msgid "validate-xml"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/module-struct.xml:248(firstterm)
+msgid "validates"
+msgstr ""
+
+#: en_US/module-struct.xml:248(seg)
+msgid ""
+"This target <placeholder-1/> the XML files to make sure they are not only "
+"well-formed, but follow the DTD. Some viewers of XML documents may not work "
+"correctly until you run this target. This target includes copying required "
+"entity files so that validating XML viewers work properly"
+msgstr ""
+
+#: en_US/module-struct.xml:256(systemitem)
+#, fuzzy
+msgid "html"
+msgstr "Pilihan Export HTML"
+
+#: en_US/module-struct.xml:257(abbrev) en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:293(abbrev) en_US/module-struct.xml:298(abbrev)
+#, fuzzy
+msgid "HTML"
+msgstr "Pilihan Export HTML"
+
+#: en_US/module-struct.xml:261(systemitem)
+#: en_US/module-struct.xml:271(systemitem)
+msgid "${DOCBASE}"
+msgstr ""
+
+#: en_US/module-struct.xml:262(systemitem)
+#: en_US/module-struct.xml:272(systemitem)
+msgid "${LANG}"
+msgstr ""
+
+#: en_US/module-struct.xml:260(filename)
+msgid "<placeholder-1/>-<placeholder-2/>/"
+msgstr ""
+
+#: en_US/module-struct.xml:257(seg)
+msgid ""
+"This target builds the \"chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a separate directory named "
+"<placeholder-2/>. Each document section is a separate file within that "
+"directory."
+msgstr ""
+
+#: en_US/module-struct.xml:267(systemitem)
+#, fuzzy
+msgid "html-nochunks"
+msgstr "Pilihan Export HTML"
+
+#: en_US/module-struct.xml:270(filename)
+#, fuzzy
+msgid "<placeholder-1/>-<placeholder-2/>.html"
+msgstr "Pilihan Export HTML"
+
+#: en_US/module-struct.xml:268(seg)
+msgid ""
+"This target builds the \"non-chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a single file: <placeholder-2/>; no "
+"other files are created."
+msgstr ""
+
+#: en_US/module-struct.xml:276(systemitem)
+msgid "pdf"
+msgstr ""
+
+#: en_US/module-struct.xml:277(abbrev) en_US/module-struct.xml:278(abbrev)
+#: en_US/module-struct.xml:294(abbrev) en_US/module-struct.xml:299(abbrev)
+msgid "PDF"
+msgstr ""
+
+#: en_US/module-struct.xml:277(seg)
+msgid ""
+"This target builds only the <placeholder-1/> document for all document "
+"languages. <placeholder-2/> production is currently erratic and may not work "
+"for your document."
+msgstr ""
+
+#: en_US/module-struct.xml:282(systemitem)
+msgid "tarball"
+msgstr ""
+
+#: en_US/module-struct.xml:283(command)
+msgid "tar(1)"
+msgstr ""
+
+#: en_US/module-struct.xml:283(seg)
+msgid ""
+"This target builds only the <placeholder-1/> archive for all document "
+"languages."
+msgstr ""
+
+#: en_US/module-struct.xml:287(systemitem)
+#, fuzzy
+msgid "all"
+msgstr "Semu&a"
+
+#: en_US/module-struct.xml:288(seg)
+msgid "This target builds all targets listed above."
+msgstr ""
+
+#: en_US/module-struct.xml:291(systemitem)
+#: en_US/module-struct.xml:300(filename)
+msgid "clean"
+msgstr ""
+
+#: en_US/module-struct.xml:293(emphasis)
+#, fuzzy
+msgid "not"
+msgstr "Tiada"
+
+#: en_US/module-struct.xml:292(seg)
+msgid ""
+"This target deletes any temporary, or generated files, but does <placeholder-"
+"1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr ""
+
+#: en_US/module-struct.xml:297(systemitem)
+msgid "distclean"
+msgstr ""
+
+#: en_US/module-struct.xml:298(seg)
+msgid ""
+"This target erases all <placeholder-1/>, <placeholder-2/>, and archive "
+"files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr ""
+
+#: en_US/module-struct.xml:305(title)
+msgid "PDF Generation is Erratic"
+msgstr ""
+
+#: en_US/module-struct.xml:306(para)
+msgid ""
+"<abbrev>PDF</abbrev> production is currently erratic and may not work for "
+"your document."
+msgstr ""
+
+#: en_US/module-struct.xml:311(title)
+msgid "Adding or Changing Targets"
+msgstr ""
+
+#: en_US/module-struct.xml:312(para)
+msgid ""
+"To add a new target and rules, place them at the bottom of the document "
+"<filename>Makefile</filename>, below the <literal>include</literal> line. "
+"Follow your target definitions with a double colon, not a single colon. The "
+"double colon allows you to specify additional rules for existing targets, or "
+"to write rules for a new target."
+msgstr ""
+
+#: en_US/module-struct.xml:320(para)
+msgid ""
+"For more information on using <command>make(1)</command>, consult the online "
+"documentation with the command <command>info make</command> in a terminal."
+msgstr ""
+
+#: en_US/module-struct.xml:327(title)
+#, fuzzy
+msgid "Using Document Image Files"
+msgstr "Selit imej kedalam dokumen"
+
+#: en_US/module-struct.xml:328(para)
+msgid ""
+"Tutorial documents often make use of images such as <filename class="
+"\"extension\">.PNG</filename> files. Store image files in a <filename class="
+"\"directory\">figs/</filename> folder in the main module directory, as shown "
+"in <xref linkend=\"ex-module-structure\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:335(para)
+msgid ""
+"Depending on the output media, sometimes images may be scaled, streteched, "
+"or squashed. To minimize any distortions, we recommend that you use only "
+"<filename class=\"extension\">.PNG</filename> images. Avoid <filename class="
+"\"extension\">.JPG</filename> files. The <command>convert(1)</command> "
+"program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</"
+"abbrev> package, provides a convenient way to reformat <filename class="
+"\"extension\">.JPG</filename> images into <filename class=\"extension\">."
+"PNG</filename> format. For more information on formatting images such as "
+"screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:349(para)
+msgid ""
+"Image files may be organized into subdirectories under <filename>figs/</"
+"filename> if necessary. The document building system recreates the image "
+"subdirectory structure in the output documents."
+msgstr ""
+
+#: en_US/module-struct.xml:355(para)
+msgid ""
+"Images often contain labels or other text which may need to be localized. A "
+"screenshot of a program, for example, may require a version for each "
+"translated language. Name language-dependent image files such as program "
+"screenshots by adding the language code to the filename, such as "
+"<filename>menu-en_US.png</filename>. Language-independent images, such as "
+"<filename>icon.png</filename>, do not need language codes."
+msgstr ""
+
+#: en_US/module-struct.xml:365(para)
+msgid ""
+"Sometimes, a document may require images that do not follow the naming "
+"convention. To use these images with the document building system, create an "
+"ordinary text file containing the image filenames. This file must be named "
+"<filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</"
+"systemitem> so the build system finds it when searching for image filenames."
+msgstr ""
+
+#: en_US/module-struct.xml:374(para)
+msgid ""
+"<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one "
+"way to create this <filename>Manifest</filename> file."
+msgstr ""
+
+#: en_US/module-struct.xml:380(title)
+#, fuzzy
+msgid "Building A Manifest"
+msgstr "Membina Dokumen:"
+
+#: en_US/module-struct.xml:387(title)
+msgid "Adding a New DocBook XML File"
+msgstr ""
+
+#: en_US/module-struct.xml:388(para)
+msgid ""
+"To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:392(para)
+msgid "Place the new DocBook XML file in the primary language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:396(para)
+msgid ""
+"Edit the <filename>Makefile</filename> and add the filename to the "
+"<varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to "
+"the last existing line, and on the next line add an entry for the new file. "
+"Remember to add the <literal>${1}/</literal> prefix as a substitute for the "
+"language directory name."
+msgstr ""
+
+#: en_US/module-struct.xml:406(title)
+msgid "Adding a Translation"
+msgstr ""
+
+#: en_US/module-struct.xml:407(para)
+msgid ""
+"Translations are stored as PO (portable object) files, which the toolchain "
+"transforms into translated documents. Each PO file is based on the POT (PO "
+"template) for the document and translated by the Fedora Translation Project. "
+"To add a translation, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:414(para)
+msgid ""
+"If the <filename class=\"directory\">po/</filename> directory does not "
+"exist, create it and add it to CVS:"
+msgstr ""
+
+#: en_US/module-struct.xml:420(para)
+msgid "If it does not exist, create the POT file:"
+msgstr ""
+
+#: en_US/module-struct.xml:424(para)
+msgid ""
+"Add the new translation language to the <varname>OTHERS</varname> listing in "
+"the <filename>Makefile</filename>."
+msgstr ""
+
+#: en_US/module-struct.xml:429(para)
+msgid ""
+"Although translators often copy the POT manually to create the new PO file, "
+"the following command also works:"
+msgstr ""
+
+#: en_US/module-struct.xml:432(replaceable)
+msgid "lang"
+msgstr ""
+
+#: en_US/module-struct.xml:432(screen)
+#, fuzzy, no-wrap
+msgid "make po/<placeholder-1/>.po"
+msgstr "Jadikan pilihan tebal (toggle)"
+
+#: en_US/intro.xml:13(title)
+#, fuzzy
+msgid "Introduction"
+msgstr "Pengenalan"
+
+#: en_US/intro.xml:15(para)
+msgid ""
+"The goal of the Fedora Documentation Project is to create easy-to-follow, "
+"task-based documentation for Fedora users and developers. The Fedora "
+"Documentation Project uses the following tools:"
+msgstr ""
+
+#: en_US/intro.xml:23(para)
+#, fuzzy
+msgid "DocBook XML v4.4"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/intro.xml:26(para)
+msgid "Custom XSLT stylesheets for both print and HTML versions"
+msgstr ""
+
+#: en_US/intro.xml:30(para)
+msgid "Custom scripts to generate HTML output (use <command>xmlto</command>)"
+msgstr ""
+
+#: en_US/intro.xml:34(para)
+msgid "Emacs with PSGML mode (optional, but recommended)"
+msgstr ""
+
+#: en_US/intro.xml:43(para)
+msgid ""
+"This document explains the tools used by the Fedora Documentation Project. "
+"It provides writing and tagging guidelines to ensure Fedora documentation is "
+"consistent and easy-to-follow."
+msgstr ""
+
+#: en_US/getting-files.xml:12(title)
+msgid "Prerequisites"
+msgstr ""
+
+#: en_US/getting-files.xml:14(para)
+msgid ""
+"To work on official Fedora documentation you need to install the required "
+"tools. Follow the directions below to configure your system."
+msgstr ""
+
+#: en_US/getting-files.xml:20(title)
+msgid "System Packages"
+msgstr ""
+
+#: en_US/getting-files.xml:22(para)
+msgid ""
+"Install the \"Authoring and Publishing\" package group, which contains "
+"required DocBook XML files, stylesheets and scripts:"
+msgstr ""
+
+#: en_US/getting-files.xml:28(userinput)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+msgstr ""
+
+#: en_US/getting-files.xml:31(para)
+msgid ""
+"Next, install the <filename>cvs</filename> package, which is used to handle "
+"revision control on files in the official repository:"
+msgstr ""
+
+#: en_US/getting-files.xml:37(userinput)
+#, no-wrap
+msgid "su -c 'yum install cvs'"
+msgstr ""
+
+#: en_US/getting-files.xml:40(para)
+msgid ""
+"If you plan to use <application>Emacs</application> to edit DocBook XML "
+"documentation, install <package>psgml</package>, which adds helpful and time-"
+"saving functionality to maximize editing efficiency:"
+msgstr ""
+
+#: en_US/getting-files.xml:44(userinput)
+#, no-wrap
+msgid "su -c 'yum install psgml'"
+msgstr ""
+
+#: en_US/getting-files.xml:48(title)
+#, fuzzy
+msgid "Fedora Documentation Tools"
+msgstr "Hidupkan Alatan Memf&ormat"
+
+#: en_US/getting-files.xml:50(para)
+msgid ""
+"The Fedora Documentation Project's custom scripts and stylesheets are stored "
+"in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</"
+"systemitem> CVS server. When you check out a document module from CVS, the "
+"tools are included in the module inside the <filename class=\"directory"
+"\">docs-common/</filename> directory. To work on existing documents in CVS, "
+"refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:59(para)
+msgid ""
+"The most powerful component in the Fedora Documentation Project toolbox is "
+"<firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for "
+"authoring technical documentation using <firstterm>Extensible Markup "
+"Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark "
+"pieces of content with descriptive tags. The following output is an example "
+"of DocBook XML:"
+msgstr ""
+
+#: en_US/getting-files.xml:76(para)
+msgid ""
+"This example article, entitled <citetitle>A Very Short Article</citetitle>, "
+"consists of only a single paragraph. The tags, or markup, surround elements "
+"of content to define the sense in which they are used. A paragraph, for "
+"example, is marked with <sgmltag>para</sgmltag> tags. Text that requires "
+"emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does "
+"not worry about the visual formatting such as italics or font size. Fedora "
+"Documentation Project build tools automatically perform all formatting tasks."
+msgstr ""
+
+#: en_US/getting-files.xml:85(para)
+msgid ""
+"The custom tools built by the Fedora Documentation Project render DocBook "
+"source into a variety of formats for publication and distribution. They also "
+"allow translators to create localized versions of the XML documents for "
+"Fedora users around the world. The flexibility of XML allows for a single "
+"document to be used many times for many purposes, like reusable code for a "
+"programmer."
+msgstr ""
+
+#: en_US/getting-files.xml:91(para)
+msgid ""
+"DocBook is itself very well documented. For more information about DocBook, "
+"visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also "
+"features complete copies of <citetitle>DocBook: The Definitive Guide</"
+"citetitle> to browse and download, the canonical source for DocBook "
+"information."
+msgstr ""
+
+#: en_US/getting-files.xml:97(title)
+#, fuzzy
+msgid "DocBook XML Versions"
+msgstr "Isytihar sebagai XML (versi 1.0)"
+
+#: en_US/getting-files.xml:98(para)
+msgid ""
+"DocBook XML, like a computer program, has version numbers. The version used "
+"by Fedora Documentation Project right now is 4.4. The DocBook web site may "
+"document a slightly newer version, but the majority of the schema still "
+"applies."
+msgstr ""
+
+#: en_US/getting-files.xml:103(para)
+msgid ""
+"Contributors who use the Microsoft Windows operating system can still make "
+"use of DocBook tools. For more information, refer to <ulink url=\"http://www."
+"codeproject.com/winhelp/docbook_howto.asp\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:110(title)
+msgid "Naming Conventions"
+msgstr ""
+
+#: en_US/getting-files.xml:111(para)
+msgid ""
+"The Fedora Documentation Project provides the tools, scripts, and "
+"stylesheets to transform your <abbrev>XML</abbrev> documents into other "
+"output formats such as <abbrev>HTML</abbrev>. In addition, these tools can "
+"build your document into a <abbrev>RPM</abbrev> package. To take advantage "
+"of these services, follow the conventions in this section to name your files."
+msgstr ""
+
+#: en_US/getting-files.xml:119(para)
+msgid ""
+"On the CVS server, directories that contain document files are called "
+"<firstterm>modules</firstterm>. Each module represents a single document. "
+"Each document may consist of several <firstterm>branches</firstterm> if that "
+"document changes with each release of Fedora. Contributors can check out "
+"single branches of these modules or the entire module. Each document or "
+"branch may contain multiple XML source files."
+msgstr ""
+
+#: en_US/getting-files.xml:126(para)
+msgid ""
+"Use the <command>cvs co -c</command> command to view existing module names."
+msgstr ""
+
+#: en_US/getting-files.xml:129(title)
+msgid "Partial List of CVS Modules"
+msgstr ""
+
+#: en_US/getting-files.xml:130(userinput)
+#, no-wrap
+msgid "cd ~/localrepo/fedora-docs/"
+msgstr ""
+
+#: en_US/getting-files.xml:149(para)
+msgid ""
+"The leftmost entry in each line is the name of a module you can check out "
+"from CVS. The rest of the line ensures that checkouts include the proper "
+"branch of a document and the common build tools. For more information on "
+"CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:154(para)
+msgid ""
+"Note in the listing above that the <systemitem>about-fedora</systemitem> "
+"module has two branches available. One branch is for Fedora 7 and one is for "
+"forward development to match the current work of developers. On the other "
+"hand, the <systemitem>documentation-guide</systemitem> module is not "
+"branched."
+msgstr ""
+
+#: en_US/getting-files.xml:161(title)
+msgid "Modules Labeled <filename>-dir</filename>"
+msgstr ""
+
+#: en_US/getting-files.xml:162(para)
+msgid ""
+"Modules ending with the suffix <filename>-dir</filename> are not usually "
+"helpful to checkout directly. These modules do not include the common build "
+"tools and thus do not provide many of the functions contributors require."
+msgstr ""
+
+#: en_US/getting-files.xml:168(title)
+#, fuzzy
+msgid "Module Names"
+msgstr "Sharuzzaman Ahmat Raslan"
+
+#: en_US/getting-files.xml:169(para)
+msgid ""
+"Choose a module name that accurately reflects your document's subject, but "
+"avoid any name already taken. The document title without any use of the word "
+"<wordasword>fedora</wordasword> is a reasonable choice in most cases. Use "
+"the length descriptors <wordasword>tutorial</wordasword> or "
+"<wordasword>guide</wordasword> in the module name where appropriate."
+msgstr ""
+
+#: en_US/getting-files.xml:178(title)
+msgid "Avoid Redundancy"
+msgstr ""
+
+#: en_US/getting-files.xml:179(para)
+msgid ""
+"Do not use the word <wordasword>fedora</wordasword> to name modules in the "
+"Fedora Documentation Project CVS repository."
+msgstr ""
+
+#: en_US/getting-files.xml:185(title)
+msgid "Correct Module Naming"
+msgstr ""
+
+#: en_US/getting-files.xml:186(segtitle)
+#, fuzzy
+msgid "Document Name"
+msgstr "Nama Dokumen:"
+
+#: en_US/getting-files.xml:187(segtitle)
+#, fuzzy
+msgid "CVS Module Name"
+msgstr "Tetap Nama Imej"
+
+#: en_US/getting-files.xml:189(seg)
+#, fuzzy
+msgid "Desktop User Guide"
+msgstr "Bahasa Antaramuka Pengguna"
+
+#: en_US/getting-files.xml:190(seg)
+#, fuzzy
+msgid "desktop-user-guide"
+msgstr "Bahasa Antaramuka Pengguna"
+
+#: en_US/getting-files.xml:194(application)
+msgid "Yum"
+msgstr ""
+
+#: en_US/getting-files.xml:193(seg)
+msgid "Software Management with <placeholder-1/>"
+msgstr ""
+
+#: en_US/getting-files.xml:195(seg)
+msgid "yum-guide"
+msgstr ""
+
+#: en_US/getting-files.xml:198(application)
+msgid "Pup"
+msgstr ""
+
+#: en_US/getting-files.xml:198(seg)
+#, fuzzy
+msgid "Using <placeholder-1/>"
+msgstr "Baru me&nggunakan Template"
+
+#: en_US/getting-files.xml:199(seg)
+msgid "pup-tutorial"
+msgstr ""
+
+#: en_US/getting-files.xml:204(title)
+#, fuzzy
+msgid "File Names"
+msgstr "Extension &fail:"
+
+#: en_US/getting-files.xml:205(para)
+msgid ""
+"Follow these guidelines for naming files to make collaboration and document "
+"reuse easy:"
+msgstr ""
+
+#: en_US/getting-files.xml:209(para)
+msgid ""
+"As with module names, avoid using the word <wordasword>fedora</wordasword> "
+"in file names since it is redundant."
+msgstr ""
+
+#: en_US/getting-files.xml:214(para)
+msgid ""
+"If the document is comprised of many XML files, avoid repeating the name of "
+"the document when naming the constituent files."
+msgstr ""
+
+#: en_US/getting-files.xml:219(para)
+msgid ""
+"Avoid numbering files to show order, since editors and authors often "
+"rearrange documents or reuse their files in other documents."
+msgstr ""
+
+#: en_US/emacs.xml:13(title)
+msgid "Emacs and PSGML Mode"
+msgstr ""
+
+#: en_US/emacs.xml:16(primary)
+msgid "PSGML"
+msgstr ""
+
+#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary)
+#: en_US/emacs.xml:43(primary) en_US/emacs.xml:224(primary)
+#: en_US/emacs.xml:233(primary) en_US/emacs.xml:238(primary)
+#: en_US/emacs.xml:243(primary) en_US/emacs.xml:523(application)
+#: en_US/emacs-nxml.xml:18(primary) en_US/emacs-nxml.xml:22(primary)
+msgid "Emacs"
+msgstr ""
+
+#: en_US/emacs.xml:25(secondary)
+#, fuzzy
+msgid "PSGML mode"
+msgstr "Anda telah mengubah mod arah."
+
+#: en_US/emacs.xml:28(para)
+msgid ""
+"You can use the PSGML mode available for Emacs to make it easier to write in "
+"XML format. PSGML mode provides syntax-highlighting, tag completion, and "
+"more."
+msgstr ""
+
+#: en_US/emacs.xml:35(title)
+msgid "Installing PSGML"
+msgstr ""
+
+#: en_US/emacs.xml:36(para)
+msgid "To install PSGML, use the <command>yum</command> command:"
+msgstr ""
+
+#: en_US/emacs.xml:37(userinput)
+#, fuzzy, no-wrap
+msgid "yum install psgml"
+msgstr "Pasang plugin baru"
+
+#: en_US/emacs.xml:40(title)
+msgid "Setting Up Your <filename>.emacs</filename> File"
+msgstr ""
+
+#: en_US/emacs.xml:48(filename)
+msgid ".emacs"
+msgstr ""
+
+#: en_US/emacs.xml:51(para)
+msgid ""
+"For Emacs to parse your DocBook documents correctly, you must have a "
+"<filename>.emacs</filename> file. Cut and paste the following into your "
+"existing <filename>.emacs</filename> file or create a new one that contains "
+"the following lines:"
+msgstr ""
+
+#: en_US/emacs.xml:181(para)
+msgid ""
+"If you have a wheel mouse and are using Emacs version 21, you can add the "
+"following to your <filename>.emacs</filename> file so your wheel will work "
+"in <application>Emacs</application>:"
+msgstr ""
+
+#: en_US/emacs.xml:192(para)
+msgid ""
+"If you are using the older version 20 of <application>Emacs</application>, "
+"add the following instead:"
+msgstr ""
+
+#: en_US/emacs.xml:221(title)
+msgid "Customizing Emacs"
+msgstr ""
+
+#: en_US/emacs.xml:225(secondary)
+msgid "customizing"
+msgstr ""
+
+#: en_US/emacs.xml:229(filename)
+msgid ".Xresources"
+msgstr ""
+
+#: en_US/emacs.xml:234(secondary)
+#, fuzzy
+msgid "colors"
+msgstr "&Warna"
+
+#: en_US/emacs.xml:239(secondary)
+#, fuzzy
+msgid "font"
+msgstr "&Font"
+
+#: en_US/emacs.xml:244(secondary)
+msgid "geometry"
+msgstr ""
+
+#: en_US/emacs.xml:247(para)
+msgid ""
+"The colors, font, and geometry (default size of window) for Emacs in your "
+"<filename>~/.Xresources</filename> file. The format for the settings is "
+"<userinput>emacs.keyword:value</userinput>."
+msgstr ""
+
+#: en_US/emacs.xml:253(para)
+msgid "The following is a sample <filename>~/.Xresources</filename> file."
+msgstr ""
+
+#: en_US/emacs.xml:258(para)
+msgid ""
+"If you have other settings in your <filename>~/.Xresources</filename>, add "
+"the following to the end of the file."
+msgstr ""
+
+#: en_US/emacs.xml:270(para)
+msgid "After modifying this file, execute the following command:"
+msgstr ""
+
+#: en_US/emacs.xml:273(command)
+#, fuzzy
+msgid "xrdb -merge ~/.Xresources"
+msgstr "Medan Gabung &Mel"
+
+#: en_US/emacs.xml:274(para)
+msgid "Then restart <application>Emacs</application> to apply the changes."
+msgstr ""
+
+#: en_US/emacs.xml:395(title)
+msgid "Basic Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:397(para)
+msgid "The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key."
+msgstr ""
+
+#: en_US/emacs.xml:403(title)
+msgid "Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:404(segtitle)
+#, fuzzy
+msgid "Shortcut"
+msgstr "Kekunci Pintasan"
+
+#: en_US/emacs.xml:405(segtitle)
+#, fuzzy
+msgid "Description"
+msgstr "Huraian"
+
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:412(keycap)
+#: en_US/emacs.xml:430(keycap) en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:443(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:458(keycap)
+#: en_US/emacs.xml:463(keycap) en_US/emacs.xml:468(keycap)
+#: en_US/emacs.xml:473(keycap) en_US/emacs.xml:478(keycap)
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:509(keycap)
+#: en_US/emacs.xml:514(keycap) en_US/emacs.xml:515(keycap)
+#: en_US/emacs.xml:520(keycap) en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap) en_US/emacs.xml:533(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "Ctrl"
+msgstr ""
+
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:521(keycap) en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "c"
+msgstr ""
+
+#: en_US/emacs.xml:413(keycap)
+msgid "p"
+msgstr ""
+
+#: en_US/emacs.xml:407(seg) en_US/emacs.xml:508(seg) en_US/emacs.xml:514(seg)
+#: en_US/emacs.xml:520(seg) en_US/emacs.xml:532(seg) en_US/emacs.xml:540(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+
+#: en_US/emacs.xml:415(seg)
+msgid "Parse DTD"
+msgstr ""
+
+#: en_US/emacs.xml:431(keycap) en_US/emacs.xml:437(keycap)
+#, fuzzy
+msgid "Shift"
+msgstr "Jepun, Shift-JIS"
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:438(keycap)
+msgid ","
+msgstr ""
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:439(keycap)
+#, fuzzy
+msgid "Tab"
+msgstr "Awalan &tab:"
+
+#: en_US/emacs.xml:430(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+msgstr ""
+
+#: en_US/emacs.xml:433(seg)
+msgid "Display list of valid tags"
+msgstr ""
+
+#: en_US/emacs.xml:436(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of "
+"tag, <placeholder-5/>"
+msgstr ""
+
+#: en_US/emacs.xml:440(seg)
+#, fuzzy
+msgid "Complete the tag"
+msgstr "Semakan ejaan selesai."
+
+#: en_US/emacs.xml:443(keycap)
+msgid "g"
+msgstr ""
+
+#: en_US/emacs.xml:445(seg)
+msgid "Cancel a command in the minibuffer"
+msgstr ""
+
+#: en_US/emacs.xml:449(keycap)
+msgid "/"
+msgstr ""
+
+#: en_US/emacs.xml:448(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:450(seg)
+#, fuzzy
+msgid "Close tag"
+msgstr "Tutup dokumen"
+
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:533(keycap)
+msgid "a"
+msgstr ""
+
+#: en_US/emacs.xml:455(seg)
+msgid "Move cursor to beginning of line"
+msgstr ""
+
+#: en_US/emacs.xml:458(keycap)
+msgid "e"
+msgstr ""
+
+#: en_US/emacs.xml:460(seg)
+msgid "Move cursor to the end of the line"
+msgstr ""
+
+#: en_US/emacs.xml:463(keycap)
+#, fuzzy
+msgid "Home"
+msgstr "Rumah"
+
+#: en_US/emacs.xml:465(seg)
+msgid "Move cursor to the beginning of the file"
+msgstr ""
+
+#: en_US/emacs.xml:468(keycap)
+msgid "End"
+msgstr ""
+
+#: en_US/emacs.xml:470(seg)
+msgid "Move cursor to the end of the file"
+msgstr ""
+
+#: en_US/emacs.xml:473(keycap)
+msgid "k"
+msgstr ""
+
+#: en_US/emacs.xml:475(seg)
+#, fuzzy
+msgid "Cut line"
+msgstr "Baris pertama"
+
+#: en_US/emacs.xml:478(keycap)
+msgid "y"
+msgstr ""
+
+#: en_US/emacs.xml:480(seg)
+#, fuzzy
+msgid "Paste line"
+msgstr "Baris pertama"
+
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:515(keycap)
+msgid "s"
+msgstr ""
+
+#: en_US/emacs.xml:485(seg)
+msgid "Search forward in the file"
+msgstr ""
+
+#: en_US/emacs.xml:488(keycap)
+msgid "r"
+msgstr ""
+
+#: en_US/emacs.xml:490(seg)
+msgid "Search backwards in the file"
+msgstr ""
+
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap) en_US/emacs.xml:527(keycap)
+msgid "Meta"
+msgstr ""
+
+#: en_US/emacs.xml:493(keycap)
+msgid "$"
+msgstr ""
+
+#: en_US/emacs.xml:495(seg) en_US/emacs.xml:500(seg)
+#, fuzzy
+msgid "Check spelling of current word"
+msgstr "Semakan ejaan selesai."
+
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:514(keycap)
+#: en_US/emacs.xml:520(keycap)
+#, fuzzy
+msgid "x"
+msgstr "x"
+
+#: en_US/emacs.xml:499(keycap) en_US/emacs.xml:504(keycap)
+#, fuzzy
+msgid "Enter"
+msgstr "Masukkan Katalaluan"
+
+#: en_US/emacs.xml:498(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:503(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:505(seg)
+#, fuzzy
+msgid "Check spelling of current buffer"
+msgstr "Semakan ejaan selesai."
+
+#: en_US/emacs.xml:509(keycap)
+msgid "f"
+msgstr ""
+
+#: en_US/emacs.xml:511(seg)
+#, fuzzy
+msgid "Open file"
+msgstr "Buka Fail"
+
+#: en_US/emacs.xml:517(seg)
+#, fuzzy
+msgid "Save file"
+msgstr "Simpan ke fail"
+
+#: en_US/emacs.xml:523(seg)
+msgid "Exit <placeholder-1/> and prompt to save files if necessary"
+msgstr ""
+
+#: en_US/emacs.xml:527(keycap)
+msgid "q"
+msgstr ""
+
+#: en_US/emacs.xml:529(seg)
+#, fuzzy
+msgid "Fill paragraph"
+msgstr ""
+"Perenggan Berikut Perenggan Berikut Perenggan Berikut Perenggan Berikut "
+"Perenggan Berikut Perenggan Berikut Perenggan Berikut Perenggan Berikut "
+
+#: en_US/emacs.xml:536(computeroutput)
+#, fuzzy, no-wrap
+msgid "url"
+msgstr "URL:"
+
+#: en_US/emacs.xml:537(computeroutput)
+#, no-wrap
+msgid "ulink"
+msgstr ""
+
+#: en_US/emacs.xml:535(seg)
+msgid ""
+"Edit attributes for a tag (for example, you can edit the <placeholder-1/> "
+"attribute of the <placeholder-2/> tag)"
+msgstr ""
+
+#: en_US/emacs.xml:544(seg)
+#, fuzzy
+msgid "Exit edit attributes"
+msgstr "Sunting Persamaan Latex"
+
+#: en_US/emacs.xml:550(title) en_US/emacs-nxml.xml:77(title)
+msgid "Examples"
+msgstr ""
+
+#: en_US/emacs.xml:552(para)
+msgid ""
+"The table or reference card of Emacs and PSGML commands can be confusing for "
+"beginners. This section provides some examples of how to use them."
+msgstr ""
+
+#: en_US/emacs.xml:559(title)
+msgid "Tag Completion"
+msgstr ""
+
+#: en_US/emacs.xml:563(para)
+msgid "This section assumes that you have already parsed the DTD file."
+msgstr ""
+
+#: en_US/emacs.xml:567(para)
+msgid ""
+"To avoid having to type a tag repeatedly, use the key combination "
+"<keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. "
+"At the bottom of the <application>Emacs</application> window, the following "
+"prompt appears:"
+msgstr ""
+
+#: en_US/emacs.xml:574(prompt)
+msgid "Tag: <"
+msgstr ""
+
+#: en_US/emacs.xml:576(para)
+msgid ""
+"To view a list of available tags, use either the <keycap>Tab</keycap> or "
+"<keycap>?</keycap>. If you know the first few letters of a tag, enter them, "
+"followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, "
+"that tag appears. If more than one completion exists, a complete list of "
+"possible tags appears."
+msgstr ""
+
+#: en_US/emacs.xml:585(para)
+msgid ""
+"If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, "
+"<keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the "
+"example below:"
+msgstr ""
+
+#: en_US/emacs.xml:602(title)
+msgid "Tag Closure"
+msgstr ""
+
+#: en_US/emacs.xml:604(para)
+msgid ""
+"After you open a tag, you must close it. The easiest way to close an open "
+"tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</"
+"keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most "
+"recently opened tag."
+msgstr ""
+
+#: en_US/emacs.xml:616(title)
+msgid "Other Emacs Tasks"
+msgstr ""
+
+#: en_US/emacs.xml:619(title)
+msgid "Working with One Window"
+msgstr ""
+
+#: en_US/emacs.xml:620(para)
+msgid ""
+"Sometimes in <application>Emacs</application>, the window becomes split, "
+"with tags completions or other text in an alternate window. To return to a "
+"single window, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+msgstr ""
+
+#: en_US/emacs.xml:630(title)
+#, fuzzy
+msgid "Saving Work"
+msgstr "Tutup Tanpa Simpan"
+
+#: en_US/emacs.xml:631(para)
+msgid ""
+"To save your work, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>s</keycap></keycombo>."
+msgstr ""
+
+#: en_US/emacs.xml:642(title)
+#, fuzzy
+msgid "The \"Clear/Quit\" Command"
+msgstr "Hilangkan Warna Latarbelakang"
+
+#: en_US/emacs.xml:643(para)
+msgid ""
+"If the tag completion process becomes unwieldy or confusing, use the "
+"keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to "
+"exit back to the text. <application>Emacs</application> clears any prompts "
+"and returns to the buffer text."
+msgstr ""
+
+#: en_US/emacs.xml:653(title)
+#, fuzzy
+msgid "Opening a new file"
+msgstr "Ralat mengimport fail %s"
+
+#: en_US/emacs.xml:654(para)
+msgid ""
+"To open a new file, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the "
+"<application>Emacs</application> window. Enter the file name, using "
+"<keycap>Tab</keycap> completion if desired, of the file you wish to open."
+msgstr ""
+
+#: en_US/emacs.xml:668(title)
+msgid "Closing <application>Emacs</application>"
+msgstr ""
+
+#: en_US/emacs.xml:669(para)
+msgid ""
+"To close <application>Emacs</application> use the key sequence "
+"<keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, "
+"<keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have "
+"not saved your work, <application>Emacs</application> prompts you to save "
+"any changed files."
+msgstr ""
+
+#: en_US/emacs.xml:687(title) en_US/emacs-nxml.xml:127(title)
+msgid "Additional Resources"
+msgstr ""
+
+#: en_US/emacs.xml:689(para)
+msgid ""
+"Additional Emacs and PSGML references are available at the following "
+"locations:"
+msgstr ""
+
+#: en_US/emacs.xml:697(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+msgid "Emacs Quick Reference Guide"
+msgstr ""
+
+#: en_US/emacs.xml:701(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs.xml:708(para)
+msgid ""
+"Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/"
+"usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+msgstr ""
+
+#: en_US/emacs.xml:714(para)
+msgid ""
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—"
+"<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of "
+"Emacs commands for PSGML mode."
+msgstr ""
+
+#: en_US/emacs.xml:723(citetitle)
+msgid "PSGML Tricks"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:11(title)
+msgid "Emacs and nXML Mode"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:14(primary) en_US/emacs-nxml.xml:51(primary)
+msgid "nXML"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:23(secondary)
+#, fuzzy
+msgid "nXML mode"
+msgstr "Anda telah mengubah mod arah."
+
+#: en_US/emacs-nxml.xml:26(para)
+msgid ""
+"You can also use the nXML mode available for <application>Emacs</"
+"application> to make it even easier to write in DocBook XML format. nXML "
+"mode provides context-sensitive editing using completion, real time validity "
+"error checking, syntax highlighting and indentation. All you need to do is "
+"install an RPM!!"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:35(title)
+msgid "Early stages"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:36(para)
+msgid ""
+"Please be aware the nxml-mode for <application>Emacs</application> is quite "
+"new, so there are a few things that the advanced user might notice when "
+"using it with other documents types. If you keep an eye on the mailing-list, "
+"you can keep up to date with these, as well as ask questions. For more "
+"details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:48(title)
+msgid "Getting the nXML RPM"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:52(secondary)
+msgid "RPM"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:56(primary)
+msgid "nXML RPM"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:59(para)
+msgid ""
+"To use nXML mode with emacs, you will need to install the nXML RPM available "
+"from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/"
+"\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www."
+"thaiopensource.com/download/\">http://www.thaiopensource.com/download/</"
+"ulink>. The source requires a lot more work to setup, therefore we will only "
+"be concentrating on the RPM version."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:69(para)
+msgid ""
+"Information on where to get the source is available in <xref linkend=\"sn-"
+"emacs-additional-resources\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:79(para)
+msgid ""
+"Compared to PSGML mode there are only couple of commands that you need. This "
+"speeds up writing with <application>Emacs</application> considerably, which "
+"means you can concentrate more on the content of your article."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:88(para)
+msgid ""
+"To create a tag, type <userinput><</userinput> and then type the keyword. "
+"To complete the keyword, press <command>Ctrl-Ret</command>, then add the "
+"last <userinput>></userinput>. To close a tag, type <userinput></</"
+"userinput>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:97(para)
+msgid ""
+"When you open a document that doesn't have a DOCTYPE declaration at the top "
+"of the file, you will get this message and tag completion won't work because "
+"nXML will not know what format you are writing."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:104(para)
+msgid ""
+"To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</"
+"command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/"
+"schema/</filename> and load <filename>docbook.rnc</filename>. "
+"<application>Emacs</application> will then prompt you to save it in the "
+"current working directory."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:115(para)
+msgid ""
+"The commands already discussed are the only differences between using "
+"<application>Emacs</application> with PSGML mode and <application>Emacs</"
+"application> with nXML mode. You will still need to use all the same "
+"commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:129(para)
+msgid ""
+"Additional Emacs and nXML references are available at the following "
+"locations:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:136(ulink)
+msgid "http://www.thaiopensource.com/download/"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:137(citetitle)
+#, fuzzy
+msgid "Author's download area"
+msgstr "Penulis dan penyelenggara"
+
+#: en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:147(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:157(title)
+#, fuzzy
+msgid "nXML README File"
+msgstr "Ralat mengimport fail %s"
+
+#: en_US/emacs-nxml.xml:161(para)
+msgid ""
+"This file can be found in the directory you extracted the source into, or in "
+"<filename>/usr/share/doc/nxml-mode-<replaceable><version></"
+"replaceable>/</filename> if you installed the RPM."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:169(para)
+msgid "README file:"
+msgstr "Fail README:"
+
+#: en_US/emacs-nxml.xml:171(para)
+msgid ""
+"This is a new major mode for GNU Emacs for editing XML documents. It "
+"supports editing well-formed XML documents and also provides schema-"
+"sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:177(para)
+msgid ""
+"To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs "
+"version 20 will not work properly, nor will XEmacs. To get started, do the "
+"following:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:184(command)
+msgid "M-x load-file RET rng-auto.el RET"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:187(para)
+msgid ""
+"This defines the necessary autoloads. Now, visit a file containing an XML "
+"document, and do the following:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:192(command)
+msgid "M-x nxml-mode"
+msgstr "M-x nxml-mode"
+
+#: en_US/emacs-nxml.xml:195(para)
+msgid "Now do"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:200(command)
+msgid "C-h m"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:203(para)
+msgid ""
+"For information on how to use nxml-mode. The beginnings of a manual are in "
+"nxml-mode.info. You can read this using:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:209(command)
+msgid "C-u M-x info RET nxml-mode.info RET"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:212(para)
+msgid ""
+"It's also installed as an entry at the end of the top-level info directory. "
+"So you can read it with <command>C-h i</command> as usual."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:217(para)
+msgid ""
+"You can use <filename>test.valid.xml</filename> and <filename>test.invalid."
+"xml</filename> as examples of valid and invalid XML documents."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:223(para)
+msgid "To get things automatically loaded each time you start Emacs, add:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:228(computeroutput)
+#, no-wrap
+msgid ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+msgstr ""
+
+#: en_US/emacs-nxml.xml:232(para)
+msgid ""
+"to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-"
+"200YMMDD</computeroutput> is the directory containing the <filename>.elc</"
+"filename> files. Note that <filename>rng-auto.el</filename> does not load "
+"all of the nxml-mode code; it merely sets things up so that all the features "
+"of nxml-mode will be autoloaded properly. You should not try to autoload "
+"<filename>rng-auto.el</filename> itself."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:242(para)
+msgid ""
+"To use nxml-mode automatically for files with an extension of <filename>xml</"
+"filename>, <filename>xsl</filename>, <filename>rng</filename> or "
+"<filename>xhtml</filename>, add the following to your <filename>.emacs</"
+"filename> file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:250(computeroutput)
+#, no-wrap
+msgid ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+msgstr ""
+
+#: en_US/emacs-nxml.xml:255(para)
+msgid ""
+"If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are "
+"running Emacs 21.3 or later, then I recommend enabling unify-8859-on-"
+"decoding-mode, by adding the following to your <filename>.emacs</filename> "
+"file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:263(computeroutput)
+#, no-wrap
+msgid "(unify-8859-on-decoding-mode)"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:266(para)
+msgid ""
+"To get validation and schema-sensitive editing, you need a RELAX NG Compact "
+"Syntax (RNC) schema for you document. The schema directory includes some "
+"schemas for popular document types."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:272(para)
+msgid ""
+"For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://"
+"relaxng.org/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:277(para)
+msgid ""
+"For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://"
+"relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial."
+"html</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:282(para)
+msgid ""
+"For automatically creating RNC schemas, I recommend my Trang program: <ulink "
+"url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee."
+"thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:293(para)
+msgid "Infer an RNC schema from an instance document"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:298(para)
+msgid "Convert a DTD to an RNC schema"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:303(para)
+msgid "Convert a RELAX NG XML syntax schema to an RNC schema"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:288(para)
+msgid "You can use this to <placeholder-1/>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:310(para)
+msgid ""
+"To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also "
+"use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html"
+"\">http://www.pantor.com/download.html\"</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:316(para)
+msgid ""
+"To convert a W3C XML Schema to an RNC schema, you need first to convert it "
+"to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on "
+"top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www."
+"dev.java.net/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:323(para)
+msgid "The file <filename>NEWS</filename> describes recent changes."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:327(para)
+msgid ""
+"Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-"
+"mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug "
+"reports, discussion. I will announce all new versions there."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:333(para)
+msgid "James Clark"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:336(para)
+msgid "jjc@@thaiopensource.com"
+msgstr ""
+
+#: en_US/acknowledgments.xml:11(title)
+msgid "Acknowledgments"
+msgstr ""
+
+#: en_US/acknowledgments.xml:13(para)
+msgid ""
+"This document is based on a document started by Tammy Fox (tfox at redhat."
+"com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray "
+"Fuller (jrfuller at redhat.com)."
+msgstr ""
+
+#: en_US/acknowledgments.xml:19(para)
+msgid ""
+"A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to "
+"fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr ""
+
+#: en_US/acknowledgments.xml:25(para)
+msgid ""
+"Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to "
+"add the trailing slashes to the <command>figure</command> tag example in "
+"<filename>docs-xml-tags.xml</filename>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:32(para)
+msgid ""
+"A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been "
+"applied to add <xref linkend=\"ch-vim\"/>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:37(para)
+msgid ""
+"A patch from Karsten Wade (kwade at redhat.com) has been applied to add "
+"<xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields "
+"(stickster at gmail.com)."
+msgstr ""
+
+#. This section has been removed.
+#. <para>
+#. A patch from Paul W. Frields (stickster at gmail.com) has been applied
+#. to add more explanation of the <command>screen</command> tag set to <xref
+#. linkend="sn-xml-tags-screen"></xref>.
+#. </para>
+#: en_US/acknowledgments.xml:50(para)
+msgid ""
+"A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been "
+"applied to more fully explaing the document building system."
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: en_US/acknowledgments.xml:0(None)
+msgid "translator-credits"
+msgstr "Sharuzzaman Ahmat Raslan <sharuzzaman@@myrealbox.com>, 2007"
+@
+
+
+1.1
+log
+ at Added new file and updated Malay translation
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-12-15 16:51-0500\n"
+d40 5
+a44 1
+#: en_US/rpm-info.xml:31(holder)
+d48 1
+a48 1
+#: en_US/rpm-info.xml:33(title)
+d52 1
+a52 1
+#: en_US/rpm-info.xml:34(desc)
+d56 5
+a60 1
+#: en_US/rpm-info.xml:38(details)
+d64 1
+a64 1
+#: en_US/rpm-info.xml:42(details)
+d68 1
+a68 1
+#: en_US/rpm-info.xml:46(details)
+d72 1
+a72 1
+#: en_US/rpm-info.xml:50(details)
+d76 1
+a76 1
+#: en_US/rpm-info.xml:54(details)
+d80 1
+a80 1
+#: en_US/rpm-info.xml:58(details)
+d84 1
+a84 1
+#: en_US/rpm-info.xml:62(details)
+d88 1
+a88 1
+#: en_US/rpm-info.xml:69(details)
+d92 171
+d268 8
+a275 1
+msgid "This chapter shows how to publish official Fedora Documentation Project work to the <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> website. To publish official documentation, you must be approved to write to the web repository in CVS. Access for publishing is limited to contributors who have demonstrated capacity for working with CVS and other project tools. Once you have acquired and are comfortable with these skills, contributions as a publisher are welcome."
+d283 7
+a289 1
+msgid "The <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> website is a set of PHP files and scripts. Publishers maintain these files in a CVS repository, and the website host retrieves them hourly to refresh the site. The host does not automatically use the newest content for the website. Instead, it pulls files with the CVS tag <systemitem>LIVE</systemitem> to populate the website."
+d293 5
+a297 1
+msgid "Each publisher sets up a local testing website on an available Fedora system. This site, sometimes called a <firstterm>sandbox</firstterm>, allows the publisher to test and view changes to documents, and ensure stability on the public site."
+d305 3
+a307 1
+msgid "To test document publishing, first set up a web sandbox on a local Fedora system."
+d329 3
+a331 1
+msgid "Change the permissions on this directory to make it easier to access for your normal user account."
+d334 1
+a334 2
+#: en_US/publishing.xml:53(replaceable)
+#: en_US/publishing.xml:62(replaceable)
+d370 7
+a376 1
+msgid "You must have access to the <systemitem>cvsweb</systemitem> module through the Fedora Account System to check in changes. If you do not have access, you can use <userinput><![CDATA[:pserver:anonymous]]></userinput> in place of <userinput><![CDATA[:ext:username]]></userinput> above. Visit the Fedora Account System at <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> for more information."
+d380 3
+a382 1
+msgid "Edit the <filename>/etc/hosts</filename> file and add the following line <emphasis>after</emphasis> all other lines:"
+d391 3
+a393 1
+msgid "Create a file <filename>/etc/httpd/conf.d/fpo.conf</filename> with the following content:"
+d397 3
+a399 1
+msgid "Create a file <filename>/etc/php.d/fpo.ini</filename> with the following content:"
+d426 3
+a428 1
+msgid "To test the new sandbox site, open a Web browser and point it at the URL <uri>http://docs.localhost.localdomain</uri>."
+d441 3
+a443 1
+msgid "Follow these guidelines to ensure maintainability and ease of use for all publishers."
+d447 5
+a451 1
+msgid "Use a short, descriptive name for the document directory. The module name from its Docs CVS location is usually appropriate. Good examples include <filename class=\"directory\">install-guide/</filename> or <filename class=\"directory\">example-tutorial/</filename>."
+d455 3
+a457 1
+msgid "Under the document directory, include a branch directory if the document references specific features of a particular Fedora release."
+d461 5
+a465 1
+msgid "Under the branch directory (or document directory if no branches are necessary), make at least a <filename class=\"directory\">en_US/</filename> directory. Make an additional directory for each locale that has been fully translated."
+d473 5
+a477 1
+msgid "To add content, follow the procedure below. The following commands show an example of adding content for a new document called the <citetitle>Foobar Tutorial</citetitle>. This document includes a translation for the \"zz_XX\" locale and follows specifics of each Fedora release."
+d494 2
+a495 1
+msgid "Build the HTML version of each translation of the document from Docs CVS."
+d522 3
+a524 1
+msgid "Convert the HTML in each directory to PHP using the provided <filename>docbookhtml2php.py</filename> script."
+d528 8
+a535 1
+msgid "Create any necessary <filename>index.php</filename> files for the overall directories. Each document and branch directory must have an <filename>index.php</filename> file directing users to appropriate content. In this example, the necessary files are <filename>foobar-tutorial/index.php</filename> and <filename>foobar-tutorial/f7/index.php</filename>. You do not need to write these files from scratch. Copy an existing file from another document, and change it as needed to suit the new document."
+d539 3
+a541 1
+msgid "Depending on content, publication may include changing a higher-level <filename>index.php</filename> file."
+d545 3
+a547 1
+msgid "To test the changes in your sandbox, open a web browser and point it at <uri>http://docs.localhost.localdomain/</uri>."
+d556 3
+a558 1
+msgid "<emphasis>Do not proceed further until you test all changes.</emphasis> Check that all links and index pages work."
+d592 3
+a594 1
+msgid "Commit the changes to CVS. Use a message that describes the document being committed."
+d621 1
+a621 2
+#: en_US/vim.xml:16(primary)
+#: en_US/vim.xml:33(primary)
+d626 7
+a632 1
+msgid "VIM has many features to help you write XML content such as DocBook, including syntax highlighting and customizable key bindings. Additionally, one can easily use external programs from VIM for features such as spell-checking. This chapter assumes you already know generally how to use VIM; if you want to learn how, try the <command>vimtutor</command> or by typing <userinput>:help tutor</userinput> from inside VIM."
+d639 1
+a639 2
+#: en_US/vim.xml:34(secondary)
+#: en_US/emacs.xml:44(secondary)
+d646 3
+a648 1
+"Below is a short sample <filename>.vimrc</filename> file that turns on some VIM features useful for editing SGML or XML content such as DocBook: <screen>\n"
+d663 7
+a669 1
+msgid "Some of these features require the <filename>vim-enhanced</filename> package to be installed. If you are using or the <filename>vim-minimal</filename> package, or if you are using an older version of VIM, you may not have the <filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still download <ulink url=\"http://vim.org/scripts/script.php?script_id=39\">matchit.zip from Vim.org</ulink> and load it separately."
+d679 8
+a686 2
+"VIM can speed up your DocBook creation by mapping frequently typed tags (or any words or phrases) onto short key combinations. By default, the keymap leader is the backslash (<literal>\\</literal>), but it can be redefined with a command like <userinput>let mapleader =\n"
+" \",\"</userinput>. There are two ways to use the following example; you can put it directly in your <filename>.vimrc</filename>, or you can save it in a separate file and load it with a <userinput>source</userinput> command in your <filename>.vimrc</filename>. <screen>\n"
+d709 2
+a710 1
+"imap<leader>cm <command></command><esc>F>a \n"
+d718 5
+a722 1
+msgid "Unfortunately, there is not currently a complete macro set for all DocBook commands, so you will need to define them yourself or customize the definitions in the examples from <xref linkend=\"sn-vim-additional-resources\"/>."
+d734 4
+a737 1
+msgid "<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to Vi Improved (VIM)</citetitle>"
+d741 3
+a743 1
+msgid "The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick Reference Card</ulink>"
+d752 5
+a756 1
+msgid "The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the <filename>vim-common</filename> package —<filename>/usr/share/vim/<replaceable><version></replaceable>/doc/intro.txt</filename> or type <userinput>:help intro</userinput> from within VIM"
+d765 5
+a769 1
+msgid "In this chapter, you will find an example of a very short tutorial as used by the Fedora Documentation Project. This example is specific to the way the Docs Project uses DocBook XML. The example consists of a set of files used to hold the content and metadata for the tutorial."
+d776 1
+a776 2
+#: en_US/tutorial.xml:21(primary)
+#: en_US/tutorial.xml:56(primary)
+d798 5
+a802 1
+msgid "The <filename>rpm-info.xml</filename> file contains all the required metadata for the document. This metadata includes title, authorship, licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates the content of this file:"
+d810 5
+a814 1
+msgid "If you are not familiar with XML editing, copy and paste this file from an existing module and then edit the values for the various elements as appropriate. Consult Fedora Documentation Project members and help channels for more assistance if needed."
+d823 6
+a828 1
+msgid "Writing good technical documentation is not simply reproducing command lines and instruction sets. Good documentation is easy to read, understand, and translate, and presents a concise logical progression of concepts. Good documentation can also be defined by what it does <emphasis>not</emphasis> contain. Your tutorial should avoid:"
+d853 6
+a858 1
+msgid "This chapter contains style rules and guidelines for writing Fedora documentation. Guidelines are not the same as rules. It is acceptable to violate a guideline when it makes your material easier to understand. Follow guidelines whenever possible, but follow rules at all times. Assume any advice is a guideline unless identified otherwise."
+d866 5
+a870 1
+msgid "Writing well comes naturally to almost no one. It is a skill that professional writers, even famous ones, must practice constantly. <firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> is the quality that separates elegant writing from the merely functional."
+d874 5
+a878 1
+msgid "For example, refer to. <ulink url=\"http://www.online-literature.com/james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>. Please note that this example contains some mature themes and language, and is not suitable for all readers."
+d882 9
+a890 1
+msgid "Elegance comes in many forms. In prose and poetry, elegant writing may not follow some (or any) common rules of grammar, syntax, or spelling. A good example is Episode 18, \"Penelope,\" in James Joyce's novel <citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long streams of words without punctuation to simulate a character's internal consciousness. By violating basic rules of grammar and syntax, Joyce simulates the disorganized but loosely connected thought patterns of the narrator."
+d894 8
+a901 1
+msgid "Technical documentation, however, should always respect these rules. The more a document departs from standard language usage, the more difficult the material becomes for the reader. For example, readers may not be native speakers of the language used, or they might be reading a translation. If the writer uses slang, idioms, or jargon, a reader or translator may easily become confused. The following example compares two different written executions of the same idea:"
+d915 5
+a919 1
+msgid "So you made the changes I showed you in the last section. What's the next thing you should do? Just pop your thumb drive onto your system and read the <filename>messages</filename> log. When you see \"USB device found,\" then Bob's your uncle."
+d930 5
+a934 2
+"After you complete the configuration changes above, attach the USB removable media to your system. Use the <command>dmesg</command> command to examine the kernel message log. The message <computeroutput>USB device\n"
+"\t found</computeroutput> indicates that your device was installed successfully."
+d938 5
+a942 1
+msgid "The first example is more conversational English, which is not appropriate for official written documentation. The second example is more formal, but as a result it is easier to comprehend, both for native readers and translators."
+d946 9
+a954 1
+msgid "Following style rules and guidelines also makes readers more comfortable with a set of documents. Consistent style enhances the professional appearance of documentation, and its perceived value. On the other hand, lapses in punctuation or poor grammar negatively affect a reader's reaction to written material. A reader can feel that an otherwise correct technical document is lacking in authority, simply because it is poorly written. Readers feel at ease when they do not have to struggle to understand an author's use of language."
+d958 5
+a962 1
+msgid "This chapter cannot possibly cover enough material to make every reader a good writer. Some manuals devoted entirely to writing style are themselves hundreds of pages long. This chapter provides enough guidelines for intermediate writers to understand style usage in technical documentation."
+d966 4
+a969 1
+msgid "If you are not a practiced writer, whether of technical documentation or otherwise, you may benefit from other style resources. The following list is far from comprehensive, but provides a starting point:"
+d973 5
+a977 1
+msgid "<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules and links to online versions can be found at: <ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+d981 4
+a984 1
+msgid "<citetitle>The Chicago Manual of Style</citetitle>, by the University of Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle.org/\">http://www.chicagomanualofstyle.org/</ulink>"
+d988 4
+a991 1
+msgid "<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/\">http://www.powa.org/</ulink>"
+d995 7
+a1001 1
+msgid "There are many free software documentation projects which have developed their own style guidelines. This chapter, in fact, draws heavily on the <citetitle>GNOME Documentation Style Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/\">http://developer.gnome.org/documents/style-guide/</ulink>."
+d1021 3
+a1023 1
+msgid "This chapter provides a brief introduction to writing technical documentation."
+d1032 4
+a1035 1
+msgid "Technical writing for the Fedora Project imposes special constraints beyond the basic requirements of good prose. Good Fedora technical documentation has the following characteristics:"
+d1043 3
+a1045 1
+msgid "Describe all of the functionality of a product. Do not omit functionality that you regard as irrelevant for the user."
+d1053 3
+a1055 1
+msgid "Describe what you see. Do not describe what you want to see. Present your information in the order that users experience the subject matter."
+d1064 4
+a1067 1
+msgid "Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>) to help make your writing clear."
+d1075 3
+a1077 1
+msgid "Use agreed vocabulary throughout your documentation. Use the same vocabulary as other writers who are working on related documentation."
+d1085 4
+a1088 1
+msgid "Review your work frequently as you write your document. Ask yourself which words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for specific guidelines."
+d1096 3
+a1098 1
+msgid "This section contains some basic style guidelines. Subsequent sections in this chapter expand on these guidelines to give more detailed guidance."
+d1119 4
+a1122 1
+msgid "Under normal operating conditions, the kernel does not always immediately write file data to the disks, storing it in a memory buffer and then periodically writing to the disks to speed up operations."
+d1130 3
+a1132 1
+msgid "Normally, the kernel stores the data in memory prior to periodically writing the data to the disk."
+d1157 10
+a1166 1
+msgid "The <application>Workspace Switcher</application> applet helps you navigate all of the virtual desktops available on your system. The X Window system, working in hand with a piece of software called a <emphasis>window manager</emphasis>, allows you to create more than one virtual desktop, known as <emphasis>workspaces</emphasis>, to organize your work, with different applications running in each workspace. The <application>Workspace Switcher</application> applet is a navigational tool to get around the various workspaces, providing a miniature road map in the GNOME panel showing all your workspaces and allowing you to switch easily between them."
+d1174 7
+a1180 1
+msgid "Use the <application>Workspace Switcher</application> to add new <emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different applications in each workspace. The <application>Workspace Switcher</application> applet provides a miniature map that shows all of your workspaces. You can use the <application>Workspace Switcher</application> applet to switch between workspaces."
+d1184 3
+a1186 1
+msgid "Plan the order of paragraphs before you start writing. Decide which topic you want to cover in each paragraph."
+d1194 3
+a1196 1
+msgid "Use explicit examples to demonstrate how an application works. Provide instructions rather than descriptions."
+d1204 2
+a1205 1
+msgid "There is a text box that you can use to find out the definition of a word."
+d1213 3
+a1215 1
+msgid "To request a definition of a word, type the word in the text box, then select <guilabel>Lookup</guilabel>."
+d1219 3
+a1221 1
+msgid "Do not apply this guideline too rigidly. Sometimes you must explain how software works to support your how-to examples."
+d1253 8
+a1260 1
+msgid "Inappropriate tone hinders reader access to information. A neutral tone free of opinion or personal flavor improves the reader's comprehension. Neutral tone helps writers to work in parallel on a large technical documentation project. Furthermore, additional writers may join the project at any time. Use of a neutral tone helps to achieve consistency across a documentation set, and thereby facilitates user access to information. The best way to achieve a common, neutral tone is to apply the following principles:"
+d1268 3
+a1270 1
+msgid "Humor distracts from the information you are trying to provide. Humor also makes documentation difficult to translate. Stay factual."
+d1278 4
+a1281 1
+msgid "Whether you think a function is useful or woeful is irrelevant. Report the function to the user, with instructions about how to use the function. Stay accurate."
+d1290 3
+a1292 1
+msgid "Colloquial language is difficult to translate and usually culture-specific. Stay neutral."
+d1300 3
+a1302 1
+msgid "An expression that is in common use today might convey something completely different tomorrow. Stay technical."
+d1310 3
+a1312 1
+msgid "Statements about the future developments of a product do not belong in technical documentation. Write about what you see right now. Stay real."
+d1321 7
+a1327 1
+msgid "All of the decisions that you make about the structure and content of a manual follow from an understanding of the audience. Consider how the audience accesses the documentation, what sort of information the audience needs, and the experience level of the audience. Usually, you need to create documentation that is suitable for different audiences. The following sections introduce some of the audience-related topics you need to consider."
+d1336 5
+a1340 1
+msgid "Do not waste the time of the user who looks for information in your documentation. Users do not read technical documentation for entertainment. Users usually have specific questions. You need to give clear answers to those questions."
+d1349 9
+a1357 1
+msgid "New users to Fedora are likely to consult online tutorials for guidance about unfamiliar applications or functionality. Each tutorial should contain enough introductory information to tell new users how to start using the relevant functions. Each tutorial should also contain enough usage instructions to tell users the different actions that they can perform with the command or function. Keep these instructions task-oriented. Do not describe GUI screens, dialogs, and dialog elements in a tutorial, unless there is an unusual feature that affects your instructions."
+d1365 4
+a1368 1
+msgid "Experienced users are more likely to use documentation as a reference. The documentation therefore needs to be complete, well-organized, and in the case of printed manuals, well-indexed."
+d1376 3
+a1378 1
+msgid "To avoid offending your readers, apply the following guidelines to your documentation:"
+d1387 5
+a1391 1
+msgid "Insider language includes both undefined jargon and the tendency of the computer community to shorten words. For example, use the term <literal>documentation</literal> instead of the term <literal>docs</literal>. A term may be jargon if it fails all the following conditions:"
+d1395 4
+a1398 1
+msgid "The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> (<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora.redhat.com/docs/jargon-buster/</ulink>)."
+d1402 4
+a1405 1
+msgid "The term does not appear in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/ </ulink>)."
+d1409 2
+a1410 1
+msgid "The term does not appear in the glossary of the manual that you are writing."
+d1414 2
+a1415 1
+msgid "The term is not defined in the body text of the manual that you are writing."
+d1423 4
+a1426 1
+msgid "Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</literal> do not exist. There is no need to identify gender in your instructions."
+d1434 3
+a1436 1
+msgid "There is little point in giving an example that everyone in your town knows about, but is a complete mystery to everyone else in the world."
+d1444 4
+a1447 1
+msgid "There are few experiences more irritating for a user than documentation that says an action is easy or quick, when in fact the user cannot complete the action. Do not qualify or prejudge actions."
+d1451 3
+a1453 1
+msgid "Other parts of this guide discuss in more detail tone and language usage that can cause offense."
+d1465 4
+a1468 1
+msgid "This section is drawn partly from the <citetitle>GDSG</citetitle>, and partly from <citetitle>The Elements of Style</citetitle>, updated as necessary for the needs of 21st-century technical documentation writers."
+d1474 9
+a1482 1
+msgid "This section contains an alphabetical list of grammar and usage guidelines for use in Fedora documentation. Many of these guidelines are only applicable to English-language usage, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+d1490 5
+a1494 1
+msgid "A shortened form of a word or phrase that takes the place of the full word or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, <literal>p.m.</literal>, and so on. Apply the following rules when you use abbreviations:"
+d1498 3
+a1500 1
+msgid "Avoid creating new abbreviations. Unfamiliar abbreviations can confuse rather than clarify a concept."
+d1512 4
+a1515 1
+msgid "For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other words\" and <literal>e.g.</literal> for \"for example\", do not use the abbreviation. Spell out the entire phrase."
+d1523 4
+a1526 1
+msgid "Use adjectives with caution. If an adjective is necessary to differentiate between items, then use adjectives. In all cases, test whether the phrase can stand alone without the adjective."
+d1534 3
+a1536 1
+msgid "A term that represents a multi-word term. Typically, acronyms are formed in the following ways:"
+d1540 3
+a1542 1
+msgid "From the first letters of each word in a compound term, for example Table of Contents (TOC)."
+d1546 3
+a1548 1
+msgid "From recognizable parts of a compound term, such as GNU Object Model Environment (GNOME)."
+d1556 3
+a1558 1
+msgid "On the first occurrence of an acronym, spell out the full term, with the acronym in parentheses."
+d1562 3
+a1564 1
+msgid "Do not spell out the full compound for well-known acronyms, unless you think the information is useful for readers."
+d1568 3
+a1570 1
+msgid "Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than clarify a concept."
+d1574 3
+a1576 1
+msgid "Write the acronym in uppercase letters, unless there is a compelling case for lowercase."
+d1588 6
+a1593 1
+msgid "Use adverbs with caution. If an adverb is necessary to qualify the function of a component, then use an adverb. In all cases, test whether the phrase can stand alone without the adverb. Classic superfluous adverbs <literal>simply</literal>, <literal>easily</literal>, <literal>quickly</literal>."
+d1605 3
+a1607 1
+msgid "Do not apply a sense of location or dimension to a software application. A user can not be \"in\" a text editor."
+d1615 3
+a1617 1
+msgid "Do not use the definite article <literal>the</literal> to begin any of the following items:"
+d1629 1
+a1629 2
+#: en_US/style.xml:836(para)
+#: en_US/style.xml:1239(term)
+d1672 2
+a1673 1
+msgid "the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+d1690 3
+a1692 1
+msgid "the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</guimenu>"
+d1708 3
+a1710 1
+msgid "Do not use brackets [such as these] as a substitute for parentheses (such as these)."
+d1718 4
+a1721 1
+msgid "Do not use angle brackets to indicate variables in text, instead use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+d1759 3
+a1761 1
+msgid "Avoid starting a sentence with a command name or application name that has a lowercase initial letter."
+d1794 3
+a1796 1
+msgid "Use the same rules as for headings, for all captions accompanying figures and tables. Do not put a period at the end of a caption."
+d1888 1
+a1888 2
+#: en_US/style.xml:1143(term)
+#: en_US/emacs-nxml.xml:86(title)
+d1901 3
+a1903 1
+msgid "Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</emphasis>, or <emphasis>isn't</emphasis>."
+d1911 4
+a1914 1
+msgid "Do not use the em dash or the en dash. Use a paragraph break or a colon instead, where you want to create an introductory piece of text. If you have several items that you want to introduce, then you can use a variable list."
+d1942 3
+a1944 1
+msgid "Use numerals for fractions in tables and in units of measurement, but spell out fractions in prose."
+d1948 3
+a1950 1
+msgid "Use a space between a numeral and a related fraction, if there is a possible ambiguity. For example: 1 1/2 instead of 11/2."
+d1954 3
+a1956 1
+msgid "If a fraction is used in a compound modifier, insert a hyphen between the fraction and the unit of measurement."
+d1973 5
+a1977 1
+msgid "Use standard American English grammar rules, refer to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+d1993 3
+a1995 1
+msgid "All lowercase letters for conjunctions, articles, and prepositions of fewer than four letters"
+d2024 4
+a2027 1
+msgid "With some standard prefixes and suffixes. Use the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidance"
+d2035 3
+a2037 1
+msgid "In variable names of two or more words, such as <replaceable>directory-name</replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+d2062 4
+a2065 1
+msgid "With a word that is listed as unhyphenated in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+d2087 3
+a2089 1
+msgid "Do not use the term <emphasis>like</emphasis> to denote equivalence or similarity."
+d2111 2
+a2112 1
+msgid "Numbers from zero through nine unless the number is part of a measurement"
+d2120 3
+a2122 1
+msgid "Extreme values such as <emphasis>million</emphasis>, but precede the value with a numeral"
+d2130 3
+a2132 1
+msgid "A number that is immediately followed by a numeral, for example: <literal>two 10 MB files</literal>"
+d2185 3
+a2187 1
+msgid "To contain the abbreviation of a term on the first occurrence of the full term"
+d2221 6
+a2226 1
+msgid "Use standard American English punctuation rules. In addition to the specific points of punctuation in this section, refer also to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+d2235 3
+a2237 1
+msgid "Do not use a comma in numerals of four digits. Use a comma in numerals of more than four digits."
+d2246 5
+a2250 1
+msgid "Use quotation marks to indicate material that is taken verbatim from another source. Do not use quotation marks to excuse terms from legitimacy. If the term is not legitimate, then use another term. If you must use that term, declare the term in the glossary and make the term legitimate."
+d2259 9
+a2267 1
+msgid "When referring a user to another resource, use \"refer to\" instead of \"see\", and \"refer also to\" instead of \"see also\". This differentiates from the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag\">seealso</sgmltag> tags that are used in indexing. These tags create special links in the index. To be consistent throughout the document, we reserve the special words \"see\" and \"see also\" for hyperlinked index references, and use \"refer to\" and \"refer also to\" for non-hyperlinked and non-indexed references."
+d2283 4
+a2286 1
+msgid "Except where required as part of a filename, do not use slashes \"/\" in your writing. The construction <literal>and/or</literal>, for example, does not exist. Use one or the other term instead."
+d2295 4
+a2298 1
+msgid "Use standard American English spelling rules, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+d2319 3
+a2321 1
+msgid "Use standard abbreviations for units of measurements, do not invent your own abbreviations."
+d2325 3
+a2327 1
+msgid "For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of Electrical and Electronics Terms</citetitle>."
+d2335 3
+a2337 1
+msgid "Most standard abbreviations of units account for both singular and plural usage."
+d2354 5
+a2358 1
+msgid "This section contains usage tips based on situations the Fedora Documentation Project editors have encountered in the past. You should read and understand these examples to improve your own documentation. The Fedora Documentation Project editors welcome additional examples."
+d2367 9
+a2375 1
+msgid "Always use active voice, except when it is awkward to do so. The tutorial tells the user how to accomplish a task, and should give instructions clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. These words are redundant in a tutorial, since the reader assumes you are outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" \"might,\" and other words that indicate you are unsure about the subject matter. Your tutorial should cover a subject authoritatively. The reader should never be concerned about unknown effects of following the tutorial."
+d2405 6
+a2410 1
+msgid "Write in the present tense. A good rule of thumb is that the words \"will\" and \"shall\" are almost never needed in describing what the user should do or see. They add unnecessary length to sentences and can confuse translators. They are also often indicators of passive voice; refer also to <xref linkend=\"sn-misc-active-voice\"/>."
+d2439 7
+a2445 1
+msgid "Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself the writer (whether including the reader or not), the Fedora Documentation Project, the Fedora community, or any other group. Do not refer to users with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word \"one.\" It is acceptable to refer to the reader with the second person pronoun \"you.\""
+d2453 3
+a2455 1
+msgid "As described in the last section, I always run <command>up2date</command> before configuring the Samba server."
+d2459 3
+a2461 1
+msgid "If the user needs to back up his or her files, s/he should use the <command>tar</command> or <command>cpio</command> command."
+d2469 3
+a2471 1
+msgid "Refer to the section on <command>up2date</command> before configuring the Samba server."
+d2475 3
+a2477 1
+msgid "If necessary, users can back up files with the <command>tar</command> or <command>cpio</command> command."
+d2486 6
+a2491 1
+msgid "Avoid negative words when possible, since they give documentation an overly dogmatic tone. The word \"avoid\" is useful for this purpose. Note that contractions are often used for negative words such as <emphasis>don't</emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-contractions\"/>."
+d2499 7
+a2505 1
+msgid "Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the like. While occasional use of these constructions is acceptable, overuse reduces the authority of your documentation. The documentation should adequately cover a stock installation of Fedora. It is impossible for a tutorial-length document to cover every possible configuration scenario. Address the most common scenarios and note discrepancies only as required."
+d2513 7
+a2519 1
+msgid "Avoid covering redundant material, such as how to update a Fedora system. These overarching topics may be covered in other tutorials. Writers frequently violate this guideline because they feel their tutorial is not long enough. Keep your tutorial from wandering off-topic. Instead, refer the reader to a separate tutorial whenever possible for complete coverage of that topic."
+d2527 10
+a2536 1
+msgid "Avoid statements such as \"One of the most important things to do is <replaceable>XYZ</replaceable>.\" If the procedure is important, the reader already expects it to be in your tutorial. The converse is also true: If a procedure appears in your tutorial, the reader expects it is important. This is especially true if you use a whole section for the procedure in question. Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as required. If the whole section concerns how to do <replaceable>XYZ</replaceable>, leave this sentence out entirely. Refer also to <xref linkend=\"vle-golden-rule-4\"/>."
+d2545 3
+a2547 1
+msgid "Use precise words for actions users should take. Do not instruct users to \"go\" to a selection, or \"find\" a menu."
+d2556 3
+a2558 1
+msgid "Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</guimenuitem>"
+d2570 3
+a2572 1
+msgid "From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</guimenuitem>"
+d2584 4
+a2587 1
+msgid "If you are writing about a GUI-only application, you may use \"click\" freely. If you are writing about an application that has a text-mode interface, use \"select\" instead as shown above."
+d2595 3
+a2597 1
+msgid "This section contains tips on how to use DocBook tags more effectively in your documentation."
+d2600 1
+a2600 2
+#: en_US/style.xml:1881(title)
+#: en_US/writing-guidelines.xml:268(title)
+d2605 6
+a2610 1
+msgid "Avoid overuse of admonitions. Keep admonitions short and effective by using only the most important material inside the admonition. Move any background material required to explain the admonition statements outside the admonition. Use a short but descriptive title for an admonition. Use title case for the admonition title."
+d2623 7
+a2629 1
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+d2642 3
+a2644 1
+msgid "Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+d2648 6
+a2653 1
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. <placeholder-1/>"
+d2657 5
+a2661 1
+msgid "Avoid punctuation in titles for sections or admonitions, except for commas only where demanded. Use a title that says something about the admonition comment, such as \"Reboot Required,\" instead of simply using the admonition type for a title (\"Note\")."
+d2665 2
+a2666 1
+msgid "Follow the capitalization rules for headings in the title of an admonition."
+d2674 4
+a2677 1
+msgid "If your documentation formally states a specific value will be used as a convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag in your text or examples."
+d2686 7
+a2692 1
+msgid "Use the entities provided by the Fedora Documentation Project. These entities are found in the <filename>common/</filename> folder in the <filename>fedora-docs</filename> distribution. (Refer also to <xref linkend=\"ch-getting-files\"/>.) For instance, do not use abbreviations such as \"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" which produces the text \"Fedora 8.\""
+d2719 3
+a2721 1
+msgid "Please read this chapter carefully. This chapter describes the guidelines that must be followed such as naming conventions."
+d2725 4
+a2728 1
+msgid "This chapter only discusses tags used for documentation for the Fedora Project, not all available DocBook XML tags. For the complete list, refer to <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+d2742 4
+a2745 1
+msgid "In accordance with good XML practices, the first line in any DocBook XML source files should identify the file as XML. Use the following line as the first line of any new XML file:"
+d2754 3
+a2756 1
+msgid "All the files must contain the CVS Id header. Use the following line as the second line of any new XML file:"
+d2760 3
+a2762 1
+msgid "Any time the file is committed to CVS, the line is updated automatically to include information about the file. For example:"
+d2797 4
+a2800 1
+msgid "This section explains the ID naming convention. IDs are unique identifiers that allow DocBook XML to cross-reference a section, chapter, or other element."
+d2817 4
+a2820 1
+msgid "Start the ID with the special short two-character label. This makes URLs and other references to this ID human readable, by self-identifying the XML container type."
+d2824 3
+a2826 1
+msgid "<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used properly."
+d2919 3
+a2921 1
+msgid "Use the title of the item as the ID. Make your titles unique within a document to prevent conflicts. For example:"
+d2939 3
+a2941 1
+msgid "It is very important that you remember the caveats in this section. These are learned suggestions or rules that make your XML experience better."
+d2949 6
+a2954 1
+msgid "Do not use the trademark entities <sgmltag class=\"genentity\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class=\"genentity\">reg</sgmltag> because the do not produce HTML output that works for all charsets. The HTML output produces by these entities are declared in the DTD and cannot be changed via the stylesheet."
+d2958 3
+a2960 1
+msgid "Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes as follows:"
+d2989 4
+a2992 1
+msgid "In general, use <sgmltag>para</sgmltag> tags around anything other than a simple paragraph. Doing so will create additional white space within the text itself in the PDF version."
+d2996 4
+a2999 1
+msgid "Specifically, do not use <sgmltag>para</sgmltag> tags around the following (or, to put this another way, do not embed the following within <sgmltag class=\"element\">para</sgmltag> elements):"
+d3020 3
+a3022 1
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag>listitem</sgmltag> tags"
+d3026 5
+a3030 1
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</emphasis> start immediately after the beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra white space in the PDF version."
+d3038 5
+a3042 1
+msgid "The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) <emphasis>must</emphasis> be flush left in the XML file; otherwise, the extraneous whitespace will appear in the HTML version."
+d3086 10
+a3095 1
+msgid "There are five types of admonitions in DocBook: <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the admonitions have the same structure: an optional <sgmltag class=\"element\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD does not impose any specific semantics on the individual admonitions. For example, DocBook does not mandate that a <sgmltag class=\"element\">warning</sgmltag> is reserved for cases where bodily harm can result."
+d3099 5
+a3103 1
+msgid "Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element\">warning</sgmltag>"
+d3107 16
+a3122 1
+msgid "There are several ways to bring attention to text within a document. A <emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to bring additional information to the users' attention. A <emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful information or another way to do something. A <emphasis><sgmltag class=\"element\">caution</sgmltag></emphasis> is used to show the user they must be careful when attempting a certain step. An <emphasis><sgmltag class=\"element\">important</sgmltag></emphasis> tag set can be used to show the user a piece of information that should not be overlooked. While this information may not change anything the user is doing, it should show the user that this piece of information could be vital. A <emphasis><sgmltag class=\"element\">warning</sgmltag></emphasis> is used to show the reader that their current setup will change or be altered, such as files being removed, and they should not c
hoose this operation unless they are alright with the consequences."
+d3126 3
+a3128 1
+msgid "The following lines of code show the basic setup for each case mentioned above, along with its appearance in HTML."
+d3131 2
+a3132 4
+#: en_US/writing-guidelines.xml:403(title)
+#: en_US/emacs.xml:257(title)
+#: en_US/emacs.xml:562(title)
+#: en_US/emacs-nxml.xml:160(title)
+d3144 1
+a3144 2
+#: en_US/writing-guidelines.xml:413(title)
+#: en_US/emacs-nxml.xml:114(title)
+d3156 1
+a3156 2
+#: en_US/writing-guidelines.xml:433(title)
+#: en_US/emacs-nxml.xml:96(title)
+d3169 1
+a3169 2
+#: en_US/writing-guidelines.xml:459(see)
+#: en_US/writing-guidelines.xml:463(see)
+d3189 8
+a3196 1
+msgid "Screenshots are illustrations that show the state of a display the user may encounter. Screenshots can be either graphical or textual. However, screenshots use a great deal of space in a text document to convey relatively small amounts of information. The same space in the document can hold a greater amount of more descriptive and helpful information. Therefore, authors should avoid screenshots whenever possible in favor of descriptive text."
+d3200 8
+a3207 1
+msgid "One of the isolated instances in which screenshots are useful is to demonstrate a physical screen layout that is unfamiliar to a reader. <emphasis>This does not mean that illustrations of dialog boxes are good uses of screenshots.</emphasis> On the contrary, dialogs are simply instances of a user interface element with which a reader is already familiar. An annotated diagram in certain cases, however, explains to the reader where to find functional landmarks on the screen such as menu bars."
+d3211 3
+a3213 1
+msgid "The steps for taking a graphical screenshot illustrate how using text to describe a procedure is more concise than a series of screenshots."
+d3221 5
+a3225 1
+msgid "Create a new user account to make screenshots. The new account uses the distribution default theme, fonts, and element sizes. The resulting screenshot has an appearance familiar to the largest number of readers, and makes Fedora Documentation Project documents consistent."
+d3229 5
+a3233 1
+msgid "Before taking the screenshot, if possible, resize the targeted GUI element(s) to the smallest possible size. The target image should be 500 pixels wide or less. If the screenshot includes more than one GUI element, you may need to resize the screenshot in a following step."
+d3237 8
+a3244 1
+msgid "To take the screenshot, select the GUI element with the mouse to bring it to the forefront, or otherwise arrange the elements. Press <keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to capture a single GUI window. For capturing the entire desktop use <keycap>Print Screen</keycap>. If the shot includes multiple elements grouped closely together, crop the resulting PNG format image in <application>The GIMP</application>."
+d3248 9
+a3256 1
+msgid "If necessary, resize the image using <application>The GIMP</application>. Open the image, then right-click on it and choose <menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</guimenuitem></menuchoice>. With the chain symbol intact, set the <guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click <guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the image before converting it."
+d3260 7
+a3266 1
+msgid "With the image open in <application>The GIMP</application>, right-click the image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As...</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</guibutton>. Allow flattening of the image by clicking <guibutton>Export</guibutton>."
+d3270 4
+a3273 1
+msgid "A <guilabel>Save as PostScript</guilabel> window appears. Select <guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</guibutton>."
+d3282 3
+a3284 1
+msgid "Textual screen information is also useful for readers. Follow these guidelines for textual screenshots:"
+d3288 4
+a3291 1
+msgid "If a graphical screenshot illustrates a function, and the textual mode has identical functions, do not include both, unless omitting either would make your description unclear."
+d3295 4
+a3298 1
+msgid "Make the information generic over specific, and omit any username and machine information if possible. Do not include the shell prompt unless it is vital to the demonstration."
+d3306 5
+a3310 1
+msgid "When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show what the user types, and use <sgmltag class=\"element\">computeroutput</sgmltag> tags to show the resulting output."
+d3314 3
+a3316 1
+msgid "<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual screenshot usage."
+d3324 2
+a3325 1
+msgid "To find all the currently active ssh sessions, execute the following command:"
+d3352 6
+a3357 1
+msgid "The GNOME <application>Help</application> browser, also known as <command>yelp</command>, and the KDE <application>Khelp</application> documentation browser can render DocBook XML information as needed. Use these applications to preview your work if you prefer reading your work in a browser-like environment. Run the following command:"
+d3361 4
+a3364 1
+msgid "Make sure to point the preferred help browser at the top parent file of your XML document. Once the document loads, you can add a bookmark for it for ease of use later."
+d3373 3
+a3375 1
+msgid "Keeping your documents in the same place for every checkout session makes help browser bookmarks more effective."
+d3379 5
+a3383 1
+msgid "Once you have a bookmark stored, it will appear in the help browser at every use. You can now hit <keycap>F1</keycap> during any GUI session to launch the help browser. Then choose your bookmark from the menu to preview your document at any time."
+d3391 6
+a3396 1
+msgid "Documentation modules have a specific structure that enables the preconfigured tools to work correctly. Follow this structure exactly or you may have problems building your module. The Fedora Documentation Project build tools locate resources in the module and use them to build new output such as HTML or RPM packages."
+d3404 4
+a3407 1
+msgid "<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example module, excluding any <filename class=\"directory\">CVS</filename> folders. Note that this example document does not have branches."
+d3437 1
+a3437 2
+#: en_US/module-struct.xml:53(seg)
+#: en_US/module-struct.xml:94(seg)
+d3453 5
+a3457 1
+msgid "Think of an XML entity as a predefined snippet of information. It can represent a chunk of XML source, or simply a word or character. If the information changes, it need be replaced only once, in the definition, to fix all usage."
+d3461 6
+a3466 1
+msgid "This is the only directory absolutely required. It is named for the original language of the document, such as <placeholder-1/> (US English). The primary language does not have to be US English; all languages are supported. This directory contains all the XML source for the actual document, as well as XML source for document-specific <placeholder-2/><placeholder-3/>."
+d3474 1
+a3474 2
+#: en_US/module-struct.xml:70(seg)
+#: en_US/module-struct.xml:80(seg)
+d3478 1
+a3478 2
+#: en_US/module-struct.xml:71(filename)
+#: en_US/module-struct.xml:75(filename)
+d3483 5
+a3487 1
+msgid "The <placeholder-1/> directory is an optional directory where graphics for the document should be stored. If graphics are screenshots that are particular to a language, the <placeholder-2/> directory can and should be stored in a language directory."
+d3495 1
+a3495 2
+#: en_US/module-struct.xml:81(filename)
+#: en_US/module-struct.xml:87(filename)
+d3512 8
+a3519 1
+msgid "The <placeholder-1/> directory contains specially formatted Portable Object, or <placeholder-2/>, files created and used by translators. The Fedora Documentation Project build tools use these files to create translated versions of documents. The translated documents are not stored in CVS; they are created as needed from these PO files. The <placeholder-3/> directory also contains the <placeholder-4/> file, which lists the active translation <placeholder-5/>, or languages."
+d3522 1
+a3522 2
+#: en_US/module-struct.xml:93(seg)
+#: en_US/module-struct.xml:95(filename)
+d3527 3
+a3529 1
+msgid "The <placeholder-1/> controls the build process. Its content is discussed in <xref linkend=\"ex-makefile\"/>."
+d3532 1
+a3532 2
+#: en_US/module-struct.xml:100(filename)
+#: en_US/module-struct.xml:102(filename)
+d3547 5
+a3551 1
+msgid "Never add the <systemitem>docs-common</systemitem> build tools directory to an individual module. Special formatting in the module list downloads these tools when a user checks out a document module. For more information, refer to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+d3560 6
+a3565 1
+msgid "In Linux and Fedora documentation, references to commands often include a number inside parentheses. This number represents the section of <firstterm>manpages</firstterm> that includes documentation for that command. To read the manpage for <command>make(1)</command>, use the command <command>man 1 make</command>."
+d3569 6
+a3574 1
+msgid "The build system can render the document into another format such as <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</command><placeholder-1/> and shell scripts. Authors need <emphasis>no</emphasis> prior experience with either shell scripts or a <command>make(1)</command>."
+d3583 4
+a3586 1
+msgid "Each individual document has its own <filename>Makefile</filename>, which only needs to be a few lines long. The document <filename>Makefile</filename> content is designed for cut and paste operations."
+d3590 3
+a3592 1
+msgid "<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</filename> for a simple document with two files and two translations."
+d3601 4
+a3604 1
+msgid "Do not be concerned with some of the more complicated syntax such as the <command>XMLFILES_template</command> stanza. An explanation for this template appears a few paragraphs below."
+d3615 1
+a3615 2
+#: en_US/module-struct.xml:170(segtitle)
+#: en_US/module-struct.xml:240(segtitle)
+d3624 3
+a3626 1
+msgid "This variable contains the name for the main (parent) XML document. Follow convention by naming your document after the module name."
+d3634 3
+a3636 1
+msgid "This variable contains the ISO code for the original version of the document, such as <placeholder-1/>."
+d3644 5
+a3648 1
+msgid "This variable contains a listing of any files containing entity definitions. The Fedora Documentation Project uses a special XML format to record document-specific entities, so they can be translated and built on the fly like any other XML document. An example is shown later in this guide."
+d3665 7
+a3671 1
+msgid "This template allows the build tools to work with the document in multiple languages once it is translated. The <placeholder-1/> marking is a variable used to substitute the appropriate language. This template is not terribly complicated. For a new module, duplicate this section exactly except for the actual filenames. Prepend the text <placeholder-2/>, in place of the language code directory name, to each filename in your document."
+d3679 3
+a3681 1
+msgid "Do not include the document-specific entities XML file or the <filename>rpm-info.xml</filename> file, which will be discussed later in this guide."
+d3685 6
+a3690 1
+msgid "The final section, beginning with <literal>define</literal>, locates the main <filename>Makefile.common</filename> for the build system. This <filename>Makefile.common</filename> file contains all the <application>make(1)</application> targets and rules to actually build the document and the various archives."
+d3698 6
+a3703 1
+msgid "Each document module's primary language directory contains a file called <filename>rpm-info.xml</filename>. This file contains document-specific metadata used to generate revision history, copyright, and contributor information. It follows a DTD specification included with the rest of the build system tools."
+d3711 3
+a3713 1
+msgid "To render the <abbrev>XML</abbrev> document into another format, use one of the following <command>make</command> targets:"
+d3745 5
+a3749 1
+msgid "This target <placeholder-1/> the XML files to make sure they are not only well-formed, but follow the DTD. Some viewers of XML documents may not work correctly until you run this target. This target includes copying required entity files so that validating XML viewers work properly"
+d3757 2
+a3758 4
+#: en_US/module-struct.xml:257(abbrev)
+#: en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:293(abbrev)
+#: en_US/module-struct.xml:298(abbrev)
+d3778 5
+a3782 1
+msgid "This target builds the \"chunked\" <placeholder-1/> document for each defined translation. Output is placed in a separate directory named <placeholder-2/>. Each document section is a separate file within that directory."
+d3796 4
+a3799 1
+msgid "This target builds the \"non-chunked\" <placeholder-1/> document for each defined translation. Output is placed in a single file: <placeholder-2/>; no other files are created."
+d3806 2
+a3807 4
+#: en_US/module-struct.xml:277(abbrev)
+#: en_US/module-struct.xml:278(abbrev)
+#: en_US/module-struct.xml:294(abbrev)
+#: en_US/module-struct.xml:299(abbrev)
+d3812 4
+a3815 1
+msgid "This target builds only the <placeholder-1/> document for all document languages. <placeholder-2/> production is currently erratic and may not work for your document."
+d3827 3
+a3829 1
+msgid "This target builds only the <placeholder-1/> archive for all document languages."
+d3852 3
+a3854 1
+msgid "This target deletes any temporary, or generated files, but does <placeholder-1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+d3862 3
+a3864 1
+msgid "This target erases all <placeholder-1/>, <placeholder-2/>, and archive files. This target automatically invokes the <placeholder-3/> target as well."
+d3872 3
+a3874 1
+msgid "<abbrev>PDF</abbrev> production is currently erratic and may not work for your document."
+d3882 6
+a3887 1
+msgid "To add a new target and rules, place them at the bottom of the document <filename>Makefile</filename>, below the <literal>include</literal> line. Follow your target definitions with a double colon, not a single colon. The double colon allows you to specify additional rules for existing targets, or to write rules for a new target."
+d3891 3
+a3893 1
+msgid "For more information on using <command>make(1)</command>, consult the online documentation with the command <command>info make</command> in a terminal."
+d3902 5
+a3906 1
+msgid "Tutorial documents often make use of images such as <filename class=\"extension\">.PNG</filename> files. Store image files in a <filename class=\"directory\">figs/</filename> folder in the main module directory, as shown in <xref linkend=\"ex-module-structure\"/>."
+d3910 10
+a3919 1
+msgid "Depending on the output media, sometimes images may be scaled, streteched, or squashed. To minimize any distortions, we recommend that you use only <filename class=\"extension\">.PNG</filename> images. Avoid <filename class=\"extension\">.JPG</filename> files. The <command>convert(1)</command> program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</abbrev> package, provides a convenient way to reformat <filename class=\"extension\">.JPG</filename> images into <filename class=\"extension\">.PNG</filename> format. For more information on formatting images such as screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+d3923 4
+a3926 1
+msgid "Image files may be organized into subdirectories under <filename>figs/</filename> if necessary. The document building system recreates the image subdirectory structure in the output documents."
+d3930 7
+a3936 1
+msgid "Images often contain labels or other text which may need to be localized. A screenshot of a program, for example, may require a version for each translated language. Name language-dependent image files such as program screenshots by adding the language code to the filename, such as <filename>menu-en_US.png</filename>. Language-independent images, such as <filename>icon.png</filename>, do not need language codes."
+d3940 6
+a3945 1
+msgid "Sometimes, a document may require images that do not follow the naming convention. To use these images with the document building system, create an ordinary text file containing the image filenames. This file must be named <filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</systemitem> so the build system finds it when searching for image filenames."
+d3949 3
+a3951 1
+msgid "<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one way to create this <filename>Manifest</filename> file."
+d3964 2
+a3965 1
+msgid "To add a new DocBook XML file to an existing document, follow these steps:"
+d3973 6
+a3978 1
+msgid "Edit the <filename>Makefile</filename> and add the filename to the <varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to the last existing line, and on the next line add an entry for the new file. Remember to add the <literal>${1}/</literal> prefix as a substitute for the language directory name."
+d3986 5
+a3990 1
+msgid "Translations are stored as PO (portable object) files, which the toolchain transforms into translated documents. Each PO file is based on the POT (PO template) for the document and translated by the Fedora Translation Project. To add a translation, follow these steps:"
+d3994 3
+a3996 1
+msgid "If the <filename class=\"directory\">po/</filename> directory does not exist, create it and add it to CVS:"
+d4004 3
+a4006 1
+msgid "Add the new translation language to the <varname>OTHERS</varname> listing in the <filename>Makefile</filename>."
+d4010 3
+a4012 1
+msgid "Although translators often copy the POT manually to create the new PO file, the following command also works:"
+d4030 4
+a4033 1
+msgid "The goal of the Fedora Documentation Project is to create easy-to-follow, task-based documentation for Fedora users and developers. The Fedora Documentation Project uses the following tools:"
+d4054 4
+a4057 1
+msgid "This document explains the tools used by the Fedora Documentation Project. It provides writing and tagging guidelines to ensure Fedora documentation is consistent and easy-to-follow."
+d4065 3
+a4067 1
+msgid "To work on official Fedora documentation you need to install the required tools. Follow the directions below to configure your system."
+d4075 3
+a4077 1
+msgid "Install the \"Authoring and Publishing\" package group, which contains required DocBook XML files, stylesheets and scripts:"
+d4086 3
+a4088 1
+msgid "Next, install the <filename>cvs</filename> package, which is used to handle revision control on files in the official repository:"
+d4097 4
+a4100 1
+msgid "If you plan to use <application>Emacs</application> to edit DocBook XML documentation, install <package>psgml</package>, which adds helpful and time-saving functionality to maximize editing efficiency:"
+d4114 7
+a4120 1
+msgid "The Fedora Documentation Project's custom scripts and stylesheets are stored in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</systemitem> CVS server. When you check out a document module from CVS, the tools are included in the module inside the <filename class=\"directory\">docs-common/</filename> directory. To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+d4124 7
+a4130 1
+msgid "The most powerful component in the Fedora Documentation Project toolbox is <firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for authoring technical documentation using <firstterm>Extensible Markup Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark pieces of content with descriptive tags. The following output is an example of DocBook XML:"
+d4134 8
+a4141 1
+msgid "This example article, entitled <citetitle>A Very Short Article</citetitle>, consists of only a single paragraph. The tags, or markup, surround elements of content to define the sense in which they are used. A paragraph, for example, is marked with <sgmltag>para</sgmltag> tags. Text that requires emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does not worry about the visual formatting such as italics or font size. Fedora Documentation Project build tools automatically perform all formatting tasks."
+d4145 7
+a4151 1
+msgid "The custom tools built by the Fedora Documentation Project render DocBook source into a variety of formats for publication and distribution. They also allow translators to create localized versions of the XML documents for Fedora users around the world. The flexibility of XML allows for a single document to be used many times for many purposes, like reusable code for a programmer."
+d4155 6
+a4160 1
+msgid "DocBook is itself very well documented. For more information about DocBook, visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also features complete copies of <citetitle>DocBook: The Definitive Guide</citetitle> to browse and download, the canonical source for DocBook information."
+d4169 5
+a4173 1
+msgid "DocBook XML, like a computer program, has version numbers. The version used by Fedora Documentation Project right now is 4.4. The DocBook web site may document a slightly newer version, but the majority of the schema still applies."
+d4177 4
+a4180 1
+msgid "Contributors who use the Microsoft Windows operating system can still make use of DocBook tools. For more information, refer to <ulink url=\"http://www.codeproject.com/winhelp/docbook_howto.asp\"/>."
+d4188 6
+a4193 1
+msgid "The Fedora Documentation Project provides the tools, scripts, and stylesheets to transform your <abbrev>XML</abbrev> documents into other output formats such as <abbrev>HTML</abbrev>. In addition, these tools can build your document into a <abbrev>RPM</abbrev> package. To take advantage of these services, follow the conventions in this section to name your files."
+d4197 7
+a4203 1
+msgid "On the CVS server, directories that contain document files are called <firstterm>modules</firstterm>. Each module represents a single document. Each document may consist of several <firstterm>branches</firstterm> if that document changes with each release of Fedora. Contributors can check out single branches of these modules or the entire module. Each document or branch may contain multiple XML source files."
+d4207 2
+a4208 1
+msgid "Use the <command>cvs co -c</command> command to view existing module names."
+d4221 5
+a4225 1
+msgid "The leftmost entry in each line is the name of a module you can check out from CVS. The rest of the line ensures that checkouts include the proper branch of a document and the common build tools. For more information on CVS, refer to <xref linkend=\"ch-cvs\"/>."
+d4229 6
+a4234 1
+msgid "Note in the listing above that the <systemitem>about-fedora</systemitem> module has two branches available. One branch is for Fedora 7 and one is for forward development to match the current work of developers. On the other hand, the <systemitem>documentation-guide</systemitem> module is not branched."
+d4242 4
+a4245 1
+msgid "Modules ending with the suffix <filename>-dir</filename> are not usually helpful to checkout directly. These modules do not include the common build tools and thus do not provide many of the functions contributors require."
+d4254 6
+a4259 1
+msgid "Choose a module name that accurately reflects your document's subject, but avoid any name already taken. The document title without any use of the word <wordasword>fedora</wordasword> is a reasonable choice in most cases. Use the length descriptors <wordasword>tutorial</wordasword> or <wordasword>guide</wordasword> in the module name where appropriate."
+d4267 3
+a4269 1
+msgid "Do not use the word <wordasword>fedora</wordasword> to name modules in the Fedora Documentation Project CVS repository."
+d4327 3
+a4329 1
+msgid "Follow these guidelines for naming files to make collaboration and document reuse easy:"
+d4333 3
+a4335 1
+msgid "As with module names, avoid using the word <wordasword>fedora</wordasword> in file names since it is redundant."
+d4339 3
+a4341 1
+msgid "If the document is comprised of many XML files, avoid repeating the name of the document when naming the constituent files."
+d4345 3
+a4347 1
+msgid "Avoid numbering files to show order, since editors and authors often rearrange documents or reuse their files in other documents."
+d4358 5
+a4362 10
+#: en_US/emacs.xml:20(primary)
+#: en_US/emacs.xml:24(primary)
+#: en_US/emacs.xml:43(primary)
+#: en_US/emacs.xml:224(primary)
+#: en_US/emacs.xml:233(primary)
+#: en_US/emacs.xml:238(primary)
+#: en_US/emacs.xml:243(primary)
+#: en_US/emacs.xml:523(application)
+#: en_US/emacs-nxml.xml:18(primary)
+#: en_US/emacs-nxml.xml:22(primary)
+d4372 4
+a4375 1
+msgid "You can use the PSGML mode available for Emacs to make it easier to write in XML format. PSGML mode provides syntax-highlighting, tag completion, and more."
+d4400 5
+a4404 1
+msgid "For Emacs to parse your DocBook documents correctly, you must have a <filename>.emacs</filename> file. Cut and paste the following into your existing <filename>.emacs</filename> file or create a new one that contains the following lines:"
+d4408 4
+a4411 1
+msgid "If you have a wheel mouse and are using Emacs version 21, you can add the following to your <filename>.emacs</filename> file so your wheel will work in <application>Emacs</application>:"
+d4415 3
+a4417 1
+msgid "If you are using the older version 20 of <application>Emacs</application>, add the following instead:"
+d4447 4
+a4450 1
+msgid "The colors, font, and geometry (default size of window) for Emacs in your <filename>~/.Xresources</filename> file. The format for the settings is <userinput>emacs.keyword:value</userinput>."
+d4458 3
+a4460 1
+msgid "If you have other settings in your <filename>~/.Xresources</filename>, add the following to the end of the file."
+d4498 12
+a4509 24
+#: en_US/emacs.xml:408(keycap)
+#: en_US/emacs.xml:412(keycap)
+#: en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:443(keycap)
+#: en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:458(keycap)
+#: en_US/emacs.xml:463(keycap)
+#: en_US/emacs.xml:468(keycap)
+#: en_US/emacs.xml:473(keycap)
+#: en_US/emacs.xml:478(keycap)
+#: en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:508(keycap)
+#: en_US/emacs.xml:509(keycap)
+#: en_US/emacs.xml:514(keycap)
+#: en_US/emacs.xml:515(keycap)
+#: en_US/emacs.xml:520(keycap)
+#: en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:533(keycap)
+#: en_US/emacs.xml:540(keycap)
+#: en_US/emacs.xml:542(keycap)
+d4513 4
+a4516 8
+#: en_US/emacs.xml:409(keycap)
+#: en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:540(keycap)
+#: en_US/emacs.xml:542(keycap)
+d4524 5
+a4528 7
+#: en_US/emacs.xml:407(seg)
+#: en_US/emacs.xml:508(seg)
+#: en_US/emacs.xml:514(seg)
+#: en_US/emacs.xml:520(seg)
+#: en_US/emacs.xml:532(seg)
+#: en_US/emacs.xml:540(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+d4535 1
+a4535 2
+#: en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:437(keycap)
+d4540 1
+a4540 2
+#: en_US/emacs.xml:432(keycap)
+#: en_US/emacs.xml:438(keycap)
+d4544 1
+a4544 2
+#: en_US/emacs.xml:432(keycap)
+#: en_US/emacs.xml:439(keycap)
+d4550 3
+a4552 1
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+d4560 4
+a4563 1
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of tag, <placeholder-5/>"
+d4592 1
+a4592 2
+#: en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:533(keycap)
+d4643 1
+a4643 2
+#: en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:515(keycap)
+d4659 2
+a4660 4
+#: en_US/emacs.xml:493(keycap)
+#: en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:527(keycap)
+d4668 1
+a4668 2
+#: en_US/emacs.xml:495(seg)
+#: en_US/emacs.xml:500(seg)
+d4673 2
+a4674 4
+#: en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:508(keycap)
+#: en_US/emacs.xml:514(keycap)
+d4680 1
+a4680 2
+#: en_US/emacs.xml:499(keycap)
+#: en_US/emacs.xml:504(keycap)
+d4686 3
+a4688 1
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, <placeholder-3/>"
+d4692 3
+a4694 1
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, <placeholder-3/>"
+d4727 3
+a4729 1
+msgstr "Perenggan Berikut Perenggan Berikut Perenggan Berikut Perenggan Berikut Perenggan Berikut Perenggan Berikut Perenggan Berikut Perenggan Berikut "
+d4742 3
+a4744 1
+msgid "Edit attributes for a tag (for example, you can edit the <placeholder-1/> attribute of the <placeholder-2/> tag)"
+d4752 1
+a4752 2
+#: en_US/emacs.xml:550(title)
+#: en_US/emacs-nxml.xml:77(title)
+d4757 3
+a4759 1
+msgid "The table or reference card of Emacs and PSGML commands can be confusing for beginners. This section provides some examples of how to use them."
+d4771 5
+a4775 1
+msgid "To avoid having to type a tag repeatedly, use the key combination <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. At the bottom of the <application>Emacs</application> window, the following prompt appears:"
+d4783 6
+a4788 1
+msgid "To view a list of available tags, use either the <keycap>Tab</keycap> or <keycap>?</keycap>. If you know the first few letters of a tag, enter them, followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, that tag appears. If more than one completion exists, a complete list of possible tags appears."
+d4792 4
+a4795 1
+msgid "If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, <keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the example below:"
+d4803 5
+a4807 1
+msgid "After you open a tag, you must close it. The easiest way to close an open tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most recently opened tag."
+d4819 5
+a4823 1
+msgid "Sometimes in <application>Emacs</application>, the window becomes split, with tags completions or other text in an alternate window. To return to a single window, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+d4832 4
+a4835 1
+msgid "To save your work, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>."
+d4844 5
+a4848 1
+msgid "If the tag completion process becomes unwieldy or confusing, use the keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to exit back to the text. <application>Emacs</application> clears any prompts and returns to the buffer text."
+d4857 6
+a4862 1
+msgid "To open a new file, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the <application>Emacs</application> window. Enter the file name, using <keycap>Tab</keycap> completion if desired, of the file you wish to open."
+d4870 6
+a4875 1
+msgid "To close <application>Emacs</application> use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have not saved your work, <application>Emacs</application> prompts you to save any changed files."
+d4878 1
+a4878 2
+#: en_US/emacs.xml:687(title)
+#: en_US/emacs-nxml.xml:127(title)
+d4883 3
+a4885 1
+msgid "Additional Emacs and PSGML references are available at the following locations:"
+d4888 1
+a4888 2
+#: en_US/emacs.xml:697(citetitle)
+#: en_US/emacs-nxml.xml:143(citetitle)
+d4893 4
+a4896 1
+msgid "Emacs reference card that comes with the <filename>emacs</filename> package. You can print it out as a reference. —<filename>/usr/share/emacs/<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+d4900 3
+a4902 1
+msgid "Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+d4906 4
+a4909 1
+msgid "<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of Emacs commands for PSGML mode."
+d4920 1
+a4920 2
+#: en_US/emacs-nxml.xml:14(primary)
+#: en_US/emacs-nxml.xml:51(primary)
+d4930 6
+a4935 1
+msgid "You can also use the nXML mode available for <application>Emacs</application> to make it even easier to write in DocBook XML format. nXML mode provides context-sensitive editing using completion, real time validity error checking, syntax highlighting and indentation. All you need to do is install an RPM!!"
+d4943 6
+a4948 1
+msgid "Please be aware the nxml-mode for <application>Emacs</application> is quite new, so there are a few things that the advanced user might notice when using it with other documents types. If you keep an eye on the mailing-list, you can keep up to date with these, as well as ask questions. For more details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+d4964 7
+a4970 1
+msgid "To use nXML mode with emacs, you will need to install the nXML RPM available from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www.thaiopensource.com/download/\">http://www.thaiopensource.com/download/</ulink>. The source requires a lot more work to setup, therefore we will only be concentrating on the RPM version."
+d4974 3
+a4976 1
+msgid "Information on where to get the source is available in <xref linkend=\"sn-emacs-additional-resources\"/>."
+d4980 4
+a4983 1
+msgid "Compared to PSGML mode there are only couple of commands that you need. This speeds up writing with <application>Emacs</application> considerably, which means you can concentrate more on the content of your article."
+d4987 5
+a4991 1
+msgid "To create a tag, type <userinput><</userinput> and then type the keyword. To complete the keyword, press <command>Ctrl-Ret</command>, then add the last <userinput>></userinput>. To close a tag, type <userinput></</userinput>."
+d4995 4
+a4998 1
+msgid "When you open a document that doesn't have a DOCTYPE declaration at the top of the file, you will get this message and tag completion won't work because nXML will not know what format you are writing."
+d5002 6
+a5007 1
+msgid "To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> and load <filename>docbook.rnc</filename>. <application>Emacs</application> will then prompt you to save it in the current working directory."
+d5011 5
+a5015 1
+msgid "The commands already discussed are the only differences between using <application>Emacs</application> with PSGML mode and <application>Emacs</application> with nXML mode. You will still need to use all the same commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+d5019 3
+a5021 1
+msgid "Additional Emacs and nXML references are available at the following locations:"
+d5038 4
+a5041 1
+msgid "Emacs reference card that comes with the <filename>emacs</filename> package. You can print it out as a reference. —<filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+d5050 4
+a5053 1
+msgid "This file can be found in the directory you extracted the source into, or in <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename> if you installed the RPM."
+d5061 4
+a5064 1
+msgid "This is a new major mode for GNU Emacs for editing XML documents. It supports editing well-formed XML documents and also provides schema-sensitive editing of XML documents using RELAX NG Compact Syntax."
+d5068 4
+a5071 1
+msgid "To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs version 20 will not work properly, nor will XEmacs. To get started, do the following:"
+d5079 3
+a5081 1
+msgid "This defines the necessary autoloads. Now, visit a file containing an XML document, and do the following:"
+d5097 3
+a5099 1
+msgid "For information on how to use nxml-mode. The beginnings of a manual are in nxml-mode.info. You can read this using:"
+d5107 3
+a5109 1
+msgid "It's also installed as an entry at the end of the top-level info directory. So you can read it with <command>C-h i</command> as usual."
+d5113 3
+a5115 1
+msgid "You can use <filename>test.valid.xml</filename> and <filename>test.invalid.xml</filename> as examples of valid and invalid XML documents."
+d5130 7
+a5136 1
+msgid "to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-200YMMDD</computeroutput> is the directory containing the <filename>.elc</filename> files. Note that <filename>rng-auto.el</filename> does not load all of the nxml-mode code; it merely sets things up so that all the features of nxml-mode will be autoloaded properly. You should not try to autoload <filename>rng-auto.el</filename> itself."
+d5140 5
+a5144 1
+msgid "To use nxml-mode automatically for files with an extension of <filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> or <filename>xhtml</filename>, add the following to your <filename>.emacs</filename> file:"
+d5156 5
+a5160 1
+msgid "If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are running Emacs 21.3 or later, then I recommend enabling unify-8859-on-decoding-mode, by adding the following to your <filename>.emacs</filename> file:"
+d5169 4
+a5172 1
+msgid "To get validation and schema-sensitive editing, you need a RELAX NG Compact Syntax (RNC) schema for you document. The schema directory includes some schemas for popular document types."
+d5176 3
+a5178 1
+msgid "For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://relaxng.org/</ulink>."
+d5182 4
+a5185 1
+msgid "For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial.html</ulink>"
+d5189 4
+a5192 1
+msgid "For automatically creating RNC schemas, I recommend my Trang program: <ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee.thaiopensource.com/relaxng/trang.html\"</ulink>"
+d5212 4
+a5215 1
+msgid "To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html\">http://www.pantor.com/download.html\"</ulink>."
+d5219 5
+a5223 1
+msgid "To convert a W3C XML Schema to an RNC schema, you need first to convert it to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+d5231 4
+a5234 1
+msgid "Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug reports, discussion. I will announce all new versions there."
+d5250 4
+a5253 1
+msgid "This document is based on a document started by Tammy Fox (tfox at redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray Fuller (jrfuller at redhat.com)."
+d5257 3
+a5259 1
+msgid "A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to fix a few typos and explain that anonymous CVS access does not allow commits."
+d5263 4
+a5266 1
+msgid "Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to add the trailing slashes to the <command>figure</command> tag example in <filename>docs-xml-tags.xml</filename>."
+d5270 3
+a5272 1
+msgid "A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been applied to add <xref linkend=\"ch-vim\"/>."
+d5276 4
+a5279 1
+msgid "A patch from Karsten Wade (kwade at redhat.com) has been applied to add <xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields (stickster at gmail.com)."
+d5289 3
+a5291 1
+msgid "A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been applied to more fully explaing the document building system."
+a5297 1
+
+@
+
diff --git a/old-documentation-guide/po/pt.po,v b/old-documentation-guide/po/pt.po,v
new file mode 100644
index 0000000..3ae5b1f
--- /dev/null
+++ b/old-documentation-guide/po/pt.po,v
@@ -0,0 +1,35838 @@
+head 1.25;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.22
+ LIVE:1.12;
+locks; strict;
+comment @# @;
+
+
+1.25
+date 2009.04.09.14.26.59; author transif; state Exp;
+branches;
+next 1.24;
+
+1.24
+date 2008.05.12.06.13.11; author mdious; state Exp;
+branches;
+next 1.23;
+
+1.23
+date 2007.12.15.21.52.11; author pfrields; state Exp;
+branches;
+next 1.22;
+
+1.22
+date 2007.11.15.02.12.48; author pfrields; state Exp;
+branches;
+next 1.21;
+
+1.21
+date 2007.10.27.17.34.37; author zepires; state Exp;
+branches;
+next 1.20;
+
+1.20
+date 2007.10.22.09.47.17; author zepires; state Exp;
+branches;
+next 1.19;
+
+1.19
+date 2007.10.21.16.03.34; author zepires; state Exp;
+branches;
+next 1.18;
+
+1.18
+date 2007.08.03.16.42.44; author pfrields; state Exp;
+branches;
+next 1.17;
+
+1.17
+date 2007.08.03.16.39.22; author pfrields; state Exp;
+branches;
+next 1.16;
+
+1.16
+date 2007.07.29.23.25.11; author pfrields; state Exp;
+branches;
+next 1.15;
+
+1.15
+date 2007.07.21.15.19.59; author zepires; state Exp;
+branches;
+next 1.14;
+
+1.14
+date 2007.07.21.15.11.14; author zepires; state Exp;
+branches;
+next 1.13;
+
+1.13
+date 2007.07.19.23.55.10; author zepires; state Exp;
+branches;
+next 1.12;
+
+1.12
+date 2007.06.10.20.46.37; author zepires; state Exp;
+branches;
+next 1.11;
+
+1.11
+date 2007.05.05.18.02.50; author zepires; state Exp;
+branches;
+next 1.10;
+
+1.10
+date 2007.05.05.14.21.44; author pfrields; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2007.05.02.09.23.12; author zepires; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2007.05.02.08.47.21; author zepires; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2007.04.25.11.30.05; author zepires; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.04.24.10.36.55; author zepires; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.04.24.01.53.28; author zepires; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.04.23.10.39.29; author zepires; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.04.23.03.02.41; author zepires; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.04.18.14.53.04; author zepires; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.04.18.10.20.06; author zepires; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.25
+log
+ at Sending translation for Portuguese
+@
+text
+ at msgid ""
+msgstr ""
+"Project-Id-Version: docs-documentation-guide\n"
+"POT-Creation-Date: 2008-05-13 02:06+1000\n"
+"PO-Revision-Date: 2009-04-08 01:28+0100\n"
+"Last-Translator: Marco Mendonça <marcormm@@gmail.com>\n"
+"Language-Team: pt <fedora-trans-pt@@redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-POFile-SpellExtra: pt Frields make Fox Emacs Tammy OPL Hat po Red Inc\n"
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu guiicon disk glossentry row Bold VHDCI tarball init Fontifying\n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ\n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend autoindent Heritage wordasword glosslist pts section decoding\n"
+"X-POFile-SpellExtra: install tags Documentation let address convert articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr\n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap dev can of simplelist Wade example prompt share agent\n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML tgroup Terms refcard tbody XEmacs VariableList textobject xhtml\n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man sy entry YMMDD documentation sw Parsed né sn ethernet QLA\n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot developer guimenu img lt ls ndash ced\n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro keycap Parse merge mode APC en End suretecsystems License year\n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC configuracao org beginning generate messages yum\n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG Dictionary Screen mkdir system SWAK XMLFILES\n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER\n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote eps Window Main option RPS xref POT ENTITIES emphasis build\n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest Enter device The Tommy OrderedList class paiu enfâse don url\n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text jrfuller syntax sfdisk ksconfig title\n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd colname accel ulink replaceable Quick guimenuitem ENTITY\n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES set DOCBASE guilabel frame FDL sgml see infrastructure\n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray ambiguidadde PO ecesso nohlsearch Sans screen citetitle\n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG PDFs login Strunk Contents load ch simplemente cd Online table\n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap\n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse cluster vs NEWS id if author XPTO member parts Karsten XXI\n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo imageobject Gavin indexterms variablelist setq onyline\n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject Qlogic EPS yes kwade elc Xclients shortcut desktop source\n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl\n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef authorgroup Guilford listitem sshd vimtutor host direcamente\n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done Jargon or varlistentry into Writing Environment nxml your\n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered nochunks Variablelist OTHERS Paradigm true info default up\n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif\n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas Redundâncias update yahoo VIMRUNTIME generated important\n"
+"X-POFile-SpellExtra: Authoring lang SYSTEM URLS apositivos Elements\n"
+"X-POFile-IgnoreConsistency: Clear\n"
+"X-POFile-IgnoreConsistency: f\n"
+"X-POFile-IgnoreConsistency: End\n"
+"X-POFile-IgnoreConsistency: warning\n"
+"X-POFile-IgnoreConsistency: all\n"
+"X-POFile-IgnoreConsistency: y\n"
+"X-POFile-SpellExtra: pfrields parent user about Portable Language pup\n"
+"X-POFile-SpellExtra: Markup stickster Yum Extensible gmail Pup Guide dir\n"
+"X-POFile-SpellExtra: Definitive www ci enUS images chkconfig httpd service\n"
+"X-POFile-SpellExtra: py LIVE start stylesheet Khelp var includepath\n"
+"X-POFile-SpellExtra: docbookhtml Server cvsweb add php yelp LINGUAS zzXX\n"
+"X-POFile-SpellExtra: chown hosts\n"
+"X-Poedit-Language: Portuguese\n"
+"X-Poedit-Country: PORTUGAL\n"
+
+#: en_US/rpm-info.xml:22(rights)
+msgid "OPL"
+msgstr "OPL"
+
+#: en_US/rpm-info.xml:23(version)
+msgid "1.0"
+msgstr "1.0"
+
+#: en_US/rpm-info.xml:26(year)
+msgid "2003"
+msgstr "2003"
+
+#: en_US/rpm-info.xml:27(year)
+msgid "2004"
+msgstr "2004"
+
+#: en_US/rpm-info.xml:28(year)
+msgid "2005"
+msgstr "2005"
+
+#: en_US/rpm-info.xml:29(year)
+msgid "2006"
+msgstr "2006"
+
+#: en_US/rpm-info.xml:30(year)
+msgid "2007"
+msgstr "2007"
+
+#: en_US/rpm-info.xml:31(year)
+msgid "2008"
+msgstr "2008"
+
+#: en_US/rpm-info.xml:32(holder)
+msgid "Red Hat, Inc. and others"
+msgstr "Red Hat, Inc. e outros"
+
+#: en_US/rpm-info.xml:34(title)
+msgid "Fedora Documentation Guide"
+msgstr "Guia de Documentação do Fedora"
+
+#: en_US/rpm-info.xml:35(desc)
+msgid "Guidelines and procedures for producing documentation for Fedora"
+msgstr "As orientações e procedimentos para produzir a documentação do Fedora"
+
+#: en_US/rpm-info.xml:39(details)
+msgid "Add L10n chapter (#441190)"
+msgstr "Adicionar capítulo L10n (#441190)"
+
+#: en_US/rpm-info.xml:43(details)
+msgid "Fix some organization and missing targets (#371531)"
+msgstr "Corrigida alguma organização e prazos não cumpridos (#371531)"
+
+#: en_US/rpm-info.xml:47(details)
+msgid "Add link to DocBook XML help for Windows"
+msgstr "Adicionar atalho a DocBook XML ajuda para windows"
+
+#: en_US/rpm-info.xml:51(details)
+msgid "Add guidance on CVS web access and previewing work"
+msgstr "Adição de indicações sobre o acesso Web ao CVS e à antevisão do trabalho"
+
+#: en_US/rpm-info.xml:55(details)
+msgid "Add new chapter on publishing"
+msgstr "Adição de um novo capítulo sobre a publicação"
+
+#: en_US/rpm-info.xml:59(details)
+msgid "Include information on LINGUAS usage"
+msgstr "Incluir a informação sobre a utilização do LINGUAS"
+
+#: en_US/rpm-info.xml:63(details)
+msgid "Remove unnecessary chapter on XML tags"
+msgstr "Remover um capítulo desnecessário sobre as etiquetas de XML"
+
+#: en_US/rpm-info.xml:67(details)
+msgid "Assorted fixes to reflect newer version of reality"
+msgstr "Correcções associadas para reflectir uma versão mais recente da realidade"
+
+#: en_US/rpm-info.xml:74(details)
+msgid "Update to new content and build requirements"
+msgstr "Actualização para o novo conteúdo e requisitos de compilação"
+
+#: en_US/l10n.xml:13(title)
+msgid "Localization (L10n)"
+msgstr "Localização (L10n)"
+
+#: en_US/l10n.xml:14(para)
+msgid "This chapter discusses how translations are provided in Fedora documentation."
+msgstr "Este capítulo trata do modo como as traduções são fornecidas na documentação do Fedora."
+
+#: en_US/l10n.xml:19(title)
+msgid "PO Files"
+msgstr "Ficheiros PO"
+
+#: en_US/l10n.xml:20(para)
+msgid "The cornerstone of translation when using XML files such as DocBook is the <firstterm>Portable Object</firstterm> or <acronym>PO</acronym> file. PO files provide a way for independent individuals or teams to translate documents. The Fedora Documentation Project toolchain includes rules for creating, updating, and maintaining these PO files."
+msgstr "A pedra angular para a tradução quando se utiliza ficheiros XML tais como o DocBook é o <firstterm>Portable Object</firstterm> ou ficheiros <acronym>PO</acronym>. Os ficheiros PO permitem a tradução individual ou por equipas, de documentos. O conjunto de ferramentas do Projecto de Documentação do Fedora inclui as regras para a criação, actualização e manutenção destes ficheiros PO. "
+
+#: en_US/l10n.xml:28(para)
+msgid "PO files are usually found in two forms:"
+msgstr "Os ficheiros PO encontram-se, normalmente, sob duas formas:"
+
+#: en_US/l10n.xml:33(para)
+msgid "the <filename class=\"extension\">.pot</filename> file, or <firstterm>PO Template</firstterm> (<acronym>POT</acronym>)"
+msgstr "o <filename class=\"extension\">.pot</filename> ficheiro, ou <firstterm>Padrão PO</firstterm> (<acronym>POT</acronym>)"
+
+#: en_US/l10n.xml:41(para)
+msgid "the <filename class=\"extension\">.po</filename> file, or translation file (<acronym>PO</acronym>)"
+msgstr "O ficheiro <filename class=\"extension\">.po</filename>, ou ficheiro de tradução (<acronym>PO</acronym>)"
+
+#: en_US/l10n.xml:47(para)
+msgid "A POT is, as the name suggests, a blank template for new translations. It contains some header information and a list of strings based on the content of the original XML file from which it was created. Translators do not alter the POT. The POT should only be changed after changes are made to the original XML file from which it is derived."
+msgstr "Um ficheiro POT é, como o nome sugere, um template em branco para novas traduções. Contém alguma informação no cabeçalho e uma lista de strings relacionadas com o conteúdo do ficheiro XML original a partir do qual foi criado. Os tradutores não alteram o POT. O POT só deve ser alterado depois de terem sido feitas as alterações ao ficheiro XML original a partir do qual este teve origem."
+
+#: en_US/l10n.xml:55(para)
+msgid "A translator who wishes to start working on a new language copies the POT to a locale-specific PO file. Then the translator uses any of a number of command-line or graphical tools to translate each of the strings in the list. A single POT is used to create many POs, one for each locale. These files are normally named for their locale code, such as <filename>de.po</filename>, <filename>it.po</filename>, and so on."
+msgstr "Um tradutor que pretenda começar a trabalhar numa nova língua, copia o ficheiro POT para um ficheiro PO específico para a sua língua. Posteriormente, o tradutor utiliza um conjunto de comandos ou ferramentas gráficas para traduzir cada uma das strings na lista. Um único ficheiro POT pode ser usado para criar muitos ficheiros PO, um por cada localização. A estes ficheiros atribui-se normalmente um nome em função do código da sua localização, tais como <filename>de.po</filename>, <filename>it.po</filename>, e assim por diante."
+
+#: en_US/l10n.xml:67(title)
+msgid "Creating or Updating a POT"
+msgstr "A criar ou a actualizar um POT"
+
+#: en_US/l10n.xml:68(para)
+msgid "The POT is named after the document from which it is derived. If document named in the <filename>Makefile</filename>) is <filename>foo-tutorial.xml</filename>, the POT is named <filename>foo-tutorial.pot</filename>."
+msgstr "É atribuído um nome ao ficheiro POT em função do documento a partir do qual este teve origem. Se o documento cujo nome no <filename>Makefile</filename>) é <filename>foo-tutorial.xml</filename>, o ficheiro POT é designado por <filename>foo-tutorial.pot</filename>. "
+
+#: en_US/l10n.xml:74(para)
+msgid "To create a new POT, use the following command:"
+msgstr "Para criar um novo POT, utilize o seguinte comando:"
+
+#: en_US/l10n.xml:78(para)
+msgid "The same command is used to update the POT when the original XML sources change."
+msgstr "O mesmo comando é utilizado para actualizar o POT quando mudam códigos originais do XML."
+
+#: en_US/l10n.xml:83(title)
+msgid "Keep POT Fresh"
+msgstr "Manter POT actualizado."
+
+#: en_US/l10n.xml:84(para)
+msgid "Update the POT whenever the original XML changes. Many translators' tools automatically notify them of the change so they can update translations quickly."
+msgstr "Actualizar o POT sempre que o XML original for alterado. Muitas das ferramentas dos tradutores fazem a notificação automática desta alteração permitindo que se efectuem rapidamente as actualizações nas traduções."
+
+#: en_US/l10n.xml:92(title)
+msgid "Updating PO Files"
+msgstr "A actualizar os ficheiros PO"
+
+#: en_US/l10n.xml:93(para)
+msgid "The translation files are created by the individual translators, and document maintainers do not normally need to create them. Translators update a list of locales in the <filename>po/LINGUAS</filename> file which defines all the locales for which translations exist."
+msgstr "Os fiheiros de tradução são criados por cada tradutor, individualmente, e os gestores de documentos normalmente não precisam de os criar. Os tradutores actualizam uma lista de locais no ficheiro <filename>po/LINGUAS</filename> o qual define todos os locais para os quais existe tradução. "
+
+#: en_US/l10n.xml:100(para)
+msgid "Whenever the source XML files are updated, the maintainer must at least update the POT. It is helpful, however, to also merge these changes with the existing translations for those translators who are not automatically notified of changes."
+msgstr "Sempre que os ficheiros fonte XML são actualizados, o gestor deve, pelo menos, actualizar o POT. Ajuda, contudo, também adicionar estas alterações às traduções existentes para aqueles tradutores que não são automaticamente notificados das alterações."
+
+#: en_US/l10n.xml:107(title)
+msgid "Staying Current"
+msgstr "A manter-se actualizado"
+
+#: en_US/l10n.xml:108(para)
+msgid "Always make sure your local copy of PO is fresh, using the CVS \"update\" command:"
+msgstr "Assegure-se sempre que a sua cópia do ficheiro PO é recente, utilizando o comando CVS \"update\""
+
+#: en_US/l10n.xml:114(para)
+msgid "To merge new changes into the existing PO translations, use the following command:"
+msgstr "Para juntar novas alterações às traduções existentes do PO, utilize o seguinte comando: "
+
+#: en_US/l10n.xml:121(title)
+msgid "Checking Statistics"
+msgstr "A confirmar estatísticas"
+
+#: en_US/l10n.xml:122(para)
+msgid "PO strings fall into three categories:"
+msgstr "As strings dos ficheiros PO recaem em três categorias:"
+
+#: en_US/l10n.xml:127(para)
+msgid "<firstterm>translated</firstterm>, meaning the string has been handled by a translator and its source has not changed since then"
+msgstr "<firstterm>traduzida</firstterm>, significa que a string foi manuseada por um tradutor e que a sua fonte não se modificou desde então. "
+
+#: en_US/l10n.xml:134(para)
+msgid "<firstterm>fuzzy</firstterm>, meaning the string has changed since it was last handled by a translator"
+msgstr "<firstterm>fuzzy</firstterm>, significa que a string se alterou desde a última vez que foi modificada por um tradutor "
+
+#: en_US/l10n.xml:140(para)
+msgid "<firstterm>untranslated</firstterm>, meaning no translation has yet been provided for this string, or it is brand new"
+msgstr "<firstterm>por traduzir</firstterm>, significa que ainda não foi adiantada qualquer tradução para a string em questão, ou então, tratar-se de uma string recente."
+
+#: en_US/l10n.xml:146(para)
+msgid "To see a rough statistical tally of the string handling inside the PO for a module, use the following command:"
+msgstr "Para ver uma aproximação estatística relativamente ao tratamento das strings num PO para determinado módulo, use o seguinte comando:"
+
+#: en_US/l10n.xml:151(para)
+msgid "For each locale in the list, a count is shown of translated, fuzzy, and untranslated strings in that order. Tallies that only provide two numerals are usually translated followed by untranslated. Tallies with only one numeral are usually fully translated."
+msgstr "Para cada local nas listas, é mostrada uma contagem das strings traduzidas, fuzzy, e por traduzir, nesta mesma ordem. Tallies"
+
+#: en_US/l10n.xml:158(para)
+msgid "To see only a specific locale, append a dash and the locale code to the <command>postat</command> target:"
+msgstr "Para visualizar especificamente uma língua, acrescente uma barra e o código da localização ao comando <command>postat</command> destino:"
+
+#: en_US/publishing.xml:11(title)
+msgid "Publishing Official Documentation"
+msgstr "Publicar a Documentação Oficial"
+
+#: en_US/publishing.xml:12(para)
+msgid "This chapter shows how to publish official Fedora Documentation Project work to the <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> website. To publish official documentation, you must be approved to write to the web repository in CVS. Access for publishing is limited to contributors who have demonstrated capacity for working with CVS and other project tools. Once you have acquired and are comfortable with these skills, contributions as a publisher are welcome."
+msgstr "Este capítulo mostra como publicar o trabalho no Projecto de Documentação do Fedora oficial para o servidor <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem>. Para publicar a documentação oficial, deverá estar aprovado para escrever o repositório Web no CVS. O acesso de publicação está limitado aos contribuintes que tenham demonstrado capacidade para trabalhar com o CVS e as outras ferramentas do projecto. Logo que a tenha adquirido e esteja à vontade com esses conhecimentos, as contribuições como responsável de publicação são bem-vindas."
+
+#: en_US/publishing.xml:21(title)
+msgid "How the Site Works"
+msgstr "Como Funciona o Site"
+
+#: en_US/publishing.xml:22(para)
+msgid "The <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> website is a set of PHP files and scripts. Publishers maintain these files in a CVS repository, and the website host retrieves them hourly to refresh the site. The host does not automatically use the newest content for the website. Instead, it pulls files with the CVS tag <systemitem>LIVE</systemitem> to populate the website."
+msgstr "A página Web do <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> é um conjunto de ficheiros e programas em PHP. Os responsáveis de publicação mantêm estes ficheiros num repositório de CVS e a página Web transfere-os de hora a hora para actualizar a página. A máquina não usa automaticamente o conteúdo mais recente para a página Web. Em vez disso, transfere os ficheiros com a marca de CVS <systemitem>LIVE</systemitem> para preencher a página Web."
+
+#: en_US/publishing.xml:30(para)
+msgid "Each publisher sets up a local testing website on an available Fedora system. This site, sometimes called a <firstterm>sandbox</firstterm>, allows the publisher to test and view changes to documents, and ensure stability on the public site."
+msgstr "Cada responsável pela publicação configura uma página de testes num sistema Fedora que que esteja disponível. Esta página do servidor, chamada normalmente de <firstterm>ambiente de testes</firstterm>, permite ao responsável testar e ver as alterações dos documentos, garantindo a estabilidade da página para o público."
+
+#: en_US/publishing.xml:37(title)
+msgid "Setting Up a Web Sandbox"
+msgstr "A configurar um ambiente de testes na Web"
+
+#: en_US/publishing.xml:38(para)
+msgid "To test document publishing, first set up a web sandbox on a local Fedora system."
+msgstr "Para testar a publicação do documento, configure primeiro um ambiente de testes na Web numa máquina local de Fedora."
+
+#: en_US/publishing.xml:42(para)
+msgid "Install the \"Web Server\" package group:"
+msgstr "Instale o grupo de pacotes \"Web Server\" (Servidor Web):"
+
+#: en_US/publishing.xml:43(screen)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Web Server\"'"
+msgstr "su -c 'yum groupinstall \"Web Server\"'"
+
+#: en_US/publishing.xml:46(para)
+msgid "Create a folder for the web server to access the site files."
+msgstr "Crie uma pasta para o servidor Web aceder aos ficheiros da página."
+
+#: en_US/publishing.xml:48(screen)
+#, no-wrap
+msgid "su -c 'mkdir /var/www/fedora'"
+msgstr "su -c 'mkdir /var/www/fedora'"
+
+#: en_US/publishing.xml:51(para)
+msgid "Change the permissions on this directory to make it easier to access for your normal user account."
+msgstr "Mude as permissões nesta pasta para facilitar o acesso para a sua conta normal de utilizador."
+
+#: en_US/publishing.xml:53(replaceable)
+#: en_US/publishing.xml:62(replaceable)
+msgid "username"
+msgstr "utilizador"
+
+#: en_US/publishing.xml:53(screen)
+#, no-wrap
+msgid "su -c 'chown <placeholder-1/> /var/www/fedora'"
+msgstr "su -c 'chown <placeholder-1/> /var/www/fedora'"
+
+#: en_US/publishing.xml:56(para)
+msgid "Link to the new directory from your home directory."
+msgstr "Associe a pasta nova à sua pasta pessoal."
+
+#: en_US/publishing.xml:57(screen)
+#, no-wrap
+msgid "ln -s /var/www/fedora ~/fedora"
+msgstr "ln -s /var/www/fedora ~/fedora"
+
+#: en_US/publishing.xml:60(para)
+msgid "Retrieve the web module from CVS."
+msgstr "Transfira o módulo 'web' do CVS."
+
+#: en_US/publishing.xml:61(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora\n"
+"cvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+msgstr ""
+"cd ~/fedora\n"
+"cvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+
+#: en_US/publishing.xml:64(title)
+msgid "Web CVS Access"
+msgstr "Acesso de CVS ao Web"
+
+#: en_US/publishing.xml:65(para)
+msgid "You must have access to the <systemitem>cvsweb</systemitem> module through the Fedora Account System to check in changes. If you do not have access, you can use <userinput><![CDATA[:pserver:anonymous]]></userinput> in place of <userinput><![CDATA[:ext:username]]></userinput> above. Visit the Fedora Account System at <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> for more information."
+msgstr "Deverá ter acesso ao módulo <systemitem>cvsweb</systemitem> através do Sistema de Contas do Fedora para verificar e enviar as alterações. Se não tiver acesso, poderá usar o <userinput><![CDATA[:pserver:anonymous]]></userinput> em vez do <userinput><![CDATA[:ext:utilizador]]></userinput> indicado acima. Visite o Sistema de Contas do Fedora em <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> para mais informações."
+
+#: en_US/publishing.xml:77(para)
+msgid "Edit the <filename>/etc/hosts</filename> file and add the following line <emphasis>after</emphasis> all other lines:"
+msgstr "Edite o ficheiro <filename>/etc/hosts</filename> e adicione a seguinte linha <emphasis>depois</emphasis> de todas as outras linhas:"
+
+#: en_US/publishing.xml:80(screen)
+#, no-wrap
+msgid "127.0.0.1 docs.localhost.localdomain"
+msgstr "127.0.0.1 docs.localhost.localdomain"
+
+#: en_US/publishing.xml:83(para)
+msgid "Create a file <filename>/etc/httpd/conf.d/fpo.conf</filename> with the following content:"
+msgstr "Crie um ficheiro <filename>/etc/httpd/conf.d/fpo.conf</filename> com o seguinte conteúdo:"
+
+#: en_US/publishing.xml:97(para)
+msgid "Create a file <filename>/etc/php.d/fpo.ini</filename> with the following content:"
+msgstr "Crie um ficheiro <filename>/etc/php.d/fpo.ini</filename> com o seguinte conteúdo:"
+
+#: en_US/publishing.xml:99(screen)
+#, no-wrap
+msgid "include_path = \".:/var/www/fedora/web/include\""
+msgstr "include_path = \".:/var/www/fedora/web/include\""
+
+#: en_US/publishing.xml:102(para)
+msgid "Start the web server using the following command:"
+msgstr "Inicie o servidor Web com o seguinte comando:"
+
+#: en_US/publishing.xml:103(screen)
+#, no-wrap
+msgid "su -c '/sbin/service httpd start'"
+msgstr "su -c '/sbin/service httpd start'"
+
+#: en_US/publishing.xml:104(para)
+msgid "To have the web server start at every boot, use the following command:"
+msgstr "Para que o servidor Web seja iniciado sempre no arranque, execute o seguinte comando:"
+
+#: en_US/publishing.xml:106(screen)
+#, no-wrap
+msgid "su -c '/sbin/chkconfig httpd on'"
+msgstr "su -c '/sbin/chkconfig httpd on'"
+
+#: en_US/publishing.xml:109(para)
+msgid "To test the new sandbox site, open a Web browser and point it at the URL <uri>http://docs.localhost.localdomain</uri>."
+msgstr "Para testar a página do novo ambiente de teste, abra um navegador Web e aponte-o para o URL <uri>http://docs.localhost.localdomain</uri>."
+
+#: en_US/publishing.xml:113(title)
+msgid "Creating a New Publication"
+msgstr "Criar uma Publicação Nova"
+
+#: en_US/publishing.xml:115(title)
+msgid "General Guidelines"
+msgstr "Recomendações Gerais"
+
+#: en_US/publishing.xml:116(para)
+msgid "Follow these guidelines to ensure maintainability and ease of use for all publishers."
+msgstr "Siga estas recomendações para garantir a facilidade de uso e manutenção para todos os responsáveis pela publicação."
+
+#: en_US/publishing.xml:120(para)
+msgid "Use a short, descriptive name for the document directory. The module name from its Docs CVS location is usually appropriate. Good examples include <filename class=\"directory\">install-guide/</filename> or <filename class=\"directory\">example-tutorial/</filename>."
+msgstr "Use um nome breve e descritivo para a pasta de documentos. O nome do módulo no seu local do CVS é normalmente apropriado. Os bons exemplos incluem o <filename class=\"directory\">install-guide/</filename> ou o <filename class=\"directory\">example-tutorial/</filename>."
+
+#: en_US/publishing.xml:127(para)
+msgid "Under the document directory, include a branch directory if the document references specific features of a particular Fedora release."
+msgstr "Sob a pasta do documento, inclua a pasta de uma ramificação, caso o documento faça referência a funcionalidades específicas de uma dada versão do Fedora."
+
+#: en_US/publishing.xml:132(para)
+msgid "Under the branch directory (or document directory if no branches are necessary), make at least a <filename class=\"directory\">en_US/</filename> directory. Make an additional directory for each locale that has been fully translated."
+msgstr "Na pasta da ramificação (ou na pasta do documento se não existirem ramificações), crie pelo menos uma pasta <filename class=\"directory\">en_US/</filename>. Crie uma pasta adicional para cada código de país cuja documentação tenha sido completamente traduzida."
+
+#: en_US/publishing.xml:141(title)
+msgid "Adding Content"
+msgstr "Adicionar Conteúdos"
+
+#: en_US/publishing.xml:142(para)
+msgid "To add content, follow the procedure below. The following commands show an example of adding content for a new document called the <citetitle>Foobar Tutorial</citetitle>. This document includes a translation for the \"zz_XX\" locale and follows specifics of each Fedora release."
+msgstr "Para adicionar conteúdos, siga o procedimento abaixo. Os comandos seguintes mostra um exemplo de adição de conteúdos para um documento novo chamado <citetitle>Tutorial XPTO</citetitle>. Este documento inclui uma tradução para o código de país \"zz_XX\" e segue as especificidades de cada versão do Fedora."
+
+#: en_US/publishing.xml:149(para)
+msgid "Make the required directory structure."
+msgstr "Crie a estrutura de pastas desejadas."
+
+#: en_US/publishing.xml:150(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"mkdir foobar-tutorial\n"
+"mkdir foobar-tutorial/f7\n"
+"mkdir foobar-tutorial/f7/{en_US,zz_XX}"
+msgstr ""
+"cd ~/fedora/web/html/docs/\n"
+"mkdir tutorial-xpto\n"
+"mkdir tutorial-xpto/f7\n"
+"mkdir tutorial-xpto/f7/{en_US,zz_XX}"
+
+#: en_US/publishing.xml:156(para)
+msgid "Build the HTML version of each translation of the document from Docs CVS."
+msgstr "Crie a versão em HTML de cada tradução do documento a partir do CVS de documentação."
+
+#: en_US/publishing.xml:158(replaceable)
+msgid "~/my-docs/foobar-tutorial/F-7/"
+msgstr "~/os-meus-docs/tutorial-xpto/F-7/"
+
+#: en_US/publishing.xml:158(screen)
+#, no-wrap
+msgid ""
+"cd <placeholder-1/>\n"
+"make html-en_US html-zz_XX"
+msgstr ""
+"cd <placeholder-1/>\n"
+"make html-en_US html-zz_XX"
+
+#: en_US/publishing.xml:162(para)
+msgid "Copy the HTML content to the web sandbox."
+msgstr "Copie o conteúdo em HTML para o ambiente de teste da Web."
+
+#: en_US/publishing.xml:163(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/foobar-tutorial/f7/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/"
+msgstr ""
+"cd ~/fedora/web/html/docs/tutorial-xpto/f7/\n"
+"cp -r ~/os-meus-docs/tutorial-xpto/F-7/tutorial-xpto-en_US/ en_US/\n"
+"cp -r ~/os-meus-docs/tutorial-xpto/F-7/tutorial-xpto-zz_XX/ zz_XX/"
+
+#: en_US/publishing.xml:168(para)
+msgid "Convert the HTML in each directory to PHP using the provided <filename>docbookhtml2php.py</filename> script."
+msgstr "Converta o HTML em cada pasta para PHP, usando o programa <filename>docbookhtml2php.py</filename> que é fornecido."
+
+#: en_US/publishing.xml:177(para)
+msgid "Create any necessary <filename>index.php</filename> files for the overall directories. Each document and branch directory must have an <filename>index.php</filename> file directing users to appropriate content. In this example, the necessary files are <filename>foobar-tutorial/index.php</filename> and <filename>foobar-tutorial/f7/index.php</filename>. You do not need to write these files from scratch. Copy an existing file from another document, and change it as needed to suit the new document."
+msgstr "Crie os ficheiros <filename>index.php</filename> necessários para as pastas globais. Cada pasta de documento e ramificação deverá ter um ficheiro <filename>index.php</filename> que direcciona os utilizadores para o conteúdo apropriado. Neste exemplo, os ficheiros necessários são o <filename>tutorial-xpto/index.php</filename> e o <filename>tutorial-xpto/f7/index.php</filename>. Não precisa de escrever estes ficheiros do zero. Copie um ficheiro existente a partir de outro documento e mude-o da forma adequada para o novo documento."
+
+#: en_US/publishing.xml:187(para)
+msgid "Depending on content, publication may include changing a higher-level <filename>index.php</filename> file."
+msgstr "Dependendo do contexto, a publicação poderá incluir a mudança de um ficheiro <filename>index.php</filename> de um nível superior."
+
+#: en_US/publishing.xml:191(para)
+msgid "To test the changes in your sandbox, open a web browser and point it at <uri>http://docs.localhost.localdomain/</uri>."
+msgstr "Para testar as alterações no seu ambiente de teste, abra um navegador Web e aponte-o para <uri>http://docs.localhost.localdomain/</uri>."
+
+#: en_US/publishing.xml:195(title)
+msgid "Always Test Changes"
+msgstr "Teste Sempre as Alterações"
+
+#: en_US/publishing.xml:196(para)
+msgid "<emphasis>Do not proceed further until you test all changes.</emphasis> Check that all links and index pages work."
+msgstr "<emphasis>Não siga mais em frente até que teste todas as alterações.</emphasis> Verifique se todas as ligações e páginas de índice funcionam."
+
+#: en_US/publishing.xml:204(title)
+msgid "Pushing Content to the Web"
+msgstr "Enviar o Conteúdo para a Web"
+
+#: en_US/publishing.xml:205(para)
+msgid "To push your new content to the web site, follow this procedure:"
+msgstr "Para enviar o seu novo conteúdo para a página Web, siga este procedimento:"
+
+#: en_US/publishing.xml:209(para)
+msgid "Add all the new file content to CVS."
+msgstr "Adicione todos os conteúdos novos de ficheiros ao CVS."
+
+#: en_US/publishing.xml:210(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"cvs add foobar-tutorial\n"
+"cd foobar-tutorial\n"
+"cvs add f7\n"
+"cd f7\n"
+"cvs add en_US/ zz_XX/\n"
+"cvs add en_US/*php en_US/stylesheet-images/\n"
+"cvs add zz_XX/*php zz_XX/stylesheet-images/\n"
+"cvs add en_US/stylesheet-images/*png\n"
+"cvs add zz_XX/stylesheet-images/*png\n"
+"cd ../../\n"
+"cvs add foobar-tutorial/index.php\n"
+"cvs add foobar-tutorial/f7/index.php\n"
+msgstr ""
+"cd ~/fedora/web/html/docs/\n"
+"cvs add tutorial-xpto\n"
+"cd tutorial-xpto\n"
+"cvs add f7\n"
+"cd f7\n"
+"cvs add en_US/ zz_XX/\n"
+"cvs add en_US/*php en_US/stylesheet-images/\n"
+"cvs add zz_XX/*php zz_XX/stylesheet-images/\n"
+"cvs add en_US/stylesheet-images/*png\n"
+"cvs add zz_XX/stylesheet-images/*png\n"
+"cd ../../\n"
+"cvs add tutorial-xpto/index.php\n"
+"cvs add tutorial-xpto/f7/index.php\n"
+
+#: en_US/publishing.xml:226(para)
+msgid "Commit the changes to CVS. Use a message that describes the document being committed."
+msgstr "Envie as alterações para o CVS. Use uma mensagem que descreva o conteúdo a ser enviado."
+
+#: en_US/publishing.xml:228(replaceable)
+msgid "message about document"
+msgstr "mensagem acerca do documento"
+
+#: en_US/publishing.xml:228(screen)
+#, no-wrap
+msgid "cvs ci -m '<placeholder-1/>' foobar-tutorial/"
+msgstr "cvs ci -m '<placeholder-1/>' tutorial-xpto/"
+
+#: en_US/publishing.xml:231(para)
+msgid "Tag the content <systemitem>LIVE</systemitem> in CVS."
+msgstr "Marque o conteúdo como <systemitem>LIVE</systemitem> no CVS."
+
+#: en_US/publishing.xml:233(screen)
+#, no-wrap
+msgid "cvs tag -F LIVE foobar-tutorial/"
+msgstr "cvs tag -F LIVE tutorial-xpto/"
+
+#: en_US/vim.xml:13(title)
+msgid "VIM and DocBook"
+msgstr "O VIM e o DocBook"
+
+#: en_US/vim.xml:16(primary)
+#: en_US/vim.xml:33(primary)
+msgid "VIM"
+msgstr "VIM"
+
+#: en_US/vim.xml:19(para)
+msgid "VIM has many features to help you write XML content such as DocBook, including syntax highlighting and customizable key bindings. Additionally, one can easily use external programs from VIM for features such as spell-checking. This chapter assumes you already know generally how to use VIM; if you want to learn how, try the <command>vimtutor</command> or by typing <userinput>:help tutor</userinput> from inside VIM."
+msgstr "O VIM tem diversas funcionalidades que o ajudam a criar conteúdos em XML, como o DocBook, incluindo o realce de sintaxe e a atribuição de atalhos de teclado personalizados. Para além disso, poderá usar facilmente programas externos a partir do VIM para funcionalidades como a verificação ortográfica. Este capítulo assume que já tem algum conhecimento geral de utilização do VIM; se quiser aprender como, experimente o <command>vimtutor</command> ou escrevendo <userinput>:help tutor</userinput> dentro do VIM."
+
+#: en_US/vim.xml:30(title)
+msgid "Setting Up Your <filename>.vimrc</filename> File"
+msgstr "Configurar o seu Ficheiro <filename>.vimrc</filename>"
+
+#: en_US/vim.xml:34(secondary)
+#: en_US/emacs.xml:44(secondary)
+msgid "configuration file"
+msgstr "ficheiro de configuração"
+
+#: en_US/vim.xml:37(para)
+msgid ""
+"Below is a short sample <filename>.vimrc</filename> file that turns on some VIM features useful for editing SGML or XML content such as DocBook: <screen>\n"
+"<computeroutput>\" Turn off vi compatibility settings like limited undo\n"
+"set nocompatible\n"
+"\" Syntax highlighting based on file extension\n"
+"syntax on\n"
+"\" Automatically insert newlines after 80 characters\n"
+"set textwidth=80\n"
+"\" Automatically indent\n"
+"set autoindent\n"
+"\" Match SGML tags with %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+msgstr ""
+"Segue-se um pequeno exemplo do ficheiro <filename>.vimrc</filename> que activa algumas das funcionalidades úteis do VIM para editar conteúdos em SGML ou XML, como o DocBook: <screen>\n"
+"<computeroutput>\" Desligar as opções de compatibilidade, como o 'desfazer' limitado\n"
+"set nocompatible\n"
+"\" Realce de sintaxe com base na extensão do ficheiro\n"
+"syntax on\n"
+"\" Inserir automaticamente mudanças de linha ao fim de 80 caracteres\n"
+"set textwidth=80\n"
+"\" Indentação automática\n"
+"set autoindent\n"
+"\" Corresponder as marcas de SGML com o %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+
+#: en_US/vim.xml:55(para)
+msgid "Some of these features require the <filename>vim-enhanced</filename> package to be installed. If you are using or the <filename>vim-minimal</filename> package, or if you are using an older version of VIM, you may not have the <filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still download <ulink url=\"http://vim.org/scripts/script.php?script_id=39\">matchit.zip from Vim.org</ulink> and load it separately."
+msgstr "Algumas destas funcionalidades necessitam de ter instalado o pacote <filename>vim-enhanced</filename>. Se estiver a usar o pacote <filename>vim-minimal</filename> ou se estiver a usar uma versão antiga do VIM, poderá não ter o ficheiro <filename>$VIMRUNTIME/macros/matchit.vim</filename>. Poderá à mesma transferir o <ulink url=\"http://vim.org/scripts/script.php?script_id=39\">ficheiro matchit.zip do Vim.org</ulink> e carregá-lo em separado."
+
+#: en_US/vim.xml:69(title)
+msgid "Keymapping with VIM"
+msgstr "Mapeamento de teclas com o VIM"
+
+#: en_US/vim.xml:71(para)
+msgid ""
+"VIM can speed up your DocBook creation by mapping frequently typed tags (or any words or phrases) onto short key combinations. By default, the keymap leader is the backslash (<literal>\\</literal>), but it can be redefined with a command like <userinput>let mapleader =\n"
+" \",\"</userinput>. There are two ways to use the following example; you can put it directly in your <filename>.vimrc</filename>, or you can save it in a separate file and load it with a <userinput>source</userinput> command in your <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\n"
+"\" skip ahead to after next tag without leaving insert mode\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\n"
+"\" common tags that start a new text block\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\n"
+"\" common tags that are placed inline\n"
+"\" use <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></command><esc>F>a \n"
+"\" entities\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+msgstr ""
+"O VIM poderá acelerar a criação do seu DocBook, mapeando as teclas escritas com mais frequência (ou palavras ou frases) em combinações de teclas breves. Por omissão, o líder do mapa de teclados é a barra invertida (<literal>\\</literal>), mas poderá ser redefinida com um comando do tipo <userinput>let mapleader =\n"
+" \",\"</userinput>. Existem duas formas de usar o seguinte exemplo; podê-lo-á colocar direcamente no seu ficheiro <filename>.vimrc</filename> ou podê-lo-a gravar num ficheiro separado e fazendo referência com o comando <userinput>source</userinput> no seu <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\" passar à frente, a seguir à próxima marca, sem deixar o modo de inserção\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\" marcas comuns que iniciam um novo bloco de texto\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\" marcas comuns que se colocam de forma incorporada\n"
+"\" use <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></command><esc>F>a \n"
+"\" entidades\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+
+#: en_US/vim.xml:110(para)
+msgid "Unfortunately, there is not currently a complete macro set for all DocBook commands, so you will need to define them yourself or customize the definitions in the examples from <xref linkend=\"sn-vim-additional-resources\"/>."
+msgstr "Infelizmente, não existe de momento um conjunto de macros completo para todos os comandos do DocBook, pelo que terá de os definir você mesmo ou personalizar as definições nos exemplos em <xref linkend=\"sn-vim-additional-resources\"/>."
+
+#: en_US/vim.xml:119(title)
+msgid "Additional VIM Resources"
+msgstr "Recursos Adicionais do VIM"
+
+#: en_US/vim.xml:121(para)
+msgid "Additional information about VIM may be found from:"
+msgstr "Poderá encontrar mais informações acerca do VIM em:"
+
+#: en_US/vim.xml:127(para)
+msgid "<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to Vi Improved (VIM)</citetitle>"
+msgstr "<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC\"> Exemplo de sgml-vimrc</ulink> do <citetitle>Guia para principiantes do Vi Improved (VIM)</citetitle>"
+
+#: en_US/vim.xml:134(para)
+msgid "The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick Reference Card</ulink>"
+msgstr "O <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">Cartão de Referências Rápidas do VIM</ulink>"
+
+#: en_US/vim.xml:140(ulink)
+msgid "Vim as XML Editor"
+msgstr "O Vim como Editor de XML"
+
+#: en_US/vim.xml:145(para)
+msgid "The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the <filename>vim-common</filename> package —<filename>/usr/share/vim/<replaceable><version></replaceable>/doc/intro.txt</filename> or type <userinput>:help intro</userinput> from within VIM"
+msgstr "O <citetitle>MANUAL DE REFERÊNCIA DO VIM</citetitle>, que vem com o pacote <filename>vim-common</filename> —<filename>/usr/share/vim/<replaceable><versão></replaceable>/doc/intro.txt</filename> ou escrevendo <userinput>:help intro</userinput> dentro do VIM"
+
+#: en_US/tutorial.xml:13(title)
+msgid "The Layout of a Tutorial"
+msgstr "O Formato de um Tutorial"
+
+#: en_US/tutorial.xml:14(para)
+msgid "In this chapter, you will find an example of a very short tutorial as used by the Fedora Documentation Project. This example is specific to the way the Docs Project uses DocBook XML. The example consists of a set of files used to hold the content and metadata for the tutorial."
+msgstr "Neste capítulo, irá descobrir um exemplo de um tutorial bastante curto de documentação do Projecto Fedora. Este exemplo é específico para a forma como o Projecto de Documentação usa o DocBook em XML. O exemplo consiste num conjunto de ficheiros usados para manter o conteúdo, bem como metadados para o tutorial."
+
+#: en_US/tutorial.xml:19(title)
+msgid "The Article"
+msgstr "O Artigo"
+
+#: en_US/tutorial.xml:21(primary)
+#: en_US/tutorial.xml:56(primary)
+msgid "tutorial layout"
+msgstr "formato do tutorial"
+
+#: en_US/tutorial.xml:22(secondary)
+msgid "article"
+msgstr "artigo"
+
+#: en_US/tutorial.xml:24(para)
+msgid "Below is a sample article:"
+msgstr "Em baixo, encontra-se um artigo de exemplo:"
+
+#: en_US/tutorial.xml:54(title)
+msgid "The Metadata"
+msgstr "Os Metadados"
+
+#: en_US/tutorial.xml:57(secondary)
+msgid "metadata"
+msgstr "metadados"
+
+#: en_US/tutorial.xml:59(para)
+msgid "The <filename>rpm-info.xml</filename> file contains all the required metadata for the document. This metadata includes title, authorship, licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates the content of this file:"
+msgstr "O ficheiro <filename>rpm-info.xml</filename> contém todos os metadados necessários para o documento. Estes metadados incluem o título, a autoria, a licença e o histórico de versões. O <xref linkend=\"ex-rpminfo\"/> ilustra o conteúdo deste ficheiro:"
+
+#: en_US/tutorial.xml:65(title)
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr "Ficheiro <filename>rpm-info.xml</filename> de Exemplo"
+
+#: en_US/tutorial.xml:95(para)
+msgid "If you are not familiar with XML editing, copy and paste this file from an existing module and then edit the values for the various elements as appropriate. Consult Fedora Documentation Project members and help channels for more assistance if needed."
+msgstr "Se não estiver familiarizado com a edição em XML, copie e cole este ficheiro a partir de um módulo existente e edite depois os valores dos vários elementos, como for mais apropriado. Consulte os membros do Projecto de Documentação do Fedora e os canais de ajuda para maior assistência, se for necessário."
+
+#: en_US/style.xml:14(title)
+msgid "Style"
+msgstr "Estilo"
+
+#: en_US/style.xml:16(para)
+msgid "Writing good technical documentation is not simply reproducing command lines and instruction sets. Good documentation is easy to read, understand, and translate, and presents a concise logical progression of concepts. Good documentation can also be defined by what it does <emphasis>not</emphasis> contain. Your tutorial should avoid:"
+msgstr "A escrita de boa documentação técnica não é simplemente reproduzir as linhas de comandos e os conjuntos de instruções. A boa documentação é fácil de ler, compreender e traduzir, oferecendo uma progressão lógica concisa dos conceitos. A boa documentação também poderá ser definida pelo que <emphasis>não</emphasis> contém. O seu tutorial deverá evitar:"
+
+#: en_US/style.xml:26(para)
+msgid "Excessive wordiness"
+msgstr "Uso excessivo de palavras"
+
+#: en_US/style.xml:31(para)
+msgid "Unnecessary or undefined jargon"
+msgstr "Uso de calão técnico indefinido ou desnecessário"
+
+#: en_US/style.xml:36(para)
+msgid "Grammatical or spelling errors"
+msgstr "Erros ortográficos ou gramaticais"
+
+#: en_US/style.xml:41(para)
+msgid "References to yourself or your experiences"
+msgstr "Referências a si próprio ou às suas experiências"
+
+#: en_US/style.xml:46(para)
+msgid "Remarks which might offend or confuse any reader"
+msgstr "Comentários que possam ofender ou confundir qualquer leitor"
+
+#: en_US/style.xml:51(para)
+msgid "This chapter contains style rules and guidelines for writing Fedora documentation. Guidelines are not the same as rules. It is acceptable to violate a guideline when it makes your material easier to understand. Follow guidelines whenever possible, but follow rules at all times. Assume any advice is a guideline unless identified otherwise."
+msgstr "Este capítulo contém regras e instruções de estilo para escrever documentação para o Fedora. As instruções não são necessariamente regras. É aceitável voltar uma instrução, se esta tornar o seu material mais fácil de compreender. Siga as instruções se possível, mas siga sempre as regras. Assuma que qualquer conselho é uma instrução a menos que seja identificado em contrário."
+
+#: en_US/style.xml:62(title)
+msgid "Why Style Is Important"
+msgstr "Porque é que o Estilo é Importante"
+
+#: en_US/style.xml:64(para)
+msgid "Writing well comes naturally to almost no one. It is a skill that professional writers, even famous ones, must practice constantly. <firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> is the quality that separates elegant writing from the merely functional."
+msgstr "A boa escrita não vem naturalmente para a maior parte das pessoas. É um dom que os escritores profissionais, até mesmo os famosos, precisam de praticar constantemente. O <firstterm>Estilo</firstterm><indexterm><primary>estilo</primary></indexterm> é a qualidade que separa a escrita elegante da meramente funcional."
+
+#: en_US/style.xml:77(para)
+msgid "For example, refer to. <ulink url=\"http://www.online-literature.com/james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>. Please note that this example contains some mature themes and language, and is not suitable for all readers."
+msgstr "Por exemplo, veja em <ulink url=\"http://www.online-literature.com/james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>. Por favor, note que este exemplo contém alguns temas e linguagem madura, não sendo, por isso, adequado a todos os leitores."
+
+#: en_US/style.xml:71(para)
+msgid "Elegance comes in many forms. In prose and poetry, elegant writing may not follow some (or any) common rules of grammar, syntax, or spelling. A good example is Episode 18, \"Penelope,\" in James Joyce's novel <citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long streams of words without punctuation to simulate a character's internal consciousness. By violating basic rules of grammar and syntax, Joyce simulates the disorganized but loosely connected thought patterns of the narrator."
+msgstr "A elegância surge sob diversas formas. Na prosa e na poesia, a escrita elegante poderá não seguir algumas (ou todas) as regras comuns da gramática, sintaxe ou ortografia. Um bom exemplo é o Episódio 18, \"Penélope,\" do romance de James Joyce <citetitle>Ulisses</citetitle><footnote id=\"fn-ulysses\"><placeholder-1/></footnote>. Aqui, Joyce usa grandes sequências de palavras sem pontuação, de modo a simular a consciência interna de uma personagem. Ao violar as regras básicas da sintaxe e da gramática, Joyce simula os padrões de pensamento desorganizados mas levemente ligados do narrador."
+
+#: en_US/style.xml:89(para)
+msgid "Technical documentation, however, should always respect these rules. The more a document departs from standard language usage, the more difficult the material becomes for the reader. For example, readers may not be native speakers of the language used, or they might be reading a translation. If the writer uses slang, idioms, or jargon, a reader or translator may easily become confused. The following example compares two different written executions of the same idea:"
+msgstr "Contudo, a documentação técnica deverá sempre respeitar estas regras. Quanto mais um documento se desviar da utilização comum da língua, mais difícil se torna o material para o leitor. Por exemplo, os leitores poderão não usar a língua do documento como língua nativa ou poderão estar a ler uma tradução. Se o escritor usar 'calão', dialectos ou termos demasiado técnicos, o leitor ou o tradutor poderão ficar facilmente confusos. O exemplo seguinte compara duas execuções da mesma ideia, escritas de forma diferente:"
+
+#: en_US/style.xml:100(title)
+msgid "Incorrect style"
+msgstr "Estilo incorrecto"
+
+#. I prefer "incorrect," because I think terms such as
+#. "problematic" are mealy-mouthed. They remind me of the late
+#. 1980's English textbook trend toward the politically correct yet
+#. wholly unhelpful "standard/nonstandard." But then, I tend to be
+#. dogmatic; it's probably my Catholic upbringing. [PWF]
+#: en_US/style.xml:108(para)
+msgid "So you made the changes I showed you in the last section. What's the next thing you should do? Just pop your thumb drive onto your system and read the <filename>messages</filename> log. When you see \"USB device found,\" then Bob's your uncle."
+msgstr "Portanto, já fez as alterações que lhe mostrei na última secção. Qual é a próxima coisa que deseja fazer? Basta colocar a sua caneta no seu sistema e ler o ficheiro de registo <filename>messages</filename>. Quando vir \"USB device found,\", então teve sucesso."
+
+#: en_US/style.xml:116(title)
+msgid "Correct style"
+msgstr "Estilo correcto"
+
+#. I prefer "correct." See above. [PWF]
+#: en_US/style.xml:120(para)
+msgid ""
+"After you complete the configuration changes above, attach the USB removable media to your system. Use the <command>dmesg</command> command to examine the kernel message log. The message <computeroutput>USB device\n"
+"\t found</computeroutput> indicates that your device was installed successfully."
+msgstr "Depois de terminar as mudanças de configuração acima, ligue o dispositivo removível USB ao seu sistema. Use o comando <command>dmesg</command> para examinar o registo de mensagens do kernel. A mensagem <computeroutput>USB device found</computeroutput> indica que o seu dispositivo foi instalado com sucesso."
+
+#: en_US/style.xml:129(para)
+msgid "The first example is more conversational English, which is not appropriate for official written documentation. The second example is more formal, but as a result it is easier to comprehend, both for native readers and translators."
+msgstr "O primeiro exemplo é um Inglês mais coloquial, o qual não é apropriado para documentação oficial escrita. O segundo exemplo é mais formal, mas tem como resultado uma maior facilidade de compreensão, quer para os leitores nativos quer para os tradutores."
+
+#: en_US/style.xml:135(para)
+msgid "Following style rules and guidelines also makes readers more comfortable with a set of documents. Consistent style enhances the professional appearance of documentation, and its perceived value. On the other hand, lapses in punctuation or poor grammar negatively affect a reader's reaction to written material. A reader can feel that an otherwise correct technical document is lacking in authority, simply because it is poorly written. Readers feel at ease when they do not have to struggle to understand an author's use of language."
+msgstr "Seguir as regras e instruções de estilo também deixa os leitores mais confortáveis com um determinado conjunto de documentos. Um estilo consistente melhor a aparência profissional da documentação, bem como o valor que é transmitido. Por outro lado, os lapsos de pontuação ou uma gramática incorrecta afectam de forma negativa a reacção de um leitor ao material escrito. Um leitor poderá sentir que um documento técnico não tem qualquer autoridade, simplesmente por estar mal escrito. Os leitores facilmente sentem que não têm de lidar com a compreensão da utilização da língua por parte de um autor."
+
+#: en_US/style.xml:146(para)
+msgid "This chapter cannot possibly cover enough material to make every reader a good writer. Some manuals devoted entirely to writing style are themselves hundreds of pages long. This chapter provides enough guidelines for intermediate writers to understand style usage in technical documentation."
+msgstr "Este capítulo não poderá cobrir possivelmente material suficiente para que um leitor seja um bom escritor. Existem alguns manuais dedicados por inteiro ao estilo de escrita, tendo alguns deles centenas de páginas. Este capítulo contém instruções suficientes para os escritores médios compreenderem a utilização do estilo de documentação técnica."
+
+#: en_US/style.xml:153(para)
+msgid "If you are not a practiced writer, whether of technical documentation or otherwise, you may benefit from other style resources. The following list is far from comprehensive, but provides a starting point:"
+msgstr "Se não for um escritor com prática, seja em documentação técnica ou noutra qualquer, poderá beneficiar de outros recursos de estilo. A lista que se segue não é excelente, mas oferece um bom ponto de partida:"
+
+#: en_US/style.xml:161(para)
+msgid "<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules and links to online versions can be found at: <ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+msgstr "<citetitle>The Elements of Style</citetitle>, de William Strunk. Poderá encontrar algumas regras básicas e referências para as versões 'online' em: <ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+
+#: en_US/style.xml:176(para)
+msgid "<citetitle>The Chicago Manual of Style</citetitle>, by the University of Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle.org/\">http://www.chicagomanualofstyle.org/</ulink>"
+msgstr "<citetitle>The Chicago Manual of Style</citetitle>, da University of Chicago Press. Versão 'online': <ulink url=\"http://www.chicagomanualofstyle.org/\">http://www.chicagomanualofstyle.org/</ulink>"
+
+#: en_US/style.xml:183(para)
+msgid "<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/\">http://www.powa.org/</ulink>"
+msgstr "<citetitle>Paradigm Online Writing Assistant</citetitle>, mantido por Chuck Guilford, Ph.D. Apenas 'online': <ulink url=\"http://www.powa.org/\">http://www.powa.org/</ulink>"
+
+#: en_US/style.xml:190(para)
+msgid "There are many free software documentation projects which have developed their own style guidelines. This chapter, in fact, draws heavily on the <citetitle>GNOME Documentation Style Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr "Existem diversos projectos de documentação de software que desenvolveram as suas próprias recomendações de estilo. Este capítulo, de facto, baseia-se em grande medida nas <citetitle>Recomendações de Estilo de Documentação do GNOME</citetitle> (<firstterm>GDSG</firstterm>). Poderá ler a <citetitle>GDSG</citetitle> original em <ulink url=\"http://developer.gnome.org/documents/style-guide/\">http://developer.gnome.org/documents/style-guide/</ulink>."
+
+#: en_US/style.xml:203(title)
+msgid "Fundamental Concepts of Technical Documentation"
+msgstr "Conceitos Fundamentais da Documentação Técnica"
+
+#: en_US/style.xml:206(title)
+msgid "Bibliographic Information"
+msgstr "Informação Bibliográfica"
+
+#: en_US/style.xml:207(para)
+msgid "This section is drawn primarily from the <citetitle>GDSG</citetitle>."
+msgstr "Esta secção baseia-se principalmente na <citetitle>GDSG</citetitle>."
+
+#. This section will reproduce mostly what is in Chapter 1 of
+#. the GDSG. There may be minor changes. FIXME: Make sure the
+#. appropriate front matter of the Documentation Guide includes
+#. attribution as required by the GNU FDL.
+#: en_US/style.xml:218(para)
+msgid "This chapter provides a brief introduction to writing technical documentation."
+msgstr "Este capítulo oferece uma breve introdução à escrita de documentação técnica."
+
+#: en_US/style.xml:224(title)
+msgid "General Style Requirements"
+msgstr "Requisitos Gerais de Estilo"
+
+#: en_US/style.xml:225(para)
+msgid "Technical writing for the Fedora Project imposes special constraints beyond the basic requirements of good prose. Good Fedora technical documentation has the following characteristics:"
+msgstr "A escrita técnica para o Projecto Fedora impõe restrições especiais para além dos requisitos básicos da boa prosa. Uma boa documentação técnica do Fedora tem as seguintes características:"
+
+#: en_US/style.xml:232(term)
+msgid "Comprehensive"
+msgstr "Compreensível"
+
+#: en_US/style.xml:234(para)
+msgid "Describe all of the functionality of a product. Do not omit functionality that you regard as irrelevant for the user."
+msgstr "Descreve todas as funcionalidades de um produto. Não omita funcionalidades que considere irrelevantes para o utilizador."
+
+#: en_US/style.xml:242(term)
+msgid "Conforming"
+msgstr "Em Conformidade"
+
+#: en_US/style.xml:249(para)
+msgid "Describe what you see. Do not describe what you want to see. Present your information in the order that users experience the subject matter."
+msgstr "Descreva o que vê. Não descreva o que deseja ver. Apresente a sua informação pela ordem em que os utilizadores se deparam com o assunto."
+
+#: en_US/style.xml:257(term)
+msgid "Clear"
+msgstr "Limpar"
+
+#: en_US/style.xml:259(para)
+msgid "Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>) to help make your writing clear."
+msgstr "Leia <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>) que o ajuda a tornar a sua escrita mais clara."
+
+#: en_US/style.xml:275(term)
+msgid "Consistent"
+msgstr "Consistente"
+
+#: en_US/style.xml:277(para)
+msgid "Use agreed vocabulary throughout your documentation. Use the same vocabulary as other writers who are working on related documentation."
+msgstr "Utilize vocabulário considerado consensual ao longo da sua documentação. Use o mesmo vocabulário dos outros escritores que estão a trabalhar sobre documentos relacionados com este."
+
+#: en_US/style.xml:285(term)
+msgid "Concise"
+msgstr "Conciso"
+
+#: en_US/style.xml:287(para)
+msgid "Review your work frequently as you write your document. Ask yourself which words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for specific guidelines."
+msgstr "Reveja o seu trabalho com frequência, à medida que escreve o seu documento. Pergunte-se quais as palavras que poderá retirar. Veja algumas recomendações específicas em <xref linkend=\"sn-fundamentals-2\"/>."
+
+#: en_US/style.xml:297(title)
+msgid "Golden Rules"
+msgstr "Regras de Ouro"
+
+#: en_US/style.xml:298(para)
+msgid "This section contains some basic style guidelines. Subsequent sections in this chapter expand on these guidelines to give more detailed guidance."
+msgstr "Esta secção contém algumas recomendações básicas de estilo. As secções seguintes deste capítulo expandem essas recomendações, para lhe dar conselhos mais detalhados."
+
+#: en_US/style.xml:305(term)
+msgid "Golden Rule 1: Be brief"
+msgstr "Regra de Ouro 1: Seja breve"
+
+#: en_US/style.xml:309(para)
+msgid "Limit each sentence to fewer than 25 words."
+msgstr "Limite cada frase a menos de 25 palavras."
+
+#: en_US/style.xml:314(para)
+msgid "Limit each procedure step to 23 words."
+msgstr "Limite cada passo de procedimento a 23 palavras."
+
+#: en_US/style.xml:320(title)
+msgid "Incorrect: Too long"
+msgstr "Incorrecto: Demasiado comprido"
+
+#: en_US/style.xml:321(para)
+msgid "Under normal operating conditions, the kernel does not always immediately write file data to the disks, storing it in a memory buffer and then periodically writing to the disks to speed up operations."
+msgstr "Em condições normais de operação, o kernel não grava sempre imediatamente os dados do ficheiros nos discos, guardando-os numa área em memória e escrevendo periodicamente para os discos, de modo a acelerar as operações."
+
+#: en_US/style.xml:328(title)
+msgid "Correct: Less wordy"
+msgstr "Correcto: Com menos palavreado"
+
+#: en_US/style.xml:329(para)
+msgid "Normally, the kernel stores the data in memory prior to periodically writing the data to the disk."
+msgstr "Normalmente, o kernel guarda os dados em memória antes de os gravar periodicamente no disco."
+
+#: en_US/style.xml:337(term)
+msgid "Golden Rule 2: Be organized"
+msgstr "Regra de Ouro 2: Ser organizado"
+
+#: en_US/style.xml:341(para)
+msgid "Limit each paragraph to one topic."
+msgstr "Limite cada parágrafo a um tópico."
+
+#: en_US/style.xml:346(para)
+msgid "Limit each sentence to one idea."
+msgstr "Limite cada frase a uma ideia."
+
+#: en_US/style.xml:351(para)
+msgid "Limit each procedure step to one action."
+msgstr "Limite cada passo de procedimento a uma acção."
+
+#: en_US/style.xml:357(title)
+msgid "Incorrect: Disorganized topics"
+msgstr "Incorrecto: Tópicos desorganizados"
+
+#: en_US/style.xml:358(para)
+msgid "The <application>Workspace Switcher</application> applet helps you navigate all of the virtual desktops available on your system. The X Window system, working in hand with a piece of software called a <emphasis>window manager</emphasis>, allows you to create more than one virtual desktop, known as <emphasis>workspaces</emphasis>, to organize your work, with different applications running in each workspace. The <application>Workspace Switcher</application> applet is a navigational tool to get around the various workspaces, providing a miniature road map in the GNOME panel showing all your workspaces and allowing you to switch easily between them."
+msgstr "A applet do <application>Alternador de ambiente de trabalho</application> ajuda-o a navegar em todos os ecrãs virtuais do seu sistema. O sistema X Window, funcionando em conjunto com uma pequena componente aplicacional, chamada de <emphasis>gestor de janelas</emphasis>, permite-lhe criar mais de um ecrã virtual, também conhecido por <emphasis>espaço de trabalho</emphasis>, para organizar o seu trabalho, com diferentes aplicações a correr em cada espaço de trabalho. A applet do <application>Selector do Espaço de Trabalho</application> é uma ferramenta de navegação para percorrer os diversos espaços de trabalho, oferecendo um roteiro em miniatura no painel do GNOME, mostrando todos os seus espaços de trabalho e permitindo uma mudança simples entre eles."
+
+#: en_US/style.xml:375(title)
+msgid "Correct: Organized topics"
+msgstr "Correcto: Tópicos organizados"
+
+#: en_US/style.xml:376(para)
+msgid "Use the <application>Workspace Switcher</application> to add new <emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different applications in each workspace. The <application>Workspace Switcher</application> applet provides a miniature map that shows all of your workspaces. You can use the <application>Workspace Switcher</application> applet to switch between workspaces."
+msgstr "Use o <application>Alternador do Ambiente de Trabalho/application> para adicionar novos <emphasis>espaços de trabalho</emphasis> ao ambiente gráfico GNOME. Poderá executar diferentes aplicações em cada um dos espaços de trabalho. A applet do <application>Selector de Espaços de Trabalho</application> oferece um mapa em miniatura que mostra todos os seus espaços de trabalho. Poderá usar a applet do <application>Selector de Espaços de Trabalho</application>, de modo a mudar de espaços de trabalho."
+
+#: en_US/style.xml:388(para)
+msgid "Plan the order of paragraphs before you start writing. Decide which topic you want to cover in each paragraph."
+msgstr "Planeie a ordem dos parágrafos antes de começar a escrever. Decida o tópico que deseja tratar em cada parágrafo."
+
+#: en_US/style.xml:396(term)
+msgid "Golden Rule 3: Be demonstrative"
+msgstr "Regra de Ouro 3: Seja demonstrativo"
+
+#: en_US/style.xml:398(para)
+msgid "Use explicit examples to demonstrate how an application works. Provide instructions rather than descriptions."
+msgstr "Use exemplos explícitos que demonstram como funciona uma aplicação. Forneça instruções em vez de descrições."
+
+#: en_US/style.xml:403(title)
+msgid "Incorrect: Describes but does not demonstrate"
+msgstr "Incorrecto: Descreve mas não demonstra"
+
+#: en_US/style.xml:405(para)
+msgid "There is a text box that you can use to find out the definition of a word."
+msgstr "Existe um campo de texto que poderá usar para descobrir a definição de uma palavra."
+
+#: en_US/style.xml:411(title)
+msgid "Correct: Demonstrates usage"
+msgstr "Correcto: Demonstra a utilização"
+
+#: en_US/style.xml:412(para)
+msgid "To request a definition of a word, type the word in the text box, then select <guilabel>Lookup</guilabel>."
+msgstr "Para pedir a definição de uma palavra, escreva a palavra no campo de texto, seleccionando depois a opção <guilabel>Procurar</guilabel>."
+
+#: en_US/style.xml:418(para)
+msgid "Do not apply this guideline too rigidly. Sometimes you must explain how software works to support your how-to examples."
+msgstr "Não aplique esta recomendação de forma muito rígida. Algumas vezes tem de explicar como funciona o software para suportar os seus exemplos."
+
+#: en_US/style.xml:427(term)
+msgid "Golden Rule 4: Be objective"
+msgstr "Regra de Ouro 4: Ser objectivo"
+
+#: en_US/style.xml:429(para)
+msgid "Write in a neutral tone."
+msgstr "Escreva num tom neutro."
+
+#: en_US/style.xml:433(title)
+msgid "Incorrect: Sentence takes sides"
+msgstr "Incorrecto: A frase tem um conteúdo de opinião parcial"
+
+#: en_US/style.xml:434(para)
+msgid "The applet is a handy little screen grabber."
+msgstr "A applet é um pequeno e útil módulo de captura do ecrã."
+
+#: en_US/style.xml:439(title)
+msgid "Correct: Sentence is objective"
+msgstr "Correcto: A frase é objectiva"
+
+#: en_US/style.xml:440(para)
+msgid "Use the applet to take screenshots."
+msgstr "Use a applet para fazer capturas do ecrã."
+
+#: en_US/style.xml:452(title)
+msgid "Tone"
+msgstr "Tom"
+
+#: en_US/style.xml:453(para)
+msgid "Inappropriate tone hinders reader access to information. A neutral tone free of opinion or personal flavor improves the reader's comprehension. Neutral tone helps writers to work in parallel on a large technical documentation project. Furthermore, additional writers may join the project at any time. Use of a neutral tone helps to achieve consistency across a documentation set, and thereby facilitates user access to information. The best way to achieve a common, neutral tone is to apply the following principles:"
+msgstr "Um tom inapropriado retrai o acesso do utilizador à informação. Um tom neutro e livre de opiniões ou escolhas pessoais aumenta a compreensão por parte do leitor. Um tom netruo ajuda os escritores a trabalharem em paralelo num projecto de documentação técnica grande. Para além disso, poder-se-ão juntar escritores adicionais ao projecto em qualquer altura. A utilização de um tom netruo ajuda a obter alguma consistência em torno de um conjunto de documentos, facilitando deste modo o acesso dos utilizadores à informação. A melhor forma de obter um tom neutro e comum é aplicar os seguintes princípios:"
+
+#: en_US/style.xml:466(term)
+msgid "Avoid humor"
+msgstr "Evite o humor"
+
+#: en_US/style.xml:468(para)
+msgid "Humor distracts from the information you are trying to provide. Humor also makes documentation difficult to translate. Stay factual."
+msgstr "O humor distrai o leitor da informação que você está a tentar transmitir. O humor também torna a documentação mais difícil de traduzir. Resuma-se a factos."
+
+#: en_US/style.xml:476(term)
+msgid "Avoid personal opinions"
+msgstr "Evite opiniões pessoais"
+
+#: en_US/style.xml:478(para)
+msgid "Whether you think a function is useful or woeful is irrelevant. Report the function to the user, with instructions about how to use the function. Stay accurate."
+msgstr "Se acha que uma dada função é útil ou inútil é irrelevante. Relate a função para o utilizador, com instruções de utilização da mesma. Mantenha-se correcto."
+
+#: en_US/style.xml:487(term)
+msgid "Avoid colloquial language"
+msgstr "Evite a linguagem coloquial"
+
+#: en_US/style.xml:489(para)
+msgid "Colloquial language is difficult to translate and usually culture-specific. Stay neutral."
+msgstr "A linguagem coloquial é difícil de traduzir e normalmente é específica da caltura. Mantenha-se neutro."
+
+#: en_US/style.xml:496(term)
+msgid "Avoid topical expressions"
+msgstr "Evite expressões por tópicos"
+
+#: en_US/style.xml:498(para)
+msgid "An expression that is in common use today might convey something completely different tomorrow. Stay technical."
+msgstr "Uma expressão que seja de uso comum nos dias de hoje poderá representar algo completamente diferente amanhã. Mantenha-se técnico."
+
+#: en_US/style.xml:505(term)
+msgid "Avoid aspirational statements"
+msgstr "Evite frases baseadas em suposições futuras"
+
+#: en_US/style.xml:507(para)
+msgid "Statements about the future developments of a product do not belong in technical documentation. Write about what you see right now. Stay real."
+msgstr "As referências aos futuros desenvolvimentos de um produto não pertencem à documentação técnica. Escreva apenas sobre o que existe agora. Mantenha-se realista."
+
+#: en_US/style.xml:517(title)
+msgid "Reaching the Right Audience"
+msgstr "Atinja a Audiência Correcta"
+
+#: en_US/style.xml:518(para)
+msgid "All of the decisions that you make about the structure and content of a manual follow from an understanding of the audience. Consider how the audience accesses the documentation, what sort of information the audience needs, and the experience level of the audience. Usually, you need to create documentation that is suitable for different audiences. The following sections introduce some of the audience-related topics you need to consider."
+msgstr "Todas as decisões que fizer acerca da estrutura e conteúdo de um manual partem de uma compreensão por parte da audiência. Pense na forma como a audiência acede à documentação, ao tipo de informação que a audiência necessita e ao nível de experiência da audiência. Normalmente, é necessário criar uma documentação que seja adequada para diferentes audiências. As seguintes secções introduzem alguns dos tópicos relacionados com a audiência que necessita de ter em consideração."
+
+#: en_US/style.xml:530(title)
+msgid "User Motivation"
+msgstr "Motivação do Utilizador"
+
+#: en_US/style.xml:531(para)
+msgid "Do not waste the time of the user who looks for information in your documentation. Users do not read technical documentation for entertainment. Users usually have specific questions. You need to give clear answers to those questions."
+msgstr "Não ocupe o tempo do utilizador que procura informações na sua documentação. Os utilizadores não lêem documentação técnica por entretenimento. Os utilizadores normalmente têm questões específicas. Terá de dar respostas claras a essas questões."
+
+#: en_US/style.xml:539(title)
+msgid "New Users"
+msgstr "Novos Utilizadores"
+
+#: en_US/style.xml:540(para)
+msgid "New users to Fedora are likely to consult online tutorials for guidance about unfamiliar applications or functionality. Each tutorial should contain enough introductory information to tell new users how to start using the relevant functions. Each tutorial should also contain enough usage instructions to tell users the different actions that they can perform with the command or function. Keep these instructions task-oriented. Do not describe GUI screens, dialogs, and dialog elements in a tutorial, unless there is an unusual feature that affects your instructions."
+msgstr "Os utilizadores novos no Fedora provavelmente irão consultar os tutoriais 'onyline' para se orientarem nas aplicações ou funcionalidades pouco familiares. Cada tutorial deverá conter informação introdutória sufciente para indicar aos novos utilizadores como começar a usar as funções relevantes. Cada tutorial deverá também conter instruções de utilização suficientes para informar os utilizadores das diferentes acções que podem efectuar com o comando ou a função. Mantenha estas instruções orientadas às tarefas. Não descreva as janelas gráficas e os seus elementos num tutoria, a menos que exista alguma funcionalidade anormal que afecte as suas instruções."
+
+#: en_US/style.xml:554(title)
+msgid "Experienced Users"
+msgstr "Utilizadores Experientes"
+
+#: en_US/style.xml:555(para)
+msgid "Experienced users are more likely to use documentation as a reference. The documentation therefore needs to be complete, well-organized, and in the case of printed manuals, well-indexed."
+msgstr "Os utilizadores experientes são mais aptos para usar a documentação como referência. A documentação aí tem de ser completa, bem organizada e, no caso dos manuais impressos, bem indexada."
+
+#: en_US/style.xml:563(title)
+msgid "Do Not Offend Your Audience"
+msgstr "Não Ofenda a sua Audiência"
+
+#: en_US/style.xml:564(para)
+msgid "To avoid offending your readers, apply the following guidelines to your documentation:"
+msgstr "Para evitar ofender os seus leitores, aplique as seguintes recomendações à sua documentação:"
+
+#: en_US/style.xml:570(term)
+msgid "Avoid insider language"
+msgstr "Evite a linguagem própria"
+
+#: en_US/style.xml:572(para)
+msgid "Insider language includes both undefined jargon and the tendency of the computer community to shorten words. For example, use the term <literal>documentation</literal> instead of the term <literal>docs</literal>. A term may be jargon if it fails all the following conditions:"
+msgstr "A linguagem própria ou interna inclui algum calão indefinido e a tendência da comunidade informática de reduzir as palavras. Por exemplo, use o termo <literal>documentação</literal> em vez do termo <literal>docs</literal>. Um termo poderá ser considerado 'calão', se não respeitar qualquer uma das seguintes condições:"
+
+#: en_US/style.xml:581(para)
+msgid "The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> (<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora.redhat.com/docs/jargon-buster/</ulink>)."
+msgstr "O termo não aparece no <citetitle>Jargon Buster do Fedora</citetitle> (<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora.redhat.com/docs/jargon-buster/</ulink>)."
+
+#: en_US/style.xml:588(para)
+msgid "The term does not appear in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/ </ulink>)."
+msgstr "O termo não aparece no <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/ </ulink>)."
+
+#: en_US/style.xml:596(para)
+msgid "The term does not appear in the glossary of the manual that you are writing."
+msgstr "O termo não aparece no glossário do manual que está a escrever."
+
+#: en_US/style.xml:602(para)
+msgid "The term is not defined in the body text of the manual that you are writing."
+msgstr "O termo não está definido no texto do conteúdo do manual que está a escrever."
+
+#: en_US/style.xml:611(term)
+msgid "Avoid gender-specific language"
+msgstr "Evite a linguagem dependente do sexo"
+
+#: en_US/style.xml:613(para)
+msgid "Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</literal> do not exist. There is no need to identify gender in your instructions."
+msgstr "As construções de pronomes como o <literal>dele/dela</literal> ou <literal>ele/a</literal> não existem. Não existe a necessidade de reflectir o sexo da audiência na suas instruções."
+
+#: en_US/style.xml:621(term)
+msgid "Avoid culture-specific language"
+msgstr "Evite a linguagem específica da cultura"
+
+#: en_US/style.xml:623(para)
+msgid "There is little point in giving an example that everyone in your town knows about, but is a complete mystery to everyone else in the world."
+msgstr "Não vale a pena dar um exemplo que seja conhecido em toda a sua cidade, mas que seja um completo mistério para o resto do mundo."
+
+#: en_US/style.xml:631(term)
+msgid "Avoid talking down to your reader"
+msgstr "Evite rebaixar o seu leitor"
+
+#: en_US/style.xml:633(para)
+msgid "There are few experiences more irritating for a user than documentation that says an action is easy or quick, when in fact the user cannot complete the action. Do not qualify or prejudge actions."
+msgstr "Existem poucas experiências mais irritantes para um utilizador que a documentação que diz que uma determinada acção é fácil ou rápida, quando o utilizador não consegue desempenhá-la de facto. Não qualifique ou faça juízos de valor das acções."
+
+#: en_US/style.xml:642(para)
+msgid "Other parts of this guide discuss in more detail tone and language usage that can cause offense."
+msgstr "Outras partes deste guia descrevem com mais detalhe o tom e linguagem que possam ser considerados ofensivos."
+
+#: en_US/style.xml:653(title)
+msgid "Grammar and Usage Guidelines"
+msgstr "Recomendações de Gramática e Utilização"
+
+#: en_US/style.xml:656(title)
+msgid "Bibliographical Information"
+msgstr "Informação Bibliográfica"
+
+#: en_US/style.xml:657(para)
+msgid "This section is drawn partly from the <citetitle>GDSG</citetitle>, and partly from <citetitle>The Elements of Style</citetitle>, updated as necessary for the needs of 21st-century technical documentation writers."
+msgstr "Esta secção é retirada em parte da <citetitle>GDSG</citetitle> e também em parte do documento <citetitle>The Elements of Style</citetitle>, actualizado de acordo com as necessidades dos escritores de documentação técnica do século XXI."
+
+#. FIXME: Again, check attribution viz. GNU FDL. This will be more work
+#. than the previous section.
+#: en_US/style.xml:668(para)
+msgid "This section contains an alphabetical list of grammar and usage guidelines for use in Fedora documentation. Many of these guidelines are only applicable to English-language usage, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr "Esta secção contém uma lista alfabética das recomendações de gramática e utilização na documentação do Fedora. Muitas destas recomendações só se aplicam na utilização da língua Inglesa; para mais informações, consulte o <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) e o <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+
+#: en_US/style.xml:679(term)
+msgid "Abbreviations"
+msgstr "Abreviaturas"
+
+#: en_US/style.xml:681(para)
+msgid "A shortened form of a word or phrase that takes the place of the full word or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, <literal>p.m.</literal>, and so on. Apply the following rules when you use abbreviations:"
+msgstr "Uma forma resumida de uma palavra ou frase que toma o lugar da palavra ou frase completa, como por exemplo <literal>Dr.</literal>, <literal>a.m.</literal>, <literal>p.m.</literal>, e assim por diante. Aplique as seguintes regras quando usar abreviaturas:"
+
+#: en_US/style.xml:689(para)
+msgid "Avoid creating new abbreviations. Unfamiliar abbreviations can confuse rather than clarify a concept."
+msgstr "Evite a criação de novas abreviaturas. As abreviaturas pouco familiares poderão confundir mais um conceito que clarificar."
+
+#: en_US/style.xml:695(para)
+msgid "Do not explain or expand familiar abbreviations."
+msgstr "Não explique ou expanda as abreviaturas conhecidas."
+
+#: en_US/style.xml:700(para)
+msgid "Do not include familiar abbreviations in the glossary of your manual."
+msgstr "Não inclua as abreviaturas conhecidas no glossário do seu manual."
+
+#: en_US/style.xml:706(para)
+msgid "For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other words\" and <literal>e.g.</literal> for \"for example\", do not use the abbreviation. Spell out the entire phrase."
+msgstr "Para as abreviaturas das frases, como o <literal>i.e.</literal> para \"isto é\" e o <literal>p.ex.</literal> como \"por exemplo\", não use a abreviatura. Descreva a frase por inteiro."
+
+#: en_US/style.xml:715(term)
+msgid "Adjectives"
+msgstr "Adjectivos"
+
+#: en_US/style.xml:717(para)
+msgid "Use adjectives with caution. If an adjective is necessary to differentiate between items, then use adjectives. In all cases, test whether the phrase can stand alone without the adjective."
+msgstr "Use os adjectivos com cuidado. Se um adjectivo for necessário para diferenciar itens, então use os adjectivos. Em qualquer um dos casos, este se a frase poderá ficar bem sem o adjectivo."
+
+#: en_US/style.xml:726(term)
+msgid "Acronyms"
+msgstr "Acrónimos"
+
+#: en_US/style.xml:728(para)
+msgid "A term that represents a multi-word term. Typically, acronyms are formed in the following ways:"
+msgstr "Um termo que representa um conjunto de palavras. Tipicamente, os acrónimos são formados da seguinte forma:"
+
+#: en_US/style.xml:734(para)
+msgid "From the first letters of each word in a compound term, for example Table of Contents (TOC)."
+msgstr "Das primeiras letras de cada palavra num termo composto. Por exemplo, TOC significa 'Table of Contents' (Índice Analítico)."
+
+#: en_US/style.xml:740(para)
+msgid "From recognizable parts of a compound term, such as GNU Object Model Environment (GNOME)."
+msgstr "A partir de partes reconhecíveis de um termo composto, como o GNU Object Model Environment (GNOME)."
+
+#: en_US/style.xml:746(para)
+msgid "Apply the following rules when you use acronyms:"
+msgstr "Aplique as seguintes regras quando usar acrónimos:"
+
+#: en_US/style.xml:751(para)
+msgid "On the first occurrence of an acronym, spell out the full term, with the acronym in parentheses."
+msgstr "Na primeira ocorrência de um acrónimo, descreva por completo o termo completo, tendo o acrónimo entre parêntesis."
+
+#: en_US/style.xml:757(para)
+msgid "Do not spell out the full compound for well-known acronyms, unless you think the information is useful for readers."
+msgstr "Não descreva extensivamente o termo completo para os acrónimos conhecidos, a menos que saiba que a informação é útil para os leitores."
+
+#: en_US/style.xml:764(para)
+msgid "Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than clarify a concept."
+msgstr "Evite a criação de novos acrónimos. Os acrónimos não conhecidos poderão confundir mais um conceito que clarificá-lo."
+
+#: en_US/style.xml:770(para)
+msgid "Write the acronym in uppercase letters, unless there is a compelling case for lowercase."
+msgstr "Escreva o acrónimo em maiúsculas, a não ser que haja um caso explícito para o uso de minúsculas."
+
+#: en_US/style.xml:776(para)
+msgid "Include the acronym and the full term in the glossary of your manual."
+msgstr "Inclua o acrónimo e o termo completo no glossário do seu manual."
+
+#: en_US/style.xml:785(term)
+msgid "Adverbs"
+msgstr "Advérbios"
+
+#: en_US/style.xml:787(para)
+msgid "Use adverbs with caution. If an adverb is necessary to qualify the function of a component, then use an adverb. In all cases, test whether the phrase can stand alone without the adverb. Classic superfluous adverbs <literal>simply</literal>, <literal>easily</literal>, <literal>quickly</literal>."
+msgstr "Use os advérbios com cuidado. Se for necessário um advérbio para qualificar a função de um componente, então use um advérbio. Em qualquer dos casos, teste se a frase pode ser usada sem o advérbio. Alguns exemplos de advérbios supérfluos são o <literal>simplesmente</literal>, <literal>facilmente</literal>, <literal>rapidamente</literal>."
+
+#: en_US/style.xml:798(term)
+msgid "Anthropomorphism"
+msgstr "Antropomorfismo"
+
+#: en_US/style.xml:802(para)
+msgid "Do not apply emotions, desires, or opinions to software applications."
+msgstr "Não aplique emoções, desejos ou opiniões nas aplicações informáticas."
+
+#: en_US/style.xml:808(para)
+msgid "Do not apply a sense of location or dimension to a software application. A user can not be \"in\" a text editor."
+msgstr "Não aplique um sentido de localização ou dimensão a uma aplicação informática. Um utilizador não pode estar \"dentro\" de um editor de texto."
+
+#: en_US/style.xml:818(term)
+msgid "Articles"
+msgstr "Artigos"
+
+#: en_US/style.xml:820(para)
+msgid "Do not use the definite article <literal>the</literal> to begin any of the following items:"
+msgstr "Não use o artigo definido <literal>the</literal> (o/a) para iniciar um dos seguintes itens (nota específica do Inglês):"
+
+#: en_US/style.xml:826(para)
+msgid "Manual titles"
+msgstr "Títulos de manuais"
+
+#: en_US/style.xml:831(para)
+msgid "Chapter titles"
+msgstr "Títulos de capítulos"
+
+#: en_US/style.xml:836(para)
+#: en_US/style.xml:1239(term)
+msgid "Headings"
+msgstr "Destaques"
+
+#: en_US/style.xml:841(para)
+msgid "Figure captions"
+msgstr "Títulos de figuras"
+
+#: en_US/style.xml:846(para)
+msgid "Table captions"
+msgstr "Títulos de tabelas"
+
+#: en_US/style.xml:851(para)
+msgid "Callouts"
+msgstr "Chamadas de atenção"
+
+#: en_US/style.xml:859(term)
+msgid "Apostrophe"
+msgstr "Apóstrofo"
+
+#: en_US/style.xml:861(para)
+msgid "Do not use apostrophes except where absolutely required"
+msgstr "Não use apóstrofos, excepto se for absolutamente necessário"
+
+#: en_US/style.xml:866(para)
+msgid "Do not use apostrophes to denote possession."
+msgstr "Não use apóstrofos para denotar a pertença (específico do Inglês)."
+
+#: en_US/style.xml:871(para)
+msgid "Do not use apostrophes to denote contractions."
+msgstr "Não use os apóstrofos para demarcar as contracções."
+
+#: en_US/style.xml:876(para)
+msgid "Do not use apostrophes to denote plurals."
+msgstr "Não use os apóstrofos para denotar formas plurais."
+
+#: en_US/style.xml:882(title)
+msgid "Incorrect: Apostrophes"
+msgstr "Incorrecto: Apóstrofos"
+
+#: en_US/style.xml:885(para)
+msgid "the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+msgstr "<guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> (opção Ajuda do Menu Principal)"
+
+#: en_US/style.xml:891(para)
+msgid "don't use the default option"
+msgstr "'don't use the default option': não usar a opção predefinida"
+
+#: en_US/style.xml:896(para)
+msgid "several SCSI disk's"
+msgstr "SCSI disk's (discos SCSI)"
+
+#: en_US/style.xml:903(title)
+msgid "Correct: No apostrophes"
+msgstr "Correcto: Sem apóstrofos"
+
+#: en_US/style.xml:906(para)
+msgid "the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</guimenu>"
+msgstr "the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</guimenu> (a opção Ajuda no Menu Principal)"
+
+#: en_US/style.xml:912(para)
+msgid "do not use the default option"
+msgstr "do not use the default option"
+
+#: en_US/style.xml:917(para)
+msgid "several SCSI disks"
+msgstr "SCSI disks"
+
+#: en_US/style.xml:926(term)
+msgid "Brackets"
+msgstr "Parêntesis Rectos"
+
+#: en_US/style.xml:930(para)
+msgid "Do not use brackets [such as these] as a substitute for parentheses (such as these)."
+msgstr "Não use parêntesis [deste tipo] como substituição dos parêntesis (deste tipo)."
+
+#: en_US/style.xml:936(para)
+msgid "Use brackets for optional command line entries."
+msgstr "Use os parêntesis rectos para os itens opcionais da linha de comandos."
+
+#: en_US/style.xml:941(para)
+msgid "Do not use angle brackets to indicate variables in text, instead use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+msgstr "Não use os símbolos '<' e '>' para indicar as variáveis no texto; em vez disso, use a marca <sgmltag class=\"starttag\">replaceable</sgmltag>. Veja a utilização do <xref linkend=\"sn-xml-tags-replaceable\"/> para mais informações sobre a utilização desta marca."
+
+#: en_US/style.xml:953(term)
+msgid "Capitalization"
+msgstr "Capitalização (Uso de maiúsculas/minúsculas)"
+
+#: en_US/style.xml:955(para)
+msgid "Capitalize in the following situations:"
+msgstr "Aplique a capitalização nas seguintes situações:"
+
+#: en_US/style.xml:960(para)
+msgid "All letters in acronyms, unless the acronym is a well-known exception"
+msgstr "Todas as letras dos acrónimos, a menos que o acrónimo seja uma excepção conhecida"
+
+#: en_US/style.xml:966(para)
+msgid "Initial letter of the first word in a list"
+msgstr "A letra inicial da primeira palavra de uma lista"
+
+#: en_US/style.xml:971(para)
+msgid "Initial letter of the first word in a callout"
+msgstr "A letra inicial da primeira palavra de uma chamada de atenção"
+
+#: en_US/style.xml:976(para)
+msgid "Initial letter of a key name, such as the <keycap>Shift</keycap> key"
+msgstr "A letra inicial do nome de uma tecla, como a tecla <keycap>Shift</keycap>"
+
+#: en_US/style.xml:982(para)
+msgid "Initial letter of a sentence"
+msgstr "A letra inicial de uma frase"
+
+#: en_US/style.xml:986(title)
+msgid "Command Names"
+msgstr "Nomes de Comandos"
+
+#: en_US/style.xml:987(para)
+msgid "Avoid starting a sentence with a command name or application name that has a lowercase initial letter."
+msgstr "Evite começar uma frase com o nome de um comando ou aplicação que tenha um nome que começa por minúsculas."
+
+#: en_US/style.xml:994(para)
+msgid "Initial letter of a complete sentence after a colon"
+msgstr "A letra inicial de uma frase completa, a seguir aos dois-pontos"
+
+#: en_US/style.xml:999(para)
+msgid "Do not capitalize in the following situations:"
+msgstr "Não capitalizar nas seguintes situações:"
+
+#: en_US/style.xml:1004(para)
+msgid "A compound term that is followed by an abbreviation or an acronym"
+msgstr "Um termo composto que seja seguido de uma abreviatura ou acrónimo"
+
+#: en_US/style.xml:1010(para)
+msgid "When you want to emphasize something"
+msgstr "Quando quiser aumentar a ênfase sobre algo"
+
+#: en_US/style.xml:1015(para)
+msgid "Variable names"
+msgstr "Nomes de variáveis"
+
+#: en_US/style.xml:1020(para)
+msgid "The initial letter of an incomplete sentence after a colon"
+msgstr "A letra inicial de uma frase incompleta, após os dois-pontos"
+
+#: en_US/style.xml:1029(term)
+msgid "Captions"
+msgstr "Legendas"
+
+#: en_US/style.xml:1031(para)
+msgid "Use the same rules as for headings, for all captions accompanying figures and tables. Do not put a period at the end of a caption."
+msgstr "Use as mesmas regras dos destaques para todas as legendas das tabelas e figuras. Não coloque um ponto no fim de uma legenda."
+
+#: en_US/style.xml:1039(term)
+msgid "Colon"
+msgstr "Dois-Pontos (:)"
+
+#: en_US/style.xml:1041(para)
+msgid "Use a colon in the following situations:"
+msgstr "Use os dois-pontos nas seguintes situações:"
+
+#: en_US/style.xml:1046(para)
+msgid "To introduce a list"
+msgstr "Para introduzir uma lista"
+
+#: en_US/style.xml:1051(para)
+msgid "Before an explanation"
+msgstr "Antes de uma explicação"
+
+#: en_US/style.xml:1056(para)
+msgid "After an introduction"
+msgstr "Após uma introdução"
+
+#: en_US/style.xml:1061(para)
+msgid "Do not use a colon in the following situations:"
+msgstr "Não use os dois-pontos nas seguintes situações:"
+
+#: en_US/style.xml:1066(para)
+msgid "To introduce a figure or a table"
+msgstr "Para introduzir uma figura ou uma tabela"
+
+#: en_US/style.xml:1071(para)
+msgid "To introduce headings"
+msgstr "Para introduzir os destaques"
+
+#: en_US/style.xml:1076(para)
+msgid "At the end of an introduction to a procedure"
+msgstr "No fim da introdução de um procedimento"
+
+#: en_US/style.xml:1084(term)
+msgid "Column headings"
+msgstr "Destaques das colunas"
+
+#: en_US/style.xml:1086(para)
+msgid "Use the same rules as for headings."
+msgstr "Use as mesmas regras dos destaques."
+
+#: en_US/style.xml:1092(term)
+msgid "Comma"
+msgstr "Vírgula"
+
+#: en_US/style.xml:1094(para)
+msgid "Use commas in the following situations:"
+msgstr "Use as vírgulas nas seguintes situações:"
+
+#: en_US/style.xml:1099(para)
+msgid "To separate items in a series"
+msgstr "Para separar os itens de uma dada série"
+
+#: en_US/style.xml:1104(para)
+msgid "To separate the parts of a sentence"
+msgstr "Para separar as partes de uma frase"
+
+#: en_US/style.xml:1109(para)
+msgid "To separate nonrestrictive phrases"
+msgstr "Para separar as frases não-restritivas"
+
+#: en_US/style.xml:1114(para)
+msgid "Instead of dashes to set off appositives"
+msgstr "Em vez dos hífenes, para definir apositivos"
+
+#: en_US/style.xml:1119(para)
+msgid "With <emphasis>for example</emphasis> and similar expressions"
+msgstr "Com as expressões <emphasis>por exemplo</emphasis> e similares"
+
+#: en_US/style.xml:1125(para)
+msgid "Do not use commas in the following situations:"
+msgstr "Não use as vírgulas nas seguintes situações:"
+
+#: en_US/style.xml:1130(para)
+msgid "In a series of adjectives used as one modifier"
+msgstr "Numa série de adjectivos usados como um modificador único"
+
+#: en_US/style.xml:1135(para)
+msgid "Between two short independent clauses"
+msgstr "Entre duas cláusulas breves e independentes"
+
+#: en_US/style.xml:1143(term)
+#: en_US/emacs-nxml.xml:86(title)
+msgid "Commands"
+msgstr "Comandos"
+
+#: en_US/style.xml:1145(para)
+msgid "Do not use commands as verbs."
+msgstr "Não use os comandos como verbos."
+
+#: en_US/style.xml:1151(term)
+msgid "Contractions"
+msgstr "Contracções"
+
+#: en_US/style.xml:1153(para)
+msgid "Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</emphasis>, or <emphasis>isn't</emphasis>."
+msgstr "Não use contracções do tipo <emphasis>tá</emphasis>, <emphasis>tar</emphasis>, or <emphasis>né</emphasis>."
+
+#: en_US/style.xml:1160(term)
+msgid "Dash"
+msgstr "Hífen"
+
+#: en_US/style.xml:1162(para)
+msgid "Do not use the em dash or the en dash. Use a paragraph break or a colon instead, where you want to create an introductory piece of text. If you have several items that you want to introduce, then you can use a variable list."
+msgstr "Não use o hífen 'mdash' ou 'ndash'. Use uma quebra de parágrafo ou os dois-pontos em alternativa onde pretender criar um pedaço introdutório de texto. Se tiver vários itens que deseja introduzir, então poderá usar uma lista variável."
+
+#: en_US/style.xml:1171(term)
+msgid "Ellipsis"
+msgstr "Reticências"
+
+#: en_US/style.xml:1173(para)
+msgid "Use an ellipsis in the following situations:"
+msgstr "Use as reticências nas seguintes situações:"
+
+#: en_US/style.xml:1178(para)
+msgid "To show that you have omitted something from a sentence"
+msgstr "Para mostrar que omitiu algo de uma frase"
+
+#: en_US/style.xml:1183(para)
+msgid "To indicate a pause when you quote displayed text"
+msgstr "Para indicar uma pausa quando fizer uma citação do texto apresentado"
+
+#: en_US/style.xml:1191(term)
+msgid "Fractions"
+msgstr "Fracções"
+
+#: en_US/style.xml:1193(para)
+msgid "Follow these rules when using fractions:"
+msgstr "Siga estas regras quando usar as fracções:"
+
+#: en_US/style.xml:1198(para)
+msgid "Use numerals for fractions in tables and in units of measurement, but spell out fractions in prose."
+msgstr "Use numerais para as fracções nas tabelas e nas unidades de medida, mas descreva por extenso as fracções."
+
+#: en_US/style.xml:1204(para)
+msgid "Use a space between a numeral and a related fraction, if there is a possible ambiguity. For example: 1 1/2 instead of 11/2."
+msgstr "Use um espaço entre um numeral e uma fracção relacionada, se puder existir alguma ambiguidadde. Por exemplo: 1 1/2 em vez de 11/2."
+
+#: en_US/style.xml:1211(para)
+msgid "If a fraction is used in a compound modifier, insert a hyphen between the fraction and the unit of measurement."
+msgstr "Se uma fracção for usada num modificador composto, indique um hífen entre a fracção e a unidade de medida."
+
+#: en_US/style.xml:1220(term)
+msgid "Gender"
+msgstr "Género"
+
+#: en_US/style.xml:1222(para)
+msgid "Refer to <xref linkend=\"sn-fundamentals-9\"/>."
+msgstr "Veja em <xref linkend=\"sn-fundamentals-9\"/>."
+
+#: en_US/style.xml:1228(term)
+msgid "Grammar"
+msgstr "Gramática"
+
+#: en_US/style.xml:1230(para)
+msgid "Use standard American English grammar rules, refer to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr "Use as regras-padrão do Inglês Americano (para documentos em Inglês); veja em <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+
+#: en_US/style.xml:1241(para)
+msgid "Use the following capitalization rules in headings:"
+msgstr "Use as seguintes regras de capitalização nos destaques:"
+
+#: en_US/style.xml:1246(para)
+msgid "Initial uppercase letter of the first word"
+msgstr "Letra maiúscula inicial da primeira palavra"
+
+#: en_US/style.xml:1251(para)
+msgid "Initial uppercase letter for all nouns, adjectives, and verbs."
+msgstr "Letra maiúscula inicial para todos os substantivos, adjectivos e verbos."
+
+#: en_US/style.xml:1257(para)
+msgid "All lowercase letters for conjunctions, articles, and prepositions of fewer than four letters"
+msgstr "Todas as letras em minúsculas para as conjunções, artigos e proposições com menos de quatro letras"
+
+#: en_US/style.xml:1263(para)
+msgid "Initial uppercase letter for prepositions of four letters or longer"
+msgstr "Letra maiúscula inicial para as proposições com quatro ou mais letras"
+
+#: en_US/style.xml:1269(para)
+msgid "Initial uppercase letter for conjunctions of four letters or longer"
+msgstr "Letra maiúscula inicial para as conjunções com quatro ou mais letras"
+
+#: en_US/style.xml:1280(term)
+msgid "Hyphen"
+msgstr "Hífen"
+
+#: en_US/style.xml:1282(para)
+msgid "Use hyphens in the following situations:"
+msgstr "Use os hífenes nas seguintes situações:"
+
+#: en_US/style.xml:1287(para)
+msgid "With a numeral in a compound modifier"
+msgstr "Com um numeral num modificador composto"
+
+#: en_US/style.xml:1291(para)
+msgid "To prevent ambiguity"
+msgstr "Para evitar ambiguidades"
+
+#: en_US/style.xml:1296(para)
+msgid "With some standard prefixes and suffixes. Use the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidance"
+msgstr "Com alguns prefixos e sufixos padrão. Use o <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) para ter algumas linhas-guia"
+
+#: en_US/style.xml:1305(para)
+msgid "In spelled-out fractions"
+msgstr "Nas fracções por extenso"
+
+#: en_US/style.xml:1310(para)
+msgid "In variable names of two or more words, such as <replaceable>directory-name</replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+msgstr "Nos nomes de variáveis com duas ou mais palavras, como o <replaceable>nome-pasta</replaceable>. Nota: <replaceable>filename</replaceable> (nome de ficheiro) é uma excepção."
+
+#: en_US/style.xml:1317(para)
+msgid "Do not use hyphens in the following situations:"
+msgstr "Não use hífenes nas seguintes situações:"
+
+#: en_US/style.xml:1322(para)
+msgid "For industry-accepted terms"
+msgstr "Para os termos aceites na indústria"
+
+#: en_US/style.xml:1327(para)
+msgid "To construct verbs"
+msgstr "Para construir verbos (excepto nos compostos)"
+
+#: en_US/style.xml:1332(para)
+msgid "With an adverb ending in <emphasis>ly</emphasis>"
+msgstr "Com um advérbio terminado em <emphasis>mente</emphasis>"
+
+#: en_US/style.xml:1337(para)
+msgid "With numerals as single modifiers"
+msgstr "Com os numerais como modificadores únicos"
+
+#: en_US/style.xml:1342(para)
+msgid "With a word that is listed as unhyphenated in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+msgstr "Com uma palavra que aparece como não-hifenizada no <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) e que use um prefixo comum"
+
+#: en_US/style.xml:1351(para)
+msgid "With trademarked terms"
+msgstr "Com termos de marcas registadas"
+
+#: en_US/style.xml:1359(term)
+msgid "Latin terms"
+msgstr "Termos em Latim"
+
+#: en_US/style.xml:1361(para)
+msgid "Do not use Latin terms. Use an equivalent English term instead."
+msgstr "Não use termos em Latim. Tente usar um termo em Inglês, em alternativa."
+
+#: en_US/style.xml:1368(term)
+msgid "Like"
+msgstr "Do Tipo"
+
+#: en_US/style.xml:1370(para)
+msgid "Do not use the term <emphasis>like</emphasis> to denote equivalence or similarity."
+msgstr "Não use o <emphasis>do tipo</emphasis> para demarcar uma equivalência ou semelhança."
+
+#: en_US/style.xml:1377(term)
+msgid "Lists"
+msgstr "Listas"
+
+#: en_US/style.xml:1379(para)
+msgid "Introduce a list with a complete sentence that ends with a colon."
+msgstr "Introduza uma lista com uma frase completa que termine com dois-pontos."
+
+#: en_US/style.xml:1386(term)
+msgid "Numbers"
+msgstr "Números"
+
+#: en_US/style.xml:1388(para)
+msgid "Spell out numbers in the following situations:"
+msgstr "Diga os números por extenso nas seguintes situações:"
+
+#: en_US/style.xml:1393(para)
+msgid "Numbers from zero through nine unless the number is part of a measurement"
+msgstr "Números de zero a nove, a menos que o número faça parte de uma medida"
+
+#: en_US/style.xml:1398(para)
+msgid "Approximations"
+msgstr "Aproximações"
+
+#: en_US/style.xml:1403(para)
+msgid "Extreme values such as <emphasis>million</emphasis>, but precede the value with a numeral"
+msgstr "Valores extremos como o <emphasis>milhão</emphasis>, se bem que pode anteceder o valor com um numeral"
+
+#: en_US/style.xml:1409(para)
+msgid "Any number that begins a sentence"
+msgstr "Qualquer número que inicie uma frase"
+
+#: en_US/style.xml:1414(para)
+msgid "A number that is immediately followed by a numeral, for example: <literal>two 10 MB files</literal>"
+msgstr "Um número que seja seguido imediatamente de um numeral, como por exemplo: <literal>dois ficheiros de 10 MB</literal>"
+
+#: en_US/style.xml:1423(term)
+msgid "Numerals"
+msgstr "Numerais"
+
+#: en_US/style.xml:1425(para)
+msgid "Use numerals in the following situations:"
+msgstr "Use os numerais (em oposição aos números por extenso) nas seguintes situações:"
+
+#: en_US/style.xml:1430(para)
+msgid "The number 10 or greater"
+msgstr "O número 10 ou superior"
+
+#: en_US/style.xml:1435(para)
+msgid "Negative numbers"
+msgstr "Números negativos"
+
+#: en_US/style.xml:1439(para)
+msgid "Most fractions"
+msgstr "A maioria das fracções"
+
+#: en_US/style.xml:1444(para)
+msgid "Percentages"
+msgstr "Percentagens"
+
+#: en_US/style.xml:1449(para)
+msgid "Decimals"
+msgstr "Casas decimais"
+
+#: en_US/style.xml:1454(para)
+msgid "Measurements"
+msgstr "Medidas"
+
+#: en_US/style.xml:1459(para)
+msgid "Units of time smaller than one second"
+msgstr "Unidades de tempo inferiores ao segundo"
+
+#: en_US/style.xml:1464(para)
+msgid "References to bits and bytes"
+msgstr "Referências a 'bits' e 'bytes'"
+
+#: en_US/style.xml:1472(term)
+msgid "Parentheses"
+msgstr "Parêntesis"
+
+#: en_US/style.xml:1474(para)
+msgid "Use parentheses in the following situations:"
+msgstr "Use os parêntesis nas seguintes situações:"
+
+#: en_US/style.xml:1479(para)
+msgid "To contain the abbreviation of a term on the first occurrence of the full term"
+msgstr "Para conter a abreviatura de um termo na primeira ocorrência do termo completo"
+
+#: en_US/style.xml:1485(para)
+msgid "In man page references, specifically the section number"
+msgstr "Nas referências a páginas do 'man', especificamente no número da secção"
+
+#: en_US/style.xml:1493(term)
+msgid "Period"
+msgstr "Ponto final"
+
+#: en_US/style.xml:1495(para)
+msgid "Use a period in the following situations:"
+msgstr "Use um ponto final nas seguintes situações:"
+
+#: en_US/style.xml:1500(para)
+msgid "To end a sentence"
+msgstr "Para terminar uma frase"
+
+#: en_US/style.xml:1505(para)
+msgid "In file and directory names"
+msgstr "Nos nomes dos ficheiros e pastas"
+
+#: en_US/style.xml:1510(para)
+msgid "In abbreviations that can be mistaken for words, such as a.m. and U.S."
+msgstr "Nas abreviaturas que possam ser confundidas com palavras, como por exemplo C.O.M., E.U."
+
+#: en_US/style.xml:1519(term)
+msgid "Punctuation"
+msgstr "Pontuação"
+
+#: en_US/style.xml:1521(para)
+msgid "Use standard American English punctuation rules. In addition to the specific points of punctuation in this section, refer also to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr "Use as regras de pontuação normais do Inglês Americano. Para além dos sinais de pontuação específicos nesta secção, veja também no <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+
+#: en_US/style.xml:1531(term)
+msgid "Punctuation in numbers"
+msgstr "Pontuação nos números"
+
+#: en_US/style.xml:1533(para)
+msgid "Do not use a comma in numerals of four digits. Use a comma in numerals of more than four digits."
+msgstr "Não use um ponto nos numerais de quatro algarismos. Use o ponto nos numerais com mais de quatro algarismos."
+
+#: en_US/style.xml:1540(term)
+msgid "Quotation marks"
+msgstr "Marcas de citações"
+
+#: en_US/style.xml:1542(para)
+msgid "Use quotation marks to indicate material that is taken verbatim from another source. Do not use quotation marks to excuse terms from legitimacy. If the term is not legitimate, then use another term. If you must use that term, declare the term in the glossary and make the term legitimate."
+msgstr "Use as marcas de citação (plicas, aspas) para indicar o material que foi explicitamente retirado de outra fonte. Não use as aspas para retirar a legitimidade dos termos. Se o termo não for legítimo, então use outro termo. Se precisar de usar esse termo, declare-o no glossário e torne-o legítimo."
+
+#: en_US/style.xml:1553(term)
+msgid "See v. Refer to"
+msgstr "'Veja' vs. 'Consulte'"
+
+#: en_US/style.xml:1555(para)
+msgid "When referring a user to another resource, use \"refer to\" instead of \"see\", and \"refer also to\" instead of \"see also\". This differentiates from the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag\">seealso</sgmltag> tags that are used in indexing. These tags create special links in the index. To be consistent throughout the document, we reserve the special words \"see\" and \"see also\" for hyperlinked index references, and use \"refer to\" and \"refer also to\" for non-hyperlinked and non-indexed references."
+msgstr "Ao referenciar um outro recurso, use o \"consulte\" em vez do \"veja\", ou então \"consulte também\" em vez de \"veja também\". Isto cria uma separação em relação às marcas <sgmltag class=\"starttag\">see</sgmltag> e <sgmltag class=\"starttag\">seealso</sgmltag>, as quais são usadas na indexação. Estas marcas criam referências especiais no índice. Para ser consistente ao longo do tempo, reservam-se as palavras especiais \"ver\" e \"ver também\" para o caso das referências com hiperligações, sendo que existe o \"consultar\" e o \"consultar também\" para o caso das referências não-ligadas e não-indexadas."
+
+#: en_US/style.xml:1570(term)
+msgid "Semicolon"
+msgstr "Ponto-e-vírgula"
+
+#: en_US/style.xml:1572(para)
+msgid "Do not use semicolons."
+msgstr "Não use pontos-e-vírgulas."
+
+#: en_US/style.xml:1578(term)
+msgid "Slash"
+msgstr "Barra"
+
+#: en_US/style.xml:1580(para)
+msgid "Except where required as part of a filename, do not use slashes \"/\" in your writing. The construction <literal>and/or</literal>, for example, does not exist. Use one or the other term instead."
+msgstr "Excepto no caso de ser necessário como parte do nome de um ficheiro, não use as barras \"/\" na sua escrita. A construção <literal>e/ou</literal>, por exemplo, não existe. Use um termo ou o outro, em alternativa."
+
+#: en_US/style.xml:1589(term)
+msgid "Spelling"
+msgstr "Ortografia"
+
+#: en_US/style.xml:1591(para)
+msgid "Use standard American English spelling rules, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+msgstr "Use as regras-padrão ortográficas do Inglês Americano; consulte o <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) para obter mais informações."
+
+#: en_US/style.xml:1600(term)
+msgid "Titles"
+msgstr "Títulos"
+
+#: en_US/style.xml:1602(para)
+msgid "For manual titles use the same rules as for headings."
+msgstr "Para os títulos manuais, use as mesmas regras dos destaques."
+
+#: en_US/style.xml:1608(term)
+msgid "Units"
+msgstr "Unidades"
+
+#: en_US/style.xml:1610(para)
+msgid "Follow these rules when using units:"
+msgstr "Siga estas regras ao usar unidades:"
+
+#: en_US/style.xml:1615(para)
+msgid "Use standard abbreviations for units of measurements, do not invent your own abbreviations."
+msgstr "Use as abreviaturas-padrão para as unidades de medida, não invente as suas próprias."
+
+#: en_US/style.xml:1621(para)
+msgid "For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of Electrical and Electronics Terms</citetitle>."
+msgstr "Para mais informações, veja em <citetitle>IEEE Standard Dictionary of Electrical and Electronics Terms</citetitle>."
+
+#: en_US/style.xml:1630(para)
+msgid "Use periods for abbreviated units that might be mistaken for a word."
+msgstr "Use pontos nas unidades abreviadas que possam ser confundidas com palavras."
+
+#: en_US/style.xml:1636(para)
+msgid "Most standard abbreviations of units account for both singular and plural usage."
+msgstr "A maior parte das abreviaturas-padrão das unidades têm em conta a utilização singular e plural."
+
+#: en_US/style.xml:1642(para)
+msgid "Insert a space between the numeral and the unit of measurement."
+msgstr "Indique um espaço entre o numeral e a unidade de medida."
+
+#: en_US/style.xml:1656(title)
+msgid "Composition Tips"
+msgstr "Sugestões de Composição"
+
+#. This section will collect miscellanea and advice for specific
+#. situations that the FDP editors encounter. I hope they will feel
+#. free to e-mail me sticky situations or particularly interesting
+#. examples of work they've beautified. Hopefully not too much will be
+#. drawn from my own work! - PWF.
+#: en_US/style.xml:1668(para)
+msgid "This section contains usage tips based on situations the Fedora Documentation Project editors have encountered in the past. You should read and understand these examples to improve your own documentation. The Fedora Documentation Project editors welcome additional examples."
+msgstr "Esta secção contém sugestões de utilização que se baseiam nas situações que os editores do Projecto de Documentação do Fedora encontraram no passado. Deverá ler e compreender estes exemplos para melhorar a sua própria documentação. Os editores do Projecto de Documentação do Fedora agradecem os exemplos adicionais."
+
+#: en_US/style.xml:1676(title)
+msgid "Active Voice"
+msgstr "Voz Activa"
+
+#: en_US/style.xml:1677(para)
+msgid "Always use active voice, except when it is awkward to do so. The tutorial tells the user how to accomplish a task, and should give instructions clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. These words are redundant in a tutorial, since the reader assumes you are outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" \"might,\" and other words that indicate you are unsure about the subject matter. Your tutorial should cover a subject authoritatively. The reader should never be concerned about unknown effects of following the tutorial."
+msgstr "Use sempre a voz activa, excepto se ficar estranha a sua utilização num determinado contexto. O tutorial diz ao utilizador como desempenhar uma tarefa, devendo dar as instruções de forma clara e concisa. Evite usar os termos \"dever\", \"ser necessário\", entre outros. Estas palavras são redundantes num tutorial, dado que o leitor assume que você já está a destacar os passos necessários para efectuar uma tarefa. Evite também usar os termos \"talvez\", \"poderá\" e outras palavras que indiquem que não tenha a certeza sobre a matéria em estudo. O seu tutorial deverá cobrir um assunto de forma autoritária. O leitor nunca se deverá preocupar com os efeitos desconhecidos de seguir o tutorial."
+
+#: en_US/style.xml:1690(title)
+msgid "Incorrect: Passive voice"
+msgstr "Incorrecto: Voz passiva"
+
+#: en_US/style.xml:1691(para)
+msgid "The <command>yum update</command> command must be run."
+msgstr "O comando <command>yum update</command> deverá ser executado."
+
+#: en_US/style.xml:1694(para)
+msgid "You might want to run the <command>yum update</command> command."
+msgstr "Poderá querer executar o comando <command>yum update</command>."
+
+#: en_US/style.xml:1700(title)
+msgid "Correct: Active voice"
+msgstr "Correcto: Voz activa"
+
+#: en_US/style.xml:1701(para)
+msgid "Run the <command>yum update</command> command."
+msgstr "Execute o comando <command>yum update</command>."
+
+#: en_US/style.xml:1708(title)
+msgid "Present Tense"
+msgstr "Tempo Presente"
+
+#: en_US/style.xml:1709(para)
+msgid "Write in the present tense. A good rule of thumb is that the words \"will\" and \"shall\" are almost never needed in describing what the user should do or see. They add unnecessary length to sentences and can confuse translators. They are also often indicators of passive voice; refer also to <xref linkend=\"sn-misc-active-voice\"/>."
+msgstr "Escreva no tempo presente. Uma boa regra de algibeira é que palavras como \"será\" ou \"deverá\" quase nunca são necessárias para descrever o que o utilizador deverá ou fazer. Estas adicionam um tamanho desnecessário às frases e poderão confundir os tradutores. Estas normalmente também são indicações de voz passiva; consule também o tópico <xref linkend=\"sn-misc-active-voice\"/>."
+
+#: en_US/style.xml:1718(title)
+msgid "Incorrect: Future tense"
+msgstr "Incorrecto: Tempo futuro"
+
+#: en_US/style.xml:1719(para)
+msgid "The application will display a list of target files."
+msgstr "A aplicação irá mostrar uma lista dos ficheiros-alvo."
+
+#: en_US/style.xml:1722(para)
+msgid "A list of target files will be displayed by the application."
+msgstr "Uma lista de ficheiros-alvo será apresentada pela aplicação."
+
+#: en_US/style.xml:1727(title)
+msgid "Correct: Present tense"
+msgstr "Correcto: Tempo presente"
+
+#: en_US/style.xml:1728(para)
+msgid "The application displays a list of target files."
+msgstr "A aplicação mostra uma lista dos ficheiros-alvo."
+
+#: en_US/style.xml:1735(title)
+msgid "Narrative Voice"
+msgstr "Voz Narrativa"
+
+#: en_US/style.xml:1736(para)
+msgid "Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself the writer (whether including the reader or not), the Fedora Documentation Project, the Fedora community, or any other group. Do not refer to users with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word \"one.\" It is acceptable to refer to the reader with the second person pronoun \"you.\""
+msgstr "Não use a primeira pessoa \"Eu,\" ou \"nós\" para se referir a si próprio como escritor (quer inclua o leitor quer não), o Projecto de Documentação do Fedora, a comunidade do Fedora ou qualquer outro grupo. Não faça referências aos utilizadores com um pronome na terceira pessoa (\"ele\", \"ela\" ou \"eles/elas\"). É aceitável fazer referências ao leitor na segunda pessoa com o pronome \"você\"."
+
+#: en_US/style.xml:1745(title)
+msgid "Incorrect: First or third person"
+msgstr "Incorrecto: Primeira ou terceira pessoa"
+
+#: en_US/style.xml:1746(para)
+msgid "As described in the last section, I always run <command>up2date</command> before configuring the Samba server."
+msgstr "Como foi descrito na última secção, eu executo sempre o <command>up2date</command> antes de configurar o servidor do Samba."
+
+#: en_US/style.xml:1751(para)
+msgid "If the user needs to back up his or her files, s/he should use the <command>tar</command> or <command>cpio</command> command."
+msgstr "Se o utilizador precisar de salvaguardar os ficheiros dele ou dela, ele/a deverá usar o comando <command>tar</command> ou <command>cpio</command>."
+
+#: en_US/style.xml:1757(title)
+msgid "Correct: Second (or no) person"
+msgstr "Correcto: Segunda pessoa (ou omisso)"
+
+#: en_US/style.xml:1758(para)
+msgid "Refer to the section on <command>up2date</command> before configuring the Samba server."
+msgstr "Veja a secção sobre o <command>up2date</command> antes de configurar o servidor do Samba."
+
+#: en_US/style.xml:1762(para)
+msgid "If necessary, users can back up files with the <command>tar</command> or <command>cpio</command> command."
+msgstr "Se necessário, os utilizadores poderão salvaguardar os ficheiros com o comando <command>tar</command> ou <command>cpio</command>."
+
+#: en_US/style.xml:1770(title)
+msgid "Negative Words"
+msgstr "Palavras pela Negativa"
+
+#: en_US/style.xml:1771(para)
+msgid "Avoid negative words when possible, since they give documentation an overly dogmatic tone. The word \"avoid\" is useful for this purpose. Note that contractions are often used for negative words such as <emphasis>don't</emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-contractions\"/>."
+msgstr "Evite as palavras negativas sempre que possível, dado que atribuem à documentação um carácter dogmático, de certa forma. A palavra \"evitar\" é útil para esse fim. De um modo geral na língua inglesa, as contracções são usadas para as palavras negativas como o <emphasis>don't</emphasis> ou o <emphasis>can't</emphasis>. Consulte a secção <xref linkend=\"vle-contractions\"/>."
+
+#: en_US/style.xml:1782(title)
+msgid "Uncertainty"
+msgstr "Incerteza"
+
+#: en_US/style.xml:1783(para)
+msgid "Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the like. While occasional use of these constructions is acceptable, overuse reduces the authority of your documentation. The documentation should adequately cover a stock installation of Fedora. It is impossible for a tutorial-length document to cover every possible configuration scenario. Address the most common scenarios and note discrepancies only as required."
+msgstr "Evite o uso excessivo do \"tipicamente\", \"normalmente\", \"na maior parte\", \"muitos\", entre outros. Embora seja aceitável um uso ocasional destas conjugações, o uso em ecesso reduz a autoridade da sua documentação. A documentação deverá cobrir de forma adequada uma instalação predefinida do Fedora. É impossível, para um documento com a dimensão de um tutorial, cobrir todos os cenários de configuração possíveis. Analise os cenários mais comuns e aponte apenas as discrepâncias mais necessárias."
+
+#: en_US/style.xml:1795(title)
+msgid "Redundant Coverage"
+msgstr "Cobertura Redundante"
+
+#: en_US/style.xml:1796(para)
+msgid "Avoid covering redundant material, such as how to update a Fedora system. These overarching topics may be covered in other tutorials. Writers frequently violate this guideline because they feel their tutorial is not long enough. Keep your tutorial from wandering off-topic. Instead, refer the reader to a separate tutorial whenever possible for complete coverage of that topic."
+msgstr "Evite a cobertura de material redundante, como a actualização de um sistema Fedora. Estes tópicos mais complicados podem ser cobertos noutros tutoriais. Os escritores violam normalmente esta recomendação por acharem que o seu tutorial não é suficientemente comprido. Mantenha o seu tutorial com o tópico bem definido e sem grandes desvios. Em vez disso, indique ao leitor para consultar um tutorial sparado, sempre que possível, para uma cobertura completa desse tópico."
+
+#: en_US/style.xml:1808(title)
+msgid "Self-referential Value Judgments"
+msgstr "Juízos de Valor com Referências Próprias"
+
+#: en_US/style.xml:1809(para)
+msgid "Avoid statements such as \"One of the most important things to do is <replaceable>XYZ</replaceable>.\" If the procedure is important, the reader already expects it to be in your tutorial. The converse is also true: If a procedure appears in your tutorial, the reader expects it is important. This is especially true if you use a whole section for the procedure in question. Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as required. If the whole section concerns how to do <replaceable>XYZ</replaceable>, leave this sentence out entirely. Refer also to <xref linkend=\"vle-golden-rule-4\"/>."
+msgstr "Evite frases do tipo \"Uma das coisas mais importantes a fazer é <replaceable>XYZ</replaceable>.\" Se o procedimento for importante, o leitor já está à espera dele no seu tutorial. O inverso também se aplica: se um procedimento aparece no seu tutorial, o leitor espera que este seja importante. Isto é particularmente verdadeiro se usar uma secção inteira para o procedimento em questão. Basta dizer, \"Faça <replaceable>XYZ</replaceable>.\". Depois disso, desenvolva de acordo com as necessidades. Se a secção completa disser respeito à forma como fazer <replaceable>XYZ</replaceable>, retire esta frase por inteiro. Consulte também a secção <xref linkend=\"vle-golden-rule-4\"/>."
+
+#: en_US/style.xml:1824(title)
+msgid "Precision of Language"
+msgstr "Precisão da Linguagem"
+
+#: en_US/style.xml:1825(para)
+msgid "Use precise words for actions users should take. Do not instruct users to \"go\" to a selection, or \"find\" a menu."
+msgstr "Use palavras exactas para as acções que os utilizadores deverão efectuar. Não diga aos utilizadores para \"ir\" para uma selecção ou \"procurar\" um menu."
+
+#: en_US/style.xml:1830(title)
+msgid "Incorrect: Imprecise wording"
+msgstr "Incorrecto: Palavras pouco exactas"
+
+#: en_US/style.xml:1833(para)
+msgid "Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</guimenuitem>"
+msgstr "Vá a <guimenu>Menu Principal</guimenu> -> <guimenuitem>XPTO</guimenuitem>"
+
+#: en_US/style.xml:1839(para)
+msgid "Find the option labeled <guilabel>Search</guilabel>"
+msgstr "Descubra a opção <guilabel>Procurar</guilabel>"
+
+#: en_US/style.xml:1846(title)
+msgid "Correct: Precise wording"
+msgstr "Correcto: Frases exactas"
+
+#: en_US/style.xml:1849(para)
+msgid "From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</guimenuitem>"
+msgstr "No <guimenu>Menu Principal</guimenu>, seleccione o <guimenuitem>XPTO</guimenuitem>"
+
+#: en_US/style.xml:1855(para)
+msgid "Select the <guilabel>Search</guilabel> option"
+msgstr "Seleccione a opção <guilabel>Procurar</guilabel>"
+
+#: en_US/style.xml:1862(title)
+msgid "Do Not Discriminate Against Non-GUI Users"
+msgstr "Não Discrimine em Relação aos Utilizadores Não-Gráficos"
+
+#: en_US/style.xml:1863(para)
+msgid "If you are writing about a GUI-only application, you may use \"click\" freely. If you are writing about an application that has a text-mode interface, use \"select\" instead as shown above."
+msgstr "Se estiver a escrever a escrever sobre uma aplicação somente gráfica, poderá usar o termo \"carregar\" ou \"clicar\" à vontade. Se estiver a escrever acerca de uma aplicação que também tem uma interface em modo texto, use o \"seleccionar\" como aparece acima."
+
+#: en_US/style.xml:1874(title)
+msgid "DocBook Tips"
+msgstr "Sugestões do DocBook"
+
+#: en_US/style.xml:1875(para)
+msgid "This section contains tips on how to use DocBook tags more effectively in your documentation."
+msgstr "Esta secção contém sugestões sobre a utilização mais eficiente da marcas de DocBook na sua documentação."
+
+#: en_US/style.xml:1881(title)
+#: en_US/writing-guidelines.xml:268(title)
+msgid "Admonitions"
+msgstr "Advertências"
+
+#: en_US/style.xml:1882(para)
+msgid "Avoid overuse of admonitions. Keep admonitions short and effective by using only the most important material inside the admonition. Move any background material required to explain the admonition statements outside the admonition. Use a short but descriptive title for an admonition. Use title case for the admonition title."
+msgstr "Evite o uso excessivo de advertências. Mantenha-as resumidas e efectivas, usando apenas o material mais importante dentro da advertência. Passe todo o material de segundo plano necessário para explicar as advertências para fora destas. Use um título breve mas descritivo para uma advertência. Use a capitalização no título da advertência."
+
+#: en_US/style.xml:1891(title)
+msgid "Incorrect: Lengthy admonition"
+msgstr "Incorrecto: Advertência comprida"
+
+#: en_US/style.xml:1894(title)
+msgid "Use <command>sfdisk</command> to check input"
+msgstr "Use o <command>sfdisk</command> para verificar os dados de entrada"
+
+#: en_US/style.xml:1895(para)
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+msgstr "O comando <command>sfdisk</command> aceita um ficheiro de programa como dados de entrada para configurar as partições num disco rígido. Em alguns casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, criando uma tabela de partições incorrecta no seu disco. Use sempre o comando <command>sfdisk -n</command> para verificar o seu ficheiro antes de efectuar gravações no disco."
+
+#: en_US/style.xml:1909(title)
+msgid "Correct: Brief admonition"
+msgstr "Correcto: Advertência breve"
+
+#: en_US/style.xml:1917(title)
+msgid "Check Input"
+msgstr "Verifique os Dados de Entrada"
+
+#: en_US/style.xml:1918(para)
+msgid "Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+msgstr "Use sempre o comando <command>sfdisk -n</command> para verificar os seus dados de entrada, antes de gravar no disco."
+
+#: en_US/style.xml:1910(para)
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. <placeholder-1/>"
+msgstr "O comando <command>sfdisk</command> aceita um script como um standard de entrada para configurar as partições num disco rígido. Em alguns casos, o <command>sfdisk</command> irá simplesmente rejeitar um ficheiro de entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, criando uma tabela de partições incorrecta no seu disco. <placeholder-1/>"
+
+#: en_US/style.xml:1925(para)
+msgid "Avoid punctuation in titles for sections or admonitions, except for commas only where demanded. Use a title that says something about the admonition comment, such as \"Reboot Required,\" instead of simply using the admonition type for a title (\"Note\")."
+msgstr "Evite a pontuação nos títulos das secções ou advertências, excepto as vírgulas e somente quando necessário. Use um título que diga algo sobre o comentário da advertência, como \"É Necessário Reiniciar,\" em vez de usar apenas o tipo de advertência como título (\"Nota\")."
+
+#: en_US/style.xml:1932(para)
+msgid "Follow the capitalization rules for headings in the title of an admonition."
+msgstr "Siga as regras de capitalização dos destaques no título de uma advertência."
+
+#: en_US/style.xml:1939(title)
+msgid "The <sgmltag class=\"starttag\">replaceable</sgmltag> Tag"
+msgstr "A Marca <sgmltag class=\"starttag\">replaceable</sgmltag>"
+
+#: en_US/style.xml:1941(para)
+msgid "If your documentation formally states a specific value will be used as a convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag in your text or examples."
+msgstr "Se a sua documentação relatar formalmente que um determinado valor será usado como convenção, não use a marca <sgmltag class=\"starttag\">replaceable</sgmltag> no seu texto ou exemplos."
+
+#: en_US/style.xml:1950(title)
+msgid "XML Entities"
+msgstr "Entidades de XML"
+
+#: en_US/style.xml:1951(para)
+msgid "Use the entities provided by the Fedora Documentation Project. These entities are found in the <filename>common/</filename> folder in the <filename>fedora-docs</filename> distribution. (Refer also to <xref linkend=\"ch-getting-files\"/>.) For instance, do not use abbreviations such as \"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" which produces the text \"Fedora 9.\""
+msgstr "Use as entidades oferecidas pelo Projecto de Documentação do Fedora. Estas entidades estão na pasta <filename>common/</filename> da distribuição <filename>fedora-docs</filename>. (Consulte também a secção <xref linkend=\"ch-getting-files\"/>.) Por exemplo, não use abreviaturas do tipo \"FC2.\" Em vez disso, use as entidades predefinidas \"&FC; &FCVER;,\" que irá gerar o texto \"Fedora 9.\""
+
+#: en_US/writing-guidelines.xml:11(title)
+msgid "Fedora Documentation Guidelines"
+msgstr "Recomendações de Documentação do Fedora"
+
+#: en_US/writing-guidelines.xml:14(primary)
+#: en_US/writing-guidelines.xml:15(see)
+msgid "recursion"
+msgstr "recorrência"
+
+#: en_US/writing-guidelines.xml:19(primary)
+#: en_US/writing-guidelines.xml:26(secondary)
+msgid "RTFM"
+msgstr "RTFM"
+
+#: en_US/writing-guidelines.xml:20(secondary)
+msgid "read the fine manual"
+msgstr "leia o belo manual"
+
+#: en_US/writing-guidelines.xml:21(seealso)
+#: en_US/writing-guidelines.xml:25(primary)
+msgid "humor"
+msgstr "humor"
+
+#: en_US/writing-guidelines.xml:29(para)
+msgid "Please read this chapter carefully. This chapter describes the guidelines that must be followed such as naming conventions."
+msgstr "Por favor, leia este capítulo com cuidado. O mesmo descreve as recomendações que deverão ser seguidas, como as nomenclaturas."
+
+#: en_US/writing-guidelines.xml:32(para)
+msgid "This chapter only discusses tags used for documentation for the Fedora Project, not all available DocBook XML tags. For the complete list, refer to <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr "Este capítulo só discute as marcas usadas na documentação do Projecto Fedora, não refere todas as marcas de XML do DocBook. Para uma lista completa, veja em <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+
+#: en_US/writing-guidelines.xml:38(title)
+msgid "File Header"
+msgstr "Cabeçalho do Ficheiro"
+
+#: en_US/writing-guidelines.xml:40(title)
+msgid "XML Header"
+msgstr "Cabeçalho de XML"
+
+#: en_US/writing-guidelines.xml:41(para)
+msgid "In accordance with good XML practices, the first line in any DocBook XML source files should identify the file as XML. Use the following line as the first line of any new XML file:"
+msgstr "De acordo com as boas práticas de XML, a primeira linha de qualquer ficheiro de DocBook em XML deverá identificar o ficheiro como XML. Use a seguinte linha como primeira linha de qualquer ficheiro em XML novo:"
+
+#: en_US/writing-guidelines.xml:47(title)
+msgid "CVS Id Header"
+msgstr "Cabeçalho do ID do CVS"
+
+#: en_US/writing-guidelines.xml:48(para)
+msgid "All the files must contain the CVS Id header. Use the following line as the second line of any new XML file:"
+msgstr "Todos os ficheiros deverão conter o cabeçalho Id do CVS. Use a seguinte linha como segunda linha para qualquer ficheiro em XML novo:"
+
+#: en_US/writing-guidelines.xml:51(para)
+msgid "Any time the file is committed to CVS, the line is updated automatically to include information about the file. For example:"
+msgstr "Sempre que este ficheiro for enviado para o CVS, a linha é actualizada automaticamente para incluir informações acerca do ficheiro. Por exemplo:"
+
+#: en_US/writing-guidelines.xml:58(title)
+msgid "ID Naming Conventions"
+msgstr "Convenções dos Nomes dos Identificadores"
+
+#: en_US/writing-guidelines.xml:61(primary)
+#: en_US/writing-guidelines.xml:74(primary)
+#: en_US/writing-guidelines.xml:275(primary)
+#: en_US/writing-guidelines.xml:280(primary)
+#: en_US/writing-guidelines.xml:285(primary)
+#: en_US/writing-guidelines.xml:290(primary)
+#: en_US/writing-guidelines.xml:295(primary)
+#: en_US/writing-guidelines.xml:300(primary)
+#: en_US/writing-guidelines.xml:306(primary)
+#: en_US/writing-guidelines.xml:312(primary)
+#: en_US/writing-guidelines.xml:318(primary)
+#: en_US/writing-guidelines.xml:324(primary)
+#: en_US/writing-guidelines.xml:350(primary)
+#: en_US/writing-guidelines.xml:355(primary)
+#: en_US/writing-guidelines.xml:360(primary)
+#: en_US/writing-guidelines.xml:365(primary)
+#: en_US/writing-guidelines.xml:370(primary)
+msgid "XML tags"
+msgstr "Marcas XML"
+
+#: en_US/writing-guidelines.xml:62(secondary)
+#: en_US/writing-guidelines.xml:66(primary)
+#: en_US/writing-guidelines.xml:79(primary)
+msgid "naming conventions"
+msgstr "nomenclaturas"
+
+#: en_US/writing-guidelines.xml:69(para)
+msgid "This section explains the ID naming convention. IDs are unique identifiers that allow DocBook XML to cross-reference a section, chapter, or other element."
+msgstr "Esta secção explica a nomenclaturas de IDs. Os IDs são identificadores únicos que permitem ao DocBook em XML fazer referências a uma dada secção, capítulo ou outro elemento."
+
+#: en_US/writing-guidelines.xml:75(secondary)
+#: en_US/writing-guidelines.xml:80(secondary)
+msgid "rules for defining an ID"
+msgstr "regras de definição de um ID"
+
+#: en_US/writing-guidelines.xml:83(para)
+msgid "The following general rules apply to IDs:"
+msgstr "As seguintes regras gerais aplicam-se aos IDs:"
+
+#: en_US/writing-guidelines.xml:87(para)
+msgid "Keep an ID as short and simple as possible."
+msgstr "Mantenha um ID o mais curto e simples possível."
+
+#: en_US/writing-guidelines.xml:90(para)
+msgid "Start the ID with the special short two-character label. This makes URLs and other references to this ID human readable, by self-identifying the XML container type."
+msgstr "Inicie o ID pela legenda especial de dois caracteres. Esta faz com que os URLs e as outras referências a este ID sejam legíveis, identificando autoamticamente o tipo do contentor de XML."
+
+#: en_US/writing-guidelines.xml:96(para)
+msgid "<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used properly."
+msgstr "O <xref linkend=\"ex-id-usage\"/> demonstra alguns atributos de IDs usados correctamente como exemplos."
+
+#: en_US/writing-guidelines.xml:102(title)
+msgid "Proper ID Usage"
+msgstr "Utilização Adequada de IDs"
+
+#: en_US/writing-guidelines.xml:111(title)
+msgid "Two-Character Naming Conventions"
+msgstr "Nomenclaturas de Dois Caracteres"
+
+#: en_US/writing-guidelines.xml:112(segtitle)
+msgid "Tag"
+msgstr "Marca"
+
+#: en_US/writing-guidelines.xml:113(segtitle)
+msgid "Prefix"
+msgstr "Prefixo"
+
+#: en_US/writing-guidelines.xml:115(sgmltag)
+msgid "preface"
+msgstr "prefácio"
+
+#: en_US/writing-guidelines.xml:116(literal)
+msgid "pr-"
+msgstr "pr-"
+
+#: en_US/writing-guidelines.xml:119(sgmltag)
+msgid "chapter"
+msgstr "chapter"
+
+#: en_US/writing-guidelines.xml:120(literal)
+msgid "ch-"
+msgstr "ch-"
+
+#: en_US/writing-guidelines.xml:123(sgmltag)
+msgid "section"
+msgstr "secção"
+
+#: en_US/writing-guidelines.xml:124(literal)
+msgid "sn-"
+msgstr "sn-"
+
+#: en_US/writing-guidelines.xml:127(sgmltag)
+msgid "figure"
+msgstr "figure"
+
+#: en_US/writing-guidelines.xml:128(literal)
+msgid "fig-"
+msgstr "fig-"
+
+#: en_US/writing-guidelines.xml:131(sgmltag)
+#: en_US/writing-guidelines.xml:235(sgmltag)
+msgid "table"
+msgstr "table"
+
+#: en_US/writing-guidelines.xml:132(literal)
+msgid "tb-"
+msgstr "tb-"
+
+#: en_US/writing-guidelines.xml:135(sgmltag)
+msgid "appendix"
+msgstr "apêndice"
+
+#: en_US/writing-guidelines.xml:136(literal)
+msgid "ap-"
+msgstr "ap-"
+
+#: en_US/writing-guidelines.xml:139(sgmltag)
+msgid "part"
+msgstr "part"
+
+#: en_US/writing-guidelines.xml:140(literal)
+msgid "pt-"
+msgstr "pt-"
+
+#: en_US/writing-guidelines.xml:143(sgmltag)
+msgid "example"
+msgstr "example"
+
+#: en_US/writing-guidelines.xml:144(literal)
+msgid "ex-"
+msgstr "ex-"
+
+#: en_US/writing-guidelines.xml:148(para)
+msgid "Use the title of the item as the ID. Make your titles unique within a document to prevent conflicts. For example:"
+msgstr "Use o título do item como ID. Torne os seus títulos únicos dentro de um documento para evitar conflitos. Por exemplo:"
+
+#: en_US/writing-guidelines.xml:157(title)
+msgid "XML Tags"
+msgstr "Marcas XML"
+
+#: en_US/writing-guidelines.xml:159(primary)
+msgid "xml tags"
+msgstr "marcas em XML"
+
+#: en_US/writing-guidelines.xml:160(secondary)
+msgid "caveats"
+msgstr "contrapartidas"
+
+#: en_US/writing-guidelines.xml:163(para)
+msgid "It is very important that you remember the caveats in this section. These are learned suggestions or rules that make your XML experience better."
+msgstr "É muito importante que recorde as contrapartidas desta secção. Estas são sugestões ou regras de aprendizagem que tornam melhor a sua experiência em XML."
+
+#: en_US/writing-guidelines.xml:171(term)
+msgid "Do Not Use Trademark Entities"
+msgstr "Não Use Entidades de Marcas Registadas"
+
+#: en_US/writing-guidelines.xml:173(para)
+msgid "Do not use the trademark entities <sgmltag class=\"genentity\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class=\"genentity\">reg</sgmltag> because the do not produce HTML output that works for all charsets. The HTML output produces by these entities are declared in the DTD and cannot be changed via the stylesheet."
+msgstr "Não use as entidades de marcas registadas <sgmltag class=\"genentity\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag> ou <sgmltag class=\"genentity\">reg</sgmltag>, porque não produzem HTML válido que funcione em todas as codificações de caracteres. O resultado em HTML produzido por estas entidades está descrito na DTD e não pode ser alterado com a folha de estilo."
+
+#: en_US/writing-guidelines.xml:181(para)
+msgid "Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes as follows:"
+msgstr "Em vez disso, use a marca <sgmltag>trademark</sgmltag> e as suas classes associadas, como se segue:"
+
+#: en_US/writing-guidelines.xml:184(segtitle)
+msgid "DocBook XML source"
+msgstr "Código XML do DocBook"
+
+#: en_US/writing-guidelines.xml:185(segtitle)
+msgid "Rendered content"
+msgstr "Conteúdo representado"
+
+#: en_US/writing-guidelines.xml:189(trademark)
+msgid "trademark symbol after me"
+msgstr "símbolo de marca comercial a seguir a mim"
+
+#: en_US/writing-guidelines.xml:196(trademark)
+msgid "registered trademark symbol after me"
+msgstr "símbolo de marca registada a seguir a mim"
+
+#: en_US/writing-guidelines.xml:202(trademark)
+msgid "copyright symbol after me"
+msgstr "símbolo de direitos de cópia a seguir a mim"
+
+#: en_US/writing-guidelines.xml:209(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr "Conteúdo dentro das marcas <sgmltag>para</sgmltag>"
+
+#: en_US/writing-guidelines.xml:211(para)
+msgid "In general, use <sgmltag>para</sgmltag> tags around anything other than a simple paragraph. Doing so will create additional white space within the text itself in the PDF version."
+msgstr "De um modo geral, não use as marcas <sgmltag>para</sgmltag> em torno de tudo o que não seja um parágrafo simples. Ao fazê-lo, irá criar espaços em branco adicionais dentro do próprio texto, na versão em PDF."
+
+#: en_US/writing-guidelines.xml:216(para)
+msgid "Specifically, do not use <sgmltag>para</sgmltag> tags around the following (or, to put this another way, do not embed the following within <sgmltag class=\"element\">para</sgmltag> elements):"
+msgstr "Especificamente, não use as marcas <sgmltag>para</sgmltag> em torno do seguinte (ou, posto de outra forma, não incorpore o seguinte dentro das marcas <sgmltag class=\"element\">para</sgmltag>):"
+
+#: en_US/writing-guidelines.xml:223(sgmltag)
+msgid "screen"
+msgstr "screen"
+
+#: en_US/writing-guidelines.xml:226(sgmltag)
+msgid "itemizedlist"
+msgstr "itemizedlist"
+
+#: en_US/writing-guidelines.xml:229(sgmltag)
+msgid "orderedlist"
+msgstr "orderedlist"
+
+#: en_US/writing-guidelines.xml:232(sgmltag)
+msgid "variablelist"
+msgstr "variablelist"
+
+#: en_US/writing-guidelines.xml:241(term)
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag>listitem</sgmltag> tags"
+msgstr "Conteúdo dentro de elementos <sgmltag class=\"element\">para</sgmltag> residentes em marcas <sgmltag>listitem</sgmltag>"
+
+#: en_US/writing-guidelines.xml:244(para)
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</emphasis> start immediately after the beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr "O conteúdo dentro das marcas <sgmltag class=\"element\">para</sgmltag> inseridas em marcas <sgmltag class=\"element\">listitem</sgmltag> <emphasis>deverá</emphasis> começar logo a seguir à marca inicial <sgmltag class=\"starttag\">para</sgmltag>, para evitar espaços em branco extra na versão em PDF."
+
+#: en_US/writing-guidelines.xml:252(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr "Conteúdo dentro das marcas <sgmltag>screen</sgmltag>"
+
+#: en_US/writing-guidelines.xml:254(para)
+msgid "The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) <emphasis>must</emphasis> be flush left in the XML file; otherwise, the extraneous whitespace will appear in the HTML version."
+msgstr "O conteúdo dentro das marcas <sgmltag>screen</sgmltag> (<sgmltag class=\"starttag\">screen</sgmltag> e <sgmltag class=\"endtag\">screen</sgmltag>) <emphasis>deverão</emphasis> ser retirados à esquerda no ficheiro em XML; caso contrário, os espaços em branco estranhos irão aparecer na versão em HTML."
+
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:301(secondary)
+#: en_US/writing-guidelines.xml:307(secondary)
+#: en_US/writing-guidelines.xml:313(secondary)
+#: en_US/writing-guidelines.xml:319(secondary)
+#: en_US/writing-guidelines.xml:325(secondary)
+msgid "admonitions"
+msgstr "advertências"
+
+#: en_US/writing-guidelines.xml:276(secondary)
+#: en_US/writing-guidelines.xml:302(tertiary)
+#: en_US/writing-guidelines.xml:371(secondary)
+msgid "warning"
+msgstr "warning"
+
+#: en_US/writing-guidelines.xml:281(secondary)
+#: en_US/writing-guidelines.xml:308(tertiary)
+#: en_US/writing-guidelines.xml:356(secondary)
+msgid "tip"
+msgstr "tip"
+
+#: en_US/writing-guidelines.xml:286(secondary)
+#: en_US/writing-guidelines.xml:314(tertiary)
+#: en_US/writing-guidelines.xml:351(secondary)
+msgid "note"
+msgstr "note"
+
+#: en_US/writing-guidelines.xml:291(secondary)
+#: en_US/writing-guidelines.xml:320(tertiary)
+#: en_US/writing-guidelines.xml:361(secondary)
+msgid "caution"
+msgstr "caution"
+
+#: en_US/writing-guidelines.xml:296(secondary)
+#: en_US/writing-guidelines.xml:326(tertiary)
+#: en_US/writing-guidelines.xml:366(secondary)
+msgid "important"
+msgstr "important"
+
+#: en_US/writing-guidelines.xml:329(para)
+msgid "There are five types of admonitions in DocBook: <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the admonitions have the same structure: an optional <sgmltag class=\"element\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD does not impose any specific semantics on the individual admonitions. For example, DocBook does not mandate that a <sgmltag class=\"element\">warning</sgmltag> is reserved for cases where bodily harm can result."
+msgstr "Existem cinco tipos de advertências no DocBook: <sgmltag class=\"element\">caution</sgmltag> (cuidado), <sgmltag class=\"element\">important</sgmltag> (importante), <sgmltag class=\"element\">note</sgmltag> (nota), <sgmltag class=\"element\">tip</sgmltag> (sugestão) e <sgmltag class=\"element\">warning</sgmltag> (aviso). Todas as advertências têm a mesma estrutura: um <sgmltag class=\"element\">title</sgmltag> opcional, seguido dos elementos do nível dos parágrafos. A DTD do DocBook não impõe qualquer semântica específica das advertências individuais. Por exemplo, o DocBook não obriga que um <sgmltag class=\"element\">warning</sgmltag> esteja reservado para os casos em que possam resultar danos corporais."
+
+#: en_US/writing-guidelines.xml:343(title)
+msgid "Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element\">warning</sgmltag>"
+msgstr "Criar um <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag> ou <sgmltag class=\"element\">warning</sgmltag>"
+
+#: en_US/writing-guidelines.xml:374(para)
+msgid "There are several ways to bring attention to text within a document. A <emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to bring additional information to the users' attention. A <emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful information or another way to do something. A <emphasis><sgmltag class=\"element\">caution</sgmltag></emphasis> is used to show the user they must be careful when attempting a certain step. An <emphasis><sgmltag class=\"element\">important</sgmltag></emphasis> tag set can be used to show the user a piece of information that should not be overlooked. While this information may not change anything the user is doing, it should show the user that this piece of information could be vital. A <emphasis><sgmltag class=\"element\">warning</sgmltag></emphasis> is used to show the reader that their current setup will change or be altered, such as files being removed, and they should not c
hoose this operation unless they are alright with the consequences."
+msgstr "Existem diversas formas de chamar a atenção ao texto dentro de um documento. Uma <emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> (nota) é usada para trazer informações para a atenção dos utilizadores. Uma <emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> (sugestão) é usada para mostrar ao utilizador alguma informação útil ou outra forma de fazer algo. Uma <emphasis><sgmltag class=\"element\">caution</sgmltag></emphasis> é usada para mostrar ao utilizador que deverá ter cuidado ao efectuar um determinado passo. Uma marca <emphasis><sgmltag class=\"element\">important</sgmltag></emphasis> pode ser usada para mostrar ao utilizador um pedaço de informação que não deva ser ignorado. Embora esta informação possa não alterar o que o utilizador irá fazer, deverá mostrar ao utilizador que esta informação poderá ser vital. Um <emphasis><sgmltag class=\"element\">warning</sgmltag></emphasis> é usado para mostrar ao leitor qu
e a sua configuração actual irá mudar ou ser alterada, como a remoção de ficheiros, pelo que não deverão escolher esta operação, a menos que estejam de acordo com as consequências."
+
+#: en_US/writing-guidelines.xml:394(para)
+msgid "The following lines of code show the basic setup for each case mentioned above, along with its appearance in HTML."
+msgstr "As seguintes linhas de código mostram a configuração básica de cada um dos casos indicados acima, em conjunto com a sua aparência em HTML."
+
+#: en_US/writing-guidelines.xml:403(title)
+#: en_US/emacs.xml:257(title)
+#: en_US/emacs.xml:562(title)
+#: en_US/emacs-nxml.xml:160(title)
+msgid "Note"
+msgstr "Nota"
+
+#: en_US/writing-guidelines.xml:404(para)
+#: en_US/writing-guidelines.xml:424(para)
+#: en_US/writing-guidelines.xml:434(para)
+#: en_US/writing-guidelines.xml:444(para)
+msgid "Body of text goes here."
+msgstr "O conteúdo do texto aparece aqui."
+
+#: en_US/writing-guidelines.xml:413(title)
+#: en_US/emacs-nxml.xml:114(title)
+msgid "Tip"
+msgstr "Sugestão"
+
+#: en_US/writing-guidelines.xml:414(para)
+msgid "Body of text goes here"
+msgstr "O conteúdo do texto aparece aqui"
+
+#: en_US/writing-guidelines.xml:423(title)
+msgid "Caution"
+msgstr "Atenção"
+
+#: en_US/writing-guidelines.xml:433(title)
+#: en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr "Importante"
+
+#: en_US/writing-guidelines.xml:443(title)
+msgid "Warning"
+msgstr "Aviso"
+
+#: en_US/writing-guidelines.xml:451(title)
+msgid "Screenshots"
+msgstr "Imagens"
+
+#: en_US/writing-guidelines.xml:454(primary)
+#: en_US/writing-guidelines.xml:459(see)
+#: en_US/writing-guidelines.xml:463(see)
+msgid "screenshots"
+msgstr "imagens"
+
+#: en_US/writing-guidelines.xml:455(secondary)
+msgid "how to take"
+msgstr "como fazer"
+
+#: en_US/writing-guidelines.xml:458(primary)
+msgid "screen captures"
+msgstr "capturas do ecrã"
+
+#: en_US/writing-guidelines.xml:462(primary)
+msgid "screen grabs"
+msgstr "gravações do ecrã"
+
+#: en_US/writing-guidelines.xml:466(para)
+msgid "Screenshots are illustrations that show the state of a display the user may encounter. Screenshots can be either graphical or textual. However, screenshots use a great deal of space in a text document to convey relatively small amounts of information. The same space in the document can hold a greater amount of more descriptive and helpful information. Therefore, authors should avoid screenshots whenever possible in favor of descriptive text."
+msgstr "As imagens ou capturas de ecrã são ilustrações que apresentam o estado do ecrã que o utilizador poderá encontrar. As imagens poderão ser gráficas ou textuais. Contudo, as imagens usam bastante espaço num documento de texto para representar pedaços de informação relativamente pequenos. o mesmo espaço num documento poderá conter uma quantidade maior de informação mais descritiva e útil. Como tal, os autores deverão evitar as imagens sempre que possível, em detrimento de texto mais descritivo."
+
+#: en_US/writing-guidelines.xml:474(para)
+msgid "One of the isolated instances in which screenshots are useful is to demonstrate a physical screen layout that is unfamiliar to a reader. <emphasis>This does not mean that illustrations of dialog boxes are good uses of screenshots.</emphasis> On the contrary, dialogs are simply instances of a user interface element with which a reader is already familiar. An annotated diagram in certain cases, however, explains to the reader where to find functional landmarks on the screen such as menu bars."
+msgstr "Uma das instâncias isoladas em que as imagens são úteis é para demonstrar a disposição física de um ecrã que não seja familiar para um leitor. <emphasis>Isto não significa que as ilustrações de janelas sejam bons usos para as imagens.</emphasis> Pelo contrário, as janelas são simplesmente instâncias de um elemento da interface com o qual o leitor já está familiarizado. Um diagrama anotado em certos casos, todavia, explica ao leitor onde encontrar certos blocos funcionais no ecrã, como as barras de menu."
+
+#: en_US/writing-guidelines.xml:482(para)
+msgid "The steps for taking a graphical screenshot illustrate how using text to describe a procedure is more concise than a series of screenshots."
+msgstr "Os passos para tirar uma imagem gráfica ilustram como a utilização de texto para descrever um dado procedimento é mais conciso que uma série de imagens."
+
+#: en_US/writing-guidelines.xml:487(term)
+msgid "Graphical Screenshot"
+msgstr "Imagem Gráfica"
+
+#: en_US/writing-guidelines.xml:491(para)
+msgid "Create a new user account to make screenshots. The new account uses the distribution default theme, fonts, and element sizes. The resulting screenshot has an appearance familiar to the largest number of readers, and makes Fedora Documentation Project documents consistent."
+msgstr "Crie uma nova conta de utilizador para criar as imagens. A conta nova usa o tema, tipos de letra e tamanhos dos elementos predefinidos da instalação. A imagem resultante tem uma aparência familiar ao maior número de leitores, e faz com que os documentos do Projecto de Documentação do Fedora sejam consistentes."
+
+#: en_US/writing-guidelines.xml:498(para)
+msgid "Before taking the screenshot, if possible, resize the targeted GUI element(s) to the smallest possible size. The target image should be 500 pixels wide or less. If the screenshot includes more than one GUI element, you may need to resize the screenshot in a following step."
+msgstr "Antes de tirar a fotografia, tente dimensionar os elementos gráficos com o tamanho mais pequeno possível. O seu objectivo é uma imagem com 500 pixels ou menos ainda. Se estiver a tirar uma fotografia com mais de um elemento gráfico, terá de dimensionar a imagem num passo seguinte."
+
+#: en_US/writing-guidelines.xml:506(para)
+msgid "To take the screenshot, select the GUI element with the mouse to bring it to the forefront, or otherwise arrange the elements. Press <keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to capture a single GUI window. For capturing the entire desktop use <keycap>Print Screen</keycap>. If the shot includes multiple elements grouped closely together, crop the resulting PNG format image in <application>The GIMP</application>."
+msgstr "Para tirar a imagem, seleccione o elemento gráfico com o seu rato, passando-o para primeiro plano, ou organizando os elementos. Carregue em <keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> para capturar uma única janela. Para capturar o ecrã completo, use o <keycap>Print Screen</keycap>. Se estiver a tirar uma fotografia de vários elementos e os tiver agrupado em conjunto, poderá recortar a imagem resultante no <application>The GIMP</application>. A imagem estará no formato PNG."
+
+#: en_US/writing-guidelines.xml:518(para)
+msgid "If necessary, resize the image using <application>The GIMP</application>. Open the image, then right-click on it and choose <menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</guimenuitem></menuchoice>. With the chain symbol intact, set the <guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click <guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the image before converting it."
+msgstr "Se precisar, poderá dimensionar a imagem com o <application>The GIMP</application>. Com a imagem aberta, carregue com o botão direito nesta e escolha a opção <menuchoice><guimenu>Imagem</guimenu><guimenuitem>Escalar a Imagem...</guimenuitem></menuchoice>. Com o símbolo da corrente intacto, configure a <guilabel>Nova Largura</guilabel> com o valor <guilabel>500 px</guilabel> e carregue em <guibutton>OK</guibutton>. Certifique-se que carrega em <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo> para gravar as suas alterações no seu PNG, antes da conversão para EPS."
+
+#: en_US/writing-guidelines.xml:534(para)
+msgid "With the image open in <application>The GIMP</application>, right-click the image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As...</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</guibutton>. Allow flattening of the image by clicking <guibutton>Export</guibutton>."
+msgstr "Com a imagem aberta no <application>The GIMP</application>, carregue com o botão direito na imagem e seleccione a opção <menuchoice><guimenu>Ficheiro</guimenu><guimenuitem>Gravar Como...</guimenuitem></menuchoice>. Em <guimenu>Determinar o Tipo de Ficheiro:</guimenu>, seleccione <guimenuitem>PostScript</guimenuitem>, carregando depois em <guibutton>OK</guibutton>. Active o alisamento da imagem com a opção <guibutton>Exportar</guibutton>."
+
+#: en_US/writing-guidelines.xml:545(para)
+msgid "A <guilabel>Save as PostScript</guilabel> window appears. Select <guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</guibutton>."
+msgstr "Na janela para <guilabel>Gravar como PostScript</guilabel>, seleccione <guilabel>PostScript Encapsulado</guilabel> e carregue em <guibutton>OK</guibutton>."
+
+#: en_US/writing-guidelines.xml:559(term)
+msgid "Text Screenshot"
+msgstr "Imagem de Texto"
+
+#: en_US/writing-guidelines.xml:561(para)
+msgid "Textual screen information is also useful for readers. Follow these guidelines for textual screenshots:"
+msgstr "A informação textual do ecrã também é útil para os leitores. Siga estas recomendações para as imagens textuais:"
+
+#: en_US/writing-guidelines.xml:565(para)
+msgid "If a graphical screenshot illustrates a function, and the textual mode has identical functions, do not include both, unless omitting either would make your description unclear."
+msgstr "Se usar uma imagem gráfica para ilustrar uma função e o modo textual tiver funções idênticas, não inclua ambas, a menos que a omissão de uma delas torne a sua descrição menos clara."
+
+#: en_US/writing-guidelines.xml:571(para)
+msgid "Make the information generic over specific, and omit any username and machine information if possible. Do not include the shell prompt unless it is vital to the demonstration."
+msgstr "Opte por ter a sua informação genérica em vez de específica, omitindo a informação do utilizador e da máquina, se possível. Não inclua a linha de comandos, a menos que seja vital para a demonstração."
+
+#: en_US/writing-guidelines.xml:577(para)
+msgid "Separate what the user types from sample command output."
+msgstr "Separe o que o utilizador escreve do resultado do comando."
+
+#: en_US/writing-guidelines.xml:581(para)
+msgid "When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show what the user types, and use <sgmltag class=\"element\">computeroutput</sgmltag> tags to show the resulting output."
+msgstr "Ao usar o <sgmltag class=\"element\">screen</sgmltag> para demonstrar um procedimento, use as marcas <sgmltag class=\"element\">userinput</sgmltag> para mostrar o que o utilizador escreve, usando as marcas <sgmltag class=\"element\">computeroutput</sgmltag> para mostrar o resultado."
+
+#: en_US/writing-guidelines.xml:589(para)
+msgid "<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual screenshot usage."
+msgstr "O <xref linkend=\"ex-text-screenshot-good\"/> é um exemplo de utilização de uma imagem textual."
+
+#: en_US/writing-guidelines.xml:594(title)
+msgid "Correct Textual Screenshot (XML Source and HTML)"
+msgstr "Corrigir a Imagem Textual (Código em XML e HTML)"
+
+#: en_US/writing-guidelines.xml:607(para)
+msgid "To find all the currently active ssh sessions, execute the following command:"
+msgstr "Para descobrir todas as sessões de SSH activas, execute o seguinte comando:"
+
+#: en_US/writing-guidelines.xml:609(userinput)
+#, no-wrap
+msgid "ps ax | grep ssh"
+msgstr "ps ax | grep ssh"
+
+#: en_US/writing-guidelines.xml:611(para)
+msgid "Output appears similar to the following:"
+msgstr "O resultado aparece semelhante ao seguinte:"
+
+#: en_US/writing-guidelines.xml:613(computeroutput)
+#, no-wrap
+msgid ""
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh user@@host.example.com\n"
+" 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+msgstr ""
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh utilizador@@maquina.exemplo.com\n"
+" 8032 pts/1 S 0:00 ssh root@@salvaguarda.exemplo.com"
+
+#: en_US/writing-guidelines.xml:648(title)
+msgid "Previewing Your Work"
+msgstr "Antever o seu Trabalho"
+
+#: en_US/writing-guidelines.xml:649(para)
+msgid "The GNOME <application>Help</application> browser, also known as <command>yelp</command>, and the KDE <application>Khelp</application> documentation browser can render DocBook XML information as needed. Use these applications to preview your work if you prefer reading your work in a browser-like environment. Run the following command:"
+msgstr "O navegador de <application>Ajuda</application> do GNOME, também conhecido como <command>yelp</command> e o <application>Khelp</application> do KDE poderão representar a informação em XML do DocBook à medida das necessidades. Use estas aplicações para antever o seu trabalho, se o preferir ler num ambiente de um navegador. Execute assim o seguinte comando:"
+
+#: en_US/writing-guidelines.xml:656(para)
+msgid "Make sure to point the preferred help browser at the top parent file of your XML document. Once the document loads, you can add a bookmark for it for ease of use later."
+msgstr "Certifique-se que aponta o navegador de ajuda preferido para o ficheiro-pai do seu documento em XML. Logo que o documento seja carregado, poderá adicionar um favorito para o mesmo para o poder usar mais tarde."
+
+#: en_US/writing-guidelines.xml:660(title)
+msgid "Using Bookmarks"
+msgstr "Usar os Favoritos"
+
+#: en_US/writing-guidelines.xml:661(para)
+msgid "Keeping your documents in the same place for every checkout session makes help browser bookmarks more effective."
+msgstr "Manter os seus documentos no mesmo local para cada sessão de recepção torna os favoritos do navegador de ajuda mais efectivos."
+
+#: en_US/writing-guidelines.xml:664(para)
+msgid "Once you have a bookmark stored, it will appear in the help browser at every use. You can now hit <keycap>F1</keycap> during any GUI session to launch the help browser. Then choose your bookmark from the menu to preview your document at any time."
+msgstr "Logo que tenha guardado um favorito, este irá aparecer no navegador de ajuda sempre que o usar. Poderá agora carregar em <keycap>F1</keycap> durante qualquer sessão gráfica para lançar o navegador de ajuda. Depois, escolha o seu favorito do menu para antever o seu documento em qualquer altura."
+
+#: en_US/module-struct.xml:12(title)
+msgid "How Modules Work"
+msgstr "Como Funcionam os Módulos"
+
+#: en_US/module-struct.xml:13(para)
+msgid "Documentation modules have a specific structure that enables the preconfigured tools to work correctly. Follow this structure exactly or you may have problems building your module. The Fedora Documentation Project build tools locate resources in the module and use them to build new output such as HTML or RPM packages."
+msgstr "Os módulos de documentação têm uma estrutura específica que activa as ferramentas pré-configuradas para funcionarem correctamente. Siga esta estrutura exacta ou então poderá vir a ter problemas com a compilação do seu módulo. As ferramentas de compilação do Projecto de Documentação do Fedora localizam os recursos no módulo e usam-nos para criar novos formatos de saída, como HTML ou pacotes RPM."
+
+#: en_US/module-struct.xml:19(title)
+msgid "Structure of a Module"
+msgstr "Estrutura de um Módulo"
+
+#: en_US/module-struct.xml:20(para)
+msgid "<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example module, excluding any <filename class=\"directory\">CVS</filename> folders. Note that this example document does not have branches."
+msgstr "A secção <xref linkend=\"ex-module-structure\"/> mostra uma árvore de pastas de um módulo de exemplo, excluindo as pastas <filename class=\"directory\">CVS</filename>. Repare que este documento de exemplo não tem ramificações."
+
+#: en_US/module-struct.xml:25(title)
+msgid "Example Module Structure"
+msgstr "Estrutura do Módulo de Exemplo"
+
+#: en_US/module-struct.xml:47(title)
+msgid "CVS Module Contents"
+msgstr "Conteúdo do Módulo de CVS"
+
+#: en_US/module-struct.xml:48(segtitle)
+msgid "Component"
+msgstr "Componente"
+
+#: en_US/module-struct.xml:49(segtitle)
+msgid "Type"
+msgstr "Tipo"
+
+#: en_US/module-struct.xml:50(segtitle)
+msgid "Usage Notes"
+msgstr "Notas de Utilização"
+
+#: en_US/module-struct.xml:52(seg)
+msgid "Primary language directory"
+msgstr "Pasta da língua primária"
+
+#: en_US/module-struct.xml:53(seg)
+#: en_US/module-struct.xml:94(seg)
+#: en_US/module-struct.xml:101(seg)
+msgid "required"
+msgstr "obrigatória"
+
+#: en_US/module-struct.xml:56(filename)
+#: en_US/module-struct.xml:181(systemitem)
+msgid "en_US"
+msgstr "pt"
+
+#: en_US/module-struct.xml:60(firstterm)
+msgid "entities"
+msgstr "entidades"
+
+#: en_US/module-struct.xml:61(para)
+msgid "Think of an XML entity as a predefined snippet of information. It can represent a chunk of XML source, or simply a word or character. If the information changes, it need be replaced only once, in the definition, to fix all usage."
+msgstr "Pense numa entidade de XML como um pedaço predefinido de informação. Poderá representar um bloco de código em XML, ou simplesmente uma palavra ou carácter. Se a informação se alterar, terá de ser substituída apenas uma vez na definição, de modo a corrigir todas as alterações."
+
+#: en_US/module-struct.xml:54(seg)
+msgid "This is the only directory absolutely required. It is named for the original language of the document, such as <placeholder-1/> (US English). The primary language does not have to be US English; all languages are supported. This directory contains all the XML source for the actual document, as well as XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr "Esta é a única pasta que constitui um requisito obrigatório. É nomeada em função da língua original do documento, como por exemplo <placeholder-1/> (Inglês dos EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas todas as línguas. Esta pasta contém todo o código em XML do documento actual, assim como o código em XML específico do documento para <placeholder-2/><footnote><placeholder-3/></footnote>."
+
+#: en_US/module-struct.xml:69(seg)
+msgid "Graphics directory"
+msgstr "Pasta de imagens"
+
+#: en_US/module-struct.xml:70(seg)
+#: en_US/module-struct.xml:80(seg)
+msgid "optional"
+msgstr "opcional"
+
+#: en_US/module-struct.xml:71(filename)
+#: en_US/module-struct.xml:75(filename)
+msgid "figs/"
+msgstr "figs/"
+
+#: en_US/module-struct.xml:71(seg)
+msgid "The <placeholder-1/> directory is an optional directory where graphics for the document should be stored. If graphics are screenshots that are particular to a language, the <placeholder-2/> directory can and should be stored in a language directory."
+msgstr "A pasta <placeholder-1/> é uma pasta opcional onde serão gravadas as imagens do documento. Se estas forem imagens particulares para uma determinada língua, a pasta <placeholder-2/> pode e deve ser gravada numa pasta de línguas."
+
+#: en_US/module-struct.xml:79(seg)
+msgid "Translation (PO) directory"
+msgstr "Pasta de traduções (PO)"
+
+#: en_US/module-struct.xml:81(filename)
+#: en_US/module-struct.xml:87(filename)
+msgid "po/"
+msgstr "po/"
+
+#: en_US/module-struct.xml:83(acronym)
+msgid "PO"
+msgstr "PO"
+
+#: en_US/module-struct.xml:88(filename)
+msgid "LINGUAS"
+msgstr "LINGUAS"
+
+#: en_US/module-struct.xml:89(firstterm)
+msgid "locales"
+msgstr "locais"
+
+#: en_US/module-struct.xml:81(seg)
+msgid "The <placeholder-1/> directory contains specially formatted Portable Object, or <placeholder-2/>, files created and used by translators. The Fedora Documentation Project build tools use these files to create translated versions of documents. The translated documents are not stored in CVS; they are created as needed from these PO files. The <placeholder-3/> directory also contains the <placeholder-4/> file, which lists the active translation <placeholder-5/>, or languages."
+msgstr "A pasta <placeholder-1/> contém os ficheiros 'Portable Object' ou <placeholder-2/> especialmente formatados, criados e usados pelos tradutores. As ferramentas de compilação do Projecto de Documentação do Fedora usam estes ficheiros para criar versões traduzidas dos documentos. Os documentos traduzidos não são guardados no CVS; são criados à medida das necessidades a partir destes ficheiros PO. A pasta <placeholder-3/> também contém o ficheiro <placeholder-4/>, que contém os <placeholder-5/> activos nas traduções ou línguas."
+
+#: en_US/module-struct.xml:93(seg)
+#: en_US/module-struct.xml:95(filename)
+msgid "Makefile"
+msgstr "Makefile"
+
+#: en_US/module-struct.xml:95(seg)
+msgid "The <placeholder-1/> controls the build process. Its content is discussed in <xref linkend=\"ex-makefile\"/>."
+msgstr "A <placeholder-1/> controla o processo de compilação. O seu conteúdo é discutido em <xref linkend=\"ex-makefile\"/>."
+
+#: en_US/module-struct.xml:100(filename)
+#: en_US/module-struct.xml:102(filename)
+msgid "rpm-info.xml"
+msgstr "rpm-info.xml"
+
+#: en_US/module-struct.xml:102(seg)
+msgid "The <placeholder-1/> file contains document specific metadata"
+msgstr "O ficheiro <placeholder-1/> contém os metadados específicos do documento"
+
+#: en_US/module-struct.xml:107(title)
+msgid "Common Build Tools"
+msgstr "Ferramentas de Compilação Comuns"
+
+#: en_US/module-struct.xml:108(para)
+msgid "Never add the <systemitem>docs-common</systemitem> build tools directory to an individual module. Special formatting in the module list downloads these tools when a user checks out a document module. For more information, refer to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+msgstr "Nunca adicione a pasta de ferramentas de compilação <systemitem>docs-common</systemitem> a um módulo individual. A formatação especial na lista de módulos transfere estas ferramentas, sempre que um utilizador obtém um módulo de um documento. Para mais informações, consulte em <xref linkend=\"ch-getting-files-naming-modules\"/>."
+
+#: en_US/module-struct.xml:116(title)
+msgid "The Document Build System"
+msgstr "O Sistema de Compilação dos Documentos"
+
+#: en_US/module-struct.xml:121(para)
+msgid "In Linux and Fedora documentation, references to commands often include a number inside parentheses. This number represents the section of <firstterm>manpages</firstterm> that includes documentation for that command. To read the manpage for <command>make(1)</command>, use the command <command>man 1 make</command>."
+msgstr "No Linux e na documentação do Fedora, as referências aos comandos normalmente incluem um número entre parêntesis. Este número representa a secção das <firstterm>páginas de manual</firstterm> que incluem a documentação para esse comando. Para ler a página de manual para o <command>make(1)</command>, use o comando <command>man 1 make</command>."
+
+#: en_US/module-struct.xml:117(para)
+msgid "The build system can render the document into another format such as <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</command><placeholder-1/> and shell scripts. Authors need <emphasis>no</emphasis> prior experience with either shell scripts or a <command>make(1)</command>."
+msgstr "O sistema de compilação poderá representar o documento noutro formato, como o <abbrev>HTML</abbrev> ou <abbrev>PDF</abbrev>, utilizando <command>make(1)</command><footnote><placeholder-1/></footnote> e os programas da linha de comandos. Os autores <emphasis>não</emphasis> precisam de qualquer experiência anterior com os programas da linha de comandos ou o <command>make(1)</command>."
+
+#: en_US/module-struct.xml:133(title)
+msgid "The Document <filename>Makefile</filename>"
+msgstr "A <filename>Makefile</filename> do Documento"
+
+#: en_US/module-struct.xml:134(para)
+msgid "Each individual document has its own <filename>Makefile</filename>, which only needs to be a few lines long. The document <filename>Makefile</filename> content is designed for cut and paste operations."
+msgstr "Cada documento individual tem a sua própria <filename>Makefile</filename>, que só necessita de ter algumas linhas. O conteúdo da <filename>Makefile</filename> do documento está desenhado para operações de corte e colagem."
+
+#: en_US/module-struct.xml:140(para)
+msgid "<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</filename> for a simple document with two files and two translations."
+msgstr "A <xref linkend=\"ex-makefile\"/> abaixo mostra a <filename>Makefile</filename> completa de um documento simples com dois ficheiros e duas traduções."
+
+#: en_US/module-struct.xml:146(title)
+msgid "Sample Document Makefile"
+msgstr "Makefile do Documento de Exemplo"
+
+#: en_US/module-struct.xml:162(para)
+msgid "Do not be concerned with some of the more complicated syntax such as the <command>XMLFILES_template</command> stanza. An explanation for this template appears a few paragraphs below."
+msgstr "Não se preocupe com alguma da sintaxe mais complicada, como o <command>XMLFILES_template</command>. Aparecerá em baixo uma explicação para este modelo."
+
+#: en_US/module-struct.xml:168(title)
+msgid "Makefile Variables"
+msgstr "Variáveis da Makefile"
+
+#: en_US/module-struct.xml:169(segtitle)
+msgid "Variable"
+msgstr "Variável"
+
+#: en_US/module-struct.xml:170(segtitle)
+#: en_US/module-struct.xml:240(segtitle)
+msgid "Explanation"
+msgstr "Explicação"
+
+#: en_US/module-struct.xml:172(systemitem)
+msgid "DOCBASE"
+msgstr "DOCBASE"
+
+#: en_US/module-struct.xml:173(seg)
+msgid "This variable contains the name for the main (parent) XML document. Follow convention by naming your document after the module name."
+msgstr "Esta variável contém o nome do documento-pai principal em XML. Siga a convenção, nomeando o seu documento com o nome do módulo."
+
+#: en_US/module-struct.xml:178(systemitem)
+msgid "PRI_LANG"
+msgstr "PRI_LANG"
+
+#: en_US/module-struct.xml:179(seg)
+msgid "This variable contains the ISO code for the original version of the document, such as <placeholder-1/>."
+msgstr "Esta variável contém o código ISO da versão original do documento, como em <placeholder-1/>."
+
+#: en_US/module-struct.xml:184(systemitem)
+msgid "DOC_ENTITIES"
+msgstr "DOC_ENTITIES"
+
+#: en_US/module-struct.xml:185(seg)
+msgid "This variable contains a listing of any files containing entity definitions. The Fedora Documentation Project uses a special XML format to record document-specific entities, so they can be translated and built on the fly like any other XML document. An example is shown later in this guide."
+msgstr "Esta variável contém uma listagem de todos os ficheiros que contêm definições de entidades. O Projecto de Documentação do Fedora usa um formato em XML especial para guardar as entidades específicas do documento, de modo que possam ser traduzidas e geradas na altura, como se fosse outro documento em XML qualquer. Aparecerá então um exemplo mais tarde neste guia."
+
+#: en_US/module-struct.xml:194(systemitem)
+msgid "XMLFILES_template"
+msgstr "XMLFILES_template"
+
+#: en_US/module-struct.xml:197(systemitem)
+msgid "${1}"
+msgstr "${1}"
+
+#: en_US/module-struct.xml:202(systemitem)
+msgid "${1}/"
+msgstr "${1}/"
+
+#: en_US/module-struct.xml:195(seg)
+msgid "This template allows the build tools to work with the document in multiple languages once it is translated. The <placeholder-1/> marking is a variable used to substitute the appropriate language. This template is not terribly complicated. For a new module, duplicate this section exactly except for the actual filenames. Prepend the text <placeholder-2/>, in place of the language code directory name, to each filename in your document."
+msgstr "Este modelo permite às ferramentas de compilação funcionarem com o documento em várias línguas, logo que esteja traduzido. A marcação <placeholder-1/> é uma variável que é usada para substituir a língua apropriada. Este modelo não é terrivelmente complicado. Para um módulo novo, duplique esta secção exactamente, excepto os nomes dos ficheiros em si. Coloque antes o texto <placeholder-2/>, no lugar do nome da pasta do código da língua, para cada nome de ficheiro no seu documento."
+
+#: en_US/module-struct.xml:208(title)
+msgid "Files Exempt From Listing"
+msgstr "Ficheiros Isentos da Listagem"
+
+#: en_US/module-struct.xml:209(para)
+msgid "Do not include the document-specific entities XML file or the <filename>rpm-info.xml</filename> file, which will be discussed later in this guide."
+msgstr "Não inclua o ficheiro XML de entidades específicas do documento nem o ficheiro <filename>rpm-info.xml</filename>, os quais serão descritos posteriormente neste guia."
+
+#: en_US/module-struct.xml:213(para)
+msgid "The final section, beginning with <literal>define</literal>, locates the main <filename>Makefile.common</filename> for the build system. This <filename>Makefile.common</filename> file contains all the <application>make(1)</application> targets and rules to actually build the document and the various archives."
+msgstr "A secção final, que começa por <literal>define</literal>, localiza o ficheiro <filename>Makefile.common</filename> principal para o sistema de compilação. Este ficheiro <filename>Makefile.common</filename> contém todos os alvos e regras do <application>make(1)</application> para criar de facto o documento e os vários pacotes."
+
+#: en_US/module-struct.xml:222(title)
+msgid "The Document <filename>rpm-info.xml</filename>"
+msgstr "O <filename>rpm-info.xml</filename> do Documento"
+
+#: en_US/module-struct.xml:223(para)
+msgid "Each document module's primary language directory contains a file called <filename>rpm-info.xml</filename>. This file contains document-specific metadata used to generate revision history, copyright, and contributor information. It follows a DTD specification included with the rest of the build system tools."
+msgstr "Cada pasta da língua primária do módulo do documento contém um ficheiro chamado filename>rpm-info.xml</filename>. Este ficheiro contém os metadados específicos do documento que são usados para gerir o histórico de revisões, direitos de cópia e a informação de contribuintes. Esta segue uma especificação em DTD que vem incluída com o resto das ferramentas do sistema de compilação."
+
+#: en_US/module-struct.xml:232(title)
+msgid "Build System Actions"
+msgstr "Acções do Sistema de Compilação"
+
+#: en_US/module-struct.xml:233(para)
+msgid "To render the <abbrev>XML</abbrev> document into another format, use one of the following <command>make</command> targets:"
+msgstr "Para representar o documento em <abbrev>XML</abbrev> noutro formato, use um dos seguintes alvos do <command>make</command>:"
+
+#: en_US/module-struct.xml:238(title)
+msgid "Build Targets"
+msgstr "Alvos de Compilação"
+
+#: en_US/module-struct.xml:239(segtitle)
+msgid "Target"
+msgstr "Alvo"
+
+#: en_US/module-struct.xml:242(systemitem)
+msgid "help"
+msgstr "ajuda"
+
+#: en_US/module-struct.xml:243(seg)
+msgid "This target prints a list of available targets and their descriptions."
+msgstr "Este alvo imprime uma listagem dos alvos disponíveis e das suas descrições."
+
+#: en_US/module-struct.xml:247(systemitem)
+msgid "validate-xml"
+msgstr "validate-xml"
+
+#: en_US/module-struct.xml:248(firstterm)
+msgid "validates"
+msgstr "valida"
+
+#: en_US/module-struct.xml:248(seg)
+msgid "This target <placeholder-1/> the XML files to make sure they are not only well-formed, but follow the DTD. Some viewers of XML documents may not work correctly until you run this target. This target includes copying required entity files so that validating XML viewers work properly"
+msgstr "Este target <placeholder-1/> os ficheiros XML não só para garantir que estes estão bem formados, mas seguem o DTD. Algumas ferramentas utilizadas para a visualização de ficheiros XML podem não funcionar correctamente até que seja corrido o target. Este target inclui a cópia de entity files de modo a que as ferramentas utilizadas para a validação do XML funcione correctamente."
+
+#: en_US/module-struct.xml:256(systemitem)
+msgid "html"
+msgstr "html"
+
+#: en_US/module-struct.xml:257(abbrev)
+#: en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:293(abbrev)
+#: en_US/module-struct.xml:298(abbrev)
+msgid "HTML"
+msgstr "HTML"
+
+#: en_US/module-struct.xml:261(systemitem)
+#: en_US/module-struct.xml:271(systemitem)
+msgid "${DOCBASE}"
+msgstr "${DOCBASE}"
+
+#: en_US/module-struct.xml:262(systemitem)
+#: en_US/module-struct.xml:272(systemitem)
+msgid "${LANG}"
+msgstr "${LANG}"
+
+#: en_US/module-struct.xml:260(filename)
+msgid "<placeholder-1/>-<placeholder-2/>/"
+msgstr "<placeholder-1/>-<placeholder-2/>/"
+
+#: en_US/module-struct.xml:257(seg)
+msgid "This target builds the \"chunked\" <placeholder-1/> document for each defined translation. Output is placed in a separate directory named <placeholder-2/>. Each document section is a separate file within that directory."
+msgstr "Este alvo compila o documento <placeholder-1/> \"em blocos\" para cada tradução definida. O resultado é colocado numa pasta separada, chamada <placeholder-2/>. Cada secção do documento fica num ficheiro separado, dentro dessa pasta."
+
+#: en_US/module-struct.xml:267(systemitem)
+msgid "html-nochunks"
+msgstr "html-nochunks"
+
+#: en_US/module-struct.xml:270(filename)
+msgid "<placeholder-1/>-<placeholder-2/>.html"
+msgstr "<placeholder-1/>-<placeholder-2/>.html"
+
+#: en_US/module-struct.xml:268(seg)
+msgid "This target builds the \"non-chunked\" <placeholder-1/> document for each defined translation. Output is placed in a single file: <placeholder-2/>; no other files are created."
+msgstr "Este alvo gera o documento <placeholder-1/> \"inteiro\" para cada tradução definida. O resultado é colocado num único ficheiro: <placeholder-2/>; não são criados outros ficheiros."
+
+#: en_US/module-struct.xml:276(systemitem)
+msgid "pdf"
+msgstr "pdf"
+
+#: en_US/module-struct.xml:277(abbrev)
+#: en_US/module-struct.xml:278(abbrev)
+#: en_US/module-struct.xml:294(abbrev)
+#: en_US/module-struct.xml:299(abbrev)
+msgid "PDF"
+msgstr "PDF"
+
+#: en_US/module-struct.xml:277(seg)
+msgid "This target builds only the <placeholder-1/> document for all document languages. <placeholder-2/> production is currently erratic and may not work for your document."
+msgstr "Este alvo constrói apenas o documento <placeholder-1/> para todas as línguas do documento. A produção em <placeholder-2/> tem alguns problemas e poderá não funcionar para o seu documento."
+
+#: en_US/module-struct.xml:282(systemitem)
+msgid "tarball"
+msgstr "tarball"
+
+#: en_US/module-struct.xml:283(command)
+msgid "tar(1)"
+msgstr "tar(1)"
+
+#: en_US/module-struct.xml:283(seg)
+msgid "This target builds only the <placeholder-1/> archive for all document languages."
+msgstr "Este alvo constrói apenas o pacote <placeholder-1/> para todas as línguas do documento."
+
+#: en_US/module-struct.xml:287(systemitem)
+msgid "all"
+msgstr "all"
+
+#: en_US/module-struct.xml:288(seg)
+msgid "This target builds all targets listed above."
+msgstr "Este alvo constrói todos os alvos apresentados em cima."
+
+#: en_US/module-struct.xml:291(systemitem)
+#: en_US/module-struct.xml:300(filename)
+msgid "clean"
+msgstr "clean"
+
+#: en_US/module-struct.xml:293(emphasis)
+msgid "not"
+msgstr "não"
+
+#: en_US/module-struct.xml:292(seg)
+msgid "This target deletes any temporary, or generated files, but does <placeholder-1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr "Este alvo apaga todos os ficheiros temporários ou gerados, mas <placeholder-1/> apaga os ficheiros <placeholder-2/>, <placeholder-3/> ou pacotes."
+
+#: en_US/module-struct.xml:297(systemitem)
+msgid "distclean"
+msgstr "distclean"
+
+#: en_US/module-struct.xml:298(seg)
+msgid "This target erases all <placeholder-1/>, <placeholder-2/>, and archive files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr "Este alvo apaga todos os ficheiros <placeholder-1/>, <placeholder-2/> e de pacotes. Este alvo também invoca automaticamente o alvo <placeholder-3/>."
+
+#: en_US/module-struct.xml:305(title)
+msgid "PDF Generation is Erratic"
+msgstr "A Geração de PDFs tem Problemas"
+
+#: en_US/module-struct.xml:306(para)
+msgid "<abbrev>PDF</abbrev> production is currently erratic and may not work for your document."
+msgstr "A produção de <abbrev>PDF</abbrev> tem alguns problemas e poderá não funcionar para o seu documento."
+
+#: en_US/module-struct.xml:311(title)
+msgid "Adding or Changing Targets"
+msgstr "Adicionar ou Modificar os Alvos"
+
+#: en_US/module-struct.xml:312(para)
+msgid "To add a new target and rules, place them at the bottom of the document <filename>Makefile</filename>, below the <literal>include</literal> line. Follow your target definitions with a double colon, not a single colon. The double colon allows you to specify additional rules for existing targets, or to write rules for a new target."
+msgstr "Para adicionar um novo alvo e regras, coloque-as no fundo da <filename>Makefile</filename> do documento, por baixo da linha <literal>include</literal>. Siga as definições do seu alvo com dois-pontos duplos, não apenas um. Os dois-pontos duplos permitem-lhe definir regras adicionais para os alvos existentes ou escrever regras para um novo alvo."
+
+#: en_US/module-struct.xml:320(para)
+msgid "For more information on using <command>make(1)</command>, consult the online documentation with the command <command>info make</command> in a terminal."
+msgstr "Para mais informações sobre a utilização do <command>make(1)</command>, consulte a documentação 'online' com o comando <command>info make</command> num terminal."
+
+#: en_US/module-struct.xml:327(title)
+msgid "Using Document Image Files"
+msgstr "Usar os Ficheiros de Imagens do Documento"
+
+#: en_US/module-struct.xml:328(para)
+msgid "Tutorial documents often make use of images such as <filename class=\"extension\">.PNG</filename> files. Store image files in a <filename class=\"directory\">figs/</filename> folder in the main module directory, as shown in <xref linkend=\"ex-module-structure\"/>."
+msgstr "Os documentos de tutoriais normalmente utilizam imagens como os ficheiros <filename class=\"extension\">.PNG</filename>. Guarde os ficheiros de imagens numa pasta <filename class=\"directory\">figs/</filename> da pasta do módulo principal, como aparece em <xref linkend=\"ex-module-structure\"/>."
+
+#: en_US/module-struct.xml:335(para)
+msgid "Depending on the output media, sometimes images may be scaled, streteched, or squashed. To minimize any distortions, we recommend that you use only <filename class=\"extension\">.PNG</filename> images. Avoid <filename class=\"extension\">.JPG</filename> files. The <command>convert(1)</command> program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</abbrev> package, provides a convenient way to reformat <filename class=\"extension\">.JPG</filename> images into <filename class=\"extension\">.PNG</filename> format. For more information on formatting images such as screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr "Dependendo do formato de saída, algumas das imagens poderão ser esticadas, encolhidas ou desfeitas. Para minimizar as distorções, recomenda-se que use apenas as imagens <filename class=\"extension\">.PNG</filename>. Evite os ficheiros <filename class=\"extension\">.JPG</filename>. O programa <command>convert(1)</command>, do pacote <abbrev>RPM</abbrev> <package role=\"rpm\">ImageMagick</package>, oferece uma forma conveniente de formatar de novo as <filename class=\"extension\">.JPG</filename> no formato <filename class=\"extension\">.PNG</filename>. Para mais informações sobre a formatação das imagens, veja em <xref linkend=\"sn-screenshots\"/>."
+
+#: en_US/module-struct.xml:349(para)
+msgid "Image files may be organized into subdirectories under <filename>figs/</filename> if necessary. The document building system recreates the image subdirectory structure in the output documents."
+msgstr "Os ficheiros de imagens poderão estar organizados em sub-pastas da <filename>figs/</filename>, se necessário. O sistema de compilação de documentos irá criar de novo a estrutura de sub-pastas das imagens nos documentos resultantes."
+
+#: en_US/module-struct.xml:355(para)
+msgid "Images often contain labels or other text which may need to be localized. A screenshot of a program, for example, may require a version for each translated language. Name language-dependent image files such as program screenshots by adding the language code to the filename, such as <filename>menu-en_US.png</filename>. Language-independent images, such as <filename>icon.png</filename>, do not need language codes."
+msgstr "As imagens contêm normalmente legendas ou outros textos que possam ter de ser traduzidos. Uma imagem de um programa, por exemplo, poderá necessitar de uma versão para cada língua traduzida. Dê um nome dependente da língua aos ficheiros de imagens, adicionando o código da língua ao nome do ficheiro, como acontece em <filename>menu-pt.png</filename>. As imagens independentes da língua, como o <filename>icon.png</filename>, não precisam de códigos de línguas."
+
+#: en_US/module-struct.xml:365(para)
+msgid "Sometimes, a document may require images that do not follow the naming convention. To use these images with the document building system, create an ordinary text file containing the image filenames. This file must be named <filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</systemitem> so the build system finds it when searching for image filenames."
+msgstr "Em alguns casos, um documento poderá necessitar de imagens que não sigam a nomenclatura. Para usar estas imagens com o sistema de compilação do documento, crie um ficheiro de texto normal que contém os nomes dos ficheiros de imagens. Este ficheiro dever-se-á chamar <filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</systemitem>, de modo que o sistema de compilação o descubra quando procurar pelos nomes dos ficheiros de imagens."
+
+#: en_US/module-struct.xml:374(para)
+msgid "<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one way to create this <filename>Manifest</filename> file."
+msgstr "O <xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstra uma forma de criar este ficheiro <filename>Manifest</filename>."
+
+#: en_US/module-struct.xml:380(title)
+msgid "Building A Manifest"
+msgstr "Criar um Manifest"
+
+#: en_US/module-struct.xml:387(title)
+msgid "Adding a New DocBook XML File"
+msgstr "Adicionar um Novo Ficheiro de DocBook em XML"
+
+#: en_US/module-struct.xml:388(para)
+msgid "To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr "Para adicionar um novo ficheiro de DocBook em XML a um documento existente, siga estes passos:"
+
+#: en_US/module-struct.xml:392(para)
+msgid "Place the new DocBook XML file in the primary language directory."
+msgstr "Coloque o novo ficheiro de DocBook em XML na pasta da língua primária."
+
+#: en_US/module-struct.xml:396(para)
+msgid "Edit the <filename>Makefile</filename> and add the filename to the <varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to the last existing line, and on the next line add an entry for the new file. Remember to add the <literal>${1}/</literal> prefix as a substitute for the language directory name."
+msgstr "Edite a <filename>Makefile</filename> e adicione o nome do ficheiro à listagem <varname>XMLFILES-${1}</varname>. Adicione uma <keycap>\\</keycap> à última linha existente e, na linha seguinte, adicione um item para o novo ficheiro. Lembre-se de adicionar o prefixo <literal>${1}/</literal> como substituto para o nome da pasta da língua."
+
+#: en_US/module-struct.xml:406(title)
+msgid "Adding a Translation"
+msgstr "Adicionar uma Tradução"
+
+#: en_US/module-struct.xml:407(para)
+msgid "Translations are stored as PO (portable object) files, which the toolchain transforms into translated documents. Each PO file is based on the POT (PO template) for the document and translated by the Fedora Translation Project. To add a translation, follow these steps:"
+msgstr "As traduções são guardadas como ficheiros PO (portable object - objecto portável), que o conjunto de ferramentas irá transformar em documentos traduzidos. Cada um dos ficheiros PO baseia-se no POT (modelo de PO) do documento e é traduzido pelo Projecto de Traduções do Fedora. Para adicionar uma tradução, siga estes passos:"
+
+#: en_US/module-struct.xml:414(para)
+msgid "If the <filename class=\"directory\">po/</filename> directory does not exist, create it and add it to CVS:"
+msgstr "Se a pasta <filename class=\"directory\">po/</filename> não existir, crie-a e adicione-a ao CVS:"
+
+#: en_US/module-struct.xml:420(para)
+msgid "If it does not exist, create the POT file:"
+msgstr "Se este não existir, crie o ficheiro POT:"
+
+#: en_US/module-struct.xml:424(para)
+msgid "Add the new translation language to the <varname>OTHERS</varname> listing in the <filename>Makefile</filename>."
+msgstr "Adicione a nova língua da tradução à listagem do <varname>OTHERS</varname> na <filename>Makefile</filename>."
+
+#: en_US/module-struct.xml:429(para)
+msgid "Although translators often copy the POT manually to create the new PO file, the following command also works:"
+msgstr "Ainda que os tradutores copiem normalmente de forma manual o ficheiro POT para criar o novo ficheiro PO, o seguinte comando também funciona:"
+
+#: en_US/module-struct.xml:432(replaceable)
+msgid "lang"
+msgstr "língua"
+
+#: en_US/module-struct.xml:432(screen)
+#, no-wrap
+msgid "make po/<placeholder-1/>.po"
+msgstr "make po/<placeholder-1/>.po"
+
+#: en_US/intro.xml:13(title)
+msgid "Introduction"
+msgstr "Introdução"
+
+#: en_US/intro.xml:15(para)
+msgid "The goal of the Fedora Documentation Project is to create easy-to-follow, task-based documentation for Fedora users and developers. The Fedora Documentation Project uses the following tools:"
+msgstr "O objectivo do Projecto de Documentação do Fedora é criar documentação simples de usar, baseada em tarefas, para os utilizadores e programadores do Fedora. O Projecto de Documentação do Fedora usa as seguintes ferramentas:"
+
+#: en_US/intro.xml:23(para)
+msgid "DocBook XML v4.4"
+msgstr "DocBook XML v4.4"
+
+#: en_US/intro.xml:26(para)
+msgid "Custom XSLT stylesheets for both print and HTML versions"
+msgstr "Folhas de estilo XSLT personalizadas para as versões impressas e em HTML"
+
+#: en_US/intro.xml:30(para)
+msgid "Custom scripts to generate HTML output (use <command>xmlto</command>)"
+msgstr "Programas personalizados para gerar o resultado em HTML (use o <command>xmlto</command>)"
+
+#: en_US/intro.xml:34(para)
+msgid "Emacs with PSGML mode (optional, but recommended)"
+msgstr "Emacs com o modo PSGML (opcional, mas recomendado)"
+
+#: en_US/intro.xml:43(para)
+msgid "This document explains the tools used by the Fedora Documentation Project. It provides writing and tagging guidelines to ensure Fedora documentation is consistent and easy-to-follow."
+msgstr "Este documento explica as ferramentas usadas pelo Projecto de Documentação do Fedora e oferece algumas recomendações de escrita e marcação que tornam a documentação do Fedora consistente e fácil de seguir."
+
+#: en_US/getting-files.xml:12(title)
+msgid "Prerequisites"
+msgstr "Pré-requisitos"
+
+#: en_US/getting-files.xml:14(para)
+msgid "To work on official Fedora documentation you need to install the required tools. Follow the directions below to configure your system."
+msgstr "Para lidar com a documentação oficial do Fedora, terá de instalar as seguintes ferramentas. Siga as instruções abaixo para configurar o seu sistema."
+
+#: en_US/getting-files.xml:20(title)
+msgid "System Packages"
+msgstr "Pacotes do Sistema"
+
+#: en_US/getting-files.xml:22(para)
+msgid "Install the \"Authoring and Publishing\" package group, which contains required DocBook XML files, stylesheets and scripts:"
+msgstr "Instale o grupo de pacotes \"Authoring and Publishing\" (Autoria e Publicações), que contém os ficheiros de DocBook em XML necessários, as folhas de estilo e os programas:"
+
+#: en_US/getting-files.xml:28(userinput)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+msgstr "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+
+#: en_US/getting-files.xml:31(para)
+msgid "Next, install the <filename>cvs</filename> package, which is used to handle revision control on files in the official repository:"
+msgstr "De seguida, instale o pacote <filename>cvs</filename>, que é usado para lidar com o controlo de versões nos ficheiros do repositório oficial:"
+
+#: en_US/getting-files.xml:37(userinput)
+#, no-wrap
+msgid "su -c 'yum install cvs'"
+msgstr "su -c 'yum install cvs'"
+
+#: en_US/getting-files.xml:40(para)
+msgid "If you plan to use <application>Emacs</application> to edit DocBook XML documentation, install <package>psgml</package>, which adds helpful and time-saving functionality to maximize editing efficiency:"
+msgstr "Se pensar em usar o <application>Emacs</application> para editar a documentação DocBook em XML, instale o pacote <package>psgml</package>, que adiciona funcionalidades úteis e de poupança de tempo, de modo a maximizar a eficiência na edição:"
+
+#: en_US/getting-files.xml:44(userinput)
+#, no-wrap
+msgid "su -c 'yum install psgml'"
+msgstr "su -c 'yum install psgml'"
+
+#: en_US/getting-files.xml:48(title)
+msgid "Fedora Documentation Tools"
+msgstr "Ferramentas de Documentação do Fedora"
+
+#: en_US/getting-files.xml:50(para)
+msgid "The Fedora Documentation Project's custom scripts and stylesheets are stored in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</systemitem> CVS server. When you check out a document module from CVS, the tools are included in the module inside the <filename class=\"directory\">docs-common/</filename> directory. To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr "Os programas e folhas de estilo personalizados do Projecto de Documentação do Fedora estão guardados em CVS, no servidor <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</systemitem>. Quando transfere um módulo de documentos do CVS, s ferramentas vão incluídas no módulo, dentro da pasta <filename class=\"directory\">docs-common/</filename>. Para trabalhar sobre documentos existentes no CVS, consulte a secção <xref linkend=\"ch-cvs\"/>."
+
+#: en_US/getting-files.xml:59(para)
+msgid "The most powerful component in the Fedora Documentation Project toolbox is <firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for authoring technical documentation using <firstterm>Extensible Markup Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark pieces of content with descriptive tags. The following output is an example of DocBook XML:"
+msgstr "O componente mais poderoso no pacote de ferramentas do Projecto de Documentação do Fedora é o <firstterm>DocBook XML</firstterm>. O DocBook XML é um esquema específico para gerar documentação técnica, usando a <firstterm>Extensible Markup Language</firstterm> ou <acronym>XML</acronym>. O XML permite aos autores marcarem certas partes de conteúdo com marcas descritivas. Segue-se um exemplo de DocBook XML:"
+
+#: en_US/getting-files.xml:76(para)
+msgid "This example article, entitled <citetitle>A Very Short Article</citetitle>, consists of only a single paragraph. The tags, or markup, surround elements of content to define the sense in which they are used. A paragraph, for example, is marked with <sgmltag>para</sgmltag> tags. Text that requires emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does not worry about the visual formatting such as italics or font size. Fedora Documentation Project build tools automatically perform all formatting tasks."
+msgstr "Este artigo de exemplo, chamado <citetitle>Um Artigo Muito Curto</citetitle>, consiste apenas num único parágrafo. As marcas de formatação reúnem os elementos de conteúdo para definirem o sentido em que são usadas. Um parágrafo, por exemplo, é rodeado com marcas <sgmltag>para</sgmltag>. O texto que necessite de ênfase está marcado com <sgmltag>emphasis</sgmltag>. O autor não se irá preocupar com a formatação visual, como os itálicos ou o tamanho da letra. As ferramentas de compilação do Projecto de Documentação do Fedora efectuam todas as tarefas de formatação."
+
+#: en_US/getting-files.xml:85(para)
+msgid "The custom tools built by the Fedora Documentation Project render DocBook source into a variety of formats for publication and distribution. They also allow translators to create localized versions of the XML documents for Fedora users around the world. The flexibility of XML allows for a single document to be used many times for many purposes, like reusable code for a programmer."
+msgstr "As ferramentas personalizadas, criadas pelo Projecto de Documentação do Fedora, representam o código em DocBook numa variedade de formatos para publicação e distribuição. Também permitem aos tradutores criarem versões locais dos documentos de XML, para os utilizadores de Fedora em todo o mundo. A flexibilidade do XML permite a um único documento ser usado várias vezes para diversos fins, como a reutilização de código para um programador."
+
+#: en_US/getting-files.xml:91(para)
+msgid "DocBook is itself very well documented. For more information about DocBook, visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also features complete copies of <citetitle>DocBook: The Definitive Guide</citetitle> to browse and download, the canonical source for DocBook information."
+msgstr "O DocBook está em si muito bem documentado. Para mais informações acerca do DocBook, visite a página <ulink url=\"http://www.docbook.org/\"/>. A página do DocBook também contém cópias completas do livro <citetitle>DocBook: The Definitive Guide</citetitle> para navegar e transferir, sendo esta a fonte canónica de informação sobre o DocBook."
+
+#: en_US/getting-files.xml:97(title)
+msgid "DocBook XML Versions"
+msgstr "Versões do DocBook XML"
+
+#: en_US/getting-files.xml:98(para)
+msgid "DocBook XML, like a computer program, has version numbers. The version used by Fedora Documentation Project right now is 4.4. The DocBook web site may document a slightly newer version, but the majority of the schema still applies."
+msgstr "O DocBook XML, como um programa de computador, tem números de versões. A versão usada no Projecto de Documentação do Fedora neste momento é a 4.4. A página Web do DocBook poderá conter uma versão ligeiramente mais recente, mas a maioria do esquema aplica-se à mesma."
+
+#: en_US/getting-files.xml:103(para)
+msgid "Contributors who use the Microsoft Windows operating system can still make use of DocBook tools. For more information, refer to <ulink url=\"http://www.codeproject.com/winhelp/docbook_howto.asp\"/>."
+msgstr "Colaboradores que utilizem o sistema operativo Microsoft Windows podem usar as ferramentas DocBook. Para mais informações consulte <ulink url=\"http://www.codeproject.com/winhelp/docbook_howto.asp\"/>."
+
+#: en_US/getting-files.xml:110(title)
+msgid "Naming Conventions"
+msgstr "Convenções dos Nomes"
+
+#: en_US/getting-files.xml:111(para)
+msgid "The Fedora Documentation Project provides the tools, scripts, and stylesheets to transform your <abbrev>XML</abbrev> documents into other output formats such as <abbrev>HTML</abbrev>. In addition, these tools can build your document into a <abbrev>RPM</abbrev> package. To take advantage of these services, follow the conventions in this section to name your files."
+msgstr "O Projecto de Documentação do Fedora oferece as ferramentas, programas e folhas de estilo que transformam os seus documentos em <abbrev>XML</abbrev> noutros formatos resultantes, como o <abbrev>HTML</abbrev>. Para além disso, estas ferramentas podem transformar o seu documento num pacote <abbrev>RPM</abbrev>. Para tirar partido destes serviços, deverá seguir as convenções de nomenclatura dos seus ficheiros."
+
+#: en_US/getting-files.xml:119(para)
+msgid "On the CVS server, directories that contain document files are called <firstterm>modules</firstterm>. Each module represents a single document. Each document may consist of several <firstterm>branches</firstterm> if that document changes with each release of Fedora. Contributors can check out single branches of these modules or the entire module. Each document or branch may contain multiple XML source files."
+msgstr "No servidor de CVS, as pastas que contêm os ficheiros de documentos chamam-se <firstterm>módulos</firstterm>. Cada módulo representa um único documento. Cada documento poderá consistir em várias <firstterm>ramificações</firstterm>, se esse documento for alterado em cada versão do Fedora. Os contribuintes poderão obter ramificações únicas desses módulos ou então o módulo inteiro. Cada documento ou ramificação poderá conter vários ficheiros em XML."
+
+#: en_US/getting-files.xml:126(para)
+msgid "Use the <command>cvs co -c</command> command to view existing module names."
+msgstr "Use sempre o comando <command>cvs co -c</command> para ver os nomes dos módulos existentes."
+
+#: en_US/getting-files.xml:129(title)
+msgid "Partial List of CVS Modules"
+msgstr "Lista Parcial dos Módulos do CVS"
+
+#: en_US/getting-files.xml:130(userinput)
+#, no-wrap
+msgid "cd ~/localrepo/fedora-docs/"
+msgstr "cd ~/repositorio-local/fedora-docs/"
+
+#: en_US/getting-files.xml:149(para)
+msgid "The leftmost entry in each line is the name of a module you can check out from CVS. The rest of the line ensures that checkouts include the proper branch of a document and the common build tools. For more information on CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr "O item mais à esquerda de cada linha é o nome de um módulo que poderá transferir do CVS. O restante da linha garante que as transferências incluem a ramificação correcta de um documento, assim como as ferramentas de compilação comuns. Para mais informações sobre o CVS, consulte em <xref linkend=\"ch-cvs\"/>."
+
+#: en_US/getting-files.xml:154(para)
+msgid "Note in the listing above that the <systemitem>about-fedora</systemitem> module has two branches available. One branch is for Fedora 7 and one is for forward development to match the current work of developers. On the other hand, the <systemitem>documentation-guide</systemitem> module is not branched."
+msgstr "Repare na listagem acima que o módulo <systemitem>about-fedora</systemitem> tem duas ramificações disponíveis. Uma é para o Fedora 7 e outra é para a versão em desenvolvimento posterior, reflectindo o trabalho actual dos programadores. Por outro lado, o módulo <systemitem>documentation-guide</systemitem> não tem ramificações."
+
+#: en_US/getting-files.xml:161(title)
+msgid "Modules Labeled <filename>-dir</filename>"
+msgstr "Módulos Chamados <filename>-dir</filename>"
+
+#: en_US/getting-files.xml:162(para)
+msgid "Modules ending with the suffix <filename>-dir</filename> are not usually helpful to checkout directly. These modules do not include the common build tools and thus do not provide many of the functions contributors require."
+msgstr "Os módulos que terminam com o sufixo <filename>-dir</filename> não são normalmente úteis para transferir directamente. Estes módulos não incluem as ferramentas de compilação comuns e, deste modo, não oferecem muitas das funções que os contribuintes necessitam."
+
+#: en_US/getting-files.xml:168(title)
+msgid "Module Names"
+msgstr "Nomes dos Módulos"
+
+#: en_US/getting-files.xml:169(para)
+msgid "Choose a module name that accurately reflects your document's subject, but avoid any name already taken. The document title without any use of the word <wordasword>fedora</wordasword> is a reasonable choice in most cases. Use the length descriptors <wordasword>tutorial</wordasword> or <wordasword>guide</wordasword> in the module name where appropriate."
+msgstr "Escolha um nome de módulo que reflicta com precisão o assunto do seu documento, mas evite um nome que já tenha sido usado. O título do documento sem usar a palavra <wordasword>fedora</wordasword> é normalmente uma escolha razoável na maioria dos casos. Use as descrições da dimensão <wordasword>tutorial</wordasword> ou <wordasword>guide</wordasword> (guia) no nome do módulo, se for apropriado."
+
+#: en_US/getting-files.xml:178(title)
+msgid "Avoid Redundancy"
+msgstr "Evite Redundâncias"
+
+#: en_US/getting-files.xml:179(para)
+msgid "Do not use the word <wordasword>fedora</wordasword> to name modules in the Fedora Documentation Project CVS repository."
+msgstr "Não use a palavra <wordasword>fedora</wordasword> no nome dos módulos do repositório de CVS do Projecto de Documentação do Fedora."
+
+#: en_US/getting-files.xml:185(title)
+msgid "Correct Module Naming"
+msgstr "Nomenclatura de Módulos Correcta"
+
+#: en_US/getting-files.xml:186(segtitle)
+msgid "Document Name"
+msgstr "Nome do Documento"
+
+#: en_US/getting-files.xml:187(segtitle)
+msgid "CVS Module Name"
+msgstr "Nome do Módulo de CVS"
+
+#: en_US/getting-files.xml:189(seg)
+msgid "Desktop User Guide"
+msgstr "Guia do Utilizador do Ambiente de Trabalho"
+
+#: en_US/getting-files.xml:190(seg)
+msgid "desktop-user-guide"
+msgstr "desktop-user-guide"
+
+#: en_US/getting-files.xml:194(application)
+msgid "Yum"
+msgstr "Yum"
+
+#: en_US/getting-files.xml:193(seg)
+msgid "Software Management with <placeholder-1/>"
+msgstr "Gestão de Software com o <placeholder-1/>"
+
+#: en_US/getting-files.xml:195(seg)
+msgid "yum-guide"
+msgstr "yum-guide"
+
+#: en_US/getting-files.xml:198(application)
+msgid "Pup"
+msgstr "Pup"
+
+#: en_US/getting-files.xml:198(seg)
+msgid "Using <placeholder-1/>"
+msgstr "A utilizar<placeholder-1/>"
+
+#: en_US/getting-files.xml:199(seg)
+msgid "pup-tutorial"
+msgstr "pup-tutorial"
+
+#: en_US/getting-files.xml:204(title)
+msgid "File Names"
+msgstr "Nomes dos Ficheiros"
+
+#: en_US/getting-files.xml:205(para)
+msgid "Follow these guidelines for naming files to make collaboration and document reuse easy:"
+msgstr "Siga estas convenções para nomear os ficheiros, de modo a tornar a colaboração e a reutilização de documentos mais simples:"
+
+#: en_US/getting-files.xml:209(para)
+msgid "As with module names, avoid using the word <wordasword>fedora</wordasword> in file names since it is redundant."
+msgstr "Como no nome dos módulos, evite usar a palavra <wordasword>fedora</wordasword> nos nomes dos ficheiros, dado que é redundante."
+
+#: en_US/getting-files.xml:214(para)
+msgid "If the document is comprised of many XML files, avoid repeating the name of the document when naming the constituent files."
+msgstr "Se o documento for composto por muitos ficheiros XML, evite repetir o nome do documento ao criar os ficheiros constituintes."
+
+#: en_US/getting-files.xml:219(para)
+msgid "Avoid numbering files to show order, since editors and authors often rearrange documents or reuse their files in other documents."
+msgstr "Evite numerar os ficheiros para demonstrar a ordem, dado que os editores e autores normalmente reorganizam os documentos ou reutilizam os seus ficheiros noutros documentos."
+
+#: en_US/emacs.xml:13(title)
+msgid "Emacs and PSGML Mode"
+msgstr "O Emacs e o Modo PSGML"
+
+#: en_US/emacs.xml:16(primary)
+msgid "PSGML"
+msgstr "PSGML"
+
+#: en_US/emacs.xml:20(primary)
+#: en_US/emacs.xml:24(primary)
+#: en_US/emacs.xml:43(primary)
+#: en_US/emacs.xml:224(primary)
+#: en_US/emacs.xml:233(primary)
+#: en_US/emacs.xml:238(primary)
+#: en_US/emacs.xml:243(primary)
+#: en_US/emacs.xml:523(application)
+#: en_US/emacs-nxml.xml:18(primary)
+#: en_US/emacs-nxml.xml:22(primary)
+msgid "Emacs"
+msgstr "Emacs"
+
+#: en_US/emacs.xml:25(secondary)
+msgid "PSGML mode"
+msgstr "Modo PSGML"
+
+#: en_US/emacs.xml:28(para)
+msgid "You can use the PSGML mode available for Emacs to make it easier to write in XML format. PSGML mode provides syntax-highlighting, tag completion, and more."
+msgstr "Poderá usar o modo PSGML, que está disponível para o Emacs, de modo a ser mais fácil de escrever no formato XML. O modo PSGML oferece o realce de sintaxe, a completação de marcas, etc."
+
+#: en_US/emacs.xml:35(title)
+msgid "Installing PSGML"
+msgstr "Instalar o PSGML"
+
+#: en_US/emacs.xml:36(para)
+msgid "To install PSGML, use the <command>yum</command> command:"
+msgstr "Para instalar o PSGML, use o comando <command>yum</command>:"
+
+#: en_US/emacs.xml:37(userinput)
+#, no-wrap
+msgid "yum install psgml"
+msgstr "yum install psgml"
+
+#: en_US/emacs.xml:40(title)
+msgid "Setting Up Your <filename>.emacs</filename> File"
+msgstr "Configurar o seu Ficheiro <filename>.emacs</filename>"
+
+#: en_US/emacs.xml:48(filename)
+msgid ".emacs"
+msgstr ".emacs"
+
+#: en_US/emacs.xml:51(para)
+msgid "For Emacs to parse your DocBook documents correctly, you must have a <filename>.emacs</filename> file. Cut and paste the following into your existing <filename>.emacs</filename> file or create a new one that contains the following lines:"
+msgstr "Para o Emacs processar correctamente os seus documentos em DocBook, deverá ter um ficheiro <filename>.emacs</filename>. Corte e cole o seguinte no seu ficheiro <filename>.emacs</filename> existente ou crie um novo que contenha as seguintes linhas:"
+
+#: en_US/emacs.xml:181(para)
+msgid "If you have a wheel mouse and are using Emacs version 21, you can add the following to your <filename>.emacs</filename> file so your wheel will work in <application>Emacs</application>:"
+msgstr "Se tiver um rato com roda e estiver a usar o Emacs versão 21, poderá adicionar o seguinte ao seu ficheiro <filename>.emacs</filename>, para que a roda do seu rato funcione no <application>Emacs</application>:"
+
+#: en_US/emacs.xml:192(para)
+msgid "If you are using the older version 20 of <application>Emacs</application>, add the following instead:"
+msgstr "Se estiver a usar a versão anterior - a 20 - do <application>Emacs</application>, adicione o seguinte comando:"
+
+#: en_US/emacs.xml:221(title)
+msgid "Customizing Emacs"
+msgstr "Personalizar o Emacs"
+
+#: en_US/emacs.xml:225(secondary)
+msgid "customizing"
+msgstr "personalização"
+
+#: en_US/emacs.xml:229(filename)
+msgid ".Xresources"
+msgstr ".Xresources"
+
+#: en_US/emacs.xml:234(secondary)
+msgid "colors"
+msgstr "cores"
+
+#: en_US/emacs.xml:239(secondary)
+msgid "font"
+msgstr "tipo de letra"
+
+#: en_US/emacs.xml:244(secondary)
+msgid "geometry"
+msgstr "geometria"
+
+#: en_US/emacs.xml:247(para)
+msgid "The colors, font, and geometry (default size of window) for Emacs in your <filename>~/.Xresources</filename> file. The format for the settings is <userinput>emacs.keyword:value</userinput>."
+msgstr "As cores, tipos de letra e geometria (tamanho predefinido da janela) do Emacs no seu ficheiro <filename>~/.Xresources</filename>. O formato da configuração é <computeroutput>emacs.palavra-chave:valor</computeroutput>."
+
+#: en_US/emacs.xml:253(para)
+msgid "The following is a sample <filename>~/.Xresources</filename> file."
+msgstr "Segue-se um exemplo de um ficheiro <filename>~/.Xresources</filename>."
+
+#: en_US/emacs.xml:258(para)
+msgid "If you have other settings in your <filename>~/.Xresources</filename>, add the following to the end of the file."
+msgstr "Se tiver outras configurações no seu ficheiro <filename>~/.Xresources</filename>, adicione o seguinte ao fim do ficheiro."
+
+#: en_US/emacs.xml:270(para)
+msgid "After modifying this file, execute the following command:"
+msgstr "Depois de modificar este ficheiro, execute o seguinte comando:"
+
+#: en_US/emacs.xml:273(command)
+msgid "xrdb -merge ~/.Xresources"
+msgstr "xrdb -merge ~/.Xresources"
+
+#: en_US/emacs.xml:274(para)
+msgid "Then restart <application>Emacs</application> to apply the changes."
+msgstr "Depois reinicie o <application>Emacs</application> para as alterações fazerem efeito."
+
+#: en_US/emacs.xml:395(title)
+msgid "Basic Emacs Commands"
+msgstr "Comandos Básicos do Emacs"
+
+#: en_US/emacs.xml:397(para)
+msgid "The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key."
+msgstr "A tecla <keycap>Meta</keycap> normalmente é a tecla <keycap>Alt</keycap>."
+
+#: en_US/emacs.xml:403(title)
+msgid "Emacs Commands"
+msgstr "Comandos do Emacs"
+
+#: en_US/emacs.xml:404(segtitle)
+msgid "Shortcut"
+msgstr "Atalho"
+
+#: en_US/emacs.xml:405(segtitle)
+msgid "Description"
+msgstr "Descrição"
+
+#: en_US/emacs.xml:408(keycap)
+#: en_US/emacs.xml:412(keycap)
+#: en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:443(keycap)
+#: en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:458(keycap)
+#: en_US/emacs.xml:463(keycap)
+#: en_US/emacs.xml:468(keycap)
+#: en_US/emacs.xml:473(keycap)
+#: en_US/emacs.xml:478(keycap)
+#: en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:508(keycap)
+#: en_US/emacs.xml:509(keycap)
+#: en_US/emacs.xml:514(keycap)
+#: en_US/emacs.xml:515(keycap)
+#: en_US/emacs.xml:520(keycap)
+#: en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:533(keycap)
+#: en_US/emacs.xml:540(keycap)
+#: en_US/emacs.xml:542(keycap)
+msgid "Ctrl"
+msgstr "Ctrl"
+
+#: en_US/emacs.xml:409(keycap)
+#: en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:540(keycap)
+#: en_US/emacs.xml:542(keycap)
+msgid "c"
+msgstr "c"
+
+#: en_US/emacs.xml:413(keycap)
+msgid "p"
+msgstr "p"
+
+#: en_US/emacs.xml:407(seg)
+#: en_US/emacs.xml:508(seg)
+#: en_US/emacs.xml:514(seg)
+#: en_US/emacs.xml:520(seg)
+#: en_US/emacs.xml:532(seg)
+#: en_US/emacs.xml:540(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+
+#: en_US/emacs.xml:415(seg)
+msgid "Parse DTD"
+msgstr "Processar a DTD"
+
+#: en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:437(keycap)
+msgid "Shift"
+msgstr "Shift"
+
+#: en_US/emacs.xml:432(keycap)
+#: en_US/emacs.xml:438(keycap)
+msgid ","
+msgstr ","
+
+#: en_US/emacs.xml:432(keycap)
+#: en_US/emacs.xml:439(keycap)
+msgid "Tab"
+msgstr "Tab"
+
+#: en_US/emacs.xml:430(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+
+#: en_US/emacs.xml:433(seg)
+msgid "Display list of valid tags"
+msgstr "Mostra uma lista com as marcas válidas"
+
+#: en_US/emacs.xml:436(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of tag, <placeholder-5/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, escrever o início da marca, <placeholder-5/>"
+
+#: en_US/emacs.xml:440(seg)
+msgid "Complete the tag"
+msgstr "Complete a etiqueta"
+
+#: en_US/emacs.xml:443(keycap)
+msgid "g"
+msgstr "G"
+
+#: en_US/emacs.xml:445(seg)
+msgid "Cancel a command in the minibuffer"
+msgstr "Cancela um comando na mini-linha de comandos"
+
+#: en_US/emacs.xml:449(keycap)
+msgid "/"
+msgstr "/"
+
+#: en_US/emacs.xml:448(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+
+#: en_US/emacs.xml:450(seg)
+msgid "Close tag"
+msgstr "Fecha a marca"
+
+#: en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:533(keycap)
+msgid "a"
+msgstr "A"
+
+#: en_US/emacs.xml:455(seg)
+msgid "Move cursor to beginning of line"
+msgstr "Move o cursor para o início da linha"
+
+#: en_US/emacs.xml:458(keycap)
+msgid "e"
+msgstr "E"
+
+#: en_US/emacs.xml:460(seg)
+msgid "Move cursor to the end of the line"
+msgstr "Move o cursor para o fim da linha"
+
+#: en_US/emacs.xml:463(keycap)
+msgid "Home"
+msgstr "Home"
+
+#: en_US/emacs.xml:465(seg)
+msgid "Move cursor to the beginning of the file"
+msgstr "Move o cursor para o início do ficheiro"
+
+#: en_US/emacs.xml:468(keycap)
+msgid "End"
+msgstr "End"
+
+#: en_US/emacs.xml:470(seg)
+msgid "Move cursor to the end of the file"
+msgstr "Move o cursor para o fim do ficheiro"
+
+#: en_US/emacs.xml:473(keycap)
+msgid "k"
+msgstr "K"
+
+#: en_US/emacs.xml:475(seg)
+msgid "Cut line"
+msgstr "Corta a linha"
+
+#: en_US/emacs.xml:478(keycap)
+msgid "y"
+msgstr "Y"
+
+#: en_US/emacs.xml:480(seg)
+msgid "Paste line"
+msgstr "Cola a linha"
+
+#: en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:515(keycap)
+msgid "s"
+msgstr "S"
+
+#: en_US/emacs.xml:485(seg)
+msgid "Search forward in the file"
+msgstr "Procura para a frente no ficheiro"
+
+#: en_US/emacs.xml:488(keycap)
+msgid "r"
+msgstr "R"
+
+#: en_US/emacs.xml:490(seg)
+msgid "Search backwards in the file"
+msgstr "Procura para trás no ficheiro"
+
+#: en_US/emacs.xml:493(keycap)
+#: en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:527(keycap)
+msgid "Meta"
+msgstr "Meta"
+
+#: en_US/emacs.xml:493(keycap)
+msgid "$"
+msgstr "$"
+
+#: en_US/emacs.xml:495(seg)
+#: en_US/emacs.xml:500(seg)
+msgid "Check spelling of current word"
+msgstr "Verifica a ortografia da palavra actual"
+
+#: en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:508(keycap)
+#: en_US/emacs.xml:514(keycap)
+#: en_US/emacs.xml:520(keycap)
+msgid "x"
+msgstr "x"
+
+#: en_US/emacs.xml:499(keycap)
+#: en_US/emacs.xml:504(keycap)
+msgid "Enter"
+msgstr "Enter"
+
+#: en_US/emacs.xml:498(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, <placeholder-3/>"
+
+#: en_US/emacs.xml:503(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, <placeholder-3/>"
+
+#: en_US/emacs.xml:505(seg)
+msgid "Check spelling of current buffer"
+msgstr "Verifica a ortografia da página actual"
+
+#: en_US/emacs.xml:509(keycap)
+msgid "f"
+msgstr "f"
+
+#: en_US/emacs.xml:511(seg)
+msgid "Open file"
+msgstr "Abrir um ficheiro"
+
+#: en_US/emacs.xml:517(seg)
+msgid "Save file"
+msgstr "Gravar um ficheiro"
+
+#: en_US/emacs.xml:523(seg)
+msgid "Exit <placeholder-1/> and prompt to save files if necessary"
+msgstr "Sai do <placeholder-1/> e pede para gravar os ficheiros, se necessário"
+
+#: en_US/emacs.xml:527(keycap)
+msgid "q"
+msgstr "Q"
+
+#: en_US/emacs.xml:529(seg)
+msgid "Fill paragraph"
+msgstr "Preenche o parágrafo"
+
+#: en_US/emacs.xml:536(computeroutput)
+#, no-wrap
+msgid "url"
+msgstr "url"
+
+#: en_US/emacs.xml:537(computeroutput)
+#, no-wrap
+msgid "ulink"
+msgstr "ulink"
+
+#: en_US/emacs.xml:535(seg)
+msgid "Edit attributes for a tag (for example, you can edit the <placeholder-1/> attribute of the <placeholder-2/> tag)"
+msgstr "Edita os atributos de uma marca (por exemplo, poderá editar o atributo <placeholder-1/> da marca <placeholder-2/>)"
+
+#: en_US/emacs.xml:544(seg)
+msgid "Exit edit attributes"
+msgstr "Sair da edição de atributos"
+
+#: en_US/emacs.xml:550(title)
+#: en_US/emacs-nxml.xml:77(title)
+msgid "Examples"
+msgstr "Exemplos"
+
+#: en_US/emacs.xml:552(para)
+msgid "The table or reference card of Emacs and PSGML commands can be confusing for beginners. This section provides some examples of how to use them."
+msgstr "A tabela ou cartão de referência dos comandos do Emacs e do PSGML poderão ser confusos para os principiantes. Esta secção oferece alguns exemplos de utilização dos mesmos."
+
+#: en_US/emacs.xml:559(title)
+msgid "Tag Completion"
+msgstr "Completação de Marcas"
+
+#: en_US/emacs.xml:563(para)
+msgid "This section assumes that you have already parsed the DTD file."
+msgstr "Esta secção assume que você já carregou o ficheiro da DTD."
+
+#: en_US/emacs.xml:567(para)
+msgid "To avoid having to type a tag repeatedly, use the key combination <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. At the bottom of the <application>Emacs</application> window, the following prompt appears:"
+msgstr "Em vez de escrever uma marca sempre que necessitar de a usar, use a combinação de teclas <keycap>Ctrl</keycap>-<keycap>C</keycap>, seguida do <keycap><</keycap>. No fundo da janela do <application>Emacs</application>, irá ver:"
+
+#: en_US/emacs.xml:574(prompt)
+msgid "Tag: <"
+msgstr "Marca: <"
+
+#: en_US/emacs.xml:576(para)
+msgid "To view a list of available tags, use either the <keycap>Tab</keycap> or <keycap>?</keycap>. If you know the first few letters of a tag, enter them, followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, that tag appears. If more than one completion exists, a complete list of possible tags appears."
+msgstr "Para ver uma lista com as marcas disponíveis, use as teclas <keycap>Tab</keycap> ou <keycap>?</keycap>. Por outro lado, se souber as primeiras letras de uma marca, podê-las-á introduzir e carregar de seguida em <keycap>Tab</keycap> para obter uma lista completa das marcas disponíveis que começam por essas letras ou para completar a marca."
+
+#: en_US/emacs.xml:585(para)
+msgid "If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, <keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the example below:"
+msgstr "Se carregar em <keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo>, <keycap><</keycap>, <keycap>K</keycap>, irá aparecer uma linha de comandos semelhante ao exemplo abaixo:"
+
+#: en_US/emacs.xml:602(title)
+msgid "Tag Closure"
+msgstr "Fecho de Marcas"
+
+#: en_US/emacs.xml:604(para)
+msgid "After you open a tag, you must close it. The easiest way to close an open tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most recently opened tag."
+msgstr "Logo que tenha iniciado a marca que escolheu, terá de a fechar. A forma mais simples de fechar uma marca é usar a combinação de teclas <keycap>Ctrl</keycap>-<keycap>C</keycap>, seguida de <keycap>/</keycap>. Esta irá fechar a marca aberta mais próxima que tiver."
+
+#: en_US/emacs.xml:616(title)
+msgid "Other Emacs Tasks"
+msgstr "Outras Tarefas do Emacs"
+
+#: en_US/emacs.xml:619(title)
+msgid "Working with One Window"
+msgstr "Lidar com uma Janela"
+
+#: en_US/emacs.xml:620(para)
+msgid "Sometimes in <application>Emacs</application>, the window becomes split, with tags completions or other text in an alternate window. To return to a single window, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+msgstr "Algumas vezes no <application>Emacs</application>, a janela vai ficando dividida (com as completações de marcas ou outro texto na janela inferior). A forma mais simples de voltar atrás, para que apenas o seu XML e o texto apareçam num ecrã, é usar a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>1</keycap>."
+
+#: en_US/emacs.xml:630(title)
+msgid "Saving Work"
+msgstr "Gravar o Trabalho"
+
+#: en_US/emacs.xml:631(para)
+msgid "To save your work, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>."
+msgstr "Para gravar o seu trabalho, use a seguinte combinação de teclas, <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>Ctrl</keycap>-<keycap>S</keycap>."
+
+#: en_US/emacs.xml:642(title)
+msgid "The \"Clear/Quit\" Command"
+msgstr "O Comando \"Limpar/Sair\""
+
+#: en_US/emacs.xml:643(para)
+msgid "If the tag completion process becomes unwieldy or confusing, use the keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to exit back to the text. <application>Emacs</application> clears any prompts and returns to the buffer text."
+msgstr "Se o processo de completação de marcas se tornar incomportável ou confuso, use a sequência de teclas <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> para voltar para o texto. O <application>Emacs</application> limpa todas as linhas de comando e volta para o texto."
+
+#: en_US/emacs.xml:653(title)
+msgid "Opening a new file"
+msgstr "Abrir um ficheiro novo"
+
+#: en_US/emacs.xml:654(para)
+msgid "To open a new file, use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the <application>Emacs</application> window. Enter the file name, using <keycap>Tab</keycap> completion if desired, of the file you wish to open."
+msgstr "Para abrir um novo ficheiro, use a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>Ctrl</keycap>-<keycap>F</keycap>. No fundo da janela do Emacs, será capaz de indicar o nome do ficheiro (usando a completação do <keycap>Tab</keycap> se necessário) do ficheiro que deseja abrir."
+
+#: en_US/emacs.xml:668(title)
+msgid "Closing <application>Emacs</application>"
+msgstr "Fechar o <application>Emacs</application>"
+
+#: en_US/emacs.xml:669(para)
+msgid "To close <application>Emacs</application> use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have not saved your work, <application>Emacs</application> prompts you to save any changed files."
+msgstr "Para fechar o <application>emacs</application>, use a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap> seguida de <keycap>Ctrl</keycap>-<keycap>C</keycap>. Se não tiver gravado o seu trabalho, será questionado pelo <application>Emacs</application> para gravar os ficheiros alterados."
+
+#: en_US/emacs.xml:687(title)
+#: en_US/emacs-nxml.xml:127(title)
+msgid "Additional Resources"
+msgstr "Recursos Adicionais"
+
+#: en_US/emacs.xml:689(para)
+msgid "Additional Emacs and PSGML references are available at the following locations:"
+msgstr "As referências adicionais ao Emacs e ao PSGML estão disponíveis nas seguintes localizações:"
+
+#: en_US/emacs.xml:697(citetitle)
+#: en_US/emacs-nxml.xml:143(citetitle)
+msgid "Emacs Quick Reference Guide"
+msgstr "Guia de Referência Rápido do Emacs"
+
+#: en_US/emacs.xml:701(para)
+msgid "Emacs reference card that comes with the <filename>emacs</filename> package. You can print it out as a reference. —<filename>/usr/share/emacs/<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+msgstr "Um cartão de referência do Emacs que vem com o pacote <filename>emacs</filename>. Poderá imprimi-lo como referência. —<filename>/usr/share/emacs/<replaceable>versão</replaceable>/etc/refcard.ps</filename>"
+
+#: en_US/emacs.xml:708(para)
+msgid "Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+msgstr "Leia o <citetitle>Editing XML with Emacs and PSGML</citetitle> no ficheiro <filename>/usr/share/doc/psgml-<replaceable>versão</replaceable>/psgml.ps</filename>."
+
+#: en_US/emacs.xml:714(para)
+msgid "<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of Emacs commands for PSGML mode."
+msgstr "O <ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—<citetitle>Emacs/PSGML Quick Reference</citetitle> é uma tabela de referência dos comandos do Emacs para o modo do PSGML."
+
+#: en_US/emacs.xml:723(citetitle)
+msgid "PSGML Tricks"
+msgstr "Truques do PSGML"
+
+#: en_US/emacs-nxml.xml:11(title)
+msgid "Emacs and nXML Mode"
+msgstr "O Emacs e o Modo nXML"
+
+#: en_US/emacs-nxml.xml:14(primary)
+#: en_US/emacs-nxml.xml:51(primary)
+msgid "nXML"
+msgstr "nXML"
+
+#: en_US/emacs-nxml.xml:23(secondary)
+msgid "nXML mode"
+msgstr "modo nXML"
+
+#: en_US/emacs-nxml.xml:26(para)
+msgid "You can also use the nXML mode available for <application>Emacs</application> to make it even easier to write in DocBook XML format. nXML mode provides context-sensitive editing using completion, real time validity error checking, syntax highlighting and indentation. All you need to do is install an RPM!!"
+msgstr "Também poderá usar o modo nXML que está disponível para o <application>Emacs</application>, de modo a ser ainda mais simples escrever no formato DocBook em XML. O modo nXML oferece uma edição sensível ao contexto com a completação, validação dos erros em tempo-real, realce de sintaxe e indentação. Tudo o que necessita é instalar um RPM!!"
+
+#: en_US/emacs-nxml.xml:35(title)
+msgid "Early stages"
+msgstr "Etapas iniciais"
+
+#: en_US/emacs-nxml.xml:36(para)
+msgid "Please be aware the nxml-mode for <application>Emacs</application> is quite new, so there are a few things that the advanced user might notice when using it with other documents types. If you keep an eye on the mailing-list, you can keep up to date with these, as well as ask questions. For more details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr "Tenha em atenção que o 'nxml-mode' do <application>Emacs</application> é relativamente novo, pelo que existem algumas coisas que o utilizador mais avançado poderá notar ao usá-lo com outros tipos de documentos. Se mantiver uma vista de olhos na lista de correio, poder-se-á manter actualizado com as mesmas, assim como poderá fazer perguntas. Para mais detalhes, veja a secção <xref linkend=\"sn-emacs-nxml-readme\"/>."
+
+#: en_US/emacs-nxml.xml:48(title)
+msgid "Getting the nXML RPM"
+msgstr "Obter o RPM do nXML"
+
+#: en_US/emacs-nxml.xml:52(secondary)
+msgid "RPM"
+msgstr "RPM"
+
+#: en_US/emacs-nxml.xml:56(primary)
+msgid "nXML RPM"
+msgstr "RPM do nXML"
+
+#: en_US/emacs-nxml.xml:59(para)
+msgid "To use nXML mode with emacs, you will need to install the nXML RPM available from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www.thaiopensource.com/download/\">http://www.thaiopensource.com/download/</ulink>. The source requires a lot more work to setup, therefore we will only be concentrating on the RPM version."
+msgstr "Para usar o modo nXML com o emacs, terá de instalar o pacote RPM nXML na <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/\">página do Tim Waugh</ulink> ou o código-fonte de <ulink url=\"http://www.thaiopensource.com/download/\">http://www.thaiopensource.com/download/</ulink>. O código necessita de bastante mais trabalho de configuração; como tal, concentrar-nos-emos na versão em RPM."
+
+#: en_US/emacs-nxml.xml:69(para)
+msgid "Information on where to get the source is available in <xref linkend=\"sn-emacs-additional-resources\"/>."
+msgstr "As informações de disponibilização do código estão disponíveis em <xref linkend=\"sn-emacs-additional-resources\"/>."
+
+#: en_US/emacs-nxml.xml:79(para)
+msgid "Compared to PSGML mode there are only couple of commands that you need. This speeds up writing with <application>Emacs</application> considerably, which means you can concentrate more on the content of your article."
+msgstr "Em comparação com o modo PSGML, só existem alguns comandos que você necessita. Isto acelera a escrita no <application>Emacs</application> consideravelmente, o que significa que se poderá concentrar mais no conteúdo do seu artigo."
+
+#: en_US/emacs-nxml.xml:88(para)
+msgid "To create a tag, type <userinput><</userinput> and then type the keyword. To complete the keyword, press <command>Ctrl-Ret</command>, then add the last <userinput>></userinput>. To close a tag, type <userinput></</userinput>."
+msgstr "Para criar uma marca, escreva <userinput><</userinput> e escreva depois a palavra-chave. Para completar a mesma, carregue em <command>Ctrl-Ret</command>, adicionando depois a última <userinput>></userinput>. Para fechar uma marca, escreva <userinput></</userinput>."
+
+#: en_US/emacs-nxml.xml:97(para)
+msgid "When you open a document that doesn't have a DOCTYPE declaration at the top of the file, you will get this message and tag completion won't work because nXML will not know what format you are writing."
+msgstr "Quando abrir um documento que não tenha uma declaração DOCTYPE no topo do ficheiro, irá obter esta mensagem e a completação de marcas não irá funcionar, porque o nXML não irá saber em que formato está a escrever."
+
+#: en_US/emacs-nxml.xml:104(para)
+msgid "To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> and load <filename>docbook.rnc</filename>. <application>Emacs</application> will then prompt you to save it in the current working directory."
+msgstr "Para carregar o esquema, escreva <command>Ctrl-C</command> e <command>Ctrl-S</command>, indo depois à pasta <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> e carregando o <filename>docbook.rnc</filename>. O <application>Emacs</application> perguntar-lhe-á então para gravar a pasta de trabalho actual."
+
+#: en_US/emacs-nxml.xml:115(para)
+msgid "The commands already discussed are the only differences between using <application>Emacs</application> with PSGML mode and <application>Emacs</application> with nXML mode. You will still need to use all the same commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr "Os comandos já discutidos são as únicas diferenças entre a utilização do <application>Emacs</application> com o modo PSGML e o <application>Emacs</application> com o modo nXML. Terá à mesma de usar todos os mesmos comandos que foram discutidos em <xref linkend=\"sn-emacs-basic-commands\"/>."
+
+#: en_US/emacs-nxml.xml:129(para)
+msgid "Additional Emacs and nXML references are available at the following locations:"
+msgstr "As referências adicionais do Emacs e do nXML estão disponíveis nos seguintes locais:"
+
+#: en_US/emacs-nxml.xml:136(ulink)
+msgid "http://www.thaiopensource.com/download/"
+msgstr "http://www.thaiopensource.com/download/"
+
+#: en_US/emacs-nxml.xml:137(citetitle)
+msgid "Author's download area"
+msgstr "Área de transferências do autor"
+
+#: en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+
+#: en_US/emacs-nxml.xml:147(para)
+msgid "Emacs reference card that comes with the <filename>emacs</filename> package. You can print it out as a reference. —<filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr "Um cartão de referência do Emacs que vem com o pacote <filename>emacs</filename>. Poderá imprimi-lo como referência. —<filename>/usr/share/emacs/<replaceable><versão></replaceable>/etc/refcard.ps</filename>"
+
+#: en_US/emacs-nxml.xml:157(title)
+msgid "nXML README File"
+msgstr "Ficheiro README do nXML"
+
+#: en_US/emacs-nxml.xml:161(para)
+msgid "This file can be found in the directory you extracted the source into, or in <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename> if you installed the RPM."
+msgstr "Este ficheiro poderá ser encontrado na pasta para onde extraiu o código ou em <filename>/usr/share/doc/nxml-mode-<replaceable><versão></replaceable>/</filename>, se instalou o RPM."
+
+#: en_US/emacs-nxml.xml:169(para)
+msgid "README file:"
+msgstr "Ficheiro README:"
+
+#: en_US/emacs-nxml.xml:171(para)
+msgid "This is a new major mode for GNU Emacs for editing XML documents. It supports editing well-formed XML documents and also provides schema-sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr "Este é um novo modo principal para o GNU Emacs editar documentos em XML. Este suporta a edição de documentos válidos em XML, oferecendo também a edição sensível ao esquema dos documentos em XML, usando a Sintaxe Compacta do RELAX NG."
+
+#: en_US/emacs-nxml.xml:177(para)
+msgid "To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs version 20 will not work properly, nor will XEmacs. To get started, do the following:"
+msgstr "Para usar isto, terá de ter o GNU Emacs versão 21.x, de preferência a 21.3. O GNU Emacs versão 20 não irá funcionar correctamente, assim como o XEmacs. Para começar, faça o seguinte:"
+
+#: en_US/emacs-nxml.xml:184(command)
+msgid "M-x load-file RET rng-auto.el RET"
+msgstr "M-x load-file RET rng-auto.el RET"
+
+#: en_US/emacs-nxml.xml:187(para)
+msgid "This defines the necessary autoloads. Now, visit a file containing an XML document, and do the following:"
+msgstr "Isto define todos os carregamentos automáticos necessários. Depois, vá a um ficheiro que contenha um documento em XML, fazendo o seguinte:"
+
+#: en_US/emacs-nxml.xml:192(command)
+msgid "M-x nxml-mode"
+msgstr "M-x nxml-mode"
+
+#: en_US/emacs-nxml.xml:195(para)
+msgid "Now do"
+msgstr "Agora faça"
+
+#: en_US/emacs-nxml.xml:200(command)
+msgid "C-h m"
+msgstr "C-H m"
+
+#: en_US/emacs-nxml.xml:203(para)
+msgid "For information on how to use nxml-mode. The beginnings of a manual are in nxml-mode.info. You can read this using:"
+msgstr "Para mais informações sobre a utilização do nxml-mode. As introduções do manual estão no ficheiro 'nxml-mode.info'. Podê-lo-á ler com:"
+
+#: en_US/emacs-nxml.xml:209(command)
+msgid "C-u M-x info RET nxml-mode.info RET"
+msgstr "C-u M-x info RET nxml-mode.info RET"
+
+#: en_US/emacs-nxml.xml:212(para)
+msgid "It's also installed as an entry at the end of the top-level info directory. So you can read it with <command>C-h i</command> as usual."
+msgstr "Também está instalado como um elemento no fim da pasta de topo do 'info'. Como tal, poderá lê-la com o <command>C-H I</command>, como de costume."
+
+#: en_US/emacs-nxml.xml:217(para)
+msgid "You can use <filename>test.valid.xml</filename> and <filename>test.invalid.xml</filename> as examples of valid and invalid XML documents."
+msgstr "Poderá usar os ficheiros <filename>test.valid.xml</filename> e <filename>test.invalid.xml</filename> como exemplos de documentos em XML válidos e inválidos."
+
+#: en_US/emacs-nxml.xml:223(para)
+msgid "To get things automatically loaded each time you start Emacs, add:"
+msgstr "Para que as coisas sejam carregadas automaticamente de cada vez que iniciar o Emacs, adicione:"
+
+#: en_US/emacs-nxml.xml:228(computeroutput)
+#, no-wrap
+msgid ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+msgstr ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+
+#: en_US/emacs-nxml.xml:232(para)
+msgid "to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-200YMMDD</computeroutput> is the directory containing the <filename>.elc</filename> files. Note that <filename>rng-auto.el</filename> does not load all of the nxml-mode code; it merely sets things up so that all the features of nxml-mode will be autoloaded properly. You should not try to autoload <filename>rng-auto.el</filename> itself."
+msgstr "ao seu ficheiro <filename>.emacs</filename>, onde o <computeroutput>~/nxml-mode-200AMMDD</computeroutput> é a pasta que contém os ficheiros <filename>.elc</filename>. Lembre-se que o <filename>rng-auto.el</filename> não carrega tudo do modo 'nxml-mode'; simplesmente configura as coisas, para que as funcionalidades do 'nxml-mode' sejam carregadas automaticamente. Não deverá tentar carregar automaticamente o <filename>rng-auto.el</filename> propriamente dito."
+
+#: en_US/emacs-nxml.xml:242(para)
+msgid "To use nxml-mode automatically for files with an extension of <filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> or <filename>xhtml</filename>, add the following to your <filename>.emacs</filename> file:"
+msgstr "Para usar o 'nxml-mode' automaticamente para os ficheiros com as extensões <filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> ou <filename>xhtml</filename>, adicione o seguinte ao seu ficheiro <filename>.emacs</filename>:"
+
+#: en_US/emacs-nxml.xml:250(computeroutput)
+#, no-wrap
+msgid ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+msgstr ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+
+#: en_US/emacs-nxml.xml:255(para)
+msgid "If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are running Emacs 21.3 or later, then I recommend enabling unify-8859-on-decoding-mode, by adding the following to your <filename>.emacs</filename> file:"
+msgstr "Se editar o XML com as codificações iso-8859-N em vez da iso-8859-1 e estiver a usar o Emacs 21.3 ou posterior, recomenda-se que active o 'unify-8859-on-decoding-mode', adicionando a seguinte sequência ao seu ficheiro <filename>.emacs</filename>:"
+
+#: en_US/emacs-nxml.xml:263(computeroutput)
+#, no-wrap
+msgid "(unify-8859-on-decoding-mode)"
+msgstr "(unify-8859-on-decoding-mode)"
+
+#: en_US/emacs-nxml.xml:266(para)
+msgid "To get validation and schema-sensitive editing, you need a RELAX NG Compact Syntax (RNC) schema for you document. The schema directory includes some schemas for popular document types."
+msgstr "Para ter uma validação e edição sensível ao esquema, precisa de um esquema de Sintaxe Compacta do Relax NG (RNC) do seu documento. A pasta do esquema inclui alguns esquemas para os tipos de documentos mais conhecidos."
+
+#: en_US/emacs-nxml.xml:272(para)
+msgid "For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://relaxng.org/</ulink>."
+msgstr "Para mais informações sobre o RELAX NG, consulte a página <ulink url=\"http://relaxng.org/\">http://relaxng.org/</ulink>."
+
+#: en_US/emacs-nxml.xml:277(para)
+msgid "For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial.html</ulink>"
+msgstr "Para um tutorial sobre a Sintaxe Compacta do RELAX NG, veja a página <ulink url=\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial.html</ulink>"
+
+#: en_US/emacs-nxml.xml:282(para)
+msgid "For automatically creating RNC schemas, I recommend my Trang program: <ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee.thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr "Para criar automaticamente os esquemas RNG, recomenda-se o programa Trang: <ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee.thaiopensource.com/relaxng/trang.html\"</ulink>"
+
+#: en_US/emacs-nxml.xml:293(para)
+msgid "Infer an RNC schema from an instance document"
+msgstr "Inferir um esquema de RNC a partir do documento de uma instância"
+
+#: en_US/emacs-nxml.xml:298(para)
+msgid "Convert a DTD to an RNC schema"
+msgstr "Converter uma DTD para um esquema RNC"
+
+#: en_US/emacs-nxml.xml:303(para)
+msgid "Convert a RELAX NG XML syntax schema to an RNC schema"
+msgstr "Converter um esquema de sintaxe do XML em Relax NG para um esquema RNC"
+
+#: en_US/emacs-nxml.xml:288(para)
+msgid "You can use this to <placeholder-1/>"
+msgstr "Poderá usar isto para <placeholder-1/>"
+
+#: en_US/emacs-nxml.xml:310(para)
+msgid "To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html\">http://www.pantor.com/download.html\"</ulink>."
+msgstr "Para converter um esquema de sintaxe em XML do RELAX NG (.rng) para um esquema RNC, poderá também usar a folha de estilo XSLT em <ulink url=\"http://www.pantor.com/download.html\">http://www.pantor.com/download.html\"</ulink>."
+
+#: en_US/emacs-nxml.xml:316(para)
+msgid "To convert a W3C XML Schema to an RNC schema, you need first to convert it to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+msgstr "Para converter um Esquema de XML da W3C num esquema RNC, terá primeiro de o converter para a sintaxe XML do RELAX NG, usando a ferramenta de conversão para RELAX NG da Sun, a 'rngconv' (assente sobre o MSV). Veja em <ulink url=\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+
+#: en_US/emacs-nxml.xml:323(para)
+msgid "The file <filename>NEWS</filename> describes recent changes."
+msgstr "O ficheiro <filename>NEWS</filename> descreve as alterações recentes."
+
+#: en_US/emacs-nxml.xml:327(para)
+msgid "Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug reports, discussion. I will announce all new versions there."
+msgstr "Use por favor a lista <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> para os relatórios de erros, discussão, etc. Serão aí anunciadas todas as versões novas."
+
+#: en_US/emacs-nxml.xml:333(para)
+msgid "James Clark"
+msgstr "James Clark"
+
+#: en_US/emacs-nxml.xml:336(para)
+msgid "jjc@@thaiopensource.com"
+msgstr "jjc@@thaiopensource.com"
+
+#: en_US/acknowledgments.xml:11(title)
+msgid "Acknowledgments"
+msgstr "Agradecimentos"
+
+#: en_US/acknowledgments.xml:13(para)
+msgid "This document is based on a document started by Tammy Fox (tfox at redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray Fuller (jrfuller at redhat.com)."
+msgstr "Este documento baseia-se num documento iniciado por Tammy Fox (tfox at redhat.com) e com contribuições de Sandra Moore (smoore at redhat.com) e Johnray Fuller (jrfuller at redhat.com)."
+
+#: en_US/acknowledgments.xml:19(para)
+msgid "A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr "Uma correcção do Roozbeh Pournader (roozbeh at sharif.edu) foi aplicada para corrigir alguns erros ortográficos e explicar que o CVS anónimo não permite o envio de novas versões."
+
+#: en_US/acknowledgments.xml:25(para)
+msgid "Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to add the trailing slashes to the <command>figure</command> tag example in <filename>docs-xml-tags.xml</filename>."
+msgstr "Foram aplicadas correcções de Gavin Henry (ghenry at suretecsystems.com) par adicionar as barras finais ao exemplo da marca <command>figure</command>, como aparece em <filename>docs-xml-tags.xml</filename>."
+
+#: en_US/acknowledgments.xml:32(para)
+msgid "A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been applied to add <xref linkend=\"ch-vim\"/>."
+msgstr "Uma actualização do Joshua Daniel Franklin (joshuadfranklin at yahoo.com) para adicionar o <xref linkend=\"ch-vim\"/>."
+
+#: en_US/acknowledgments.xml:37(para)
+msgid "A patch from Karsten Wade (kwade at redhat.com) has been applied to add <xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields (stickster at gmail.com)."
+msgstr "Uma correcção de Karsten Wade (kwade at redhat.com) foi aplicada para adicionar o <xref linkend=\"sn-screenshots\"/>. Foi editada por Paul W. Frields (stickster at gmail.com)."
+
+#. This section has been removed.
+#. <para>
+#. A patch from Paul W. Frields (stickster at gmail.com) has been applied
+#. to add more explanation of the <command>screen</command> tag set to <xref
+#. linkend="sn-xml-tags-screen"></xref>.
+#. </para>
+#: en_US/acknowledgments.xml:50(para)
+msgid "A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been applied to more fully explaing the document building system."
+msgstr "Uma correcção de Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) foi aplicada para descrever com maior pormenor o sistema de compilação de documentos."
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: en_US/acknowledgments.xml:0(None)
+msgid "translator-credits"
+msgstr "José Nuno Pires <jncp@@netcabo.pt>, 2006."
+
+#~ msgid "OTHERS"
+#~ msgstr "OTHERS"
+#~ msgid ""
+#~ "This variable contains a listing of ISO codes for any other versions into "
+#~ "which the document has been translated. The module must contain a "
+#~ "<placeholder-1/> directory and a PO file for any indicated additional "
+#~ "languages."
+#~ msgstr ""
+#~ "Esta variável contém uma lista dos códigos ISO das outras versões "
+#~ "traduzidas do documento. O módulo deverá conter uma pasta <placeholder-1/"
+#~ "> e um ficheiro PO para cada língua adicional indicada."
+#~ msgid ""
+#~ "<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, "
+#~ "<placeholder-3/>"
+#~ msgstr ""
+#~ "<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, "
+#~ "<placeholder-3/>"
+#~ msgid ""
+#~ "A patch from Paul W. Frields (stickster at gmail.com) has been applied to "
+#~ "add more explanation of the <command>screen</command> tag set to <xref "
+#~ "linkend=\"sn-xml-tags-screen\"/>."
+#~ msgstr ""
+#~ "Uma correcção de Paul W. Frields (stickster at hotmail.com) foi aplicada "
+#~ "para adicionar mais explicações sobre o conjunto de marcas "
+#~ "<command>screen</command> em <xref linkend=\"sn-xml-tags-screen\"/>."
+#~ msgid "DocBook XML Tags"
+#~ msgstr "Marcas XML do DocBook"
+#~ msgid "XML"
+#~ msgstr "XML"
+#~ msgid "tags"
+#~ msgstr "marcas"
+#~ msgid ""
+#~ "Please read this chapter carefully. This chapter describes the tags used "
+#~ "by the Docs Project. Some of the rules described are specific to the "
+#~ "project."
+#~ msgstr ""
+#~ "Leia por favor este capítulo com cuidado. O mesmo descreve as marcas "
+#~ "usadas pelo Projecto de Documentação. Algumas das regras aqui descritas "
+#~ "são específicas do projecto."
+#~ msgid ""
+#~ "If these tags are used appropriately, document searches will provide "
+#~ "meaningful results. These tags help search engines identify the "
+#~ "information relevant to the search request. Another benefit is that all "
+#~ "Fedora Project documents will have a similar look and feel (however, they "
+#~ "will have some differences depending upon the output format)."
+#~ msgstr ""
+#~ "Se estas marcas forem usadas de forma apropriada, as pesquisas no "
+#~ "documento irão oferecer resultados significativos. Estas marcas ajudam os "
+#~ "motores de busca a identificar a informação relevante para o pedido de "
+#~ "pesquisa. Outro benefício é o facto de todos os documentos do Projecto "
+#~ "Fedora terão uma aparência e comportamento semelhante (contudo, terão "
+#~ "algumas diferenças que dependem do formato de saída)."
+#~ msgid "general tag information"
+#~ msgstr "informação geral de marcas"
+#~ msgid ""
+#~ "Most tags in XML must have an opening and closing tag. A few tags, such "
+#~ "as <sgmltag class=\"emptytag\">xref</sgmltag>, have no content and close "
+#~ "themselves. Additionally, proper XML conventions say that there must be a "
+#~ "unique identifier for sections, chapters, figures, tables, and so on, so "
+#~ "that they may be correctly identified, and cross referenced if needed."
+#~ msgstr ""
+#~ "A maior parte das marcas em XML deverão ter uma marca de abertura e de "
+#~ "fecho. Algumas marcas, como a <sgmltag class=\"emptytag\">xref</sgmltag>, "
+#~ "não têm conteúdo, pelo que se fecham a si próprias. Adicionalmente, as "
+#~ "convenções adequadas em XML dizem que deverá existir um identificador "
+#~ "único para as secções, capítulos, figuras, tabelas, entre outros, para "
+#~ "que possam ser identificadas e refenciadas correctamente se necessário."
+#~ msgid ""
+#~ "Although XML is capable of handling many document types, the format "
+#~ "discussed here is the article format."
+#~ msgstr ""
+#~ "Ainda que o XML seja capaz de lidar com muitos tipos de documentos, o "
+#~ "formato aqui discutido é o formato dos artigos."
+#~ msgid "Tags and Entities Caveats"
+#~ msgstr "Contrapartidas das Marcas e Entidades"
+#~ msgid ""
+#~ "It is very important that you remember the caveats in this section. Even "
+#~ "though they are more strict than valid DocBook XML, these rules exist so "
+#~ "that both the HTML and PDF outputs look proper."
+#~ msgstr ""
+#~ "É bastante importante que recorde as contrapartidas desta secção. Ainda "
+#~ "que sejam mais restritas que o DocBook em XML válido, estas regras "
+#~ "existem para que os resultados em HTML e PDF apareçam válidos."
+#~ msgid ""
+#~ "Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+#~ "sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+#~ "\"genentity\">reg</sgmltag> because they do not produce HTML output that "
+#~ "works for all charsets. The HTML output produces by these entities are "
+#~ "declared in the DTD and cannot be changed via the stylesheet."
+#~ msgstr ""
+#~ "Não use as entidades de marcas registadas <sgmltag class=\"genentity"
+#~ "\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag> ou "
+#~ "<sgmltag class=\"genentity\">reg</sgmltag>, porque não produzem HTML "
+#~ "válido que funcione em todas as codificações de caracteres. O resultado "
+#~ "em HTML produzido por estas entidades está descrito na DTD e não pode ser "
+#~ "alterado com a folha de estilo."
+#~ msgid ""
+#~ "Instead, use the <sgmltag class=\"element\">trademark</sgmltag> tag and "
+#~ "its associates classes as follows:"
+#~ msgstr ""
+#~ "Em vez disso, use a marca <sgmltag class=\"element\">trademark</sgmltag> "
+#~ "e as suas classes associadas, como se segue:"
+#~ msgid ""
+#~ "<sgmltag class=\"starttag\">trademark</sgmltag>trademark symbol after "
+#~ "me<sgmltag class=\"endtag\">trademark</sgmltag>"
+#~ msgstr ""
+#~ "<sgmltag class=\"starttag\">trademark</sgmltag>símbolo de marca a seguir "
+#~ "a mim<sgmltag class=\"endtag\">trademark</sgmltag>"
+#~ msgid ""
+#~ "<sgmltag class=\"starttag\">trademark class=\"registered\"</"
+#~ "sgmltag>registered trademark symbol after me<sgmltag class=\"endtag"
+#~ "\">trademark</sgmltag>"
+#~ msgstr ""
+#~ "<sgmltag class=\"starttag\">trademark class=\"registered\"</"
+#~ "sgmltag>símbolo de marca registada a seguir a mim<sgmltag class=\"endtag"
+#~ "\">trademark</sgmltag>"
+#~ msgid ""
+#~ "<sgmltag class=\"starttag\">trademark class=\"copyright\"</"
+#~ "sgmltag>copyright symbol after me<sgmltag class=\"endtag\">trademark</"
+#~ "sgmltag>"
+#~ msgstr ""
+#~ "<sgmltag class=\"starttag\">trademark class=\"copyright\"</"
+#~ "sgmltag>símbolo de direitos de cópia a seguir a mim<sgmltag class=\"endtag"
+#~ "\">trademark</sgmltag>"
+#~ msgid ""
+#~ "Do not use <sgmltag>para</sgmltag> tags around anything other than a "
+#~ "simple paragraph. Doing so will create additional white space within the "
+#~ "text itself in the PDF version."
+#~ msgstr ""
+#~ "Não use as marcas <sgmltag>para</sgmltag> em torno de tudo o que não seja "
+#~ "um parágrafo simples. Ao fazê-lo, irá criar espaços em branco adicionais "
+#~ "dentro do próprio texto, na versão em PDF."
+#~ msgid ""
+#~ "Specifically, do not use <sgmltag>para</sgmltag> tags around the "
+#~ "following (or, to put this another way, do not embed the following within "
+#~ "<sgmltag>para</sgmltag> tags):"
+#~ msgstr ""
+#~ "Especificamente, não use as marcas <sgmltag>para</sgmltag> em torno do "
+#~ "seguinte (ou, posto de outra forma, não incorpore o seguinte dentro das "
+#~ "marcas <sgmltag>para</sgmltag>):"
+#~ msgid ""
+#~ "Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+#~ "sgmltag> tags"
+#~ msgstr ""
+#~ "Conteúdo dentro das marcas <sgmltag>para</sgmltag> dentro de marcas "
+#~ "<sgmltag>listitem</sgmltag>"
+#~ msgid ""
+#~ "Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+#~ "sgmltag> tags <emphasis>must</emphasis> start immediately after the "
+#~ "beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra "
+#~ "white space in the PDF version."
+#~ msgstr ""
+#~ "O conteúdo dentro das marcas <sgmltag>para</sgmltag> inseridas em marcas "
+#~ "<sgmltag>listitem</sgmltag> <emphasis>deverá</emphasis> começar logo a "
+#~ "seguir à marca inicial <sgmltag class=\"starttag\">para</sgmltag>, para "
+#~ "evitar espaços em branco extra na versão em PDF."
+#~ msgid "application"
+#~ msgstr "application"
+#~ msgid ""
+#~ "An application is the name of a GUI software program. A command is the "
+#~ "name of an executable (text) program or a software command."
+#~ msgstr ""
+#~ "Uma aplicação é o nome de um programa de 'software' gráfico. Um comando é "
+#~ "o nome de um programa executável (em texto) ou um comando do sistema."
+#~ msgid ""
+#~ "The <sgmltag class=\"starttag\">application</sgmltag> and <sgmltag class="
+#~ "\"endtag\">application</sgmltag> tags allow you to refer to an "
+#~ "application or program. For example, the following XML:"
+#~ msgstr ""
+#~ "As marcas <sgmltag class=\"starttag\">application</sgmltag> e <sgmltag "
+#~ "class=\"endtag\">application</sgmltag> permitem-lhe referenciar uma "
+#~ "aplicação ou um programa. Por exemplo, o seguinte XML:"
+#~ msgid ""
+#~ "\n"
+#~ "To view the Web in Linux, you can use\n"
+#~ "<placeholder-1/>Mozilla<placeholder-2/> \n"
+#~ "or <placeholder-3/>lynx<placeholder-4/> if\n"
+#~ "you only want a text-based browser.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Para ver a Web no Linux, pode usar o\n"
+#~ "<placeholder-1/>Mozilla<placeholder-2/> \n"
+#~ "ou o <placeholder-3/>lynx<placeholder-4/>,\n"
+#~ "se só quiser um navegador em modo texto.\n"
+#~ msgid "produces the following output:"
+#~ msgstr "produz o seguinte resultado:"
+#~ msgid ""
+#~ "To view the Web in Linux, you can use <application>Mozilla</application> "
+#~ "or <application>lynx</application> if you only want a text-based browser."
+#~ msgstr ""
+#~ "Para ver a Web no Linux, poderá usar o <application>Mozilla</application> "
+#~ "ou o <application>lynx</application> se só quiser um navegador em modo "
+#~ "texto."
+#~ msgid "A DocBook book can be divided into chapters such as:"
+#~ msgstr ""
+#~ "Um livro em DocBook poderá ser dividido em capítulos como os seguintes:"
+
+#, fuzzy
+#~ msgid ""
+#~ "\n"
+#~ "<!--$Id: pt.po,v 1.24 2008/05/12 06:13:11 mdious Exp $ -->\n"
+#~ "\n"
+#~ " <chapter id=\"ch-sample\">\n"
+#~ " <title>Sample Chapter</title>\n"
+#~ "\n"
+#~ " <para>This is a sample chapter, showing you the XML tags used "
+#~ "to create a\n"
+#~ " chapter, sections, and subsections.</para>\n"
+#~ " \n"
+#~ " </chapter>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<!--$Id: pt.po,v 1.24 2008/05/12 06:13:11 mdious Exp $ -->\n"
+#~ "\n"
+#~ " <chapter id=\"cap-exemplo\">\n"
+#~ " <title>Capítulo de Exemplo</title>\n"
+#~ "\n"
+#~ " <para>Este é um capítulo de exemplo, que lhe mostra as marcas \n"
+#~ " em XML usadas para criar um capítulo, secções e sub-secções.</"
+#~ "para>\n"
+#~ " \n"
+#~ " </chapter>\n"
+#~ msgid ""
+#~ "The chapter can also be further divided into sections (<sgmltag>section</"
+#~ "sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). "
+#~ "Refer to <xref linkend=\"sn-xml-tags-sections\"/> for details."
+#~ msgstr ""
+#~ "O capítulo poderá também ser dividido em secções (<sgmltag>section</"
+#~ "sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). "
+#~ "Veja mais detalhes em <xref linkend=\"sn-xml-tags-sections\"/>."
+#~ msgid "citetitle"
+#~ msgstr "citetitle"
+#~ msgid ""
+#~ "An entity is a short hand way of referring to some predefined content, "
+#~ "such as a title or name. It can be defined within the parent document or "
+#~ "within a set of files that your DTD references for your specific "
+#~ "documentation set."
+#~ msgstr ""
+#~ "Um entidade é uma forma resumida de fazer referẽncia a algum conteúdo "
+#~ "predefinido, como um título ou um nome. Poderá ser definida dentro do "
+#~ "documento-pai ou dentro de um conjunto de ficheiros que a sua DTD faça "
+#~ "referência, para o seu conjunto de documentação específico."
+
+#, fuzzy
+#~ msgid ""
+#~ "The <sgmltag>citetitle</sgmltag> tag provides formatting for a specific "
+#~ "references (title can be manually typed out or if already defined within "
+#~ "your document set, given as an entity<placeholder-1/> )."
+#~ msgstr ""
+#~ "A marca <sgmltag>citetitle</sgmltag> produz a formatação para uma "
+#~ "referência específica (o título poderá ser escrito manualmente ou, se já "
+#~ "estiver definido dentro do seu conjunto de documentos, indicado como uma "
+#~ "entidade<footnote><placeholder-1/></footnote> )."
+#~ msgid "For example:"
+#~ msgstr "Por exemplo:"
+#~ msgid "IG"
+#~ msgstr "IG"
+#~ msgid ""
+#~ "\n"
+#~ "<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+#~ msgid ""
+#~ "The output looks like <citetitle>Installation Guide</citetitle> because "
+#~ "<sgmltag class=\"genentity\">IG</sgmltag> is an entity."
+#~ msgstr ""
+#~ "O resultado fica semelhante a <citetitle>Guia de Instalação</citetitle>, "
+#~ "porque o <sgmltag class=\"genentity\">IG</sgmltag> é uma entidade."
+#~ msgid "command"
+#~ msgstr "command"
+#~ msgid ""
+#~ "An application is the name of a GUI software program. A command is the "
+#~ "name of an executable (text) program or a software command. Any program "
+#~ "that is a command line or text-based only tool is marked with "
+#~ "<sgmltag>command</sgmltag> tags."
+#~ msgstr ""
+#~ "Uma aplicação é o nome de um programa de 'software' gráfico. Um comando é "
+#~ "o nome de um programa executável (em texto) ou um comando do sistema. "
+#~ "Todos os programas que sejam ferramentas da linha de comandos ou apenas "
+#~ "para modo texto são marcados com as marcas <sgmltag>command</sgmltag>."
+#~ msgid ""
+#~ "If you have text that is a command, use the <sgmltag class=\"starttag"
+#~ "\">command</sgmltag> and <sgmltag class=\"endtag\">command</sgmltag> tags "
+#~ "such as:"
+#~ msgstr ""
+#~ "Se tiver texto que seja um comando, use as marcas <sgmltag class="
+#~ "\"starttag\">command</sgmltag> e <sgmltag class=\"endtag\">command</"
+#~ "sgmltag>, como no exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "To change your keyboard after installation, become root \n"
+#~ "and use the <command>redhat-config-keyboard</command> "
+#~ "command, \n"
+#~ "or you can type <command>setup</command> at the root prompt.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Para mudar o seu teclado após a instalação, torne-se 'root'\n"
+#~ "e use o comando <command>redhat-config-keyboard</command>,\n"
+#~ "ou então escreva o comando <command>setup</command> na linha "
+#~ "de comandos do 'root'.\n"
+#~ msgid "The output:"
+#~ msgstr "O resultado:"
+#~ msgid ""
+#~ "To change your keyboard after installation, become root and use the "
+#~ "<command>redhat-config-keyboard</command> command, or you can type "
+#~ "<command>setup</command> at the root prompt."
+#~ msgstr ""
+#~ "Para mudar o seu teclado após a instalação, torne-se 'root' e use o "
+#~ "comando <command>redhat-config-keyboard</command> ou então escreva o "
+#~ "comando <command>setup</command> na linha de comandos do 'root'."
+#~ msgid "Another example would be:"
+#~ msgstr "Outro exemplo seria:"
+#~ msgid ""
+#~ "\n"
+#~ "<command>MAILNOVIOLATIONS</command> — If set\n"
+#~ "to <command>true</command> this option tells Tripwire to\n"
+#~ "email a report at a regular interval regardless of whether or not\n"
+#~ "any violations have occured. The default value is\n"
+#~ "<command>true</command>.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<command>MAILNOVIOLATIONS</command> — Se estiver\n"
+#~ "definido como <command>true</command>, esta opção indica\n"
+#~ "ao Tripwire para enviar por e-mail um relatório com um intervalo "
+#~ "regular,\n"
+#~ "independentemente das violações que tiverem ocorrido. O valor por "
+#~ "omissão\n"
+#~ "é <command>true</command>.\n"
+#~ msgid "with the output:"
+#~ msgstr "com o resultado:"
+#~ msgid ""
+#~ "<command>MAILNOVIOLATIONS</command>— If set to <command>true</"
+#~ "command> this variable tells Tripwire to email a report at a regular "
+#~ "interval regardless of whether or not any violations have occured. The "
+#~ "default value is <command>true</command>."
+#~ msgstr ""
+#~ "<command>MAILNOVIOLATIONS</command> — Se estiver definido como "
+#~ "<command>true</command>, esta opção indica ao Tripwire para enviar por e-"
+#~ "mail um relatório com um intervalo regular, independentemente das "
+#~ "violações que tiverem ocorrido. O valor por omissão é <command>true</"
+#~ "command>."
+#~ msgid ""
+#~ "In this example, the option value (true) is defined with a <"
+#~ "command> tag set. Because a option is a configuration file option "
+#~ "(command line options which would use the <option> tag set), and "
+#~ "because there is no configuration file option tag available to use, we "
+#~ "are extending the <command> tag set to define options in a "
+#~ "configuration file."
+#~ msgstr ""
+#~ "Neste exemplo, o valor de 'option' ('true') está definido com uma marca "
+#~ "<command> atribuída. Dado que uma 'option' é uma opção do ficheiro "
+#~ "de configuração (as opções das linhas de comandos devem usar a marca <"
+#~ "option>), e dado que não existe nenhuma marca de opção de ficheiros de "
+#~ "configuração para usar, será extendida a marca <command> para "
+#~ "definir opções num ficheiro de configuração."
+#~ msgid ""
+#~ "Terms marked with <command>command</command> tags because there aren't "
+#~ "exact tags for them:"
+#~ msgstr ""
+#~ "Os termos marcados como <command>command</command>, porque não existem "
+#~ "marcas exactas para eles:"
+#~ msgid "Options in configuration files such as Apache directives"
+#~ msgstr ""
+#~ "As opções nos ficheiros de configuração, como as directivas do Apache"
+#~ msgid "daemon names"
+#~ msgstr "nomes de servidores"
+#~ msgid "computeroutput"
+#~ msgstr "computeroutput"
+#~ msgid "To show computer output use the following tags:"
+#~ msgstr "Para mostrar o resultado do computador, use as seguintes marcas:"
+#~ msgid ""
+#~ "\n"
+#~ "<computeroutput>Do you want to delete this file? y n</"
+#~ "computeroutput>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<computeroutput>Deseja remover este ficheiro? s n</"
+#~ "computeroutput>\n"
+#~ msgid "Do you really want to delete this file? y n"
+#~ msgstr "Deseja remover este ficheiro? s n"
+#~ msgid "emphasis"
+#~ msgstr "emphasis"
+#~ msgid ""
+#~ "To emphasis content, use the <command><emphasis></command> and "
+#~ "<command></emphasis></command> tags. For example:"
+#~ msgstr ""
+#~ "Para aumentar a ênfase sobre o conteúdo, use as marcas <command><"
+#~ "emphasis></command> e <command></emphasis></command>. Por "
+#~ "exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "This installation <emphasis>will remove all</emphasis> "
+#~ "existing\n"
+#~ "Linux partitions on <emphasis>all</emphasis> hard drives in "
+#~ "your\n"
+#~ "system; non-Linux partitions will not be removed.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Esta instalação <emphasis> irá remover todas as </emphasis> \n"
+#~ "partições de Linux existentes em\n"
+#~ "<emphasis>todos</emphasis> os discos rígidos do seu sistema;\n"
+#~ "as partições não-Linux não serão removidas.\n"
+#~ msgid ""
+#~ "This installation <emphasis>will remove all</emphasis> existing Linux "
+#~ "partitions on <emphasis>all</emphasis> hard drives in your system; non-"
+#~ "Linux partitions will not be removed."
+#~ msgstr ""
+#~ "Esta instalação <emphasis> irá remover todas as </emphasis>partições de "
+#~ "Linux existentes em <emphasis>todos</emphasis> os discos rígidos do seu "
+#~ "sistema; as partições não-Linux não serão removidas."
+#~ msgid ""
+#~ "The <command><example></command> and <command></example></"
+#~ "command> tags are used to format text within a document and is great for "
+#~ "adding emphasis to show examples of code, exercises, and more."
+#~ msgstr ""
+#~ "As marcas <command><example></command> e <command></example></"
+#~ "command> são usadas para formatar o texto dentro de um documento e são "
+#~ "óptimas para adicionar alguma enfâse sobre exemplos de código, "
+#~ "exercícios, entre outros."
+#~ msgid ""
+#~ "The <command><example></command> tag set should be given an ID and "
+#~ "title:"
+#~ msgstr ""
+#~ "A marca <command><example></command> definida deverá ter um ID e um "
+#~ "título:"
+#~ msgid ""
+#~ "\n"
+#~ "\t<example id=\"static-ip\">\n"
+#~ "\t <title>Static IP Address using DHCP</title>\n"
+#~ "\n"
+#~ "<screen width=60>\n"
+#~ "<computeroutput>\n"
+#~ "host apex {\n"
+#~ " option host-name \"apex.example.com\";\n"
+#~ " hardware ethernet 00:A0:78:8E:9E:AA; \n"
+#~ " fixed-address 192.168.1.4;\n"
+#~ "}\n"
+#~ "<computeroutput>\n"
+#~ "</screen>\n"
+#~ "\n"
+#~ "\t</example>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "\t<example id=\"ip-estatico\">\n"
+#~ "\t <title>Endereço IP Estático com o DHCP</title>\n"
+#~ "\n"
+#~ "<screen width=60>\n"
+#~ "<computeroutput>\n"
+#~ "host ze {\n"
+#~ " option host-name \"ze.exemplo.com\";\n"
+#~ " hardware ethernet 00:A0:78:8E:9E:AA; \n"
+#~ " fixed-address 192.168.1.4;\n"
+#~ "}\n"
+#~ "<computeroutput>\n"
+#~ "</screen>\n"
+#~ "\n"
+#~ "\t</example>\n"
+#~ msgid "Static IP Address using DHCP"
+#~ msgstr "Endereço IP Estático com o DHCP"
+#~ msgid ""
+#~ "\n"
+#~ "host apex {\n"
+#~ " option host-name \"apex.example.com\";\n"
+#~ " hardware ethernet 00:A0:78:8E:9E:AA; \n"
+#~ " fixed-address 192.168.1.4;\n"
+#~ "}\n"
+#~ msgstr ""
+#~ "\n"
+#~ "host ze {\n"
+#~ " option host-name \"ze.exemplo.com\";\n"
+#~ " hardware ethernet 00:A0:78:8E:9E:AA; \n"
+#~ " fixed-address 192.168.1.4;\n"
+#~ "}\n"
+#~ msgid "filename"
+#~ msgstr "filename"
+#~ msgid ""
+#~ "The <command><filename></command> and <command></filename></"
+#~ "command> tags define a filename or path to a file. Since directories are "
+#~ "just special files, they are marked with the <command>filename</command> "
+#~ "tags as well. For example:"
+#~ msgstr ""
+#~ "As marcas <command><filename></command> e <command></filename>"
+#~ "</command> definem o nome ou o local de um ficheiro. Dado que as pastas "
+#~ "são ficheiros especiais, são marcadas também com o <command>filename</"
+#~ "command>. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "Edit the <filename>/home/smoore/sam.xml</filename> file to "
+#~ "make\n"
+#~ "changes or add comments.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Edite o ficheiro <filename>/home/ze/nuno.xml</filename> para\n"
+#~ "fazer alterações ou adicionar comentários.\n"
+#~ msgid ""
+#~ "Edit the <filename>/home/smoore/sam.xml</filename> file to make changes "
+#~ "or add comments."
+#~ msgstr ""
+#~ "Edite o ficheiro <filename>/home/ze/nuno.xml</filename> para fazer "
+#~ "alterações ou adicionar comentários."
+#~ msgid "They are also used to markup an RPM package name. For example:"
+#~ msgstr ""
+#~ "São também usadas para formatar o nome de um pacote RPM. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "To use the <application>Keyboard Configuration Tool</"
+#~ "application>, the\n"
+#~ "<filename>system-config-keyboard</filename> RPM package must "
+#~ "be installed.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Para usar a <application>Ferramenta de Configuração do Teclado</"
+#~ "application>, o pacote RPM\n"
+#~ "<filename>system-config-keyboard</filename> deverá estar "
+#~ "instalado.\n"
+#~ msgid ""
+#~ "To use the <application>Keyboard Configuration Tool</application>, the "
+#~ "<command>redhat-config-keyboard</command> RPM package must be installed."
+#~ msgstr ""
+#~ "Para usar a <application>Ferramenta de Configuração do Teclado</"
+#~ "application>, o pacote RPM <filename>system-config-keyboard</filename> "
+#~ "deverá estar instalado."
+#~ msgid ""
+#~ "Directory names must end with a forward slash (<computeroutput>/</"
+#~ "computeroutput>) to distinguish them from file names."
+#~ msgstr ""
+#~ "Os nomes das pastas deverão terminar com uma barra (<computeroutput>/</"
+#~ "computeroutput>) para os distinguir dos nomes dos ficheiros."
+#~ msgid "firstterm"
+#~ msgstr "firstterm"
+#~ msgid ""
+#~ "The <command><firstterm></command> and <command></firstterm></"
+#~ "command> tags helps to define a word that may be unfamiliar to the user, "
+#~ "but that will be seen commonly throughout the text. For example:"
+#~ msgstr ""
+#~ "As marcas <command><firstterm></command> e <command></"
+#~ "firstterm></command> ajudam a definir uma palavra que possa não "
+#~ "parecer familiar ao utilizador, mas que aparecerá frequentemente ao longo "
+#~ "do texto. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "Nearly every modern-day operating system uses <firstterm>disk\n"
+#~ "partitions</firstterm>, and Fedora is no exception.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Praticamente todos os sistemas operativos modernos usam as\n"
+#~ "<firstterm>partições de disco</firstterm> e o Fedora não é "
+#~ "excepção.\n"
+#~ msgid ""
+#~ "Nearly every modern-day operating system uses <firstterm>disk partitions</"
+#~ "firstterm>, and Fedora is no exception."
+#~ msgstr ""
+#~ "Praticamente todos os sistemas operativos modernos usam as "
+#~ "<firstterm>partições de disco</firstterm> e o Fedora não é excepção."
+#~ msgid "footnote"
+#~ msgstr "footnote"
+#~ msgid "If you need to make a footnote, use the following example:"
+#~ msgstr "Se precisar de criar uma nota de rodapé, use o seguinte exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "For those of you who need to perform a server-class\n"
+#~ "<footnote>\n"
+#~ "<para>\n"
+#~ "A server-class installation sets up a typical server\n"
+#~ "environment. Note, no graphical environment is \n"
+#~ "installed during a server-class installation.\n"
+#~ "</para> \n"
+#~ "</footnote> installation, refer to the <citetitle>"
+#~ "Installation Guide</citetitle>.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Para os que precisam de efectuar uma instalação para servidores\n"
+#~ "<footnote>\n"
+#~ "<para>\n"
+#~ "Uma instalação para servidores configura um ambiente\n"
+#~ "típico de servidores. Como nota, não é instalado nenhum\n"
+#~ "ambiente gráfico durante uma instalação para servidores.\n"
+#~ "</para> \n"
+#~ "</footnote>, veja no <citetitle>Guia de Instalação</"
+#~ "citetitle>.\n"
+#~ msgid ""
+#~ "A server-class installation sets up a typical server environment. Please "
+#~ "note, no graphical environment is installed during a server-class "
+#~ "installation."
+#~ msgstr ""
+#~ "Uma instalação para servidores configura um ambiente típico de "
+#~ "servidores. Como nota, não é instalado nenhum ambiente gráfico durante "
+#~ "uma instalação para servidores."
+
+#, fuzzy
+#~ msgid ""
+#~ "For those of you who need to perform a server-class <placeholder-1/> "
+#~ "installation, refer to the <citetitle>Installation Guide</citetitle>."
+#~ msgstr ""
+#~ "Para os que precisam de efectuar uma instalação para servidores "
+#~ "<footnote><placeholder-1/></footnote>, veja no <citetitle>Guia de "
+#~ "Instalação</citetitle>."
+#~ msgid ""
+#~ "Order matters! The EPS file <emphasis>must</emphasis> be declared first."
+#~ msgstr ""
+#~ "A ordem importa! O ficheiro EPS <emphasis>deverá</emphasis> estar "
+#~ "declarado primeiro."
+#~ msgid "An example figure declaration:"
+#~ msgstr "Uma declaração de exemplo de figuras:"
+#~ msgid ""
+#~ "\n"
+#~ "<figure id=\"fig-ksconfig-basic\">\n"
+#~ " <title>Basic Configuration</title>\n"
+#~ " <mediaobject>\n"
+#~ " <imageobject>\n"
+#~ " <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.eps\"\n"
+#~ " format=\"EPS\"/>\n"
+#~ " </imageobject>\n"
+#~ " <imageobject>\n"
+#~ " <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.png\"\n"
+#~ " format=\"PNG\"/>\n"
+#~ " </imageobject>\n"
+#~ " <textobject>\n"
+#~ " <phrase>\n"
+#~ " Some text description of this image\n"
+#~ " </phrase>\n"
+#~ " </textobject>\n"
+#~ " </mediaobject>\n"
+#~ "</figure>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<figure id=\"fig-config-basica\">\n"
+#~ " <title>Configuração Básica</title>\n"
+#~ " <mediaobject>\n"
+#~ " <imageobject>\n"
+#~ " <imagedata fileref=\"./figs/ksconfig/config-basica.eps\"\n"
+#~ " format=\"EPS\"/>\n"
+#~ " </imageobject>\n"
+#~ " <imageobject>\n"
+#~ " <imagedata fileref=\"./figs/ksconfig/config-basica.png\"\n"
+#~ " format=\"PNG\"/>\n"
+#~ " </imageobject>\n"
+#~ " <textobject>\n"
+#~ " <phrase>\n"
+#~ " Alguma descrição em texto desta imagem\n"
+#~ " </phrase>\n"
+#~ " </textobject>\n"
+#~ " </mediaobject>\n"
+#~ "</figure>\n"
+#~ msgid "The following describes what needs to be edited:"
+#~ msgstr "Os itens seguintes descrevem o que é necessário editar:"
+#~ msgid "==> id=\"\" would be edited"
+#~ msgstr "==> o id=\"\" seria editado"
+#~ msgid "==> title would be edited"
+#~ msgstr "==> o título seria editado"
+#~ msgid "==> .eps location would be edited"
+#~ msgstr "==> a localização do ficheiro .eps seria editada"
+#~ msgid "==> .png location would be edited"
+#~ msgstr "==> a localização do ficheiro .png seria editada"
+#~ msgid "==> \"Some text...\" would be edited"
+#~ msgstr "==> O \"Algum texto...\" seria editado"
+#~ msgid ""
+#~ "\n"
+#~ "<figure id=\"fig-ksconfig-basic\"> <placeholder-1/>\n"
+#~ "\n"
+#~ "<title>Basic Configuration</title> <placeholder-2/>\n"
+#~ "\n"
+#~ "fileref=\"./figs/ksconfig/ksconfig-basics.eps\"> <placeholder-3/>\n"
+#~ "\n"
+#~ "fileref=\"./figs/ksconfig/ksconfig-basics.png\"> <placeholder-4/>\n"
+#~ " \n"
+#~ "<phrase>Some text description of this image</phrase> "
+#~ "<placeholder-5/>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<figure id=\"fig-config-basica\"> <placeholder-1/>\n"
+#~ "\n"
+#~ "<title>Configuração Básica</title> <placeholder-2/>\n"
+#~ "\n"
+#~ "fileref=\"./figs/ksconfig/config-basica.eps\"> <placeholder-3/>\n"
+#~ "\n"
+#~ "fileref=\"./figs/ksconfig/config-basica.png\"> <placeholder-4/>\n"
+#~ " \n"
+#~ "<phrase>Alguma descrição em texto desta imagem</phrase> "
+#~ "<placeholder-5/>\n"
+#~ msgid ""
+#~ "For more information on taking screenshots, refer to <xref linkend=\"sn-"
+#~ "screenshots\"/>."
+#~ msgstr ""
+#~ "Para mais informações sobre como tirar fotografias, veja em <xref linkend="
+#~ "\"sn-screenshots\"/>."
+#~ msgid "GUI Tags"
+#~ msgstr "Marcas GUI"
+#~ msgid "GUI tags"
+#~ msgstr "marcas GUI"
+#~ msgid "guilabel"
+#~ msgstr "guilabel"
+#~ msgid ""
+#~ "Use the <command><guilabel></command> and <command></guilabel>"
+#~ "</command> tags as a default for GUI descriptions, like a screen name or "
+#~ "screen title. For example:"
+#~ msgstr ""
+#~ "Use as marcas <command><guilabel></command> e <command></"
+#~ "guilabel></command> por omissão para descrições gráficas, como o nome "
+#~ "ou um título de um ecrã. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "The <guilabel>Authentication Configuration</guilabel> "
+#~ "screen \n"
+#~ "shows you how to make your system more secure.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "O ecrã de <guilabel>Configuração da Autenticação</guilabel>\n"
+#~ "mostra-lhe como tornar o seu sistema mais seguro.\n"
+#~ msgid ""
+#~ "The <guilabel>Authentication Configuration</guilabel> screen shows you "
+#~ "how to make your system more secure."
+#~ msgstr ""
+#~ "O ecrã de <guilabel>Configuração da Autenticação</guilabel> mostra-lhe "
+#~ "como tornar o seu sistema mais seguro."
+#~ msgid "guibutton"
+#~ msgstr "guibutton"
+#~ msgid ""
+#~ "Use the <command><guibutton></command> and <command></"
+#~ "guibutton></command> tags to denote a button on a screen or menu. For "
+#~ "example:"
+#~ msgstr ""
+#~ "Use as marcas <command><guibutton></command> e <command></"
+#~ "guibutton></command> para demarcar um botão num ecrã ou menu. Po "
+#~ "exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "Check the <guibutton>Activate on boot</guibutton> button \n"
+#~ "to have the X Window System start automatically.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Assinale o botão <guibutton>Activar no arranque</guibutton>\n"
+#~ "para que o X Window System se inicie automaticamente.\n"
+#~ msgid ""
+#~ "Check the <guibutton>Activate on boot</guibutton> button to have the X "
+#~ "Window System start automatically."
+#~ msgstr ""
+#~ "Assinale o botão <guibutton>Activar no arranque</guibutton> para que o X "
+#~ "Window System se inicie automaticamente."
+#~ msgid "guiicon"
+#~ msgstr "guiicon"
+#~ msgid ""
+#~ "The <command><guiicon></command> and <command></guiicon></"
+#~ "command> tags are used to denote a panel or desktop icon. For example:"
+#~ msgstr ""
+#~ "As marcas <command><guiicon></command> e <command></guiicon></"
+#~ "command> são usadas para demarcar um ícone do painel ou do ambiente de "
+#~ "trabalho. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "Double-click the <guiicon>Start Here</guiicon> icon on the "
+#~ "desktop.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Faça duplo-click no ícone <guiicon>Iniciar Aqui</guiicon> do "
+#~ "ecrã.\n"
+#~ msgid "Double-click the <guiicon>Start Here</guiicon> icon on the desktop."
+#~ msgstr "Faça duplo-click no ícone <guiicon>Iniciar Aqui</guiicon> do ecrã."
+#~ msgid "<command>guimenu</command> and <command>guimenuitem</command>"
+#~ msgstr "<command>guimenu</command> e <command>guimenuitem</command>"
+#~ msgid "guimenu"
+#~ msgstr "guimenu"
+#~ msgid "guimenuitem"
+#~ msgstr "guimenuitem"
+#~ msgid ""
+#~ "To note a menu (like in the installation program or within the control "
+#~ "panel), use the <command><guimenu></command> and <command></"
+#~ "guimenu></command> tags."
+#~ msgstr ""
+#~ "Para definir um menu (como aparece no programa de instalação ou no centro "
+#~ "de controlo), use as marcas <command><guimenu></command> e "
+#~ "<command></guimenu></command>."
+#~ msgid ""
+#~ "To note submenu items, use the <command><guimenuitem></command> and "
+#~ "<command></guimenuitem></command> tags. (Please note that there "
+#~ "should not be any breaks between these commands, but for printing "
+#~ "purposes breaks have been inserted). For example:"
+#~ msgstr ""
+#~ "Para definir os itens dos sub-menus, use as marcas <command><"
+#~ "guimenuitem></command> e <command></guimenuitem></command>. "
+#~ "(Repare que não deverão existir nenhumas quebras entre estes comandos "
+#~ "mas, para fins de impressão, poderão ter sido inseridas quebras). Por "
+#~ "exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "Select \n"
+#~ "<guimenu>Main Menu</guimenu> =>\n"
+#~ "\t <guimenuitem>Programming</guimenuitem> => <"
+#~ "guimenuitem>Emacs</guimenuitem> to start the \n"
+#~ "<application>Emacs</application> text editor.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Seleccione\n"
+#~ "<guimenu>Menu Principal</guimenu> =>\n"
+#~ "\t <guimenuitem>Programação</guimenuitem> => <"
+#~ "guimenuitem>Emacs</guimenuitem> para iniciar o editor de texto\n"
+#~ "<application>Emacs</application>.\n"
+#~ msgid ""
+#~ "From the control panel, click on <guimenu>Main Menu</guimenu> => "
+#~ "<guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</"
+#~ "guimenuitem> to start the <application>Emacs</application> text editor."
+#~ msgstr ""
+#~ "No painel de controlo, seleccione <guimenu>Menu Principal</guimenu> => "
+#~ "<guimenuitem>Programação</guimenuitem> => <guimenuitem>Emacs</"
+#~ "guimenuitem> para iniciar o editor de texto <application>Emacs</"
+#~ "application>."
+#~ msgid "keycap"
+#~ msgstr "keycap"
+#~ msgid ""
+#~ "To denote a specific key, you will need to use the <command><keycap>"
+#~ "</command> and <command></keycap></command> tags. Brackets are "
+#~ "automatically added around the keycap, so do not add them in your XML "
+#~ "code. For example:"
+#~ msgstr ""
+#~ "Para apresentar uma tecla específica, terá de usar as marcas <command><"
+#~ "keycap></command> e <command></keycap></command>. Os parêntesis "
+#~ "rectos serão adicionados automaticamente em torno da tecla, por isso não "
+#~ "os adicione no seu código em XML. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "To make your selection, press the <keycap>Enter</keycap> "
+#~ "key.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Para fazer a sua selecção, carregue na tecla <keycap>Enter</"
+#~ "keycap>.\n"
+#~ msgid "To make your selection, press the <keycap>Enter</keycap> key."
+#~ msgstr ""
+#~ "Para fazer a sua selecção, carregue na tecla <keycap>Enter</keycap>."
+#~ msgid "menuchoice"
+#~ msgstr "menuchoice"
+#~ msgid ""
+#~ "Often using a mouse is tedious for common tasks. Therefore, programmers "
+#~ "often build in keyboard-shortcuts to simplify their program. These should "
+#~ "be described using the shortcut tag as a wrapper for the keyboard tags. "
+#~ "The shortcut tag must be wrapped inside the menuchoice tag. For example:"
+#~ msgstr ""
+#~ "Normalmente, a utilização de um rato é aborrecida para as tarefas comuns. "
+#~ "Como tal, os programadores baseiam-se frequentemente nas combinações de "
+#~ "teclas de atalho para simplificar o seu programa. Estas deverão ser "
+#~ "descritas com a marca 'shortcut', como uma envolvência para as marcas de "
+#~ "teclado. A marca 'shortcut' deverá estar envolvida dentro da marca "
+#~ "'menuchoice'. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "Go to the menu bar and choose: \n"
+#~ " <menuchoice>\n"
+#~ " <shortcut>\n"
+#~ " <keycombo><keycap>Ctrl</keycap><keycap>s</"
+#~ "keycap></keycombo>\n"
+#~ " </shortcut>\n"
+#~ " <guimenu><accel>F</accel>ile</guimenu>\n"
+#~ " <guimenuitem><accel>S</accel>ave</"
+#~ "guimenuitem>\n"
+#~ " </menuchoice>.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Vá para a barra de menu e escolha:\n"
+#~ " <menuchoice>\n"
+#~ " <shortcut>\n"
+#~ " <keycombo><keycap>Ctrl</keycap><keycap>s</"
+#~ "keycap></keycombo>\n"
+#~ " </shortcut>\n"
+#~ " <guimenu><accel>F</accel>icheiro</guimenu>\n"
+#~ " <guimenuitem><accel>G</accel>ravar</"
+#~ "guimenuitem>\n"
+#~ " </menuchoice>.\n"
+#~ msgid ""
+#~ "Go to the menu bar and choose: "
+#~ "<menuchoice><shortcut><keycombo><keycap>Ctrl</keycap><keycap>s</keycap></"
+#~ "keycombo></shortcut><guimenu><accel>F</accel>ile</"
+#~ "guimenu><guimenuitem><accel>S</accel>ave</guimenuitem></menuchoice>."
+#~ msgstr ""
+#~ "Vá para a barra de menu e escolha: "
+#~ "<menuchoice><shortcut><keycombo><keycap>Ctrl</keycap><keycap>s</keycap></"
+#~ "keycombo></shortcut><guimenu><accel>F</accel>icheiro</"
+#~ "guimenu><guimenuitem><accel>G</accel>ravar</guimenuitem></menuchoice>."
+#~ msgid "keycombo"
+#~ msgstr "keycombo"
+#~ msgid ""
+#~ "To illustrate a key combination, you need to use the <command><"
+#~ "keycombo></command> and <command></keycombo></command>, "
+#~ "<command><keycap></command> and <command></keycap></command> "
+#~ "tags. For example:"
+#~ msgstr ""
+#~ "Para ilustrar uma combinação de teclas, terá de usar as marcas "
+#~ "<command><keycombo></command> e <command></keycombo></"
+#~ "command>, <command><keycap></command> e <command></keycap></"
+#~ "command>. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "To reboot your system, press <keycombo>\n"
+#~ "<keycap>Ctrl</keycap><keycap>Alt</keycap><"
+#~ "keycap>Del</keycap>\n"
+#~ "</keycombo>.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Para reiniciar o seu sistema, carregue em <keycombo>\n"
+#~ "<keycap>Ctrl</keycap><keycap>Alt</keycap><"
+#~ "keycap>Del</keycap>\n"
+#~ "</keycombo>.\n"
+#~ msgid ""
+#~ "To reboot your system, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</"
+#~ "keycap><keycap>Del</keycap></keycombo>."
+#~ msgstr ""
+#~ "Para reiniciar o seu sistema, carregue em <keycombo><keycap>Ctrl</"
+#~ "keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo>."
+#~ msgid "lists"
+#~ msgstr "listas"
+#~ msgid "creating"
+#~ msgstr "criar"
+#~ msgid ""
+#~ "There are several types of lists you can create using XML. You can have a "
+#~ "itemized (bulleted) list, a ordered (numbered) list, or a variable list "
+#~ "(presents a term and then a separate paragraph)."
+#~ msgstr ""
+#~ "Existem diversos tipos de listas que poderá criar em XML. Poderá ter uma "
+#~ "lista por itens (pontos), uma lista ordenada (numerada) ou uma lista "
+#~ "variável (apresenta um termo e depois um parágrafo separado)."
+#~ msgid ""
+#~ "There is also a list format for tables and for for creating a list of "
+#~ "glossary terms and their definitions."
+#~ msgstr ""
+#~ "Existem também um formato em lista para as tabelas e para criar uma lista "
+#~ "de termos de glossário e as suas definições."
+#~ msgid ""
+#~ "The sections below will discuss the proper uses for the various list and "
+#~ "how to create them."
+#~ msgstr ""
+#~ "As secções abaixo irão discutir as utilizações correctas das diversas "
+#~ "listas, bem como descrições para a sua criação."
+#~ msgid ""
+#~ "An <command>ItemizedList</command> is best used to present information "
+#~ "that is important for the reader to know, but that does not need to be in "
+#~ "a specific order. It is shorter than a <command>VariableList</command> "
+#~ "and presents the information in a very simple way."
+#~ msgstr ""
+#~ "Uma <command>ItemizedList</command> (lista por itens) é melhor usada para "
+#~ "apresentar informações que sejam importantes para o leitor, mas esta não "
+#~ "necessita de estar por uma determinada ordem. É mais reduzida que uma "
+#~ "<command>VariableList</command> (lista variável) e apresenta a informação "
+#~ "de uma forma muito simples."
+#~ msgid ""
+#~ "To create an <command>ItemizedList</command> (otherwise known as bulleted "
+#~ "list), use the following command sequence:"
+#~ msgstr ""
+#~ "Para criar uma <command>ItemizedList</command> (também conhecida por "
+#~ "lista por pontos), use a seguinte sequência de comandos:"
+#~ msgid ""
+#~ "Notice below that the text for the list item is directly surrounded by "
+#~ "the <command>para</command> tags. If you do not do this, you will find "
+#~ "extra whitespace in your lists where the text does not line up correctly. "
+#~ "This is most noticeable when you have a series of list items that consist "
+#~ "of multiple lines of text. This whitespace is not as noticeable in the "
+#~ "HTML output as it is in the PDFs."
+#~ msgstr ""
+#~ "Repare em baixo que o texto do item da lista está directamente rodeado "
+#~ "pelas marcas <command>para</command>. Se não fizer isto, irá encontrar "
+#~ "espaços em branco extra nas suas listas, sobre as quais o texto não se "
+#~ "irá alinhar correctamente. Isto nota-se mais quando tiver uma série de "
+#~ "itens da lista que consistam em diversas linhas de texto. Este espaço em "
+#~ "branco não é tão notório no resultado em HTML como será nos PDFs."
+#~ msgid ""
+#~ "\n"
+#~ "<itemizedlist> \n"
+#~ " <listitem>\n"
+#~ " <para>Getting familiar with the installation program's user "
+#~ "interface</para>\n"
+#~ " </listitem>\n"
+#~ "\n"
+#~ " <listitem>\n"
+#~ " <para>Starting the installation program</para> \n"
+#~ " </listitem>\n"
+#~ "\n"
+#~ " <listitem>\n"
+#~ " <para>Selecting an installation method</para>\n"
+#~ " </listitem>\n"
+#~ "</itemizedlist>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<itemizedlist> \n"
+#~ " <listitem>\n"
+#~ " <para>Familiarizar-se com a interface de utilizador do programa "
+#~ "de instalação</para>\n"
+#~ " </listitem>\n"
+#~ "\n"
+#~ " <listitem>\n"
+#~ " <para>Iniciar o programa de instalação</para> \n"
+#~ " </listitem>\n"
+#~ "\n"
+#~ " <listitem>\n"
+#~ " <para>Seleccionar um método de instalação</para>\n"
+#~ " </listitem>\n"
+#~ "</itemizedlist>\n"
+#~ msgid "The output looks like:"
+#~ msgstr "O resultado ficará semelhante a:"
+#~ msgid "Getting familiar with the installation program's user interface"
+#~ msgstr ""
+#~ "Familiarizar-se com a interface de utilizador do programa de instalação"
+#~ msgid "Starting the installation program"
+#~ msgstr "Iniciar o programa de instalação"
+#~ msgid "Selecting an installation method"
+#~ msgstr "Seleccionar um método de instalação"
+#~ msgid "OrderedList"
+#~ msgstr "OrderedList"
+#~ msgid ""
+#~ "An <command>orderedlist</command> is best used to present information "
+#~ "that is important for the reader to know in a specific order. "
+#~ "<command>orderedlist</command>s are a good way to convey step-by-step "
+#~ "senarios to the audience you are writing for."
+#~ msgstr ""
+#~ "Uma <command>orderedlist</command> (lista ordenada) é melhor para "
+#~ "apresentar informações importantes para o leitor, mas que este as saiba "
+#~ "por uma determinada ordem. As <command>orderedlist</command>s são uma boa "
+#~ "forma de explicar cenários passo-a-passo à audiência para a qual está a "
+#~ "escrever."
+#~ msgid ""
+#~ "To create an <command>orderedlist</command> (numbered list), use the "
+#~ "following XML code sequence:"
+#~ msgstr ""
+#~ "Para criar uma <command>orderedlist</command> (lista numerada), use a "
+#~ "seguinte sequência de código em XML:"
+#~ msgid ""
+#~ "\n"
+#~ "<orderedlist>\n"
+#~ " <listitem>\n"
+#~ " <para>Online &mdash; http://www.redhat.com/support/errata; "
+#~ "supplies errata\n"
+#~ " you can read online, and you can download diskette images\n"
+#~ " easily.</para>\n"
+#~ " </listitem>\n"
+#~ "\t \n"
+#~ " <listitem>\n"
+#~ " <para>Email &mdash; By sending an empty mail message to "
+#~ "errata@@redhat.com, \n"
+#~ " you will receive an email containing a text listing of the \n"
+#~ " complete errata of the installation program and related software \n"
+#~ " (if errata exist at that time). Also included are URLs to each \n"
+#~ " updated package and diskette image in the errata. Using these \n"
+#~ " URLs, you can download any necessary diskette images. Please \n"
+#~ " note: use binary mode when transferring a diskette image.</"
+#~ "para> \n"
+#~ " </listitem>\n"
+#~ "</orderedlist>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<orderedlist>\n"
+#~ " <listitem>\n"
+#~ " <para>Online &mdash; http://www.redhat.com/support/errata; "
+#~ "oferece uma errata\n"
+#~ " que poderá ler 'online', e onde poderá obter imagens de disquetes\n"
+#~ " com facilidade.</para>\n"
+#~ " </listitem>\n"
+#~ "\t \n"
+#~ " <listitem>\n"
+#~ " <para>E-mail &mdash; Se enviar uma mensagem de e-mail vazia "
+#~ "para errata@@redhat.com, \n"
+#~ " irá receber um e-mail que contém uma listagem em texto da errata "
+#~ "completa\n"
+#~ " do programa de instalação e das aplicações relacionadas (se existir "
+#~ "alguma\n"
+#~ " nessa altura). Também estão incluídos os URLS de cada pacote "
+#~ "actualizado\n"
+#~ " e da imagem da disquete na errata. Se usar estes URLs, poderá obter "
+#~ "as\n"
+#~ " imagens de disquetes necessárias. Repare por favor: use o modo "
+#~ "binário\n"
+#~ " quando transferir uma imagem de disquete.</para> \n"
+#~ " </listitem>\n"
+#~ "</orderedlist>\n"
+#~ msgid ""
+#~ "Online — http://www.redhat.com/support/errata; supplies errata you "
+#~ "can read online, and you can download diskette images easily."
+#~ msgstr ""
+#~ "Online — http://www.redhat.com/support/errata; oferece uma errata "
+#~ "que poderá ler 'online', e onde poderá obter imagens de disquetes com "
+#~ "facilidade."
+#~ msgid ""
+#~ "Email — By sending an empty mail message to errata@@redhat.com, you "
+#~ "will receive an email containing a text listing of the complete errata of "
+#~ "the installation program and related software (if errata exist at that "
+#~ "time). Also included are URLs to each updated package and diskette image "
+#~ "in the errata. Using these URLs, you can download any necessary diskette "
+#~ "images. Please note: use binary mode when transferring a diskette image."
+#~ msgstr ""
+#~ "E-mail — Se enviar uma mensagem de e-mail vazia para errata@@redhat."
+#~ "com, irá receber um e-mail que contém uma listagem em texto da errata "
+#~ "completa do programa de instalação e das aplicações relacionadas (se "
+#~ "existir alguma nessa altura). Também estão incluídos os URLS de cada "
+#~ "pacote actualizado e da imagem da disquete na errata. Se usar estes URLs, "
+#~ "poderá obter as imagens de disquetes necessárias. Repare por favor: use o "
+#~ "modo binário quando transferir uma imagem de disquete."
+#~ msgid "Variablelist"
+#~ msgstr "Variablelist"
+#~ msgid ""
+#~ "A <command>variablelist</command> best represents a list of terms and "
+#~ "definitions or descriptions for those terms."
+#~ msgstr ""
+#~ "Uma <command>variablelist</command> (lista variável) representa uma lista "
+#~ "de termos e definições ou descrições desses termos."
+#~ msgid ""
+#~ "To create a <command>variablelist</command>, use the following command "
+#~ "sequence:"
+#~ msgstr ""
+#~ "Para criar uma <command>variablelist</command>, use a seguinte sequência "
+#~ "de comandos:"
+#~ msgid ""
+#~ "\n"
+#~ "<variablelist>\n"
+#~ " <varlistentry> \n"
+#~ " <term> New Multi-CD Install </term>\n"
+#~ " <listitem> \n"
+#~ " <para>As the installation program continues to grow, Red Hat "
+#~ "has developed \n"
+#~ " an installation program capable of installing from \n"
+#~ " multiple CD-ROMs.</para>\n"
+#~ " </listitem>\n"
+#~ " </varlistentry>\n"
+#~ "\n"
+#~ " <varlistentry>\n"
+#~ " <term>XFree 4.0 </term>\n"
+#~ " <listitem>\n"
+#~ " <para>Configuration of your X Window System during the "
+#~ "installation has \n"
+#~ " never been more thorough. From choosing your monitor and its "
+#~ "correct \n"
+#~ " settings, to video card probing, to testing your desired X setup, \n"
+#~ " Xconfigurator will help you set everything just right.</"
+#~ "para>\n"
+#~ " </listitem>\n"
+#~ " </varlistentry>\n"
+#~ "</variablelist>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<variablelist>\n"
+#~ " <varlistentry> \n"
+#~ " <term> Nova Instalação Multi-CDs</term>\n"
+#~ " <listitem> \n"
+#~ " <para>À medida que o programa de instalação continua a "
+#~ "crescer,\n"
+#~ " a Red Hat criou um programa de instalação que consegue instalar a "
+#~ "partir\n"
+#~ " de vários CD-ROMs.</para>\n"
+#~ " </listitem>\n"
+#~ " </varlistentry>\n"
+#~ "\n"
+#~ " <varlistentry>\n"
+#~ " <term>XFree 4.0 </term>\n"
+#~ " <listitem>\n"
+#~ " <para>A configuração do seu X Window System durante a "
+#~ "instalação\n"
+#~ " nunca foi tão abrangente. Desde escolher o seu monitor e as suas\n"
+#~ " respectivas opções, até à detecção da placa gráfica, ao teste da "
+#~ "sua\n"
+#~ " configuração do X, o Xconfigurator ajudá-lo-á a configurar tudo \n"
+#~ " facilmente.</para>\n"
+#~ " </listitem>\n"
+#~ " </varlistentry>\n"
+#~ "</variablelist>\n"
+#~ msgid "New Multi-CD Install"
+#~ msgstr "Nova Instalação Multi-CDs"
+#~ msgid ""
+#~ "As the installation program continues to grow, Red Hat has developed an "
+#~ "installation program capable of installing from multiple CD-ROMs."
+#~ msgstr ""
+#~ "À medida que o programa de instalação continua a crescer, a Red Hat criou "
+#~ "um programa de instalação que consegue instalar a partir de vários CD-"
+#~ "ROMs."
+#~ msgid "XFree 4.0"
+#~ msgstr "XFree 4.0"
+#~ msgid ""
+#~ "Configuration of your X Window System during the installation has never "
+#~ "been more thorough. From choosing your monitor and its correct settings, "
+#~ "to video card probing, to testing your desired X setup, Xconfigurator "
+#~ "will help you set everything just right."
+#~ msgstr ""
+#~ "A configuração do seu X Window System durante a instalação nunca foi tão "
+#~ "abrangente. Desde escolher o seu monitor e as suas respectivas opções, "
+#~ "até à detecção da placa gráfica, ao teste da sua configuração do X, o "
+#~ "Xconfigurator ajudá-lo-á a configurar tudo facilmente."
+#~ msgid ""
+#~ "Do <emphasis>not</emphasis> specify the <computeroutput>frame</"
+#~ "computeroutput> attribute to the table. Doing so breaks PDF production."
+#~ msgstr ""
+#~ "<emphasis>Não</emphasis> defina o atributo <computeroutput>frame</"
+#~ "computeroutput> da tabela. Se fizer isso, impede a geração de PDFs."
+#~ msgid "Creating a List Within a Table Using <command>Simplelist</command>"
+#~ msgstr ""
+#~ "Criar uma Lista Dentro de uma Tabela com uma <command>SimpleList</command>"
+#~ msgid "simplelist"
+#~ msgstr "simplelist"
+#~ msgid "creating a list within a table"
+#~ msgstr "criar uma lista dentro de uma tabela"
+#~ msgid ""
+#~ "A <command>simplelist</command> is an unadorned list of items. "
+#~ "<command>simplelist</command>s can be inline or arranged in columns."
+#~ msgstr ""
+#~ "Uma <command>simplelist</command> é lista sem qualquer enfeite dos itens. "
+#~ "As <command>simplelist</command>s podem ser incorporadas ou organizadas "
+#~ "em colunas."
+#~ msgid ""
+#~ "We use <command>simplelist</command> to add separate paragraphs of text "
+#~ "within a table element. A regular list, such as <command>itemizedlist</"
+#~ "command>, cannot be embedded within a table."
+#~ msgstr ""
+#~ "É usada a <command>simplelist</command> para adicionar parágrafos "
+#~ "separados de texto dentro de um elemento de tabela. Uma lista normal, "
+#~ "como a <command>itemizedlist</command>, não poderá ser incorporada dentro "
+#~ "de uma tabela."
+#~ msgid "The XML commands for a table look like:"
+#~ msgstr "Os comandos em XML de uma tabela assemelham-se a:"
+#~ msgid ""
+#~ "\n"
+#~ "\t <table id=\"tb-hwinfo-hostbus\">\n"
+#~ "\t <title>Host Bus Adapter Features and Configuration "
+#~ "Requirements</title>\n"
+#~ "\t \n"
+#~ "\t <tgroup cols=\"3\">\n"
+#~ "\t <colspec colnum=\"1\" colname=\"HostBus\" colwidth=\"33\"/"
+#~ ">\n"
+#~ "\t <colspec colnum=\"2\" colname=\"Features\" colwidth=\"34\"/"
+#~ ">\n"
+#~ "\t <colspec colnum=\"3\" colname=\"Single\" colwidth=\"33\"/>\n"
+#~ "\t \n"
+#~ "\t <thead>\n"
+#~ "\t\t<row>\n"
+#~ "\t\t <entry>Host Bus Adapter</entry>\n"
+#~ "\t\t <entry>Features</entry>\n"
+#~ "\t\t <entry>Single-Initiator Configuration</entry>\n"
+#~ "\t\t</row>\n"
+#~ "\t </thead>\n"
+#~ "\t \n"
+#~ "\t <tbody>\n"
+#~ "\t\t\n"
+#~ "\t\t<row>\n"
+#~ "\t\t <entry>Adaptec 2940U2W</entry>\n"
+#~ "\t\t \n"
+#~ "\t\t <entry><simplelist> \n"
+#~ "\t\t <member>Ultra2, wide, LVD.</member>\n"
+#~ "\t\t <member>HD68 external connector.</member>\n"
+#~ "\t\t <member>One channel, with two bus segments.</"
+#~ "member>\n"
+#~ "\t\t <member>Set the onboard termination by using the BIOS\n"
+#~ "\t\t\tutility.</member>\n"
+#~ "\t\t <member>Onboard termination is disabled when the power "
+#~ "is\n"
+#~ "\t\t\toff.</member>\n"
+#~ "\t\t </simplelist></entry>\n"
+#~ "\t\t \n"
+#~ "\t\t <entry><simplelist>\n"
+#~ "\t\t <member>Set the onboard termination to automatic (the\n"
+#~ "\t\t\tdefault).</member>\n"
+#~ "\t\t <member>Use the internal SCSI connector for private\n"
+#~ "\t\t\t(non-cluster) storage.</member>\n"
+#~ "\t\t </simplelist></entry>\n"
+#~ "\t\t</row>\n"
+#~ "\t\t\n"
+#~ "\t\t<row>\n"
+#~ "\t\t <entry>Qlogic QLA1080</entry>\n"
+#~ "\t\t \n"
+#~ "\t\t <entry><simplelist> \n"
+#~ "\t\t <member>Ultra2, wide, LVD</member>\n"
+#~ "\t\t <member>VHDCI external connector</member>\n"
+#~ "\t\t <member>One channel</member>\n"
+#~ "\t\t <member>Set the onboard termination by using the BIOS\n"
+#~ "\t\t\tutility.</member>\n"
+#~ "\t\t <member>Onboard termination is disabled when the power is "
+#~ "off,\n"
+#~ "\t\t\tunless jumpers are used to enforce termination.</member>\n"
+#~ "\t\t </simplelist></entry>\n"
+#~ "\t\t \n"
+#~ "\t\t \n"
+#~ "\t\t <entry><simplelist> \n"
+#~ "\t\t <member>Set the onboard termination to\n"
+#~ "\t\t\tautomatic (the default).</member>\n"
+#~ "\t\t <member>Use the internal SCSI connector for private\n"
+#~ "\t\t\t(non-cluster) storage.</member>\n"
+#~ "\t\t </simplelist></entry>\n"
+#~ "\t\t</row>\n"
+#~ "\t\t\n"
+#~ "\t </tbody>\n"
+#~ "\t </tgroup>\n"
+#~ "\t </table>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "\t <table id=\"tb-hwinfo-hostbus\">\n"
+#~ "\t <title>Funcionalidades e Requisitos de Configuração do "
+#~ "Adaptador-Anfitrião do Barramento</title>\n"
+#~ "\t \n"
+#~ "\t <tgroup cols=\"3\">\n"
+#~ "\t <colspec colnum=\"1\" colname=\"Barramento\" colwidth=\"33\"/"
+#~ ">\n"
+#~ "\t <colspec colnum=\"2\" colname=\"Funcionalidades\" colwidth=\"34"
+#~ "\"/>\n"
+#~ "\t <colspec colnum=\"3\" colname=\"Único\" colwidth=\"33\"/>\n"
+#~ "\t \n"
+#~ "\t <thead>\n"
+#~ "\t\t<row>\n"
+#~ "\t\t <entry>Adaptador-Anfitrião do Barramento</entry>\n"
+#~ "\t\t <entry>Funcionalidades</entry>\n"
+#~ "\t\t <entry>Configuração do Iniciador Único</entry>\n"
+#~ "\t\t</row>\n"
+#~ "\t </thead>\n"
+#~ "\t \n"
+#~ "\t <tbody>\n"
+#~ "\t\t\n"
+#~ "\t\t<row>\n"
+#~ "\t\t <entry>Adaptec 2940U2W</entry>\n"
+#~ "\t\t \n"
+#~ "\t\t <entry><simplelist> \n"
+#~ "\t\t <member>Ultra2, wide, LVD.</member>\n"
+#~ "\t\t <member>conector externo HD68.</member>\n"
+#~ "\t\t <member>Um canal, com dois segmentos do barramento.</"
+#~ "member>\n"
+#~ "\t\t <member>Configurar a terminação na placa com o utilitário "
+#~ "da BIOS..</member>\n"
+#~ "\t\t <member>A terminação na placa está desactivada quando a "
+#~ "máquina estiver desligada.</member>\n"
+#~ "\t\t </simplelist></entry>\n"
+#~ "\t\t \n"
+#~ "\t\t <entry><simplelist>\n"
+#~ "\t\t <member>Configura a terminação na placa como automática "
+#~ "(por omissão).</member>\n"
+#~ "\t\t <member>Use o conector interno do SCSI para o "
+#~ "armazenamento\n"
+#~ "\t\t\tprivado (sem 'cluster').</member>\n"
+#~ "\t\t </simplelist></entry>\n"
+#~ "\t\t</row>\n"
+#~ "\t\t\n"
+#~ "\t\t<row>\n"
+#~ "\t\t <entry>Qlogic QLA1080</entry>\n"
+#~ "\t\t \n"
+#~ "\t\t <entry><simplelist> \n"
+#~ "\t\t <member>Ultra2, wide, LVD</member>\n"
+#~ "\t\t <member>Conector externo VHDCI</member>\n"
+#~ "\t\t <member>Um canal</member>\n"
+#~ "\t\t <member>Configura a terminação na placa com o utilitário "
+#~ "da BIOS.</member>\n"
+#~ "\t\t <member>A terminação na placa está desactivada com a "
+#~ "energia desligada, a menos que use os interruptores para forçar a "
+#~ "terminação.</member>\n"
+#~ "\t\t </simplelist></entry>\n"
+#~ "\t\t \n"
+#~ "\t\t \n"
+#~ "\t\t <entry><simplelist> \n"
+#~ "\t\t <member>Configure a terminação na placa como automática\n"
+#~ "\t\t\t (por omissão).</member>\n"
+#~ "\t\t <member>Use o conector interno do SCSI para o "
+#~ "armazenamento privado (sem 'cluster').</member>\n"
+#~ "\t\t </simplelist></entry>\n"
+#~ "\t\t</row>\n"
+#~ "\t\t\n"
+#~ "\t </tbody>\n"
+#~ "\t </tgroup>\n"
+#~ "\t </table>\n"
+#~ msgid "Host Bus Adapter Features and Configuration Requirements"
+#~ msgstr ""
+#~ "Funcionalidades do Adaptador-Anfitrião do Barramento e Requisitos de "
+#~ "Configuração"
+#~ msgid "Host Bus Adapter"
+#~ msgstr "Adaptador-Anfitrião do Barramento"
+#~ msgid "Features"
+#~ msgstr "Funcionalidades"
+#~ msgid "Single-Initiator Configuration"
+#~ msgstr "Configuração do Iniciador Único"
+#~ msgid "Adaptec 2940U2W"
+#~ msgstr "Adaptec 2940U2W"
+#~ msgid "Ultra2, wide, LVD."
+#~ msgstr "Ultra2, wide, LVD."
+#~ msgid "HD68 external connector."
+#~ msgstr "Conector externo HD68."
+#~ msgid "One channel, with two bus segments."
+#~ msgstr "Um canal, com dois segmentos do barramento."
+#~ msgid "Set the onboard termination by using the BIOS utility."
+#~ msgstr "Configure a terminação na placa com o utilitário da BIOS."
+#~ msgid "Onboard termination is disabled when the power is off."
+#~ msgstr ""
+#~ "A terminação na placa é desactivada quando é desligada a alimentação."
+#~ msgid "Set the onboard termination to automatic (the default)."
+#~ msgstr "Configure a terminação na placa como automática (por omissão)."
+#~ msgid "Use the internal SCSI connector for private (non-cluster) storage."
+#~ msgstr ""
+#~ "Use o conector interno SCSI para armazenamento privado (sem 'cluster')."
+#~ msgid "Qlogic QLA1080"
+#~ msgstr "Qlogic QLA1080"
+#~ msgid "Ultra2, wide, LVD"
+#~ msgstr "Ultra2, wide, LVD"
+#~ msgid "VHDCI external connector"
+#~ msgstr "conector externo VHDCI"
+#~ msgid "One channel"
+#~ msgstr "Um canal"
+#~ msgid ""
+#~ "Onboard termination is disabled when the power is off, unless jumpers are "
+#~ "used to enforce termination."
+#~ msgstr ""
+#~ "A terminação na placa é desactivada quando se desliga a alimentação, a "
+#~ "menos que existam interruptores para forçar a terminação."
+#~ msgid ""
+#~ "Notice how the <command>SimpleList</command> tags are used. The <"
+#~ "entry> and <simplelist> tags must be aligned beside one another, "
+#~ "otherwise you will receive a parsing error."
+#~ msgstr ""
+#~ "Repare na utilização das marcas <command>SimpleList</command>. As marcas "
+#~ "<entry> e <simplelist> deverão ser alinhadas uma ao lado da "
+#~ "outra, caso contrário irá receber um erro de processamento."
+#~ msgid ""
+#~ "For each paragraph or list item to be added within a <command>SimpleList</"
+#~ "command>, the <member> tag set must be added around that particular "
+#~ "text item."
+#~ msgstr ""
+#~ "Para cada parágrafo ou item da lista adicionado dentro de uma "
+#~ "<command>SimpleList</command>, dever-se-á adicionar uma marca <"
+#~ "member> em torno desse item de texto em particular."
+#~ msgid "glosslist"
+#~ msgstr "glosslist"
+#~ msgid ""
+#~ "Use the <command>glosslist</command> command set to create a list of "
+#~ "glossary terms and their definitions."
+#~ msgstr ""
+#~ "Use o comando <command>glosslist</command> para criar uma lista de termos "
+#~ "do glossário e as suas definições."
+#~ msgid "In XML, an example looks like the following:"
+#~ msgstr "Em XML, um exemplo poderá ser o seguinte:"
+#~ msgid ""
+#~ "\n"
+#~ "\t <glosslist>\n"
+#~ "\t <glossentry>\n"
+#~ "\t <glossterm>applet</glossterm>\n"
+#~ "\t <glossdef>\n"
+#~ "\t\t<para>A small application, usually a utility or other\n"
+#~ "\t simple program.</para>\n"
+#~ "\t </glossdef>\n"
+#~ "\t </glossentry>\n"
+#~ "\n"
+#~ "\t <glossentry>\n"
+#~ "\t <glossterm>architecture</glossterm>\n"
+#~ "\t <glossdef>\n"
+#~ "\t\t<para>The design for organization and integration of \n"
+#~ " components within a computer or computer system.</"
+#~ "para>\n"
+#~ "\t </glossdef>\n"
+#~ "\t </glossentry>\n"
+#~ "\n"
+#~ "\t <glossentry>\n"
+#~ "\t <glossterm>archive</glossterm>\n"
+#~ "\t <glossdef>\n"
+#~ "\t\t<para>To transfer files into storage for the purpose of \n"
+#~ "\t saving space and/or organization.</para>\n"
+#~ "\t </glossdef>\n"
+#~ "\t </glossentry>\n"
+#~ "\t </glosslist>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "\t <glosslist>\n"
+#~ "\t <glossentry>\n"
+#~ "\t <glossterm>applet</glossterm>\n"
+#~ "\t <glossdef>\n"
+#~ "\t\t<para>Uma pequena aplicação, normalmente um utilitário\n"
+#~ " ou outro programa simples.</para>\n"
+#~ "\t </glossdef>\n"
+#~ "\t </glossentry>\n"
+#~ "\n"
+#~ "\t <glossentry>\n"
+#~ "\t <glossterm>arquitectura</glossterm>\n"
+#~ "\t <glossdef>\n"
+#~ "\t\t<para>O desenho da organização e integração dos\n"
+#~ " componentes dentro de um computador ou sistema "
+#~ "computacional.</para>\n"
+#~ "\t </glossdef>\n"
+#~ "\t </glossentry>\n"
+#~ "\n"
+#~ "\t <glossentry>\n"
+#~ "\t <glossterm>pacote</glossterm>\n"
+#~ "\t <glossdef>\n"
+#~ "\t\t<para>Para transferir os ficheiros armazenados com o\n"
+#~ " intuito de poupar espaço e/ou organização.</para>\n"
+#~ "\t </glossdef>\n"
+#~ "\t </glossentry>\n"
+#~ "\t </glosslist>\n"
+#~ msgid "applet"
+#~ msgstr "applet"
+#~ msgid "A small application, usually a utility or other simple program."
+#~ msgstr ""
+#~ "Uma pequena aplicação, normalmente um utilitário ou outro programa "
+#~ "simples."
+#~ msgid "architecture"
+#~ msgstr "arquitectura"
+#~ msgid ""
+#~ "The design for organization and integration of components within a "
+#~ "computer or computer system."
+#~ msgstr ""
+#~ "O desenho da organização e integração dos componentes dentro de um "
+#~ "computador ou sistema computacional."
+#~ msgid "archive"
+#~ msgstr "pacote"
+#~ msgid ""
+#~ "To transfer files into storage for the purpose of saving space and/or "
+#~ "organization."
+#~ msgstr ""
+#~ "Para transferir os ficheiros armazenados com o intuito de poupar espaço e/"
+#~ "ou organização."
+#~ msgid "option"
+#~ msgstr "option"
+#~ msgid ""
+#~ "If you have a command that offers an option or a flag, use the "
+#~ "<command><option></command> and <command></option></command> "
+#~ "tags."
+#~ msgstr ""
+#~ "Se tiver um comando que ofereça uma opção qualquer, use as marcas "
+#~ "<command><option></command> e <command></option></command>."
+#~ msgid ""
+#~ "The <option> tag set is only meant to be used for command line "
+#~ "options, not options in configuration files."
+#~ msgstr ""
+#~ "A marca <option> só pretende ser usada para as opções da linha de "
+#~ "comandos, não para as opções dos ficheiros de configuração."
+#~ msgid "In XML, specifying an option would look like the following:"
+#~ msgstr "Em XML, a definição de uma opção ficará semelhante à seguinte:"
+#~ msgid ""
+#~ "\n"
+#~ "For example, with the command <command>ls</command> you can \n"
+#~ "specify an option such as <option>-la</option>.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Por exemplo, com o comando <command>ls</command>, poderá\n"
+#~ "definir uma opção como a <option>-la</option>.\n"
+#~ msgid ""
+#~ "For example, with the command <command>ls</command> you can specify an "
+#~ "option such as <option>-la</option>."
+#~ msgstr ""
+#~ "Por exemplo, com o comando <command>ls</command>, poderá definir uma "
+#~ "opção como a <option>-la</option>."
+#~ msgid "Index Entries"
+#~ msgstr "Itens do Índice"
+#~ msgid "indexing"
+#~ msgstr "indexação"
+#~ msgid ""
+#~ "The following command sequence shows you the code inserted into the body "
+#~ "of the text to add an index entry to your document:"
+#~ msgstr ""
+#~ "A seguinte sequência de comandos mostra-lhe o código inserido dentro do "
+#~ "conteúdo do texto, de modo a adicionar um item do índice ao seu documento:"
+#~ msgid ""
+#~ "\n"
+#~ "<indexterm> <-- indicates a term to be placed in the index\n"
+#~ "<primary>foo</primary> <-- indicates that \"foo\" is the "
+#~ "first term\n"
+#~ "<secondary>bar</secondary> <-- \"bar\" will be listed "
+#~ "under \"foo\" \n"
+#~ "</indexterm> <-- closes this index entry\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<indexterm> <-- indica um termo a colocar no índice\n"
+#~ "<primary>xpto</primary> <-- indica que o \"xpto\" é o "
+#~ "primeiro termo\n"
+#~ "<secondary>xpto-2</secondary> <-- o \"xpto-2\" aparecerá "
+#~ "debaixo do \"xpto\"\n"
+#~ "</indexterm> <-- fecha este item do índice\n"
+#~ msgid "foo"
+#~ msgstr "xpto"
+#~ msgid "bar"
+#~ msgstr "xpto-2"
+#~ msgid ""
+#~ "The <command><seealso></command> tag allows you to reference "
+#~ "another index entry or refer to another manual. Make sure the "
+#~ "<command><seealso></command> reference you are pointing to has its "
+#~ "own entry. For example:"
+#~ msgstr ""
+#~ "A marca <command><seealso></command> permite-lhe fazer referências "
+#~ "a outros itens do índice ou referenciar outro manual. Certifique-se que o "
+#~ "<command><seealso></command> para o qual aponta tem o seu próprio "
+#~ "item. Por exemplo:"
+#~ msgid "seealso tag"
+#~ msgstr "marca 'seealso'"
+#~ msgid ""
+#~ "\n"
+#~ "<indexterm> \n"
+#~ "<primary>SWAK</primary> \n"
+#~ "<seealso>salutations</seealso>\n"
+#~ "</indexterm>\n"
+#~ "\n"
+#~ "\n"
+#~ "<indexterm> \n"
+#~ "<primary>salutations</primary> \n"
+#~ "</indexterm>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<indexterm> \n"
+#~ "<primary>SWAK</primary> \n"
+#~ "<seealso>saudações</seealso>\n"
+#~ "</indexterm>\n"
+#~ "\n"
+#~ "\n"
+#~ "<indexterm> \n"
+#~ "<primary>saudações</primary> \n"
+#~ "</indexterm>\n"
+#~ msgid "SWAK"
+#~ msgstr "SWAK"
+#~ msgid "Salutations"
+#~ msgstr "Saudações"
+#~ msgid ""
+#~ "The <command><see></command> tag allows you to reference to another "
+#~ "index entry entirely. For example:"
+#~ msgstr ""
+#~ "A marca <command><see></command> permite-lhe referenciar outro item "
+#~ "do índice por inteiro. Por exemplo:"
+#~ msgid "see tag"
+#~ msgstr "marca 'see'"
+#~ msgid ""
+#~ "\n"
+#~ "<indexterm> \n"
+#~ "<primary>Guinness</primary> \n"
+#~ "<see>beer</see> <-- beer will be listed under \n"
+#~ "the Guinness entry, but you must make sure beer also has its \n"
+#~ "own entry to refer to.\n"
+#~ "</indexterm>\n"
+#~ "\n"
+#~ "<indexterm>\n"
+#~ "<primary>beer</primary>\n"
+#~ "</indexterm>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<indexterm> \n"
+#~ "<primary>Guinness</primary> \n"
+#~ "<see>cerveja</see> <-- a 'cerveja' irá aparecer\n"
+#~ "abaixo do item 'Guinness', mas terá de garantir que a 'cerveja'\n"
+#~ "tem também o seu próprio item para ser referenciado.\n"
+#~ "</indexterm>\n"
+#~ "\n"
+#~ "<indexterm>\n"
+#~ "<primary>cerveja</primary>\n"
+#~ "</indexterm>\n"
+#~ msgid "Guinness"
+#~ msgstr "Guinness"
+#~ msgid "Beer"
+#~ msgstr "Cerveja"
+#~ msgid ""
+#~ "To view the HTML output of the index entries shown here, refer to the "
+#~ "<filename>generated-index.html</filename> file at the end of this "
+#~ "document."
+#~ msgstr ""
+#~ "Para ver o resultado em HTML dos itens do índice que aparecem aqui, veja "
+#~ "o ficheiro <filename>generated-index.html</filename> no fim deste "
+#~ "documento."
+#~ msgid ""
+#~ "How does the index get generated? If indexterms exist in the document and "
+#~ "the beginning and ending index tags exist before the end tag for the book "
+#~ "or article, an index is created because of the <command>generate.index</"
+#~ "command> stylesheet parameter, which is set to true by default."
+#~ msgstr ""
+#~ "Agora como é que o índice é gerado? Se existirem 'indexterms' no "
+#~ "documento e as marcas de início e fim do índice existirem antes da marca "
+#~ "final do livro ou do artigo, é criado um índice devido ao parâmetro "
+#~ "<command>generate.index</command> da folha de estilo, que está definido "
+#~ "como verdadeiro por omissão."
+#~ msgid "para"
+#~ msgstr "para"
+#~ msgid ""
+#~ "For any paragraph, the <command><para></command> and <command></"
+#~ "para></command> tags must open and close that particular paragraph."
+#~ msgstr ""
+#~ "Para qualquer parágrafo, as marcas <command><para></command> e "
+#~ "<command></para></command> deverão abrir e fechar esse parágrafo em "
+#~ "particular."
+#~ msgid ""
+#~ "Do not use para tags around anything other than a simple paragraph. Doing "
+#~ "so will create additional white space within the text itself."
+#~ msgstr ""
+#~ "Não use as marcas 'para' para nada que não seja um parágrafo simples. Se "
+#~ "o fizer, irá criar espaço em branco adicional dentro do próprio texto."
+#~ msgid ""
+#~ "Do not use <command><para></command> tags around the following (or, "
+#~ "to put this another way, do not embed the following within <command><"
+#~ "para></command> tags):"
+#~ msgstr ""
+#~ "Não use as marcas <command><para></command> em torno dos seguintes "
+#~ "ponto (ou, posto de outra forma, não incorpore o seguinte dentro das "
+#~ "marcas <command><para></command>):"
+#~ msgid "<screen>"
+#~ msgstr "<screen>"
+#~ msgid "<itemizedlist>"
+#~ msgstr "<itemizedlist>"
+#~ msgid "<orderedlist>"
+#~ msgstr "<orderedlist>"
+#~ msgid "<variablelist>"
+#~ msgstr "<variablelist>"
+#~ msgid "<table>"
+#~ msgstr "<table>"
+#~ msgid "parts"
+#~ msgstr "parts"
+#~ msgid ""
+#~ "In the parent file, you can separate the chapters into parts to divide "
+#~ "them into logical groups. For example, in the parent file, the "
+#~ "<command>part</command> tags surround the chapter entities:"
+#~ msgstr ""
+#~ "No ficheiro-pai, poderá separar os capítulos em partes, de modo a dividi-"
+#~ "los em grupos lógicos. Por exemplo, no ficheiro-pai, as marcas "
+#~ "<command>part</command> rodeiam as entidades do capítulo:"
+#~ msgid ""
+#~ "\n"
+#~ "<part id=\"pt-foo\">\n"
+#~ " <partintro>\n"
+#~ " <para>Some text for the part intro</para>\n"
+#~ " &CHAPTER; \n"
+#~ "\n"
+#~ " &ANOTHER-CHAPTER;\n"
+#~ "</part>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<part id=\"pt-xpto\">\n"
+#~ " <partintro>\n"
+#~ " <para>Algum texto para a introdução da parte</para>\n"
+#~ " &CAPITULO; \n"
+#~ "\n"
+#~ " &OUTRO-CAPITULO;\n"
+#~ "</part>\n"
+#~ msgid ""
+#~ "If you create a part, include a part introduction describing the contents "
+#~ "of the part. For example:"
+#~ msgstr ""
+#~ "Se criar uma parte, inclua uma introdução de uma parte que descreva o seu "
+#~ "conteúdo. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ " <part id=\"pt-setup\">\n"
+#~ " <title>Getting Setup</title>\n"
+#~ " <partintro>\n"
+#~ " <para>This section contains information you will need when "
+#~ "you first join\n"
+#~ "\tthe Docs group. You might need to refer to this part again for\n"
+#~ "\tinformation such as installing &FC;.</para>\n"
+#~ " </partintro>\n"
+#~ msgstr ""
+#~ "\n"
+#~ " <part id=\"pt-configuracao\">\n"
+#~ " <title>Compreender a Configuração</title>\n"
+#~ " <partintro>\n"
+#~ " <para>Esta secção contém informações que irá necessitar "
+#~ "quando\n"
+#~ " se juntar pela primeira vez ao grupo de Documentação. Poderá ter "
+#~ "de\n"
+#~ " referenciar esta parte de novo para mais informações, como a "
+#~ "instalação\n"
+#~ " do &FC;.</para>\n"
+#~ " </partintro>\n"
+#~ msgid ""
+#~ "In the HTML output, a separate HTML page is generated with the part "
+#~ "number, title, introduction, and TOC. In the PDF output, the same "
+#~ "information about the part is on a separate page."
+#~ msgstr ""
+#~ "No resultado em HTML, é gerada uma página separada em HTML para o número, "
+#~ "título, introdução e índice da parte. No resultado em PDF, a mesma "
+#~ "informação acerca da página está numa página em separado."
+#~ msgid "prompt"
+#~ msgstr "prompt"
+#~ msgid ""
+#~ "To show a prompt, such as a root or DOS prompt, use the <command><"
+#~ "prompt></command> and <command></prompt></command> commands. For "
+#~ "example:"
+#~ msgstr ""
+#~ "Para mostrar uma linha de comandos, como a linha de comandos do 'root' ou "
+#~ "do DOS, use os comandos <command><prompt></command> e <command></"
+#~ "prompt></command>. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "At the <prompt>LILO:</prompt> boot prompt, type linux to \n"
+#~ "boot into your Linux partition.\n"
+#~ "\n"
+#~ "At the <prompt>C:\\></prompt> prompt, type ....\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Na linha de comandos <prompt>LILO:</prompt>, escreva 'linux'\n"
+#~ "para arrancar para a sua partição de Linux.\n"
+#~ "boot into your Linux partition.\n"
+#~ "\n"
+#~ "Na linha de comandos <prompt>C:\\></prompt>, escreva ....\n"
+#~ msgid ""
+#~ "At the <prompt>LILO:</prompt> boot prompt, type linux to boot into your "
+#~ "Linux partition."
+#~ msgstr ""
+#~ "Na linha de comandos <prompt>LILO:</prompt>, escreva 'linux' para "
+#~ "arrancar para a sua partição de Linux."
+#~ msgid "At the <prompt>C:\\></prompt> prompt, type ...."
+#~ msgstr "Na linha de comandos <prompt>C:\\></prompt>, escreva ...."
+#~ msgid ""
+#~ "When showing example computer output (usually in <command>screen</"
+#~ "command> tags), do not include the prompt or command (unless the command "
+#~ "or prompt is the actually computer output you want to show)."
+#~ msgstr ""
+#~ "Ao mostrar um exemplo de resultados do computador (normalmente em marcas "
+#~ "<command>screen</command>), não inclua a linha de comandos ou o comando "
+#~ "em si (a menos que este seja de facto o resultado do computador que "
+#~ "deseja mostrar)."
+#~ msgid "replaceable"
+#~ msgstr "replaceable"
+#~ msgid ""
+#~ "To create replaceable text, use the tags <command><replaceable></"
+#~ "command> and <command></replaceable></command> around the text you "
+#~ "want to use as a variable."
+#~ msgstr ""
+#~ "Para criar texto que poderá ser substituído, use as marcas <command><"
+#~ "replaceable></command> e <command></replaceable></command> em "
+#~ "torno do texto que deseja usar como variável."
+#~ msgid ""
+#~ "This example demonstrates how to use the <command>replaceable</command> "
+#~ "tags when referencing the name of an RPM file:"
+#~ msgstr ""
+#~ "Este exemplo demonstra como usar as marcas <command>replaceable</command> "
+#~ "na referência ao nome de um ficheiro RPM:"
+#~ msgid ""
+#~ "\n"
+#~ "foo-<replaceable>version-number</replaceable>.<"
+#~ "replaceable>arch</replaceable>.rpm\n"
+#~ msgstr ""
+#~ "\n"
+#~ "xpto-<replaceable>número-versão</replaceable>.<"
+#~ "replaceable>arquitectura</replaceable>.rpm\n"
+#~ msgid "version-number"
+#~ msgstr "número-versão"
+#~ msgid "arch"
+#~ msgstr "arquitectura"
+#~ msgid ""
+#~ "\n"
+#~ "foo-<placeholder-1/>.<placeholder-2/>.rpm\n"
+#~ msgstr ""
+#~ "\n"
+#~ "xpto-<placeholder-1/>.<placeholder-2/>.rpm\n"
+#~ msgid ""
+#~ "The <command><screen></command> command is used to format text "
+#~ "within a document and is great for adding emphasis to show examples of "
+#~ "code, computer output, and more. In HTML with the Fedora CSS file, this "
+#~ "appears in box with a grey background. To use this command you only need "
+#~ "the opening <command><screen></command> and closing <command></"
+#~ "screen></command> tags around the text you are emphasizing."
+#~ msgstr ""
+#~ "O comando <command><screen></command> é usado para formatar o texto "
+#~ "dentro de um documento e é óptimo para adicionar alguma ênfase na "
+#~ "apresentação de exemplos de código, resultados do computador, entre "
+#~ "outras coisas. No HTML, com o ficheiro CSS do Fedora, este aparecerá numa "
+#~ "caixa com um fundo cinzento. Para usar este comando, só necessita do "
+#~ "<command><screen></command> de abertura e de delimitar o texto que "
+#~ "deseja realçar com a marca <command></screen></command> de fecho."
+#~ msgid ""
+#~ "When using the <command><screen></command> tag, set everything "
+#~ "within that screen to flush left. The contents of the <sgmltag class="
+#~ "\"starttag\">screen</sgmltag> element are rendered exactly as is, "
+#~ "including any indentation. Using flush left prevents extra blank space in "
+#~ "front of the text inside the gray background when the content is "
+#~ "converted to HTML."
+#~ msgstr ""
+#~ "Ao usar a marca <command><screen></command>, configure tudo dentro "
+#~ "desse ecrã para se colocar à esquerda. O conteúdo do elemento <sgmltag "
+#~ "class=\"starttag\">screen</sgmltag> é representado tal-e-qual, incluindo "
+#~ "a indentação. Se usar a remoção à esquerda, impede que apareçam espaços "
+#~ "em branco extra à frente do texto, dentro do fundo cinzento, quando o "
+#~ "conteúdo for convertido para HTML."
+#~ msgid ""
+#~ "The <command><screen></command> tag set may contain other inline "
+#~ "tags, such as <command><computeroutput></command>, <command><"
+#~ "userinput></command>, or <command><replaceable></command>. "
+#~ "Additional inline tags are not required by definition. The <command><"
+#~ "screen></command> tags by themselves may provide sufficient context, "
+#~ "especially for simple examples or file listings. Consider the context of "
+#~ "the example, and use inline tags if they are helpful to the reader."
+#~ msgstr ""
+#~ "A marca <command><screen></command> poderá conter outras marcas "
+#~ "incorporadas, como a <command><computeroutput></command>, a "
+#~ "<command><userinput></command> ou a <command><replaceable></"
+#~ "command>. As outras marcas incorporadas não são obrigatórias por "
+#~ "definição. As marcas <command><screen></command> propriamente ditas "
+#~ "poderão oferecer um contexto suficiente, especialmente no caso dos "
+#~ "exemplos simples ou das listagens de ficheiros. Considere o contexto do "
+#~ "exemplo e use as marcas incorporadas se forem úteis para o leitor."
+#~ msgid ""
+#~ "If you use inline tags, remember that line breaks inside <command><"
+#~ "screen></command> tags create line breaks in any rendered output. "
+#~ "Place any inline tags <emphasis>on the same line</emphasis> as their "
+#~ "content. Do not overuse tagging within a <command><screen></"
+#~ "command> tag set."
+#~ msgstr ""
+#~ "Se usar as marcas incorporadas, recorde-se que as quebras de linha dentro "
+#~ "das marcas <command><screen></command> criam quebras de linha no "
+#~ "resultado apresentado. Coloque as marcas incorporadas <emphasis>na mesma "
+#~ "linha</emphasis> que o seu conteúdo. Não sobrecarregue com marcas dentro "
+#~ "de uma marca <command><screen></command>."
+#~ msgid "An example of <command><screen></command> is the following:"
+#~ msgstr "Um exemplo do <command><screen></command> é o seguinte:"
+#~ msgid ""
+#~ "<screen>\n"
+#~ "This is an example of a screen. You do not need &lt;para&gt; "
+#~ "tags\n"
+#~ "within this command.\n"
+#~ "</screen>"
+#~ msgstr ""
+#~ "<screen>\n"
+#~ "Este é um exemplo de um ecrã. Não precisa de marcas &lt;para&gt;\n"
+#~ "dentro deste comando.\n"
+#~ "</screen>"
+#~ msgid ""
+#~ "\n"
+#~ "This is an example of a screen. You do not need <para> tags\n"
+#~ "within this command.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Este é um exemplo de um ecrã. Não precisa de marcas <para>\n"
+#~ "dentro deste comando.\n"
+#~ msgid "Using Inline Tags with <command>screen</command>"
+#~ msgstr "Usar Marcas Incorporadas com o <command>screen</command>"
+#~ msgid ""
+#~ "If you choose to use inline tags inside a <command><screen></"
+#~ "command> section, follow these guidelines for consistency. If the content "
+#~ "in the screen is a listing of a configuration file or the output of a "
+#~ "program, use the <command><computeroutput></command> tag set around "
+#~ "the entire output. If the user should type the example on the command "
+#~ "line or in a configuration file, use the <command><userinput></"
+#~ "command> tag set. Separate input and output with a short sentence of "
+#~ "narrative, as below:"
+#~ msgstr ""
+#~ "Se optar por usar marcas incorporadas dentro de uma secção <command><"
+#~ "screen></command>, siga estas instruções por razões de consistência. "
+#~ "Se o conteúdo no ecrã for uma listagem de um ficheiro de configuração ou "
+#~ "o resultado de um programa, use a marca <command><computeroutput></"
+#~ "command> em torno do resultado completo. Se o utilizador deverá escrever "
+#~ "o exemplo na linha de comandos ou num ficheiro de configuração, use a "
+#~ "marca <command><userinput></command>. Separe as entradas e saídas "
+#~ "com uma pequena frase narrativa, como aparece em baixo:"
+#~ msgid "<para>"
+#~ msgstr "<para>"
+#~ msgid "</para>"
+#~ msgstr "</para>"
+#~ msgid "<userinput>"
+#~ msgstr "<userinput>"
+#~ msgid "</userinput>"
+#~ msgstr "</userinput>"
+#~ msgid "</screen>"
+#~ msgstr "</screen>"
+#~ msgid "<computeroutput>"
+#~ msgstr "<computeroutput>"
+#~ msgid "</computeroutput>"
+#~ msgstr "</computeroutput>"
+#~ msgid ""
+#~ "\n"
+#~ "\t<placeholder-1/>\n"
+#~ "\t Type the following command:\n"
+#~ "\t<placeholder-2/>\n"
+#~ "\n"
+#~ "<placeholder-3/>\n"
+#~ "<placeholder-4/>command -sw file1<placeholder-5/>\n"
+#~ "<placeholder-6/>\n"
+#~ "\n"
+#~ "\t<placeholder-7/>\n"
+#~ "\t You should see the following output:\n"
+#~ "\t<placeholder-8/>\n"
+#~ "\n"
+#~ "<placeholder-9/>\n"
+#~ "<placeholder-10/>Completed, time = 0.12 sec<placeholder-11/>\n"
+#~ "<placeholder-12/>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "\t<placeholder-1/>\n"
+#~ "\t Escreva o seguinte comando:\n"
+#~ "\t<placeholder-2/>\n"
+#~ "\n"
+#~ "<placeholder-3/>\n"
+#~ "<placeholder-4/>comando -sw ficheiro1<placeholder-5/>\n"
+#~ "<placeholder-6/>\n"
+#~ "\n"
+#~ "\t<placeholder-7/>\n"
+#~ "\t Deverá ver o seguinte resultado:\n"
+#~ "\t<placeholder-8/>\n"
+#~ "\n"
+#~ "<placeholder-9/>\n"
+#~ "<placeholder-10/>Completo, tempo = 0.12 s<placeholder-11/>\n"
+#~ "<placeholder-12/>\n"
+#~ msgid "Type the following command:"
+#~ msgstr "Escreva o seguinte comando:"
+#~ msgid "command -sw file1"
+#~ msgstr "comando -sw ficheiro1"
+#~ msgid "You should see the following output:"
+#~ msgstr "Deverá ver o seguinte resultado:"
+#~ msgid "Completed, time = 0.12 sec"
+#~ msgstr "Completo, tempo = 0.12 s"
+#~ msgid ""
+#~ "When showing a command or series of commands inside <command>screen</"
+#~ "command> tags, do not show the prompt."
+#~ msgstr ""
+#~ "Ao mostrar um comando ou uma série de comandos dentro das marcas "
+#~ "<command>screen</command>, não mostre a linha de comandos."
+#~ msgid ""
+#~ "If the <command><screen></command> shows the reader how to change "
+#~ "only <emphasis>part</emphasis> of a line, mark the change with an inline "
+#~ "<command><userinput></command> tag set. You may use the "
+#~ "<command><userinput></command> tag set inside a larger area that is "
+#~ "already marked inline with <command><computeroutput></command>. Do "
+#~ "not include any extra lines of context in this case, unless excluding "
+#~ "them would confuse the reader. The following example illustrates these "
+#~ "guidelines:"
+#~ msgstr ""
+#~ "Se o <command><screen></command> mostrar ao leitor como alterar "
+#~ "apenas <emphasis>parte</emphasis> de uma linha, marque a alteração com um "
+#~ "conjunto de marcas <command><userinput></command>. Poderá usar o "
+#~ "conjunto de marcas <command><userinput></command> dentro de uma "
+#~ "área maior que já esteja marcada dentro de um <command><"
+#~ "computeroutput></command>. Não inclua as linhas extra de contexto "
+#~ "neste caso, a menos que a sua exclusão possa confundir o leitor. O "
+#~ "seguinte exemplo demonstra estas regras:"
+#~ msgid "<filename>"
+#~ msgstr "<filename>"
+#~ msgid "</filename>"
+#~ msgstr "</filename>"
+#~ msgid ""
+#~ "\n"
+#~ "\t<placeholder-1/>\n"
+#~ "\t Edit the <placeholder-2/>/etc/sysconfig/init<placeholder-3/> file as "
+#~ "follows:\n"
+#~ "\t<placeholder-4/>\n"
+#~ "\n"
+#~ "<placeholder-5/>\n"
+#~ "GRAPHICAL=<placeholder-6/>yes<placeholder-7/> \n"
+#~ "<placeholder-8/>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "\t<placeholder-1/>\n"
+#~ "\t Edite o ficheiro <placeholder-2/>/etc/sysconfig/init<placeholder-3/> "
+#~ "como se segue:\n"
+#~ "\t<placeholder-4/>\n"
+#~ "\n"
+#~ "<placeholder-5/>\n"
+#~ "GRAPHICAL=<placeholder-6/>yes<placeholder-7/> \n"
+#~ "<placeholder-8/>\n"
+#~ msgid "yes"
+#~ msgstr "yes"
+#~ msgid ""
+#~ "\n"
+#~ "GRAPHICAL=<placeholder-1/>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "GRAPHICAL=<placeholder-1/>\n"
+#~ msgid ""
+#~ "For an explanation of how to use the <command>replaceable</command> tags "
+#~ "within a set of <command>screen</command> tags, refer to <xref linkend="
+#~ "\"sn-xml-tags-replaceable\"/>."
+#~ msgstr ""
+#~ "Para uma explicação de como usar as marcas <command>replaceable</command> "
+#~ "dentro das marcas <command>screen</command>, veja em <xref linkend=\"sn-"
+#~ "xml-tags-replaceable\"/>."
+#~ msgid "Sections"
+#~ msgstr "Secções"
+#~ msgid "sections"
+#~ msgstr "secções"
+#~ msgid ""
+#~ "Within an article (or chapter if it is a DocBook XML book like the "
+#~ "<citetitle>Installation Guide</citetitle>), you can have sections and "
+#~ "subsections. <command><section></command> is always the highest "
+#~ "section and you cannot have two sections of the same level within one "
+#~ "another (a section 2 can be created within a section 1, but section 1 has "
+#~ "to be closed before another section 1 can be created). The general layout "
+#~ "follows:"
+#~ msgstr ""
+#~ "Dentro de um artigo (ou capítulo, se for um livro de DocBook em XML, como "
+#~ "o <citetitle>Guia de Instalação</citetitle>), você poderá ter secções e "
+#~ "sub-secções. A <command><section></command> é sempre a secção do "
+#~ "nível de topo e não poderá ter duas secções ao mesmo nível dentro de "
+#~ "outra (uma secção 2 poderá ser criada dentro de uma secção 1, mas a "
+#~ "secção 1 terá de ser fechada antes de poder criar outra secção 1). Segue-"
+#~ "se a disposição geral:"
+#~ msgid ""
+#~ "\n"
+#~ "<section id=\"sn-uniquename\">\n"
+#~ " <title>Insert Title Here</title>\n"
+#~ " <para>\n"
+#~ " Body text goes here.\n"
+#~ " </para>\n"
+#~ "\n"
+#~ "\n"
+#~ " <section id=\"sn-uniquename\">\n"
+#~ " <title>Insert Title Here</title>\n"
+#~ " <para>\n"
+#~ " Body text goes here.\n"
+#~ " </para>\n"
+#~ "\n"
+#~ " <sect3 id=\"s3-uniquename\">\n"
+#~ " <title>Insert Title Here</title>\n"
+#~ " <para>\n"
+#~ " Body text goes here.\n"
+#~ " </para>\n"
+#~ "\n"
+#~ " </sect3>\n"
+#~ "\n"
+#~ " </section>\n"
+#~ "\n"
+#~ "</section>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<section id=\"sn-nomeunico\">\n"
+#~ " <title>Indique Aqui o Título</title>\n"
+#~ " <para>\n"
+#~ " O texto do conteúdo vem aqui.\n"
+#~ " </para>\n"
+#~ "\n"
+#~ "\n"
+#~ " <section id=\"sn-nomeunico\">\n"
+#~ " <title>Indique Aqui o Título</title>\n"
+#~ " <para>\n"
+#~ " O texto do conteúdo vem aqui.\n"
+#~ " </para>\n"
+#~ "\n"
+#~ " <sect3 id=\"s3-nomeunico\">\n"
+#~ " <title>Indique Aqui o Título</title>\n"
+#~ " <para>\n"
+#~ " O texto do conteúdo vem aqui.\n"
+#~ " </para>\n"
+#~ "\n"
+#~ " </sect3>\n"
+#~ "\n"
+#~ " </section>\n"
+#~ "\n"
+#~ "</section>\n"
+#~ msgid ""
+#~ "If you only need one level of sections in a DocBook article, you can use "
+#~ "the <command>section</command> tag. For example:"
+#~ msgstr ""
+#~ "Se só necessitar de um nível de secções num artigo em DocBook, poderá "
+#~ "usar a marca <command>section</command>. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "<section id=\"sn-uniquename\">\n"
+#~ " <title>Insert Title Here</title>\n"
+#~ " <para>\n"
+#~ " Body text goes here.\n"
+#~ " </para>\n"
+#~ "</section>\n"
+#~ "<section id=\"sn-anothername\">\n"
+#~ " <title>Insert Title Here</title>\n"
+#~ " <para>\n"
+#~ " More body text goes here.\n"
+#~ " </para>\n"
+#~ "</section>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<section id=\"sn-nomeunico\">\n"
+#~ " <title>Indique o Título Aqui</title>\n"
+#~ " <para>\n"
+#~ " O texto do conteúdo vem aqui.\n"
+#~ " </para>\n"
+#~ "</section>\n"
+#~ "<section id=\"sn-outronome\">\n"
+#~ " <title>Indique o Título Aqui</title>\n"
+#~ " <para>\n"
+#~ " Vem mais texto de conteúdo aqui.\n"
+#~ " </para>\n"
+#~ "</section>\n"
+#~ msgid "The following is an example of creating a table."
+#~ msgstr "Segue-se um exemplo de criação de uma tabela."
+#~ msgid "\"tb-mockup-before-begin.\""
+#~ msgstr "\"tb-teste-antes-inicio.\""
+#~ msgid ""
+#~ "This tells XML that you will be creating a table and the ID name is "
+#~ "<placeholder-1/>"
+#~ msgstr ""
+#~ "Isto diz ao XML que irá criar uma tabela e que o seu nome identificador é "
+#~ "<placeholder-1/>"
+#~ msgid "This tells XML that you are creating a table with three columns."
+#~ msgstr "Isto diz ao XML que irá criar uma tabela com três colunas."
+#~ msgid "colspec"
+#~ msgstr "colspec"
+#~ msgid ""
+#~ "<placeholder-1/> says that you are giving information about the column to "
+#~ "XML"
+#~ msgstr ""
+#~ "O <placeholder-1/> indica que está a dar informações acerca da coluna ao "
+#~ "XML"
+#~ msgid "colnum=\"1\""
+#~ msgstr "colnum=\"1\""
+#~ msgid ""
+#~ "<placeholder-1/> says that you are giving specifications for the first "
+#~ "column."
+#~ msgstr ""
+#~ "O <placeholder-1/> indica que está a introduzir definições para a "
+#~ "primeira coluna."
+#~ msgid "colname=\"Features\""
+#~ msgstr "colname=\"Funcionalidades\""
+#~ msgid ""
+#~ "<placeholder-1/> says that the title for this column will be \"Features.\""
+#~ msgstr ""
+#~ "O <placeholder-1/> diz que o título desta coluna será \"Funcionalidades.\""
+#~ msgid "colwidth=\"3\""
+#~ msgstr "colwidth=\"3\""
+#~ msgid ""
+#~ "<placeholder-1/> specifies the width of the column. This can be more "
+#~ "tricky: such as two columns with widths of 1 and 2,the 1 is one-half the "
+#~ "width of the 2, in respect to the page size. But, what if you need the 1 "
+#~ "to be a little more than half of the 2, using a larger number ratio, such "
+#~ "as 10 to 20 would accomplish this. You could then change the 10 to an 11 "
+#~ "or a 12 to make it a little more than half of the second column of 20. In "
+#~ "no value is given, a value of 1 is assumed."
+#~ msgstr ""
+#~ "O <placeholder-1/> define a largura da coluna. Isto poderá ser mais "
+#~ "complicado: se tiver duas colunas com larguras 1 e 2, a 1 terá metade da "
+#~ "largura da 2, no que respeita ao tamanho da página. Contudo, se precisar "
+#~ "que a 1 seja um pouco mais de metade da 2, se usar uma proporção maior, "
+#~ "como o 10 ou 20, será mais fácil de fazer isto. Poderá então alterar o 10 "
+#~ "para um 11 ou 12, de modo a torná-lo um pouco mais de metade da segunda "
+#~ "coluna com 20. Se não for indicado nenhum valor, será usado o valor 1."
+#~ msgid "Contains one or more table row elements."
+#~ msgstr "Contém um ou mais elementos de linhas da tabela."
+#~ msgid "Contains one or more table cell (entry) elements."
+#~ msgstr "Contém um ou mais elementos de células (itens) da tabela."
+#~ msgid ""
+#~ "Table cell element, one of several in a row element, defining columns "
+#~ "within the row."
+#~ msgstr ""
+#~ "Elemento de célula da tabela, um de vários num elemento da linha, a "
+#~ "definir as colunas dentro da linha."
+#~ msgid "Contains one or more row elements, for the main text of the table."
+#~ msgstr ""
+#~ "Contém um ou mais elementos de linhas, para o texto principal da tabela."
+#~ msgid ""
+#~ "\n"
+#~ "<table id=\"tb-mockup-before-begin\">\n"
+#~ " <placeholder-1/>\n"
+#~ "\n"
+#~ "<title>Available Features of GNOME and KDE</title>\n"
+#~ "\n"
+#~ "<tgroup cols=\"3\">\n"
+#~ " <placeholder-2/>\n"
+#~ "\n"
+#~ "<colspec colnum=\"1\" colname=\"Features\" colwidth=\"3\"/>\n"
+#~ " <placeholder-3/> <placeholder-4/>\n"
+#~ " \n"
+#~ " <placeholder-5/>\n"
+#~ " \n"
+#~ " <placeholder-6/>\n"
+#~ "\n"
+#~ "<colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/>\n"
+#~ "<colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/>\n"
+#~ "\n"
+#~ "<thead>\n"
+#~ " <placeholder-7/>\n"
+#~ "\n"
+#~ "<row> \n"
+#~ " <placeholder-8/>\n"
+#~ "\n"
+#~ "<entry>Features</entry>\n"
+#~ " <placeholder-9/>\n"
+#~ "\n"
+#~ "<entry>GNOME</entry> \n"
+#~ "<entry>KDE</entry>\n"
+#~ "</row> \n"
+#~ "</thead> \n"
+#~ "\n"
+#~ "<tbody> \n"
+#~ " <placeholder-10/>\n"
+#~ "\n"
+#~ "<row> \n"
+#~ "<entry>highly configurable</entry> \n"
+#~ "<entry>yes</entry> \n"
+#~ "<entry>yes</entry> \n"
+#~ "</row> \n"
+#~ "<row> \n"
+#~ "<entry>multiple window managers </entry>\n"
+#~ "<entry>yes</entry> \n"
+#~ "<entry>yes</entry> \n"
+#~ "</row> \n"
+#~ "<row> \n"
+#~ "<entry>Internet applications</entry> \n"
+#~ "<entry>yes </entry> \n"
+#~ "<entry>yes </entry> \n"
+#~ "</row> \n"
+#~ "</tbody> \n"
+#~ "</tgroup> \n"
+#~ "</table> \n"
+#~ msgstr ""
+#~ "\n"
+#~ "<table id=\"tb-teste-antes-inicio\">\n"
+#~ " <placeholder-1/>\n"
+#~ "\n"
+#~ "<title>Funcionalidades Disponíveis no GNOME e no KDE</title>\n"
+#~ "\n"
+#~ "<tgroup cols=\"3\">\n"
+#~ " <placeholder-2/>\n"
+#~ "\n"
+#~ "<colspec colnum=\"1\" colname=\"Funcionalidades\" colwidth=\"3\"/>\n"
+#~ " <placeholder-3/> <placeholder-4/>\n"
+#~ " \n"
+#~ " <placeholder-5/>\n"
+#~ " \n"
+#~ " <placeholder-6/>\n"
+#~ "\n"
+#~ "<colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/>\n"
+#~ "<colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/>\n"
+#~ "\n"
+#~ "<thead>\n"
+#~ " <placeholder-7/>\n"
+#~ "\n"
+#~ "<row> \n"
+#~ " <placeholder-8/>\n"
+#~ "\n"
+#~ "<entry>Funcionalidades</entry>\n"
+#~ " <placeholder-9/>\n"
+#~ "\n"
+#~ "<entry>GNOME</entry> \n"
+#~ "<entry>KDE</entry>\n"
+#~ "</row> \n"
+#~ "</thead> \n"
+#~ "\n"
+#~ "<tbody> \n"
+#~ " <placeholder-10/>\n"
+#~ "\n"
+#~ "<row> \n"
+#~ "<entry>altamente configurável</entry> \n"
+#~ "<entry>sim</entry> \n"
+#~ "<entry>sim</entry> \n"
+#~ "</row> \n"
+#~ "<row> \n"
+#~ "<entry>vários gestores de janelas</entry>\n"
+#~ "<entry>sim</entry> \n"
+#~ "<entry>sim</entry> \n"
+#~ "</row> \n"
+#~ "<row> \n"
+#~ "<entry>Aplicações para a Internet</entry> \n"
+#~ "<entry>sim</entry> \n"
+#~ "<entry>sim</entry> \n"
+#~ "</row> \n"
+#~ "</tbody> \n"
+#~ "</tgroup> \n"
+#~ "</table> \n"
+#~ msgid "Available Features of GNOME and KDE"
+#~ msgstr "Funcionalidades Disponíveis no GNOME e no KDE"
+#~ msgid "GNOME"
+#~ msgstr "GNOME"
+#~ msgid "KDE"
+#~ msgstr "KDE"
+#~ msgid "highly configurable"
+#~ msgstr "altamente configurável"
+#~ msgid "multiple window managers"
+#~ msgstr "vários gestores de janelas"
+#~ msgid "Internet applications"
+#~ msgstr "Aplicações para a Internet"
+#~ msgid "list within a table"
+#~ msgstr "lista dentro de uma tabela"
+#~ msgid ""
+#~ "Creating a list within a table can be a difficult task. It requires "
+#~ "strict formatting and a set of commands that are not available for "
+#~ "command completion in <application>Emacs</application>."
+#~ msgstr ""
+#~ "A criação de uma lista dentro de uma tabela poderá ser uma tarefa "
+#~ "complicada. Necessita de uma formatação restrita e de um conjunto de "
+#~ "comandos que não estão disponíveis na completação de comandos no "
+#~ "<application>Emacs</application>."
+#~ msgid ""
+#~ "The tags you will need to use are <command><simplelist></command> "
+#~ "and <command><member></command>."
+#~ msgstr ""
+#~ "As marcas que terá de usar são a <command><simplelist></command> e "
+#~ "a <command><member></command>."
+#~ msgid ""
+#~ "The following example will show you the proper formatting for creating a "
+#~ "list within a table."
+#~ msgstr ""
+#~ "O exemplo que se segue mostrar-lhe-á a devida formatação para criar uma "
+#~ "lista dentro de uma tabela."
+#~ msgid ""
+#~ "\n"
+#~ "<table id=\"tb-hardware-powerswitch\">\n"
+#~ " <title>Power Switch Hardware Table</title>\n"
+#~ " <tgroup cols=\"4\">\n"
+#~ " <colspec colnum=\"1\" colname=\"Hardware\" colwidth=\"2\"/>\n"
+#~ " <colspec colnum=\"2\" colname=\"Quantity\" colwidth=\"2\"/>\n"
+#~ " <colspec colnum=\"3\" colname=\"Description\" colwidth=\"6\"/"
+#~ "> \n"
+#~ " <colspec colnum=\"4\" colname=\"Required\" colwidth=\"2\"/>\n"
+#~ "\n"
+#~ " <thead>\n"
+#~ "\t <row>\n"
+#~ " <entry>Hardware</entry>\n"
+#~ "\t <entry>Quantity</entry>\n"
+#~ " <entry>Description</entry>\n"
+#~ "\t <entry>Required</entry>\n"
+#~ "\t </row>\n"
+#~ " </thead>\n"
+#~ "\t \n"
+#~ " <tbody>\n"
+#~ "\t \n"
+#~ "\t<row>\n"
+#~ " <entry>Serial power switches</entry>\n"
+#~ "\n"
+#~ "\t <entry>Two</entry>\n"
+#~ "\n"
+#~ "\t <entry><simplelist> <member>Power switches enable "
+#~ "each cluster system\n"
+#~ "\t to power-cycle the other cluster system. Note that clusters are\n"
+#~ "\t configured with either serial or network attached power switches "
+#~ "and\n"
+#~ "\t not both.</member>\n"
+#~ "\t\t \n"
+#~ " <member>The following serial attached power switch "
+#~ "has been\n"
+#~ "\t fully tested:</member>\n"
+#~ "\n"
+#~ " <member>RPS-10 (model M/HD in the US, and model M/EC "
+#~ "in\n"
+#~ "\t Europe) </member>\n"
+#~ "\n"
+#~ " <member>Latent support is provided for the following "
+#~ "serial\n"
+#~ "\t attached power switch. This switch has not yet been fully\n"
+#~ " tested:</member>\n"
+#~ "\t\t \n"
+#~ "\t <member>APC Serial On/Off Switch (partAP9211), <ulink\n"
+#~ " url=\"http://www.apc.com/\">http://www.apc.com/</"
+#~ "ulink></member>\n"
+#~ " </simplelist></entry>\n"
+#~ "\n"
+#~ " <entry>Strongly recommended for data integrity under all "
+#~ "failure\n"
+#~ "\t conditions</entry>\n"
+#~ "\n"
+#~ "\t </row>\n"
+#~ " </tbody>\n"
+#~ " </tgroup>\n"
+#~ "</table>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<table id=\"tb-hardware-interruptor\">\n"
+#~ " <title>Tabela de 'Hardware' de Interruptores</title>\n"
+#~ " <tgroup cols=\"4\">\n"
+#~ " <colspec colnum=\"1\" colname=\"Hardware\" colwidth=\"2\"/>\n"
+#~ " <colspec colnum=\"2\" colname=\"Quantidade\" colwidth=\"2\"/"
+#~ ">\n"
+#~ " <colspec colnum=\"3\" colname=\"Descrição\" colwidth=\"6\"/"
+#~ "> \n"
+#~ " <colspec colnum=\"4\" colname=\"Obrigatório\" colwidth=\"2\"/"
+#~ ">\n"
+#~ "\n"
+#~ " <thead>\n"
+#~ "\t <row>\n"
+#~ " <entry>Hardware</entry>\n"
+#~ "\t <entry>Quantidade</entry>\n"
+#~ " <entry>Descrição</entry>\n"
+#~ "\t <entry>Obrigatório</entry>\n"
+#~ "\t </row>\n"
+#~ " </thead>\n"
+#~ "\t \n"
+#~ " <tbody>\n"
+#~ "\t \n"
+#~ "\t<row>\n"
+#~ " <entry>Interruptores série</entry>\n"
+#~ "\n"
+#~ "\t <entry>Dois</entry>\n"
+#~ "\n"
+#~ "\t <entry><simplelist> <member>Os interruptores "
+#~ "permitem\n"
+#~ " a cada sistema do 'cluster' controlar a alimentação do outro "
+#~ "sistema\n"
+#~ " do 'cluster'. Lembre-se que os 'cluster's são configurados com\n"
+#~ " interruptores série ou ligados à rede, não com ambos.</"
+#~ "member>\n"
+#~ "\t\t \n"
+#~ " <member>O interruptor série que se segue foi "
+#~ "testado\n"
+#~ "\t por completo:</member>\n"
+#~ "\n"
+#~ " <member>RPS-10 (modelo M/HD nos EUA e modelo M/EC\n"
+#~ "\t na Europa) </member>\n"
+#~ "\n"
+#~ " <member>O suporte latente é oferecido para o "
+#~ "seguinte\n"
+#~ " interruptor série. Este interruptor não foi completamente\n"
+#~ " testado:</member>\n"
+#~ "\t\t \n"
+#~ "\t <member>APC Interruptor On/Off Série (partAP9211), <"
+#~ "ulink\n"
+#~ " url=\"http://www.apc.com/\">http://www.apc.com/</"
+#~ "ulink></member>\n"
+#~ " </simplelist></entry>\n"
+#~ "\n"
+#~ " <entry>Altamente recomendado para a integridade dos "
+#~ "dados\n"
+#~ " em todas as condições de falha</entry>\n"
+#~ "\n"
+#~ "\t </row>\n"
+#~ " </tbody>\n"
+#~ " </tgroup>\n"
+#~ "</table>\n"
+#~ msgid ""
+#~ "Notice how the <command><simplelist></command> tag must be beside "
+#~ "the <command><entry></command> tag? If you do not format this "
+#~ "properly, it will not parse cleanly."
+#~ msgstr ""
+#~ "Reparou como a marca <command><simplelist></command> deve estar "
+#~ "dentro da marca <command><entry></command>? Se não formatar isto "
+#~ "correctamente, o processamento não será bem sucedido."
+#~ msgid "The above example will look like the following:"
+#~ msgstr "O exemplo acima ficará como o seguinte:"
+#~ msgid "Power Switch Hardware Table"
+#~ msgstr "Tabela de 'Hardware' de Interruptores"
+#~ msgid "Hardware"
+#~ msgstr "'Hardware'"
+#~ msgid "Quantity"
+#~ msgstr "Quantidade"
+#~ msgid "Required"
+#~ msgstr "Obrigatório"
+#~ msgid "Serial power switches"
+#~ msgstr "Interruptores série"
+#~ msgid "Two"
+#~ msgstr "Dois"
+#~ msgid ""
+#~ "Power switches enable each cluster system to power-cycle the other "
+#~ "cluster system. Note that clusters are configured with either serial or "
+#~ "network attached power switches and not both."
+#~ msgstr ""
+#~ "Os interruptores permitem a cada sistema do 'cluster' controlar a "
+#~ "alimentação do outro sistema do 'cluster'. Lembre-se que os 'cluster's "
+#~ "são configurados com interruptores série ou ligados à rede, não com ambos."
+#~ msgid "The following serial attached power switch has been fully tested:"
+#~ msgstr "O interruptor série que se segue foi testado por completo:"
+#~ msgid "RPS-10 (model M/HD in the US, and model M/EC in Europe)"
+#~ msgstr "RPS-10 (modelo M/HD nos EUA e modelo M/EC na Europa)"
+#~ msgid ""
+#~ "Latent support is provided for the following serial attached power "
+#~ "switch. This switch has not yet been fully tested:"
+#~ msgstr ""
+#~ "O suporte latente é oferecido para o seguinte interruptor série. Este "
+#~ "interruptor não foi completamente testado:"
+#~ msgid "http://www.apc.com/"
+#~ msgstr "http://www.apc.com/"
+#~ msgid "APC Serial On/Off Switch (partAP9211), <placeholder-1/>"
+#~ msgstr "APC Interruptor On/Off Série (partAP9211), <placeholder-1/>"
+#~ msgid "Strongly recommended for data integrity under all failure conditions"
+#~ msgstr ""
+#~ "Altamente recomendado para a integridade dos dados em todas as condições "
+#~ "de falha"
+#~ msgid "trademark"
+#~ msgstr "trademark"
+#~ msgid ""
+#~ "Do not use the trademark entities &trade;, &copy;, or &reg; "
+#~ "because the do not produce HTML output that works for all charsets. The "
+#~ "HTML output produces by these entities are declared in the DTD and cannot "
+#~ "be changed via the stylesheet."
+#~ msgstr ""
+#~ "Não use as entidades de marcas registadas &trade;, &copy; ou &"
+#~ "reg;, dado que não produzem um resultado em HTML que funcione em todas as "
+#~ "codificações de caracteres. O resultado em HTML produzido por estas "
+#~ "entidades está declarado na DTD e não poderá ser alterado com a folha de "
+#~ "estilo."
+#~ msgid ""
+#~ "Instead, use the <command>trademark</command> tag and its associates "
+#~ "classes as follows:"
+#~ msgstr ""
+#~ "Em vez disso, use a marca <command>trademark</command> e as suas classes "
+#~ "associadas, como se segue:"
+#~ msgid ""
+#~ "\n"
+#~ "<trademark>trademark symbol after me</trademark>\n"
+#~ "<trademark class=\"registered\">registered trademark symbol after "
+#~ "me</trademark>\n"
+#~ "<trademark class=\"copyright\">copyright symbol after me</"
+#~ "trademark>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<trademark>símbolo de marca a seguir a mime</trademark>\n"
+#~ "<trademark class=\"registered\">símbolo de marca registada a seguir "
+#~ "a mim</trademark>\n"
+#~ "<trademark class=\"copyright\">símbolo de direitos de cópia a "
+#~ "seguir a mim</trademark>\n"
+#~ msgid "userinput"
+#~ msgstr "userinput"
+#~ msgid ""
+#~ "To show what a user would type, use the <command>userinput</command> tag. "
+#~ "For example:"
+#~ msgstr ""
+#~ "Para mostrar o que um dado utilizador iria escrever, use a marca "
+#~ "<command>userinput</command>. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "At the prompt, type:\n"
+#~ "\n"
+#~ "<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Na linha de comandos, escreva:\n"
+#~ "\n"
+#~ "<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>\n"
+#~ msgid "At the prompt, type:"
+#~ msgstr "Na linha de comandos, escreva:"
+#~ msgid "dd if=boot.img of=/dev/fd0 bs=1440k"
+#~ msgstr "dd if=boot.img of=/dev/fd0 bs=1440k"
+#~ msgid "To create a URL link within your text, use the following example:"
+#~ msgstr ""
+#~ "Para criar uma hiperligação para um URL dentro do seu texto, use o "
+#~ "seguinte exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "Online &mdash; <ulink url=\"http://www.redhat.com/support/errata/"
+#~ "\">\n"
+#~ "http://www.redhat.com/support/errata/</ulink>; supplies errata \n"
+#~ "you can read online, and you can download diskette images easily.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Online &mdash; <ulink url=\"http://www.redhat.com/support/errata/"
+#~ "\">\n"
+#~ "http://www.redhat.com/support/errata/</ulink>; fornece uma errata\n"
+#~ "que poderá ler 'online' e onde poderá transferir imagens de disquetes com "
+#~ "facilidade.\n"
+#~ msgid ""
+#~ "Online —<ulink url=\"http://www.redhat.com/support/errata/\"> "
+#~ "http://www.redhat.com/support/errata/</ulink>; supplies errata you can "
+#~ "read online, and you can download diskette images easily."
+#~ msgstr ""
+#~ "Online — <ulink url=\"http://www.redhat.com/support/errata/"
+#~ "\">http://www.redhat.com/support/errata/</ulink>; fornece uma errata que "
+#~ "poderá ler 'online' e onde poderá transferir imagens de disquetes com "
+#~ "facilidade."
+#~ msgid ""
+#~ "If the URL does not end in a filename, it must end in a slash "
+#~ "(<computeroutput>/</computeroutput>) to be a properly formed URL. For "
+#~ "example, <ulink url=\"http://www.redhat.com/\">http://www.redhat.com/</"
+#~ "ulink>."
+#~ msgstr ""
+#~ "Se o URL não terminar com o nome de um ficheiro, deverá terminar com uma "
+#~ "barra (<computeroutput>/</computeroutput>), de modo a ser um URL "
+#~ "completamente válido. Por exemplo, <ulink url=\"http://www.redhat.com/"
+#~ "\">http://www.redhat.com/</ulink>."
+#~ msgid "wordasword"
+#~ msgstr "wordasword"
+#~ msgid ""
+#~ "The <wordasword> tag set is used to define a word meant "
+#~ "specifically as a word and not representing anything else."
+#~ msgstr ""
+#~ "O conjunto de marcas <wordasword> é usado para definir uma palavra "
+#~ "que é suposto representar mesmo uma palavra e não representar outro "
+#~ "conceito qualquer."
+#~ msgid ""
+#~ "A lot of technical documentation contains words that have overloaded "
+#~ "meanings. Sometimes it is useful to be able to use a word without "
+#~ "invoking its technical meaning. The <wordasword> element identifies "
+#~ "a word or phrase that might otherwise be interpreted in some specific "
+#~ "way, and asserts that it should be interpreted simply as a word."
+#~ msgstr ""
+#~ "Diversa documentação contém palavras que têm significados sobrepostos. "
+#~ "Algumas vezes é útil ter a possibilidade de usar uma palavra sem invocar "
+#~ "o seu significado técnico. O elemento <wordasword> identifica uma "
+#~ "palavra ou frase que poderá ser interpretada de alguma forma específica, "
+#~ "indicando que deverá ser interpretada apenas como uma palavra."
+#~ msgid ""
+#~ "It is unlikely that the presentation of this element will be able to help "
+#~ "readers understand the variation in meaning; good writing will have to "
+#~ "achieve that goal. The real value of <wordasword> lies in the fact "
+#~ "that full-text searching and indexing tools can use it to avoid false-"
+#~ "positives."
+#~ msgstr ""
+#~ "É pouco provável que a apresentação deste elemento seja capaz de ajudar "
+#~ "os leitores a compreender a diferença de significado; uma boa escrita "
+#~ "terá de conseguir esse objectivo. O valor real do <wordasword> "
+#~ "reside no facto que as ferramentas de pesquisa e indexação no texto "
+#~ "completo podê-la-ão usar para evitar falsos positivos."
+#~ msgid ""
+#~ "To use <command>grep</command> to search for the word\n"
+#~ "<wordasword>linux</wordasword>, use the command \n"
+#~ "<command>grep linux</command>."
+#~ msgstr ""
+#~ "Para usar o <command>grep</command> na pesquisa pela palavra\n"
+#~ "<wordasword>linux</wordasword>, use o comando\n"
+#~ "<command>grep linux</command>."
+#~ msgid ""
+#~ "To use <command>grep</command> to search for the word <wordasword>linux</"
+#~ "wordasword>, use the command <command>grep linux</command>."
+#~ msgstr ""
+#~ "Para usar o <command>grep</command> na pesquisa pela palavra "
+#~ "<wordasword>linux</wordasword>, use o comando <command>grep linux</"
+#~ "command>."
+#~ msgid ""
+#~ "In the example, the word \"linux\" is just a word. It is not meant to "
+#~ "convey anything about Linux as a subject, or to add relevance or meaning "
+#~ "to the content. It can be replaced with any other word without losing any "
+#~ "of the context."
+#~ msgstr ""
+#~ "No exemplo, a palavra \"linux\" é apenas uma palavra. Não diz respeito ao "
+#~ "Linux como um assunto nem pretende adicionar relevância ou significado ao "
+#~ "conteúdo. Esta poderá ser substituída por outra palavra qualquer, sem "
+#~ "perder nenhum do contexto."
+#~ msgid "xref"
+#~ msgstr "xref"
+#~ msgid ""
+#~ "To refer to other sections or chapters within a manual, use the "
+#~ "<command><xref></command> tag."
+#~ msgstr ""
+#~ "Para fazer referência a outras secções ou capítulos dentro de um manual, "
+#~ "use a marca <command><xref></command>."
+#~ msgid ""
+#~ "The output of this displays the title of the section or chapter you are "
+#~ "pointing the user to. For example:"
+#~ msgstr ""
+#~ "O resultado disto mostra o título da secção ou capítulo para onde está a "
+#~ "apontar o utilizador. Por exemplo:"
+#~ msgid ""
+#~ "\n"
+#~ "For more information about the parent file, refer to\n"
+#~ "<xref linkend=\"ch-tutorial\"></xref> and <xref linkend="
+#~ "\"sn-tutorial-article\"></xref>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Para mais informações acerca do ficheiro-pai, veja em\n"
+#~ "<xref linkend=\"ch-tutorial\"></xref> e <xref linkend=\"sn-"
+#~ "tutorial-parent\"></xref>\n"
+#~ msgid ""
+#~ "For more information about the parent file, refer to <xref linkend=\"ch-"
+#~ "tutorial\"/> and <xref linkend=\"sn-tutorial-article\"/>."
+#~ msgstr ""
+#~ "Para mais informações acerca do ficheiro-pai, veja em <xref linkend=\"ch-"
+#~ "tutorial\"></xref> e <xref linkend=\"sn-tutorial-parent\"></xref>."
+#~ msgid "Tammy Fox"
+#~ msgstr "Tammy Fox"
+#~ msgid "Johnray Fuller"
+#~ msgstr "Johnray Fuller"
+#~ msgid "Sandra Moore"
+#~ msgstr "Sandra Moore"
+#~ msgid "Paul W. Frields"
+#~ msgstr "Paul W. Frields"
+#~ msgid "The Parent File"
+#~ msgstr "O Ficheiro-Pai"
+#~ msgid ""
+#~ "\n"
+#~ "<!DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook XML V4.2//EN\"\n"
+#~ " \"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd\" [\n"
+#~ "\n"
+#~ "<!ENTITY % FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-en.xml"
+#~ "\">\n"
+#~ "%FEDORA-ENTITIES-EN;\n"
+#~ "\n"
+#~ "<!ENTITY VERSION \"0.1\"> <!-- change version of tutorial here "
+#~ "-->\n"
+#~ "\n"
+#~ "<!ENTITY DOCID \"example-tutorial-&VERSION; (2003-07-07)\"> "
+#~ "<!-- change last modified date here -->\n"
+#~ "\n"
+#~ "<!ENTITY LEGALNOTICE SYSTEM \"../common/legalnotice-en.xml\">\n"
+#~ "\n"
+#~ "\n"
+#~ "]>\n"
+#~ "\n"
+#~ "<article id=\"example-tutorial\" lang=\"en\">\n"
+#~ " <articleinfo>\n"
+#~ " <title>Example Tutorial</title>\n"
+#~ " <copyright>\n"
+#~ " <year>2003</year>\n"
+#~ " <holder>Red Hat Inc.</holder>\n"
+#~ " <holder>Tammy Fox</holder>\n"
+#~ " </copyright>\n"
+#~ " <authorgroup>\n"
+#~ " <author>\n"
+#~ "\t<surname>Fox</surname>\n"
+#~ "\t<firstname>Tammy</firstname>\n"
+#~ " </author>\n"
+#~ " </authorgroup>\n"
+#~ " &LEGALNOTICE;\n"
+#~ " </articleinfo>\n"
+#~ "\n"
+#~ " <section id=\"some-section\">\n"
+#~ " <title>Some Section</title>\n"
+#~ "\n"
+#~ " <para>\n"
+#~ " This is an example section. You can also use section, section, "
+#~ "etc.\n"
+#~ " </para>\n"
+#~ "\n"
+#~ " <warning>\n"
+#~ " <title>Warning</title>\n"
+#~ " <para>\n"
+#~ "\tExample of an admonition.\n"
+#~ " </para>\n"
+#~ " </warning>\n"
+#~ "\n"
+#~ " </section>\n"
+#~ "\n"
+#~ "<index id=\"generated-index\"></index>\n"
+#~ "</article>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<!DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook XML V4.2//EN\"\n"
+#~ " \"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd\" [\n"
+#~ "\n"
+#~ "<!ENTITY % FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-pt.xml"
+#~ "\">\n"
+#~ "%FEDORA-ENTITIES-PT;\n"
+#~ "\n"
+#~ "<!ENTITY VERSION \"0.1\"> <!-- altere aqui a versão do tutorial "
+#~ "-->\n"
+#~ "\n"
+#~ "<!ENTITY DOCID \"tutorial-exemplo-&VERSION; (2003-07-07)\"> "
+#~ "<!-- altere aqui a data da última modificação -->\n"
+#~ "\n"
+#~ "<!ENTITY LEGALNOTICE SYSTEM \"../common/legalnotice-pt.xml\">\n"
+#~ "\n"
+#~ "\n"
+#~ "]>\n"
+#~ "\n"
+#~ "<article id=\"tutorial-exemplo\" lang=\"pt\">\n"
+#~ " <articleinfo>\n"
+#~ " <title>Tutorial de Exemplo</title>\n"
+#~ " <copyright>\n"
+#~ " <year>2003</year>\n"
+#~ " <holder>Red Hat Inc.</holder>\n"
+#~ " <holder>José Pires</holder>\n"
+#~ " </copyright>\n"
+#~ " <authorgroup>\n"
+#~ " <author>\n"
+#~ "\t<surname>Pires</surname>\n"
+#~ "\t<firstname>José</firstname>\n"
+#~ " </author>\n"
+#~ " </authorgroup>\n"
+#~ " &LEGALNOTICE;\n"
+#~ " </articleinfo>\n"
+#~ "\n"
+#~ " <section id=\"uma-seccao\">\n"
+#~ " <title>Uma Secção</title>\n"
+#~ "\n"
+#~ " <para>\n"
+#~ " Esta é uma secção de exemplo. Poderá também usar 'section', "
+#~ "'section', etc.\n"
+#~ " </para>\n"
+#~ "\n"
+#~ " <warning>\n"
+#~ " <title>Aviso</title>\n"
+#~ " <para>\n"
+#~ "\tExemplo de uma chamada de atenção.\n"
+#~ " </para>\n"
+#~ " </warning>\n"
+#~ "\n"
+#~ " </section>\n"
+#~ "\n"
+#~ "<index id=\"generated-index\"></index>\n"
+#~ "</article>\n"
+#~ msgid "Including the License Information"
+#~ msgstr "Incluir a Informação da Licença"
+#~ msgid "license"
+#~ msgstr "licença"
+#~ msgid ""
+#~ "All Fedora Project manuals <emphasis>must</emphasis> contain the file "
+#~ "<filename>legalnotice.xml</filename>. This file makes the license for the "
+#~ "file the GNU Free Documentation License (FDL)."
+#~ msgstr ""
+#~ "Todos os manuais do Projecto Fedora <emphasis>deverão</emphasis> conter o "
+#~ "ficheiro <filename>legalnotice.xml</filename>. Este ficheiro faz com que "
+#~ "a licença do ficheiro seja a GNU Free Documentation License (FDL)."
+#~ msgid "The sample parent file shows how it is included."
+#~ msgstr "O ficheiro-paiu de exemplo demonstra como este é incluído."
+#~ msgid ""
+#~ "There are two types of screenshots: graphical and textual. The philosophy "
+#~ "on using these two types is <firstterm>rely on text over graphics</"
+#~ "firstterm>. This means, if you can say it in text instead of showing a "
+#~ "graphic, do so. A graphical screenshot of a GUI can create a good setting "
+#~ "of objects to then describe textually, but you don't want to create a "
+#~ "screenshot for each graphical step."
+#~ msgstr ""
+#~ "Existem dois tipos de imagens: gráficas e textuais. A filosofia na "
+#~ "utilização destes dois tipos é <firstterm>basear-se em texto acima dos "
+#~ "gráficos</firstterm>. Isto significa que, se puder dizer em texto, em vez "
+#~ "de usar um gráfico, faça-o. Uma imagem gráfica de uma GUI poderá criar "
+#~ "uma boa configuração de objectos que será depois descrita textualmente, "
+#~ "mas não será interessante criar uma imagem por cada passo gráfico."
+#~ msgid ""
+#~ "The main reason for this preference is that a block of text can usually "
+#~ "convey more meaning than the same physical space of graphics. This is "
+#~ "highly dependent on the graphic; obviously, a photographic image of a "
+#~ "scene can convey more than 1000 words can. A GUI screenshot is usually "
+#~ "full of blank space with a few elements that can just as easily be "
+#~ "described or listed."
+#~ msgstr ""
+#~ "A razão principal para esta preferência é que um bloco de texto poderá "
+#~ "conter normalmente mais significado que o mesmo espaço físico de uma "
+#~ "imagem. Isto é altamente dependente do gráfico; obviamente, uma imagem "
+#~ "vale mais que 1000 palavras. Ua imagem gráfica normalmente está cheia de "
+#~ "espaço em branco, contendo apenas alguns elementos que poderão ser "
+#~ "descritos ou listados facilmente."
+#~ msgid ""
+#~ "Set the theme to Bluecurve defaults. This gives a look that is familiar "
+#~ "to most readers, and makes Fedora Documentation Project documents "
+#~ "consistent. From the panel menu, choose <guimenu>Preferences</guimenu>, "
+#~ "<guimenuitem>Theme</guimenuitem> and select <guimenuitem>Bluecurve</"
+#~ "guimenuitem> from the theme list."
+#~ msgstr ""
+#~ "Configure o tema com as predefinições do Bluecurve. Este gera uma "
+#~ "aparência que é familiar para a maioria dos leitores, tornando também os "
+#~ "documentos do Projecto de Documentação do Fedora mais consistentes. No "
+#~ "menu do painel, escolha as <guimenu>Preferências</guimenu>, "
+#~ "<guimenuitem>Tema</guimenuitem> e depois o <guimenuitem>Bluecurve</"
+#~ "guimenuitem> na lista de temas."
+#~ msgid ""
+#~ "Set fonts to Bluecurve defaults as well. From the panel menu, choose "
+#~ "<guimenu>Preferences</guimenu>, <guimenuitem>Fonts</guimenuitem>. Set the "
+#~ "<guilabel>Application font</guilabel> and the <guilabel>Desktop font</"
+#~ "guilabel> to Sans Regular 10. Set the <guilabel>Window Title font</"
+#~ "guilabel> to Sans Bold 10. Set the <guilabel>Terminal font</guilabel> to "
+#~ "Monospace Regular 10."
+#~ msgstr ""
+#~ "Configure os tipos de letra com os predefinidos do Bluecurve. No menu do "
+#~ "painel, escolha as <guimenu>Preferências</guimenu>, <guimenuitem>Tipos de "
+#~ "Letra</guimenuitem>. Configure o <guilabel>Tipo de letra da aplicação</"
+#~ "guilabel> e o <guilabel>Tipo de letra do ambiente de trabalho</guilabel> "
+#~ "como Sans Regular 10. Configure o <guilabel>Tipo de letra do título da "
+#~ "janela</guilabel> como Sans Bold 10. Configure o <guilabel>Tipo de letra "
+#~ "do terminal</guilabel> como Monospace Regular 10."
+#~ msgid "<xref linkend=\"ex-rpminfo\"/> illustrates the content of this file:"
+#~ msgstr "O <xref linkend=\"ex-rpminfo\"/> ilustra o conteúdo deste ficheiro:"
+#~ msgid ""
+#~ "The goal of the Fedora Documentation Project is to create easy-to-follow, "
+#~ "task-based documentation for Fedora users and developers. Other than the "
+#~ "<citetitle>Installation Guide</citetitle>, each tutorial should be in "
+#~ "DocBook XML article format, with one article per topic. This way, writers "
+#~ "can contribute documentation about a specific topic without having to "
+#~ "worry about how it fits into a manual or how it flows with other topics."
+#~ msgstr ""
+#~ "O objectivo do Projecto de Documentação do Fedora é criar documentação "
+#~ "simples e baseada em tarefas para os utilizadores e programadores do "
+#~ "Fedora. Exceptuando o <citetitle>Guia de Instalação</citetitle>, cada "
+#~ "tutorial deverá estar no formato de artigos do DocBook em XML, tendo cada "
+#~ "um dos artigos por tópico. Desta forma, os escritores poderão contribuir "
+#~ "com documentação acerca de um tópico específico, sem terem de se "
+#~ "preocupar com a sua adaptação a um manual ou como este se coaduna com "
+#~ "outros tópicos."
+#~ msgid "The following tools are used:"
+#~ msgstr "São usadas as seguintes ferramentas:"
+#~ msgid "my-fedora-docs-sandbox"
+#~ msgstr "minha-pasta-documentos-fedora"
+#~ msgid ""
+#~ "mkdir <placeholder-1/>\n"
+#~ "cd <placeholder-2/>\n"
+#~ "export CVSROOT=:ext:<placeholder-3/>@@cvs.fedora.redhat.com:/cvs/docs\n"
+#~ "cvs login\n"
+#~ "cvs co docs-common"
+#~ msgstr ""
+#~ "mkdir <placeholder-1/>\n"
+#~ "cd <placeholder-2/>\n"
+#~ "export CVSROOT=:ext:<placeholder-3/>@@cvs.fedora.redhat.com:/cvs/docs\n"
+#~ "cvs login\n"
+#~ "cvs co docs-common"
+#~ msgid "At the password prompt, press the <keycap>Enter</keycap> key."
+#~ msgstr ""
+#~ "Na linha de comandos da senha, carregue na tecla <keycap>Enter</keycap>."
+#~ msgid ""
+#~ "You need to perform this \"checkout\" step only once, although you may "
+#~ "need to update the files later. These files are common to all the "
+#~ "official documentation."
+#~ msgstr ""
+#~ "Só precisa de efectuar este passo de \"extracção\" uma vez, ainda que "
+#~ "precise de actualizar os ficheiros mais tarde. Estes ficheiros são comuns "
+#~ "a toda a documentação oficial."
+#~ msgid ""
+#~ "To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+#~ msgstr ""
+#~ "Para trabalhar com os documentos existentes no CVS, consulte a secção "
+#~ "<xref linkend=\"ch-cvs\"/>."
+#~ msgid "Filename Conventions"
+#~ msgstr "Convenções de Nomes de Ficheiros"
+#~ msgid ""
+#~ "Each document lives in a peer directory to the <filename>docs-common</"
+#~ "filename> directory you extracted from the Fedora archive earlier. On the "
+#~ "CVS server, these directories are called <firstterm>modules</firstterm>. "
+#~ "Use the <command>cvs co -c</command> command to view existing module "
+#~ "names."
+#~ msgstr ""
+#~ "Cada documento reside numa pasta acompanhante da <filename>docs-common</"
+#~ "filename> que extraiu anteriormente do pacote do Fedora. No servidor de "
+#~ "CVS, estas pastas chamam-se <firstterm>módulos</firstterm>. Use o comando "
+#~ "<command>cvs co -c</command> para ver os nomes dos módulos existentes."
+#~ msgid ""
+#~ "build-docs infrastructure/build-docs\n"
+#~ "cvsroot CVSROOT\n"
+#~ "desktop-up2date desktop-up2date\n"
+#~ "developer-guide developer-guide\n"
+#~ "docs .\n"
+#~ "docs-common docs-common\n"
+#~ "documentation-guide documentation-guide\n"
+#~ "example-tutorial example-tutorial"
+#~ msgstr ""
+#~ "build-docs infrastructure/build-docs\n"
+#~ "cvsroot CVSROOT\n"
+#~ "desktop-up2date desktop-up2date\n"
+#~ "developer-guide developer-guide\n"
+#~ "docs .\n"
+#~ "docs-common docs-common\n"
+#~ "documentation-guide documentation-guide\n"
+#~ "example-tutorial example-tutorial"
+#~ msgid ""
+#~ "Choose a module name that accurately reflects your document's subject, "
+#~ "but avoid any name already taken."
+#~ msgstr ""
+#~ "Escolha um nome de módulo que reflicta com precisão o assunto do seu "
+#~ "documento, evitando qualquer nome que já tenha sido usado."
+#~ msgid ""
+#~ "For Emacs to parse your DocBook documents correctly, you must have a "
+#~ "<filename>.emacs</filename> file. Cut and paste the following into your "
+#~ "existing <filename>.emacs</filename> file or create a new one that "
+#~ "contains the following lines: <screen><computeroutput><![CDATA[\n"
+#~ ";; turn on auto-fill in `text-mode' and derived modes \n"
+#~ ";;(mail, news, etc)\n"
+#~ "(add-hook 'text-mode-hook 'turn-on-auto-fill)\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";;MODES\n"
+#~ ";;\n"
+#~ "\n"
+#~ "(setq auto-mode-alist (cons '(\"\\\\.sgml$\" . sgml-mode) auto-mode-"
+#~ "alist))\n"
+#~ "(setq auto-mode-alist (cons '(\"\\\\.sgm$\" . sgml-mode) auto-mode-"
+#~ "alist))\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";;XML!!\n"
+#~ ";;\n"
+#~ ";;#############################################################\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";;PSGML mode stuff\n"
+#~ ";;\n"
+#~ "\n"
+#~ "(autoload 'sgml-mode \"psgml\" \"My Most Major Mode\" t)\n"
+#~ "\n"
+#~ "(setq sgml-mode-hook '(lambda () \"Defaults for XML mode.\" (turn-on-auto-"
+#~ "fill) \n"
+#~ "(setq fill-column 80)))\n"
+#~ "\n"
+#~ "(defun My-XML-keymap ()\n"
+#~ " (local-set-key [(alt i)] \n"
+#~ " '(lambda ()\n"
+#~ " (interactive)\n"
+#~ " (sgml-indent-line)\n"
+#~ " (sgml-insert-element 'item)\n"
+#~ " (sgml-indent-line)))\n"
+#~ " (local-set-key [(alt l)] \n"
+#~ " '(lambda ()\n"
+#~ " (interactive)\n"
+#~ " (sgml-insert-element 'list)\n"
+#~ " (sgml-insert-element 'item)\n"
+#~ " (sgml-indent-line)))\n"
+#~ " (local-set-key [(alt p)]\n"
+#~ " '(lambda ()\n"
+#~ " (interactive)\n"
+#~ " (sgml-indent-line)\n"
+#~ " (sgml-insert-element 'para)\n"
+#~ " (sgml-indent-line)))\n"
+#~ " (local-set-key [(alt -)]\n"
+#~ " '(lambda ()\n"
+#~ " (interactive)\n"
+#~ " (insert \"—\")))) \n"
+#~ "\n"
+#~ "(add-hook 'sgml-mode-hook 'My-XML-keymap)\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";; Fix up indentation of data...\n"
+#~ ";;\n"
+#~ "\n"
+#~ "(setq-default sgml-indent-data t)\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";; XML markup faces.\n"
+#~ ";;\n"
+#~ "\n"
+#~ "(setq-default sgml-set-face t)\n"
+#~ "\n"
+#~ "\n"
+#~ "(make-face 'sgml-comment-face)\n"
+#~ "(make-face 'sgml-doctype-face)\n"
+#~ "(make-face 'sgml-end-tag-face)\n"
+#~ "(make-face 'sgml-entity-face)\n"
+#~ "(make-face 'sgml-ignored-face)\n"
+#~ "(make-face 'sgml-ms-end-face)\n"
+#~ "(make-face 'sgml-ms-start-face)\n"
+#~ "(make-face 'sgml-pi-face)\n"
+#~ "(make-face 'sgml-sgml-face)\n"
+#~ "(make-face 'sgml-short-ref-face)\n"
+#~ "(make-face 'sgml-start-tag-face)\n"
+#~ "\n"
+#~ "(set-face-foreground 'sgml-comment-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-doctype-face \"dark green\")\n"
+#~ "(set-face-foreground 'sgml-end-tag-face \"blue2\")\n"
+#~ "(set-face-foreground 'sgml-entity-face \"red2\")\n"
+#~ "(set-face-foreground 'sgml-ignored-face \"maroon\")\n"
+#~ "(set-face-background 'sgml-ignored-face \"gray90\")\n"
+#~ "(set-face-foreground 'sgml-ms-end-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-ms-start-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-pi-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-sgml-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-short-ref-face \"goldenrod\")\n"
+#~ "(set-face-foreground 'sgml-start-tag-face \"blue2\")\n"
+#~ "\n"
+#~ "(setq-default sgml-markup-faces\n"
+#~ " '((comment . sgml-comment-face)\n"
+#~ " (doctype . sgml-doctype-face)\n"
+#~ " (end-tag . sgml-end-tag-face)\n"
+#~ " (entity . sgml-entity-face)\n"
+#~ " (ignored . sgml-ignored-face)\n"
+#~ " (ms-end . sgml-ms-end-face)\n"
+#~ " (ms-start . sgml-ms-start-face)\n"
+#~ " (pi . sgml-pi-face)\n"
+#~ " (sgml . sgml-sgml-face)\n"
+#~ " (short-ref . sgml-short-ref-face)\n"
+#~ " (start-tag . sgml-start-tag-face)))\n"
+#~ "\n"
+#~ "\n"
+#~ "(defun docbook-mode ()\n"
+#~ " (sgml-mode)\n"
+#~ " )\n"
+#~ "\n"
+#~ "\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";;END XML STUFF\n"
+#~ ";;\n"
+#~ ";;##################################################################\n"
+#~ "\n"
+#~ ";PO mode stuff\n"
+#~ "\n"
+#~ "(setq auto-mode-alist\n"
+#~ "\t(cons '(\"\\\\.pox?\\\\'\" . po-mode) auto-mode-alist))\n"
+#~ "(autoload 'po-mode \"po-mode\")\n"
+#~ "\n"
+#~ "\n"
+#~ " (global-set-key [(f1)] (lambda () (interactive) (manual-\n"
+#~ " entry (current-word))))\n"
+#~ "]]></computeroutput></screen>"
+#~ msgstr ""
+#~ "Para o Emacs processar correctamente os seus documentos em DocBook, terá "
+#~ "de criar um ficheiro <filename>.emacs</filename>. Corte e cole o seguinte "
+#~ "texto no seu ficheiro <filename>.emacs</filename> existente ou crie um "
+#~ "novo que contenha as seguintes linhas:<screen><computeroutput><![CDATA[\n"
+#~ ";; activar o preenchimento automático no `text-mode' e nos modos "
+#~ "derivados\n"
+#~ ";;(mail, news, etc)\n"
+#~ "(add-hook 'text-mode-hook 'turn-on-auto-fill)\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";;MODOS\n"
+#~ ";;\n"
+#~ "\n"
+#~ "(setq auto-mode-alist (cons '(\"\\\\.sgml$\" . sgml-mode) auto-mode-"
+#~ "alist))\n"
+#~ "(setq auto-mode-alist (cons '(\"\\\\.sgm$\" . sgml-mode) auto-mode-"
+#~ "alist))\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";;XML!!\n"
+#~ ";;\n"
+#~ ";;#############################################################\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";;Coisas do modo PSGML\n"
+#~ ";;\n"
+#~ "\n"
+#~ "(autoload 'sgml-mode \"psgml\" \"O Meu Modo Maior\" t)\n"
+#~ "\n"
+#~ "(setq sgml-mode-hook '(lambda () \"Predefinições do modo XML.\" (turn-on-"
+#~ "auto-fill) \n"
+#~ "(setq fill-column 80)))\n"
+#~ "\n"
+#~ "(defun Meu-Mapa-Teclas-XML ()\n"
+#~ " (local-set-key [(alt i)] \n"
+#~ " '(lambda ()\n"
+#~ " (interactive)\n"
+#~ " (sgml-indent-line)\n"
+#~ " (sgml-insert-element 'item)\n"
+#~ " (sgml-indent-line)))\n"
+#~ " (local-set-key [(alt l)] \n"
+#~ " '(lambda ()\n"
+#~ " (interactive)\n"
+#~ " (sgml-insert-element 'list)\n"
+#~ " (sgml-insert-element 'item)\n"
+#~ " (sgml-indent-line)))\n"
+#~ " (local-set-key [(alt p)]\n"
+#~ " '(lambda ()\n"
+#~ " (interactive)\n"
+#~ " (sgml-indent-line)\n"
+#~ " (sgml-insert-element 'para)\n"
+#~ " (sgml-indent-line)))\n"
+#~ " (local-set-key [(alt -)]\n"
+#~ " '(lambda ()\n"
+#~ " (interactive)\n"
+#~ " (insert \"—\")))) \n"
+#~ "\n"
+#~ "(add-hook 'sgml-mode-hook 'Meu-Mapa-Teclas-XML)\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";; Corrigir a indentação dos dados...\n"
+#~ ";;\n"
+#~ "\n"
+#~ "(setq-default sgml-indent-data t)\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";; Faces da formatação em XML.\n"
+#~ ";;\n"
+#~ "\n"
+#~ "(setq-default sgml-set-face t)\n"
+#~ "\n"
+#~ "\n"
+#~ "(make-face 'sgml-comment-face)\n"
+#~ "(make-face 'sgml-doctype-face)\n"
+#~ "(make-face 'sgml-end-tag-face)\n"
+#~ "(make-face 'sgml-entity-face)\n"
+#~ "(make-face 'sgml-ignored-face)\n"
+#~ "(make-face 'sgml-ms-end-face)\n"
+#~ "(make-face 'sgml-ms-start-face)\n"
+#~ "(make-face 'sgml-pi-face)\n"
+#~ "(make-face 'sgml-sgml-face)\n"
+#~ "(make-face 'sgml-short-ref-face)\n"
+#~ "(make-face 'sgml-start-tag-face)\n"
+#~ "\n"
+#~ "(set-face-foreground 'sgml-comment-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-doctype-face \"dark green\")\n"
+#~ "(set-face-foreground 'sgml-end-tag-face \"blue2\")\n"
+#~ "(set-face-foreground 'sgml-entity-face \"red2\")\n"
+#~ "(set-face-foreground 'sgml-ignored-face \"maroon\")\n"
+#~ "(set-face-background 'sgml-ignored-face \"gray90\")\n"
+#~ "(set-face-foreground 'sgml-ms-end-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-ms-start-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-pi-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-sgml-face \"maroon\")\n"
+#~ "(set-face-foreground 'sgml-short-ref-face \"goldenrod\")\n"
+#~ "(set-face-foreground 'sgml-start-tag-face \"blue2\")\n"
+#~ "\n"
+#~ "(setq-default sgml-markup-faces\n"
+#~ " '((comment . sgml-comment-face)\n"
+#~ " (doctype . sgml-doctype-face)\n"
+#~ " (end-tag . sgml-end-tag-face)\n"
+#~ " (entity . sgml-entity-face)\n"
+#~ " (ignored . sgml-ignored-face)\n"
+#~ " (ms-end . sgml-ms-end-face)\n"
+#~ " (ms-start . sgml-ms-start-face)\n"
+#~ " (pi . sgml-pi-face)\n"
+#~ " (sgml . sgml-sgml-face)\n"
+#~ " (short-ref . sgml-short-ref-face)\n"
+#~ " (start-tag . sgml-start-tag-face)))\n"
+#~ "\n"
+#~ "\n"
+#~ "(defun docbook-mode ()\n"
+#~ " (sgml-mode)\n"
+#~ " )\n"
+#~ "\n"
+#~ "\n"
+#~ "\n"
+#~ ";;\n"
+#~ ";;FIM DAS COISAS DE XML\n"
+#~ ";;\n"
+#~ ";;##################################################################\n"
+#~ "\n"
+#~ ";coisas do modo PO\n"
+#~ "\n"
+#~ "(setq auto-mode-alist\n"
+#~ "\t(cons '(\"\\\\.pox?\\\\'\" . po-mode) auto-mode-alist))\n"
+#~ "(autoload 'po-mode \"po-mode\")\n"
+#~ "\n"
+#~ "\n"
+#~ " (global-set-key [(f1)] (lambda () (interactive) (manual-\n"
+#~ " entry (current-word))))\n"
+#~ "]]></computeroutput></screen>"
+#~ msgid "Create Recompiled DTD Subset"
+#~ msgstr "Criar um Sub-Conjunto da DTD Compilado de Novo"
+#~ msgid ""
+#~ "Emacs will perform syntax highlighting and indent correctly on DocBook "
+#~ "XML files if you provide it with the proper Document Type Declarations "
+#~ "(DTD) file. These two features will make your XML file look pretty and "
+#~ "help you spot errors."
+#~ msgstr ""
+#~ "O Emacs irá efectuar o realce de sintaxe e a indentação correctamente "
+#~ "para os ficheiros de DocBook em XML, se lhe fornecer o ficheiro de DTD "
+#~ "(Declarações do Tipo de Documento) adequado. Estas duas funcionalidades "
+#~ "farão com que o seu ficheiro XML fique bonito e você tenha alguma ajuda "
+#~ "na descoberta de erros."
+#~ msgid ""
+#~ "Find the parent file for the group of DocBook files. You will recognize "
+#~ "this file by the header <filename><!DOCTYPE article PUBLIC \"-//OASIS//"
+#~ "DTD DocBook V4.1//EN\"</filename>. An easy way to find this parent file "
+#~ "is to use the command <command>grep DocBook *.xml</command>. Once you "
+#~ "find the parent file, open it in Emacs with the command <command>emacs "
+#~ "<replaceable><parentfile></replaceable>.xml</command> (where "
+#~ "<replaceable><parentfile></replaceable>.xml is the parent file you "
+#~ "found."
+#~ msgstr ""
+#~ "Descubra o ficheiro-pai do grupo de ficheiros DocBook. Irá reconhecer "
+#~ "este ficheiro pelo cabeçalho <filename><!DOCTYPE article PUBLIC \"-//"
+#~ "OASIS//DTD DocBook V4.1//EN\"</filename>. Uma forma simples de descobrir "
+#~ "este ficheiro-pai é usar o comando <command>grep DocBook *.xml</command>. "
+#~ "Logo que descubra o ficheiro-pai, abra-o no Emacs com o comando "
+#~ "<command>emacs <replaceable><ficheiro-pai></replaceable>.xml</"
+#~ "command> (onde o <replaceable><ficheiro-pai></replaceable>.xml é o "
+#~ "ficheiro que descobriu."
+#~ msgid ""
+#~ "Choose <command>DTD -> Parse DTD</command> from the pulldown menu."
+#~ msgstr ""
+#~ "Escolha a opção <command>DTD -> Parse DTD</command> (Processar a DTD) "
+#~ "do menu respectivo."
+#~ msgid ""
+#~ "You will know the parsing is finished when you see the message "
+#~ "<computeroutput>Fontifying...done</computeroutput> at the bottom of your "
+#~ "screen. Save the parsed DTD to a file by choosing <command>DTD -> Save "
+#~ "Parsed DTD</command> from the pulldown menu."
+#~ msgstr ""
+#~ "Irá concluir se o processamento terminou quando lhe aparecer a mensagem "
+#~ "<computeroutput>Fontifying...done</computeroutput> (A formatar... pronto) "
+#~ "no fundo do seu ecrã. Grave a DTD processada num ficheiro com a opção "
+#~ "<command>DTD -> Save Parsed DTD</command> (DTD - Gravar a DTD "
+#~ "Processada) no menu."
+#~ msgid ""
+#~ "Press <keycap>Enter</keycap> to save the file to the default filename or "
+#~ "rename the file keeping the <filename>.ced</filename> extension. It can "
+#~ "be useful to name it something generic such as <filename>docbook.ced</"
+#~ "filename> so you can refer to it when opening all DocBook files. This "
+#~ "file can also be copied from directory to directory to be loaded."
+#~ msgstr ""
+#~ "Carregue em <keycap>Enter</keycap> para gravar o ficheiro com o nome "
+#~ "predefinido, ou mude o nome do ficheiro, mantendo a extensão <filename>."
+#~ "ced</filename>. Poderá ser útil atribuir-lhe um nome genérico, do tipo "
+#~ "<filename>docbook.ced</filename>, para que o possa consultar quando abrir "
+#~ "todos os ficheiros DocBook. Este ficheiro também poderá ser copiado de "
+#~ "uma pasta para a pasta onde será carregado."
+#~ msgid "To create a loadable Parsed DTD file: <placeholder-1/>"
+#~ msgstr ""
+#~ "Para criar o ficheiro de uma DTD processada e com possibilidade de "
+#~ "carregamento: <placeholder-1/>"
+#~ msgid ""
+#~ "You can also use the Emacs command <command>Meta-x sgml-parse-prolog</"
+#~ "command> to parse the file, and then use the command <command>Meta-x sgml-"
+#~ "save-dtd</command> to save the parsed DTD to a <filename>.ced</filename> "
+#~ "file."
+#~ msgstr ""
+#~ "Poderá também usar o comando do Emacs <command>Meta-x sgml-parse-prolog</"
+#~ "command> para processar o ficheiro, usando depois o comando <command>Meta-"
+#~ "x sgml-save-dtd</command> para gravar a DTD processada num ficheiro "
+#~ "<filename>.ced</filename>."
+#~ msgid "Load the Parsed DTD"
+#~ msgstr "Carregar a DTD Processada"
+#~ msgid ""
+#~ "Now that you have saved the DTD settings, you can load the <filename>."
+#~ "ced</filename> file and see the syntax highlighting for your <filename>."
+#~ "sgml</filename> files."
+#~ msgstr ""
+#~ "Agora que gravou a configuração da DTD, poderá carregar o ficheiro "
+#~ "<filename>.ced</filename> e ver o realce de sintaxe dos seus ficheiros "
+#~ "<filename>.sgml</filename>."
+#~ msgid "Open an XML file in Emacs."
+#~ msgstr "Abra um ficheiro em XML no Emacs."
+#~ msgid ""
+#~ "Choose <command>DTD -> Load DTD</command> from the pulldown menu and "
+#~ "choose the file you saved from the previous step. For instance, choose "
+#~ "<filename>docbook.ced</filename>."
+#~ msgstr ""
+#~ "Escolha a opção <command>DTD -> Load DTD</command> (DTD - Carregar a "
+#~ "DTD) do menu que aparece e escolher o ficheiro que gravou no passo "
+#~ "anterior. Por exemplo, escolha o <filename>docbook.ced</filename>."
+#~ msgid ""
+#~ "You will know it is finished when you see the message "
+#~ "<computeroutput>Fontifying...done</computeroutput> at the bottom of your "
+#~ "screen. Loading the parsed DTD might take a long time. You can start "
+#~ "editing the file before it finishes."
+#~ msgstr ""
+#~ "Irá saber quando terminou quando ver a mensagem "
+#~ "<computeroutput>Fontifying...done</computeroutput> (A formatar... pronto) "
+#~ "no fundo do seu ecrã. O carregamento da DTD processada poderá levar "
+#~ "bastante tempo. Poderá começar a editar o ficheiro antes de este terminar."
+#~ msgid "To load a parsed DTD file: <placeholder-1/>"
+#~ msgstr "Para carregar um ficheiro de DTD processado: <placeholder-1/>"
+#~ msgid ""
+#~ "You can also use the Emacs command <command>Meta-x sgml-load-dtd</"
+#~ "command> to load the parsed DTD."
+#~ msgstr ""
+#~ "Poderá também usar o comando do Emacs <command>Meta-x sgml-load-dtd</"
+#~ "command> para carregar a DTD processada."
+#~ msgid ""
+#~ "<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-save-dtd, "
+#~ "<placeholder-3/>"
+#~ msgstr ""
+#~ "<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-save-dtd, "
+#~ "<placeholder-3/>"
+#~ msgid "Save the Parse DTD"
+#~ msgstr "Gravar a DTD Processada"
+#~ msgid ""
+#~ "<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-load-dtd, "
+#~ "<placeholder-3/>"
+#~ msgstr ""
+#~ "<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-load-dtd, "
+#~ "<placeholder-3/>"
+#~ msgid "Load DTD"
+#~ msgstr "Carregar a DTD"
+#~ msgid ""
+#~ "<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+#~ "<keycombo><placeholder-3/><keycap/></keycombo>, <placeholder-4/>"
+#~ msgstr ""
+#~ "<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+#~ "<keycombo><placeholder-3/><keycap/></keycombo>, <placeholder-4/>"
+#~ msgid ""
+#~ "Try the following: Type <keycap>Ctrl</keycap>-<keycap>c</keycap> followed "
+#~ "by <keycap><</keycap>. Then enter the letter <keycap>k</keycap>, "
+#~ "followed by <keycap>Tab</keycap>. You may have to use the <keycap>Tab</"
+#~ "keycap> key several times to get a complete list."
+#~ msgstr ""
+#~ "Tente o seguinte: Escreva <keycap>Ctrl</keycap>-<keycap>C</keycap>, "
+#~ "seguida de <keycap><</keycap>. Depois, escreva a letra <keycap>k</"
+#~ "keycap>, seguida de <keycap>Tab</keycap>. Poderá ter de usar a tecla "
+#~ "<keycap>Tab</keycap> várias vezes, para obter uma lista completa."
+#~ msgid "The output should look similar to the example below:"
+#~ msgstr "O resultado deverá ficar semelhante ao exemplo abaixo:"
+#~ msgid ""
+#~ "\n"
+#~ "Click mouse-2 on a completion to select it.\n"
+#~ "In this buffer, type RET to select the completion near point.\n"
+#~ "\n"
+#~ "Possible completions are:\n"
+#~ "<keycap> <keycode>\n"
+#~ "<keycombo> <keysym>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Carregue em rato-2 sobre uma completação para a seleccionar.\n"
+#~ "Nesta área, carregue em RET para seleccionar a completação perto do "
+#~ "ponto.\n"
+#~ "\n"
+#~ "As completações possíveis são:\n"
+#~ "<keycap> <keycode>\n"
+#~ "<keycombo> <keysym>\n"
+#~ msgid ""
+#~ "<guilabel>The \"clear/quit\" command</guilabel>: I have found on some "
+#~ "occasions that I have gotten too far into the tag completion process and "
+#~ "need to just exit back out to my text. The easiest way to do this is the "
+#~ "keycombo <keycap>Ctrl</keycap>-<keycap>g</keycap>. This command quits "
+#~ "what you have been doing within the file, without quitting the file "
+#~ "itself."
+#~ msgstr ""
+#~ "<guilabel>O comando \"limpar/sair\"</guilabel>: Descobri em algumas "
+#~ "ocasiões que fui demasiado longe no processo de completação de marcas e "
+#~ "preciso de sair para voltar ao meu text. A forma mais simples de fazer "
+#~ "isto é a combinação de teclas <keycap>Ctrl</keycap>-<keycap>G</keycap>. "
+#~ "Este comando sai do que estiver a fazer com o ficheiro, sem sair do "
+#~ "ficheiro em si."
+#~ msgid "http://www.snee.com/bob/sgmlfree/emcspsgm.html"
+#~ msgstr "http://www.snee.com/bob/sgmlfree/emcspsgm.html"
+
+@
+
+
+1.24
+log
+ at updating pot and po files for noriko
+@
+text
+ at d3 1
+a3 1
+"Project-Id-Version: PACKAGE VERSION\n"
+d5 3
+a7 3
+"PO-Revision-Date: 2007-10-22 01:57+0100\n"
+"Last-Translator: FULL NAME <EMAIL@@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@@li.org>\n"
+d12 29
+a40 58
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu "
+"guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires "
+"VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend "
+"autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert "
+"articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap "
+"dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML "
+"tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man "
+"sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot "
+"developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro "
+"keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC "
+"configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG "
+"Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule "
+"Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote "
+"eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest "
+"Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text "
+"jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd "
+"colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES "
+"set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray "
+"ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG "
+"PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar "
+"Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse "
+"cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo "
+"imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject "
+"Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference "
+"rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef "
+"authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done "
+"Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered "
+"nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead "
+"Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas "
+"Redundâncias update yahoo VIMRUNTIME generated important \n"
+d54 2
+a85 1
+#, fuzzy
+d87 1
+a87 1
+msgstr "2003"
+d99 1
+a99 2
+msgstr ""
+"As linhas-mestras e procedimentos para produzir a documentação do Fedora"
+d103 1
+a103 1
+msgstr ""
+d107 1
+a107 1
+msgstr ""
+d111 1
+a111 1
+msgstr ""
+d115 1
+a115 2
+msgstr ""
+"Adição de indicações sobre o acesso Web ao CVS e à antevisão do trabalho"
+d127 1
+a127 1
+msgstr "Remover um capítulo desnecessário sobre as marcas de XML"
+d131 1
+a131 2
+msgstr ""
+"Correcções associadas para reflectir uma versão mais recente da realidade"
+d139 1
+a139 1
+msgstr ""
+d142 2
+a143 6
+#, fuzzy
+msgid ""
+"This chapter discusses how translations are provided in Fedora documentation."
+msgstr ""
+"Este capítulo oferece uma breve introdução à escritaq de documentação "
+"técnica."
+d147 1
+a147 1
+msgstr ""
+d150 2
+a151 7
+msgid ""
+"The cornerstone of translation when using XML files such as DocBook is the "
+"<firstterm>Portable Object</firstterm> or <acronym>PO</acronym> file. PO "
+"files provide a way for independent individuals or teams to translate "
+"documents. The Fedora Documentation Project toolchain includes rules for "
+"creating, updating, and maintaining these PO files."
+msgstr ""
+d155 1
+a155 1
+msgstr ""
+d158 2
+a159 4
+msgid ""
+"the <filename class=\"extension\">.pot</filename> file, or <firstterm>PO "
+"Template</firstterm> (<acronym>POT</acronym>)"
+msgstr ""
+d162 2
+a163 4
+msgid ""
+"the <filename class=\"extension\">.po</filename> file, or translation file "
+"(<acronym>PO</acronym>)"
+msgstr ""
+d166 2
+a167 7
+msgid ""
+"A POT is, as the name suggests, a blank template for new translations. It "
+"contains some header information and a list of strings based on the content "
+"of the original XML file from which it was created. Translators do not alter "
+"the POT. The POT should only be changed after changes are made to the "
+"original XML file from which it is derived."
+msgstr ""
+d170 2
+a171 8
+msgid ""
+"A translator who wishes to start working on a new language copies the POT to "
+"a locale-specific PO file. Then the translator uses any of a number of "
+"command-line or graphical tools to translate each of the strings in the "
+"list. A single POT is used to create many POs, one for each locale. These "
+"files are normally named for their locale code, such as <filename>de.po</"
+"filename>, <filename>it.po</filename>, and so on."
+msgstr ""
+a173 1
+#, fuzzy
+d175 1
+a175 1
+msgstr "Criar uma Lista Dentro de uma Tabela"
+d178 2
+a179 5
+msgid ""
+"The POT is named after the document from which it is derived. If document "
+"named in the <filename>Makefile</filename>) is <filename>foo-tutorial.xml</"
+"filename>, the POT is named <filename>foo-tutorial.pot</filename>."
+msgstr ""
+a181 1
+#, fuzzy
+d183 1
+a183 3
+msgstr ""
+"Para que o servidor Web seja iniciado sempre no arranque, execute o seguinte "
+"comando:"
+d186 2
+a187 4
+msgid ""
+"The same command is used to update the POT when the original XML sources "
+"change."
+msgstr ""
+d191 1
+a191 1
+msgstr ""
+d194 2
+a195 5
+msgid ""
+"Update the POT whenever the original XML changes. Many translators' tools "
+"automatically notify them of the change so they can update translations "
+"quickly."
+msgstr ""
+d199 1
+a199 1
+msgstr ""
+d202 2
+a203 6
+msgid ""
+"The translation files are created by the individual translators, and "
+"document maintainers do not normally need to create them. Translators update "
+"a list of locales in the <filename>po/LINGUAS</filename> file which defines "
+"all the locales for which translations exist."
+msgstr ""
+d206 2
+a207 6
+msgid ""
+"Whenever the source XML files are updated, the maintainer must at least "
+"update the POT. It is helpful, however, to also merge these changes with the "
+"existing translations for those translators who are not automatically "
+"notified of changes."
+msgstr ""
+d211 1
+a211 1
+msgstr ""
+d214 2
+a215 4
+msgid ""
+"Always make sure your local copy of PO is fresh, using the CVS \"update\" "
+"command:"
+msgstr ""
+d218 2
+a219 7
+#, fuzzy
+msgid ""
+"To merge new changes into the existing PO translations, use the following "
+"command:"
+msgstr ""
+"Para que o servidor Web seja iniciado sempre no arranque, execute o seguinte "
+"comando:"
+d223 1
+a223 1
+msgstr ""
+d227 1
+a227 1
+msgstr ""
+d230 2
+a231 4
+msgid ""
+"<firstterm>translated</firstterm>, meaning the string has been handled by a "
+"translator and its source has not changed since then"
+msgstr ""
+d234 2
+a235 4
+msgid ""
+"<firstterm>fuzzy</firstterm>, meaning the string has changed since it was "
+"last handled by a translator"
+msgstr ""
+d238 2
+a239 4
+msgid ""
+"<firstterm>untranslated</firstterm>, meaning no translation has yet been "
+"provided for this string, or it is brand new"
+msgstr ""
+d242 2
+a243 4
+msgid ""
+"To see a rough statistical tally of the string handling inside the PO for a "
+"module, use the following command:"
+msgstr ""
+d246 2
+a247 6
+msgid ""
+"For each locale in the list, a count is shown of translated, fuzzy, and "
+"untranslated strings in that order. Tallies that only provide two numerals "
+"are usually translated followed by untranslated. Tallies with only one "
+"numeral are usually fully translated."
+msgstr ""
+d250 2
+a251 4
+msgid ""
+"To see only a specific locale, append a dash and the locale code to the "
+"<command>postat</command> target:"
+msgstr ""
+d258 2
+a259 17
+msgid ""
+"This chapter shows how to publish official Fedora Documentation Project work "
+"to the <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem> website. To publish official documentation, you must be approved "
+"to write to the web repository in CVS. Access for publishing is limited to "
+"contributors who have demonstrated capacity for working with CVS and other "
+"project tools. Once you have acquired and are comfortable with these skills, "
+"contributions as a publisher are welcome."
+msgstr ""
+"Este capítulo mostra como publicar o trabalho no Projecto de Documentação do "
+"Fedora oficial para o servidor <systemitem class=\"fqdomainname\">docs."
+"fedoraproject.org</systemitem>. Para publicar a documentação oficial, deverá "
+"estar aprovado para escrever o repositório Web no CVS. O acesso de "
+"publicação está limitado aos contribuintes que tenham demonstrado capacidade "
+"para trabalhar com o CVS e as outras ferramentas do projecto. Logo que a "
+"tenha adquirido e esteja à vontade com esses conhecimentos, as contribuições "
+"como responsável de publicação são bem-vindas."
+d263 1
+a263 1
+msgstr "Como Funciona a Página"
+d266 2
+a267 15
+msgid ""
+"The <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> "
+"website is a set of PHP files and scripts. Publishers maintain these files "
+"in a CVS repository, and the website host retrieves them hourly to refresh "
+"the site. The host does not automatically use the newest content for the "
+"website. Instead, it pulls files with the CVS tag <systemitem>LIVE</"
+"systemitem> to populate the website."
+msgstr ""
+"A página Web do <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem> é um conjunto de ficheiros e programas em PHP. Os responsáveis "
+"de publicação mantêm estes ficheiros num repositório de CVS e a página Web "
+"transfere-os de hora a hora para actualizar a página. A máquina não usa "
+"automaticamente o conteúdo mais recente para a página Web. Em vez disso, "
+"transfere os ficheiros com a marca de CVS <systemitem>LIVE</systemitem> para "
+"preencher a página Web."
+d270 2
+a271 11
+msgid ""
+"Each publisher sets up a local testing website on an available Fedora "
+"system. This site, sometimes called a <firstterm>sandbox</firstterm>, allows "
+"the publisher to test and view changes to documents, and ensure stability on "
+"the public site."
+msgstr ""
+"Cada responsável de publicação configura uma página de testes num sistema "
+"Fedora disponível. Esta página do servidor, chamada normalmente de "
+"<firstterm>área segura</firstterm>, permite ao responsável testar e ver as "
+"alterações dos documentos, garantindo a estabilidade da página para o "
+"público."
+d275 1
+a275 1
+msgstr "Configurar uma Área Segura na Web"
+d278 2
+a279 6
+msgid ""
+"To test document publishing, first set up a web sandbox on a local Fedora "
+"system."
+msgstr ""
+"Para testar a publicação do documento, configure primeiro uma área segura na "
+"Web numa máquina local de Fedora."
+d300 2
+a301 6
+msgid ""
+"Change the permissions on this directory to make it easier to access for "
+"your normal user account."
+msgstr ""
+"Mude as permissões nesta pasta para facilitar o acesso para a sua conta "
+"normal de utilizador."
+d303 2
+a304 1
+#: en_US/publishing.xml:53(replaceable) en_US/publishing.xml:62(replaceable)
+d340 2
+a341 14
+msgid ""
+"You must have access to the <systemitem>cvsweb</systemitem> module through "
+"the Fedora Account System to check in changes. If you do not have access, "
+"you can use <userinput><![CDATA[:pserver:anonymous]]></userinput> in place "
+"of <userinput><![CDATA[:ext:username]]></userinput> above. Visit the Fedora "
+"Account System at <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> "
+"for more information."
+msgstr ""
+"Deverá ter acesso ao módulo <systemitem>cvsweb</systemitem> através do "
+"Sistema de Contas do Fedora para verificar e enviar as alterações. Se não "
+"tiver acesso, poderá usar o <userinput><![CDATA[:pserver:anonymous]]></"
+"userinput> em vez do <userinput><![CDATA[:ext:utilizador]]></userinput> "
+"indicado acima. Visite o Sistema de Contas do Fedora em <ulink url=\"http://"
+"admin.fedoraproject.org/accounts/\"/> para mais informações."
+d344 2
+a345 6
+msgid ""
+"Edit the <filename>/etc/hosts</filename> file and add the following line "
+"<emphasis>after</emphasis> all other lines:"
+msgstr ""
+"Edite o ficheiro <filename>/etc/hosts</filename> e adicione a seguinte linha "
+"<emphasis>depois</emphasis> de todas as outras linhas:"
+d353 2
+a354 6
+msgid ""
+"Create a file <filename>/etc/httpd/conf.d/fpo.conf</filename> with the "
+"following content:"
+msgstr ""
+"Crie um ficheiro <filename>/etc/httpd/conf.d/fpo.conf</filename> com o "
+"seguinte conteúdo:"
+d357 2
+a358 6
+msgid ""
+"Create a file <filename>/etc/php.d/fpo.ini</filename> with the following "
+"content:"
+msgstr ""
+"Crie um ficheiro <filename>/etc/php.d/fpo.ini</filename> com o seguinte "
+"conteúdo:"
+d376 1
+a376 3
+msgstr ""
+"Para que o servidor Web seja iniciado sempre no arranque, execute o seguinte "
+"comando:"
+d384 2
+a385 6
+msgid ""
+"To test the new sandbox site, open a Web browser and point it at the URL "
+"<uri>http://docs.localhost.localdomain</uri>."
+msgstr ""
+"Para testar a página da nova área segura, abra um navegador Web e aponte-o "
+"para o URL <uri>http://docs.localhost.localdomain</uri>."
+d396 2
+a397 6
+msgid ""
+"Follow these guidelines to ensure maintainability and ease of use for all "
+"publishers."
+msgstr ""
+"Siga estas recomendações para garantir a facilidade de uso e manutenção para "
+"todos os responsáveis de publicação."
+d400 2
+a401 10
+msgid ""
+"Use a short, descriptive name for the document directory. The module name "
+"from its Docs CVS location is usually appropriate. Good examples include "
+"<filename class=\"directory\">install-guide/</filename> or <filename class="
+"\"directory\">example-tutorial/</filename>."
+msgstr ""
+"Use um nome breve e descritivo para a pasta de documentos. O nome do módulo "
+"no seu local do CVS é normalmente apropriado. Os bons exemplos incluem o "
+"<filename class=\"directory\">install-guide/</filename> ou o <filename class="
+"\"directory\">example-tutorial/</filename>."
+d404 2
+a405 7
+msgid ""
+"Under the document directory, include a branch directory if the document "
+"references specific features of a particular Fedora release."
+msgstr ""
+"Sob a pasta do documento, inclua a pasta de uma ramificação, caso o "
+"documento faça referência a funcionalidades específicas de uma dada versão "
+"do Fedora."
+d408 2
+a409 10
+msgid ""
+"Under the branch directory (or document directory if no branches are "
+"necessary), make at least a <filename class=\"directory\">en_US/</filename> "
+"directory. Make an additional directory for each locale that has been fully "
+"translated."
+msgstr ""
+"Na pasta da ramificação (ou na pasta do documento se não existirem "
+"ramificações), crie pelo menos uma pasta <filename class=\"directory\">en_US/"
+"</filename>. Crie uma pasta adicional para cada código de país cuja "
+"documentação tenha sido completamente traduzida."
+d416 2
+a417 11
+msgid ""
+"To add content, follow the procedure below. The following commands show an "
+"example of adding content for a new document called the <citetitle>Foobar "
+"Tutorial</citetitle>. This document includes a translation for the \"zz_XX\" "
+"locale and follows specifics of each Fedora release."
+msgstr ""
+"Para adicionar conteúdos, siga o procedimento abaixo. Os comandos seguintes "
+"mostra um exemplo de adição de conteúdos para um documento novo chamado "
+"<citetitle>Tutorial XPTO</citetitle>. Este documento inclui uma tradução "
+"para o código de país \"zz_XX\" e segue as especificidades de cada versão do "
+"Fedora."
+d437 2
+a438 5
+msgid ""
+"Build the HTML version of each translation of the document from Docs CVS."
+msgstr ""
+"Crie a versão em HTML de cada tradução do documento a partir do CVS de "
+"documentação."
+d455 1
+a455 1
+msgstr "Copie o conteúdo em HTML para a área segura da Web."
+d469 2
+a470 6
+msgid ""
+"Convert the HTML in each directory to PHP using the provided "
+"<filename>docbookhtml2php.py</filename> script."
+msgstr ""
+"Converta o HTML em cada pasta para PHP, usando o programa "
+"<filename>docbookhtml2php.py</filename> que é fornecido."
+d473 2
+a474 17
+msgid ""
+"Create any necessary <filename>index.php</filename> files for the overall "
+"directories. Each document and branch directory must have an <filename>index."
+"php</filename> file directing users to appropriate content. In this example, "
+"the necessary files are <filename>foobar-tutorial/index.php</filename> and "
+"<filename>foobar-tutorial/f7/index.php</filename>. You do not need to write "
+"these files from scratch. Copy an existing file from another document, and "
+"change it as needed to suit the new document."
+msgstr ""
+"Crie os ficheiros <filename>index.php</filename> necessários para as pastas "
+"globais. Cada pasta de documento e ramificação deverá ter um ficheiro "
+"<filename>index.php</filename> que direcciona os utilizadores para o "
+"conteúdo apropriado. Neste exemplo, os ficheiros necessários são o "
+"<filename>tutorial-xpto/index.php</filename> e o <filename>tutorial-xpto/f7/"
+"index.php</filename>. Não precisa de escrever estes ficheiros do zero. Copie "
+"um ficheiro existente a partir de outro documento e mude-o da forma adequada "
+"para o novo documento."
+d477 2
+a478 6
+msgid ""
+"Depending on content, publication may include changing a higher-level "
+"<filename>index.php</filename> file."
+msgstr ""
+"Dependendo do contexto, a publicação poderá incluir a mudança de um ficheiro "
+"<filename>index.php</filename> de um nível superior."
+d481 2
+a482 6
+msgid ""
+"To test the changes in your sandbox, open a web browser and point it at "
+"<uri>http://docs.localhost.localdomain/</uri>."
+msgstr ""
+"Para testar as alterações na sua área segura, abra um navegador Web e aponte-"
+"o para <uri>http://docs.localhost.localdomain/</uri>."
+d489 2
+a490 6
+msgid ""
+"<emphasis>Do not proceed further until you test all changes.</emphasis> "
+"Check that all links and index pages work."
+msgstr ""
+"<emphasis>Não siga mais em frente até que teste todas as alterações.</"
+"emphasis> Verifique se todas as ligações e páginas de índice funcionam."
+d498 1
+a498 2
+msgstr ""
+"Para enviar o seu novo conteúdo para a página Web, siga este procedimento:"
+d536 2
+a537 6
+msgid ""
+"Commit the changes to CVS. Use a message that describes the document being "
+"committed."
+msgstr ""
+"Envie as alterações para o CVS. Use uma mensagem que descreva o conteúdo a "
+"ser enviado."
+d561 2
+a562 1
+#: en_US/vim.xml:16(primary) en_US/vim.xml:33(primary)
+d567 2
+a568 15
+msgid ""
+"VIM has many features to help you write XML content such as DocBook, "
+"including syntax highlighting and customizable key bindings. Additionally, "
+"one can easily use external programs from VIM for features such as spell-"
+"checking. This chapter assumes you already know generally how to use VIM; if "
+"you want to learn how, try the <command>vimtutor</command> or by typing "
+"<userinput>:help tutor</userinput> from inside VIM."
+msgstr ""
+"O VIM tem diversas funcionalidades que o ajudam a criar conteúdos em XML, "
+"como o DocBook, incluindo o realce de sintaxe e a atribuição de atalhos de "
+"teclado personalizados. Para além disso, poderá usar facilmente programas "
+"externos a partir do VIM para funcionalidades como a verificação "
+"ortográfica. Este capítulo assume que já tem algum conhecimento geral de "
+"utilização do VIM; se quiser aprender como, experimente o <command>vimtutor</"
+"command> ou escrevendo <userinput>:help tutor</userinput> dentro do VIM."
+d574 2
+a575 1
+#: en_US/vim.xml:34(secondary) en_US/emacs.xml:44(secondary)
+d581 1
+a581 3
+"Below is a short sample <filename>.vimrc</filename> file that turns on some "
+"VIM features useful for editing SGML or XML content such as DocBook: "
+"<screen>\n"
+d594 2
+a595 5
+"Segue-se um pequeno exemplo do ficheiro <filename>.vimrc</filename> que "
+"activa algumas das funcionalidades úteis do VIM para editar conteúdos em "
+"SGML ou XML, como o DocBook: <screen>\n"
+"<computeroutput>\" Desligar as opções de compatibilidade, como o 'desfazer' "
+"limitado\n"
+d608 2
+a609 15
+msgid ""
+"Some of these features require the <filename>vim-enhanced</filename> package "
+"to be installed. If you are using or the <filename>vim-minimal</filename> "
+"package, or if you are using an older version of VIM, you may not have the "
+"<filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still "
+"download <ulink url=\"http://vim.org/scripts/script.php?script_id=39"
+"\">matchit.zip from Vim.org</ulink> and load it separately."
+msgstr ""
+"Algumas destas funcionalidades necessitam de ter instalado o pacote "
+"<filename>vim-enhanced</filename>. Se estiver a usar o pacote <filename>vim-"
+"minimal</filename> ou se estiver a usar uma versão antiga do VIM, poderá não "
+"ter o ficheiro <filename>$VIMRUNTIME/macros/matchit.vim</filename>. Poderá à "
+"mesma transferir o <ulink url=\"http://vim.org/scripts/script.php?"
+"script_id=39\">ficheiro matchit.zip do Vim.org</ulink> e carregá-lo em "
+"separado."
+d617 2
+a618 8
+"VIM can speed up your DocBook creation by mapping frequently typed tags (or "
+"any words or phrases) onto short key combinations. By default, the keymap "
+"leader is the backslash (<literal>\\</literal>), but it can be redefined "
+"with a command like <userinput>let mapleader =\n"
+" \",\"</userinput>. There are two ways to use the following example; "
+"you can put it directly in your <filename>.vimrc</filename>, or you can save "
+"it in a separate file and load it with a <userinput>source</userinput> "
+"command in your <filename>.vimrc</filename>. <screen>\n"
+d641 1
+a641 2
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+d647 2
+a648 9
+"O VIM poderá acelerar a criação do seu DocBook, mapeando as teclas escritas "
+"com mais frequência (ou palavras ou frases) em combinações de teclas breves. "
+"Por omissão, o líder do mapa de teclados é a barra invertida (<literal>\\</"
+"literal>), mas poderá ser redefinida com um comando do tipo <userinput>let "
+"mapleader =\n"
+" \",\"</userinput>. Existem duas formas de usar o seguinte exemplo; "
+"podê-lo-á colocar direcamente no seu ficheiro <filename>.vimrc</filename> ou "
+"podê-lo-a gravar num ficheiro separado e fazendo referência com o comando "
+"<userinput>source</userinput> no seu <filename>.vimrc</filename>. <screen>\n"
+d668 1
+a668 2
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+d675 2
+a676 10
+msgid ""
+"Unfortunately, there is not currently a complete macro set for all DocBook "
+"commands, so you will need to define them yourself or customize the "
+"definitions in the examples from <xref linkend=\"sn-vim-additional-resources"
+"\"/>."
+msgstr ""
+"Infelizmente, não existe de momento um conjunto de macros completo para "
+"todos os comandos do DocBook, pelo que terá de os definir você mesmo ou "
+"personalizar as definições nos exemplos em <xref linkend=\"sn-vim-additional-"
+"resources\"/>."
+d687 2
+a688 8
+msgid ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to "
+"Vi Improved (VIM)</citetitle>"
+msgstr ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> Exemplo de sgml-vimrc</ulink> do <citetitle>Guia para "
+"principiantes do Vi Improved (VIM)</citetitle>"
+d691 2
+a692 6
+msgid ""
+"The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick "
+"Reference Card</ulink>"
+msgstr ""
+"O <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">Cartão de "
+"Referências Rápidas do VIM</ulink>"
+d699 2
+a700 10
+msgid ""
+"The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the "
+"<filename>vim-common</filename> package —<filename>/usr/share/vim/"
+"<replaceable><version></replaceable>/doc/intro.txt</filename> or type "
+"<userinput>:help intro</userinput> from within VIM"
+msgstr ""
+"O <citetitle>MANUAL DE REFERÊNCIA DO VIM</citetitle>, que vem com o pacote "
+"<filename>vim-common</filename> —<filename>/usr/share/vim/"
+"<replaceable><versão></replaceable>/doc/intro.txt</filename> ou "
+"escrevendo <userinput>:help intro</userinput> dentro do VIM"
+d707 2
+a708 11
+msgid ""
+"In this chapter, you will find an example of a very short tutorial as used "
+"by the Fedora Documentation Project. This example is specific to the way the "
+"Docs Project uses DocBook XML. The example consists of a set of files used "
+"to hold the content and metadata for the tutorial."
+msgstr ""
+"Neste capítulo, irá descobrir um exemplo de um tutorial bastante curto de "
+"documentação do Projecto Fedora. Este exemplo é específico para a forma como "
+"o Projecto de Documentação usa o DocBook em XML. O exemplo consiste num "
+"conjunto de ficheiros usados para manter o conteúdo, bem como meta-dados "
+"para o tutorial."
+d714 2
+a715 1
+#: en_US/tutorial.xml:21(primary) en_US/tutorial.xml:56(primary)
+d729 1
+a729 1
+msgstr "Os Meta-Dados"
+d733 1
+a733 1
+msgstr "meta-dados"
+d736 2
+a737 10
+msgid ""
+"The <filename>rpm-info.xml</filename> file contains all the required "
+"metadata for the document. This metadata includes title, authorship, "
+"licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates "
+"the content of this file:"
+msgstr ""
+"O ficheiro <filename>rpm-info.xml</filename> contém todos os meta-dados "
+"necessários para o documento. Estes meta-dados incluem o título, a autoria, "
+"a licença e o histórico de versões. O <xref linkend=\"ex-rpminfo\"/> ilustra "
+"o conteúdo deste ficheiro:"
+d744 2
+a745 11
+msgid ""
+"If you are not familiar with XML editing, copy and paste this file from an "
+"existing module and then edit the values for the various elements as "
+"appropriate. Consult Fedora Documentation Project members and help channels "
+"for more assistance if needed."
+msgstr ""
+"Se não estiver familiarizado com a edição em XML, copie e cole este ficheiro "
+"a partir de um módulo existente e edite depois os valores dos vários "
+"elementos, como for mais apropriado. Consulte os membros do Projecto de "
+"Documentação do Fedora e os canais de ajuda para maior assistência, se for "
+"necessário."
+d752 2
+a753 12
+msgid ""
+"Writing good technical documentation is not simply reproducing command lines "
+"and instruction sets. Good documentation is easy to read, understand, and "
+"translate, and presents a concise logical progression of concepts. Good "
+"documentation can also be defined by what it does <emphasis>not</emphasis> "
+"contain. Your tutorial should avoid:"
+msgstr ""
+"A escrita de boa documentação técnica não é simplemente reproduzir as linhas "
+"de comandos e os conjuntos de instruções. A boa documentação é fácil de ler, "
+"compreender e traduzir, oferecendo uma progressão lógica concisa dos "
+"conceitos. A boa documentação também poderá ser definida pelo que "
+"<emphasis>não</emphasis> contém. O seu tutorial deverá evitar:"
+d761 1
+a761 1
+msgstr "Uso de 'calão' técnico indefinido ou desnecessário"
+d776 2
+a777 13
+msgid ""
+"This chapter contains style rules and guidelines for writing Fedora "
+"documentation. Guidelines are not the same as rules. It is acceptable to "
+"violate a guideline when it makes your material easier to understand. Follow "
+"guidelines whenever possible, but follow rules at all times. Assume any "
+"advice is a guideline unless identified otherwise."
+msgstr ""
+"Este capítulo contém regras e instruções de estilo para escrever "
+"documentação para o Fedora. As instruções não são necessariamente regras. É "
+"aceitável voltar uma instrução, se esta tornar o seu material mais fácil de "
+"compreender. Siga as instruções se possível, mas siga sempre as regras. "
+"Assuma que qualquer conselho é uma instrução a menos que seja identificado "
+"em contrário."
+d781 1
+a781 1
+msgstr "Porque o Estilo é Importante"
+d784 2
+a785 11
+msgid ""
+"Writing well comes naturally to almost no one. It is a skill that "
+"professional writers, even famous ones, must practice constantly. "
+"<firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> "
+"is the quality that separates elegant writing from the merely functional."
+msgstr ""
+"A boa escrita não vem naturalmente para a maior parte das pessoas. É um dom "
+"que os escritores profissionais, até mesmo os famosos, precisam de praticar "
+"constantemente. O <firstterm>Estilo</firstterm><indexterm><primary>estilo</"
+"primary></indexterm> é a qualidade que separa a escrita elegante da "
+"meramente funcional."
+d788 2
+a789 10
+msgid ""
+"For example, refer to. <ulink url=\"http://www.online-literature.com/"
+"james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/"
+"ulysses/18/</ulink>. Please note that this example contains some mature "
+"themes and language, and is not suitable for all readers."
+msgstr ""
+"Por exemplo, veja em <ulink url=\"http://www.online-literature.com/"
+"james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/"
+"ulysses/18/</ulink>. Rpare por favor como este exemplo contém alguns temas e "
+"linguagem madura, mas não sendo adequado para todos os leitores."
+d792 2
+a793 20
+#, fuzzy
+msgid ""
+"Elegance comes in many forms. In prose and poetry, elegant writing may not "
+"follow some (or any) common rules of grammar, syntax, or spelling. A good "
+"example is Episode 18, \"Penelope,\" in James Joyce's novel "
+"<citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long "
+"streams of words without punctuation to simulate a character's internal "
+"consciousness. By violating basic rules of grammar and syntax, Joyce "
+"simulates the disorganized but loosely connected thought patterns of the "
+"narrator."
+msgstr ""
+"A elegância vem em diversas formas. Na prosa e na poesia, a escrita elegante "
+"poderá não seguir algumas (ou todas) as regras comuns da gramática, sintaxe "
+"ou ortografia. Um bom exemplo é o Episódio 18, \"Penélope,\" do romance de "
+"James Joyce <citetitle>Ulisses</citetitle><footnote id=\"fn-ulysses"
+"\"><placeholder-1/></footnote>. Aqui, Joyce usa grandes sequências de "
+"palavras sem pontuação, de modo a simular a consciência interna de uma "
+"personagem. Ao violar as regras básicas da sintaxe e da gramática, Joyce "
+"simula os padrões de pensamento desorganizados mas levemente ligados do "
+"narrador."
+d796 2
+a797 16
+msgid ""
+"Technical documentation, however, should always respect these rules. The "
+"more a document departs from standard language usage, the more difficult the "
+"material becomes for the reader. For example, readers may not be native "
+"speakers of the language used, or they might be reading a translation. If "
+"the writer uses slang, idioms, or jargon, a reader or translator may easily "
+"become confused. The following example compares two different written "
+"executions of the same idea:"
+msgstr ""
+"Contudo, a documentação técnica deverá sempre respeitar estas regras. Quanto "
+"mais um documento se desviar da utilização comum da língua, mais difícil se "
+"torna o material para o leitor. Por exemplo, os leitores poderão não usar a "
+"língua do documento como língua nativa ou poderão estar a ler uma tradução. "
+"Se o escritor usar 'calão', dialectos ou termos demasiado técnicos, o leitor "
+"ou o tradutor poderão ficar facilmente confusos. O exemplo seguinte compara "
+"duas execuções da mesma ideia, escritas de forma diferente:"
+d809 2
+a810 10
+msgid ""
+"So you made the changes I showed you in the last section. What's the next "
+"thing you should do? Just pop your thumb drive onto your system and read the "
+"<filename>messages</filename> log. When you see \"USB device found,\" then "
+"Bob's your uncle."
+msgstr ""
+"Portanto, já fez as alterações que lhe mostrei na última secção. Qual é a "
+"próxima coisa que deseja fazer? Basta colocar a sua caneta no seu sistema e "
+"ler o ficheiro de registo <filename>messages</filename>. Quando ver \"USB "
+"device found,\", então o João é o seu tio."
+d819 3
+a821 11
+"After you complete the configuration changes above, attach the USB removable "
+"media to your system. Use the <command>dmesg</command> command to examine "
+"the kernel message log. The message <computeroutput>USB device\n"
+"\t found</computeroutput> indicates that your device was installed "
+"successfully."
+msgstr ""
+"Depois de terminar as mudanças de configuração acima, ligue o dispositivo "
+"removível USB ao seu sistema. Use o comando <command>dmesg</command> para "
+"examinar o registo de mensagens do 'kernel'. A mensagem <computeroutput>USB "
+"device found</computeroutput> indica que o seu dispositivo foi instalado com "
+"sucesso."
+d824 2
+a825 10
+msgid ""
+"The first example is more conversational English, which is not appropriate "
+"for official written documentation. The second example is more formal, but "
+"as a result it is easier to comprehend, both for native readers and "
+"translators."
+msgstr ""
+"O primeiro exemplo é um Inglês mais coloquial, o qual não é apropriado para "
+"documentação oficial escrita. O segundo exemplo é mais formal, mas tem como "
+"resultado uma maior facilidade de compreensão, quer para os leitores nativos "
+"quer para os tradutores."
+d828 2
+a829 19
+msgid ""
+"Following style rules and guidelines also makes readers more comfortable "
+"with a set of documents. Consistent style enhances the professional "
+"appearance of documentation, and its perceived value. On the other hand, "
+"lapses in punctuation or poor grammar negatively affect a reader's reaction "
+"to written material. A reader can feel that an otherwise correct technical "
+"document is lacking in authority, simply because it is poorly written. "
+"Readers feel at ease when they do not have to struggle to understand an "
+"author's use of language."
+msgstr ""
+"Seguir as regras e instruções de estilo também deixa os leitores mais "
+"confortáveis com um determinado conjunto de documentos. Um estilo "
+"consistente melhor a aparência profissional da documentação, bem como o "
+"valor que é transmitido. Por outro lado, os lapsos de pontuação ou uma "
+"gramática incorrecta afectam de forma negativa a reacção de um leitor ao "
+"material escrito. Um leitor poderá sentir que um documento técnico não tem "
+"qualquer autoridade, simplesmente por estar mal escrito. Os leitores "
+"facilmente sentem que não têm de lidar com a compreensão da utilização da "
+"língua por parte de um autor."
+d832 2
+a833 11
+msgid ""
+"This chapter cannot possibly cover enough material to make every reader a "
+"good writer. Some manuals devoted entirely to writing style are themselves "
+"hundreds of pages long. This chapter provides enough guidelines for "
+"intermediate writers to understand style usage in technical documentation."
+msgstr ""
+"Este capítulo não poderá cobrir possivelmente material suficiente para que "
+"um leitor seja um bom escritor. Existem alguns manuais dedicados por inteiro "
+"ao estilo de escrita, tendo alguns deles centenas de páginas. Este capítulo "
+"contém instruções suficientes para os escritores médios compreenderem a "
+"utilização do estilo de documentação técnica."
+d836 2
+a837 8
+msgid ""
+"If you are not a practiced writer, whether of technical documentation or "
+"otherwise, you may benefit from other style resources. The following list is "
+"far from comprehensive, but provides a starting point:"
+msgstr ""
+"Se não for um escritor com prática, seja em documentação técnica ou noutra "
+"qualquer, poderá beneficiar de outros recursos de estilo. A lista que se "
+"segue não é excelente, mas oferece um bom ponto de partida:"
+d840 2
+a841 10
+msgid ""
+"<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules "
+"and links to online versions can be found at: <ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>"
+msgstr ""
+"<citetitle>The Elements of Style</citetitle>, de William Strunk. Poderá "
+"encontrar algumas regras básicas e referências para as versões 'online' em: "
+"<ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en."
+"wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+d844 2
+a845 8
+msgid ""
+"<citetitle>The Chicago Manual of Style</citetitle>, by the University of "
+"Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle."
+"org/\">http://www.chicagomanualofstyle.org/</ulink>"
+msgstr ""
+"<citetitle>The Chicago Manual of Style</citetitle>, da University of Chicago "
+"Press. Versão 'online': <ulink url=\"http://www.chicagomanualofstyle.org/"
+"\">http://www.chicagomanualofstyle.org/</ulink>"
+d848 2
+a849 8
+msgid ""
+"<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by "
+"Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/"
+"\">http://www.powa.org/</ulink>"
+msgstr ""
+"<citetitle>Paradigm Online Writing Assistant</citetitle>, mantido por Chuck "
+"Guilford, Ph.D. Apenas 'online': <ulink url=\"http://www.powa.org/\">http://"
+"www.powa.org/</ulink>"
+d852 2
+a853 15
+msgid ""
+"There are many free software documentation projects which have developed "
+"their own style guidelines. This chapter, in fact, draws heavily on the "
+"<citetitle>GNOME Documentation Style Guidelines</citetitle> "
+"(<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</"
+"citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/"
+"\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr ""
+"Existem diversos projectos de documentação de 'software' que desenvolveram "
+"as suas próprias recomendações de estilo. Este capítulo, de facto, baseia-se "
+"em grande medida nas <citetitle>Recomendações de Estilo de Documentação do "
+"GNOME</citetitle> (<firstterm>GDSG</firstterm>). Poderá ler a "
+"<citetitle>GDSG</citetitle> original em <ulink url=\"http://developer.gnome."
+"org/documents/style-guide/\">http://developer.gnome.org/documents/style-"
+"guide/</ulink>."
+d872 2
+a873 6
+msgid ""
+"This chapter provides a brief introduction to writing technical "
+"documentation."
+msgstr ""
+"Este capítulo oferece uma breve introdução à escritaq de documentação "
+"técnica."
+d880 2
+a881 8
+msgid ""
+"Technical writing for the Fedora Project imposes special constraints beyond "
+"the basic requirements of good prose. Good Fedora technical documentation "
+"has the following characteristics:"
+msgstr ""
+"A escrita técnica para o Projecto Fedora impõe restrições especiais para "
+"além dos requisitos básicos da boa prosa. Uma boa documentação técnica do "
+"Fedora tem as seguintes características:"
+d888 2
+a889 6
+msgid ""
+"Describe all of the functionality of a product. Do not omit functionality "
+"that you regard as irrelevant for the user."
+msgstr ""
+"Descreve todas as funcionalidades de um produto. Não omita funcionalidades "
+"que considere irrelevantes para o utilizador, do seu ponto de vista."
+d896 2
+a897 6
+msgid ""
+"Describe what you see. Do not describe what you want to see. Present your "
+"information in the order that users experience the subject matter."
+msgstr ""
+"Descreva o que vê. Não descreva o que deseja ver. Apresente a sua informação "
+"pela ordem em que os utilizadores deparam com o assunto."
+d901 1
+a901 1
+msgstr "Clara"
+d904 2
+a905 8
+msgid ""
+"Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>) to help make your writing clear."
+msgstr ""
+"Leia <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>) que o ajuda a tornar a sua escrita mais clara."
+d912 2
+a913 7
+msgid ""
+"Use agreed vocabulary throughout your documentation. Use the same vocabulary "
+"as other writers who are working on related documentation."
+msgstr ""
+"Use um vocabulário adequado ao longo da sua documentação. Use o mesmo "
+"vocabulário dos outros escritores que estão a trabalhar sobre documentos "
+"relacionados com este."
+d917 1
+a917 1
+msgstr "Concisa"
+d920 2
+a921 8
+msgid ""
+"Review your work frequently as you write your document. Ask yourself which "
+"words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for "
+"specific guidelines."
+msgstr ""
+"Reveja o seu trabalho com frequência, à medida que escreve o seu documento. "
+"Pergunte a si mesmo as palavras que poderá retirar. Veja algumas "
+"recomendações específicas em <xref linkend=\"sn-fundamentals-2\"/>."
+d928 2
+a929 7
+msgid ""
+"This section contains some basic style guidelines. Subsequent sections in "
+"this chapter expand on these guidelines to give more detailed guidance."
+msgstr ""
+"Esta secção contém algumas recomendações básicas de estilo. As secções "
+"seguintes deste capítulo expandem essas recomendações, para lhe dar "
+"conselhos mais detalhados."
+d948 2
+a949 8
+msgid ""
+"Under normal operating conditions, the kernel does not always immediately "
+"write file data to the disks, storing it in a memory buffer and then "
+"periodically writing to the disks to speed up operations."
+msgstr ""
+"Em condições normais de operação, o 'kernel' não grava sempre imediatamente "
+"os dados do ficheiros nos discos, guardando-os numa área em memória e "
+"escrevendo periodicamente para os discos, de modo a acelerar as operações."
+d956 2
+a957 6
+msgid ""
+"Normally, the kernel stores the data in memory prior to periodically writing "
+"the data to the disk."
+msgstr ""
+"Normalmente, o 'kernel' guarda os dados em memória antes de os gravar "
+"periodicamente no disco."
+d980 2
+a981 22
+msgid ""
+"The <application>Workspace Switcher</application> applet helps you navigate "
+"all of the virtual desktops available on your system. The X Window system, "
+"working in hand with a piece of software called a <emphasis>window manager</"
+"emphasis>, allows you to create more than one virtual desktop, known as "
+"<emphasis>workspaces</emphasis>, to organize your work, with different "
+"applications running in each workspace. The <application>Workspace Switcher</"
+"application> applet is a navigational tool to get around the various "
+"workspaces, providing a miniature road map in the GNOME panel showing all "
+"your workspaces and allowing you to switch easily between them."
+msgstr ""
+"A 'applet' do <application>Selector do Espaço de Trabalho</application> "
+"ajuda-o a navegar em todos os ecrãs virtuais do seu sistema. O sistema X "
+"Window, funcionando em conjunto com uma pequena componente aplicacional, "
+"chamada de <emphasis>gestor de janelas</emphasis>, permite-lhe criar mais de "
+"um ecrã virtual, também conhecido por <emphasis>espaço de trabalho</"
+"emphasis>, para organizar o seu trabalho, com diferentes aplicações a correr "
+"em cada espaço de trabalho. A 'applet' do <application>Selector do Espaço de "
+"Trabalho</application> é uma ferramenta de navegação para percorrer os "
+"diversos espaços de trabalho, oferecendo um roteiro em miniatura no painel "
+"do GNOME, mostrando todos os seus espaços de trabalho e permitindo uma "
+"mudança simples entre eles."
+d988 2
+a989 15
+msgid ""
+"Use the <application>Workspace Switcher</application> to add new "
+"<emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different "
+"applications in each workspace. The <application>Workspace Switcher</"
+"application> applet provides a miniature map that shows all of your "
+"workspaces. You can use the <application>Workspace Switcher</application> "
+"applet to switch between workspaces."
+msgstr ""
+"Use o <application>Selector de Espaços de Trabalho</application> para "
+"adicionar novos <emphasis>espaços de trabalho</emphasis> ao ambiente gráfico "
+"GNOME. Poderá executar diferentes aplicações em cada um dos espaços de "
+"trabalho. A 'applet' do <application>Selector de Espaços de Trabalho</"
+"application> oferece um mapa em miniatura que mostra todos os seus espaços "
+"de trabalho. Poderá usar a 'applet' do <application>Selector de Espaços de "
+"Trabalho</application>, de modo a mudar de espaços de trabalho."
+d992 2
+a993 6
+msgid ""
+"Plan the order of paragraphs before you start writing. Decide which topic "
+"you want to cover in each paragraph."
+msgstr ""
+"Planeie a ordem dos parágrafos antes de começar a escrever. Decida o tópico "
+"que deseja cobrir em cada parágrafo."
+d1000 2
+a1001 6
+msgid ""
+"Use explicit examples to demonstrate how an application works. Provide "
+"instructions rather than descriptions."
+msgstr ""
+"Use exemplos explícitos que demonstram como funciona uma aplicação. Forneça "
+"instruções em vez de descrições."
+d1008 2
+a1009 5
+msgid ""
+"There is a text box that you can use to find out the definition of a word."
+msgstr ""
+"Existe um campo de texto que poderá usar para descobrir a definição de uma "
+"palavra."
+d1016 2
+a1017 6
+msgid ""
+"To request a definition of a word, type the word in the text box, then "
+"select <guilabel>Lookup</guilabel>."
+msgstr ""
+"Para pedir a definição de uma palavra, escreva a palavra no campo de texto, "
+"seleccionando depois a opção <guilabel>Procurar</guilabel>."
+d1020 2
+a1021 6
+msgid ""
+"Do not apply this guideline too rigidly. Sometimes you must explain how "
+"software works to support your how-to examples."
+msgstr ""
+"Não aplique esta recomendação de forma muito rígida. Algumas vezes tem de "
+"explicar como funciona o 'software' para suportar os seus exemplos."
+d1037 1
+a1037 1
+msgstr "A 'applet' é um pequeno e útil módulo de captura do ecrã."
+d1045 1
+a1045 1
+msgstr "Use a 'applet' para fazer capturas do ecrã."
+d1052 2
+a1053 18
+msgid ""
+"Inappropriate tone hinders reader access to information. A neutral tone free "
+"of opinion or personal flavor improves the reader's comprehension. Neutral "
+"tone helps writers to work in parallel on a large technical documentation "
+"project. Furthermore, additional writers may join the project at any time. "
+"Use of a neutral tone helps to achieve consistency across a documentation "
+"set, and thereby facilitates user access to information. The best way to "
+"achieve a common, neutral tone is to apply the following principles:"
+msgstr ""
+"Um tom inapropriado retrai o acesso do utilizador à informação. Um tom "
+"neutro e livre de opiniões ou escolhas pessoais aumenta a compreensão por "
+"parte do leitor. Um tom netruo ajuda os escritores a trabalharem em paralelo "
+"num projecto de documentação técnica grande. Para além disso, poder-se-ão "
+"juntar escritores adicionais ao projecto em qualquer altura. A utilização de "
+"um tom netruo ajuda a obter alguma consistência em torno de um conjunto de "
+"documentos, facilitando deste modo o acesso dos utilizadores à informação. A "
+"melhor forma de obter um tom neutro e comum é aplicar os seguintes "
+"princípios:"
+d1060 2
+a1061 7
+msgid ""
+"Humor distracts from the information you are trying to provide. Humor also "
+"makes documentation difficult to translate. Stay factual."
+msgstr ""
+"O humor distrai o leitor da informação que você está a tentar transmitir. O "
+"humor também torna a documentação mais difícil de traduzir. Resuma-se a "
+"factos."
+d1068 2
+a1069 8
+msgid ""
+"Whether you think a function is useful or woeful is irrelevant. Report the "
+"function to the user, with instructions about how to use the function. Stay "
+"accurate."
+msgstr ""
+"Se acha que uma dada função é útil ou inútil é irrelevante. Relate a função "
+"para o utilizador, com instruções de utilização da mesma. Mantenha-se "
+"correcto."
+d1076 2
+a1077 6
+msgid ""
+"Colloquial language is difficult to translate and usually culture-specific. "
+"Stay neutral."
+msgstr ""
+"A linguagem coloquial é difícil de traduzir e normalmente é específica da "
+"caltura. Mantenha-se neutro."
+d1084 2
+a1085 6
+msgid ""
+"An expression that is in common use today might convey something completely "
+"different tomorrow. Stay technical."
+msgstr ""
+"Uma expressão que seja de uso comum nos dias de hoje poderá representar algo "
+"completamente diferente amanhã. Mantenha-se técnico."
+d1092 2
+a1093 7
+msgid ""
+"Statements about the future developments of a product do not belong in "
+"technical documentation. Write about what you see right now. Stay real."
+msgstr ""
+"As referências aos futuros desenvolvimentos de um produto não pertencem à "
+"documentação técnica. Escreva apenas sobre o que existe agora. Mantenha-se "
+"realista."
+d1100 2
+a1101 15
+msgid ""
+"All of the decisions that you make about the structure and content of a "
+"manual follow from an understanding of the audience. Consider how the "
+"audience accesses the documentation, what sort of information the audience "
+"needs, and the experience level of the audience. Usually, you need to create "
+"documentation that is suitable for different audiences. The following "
+"sections introduce some of the audience-related topics you need to consider."
+msgstr ""
+"Todas as decisões que fizer acerca da estrutura e conteúdo de um manual "
+"partem de uma compreensão por parte da audiência. Pense na forma como a "
+"audiência acede à documentação, ao tipo de informação que a audiência "
+"necessita e ao nível de experiência da audiência. Normalmente, é necessário "
+"criar uma documentação que seja adequada para diferentes audiências. As "
+"seguintes secções introduzem alguns dos tópicos relacionados com a audiência "
+"que necessita de ter em consideração."
+d1108 2
+a1109 10
+msgid ""
+"Do not waste the time of the user who looks for information in your "
+"documentation. Users do not read technical documentation for entertainment. "
+"Users usually have specific questions. You need to give clear answers to "
+"those questions."
+msgstr ""
+"Não ocupe o tempo do utilizador que procura informações na sua documentação. "
+"Os utilizadores não lêem documentação técnica por entretenimento. Os "
+"utilizadores normalmente têm questões específicas. Terá de dar respostas "
+"claras a essas questões."
+d1116 2
+a1117 19
+msgid ""
+"New users to Fedora are likely to consult online tutorials for guidance "
+"about unfamiliar applications or functionality. Each tutorial should contain "
+"enough introductory information to tell new users how to start using the "
+"relevant functions. Each tutorial should also contain enough usage "
+"instructions to tell users the different actions that they can perform with "
+"the command or function. Keep these instructions task-oriented. Do not "
+"describe GUI screens, dialogs, and dialog elements in a tutorial, unless "
+"there is an unusual feature that affects your instructions."
+msgstr ""
+"Os utilizadores novos no Fedora provavelmente irão consultar os tutoriais "
+"'onyline' para se orientarem nas aplicações ou funcionalidades pouco "
+"familiares. Cada tutorial deverá conter informação introdutória sufciente "
+"para indicar aos novos utilizadores como começar a usar as funções "
+"relevantes. Cada tutorial deverá também conter instruções de utilização "
+"suficientes para informar os utilizadores das diferentes acções que podem "
+"efectuar com o comando ou a função. Mantenha estas instruções orientadas às "
+"tarefas. Não descreva as janelas gráficas e os seus elementos num tutoria, a "
+"menos que exista alguma funcionalidade anormal que afecte as suas instruções."
+d1124 2
+a1125 8
+msgid ""
+"Experienced users are more likely to use documentation as a reference. The "
+"documentation therefore needs to be complete, well-organized, and in the "
+"case of printed manuals, well-indexed."
+msgstr ""
+"Os utilizadores experientes são mais aptos para usar a documentação como "
+"referência. A documentação aí tem de ser completa, bem organizada e, no caso "
+"dos manuais impressos, bem indexada."
+d1132 2
+a1133 6
+msgid ""
+"To avoid offending your readers, apply the following guidelines to your "
+"documentation:"
+msgstr ""
+"Para evitar ofender os seus leitores, aplique as seguintes recomendações à "
+"sua documentação:"
+d1140 2
+a1141 11
+msgid ""
+"Insider language includes both undefined jargon and the tendency of the "
+"computer community to shorten words. For example, use the term "
+"<literal>documentation</literal> instead of the term <literal>docs</"
+"literal>. A term may be jargon if it fails all the following conditions:"
+msgstr ""
+"A linguagem própria ou interna inclui algum calão indefinido e a tendência "
+"da comunidade informática de reduzir as palavras. Por exemplo, use o termo "
+"<literal>documentação</literal> em vez do termo <literal>docs</literal>. Um "
+"termo poderá ser considerado 'calão', se não respeitar qualquer uma das "
+"seguintes condições:"
+d1144 2
+a1145 8
+msgid ""
+"The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> "
+"(<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora."
+"redhat.com/docs/jargon-buster/</ulink>)."
+msgstr ""
+"O termo não aparece no <citetitle>Jargon Buster do Fedora</citetitle> "
+"(<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora."
+"redhat.com/docs/jargon-buster/</ulink>)."
+d1148 2
+a1149 8
+msgid ""
+"The term does not appear in the <citetitle>American Heritage Dictionary</"
+"citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby."
+"com/61/ </ulink>)."
+msgstr ""
+"O termo não aparece no <citetitle>American Heritage Dictionary</citetitle> "
+"(<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/ </"
+"ulink>)."
+d1152 1
+a1152 2
+msgid ""
+"The term does not appear in the glossary of the manual that you are writing."
+d1156 2
+a1157 4
+msgid ""
+"The term is not defined in the body text of the manual that you are writing."
+msgstr ""
+"O termo não está definido no texto do conteúdo do manual que está a escrever."
+d1164 2
+a1165 8
+msgid ""
+"Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</"
+"literal> do not exist. There is no need to identify gender in your "
+"instructions."
+msgstr ""
+"As construções de pronomes como o <literal>dele/dela</literal> ou "
+"<literal>ele/a</literal> não existem. Não existe a necessidade de reflectir "
+"o sexo da audiência na suas instruções."
+d1172 2
+a1173 6
+msgid ""
+"There is little point in giving an example that everyone in your town knows "
+"about, but is a complete mystery to everyone else in the world."
+msgstr ""
+"Não vale a pena dar um exemplo que seja conhecido em toda a sua cidade, mas "
+"que seja um completo mistério para o resto do mundo."
+d1180 2
+a1181 9
+msgid ""
+"There are few experiences more irritating for a user than documentation that "
+"says an action is easy or quick, when in fact the user cannot complete the "
+"action. Do not qualify or prejudge actions."
+msgstr ""
+"Existem poucas experiências mais irritantes para um utilizador que a "
+"documentação que diz que uma determinada acção é fácil ou rápida, quando o "
+"utilizador não consegue desempenhá-la de facto. Não qualifique ou faça "
+"juízos de valor das acções."
+d1184 2
+a1185 6
+msgid ""
+"Other parts of this guide discuss in more detail tone and language usage "
+"that can cause offense."
+msgstr ""
+"Outras partes deste guia descrevem com mais detalhe o tom e linguagem que "
+"possam ser considerados ofensivos."
+d1196 2
+a1197 9
+msgid ""
+"This section is drawn partly from the <citetitle>GDSG</citetitle>, and "
+"partly from <citetitle>The Elements of Style</citetitle>, updated as "
+"necessary for the needs of 21st-century technical documentation writers."
+msgstr ""
+"Esta secção é retirada em parte da <citetitle>GDSG</citetitle> e também em "
+"parte do documento <citetitle>The Elements of Style</citetitle>, actualizado "
+"de acordo com as necessidades dos escritores de documentação técnica do "
+"século XXI."
+d1202 2
+a1203 18
+msgid ""
+"This section contains an alphabetical list of grammar and usage guidelines "
+"for use in Fedora documentation. Many of these guidelines are only "
+"applicable to English-language usage, refer to the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of "
+"Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/"
+"cmosfaq.html</ulink>.)"
+msgstr ""
+"Esta secção contém uma lista alfabética das recomendações de gramática e "
+"utilização na documentação do Fedora. Muitas destas recomendações só se "
+"aplicam na utilização da língua Inglesa; para mais informações, consulte o "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) e o "
+"<citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www."
+"press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press."
+"uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+d1210 2
+a1211 10
+msgid ""
+"A shortened form of a word or phrase that takes the place of the full word "
+"or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, "
+"<literal>p.m.</literal>, and so on. Apply the following rules when you use "
+"abbreviations:"
+msgstr ""
+"Uma forma resumida de uma palavra ou frase que toma o lugar da palavra ou "
+"frase completa, como por exemplo <literal>Dr.</literal>, <literal>a.m.</"
+"literal>, <literal>p.m.</literal>, e assim por diante. Aplique as seguintes "
+"regras quando usar abreviaturas:"
+d1214 2
+a1215 6
+msgid ""
+"Avoid creating new abbreviations. Unfamiliar abbreviations can confuse "
+"rather than clarify a concept."
+msgstr ""
+"Evite a criação de novas abreviaturas. As abreviaturas pouco familiares "
+"poderão confundir mais um conceito que clarificar."
+d1226 2
+a1227 8
+msgid ""
+"For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other "
+"words\" and <literal>e.g.</literal> for \"for example\", do not use the "
+"abbreviation. Spell out the entire phrase."
+msgstr ""
+"Para as abreviaturas das frases, como o <literal>i.e.</literal> para \"isto é"
+"\" e o <literal>p.ex.</literal> como \"por exemplo\", não use a abreviatura. "
+"Descreva a frase por inteiro."
+d1234 2
+a1235 8
+msgid ""
+"Use adjectives with caution. If an adjective is necessary to differentiate "
+"between items, then use adjectives. In all cases, test whether the phrase "
+"can stand alone without the adjective."
+msgstr ""
+"Use os adjectivos com cuidado. Se um adjectivo for necessário para "
+"diferenciar itens, então use os adjectivos. Em qualquer um dos casos, este "
+"se a frase poderá ficar bem sem o adjectivo."
+d1242 2
+a1243 6
+msgid ""
+"A term that represents a multi-word term. Typically, acronyms are formed in "
+"the following ways:"
+msgstr ""
+"Um termo que representa um conjunto de palavras. Tipicamente, os acrónimos "
+"são formados da seguinte forma:"
+d1246 2
+a1247 6
+msgid ""
+"From the first letters of each word in a compound term, for example Table of "
+"Contents (TOC)."
+msgstr ""
+"Das primeiras letras de cada palavra num termo composto. Por exemplo, TOC "
+"significa 'Table of Contents' (Índice Analítico)."
+d1250 2
+a1251 6
+msgid ""
+"From recognizable parts of a compound term, such as GNU Object Model "
+"Environment (GNOME)."
+msgstr ""
+"A partir de partes reconhecíveis de um termo composto, como o GNU Object "
+"Model Environment (GNOME)."
+d1258 2
+a1259 6
+msgid ""
+"On the first occurrence of an acronym, spell out the full term, with the "
+"acronym in parentheses."
+msgstr ""
+"Na primeira ocorrência de um acrónimo, descreva por completo o termo "
+"completo, tendo o acrónimo entre parêntesis."
+d1262 2
+a1263 6
+msgid ""
+"Do not spell out the full compound for well-known acronyms, unless you think "
+"the information is useful for readers."
+msgstr ""
+"Não descreva extensivamente o termo completo para os acrónimos conhecidos, a "
+"menos que saiba que a informação é útil para os leitores."
+d1266 2
+a1267 6
+msgid ""
+"Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than "
+"clarify a concept."
+msgstr ""
+"Evite a criação de novos acrónimos. Os acrónimos não conhecidos poderão "
+"confundir mais um conceito que clarificá-lo."
+d1270 2
+a1271 6
+msgid ""
+"Write the acronym in uppercase letters, unless there is a compelling case "
+"for lowercase."
+msgstr ""
+"Escreva o acrónimo em maiúsculas, a não ser que haja um caso explícito para "
+"o uso de minúsculas."
+d1282 2
+a1283 12
+msgid ""
+"Use adverbs with caution. If an adverb is necessary to qualify the function "
+"of a component, then use an adverb. In all cases, test whether the phrase "
+"can stand alone without the adverb. Classic superfluous adverbs "
+"<literal>simply</literal>, <literal>easily</literal>, <literal>quickly</"
+"literal>."
+msgstr ""
+"Use os advérbios com cuidado. Se for necessário um advérbio para qualificar "
+"a função de um componente, então use um advérbio. Em qualquer dos casos, "
+"teste se a frase pode ser usada sem o advérbio. Alguns exemplos de advérbios "
+"supérfluos são o <literal>simplesmente</literal>, <literal>facilmente</"
+"literal>, <literal>rapidamente</literal>."
+d1294 2
+a1295 6
+msgid ""
+"Do not apply a sense of location or dimension to a software application. A "
+"user can not be \"in\" a text editor."
+msgstr ""
+"Não aplique um sentido de localização ou dimensão a uma aplicação "
+"informática. Um utilizador não pode estar \"dentro\" de um editor de texto."
+d1302 2
+a1303 6
+msgid ""
+"Do not use the definite article <literal>the</literal> to begin any of the "
+"following items:"
+msgstr ""
+"Não use o artigo definido <literal>the</literal> (o/a) para iniciar um dos "
+"seguintes itens (nota específica do Inglês):"
+d1313 2
+a1314 1
+#: en_US/style.xml:836(para) en_US/style.xml:1239(term)
+d1355 2
+a1356 5
+msgid ""
+"the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+msgstr ""
+"<guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> (opção Ajuda "
+"do Menu Principal)"
+d1371 2
+a1372 6
+msgid ""
+"the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</"
+"guimenu>"
+msgstr ""
+"the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</"
+"guimenu> (a opção Ajuda no Menu Principal)"
+d1387 2
+a1388 6
+msgid ""
+"Do not use brackets [such as these] as a substitute for parentheses (such as "
+"these)."
+msgstr ""
+"Não use parêntesis [deste tipo] como substituição dos parêntesis (deste "
+"tipo)."
+d1395 2
+a1396 9
+msgid ""
+"Do not use angle brackets to indicate variables in text, instead use the "
+"<sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref "
+"linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+msgstr ""
+"Não use os símbolos '<' e '>' para indicar as variáveis no texto; em "
+"vez disso, use a marca <sgmltag class=\"starttag\">replaceable</sgmltag>. "
+"Veja a utilização do <xref linkend=\"sn-xml-tags-replaceable\"/> para mais "
+"informações sobre a utilização desta marca."
+d1408 1
+a1408 3
+msgstr ""
+"Todas as letras dos acrónimos, a menos que o acrónimo seja uma excepção "
+"conhecida"
+d1420 1
+a1420 2
+msgstr ""
+"A letra inicial do nome de uma tecla, como a tecla <keycap>Shift</keycap>"
+d1431 2
+a1432 6
+msgid ""
+"Avoid starting a sentence with a command name or application name that has a "
+"lowercase initial letter."
+msgstr ""
+"Evite começar uma frase com o nome de um comando ou aplicação que tenha um "
+"nome que começa por minúsculas."
+d1463 2
+a1464 6
+msgid ""
+"Use the same rules as for headings, for all captions accompanying figures "
+"and tables. Do not put a period at the end of a caption."
+msgstr ""
+"Use as mesmas regras dos destaques para todas as legendas das tabelas e "
+"figuras. Não coloque um ponto no fim de uma legenda."
+d1550 2
+a1551 1
+#: en_US/style.xml:1143(term) en_US/emacs-nxml.xml:86(title)
+d1564 2
+a1565 6
+msgid ""
+"Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</"
+"emphasis>, or <emphasis>isn't</emphasis>."
+msgstr ""
+"Não use contracções do tipo <emphasis>tá</emphasis>, <emphasis>tar</"
+"emphasis>, or <emphasis>né</emphasis>."
+d1572 2
+a1573 9
+msgid ""
+"Do not use the em dash or the en dash. Use a paragraph break or a colon "
+"instead, where you want to create an introductory piece of text. If you have "
+"several items that you want to introduce, then you can use a variable list."
+msgstr ""
+"Não use o hífen 'mdash' ou 'ndash'. Use uma quebra de parágrafo ou os dois-"
+"pontos em alternativa onde pretender criar um pedaço introdutório de texto. "
+"Se tiver vários itens que deseja introduzir, então poderá usar uma lista "
+"variável."
+d1600 2
+a1601 6
+msgid ""
+"Use numerals for fractions in tables and in units of measurement, but spell "
+"out fractions in prose."
+msgstr ""
+"Use numerais para as fracções nas tabelas e nas unidades de medida, mas "
+"descreva por extenso as fracções."
+d1604 2
+a1605 6
+msgid ""
+"Use a space between a numeral and a related fraction, if there is a possible "
+"ambiguity. For example: 1 1/2 instead of 11/2."
+msgstr ""
+"Use um espaço entre um numeral e uma fracção relacionada, se puder existir "
+"alguma ambiguidadde. Por exemplo: 1 1/2 em vez de 11/2."
+d1608 2
+a1609 6
+msgid ""
+"If a fraction is used in a compound modifier, insert a hyphen between the "
+"fraction and the unit of measurement."
+msgstr ""
+"Se uma fracção for usada num modificador composto, indique um hífen entre a "
+"fracção e a unidade de medida."
+d1624 2
+a1625 10
+msgid ""
+"Use standard American English grammar rules, refer to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+"Use as regras-padrão do Inglês Americano (para documentos em Inglês); veja "
+"em <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www."
+"press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\"> http://www.press."
+"uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+d1637 1
+a1637 2
+msgstr ""
+"Letra maiúscula inicial para todos os substantivos, adjectivos e verbos."
+d1640 2
+a1641 6
+msgid ""
+"All lowercase letters for conjunctions, articles, and prepositions of fewer "
+"than four letters"
+msgstr ""
+"Todas as letras em minúsculas para as conjunções, artigos e proposições com "
+"menos de quatro letras"
+d1668 2
+a1669 8
+msgid ""
+"With some standard prefixes and suffixes. Use the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) for guidance"
+msgstr ""
+"Com alguns prefixos e sufixos padrão. Use o <citetitle>American Heritage "
+"Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://"
+"www.bartleby.com/61/</ulink>) para ter algumas linhas-guia"
+d1676 2
+a1677 7
+msgid ""
+"In variable names of two or more words, such as <replaceable>directory-name</"
+"replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+msgstr ""
+"Nos nomes de variáveis com duas ou mais palavras, como o <replaceable>nome-"
+"pasta</replaceable>. Nota: <replaceable>filename</replaceable> (nome de "
+"ficheiro) é uma excepção."
+d1700 2
+a1701 8
+msgid ""
+"With a word that is listed as unhyphenated in the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+msgstr ""
+"Com uma palavra que aparece como não-hifenizada no <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) e que use um prefixo comum"
+d1713 1
+a1713 2
+msgstr ""
+"Não use termos em Latim. Tente usar um termo em Inglês, em alternativa."
+d1720 2
+a1721 6
+msgid ""
+"Do not use the term <emphasis>like</emphasis> to denote equivalence or "
+"similarity."
+msgstr ""
+"Não use o <emphasis>do tipo</emphasis> para demarcar uma equivalência ou "
+"semelhança."
+d1729 1
+a1729 2
+msgstr ""
+"Introduza uma lista com uma frase completa que termine com dois-pontos."
+d1740 1
+a1740 2
+msgid ""
+"Numbers from zero through nine unless the number is part of a measurement"
+d1748 2
+a1749 6
+msgid ""
+"Extreme values such as <emphasis>million</emphasis>, but precede the value "
+"with a numeral"
+msgstr ""
+"Valores extremos como o <emphasis>milhão</emphasis>, se bem que pode "
+"anteceder o valor com um numeral"
+d1756 2
+a1757 6
+msgid ""
+"A number that is immediately followed by a numeral, for example: "
+"<literal>two 10 MB files</literal>"
+msgstr ""
+"Um número que seja seguido imediatamente de um numeral, como por exemplo: "
+"<literal>dois ficheiros de 10 MB</literal>"
+d1765 1
+a1765 3
+msgstr ""
+"Use os numerais (em oposição aos números por extenso) nas seguintes "
+"situações:"
+d1808 2
+a1809 6
+msgid ""
+"To contain the abbreviation of a term on the first occurrence of the full "
+"term"
+msgstr ""
+"Para conter a abreviatura de um termo na primeira ocorrência do termo "
+"completo"
+d1813 1
+a1813 2
+msgstr ""
+"Nas referências a páginas do 'man', especificamente no número da secção"
+d1833 1
+a1833 3
+msgstr ""
+"Nas abreviaturas que possam ser confundidas com palavras, como por exemplo C."
+"O.M., E.U."
+d1840 2
+a1841 12
+msgid ""
+"Use standard American English punctuation rules. In addition to the specific "
+"points of punctuation in this section, refer also to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+"Use as regras de pontuação normais do Inglês Americano. Para além dos sinais "
+"de pontuação específicos nesta secção, veja também no <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+d1848 2
+a1849 6
+msgid ""
+"Do not use a comma in numerals of four digits. Use a comma in numerals of "
+"more than four digits."
+msgstr ""
+"Não use um ponto nos numerais de quatro algarismos. Use o ponto nos numerais "
+"com mais de quatro algarismos."
+d1856 2
+a1857 10
+msgid ""
+"Use quotation marks to indicate material that is taken verbatim from another "
+"source. Do not use quotation marks to excuse terms from legitimacy. If the "
+"term is not legitimate, then use another term. If you must use that term, "
+"declare the term in the glossary and make the term legitimate."
+msgstr ""
+"Use as marcas de citação (plicas, aspas) para indicar o material que foi "
+"explicitamente retirado de outra fonte. Não use as aspas para retirar a "
+"legitimidade dos termos. Se o termo não for legítimo, então use outro termo. "
+"Se precisar de usar esse termo, declare-o no glossário e torne-o legítimo."
+d1864 2
+a1865 19
+msgid ""
+"When referring a user to another resource, use \"refer to\" instead of \"see"
+"\", and \"refer also to\" instead of \"see also\". This differentiates from "
+"the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag"
+"\">seealso</sgmltag> tags that are used in indexing. These tags create "
+"special links in the index. To be consistent throughout the document, we "
+"reserve the special words \"see\" and \"see also\" for hyperlinked index "
+"references, and use \"refer to\" and \"refer also to\" for non-hyperlinked "
+"and non-indexed references."
+msgstr ""
+"Ao referenciar um outro recurso, use o \"consulte\" em vez do \"veja\", ou "
+"então \"consulte também\" em vez de \"veja também\". Isto cria uma separação "
+"em relação às marcas <sgmltag class=\"starttag\">see</sgmltag> e <sgmltag "
+"class=\"starttag\">seealso</sgmltag>, as quais são usadas na indexação. "
+"Estas marcas criam referências especiais no índice. Para ser consistente ao "
+"longo do tempo, reservam-se as palavras especiais \"ver\" e \"ver também\" "
+"para o caso das referências com hiperligações, sendo que existe o \"consultar"
+"\" e o \"consultar também\" para o caso das referências não-ligadas e não-"
+"indexadas."
+d1880 2
+a1881 8
+msgid ""
+"Except where required as part of a filename, do not use slashes \"/\" in "
+"your writing. The construction <literal>and/or</literal>, for example, does "
+"not exist. Use one or the other term instead."
+msgstr ""
+"Excepto no caso de ser necessário como parte do nome de um ficheiro, não use "
+"as barras \"/\" na sua escrita. A construção <literal>e/ou</literal>, por "
+"exemplo, não existe. Use um termo ou o outro, em alternativa."
+d1888 2
+a1889 9
+msgid ""
+"Use standard American English spelling rules, refer to the "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+msgstr ""
+"Use as regras-padrão ortográficas do Inglês Americano; consulte o "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) para obter mais "
+"informações."
+d1908 2
+a1909 6
+msgid ""
+"Use standard abbreviations for units of measurements, do not invent your own "
+"abbreviations."
+msgstr ""
+"Use as abreviaturas-padrão para as unidades de medida, não invente as suas "
+"próprias."
+d1912 2
+a1913 6
+msgid ""
+"For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of "
+"Electrical and Electronics Terms</citetitle>."
+msgstr ""
+"Para mais informações, veja em <citetitle>IEEE Standard Dictionary of "
+"Electrical and Electronics Terms</citetitle>."
+d1917 1
+a1917 2
+msgstr ""
+"Use pontos nas unidades abreviadas que possam ser confundidas com palavras."
+d1920 2
+a1921 6
+msgid ""
+"Most standard abbreviations of units account for both singular and plural "
+"usage."
+msgstr ""
+"A maior parte das abreviaturas-padrão das unidades têm em conta a utilização "
+"singular e plural."
+d1937 2
+a1938 11
+msgid ""
+"This section contains usage tips based on situations the Fedora "
+"Documentation Project editors have encountered in the past. You should read "
+"and understand these examples to improve your own documentation. The Fedora "
+"Documentation Project editors welcome additional examples."
+msgstr ""
+"Esta secção contém sugestões de utilização que se baseiam nas situações que "
+"os editores do Projecto de Documentação do Fedora encontraram no passado. "
+"Deverá ler e compreender estes exemplos para melhorar a sua própria "
+"documentação. Os editores do Projecto de Documentação do Fedora agradecem os "
+"exemplos adicionais."
+d1945 2
+a1946 20
+msgid ""
+"Always use active voice, except when it is awkward to do so. The tutorial "
+"tells the user how to accomplish a task, and should give instructions "
+"clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. "
+"These words are redundant in a tutorial, since the reader assumes you are "
+"outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" "
+"\"might,\" and other words that indicate you are unsure about the subject "
+"matter. Your tutorial should cover a subject authoritatively. The reader "
+"should never be concerned about unknown effects of following the tutorial."
+msgstr ""
+"Use sempre a voz activa, excepto se ficar estranha a sua utilização num "
+"determinado contexto. O tutorial diz ao utilizador como desempenhar uma "
+"tarefa, devendo dar as instruções de forma clara e concisa. Evite usar os "
+"termos \"dever\", \"ser necessário\", entre outros. Estas palavras são "
+"redundantes num tutorial, dado que o leitor assume que você já está a "
+"destacar os passos necessários para efectuar uma tarefa. Evite também usar "
+"os termos \"talvez\", \"poderá\" e outras palavras que indiquem que não "
+"tenha a certeza sobre a matéria em estudo. O seu tutorial deverá cobrir um "
+"assunto de forma autoritária. O leitor nunca se deverá preocupar com os "
+"efeitos desconhecidos de seguir o tutorial."
+d1973 2
+a1974 13
+msgid ""
+"Write in the present tense. A good rule of thumb is that the words \"will\" "
+"and \"shall\" are almost never needed in describing what the user should do "
+"or see. They add unnecessary length to sentences and can confuse "
+"translators. They are also often indicators of passive voice; refer also to "
+"<xref linkend=\"sn-misc-active-voice\"/>."
+msgstr ""
+"Escreva no tempo presente. Uma boa regra de algibeira é que palavras como "
+"\"será\" ou \"deverá\" quase nunca são necessárias para descrever o que o "
+"utilizador deverá ou fazer. Estas adicionam um tamanho desnecessário às "
+"frases e poderão confundir os tradutores. Estas normalmente também são "
+"indicações de voz passiva; consule também o tópico <xref linkend=\"sn-misc-"
+"active-voice\"/>."
+d2001 2
+a2002 14
+msgid ""
+"Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself "
+"the writer (whether including the reader or not), the Fedora Documentation "
+"Project, the Fedora community, or any other group. Do not refer to users "
+"with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word "
+"\"one.\" It is acceptable to refer to the reader with the second person "
+"pronoun \"you.\""
+msgstr ""
+"Não use a primeira pessoa \"Eu,\" ou \"nós\" para se referir a si próprio "
+"como escritor (quer inclua o leitor quer não), o Projecto de Documentação do "
+"Fedora, a comunidade do Fedora ou qualquer outro grupo. Não faça referências "
+"aos utilizadores com um pronome na terceira pessoa (\"ele\", \"ela\" ou "
+"\"eles/elas\"). É aceitável fazer referências ao leitor na segunda pessoa "
+"com o pronome \"você\"."
+d2009 2
+a2010 6
+msgid ""
+"As described in the last section, I always run <command>up2date</command> "
+"before configuring the Samba server."
+msgstr ""
+"Como foi descrito na última secção, eu executo sempre o <command>up2date</"
+"command> antes de configurar o servidor do Samba."
+d2013 2
+a2014 6
+msgid ""
+"If the user needs to back up his or her files, s/he should use the "
+"<command>tar</command> or <command>cpio</command> command."
+msgstr ""
+"Se o utilizador precisar de salvaguardar os ficheiros dele ou dela, ele/a "
+"deverá usar o comando <command>tar</command> ou <command>cpio</command>."
+d2021 2
+a2022 6
+msgid ""
+"Refer to the section on <command>up2date</command> before configuring the "
+"Samba server."
+msgstr ""
+"Veja a secção sobre o <command>up2date</command> antes de configurar o "
+"servidor do Samba."
+d2025 2
+a2026 6
+msgid ""
+"If necessary, users can back up files with the <command>tar</command> or "
+"<command>cpio</command> command."
+msgstr ""
+"Se necessário, os utilizadores poderão salvaguardar os ficheiros com o "
+"comando <command>tar</command> ou <command>cpio</command>."
+d2033 2
+a2034 13
+msgid ""
+"Avoid negative words when possible, since they give documentation an overly "
+"dogmatic tone. The word \"avoid\" is useful for this purpose. Note that "
+"contractions are often used for negative words such as <emphasis>don't</"
+"emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-"
+"contractions\"/>."
+msgstr ""
+"Evite as palavras negativas sempre que possível, dado que atribuem à "
+"documentação um carácter dogmático, de certa forma. A palavra \"evitar\" é "
+"útil para esse fim. De um modo geral na língua inglesa, as contracções são "
+"usadas para as palavras negativas como o <emphasis>don't</emphasis> ou o "
+"<emphasis>can't</emphasis>. Consulte a secção <xref linkend=\"vle-"
+"contractions\"/>."
+d2041 2
+a2042 15
+msgid ""
+"Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the "
+"like. While occasional use of these constructions is acceptable, overuse "
+"reduces the authority of your documentation. The documentation should "
+"adequately cover a stock installation of Fedora. It is impossible for a "
+"tutorial-length document to cover every possible configuration scenario. "
+"Address the most common scenarios and note discrepancies only as required."
+msgstr ""
+"Evite o uso excessivo do \"tipicamente\", \"normalmente\", \"na maior parte"
+"\", \"muitos\", entre outros. Embora seja aceitável um uso ocasional destas "
+"conjugações, o uso em ecesso reduz a autoridade da sua documentação. A "
+"documentação deverá cobrir de forma adequada uma instalação predefinida do "
+"Fedora. É impossível, para um documento com a dimensão de um tutorial, "
+"cobrir todos os cenários de configuração possíveis. Analise os cenários mais "
+"comuns e aponte apenas as discrepâncias mais necessárias."
+d2049 2
+a2050 15
+msgid ""
+"Avoid covering redundant material, such as how to update a Fedora system. "
+"These overarching topics may be covered in other tutorials. Writers "
+"frequently violate this guideline because they feel their tutorial is not "
+"long enough. Keep your tutorial from wandering off-topic. Instead, refer the "
+"reader to a separate tutorial whenever possible for complete coverage of "
+"that topic."
+msgstr ""
+"Evite a cobertura de material redundante, como a actualização de um sistema "
+"Fedora. Estes tópicos mais complicados podem ser cobertos noutros tutoriais. "
+"Os escritores violam normalmente esta recomendação por acharem que o seu "
+"tutorial não é suficientemente comprido. Mantenha o seu tutorial com o "
+"tópico bem definido e sem grandes desvios. Em vez disso, indique ao leitor "
+"para consultar um tutorial sparado, sempre que possível, para uma cobertura "
+"completa desse tópico."
+d2057 2
+a2058 21
+msgid ""
+"Avoid statements such as \"One of the most important things to do is "
+"<replaceable>XYZ</replaceable>.\" If the procedure is important, the reader "
+"already expects it to be in your tutorial. The converse is also true: If a "
+"procedure appears in your tutorial, the reader expects it is important. This "
+"is especially true if you use a whole section for the procedure in question. "
+"Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as "
+"required. If the whole section concerns how to do <replaceable>XYZ</"
+"replaceable>, leave this sentence out entirely. Refer also to <xref linkend="
+"\"vle-golden-rule-4\"/>."
+msgstr ""
+"Evite frases do tipo \"Uma das coisas mais importantes a fazer é "
+"<replaceable>XYZ</replaceable>.\" Se o procedimento for importante, o leitor "
+"já está à espera dele no seu tutorial. O inverso também se aplica: se um "
+"procedimento aparece no seu tutorial, o leitor espera que este seja "
+"importante. Isto é particularmente verdadeiro se usar uma secção inteira "
+"para o procedimento em questão. Basta dizer, \"Faça <replaceable>XYZ</"
+"replaceable>.\". Depois disso, desenvolva de acordo com as necessidades. Se "
+"a secção completa disser respeito à forma como fazer <replaceable>XYZ</"
+"replaceable>, retire esta frase por inteiro. Consulte também a secção <xref "
+"linkend=\"vle-golden-rule-4\"/>."
+d2065 2
+a2066 7
+msgid ""
+"Use precise words for actions users should take. Do not instruct users to "
+"\"go\" to a selection, or \"find\" a menu."
+msgstr ""
+"Use palavras exactas para as acções que os utilizadores deverão efectuar. "
+"Não diga aos utilizadores para \"ir\" para uma selecção ou \"procurar\" um "
+"menu."
+d2073 2
+a2074 5
+msgid ""
+"Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+"Vá a <guimenu>Menu Principal</guimenu> -> <guimenuitem>XPTO</guimenuitem>"
+d2085 2
+a2086 6
+msgid ""
+"From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+"No <guimenu>Menu Principal</guimenu>, seleccione o <guimenuitem>XPTO</"
+"guimenuitem>"
+d2097 2
+a2098 9
+msgid ""
+"If you are writing about a GUI-only application, you may use \"click\" "
+"freely. If you are writing about an application that has a text-mode "
+"interface, use \"select\" instead as shown above."
+msgstr ""
+"Se estiver a escrever a escrever sobre uma aplicação somente gráfica, poderá "
+"usar o termo \"carregar\" ou \"clicar\" à vontade. Se estiver a escrever "
+"acerca de uma aplicação que também tem uma interface em modo texto, use o "
+"\"seleccionar\" como aparece acima."
+d2105 2
+a2106 6
+msgid ""
+"This section contains tips on how to use DocBook tags more effectively in "
+"your documentation."
+msgstr ""
+"Esta secção contém sugestões sobre a utilização mais eficiente da marcas de "
+"DocBook na sua documentação."
+d2108 2
+a2109 1
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:268(title)
+d2114 2
+a2115 12
+msgid ""
+"Avoid overuse of admonitions. Keep admonitions short and effective by using "
+"only the most important material inside the admonition. Move any background "
+"material required to explain the admonition statements outside the "
+"admonition. Use a short but descriptive title for an admonition. Use title "
+"case for the admonition title."
+msgstr ""
+"Evite o uso excessivo de advertências. Mantenha-as resumidas e efectivas, "
+"usando apenas o material mais importante dentro da advertência. Passe todo o "
+"material de segundo plano necessário para explicar as advertências para fora "
+"destas. Use um título breve mas descritivo para uma advertência. Use a "
+"capitalização no título da advertência."
+d2126 2
+a2127 15
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+"O comando <command>sfdisk</command> aceita um ficheiro de programa como "
+"dados de entrada para configurar as partições num disco rígido. Em alguns "
+"casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de "
+"entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, "
+"criando uma tabela de partições incorrecta no seu disco. Use sempre o "
+"comando <command>sfdisk -n</command> para verificar o seu ficheiro antes de "
+"efectuar gravações no disco."
+d2138 2
+a2139 6
+msgid ""
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+"Use sempre o comando <command>sfdisk -n</command> para verificar os seus "
+"dados de entrada, antes de gravar no disco."
+d2142 2
+a2143 14
+#, fuzzy
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"<placeholder-1/>"
+msgstr ""
+"O comando <command>sfdisk</command> aceita um ficheiro de programa como "
+"dados de entrada para configurar as partições num disco rígido. Em alguns "
+"casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de "
+"entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, "
+"criando uma tabela de partições incorrecta no seu disco."
+"<warning><placeholder-1/><placeholder-2/></warning>"
+d2146 2
+a2147 10
+msgid ""
+"Avoid punctuation in titles for sections or admonitions, except for commas "
+"only where demanded. Use a title that says something about the admonition "
+"comment, such as \"Reboot Required,\" instead of simply using the admonition "
+"type for a title (\"Note\")."
+msgstr ""
+"Evite a pontuação nos títulos das secções ou advertências, excepto as "
+"vírgulas e somente quando necessário. Use um título que diga algo sobre o "
+"comentário da advertência, como \"É Necessário Reiniciar,\" em vez de usar "
+"apenas o tipo de advertência como título (\"Nota\")."
+d2150 2
+a2151 4
+msgid ""
+"Follow the capitalization rules for headings in the title of an admonition."
+msgstr ""
+"Siga as regras de capitalização dos destaques no título de uma advertência."
+d2158 2
+a2159 8
+msgid ""
+"If your documentation formally states a specific value will be used as a "
+"convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> "
+"tag in your text or examples."
+msgstr ""
+"Se a sua documentação relatar formalmente que um determinado valor será "
+"usado como convenção, não use a marca <sgmltag class=\"starttag"
+"\">replaceable</sgmltag> no seu texto ou exemplos."
+d2166 2
+a2167 15
+#, fuzzy
+msgid ""
+"Use the entities provided by the Fedora Documentation Project. These "
+"entities are found in the <filename>common/</filename> folder in the "
+"<filename>fedora-docs</filename> distribution. (Refer also to <xref linkend="
+"\"ch-getting-files\"/>.) For instance, do not use abbreviations such as "
+"\"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" "
+"which produces the text \"Fedora 9.\""
+msgstr ""
+"Use as entidades oferecidas pelo Projecto de Documentação do Fedora. Estas "
+"entidades aparecem na pasta <filename>common/</filename> da distribuição "
+"<filename>fedora-docs</filename>. (Consulte também a secção <xref linkend="
+"\"ch-getting-files\"/>.) Por exemplo, não use abreviaturas do tipo \"FC2.\" "
+"Em vez disso, use as entidades predefinidas \"&FC; &FCVER;,\" que "
+"irá gerar o texto \"Fedora 8.\""
+d2193 2
+a2194 6
+msgid ""
+"Please read this chapter carefully. This chapter describes the guidelines "
+"that must be followed such as naming conventions."
+msgstr ""
+"Por favor, leia este capítulo com cuidado. O mesmo descreve as recomendações "
+"que deverão ser seguidas, como as nomenclaturas."
+d2197 2
+a2198 9
+msgid ""
+"This chapter only discusses tags used for documentation for the Fedora "
+"Project, not all available DocBook XML tags. For the complete list, refer to "
+"<ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr ""
+"Este capítulo só discute as marcas usadas na documentação do Projecto "
+"Fedora, não refere todas as marcas de XML do DocBook. Para uma lista "
+"completa, veja em <ulink url=\"http://www.docbook.org/tdg/en/html/docbook."
+"html\"/>."
+d2209 2
+a2210 8
+msgid ""
+"In accordance with good XML practices, the first line in any DocBook XML "
+"source files should identify the file as XML. Use the following line as the "
+"first line of any new XML file:"
+msgstr ""
+"De acordo com as boas práticas de XML, a primeira linha de qualquer ficheiro "
+"de DocBook em XML deverá identificar o ficheiro como XML. Use a seguinte "
+"linha como primeira linha de qualquer ficheiro em XML novo:"
+d2217 2
+a2218 6
+msgid ""
+"All the files must contain the CVS Id header. Use the following line as the "
+"second line of any new XML file:"
+msgstr ""
+"Todos os ficheiros deverão conter o cabeçalho Id do CVS. Use a seguinte "
+"linha como segunda linha para qualquer ficheiro em XML novo:"
+d2221 2
+a2222 6
+msgid ""
+"Any time the file is committed to CVS, the line is updated automatically to "
+"include information about the file. For example:"
+msgstr ""
+"Sempre que este ficheiro for enviado para o CVS, a linha é actualizada "
+"automaticamente para incluir informações acerca do ficheiro. Por exemplo:"
+d2255 2
+a2256 8
+msgid ""
+"This section explains the ID naming convention. IDs are unique identifiers "
+"that allow DocBook XML to cross-reference a section, chapter, or other "
+"element."
+msgstr ""
+"Esta secção explica a nomenclaturas de IDs. Os IDs são identificadores "
+"únicos que permitem ao DocBook em XML fazer referências a uma dada secção, "
+"capítulo ou outro elemento."
+d2272 2
+a2273 8
+msgid ""
+"Start the ID with the special short two-character label. This makes URLs and "
+"other references to this ID human readable, by self-identifying the XML "
+"container type."
+msgstr ""
+"Inicie o ID pela legenda especial de dois caracteres. Esta faz com que os "
+"URLs e as outras referências a este ID sejam legíveis, identificando "
+"autoamticamente o tipo do contentor de XML."
+d2276 2
+a2277 6
+msgid ""
+"<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used "
+"properly."
+msgstr ""
+"O <xref linkend=\"ex-id-usage\"/> demonstra alguns atributos de IDs usados "
+"correctamente como exemplos."
+d2361 2
+a2362 6
+msgid ""
+"Use the title of the item as the ID. Make your titles unique within a "
+"document to prevent conflicts. For example:"
+msgstr ""
+"Use o título do item como ID. Torne os seus títulos únicos dentro de um "
+"documento para evitar conflitos. Por exemplo:"
+d2377 2
+a2378 7
+msgid ""
+"It is very important that you remember the caveats in this section. These "
+"are learned suggestions or rules that make your XML experience better."
+msgstr ""
+"É muito importante que recorde as contrapartidas desta secção. Estas são "
+"sugestões ou regras de aprendizagem que tornam melhor a sua experiência em "
+"XML."
+d2385 2
+a2386 13
+msgid ""
+"Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+"\"genentity\">reg</sgmltag> because the do not produce HTML output that "
+"works for all charsets. The HTML output produces by these entities are "
+"declared in the DTD and cannot be changed via the stylesheet."
+msgstr ""
+"Não use as entidades de marcas registadas <sgmltag class=\"genentity"
+"\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag> ou <sgmltag "
+"class=\"genentity\">reg</sgmltag>, porque não produzem HTML válido que "
+"funcione em todas as codificações de caracteres. O resultado em HTML "
+"produzido por estas entidades está descrito na DTD e não pode ser alterado "
+"com a folha de estilo."
+d2389 2
+a2390 6
+msgid ""
+"Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes "
+"as follows:"
+msgstr ""
+"Em vez disso, use a marca <sgmltag>trademark</sgmltag> e as suas classes "
+"associadas, como se segue:"
+d2417 2
+a2418 8
+msgid ""
+"In general, use <sgmltag>para</sgmltag> tags around anything other than a "
+"simple paragraph. Doing so will create additional white space within the "
+"text itself in the PDF version."
+msgstr ""
+"De um modo geral, não use as marcas <sgmltag>para</sgmltag> em torno de tudo "
+"o que não seja um parágrafo simples. Ao fazê-lo, irá criar espaços em branco "
+"adicionais dentro do próprio texto, na versão em PDF."
+d2421 2
+a2422 8
+msgid ""
+"Specifically, do not use <sgmltag>para</sgmltag> tags around the following "
+"(or, to put this another way, do not embed the following within <sgmltag "
+"class=\"element\">para</sgmltag> elements):"
+msgstr ""
+"Especificamente, não use as marcas <sgmltag>para</sgmltag> em torno do "
+"seguinte (ou, posto de outra forma, não incorpore o seguinte dentro das "
+"marcas <sgmltag class=\"element\">para</sgmltag>):"
+d2441 2
+a2442 6
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag>listitem</sgmltag> tags"
+msgstr ""
+"Conteúdo dentro de elementos <sgmltag class=\"element\">para</sgmltag> "
+"residentes em marcas <sgmltag>listitem</sgmltag>"
+d2445 2
+a2446 11
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</"
+"emphasis> start immediately after the beginning <sgmltag class=\"starttag"
+"\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr ""
+"O conteúdo dentro das marcas <sgmltag class=\"element\">para</sgmltag> "
+"inseridas em marcas <sgmltag class=\"element\">listitem</sgmltag> "
+"<emphasis>deverá</emphasis> começar logo a seguir à marca inicial <sgmltag "
+"class=\"starttag\">para</sgmltag>, para evitar espaços em branco extra na "
+"versão em PDF."
+d2453 2
+a2454 11
+msgid ""
+"The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag"
+"\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis> be flush left in the XML file; otherwise, the "
+"extraneous whitespace will appear in the HTML version."
+msgstr ""
+"O conteúdo dentro das marcas <sgmltag>screen</sgmltag> (<sgmltag class="
+"\"starttag\">screen</sgmltag> e <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>deverão</emphasis> ser retirados à esquerda no ficheiro em XML; "
+"caso contrário, os espaços em branco estranhos irão aparecer na versão em "
+"HTML."
+d2496 2
+a2497 21
+msgid ""
+"There are five types of admonitions in DocBook: <sgmltag class=\"element"
+"\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, "
+"<sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</"
+"sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the "
+"admonitions have the same structure: an optional <sgmltag class=\"element"
+"\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD "
+"does not impose any specific semantics on the individual admonitions. For "
+"example, DocBook does not mandate that a <sgmltag class=\"element\">warning</"
+"sgmltag> is reserved for cases where bodily harm can result."
+msgstr ""
+"Existem cinco tipos de advertências no DocBook: <sgmltag class=\"element"
+"\">caution</sgmltag> (cuidado), <sgmltag class=\"element\">important</"
+"sgmltag> (importante), <sgmltag class=\"element\">note</sgmltag> (nota), "
+"<sgmltag class=\"element\">tip</sgmltag> (sugestão) e <sgmltag class="
+"\"element\">warning</sgmltag> (aviso). Todas as advertências têm a mesma "
+"estrutura: um <sgmltag class=\"element\">title</sgmltag> opcional, seguido "
+"dos elementos do nível dos parágrafos. A DTD do DocBook não impõe qualquer "
+"semântica específica das advertências individuais. Por exemplo, o DocBook "
+"não obriga que um <sgmltag class=\"element\">warning</sgmltag> esteja "
+"reservado para os casos em que possam resultar danos corporais."
+d2500 2
+a2501 10
+msgid ""
+"Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class="
+"\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, "
+"<sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element"
+"\">warning</sgmltag>"
+msgstr ""
+"Criar um <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element"
+"\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, <sgmltag "
+"class=\"element\">important</sgmltag> ou <sgmltag class=\"element\">warning</"
+"sgmltag>"
+d2504 2
+a2505 33
+msgid ""
+"There are several ways to bring attention to text within a document. A "
+"<emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to "
+"bring additional information to the users' attention. A <emphasis><sgmltag "
+"class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful "
+"information or another way to do something. A <emphasis><sgmltag class="
+"\"element\">caution</sgmltag></emphasis> is used to show the user they must "
+"be careful when attempting a certain step. An <emphasis><sgmltag class="
+"\"element\">important</sgmltag></emphasis> tag set can be used to show the "
+"user a piece of information that should not be overlooked. While this "
+"information may not change anything the user is doing, it should show the "
+"user that this piece of information could be vital. A <emphasis><sgmltag "
+"class=\"element\">warning</sgmltag></emphasis> is used to show the reader "
+"that their current setup will change or be altered, such as files being "
+"removed, and they should not choose this operation unless they are alright "
+"with the consequences."
+msgstr ""
+"Existem diversas formas de chamar a atenção ao texto dentro de um documento. "
+"Uma <emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> (nota) é "
+"usada para trazer informações para a atenção dos utilizadores. Uma "
+"<emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> (sugestão) é "
+"usada para mostrar ao utilizador alguma informação útil ou outra forma de "
+"fazer algo. Uma <emphasis><sgmltag class=\"element\">caution</sgmltag></"
+"emphasis> é usada para mostrar ao utilizador que deverá ter cuidado ao "
+"efectuar um determinado passo. Uma marca <emphasis><sgmltag class=\"element"
+"\">important</sgmltag></emphasis> pode ser usada para mostrar ao utilizador "
+"um pedaço de informação que não deva ser ignorado. Embora esta informação "
+"possa não alterar o que o utilizador irá fazer, deverá mostrar ao utilizador "
+"que esta informação poderá ser vital. Um <emphasis><sgmltag class=\"element"
+"\">warning</sgmltag></emphasis> é usado para mostrar ao leitor que a sua "
+"configuração actual irá mudar ou ser alterada, como a remoção de ficheiros, "
+"pelo que não deverão escolher esta operação, a menos que estejam de acordo "
+"com as consequências."
+d2508 2
+a2509 6
+msgid ""
+"The following lines of code show the basic setup for each case mentioned "
+"above, along with its appearance in HTML."
+msgstr ""
+"As seguintes linhas de código mostram a configuração básica de cada um dos "
+"casos indicados acima, em conjunto com a sua aparência em HTML."
+d2511 4
+a2514 2
+#: en_US/writing-guidelines.xml:403(title) en_US/emacs.xml:257(title)
+#: en_US/emacs.xml:562(title) en_US/emacs-nxml.xml:160(title)
+d2525 2
+a2526 1
+#: en_US/writing-guidelines.xml:413(title) en_US/emacs-nxml.xml:114(title)
+d2538 2
+a2539 1
+#: en_US/writing-guidelines.xml:433(title) en_US/emacs-nxml.xml:96(title)
+d2552 2
+a2553 1
+#: en_US/writing-guidelines.xml:459(see) en_US/writing-guidelines.xml:463(see)
+d2570 2
+a2571 16
+msgid ""
+"Screenshots are illustrations that show the state of a display the user may "
+"encounter. Screenshots can be either graphical or textual. However, "
+"screenshots use a great deal of space in a text document to convey "
+"relatively small amounts of information. The same space in the document can "
+"hold a greater amount of more descriptive and helpful information. "
+"Therefore, authors should avoid screenshots whenever possible in favor of "
+"descriptive text."
+msgstr ""
+"As imagens ou capturas de ecrã são ilustrações que apresentam o estado do "
+"ecrã que o utilizador poderá encontrar. As imagens poderão ser gráficas ou "
+"textuais. Contudo, as imagens usam bastante espaço num documento de texto "
+"para representar pedaços de informação relativamente pequenos. o mesmo "
+"espaço num documento poderá conter uma quantidade maior de informação mais "
+"descritiva e útil. Como tal, os autores deverão evitar as imagens sempre que "
+"possível, em detrimento de texto mais descritivo."
+d2574 2
+a2575 17
+msgid ""
+"One of the isolated instances in which screenshots are useful is to "
+"demonstrate a physical screen layout that is unfamiliar to a reader. "
+"<emphasis>This does not mean that illustrations of dialog boxes are good "
+"uses of screenshots.</emphasis> On the contrary, dialogs are simply "
+"instances of a user interface element with which a reader is already "
+"familiar. An annotated diagram in certain cases, however, explains to the "
+"reader where to find functional landmarks on the screen such as menu bars."
+msgstr ""
+"Uma das instâncias isoladas em que as imagens são úteis é para demonstrar a "
+"disposição física de um ecrã que não seja familiar para um leitor. "
+"<emphasis>Isto não significa que as ilustrações de janelas sejam bons usos "
+"para as imagens.</emphasis> Pelo contrário, as janelas são simplesmente "
+"instâncias de um elemento da interface com o qual o leitor já está "
+"familiarizado. Um diagrama anotado em certos casos, todavia, explica ao "
+"leitor onde encontrar certos blocos funcionais no ecrã, como as barras de "
+"menu."
+d2578 2
+a2579 6
+msgid ""
+"The steps for taking a graphical screenshot illustrate how using text to "
+"describe a procedure is more concise than a series of screenshots."
+msgstr ""
+"Os passos para tirar uma imagem gráfica ilustram como a utilização de texto "
+"para descrever um dado procedimento é mais conciso que uma série de imagens."
+d2586 2
+a2587 11
+msgid ""
+"Create a new user account to make screenshots. The new account uses the "
+"distribution default theme, fonts, and element sizes. The resulting "
+"screenshot has an appearance familiar to the largest number of readers, and "
+"makes Fedora Documentation Project documents consistent."
+msgstr ""
+"Crie uma nova conta de utilizador para criar as imagens. A conta nova usa o "
+"tema, tipos de letra e tamanhos dos elementos predefinidos da instalação. A "
+"imagem resultante tem uma aparência familiar ao maior número de leitores, e "
+"faz com que os documentos do Projecto de Documentação do Fedora sejam "
+"consistentes."
+d2590 2
+a2591 10
+msgid ""
+"Before taking the screenshot, if possible, resize the targeted GUI element"
+"(s) to the smallest possible size. The target image should be 500 pixels "
+"wide or less. If the screenshot includes more than one GUI element, you may "
+"need to resize the screenshot in a following step."
+msgstr ""
+"Antes de tirar a fotografia, tente dimensionar os elementos gráficos com o "
+"tamanho mais pequeno possível. O seu objectivo é uma imagem com 500 pixels "
+"ou menos ainda. Se estiver a tirar uma fotografia com mais de um elemento "
+"gráfico, terá de dimensionar a imagem num passo seguinte."
+d2594 2
+a2595 17
+msgid ""
+"To take the screenshot, select the GUI element with the mouse to bring it to "
+"the forefront, or otherwise arrange the elements. Press "
+"<keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to "
+"capture a single GUI window. For capturing the entire desktop use "
+"<keycap>Print Screen</keycap>. If the shot includes multiple elements "
+"grouped closely together, crop the resulting PNG format image in "
+"<application>The GIMP</application>."
+msgstr ""
+"Para tirar a imagem, seleccione o elemento gráfico com o seu rato, passando-"
+"o para primeiro plano, ou organizando os elementos. Carregue em "
+"<keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> para "
+"capturar uma única janela. Para capturar o ecrã completo, use o "
+"<keycap>Print Screen</keycap>. Se estiver a tirar uma fotografia de vários "
+"elementos e os tiver agrupado em conjunto, poderá recortar a imagem "
+"resultante no <application>The GIMP</application>. A imagem estará no "
+"formato PNG."
+d2598 2
+a2599 18
+msgid ""
+"If necessary, resize the image using <application>The GIMP</application>. "
+"Open the image, then right-click on it and choose "
+"<menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</"
+"guimenuitem></menuchoice>. With the chain symbol intact, set the "
+"<guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click "
+"<guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</"
+"guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the "
+"image before converting it."
+msgstr ""
+"Se precisar, poderá dimensionar a imagem com o <application>The GIMP</"
+"application>. Com a imagem aberta, carregue com o botão direito nesta e "
+"escolha a opção <menuchoice><guimenu>Imagem</guimenu><guimenuitem>Escalar a "
+"Imagem...</guimenuitem></menuchoice>. Com o símbolo da corrente intacto, "
+"configure a <guilabel>Nova Largura</guilabel> com o valor <guilabel>500 px</"
+"guilabel> e carregue em <guibutton>OK</guibutton>. Certifique-se que carrega "
+"em <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo> para gravar "
+"as suas alterações no seu PNG, antes da conversão para EPS."
+d2602 2
+a2603 15
+msgid ""
+"With the image open in <application>The GIMP</application>, right-click the "
+"image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As..."
+"</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, "
+"select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</"
+"guibutton>. Allow flattening of the image by clicking <guibutton>Export</"
+"guibutton>."
+msgstr ""
+"Com a imagem aberta no <application>The GIMP</application>, carregue com o "
+"botão direito na imagem e seleccione a opção <menuchoice><guimenu>Ficheiro</"
+"guimenu><guimenuitem>Gravar Como...</guimenuitem></menuchoice>. Em "
+"<guimenu>Determinar o Tipo de Ficheiro:</guimenu>, seleccione "
+"<guimenuitem>PostScript</guimenuitem>, carregando depois em <guibutton>OK</"
+"guibutton>. Active o alisamento da imagem com a opção <guibutton>Exportar</"
+"guibutton>."
+d2606 2
+a2607 8
+msgid ""
+"A <guilabel>Save as PostScript</guilabel> window appears. Select "
+"<guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</"
+"guibutton>."
+msgstr ""
+"Na janela para <guilabel>Gravar como PostScript</guilabel>, seleccione "
+"<guilabel>PostScript Encapsulado</guilabel> e carregue em <guibutton>OK</"
+"guibutton>."
+d2614 2
+a2615 6
+msgid ""
+"Textual screen information is also useful for readers. Follow these "
+"guidelines for textual screenshots:"
+msgstr ""
+"A informação textual do ecrã também é útil para os leitores. Siga estas "
+"recomendações para as imagens textuais:"
+d2618 2
+a2619 8
+msgid ""
+"If a graphical screenshot illustrates a function, and the textual mode has "
+"identical functions, do not include both, unless omitting either would make "
+"your description unclear."
+msgstr ""
+"Se usar uma imagem gráfica para ilustrar uma função e o modo textual tiver "
+"funções idênticas, não inclua ambas, a menos que a omissão de uma delas "
+"torne a sua descrição menos clara."
+d2622 2
+a2623 8
+msgid ""
+"Make the information generic over specific, and omit any username and "
+"machine information if possible. Do not include the shell prompt unless it "
+"is vital to the demonstration."
+msgstr ""
+"Opte por ter a sua informação genérica em vez de específica, omitindo a "
+"informação do utilizador e da máquina, se possível. Não inclua a linha de "
+"comandos, a menos que seja vital para a demonstração."
+d2630 2
+a2631 10
+msgid ""
+"When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a "
+"procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show "
+"what the user types, and use <sgmltag class=\"element\">computeroutput</"
+"sgmltag> tags to show the resulting output."
+msgstr ""
+"Ao usar o <sgmltag class=\"element\">screen</sgmltag> para demonstrar um "
+"procedimento, use as marcas <sgmltag class=\"element\">userinput</sgmltag> "
+"para mostrar o que o utilizador escreve, usando as marcas <sgmltag class="
+"\"element\">computeroutput</sgmltag> para mostrar o resultado."
+d2634 2
+a2635 6
+msgid ""
+"<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual "
+"screenshot usage."
+msgstr ""
+"O <xref linkend=\"ex-text-screenshot-good\"/> é um exemplo de utilização de "
+"uma imagem textual."
+d2642 2
+a2643 4
+msgid ""
+"To find all the currently active ssh sessions, execute the following command:"
+msgstr ""
+"Para descobrir todas as sessões de SSH activas, execute o seguinte comando:"
+d2672 2
+a2673 12
+msgid ""
+"The GNOME <application>Help</application> browser, also known as "
+"<command>yelp</command>, and the KDE <application>Khelp</application> "
+"documentation browser can render DocBook XML information as needed. Use "
+"these applications to preview your work if you prefer reading your work in a "
+"browser-like environment. Run the following command:"
+msgstr ""
+"O navegador de <application>Ajuda</application> do GNOME, também conhecido "
+"como <command>yelp</command> e o <application>Khelp</application> do KDE "
+"poderão representar a informação em XML do DocBook à medida das "
+"necessidades. Use estas aplicações para antever o seu trabalho, se o "
+"preferir ler num ambiente de um navegador. Execute assim o seguinte comando:"
+d2676 2
+a2677 8
+msgid ""
+"Make sure to point the preferred help browser at the top parent file of your "
+"XML document. Once the document loads, you can add a bookmark for it for "
+"ease of use later."
+msgstr ""
+"Certifique-se que aponta o navegador de ajuda preferido para o ficheiro-pai "
+"do seu documento em XML. Logo que o documento seja carregado, poderá "
+"adicionar um favorito para o mesmo para o poder usar mais tarde."
+d2684 2
+a2685 6
+msgid ""
+"Keeping your documents in the same place for every checkout session makes "
+"help browser bookmarks more effective."
+msgstr ""
+"Manter os seus documentos no mesmo local para cada sessão de recepção torna "
+"os favoritos do navegador de ajuda mais efectivos."
+d2688 2
+a2689 10
+msgid ""
+"Once you have a bookmark stored, it will appear in the help browser at every "
+"use. You can now hit <keycap>F1</keycap> during any GUI session to launch "
+"the help browser. Then choose your bookmark from the menu to preview your "
+"document at any time."
+msgstr ""
+"Logo que tenha guardado um favorito, este irá aparecer no navegador de ajuda "
+"sempre que o usar. Poderá agora carregar em <keycap>F1</keycap> durante "
+"qualquer sessão gráfica para lançar o navegador de ajuda. Depois, escolha o "
+"seu favorito do menu para antever o seu documento em qualquer altura."
+d2696 2
+a2697 13
+msgid ""
+"Documentation modules have a specific structure that enables the "
+"preconfigured tools to work correctly. Follow this structure exactly or you "
+"may have problems building your module. The Fedora Documentation Project "
+"build tools locate resources in the module and use them to build new output "
+"such as HTML or RPM packages."
+msgstr ""
+"Os módulos de documentação têm uma estrutura específica que activa as "
+"ferramentas pré-configuradas para funcionarem correctamente. Siga esta "
+"estrutura exacta ou então poderá vir a ter problemas com a compilação do seu "
+"módulo. As ferramentas de compilação do Projecto de Documentação do Fedora "
+"localizam os recursos no módulo e usam-nos para criar novos formatos de "
+"saída, como HTML ou pacotes RPM."
+d2704 2
+a2705 8
+msgid ""
+"<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example "
+"module, excluding any <filename class=\"directory\">CVS</filename> folders. "
+"Note that this example document does not have branches."
+msgstr ""
+"A secção <xref linkend=\"ex-module-structure\"/> mostra uma árvore de pastas "
+"de um módulo de exemplo, excluindo as pastas <filename class=\"directory"
+"\">CVS</filename>. Repare que este documento de exemplo não tem ramificações."
+d2731 2
+a2732 1
+#: en_US/module-struct.xml:53(seg) en_US/module-struct.xml:94(seg)
+d2747 2
+a2748 10
+msgid ""
+"Think of an XML entity as a predefined snippet of information. It can "
+"represent a chunk of XML source, or simply a word or character. If the "
+"information changes, it need be replaced only once, in the definition, to "
+"fix all usage."
+msgstr ""
+"Pense numa entidade de XML como um pedaço predefinido de informação. Poderá "
+"representar um bloco de código em XML, ou simplesmente uma palavra ou "
+"carácter. Se a informação se alterar, terá de ser substituída apenas uma vez "
+"na definição, de modo a corrigir todas as alterações."
+d2751 2
+a2752 14
+#, fuzzy
+msgid ""
+"This is the only directory absolutely required. It is named for the original "
+"language of the document, such as <placeholder-1/> (US English). The primary "
+"language does not have to be US English; all languages are supported. This "
+"directory contains all the XML source for the actual document, as well as "
+"XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr ""
+"Esta é a única pasta que é absolutamente necessária. Esta tem o nome da "
+"língua original do documento, como por exemplo <placeholder-1/> (Inglês dos "
+"EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas "
+"todas as línguas. Esta pasta contém todo o código em XML do documento "
+"actual, assim como o código em XML específico do documento para <placeholder-"
+"2/><footnote><placeholder-3/></footnote>."
+d2758 2
+a2759 1
+#: en_US/module-struct.xml:70(seg) en_US/module-struct.xml:80(seg)
+d2763 2
+a2764 1
+#: en_US/module-struct.xml:71(filename) en_US/module-struct.xml:75(filename)
+d2769 2
+a2770 10
+msgid ""
+"The <placeholder-1/> directory is an optional directory where graphics for "
+"the document should be stored. If graphics are screenshots that are "
+"particular to a language, the <placeholder-2/> directory can and should be "
+"stored in a language directory."
+msgstr ""
+"A pasta <placeholder-1/> é uma pasta opcional onde serão gravadas as imagens "
+"do documento. Se estas forem imagens particulares para uma determinada "
+"língua, a pasta <placeholder-2/> pode e deve ser gravada numa pasta de "
+"línguas."
+d2776 2
+a2777 1
+#: en_US/module-struct.xml:81(filename) en_US/module-struct.xml:87(filename)
+d2794 2
+a2795 17
+msgid ""
+"The <placeholder-1/> directory contains specially formatted Portable Object, "
+"or <placeholder-2/>, files created and used by translators. The Fedora "
+"Documentation Project build tools use these files to create translated "
+"versions of documents. The translated documents are not stored in CVS; they "
+"are created as needed from these PO files. The <placeholder-3/> directory "
+"also contains the <placeholder-4/> file, which lists the active translation "
+"<placeholder-5/>, or languages."
+msgstr ""
+"A pasta <placeholder-1/> contém os ficheiros 'Portable Object' ou "
+"<placeholder-2/> especialmente formatados, criados e usados pelos "
+"tradutores. As ferramentas de compilação do Projecto de Documentação do "
+"Fedora usam estes ficheiros para criar versões traduzidas dos documentos. Os "
+"documentos traduzidos não são guardados no CVS; são criados à medida das "
+"necessidades a partir destes ficheiros PO. A pasta <placeholder-3/> também "
+"contém o ficheiro <placeholder-4/>, que contém os <placeholder-5/> activos "
+"nas traduções ou línguas."
+d2797 2
+a2798 1
+#: en_US/module-struct.xml:93(seg) en_US/module-struct.xml:95(filename)
+d2803 2
+a2804 6
+msgid ""
+"The <placeholder-1/> controls the build process. Its content is discussed in "
+"<xref linkend=\"ex-makefile\"/>."
+msgstr ""
+"A <placeholder-1/> controla o processo de compilação. O seu conteúdo é "
+"discutido em <xref linkend=\"ex-makefile\"/>."
+d2806 2
+a2807 1
+#: en_US/module-struct.xml:100(filename) en_US/module-struct.xml:102(filename)
+d2813 1
+a2813 2
+msgstr ""
+"O ficheiro <placeholder-1/> contém os meta-dados específicos do documento"
+d2820 2
+a2821 11
+msgid ""
+"Never add the <systemitem>docs-common</systemitem> build tools directory to "
+"an individual module. Special formatting in the module list downloads these "
+"tools when a user checks out a document module. For more information, refer "
+"to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+msgstr ""
+"Nunca adicione a pasta de ferramentas de compilação <systemitem>docs-common</"
+"systemitem> a um módulo individual. A formatação especial na lista de "
+"módulos transfere estas ferramentas, sempre que um utilizador obtém um "
+"módulo de um documento. Para mais informações, consulte em <xref linkend="
+"\"ch-getting-files-naming-modules\"/>."
+d2828 2
+a2829 12
+msgid ""
+"In Linux and Fedora documentation, references to commands often include a "
+"number inside parentheses. This number represents the section of "
+"<firstterm>manpages</firstterm> that includes documentation for that "
+"command. To read the manpage for <command>make(1)</command>, use the command "
+"<command>man 1 make</command>."
+msgstr ""
+"No Linux e na documentação do Fedora, as referências aos comandos "
+"normalmente incluem um número entre parêntesis. Este número representa a "
+"secção das <firstterm>páginas de manual</firstterm> que incluem a "
+"documentação para esse comando. Para ler a página de manual para o "
+"<command>make(1)</command>, use o comando <command>man 1 make</command>."
+d2832 2
+a2833 14
+#, fuzzy
+msgid ""
+"The build system can render the document into another format such as "
+"<abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</"
+"command><placeholder-1/> and shell scripts. Authors need <emphasis>no</"
+"emphasis> prior experience with either shell scripts or a <command>make(1)</"
+"command>."
+msgstr ""
+"O sistema de compilação poderá representar o documento noutro formato, como "
+"o <abbrev>HTML</abbrev> ou o <abbrev>PDF</abbrev>, usando o <command>make(1)"
+"</command><footnote><placeholder-1/></footnote> e os programas da linha de "
+"comandos. Os autores <emphasis>não</emphasis> precisam de qualquer "
+"experiência anterior com os programas da linha de comandos ou o <command>make"
+"(1)</command>."
+d2840 2
+a2841 8
+msgid ""
+"Each individual document has its own <filename>Makefile</filename>, which "
+"only needs to be a few lines long. The document <filename>Makefile</"
+"filename> content is designed for cut and paste operations."
+msgstr ""
+"Cada documento individual tem a sua própria <filename>Makefile</filename>, "
+"que só necessita de ter algumas linhas. O conteúdo da <filename>Makefile</"
+"filename> do documento está desenhado para operações de corte e colagem."
+d2844 2
+a2845 7
+msgid ""
+"<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</"
+"filename> for a simple document with two files and two translations."
+msgstr ""
+"A <xref linkend=\"ex-makefile\"/> abaixo mostra a <filename>Makefile</"
+"filename> completa de um documento simples com dois ficheiros e duas "
+"traduções."
+d2852 2
+a2853 8
+msgid ""
+"Do not be concerned with some of the more complicated syntax such as the "
+"<command>XMLFILES_template</command> stanza. An explanation for this "
+"template appears a few paragraphs below."
+msgstr ""
+"Não se preocupe com alguma da sintaxe mais complicada, como o "
+"<command>XMLFILES_template</command>. Aparecerá em baixo uma explicação para "
+"este modelo."
+d2863 2
+a2864 1
+#: en_US/module-struct.xml:170(segtitle) en_US/module-struct.xml:240(segtitle)
+d2873 2
+a2874 6
+msgid ""
+"This variable contains the name for the main (parent) XML document. Follow "
+"convention by naming your document after the module name."
+msgstr ""
+"Esta variável contém o nome do documento-pai principal em XML. Siga a "
+"convenção, nomeando o seu documento com o nome do módulo."
+d2881 2
+a2882 6
+msgid ""
+"This variable contains the ISO code for the original version of the "
+"document, such as <placeholder-1/>."
+msgstr ""
+"Esta variável contém o código ISO da versão original do documento, como em "
+"<placeholder-1/>."
+d2889 2
+a2890 11
+msgid ""
+"This variable contains a listing of any files containing entity definitions. "
+"The Fedora Documentation Project uses a special XML format to record "
+"document-specific entities, so they can be translated and built on the fly "
+"like any other XML document. An example is shown later in this guide."
+msgstr ""
+"Esta variável contém uma listagem de todos os ficheiros que contêm "
+"definições de entidades. O Projecto de Documentação do Fedora usa um formato "
+"em XML especial para guardar as entidades específicas do documento, de modo "
+"que possam ser traduzidas e geradas na altura, como se fosse outro documento "
+"em XML qualquer. Aparecerá então um exemplo mais tarde neste guia."
+d2905 2
+a2906 15
+msgid ""
+"This template allows the build tools to work with the document in multiple "
+"languages once it is translated. The <placeholder-1/> marking is a variable "
+"used to substitute the appropriate language. This template is not terribly "
+"complicated. For a new module, duplicate this section exactly except for the "
+"actual filenames. Prepend the text <placeholder-2/>, in place of the "
+"language code directory name, to each filename in your document."
+msgstr ""
+"Este modelo permite às ferramentas de compilação funcionarem com o documento "
+"em várias línguas, logo que esteja traduzido. A marcação <placeholder-1/> é "
+"uma variável que é usada para substituir a língua apropriada. Este modelo "
+"não é terrivelmente complicado. Para um módulo novo, duplique esta secção "
+"exactamente, excepto os nomes dos ficheiros em si. Coloque antes o texto "
+"<placeholder-2/>, no lugar do nome da pasta do código da língua, para cada "
+"nome de ficheiro no seu documento."
+d2913 2
+a2914 7
+msgid ""
+"Do not include the document-specific entities XML file or the <filename>rpm-"
+"info.xml</filename> file, which will be discussed later in this guide."
+msgstr ""
+"Não inclua o ficheiro XML de entidades específicas do documento nem o "
+"ficheiro <filename>rpm-info.xml</filename>, os quais serão descritos "
+"posteriormente neste guia."
+d2917 2
+a2918 12
+msgid ""
+"The final section, beginning with <literal>define</literal>, locates the "
+"main <filename>Makefile.common</filename> for the build system. This "
+"<filename>Makefile.common</filename> file contains all the <application>make"
+"(1)</application> targets and rules to actually build the document and the "
+"various archives."
+msgstr ""
+"A secção final, que começa por <literal>define</literal>, localiza o "
+"ficheiro <filename>Makefile.common</filename> principal para o sistema de "
+"compilação. Este ficheiro <filename>Makefile.common</filename> contém todos "
+"os alvos e regras do <application>make(1)</application> para criar de facto "
+"o documento e os vários pacotes."
+d2925 2
+a2926 13
+msgid ""
+"Each document module's primary language directory contains a file called "
+"<filename>rpm-info.xml</filename>. This file contains document-specific "
+"metadata used to generate revision history, copyright, and contributor "
+"information. It follows a DTD specification included with the rest of the "
+"build system tools."
+msgstr ""
+"Cada pasta da língua primária do módulo do documento contém um ficheiro "
+"chamado filename>rpm-info.xml</filename>. Este ficheiro contém os meta-"
+"dados específicos do documento que são usados para gerir o histórico de "
+"revisões, direitos de cópia e a informação de contribuintes. Esta segue uma "
+"especificação em DTD que vem incluída com o resto das ferramentas do sistema "
+"de compilação."
+d2933 2
+a2934 6
+msgid ""
+"To render the <abbrev>XML</abbrev> document into another format, use one of "
+"the following <command>make</command> targets:"
+msgstr ""
+"Para representar o documento em <abbrev>XML</abbrev> noutro formato, use um "
+"dos seguintes alvos do <command>make</command>:"
+d2946 1
+a2946 1
+msgstr ""
+d2950 1
+a2950 1
+msgstr ""
+d2954 1
+a2954 1
+msgstr ""
+d2958 1
+a2958 1
+msgstr ""
+d2961 2
+a2962 6
+msgid ""
+"This target <placeholder-1/> the XML files to make sure they are not only "
+"well-formed, but follow the DTD. Some viewers of XML documents may not work "
+"correctly until you run this target. This target includes copying required "
+"entity files so that validating XML viewers work properly"
+msgstr ""
+d2968 4
+a2971 2
+#: en_US/module-struct.xml:257(abbrev) en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:293(abbrev) en_US/module-struct.xml:298(abbrev)
+d2990 2
+a2991 10
+msgid ""
+"This target builds the \"chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a separate directory named "
+"<placeholder-2/>. Each document section is a separate file within that "
+"directory."
+msgstr ""
+"Este alvo compila o documento <placeholder-1/> \"em blocos\" para cada "
+"tradução definida. O resultado é colocado numa pasta separada, chamada "
+"<placeholder-2/>. Cada secção do documento fica num ficheiro separado, "
+"dentro dessa pasta."
+d3002 2
+a3003 8
+msgid ""
+"This target builds the \"non-chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a single file: <placeholder-2/>; no "
+"other files are created."
+msgstr ""
+"Este alvo gera o documento <placeholder-1/> \"inteiro\" para cada tradução "
+"definida. O resultado é colocado num único ficheiro: <placeholder-2/>; não "
+"são criados outros ficheiros."
+d3009 4
+a3012 2
+#: en_US/module-struct.xml:277(abbrev) en_US/module-struct.xml:278(abbrev)
+#: en_US/module-struct.xml:294(abbrev) en_US/module-struct.xml:299(abbrev)
+d3017 2
+a3018 8
+msgid ""
+"This target builds only the <placeholder-1/> document for all document "
+"languages. <placeholder-2/> production is currently erratic and may not work "
+"for your document."
+msgstr ""
+"Este alvo constrói apenas o documento <placeholder-1/> para todas as línguas "
+"do documento. A produção em <placeholder-2/> tem alguns problemas e poderá "
+"não funcionar para o seu documento."
+d3029 2
+a3030 6
+msgid ""
+"This target builds only the <placeholder-1/> archive for all document "
+"languages."
+msgstr ""
+"Este alvo constrói apenas o pacote <placeholder-1/> para todas as línguas do "
+"documento."
+d3050 2
+a3051 6
+msgid ""
+"This target deletes any temporary, or generated files, but does <placeholder-"
+"1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr ""
+"Este alvo apaga todos os ficheiros temporários ou gerados, mas <placeholder-"
+"1/> apaga os ficheiros <placeholder-2/>, <placeholder-3/> ou pacotes."
+d3058 2
+a3059 6
+msgid ""
+"This target erases all <placeholder-1/>, <placeholder-2/>, and archive "
+"files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr ""
+"Este alvo apaga todos os ficheiros <placeholder-1/>, <placeholder-2/> e de "
+"pacotes. Este alvo também invoca automaticamente o alvo <placeholder-3/>."
+d3066 2
+a3067 6
+msgid ""
+"<abbrev>PDF</abbrev> production is currently erratic and may not work for "
+"your document."
+msgstr ""
+"A produção de <abbrev>PDF</abbrev> tem alguns problemas e poderá não "
+"funcionar para o seu documento."
+d3074 2
+a3075 12
+msgid ""
+"To add a new target and rules, place them at the bottom of the document "
+"<filename>Makefile</filename>, below the <literal>include</literal> line. "
+"Follow your target definitions with a double colon, not a single colon. The "
+"double colon allows you to specify additional rules for existing targets, or "
+"to write rules for a new target."
+msgstr ""
+"Para adicionar um novo alvo e regras, coloque-as no fundo da "
+"<filename>Makefile</filename> do documento, por baixo da linha "
+"<literal>include</literal>. Siga as definições do seu alvo com dois-pontos "
+"duplos, não apenas um. Os dois-pontos duplos permitem-lhe definir regras "
+"adicionais para os alvos existentes ou escrever regras para um novo alvo."
+d3078 2
+a3079 7
+msgid ""
+"For more information on using <command>make(1)</command>, consult the online "
+"documentation with the command <command>info make</command> in a terminal."
+msgstr ""
+"Para mais informações sobre a utilização do <command>make(1)</command>, "
+"consulte a documentação 'online' com o comando <command>info make</command> "
+"num terminal."
+d3086 2
+a3087 10
+msgid ""
+"Tutorial documents often make use of images such as <filename class="
+"\"extension\">.PNG</filename> files. Store image files in a <filename class="
+"\"directory\">figs/</filename> folder in the main module directory, as shown "
+"in <xref linkend=\"ex-module-structure\"/>."
+msgstr ""
+"Os documentos de tutoriais normalmente utilizam imagens como os ficheiros "
+"<filename class=\"extension\">.PNG</filename>. Guarde os ficheiros de "
+"imagens numa pasta <filename class=\"directory\">figs/</filename> da pasta "
+"do módulo principal, como aparece em <xref linkend=\"ex-module-structure\"/>."
+d3090 2
+a3091 20
+msgid ""
+"Depending on the output media, sometimes images may be scaled, streteched, "
+"or squashed. To minimize any distortions, we recommend that you use only "
+"<filename class=\"extension\">.PNG</filename> images. Avoid <filename class="
+"\"extension\">.JPG</filename> files. The <command>convert(1)</command> "
+"program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</"
+"abbrev> package, provides a convenient way to reformat <filename class="
+"\"extension\">.JPG</filename> images into <filename class=\"extension\">."
+"PNG</filename> format. For more information on formatting images such as "
+"screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr ""
+"Dependendo do formato de saída, algumas das imagens poderão ser esticadas, "
+"encolhidas ou desfeitas. Para minimizar as distorções, recomenda-se que use "
+"apenas as imagens <filename class=\"extension\">.PNG</filename>. Evite os "
+"ficheiros <filename class=\"extension\">.JPG</filename>. O programa "
+"<command>convert(1)</command>, do pacote <abbrev>RPM</abbrev> <package role="
+"\"rpm\">ImageMagick</package>, oferece uma forma conveniente de formatar de "
+"novo as <filename class=\"extension\">.JPG</filename> no formato <filename "
+"class=\"extension\">.PNG</filename>. Para mais informações sobre a "
+"formatação das imagens, veja em <xref linkend=\"sn-screenshots\"/>."
+d3094 2
+a3095 9
+msgid ""
+"Image files may be organized into subdirectories under <filename>figs/</"
+"filename> if necessary. The document building system recreates the image "
+"subdirectory structure in the output documents."
+msgstr ""
+"Os ficheiros de imagens poderão estar organizados em sub-pastas da "
+"<filename>figs/</filename>, se necessário. O sistema de compilação de "
+"documentos irá criar de novo a estrutura de sub-pastas das imagens nos "
+"documentos resultantes."
+d3098 2
+a3099 15
+msgid ""
+"Images often contain labels or other text which may need to be localized. A "
+"screenshot of a program, for example, may require a version for each "
+"translated language. Name language-dependent image files such as program "
+"screenshots by adding the language code to the filename, such as "
+"<filename>menu-en_US.png</filename>. Language-independent images, such as "
+"<filename>icon.png</filename>, do not need language codes."
+msgstr ""
+"As imagens contêm normalmente legendas ou outros textos que possam ter de "
+"ser traduzidos. Uma imagem de um programa, por exemplo, poderá necessitar de "
+"uma versão para cada língua traduzida. Dê um nome dependente da língua aos "
+"ficheiros de imagens, adicionando o código da língua ao nome do ficheiro, "
+"como acontece em <filename>menu-pt.png</filename>. As imagens independentes "
+"da língua, como o <filename>icon.png</filename>, não precisam de códigos de "
+"línguas."
+d3102 2
+a3103 14
+msgid ""
+"Sometimes, a document may require images that do not follow the naming "
+"convention. To use these images with the document building system, create an "
+"ordinary text file containing the image filenames. This file must be named "
+"<filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</"
+"systemitem> so the build system finds it when searching for image filenames."
+msgstr ""
+"Em alguns casos, um documento poderá necessitar de imagens que não sigam a "
+"nomenclatura. Para usar estas imagens com o sistema de compilação do "
+"documento, crie um ficheiro de texto normal que contém os nomes dos "
+"ficheiros de imagens. Este ficheiro dever-se-á chamar <filename>figs/"
+"Manifest-</filename><systemitem class=\"macro\">${LANG}</systemitem>, de "
+"modo que o sistema de compilação o descubra quando procurar pelos nomes dos "
+"ficheiros de imagens."
+d3106 2
+a3107 6
+msgid ""
+"<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one "
+"way to create this <filename>Manifest</filename> file."
+msgstr ""
+"O <xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstra uma "
+"forma de criar este ficheiro <filename>Manifest</filename>."
+d3118 2
+a3119 5
+msgid ""
+"To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr ""
+"Para adicionar um novo ficheiro de DocBook em XML a um documento existente, "
+"siga estes passos:"
+d3126 2
+a3127 12
+msgid ""
+"Edit the <filename>Makefile</filename> and add the filename to the "
+"<varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to "
+"the last existing line, and on the next line add an entry for the new file. "
+"Remember to add the <literal>${1}/</literal> prefix as a substitute for the "
+"language directory name."
+msgstr ""
+"Edite a <filename>Makefile</filename> e adicione o nome do ficheiro à "
+"listagem <varname>XMLFILES-${1}</varname>. Adicione uma <keycap>\\</keycap> "
+"à última linha existente e, na linha seguinte, adicione um item para o novo "
+"ficheiro. Lembre-se de adicionar o prefixo <literal>${1}/</literal> como "
+"substituto para o nome da pasta da língua."
+d3134 2
+a3135 11
+msgid ""
+"Translations are stored as PO (portable object) files, which the toolchain "
+"transforms into translated documents. Each PO file is based on the POT (PO "
+"template) for the document and translated by the Fedora Translation Project. "
+"To add a translation, follow these steps:"
+msgstr ""
+"As traduções são guardadas como ficheiros PO (portable object - objecto "
+"portável), que o conjunto de ferramentas irá transformar em documentos "
+"traduzidos. Cada um dos ficheiros PO baseia-se no POT (modelo de PO) do "
+"documento e é traduzido pelo Projecto de Traduções do Fedora. Para adicionar "
+"uma tradução, siga estes passos:"
+d3138 2
+a3139 6
+msgid ""
+"If the <filename class=\"directory\">po/</filename> directory does not "
+"exist, create it and add it to CVS:"
+msgstr ""
+"Se a pasta <filename class=\"directory\">po/</filename> não existir, crie-a "
+"e adicione-a ao CVS:"
+d3146 2
+a3147 6
+msgid ""
+"Add the new translation language to the <varname>OTHERS</varname> listing in "
+"the <filename>Makefile</filename>."
+msgstr ""
+"Adicione a nova língua da tradução à listagem do <varname>OTHERS</varname> "
+"na <filename>Makefile</filename>."
+d3150 2
+a3151 6
+msgid ""
+"Although translators often copy the POT manually to create the new PO file, "
+"the following command also works:"
+msgstr ""
+"Ainda que os tradutores copiem normalmente de forma manual o ficheiro POT "
+"para criar o novo ficheiro PO, o seguinte comando também funciona:"
+d3167 2
+a3168 8
+msgid ""
+"The goal of the Fedora Documentation Project is to create easy-to-follow, "
+"task-based documentation for Fedora users and developers. The Fedora "
+"Documentation Project uses the following tools:"
+msgstr ""
+"O objectivo do Projecto de Documentação do Fedora é criar documentação "
+"simples de usar, baseada em tarefas, para os utilizadores e programadores do "
+"Fedora. O Projecto de Documentação do Fedora usa as seguintes ferramentas:"
+d3176 1
+a3176 2
+msgstr ""
+"Folhas de estilo XSLT personalizadas para as versões impressas e em HTML"
+d3180 1
+a3180 3
+msgstr ""
+"Programas personalizados para gerar o resultado em HTML (use o "
+"<command>xmlto</command>)"
+d3187 2
+a3188 8
+msgid ""
+"This document explains the tools used by the Fedora Documentation Project. "
+"It provides writing and tagging guidelines to ensure Fedora documentation is "
+"consistent and easy-to-follow."
+msgstr ""
+"Este documento explica as ferramentas usadas pelo Projecto de Documentação "
+"do Fedora e oferece algumas recomendações de escrita e marcação que tornam a "
+"documentação do Fedora consistente e fácil de seguir."
+d3195 2
+a3196 7
+msgid ""
+"To work on official Fedora documentation you need to install the required "
+"tools. Follow the directions below to configure your system."
+msgstr ""
+"Para lidar com a documentação oficial do Fedora, terá de instalar as "
+"seguintes ferramentas. Siga as instruções abaixo para configurar o seu "
+"sistema."
+d3203 2
+a3204 7
+msgid ""
+"Install the \"Authoring and Publishing\" package group, which contains "
+"required DocBook XML files, stylesheets and scripts:"
+msgstr ""
+"Instale o grupo de pacotes \"Authoring and Publishing\" (Autoria e "
+"Publicações), que contém os ficheiros de DocBook em XML necessários, as "
+"folhas de estilo e os programas:"
+d3212 2
+a3213 6
+msgid ""
+"Next, install the <filename>cvs</filename> package, which is used to handle "
+"revision control on files in the official repository:"
+msgstr ""
+"De seguida, instale o pacote <filename>cvs</filename>, que é usado para "
+"lidar com o controlo de versões nos ficheiros do repositório oficial:"
+d3221 2
+a3222 9
+msgid ""
+"If you plan to use <application>Emacs</application> to edit DocBook XML "
+"documentation, install <package>psgml</package>, which adds helpful and time-"
+"saving functionality to maximize editing efficiency:"
+msgstr ""
+"Se pensar em usar o <application>Emacs</application> para editar a "
+"documentação DocBook em XML, instale o pacote <package>psgml</package>, que "
+"adiciona funcionalidades úteis e de poupança de tempo, de modo a maximizar a "
+"eficiência na edição:"
+d3234 2
+a3235 15
+msgid ""
+"The Fedora Documentation Project's custom scripts and stylesheets are stored "
+"in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</"
+"systemitem> CVS server. When you check out a document module from CVS, the "
+"tools are included in the module inside the <filename class=\"directory"
+"\">docs-common/</filename> directory. To work on existing documents in CVS, "
+"refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+"Os programas e folhas de estilo personalizados do Projecto de Documentação "
+"do Fedora estão guardados em CVS, no servidor <systemitem class="
+"\"fqdomainname\">cvs.fedoraproject.org</systemitem>. Quando transfere um "
+"módulo de documentos do CVS, s ferramentas vão incluídas no módulo, dentro "
+"da pasta <filename class=\"directory\">docs-common/</filename>. Para "
+"trabalhar sobre documentos existentes no CVS, consulte a secção <xref "
+"linkend=\"ch-cvs\"/>."
+d3238 2
+a3239 14
+msgid ""
+"The most powerful component in the Fedora Documentation Project toolbox is "
+"<firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for "
+"authoring technical documentation using <firstterm>Extensible Markup "
+"Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark "
+"pieces of content with descriptive tags. The following output is an example "
+"of DocBook XML:"
+msgstr ""
+"O componente mais poderoso no pacote de ferramentas do Projecto de "
+"Documentação do Fedora é o <firstterm>DocBook XML</firstterm>. O DocBook XML "
+"é um esquema específico para gerar documentação técnica, usando a "
+"<firstterm>Extensible Markup Language</firstterm> ou <acronym>XML</acronym>. "
+"O XML permite aos autores marcarem certas partes de conteúdo com marcas "
+"descritivas. Segue-se um exemplo de DocBook XML:"
+d3242 2
+a3243 17
+msgid ""
+"This example article, entitled <citetitle>A Very Short Article</citetitle>, "
+"consists of only a single paragraph. The tags, or markup, surround elements "
+"of content to define the sense in which they are used. A paragraph, for "
+"example, is marked with <sgmltag>para</sgmltag> tags. Text that requires "
+"emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does "
+"not worry about the visual formatting such as italics or font size. Fedora "
+"Documentation Project build tools automatically perform all formatting tasks."
+msgstr ""
+"Este artigo de exemplo, chamado <citetitle>Um Artigo Muito Curto</"
+"citetitle>, consiste apenas num único parágrafo. As marcas de formatação "
+"reúnem os elementos de conteúdo para definirem o sentido em que são usadas. "
+"Um parágrafo, por exemplo, é rodeado com marcas <sgmltag>para</sgmltag>. O "
+"texto que necessite de ênfase está marcado com <sgmltag>emphasis</sgmltag>. "
+"O autor não se irá preocupar com a formatação visual, como os itálicos ou o "
+"tamanho da letra. As ferramentas de compilação do Projecto de Documentação "
+"do Fedora efectuam todas as tarefas de formatação."
+d3246 2
+a3247 14
+msgid ""
+"The custom tools built by the Fedora Documentation Project render DocBook "
+"source into a variety of formats for publication and distribution. They also "
+"allow translators to create localized versions of the XML documents for "
+"Fedora users around the world. The flexibility of XML allows for a single "
+"document to be used many times for many purposes, like reusable code for a "
+"programmer."
+msgstr ""
+"As ferramentas personalizadas, criadas pelo Projecto de Documentação do "
+"Fedora, representam o código em DocBook numa variedade de formatos para "
+"publicação e distribuição. Também permitem aos tradutores criarem versões "
+"locais dos documentos de XML, para os utilizadores de Fedora em todo o "
+"mundo. A flexibilidade do XML permite a um único documento ser usado várias "
+"vezes para diversos fins, como a reutilização de código para um programador."
+d3250 2
+a3251 12
+msgid ""
+"DocBook is itself very well documented. For more information about DocBook, "
+"visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also "
+"features complete copies of <citetitle>DocBook: The Definitive Guide</"
+"citetitle> to browse and download, the canonical source for DocBook "
+"information."
+msgstr ""
+"O DocBook está em si muito bem documentado. Para mais informações acerca do "
+"DocBook, visite a página <ulink url=\"http://www.docbook.org/\"/>. A página "
+"do DocBook também contém cópias completas do livro <citetitle>DocBook: The "
+"Definitive Guide</citetitle> para navegar e transferir, sendo esta a fonte "
+"canónica de informação sobre o DocBook."
+d3258 2
+a3259 10
+msgid ""
+"DocBook XML, like a computer program, has version numbers. The version used "
+"by Fedora Documentation Project right now is 4.4. The DocBook web site may "
+"document a slightly newer version, but the majority of the schema still "
+"applies."
+msgstr ""
+"O DocBook XML, como um programa de computador, tem números de versões. A "
+"versão usada no Projecto de Documentação do Fedora neste momento é a 4.4. A "
+"página Web do DocBook poderá conter uma versão ligeiramente mais recente, "
+"mas a maioria do esquema aplica-se à mesma."
+d3262 2
+a3263 5
+msgid ""
+"Contributors who use the Microsoft Windows operating system can still make "
+"use of DocBook tools. For more information, refer to <ulink url=\"http://www."
+"codeproject.com/winhelp/docbook_howto.asp\"/>."
+msgstr ""
+d3270 2
+a3271 13
+msgid ""
+"The Fedora Documentation Project provides the tools, scripts, and "
+"stylesheets to transform your <abbrev>XML</abbrev> documents into other "
+"output formats such as <abbrev>HTML</abbrev>. In addition, these tools can "
+"build your document into a <abbrev>RPM</abbrev> package. To take advantage "
+"of these services, follow the conventions in this section to name your files."
+msgstr ""
+"O Projecto de Documentação do Fedora oferece as ferramentas, programas e "
+"folhas de estilo que transformam os seus documentos em <abbrev>XML</abbrev> "
+"noutros formatos resultantes, como o <abbrev>HTML</abbrev>. Para além disso, "
+"estas ferramentas podem transformar o seu documento num pacote <abbrev>RPM</"
+"abbrev>. Para tirar partido destes serviços, deverá seguir as convenções de "
+"nomenclatura dos seus ficheiros."
+d3274 2
+a3275 15
+msgid ""
+"On the CVS server, directories that contain document files are called "
+"<firstterm>modules</firstterm>. Each module represents a single document. "
+"Each document may consist of several <firstterm>branches</firstterm> if that "
+"document changes with each release of Fedora. Contributors can check out "
+"single branches of these modules or the entire module. Each document or "
+"branch may contain multiple XML source files."
+msgstr ""
+"No servidor de CVS, as pastas que contêm os ficheiros de documentos chamam-"
+"se <firstterm>módulos</firstterm>. Cada módulo representa um único "
+"documento. Cada documento poderá consistir em várias "
+"<firstterm>ramificações</firstterm>, se esse documento for alterado em cada "
+"versão do Fedora. Os contribuintes poderão obter ramificações únicas desses "
+"módulos ou então o módulo inteiro. Cada documento ou ramificação poderá "
+"conter vários ficheiros em XML."
+d3278 2
+a3279 5
+msgid ""
+"Use the <command>cvs co -c</command> command to view existing module names."
+msgstr ""
+"Use sempre o comando <command>cvs co -c</command> para ver os nomes dos "
+"módulos existentes."
+d3291 2
+a3292 11
+msgid ""
+"The leftmost entry in each line is the name of a module you can check out "
+"from CVS. The rest of the line ensures that checkouts include the proper "
+"branch of a document and the common build tools. For more information on "
+"CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+"O item mais à esquerda de cada linha é o nome de um módulo que poderá "
+"transferir do CVS. O restante da linha garante que as transferências incluem "
+"a ramificação correcta de um documento, assim como as ferramentas de "
+"compilação comuns. Para mais informações sobre o CVS, consulte em <xref "
+"linkend=\"ch-cvs\"/>."
+d3295 2
+a3296 12
+msgid ""
+"Note in the listing above that the <systemitem>about-fedora</systemitem> "
+"module has two branches available. One branch is for Fedora 7 and one is for "
+"forward development to match the current work of developers. On the other "
+"hand, the <systemitem>documentation-guide</systemitem> module is not "
+"branched."
+msgstr ""
+"Repare na listagem acima que o módulo <systemitem>about-fedora</systemitem> "
+"tem duas ramificações disponíveis. Uma é para o Fedora 7 e outra é para a "
+"versão em desenvolvimento posterior, reflectindo o trabalho actual dos "
+"programadores. Por outro lado, o módulo <systemitem>documentation-guide</"
+"systemitem> não tem ramificações."
+d3303 2
+a3304 9
+msgid ""
+"Modules ending with the suffix <filename>-dir</filename> are not usually "
+"helpful to checkout directly. These modules do not include the common build "
+"tools and thus do not provide many of the functions contributors require."
+msgstr ""
+"Os módulos que terminam com o sufixo <filename>-dir</filename> não são "
+"normalmente úteis para transferir directamente. Estes módulos não incluem as "
+"ferramentas de compilação comuns e, deste modo, não oferecem muitas das "
+"funções que os contribuintes necessitam."
+d3311 2
+a3312 13
+msgid ""
+"Choose a module name that accurately reflects your document's subject, but "
+"avoid any name already taken. The document title without any use of the word "
+"<wordasword>fedora</wordasword> is a reasonable choice in most cases. Use "
+"the length descriptors <wordasword>tutorial</wordasword> or "
+"<wordasword>guide</wordasword> in the module name where appropriate."
+msgstr ""
+"Escolha um nome de módulo que reflicta com precisão o assunto do seu "
+"documento, mas evite um nome que já tenha sido usado. O título do documento "
+"sem usar a palavra <wordasword>fedora</wordasword> é normalmente uma escolha "
+"razoável na maioria dos casos. Use as descrições da dimensão "
+"<wordasword>tutorial</wordasword> ou <wordasword>guide</wordasword> (guia) "
+"no nome do módulo, se for apropriado."
+d3319 2
+a3320 6
+msgid ""
+"Do not use the word <wordasword>fedora</wordasword> to name modules in the "
+"Fedora Documentation Project CVS repository."
+msgstr ""
+"Não use a palavra <wordasword>fedora</wordasword> no nome dos módulos do "
+"repositório de CVS do Projecto de Documentação do Fedora."
+d3348 1
+a3348 1
+msgstr "Gestão de 'Software' com o <placeholder-1/>"
+d3360 1
+a3360 1
+msgstr "Usar o <placeholder-1/>"
+d3371 2
+a3372 6
+msgid ""
+"Follow these guidelines for naming files to make collaboration and document "
+"reuse easy:"
+msgstr ""
+"Siga estas convenções para nomear os ficheiros, de modo a tornar a "
+"colaboração e a reutilização de documentos mais simples:"
+d3375 2
+a3376 6
+msgid ""
+"As with module names, avoid using the word <wordasword>fedora</wordasword> "
+"in file names since it is redundant."
+msgstr ""
+"Como no nome dos módulos, evite usar a palavra <wordasword>fedora</"
+"wordasword> nos nomes dos ficheiros, dado que é redundante."
+d3379 2
+a3380 6
+msgid ""
+"If the document is comprised of many XML files, avoid repeating the name of "
+"the document when naming the constituent files."
+msgstr ""
+"Se o documento for composto por muitos ficheiros XML, evite repetir o nome "
+"do documento ao criar os ficheiros constituintes."
+d3383 2
+a3384 7
+msgid ""
+"Avoid numbering files to show order, since editors and authors often "
+"rearrange documents or reuse their files in other documents."
+msgstr ""
+"Evite numerar os ficheiros para demonstrar a ordem, dado que os editores e "
+"autores normalmente reorganizam os documentos ou reutilizam os seus "
+"ficheiros noutros documentos."
+d3394 10
+a3403 5
+#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary)
+#: en_US/emacs.xml:43(primary) en_US/emacs.xml:224(primary)
+#: en_US/emacs.xml:233(primary) en_US/emacs.xml:238(primary)
+#: en_US/emacs.xml:243(primary) en_US/emacs.xml:523(application)
+#: en_US/emacs-nxml.xml:18(primary) en_US/emacs-nxml.xml:22(primary)
+d3412 2
+a3413 8
+msgid ""
+"You can use the PSGML mode available for Emacs to make it easier to write in "
+"XML format. PSGML mode provides syntax-highlighting, tag completion, and "
+"more."
+msgstr ""
+"Poderá usar o modo PSGML, que está disponível para o Emacs, de modo a ser "
+"mais fácil de escrever no formato XML. O modo PSGML oferece o realce de "
+"sintaxe, a completação de marcas, etc."
+d3437 2
+a3438 10
+msgid ""
+"For Emacs to parse your DocBook documents correctly, you must have a "
+"<filename>.emacs</filename> file. Cut and paste the following into your "
+"existing <filename>.emacs</filename> file or create a new one that contains "
+"the following lines:"
+msgstr ""
+"Para o Emacs processar correctamente os seus documentos em DocBook, deverá "
+"ter um ficheiro <filename>.emacs</filename>. Corte e cole o seguinte no seu "
+"ficheiro <filename>.emacs</filename> existente ou crie um novo que contenha "
+"as seguintes linhas:"
+d3441 2
+a3442 8
+msgid ""
+"If you have a wheel mouse and are using Emacs version 21, you can add the "
+"following to your <filename>.emacs</filename> file so your wheel will work "
+"in <application>Emacs</application>:"
+msgstr ""
+"Se tiver um rato com roda e estiver a usar o Emacs versão 21, poderá "
+"adicionar o seguinte ao seu ficheiro <filename>.emacs</filename>, para que a "
+"roda do seu rato funcione no <application>Emacs</application>:"
+d3445 2
+a3446 6
+msgid ""
+"If you are using the older version 20 of <application>Emacs</application>, "
+"add the following instead:"
+msgstr ""
+"Se estiver a usar a versão anterior - a 20 - do <application>Emacs</"
+"application>, adicione o seguinte comando:"
+d3473 2
+a3474 8
+msgid ""
+"The colors, font, and geometry (default size of window) for Emacs in your "
+"<filename>~/.Xresources</filename> file. The format for the settings is "
+"<userinput>emacs.keyword:value</userinput>."
+msgstr ""
+"As cores, tipos de letra e geometria (tamanho predefinido da janela) do "
+"Emacs no seu ficheiro <filename>~/.Xresources</filename>. O formato da "
+"configuração é <computeroutput>emacs.palavra-chave:valor</computeroutput>."
+d3481 2
+a3482 6
+msgid ""
+"If you have other settings in your <filename>~/.Xresources</filename>, add "
+"the following to the end of the file."
+msgstr ""
+"Se tiver outras configurações no seu ficheiro <filename>~/.Xresources</"
+"filename>, adicione o seguinte ao fim do ficheiro."
+d3494 1
+a3494 3
+msgstr ""
+"Depois reinicie o <application>Emacs</application> para as alterações "
+"fazerem efeito."
+d3502 1
+a3502 2
+msgstr ""
+"A tecla <keycap>Meta</keycap> normalmente é a tecla <keycap>Alt</keycap>."
+d3511 29
+a3539 17
+
+#: en_US/emacs.xml:405(segtitle)
+msgid "Description"
+msgstr "Descrição"
+
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:412(keycap)
+#: en_US/emacs.xml:430(keycap) en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:443(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:458(keycap)
+#: en_US/emacs.xml:463(keycap) en_US/emacs.xml:468(keycap)
+#: en_US/emacs.xml:473(keycap) en_US/emacs.xml:478(keycap)
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:509(keycap)
+#: en_US/emacs.xml:514(keycap) en_US/emacs.xml:515(keycap)
+#: en_US/emacs.xml:520(keycap) en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap) en_US/emacs.xml:533(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+d3543 8
+a3550 4
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:521(keycap) en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+d3552 1
+a3552 1
+msgstr "C"
+d3558 8
+a3565 8
+#: en_US/emacs.xml:407(seg) en_US/emacs.xml:508(seg) en_US/emacs.xml:514(seg)
+#: en_US/emacs.xml:520(seg) en_US/emacs.xml:532(seg) en_US/emacs.xml:540(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+d3571 2
+a3572 1
+#: en_US/emacs.xml:431(keycap) en_US/emacs.xml:437(keycap)
+d3576 2
+a3577 1
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:438(keycap)
+d3581 2
+a3582 1
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:439(keycap)
+d3587 2
+a3588 6
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+d3595 2
+a3596 8
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of "
+"tag, <placeholder-5/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, escrever o início da "
+"marca, <placeholder-5/>"
+d3600 1
+a3600 1
+msgstr "Completa a marca"
+d3616 1
+a3616 2
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+d3622 2
+a3623 1
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:533(keycap)
+d3671 2
+a3672 1
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:515(keycap)
+d3688 4
+a3691 2
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap) en_US/emacs.xml:527(keycap)
+d3699 2
+a3700 1
+#: en_US/emacs.xml:495(seg) en_US/emacs.xml:500(seg)
+d3704 4
+a3707 2
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:514(keycap)
+d3712 2
+a3713 1
+#: en_US/emacs.xml:499(keycap) en_US/emacs.xml:504(keycap)
+d3718 2
+a3719 6
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, "
+"<placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, "
+"<placeholder-3/>"
+d3722 2
+a3723 6
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, "
+"<placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, "
+"<placeholder-3/>"
+d3731 1
+a3731 1
+msgstr "F"
+d3764 2
+a3765 6
+msgid ""
+"Edit attributes for a tag (for example, you can edit the <placeholder-1/> "
+"attribute of the <placeholder-2/> tag)"
+msgstr ""
+"Edita os atributos de uma marca (por exemplo, poderá editar o atributo "
+"<placeholder-1/> da marca <placeholder-2/>)"
+d3771 2
+a3772 1
+#: en_US/emacs.xml:550(title) en_US/emacs-nxml.xml:77(title)
+d3777 2
+a3778 7
+msgid ""
+"The table or reference card of Emacs and PSGML commands can be confusing for "
+"beginners. This section provides some examples of how to use them."
+msgstr ""
+"A tabela ou cartão de referência dos comandos do Emacs e do PSGML poderão "
+"ser confusos para os principiantes. Esta secção oferece alguns exemplos de "
+"utilização dos mesmos."
+d3789 2
+a3790 10
+msgid ""
+"To avoid having to type a tag repeatedly, use the key combination "
+"<keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. "
+"At the bottom of the <application>Emacs</application> window, the following "
+"prompt appears:"
+msgstr ""
+"Em vez de escrever uma marca sempre que necessitar de a usar, use a "
+"combinação de teclas <keycap>Ctrl</keycap>-<keycap>C</keycap>, seguida do "
+"<keycap><</keycap>. No fundo da janela do <application>Emacs</"
+"application>, irá ver:"
+d3797 2
+a3798 12
+msgid ""
+"To view a list of available tags, use either the <keycap>Tab</keycap> or "
+"<keycap>?</keycap>. If you know the first few letters of a tag, enter them, "
+"followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, "
+"that tag appears. If more than one completion exists, a complete list of "
+"possible tags appears."
+msgstr ""
+"Para ver uma lista com as marcas disponíveis, use as teclas <keycap>Tab</"
+"keycap> ou <keycap>?</keycap>. Por outro lado, se souber as primeiras letras "
+"de uma marca, podê-las-á introduzir e carregar de seguida em <keycap>Tab</"
+"keycap> para obter uma lista completa das marcas disponíveis que começam por "
+"essas letras ou para completar a marca."
+d3801 2
+a3802 8
+msgid ""
+"If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, "
+"<keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the "
+"example below:"
+msgstr ""
+"Se carregar em <keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo>, "
+"<keycap><</keycap>, <keycap>K</keycap>, irá aparecer uma linha de "
+"comandos semelhante ao exemplo abaixo:"
+d3809 2
+a3810 10
+msgid ""
+"After you open a tag, you must close it. The easiest way to close an open "
+"tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</"
+"keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most "
+"recently opened tag."
+msgstr ""
+"Logo que tenha iniciado a marca que escolheu, terá de a fechar. A forma mais "
+"simples de fechar uma marca é usar a combinação de teclas <keycap>Ctrl</"
+"keycap>-<keycap>C</keycap>, seguida de <keycap>/</keycap>. Esta irá fechar a "
+"marca aberta mais próxima que tiver."
+d3821 2
+a3822 11
+msgid ""
+"Sometimes in <application>Emacs</application>, the window becomes split, "
+"with tags completions or other text in an alternate window. To return to a "
+"single window, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+msgstr ""
+"Algumas vezes no <application>Emacs</application>, a janela vai ficando "
+"dividida (com as completações de marcas ou outro texto na janela inferior). "
+"A forma mais simples de voltar atrás, para que apenas o seu XML e o texto "
+"apareçam num ecrã, é usar a combinação de teclas <keycap>Ctrl</keycap>-"
+"<keycap>X</keycap>, seguida de <keycap>1</keycap>."
+d3829 2
+a3830 8
+msgid ""
+"To save your work, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>s</keycap></keycombo>."
+msgstr ""
+"Para gravar o seu trabalho, use a seguinte combinação de teclas, "
+"<keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>Ctrl</keycap>-"
+"<keycap>S</keycap>."
+d3837 2
+a3838 10
+msgid ""
+"If the tag completion process becomes unwieldy or confusing, use the "
+"keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to "
+"exit back to the text. <application>Emacs</application> clears any prompts "
+"and returns to the buffer text."
+msgstr ""
+"Se o processo de completação de marcas se tornar incomportável ou confuso, "
+"use a sequência de teclas <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></"
+"keycombo> para voltar para o texto. O <application>Emacs</application> limpa "
+"todas as linhas de comando e volta para o texto."
+d3845 2
+a3846 12
+msgid ""
+"To open a new file, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the "
+"<application>Emacs</application> window. Enter the file name, using "
+"<keycap>Tab</keycap> completion if desired, of the file you wish to open."
+msgstr ""
+"Para abrir um novo ficheiro, use a combinação de teclas <keycap>Ctrl</"
+"keycap>-<keycap>X</keycap>, seguida de <keycap>Ctrl</keycap>-<keycap>F</"
+"keycap>. No fundo da janela do Emacs, será capaz de indicar o nome do "
+"ficheiro (usando a completação do <keycap>Tab</keycap> se necessário) do "
+"ficheiro que deseja abrir."
+d3853 2
+a3854 11
+msgid ""
+"To close <application>Emacs</application> use the key sequence "
+"<keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, "
+"<keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have "
+"not saved your work, <application>Emacs</application> prompts you to save "
+"any changed files."
+msgstr ""
+"Para fechar o <application>emacs</application>, use a combinação de teclas "
+"<keycap>Ctrl</keycap>-<keycap>X</keycap> seguida de <keycap>Ctrl</keycap>-"
+"<keycap>C</keycap>. Se não tiver gravado o seu trabalho, será questionado "
+"pelo <application>Emacs</application> para gravar os ficheiros alterados."
+d3856 2
+a3857 1
+#: en_US/emacs.xml:687(title) en_US/emacs-nxml.xml:127(title)
+d3862 2
+a3863 6
+msgid ""
+"Additional Emacs and PSGML references are available at the following "
+"locations:"
+msgstr ""
+"As referências adicionais ao Emacs e ao PSGML estão disponíveis nas "
+"seguintes localizações:"
+d3865 2
+a3866 1
+#: en_US/emacs.xml:697(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+d3871 2
+a3872 8
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+"Um cartão de referência do Emacs que vem com o pacote <filename>emacs</"
+"filename>. Poderá imprimi-lo como referência. —<filename>/usr/share/"
+"emacs/<replaceable>versão</replaceable>/etc/refcard.ps</filename>"
+d3875 2
+a3876 7
+msgid ""
+"Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/"
+"usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+msgstr ""
+"Leia o <citetitle>Editing XML with Emacs and PSGML</citetitle> no ficheiro "
+"<filename>/usr/share/doc/psgml-<replaceable>versão</replaceable>/psgml.ps</"
+"filename>."
+d3879 2
+a3880 8
+msgid ""
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—"
+"<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of "
+"Emacs commands for PSGML mode."
+msgstr ""
+"O <ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—"
+"<citetitle>Emacs/PSGML Quick Reference</citetitle> é uma tabela de "
+"referência dos comandos do Emacs para o modo do PSGML."
+d3890 2
+a3891 1
+#: en_US/emacs-nxml.xml:14(primary) en_US/emacs-nxml.xml:51(primary)
+d3900 2
+a3901 12
+msgid ""
+"You can also use the nXML mode available for <application>Emacs</"
+"application> to make it even easier to write in DocBook XML format. nXML "
+"mode provides context-sensitive editing using completion, real time validity "
+"error checking, syntax highlighting and indentation. All you need to do is "
+"install an RPM!!"
+msgstr ""
+"Também poderá usar o modo nXML que está disponível para o "
+"<application>Emacs</application>, de modo a ser ainda mais simples escrever "
+"no formato DocBook em XML. O modo nXML oferece uma edição sensível ao "
+"contexto com a completação, validação dos erros em tempo-real, realce de "
+"sintaxe e indentação. Tudo o que necessita é instalar um RPM!!"
+d3908 2
+a3909 13
+msgid ""
+"Please be aware the nxml-mode for <application>Emacs</application> is quite "
+"new, so there are a few things that the advanced user might notice when "
+"using it with other documents types. If you keep an eye on the mailing-list, "
+"you can keep up to date with these, as well as ask questions. For more "
+"details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr ""
+"Tenha em atenção que o 'nxml-mode' do <application>Emacs</application> é "
+"relativamente novo, pelo que existem algumas coisas que o utilizador mais "
+"avançado poderá notar ao usá-lo com outros tipos de documentos. Se mantiver "
+"uma vista de olhos na lista de correio, poder-se-á manter actualizado com as "
+"mesmas, assim como poderá fazer perguntas. Para mais detalhes, veja a secção "
+"<xref linkend=\"sn-emacs-nxml-readme\"/>."
+d3924 2
+a3925 14
+msgid ""
+"To use nXML mode with emacs, you will need to install the nXML RPM available "
+"from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/"
+"\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www."
+"thaiopensource.com/download/\">http://www.thaiopensource.com/download/</"
+"ulink>. The source requires a lot more work to setup, therefore we will only "
+"be concentrating on the RPM version."
+msgstr ""
+"Para usar o modo nXML com o emacs, terá de instalar o pacote RPM nXML na "
+"<ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/\">página "
+"do Tim Waugh</ulink> ou o código-fonte de <ulink url=\"http://www."
+"thaiopensource.com/download/\">http://www.thaiopensource.com/download/</"
+"ulink>. O código necessita de bastante mais trabalho de configuração; como "
+"tal, concentrar-nos-emos na versão em RPM."
+d3928 2
+a3929 6
+msgid ""
+"Information on where to get the source is available in <xref linkend=\"sn-"
+"emacs-additional-resources\"/>."
+msgstr ""
+"As informações de disponibilização do código estão disponíveis em <xref "
+"linkend=\"sn-emacs-additional-resources\"/>."
+d3932 2
+a3933 9
+msgid ""
+"Compared to PSGML mode there are only couple of commands that you need. This "
+"speeds up writing with <application>Emacs</application> considerably, which "
+"means you can concentrate more on the content of your article."
+msgstr ""
+"Em comparação com o modo PSGML, só existem alguns comandos que você "
+"necessita. Isto acelera a escrita no <application>Emacs</application> "
+"consideravelmente, o que significa que se poderá concentrar mais no conteúdo "
+"do seu artigo."
+d3936 2
+a3937 10
+msgid ""
+"To create a tag, type <userinput><</userinput> and then type the keyword. "
+"To complete the keyword, press <command>Ctrl-Ret</command>, then add the "
+"last <userinput>></userinput>. To close a tag, type <userinput></</"
+"userinput>."
+msgstr ""
+"Para criar uma marca, escreva <userinput><</userinput> e escreva depois a "
+"palavra-chave. Para completar a mesma, carregue em <command>Ctrl-Ret</"
+"command>, adicionando depois a última <userinput>></userinput>. Para "
+"fechar uma marca, escreva <userinput></</userinput>."
+d3940 2
+a3941 8
+msgid ""
+"When you open a document that doesn't have a DOCTYPE declaration at the top "
+"of the file, you will get this message and tag completion won't work because "
+"nXML will not know what format you are writing."
+msgstr ""
+"Quando abrir um documento que não tenha uma declaração DOCTYPE no topo do "
+"ficheiro, irá obter esta mensagem e a completação de marcas não irá "
+"funcionar, porque o nXML não irá saber em que formato está a escrever."
+d3944 2
+a3945 12
+msgid ""
+"To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</"
+"command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/"
+"schema/</filename> and load <filename>docbook.rnc</filename>. "
+"<application>Emacs</application> will then prompt you to save it in the "
+"current working directory."
+msgstr ""
+"Para carregar o esquema, escreva <command>Ctrl-C</command> e <command>Ctrl-"
+"S</command>, indo depois à pasta <filename>/usr/share/emacs/site-lisp/nxml-"
+"mode/schema/</filename> e carregando o <filename>docbook.rnc</filename>. O "
+"<application>Emacs</application> perguntar-lhe-á então para gravar a pasta "
+"de trabalho actual."
+d3948 2
+a3949 10
+msgid ""
+"The commands already discussed are the only differences between using "
+"<application>Emacs</application> with PSGML mode and <application>Emacs</"
+"application> with nXML mode. You will still need to use all the same "
+"commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr ""
+"Os comandos já discutidos são as únicas diferenças entre a utilização do "
+"<application>Emacs</application> com o modo PSGML e o <application>Emacs</"
+"application> com o modo nXML. Terá à mesma de usar todos os mesmos comandos "
+"que foram discutidos em <xref linkend=\"sn-emacs-basic-commands\"/>."
+d3952 2
+a3953 6
+msgid ""
+"Additional Emacs and nXML references are available at the following "
+"locations:"
+msgstr ""
+"As referências adicionais do Emacs e do nXML estão disponíveis nos seguintes "
+"locais:"
+d3968 2
+a3969 8
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+"Um cartão de referência do Emacs que vem com o pacote <filename>emacs</"
+"filename>. Poderá imprimi-lo como referência. —<filename>/usr/share/"
+"emacs/<replaceable><versão></replaceable>/etc/refcard.ps</filename>"
+d3976 2
+a3977 8
+msgid ""
+"This file can be found in the directory you extracted the source into, or in "
+"<filename>/usr/share/doc/nxml-mode-<replaceable><version></"
+"replaceable>/</filename> if you installed the RPM."
+msgstr ""
+"Este ficheiro poderá ser encontrado na pasta para onde extraiu o código ou "
+"em <filename>/usr/share/doc/nxml-mode-<replaceable><versão></"
+"replaceable>/</filename>, se instalou o RPM."
+d3984 2
+a3985 9
+msgid ""
+"This is a new major mode for GNU Emacs for editing XML documents. It "
+"supports editing well-formed XML documents and also provides schema-"
+"sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr ""
+"Este é um novo modo principal para o GNU Emacs editar documentos em XML. "
+"Este suporta a edição de documentos válidos em XML, oferecendo também a "
+"edição sensível ao esquema dos documentos em XML, usando a Sintaxe Compacta "
+"do RELAX NG."
+d3988 2
+a3989 8
+msgid ""
+"To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs "
+"version 20 will not work properly, nor will XEmacs. To get started, do the "
+"following:"
+msgstr ""
+"Para usar isto, terá de ter o GNU Emacs versão 21.x, de preferência a 21.3. "
+"O GNU Emacs versão 20 não irá funcionar correctamente, assim como o XEmacs. "
+"Para começar, faça o seguinte:"
+d3996 2
+a3997 6
+msgid ""
+"This defines the necessary autoloads. Now, visit a file containing an XML "
+"document, and do the following:"
+msgstr ""
+"Isto define todos os carregamentos automáticos necessários. Depois, vá a um "
+"ficheiro que contenha um documento em XML, fazendo o seguinte:"
+d4012 2
+a4013 6
+msgid ""
+"For information on how to use nxml-mode. The beginnings of a manual are in "
+"nxml-mode.info. You can read this using:"
+msgstr ""
+"Para mais informações sobre a utilização do nxml-mode. As introduções do "
+"manual estão no ficheiro 'nxml-mode.info'. Podê-lo-á ler com:"
+d4020 2
+a4021 6
+msgid ""
+"It's also installed as an entry at the end of the top-level info directory. "
+"So you can read it with <command>C-h i</command> as usual."
+msgstr ""
+"Também está instalado como um elemento no fim da pasta de topo do 'info'. "
+"Como tal, poderá lê-la com o <command>C-H I</command>, como de costume."
+d4024 2
+a4025 7
+msgid ""
+"You can use <filename>test.valid.xml</filename> and <filename>test.invalid."
+"xml</filename> as examples of valid and invalid XML documents."
+msgstr ""
+"Poderá usar os ficheiros <filename>test.valid.xml</filename> e "
+"<filename>test.invalid.xml</filename> como exemplos de documentos em XML "
+"válidos e inválidos."
+d4029 1
+a4029 3
+msgstr ""
+"Para que as coisas sejam carregadas automaticamente de cada vez que iniciar "
+"o Emacs, adicione:"
+d4041 2
+a4042 15
+msgid ""
+"to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-"
+"200YMMDD</computeroutput> is the directory containing the <filename>.elc</"
+"filename> files. Note that <filename>rng-auto.el</filename> does not load "
+"all of the nxml-mode code; it merely sets things up so that all the features "
+"of nxml-mode will be autoloaded properly. You should not try to autoload "
+"<filename>rng-auto.el</filename> itself."
+msgstr ""
+"ao seu ficheiro <filename>.emacs</filename>, onde o <computeroutput>~/nxml-"
+"mode-200AMMDD</computeroutput> é a pasta que contém os ficheiros <filename>."
+"elc</filename>. Lembre-se que o <filename>rng-auto.el</filename> não carrega "
+"tudo do modo 'nxml-mode'; simplesmente configura as coisas, para que as "
+"funcionalidades do 'nxml-mode' sejam carregadas automaticamente. Não deverá "
+"tentar carregar automaticamente o <filename>rng-auto.el</filename> "
+"propriamente dito."
+d4045 2
+a4046 10
+msgid ""
+"To use nxml-mode automatically for files with an extension of <filename>xml</"
+"filename>, <filename>xsl</filename>, <filename>rng</filename> or "
+"<filename>xhtml</filename>, add the following to your <filename>.emacs</"
+"filename> file:"
+msgstr ""
+"Para usar o 'nxml-mode' automaticamente para os ficheiros com as extensões "
+"<filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> "
+"ou <filename>xhtml</filename>, adicione o seguinte ao seu ficheiro "
+"<filename>.emacs</filename>:"
+d4060 2
+a4061 10
+msgid ""
+"If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are "
+"running Emacs 21.3 or later, then I recommend enabling unify-8859-on-"
+"decoding-mode, by adding the following to your <filename>.emacs</filename> "
+"file:"
+msgstr ""
+"Se editar o XML com as codificações iso-8859-N em vez da iso-8859-1 e "
+"estiver a usar o Emacs 21.3 ou posterior, recomenda-se que active o 'unify-"
+"8859-on-decoding-mode', adicionando a seguinte sequência ao seu ficheiro "
+"<filename>.emacs</filename>:"
+d4069 2
+a4070 8
+msgid ""
+"To get validation and schema-sensitive editing, you need a RELAX NG Compact "
+"Syntax (RNC) schema for you document. The schema directory includes some "
+"schemas for popular document types."
+msgstr ""
+"Para ter uma validação e edição sensível ao esquema, precisa de um esquema "
+"de Sintaxe Compacta do Relax NG (RNC) do seu documento. A pasta do esquema "
+"inclui alguns esquemas para os tipos de documentos mais conhecidos."
+d4073 2
+a4074 6
+msgid ""
+"For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://"
+"relaxng.org/</ulink>."
+msgstr ""
+"Para mais informações sobre o RELAX NG, consulte a página <ulink url="
+"\"http://relaxng.org/\">http://relaxng.org/</ulink>."
+d4077 2
+a4078 8
+msgid ""
+"For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://"
+"relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial."
+"html</ulink>"
+msgstr ""
+"Para um tutorial sobre a Sintaxe Compacta do RELAX NG, veja a página <ulink "
+"url=\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-"
+"tutorial.html</ulink>"
+d4081 2
+a4082 8
+msgid ""
+"For automatically creating RNC schemas, I recommend my Trang program: <ulink "
+"url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee."
+"thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr ""
+"Para criar automaticamente os esquemas RNG, recomenda-se o programa Trang: "
+"<ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee."
+"thaiopensource.com/relaxng/trang.html\"</ulink>"
+d4101 2
+a4102 9
+msgid ""
+"To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also "
+"use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html"
+"\">http://www.pantor.com/download.html\"</ulink>."
+msgstr ""
+"Para converter um esquema de sintaxe em XML do RELAX NG (.rng) para um "
+"esquema RNC, poderá também usar a folha de estilo XSLT em <ulink url="
+"\"http://www.pantor.com/download.html\">http://www.pantor.com/download.html"
+"\"</ulink>."
+d4105 2
+a4106 10
+msgid ""
+"To convert a W3C XML Schema to an RNC schema, you need first to convert it "
+"to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on "
+"top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www."
+"dev.java.net/</ulink>."
+msgstr ""
+"Para converter um Esquema de XML da W3C num esquema RNC, terá primeiro de o "
+"converter para a sintaxe XML do RELAX NG, usando a ferramenta de conversão "
+"para RELAX NG da Sun, a 'rngconv' (assente sobre o MSV). Veja em <ulink url="
+"\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+d4113 2
+a4114 9
+msgid ""
+"Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-"
+"mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug "
+"reports, discussion. I will announce all new versions there."
+msgstr ""
+"Use por favor a lista <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-"
+"mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> para os "
+"relatórios de erros, discussão, etc. Serão aí anunciadas todas as versões "
+"novas."
+d4129 2
+a4130 8
+msgid ""
+"This document is based on a document started by Tammy Fox (tfox at redhat."
+"com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray "
+"Fuller (jrfuller at redhat.com)."
+msgstr ""
+"Este documento baseia-se num documento iniciado por Tammy Fox (tfox at "
+"redhat.com) e com contribuições de Sandra Moore (smoore at redhat.com) e "
+"Johnray Fuller (jrfuller at redhat.com)."
+d4133 2
+a4134 7
+msgid ""
+"A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to "
+"fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr ""
+"Uma correcção do Roozbeh Pournader (roozbeh at sharif.edu) foi aplicada para "
+"corrigir alguns erros ortográficos e explicar que o CVS anónimo não permite "
+"o envio de novas versões."
+d4137 2
+a4138 8
+msgid ""
+"Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to "
+"add the trailing slashes to the <command>figure</command> tag example in "
+"<filename>docs-xml-tags.xml</filename>."
+msgstr ""
+"Foram aplicadas correcções de Gavin Henry (ghenry at suretecsystems.com) par "
+"adicionar as barras finais ao exemplo da marca <command>figure</command>, "
+"como aparece em <filename>docs-xml-tags.xml</filename>."
+d4141 2
+a4142 6
+msgid ""
+"A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been "
+"applied to add <xref linkend=\"ch-vim\"/>."
+msgstr ""
+"Uma actualização do Joshua Daniel Franklin (joshuadfranklin at yahoo.com) "
+"para adicionar o <xref linkend=\"ch-vim\"/>."
+d4145 2
+a4146 8
+msgid ""
+"A patch from Karsten Wade (kwade at redhat.com) has been applied to add "
+"<xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields "
+"(stickster at gmail.com)."
+msgstr ""
+"Uma correcção de Karsten Wade (kwade at redhat.com) foi aplicada para "
+"adicionar o <xref linkend=\"sn-screenshots\"/>. Foi editada por Paul W. "
+"Frields (stickster at gmail.com)."
+d4155 2
+a4156 7
+msgid ""
+"A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been "
+"applied to more fully explaing the document building system."
+msgstr ""
+"Uma correcção de Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) foi "
+"aplicada para descrever com maior pormenor o sistema de compilação de "
+"documentos."
+a4164 1
+
+a4173 1
+
+a4179 1
+
+a4187 1
+
+a4189 1
+
+a4191 1
+
+a4193 1
+
+a4201 1
+
+a4214 1
+
+a4216 1
+
+a4229 1
+
+a4235 1
+
+a4237 1
+
+a4245 1
+
+a4258 1
+
+a4264 1
+
+a4270 1
+
+a4278 1
+
+a4286 1
+
+a4294 1
+
+a4302 1
+
+a4308 1
+
+a4318 1
+
+a4320 1
+
+a4326 1
+
+a4334 1
+
+a4346 1
+
+a4348 1
+
+a4355 1
+
+d4363 1
+a4363 1
+#~ "<!--$Id: pt.po,v 1.23 2007/12/15 21:52:11 pfrields Exp $ -->\n"
+d4375 1
+a4375 1
+#~ "<!--$Id: pt.po,v 1.23 2007/12/15 21:52:11 pfrields Exp $ -->\n"
+a4384 1
+
+a4392 1
+
+a4394 1
+
+a4415 1
+
+a4417 1
+
+a4419 1
+
+a4425 1
+
+a4431 1
+
+a4433 1
+
+a4443 1
+
+a4451 1
+
+a4463 1
+
+a4465 1
+
+a4473 1
+
+a4475 1
+
+a4491 1
+
+a4493 1
+
+a4504 1
+
+a4518 1
+
+a4524 1
+
+a4527 1
+
+a4529 1
+
+a4531 1
+
+a4533 1
+
+a4541 1
+
+a4543 1
+
+a4545 1
+
+a4552 1
+
+a4565 1
+
+a4573 1
+
+a4582 1
+
+a4588 1
+
+a4620 1
+
+a4622 1
+
+a4636 1
+
+a4638 1
+
+a4648 1
+
+a4657 1
+
+a4663 1
+
+a4666 1
+
+a4678 1
+
+a4685 1
+
+a4691 1
+
+a4693 1
+
+a4702 1
+
+a4711 1
+
+a4717 1
+
+a4719 1
+
+a4721 1
+
+a4743 1
+
+a4760 1
+
+a4765 1
+
+a4767 1
+
+a4807 1
+
+a4809 1
+
+a4811 1
+
+a4813 1
+
+a4815 1
+
+a4817 1
+
+a4819 1
+
+a4843 1
+
+a4849 1
+
+a4851 1
+
+a4853 1
+
+a4855 1
+
+a4863 1
+
+a4872 1
+
+a4878 1
+
+a4880 1
+
+a4888 1
+
+a4896 1
+
+a4902 1
+
+a4904 1
+
+a4911 1
+
+a4919 1
+
+a4921 1
+
+a4923 1
+
+a4925 1
+
+a4927 1
+
+a4935 1
+
+a4946 1
+
+a4960 1
+
+a4969 1
+
+a4971 1
+
+a4981 1
+
+a4989 1
+
+a4992 1
+
+a4994 1
+
+a5006 1
+
+a5030 1
+
+a5040 1
+
+a5042 1
+
+a5052 1
+
+a5064 1
+
+a5070 1
+
+a5072 1
+
+a5074 1
+
+a5082 1
+
+a5088 1
+
+a5094 1
+
+a5105 1
+
+a5111 1
+
+a5125 1
+
+a5157 1
+
+a5159 1
+
+a5162 1
+
+a5164 1
+
+a5166 1
+
+a5168 1
+
+a5179 1
+
+a5185 1
+
+a5233 1
+
+a5240 1
+
+a5255 1
+
+a5257 1
+
+a5263 1
+
+a5269 1
+
+a5322 1
+
+a5324 1
+
+a5331 1
+
+a5333 1
+
+a5343 1
+
+a5349 1
+
+a5352 1
+
+a5354 1
+
+a5356 1
+
+a5363 1
+
+a5372 1
+
+a5374 1
+
+a5518 1
+
+a5522 1
+
+a5524 1
+
+a5526 1
+
+a5528 1
+
+a5530 1
+
+a5532 1
+
+a5534 1
+
+a5536 1
+
+a5538 1
+
+a5541 1
+
+a5543 1
+
+a5546 1
+
+a5548 1
+
+a5550 1
+
+a5552 1
+
+a5554 1
+
+a5560 1
+
+a5568 1
+
+a5576 1
+
+a5578 1
+
+a5584 1
+
+a5586 1
+
+a5642 1
+
+a5644 1
+
+a5648 1
+
+a5650 1
+
+a5656 1
+
+a5658 1
+
+a5664 1
+
+a5666 1
+
+a5673 1
+
+a5679 1
+
+a5681 1
+
+a5689 1
+
+a5695 1
+
+a5697 1
+
+a5699 1
+
+a5705 1
+
+a5721 1
+
+a5723 1
+
+a5725 1
+
+a5735 1
+
+a5737 1
+
+a5759 1
+
+a5761 1
+
+a5763 1
+
+a5769 1
+
+a5771 1
+
+a5795 1
+
+a5797 1
+
+a5799 1
+
+a5807 1
+
+a5818 1
+
+a5820 1
+
+a5827 1
+
+a5833 1
+
+a5841 1
+
+a5843 1
+
+a5845 1
+
+a5847 1
+
+a5849 1
+
+a5851 1
+
+a5853 1
+
+a5861 1
+
+a5879 1
+
+a5885 1
+
+a5908 1
+
+a5916 1
+
+a5918 1
+
+a5926 1
+
+a5939 1
+
+a5945 1
+
+a5947 1
+
+a5956 1
+
+a5958 1
+
+a5966 1
+
+a5972 1
+
+a5980 1
+
+a5982 1
+
+a5984 1
+
+a5990 1
+
+a6005 1
+
+a6019 1
+
+a6036 1
+
+a6048 1
+
+a6050 1
+
+a6061 1
+
+a6069 1
+
+a6071 1
+
+a6089 1
+
+a6091 1
+
+a6093 1
+
+a6095 1
+
+a6097 1
+
+a6099 1
+
+a6101 1
+
+a6103 1
+
+a6137 1
+
+a6139 1
+
+a6141 1
+
+a6143 1
+
+a6145 1
+
+a6151 1
+
+a6169 1
+
+a6171 1
+
+a6173 1
+
+a6193 1
+
+a6195 1
+
+a6201 1
+
+a6209 1
+
+a6211 1
+
+a6213 1
+
+a6229 1
+
+a6281 1
+
+a6287 1
+
+a6315 1
+
+a6317 1
+
+a6319 1
+
+a6325 1
+
+a6327 1
+
+a6329 1
+
+a6335 1
+
+a6337 1
+
+a6343 1
+
+a6345 1
+
+a6349 1
+
+a6351 1
+
+a6367 1
+
+a6369 1
+
+a6371 1
+
+a6377 1
+
+a6380 1
+
+a6490 1
+
+a6492 1
+
+a6494 1
+
+a6496 1
+
+a6498 1
+
+a6500 1
+
+a6502 1
+
+a6504 1
+
+a6513 1
+
+a6519 1
+
+a6525 1
+
+a6648 1
+
+a6656 1
+
+a6658 1
+
+a6660 1
+
+a6662 1
+
+a6664 1
+
+a6666 1
+
+a6668 1
+
+a6670 1
+
+a6678 1
+
+a6680 1
+
+a6682 1
+
+a6688 1
+
+a6690 1
+
+a6692 1
+
+a6696 1
+
+a6698 1
+
+a6709 1
+
+a6715 1
+
+a6729 1
+
+a6731 1
+
+a6737 1
+
+a6747 1
+
+a6749 1
+
+a6751 1
+
+a6755 1
+
+a6768 1
+
+a6777 1
+
+a6787 1
+
+a6789 1
+
+a6796 1
+
+a6808 1
+
+a6820 1
+
+a6828 1
+
+a6835 1
+
+a6845 1
+
+a6847 1
+
+a6853 1
+
+a6859 1
+
+a6869 1
+
+a6875 1
+
+a6877 1
+
+a6879 1
+
+a6881 1
+
+a6883 1
+
+a6885 1
+
+a6997 1
+
+a6999 1
+
+a7001 1
+
+a7009 1
+
+a7011 1
+
+a7025 1
+
+a7039 1
+
+a7052 1
+
+a7067 1
+
+a7069 1
+
+a7085 1
+
+a7087 1
+
+a7089 1
+
+a7101 1
+
+a7104 1
+
+a7112 1
+
+a7117 1
+
+a7119 1
+
+a7130 1
+
+a7148 1
+
+a7154 1
+
+a7419 1
+
+a7421 1
+
+a7432 1
+
+a7450 1
+
+a7455 1
+
+a7466 1
+
+a7479 1
+
+a7483 1
+
+a7493 1
+
+a7495 1
+
+a7503 1
+
+a7505 1
+
+a7513 1
+
+a7523 1
+
+a7525 1
+
+a7531 1
+
+a7537 1
+
+a7539 1
+
+a7545 1
+
+a7547 1
+
+a7553 1
+
+a7563 1
+
+a7565 1
+
+a7582 1
+
+a7596 1
+
+d7599 1
+@
+
+
+1.23
+log
+ at Update POT and PO
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-12-15 16:51-0500\n"
+d112 6
+a117 1
+#: en_US/rpm-info.xml:31(holder)
+d121 1
+a121 1
+#: en_US/rpm-info.xml:33(title)
+d125 1
+a125 1
+#: en_US/rpm-info.xml:34(desc)
+d130 5
+a134 1
+#: en_US/rpm-info.xml:38(details)
+d138 1
+a138 1
+#: en_US/rpm-info.xml:42(details)
+d142 1
+a142 1
+#: en_US/rpm-info.xml:46(details)
+d147 1
+a147 1
+#: en_US/rpm-info.xml:50(details)
+d151 1
+a151 1
+#: en_US/rpm-info.xml:54(details)
+d155 1
+a155 1
+#: en_US/rpm-info.xml:58(details)
+d159 1
+a159 1
+#: en_US/rpm-info.xml:62(details)
+d164 1
+a164 1
+#: en_US/rpm-info.xml:69(details)
+d168 181
+d3359 1
+d3366 1
+a3366 1
+"which produces the text \"Fedora 8.\""
+d6772 1
+a6772 1
+#~ "<!--$Id: pt.po,v 1.22 2007/11/15 02:12:48 pfrields Exp $ -->\n"
+d6784 1
+a6784 1
+#~ "<!--$Id: pt.po,v 1.22 2007/11/15 02:12:48 pfrields Exp $ -->\n"
+a9180 3
+#~ msgid "Creating a List Within a Table"
+#~ msgstr "Criar uma Lista Dentro de uma Tabela"
+
+@
+
+
+1.22
+log
+ at Update POT/PO files for DocGuide, minor changes
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-11-14 21:12-0500\n"
+d126 4
+d133 1
+a133 1
+#: en_US/rpm-info.xml:42(details)
+d138 1
+a138 1
+#: en_US/rpm-info.xml:46(details)
+d142 1
+a142 1
+#: en_US/rpm-info.xml:50(details)
+d146 1
+a146 1
+#: en_US/rpm-info.xml:54(details)
+d150 1
+a150 1
+#: en_US/rpm-info.xml:58(details)
+d155 1
+a155 1
+#: en_US/rpm-info.xml:65(details)
+d4440 24
+d4467 2
+a4468 2
+#: en_US/module-struct.xml:243(abbrev) en_US/module-struct.xml:254(abbrev)
+#: en_US/module-struct.xml:279(abbrev) en_US/module-struct.xml:284(abbrev)
+d4472 2
+a4473 2
+#: en_US/module-struct.xml:247(systemitem)
+#: en_US/module-struct.xml:257(systemitem)
+d4477 2
+a4478 2
+#: en_US/module-struct.xml:248(systemitem)
+#: en_US/module-struct.xml:258(systemitem)
+d4482 1
+a4482 1
+#: en_US/module-struct.xml:246(filename)
+d4486 1
+a4486 1
+#: en_US/module-struct.xml:243(seg)
+d4498 1
+a4498 1
+#: en_US/module-struct.xml:253(systemitem)
+d4502 1
+a4502 1
+#: en_US/module-struct.xml:256(filename)
+d4506 1
+a4506 1
+#: en_US/module-struct.xml:254(seg)
+d4516 1
+a4516 1
+#: en_US/module-struct.xml:262(systemitem)
+d4520 2
+a4521 2
+#: en_US/module-struct.xml:263(abbrev) en_US/module-struct.xml:264(abbrev)
+#: en_US/module-struct.xml:280(abbrev) en_US/module-struct.xml:285(abbrev)
+d4525 1
+a4525 1
+#: en_US/module-struct.xml:263(seg)
+d4535 1
+a4535 1
+#: en_US/module-struct.xml:268(systemitem)
+d4539 1
+a4539 1
+#: en_US/module-struct.xml:269(command)
+d4543 1
+a4543 1
+#: en_US/module-struct.xml:269(seg)
+d4551 1
+a4551 1
+#: en_US/module-struct.xml:273(systemitem)
+d4555 1
+a4555 1
+#: en_US/module-struct.xml:274(seg)
+d4559 2
+a4560 2
+#: en_US/module-struct.xml:277(systemitem)
+#: en_US/module-struct.xml:286(filename)
+d4564 1
+a4564 1
+#: en_US/module-struct.xml:279(emphasis)
+d4568 1
+a4568 1
+#: en_US/module-struct.xml:278(seg)
+d4576 1
+a4576 1
+#: en_US/module-struct.xml:283(systemitem)
+d4580 1
+a4580 1
+#: en_US/module-struct.xml:284(seg)
+d4588 1
+a4588 1
+#: en_US/module-struct.xml:291(title)
+d4592 1
+a4592 1
+#: en_US/module-struct.xml:292(para)
+d4600 1
+a4600 1
+#: en_US/module-struct.xml:296(title)
+d4604 1
+a4604 1
+#: en_US/module-struct.xml:297(para)
+d4618 1
+a4618 1
+#: en_US/module-struct.xml:305(para)
+d4627 1
+a4627 1
+#: en_US/module-struct.xml:312(title)
+d4631 1
+a4631 1
+#: en_US/module-struct.xml:313(para)
+d4643 1
+a4643 1
+#: en_US/module-struct.xml:320(para)
+d4665 1
+a4665 1
+#: en_US/module-struct.xml:334(para)
+d4676 1
+a4676 1
+#: en_US/module-struct.xml:340(para)
+d4693 1
+a4693 1
+#: en_US/module-struct.xml:350(para)
+d4709 1
+a4709 1
+#: en_US/module-struct.xml:359(para)
+d4717 1
+a4717 1
+#: en_US/module-struct.xml:365(title)
+d4721 1
+a4721 1
+#: en_US/module-struct.xml:372(title)
+d4725 1
+a4725 1
+#: en_US/module-struct.xml:373(para)
+d4732 1
+a4732 1
+#: en_US/module-struct.xml:377(para)
+d4736 1
+a4736 1
+#: en_US/module-struct.xml:381(para)
+d4750 1
+a4750 1
+#: en_US/module-struct.xml:391(title)
+d4754 1
+a4754 1
+#: en_US/module-struct.xml:392(para)
+d4767 1
+a4767 1
+#: en_US/module-struct.xml:399(para)
+d4775 1
+a4775 1
+#: en_US/module-struct.xml:405(para)
+d4779 1
+a4779 1
+#: en_US/module-struct.xml:409(para)
+d4787 1
+a4787 1
+#: en_US/module-struct.xml:414(para)
+d4795 1
+a4795 1
+#: en_US/module-struct.xml:417(replaceable)
+d4799 1
+a4799 1
+#: en_US/module-struct.xml:417(screen)
+d6581 1
+a6581 1
+#~ "<!--$Id: pt.po,v 1.21 2007/10/27 17:34:37 zepires Exp $ -->\n"
+d6593 1
+a6593 1
+#~ "<!--$Id: pt.po,v 1.21 2007/10/27 17:34:37 zepires Exp $ -->\n"
+@
+
+
+1.21
+log
+ at Synced Devel Release Notes with F-8 one. Fixed spelling errors and inconsistencies
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-10-22 01:49+0100\n"
+d12 58
+a69 29
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas Redundâncias update yahoo VIMRUNTIME generated important \n"
+d126 4
+d131 2
+a132 1
+msgstr "Adição de indicações sobre o acesso Web ao CVS e à antevisão do trabalho"
+d134 1
+a134 1
+#: en_US/rpm-info.xml:42(details)
+d138 1
+a138 1
+#: en_US/rpm-info.xml:46(details)
+d142 1
+a142 1
+#: en_US/rpm-info.xml:50(details)
+d146 1
+a146 1
+#: en_US/rpm-info.xml:54(details)
+d151 1
+a151 1
+#: en_US/rpm-info.xml:61(details)
+d190 8
+a197 1
+msgstr "A página Web do <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> é um conjunto de ficheiros e programas em PHP. Os responsáveis de publicação mantêm estes ficheiros num repositório de CVS e a página Web transfere-os de hora a hora para actualizar a página. A máquina não usa automaticamente o conteúdo mais recente para a página Web. Em vez disso, transfere os ficheiros com a marca de CVS <systemitem>LIVE</systemitem> para preencher a página Web."
+d293 7
+a299 1
+msgstr "Deverá ter acesso ao módulo <systemitem>cvsweb</systemitem> através do Sistema de Contas do Fedora para verificar e enviar as alterações. Se não tiver acesso, poderá usar o <userinput><![CDATA[:pserver:anonymous]]></userinput> em vez do <userinput><![CDATA[:ext:utilizador]]></userinput> indicado acima. Visite o Sistema de Contas do Fedora em <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> para mais informações."
+d974 1
+d979 5
+a983 5
+"<citetitle>Ulysses</citetitle><footnote id=\"fn-ulysses\"><placeholder-1/></"
+"footnote>. There, Joyce uses long streams of words without punctuation to "
+"simulate a character's internal consciousness. By violating basic rules of "
+"grammar and syntax, Joyce simulates the disorganized but loosely connected "
+"thought patterns of the narrator."
+d3113 1
+d3119 7
+a3126 1
+msgstr "O comando <command>sfdisk</command> aceita um ficheiro de programa como dados de entrada para configurar as partições num disco rígido. Em alguns casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, criando uma tabela de partições incorrecta no seu disco.<warning><placeholder-1/><placeholder-2/></warning>"
+d3172 7
+a3178 1
+msgstr "Use as entidades oferecidas pelo Projecto de Documentação do Fedora. Estas entidades aparecem na pasta <filename>common/</filename> da distribuição <filename>fedora-docs</filename>. (Consulte também a secção <xref linkend=\"ch-getting-files\"/>.) Por exemplo, não use abreviaturas do tipo \"FC2.\" Em vez disso, use as entidades predefinidas \"&FC; &FCVER;,\" que irá gerar o texto \"Fedora 8.\""
+d3975 6
+a3980 1
+msgstr "O navegador de <application>Ajuda</application> do GNOME, também conhecido como <command>yelp</command> e o <application>Khelp</application> do KDE poderão representar a informação em XML do DocBook à medida das necessidades. Use estas aplicações para antever o seu trabalho, se o preferir ler num ambiente de um navegador. Execute assim o seguinte comando:"
+d3987 4
+a3990 1
+msgstr "Certifique-se que aponta o navegador de ajuda preferido para o ficheiro-pai do seu documento em XML. Logo que o documento seja carregado, poderá adicionar um favorito para o mesmo para o poder usar mais tarde."
+d4000 3
+a4002 1
+msgstr "Manter os seus documentos no mesmo local para cada sessão de recepção torna os favoritos do navegador de ajuda mais efectivos."
+d4010 5
+a4014 1
+msgstr "Logo que tenha guardado um favorito, este irá aparecer no navegador de ajuda sempre que o usar. Poderá agora carregar em <keycap>F1</keycap> durante qualquer sessão gráfica para lançar o navegador de ajuda. Depois, escolha o seu favorito do menu para antever o seu documento em qualquer altura."
+d4100 1
+d4106 8
+a4113 3
+"XML source for document-specific <placeholder-2/><footnote><placeholder-3/></"
+"footnote>."
+msgstr "Esta é a única pasta que é absolutamente necessária. Esta tem o nome da língua original do documento, como por exemplo <placeholder-1/> (Inglês dos EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas todas as línguas. Esta pasta contém todo o código em XML do documento actual, assim como o código em XML específico do documento para <placeholder-2/><footnote><placeholder-3/></footnote>."
+d4235 1
+d4239 10
+a4248 4
+"command><footnote><placeholder-1/></footnote> and shell scripts. Authors "
+"need <emphasis>no</emphasis> prior experience with either shell scripts or a "
+"<command>make(1)</command>."
+msgstr "O sistema de compilação poderá representar o documento noutro formato, como o <abbrev>HTML</abbrev> ou o <abbrev>PDF</abbrev>, usando o <command>make(1)</command><footnote><placeholder-1/></footnote> e os programas da linha de comandos. Os autores <emphasis>não</emphasis> precisam de qualquer experiência anterior com os programas da linha de comandos ou o <command>make(1)</command>."
+d4981 8
+a4988 1
+#: en_US/getting-files.xml:106(title)
+d4992 1
+a4992 1
+#: en_US/getting-files.xml:107(para)
+d5007 1
+a5007 1
+#: en_US/getting-files.xml:115(para)
+d5024 1
+a5024 1
+#: en_US/getting-files.xml:122(para)
+d5031 1
+a5031 1
+#: en_US/getting-files.xml:125(title)
+d5035 1
+a5035 1
+#: en_US/getting-files.xml:126(userinput)
+d5040 1
+a5040 1
+#: en_US/getting-files.xml:145(para)
+d5053 1
+a5053 1
+#: en_US/getting-files.xml:150(para)
+d5067 1
+a5067 1
+#: en_US/getting-files.xml:157(title)
+d5071 1
+a5071 1
+#: en_US/getting-files.xml:158(para)
+d5082 1
+a5082 1
+#: en_US/getting-files.xml:164(title)
+d5086 1
+a5086 1
+#: en_US/getting-files.xml:165(para)
+d5101 1
+a5101 1
+#: en_US/getting-files.xml:174(title)
+d5105 1
+a5105 1
+#: en_US/getting-files.xml:175(para)
+d5113 1
+a5113 1
+#: en_US/getting-files.xml:181(title)
+d5117 1
+a5117 1
+#: en_US/getting-files.xml:182(segtitle)
+d5121 1
+a5121 1
+#: en_US/getting-files.xml:183(segtitle)
+d5125 1
+a5125 1
+#: en_US/getting-files.xml:185(seg)
+d5129 1
+a5129 1
+#: en_US/getting-files.xml:186(seg)
+d5133 1
+a5133 1
+#: en_US/getting-files.xml:190(application)
+d5137 1
+a5137 1
+#: en_US/getting-files.xml:189(seg)
+d5141 1
+a5141 1
+#: en_US/getting-files.xml:191(seg)
+d5145 1
+a5145 1
+#: en_US/getting-files.xml:194(application)
+d5149 1
+a5149 1
+#: en_US/getting-files.xml:194(seg)
+d5153 1
+a5153 1
+#: en_US/getting-files.xml:195(seg)
+d5157 1
+a5157 1
+#: en_US/getting-files.xml:200(title)
+d5161 1
+a5161 1
+#: en_US/getting-files.xml:201(para)
+d5169 1
+a5169 1
+#: en_US/getting-files.xml:205(para)
+d5177 1
+a5177 1
+#: en_US/getting-files.xml:210(para)
+d5185 1
+a5185 1
+#: en_US/getting-files.xml:215(para)
+d6553 1
+a6553 1
+#~ "<!--$Id: pt.po,v 1.20 2007/10/22 09:47:17 zepires Exp $ -->\n"
+d6565 1
+a6565 1
+#~ "<!--$Id: pt.po,v 1.20 2007/10/22 09:47:17 zepires Exp $ -->\n"
+@
+
+
+1.20
+log
+ at Some updates on documentation
+@
+text
+ at d12 29
+a40 58
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu "
+"guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires "
+"VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend "
+"autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert "
+"articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap "
+"dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML "
+"tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man "
+"sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot "
+"developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro "
+"keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC "
+"configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG "
+"Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule "
+"Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote "
+"eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest "
+"Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text "
+"jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd "
+"colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES "
+"set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray "
+"ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG "
+"PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar "
+"Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse "
+"cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo "
+"imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject "
+"Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference "
+"rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef "
+"authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done "
+"Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered "
+"nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead "
+"Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas "
+"Redundâncias update yahoo VIMRUNTIME generated important \n"
+d50 4
+a53 1
+"X-POFile-SpellExtra: Definitive\n"
+d156 1
+a156 8
+msgstr ""
+"A página Web do <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem> é um conjunto de ficheiros e programas em PHP. Os respoonsáveis "
+"de publicação mantêm estes ficheiros num repositório de CVS e a página Web "
+"transfere-os de hora a hora para actualizar a página. A máquina não usa "
+"automaticamente o conteúdo mais recente para a página Web. Em vez disso, "
+"transfere os ficheiros com a marca de CVS <systemitem>LIVE</systemitem> para "
+"preencher a página Web."
+d6458 1
+a6458 1
+#~ "<!--$Id: pt.po,v 1.19 2007/10/21 16:03:34 zepires Exp $ -->\n"
+d6470 1
+a6470 1
+#~ "<!--$Id: pt.po,v 1.19 2007/10/21 16:03:34 zepires Exp $ -->\n"
+@
+
+
+1.19
+log
+ at Some updates on docs
+@
+text
+ at d4 2
+a5 2
+"POT-Creation-Date: 2007-08-03 12:42-0400\n"
+"PO-Revision-Date: 2007-10-21 16:43+0100\n"
+d123 4
+d130 1
+a130 1
+#: en_US/rpm-info.xml:42(details)
+d134 1
+a134 1
+#: en_US/rpm-info.xml:46(details)
+d138 1
+a138 1
+#: en_US/rpm-info.xml:50(details)
+d143 1
+a143 1
+#: en_US/rpm-info.xml:57(details)
+d160 9
+a168 1
+msgstr "Este capítulo mostra como publicar o trabalho no Projecto de Documentação do Fedora oficial para o servidor <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem>. Para publicar a documentação oficial, deverá estar aprovado para escrever o repositório Web no CVS. O acesso de publicação está limitado aos contribuintes que tenham demonstrado capacidade para trabalhar com o CVS e as outras ferramentas do projecto. Logo que a tenha adquirido e esteja à vontade com esses conhecimentos, as contribuições como responsável de publicação são bem-vindas."
+d182 8
+a189 1
+msgstr "A página Web do <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> é um conjunto de ficheiros e programas em PHP. Os respoonsáveis de publicação mantêm estes ficheiros num repositório de CVS e a página Web transfere-os de hora a hora para actualizar a página. A máquina não usa automaticamente o conteúdo mais recente para a página Web. Em vez disso, transfere os ficheiros com a marca de CVS <systemitem>LIVE</systemitem> para preencher a página Web."
+d197 6
+a202 1
+msgstr "Cada responsável de publicação configura uma página de testes num sistema Fedora disponível. Esta página do servidor, chamada normalmente de <firstterm>área segura</firstterm>, permite ao responsável testar e ver as alterações dos documentos, garantindo a estabilidade da página para o público."
+d212 3
+a214 1
+msgstr "Para testar a publicação do documento, configure primeiro uma área segura na Web numa máquina local de Fedora."
+d238 3
+a240 1
+msgstr "Mude as permissões nesta pasta para facilitar o acesso para a sua conta normal de utilizador."
+d273 4
+d279 10
+d291 3
+a293 1
+msgstr "Edite o ficheiro <filename>/etc/hosts</filename> e adicione a seguinte linha <emphasis>depois</emphasis> de todas as outras linhas:"
+d295 1
+a295 1
+#: en_US/publishing.xml:68(screen)
+d300 1
+a300 1
+#: en_US/publishing.xml:71(para)
+d304 3
+a306 1
+msgstr "Crie um ficheiro <filename>/etc/httpd/conf.d/fpo.conf</filename> com o seguinte conteúdo:"
+d308 1
+a308 1
+#: en_US/publishing.xml:85(para)
+d312 3
+a314 1
+msgstr "Crie um ficheiro <filename>/etc/php.d/fpo.ini</filename> com o seguinte conteúdo:"
+d316 1
+a316 1
+#: en_US/publishing.xml:87(screen)
+d321 1
+a321 1
+#: en_US/publishing.xml:90(para)
+d325 1
+a325 1
+#: en_US/publishing.xml:91(screen)
+d330 1
+a330 2
+#: en_US/publishing.xml:92(para)
+#, fuzzy
+d332 3
+a334 1
+msgstr "Para que o servidor Web seja iniciado sempre no arranque, execute o seguinte comando:"
+d336 1
+a336 1
+#: en_US/publishing.xml:94(screen)
+d341 1
+a341 1
+#: en_US/publishing.xml:97(para)
+d345 3
+a347 1
+msgstr "Para testar a página da nova área segura, abra um navegador Web e aponte-o para o URL <uri>http://docs.localhost.localdomain</uri>."
+d349 1
+a349 1
+#: en_US/publishing.xml:101(title)
+d353 1
+a353 1
+#: en_US/publishing.xml:103(title)
+d357 1
+a357 1
+#: en_US/publishing.xml:104(para)
+d361 3
+a363 1
+msgstr "Siga estas recomendações para garantir a facilidade de uso e manutenção para todos os responsáveis de publicação."
+d365 1
+a365 1
+#: en_US/publishing.xml:108(para)
+d371 5
+a375 1
+msgstr "Use um nome breve e descritivo para a pasta de documentos. O nome do módulo no seu local do CVS é normalmente apropriado. Os bons exemplos incluem o <filename class=\"directory\">install-guide/</filename> ou o <filename class=\"directory\">example-tutorial/</filename>."
+d377 1
+a377 1
+#: en_US/publishing.xml:115(para)
+d381 4
+a384 1
+msgstr "Sob a pasta do documento, inclua a pasta de uma ramificação, caso o documento faça referência a funcionalidades específicas de uma dada versão do Fedora."
+d386 1
+a386 1
+#: en_US/publishing.xml:120(para)
+d392 5
+a396 1
+msgstr "Na pasta da ramificação (ou na pasta do documento se não existirem ramificações), crie pelo menos uma pasta <filename class=\"directory\">en_US/</filename>. Crie uma pasta adicional para cada código de país cuja documentação tenha sido completamente traduzida."
+d398 1
+a398 1
+#: en_US/publishing.xml:129(title)
+d402 1
+a402 1
+#: en_US/publishing.xml:130(para)
+d408 6
+a413 1
+msgstr "Para adicionar conteúdos, siga o procedimento abaixo. Os comandos seguintes mostra um exemplo de adição de conteúdos para um documento novo chamado <citetitle>Tutorial XPTO</citetitle>. Este documento inclui uma tradução para o código de país \"zz_XX\" e segue as especificidades de cada versão do Fedora."
+d415 1
+a415 1
+#: en_US/publishing.xml:137(para)
+d419 1
+a419 1
+#: en_US/publishing.xml:138(screen)
+d432 1
+a432 1
+#: en_US/publishing.xml:144(para)
+d435 3
+a437 1
+msgstr "Crie a versão em HTML de cada tradução do documento a partir do CVS de documentação."
+d439 1
+a439 1
+#: en_US/publishing.xml:146(replaceable)
+d443 1
+a443 1
+#: en_US/publishing.xml:146(screen)
+d452 1
+a452 1
+#: en_US/publishing.xml:150(para)
+d456 1
+a456 1
+#: en_US/publishing.xml:151(screen)
+d467 1
+a467 1
+#: en_US/publishing.xml:156(para)
+d471 3
+a473 1
+msgstr "Converta o HTML em cada pasta para PHP, usando o programa <filename>docbookhtml2php.py</filename> que é fornecido."
+d475 1
+a475 1
+#: en_US/publishing.xml:165(para)
+d484 9
+a492 1
+msgstr "Crie os ficheiros <filename>index.php</filename> necessários para as pastas globais. Cada pasta de documento e ramificação deverá ter um ficheiro <filename>index.php</filename> que direcciona os utilizadores para o conteúdo apropriado. Neste exemplo, os ficheiros necessários são o <filename>tutorial-xpto/index.php</filename> e o <filename>tutorial-xpto/f7/index.php</filename>. Não precisa de escrever estes ficheiros do zero. Copie um ficheiro existente a partir de outro documento e mude-o da forma adequada para o novo documento."
+d494 1
+a494 1
+#: en_US/publishing.xml:175(para)
+d498 3
+a500 1
+msgstr "Dependendo do contexto, a publicação poderá incluir a mudança de um ficheiro <filename>index.php</filename> de um nível superior."
+d502 1
+a502 1
+#: en_US/publishing.xml:179(para)
+d506 3
+a508 1
+msgstr "Para testar as alterações na sua área segura, abra um navegador Web e aponte-o para <uri>http://docs.localhost.localdomain/</uri>."
+d510 1
+a510 1
+#: en_US/publishing.xml:183(title)
+d514 1
+a514 1
+#: en_US/publishing.xml:184(para)
+d518 3
+a520 1
+msgstr "<emphasis>Não siga mais em frente até que teste todas as alterações.</emphasis> Verifique se todas as ligações e páginas de índice funcionam."
+d522 1
+a522 1
+#: en_US/publishing.xml:192(title)
+d526 1
+a526 1
+#: en_US/publishing.xml:193(para)
+d528 2
+a529 1
+msgstr "Para enviar o seu novo conteúdo para a página Web, siga este procedimento:"
+d531 1
+a531 1
+#: en_US/publishing.xml:197(para)
+d535 1
+a535 1
+#: en_US/publishing.xml:198(screen)
+d566 1
+a566 1
+#: en_US/publishing.xml:214(para)
+d570 3
+a572 1
+msgstr "Envie as alterações para o CVS. Use uma mensagem que descreva o conteúdo a ser enviado."
+d574 1
+a574 1
+#: en_US/publishing.xml:216(replaceable)
+d578 1
+a578 1
+#: en_US/publishing.xml:216(screen)
+d583 1
+a583 1
+#: en_US/publishing.xml:219(para)
+d587 1
+a587 1
+#: en_US/publishing.xml:221(screen)
+d964 5
+a968 5
+"<citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long "
+"streams of words without punctuation to simulate a character's internal "
+"consciousness. By violating basic rules of grammar and syntax, Joyce "
+"simulates the disorganized but loosely connected thought patterns of the "
+"narrator."
+d3103 2
+a3104 2
+"<placeholder-1/>"
+msgstr "O comando <command>sfdisk</command> aceita um ficheiro de programa como dados de entrada para configurar as partições num disco rígido. Em alguns casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, criando uma tabela de partições incorrecta no seu disco.<placeholder-1/>"
+d3149 2
+a3150 8
+"which produces the text \"Fedora 7.\""
+msgstr ""
+"Use as entidades oferecidas pelo Projecto de Documentação do Fedora. Estas "
+"entidades aparecem na pasta <filename>common/</filename> da distribuição "
+"<filename>fedora-docs</filename>. (Consulte também a secção <xref linkend="
+"\"ch-getting-files\"/>.) Por exemplo, não use abreviaturas do tipo \"FC2.\" "
+"Em vez disso, use as entidades predefinidas \"&FC; &FCVER;,\" que "
+"irá gerar o texto \"Fedora 7.\""
+d3936 38
+d4063 3
+a4065 2
+"XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr "Esta é a única pasta que é absolutamente necessária. Esta tem o nome da língua original do documento, como por exemplo <placeholder-1/> (Inglês dos EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas todas as línguas. Esta pasta contém todo o código em XML do documento actual, assim como o código em XML específico do documento para <placeholder-2/><placeholder-3/>."
+d4120 9
+a4128 1
+msgstr "A pasta <placeholder-1/> contém os ficheiros 'Portable Object' ou <placeholder-2/> especialmente formatados, criados e usados pelos tradutores. As ferramentas de compilação do Projecto de Documentação do Fedora usam estes ficheiros para criar versões traduzidas dos documentos. Os documentos traduzidos não são guardados no CVS; são criados à medida das necessidades a partir destes ficheiros PO. A pasta <placeholder-3/> também contém o ficheiro <placeholder-4/>, que contém os <placeholder-5/> activos nas traduções ou línguas."
+d4190 4
+a4193 4
+"command><placeholder-1/> and shell scripts. Authors need <emphasis>no</"
+"emphasis> prior experience with either shell scripts or a <command>make(1)</"
+"command>."
+msgstr "O sistema de compilação poderá representar o documento noutro formato, como o <abbrev>HTML</abbrev> ou o <abbrev>PDF</abbrev>, usando o <command>make(1)</command><placeholder-1/> e os programas da linha de comandos. Os autores <emphasis>não</emphasis> precisam de qualquer experiência anterior com os programas da linha de comandos ou o <command>make(1)</command>."
+d6491 1
+a6491 1
+#~ "<!--$Id: pt.po,v 1.18 2007/08/03 16:42:44 pfrields Exp $ -->\n"
+d6503 1
+a6503 1
+#~ "<!--$Id: pt.po,v 1.18 2007/08/03 16:42:44 pfrields Exp $ -->\n"
+@
+
+
+1.18
+log
+ at Push new 0.3.1 POT and update PO - ERRATA, this time with new content file
+@
+text
+ at d5 1
+a5 1
+"PO-Revision-Date: 2007-07-28 18:10-0400\n"
+d124 1
+a124 1
+msgstr ""
+d128 1
+a128 1
+msgstr ""
+d132 1
+a132 1
+msgstr ""
+d145 1
+a145 1
+msgstr ""
+d156 1
+a156 1
+msgstr ""
+d160 1
+a160 1
+msgstr ""
+d170 1
+a170 1
+msgstr ""
+d178 1
+a178 1
+msgstr ""
+d182 1
+a182 1
+msgstr ""
+d188 1
+a188 1
+msgstr ""
+d192 1
+a192 1
+msgstr ""
+d195 1
+a195 1
+#, fuzzy, no-wrap
+d197 1
+a197 1
+msgstr "su -c 'yum install cvs'"
+d201 1
+a201 1
+msgstr ""
+d206 1
+a206 1
+msgstr ""
+d212 1
+a212 1
+msgstr ""
+d221 1
+a221 1
+msgstr ""
+d225 1
+a225 1
+msgstr ""
+d230 1
+a230 1
+msgstr ""
+d234 1
+a234 1
+msgstr ""
+d242 2
+d249 1
+a249 1
+msgstr ""
+d254 1
+a254 1
+msgstr ""
+a256 1
+#, fuzzy
+d260 1
+a260 2
+msgstr ""
+"Edite o ficheiro <filename>/etc/sysconfig/init</filename> como se segue:"
+a262 1
+#, fuzzy
+d266 1
+a266 2
+msgstr ""
+"Edite o ficheiro <filename>/etc/sysconfig/init</filename> como se segue:"
+d271 1
+a271 1
+msgstr ""
+a273 1
+#, fuzzy
+d275 1
+a275 1
+msgstr "Depois de modificar este ficheiro, execute o seguinte comando:"
+d280 1
+a280 1
+msgstr ""
+d285 1
+a285 2
+msgstr ""
+"Para descobrir todas as sessões de SSH activas, execute o seguinte comando:"
+d290 1
+a290 1
+msgstr ""
+d296 1
+a296 1
+msgstr ""
+d300 1
+a300 1
+msgstr ""
+a302 1
+#, fuzzy
+d304 1
+a304 1
+msgstr "Recomendações de Gramática e Utilização"
+d310 1
+a310 1
+msgstr ""
+d318 1
+a318 1
+msgstr ""
+d324 1
+a324 1
+msgstr ""
+d332 1
+a332 1
+msgstr ""
+a334 1
+#, fuzzy
+d336 1
+a336 1
+msgstr "Convenções dos Nomes"
+d344 1
+a344 1
+msgstr ""
+d348 1
+a348 1
+msgstr ""
+d358 4
+d366 1
+a366 1
+msgstr ""
+d370 1
+a370 1
+msgstr ""
+d378 2
+d383 1
+a383 1
+msgstr ""
+d392 3
+d400 1
+a400 1
+msgstr ""
+d411 1
+a411 1
+msgstr ""
+d417 1
+a417 1
+msgstr ""
+d423 1
+a423 1
+msgstr ""
+d427 1
+a427 1
+msgstr ""
+d433 1
+a433 1
+msgstr ""
+d437 1
+a437 1
+msgstr ""
+d441 1
+a441 1
+msgstr ""
+d445 1
+a445 1
+msgstr ""
+d464 13
+d482 1
+a482 1
+msgstr ""
+d486 1
+a486 1
+msgstr ""
+d491 1
+a491 1
+msgstr ""
+d495 1
+a495 1
+msgstr ""
+d500 1
+a500 1
+msgstr ""
+a869 1
+#, fuzzy
+a3007 1
+#, fuzzy
+d3014 1
+a3014 7
+msgstr ""
+"O comando <command>sfdisk</command> aceita um ficheiro de programa como "
+"dados de entrada para configurar as partições num disco rígido. Em alguns "
+"casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de "
+"entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, "
+"criando uma tabela de partições incorrecta no seu disco."
+"<warning><placeholder-1/><placeholder-2/></warning>"
+a3935 1
+#, fuzzy
+d3942 1
+a3942 7
+msgstr ""
+"Esta é a única pasta que é absolutamente necessária. Esta tem o nome da "
+"língua original do documento, como por exemplo <placeholder-1/> (Inglês dos "
+"EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas "
+"todas as línguas. Esta pasta contém todo o código em XML do documento "
+"actual, assim como o código em XML específico do documento para <placeholder-"
+"2/><footnote><placeholder-3/></footnote>."
+d3982 1
+a3982 1
+msgstr ""
+a3984 1
+#, fuzzy
+d3986 1
+a3986 1
+msgstr "tabelas"
+a3988 1
+#, fuzzy
+d3997 1
+a3997 7
+msgstr ""
+"A pasta <placeholder-1/> contém os ficheiros 'Portable Object' ou "
+"<placeholder-2/> especialmente formatados, criados e usados pelos "
+"tradutores. As ferramentas de compilação do Projecto de Documentação do "
+"Fedora usam estes ficheiros para criar versões traduzidas dos documentos. Os "
+"documentos traduzidos não são guardados no CVS; são criados à medida das "
+"necessidades a partir destes ficheiros PO."
+a4055 1
+#, fuzzy
+d4062 1
+a4062 7
+msgstr ""
+"O sistema de compilação poderá representar o documento noutro formato, como "
+"o <abbrev>HTML</abbrev> ou o <abbrev>PDF</abbrev>, usando o <command>make(1)"
+"</command><footnote><placeholder-1/></footnote> e os programas da linha de "
+"comandos. Os autores <emphasis>não</emphasis> precisam de qualquer "
+"experiência anterior com os programas da linha de comandos ou o <command>make"
+"(1)</command>."
+a4623 1
+#, fuzzy
+d5187 1
+a5187 1
+msgstr ""
+d6360 1
+a6360 1
+#~ "<!--$Id: pt.po,v 1.17 2007/08/03 16:39:22 pfrields Exp $ -->\n"
+d6372 1
+a6372 1
+#~ "<!--$Id: pt.po,v 1.17 2007/08/03 16:39:22 pfrields Exp $ -->\n"
+@
+
+
+1.17
+log
+ at Push new 0.3.1 POT and update PO
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-08-03 12:38-0400\n"
+d143 343
+d6375 1
+a6375 1
+#~ "<!--$Id: pt.po,v 1.16 2007/07/29 23:25:11 pfrields Exp $ -->\n"
+d6387 1
+a6387 1
+#~ "<!--$Id: pt.po,v 1.16 2007/07/29 23:25:11 pfrields Exp $ -->\n"
+a8442 4
+#~ msgid "Edit the <filename>/etc/sysconfig/init</filename> file as follows:"
+#~ msgstr ""
+#~ "Edite o ficheiro <filename>/etc/sysconfig/init</filename> como se segue:"
+
+a9436 3
+#~ msgid "username"
+#~ msgstr "utilizador"
+
+@
+
+
+1.16
+log
+ at Update POT and PO with new metadata strings
+@
+text
+ at d4 1
+a4 1
+"POT-Creation-Date: 2007-07-28 18:10-0400\n"
+d123 8
+d134 1
+a134 1
+#: en_US/rpm-info.xml:42(details)
+d139 1
+a139 1
+#: en_US/rpm-info.xml:49(details)
+d3221 1
+a3221 1
+#: en_US/emacs.xml:557(title) en_US/emacs-nxml.xml:160(title)
+d3538 1
+a3538 1
+#: en_US/module-struct.xml:46(title)
+d3542 1
+a3542 1
+#: en_US/module-struct.xml:47(segtitle)
+d3546 1
+a3546 1
+#: en_US/module-struct.xml:48(segtitle)
+d3550 1
+a3550 1
+#: en_US/module-struct.xml:49(segtitle)
+d3554 1
+a3554 1
+#: en_US/module-struct.xml:51(seg)
+d3558 2
+a3559 2
+#: en_US/module-struct.xml:52(seg) en_US/module-struct.xml:89(seg)
+#: en_US/module-struct.xml:96(seg)
+d3563 2
+a3564 2
+#: en_US/module-struct.xml:55(filename)
+#: en_US/module-struct.xml:177(systemitem)
+d3568 1
+a3568 1
+#: en_US/module-struct.xml:59(firstterm)
+d3572 1
+a3572 1
+#: en_US/module-struct.xml:60(para)
+d3584 1
+a3584 1
+#: en_US/module-struct.xml:53(seg)
+d3600 1
+a3600 1
+#: en_US/module-struct.xml:68(seg)
+d3604 1
+a3604 1
+#: en_US/module-struct.xml:69(seg) en_US/module-struct.xml:79(seg)
+d3608 1
+a3608 1
+#: en_US/module-struct.xml:70(filename) en_US/module-struct.xml:74(filename)
+d3612 1
+a3612 1
+#: en_US/module-struct.xml:70(seg)
+d3624 1
+a3624 1
+#: en_US/module-struct.xml:78(seg)
+d3628 1
+a3628 1
+#: en_US/module-struct.xml:80(filename) en_US/module-struct.xml:184(filename)
+d3632 1
+a3632 1
+#: en_US/module-struct.xml:82(acronym)
+d3636 11
+a3646 1
+#: en_US/module-struct.xml:80(seg)
+d3652 3
+a3654 1
+"are created as needed from these PO files."
+d3663 1
+a3663 1
+#: en_US/module-struct.xml:88(seg) en_US/module-struct.xml:90(filename)
+d3667 1
+a3667 1
+#: en_US/module-struct.xml:90(seg)
+d3675 1
+a3675 1
+#: en_US/module-struct.xml:95(filename) en_US/module-struct.xml:97(filename)
+d3679 1
+a3679 1
+#: en_US/module-struct.xml:97(seg)
+d3684 1
+a3684 1
+#: en_US/module-struct.xml:102(title)
+d3688 1
+a3688 1
+#: en_US/module-struct.xml:103(para)
+d3701 1
+a3701 1
+#: en_US/module-struct.xml:111(title)
+d3705 1
+a3705 1
+#: en_US/module-struct.xml:116(para)
+d3719 1
+a3719 1
+#: en_US/module-struct.xml:112(para)
+d3735 1
+a3735 1
+#: en_US/module-struct.xml:128(title)
+d3739 1
+a3739 1
+#: en_US/module-struct.xml:129(para)
+d3749 1
+a3749 1
+#: en_US/module-struct.xml:135(para)
+d3758 1
+a3758 1
+#: en_US/module-struct.xml:141(title)
+d3762 1
+a3762 1
+#: en_US/module-struct.xml:158(para)
+d3772 1
+a3772 1
+#: en_US/module-struct.xml:164(title)
+d3776 1
+a3776 1
+#: en_US/module-struct.xml:165(segtitle)
+d3780 1
+a3780 1
+#: en_US/module-struct.xml:166(segtitle) en_US/module-struct.xml:244(segtitle)
+d3784 1
+a3784 1
+#: en_US/module-struct.xml:168(systemitem)
+d3788 1
+a3788 1
+#: en_US/module-struct.xml:169(seg)
+d3796 1
+a3796 1
+#: en_US/module-struct.xml:174(systemitem)
+d3800 1
+a3800 1
+#: en_US/module-struct.xml:175(seg)
+d3808 1
+a3808 16
+#: en_US/module-struct.xml:180(systemitem)
+msgid "OTHERS"
+msgstr "OTHERS"
+
+#: en_US/module-struct.xml:181(seg)
+msgid ""
+"This variable contains a listing of ISO codes for any other versions into "
+"which the document has been translated. The module must contain a "
+"<placeholder-1/> directory and a PO file for any indicated additional "
+"languages."
+msgstr ""
+"Esta variável contém uma lista dos códigos ISO das outras versões traduzidas "
+"do documento. O módulo deverá conter uma pasta <placeholder-1/> e um "
+"ficheiro PO para cada língua adicional indicada."
+
+#: en_US/module-struct.xml:188(systemitem)
+d3812 1
+a3812 1
+#: en_US/module-struct.xml:189(seg)
+d3825 1
+a3825 1
+#: en_US/module-struct.xml:198(systemitem)
+d3829 1
+a3829 1
+#: en_US/module-struct.xml:201(systemitem)
+d3833 1
+a3833 1
+#: en_US/module-struct.xml:206(systemitem)
+d3837 1
+a3837 1
+#: en_US/module-struct.xml:199(seg)
+d3854 1
+a3854 1
+#: en_US/module-struct.xml:212(title)
+d3858 1
+a3858 1
+#: en_US/module-struct.xml:213(para)
+d3867 1
+a3867 1
+#: en_US/module-struct.xml:217(para)
+d3881 1
+a3881 1
+#: en_US/module-struct.xml:226(title)
+d3885 1
+a3885 1
+#: en_US/module-struct.xml:227(para)
+d3900 1
+a3900 1
+#: en_US/module-struct.xml:236(title)
+d3904 1
+a3904 1
+#: en_US/module-struct.xml:237(para)
+d3912 1
+a3912 1
+#: en_US/module-struct.xml:242(title)
+d3916 1
+a3916 1
+#: en_US/module-struct.xml:243(segtitle)
+d3920 1
+a3920 1
+#: en_US/module-struct.xml:246(systemitem)
+d3924 2
+a3925 2
+#: en_US/module-struct.xml:247(abbrev) en_US/module-struct.xml:258(abbrev)
+#: en_US/module-struct.xml:283(abbrev) en_US/module-struct.xml:288(abbrev)
+d3929 2
+a3930 2
+#: en_US/module-struct.xml:251(systemitem)
+#: en_US/module-struct.xml:261(systemitem)
+d3934 2
+a3935 2
+#: en_US/module-struct.xml:252(systemitem)
+#: en_US/module-struct.xml:262(systemitem)
+d3939 1
+a3939 1
+#: en_US/module-struct.xml:250(filename)
+d3943 1
+a3943 1
+#: en_US/module-struct.xml:247(seg)
+d3955 1
+a3955 1
+#: en_US/module-struct.xml:257(systemitem)
+d3959 1
+a3959 1
+#: en_US/module-struct.xml:260(filename)
+d3963 1
+a3963 1
+#: en_US/module-struct.xml:258(seg)
+d3973 1
+a3973 1
+#: en_US/module-struct.xml:266(systemitem)
+d3977 2
+a3978 2
+#: en_US/module-struct.xml:267(abbrev) en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:284(abbrev) en_US/module-struct.xml:289(abbrev)
+d3982 1
+a3982 1
+#: en_US/module-struct.xml:267(seg)
+d3992 1
+a3992 1
+#: en_US/module-struct.xml:272(systemitem)
+d3996 1
+a3996 1
+#: en_US/module-struct.xml:273(command)
+d4000 1
+a4000 1
+#: en_US/module-struct.xml:273(seg)
+d4008 1
+a4008 1
+#: en_US/module-struct.xml:277(systemitem)
+d4012 1
+a4012 1
+#: en_US/module-struct.xml:278(seg)
+d4016 2
+a4017 2
+#: en_US/module-struct.xml:281(systemitem)
+#: en_US/module-struct.xml:290(filename)
+d4021 1
+a4021 1
+#: en_US/module-struct.xml:283(emphasis)
+d4025 1
+a4025 1
+#: en_US/module-struct.xml:282(seg)
+d4033 1
+a4033 1
+#: en_US/module-struct.xml:287(systemitem)
+d4037 1
+a4037 1
+#: en_US/module-struct.xml:288(seg)
+d4045 1
+a4045 1
+#: en_US/module-struct.xml:295(title)
+d4049 1
+a4049 1
+#: en_US/module-struct.xml:296(para)
+d4057 1
+a4057 1
+#: en_US/module-struct.xml:300(title)
+d4061 1
+a4061 1
+#: en_US/module-struct.xml:301(para)
+d4075 1
+a4075 1
+#: en_US/module-struct.xml:309(para)
+d4084 1
+a4084 1
+#: en_US/module-struct.xml:316(title)
+d4088 1
+a4088 1
+#: en_US/module-struct.xml:317(para)
+d4100 1
+a4100 1
+#: en_US/module-struct.xml:324(para)
+d4122 1
+a4122 1
+#: en_US/module-struct.xml:338(para)
+d4133 1
+a4133 1
+#: en_US/module-struct.xml:344(para)
+d4150 1
+a4150 1
+#: en_US/module-struct.xml:354(para)
+d4166 1
+a4166 1
+#: en_US/module-struct.xml:363(para)
+d4174 1
+a4174 1
+#: en_US/module-struct.xml:369(title)
+d4178 1
+a4178 1
+#: en_US/module-struct.xml:376(title)
+d4182 1
+a4182 1
+#: en_US/module-struct.xml:377(para)
+d4189 1
+a4189 1
+#: en_US/module-struct.xml:381(para)
+d4193 1
+a4193 1
+#: en_US/module-struct.xml:385(para)
+d4207 1
+a4207 1
+#: en_US/module-struct.xml:395(title)
+d4211 1
+a4211 1
+#: en_US/module-struct.xml:396(para)
+d4224 1
+a4224 1
+#: en_US/module-struct.xml:403(para)
+d4232 1
+a4232 1
+#: en_US/module-struct.xml:409(para)
+d4236 1
+a4236 1
+#: en_US/module-struct.xml:413(para)
+d4244 1
+a4244 1
+#: en_US/module-struct.xml:418(para)
+d4252 1
+a4252 1
+#: en_US/module-struct.xml:421(replaceable)
+d4256 1
+a4256 1
+#: en_US/module-struct.xml:421(screen)
+d4295 1
+d4297 2
+a4298 2
+"This document explains the tools used by the Fedora Documentation Project "
+"and provides writing and tagging guidelines to make Fedora documentation is "
+d4684 1
+a4684 1
+#: en_US/emacs.xml:243(primary) en_US/emacs.xml:518(application)
+d4835 14
+a4848 5
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:522(keycap)
+msgid "Meta"
+msgstr "Meta"
+d4850 6
+a4855 5
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:493(keycap)
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:509(keycap) en_US/emacs.xml:515(keycap)
+msgid "x"
+msgstr "x"
+d4857 3
+a4859 4
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:494(keycap)
+#: en_US/emacs.xml:499(keycap)
+msgid "Enter"
+msgstr "Enter"
+d4861 2
+a4862 1
+#: en_US/emacs.xml:407(seg)
+d4864 2
+a4865 2
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, "
+"<placeholder-3/>"
+d4867 2
+a4868 2
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, "
+"<placeholder-3/>"
+d4870 1
+a4870 1
+#: en_US/emacs.xml:410(seg)
+d4874 1
+a4874 22
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:438(keycap) en_US/emacs.xml:443(keycap)
+#: en_US/emacs.xml:448(keycap) en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:458(keycap) en_US/emacs.xml:463(keycap)
+#: en_US/emacs.xml:468(keycap) en_US/emacs.xml:473(keycap)
+#: en_US/emacs.xml:478(keycap) en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:503(keycap) en_US/emacs.xml:504(keycap)
+#: en_US/emacs.xml:509(keycap) en_US/emacs.xml:510(keycap)
+#: en_US/emacs.xml:515(keycap) en_US/emacs.xml:516(keycap)
+#: en_US/emacs.xml:527(keycap) en_US/emacs.xml:528(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:537(keycap)
+msgid "Ctrl"
+msgstr "Ctrl"
+
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:443(keycap) en_US/emacs.xml:516(keycap)
+#: en_US/emacs.xml:527(keycap) en_US/emacs.xml:535(keycap)
+#: en_US/emacs.xml:537(keycap)
+msgid "c"
+msgstr "C"
+
+#: en_US/emacs.xml:426(keycap) en_US/emacs.xml:432(keycap)
+d4878 1
+a4878 1
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:433(keycap)
+d4882 1
+a4882 1
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:434(keycap)
+d4886 1
+a4886 1
+#: en_US/emacs.xml:425(seg)
+d4894 1
+a4894 1
+#: en_US/emacs.xml:428(seg)
+d4898 1
+a4898 1
+#: en_US/emacs.xml:431(seg)
+d4908 1
+a4908 1
+#: en_US/emacs.xml:435(seg)
+d4912 1
+a4912 1
+#: en_US/emacs.xml:438(keycap)
+d4916 1
+a4916 1
+#: en_US/emacs.xml:440(seg)
+d4920 1
+a4920 1
+#: en_US/emacs.xml:444(keycap)
+d4924 1
+a4924 1
+#: en_US/emacs.xml:443(seg)
+d4929 1
+a4929 1
+#: en_US/emacs.xml:445(seg)
+d4933 1
+a4933 1
+#: en_US/emacs.xml:448(keycap) en_US/emacs.xml:528(keycap)
+d4937 1
+a4937 1
+#: en_US/emacs.xml:450(seg)
+d4941 1
+a4941 1
+#: en_US/emacs.xml:453(keycap)
+d4945 1
+a4945 1
+#: en_US/emacs.xml:455(seg)
+d4949 1
+a4949 1
+#: en_US/emacs.xml:458(keycap)
+d4953 1
+a4953 1
+#: en_US/emacs.xml:460(seg)
+d4957 1
+a4957 1
+#: en_US/emacs.xml:463(keycap)
+d4961 1
+a4961 1
+#: en_US/emacs.xml:465(seg)
+d4965 1
+a4965 1
+#: en_US/emacs.xml:468(keycap)
+d4969 1
+a4969 1
+#: en_US/emacs.xml:470(seg)
+d4973 1
+a4973 1
+#: en_US/emacs.xml:473(keycap)
+d4977 1
+a4977 1
+#: en_US/emacs.xml:475(seg)
+d4981 1
+a4981 1
+#: en_US/emacs.xml:478(keycap) en_US/emacs.xml:510(keycap)
+d4985 1
+a4985 1
+#: en_US/emacs.xml:480(seg)
+d4989 1
+a4989 1
+#: en_US/emacs.xml:483(keycap)
+d4993 1
+a4993 1
+#: en_US/emacs.xml:485(seg)
+d4997 6
+a5002 1
+#: en_US/emacs.xml:488(keycap)
+d5006 1
+a5006 1
+#: en_US/emacs.xml:490(seg) en_US/emacs.xml:495(seg)
+d5010 11
+a5020 1
+#: en_US/emacs.xml:493(seg)
+d5028 1
+a5028 1
+#: en_US/emacs.xml:498(seg)
+d5036 1
+a5036 1
+#: en_US/emacs.xml:500(seg)
+d5040 1
+a5040 1
+#: en_US/emacs.xml:504(keycap)
+d5044 1
+a5044 10
+#: en_US/emacs.xml:503(seg) en_US/emacs.xml:509(seg) en_US/emacs.xml:515(seg)
+#: en_US/emacs.xml:527(seg) en_US/emacs.xml:535(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+
+#: en_US/emacs.xml:506(seg)
+d5048 1
+a5048 1
+#: en_US/emacs.xml:512(seg)
+d5052 1
+a5052 1
+#: en_US/emacs.xml:518(seg)
+d5056 1
+a5056 1
+#: en_US/emacs.xml:522(keycap)
+d5060 1
+a5060 1
+#: en_US/emacs.xml:524(seg)
+d5064 1
+a5064 1
+#: en_US/emacs.xml:531(computeroutput)
+d5069 1
+a5069 1
+#: en_US/emacs.xml:532(computeroutput)
+d5074 1
+a5074 1
+#: en_US/emacs.xml:530(seg)
+d5082 1
+a5082 1
+#: en_US/emacs.xml:539(seg)
+d5086 1
+a5086 1
+#: en_US/emacs.xml:545(title) en_US/emacs-nxml.xml:77(title)
+d5090 1
+a5090 1
+#: en_US/emacs.xml:547(para)
+d5099 1
+a5099 1
+#: en_US/emacs.xml:554(title)
+d5103 1
+a5103 1
+#: en_US/emacs.xml:558(para)
+d5107 1
+a5107 1
+#: en_US/emacs.xml:562(para)
+d5119 1
+a5119 1
+#: en_US/emacs.xml:569(prompt)
+d5123 1
+a5123 1
+#: en_US/emacs.xml:571(para)
+d5137 1
+a5137 1
+#: en_US/emacs.xml:580(para)
+d5147 1
+a5147 1
+#: en_US/emacs.xml:597(title)
+d5151 1
+a5151 1
+#: en_US/emacs.xml:599(para)
+d5163 1
+a5163 1
+#: en_US/emacs.xml:611(title)
+d5167 1
+a5167 1
+#: en_US/emacs.xml:614(title)
+d5171 1
+a5171 1
+#: en_US/emacs.xml:615(para)
+d5184 1
+a5184 1
+#: en_US/emacs.xml:625(title)
+d5188 1
+a5188 1
+#: en_US/emacs.xml:626(para)
+d5198 1
+a5198 1
+#: en_US/emacs.xml:637(title)
+d5202 1
+a5202 1
+#: en_US/emacs.xml:638(para)
+d5214 1
+a5214 1
+#: en_US/emacs.xml:648(title)
+d5218 1
+a5218 1
+#: en_US/emacs.xml:649(para)
+d5232 1
+a5232 1
+#: en_US/emacs.xml:663(title)
+d5236 1
+a5236 1
+#: en_US/emacs.xml:664(para)
+d5249 1
+a5249 1
+#: en_US/emacs.xml:682(title) en_US/emacs-nxml.xml:127(title)
+d5253 1
+a5253 1
+#: en_US/emacs.xml:684(para)
+d5261 1
+a5261 1
+#: en_US/emacs.xml:692(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+d5265 1
+a5265 1
+#: en_US/emacs.xml:696(para)
+d5275 1
+a5275 1
+#: en_US/emacs.xml:703(para)
+d5284 1
+a5284 1
+#: en_US/emacs.xml:709(para)
+d5294 1
+a5294 1
+#: en_US/emacs.xml:718(citetitle)
+d5783 7
+a5789 11
+#: en_US/acknowledgments.xml:43(para)
+msgid ""
+"A patch from Paul W. Frields (stickster at gmail.com) has been applied to "
+"add more explanation of the <command>screen</command> tag set to <xref "
+"linkend=\"sn-xml-tags-screen\"/>."
+msgstr ""
+"Uma correcção de Paul W. Frields (stickster at hotmail.com) foi aplicada "
+"para adicionar mais explicações sobre o conjunto de marcas <command>screen</"
+"command> em <xref linkend=\"sn-xml-tags-screen\"/>."
+
+#: en_US/acknowledgments.xml:49(para)
+d5803 29
+d6032 1
+a6032 1
+#~ "<!--$Id: xml-tags.xml,v 1.6 2007/06/23 05:25:29 pfrields Exp $ -->\n"
+d6044 1
+a6044 1
+#~ "<!--$Id: pt.po,v 1.15 2007/07/21 15:19:59 zepires Exp $ -->\n"
+a7148 3
+#~ msgid "tables"
+#~ msgstr "tabelas"
+
+@
+
+
+1.15
+log
+ at Finished changes on RH translations and docs
+@
+text
+ at d4 2
+a5 2
+"POT-Creation-Date: 2007-07-21 15:03+0100\n"
+"PO-Revision-Date: 2007-07-21 16:11+0100\n"
+d12 58
+a69 29
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas Redundâncias update yahoo VIMRUNTIME generated important \n"
+d123 4
+d131 1
+a131 1
+#: en_US/rpm-info.xml:45(details)
+d135 3
+a137 56
+#: en_US/xml-tags.xml:13(title)
+msgid "DocBook XML Tags"
+msgstr "Marcas XML do DocBook"
+
+#: en_US/xml-tags.xml:16(primary) en_US/xml-tags.xml:34(primary)
+msgid "XML"
+msgstr "XML"
+
+#: en_US/xml-tags.xml:17(secondary)
+msgid "tags"
+msgstr "marcas"
+
+#: en_US/xml-tags.xml:18(see) en_US/xml-tags.xml:167(primary)
+#: en_US/xml-tags.xml:205(primary) en_US/xml-tags.xml:241(primary)
+#: en_US/xml-tags.xml:276(primary) en_US/xml-tags.xml:361(primary)
+#: en_US/xml-tags.xml:386(primary) en_US/xml-tags.xml:417(primary)
+#: en_US/xml-tags.xml:471(primary) en_US/xml-tags.xml:523(primary)
+#: en_US/xml-tags.xml:555(primary) en_US/xml-tags.xml:593(primary)
+#: en_US/xml-tags.xml:659(primary) en_US/xml-tags.xml:667(primary)
+#: en_US/xml-tags.xml:673(primary) en_US/xml-tags.xml:703(primary)
+#: en_US/xml-tags.xml:709(primary) en_US/xml-tags.xml:739(primary)
+#: en_US/xml-tags.xml:745(primary) en_US/xml-tags.xml:774(primary)
+#: en_US/xml-tags.xml:780(primary) en_US/xml-tags.xml:785(primary)
+#: en_US/xml-tags.xml:791(primary) en_US/xml-tags.xml:833(primary)
+#: en_US/xml-tags.xml:861(primary) en_US/xml-tags.xml:908(primary)
+#: en_US/xml-tags.xml:963(primary) en_US/xml-tags.xml:968(primary)
+#: en_US/xml-tags.xml:1037(primary) en_US/xml-tags.xml:1047(primary)
+#: en_US/xml-tags.xml:1124(primary) en_US/xml-tags.xml:1129(primary)
+#: en_US/xml-tags.xml:1219(primary) en_US/xml-tags.xml:1224(primary)
+#: en_US/xml-tags.xml:1402(primary) en_US/xml-tags.xml:1407(primary)
+#: en_US/xml-tags.xml:1490(primary) en_US/xml-tags.xml:1533(primary)
+#: en_US/xml-tags.xml:1642(primary) en_US/xml-tags.xml:1688(primary)
+#: en_US/xml-tags.xml:1738(primary) en_US/xml-tags.xml:1782(primary)
+#: en_US/xml-tags.xml:1812(primary) en_US/xml-tags.xml:1983(primary)
+#: en_US/xml-tags.xml:2055(primary) en_US/xml-tags.xml:2174(primary)
+#: en_US/xml-tags.xml:2313(primary) en_US/xml-tags.xml:2341(primary)
+#: en_US/xml-tags.xml:2396(primary) en_US/xml-tags.xml:2437(primary)
+#: en_US/xml-tags.xml:2484(primary) en_US/writing-guidelines.xml:61(primary)
+#: en_US/writing-guidelines.xml:74(primary)
+#: en_US/writing-guidelines.xml:275(primary)
+#: en_US/writing-guidelines.xml:280(primary)
+#: en_US/writing-guidelines.xml:285(primary)
+#: en_US/writing-guidelines.xml:290(primary)
+#: en_US/writing-guidelines.xml:295(primary)
+#: en_US/writing-guidelines.xml:300(primary)
+#: en_US/writing-guidelines.xml:306(primary)
+#: en_US/writing-guidelines.xml:312(primary)
+#: en_US/writing-guidelines.xml:318(primary)
+#: en_US/writing-guidelines.xml:324(primary)
+#: en_US/writing-guidelines.xml:350(primary)
+#: en_US/writing-guidelines.xml:355(primary)
+#: en_US/writing-guidelines.xml:360(primary)
+#: en_US/writing-guidelines.xml:365(primary)
+#: en_US/writing-guidelines.xml:370(primary)
+msgid "XML tags"
+msgstr "Marcas XML"
+d139 3
+a141 50
+#: en_US/xml-tags.xml:21(para)
+msgid ""
+"Please read this chapter carefully. This chapter describes the tags used by "
+"the Docs Project. Some of the rules described are specific to the project."
+msgstr ""
+"Leia por favor este capítulo com cuidado. O mesmo descreve as marcas usadas "
+"pelo Projecto de Documentação. Algumas das regras aqui descritas são "
+"específicas do projecto."
+
+#: en_US/xml-tags.xml:26(para)
+msgid ""
+"If these tags are used appropriately, document searches will provide "
+"meaningful results. These tags help search engines identify the information "
+"relevant to the search request. Another benefit is that all Fedora Project "
+"documents will have a similar look and feel (however, they will have some "
+"differences depending upon the output format)."
+msgstr ""
+"Se estas marcas forem usadas de forma apropriada, as pesquisas no documento "
+"irão oferecer resultados significativos. Estas marcas ajudam os motores de "
+"busca a identificar a informação relevante para o pedido de pesquisa. Outro "
+"benefício é o facto de todos os documentos do Projecto Fedora terão uma "
+"aparência e comportamento semelhante (contudo, terão algumas diferenças que "
+"dependem do formato de saída)."
+
+#: en_US/xml-tags.xml:35(secondary)
+msgid "general tag information"
+msgstr "informação geral de marcas"
+
+#: en_US/xml-tags.xml:38(para)
+msgid ""
+"Most tags in XML must have an opening and closing tag. A few tags, such as "
+"<sgmltag class=\"emptytag\">xref</sgmltag>, have no content and close "
+"themselves. Additionally, proper XML conventions say that there must be a "
+"unique identifier for sections, chapters, figures, tables, and so on, so "
+"that they may be correctly identified, and cross referenced if needed."
+msgstr ""
+"A maior parte das marcas em XML deverão ter uma marca de abertura e de "
+"fecho. Algumas marcas, como a <sgmltag class=\"emptytag\">xref</sgmltag>, "
+"não têm conteúdo, pelo que se fecham a si próprias. Adicionalmente, as "
+"convenções adequadas em XML dizem que deverá existir um identificador único "
+"para as secções, capítulos, figuras, tabelas, entre outros, para que possam "
+"ser identificadas e refenciadas correctamente se necessário."
+
+#: en_US/xml-tags.xml:45(para)
+msgid ""
+"Although XML is capable of handling many document types, the format "
+"discussed here is the article format."
+msgstr ""
+"Ainda que o XML seja capaz de lidar com muitos tipos de documentos, o "
+"formato aqui discutido é o formato dos artigos."
+d143 1
+a143 1
+#: en_US/xml-tags.xml:48(para) en_US/writing-guidelines.xml:32(para)
+d145 6
+a150 3
+"This chapter only discusses tags used for documentation for the Fedora "
+"Project, not all available DocBook XML tags. For the complete list, refer to "
+"<ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+d152 7
+a158 4
+"Este capítulo só discute as marcas usadas na documentação do Projecto "
+"Fedora, não refere todas as marcas de XML do DocBook. Para uma lista "
+"completa, veja em <ulink url=\"http://www.docbook.org/tdg/en/html/docbook."
+"html\"/>."
+d160 3
+a162 3
+#: en_US/xml-tags.xml:56(title)
+msgid "Tags and Entities Caveats"
+msgstr "Contrapartidas das Marcas e Entidades"
+d164 3
+a166 3
+#: en_US/xml-tags.xml:59(primary) en_US/writing-guidelines.xml:159(primary)
+msgid "xml tags"
+msgstr "marcas em XML"
+d168 32
+a199 4
+#: en_US/xml-tags.xml:60(secondary)
+#: en_US/writing-guidelines.xml:160(secondary)
+msgid "caveats"
+msgstr "contrapartidas"
+d201 1
+a201 1
+#: en_US/xml-tags.xml:63(para)
+d203 6
+a208 3
+"It is very important that you remember the caveats in this section. Even "
+"though they are more strict than valid DocBook XML, these rules exist so "
+"that both the HTML and PDF outputs look proper."
+d210 7
+a216 3
+"É bastante importante que recorde as contrapartidas desta secção. Ainda que "
+"sejam mais restritas que o DocBook em XML válido, estas regras existem para "
+"que os resultados em HTML e PDF apareçam válidos."
+d218 3
+a220 3
+#: en_US/xml-tags.xml:71(term) en_US/writing-guidelines.xml:171(term)
+msgid "Do Not Use Trademark Entities"
+msgstr "Não Use Entidades de Marcas Registadas"
+d222 1
+a222 1
+#: en_US/xml-tags.xml:73(para)
+d224 36
+a259 5
+"Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+"\"genentity\">reg</sgmltag> because they do not produce HTML output that "
+"works for all charsets. The HTML output produces by these entities are "
+"declared in the DTD and cannot be changed via the stylesheet."
+d261 34
+a294 6
+"Não use as entidades de marcas registadas <sgmltag class=\"genentity"
+"\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag> ou <sgmltag "
+"class=\"genentity\">reg</sgmltag>, porque não produzem HTML válido que "
+"funcione em todas as codificações de caracteres. O resultado em HTML "
+"produzido por estas entidades está descrito na DTD e não pode ser alterado "
+"com a folha de estilo."
+d296 1
+a296 1
+#: en_US/xml-tags.xml:80(para)
+d298 4
+a301 2
+"Instead, use the <sgmltag class=\"element\">trademark</sgmltag> tag and its "
+"associates classes as follows:"
+d303 12
+a314 2
+"Em vez disso, use a marca <sgmltag class=\"element\">trademark</sgmltag> e "
+"as suas classes associadas, como se segue:"
+d316 1
+a316 1
+#: en_US/xml-tags.xml:85(para)
+d318 3
+a320 2
+"<sgmltag class=\"starttag\">trademark</sgmltag>trademark symbol after "
+"me<sgmltag class=\"endtag\">trademark</sgmltag>"
+d322 3
+a324 2
+"<sgmltag class=\"starttag\">trademark</sgmltag>símbolo de marca a seguir a "
+"mim<sgmltag class=\"endtag\">trademark</sgmltag>"
+d326 1
+a326 1
+#: en_US/xml-tags.xml:91(para)
+d328 2
+a329 3
+"<sgmltag class=\"starttag\">trademark class=\"registered\"</"
+"sgmltag>registered trademark symbol after me<sgmltag class=\"endtag"
+"\">trademark</sgmltag>"
+d331 6
+a336 3
+"<sgmltag class=\"starttag\">trademark class=\"registered\"</sgmltag>símbolo "
+"de marca registada a seguir a mim<sgmltag class=\"endtag\">trademark</"
+"sgmltag>"
+d338 1
+a338 1
+#: en_US/xml-tags.xml:97(para)
+d340 4
+a343 2
+"<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag>copyright "
+"symbol after me<sgmltag class=\"endtag\">trademark</sgmltag>"
+d345 4
+a348 3
+"<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag>símbolo "
+"de direitos de cópia a seguir a mim<sgmltag class=\"endtag\">trademark</"
+"sgmltag>"
+d350 3
+a352 3
+#: en_US/xml-tags.xml:105(term) en_US/writing-guidelines.xml:209(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr "Conteúdo dentro das marcas <sgmltag>para</sgmltag>"
+d354 1
+a354 1
+#: en_US/xml-tags.xml:107(para)
+d356 4
+a359 3
+"Do not use <sgmltag>para</sgmltag> tags around anything other than a simple "
+"paragraph. Doing so will create additional white space within the text "
+"itself in the PDF version."
+d361 5
+a365 3
+"Não use as marcas <sgmltag>para</sgmltag> em torno de tudo o que não seja um "
+"parágrafo simples. Ao fazê-lo, irá criar espaços em branco adicionais dentro "
+"do próprio texto, na versão em PDF."
+d367 3
+a369 9
+#: en_US/xml-tags.xml:112(para)
+msgid ""
+"Specifically, do not use <sgmltag>para</sgmltag> tags around the following "
+"(or, to put this another way, do not embed the following within "
+"<sgmltag>para</sgmltag> tags):"
+msgstr ""
+"Especificamente, não use as marcas <sgmltag>para</sgmltag> em torno do "
+"seguinte (ou, posto de outra forma, não incorpore o seguinte dentro das "
+"marcas <sgmltag>para</sgmltag>):"
+d371 3
+a373 5
+#: en_US/xml-tags.xml:118(sgmltag) en_US/xml-tags.xml:1810(command)
+#: en_US/xml-tags.xml:1813(secondary)
+#: en_US/writing-guidelines.xml:223(sgmltag)
+msgid "screen"
+msgstr "screen"
+d375 3
+a377 5
+#: en_US/xml-tags.xml:121(sgmltag) en_US/xml-tags.xml:960(command)
+#: en_US/xml-tags.xml:964(command) en_US/xml-tags.xml:970(tertiary)
+#: en_US/xml-tags.xml:975(command) en_US/writing-guidelines.xml:226(sgmltag)
+msgid "itemizedlist"
+msgstr "itemizedlist"
+d379 3
+a381 5
+#: en_US/xml-tags.xml:124(sgmltag) en_US/xml-tags.xml:1038(command)
+#: en_US/xml-tags.xml:1043(command) en_US/xml-tags.xml:1049(tertiary)
+#: en_US/writing-guidelines.xml:229(sgmltag)
+msgid "orderedlist"
+msgstr "orderedlist"
+d383 3
+a385 5
+#: en_US/xml-tags.xml:127(sgmltag) en_US/xml-tags.xml:1125(command)
+#: en_US/xml-tags.xml:1131(tertiary) en_US/xml-tags.xml:1136(command)
+#: en_US/writing-guidelines.xml:232(sgmltag)
+msgid "variablelist"
+msgstr "variablelist"
+d387 3
+a389 6
+#: en_US/xml-tags.xml:130(sgmltag) en_US/xml-tags.xml:2052(command)
+#: en_US/xml-tags.xml:2056(secondary) en_US/xml-tags.xml:2175(secondary)
+#: en_US/writing-guidelines.xml:131(sgmltag)
+#: en_US/writing-guidelines.xml:235(sgmltag)
+msgid "table"
+msgstr "table"
+d391 1
+a391 1
+#: en_US/xml-tags.xml:136(term)
+d393 4
+a396 2
+"Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+"sgmltag> tags"
+d398 8
+a405 2
+"Conteúdo dentro das marcas <sgmltag>para</sgmltag> dentro de marcas "
+"<sgmltag>listitem</sgmltag>"
+d407 1
+a407 1
+#: en_US/xml-tags.xml:139(para)
+d409 4
+a412 4
+"Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+"sgmltag> tags <emphasis>must</emphasis> start immediately after the "
+"beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra "
+"white space in the PDF version."
+d414 5
+a418 4
+"O conteúdo dentro das marcas <sgmltag>para</sgmltag> inseridas em marcas "
+"<sgmltag>listitem</sgmltag> <emphasis>deverá</emphasis> começar logo a "
+"seguir à marca inicial <sgmltag class=\"starttag\">para</sgmltag>, para "
+"evitar espaços em branco extra na versão em PDF."
+d420 3
+a422 3
+#: en_US/xml-tags.xml:148(term) en_US/writing-guidelines.xml:252(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr "Conteúdo dentro das marcas <sgmltag>screen</sgmltag>"
+d424 1
+a424 1
+#: en_US/xml-tags.xml:150(para) en_US/writing-guidelines.xml:254(para)
+d426 5
+a430 4
+"The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag"
+"\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis> be flush left in the XML file; otherwise, the "
+"extraneous whitespace will appear in the HTML version."
+d432 5
+a436 5
+"O conteúdo dentro das marcas <sgmltag>screen</sgmltag> (<sgmltag class="
+"\"starttag\">screen</sgmltag> e <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>deverão</emphasis> ser retirados à esquerda no ficheiro em XML; "
+"caso contrário, os espaços em branco estranhos irão aparecer na versão em "
+"HTML."
+d438 3
+a440 5
+#: en_US/xml-tags.xml:164(sgmltag) en_US/xml-tags.xml:168(secondary)
+#: en_US/xml-tags.xml:182(sgmltag) en_US/xml-tags.xml:183(sgmltag)
+#: en_US/xml-tags.xml:184(sgmltag) en_US/xml-tags.xml:185(sgmltag)
+msgid "application"
+msgstr "application"
+d442 3
+a444 7
+#: en_US/xml-tags.xml:171(para)
+msgid ""
+"An application is the name of a GUI software program. A command is the name "
+"of an executable (text) program or a software command."
+msgstr ""
+"Uma aplicação é o nome de um programa de 'software' gráfico. Um comando é o "
+"nome de um programa executável (em texto) ou um comando do sistema."
+d446 3
+a448 9
+#: en_US/xml-tags.xml:174(para)
+msgid ""
+"The <sgmltag class=\"starttag\">application</sgmltag> and <sgmltag class="
+"\"endtag\">application</sgmltag> tags allow you to refer to an application "
+"or program. For example, the following XML:"
+msgstr ""
+"As marcas <sgmltag class=\"starttag\">application</sgmltag> e <sgmltag class="
+"\"endtag\">application</sgmltag> permitem-lhe referenciar uma aplicação ou "
+"um programa. Por exemplo, o seguinte XML:"
+d450 3
+a452 14
+#: en_US/xml-tags.xml:180(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To view the Web in Linux, you can use\n"
+"<placeholder-1/>Mozilla<placeholder-2/> \n"
+"or <placeholder-3/>lynx<placeholder-4/> if\n"
+"you only want a text-based browser.\n"
+msgstr ""
+"\n"
+"Para ver a Web no Linux, pode usar o\n"
+"<placeholder-1/>Mozilla<placeholder-2/> \n"
+"ou o <placeholder-3/>lynx<placeholder-4/>,\n"
+"se só quiser um navegador em modo texto.\n"
+d454 3
+a456 3
+#: en_US/xml-tags.xml:190(para)
+msgid "produces the following output:"
+msgstr "produz o seguinte resultado:"
+d458 1
+a458 1
+#: en_US/xml-tags.xml:194(para)
+d460 5
+a464 2
+"To view the Web in Linux, you can use <application>Mozilla</application> or "
+"<application>lynx</application> if you only want a text-based browser."
+d466 6
+a471 2
+"Para ver a Web no Linux, poderá usar o <application>Mozilla</application> ou "
+"o <application>lynx</application> se só quiser um navegador em modo texto."
+d473 3
+a475 4
+#: en_US/xml-tags.xml:202(sgmltag) en_US/xml-tags.xml:206(secondary)
+#: en_US/writing-guidelines.xml:119(sgmltag)
+msgid "chapter"
+msgstr "chapter"
+d477 6
+a482 2
+#: en_US/xml-tags.xml:209(para)
+msgid "A DocBook book can be divided into chapters such as:"
+d484 5
+a488 1
+"Um livro em DocBook poderá ser dividido em capítulos como os seguintes:"
+d490 1
+a490 2
+#: en_US/xml-tags.xml:214(computeroutput)
+#, no-wrap
+d492 4
+a495 10
+"\n"
+"<!--$Id: pt.po,v 1.14 2007/07/21 15:11:14 zepires Exp $ -->\n"
+"\n"
+" <chapter id=\"ch-sample\">\n"
+" <title>Sample Chapter</title>\n"
+"\n"
+" <para>This is a sample chapter, showing you the XML tags used to create a\n"
+" chapter, sections, and subsections.</para>\n"
+" \n"
+" </chapter>\n"
+d497 4
+a500 10
+"\n"
+"<!--$Id: pt.po,v 1.14 2007/07/21 15:11:14 zepires Exp $ -->\n"
+"\n"
+" <chapter id=\"cap-exemplo\">\n"
+" <title>Capítulo de Exemplo</title>\n"
+"\n"
+" <para>Este é um capítulo de exemplo, que lhe mostra as marcas \n"
+" em XML usadas para criar um capítulo, secções e sub-secções.</para>\n"
+" \n"
+" </chapter>\n"
+d502 2
+a503 1
+#: en_US/xml-tags.xml:227(para)
+d505 8
+a512 3
+"The chapter can also be further divided into sections (<sgmltag>section</"
+"sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). Refer "
+"to <xref linkend=\"sn-xml-tags-sections\"/> for details."
+d514 9
+a522 3
+"O capítulo poderá também ser dividido em secções (<sgmltag>section</"
+"sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). Veja "
+"mais detalhes em <xref linkend=\"sn-xml-tags-sections\"/>."
+d524 1
+a524 6
+#: en_US/xml-tags.xml:238(sgmltag) en_US/xml-tags.xml:242(secondary)
+#: en_US/xml-tags.xml:262(sgmltag)
+msgid "citetitle"
+msgstr "citetitle"
+
+#: en_US/xml-tags.xml:249(para)
+d526 7
+a532 3
+"An entity is a short hand way of referring to some predefined content, such "
+"as a title or name. It can be defined within the parent document or within a "
+"set of files that your DTD references for your specific documentation set."
+d534 11
+a544 4
+"Um entidade é uma forma resumida de fazer referẽncia a algum conteúdo "
+"predefinido, como um título ou um nome. Poderá ser definida dentro do "
+"documento-pai ou dentro de um conjunto de ficheiros que a sua DTD faça "
+"referência, para o seu conjunto de documentação específico."
+d546 6
+a551 1
+#: en_US/xml-tags.xml:246(para)
+d553 4
+a556 3
+"The <sgmltag>citetitle</sgmltag> tag provides formatting for a specific "
+"references (title can be manually typed out or if already defined within "
+"your document set, given as an entity<footnote><placeholder-1/></footnote> )."
+d558 4
+a561 4
+"A marca <sgmltag>citetitle</sgmltag> produz a formatação para uma referência "
+"específica (o título poderá ser escrito manualmente ou, se já estiver "
+"definido dentro do seu conjunto de documentos, indicado como uma "
+"entidade<footnote><placeholder-1/></footnote> )."
+d563 3
+a565 3
+#: en_US/xml-tags.xml:257(para) en_US/xml-tags.xml:2456(para)
+msgid "For example:"
+msgstr "Por exemplo:"
+d567 2
+a568 6
+#: en_US/xml-tags.xml:262(sgmltag)
+msgid "IG"
+msgstr "IG"
+
+#: en_US/xml-tags.xml:261(computeroutput)
+#, no-wrap
+d570 5
+a574 2
+"\n"
+"<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+d576 5
+a580 2
+"\n"
+"<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+d582 1
+a582 1
+#: en_US/xml-tags.xml:265(para)
+d584 4
+a587 2
+"The output looks like <citetitle>Installation Guide</citetitle> because "
+"<sgmltag class=\"genentity\">IG</sgmltag> is an entity."
+d589 4
+a592 2
+"O resultado fica semelhante a <citetitle>Guia de Instalação</citetitle>, "
+"porque o <sgmltag class=\"genentity\">IG</sgmltag> é uma entidade."
+d594 1
+a594 5
+#: en_US/xml-tags.xml:273(sgmltag) en_US/xml-tags.xml:277(secondary)
+msgid "command"
+msgstr "command"
+
+#: en_US/xml-tags.xml:280(para)
+d596 8
+a603 4
+"An application is the name of a GUI software program. A command is the name "
+"of an executable (text) program or a software command. Any program that is a "
+"command line or text-based only tool is marked with <sgmltag>command</"
+"sgmltag> tags."
+d605 9
+a613 4
+"Uma aplicação é o nome de um programa de 'software' gráfico. Um comando é o "
+"nome de um programa executável (em texto) ou um comando do sistema. Todos os "
+"programas que sejam ferramentas da linha de comandos ou apenas para modo "
+"texto são marcados com as marcas <sgmltag>command</sgmltag>."
+d615 1
+a615 1
+#: en_US/xml-tags.xml:286(para)
+d617 4
+a620 3
+"If you have text that is a command, use the <sgmltag class=\"starttag"
+"\">command</sgmltag> and <sgmltag class=\"endtag\">command</sgmltag> tags "
+"such as:"
+d622 5
+a626 3
+"Se tiver texto que seja um comando, use as marcas <sgmltag class=\"starttag"
+"\">command</sgmltag> e <sgmltag class=\"endtag\">command</sgmltag>, como no "
+"exemplo:"
+d628 1
+a628 2
+#: en_US/xml-tags.xml:294(computeroutput)
+#, no-wrap
+d630 3
+a632 4
+"\n"
+"To change your keyboard after installation, become root \n"
+"and use the <command>redhat-config-keyboard</command> command, \n"
+"or you can type <command>setup</command> at the root prompt.\n"
+d634 3
+a636 33
+"\n"
+"Para mudar o seu teclado após a instalação, torne-se 'root'\n"
+"e use o comando <command>redhat-config-keyboard</command>,\n"
+"ou então escreva o comando <command>setup</command> na linha de comandos do 'root'.\n"
+
+#: en_US/xml-tags.xml:301(para) en_US/xml-tags.xml:374(para)
+#: en_US/xml-tags.xml:402(para) en_US/xml-tags.xml:446(para)
+#: en_US/xml-tags.xml:485(para) en_US/xml-tags.xml:500(para)
+#: en_US/xml-tags.xml:540(para) en_US/xml-tags.xml:575(para)
+#: en_US/xml-tags.xml:689(para) en_US/xml-tags.xml:725(para)
+#: en_US/xml-tags.xml:759(para) en_US/xml-tags.xml:816(para)
+#: en_US/xml-tags.xml:849(para) en_US/xml-tags.xml:887(para)
+#: en_US/xml-tags.xml:927(para) en_US/xml-tags.xml:1515(para)
+#: en_US/xml-tags.xml:1756(para) en_US/xml-tags.xml:1800(para)
+#: en_US/xml-tags.xml:1868(para) en_US/xml-tags.xml:2357(para)
+#: en_US/xml-tags.xml:2411(para) en_US/xml-tags.xml:2464(para)
+#: en_US/xml-tags.xml:2504(para)
+msgid "The output:"
+msgstr "O resultado:"
+
+#: en_US/xml-tags.xml:304(para)
+msgid ""
+"To change your keyboard after installation, become root and use the "
+"<command>redhat-config-keyboard</command> command, or you can type "
+"<command>setup</command> at the root prompt."
+msgstr ""
+"Para mudar o seu teclado após a instalação, torne-se 'root' e use o comando "
+"<command>redhat-config-keyboard</command> ou então escreva o comando "
+"<command>setup</command> na linha de comandos do 'root'."
+
+#: en_US/xml-tags.xml:310(para)
+msgid "Another example would be:"
+msgstr "Outro exemplo seria:"
+d638 1
+a638 2
+#: en_US/xml-tags.xml:313(computeroutput)
+#, no-wrap
+d640 4
+a643 6
+"\n"
+"<command>MAILNOVIOLATIONS</command> — If set\n"
+"to <command>true</command> this option tells Tripwire to\n"
+"email a report at a regular interval regardless of whether or not\n"
+"any violations have occured. The default value is\n"
+"<command>true</command>.\n"
+d645 4
+a648 32
+"\n"
+"<command>MAILNOVIOLATIONS</command> — Se estiver\n"
+"definido como <command>true</command>, esta opção indica\n"
+"ao Tripwire para enviar por e-mail um relatório com um intervalo regular,\n"
+"independentemente das violações que tiverem ocorrido. O valor por omissão\n"
+"é <command>true</command>.\n"
+
+#: en_US/xml-tags.xml:322(para)
+msgid "with the output:"
+msgstr "com o resultado:"
+
+#: en_US/xml-tags.xml:326(para)
+msgid ""
+"<command>MAILNOVIOLATIONS</command>— If set to <command>true</command> "
+"this variable tells Tripwire to email a report at a regular interval "
+"regardless of whether or not any violations have occured. The default value "
+"is <command>true</command>."
+msgstr ""
+"<command>MAILNOVIOLATIONS</command> — Se estiver definido como "
+"<command>true</command>, esta opção indica ao Tripwire para enviar por e-"
+"mail um relatório com um intervalo regular, independentemente das violações "
+"que tiverem ocorrido. O valor por omissão é <command>true</command>."
+
+#: en_US/xml-tags.xml:334(title) en_US/xml-tags.xml:509(title)
+#: en_US/xml-tags.xml:988(title) en_US/xml-tags.xml:1063(title)
+#: en_US/xml-tags.xml:1147(title) en_US/xml-tags.xml:1387(title)
+#: en_US/xml-tags.xml:1500(title) en_US/xml-tags.xml:1769(title)
+#: en_US/xml-tags.xml:1930(title) en_US/xml-tags.xml:2422(title)
+#: en_US/writing-guidelines.xml:403(title) en_US/emacs.xml:257(title)
+#: en_US/emacs.xml:557(title) en_US/emacs-nxml.xml:160(title)
+msgid "Note"
+msgstr "Nota"
+d650 1
+a650 1
+#: en_US/xml-tags.xml:334(para)
+d652 3
+a654 42
+"In this example, the option value (true) is defined with a <command> "
+"tag set. Because a option is a configuration file option (command line "
+"options which would use the <option> tag set), and because there is no "
+"configuration file option tag available to use, we are extending the <"
+"command> tag set to define options in a configuration file."
+msgstr ""
+"Neste exemplo, o valor de 'option' ('true') está definido com uma marca <"
+"command> atribuída. Dado que uma 'option' é uma opção do ficheiro de "
+"configuração (as opções das linhas de comandos devem usar a marca <"
+"option>), e dado que não existe nenhuma marca de opção de ficheiros de "
+"configuração para usar, será extendida a marca <command> para definir "
+"opções num ficheiro de configuração."
+
+#: en_US/xml-tags.xml:342(para)
+msgid ""
+"Terms marked with <command>command</command> tags because there aren't exact "
+"tags for them:"
+msgstr ""
+"Os termos marcados como <command>command</command>, porque não existem "
+"marcas exactas para eles:"
+
+#: en_US/xml-tags.xml:348(para)
+msgid "Options in configuration files such as Apache directives"
+msgstr "As opções nos ficheiros de configuração, como as directivas do Apache"
+
+#: en_US/xml-tags.xml:351(para)
+msgid "daemon names"
+msgstr "nomes de servidores"
+
+#: en_US/xml-tags.xml:358(command) en_US/xml-tags.xml:362(secondary)
+msgid "computeroutput"
+msgstr "computeroutput"
+
+#: en_US/xml-tags.xml:365(para)
+msgid "To show computer output use the following tags:"
+msgstr "Para mostrar o resultado do computador, use as seguintes marcas:"
+
+#: en_US/xml-tags.xml:369(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<computeroutput>Do you want to delete this file? y n</computeroutput>\n"
+d656 3
+a658 2
+"\n"
+"<computeroutput>Deseja remover este ficheiro? s n</computeroutput>\n"
+d660 1
+a660 10
+#: en_US/xml-tags.xml:378(computeroutput)
+#, no-wrap
+msgid "Do you really want to delete this file? y n"
+msgstr "Deseja remover este ficheiro? s n"
+
+#: en_US/xml-tags.xml:383(command) en_US/xml-tags.xml:387(secondary)
+msgid "emphasis"
+msgstr "emphasis"
+
+#: en_US/xml-tags.xml:390(para)
+d662 3
+a664 2
+"To emphasis content, use the <command><emphasis></command> and "
+"<command></emphasis></command> tags. For example:"
+d666 3
+a668 2
+"Para aumentar a ênfase sobre o conteúdo, use as marcas <command><"
+"emphasis></command> e <command></emphasis></command>. Por exemplo:"
+d670 1
+a670 2
+#: en_US/xml-tags.xml:395(computeroutput)
+#, no-wrap
+d672 6
+a677 4
+"\n"
+"This installation <emphasis>will remove all</emphasis> existing\n"
+"Linux partitions on <emphasis>all</emphasis> hard drives in your\n"
+"system; non-Linux partitions will not be removed.\n"
+d679 7
+a685 15
+"\n"
+"Esta instalação <emphasis> irá remover todas as </emphasis> \n"
+"partições de Linux existentes em\n"
+"<emphasis>todos</emphasis> os discos rígidos do seu sistema;\n"
+"as partições não-Linux não serão removidas.\n"
+
+#: en_US/xml-tags.xml:406(para)
+msgid ""
+"This installation <emphasis>will remove all</emphasis> existing Linux "
+"partitions on <emphasis>all</emphasis> hard drives in your system; non-Linux "
+"partitions will not be removed."
+msgstr ""
+"Esta instalação <emphasis> irá remover todas as </emphasis>partições de "
+"Linux existentes em <emphasis>todos</emphasis> os discos rígidos do seu "
+"sistema; as partições não-Linux não serão removidas."
+d687 3
+a689 4
+#: en_US/xml-tags.xml:414(command) en_US/xml-tags.xml:418(secondary)
+#: en_US/writing-guidelines.xml:143(sgmltag)
+msgid "example"
+msgstr "example"
+d691 3
+a693 10
+#: en_US/xml-tags.xml:421(para)
+msgid ""
+"The <command><example></command> and <command></example></"
+"command> tags are used to format text within a document and is great for "
+"adding emphasis to show examples of code, exercises, and more."
+msgstr ""
+"As marcas <command><example></command> e <command></example></"
+"command> são usadas para formatar o texto dentro de um documento e são "
+"óptimas para adicionar alguma enfâse sobre exemplos de código, exercícios, "
+"entre outros."
+d695 3
+a697 7
+#: en_US/xml-tags.xml:426(para)
+msgid ""
+"The <command><example></command> tag set should be given an ID and "
+"title:"
+msgstr ""
+"A marca <command><example></command> definida deverá ter um ID e um "
+"título:"
+d699 5
+a703 2
+#: en_US/xml-tags.xml:429(screen)
+#, no-wrap
+d705 2
+a706 15
+"\n"
+"\t<example id=\"static-ip\">\n"
+"\t <title>Static IP Address using DHCP</title>\n"
+"\n"
+"<screen width=60>\n"
+"<computeroutput>\n"
+"host apex {\n"
+" option host-name \"apex.example.com\";\n"
+" hardware ethernet 00:A0:78:8E:9E:AA; \n"
+" fixed-address 192.168.1.4;\n"
+"}\n"
+"<computeroutput>\n"
+"</screen>\n"
+"\n"
+"\t</example>\n"
+d708 2
+a709 15
+"\n"
+"\t<example id=\"ip-estatico\">\n"
+"\t <title>Endereço IP Estático com o DHCP</title>\n"
+"\n"
+"<screen width=60>\n"
+"<computeroutput>\n"
+"host ze {\n"
+" option host-name \"ze.exemplo.com\";\n"
+" hardware ethernet 00:A0:78:8E:9E:AA; \n"
+" fixed-address 192.168.1.4;\n"
+"}\n"
+"<computeroutput>\n"
+"</screen>\n"
+"\n"
+"\t</example>\n"
+d711 3
+a713 3
+#: en_US/xml-tags.xml:451(title)
+msgid "Static IP Address using DHCP"
+msgstr "Endereço IP Estático com o DHCP"
+d715 1
+a715 2
+#: en_US/xml-tags.xml:454(computeroutput)
+#, no-wrap
+d717 3
+a719 6
+"\n"
+"host apex {\n"
+" option host-name \"apex.example.com\";\n"
+" hardware ethernet 00:A0:78:8E:9E:AA; \n"
+" fixed-address 192.168.1.4;\n"
+"}\n"
+d721 3
+a723 22
+"\n"
+"host ze {\n"
+" option host-name \"ze.exemplo.com\";\n"
+" hardware ethernet 00:A0:78:8E:9E:AA; \n"
+" fixed-address 192.168.1.4;\n"
+"}\n"
+
+#: en_US/xml-tags.xml:468(command) en_US/xml-tags.xml:472(secondary)
+msgid "filename"
+msgstr "filename"
+
+#: en_US/xml-tags.xml:475(para)
+msgid ""
+"The <command><filename></command> and <command></filename></"
+"command> tags define a filename or path to a file. Since directories are "
+"just special files, they are marked with the <command>filename</command> "
+"tags as well. For example:"
+msgstr ""
+"As marcas <command><filename></command> e <command></filename></"
+"command> definem o nome ou o local de um ficheiro. Dado que as pastas são "
+"ficheiros especiais, são marcadas também com o <command>filename</command>. "
+"Por exemplo:"
+d725 3
+a727 10
+#: en_US/xml-tags.xml:481(screen)
+#, no-wrap
+msgid ""
+"\n"
+"Edit the <filename>/home/smoore/sam.xml</filename> file to make\n"
+"changes or add comments.\n"
+msgstr ""
+"\n"
+"Edite o ficheiro <filename>/home/ze/nuno.xml</filename> para\n"
+"fazer alterações ou adicionar comentários.\n"
+d729 1
+a729 1
+#: en_US/xml-tags.xml:488(para)
+d731 2
+a732 2
+"Edit the <filename>/home/smoore/sam.xml</filename> file to make changes or "
+"add comments."
+d734 2
+a735 2
+"Edite o ficheiro <filename>/home/ze/nuno.xml</filename> para fazer "
+"alterações ou adicionar comentários."
+d737 3
+a739 3
+#: en_US/xml-tags.xml:493(para)
+msgid "They are also used to markup an RPM package name. For example:"
+msgstr "São também usadas para formatar o nome de um pacote RPM. Por exemplo:"
+d741 1
+a741 2
+#: en_US/xml-tags.xml:496(screen)
+#, no-wrap
+d743 2
+a744 3
+"\n"
+"To use the <application>Keyboard Configuration Tool</application>, the\n"
+"<filename>system-config-keyboard</filename> RPM package must be installed.\n"
+d746 2
+a747 3
+"\n"
+"Para usar a <application>Ferramenta de Configuração do Teclado</application>, o pacote RPM\n"
+"<filename>system-config-keyboard</filename> deverá estar instalado.\n"
+d749 3
+a751 8
+#: en_US/xml-tags.xml:503(para)
+msgid ""
+"To use the <application>Keyboard Configuration Tool</application>, the "
+"<command>redhat-config-keyboard</command> RPM package must be installed."
+msgstr ""
+"Para usar a <application>Ferramenta de Configuração do Teclado</"
+"application>, o pacote RPM <filename>system-config-keyboard</filename> "
+"deverá estar instalado."
+d753 1
+a753 1
+#: en_US/xml-tags.xml:510(para)
+d755 3
+a757 2
+"Directory names must end with a forward slash (<computeroutput>/</"
+"computeroutput>) to distinguish them from file names."
+d759 3
+a761 2
+"Os nomes das pastas deverão terminar com uma barra (<computeroutput>/</"
+"computeroutput>) para os distinguir dos nomes dos ficheiros."
+d763 3
+a765 3
+#: en_US/xml-tags.xml:520(command) en_US/xml-tags.xml:524(secondary)
+msgid "firstterm"
+msgstr "firstterm"
+d767 1
+a767 1
+#: en_US/xml-tags.xml:527(para)
+d769 2
+a770 3
+"The <command><firstterm></command> and <command></firstterm></"
+"command> tags helps to define a word that may be unfamiliar to the user, but "
+"that will be seen commonly throughout the text. For example:"
+d772 3
+a774 3
+"As marcas <command><firstterm></command> e <command></firstterm>"
+"</command> ajudam a definir uma palavra que possa não parecer familiar ao "
+"utilizador, mas que aparecerá frequentemente ao longo do texto. Por exemplo:"
+d776 3
+a778 10
+#: en_US/xml-tags.xml:534(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Nearly every modern-day operating system uses <firstterm>disk\n"
+"partitions</firstterm>, and Fedora is no exception.\n"
+msgstr ""
+"\n"
+"Praticamente todos os sistemas operativos modernos usam as\n"
+"<firstterm>partições de disco</firstterm> e o Fedora não é excepção.\n"
+d780 1
+a780 1
+#: en_US/xml-tags.xml:544(para)
+d782 3
+a784 2
+"Nearly every modern-day operating system uses <firstterm>disk partitions</"
+"firstterm>, and Fedora is no exception."
+d786 3
+a788 2
+"Praticamente todos os sistemas operativos modernos usam as "
+"<firstterm>partições de disco</firstterm> e o Fedora não é excepção."
+d790 3
+a792 3
+#: en_US/xml-tags.xml:552(command) en_US/xml-tags.xml:556(secondary)
+msgid "footnote"
+msgstr "footnote"
+d794 1
+a794 6
+#: en_US/xml-tags.xml:559(para)
+msgid "If you need to make a footnote, use the following example:"
+msgstr "Se precisar de criar uma nota de rodapé, use o seguinte exemplo:"
+
+#: en_US/xml-tags.xml:563(computeroutput)
+#, no-wrap
+d796 2
+a797 9
+"\n"
+"For those of you who need to perform a server-class\n"
+"<footnote>\n"
+"<para>\n"
+"A server-class installation sets up a typical server\n"
+"environment. Note, no graphical environment is \n"
+"installed during a server-class installation.\n"
+"</para> \n"
+"</footnote> installation, refer to the <citetitle>Installation Guide</citetitle>.\n"
+d799 3
+a801 29
+"\n"
+"Para os que precisam de efectuar uma instalação para servidores\n"
+"<footnote>\n"
+"<para>\n"
+"Uma instalação para servidores configura um ambiente\n"
+"típico de servidores. Como nota, não é instalado nenhum\n"
+"ambiente gráfico durante uma instalação para servidores.\n"
+"</para> \n"
+"</footnote>, veja no <citetitle>Guia de Instalação</citetitle>.\n"
+
+#: en_US/xml-tags.xml:580(para)
+msgid ""
+"A server-class installation sets up a typical server environment. Please "
+"note, no graphical environment is installed during a server-class "
+"installation."
+msgstr ""
+"Uma instalação para servidores configura um ambiente típico de servidores. "
+"Como nota, não é instalado nenhum ambiente gráfico durante uma instalação "
+"para servidores."
+
+#: en_US/xml-tags.xml:579(para)
+msgid ""
+"For those of you who need to perform a server-class <footnote><placeholder-1/"
+"></footnote> installation, refer to the <citetitle>Installation Guide</"
+"citetitle>."
+msgstr ""
+"Para os que precisam de efectuar uma instalação para servidores "
+"<footnote><placeholder-1/></footnote>, veja no <citetitle>Guia de "
+"Instalação</citetitle>."
+d803 3
+a805 4
+#: en_US/xml-tags.xml:590(command) en_US/xml-tags.xml:594(secondary)
+#: en_US/writing-guidelines.xml:127(sgmltag)
+msgid "figure"
+msgstr "figure"
+d807 3
+a809 4
+#: en_US/xml-tags.xml:598(title) en_US/xml-tags.xml:1827(title)
+#: en_US/writing-guidelines.xml:433(title) en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr "Importante"
+d811 3
+a813 6
+#: en_US/xml-tags.xml:599(para)
+msgid ""
+"Order matters! The EPS file <emphasis>must</emphasis> be declared first."
+msgstr ""
+"A ordem importa! O ficheiro EPS <emphasis>deverá</emphasis> estar declarado "
+"primeiro."
+d815 3
+a817 3
+#: en_US/xml-tags.xml:605(para)
+msgid "An example figure declaration:"
+msgstr "Uma declaração de exemplo de figuras:"
+d819 1
+a819 2
+#: en_US/xml-tags.xml:610(computeroutput)
+#, no-wrap
+d821 3
+a823 19
+"\n"
+"<figure id=\"fig-ksconfig-basic\">\n"
+" <title>Basic Configuration</title>\n"
+" <mediaobject>\n"
+" <imageobject>\n"
+" <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.eps\"\n"
+" format=\"EPS\"/>\n"
+" </imageobject>\n"
+" <imageobject>\n"
+" <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.png\"\n"
+" format=\"PNG\"/>\n"
+" </imageobject>\n"
+" <textobject>\n"
+" <phrase>\n"
+" Some text description of this image\n"
+" </phrase>\n"
+" </textobject>\n"
+" </mediaobject>\n"
+"</figure>\n"
+d825 3
+a827 43
+"\n"
+"<figure id=\"fig-config-basica\">\n"
+" <title>Configuração Básica</title>\n"
+" <mediaobject>\n"
+" <imageobject>\n"
+" <imagedata fileref=\"./figs/ksconfig/config-basica.eps\"\n"
+" format=\"EPS\"/>\n"
+" </imageobject>\n"
+" <imageobject>\n"
+" <imagedata fileref=\"./figs/ksconfig/config-basica.png\"\n"
+" format=\"PNG\"/>\n"
+" </imageobject>\n"
+" <textobject>\n"
+" <phrase>\n"
+" Alguma descrição em texto desta imagem\n"
+" </phrase>\n"
+" </textobject>\n"
+" </mediaobject>\n"
+"</figure>\n"
+
+#: en_US/xml-tags.xml:632(para)
+msgid "The following describes what needs to be edited:"
+msgstr "Os itens seguintes descrevem o que é necessário editar:"
+
+#: en_US/xml-tags.xml:637(emphasis)
+msgid "==> id=\"\" would be edited"
+msgstr "==> o id=\"\" seria editado"
+
+#: en_US/xml-tags.xml:639(emphasis)
+msgid "==> title would be edited"
+msgstr "==> o título seria editado"
+
+#: en_US/xml-tags.xml:641(emphasis)
+msgid "==> .eps location would be edited"
+msgstr "==> a localização do ficheiro .eps seria editada"
+
+#: en_US/xml-tags.xml:643(emphasis)
+msgid "==> .png location would be edited"
+msgstr "==> a localização do ficheiro .png seria editada"
+
+#: en_US/xml-tags.xml:645(emphasis)
+msgid "==> \"Some text...\" would be edited"
+msgstr "==> O \"Algum texto...\" seria editado"
+d829 3
+a831 24
+#: en_US/xml-tags.xml:636(screen)
+#, no-wrap
+msgid ""
+"\n"
+"<figure id=\"fig-ksconfig-basic\"> <placeholder-1/>\n"
+"\n"
+"<title>Basic Configuration</title> <placeholder-2/>\n"
+"\n"
+"fileref=\"./figs/ksconfig/ksconfig-basics.eps\"> <placeholder-3/>\n"
+"\n"
+"fileref=\"./figs/ksconfig/ksconfig-basics.png\"> <placeholder-4/>\n"
+" \n"
+"<phrase>Some text description of this image</phrase> <placeholder-5/>\n"
+msgstr ""
+"\n"
+"<figure id=\"fig-config-basica\"> <placeholder-1/>\n"
+"\n"
+"<title>Configuração Básica</title> <placeholder-2/>\n"
+"\n"
+"fileref=\"./figs/ksconfig/config-basica.eps\"> <placeholder-3/>\n"
+"\n"
+"fileref=\"./figs/ksconfig/config-basica.png\"> <placeholder-4/>\n"
+" \n"
+"<phrase>Alguma descrição em texto desta imagem</phrase> <placeholder-5/>\n"
+d833 1
+a833 1
+#: en_US/xml-tags.xml:648(para)
+d835 2
+a836 2
+"For more information on taking screenshots, refer to <xref linkend=\"sn-"
+"screenshots\"/>."
+d838 2
+a839 2
+"Para mais informações sobre como tirar fotografias, veja em <xref linkend="
+"\"sn-screenshots\"/>."
+d841 3
+a843 3
+#: en_US/xml-tags.xml:656(title)
+msgid "GUI Tags"
+msgstr "Marcas GUI"
+d845 3
+a847 5
+#: en_US/xml-tags.xml:660(secondary) en_US/xml-tags.xml:668(secondary)
+#: en_US/xml-tags.xml:704(secondary) en_US/xml-tags.xml:740(secondary)
+#: en_US/xml-tags.xml:775(secondary) en_US/xml-tags.xml:786(secondary)
+msgid "GUI tags"
+msgstr "marcas GUI"
+d849 3
+a851 4
+#: en_US/xml-tags.xml:664(command) en_US/xml-tags.xml:669(tertiary)
+#: en_US/xml-tags.xml:674(secondary)
+msgid "guilabel"
+msgstr "guilabel"
+d853 3
+a855 9
+#: en_US/xml-tags.xml:677(para)
+msgid ""
+"Use the <command><guilabel></command> and <command></guilabel></"
+"command> tags as a default for GUI descriptions, like a screen name or "
+"screen title. For example:"
+msgstr ""
+"Use as marcas <command><guilabel></command> e <command></"
+"guilabel></command> por omissão para descrições gráficas, como o nome ou "
+"um título de um ecrã. Por exemplo:"
+d857 3
+a859 10
+#: en_US/xml-tags.xml:683(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"The <guilabel>Authentication Configuration</guilabel> screen \n"
+"shows you how to make your system more secure.\n"
+msgstr ""
+"\n"
+"O ecrã de <guilabel>Configuração da Autenticação</guilabel>\n"
+"mostra-lhe como tornar o seu sistema mais seguro.\n"
+d861 1
+a861 1
+#: en_US/xml-tags.xml:693(para)
+d863 9
+a871 2
+"The <guilabel>Authentication Configuration</guilabel> screen shows you how "
+"to make your system more secure."
+d873 11
+a883 2
+"O ecrã de <guilabel>Configuração da Autenticação</guilabel> mostra-lhe como "
+"tornar o seu sistema mais seguro."
+d885 3
+a887 4
+#: en_US/xml-tags.xml:700(command) en_US/xml-tags.xml:705(tertiary)
+#: en_US/xml-tags.xml:710(secondary)
+msgid "guibutton"
+msgstr "guibutton"
+d889 1
+a889 1
+#: en_US/xml-tags.xml:713(para)
+d891 6
+a896 2
+"Use the <command><guibutton></command> and <command></guibutton>"
+"</command> tags to denote a button on a screen or menu. For example:"
+d898 7
+a904 2
+"Use as marcas <command><guibutton></command> e <command></"
+"guibutton></command> para demarcar um botão num ecrã ou menu. Po exemplo:"
+d906 1
+a906 2
+#: en_US/xml-tags.xml:719(computeroutput)
+#, no-wrap
+d908 2
+a909 3
+"\n"
+"Check the <guibutton>Activate on boot</guibutton> button \n"
+"to have the X Window System start automatically.\n"
+d911 2
+a912 3
+"\n"
+"Assinale o botão <guibutton>Activar no arranque</guibutton>\n"
+"para que o X Window System se inicie automaticamente.\n"
+d914 3
+a916 7
+#: en_US/xml-tags.xml:729(para)
+msgid ""
+"Check the <guibutton>Activate on boot</guibutton> button to have the X "
+"Window System start automatically."
+msgstr ""
+"Assinale o botão <guibutton>Activar no arranque</guibutton> para que o X "
+"Window System se inicie automaticamente."
+d918 1
+a918 6
+#: en_US/xml-tags.xml:736(command) en_US/xml-tags.xml:741(tertiary)
+#: en_US/xml-tags.xml:746(secondary)
+msgid "guiicon"
+msgstr "guiicon"
+
+#: en_US/xml-tags.xml:749(para)
+d920 2
+a921 2
+"The <command><guiicon></command> and <command></guiicon></"
+"command> tags are used to denote a panel or desktop icon. For example:"
+d923 2
+a924 3
+"As marcas <command><guiicon></command> e <command></guiicon></"
+"command> são usadas para demarcar um ícone do painel ou do ambiente de "
+"trabalho. Por exemplo:"
+d926 3
+a928 8
+#: en_US/xml-tags.xml:754(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Double-click the <guiicon>Start Here</guiicon> icon on the desktop.\n"
+msgstr ""
+"\n"
+"Faça duplo-click no ícone <guiicon>Iniciar Aqui</guiicon> do ecrã.\n"
+d930 1
+a930 17
+#: en_US/xml-tags.xml:763(para)
+msgid "Double-click the <guiicon>Start Here</guiicon> icon on the desktop."
+msgstr "Faça duplo-click no ícone <guiicon>Iniciar Aqui</guiicon> do ecrã."
+
+#: en_US/xml-tags.xml:770(title)
+msgid "<command>guimenu</command> and <command>guimenuitem</command>"
+msgstr "<command>guimenu</command> e <command>guimenuitem</command>"
+
+#: en_US/xml-tags.xml:776(tertiary) en_US/xml-tags.xml:781(secondary)
+msgid "guimenu"
+msgstr "guimenu"
+
+#: en_US/xml-tags.xml:787(tertiary) en_US/xml-tags.xml:792(secondary)
+msgid "guimenuitem"
+msgstr "guimenuitem"
+
+#: en_US/xml-tags.xml:795(para)
+d932 1
+a932 3
+"To note a menu (like in the installation program or within the control "
+"panel), use the <command><guimenu></command> and <command></"
+"guimenu></command> tags."
+d934 2
+a935 3
+"Para definir um menu (como aparece no programa de instalação ou no centro de "
+"controlo), use as marcas <command><guimenu></command> e <command></"
+"guimenu></command>."
+d937 3
+a939 11
+#: en_US/xml-tags.xml:801(para)
+msgid ""
+"To note submenu items, use the <command><guimenuitem></command> and "
+"<command></guimenuitem></command> tags. (Please note that there should "
+"not be any breaks between these commands, but for printing purposes breaks "
+"have been inserted). For example:"
+msgstr ""
+"Para definir os itens dos sub-menus, use as marcas <command><"
+"guimenuitem></command> e <command></guimenuitem></command>. (Repare "
+"que não deverão existir nenhumas quebras entre estes comandos mas, para fins "
+"de impressão, poderão ter sido inseridas quebras). Por exemplo:"
+d941 1
+a941 2
+#: en_US/xml-tags.xml:808(computeroutput)
+#, no-wrap
+d943 2
+a944 5
+"\n"
+"Select \n"
+"<guimenu>Main Menu</guimenu> =>\n"
+"\t <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> to start the \n"
+"<application>Emacs</application> text editor.\n"
+d946 2
+a947 31
+"\n"
+"Seleccione\n"
+"<guimenu>Menu Principal</guimenu> =>\n"
+"\t <guimenuitem>Programação</guimenuitem> => <guimenuitem>Emacs</guimenuitem> para iniciar o editor de texto\n"
+"<application>Emacs</application>.\n"
+
+#: en_US/xml-tags.xml:820(para)
+msgid ""
+"From the control panel, click on <guimenu>Main Menu</guimenu> => "
+"<guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</"
+"guimenuitem> to start the <application>Emacs</application> text editor."
+msgstr ""
+"No painel de controlo, seleccione <guimenu>Menu Principal</guimenu> => "
+"<guimenuitem>Programação</guimenuitem> => <guimenuitem>Emacs</"
+"guimenuitem> para iniciar o editor de texto <application>Emacs</application>."
+
+#: en_US/xml-tags.xml:830(command) en_US/xml-tags.xml:834(secondary)
+msgid "keycap"
+msgstr "keycap"
+
+#: en_US/xml-tags.xml:837(para)
+msgid ""
+"To denote a specific key, you will need to use the <command><keycap></"
+"command> and <command></keycap></command> tags. Brackets are "
+"automatically added around the keycap, so do not add them in your XML code. "
+"For example:"
+msgstr ""
+"Para apresentar uma tecla específica, terá de usar as marcas <command><"
+"keycap></command> e <command></keycap></command>. Os parêntesis "
+"rectos serão adicionados automaticamente em torno da tecla, por isso não os "
+"adicione no seu código em XML. Por exemplo:"
+d949 1
+a949 2
+#: en_US/xml-tags.xml:844(computeroutput)
+#, no-wrap
+d951 2
+a952 2
+"\n"
+"To make your selection, press the <keycap>Enter</keycap> key.\n"
+d954 2
+a955 2
+"\n"
+"Para fazer a sua selecção, carregue na tecla <keycap>Enter</keycap>.\n"
+d957 3
+a959 21
+#: en_US/xml-tags.xml:853(para)
+msgid "To make your selection, press the <keycap>Enter</keycap> key."
+msgstr "Para fazer a sua selecção, carregue na tecla <keycap>Enter</keycap>."
+
+#: en_US/xml-tags.xml:858(command) en_US/xml-tags.xml:862(secondary)
+msgid "menuchoice"
+msgstr "menuchoice"
+
+#: en_US/xml-tags.xml:865(para)
+msgid ""
+"Often using a mouse is tedious for common tasks. Therefore, programmers "
+"often build in keyboard-shortcuts to simplify their program. These should be "
+"described using the shortcut tag as a wrapper for the keyboard tags. The "
+"shortcut tag must be wrapped inside the menuchoice tag. For example:"
+msgstr ""
+"Normalmente, a utilização de um rato é aborrecida para as tarefas comuns. "
+"Como tal, os programadores baseiam-se frequentemente nas combinações de "
+"teclas de atalho para simplificar o seu programa. Estas deverão ser "
+"descritas com a marca 'shortcut', como uma envolvência para as marcas de "
+"teclado. A marca 'shortcut' deverá estar envolvida dentro da marca "
+"'menuchoice'. Por exemplo:"
+d961 3
+a963 48
+#: en_US/xml-tags.xml:874(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Go to the menu bar and choose: \n"
+" <menuchoice>\n"
+" <shortcut>\n"
+" <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>\n"
+" </shortcut>\n"
+" <guimenu><accel>F</accel>ile</guimenu>\n"
+" <guimenuitem><accel>S</accel>ave</guimenuitem>\n"
+" </menuchoice>.\n"
+msgstr ""
+"\n"
+"Vá para a barra de menu e escolha:\n"
+" <menuchoice>\n"
+" <shortcut>\n"
+" <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>\n"
+" </shortcut>\n"
+" <guimenu><accel>F</accel>icheiro</guimenu>\n"
+" <guimenuitem><accel>G</accel>ravar</guimenuitem>\n"
+" </menuchoice>.\n"
+
+#: en_US/xml-tags.xml:891(para)
+msgid ""
+"Go to the menu bar and choose: <menuchoice><shortcut><keycombo><keycap>Ctrl</"
+"keycap><keycap>s</keycap></keycombo></shortcut><guimenu><accel>F</accel>ile</"
+"guimenu><guimenuitem><accel>S</accel>ave</guimenuitem></menuchoice>."
+msgstr ""
+"Vá para a barra de menu e escolha: "
+"<menuchoice><shortcut><keycombo><keycap>Ctrl</keycap><keycap>s</keycap></"
+"keycombo></shortcut><guimenu><accel>F</accel>icheiro</"
+"guimenu><guimenuitem><accel>G</accel>ravar</guimenuitem></menuchoice>."
+
+#: en_US/xml-tags.xml:905(command) en_US/xml-tags.xml:909(secondary)
+msgid "keycombo"
+msgstr "keycombo"
+
+#: en_US/xml-tags.xml:912(para)
+msgid ""
+"To illustrate a key combination, you need to use the <command><"
+"keycombo></command> and <command></keycombo></command>, "
+"<command><keycap></command> and <command></keycap></command> "
+"tags. For example:"
+msgstr ""
+"Para ilustrar uma combinação de teclas, terá de usar as marcas <command><"
+"keycombo></command> e <command></keycombo></command>, <command><"
+"keycap></command> e <command></keycap></command>. Por exemplo:"
+d965 3
+a967 12
+#: en_US/xml-tags.xml:920(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To reboot your system, press <keycombo>\n"
+"<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>\n"
+"</keycombo>.\n"
+msgstr ""
+"\n"
+"Para reiniciar o seu sistema, carregue em <keycombo>\n"
+"<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>\n"
+"</keycombo>.\n"
+d969 3
+a971 7
+#: en_US/xml-tags.xml:931(para)
+msgid ""
+"To reboot your system, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</"
+"keycap><keycap>Del</keycap></keycombo>."
+msgstr ""
+"Para reiniciar o seu sistema, carregue em <keycombo><keycap>Ctrl</"
+"keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo>."
+d973 3
+a975 3
+#: en_US/xml-tags.xml:942(title) en_US/style.xml:1377(term)
+msgid "Lists"
+msgstr "Listas"
+d977 3
+a979 8
+#: en_US/xml-tags.xml:945(primary) en_US/xml-tags.xml:969(secondary)
+#: en_US/xml-tags.xml:974(primary) en_US/xml-tags.xml:1042(primary)
+#: en_US/xml-tags.xml:1048(secondary) en_US/xml-tags.xml:1130(secondary)
+#: en_US/xml-tags.xml:1135(primary) en_US/xml-tags.xml:1225(secondary)
+#: en_US/xml-tags.xml:1230(primary) en_US/xml-tags.xml:1408(secondary)
+#: en_US/xml-tags.xml:1413(primary)
+msgid "lists"
+msgstr "listas"
+d981 3
+a983 3
+#: en_US/xml-tags.xml:946(secondary)
+msgid "creating"
+msgstr "criar"
+d985 1
+a985 1
+#: en_US/xml-tags.xml:949(para)
+d987 7
+a993 3
+"There are several types of lists you can create using XML. You can have a "
+"itemized (bulleted) list, a ordered (numbered) list, or a variable list "
+"(presents a term and then a separate paragraph)."
+d995 9
+a1003 3
+"Existem diversos tipos de listas que poderá criar em XML. Poderá ter uma "
+"lista por itens (pontos), uma lista ordenada (numerada) ou uma lista "
+"variável (apresenta um termo e depois um parágrafo separado)."
+d1005 3
+a1007 7
+#: en_US/xml-tags.xml:953(para)
+msgid ""
+"There is also a list format for tables and for for creating a list of "
+"glossary terms and their definitions."
+msgstr ""
+"Existem também um formato em lista para as tabelas e para criar uma lista de "
+"termos de glossário e as suas definições."
+d1009 1
+a1009 1
+#: en_US/xml-tags.xml:956(para)
+d1011 2
+a1012 2
+"The sections below will discuss the proper uses for the various list and how "
+"to create them."
+d1014 3
+a1016 2
+"As secções abaixo irão discutir as utilizações correctas das diversas "
+"listas, bem como descrições para a sua criação."
+d1018 3
+a1020 12
+#: en_US/xml-tags.xml:978(para)
+msgid ""
+"An <command>ItemizedList</command> is best used to present information that "
+"is important for the reader to know, but that does not need to be in a "
+"specific order. It is shorter than a <command>VariableList</command> and "
+"presents the information in a very simple way."
+msgstr ""
+"Uma <command>ItemizedList</command> (lista por itens) é melhor usada para "
+"apresentar informações que sejam importantes para o leitor, mas esta não "
+"necessita de estar por uma determinada ordem. É mais reduzida que uma "
+"<command>VariableList</command> (lista variável) e apresenta a informação de "
+"uma forma muito simples."
+d1022 1
+a1022 1
+#: en_US/xml-tags.xml:984(para)
+d1024 3
+a1026 2
+"To create an <command>ItemizedList</command> (otherwise known as bulleted "
+"list), use the following command sequence:"
+d1028 3
+a1030 2
+"Para criar uma <command>ItemizedList</command> (também conhecida por lista "
+"por pontos), use a seguinte sequência de comandos:"
+d1032 3
+a1034 16
+#: en_US/xml-tags.xml:988(para) en_US/xml-tags.xml:1063(para)
+#: en_US/xml-tags.xml:1147(para)
+msgid ""
+"Notice below that the text for the list item is directly surrounded by the "
+"<command>para</command> tags. If you do not do this, you will find extra "
+"whitespace in your lists where the text does not line up correctly. This is "
+"most noticeable when you have a series of list items that consist of "
+"multiple lines of text. This whitespace is not as noticeable in the HTML "
+"output as it is in the PDFs."
+msgstr ""
+"Repare em baixo que o texto do item da lista está directamente rodeado pelas "
+"marcas <command>para</command>. Se não fizer isto, irá encontrar espaços em "
+"branco extra nas suas listas, sobre as quais o texto não se irá alinhar "
+"correctamente. Isto nota-se mais quando tiver uma série de itens da lista "
+"que consistam em diversas linhas de texto. Este espaço em branco não é tão "
+"notório no resultado em HTML como será nos PDFs."
+d1036 1
+a1036 2
+#: en_US/xml-tags.xml:998(computeroutput)
+#, no-wrap
+d1038 2
+a1039 14
+"\n"
+"<itemizedlist> \n"
+" <listitem>\n"
+" <para>Getting familiar with the installation program's user interface</para>\n"
+" </listitem>\n"
+"\n"
+" <listitem>\n"
+" <para>Starting the installation program</para> \n"
+" </listitem>\n"
+"\n"
+" <listitem>\n"
+" <para>Selecting an installation method</para>\n"
+" </listitem>\n"
+"</itemizedlist>\n"
+d1041 2
+a1042 14
+"\n"
+"<itemizedlist> \n"
+" <listitem>\n"
+" <para>Familiarizar-se com a interface de utilizador do programa de instalação</para>\n"
+" </listitem>\n"
+"\n"
+" <listitem>\n"
+" <para>Iniciar o programa de instalação</para> \n"
+" </listitem>\n"
+"\n"
+" <listitem>\n"
+" <para>Seleccionar um método de instalação</para>\n"
+" </listitem>\n"
+"</itemizedlist>\n"
+d1044 3
+a1046 6
+#: en_US/xml-tags.xml:1015(para) en_US/xml-tags.xml:1094(para)
+#: en_US/xml-tags.xml:1181(para) en_US/xml-tags.xml:1319(para)
+#: en_US/xml-tags.xml:1453(para) en_US/xml-tags.xml:1909(para)
+#: en_US/xml-tags.xml:1958(para)
+msgid "The output looks like:"
+msgstr "O resultado ficará semelhante a:"
+d1048 4
+a1051 2
+#: en_US/xml-tags.xml:1019(para)
+msgid "Getting familiar with the installation program's user interface"
+d1053 2
+a1054 1
+"Familiarizar-se com a interface de utilizador do programa de instalação"
+d1056 3
+a1058 3
+#: en_US/xml-tags.xml:1023(para)
+msgid "Starting the installation program"
+msgstr "Iniciar o programa de instalação"
+d1060 1
+a1060 9
+#: en_US/xml-tags.xml:1027(para)
+msgid "Selecting an installation method"
+msgstr "Seleccionar um método de instalação"
+
+#: en_US/xml-tags.xml:1034(command)
+msgid "OrderedList"
+msgstr "OrderedList"
+
+#: en_US/xml-tags.xml:1052(para)
+d1062 2
+a1063 4
+"An <command>orderedlist</command> is best used to present information that "
+"is important for the reader to know in a specific order. "
+"<command>orderedlist</command>s are a good way to convey step-by-step "
+"senarios to the audience you are writing for."
+d1065 7
+a1071 4
+"Uma <command>orderedlist</command> (lista ordenada) é melhor para apresentar "
+"informações importantes para o leitor, mas que este as saiba por uma "
+"determinada ordem. As <command>orderedlist</command>s são uma boa forma de "
+"explicar cenários passo-a-passo à audiência para a qual está a escrever."
+d1073 1
+a1073 1
+#: en_US/xml-tags.xml:1057(para)
+d1075 6
+a1080 2
+"To create an <command>orderedlist</command> (numbered list), use the "
+"following XML code sequence:"
+d1082 7
+a1088 2
+"Para criar uma <command>orderedlist</command> (lista numerada), use a "
+"seguinte sequência de código em XML:"
+d1090 3
+a1092 85
+#: en_US/xml-tags.xml:1073(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<orderedlist>\n"
+" <listitem>\n"
+" <para>Online &mdash; http://www.redhat.com/support/errata; supplies errata\n"
+" you can read online, and you can download diskette images\n"
+" easily.</para>\n"
+" </listitem>\n"
+"\t \n"
+" <listitem>\n"
+" <para>Email &mdash; By sending an empty mail message to errata@@redhat.com, \n"
+" you will receive an email containing a text listing of the \n"
+" complete errata of the installation program and related software \n"
+" (if errata exist at that time). Also included are URLs to each \n"
+" updated package and diskette image in the errata. Using these \n"
+" URLs, you can download any necessary diskette images. Please \n"
+" note: use binary mode when transferring a diskette image.</para> \n"
+" </listitem>\n"
+"</orderedlist>\n"
+msgstr ""
+"\n"
+"<orderedlist>\n"
+" <listitem>\n"
+" <para>Online &mdash; http://www.redhat.com/support/errata; oferece uma errata\n"
+" que poderá ler 'online', e onde poderá obter imagens de disquetes\n"
+" com facilidade.</para>\n"
+" </listitem>\n"
+"\t \n"
+" <listitem>\n"
+" <para>E-mail &mdash; Se enviar uma mensagem de e-mail vazia para errata@@redhat.com, \n"
+" irá receber um e-mail que contém uma listagem em texto da errata completa\n"
+" do programa de instalação e das aplicações relacionadas (se existir alguma\n"
+" nessa altura). Também estão incluídos os URLS de cada pacote actualizado\n"
+" e da imagem da disquete na errata. Se usar estes URLs, poderá obter as\n"
+" imagens de disquetes necessárias. Repare por favor: use o modo binário\n"
+" quando transferir uma imagem de disquete.</para> \n"
+" </listitem>\n"
+"</orderedlist>\n"
+
+#: en_US/xml-tags.xml:1098(para)
+msgid ""
+"Online — http://www.redhat.com/support/errata; supplies errata you can "
+"read online, and you can download diskette images easily."
+msgstr ""
+"Online — http://www.redhat.com/support/errata; oferece uma errata que "
+"poderá ler 'online', e onde poderá obter imagens de disquetes com facilidade."
+
+#: en_US/xml-tags.xml:1105(para)
+msgid ""
+"Email — By sending an empty mail message to errata@@redhat.com, you "
+"will receive an email containing a text listing of the complete errata of "
+"the installation program and related software (if errata exist at that "
+"time). Also included are URLs to each updated package and diskette image in "
+"the errata. Using these URLs, you can download any necessary diskette "
+"images. Please note: use binary mode when transferring a diskette image."
+msgstr ""
+"E-mail — Se enviar uma mensagem de e-mail vazia para errata@@redhat."
+"com, irá receber um e-mail que contém uma listagem em texto da errata "
+"completa do programa de instalação e das aplicações relacionadas (se existir "
+"alguma nessa altura). Também estão incluídos os URLS de cada pacote "
+"actualizado e da imagem da disquete na errata. Se usar estes URLs, poderá "
+"obter as imagens de disquetes necessárias. Repare por favor: use o modo "
+"binário quando transferir uma imagem de disquete."
+
+#: en_US/xml-tags.xml:1121(command)
+msgid "Variablelist"
+msgstr "Variablelist"
+
+#: en_US/xml-tags.xml:1139(para)
+msgid ""
+"A <command>variablelist</command> best represents a list of terms and "
+"definitions or descriptions for those terms."
+msgstr ""
+"Uma <command>variablelist</command> (lista variável) representa uma lista de "
+"termos e definições ou descrições desses termos."
+
+#: en_US/xml-tags.xml:1142(para)
+msgid ""
+"To create a <command>variablelist</command>, use the following command "
+"sequence:"
+msgstr ""
+"Para criar uma <command>variablelist</command>, use a seguinte sequência de "
+"comandos:"
+d1094 1
+a1094 2
+#: en_US/xml-tags.xml:1157(computeroutput)
+#, no-wrap
+d1096 4
+a1099 21
+"\n"
+"<variablelist>\n"
+" <varlistentry> \n"
+" <term> New Multi-CD Install </term>\n"
+" <listitem> \n"
+" <para>As the installation program continues to grow, Red Hat has developed \n"
+" an installation program capable of installing from \n"
+" multiple CD-ROMs.</para>\n"
+" </listitem>\n"
+" </varlistentry>\n"
+"\n"
+" <varlistentry>\n"
+" <term>XFree 4.0 </term>\n"
+" <listitem>\n"
+" <para>Configuration of your X Window System during the installation has \n"
+" never been more thorough. From choosing your monitor and its correct \n"
+" settings, to video card probing, to testing your desired X setup, \n"
+" Xconfigurator will help you set everything just right.</para>\n"
+" </listitem>\n"
+" </varlistentry>\n"
+"</variablelist>\n"
+d1101 4
+a1104 50
+"\n"
+"<variablelist>\n"
+" <varlistentry> \n"
+" <term> Nova Instalação Multi-CDs</term>\n"
+" <listitem> \n"
+" <para>À medida que o programa de instalação continua a crescer,\n"
+" a Red Hat criou um programa de instalação que consegue instalar a partir\n"
+" de vários CD-ROMs.</para>\n"
+" </listitem>\n"
+" </varlistentry>\n"
+"\n"
+" <varlistentry>\n"
+" <term>XFree 4.0 </term>\n"
+" <listitem>\n"
+" <para>A configuração do seu X Window System durante a instalação\n"
+" nunca foi tão abrangente. Desde escolher o seu monitor e as suas\n"
+" respectivas opções, até à detecção da placa gráfica, ao teste da sua\n"
+" configuração do X, o Xconfigurator ajudá-lo-á a configurar tudo \n"
+" facilmente.</para>\n"
+" </listitem>\n"
+" </varlistentry>\n"
+"</variablelist>\n"
+
+#: en_US/xml-tags.xml:1185(term)
+msgid "New Multi-CD Install"
+msgstr "Nova Instalação Multi-CDs"
+
+#: en_US/xml-tags.xml:1185(para)
+msgid ""
+"As the installation program continues to grow, Red Hat has developed an "
+"installation program capable of installing from multiple CD-ROMs."
+msgstr ""
+"À medida que o programa de instalação continua a crescer, a Red Hat criou um "
+"programa de instalação que consegue instalar a partir de vários CD-ROMs."
+
+#: en_US/xml-tags.xml:1193(term)
+msgid "XFree 4.0"
+msgstr "XFree 4.0"
+
+#: en_US/xml-tags.xml:1195(para)
+msgid ""
+"Configuration of your X Window System during the installation has never been "
+"more thorough. From choosing your monitor and its correct settings, to video "
+"card probing, to testing your desired X setup, Xconfigurator will help you "
+"set everything just right."
+msgstr ""
+"A configuração do seu X Window System durante a instalação nunca foi tão "
+"abrangente. Desde escolher o seu monitor e as suas respectivas opções, até à "
+"detecção da placa gráfica, ao teste da sua configuração do X, o "
+"Xconfigurator ajudá-lo-á a configurar tudo facilmente."
+d1106 3
+a1108 3
+#: en_US/xml-tags.xml:1205(title) en_US/writing-guidelines.xml:443(title)
+msgid "Warning"
+msgstr "Aviso"
+d1110 1
+a1110 1
+#: en_US/xml-tags.xml:1206(para)
+d1112 8
+a1119 2
+"Do <emphasis>not</emphasis> specify the <computeroutput>frame</"
+"computeroutput> attribute to the table. Doing so breaks PDF production."
+d1121 13
+a1133 2
+"<emphasis>Não</emphasis> defina o atributo <computeroutput>frame</"
+"computeroutput> da tabela. Se fizer isso, impede a geração de PDFs."
+d1135 5
+a1139 2
+#: en_US/xml-tags.xml:1216(title)
+msgid "Creating a List Within a Table Using <command>Simplelist</command>"
+d1141 3
+a1143 1
+"Criar uma Lista Dentro de uma Tabela com uma <command>SimpleList</command>"
+d1145 3
+a1147 4
+#: en_US/xml-tags.xml:1220(command) en_US/xml-tags.xml:1226(tertiary)
+#: en_US/xml-tags.xml:1231(command) en_US/xml-tags.xml:1237(command)
+msgid "simplelist"
+msgstr "simplelist"
+d1149 7
+a1155 3
+#: en_US/xml-tags.xml:1235(primary)
+msgid "tables"
+msgstr "tabelas"
+d1157 3
+a1159 3
+#: en_US/xml-tags.xml:1236(secondary)
+msgid "creating a list within a table"
+msgstr "criar uma lista dentro de uma tabela"
+d1161 1
+a1161 1
+#: en_US/xml-tags.xml:1240(para)
+d1163 4
+a1166 2
+"A <command>simplelist</command> is an unadorned list of items. "
+"<command>simplelist</command>s can be inline or arranged in columns."
+d1168 5
+a1172 3
+"Uma <command>simplelist</command> é lista sem qualquer enfeite dos itens. As "
+"<command>simplelist</command>s podem ser incorporadas ou organizadas em "
+"colunas."
+d1174 1
+a1174 1
+#: en_US/xml-tags.xml:1244(para)
+d1176 3
+a1178 3
+"We use <command>simplelist</command> to add separate paragraphs of text "
+"within a table element. A regular list, such as <command>itemizedlist</"
+"command>, cannot be embedded within a table."
+d1180 3
+a1182 4
+"É usada a <command>simplelist</command> para adicionar parágrafos separados "
+"de texto dentro de um elemento de tabela. Uma lista normal, como a "
+"<command>itemizedlist</command>, não poderá ser incorporada dentro de uma "
+"tabela."
+d1184 1
+a1184 6
+#: en_US/xml-tags.xml:1248(para)
+msgid "The XML commands for a table look like:"
+msgstr "Os comandos em XML de uma tabela assemelham-se a:"
+
+#: en_US/xml-tags.xml:1251(computeroutput)
+#, no-wrap
+d1186 3
+a1188 65
+"\n"
+"\t <table id=\"tb-hwinfo-hostbus\">\n"
+"\t <title>Host Bus Adapter Features and Configuration Requirements</title>\n"
+"\t \n"
+"\t <tgroup cols=\"3\">\n"
+"\t <colspec colnum=\"1\" colname=\"HostBus\" colwidth=\"33\"/>\n"
+"\t <colspec colnum=\"2\" colname=\"Features\" colwidth=\"34\"/>\n"
+"\t <colspec colnum=\"3\" colname=\"Single\" colwidth=\"33\"/>\n"
+"\t \n"
+"\t <thead>\n"
+"\t\t<row>\n"
+"\t\t <entry>Host Bus Adapter</entry>\n"
+"\t\t <entry>Features</entry>\n"
+"\t\t <entry>Single-Initiator Configuration</entry>\n"
+"\t\t</row>\n"
+"\t </thead>\n"
+"\t \n"
+"\t <tbody>\n"
+"\t\t\n"
+"\t\t<row>\n"
+"\t\t <entry>Adaptec 2940U2W</entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Ultra2, wide, LVD.</member>\n"
+"\t\t <member>HD68 external connector.</member>\n"
+"\t\t <member>One channel, with two bus segments.</member>\n"
+"\t\t <member>Set the onboard termination by using the BIOS\n"
+"\t\t\tutility.</member>\n"
+"\t\t <member>Onboard termination is disabled when the power is\n"
+"\t\t\toff.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist>\n"
+"\t\t <member>Set the onboard termination to automatic (the\n"
+"\t\t\tdefault).</member>\n"
+"\t\t <member>Use the internal SCSI connector for private\n"
+"\t\t\t(non-cluster) storage.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t</row>\n"
+"\t\t\n"
+"\t\t<row>\n"
+"\t\t <entry>Qlogic QLA1080</entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Ultra2, wide, LVD</member>\n"
+"\t\t <member>VHDCI external connector</member>\n"
+"\t\t <member>One channel</member>\n"
+"\t\t <member>Set the onboard termination by using the BIOS\n"
+"\t\t\tutility.</member>\n"
+"\t\t <member>Onboard termination is disabled when the power is off,\n"
+"\t\t\tunless jumpers are used to enforce termination.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t \n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Set the onboard termination to\n"
+"\t\t\tautomatic (the default).</member>\n"
+"\t\t <member>Use the internal SCSI connector for private\n"
+"\t\t\t(non-cluster) storage.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t</row>\n"
+"\t\t\n"
+"\t </tbody>\n"
+"\t </tgroup>\n"
+"\t </table>\n"
+d1190 3
+a1192 171
+"\n"
+"\t <table id=\"tb-hwinfo-hostbus\">\n"
+"\t <title>Funcionalidades e Requisitos de Configuração do Adaptador-Anfitrião do Barramento</title>\n"
+"\t \n"
+"\t <tgroup cols=\"3\">\n"
+"\t <colspec colnum=\"1\" colname=\"Barramento\" colwidth=\"33\"/>\n"
+"\t <colspec colnum=\"2\" colname=\"Funcionalidades\" colwidth=\"34\"/>\n"
+"\t <colspec colnum=\"3\" colname=\"Único\" colwidth=\"33\"/>\n"
+"\t \n"
+"\t <thead>\n"
+"\t\t<row>\n"
+"\t\t <entry>Adaptador-Anfitrião do Barramento</entry>\n"
+"\t\t <entry>Funcionalidades</entry>\n"
+"\t\t <entry>Configuração do Iniciador Único</entry>\n"
+"\t\t</row>\n"
+"\t </thead>\n"
+"\t \n"
+"\t <tbody>\n"
+"\t\t\n"
+"\t\t<row>\n"
+"\t\t <entry>Adaptec 2940U2W</entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Ultra2, wide, LVD.</member>\n"
+"\t\t <member>conector externo HD68.</member>\n"
+"\t\t <member>Um canal, com dois segmentos do barramento.</member>\n"
+"\t\t <member>Configurar a terminação na placa com o utilitário da BIOS..</member>\n"
+"\t\t <member>A terminação na placa está desactivada quando a máquina estiver desligada.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist>\n"
+"\t\t <member>Configura a terminação na placa como automática (por omissão).</member>\n"
+"\t\t <member>Use o conector interno do SCSI para o armazenamento\n"
+"\t\t\tprivado (sem 'cluster').</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t</row>\n"
+"\t\t\n"
+"\t\t<row>\n"
+"\t\t <entry>Qlogic QLA1080</entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Ultra2, wide, LVD</member>\n"
+"\t\t <member>Conector externo VHDCI</member>\n"
+"\t\t <member>Um canal</member>\n"
+"\t\t <member>Configura a terminação na placa com o utilitário da BIOS.</member>\n"
+"\t\t <member>A terminação na placa está desactivada com a energia desligada, a menos que use os interruptores para forçar a terminação.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t \n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Configure a terminação na placa como automática\n"
+"\t\t\t (por omissão).</member>\n"
+"\t\t <member>Use o conector interno do SCSI para o armazenamento privado (sem 'cluster').</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t</row>\n"
+"\t\t\n"
+"\t </tbody>\n"
+"\t </tgroup>\n"
+"\t </table>\n"
+
+#: en_US/xml-tags.xml:1322(title)
+msgid "Host Bus Adapter Features and Configuration Requirements"
+msgstr ""
+"Funcionalidades do Adaptador-Anfitrião do Barramento e Requisitos de "
+"Configuração"
+
+#: en_US/xml-tags.xml:1331(entry)
+msgid "Host Bus Adapter"
+msgstr "Adaptador-Anfitrião do Barramento"
+
+#: en_US/xml-tags.xml:1332(entry) en_US/xml-tags.xml:2144(entry)
+msgid "Features"
+msgstr "Funcionalidades"
+
+#: en_US/xml-tags.xml:1333(entry)
+msgid "Single-Initiator Configuration"
+msgstr "Configuração do Iniciador Único"
+
+#: en_US/xml-tags.xml:1340(entry)
+msgid "Adaptec 2940U2W"
+msgstr "Adaptec 2940U2W"
+
+#: en_US/xml-tags.xml:1343(member)
+msgid "Ultra2, wide, LVD."
+msgstr "Ultra2, wide, LVD."
+
+#: en_US/xml-tags.xml:1344(member)
+msgid "HD68 external connector."
+msgstr "Conector externo HD68."
+
+#: en_US/xml-tags.xml:1345(member)
+msgid "One channel, with two bus segments."
+msgstr "Um canal, com dois segmentos do barramento."
+
+#: en_US/xml-tags.xml:1346(member) en_US/xml-tags.xml:1367(member)
+msgid "Set the onboard termination by using the BIOS utility."
+msgstr "Configure a terminação na placa com o utilitário da BIOS."
+
+#: en_US/xml-tags.xml:1348(member)
+msgid "Onboard termination is disabled when the power is off."
+msgstr "A terminação na placa é desactivada quando é desligada a alimentação."
+
+#: en_US/xml-tags.xml:1353(member) en_US/xml-tags.xml:1375(member)
+msgid "Set the onboard termination to automatic (the default)."
+msgstr "Configure a terminação na placa como automática (por omissão)."
+
+#: en_US/xml-tags.xml:1355(member) en_US/xml-tags.xml:1377(member)
+msgid "Use the internal SCSI connector for private (non-cluster) storage."
+msgstr ""
+"Use o conector interno SCSI para armazenamento privado (sem 'cluster')."
+
+#: en_US/xml-tags.xml:1361(entry)
+msgid "Qlogic QLA1080"
+msgstr "Qlogic QLA1080"
+
+#: en_US/xml-tags.xml:1364(member)
+msgid "Ultra2, wide, LVD"
+msgstr "Ultra2, wide, LVD"
+
+#: en_US/xml-tags.xml:1365(member)
+msgid "VHDCI external connector"
+msgstr "conector externo VHDCI"
+
+#: en_US/xml-tags.xml:1366(member)
+msgid "One channel"
+msgstr "Um canal"
+
+#: en_US/xml-tags.xml:1369(member)
+msgid ""
+"Onboard termination is disabled when the power is off, unless jumpers are "
+"used to enforce termination."
+msgstr ""
+"A terminação na placa é desactivada quando se desliga a alimentação, a menos "
+"que existam interruptores para forçar a terminação."
+
+#: en_US/xml-tags.xml:1388(para)
+msgid ""
+"Notice how the <command>SimpleList</command> tags are used. The <"
+"entry> and <simplelist> tags must be aligned beside one another, "
+"otherwise you will receive a parsing error."
+msgstr ""
+"Repare na utilização das marcas <command>SimpleList</command>. As marcas <"
+"entry> e <simplelist> deverão ser alinhadas uma ao lado da outra, "
+"caso contrário irá receber um erro de processamento."
+
+#: en_US/xml-tags.xml:1393(para)
+msgid ""
+"For each paragraph or list item to be added within a <command>SimpleList</"
+"command>, the <member> tag set must be added around that particular "
+"text item."
+msgstr ""
+"Para cada parágrafo ou item da lista adicionado dentro de uma "
+"<command>SimpleList</command>, dever-se-á adicionar uma marca <member> "
+"em torno desse item de texto em particular."
+
+#: en_US/xml-tags.xml:1399(command) en_US/xml-tags.xml:1403(command)
+#: en_US/xml-tags.xml:1409(tertiary) en_US/xml-tags.xml:1414(command)
+msgid "glosslist"
+msgstr "glosslist"
+
+#: en_US/xml-tags.xml:1417(para)
+msgid ""
+"Use the <command>glosslist</command> command set to create a list of "
+"glossary terms and their definitions."
+msgstr ""
+"Use o comando <command>glosslist</command> para criar uma lista de termos do "
+"glossário e as suas definições."
+
+#: en_US/xml-tags.xml:1421(para)
+msgid "In XML, an example looks like the following:"
+msgstr "Em XML, um exemplo poderá ser o seguinte:"
+d1194 1
+a1194 2
+#: en_US/xml-tags.xml:1424(computeroutput)
+#, no-wrap
+d1196 2
+a1197 53
+"\n"
+"\t <glosslist>\n"
+"\t <glossentry>\n"
+"\t <glossterm>applet</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>A small application, usually a utility or other\n"
+"\t simple program.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\n"
+"\t <glossentry>\n"
+"\t <glossterm>architecture</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>The design for organization and integration of \n"
+" components within a computer or computer system.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\n"
+"\t <glossentry>\n"
+"\t <glossterm>archive</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>To transfer files into storage for the purpose of \n"
+"\t saving space and/or organization.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\t </glosslist>\n"
+msgstr ""
+"\n"
+"\t <glosslist>\n"
+"\t <glossentry>\n"
+"\t <glossterm>applet</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>Uma pequena aplicação, normalmente um utilitário\n"
+" ou outro programa simples.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\n"
+"\t <glossentry>\n"
+"\t <glossterm>arquitectura</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>O desenho da organização e integração dos\n"
+" componentes dentro de um computador ou sistema computacional.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\n"
+"\t <glossentry>\n"
+"\t <glossterm>pacote</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>Para transferir os ficheiros armazenados com o\n"
+" intuito de poupar espaço e/ou organização.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\t </glosslist>\n"
+d1199 3
+a1201 6
+#: en_US/xml-tags.xml:1459(glossterm)
+msgid "applet"
+msgstr "applet"
+
+#: en_US/xml-tags.xml:1461(para)
+msgid "A small application, usually a utility or other simple program."
+d1203 1
+a1203 1
+"Uma pequena aplicação, normalmente um utilitário ou outro programa simples."
+d1205 3
+a1207 3
+#: en_US/xml-tags.xml:1466(glossterm)
+msgid "architecture"
+msgstr "arquitectura"
+d1209 1
+a1209 1
+#: en_US/xml-tags.xml:1468(para)
+d1211 3
+a1213 2
+"The design for organization and integration of components within a computer "
+"or computer system."
+d1215 3
+a1217 2
+"O desenho da organização e integração dos componentes dentro de um "
+"computador ou sistema computacional."
+d1219 3
+a1221 3
+#: en_US/xml-tags.xml:1474(glossterm)
+msgid "archive"
+msgstr "pacote"
+d1223 1
+a1223 1
+#: en_US/xml-tags.xml:1476(para)
+d1225 2
+a1226 2
+"To transfer files into storage for the purpose of saving space and/or "
+"organization."
+d1228 2
+a1229 2
+"Para transferir os ficheiros armazenados com o intuito de poupar espaço e/ou "
+"organização."
+d1231 3
+a1233 3
+#: en_US/xml-tags.xml:1487(command) en_US/xml-tags.xml:1491(secondary)
+msgid "option"
+msgstr "option"
+d1235 1
+a1235 1
+#: en_US/xml-tags.xml:1494(para)
+d1237 3
+a1239 2
+"If you have a command that offers an option or a flag, use the <command><"
+"option></command> and <command></option></command> tags."
+d1241 4
+a1244 2
+"Se tiver um comando que ofereça uma opção qualquer, use as marcas "
+"<command><option></command> e <command></option></command>."
+d1246 1
+a1246 1
+#: en_US/xml-tags.xml:1501(para)
+d1248 2
+a1249 2
+"The <option> tag set is only meant to be used for command line "
+"options, not options in configuration files."
+d1251 6
+a1256 2
+"A marca <option> só pretende ser usada para as opções da linha de "
+"comandos, não para as opções dos ficheiros de configuração."
+d1258 3
+a1260 3
+#: en_US/xml-tags.xml:1505(para)
+msgid "In XML, specifying an option would look like the following:"
+msgstr "Em XML, a definição de uma opção ficará semelhante à seguinte:"
+d1262 1
+a1262 2
+#: en_US/xml-tags.xml:1509(computeroutput)
+#, no-wrap
+d1264 3
+a1266 3
+"\n"
+"For example, with the command <command>ls</command> you can \n"
+"specify an option such as <option>-la</option>.\n"
+d1268 4
+a1271 3
+"\n"
+"Por exemplo, com o comando <command>ls</command>, poderá\n"
+"definir uma opção como a <option>-la</option>.\n"
+d1273 3
+a1275 1
+#: en_US/xml-tags.xml:1519(para)
+d1277 8
+a1284 2
+"For example, with the command <command>ls</command> you can specify an "
+"option such as <option>-la</option>."
+d1286 8
+a1293 2
+"Por exemplo, com o comando <command>ls</command>, poderá definir uma opção "
+"como a <option>-la</option>."
+d1295 3
+a1297 3
+#: en_US/xml-tags.xml:1525(title)
+msgid "Index Entries"
+msgstr "Itens do Índice"
+d1299 1
+a1299 6
+#: en_US/xml-tags.xml:1528(primary) en_US/xml-tags.xml:1534(secondary)
+#: en_US/xml-tags.xml:1563(primary) en_US/xml-tags.xml:1595(primary)
+msgid "indexing"
+msgstr "indexação"
+
+#: en_US/xml-tags.xml:1537(para)
+d1301 4
+a1304 2
+"The following command sequence shows you the code inserted into the body of "
+"the text to add an index entry to your document:"
+d1306 4
+a1309 2
+"A seguinte sequência de comandos mostra-lhe o código inserido dentro do "
+"conteúdo do texto, de modo a adicionar um item do índice ao seu documento:"
+d1311 1
+a1311 2
+#: en_US/xml-tags.xml:1542(computeroutput)
+#, no-wrap
+d1313 2
+a1314 5
+"\n"
+"<indexterm> <-- indicates a term to be placed in the index\n"
+"<primary>foo</primary> <-- indicates that \"foo\" is the first term\n"
+"<secondary>bar</secondary> <-- \"bar\" will be listed under \"foo\" \n"
+"</indexterm> <-- closes this index entry\n"
+d1316 10
+a1325 29
+"\n"
+"<indexterm> <-- indica um termo a colocar no índice\n"
+"<primary>xpto</primary> <-- indica que o \"xpto\" é o primeiro termo\n"
+"<secondary>xpto-2</secondary> <-- o \"xpto-2\" aparecerá debaixo do \"xpto\"\n"
+"</indexterm> <-- fecha este item do índice\n"
+
+#: en_US/xml-tags.xml:1551(primary)
+msgid "foo"
+msgstr "xpto"
+
+#: en_US/xml-tags.xml:1552(secondary)
+msgid "bar"
+msgstr "xpto-2"
+
+#: en_US/xml-tags.xml:1556(para)
+msgid ""
+"The <command><seealso></command> tag allows you to reference another "
+"index entry or refer to another manual. Make sure the <command><"
+"seealso></command> reference you are pointing to has its own entry. For "
+"example:"
+msgstr ""
+"A marca <command><seealso></command> permite-lhe fazer referências a "
+"outros itens do índice ou referenciar outro manual. Certifique-se que o "
+"<command><seealso></command> para o qual aponta tem o seu próprio "
+"item. Por exemplo:"
+
+#: en_US/xml-tags.xml:1564(secondary)
+msgid "seealso tag"
+msgstr "marca 'seealso'"
+d1327 1
+a1327 2
+#: en_US/xml-tags.xml:1568(computeroutput)
+#, no-wrap
+d1329 3
+a1331 10
+"\n"
+"<indexterm> \n"
+"<primary>SWAK</primary> \n"
+"<seealso>salutations</seealso>\n"
+"</indexterm>\n"
+"\n"
+"\n"
+"<indexterm> \n"
+"<primary>salutations</primary> \n"
+"</indexterm>\n"
+d1333 3
+a1335 10
+"\n"
+"<indexterm> \n"
+"<primary>SWAK</primary> \n"
+"<seealso>saudações</seealso>\n"
+"</indexterm>\n"
+"\n"
+"\n"
+"<indexterm> \n"
+"<primary>saudações</primary> \n"
+"</indexterm>\n"
+d1337 3
+a1339 3
+#: en_US/xml-tags.xml:1582(primary)
+msgid "SWAK"
+msgstr "SWAK"
+d1341 1
+a1341 5
+#: en_US/xml-tags.xml:1583(seealso) en_US/xml-tags.xml:1587(primary)
+msgid "Salutations"
+msgstr "Saudações"
+
+#: en_US/xml-tags.xml:1590(para)
+d1343 3
+a1345 2
+"The <command><see></command> tag allows you to reference to another "
+"index entry entirely. For example:"
+d1347 3
+a1349 2
+"A marca <command><see></command> permite-lhe referenciar outro item do "
+"índice por inteiro. Por exemplo:"
+d1351 3
+a1353 3
+#: en_US/xml-tags.xml:1596(secondary)
+msgid "see tag"
+msgstr "marca 'see'"
+d1355 1
+a1355 2
+#: en_US/xml-tags.xml:1601(computeroutput)
+#, no-wrap
+d1357 2
+a1358 11
+"\n"
+"<indexterm> \n"
+"<primary>Guinness</primary> \n"
+"<see>beer</see> <-- beer will be listed under \n"
+"the Guinness entry, but you must make sure beer also has its \n"
+"own entry to refer to.\n"
+"</indexterm>\n"
+"\n"
+"<indexterm>\n"
+"<primary>beer</primary>\n"
+"</indexterm>\n"
+d1360 2
+a1361 11
+"\n"
+"<indexterm> \n"
+"<primary>Guinness</primary> \n"
+"<see>cerveja</see> <-- a 'cerveja' irá aparecer\n"
+"abaixo do item 'Guinness', mas terá de garantir que a 'cerveja'\n"
+"tem também o seu próprio item para ser referenciado.\n"
+"</indexterm>\n"
+"\n"
+"<indexterm>\n"
+"<primary>cerveja</primary>\n"
+"</indexterm>\n"
+d1363 1
+a1363 9
+#: en_US/xml-tags.xml:1616(primary)
+msgid "Guinness"
+msgstr "Guinness"
+
+#: en_US/xml-tags.xml:1617(see) en_US/xml-tags.xml:1621(primary)
+msgid "Beer"
+msgstr "Cerveja"
+
+#: en_US/xml-tags.xml:1624(para)
+d1365 2
+a1366 2
+"To view the HTML output of the index entries shown here, refer to the "
+"<filename>generated-index.html</filename> file at the end of this document."
+d1368 2
+a1369 2
+"Para ver o resultado em HTML dos itens do índice que aparecem aqui, veja o "
+"ficheiro <filename>generated-index.html</filename> no fim deste documento."
+d1371 1
+a1371 1
+#: en_US/xml-tags.xml:1628(para)
+d1373 2
+a1374 4
+"How does the index get generated? If indexterms exist in the document and "
+"the beginning and ending index tags exist before the end tag for the book or "
+"article, an index is created because of the <command>generate.index</"
+"command> stylesheet parameter, which is set to true by default."
+d1376 2
+a1377 5
+"Agora como é que o índice é gerado? Se existirem 'indexterms' no documento e "
+"as marcas de início e fim do índice existirem antes da marca final do livro "
+"ou do artigo, é criado um índice devido ao parâmetro <command>generate."
+"index</command> da folha de estilo, que está definido como verdadeiro por "
+"omissão."
+d1379 3
+a1381 3
+#: en_US/xml-tags.xml:1638(command) en_US/xml-tags.xml:1643(secondary)
+msgid "para"
+msgstr "para"
+d1383 1
+a1383 1
+#: en_US/xml-tags.xml:1646(para)
+d1385 2
+a1386 2
+"For any paragraph, the <command><para></command> and <command></"
+"para></command> tags must open and close that particular paragraph."
+d1388 2
+a1389 3
+"Para qualquer parágrafo, as marcas <command><para></command> e "
+"<command></para></command> deverão abrir e fechar esse parágrafo em "
+"particular."
+d1391 1
+a1391 1
+#: en_US/xml-tags.xml:1651(para)
+d1393 2
+a1394 2
+"Do not use para tags around anything other than a simple paragraph. Doing so "
+"will create additional white space within the text itself."
+d1396 2
+a1397 2
+"Não use as marcas 'para' para nada que não seja um parágrafo simples. Se o "
+"fizer, irá criar espaço em branco adicional dentro do próprio texto."
+d1399 1
+a1399 1
+#: en_US/xml-tags.xml:1655(para)
+d1401 2
+a1402 3
+"Do not use <command><para></command> tags around the following (or, to "
+"put this another way, do not embed the following within <command><para>"
+"</command> tags):"
+d1404 2
+a1405 3
+"Não use as marcas <command><para></command> em torno dos seguintes "
+"ponto (ou, posto de outra forma, não incorpore o seguinte dentro das marcas "
+"<command><para></command>):"
+d1407 7
+a1413 4
+#: en_US/xml-tags.xml:1661(command) en_US/xml-tags.xml:1896(command)
+#: en_US/xml-tags.xml:1904(command) en_US/xml-tags.xml:1953(command)
+msgid "<screen>"
+msgstr "<screen>"
+d1415 3
+a1417 3
+#: en_US/xml-tags.xml:1664(command)
+msgid "<itemizedlist>"
+msgstr "<itemizedlist>"
+d1419 3
+a1421 3
+#: en_US/xml-tags.xml:1667(command)
+msgid "<orderedlist>"
+msgstr "<orderedlist>"
+d1423 1
+a1423 18
+#: en_US/xml-tags.xml:1670(command)
+msgid "<variablelist>"
+msgstr "<variablelist>"
+
+#: en_US/xml-tags.xml:1673(command)
+msgid "<table>"
+msgstr "<table>"
+
+#: en_US/xml-tags.xml:1680(command) en_US/xml-tags.xml:1689(secondary)
+#: en_US/writing-guidelines.xml:139(sgmltag)
+msgid "part"
+msgstr "part"
+
+#: en_US/xml-tags.xml:1683(primary)
+msgid "parts"
+msgstr "parts"
+
+#: en_US/xml-tags.xml:1692(para)
+d1425 5
+a1429 3
+"In the parent file, you can separate the chapters into parts to divide them "
+"into logical groups. For example, in the parent file, the <command>part</"
+"command> tags surround the chapter entities:"
+d1431 5
+a1435 3
+"No ficheiro-pai, poderá separar os capítulos em partes, de modo a dividi-los "
+"em grupos lógicos. Por exemplo, no ficheiro-pai, as marcas <command>part</"
+"command> rodeiam as entidades do capítulo:"
+d1437 3
+a1439 20
+#: en_US/xml-tags.xml:1698(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<part id=\"pt-foo\">\n"
+" <partintro>\n"
+" <para>Some text for the part intro</para>\n"
+" &CHAPTER; \n"
+"\n"
+" &ANOTHER-CHAPTER;\n"
+"</part>\n"
+msgstr ""
+"\n"
+"<part id=\"pt-xpto\">\n"
+" <partintro>\n"
+" <para>Algum texto para a introdução da parte</para>\n"
+" &CAPITULO; \n"
+"\n"
+" &OUTRO-CAPITULO;\n"
+"</part>\n"
+d1441 3
+a1443 7
+#: en_US/xml-tags.xml:1709(para)
+msgid ""
+"If you create a part, include a part introduction describing the contents of "
+"the part. For example:"
+msgstr ""
+"Se criar uma parte, inclua uma introdução de uma parte que descreva o seu "
+"conteúdo. Por exemplo:"
+d1445 1
+a1445 2
+#: en_US/xml-tags.xml:1715(computeroutput)
+#, no-wrap
+d1447 2
+a1448 8
+"\n"
+" <part id=\"pt-setup\">\n"
+" <title>Getting Setup</title>\n"
+" <partintro>\n"
+" <para>This section contains information you will need when you first join\n"
+"\tthe Docs group. You might need to refer to this part again for\n"
+"\tinformation such as installing &FC;.</para>\n"
+" </partintro>\n"
+d1450 2
+a1451 33
+"\n"
+" <part id=\"pt-configuracao\">\n"
+" <title>Compreender a Configuração</title>\n"
+" <partintro>\n"
+" <para>Esta secção contém informações que irá necessitar quando\n"
+" se juntar pela primeira vez ao grupo de Documentação. Poderá ter de\n"
+" referenciar esta parte de novo para mais informações, como a instalação\n"
+" do &FC;.</para>\n"
+" </partintro>\n"
+
+#: en_US/xml-tags.xml:1726(para)
+msgid ""
+"In the HTML output, a separate HTML page is generated with the part number, "
+"title, introduction, and TOC. In the PDF output, the same information about "
+"the part is on a separate page."
+msgstr ""
+"No resultado em HTML, é gerada uma página separada em HTML para o número, "
+"título, introdução e índice da parte. No resultado em PDF, a mesma "
+"informação acerca da página está numa página em separado."
+
+#: en_US/xml-tags.xml:1735(command) en_US/xml-tags.xml:1739(secondary)
+msgid "prompt"
+msgstr "prompt"
+
+#: en_US/xml-tags.xml:1742(para)
+msgid ""
+"To show a prompt, such as a root or DOS prompt, use the <command><"
+"prompt></command> and <command></prompt></command> commands. For "
+"example:"
+msgstr ""
+"Para mostrar uma linha de comandos, como a linha de comandos do 'root' ou do "
+"DOS, use os comandos <command><prompt></command> e <command></"
+"prompt></command>. Por exemplo:"
+d1453 3
+a1455 15
+#: en_US/xml-tags.xml:1748(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"At the <prompt>LILO:</prompt> boot prompt, type linux to \n"
+"boot into your Linux partition.\n"
+"\n"
+"At the <prompt>C:\\></prompt> prompt, type ....\n"
+msgstr ""
+"\n"
+"Na linha de comandos <prompt>LILO:</prompt>, escreva 'linux'\n"
+"para arrancar para a sua partição de Linux.\n"
+"boot into your Linux partition.\n"
+"\n"
+"Na linha de comandos <prompt>C:\\></prompt>, escreva ....\n"
+d1457 1
+a1457 1
+#: en_US/xml-tags.xml:1760(para)
+d1459 2
+a1460 2
+"At the <prompt>LILO:</prompt> boot prompt, type linux to boot into your "
+"Linux partition."
+d1462 2
+a1463 2
+"Na linha de comandos <prompt>LILO:</prompt>, escreva 'linux' para arrancar "
+"para a sua partição de Linux."
+d1465 3
+a1467 3
+#: en_US/xml-tags.xml:1764(para)
+msgid "At the <prompt>C:\\></prompt> prompt, type ...."
+msgstr "Na linha de comandos <prompt>C:\\></prompt>, escreva ...."
+d1469 3
+a1471 10
+#: en_US/xml-tags.xml:1770(para)
+msgid ""
+"When showing example computer output (usually in <command>screen</command> "
+"tags), do not include the prompt or command (unless the command or prompt is "
+"the actually computer output you want to show)."
+msgstr ""
+"Ao mostrar um exemplo de resultados do computador (normalmente em marcas "
+"<command>screen</command>), não inclua a linha de comandos ou o comando em "
+"si (a menos que este seja de facto o resultado do computador que deseja "
+"mostrar)."
+d1473 3
+a1475 3
+#: en_US/xml-tags.xml:1779(command) en_US/xml-tags.xml:1783(secondary)
+msgid "replaceable"
+msgstr "replaceable"
+d1477 3
+a1479 9
+#: en_US/xml-tags.xml:1786(para)
+msgid ""
+"To create replaceable text, use the tags <command><replaceable></"
+"command> and <command></replaceable></command> around the text you "
+"want to use as a variable."
+msgstr ""
+"Para criar texto que poderá ser substituído, use as marcas <command><"
+"replaceable></command> e <command></replaceable></command> em torno "
+"do texto que deseja usar como variável."
+d1481 3
+a1483 7
+#: en_US/xml-tags.xml:1792(para)
+msgid ""
+"This example demonstrates how to use the <command>replaceable</command> tags "
+"when referencing the name of an RPM file:"
+msgstr ""
+"Este exemplo demonstra como usar as marcas <command>replaceable</command> na "
+"referência ao nome de um ficheiro RPM:"
+d1485 3
+a1487 8
+#: en_US/xml-tags.xml:1796(screen)
+#, no-wrap
+msgid ""
+"\n"
+"foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm\n"
+msgstr ""
+"\n"
+"xpto-<replaceable>número-versão</replaceable>.<replaceable>arquitectura</replaceable>.rpm\n"
+d1489 3
+a1491 3
+#: en_US/xml-tags.xml:1805(replaceable)
+msgid "version-number"
+msgstr "número-versão"
+d1493 3
+a1495 3
+#: en_US/xml-tags.xml:1805(replaceable)
+msgid "arch"
+msgstr "arquitectura"
+d1497 3
+a1499 8
+#: en_US/xml-tags.xml:1804(screen)
+#, no-wrap
+msgid ""
+"\n"
+"foo-<placeholder-1/>.<placeholder-2/>.rpm\n"
+msgstr ""
+"\n"
+"xpto-<placeholder-1/>.<placeholder-2/>.rpm\n"
+d1501 3
+a1503 67
+#: en_US/xml-tags.xml:1816(para)
+msgid ""
+"The <command><screen></command> command is used to format text within "
+"a document and is great for adding emphasis to show examples of code, "
+"computer output, and more. In HTML with the Fedora CSS file, this appears in "
+"box with a grey background. To use this command you only need the opening "
+"<command><screen></command> and closing <command></screen></"
+"command> tags around the text you are emphasizing."
+msgstr ""
+"O comando <command><screen></command> é usado para formatar o texto "
+"dentro de um documento e é óptimo para adicionar alguma ênfase na "
+"apresentação de exemplos de código, resultados do computador, entre outras "
+"coisas. No HTML, com o ficheiro CSS do Fedora, este aparecerá numa caixa com "
+"um fundo cinzento. Para usar este comando, só necessita do <command><"
+"screen></command> de abertura e de delimitar o texto que deseja realçar "
+"com a marca <command></screen></command> de fecho."
+
+#: en_US/xml-tags.xml:1828(para)
+msgid ""
+"When using the <command><screen></command> tag, set everything within "
+"that screen to flush left. The contents of the <sgmltag class=\"starttag"
+"\">screen</sgmltag> element are rendered exactly as is, including any "
+"indentation. Using flush left prevents extra blank space in front of the "
+"text inside the gray background when the content is converted to HTML."
+msgstr ""
+"Ao usar a marca <command><screen></command>, configure tudo dentro "
+"desse ecrã para se colocar à esquerda. O conteúdo do elemento <sgmltag class="
+"\"starttag\">screen</sgmltag> é representado tal-e-qual, incluindo a "
+"indentação. Se usar a remoção à esquerda, impede que apareçam espaços em "
+"branco extra à frente do texto, dentro do fundo cinzento, quando o conteúdo "
+"for convertido para HTML."
+
+#: en_US/xml-tags.xml:1838(para)
+msgid ""
+"The <command><screen></command> tag set may contain other inline tags, "
+"such as <command><computeroutput></command>, <command><userinput>"
+"</command>, or <command><replaceable></command>. Additional inline "
+"tags are not required by definition. The <command><screen></command> "
+"tags by themselves may provide sufficient context, especially for simple "
+"examples or file listings. Consider the context of the example, and use "
+"inline tags if they are helpful to the reader."
+msgstr ""
+"A marca <command><screen></command> poderá conter outras marcas "
+"incorporadas, como a <command><computeroutput></command>, a "
+"<command><userinput></command> ou a <command><replaceable></"
+"command>. As outras marcas incorporadas não são obrigatórias por definição. "
+"As marcas <command><screen></command> propriamente ditas poderão "
+"oferecer um contexto suficiente, especialmente no caso dos exemplos simples "
+"ou das listagens de ficheiros. Considere o contexto do exemplo e use as "
+"marcas incorporadas se forem úteis para o leitor."
+
+#: en_US/xml-tags.xml:1849(para)
+msgid ""
+"If you use inline tags, remember that line breaks inside <command><"
+"screen></command> tags create line breaks in any rendered output. Place "
+"any inline tags <emphasis>on the same line</emphasis> as their content. Do "
+"not overuse tagging within a <command><screen></command> tag set."
+msgstr ""
+"Se usar as marcas incorporadas, recorde-se que as quebras de linha dentro "
+"das marcas <command><screen></command> criam quebras de linha no "
+"resultado apresentado. Coloque as marcas incorporadas <emphasis>na mesma "
+"linha</emphasis> que o seu conteúdo. Não sobrecarregue com marcas dentro de "
+"uma marca <command><screen></command>."
+
+#: en_US/xml-tags.xml:1857(para)
+msgid "An example of <command><screen></command> is the following:"
+msgstr "Um exemplo do <command><screen></command> é o seguinte:"
+d1505 3
+a1507 12
+#: en_US/xml-tags.xml:1862(computeroutput)
+#, no-wrap
+msgid ""
+"<screen>\n"
+"This is an example of a screen. You do not need &lt;para&gt; tags\n"
+"within this command.\n"
+"</screen>"
+msgstr ""
+"<screen>\n"
+"Este é um exemplo de um ecrã. Não precisa de marcas &lt;para&gt;\n"
+"dentro deste comando.\n"
+"</screen>"
+d1509 3
+a1511 10
+#: en_US/xml-tags.xml:1872(screen)
+#, no-wrap
+msgid ""
+"\n"
+"This is an example of a screen. You do not need <para> tags\n"
+"within this command.\n"
+msgstr ""
+"\n"
+"Este é um exemplo de um ecrã. Não precisa de marcas <para>\n"
+"dentro deste comando.\n"
+d1513 1
+a1513 56
+#: en_US/xml-tags.xml:1878(title)
+msgid "Using Inline Tags with <command>screen</command>"
+msgstr "Usar Marcas Incorporadas com o <command>screen</command>"
+
+#: en_US/xml-tags.xml:1879(para)
+msgid ""
+"If you choose to use inline tags inside a <command><screen></command> "
+"section, follow these guidelines for consistency. If the content in the "
+"screen is a listing of a configuration file or the output of a program, use "
+"the <command><computeroutput></command> tag set around the entire "
+"output. If the user should type the example on the command line or in a "
+"configuration file, use the <command><userinput></command> tag set. "
+"Separate input and output with a short sentence of narrative, as below:"
+msgstr ""
+"Se optar por usar marcas incorporadas dentro de uma secção <command><"
+"screen></command>, siga estas instruções por razões de consistência. Se o "
+"conteúdo no ecrã for uma listagem de um ficheiro de configuração ou o "
+"resultado de um programa, use a marca <command><computeroutput></"
+"command> em torno do resultado completo. Se o utilizador deverá escrever o "
+"exemplo na linha de comandos ou num ficheiro de configuração, use a marca "
+"<command><userinput></command>. Separe as entradas e saídas com uma "
+"pequena frase narrativa, como aparece em baixo:"
+
+#: en_US/xml-tags.xml:1892(command) en_US/xml-tags.xml:1900(command)
+#: en_US/xml-tags.xml:1949(command)
+msgid "<para>"
+msgstr "<para>"
+
+#: en_US/xml-tags.xml:1894(command) en_US/xml-tags.xml:1902(command)
+#: en_US/xml-tags.xml:1951(command)
+msgid "</para>"
+msgstr "</para>"
+
+#: en_US/xml-tags.xml:1897(command) en_US/xml-tags.xml:1954(command)
+msgid "<userinput>"
+msgstr "<userinput>"
+
+#: en_US/xml-tags.xml:1897(command) en_US/xml-tags.xml:1954(command)
+msgid "</userinput>"
+msgstr "</userinput>"
+
+#: en_US/xml-tags.xml:1898(command) en_US/xml-tags.xml:1906(command)
+#: en_US/xml-tags.xml:1955(command)
+msgid "</screen>"
+msgstr "</screen>"
+
+#: en_US/xml-tags.xml:1905(command)
+msgid "<computeroutput>"
+msgstr "<computeroutput>"
+
+#: en_US/xml-tags.xml:1905(command)
+msgid "</computeroutput>"
+msgstr "</computeroutput>"
+
+#: en_US/xml-tags.xml:1891(screen)
+#, no-wrap
+d1515 1
+a1515 16
+"\n"
+"\t<placeholder-1/>\n"
+"\t Type the following command:\n"
+"\t<placeholder-2/>\n"
+"\n"
+"<placeholder-3/>\n"
+"<placeholder-4/>command -sw file1<placeholder-5/>\n"
+"<placeholder-6/>\n"
+"\n"
+"\t<placeholder-7/>\n"
+"\t You should see the following output:\n"
+"\t<placeholder-8/>\n"
+"\n"
+"<placeholder-9/>\n"
+"<placeholder-10/>Completed, time = 0.12 sec<placeholder-11/>\n"
+"<placeholder-12/>\n"
+d1517 2
+a1518 20
+"\n"
+"\t<placeholder-1/>\n"
+"\t Escreva o seguinte comando:\n"
+"\t<placeholder-2/>\n"
+"\n"
+"<placeholder-3/>\n"
+"<placeholder-4/>comando -sw ficheiro1<placeholder-5/>\n"
+"<placeholder-6/>\n"
+"\n"
+"\t<placeholder-7/>\n"
+"\t Deverá ver o seguinte resultado:\n"
+"\t<placeholder-8/>\n"
+"\n"
+"<placeholder-9/>\n"
+"<placeholder-10/>Completo, tempo = 0.12 s<placeholder-11/>\n"
+"<placeholder-12/>\n"
+
+#: en_US/xml-tags.xml:1913(para)
+msgid "Type the following command:"
+msgstr "Escreva o seguinte comando:"
+d1520 3
+a1522 4
+#: en_US/xml-tags.xml:1918(userinput)
+#, no-wrap
+msgid "command -sw file1"
+msgstr "comando -sw ficheiro1"
+d1524 3
+a1526 3
+#: en_US/xml-tags.xml:1921(para)
+msgid "You should see the following output:"
+msgstr "Deverá ver o seguinte resultado:"
+d1528 3
+a1530 4
+#: en_US/xml-tags.xml:1926(computeroutput)
+#, no-wrap
+msgid "Completed, time = 0.12 sec"
+msgstr "Completo, tempo = 0.12 s"
+d1532 1
+a1532 1
+#: en_US/xml-tags.xml:1931(para)
+d1534 2
+a1535 2
+"When showing a command or series of commands inside <command>screen</"
+"command> tags, do not show the prompt."
+d1537 2
+a1538 28
+"Ao mostrar um comando ou uma série de comandos dentro das marcas "
+"<command>screen</command>, não mostre a linha de comandos."
+
+#: en_US/xml-tags.xml:1937(para)
+msgid ""
+"If the <command><screen></command> shows the reader how to change only "
+"<emphasis>part</emphasis> of a line, mark the change with an inline "
+"<command><userinput></command> tag set. You may use the <command><"
+"userinput></command> tag set inside a larger area that is already marked "
+"inline with <command><computeroutput></command>. Do not include any "
+"extra lines of context in this case, unless excluding them would confuse the "
+"reader. The following example illustrates these guidelines:"
+msgstr ""
+"Se o <command><screen></command> mostrar ao leitor como alterar apenas "
+"<emphasis>parte</emphasis> de uma linha, marque a alteração com um conjunto "
+"de marcas <command><userinput></command>. Poderá usar o conjunto de "
+"marcas <command><userinput></command> dentro de uma área maior que já "
+"esteja marcada dentro de um <command><computeroutput></command>. Não "
+"inclua as linhas extra de contexto neste caso, a menos que a sua exclusão "
+"possa confundir o leitor. O seguinte exemplo demonstra estas regras:"
+
+#: en_US/xml-tags.xml:1950(command)
+msgid "<filename>"
+msgstr "<filename>"
+
+#: en_US/xml-tags.xml:1950(command)
+msgid "</filename>"
+msgstr "</filename>"
+d1540 3
+a1542 33
+#: en_US/xml-tags.xml:1948(screen)
+#, no-wrap
+msgid ""
+"\n"
+"\t<placeholder-1/>\n"
+"\t Edit the <placeholder-2/>/etc/sysconfig/init<placeholder-3/> file as follows:\n"
+"\t<placeholder-4/>\n"
+"\n"
+"<placeholder-5/>\n"
+"GRAPHICAL=<placeholder-6/>yes<placeholder-7/> \n"
+"<placeholder-8/>\n"
+msgstr ""
+"\n"
+"\t<placeholder-1/>\n"
+"\t Edite o ficheiro <placeholder-2/>/etc/sysconfig/init<placeholder-3/> como se segue:\n"
+"\t<placeholder-4/>\n"
+"\n"
+"<placeholder-5/>\n"
+"GRAPHICAL=<placeholder-6/>yes<placeholder-7/> \n"
+"<placeholder-8/>\n"
+
+#: en_US/xml-tags.xml:1962(para)
+msgid "Edit the <filename>/etc/sysconfig/init</filename> file as follows:"
+msgstr ""
+"Edite o ficheiro <filename>/etc/sysconfig/init</filename> como se segue:"
+
+#: en_US/xml-tags.xml:1967(userinput) en_US/xml-tags.xml:2153(entry)
+#: en_US/xml-tags.xml:2154(entry) en_US/xml-tags.xml:2158(entry)
+#: en_US/xml-tags.xml:2159(entry) en_US/xml-tags.xml:2163(entry)
+#: en_US/xml-tags.xml:2164(entry)
+#, no-wrap
+msgid "yes"
+msgstr "yes"
+d1544 3
+a1546 8
+#: en_US/xml-tags.xml:1966(screen)
+#, no-wrap
+msgid ""
+"\n"
+"GRAPHICAL=<placeholder-1/>\n"
+msgstr ""
+"\n"
+"GRAPHICAL=<placeholder-1/>\n"
+d1548 3
+a1550 35
+#: en_US/xml-tags.xml:1970(para)
+msgid ""
+"For an explanation of how to use the <command>replaceable</command> tags "
+"within a set of <command>screen</command> tags, refer to <xref linkend=\"sn-"
+"xml-tags-replaceable\"/>."
+msgstr ""
+"Para uma explicação de como usar as marcas <command>replaceable</command> "
+"dentro das marcas <command>screen</command>, veja em <xref linkend=\"sn-xml-"
+"tags-replaceable\"/>."
+
+#: en_US/xml-tags.xml:1980(title)
+msgid "Sections"
+msgstr "Secções"
+
+#: en_US/xml-tags.xml:1984(secondary) en_US/xml-tags.xml:1988(primary)
+msgid "sections"
+msgstr "secções"
+
+#: en_US/xml-tags.xml:1991(para)
+msgid ""
+"Within an article (or chapter if it is a DocBook XML book like the "
+"<citetitle>Installation Guide</citetitle>), you can have sections and "
+"subsections. <command><section></command> is always the highest "
+"section and you cannot have two sections of the same level within one "
+"another (a section 2 can be created within a section 1, but section 1 has to "
+"be closed before another section 1 can be created). The general layout "
+"follows:"
+msgstr ""
+"Dentro de um artigo (ou capítulo, se for um livro de DocBook em XML, como o "
+"<citetitle>Guia de Instalação</citetitle>), você poderá ter secções e sub-"
+"secções. A <command><section></command> é sempre a secção do nível de "
+"topo e não poderá ter duas secções ao mesmo nível dentro de outra (uma "
+"secção 2 poderá ser criada dentro de uma secção 1, mas a secção 1 terá de "
+"ser fechada antes de poder criar outra secção 1). Segue-se a disposição "
+"geral:"
+d1552 1
+a1552 2
+#: en_US/xml-tags.xml:2000(computeroutput)
+#, no-wrap
+d1554 2
+a1555 25
+"\n"
+"<section id=\"sn-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"\n"
+"\n"
+" <section id=\"sn-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"\n"
+" <sect3 id=\"s3-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"\n"
+" </sect3>\n"
+"\n"
+" </section>\n"
+"\n"
+"</section>\n"
+d1557 2
+a1558 25
+"\n"
+"<section id=\"sn-nomeunico\">\n"
+" <title>Indique Aqui o Título</title>\n"
+" <para>\n"
+" O texto do conteúdo vem aqui.\n"
+" </para>\n"
+"\n"
+"\n"
+" <section id=\"sn-nomeunico\">\n"
+" <title>Indique Aqui o Título</title>\n"
+" <para>\n"
+" O texto do conteúdo vem aqui.\n"
+" </para>\n"
+"\n"
+" <sect3 id=\"s3-nomeunico\">\n"
+" <title>Indique Aqui o Título</title>\n"
+" <para>\n"
+" O texto do conteúdo vem aqui.\n"
+" </para>\n"
+"\n"
+" </sect3>\n"
+"\n"
+" </section>\n"
+"\n"
+"</section>\n"
+d1560 3
+a1562 7
+#: en_US/xml-tags.xml:2028(para)
+msgid ""
+"If you only need one level of sections in a DocBook article, you can use the "
+"<command>section</command> tag. For example:"
+msgstr ""
+"Se só necessitar de um nível de secções num artigo em DocBook, poderá usar a "
+"marca <command>section</command>. Por exemplo:"
+d1564 1
+a1564 2
+#: en_US/xml-tags.xml:2034(computeroutput)
+#, no-wrap
+d1566 3
+a1568 13
+"\n"
+"<section id=\"sn-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"</section>\n"
+"<section id=\"sn-anothername\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" More body text goes here.\n"
+" </para>\n"
+"</section>\n"
+d1570 4
+a1573 21
+"\n"
+"<section id=\"sn-nomeunico\">\n"
+" <title>Indique o Título Aqui</title>\n"
+" <para>\n"
+" O texto do conteúdo vem aqui.\n"
+" </para>\n"
+"</section>\n"
+"<section id=\"sn-outronome\">\n"
+" <title>Indique o Título Aqui</title>\n"
+" <para>\n"
+" Vem mais texto de conteúdo aqui.\n"
+" </para>\n"
+"</section>\n"
+
+#: en_US/xml-tags.xml:2059(para)
+msgid "The following is an example of creating a table."
+msgstr "Segue-se um exemplo de criação de uma tabela."
+
+#: en_US/xml-tags.xml:2066(command)
+msgid "\"tb-mockup-before-begin.\""
+msgstr "\"tb-teste-antes-inicio.\""
+d1575 3
+a1577 7
+#: en_US/xml-tags.xml:2065(emphasis)
+msgid ""
+"This tells XML that you will be creating a table and the ID name is "
+"<placeholder-1/>"
+msgstr ""
+"Isto diz ao XML que irá criar uma tabela e que o seu nome identificador é "
+"<placeholder-1/>"
+d1579 3
+a1581 3
+#: en_US/xml-tags.xml:2071(emphasis)
+msgid "This tells XML that you are creating a table with three columns."
+msgstr "Isto diz ao XML que irá criar uma tabela com três colunas."
+d1583 5
+a1587 3
+#: en_US/xml-tags.xml:2075(command)
+msgid "colspec"
+msgstr "colspec"
+d1589 3
+a1591 5
+#: en_US/xml-tags.xml:2075(emphasis)
+msgid ""
+"<placeholder-1/> says that you are giving information about the column to XML"
+msgstr ""
+"O <placeholder-1/> indica que está a dar informações acerca da coluna ao XML"
+d1593 3
+a1595 3
+#: en_US/xml-tags.xml:2076(command)
+msgid "colnum=\"1\""
+msgstr "colnum=\"1\""
+d1597 2
+a1598 4
+#: en_US/xml-tags.xml:2076(emphasis)
+msgid ""
+"<placeholder-1/> says that you are giving specifications for the first "
+"column."
+d1600 1
+a1600 2
+"O <placeholder-1/> indica que está a introduzir definições para a primeira "
+"coluna."
+d1602 3
+a1604 3
+#: en_US/xml-tags.xml:2079(command)
+msgid "colname=\"Features\""
+msgstr "colname=\"Funcionalidades\""
+d1606 3
+a1608 5
+#: en_US/xml-tags.xml:2079(emphasis)
+msgid ""
+"<placeholder-1/> says that the title for this column will be \"Features.\""
+msgstr ""
+"O <placeholder-1/> diz que o título desta coluna será \"Funcionalidades.\""
+d1610 1
+a1610 5
+#: en_US/xml-tags.xml:2082(command)
+msgid "colwidth=\"3\""
+msgstr "colwidth=\"3\""
+
+#: en_US/xml-tags.xml:2082(emphasis)
+d1612 2
+a1613 7
+"<placeholder-1/> specifies the width of the column. This can be more tricky: "
+"such as two columns with widths of 1 and 2,the 1 is one-half the width of "
+"the 2, in respect to the page size. But, what if you need the 1 to be a "
+"little more than half of the 2, using a larger number ratio, such as 10 to "
+"20 would accomplish this. You could then change the 10 to an 11 or a 12 to "
+"make it a little more than half of the second column of 20. In no value is "
+"given, a value of 1 is assumed."
+d1615 2
+a1616 7
+"O <placeholder-1/> define a largura da coluna. Isto poderá ser mais "
+"complicado: se tiver duas colunas com larguras 1 e 2, a 1 terá metade da "
+"largura da 2, no que respeita ao tamanho da página. Contudo, se precisar que "
+"a 1 seja um pouco mais de metade da 2, se usar uma proporção maior, como o "
+"10 ou 20, será mais fácil de fazer isto. Poderá então alterar o 10 para um "
+"11 ou 12, de modo a torná-lo um pouco mais de metade da segunda coluna com "
+"20. Se não for indicado nenhum valor, será usado o valor 1."
+d1618 3
+a1620 3
+#: en_US/xml-tags.xml:2096(emphasis)
+msgid "Contains one or more table row elements."
+msgstr "Contém um ou mais elementos de linhas da tabela."
+d1622 15
+a1636 3
+#: en_US/xml-tags.xml:2099(emphasis)
+msgid "Contains one or more table cell (entry) elements."
+msgstr "Contém um ou mais elementos de células (itens) da tabela."
+d1638 3
+a1640 7
+#: en_US/xml-tags.xml:2102(emphasis)
+msgid ""
+"Table cell element, one of several in a row element, defining columns within "
+"the row."
+msgstr ""
+"Elemento de célula da tabela, um de vários num elemento da linha, a definir "
+"as colunas dentro da linha."
+d1642 3
+a1644 4
+#: en_US/xml-tags.xml:2111(emphasis)
+msgid "Contains one or more row elements, for the main text of the table."
+msgstr ""
+"Contém um ou mais elementos de linhas, para o texto principal da tabela."
+d1646 1
+a1646 2
+#: en_US/xml-tags.xml:2063(screen)
+#, no-wrap
+d1648 2
+a1649 54
+"\n"
+"<table id=\"tb-mockup-before-begin\">\n"
+" <placeholder-1/>\n"
+"\n"
+"<title>Available Features of GNOME and KDE</title>\n"
+"\n"
+"<tgroup cols=\"3\">\n"
+" <placeholder-2/>\n"
+"\n"
+"<colspec colnum=\"1\" colname=\"Features\" colwidth=\"3\"/>\n"
+" <placeholder-3/> <placeholder-4/>\n"
+" \n"
+" <placeholder-5/>\n"
+" \n"
+" <placeholder-6/>\n"
+"\n"
+"<colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/>\n"
+"<colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/>\n"
+"\n"
+"<thead>\n"
+" <placeholder-7/>\n"
+"\n"
+"<row> \n"
+" <placeholder-8/>\n"
+"\n"
+"<entry>Features</entry>\n"
+" <placeholder-9/>\n"
+"\n"
+"<entry>GNOME</entry> \n"
+"<entry>KDE</entry>\n"
+"</row> \n"
+"</thead> \n"
+"\n"
+"<tbody> \n"
+" <placeholder-10/>\n"
+"\n"
+"<row> \n"
+"<entry>highly configurable</entry> \n"
+"<entry>yes</entry> \n"
+"<entry>yes</entry> \n"
+"</row> \n"
+"<row> \n"
+"<entry>multiple window managers </entry>\n"
+"<entry>yes</entry> \n"
+"<entry>yes</entry> \n"
+"</row> \n"
+"<row> \n"
+"<entry>Internet applications</entry> \n"
+"<entry>yes </entry> \n"
+"<entry>yes </entry> \n"
+"</row> \n"
+"</tbody> \n"
+"</tgroup> \n"
+"</table> \n"
+d1651 6
+a1656 113
+"\n"
+"<table id=\"tb-teste-antes-inicio\">\n"
+" <placeholder-1/>\n"
+"\n"
+"<title>Funcionalidades Disponíveis no GNOME e no KDE</title>\n"
+"\n"
+"<tgroup cols=\"3\">\n"
+" <placeholder-2/>\n"
+"\n"
+"<colspec colnum=\"1\" colname=\"Funcionalidades\" colwidth=\"3\"/>\n"
+" <placeholder-3/> <placeholder-4/>\n"
+" \n"
+" <placeholder-5/>\n"
+" \n"
+" <placeholder-6/>\n"
+"\n"
+"<colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/>\n"
+"<colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/>\n"
+"\n"
+"<thead>\n"
+" <placeholder-7/>\n"
+"\n"
+"<row> \n"
+" <placeholder-8/>\n"
+"\n"
+"<entry>Funcionalidades</entry>\n"
+" <placeholder-9/>\n"
+"\n"
+"<entry>GNOME</entry> \n"
+"<entry>KDE</entry>\n"
+"</row> \n"
+"</thead> \n"
+"\n"
+"<tbody> \n"
+" <placeholder-10/>\n"
+"\n"
+"<row> \n"
+"<entry>altamente configurável</entry> \n"
+"<entry>sim</entry> \n"
+"<entry>sim</entry> \n"
+"</row> \n"
+"<row> \n"
+"<entry>vários gestores de janelas</entry>\n"
+"<entry>sim</entry> \n"
+"<entry>sim</entry> \n"
+"</row> \n"
+"<row> \n"
+"<entry>Aplicações para a Internet</entry> \n"
+"<entry>sim</entry> \n"
+"<entry>sim</entry> \n"
+"</row> \n"
+"</tbody> \n"
+"</tgroup> \n"
+"</table> \n"
+
+#: en_US/xml-tags.xml:2135(title)
+msgid "Available Features of GNOME and KDE"
+msgstr "Funcionalidades Disponíveis no GNOME e no KDE"
+
+#: en_US/xml-tags.xml:2145(entry)
+msgid "GNOME"
+msgstr "GNOME"
+
+#: en_US/xml-tags.xml:2146(entry)
+msgid "KDE"
+msgstr "KDE"
+
+#: en_US/xml-tags.xml:2152(entry)
+msgid "highly configurable"
+msgstr "altamente configurável"
+
+#: en_US/xml-tags.xml:2157(entry)
+msgid "multiple window managers"
+msgstr "vários gestores de janelas"
+
+#: en_US/xml-tags.xml:2162(entry)
+msgid "Internet applications"
+msgstr "Aplicações para a Internet"
+
+#: en_US/xml-tags.xml:2171(title)
+msgid "Creating a List Within a Table"
+msgstr "Criar uma Lista Dentro de uma Tabela"
+
+#: en_US/xml-tags.xml:2176(tertiary)
+msgid "list within a table"
+msgstr "lista dentro de uma tabela"
+
+#: en_US/xml-tags.xml:2180(para)
+msgid ""
+"Creating a list within a table can be a difficult task. It requires strict "
+"formatting and a set of commands that are not available for command "
+"completion in <application>Emacs</application>."
+msgstr ""
+"A criação de uma lista dentro de uma tabela poderá ser uma tarefa "
+"complicada. Necessita de uma formatação restrita e de um conjunto de "
+"comandos que não estão disponíveis na completação de comandos no "
+"<application>Emacs</application>."
+
+#: en_US/xml-tags.xml:2185(para)
+msgid ""
+"The tags you will need to use are <command><simplelist></command> and "
+"<command><member></command>."
+msgstr ""
+"As marcas que terá de usar são a <command><simplelist></command> e a "
+"<command><member></command>."
+
+#: en_US/xml-tags.xml:2189(para)
+msgid ""
+"The following example will show you the proper formatting for creating a "
+"list within a table."
+msgstr ""
+"O exemplo que se segue mostrar-lhe-á a devida formatação para criar uma "
+"lista dentro de uma tabela."
+d1658 3
+a1660 132
+#: en_US/xml-tags.xml:2194(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<table id=\"tb-hardware-powerswitch\">\n"
+" <title>Power Switch Hardware Table</title>\n"
+" <tgroup cols=\"4\">\n"
+" <colspec colnum=\"1\" colname=\"Hardware\" colwidth=\"2\"/>\n"
+" <colspec colnum=\"2\" colname=\"Quantity\" colwidth=\"2\"/>\n"
+" <colspec colnum=\"3\" colname=\"Description\" colwidth=\"6\"/> \n"
+" <colspec colnum=\"4\" colname=\"Required\" colwidth=\"2\"/>\n"
+"\n"
+" <thead>\n"
+"\t <row>\n"
+" <entry>Hardware</entry>\n"
+"\t <entry>Quantity</entry>\n"
+" <entry>Description</entry>\n"
+"\t <entry>Required</entry>\n"
+"\t </row>\n"
+" </thead>\n"
+"\t \n"
+" <tbody>\n"
+"\t \n"
+"\t<row>\n"
+" <entry>Serial power switches</entry>\n"
+"\n"
+"\t <entry>Two</entry>\n"
+"\n"
+"\t <entry><simplelist> <member>Power switches enable each cluster system\n"
+"\t to power-cycle the other cluster system. Note that clusters are\n"
+"\t configured with either serial or network attached power switches and\n"
+"\t not both.</member>\n"
+"\t\t \n"
+" <member>The following serial attached power switch has been\n"
+"\t fully tested:</member>\n"
+"\n"
+" <member>RPS-10 (model M/HD in the US, and model M/EC in\n"
+"\t Europe) </member>\n"
+"\n"
+" <member>Latent support is provided for the following serial\n"
+"\t attached power switch. This switch has not yet been fully\n"
+" tested:</member>\n"
+"\t\t \n"
+"\t <member>APC Serial On/Off Switch (partAP9211), <ulink\n"
+" url=\"http://www.apc.com/\">http://www.apc.com/</ulink></member>\n"
+" </simplelist></entry>\n"
+"\n"
+" <entry>Strongly recommended for data integrity under all failure\n"
+"\t conditions</entry>\n"
+"\n"
+"\t </row>\n"
+" </tbody>\n"
+" </tgroup>\n"
+"</table>\n"
+msgstr ""
+"\n"
+"<table id=\"tb-hardware-interruptor\">\n"
+" <title>Tabela de 'Hardware' de Interruptores</title>\n"
+" <tgroup cols=\"4\">\n"
+" <colspec colnum=\"1\" colname=\"Hardware\" colwidth=\"2\"/>\n"
+" <colspec colnum=\"2\" colname=\"Quantidade\" colwidth=\"2\"/>\n"
+" <colspec colnum=\"3\" colname=\"Descrição\" colwidth=\"6\"/> \n"
+" <colspec colnum=\"4\" colname=\"Obrigatório\" colwidth=\"2\"/>\n"
+"\n"
+" <thead>\n"
+"\t <row>\n"
+" <entry>Hardware</entry>\n"
+"\t <entry>Quantidade</entry>\n"
+" <entry>Descrição</entry>\n"
+"\t <entry>Obrigatório</entry>\n"
+"\t </row>\n"
+" </thead>\n"
+"\t \n"
+" <tbody>\n"
+"\t \n"
+"\t<row>\n"
+" <entry>Interruptores série</entry>\n"
+"\n"
+"\t <entry>Dois</entry>\n"
+"\n"
+"\t <entry><simplelist> <member>Os interruptores permitem\n"
+" a cada sistema do 'cluster' controlar a alimentação do outro sistema\n"
+" do 'cluster'. Lembre-se que os 'cluster's são configurados com\n"
+" interruptores série ou ligados à rede, não com ambos.</member>\n"
+"\t\t \n"
+" <member>O interruptor série que se segue foi testado\n"
+"\t por completo:</member>\n"
+"\n"
+" <member>RPS-10 (modelo M/HD nos EUA e modelo M/EC\n"
+"\t na Europa) </member>\n"
+"\n"
+" <member>O suporte latente é oferecido para o seguinte\n"
+" interruptor série. Este interruptor não foi completamente\n"
+" testado:</member>\n"
+"\t\t \n"
+"\t <member>APC Interruptor On/Off Série (partAP9211), <ulink\n"
+" url=\"http://www.apc.com/\">http://www.apc.com/</ulink></member>\n"
+" </simplelist></entry>\n"
+"\n"
+" <entry>Altamente recomendado para a integridade dos dados\n"
+" em todas as condições de falha</entry>\n"
+"\n"
+"\t </row>\n"
+" </tbody>\n"
+" </tgroup>\n"
+"</table>\n"
+
+#: en_US/xml-tags.xml:2248(para)
+msgid ""
+"Notice how the <command><simplelist></command> tag must be beside the "
+"<command><entry></command> tag? If you do not format this properly, it "
+"will not parse cleanly."
+msgstr ""
+"Reparou como a marca <command><simplelist></command> deve estar dentro "
+"da marca <command><entry></command>? Se não formatar isto "
+"correctamente, o processamento não será bem sucedido."
+
+#: en_US/xml-tags.xml:2252(para)
+msgid "The above example will look like the following:"
+msgstr "O exemplo acima ficará como o seguinte:"
+
+#: en_US/xml-tags.xml:2255(title)
+msgid "Power Switch Hardware Table"
+msgstr "Tabela de 'Hardware' de Interruptores"
+
+#: en_US/xml-tags.xml:2264(entry)
+msgid "Hardware"
+msgstr "'Hardware'"
+
+#: en_US/xml-tags.xml:2265(entry)
+msgid "Quantity"
+msgstr "Quantidade"
+d1662 3
+a1664 3
+#: en_US/xml-tags.xml:2266(entry) en_US/emacs.xml:405(segtitle)
+msgid "Description"
+msgstr "Descrição"
+d1666 3
+a1668 3
+#: en_US/xml-tags.xml:2267(entry)
+msgid "Required"
+msgstr "Obrigatório"
+d1670 3
+a1672 3
+#: en_US/xml-tags.xml:2274(entry)
+msgid "Serial power switches"
+msgstr "Interruptores série"
+d1674 3
+a1676 3
+#: en_US/xml-tags.xml:2276(entry)
+msgid "Two"
+msgstr "Dois"
+d1678 3
+a1680 9
+#: en_US/xml-tags.xml:2278(member)
+msgid ""
+"Power switches enable each cluster system to power-cycle the other cluster "
+"system. Note that clusters are configured with either serial or network "
+"attached power switches and not both."
+msgstr ""
+"Os interruptores permitem a cada sistema do 'cluster' controlar a "
+"alimentação do outro sistema do 'cluster'. Lembre-se que os 'cluster's são "
+"configurados com interruptores série ou ligados à rede, não com ambos."
+d1682 3
+a1684 3
+#: en_US/xml-tags.xml:2283(member)
+msgid "The following serial attached power switch has been fully tested:"
+msgstr "O interruptor série que se segue foi testado por completo:"
+d1686 3
+a1688 3
+#: en_US/xml-tags.xml:2286(member)
+msgid "RPS-10 (model M/HD in the US, and model M/EC in Europe)"
+msgstr "RPS-10 (modelo M/HD nos EUA e modelo M/EC na Europa)"
+d1690 3
+a1692 7
+#: en_US/xml-tags.xml:2289(member)
+msgid ""
+"Latent support is provided for the following serial attached power switch. "
+"This switch has not yet been fully tested:"
+msgstr ""
+"O suporte latente é oferecido para o seguinte interruptor série. Este "
+"interruptor não foi completamente testado:"
+d1694 3
+a1696 3
+#: en_US/xml-tags.xml:2294(ulink)
+msgid "http://www.apc.com/"
+msgstr "http://www.apc.com/"
+d1698 3
+a1700 3
+#: en_US/xml-tags.xml:2293(member)
+msgid "APC Serial On/Off Switch (partAP9211), <placeholder-1/>"
+msgstr "APC Interruptor On/Off Série (partAP9211), <placeholder-1/>"
+d1702 3
+a1704 5
+#: en_US/xml-tags.xml:2297(entry)
+msgid "Strongly recommended for data integrity under all failure conditions"
+msgstr ""
+"Altamente recomendado para a integridade dos dados em todas as condições de "
+"falha"
+d1706 3
+a1708 3
+#: en_US/xml-tags.xml:2310(command) en_US/xml-tags.xml:2314(command)
+msgid "trademark"
+msgstr "trademark"
+d1710 3
+a1712 12
+#: en_US/xml-tags.xml:2318(para)
+msgid ""
+"Do not use the trademark entities &trade;, &copy;, or &reg; "
+"because the do not produce HTML output that works for all charsets. The HTML "
+"output produces by these entities are declared in the DTD and cannot be "
+"changed via the stylesheet."
+msgstr ""
+"Não use as entidades de marcas registadas &trade;, &copy; ou &"
+"reg;, dado que não produzem um resultado em HTML que funcione em todas as "
+"codificações de caracteres. O resultado em HTML produzido por estas "
+"entidades está declarado na DTD e não poderá ser alterado com a folha de "
+"estilo."
+d1714 3
+a1716 7
+#: en_US/xml-tags.xml:2323(para)
+msgid ""
+"Instead, use the <command>trademark</command> tag and its associates classes "
+"as follows:"
+msgstr ""
+"Em vez disso, use a marca <command>trademark</command> e as suas classes "
+"associadas, como se segue:"
+d1718 3
+a1720 12
+#: en_US/xml-tags.xml:2328(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<trademark>trademark symbol after me</trademark>\n"
+"<trademark class=\"registered\">registered trademark symbol after me</trademark>\n"
+"<trademark class=\"copyright\">copyright symbol after me</trademark>\n"
+msgstr ""
+"\n"
+"<trademark>símbolo de marca a seguir a mime</trademark>\n"
+"<trademark class=\"registered\">símbolo de marca registada a seguir a mim</trademark>\n"
+"<trademark class=\"copyright\">símbolo de direitos de cópia a seguir a mim</trademark>\n"
+d1722 3
+a1724 3
+#: en_US/xml-tags.xml:2338(command) en_US/xml-tags.xml:2342(command)
+msgid "userinput"
+msgstr "userinput"
+d1726 3
+a1728 7
+#: en_US/xml-tags.xml:2345(para)
+msgid ""
+"To show what a user would type, use the <command>userinput</command> tag. "
+"For example:"
+msgstr ""
+"Para mostrar o que um dado utilizador iria escrever, use a marca "
+"<command>userinput</command>. Por exemplo:"
+d1730 3
+a1732 12
+#: en_US/xml-tags.xml:2350(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"At the prompt, type:\n"
+"\n"
+"<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>\n"
+msgstr ""
+"\n"
+"Na linha de comandos, escreva:\n"
+"\n"
+"<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>\n"
+d1734 3
+a1736 3
+#: en_US/xml-tags.xml:2361(para)
+msgid "At the prompt, type:"
+msgstr "Na linha de comandos, escreva:"
+d1738 3
+a1740 4
+#: en_US/xml-tags.xml:2366(userinput)
+#, no-wrap
+msgid "dd if=boot.img of=/dev/fd0 bs=1440k"
+msgstr "dd if=boot.img of=/dev/fd0 bs=1440k"
+d1742 3
+a1744 4
+#: en_US/xml-tags.xml:2393(command) en_US/xml-tags.xml:2397(secondary)
+#: en_US/emacs.xml:532(computeroutput)
+msgid "ulink"
+msgstr "ulink"
+d1746 3
+a1748 5
+#: en_US/xml-tags.xml:2400(para)
+msgid "To create a URL link within your text, use the following example:"
+msgstr ""
+"Para criar uma hiperligação para um URL dentro do seu texto, use o seguinte "
+"exemplo:"
+d1750 1
+a1750 2
+#: en_US/xml-tags.xml:2404(computeroutput)
+#, no-wrap
+d1752 2
+a1753 4
+"\n"
+"Online &mdash; <ulink url=\"http://www.redhat.com/support/errata/\">\n"
+"http://www.redhat.com/support/errata/</ulink>; supplies errata \n"
+"you can read online, and you can download diskette images easily.\n"
+d1755 6
+a1760 67
+"\n"
+"Online &mdash; <ulink url=\"http://www.redhat.com/support/errata/\">\n"
+"http://www.redhat.com/support/errata/</ulink>; fornece uma errata\n"
+"que poderá ler 'online' e onde poderá transferir imagens de disquetes com facilidade.\n"
+
+#: en_US/xml-tags.xml:2415(para)
+msgid ""
+"Online —<ulink url=\"http://www.redhat.com/support/errata/\"> http://"
+"www.redhat.com/support/errata/</ulink>; supplies errata you can read online, "
+"and you can download diskette images easily."
+msgstr ""
+"Online — <ulink url=\"http://www.redhat.com/support/errata/\">http://"
+"www.redhat.com/support/errata/</ulink>; fornece uma errata que poderá ler "
+"'online' e onde poderá transferir imagens de disquetes com facilidade."
+
+#: en_US/xml-tags.xml:2423(para)
+msgid ""
+"If the URL does not end in a filename, it must end in a slash "
+"(<computeroutput>/</computeroutput>) to be a properly formed URL. For "
+"example, <ulink url=\"http://www.redhat.com/\">http://www.redhat.com/</"
+"ulink>."
+msgstr ""
+"Se o URL não terminar com o nome de um ficheiro, deverá terminar com uma "
+"barra (<computeroutput>/</computeroutput>), de modo a ser um URL "
+"completamente válido. Por exemplo, <ulink url=\"http://www.redhat.com/"
+"\">http://www.redhat.com/</ulink>."
+
+#: en_US/xml-tags.xml:2434(command) en_US/xml-tags.xml:2438(secondary)
+msgid "wordasword"
+msgstr "wordasword"
+
+#: en_US/xml-tags.xml:2441(para)
+msgid ""
+"The <wordasword> tag set is used to define a word meant specifically "
+"as a word and not representing anything else."
+msgstr ""
+"O conjunto de marcas <wordasword> é usado para definir uma palavra que "
+"é suposto representar mesmo uma palavra e não representar outro conceito "
+"qualquer."
+
+#: en_US/xml-tags.xml:2444(para)
+msgid ""
+"A lot of technical documentation contains words that have overloaded "
+"meanings. Sometimes it is useful to be able to use a word without invoking "
+"its technical meaning. The <wordasword> element identifies a word or "
+"phrase that might otherwise be interpreted in some specific way, and asserts "
+"that it should be interpreted simply as a word."
+msgstr ""
+"Diversa documentação contém palavras que têm significados sobrepostos. "
+"Algumas vezes é útil ter a possibilidade de usar uma palavra sem invocar o "
+"seu significado técnico. O elemento <wordasword> identifica uma "
+"palavra ou frase que poderá ser interpretada de alguma forma específica, "
+"indicando que deverá ser interpretada apenas como uma palavra."
+
+#: en_US/xml-tags.xml:2450(para)
+msgid ""
+"It is unlikely that the presentation of this element will be able to help "
+"readers understand the variation in meaning; good writing will have to "
+"achieve that goal. The real value of <wordasword> lies in the fact "
+"that full-text searching and indexing tools can use it to avoid false-"
+"positives."
+msgstr ""
+"É pouco provável que a apresentação deste elemento seja capaz de ajudar os "
+"leitores a compreender a diferença de significado; uma boa escrita terá de "
+"conseguir esse objectivo. O valor real do <wordasword> reside no facto "
+"que as ferramentas de pesquisa e indexação no texto completo podê-la-ão usar "
+"para evitar falsos positivos."
+d1762 1
+a1762 2
+#: en_US/xml-tags.xml:2459(computeroutput)
+#, no-wrap
+d1764 3
+a1766 3
+"To use <command>grep</command> to search for the word\n"
+"<wordasword>linux</wordasword>, use the command \n"
+"<command>grep linux</command>."
+d1768 12
+a1779 3
+"Para usar o <command>grep</command> na pesquisa pela palavra\n"
+"<wordasword>linux</wordasword>, use o comando\n"
+"<command>grep linux</command>."
+d1781 3
+a1783 7
+#: en_US/xml-tags.xml:2468(para)
+msgid ""
+"To use <command>grep</command> to search for the word <wordasword>linux</"
+"wordasword>, use the command <command>grep linux</command>."
+msgstr ""
+"Para usar o <command>grep</command> na pesquisa pela palavra "
+"<wordasword>linux</wordasword>, use o comando <command>grep linux</command>."
+d1785 3
+a1787 11
+#: en_US/xml-tags.xml:2472(para)
+msgid ""
+"In the example, the word \"linux\" is just a word. It is not meant to convey "
+"anything about Linux as a subject, or to add relevance or meaning to the "
+"content. It can be replaced with any other word without losing any of the "
+"context."
+msgstr ""
+"No exemplo, a palavra \"linux\" é apenas uma palavra. Não diz respeito ao "
+"Linux como um assunto nem pretende adicionar relevância ou significado ao "
+"conteúdo. Esta poderá ser substituída por outra palavra qualquer, sem perder "
+"nenhum do contexto."
+d1789 3
+a1791 3
+#: en_US/xml-tags.xml:2481(command) en_US/xml-tags.xml:2485(secondary)
+msgid "xref"
+msgstr "xref"
+d1793 3
+a1795 7
+#: en_US/xml-tags.xml:2488(para)
+msgid ""
+"To refer to other sections or chapters within a manual, use the <command><"
+"xref></command> tag."
+msgstr ""
+"Para fazer referência a outras secções ou capítulos dentro de um manual, use "
+"a marca <command><xref></command>."
+d1797 1
+a1797 1
+#: en_US/xml-tags.xml:2493(para)
+d1799 2
+a1800 2
+"The output of this displays the title of the section or chapter you are "
+"pointing the user to. For example:"
+d1802 2
+a1803 2
+"O resultado disto mostra o título da secção ou capítulo para onde está a "
+"apontar o utilizador. Por exemplo:"
+d1805 1
+a1805 2
+#: en_US/xml-tags.xml:2498(computeroutput)
+#, no-wrap
+d1807 2
+a1808 3
+"\n"
+"For more information about the parent file, refer to\n"
+"<xref linkend=\"ch-tutorial\"></xref> and <xref linkend=\"sn-tutorial-article\"></xref>\n"
+d1810 2
+a1811 3
+"\n"
+"Para mais informações acerca do ficheiro-pai, veja em\n"
+"<xref linkend=\"ch-tutorial\"></xref> e <xref linkend=\"sn-tutorial-parent\"></xref>\n"
+d1813 1
+a1813 1
+#: en_US/xml-tags.xml:2508(para)
+d1815 2
+a1816 2
+"For more information about the parent file, refer to <xref linkend=\"ch-"
+"tutorial\"/> and <xref linkend=\"sn-tutorial-article\"/>."
+d1818 2
+a1819 2
+"Para mais informações acerca do ficheiro-pai, veja em <xref linkend=\"ch-"
+"tutorial\"></xref> e <xref linkend=\"sn-tutorial-parent\"></xref>."
+d1821 3
+a1823 3
+#: en_US/vim.xml:13(title)
+msgid "VIM and DocBook"
+msgstr "O VIM e o DocBook"
+d1825 3
+a1827 3
+#: en_US/vim.xml:16(primary) en_US/vim.xml:33(primary)
+msgid "VIM"
+msgstr "VIM"
+d1829 5
+a1833 1
+#: en_US/vim.xml:19(para)
+d1835 4
+a1838 6
+"VIM has many features to help you write XML content such as DocBook, "
+"including syntax highlighting and customizable key bindings. Additionally, "
+"one can easily use external programs from VIM for features such as spell-"
+"checking. This chapter assumes you already know generally how to use VIM; if "
+"you want to learn how, try the <command>vimtutor</command> or by typing "
+"<userinput>:help tutor</userinput> from inside VIM."
+d1840 4
+a1843 7
+"O VIM tem diversas funcionalidades que o ajudam a criar conteúdos em XML, "
+"como o DocBook, incluindo o realce de sintaxe e a atribuição de atalhos de "
+"teclado personalizados. Para além disso, poderá usar facilmente programas "
+"externos a partir do VIM para funcionalidades como a verificação "
+"ortográfica. Este capítulo assume que já tem algum conhecimento geral de "
+"utilização do VIM; se quiser aprender como, experimente o <command>vimtutor</"
+"command> ou escrevendo <userinput>:help tutor</userinput> dentro do VIM."
+d1845 3
+a1847 3
+#: en_US/vim.xml:30(title)
+msgid "Setting Up Your <filename>.vimrc</filename> File"
+msgstr "Configurar o seu Ficheiro <filename>.vimrc</filename>"
+d1849 3
+a1851 3
+#: en_US/vim.xml:34(secondary) en_US/emacs.xml:44(secondary)
+msgid "configuration file"
+msgstr "ficheiro de configuração"
+d1853 2
+a1854 16
+#: en_US/vim.xml:37(para)
+msgid ""
+"Below is a short sample <filename>.vimrc</filename> file that turns on some "
+"VIM features useful for editing SGML or XML content such as DocBook: "
+"<screen>\n"
+"<computeroutput>\" Turn off vi compatibility settings like limited undo\n"
+"set nocompatible\n"
+"\" Syntax highlighting based on file extension\n"
+"syntax on\n"
+"\" Automatically insert newlines after 80 characters\n"
+"set textwidth=80\n"
+"\" Automatically indent\n"
+"set autoindent\n"
+"\" Match SGML tags with %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+d1856 1
+a1856 15
+"Segue-se um pequeno exemplo do ficheiro <filename>.vimrc</filename> que "
+"activa algumas das funcionalidades úteis do VIM para editar conteúdos em "
+"SGML ou XML, como o DocBook: <screen>\n"
+"<computeroutput>\" Desligar as opções de compatibilidade, como o 'desfazer' "
+"limitado\n"
+"set nocompatible\n"
+"\" Realce de sintaxe com base na extensão do ficheiro\n"
+"syntax on\n"
+"\" Inserir automaticamente mudanças de linha ao fim de 80 caracteres\n"
+"set textwidth=80\n"
+"\" Indentação automática\n"
+"set autoindent\n"
+"\" Corresponder as marcas de SGML com o %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+d1858 1
+a1858 1
+#: en_US/vim.xml:55(para)
+d1860 2
+a1861 6
+"Some of these features require the <filename>vim-enhanced</filename> package "
+"to be installed. If you are using or the <filename>vim-minimal</filename> "
+"package, or if you are using an older version of VIM, you may not have the "
+"<filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still "
+"download <ulink url=\"http://vim.org/scripts/script.php?script_id=39"
+"\">matchit.zip from Vim.org</ulink> and load it separately."
+d1863 22
+a1884 7
+"Algumas destas funcionalidades necessitam de ter instalado o pacote "
+"<filename>vim-enhanced</filename>. Se estiver a usar o pacote <filename>vim-"
+"minimal</filename> ou se estiver a usar uma versão antiga do VIM, poderá não "
+"ter o ficheiro <filename>$VIMRUNTIME/macros/matchit.vim</filename>. Poderá à "
+"mesma transferir o <ulink url=\"http://vim.org/scripts/script.php?"
+"script_id=39\">ficheiro matchit.zip do Vim.org</ulink> e carregá-lo em "
+"separado."
+d1886 3
+a1888 3
+#: en_US/vim.xml:69(title)
+msgid "Keymapping with VIM"
+msgstr "Mapeamento de teclas com o VIM"
+d1890 1
+a1890 1
+#: en_US/vim.xml:71(para)
+d1892 3
+a1894 36
+"VIM can speed up your DocBook creation by mapping frequently typed tags (or "
+"any words or phrases) onto short key combinations. By default, the keymap "
+"leader is the backslash (<literal>\\</literal>), but it can be redefined "
+"with a command like <userinput>let mapleader =\n"
+" \",\"</userinput>. There are two ways to use the following example; "
+"you can put it directly in your <filename>.vimrc</filename>, or you can save "
+"it in a separate file and load it with a <userinput>source</userinput> "
+"command in your <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\n"
+"\" skip ahead to after next tag without leaving insert mode\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\n"
+"\" common tags that start a new text block\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\n"
+"\" common tags that are placed inline\n"
+"\" use <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+"\" entities\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+d1896 7
+a1902 34
+"O VIM poderá acelerar a criação do seu DocBook, mapeando as teclas escritas "
+"com mais frequência (ou palavras ou frases) em combinações de teclas breves. "
+"Por omissão, o líder do mapa de teclados é a barra invertida (<literal>\\</"
+"literal>), mas poderá ser redefinida com um comando do tipo <userinput>let "
+"mapleader =\n"
+" \",\"</userinput>. Existem duas formas de usar o seguinte exemplo; "
+"podê-lo-á colocar direcamente no seu ficheiro <filename>.vimrc</filename> ou "
+"podê-lo-a gravar num ficheiro separado e fazendo referência com o comando "
+"<userinput>source</userinput> no seu <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\" passar à frente, a seguir à próxima marca, sem deixar o modo de inserção\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\" marcas comuns que iniciam um novo bloco de texto\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\" marcas comuns que se colocam de forma incorporada\n"
+"\" use <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+"\" entidades\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+d1904 1
+a1904 1
+#: en_US/vim.xml:110(para)
+d1906 2
+a1907 4
+"Unfortunately, there is not currently a complete macro set for all DocBook "
+"commands, so you will need to define them yourself or customize the "
+"definitions in the examples from <xref linkend=\"sn-vim-additional-resources"
+"\"/>."
+d1909 3
+a1911 4
+"Infelizmente, não existe de momento um conjunto de macros completo para "
+"todos os comandos do DocBook, pelo que terá de os definir você mesmo ou "
+"personalizar as definições nos exemplos em <xref linkend=\"sn-vim-additional-"
+"resources\"/>."
+d1913 3
+a1915 3
+#: en_US/vim.xml:119(title)
+msgid "Additional VIM Resources"
+msgstr "Recursos Adicionais do VIM"
+d1917 3
+a1919 3
+#: en_US/vim.xml:121(para)
+msgid "Additional information about VIM may be found from:"
+msgstr "Poderá encontrar mais informações acerca do VIM em:"
+d1921 3
+a1923 9
+#: en_US/vim.xml:127(para)
+msgid ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to "
+"Vi Improved (VIM)</citetitle>"
+msgstr ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> Exemplo de sgml-vimrc</ulink> do <citetitle>Guia para "
+"principiantes do Vi Improved (VIM)</citetitle>"
+d1925 3
+a1927 7
+#: en_US/vim.xml:134(para)
+msgid ""
+"The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick "
+"Reference Card</ulink>"
+msgstr ""
+"O <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">Cartão de "
+"Referências Rápidas do VIM</ulink>"
+d1929 3
+a1931 3
+#: en_US/vim.xml:140(ulink)
+msgid "Vim as XML Editor"
+msgstr "O Vim como Editor de XML"
+d1933 1
+a1933 1
+#: en_US/vim.xml:145(para)
+d1935 921
+a2855 4
+"The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the "
+"<filename>vim-common</filename> package —<filename>/usr/share/vim/"
+"<replaceable><version></replaceable>/doc/intro.txt</filename> or type "
+"<userinput>:help intro</userinput> from within VIM"
+d2857 79
+a2935 4
+"O <citetitle>MANUAL DE REFERÊNCIA DO VIM</citetitle>, que vem com o pacote "
+"<filename>vim-common</filename> —<filename>/usr/share/vim/"
+"<replaceable><versão></replaceable>/doc/intro.txt</filename> ou "
+"escrevendo <userinput>:help intro</userinput> dentro do VIM"
+d2937 3
+a2939 3
+#: en_US/tutorial.xml:13(title)
+msgid "The Layout of a Tutorial"
+msgstr "O Formato de um Tutorial"
+d2941 1
+a2941 1
+#: en_US/tutorial.xml:14(para)
+d2943 2
+a2944 4
+"In this chapter, you will find an example of a very short tutorial as used "
+"by the Fedora Documentation Project. This example is specific to the way the "
+"Docs Project uses DocBook XML. The example consists of a set of files used "
+"to hold the content and metadata for the tutorial."
+d2946 2
+a2947 5
+"Neste capítulo, irá descobrir um exemplo de um tutorial bastante curto de "
+"documentação do Projecto Fedora. Este exemplo é específico para a forma como "
+"o Projecto de Documentação usa o DocBook em XML. O exemplo consiste num "
+"conjunto de ficheiros usados para manter o conteúdo, bem como meta-dados "
+"para o tutorial."
+d2949 3
+a2951 3
+#: en_US/tutorial.xml:19(title)
+msgid "The Article"
+msgstr "O Artigo"
+d2953 3
+a2955 3
+#: en_US/tutorial.xml:21(primary) en_US/tutorial.xml:56(primary)
+msgid "tutorial layout"
+msgstr "formato do tutorial"
+d2957 3
+a2959 3
+#: en_US/tutorial.xml:22(secondary)
+msgid "article"
+msgstr "artigo"
+d2961 1
+a2961 13
+#: en_US/tutorial.xml:24(para)
+msgid "Below is a sample article:"
+msgstr "Em baixo, encontra-se um artigo de exemplo:"
+
+#: en_US/tutorial.xml:54(title)
+msgid "The Metadata"
+msgstr "Os Meta-Dados"
+
+#: en_US/tutorial.xml:57(secondary)
+msgid "metadata"
+msgstr "meta-dados"
+
+#: en_US/tutorial.xml:59(para)
+d2963 2
+a2964 4
+"The <filename>rpm-info.xml</filename> file contains all the required "
+"metadata for the document. This metadata includes title, authorship, "
+"licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates "
+"the content of this file:"
+d2966 3
+a2968 4
+"O ficheiro <filename>rpm-info.xml</filename> contém todos os meta-dados "
+"necessários para o documento. Estes meta-dados incluem o título, a autoria, "
+"a licença e o histórico de versões. O <xref linkend=\"ex-rpminfo\"/> ilustra "
+"o conteúdo deste ficheiro:"
+d2970 3
+a2972 3
+#: en_US/tutorial.xml:65(title)
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr "Ficheiro <filename>rpm-info.xml</filename> de Exemplo"
+d2974 1
+a2974 1
+#: en_US/tutorial.xml:95(para)
+d2976 5
+a2980 4
+"If you are not familiar with XML editing, copy and paste this file from an "
+"existing module and then edit the values for the various elements as "
+"appropriate. Consult Fedora Documentation Project members and help channels "
+"for more assistance if needed."
+d2982 6
+a2987 5
+"Se não estiver familiarizado com a edição em XML, copie e cole este ficheiro "
+"a partir de um módulo existente e edite depois os valores dos vários "
+"elementos, como for mais apropriado. Consulte os membros do Projecto de "
+"Documentação do Fedora e os canais de ajuda para maior assistência, se for "
+"necessário."
+d2989 1
+a2989 5
+#: en_US/style.xml:14(title)
+msgid "Style"
+msgstr "Estilo"
+
+#: en_US/style.xml:16(para)
+d2991 2
+a2992 5
+"Writing good technical documentation is not simply reproducing command lines "
+"and instruction sets. Good documentation is easy to read, understand, and "
+"translate, and presents a concise logical progression of concepts. Good "
+"documentation can also be defined by what it does <emphasis>not</emphasis> "
+"contain. Your tutorial should avoid:"
+d2994 2
+a2995 5
+"A escrita de boa documentação técnica não é simplemente reproduzir as linhas "
+"de comandos e os conjuntos de instruções. A boa documentação é fácil de ler, "
+"compreender e traduzir, oferecendo uma progressão lógica concisa dos "
+"conceitos. A boa documentação também poderá ser definida pelo que "
+"<emphasis>não</emphasis> contém. O seu tutorial deverá evitar:"
+d2997 3
+a2999 3
+#: en_US/style.xml:26(para)
+msgid "Excessive wordiness"
+msgstr "Uso excessivo de palavras"
+d3001 3
+a3003 3
+#: en_US/style.xml:31(para)
+msgid "Unnecessary or undefined jargon"
+msgstr "Uso de 'calão' técnico indefinido ou desnecessário"
+d3005 3
+a3007 3
+#: en_US/style.xml:36(para)
+msgid "Grammatical or spelling errors"
+msgstr "Erros ortográficos ou gramaticais"
+d3009 3
+a3011 3
+#: en_US/style.xml:41(para)
+msgid "References to yourself or your experiences"
+msgstr "Referências a si próprio ou às suas experiências"
+d3013 3
+a3015 3
+#: en_US/style.xml:46(para)
+msgid "Remarks which might offend or confuse any reader"
+msgstr "Comentários que possam ofender ou confundir qualquer leitor"
+d3017 3
+a3019 14
+#: en_US/style.xml:51(para)
+msgid ""
+"This chapter contains style rules and guidelines for writing Fedora "
+"documentation. Guidelines are not the same as rules. It is acceptable to "
+"violate a guideline when it makes your material easier to understand. Follow "
+"guidelines whenever possible, but follow rules at all times. Assume any "
+"advice is a guideline unless identified otherwise."
+msgstr ""
+"Este capítulo contém regras e instruções de estilo para escrever "
+"documentação para o Fedora. As instruções não são necessariamente regras. É "
+"aceitável voltar uma instrução, se esta tornar o seu material mais fácil de "
+"compreender. Siga as instruções se possível, mas siga sempre as regras. "
+"Assuma que qualquer conselho é uma instrução a menos que seja identificado "
+"em contrário."
+d3021 1
+a3021 5
+#: en_US/style.xml:62(title)
+msgid "Why Style Is Important"
+msgstr "Porque o Estilo é Importante"
+
+#: en_US/style.xml:64(para)
+d3023 3
+a3025 4
+"Writing well comes naturally to almost no one. It is a skill that "
+"professional writers, even famous ones, must practice constantly. "
+"<firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> "
+"is the quality that separates elegant writing from the merely functional."
+d3027 3
+a3029 5
+"A boa escrita não vem naturalmente para a maior parte das pessoas. É um dom "
+"que os escritores profissionais, até mesmo os famosos, precisam de praticar "
+"constantemente. O <firstterm>Estilo</firstterm><indexterm><primary>estilo</"
+"primary></indexterm> é a qualidade que separa a escrita elegante da "
+"meramente funcional."
+d3031 1
+a3031 1
+#: en_US/style.xml:77(para)
+d3033 3
+a3035 4
+"For example, refer to. <ulink url=\"http://www.online-literature.com/"
+"james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/"
+"ulysses/18/</ulink>. Please note that this example contains some mature "
+"themes and language, and is not suitable for all readers."
+d3037 3
+a3039 4
+"Por exemplo, veja em <ulink url=\"http://www.online-literature.com/"
+"james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/"
+"ulysses/18/</ulink>. Rpare por favor como este exemplo contém alguns temas e "
+"linguagem madura, mas não sendo adequado para todos os leitores."
+d3041 3
+a3043 20
+#: en_US/style.xml:71(para)
+msgid ""
+"Elegance comes in many forms. In prose and poetry, elegant writing may not "
+"follow some (or any) common rules of grammar, syntax, or spelling. A good "
+"example is Episode 18, \"Penelope,\" in James Joyce's novel "
+"<citetitle>Ulysses</citetitle><footnote id=\"fn-ulysses\"><placeholder-1/></"
+"footnote>. There, Joyce uses long streams of words without punctuation to "
+"simulate a character's internal consciousness. By violating basic rules of "
+"grammar and syntax, Joyce simulates the disorganized but loosely connected "
+"thought patterns of the narrator."
+msgstr ""
+"A elegância vem em diversas formas. Na prosa e na poesia, a escrita elegante "
+"poderá não seguir algumas (ou todas) as regras comuns da gramática, sintaxe "
+"ou ortografia. Um bom exemplo é o Episódio 18, \"Penélope,\" do romance de "
+"James Joyce <citetitle>Ulisses</citetitle><footnote id=\"fn-ulysses"
+"\"><placeholder-1/></footnote>. Aqui, Joyce usa grandes sequências de "
+"palavras sem pontuação, de modo a simular a consciência interna de uma "
+"personagem. Ao violar as regras básicas da sintaxe e da gramática, Joyce "
+"simula os padrões de pensamento desorganizados mas levemente ligados do "
+"narrador."
+d3045 3
+a3047 17
+#: en_US/style.xml:89(para)
+msgid ""
+"Technical documentation, however, should always respect these rules. The "
+"more a document departs from standard language usage, the more difficult the "
+"material becomes for the reader. For example, readers may not be native "
+"speakers of the language used, or they might be reading a translation. If "
+"the writer uses slang, idioms, or jargon, a reader or translator may easily "
+"become confused. The following example compares two different written "
+"executions of the same idea:"
+msgstr ""
+"Contudo, a documentação técnica deverá sempre respeitar estas regras. Quanto "
+"mais um documento se desviar da utilização comum da língua, mais difícil se "
+"torna o material para o leitor. Por exemplo, os leitores poderão não usar a "
+"língua do documento como língua nativa ou poderão estar a ler uma tradução. "
+"Se o escritor usar 'calão', dialectos ou termos demasiado técnicos, o leitor "
+"ou o tradutor poderão ficar facilmente confusos. O exemplo seguinte compara "
+"duas execuções da mesma ideia, escritas de forma diferente:"
+d3049 3
+a3051 3
+#: en_US/style.xml:100(title)
+msgid "Incorrect style"
+msgstr "Estilo incorrecto"
+d3053 3
+a3055 16
+#. I prefer "incorrect," because I think terms such as
+#. "problematic" are mealy-mouthed. They remind me of the late
+#. 1980's English textbook trend toward the politically correct yet
+#. wholly unhelpful "standard/nonstandard." But then, I tend to be
+#. dogmatic; it's probably my Catholic upbringing. [PWF]
+#: en_US/style.xml:108(para)
+msgid ""
+"So you made the changes I showed you in the last section. What's the next "
+"thing you should do? Just pop your thumb drive onto your system and read the "
+"<filename>messages</filename> log. When you see \"USB device found,\" then "
+"Bob's your uncle."
+msgstr ""
+"Portanto, já fez as alterações que lhe mostrei na última secção. Qual é a "
+"próxima coisa que deseja fazer? Basta colocar a sua caneta no seu sistema e "
+"ler o ficheiro de registo <filename>messages</filename>. Quando ver \"USB "
+"device found,\", então o João é o seu tio."
+d3057 1
+a3057 6
+#: en_US/style.xml:116(title)
+msgid "Correct style"
+msgstr "Estilo correcto"
+
+#. I prefer "correct." See above. [PWF]
+#: en_US/style.xml:120(para)
+d3059 2
+a3060 5
+"After you complete the configuration changes above, attach the USB removable "
+"media to your system. Use the <command>dmesg</command> command to examine "
+"the kernel message log. The message <computeroutput>USB device\n"
+"\t found</computeroutput> indicates that your device was installed "
+"successfully."
+d3062 2
+a3063 5
+"Depois de terminar as mudanças de configuração acima, ligue o dispositivo "
+"removível USB ao seu sistema. Use o comando <command>dmesg</command> para "
+"examinar o registo de mensagens do 'kernel'. A mensagem <computeroutput>USB "
+"device found</computeroutput> indica que o seu dispositivo foi instalado com "
+"sucesso."
+d3065 1
+a3065 1
+#: en_US/style.xml:129(para)
+d3067 4
+a3070 4
+"The first example is more conversational English, which is not appropriate "
+"for official written documentation. The second example is more formal, but "
+"as a result it is easier to comprehend, both for native readers and "
+"translators."
+d3072 9
+a3080 4
+"O primeiro exemplo é um Inglês mais coloquial, o qual não é apropriado para "
+"documentação oficial escrita. O segundo exemplo é mais formal, mas tem como "
+"resultado uma maior facilidade de compreensão, quer para os leitores nativos "
+"quer para os tradutores."
+d3082 1
+a3082 1
+#: en_US/style.xml:135(para)
+d3084 4
+a3087 8
+"Following style rules and guidelines also makes readers more comfortable "
+"with a set of documents. Consistent style enhances the professional "
+"appearance of documentation, and its perceived value. On the other hand, "
+"lapses in punctuation or poor grammar negatively affect a reader's reaction "
+"to written material. A reader can feel that an otherwise correct technical "
+"document is lacking in authority, simply because it is poorly written. "
+"Readers feel at ease when they do not have to struggle to understand an "
+"author's use of language."
+d3089 44
+a3132 9
+"Seguir as regras e instruções de estilo também deixa os leitores mais "
+"confortáveis com um determinado conjunto de documentos. Um estilo "
+"consistente melhor a aparência profissional da documentação, bem como o "
+"valor que é transmitido. Por outro lado, os lapsos de pontuação ou uma "
+"gramática incorrecta afectam de forma negativa a reacção de um leitor ao "
+"material escrito. Um leitor poderá sentir que um documento técnico não tem "
+"qualquer autoridade, simplesmente por estar mal escrito. Os leitores "
+"facilmente sentem que não têm de lidar com a compreensão da utilização da "
+"língua por parte de um autor."
+d3134 1
+a3134 1
+#: en_US/style.xml:146(para)
+d3136 9
+a3144 4
+"This chapter cannot possibly cover enough material to make every reader a "
+"good writer. Some manuals devoted entirely to writing style are themselves "
+"hundreds of pages long. This chapter provides enough guidelines for "
+"intermediate writers to understand style usage in technical documentation."
+d3146 10
+a3155 5
+"Este capítulo não poderá cobrir possivelmente material suficiente para que "
+"um leitor seja um bom escritor. Existem alguns manuais dedicados por inteiro "
+"ao estilo de escrita, tendo alguns deles centenas de páginas. Este capítulo "
+"contém instruções suficientes para os escritores médios compreenderem a "
+"utilização do estilo de documentação técnica."
+d3157 1
+a3157 1
+#: en_US/style.xml:153(para)
+d3159 4
+a3162 3
+"If you are not a practiced writer, whether of technical documentation or "
+"otherwise, you may benefit from other style resources. The following list is "
+"far from comprehensive, but provides a starting point:"
+d3164 4
+a3167 3
+"Se não for um escritor com prática, seja em documentação técnica ou noutra "
+"qualquer, poderá beneficiar de outros recursos de estilo. A lista que se "
+"segue não é excelente, mas oferece um bom ponto de partida:"
+d3169 1
+a3169 1
+#: en_US/style.xml:161(para)
+d3171 15
+a3185 4
+"<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules "
+"and links to online versions can be found at: <ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>"
+d3187 16
+a3202 4
+"<citetitle>The Elements of Style</citetitle>, de William Strunk. Poderá "
+"encontrar algumas regras básicas e referências para as versões 'online' em: "
+"<ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en."
+"wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+d3204 1
+a3204 1
+#: en_US/style.xml:176(para)
+d3206 2
+a3207 3
+"<citetitle>The Chicago Manual of Style</citetitle>, by the University of "
+"Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle."
+"org/\">http://www.chicagomanualofstyle.org/</ulink>"
+d3209 2
+a3210 3
+"<citetitle>The Chicago Manual of Style</citetitle>, da University of Chicago "
+"Press. Versão 'online': <ulink url=\"http://www.chicagomanualofstyle.org/"
+"\">http://www.chicagomanualofstyle.org/</ulink>"
+d3212 4
+a3215 9
+#: en_US/style.xml:183(para)
+msgid ""
+"<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by "
+"Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/"
+"\">http://www.powa.org/</ulink>"
+msgstr ""
+"<citetitle>Paradigm Online Writing Assistant</citetitle>, mantido por Chuck "
+"Guilford, Ph.D. Apenas 'online': <ulink url=\"http://www.powa.org/\">http://"
+"www.powa.org/</ulink>"
+d3217 6
+a3222 16
+#: en_US/style.xml:190(para)
+msgid ""
+"There are many free software documentation projects which have developed "
+"their own style guidelines. This chapter, in fact, draws heavily on the "
+"<citetitle>GNOME Documentation Style Guidelines</citetitle> "
+"(<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</"
+"citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/"
+"\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr ""
+"Existem diversos projectos de documentação de 'software' que desenvolveram "
+"as suas próprias recomendações de estilo. Este capítulo, de facto, baseia-se "
+"em grande medida nas <citetitle>Recomendações de Estilo de Documentação do "
+"GNOME</citetitle> (<firstterm>GDSG</firstterm>). Poderá ler a "
+"<citetitle>GDSG</citetitle> original em <ulink url=\"http://developer.gnome."
+"org/documents/style-guide/\">http://developer.gnome.org/documents/style-"
+"guide/</ulink>."
+d3224 3
+a3226 3
+#: en_US/style.xml:203(title)
+msgid "Fundamental Concepts of Technical Documentation"
+msgstr "Conceitos Fundamentais da Documentação Técnica"
+d3228 3
+a3230 3
+#: en_US/style.xml:206(title)
+msgid "Bibliographic Information"
+msgstr "Informação Bibliográfica"
+d3232 3
+a3234 3
+#: en_US/style.xml:207(para)
+msgid "This section is drawn primarily from the <citetitle>GDSG</citetitle>."
+msgstr "Esta secção baseia-se principalmente na <citetitle>GDSG</citetitle>."
+d3236 3
+a3238 11
+#. This section will reproduce mostly what is in Chapter 1 of
+#. the GDSG. There may be minor changes. FIXME: Make sure the
+#. appropriate front matter of the Documentation Guide includes
+#. attribution as required by the GNU FDL.
+#: en_US/style.xml:218(para)
+msgid ""
+"This chapter provides a brief introduction to writing technical "
+"documentation."
+msgstr ""
+"Este capítulo oferece uma breve introdução à escritaq de documentação "
+"técnica."
+d3240 3
+a3242 3
+#: en_US/style.xml:224(title)
+msgid "General Style Requirements"
+msgstr "Requisitos Gerais de Estilo"
+d3244 3
+a3246 9
+#: en_US/style.xml:225(para)
+msgid ""
+"Technical writing for the Fedora Project imposes special constraints beyond "
+"the basic requirements of good prose. Good Fedora technical documentation "
+"has the following characteristics:"
+msgstr ""
+"A escrita técnica para o Projecto Fedora impõe restrições especiais para "
+"além dos requisitos básicos da boa prosa. Uma boa documentação técnica do "
+"Fedora tem as seguintes características:"
+d3248 4
+a3251 3
+#: en_US/style.xml:232(term)
+msgid "Comprehensive"
+msgstr "Compreensível"
+d3253 3
+a3255 7
+#: en_US/style.xml:234(para)
+msgid ""
+"Describe all of the functionality of a product. Do not omit functionality "
+"that you regard as irrelevant for the user."
+msgstr ""
+"Descreve todas as funcionalidades de um produto. Não omita funcionalidades "
+"que considere irrelevantes para o utilizador, do seu ponto de vista."
+d3257 3
+a3259 3
+#: en_US/style.xml:242(term)
+msgid "Conforming"
+msgstr "Em Conformidade"
+d3261 3
+a3263 7
+#: en_US/style.xml:249(para)
+msgid ""
+"Describe what you see. Do not describe what you want to see. Present your "
+"information in the order that users experience the subject matter."
+msgstr ""
+"Descreva o que vê. Não descreva o que deseja ver. Apresente a sua informação "
+"pela ordem em que os utilizadores deparam com o assunto."
+d3265 1
+a3265 5
+#: en_US/style.xml:257(term)
+msgid "Clear"
+msgstr "Clara"
+
+#: en_US/style.xml:259(para)
+d3267 7
+a3273 3
+"Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>) to help make your writing clear."
+d3275 7
+a3281 3
+"Leia <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>) que o ajuda a tornar a sua escrita mais clara."
+d3283 1
+a3283 5
+#: en_US/style.xml:275(term)
+msgid "Consistent"
+msgstr "Consistente"
+
+#: en_US/style.xml:277(para)
+d3285 7
+a3291 2
+"Use agreed vocabulary throughout your documentation. Use the same vocabulary "
+"as other writers who are working on related documentation."
+d3293 8
+a3300 3
+"Use um vocabulário adequado ao longo da sua documentação. Use o mesmo "
+"vocabulário dos outros escritores que estão a trabalhar sobre documentos "
+"relacionados com este."
+d3302 1
+a3302 5
+#: en_US/style.xml:285(term)
+msgid "Concise"
+msgstr "Concisa"
+
+#: en_US/style.xml:287(para)
+d3304 2
+a3305 3
+"Review your work frequently as you write your document. Ask yourself which "
+"words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for "
+"specific guidelines."
+d3307 2
+a3308 3
+"Reveja o seu trabalho com frequência, à medida que escreve o seu documento. "
+"Pergunte a si mesmo as palavras que poderá retirar. Veja algumas "
+"recomendações específicas em <xref linkend=\"sn-fundamentals-2\"/>."
+d3310 3
+a3312 3
+#: en_US/style.xml:297(title)
+msgid "Golden Rules"
+msgstr "Regras de Ouro"
+d3314 1
+a3314 1
+#: en_US/style.xml:298(para)
+d3316 4
+a3319 2
+"This section contains some basic style guidelines. Subsequent sections in "
+"this chapter expand on these guidelines to give more detailed guidance."
+d3321 5
+a3325 3
+"Esta secção contém algumas recomendações básicas de estilo. As secções "
+"seguintes deste capítulo expandem essas recomendações, para lhe dar "
+"conselhos mais detalhados."
+d3327 1
+a3327 17
+#: en_US/style.xml:305(term)
+msgid "Golden Rule 1: Be brief"
+msgstr "Regra de Ouro 1: Seja breve"
+
+#: en_US/style.xml:309(para)
+msgid "Limit each sentence to fewer than 25 words."
+msgstr "Limite cada frase a menos de 25 palavras."
+
+#: en_US/style.xml:314(para)
+msgid "Limit each procedure step to 23 words."
+msgstr "Limite cada passo de procedimento a 23 palavras."
+
+#: en_US/style.xml:320(title)
+msgid "Incorrect: Too long"
+msgstr "Incorrecto: Demasiado comprido"
+
+#: en_US/style.xml:321(para)
+d3329 4
+a3332 3
+"Under normal operating conditions, the kernel does not always immediately "
+"write file data to the disks, storing it in a memory buffer and then "
+"periodically writing to the disks to speed up operations."
+d3334 4
+a3337 3
+"Em condições normais de operação, o 'kernel' não grava sempre imediatamente "
+"os dados do ficheiros nos discos, guardando-os numa área em memória e "
+"escrevendo periodicamente para os discos, de modo a acelerar as operações."
+d3339 1
+a3339 5
+#: en_US/style.xml:328(title)
+msgid "Correct: Less wordy"
+msgstr "Correcto: Com menos palavreado"
+
+#: en_US/style.xml:329(para)
+d3341 7
+a3347 2
+"Normally, the kernel stores the data in memory prior to periodically writing "
+"the data to the disk."
+d3349 8
+a3356 2
+"Normalmente, o 'kernel' guarda os dados em memória antes de os gravar "
+"periodicamente no disco."
+d3358 1
+a3358 21
+#: en_US/style.xml:337(term)
+msgid "Golden Rule 2: Be organized"
+msgstr "Regra de Ouro 2: Ser organizado"
+
+#: en_US/style.xml:341(para)
+msgid "Limit each paragraph to one topic."
+msgstr "Limite cada parágrafo a um tópico."
+
+#: en_US/style.xml:346(para)
+msgid "Limit each sentence to one idea."
+msgstr "Limite cada frase a uma ideia."
+
+#: en_US/style.xml:351(para)
+msgid "Limit each procedure step to one action."
+msgstr "Limite cada passo de procedimento a uma acção."
+
+#: en_US/style.xml:357(title)
+msgid "Incorrect: Disorganized topics"
+msgstr "Incorrecto: Tópicos desorganizados"
+
+#: en_US/style.xml:358(para)
+d3360 8
+a3367 9
+"The <application>Workspace Switcher</application> applet helps you navigate "
+"all of the virtual desktops available on your system. The X Window system, "
+"working in hand with a piece of software called a <emphasis>window manager</"
+"emphasis>, allows you to create more than one virtual desktop, known as "
+"<emphasis>workspaces</emphasis>, to organize your work, with different "
+"applications running in each workspace. The <application>Workspace Switcher</"
+"application> applet is a navigational tool to get around the various "
+"workspaces, providing a miniature road map in the GNOME panel showing all "
+"your workspaces and allowing you to switch easily between them."
+d3369 8
+a3376 11
+"A 'applet' do <application>Selector do Espaço de Trabalho</application> "
+"ajuda-o a navegar em todos os ecrãs virtuais do seu sistema. O sistema X "
+"Window, funcionando em conjunto com uma pequena componente aplicacional, "
+"chamada de <emphasis>gestor de janelas</emphasis>, permite-lhe criar mais de "
+"um ecrã virtual, também conhecido por <emphasis>espaço de trabalho</"
+"emphasis>, para organizar o seu trabalho, com diferentes aplicações a correr "
+"em cada espaço de trabalho. A 'applet' do <application>Selector do Espaço de "
+"Trabalho</application> é uma ferramenta de navegação para percorrer os "
+"diversos espaços de trabalho, oferecendo um roteiro em miniatura no painel "
+"do GNOME, mostrando todos os seus espaços de trabalho e permitindo uma "
+"mudança simples entre eles."
+d3378 1
+a3378 5
+#: en_US/style.xml:375(title)
+msgid "Correct: Organized topics"
+msgstr "Correcto: Tópicos organizados"
+
+#: en_US/style.xml:376(para)
+d3380 6
+a3385 6
+"Use the <application>Workspace Switcher</application> to add new "
+"<emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different "
+"applications in each workspace. The <application>Workspace Switcher</"
+"application> applet provides a miniature map that shows all of your "
+"workspaces. You can use the <application>Workspace Switcher</application> "
+"applet to switch between workspaces."
+d3387 7
+a3393 7
+"Use o <application>Selector de Espaços de Trabalho</application> para "
+"adicionar novos <emphasis>espaços de trabalho</emphasis> ao ambiente gráfico "
+"GNOME. Poderá executar diferentes aplicações em cada um dos espaços de "
+"trabalho. A 'applet' do <application>Selector de Espaços de Trabalho</"
+"application> oferece um mapa em miniatura que mostra todos os seus espaços "
+"de trabalho. Poderá usar a 'applet' do <application>Selector de Espaços de "
+"Trabalho</application>, de modo a mudar de espaços de trabalho."
+d3395 1
+a3395 1
+#: en_US/style.xml:388(para)
+d3397 3
+a3399 2
+"Plan the order of paragraphs before you start writing. Decide which topic "
+"you want to cover in each paragraph."
+d3401 3
+a3403 2
+"Planeie a ordem dos parágrafos antes de começar a escrever. Decida o tópico "
+"que deseja cobrir em cada parágrafo."
+d3405 3
+a3407 3
+#: en_US/style.xml:396(term)
+msgid "Golden Rule 3: Be demonstrative"
+msgstr "Regra de Ouro 3: Seja demonstrativo"
+d3409 1
+a3409 1
+#: en_US/style.xml:398(para)
+d3411 2
+a3412 2
+"Use explicit examples to demonstrate how an application works. Provide "
+"instructions rather than descriptions."
+d3414 2
+a3415 2
+"Use exemplos explícitos que demonstram como funciona uma aplicação. Forneça "
+"instruções em vez de descrições."
+d3417 9
+a3425 3
+#: en_US/style.xml:403(title)
+msgid "Incorrect: Describes but does not demonstrate"
+msgstr "Incorrecto: Descreve mas não demonstra"
+d3427 1
+a3427 1
+#: en_US/style.xml:405(para)
+d3429 3
+a3431 1
+"There is a text box that you can use to find out the definition of a word."
+d3433 3
+a3435 2
+"Existe um campo de texto que poderá usar para descobrir a definição de uma "
+"palavra."
+d3437 3
+a3439 3
+#: en_US/style.xml:411(title)
+msgid "Correct: Demonstrates usage"
+msgstr "Correcto: Demonstra a utilização"
+d3441 1
+a3441 1
+#: en_US/style.xml:412(para)
+d3443 4
+a3446 2
+"To request a definition of a word, type the word in the text box, then "
+"select <guilabel>Lookup</guilabel>."
+d3448 4
+a3451 2
+"Para pedir a definição de uma palavra, escreva a palavra no campo de texto, "
+"seleccionando depois a opção <guilabel>Procurar</guilabel>."
+d3453 1
+a3453 1
+#: en_US/style.xml:418(para)
+d3455 2
+a3456 2
+"Do not apply this guideline too rigidly. Sometimes you must explain how "
+"software works to support your how-to examples."
+d3458 2
+a3459 2
+"Não aplique esta recomendação de forma muito rígida. Algumas vezes tem de "
+"explicar como funciona o 'software' para suportar os seus exemplos."
+d3461 3
+a3463 3
+#: en_US/style.xml:427(term)
+msgid "Golden Rule 4: Be objective"
+msgstr "Regra de Ouro 4: Ser objectivo"
+d3465 5
+a3469 3
+#: en_US/style.xml:429(para)
+msgid "Write in a neutral tone."
+msgstr "Escreva num tom neutro."
+d3471 4
+a3474 3
+#: en_US/style.xml:433(title)
+msgid "Incorrect: Sentence takes sides"
+msgstr "Incorrecto: A frase tem um conteúdo de opinião parcial"
+d3476 3
+a3478 3
+#: en_US/style.xml:434(para)
+msgid "The applet is a handy little screen grabber."
+msgstr "A 'applet' é um pequeno e útil módulo de captura do ecrã."
+d3480 2
+a3481 13
+#: en_US/style.xml:439(title)
+msgid "Correct: Sentence is objective"
+msgstr "Correcto: A frase é objectiva"
+
+#: en_US/style.xml:440(para)
+msgid "Use the applet to take screenshots."
+msgstr "Use a 'applet' para fazer capturas do ecrã."
+
+#: en_US/style.xml:452(title)
+msgid "Tone"
+msgstr "Tom"
+
+#: en_US/style.xml:453(para)
+d3483 4
+a3486 7
+"Inappropriate tone hinders reader access to information. A neutral tone free "
+"of opinion or personal flavor improves the reader's comprehension. Neutral "
+"tone helps writers to work in parallel on a large technical documentation "
+"project. Furthermore, additional writers may join the project at any time. "
+"Use of a neutral tone helps to achieve consistency across a documentation "
+"set, and thereby facilitates user access to information. The best way to "
+"achieve a common, neutral tone is to apply the following principles:"
+d3488 4
+a3491 9
+"Um tom inapropriado retrai o acesso do utilizador à informação. Um tom "
+"neutro e livre de opiniões ou escolhas pessoais aumenta a compreensão por "
+"parte do leitor. Um tom netruo ajuda os escritores a trabalharem em paralelo "
+"num projecto de documentação técnica grande. Para além disso, poder-se-ão "
+"juntar escritores adicionais ao projecto em qualquer altura. A utilização de "
+"um tom netruo ajuda a obter alguma consistência em torno de um conjunto de "
+"documentos, facilitando deste modo o acesso dos utilizadores à informação. A "
+"melhor forma de obter um tom neutro e comum é aplicar os seguintes "
+"princípios:"
+d3493 3
+a3495 3
+#: en_US/style.xml:466(term)
+msgid "Avoid humor"
+msgstr "Evite o humor"
+d3497 1
+a3497 1
+#: en_US/style.xml:468(para)
+d3499 5
+a3503 2
+"Humor distracts from the information you are trying to provide. Humor also "
+"makes documentation difficult to translate. Stay factual."
+d3505 6
+a3510 3
+"O humor distrai o leitor da informação que você está a tentar transmitir. O "
+"humor também torna a documentação mais difícil de traduzir. Resuma-se a "
+"factos."
+d3512 3
+a3514 3
+#: en_US/style.xml:476(term)
+msgid "Avoid personal opinions"
+msgstr "Evite opiniões pessoais"
+d3516 1
+a3516 1
+#: en_US/style.xml:478(para)
+d3518 3
+a3520 3
+"Whether you think a function is useful or woeful is irrelevant. Report the "
+"function to the user, with instructions about how to use the function. Stay "
+"accurate."
+d3522 3
+a3524 3
+"Se acha que uma dada função é útil ou inútil é irrelevante. Relate a função "
+"para o utilizador, com instruções de utilização da mesma. Mantenha-se "
+"correcto."
+d3526 3
+a3528 3
+#: en_US/style.xml:487(term)
+msgid "Avoid colloquial language"
+msgstr "Evite a linguagem coloquial"
+d3530 3
+a3532 7
+#: en_US/style.xml:489(para)
+msgid ""
+"Colloquial language is difficult to translate and usually culture-specific. "
+"Stay neutral."
+msgstr ""
+"A linguagem coloquial é difícil de traduzir e normalmente é específica da "
+"caltura. Mantenha-se neutro."
+d3534 3
+a3536 3
+#: en_US/style.xml:496(term)
+msgid "Avoid topical expressions"
+msgstr "Evite expressões por tópicos"
+d3538 3
+a3540 7
+#: en_US/style.xml:498(para)
+msgid ""
+"An expression that is in common use today might convey something completely "
+"different tomorrow. Stay technical."
+msgstr ""
+"Uma expressão que seja de uso comum nos dias de hoje poderá representar algo "
+"completamente diferente amanhã. Mantenha-se técnico."
+d3542 3
+a3544 3
+#: en_US/style.xml:505(term)
+msgid "Avoid aspirational statements"
+msgstr "Evite frases baseadas em suposições futuras"
+d3546 3
+a3548 8
+#: en_US/style.xml:507(para)
+msgid ""
+"Statements about the future developments of a product do not belong in "
+"technical documentation. Write about what you see right now. Stay real."
+msgstr ""
+"As referências aos futuros desenvolvimentos de um produto não pertencem à "
+"documentação técnica. Escreva apenas sobre o que existe agora. Mantenha-se "
+"realista."
+d3550 4
+a3553 3
+#: en_US/style.xml:517(title)
+msgid "Reaching the Right Audience"
+msgstr "Atinja a Audiência Correcta"
+d3555 4
+a3558 16
+#: en_US/style.xml:518(para)
+msgid ""
+"All of the decisions that you make about the structure and content of a "
+"manual follow from an understanding of the audience. Consider how the "
+"audience accesses the documentation, what sort of information the audience "
+"needs, and the experience level of the audience. Usually, you need to create "
+"documentation that is suitable for different audiences. The following "
+"sections introduce some of the audience-related topics you need to consider."
+msgstr ""
+"Todas as decisões que fizer acerca da estrutura e conteúdo de um manual "
+"partem de uma compreensão por parte da audiência. Pense na forma como a "
+"audiência acede à documentação, ao tipo de informação que a audiência "
+"necessita e ao nível de experiência da audiência. Normalmente, é necessário "
+"criar uma documentação que seja adequada para diferentes audiências. As "
+"seguintes secções introduzem alguns dos tópicos relacionados com a audiência "
+"que necessita de ter em consideração."
+d3560 3
+a3562 3
+#: en_US/style.xml:530(title)
+msgid "User Motivation"
+msgstr "Motivação do Utilizador"
+d3564 1
+a3564 1
+#: en_US/style.xml:531(para)
+d3566 4
+a3569 4
+"Do not waste the time of the user who looks for information in your "
+"documentation. Users do not read technical documentation for entertainment. "
+"Users usually have specific questions. You need to give clear answers to "
+"those questions."
+d3571 4
+a3574 4
+"Não ocupe o tempo do utilizador que procura informações na sua documentação. "
+"Os utilizadores não lêem documentação técnica por entretenimento. Os "
+"utilizadores normalmente têm questões específicas. Terá de dar respostas "
+"claras a essas questões."
+d3576 2
+a3577 5
+#: en_US/style.xml:539(title)
+msgid "New Users"
+msgstr "Novos Utilizadores"
+
+#: en_US/style.xml:540(para)
+d3579 5
+a3583 8
+"New users to Fedora are likely to consult online tutorials for guidance "
+"about unfamiliar applications or functionality. Each tutorial should contain "
+"enough introductory information to tell new users how to start using the "
+"relevant functions. Each tutorial should also contain enough usage "
+"instructions to tell users the different actions that they can perform with "
+"the command or function. Keep these instructions task-oriented. Do not "
+"describe GUI screens, dialogs, and dialog elements in a tutorial, unless "
+"there is an unusual feature that affects your instructions."
+d3585 6
+a3590 9
+"Os utilizadores novos no Fedora provavelmente irão consultar os tutoriais "
+"'onyline' para se orientarem nas aplicações ou funcionalidades pouco "
+"familiares. Cada tutorial deverá conter informação introdutória sufciente "
+"para indicar aos novos utilizadores como começar a usar as funções "
+"relevantes. Cada tutorial deverá também conter instruções de utilização "
+"suficientes para informar os utilizadores das diferentes acções que podem "
+"efectuar com o comando ou a função. Mantenha estas instruções orientadas às "
+"tarefas. Não descreva as janelas gráficas e os seus elementos num tutoria, a "
+"menos que exista alguma funcionalidade anormal que afecte as suas instruções."
+d3592 3
+a3594 3
+#: en_US/style.xml:554(title)
+msgid "Experienced Users"
+msgstr "Utilizadores Experientes"
+d3596 3
+a3598 9
+#: en_US/style.xml:555(para)
+msgid ""
+"Experienced users are more likely to use documentation as a reference. The "
+"documentation therefore needs to be complete, well-organized, and in the "
+"case of printed manuals, well-indexed."
+msgstr ""
+"Os utilizadores experientes são mais aptos para usar a documentação como "
+"referência. A documentação aí tem de ser completa, bem organizada e, no caso "
+"dos manuais impressos, bem indexada."
+d3600 3
+a3602 3
+#: en_US/style.xml:563(title)
+msgid "Do Not Offend Your Audience"
+msgstr "Não Ofenda a sua Audiência"
+d3604 1
+a3604 1
+#: en_US/style.xml:564(para)
+d3606 4
+a3609 2
+"To avoid offending your readers, apply the following guidelines to your "
+"documentation:"
+d3611 4
+a3614 2
+"Para evitar ofender os seus leitores, aplique as seguintes recomendações à "
+"sua documentação:"
+d3616 3
+a3618 3
+#: en_US/style.xml:570(term)
+msgid "Avoid insider language"
+msgstr "Evite a linguagem própria"
+d3620 3
+a3622 12
+#: en_US/style.xml:572(para)
+msgid ""
+"Insider language includes both undefined jargon and the tendency of the "
+"computer community to shorten words. For example, use the term "
+"<literal>documentation</literal> instead of the term <literal>docs</"
+"literal>. A term may be jargon if it fails all the following conditions:"
+msgstr ""
+"A linguagem própria ou interna inclui algum calão indefinido e a tendência "
+"da comunidade informática de reduzir as palavras. Por exemplo, use o termo "
+"<literal>documentação</literal> em vez do termo <literal>docs</literal>. Um "
+"termo poderá ser considerado 'calão', se não respeitar qualquer uma das "
+"seguintes condições:"
+d3624 3
+a3626 9
+#: en_US/style.xml:581(para)
+msgid ""
+"The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> "
+"(<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora."
+"redhat.com/docs/jargon-buster/</ulink>)."
+msgstr ""
+"O termo não aparece no <citetitle>Jargon Buster do Fedora</citetitle> "
+"(<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora."
+"redhat.com/docs/jargon-buster/</ulink>)."
+d3628 1
+a3628 1
+#: en_US/style.xml:588(para)
+d3630 5
+a3634 3
+"The term does not appear in the <citetitle>American Heritage Dictionary</"
+"citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby."
+"com/61/ </ulink>)."
+d3636 6
+a3641 3
+"O termo não aparece no <citetitle>American Heritage Dictionary</citetitle> "
+"(<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/ </"
+"ulink>)."
+d3643 3
+a3645 4
+#: en_US/style.xml:596(para)
+msgid ""
+"The term does not appear in the glossary of the manual that you are writing."
+msgstr "O termo não aparece no glossário do manual que está a escrever."
+d3647 1
+a3647 1
+#: en_US/style.xml:602(para)
+d3649 2
+a3650 1
+"The term is not defined in the body text of the manual that you are writing."
+d3652 2
+a3653 1
+"O termo não está definido no texto do conteúdo do manual que está a escrever."
+d3655 3
+a3657 3
+#: en_US/style.xml:611(term)
+msgid "Avoid gender-specific language"
+msgstr "Evite a linguagem dependente do sexo"
+d3659 2
+a3660 5
+#: en_US/style.xml:613(para)
+msgid ""
+"Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</"
+"literal> do not exist. There is no need to identify gender in your "
+"instructions."
+d3662 1
+a3662 3
+"As construções de pronomes como o <literal>dele/dela</literal> ou "
+"<literal>ele/a</literal> não existem. Não existe a necessidade de reflectir "
+"o sexo da audiência na suas instruções."
+d3664 3
+a3666 3
+#: en_US/style.xml:621(term)
+msgid "Avoid culture-specific language"
+msgstr "Evite a linguagem específica da cultura"
+d3668 1
+a3668 1
+#: en_US/style.xml:623(para)
+d3670 4
+a3673 2
+"There is little point in giving an example that everyone in your town knows "
+"about, but is a complete mystery to everyone else in the world."
+d3675 5
+a3679 2
+"Não vale a pena dar um exemplo que seja conhecido em toda a sua cidade, mas "
+"que seja um completo mistério para o resto do mundo."
+d3681 3
+a3683 14
+#: en_US/style.xml:631(term)
+msgid "Avoid talking down to your reader"
+msgstr "Evite rebaixar o seu leitor"
+
+#: en_US/style.xml:633(para)
+msgid ""
+"There are few experiences more irritating for a user than documentation that "
+"says an action is easy or quick, when in fact the user cannot complete the "
+"action. Do not qualify or prejudge actions."
+msgstr ""
+"Existem poucas experiências mais irritantes para um utilizador que a "
+"documentação que diz que uma determinada acção é fácil ou rápida, quando o "
+"utilizador não consegue desempenhá-la de facto. Não qualifique ou faça "
+"juízos de valor das acções."
+d3685 1
+a3685 1
+#: en_US/style.xml:642(para)
+d3687 5
+a3691 2
+"Other parts of this guide discuss in more detail tone and language usage "
+"that can cause offense."
+d3693 5
+a3697 2
+"Outras partes deste guia descrevem com mais detalhe o tom e linguagem que "
+"possam ser considerados ofensivos."
+d3699 15
+a3713 3
+#: en_US/style.xml:653(title)
+msgid "Grammar and Usage Guidelines"
+msgstr "Recomendações de Gramática e Utilização"
+d3715 3
+a3717 3
+#: en_US/style.xml:656(title)
+msgid "Bibliographical Information"
+msgstr "Informação Bibliográfica"
+d3719 1
+a3719 1
+#: en_US/style.xml:657(para)
+d3721 3
+a3723 3
+"This section is drawn partly from the <citetitle>GDSG</citetitle>, and "
+"partly from <citetitle>The Elements of Style</citetitle>, updated as "
+"necessary for the needs of 21st-century technical documentation writers."
+d3725 3
+a3727 4
+"Esta secção é retirada em parte da <citetitle>GDSG</citetitle> e também em "
+"parte do documento <citetitle>The Elements of Style</citetitle>, actualizado "
+"de acordo com as necessidades dos escritores de documentação técnica do "
+"século XXI."
+d3729 1
+a3729 3
+#. FIXME: Again, check attribution viz. GNU FDL. This will be more work
+#. than the previous section.
+#: en_US/style.xml:668(para)
+d3731 2
+a3732 8
+"This section contains an alphabetical list of grammar and usage guidelines "
+"for use in Fedora documentation. Many of these guidelines are only "
+"applicable to English-language usage, refer to the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of "
+"Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/"
+"cmosfaq.html</ulink>.)"
+d3734 3
+a3736 8
+"Esta secção contém uma lista alfabética das recomendações de gramática e "
+"utilização na documentação do Fedora. Muitas destas recomendações só se "
+"aplicam na utilização da língua Inglesa; para mais informações, consulte o "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) e o "
+"<citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www."
+"press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press."
+"uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+d3738 3
+a3740 3
+#: en_US/style.xml:679(term)
+msgid "Abbreviations"
+msgstr "Abreviaturas"
+d3742 1
+a3742 1
+#: en_US/style.xml:681(para)
+d3744 3
+a3746 4
+"A shortened form of a word or phrase that takes the place of the full word "
+"or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, "
+"<literal>p.m.</literal>, and so on. Apply the following rules when you use "
+"abbreviations:"
+d3748 7
+a3754 4
+"Uma forma resumida de uma palavra ou frase que toma o lugar da palavra ou "
+"frase completa, como por exemplo <literal>Dr.</literal>, <literal>a.m.</"
+"literal>, <literal>p.m.</literal>, e assim por diante. Aplique as seguintes "
+"regras quando usar abreviaturas:"
+d3756 3
+a3758 7
+#: en_US/style.xml:689(para)
+msgid ""
+"Avoid creating new abbreviations. Unfamiliar abbreviations can confuse "
+"rather than clarify a concept."
+msgstr ""
+"Evite a criação de novas abreviaturas. As abreviaturas pouco familiares "
+"poderão confundir mais um conceito que clarificar."
+d3760 3
+a3762 3
+#: en_US/style.xml:695(para)
+msgid "Do not explain or expand familiar abbreviations."
+msgstr "Não explique ou expanda as abreviaturas conhecidas."
+d3764 3
+a3766 3
+#: en_US/style.xml:700(para)
+msgid "Do not include familiar abbreviations in the glossary of your manual."
+msgstr "Não inclua as abreviaturas conhecidas no glossário do seu manual."
+d3768 1
+a3768 1
+#: en_US/style.xml:706(para)
+d3770 2
+a3771 3
+"For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other "
+"words\" and <literal>e.g.</literal> for \"for example\", do not use the "
+"abbreviation. Spell out the entire phrase."
+d3773 2
+a3774 3
+"Para as abreviaturas das frases, como o <literal>i.e.</literal> para \"isto é"
+"\" e o <literal>p.ex.</literal> como \"por exemplo\", não use a abreviatura. "
+"Descreva a frase por inteiro."
+d3776 3
+a3778 3
+#: en_US/style.xml:715(term)
+msgid "Adjectives"
+msgstr "Adjectivos"
+d3780 1
+a3780 1
+#: en_US/style.xml:717(para)
+d3782 2
+a3783 3
+"Use adjectives with caution. If an adjective is necessary to differentiate "
+"between items, then use adjectives. In all cases, test whether the phrase "
+"can stand alone without the adjective."
+d3785 2
+a3786 3
+"Use os adjectivos com cuidado. Se um adjectivo for necessário para "
+"diferenciar itens, então use os adjectivos. Em qualquer um dos casos, este "
+"se a frase poderá ficar bem sem o adjectivo."
+d3788 3
+a3790 3
+#: en_US/style.xml:726(term)
+msgid "Acronyms"
+msgstr "Acrónimos"
+d3792 1
+a3792 1
+#: en_US/style.xml:728(para)
+d3794 4
+a3797 2
+"A term that represents a multi-word term. Typically, acronyms are formed in "
+"the following ways:"
+d3799 7
+a3805 2
+"Um termo que representa um conjunto de palavras. Tipicamente, os acrónimos "
+"são formados da seguinte forma:"
+d3807 1
+a3807 1
+#: en_US/style.xml:734(para)
+d3809 4
+a3812 2
+"From the first letters of each word in a compound term, for example Table of "
+"Contents (TOC)."
+d3814 5
+a3818 2
+"Das primeiras letras de cada palavra num termo composto. Por exemplo, TOC "
+"significa 'Table of Contents' (Índice Analítico)."
+d3820 3
+a3822 7
+#: en_US/style.xml:740(para)
+msgid ""
+"From recognizable parts of a compound term, such as GNU Object Model "
+"Environment (GNOME)."
+msgstr ""
+"A partir de partes reconhecíveis de um termo composto, como o GNU Object "
+"Model Environment (GNOME)."
+d3824 3
+a3826 3
+#: en_US/style.xml:746(para)
+msgid "Apply the following rules when you use acronyms:"
+msgstr "Aplique as seguintes regras quando usar acrónimos:"
+d3828 3
+a3830 7
+#: en_US/style.xml:751(para)
+msgid ""
+"On the first occurrence of an acronym, spell out the full term, with the "
+"acronym in parentheses."
+msgstr ""
+"Na primeira ocorrência de um acrónimo, descreva por completo o termo "
+"completo, tendo o acrónimo entre parêntesis."
+d3832 1
+a3832 1
+#: en_US/style.xml:757(para)
+d3834 6
+a3839 2
+"Do not spell out the full compound for well-known acronyms, unless you think "
+"the information is useful for readers."
+d3841 7
+a3847 2
+"Não descreva extensivamente o termo completo para os acrónimos conhecidos, a "
+"menos que saiba que a informação é útil para os leitores."
+d3849 3
+a3851 7
+#: en_US/style.xml:764(para)
+msgid ""
+"Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than "
+"clarify a concept."
+msgstr ""
+"Evite a criação de novos acrónimos. Os acrónimos não conhecidos poderão "
+"confundir mais um conceito que clarificá-lo."
+d3853 1
+a3853 1
+#: en_US/style.xml:770(para)
+d3855 2
+a3856 2
+"Write the acronym in uppercase letters, unless there is a compelling case "
+"for lowercase."
+d3858 3
+a3860 10
+"Escreva o acrónimo em maiúsculas, a não ser que haja um caso explícito para "
+"o uso de minúsculas."
+
+#: en_US/style.xml:776(para)
+msgid "Include the acronym and the full term in the glossary of your manual."
+msgstr "Inclua o acrónimo e o termo completo no glossário do seu manual."
+
+#: en_US/style.xml:785(term)
+msgid "Adverbs"
+msgstr "Advérbios"
+d3862 1
+a3862 1
+#: en_US/style.xml:787(para)
+d3864 5
+a3868 5
+"Use adverbs with caution. If an adverb is necessary to qualify the function "
+"of a component, then use an adverb. In all cases, test whether the phrase "
+"can stand alone without the adverb. Classic superfluous adverbs "
+"<literal>simply</literal>, <literal>easily</literal>, <literal>quickly</"
+"literal>."
+d3870 5
+a3874 5
+"Use os advérbios com cuidado. Se for necessário um advérbio para qualificar "
+"a função de um componente, então use um advérbio. Em qualquer dos casos, "
+"teste se a frase pode ser usada sem o advérbio. Alguns exemplos de advérbios "
+"supérfluos são o <literal>simplesmente</literal>, <literal>facilmente</"
+"literal>, <literal>rapidamente</literal>."
+d3876 3
+a3878 3
+#: en_US/style.xml:798(term)
+msgid "Anthropomorphism"
+msgstr "Antropomorfismo"
+d3880 1
+a3880 5
+#: en_US/style.xml:802(para)
+msgid "Do not apply emotions, desires, or opinions to software applications."
+msgstr "Não aplique emoções, desejos ou opiniões nas aplicações informáticas."
+
+#: en_US/style.xml:808(para)
+d3882 5
+a3886 2
+"Do not apply a sense of location or dimension to a software application. A "
+"user can not be \"in\" a text editor."
+d3888 6
+a3893 2
+"Não aplique um sentido de localização ou dimensão a uma aplicação "
+"informática. Um utilizador não pode estar \"dentro\" de um editor de texto."
+d3895 3
+a3897 3
+#: en_US/style.xml:818(term)
+msgid "Articles"
+msgstr "Artigos"
+d3899 1
+a3899 1
+#: en_US/style.xml:820(para)
+d3901 2
+a3902 2
+"Do not use the definite article <literal>the</literal> to begin any of the "
+"following items:"
+d3904 2
+a3905 2
+"Não use o artigo definido <literal>the</literal> (o/a) para iniciar um dos "
+"seguintes itens (nota específica do Inglês):"
+d3907 3
+a3909 3
+#: en_US/style.xml:826(para)
+msgid "Manual titles"
+msgstr "Títulos de manuais"
+d3911 3
+a3913 3
+#: en_US/style.xml:831(para)
+msgid "Chapter titles"
+msgstr "Títulos de capítulos"
+d3915 3
+a3917 3
+#: en_US/style.xml:836(para) en_US/style.xml:1239(term)
+msgid "Headings"
+msgstr "Destaques"
+d3919 4
+a3922 3
+#: en_US/style.xml:841(para)
+msgid "Figure captions"
+msgstr "Títulos de figuras"
+d3924 4
+a3927 3
+#: en_US/style.xml:846(para)
+msgid "Table captions"
+msgstr "Títulos de tabelas"
+d3929 4
+a3932 3
+#: en_US/style.xml:851(para)
+msgid "Callouts"
+msgstr "Chamadas de atenção"
+d3934 3
+a3936 3
+#: en_US/style.xml:859(term)
+msgid "Apostrophe"
+msgstr "Apóstrofo"
+d3938 1
+a3938 21
+#: en_US/style.xml:861(para)
+msgid "Do not use apostrophes except where absolutely required"
+msgstr "Não use apóstrofos, excepto se for absolutamente necessário"
+
+#: en_US/style.xml:866(para)
+msgid "Do not use apostrophes to denote possession."
+msgstr "Não use apóstrofos para denotar a pertença (específico do Inglês)."
+
+#: en_US/style.xml:871(para)
+msgid "Do not use apostrophes to denote contractions."
+msgstr "Não use os apóstrofos para demarcar as contracções."
+
+#: en_US/style.xml:876(para)
+msgid "Do not use apostrophes to denote plurals."
+msgstr "Não use os apóstrofos para denotar formas plurais."
+
+#: en_US/style.xml:882(title)
+msgid "Incorrect: Apostrophes"
+msgstr "Incorrecto: Apóstrofos"
+
+#: en_US/style.xml:885(para)
+d3940 4
+a3943 1
+"the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+d3945 4
+a3948 2
+"<guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> (opção Ajuda "
+"do Menu Principal)"
+d3950 3
+a3952 3
+#: en_US/style.xml:891(para)
+msgid "don't use the default option"
+msgstr "'don't use the default option': não usar a opção predefinida"
+d3954 3
+a3956 3
+#: en_US/style.xml:896(para)
+msgid "several SCSI disk's"
+msgstr "SCSI disk's (discos SCSI)"
+d3958 1
+a3958 5
+#: en_US/style.xml:903(title)
+msgid "Correct: No apostrophes"
+msgstr "Correcto: Sem apóstrofos"
+
+#: en_US/style.xml:906(para)
+d3960 3
+a3962 2
+"the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</"
+"guimenu>"
+d3964 3
+a3966 2
+"the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</"
+"guimenu> (a opção Ajuda no Menu Principal)"
+d3968 3
+a3970 3
+#: en_US/style.xml:912(para)
+msgid "do not use the default option"
+msgstr "do not use the default option"
+d3972 4
+a3975 3
+#: en_US/style.xml:917(para)
+msgid "several SCSI disks"
+msgstr "SCSI disks"
+d3977 1
+a3977 5
+#: en_US/style.xml:926(term)
+msgid "Brackets"
+msgstr "Parêntesis Rectos"
+
+#: en_US/style.xml:930(para)
+d3979 3
+a3981 2
+"Do not use brackets [such as these] as a substitute for parentheses (such as "
+"these)."
+d3983 7
+a3989 2
+"Não use parêntesis [deste tipo] como substituição dos parêntesis (deste "
+"tipo)."
+d3991 3
+a3993 3
+#: en_US/style.xml:936(para)
+msgid "Use brackets for optional command line entries."
+msgstr "Use os parêntesis rectos para os itens opcionais da linha de comandos."
+d3995 1
+a3995 1
+#: en_US/style.xml:941(para)
+d3997 2
+a3998 3
+"Do not use angle brackets to indicate variables in text, instead use the "
+"<sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref "
+"linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+d4000 2
+a4001 4
+"Não use os símbolos '<' e '>' para indicar as variáveis no texto; em "
+"vez disso, use a marca <sgmltag class=\"starttag\">replaceable</sgmltag>. "
+"Veja a utilização do <xref linkend=\"sn-xml-tags-replaceable\"/> para mais "
+"informações sobre a utilização desta marca."
+d4003 3
+a4005 3
+#: en_US/style.xml:953(term)
+msgid "Capitalization"
+msgstr "Capitalização (Uso de maiúsculas/minúsculas)"
+d4007 3
+a4009 3
+#: en_US/style.xml:955(para)
+msgid "Capitalize in the following situations:"
+msgstr "Aplique a capitalização nas seguintes situações:"
+d4011 4
+a4014 5
+#: en_US/style.xml:960(para)
+msgid "All letters in acronyms, unless the acronym is a well-known exception"
+msgstr ""
+"Todas as letras dos acrónimos, a menos que o acrónimo seja uma excepção "
+"conhecida"
+d4016 3
+a4018 7
+#: en_US/style.xml:966(para)
+msgid "Initial letter of the first word in a list"
+msgstr "A letra inicial da primeira palavra de uma lista"
+
+#: en_US/style.xml:971(para)
+msgid "Initial letter of the first word in a callout"
+msgstr "A letra inicial da primeira palavra de uma chamada de atenção"
+d4020 4
+a4023 2
+#: en_US/style.xml:976(para)
+msgid "Initial letter of a key name, such as the <keycap>Shift</keycap> key"
+d4025 2
+a4026 1
+"A letra inicial do nome de uma tecla, como a tecla <keycap>Shift</keycap>"
+d4028 3
+a4030 3
+#: en_US/style.xml:982(para)
+msgid "Initial letter of a sentence"
+msgstr "A letra inicial de uma frase"
+d4032 1
+a4032 5
+#: en_US/style.xml:986(title)
+msgid "Command Names"
+msgstr "Nomes de Comandos"
+
+#: en_US/style.xml:987(para)
+d4034 2
+a4035 2
+"Avoid starting a sentence with a command name or application name that has a "
+"lowercase initial letter."
+d4037 2
+a4038 2
+"Evite começar uma frase com o nome de um comando ou aplicação que tenha um "
+"nome que começa por minúsculas."
+d4040 3
+a4042 3
+#: en_US/style.xml:994(para)
+msgid "Initial letter of a complete sentence after a colon"
+msgstr "A letra inicial de uma frase completa, a seguir aos dois-pontos"
+d4044 7
+a4050 3
+#: en_US/style.xml:999(para)
+msgid "Do not capitalize in the following situations:"
+msgstr "Não capitalizar nas seguintes situações:"
+d4052 3
+a4054 3
+#: en_US/style.xml:1004(para)
+msgid "A compound term that is followed by an abbreviation or an acronym"
+msgstr "Um termo composto que seja seguido de uma abreviatura ou acrónimo"
+d4056 13
+a4068 3
+#: en_US/style.xml:1010(para)
+msgid "When you want to emphasize something"
+msgstr "Quando quiser aumentar a ênfase sobre algo"
+d4070 8
+a4077 3
+#: en_US/style.xml:1015(para)
+msgid "Variable names"
+msgstr "Nomes de variáveis"
+d4079 3
+a4081 3
+#: en_US/style.xml:1020(para)
+msgid "The initial letter of an incomplete sentence after a colon"
+msgstr "A letra inicial de uma frase incompleta, após os dois-pontos"
+d4083 11
+a4093 3
+#: en_US/style.xml:1029(term)
+msgid "Captions"
+msgstr "Legendas"
+d4095 1
+a4095 1
+#: en_US/style.xml:1031(para)
+d4097 9
+a4105 2
+"Use the same rules as for headings, for all captions accompanying figures "
+"and tables. Do not put a period at the end of a caption."
+d4107 9
+a4115 2
+"Use as mesmas regras dos destaques para todas as legendas das tabelas e "
+"figuras. Não coloque um ponto no fim de uma legenda."
+d4117 10
+a4126 3
+#: en_US/style.xml:1039(term)
+msgid "Colon"
+msgstr "Dois-Pontos (:)"
+d4128 16
+a4143 3
+#: en_US/style.xml:1041(para)
+msgid "Use a colon in the following situations:"
+msgstr "Use os dois-pontos nas seguintes situações:"
+d4145 15
+a4159 3
+#: en_US/style.xml:1046(para)
+msgid "To introduce a list"
+msgstr "Para introduzir uma lista"
+d4161 7
+a4167 3
+#: en_US/style.xml:1051(para)
+msgid "Before an explanation"
+msgstr "Antes de uma explicação"
+d4169 3
+a4171 3
+#: en_US/style.xml:1056(para)
+msgid "After an introduction"
+msgstr "Após uma introdução"
+d4173 3
+a4175 3
+#: en_US/style.xml:1061(para)
+msgid "Do not use a colon in the following situations:"
+msgstr "Não use os dois-pontos nas seguintes situações:"
+d4177 6
+a4182 3
+#: en_US/style.xml:1066(para)
+msgid "To introduce a figure or a table"
+msgstr "Para introduzir uma figura ou uma tabela"
+d4184 3
+a4186 3
+#: en_US/style.xml:1071(para)
+msgid "To introduce headings"
+msgstr "Para introduzir os destaques"
+d4188 13
+a4200 3
+#: en_US/style.xml:1076(para)
+msgid "At the end of an introduction to a procedure"
+msgstr "No fim da introdução de um procedimento"
+d4202 3
+a4204 3
+#: en_US/style.xml:1084(term)
+msgid "Column headings"
+msgstr "Destaques das colunas"
+d4206 12
+a4217 3
+#: en_US/style.xml:1086(para)
+msgid "Use the same rules as for headings."
+msgstr "Use as mesmas regras dos destaques."
+d4219 7
+a4225 3
+#: en_US/style.xml:1092(term)
+msgid "Comma"
+msgstr "Vírgula"
+d4227 3
+a4229 3
+#: en_US/style.xml:1094(para)
+msgid "Use commas in the following situations:"
+msgstr "Use as vírgulas nas seguintes situações:"
+d4231 7
+a4237 3
+#: en_US/style.xml:1099(para)
+msgid "To separate items in a series"
+msgstr "Para separar os itens de uma dada série"
+d4239 7
+a4245 3
+#: en_US/style.xml:1104(para)
+msgid "To separate the parts of a sentence"
+msgstr "Para separar as partes de uma frase"
+d4247 3
+a4249 3
+#: en_US/style.xml:1109(para)
+msgid "To separate nonrestrictive phrases"
+msgstr "Para separar as frases não-restritivas"
+d4251 4
+a4254 3
+#: en_US/style.xml:1114(para)
+msgid "Instead of dashes to set off appositives"
+msgstr "Em vez dos hífenes, para definir apositivos"
+d4256 3
+a4258 3
+#: en_US/style.xml:1119(para)
+msgid "With <emphasis>for example</emphasis> and similar expressions"
+msgstr "Com as expressões <emphasis>por exemplo</emphasis> e similares"
+d4260 9
+a4268 3
+#: en_US/style.xml:1125(para)
+msgid "Do not use commas in the following situations:"
+msgstr "Não use as vírgulas nas seguintes situações:"
+d4270 3
+a4272 3
+#: en_US/style.xml:1130(para)
+msgid "In a series of adjectives used as one modifier"
+msgstr "Numa série de adjectivos usados como um modificador único"
+d4274 4
+a4277 3
+#: en_US/style.xml:1135(para)
+msgid "Between two short independent clauses"
+msgstr "Entre duas cláusulas breves e independentes"
+d4279 5
+a4283 3
+#: en_US/style.xml:1143(term) en_US/emacs-nxml.xml:86(title)
+msgid "Commands"
+msgstr "Comandos"
+d4285 3
+a4287 3
+#: en_US/style.xml:1145(para)
+msgid "Do not use commands as verbs."
+msgstr "Não use os comandos como verbos."
+d4289 1
+a4289 5
+#: en_US/style.xml:1151(term)
+msgid "Contractions"
+msgstr "Contracções"
+
+#: en_US/style.xml:1153(para)
+d4291 3
+a4293 2
+"Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</"
+"emphasis>, or <emphasis>isn't</emphasis>."
+d4295 3
+a4297 2
+"Não use contracções do tipo <emphasis>tá</emphasis>, <emphasis>tar</"
+"emphasis>, or <emphasis>né</emphasis>."
+d4299 3
+a4301 3
+#: en_US/style.xml:1160(term)
+msgid "Dash"
+msgstr "Hífen"
+d4303 1
+a4303 1
+#: en_US/style.xml:1162(para)
+d4305 2
+a4306 3
+"Do not use the em dash or the en dash. Use a paragraph break or a colon "
+"instead, where you want to create an introductory piece of text. If you have "
+"several items that you want to introduce, then you can use a variable list."
+d4308 3
+a4310 4
+"Não use o hífen 'mdash' ou 'ndash'. Use uma quebra de parágrafo ou os dois-"
+"pontos em alternativa onde pretender criar um pedaço introdutório de texto. "
+"Se tiver vários itens que deseja introduzir, então poderá usar uma lista "
+"variável."
+d4312 3
+a4314 3
+#: en_US/style.xml:1171(term)
+msgid "Ellipsis"
+msgstr "Reticências"
+d4316 8
+a4323 3
+#: en_US/style.xml:1173(para)
+msgid "Use an ellipsis in the following situations:"
+msgstr "Use as reticências nas seguintes situações:"
+d4325 4
+a4328 3
+#: en_US/style.xml:1178(para)
+msgid "To show that you have omitted something from a sentence"
+msgstr "Para mostrar que omitiu algo de uma frase"
+d4330 7
+a4336 3
+#: en_US/style.xml:1183(para)
+msgid "To indicate a pause when you quote displayed text"
+msgstr "Para indicar uma pausa quando fizer uma citação do texto apresentado"
+d4338 4
+a4341 3
+#: en_US/style.xml:1191(term)
+msgid "Fractions"
+msgstr "Fracções"
+d4343 1
+a4343 5
+#: en_US/style.xml:1193(para)
+msgid "Follow these rules when using fractions:"
+msgstr "Siga estas regras quando usar as fracções:"
+
+#: en_US/style.xml:1198(para)
+d4345 3
+a4347 2
+"Use numerals for fractions in tables and in units of measurement, but spell "
+"out fractions in prose."
+d4349 13
+a4361 2
+"Use numerais para as fracções nas tabelas e nas unidades de medida, mas "
+"descreva por extenso as fracções."
+d4363 1
+a4363 1
+#: en_US/style.xml:1204(para)
+d4365 6
+a4370 2
+"Use a space between a numeral and a related fraction, if there is a possible "
+"ambiguity. For example: 1 1/2 instead of 11/2."
+d4372 7
+a4378 2
+"Use um espaço entre um numeral e uma fracção relacionada, se puder existir "
+"alguma ambiguidadde. Por exemplo: 1 1/2 em vez de 11/2."
+d4380 1
+a4380 1
+#: en_US/style.xml:1211(para)
+d4382 6
+a4387 2
+"If a fraction is used in a compound modifier, insert a hyphen between the "
+"fraction and the unit of measurement."
+d4389 6
+a4394 2
+"Se uma fracção for usada num modificador composto, indique um hífen entre a "
+"fracção e a unidade de medida."
+d4396 1
+a4396 13
+#: en_US/style.xml:1220(term)
+msgid "Gender"
+msgstr "Género"
+
+#: en_US/style.xml:1222(para)
+msgid "Refer to <xref linkend=\"sn-fundamentals-9\"/>."
+msgstr "Veja em <xref linkend=\"sn-fundamentals-9\"/>."
+
+#: en_US/style.xml:1228(term)
+msgid "Grammar"
+msgstr "Gramática"
+
+#: en_US/style.xml:1230(para)
+d4398 7
+a4404 4
+"Use standard American English grammar rules, refer to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+d4406 8
+a4413 12
+"Use as regras-padrão do Inglês Americano (para documentos em Inglês); veja "
+"em <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www."
+"press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\"> http://www.press."
+"uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+
+#: en_US/style.xml:1241(para)
+msgid "Use the following capitalization rules in headings:"
+msgstr "Use as seguintes regras de capitalização nos destaques:"
+
+#: en_US/style.xml:1246(para)
+msgid "Initial uppercase letter of the first word"
+msgstr "Letra maiúscula inicial da primeira palavra"
+d4415 8
+a4422 2
+#: en_US/style.xml:1251(para)
+msgid "Initial uppercase letter for all nouns, adjectives, and verbs."
+d4424 6
+a4429 1
+"Letra maiúscula inicial para todos os substantivos, adjectivos e verbos."
+d4431 1
+a4431 1
+#: en_US/style.xml:1257(para)
+d4433 5
+a4437 2
+"All lowercase letters for conjunctions, articles, and prepositions of fewer "
+"than four letters"
+d4439 5
+a4443 2
+"Todas as letras em minúsculas para as conjunções, artigos e proposições com "
+"menos de quatro letras"
+d4445 3
+a4447 3
+#: en_US/style.xml:1263(para)
+msgid "Initial uppercase letter for prepositions of four letters or longer"
+msgstr "Letra maiúscula inicial para as proposições com quatro ou mais letras"
+d4449 11
+a4459 3
+#: en_US/style.xml:1269(para)
+msgid "Initial uppercase letter for conjunctions of four letters or longer"
+msgstr "Letra maiúscula inicial para as conjunções com quatro ou mais letras"
+d4461 3
+a4463 3
+#: en_US/style.xml:1280(term)
+msgid "Hyphen"
+msgstr "Hífen"
+d4465 14
+a4478 3
+#: en_US/style.xml:1282(para)
+msgid "Use hyphens in the following situations:"
+msgstr "Use os hífenes nas seguintes situações:"
+d4480 1
+a4480 9
+#: en_US/style.xml:1287(para)
+msgid "With a numeral in a compound modifier"
+msgstr "Com um numeral num modificador composto"
+
+#: en_US/style.xml:1291(para)
+msgid "To prevent ambiguity"
+msgstr "Para evitar ambiguidades"
+
+#: en_US/style.xml:1296(para)
+d4482 6
+a4487 3
+"With some standard prefixes and suffixes. Use the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) for guidance"
+d4489 7
+a4495 3
+"Com alguns prefixos e sufixos padrão. Use o <citetitle>American Heritage "
+"Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://"
+"www.bartleby.com/61/</ulink>) para ter algumas linhas-guia"
+d4497 1
+a4497 5
+#: en_US/style.xml:1305(para)
+msgid "In spelled-out fractions"
+msgstr "Nas fracções por extenso"
+
+#: en_US/style.xml:1310(para)
+d4499 1
+a4499 2
+"In variable names of two or more words, such as <replaceable>directory-name</"
+"replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+d4501 2
+a4502 3
+"Nos nomes de variáveis com duas ou mais palavras, como o <replaceable>nome-"
+"pasta</replaceable>. Nota: <replaceable>filename</replaceable> (nome de "
+"ficheiro) é uma excepção."
+d4504 3
+a4506 3
+#: en_US/style.xml:1317(para)
+msgid "Do not use hyphens in the following situations:"
+msgstr "Não use hífenes nas seguintes situações:"
+d4508 4
+a4511 3
+#: en_US/style.xml:1322(para)
+msgid "For industry-accepted terms"
+msgstr "Para os termos aceites na indústria"
+d4513 1
+a4513 13
+#: en_US/style.xml:1327(para)
+msgid "To construct verbs"
+msgstr "Para construir verbos (excepto nos compostos)"
+
+#: en_US/style.xml:1332(para)
+msgid "With an adverb ending in <emphasis>ly</emphasis>"
+msgstr "Com um advérbio terminado em <emphasis>mente</emphasis>"
+
+#: en_US/style.xml:1337(para)
+msgid "With numerals as single modifiers"
+msgstr "Com os numerais como modificadores únicos"
+
+#: en_US/style.xml:1342(para)
+d4515 4
+a4518 3
+"With a word that is listed as unhyphenated in the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+d4520 5
+a4524 3
+"Com uma palavra que aparece como não-hifenizada no <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) e que use um prefixo comum"
+d4526 7
+a4532 10
+#: en_US/style.xml:1351(para)
+msgid "With trademarked terms"
+msgstr "Com termos de marcas registadas"
+
+#: en_US/style.xml:1359(term)
+msgid "Latin terms"
+msgstr "Termos em Latim"
+
+#: en_US/style.xml:1361(para)
+msgid "Do not use Latin terms. Use an equivalent English term instead."
+d4534 5
+a4538 1
+"Não use termos em Latim. Tente usar um termo em Inglês, em alternativa."
+d4540 3
+a4542 3
+#: en_US/style.xml:1368(term)
+msgid "Like"
+msgstr "Do Tipo"
+d4544 1
+a4544 1
+#: en_US/style.xml:1370(para)
+d4546 3
+a4548 2
+"Do not use the term <emphasis>like</emphasis> to denote equivalence or "
+"similarity."
+d4550 4
+a4553 2
+"Não use o <emphasis>do tipo</emphasis> para demarcar uma equivalência ou "
+"semelhança."
+d4555 3
+a4557 4
+#: en_US/style.xml:1379(para)
+msgid "Introduce a list with a complete sentence that ends with a colon."
+msgstr ""
+"Introduza uma lista com uma frase completa que termine com dois-pontos."
+d4559 1
+a4559 9
+#: en_US/style.xml:1386(term)
+msgid "Numbers"
+msgstr "Números"
+
+#: en_US/style.xml:1388(para)
+msgid "Spell out numbers in the following situations:"
+msgstr "Diga os números por extenso nas seguintes situações:"
+
+#: en_US/style.xml:1393(para)
+d4561 12
+a4572 2
+"Numbers from zero through nine unless the number is part of a measurement"
+msgstr "Números de zero a nove, a menos que o número faça parte de uma medida"
+d4574 3
+a4576 3
+#: en_US/style.xml:1398(para)
+msgid "Approximations"
+msgstr "Aproximações"
+d4578 1
+a4578 1
+#: en_US/style.xml:1403(para)
+d4580 2
+a4581 2
+"Extreme values such as <emphasis>million</emphasis>, but precede the value "
+"with a numeral"
+d4583 2
+a4584 2
+"Valores extremos como o <emphasis>milhão</emphasis>, se bem que pode "
+"anteceder o valor com um numeral"
+d4586 3
+a4588 3
+#: en_US/style.xml:1409(para)
+msgid "Any number that begins a sentence"
+msgstr "Qualquer número que inicie uma frase"
+d4590 3
+a4592 7
+#: en_US/style.xml:1414(para)
+msgid ""
+"A number that is immediately followed by a numeral, for example: "
+"<literal>two 10 MB files</literal>"
+msgstr ""
+"Um número que seja seguido imediatamente de um numeral, como por exemplo: "
+"<literal>dois ficheiros de 10 MB</literal>"
+d4594 3
+a4596 3
+#: en_US/style.xml:1423(term)
+msgid "Numerals"
+msgstr "Numerais"
+d4598 3
+a4600 5
+#: en_US/style.xml:1425(para)
+msgid "Use numerals in the following situations:"
+msgstr ""
+"Use os numerais (em oposição aos números por extenso) nas seguintes "
+"situações:"
+d4602 3
+a4604 3
+#: en_US/style.xml:1430(para)
+msgid "The number 10 or greater"
+msgstr "O número 10 ou superior"
+d4606 3
+a4608 3
+#: en_US/style.xml:1435(para)
+msgid "Negative numbers"
+msgstr "Números negativos"
+d4610 3
+a4612 3
+#: en_US/style.xml:1439(para)
+msgid "Most fractions"
+msgstr "A maioria das fracções"
+d4614 3
+a4616 3
+#: en_US/style.xml:1444(para)
+msgid "Percentages"
+msgstr "Percentagens"
+d4618 3
+a4620 3
+#: en_US/style.xml:1449(para)
+msgid "Decimals"
+msgstr "Casas decimais"
+d4622 3
+a4624 3
+#: en_US/style.xml:1454(para)
+msgid "Measurements"
+msgstr "Medidas"
+d4626 3
+a4628 3
+#: en_US/style.xml:1459(para)
+msgid "Units of time smaller than one second"
+msgstr "Unidades de tempo inferiores ao segundo"
+d4630 3
+a4632 3
+#: en_US/style.xml:1464(para)
+msgid "References to bits and bytes"
+msgstr "Referências a 'bits' e 'bytes'"
+d4634 7
+a4640 3
+#: en_US/style.xml:1472(term)
+msgid "Parentheses"
+msgstr "Parêntesis"
+d4642 7
+a4648 3
+#: en_US/style.xml:1474(para)
+msgid "Use parentheses in the following situations:"
+msgstr "Use os parêntesis nas seguintes situações:"
+d4650 1
+a4650 1
+#: en_US/style.xml:1479(para)
+d4652 2
+a4653 2
+"To contain the abbreviation of a term on the first occurrence of the full "
+"term"
+d4655 2
+a4656 2
+"Para conter a abreviatura de um termo na primeira ocorrência do termo "
+"completo"
+d4658 4
+a4661 2
+#: en_US/style.xml:1485(para)
+msgid "In man page references, specifically the section number"
+d4663 3
+a4665 1
+"Nas referências a páginas do 'man', especificamente no número da secção"
+d4667 3
+a4669 3
+#: en_US/style.xml:1493(term)
+msgid "Period"
+msgstr "Ponto final"
+d4671 3
+a4673 3
+#: en_US/style.xml:1495(para)
+msgid "Use a period in the following situations:"
+msgstr "Use um ponto final nas seguintes situações:"
+d4675 7
+a4681 3
+#: en_US/style.xml:1500(para)
+msgid "To end a sentence"
+msgstr "Para terminar uma frase"
+d4683 3
+a4685 3
+#: en_US/style.xml:1505(para)
+msgid "In file and directory names"
+msgstr "Nos nomes dos ficheiros e pastas"
+d4687 5
+a4691 2
+#: en_US/style.xml:1510(para)
+msgid "In abbreviations that can be mistaken for words, such as a.m. and U.S."
+d4693 20
+a4712 2
+"Nas abreviaturas que possam ser confundidas com palavras, como por exemplo C."
+"O.M., E.U."
+d4714 3
+a4716 3
+#: en_US/style.xml:1519(term)
+msgid "Punctuation"
+msgstr "Pontuação"
+d4718 1
+a4718 1
+#: en_US/style.xml:1521(para)
+d4720 4
+a4723 5
+"Use standard American English punctuation rules. In addition to the specific "
+"points of punctuation in this section, refer also to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+d4725 4
+a4728 5
+"Use as regras de pontuação normais do Inglês Americano. Para além dos sinais "
+"de pontuação específicos nesta secção, veja também no <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+d4730 1
+a4730 5
+#: en_US/style.xml:1531(term)
+msgid "Punctuation in numbers"
+msgstr "Pontuação nos números"
+
+#: en_US/style.xml:1533(para)
+d4732 3
+a4734 2
+"Do not use a comma in numerals of four digits. Use a comma in numerals of "
+"more than four digits."
+d4736 3
+a4738 2
+"Não use um ponto nos numerais de quatro algarismos. Use o ponto nos numerais "
+"com mais de quatro algarismos."
+d4740 1
+a4740 5
+#: en_US/style.xml:1540(term)
+msgid "Quotation marks"
+msgstr "Marcas de citações"
+
+#: en_US/style.xml:1542(para)
+d4742 2
+a4743 4
+"Use quotation marks to indicate material that is taken verbatim from another "
+"source. Do not use quotation marks to excuse terms from legitimacy. If the "
+"term is not legitimate, then use another term. If you must use that term, "
+"declare the term in the glossary and make the term legitimate."
+d4745 6
+a4750 4
+"Use as marcas de citação (plicas, aspas) para indicar o material que foi "
+"explicitamente retirado de outra fonte. Não use as aspas para retirar a "
+"legitimidade dos termos. Se o termo não for legítimo, então use outro termo. "
+"Se precisar de usar esse termo, declare-o no glossário e torne-o legítimo."
+d4752 3
+a4754 3
+#: en_US/style.xml:1553(term)
+msgid "See v. Refer to"
+msgstr "'Veja' vs. 'Consulte'"
+d4756 3
+a4758 20
+#: en_US/style.xml:1555(para)
+msgid ""
+"When referring a user to another resource, use \"refer to\" instead of \"see"
+"\", and \"refer also to\" instead of \"see also\". This differentiates from "
+"the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag"
+"\">seealso</sgmltag> tags that are used in indexing. These tags create "
+"special links in the index. To be consistent throughout the document, we "
+"reserve the special words \"see\" and \"see also\" for hyperlinked index "
+"references, and use \"refer to\" and \"refer also to\" for non-hyperlinked "
+"and non-indexed references."
+msgstr ""
+"Ao referenciar um outro recurso, use o \"consulte\" em vez do \"veja\", ou "
+"então \"consulte também\" em vez de \"veja também\". Isto cria uma separação "
+"em relação às marcas <sgmltag class=\"starttag\">see</sgmltag> e <sgmltag "
+"class=\"starttag\">seealso</sgmltag>, as quais são usadas na indexação. "
+"Estas marcas criam referências especiais no índice. Para ser consistente ao "
+"longo do tempo, reservam-se as palavras especiais \"ver\" e \"ver também\" "
+"para o caso das referências com hiperligações, sendo que existe o \"consultar"
+"\" e o \"consultar também\" para o caso das referências não-ligadas e não-"
+"indexadas."
+d4760 3
+a4762 3
+#: en_US/style.xml:1570(term)
+msgid "Semicolon"
+msgstr "Ponto-e-vírgula"
+d4764 3
+a4766 3
+#: en_US/style.xml:1572(para)
+msgid "Do not use semicolons."
+msgstr "Não use pontos-e-vírgulas."
+d4768 3
+a4770 3
+#: en_US/style.xml:1578(term)
+msgid "Slash"
+msgstr "Barra"
+d4772 1
+a4772 1
+#: en_US/style.xml:1580(para)
+d4774 3
+a4776 3
+"Except where required as part of a filename, do not use slashes \"/\" in "
+"your writing. The construction <literal>and/or</literal>, for example, does "
+"not exist. Use one or the other term instead."
+d4778 3
+a4780 3
+"Excepto no caso de ser necessário como parte do nome de um ficheiro, não use "
+"as barras \"/\" na sua escrita. A construção <literal>e/ou</literal>, por "
+"exemplo, não existe. Use um termo ou o outro, em alternativa."
+d4782 3
+a4784 3
+#: en_US/style.xml:1589(term)
+msgid "Spelling"
+msgstr "Ortografia"
+d4786 1
+a4786 1
+#: en_US/style.xml:1591(para)
+d4788 2
+a4789 3
+"Use standard American English spelling rules, refer to the "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+d4791 2
+a4792 4
+"Use as regras-padrão ortográficas do Inglês Americano; consulte o "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) para obter mais "
+"informações."
+d4794 3
+a4796 3
+#: en_US/style.xml:1600(term)
+msgid "Titles"
+msgstr "Títulos"
+d4798 3
+a4800 3
+#: en_US/style.xml:1602(para)
+msgid "For manual titles use the same rules as for headings."
+msgstr "Para os títulos manuais, use as mesmas regras dos destaques."
+d4802 5
+a4806 3
+#: en_US/style.xml:1608(term)
+msgid "Units"
+msgstr "Unidades"
+d4808 3
+a4810 3
+#: en_US/style.xml:1610(para)
+msgid "Follow these rules when using units:"
+msgstr "Siga estas regras ao usar unidades:"
+d4812 2
+a4813 4
+#: en_US/style.xml:1615(para)
+msgid ""
+"Use standard abbreviations for units of measurements, do not invent your own "
+"abbreviations."
+d4815 5
+a4819 2
+"Use as abreviaturas-padrão para as unidades de medida, não invente as suas "
+"próprias."
+d4821 3
+a4823 7
+#: en_US/style.xml:1621(para)
+msgid ""
+"For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of "
+"Electrical and Electronics Terms</citetitle>."
+msgstr ""
+"Para mais informações, veja em <citetitle>IEEE Standard Dictionary of "
+"Electrical and Electronics Terms</citetitle>."
+d4825 3
+a4827 4
+#: en_US/style.xml:1630(para)
+msgid "Use periods for abbreviated units that might be mistaken for a word."
+msgstr ""
+"Use pontos nas unidades abreviadas que possam ser confundidas com palavras."
+d4829 5
+a4833 7
+#: en_US/style.xml:1636(para)
+msgid ""
+"Most standard abbreviations of units account for both singular and plural "
+"usage."
+msgstr ""
+"A maior parte das abreviaturas-padrão das unidades têm em conta a utilização "
+"singular e plural."
+d4835 5
+a4839 3
+#: en_US/style.xml:1642(para)
+msgid "Insert a space between the numeral and the unit of measurement."
+msgstr "Indique um espaço entre o numeral e a unidade de medida."
+d4841 4
+a4844 3
+#: en_US/style.xml:1656(title)
+msgid "Composition Tips"
+msgstr "Sugestões de Composição"
+d4846 1
+a4846 6
+#. This section will collect miscellanea and advice for specific
+#. situations that the FDP editors encounter. I hope they will feel
+#. free to e-mail me sticky situations or particularly interesting
+#. examples of work they've beautified. Hopefully not too much will be
+#. drawn from my own work! - PWF.
+#: en_US/style.xml:1668(para)
+d4848 2
+a4849 4
+"This section contains usage tips based on situations the Fedora "
+"Documentation Project editors have encountered in the past. You should read "
+"and understand these examples to improve your own documentation. The Fedora "
+"Documentation Project editors welcome additional examples."
+d4851 2
+a4852 5
+"Esta secção contém sugestões de utilização que se baseiam nas situações que "
+"os editores do Projecto de Documentação do Fedora encontraram no passado. "
+"Deverá ler e compreender estes exemplos para melhorar a sua própria "
+"documentação. Os editores do Projecto de Documentação do Fedora agradecem os "
+"exemplos adicionais."
+d4854 3
+a4856 3
+#: en_US/style.xml:1676(title)
+msgid "Active Voice"
+msgstr "Voz Activa"
+d4858 13
+a4870 21
+#: en_US/style.xml:1677(para)
+msgid ""
+"Always use active voice, except when it is awkward to do so. The tutorial "
+"tells the user how to accomplish a task, and should give instructions "
+"clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. "
+"These words are redundant in a tutorial, since the reader assumes you are "
+"outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" "
+"\"might,\" and other words that indicate you are unsure about the subject "
+"matter. Your tutorial should cover a subject authoritatively. The reader "
+"should never be concerned about unknown effects of following the tutorial."
+msgstr ""
+"Use sempre a voz activa, excepto se ficar estranha a sua utilização num "
+"determinado contexto. O tutorial diz ao utilizador como desempenhar uma "
+"tarefa, devendo dar as instruções de forma clara e concisa. Evite usar os "
+"termos \"dever\", \"ser necessário\", entre outros. Estas palavras são "
+"redundantes num tutorial, dado que o leitor assume que você já está a "
+"destacar os passos necessários para efectuar uma tarefa. Evite também usar "
+"os termos \"talvez\", \"poderá\" e outras palavras que indiquem que não "
+"tenha a certeza sobre a matéria em estudo. O seu tutorial deverá cobrir um "
+"assunto de forma autoritária. O leitor nunca se deverá preocupar com os "
+"efeitos desconhecidos de seguir o tutorial."
+d4872 6
+a4877 3
+#: en_US/style.xml:1690(title)
+msgid "Incorrect: Passive voice"
+msgstr "Incorrecto: Voz passiva"
+d4879 3
+a4881 3
+#: en_US/style.xml:1691(para)
+msgid "The <command>yum update</command> command must be run."
+msgstr "O comando <command>yum update</command> deverá ser executado."
+d4883 3
+a4885 3
+#: en_US/style.xml:1694(para)
+msgid "You might want to run the <command>yum update</command> command."
+msgstr "Poderá querer executar o comando <command>yum update</command>."
+d4887 3
+a4889 3
+#: en_US/style.xml:1700(title)
+msgid "Correct: Active voice"
+msgstr "Correcto: Voz activa"
+d4891 7
+a4897 3
+#: en_US/style.xml:1701(para)
+msgid "Run the <command>yum update</command> command."
+msgstr "Execute o comando <command>yum update</command>."
+d4899 3
+a4901 3
+#: en_US/style.xml:1708(title)
+msgid "Present Tense"
+msgstr "Tempo Presente"
+d4903 1
+a4903 1
+#: en_US/style.xml:1709(para)
+d4905 3
+a4907 5
+"Write in the present tense. A good rule of thumb is that the words \"will\" "
+"and \"shall\" are almost never needed in describing what the user should do "
+"or see. They add unnecessary length to sentences and can confuse "
+"translators. They are also often indicators of passive voice; refer also to "
+"<xref linkend=\"sn-misc-active-voice\"/>."
+d4909 3
+a4911 6
+"Escreva no tempo presente. Uma boa regra de algibeira é que palavras como "
+"\"será\" ou \"deverá\" quase nunca são necessárias para descrever o que o "
+"utilizador deverá ou fazer. Estas adicionam um tamanho desnecessário às "
+"frases e poderão confundir os tradutores. Estas normalmente também são "
+"indicações de voz passiva; consule também o tópico <xref linkend=\"sn-misc-"
+"active-voice\"/>."
+d4913 3
+a4915 3
+#: en_US/style.xml:1718(title)
+msgid "Incorrect: Future tense"
+msgstr "Incorrecto: Tempo futuro"
+d4917 3
+a4919 3
+#: en_US/style.xml:1719(para)
+msgid "The application will display a list of target files."
+msgstr "A aplicação irá mostrar uma lista dos ficheiros-alvo."
+d4921 3
+a4923 3
+#: en_US/style.xml:1722(para)
+msgid "A list of target files will be displayed by the application."
+msgstr "Uma lista de ficheiros-alvo será apresentada pela aplicação."
+d4925 3
+a4927 3
+#: en_US/style.xml:1727(title)
+msgid "Correct: Present tense"
+msgstr "Correcto: Tempo presente"
+d4929 4
+a4932 3
+#: en_US/style.xml:1728(para)
+msgid "The application displays a list of target files."
+msgstr "A aplicação mostra uma lista dos ficheiros-alvo."
+d4934 3
+a4936 3
+#: en_US/style.xml:1735(title)
+msgid "Narrative Voice"
+msgstr "Voz Narrativa"
+d4938 3
+a4940 15
+#: en_US/style.xml:1736(para)
+msgid ""
+"Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself "
+"the writer (whether including the reader or not), the Fedora Documentation "
+"Project, the Fedora community, or any other group. Do not refer to users "
+"with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word "
+"\"one.\" It is acceptable to refer to the reader with the second person "
+"pronoun \"you.\""
+msgstr ""
+"Não use a primeira pessoa \"Eu,\" ou \"nós\" para se referir a si próprio "
+"como escritor (quer inclua o leitor quer não), o Projecto de Documentação do "
+"Fedora, a comunidade do Fedora ou qualquer outro grupo. Não faça referências "
+"aos utilizadores com um pronome na terceira pessoa (\"ele\", \"ela\" ou "
+"\"eles/elas\"). É aceitável fazer referências ao leitor na segunda pessoa "
+"com o pronome \"você\"."
+d4942 3
+a4944 3
+#: en_US/style.xml:1745(title)
+msgid "Incorrect: First or third person"
+msgstr "Incorrecto: Primeira ou terceira pessoa"
+d4946 3
+a4948 7
+#: en_US/style.xml:1746(para)
+msgid ""
+"As described in the last section, I always run <command>up2date</command> "
+"before configuring the Samba server."
+msgstr ""
+"Como foi descrito na última secção, eu executo sempre o <command>up2date</"
+"command> antes de configurar o servidor do Samba."
+d4950 3
+a4952 7
+#: en_US/style.xml:1751(para)
+msgid ""
+"If the user needs to back up his or her files, s/he should use the "
+"<command>tar</command> or <command>cpio</command> command."
+msgstr ""
+"Se o utilizador precisar de salvaguardar os ficheiros dele ou dela, ele/a "
+"deverá usar o comando <command>tar</command> ou <command>cpio</command>."
+d4954 3
+a4956 3
+#: en_US/style.xml:1757(title)
+msgid "Correct: Second (or no) person"
+msgstr "Correcto: Segunda pessoa (ou omisso)"
+d4958 3
+a4960 7
+#: en_US/style.xml:1758(para)
+msgid ""
+"Refer to the section on <command>up2date</command> before configuring the "
+"Samba server."
+msgstr ""
+"Veja a secção sobre o <command>up2date</command> antes de configurar o "
+"servidor do Samba."
+d4962 3
+a4964 7
+#: en_US/style.xml:1762(para)
+msgid ""
+"If necessary, users can back up files with the <command>tar</command> or "
+"<command>cpio</command> command."
+msgstr ""
+"Se necessário, os utilizadores poderão salvaguardar os ficheiros com o "
+"comando <command>tar</command> ou <command>cpio</command>."
+d4966 3
+a4968 3
+#: en_US/style.xml:1770(title)
+msgid "Negative Words"
+msgstr "Palavras pela Negativa"
+d4970 3
+a4972 14
+#: en_US/style.xml:1771(para)
+msgid ""
+"Avoid negative words when possible, since they give documentation an overly "
+"dogmatic tone. The word \"avoid\" is useful for this purpose. Note that "
+"contractions are often used for negative words such as <emphasis>don't</"
+"emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-"
+"contractions\"/>."
+msgstr ""
+"Evite as palavras negativas sempre que possível, dado que atribuem à "
+"documentação um carácter dogmático, de certa forma. A palavra \"evitar\" é "
+"útil para esse fim. De um modo geral na língua inglesa, as contracções são "
+"usadas para as palavras negativas como o <emphasis>don't</emphasis> ou o "
+"<emphasis>can't</emphasis>. Consulte a secção <xref linkend=\"vle-"
+"contractions\"/>."
+d4974 3
+a4976 3
+#: en_US/style.xml:1782(title)
+msgid "Uncertainty"
+msgstr "Incerteza"
+d4978 3
+a4980 16
+#: en_US/style.xml:1783(para)
+msgid ""
+"Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the "
+"like. While occasional use of these constructions is acceptable, overuse "
+"reduces the authority of your documentation. The documentation should "
+"adequately cover a stock installation of Fedora. It is impossible for a "
+"tutorial-length document to cover every possible configuration scenario. "
+"Address the most common scenarios and note discrepancies only as required."
+msgstr ""
+"Evite o uso excessivo do \"tipicamente\", \"normalmente\", \"na maior parte"
+"\", \"muitos\", entre outros. Embora seja aceitável um uso ocasional destas "
+"conjugações, o uso em ecesso reduz a autoridade da sua documentação. A "
+"documentação deverá cobrir de forma adequada uma instalação predefinida do "
+"Fedora. É impossível, para um documento com a dimensão de um tutorial, "
+"cobrir todos os cenários de configuração possíveis. Analise os cenários mais "
+"comuns e aponte apenas as discrepâncias mais necessárias."
+d4982 3
+a4984 3
+#: en_US/style.xml:1795(title)
+msgid "Redundant Coverage"
+msgstr "Cobertura Redundante"
+d4986 3
+a4988 16
+#: en_US/style.xml:1796(para)
+msgid ""
+"Avoid covering redundant material, such as how to update a Fedora system. "
+"These overarching topics may be covered in other tutorials. Writers "
+"frequently violate this guideline because they feel their tutorial is not "
+"long enough. Keep your tutorial from wandering off-topic. Instead, refer the "
+"reader to a separate tutorial whenever possible for complete coverage of "
+"that topic."
+msgstr ""
+"Evite a cobertura de material redundante, como a actualização de um sistema "
+"Fedora. Estes tópicos mais complicados podem ser cobertos noutros tutoriais. "
+"Os escritores violam normalmente esta recomendação por acharem que o seu "
+"tutorial não é suficientemente comprido. Mantenha o seu tutorial com o "
+"tópico bem definido e sem grandes desvios. Em vez disso, indique ao leitor "
+"para consultar um tutorial sparado, sempre que possível, para uma cobertura "
+"completa desse tópico."
+d4990 3
+a4992 3
+#: en_US/style.xml:1808(title)
+msgid "Self-referential Value Judgments"
+msgstr "Juízos de Valor com Referências Próprias"
+d4994 3
+a4996 22
+#: en_US/style.xml:1809(para)
+msgid ""
+"Avoid statements such as \"One of the most important things to do is "
+"<replaceable>XYZ</replaceable>.\" If the procedure is important, the reader "
+"already expects it to be in your tutorial. The converse is also true: If a "
+"procedure appears in your tutorial, the reader expects it is important. This "
+"is especially true if you use a whole section for the procedure in question. "
+"Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as "
+"required. If the whole section concerns how to do <replaceable>XYZ</"
+"replaceable>, leave this sentence out entirely. Refer also to <xref linkend="
+"\"vle-golden-rule-4\"/>."
+msgstr ""
+"Evite frases do tipo \"Uma das coisas mais importantes a fazer é "
+"<replaceable>XYZ</replaceable>.\" Se o procedimento for importante, o leitor "
+"já está à espera dele no seu tutorial. O inverso também se aplica: se um "
+"procedimento aparece no seu tutorial, o leitor espera que este seja "
+"importante. Isto é particularmente verdadeiro se usar uma secção inteira "
+"para o procedimento em questão. Basta dizer, \"Faça <replaceable>XYZ</"
+"replaceable>.\". Depois disso, desenvolva de acordo com as necessidades. Se "
+"a secção completa disser respeito à forma como fazer <replaceable>XYZ</"
+"replaceable>, retire esta frase por inteiro. Consulte também a secção <xref "
+"linkend=\"vle-golden-rule-4\"/>."
+d4998 3
+a5000 3
+#: en_US/style.xml:1824(title)
+msgid "Precision of Language"
+msgstr "Precisão da Linguagem"
+d5002 3
+a5004 8
+#: en_US/style.xml:1825(para)
+msgid ""
+"Use precise words for actions users should take. Do not instruct users to "
+"\"go\" to a selection, or \"find\" a menu."
+msgstr ""
+"Use palavras exactas para as acções que os utilizadores deverão efectuar. "
+"Não diga aos utilizadores para \"ir\" para uma selecção ou \"procurar\" um "
+"menu."
+d5006 3
+a5008 3
+#: en_US/style.xml:1830(title)
+msgid "Incorrect: Imprecise wording"
+msgstr "Incorrecto: Palavras pouco exactas"
+d5010 1
+a5010 1
+#: en_US/style.xml:1833(para)
+d5012 2
+a5013 2
+"Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</"
+"guimenuitem>"
+d5015 2
+a5016 1
+"Vá a <guimenu>Menu Principal</guimenu> -> <guimenuitem>XPTO</guimenuitem>"
+d5018 1
+a5018 9
+#: en_US/style.xml:1839(para)
+msgid "Find the option labeled <guilabel>Search</guilabel>"
+msgstr "Descubra a opção <guilabel>Procurar</guilabel>"
+
+#: en_US/style.xml:1846(title)
+msgid "Correct: Precise wording"
+msgstr "Correcto: Frases exactas"
+
+#: en_US/style.xml:1849(para)
+d5020 2
+a5021 2
+"From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</"
+"guimenuitem>"
+d5023 2
+a5024 2
+"No <guimenu>Menu Principal</guimenu>, seleccione o <guimenuitem>XPTO</"
+"guimenuitem>"
+d5026 3
+a5028 3
+#: en_US/style.xml:1855(para)
+msgid "Select the <guilabel>Search</guilabel> option"
+msgstr "Seleccione a opção <guilabel>Procurar</guilabel>"
+d5030 3
+a5032 3
+#: en_US/style.xml:1862(title)
+msgid "Do Not Discriminate Against Non-GUI Users"
+msgstr "Não Discrimine em Relação aos Utilizadores Não-Gráficos"
+d5034 2
+a5035 1
+#: en_US/style.xml:1863(para)
+d5037 2
+a5038 3
+"If you are writing about a GUI-only application, you may use \"click\" "
+"freely. If you are writing about an application that has a text-mode "
+"interface, use \"select\" instead as shown above."
+d5040 6
+a5045 4
+"Se estiver a escrever a escrever sobre uma aplicação somente gráfica, poderá "
+"usar o termo \"carregar\" ou \"clicar\" à vontade. Se estiver a escrever "
+"acerca de uma aplicação que também tem uma interface em modo texto, use o "
+"\"seleccionar\" como aparece acima."
+d5047 3
+a5049 3
+#: en_US/style.xml:1874(title)
+msgid "DocBook Tips"
+msgstr "Sugestões do DocBook"
+d5051 3
+a5053 7
+#: en_US/style.xml:1875(para)
+msgid ""
+"This section contains tips on how to use DocBook tags more effectively in "
+"your documentation."
+msgstr ""
+"Esta secção contém sugestões sobre a utilização mais eficiente da marcas de "
+"DocBook na sua documentação."
+d5055 3
+a5057 3
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:268(title)
+msgid "Admonitions"
+msgstr "Advertências"
+d5059 3
+a5061 13
+#: en_US/style.xml:1882(para)
+msgid ""
+"Avoid overuse of admonitions. Keep admonitions short and effective by using "
+"only the most important material inside the admonition. Move any background "
+"material required to explain the admonition statements outside the "
+"admonition. Use a short but descriptive title for an admonition. Use title "
+"case for the admonition title."
+msgstr ""
+"Evite o uso excessivo de advertências. Mantenha-as resumidas e efectivas, "
+"usando apenas o material mais importante dentro da advertência. Passe todo o "
+"material de segundo plano necessário para explicar as advertências para fora "
+"destas. Use um título breve mas descritivo para uma advertência. Use a "
+"capitalização no título da advertência."
+d5063 4
+a5066 3
+#: en_US/style.xml:1891(title)
+msgid "Incorrect: Lengthy admonition"
+msgstr "Incorrecto: Advertência comprida"
+d5068 4
+a5071 3
+#: en_US/style.xml:1894(title)
+msgid "Use <command>sfdisk</command> to check input"
+msgstr "Use o <command>sfdisk</command> para verificar os dados de entrada"
+d5073 1
+a5073 1
+#: en_US/style.xml:1895(para)
+d5075 2
+a5076 6
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+d5078 2
+a5079 7
+"O comando <command>sfdisk</command> aceita um ficheiro de programa como "
+"dados de entrada para configurar as partições num disco rígido. Em alguns "
+"casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de "
+"entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, "
+"criando uma tabela de partições incorrecta no seu disco. Use sempre o "
+"comando <command>sfdisk -n</command> para verificar o seu ficheiro antes de "
+"efectuar gravações no disco."
+d5081 3
+a5083 3
+#: en_US/style.xml:1909(title)
+msgid "Correct: Brief admonition"
+msgstr "Correcto: Advertência breve"
+d5085 3
+a5087 3
+#: en_US/style.xml:1917(title)
+msgid "Check Input"
+msgstr "Verifique os Dados de Entrada"
+d5089 1
+a5089 1
+#: en_US/style.xml:1918(para)
+d5091 2
+a5092 2
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+d5094 11
+a5104 2
+"Use sempre o comando <command>sfdisk -n</command> para verificar os seus "
+"dados de entrada, antes de gravar no disco."
+d5106 1
+a5106 1
+#: en_US/style.xml:1910(para)
+d5108 4
+a5111 5
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"<warning><placeholder-1/><placeholder-2/></warning>"
+d5113 4
+a5116 6
+"O comando <command>sfdisk</command> aceita um ficheiro de programa como "
+"dados de entrada para configurar as partições num disco rígido. Em alguns "
+"casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de "
+"entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, "
+"criando uma tabela de partições incorrecta no seu disco."
+"<warning><placeholder-1/><placeholder-2/></warning>"
+d5118 3
+a5120 11
+#: en_US/style.xml:1925(para)
+msgid ""
+"Avoid punctuation in titles for sections or admonitions, except for commas "
+"only where demanded. Use a title that says something about the admonition "
+"comment, such as \"Reboot Required,\" instead of simply using the admonition "
+"type for a title (\"Note\")."
+msgstr ""
+"Evite a pontuação nos títulos das secções ou advertências, excepto as "
+"vírgulas e somente quando necessário. Use um título que diga algo sobre o "
+"comentário da advertência, como \"É Necessário Reiniciar,\" em vez de usar "
+"apenas o tipo de advertência como título (\"Nota\")."
+d5122 1
+a5122 1
+#: en_US/style.xml:1932(para)
+d5124 5
+a5128 1
+"Follow the capitalization rules for headings in the title of an admonition."
+d5130 5
+a5134 1
+"Siga as regras de capitalização dos destaques no título de uma advertência."
+d5136 1
+a5136 5
+#: en_US/style.xml:1939(title)
+msgid "The <sgmltag class=\"starttag\">replaceable</sgmltag> Tag"
+msgstr "A Marca <sgmltag class=\"starttag\">replaceable</sgmltag>"
+
+#: en_US/style.xml:1941(para)
+d5138 3
+a5140 3
+"If your documentation formally states a specific value will be used as a "
+"convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> "
+"tag in your text or examples."
+d5142 3
+a5144 3
+"Se a sua documentação relatar formalmente que um determinado valor será "
+"usado como convenção, não use a marca <sgmltag class=\"starttag"
+"\">replaceable</sgmltag> no seu texto ou exemplos."
+d5146 3
+a5148 3
+#: en_US/style.xml:1950(title)
+msgid "XML Entities"
+msgstr "Entidades de XML"
+d5150 1
+a5150 1
+#: en_US/style.xml:1951(para)
+d5152 4
+a5155 6
+"Use the entities provided by the Fedora Documentation Project. These "
+"entities are found in the <filename>common/</filename> folder in the "
+"<filename>fedora-docs</filename> distribution. (Refer also to <xref linkend="
+"\"ch-getting-files\"/>.) For instance, do not use abbreviations such as "
+"\"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" "
+"which produces the text \"Fedora 7.\""
+d5157 4
+a5160 6
+"Use as entidades oferecidas pelo Projecto de Documentação do Fedora. Estas "
+"entidades aparecem na pasta <filename>common/</filename> da distribuição "
+"<filename>fedora-docs</filename>. (Consulte também a secção <xref linkend="
+"\"ch-getting-files\"/>.) Por exemplo, não use abreviaturas do tipo \"FC2.\" "
+"Em vez disso, use as entidades predefinidas \"&FC; &FCVER;,\" que "
+"irá gerar o texto \"Fedora 7.\""
+d5162 3
+a5164 3
+#: en_US/writing-guidelines.xml:11(title)
+msgid "Fedora Documentation Guidelines"
+msgstr "Recomendações de Documentação do Fedora"
+d5166 3
+a5168 4
+#: en_US/writing-guidelines.xml:14(primary)
+#: en_US/writing-guidelines.xml:15(see)
+msgid "recursion"
+msgstr "recorrência"
+d5170 1
+a5170 15
+#: en_US/writing-guidelines.xml:19(primary)
+#: en_US/writing-guidelines.xml:26(secondary)
+msgid "RTFM"
+msgstr "RTFM"
+
+#: en_US/writing-guidelines.xml:20(secondary)
+msgid "read the fine manual"
+msgstr "leia o belo manual"
+
+#: en_US/writing-guidelines.xml:21(seealso)
+#: en_US/writing-guidelines.xml:25(primary)
+msgid "humor"
+msgstr "humor"
+
+#: en_US/writing-guidelines.xml:29(para)
+d5172 4
+a5175 2
+"Please read this chapter carefully. This chapter describes the guidelines "
+"that must be followed such as naming conventions."
+d5177 5
+a5181 2
+"Por favor, leia este capítulo com cuidado. O mesmo descreve as recomendações "
+"que deverão ser seguidas, como as nomenclaturas."
+d5183 3
+a5185 7
+#: en_US/writing-guidelines.xml:38(title)
+msgid "File Header"
+msgstr "Cabeçalho do Ficheiro"
+
+#: en_US/writing-guidelines.xml:40(title)
+msgid "XML Header"
+msgstr "Cabeçalho de XML"
+d5187 1
+a5187 1
+#: en_US/writing-guidelines.xml:41(para)
+d5189 3
+a5191 3
+"In accordance with good XML practices, the first line in any DocBook XML "
+"source files should identify the file as XML. Use the following line as the "
+"first line of any new XML file:"
+d5193 3
+a5195 3
+"De acordo com as boas práticas de XML, a primeira linha de qualquer ficheiro "
+"de DocBook em XML deverá identificar o ficheiro como XML. Use a seguinte "
+"linha como primeira linha de qualquer ficheiro em XML novo:"
+d5197 3
+a5199 3
+#: en_US/writing-guidelines.xml:47(title)
+msgid "CVS Id Header"
+msgstr "Cabeçalho do ID do CVS"
+d5201 1
+a5201 1
+#: en_US/writing-guidelines.xml:48(para)
+d5203 4
+a5206 2
+"All the files must contain the CVS Id header. Use the following line as the "
+"second line of any new XML file:"
+d5208 8
+a5215 2
+"Todos os ficheiros deverão conter o cabeçalho Id do CVS. Use a seguinte "
+"linha como segunda linha para qualquer ficheiro em XML novo:"
+d5217 1
+a5217 1
+#: en_US/writing-guidelines.xml:51(para)
+d5219 5
+a5223 2
+"Any time the file is committed to CVS, the line is updated automatically to "
+"include information about the file. For example:"
+d5225 5
+a5229 2
+"Sempre que este ficheiro for enviado para o CVS, a linha é actualizada "
+"automaticamente para incluir informações acerca do ficheiro. Por exemplo:"
+d5231 3
+a5233 3
+#: en_US/writing-guidelines.xml:58(title)
+msgid "ID Naming Conventions"
+msgstr "Convenções dos Nomes dos Identificadores"
+d5235 1
+a5235 7
+#: en_US/writing-guidelines.xml:62(secondary)
+#: en_US/writing-guidelines.xml:66(primary)
+#: en_US/writing-guidelines.xml:79(primary)
+msgid "naming conventions"
+msgstr "nomenclaturas"
+
+#: en_US/writing-guidelines.xml:69(para)
+d5237 5
+a5241 3
+"This section explains the ID naming convention. IDs are unique identifiers "
+"that allow DocBook XML to cross-reference a section, chapter, or other "
+"element."
+d5243 4
+a5246 3
+"Esta secção explica a nomenclaturas de IDs. Os IDs são identificadores "
+"únicos que permitem ao DocBook em XML fazer referências a uma dada secção, "
+"capítulo ou outro elemento."
+d5248 3
+a5250 4
+#: en_US/writing-guidelines.xml:75(secondary)
+#: en_US/writing-guidelines.xml:80(secondary)
+msgid "rules for defining an ID"
+msgstr "regras de definição de um ID"
+d5252 7
+a5258 3
+#: en_US/writing-guidelines.xml:83(para)
+msgid "The following general rules apply to IDs:"
+msgstr "As seguintes regras gerais aplicam-se aos IDs:"
+d5260 3
+a5262 3
+#: en_US/writing-guidelines.xml:87(para)
+msgid "Keep an ID as short and simple as possible."
+msgstr "Mantenha um ID o mais curto e simples possível."
+d5264 1
+a5264 1
+#: en_US/writing-guidelines.xml:90(para)
+d5266 3
+a5268 3
+"Start the ID with the special short two-character label. This makes URLs and "
+"other references to this ID human readable, by self-identifying the XML "
+"container type."
+d5270 3
+a5272 3
+"Inicie o ID pela legenda especial de dois caracteres. Esta faz com que os "
+"URLs e as outras referências a este ID sejam legíveis, identificando "
+"autoamticamente o tipo do contentor de XML."
+d5274 1
+a5274 1
+#: en_US/writing-guidelines.xml:96(para)
+d5276 2
+a5277 2
+"<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used "
+"properly."
+d5279 3
+a5281 2
+"O <xref linkend=\"ex-id-usage\"/> demonstra alguns atributos de IDs usados "
+"correctamente como exemplos."
+d5283 9
+a5291 3
+#: en_US/writing-guidelines.xml:102(title)
+msgid "Proper ID Usage"
+msgstr "Utilização Adequada de IDs"
+d5293 3
+a5295 3
+#: en_US/writing-guidelines.xml:111(title)
+msgid "Two-Character Naming Conventions"
+msgstr "Nomenclaturas de Dois Caracteres"
+d5297 3
+a5299 3
+#: en_US/writing-guidelines.xml:112(segtitle)
+msgid "Tag"
+msgstr "Marca"
+d5301 3
+a5303 3
+#: en_US/writing-guidelines.xml:113(segtitle)
+msgid "Prefix"
+msgstr "Prefixo"
+d5305 3
+a5307 3
+#: en_US/writing-guidelines.xml:115(sgmltag)
+msgid "preface"
+msgstr "prefácio"
+d5309 13
+a5321 3
+#: en_US/writing-guidelines.xml:116(literal)
+msgid "pr-"
+msgstr "pr-"
+d5323 3
+a5325 3
+#: en_US/writing-guidelines.xml:120(literal)
+msgid "ch-"
+msgstr "ch-"
+d5327 14
+a5340 3
+#: en_US/writing-guidelines.xml:123(sgmltag)
+msgid "section"
+msgstr "secção"
+d5342 3
+a5344 3
+#: en_US/writing-guidelines.xml:124(literal)
+msgid "sn-"
+msgstr "sn-"
+d5346 3
+a5348 3
+#: en_US/writing-guidelines.xml:128(literal)
+msgid "fig-"
+msgstr "fig-"
+d5350 3
+a5352 3
+#: en_US/writing-guidelines.xml:132(literal)
+msgid "tb-"
+msgstr "tb-"
+d5354 1
+a5354 17
+#: en_US/writing-guidelines.xml:135(sgmltag)
+msgid "appendix"
+msgstr "apêndice"
+
+#: en_US/writing-guidelines.xml:136(literal)
+msgid "ap-"
+msgstr "ap-"
+
+#: en_US/writing-guidelines.xml:140(literal)
+msgid "pt-"
+msgstr "pt-"
+
+#: en_US/writing-guidelines.xml:144(literal)
+msgid "ex-"
+msgstr "ex-"
+
+#: en_US/writing-guidelines.xml:148(para)
+d5356 6
+a5361 2
+"Use the title of the item as the ID. Make your titles unique within a "
+"document to prevent conflicts. For example:"
+d5363 6
+a5368 2
+"Use o título do item como ID. Torne os seus títulos únicos dentro de um "
+"documento para evitar conflitos. Por exemplo:"
+d5370 1
+a5370 5
+#: en_US/writing-guidelines.xml:157(title)
+msgid "XML Tags"
+msgstr "Marcas XML"
+
+#: en_US/writing-guidelines.xml:163(para)
+d5372 2
+a5373 2
+"It is very important that you remember the caveats in this section. These "
+"are learned suggestions or rules that make your XML experience better."
+d5375 2
+a5376 3
+"É muito importante que recorde as contrapartidas desta secção. Estas são "
+"sugestões ou regras de aprendizagem que tornam melhor a sua experiência em "
+"XML."
+d5378 1
+a5378 1
+#: en_US/writing-guidelines.xml:173(para)
+d5380 3
+a5382 5
+"Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+"\"genentity\">reg</sgmltag> because the do not produce HTML output that "
+"works for all charsets. The HTML output produces by these entities are "
+"declared in the DTD and cannot be changed via the stylesheet."
+d5384 4
+a5387 6
+"Não use as entidades de marcas registadas <sgmltag class=\"genentity"
+"\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag> ou <sgmltag "
+"class=\"genentity\">reg</sgmltag>, porque não produzem HTML válido que "
+"funcione em todas as codificações de caracteres. O resultado em HTML "
+"produzido por estas entidades está descrito na DTD e não pode ser alterado "
+"com a folha de estilo."
+d5389 1
+a5389 1
+#: en_US/writing-guidelines.xml:181(para)
+d5391 4
+a5394 2
+"Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes "
+"as follows:"
+d5396 4
+a5399 2
+"Em vez disso, use a marca <sgmltag>trademark</sgmltag> e as suas classes "
+"associadas, como se segue:"
+d5401 1
+a5401 21
+#: en_US/writing-guidelines.xml:184(segtitle)
+msgid "DocBook XML source"
+msgstr "Código XML do DocBook"
+
+#: en_US/writing-guidelines.xml:185(segtitle)
+msgid "Rendered content"
+msgstr "Conteúdo representado"
+
+#: en_US/writing-guidelines.xml:189(trademark)
+msgid "trademark symbol after me"
+msgstr "símbolo de marca comercial a seguir a mim"
+
+#: en_US/writing-guidelines.xml:196(trademark)
+msgid "registered trademark symbol after me"
+msgstr "símbolo de marca registada a seguir a mim"
+
+#: en_US/writing-guidelines.xml:202(trademark)
+msgid "copyright symbol after me"
+msgstr "símbolo de direitos de cópia a seguir a mim"
+
+#: en_US/writing-guidelines.xml:211(para)
+d5403 3
+a5405 3
+"In general, use <sgmltag>para</sgmltag> tags around anything other than a "
+"simple paragraph. Doing so will create additional white space within the "
+"text itself in the PDF version."
+d5407 3
+a5409 3
+"De um modo geral, não use as marcas <sgmltag>para</sgmltag> em torno de tudo "
+"o que não seja um parágrafo simples. Ao fazê-lo, irá criar espaços em branco "
+"adicionais dentro do próprio texto, na versão em PDF."
+d5411 1
+a5411 1
+#: en_US/writing-guidelines.xml:216(para)
+d5413 5
+a5417 3
+"Specifically, do not use <sgmltag>para</sgmltag> tags around the following "
+"(or, to put this another way, do not embed the following within <sgmltag "
+"class=\"element\">para</sgmltag> elements):"
+d5419 5
+a5423 3
+"Especificamente, não use as marcas <sgmltag>para</sgmltag> em torno do "
+"seguinte (ou, posto de outra forma, não incorpore o seguinte dentro das "
+"marcas <sgmltag class=\"element\">para</sgmltag>):"
+d5425 1
+a5425 1
+#: en_US/writing-guidelines.xml:241(term)
+d5427 4
+a5430 2
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag>listitem</sgmltag> tags"
+d5432 4
+a5435 2
+"Conteúdo dentro de elementos <sgmltag class=\"element\">para</sgmltag> "
+"residentes em marcas <sgmltag>listitem</sgmltag>"
+d5437 1
+a5437 1
+#: en_US/writing-guidelines.xml:244(para)
+d5439 2
+a5440 4
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</"
+"emphasis> start immediately after the beginning <sgmltag class=\"starttag"
+"\">para</sgmltag> tag to avoid extra white space in the PDF version."
+d5442 2
+a5443 5
+"O conteúdo dentro das marcas <sgmltag class=\"element\">para</sgmltag> "
+"inseridas em marcas <sgmltag class=\"element\">listitem</sgmltag> "
+"<emphasis>deverá</emphasis> começar logo a seguir à marca inicial <sgmltag "
+"class=\"starttag\">para</sgmltag>, para evitar espaços em branco extra na "
+"versão em PDF."
+d5445 3
+a5447 8
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:301(secondary)
+#: en_US/writing-guidelines.xml:307(secondary)
+#: en_US/writing-guidelines.xml:313(secondary)
+#: en_US/writing-guidelines.xml:319(secondary)
+#: en_US/writing-guidelines.xml:325(secondary)
+msgid "admonitions"
+msgstr "advertências"
+d5449 3
+a5451 5
+#: en_US/writing-guidelines.xml:276(secondary)
+#: en_US/writing-guidelines.xml:302(tertiary)
+#: en_US/writing-guidelines.xml:371(secondary)
+msgid "warning"
+msgstr "warning"
+d5453 3
+a5455 5
+#: en_US/writing-guidelines.xml:281(secondary)
+#: en_US/writing-guidelines.xml:308(tertiary)
+#: en_US/writing-guidelines.xml:356(secondary)
+msgid "tip"
+msgstr "tip"
+d5457 9
+a5465 5
+#: en_US/writing-guidelines.xml:286(secondary)
+#: en_US/writing-guidelines.xml:314(tertiary)
+#: en_US/writing-guidelines.xml:351(secondary)
+msgid "note"
+msgstr "note"
+d5467 3
+a5469 5
+#: en_US/writing-guidelines.xml:291(secondary)
+#: en_US/writing-guidelines.xml:320(tertiary)
+#: en_US/writing-guidelines.xml:361(secondary)
+msgid "caution"
+msgstr "caution"
+d5471 1
+a5471 7
+#: en_US/writing-guidelines.xml:296(secondary)
+#: en_US/writing-guidelines.xml:326(tertiary)
+#: en_US/writing-guidelines.xml:366(secondary)
+msgid "important"
+msgstr "important"
+
+#: en_US/writing-guidelines.xml:329(para)
+d5473 3
+a5475 9
+"There are five types of admonitions in DocBook: <sgmltag class=\"element"
+"\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, "
+"<sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</"
+"sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the "
+"admonitions have the same structure: an optional <sgmltag class=\"element"
+"\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD "
+"does not impose any specific semantics on the individual admonitions. For "
+"example, DocBook does not mandate that a <sgmltag class=\"element\">warning</"
+"sgmltag> is reserved for cases where bodily harm can result."
+d5477 7
+a5483 10
+"Existem cinco tipos de advertências no DocBook: <sgmltag class=\"element"
+"\">caution</sgmltag> (cuidado), <sgmltag class=\"element\">important</"
+"sgmltag> (importante), <sgmltag class=\"element\">note</sgmltag> (nota), "
+"<sgmltag class=\"element\">tip</sgmltag> (sugestão) e <sgmltag class="
+"\"element\">warning</sgmltag> (aviso). Todas as advertências têm a mesma "
+"estrutura: um <sgmltag class=\"element\">title</sgmltag> opcional, seguido "
+"dos elementos do nível dos parágrafos. A DTD do DocBook não impõe qualquer "
+"semântica específica das advertências individuais. Por exemplo, o DocBook "
+"não obriga que um <sgmltag class=\"element\">warning</sgmltag> esteja "
+"reservado para os casos em que possam resultar danos corporais."
+d5485 1
+a5485 1
+#: en_US/writing-guidelines.xml:343(title)
+d5487 3
+a5489 4
+"Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class="
+"\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, "
+"<sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element"
+"\">warning</sgmltag>"
+d5491 4
+a5494 4
+"Criar um <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element"
+"\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, <sgmltag "
+"class=\"element\">important</sgmltag> ou <sgmltag class=\"element\">warning</"
+"sgmltag>"
+d5496 1
+a5496 1
+#: en_US/writing-guidelines.xml:374(para)
+d5498 3
+a5500 15
+"There are several ways to bring attention to text within a document. A "
+"<emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to "
+"bring additional information to the users' attention. A <emphasis><sgmltag "
+"class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful "
+"information or another way to do something. A <emphasis><sgmltag class="
+"\"element\">caution</sgmltag></emphasis> is used to show the user they must "
+"be careful when attempting a certain step. An <emphasis><sgmltag class="
+"\"element\">important</sgmltag></emphasis> tag set can be used to show the "
+"user a piece of information that should not be overlooked. While this "
+"information may not change anything the user is doing, it should show the "
+"user that this piece of information could be vital. A <emphasis><sgmltag "
+"class=\"element\">warning</sgmltag></emphasis> is used to show the reader "
+"that their current setup will change or be altered, such as files being "
+"removed, and they should not choose this operation unless they are alright "
+"with the consequences."
+d5502 7
+a5508 16
+"Existem diversas formas de chamar a atenção ao texto dentro de um documento. "
+"Uma <emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> (nota) é "
+"usada para trazer informações para a atenção dos utilizadores. Uma "
+"<emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> (sugestão) é "
+"usada para mostrar ao utilizador alguma informação útil ou outra forma de "
+"fazer algo. Uma <emphasis><sgmltag class=\"element\">caution</sgmltag></"
+"emphasis> é usada para mostrar ao utilizador que deverá ter cuidado ao "
+"efectuar um determinado passo. Uma marca <emphasis><sgmltag class=\"element"
+"\">important</sgmltag></emphasis> pode ser usada para mostrar ao utilizador "
+"um pedaço de informação que não deva ser ignorado. Embora esta informação "
+"possa não alterar o que o utilizador irá fazer, deverá mostrar ao utilizador "
+"que esta informação poderá ser vital. Um <emphasis><sgmltag class=\"element"
+"\">warning</sgmltag></emphasis> é usado para mostrar ao leitor que a sua "
+"configuração actual irá mudar ou ser alterada, como a remoção de ficheiros, "
+"pelo que não deverão escolher esta operação, a menos que estejam de acordo "
+"com as consequências."
+d5510 1
+a5510 1
+#: en_US/writing-guidelines.xml:394(para)
+d5512 2
+a5513 2
+"The following lines of code show the basic setup for each case mentioned "
+"above, along with its appearance in HTML."
+d5515 10
+a5524 2
+"As seguintes linhas de código mostram a configuração básica de cada um dos "
+"casos indicados acima, em conjunto com a sua aparência em HTML."
+d5526 3
+a5528 6
+#: en_US/writing-guidelines.xml:404(para)
+#: en_US/writing-guidelines.xml:424(para)
+#: en_US/writing-guidelines.xml:434(para)
+#: en_US/writing-guidelines.xml:444(para)
+msgid "Body of text goes here."
+msgstr "O conteúdo do texto aparece aqui."
+d5530 7
+a5536 3
+#: en_US/writing-guidelines.xml:413(title) en_US/emacs-nxml.xml:114(title)
+msgid "Tip"
+msgstr "Sugestão"
+d5538 3
+a5540 3
+#: en_US/writing-guidelines.xml:414(para)
+msgid "Body of text goes here"
+msgstr "O conteúdo do texto aparece aqui"
+d5542 7
+a5548 3
+#: en_US/writing-guidelines.xml:423(title)
+msgid "Caution"
+msgstr "Atenção"
+d5550 8
+a5557 3
+#: en_US/writing-guidelines.xml:451(title)
+msgid "Screenshots"
+msgstr "Imagens"
+d5559 5
+a5563 4
+#: en_US/writing-guidelines.xml:454(primary)
+#: en_US/writing-guidelines.xml:459(see) en_US/writing-guidelines.xml:463(see)
+msgid "screenshots"
+msgstr "imagens"
+d5565 8
+a5572 3
+#: en_US/writing-guidelines.xml:455(secondary)
+msgid "how to take"
+msgstr "como fazer"
+d5574 16
+a5589 3
+#: en_US/writing-guidelines.xml:458(primary)
+msgid "screen captures"
+msgstr "capturas do ecrã"
+d5591 11
+a5601 3
+#: en_US/writing-guidelines.xml:462(primary)
+msgid "screen grabs"
+msgstr "gravações do ecrã"
+d5603 2
+a5604 1
+#: en_US/writing-guidelines.xml:466(para)
+d5606 3
+a5608 7
+"Screenshots are illustrations that show the state of a display the user may "
+"encounter. Screenshots can be either graphical or textual. However, "
+"screenshots use a great deal of space in a text document to convey "
+"relatively small amounts of information. The same space in the document can "
+"hold a greater amount of more descriptive and helpful information. "
+"Therefore, authors should avoid screenshots whenever possible in favor of "
+"descriptive text."
+d5610 3
+a5612 7
+"As imagens ou capturas de ecrã são ilustrações que apresentam o estado do "
+"ecrã que o utilizador poderá encontrar. As imagens poderão ser gráficas ou "
+"textuais. Contudo, as imagens usam bastante espaço num documento de texto "
+"para representar pedaços de informação relativamente pequenos. o mesmo "
+"espaço num documento poderá conter uma quantidade maior de informação mais "
+"descritiva e útil. Como tal, os autores deverão evitar as imagens sempre que "
+"possível, em detrimento de texto mais descritivo."
+d5614 1
+a5614 1
+#: en_US/writing-guidelines.xml:474(para)
+d5616 4
+a5619 7
+"One of the isolated instances in which screenshots are useful is to "
+"demonstrate a physical screen layout that is unfamiliar to a reader. "
+"<emphasis>This does not mean that illustrations of dialog boxes are good "
+"uses of screenshots.</emphasis> On the contrary, dialogs are simply "
+"instances of a user interface element with which a reader is already "
+"familiar. An annotated diagram in certain cases, however, explains to the "
+"reader where to find functional landmarks on the screen such as menu bars."
+d5621 9
+a5629 8
+"Uma das instâncias isoladas em que as imagens são úteis é para demonstrar a "
+"disposição física de um ecrã que não seja familiar para um leitor. "
+"<emphasis>Isto não significa que as ilustrações de janelas sejam bons usos "
+"para as imagens.</emphasis> Pelo contrário, as janelas são simplesmente "
+"instâncias de um elemento da interface com o qual o leitor já está "
+"familiarizado. Um diagrama anotado em certos casos, todavia, explica ao "
+"leitor onde encontrar certos blocos funcionais no ecrã, como as barras de "
+"menu."
+d5631 1
+a5631 1
+#: en_US/writing-guidelines.xml:482(para)
+d5633 3
+a5635 2
+"The steps for taking a graphical screenshot illustrate how using text to "
+"describe a procedure is more concise than a series of screenshots."
+d5637 3
+a5639 2
+"Os passos para tirar uma imagem gráfica ilustram como a utilização de texto "
+"para descrever um dado procedimento é mais conciso que uma série de imagens."
+d5641 7
+a5647 3
+#: en_US/writing-guidelines.xml:487(term)
+msgid "Graphical Screenshot"
+msgstr "Imagem Gráfica"
+d5649 1
+a5649 1
+#: en_US/writing-guidelines.xml:491(para)
+d5651 3
+a5653 4
+"Create a new user account to make screenshots. The new account uses the "
+"distribution default theme, fonts, and element sizes. The resulting "
+"screenshot has an appearance familiar to the largest number of readers, and "
+"makes Fedora Documentation Project documents consistent."
+d5655 3
+a5657 5
+"Crie uma nova conta de utilizador para criar as imagens. A conta nova usa o "
+"tema, tipos de letra e tamanhos dos elementos predefinidos da instalação. A "
+"imagem resultante tem uma aparência familiar ao maior número de leitores, e "
+"faz com que os documentos do Projecto de Documentação do Fedora sejam "
+"consistentes."
+d5659 1
+a5659 1
+#: en_US/writing-guidelines.xml:498(para)
+d5661 3
+a5663 4
+"Before taking the screenshot, if possible, resize the targeted GUI element"
+"(s) to the smallest possible size. The target image should be 500 pixels "
+"wide or less. If the screenshot includes more than one GUI element, you may "
+"need to resize the screenshot in a following step."
+d5665 19
+a5683 4
+"Antes de tirar a fotografia, tente dimensionar os elementos gráficos com o "
+"tamanho mais pequeno possível. O seu objectivo é uma imagem com 500 pixels "
+"ou menos ainda. Se estiver a tirar uma fotografia com mais de um elemento "
+"gráfico, terá de dimensionar a imagem num passo seguinte."
+d5685 1
+a5685 1
+#: en_US/writing-guidelines.xml:506(para)
+d5687 3
+a5689 7
+"To take the screenshot, select the GUI element with the mouse to bring it to "
+"the forefront, or otherwise arrange the elements. Press "
+"<keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to "
+"capture a single GUI window. For capturing the entire desktop use "
+"<keycap>Print Screen</keycap>. If the shot includes multiple elements "
+"grouped closely together, crop the resulting PNG format image in "
+"<application>The GIMP</application>."
+d5691 4
+a5694 8
+"Para tirar a imagem, seleccione o elemento gráfico com o seu rato, passando-"
+"o para primeiro plano, ou organizando os elementos. Carregue em "
+"<keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> para "
+"capturar uma única janela. Para capturar o ecrã completo, use o "
+"<keycap>Print Screen</keycap>. Se estiver a tirar uma fotografia de vários "
+"elementos e os tiver agrupado em conjunto, poderá recortar a imagem "
+"resultante no <application>The GIMP</application>. A imagem estará no "
+"formato PNG."
+d5696 1
+a5696 1
+#: en_US/writing-guidelines.xml:518(para)
+d5698 9
+a5706 9
+"If necessary, resize the image using <application>The GIMP</application>. "
+"Open the image, then right-click on it and choose "
+"<menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</"
+"guimenuitem></menuchoice>. With the chain symbol intact, set the "
+"<guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click "
+"<guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</"
+"guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the "
+"image before converting it."
+msgstr "Se precisar, poderá dimensionar a imagem com o <application>The GIMP</application>. Com a imagem aberta, carregue com o botão direito nesta e escolha a opção <menuchoice><guimenu>Imagem</guimenu><guimenuitem>Escalar a Imagem...</guimenuitem></menuchoice>. Com o símbolo da corrente intacto, configure a <guilabel>Nova Largura</guilabel> com o valor <guilabel>500 px</guilabel> e carregue em <guibutton>OK</guibutton>. Certifique-se que carrega em <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo> para gravar as suas alterações no seu PNG, antes da conversão para EPS."
+d5708 3
+a5710 9
+#: en_US/writing-guidelines.xml:534(para)
+msgid ""
+"With the image open in <application>The GIMP</application>, right-click the "
+"image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As..."
+"</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, "
+"select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</"
+"guibutton>. Allow flattening of the image by clicking <guibutton>Export</"
+"guibutton>."
+msgstr "Com a imagem aberta no <application>The GIMP</application>, carregue com o botão direito na imagem e seleccione a opção <menuchoice><guimenu>Ficheiro</guimenu><guimenuitem>Gravar Como...</guimenuitem></menuchoice. Em <guimenu>Determinar o Tipo de Ficheiro:</guimenu>, seleccione <guimenuitem>PostScript</guimenuitem>, carregando depois em <guibutton>OK</guibutton>. Active o alisamento da imagem com a opção <guibutton>Exportar</guibutton>."
+d5712 1
+a5712 1
+#: en_US/writing-guidelines.xml:545(para)
+d5714 3
+a5716 3
+"A <guilabel>Save as PostScript</guilabel> window appears. Select "
+"<guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</"
+"guibutton>."
+d5718 12
+a5729 3
+"Na janela para <guilabel>Gravar como PostScript</guilabel>, seleccione "
+"<guilabel>PostScript Encapsulado</guilabel> e carregue em <guibutton>OK</"
+"guibutton>."
+d5731 3
+a5733 3
+#: en_US/writing-guidelines.xml:559(term)
+msgid "Text Screenshot"
+msgstr "Imagem de Texto"
+d5735 1
+a5735 1
+#: en_US/writing-guidelines.xml:561(para)
+d5737 3
+a5739 2
+"Textual screen information is also useful for readers. Follow these "
+"guidelines for textual screenshots:"
+d5741 3
+a5743 2
+"A informação textual do ecrã também é útil para os leitores. Siga estas "
+"recomendações para as imagens textuais:"
+d5745 1
+a5745 1
+#: en_US/writing-guidelines.xml:565(para)
+d5747 2
+a5748 3
+"If a graphical screenshot illustrates a function, and the textual mode has "
+"identical functions, do not include both, unless omitting either would make "
+"your description unclear."
+d5750 3
+a5752 3
+"Se usar uma imagem gráfica para ilustrar uma função e o modo textual tiver "
+"funções idênticas, não inclua ambas, a menos que a omissão de uma delas "
+"torne a sua descrição menos clara."
+d5754 1
+a5754 1
+#: en_US/writing-guidelines.xml:571(para)
+d5756 3
+a5758 3
+"Make the information generic over specific, and omit any username and "
+"machine information if possible. Do not include the shell prompt unless it "
+"is vital to the demonstration."
+d5760 3
+a5762 3
+"Opte por ter a sua informação genérica em vez de específica, omitindo a "
+"informação do utilizador e da máquina, se possível. Não inclua a linha de "
+"comandos, a menos que seja vital para a demonstração."
+d5764 1
+a5764 5
+#: en_US/writing-guidelines.xml:577(para)
+msgid "Separate what the user types from sample command output."
+msgstr "Separe o que o utilizador escreve do resultado do comando."
+
+#: en_US/writing-guidelines.xml:581(para)
+d5766 2
+a5767 4
+"When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a "
+"procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show "
+"what the user types, and use <sgmltag class=\"element\">computeroutput</"
+"sgmltag> tags to show the resulting output."
+d5769 2
+a5770 4
+"Ao usar o <sgmltag class=\"element\">screen</sgmltag> para demonstrar um "
+"procedimento, use as marcas <sgmltag class=\"element\">userinput</sgmltag> "
+"para mostrar o que o utilizador escreve, usando as marcas <sgmltag class="
+"\"element\">computeroutput</sgmltag> para mostrar o resultado."
+d5772 1
+a5772 1
+#: en_US/writing-guidelines.xml:589(para)
+d5774 3
+a5776 2
+"<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual "
+"screenshot usage."
+d5778 3
+a5780 2
+"O <xref linkend=\"ex-text-screenshot-good\"/> é um exemplo de utilização de "
+"uma imagem textual."
+d5782 1
+a5782 5
+#: en_US/writing-guidelines.xml:594(title)
+msgid "Correct Textual Screenshot (XML Source and HTML)"
+msgstr "Corrigir a Imagem Textual (Código em XML e HTML)"
+
+#: en_US/writing-guidelines.xml:607(para)
+d5784 3
+a5786 1
+"To find all the currently active ssh sessions, execute the following command:"
+d5788 3
+a5790 1
+"Para descobrir todas as sessões de SSH activas, execute o seguinte comando:"
+d5792 1
+a5792 11
+#: en_US/writing-guidelines.xml:609(userinput)
+#, no-wrap
+msgid "ps ax | grep ssh"
+msgstr "ps ax | grep ssh"
+
+#: en_US/writing-guidelines.xml:611(para)
+msgid "Output appears similar to the following:"
+msgstr "O resultado aparece semelhante ao seguinte:"
+
+#: en_US/writing-guidelines.xml:613(computeroutput)
+#, no-wrap
+d5794 2
+a5795 4
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh user@@host.example.com\n"
+" 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+d5797 3
+a5799 4
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh utilizador@@maquina.exemplo.com\n"
+" 8032 pts/1 S 0:00 ssh root@@salvaguarda.exemplo.com"
+d5801 4
+a5804 3
+#: en_US/module-struct.xml:12(title)
+msgid "How Modules Work"
+msgstr "Como Funcionam os Módulos"
+d5806 2
+a5807 14
+#: en_US/module-struct.xml:13(para)
+msgid ""
+"Documentation modules have a specific structure that enables the "
+"preconfigured tools to work correctly. Follow this structure exactly or you "
+"may have problems building your module. The Fedora Documentation Project "
+"build tools locate resources in the module and use them to build new output "
+"such as HTML or RPM packages."
+msgstr ""
+"Os módulos de documentação têm uma estrutura específica que activa as "
+"ferramentas pré-configuradas para funcionarem correctamente. Siga esta "
+"estrutura exacta ou então poderá vir a ter problemas com a compilação do seu "
+"módulo. As ferramentas de compilação do Projecto de Documentação do Fedora "
+"localizam os recursos no módulo e usam-nos para criar novos formatos de "
+"saída, como HTML ou pacotes RPM."
+d5809 2
+a5810 3
+#: en_US/module-struct.xml:19(title)
+msgid "Structure of a Module"
+msgstr "Estrutura de um Módulo"
+d5812 2
+a5813 6
+#: en_US/module-struct.xml:20(para)
+msgid ""
+"<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example "
+"module, excluding any <filename class=\"directory\">CVS</filename> folders. "
+"Note that this example document does not have branches."
+msgstr "A secção <xref linkend=\"ex-module-structure\"/> mostra uma árvore de pastas de um módulo de exemplo, excluindo as pastas <filename class=\"directory\">CVS</filename>. Repare que este documento de exemplo não tem ramificações."
+d5815 8
+a5822 3
+#: en_US/module-struct.xml:25(title)
+msgid "Example Module Structure"
+msgstr "Estrutura do Módulo de Exemplo"
+d5824 13
+a5836 3
+#: en_US/module-struct.xml:46(title)
+msgid "CVS Module Contents"
+msgstr "Conteúdo do Módulo de CVS"
+d5838 2
+a5839 3
+#: en_US/module-struct.xml:47(segtitle)
+msgid "Component"
+msgstr "Componente"
+d5841 13
+a5853 3
+#: en_US/module-struct.xml:48(segtitle)
+msgid "Type"
+msgstr "Tipo"
+d5855 6
+a5860 3
+#: en_US/module-struct.xml:49(segtitle)
+msgid "Usage Notes"
+msgstr "Notas de Utilização"
+d5862 2
+a5863 3
+#: en_US/module-struct.xml:51(seg)
+msgid "Primary language directory"
+msgstr "Pasta da língua primária"
+d5865 8
+a5872 4
+#: en_US/module-struct.xml:52(seg) en_US/module-struct.xml:89(seg)
+#: en_US/module-struct.xml:96(seg)
+msgid "required"
+msgstr "obrigatória"
+d5874 13
+a5886 4
+#: en_US/module-struct.xml:55(filename)
+#: en_US/module-struct.xml:177(systemitem)
+msgid "en_US"
+msgstr "pt"
+d5888 6
+a5893 3
+#: en_US/module-struct.xml:59(firstterm)
+msgid "entities"
+msgstr "entidades"
+d5895 6
+a5900 11
+#: en_US/module-struct.xml:60(para)
+msgid ""
+"Think of an XML entity as a predefined snippet of information. It can "
+"represent a chunk of XML source, or simply a word or character. If the "
+"information changes, it need be replaced only once, in the definition, to "
+"fix all usage."
+msgstr ""
+"Pense numa entidade de XML como um pedaço predefinido de informação. Poderá "
+"representar um bloco de código em XML, ou simplesmente uma palavra ou "
+"carácter. Se a informação se alterar, terá de ser substituída apenas uma vez "
+"na definição, de modo a corrigir todas as alterações."
+d5902 8
+a5909 15
+#: en_US/module-struct.xml:53(seg)
+msgid ""
+"This is the only directory absolutely required. It is named for the original "
+"language of the document, such as <placeholder-1/> (US English). The primary "
+"language does not have to be US English; all languages are supported. This "
+"directory contains all the XML source for the actual document, as well as "
+"XML source for document-specific <placeholder-2/><footnote><placeholder-3/></"
+"footnote>."
+msgstr ""
+"Esta é a única pasta que é absolutamente necessária. Esta tem o nome da "
+"língua original do documento, como por exemplo <placeholder-1/> (Inglês dos "
+"EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas "
+"todas as línguas. Esta pasta contém todo o código em XML do documento "
+"actual, assim como o código em XML específico do documento para <placeholder-"
+"2/><footnote><placeholder-3/></footnote>."
+d5911 8
+a5918 3
+#: en_US/module-struct.xml:68(seg)
+msgid "Graphics directory"
+msgstr "Pasta de imagens"
+d5920 8
+a5927 3
+#: en_US/module-struct.xml:69(seg) en_US/module-struct.xml:79(seg)
+msgid "optional"
+msgstr "opcional"
+d5929 8
+a5936 3
+#: en_US/module-struct.xml:70(filename) en_US/module-struct.xml:74(filename)
+msgid "figs/"
+msgstr "figs/"
+d5938 6
+a5943 11
+#: en_US/module-struct.xml:70(seg)
+msgid ""
+"The <placeholder-1/> directory is an optional directory where graphics for "
+"the document should be stored. If graphics are screenshots that are "
+"particular to a language, the <placeholder-2/> directory can and should be "
+"stored in a language directory."
+msgstr ""
+"A pasta <placeholder-1/> é uma pasta opcional onde serão gravadas as imagens "
+"do documento. Se estas forem imagens particulares para uma determinada "
+"língua, a pasta <placeholder-2/> pode e deve ser gravada numa pasta de "
+"línguas."
+d5945 10
+a5954 3
+#: en_US/module-struct.xml:78(seg)
+msgid "Translation (PO) directory"
+msgstr "Pasta de traduções (PO)"
+d5956 2
+a5957 3
+#: en_US/module-struct.xml:80(filename) en_US/module-struct.xml:184(filename)
+msgid "po/"
+msgstr "po/"
+d5959 6
+a5964 3
+#: en_US/module-struct.xml:82(acronym)
+msgid "PO"
+msgstr "PO"
+d5966 8
+a5973 8
+#: en_US/module-struct.xml:80(seg)
+msgid ""
+"The <placeholder-1/> directory contains specially formatted Portable Object, "
+"or <placeholder-2/>, files created and used by translators. The Fedora "
+"Documentation Project build tools use these files to create translated "
+"versions of documents. The translated documents are not stored in CVS; they "
+"are created as needed from these PO files."
+msgstr "A pasta <placeholder-1/> contém os ficheiros 'Portable Object' ou <placeholder-2/> especialmente formatados, criados e usados pelos tradutores. As ferramentas de compilação do Projecto de Documentação do Fedora usam estes ficheiros para criar versões traduzidas dos documentos. Os documentos traduzidos não são guardados no CVS; são criados à medida das necessidades a partir destes ficheiros PO."
+d5975 12
+a5986 3
+#: en_US/module-struct.xml:88(seg) en_US/module-struct.xml:90(filename)
+msgid "Makefile"
+msgstr "Makefile"
+d5988 2
+a5989 7
+#: en_US/module-struct.xml:90(seg)
+msgid ""
+"The <placeholder-1/> controls the build process. Its content is discussed in "
+"<xref linkend=\"ex-makefile\"/>."
+msgstr ""
+"A <placeholder-1/> controla o processo de compilação. O seu conteúdo é "
+"discutido em <xref linkend=\"ex-makefile\"/>."
+d5991 7
+a5997 3
+#: en_US/module-struct.xml:95(filename) en_US/module-struct.xml:97(filename)
+msgid "rpm-info.xml"
+msgstr "rpm-info.xml"
+d5999 3
+a6001 4
+#: en_US/module-struct.xml:97(seg)
+msgid "The <placeholder-1/> file contains document specific metadata"
+msgstr ""
+"O ficheiro <placeholder-1/> contém os meta-dados específicos do documento"
+d6003 25
+a6027 3
+#: en_US/module-struct.xml:102(title)
+msgid "Common Build Tools"
+msgstr "Ferramentas de Compilação Comuns"
+d6029 8
+a6036 12
+#: en_US/module-struct.xml:103(para)
+msgid ""
+"Never add the <systemitem>docs-common</systemitem> build tools directory to "
+"an individual module. Special formatting in the module list downloads these "
+"tools when a user checks out a document module. For more information, refer "
+"to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+msgstr ""
+"Nunca adicione a pasta de ferramentas de compilação <systemitem>docs-common</"
+"systemitem> a um módulo individual. A formatação especial na lista de "
+"módulos transfere estas ferramentas, sempre que um utilizador obtém um "
+"módulo de um documento. Para mais informações, consulte em <xref linkend="
+"\"ch-getting-files-naming-modules\"/>."
+d6038 2
+a6039 3
+#: en_US/module-struct.xml:111(title)
+msgid "The Document Build System"
+msgstr "O Sistema de Compilação dos Documentos"
+d6041 10
+a6050 13
+#: en_US/module-struct.xml:116(para)
+msgid ""
+"In Linux and Fedora documentation, references to commands often include a "
+"number inside parentheses. This number represents the section of "
+"<firstterm>manpages</firstterm> that includes documentation for that "
+"command. To read the manpage for <command>make(1)</command>, use the command "
+"<command>man 1 make</command>."
+msgstr ""
+"No Linux e na documentação do Fedora, as referências aos comandos "
+"normalmente incluem um número entre parêntesis. Este número representa a "
+"secção das <firstterm>páginas de manual</firstterm> que incluem a "
+"documentação para esse comando. Para ler a página de manual para o "
+"<command>make(1)</command>, use o comando <command>man 1 make</command>."
+d6052 10
+a6061 8
+#: en_US/module-struct.xml:112(para)
+msgid ""
+"The build system can render the document into another format such as "
+"<abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</"
+"command><footnote><placeholder-1/></footnote> and shell scripts. Authors "
+"need <emphasis>no</emphasis> prior experience with either shell scripts or a "
+"<command>make(1)</command>."
+msgstr "O sistema de compilação poderá representar o documento noutro formato, como o <abbrev>HTML</abbrev> ou o <abbrev>PDF</abbrev>, usando o <command>make(1)</command><footnote><placeholder-1/></footnote> e os programas da linha de comandos. Os autores <emphasis>não</emphasis> precisam de qualquer experiência anterior com os programas da linha de comandos ou o <command>make(1)</command>."
+d6063 2
+a6064 3
+#: en_US/module-struct.xml:128(title)
+msgid "The Document <filename>Makefile</filename>"
+msgstr "A <filename>Makefile</filename> do Documento"
+d6066 2
+a6067 9
+#: en_US/module-struct.xml:129(para)
+msgid ""
+"Each individual document has its own <filename>Makefile</filename>, which "
+"only needs to be a few lines long. The document <filename>Makefile</"
+"filename> content is designed for cut and paste operations."
+msgstr ""
+"Cada documento individual tem a sua própria <filename>Makefile</filename>, "
+"que só necessita de ter algumas linhas. O conteúdo da <filename>Makefile</"
+"filename> do documento está desenhado para operações de corte e colagem."
+d6069 6
+a6074 8
+#: en_US/module-struct.xml:135(para)
+msgid ""
+"<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</"
+"filename> for a simple document with two files and two translations."
+msgstr ""
+"A <xref linkend=\"ex-makefile\"/> abaixo mostra a <filename>Makefile</"
+"filename> completa de um documento simples com dois ficheiros e duas "
+"traduções."
+d6076 6
+a6081 3
+#: en_US/module-struct.xml:141(title)
+msgid "Sample Document Makefile"
+msgstr "Makefile do Documento de Exemplo"
+d6083 2
+a6084 9
+#: en_US/module-struct.xml:158(para)
+msgid ""
+"Do not be concerned with some of the more complicated syntax such as the "
+"<command>XMLFILES_template</command> stanza. An explanation for this "
+"template appears a few paragraphs below."
+msgstr ""
+"Não se preocupe com alguma da sintaxe mais complicada, como o "
+"<command>XMLFILES_template</command>. Aparecerá em baixo uma explicação para "
+"este modelo."
+d6086 10
+a6095 3
+#: en_US/module-struct.xml:164(title)
+msgid "Makefile Variables"
+msgstr "Variáveis da Makefile"
+d6097 8
+a6104 3
+#: en_US/module-struct.xml:165(segtitle)
+msgid "Variable"
+msgstr "Variável"
+d6106 12
+a6117 3
+#: en_US/module-struct.xml:166(segtitle) en_US/module-struct.xml:244(segtitle)
+msgid "Explanation"
+msgstr "Explicação"
+d6119 2
+a6120 3
+#: en_US/module-struct.xml:168(systemitem)
+msgid "DOCBASE"
+msgstr "DOCBASE"
+d6122 8
+a6129 7
+#: en_US/module-struct.xml:169(seg)
+msgid ""
+"This variable contains the name for the main (parent) XML document. Follow "
+"convention by naming your document after the module name."
+msgstr ""
+"Esta variável contém o nome do documento-pai principal em XML. Siga a "
+"convenção, nomeando o seu documento com o nome do módulo."
+d6131 2
+a6132 3
+#: en_US/module-struct.xml:174(systemitem)
+msgid "PRI_LANG"
+msgstr "PRI_LANG"
+d6134 16
+a6149 7
+#: en_US/module-struct.xml:175(seg)
+msgid ""
+"This variable contains the ISO code for the original version of the "
+"document, such as <placeholder-1/>."
+msgstr ""
+"Esta variável contém o código ISO da versão original do documento, como em "
+"<placeholder-1/>."
+d6151 2
+a6152 3
+#: en_US/module-struct.xml:180(systemitem)
+msgid "OTHERS"
+msgstr "OTHERS"
+d6154 11
+a6164 10
+#: en_US/module-struct.xml:181(seg)
+msgid ""
+"This variable contains a listing of ISO codes for any other versions into "
+"which the document has been translated. The module must contain a "
+"<placeholder-1/> directory and a PO file for any indicated additional "
+"languages."
+msgstr ""
+"Esta variável contém uma lista dos códigos ISO das outras versões traduzidas "
+"do documento. O módulo deverá conter uma pasta <placeholder-1/> e um "
+"ficheiro PO para cada língua adicional indicada."
+d6166 14
+a6179 3
+#: en_US/module-struct.xml:188(systemitem)
+msgid "DOC_ENTITIES"
+msgstr "DOC_ENTITIES"
+d6181 6
+a6186 12
+#: en_US/module-struct.xml:189(seg)
+msgid ""
+"This variable contains a listing of any files containing entity definitions. "
+"The Fedora Documentation Project uses a special XML format to record "
+"document-specific entities, so they can be translated and built on the fly "
+"like any other XML document. An example is shown later in this guide."
+msgstr ""
+"Esta variável contém uma listagem de todos os ficheiros que contêm "
+"definições de entidades. O Projecto de Documentação do Fedora usa um formato "
+"em XML especial para guardar as entidades específicas do documento, de modo "
+"que possam ser traduzidas e geradas na altura, como se fosse outro documento "
+"em XML qualquer. Aparecerá então um exemplo mais tarde neste guia."
+d6188 3
+a6190 3
+#: en_US/module-struct.xml:198(systemitem)
+msgid "XMLFILES_template"
+msgstr "XMLFILES_template"
+d6192 2
+a6193 3
+#: en_US/module-struct.xml:201(systemitem)
+msgid "${1}"
+msgstr "${1}"
+d6195 2
+a6196 3
+#: en_US/module-struct.xml:206(systemitem)
+msgid "${1}/"
+msgstr "${1}/"
+d6198 2
+a6199 16
+#: en_US/module-struct.xml:199(seg)
+msgid ""
+"This template allows the build tools to work with the document in multiple "
+"languages once it is translated. The <placeholder-1/> marking is a variable "
+"used to substitute the appropriate language. This template is not terribly "
+"complicated. For a new module, duplicate this section exactly except for the "
+"actual filenames. Prepend the text <placeholder-2/>, in place of the "
+"language code directory name, to each filename in your document."
+msgstr ""
+"Este modelo permite às ferramentas de compilação funcionarem com o documento "
+"em várias línguas, logo que esteja traduzido. A marcação <placeholder-1/> é "
+"uma variável que é usada para substituir a língua apropriada. Este modelo "
+"não é terrivelmente complicado. Para um módulo novo, duplique esta secção "
+"exactamente, excepto os nomes dos ficheiros em si. Coloque antes o texto "
+"<placeholder-2/>, no lugar do nome da pasta do código da língua, para cada "
+"nome de ficheiro no seu documento."
+d6201 8
+a6208 3
+#: en_US/module-struct.xml:212(title)
+msgid "Files Exempt From Listing"
+msgstr "Ficheiros Isentos da Listagem"
+d6210 2
+a6211 8
+#: en_US/module-struct.xml:213(para)
+msgid ""
+"Do not include the document-specific entities XML file or the <filename>rpm-"
+"info.xml</filename> file, which will be discussed later in this guide."
+msgstr ""
+"Não inclua o ficheiro XML de entidades específicas do documento nem o "
+"ficheiro <filename>rpm-info.xml</filename>, os quais serão descritos "
+"posteriormente neste guia."
+d6213 2
+a6214 13
+#: en_US/module-struct.xml:217(para)
+msgid ""
+"The final section, beginning with <literal>define</literal>, locates the "
+"main <filename>Makefile.common</filename> for the build system. This "
+"<filename>Makefile.common</filename> file contains all the <application>make"
+"(1)</application> targets and rules to actually build the document and the "
+"various archives."
+msgstr ""
+"A secção final, que começa por <literal>define</literal>, localiza o "
+"ficheiro <filename>Makefile.common</filename> principal para o sistema de "
+"compilação. Este ficheiro <filename>Makefile.common</filename> contém todos "
+"os alvos e regras do <application>make(1)</application> para criar de facto "
+"o documento e os vários pacotes."
+d6216 7
+a6222 3
+#: en_US/module-struct.xml:226(title)
+msgid "The Document <filename>rpm-info.xml</filename>"
+msgstr "O <filename>rpm-info.xml</filename> do Documento"
+d6224 13
+a6236 14
+#: en_US/module-struct.xml:227(para)
+msgid ""
+"Each document module's primary language directory contains a file called "
+"<filename>rpm-info.xml</filename>. This file contains document-specific "
+"metadata used to generate revision history, copyright, and contributor "
+"information. It follows a DTD specification included with the rest of the "
+"build system tools."
+msgstr ""
+"Cada pasta da língua primária do módulo do documento contém um ficheiro "
+"chamado filename>rpm-info.xml</filename>. Este ficheiro contém os meta-"
+"dados específicos do documento que são usados para gerir o histórico de "
+"revisões, direitos de cópia e a informação de contribuintes. Esta segue uma "
+"especificação em DTD que vem incluída com o resto das ferramentas do sistema "
+"de compilação."
+d6238 8
+a6245 3
+#: en_US/module-struct.xml:236(title)
+msgid "Build System Actions"
+msgstr "Acções do Sistema de Compilação"
+d6247 9
+a6255 7
+#: en_US/module-struct.xml:237(para)
+msgid ""
+"To render the <abbrev>XML</abbrev> document into another format, use one of "
+"the following <command>make</command> targets:"
+msgstr ""
+"Para representar o documento em <abbrev>XML</abbrev> noutro formato, use um "
+"dos seguintes alvos do <command>make</command>:"
+d6257 6
+a6262 3
+#: en_US/module-struct.xml:242(title)
+msgid "Build Targets"
+msgstr "Alvos de Compilação"
+d6264 32
+a6295 3
+#: en_US/module-struct.xml:243(segtitle)
+msgid "Target"
+msgstr "Alvo"
+d6297 2
+a6298 3
+#: en_US/module-struct.xml:246(systemitem)
+msgid "html"
+msgstr "html"
+d6300 14
+a6313 4
+#: en_US/module-struct.xml:247(abbrev) en_US/module-struct.xml:258(abbrev)
+#: en_US/module-struct.xml:283(abbrev) en_US/module-struct.xml:288(abbrev)
+msgid "HTML"
+msgstr "HTML"
+d6315 2
+a6316 4
+#: en_US/module-struct.xml:251(systemitem)
+#: en_US/module-struct.xml:261(systemitem)
+msgid "${DOCBASE}"
+msgstr "${DOCBASE}"
+d6318 10
+a6327 4
+#: en_US/module-struct.xml:252(systemitem)
+#: en_US/module-struct.xml:262(systemitem)
+msgid "${LANG}"
+msgstr "${LANG}"
+d6329 9
+a6337 3
+#: en_US/module-struct.xml:250(filename)
+msgid "<placeholder-1/>-<placeholder-2/>/"
+msgstr "<placeholder-1/>-<placeholder-2/>/"
+d6339 6
+a6344 11
+#: en_US/module-struct.xml:247(seg)
+msgid ""
+"This target builds the \"chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a separate directory named "
+"<placeholder-2/>. Each document section is a separate file within that "
+"directory."
+msgstr ""
+"Este alvo compila o documento <placeholder-1/> \"em blocos\" para cada "
+"tradução definida. O resultado é colocado numa pasta separada, chamada "
+"<placeholder-2/>. Cada secção do documento fica num ficheiro separado, "
+"dentro dessa pasta."
+d6346 3
+a6348 3
+#: en_US/module-struct.xml:257(systemitem)
+msgid "html-nochunks"
+msgstr "html-nochunks"
+d6350 12
+a6361 3
+#: en_US/module-struct.xml:260(filename)
+msgid "<placeholder-1/>-<placeholder-2/>.html"
+msgstr "<placeholder-1/>-<placeholder-2/>.html"
+d6363 7
+a6369 9
+#: en_US/module-struct.xml:258(seg)
+msgid ""
+"This target builds the \"non-chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a single file: <placeholder-2/>; no "
+"other files are created."
+msgstr ""
+"Este alvo gera o documento <placeholder-1/> \"inteiro\" para cada tradução "
+"definida. O resultado é colocado num único ficheiro: <placeholder-2/>; não "
+"são criados outros ficheiros."
+d6371 6
+a6376 3
+#: en_US/module-struct.xml:266(systemitem)
+msgid "pdf"
+msgstr "pdf"
+d6378 2
+a6379 4
+#: en_US/module-struct.xml:267(abbrev) en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:284(abbrev) en_US/module-struct.xml:289(abbrev)
+msgid "PDF"
+msgstr "PDF"
+d6381 9
+a6389 9
+#: en_US/module-struct.xml:267(seg)
+msgid ""
+"This target builds only the <placeholder-1/> document for all document "
+"languages. <placeholder-2/> production is currently erratic and may not work "
+"for your document."
+msgstr ""
+"Este alvo constrói apenas o documento <placeholder-1/> para todas as línguas "
+"do documento. A produção em <placeholder-2/> tem alguns problemas e poderá "
+"não funcionar para o seu documento."
+d6391 9
+a6399 3
+#: en_US/module-struct.xml:272(systemitem)
+msgid "tarball"
+msgstr "tarball"
+d6401 6
+a6406 3
+#: en_US/module-struct.xml:273(command)
+msgid "tar(1)"
+msgstr "tar(1)"
+d6408 2
+a6409 7
+#: en_US/module-struct.xml:273(seg)
+msgid ""
+"This target builds only the <placeholder-1/> archive for all document "
+"languages."
+msgstr ""
+"Este alvo constrói apenas o pacote <placeholder-1/> para todas as línguas do "
+"documento."
+d6411 2
+a6412 3
+#: en_US/module-struct.xml:277(systemitem)
+msgid "all"
+msgstr "all"
+d6414 22
+a6435 3
+#: en_US/module-struct.xml:278(seg)
+msgid "This target builds all targets listed above."
+msgstr "Este alvo constrói todos os alvos apresentados em cima."
+d6437 8
+a6444 4
+#: en_US/module-struct.xml:281(systemitem)
+#: en_US/module-struct.xml:290(filename)
+msgid "clean"
+msgstr "clean"
+d6446 8
+a6453 3
+#: en_US/module-struct.xml:283(emphasis)
+msgid "not"
+msgstr "não"
+d6455 5
+a6459 7
+#: en_US/module-struct.xml:282(seg)
+msgid ""
+"This target deletes any temporary, or generated files, but does <placeholder-"
+"1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr ""
+"Este alvo apaga todos os ficheiros temporários ou gerados, mas <placeholder-"
+"1/> apaga os ficheiros <placeholder-2/>, <placeholder-3/> ou pacotes."
+d6461 2
+a6462 3
+#: en_US/module-struct.xml:287(systemitem)
+msgid "distclean"
+msgstr "distclean"
+d6464 49
+a6512 7
+#: en_US/module-struct.xml:288(seg)
+msgid ""
+"This target erases all <placeholder-1/>, <placeholder-2/>, and archive "
+"files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr ""
+"Este alvo apaga todos os ficheiros <placeholder-1/>, <placeholder-2/> e de "
+"pacotes. Este alvo também invoca automaticamente o alvo <placeholder-3/>."
+d6514 2
+a6515 3
+#: en_US/module-struct.xml:295(title)
+msgid "PDF Generation is Erratic"
+msgstr "A Geração de PDFs tem Problemas"
+d6517 2
+a6518 7
+#: en_US/module-struct.xml:296(para)
+msgid ""
+"<abbrev>PDF</abbrev> production is currently erratic and may not work for "
+"your document."
+msgstr ""
+"A produção de <abbrev>PDF</abbrev> tem alguns problemas e poderá não "
+"funcionar para o seu documento."
+d6520 2
+a6521 3
+#: en_US/module-struct.xml:300(title)
+msgid "Adding or Changing Targets"
+msgstr "Adicionar ou Modificar os Alvos"
+d6523 24
+a6546 13
+#: en_US/module-struct.xml:301(para)
+msgid ""
+"To add a new target and rules, place them at the bottom of the document "
+"<filename>Makefile</filename>, below the <literal>include</literal> line. "
+"Follow your target definitions with a double colon, not a single colon. The "
+"double colon allows you to specify additional rules for existing targets, or "
+"to write rules for a new target."
+msgstr ""
+"Para adicionar um novo alvo e regras, coloque-as no fundo da "
+"<filename>Makefile</filename> do documento, por baixo da linha "
+"<literal>include</literal>. Siga as definições do seu alvo com dois-pontos "
+"duplos, não apenas um. Os dois-pontos duplos permitem-lhe definir regras "
+"adicionais para os alvos existentes ou escrever regras para um novo alvo."
+d6548 6
+a6553 8
+#: en_US/module-struct.xml:309(para)
+msgid ""
+"For more information on using <command>make(1)</command>, consult the online "
+"documentation with the command <command>info make</command> in a terminal."
+msgstr ""
+"Para mais informações sobre a utilização do <command>make(1)</command>, "
+"consulte a documentação 'online' com o comando <command>info make</command> "
+"num terminal."
+d6555 2
+a6556 3
+#: en_US/module-struct.xml:316(title)
+msgid "Using Document Image Files"
+msgstr "Usar os Ficheiros de Imagens do Documento"
+d6558 2
+a6559 11
+#: en_US/module-struct.xml:317(para)
+msgid ""
+"Tutorial documents often make use of images such as <filename class="
+"\"extension\">.PNG</filename> files. Store image files in a <filename class="
+"\"directory\">figs/</filename> folder in the main module directory, as shown "
+"in <xref linkend=\"ex-module-structure\"/>."
+msgstr ""
+"Os documentos de tutoriais normalmente utilizam imagens como os ficheiros "
+"<filename class=\"extension\">.PNG</filename>. Guarde os ficheiros de "
+"imagens numa pasta <filename class=\"directory\">figs/</filename> da pasta "
+"do módulo principal, como aparece em <xref linkend=\"ex-module-structure\"/>."
+d6561 2
+a6562 21
+#: en_US/module-struct.xml:324(para)
+msgid ""
+"Depending on the output media, sometimes images may be scaled, streteched, "
+"or squashed. To minimize any distortions, we recommend that you use only "
+"<filename class=\"extension\">.PNG</filename> images. Avoid <filename class="
+"\"extension\">.JPG</filename> files. The <command>convert(1)</command> "
+"program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</"
+"abbrev> package, provides a convenient way to reformat <filename class="
+"\"extension\">.JPG</filename> images into <filename class=\"extension\">."
+"PNG</filename> format. For more information on formatting images such as "
+"screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr ""
+"Dependendo do formato de saída, algumas das imagens poderão ser esticadas, "
+"encolhidas ou desfeitas. Para minimizar as distorções, recomenda-se que use "
+"apenas as imagens <filename class=\"extension\">.PNG</filename>. Evite os "
+"ficheiros <filename class=\"extension\">.JPG</filename>. O programa "
+"<command>convert(1)</command>, do pacote <abbrev>RPM</abbrev> <package role="
+"\"rpm\">ImageMagick</package>, oferece uma forma conveniente de formatar de "
+"novo as <filename class=\"extension\">.JPG</filename> no formato <filename "
+"class=\"extension\">.PNG</filename>. Para mais informações sobre a "
+"formatação das imagens, veja em <xref linkend=\"sn-screenshots\"/>."
+d6564 8
+a6571 10
+#: en_US/module-struct.xml:338(para)
+msgid ""
+"Image files may be organized into subdirectories under <filename>figs/</"
+"filename> if necessary. The document building system recreates the image "
+"subdirectory structure in the output documents."
+msgstr ""
+"Os ficheiros de imagens poderão estar organizados em sub-pastas da "
+"<filename>figs/</filename>, se necessário. O sistema de compilação de "
+"documentos irá criar de novo a estrutura de sub-pastas das imagens nos "
+"documentos resultantes."
+d6573 9
+a6581 16
+#: en_US/module-struct.xml:344(para)
+msgid ""
+"Images often contain labels or other text which may need to be localized. A "
+"screenshot of a program, for example, may require a version for each "
+"translated language. Name language-dependent image files such as program "
+"screenshots by adding the language code to the filename, such as "
+"<filename>menu-en_US.png</filename>. Language-independent images, such as "
+"<filename>icon.png</filename>, do not need language codes."
+msgstr ""
+"As imagens contêm normalmente legendas ou outros textos que possam ter de "
+"ser traduzidos. Uma imagem de um programa, por exemplo, poderá necessitar de "
+"uma versão para cada língua traduzida. Dê um nome dependente da língua aos "
+"ficheiros de imagens, adicionando o código da língua ao nome do ficheiro, "
+"como acontece em <filename>menu-pt.png</filename>. As imagens independentes "
+"da língua, como o <filename>icon.png</filename>, não precisam de códigos de "
+"línguas."
+d6583 6
+a6588 15
+#: en_US/module-struct.xml:354(para)
+msgid ""
+"Sometimes, a document may require images that do not follow the naming "
+"convention. To use these images with the document building system, create an "
+"ordinary text file containing the image filenames. This file must be named "
+"<filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</"
+"systemitem> so the build system finds it when searching for image filenames."
+msgstr ""
+"Em alguns casos, um documento poderá necessitar de imagens que não sigam a "
+"nomenclatura. Para usar estas imagens com o sistema de compilação do "
+"documento, crie um ficheiro de texto normal que contém os nomes dos "
+"ficheiros de imagens. Este ficheiro dever-se-á chamar <filename>figs/"
+"Manifest-</filename><systemitem class=\"macro\">${LANG}</systemitem>, de "
+"modo que o sistema de compilação o descubra quando procurar pelos nomes dos "
+"ficheiros de imagens."
+d6590 2
+a6591 7
+#: en_US/module-struct.xml:363(para)
+msgid ""
+"<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one "
+"way to create this <filename>Manifest</filename> file."
+msgstr ""
+"O <xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstra uma "
+"forma de criar este ficheiro <filename>Manifest</filename>."
+d6593 8
+a6600 3
+#: en_US/module-struct.xml:369(title)
+msgid "Building A Manifest"
+msgstr "Criar um Manifest"
+d6602 8
+a6609 3
+#: en_US/module-struct.xml:376(title)
+msgid "Adding a New DocBook XML File"
+msgstr "Adicionar um Novo Ficheiro de DocBook em XML"
+d6611 6
+a6616 6
+#: en_US/module-struct.xml:377(para)
+msgid ""
+"To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr ""
+"Para adicionar um novo ficheiro de DocBook em XML a um documento existente, "
+"siga estes passos:"
+d6618 2
+a6619 3
+#: en_US/module-struct.xml:381(para)
+msgid "Place the new DocBook XML file in the primary language directory."
+msgstr "Coloque o novo ficheiro de DocBook em XML na pasta da língua primária."
+d6621 7
+a6627 13
+#: en_US/module-struct.xml:385(para)
+msgid ""
+"Edit the <filename>Makefile</filename> and add the filename to the "
+"<varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to "
+"the last existing line, and on the next line add an entry for the new file. "
+"Remember to add the <literal>${1}/</literal> prefix as a substitute for the "
+"language directory name."
+msgstr ""
+"Edite a <filename>Makefile</filename> e adicione o nome do ficheiro à "
+"listagem <varname>XMLFILES-${1}</varname>. Adicione uma <keycap>\\</keycap> "
+"à última linha existente e, na linha seguinte, adicione um item para o novo "
+"ficheiro. Lembre-se de adicionar o prefixo <literal>${1}/</literal> como "
+"substituto para o nome da pasta da língua."
+d6629 8
+a6636 3
+#: en_US/module-struct.xml:395(title)
+msgid "Adding a Translation"
+msgstr "Adicionar uma Tradução"
+d6638 2
+a6639 12
+#: en_US/module-struct.xml:396(para)
+msgid ""
+"Translations are stored as PO (portable object) files, which the toolchain "
+"transforms into translated documents. Each PO file is based on the POT (PO "
+"template) for the document and translated by the Fedora Translation Project. "
+"To add a translation, follow these steps:"
+msgstr ""
+"As traduções são guardadas como ficheiros PO (portable object - objecto "
+"portável), que o conjunto de ferramentas irá transformar em documentos "
+"traduzidos. Cada um dos ficheiros PO baseia-se no POT (modelo de PO) do "
+"documento e é traduzido pelo Projecto de Traduções do Fedora. Para adicionar "
+"uma tradução, siga estes passos:"
+d6641 2
+a6642 7
+#: en_US/module-struct.xml:403(para)
+msgid ""
+"If the <filename class=\"directory\">po/</filename> directory does not "
+"exist, create it and add it to CVS:"
+msgstr ""
+"Se a pasta <filename class=\"directory\">po/</filename> não existir, crie-a "
+"e adicione-a ao CVS:"
+d6644 2
+a6645 3
+#: en_US/module-struct.xml:409(para)
+msgid "If it does not exist, create the POT file:"
+msgstr "Se este não existir, crie o ficheiro POT:"
+d6647 2
+a6648 7
+#: en_US/module-struct.xml:413(para)
+msgid ""
+"Add the new translation language to the <varname>OTHERS</varname> listing in "
+"the <filename>Makefile</filename>."
+msgstr ""
+"Adicione a nova língua da tradução à listagem do <varname>OTHERS</varname> "
+"na <filename>Makefile</filename>."
+d6650 8
+a6657 7
+#: en_US/module-struct.xml:418(para)
+msgid ""
+"Although translators often copy the POT manually to create the new PO file, "
+"the following command also works:"
+msgstr ""
+"Ainda que os tradutores copiem normalmente de forma manual o ficheiro POT "
+"para criar o novo ficheiro PO, o seguinte comando também funciona:"
+d6659 11
+a6669 3
+#: en_US/module-struct.xml:421(replaceable)
+msgid "lang"
+msgstr "língua"
+d6671 14
+a6684 4
+#: en_US/module-struct.xml:421(screen)
+#, no-wrap
+msgid "make po/<placeholder-1/>.po"
+msgstr "make po/<placeholder-1/>.po"
+d6686 9
+a6694 3
+#: en_US/intro.xml:13(title)
+msgid "Introduction"
+msgstr "Introdução"
+d6696 2
+a6697 9
+#: en_US/intro.xml:15(para)
+msgid ""
+"The goal of the Fedora Documentation Project is to create easy-to-follow, "
+"task-based documentation for Fedora users and developers. The Fedora "
+"Documentation Project uses the following tools:"
+msgstr ""
+"O objectivo do Projecto de Documentação do Fedora é criar documentação "
+"simples de usar, baseada em tarefas, para os utilizadores e programadores do "
+"Fedora. O Projecto de Documentação do Fedora usa as seguintes ferramentas:"
+d6699 10
+a6708 3
+#: en_US/intro.xml:23(para)
+msgid "DocBook XML v4.4"
+msgstr "DocBook XML v4.4"
+d6710 8
+a6717 4
+#: en_US/intro.xml:26(para)
+msgid "Custom XSLT stylesheets for both print and HTML versions"
+msgstr ""
+"Folhas de estilo XSLT personalizadas para as versões impressas e em HTML"
+d6719 3
+a6721 5
+#: en_US/intro.xml:30(para)
+msgid "Custom scripts to generate HTML output (use <command>xmlto</command>)"
+msgstr ""
+"Programas personalizados para gerar o resultado em HTML (use o "
+"<command>xmlto</command>)"
+d6723 2
+a6724 3
+#: en_US/intro.xml:34(para)
+msgid "Emacs with PSGML mode (optional, but recommended)"
+msgstr "Emacs com o modo PSGML (opcional, mas recomendado)"
+d6726 12
+a6737 9
+#: en_US/intro.xml:43(para)
+msgid ""
+"This document explains the tools used by the Fedora Documentation Project "
+"and provides writing and tagging guidelines to make Fedora documentation is "
+"consistent and easy-to-follow."
+msgstr ""
+"Este documento explica as ferramentas usadas pelo Projecto de Documentação "
+"do Fedora e oferece algumas recomendações de escrita e marcação que tornam a "
+"documentação do Fedora consistente e fácil de seguir."
+d6739 24
+a6762 3
+#: en_US/getting-files.xml:12(title)
+msgid "Prerequisites"
+msgstr "Pré-requisitos"
+d6764 10
+a6773 8
+#: en_US/getting-files.xml:14(para)
+msgid ""
+"To work on official Fedora documentation you need to install the required "
+"tools. Follow the directions below to configure your system."
+msgstr ""
+"Para lidar com a documentação oficial do Fedora, terá de instalar as "
+"seguintes ferramentas. Siga as instruções abaixo para configurar o seu "
+"sistema."
+d6775 2
+a6776 3
+#: en_US/getting-files.xml:20(title)
+msgid "System Packages"
+msgstr "Pacotes do Sistema"
+d6778 10
+a6787 8
+#: en_US/getting-files.xml:22(para)
+msgid ""
+"Install the \"Authoring and Publishing\" package group, which contains "
+"required DocBook XML files, stylesheets and scripts:"
+msgstr ""
+"Instale o grupo de pacotes \"Authoring and Publishing\" (Autoria e "
+"Publicações), que contém os ficheiros de DocBook em XML necessários, as "
+"folhas de estilo e os programas:"
+d6789 12
+a6800 4
+#: en_US/getting-files.xml:28(userinput)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+msgstr "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+d6802 6
+a6807 7
+#: en_US/getting-files.xml:31(para)
+msgid ""
+"Next, install the <filename>cvs</filename> package, which is used to handle "
+"revision control on files in the official repository:"
+msgstr ""
+"De seguida, instale o pacote <filename>cvs</filename>, que é usado para "
+"lidar com o controlo de versões nos ficheiros do repositório oficial:"
+d6809 2
+a6810 4
+#: en_US/getting-files.xml:37(userinput)
+#, no-wrap
+msgid "su -c 'yum install cvs'"
+msgstr "su -c 'yum install cvs'"
+d6812 2
+a6813 10
+#: en_US/getting-files.xml:40(para)
+msgid ""
+"If you plan to use <application>Emacs</application> to edit DocBook XML "
+"documentation, install <package>psgml</package>, which adds helpful and time-"
+"saving functionality to maximize editing efficiency:"
+msgstr ""
+"Se pensar em usar o <application>Emacs</application> para editar a "
+"documentação DocBook em XML, instale o pacote <package>psgml</package>, que "
+"adiciona funcionalidades úteis e de poupança de tempo, de modo a maximizar a "
+"eficiência na edição:"
+d6815 8
+a6822 4
+#: en_US/getting-files.xml:44(userinput)
+#, no-wrap
+msgid "su -c 'yum install psgml'"
+msgstr "su -c 'yum install psgml'"
+d6824 6
+a6829 3
+#: en_US/getting-files.xml:48(title)
+msgid "Fedora Documentation Tools"
+msgstr "Ferramentas de Documentação do Fedora"
+d6831 6
+a6836 9
+#: en_US/getting-files.xml:50(para)
+msgid ""
+"The Fedora Documentation Project's custom scripts and stylesheets are stored "
+"in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</"
+"systemitem> CVS server. When you check out a document module from CVS, the "
+"tools are included in the module inside the <filename class=\"directory"
+"\">docs-common/</filename> directory. To work on existing documents in CVS, "
+"refer to <xref linkend=\"ch-cvs\"/>."
+msgstr "Os programas e folhas de estilo personalizados do Projecto de Documentação do Fedora estão guardados em CVS, no servidor <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</systemitem>. Quando transfere um módulo de documentos do CVS, s ferramentas vão incluídas no módulo, dentro da pasta <filename class=\"directory\">docs-common/</filename>. Para trabalhar sobre documentos existentes no CVS, consulte a secção <xref linkend=\"ch-cvs\"/>."
+d6838 11
+a6848 15
+#: en_US/getting-files.xml:59(para)
+msgid ""
+"The most powerful component in the Fedora Documentation Project toolbox is "
+"<firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for "
+"authoring technical documentation using <firstterm>Extensible Markup "
+"Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark "
+"pieces of content with descriptive tags. The following output is an example "
+"of DocBook XML:"
+msgstr ""
+"O componente mais poderoso no pacote de ferramentas do Projecto de "
+"Documentação do Fedora é o <firstterm>DocBook XML</firstterm>. O DocBook XML "
+"é um esquema específico para gerar documentação técnica, usando a "
+"<firstterm>Extensible Markup Language</firstterm> ou <acronym>XML</acronym>. "
+"O XML permite aos autores marcarem certas partes de conteúdo com marcas "
+"descritivas. Segue-se um exemplo de DocBook XML:"
+d6850 6
+a6855 10
+#: en_US/getting-files.xml:76(para)
+msgid ""
+"This example article, entitled <citetitle>A Very Short Article</citetitle>, "
+"consists of only a single paragraph. The tags, or markup, surround elements "
+"of content to define the sense in which they are used. A paragraph, for "
+"example, is marked with <sgmltag>para</sgmltag> tags. Text that requires "
+"emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does "
+"not worry about the visual formatting such as italics or font size. Fedora "
+"Documentation Project build tools automatically perform all formatting tasks."
+msgstr "Este artigo de exemplo, chamado <citetitle>Um Artigo Muito Curto</citetitle>, consiste apenas num único parágrafo. As marcas de formatação reúnem os elementos de conteúdo para definirem o sentido em que são usadas. Um parágrafo, por exemplo, é rodeado com marcas <sgmltag>para</sgmltag>. O texto que necessite de ênfase está marcado com <sgmltag>emphasis</sgmltag>. O autor não se irá preocupar com a formatação visual, como os itálicos ou o tamanho da letra. As ferramentas de compilação do Projecto de Documentação do Fedora efectuam todas as tarefas de formatação."
+d6857 14
+a6870 9
+#: en_US/getting-files.xml:85(para)
+msgid ""
+"The custom tools built by the Fedora Documentation Project render DocBook "
+"source into a variety of formats for publication and distribution. They also "
+"allow translators to create localized versions of the XML documents for "
+"Fedora users around the world. The flexibility of XML allows for a single "
+"document to be used many times for many purposes, like reusable code for a "
+"programmer."
+msgstr "As ferramentas personalizadas, criadas pelo Projecto de Documentação do Fedora, representam o código em DocBook numa variedade de formatos para publicação e distribuição. Também permitem aos tradutores criarem versões locais dos documentos de XML, para os utilizadores de Fedora em todo o mundo. A flexibilidade do XML permite a um único documento ser usado várias vezes para diversos fins, como a reutilização de código para um programador."
+d6872 32
+a6903 8
+#: en_US/getting-files.xml:91(para)
+msgid ""
+"DocBook is itself very well documented. For more information about DocBook, "
+"visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also "
+"features complete copies of <citetitle>DocBook: The Definitive Guide</"
+"citetitle> to browse and download, the canonical source for DocBook "
+"information."
+msgstr "O DocBook está em si muito bem documentado. Para mais informações acerca do DocBook, visite a página <ulink url=\"http://www.docbook.org/\"/>. A página do DocBook também contém cópias completas do livro <citetitle>DocBook: The Definitive Guide</citetitle> para navegar e transferir, sendo esta a fonte canónica de informação sobre o DocBook."
+d6905 2
+a6906 3
+#: en_US/getting-files.xml:97(title)
+msgid "DocBook XML Versions"
+msgstr "Versões do DocBook XML"
+d6908 3
+a6910 11
+#: en_US/getting-files.xml:98(para)
+msgid ""
+"DocBook XML, like a computer program, has version numbers. The version used "
+"by Fedora Documentation Project right now is 4.4. The DocBook web site may "
+"document a slightly newer version, but the majority of the schema still "
+"applies."
+msgstr ""
+"O DocBook XML, como um programa de computador, tem números de versões. A "
+"versão usada no Projecto de Documentação do Fedora neste momento é a 4.4. A "
+"página Web do DocBook poderá conter uma versão ligeiramente mais recente, "
+"mas a maioria do esquema aplica-se à mesma."
+d6912 2
+a6913 3
+#: en_US/getting-files.xml:106(title)
+msgid "Naming Conventions"
+msgstr "Convenções dos Nomes"
+d6915 2
+a6916 14
+#: en_US/getting-files.xml:107(para)
+msgid ""
+"The Fedora Documentation Project provides the tools, scripts, and "
+"stylesheets to transform your <abbrev>XML</abbrev> documents into other "
+"output formats such as <abbrev>HTML</abbrev>. In addition, these tools can "
+"build your document into a <abbrev>RPM</abbrev> package. To take advantage "
+"of these services, follow the conventions in this section to name your files."
+msgstr ""
+"O Projecto de Documentação do Fedora oferece as ferramentas, programas e "
+"folhas de estilo que transformam os seus documentos em <abbrev>XML</abbrev> "
+"noutros formatos resultantes, como o <abbrev>HTML</abbrev>. Para além disso, "
+"estas ferramentas podem transformar o seu documento num pacote <abbrev>RPM</"
+"abbrev>. Para tirar partido destes serviços, deverá seguir as convenções de "
+"nomenclatura dos seus ficheiros."
+d6918 2
+a6919 16
+#: en_US/getting-files.xml:115(para)
+msgid ""
+"On the CVS server, directories that contain document files are called "
+"<firstterm>modules</firstterm>. Each module represents a single document. "
+"Each document may consist of several <firstterm>branches</firstterm> if that "
+"document changes with each release of Fedora. Contributors can check out "
+"single branches of these modules or the entire module. Each document or "
+"branch may contain multiple XML source files."
+msgstr ""
+"No servidor de CVS, as pastas que contêm os ficheiros de documentos chamam-"
+"se <firstterm>módulos</firstterm>. Cada módulo representa um único "
+"documento. Cada documento poderá consistir em várias "
+"<firstterm>ramificações</firstterm>, se esse documento for alterado em cada "
+"versão do Fedora. Os contribuintes poderão obter ramificações únicas desses "
+"módulos ou então o módulo inteiro. Cada documento ou ramificação poderá "
+"conter vários ficheiros em XML."
+d6921 11
+a6931 4
+#: en_US/getting-files.xml:122(para)
+msgid ""
+"Use the <command>cvs co -c</command> command to view existing module names."
+msgstr "Use sempre o comando <command>cvs co -c</command> para ver os nomes dos módulos existentes."
+d6933 6
+a6938 3
+#: en_US/getting-files.xml:125(title)
+msgid "Partial List of CVS Modules"
+msgstr "Lista Parcial dos Módulos do CVS"
+d6940 48
+a6987 4
+#: en_US/getting-files.xml:126(userinput)
+#, no-wrap
+msgid "cd ~/localrepo/fedora-docs/"
+msgstr "cd ~/repositorio-local/fedora-docs/"
+d6989 7
+a6995 12
+#: en_US/getting-files.xml:145(para)
+msgid ""
+"The leftmost entry in each line is the name of a module you can check out "
+"from CVS. The rest of the line ensures that checkouts include the proper "
+"branch of a document and the common build tools. For more information on "
+"CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+"O item mais à esquerda de cada linha é o nome de um módulo que poderá "
+"transferir do CVS. O restante da linha garante que as transferências incluem "
+"a ramificação correcta de um documento, assim como as ferramentas de "
+"compilação comuns. Para mais informações sobre o CVS, consulte em <xref "
+"linkend=\"ch-cvs\"/>."
+d6997 15
+a7011 13
+#: en_US/getting-files.xml:150(para)
+msgid ""
+"Note in the listing above that the <systemitem>about-fedora</systemitem> "
+"module has two branches available. One branch is for Fedora 7 and one is for "
+"forward development to match the current work of developers. On the other "
+"hand, the <systemitem>documentation-guide</systemitem> module is not "
+"branched."
+msgstr ""
+"Repare na listagem acima que o módulo <systemitem>about-fedora</systemitem> "
+"tem duas ramificações disponíveis. Uma é para o Fedora 7 e outra é para a "
+"versão em desenvolvimento posterior, reflectindo o trabalho actual dos "
+"programadores. Por outro lado, o módulo <systemitem>documentation-guide</"
+"systemitem> não tem ramificações."
+d7013 2
+a7014 3
+#: en_US/getting-files.xml:157(title)
+msgid "Modules Labeled <filename>-dir</filename>"
+msgstr "Módulos Chamados <filename>-dir</filename>"
+d7016 6
+a7021 10
+#: en_US/getting-files.xml:158(para)
+msgid ""
+"Modules ending with the suffix <filename>-dir</filename> are not usually "
+"helpful to checkout directly. These modules do not include the common build "
+"tools and thus do not provide many of the functions contributors require."
+msgstr ""
+"Os módulos que terminam com o sufixo <filename>-dir</filename> não são "
+"normalmente úteis para transferir directamente. Estes módulos não incluem as "
+"ferramentas de compilação comuns e, deste modo, não oferecem muitas das "
+"funções que os contribuintes necessitam."
+d7023 6
+a7028 3
+#: en_US/getting-files.xml:164(title)
+msgid "Module Names"
+msgstr "Nomes dos Módulos"
+d7030 53
+a7082 14
+#: en_US/getting-files.xml:165(para)
+msgid ""
+"Choose a module name that accurately reflects your document's subject, but "
+"avoid any name already taken. The document title without any use of the word "
+"<wordasword>fedora</wordasword> is a reasonable choice in most cases. Use "
+"the length descriptors <wordasword>tutorial</wordasword> or "
+"<wordasword>guide</wordasword> in the module name where appropriate."
+msgstr ""
+"Escolha um nome de módulo que reflicta com precisão o assunto do seu "
+"documento, mas evite um nome que já tenha sido usado. O título do documento "
+"sem usar a palavra <wordasword>fedora</wordasword> é normalmente uma escolha "
+"razoável na maioria dos casos. Use as descrições da dimensão "
+"<wordasword>tutorial</wordasword> ou <wordasword>guide</wordasword> (guia) "
+"no nome do módulo, se for apropriado."
+d7084 2
+a7085 3
+#: en_US/getting-files.xml:174(title)
+msgid "Avoid Redundancy"
+msgstr "Evite Redundâncias"
+d7087 7
+a7093 5
+#: en_US/getting-files.xml:175(para)
+msgid ""
+"Do not use the word <wordasword>fedora</wordasword> to name modules in the "
+"Fedora Documentation Project CVS repository."
+msgstr "Não use a palavra <wordasword>fedora</wordasword> no nome dos módulos do repositório de CVS do Projecto de Documentação do Fedora."
+d7095 2
+a7096 3
+#: en_US/getting-files.xml:181(title)
+msgid "Correct Module Naming"
+msgstr "Nomenclatura de Módulos Correcta"
+d7098 10
+a7107 3
+#: en_US/getting-files.xml:182(segtitle)
+msgid "Document Name"
+msgstr "Nome do Documento"
+d7109 6
+a7114 3
+#: en_US/getting-files.xml:183(segtitle)
+msgid "CVS Module Name"
+msgstr "Nome do Módulo de CVS"
+d7116 3
+a7118 3
+#: en_US/getting-files.xml:185(seg)
+msgid "Desktop User Guide"
+msgstr "Guia do Utilizador do Ambiente de Trabalho"
+d7120 2
+a7121 3
+#: en_US/getting-files.xml:186(seg)
+msgid "desktop-user-guide"
+msgstr "desktop-user-guide"
+d7123 2
+a7124 3
+#: en_US/getting-files.xml:190(application)
+msgid "Yum"
+msgstr "Yum"
+d7126 2
+a7127 3
+#: en_US/getting-files.xml:189(seg)
+msgid "Software Management with <placeholder-1/>"
+msgstr "Gestão de 'Software' com o <placeholder-1/>"
+d7129 7
+a7135 3
+#: en_US/getting-files.xml:191(seg)
+msgid "yum-guide"
+msgstr "yum-guide"
+d7137 9
+a7145 3
+#: en_US/getting-files.xml:194(application)
+msgid "Pup"
+msgstr "Pup"
+d7147 2
+a7148 3
+#: en_US/getting-files.xml:194(seg)
+msgid "Using <placeholder-1/>"
+msgstr "Usar o <placeholder-1/>"
+d7150 144
+a7293 3
+#: en_US/getting-files.xml:195(seg)
+msgid "pup-tutorial"
+msgstr "pup-tutorial"
+d7295 4
+a7298 3
+#: en_US/getting-files.xml:200(title)
+msgid "File Names"
+msgstr "Nomes dos Ficheiros"
+d7300 2
+a7301 7
+#: en_US/getting-files.xml:201(para)
+msgid ""
+"Follow these guidelines for naming files to make collaboration and document "
+"reuse easy:"
+msgstr ""
+"Siga estas convenções para nomear os ficheiros, de modo a tornar a "
+"colaboração e a reutilização de documentos mais simples:"
+d7303 2
+a7304 7
+#: en_US/getting-files.xml:205(para)
+msgid ""
+"As with module names, avoid using the word <wordasword>fedora</wordasword> "
+"in file names since it is redundant."
+msgstr ""
+"Como no nome dos módulos, evite usar a palavra <wordasword>fedora</"
+"wordasword> nos nomes dos ficheiros, dado que é redundante."
+d7306 2
+a7307 7
+#: en_US/getting-files.xml:210(para)
+msgid ""
+"If the document is comprised of many XML files, avoid repeating the name of "
+"the document when naming the constituent files."
+msgstr ""
+"Se o documento for composto por muitos ficheiros XML, evite repetir o nome "
+"do documento ao criar os ficheiros constituintes."
+d7309 2
+a7310 8
+#: en_US/getting-files.xml:215(para)
+msgid ""
+"Avoid numbering files to show order, since editors and authors often "
+"rearrange documents or reuse their files in other documents."
+msgstr ""
+"Evite numerar os ficheiros para demonstrar a ordem, dado que os editores e "
+"autores normalmente reorganizam os documentos ou reutilizam os seus "
+"ficheiros noutros documentos."
+d7312 2
+a7313 3
+#: en_US/emacs.xml:13(title)
+msgid "Emacs and PSGML Mode"
+msgstr "O Emacs e o Modo PSGML"
+d7315 2
+a7316 3
+#: en_US/emacs.xml:16(primary)
+msgid "PSGML"
+msgstr "PSGML"
+d7318 2
+a7319 7
+#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary)
+#: en_US/emacs.xml:43(primary) en_US/emacs.xml:224(primary)
+#: en_US/emacs.xml:233(primary) en_US/emacs.xml:238(primary)
+#: en_US/emacs.xml:243(primary) en_US/emacs.xml:518(application)
+#: en_US/emacs-nxml.xml:18(primary) en_US/emacs-nxml.xml:22(primary)
+msgid "Emacs"
+msgstr "Emacs"
+d7321 2
+a7322 3
+#: en_US/emacs.xml:25(secondary)
+msgid "PSGML mode"
+msgstr "Modo PSGML"
+d7324 3
+a7326 9
+#: en_US/emacs.xml:28(para)
+msgid ""
+"You can use the PSGML mode available for Emacs to make it easier to write in "
+"XML format. PSGML mode provides syntax-highlighting, tag completion, and "
+"more."
+msgstr ""
+"Poderá usar o modo PSGML, que está disponível para o Emacs, de modo a ser "
+"mais fácil de escrever no formato XML. O modo PSGML oferece o realce de "
+"sintaxe, a completação de marcas, etc."
+d7328 2
+a7329 3
+#: en_US/emacs.xml:35(title)
+msgid "Installing PSGML"
+msgstr "Instalar o PSGML"
+d7331 3
+a7333 3
+#: en_US/emacs.xml:36(para)
+msgid "To install PSGML, use the <command>yum</command> command:"
+msgstr "Para instalar o PSGML, use o comando <command>yum</command>:"
+d7335 2
+a7336 4
+#: en_US/emacs.xml:37(userinput)
+#, no-wrap
+msgid "yum install psgml"
+msgstr "yum install psgml"
+d7338 2
+a7339 3
+#: en_US/emacs.xml:40(title)
+msgid "Setting Up Your <filename>.emacs</filename> File"
+msgstr "Configurar o seu Ficheiro <filename>.emacs</filename>"
+d7341 2
+a7342 3
+#: en_US/emacs.xml:48(filename)
+msgid ".emacs"
+msgstr ".emacs"
+d7344 2
+a7345 11
+#: en_US/emacs.xml:51(para)
+msgid ""
+"For Emacs to parse your DocBook documents correctly, you must have a "
+"<filename>.emacs</filename> file. Cut and paste the following into your "
+"existing <filename>.emacs</filename> file or create a new one that contains "
+"the following lines:"
+msgstr ""
+"Para o Emacs processar correctamente os seus documentos em DocBook, deverá "
+"ter um ficheiro <filename>.emacs</filename>. Corte e cole o seguinte no seu "
+"ficheiro <filename>.emacs</filename> existente ou crie um novo que contenha "
+"as seguintes linhas:"
+d7347 6
+a7352 9
+#: en_US/emacs.xml:181(para)
+msgid ""
+"If you have a wheel mouse and are using Emacs version 21, you can add the "
+"following to your <filename>.emacs</filename> file so your wheel will work "
+"in <application>Emacs</application>:"
+msgstr ""
+"Se tiver um rato com roda e estiver a usar o Emacs versão 21, poderá "
+"adicionar o seguinte ao seu ficheiro <filename>.emacs</filename>, para que a "
+"roda do seu rato funcione no <application>Emacs</application>:"
+d7354 8
+a7361 7
+#: en_US/emacs.xml:192(para)
+msgid ""
+"If you are using the older version 20 of <application>Emacs</application>, "
+"add the following instead:"
+msgstr ""
+"Se estiver a usar a versão anterior - a 20 - do <application>Emacs</"
+"application>, adicione o seguinte comando:"
+d7363 8
+a7370 3
+#: en_US/emacs.xml:221(title)
+msgid "Customizing Emacs"
+msgstr "Personalizar o Emacs"
+d7372 2
+a7373 3
+#: en_US/emacs.xml:225(secondary)
+msgid "customizing"
+msgstr "personalização"
+d7375 6
+a7380 3
+#: en_US/emacs.xml:229(filename)
+msgid ".Xresources"
+msgstr ".Xresources"
+d7382 2
+a7383 3
+#: en_US/emacs.xml:234(secondary)
+msgid "colors"
+msgstr "cores"
+d7385 56
+a7440 3
+#: en_US/emacs.xml:239(secondary)
+msgid "font"
+msgstr "tipo de letra"
+d7442 2
+a7443 3
+#: en_US/emacs.xml:244(secondary)
+msgid "geometry"
+msgstr "geometria"
+d7445 4
+a7448 6
+#: en_US/emacs.xml:247(para)
+msgid ""
+"The colors, font, and geometry (default size of window) for Emacs in your "
+"<filename>~/.Xresources</filename> file. The format for the settings is "
+"<userinput>emacs.keyword:value</userinput>."
+msgstr "As cores, tipos de letra e geometria (tamanho predefinido da janela) do Emacs no seu ficheiro <filename>~/.Xresources</filename>. O formato da configuração é <computeroutput>emacs.palavra-chave:valor</computeroutput>."
+d7450 2
+a7451 3
+#: en_US/emacs.xml:253(para)
+msgid "The following is a sample <filename>~/.Xresources</filename> file."
+msgstr "Segue-se um exemplo de um ficheiro <filename>~/.Xresources</filename>."
+d7453 6
+a7458 7
+#: en_US/emacs.xml:258(para)
+msgid ""
+"If you have other settings in your <filename>~/.Xresources</filename>, add "
+"the following to the end of the file."
+msgstr ""
+"Se tiver outras configurações no seu ficheiro <filename>~/.Xresources</"
+"filename>, adicione o seguinte ao fim do ficheiro."
+d7460 2
+a7461 3
+#: en_US/emacs.xml:270(para)
+msgid "After modifying this file, execute the following command:"
+msgstr "Depois de modificar este ficheiro, execute o seguinte comando:"
+d7463 6
+a7468 3
+#: en_US/emacs.xml:273(command)
+msgid "xrdb -merge ~/.Xresources"
+msgstr "xrdb -merge ~/.Xresources"
+d7470 2
+a7471 3
+#: en_US/emacs.xml:274(para)
+msgid "Then restart <application>Emacs</application> to apply the changes."
+msgstr "Depois reinicie o <application>Emacs</application> para as alterações fazerem efeito."
+d7473 7
+a7479 3
+#: en_US/emacs.xml:395(title)
+msgid "Basic Emacs Commands"
+msgstr "Comandos Básicos do Emacs"
+d7481 6
+a7486 4
+#: en_US/emacs.xml:397(para)
+msgid "The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key."
+msgstr ""
+"A tecla <keycap>Meta</keycap> normalmente é a tecla <keycap>Alt</keycap>."
+d7488 2
+a7489 3
+#: en_US/emacs.xml:403(title)
+msgid "Emacs Commands"
+msgstr "Comandos do Emacs"
+d7491 8
+a7498 3
+#: en_US/emacs.xml:404(segtitle)
+msgid "Shortcut"
+msgstr "Atalho"
+d7500 6
+a7505 5
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:522(keycap)
+msgid "Meta"
+msgstr "Meta"
+d7507 2
+a7508 5
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:493(keycap)
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:509(keycap) en_US/emacs.xml:515(keycap)
+msgid "x"
+msgstr "x"
+d7510 2
+a7511 4
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:494(keycap)
+#: en_US/emacs.xml:499(keycap)
+msgid "Enter"
+msgstr "Enter"
+d7513 6
+a7518 7
+#: en_US/emacs.xml:407(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, "
+"<placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, "
+"<placeholder-3/>"
+d7520 16
+a7535 3
+#: en_US/emacs.xml:410(seg)
+msgid "Parse DTD"
+msgstr "Processar a DTD"
+d7537 2
+a7538 13
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:438(keycap) en_US/emacs.xml:443(keycap)
+#: en_US/emacs.xml:448(keycap) en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:458(keycap) en_US/emacs.xml:463(keycap)
+#: en_US/emacs.xml:468(keycap) en_US/emacs.xml:473(keycap)
+#: en_US/emacs.xml:478(keycap) en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:503(keycap) en_US/emacs.xml:504(keycap)
+#: en_US/emacs.xml:509(keycap) en_US/emacs.xml:510(keycap)
+#: en_US/emacs.xml:515(keycap) en_US/emacs.xml:516(keycap)
+#: en_US/emacs.xml:527(keycap) en_US/emacs.xml:528(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:537(keycap)
+msgid "Ctrl"
+msgstr "Ctrl"
+d7540 2
+a7541 6
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:443(keycap) en_US/emacs.xml:516(keycap)
+#: en_US/emacs.xml:527(keycap) en_US/emacs.xml:535(keycap)
+#: en_US/emacs.xml:537(keycap)
+msgid "c"
+msgstr "C"
+d7543 10
+a7552 3
+#: en_US/emacs.xml:426(keycap) en_US/emacs.xml:432(keycap)
+msgid "Shift"
+msgstr "Shift"
+d7554 2
+a7555 3
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:433(keycap)
+msgid ","
+msgstr ","
+d7557 22
+a7578 3
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:434(keycap)
+msgid "Tab"
+msgstr "Tab"
+d7580 2
+a7581 5
+#: en_US/emacs.xml:425(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+d7583 2
+a7584 3
+#: en_US/emacs.xml:428(seg)
+msgid "Display list of valid tags"
+msgstr "Mostra uma lista com as marcas válidas"
+d7586 6
+a7591 6
+#: en_US/emacs.xml:431(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of "
+"tag, <placeholder-5/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>, escrever o início da marca, <placeholder-5/>"
+d7593 2
+a7594 3
+#: en_US/emacs.xml:435(seg)
+msgid "Complete the tag"
+msgstr "Completa a marca"
+d7596 24
+a7619 3
+#: en_US/emacs.xml:438(keycap)
+msgid "g"
+msgstr "G"
+d7621 2
+a7622 3
+#: en_US/emacs.xml:440(seg)
+msgid "Cancel a command in the minibuffer"
+msgstr "Cancela um comando na mini-linha de comandos"
+d7624 2
+a7625 3
+#: en_US/emacs.xml:444(keycap)
+msgid "/"
+msgstr "/"
+d7627 8
+a7634 4
+#: en_US/emacs.xml:443(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+d7636 11
+a7646 3
+#: en_US/emacs.xml:445(seg)
+msgid "Close tag"
+msgstr "Fecha a marca"
+d7648 2
+a7649 3
+#: en_US/emacs.xml:448(keycap) en_US/emacs.xml:528(keycap)
+msgid "a"
+msgstr "A"
+d7651 7
+a7657 3
+#: en_US/emacs.xml:450(seg)
+msgid "Move cursor to beginning of line"
+msgstr "Move o cursor para o início da linha"
+d7659 6
+a7664 3
+#: en_US/emacs.xml:453(keycap)
+msgid "e"
+msgstr "E"
+d7666 8
+a7673 3
+#: en_US/emacs.xml:455(seg)
+msgid "Move cursor to the end of the line"
+msgstr "Move o cursor para o fim da linha"
+d7675 2
+a7676 3
+#: en_US/emacs.xml:458(keycap)
+msgid "Home"
+msgstr "Home"
+d7678 2
+a7679 3
+#: en_US/emacs.xml:460(seg)
+msgid "Move cursor to the beginning of the file"
+msgstr "Move o cursor para o início do ficheiro"
+d7681 2
+a7682 3
+#: en_US/emacs.xml:463(keycap)
+msgid "End"
+msgstr "End"
+d7684 2
+a7685 3
+#: en_US/emacs.xml:465(seg)
+msgid "Move cursor to the end of the file"
+msgstr "Move o cursor para o fim do ficheiro"
+d7687 2
+a7688 3
+#: en_US/emacs.xml:468(keycap)
+msgid "k"
+msgstr "K"
+d7690 2
+a7691 3
+#: en_US/emacs.xml:470(seg)
+msgid "Cut line"
+msgstr "Corta a linha"
+d7693 8
+a7700 3
+#: en_US/emacs.xml:473(keycap)
+msgid "y"
+msgstr "Y"
+d7702 18
+a7719 3
+#: en_US/emacs.xml:475(seg)
+msgid "Paste line"
+msgstr "Cola a linha"
+d7721 6
+a7726 3
+#: en_US/emacs.xml:478(keycap) en_US/emacs.xml:510(keycap)
+msgid "s"
+msgstr "S"
+d7728 23
+a7750 3
+#: en_US/emacs.xml:480(seg)
+msgid "Search forward in the file"
+msgstr "Procura para a frente no ficheiro"
+d7752 8
+a7759 3
+#: en_US/emacs.xml:483(keycap)
+msgid "r"
+msgstr "R"
+d7761 2
+a7762 3
+#: en_US/emacs.xml:485(seg)
+msgid "Search backwards in the file"
+msgstr "Procura para trás no ficheiro"
+d7764 8
+a7771 3
+#: en_US/emacs.xml:488(keycap)
+msgid "$"
+msgstr "$"
+d7773 13
+a7785 3
+#: en_US/emacs.xml:490(seg) en_US/emacs.xml:495(seg)
+msgid "Check spelling of current word"
+msgstr "Verifica a ortografia da palavra actual"
+d7787 6
+a7792 7
+#: en_US/emacs.xml:493(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, "
+"<placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, "
+"<placeholder-3/>"
+d7794 2
+a7795 7
+#: en_US/emacs.xml:498(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, "
+"<placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, "
+"<placeholder-3/>"
+d7797 9
+a7805 3
+#: en_US/emacs.xml:500(seg)
+msgid "Check spelling of current buffer"
+msgstr "Verifica a ortografia da página actual"
+d7807 2
+a7808 3
+#: en_US/emacs.xml:504(keycap)
+msgid "f"
+msgstr "F"
+d7810 8
+a7817 8
+#: en_US/emacs.xml:503(seg) en_US/emacs.xml:509(seg) en_US/emacs.xml:515(seg)
+#: en_US/emacs.xml:527(seg) en_US/emacs.xml:535(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+d7819 6
+a7824 3
+#: en_US/emacs.xml:506(seg)
+msgid "Open file"
+msgstr "Abrir um ficheiro"
+d7826 8
+a7833 3
+#: en_US/emacs.xml:512(seg)
+msgid "Save file"
+msgstr "Gravar um ficheiro"
+d7835 2
+a7836 3
+#: en_US/emacs.xml:518(seg)
+msgid "Exit <placeholder-1/> and prompt to save files if necessary"
+msgstr "Sai do <placeholder-1/> e pede para gravar os ficheiros, se necessário"
+d7838 2
+a7839 3
+#: en_US/emacs.xml:522(keycap)
+msgid "q"
+msgstr "Q"
+d7841 6
+a7846 3
+#: en_US/emacs.xml:524(seg)
+msgid "Fill paragraph"
+msgstr "Preenche o parágrafo"
+d7848 15
+a7862 4
+#: en_US/emacs.xml:531(computeroutput)
+#, no-wrap
+msgid "url"
+msgstr "url"
+d7864 14
+a7877 7
+#: en_US/emacs.xml:530(seg)
+msgid ""
+"Edit attributes for a tag (for example, you can edit the <placeholder-1/> "
+"attribute of the <placeholder-2/> tag)"
+msgstr ""
+"Edita os atributos de uma marca (por exemplo, poderá editar o atributo "
+"<placeholder-1/> da marca <placeholder-2/>)"
+d7879 17
+a7895 3
+#: en_US/emacs.xml:539(seg)
+msgid "Exit edit attributes"
+msgstr "Sair da edição de atributos"
+d7897 12
+a7908 3
+#: en_US/emacs.xml:545(title) en_US/emacs-nxml.xml:77(title)
+msgid "Examples"
+msgstr "Exemplos"
+d7910 2
+a7911 8
+#: en_US/emacs.xml:547(para)
+msgid ""
+"The table or reference card of Emacs and PSGML commands can be confusing for "
+"beginners. This section provides some examples of how to use them."
+msgstr ""
+"A tabela ou cartão de referência dos comandos do Emacs e do PSGML poderão "
+"ser confusos para os principiantes. Esta secção oferece alguns exemplos de "
+"utilização dos mesmos."
+d7913 11
+a7923 3
+#: en_US/emacs.xml:554(title)
+msgid "Tag Completion"
+msgstr "Completação de Marcas"
+d7925 8
+a7932 3
+#: en_US/emacs.xml:558(para)
+msgid "This section assumes that you have already parsed the DTD file."
+msgstr "Esta secção assume que você já carregou o ficheiro da DTD."
+d7934 2
+a7935 11
+#: en_US/emacs.xml:562(para)
+msgid ""
+"To avoid having to type a tag repeatedly, use the key combination "
+"<keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. "
+"At the bottom of the <application>Emacs</application> window, the following "
+"prompt appears:"
+msgstr ""
+"Em vez de escrever uma marca sempre que necessitar de a usar, use a "
+"combinação de teclas <keycap>Ctrl</keycap>-<keycap>C</keycap>, seguida do "
+"<keycap><</keycap>. No fundo da janela do <application>Emacs</"
+"application>, irá ver:"
+d7937 30
+a7966 3
+#: en_US/emacs.xml:569(prompt)
+msgid "Tag: <"
+msgstr "Marca: <"
+d7968 2
+a7969 13
+#: en_US/emacs.xml:571(para)
+msgid ""
+"To view a list of available tags, use either the <keycap>Tab</keycap> or "
+"<keycap>?</keycap>. If you know the first few letters of a tag, enter them, "
+"followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, "
+"that tag appears. If more than one completion exists, a complete list of "
+"possible tags appears."
+msgstr ""
+"Para ver uma lista com as marcas disponíveis, use as teclas <keycap>Tab</"
+"keycap> ou <keycap>?</keycap>. Por outro lado, se souber as primeiras letras "
+"de uma marca, podê-las-á introduzir e carregar de seguida em <keycap>Tab</"
+"keycap> para obter uma lista completa das marcas disponíveis que começam por "
+"essas letras ou para completar a marca."
+d7971 2
+a7972 6
+#: en_US/emacs.xml:580(para)
+msgid ""
+"If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, "
+"<keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the "
+"example below:"
+msgstr "Se carregar em <keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo>, <keycap><</keycap>, <keycap>K</keycap>, irá aparecer uma linha de comandos semelhante ao exemplo abaixo:"
+d7974 2
+a7975 3
+#: en_US/emacs.xml:597(title)
+msgid "Tag Closure"
+msgstr "Fecho de Marcas"
+d7977 34
+a8010 11
+#: en_US/emacs.xml:599(para)
+msgid ""
+"After you open a tag, you must close it. The easiest way to close an open "
+"tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</"
+"keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most "
+"recently opened tag."
+msgstr ""
+"Logo que tenha iniciado a marca que escolheu, terá de a fechar. A forma mais "
+"simples de fechar uma marca é usar a combinação de teclas <keycap>Ctrl</"
+"keycap>-<keycap>C</keycap>, seguida de <keycap>/</keycap>. Esta irá fechar a "
+"marca aberta mais próxima que tiver."
+d8012 2
+a8013 3
+#: en_US/emacs.xml:611(title)
+msgid "Other Emacs Tasks"
+msgstr "Outras Tarefas do Emacs"
+d8015 2
+a8016 3
+#: en_US/emacs.xml:614(title)
+msgid "Working with One Window"
+msgstr "Lidar com uma Janela"
+d8018 2
+a8019 7
+#: en_US/emacs.xml:615(para)
+msgid ""
+"Sometimes in <application>Emacs</application>, the window becomes split, "
+"with tags completions or other text in an alternate window. To return to a "
+"single window, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+msgstr "Algumas vezes no <application>Emacs</application>, a janela vai ficando dividida (com as completações de marcas ou outro texto na janela inferior). A forma mais simples de voltar atrás, para que apenas o seu XML e o texto apareçam num ecrã, é usar a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>1</keycap>."
+d8021 2
+a8022 3
+#: en_US/emacs.xml:625(title)
+msgid "Saving Work"
+msgstr "Gravar o Trabalho"
+d8024 6
+a8029 6
+#: en_US/emacs.xml:626(para)
+msgid ""
+"To save your work, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>s</keycap></keycombo>."
+msgstr "Para gravar o seu trabalho, use a seguinte combinação de teclas, <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>Ctrl</keycap>-<keycap>S</keycap>."
+d8031 18
+a8048 3
+#: en_US/emacs.xml:637(title)
+msgid "The \"Clear/Quit\" Command"
+msgstr "O Comando \"Limpar/Sair\""
+d8050 2
+a8051 11
+#: en_US/emacs.xml:638(para)
+msgid ""
+"If the tag completion process becomes unwieldy or confusing, use the "
+"keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to "
+"exit back to the text. <application>Emacs</application> clears any prompts "
+"and returns to the buffer text."
+msgstr ""
+"Se o processo de completação de marcas se tornar incomportável ou confuso, "
+"use a sequência de teclas <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></"
+"keycombo> para voltar para o texto. O <application>Emacs</application> limpa "
+"todas as linhas de comando e volta para o texto."
+d8053 2
+a8054 3
+#: en_US/emacs.xml:648(title)
+msgid "Opening a new file"
+msgstr "Abrir um ficheiro novo"
+d8056 20
+a8075 8
+#: en_US/emacs.xml:649(para)
+msgid ""
+"To open a new file, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the "
+"<application>Emacs</application> window. Enter the file name, using "
+"<keycap>Tab</keycap> completion if desired, of the file you wish to open."
+msgstr "Para abrir um novo ficheiro, use a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>Ctrl</keycap>-<keycap>F</keycap>. No fundo da janela do Emacs, será capaz de indicar o nome do ficheiro (usando a completação do <keycap>Tab</keycap> se necessário) do ficheiro que deseja abrir."
+d8077 3
+a8079 3
+#: en_US/emacs.xml:663(title)
+msgid "Closing <application>Emacs</application>"
+msgstr "Fechar o <application>Emacs</application>"
+d8081 2
+a8082 8
+#: en_US/emacs.xml:664(para)
+msgid ""
+"To close <application>Emacs</application> use the key sequence "
+"<keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, "
+"<keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have "
+"not saved your work, <application>Emacs</application> prompts you to save "
+"any changed files."
+msgstr "Para fechar o <application>emacs</application>, use a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap> seguida de <keycap>Ctrl</keycap>-<keycap>C</keycap>. Se não tiver gravado o seu trabalho, será questionado pelo <application>Emacs</application> para gravar os ficheiros alterados."
+d8084 6
+a8089 3
+#: en_US/emacs.xml:682(title) en_US/emacs-nxml.xml:127(title)
+msgid "Additional Resources"
+msgstr "Recursos Adicionais"
+d8091 8
+a8098 7
+#: en_US/emacs.xml:684(para)
+msgid ""
+"Additional Emacs and PSGML references are available at the following "
+"locations:"
+msgstr ""
+"As referências adicionais ao Emacs e ao PSGML estão disponíveis nas "
+"seguintes localizações:"
+d8100 2
+a8101 3
+#: en_US/emacs.xml:692(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+msgid "Emacs Quick Reference Guide"
+msgstr "Guia de Referência Rápido do Emacs"
+d8103 2
+a8104 6
+#: en_US/emacs.xml:696(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+msgstr "Um cartão de referência do Emacs que vem com o pacote <filename>emacs</filename>. Poderá imprimi-lo como referência. —<filename>/usr/share/emacs/<replaceable>versão</replaceable>/etc/refcard.ps</filename>"
+d8106 16
+a8121 5
+#: en_US/emacs.xml:703(para)
+msgid ""
+"Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/"
+"usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+msgstr "Leia o <citetitle>Editing XML with Emacs and PSGML</citetitle> no ficheiro <filename>/usr/share/doc/psgml-<replaceable>versão</replaceable>/psgml.ps</filename>."
+d8123 52
+a8174 6
+#: en_US/emacs.xml:709(para)
+msgid ""
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—"
+"<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of "
+"Emacs commands for PSGML mode."
+msgstr "O <ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—<citetitle>Emacs/PSGML Quick Reference</citetitle> é uma tabela de referência dos comandos do Emacs para o modo do PSGML."
+d8176 6
+a8181 3
+#: en_US/emacs.xml:718(citetitle)
+msgid "PSGML Tricks"
+msgstr "Truques do PSGML"
+d8183 28
+a8210 3
+#: en_US/emacs-nxml.xml:11(title)
+msgid "Emacs and nXML Mode"
+msgstr "O Emacs e o Modo nXML"
+d8212 2
+a8213 3
+#: en_US/emacs-nxml.xml:14(primary) en_US/emacs-nxml.xml:51(primary)
+msgid "nXML"
+msgstr "nXML"
+d8215 2
+a8216 3
+#: en_US/emacs-nxml.xml:23(secondary)
+msgid "nXML mode"
+msgstr "modo nXML"
+d8218 6
+a8223 13
+#: en_US/emacs-nxml.xml:26(para)
+msgid ""
+"You can also use the nXML mode available for <application>Emacs</"
+"application> to make it even easier to write in DocBook XML format. nXML "
+"mode provides context-sensitive editing using completion, real time validity "
+"error checking, syntax highlighting and indentation. All you need to do is "
+"install an RPM!!"
+msgstr ""
+"Também poderá usar o modo nXML que está disponível para o "
+"<application>Emacs</application>, de modo a ser ainda mais simples escrever "
+"no formato DocBook em XML. O modo nXML oferece uma edição sensível ao "
+"contexto com a completação, validação dos erros em tempo-real, realce de "
+"sintaxe e indentação. Tudo o que necessita é instalar um RPM!!"
+d8225 2
+a8226 3
+#: en_US/emacs-nxml.xml:35(title)
+msgid "Early stages"
+msgstr "Etapas iniciais"
+d8228 2
+a8229 14
+#: en_US/emacs-nxml.xml:36(para)
+msgid ""
+"Please be aware the nxml-mode for <application>Emacs</application> is quite "
+"new, so there are a few things that the advanced user might notice when "
+"using it with other documents types. If you keep an eye on the mailing-list, "
+"you can keep up to date with these, as well as ask questions. For more "
+"details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr ""
+"Tenha em atenção que o 'nxml-mode' do <application>Emacs</application> é "
+"relativamente novo, pelo que existem algumas coisas que o utilizador mais "
+"avançado poderá notar ao usá-lo com outros tipos de documentos. Se mantiver "
+"uma vista de olhos na lista de correio, poder-se-á manter actualizado com as "
+"mesmas, assim como poderá fazer perguntas. Para mais detalhes, veja a secção "
+"<xref linkend=\"sn-emacs-nxml-readme\"/>."
+d8231 6
+a8236 3
+#: en_US/emacs-nxml.xml:48(title)
+msgid "Getting the nXML RPM"
+msgstr "Obter o RPM do nXML"
+d8238 2
+a8239 3
+#: en_US/emacs-nxml.xml:52(secondary)
+msgid "RPM"
+msgstr "RPM"
+d8241 6
+a8246 3
+#: en_US/emacs-nxml.xml:56(primary)
+msgid "nXML RPM"
+msgstr "RPM do nXML"
+d8248 2
+a8249 15
+#: en_US/emacs-nxml.xml:59(para)
+msgid ""
+"To use nXML mode with emacs, you will need to install the nXML RPM available "
+"from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/"
+"\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www."
+"thaiopensource.com/download/\">http://www.thaiopensource.com/download/</"
+"ulink>. The source requires a lot more work to setup, therefore we will only "
+"be concentrating on the RPM version."
+msgstr ""
+"Para usar o modo nXML com o emacs, terá de instalar o pacote RPM nXML na "
+"<ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/\">página "
+"do Tim Waugh</ulink> ou o código-fonte de <ulink url=\"http://www."
+"thaiopensource.com/download/\">http://www.thaiopensource.com/download/</"
+"ulink>. O código necessita de bastante mais trabalho de configuração; como "
+"tal, concentrar-nos-emos na versão em RPM."
+d8251 4
+a8254 7
+#: en_US/emacs-nxml.xml:69(para)
+msgid ""
+"Information on where to get the source is available in <xref linkend=\"sn-"
+"emacs-additional-resources\"/>."
+msgstr ""
+"As informações de disponibilização do código estão disponíveis em <xref "
+"linkend=\"sn-emacs-additional-resources\"/>."
+d8256 2
+a8257 10
+#: en_US/emacs-nxml.xml:79(para)
+msgid ""
+"Compared to PSGML mode there are only couple of commands that you need. This "
+"speeds up writing with <application>Emacs</application> considerably, which "
+"means you can concentrate more on the content of your article."
+msgstr ""
+"Em comparação com o modo PSGML, só existem alguns comandos que você "
+"necessita. Isto acelera a escrita no <application>Emacs</application> "
+"consideravelmente, o que significa que se poderá concentrar mais no conteúdo "
+"do seu artigo."
+d8259 16
+a8274 11
+#: en_US/emacs-nxml.xml:88(para)
+msgid ""
+"To create a tag, type <userinput><</userinput> and then type the keyword. "
+"To complete the keyword, press <command>Ctrl-Ret</command>, then add the "
+"last <userinput>></userinput>. To close a tag, type <userinput></</"
+"userinput>."
+msgstr ""
+"Para criar uma marca, escreva <userinput><</userinput> e escreva depois a "
+"palavra-chave. Para completar a mesma, carregue em <command>Ctrl-Ret</"
+"command>, adicionando depois a última <userinput>></userinput>. Para "
+"fechar uma marca, escreva <userinput></</userinput>."
+d8276 2
+a8277 9
+#: en_US/emacs-nxml.xml:97(para)
+msgid ""
+"When you open a document that doesn't have a DOCTYPE declaration at the top "
+"of the file, you will get this message and tag completion won't work because "
+"nXML will not know what format you are writing."
+msgstr ""
+"Quando abrir um documento que não tenha uma declaração DOCTYPE no topo do "
+"ficheiro, irá obter esta mensagem e a completação de marcas não irá "
+"funcionar, porque o nXML não irá saber em que formato está a escrever."
+d8279 2
+a8280 13
+#: en_US/emacs-nxml.xml:104(para)
+msgid ""
+"To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</"
+"command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/"
+"schema/</filename> and load <filename>docbook.rnc</filename>. "
+"<application>Emacs</application> will then prompt you to save it in the "
+"current working directory."
+msgstr ""
+"Para carregar o esquema, escreva <command>Ctrl-C</command> e <command>Ctrl-"
+"S</command>, indo depois à pasta <filename>/usr/share/emacs/site-lisp/nxml-"
+"mode/schema/</filename> e carregando o <filename>docbook.rnc</filename>. O "
+"<application>Emacs</application> perguntar-lhe-á então para gravar a pasta "
+"de trabalho actual."
+d8282 6
+a8287 11
+#: en_US/emacs-nxml.xml:115(para)
+msgid ""
+"The commands already discussed are the only differences between using "
+"<application>Emacs</application> with PSGML mode and <application>Emacs</"
+"application> with nXML mode. You will still need to use all the same "
+"commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr ""
+"Os comandos já discutidos são as únicas diferenças entre a utilização do "
+"<application>Emacs</application> com o modo PSGML e o <application>Emacs</"
+"application> com o modo nXML. Terá à mesma de usar todos os mesmos comandos "
+"que foram discutidos em <xref linkend=\"sn-emacs-basic-commands\"/>."
+d8289 3
+a8291 7
+#: en_US/emacs-nxml.xml:129(para)
+msgid ""
+"Additional Emacs and nXML references are available at the following "
+"locations:"
+msgstr ""
+"As referências adicionais do Emacs e do nXML estão disponíveis nos seguintes "
+"locais:"
+d8293 125
+a8417 3
+#: en_US/emacs-nxml.xml:136(ulink)
+msgid "http://www.thaiopensource.com/download/"
+msgstr "http://www.thaiopensource.com/download/"
+d8419 2
+a8420 3
+#: en_US/emacs-nxml.xml:137(citetitle)
+msgid "Author's download area"
+msgstr "Área de transferências do autor"
+d8422 2
+a8423 3
+#: en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+d8425 2
+a8426 9
+#: en_US/emacs-nxml.xml:147(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+"Um cartão de referência do Emacs que vem com o pacote <filename>emacs</"
+"filename>. Poderá imprimi-lo como referência. —<filename>/usr/share/"
+"emacs/<replaceable><versão></replaceable>/etc/refcard.ps</filename>"
+d8428 9
+a8436 3
+#: en_US/emacs-nxml.xml:157(title)
+msgid "nXML README File"
+msgstr "Ficheiro README do nXML"
+d8438 6
+a8443 9
+#: en_US/emacs-nxml.xml:161(para)
+msgid ""
+"This file can be found in the directory you extracted the source into, or in "
+"<filename>/usr/share/doc/nxml-mode-<replaceable><version></"
+"replaceable>/</filename> if you installed the RPM."
+msgstr ""
+"Este ficheiro poderá ser encontrado na pasta para onde extraiu o código ou "
+"em <filename>/usr/share/doc/nxml-mode-<replaceable><versão></"
+"replaceable>/</filename>, se instalou o RPM."
+d8445 6
+a8450 3
+#: en_US/emacs-nxml.xml:169(para)
+msgid "README file:"
+msgstr "Ficheiro README:"
+d8452 123
+a8574 10
+#: en_US/emacs-nxml.xml:171(para)
+msgid ""
+"This is a new major mode for GNU Emacs for editing XML documents. It "
+"supports editing well-formed XML documents and also provides schema-"
+"sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr ""
+"Este é um novo modo principal para o GNU Emacs editar documentos em XML. "
+"Este suporta a edição de documentos válidos em XML, oferecendo também a "
+"edição sensível ao esquema dos documentos em XML, usando a Sintaxe Compacta "
+"do RELAX NG."
+d8576 8
+a8583 9
+#: en_US/emacs-nxml.xml:177(para)
+msgid ""
+"To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs "
+"version 20 will not work properly, nor will XEmacs. To get started, do the "
+"following:"
+msgstr ""
+"Para usar isto, terá de ter o GNU Emacs versão 21.x, de preferência a 21.3. "
+"O GNU Emacs versão 20 não irá funcionar correctamente, assim como o XEmacs. "
+"Para começar, faça o seguinte:"
+d8585 2
+a8586 3
+#: en_US/emacs-nxml.xml:184(command)
+msgid "M-x load-file RET rng-auto.el RET"
+msgstr "M-x load-file RET rng-auto.el RET"
+d8588 2
+a8589 7
+#: en_US/emacs-nxml.xml:187(para)
+msgid ""
+"This defines the necessary autoloads. Now, visit a file containing an XML "
+"document, and do the following:"
+msgstr ""
+"Isto define todos os carregamentos automáticos necessários. Depois, vá a um "
+"ficheiro que contenha um documento em XML, fazendo o seguinte:"
+d8591 2
+a8592 3
+#: en_US/emacs-nxml.xml:192(command)
+msgid "M-x nxml-mode"
+msgstr "M-x nxml-mode"
+d8594 2
+a8595 3
+#: en_US/emacs-nxml.xml:195(para)
+msgid "Now do"
+msgstr "Agora faça"
+d8597 2
+a8598 3
+#: en_US/emacs-nxml.xml:200(command)
+msgid "C-h m"
+msgstr "C-H m"
+d8600 2
+a8601 7
+#: en_US/emacs-nxml.xml:203(para)
+msgid ""
+"For information on how to use nxml-mode. The beginnings of a manual are in "
+"nxml-mode.info. You can read this using:"
+msgstr ""
+"Para mais informações sobre a utilização do nxml-mode. As introduções do "
+"manual estão no ficheiro 'nxml-mode.info'. Podê-lo-á ler com:"
+d8603 2
+a8604 3
+#: en_US/emacs-nxml.xml:209(command)
+msgid "C-u M-x info RET nxml-mode.info RET"
+msgstr "C-u M-x info RET nxml-mode.info RET"
+d8606 8
+a8613 7
+#: en_US/emacs-nxml.xml:212(para)
+msgid ""
+"It's also installed as an entry at the end of the top-level info directory. "
+"So you can read it with <command>C-h i</command> as usual."
+msgstr ""
+"Também está instalado como um elemento no fim da pasta de topo do 'info'. "
+"Como tal, poderá lê-la com o <command>C-H I</command>, como de costume."
+d8615 2
+a8616 8
+#: en_US/emacs-nxml.xml:217(para)
+msgid ""
+"You can use <filename>test.valid.xml</filename> and <filename>test.invalid."
+"xml</filename> as examples of valid and invalid XML documents."
+msgstr ""
+"Poderá usar os ficheiros <filename>test.valid.xml</filename> e "
+"<filename>test.invalid.xml</filename> como exemplos de documentos em XML "
+"válidos e inválidos."
+d8618 2
+a8619 5
+#: en_US/emacs-nxml.xml:223(para)
+msgid "To get things automatically loaded each time you start Emacs, add:"
+msgstr ""
+"Para que as coisas sejam carregadas automaticamente de cada vez que iniciar "
+"o Emacs, adicione:"
+d8621 6
+a8626 8
+#: en_US/emacs-nxml.xml:228(computeroutput)
+#, no-wrap
+msgid ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+msgstr ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+d8628 2
+a8629 16
+#: en_US/emacs-nxml.xml:232(para)
+msgid ""
+"to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-"
+"200YMMDD</computeroutput> is the directory containing the <filename>.elc</"
+"filename> files. Note that <filename>rng-auto.el</filename> does not load "
+"all of the nxml-mode code; it merely sets things up so that all the features "
+"of nxml-mode will be autoloaded properly. You should not try to autoload "
+"<filename>rng-auto.el</filename> itself."
+msgstr ""
+"ao seu ficheiro <filename>.emacs</filename>, onde o <computeroutput>~/nxml-"
+"mode-200AMMDD</computeroutput> é a pasta que contém os ficheiros <filename>."
+"elc</filename>. Lembre-se que o <filename>rng-auto.el</filename> não carrega "
+"tudo do modo 'nxml-mode'; simplesmente configura as coisas, para que as "
+"funcionalidades do 'nxml-mode' sejam carregadas automaticamente. Não deverá "
+"tentar carregar automaticamente o <filename>rng-auto.el</filename> "
+"propriamente dito."
+d8631 2
+a8632 11
+#: en_US/emacs-nxml.xml:242(para)
+msgid ""
+"To use nxml-mode automatically for files with an extension of <filename>xml</"
+"filename>, <filename>xsl</filename>, <filename>rng</filename> or "
+"<filename>xhtml</filename>, add the following to your <filename>.emacs</"
+"filename> file:"
+msgstr ""
+"Para usar o 'nxml-mode' automaticamente para os ficheiros com as extensões "
+"<filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> "
+"ou <filename>xhtml</filename>, adicione o seguinte ao seu ficheiro "
+"<filename>.emacs</filename>:"
+d8634 4
+a8637 10
+#: en_US/emacs-nxml.xml:250(computeroutput)
+#, no-wrap
+msgid ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+msgstr ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+d8639 2
+a8640 11
+#: en_US/emacs-nxml.xml:255(para)
+msgid ""
+"If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are "
+"running Emacs 21.3 or later, then I recommend enabling unify-8859-on-"
+"decoding-mode, by adding the following to your <filename>.emacs</filename> "
+"file:"
+msgstr ""
+"Se editar o XML com as codificações iso-8859-N em vez da iso-8859-1 e "
+"estiver a usar o Emacs 21.3 ou posterior, recomenda-se que active o 'unify-"
+"8859-on-decoding-mode', adicionando a seguinte sequência ao seu ficheiro "
+"<filename>.emacs</filename>:"
+d8642 11
+a8652 4
+#: en_US/emacs-nxml.xml:263(computeroutput)
+#, no-wrap
+msgid "(unify-8859-on-decoding-mode)"
+msgstr "(unify-8859-on-decoding-mode)"
+d8654 6
+a8659 9
+#: en_US/emacs-nxml.xml:266(para)
+msgid ""
+"To get validation and schema-sensitive editing, you need a RELAX NG Compact "
+"Syntax (RNC) schema for you document. The schema directory includes some "
+"schemas for popular document types."
+msgstr ""
+"Para ter uma validação e edição sensível ao esquema, precisa de um esquema "
+"de Sintaxe Compacta do Relax NG (RNC) do seu documento. A pasta do esquema "
+"inclui alguns esquemas para os tipos de documentos mais conhecidos."
+d8661 14
+a8674 7
+#: en_US/emacs-nxml.xml:272(para)
+msgid ""
+"For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://"
+"relaxng.org/</ulink>."
+msgstr ""
+"Para mais informações sobre o RELAX NG, consulte a página <ulink url="
+"\"http://relaxng.org/\">http://relaxng.org/</ulink>."
+d8676 2
+a8677 9
+#: en_US/emacs-nxml.xml:277(para)
+msgid ""
+"For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://"
+"relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial."
+"html</ulink>"
+msgstr ""
+"Para um tutorial sobre a Sintaxe Compacta do RELAX NG, veja a página <ulink "
+"url=\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-"
+"tutorial.html</ulink>"
+d8679 6
+a8684 9
+#: en_US/emacs-nxml.xml:282(para)
+msgid ""
+"For automatically creating RNC schemas, I recommend my Trang program: <ulink "
+"url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee."
+"thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr ""
+"Para criar automaticamente os esquemas RNG, recomenda-se o programa Trang: "
+"<ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee."
+"thaiopensource.com/relaxng/trang.html\"</ulink>"
+d8686 10
+a8695 3
+#: en_US/emacs-nxml.xml:293(para)
+msgid "Infer an RNC schema from an instance document"
+msgstr "Inferir um esquema de RNC a partir do documento de uma instância"
+d8697 2
+a8698 3
+#: en_US/emacs-nxml.xml:298(para)
+msgid "Convert a DTD to an RNC schema"
+msgstr "Converter uma DTD para um esquema RNC"
+d8700 2
+a8701 3
+#: en_US/emacs-nxml.xml:303(para)
+msgid "Convert a RELAX NG XML syntax schema to an RNC schema"
+msgstr "Converter um esquema de sintaxe do XML em Relax NG para um esquema RNC"
+d8703 4
+a8706 3
+#: en_US/emacs-nxml.xml:288(para)
+msgid "You can use this to <placeholder-1/>"
+msgstr "Poderá usar isto para <placeholder-1/>"
+d8708 13
+a8720 10
+#: en_US/emacs-nxml.xml:310(para)
+msgid ""
+"To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also "
+"use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html"
+"\">http://www.pantor.com/download.html\"</ulink>."
+msgstr ""
+"Para converter um esquema de sintaxe em XML do RELAX NG (.rng) para um "
+"esquema RNC, poderá também usar a folha de estilo XSLT em <ulink url="
+"\"http://www.pantor.com/download.html\">http://www.pantor.com/download.html"
+"\"</ulink>."
+d8722 9
+a8730 11
+#: en_US/emacs-nxml.xml:316(para)
+msgid ""
+"To convert a W3C XML Schema to an RNC schema, you need first to convert it "
+"to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on "
+"top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www."
+"dev.java.net/</ulink>."
+msgstr ""
+"Para converter um Esquema de XML da W3C num esquema RNC, terá primeiro de o "
+"converter para a sintaxe XML do RELAX NG, usando a ferramenta de conversão "
+"para RELAX NG da Sun, a 'rngconv' (assente sobre o MSV). Veja em <ulink url="
+"\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+d8732 10
+a8741 3
+#: en_US/emacs-nxml.xml:323(para)
+msgid "The file <filename>NEWS</filename> describes recent changes."
+msgstr "O ficheiro <filename>NEWS</filename> descreve as alterações recentes."
+d8743 2
+a8744 10
+#: en_US/emacs-nxml.xml:327(para)
+msgid ""
+"Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-"
+"mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug "
+"reports, discussion. I will announce all new versions there."
+msgstr ""
+"Use por favor a lista <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-"
+"mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> para os "
+"relatórios de erros, discussão, etc. Serão aí anunciadas todas as versões "
+"novas."
+d8746 7
+a8752 3
+#: en_US/emacs-nxml.xml:333(para)
+msgid "James Clark"
+msgstr "James Clark"
+d8754 12
+a8765 3
+#: en_US/emacs-nxml.xml:336(para)
+msgid "jjc@@thaiopensource.com"
+msgstr "jjc@@thaiopensource.com"
+d8767 12
+a8778 3
+#: en_US/acknowledgments.xml:11(title)
+msgid "Acknowledgments"
+msgstr "Agradecimentos"
+d8780 8
+a8787 9
+#: en_US/acknowledgments.xml:13(para)
+msgid ""
+"This document is based on a document started by Tammy Fox (tfox at redhat."
+"com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray "
+"Fuller (jrfuller at redhat.com)."
+msgstr ""
+"Este documento baseia-se num documento iniciado por Tammy Fox (tfox at "
+"redhat.com) e com contribuições de Sandra Moore (smoore at redhat.com) e "
+"Johnray Fuller (jrfuller at redhat.com)."
+d8789 7
+a8795 8
+#: en_US/acknowledgments.xml:19(para)
+msgid ""
+"A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to "
+"fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr ""
+"Uma correcção do Roozbeh Pournader (roozbeh at sharif.edu) foi aplicada para "
+"corrigir alguns erros ortográficos e explicar que o CVS anónimo não permite "
+"o envio de novas versões."
+d8797 10
+a8806 9
+#: en_US/acknowledgments.xml:25(para)
+msgid ""
+"Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to "
+"add the trailing slashes to the <command>figure</command> tag example in "
+"<filename>docs-xml-tags.xml</filename>."
+msgstr ""
+"Foram aplicadas correcções de Gavin Henry (ghenry at suretecsystems.com) par "
+"adicionar as barras finais ao exemplo da marca <command>figure</command>, "
+"como aparece em <filename>docs-xml-tags.xml</filename>."
+d8808 2
+a8809 7
+#: en_US/acknowledgments.xml:32(para)
+msgid ""
+"A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been "
+"applied to add <xref linkend=\"ch-vim\"/>."
+msgstr ""
+"Uma actualização do Joshua Daniel Franklin (joshuadfranklin at yahoo.com) "
+"para adicionar o <xref linkend=\"ch-vim\"/>."
+d8811 6
+a8816 6
+#: en_US/acknowledgments.xml:37(para)
+msgid ""
+"A patch from Karsten Wade (kwade at redhat.com) has been applied to add "
+"<xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields "
+"(stickster at gmail.com)."
+msgstr "Uma correcção de Karsten Wade (kwade at redhat.com) foi aplicada para adicionar o <xref linkend=\"sn-screenshots\"/>. Foi editada por Paul W. Frields (stickster at gmail.com)."
+d8818 6
+a8823 6
+#: en_US/acknowledgments.xml:43(para)
+msgid ""
+"A patch from Paul W. Frields (stickster at gmail.com) has been applied to "
+"add more explanation of the <command>screen</command> tag set to <xref "
+"linkend=\"sn-xml-tags-screen\"/>."
+msgstr "Uma correcção de Paul W. Frields (stickster at hotmail.com) foi aplicada para adicionar mais explicações sobre o conjunto de marcas <command>screen</command> em <xref linkend=\"sn-xml-tags-screen\"/>."
+d8825 10
+a8834 8
+#: en_US/acknowledgments.xml:49(para)
+msgid ""
+"A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been "
+"applied to more fully explaing the document building system."
+msgstr ""
+"Uma correcção de Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) foi "
+"aplicada para descrever com maior pormenor o sistema de compilação de "
+"documentos."
+d8836 6
+a8841 4
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: en_US/acknowledgments.xml:0(None)
+msgid "translator-credits"
+msgstr "José Nuno Pires <jncp@@netcabo.pt>, 2006."
+@
+
+
+1.14
+log
+ at Finished changes on RH translations and docs
+@
+text
+ at d5 1
+a5 1
+"PO-Revision-Date: 2007-07-21 15:41+0100\n"
+d12 29
+a40 58
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu "
+"guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires "
+"VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend "
+"autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert "
+"articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap "
+"dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML "
+"tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man "
+"sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot "
+"developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro "
+"keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC "
+"configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG "
+"Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule "
+"Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote "
+"eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest "
+"Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text "
+"jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd "
+"colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES "
+"set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray "
+"ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG "
+"PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar "
+"Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse "
+"cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo "
+"imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject "
+"Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference "
+"rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef "
+"authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done "
+"Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered "
+"nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead "
+"Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas "
+"Redundâncias update yahoo VIMRUNTIME generated important \n"
+d48 3
+a50 1
+"X-POFile-SpellExtra: pfrields parent\n"
+d455 1
+a455 1
+"<!--$Id: xml-tags.xml,v 1.6 2007/06/23 05:25:29 pfrields Exp $ -->\n"
+d466 1
+a466 1
+"<!--$Id: pt.po,v 1.13 2007/07/19 23:55:10 zepires Exp $ -->\n"
+d6713 1
+a6713 9
+msgstr ""
+"Se precisar, poderá dimensionar a imagem com o <application>The GIMP</"
+"application>. Com a imagem aberta, carregue com o botão direito nesta e "
+"escolha a opção <guimenu>Imagem</guimenu> -> <guimenuitem>Escalar a "
+"Imagem...</guimenuitem>. Com o símbolo da corrente intacto, configure a "
+"<guilabel>Nova Largura</guilabel> com o valor <guilabel>500 px</guilabel> e "
+"carregue em <guibutton>OK</guibutton>. Certifique-se que carrega em "
+"<keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo> para gravar as "
+"suas alterações no seu PNG, antes da conversão para EPS."
+d7712 1
+a7712 9
+msgstr ""
+"Este artigo de exemplo, chamado <citetitle>Um Artigo Muito Curto</"
+"citetitle>, consiste apenas num único parágrafo. As marcas de formatação "
+"reunem os elementos de conteúdo para definirem o sentido em que são usadas. "
+"Um parágrafo, por exemplo, é rodeado com marcas <sgmltag>para</sgmltag>. O "
+"texto que necessite de ênfase está marcado com <sgmltag>emphasis</sgmltag>. "
+"O autor não se irá preocupar com a formatação visual, como os itálicos ou o "
+"tamanho da letra. As ferramentas de compilação do Projecto de Documentação "
+"do Fedora efectuam todas as tarefas de formatação."
+d7722 1
+a7722 7
+msgstr ""
+"As ferramentas personalizadas, criadas pelo Projecto de Documentação do "
+"Fedora, representam o código em DocBook numa variedade de formatos para "
+"publicação e distribuição. Também permitem aos tradutores criarem versões "
+"locaais dos documentos de XML, para os utilizadores de Fedora em todo o "
+"mundo. A flexibilidade do XML permite a um único documento ser usado várias "
+"vezes para diversos fins, como a reutilização de código para um programador."
+d7731 1
+a7731 6
+msgstr ""
+"O DocBook está em si muito bem documentado. Para mais informações acerca do "
+"DocBook, visite a página <ulink url=\"http://www.docbook.org/\"/>. A página "
+"do DocBook também contém cópias completas do livro <citetitle>DocBook: The "
+"Definitive Guide</citetitle> para navegar e transferir, sendo esta a fonte "
+"canónicad de informação sobre o DocBook."
+d8061 1
+a8061 4
+msgstr ""
+"As cores, tipos de letra e geometria (tamanho predefinido da janela) do "
+"Emacs no seu ficheiro <filename>~/.Xresources</filename>. O formato da "
+"configuração é <computeroutput>emacs.palavra-chave:valor</computeroutput>"
+d8514 1
+a8514 4
+msgstr ""
+"Um cartão de referência do Emacs que vem com o pacote <filename>emacs</"
+"filename>. Poderá imprimi-lo como referência. —<filename>/usr/share/"
+"emacs/<replaceable><versão></replaceable>/etc/refcard.ps</filename>"
+d8520 1
+a8520 4
+msgstr ""
+"Leia o <citetitle>Editing XML with Emacs and PSGML</citetitle> no ficheiro "
+"<filename>/usr/share/doc/psgml-<replaceable><versão></replaceable>/"
+"psgml.ps</filename>."
+@
+
+
+1.13
+log
+ at Finished changes on RH translations and docs
+@
+text
+ at d4 2
+a5 2
+"POT-Creation-Date: 2007-07-19 22:28+0100\n"
+"PO-Revision-Date: 2007-07-20 00:42+0100\n"
+d122 2
+a123 1
+msgstr "Correcções associadas para reflectir uma versão mais recente da realidade"
+d493 1
+a493 1
+"<!--$Id: pt.po,v 1.12 2007/06/10 20:46:37 zepires Exp $ -->\n"
+d3852 6
+a3857 1
+msgstr "Neste capítulo, irá descobrir um exemplo de um tutorial bastante curto de documentação do Projecto Fedora. Este exemplo é específico para a forma como o Projecto de Documentação usa o DocBook em XML. O exemplo consiste num conjunto de ficheiros usados para manter o conteúdo, bem como meta-dados para o tutorial."
+d3889 5
+a3893 1
+msgstr "O ficheiro <filename>rpm-info.xml</filename> contém todos os meta-dados necessários para o documento. Estes meta-dados incluem o título, a autoria, a licença e o histórico de versões. O <xref linkend=\"ex-rpminfo\"/> ilustra o conteúdo deste ficheiro:"
+d6239 4
+a6242 1
+msgstr "De acordo com as boas práticas de XML, a primeira linha de qualquer ficheiro de DocBook em XML deverá identificar o ficheiro como XML. Use a seguinte linha como primeira linha de qualquer ficheiro em XML novo:"
+d6252 3
+a6254 1
+msgstr "Todos os ficheiros deverão conter o cabeçalho Id do CVS. Use a seguinte linha como segunda linha para qualquer ficheiro em XML novo:"
+d6260 3
+a6262 1
+msgstr "Sempre que este ficheiro for enviado para o CVS, a linha é actualizada automaticamente para incluir informações acerca do ficheiro. Por exemplo:"
+d6646 8
+a6653 1
+msgstr "As imagens ou capturas de ecrã são ilustrações que apresentam o estado do ecrã que o utilizador poderá encontrar. As imagens poderão ser gráficas ou textuais. Contudo, as imagens usam bastante espaço num documento de texto para representar pedaços de informação relativamente pequenos. o mesmo espaço num documento poderá conter uma quantidade maior de informação mais descritiva e útil. Como tal, os autores deverão evitar as imagens sempre que possível, em detrimento de texto mais descritivo."
+d6664 9
+a6672 1
+msgstr "Uma das instâncias isoladas em que as imagens são úteis é para demonstrar a disposição física de um ecrã que não seja familiar para um leitor. <emphasis>Isto não significa que as ilustrações de janelas sejam bons usos para as imagens.</emphasis> Pelo contrário, as janelas são simplesmente instâncias de um elemento da interface com o qual o leitor já está familiarizado. Um diagrama anotado em certos casos, todavia, explica ao leitor onde encontrar certos blocos funcionais no ecrã, como as barras de menu."
+d6692 6
+a6697 1
+msgstr "Crie uma nova conta de utilizador para criar as imagens. A conta nova usa o tema, tipos de letra e tamanhos dos elementos predefinidos da instalação. A imagem resultante tem uma aparência familiar ao maior número de leitores, e faz com que os documentos do Projecto de Documentação do Fedora sejam consistentes."
+a6750 1
+#, fuzzy
+d6758 1
+a6758 7
+msgstr ""
+"Com a imagem aberta no <application>The GIMP</application>, carregue com o "
+"botão direito na imagem e seleccione a opção <guimenu>Ficheiro</guimenu> -"
+"> <guimenuitem>Gravar Como...</guimenuitem>. Em <guimenu>Determinar o "
+"Tipo de Ficheiro:</guimenu>, seleccione <guimenuitem>PostScript</"
+"guimenuitem>, carregando depois em <guibutton>OK</guibutton>. Active o "
+"alisamento da imagem com a opção <guibutton>Exportar</guibutton>."
+a6760 1
+#, fuzzy
+a6782 1
+#, fuzzy
+a6792 1
+#, fuzzy
+a6881 1
+#, fuzzy
+d6886 1
+a6886 4
+msgstr ""
+"A secção <xref linkend=\"ex-module-structure\"/> mostra uma árvore de pastas "
+"de um módulo de exemplo, excluindo as pastas <filename class=\"directory"
+"\">CVS</filename>:"
+a6990 1
+#, fuzzy
+d6997 1
+a6997 6
+msgstr ""
+"A pasta <placeholder-1/> contém os ficheiros especialmente formatados, "
+"criados e usados pelos tradutores. As ferramentas de compilação do Projecto "
+"de Documentação do Fedora usam estes ficheiros para criar versões traduzidas "
+"dos documentos. Os documentos traduzidos não são guardados no CVS; são "
+"criados à medida das necessidades a partir destes ficheiros PO."
+a7020 1
+#, fuzzy
+d7022 1
+a7022 1
+msgstr "Ficheiros Comuns"
+d7030 6
+a7035 1
+msgstr "Nunca adicione a pasta de ferramentas de compilação <systemitem>docs-common</systemitem> a um módulo individual. A formatação especial na lista de módulos transfere estas ferramentas, sempre que um utilizador obtém um módulo de um documento. Para mais informações, consulte em <xref linkend=\"ch-getting-files-naming-modules\"/>."
+d7048 6
+a7053 1
+msgstr "No Linux e na documentação do Fedora, as referências aos comandos normalmente incluem um número entre parêntesis. Este número representa a secção das <firstterm>páginas de manual</firstterm> que incluem a documentação para esse comando. Para ler a página de manual para o <command>make(1)</command>, use o comando <command>man 1 make</command>."
+a7055 1
+#, fuzzy
+d7062 1
+a7062 6
+msgstr ""
+"O sistema de compilação poderá representar o documento noutro formato, como "
+"o <abbrev>HTML</abbrev> ou o <abbrev>PDF</abbrev>, usando o <command>make(1)"
+"</command> e os programas da linha de comandos. Os autores <emphasis>não</"
+"emphasis> precisam de qualquer experiência anterior com os programas da "
+"linha de comandos ou o <command>make(1)</command>."
+d7397 3
+a7399 1
+msgstr "A produção de <abbrev>PDF</abbrev> tem alguns problemas e poderá não funcionar para o seu documento."
+d7614 4
+a7617 1
+msgstr "O objectivo do Projecto de Documentação do Fedora é criar documentação simples de usar, baseada em tarefas, para os utilizadores e programadores do Fedora. O Projecto de Documentação do Fedora usa as seguintes ferramentas:"
+a7712 1
+#, fuzzy
+d7720 1
+a7720 5
+msgstr ""
+"Os programas e folhas de estilo personalizados do Projecto de Documentação "
+"do Fedora estão guardados em CVS, no servidor <systemitem class="
+"\"fqdomainname\">cvs.fedoraproject.org</systemitem>. Obtenha-os em conjunto "
+"com os ficheiros de DocBook em XML, no que respeita à documentação existente."
+d7730 7
+a7736 1
+msgstr "O componente mais poderoso no pacote de ferramentas do Projecto de Documentação do Fedora é o <firstterm>DocBook XML</firstterm>. O DocBook XML é um esquema específico para gerar documentação técnica, usando a <firstterm>Extensible Markup Language</firstterm> ou <acronym>XML</acronym>. O XML permite aos autores marcarem certas partes de conteúdo com marcas descritivas. Segue-se um exemplo de DocBook XML:"
+d7747 9
+a7755 1
+msgstr "Este artigo de exemplo, chamado <citetitle>Um Artigo Muito Curto</citetitle>, consiste apenas num único parágrafo. As marcas de formatação reunem os elementos de conteúdo para definirem o sentido em que são usadas. Um parágrafo, por exemplo, é rodeado com marcas <sgmltag>para</sgmltag>. O texto que necessite de ênfase está marcado com <sgmltag>emphasis</sgmltag>. O autor não se irá preocupar com a formatação visual, como os itálicos ou o tamanho da letra. As ferramentas de compilação do Projecto de Documentação do Fedora efectuam todas as tarefas de formatação."
+d7765 7
+a7771 1
+msgstr "As ferramentas personalizadas, criadas pelo Projecto de Documentação do Fedora, representam o código em DocBook numa variedade de formatos para publicação e distribuição. Também permitem aos tradutores criarem versões locaais dos documentos de XML, para os utilizadores de Fedora em todo o mundo. A flexibilidade do XML permite a um único documento ser usado várias vezes para diversos fins, como a reutilização de código para um programador."
+d7780 6
+a7785 1
+msgstr "O DocBook está em si muito bem documentado. Para mais informações acerca do DocBook, visite a página <ulink url=\"http://www.docbook.org/\"/>. A página do DocBook também contém cópias completas do livro <citetitle>DocBook: The Definitive Guide</citetitle> para navegar e transferir, sendo esta a fonte canónicad de informação sobre o DocBook."
+a7787 1
+#, fuzzy
+d7789 1
+a7789 1
+msgstr "Marcas XML do DocBook"
+d7797 5
+a7801 1
+msgstr "O DocBook XML, como um programa de computador, tem números de versões. A versão usada no Projecto de Documentação do Fedora neste momento é a 4.4. A página Web do DocBook poderá conter uma versão ligeiramente mais recente, mas a maioria do esquema aplica-se à mesma."
+a7803 1
+#, fuzzy
+d7805 1
+a7805 1
+msgstr "Convenções dos Nomes dos Identificadores"
+a7807 1
+#, fuzzy
+d7830 8
+a7837 1
+msgstr "No servidor de CVS, as pastas que contêm os ficheiros de documentos chamam-se <firstterm>módulos</firstterm>. Cada módulo representa um único documento. Cada documento poderá consistir em várias <firstterm>ramificações</firstterm>, se esse documento for alterado em cada versão do Fedora. Os contribuintes poderão obter ramificações únicas desses módulos ou então o módulo inteiro. Cada documento ou ramificação poderá conter vários ficheiros em XML."
+a7839 1
+#, fuzzy
+d7842 1
+a7842 3
+msgstr ""
+"Use sempre o comando <command>sfdisk -n</command> para verificar os seus "
+"dados de entrada, antes de gravar no disco."
+d7859 6
+a7864 1
+msgstr "O item mais à esquerda de cada linha é o nome de um módulo que poderá transferir do CVS. O restante da linha garante que as transferências incluem a ramificação correcta de um documento, assim como as ferramentas de compilação comuns. Para mais informações sobre o CVS, consulte em <xref linkend=\"ch-cvs\"/>."
+d7873 6
+a7878 1
+msgstr "Repare na listagem acima que o módulo <systemitem>about-fedora</systemitem> tem duas ramificações disponíveis. Uma é para o Fedora 7 e outra é para a versão em desenvolvimento posterior, reflectindo o trabalho actual dos programadores. Por outro lado, o módulo <systemitem>documentation-guide</systemitem> não tem ramificações."
+a7880 1
+#, fuzzy
+d7882 1
+a7882 1
+msgstr "A <filename>Makefile</filename> do Documento"
+d7889 5
+a7893 1
+msgstr "Os módulos que terminam com o sufixo <filename>-dir</filename> não são normalmente úteis para transferir directamente. Estes módulos não incluem as ferramentas de compilação comuns e, deste modo, não oferecem muitas das funções que os contribuintes necessitam."
+a7895 1
+#, fuzzy
+d7897 1
+a7897 1
+msgstr "Nomes de Comandos"
+d7906 7
+a7912 1
+msgstr "Escolha um nome de módulo que reflicta com precisão o assunto do seu documento, mas evite um nome que já tenha sido usado. O título do documento sem usar a palavra <wordasword>fedora</wordasword> é normalmente uma escolha razoável na maioria dos casos. Use as descrições da dimensão <wordasword>tutorial</wordasword> ou <wordasword>guide</wordasword> (guia) no nome do módulo, se for apropriado."
+a7918 1
+#, fuzzy
+d7922 1
+a7922 3
+msgstr ""
+"Não use a palavra <wordasword>Fedora</wordasword> no nome dos módulos do "
+"repositório de CVS do Projecto de Documentação do Fedora."
+a7924 1
+#, fuzzy
+d7926 1
+a7926 1
+msgstr "Correcto: Advertência breve"
+a7928 1
+#, fuzzy
+d7930 1
+a7930 1
+msgstr "Nomes dos Ficheiros do Documento"
+a7932 1
+#, fuzzy
+d7934 1
+a7934 1
+msgstr "Conteúdo do Módulo de CVS"
+a7948 1
+#, fuzzy
+d7950 1
+a7950 1
+msgstr "Poderá usar isto para <placeholder-1/>"
+a7960 1
+#, fuzzy
+d7962 1
+a7962 1
+msgstr "make po/<placeholder-1/>.po"
+a7968 1
+#, fuzzy
+d7970 1
+a7970 1
+msgstr "filename"
+d7976 3
+a7978 1
+msgstr "Siga estas convenções para nomear os ficheiros, de modo a tornar a colaboração e a reutilização de documentos mais simples:"
+d7984 3
+a7986 1
+msgstr "Como no nome dos módulos, evite usar a palavra <wordasword>fedora</wordasword> nos nomes dos ficheiros, dado que é redundante."
+d7992 3
+a7994 1
+msgstr "Se o documento for composto por muitos ficheiros XML, evite repetir o nome do documento ao criar os ficheiros constituintes."
+d8000 4
+a8003 1
+msgstr "Evite numerar os ficheiros para demonstrar a ordem, dado que os editores e autores normalmente reorganizam os documentos ou reutilizam os seus ficheiros noutros documentos."
+d8062 5
+a8066 1
+msgstr "Para o Emacs processar correctamente os seus documentos em DocBook, deverá ter um ficheiro <filename>.emacs</filename>. Corte e cole o seguinte no seu ficheiro <filename>.emacs</filename> existente ou crie um novo que contenha as seguintes linhas:"
+a8110 1
+#, fuzzy
+a8132 1
+#, fuzzy
+d8134 1
+a8134 1
+msgstr "Depois de modificar este ficheiro, terá de executar o comando"
+a8140 1
+#, fuzzy
+d8142 1
+a8142 3
+msgstr ""
+"e reiniciar o <application>Emacs</application> para as alterações fazerem "
+"efeito."
+a8223 1
+#, fuzzy
+d8227 1
+a8227 3
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+a8233 1
+#, fuzzy
+d8238 1
+a8238 4
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><keycap/></keycombo>, type beginning of tag, "
+"<placeholder-4/>"
+a8424 1
+#, fuzzy
+d8426 1
+a8426 3
+msgstr ""
+"Esta secção assume que você já carregou o ficheiro da DTD (<filename>.ced</"
+"filename>)."
+a8428 1
+#, fuzzy
+a8444 1
+#, fuzzy
+a8458 1
+#, fuzzy
+d8463 1
+a8463 3
+msgstr ""
+"Para reiniciar o seu sistema, carregue em <keycombo><keycap>Ctrl</"
+"keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo>."
+a8469 1
+#, fuzzy
+a8489 1
+#, fuzzy
+d8495 1
+a8495 7
+msgstr ""
+"<guilabel>Funcionar com uma janela</guilabel>: Algumas vezes no "
+"<application>Emacs</application>, a janela vai ficando dividida (com as "
+"completações de marcas ou outro texto na janela inferior). A forma mais "
+"simples de voltar atrás, para que apenas o seu XML e o texto apareçam num "
+"ecrã, é usar a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</"
+"keycap>, seguida de <keycap>1</keycap>."
+a8501 1
+#, fuzzy
+d8506 1
+a8506 4
+msgstr ""
+"<guilabel>Gravar o seu trabalho</guilabel>: Para gravar o seu trabalho, use "
+"a seguinte combinação de teclas, <keycap>Ctrl</keycap>-<keycap>X</keycap>, "
+"seguida de <keycap>Ctrl</keycap>-<keycap>S</keycap>."
+d8518 5
+a8522 1
+msgstr "Se o processo de completação de marcas se tornar incomportável ou confuso, use a sequência de teclas <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> para voltar para o texto. O <application>Emacs</application> limpa todas as linhas de comando e volta para o texto."
+a8524 1
+#, fuzzy
+d8526 1
+a8526 1
+msgstr "Abrir um ficheiro"
+a8528 1
+#, fuzzy
+d8535 1
+a8535 6
+msgstr ""
+"<guilabel>Abrir um novo ficheiro</guilabel>: Para abrir um novo ficheiro, "
+"use a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida "
+"de <keycap>Ctrl</keycap>-<keycap>F</keycap>. No fundo da janela do Emacs, "
+"será capaz de indicar o nome do ficheiro (usando a completação do "
+"<keycap>Tab</keycap> se necessário) do ficheiro que deseja abrir."
+a8541 1
+#, fuzzy
+d8548 1
+a8548 7
+msgstr ""
+"<guilabel>Fechar o emacs</guilabel>: A forma mais simples de fechar o "
+"<application>emacs</application> é usar a combinação de teclas <keycap>Ctrl</"
+"keycap>-<keycap>X</keycap> seguida de <keycap>Ctrl</keycap>-<keycap>C</"
+"keycap>. Se não tiver gravado o seu trabalho, será questionado para gravar o "
+"ficheiro; caso contrário, só irá sair da sessão actual do Emacs com que "
+"esteve a trabalhar."
+a8566 1
+#, fuzzy
+a8576 1
+#, fuzzy
+a8585 1
+#, fuzzy
+d8590 1
+a8590 5
+msgstr ""
+"O <ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\">http://www."
+"snee.com/bob/sgmlfree/psgmqref.html</ulink>—<citetitle>Emacs/PSGML "
+"Quick Reference</citetitle> é uma tabela de referência dos comandos do Emacs "
+"para o modo do PSGML."
+a9034 1
+#, fuzzy
+a9071 1
+#, fuzzy
+d9076 1
+a9076 4
+msgstr ""
+"Uma correcção de Karsten Wade (kwade at redhat.com) foi aplicada para "
+"adicionar o <xref linkend=\"sn-screenshots\"/>. Foi editada por Paul W. "
+"Frields (stickstr5 at hotmail.com)."
+a9078 1
+#, fuzzy
+d9083 1
+a9083 4
+msgstr ""
+"Uma correcção de Paul W. Frields (stickstr5 at hotmail.com) foi aplicada "
+"para adicionar mais explicações sobre o conjunto de marcas <command>screen</"
+"command> em <xref linkend=\"sn-xml-tags-screen\"/>."
+d9119 2
+a9120 1
+#~ "<!ENTITY % FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-en.xml\">\n"
+d9123 2
+a9124 1
+#~ "<!ENTITY VERSION \"0.1\"> <!-- change version of tutorial here -->\n"
+d9126 2
+a9127 1
+#~ "<!ENTITY DOCID \"example-tutorial-&VERSION; (2003-07-07)\"> <!-- change last modified date here -->\n"
+d9155 2
+a9156 1
+#~ " This is an example section. You can also use section, section, etc.\n"
+d9175 2
+a9176 1
+#~ "<!ENTITY % FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-pt.xml\">\n"
+d9179 2
+a9180 1
+#~ "<!ENTITY VERSION \"0.1\"> <!-- altere aqui a versão do tutorial -->\n"
+d9182 2
+a9183 1
+#~ "<!ENTITY DOCID \"tutorial-exemplo-&VERSION; (2003-07-07)\"> <!-- altere aqui a data da última modificação -->\n"
+d9211 2
+a9212 1
+#~ " Esta é uma secção de exemplo. Poderá também usar 'section', 'section', etc.\n"
+d9852 2
+a9853 1
+#~ "Nesta área, carregue em RET para seleccionar a completação perto do ponto.\n"
+@
+
+
+1.12
+log
+ at Finished changes on RH translations and docs
+@
+text
+ at d4 2
+a5 2
+"POT-Creation-Date: 2007-06-10 21:36+0100\n"
+"PO-Revision-Date: 2007-06-10 21:40+0100\n"
+d79 1
+a79 1
+#: en_US/rpm-info.xml:20(rights)
+d83 1
+a83 1
+#: en_US/rpm-info.xml:21(version)
+d87 1
+a87 1
+#: en_US/rpm-info.xml:24(year)
+d91 1
+a91 1
+#: en_US/rpm-info.xml:25(year)
+d95 1
+a95 1
+#: en_US/rpm-info.xml:26(year)
+d99 1
+a99 1
+#: en_US/rpm-info.xml:27(year)
+d103 3
+a105 11
+#: en_US/rpm-info.xml:28(holder)
+msgid "Red Hat, Inc."
+msgstr "Red Hat, Inc."
+
+#: en_US/rpm-info.xml:29(holder)
+msgid "Tammy Fox"
+msgstr "Tammy Fox"
+
+#: en_US/rpm-info.xml:30(holder)
+msgid "Johnray Fuller"
+msgstr "Johnray Fuller"
+d108 2
+a109 6
+msgid "Sandra Moore"
+msgstr "Sandra Moore"
+
+#: en_US/rpm-info.xml:32(holder)
+msgid "Paul W. Frields"
+msgstr "Paul W. Frields"
+d111 1
+a111 1
+#: en_US/rpm-info.xml:34(title)
+d115 1
+a115 1
+#: en_US/rpm-info.xml:35(desc)
+d120 7
+a126 3
+#: en_US/rpm-info.xml:42(details)
+msgid "Update to new build requirements"
+msgstr "Actualização para os novos requisitos de compilação"
+d165 17
+a181 17
+#: en_US/xml-tags.xml:2484(primary) en_US/writing-guidelines.xml:41(primary)
+#: en_US/writing-guidelines.xml:54(primary)
+#: en_US/writing-guidelines.xml:266(primary)
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:276(primary)
+#: en_US/writing-guidelines.xml:281(primary)
+#: en_US/writing-guidelines.xml:286(primary)
+#: en_US/writing-guidelines.xml:291(primary)
+#: en_US/writing-guidelines.xml:297(primary)
+#: en_US/writing-guidelines.xml:303(primary)
+#: en_US/writing-guidelines.xml:309(primary)
+#: en_US/writing-guidelines.xml:315(primary)
+#: en_US/writing-guidelines.xml:341(primary)
+#: en_US/writing-guidelines.xml:346(primary)
+#: en_US/writing-guidelines.xml:351(primary)
+#: en_US/writing-guidelines.xml:356(primary)
+#: en_US/writing-guidelines.xml:361(primary)
+d251 1
+a251 1
+#: en_US/xml-tags.xml:59(primary) en_US/writing-guidelines.xml:137(primary)
+d256 1
+a256 1
+#: en_US/writing-guidelines.xml:138(secondary)
+d270 1
+a270 1
+#: en_US/xml-tags.xml:71(term) en_US/writing-guidelines.xml:149(term)
+d297 1
+a297 1
+#: en_US/xml-tags.xml:85(para) en_US/writing-guidelines.xml:164(para)
+d305 1
+a305 1
+#: en_US/xml-tags.xml:91(para) en_US/writing-guidelines.xml:170(para)
+d315 1
+a315 1
+#: en_US/xml-tags.xml:97(para) en_US/writing-guidelines.xml:176(para)
+d324 1
+a324 1
+#: en_US/xml-tags.xml:105(term) en_US/writing-guidelines.xml:184(term)
+d350 1
+a350 1
+#: en_US/writing-guidelines.xml:198(sgmltag)
+d356 1
+a356 1
+#: en_US/xml-tags.xml:975(command) en_US/writing-guidelines.xml:201(sgmltag)
+d362 1
+a362 1
+#: en_US/writing-guidelines.xml:204(sgmltag)
+d368 1
+a368 1
+#: en_US/writing-guidelines.xml:207(sgmltag)
+d374 2
+a375 2
+#: en_US/writing-guidelines.xml:111(sgmltag)
+#: en_US/writing-guidelines.xml:210(sgmltag)
+d399 1
+a399 1
+#: en_US/xml-tags.xml:148(term) en_US/writing-guidelines.xml:227(term)
+d403 1
+a403 1
+#: en_US/xml-tags.xml:150(para) en_US/writing-guidelines.xml:229(para)
+d468 1
+a468 1
+#: en_US/writing-guidelines.xml:99(sgmltag)
+d481 1
+a481 1
+"<!--$Id: xml-tags.xml,v 1.5 2007/02/04 14:55:28 pfrields Exp $ -->\n"
+d492 1
+a492 1
+"<!--$Id: pt.po,v 1.11 2007/05/05 18:02:50 zepires Exp $ -->\n"
+d533 5
+a537 1
+msgstr "A marca <sgmltag>citetitle</sgmltag> produz a formatação para uma referência específica (o título poderá ser escrito manualmente ou, se já estiver definido dentro do seu conjunto de documentos, indicado como uma entidade<footnote><placeholder-1/></footnote> )."
+d670 2
+a671 2
+#: en_US/writing-guidelines.xml:394(title) en_US/emacs.xml:265(title)
+#: en_US/emacs.xml:565(title) en_US/emacs-nxml.xml:160(title)
+d765 1
+a765 1
+#: en_US/writing-guidelines.xml:123(sgmltag)
+d990 4
+a993 1
+msgstr "Para os que precisam de efectuar uma instalação para servidores <footnote><placeholder-1/></footnote>, veja no <citetitle>Guia de Instalação</citetitle>."
+d996 1
+a996 1
+#: en_US/writing-guidelines.xml:107(sgmltag)
+d1001 1
+a1001 1
+#: en_US/writing-guidelines.xml:424(title) en_US/emacs-nxml.xml:96(title)
+d1715 1
+a1715 1
+#: en_US/xml-tags.xml:1205(title) en_US/writing-guidelines.xml:434(title)
+d2353 1
+a2353 1
+#: en_US/writing-guidelines.xml:119(sgmltag)
+d3341 1
+a3341 1
+#: en_US/xml-tags.xml:2266(entry) en_US/emacs.xml:415(segtitle)
+d3470 1
+a3470 1
+#: en_US/emacs.xml:540(computeroutput)
+d3612 1
+a3612 1
+"<xref linkend=\"ch-tutorial\"></xref> and <xref linkend=\"sn-tutorial-parent\"></xref>\n"
+d3621 1
+a3621 1
+"tutorial\"/> and <xref linkend=\"sn-tutorial-parent\"/>."
+d3841 1
+a3841 1
+#: en_US/tutorial.xml:12(title)
+d3847 13
+a3859 12
+"In this chapter, you will find an example of a Fedora Project documentation "
+"parent file. This example is specific to the way the Docs Project uses "
+"DocBook XML. The parent file contains the main structural format of the "
+"book, a link to the entities file that contain common entities that should "
+"be used, and an entity to change the version and date of the tutorial."
+msgstr ""
+"Neste capítulo, irá descobrir um exemplo de um ficheiro-pai de documentação "
+"do Projecto Fedora. Este exemplo é específico para a forma como o Projecto "
+"de Documentação usa o DocBook em XML. O ficheiro-pai contém o formato "
+"principal da estrutura do livro, uma referência para o ficheiro de entidades "
+"que contém as entidades comuns a usar, bem como uma entidade para alterar a "
+"versão e a data do tutorial."
+d3861 23
+a3883 3
+#: en_US/tutorial.xml:23(title)
+msgid "The Parent File"
+msgstr "O Ficheiro-Pai"
+d3885 3
+a3887 3
+#: en_US/tutorial.xml:25(para)
+msgid "Below is a sample parent file:"
+msgstr "Em baixo, encontra-se um ficheiro-pai de exemplo:"
+d3889 1
+a3889 2
+#: en_US/tutorial.xml:30(computeroutput)
+#, no-wrap
+d3891 4
+a3894 51
+"\n"
+"<!DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook XML V4.2//EN\"\n"
+" \"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd\" [\n"
+"\n"
+"<!ENTITY % FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-en.xml\">\n"
+"%FEDORA-ENTITIES-EN;\n"
+"\n"
+"<!ENTITY VERSION \"0.1\"> <!-- change version of tutorial here -->\n"
+"\n"
+"<!ENTITY DOCID \"example-tutorial-&VERSION; (2003-07-07)\"> <!-- change last modified date here -->\n"
+"\n"
+"<!ENTITY LEGALNOTICE SYSTEM \"../common/legalnotice-en.xml\">\n"
+"\n"
+"\n"
+"]>\n"
+"\n"
+"<article id=\"example-tutorial\" lang=\"en\">\n"
+" <articleinfo>\n"
+" <title>Example Tutorial</title>\n"
+" <copyright>\n"
+" <year>2003</year>\n"
+" <holder>Red Hat Inc.</holder>\n"
+" <holder>Tammy Fox</holder>\n"
+" </copyright>\n"
+" <authorgroup>\n"
+" <author>\n"
+"\t<surname>Fox</surname>\n"
+"\t<firstname>Tammy</firstname>\n"
+" </author>\n"
+" </authorgroup>\n"
+" &LEGALNOTICE;\n"
+" </articleinfo>\n"
+"\n"
+" <section id=\"some-section\">\n"
+" <title>Some Section</title>\n"
+"\n"
+" <para>\n"
+" This is an example section. You can also use section, section, etc.\n"
+" </para>\n"
+"\n"
+" <warning>\n"
+" <title>Warning</title>\n"
+" <para>\n"
+"\tExample of an admonition.\n"
+" </para>\n"
+" </warning>\n"
+"\n"
+" </section>\n"
+"\n"
+"<index id=\"generated-index\"></index>\n"
+"</article>\n"
+d3896 5
+a3900 77
+"\n"
+"<!DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook XML V4.2//EN\"\n"
+" \"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd\" [\n"
+"\n"
+"<!ENTITY % FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-pt.xml\">\n"
+"%FEDORA-ENTITIES-PT;\n"
+"\n"
+"<!ENTITY VERSION \"0.1\"> <!-- altere aqui a versão do tutorial -->\n"
+"\n"
+"<!ENTITY DOCID \"tutorial-exemplo-&VERSION; (2003-07-07)\"> <!-- altere aqui a data da última modificação -->\n"
+"\n"
+"<!ENTITY LEGALNOTICE SYSTEM \"../common/legalnotice-pt.xml\">\n"
+"\n"
+"\n"
+"]>\n"
+"\n"
+"<article id=\"tutorial-exemplo\" lang=\"pt\">\n"
+" <articleinfo>\n"
+" <title>Tutorial de Exemplo</title>\n"
+" <copyright>\n"
+" <year>2003</year>\n"
+" <holder>Red Hat Inc.</holder>\n"
+" <holder>José Pires</holder>\n"
+" </copyright>\n"
+" <authorgroup>\n"
+" <author>\n"
+"\t<surname>Pires</surname>\n"
+"\t<firstname>José</firstname>\n"
+" </author>\n"
+" </authorgroup>\n"
+" &LEGALNOTICE;\n"
+" </articleinfo>\n"
+"\n"
+" <section id=\"uma-seccao\">\n"
+" <title>Uma Secção</title>\n"
+"\n"
+" <para>\n"
+" Esta é uma secção de exemplo. Poderá também usar 'section', 'section', etc.\n"
+" </para>\n"
+"\n"
+" <warning>\n"
+" <title>Aviso</title>\n"
+" <para>\n"
+"\tExemplo de uma chamada de atenção.\n"
+" </para>\n"
+" </warning>\n"
+"\n"
+" </section>\n"
+"\n"
+"<index id=\"generated-index\"></index>\n"
+"</article>\n"
+
+#: en_US/tutorial.xml:87(title)
+msgid "Including the License Information"
+msgstr "Incluir a Informação da Licença"
+
+#: en_US/tutorial.xml:90(primary)
+msgid "tutorial layout"
+msgstr "formato do tutorial"
+
+#: en_US/tutorial.xml:91(secondary)
+msgid "license"
+msgstr "licença"
+
+#: en_US/tutorial.xml:94(para)
+msgid ""
+"All Fedora Project manuals <emphasis>must</emphasis> contain the file "
+"<filename>legalnotice.xml</filename>. This file makes the license for the "
+"file the GNU Free Documentation License (FDL)."
+msgstr ""
+"Todos os manuais do Projecto Fedora <emphasis>deverão</emphasis> conter o "
+"ficheiro <filename>legalnotice.xml</filename>. Este ficheiro faz com que a "
+"licença do ficheiro seja a GNU Free Documentation License (FDL)."
+
+#: en_US/tutorial.xml:100(para)
+msgid "The sample parent file shows how it is included."
+msgstr "O ficheiro-paiu de exemplo demonstra como este é incluído."
+d3994 10
+a4003 1
+msgstr "A elegância vem em diversas formas. Na prosa e na poesia, a escrita elegante poderá não seguir algumas (ou todas) as regras comuns da gramática, sintaxe ou ortografia. Um bom exemplo é o Episódio 18, \"Penélope,\" do romance de James Joyce <citetitle>Ulisses</citetitle><footnote id=\"fn-ulysses\"><placeholder-1/></footnote>. Aqui, Joyce usa grandes sequências de palavras sem pontuação, de modo a simular a consciência interna de uma personagem. Ao violar as regras básicas da sintaxe e da gramática, Joyce simula os padrões de pensamento desorganizados mas levemente ligados do narrador."
+d6059 1
+a6059 1
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:259(title)
+d6125 7
+a6131 1
+msgstr "O comando <command>sfdisk</command> aceita um ficheiro de programa como dados de entrada para configurar as partições num disco rígido. Em alguns casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, criando uma tabela de partições incorrecta no seu disco.<warning><placeholder-1/><placeholder-2/></warning>"
+d6217 31
+d6251 3
+a6253 3
+#: en_US/writing-guidelines.xml:42(secondary)
+#: en_US/writing-guidelines.xml:46(primary)
+#: en_US/writing-guidelines.xml:59(primary)
+d6257 1
+a6257 1
+#: en_US/writing-guidelines.xml:49(para)
+d6267 2
+a6268 2
+#: en_US/writing-guidelines.xml:55(secondary)
+#: en_US/writing-guidelines.xml:60(secondary)
+d6272 1
+a6272 1
+#: en_US/writing-guidelines.xml:63(para)
+d6276 1
+a6276 1
+#: en_US/writing-guidelines.xml:67(para)
+d6280 1
+a6280 1
+#: en_US/writing-guidelines.xml:70(para)
+d6290 1
+a6290 1
+#: en_US/writing-guidelines.xml:76(para)
+d6298 1
+a6298 1
+#: en_US/writing-guidelines.xml:82(title)
+d6302 1
+a6302 1
+#: en_US/writing-guidelines.xml:91(title)
+d6306 1
+a6306 1
+#: en_US/writing-guidelines.xml:92(segtitle)
+d6310 1
+a6310 1
+#: en_US/writing-guidelines.xml:93(segtitle)
+d6314 1
+a6314 1
+#: en_US/writing-guidelines.xml:95(sgmltag)
+d6318 1
+a6318 1
+#: en_US/writing-guidelines.xml:96(literal)
+d6322 1
+a6322 1
+#: en_US/writing-guidelines.xml:100(literal)
+d6326 1
+a6326 1
+#: en_US/writing-guidelines.xml:103(sgmltag)
+d6330 1
+a6330 1
+#: en_US/writing-guidelines.xml:104(literal)
+d6334 1
+a6334 1
+#: en_US/writing-guidelines.xml:108(literal)
+d6338 1
+a6338 1
+#: en_US/writing-guidelines.xml:112(literal)
+d6342 1
+a6342 1
+#: en_US/writing-guidelines.xml:115(sgmltag)
+d6346 1
+a6346 1
+#: en_US/writing-guidelines.xml:116(literal)
+d6350 1
+a6350 1
+#: en_US/writing-guidelines.xml:120(literal)
+d6354 1
+a6354 1
+#: en_US/writing-guidelines.xml:124(literal)
+d6358 1
+a6358 1
+#: en_US/writing-guidelines.xml:128(para)
+d6366 5
+a6370 1
+#: en_US/writing-guidelines.xml:141(para)
+d6379 1
+a6379 1
+#: en_US/writing-guidelines.xml:151(para)
+d6394 1
+a6394 1
+#: en_US/writing-guidelines.xml:159(para)
+d6402 21
+a6422 1
+#: en_US/writing-guidelines.xml:186(para)
+d6432 1
+a6432 1
+#: en_US/writing-guidelines.xml:191(para)
+d6442 1
+a6442 1
+#: en_US/writing-guidelines.xml:216(term)
+d6450 1
+a6450 1
+#: en_US/writing-guidelines.xml:219(para)
+d6463 6
+a6468 28
+#: en_US/writing-guidelines.xml:243(title)
+msgid "File Header"
+msgstr "Cabeçalho do Ficheiro"
+
+#: en_US/writing-guidelines.xml:245(para)
+msgid ""
+"All the files must contain the CVS Id header. If you create a new file, the "
+"first line must be:"
+msgstr ""
+"Todos os ficheiros deverão conter o cabeçalho Id do CVS. Se criar um "
+"ficheiro novo, a primeira linha deverá ser:"
+
+#: en_US/writing-guidelines.xml:250(para)
+msgid ""
+"The first time it is committed to CVS (and every time it is committed to "
+"CVS) the line is updated automatically to include information about the "
+"file. For example:"
+msgstr ""
+"A primeira vez em que este ficheiro for enviado para o CVS (e sempre que "
+"forem enviadas novas versões), a linha actualizada automaticamente para "
+"incluir informações acerca do ficheiro. Por exemplo:"
+
+#: en_US/writing-guidelines.xml:262(primary)
+#: en_US/writing-guidelines.xml:292(secondary)
+#: en_US/writing-guidelines.xml:298(secondary)
+#: en_US/writing-guidelines.xml:304(secondary)
+#: en_US/writing-guidelines.xml:310(secondary)
+#: en_US/writing-guidelines.xml:316(secondary)
+d6472 3
+a6474 3
+#: en_US/writing-guidelines.xml:267(secondary)
+#: en_US/writing-guidelines.xml:293(tertiary)
+#: en_US/writing-guidelines.xml:362(secondary)
+d6478 3
+a6480 3
+#: en_US/writing-guidelines.xml:272(secondary)
+#: en_US/writing-guidelines.xml:299(tertiary)
+#: en_US/writing-guidelines.xml:347(secondary)
+d6484 3
+a6486 3
+#: en_US/writing-guidelines.xml:277(secondary)
+#: en_US/writing-guidelines.xml:305(tertiary)
+#: en_US/writing-guidelines.xml:342(secondary)
+d6490 3
+a6492 3
+#: en_US/writing-guidelines.xml:282(secondary)
+#: en_US/writing-guidelines.xml:311(tertiary)
+#: en_US/writing-guidelines.xml:352(secondary)
+d6496 3
+a6498 3
+#: en_US/writing-guidelines.xml:287(secondary)
+#: en_US/writing-guidelines.xml:317(tertiary)
+#: en_US/writing-guidelines.xml:357(secondary)
+d6502 1
+a6502 1
+#: en_US/writing-guidelines.xml:320(para)
+d6525 1
+a6525 1
+#: en_US/writing-guidelines.xml:334(title)
+d6537 1
+a6537 1
+#: en_US/writing-guidelines.xml:365(para)
+d6572 1
+a6572 1
+#: en_US/writing-guidelines.xml:385(para)
+d6580 4
+a6583 4
+#: en_US/writing-guidelines.xml:395(para)
+#: en_US/writing-guidelines.xml:415(para)
+#: en_US/writing-guidelines.xml:425(para)
+#: en_US/writing-guidelines.xml:435(para)
+d6587 1
+a6587 2
+#: en_US/writing-guidelines.xml:404(title) en_US/emacs.xml:348(title)
+#: en_US/emacs.xml:396(title) en_US/emacs-nxml.xml:114(title)
+d6591 1
+a6591 1
+#: en_US/writing-guidelines.xml:405(para)
+d6595 1
+a6595 1
+#: en_US/writing-guidelines.xml:414(title)
+d6599 1
+a6599 1
+#: en_US/writing-guidelines.xml:442(title)
+d6603 2
+a6604 2
+#: en_US/writing-guidelines.xml:445(primary)
+#: en_US/writing-guidelines.xml:450(see) en_US/writing-guidelines.xml:454(see)
+d6608 1
+a6608 1
+#: en_US/writing-guidelines.xml:446(secondary)
+d6612 1
+a6612 1
+#: en_US/writing-guidelines.xml:449(primary)
+d6616 1
+a6616 1
+#: en_US/writing-guidelines.xml:453(primary)
+d6620 1
+a6620 1
+#: en_US/writing-guidelines.xml:457(para)
+d6622 19
+a6640 28
+"There are two types of screenshots: graphical and textual. The philosophy on "
+"using these two types is <firstterm>rely on text over graphics</firstterm>. "
+"This means, if you can say it in text instead of showing a graphic, do so. A "
+"graphical screenshot of a GUI can create a good setting of objects to then "
+"describe textually, but you don't want to create a screenshot for each "
+"graphical step."
+msgstr ""
+"Existem dois tipos de imagens: gráficas e textuais. A filosofia na "
+"utilização destes dois tipos é <firstterm>basear-se em texto acima dos "
+"gráficos</firstterm>. Isto significa que, se puder dizer em texto, em vez de "
+"usar um gráfico, faça-o. Uma imagem gráfica de uma GUI poderá criar uma boa "
+"configuração de objectos que será depois descrita textualmente, mas não será "
+"interessante criar uma imagem por cada passo gráfico."
+
+#: en_US/writing-guidelines.xml:464(para)
+msgid ""
+"The main reason for this preference is that a block of text can usually "
+"convey more meaning than the same physical space of graphics. This is highly "
+"dependent on the graphic; obviously, a photographic image of a scene can "
+"convey more than 1000 words can. A GUI screenshot is usually full of blank "
+"space with a few elements that can just as easily be described or listed."
+msgstr ""
+"A razão principal para esta preferência é que um bloco de texto poderá "
+"conter normalmente mais significado que o mesmo espaço físico de uma imagem. "
+"Isto é altamente dependente do gráfico; obviamente, uma imagem vale mais que "
+"1000 palavras. Ua imagem gráfica normalmente está cheia de espaço em branco, "
+"contendo apenas alguns elementos que poderão ser descritos ou listados "
+"facilmente."
+d6642 1
+a6642 1
+#: en_US/writing-guidelines.xml:470(para)
+d6650 1
+a6650 1
+#: en_US/writing-guidelines.xml:475(term)
+d6654 1
+a6654 1
+#: en_US/writing-guidelines.xml:479(para)
+d6656 5
+a6660 28
+"Set the theme to Bluecurve defaults. This gives a look that is familiar to "
+"most readers, and makes Fedora Documentation Project documents consistent. "
+"From the panel menu, choose <guimenu>Preferences</guimenu>, "
+"<guimenuitem>Theme</guimenuitem> and select <guimenuitem>Bluecurve</"
+"guimenuitem> from the theme list."
+msgstr ""
+"Configure o tema com as predefinições do Bluecurve. Este gera uma aparência "
+"que é familiar para a maioria dos leitores, tornando também os documentos do "
+"Projecto de Documentação do Fedora mais consistentes. No menu do painel, "
+"escolha as <guimenu>Preferências</guimenu>, <guimenuitem>Tema</guimenuitem> "
+"e depois o <guimenuitem>Bluecurve</guimenuitem> na lista de temas."
+
+#: en_US/writing-guidelines.xml:488(para)
+msgid ""
+"Set fonts to Bluecurve defaults as well. From the panel menu, choose "
+"<guimenu>Preferences</guimenu>, <guimenuitem>Fonts</guimenuitem>. Set the "
+"<guilabel>Application font</guilabel> and the <guilabel>Desktop font</"
+"guilabel> to Sans Regular 10. Set the <guilabel>Window Title font</guilabel> "
+"to Sans Bold 10. Set the <guilabel>Terminal font</guilabel> to Monospace "
+"Regular 10."
+msgstr ""
+"Configure os tipos de letra com os predefinidos do Bluecurve. No menu do "
+"painel, escolha as <guimenu>Preferências</guimenu>, <guimenuitem>Tipos de "
+"Letra</guimenuitem>. Configure o <guilabel>Tipo de letra da aplicação</"
+"guilabel> e o <guilabel>Tipo de letra do ambiente de trabalho</guilabel> "
+"como Sans Regular 10. Configure o <guilabel>Tipo de letra do título da "
+"janela</guilabel> como Sans Bold 10. Configure o <guilabel>Tipo de letra do "
+"terminal</guilabel> como Monospace Regular 10."
+d6664 4
+a6667 4
+"Before taking the screenshot, try to resize the targeted GUI element(s) to "
+"the smallest possible size they can be. Your target is an image of 500 "
+"pixels or less. If you are doing a screenshot of more than one GUI element, "
+"you may need to resize the screenshot in a following step."
+d6676 2
+a6677 2
+"To take the screenshot, select the GUI element with your mouse, bringing it "
+"to the forefront, or otherwise arranging the elements. Press "
+d6680 3
+a6682 3
+"<keycap>Print Screen</keycap>. If you are taking a shot of multiple elements "
+"and have grouped them closely together, you can crop the resulting image in "
+"<application>The GIMP</application>. The image will be in the PNG format."
+d6693 1
+a6693 1
+#: en_US/writing-guidelines.xml:519(para)
+d6695 8
+a6702 7
+"If you need to, you can resize using <application>The GIMP</application>. "
+"With the image open, right-click on it and choose <guimenu>Image</guimenu> -"
+"> <guimenuitem>Scale Image...</guimenuitem>. With the chain symbol "
+"intact, set the <guilabel>New Width</guilabel> to <guilabel>500 px</"
+"guilabel>, and click <guibutton>OK</guibutton>. Be sure to "
+"<keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo> to save your "
+"changes to your PNG before converting to EPS."
+d6713 2
+a6714 1
+#: en_US/writing-guidelines.xml:532(para)
+d6716 6
+a6721 5
+"With the image open in <application>The GIMP</application>, right-click on "
+"the image, selecting <guimenu>File</guimenu> -> <guimenuitem>Save As...</"
+"guimenuitem>. Under <guimenu>Determine File Type:</guimenu>, select "
+"<guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</guibutton>. "
+"Allow flattening of the image by clicking <guibutton>Export</guibutton>."
+d6730 2
+a6731 1
+#: en_US/writing-guidelines.xml:541(para)
+d6733 1
+a6733 1
+"In the <guilabel>Save as PostScript</guilabel> window, select "
+d6741 1
+a6741 1
+#: en_US/writing-guidelines.xml:555(term)
+d6745 1
+a6745 1
+#: en_US/writing-guidelines.xml:557(para)
+d6753 2
+a6754 1
+#: en_US/writing-guidelines.xml:561(para)
+d6756 3
+a6758 3
+"If you use a graphical screenshot to illustrate a function, and the textual "
+"mode has identical functions, do not include both, unless omitting either "
+"would make your description unclear."
+d6764 2
+a6765 1
+#: en_US/writing-guidelines.xml:567(para)
+d6767 1
+a6767 1
+"Make your information generic over specific, and omit any username and "
+d6775 1
+a6775 1
+#: en_US/writing-guidelines.xml:573(para)
+d6779 1
+a6779 1
+#: en_US/writing-guidelines.xml:577(para)
+d6791 1
+a6791 1
+#: en_US/writing-guidelines.xml:585(para)
+d6799 1
+a6799 1
+#: en_US/writing-guidelines.xml:590(title)
+d6803 1
+a6803 1
+#: en_US/writing-guidelines.xml:603(para)
+d6809 1
+a6809 1
+#: en_US/writing-guidelines.xml:605(userinput)
+d6814 1
+a6814 1
+#: en_US/writing-guidelines.xml:607(para)
+d6818 1
+a6818 1
+#: en_US/writing-guidelines.xml:609(computeroutput)
+d6855 1
+d6858 2
+a6859 1
+"module, excluding any <filename class=\"directory\">CVS</filename> folders:"
+d6865 1
+a6865 1
+#: en_US/module-struct.xml:24(title)
+d6869 1
+a6869 1
+#: en_US/module-struct.xml:45(title)
+d6873 1
+a6873 1
+#: en_US/module-struct.xml:46(segtitle)
+d6877 1
+a6877 1
+#: en_US/module-struct.xml:47(segtitle)
+d6881 1
+a6881 1
+#: en_US/module-struct.xml:48(segtitle)
+d6885 1
+a6885 1
+#: en_US/module-struct.xml:50(seg)
+d6889 2
+a6890 2
+#: en_US/module-struct.xml:51(seg) en_US/module-struct.xml:88(seg)
+#: en_US/module-struct.xml:95(seg)
+d6894 2
+a6895 2
+#: en_US/module-struct.xml:54(filename)
+#: en_US/module-struct.xml:160(systemitem)
+d6899 1
+a6899 1
+#: en_US/module-struct.xml:58(firstterm)
+d6903 1
+a6903 1
+#: en_US/module-struct.xml:59(para)
+d6915 1
+a6915 1
+#: en_US/module-struct.xml:52(seg)
+d6923 7
+a6929 1
+msgstr "Esta é a única pasta que é absolutamente necessária. Esta tem o nome da língua original do documento, como por exemplo <placeholder-1/> (Inglês dos EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas todas as línguas. Esta pasta contém todo o código em XML do documento actual, assim como o código em XML específico do documento para <placeholder-2/><footnote><placeholder-3/></footnote>."
+d6931 1
+a6931 1
+#: en_US/module-struct.xml:67(seg)
+d6935 1
+a6935 1
+#: en_US/module-struct.xml:68(seg) en_US/module-struct.xml:78(seg)
+d6939 1
+a6939 1
+#: en_US/module-struct.xml:69(filename) en_US/module-struct.xml:73(filename)
+d6943 1
+a6943 1
+#: en_US/module-struct.xml:69(seg)
+d6955 1
+a6955 1
+#: en_US/module-struct.xml:77(seg)
+d6959 1
+a6959 1
+#: en_US/module-struct.xml:79(filename) en_US/module-struct.xml:167(filename)
+d6963 12
+a6974 7
+#: en_US/module-struct.xml:79(seg)
+msgid ""
+"The <placeholder-1/> directory contains specially formatted files created "
+"and used by translators. The Fedora Documentation Project build tools use "
+"these files to create translated versions of documents. The translated "
+"documents are not stored in CVS; they are created as needed from these PO "
+"files."
+d6982 1
+a6982 1
+#: en_US/module-struct.xml:87(seg) en_US/module-struct.xml:89(filename)
+d6986 1
+a6986 1
+#: en_US/module-struct.xml:89(seg)
+d6994 1
+a6994 1
+#: en_US/module-struct.xml:94(filename) en_US/module-struct.xml:96(filename)
+d6998 1
+a6998 1
+#: en_US/module-struct.xml:96(seg)
+d7004 13
+d7020 11
+a7030 1
+#: en_US/module-struct.xml:103(para)
+d7034 3
+a7036 2
+"command> and shell scripts. Authors need <emphasis>no</emphasis> prior "
+"experience with either shell scripts or a <command>make(1)</command>."
+d7044 1
+a7044 1
+#: en_US/module-struct.xml:111(title)
+d7048 1
+a7048 1
+#: en_US/module-struct.xml:112(para)
+d7058 1
+a7058 1
+#: en_US/module-struct.xml:118(para)
+d7067 1
+a7067 1
+#: en_US/module-struct.xml:124(title)
+d7071 1
+a7071 1
+#: en_US/module-struct.xml:141(para)
+d7081 1
+a7081 1
+#: en_US/module-struct.xml:147(title)
+d7085 1
+a7085 1
+#: en_US/module-struct.xml:148(segtitle)
+d7089 1
+a7089 1
+#: en_US/module-struct.xml:149(segtitle) en_US/module-struct.xml:263(segtitle)
+d7093 1
+a7093 1
+#: en_US/module-struct.xml:151(systemitem)
+d7097 1
+a7097 1
+#: en_US/module-struct.xml:152(seg)
+d7105 1
+a7105 1
+#: en_US/module-struct.xml:157(systemitem)
+d7109 1
+a7109 1
+#: en_US/module-struct.xml:158(seg)
+d7117 1
+a7117 1
+#: en_US/module-struct.xml:163(systemitem)
+d7121 1
+a7121 1
+#: en_US/module-struct.xml:164(seg)
+d7132 1
+a7132 1
+#: en_US/module-struct.xml:171(systemitem)
+d7136 1
+a7136 1
+#: en_US/module-struct.xml:172(seg)
+d7149 1
+a7149 1
+#: en_US/module-struct.xml:181(systemitem)
+d7153 1
+a7153 1
+#: en_US/module-struct.xml:184(systemitem)
+d7157 1
+a7157 1
+#: en_US/module-struct.xml:189(systemitem)
+d7161 1
+a7161 1
+#: en_US/module-struct.xml:182(seg)
+d7178 1
+a7178 1
+#: en_US/module-struct.xml:195(title)
+d7182 1
+a7182 1
+#: en_US/module-struct.xml:196(para)
+d7191 1
+a7191 1
+#: en_US/module-struct.xml:200(para)
+d7205 1
+a7205 1
+#: en_US/module-struct.xml:209(title)
+d7209 1
+a7209 1
+#: en_US/module-struct.xml:210(para)
+d7224 1
+a7224 22
+#: en_US/module-struct.xml:216(para)
+msgid "<xref linkend=\"ex-rpminfo\"/> illustrates the content of this file:"
+msgstr "O <xref linkend=\"ex-rpminfo\"/> ilustra o conteúdo deste ficheiro:"
+
+#: en_US/module-struct.xml:219(title)
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr "Ficheiro <filename>rpm-info.xml</filename> de Exemplo"
+
+#: en_US/module-struct.xml:248(para)
+msgid ""
+"If you are not familiar with XML editing, copy and paste this file from an "
+"existing module and then edit the values for the various elements as "
+"appropriate. Consult Fedora Documentation Project members and help channels "
+"for more assistance if needed."
+msgstr ""
+"Se não estiver familiarizado com a edição em XML, copie e cole este ficheiro "
+"a partir de um módulo existente e edite depois os valores dos vários "
+"elementos, como for mais apropriado. Consulte os membros do Projecto de "
+"Documentação do Fedora e os canais de ajuda para maior assistência, se for "
+"necessário."
+
+#: en_US/module-struct.xml:255(title)
+d7228 1
+a7228 1
+#: en_US/module-struct.xml:256(para)
+d7236 1
+a7236 1
+#: en_US/module-struct.xml:261(title)
+d7240 1
+a7240 1
+#: en_US/module-struct.xml:262(segtitle)
+d7244 1
+a7244 1
+#: en_US/module-struct.xml:265(systemitem)
+d7248 2
+a7249 2
+#: en_US/module-struct.xml:266(abbrev) en_US/module-struct.xml:277(abbrev)
+#: en_US/module-struct.xml:302(abbrev) en_US/module-struct.xml:307(abbrev)
+d7253 2
+a7254 2
+#: en_US/module-struct.xml:270(systemitem)
+#: en_US/module-struct.xml:280(systemitem)
+d7258 2
+a7259 2
+#: en_US/module-struct.xml:271(systemitem)
+#: en_US/module-struct.xml:281(systemitem)
+d7263 1
+a7263 1
+#: en_US/module-struct.xml:269(filename)
+d7267 1
+a7267 1
+#: en_US/module-struct.xml:266(seg)
+d7279 1
+a7279 1
+#: en_US/module-struct.xml:276(systemitem)
+d7283 1
+a7283 1
+#: en_US/module-struct.xml:279(filename)
+d7287 1
+a7287 1
+#: en_US/module-struct.xml:277(seg)
+d7297 1
+a7297 1
+#: en_US/module-struct.xml:285(systemitem)
+d7301 2
+a7302 2
+#: en_US/module-struct.xml:286(abbrev) en_US/module-struct.xml:287(abbrev)
+#: en_US/module-struct.xml:303(abbrev) en_US/module-struct.xml:308(abbrev)
+d7306 1
+a7306 1
+#: en_US/module-struct.xml:286(seg)
+d7316 1
+a7316 1
+#: en_US/module-struct.xml:291(systemitem)
+d7320 1
+a7320 1
+#: en_US/module-struct.xml:292(command)
+d7324 1
+a7324 1
+#: en_US/module-struct.xml:292(seg)
+d7332 1
+a7332 1
+#: en_US/module-struct.xml:296(systemitem)
+d7336 1
+a7336 1
+#: en_US/module-struct.xml:297(seg)
+d7340 2
+a7341 2
+#: en_US/module-struct.xml:300(systemitem)
+#: en_US/module-struct.xml:309(filename)
+d7345 1
+a7345 1
+#: en_US/module-struct.xml:302(emphasis)
+d7349 1
+a7349 1
+#: en_US/module-struct.xml:301(seg)
+d7357 1
+a7357 1
+#: en_US/module-struct.xml:306(systemitem)
+d7361 1
+a7361 1
+#: en_US/module-struct.xml:307(seg)
+d7369 11
+a7379 1
+#: en_US/module-struct.xml:314(title)
+d7383 1
+a7383 1
+#: en_US/module-struct.xml:315(para)
+d7397 1
+a7397 1
+#: en_US/module-struct.xml:323(para)
+d7406 1
+a7406 1
+#: en_US/module-struct.xml:330(title)
+d7410 1
+a7410 1
+#: en_US/module-struct.xml:331(para)
+d7422 1
+a7422 1
+#: en_US/module-struct.xml:338(para)
+d7444 1
+a7444 1
+#: en_US/module-struct.xml:352(para)
+d7455 1
+a7455 1
+#: en_US/module-struct.xml:358(para)
+d7472 1
+a7472 1
+#: en_US/module-struct.xml:368(para)
+d7488 1
+a7488 1
+#: en_US/module-struct.xml:377(para)
+d7496 1
+a7496 1
+#: en_US/module-struct.xml:383(title)
+d7500 1
+a7500 1
+#: en_US/module-struct.xml:390(title)
+d7504 1
+a7504 1
+#: en_US/module-struct.xml:391(para)
+d7511 1
+a7511 1
+#: en_US/module-struct.xml:395(para)
+d7515 1
+a7515 1
+#: en_US/module-struct.xml:399(para)
+d7529 1
+a7529 1
+#: en_US/module-struct.xml:409(title)
+d7533 1
+a7533 1
+#: en_US/module-struct.xml:410(para)
+d7546 1
+a7546 1
+#: en_US/module-struct.xml:417(para)
+d7554 1
+a7554 1
+#: en_US/module-struct.xml:423(para)
+d7558 1
+a7558 1
+#: en_US/module-struct.xml:427(para)
+d7566 1
+a7566 1
+#: en_US/module-struct.xml:432(para)
+d7574 1
+a7574 1
+#: en_US/module-struct.xml:435(replaceable)
+d7578 1
+a7578 1
+#: en_US/module-struct.xml:435(screen)
+d7590 3
+a7592 17
+"task-based documentation for Fedora users and developers. Other than the "
+"<citetitle>Installation Guide</citetitle>, each tutorial should be in "
+"DocBook XML article format, with one article per topic. This way, writers "
+"can contribute documentation about a specific topic without having to worry "
+"about how it fits into a manual or how it flows with other topics."
+msgstr ""
+"O objectivo do Projecto de Documentação do Fedora é criar documentação "
+"simples e baseada em tarefas para os utilizadores e programadores do Fedora. "
+"Exceptuando o <citetitle>Guia de Instalação</citetitle>, cada tutorial "
+"deverá estar no formato de artigos do DocBook em XML, tendo cada um dos "
+"artigos por tópico. Desta forma, os escritores poderão contribuir com "
+"documentação acerca de um tópico específico, sem terem de se preocupar com a "
+"sua adaptação a um manual ou como este se coaduna com outros tópicos."
+
+#: en_US/intro.xml:25(para)
+msgid "The following tools are used:"
+msgstr "São usadas as seguintes ferramentas:"
+d7594 1
+a7594 1
+#: en_US/intro.xml:31(para)
+d7598 1
+a7598 1
+#: en_US/intro.xml:34(para)
+d7603 1
+a7603 1
+#: en_US/intro.xml:38(para)
+d7609 1
+a7609 1
+#: en_US/intro.xml:42(para)
+d7613 1
+a7613 1
+#: en_US/intro.xml:51(para)
+d7672 5
+a7676 1
+msgstr "Se pensar em usar o <application>Emacs</application> para editar a documentação DocBook em XML, instale o pacote <package>psgml</package>, que adiciona funcionalidades úteis e de poupança de tempo, de modo a maximizar a eficiência na edição:"
+d7688 1
+d7692 4
+a7695 2
+"systemitem> CVS server. Check them out along with the DocBook XML files for "
+"the existing docs."
+d7702 1
+a7702 11
+#: en_US/getting-files.xml:58(replaceable)
+#: en_US/getting-files.xml:59(replaceable)
+msgid "my-fedora-docs-sandbox"
+msgstr "minha-pasta-documentos-fedora"
+
+#: en_US/getting-files.xml:60(replaceable)
+msgid "username"
+msgstr "utilizador"
+
+#: en_US/getting-files.xml:58(userinput)
+#, no-wrap
+d7704 42
+a7745 16
+"mkdir <placeholder-1/>\n"
+"cd <placeholder-2/>\n"
+"export CVSROOT=:ext:<placeholder-3/>@@cvs.fedora.redhat.com:/cvs/docs\n"
+"cvs login\n"
+"cvs co docs-common"
+msgstr ""
+"mkdir <placeholder-1/>\n"
+"cd <placeholder-2/>\n"
+"export CVSROOT=:ext:<placeholder-3/>@@cvs.fedora.redhat.com:/cvs/docs\n"
+"cvs login\n"
+"cvs co docs-common"
+
+#: en_US/getting-files.xml:65(para)
+msgid "At the password prompt, press the <keycap>Enter</keycap> key."
+msgstr ""
+"Na linha de comandos da senha, carregue na tecla <keycap>Enter</keycap>."
+d7747 1
+a7747 5
+#: en_US/getting-files.xml:70(title)
+msgid "Common Files"
+msgstr "Ficheiros Comuns"
+
+#: en_US/getting-files.xml:71(para)
+d7749 10
+a7758 18
+"You need to perform this \"checkout\" step only once, although you may need "
+"to update the files later. These files are common to all the official "
+"documentation."
+msgstr ""
+"Só precisa de efectuar este passo de \"extracção\" uma vez, ainda que "
+"precise de actualizar os ficheiros mais tarde. Estes ficheiros são comuns a "
+"toda a documentação oficial."
+
+#: en_US/getting-files.xml:78(para)
+msgid ""
+"To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+"Para trabalhar com os documentos existentes no CVS, consulte a secção <xref "
+"linkend=\"ch-cvs\"/>."
+
+#: en_US/getting-files.xml:85(title)
+msgid "Filename Conventions"
+msgstr "Convenções de Nomes de Ficheiros"
+d7760 2
+a7761 1
+#: en_US/getting-files.xml:86(para)
+d7767 1
+a7767 1
+"of these services, you must follow conventions for naming your files."
+d7776 9
+a7784 3
+#: en_US/getting-files.xml:94(title)
+msgid "Document Filenames"
+msgstr "Nomes dos Ficheiros do Documento"
+d7786 2
+a7787 1
+#: en_US/getting-files.xml:95(para)
+d7789 4
+a7792 9
+"Each document lives in a peer directory to the <filename>docs-common</"
+"filename> directory you extracted from the Fedora archive earlier. On the "
+"CVS server, these directories are called <firstterm>modules</firstterm>. Use "
+"the <command>cvs co -c</command> command to view existing module names."
+msgstr ""
+"Cada documento reside numa pasta acompanhante da <filename>docs-common</"
+"filename> que extraiu anteriormente do pacote do Fedora. No servidor de CVS, "
+"estas pastas chamam-se <firstterm>módulos</firstterm>. Use o comando "
+"<command>cvs co -c</command> para ver os nomes dos módulos existentes."
+d7794 1
+a7794 1
+#: en_US/getting-files.xml:103(title)
+d7798 1
+a7798 1
+#: en_US/getting-files.xml:104(userinput)
+d7803 1
+a7803 2
+#: en_US/getting-files.xml:105(computeroutput)
+#, no-wrap
+d7805 19
+a7823 17
+"build-docs infrastructure/build-docs\n"
+"cvsroot CVSROOT\n"
+"desktop-up2date desktop-up2date\n"
+"developer-guide developer-guide\n"
+"docs .\n"
+"docs-common docs-common\n"
+"documentation-guide documentation-guide\n"
+"example-tutorial example-tutorial"
+msgstr ""
+"build-docs infrastructure/build-docs\n"
+"cvsroot CVSROOT\n"
+"desktop-up2date desktop-up2date\n"
+"developer-guide developer-guide\n"
+"docs .\n"
+"docs-common docs-common\n"
+"documentation-guide documentation-guide\n"
+"example-tutorial example-tutorial"
+d7825 13
+a7837 1
+#: en_US/getting-files.xml:114(para)
+d7840 5
+a7844 4
+"avoid any name already taken."
+msgstr ""
+"Escolha um nome de módulo que reflicta com precisão o assunto do seu "
+"documento, evitando qualquer nome que já tenha sido usado."
+d7846 1
+a7846 1
+#: en_US/getting-files.xml:117(title)
+d7850 2
+a7851 1
+#: en_US/getting-files.xml:118(para)
+d7853 1
+a7853 1
+"Do not use the word <wordasword>Fedora</wordasword> to name modules in the "
+d7859 78
+d7946 3
+a7948 3
+#: en_US/emacs.xml:43(primary) en_US/emacs.xml:232(primary)
+#: en_US/emacs.xml:241(primary) en_US/emacs.xml:246(primary)
+#: en_US/emacs.xml:251(primary) en_US/emacs.xml:526(application)
+d7993 2
+a7994 256
+"the following lines: <screen><computeroutput><![CDATA[\n"
+";; turn on auto-fill in `text-mode' and derived modes \n"
+";;(mail, news, etc)\n"
+"(add-hook 'text-mode-hook 'turn-on-auto-fill)\n"
+"\n"
+";;\n"
+";;MODES\n"
+";;\n"
+"\n"
+"(setq auto-mode-alist (cons '(\"\\\\.sgml$\" . sgml-mode) auto-mode-alist))\n"
+"(setq auto-mode-alist (cons '(\"\\\\.sgm$\" . sgml-mode) auto-mode-alist))\n"
+"\n"
+";;\n"
+";;XML!!\n"
+";;\n"
+";;#############################################################\n"
+"\n"
+";;\n"
+";;PSGML mode stuff\n"
+";;\n"
+"\n"
+"(autoload 'sgml-mode \"psgml\" \"My Most Major Mode\" t)\n"
+"\n"
+"(setq sgml-mode-hook '(lambda () \"Defaults for XML mode.\" (turn-on-auto-"
+"fill) \n"
+"(setq fill-column 80)))\n"
+"\n"
+"(defun My-XML-keymap ()\n"
+" (local-set-key [(alt i)] \n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-indent-line)\n"
+" (sgml-insert-element 'item)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt l)] \n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-insert-element 'list)\n"
+" (sgml-insert-element 'item)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt p)]\n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-indent-line)\n"
+" (sgml-insert-element 'para)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt -)]\n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (insert \"—\")))) \n"
+"\n"
+"(add-hook 'sgml-mode-hook 'My-XML-keymap)\n"
+"\n"
+";;\n"
+";; Fix up indentation of data...\n"
+";;\n"
+"\n"
+"(setq-default sgml-indent-data t)\n"
+"\n"
+";;\n"
+";; XML markup faces.\n"
+";;\n"
+"\n"
+"(setq-default sgml-set-face t)\n"
+"\n"
+"\n"
+"(make-face 'sgml-comment-face)\n"
+"(make-face 'sgml-doctype-face)\n"
+"(make-face 'sgml-end-tag-face)\n"
+"(make-face 'sgml-entity-face)\n"
+"(make-face 'sgml-ignored-face)\n"
+"(make-face 'sgml-ms-end-face)\n"
+"(make-face 'sgml-ms-start-face)\n"
+"(make-face 'sgml-pi-face)\n"
+"(make-face 'sgml-sgml-face)\n"
+"(make-face 'sgml-short-ref-face)\n"
+"(make-face 'sgml-start-tag-face)\n"
+"\n"
+"(set-face-foreground 'sgml-comment-face \"maroon\")\n"
+"(set-face-foreground 'sgml-doctype-face \"dark green\")\n"
+"(set-face-foreground 'sgml-end-tag-face \"blue2\")\n"
+"(set-face-foreground 'sgml-entity-face \"red2\")\n"
+"(set-face-foreground 'sgml-ignored-face \"maroon\")\n"
+"(set-face-background 'sgml-ignored-face \"gray90\")\n"
+"(set-face-foreground 'sgml-ms-end-face \"maroon\")\n"
+"(set-face-foreground 'sgml-ms-start-face \"maroon\")\n"
+"(set-face-foreground 'sgml-pi-face \"maroon\")\n"
+"(set-face-foreground 'sgml-sgml-face \"maroon\")\n"
+"(set-face-foreground 'sgml-short-ref-face \"goldenrod\")\n"
+"(set-face-foreground 'sgml-start-tag-face \"blue2\")\n"
+"\n"
+"(setq-default sgml-markup-faces\n"
+" '((comment . sgml-comment-face)\n"
+" (doctype . sgml-doctype-face)\n"
+" (end-tag . sgml-end-tag-face)\n"
+" (entity . sgml-entity-face)\n"
+" (ignored . sgml-ignored-face)\n"
+" (ms-end . sgml-ms-end-face)\n"
+" (ms-start . sgml-ms-start-face)\n"
+" (pi . sgml-pi-face)\n"
+" (sgml . sgml-sgml-face)\n"
+" (short-ref . sgml-short-ref-face)\n"
+" (start-tag . sgml-start-tag-face)))\n"
+"\n"
+"\n"
+"(defun docbook-mode ()\n"
+" (sgml-mode)\n"
+" )\n"
+"\n"
+"\n"
+"\n"
+";;\n"
+";;END XML STUFF\n"
+";;\n"
+";;##################################################################\n"
+"\n"
+";PO mode stuff\n"
+"\n"
+"(setq auto-mode-alist\n"
+"\t(cons '(\"\\\\.pox?\\\\'\" . po-mode) auto-mode-alist))\n"
+"(autoload 'po-mode \"po-mode\")\n"
+"\n"
+"\n"
+" (global-set-key [(f1)] (lambda () (interactive) (manual-\n"
+" entry (current-word))))\n"
+"]]></computeroutput></screen>"
+msgstr ""
+"Para o Emacs processar correctamente os seus documentos em DocBook, terá de "
+"criar um ficheiro <filename>.emacs</filename>. Corte e cole o seguinte texto "
+"no seu ficheiro <filename>.emacs</filename> existente ou crie um novo que "
+"contenha as seguintes linhas:<screen><computeroutput><![CDATA[\n"
+";; activar o preenchimento automático no `text-mode' e nos modos derivados\n"
+";;(mail, news, etc)\n"
+"(add-hook 'text-mode-hook 'turn-on-auto-fill)\n"
+"\n"
+";;\n"
+";;MODOS\n"
+";;\n"
+"\n"
+"(setq auto-mode-alist (cons '(\"\\\\.sgml$\" . sgml-mode) auto-mode-alist))\n"
+"(setq auto-mode-alist (cons '(\"\\\\.sgm$\" . sgml-mode) auto-mode-alist))\n"
+"\n"
+";;\n"
+";;XML!!\n"
+";;\n"
+";;#############################################################\n"
+"\n"
+";;\n"
+";;Coisas do modo PSGML\n"
+";;\n"
+"\n"
+"(autoload 'sgml-mode \"psgml\" \"O Meu Modo Maior\" t)\n"
+"\n"
+"(setq sgml-mode-hook '(lambda () \"Predefinições do modo XML.\" (turn-on-"
+"auto-fill) \n"
+"(setq fill-column 80)))\n"
+"\n"
+"(defun Meu-Mapa-Teclas-XML ()\n"
+" (local-set-key [(alt i)] \n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-indent-line)\n"
+" (sgml-insert-element 'item)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt l)] \n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-insert-element 'list)\n"
+" (sgml-insert-element 'item)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt p)]\n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-indent-line)\n"
+" (sgml-insert-element 'para)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt -)]\n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (insert \"—\")))) \n"
+"\n"
+"(add-hook 'sgml-mode-hook 'Meu-Mapa-Teclas-XML)\n"
+"\n"
+";;\n"
+";; Corrigir a indentação dos dados...\n"
+";;\n"
+"\n"
+"(setq-default sgml-indent-data t)\n"
+"\n"
+";;\n"
+";; Faces da formatação em XML.\n"
+";;\n"
+"\n"
+"(setq-default sgml-set-face t)\n"
+"\n"
+"\n"
+"(make-face 'sgml-comment-face)\n"
+"(make-face 'sgml-doctype-face)\n"
+"(make-face 'sgml-end-tag-face)\n"
+"(make-face 'sgml-entity-face)\n"
+"(make-face 'sgml-ignored-face)\n"
+"(make-face 'sgml-ms-end-face)\n"
+"(make-face 'sgml-ms-start-face)\n"
+"(make-face 'sgml-pi-face)\n"
+"(make-face 'sgml-sgml-face)\n"
+"(make-face 'sgml-short-ref-face)\n"
+"(make-face 'sgml-start-tag-face)\n"
+"\n"
+"(set-face-foreground 'sgml-comment-face \"maroon\")\n"
+"(set-face-foreground 'sgml-doctype-face \"dark green\")\n"
+"(set-face-foreground 'sgml-end-tag-face \"blue2\")\n"
+"(set-face-foreground 'sgml-entity-face \"red2\")\n"
+"(set-face-foreground 'sgml-ignored-face \"maroon\")\n"
+"(set-face-background 'sgml-ignored-face \"gray90\")\n"
+"(set-face-foreground 'sgml-ms-end-face \"maroon\")\n"
+"(set-face-foreground 'sgml-ms-start-face \"maroon\")\n"
+"(set-face-foreground 'sgml-pi-face \"maroon\")\n"
+"(set-face-foreground 'sgml-sgml-face \"maroon\")\n"
+"(set-face-foreground 'sgml-short-ref-face \"goldenrod\")\n"
+"(set-face-foreground 'sgml-start-tag-face \"blue2\")\n"
+"\n"
+"(setq-default sgml-markup-faces\n"
+" '((comment . sgml-comment-face)\n"
+" (doctype . sgml-doctype-face)\n"
+" (end-tag . sgml-end-tag-face)\n"
+" (entity . sgml-entity-face)\n"
+" (ignored . sgml-ignored-face)\n"
+" (ms-end . sgml-ms-end-face)\n"
+" (ms-start . sgml-ms-start-face)\n"
+" (pi . sgml-pi-face)\n"
+" (sgml . sgml-sgml-face)\n"
+" (short-ref . sgml-short-ref-face)\n"
+" (start-tag . sgml-start-tag-face)))\n"
+"\n"
+"\n"
+"(defun docbook-mode ()\n"
+" (sgml-mode)\n"
+" )\n"
+"\n"
+"\n"
+"\n"
+";;\n"
+";;FIM DAS COISAS DE XML\n"
+";;\n"
+";;##################################################################\n"
+"\n"
+";coisas do modo PO\n"
+"\n"
+"(setq auto-mode-alist\n"
+"\t(cons '(\"\\\\.pox?\\\\'\" . po-mode) auto-mode-alist))\n"
+"(autoload 'po-mode \"po-mode\")\n"
+"\n"
+"\n"
+" (global-set-key [(f1)] (lambda () (interactive) (manual-\n"
+" entry (current-word))))\n"
+"]]></computeroutput></screen>"
+d7996 1
+a7996 1
+#: en_US/emacs.xml:185(para)
+d8006 1
+a8006 1
+#: en_US/emacs.xml:198(para)
+d8014 1
+a8014 1
+#: en_US/emacs.xml:229(title)
+d8018 1
+a8018 1
+#: en_US/emacs.xml:233(secondary)
+d8022 1
+a8022 1
+#: en_US/emacs.xml:237(filename)
+d8026 1
+a8026 1
+#: en_US/emacs.xml:242(secondary)
+d8030 1
+a8030 1
+#: en_US/emacs.xml:247(secondary)
+d8034 1
+a8034 1
+#: en_US/emacs.xml:252(secondary)
+d8038 2
+a8039 1
+#: en_US/emacs.xml:255(para)
+d8043 1
+a8043 1
+"<computeroutput>emacs.keyword:value</computeroutput>"
+d8049 1
+a8049 1
+#: en_US/emacs.xml:261(para)
+d8053 1
+a8053 1
+#: en_US/emacs.xml:266(para)
+d8061 3
+a8063 2
+#: en_US/emacs.xml:282(para)
+msgid "After modifying this file, you must execute the command"
+d8066 1
+a8066 1
+#: en_US/emacs.xml:286(command)
+d8070 3
+a8072 3
+#: en_US/emacs.xml:287(para)
+msgid ""
+"and restart <application>Emacs</application> for the changes to take place."
+d8077 1
+a8077 142
+#: en_US/emacs.xml:295(title)
+msgid "Create Recompiled DTD Subset"
+msgstr "Criar um Sub-Conjunto da DTD Compilado de Novo"
+
+#: en_US/emacs.xml:297(para)
+msgid ""
+"Emacs will perform syntax highlighting and indent correctly on DocBook XML "
+"files if you provide it with the proper Document Type Declarations (DTD) "
+"file. These two features will make your XML file look pretty and help you "
+"spot errors."
+msgstr ""
+"O Emacs irá efectuar o realce de sintaxe e a indentação correctamente para "
+"os ficheiros de DocBook em XML, se lhe fornecer o ficheiro de DTD "
+"(Declarações do Tipo de Documento) adequado. Estas duas funcionalidades "
+"farão com que o seu ficheiro XML fique bonito e você tenha alguma ajuda na "
+"descoberta de erros."
+
+#: en_US/emacs.xml:308(para)
+msgid ""
+"Find the parent file for the group of DocBook files. You will recognize this "
+"file by the header <filename><!DOCTYPE article PUBLIC \"-//OASIS//DTD "
+"DocBook V4.1//EN\"</filename>. An easy way to find this parent file is to "
+"use the command <command>grep DocBook *.xml</command>. Once you find the "
+"parent file, open it in Emacs with the command <command>emacs "
+"<replaceable><parentfile></replaceable>.xml</command> (where "
+"<replaceable><parentfile></replaceable>.xml is the parent file you "
+"found."
+msgstr ""
+"Descubra o ficheiro-pai do grupo de ficheiros DocBook. Irá reconhecer este "
+"ficheiro pelo cabeçalho <filename><!DOCTYPE article PUBLIC \"-//OASIS//"
+"DTD DocBook V4.1//EN\"</filename>. Uma forma simples de descobrir este "
+"ficheiro-pai é usar o comando <command>grep DocBook *.xml</command>. Logo "
+"que descubra o ficheiro-pai, abra-o no Emacs com o comando <command>emacs "
+"<replaceable><ficheiro-pai></replaceable>.xml</command> (onde o "
+"<replaceable><ficheiro-pai></replaceable>.xml é o ficheiro que "
+"descobriu."
+
+#: en_US/emacs.xml:321(para)
+msgid "Choose <command>DTD -> Parse DTD</command> from the pulldown menu."
+msgstr ""
+"Escolha a opção <command>DTD -> Parse DTD</command> (Processar a DTD) do "
+"menu respectivo."
+
+#: en_US/emacs.xml:327(para)
+msgid ""
+"You will know the parsing is finished when you see the message "
+"<computeroutput>Fontifying...done</computeroutput> at the bottom of your "
+"screen. Save the parsed DTD to a file by choosing <command>DTD -> Save "
+"Parsed DTD</command> from the pulldown menu."
+msgstr ""
+"Irá concluir se o processamento terminou quando lhe aparecer a mensagem "
+"<computeroutput>Fontifying...done</computeroutput> (A formatar... pronto) no "
+"fundo do seu ecrã. Grave a DTD processada num ficheiro com a opção "
+"<command>DTD -> Save Parsed DTD</command> (DTD - Gravar a DTD Processada) "
+"no menu."
+
+#: en_US/emacs.xml:335(para)
+msgid ""
+"Press <keycap>Enter</keycap> to save the file to the default filename or "
+"rename the file keeping the <filename>.ced</filename> extension. It can be "
+"useful to name it something generic such as <filename>docbook.ced</filename> "
+"so you can refer to it when opening all DocBook files. This file can also be "
+"copied from directory to directory to be loaded."
+msgstr ""
+"Carregue em <keycap>Enter</keycap> para gravar o ficheiro com o nome "
+"predefinido, ou mude o nome do ficheiro, mantendo a extensão <filename>.ced</"
+"filename>. Poderá ser útil atribuir-lhe um nome genérico, do tipo "
+"<filename>docbook.ced</filename>, para que o possa consultar quando abrir "
+"todos os ficheiros DocBook. Este ficheiro também poderá ser copiado de uma "
+"pasta para a pasta onde será carregado."
+
+#: en_US/emacs.xml:304(para)
+msgid "To create a loadable Parsed DTD file: <placeholder-1/>"
+msgstr ""
+"Para criar o ficheiro de uma DTD processada e com possibilidade de "
+"carregamento: <placeholder-1/>"
+
+#: en_US/emacs.xml:349(para)
+msgid ""
+"You can also use the Emacs command <command>Meta-x sgml-parse-prolog</"
+"command> to parse the file, and then use the command <command>Meta-x sgml-"
+"save-dtd</command> to save the parsed DTD to a <filename>.ced</filename> "
+"file."
+msgstr ""
+"Poderá também usar o comando do Emacs <command>Meta-x sgml-parse-prolog</"
+"command> para processar o ficheiro, usando depois o comando <command>Meta-x "
+"sgml-save-dtd</command> para gravar a DTD processada num ficheiro <filename>."
+"ced</filename>."
+
+#: en_US/emacs.xml:360(title)
+msgid "Load the Parsed DTD"
+msgstr "Carregar a DTD Processada"
+
+#: en_US/emacs.xml:362(para)
+msgid ""
+"Now that you have saved the DTD settings, you can load the <filename>.ced</"
+"filename> file and see the syntax highlighting for your <filename>.sgml</"
+"filename> files."
+msgstr ""
+"Agora que gravou a configuração da DTD, poderá carregar o ficheiro "
+"<filename>.ced</filename> e ver o realce de sintaxe dos seus ficheiros "
+"<filename>.sgml</filename>."
+
+#: en_US/emacs.xml:372(para)
+msgid "Open an XML file in Emacs."
+msgstr "Abra um ficheiro em XML no Emacs."
+
+#: en_US/emacs.xml:377(para)
+msgid ""
+"Choose <command>DTD -> Load DTD</command> from the pulldown menu and "
+"choose the file you saved from the previous step. For instance, choose "
+"<filename>docbook.ced</filename>."
+msgstr ""
+"Escolha a opção <command>DTD -> Load DTD</command> (DTD - Carregar a DTD) "
+"do menu que aparece e escolher o ficheiro que gravou no passo anterior. Por "
+"exemplo, escolha o <filename>docbook.ced</filename>."
+
+#: en_US/emacs.xml:384(para)
+msgid ""
+"You will know it is finished when you see the message "
+"<computeroutput>Fontifying...done</computeroutput> at the bottom of your "
+"screen. Loading the parsed DTD might take a long time. You can start editing "
+"the file before it finishes."
+msgstr ""
+"Irá saber quando terminou quando ver a mensagem <computeroutput>Fontifying..."
+"done</computeroutput> (A formatar... pronto) no fundo do seu ecrã. O "
+"carregamento da DTD processada poderá levar bastante tempo. Poderá começar a "
+"editar o ficheiro antes de este terminar."
+
+#: en_US/emacs.xml:368(para)
+msgid "To load a parsed DTD file: <placeholder-1/>"
+msgstr "Para carregar um ficheiro de DTD processado: <placeholder-1/>"
+
+#: en_US/emacs.xml:397(para)
+msgid ""
+"You can also use the Emacs command <command>Meta-x sgml-load-dtd</command> "
+"to load the parsed DTD."
+msgstr ""
+"Poderá também usar o comando do Emacs <command>Meta-x sgml-load-dtd</"
+"command> para carregar a DTD processada."
+
+#: en_US/emacs.xml:406(title)
+d8081 1
+a8081 1
+#: en_US/emacs.xml:408(para)
+d8086 1
+a8086 1
+#: en_US/emacs.xml:413(title)
+d8090 1
+a8090 1
+#: en_US/emacs.xml:414(segtitle)
+d8094 3
+a8096 4
+#: en_US/emacs.xml:418(keycap) en_US/emacs.xml:423(keycap)
+#: en_US/emacs.xml:428(keycap) en_US/emacs.xml:496(keycap)
+#: en_US/emacs.xml:501(keycap) en_US/emacs.xml:506(keycap)
+#: en_US/emacs.xml:530(keycap)
+d8100 3
+a8102 4
+#: en_US/emacs.xml:418(keycap) en_US/emacs.xml:423(keycap)
+#: en_US/emacs.xml:428(keycap) en_US/emacs.xml:501(keycap)
+#: en_US/emacs.xml:506(keycap) en_US/emacs.xml:511(keycap)
+#: en_US/emacs.xml:517(keycap) en_US/emacs.xml:523(keycap)
+d8106 2
+a8107 3
+#: en_US/emacs.xml:419(keycap) en_US/emacs.xml:424(keycap)
+#: en_US/emacs.xml:429(keycap) en_US/emacs.xml:502(keycap)
+#: en_US/emacs.xml:507(keycap)
+d8111 1
+a8111 1
+#: en_US/emacs.xml:417(seg)
+d8119 1
+a8119 1
+#: en_US/emacs.xml:420(seg)
+d8123 11
+a8133 35
+#: en_US/emacs.xml:423(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-save-dtd, "
+"<placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-save-dtd, "
+"<placeholder-3/>"
+
+#: en_US/emacs.xml:425(seg)
+msgid "Save the Parse DTD"
+msgstr "Gravar a DTD Processada"
+
+#: en_US/emacs.xml:428(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-load-dtd, "
+"<placeholder-3/>"
+msgstr ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-load-dtd, "
+"<placeholder-3/>"
+
+#: en_US/emacs.xml:430(seg)
+msgid "Load DTD"
+msgstr "Carregar a DTD"
+
+#: en_US/emacs.xml:433(keycap) en_US/emacs.xml:439(keycap)
+#: en_US/emacs.xml:446(keycap) en_US/emacs.xml:451(keycap)
+#: en_US/emacs.xml:456(keycap) en_US/emacs.xml:461(keycap)
+#: en_US/emacs.xml:466(keycap) en_US/emacs.xml:471(keycap)
+#: en_US/emacs.xml:476(keycap) en_US/emacs.xml:481(keycap)
+#: en_US/emacs.xml:486(keycap) en_US/emacs.xml:491(keycap)
+#: en_US/emacs.xml:511(keycap) en_US/emacs.xml:512(keycap)
+#: en_US/emacs.xml:517(keycap) en_US/emacs.xml:518(keycap)
+#: en_US/emacs.xml:523(keycap) en_US/emacs.xml:524(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:536(keycap)
+#: en_US/emacs.xml:543(keycap) en_US/emacs.xml:545(keycap)
+d8137 4
+a8140 4
+#: en_US/emacs.xml:433(keycap) en_US/emacs.xml:439(keycap)
+#: en_US/emacs.xml:451(keycap) en_US/emacs.xml:524(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:543(keycap)
+#: en_US/emacs.xml:545(keycap)
+d8144 1
+a8144 1
+#: en_US/emacs.xml:434(keycap) en_US/emacs.xml:440(keycap)
+d8148 5
+a8152 1
+#: en_US/emacs.xml:435(keycap) en_US/emacs.xml:442(keycap)
+d8156 2
+a8157 1
+#: en_US/emacs.xml:433(seg)
+d8160 1
+a8160 1
+"<keycombo><placeholder-3/><keycap/></keycombo>, <placeholder-4/>"
+d8163 1
+a8163 1
+"<keycombo><placeholder-3/><keycap/></keycombo>, <placeholder-4/>"
+d8165 1
+a8165 1
+#: en_US/emacs.xml:436(seg)
+d8169 2
+a8170 1
+#: en_US/emacs.xml:439(seg)
+d8173 2
+a8174 2
+"<keycombo><placeholder-3/><keycap/></keycombo>, type beginning of tag, "
+"<placeholder-4/>"
+d8180 1
+a8180 1
+#: en_US/emacs.xml:443(seg)
+d8184 1
+a8184 1
+#: en_US/emacs.xml:446(keycap)
+d8188 1
+a8188 1
+#: en_US/emacs.xml:448(seg)
+d8192 1
+a8192 1
+#: en_US/emacs.xml:452(keycap)
+d8196 1
+a8196 1
+#: en_US/emacs.xml:451(seg)
+d8201 1
+a8201 1
+#: en_US/emacs.xml:453(seg)
+d8205 1
+a8205 1
+#: en_US/emacs.xml:456(keycap) en_US/emacs.xml:536(keycap)
+d8209 1
+a8209 1
+#: en_US/emacs.xml:458(seg)
+d8213 1
+a8213 1
+#: en_US/emacs.xml:461(keycap)
+d8217 1
+a8217 1
+#: en_US/emacs.xml:463(seg)
+d8221 1
+a8221 1
+#: en_US/emacs.xml:466(keycap)
+d8225 1
+a8225 1
+#: en_US/emacs.xml:468(seg)
+d8229 1
+a8229 1
+#: en_US/emacs.xml:471(keycap)
+d8233 1
+a8233 1
+#: en_US/emacs.xml:473(seg)
+d8237 1
+a8237 1
+#: en_US/emacs.xml:476(keycap)
+d8241 1
+a8241 1
+#: en_US/emacs.xml:478(seg)
+d8245 1
+a8245 1
+#: en_US/emacs.xml:481(keycap)
+d8249 1
+a8249 1
+#: en_US/emacs.xml:483(seg)
+d8253 1
+a8253 1
+#: en_US/emacs.xml:486(keycap) en_US/emacs.xml:518(keycap)
+d8257 1
+a8257 1
+#: en_US/emacs.xml:488(seg)
+d8261 1
+a8261 1
+#: en_US/emacs.xml:491(keycap)
+d8265 1
+a8265 1
+#: en_US/emacs.xml:493(seg)
+d8269 1
+a8269 1
+#: en_US/emacs.xml:496(keycap)
+d8273 1
+a8273 1
+#: en_US/emacs.xml:498(seg) en_US/emacs.xml:503(seg)
+d8277 1
+a8277 1
+#: en_US/emacs.xml:501(seg)
+d8285 1
+a8285 1
+#: en_US/emacs.xml:506(seg)
+d8293 1
+a8293 1
+#: en_US/emacs.xml:508(seg)
+d8297 1
+a8297 1
+#: en_US/emacs.xml:512(keycap)
+d8301 2
+a8302 2
+#: en_US/emacs.xml:511(seg) en_US/emacs.xml:517(seg) en_US/emacs.xml:523(seg)
+#: en_US/emacs.xml:535(seg) en_US/emacs.xml:543(seg)
+d8310 1
+a8310 1
+#: en_US/emacs.xml:514(seg)
+d8314 1
+a8314 1
+#: en_US/emacs.xml:520(seg)
+d8318 1
+a8318 1
+#: en_US/emacs.xml:526(seg)
+d8322 1
+a8322 1
+#: en_US/emacs.xml:530(keycap)
+d8326 1
+a8326 1
+#: en_US/emacs.xml:532(seg)
+d8330 1
+a8330 1
+#: en_US/emacs.xml:539(computeroutput)
+d8335 1
+a8335 1
+#: en_US/emacs.xml:538(seg)
+d8343 1
+a8343 1
+#: en_US/emacs.xml:547(seg)
+d8347 1
+a8347 1
+#: en_US/emacs.xml:554(title) en_US/emacs-nxml.xml:77(title)
+d8351 1
+a8351 1
+#: en_US/emacs.xml:556(para)
+d8360 1
+a8360 1
+#: en_US/emacs.xml:562(title)
+d8364 3
+a8366 4
+#: en_US/emacs.xml:566(para)
+msgid ""
+"This section assumes that you have already loaded the DTD file (<filename>."
+"ced</filename>)."
+d8371 2
+a8372 1
+#: en_US/emacs.xml:571(para)
+d8374 4
+a8377 4
+"Instead of typing a tag each time you need to use it, use the key "
+"combination <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by "
+"<keycap><</keycap>. At the bottom of the <application>Emacs</application> "
+"window, you will see:"
+d8384 1
+a8384 2
+#: en_US/emacs.xml:578(computeroutput)
+#, no-wrap
+d8388 2
+a8389 1
+#: en_US/emacs.xml:581(para)
+d8392 4
+a8395 3
+"<keycap>?</keycap>. Or, if you know the first few letters of a tag, you can "
+"enter them followed by <keycap>Tab</keycap> for a complete list of available "
+"tags beginning with those letters or for a tag completion."
+d8403 2
+a8404 1
+#: en_US/emacs.xml:589(para)
+d8406 3
+a8408 4
+"Try the following: Type <keycap>Ctrl</keycap>-<keycap>c</keycap> followed by "
+"<keycap><</keycap>. Then enter the letter <keycap>k</keycap>, followed by "
+"<keycap>Tab</keycap>. You may have to use the <keycap>Tab</keycap> key "
+"several times to get a complete list."
+d8410 2
+a8411 8
+"Tente o seguinte: Escreva <keycap>Ctrl</keycap>-<keycap>C</keycap>, seguida "
+"de <keycap><</keycap>. Depois, escreva a letra <keycap>k</keycap>, "
+"seguida de <keycap>Tab</keycap>. Poderá ter de usar a tecla <keycap>Tab</"
+"keycap> várias vezes, para obter uma lista completa."
+
+#: en_US/emacs.xml:596(para)
+msgid "The output should look similar to the example below:"
+msgstr "O resultado deverá ficar semelhante ao exemplo abaixo:"
+d8413 1
+a8413 20
+#: en_US/emacs.xml:601(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Click mouse-2 on a completion to select it.\n"
+"In this buffer, type RET to select the completion near point.\n"
+"\n"
+"Possible completions are:\n"
+"<keycap> <keycode>\n"
+"<keycombo> <keysym>\n"
+msgstr ""
+"\n"
+"Carregue em rato-2 sobre uma completação para a seleccionar.\n"
+"Nesta área, carregue em RET para seleccionar a completação perto do ponto.\n"
+"\n"
+"As completações possíveis são:\n"
+"<keycap> <keycode>\n"
+"<keycombo> <keysym>\n"
+
+#: en_US/emacs.xml:613(title)
+d8417 2
+a8418 1
+#: en_US/emacs.xml:615(para)
+d8420 4
+a8423 4
+"Once you have started the tag of choice, you must close it. The easiest way "
+"to close an open tag is to use the keycombo <keycap>Ctrl</keycap>-<keycap>c</"
+"keycap>, followed by <keycap>/</keycap>. This will close the closest open "
+"tag you have."
+d8430 1
+a8430 1
+#: en_US/emacs.xml:625(title)
+d8434 6
+a8439 1
+#: en_US/emacs.xml:627(para)
+d8441 4
+a8444 6
+"<guilabel>Working with one window</guilabel>: Sometimes in "
+"<application>Emacs</application> the window becomes split (with tags "
+"completions or other text in the bottom window). The easiest way to get it "
+"back so that only your XML and text appear on one screen is to use the "
+"keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap>, followed by <keycap>1</"
+"keycap>."
+d8453 6
+a8458 1
+#: en_US/emacs.xml:636(para)
+d8460 3
+a8462 3
+"<guilabel>Saving your work</guilabel>: To save your work, use the following "
+"keycombo, <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</"
+"keycap>-<keycap>s</keycap>."
+d8468 19
+a8486 1
+#: en_US/emacs.xml:642(para)
+d8488 5
+a8492 19
+"<guilabel>The \"clear/quit\" command</guilabel>: I have found on some "
+"occasions that I have gotten too far into the tag completion process and "
+"need to just exit back out to my text. The easiest way to do this is the "
+"keycombo <keycap>Ctrl</keycap>-<keycap>g</keycap>. This command quits what "
+"you have been doing within the file, without quitting the file itself."
+msgstr ""
+"<guilabel>O comando \"limpar/sair\"</guilabel>: Descobri em algumas ocasiões "
+"que fui demasiado longe no processo de completação de marcas e preciso de "
+"sair para voltar ao meu text. A forma mais simples de fazer isto é a "
+"combinação de teclas <keycap>Ctrl</keycap>-<keycap>G</keycap>. Este comando "
+"sai do que estiver a fazer com o ficheiro, sem sair do ficheiro em si."
+
+#: en_US/emacs.xml:651(para)
+msgid ""
+"<guilabel>Opening a new file</guilabel>: To open a new file, use the "
+"keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</"
+"keycap>-<keycap>f</keycap>. At the bottom of the emacs window, you will be "
+"able to enter in the file name (using <keycap>Tab</keycap> completion if "
+"needed) of the file you wish to open."
+d8500 12
+a8511 8
+#: en_US/emacs.xml:660(para)
+msgid ""
+"<guilabel>Closing emacs</guilabel>: The easiest way to close "
+"<application>emacs</application> is to use the keycombo <keycap>Ctrl</"
+"keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</keycap>-<keycap>c</"
+"keycap>. If you have not saved your work, it will prompt you to save the "
+"file, otherwise it will just quit the current emacs session you have been "
+"working with."
+d8520 1
+a8520 1
+#: en_US/emacs.xml:673(title) en_US/emacs-nxml.xml:127(title)
+d8524 1
+a8524 1
+#: en_US/emacs.xml:675(para)
+d8532 1
+a8532 5
+#: en_US/emacs.xml:682(ulink) en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+
+#: en_US/emacs.xml:683(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+d8536 2
+a8537 1
+#: en_US/emacs.xml:686(para) en_US/emacs-nxml.xml:147(para)
+d8541 1
+a8541 1
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+d8547 2
+a8548 1
+#: en_US/emacs.xml:693(para)
+d8551 1
+a8551 2
+"usr/share/doc/psgml-<replaceable><version></replaceable>/psgml.ps</"
+"filename>."
+d8557 2
+a8558 1
+#: en_US/emacs.xml:697(para)
+d8560 3
+a8562 4
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\">http://www."
+"snee.com/bob/sgmlfree/psgmqref.html</ulink>—<citetitle>Emacs/PSGML "
+"Quick Reference</citetitle> is a reference table of Emacs commands for PSGML "
+"mode."
+d8569 1
+a8569 5
+#: en_US/emacs.xml:705(ulink)
+msgid "http://www.snee.com/bob/sgmlfree/emcspsgm.html"
+msgstr "http://www.snee.com/bob/sgmlfree/emcspsgm.html"
+
+#: en_US/emacs.xml:706(citetitle)
+d8729 14
+d9012 1
+d9014 3
+a9016 3
+"This document is based on the a document started by Tammy Fox (tfox at "
+"redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and "
+"Johnray Fuller (jrfuller at redhat.com)."
+d9050 1
+d9054 1
+a9054 1
+"(stickstr5 at hotmail.com)."
+d9061 1
+d9063 1
+a9063 1
+"A patch from Paul W. Frields (stickstr5 at hotmail.com) has been applied to "
+d9084 769
+@
+
+
+1.11
+log
+ at Finished changes on RH translations and docs
+@
+text
+ at d4 2
+a5 2
+"POT-Creation-Date: 2007-05-05 10:19-0400\n"
+"PO-Revision-Date: 2007-05-05 18:56+0100\n"
+d12 58
+a69 29
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas Redundâncias update yahoo VIMRUNTIME generated important \n"
+d489 1
+a489 1
+"<!--$Id: pt.po,v 1.10 2007/05/05 14:21:44 pfrields Exp $ -->\n"
+d500 1
+a500 1
+"<!--$Id: pt.po,v 1.10 2007/05/05 14:21:44 pfrields Exp $ -->\n"
+d540 2
+a541 2
+"your document set, given as an entity<placeholder-1/> )."
+msgstr "A marca <sgmltag>citetitle</sgmltag> produz a formatação para uma referência específica (o título poderá ser escrito manualmente ou, se já estiver definido dentro do seu conjunto de documentos, indicado como uma entidade<placeholder-1/> )."
+d991 4
+a994 3
+"For those of you who need to perform a server-class <placeholder-1/> "
+"installation, refer to the <citetitle>Installation Guide</citetitle>."
+msgstr "Para os que precisam de efectuar uma instalação para servidores <placeholder-1/>, veja no <citetitle>Guia de Instalação</citetitle>."
+d3623 3
+a3625 1
+msgstr "Para mais informações acerca do ficheiro-pai, veja em <xref linkend=\"ch-tutorial\"></xref> e <xref linkend=\"sn-tutorial-parent\"></xref>."
+d4089 6
+a4094 6
+"<citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long "
+"streams of words without punctuation to simulate a character's internal "
+"consciousness. By violating basic rules of grammar and syntax, Joyce "
+"simulates the disorganized but loosely connected thought patterns of the "
+"narrator."
+msgstr "A elegância vem em diversas formas. Na prosa e na poesia, a escrita elegante poderá não seguir algumas (ou todas) as regras comuns da gramática, sintaxe ou ortografia. Um bom exemplo é o Episódio 18, \"Penélope,\" do romance de James Joyce <citetitle>Ulisses</citetitle><placeholder-1/>. Aqui, Joyce usa grandes sequências de palavras sem pontuação, de modo a simular a consciência interna de uma personagem. Ao violar as regras básicas da sintaxe e da gramática, Joyce simula os padrões de pensamento desorganizados mas levemente ligados do narrador."
+d6215 2
+a6216 2
+"<placeholder-1/>"
+msgstr "O comando <command>sfdisk</command> aceita um ficheiro de programa como dados de entrada para configurar as partições num disco rígido. Em alguns casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, criando uma tabela de partições incorrecta no seu disco.<placeholder-1/>"
+d6998 3
+a7000 2
+"XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr "Esta é a única pasta que é absolutamente necessária. Esta tem o nome da língua original do documento, como por exemplo <placeholder-1/> (Inglês dos EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas todas as línguas. Esta pasta contém todo o código em XML do documento actual, assim como o código em XML específico do documento para <placeholder-2/><placeholder-3/>."
+d7734 13
+a7746 1
+#: en_US/getting-files.xml:43(title)
+d7750 1
+a7750 1
+#: en_US/getting-files.xml:45(para)
+d7762 2
+a7763 2
+#: en_US/getting-files.xml:53(replaceable)
+#: en_US/getting-files.xml:54(replaceable)
+d7767 1
+a7767 1
+#: en_US/getting-files.xml:55(replaceable)
+d7771 1
+a7771 1
+#: en_US/getting-files.xml:53(userinput)
+d7786 1
+a7786 1
+#: en_US/getting-files.xml:60(para)
+d7791 1
+a7791 1
+#: en_US/getting-files.xml:65(title)
+d7795 1
+a7795 1
+#: en_US/getting-files.xml:66(para)
+d7805 1
+a7805 1
+#: en_US/getting-files.xml:73(para)
+d7812 1
+a7812 1
+#: en_US/getting-files.xml:80(title)
+d7816 1
+a7816 1
+#: en_US/getting-files.xml:81(para)
+d7831 1
+a7831 1
+#: en_US/getting-files.xml:89(title)
+d7835 1
+a7835 1
+#: en_US/getting-files.xml:90(para)
+d7847 1
+a7847 1
+#: en_US/getting-files.xml:98(title)
+d7851 1
+a7851 1
+#: en_US/getting-files.xml:99(userinput)
+d7856 1
+a7856 1
+#: en_US/getting-files.xml:100(computeroutput)
+d7877 1
+a7877 1
+#: en_US/getting-files.xml:109(para)
+d7885 1
+a7885 1
+#: en_US/getting-files.xml:112(title)
+d7889 1
+a7889 1
+#: en_US/getting-files.xml:113(para)
+@
+
+
+1.10
+log
+ at Fix two small errors in pt PO file -- don't translate XML tags
+@
+text
+ at d5 1
+a5 1
+"PO-Revision-Date: 2007-05-05 10:21-0400\n"
+d12 29
+a40 58
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu "
+"guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires "
+"VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend "
+"autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert "
+"articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap "
+"dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML "
+"tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man "
+"sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot "
+"developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro "
+"keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC "
+"configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG "
+"Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule "
+"Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote "
+"eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest "
+"Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text "
+"jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd "
+"colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES "
+"set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray "
+"ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG "
+"PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar "
+"Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse "
+"cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo "
+"imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject "
+"Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference "
+"rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef "
+"authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done "
+"Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered "
+"nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead "
+"Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas "
+"Redundâncias update yahoo VIMRUNTIME generated important \n"
+d48 1
+d457 1
+a457 1
+#, fuzzy, no-wrap
+d460 1
+a460 1
+"<!--$Id: xml-tags.xml,v 1.5 2007/02/04 14:55:28 pfrields Exp $ -->\n"
+d471 1
+a471 1
+"<!--$Id: pt.po,v 1.9 2007/05/02 09:23:12 zepires Exp $ -->\n"
+a507 1
+#, fuzzy
+d512 1
+a512 5
+msgstr ""
+"A marca <sgmltag>citetitle</sgmltag> produz a formatação para uma referência "
+"específica (o título poderá ser escrito manualmente ou, se já estiver "
+"definido dentro do seu conjunto de documentos, indicado como uma "
+"entidade<footnote><placeholder-1/></footnote> )."
+a960 1
+#, fuzzy
+d964 1
+a964 4
+msgstr ""
+"Para os que precisam de efectuar uma instalação para servidores "
+"<footnote><placeholder-1/></footnote>, veja no <citetitle>Guia de "
+"Instalação</citetitle>."
+a4052 1
+#, fuzzy
+d4062 1
+a4062 10
+msgstr ""
+"A elegância vem em diversas formas. Na prosa e na poesia, a escrita elegante "
+"poderá não seguir algumas (ou todas) as regras comuns da gramática, sintaxe "
+"ou ortografia. Um bom exemplo é o Episódio 18, \"Penélope,\" do romance de "
+"James Joyce <citetitle>Ulisses</citetitle><footnote id=\"fn-ulysses"
+"\"><placeholder-1/></footnote>. Aqui, Joyce usa grandes sequências de "
+"palavras sem pontuação, de modo a simular a consciência interna de uma "
+"personagem. Ao violar as regras básicas da sintaxe e da gramática, Joyce "
+"simula os padrões de pensamento desorganizados mas levemente ligados do "
+"narrador."
+a6177 1
+#, fuzzy
+d6184 1
+a6184 7
+msgstr ""
+"O comando <command>sfdisk</command> aceita um ficheiro de programa como "
+"dados de entrada para configurar as partições num disco rígido. Em alguns "
+"casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de "
+"entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, "
+"criando uma tabela de partições incorrecta no seu disco."
+"<warning><placeholder-1/><placeholder-2/></warning>"
+a6960 1
+#, fuzzy
+d6967 1
+a6967 7
+msgstr ""
+"Esta é a única pasta que é absolutamente necessária. Esta tem o nome da "
+"língua original do documento, como por exemplo <placeholder-1/> (Inglês dos "
+"EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas "
+"todas as línguas. Esta pasta contém todo o código em XML do documento "
+"actual, assim como o código em XML específico do documento para <placeholder-"
+"2/><footnote><placeholder-3/></footnote>."
+@
+
+
+1.9
+log
+ at Finished RH for today
+@
+text
+ at d4 2
+a5 2
+"POT-Creation-Date: 2007-04-25 12:13+0100\n"
+"PO-Revision-Date: 2007-05-02 09:40+0100\n"
+d12 58
+a69 29
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas Redundâncias update yahoo VIMRUNTIME generated important \n"
+d485 1
+a485 1
+#, no-wrap
+d488 1
+a488 1
+"<!--$Id: pt.po,v 1.8 2007/05/02 08:47:21 zepires Exp $ -->\n"
+d499 1
+a499 1
+"<!--$Id: pt.po,v 1.8 2007/05/02 08:47:21 zepires Exp $ -->\n"
+d536 1
+d540 1
+a540 1
+"your document set, given as an entity<footnote><placeholder-1/></footnote> )."
+d994 1
+d996 2
+a997 3
+"For those of you who need to perform a server-class <footnote><placeholder-1/"
+"></footnote> installation, refer to the <citetitle>Installation Guide</"
+"citetitle>."
+d3624 1
+a3624 1
+"<xref linkend=\"ch-tutorial\"></xref> e <xref linkend=\"sn-tutorial-pai\"></xref>\n"
+d3630 1
+a3630 3
+msgstr ""
+"Para mais informações acerca do ficheiro-pai, veja em <xref linkend=\"ch-"
+"tutorial\"></xref> e <xref linkend=\"sn-tutorial-pai\"></xref>."
+d3758 9
+a3766 2
+"O VIM poderá acelerar a criação do seu DocBook, mapeando as teclas escritas com mais frequência (ou palavras ou frases) em combinações de teclas breves. Por omissão, o líder do mapa de teclados é a barra invertida (<literal>\\</literal>), mas poderá ser redefinida com um comando do tipo <userinput>let mapleader =\n"
+" \",\"</userinput>. Existem duas formas de usar o seguinte exemplo; podê-lo-á colocar direcamente no seu ficheiro <filename>.vimrc</filename> ou podê-lo-a gravar num ficheiro separado e fazendo referência com o comando <userinput>source</userinput> no seu <filename>.vimrc</filename>. <screen>\n"
+d3786 2
+a3787 1
+"imap<leader>cm <command></command><esc>F>a \n"
+d4090 1
+d4095 5
+a4099 5
+"<citetitle>Ulysses</citetitle><footnote id=\"fn-ulysses\"><placeholder-1/></"
+"footnote>. There, Joyce uses long streams of words without punctuation to "
+"simulate a character's internal consciousness. By violating basic rules of "
+"grammar and syntax, Joyce simulates the disorganized but loosely connected "
+"thought patterns of the narrator."
+d6225 1
+d6231 1
+a6231 1
+"<warning><placeholder-1/><placeholder-2/></warning>"
+d7015 1
+d7021 1
+a7021 2
+"XML source for document-specific <placeholder-2/><footnote><placeholder-3/></"
+"footnote>."
+@
+
+
+1.8
+log
+ at Finished docs for now
+@
+text
+ at d12 29
+a40 58
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu "
+"guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires "
+"VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend "
+"autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert "
+"articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap "
+"dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML "
+"tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man "
+"sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot "
+"developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro "
+"keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC "
+"configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG "
+"Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule "
+"Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote "
+"eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest "
+"Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text "
+"jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd "
+"colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES "
+"set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray "
+"ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG "
+"PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar "
+"Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse "
+"cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo "
+"imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject "
+"Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference "
+"rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef "
+"authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done "
+"Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered "
+"nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead "
+"Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas "
+"Redundâncias update yahoo VIMRUNTIME generated important \n"
+d47 1
+d459 1
+a459 1
+"<!--$Id: pt.po,v 1.7 2007/04/25 11:30:05 zepires Exp $ -->\n"
+d470 1
+a470 1
+"<!--$Id: pt.po,v 1.7 2007/04/25 11:30:05 zepires Exp $ -->\n"
+@
+
+
+1.7
+log
+ at Finished docs for now
+@
+text
+ at d5 1
+a5 1
+"PO-Revision-Date: 2007-04-25 12:13+0100\n"
+d487 1
+a487 1
+"<!--$Id: xml-tags.xml,v 1.5 2007/02/04 14:55:28 pfrields Exp $ -->\n"
+d498 1
+a498 1
+"<!--$Id: pt.po,v 1.6 2007/04/24 10:36:55 zepires Exp $ -->\n"
+d2418 1
+d3758 2
+a3759 9
+"O VIM poderá acelerar a criação do seu DocBook, mapeando as teclas escritas "
+"com mais frequência (ou palavras ou frases) em combinações de teclas breves. "
+"Por omissão, o líder do mapa de teclados é a barra invertida (<literal>\\</"
+"literal>), mas poderá ser redefinida com um comando do tipo <userinput>let "
+"mapleader =\n"
+" \",\"</userinput>. Existem duas formas de usar o seguinte exemplo; "
+"podê-lo-á colocar direcamente no seu ficheiro <filename>.vimrc</filename> ou "
+"podê-lo-a gravar num ficheiro separado e fazendo referência com o comando "
+"<userinput>source</userinput> no seu <filename>.vimrc</filename>. <screen>\n"
+d3779 1
+a3779 2
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+d3783 1
+a3783 1
+"</screen>\n"
+@
+
+
+1.6
+log
+ at Finished docs for now
+@
+text
+ at d4 2
+a5 2
+"POT-Creation-Date: 2007-04-18 10:54+0100\n"
+"PO-Revision-Date: 2007-04-24 11:30+0100\n"
+d12 58
+a69 29
+"X-POFile-SpellExtra: MegaCoder all gt XMLFILEStemplate nuno netruo edu guiicon disk glossentry row Bold VHDCI tarball init Fontifying \n"
+"X-POFile-SpellExtra: SimpleList colwidth include tb nomeunico zepires VERSION figs fileref seealso Joshua partintro imagedata lisp XYZ \n"
+"X-POFile-SpellExtra: CVSROOT basica Tab portable ze stickstr Ret linkend autoindent Heritage wordasword glosslist pts section decoding \n"
+"X-POFile-SpellExtra: install tags Documentation let address convert articleinfo guide Home Style Object DOCID ROMs bs RET FC xrdb txt usr \n"
+"X-POFile-SpellExtra: type hostbus Chuck mapleader American word setup cap dev can of simplelist Wade example prompt share agent \n"
+"X-POFile-SpellExtra: nomenclaturas tag caution phrase TOC ispell PSGML tgroup Terms refcard tbody XEmacs VariableList textobject xhtml \n"
+"X-POFile-SpellExtra: indexterm config firstname cpio fd fi Model Adaptec man sy entry YMMDD documentation sw Parsed né sn ethernet QLA \n"
+"X-POFile-SpellExtra: help cols trade sysconfig keyboard PRILANG cvsroot developer guimenu img lt ls ndash ced \n"
+"X-POFile-SpellExtra: docs alist AMMDD not Roozbeh term name RELAX icheiro keycap Parse merge mode APC en End suretecsystems License year \n"
+"X-POFile-SpellExtra: Print Save Xconfigurator Waugh re reg EN University EC configuracao org beginning generate messages yum \n"
+"X-POFile-SpellExtra: guibutton redhat primary Electrical caltura partAP LANG Dictionary Screen mkdir system SWAK XMLFILES \n"
+"X-POFile-SpellExtra: Press matchit textwidth schema Improved Buster consule Rpare GRAPHICAL part copy holder wide ItemizedList grep FCVER \n"
+"X-POFile-SpellExtra: xmlto nXML itemizedlist and surname menuchoice footnote eps Window Main option RPS xref POT ENTITIES emphasis build \n"
+"X-POFile-SpellExtra: command iso sect Off joshuadfranklin object Manifest Enter device The Tommy OrderedList class paiu enfâse don url \n"
+"X-POFile-SpellExtra: doc partition JPG repositorio ext clean xinit text jrfuller syntax sfdisk ksconfig title \n"
+"X-POFile-SpellExtra: orderedlist Free LEGALNOTICE Pournader Load hotmail dd colname accel ulink replaceable Quick guimenuitem ENTITY \n"
+"X-POFile-SpellExtra: secondary Help sufciente common fixed tfox DOCENTITIES set DOCBASE guilabel frame FDL sgml see infrastructure \n"
+"X-POFile-SpellExtra: enhanced Ph Po PT ul filename computeroutput Johnray ambiguidadde PO ecesso nohlsearch Sans screen citetitle \n"
+"X-POFile-SpellExtra: jo Exp article seccao vimrc FEDORA RNC escritaq RNG PDFs login Strunk Contents load ch simplemente cd Online table \n"
+"X-POFile-SpellExtra: cp pr ps Relax px trademark pa Editing pl ravar Bluecurve XSLT with groupinstall Trang rngconv legalnotice imap \n"
+"X-POFile-SpellExtra: unify ghenry intro PUBLIC prolog roozbeh cons ip parse cluster vs NEWS id if author XPTO member parts Karsten XXI \n"
+"X-POFile-SpellExtra: psgml firstterm LVD IG dmesg Tripwire hwinfo imageobject Gavin indexterms variablelist setq onyline \n"
+"X-POFile-SpellExtra: Table the keysym Id keycombo colspec boot mediaobject Qlogic EPS yes kwade elc Xclients shortcut desktop source \n"
+"X-POFile-SpellExtra: nocompatible sparado save bin On format rnc Reference rng outronome MAILNOVIOLATIONS GDSG disks colnum smoore xsl \n"
+"X-POFile-SpellExtra: Fuller Guinness Sun System export home HD glossdef authorgroup Guilford listitem sshd vimtutor host direcamente \n"
+"X-POFile-SpellExtra: found Ua keycode chapter on sbin glossterm mdash done Jargon or varlistentry into Writing Environment nxml your \n"
+"X-POFile-SpellExtra: Assistant IDs NG width emacs icon Xresources registered nochunks Variablelist OTHERS Paradigm true info default up \n"
+"X-POFile-SpellExtra: us Nomenclaturas estatico lynx distclean thead Publishing MSV ap warning at ax Electronics Monospace RTFM tip sharif \n"
+"X-POFile-SpellExtra: autoamticamente application userinput AA refenciadas Redundâncias update yahoo VIMRUNTIME generated important \n"
+d77 1
+a77 1
+#: en_US/rpm-info.xml:20(rights)
+d81 1
+a81 1
+#: en_US/rpm-info.xml:21(version)
+d85 1
+a85 1
+#: en_US/rpm-info.xml:24(year)
+d89 1
+a89 1
+#: en_US/rpm-info.xml:25(year)
+d93 1
+a93 1
+#: en_US/rpm-info.xml:26(year)
+d97 1
+a97 1
+#: en_US/rpm-info.xml:27(year)
+d101 1
+a101 1
+#: en_US/rpm-info.xml:28(holder)
+d105 1
+a105 1
+#: en_US/rpm-info.xml:29(holder)
+d109 1
+a109 1
+#: en_US/rpm-info.xml:30(holder)
+d113 1
+a113 1
+#: en_US/rpm-info.xml:31(holder)
+d117 1
+a117 1
+#: en_US/rpm-info.xml:32(holder)
+d121 1
+a121 1
+#: en_US/rpm-info.xml:34(title)
+d125 1
+a125 1
+#: en_US/rpm-info.xml:35(desc)
+d127 2
+a128 1
+msgstr "As linhas-mestras e procedimentos para produzir a documentação do Fedora"
+d130 1
+a130 1
+#: en_US/rpm-info.xml:42(details)
+d134 1
+a134 1
+#: en_US/xml-tags.xml:13(title)
+d138 1
+a138 1
+#: en_US/xml-tags.xml:16(primary) en_US/xml-tags.xml:34(primary)
+d142 1
+a142 1
+#: en_US/xml-tags.xml:17(secondary)
+d146 42
+a187 1
+#: en_US/xml-tags.xml:18(see) en_US/xml-tags.xml:167(primary) en_US/xml-tags.xml:205(primary) en_US/xml-tags.xml:241(primary) en_US/xml-tags.xml:276(primary) en_US/xml-tags.xml:361(primary) en_US/xml-tags.xml:386(primary) en_US/xml-tags.xml:417(primary) en_US/xml-tags.xml:471(primary) en_US/xml-tags.xml:523(primary) en_US/xml-tags.xml:555(primary) en_US/xml-tags.xml:593(primary) en_US/xml-tags.xml:659(primary) en_US/xml-tags.xml:667(primary) en_US/xml-tags.xml:673(primary) en_US/xml-tags.xml:703(primary) en_US/xml-tags.xml:709(primary) en_US/xml-tags.xml:739(primary) en_US/xml-tags.xml:745(primary) en_US/xml-tags.xml:774(primary) en_US/xml-tags.xml:780(primary) en_US/xml-tags.xml:785(primary) en_US/xml-tags.xml:791(primary) en_US/xml-tags.xml:833(primary) en_US/xml-tags.xml:861(primary) en_US/xml-tags.xml:908(primary) en_US/xml-tags.xml:963(primary) en_US/xml-tags.xml:968(primary) en_US/xml-tags.xml:1037(primary) en_US/xml-tags.xml:1047(primary) en_US/xml-tags.xml:1124(prima
ry) en_US/xml-tags.xml:1129(primary) en_US/xml-tags.xml:1219(primary) en_US/xml-tags.xml:1224(primary) en_US/xml-tags.xml:1402(primary) en_US/xml-tags.xml:1407(primary) en_US/xml-tags.xml:1490(primary) en_US/xml-tags.xml:1533(primary) en_US/xml-tags.xml:1642(primary) en_US/xml-tags.xml:1688(primary) en_US/xml-tags.xml:1738(primary) en_US/xml-tags.xml:1782(primary) en_US/xml-tags.xml:1812(primary) en_US/xml-tags.xml:1983(primary) en_US/xml-tags.xml:2055(primary) en_US/xml-tags.xml:2174(primary) en_US/xml-tags.xml:2313(primary) en_US/xml-tags.xml:2341(primary) en_US/xml-tags.xml:2396(primary) en_US/xml-tags.xml:2437(primary) en_US/xml-tags.xml:2484(primary) en_US/writing-guidelines.xml:41(primary) en_US/writing-guidelines.xml:54(primary) en_US/writing-guidelines.xml:266(primary) en_US/writing-guidelines.xml:271(primary) en_US/writing-guidelines.xml:276(primary) en_US/writing-guidelines.xml:281(primary) en_US/writing-guidelines.xml:286(primary) en_US/writing-guidelines.xml:291(
primary) en_US/writing-guidelines.xml:297(primary) en_US/writing-guidelines.xml:303(primary) en_US/writing-guidelines.xml:309(primary) en_US/writing-guidelines.xml:315(primary) en_US/writing-guidelines.xml:341(primary) en_US/writing-guidelines.xml:346(primary) en_US/writing-guidelines.xml:351(primary) en_US/writing-guidelines.xml:356(primary) en_US/writing-guidelines.xml:361(primary)
+d191 23
+a213 7
+#: en_US/xml-tags.xml:21(para)
+msgid "Please read this chapter carefully. This chapter describes the tags used by the Docs Project. Some of the rules described are specific to the project."
+msgstr "Leia por favor este capítulo com cuidado. O mesmo descreve as marcas usadas pelo Projecto de Documentação. Algumas das regras aqui descritas são específicas do projecto."
+
+#: en_US/xml-tags.xml:26(para)
+msgid "If these tags are used appropriately, document searches will provide meaningful results. These tags help search engines identify the information relevant to the search request. Another benefit is that all Fedora Project documents will have a similar look and feel (however, they will have some differences depending upon the output format)."
+msgstr "Se estas marcas forem usadas de forma apropriada, as pesquisas no documento irão oferecer resultados significativos. Estas marcas ajudam os motores de busca a identificar a informação relevante para o pedido de pesquisa. Outro benefício é o facto de todos os documentos do Projecto Fedora terão uma aparência e comportamento semelhante (contudo, terão algumas diferenças que dependem do formato de saída)."
+d215 1
+a215 1
+#: en_US/xml-tags.xml:35(secondary)
+d219 33
+a251 11
+#: en_US/xml-tags.xml:38(para)
+msgid "Most tags in XML must have an opening and closing tag. A few tags, such as <sgmltag class=\"emptytag\">xref</sgmltag>, have no content and close themselves. Additionally, proper XML conventions say that there must be a unique identifier for sections, chapters, figures, tables, and so on, so that they may be correctly identified, and cross referenced if needed."
+msgstr "A maior parte das marcas em XML deverão ter uma marca de abertura e de fecho. Algumas marcas, como a <sgmltag class=\"emptytag\">xref</sgmltag>, não têm conteúdo, pelo que se fecham a si próprias. Adicionalmente, as convenções adequadas em XML dizem que deverá existir um identificador único para as secções, capítulos, figuras, tabelas, entre outros, para que possam ser identificadas e refenciadas correctamente se necessário."
+
+#: en_US/xml-tags.xml:45(para)
+msgid "Although XML is capable of handling many document types, the format discussed here is the article format."
+msgstr "Ainda que o XML seja capaz de lidar com muitos tipos de documentos, o formato aqui discutido é o formato dos artigos."
+
+#: en_US/xml-tags.xml:48(para) en_US/writing-guidelines.xml:32(para)
+msgid "This chapter only discusses tags used for documentation for the Fedora Project, not all available DocBook XML tags. For the complete list, refer to <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr "Este capítulo só discute as marcas usadas na documentação do Projecto Fedora, não refere todas as marcas de XML do DocBook. Para uma lista completa, veja em <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+d253 1
+a253 1
+#: en_US/xml-tags.xml:56(title)
+d257 1
+a257 1
+#: en_US/xml-tags.xml:59(primary) en_US/writing-guidelines.xml:137(primary)
+d261 2
+a262 1
+#: en_US/xml-tags.xml:60(secondary) en_US/writing-guidelines.xml:138(secondary)
+d266 9
+a274 3
+#: en_US/xml-tags.xml:63(para)
+msgid "It is very important that you remember the caveats in this section. Even though they are more strict than valid DocBook XML, these rules exist so that both the HTML and PDF outputs look proper."
+msgstr "É bastante importante que recorde as contrapartidas desta secção. Ainda que sejam mais restritas que o DocBook em XML válido, estas regras existem para que os resultados em HTML e PDF apareçam válidos."
+d276 1
+a276 1
+#: en_US/xml-tags.xml:71(term) en_US/writing-guidelines.xml:149(term)
+d280 49
+a328 19
+#: en_US/xml-tags.xml:73(para)
+msgid "Do not use the trademark entities <sgmltag class=\"genentity\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class=\"genentity\">reg</sgmltag> because they do not produce HTML output that works for all charsets. The HTML output produces by these entities are declared in the DTD and cannot be changed via the stylesheet."
+msgstr "Não use as entidades de marcas registadas <sgmltag class=\"genentity\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag> ou <sgmltag class=\"genentity\">reg</sgmltag>, porque não produzem HTML válido que funcione em todas as codificações de caracteres. O resultado em HTML produzido por estas entidades está descrito na DTD e não pode ser alterado com a folha de estilo."
+
+#: en_US/xml-tags.xml:80(para)
+msgid "Instead, use the <sgmltag class=\"element\">trademark</sgmltag> tag and its associates classes as follows:"
+msgstr "Em vez disso, use a marca <sgmltag class=\"element\">trademark</sgmltag> e as suas classes associadas, como se segue:"
+
+#: en_US/xml-tags.xml:85(para) en_US/writing-guidelines.xml:164(para)
+msgid "<sgmltag class=\"starttag\">trademark</sgmltag>trademark symbol after me<sgmltag class=\"endtag\">trademark</sgmltag>"
+msgstr "<sgmltag class=\"starttag\">trademark</sgmltag>símbolo de marca a seguir a mim<sgmltag class=\"endtag\">trademark</sgmltag>"
+
+#: en_US/xml-tags.xml:91(para) en_US/writing-guidelines.xml:170(para)
+msgid "<sgmltag class=\"starttag\">trademark class=\"registered\"</sgmltag>registered trademark symbol after me<sgmltag class=\"endtag\">trademark</sgmltag>"
+msgstr "<sgmltag class=\"starttag\">trademark class=\"registered\"</sgmltag>símbolo de marca registada a seguir a mim<sgmltag class=\"endtag\">trademark</sgmltag>"
+
+#: en_US/xml-tags.xml:97(para) en_US/writing-guidelines.xml:176(para)
+msgid "<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag>copyright symbol after me<sgmltag class=\"endtag\">trademark</sgmltag>"
+msgstr "<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag>símbolo de direitos de cópia a seguir a mim<sgmltag class=\"endtag\">trademark</sgmltag>"
+d330 1
+a330 1
+#: en_US/xml-tags.xml:105(term) en_US/writing-guidelines.xml:184(term)
+d334 23
+a356 9
+#: en_US/xml-tags.xml:107(para)
+msgid "Do not use <sgmltag>para</sgmltag> tags around anything other than a simple paragraph. Doing so will create additional white space within the text itself in the PDF version."
+msgstr "Não use as marcas <sgmltag>para</sgmltag> em torno de tudo o que não seja um parágrafo simples. Ao fazê-lo, irá criar espaços em branco adicionais dentro do próprio texto, na versão em PDF."
+
+#: en_US/xml-tags.xml:112(para)
+msgid "Specifically, do not use <sgmltag>para</sgmltag> tags around the following (or, to put this another way, do not embed the following within <sgmltag>para</sgmltag> tags):"
+msgstr "Especificamente, não use as marcas <sgmltag>para</sgmltag> em torno do seguinte (ou, posto de outra forma, não incorpore o seguinte dentro das marcas <sgmltag>para</sgmltag>):"
+
+#: en_US/xml-tags.xml:118(sgmltag) en_US/xml-tags.xml:1810(command) en_US/xml-tags.xml:1813(secondary) en_US/writing-guidelines.xml:198(sgmltag)
+d360 3
+a362 1
+#: en_US/xml-tags.xml:121(sgmltag) en_US/xml-tags.xml:960(command) en_US/xml-tags.xml:964(command) en_US/xml-tags.xml:970(tertiary) en_US/xml-tags.xml:975(command) en_US/writing-guidelines.xml:201(sgmltag)
+d366 3
+a368 1
+#: en_US/xml-tags.xml:124(sgmltag) en_US/xml-tags.xml:1038(command) en_US/xml-tags.xml:1043(command) en_US/xml-tags.xml:1049(tertiary) en_US/writing-guidelines.xml:204(sgmltag)
+d372 3
+a374 1
+#: en_US/xml-tags.xml:127(sgmltag) en_US/xml-tags.xml:1125(command) en_US/xml-tags.xml:1131(tertiary) en_US/xml-tags.xml:1136(command) en_US/writing-guidelines.xml:207(sgmltag)
+d378 4
+a381 1
+#: en_US/xml-tags.xml:130(sgmltag) en_US/xml-tags.xml:2052(command) en_US/xml-tags.xml:2056(secondary) en_US/xml-tags.xml:2175(secondary) en_US/writing-guidelines.xml:111(sgmltag) en_US/writing-guidelines.xml:210(sgmltag)
+d385 19
+a403 7
+#: en_US/xml-tags.xml:136(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</sgmltag> tags"
+msgstr "Conteúdo dentro das marcas <sgmltag>para</sgmltag> dentro de marcas <sgmltag>listitem</sgmltag>"
+
+#: en_US/xml-tags.xml:139(para)
+msgid "Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</sgmltag> tags <emphasis>must</emphasis> start immediately after the beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr "O conteúdo dentro das marcas <sgmltag>para</sgmltag> inseridas em marcas <sgmltag>listitem</sgmltag> <emphasis>deverá</emphasis> começar logo a seguir à marca inicial <sgmltag class=\"starttag\">para</sgmltag>, para evitar espaços em branco extra na versão em PDF."
+d405 1
+a405 1
+#: en_US/xml-tags.xml:148(term) en_US/writing-guidelines.xml:227(term)
+d409 16
+a424 5
+#: en_US/xml-tags.xml:150(para) en_US/writing-guidelines.xml:229(para)
+msgid "The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) <emphasis>must</emphasis> be flush left in the XML file; otherwise, the extraneous whitespace will appear in the HTML version."
+msgstr "O conteúdo dentro das marcas <sgmltag>screen</sgmltag> (<sgmltag class=\"starttag\">screen</sgmltag> e <sgmltag class=\"endtag\">screen</sgmltag>) <emphasis>deverão</emphasis> ser retirados à esquerda no ficheiro em XML; caso contrário, os espaços em branco estranhos irão aparecer na versão em HTML."
+
+#: en_US/xml-tags.xml:164(sgmltag) en_US/xml-tags.xml:168(secondary) en_US/xml-tags.xml:182(sgmltag) en_US/xml-tags.xml:183(sgmltag) en_US/xml-tags.xml:184(sgmltag) en_US/xml-tags.xml:185(sgmltag)
+d428 7
+a434 3
+#: en_US/xml-tags.xml:171(para)
+msgid "An application is the name of a GUI software program. A command is the name of an executable (text) program or a software command."
+msgstr "Uma aplicação é o nome de um programa de 'software' gráfico. Um comando é o nome de um programa executável (em texto) ou um comando do sistema."
+d436 9
+a444 3
+#: en_US/xml-tags.xml:174(para)
+msgid "The <sgmltag class=\"starttag\">application</sgmltag> and <sgmltag class=\"endtag\">application</sgmltag> tags allow you to refer to an application or program. For example, the following XML:"
+msgstr "As marcas <sgmltag class=\"starttag\">application</sgmltag> e <sgmltag class=\"endtag\">application</sgmltag> permitem-lhe referenciar uma aplicação ou um programa. Por exemplo, o seguinte XML:"
+d446 1
+a446 1
+#: en_US/xml-tags.xml:180(computeroutput)
+d448 6
+a453 1
+msgid "\nTo view the Web in Linux, you can use\n<placeholder-1/>Mozilla<placeholder-2/> \nor <placeholder-3/>lynx<placeholder-4/> if\nyou only want a text-based browser.\n"
+d461 1
+a461 1
+#: en_US/xml-tags.xml:190(para)
+d465 7
+a471 3
+#: en_US/xml-tags.xml:194(para)
+msgid "To view the Web in Linux, you can use <application>Mozilla</application> or <application>lynx</application> if you only want a text-based browser."
+msgstr "Para ver a Web no Linux, poderá usar o <application>Mozilla</application> ou o <application>lynx</application> se só quiser um navegador em modo texto."
+d473 2
+a474 1
+#: en_US/xml-tags.xml:202(sgmltag) en_US/xml-tags.xml:206(secondary) en_US/writing-guidelines.xml:99(sgmltag)
+d478 1
+a478 1
+#: en_US/xml-tags.xml:209(para)
+d480 2
+a481 1
+msgstr "Um livro em DocBook poderá ser dividido em capítulos como os seguintes:"
+d483 1
+a483 1
+#: en_US/xml-tags.xml:214(computeroutput)
+d485 11
+a495 1
+msgid "\n<!--$Id: pt.po,v 1.5 2007/04/24 01:53:28 zepires Exp $ -->\n\n <chapter id=\"ch-sample\">\n <title>Sample Chapter</title>\n\n <para>This is a sample chapter, showing you the XML tags used to create a\n chapter, sections, and subsections.</para>\n \n </chapter>\n"
+d498 1
+a498 1
+"<!--$Id: pt.po,v 1.5 2007/04/24 01:53:28 zepires Exp $ -->\n"
+d508 9
+a516 3
+#: en_US/xml-tags.xml:227(para)
+msgid "The chapter can also be further divided into sections (<sgmltag>section</sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). Refer to <xref linkend=\"sn-xml-tags-sections\"/> for details."
+msgstr "O capítulo poderá também ser dividido em secções (<sgmltag>section</sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). Veja mais detalhes em <xref linkend=\"sn-xml-tags-sections\"/>."
+d518 2
+a519 1
+#: en_US/xml-tags.xml:238(sgmltag) en_US/xml-tags.xml:242(secondary) en_US/xml-tags.xml:262(sgmltag) en_US/xml-tags.xml:262(sgmltag)
+d523 21
+a543 7
+#: en_US/xml-tags.xml:249(para)
+msgid "An entity is a short hand way of referring to some predefined content, such as a title or name. It can be defined within the parent document or within a set of files that your DTD references for your specific documentation set."
+msgstr "Um entidade é uma forma resumida de fazer referẽncia a algum conteúdo predefinido, como um título ou um nome. Poderá ser definida dentro do documento-pai ou dentro de um conjunto de ficheiros que a sua DTD faça referência, para o seu conjunto de documentação específico."
+
+#: en_US/xml-tags.xml:246(para)
+msgid "The <sgmltag>citetitle</sgmltag> tag provides formatting for a specific references (title can be manually typed out or if already defined within your document set, given as an entity<footnote><placeholder-1/></footnote> )."
+msgstr "A marca <sgmltag>citetitle</sgmltag> produz a formatação para uma referência específica (o título poderá ser escrito manualmente ou, se já estiver definido dentro do seu conjunto de documentos, indicado como uma entidade<footnote><placeholder-1/></footnote> )."
+d545 1
+a545 1
+#: en_US/xml-tags.xml:257(para) en_US/xml-tags.xml:2456(para)
+d549 1
+a549 1
+#: en_US/xml-tags.xml:262(sgmltag)
+d553 1
+a553 1
+#: en_US/xml-tags.xml:261(computeroutput)
+d555 6
+a560 2
+msgid "\n<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+msgstr "\n<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+d562 7
+a568 3
+#: en_US/xml-tags.xml:265(para)
+msgid "The output looks like <citetitle>Installation Guide</citetitle> because <sgmltag class=\"genentity\">IG</sgmltag> is an entity."
+msgstr "O resultado fica semelhante a <citetitle>Guia de Instalação</citetitle>, porque o <sgmltag class=\"genentity\">IG</sgmltag> é uma entidade."
+d570 1
+a570 1
+#: en_US/xml-tags.xml:273(sgmltag) en_US/xml-tags.xml:277(secondary)
+d574 29
+a602 11
+#: en_US/xml-tags.xml:280(para)
+msgid "An application is the name of a GUI software program. A command is the name of an executable (text) program or a software command. Any program that is a command line or text-based only tool is marked with <sgmltag>command</sgmltag> tags."
+msgstr "Uma aplicação é o nome de um programa de 'software' gráfico. Um comando é o nome de um programa executável (em texto) ou um comando do sistema. Todos os programas que sejam ferramentas da linha de comandos ou apenas para modo texto são marcados com as marcas <sgmltag>command</sgmltag>."
+
+#: en_US/xml-tags.xml:286(para)
+msgid "If you have text that is a command, use the <sgmltag class=\"starttag\">command</sgmltag> and <sgmltag class=\"endtag\">command</sgmltag> tags such as:"
+msgstr "Se tiver texto que seja um comando, use as marcas <sgmltag class=\"starttag\">command</sgmltag> e <sgmltag class=\"endtag\">command</sgmltag>, como no exemplo:"
+
+#: en_US/xml-tags.xml:294(computeroutput)
+#, no-wrap
+msgid "\nTo change your keyboard after installation, become root \nand use the <command>redhat-config-keyboard</command> command, \nor you can type <command>setup</command> at the root prompt.\n"
+d609 12
+a620 1
+#: en_US/xml-tags.xml:301(para) en_US/xml-tags.xml:374(para) en_US/xml-tags.xml:402(para) en_US/xml-tags.xml:446(para) en_US/xml-tags.xml:485(para) en_US/xml-tags.xml:500(para) en_US/xml-tags.xml:540(para) en_US/xml-tags.xml:575(para) en_US/xml-tags.xml:689(para) en_US/xml-tags.xml:725(para) en_US/xml-tags.xml:759(para) en_US/xml-tags.xml:816(para) en_US/xml-tags.xml:849(para) en_US/xml-tags.xml:887(para) en_US/xml-tags.xml:927(para) en_US/xml-tags.xml:1515(para) en_US/xml-tags.xml:1756(para) en_US/xml-tags.xml:1800(para) en_US/xml-tags.xml:1868(para) en_US/xml-tags.xml:2357(para) en_US/xml-tags.xml:2411(para) en_US/xml-tags.xml:2464(para) en_US/xml-tags.xml:2504(para)
+d624 9
+a632 3
+#: en_US/xml-tags.xml:304(para)
+msgid "To change your keyboard after installation, become root and use the <command>redhat-config-keyboard</command> command, or you can type <command>setup</command> at the root prompt."
+msgstr "Para mudar o seu teclado após a instalação, torne-se 'root' e use o comando <command>redhat-config-keyboard</command> ou então escreva o comando <command>setup</command> na linha de comandos do 'root'."
+d634 1
+a634 1
+#: en_US/xml-tags.xml:310(para)
+d638 1
+a638 1
+#: en_US/xml-tags.xml:313(computeroutput)
+d640 7
+a646 1
+msgid "\n<command>MAILNOVIOLATIONS</command> — If set\nto <command>true</command> this option tells Tripwire to\nemail a report at a regular interval regardless of whether or not\nany violations have occured. The default value is\n<command>true</command>.\n"
+d655 1
+a655 1
+#: en_US/xml-tags.xml:322(para)
+d659 19
+a677 5
+#: en_US/xml-tags.xml:326(para)
+msgid "<command>MAILNOVIOLATIONS</command>— If set to <command>true</command> this variable tells Tripwire to email a report at a regular interval regardless of whether or not any violations have occured. The default value is <command>true</command>."
+msgstr "<command>MAILNOVIOLATIONS</command> — Se estiver definido como <command>true</command>, esta opção indica ao Tripwire para enviar por e-mail um relatório com um intervalo regular, independentemente das violações que tiverem ocorrido. O valor por omissão é <command>true</command>."
+
+#: en_US/xml-tags.xml:334(title) en_US/xml-tags.xml:509(title) en_US/xml-tags.xml:988(title) en_US/xml-tags.xml:1063(title) en_US/xml-tags.xml:1147(title) en_US/xml-tags.xml:1387(title) en_US/xml-tags.xml:1500(title) en_US/xml-tags.xml:1769(title) en_US/xml-tags.xml:1930(title) en_US/xml-tags.xml:2422(title) en_US/writing-guidelines.xml:394(title) en_US/emacs.xml:265(title) en_US/emacs.xml:565(title) en_US/emacs-nxml.xml:160(title)
+d681 22
+a702 7
+#: en_US/xml-tags.xml:334(para)
+msgid "In this example, the option value (true) is defined with a <command> tag set. Because a option is a configuration file option (command line options which would use the <option> tag set), and because there is no configuration file option tag available to use, we are extending the <command> tag set to define options in a configuration file."
+msgstr "Neste exemplo, o valor de 'option' ('true') está definido com uma marca <command> atribuída. Dado que uma 'option' é uma opção do ficheiro de configuração (as opções das linhas de comandos devem usar a marca <option>), e dado que não existe nenhuma marca de opção de ficheiros de configuração para usar, será extendida a marca <command> para definir opções num ficheiro de configuração."
+
+#: en_US/xml-tags.xml:342(para)
+msgid "Terms marked with <command>command</command> tags because there aren't exact tags for them:"
+msgstr "Os termos marcados como <command>command</command>, porque não existem marcas exactas para eles:"
+d704 1
+a704 1
+#: en_US/xml-tags.xml:348(para)
+d708 1
+a708 1
+#: en_US/xml-tags.xml:351(para)
+d712 1
+a712 1
+#: en_US/xml-tags.xml:358(command) en_US/xml-tags.xml:362(secondary)
+d716 1
+a716 1
+#: en_US/xml-tags.xml:365(para)
+d720 1
+a720 1
+#: en_US/xml-tags.xml:369(computeroutput)
+d722 6
+a727 2
+msgid "\n<computeroutput>Do you want to delete this file? y n</computeroutput>\n"
+msgstr "\n<computeroutput>Deseja remover este ficheiro? s n</computeroutput>\n"
+d729 1
+a729 1
+#: en_US/xml-tags.xml:378(computeroutput)
+d734 1
+a734 1
+#: en_US/xml-tags.xml:383(command) en_US/xml-tags.xml:387(secondary)
+d738 7
+a744 3
+#: en_US/xml-tags.xml:390(para)
+msgid "To emphasis content, use the <command><emphasis></command> and <command></emphasis></command> tags. For example:"
+msgstr "Para aumentar a ênfase sobre o conteúdo, use as marcas <command><emphasis></command> e <command></emphasis></command>. Por exemplo:"
+d746 1
+a746 1
+#: en_US/xml-tags.xml:395(computeroutput)
+d748 5
+a752 1
+msgid "\nThis installation <emphasis>will remove all</emphasis> existing\nLinux partitions on <emphasis>all</emphasis> hard drives in your\nsystem; non-Linux partitions will not be removed.\n"
+d760 9
+a768 3
+#: en_US/xml-tags.xml:406(para)
+msgid "This installation <emphasis>will remove all</emphasis> existing Linux partitions on <emphasis>all</emphasis> hard drives in your system; non-Linux partitions will not be removed."
+msgstr "Esta instalação <emphasis> irá remover todas as </emphasis>partições de Linux existentes em <emphasis>todos</emphasis> os discos rígidos do seu sistema; as partições não-Linux não serão removidas."
+d770 2
+a771 1
+#: en_US/xml-tags.xml:414(command) en_US/xml-tags.xml:418(secondary) en_US/writing-guidelines.xml:123(sgmltag)
+d775 18
+a792 7
+#: en_US/xml-tags.xml:421(para)
+msgid "The <command><example></command> and <command></example></command> tags are used to format text within a document and is great for adding emphasis to show examples of code, exercises, and more."
+msgstr "As marcas <command><example></command> e <command></example></command> são usadas para formatar o texto dentro de um documento e são óptimas para adicionar alguma enfâse sobre exemplos de código, exercícios, entre outros."
+
+#: en_US/xml-tags.xml:426(para)
+msgid "The <command><example></command> tag set should be given an ID and title:"
+msgstr "A marca <command><example></command> definida deverá ter um ID e um título:"
+d794 1
+a794 1
+#: en_US/xml-tags.xml:429(screen)
+d796 16
+a811 1
+msgid "\n\t<example id=\"static-ip\">\n\t <title>Static IP Address using DHCP</title>\n\n<screen width=60>\n<computeroutput>\nhost apex {\n option host-name \"apex.example.com\";\n hardware ethernet 00:A0:78:8E:9E:AA; \n fixed-address 192.168.1.4;\n}\n<computeroutput>\n</screen>\n\n\t</example>\n"
+d829 1
+a829 1
+#: en_US/xml-tags.xml:451(title)
+d833 1
+a833 1
+#: en_US/xml-tags.xml:454(computeroutput)
+d835 7
+a841 1
+msgid "\nhost apex {\n option host-name \"apex.example.com\";\n hardware ethernet 00:A0:78:8E:9E:AA; \n fixed-address 192.168.1.4;\n}\n"
+d850 1
+a850 1
+#: en_US/xml-tags.xml:468(command) en_US/xml-tags.xml:472(secondary)
+d854 11
+a864 3
+#: en_US/xml-tags.xml:475(para)
+msgid "The <command><filename></command> and <command></filename></command> tags define a filename or path to a file. Since directories are just special files, they are marked with the <command>filename</command> tags as well. For example:"
+msgstr "As marcas <command><filename></command> e <command></filename></command> definem o nome ou o local de um ficheiro. Dado que as pastas são ficheiros especiais, são marcadas também com o <command>filename</command>. Por exemplo:"
+d866 1
+a866 1
+#: en_US/xml-tags.xml:481(screen)
+d868 4
+a871 1
+msgid "\nEdit the <filename>/home/smoore/sam.xml</filename> file to make\nchanges or add comments.\n"
+d877 7
+a883 3
+#: en_US/xml-tags.xml:488(para)
+msgid "Edit the <filename>/home/smoore/sam.xml</filename> file to make changes or add comments."
+msgstr "Edite o ficheiro <filename>/home/ze/nuno.xml</filename> para fazer alterações ou adicionar comentários."
+d885 1
+a885 1
+#: en_US/xml-tags.xml:493(para)
+d889 1
+a889 1
+#: en_US/xml-tags.xml:496(screen)
+d891 4
+a894 1
+msgid "\nTo use the <application>Keyboard Configuration Tool</application>, the\n<filename>system-config-keyboard</filename> RPM package must be installed.\n"
+d900 16
+a915 7
+#: en_US/xml-tags.xml:503(para)
+msgid "To use the <application>Keyboard Configuration Tool</application>, the <command>redhat-config-keyboard</command> RPM package must be installed."
+msgstr "Para usar a <application>Ferramenta de Configuração do Teclado</application>, o pacote RPM <filename>system-config-keyboard</filename> deverá estar instalado."
+
+#: en_US/xml-tags.xml:510(para)
+msgid "Directory names must end with a forward slash (<computeroutput>/</computeroutput>) to distinguish them from file names."
+msgstr "Os nomes das pastas deverão terminar com uma barra (<computeroutput>/</computeroutput>) para os distinguir dos nomes dos ficheiros."
+d917 1
+a917 1
+#: en_US/xml-tags.xml:520(command) en_US/xml-tags.xml:524(secondary)
+d921 9
+a929 3
+#: en_US/xml-tags.xml:527(para)
+msgid "The <command><firstterm></command> and <command></firstterm></command> tags helps to define a word that may be unfamiliar to the user, but that will be seen commonly throughout the text. For example:"
+msgstr "As marcas <command><firstterm></command> e <command></firstterm></command> ajudam a definir uma palavra que possa não parecer familiar ao utilizador, mas que aparecerá frequentemente ao longo do texto. Por exemplo:"
+d931 1
+a931 1
+#: en_US/xml-tags.xml:534(computeroutput)
+d933 4
+a936 1
+msgid "\nNearly every modern-day operating system uses <firstterm>disk\npartitions</firstterm>, and Fedora is no exception.\n"
+d942 7
+a948 3
+#: en_US/xml-tags.xml:544(para)
+msgid "Nearly every modern-day operating system uses <firstterm>disk partitions</firstterm>, and Fedora is no exception."
+msgstr "Praticamente todos os sistemas operativos modernos usam as <firstterm>partições de disco</firstterm> e o Fedora não é excepção."
+d950 1
+a950 1
+#: en_US/xml-tags.xml:552(command) en_US/xml-tags.xml:556(secondary)
+d954 1
+a954 1
+#: en_US/xml-tags.xml:559(para)
+d958 1
+a958 1
+#: en_US/xml-tags.xml:563(computeroutput)
+d960 10
+a969 1
+msgid "\nFor those of you who need to perform a server-class\n<footnote>\n<para>\nA server-class installation sets up a typical server\nenvironment. Note, no graphical environment is \ninstalled during a server-class installation.\n</para> \n</footnote> installation, refer to the <citetitle>Installation Guide</citetitle>.\n"
+d981 19
+a999 7
+#: en_US/xml-tags.xml:580(para)
+msgid "A server-class installation sets up a typical server environment. Please note, no graphical environment is installed during a server-class installation."
+msgstr "Uma instalação para servidores configura um ambiente típico de servidores. Como nota, não é instalado nenhum ambiente gráfico durante uma instalação para servidores."
+
+#: en_US/xml-tags.xml:579(para)
+msgid "For those of you who need to perform a server-class <footnote><placeholder-1/></footnote> installation, refer to the <citetitle>Installation Guide</citetitle>."
+msgstr "Para os que precisam de efectuar uma instalação para servidores <footnote><placeholder-1/></footnote>, veja no <citetitle>Guia de Instalação</citetitle>."
+d1001 2
+a1002 1
+#: en_US/xml-tags.xml:590(command) en_US/xml-tags.xml:594(secondary) en_US/writing-guidelines.xml:107(sgmltag)
+d1006 2
+a1007 1
+#: en_US/xml-tags.xml:598(title) en_US/xml-tags.xml:1827(title) en_US/writing-guidelines.xml:424(title) en_US/emacs-nxml.xml:96(title)
+d1011 6
+a1016 3
+#: en_US/xml-tags.xml:599(para)
+msgid "Order matters! The EPS file <emphasis>must</emphasis> be declared first."
+msgstr "A ordem importa! O ficheiro EPS <emphasis>deverá</emphasis> estar declarado primeiro."
+d1018 1
+a1018 1
+#: en_US/xml-tags.xml:605(para)
+d1022 1
+a1022 1
+#: en_US/xml-tags.xml:610(computeroutput)
+d1024 20
+a1043 1
+msgid "\n<figure id=\"fig-ksconfig-basic\">\n <title>Basic Configuration</title>\n <mediaobject>\n <imageobject>\n <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.eps\"\n format=\"EPS\"/>\n </imageobject>\n <imageobject>\n <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.png\"\n format=\"PNG\"/>\n </imageobject>\n <textobject>\n <phrase>\n Some text description of this image\n </phrase>\n </textobject>\n </mediaobject>\n</figure>\n"
+d1065 1
+a1065 1
+#: en_US/xml-tags.xml:632(para)
+d1069 1
+a1069 1
+#: en_US/xml-tags.xml:637(emphasis)
+d1073 1
+a1073 1
+#: en_US/xml-tags.xml:639(emphasis)
+d1077 1
+a1077 1
+#: en_US/xml-tags.xml:641(emphasis)
+d1081 1
+a1081 1
+#: en_US/xml-tags.xml:643(emphasis)
+d1085 1
+a1085 1
+#: en_US/xml-tags.xml:645(emphasis)
+d1089 1
+a1089 1
+#: en_US/xml-tags.xml:636(screen)
+d1091 11
+a1101 1
+msgid "\n<figure id=\"fig-ksconfig-basic\"> <placeholder-1/>\n\n<title>Basic Configuration</title> <placeholder-2/>\n\nfileref=\"./figs/ksconfig/ksconfig-basics.eps\"> <placeholder-3/>\n\nfileref=\"./figs/ksconfig/ksconfig-basics.png\"> <placeholder-4/>\n \n<phrase>Some text description of this image</phrase> <placeholder-5/>\n"
+d1114 7
+a1120 3
+#: en_US/xml-tags.xml:648(para)
+msgid "For more information on taking screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr "Para mais informações sobre como tirar fotografias, veja em <xref linkend=\"sn-screenshots\"/>."
+d1122 1
+a1122 1
+#: en_US/xml-tags.xml:656(title)
+d1126 3
+a1128 1
+#: en_US/xml-tags.xml:660(secondary) en_US/xml-tags.xml:668(secondary) en_US/xml-tags.xml:704(secondary) en_US/xml-tags.xml:740(secondary) en_US/xml-tags.xml:775(secondary) en_US/xml-tags.xml:786(secondary)
+d1132 2
+a1133 1
+#: en_US/xml-tags.xml:664(command) en_US/xml-tags.xml:669(tertiary) en_US/xml-tags.xml:674(secondary)
+d1137 9
+a1145 3
+#: en_US/xml-tags.xml:677(para)
+msgid "Use the <command><guilabel></command> and <command></guilabel></command> tags as a default for GUI descriptions, like a screen name or screen title. For example:"
+msgstr "Use as marcas <command><guilabel></command> e <command></guilabel></command> por omissão para descrições gráficas, como o nome ou um título de um ecrã. Por exemplo:"
+d1147 1
+a1147 1
+#: en_US/xml-tags.xml:683(computeroutput)
+d1149 4
+a1152 1
+msgid "\nThe <guilabel>Authentication Configuration</guilabel> screen \nshows you how to make your system more secure.\n"
+d1158 7
+a1164 3
+#: en_US/xml-tags.xml:693(para)
+msgid "The <guilabel>Authentication Configuration</guilabel> screen shows you how to make your system more secure."
+msgstr "O ecrã de <guilabel>Configuração da Autenticação</guilabel> mostra-lhe como tornar o seu sistema mais seguro."
+d1166 2
+a1167 1
+#: en_US/xml-tags.xml:700(command) en_US/xml-tags.xml:705(tertiary) en_US/xml-tags.xml:710(secondary)
+d1171 7
+a1177 3
+#: en_US/xml-tags.xml:713(para)
+msgid "Use the <command><guibutton></command> and <command></guibutton></command> tags to denote a button on a screen or menu. For example:"
+msgstr "Use as marcas <command><guibutton></command> e <command></guibutton></command> para demarcar um botão num ecrã ou menu. Po exemplo:"
+d1179 1
+a1179 1
+#: en_US/xml-tags.xml:719(computeroutput)
+d1181 4
+a1184 1
+msgid "\nCheck the <guibutton>Activate on boot</guibutton> button \nto have the X Window System start automatically.\n"
+d1190 7
+a1196 3
+#: en_US/xml-tags.xml:729(para)
+msgid "Check the <guibutton>Activate on boot</guibutton> button to have the X Window System start automatically."
+msgstr "Assinale o botão <guibutton>Activar no arranque</guibutton> para que o X Window System se inicie automaticamente."
+d1198 2
+a1199 1
+#: en_US/xml-tags.xml:736(command) en_US/xml-tags.xml:741(tertiary) en_US/xml-tags.xml:746(secondary)
+d1203 8
+a1210 3
+#: en_US/xml-tags.xml:749(para)
+msgid "The <command><guiicon></command> and <command></guiicon></command> tags are used to denote a panel or desktop icon. For example:"
+msgstr "As marcas <command><guiicon></command> e <command></guiicon></command> são usadas para demarcar um ícone do painel ou do ambiente de trabalho. Por exemplo:"
+d1212 1
+a1212 1
+#: en_US/xml-tags.xml:754(computeroutput)
+d1214 6
+a1219 2
+msgid "\nDouble-click the <guiicon>Start Here</guiicon> icon on the desktop.\n"
+msgstr "\nFaça duplo-click no ícone <guiicon>Iniciar Aqui</guiicon> do ecrã.\n"
+d1221 1
+a1221 1
+#: en_US/xml-tags.xml:763(para)
+d1225 1
+a1225 1
+#: en_US/xml-tags.xml:770(title)
+d1229 1
+a1229 1
+#: en_US/xml-tags.xml:776(tertiary) en_US/xml-tags.xml:781(secondary)
+d1233 1
+a1233 1
+#: en_US/xml-tags.xml:787(tertiary) en_US/xml-tags.xml:792(secondary)
+d1237 30
+a1266 11
+#: en_US/xml-tags.xml:795(para)
+msgid "To note a menu (like in the installation program or within the control panel), use the <command><guimenu></command> and <command></guimenu></command> tags."
+msgstr "Para definir um menu (como aparece no programa de instalação ou no centro de controlo), use as marcas <command><guimenu></command> e <command></guimenu></command>."
+
+#: en_US/xml-tags.xml:801(para)
+msgid "To note submenu items, use the <command><guimenuitem></command> and <command></guimenuitem></command> tags. (Please note that there should not be any breaks between these commands, but for printing purposes breaks have been inserted). For example:"
+msgstr "Para definir os itens dos sub-menus, use as marcas <command><guimenuitem></command> e <command></guimenuitem></command>. (Repare que não deverão existir nenhumas quebras entre estes comandos mas, para fins de impressão, poderão ter sido inseridas quebras). Por exemplo:"
+
+#: en_US/xml-tags.xml:808(computeroutput)
+#, no-wrap
+msgid "\nSelect \n<guimenu>Main Menu</guimenu> =>\n\t <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> to start the \n<application>Emacs</application> text editor.\n"
+d1274 9
+a1282 3
+#: en_US/xml-tags.xml:820(para)
+msgid "From the control panel, click on <guimenu>Main Menu</guimenu> => <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> to start the <application>Emacs</application> text editor."
+msgstr "No painel de controlo, seleccione <guimenu>Menu Principal</guimenu> => <guimenuitem>Programação</guimenuitem> => <guimenuitem>Emacs</guimenuitem> para iniciar o editor de texto <application>Emacs</application>."
+d1284 1
+a1284 1
+#: en_US/xml-tags.xml:830(command) en_US/xml-tags.xml:834(secondary)
+d1288 11
+a1298 3
+#: en_US/xml-tags.xml:837(para)
+msgid "To denote a specific key, you will need to use the <command><keycap></command> and <command></keycap></command> tags. Brackets are automatically added around the keycap, so do not add them in your XML code. For example:"
+msgstr "Para apresentar uma tecla específica, terá de usar as marcas <command><keycap></command> e <command></keycap></command>. Os parêntesis rectos serão adicionados automaticamente em torno da tecla, por isso não os adicione no seu código em XML. Por exemplo:"
+d1300 1
+a1300 1
+#: en_US/xml-tags.xml:844(computeroutput)
+d1302 6
+a1307 2
+msgid "\nTo make your selection, press the <keycap>Enter</keycap> key.\n"
+msgstr "\nPara fazer a sua selecção, carregue na tecla <keycap>Enter</keycap>.\n"
+d1309 1
+a1309 1
+#: en_US/xml-tags.xml:853(para)
+d1313 1
+a1313 1
+#: en_US/xml-tags.xml:858(command) en_US/xml-tags.xml:862(secondary)
+d1317 13
+a1329 3
+#: en_US/xml-tags.xml:865(para)
+msgid "Often using a mouse is tedious for common tasks. Therefore, programmers often build in keyboard-shortcuts to simplify their program. These should be described using the shortcut tag as a wrapper for the keyboard tags. The shortcut tag must be wrapped inside the menuchoice tag. For example:"
+msgstr "Normalmente, a utilização de um rato é aborrecida para as tarefas comuns. Como tal, os programadores baseiam-se frequentemente nas combinações de teclas de atalho para simplificar o seu programa. Estas deverão ser descritas com a marca 'shortcut', como uma envolvência para as marcas de teclado. A marca 'shortcut' deverá estar envolvida dentro da marca 'menuchoice'. Por exemplo:"
+d1331 1
+a1331 1
+#: en_US/xml-tags.xml:874(computeroutput)
+d1333 10
+a1342 1
+msgid "\nGo to the menu bar and choose: \n <menuchoice>\n <shortcut>\n <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>\n </shortcut>\n <guimenu><accel>F</accel>ile</guimenu>\n <guimenuitem><accel>S</accel>ave</guimenuitem>\n </menuchoice>.\n"
+d1354 10
+a1363 3
+#: en_US/xml-tags.xml:891(para)
+msgid "Go to the menu bar and choose: <menuchoice><shortcut><keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo></shortcut><guimenu><accel>F</accel>ile</guimenu><guimenuitem><accel>S</accel>ave</guimenuitem></menuchoice>."
+msgstr "Vá para a barra de menu e escolha: <menuchoice><shortcut><keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo></shortcut><guimenu><accel>F</accel>icheiro</guimenu><guimenuitem><accel>G</accel>ravar</guimenuitem></menuchoice>."
+d1365 1
+a1365 1
+#: en_US/xml-tags.xml:905(command) en_US/xml-tags.xml:909(secondary)
+d1369 10
+a1378 3
+#: en_US/xml-tags.xml:912(para)
+msgid "To illustrate a key combination, you need to use the <command><keycombo></command> and <command></keycombo></command>, <command><keycap></command> and <command></keycap></command> tags. For example:"
+msgstr "Para ilustrar uma combinação de teclas, terá de usar as marcas <command><keycombo></command> e <command></keycombo></command>, <command><keycap></command> e <command></keycap></command>. Por exemplo:"
+d1380 1
+a1380 1
+#: en_US/xml-tags.xml:920(computeroutput)
+d1382 5
+a1386 1
+msgid "\nTo reboot your system, press <keycombo>\n<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>\n</keycombo>.\n"
+d1393 7
+a1399 3
+#: en_US/xml-tags.xml:931(para)
+msgid "To reboot your system, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo>."
+msgstr "Para reiniciar o seu sistema, carregue em <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo>."
+d1401 1
+a1401 1
+#: en_US/xml-tags.xml:942(title) en_US/style.xml:1377(term)
+d1405 6
+a1410 1
+#: en_US/xml-tags.xml:945(primary) en_US/xml-tags.xml:969(secondary) en_US/xml-tags.xml:974(primary) en_US/xml-tags.xml:1042(primary) en_US/xml-tags.xml:1048(secondary) en_US/xml-tags.xml:1130(secondary) en_US/xml-tags.xml:1135(primary) en_US/xml-tags.xml:1225(secondary) en_US/xml-tags.xml:1230(primary) en_US/xml-tags.xml:1408(secondary) en_US/xml-tags.xml:1413(primary)
+d1414 1
+a1414 1
+#: en_US/xml-tags.xml:946(secondary)
+d1418 63
+a1480 23
+#: en_US/xml-tags.xml:949(para)
+msgid "There are several types of lists you can create using XML. You can have a itemized (bulleted) list, a ordered (numbered) list, or a variable list (presents a term and then a separate paragraph)."
+msgstr "Existem diversos tipos de listas que poderá criar em XML. Poderá ter uma lista por itens (pontos), uma lista ordenada (numerada) ou uma lista variável (apresenta um termo e depois um parágrafo separado)."
+
+#: en_US/xml-tags.xml:953(para)
+msgid "There is also a list format for tables and for for creating a list of glossary terms and their definitions."
+msgstr "Existem também um formato em lista para as tabelas e para criar uma lista de termos de glossário e as suas definições."
+
+#: en_US/xml-tags.xml:956(para)
+msgid "The sections below will discuss the proper uses for the various list and how to create them."
+msgstr "As secções abaixo irão discutir as utilizações correctas das diversas listas, bem como descrições para a sua criação."
+
+#: en_US/xml-tags.xml:978(para)
+msgid "An <command>ItemizedList</command> is best used to present information that is important for the reader to know, but that does not need to be in a specific order. It is shorter than a <command>VariableList</command> and presents the information in a very simple way."
+msgstr "Uma <command>ItemizedList</command> (lista por itens) é melhor usada para apresentar informações que sejam importantes para o leitor, mas esta não necessita de estar por uma determinada ordem. É mais reduzida que uma <command>VariableList</command> (lista variável) e apresenta a informação de uma forma muito simples."
+
+#: en_US/xml-tags.xml:984(para)
+msgid "To create an <command>ItemizedList</command> (otherwise known as bulleted list), use the following command sequence:"
+msgstr "Para criar uma <command>ItemizedList</command> (também conhecida por lista por pontos), use a seguinte sequência de comandos:"
+
+#: en_US/xml-tags.xml:988(para) en_US/xml-tags.xml:1063(para) en_US/xml-tags.xml:1147(para)
+msgid "Notice below that the text for the list item is directly surrounded by the <command>para</command> tags. If you do not do this, you will find extra whitespace in your lists where the text does not line up correctly. This is most noticeable when you have a series of list items that consist of multiple lines of text. This whitespace is not as noticeable in the HTML output as it is in the PDFs."
+msgstr "Repare em baixo que o texto do item da lista está directamente rodeado pelas marcas <command>para</command>. Se não fizer isto, irá encontrar espaços em branco extra nas suas listas, sobre as quais o texto não se irá alinhar correctamente. Isto nota-se mais quando tiver uma série de itens da lista que consistam em diversas linhas de texto. Este espaço em branco não é tão notório no resultado em HTML como será nos PDFs."
+d1482 1
+a1482 1
+#: en_US/xml-tags.xml:998(computeroutput)
+d1484 15
+a1498 1
+msgid "\n<itemizedlist> \n <listitem>\n <para>Getting familiar with the installation program's user interface</para>\n </listitem>\n\n <listitem>\n <para>Starting the installation program</para> \n </listitem>\n\n <listitem>\n <para>Selecting an installation method</para>\n </listitem>\n</itemizedlist>\n"
+d1515 4
+a1518 1
+#: en_US/xml-tags.xml:1015(para) en_US/xml-tags.xml:1094(para) en_US/xml-tags.xml:1181(para) en_US/xml-tags.xml:1319(para) en_US/xml-tags.xml:1453(para) en_US/xml-tags.xml:1909(para) en_US/xml-tags.xml:1958(para)
+d1522 1
+a1522 1
+#: en_US/xml-tags.xml:1019(para)
+d1524 2
+a1525 1
+msgstr "Familiarizar-se com a interface de utilizador do programa de instalação"
+d1527 1
+a1527 1
+#: en_US/xml-tags.xml:1023(para)
+d1531 1
+a1531 1
+#: en_US/xml-tags.xml:1027(para)
+d1535 1
+a1535 1
+#: en_US/xml-tags.xml:1034(command)
+d1539 19
+a1557 7
+#: en_US/xml-tags.xml:1052(para)
+msgid "An <command>orderedlist</command> is best used to present information that is important for the reader to know in a specific order. <command>orderedlist</command>s are a good way to convey step-by-step senarios to the audience you are writing for."
+msgstr "Uma <command>orderedlist</command> (lista ordenada) é melhor para apresentar informações importantes para o leitor, mas que este as saiba por uma determinada ordem. As <command>orderedlist</command>s são uma boa forma de explicar cenários passo-a-passo à audiência para a qual está a escrever."
+
+#: en_US/xml-tags.xml:1057(para)
+msgid "To create an <command>orderedlist</command> (numbered list), use the following XML code sequence:"
+msgstr "Para criar uma <command>orderedlist</command> (lista numerada), use a seguinte sequência de código em XML:"
+d1559 1
+a1559 1
+#: en_US/xml-tags.xml:1073(computeroutput)
+d1561 19
+a1579 1
+msgid "\n<orderedlist>\n <listitem>\n <para>Online &mdash; http://www.redhat.com/support/errata; supplies errata\n you can read online, and you can download diskette images\n easily.</para>\n </listitem>\n\t \n <listitem>\n <para>Email &mdash; By sending an empty mail message to errata@@redhat.com, \n you will receive an email containing a text listing of the \n complete errata of the installation program and related software \n (if errata exist at that time). Also included are URLs to each \n updated package and diskette image in the errata. Using these \n URLs, you can download any necessary diskette images. Please \n note: use binary mode when transferring a diskette image.</para> \n </listitem>\n</orderedlist>\n"
+d1600 24
+a1623 7
+#: en_US/xml-tags.xml:1098(para)
+msgid "Online — http://www.redhat.com/support/errata; supplies errata you can read online, and you can download diskette images easily."
+msgstr "Online — http://www.redhat.com/support/errata; oferece uma errata que poderá ler 'online', e onde poderá obter imagens de disquetes com facilidade."
+
+#: en_US/xml-tags.xml:1105(para)
+msgid "Email — By sending an empty mail message to errata@@redhat.com, you will receive an email containing a text listing of the complete errata of the installation program and related software (if errata exist at that time). Also included are URLs to each updated package and diskette image in the errata. Using these URLs, you can download any necessary diskette images. Please note: use binary mode when transferring a diskette image."
+msgstr "E-mail — Se enviar uma mensagem de e-mail vazia para errata@@redhat.com, irá receber um e-mail que contém uma listagem em texto da errata completa do programa de instalação e das aplicações relacionadas (se existir alguma nessa altura). Também estão incluídos os URLS de cada pacote actualizado e da imagem da disquete na errata. Se usar estes URLs, poderá obter as imagens de disquetes necessárias. Repare por favor: use o modo binário quando transferir uma imagem de disquete."
+d1625 1
+a1625 1
+#: en_US/xml-tags.xml:1121(command)
+d1629 7
+a1635 3
+#: en_US/xml-tags.xml:1139(para)
+msgid "A <command>variablelist</command> best represents a list of terms and definitions or descriptions for those terms."
+msgstr "Uma <command>variablelist</command> (lista variável) representa uma lista de termos e definições ou descrições desses termos."
+d1637 7
+a1643 3
+#: en_US/xml-tags.xml:1142(para)
+msgid "To create a <command>variablelist</command>, use the following command sequence:"
+msgstr "Para criar uma <command>variablelist</command>, use a seguinte sequência de comandos:"
+d1645 1
+a1645 1
+#: en_US/xml-tags.xml:1157(computeroutput)
+d1647 22
+a1668 1
+msgid "\n<variablelist>\n <varlistentry> \n <term> New Multi-CD Install </term>\n <listitem> \n <para>As the installation program continues to grow, Red Hat has developed \n an installation program capable of installing from \n multiple CD-ROMs.</para>\n </listitem>\n </varlistentry>\n\n <varlistentry>\n <term>XFree 4.0 </term>\n <listitem>\n <para>Configuration of your X Window System during the installation has \n never been more thorough. From choosing your monitor and its correct \n settings, to video card probing, to testing your desired X setup, \n Xconfigurator will help you set everything just right.</para>\n </listitem>\n </varlistentry>\n</variablelist>\n"
+d1693 1
+a1693 1
+#: en_US/xml-tags.xml:1185(term)
+d1697 7
+a1703 3
+#: en_US/xml-tags.xml:1185(para)
+msgid "As the installation program continues to grow, Red Hat has developed an installation program capable of installing from multiple CD-ROMs."
+msgstr "À medida que o programa de instalação continua a crescer, a Red Hat criou um programa de instalação que consegue instalar a partir de vários CD-ROMs."
+d1705 1
+a1705 1
+#: en_US/xml-tags.xml:1193(term)
+d1709 11
+a1719 3
+#: en_US/xml-tags.xml:1195(para)
+msgid "Configuration of your X Window System during the installation has never been more thorough. From choosing your monitor and its correct settings, to video card probing, to testing your desired X setup, Xconfigurator will help you set everything just right."
+msgstr "A configuração do seu X Window System durante a instalação nunca foi tão abrangente. Desde escolher o seu monitor e as suas respectivas opções, até à detecção da placa gráfica, ao teste da sua configuração do X, o Xconfigurator ajudá-lo-á a configurar tudo facilmente."
+d1721 1
+a1721 1
+#: en_US/xml-tags.xml:1205(title) en_US/writing-guidelines.xml:434(title)
+d1725 7
+a1731 3
+#: en_US/xml-tags.xml:1206(para)
+msgid "Do <emphasis>not</emphasis> specify the <computeroutput>frame</computeroutput> attribute to the table. Doing so breaks PDF production."
+msgstr "<emphasis>Não</emphasis> defina o atributo <computeroutput>frame</computeroutput> da tabela. Se fizer isso, impede a geração de PDFs."
+d1733 1
+a1733 1
+#: en_US/xml-tags.xml:1216(title)
+d1735 2
+a1736 1
+msgstr "Criar uma Lista Dentro de uma Tabela com uma <command>SimpleList</command>"
+d1738 2
+a1739 1
+#: en_US/xml-tags.xml:1220(command) en_US/xml-tags.xml:1226(tertiary) en_US/xml-tags.xml:1231(command) en_US/xml-tags.xml:1237(command)
+d1743 1
+a1743 1
+#: en_US/xml-tags.xml:1235(primary)
+d1747 1
+a1747 1
+#: en_US/xml-tags.xml:1236(secondary)
+d1751 19
+a1769 7
+#: en_US/xml-tags.xml:1240(para)
+msgid "A <command>simplelist</command> is an unadorned list of items. <command>simplelist</command>s can be inline or arranged in columns."
+msgstr "Uma <command>simplelist</command> é lista sem qualquer enfeite dos itens. As <command>simplelist</command>s podem ser incorporadas ou organizadas em colunas."
+
+#: en_US/xml-tags.xml:1244(para)
+msgid "We use <command>simplelist</command> to add separate paragraphs of text within a table element. A regular list, such as <command>itemizedlist</command>, cannot be embedded within a table."
+msgstr "É usada a <command>simplelist</command> para adicionar parágrafos separados de texto dentro de um elemento de tabela. Uma lista normal, como a <command>itemizedlist</command>, não poderá ser incorporada dentro de uma tabela."
+d1771 1
+a1771 1
+#: en_US/xml-tags.xml:1248(para)
+d1775 1
+a1775 1
+#: en_US/xml-tags.xml:1251(computeroutput)
+d1777 66
+a1842 1
+msgid "\n\t <table id=\"tb-hwinfo-hostbus\">\n\t <title>Host Bus Adapter Features and Configuration Requirements</title>\n\t \n\t <tgroup cols=\"3\">\n\t <colspec colnum=\"1\" colname=\"HostBus\" colwidth=\"33\"/>\n\t <colspec colnum=\"2\" colname=\"Features\" colwidth=\"34\"/>\n\t <colspec colnum=\"3\" colname=\"Single\" colwidth=\"33\"/>\n\t \n\t <thead>\n\t\t<row>\n\t\t <entry>Host Bus Adapter</entry>\n\t\t <entry>Features</entry>\n\t\t <entry>Single-Initiator Configuration</entry>\n\t\t</row>\n\t </thead>\n\t \n\t <tbody>\n\t\t\n\t\t<row>\n\t\t <entry>Adaptec 2940U2W</entry>\n\t\t \n\t\t <entry><simplelist> \n\t\t <member>Ultra2, wide, LVD.</member>\n\t\t <member>HD68 external connector.</member>\n\t\t <member>One channel, with two bus
segments.</member>\n\t\t <member>Set the onboard termination by using the BIOS\n\t\t\tutility.</member>\n\t\t <member>Onboard termination is disabled when the power is\n\t\t\toff.</member>\n\t\t </simplelist></entry>\n\t\t \n\t\t <entry><simplelist>\n\t\t <member>Set the onboard termination to automatic (the\n\t\t\tdefault).</member>\n\t\t <member>Use the internal SCSI connector for private\n\t\t\t(non-cluster) storage.</member>\n\t\t </simplelist></entry>\n\t\t</row>\n\t\t\n\t\t<row>\n\t\t <entry>Qlogic QLA1080</entry>\n\t\t \n\t\t <entry><simplelist> \n\t\t <member>Ultra2, wide, LVD</member>\n\t\t <member>VHDCI external connector</member>\n\t\t <member>One channel</member>\n\t\t <member>Set the onboard termination by using the BIOS\n\t\t\tutility.</member
>\n\t\t <member>Onboard termination is disabled when the power is off,\n\t\t\tunless jumpers are used to enforce termination.</member>\n\t\t </simplelist></entry>\n\t\t \n\t\t \n\t\t <entry><simplelist> \n\t\t <member>Set the onboard termination to\n\t\t\tautomatic (the default).</member>\n\t\t <member>Use the internal SCSI connector for private\n\t\t\t(non-cluster) storage.</member>\n\t\t </simplelist></entry>\n\t\t</row>\n\t\t\n\t </tbody>\n\t </tgroup>\n\t </table>\n"
+d1904 1
+a1904 1
+#: en_US/xml-tags.xml:1322(title)
+d1906 3
+a1908 1
+msgstr "Funcionalidades do Adaptador-Anfitrião do Barramento e Requisitos de Configuração"
+d1910 1
+a1910 1
+#: en_US/xml-tags.xml:1331(entry)
+d1914 1
+a1914 1
+#: en_US/xml-tags.xml:1332(entry) en_US/xml-tags.xml:2144(entry)
+d1918 1
+a1918 1
+#: en_US/xml-tags.xml:1333(entry)
+d1922 1
+a1922 1
+#: en_US/xml-tags.xml:1340(entry)
+d1926 1
+a1926 1
+#: en_US/xml-tags.xml:1343(member)
+d1930 1
+a1930 1
+#: en_US/xml-tags.xml:1344(member)
+d1934 1
+a1934 1
+#: en_US/xml-tags.xml:1345(member)
+d1938 1
+a1938 1
+#: en_US/xml-tags.xml:1346(member) en_US/xml-tags.xml:1367(member)
+d1942 1
+a1942 1
+#: en_US/xml-tags.xml:1348(member)
+d1946 1
+a1946 1
+#: en_US/xml-tags.xml:1353(member) en_US/xml-tags.xml:1375(member)
+d1950 1
+a1950 1
+#: en_US/xml-tags.xml:1355(member) en_US/xml-tags.xml:1377(member)
+d1952 2
+a1953 1
+msgstr "Use o conector interno SCSI para armazenamento privado (sem 'cluster')."
+d1955 1
+a1955 1
+#: en_US/xml-tags.xml:1361(entry)
+d1959 1
+a1959 1
+#: en_US/xml-tags.xml:1364(member)
+d1963 1
+a1963 1
+#: en_US/xml-tags.xml:1365(member)
+d1967 1
+a1967 1
+#: en_US/xml-tags.xml:1366(member)
+d1971 27
+a1997 11
+#: en_US/xml-tags.xml:1369(member)
+msgid "Onboard termination is disabled when the power is off, unless jumpers are used to enforce termination."
+msgstr "A terminação na placa é desactivada quando se desliga a alimentação, a menos que existam interruptores para forçar a terminação."
+
+#: en_US/xml-tags.xml:1388(para)
+msgid "Notice how the <command>SimpleList</command> tags are used. The <entry> and <simplelist> tags must be aligned beside one another, otherwise you will receive a parsing error."
+msgstr "Repare na utilização das marcas <command>SimpleList</command>. As marcas <entry> e <simplelist> deverão ser alinhadas uma ao lado da outra, caso contrário irá receber um erro de processamento."
+
+#: en_US/xml-tags.xml:1393(para)
+msgid "For each paragraph or list item to be added within a <command>SimpleList</command>, the <member> tag set must be added around that particular text item."
+msgstr "Para cada parágrafo ou item da lista adicionado dentro de uma <command>SimpleList</command>, dever-se-á adicionar uma marca <member> em torno desse item de texto em particular."
+d1999 2
+a2000 1
+#: en_US/xml-tags.xml:1399(command) en_US/xml-tags.xml:1403(command) en_US/xml-tags.xml:1409(tertiary) en_US/xml-tags.xml:1414(command)
+d2004 7
+a2010 3
+#: en_US/xml-tags.xml:1417(para)
+msgid "Use the <command>glosslist</command> command set to create a list of glossary terms and their definitions."
+msgstr "Use o comando <command>glosslist</command> para criar uma lista de termos do glossário e as suas definições."
+d2012 1
+a2012 1
+#: en_US/xml-tags.xml:1421(para)
+d2016 1
+a2016 1
+#: en_US/xml-tags.xml:1424(computeroutput)
+d2018 27
+a2044 1
+msgid "\n\t <glosslist>\n\t <glossentry>\n\t <glossterm>applet</glossterm>\n\t <glossdef>\n\t\t<para>A small application, usually a utility or other\n\t simple program.</para>\n\t </glossdef>\n\t </glossentry>\n\n\t <glossentry>\n\t <glossterm>architecture</glossterm>\n\t <glossdef>\n\t\t<para>The design for organization and integration of \n components within a computer or computer system.</para>\n\t </glossdef>\n\t </glossentry>\n\n\t <glossentry>\n\t <glossterm>archive</glossterm>\n\t <glossdef>\n\t\t<para>To transfer files into storage for the purpose of \n\t saving space and/or organization.</para>\n\t </glossdef>\n\t </glossentry>\n\t </glosslist>\n"
+d2073 1
+a2073 1
+#: en_US/xml-tags.xml:1459(glossterm)
+d2077 1
+a2077 1
+#: en_US/xml-tags.xml:1461(para)
+d2079 2
+a2080 1
+msgstr "Uma pequena aplicação, normalmente um utilitário ou outro programa simples."
+d2082 1
+a2082 1
+#: en_US/xml-tags.xml:1466(glossterm)
+d2086 7
+a2092 3
+#: en_US/xml-tags.xml:1468(para)
+msgid "The design for organization and integration of components within a computer or computer system."
+msgstr "O desenho da organização e integração dos componentes dentro de um computador ou sistema computacional."
+d2094 1
+a2094 1
+#: en_US/xml-tags.xml:1474(glossterm)
+d2098 7
+a2104 3
+#: en_US/xml-tags.xml:1476(para)
+msgid "To transfer files into storage for the purpose of saving space and/or organization."
+msgstr "Para transferir os ficheiros armazenados com o intuito de poupar espaço e/ou organização."
+d2106 1
+a2106 1
+#: en_US/xml-tags.xml:1487(command) en_US/xml-tags.xml:1491(secondary)
+d2110 15
+a2124 7
+#: en_US/xml-tags.xml:1494(para)
+msgid "If you have a command that offers an option or a flag, use the <command><option></command> and <command></option></command> tags."
+msgstr "Se tiver um comando que ofereça uma opção qualquer, use as marcas <command><option></command> e <command></option></command>."
+
+#: en_US/xml-tags.xml:1501(para)
+msgid "The <option> tag set is only meant to be used for command line options, not options in configuration files."
+msgstr "A marca <option> só pretende ser usada para as opções da linha de comandos, não para as opções dos ficheiros de configuração."
+d2126 1
+a2126 1
+#: en_US/xml-tags.xml:1505(para)
+d2130 1
+a2130 1
+#: en_US/xml-tags.xml:1509(computeroutput)
+d2132 4
+a2135 1
+msgid "\nFor example, with the command <command>ls</command> you can \nspecify an option such as <option>-la</option>.\n"
+d2141 7
+a2147 3
+#: en_US/xml-tags.xml:1519(para)
+msgid "For example, with the command <command>ls</command> you can specify an option such as <option>-la</option>."
+msgstr "Por exemplo, com o comando <command>ls</command>, poderá definir uma opção como a <option>-la</option>."
+d2149 1
+a2149 1
+#: en_US/xml-tags.xml:1525(title)
+d2153 2
+a2154 1
+#: en_US/xml-tags.xml:1528(primary) en_US/xml-tags.xml:1534(secondary) en_US/xml-tags.xml:1563(primary) en_US/xml-tags.xml:1595(primary)
+d2158 16
+a2173 7
+#: en_US/xml-tags.xml:1537(para)
+msgid "The following command sequence shows you the code inserted into the body of the text to add an index entry to your document:"
+msgstr "A seguinte sequência de comandos mostra-lhe o código inserido dentro do conteúdo do texto, de modo a adicionar um item do índice ao seu documento:"
+
+#: en_US/xml-tags.xml:1542(computeroutput)
+#, no-wrap
+msgid "\n<indexterm> <-- indicates a term to be placed in the index\n<primary>foo</primary> <-- indicates that \"foo\" is the first term\n<secondary>bar</secondary> <-- \"bar\" will be listed under \"foo\" \n</indexterm> <-- closes this index entry\n"
+d2181 1
+a2181 1
+#: en_US/xml-tags.xml:1551(primary)
+d2185 1
+a2185 1
+#: en_US/xml-tags.xml:1552(secondary)
+d2189 11
+a2199 3
+#: en_US/xml-tags.xml:1556(para)
+msgid "The <command><seealso></command> tag allows you to reference another index entry or refer to another manual. Make sure the <command><seealso></command> reference you are pointing to has its own entry. For example:"
+msgstr "A marca <command><seealso></command> permite-lhe fazer referências a outros itens do índice ou referenciar outro manual. Certifique-se que o <command><seealso></command> para o qual aponta tem o seu próprio item. Por exemplo:"
+d2201 1
+a2201 1
+#: en_US/xml-tags.xml:1564(secondary)
+d2205 1
+a2205 1
+#: en_US/xml-tags.xml:1568(computeroutput)
+d2207 11
+a2217 1
+msgid "\n<indexterm> \n<primary>SWAK</primary> \n<seealso>salutations</seealso>\n</indexterm>\n\n\n<indexterm> \n<primary>salutations</primary> \n</indexterm>\n"
+d2230 1
+a2230 1
+#: en_US/xml-tags.xml:1582(primary)
+d2234 1
+a2234 1
+#: en_US/xml-tags.xml:1583(seealso) en_US/xml-tags.xml:1587(primary)
+d2238 7
+a2244 3
+#: en_US/xml-tags.xml:1590(para)
+msgid "The <command><see></command> tag allows you to reference to another index entry entirely. For example:"
+msgstr "A marca <command><see></command> permite-lhe referenciar outro item do índice por inteiro. Por exemplo:"
+d2246 1
+a2246 1
+#: en_US/xml-tags.xml:1596(secondary)
+d2250 1
+a2250 1
+#: en_US/xml-tags.xml:1601(computeroutput)
+d2252 12
+a2263 1
+msgid "\n<indexterm> \n<primary>Guinness</primary> \n<see>beer</see> <-- beer will be listed under \nthe Guinness entry, but you must make sure beer also has its \nown entry to refer to.\n</indexterm>\n\n<indexterm>\n<primary>beer</primary>\n</indexterm>\n"
+d2277 1
+a2277 1
+#: en_US/xml-tags.xml:1616(primary)
+d2281 1
+a2281 1
+#: en_US/xml-tags.xml:1617(see) en_US/xml-tags.xml:1621(primary)
+d2285 20
+a2304 7
+#: en_US/xml-tags.xml:1624(para)
+msgid "To view the HTML output of the index entries shown here, refer to the <filename>generated-index.html</filename> file at the end of this document."
+msgstr "Para ver o resultado em HTML dos itens do índice que aparecem aqui, veja o ficheiro <filename>generated-index.html</filename> no fim deste documento."
+
+#: en_US/xml-tags.xml:1628(para)
+msgid "How does the index get generated? If indexterms exist in the document and the beginning and ending index tags exist before the end tag for the book or article, an index is created because of the <command>generate.index</command> stylesheet parameter, which is set to true by default."
+msgstr "Agora como é que o índice é gerado? Se existirem 'indexterms' no documento e as marcas de início e fim do índice existirem antes da marca final do livro ou do artigo, é criado um índice devido ao parâmetro <command>generate.index</command> da folha de estilo, que está definido como verdadeiro por omissão."
+d2306 1
+a2306 1
+#: en_US/xml-tags.xml:1638(command) en_US/xml-tags.xml:1643(secondary)
+d2310 26
+a2335 11
+#: en_US/xml-tags.xml:1646(para)
+msgid "For any paragraph, the <command><para></command> and <command></para></command> tags must open and close that particular paragraph."
+msgstr "Para qualquer parágrafo, as marcas <command><para></command> e <command></para></command> deverão abrir e fechar esse parágrafo em particular."
+
+#: en_US/xml-tags.xml:1651(para)
+msgid "Do not use para tags around anything other than a simple paragraph. Doing so will create additional white space within the text itself."
+msgstr "Não use as marcas 'para' para nada que não seja um parágrafo simples. Se o fizer, irá criar espaço em branco adicional dentro do próprio texto."
+
+#: en_US/xml-tags.xml:1655(para)
+msgid "Do not use <command><para></command> tags around the following (or, to put this another way, do not embed the following within <command><para></command> tags):"
+msgstr "Não use as marcas <command><para></command> em torno dos seguintes ponto (ou, posto de outra forma, não incorpore o seguinte dentro das marcas <command><para></command>):"
+d2337 2
+a2338 1
+#: en_US/xml-tags.xml:1661(command) en_US/xml-tags.xml:1896(command) en_US/xml-tags.xml:1904(command) en_US/xml-tags.xml:1953(command)
+d2342 1
+a2342 1
+#: en_US/xml-tags.xml:1664(command)
+d2346 1
+a2346 1
+#: en_US/xml-tags.xml:1667(command)
+d2350 1
+a2350 1
+#: en_US/xml-tags.xml:1670(command)
+d2354 1
+a2354 1
+#: en_US/xml-tags.xml:1673(command)
+d2358 2
+a2359 1
+#: en_US/xml-tags.xml:1680(command) en_US/xml-tags.xml:1689(secondary) en_US/writing-guidelines.xml:119(sgmltag)
+d2363 1
+a2363 1
+#: en_US/xml-tags.xml:1683(primary)
+d2367 9
+a2375 3
+#: en_US/xml-tags.xml:1692(para)
+msgid "In the parent file, you can separate the chapters into parts to divide them into logical groups. For example, in the parent file, the <command>part</command> tags surround the chapter entities:"
+msgstr "No ficheiro-pai, poderá separar os capítulos em partes, de modo a dividi-los em grupos lógicos. Por exemplo, no ficheiro-pai, as marcas <command>part</command> rodeiam as entidades do capítulo:"
+d2377 1
+a2377 1
+#: en_US/xml-tags.xml:1698(computeroutput)
+d2379 9
+a2387 1
+msgid "\n<part id=\"pt-foo\">\n <partintro>\n <para>Some text for the part intro</para>\n &CHAPTER; \n\n &ANOTHER-CHAPTER;\n</part>\n"
+d2398 7
+a2404 3
+#: en_US/xml-tags.xml:1709(para)
+msgid "If you create a part, include a part introduction describing the contents of the part. For example:"
+msgstr "Se criar uma parte, inclua uma introdução de uma parte que descreva o seu conteúdo. Por exemplo:"
+d2406 1
+a2406 1
+#: en_US/xml-tags.xml:1715(computeroutput)
+d2408 9
+a2416 1
+msgid "\n <part id=\"pt-setup\">\n <title>Getting Setup</title>\n <partintro>\n <para>This section contains information you will need when you first join\n\tthe Docs group. You might need to refer to this part again for\n\tinformation such as installing &FC;.</para>\n </partintro>\n"
+d2427 9
+a2435 3
+#: en_US/xml-tags.xml:1726(para)
+msgid "In the HTML output, a separate HTML page is generated with the part number, title, introduction, and TOC. In the PDF output, the same information about the part is on a separate page."
+msgstr "No resultado em HTML, é gerada uma página separada em HTML para o número, título, introdução e índice da parte. No resultado em PDF, a mesma informação acerca da página está numa página em separado."
+d2437 1
+a2437 1
+#: en_US/xml-tags.xml:1735(command) en_US/xml-tags.xml:1739(secondary)
+d2441 9
+a2449 3
+#: en_US/xml-tags.xml:1742(para)
+msgid "To show a prompt, such as a root or DOS prompt, use the <command><prompt></command> and <command></prompt></command> commands. For example:"
+msgstr "Para mostrar uma linha de comandos, como a linha de comandos do 'root' ou do DOS, use os comandos <command><prompt></command> e <command></prompt></command>. Por exemplo:"
+d2451 1
+a2451 1
+#: en_US/xml-tags.xml:1748(computeroutput)
+d2453 6
+a2458 1
+msgid "\nAt the <prompt>LILO:</prompt> boot prompt, type linux to \nboot into your Linux partition.\n\nAt the <prompt>C:\\></prompt> prompt, type ....\n"
+d2467 7
+a2473 3
+#: en_US/xml-tags.xml:1760(para)
+msgid "At the <prompt>LILO:</prompt> boot prompt, type linux to boot into your Linux partition."
+msgstr "Na linha de comandos <prompt>LILO:</prompt>, escreva 'linux' para arrancar para a sua partição de Linux."
+d2475 1
+a2475 1
+#: en_US/xml-tags.xml:1764(para)
+d2479 10
+a2488 3
+#: en_US/xml-tags.xml:1770(para)
+msgid "When showing example computer output (usually in <command>screen</command> tags), do not include the prompt or command (unless the command or prompt is the actually computer output you want to show)."
+msgstr "Ao mostrar um exemplo de resultados do computador (normalmente em marcas <command>screen</command>), não inclua a linha de comandos ou o comando em si (a menos que este seja de facto o resultado do computador que deseja mostrar)."
+d2490 1
+a2490 1
+#: en_US/xml-tags.xml:1779(command) en_US/xml-tags.xml:1783(secondary)
+d2494 9
+a2502 3
+#: en_US/xml-tags.xml:1786(para)
+msgid "To create replaceable text, use the tags <command><replaceable></command> and <command></replaceable></command> around the text you want to use as a variable."
+msgstr "Para criar texto que poderá ser substituído, use as marcas <command><replaceable></command> e <command></replaceable></command> em torno do texto que deseja usar como variável."
+d2504 7
+a2510 3
+#: en_US/xml-tags.xml:1792(para)
+msgid "This example demonstrates how to use the <command>replaceable</command> tags when referencing the name of an RPM file:"
+msgstr "Este exemplo demonstra como usar as marcas <command>replaceable</command> na referência ao nome de um ficheiro RPM:"
+d2512 1
+a2512 1
+#: en_US/xml-tags.xml:1796(screen)
+d2514 6
+a2519 2
+msgid "\nfoo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm\n"
+msgstr "\nxpto-<replaceable>número-versão</replaceable>.<replaceable>arquitectura</replaceable>.rpm\n"
+d2521 1
+a2521 1
+#: en_US/xml-tags.xml:1805(replaceable)
+d2525 1
+a2525 1
+#: en_US/xml-tags.xml:1805(replaceable)
+d2529 1
+a2529 1
+#: en_US/xml-tags.xml:1804(screen)
+d2531 6
+a2536 2
+msgid "\nfoo-<placeholder-1/>.<placeholder-2/>.rpm\n"
+msgstr "\nxpto-<placeholder-1/>.<placeholder-2/>.rpm\n"
+d2538 63
+a2600 3
+#: en_US/xml-tags.xml:1816(para)
+msgid "The <command><screen></command> command is used to format text within a document and is great for adding emphasis to show examples of code, computer output, and more. In HTML with the Fedora CSS file, this appears in box with a grey background. To use this command you only need the opening <command><screen></command> and closing <command></screen></command> tags around the text you are emphasizing."
+msgstr "O comando <command><screen></command> é usado para formatar o texto dentro de um documento e é óptimo para adicionar alguma ênfase na apresentação de exemplos de código, resultados do computador, entre outras coisas. No HTML, com o ficheiro CSS do Fedora, este aparecerá numa caixa com um fundo cinzento. Para usar este comando, só necessita do <command><screen></command> de abertura e de delimitar o texto que deseja realçar com a marca <command></screen></command> de fecho."
+d2602 1
+a2602 13
+#: en_US/xml-tags.xml:1828(para)
+msgid "When using the <command><screen></command> tag, set everything within that screen to flush left. The contents of the <sgmltag class=\"starttag\">screen</sgmltag> element are rendered exactly as is, including any indentation. Using flush left prevents extra blank space in front of the text inside the gray background when the content is converted to HTML."
+msgstr "Ao usar a marca <command><screen></command>, configure tudo dentro desse ecrã para se colocar à esquerda. O conteúdo do elemento <sgmltag class=\"starttag\">screen</sgmltag> é representado tal-e-qual, incluindo a indentação. Se usar a remoção à esquerda, impede que apareçam espaços em branco extra à frente do texto, dentro do fundo cinzento, quando o conteúdo for convertido para HTML."
+
+#: en_US/xml-tags.xml:1838(para)
+msgid "The <command><screen></command> tag set may contain other inline tags, such as <command><computeroutput></command>, <command><userinput></command>, or <command><replaceable></command>. Additional inline tags are not required by definition. The <command><screen></command> tags by themselves may provide sufficient context, especially for simple examples or file listings. Consider the context of the example, and use inline tags if they are helpful to the reader."
+msgstr "A marca <command><screen></command> poderá conter outras marcas incorporadas, como a <command><computeroutput></command>, a <command><userinput></command> ou a <command><replaceable></command>. As outras marcas incorporadas não são obrigatórias por definição. As marcas <command><screen></command> propriamente ditas poderão oferecer um contexto suficiente, especialmente no caso dos exemplos simples ou das listagens de ficheiros. Considere o contexto do exemplo e use as marcas incorporadas se forem úteis para o leitor."
+
+#: en_US/xml-tags.xml:1849(para)
+msgid "If you use inline tags, remember that line breaks inside <command><screen></command> tags create line breaks in any rendered output. Place any inline tags <emphasis>on the same line</emphasis> as their content. Do not overuse tagging within a <command><screen></command> tag set."
+msgstr "Se usar as marcas incorporadas, recorde-se que as quebras de linha dentro das marcas <command><screen></command> criam quebras de linha no resultado apresentado. Coloque as marcas incorporadas <emphasis>na mesma linha</emphasis> que o seu conteúdo. Não sobrecarregue com marcas dentro de uma marca <command><screen></command>."
+
+#: en_US/xml-tags.xml:1857(para)
+d2606 1
+a2606 1
+#: en_US/xml-tags.xml:1862(computeroutput)
+d2608 5
+a2612 1
+msgid "<screen>\nThis is an example of a screen. You do not need &lt;para&gt; tags\nwithin this command.\n</screen>"
+d2619 1
+a2619 1
+#: en_US/xml-tags.xml:1872(screen)
+d2621 4
+a2624 1
+msgid "\nThis is an example of a screen. You do not need <para> tags\nwithin this command.\n"
+d2630 1
+a2630 1
+#: en_US/xml-tags.xml:1878(title)
+d2634 18
+a2651 3
+#: en_US/xml-tags.xml:1879(para)
+msgid "If you choose to use inline tags inside a <command><screen></command> section, follow these guidelines for consistency. If the content in the screen is a listing of a configuration file or the output of a program, use the <command><computeroutput></command> tag set around the entire output. If the user should type the example on the command line or in a configuration file, use the <command><userinput></command> tag set. Separate input and output with a short sentence of narrative, as below:"
+msgstr "Se optar por usar marcas incorporadas dentro de uma secção <command><screen></command>, siga estas instruções por razões de consistência. Se o conteúdo no ecrã for uma listagem de um ficheiro de configuração ou o resultado de um programa, use a marca <command><computeroutput></command> em torno do resultado completo. Se o utilizador deverá escrever o exemplo na linha de comandos ou num ficheiro de configuração, use a marca <command><userinput></command>. Separe as entradas e saídas com uma pequena frase narrativa, como aparece em baixo:"
+d2653 2
+a2654 1
+#: en_US/xml-tags.xml:1892(command) en_US/xml-tags.xml:1900(command) en_US/xml-tags.xml:1949(command)
+d2658 2
+a2659 1
+#: en_US/xml-tags.xml:1894(command) en_US/xml-tags.xml:1902(command) en_US/xml-tags.xml:1951(command)
+d2663 1
+a2663 1
+#: en_US/xml-tags.xml:1897(command) en_US/xml-tags.xml:1954(command)
+d2667 1
+a2667 1
+#: en_US/xml-tags.xml:1897(command) en_US/xml-tags.xml:1954(command)
+d2671 2
+a2672 1
+#: en_US/xml-tags.xml:1898(command) en_US/xml-tags.xml:1906(command) en_US/xml-tags.xml:1955(command)
+d2676 1
+a2676 1
+#: en_US/xml-tags.xml:1905(command)
+d2680 1
+a2680 1
+#: en_US/xml-tags.xml:1905(command)
+d2684 1
+a2684 1
+#: en_US/xml-tags.xml:1891(screen)
+d2686 17
+a2702 1
+msgid "\n\t<placeholder-1/>\n\t Type the following command:\n\t<placeholder-2/>\n\n<placeholder-3/>\n<placeholder-4/>command -sw file1<placeholder-5/>\n<placeholder-6/>\n\n\t<placeholder-7/>\n\t You should see the following output:\n\t<placeholder-8/>\n\n<placeholder-9/>\n<placeholder-10/>Completed, time = 0.12 sec<placeholder-11/>\n<placeholder-12/>\n"
+d2721 1
+a2721 1
+#: en_US/xml-tags.xml:1913(para)
+d2725 1
+a2725 1
+#: en_US/xml-tags.xml:1918(userinput)
+d2730 1
+a2730 1
+#: en_US/xml-tags.xml:1921(para)
+d2734 1
+a2734 1
+#: en_US/xml-tags.xml:1926(computeroutput)
+d2739 25
+a2763 7
+#: en_US/xml-tags.xml:1931(para)
+msgid "When showing a command or series of commands inside <command>screen</command> tags, do not show the prompt."
+msgstr "Ao mostrar um comando ou uma série de comandos dentro das marcas <command>screen</command>, não mostre a linha de comandos."
+
+#: en_US/xml-tags.xml:1937(para)
+msgid "If the <command><screen></command> shows the reader how to change only <emphasis>part</emphasis> of a line, mark the change with an inline <command><userinput></command> tag set. You may use the <command><userinput></command> tag set inside a larger area that is already marked inline with <command><computeroutput></command>. Do not include any extra lines of context in this case, unless excluding them would confuse the reader. The following example illustrates these guidelines:"
+msgstr "Se o <command><screen></command> mostrar ao leitor como alterar apenas <emphasis>parte</emphasis> de uma linha, marque a alteração com um conjunto de marcas <command><userinput></command>. Poderá usar o conjunto de marcas <command><userinput></command> dentro de uma área maior que já esteja marcada dentro de um <command><computeroutput></command>. Não inclua as linhas extra de contexto neste caso, a menos que a sua exclusão possa confundir o leitor. O seguinte exemplo demonstra estas regras:"
+d2765 1
+a2765 1
+#: en_US/xml-tags.xml:1950(command)
+d2769 1
+a2769 1
+#: en_US/xml-tags.xml:1950(command)
+d2773 1
+a2773 1
+#: en_US/xml-tags.xml:1948(screen)
+d2775 9
+a2783 1
+msgid "\n\t<placeholder-1/>\n\t Edit the <placeholder-2/>/etc/sysconfig/init<placeholder-3/> file as follows:\n\t<placeholder-4/>\n\n<placeholder-5/>\nGRAPHICAL=<placeholder-6/>yes<placeholder-7/> \n<placeholder-8/>\n"
+d2794 1
+a2794 1
+#: en_US/xml-tags.xml:1962(para)
+d2796 2
+a2797 1
+msgstr "Edite o ficheiro <filename>/etc/sysconfig/init</filename> como se segue:"
+d2799 4
+a2802 1
+#: en_US/xml-tags.xml:1967(userinput) en_US/xml-tags.xml:2153(entry) en_US/xml-tags.xml:2154(entry) en_US/xml-tags.xml:2158(entry) en_US/xml-tags.xml:2159(entry) en_US/xml-tags.xml:2163(entry) en_US/xml-tags.xml:2164(entry)
+d2807 1
+a2807 1
+#: en_US/xml-tags.xml:1966(screen)
+d2809 6
+a2814 2
+msgid "\nGRAPHICAL=<placeholder-1/>\n"
+msgstr "\nGRAPHICAL=<placeholder-1/>\n"
+d2816 9
+a2824 3
+#: en_US/xml-tags.xml:1970(para)
+msgid "For an explanation of how to use the <command>replaceable</command> tags within a set of <command>screen</command> tags, refer to <xref linkend=\"sn-xml-tags-replaceable\"/>."
+msgstr "Para uma explicação de como usar as marcas <command>replaceable</command> dentro das marcas <command>screen</command>, veja em <xref linkend=\"sn-xml-tags-replaceable\"/>."
+d2826 1
+a2826 1
+#: en_US/xml-tags.xml:1980(title)
+d2830 1
+a2830 1
+#: en_US/xml-tags.xml:1984(secondary) en_US/xml-tags.xml:1988(primary)
+d2834 17
+a2850 3
+#: en_US/xml-tags.xml:1991(para)
+msgid "Within an article (or chapter if it is a DocBook XML book like the <citetitle>Installation Guide</citetitle>), you can have sections and subsections. <command><section></command> is always the highest section and you cannot have two sections of the same level within one another (a section 2 can be created within a section 1, but section 1 has to be closed before another section 1 can be created). The general layout follows:"
+msgstr "Dentro de um artigo (ou capítulo, se for um livro de DocBook em XML, como o <citetitle>Guia de Instalação</citetitle>), você poderá ter secções e sub-secções. A <command><section></command> é sempre a secção do nível de topo e não poderá ter duas secções ao mesmo nível dentro de outra (uma secção 2 poderá ser criada dentro de uma secção 1, mas a secção 1 terá de ser fechada antes de poder criar outra secção 1). Segue-se a disposição geral:"
+d2852 1
+a2852 1
+#: en_US/xml-tags.xml:2000(computeroutput)
+d2854 26
+a2879 1
+msgid "\n<section id=\"sn-uniquename\">\n <title>Insert Title Here</title>\n <para>\n Body text goes here.\n </para>\n\n\n <section id=\"sn-uniquename\">\n <title>Insert Title Here</title>\n <para>\n Body text goes here.\n </para>\n\n <sect3 id=\"s3-uniquename\">\n <title>Insert Title Here</title>\n <para>\n Body text goes here.\n </para>\n\n </sect3>\n\n </section>\n\n</section>\n"
+d2907 7
+a2913 3
+#: en_US/xml-tags.xml:2028(para)
+msgid "If you only need one level of sections in a DocBook article, you can use the <command>section</command> tag. For example:"
+msgstr "Se só necessitar de um nível de secções num artigo em DocBook, poderá usar a marca <command>section</command>. Por exemplo:"
+d2915 1
+a2915 1
+#: en_US/xml-tags.xml:2034(computeroutput)
+d2917 14
+a2930 1
+msgid "\n<section id=\"sn-uniquename\">\n <title>Insert Title Here</title>\n <para>\n Body text goes here.\n </para>\n</section>\n<section id=\"sn-anothername\">\n <title>Insert Title Here</title>\n <para>\n More body text goes here.\n </para>\n</section>\n"
+d2946 1
+a2946 1
+#: en_US/xml-tags.xml:2059(para)
+d2950 1
+a2950 1
+#: en_US/xml-tags.xml:2066(command)
+d2954 7
+a2960 3
+#: en_US/xml-tags.xml:2065(emphasis)
+msgid "This tells XML that you will be creating a table and the ID name is <placeholder-1/>"
+msgstr "Isto diz ao XML que irá criar uma tabela e que o seu nome identificador é <placeholder-1/>"
+d2962 1
+a2962 1
+#: en_US/xml-tags.xml:2071(emphasis)
+d2966 1
+a2966 1
+#: en_US/xml-tags.xml:2075(command)
+d2970 5
+a2974 3
+#: en_US/xml-tags.xml:2075(emphasis)
+msgid "<placeholder-1/> says that you are giving information about the column to XML"
+msgstr "O <placeholder-1/> indica que está a dar informações acerca da coluna ao XML"
+d2976 1
+a2976 1
+#: en_US/xml-tags.xml:2076(command)
+d2980 7
+a2986 3
+#: en_US/xml-tags.xml:2076(emphasis)
+msgid "<placeholder-1/> says that you are giving specifications for the first column."
+msgstr "O <placeholder-1/> indica que está a introduzir definições para a primeira coluna."
+d2988 1
+a2988 1
+#: en_US/xml-tags.xml:2079(command)
+d2992 5
+a2996 3
+#: en_US/xml-tags.xml:2079(emphasis)
+msgid "<placeholder-1/> says that the title for this column will be \"Features.\""
+msgstr "O <placeholder-1/> diz que o título desta coluna será \"Funcionalidades.\""
+d2998 1
+a2998 1
+#: en_US/xml-tags.xml:2082(command)
+d3002 17
+a3018 3
+#: en_US/xml-tags.xml:2082(emphasis)
+msgid "<placeholder-1/> specifies the width of the column. This can be more tricky: such as two columns with widths of 1 and 2,the 1 is one-half the width of the 2, in respect to the page size. But, what if you need the 1 to be a little more than half of the 2, using a larger number ratio, such as 10 to 20 would accomplish this. You could then change the 10 to an 11 or a 12 to make it a little more than half of the second column of 20. In no value is given, a value of 1 is assumed."
+msgstr "O <placeholder-1/> define a largura da coluna. Isto poderá ser mais complicado: se tiver duas colunas com larguras 1 e 2, a 1 terá metade da largura da 2, no que respeita ao tamanho da página. Contudo, se precisar que a 1 seja um pouco mais de metade da 2, se usar uma proporção maior, como o 10 ou 20, será mais fácil de fazer isto. Poderá então alterar o 10 para um 11 ou 12, de modo a torná-lo um pouco mais de metade da segunda coluna com 20. Se não for indicado nenhum valor, será usado o valor 1."
+d3020 1
+a3020 1
+#: en_US/xml-tags.xml:2096(emphasis)
+d3024 1
+a3024 1
+#: en_US/xml-tags.xml:2099(emphasis)
+d3028 7
+a3034 3
+#: en_US/xml-tags.xml:2102(emphasis)
+msgid "Table cell element, one of several in a row element, defining columns within the row."
+msgstr "Elemento de célula da tabela, um de vários num elemento da linha, a definir as colunas dentro da linha."
+d3036 1
+a3036 1
+#: en_US/xml-tags.xml:2111(emphasis)
+d3038 2
+a3039 1
+msgstr "Contém um ou mais elementos de linhas, para o texto principal da tabela."
+d3041 1
+a3041 1
+#: en_US/xml-tags.xml:2063(screen)
+d3043 55
+a3097 1
+msgid "\n<table id=\"tb-mockup-before-begin\">\n <placeholder-1/>\n\n<title>Available Features of GNOME and KDE</title>\n\n<tgroup cols=\"3\">\n <placeholder-2/>\n\n<colspec colnum=\"1\" colname=\"Features\" colwidth=\"3\"/>\n <placeholder-3/> <placeholder-4/>\n \n <placeholder-5/>\n \n <placeholder-6/>\n\n<colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/>\n<colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/>\n\n<thead>\n <placeholder-7/>\n\n<row> \n <placeholder-8/>\n\n<entry>Features</entry>\n <placeholder-9/>\n\n<entry>GNOME</entry> \n<entry>KDE</entry>\n</row> \n</thead> \n\n<tbody> \n <placeholder-10/>\n\n<row> \n<entry>highly configurable</entry> \n<entry>yes</entry> \n<entry>yes</entry> \n</row> \n<row> \n<entry>multiple window managers </entry>\n<entry>y
es</entry> \n<entry>yes</entry> \n</row> \n<row> \n<entry>Internet applications</entry> \n<entry>yes </entry> \n<entry>yes </entry> \n</row> \n</tbody> \n</tgroup> \n</table> \n"
+d3154 1
+a3154 1
+#: en_US/xml-tags.xml:2135(title)
+d3158 1
+a3158 1
+#: en_US/xml-tags.xml:2145(entry)
+d3162 1
+a3162 1
+#: en_US/xml-tags.xml:2146(entry)
+d3166 1
+a3166 1
+#: en_US/xml-tags.xml:2152(entry)
+d3170 1
+a3170 1
+#: en_US/xml-tags.xml:2157(entry)
+d3174 1
+a3174 1
+#: en_US/xml-tags.xml:2162(entry)
+d3178 1
+a3178 1
+#: en_US/xml-tags.xml:2171(title)
+d3182 1
+a3182 1
+#: en_US/xml-tags.xml:2176(tertiary)
+d3186 26
+a3211 11
+#: en_US/xml-tags.xml:2180(para)
+msgid "Creating a list within a table can be a difficult task. It requires strict formatting and a set of commands that are not available for command completion in <application>Emacs</application>."
+msgstr "A criação de uma lista dentro de uma tabela poderá ser uma tarefa complicada. Necessita de uma formatação restrita e de um conjunto de comandos que não estão disponíveis na completação de comandos no <application>Emacs</application>."
+
+#: en_US/xml-tags.xml:2185(para)
+msgid "The tags you will need to use are <command><simplelist></command> and <command><member></command>."
+msgstr "As marcas que terá de usar são a <command><simplelist></command> e a <command><member></command>."
+
+#: en_US/xml-tags.xml:2189(para)
+msgid "The following example will show you the proper formatting for creating a list within a table."
+msgstr "O exemplo que se segue mostrar-lhe-á a devida formatação para criar uma lista dentro de uma tabela."
+d3213 1
+a3213 1
+#: en_US/xml-tags.xml:2194(computeroutput)
+d3215 52
+a3266 1
+msgid "\n<table id=\"tb-hardware-powerswitch\">\n <title>Power Switch Hardware Table</title>\n <tgroup cols=\"4\">\n <colspec colnum=\"1\" colname=\"Hardware\" colwidth=\"2\"/>\n <colspec colnum=\"2\" colname=\"Quantity\" colwidth=\"2\"/>\n <colspec colnum=\"3\" colname=\"Description\" colwidth=\"6\"/> \n <colspec colnum=\"4\" colname=\"Required\" colwidth=\"2\"/>\n\n <thead>\n\t <row>\n <entry>Hardware</entry>\n\t <entry>Quantity</entry>\n <entry>Description</entry>\n\t <entry>Required</entry>\n\t </row>\n </thead>\n\t \n <tbody>\n\t \n\t<row>\n <entry>Serial power switches</entry>\n\n\t <entry>Two</entry>\n\n\t <entry><simplelist> <member>Power switches enable each cluster system\n\t to power-cycle the other cluster
system. Note that clusters are\n\t configured with either serial or network attached power switches and\n\t not both.</member>\n\t\t \n <member>The following serial attached power switch has been\n\t fully tested:</member>\n\n <member>RPS-10 (model M/HD in the US, and model M/EC in\n\t Europe) </member>\n\n <member>Latent support is provided for the following serial\n\t attached power switch. This switch has not yet been fully\n tested:</member>\n\t\t \n\t <member>APC Serial On/Off Switch (partAP9211), <ulink\n url=\"http://www.apc.com/\">http://www.apc.com/</ulink></member>\n </simplelist></entry>\n\n <entry>Strongly recommended for data integrity under all failure\n\t conditions</entry>\n\n\t </row>\n </tbody>\n </tgroup>\n</table
>\n"
+d3320 9
+a3328 3
+#: en_US/xml-tags.xml:2248(para)
+msgid "Notice how the <command><simplelist></command> tag must be beside the <command><entry></command> tag? If you do not format this properly, it will not parse cleanly."
+msgstr "Reparou como a marca <command><simplelist></command> deve estar dentro da marca <command><entry></command>? Se não formatar isto correctamente, o processamento não será bem sucedido."
+d3330 1
+a3330 1
+#: en_US/xml-tags.xml:2252(para)
+d3334 1
+a3334 1
+#: en_US/xml-tags.xml:2255(title)
+d3338 1
+a3338 1
+#: en_US/xml-tags.xml:2264(entry)
+d3342 1
+a3342 1
+#: en_US/xml-tags.xml:2265(entry)
+d3346 1
+a3346 1
+#: en_US/xml-tags.xml:2266(entry) en_US/emacs.xml:415(segtitle)
+d3350 1
+a3350 1
+#: en_US/xml-tags.xml:2267(entry)
+d3354 1
+a3354 1
+#: en_US/xml-tags.xml:2274(entry)
+d3358 1
+a3358 1
+#: en_US/xml-tags.xml:2276(entry)
+d3362 9
+a3370 3
+#: en_US/xml-tags.xml:2278(member)
+msgid "Power switches enable each cluster system to power-cycle the other cluster system. Note that clusters are configured with either serial or network attached power switches and not both."
+msgstr "Os interruptores permitem a cada sistema do 'cluster' controlar a alimentação do outro sistema do 'cluster'. Lembre-se que os 'cluster's são configurados com interruptores série ou ligados à rede, não com ambos."
+d3372 1
+a3372 1
+#: en_US/xml-tags.xml:2283(member)
+d3376 1
+a3376 1
+#: en_US/xml-tags.xml:2286(member)
+d3380 7
+a3386 3
+#: en_US/xml-tags.xml:2289(member)
+msgid "Latent support is provided for the following serial attached power switch. This switch has not yet been fully tested:"
+msgstr "O suporte latente é oferecido para o seguinte interruptor série. Este interruptor não foi completamente testado:"
+d3388 1
+a3388 1
+#: en_US/xml-tags.xml:2294(ulink)
+d3392 1
+a3392 1
+#: en_US/xml-tags.xml:2293(member)
+d3396 1
+a3396 1
+#: en_US/xml-tags.xml:2297(entry)
+d3398 3
+a3400 1
+msgstr "Altamente recomendado para a integridade dos dados em todas as condições de falha"
+d3402 1
+a3402 1
+#: en_US/xml-tags.xml:2310(command) en_US/xml-tags.xml:2314(command)
+d3406 28
+a3433 11
+#: en_US/xml-tags.xml:2318(para)
+msgid "Do not use the trademark entities &trade;, &copy;, or &reg; because the do not produce HTML output that works for all charsets. The HTML output produces by these entities are declared in the DTD and cannot be changed via the stylesheet."
+msgstr "Não use as entidades de marcas registadas &trade;, &copy; ou &reg;, dado que não produzem um resultado em HTML que funcione em todas as codificações de caracteres. O resultado em HTML produzido por estas entidades está declarado na DTD e não poderá ser alterado com a folha de estilo."
+
+#: en_US/xml-tags.xml:2323(para)
+msgid "Instead, use the <command>trademark</command> tag and its associates classes as follows:"
+msgstr "Em vez disso, use a marca <command>trademark</command> e as suas classes associadas, como se segue:"
+
+#: en_US/xml-tags.xml:2328(computeroutput)
+#, no-wrap
+msgid "\n<trademark>trademark symbol after me</trademark>\n<trademark class=\"registered\">registered trademark symbol after me</trademark>\n<trademark class=\"copyright\">copyright symbol after me</trademark>\n"
+d3440 1
+a3440 1
+#: en_US/xml-tags.xml:2338(command) en_US/xml-tags.xml:2342(command)
+d3444 7
+a3450 3
+#: en_US/xml-tags.xml:2345(para)
+msgid "To show what a user would type, use the <command>userinput</command> tag. For example:"
+msgstr "Para mostrar o que um dado utilizador iria escrever, use a marca <command>userinput</command>. Por exemplo:"
+d3452 1
+a3452 1
+#: en_US/xml-tags.xml:2350(computeroutput)
+d3454 5
+a3458 1
+msgid "\nAt the prompt, type:\n\n<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>\n"
+d3465 1
+a3465 1
+#: en_US/xml-tags.xml:2361(para)
+d3469 1
+a3469 1
+#: en_US/xml-tags.xml:2366(userinput)
+d3474 2
+a3475 1
+#: en_US/xml-tags.xml:2393(command) en_US/xml-tags.xml:2397(secondary) en_US/emacs.xml:540(computeroutput)
+d3479 1
+a3479 1
+#: en_US/xml-tags.xml:2400(para)
+d3481 3
+a3483 1
+msgstr "Para criar uma hiperligação para um URL dentro do seu texto, use o seguinte exemplo:"
+d3485 1
+a3485 1
+#: en_US/xml-tags.xml:2404(computeroutput)
+d3487 5
+a3491 1
+msgid "\nOnline &mdash; <ulink url=\"http://www.redhat.com/support/errata/\">\nhttp://www.redhat.com/support/errata/</ulink>; supplies errata \nyou can read online, and you can download diskette images easily.\n"
+d3498 21
+a3518 7
+#: en_US/xml-tags.xml:2415(para)
+msgid "Online —<ulink url=\"http://www.redhat.com/support/errata/\"> http://www.redhat.com/support/errata/</ulink>; supplies errata you can read online, and you can download diskette images easily."
+msgstr "Online — <ulink url=\"http://www.redhat.com/support/errata/\">http://www.redhat.com/support/errata/</ulink>; fornece uma errata que poderá ler 'online' e onde poderá transferir imagens de disquetes com facilidade."
+
+#: en_US/xml-tags.xml:2423(para)
+msgid "If the URL does not end in a filename, it must end in a slash (<computeroutput>/</computeroutput>) to be a properly formed URL. For example, <ulink url=\"http://www.redhat.com/\">http://www.redhat.com/</ulink>."
+msgstr "Se o URL não terminar com o nome de um ficheiro, deverá terminar com uma barra (<computeroutput>/</computeroutput>), de modo a ser um URL completamente válido. Por exemplo, <ulink url=\"http://www.redhat.com/\">http://www.redhat.com/</ulink>."
+d3520 1
+a3520 1
+#: en_US/xml-tags.xml:2434(command) en_US/xml-tags.xml:2438(secondary)
+d3524 43
+a3566 15
+#: en_US/xml-tags.xml:2441(para)
+msgid "The <wordasword> tag set is used to define a word meant specifically as a word and not representing anything else."
+msgstr "O conjunto de marcas <wordasword> é usado para definir uma palavra que é suposto representar mesmo uma palavra e não representar outro conceito qualquer."
+
+#: en_US/xml-tags.xml:2444(para)
+msgid "A lot of technical documentation contains words that have overloaded meanings. Sometimes it is useful to be able to use a word without invoking its technical meaning. The <wordasword> element identifies a word or phrase that might otherwise be interpreted in some specific way, and asserts that it should be interpreted simply as a word."
+msgstr "Diversa documentação contém palavras que têm significados sobrepostos. Algumas vezes é útil ter a possibilidade de usar uma palavra sem invocar o seu significado técnico. O elemento <wordasword> identifica uma palavra ou frase que poderá ser interpretada de alguma forma específica, indicando que deverá ser interpretada apenas como uma palavra."
+
+#: en_US/xml-tags.xml:2450(para)
+msgid "It is unlikely that the presentation of this element will be able to help readers understand the variation in meaning; good writing will have to achieve that goal. The real value of <wordasword> lies in the fact that full-text searching and indexing tools can use it to avoid false-positives."
+msgstr "É pouco provável que a apresentação deste elemento seja capaz de ajudar os leitores a compreender a diferença de significado; uma boa escrita terá de conseguir esse objectivo. O valor real do <wordasword> reside no facto que as ferramentas de pesquisa e indexação no texto completo podê-la-ão usar para evitar falsos positivos."
+
+#: en_US/xml-tags.xml:2459(computeroutput)
+#, no-wrap
+msgid "To use <command>grep</command> to search for the word\n<wordasword>linux</wordasword>, use the command \n<command>grep linux</command>."
+d3572 19
+a3590 7
+#: en_US/xml-tags.xml:2468(para)
+msgid "To use <command>grep</command> to search for the word <wordasword>linux</wordasword>, use the command <command>grep linux</command>."
+msgstr "Para usar o <command>grep</command> na pesquisa pela palavra <wordasword>linux</wordasword>, use o comando <command>grep linux</command>."
+
+#: en_US/xml-tags.xml:2472(para)
+msgid "In the example, the word \"linux\" is just a word. It is not meant to convey anything about Linux as a subject, or to add relevance or meaning to the content. It can be replaced with any other word without losing any of the context."
+msgstr "No exemplo, a palavra \"linux\" é apenas uma palavra. Não diz respeito ao Linux como um assunto nem pretende adicionar relevância ou significado ao conteúdo. Esta poderá ser substituída por outra palavra qualquer, sem perder nenhum do contexto."
+d3592 1
+a3592 1
+#: en_US/xml-tags.xml:2481(command) en_US/xml-tags.xml:2485(secondary)
+d3596 7
+a3602 3
+#: en_US/xml-tags.xml:2488(para)
+msgid "To refer to other sections or chapters within a manual, use the <command><xref></command> tag."
+msgstr "Para fazer referência a outras secções ou capítulos dentro de um manual, use a marca <command><xref></command>."
+d3604 7
+a3610 3
+#: en_US/xml-tags.xml:2493(para)
+msgid "The output of this displays the title of the section or chapter you are pointing the user to. For example:"
+msgstr "O resultado disto mostra o título da secção ou capítulo para onde está a apontar o utilizador. Por exemplo:"
+d3612 1
+a3612 1
+#: en_US/xml-tags.xml:2498(computeroutput)
+d3614 4
+a3617 1
+msgid "\nFor more information about the parent file, refer to\n<xref linkend=\"ch-tutorial\"></xref> and <xref linkend=\"sn-tutorial-parent\"></xref>\n"
+d3623 7
+a3629 3
+#: en_US/xml-tags.xml:2508(para)
+msgid "For more information about the parent file, refer to <xref linkend=\"ch-tutorial\"/> and <xref linkend=\"sn-tutorial-parent\"/>."
+msgstr "Para mais informações acerca do ficheiro-pai, veja em <xref linkend=\"ch-tutorial\"></xref> e <xref linkend=\"sn-tutorial-pai\"></xref>."
+d3631 1
+a3631 1
+#: en_US/vim.xml:13(title)
+d3635 1
+a3635 1
+#: en_US/vim.xml:16(primary) en_US/vim.xml:33(primary)
+d3639 16
+a3654 3
+#: en_US/vim.xml:19(para)
+msgid "VIM has many features to help you write XML content such as DocBook, including syntax highlighting and customizable key bindings. Additionally, one can easily use external programs from VIM for features such as spell-checking. This chapter assumes you already know generally how to use VIM; if you want to learn how, try the <command>vimtutor</command> or by typing <userinput>:help tutor</userinput> from inside VIM."
+msgstr "O VIM tem diversas funcionalidades que o ajudam a criar conteúdos em XML, como o DocBook, incluindo o realce de sintaxe e a atribuição de atalhos de teclado personalizados. Para além disso, poderá usar facilmente programas externos a partir do VIM para funcionalidades como a verificação ortográfica. Este capítulo assume que já tem algum conhecimento geral de utilização do VIM; se quiser aprender como, experimente o <command>vimtutor</command> ou escrevendo <userinput>:help tutor</userinput> dentro do VIM."
+d3656 1
+a3656 1
+#: en_US/vim.xml:30(title)
+d3660 1
+a3660 1
+#: en_US/vim.xml:34(secondary) en_US/emacs.xml:44(secondary)
+d3664 16
+a3679 2
+#: en_US/vim.xml:37(para)
+msgid "Below is a short sample <filename>.vimrc</filename> file that turns on some VIM features useful for editing SGML or XML content such as DocBook: <screen>\n<computeroutput>\" Turn off vi compatibility settings like limited undo\nset nocompatible\n\" Syntax highlighting based on file extension\nsyntax on\n\" Automatically insert newlines after 80 characters\nset textwidth=80\n\" Automatically indent\nset autoindent\n\" Match SGML tags with %\nsource $VIMRUNTIME/macros/matchit.vim</computeroutput>\n</screen>"
+d3681 5
+a3685 2
+"Segue-se um pequeno exemplo do ficheiro <filename>.vimrc</filename> que activa algumas das funcionalidades úteis do VIM para editar conteúdos em SGML ou XML, como o DocBook: <screen>\n"
+"<computeroutput>\" Desligar as opções de compatibilidade, como o 'desfazer' limitado\n"
+d3697 16
+a3712 3
+#: en_US/vim.xml:55(para)
+msgid "Some of these features require the <filename>vim-enhanced</filename> package to be installed. If you are using or the <filename>vim-minimal</filename> package, or if you are using an older version of VIM, you may not have the <filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still download <ulink url=\"http://vim.org/scripts/script.php?script_id=39\">matchit.zip from Vim.org</ulink> and load it separately."
+msgstr "Algumas destas funcionalidades necessitam de ter instalado o pacote <filename>vim-enhanced</filename>. Se estiver a usar o pacote <filename>vim-minimal</filename> ou se estiver a usar uma versão antiga do VIM, poderá não ter o ficheiro <filename>$VIMRUNTIME/macros/matchit.vim</filename>. Poderá à mesma transferir o <ulink url=\"http://vim.org/scripts/script.php?script_id=39\">ficheiro matchit.zip do Vim.org</ulink> e carregá-lo em separado."
+d3714 1
+a3714 1
+#: en_US/vim.xml:69(title)
+d3718 38
+a3755 2
+#: en_US/vim.xml:71(para)
+msgid "VIM can speed up your DocBook creation by mapping frequently typed tags (or any words or phrases) onto short key combinations. By default, the keymap leader is the backslash (<literal>\\</literal>), but it can be redefined with a command like <userinput>let mapleader =\n \",\"</userinput>. There are two ways to use the following example; you can put it directly in your <filename>.vimrc</filename>, or you can save it in a separate file and load it with a <userinput>source</userinput> command in your <filename>.vimrc</filename>. <screen>\n<![CDATA[let mapleader = \",\"\n\n\" skip ahead to after next tag without leaving insert mode\nimap <leader>e <esc>/><cr>:nohlsearch<cr>a\n\n\" common tags that start a new text block\nimap<leader>pa <para><cr></para><esc>O\nimap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\nimap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\nimap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n\n\" common
tags that are placed inline\n\" use <esc>F>a\nimap<leader>en <envar></envar><esc>F>a\nimap<leader>fi <filename></filename><esc>F>a\nimap<leader>lt <literal></literal><esc>F>a\nimap<leader>re <replaceable></replaceable><esc>F>a\nimap<leader>ui <userinput></userinput><esc>F>a\nimap<leader>ul <ulink url=\"\"></ulink><esc>F>a\nimap<leader>si <systemitem></systemitem><esc>F>a\nimap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\nimap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\nimap<leader>cm <command></command><esc>F>a \n\" entities\nimap <leader>> >\nimap <leader>< <]]>\n</screen>"
+d3757 9
+a3765 2
+"O VIM poderá acelerar a criação do seu DocBook, mapeando as teclas escritas com mais frequência (ou palavras ou frases) em combinações de teclas breves. Por omissão, o líder do mapa de teclados é a barra invertida (<literal>\\</literal>), mas poderá ser redefinida com um comando do tipo <userinput>let mapleader =\n"
+" \",\"</userinput>. Existem duas formas de usar o seguinte exemplo; podê-lo-á colocar direcamente no seu ficheiro <filename>.vimrc</filename> ou podê-lo-a gravar num ficheiro separado e fazendo referência com o comando <userinput>source</userinput> no seu <filename>.vimrc</filename>. <screen>\n"
+d3785 2
+a3786 1
+"imap<leader>cm <command></command><esc>F>a \n"
+d3792 11
+a3802 3
+#: en_US/vim.xml:110(para)
+msgid "Unfortunately, there is not currently a complete macro set for all DocBook commands, so you will need to define them yourself or customize the definitions in the examples from <xref linkend=\"sn-vim-additional-resources\"/>."
+msgstr "Infelizmente, não existe de momento um conjunto de macros completo para todos os comandos do DocBook, pelo que terá de os definir você mesmo ou personalizar as definições nos exemplos em <xref linkend=\"sn-vim-additional-resources\"/>."
+d3804 1
+a3804 1
+#: en_US/vim.xml:119(title)
+d3807 120
+a3926 40
+
+#: en_US/vim.xml:121(para)
+msgid "Additional information about VIM may be found from:"
+msgstr "Poderá encontrar mais informações acerca do VIM em:"
+
+#: en_US/vim.xml:127(para)
+msgid "<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to Vi Improved (VIM)</citetitle>"
+msgstr "<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-SGMLRC\"> Exemplo de sgml-vimrc</ulink> do <citetitle>Guia para principiantes do Vi Improved (VIM)</citetitle>"
+
+#: en_US/vim.xml:134(para)
+msgid "The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick Reference Card</ulink>"
+msgstr "O <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">Cartão de Referências Rápidas do VIM</ulink>"
+
+#: en_US/vim.xml:140(ulink)
+msgid "Vim as XML Editor"
+msgstr "O Vim como Editor de XML"
+
+#: en_US/vim.xml:145(para)
+msgid "The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the <filename>vim-common</filename> package —<filename>/usr/share/vim/<replaceable><version></replaceable>/doc/intro.txt</filename> or type <userinput>:help intro</userinput> from within VIM"
+msgstr "O <citetitle>MANUAL DE REFERÊNCIA DO VIM</citetitle>, que vem com o pacote <filename>vim-common</filename> —<filename>/usr/share/vim/<replaceable><versão></replaceable>/doc/intro.txt</filename> ou escrevendo <userinput>:help intro</userinput> dentro do VIM"
+
+#: en_US/tutorial.xml:12(title)
+msgid "The Layout of a Tutorial"
+msgstr "O Formato de um Tutorial"
+
+#: en_US/tutorial.xml:14(para)
+msgid "In this chapter, you will find an example of a Fedora Project documentation parent file. This example is specific to the way the Docs Project uses DocBook XML. The parent file contains the main structural format of the book, a link to the entities file that contain common entities that should be used, and an entity to change the version and date of the tutorial."
+msgstr "Neste capítulo, irá descobrir um exemplo de um ficheiro-pai de documentação do Projecto Fedora. Este exemplo é específico para a forma como o Projecto de Documentação usa o DocBook em XML. O ficheiro-pai contém o formato principal da estrutura do livro, uma referência para o ficheiro de entidades que contém as entidades comuns a usar, bem como uma entidade para alterar a versão e a data do tutorial."
+
+#: en_US/tutorial.xml:23(title)
+msgid "The Parent File"
+msgstr "O Ficheiro-Pai"
+
+#: en_US/tutorial.xml:25(para)
+msgid "Below is a sample parent file:"
+msgstr "Em baixo, encontra-se um ficheiro-pai de exemplo:"
+
+#: en_US/tutorial.xml:30(computeroutput)
+#, no-wrap
+msgid "\n<!DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook XML V4.2//EN\"\n \"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd\" [\n\n<!ENTITY % FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-en.xml\">\n%FEDORA-ENTITIES-EN;\n\n<!ENTITY VERSION \"0.1\"> <!-- change version of tutorial here -->\n\n<!ENTITY DOCID \"example-tutorial-&VERSION; (2003-07-07)\"> <!-- change last modified date here -->\n\n<!ENTITY LEGALNOTICE SYSTEM \"../common/legalnotice-en.xml\">\n\n\n]>\n\n<article id=\"example-tutorial\" lang=\"en\">\n <articleinfo>\n <title>Example Tutorial</title>\n <copyright>\n <year>2003</year>\n <holder>Red Hat Inc.</holder>\n <holder>Tammy Fox</holder>\n </copyright>\n <authorgroup>\n <author>\n\t<surname>Fox</surname>\n\t<firstname>Tammy</firstname>\n </author>\n
</authorgroup>\n &LEGALNOTICE;\n </articleinfo>\n\n <section id=\"some-section\">\n <title>Some Section</title>\n\n <para>\n This is an example section. You can also use section, section, etc.\n </para>\n\n <warning>\n <title>Warning</title>\n <para>\n\tExample of an admonition.\n </para>\n </warning>\n\n </section>\n\n<index id=\"generated-index\"></index>\n</article>\n"
+d3980 1
+a3980 1
+#: en_US/tutorial.xml:87(title)
+d3984 1
+a3984 1
+#: en_US/tutorial.xml:90(primary)
+d3988 1
+a3988 1
+#: en_US/tutorial.xml:91(secondary)
+d3992 9
+a4000 3
+#: en_US/tutorial.xml:94(para)
+msgid "All Fedora Project manuals <emphasis>must</emphasis> contain the file <filename>legalnotice.xml</filename>. This file makes the license for the file the GNU Free Documentation License (FDL)."
+msgstr "Todos os manuais do Projecto Fedora <emphasis>deverão</emphasis> conter o ficheiro <filename>legalnotice.xml</filename>. Este ficheiro faz com que a licença do ficheiro seja a GNU Free Documentation License (FDL)."
+d4002 1
+a4002 1
+#: en_US/tutorial.xml:100(para)
+d4006 1
+a4006 1
+#: en_US/style.xml:14(title)
+d4010 13
+a4022 3
+#: en_US/style.xml:16(para)
+msgid "Writing good technical documentation is not simply reproducing command lines and instruction sets. Good documentation is easy to read, understand, and translate, and presents a concise logical progression of concepts. Good documentation can also be defined by what it does <emphasis>not</emphasis> contain. Your tutorial should avoid:"
+msgstr "A escrita de boa documentação técnica não é simplemente reproduzir as linhas de comandos e os conjuntos de instruções. A boa documentação é fácil de ler, compreender e traduzir, oferecendo uma progressão lógica concisa dos conceitos. A boa documentação também poderá ser definida pelo que <emphasis>não</emphasis> contém. O seu tutorial deverá evitar:"
+d4024 1
+a4024 1
+#: en_US/style.xml:26(para)
+d4028 1
+a4028 1
+#: en_US/style.xml:31(para)
+d4032 1
+a4032 1
+#: en_US/style.xml:36(para)
+d4036 1
+a4036 1
+#: en_US/style.xml:41(para)
+d4040 1
+a4040 1
+#: en_US/style.xml:46(para)
+d4044 14
+a4057 3
+#: en_US/style.xml:51(para)
+msgid "This chapter contains style rules and guidelines for writing Fedora documentation. Guidelines are not the same as rules. It is acceptable to violate a guideline when it makes your material easier to understand. Follow guidelines whenever possible, but follow rules at all times. Assume any advice is a guideline unless identified otherwise."
+msgstr "Este capítulo contém regras e instruções de estilo para escrever documentação para o Fedora. As instruções não são necessariamente regras. É aceitável voltar uma instrução, se esta tornar o seu material mais fácil de compreender. Siga as instruções se possível, mas siga sempre as regras. Assuma que qualquer conselho é uma instrução a menos que seja identificado em contrário."
+d4059 1
+a4059 1
+#: en_US/style.xml:62(title)
+d4063 63
+a4125 15
+#: en_US/style.xml:64(para)
+msgid "Writing well comes naturally to almost no one. It is a skill that professional writers, even famous ones, must practice constantly. <firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> is the quality that separates elegant writing from the merely functional."
+msgstr "A boa escrita não vem naturalmente para a maior parte das pessoas. É um dom que os escritores profissionais, até mesmo os famosos, precisam de praticar constantemente. O <firstterm>Estilo</firstterm><indexterm><primary>estilo</primary></indexterm> é a qualidade que separa a escrita elegante da meramente funcional."
+
+#: en_US/style.xml:77(para)
+msgid "For example, refer to. <ulink url=\"http://www.online-literature.com/james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>. Please note that this example contains some mature themes and language, and is not suitable for all readers."
+msgstr "Por exemplo, veja em <ulink url=\"http://www.online-literature.com/james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/ulysses/18/</ulink>. Rpare por favor como este exemplo contém alguns temas e linguagem madura, mas não sendo adequado para todos os leitores."
+
+#: en_US/style.xml:71(para)
+msgid "Elegance comes in many forms. In prose and poetry, elegant writing may not follow some (or any) common rules of grammar, syntax, or spelling. A good example is Episode 18, \"Penelope,\" in James Joyce's novel <citetitle>Ulysses</citetitle><footnote id=\"fn-ulysses\"><placeholder-1/></footnote>. There, Joyce uses long streams of words without punctuation to simulate a character's internal consciousness. By violating basic rules of grammar and syntax, Joyce simulates the disorganized but loosely connected thought patterns of the narrator."
+msgstr "A elegância vem em diversas formas. Na prosa e na poesia, a escrita elegante poderá não seguir algumas (ou todas) as regras comuns da gramática, sintaxe ou ortografia. Um bom exemplo é o Episódio 18, \"Penélope,\" do romance de James Joyce <citetitle>Ulisses</citetitle><footnote id=\"fn-ulysses\"><placeholder-1/></footnote>. Aqui, Joyce usa grandes sequências de palavras sem pontuação, de modo a simular a consciência interna de uma personagem. Ao violar as regras básicas da sintaxe e da gramática, Joyce simula os padrões de pensamento desorganizados mas levemente ligados do narrador."
+
+#: en_US/style.xml:89(para)
+msgid "Technical documentation, however, should always respect these rules. The more a document departs from standard language usage, the more difficult the material becomes for the reader. For example, readers may not be native speakers of the language used, or they might be reading a translation. If the writer uses slang, idioms, or jargon, a reader or translator may easily become confused. The following example compares two different written executions of the same idea:"
+msgstr "Contudo, a documentação técnica deverá sempre respeitar estas regras. Quanto mais um documento se desviar da utilização comum da língua, mais difícil se torna o material para o leitor. Por exemplo, os leitores poderão não usar a língua do documento como língua nativa ou poderão estar a ler uma tradução. Se o escritor usar 'calão', dialectos ou termos demasiado técnicos, o leitor ou o tradutor poderão ficar facilmente confusos. O exemplo seguinte compara duas execuções da mesma ideia, escritas de forma diferente:"
+d4127 1
+a4127 1
+#: en_US/style.xml:100(title)
+d4136 11
+a4146 3
+#: en_US/style.xml:108(para)
+msgid "So you made the changes I showed you in the last section. What's the next thing you should do? Just pop your thumb drive onto your system and read the <filename>messages</filename> log. When you see \"USB device found,\" then Bob's your uncle."
+msgstr "Portanto, já fez as alterações que lhe mostrei na última secção. Qual é a próxima coisa que deseja fazer? Basta colocar a sua caneta no seu sistema e ler o ficheiro de registo <filename>messages</filename>. Quando ver \"USB device found,\", então o João é o seu tio."
+d4148 1
+a4148 1
+#: en_US/style.xml:116(title)
+d4153 118
+a4270 35
+#: en_US/style.xml:120(para)
+msgid "After you complete the configuration changes above, attach the USB removable media to your system. Use the <command>dmesg</command> command to examine the kernel message log. The message <computeroutput>USB device\n\t found</computeroutput> indicates that your device was installed successfully."
+msgstr "Depois de terminar as mudanças de configuração acima, ligue o dispositivo removível USB ao seu sistema. Use o comando <command>dmesg</command> para examinar o registo de mensagens do 'kernel'. A mensagem <computeroutput>USB device found</computeroutput> indica que o seu dispositivo foi instalado com sucesso."
+
+#: en_US/style.xml:129(para)
+msgid "The first example is more conversational English, which is not appropriate for official written documentation. The second example is more formal, but as a result it is easier to comprehend, both for native readers and translators."
+msgstr "O primeiro exemplo é um Inglês mais coloquial, o qual não é apropriado para documentação oficial escrita. O segundo exemplo é mais formal, mas tem como resultado uma maior facilidade de compreensão, quer para os leitores nativos quer para os tradutores."
+
+#: en_US/style.xml:135(para)
+msgid "Following style rules and guidelines also makes readers more comfortable with a set of documents. Consistent style enhances the professional appearance of documentation, and its perceived value. On the other hand, lapses in punctuation or poor grammar negatively affect a reader's reaction to written material. A reader can feel that an otherwise correct technical document is lacking in authority, simply because it is poorly written. Readers feel at ease when they do not have to struggle to understand an author's use of language."
+msgstr "Seguir as regras e instruções de estilo também deixa os leitores mais confortáveis com um determinado conjunto de documentos. Um estilo consistente melhor a aparência profissional da documentação, bem como o valor que é transmitido. Por outro lado, os lapsos de pontuação ou uma gramática incorrecta afectam de forma negativa a reacção de um leitor ao material escrito. Um leitor poderá sentir que um documento técnico não tem qualquer autoridade, simplesmente por estar mal escrito. Os leitores facilmente sentem que não têm de lidar com a compreensão da utilização da língua por parte de um autor."
+
+#: en_US/style.xml:146(para)
+msgid "This chapter cannot possibly cover enough material to make every reader a good writer. Some manuals devoted entirely to writing style are themselves hundreds of pages long. This chapter provides enough guidelines for intermediate writers to understand style usage in technical documentation."
+msgstr "Este capítulo não poderá cobrir possivelmente material suficiente para que um leitor seja um bom escritor. Existem alguns manuais dedicados por inteiro ao estilo de escrita, tendo alguns deles centenas de páginas. Este capítulo contém instruções suficientes para os escritores médios compreenderem a utilização do estilo de documentação técnica."
+
+#: en_US/style.xml:153(para)
+msgid "If you are not a practiced writer, whether of technical documentation or otherwise, you may benefit from other style resources. The following list is far from comprehensive, but provides a starting point:"
+msgstr "Se não for um escritor com prática, seja em documentação técnica ou noutra qualquer, poderá beneficiar de outros recursos de estilo. A lista que se segue não é excelente, mas oferece um bom ponto de partida:"
+
+#: en_US/style.xml:161(para)
+msgid "<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules and links to online versions can be found at: <ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+msgstr "<citetitle>The Elements of Style</citetitle>, de William Strunk. Poderá encontrar algumas regras básicas e referências para as versões 'online' em: <ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>"
+
+#: en_US/style.xml:176(para)
+msgid "<citetitle>The Chicago Manual of Style</citetitle>, by the University of Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle.org/\">http://www.chicagomanualofstyle.org/</ulink>"
+msgstr "<citetitle>The Chicago Manual of Style</citetitle>, da University of Chicago Press. Versão 'online': <ulink url=\"http://www.chicagomanualofstyle.org/\">http://www.chicagomanualofstyle.org/</ulink>"
+
+#: en_US/style.xml:183(para)
+msgid "<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/\">http://www.powa.org/</ulink>"
+msgstr "<citetitle>Paradigm Online Writing Assistant</citetitle>, mantido por Chuck Guilford, Ph.D. Apenas 'online': <ulink url=\"http://www.powa.org/\">http://www.powa.org/</ulink>"
+
+#: en_US/style.xml:190(para)
+msgid "There are many free software documentation projects which have developed their own style guidelines. This chapter, in fact, draws heavily on the <citetitle>GNOME Documentation Style Guidelines</citetitle> (<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr "Existem diversos projectos de documentação de 'software' que desenvolveram as suas próprias recomendações de estilo. Este capítulo, de facto, baseia-se em grande medida nas <citetitle>Recomendações de Estilo de Documentação do GNOME</citetitle> (<firstterm>GDSG</firstterm>). Poderá ler a <citetitle>GDSG</citetitle> original em <ulink url=\"http://developer.gnome.org/documents/style-guide/\">http://developer.gnome.org/documents/style-guide/</ulink>."
+d4272 1
+a4272 1
+#: en_US/style.xml:203(title)
+d4276 1
+a4276 1
+#: en_US/style.xml:206(title)
+d4280 1
+a4280 1
+#: en_US/style.xml:207(para)
+d4288 7
+a4294 3
+#: en_US/style.xml:218(para)
+msgid "This chapter provides a brief introduction to writing technical documentation."
+msgstr "Este capítulo oferece uma breve introdução à escritaq de documentação técnica."
+d4296 1
+a4296 1
+#: en_US/style.xml:224(title)
+d4300 9
+a4308 3
+#: en_US/style.xml:225(para)
+msgid "Technical writing for the Fedora Project imposes special constraints beyond the basic requirements of good prose. Good Fedora technical documentation has the following characteristics:"
+msgstr "A escrita técnica para o Projecto Fedora impõe restrições especiais para além dos requisitos básicos da boa prosa. Uma boa documentação técnica do Fedora tem as seguintes características:"
+d4310 1
+a4310 1
+#: en_US/style.xml:232(term)
+d4314 7
+a4320 3
+#: en_US/style.xml:234(para)
+msgid "Describe all of the functionality of a product. Do not omit functionality that you regard as irrelevant for the user."
+msgstr "Descreve todas as funcionalidades de um produto. Não omita funcionalidades que considere irrelevantes para o utilizador, do seu ponto de vista."
+d4322 1
+a4322 1
+#: en_US/style.xml:242(term)
+d4326 7
+a4332 3
+#: en_US/style.xml:249(para)
+msgid "Describe what you see. Do not describe what you want to see. Present your information in the order that users experience the subject matter."
+msgstr "Descreva o que vê. Não descreva o que deseja ver. Apresente a sua informação pela ordem em que os utilizadores deparam com o assunto."
+d4334 1
+a4334 1
+#: en_US/style.xml:257(term)
+d4338 9
+a4346 3
+#: en_US/style.xml:259(para)
+msgid "Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>) to help make your writing clear."
+msgstr "Leia <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en.wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/The_Elements_of_Style</ulink>) que o ajuda a tornar a sua escrita mais clara."
+d4348 1
+a4348 1
+#: en_US/style.xml:275(term)
+d4352 8
+a4359 3
+#: en_US/style.xml:277(para)
+msgid "Use agreed vocabulary throughout your documentation. Use the same vocabulary as other writers who are working on related documentation."
+msgstr "Use um vocabulário adequado ao longo da sua documentação. Use o mesmo vocabulário dos outros escritores que estão a trabalhar sobre documentos relacionados com este."
+d4361 1
+a4361 1
+#: en_US/style.xml:285(term)
+d4365 9
+a4373 3
+#: en_US/style.xml:287(para)
+msgid "Review your work frequently as you write your document. Ask yourself which words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for specific guidelines."
+msgstr "Reveja o seu trabalho com frequência, à medida que escreve o seu documento. Pergunte a si mesmo as palavras que poderá retirar. Veja algumas recomendações específicas em <xref linkend=\"sn-fundamentals-2\"/>."
+d4375 1
+a4375 1
+#: en_US/style.xml:297(title)
+d4379 8
+a4386 3
+#: en_US/style.xml:298(para)
+msgid "This section contains some basic style guidelines. Subsequent sections in this chapter expand on these guidelines to give more detailed guidance."
+msgstr "Esta secção contém algumas recomendações básicas de estilo. As secções seguintes deste capítulo expandem essas recomendações, para lhe dar conselhos mais detalhados."
+d4388 1
+a4388 1
+#: en_US/style.xml:305(term)
+d4392 1
+a4392 1
+#: en_US/style.xml:309(para)
+d4396 1
+a4396 1
+#: en_US/style.xml:314(para)
+d4400 1
+a4400 1
+#: en_US/style.xml:320(title)
+d4404 9
+a4412 3
+#: en_US/style.xml:321(para)
+msgid "Under normal operating conditions, the kernel does not always immediately write file data to the disks, storing it in a memory buffer and then periodically writing to the disks to speed up operations."
+msgstr "Em condições normais de operação, o 'kernel' não grava sempre imediatamente os dados do ficheiros nos discos, guardando-os numa área em memória e escrevendo periodicamente para os discos, de modo a acelerar as operações."
+d4414 1
+a4414 1
+#: en_US/style.xml:328(title)
+d4418 7
+a4424 3
+#: en_US/style.xml:329(para)
+msgid "Normally, the kernel stores the data in memory prior to periodically writing the data to the disk."
+msgstr "Normalmente, o 'kernel' guarda os dados em memória antes de os gravar periodicamente no disco."
+d4426 1
+a4426 1
+#: en_US/style.xml:337(term)
+d4430 1
+a4430 1
+#: en_US/style.xml:341(para)
+d4434 1
+a4434 1
+#: en_US/style.xml:346(para)
+d4438 1
+a4438 1
+#: en_US/style.xml:351(para)
+d4442 1
+a4442 1
+#: en_US/style.xml:357(title)
+d4446 23
+a4468 3
+#: en_US/style.xml:358(para)
+msgid "The <application>Workspace Switcher</application> applet helps you navigate all of the virtual desktops available on your system. The X Window system, working in hand with a piece of software called a <emphasis>window manager</emphasis>, allows you to create more than one virtual desktop, known as <emphasis>workspaces</emphasis>, to organize your work, with different applications running in each workspace. The <application>Workspace Switcher</application> applet is a navigational tool to get around the various workspaces, providing a miniature road map in the GNOME panel showing all your workspaces and allowing you to switch easily between them."
+msgstr "A 'applet' do <application>Selector do Espaço de Trabalho</application> ajuda-o a navegar em todos os ecrãs virtuais do seu sistema. O sistema X Window, funcionando em conjunto com uma pequena componente aplicacional, chamada de <emphasis>gestor de janelas</emphasis>, permite-lhe criar mais de um ecrã virtual, também conhecido por <emphasis>espaço de trabalho</emphasis>, para organizar o seu trabalho, com diferentes aplicações a correr em cada espaço de trabalho. A 'applet' do <application>Selector do Espaço de Trabalho</application> é uma ferramenta de navegação para percorrer os diversos espaços de trabalho, oferecendo um roteiro em miniatura no painel do GNOME, mostrando todos os seus espaços de trabalho e permitindo uma mudança simples entre eles."
+d4470 1
+a4470 1
+#: en_US/style.xml:375(title)
+d4474 24
+a4497 7
+#: en_US/style.xml:376(para)
+msgid "Use the <application>Workspace Switcher</application> to add new <emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different applications in each workspace. The <application>Workspace Switcher</application> applet provides a miniature map that shows all of your workspaces. You can use the <application>Workspace Switcher</application> applet to switch between workspaces."
+msgstr "Use o <application>Selector de Espaços de Trabalho</application> para adicionar novos <emphasis>espaços de trabalho</emphasis> ao ambiente gráfico GNOME. Poderá executar diferentes aplicações em cada um dos espaços de trabalho. A 'applet' do <application>Selector de Espaços de Trabalho</application> oferece um mapa em miniatura que mostra todos os seus espaços de trabalho. Poderá usar a 'applet' do <application>Selector de Espaços de Trabalho</application>, de modo a mudar de espaços de trabalho."
+
+#: en_US/style.xml:388(para)
+msgid "Plan the order of paragraphs before you start writing. Decide which topic you want to cover in each paragraph."
+msgstr "Planeie a ordem dos parágrafos antes de começar a escrever. Decida o tópico que deseja cobrir em cada parágrafo."
+d4499 1
+a4499 1
+#: en_US/style.xml:396(term)
+d4503 7
+a4509 3
+#: en_US/style.xml:398(para)
+msgid "Use explicit examples to demonstrate how an application works. Provide instructions rather than descriptions."
+msgstr "Use exemplos explícitos que demonstram como funciona uma aplicação. Forneça instruções em vez de descrições."
+d4511 1
+a4511 1
+#: en_US/style.xml:403(title)
+d4515 6
+a4520 3
+#: en_US/style.xml:405(para)
+msgid "There is a text box that you can use to find out the definition of a word."
+msgstr "Existe um campo de texto que poderá usar para descobrir a definição de uma palavra."
+d4522 1
+a4522 1
+#: en_US/style.xml:411(title)
+d4526 15
+a4540 7
+#: en_US/style.xml:412(para)
+msgid "To request a definition of a word, type the word in the text box, then select <guilabel>Lookup</guilabel>."
+msgstr "Para pedir a definição de uma palavra, escreva a palavra no campo de texto, seleccionando depois a opção <guilabel>Procurar</guilabel>."
+
+#: en_US/style.xml:418(para)
+msgid "Do not apply this guideline too rigidly. Sometimes you must explain how software works to support your how-to examples."
+msgstr "Não aplique esta recomendação de forma muito rígida. Algumas vezes tem de explicar como funciona o 'software' para suportar os seus exemplos."
+d4542 1
+a4542 1
+#: en_US/style.xml:427(term)
+d4546 1
+a4546 1
+#: en_US/style.xml:429(para)
+d4550 1
+a4550 1
+#: en_US/style.xml:433(title)
+d4554 1
+a4554 1
+#: en_US/style.xml:434(para)
+d4558 1
+a4558 1
+#: en_US/style.xml:439(title)
+d4562 1
+a4562 1
+#: en_US/style.xml:440(para)
+d4566 1
+a4566 1
+#: en_US/style.xml:452(title)
+d4570 19
+a4588 3
+#: en_US/style.xml:453(para)
+msgid "Inappropriate tone hinders reader access to information. A neutral tone free of opinion or personal flavor improves the reader's comprehension. Neutral tone helps writers to work in parallel on a large technical documentation project. Furthermore, additional writers may join the project at any time. Use of a neutral tone helps to achieve consistency across a documentation set, and thereby facilitates user access to information. The best way to achieve a common, neutral tone is to apply the following principles:"
+msgstr "Um tom inapropriado retrai o acesso do utilizador à informação. Um tom neutro e livre de opiniões ou escolhas pessoais aumenta a compreensão por parte do leitor. Um tom netruo ajuda os escritores a trabalharem em paralelo num projecto de documentação técnica grande. Para além disso, poder-se-ão juntar escritores adicionais ao projecto em qualquer altura. A utilização de um tom netruo ajuda a obter alguma consistência em torno de um conjunto de documentos, facilitando deste modo o acesso dos utilizadores à informação. A melhor forma de obter um tom neutro e comum é aplicar os seguintes princípios:"
+d4590 1
+a4590 1
+#: en_US/style.xml:466(term)
+d4594 8
+a4601 3
+#: en_US/style.xml:468(para)
+msgid "Humor distracts from the information you are trying to provide. Humor also makes documentation difficult to translate. Stay factual."
+msgstr "O humor distrai o leitor da informação que você está a tentar transmitir. O humor também torna a documentação mais difícil de traduzir. Resuma-se a factos."
+d4603 1
+a4603 1
+#: en_US/style.xml:476(term)
+d4607 9
+a4615 3
+#: en_US/style.xml:478(para)
+msgid "Whether you think a function is useful or woeful is irrelevant. Report the function to the user, with instructions about how to use the function. Stay accurate."
+msgstr "Se acha que uma dada função é útil ou inútil é irrelevante. Relate a função para o utilizador, com instruções de utilização da mesma. Mantenha-se correcto."
+d4617 1
+a4617 1
+#: en_US/style.xml:487(term)
+d4621 7
+a4627 3
+#: en_US/style.xml:489(para)
+msgid "Colloquial language is difficult to translate and usually culture-specific. Stay neutral."
+msgstr "A linguagem coloquial é difícil de traduzir e normalmente é específica da caltura. Mantenha-se neutro."
+d4629 1
+a4629 1
+#: en_US/style.xml:496(term)
+d4633 7
+a4639 3
+#: en_US/style.xml:498(para)
+msgid "An expression that is in common use today might convey something completely different tomorrow. Stay technical."
+msgstr "Uma expressão que seja de uso comum nos dias de hoje poderá representar algo completamente diferente amanhã. Mantenha-se técnico."
+d4641 1
+a4641 1
+#: en_US/style.xml:505(term)
+d4645 8
+a4652 3
+#: en_US/style.xml:507(para)
+msgid "Statements about the future developments of a product do not belong in technical documentation. Write about what you see right now. Stay real."
+msgstr "As referências aos futuros desenvolvimentos de um produto não pertencem à documentação técnica. Escreva apenas sobre o que existe agora. Mantenha-se realista."
+d4654 1
+a4654 1
+#: en_US/style.xml:517(title)
+d4658 16
+a4673 3
+#: en_US/style.xml:518(para)
+msgid "All of the decisions that you make about the structure and content of a manual follow from an understanding of the audience. Consider how the audience accesses the documentation, what sort of information the audience needs, and the experience level of the audience. Usually, you need to create documentation that is suitable for different audiences. The following sections introduce some of the audience-related topics you need to consider."
+msgstr "Todas as decisões que fizer acerca da estrutura e conteúdo de um manual partem de uma compreensão por parte da audiência. Pense na forma como a audiência acede à documentação, ao tipo de informação que a audiência necessita e ao nível de experiência da audiência. Normalmente, é necessário criar uma documentação que seja adequada para diferentes audiências. As seguintes secções introduzem alguns dos tópicos relacionados com a audiência que necessita de ter em consideração."
+d4675 1
+a4675 1
+#: en_US/style.xml:530(title)
+d4679 11
+a4689 3
+#: en_US/style.xml:531(para)
+msgid "Do not waste the time of the user who looks for information in your documentation. Users do not read technical documentation for entertainment. Users usually have specific questions. You need to give clear answers to those questions."
+msgstr "Não ocupe o tempo do utilizador que procura informações na sua documentação. Os utilizadores não lêem documentação técnica por entretenimento. Os utilizadores normalmente têm questões específicas. Terá de dar respostas claras a essas questões."
+d4691 1
+a4691 1
+#: en_US/style.xml:539(title)
+d4695 20
+a4714 3
+#: en_US/style.xml:540(para)
+msgid "New users to Fedora are likely to consult online tutorials for guidance about unfamiliar applications or functionality. Each tutorial should contain enough introductory information to tell new users how to start using the relevant functions. Each tutorial should also contain enough usage instructions to tell users the different actions that they can perform with the command or function. Keep these instructions task-oriented. Do not describe GUI screens, dialogs, and dialog elements in a tutorial, unless there is an unusual feature that affects your instructions."
+msgstr "Os utilizadores novos no Fedora provavelmente irão consultar os tutoriais 'onyline' para se orientarem nas aplicações ou funcionalidades pouco familiares. Cada tutorial deverá conter informação introdutória sufciente para indicar aos novos utilizadores como começar a usar as funções relevantes. Cada tutorial deverá também conter instruções de utilização suficientes para informar os utilizadores das diferentes acções que podem efectuar com o comando ou a função. Mantenha estas instruções orientadas às tarefas. Não descreva as janelas gráficas e os seus elementos num tutoria, a menos que exista alguma funcionalidade anormal que afecte as suas instruções."
+d4716 1
+a4716 1
+#: en_US/style.xml:554(title)
+d4720 9
+a4728 3
+#: en_US/style.xml:555(para)
+msgid "Experienced users are more likely to use documentation as a reference. The documentation therefore needs to be complete, well-organized, and in the case of printed manuals, well-indexed."
+msgstr "Os utilizadores experientes são mais aptos para usar a documentação como referência. A documentação aí tem de ser completa, bem organizada e, no caso dos manuais impressos, bem indexada."
+d4730 1
+a4730 1
+#: en_US/style.xml:563(title)
+d4734 7
+a4740 3
+#: en_US/style.xml:564(para)
+msgid "To avoid offending your readers, apply the following guidelines to your documentation:"
+msgstr "Para evitar ofender os seus leitores, aplique as seguintes recomendações à sua documentação:"
+d4742 1
+a4742 1
+#: en_US/style.xml:570(term)
+d4746 36
+a4781 14
+#: en_US/style.xml:572(para)
+msgid "Insider language includes both undefined jargon and the tendency of the computer community to shorten words. For example, use the term <literal>documentation</literal> instead of the term <literal>docs</literal>. A term may be jargon if it fails all the following conditions:"
+msgstr "A linguagem própria ou interna inclui algum calão indefinido e a tendência da comunidade informática de reduzir as palavras. Por exemplo, use o termo <literal>documentação</literal> em vez do termo <literal>docs</literal>. Um termo poderá ser considerado 'calão', se não respeitar qualquer uma das seguintes condições:"
+
+#: en_US/style.xml:581(para)
+msgid "The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> (<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora.redhat.com/docs/jargon-buster/</ulink>)."
+msgstr "O termo não aparece no <citetitle>Jargon Buster do Fedora</citetitle> (<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora.redhat.com/docs/jargon-buster/</ulink>)."
+
+#: en_US/style.xml:588(para)
+msgid "The term does not appear in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/ </ulink>)."
+msgstr "O termo não aparece no <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/ </ulink>)."
+
+#: en_US/style.xml:596(para)
+msgid "The term does not appear in the glossary of the manual that you are writing."
+d4784 5
+a4788 3
+#: en_US/style.xml:602(para)
+msgid "The term is not defined in the body text of the manual that you are writing."
+msgstr "O termo não está definido no texto do conteúdo do manual que está a escrever."
+d4790 1
+a4790 1
+#: en_US/style.xml:611(term)
+d4794 9
+a4802 3
+#: en_US/style.xml:613(para)
+msgid "Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</literal> do not exist. There is no need to identify gender in your instructions."
+msgstr "As construções de pronomes como o <literal>dele/dela</literal> ou <literal>ele/a</literal> não existem. Não existe a necessidade de reflectir o sexo da audiência na suas instruções."
+d4804 1
+a4804 1
+#: en_US/style.xml:621(term)
+d4808 7
+a4814 3
+#: en_US/style.xml:623(para)
+msgid "There is little point in giving an example that everyone in your town knows about, but is a complete mystery to everyone else in the world."
+msgstr "Não vale a pena dar um exemplo que seja conhecido em toda a sua cidade, mas que seja um completo mistério para o resto do mundo."
+d4816 1
+a4816 1
+#: en_US/style.xml:631(term)
+d4820 18
+a4837 7
+#: en_US/style.xml:633(para)
+msgid "There are few experiences more irritating for a user than documentation that says an action is easy or quick, when in fact the user cannot complete the action. Do not qualify or prejudge actions."
+msgstr "Existem poucas experiências mais irritantes para um utilizador que a documentação que diz que uma determinada acção é fácil ou rápida, quando o utilizador não consegue desempenhá-la de facto. Não qualifique ou faça juízos de valor das acções."
+
+#: en_US/style.xml:642(para)
+msgid "Other parts of this guide discuss in more detail tone and language usage that can cause offense."
+msgstr "Outras partes deste guia descrevem com mais detalhe o tom e linguagem que possam ser considerados ofensivos."
+d4839 1
+a4839 1
+#: en_US/style.xml:653(title)
+d4843 1
+a4843 1
+#: en_US/style.xml:656(title)
+d4847 10
+a4856 3
+#: en_US/style.xml:657(para)
+msgid "This section is drawn partly from the <citetitle>GDSG</citetitle>, and partly from <citetitle>The Elements of Style</citetitle>, updated as necessary for the needs of 21st-century technical documentation writers."
+msgstr "Esta secção é retirada em parte da <citetitle>GDSG</citetitle> e também em parte do documento <citetitle>The Elements of Style</citetitle>, actualizado de acordo com as necessidades dos escritores de documentação técnica do século XXI."
+d4860 19
+a4878 3
+#: en_US/style.xml:668(para)
+msgid "This section contains an alphabetical list of grammar and usage guidelines for use in Fedora documentation. Many of these guidelines are only applicable to English-language usage, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr "Esta secção contém uma lista alfabética das recomendações de gramática e utilização na documentação do Fedora. Muitas destas recomendações só se aplicam na utilização da língua Inglesa; para mais informações, consulte o <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) e o <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+d4880 1
+a4880 1
+#: en_US/style.xml:679(term)
+d4884 19
+a4902 7
+#: en_US/style.xml:681(para)
+msgid "A shortened form of a word or phrase that takes the place of the full word or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, <literal>p.m.</literal>, and so on. Apply the following rules when you use abbreviations:"
+msgstr "Uma forma resumida de uma palavra ou frase que toma o lugar da palavra ou frase completa, como por exemplo <literal>Dr.</literal>, <literal>a.m.</literal>, <literal>p.m.</literal>, e assim por diante. Aplique as seguintes regras quando usar abreviaturas:"
+
+#: en_US/style.xml:689(para)
+msgid "Avoid creating new abbreviations. Unfamiliar abbreviations can confuse rather than clarify a concept."
+msgstr "Evite a criação de novas abreviaturas. As abreviaturas pouco familiares poderão confundir mais um conceito que clarificar."
+d4904 1
+a4904 1
+#: en_US/style.xml:695(para)
+d4908 1
+a4908 1
+#: en_US/style.xml:700(para)
+d4912 9
+a4920 3
+#: en_US/style.xml:706(para)
+msgid "For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other words\" and <literal>e.g.</literal> for \"for example\", do not use the abbreviation. Spell out the entire phrase."
+msgstr "Para as abreviaturas das frases, como o <literal>i.e.</literal> para \"isto é\" e o <literal>p.ex.</literal> como \"por exemplo\", não use a abreviatura. Descreva a frase por inteiro."
+d4922 1
+a4922 1
+#: en_US/style.xml:715(term)
+d4926 9
+a4934 3
+#: en_US/style.xml:717(para)
+msgid "Use adjectives with caution. If an adjective is necessary to differentiate between items, then use adjectives. In all cases, test whether the phrase can stand alone without the adjective."
+msgstr "Use os adjectivos com cuidado. Se um adjectivo for necessário para diferenciar itens, então use os adjectivos. Em qualquer um dos casos, este se a frase poderá ficar bem sem o adjectivo."
+d4936 1
+a4936 1
+#: en_US/style.xml:726(term)
+d4940 23
+a4962 11
+#: en_US/style.xml:728(para)
+msgid "A term that represents a multi-word term. Typically, acronyms are formed in the following ways:"
+msgstr "Um termo que representa um conjunto de palavras. Tipicamente, os acrónimos são formados da seguinte forma:"
+
+#: en_US/style.xml:734(para)
+msgid "From the first letters of each word in a compound term, for example Table of Contents (TOC)."
+msgstr "Das primeiras letras de cada palavra num termo composto. Por exemplo, TOC significa 'Table of Contents' (Índice Analítico)."
+
+#: en_US/style.xml:740(para)
+msgid "From recognizable parts of a compound term, such as GNU Object Model Environment (GNOME)."
+msgstr "A partir de partes reconhecíveis de um termo composto, como o GNU Object Model Environment (GNOME)."
+d4964 1
+a4964 1
+#: en_US/style.xml:746(para)
+d4968 31
+a4998 15
+#: en_US/style.xml:751(para)
+msgid "On the first occurrence of an acronym, spell out the full term, with the acronym in parentheses."
+msgstr "Na primeira ocorrência de um acrónimo, descreva por completo o termo completo, tendo o acrónimo entre parêntesis."
+
+#: en_US/style.xml:757(para)
+msgid "Do not spell out the full compound for well-known acronyms, unless you think the information is useful for readers."
+msgstr "Não descreva extensivamente o termo completo para os acrónimos conhecidos, a menos que saiba que a informação é útil para os leitores."
+
+#: en_US/style.xml:764(para)
+msgid "Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than clarify a concept."
+msgstr "Evite a criação de novos acrónimos. Os acrónimos não conhecidos poderão confundir mais um conceito que clarificá-lo."
+
+#: en_US/style.xml:770(para)
+msgid "Write the acronym in uppercase letters, unless there is a compelling case for lowercase."
+msgstr "Escreva o acrónimo em maiúsculas, a não ser que haja um caso explícito para o uso de minúsculas."
+d5000 1
+a5000 1
+#: en_US/style.xml:776(para)
+d5004 1
+a5004 1
+#: en_US/style.xml:785(term)
+d5008 13
+a5020 3
+#: en_US/style.xml:787(para)
+msgid "Use adverbs with caution. If an adverb is necessary to qualify the function of a component, then use an adverb. In all cases, test whether the phrase can stand alone without the adverb. Classic superfluous adverbs <literal>simply</literal>, <literal>easily</literal>, <literal>quickly</literal>."
+msgstr "Use os advérbios com cuidado. Se for necessário um advérbio para qualificar a função de um componente, então use um advérbio. Em qualquer dos casos, teste se a frase pode ser usada sem o advérbio. Alguns exemplos de advérbios supérfluos são o <literal>simplesmente</literal>, <literal>facilmente</literal>, <literal>rapidamente</literal>."
+d5022 1
+a5022 1
+#: en_US/style.xml:798(term)
+d5026 1
+a5026 1
+#: en_US/style.xml:802(para)
+d5030 7
+a5036 3
+#: en_US/style.xml:808(para)
+msgid "Do not apply a sense of location or dimension to a software application. A user can not be \"in\" a text editor."
+msgstr "Não aplique um sentido de localização ou dimensão a uma aplicação informática. Um utilizador não pode estar \"dentro\" de um editor de texto."
+d5038 1
+a5038 1
+#: en_US/style.xml:818(term)
+d5042 7
+a5048 3
+#: en_US/style.xml:820(para)
+msgid "Do not use the definite article <literal>the</literal> to begin any of the following items:"
+msgstr "Não use o artigo definido <literal>the</literal> (o/a) para iniciar um dos seguintes itens (nota específica do Inglês):"
+d5050 1
+a5050 1
+#: en_US/style.xml:826(para)
+d5054 1
+a5054 1
+#: en_US/style.xml:831(para)
+d5058 1
+a5058 1
+#: en_US/style.xml:836(para) en_US/style.xml:1239(term)
+d5062 1
+a5062 1
+#: en_US/style.xml:841(para)
+d5066 1
+a5066 1
+#: en_US/style.xml:846(para)
+d5070 1
+a5070 1
+#: en_US/style.xml:851(para)
+d5074 1
+a5074 1
+#: en_US/style.xml:859(term)
+d5078 1
+a5078 1
+#: en_US/style.xml:861(para)
+d5082 1
+a5082 1
+#: en_US/style.xml:866(para)
+d5086 1
+a5086 1
+#: en_US/style.xml:871(para)
+d5090 1
+a5090 1
+#: en_US/style.xml:876(para)
+d5094 1
+a5094 1
+#: en_US/style.xml:882(title)
+d5098 6
+a5103 3
+#: en_US/style.xml:885(para)
+msgid "the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+msgstr "<guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> (opção Ajuda do Menu Principal)"
+d5105 1
+a5105 1
+#: en_US/style.xml:891(para)
+d5109 1
+a5109 1
+#: en_US/style.xml:896(para)
+d5113 1
+a5113 1
+#: en_US/style.xml:903(title)
+d5117 7
+a5123 3
+#: en_US/style.xml:906(para)
+msgid "the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</guimenu>"
+msgstr "the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</guimenu> (a opção Ajuda no Menu Principal)"
+d5125 1
+a5125 1
+#: en_US/style.xml:912(para)
+d5129 1
+a5129 1
+#: en_US/style.xml:917(para)
+d5133 1
+a5133 1
+#: en_US/style.xml:926(term)
+d5137 7
+a5143 3
+#: en_US/style.xml:930(para)
+msgid "Do not use brackets [such as these] as a substitute for parentheses (such as these)."
+msgstr "Não use parêntesis [deste tipo] como substituição dos parêntesis (deste tipo)."
+d5145 1
+a5145 1
+#: en_US/style.xml:936(para)
+d5149 10
+a5158 3
+#: en_US/style.xml:941(para)
+msgid "Do not use angle brackets to indicate variables in text, instead use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+msgstr "Não use os símbolos '<' e '>' para indicar as variáveis no texto; em vez disso, use a marca <sgmltag class=\"starttag\">replaceable</sgmltag>. Veja a utilização do <xref linkend=\"sn-xml-tags-replaceable\"/> para mais informações sobre a utilização desta marca."
+d5160 1
+a5160 1
+#: en_US/style.xml:953(term)
+d5164 1
+a5164 1
+#: en_US/style.xml:955(para)
+d5168 1
+a5168 1
+#: en_US/style.xml:960(para)
+d5170 3
+a5172 1
+msgstr "Todas as letras dos acrónimos, a menos que o acrónimo seja uma excepção conhecida"
+d5174 1
+a5174 1
+#: en_US/style.xml:966(para)
+d5178 1
+a5178 1
+#: en_US/style.xml:971(para)
+d5182 1
+a5182 1
+#: en_US/style.xml:976(para)
+d5184 2
+a5185 1
+msgstr "A letra inicial do nome de uma tecla, como a tecla <keycap>Shift</keycap>"
+d5187 1
+a5187 1
+#: en_US/style.xml:982(para)
+d5191 1
+a5191 1
+#: en_US/style.xml:986(title)
+d5195 7
+a5201 3
+#: en_US/style.xml:987(para)
+msgid "Avoid starting a sentence with a command name or application name that has a lowercase initial letter."
+msgstr "Evite começar uma frase com o nome de um comando ou aplicação que tenha um nome que começa por minúsculas."
+d5203 1
+a5203 1
+#: en_US/style.xml:994(para)
+d5207 1
+a5207 1
+#: en_US/style.xml:999(para)
+d5211 1
+a5211 1
+#: en_US/style.xml:1004(para)
+d5215 1
+a5215 1
+#: en_US/style.xml:1010(para)
+d5219 1
+a5219 1
+#: en_US/style.xml:1015(para)
+d5223 1
+a5223 1
+#: en_US/style.xml:1020(para)
+d5227 1
+a5227 1
+#: en_US/style.xml:1029(term)
+d5231 7
+a5237 3
+#: en_US/style.xml:1031(para)
+msgid "Use the same rules as for headings, for all captions accompanying figures and tables. Do not put a period at the end of a caption."
+msgstr "Use as mesmas regras dos destaques para todas as legendas das tabelas e figuras. Não coloque um ponto no fim de uma legenda."
+d5239 1
+a5239 1
+#: en_US/style.xml:1039(term)
+d5243 1
+a5243 1
+#: en_US/style.xml:1041(para)
+d5247 1
+a5247 1
+#: en_US/style.xml:1046(para)
+d5251 1
+a5251 1
+#: en_US/style.xml:1051(para)
+d5255 1
+a5255 1
+#: en_US/style.xml:1056(para)
+d5259 1
+a5259 1
+#: en_US/style.xml:1061(para)
+d5263 1
+a5263 1
+#: en_US/style.xml:1066(para)
+d5267 1
+a5267 1
+#: en_US/style.xml:1071(para)
+d5271 1
+a5271 1
+#: en_US/style.xml:1076(para)
+d5275 1
+a5275 1
+#: en_US/style.xml:1084(term)
+d5279 1
+a5279 1
+#: en_US/style.xml:1086(para)
+d5283 1
+a5283 1
+#: en_US/style.xml:1092(term)
+d5287 1
+a5287 1
+#: en_US/style.xml:1094(para)
+d5291 1
+a5291 1
+#: en_US/style.xml:1099(para)
+d5295 1
+a5295 1
+#: en_US/style.xml:1104(para)
+d5299 1
+a5299 1
+#: en_US/style.xml:1109(para)
+d5303 1
+a5303 1
+#: en_US/style.xml:1114(para)
+d5307 1
+a5307 1
+#: en_US/style.xml:1119(para)
+d5311 1
+a5311 1
+#: en_US/style.xml:1125(para)
+d5315 1
+a5315 1
+#: en_US/style.xml:1130(para)
+d5319 1
+a5319 1
+#: en_US/style.xml:1135(para)
+d5323 1
+a5323 1
+#: en_US/style.xml:1143(term) en_US/emacs-nxml.xml:86(title)
+d5327 1
+a5327 1
+#: en_US/style.xml:1145(para)
+d5331 1
+a5331 1
+#: en_US/style.xml:1151(term)
+d5335 7
+a5341 3
+#: en_US/style.xml:1153(para)
+msgid "Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</emphasis>, or <emphasis>isn't</emphasis>."
+msgstr "Não use contracções do tipo <emphasis>tá</emphasis>, <emphasis>tar</emphasis>, or <emphasis>né</emphasis>."
+d5343 1
+a5343 1
+#: en_US/style.xml:1160(term)
+d5347 10
+a5356 3
+#: en_US/style.xml:1162(para)
+msgid "Do not use the em dash or the en dash. Use a paragraph break or a colon instead, where you want to create an introductory piece of text. If you have several items that you want to introduce, then you can use a variable list."
+msgstr "Não use o hífen 'mdash' ou 'ndash'. Use uma quebra de parágrafo ou os dois-pontos em alternativa onde pretender criar um pedaço introdutório de texto. Se tiver vários itens que deseja introduzir, então poderá usar uma lista variável."
+d5358 1
+a5358 1
+#: en_US/style.xml:1171(term)
+d5362 1
+a5362 1
+#: en_US/style.xml:1173(para)
+d5366 1
+a5366 1
+#: en_US/style.xml:1178(para)
+d5370 1
+a5370 1
+#: en_US/style.xml:1183(para)
+d5374 1
+a5374 1
+#: en_US/style.xml:1191(term)
+d5378 1
+a5378 1
+#: en_US/style.xml:1193(para)
+d5382 23
+a5404 11
+#: en_US/style.xml:1198(para)
+msgid "Use numerals for fractions in tables and in units of measurement, but spell out fractions in prose."
+msgstr "Use numerais para as fracções nas tabelas e nas unidades de medida, mas descreva por extenso as fracções."
+
+#: en_US/style.xml:1204(para)
+msgid "Use a space between a numeral and a related fraction, if there is a possible ambiguity. For example: 1 1/2 instead of 11/2."
+msgstr "Use um espaço entre um numeral e uma fracção relacionada, se puder existir alguma ambiguidadde. Por exemplo: 1 1/2 em vez de 11/2."
+
+#: en_US/style.xml:1211(para)
+msgid "If a fraction is used in a compound modifier, insert a hyphen between the fraction and the unit of measurement."
+msgstr "Se uma fracção for usada num modificador composto, indique um hífen entre a fracção e a unidade de medida."
+d5406 1
+a5406 1
+#: en_US/style.xml:1220(term)
+d5410 1
+a5410 1
+#: en_US/style.xml:1222(para)
+d5414 1
+a5414 1
+#: en_US/style.xml:1228(term)
+d5418 11
+a5428 3
+#: en_US/style.xml:1230(para)
+msgid "Use standard American English grammar rules, refer to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr "Use as regras-padrão do Inglês Americano (para documentos em Inglês); veja em <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+d5430 1
+a5430 1
+#: en_US/style.xml:1241(para)
+d5434 1
+a5434 1
+#: en_US/style.xml:1246(para)
+d5438 1
+a5438 1
+#: en_US/style.xml:1251(para)
+d5440 2
+a5441 1
+msgstr "Letra maiúscula inicial para todos os substantivos, adjectivos e verbos."
+d5443 7
+a5449 3
+#: en_US/style.xml:1257(para)
+msgid "All lowercase letters for conjunctions, articles, and prepositions of fewer than four letters"
+msgstr "Todas as letras em minúsculas para as conjunções, artigos e proposições com menos de quatro letras"
+d5451 1
+a5451 1
+#: en_US/style.xml:1263(para)
+d5455 1
+a5455 1
+#: en_US/style.xml:1269(para)
+d5459 1
+a5459 1
+#: en_US/style.xml:1280(term)
+d5463 1
+a5463 1
+#: en_US/style.xml:1282(para)
+d5467 1
+a5467 1
+#: en_US/style.xml:1287(para)
+d5471 1
+a5471 1
+#: en_US/style.xml:1291(para)
+d5475 9
+a5483 3
+#: en_US/style.xml:1296(para)
+msgid "With some standard prefixes and suffixes. Use the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidance"
+msgstr "Com alguns prefixos e sufixos padrão. Use o <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) para ter algumas linhas-guia"
+d5485 1
+a5485 1
+#: en_US/style.xml:1305(para)
+d5489 8
+a5496 3
+#: en_US/style.xml:1310(para)
+msgid "In variable names of two or more words, such as <replaceable>directory-name</replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+msgstr "Nos nomes de variáveis com duas ou mais palavras, como o <replaceable>nome-pasta</replaceable>. Nota: <replaceable>filename</replaceable> (nome de ficheiro) é uma excepção."
+d5498 1
+a5498 1
+#: en_US/style.xml:1317(para)
+d5502 1
+a5502 1
+#: en_US/style.xml:1322(para)
+d5506 1
+a5506 1
+#: en_US/style.xml:1327(para)
+d5510 1
+a5510 1
+#: en_US/style.xml:1332(para)
+d5514 1
+a5514 1
+#: en_US/style.xml:1337(para)
+d5518 9
+a5526 3
+#: en_US/style.xml:1342(para)
+msgid "With a word that is listed as unhyphenated in the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+msgstr "Com uma palavra que aparece como não-hifenizada no <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) e que use um prefixo comum"
+d5528 1
+a5528 1
+#: en_US/style.xml:1351(para)
+d5532 1
+a5532 1
+#: en_US/style.xml:1359(term)
+d5536 1
+a5536 1
+#: en_US/style.xml:1361(para)
+d5538 2
+a5539 1
+msgstr "Não use termos em Latim. Tente usar um termo em Inglês, em alternativa."
+d5541 1
+a5541 1
+#: en_US/style.xml:1368(term)
+d5545 7
+a5551 3
+#: en_US/style.xml:1370(para)
+msgid "Do not use the term <emphasis>like</emphasis> to denote equivalence or similarity."
+msgstr "Não use o <emphasis>do tipo</emphasis> para demarcar uma equivalência ou semelhança."
+d5553 1
+a5553 1
+#: en_US/style.xml:1379(para)
+d5555 2
+a5556 1
+msgstr "Introduza uma lista com uma frase completa que termine com dois-pontos."
+d5558 1
+a5558 1
+#: en_US/style.xml:1386(term)
+d5562 1
+a5562 1
+#: en_US/style.xml:1388(para)
+d5566 3
+a5568 2
+#: en_US/style.xml:1393(para)
+msgid "Numbers from zero through nine unless the number is part of a measurement"
+d5571 1
+a5571 1
+#: en_US/style.xml:1398(para)
+d5575 7
+a5581 3
+#: en_US/style.xml:1403(para)
+msgid "Extreme values such as <emphasis>million</emphasis>, but precede the value with a numeral"
+msgstr "Valores extremos como o <emphasis>milhão</emphasis>, se bem que pode anteceder o valor com um numeral"
+d5583 1
+a5583 1
+#: en_US/style.xml:1409(para)
+d5587 7
+a5593 3
+#: en_US/style.xml:1414(para)
+msgid "A number that is immediately followed by a numeral, for example: <literal>two 10 MB files</literal>"
+msgstr "Um número que seja seguido imediatamente de um numeral, como por exemplo: <literal>dois ficheiros de 10 MB</literal>"
+d5595 1
+a5595 1
+#: en_US/style.xml:1423(term)
+d5599 1
+a5599 1
+#: en_US/style.xml:1425(para)
+d5601 3
+a5603 1
+msgstr "Use os numerais (em oposição aos números por extenso) nas seguintes situações:"
+d5605 1
+a5605 1
+#: en_US/style.xml:1430(para)
+d5609 1
+a5609 1
+#: en_US/style.xml:1435(para)
+d5613 1
+a5613 1
+#: en_US/style.xml:1439(para)
+d5617 1
+a5617 1
+#: en_US/style.xml:1444(para)
+d5621 1
+a5621 1
+#: en_US/style.xml:1449(para)
+d5625 1
+a5625 1
+#: en_US/style.xml:1454(para)
+d5629 1
+a5629 1
+#: en_US/style.xml:1459(para)
+d5633 1
+a5633 1
+#: en_US/style.xml:1464(para)
+d5637 1
+a5637 1
+#: en_US/style.xml:1472(term)
+d5641 1
+a5641 1
+#: en_US/style.xml:1474(para)
+d5645 7
+a5651 3
+#: en_US/style.xml:1479(para)
+msgid "To contain the abbreviation of a term on the first occurrence of the full term"
+msgstr "Para conter a abreviatura de um termo na primeira ocorrência do termo completo"
+d5653 1
+a5653 1
+#: en_US/style.xml:1485(para)
+d5655 2
+a5656 1
+msgstr "Nas referências a páginas do 'man', especificamente no número da secção"
+d5658 1
+a5658 1
+#: en_US/style.xml:1493(term)
+d5662 1
+a5662 1
+#: en_US/style.xml:1495(para)
+d5666 1
+a5666 1
+#: en_US/style.xml:1500(para)
+d5670 1
+a5670 1
+#: en_US/style.xml:1505(para)
+d5674 1
+a5674 1
+#: en_US/style.xml:1510(para)
+d5676 3
+a5678 1
+msgstr "Nas abreviaturas que possam ser confundidas com palavras, como por exemplo C.O.M., E.U."
+d5680 1
+a5680 1
+#: en_US/style.xml:1519(term)
+d5684 13
+a5696 3
+#: en_US/style.xml:1521(para)
+msgid "Use standard American English punctuation rules. In addition to the specific points of punctuation in this section, refer also to the <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+msgstr "Use as regras de pontuação normais do Inglês Americano. Para além dos sinais de pontuação específicos nesta secção, veja também no <citetitle>Chicago Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html</ulink>.)"
+d5698 1
+a5698 1
+#: en_US/style.xml:1531(term)
+d5702 7
+a5708 3
+#: en_US/style.xml:1533(para)
+msgid "Do not use a comma in numerals of four digits. Use a comma in numerals of more than four digits."
+msgstr "Não use um ponto nos numerais de quatro algarismos. Use o ponto nos numerais com mais de quatro algarismos."
+d5710 1
+a5710 1
+#: en_US/style.xml:1540(term)
+d5714 11
+a5724 3
+#: en_US/style.xml:1542(para)
+msgid "Use quotation marks to indicate material that is taken verbatim from another source. Do not use quotation marks to excuse terms from legitimacy. If the term is not legitimate, then use another term. If you must use that term, declare the term in the glossary and make the term legitimate."
+msgstr "Use as marcas de citação (plicas, aspas) para indicar o material que foi explicitamente retirado de outra fonte. Não use as aspas para retirar a legitimidade dos termos. Se o termo não for legítimo, então use outro termo. Se precisar de usar esse termo, declare-o no glossário e torne-o legítimo."
+d5726 1
+a5726 1
+#: en_US/style.xml:1553(term)
+d5730 20
+a5749 3
+#: en_US/style.xml:1555(para)
+msgid "When referring a user to another resource, use \"refer to\" instead of \"see\", and \"refer also to\" instead of \"see also\". This differentiates from the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag\">seealso</sgmltag> tags that are used in indexing. These tags create special links in the index. To be consistent throughout the document, we reserve the special words \"see\" and \"see also\" for hyperlinked index references, and use \"refer to\" and \"refer also to\" for non-hyperlinked and non-indexed references."
+msgstr "Ao referenciar um outro recurso, use o \"consulte\" em vez do \"veja\", ou então \"consulte também\" em vez de \"veja também\". Isto cria uma separação em relação às marcas <sgmltag class=\"starttag\">see</sgmltag> e <sgmltag class=\"starttag\">seealso</sgmltag>, as quais são usadas na indexação. Estas marcas criam referências especiais no índice. Para ser consistente ao longo do tempo, reservam-se as palavras especiais \"ver\" e \"ver também\" para o caso das referências com hiperligações, sendo que existe o \"consultar\" e o \"consultar também\" para o caso das referências não-ligadas e não-indexadas."
+d5751 1
+a5751 1
+#: en_US/style.xml:1570(term)
+d5755 1
+a5755 1
+#: en_US/style.xml:1572(para)
+d5759 1
+a5759 1
+#: en_US/style.xml:1578(term)
+d5763 9
+a5771 3
+#: en_US/style.xml:1580(para)
+msgid "Except where required as part of a filename, do not use slashes \"/\" in your writing. The construction <literal>and/or</literal>, for example, does not exist. Use one or the other term instead."
+msgstr "Excepto no caso de ser necessário como parte do nome de um ficheiro, não use as barras \"/\" na sua escrita. A construção <literal>e/ou</literal>, por exemplo, não existe. Use um termo ou o outro, em alternativa."
+d5773 1
+a5773 1
+#: en_US/style.xml:1589(term)
+d5777 10
+a5786 3
+#: en_US/style.xml:1591(para)
+msgid "Use standard American English spelling rules, refer to the <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+msgstr "Use as regras-padrão ortográficas do Inglês Americano; consulte o <citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) para obter mais informações."
+d5788 1
+a5788 1
+#: en_US/style.xml:1600(term)
+d5792 1
+a5792 1
+#: en_US/style.xml:1602(para)
+d5796 1
+a5796 1
+#: en_US/style.xml:1608(term)
+d5800 1
+a5800 1
+#: en_US/style.xml:1610(para)
+d5804 15
+a5818 7
+#: en_US/style.xml:1615(para)
+msgid "Use standard abbreviations for units of measurements, do not invent your own abbreviations."
+msgstr "Use as abreviaturas-padrão para as unidades de medida, não invente as suas próprias."
+
+#: en_US/style.xml:1621(para)
+msgid "For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of Electrical and Electronics Terms</citetitle>."
+msgstr "Para mais informações, veja em <citetitle>IEEE Standard Dictionary of Electrical and Electronics Terms</citetitle>."
+d5820 1
+a5820 1
+#: en_US/style.xml:1630(para)
+d5822 2
+a5823 1
+msgstr "Use pontos nas unidades abreviadas que possam ser confundidas com palavras."
+d5825 7
+a5831 3
+#: en_US/style.xml:1636(para)
+msgid "Most standard abbreviations of units account for both singular and plural usage."
+msgstr "A maior parte das abreviaturas-padrão das unidades têm em conta a utilização singular e plural."
+d5833 1
+a5833 1
+#: en_US/style.xml:1642(para)
+d5837 1
+a5837 1
+#: en_US/style.xml:1656(title)
+d5846 12
+a5857 3
+#: en_US/style.xml:1668(para)
+msgid "This section contains usage tips based on situations the Fedora Documentation Project editors have encountered in the past. You should read and understand these examples to improve your own documentation. The Fedora Documentation Project editors welcome additional examples."
+msgstr "Esta secção contém sugestões de utilização que se baseiam nas situações que os editores do Projecto de Documentação do Fedora encontraram no passado. Deverá ler e compreender estes exemplos para melhorar a sua própria documentação. Os editores do Projecto de Documentação do Fedora agradecem os exemplos adicionais."
+d5859 1
+a5859 1
+#: en_US/style.xml:1676(title)
+d5863 21
+a5883 3
+#: en_US/style.xml:1677(para)
+msgid "Always use active voice, except when it is awkward to do so. The tutorial tells the user how to accomplish a task, and should give instructions clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. These words are redundant in a tutorial, since the reader assumes you are outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" \"might,\" and other words that indicate you are unsure about the subject matter. Your tutorial should cover a subject authoritatively. The reader should never be concerned about unknown effects of following the tutorial."
+msgstr "Use sempre a voz activa, excepto se ficar estranha a sua utilização num determinado contexto. O tutorial diz ao utilizador como desempenhar uma tarefa, devendo dar as instruções de forma clara e concisa. Evite usar os termos \"dever\", \"ser necessário\", entre outros. Estas palavras são redundantes num tutorial, dado que o leitor assume que você já está a destacar os passos necessários para efectuar uma tarefa. Evite também usar os termos \"talvez\", \"poderá\" e outras palavras que indiquem que não tenha a certeza sobre a matéria em estudo. O seu tutorial deverá cobrir um assunto de forma autoritária. O leitor nunca se deverá preocupar com os efeitos desconhecidos de seguir o tutorial."
+d5885 1
+a5885 1
+#: en_US/style.xml:1690(title)
+d5889 1
+a5889 1
+#: en_US/style.xml:1691(para)
+d5893 1
+a5893 1
+#: en_US/style.xml:1694(para)
+d5897 1
+a5897 1
+#: en_US/style.xml:1700(title)
+d5901 1
+a5901 1
+#: en_US/style.xml:1701(para)
+d5905 1
+a5905 1
+#: en_US/style.xml:1708(title)
+d5909 14
+a5922 3
+#: en_US/style.xml:1709(para)
+msgid "Write in the present tense. A good rule of thumb is that the words \"will\" and \"shall\" are almost never needed in describing what the user should do or see. They add unnecessary length to sentences and can confuse translators. They are also often indicators of passive voice; refer also to <xref linkend=\"sn-misc-active-voice\"/>."
+msgstr "Escreva no tempo presente. Uma boa regra de algibeira é que palavras como \"será\" ou \"deverá\" quase nunca são necessárias para descrever o que o utilizador deverá ou fazer. Estas adicionam um tamanho desnecessário às frases e poderão confundir os tradutores. Estas normalmente também são indicações de voz passiva; consule também o tópico <xref linkend=\"sn-misc-active-voice\"/>."
+d5924 1
+a5924 1
+#: en_US/style.xml:1718(title)
+d5928 1
+a5928 1
+#: en_US/style.xml:1719(para)
+d5932 1
+a5932 1
+#: en_US/style.xml:1722(para)
+d5936 1
+a5936 1
+#: en_US/style.xml:1727(title)
+d5940 1
+a5940 1
+#: en_US/style.xml:1728(para)
+d5944 1
+a5944 1
+#: en_US/style.xml:1735(title)
+d5948 15
+a5962 3
+#: en_US/style.xml:1736(para)
+msgid "Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself the writer (whether including the reader or not), the Fedora Documentation Project, the Fedora community, or any other group. Do not refer to users with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word \"one.\" It is acceptable to refer to the reader with the second person pronoun \"you.\""
+msgstr "Não use a primeira pessoa \"Eu,\" ou \"nós\" para se referir a si próprio como escritor (quer inclua o leitor quer não), o Projecto de Documentação do Fedora, a comunidade do Fedora ou qualquer outro grupo. Não faça referências aos utilizadores com um pronome na terceira pessoa (\"ele\", \"ela\" ou \"eles/elas\"). É aceitável fazer referências ao leitor na segunda pessoa com o pronome \"você\"."
+d5964 1
+a5964 1
+#: en_US/style.xml:1745(title)
+d5968 15
+a5982 7
+#: en_US/style.xml:1746(para)
+msgid "As described in the last section, I always run <command>up2date</command> before configuring the Samba server."
+msgstr "Como foi descrito na última secção, eu executo sempre o <command>up2date</command> antes de configurar o servidor do Samba."
+
+#: en_US/style.xml:1751(para)
+msgid "If the user needs to back up his or her files, s/he should use the <command>tar</command> or <command>cpio</command> command."
+msgstr "Se o utilizador precisar de salvaguardar os ficheiros dele ou dela, ele/a deverá usar o comando <command>tar</command> ou <command>cpio</command>."
+d5984 1
+a5984 1
+#: en_US/style.xml:1757(title)
+d5988 15
+a6002 7
+#: en_US/style.xml:1758(para)
+msgid "Refer to the section on <command>up2date</command> before configuring the Samba server."
+msgstr "Veja a secção sobre o <command>up2date</command> antes de configurar o servidor do Samba."
+
+#: en_US/style.xml:1762(para)
+msgid "If necessary, users can back up files with the <command>tar</command> or <command>cpio</command> command."
+msgstr "Se necessário, os utilizadores poderão salvaguardar os ficheiros com o comando <command>tar</command> ou <command>cpio</command>."
+d6004 1
+a6004 1
+#: en_US/style.xml:1770(title)
+d6008 14
+a6021 3
+#: en_US/style.xml:1771(para)
+msgid "Avoid negative words when possible, since they give documentation an overly dogmatic tone. The word \"avoid\" is useful for this purpose. Note that contractions are often used for negative words such as <emphasis>don't</emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-contractions\"/>."
+msgstr "Evite as palavras negativas sempre que possível, dado que atribuem à documentação um carácter dogmático, de certa forma. A palavra \"evitar\" é útil para esse fim. De um modo geral na língua inglesa, as contracções são usadas para as palavras negativas como o <emphasis>don't</emphasis> ou o <emphasis>can't</emphasis>. Consulte a secção <xref linkend=\"vle-contractions\"/>."
+d6023 1
+a6023 1
+#: en_US/style.xml:1782(title)
+d6027 16
+a6042 3
+#: en_US/style.xml:1783(para)
+msgid "Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the like. While occasional use of these constructions is acceptable, overuse reduces the authority of your documentation. The documentation should adequately cover a stock installation of Fedora. It is impossible for a tutorial-length document to cover every possible configuration scenario. Address the most common scenarios and note discrepancies only as required."
+msgstr "Evite o uso excessivo do \"tipicamente\", \"normalmente\", \"na maior parte\", \"muitos\", entre outros. Embora seja aceitável um uso ocasional destas conjugações, o uso em ecesso reduz a autoridade da sua documentação. A documentação deverá cobrir de forma adequada uma instalação predefinida do Fedora. É impossível, para um documento com a dimensão de um tutorial, cobrir todos os cenários de configuração possíveis. Analise os cenários mais comuns e aponte apenas as discrepâncias mais necessárias."
+d6044 1
+a6044 1
+#: en_US/style.xml:1795(title)
+d6048 16
+a6063 3
+#: en_US/style.xml:1796(para)
+msgid "Avoid covering redundant material, such as how to update a Fedora system. These overarching topics may be covered in other tutorials. Writers frequently violate this guideline because they feel their tutorial is not long enough. Keep your tutorial from wandering off-topic. Instead, refer the reader to a separate tutorial whenever possible for complete coverage of that topic."
+msgstr "Evite a cobertura de material redundante, como a actualização de um sistema Fedora. Estes tópicos mais complicados podem ser cobertos noutros tutoriais. Os escritores violam normalmente esta recomendação por acharem que o seu tutorial não é suficientemente comprido. Mantenha o seu tutorial com o tópico bem definido e sem grandes desvios. Em vez disso, indique ao leitor para consultar um tutorial sparado, sempre que possível, para uma cobertura completa desse tópico."
+d6065 1
+a6065 1
+#: en_US/style.xml:1808(title)
+d6069 22
+a6090 3
+#: en_US/style.xml:1809(para)
+msgid "Avoid statements such as \"One of the most important things to do is <replaceable>XYZ</replaceable>.\" If the procedure is important, the reader already expects it to be in your tutorial. The converse is also true: If a procedure appears in your tutorial, the reader expects it is important. This is especially true if you use a whole section for the procedure in question. Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as required. If the whole section concerns how to do <replaceable>XYZ</replaceable>, leave this sentence out entirely. Refer also to <xref linkend=\"vle-golden-rule-4\"/>."
+msgstr "Evite frases do tipo \"Uma das coisas mais importantes a fazer é <replaceable>XYZ</replaceable>.\" Se o procedimento for importante, o leitor já está à espera dele no seu tutorial. O inverso também se aplica: se um procedimento aparece no seu tutorial, o leitor espera que este seja importante. Isto é particularmente verdadeiro se usar uma secção inteira para o procedimento em questão. Basta dizer, \"Faça <replaceable>XYZ</replaceable>.\". Depois disso, desenvolva de acordo com as necessidades. Se a secção completa disser respeito à forma como fazer <replaceable>XYZ</replaceable>, retire esta frase por inteiro. Consulte também a secção <xref linkend=\"vle-golden-rule-4\"/>."
+d6092 1
+a6092 1
+#: en_US/style.xml:1824(title)
+d6096 8
+a6103 3
+#: en_US/style.xml:1825(para)
+msgid "Use precise words for actions users should take. Do not instruct users to \"go\" to a selection, or \"find\" a menu."
+msgstr "Use palavras exactas para as acções que os utilizadores deverão efectuar. Não diga aos utilizadores para \"ir\" para uma selecção ou \"procurar\" um menu."
+d6105 1
+a6105 1
+#: en_US/style.xml:1830(title)
+d6109 6
+a6114 3
+#: en_US/style.xml:1833(para)
+msgid "Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</guimenuitem>"
+msgstr "Vá a <guimenu>Menu Principal</guimenu> -> <guimenuitem>XPTO</guimenuitem>"
+d6116 1
+a6116 1
+#: en_US/style.xml:1839(para)
+d6120 1
+a6120 1
+#: en_US/style.xml:1846(title)
+d6124 7
+a6130 3
+#: en_US/style.xml:1849(para)
+msgid "From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</guimenuitem>"
+msgstr "No <guimenu>Menu Principal</guimenu>, seleccione o <guimenuitem>XPTO</guimenuitem>"
+d6132 1
+a6132 1
+#: en_US/style.xml:1855(para)
+d6136 1
+a6136 1
+#: en_US/style.xml:1862(title)
+d6140 10
+a6149 3
+#: en_US/style.xml:1863(para)
+msgid "If you are writing about a GUI-only application, you may use \"click\" freely. If you are writing about an application that has a text-mode interface, use \"select\" instead as shown above."
+msgstr "Se estiver a escrever a escrever sobre uma aplicação somente gráfica, poderá usar o termo \"carregar\" ou \"clicar\" à vontade. Se estiver a escrever acerca de uma aplicação que também tem uma interface em modo texto, use o \"seleccionar\" como aparece acima."
+d6151 1
+a6151 1
+#: en_US/style.xml:1874(title)
+d6155 7
+a6161 3
+#: en_US/style.xml:1875(para)
+msgid "This section contains tips on how to use DocBook tags more effectively in your documentation."
+msgstr "Esta secção contém sugestões sobre a utilização mais eficiente da marcas de DocBook na sua documentação."
+d6163 1
+a6163 1
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:259(title)
+d6167 13
+a6179 3
+#: en_US/style.xml:1882(para)
+msgid "Avoid overuse of admonitions. Keep admonitions short and effective by using only the most important material inside the admonition. Move any background material required to explain the admonition statements outside the admonition. Use a short but descriptive title for an admonition. Use title case for the admonition title."
+msgstr "Evite o uso excessivo de advertências. Mantenha-as resumidas e efectivas, usando apenas o material mais importante dentro da advertência. Passe todo o material de segundo plano necessário para explicar as advertências para fora destas. Use um título breve mas descritivo para uma advertência. Use a capitalização no título da advertência."
+d6181 1
+a6181 1
+#: en_US/style.xml:1891(title)
+d6185 1
+a6185 1
+#: en_US/style.xml:1894(title)
+d6189 16
+a6204 3
+#: en_US/style.xml:1895(para)
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+msgstr "O comando <command>sfdisk</command> aceita um ficheiro de programa como dados de entrada para configurar as partições num disco rígido. Em alguns casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, criando uma tabela de partições incorrecta no seu disco. Use sempre o comando <command>sfdisk -n</command> para verificar o seu ficheiro antes de efectuar gravações no disco."
+d6206 1
+a6206 1
+#: en_US/style.xml:1909(title)
+d6210 1
+a6210 1
+#: en_US/style.xml:1917(title)
+d6214 40
+a6253 15
+#: en_US/style.xml:1918(para)
+msgid "Always use the <command>sfdisk -n</command> command to check your input file before writing to the disk."
+msgstr "Use sempre o comando <command>sfdisk -n</command> para verificar os seus dados de entrada, antes de gravar no disco."
+
+#: en_US/style.xml:1910(para)
+msgid "The <command>sfdisk</command> command accepts a script file as standard input to set up partitions on a hard disk. Sometimes <command>sfdisk</command> will simply reject an erroneous input file. In other cases, it will use the input verbatim, writing an incorrect partition table to your disk. <warning><placeholder-1/><placeholder-2/></warning>"
+msgstr "O comando <command>sfdisk</command> aceita um ficheiro de programa como dados de entrada para configurar as partições num disco rígido. Em alguns casos, o <command>sfdisk</command> irá rejeitar simplesmente um ficheiro de entrada inválido. Nos outros, irá usar os dados de entrada tal-e-qual, criando uma tabela de partições incorrecta no seu disco.<warning><placeholder-1/><placeholder-2/></warning>"
+
+#: en_US/style.xml:1925(para)
+msgid "Avoid punctuation in titles for sections or admonitions, except for commas only where demanded. Use a title that says something about the admonition comment, such as \"Reboot Required,\" instead of simply using the admonition type for a title (\"Note\")."
+msgstr "Evite a pontuação nos títulos das secções ou advertências, excepto as vírgulas e somente quando necessário. Use um título que diga algo sobre o comentário da advertência, como \"É Necessário Reiniciar,\" em vez de usar apenas o tipo de advertência como título (\"Nota\")."
+
+#: en_US/style.xml:1932(para)
+msgid "Follow the capitalization rules for headings in the title of an admonition."
+msgstr "Siga as regras de capitalização dos destaques no título de uma advertência."
+d6255 1
+a6255 1
+#: en_US/style.xml:1939(title)
+d6259 9
+a6267 3
+#: en_US/style.xml:1941(para)
+msgid "If your documentation formally states a specific value will be used as a convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> tag in your text or examples."
+msgstr "Se a sua documentação relatar formalmente que um determinado valor será usado como convenção, não use a marca <sgmltag class=\"starttag\">replaceable</sgmltag> no seu texto ou exemplos."
+d6269 1
+a6269 1
+#: en_US/style.xml:1950(title)
+d6273 15
+a6287 3
+#: en_US/style.xml:1951(para)
+msgid "Use the entities provided by the Fedora Documentation Project. These entities are found in the <filename>common/</filename> folder in the <filename>fedora-docs</filename> distribution. (Refer also to <xref linkend=\"ch-getting-files\"/>.) For instance, do not use abbreviations such as \"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" which produces the text \"Fedora 7.\""
+msgstr "Use as entidades oferecidas pelo Projecto de Documentação do Fedora. Estas entidades aparecem na pasta <filename>common/</filename> da distribuição <filename>fedora-docs</filename>. (Consulte também a secção <xref linkend=\"ch-getting-files\"/>.) Por exemplo, não use abreviaturas do tipo \"FC2.\" Em vez disso, use as entidades predefinidas \"&FC; &FCVER;,\" que irá gerar o texto \"Fedora 7.\""
+d6289 1
+a6289 1
+#: en_US/writing-guidelines.xml:11(title)
+d6293 2
+a6294 1
+#: en_US/writing-guidelines.xml:14(primary) en_US/writing-guidelines.xml:15(see)
+d6298 2
+a6299 1
+#: en_US/writing-guidelines.xml:19(primary) en_US/writing-guidelines.xml:26(secondary)
+d6303 1
+a6303 1
+#: en_US/writing-guidelines.xml:20(secondary)
+d6307 2
+a6308 1
+#: en_US/writing-guidelines.xml:21(seealso) en_US/writing-guidelines.xml:25(primary)
+d6312 7
+a6318 3
+#: en_US/writing-guidelines.xml:29(para)
+msgid "Please read this chapter carefully. This chapter describes the guidelines that must be followed such as naming conventions."
+msgstr "Por favor, leia este capítulo com cuidado. O mesmo descreve as recomendações que deverão ser seguidas, como as nomenclaturas."
+d6320 1
+a6320 1
+#: en_US/writing-guidelines.xml:38(title)
+d6324 3
+a6326 1
+#: en_US/writing-guidelines.xml:42(secondary) en_US/writing-guidelines.xml:46(primary) en_US/writing-guidelines.xml:59(primary)
+d6330 9
+a6338 3
+#: en_US/writing-guidelines.xml:49(para)
+msgid "This section explains the ID naming convention. IDs are unique identifiers that allow DocBook XML to cross-reference a section, chapter, or other element."
+msgstr "Esta secção explica a nomenclaturas de IDs. Os IDs são identificadores únicos que permitem ao DocBook em XML fazer referências a uma dada secção, capítulo ou outro elemento."
+d6340 2
+a6341 1
+#: en_US/writing-guidelines.xml:55(secondary) en_US/writing-guidelines.xml:60(secondary)
+d6345 1
+a6345 1
+#: en_US/writing-guidelines.xml:63(para)
+d6349 1
+a6349 1
+#: en_US/writing-guidelines.xml:67(para)
+d6353 17
+a6369 7
+#: en_US/writing-guidelines.xml:70(para)
+msgid "Start the ID with the special short two-character label. This makes URLs and other references to this ID human readable, by self-identifying the XML container type."
+msgstr "Inicie o ID pela legenda especial de dois caracteres. Esta faz com que os URLs e as outras referências a este ID sejam legíveis, identificando autoamticamente o tipo do contentor de XML."
+
+#: en_US/writing-guidelines.xml:76(para)
+msgid "<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used properly."
+msgstr "O <xref linkend=\"ex-id-usage\"/> demonstra alguns atributos de IDs usados correctamente como exemplos."
+d6371 1
+a6371 1
+#: en_US/writing-guidelines.xml:82(title)
+d6375 1
+a6375 1
+#: en_US/writing-guidelines.xml:91(title)
+d6379 1
+a6379 1
+#: en_US/writing-guidelines.xml:92(segtitle)
+d6383 1
+a6383 1
+#: en_US/writing-guidelines.xml:93(segtitle)
+d6387 1
+a6387 1
+#: en_US/writing-guidelines.xml:95(sgmltag)
+d6391 1
+a6391 1
+#: en_US/writing-guidelines.xml:96(literal)
+d6395 1
+a6395 1
+#: en_US/writing-guidelines.xml:100(literal)
+d6399 1
+a6399 1
+#: en_US/writing-guidelines.xml:103(sgmltag)
+d6403 1
+a6403 1
+#: en_US/writing-guidelines.xml:104(literal)
+d6407 1
+a6407 1
+#: en_US/writing-guidelines.xml:108(literal)
+d6411 1
+a6411 1
+#: en_US/writing-guidelines.xml:112(literal)
+d6415 1
+a6415 1
+#: en_US/writing-guidelines.xml:115(sgmltag)
+d6419 1
+a6419 1
+#: en_US/writing-guidelines.xml:116(literal)
+d6423 1
+a6423 1
+#: en_US/writing-guidelines.xml:120(literal)
+d6427 1
+a6427 1
+#: en_US/writing-guidelines.xml:124(literal)
+d6431 80
+a6510 31
+#: en_US/writing-guidelines.xml:128(para)
+msgid "Use the title of the item as the ID. Make your titles unique within a document to prevent conflicts. For example:"
+msgstr "Use o título do item como ID. Torne os seus títulos únicos dentro de um documento para evitar conflitos. Por exemplo:"
+
+#: en_US/writing-guidelines.xml:141(para)
+msgid "It is very important that you remember the caveats in this section. These are learned suggestions or rules that make your XML experience better."
+msgstr "É muito importante que recorde as contrapartidas desta secção. Estas são sugestões ou regras de aprendizagem que tornam melhor a sua experiência em XML."
+
+#: en_US/writing-guidelines.xml:151(para)
+msgid "Do not use the trademark entities <sgmltag class=\"genentity\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class=\"genentity\">reg</sgmltag> because the do not produce HTML output that works for all charsets. The HTML output produces by these entities are declared in the DTD and cannot be changed via the stylesheet."
+msgstr "Não use as entidades de marcas registadas <sgmltag class=\"genentity\">trade</sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag> ou <sgmltag class=\"genentity\">reg</sgmltag>, porque não produzem HTML válido que funcione em todas as codificações de caracteres. O resultado em HTML produzido por estas entidades está descrito na DTD e não pode ser alterado com a folha de estilo."
+
+#: en_US/writing-guidelines.xml:159(para)
+msgid "Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes as follows:"
+msgstr "Em vez disso, use a marca <sgmltag>trademark</sgmltag> e as suas classes associadas, como se segue:"
+
+#: en_US/writing-guidelines.xml:186(para)
+msgid "In general, use <sgmltag>para</sgmltag> tags around anything other than a simple paragraph. Doing so will create additional white space within the text itself in the PDF version."
+msgstr "De um modo geral, não use as marcas <sgmltag>para</sgmltag> em torno de tudo o que não seja um parágrafo simples. Ao fazê-lo, irá criar espaços em branco adicionais dentro do próprio texto, na versão em PDF."
+
+#: en_US/writing-guidelines.xml:191(para)
+msgid "Specifically, do not use <sgmltag>para</sgmltag> tags around the following (or, to put this another way, do not embed the following within <sgmltag class=\"element\">para</sgmltag> elements):"
+msgstr "Especificamente, não use as marcas <sgmltag>para</sgmltag> em torno do seguinte (ou, posto de outra forma, não incorpore o seguinte dentro das marcas <sgmltag class=\"element\">para</sgmltag>):"
+
+#: en_US/writing-guidelines.xml:216(term)
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag>listitem</sgmltag> tags"
+msgstr "Conteúdo dentro de elementos <sgmltag class=\"element\">para</sgmltag> residentes em marcas <sgmltag>listitem</sgmltag>"
+
+#: en_US/writing-guidelines.xml:219(para)
+msgid "Content inside <sgmltag class=\"element\">para</sgmltag> elements within <sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</emphasis> start immediately after the beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr "O conteúdo dentro das marcas <sgmltag class=\"element\">para</sgmltag> inseridas em marcas <sgmltag class=\"element\">listitem</sgmltag> <emphasis>deverá</emphasis> começar logo a seguir à marca inicial <sgmltag class=\"starttag\">para</sgmltag>, para evitar espaços em branco extra na versão em PDF."
+d6512 1
+a6512 1
+#: en_US/writing-guidelines.xml:243(title)
+d6516 24
+a6539 9
+#: en_US/writing-guidelines.xml:245(para)
+msgid "All the files must contain the CVS Id header. If you create a new file, the first line must be:"
+msgstr "Todos os ficheiros deverão conter o cabeçalho Id do CVS. Se criar um ficheiro novo, a primeira linha deverá ser:"
+
+#: en_US/writing-guidelines.xml:250(para)
+msgid "The first time it is committed to CVS (and every time it is committed to CVS) the line is updated automatically to include information about the file. For example:"
+msgstr "A primeira vez em que este ficheiro for enviado para o CVS (e sempre que forem enviadas novas versões), a linha actualizada automaticamente para incluir informações acerca do ficheiro. Por exemplo:"
+
+#: en_US/writing-guidelines.xml:262(primary) en_US/writing-guidelines.xml:292(secondary) en_US/writing-guidelines.xml:298(secondary) en_US/writing-guidelines.xml:304(secondary) en_US/writing-guidelines.xml:310(secondary) en_US/writing-guidelines.xml:316(secondary)
+d6543 3
+a6545 1
+#: en_US/writing-guidelines.xml:267(secondary) en_US/writing-guidelines.xml:293(tertiary) en_US/writing-guidelines.xml:362(secondary)
+d6549 3
+a6551 1
+#: en_US/writing-guidelines.xml:272(secondary) en_US/writing-guidelines.xml:299(tertiary) en_US/writing-guidelines.xml:347(secondary)
+d6555 3
+a6557 1
+#: en_US/writing-guidelines.xml:277(secondary) en_US/writing-guidelines.xml:305(tertiary) en_US/writing-guidelines.xml:342(secondary)
+d6561 3
+a6563 1
+#: en_US/writing-guidelines.xml:282(secondary) en_US/writing-guidelines.xml:311(tertiary) en_US/writing-guidelines.xml:352(secondary)
+d6567 3
+a6569 1
+#: en_US/writing-guidelines.xml:287(secondary) en_US/writing-guidelines.xml:317(tertiary) en_US/writing-guidelines.xml:357(secondary)
+d6573 82
+a6654 17
+#: en_US/writing-guidelines.xml:320(para)
+msgid "There are five types of admonitions in DocBook: <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the admonitions have the same structure: an optional <sgmltag class=\"element\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD does not impose any specific semantics on the individual admonitions. For example, DocBook does not mandate that a <sgmltag class=\"element\">warning</sgmltag> is reserved for cases where bodily harm can result."
+msgstr "Existem cinco tipos de advertências no DocBook: <sgmltag class=\"element\">caution</sgmltag> (cuidado), <sgmltag class=\"element\">important</sgmltag> (importante), <sgmltag class=\"element\">note</sgmltag> (nota), <sgmltag class=\"element\">tip</sgmltag> (sugestão) e <sgmltag class=\"element\">warning</sgmltag> (aviso). Todas as advertências têm a mesma estrutura: um <sgmltag class=\"element\">title</sgmltag> opcional, seguido dos elementos do nível dos parágrafos. A DTD do DocBook não impõe qualquer semântica específica das advertências individuais. Por exemplo, o DocBook não obriga que um <sgmltag class=\"element\">warning</sgmltag> esteja reservado para os casos em que possam resultar danos corporais."
+
+#: en_US/writing-guidelines.xml:334(title)
+msgid "Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element\">warning</sgmltag>"
+msgstr "Criar um <sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag> ou <sgmltag class=\"element\">warning</sgmltag>"
+
+#: en_US/writing-guidelines.xml:365(para)
+msgid "There are several ways to bring attention to text within a document. A <emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to bring additional information to the users' attention. A <emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful information or another way to do something. A <emphasis><sgmltag class=\"element\">caution</sgmltag></emphasis> is used to show the user they must be careful when attempting a certain step. An <emphasis><sgmltag class=\"element\">important</sgmltag></emphasis> tag set can be used to show the user a piece of information that should not be overlooked. While this information may not change anything the user is doing, it should show the user that this piece of information could be vital. A <emphasis><sgmltag class=\"element\">warning</sgmltag></emphasis> is used to show the reader that their current setup will change or be altered, such as files being removed, and they should not c
hoose this operation unless they are alright with the consequences."
+msgstr "Existem diversas formas de chamar a atenção ao texto dentro de um documento. Uma <emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> (nota) é usada para trazer informações para a atenção dos utilizadores. Uma <emphasis><sgmltag class=\"element\">tip</sgmltag></emphasis> (sugestão) é usada para mostrar ao utilizador alguma informação útil ou outra forma de fazer algo. Uma <emphasis><sgmltag class=\"element\">caution</sgmltag></emphasis> é usada para mostrar ao utilizador que deverá ter cuidado ao efectuar um determinado passo. Uma marca <emphasis><sgmltag class=\"element\">important</sgmltag></emphasis> pode ser usada para mostrar ao utilizador um pedaço de informação que não deva ser ignorado. Embora esta informação possa não alterar o que o utilizador irá fazer, deverá mostrar ao utilizador que esta informação poderá ser vital. Um <emphasis><sgmltag class=\"element\">warning</sgmltag></emphasis> é usado para mostrar ao leitor qu
e a sua configuração actual irá mudar ou ser alterada, como a remoção de ficheiros, pelo que não deverão escolher esta operação, a menos que estejam de acordo com as consequências."
+
+#: en_US/writing-guidelines.xml:385(para)
+msgid "The following lines of code show the basic setup for each case mentioned above, along with its appearance in HTML."
+msgstr "As seguintes linhas de código mostram a configuração básica de cada um dos casos indicados acima, em conjunto com a sua aparência em HTML."
+
+#: en_US/writing-guidelines.xml:395(para) en_US/writing-guidelines.xml:415(para) en_US/writing-guidelines.xml:425(para) en_US/writing-guidelines.xml:435(para)
+d6658 2
+a6659 1
+#: en_US/writing-guidelines.xml:404(title) en_US/emacs.xml:348(title) en_US/emacs.xml:396(title) en_US/emacs-nxml.xml:114(title)
+d6663 1
+a6663 1
+#: en_US/writing-guidelines.xml:405(para)
+d6667 1
+a6667 1
+#: en_US/writing-guidelines.xml:414(title)
+d6671 1
+a6671 1
+#: en_US/writing-guidelines.xml:442(title)
+d6675 2
+a6676 1
+#: en_US/writing-guidelines.xml:445(primary) en_US/writing-guidelines.xml:450(see) en_US/writing-guidelines.xml:454(see)
+d6680 1
+a6680 1
+#: en_US/writing-guidelines.xml:446(secondary)
+d6684 1
+a6684 1
+#: en_US/writing-guidelines.xml:449(primary)
+d6688 1
+a6688 1
+#: en_US/writing-guidelines.xml:453(primary)
+d6692 38
+a6729 11
+#: en_US/writing-guidelines.xml:457(para)
+msgid "There are two types of screenshots: graphical and textual. The philosophy on using these two types is <firstterm>rely on text over graphics</firstterm>. This means, if you can say it in text instead of showing a graphic, do so. A graphical screenshot of a GUI can create a good setting of objects to then describe textually, but you don't want to create a screenshot for each graphical step."
+msgstr "Existem dois tipos de imagens: gráficas e textuais. A filosofia na utilização destes dois tipos é <firstterm>basear-se em texto acima dos gráficos</firstterm>. Isto significa que, se puder dizer em texto, em vez de usar um gráfico, faça-o. Uma imagem gráfica de uma GUI poderá criar uma boa configuração de objectos que será depois descrita textualmente, mas não será interessante criar uma imagem por cada passo gráfico."
+
+#: en_US/writing-guidelines.xml:464(para)
+msgid "The main reason for this preference is that a block of text can usually convey more meaning than the same physical space of graphics. This is highly dependent on the graphic; obviously, a photographic image of a scene can convey more than 1000 words can. A GUI screenshot is usually full of blank space with a few elements that can just as easily be described or listed."
+msgstr "A razão principal para esta preferência é que um bloco de texto poderá conter normalmente mais significado que o mesmo espaço físico de uma imagem. Isto é altamente dependente do gráfico; obviamente, uma imagem vale mais que 1000 palavras. Ua imagem gráfica normalmente está cheia de espaço em branco, contendo apenas alguns elementos que poderão ser descritos ou listados facilmente."
+
+#: en_US/writing-guidelines.xml:470(para)
+msgid "The steps for taking a graphical screenshot illustrate how using text to describe a procedure is more concise than a series of screenshots."
+msgstr "Os passos para tirar uma imagem gráfica ilustram como a utilização de texto para descrever um dado procedimento é mais conciso que uma série de imagens."
+d6731 1
+a6731 1
+#: en_US/writing-guidelines.xml:475(term)
+d6735 105
+a6839 27
+#: en_US/writing-guidelines.xml:479(para)
+msgid "Set the theme to Bluecurve defaults. This gives a look that is familiar to most readers, and makes Fedora Documentation Project documents consistent. From the panel menu, choose <guimenu>Preferences</guimenu>, <guimenuitem>Theme</guimenuitem> and select <guimenuitem>Bluecurve</guimenuitem> from the theme list."
+msgstr "Configure o tema com as predefinições do Bluecurve. Este gera uma aparência que é familiar para a maioria dos leitores, tornando também os documentos do Projecto de Documentação do Fedora mais consistentes. No menu do painel, escolha as <guimenu>Preferências</guimenu>, <guimenuitem>Tema</guimenuitem> e depois o <guimenuitem>Bluecurve</guimenuitem> na lista de temas."
+
+#: en_US/writing-guidelines.xml:488(para)
+msgid "Set fonts to Bluecurve defaults as well. From the panel menu, choose <guimenu>Preferences</guimenu>, <guimenuitem>Fonts</guimenuitem>. Set the <guilabel>Application font</guilabel> and the <guilabel>Desktop font</guilabel> to Sans Regular 10. Set the <guilabel>Window Title font</guilabel> to Sans Bold 10. Set the <guilabel>Terminal font</guilabel> to Monospace Regular 10."
+msgstr "Configure os tipos de letra com os predefinidos do Bluecurve. No menu do painel, escolha as <guimenu>Preferências</guimenu>, <guimenuitem>Tipos de Letra</guimenuitem>. Configure o <guilabel>Tipo de letra da aplicação</guilabel> e o <guilabel>Tipo de letra do ambiente de trabalho</guilabel> como Sans Regular 10. Configure o <guilabel>Tipo de letra do título da janela</guilabel> como Sans Bold 10. Configure o <guilabel>Tipo de letra do terminal</guilabel> como Monospace Regular 10."
+
+#: en_US/writing-guidelines.xml:498(para)
+msgid "Before taking the screenshot, try to resize the targeted GUI element(s) to the smallest possible size they can be. Your target is an image of 500 pixels or less. If you are doing a screenshot of more than one GUI element, you may need to resize the screenshot in a following step."
+msgstr "Antes de tirar a fotografia, tente dimensionar os elementos gráficos com o tamanho mais pequeno possível. O seu objectivo é uma imagem com 500 pixels ou menos ainda. Se estiver a tirar uma fotografia com mais de um elemento gráfico, terá de dimensionar a imagem num passo seguinte."
+
+#: en_US/writing-guidelines.xml:506(para)
+msgid "To take the screenshot, select the GUI element with your mouse, bringing it to the forefront, or otherwise arranging the elements. Press <keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to capture a single GUI window. For capturing the entire desktop use <keycap>Print Screen</keycap>. If you are taking a shot of multiple elements and have grouped them closely together, you can crop the resulting image in <application>The GIMP</application>. The image will be in the PNG format."
+msgstr "Para tirar a imagem, seleccione o elemento gráfico com o seu rato, passando-o para primeiro plano, ou organizando os elementos. Carregue em <keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> para capturar uma única janela. Para capturar o ecrã completo, use o <keycap>Print Screen</keycap>. Se estiver a tirar uma fotografia de vários elementos e os tiver agrupado em conjunto, poderá recortar a imagem resultante no <application>The GIMP</application>. A imagem estará no formato PNG."
+
+#: en_US/writing-guidelines.xml:519(para)
+msgid "If you need to, you can resize using <application>The GIMP</application>. With the image open, right-click on it and choose <guimenu>Image</guimenu> -> <guimenuitem>Scale Image...</guimenuitem>. With the chain symbol intact, set the <guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click <guibutton>OK</guibutton>. Be sure to <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo> to save your changes to your PNG before converting to EPS."
+msgstr "Se precisar, poderá dimensionar a imagem com o <application>The GIMP</application>. Com a imagem aberta, carregue com o botão direito nesta e escolha a opção <guimenu>Imagem</guimenu> -> <guimenuitem>Escalar a Imagem...</guimenuitem>. Com o símbolo da corrente intacto, configure a <guilabel>Nova Largura</guilabel> com o valor <guilabel>500 px</guilabel> e carregue em <guibutton>OK</guibutton>. Certifique-se que carrega em <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo> para gravar as suas alterações no seu PNG, antes da conversão para EPS."
+
+#: en_US/writing-guidelines.xml:532(para)
+msgid "With the image open in <application>The GIMP</application>, right-click on the image, selecting <guimenu>File</guimenu> -> <guimenuitem>Save As...</guimenuitem>. Under <guimenu>Determine File Type:</guimenu>, select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</guibutton>. Allow flattening of the image by clicking <guibutton>Export</guibutton>."
+msgstr "Com a imagem aberta no <application>The GIMP</application>, carregue com o botão direito na imagem e seleccione a opção <guimenu>Ficheiro</guimenu> -> <guimenuitem>Gravar Como...</guimenuitem>. Em <guimenu>Determinar o Tipo de Ficheiro:</guimenu>, seleccione <guimenuitem>PostScript</guimenuitem>, carregando depois em <guibutton>OK</guibutton>. Active o alisamento da imagem com a opção <guibutton>Exportar</guibutton>."
+
+#: en_US/writing-guidelines.xml:541(para)
+msgid "In the <guilabel>Save as PostScript</guilabel> window, select <guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</guibutton>."
+msgstr "Na janela para <guilabel>Gravar como PostScript</guilabel>, seleccione <guilabel>PostScript Encapsulado</guilabel> e carregue em <guibutton>OK</guibutton>."
+d6841 1
+a6841 1
+#: en_US/writing-guidelines.xml:555(term)
+d6845 27
+a6871 11
+#: en_US/writing-guidelines.xml:557(para)
+msgid "Textual screen information is also useful for readers. Follow these guidelines for textual screenshots:"
+msgstr "A informação textual do ecrã também é útil para os leitores. Siga estas recomendações para as imagens textuais:"
+
+#: en_US/writing-guidelines.xml:561(para)
+msgid "If you use a graphical screenshot to illustrate a function, and the textual mode has identical functions, do not include both, unless omitting either would make your description unclear."
+msgstr "Se usar uma imagem gráfica para ilustrar uma função e o modo textual tiver funções idênticas, não inclua ambas, a menos que a omissão de uma delas torne a sua descrição menos clara."
+
+#: en_US/writing-guidelines.xml:567(para)
+msgid "Make your information generic over specific, and omit any username and machine information if possible. Do not include the shell prompt unless it is vital to the demonstration."
+msgstr "Opte por ter a sua informação genérica em vez de específica, omitindo a informação do utilizador e da máquina, se possível. Não inclua a linha de comandos, a menos que seja vital para a demonstração."
+d6873 1
+a6873 1
+#: en_US/writing-guidelines.xml:573(para)
+d6877 19
+a6895 7
+#: en_US/writing-guidelines.xml:577(para)
+msgid "When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show what the user types, and use <sgmltag class=\"element\">computeroutput</sgmltag> tags to show the resulting output."
+msgstr "Ao usar o <sgmltag class=\"element\">screen</sgmltag> para demonstrar um procedimento, use as marcas <sgmltag class=\"element\">userinput</sgmltag> para mostrar o que o utilizador escreve, usando as marcas <sgmltag class=\"element\">computeroutput</sgmltag> para mostrar o resultado."
+
+#: en_US/writing-guidelines.xml:585(para)
+msgid "<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual screenshot usage."
+msgstr "O <xref linkend=\"ex-text-screenshot-good\"/> é um exemplo de utilização de uma imagem textual."
+d6897 1
+a6897 1
+#: en_US/writing-guidelines.xml:590(title)
+d6901 5
+a6905 3
+#: en_US/writing-guidelines.xml:603(para)
+msgid "To find all the currently active ssh sessions, execute the following command:"
+msgstr "Para descobrir todas as sessões de SSH activas, execute o seguinte comando:"
+d6907 1
+a6907 1
+#: en_US/writing-guidelines.xml:605(userinput)
+d6912 1
+a6912 1
+#: en_US/writing-guidelines.xml:607(para)
+d6916 1
+a6916 1
+#: en_US/writing-guidelines.xml:609(computeroutput)
+d6918 5
+a6922 1
+msgid " 2564 ? S 0:23 /usr/sbin/sshd\n 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n 8032 pts/0 S 0:00 ssh user@@host.example.com\n 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+d6929 1
+a6929 1
+#: en_US/module-struct.xml:12(title)
+d6933 14
+a6946 3
+#: en_US/module-struct.xml:13(para)
+msgid "Documentation modules have a specific structure that enables the preconfigured tools to work correctly. Follow this structure exactly or you may have problems building your module. The Fedora Documentation Project build tools locate resources in the module and use them to build new output such as HTML or RPM packages."
+msgstr "Os módulos de documentação têm uma estrutura específica que activa as ferramentas pré-configuradas para funcionarem correctamente. Siga esta estrutura exacta ou então poderá vir a ter problemas com a compilação do seu módulo. As ferramentas de compilação do Projecto de Documentação do Fedora localizam os recursos no módulo e usam-nos para criar novos formatos de saída, como HTML ou pacotes RPM."
+d6948 1
+a6948 1
+#: en_US/module-struct.xml:19(title)
+d6952 8
+a6959 3
+#: en_US/module-struct.xml:20(para)
+msgid "<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example module, excluding any <filename class=\"directory\">CVS</filename> folders:"
+msgstr "A secção <xref linkend=\"ex-module-structure\"/> mostra uma árvore de pastas de um módulo de exemplo, excluindo as pastas <filename class=\"directory\">CVS</filename>:"
+d6961 1
+a6961 1
+#: en_US/module-struct.xml:24(title)
+d6965 1
+a6965 1
+#: en_US/module-struct.xml:45(title)
+d6969 1
+a6969 1
+#: en_US/module-struct.xml:46(segtitle)
+d6973 1
+a6973 1
+#: en_US/module-struct.xml:47(segtitle)
+d6977 1
+a6977 1
+#: en_US/module-struct.xml:48(segtitle)
+d6981 1
+a6981 1
+#: en_US/module-struct.xml:50(seg)
+d6985 2
+a6986 1
+#: en_US/module-struct.xml:51(seg) en_US/module-struct.xml:88(seg) en_US/module-struct.xml:95(seg)
+d6990 2
+a6991 1
+#: en_US/module-struct.xml:54(filename) en_US/module-struct.xml:160(systemitem)
+d6995 1
+a6995 1
+#: en_US/module-struct.xml:58(firstterm)
+d6999 27
+a7025 7
+#: en_US/module-struct.xml:59(para)
+msgid "Think of an XML entity as a predefined snippet of information. It can represent a chunk of XML source, or simply a word or character. If the information changes, it need be replaced only once, in the definition, to fix all usage."
+msgstr "Pense numa entidade de XML como um pedaço predefinido de informação. Poderá representar um bloco de código em XML, ou simplesmente uma palavra ou carácter. Se a informação se alterar, terá de ser substituída apenas uma vez na definição, de modo a corrigir todas as alterações."
+
+#: en_US/module-struct.xml:52(seg)
+msgid "This is the only directory absolutely required. It is named for the original language of the document, such as <placeholder-1/> (US English). The primary language does not have to be US English; all languages are supported. This directory contains all the XML source for the actual document, as well as XML source for document-specific <placeholder-2/><footnote><placeholder-3/></footnote>."
+msgstr "Esta é a única pasta que é absolutamente necessária. Esta tem o nome da língua original do documento, como por exemplo <placeholder-1/> (Inglês dos EUA). A língua primária não tem de ser o Inglês dos EUA; são suportadas todas as línguas. Esta pasta contém todo o código em XML do documento actual, assim como o código em XML específico do documento para <placeholder-2/><footnote><placeholder-3/></footnote>."
+d7027 1
+a7027 1
+#: en_US/module-struct.xml:67(seg)
+d7031 1
+a7031 1
+#: en_US/module-struct.xml:68(seg) en_US/module-struct.xml:78(seg)
+d7035 1
+a7035 1
+#: en_US/module-struct.xml:69(filename) en_US/module-struct.xml:73(filename)
+d7039 11
+a7049 3
+#: en_US/module-struct.xml:69(seg)
+msgid "The <placeholder-1/> directory is an optional directory where graphics for the document should be stored. If graphics are screenshots that are particular to a language, the <placeholder-2/> directory can and should be stored in a language directory."
+msgstr "A pasta <placeholder-1/> é uma pasta opcional onde serão gravadas as imagens do documento. Se estas forem imagens particulares para uma determinada língua, a pasta <placeholder-2/> pode e deve ser gravada numa pasta de línguas."
+d7051 1
+a7051 1
+#: en_US/module-struct.xml:77(seg)
+d7055 1
+a7055 1
+#: en_US/module-struct.xml:79(filename) en_US/module-struct.xml:167(filename)
+d7059 13
+a7071 3
+#: en_US/module-struct.xml:79(seg)
+msgid "The <placeholder-1/> directory contains specially formatted files created and used by translators. The Fedora Documentation Project build tools use these files to create translated versions of documents. The translated documents are not stored in CVS; they are created as needed from these PO files."
+msgstr "A pasta <placeholder-1/> contém os ficheiros especialmente formatados, criados e usados pelos tradutores. As ferramentas de compilação do Projecto de Documentação do Fedora usam estes ficheiros para criar versões traduzidas dos documentos. Os documentos traduzidos não são guardados no CVS; são criados à medida das necessidades a partir destes ficheiros PO."
+d7073 1
+a7073 1
+#: en_US/module-struct.xml:87(seg) en_US/module-struct.xml:89(filename)
+d7077 7
+a7083 3
+#: en_US/module-struct.xml:89(seg)
+msgid "The <placeholder-1/> controls the build process. Its content is discussed in <xref linkend=\"ex-makefile\"/>."
+msgstr "A <placeholder-1/> controla o processo de compilação. O seu conteúdo é discutido em <xref linkend=\"ex-makefile\"/>."
+d7085 1
+a7085 1
+#: en_US/module-struct.xml:94(filename) en_US/module-struct.xml:96(filename)
+d7089 1
+a7089 1
+#: en_US/module-struct.xml:96(seg)
+d7091 2
+a7092 1
+msgstr "O ficheiro <placeholder-1/> contém os meta-dados específicos do documento"
+d7094 1
+a7094 1
+#: en_US/module-struct.xml:102(title)
+d7098 12
+a7109 3
+#: en_US/module-struct.xml:103(para)
+msgid "The build system can render the document into another format such as <abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</command> and shell scripts. Authors need <emphasis>no</emphasis> prior experience with either shell scripts or a <command>make(1)</command>."
+msgstr "O sistema de compilação poderá representar o documento noutro formato, como o <abbrev>HTML</abbrev> ou o <abbrev>PDF</abbrev>, usando o <command>make(1)</command> e os programas da linha de comandos. Os autores <emphasis>não</emphasis> precisam de qualquer experiência anterior com os programas da linha de comandos ou o <command>make(1)</command>."
+d7111 1
+a7111 1
+#: en_US/module-struct.xml:111(title)
+d7115 18
+a7132 7
+#: en_US/module-struct.xml:112(para)
+msgid "Each individual document has its own <filename>Makefile</filename>, which only needs to be a few lines long. The document <filename>Makefile</filename> content is designed for cut and paste operations."
+msgstr "Cada documento individual tem a sua própria <filename>Makefile</filename>, que só necessita de ter algumas linhas. O conteúdo da <filename>Makefile</filename> do documento está desenhado para operações de corte e colagem."
+
+#: en_US/module-struct.xml:118(para)
+msgid "<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</filename> for a simple document with two files and two translations."
+msgstr "A <xref linkend=\"ex-makefile\"/> abaixo mostra a <filename>Makefile</filename> completa de um documento simples com dois ficheiros e duas traduções."
+d7134 1
+a7134 1
+#: en_US/module-struct.xml:124(title)
+d7138 9
+a7146 3
+#: en_US/module-struct.xml:141(para)
+msgid "Do not be concerned with some of the more complicated syntax such as the <command>XMLFILES_template</command> stanza. An explanation for this template appears a few paragraphs below."
+msgstr "Não se preocupe com alguma da sintaxe mais complicada, como o <command>XMLFILES_template</command>. Aparecerá em baixo uma explicação para este modelo."
+d7148 1
+a7148 1
+#: en_US/module-struct.xml:147(title)
+d7152 1
+a7152 1
+#: en_US/module-struct.xml:148(segtitle)
+d7156 1
+a7156 1
+#: en_US/module-struct.xml:149(segtitle) en_US/module-struct.xml:263(segtitle)
+d7160 1
+a7160 1
+#: en_US/module-struct.xml:151(systemitem)
+d7164 7
+a7170 3
+#: en_US/module-struct.xml:152(seg)
+msgid "This variable contains the name for the main (parent) XML document. Follow convention by naming your document after the module name."
+msgstr "Esta variável contém o nome do documento-pai principal em XML. Siga a convenção, nomeando o seu documento com o nome do módulo."
+d7172 1
+a7172 1
+#: en_US/module-struct.xml:157(systemitem)
+d7176 7
+a7182 3
+#: en_US/module-struct.xml:158(seg)
+msgid "This variable contains the ISO code for the original version of the document, such as <placeholder-1/>."
+msgstr "Esta variável contém o código ISO da versão original do documento, como em <placeholder-1/>."
+d7184 1
+a7184 1
+#: en_US/module-struct.xml:163(systemitem)
+d7188 10
+a7197 3
+#: en_US/module-struct.xml:164(seg)
+msgid "This variable contains a listing of ISO codes for any other versions into which the document has been translated. The module must contain a <placeholder-1/> directory and a PO file for any indicated additional languages."
+msgstr "Esta variável contém uma lista dos códigos ISO das outras versões traduzidas do documento. O módulo deverá conter uma pasta <placeholder-1/> e um ficheiro PO para cada língua adicional indicada."
+d7199 1
+a7199 1
+#: en_US/module-struct.xml:171(systemitem)
+d7203 12
+a7214 3
+#: en_US/module-struct.xml:172(seg)
+msgid "This variable contains a listing of any files containing entity definitions. The Fedora Documentation Project uses a special XML format to record document-specific entities, so they can be translated and built on the fly like any other XML document. An example is shown later in this guide."
+msgstr "Esta variável contém uma listagem de todos os ficheiros que contêm definições de entidades. O Projecto de Documentação do Fedora usa um formato em XML especial para guardar as entidades específicas do documento, de modo que possam ser traduzidas e geradas na altura, como se fosse outro documento em XML qualquer. Aparecerá então um exemplo mais tarde neste guia."
+d7216 1
+a7216 1
+#: en_US/module-struct.xml:181(systemitem)
+d7220 1
+a7220 1
+#: en_US/module-struct.xml:184(systemitem)
+d7224 1
+a7224 1
+#: en_US/module-struct.xml:189(systemitem)
+d7228 16
+a7243 3
+#: en_US/module-struct.xml:182(seg)
+msgid "This template allows the build tools to work with the document in multiple languages once it is translated. The <placeholder-1/> marking is a variable used to substitute the appropriate language. This template is not terribly complicated. For a new module, duplicate this section exactly except for the actual filenames. Prepend the text <placeholder-2/>, in place of the language code directory name, to each filename in your document."
+msgstr "Este modelo permite às ferramentas de compilação funcionarem com o documento em várias línguas, logo que esteja traduzido. A marcação <placeholder-1/> é uma variável que é usada para substituir a língua apropriada. Este modelo não é terrivelmente complicado. Para um módulo novo, duplique esta secção exactamente, excepto os nomes dos ficheiros em si. Coloque antes o texto <placeholder-2/>, no lugar do nome da pasta do código da língua, para cada nome de ficheiro no seu documento."
+d7245 1
+a7245 1
+#: en_US/module-struct.xml:195(title)
+d7249 22
+a7270 7
+#: en_US/module-struct.xml:196(para)
+msgid "Do not include the document-specific entities XML file or the <filename>rpm-info.xml</filename> file, which will be discussed later in this guide."
+msgstr "Não inclua o ficheiro XML de entidades específicas do documento nem o ficheiro <filename>rpm-info.xml</filename>, os quais serão descritos posteriormente neste guia."
+
+#: en_US/module-struct.xml:200(para)
+msgid "The final section, beginning with <literal>define</literal>, locates the main <filename>Makefile.common</filename> for the build system. This <filename>Makefile.common</filename> file contains all the <application>make(1)</application> targets and rules to actually build the document and the various archives."
+msgstr "A secção final, que começa por <literal>define</literal>, localiza o ficheiro <filename>Makefile.common</filename> principal para o sistema de compilação. Este ficheiro <filename>Makefile.common</filename> contém todos os alvos e regras do <application>make(1)</application> para criar de facto o documento e os vários pacotes."
+d7272 1
+a7272 1
+#: en_US/module-struct.xml:209(title)
+d7276 14
+a7289 3
+#: en_US/module-struct.xml:210(para)
+msgid "Each document module's primary language directory contains a file called <filename>rpm-info.xml</filename>. This file contains document-specific metadata used to generate revision history, copyright, and contributor information. It follows a DTD specification included with the rest of the build system tools."
+msgstr "Cada pasta da língua primária do módulo do documento contém um ficheiro chamado filename>rpm-info.xml</filename>. Este ficheiro contém os meta-dados específicos do documento que são usados para gerir o histórico de revisões, direitos de cópia e a informação de contribuintes. Esta segue uma especificação em DTD que vem incluída com o resto das ferramentas do sistema de compilação."
+d7291 1
+a7291 1
+#: en_US/module-struct.xml:216(para)
+d7295 1
+a7295 1
+#: en_US/module-struct.xml:219(title)
+d7299 12
+a7310 3
+#: en_US/module-struct.xml:248(para)
+msgid "If you are not familiar with XML editing, copy and paste this file from an existing module and then edit the values for the various elements as appropriate. Consult Fedora Documentation Project members and help channels for more assistance if needed."
+msgstr "Se não estiver familiarizado com a edição em XML, copie e cole este ficheiro a partir de um módulo existente e edite depois os valores dos vários elementos, como for mais apropriado. Consulte os membros do Projecto de Documentação do Fedora e os canais de ajuda para maior assistência, se for necessário."
+d7312 1
+a7312 1
+#: en_US/module-struct.xml:255(title)
+d7316 7
+a7322 3
+#: en_US/module-struct.xml:256(para)
+msgid "To render the <abbrev>XML</abbrev> document into another format, use one of the following <command>make</command> targets:"
+msgstr "Para representar o documento em <abbrev>XML</abbrev> noutro formato, use um dos seguintes alvos do <command>make</command>:"
+d7324 1
+a7324 1
+#: en_US/module-struct.xml:261(title)
+d7328 1
+a7328 1
+#: en_US/module-struct.xml:262(segtitle)
+d7332 1
+a7332 1
+#: en_US/module-struct.xml:265(systemitem)
+d7336 2
+a7337 1
+#: en_US/module-struct.xml:266(abbrev) en_US/module-struct.xml:277(abbrev) en_US/module-struct.xml:302(abbrev) en_US/module-struct.xml:307(abbrev)
+d7341 2
+a7342 1
+#: en_US/module-struct.xml:270(systemitem) en_US/module-struct.xml:280(systemitem)
+d7346 2
+a7347 1
+#: en_US/module-struct.xml:271(systemitem) en_US/module-struct.xml:281(systemitem)
+d7351 1
+a7351 1
+#: en_US/module-struct.xml:269(filename)
+d7355 11
+a7365 3
+#: en_US/module-struct.xml:266(seg)
+msgid "This target builds the \"chunked\" <placeholder-1/> document for each defined translation. Output is placed in a separate directory named <placeholder-2/>. Each document section is a separate file within that directory."
+msgstr "Este alvo compila o documento <placeholder-1/> \"em blocos\" para cada tradução definida. O resultado é colocado numa pasta separada, chamada <placeholder-2/>. Cada secção do documento fica num ficheiro separado, dentro dessa pasta."
+d7367 1
+a7367 1
+#: en_US/module-struct.xml:276(systemitem)
+d7371 1
+a7371 1
+#: en_US/module-struct.xml:279(filename)
+d7375 9
+a7383 3
+#: en_US/module-struct.xml:277(seg)
+msgid "This target builds the \"non-chunked\" <placeholder-1/> document for each defined translation. Output is placed in a single file: <placeholder-2/>; no other files are created."
+msgstr "Este alvo gera o documento <placeholder-1/> \"inteiro\" para cada tradução definida. O resultado é colocado num único ficheiro: <placeholder-2/>; não são criados outros ficheiros."
+d7385 1
+a7385 1
+#: en_US/module-struct.xml:285(systemitem)
+d7389 2
+a7390 1
+#: en_US/module-struct.xml:286(abbrev) en_US/module-struct.xml:287(abbrev) en_US/module-struct.xml:303(abbrev) en_US/module-struct.xml:308(abbrev)
+d7394 9
+a7402 3
+#: en_US/module-struct.xml:286(seg)
+msgid "This target builds only the <placeholder-1/> document for all document languages. <placeholder-2/> production is currently erratic and may not work for your document."
+msgstr "Este alvo constrói apenas o documento <placeholder-1/> para todas as línguas do documento. A produção em <placeholder-2/> tem alguns problemas e poderá não funcionar para o seu documento."
+d7404 1
+a7404 1
+#: en_US/module-struct.xml:291(systemitem)
+d7408 1
+a7408 1
+#: en_US/module-struct.xml:292(command)
+d7412 7
+a7418 3
+#: en_US/module-struct.xml:292(seg)
+msgid "This target builds only the <placeholder-1/> archive for all document languages."
+msgstr "Este alvo constrói apenas o pacote <placeholder-1/> para todas as línguas do documento."
+d7420 1
+a7420 1
+#: en_US/module-struct.xml:296(systemitem)
+d7424 1
+a7424 1
+#: en_US/module-struct.xml:297(seg)
+d7428 2
+a7429 1
+#: en_US/module-struct.xml:300(systemitem) en_US/module-struct.xml:309(filename)
+d7433 1
+a7433 1
+#: en_US/module-struct.xml:302(emphasis)
+d7437 7
+a7443 3
+#: en_US/module-struct.xml:301(seg)
+msgid "This target deletes any temporary, or generated files, but does <placeholder-1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr "Este alvo apaga todos os ficheiros temporários ou gerados, mas <placeholder-1/> apaga os ficheiros <placeholder-2/>, <placeholder-3/> ou pacotes."
+d7445 1
+a7445 1
+#: en_US/module-struct.xml:306(systemitem)
+d7449 7
+a7455 3
+#: en_US/module-struct.xml:307(seg)
+msgid "This target erases all <placeholder-1/>, <placeholder-2/>, and archive files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr "Este alvo apaga todos os ficheiros <placeholder-1/>, <placeholder-2/> e de pacotes. Este alvo também invoca automaticamente o alvo <placeholder-3/>."
+d7457 1
+a7457 1
+#: en_US/module-struct.xml:314(title)
+d7461 22
+a7482 7
+#: en_US/module-struct.xml:315(para)
+msgid "To add a new target and rules, place them at the bottom of the document <filename>Makefile</filename>, below the <literal>include</literal> line. Follow your target definitions with a double colon, not a single colon. The double colon allows you to specify additional rules for existing targets, or to write rules for a new target."
+msgstr "Para adicionar um novo alvo e regras, coloque-as no fundo da <filename>Makefile</filename> do documento, por baixo da linha <literal>include</literal>. Siga as definições do seu alvo com dois-pontos duplos, não apenas um. Os dois-pontos duplos permitem-lhe definir regras adicionais para os alvos existentes ou escrever regras para um novo alvo."
+
+#: en_US/module-struct.xml:323(para)
+msgid "For more information on using <command>make(1)</command>, consult the online documentation with the command <command>info make</command> in a terminal."
+msgstr "Para mais informações sobre a utilização do <command>make(1)</command>, consulte a documentação 'online' com o comando <command>info make</command> num terminal."
+d7484 1
+a7484 1
+#: en_US/module-struct.xml:330(title)
+d7488 85
+a7572 23
+#: en_US/module-struct.xml:331(para)
+msgid "Tutorial documents often make use of images such as <filename class=\"extension\">.PNG</filename> files. Store image files in a <filename class=\"directory\">figs/</filename> folder in the main module directory, as shown in <xref linkend=\"ex-module-structure\"/>."
+msgstr "Os documentos de tutoriais normalmente utilizam imagens como os ficheiros <filename class=\"extension\">.PNG</filename>. Guarde os ficheiros de imagens numa pasta <filename class=\"directory\">figs/</filename> da pasta do módulo principal, como aparece em <xref linkend=\"ex-module-structure\"/>."
+
+#: en_US/module-struct.xml:338(para)
+msgid "Depending on the output media, sometimes images may be scaled, streteched, or squashed. To minimize any distortions, we recommend that you use only <filename class=\"extension\">.PNG</filename> images. Avoid <filename class=\"extension\">.JPG</filename> files. The <command>convert(1)</command> program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</abbrev> package, provides a convenient way to reformat <filename class=\"extension\">.JPG</filename> images into <filename class=\"extension\">.PNG</filename> format. For more information on formatting images such as screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr "Dependendo do formato de saída, algumas das imagens poderão ser esticadas, encolhidas ou desfeitas. Para minimizar as distorções, recomenda-se que use apenas as imagens <filename class=\"extension\">.PNG</filename>. Evite os ficheiros <filename class=\"extension\">.JPG</filename>. O programa <command>convert(1)</command>, do pacote <abbrev>RPM</abbrev> <package role=\"rpm\">ImageMagick</package>, oferece uma forma conveniente de formatar de novo as <filename class=\"extension\">.JPG</filename> no formato <filename class=\"extension\">.PNG</filename>. Para mais informações sobre a formatação das imagens, veja em <xref linkend=\"sn-screenshots\"/>."
+
+#: en_US/module-struct.xml:352(para)
+msgid "Image files may be organized into subdirectories under <filename>figs/</filename> if necessary. The document building system recreates the image subdirectory structure in the output documents."
+msgstr "Os ficheiros de imagens poderão estar organizados em sub-pastas da <filename>figs/</filename>, se necessário. O sistema de compilação de documentos irá criar de novo a estrutura de sub-pastas das imagens nos documentos resultantes."
+
+#: en_US/module-struct.xml:358(para)
+msgid "Images often contain labels or other text which may need to be localized. A screenshot of a program, for example, may require a version for each translated language. Name language-dependent image files such as program screenshots by adding the language code to the filename, such as <filename>menu-en_US.png</filename>. Language-independent images, such as <filename>icon.png</filename>, do not need language codes."
+msgstr "As imagens contêm normalmente legendas ou outros textos que possam ter de ser traduzidos. Uma imagem de um programa, por exemplo, poderá necessitar de uma versão para cada língua traduzida. Dê um nome dependente da língua aos ficheiros de imagens, adicionando o código da língua ao nome do ficheiro, como acontece em <filename>menu-pt.png</filename>. As imagens independentes da língua, como o <filename>icon.png</filename>, não precisam de códigos de línguas."
+
+#: en_US/module-struct.xml:368(para)
+msgid "Sometimes, a document may require images that do not follow the naming convention. To use these images with the document building system, create an ordinary text file containing the image filenames. This file must be named <filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</systemitem> so the build system finds it when searching for image filenames."
+msgstr "Em alguns casos, um documento poderá necessitar de imagens que não sigam a nomenclatura. Para usar estas imagens com o sistema de compilação do documento, crie um ficheiro de texto normal que contém os nomes dos ficheiros de imagens. Este ficheiro dever-se-á chamar <filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</systemitem>, de modo que o sistema de compilação o descubra quando procurar pelos nomes dos ficheiros de imagens."
+
+#: en_US/module-struct.xml:377(para)
+msgid "<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one way to create this <filename>Manifest</filename> file."
+msgstr "O <xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstra uma forma de criar este ficheiro <filename>Manifest</filename>."
+d7574 1
+a7574 1
+#: en_US/module-struct.xml:383(title)
+d7578 1
+a7578 1
+#: en_US/module-struct.xml:390(title)
+d7582 6
+a7587 3
+#: en_US/module-struct.xml:391(para)
+msgid "To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr "Para adicionar um novo ficheiro de DocBook em XML a um documento existente, siga estes passos:"
+d7589 1
+a7589 1
+#: en_US/module-struct.xml:395(para)
+d7593 13
+a7605 3
+#: en_US/module-struct.xml:399(para)
+msgid "Edit the <filename>Makefile</filename> and add the filename to the <varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to the last existing line, and on the next line add an entry for the new file. Remember to add the <literal>${1}/</literal> prefix as a substitute for the language directory name."
+msgstr "Edite a <filename>Makefile</filename> e adicione o nome do ficheiro à listagem <varname>XMLFILES-${1}</varname>. Adicione uma <keycap>\\</keycap> à última linha existente e, na linha seguinte, adicione um item para o novo ficheiro. Lembre-se de adicionar o prefixo <literal>${1}/</literal> como substituto para o nome da pasta da língua."
+d7607 1
+a7607 1
+#: en_US/module-struct.xml:409(title)
+d7611 20
+a7630 7
+#: en_US/module-struct.xml:410(para)
+msgid "Translations are stored as PO (portable object) files, which the toolchain transforms into translated documents. Each PO file is based on the POT (PO template) for the document and translated by the Fedora Translation Project. To add a translation, follow these steps:"
+msgstr "As traduções são guardadas como ficheiros PO (portable object - objecto portável), que o conjunto de ferramentas irá transformar em documentos traduzidos. Cada um dos ficheiros PO baseia-se no POT (modelo de PO) do documento e é traduzido pelo Projecto de Traduções do Fedora. Para adicionar uma tradução, siga estes passos:"
+
+#: en_US/module-struct.xml:417(para)
+msgid "If the <filename class=\"directory\">po/</filename> directory does not exist, create it and add it to CVS:"
+msgstr "Se a pasta <filename class=\"directory\">po/</filename> não existir, crie-a e adicione-a ao CVS:"
+d7632 1
+a7632 1
+#: en_US/module-struct.xml:423(para)
+d7636 15
+a7650 7
+#: en_US/module-struct.xml:427(para)
+msgid "Add the new translation language to the <varname>OTHERS</varname> listing in the <filename>Makefile</filename>."
+msgstr "Adicione a nova língua da tradução à listagem do <varname>OTHERS</varname> na <filename>Makefile</filename>."
+
+#: en_US/module-struct.xml:432(para)
+msgid "Although translators often copy the POT manually to create the new PO file, the following command also works:"
+msgstr "Ainda que os tradutores copiem normalmente de forma manual o ficheiro POT para criar o novo ficheiro PO, o seguinte comando também funciona:"
+d7652 1
+a7652 1
+#: en_US/module-struct.xml:435(replaceable)
+d7656 1
+a7656 1
+#: en_US/module-struct.xml:435(screen)
+d7661 1
+a7661 1
+#: en_US/intro.xml:13(title)
+d7665 16
+a7680 3
+#: en_US/intro.xml:15(para)
+msgid "The goal of the Fedora Documentation Project is to create easy-to-follow, task-based documentation for Fedora users and developers. Other than the <citetitle>Installation Guide</citetitle>, each tutorial should be in DocBook XML article format, with one article per topic. This way, writers can contribute documentation about a specific topic without having to worry about how it fits into a manual or how it flows with other topics."
+msgstr "O objectivo do Projecto de Documentação do Fedora é criar documentação simples e baseada em tarefas para os utilizadores e programadores do Fedora. Exceptuando o <citetitle>Guia de Instalação</citetitle>, cada tutorial deverá estar no formato de artigos do DocBook em XML, tendo cada um dos artigos por tópico. Desta forma, os escritores poderão contribuir com documentação acerca de um tópico específico, sem terem de se preocupar com a sua adaptação a um manual ou como este se coaduna com outros tópicos."
+d7682 1
+a7682 1
+#: en_US/intro.xml:25(para)
+d7686 1
+a7686 1
+#: en_US/intro.xml:31(para)
+d7690 1
+a7690 1
+#: en_US/intro.xml:34(para)
+d7692 2
+a7693 1
+msgstr "Folhas de estilo XSLT personalizadas para as versões impressas e em HTML"
+d7695 1
+a7695 1
+#: en_US/intro.xml:38(para)
+d7697 3
+a7699 1
+msgstr "Programas personalizados para gerar o resultado em HTML (use o <command>xmlto</command>)"
+d7701 1
+a7701 1
+#: en_US/intro.xml:42(para)
+d7705 9
+a7713 3
+#: en_US/intro.xml:51(para)
+msgid "This document explains the tools used by the Fedora Documentation Project and provides writing and tagging guidelines to make Fedora documentation is consistent and easy-to-follow."
+msgstr "Este documento explica as ferramentas usadas pelo Projecto de Documentação do Fedora e oferece algumas recomendações de escrita e marcação que tornam a documentação do Fedora consistente e fácil de seguir."
+d7715 1
+a7715 1
+#: en_US/getting-files.xml:12(title)
+d7719 8
+a7726 3
+#: en_US/getting-files.xml:14(para)
+msgid "To work on official Fedora documentation you need to install the required tools. Follow the directions below to configure your system."
+msgstr "Para lidar com a documentação oficial do Fedora, terá de instalar as seguintes ferramentas. Siga as instruções abaixo para configurar o seu sistema."
+d7728 1
+a7728 1
+#: en_US/getting-files.xml:20(title)
+d7732 8
+a7739 3
+#: en_US/getting-files.xml:22(para)
+msgid "Install the \"Authoring and Publishing\" package group, which contains required DocBook XML files, stylesheets and scripts:"
+msgstr "Instale o grupo de pacotes \"Authoring and Publishing\" (Autoria e Publicações), que contém os ficheiros de DocBook em XML necessários, as folhas de estilo e os programas:"
+d7741 1
+a7741 1
+#: en_US/getting-files.xml:28(userinput)
+d7746 7
+a7752 3
+#: en_US/getting-files.xml:31(para)
+msgid "Next, install the <filename>cvs</filename> package, which is used to handle revision control on files in the official repository:"
+msgstr "De seguida, instale o pacote <filename>cvs</filename>, que é usado para lidar com o controlo de versões nos ficheiros do repositório oficial:"
+d7754 1
+a7754 1
+#: en_US/getting-files.xml:37(userinput)
+d7759 1
+a7759 1
+#: en_US/getting-files.xml:43(title)
+d7763 11
+a7773 3
+#: en_US/getting-files.xml:45(para)
+msgid "The Fedora Documentation Project's custom scripts and stylesheets are stored in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</systemitem> CVS server. Check them out along with the DocBook XML files for the existing docs."
+msgstr "Os programas e folhas de estilo personalizados do Projecto de Documentação do Fedora estão guardados em CVS, no servidor <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</systemitem>. Obtenha-os em conjunto com os ficheiros de DocBook em XML, no que respeita à documentação existente."
+d7775 2
+a7776 1
+#: en_US/getting-files.xml:53(replaceable) en_US/getting-files.xml:54(replaceable)
+d7780 1
+a7780 1
+#: en_US/getting-files.xml:55(replaceable)
+d7784 1
+a7784 1
+#: en_US/getting-files.xml:53(userinput)
+d7786 6
+a7791 1
+msgid "mkdir <placeholder-1/>\ncd <placeholder-2/>\nexport CVSROOT=:ext:<placeholder-3/>@@cvs.fedora.redhat.com:/cvs/docs\ncvs login\ncvs co docs-common"
+d7799 1
+a7799 1
+#: en_US/getting-files.xml:60(para)
+d7801 2
+a7802 1
+msgstr "Na linha de comandos da senha, carregue na tecla <keycap>Enter</keycap>."
+d7804 1
+a7804 1
+#: en_US/getting-files.xml:65(title)
+d7808 16
+a7823 7
+#: en_US/getting-files.xml:66(para)
+msgid "You need to perform this \"checkout\" step only once, although you may need to update the files later. These files are common to all the official documentation."
+msgstr "Só precisa de efectuar este passo de \"extracção\" uma vez, ainda que precise de actualizar os ficheiros mais tarde. Estes ficheiros são comuns a toda a documentação oficial."
+
+#: en_US/getting-files.xml:73(para)
+msgid "To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr "Para trabalhar com os documentos existentes no CVS, consulte a secção <xref linkend=\"ch-cvs\"/>."
+d7825 1
+a7825 1
+#: en_US/getting-files.xml:80(title)
+d7829 14
+a7842 3
+#: en_US/getting-files.xml:81(para)
+msgid "The Fedora Documentation Project provides the tools, scripts, and stylesheets to transform your <abbrev>XML</abbrev> documents into other output formats such as <abbrev>HTML</abbrev>. In addition, these tools can build your document into a <abbrev>RPM</abbrev> package. To take advantage of these services, you must follow conventions for naming your files."
+msgstr "O Projecto de Documentação do Fedora oferece as ferramentas, programas e folhas de estilo que transformam os seus documentos em <abbrev>XML</abbrev> noutros formatos resultantes, como o <abbrev>HTML</abbrev>. Para além disso, estas ferramentas podem transformar o seu documento num pacote <abbrev>RPM</abbrev>. Para tirar partido destes serviços, deverá seguir as convenções de nomenclatura dos seus ficheiros."
+d7844 1
+a7844 1
+#: en_US/getting-files.xml:89(title)
+d7848 11
+a7858 3
+#: en_US/getting-files.xml:90(para)
+msgid "Each document lives in a peer directory to the <filename>docs-common</filename> directory you extracted from the Fedora archive earlier. On the CVS server, these directories are called <firstterm>modules</firstterm>. Use the <command>cvs co -c</command> command to view existing module names."
+msgstr "Cada documento reside numa pasta acompanhante da <filename>docs-common</filename> que extraiu anteriormente do pacote do Fedora. No servidor de CVS, estas pastas chamam-se <firstterm>módulos</firstterm>. Use o comando <command>cvs co -c</command> para ver os nomes dos módulos existentes."
+d7860 1
+a7860 1
+#: en_US/getting-files.xml:98(title)
+d7864 1
+a7864 1
+#: en_US/getting-files.xml:99(userinput)
+d7869 1
+a7869 1
+#: en_US/getting-files.xml:100(computeroutput)
+d7871 9
+a7879 1
+msgid "build-docs infrastructure/build-docs\ncvsroot CVSROOT\ndesktop-up2date desktop-up2date\ndeveloper-guide developer-guide\ndocs .\ndocs-common docs-common\ndocumentation-guide documentation-guide\nexample-tutorial example-tutorial"
+d7890 7
+a7896 3
+#: en_US/getting-files.xml:109(para)
+msgid "Choose a module name that accurately reflects your document's subject, but avoid any name already taken."
+msgstr "Escolha um nome de módulo que reflicta com precisão o assunto do seu documento, evitando qualquer nome que já tenha sido usado."
+d7898 1
+a7898 1
+#: en_US/getting-files.xml:112(title)
+d7902 7
+a7908 3
+#: en_US/getting-files.xml:113(para)
+msgid "Do not use the word <wordasword>Fedora</wordasword> to name modules in the Fedora Documentation Project CVS repository."
+msgstr "Não use a palavra <wordasword>Fedora</wordasword> no nome dos módulos do repositório de CVS do Projecto de Documentação do Fedora."
+d7910 1
+a7910 1
+#: en_US/emacs.xml:13(title)
+d7914 1
+a7914 1
+#: en_US/emacs.xml:16(primary)
+d7918 5
+a7922 1
+#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary) en_US/emacs.xml:43(primary) en_US/emacs.xml:232(primary) en_US/emacs.xml:241(primary) en_US/emacs.xml:246(primary) en_US/emacs.xml:251(primary) en_US/emacs.xml:526(application) en_US/emacs-nxml.xml:18(primary) en_US/emacs-nxml.xml:22(primary)
+d7926 1
+a7926 1
+#: en_US/emacs.xml:25(secondary)
+d7930 9
+a7938 3
+#: en_US/emacs.xml:28(para)
+msgid "You can use the PSGML mode available for Emacs to make it easier to write in XML format. PSGML mode provides syntax-highlighting, tag completion, and more."
+msgstr "Poderá usar o modo PSGML, que está disponível para o Emacs, de modo a ser mais fácil de escrever no formato XML. O modo PSGML oferece o realce de sintaxe, a completação de marcas, etc."
+d7940 1
+a7940 1
+#: en_US/emacs.xml:35(title)
+d7944 1
+a7944 1
+#: en_US/emacs.xml:36(para)
+d7948 1
+a7948 1
+#: en_US/emacs.xml:37(userinput)
+d7953 1
+a7953 1
+#: en_US/emacs.xml:40(title)
+d7957 1
+a7957 1
+#: en_US/emacs.xml:48(filename)
+d7961 131
+a8091 2
+#: en_US/emacs.xml:51(para)
+msgid "For Emacs to parse your DocBook documents correctly, you must have a <filename>.emacs</filename> file. Cut and paste the following into your existing <filename>.emacs</filename> file or create a new one that contains the following lines: <screen><computeroutput><![CDATA[\n;; turn on auto-fill in `text-mode' and derived modes \n;;(mail, news, etc)\n(add-hook 'text-mode-hook 'turn-on-auto-fill)\n\n;;\n;;MODES\n;;\n\n(setq auto-mode-alist (cons '(\"\\\\.sgml$\" . sgml-mode) auto-mode-alist))\n(setq auto-mode-alist (cons '(\"\\\\.sgm$\" . sgml-mode) auto-mode-alist))\n\n;;\n;;XML!!\n;;\n;;#############################################################\n\n;;\n;;PSGML mode stuff\n;;\n\n(autoload 'sgml-mode \"psgml\" \"My Most Major Mode\" t)\n\n(setq sgml-mode-hook '(lambda () \"Defaults for XML mode.\" (turn-on-auto-fill) \n(setq fill-column 80)))\n\n(defun My-XML-keymap ()\n (local-set-key [(alt i)] \n '(lambda ()\n (interactive)\n
(sgml-indent-line)\n (sgml-insert-element 'item)\n (sgml-indent-line)))\n (local-set-key [(alt l)] \n '(lambda ()\n (interactive)\n (sgml-insert-element 'list)\n (sgml-insert-element 'item)\n (sgml-indent-line)))\n (local-set-key [(alt p)]\n '(lambda ()\n (interactive)\n (sgml-indent-line)\n (sgml-insert-element 'para)\n (sgml-indent-line)))\n (local-set-key [(alt -)]\n '(lambda ()\n (interactive)\n (insert \"—\")))) \n\n(add-hook 'sgml-mode-hook 'My-XML-keymap)\n\n;;\n;; Fix up indentation of data...\n;;\n\n(setq-default sgml-indent-data t)\n\n;;\n;; XML markup faces.\n;;\n\n(setq-default sgml-set-face t)\n\n\n(make-face 'sgml-comment-face)\n(make-face 'sgml-doctype-face)\n(ma
ke-face 'sgml-end-tag-face)\n(make-face 'sgml-entity-face)\n(make-face 'sgml-ignored-face)\n(make-face 'sgml-ms-end-face)\n(make-face 'sgml-ms-start-face)\n(make-face 'sgml-pi-face)\n(make-face 'sgml-sgml-face)\n(make-face 'sgml-short-ref-face)\n(make-face 'sgml-start-tag-face)\n\n(set-face-foreground 'sgml-comment-face \"maroon\")\n(set-face-foreground 'sgml-doctype-face \"dark green\")\n(set-face-foreground 'sgml-end-tag-face \"blue2\")\n(set-face-foreground 'sgml-entity-face \"red2\")\n(set-face-foreground 'sgml-ignored-face \"maroon\")\n(set-face-background 'sgml-ignored-face \"gray90\")\n(set-face-foreground 'sgml-ms-end-face \"maroon\")\n(set-face-foreground 'sgml-ms-start-face \"maroon\")\n(set-face-foreground 'sgml-pi-face \"maroon\")\n(set-face-foreground 'sgml-sgml-face \"maroon\")\n(set-face-foreground 'sgml-short-ref-face \"goldenrod\")\n(set-face-foreground 'sgml-start-tag-face \"blue2\")\n\n(setq-default sgml-markup-faces\n '((comment . sgml-commen
t-face)\n (doctype . sgml-doctype-face)\n (end-tag . sgml-end-tag-face)\n (entity . sgml-entity-face)\n (ignored . sgml-ignored-face)\n (ms-end . sgml-ms-end-face)\n (ms-start . sgml-ms-start-face)\n (pi . sgml-pi-face)\n (sgml . sgml-sgml-face)\n (short-ref . sgml-short-ref-face)\n (start-tag . sgml-start-tag-face)))\n\n\n(defun docbook-mode ()\n (sgml-mode)\n )\n\n\n\n;;\n;;END XML STUFF\n;;\n;;##################################################################\n\n;PO mode stuff\n\n(setq auto-mode-alist\n\t(cons '(\"\\\\.pox?\\\\'\" . po-mode) auto-mode-alist))\n(autoload 'po-mode \"po-mode\")\n\n\n (global-set-key [(f1)] (lambda () (interactive) (manual-\n entry (current-word))))\n]]></computeroutput></screen>"
+d8093 4
+a8096 1
+"Para o Emacs processar correctamente os seus documentos em DocBook, terá de criar um ficheiro <filename>.emacs</filename>. Corte e cole o seguinte texto no seu ficheiro <filename>.emacs</filename> existente ou crie um novo que contenha as seguintes linhas:<screen><computeroutput><![CDATA[\n"
+d8119 2
+a8120 1
+"(setq sgml-mode-hook '(lambda () \"Predefinições do modo XML.\" (turn-on-auto-fill) \n"
+d8223 17
+a8239 7
+#: en_US/emacs.xml:185(para)
+msgid "If you have a wheel mouse and are using Emacs version 21, you can add the following to your <filename>.emacs</filename> file so your wheel will work in <application>Emacs</application>:"
+msgstr "Se tiver um rato com roda e estiver a usar o Emacs versão 21, poderá adicionar o seguinte ao seu ficheiro <filename>.emacs</filename>, para que a roda do seu rato funcione no <application>Emacs</application>:"
+
+#: en_US/emacs.xml:198(para)
+msgid "If you are using the older version 20 of <application>Emacs</application>, add the following instead:"
+msgstr "Se estiver a usar a versão anterior - a 20 - do <application>Emacs</application>, adicione o seguinte comando:"
+d8241 1
+a8241 1
+#: en_US/emacs.xml:229(title)
+d8245 1
+a8245 1
+#: en_US/emacs.xml:233(secondary)
+d8249 1
+a8249 1
+#: en_US/emacs.xml:237(filename)
+d8253 1
+a8253 1
+#: en_US/emacs.xml:242(secondary)
+d8257 1
+a8257 1
+#: en_US/emacs.xml:247(secondary)
+d8261 1
+a8261 1
+#: en_US/emacs.xml:252(secondary)
+d8265 9
+a8273 3
+#: en_US/emacs.xml:255(para)
+msgid "The colors, font, and geometry (default size of window) for Emacs in your <filename>~/.Xresources</filename> file. The format for the settings is <computeroutput>emacs.keyword:value</computeroutput>"
+msgstr "As cores, tipos de letra e geometria (tamanho predefinido da janela) do Emacs no seu ficheiro <filename>~/.Xresources</filename>. O formato da configuração é <computeroutput>emacs.palavra-chave:valor</computeroutput>"
+d8275 1
+a8275 1
+#: en_US/emacs.xml:261(para)
+d8279 7
+a8285 3
+#: en_US/emacs.xml:266(para)
+msgid "If you have other settings in your <filename>~/.Xresources</filename>, add the following to the end of the file."
+msgstr "Se tiver outras configurações no seu ficheiro <filename>~/.Xresources</filename>, adicione o seguinte ao fim do ficheiro."
+d8287 1
+a8287 1
+#: en_US/emacs.xml:282(para)
+d8291 1
+a8291 1
+#: en_US/emacs.xml:286(command)
+d8295 6
+a8300 3
+#: en_US/emacs.xml:287(para)
+msgid "and restart <application>Emacs</application> for the changes to take place."
+msgstr "e reiniciar o <application>Emacs</application> para as alterações fazerem efeito."
+d8302 1
+a8302 1
+#: en_US/emacs.xml:295(title)
+d8306 32
+a8337 7
+#: en_US/emacs.xml:297(para)
+msgid "Emacs will perform syntax highlighting and indent correctly on DocBook XML files if you provide it with the proper Document Type Declarations (DTD) file. These two features will make your XML file look pretty and help you spot errors."
+msgstr "O Emacs irá efectuar o realce de sintaxe e a indentação correctamente para os ficheiros de DocBook em XML, se lhe fornecer o ficheiro de DTD (Declarações do Tipo de Documento) adequado. Estas duas funcionalidades farão com que o seu ficheiro XML fique bonito e você tenha alguma ajuda na descoberta de erros."
+
+#: en_US/emacs.xml:308(para)
+msgid "Find the parent file for the group of DocBook files. You will recognize this file by the header <filename><!DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook V4.1//EN\"</filename>. An easy way to find this parent file is to use the command <command>grep DocBook *.xml</command>. Once you find the parent file, open it in Emacs with the command <command>emacs <replaceable><parentfile></replaceable>.xml</command> (where <replaceable><parentfile></replaceable>.xml is the parent file you found."
+msgstr "Descubra o ficheiro-pai do grupo de ficheiros DocBook. Irá reconhecer este ficheiro pelo cabeçalho <filename><!DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook V4.1//EN\"</filename>. Uma forma simples de descobrir este ficheiro-pai é usar o comando <command>grep DocBook *.xml</command>. Logo que descubra o ficheiro-pai, abra-o no Emacs com o comando <command>emacs <replaceable><ficheiro-pai></replaceable>.xml</command> (onde o <replaceable><ficheiro-pai></replaceable>.xml é o ficheiro que descobriu."
+d8339 1
+a8339 1
+#: en_US/emacs.xml:321(para)
+d8341 3
+a8343 1
+msgstr "Escolha a opção <command>DTD -> Parse DTD</command> (Processar a DTD) do menu respectivo."
+d8345 27
+a8371 3
+#: en_US/emacs.xml:327(para)
+msgid "You will know the parsing is finished when you see the message <computeroutput>Fontifying...done</computeroutput> at the bottom of your screen. Save the parsed DTD to a file by choosing <command>DTD -> Save Parsed DTD</command> from the pulldown menu."
+msgstr "Irá concluir se o processamento terminou quando lhe aparecer a mensagem <computeroutput>Fontifying...done</computeroutput> (A formatar... pronto) no fundo do seu ecrã. Grave a DTD processada num ficheiro com a opção <command>DTD -> Save Parsed DTD</command> (DTD - Gravar a DTD Processada) no menu."
+d8373 1
+a8373 5
+#: en_US/emacs.xml:335(para)
+msgid "Press <keycap>Enter</keycap> to save the file to the default filename or rename the file keeping the <filename>.ced</filename> extension. It can be useful to name it something generic such as <filename>docbook.ced</filename> so you can refer to it when opening all DocBook files. This file can also be copied from directory to directory to be loaded."
+msgstr "Carregue em <keycap>Enter</keycap> para gravar o ficheiro com o nome predefinido, ou mude o nome do ficheiro, mantendo a extensão <filename>.ced</filename>. Poderá ser útil atribuir-lhe um nome genérico, do tipo <filename>docbook.ced</filename>, para que o possa consultar quando abrir todos os ficheiros DocBook. Este ficheiro também poderá ser copiado de uma pasta para a pasta onde será carregado."
+
+#: en_US/emacs.xml:304(para)
+d8375 3
+a8377 1
+msgstr "Para criar o ficheiro de uma DTD processada e com possibilidade de carregamento: <placeholder-1/>"
+d8379 11
+a8389 3
+#: en_US/emacs.xml:349(para)
+msgid "You can also use the Emacs command <command>Meta-x sgml-parse-prolog</command> to parse the file, and then use the command <command>Meta-x sgml-save-dtd</command> to save the parsed DTD to a <filename>.ced</filename> file."
+msgstr "Poderá também usar o comando do Emacs <command>Meta-x sgml-parse-prolog</command> para processar o ficheiro, usando depois o comando <command>Meta-x sgml-save-dtd</command> para gravar a DTD processada num ficheiro <filename>.ced</filename>."
+d8391 1
+a8391 1
+#: en_US/emacs.xml:360(title)
+d8395 9
+a8403 3
+#: en_US/emacs.xml:362(para)
+msgid "Now that you have saved the DTD settings, you can load the <filename>.ced</filename> file and see the syntax highlighting for your <filename>.sgml</filename> files."
+msgstr "Agora que gravou a configuração da DTD, poderá carregar o ficheiro <filename>.ced</filename> e ver o realce de sintaxe dos seus ficheiros <filename>.sgml</filename>."
+d8405 1
+a8405 1
+#: en_US/emacs.xml:372(para)
+d8409 21
+a8429 7
+#: en_US/emacs.xml:377(para)
+msgid "Choose <command>DTD -> Load DTD</command> from the pulldown menu and choose the file you saved from the previous step. For instance, choose <filename>docbook.ced</filename>."
+msgstr "Escolha a opção <command>DTD -> Load DTD</command> (DTD - Carregar a DTD) do menu que aparece e escolher o ficheiro que gravou no passo anterior. Por exemplo, escolha o <filename>docbook.ced</filename>."
+
+#: en_US/emacs.xml:384(para)
+msgid "You will know it is finished when you see the message <computeroutput>Fontifying...done</computeroutput> at the bottom of your screen. Loading the parsed DTD might take a long time. You can start editing the file before it finishes."
+msgstr "Irá saber quando terminou quando ver a mensagem <computeroutput>Fontifying...done</computeroutput> (A formatar... pronto) no fundo do seu ecrã. O carregamento da DTD processada poderá levar bastante tempo. Poderá começar a editar o ficheiro antes de este terminar."
+d8431 1
+a8431 1
+#: en_US/emacs.xml:368(para)
+d8435 7
+a8441 3
+#: en_US/emacs.xml:397(para)
+msgid "You can also use the Emacs command <command>Meta-x sgml-load-dtd</command> to load the parsed DTD."
+msgstr "Poderá também usar o comando do Emacs <command>Meta-x sgml-load-dtd</command> para carregar a DTD processada."
+d8443 1
+a8443 1
+#: en_US/emacs.xml:406(title)
+d8447 1
+a8447 1
+#: en_US/emacs.xml:408(para)
+d8449 2
+a8450 1
+msgstr "A tecla <keycap>Meta</keycap> normalmente é a tecla <keycap>Alt</keycap>."
+d8452 1
+a8452 1
+#: en_US/emacs.xml:413(title)
+d8456 1
+a8456 1
+#: en_US/emacs.xml:414(segtitle)
+d8460 4
+a8463 1
+#: en_US/emacs.xml:418(keycap) en_US/emacs.xml:423(keycap) en_US/emacs.xml:428(keycap) en_US/emacs.xml:496(keycap) en_US/emacs.xml:501(keycap) en_US/emacs.xml:506(keycap) en_US/emacs.xml:530(keycap)
+d8467 4
+a8470 1
+#: en_US/emacs.xml:418(keycap) en_US/emacs.xml:423(keycap) en_US/emacs.xml:428(keycap) en_US/emacs.xml:501(keycap) en_US/emacs.xml:506(keycap) en_US/emacs.xml:511(keycap) en_US/emacs.xml:517(keycap) en_US/emacs.xml:523(keycap)
+d8474 3
+a8476 1
+#: en_US/emacs.xml:419(keycap) en_US/emacs.xml:424(keycap) en_US/emacs.xml:429(keycap) en_US/emacs.xml:502(keycap) en_US/emacs.xml:507(keycap)
+d8480 7
+a8486 3
+#: en_US/emacs.xml:417(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, <placeholder-3/>"
+d8488 1
+a8488 1
+#: en_US/emacs.xml:420(seg)
+d8492 7
+a8498 3
+#: en_US/emacs.xml:423(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-save-dtd, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-save-dtd, <placeholder-3/>"
+d8500 1
+a8500 1
+#: en_US/emacs.xml:425(seg)
+d8504 7
+a8510 3
+#: en_US/emacs.xml:428(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-load-dtd, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-load-dtd, <placeholder-3/>"
+d8512 1
+a8512 1
+#: en_US/emacs.xml:430(seg)
+d8516 11
+a8526 1
+#: en_US/emacs.xml:433(keycap) en_US/emacs.xml:439(keycap) en_US/emacs.xml:446(keycap) en_US/emacs.xml:451(keycap) en_US/emacs.xml:456(keycap) en_US/emacs.xml:461(keycap) en_US/emacs.xml:466(keycap) en_US/emacs.xml:471(keycap) en_US/emacs.xml:476(keycap) en_US/emacs.xml:481(keycap) en_US/emacs.xml:486(keycap) en_US/emacs.xml:491(keycap) en_US/emacs.xml:511(keycap) en_US/emacs.xml:512(keycap) en_US/emacs.xml:517(keycap) en_US/emacs.xml:518(keycap) en_US/emacs.xml:523(keycap) en_US/emacs.xml:524(keycap) en_US/emacs.xml:535(keycap) en_US/emacs.xml:536(keycap) en_US/emacs.xml:543(keycap) en_US/emacs.xml:545(keycap)
+d8530 4
+a8533 1
+#: en_US/emacs.xml:433(keycap) en_US/emacs.xml:439(keycap) en_US/emacs.xml:451(keycap) en_US/emacs.xml:524(keycap) en_US/emacs.xml:535(keycap) en_US/emacs.xml:543(keycap) en_US/emacs.xml:545(keycap)
+d8537 1
+a8537 1
+#: en_US/emacs.xml:434(keycap) en_US/emacs.xml:440(keycap)
+d8541 1
+a8541 1
+#: en_US/emacs.xml:435(keycap) en_US/emacs.xml:442(keycap)
+d8545 7
+a8551 3
+#: en_US/emacs.xml:433(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><keycap/></keycombo>, <placeholder-4/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><keycap/></keycombo>, <placeholder-4/>"
+d8553 1
+a8553 1
+#: en_US/emacs.xml:436(seg)
+d8557 9
+a8565 3
+#: en_US/emacs.xml:439(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><keycap/></keycombo>, type beginning of tag, <placeholder-4/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><keycap/></keycombo>, type beginning of tag, <placeholder-4/>"
+d8567 1
+a8567 1
+#: en_US/emacs.xml:443(seg)
+d8571 1
+a8571 1
+#: en_US/emacs.xml:446(keycap)
+d8575 1
+a8575 1
+#: en_US/emacs.xml:448(seg)
+d8579 1
+a8579 1
+#: en_US/emacs.xml:452(keycap)
+d8583 1
+a8583 1
+#: en_US/emacs.xml:451(seg)
+d8585 2
+a8586 1
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+d8588 1
+a8588 1
+#: en_US/emacs.xml:453(seg)
+d8592 1
+a8592 1
+#: en_US/emacs.xml:456(keycap) en_US/emacs.xml:536(keycap)
+d8596 1
+a8596 1
+#: en_US/emacs.xml:458(seg)
+d8600 1
+a8600 1
+#: en_US/emacs.xml:461(keycap)
+d8604 1
+a8604 1
+#: en_US/emacs.xml:463(seg)
+d8608 1
+a8608 1
+#: en_US/emacs.xml:466(keycap)
+d8612 1
+a8612 1
+#: en_US/emacs.xml:468(seg)
+d8616 1
+a8616 1
+#: en_US/emacs.xml:471(keycap)
+d8620 1
+a8620 1
+#: en_US/emacs.xml:473(seg)
+d8624 1
+a8624 1
+#: en_US/emacs.xml:476(keycap)
+d8628 1
+a8628 1
+#: en_US/emacs.xml:478(seg)
+d8632 1
+a8632 1
+#: en_US/emacs.xml:481(keycap)
+d8636 1
+a8636 1
+#: en_US/emacs.xml:483(seg)
+d8640 1
+a8640 1
+#: en_US/emacs.xml:486(keycap) en_US/emacs.xml:518(keycap)
+d8644 1
+a8644 1
+#: en_US/emacs.xml:488(seg)
+d8648 1
+a8648 1
+#: en_US/emacs.xml:491(keycap)
+d8652 1
+a8652 1
+#: en_US/emacs.xml:493(seg)
+d8656 1
+a8656 1
+#: en_US/emacs.xml:496(keycap)
+d8660 1
+a8660 1
+#: en_US/emacs.xml:498(seg) en_US/emacs.xml:503(seg)
+d8664 15
+a8678 7
+#: en_US/emacs.xml:501(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, <placeholder-3/>"
+
+#: en_US/emacs.xml:506(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, <placeholder-3/>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, <placeholder-3/>"
+d8680 1
+a8680 1
+#: en_US/emacs.xml:508(seg)
+d8684 1
+a8684 1
+#: en_US/emacs.xml:512(keycap)
+d8688 8
+a8695 3
+#: en_US/emacs.xml:511(seg) en_US/emacs.xml:517(seg) en_US/emacs.xml:523(seg) en_US/emacs.xml:535(seg) en_US/emacs.xml:543(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <keycombo><placeholder-3/><placeholder-4/></keycombo>"
+d8697 1
+a8697 1
+#: en_US/emacs.xml:514(seg)
+d8701 1
+a8701 1
+#: en_US/emacs.xml:520(seg)
+d8705 1
+a8705 1
+#: en_US/emacs.xml:526(seg)
+d8709 1
+a8709 1
+#: en_US/emacs.xml:530(keycap)
+d8713 1
+a8713 1
+#: en_US/emacs.xml:532(seg)
+d8717 1
+a8717 1
+#: en_US/emacs.xml:539(computeroutput)
+d8722 7
+a8728 3
+#: en_US/emacs.xml:538(seg)
+msgid "Edit attributes for a tag (for example, you can edit the <placeholder-1/> attribute of the <placeholder-2/> tag)"
+msgstr "Edita os atributos de uma marca (por exemplo, poderá editar o atributo <placeholder-1/> da marca <placeholder-2/>)"
+d8730 1
+a8730 1
+#: en_US/emacs.xml:547(seg)
+d8734 1
+a8734 1
+#: en_US/emacs.xml:554(title) en_US/emacs-nxml.xml:77(title)
+d8738 8
+a8745 3
+#: en_US/emacs.xml:556(para)
+msgid "The table or reference card of Emacs and PSGML commands can be confusing for beginners. This section provides some examples of how to use them."
+msgstr "A tabela ou cartão de referência dos comandos do Emacs e do PSGML poderão ser confusos para os principiantes. Esta secção oferece alguns exemplos de utilização dos mesmos."
+d8747 1
+a8747 1
+#: en_US/emacs.xml:562(title)
+d8751 19
+a8769 7
+#: en_US/emacs.xml:566(para)
+msgid "This section assumes that you have already loaded the DTD file (<filename>.ced</filename>)."
+msgstr "Esta secção assume que você já carregou o ficheiro da DTD (<filename>.ced</filename>)."
+
+#: en_US/emacs.xml:571(para)
+msgid "Instead of typing a tag each time you need to use it, use the key combination <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. At the bottom of the <application>Emacs</application> window, you will see:"
+msgstr "Em vez de escrever uma marca sempre que necessitar de a usar, use a combinação de teclas <keycap>Ctrl</keycap>-<keycap>C</keycap>, seguida do <keycap><</keycap>. No fundo da janela do <application>Emacs</application>, irá ver:"
+d8771 1
+a8771 1
+#: en_US/emacs.xml:578(computeroutput)
+d8776 24
+a8799 7
+#: en_US/emacs.xml:581(para)
+msgid "To view a list of available tags, use either the <keycap>Tab</keycap> or <keycap>?</keycap>. Or, if you know the first few letters of a tag, you can enter them followed by <keycap>Tab</keycap> for a complete list of available tags beginning with those letters or for a tag completion."
+msgstr "Para ver uma lista com as marcas disponíveis, use as teclas <keycap>Tab</keycap> ou <keycap>?</keycap>. Por outro lado, se souber as primeiras letras de uma marca, podê-las-á introduzir e carregar de seguida em <keycap>Tab</keycap> para obter uma lista completa das marcas disponíveis que começam por essas letras ou para completar a marca."
+
+#: en_US/emacs.xml:589(para)
+msgid "Try the following: Type <keycap>Ctrl</keycap>-<keycap>c</keycap> followed by <keycap><</keycap>. Then enter the letter <keycap>k</keycap>, followed by <keycap>Tab</keycap>. You may have to use the <keycap>Tab</keycap> key several times to get a complete list."
+msgstr "Tente o seguinte: Escreva <keycap>Ctrl</keycap>-<keycap>C</keycap>, seguida de <keycap><</keycap>. Depois, escreva a letra <keycap>k</keycap>, seguida de <keycap>Tab</keycap>. Poderá ter de usar a tecla <keycap>Tab</keycap> várias vezes, para obter uma lista completa."
+d8801 1
+a8801 1
+#: en_US/emacs.xml:596(para)
+d8805 1
+a8805 1
+#: en_US/emacs.xml:601(computeroutput)
+d8807 8
+a8814 1
+msgid "\nClick mouse-2 on a completion to select it.\nIn this buffer, type RET to select the completion near point.\n\nPossible completions are:\n<keycap> <keycode>\n<keycombo> <keysym>\n"
+d8824 1
+a8824 1
+#: en_US/emacs.xml:613(title)
+d8828 11
+a8838 3
+#: en_US/emacs.xml:615(para)
+msgid "Once you have started the tag of choice, you must close it. The easiest way to close an open tag is to use the keycombo <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap>/</keycap>. This will close the closest open tag you have."
+msgstr "Logo que tenha iniciado a marca que escolheu, terá de a fechar. A forma mais simples de fechar uma marca é usar a combinação de teclas <keycap>Ctrl</keycap>-<keycap>C</keycap>, seguida de <keycap>/</keycap>. Esta irá fechar a marca aberta mais próxima que tiver."
+d8840 1
+a8840 1
+#: en_US/emacs.xml:625(title)
+d8844 69
+a8912 19
+#: en_US/emacs.xml:627(para)
+msgid "<guilabel>Working with one window</guilabel>: Sometimes in <application>Emacs</application> the window becomes split (with tags completions or other text in the bottom window). The easiest way to get it back so that only your XML and text appear on one screen is to use the keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap>, followed by <keycap>1</keycap>."
+msgstr "<guilabel>Funcionar com uma janela</guilabel>: Algumas vezes no <application>Emacs</application>, a janela vai ficando dividida (com as completações de marcas ou outro texto na janela inferior). A forma mais simples de voltar atrás, para que apenas o seu XML e o texto apareçam num ecrã, é usar a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>1</keycap>."
+
+#: en_US/emacs.xml:636(para)
+msgid "<guilabel>Saving your work</guilabel>: To save your work, use the following keycombo, <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</keycap>-<keycap>s</keycap>."
+msgstr "<guilabel>Gravar o seu trabalho</guilabel>: Para gravar o seu trabalho, use a seguinte combinação de teclas, <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>Ctrl</keycap>-<keycap>S</keycap>."
+
+#: en_US/emacs.xml:642(para)
+msgid "<guilabel>The \"clear/quit\" command</guilabel>: I have found on some occasions that I have gotten too far into the tag completion process and need to just exit back out to my text. The easiest way to do this is the keycombo <keycap>Ctrl</keycap>-<keycap>g</keycap>. This command quits what you have been doing within the file, without quitting the file itself."
+msgstr "<guilabel>O comando \"limpar/sair\"</guilabel>: Descobri em algumas ocasiões que fui demasiado longe no processo de completação de marcas e preciso de sair para voltar ao meu text. A forma mais simples de fazer isto é a combinação de teclas <keycap>Ctrl</keycap>-<keycap>G</keycap>. Este comando sai do que estiver a fazer com o ficheiro, sem sair do ficheiro em si."
+
+#: en_US/emacs.xml:651(para)
+msgid "<guilabel>Opening a new file</guilabel>: To open a new file, use the keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</keycap>-<keycap>f</keycap>. At the bottom of the emacs window, you will be able to enter in the file name (using <keycap>Tab</keycap> completion if needed) of the file you wish to open."
+msgstr "<guilabel>Abrir um novo ficheiro</guilabel>: Para abrir um novo ficheiro, use a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap>, seguida de <keycap>Ctrl</keycap>-<keycap>F</keycap>. No fundo da janela do Emacs, será capaz de indicar o nome do ficheiro (usando a completação do <keycap>Tab</keycap> se necessário) do ficheiro que deseja abrir."
+
+#: en_US/emacs.xml:660(para)
+msgid "<guilabel>Closing emacs</guilabel>: The easiest way to close <application>emacs</application> is to use the keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</keycap>-<keycap>c</keycap>. If you have not saved your work, it will prompt you to save the file, otherwise it will just quit the current emacs session you have been working with."
+msgstr "<guilabel>Fechar o emacs</guilabel>: A forma mais simples de fechar o <application>emacs</application> é usar a combinação de teclas <keycap>Ctrl</keycap>-<keycap>X</keycap> seguida de <keycap>Ctrl</keycap>-<keycap>C</keycap>. Se não tiver gravado o seu trabalho, será questionado para gravar o ficheiro; caso contrário, só irá sair da sessão actual do Emacs com que esteve a trabalhar."
+d8914 1
+a8914 1
+#: en_US/emacs.xml:673(title) en_US/emacs-nxml.xml:127(title)
+d8918 7
+a8924 3
+#: en_US/emacs.xml:675(para)
+msgid "Additional Emacs and PSGML references are available at the following locations:"
+msgstr "As referências adicionais ao Emacs e ao PSGML estão disponíveis nas seguintes localizações:"
+d8926 1
+a8926 1
+#: en_US/emacs.xml:682(ulink) en_US/emacs-nxml.xml:142(ulink)
+d8930 1
+a8930 1
+#: en_US/emacs.xml:683(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+d8934 31
+a8964 11
+#: en_US/emacs.xml:686(para) en_US/emacs-nxml.xml:147(para)
+msgid "Emacs reference card that comes with the <filename>emacs</filename> package. You can print it out as a reference. —<filename>/usr/share/emacs/<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr "Um cartão de referência do Emacs que vem com o pacote <filename>emacs</filename>. Poderá imprimi-lo como referência. —<filename>/usr/share/emacs/<replaceable><versão></replaceable>/etc/refcard.ps</filename>"
+
+#: en_US/emacs.xml:693(para)
+msgid "Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/usr/share/doc/psgml-<replaceable><version></replaceable>/psgml.ps</filename>."
+msgstr "Leia o <citetitle>Editing XML with Emacs and PSGML</citetitle> no ficheiro <filename>/usr/share/doc/psgml-<replaceable><versão></replaceable>/psgml.ps</filename>."
+
+#: en_US/emacs.xml:697(para)
+msgid "<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\">http://www.snee.com/bob/sgmlfree/psgmqref.html</ulink>—<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of Emacs commands for PSGML mode."
+msgstr "O <ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\">http://www.snee.com/bob/sgmlfree/psgmqref.html</ulink>—<citetitle>Emacs/PSGML Quick Reference</citetitle> é uma tabela de referência dos comandos do Emacs para o modo do PSGML."
+d8966 1
+a8966 1
+#: en_US/emacs.xml:705(ulink)
+d8970 1
+a8970 1
+#: en_US/emacs.xml:706(citetitle)
+d8974 1
+a8974 1
+#: en_US/emacs-nxml.xml:11(title)
+d8978 1
+a8978 1
+#: en_US/emacs-nxml.xml:14(primary) en_US/emacs-nxml.xml:51(primary)
+d8982 1
+a8982 1
+#: en_US/emacs-nxml.xml:23(secondary)
+d8986 13
+a8998 3
+#: en_US/emacs-nxml.xml:26(para)
+msgid "You can also use the nXML mode available for <application>Emacs</application> to make it even easier to write in DocBook XML format. nXML mode provides context-sensitive editing using completion, real time validity error checking, syntax highlighting and indentation. All you need to do is install an RPM!!"
+msgstr "Também poderá usar o modo nXML que está disponível para o <application>Emacs</application>, de modo a ser ainda mais simples escrever no formato DocBook em XML. O modo nXML oferece uma edição sensível ao contexto com a completação, validação dos erros em tempo-real, realce de sintaxe e indentação. Tudo o que necessita é instalar um RPM!!"
+d9000 1
+a9000 1
+#: en_US/emacs-nxml.xml:35(title)
+d9004 14
+a9017 3
+#: en_US/emacs-nxml.xml:36(para)
+msgid "Please be aware the nxml-mode for <application>Emacs</application> is quite new, so there are a few things that the advanced user might notice when using it with other documents types. If you keep an eye on the mailing-list, you can keep up to date with these, as well as ask questions. For more details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr "Tenha em atenção que o 'nxml-mode' do <application>Emacs</application> é relativamente novo, pelo que existem algumas coisas que o utilizador mais avançado poderá notar ao usá-lo com outros tipos de documentos. Se mantiver uma vista de olhos na lista de correio, poder-se-á manter actualizado com as mesmas, assim como poderá fazer perguntas. Para mais detalhes, veja a secção <xref linkend=\"sn-emacs-nxml-readme\"/>."
+d9019 1
+a9019 1
+#: en_US/emacs-nxml.xml:48(title)
+d9023 1
+a9023 1
+#: en_US/emacs-nxml.xml:52(secondary)
+d9027 1
+a9027 1
+#: en_US/emacs-nxml.xml:56(primary)
+d9031 90
+a9120 31
+#: en_US/emacs-nxml.xml:59(para)
+msgid "To use nXML mode with emacs, you will need to install the nXML RPM available from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www.thaiopensource.com/download/\">http://www.thaiopensource.com/download/</ulink>. The source requires a lot more work to setup, therefore we will only be concentrating on the RPM version."
+msgstr "Para usar o modo nXML com o emacs, terá de instalar o pacote RPM nXML na <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/\">página do Tim Waugh</ulink> ou o código-fonte de <ulink url=\"http://www.thaiopensource.com/download/\">http://www.thaiopensource.com/download/</ulink>. O código necessita de bastante mais trabalho de configuração; como tal, concentrar-nos-emos na versão em RPM."
+
+#: en_US/emacs-nxml.xml:69(para)
+msgid "Information on where to get the source is available in <xref linkend=\"sn-emacs-additional-resources\"/>."
+msgstr "As informações de disponibilização do código estão disponíveis em <xref linkend=\"sn-emacs-additional-resources\"/>."
+
+#: en_US/emacs-nxml.xml:79(para)
+msgid "Compared to PSGML mode there are only couple of commands that you need. This speeds up writing with <application>Emacs</application> considerably, which means you can concentrate more on the content of your article."
+msgstr "Em comparação com o modo PSGML, só existem alguns comandos que você necessita. Isto acelera a escrita no <application>Emacs</application> consideravelmente, o que significa que se poderá concentrar mais no conteúdo do seu artigo."
+
+#: en_US/emacs-nxml.xml:88(para)
+msgid "To create a tag, type <userinput><</userinput> and then type the keyword. To complete the keyword, press <command>Ctrl-Ret</command>, then add the last <userinput>></userinput>. To close a tag, type <userinput></</userinput>."
+msgstr "Para criar uma marca, escreva <userinput><</userinput> e escreva depois a palavra-chave. Para completar a mesma, carregue em <command>Ctrl-Ret</command>, adicionando depois a última <userinput>></userinput>. Para fechar uma marca, escreva <userinput></</userinput>."
+
+#: en_US/emacs-nxml.xml:97(para)
+msgid "When you open a document that doesn't have a DOCTYPE declaration at the top of the file, you will get this message and tag completion won't work because nXML will not know what format you are writing."
+msgstr "Quando abrir um documento que não tenha uma declaração DOCTYPE no topo do ficheiro, irá obter esta mensagem e a completação de marcas não irá funcionar, porque o nXML não irá saber em que formato está a escrever."
+
+#: en_US/emacs-nxml.xml:104(para)
+msgid "To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> and load <filename>docbook.rnc</filename>. <application>Emacs</application> will then prompt you to save it in the current working directory."
+msgstr "Para carregar o esquema, escreva <command>Ctrl-C</command> e <command>Ctrl-S</command>, indo depois à pasta <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</filename> e carregando o <filename>docbook.rnc</filename>. O <application>Emacs</application> perguntar-lhe-á então para gravar a pasta de trabalho actual."
+
+#: en_US/emacs-nxml.xml:115(para)
+msgid "The commands already discussed are the only differences between using <application>Emacs</application> with PSGML mode and <application>Emacs</application> with nXML mode. You will still need to use all the same commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr "Os comandos já discutidos são as únicas diferenças entre a utilização do <application>Emacs</application> com o modo PSGML e o <application>Emacs</application> com o modo nXML. Terá à mesma de usar todos os mesmos comandos que foram discutidos em <xref linkend=\"sn-emacs-basic-commands\"/>."
+
+#: en_US/emacs-nxml.xml:129(para)
+msgid "Additional Emacs and nXML references are available at the following locations:"
+msgstr "As referências adicionais do Emacs e do nXML estão disponíveis nos seguintes locais:"
+d9122 1
+a9122 1
+#: en_US/emacs-nxml.xml:136(ulink)
+d9126 1
+a9126 1
+#: en_US/emacs-nxml.xml:137(citetitle)
+d9130 1
+a9130 1
+#: en_US/emacs-nxml.xml:157(title)
+d9134 9
+a9142 3
+#: en_US/emacs-nxml.xml:161(para)
+msgid "This file can be found in the directory you extracted the source into, or in <filename>/usr/share/doc/nxml-mode-<replaceable><version></replaceable>/</filename> if you installed the RPM."
+msgstr "Este ficheiro poderá ser encontrado na pasta para onde extraiu o código ou em <filename>/usr/share/doc/nxml-mode-<replaceable><versão></replaceable>/</filename>, se instalou o RPM."
+d9144 1
+a9144 1
+#: en_US/emacs-nxml.xml:169(para)
+d9148 20
+a9167 7
+#: en_US/emacs-nxml.xml:171(para)
+msgid "This is a new major mode for GNU Emacs for editing XML documents. It supports editing well-formed XML documents and also provides schema-sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr "Este é um novo modo principal para o GNU Emacs editar documentos em XML. Este suporta a edição de documentos válidos em XML, oferecendo também a edição sensível ao esquema dos documentos em XML, usando a Sintaxe Compacta do RELAX NG."
+
+#: en_US/emacs-nxml.xml:177(para)
+msgid "To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs version 20 will not work properly, nor will XEmacs. To get started, do the following:"
+msgstr "Para usar isto, terá de ter o GNU Emacs versão 21.x, de preferência a 21.3. O GNU Emacs versão 20 não irá funcionar correctamente, assim como o XEmacs. Para começar, faça o seguinte:"
+d9169 1
+a9169 1
+#: en_US/emacs-nxml.xml:184(command)
+d9173 7
+a9179 3
+#: en_US/emacs-nxml.xml:187(para)
+msgid "This defines the necessary autoloads. Now, visit a file containing an XML document, and do the following:"
+msgstr "Isto define todos os carregamentos automáticos necessários. Depois, vá a um ficheiro que contenha um documento em XML, fazendo o seguinte:"
+d9181 1
+a9181 1
+#: en_US/emacs-nxml.xml:192(command)
+d9185 1
+a9185 1
+#: en_US/emacs-nxml.xml:195(para)
+d9189 1
+a9189 1
+#: en_US/emacs-nxml.xml:200(command)
+d9193 7
+a9199 3
+#: en_US/emacs-nxml.xml:203(para)
+msgid "For information on how to use nxml-mode. The beginnings of a manual are in nxml-mode.info. You can read this using:"
+msgstr "Para mais informações sobre a utilização do nxml-mode. As introduções do manual estão no ficheiro 'nxml-mode.info'. Podê-lo-á ler com:"
+d9201 1
+a9201 1
+#: en_US/emacs-nxml.xml:209(command)
+d9205 16
+a9220 7
+#: en_US/emacs-nxml.xml:212(para)
+msgid "It's also installed as an entry at the end of the top-level info directory. So you can read it with <command>C-h i</command> as usual."
+msgstr "Também está instalado como um elemento no fim da pasta de topo do 'info'. Como tal, poderá lê-la com o <command>C-H I</command>, como de costume."
+
+#: en_US/emacs-nxml.xml:217(para)
+msgid "You can use <filename>test.valid.xml</filename> and <filename>test.invalid.xml</filename> as examples of valid and invalid XML documents."
+msgstr "Poderá usar os ficheiros <filename>test.valid.xml</filename> e <filename>test.invalid.xml</filename> como exemplos de documentos em XML válidos e inválidos."
+d9222 1
+a9222 1
+#: en_US/emacs-nxml.xml:223(para)
+d9224 3
+a9226 1
+msgstr "Para que as coisas sejam carregadas automaticamente de cada vez que iniciar o Emacs, adicione:"
+d9228 1
+a9228 1
+#: en_US/emacs-nxml.xml:228(computeroutput)
+d9230 3
+a9232 1
+msgid " (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n "
+d9237 28
+a9264 7
+#: en_US/emacs-nxml.xml:232(para)
+msgid "to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-200YMMDD</computeroutput> is the directory containing the <filename>.elc</filename> files. Note that <filename>rng-auto.el</filename> does not load all of the nxml-mode code; it merely sets things up so that all the features of nxml-mode will be autoloaded properly. You should not try to autoload <filename>rng-auto.el</filename> itself."
+msgstr "ao seu ficheiro <filename>.emacs</filename>, onde o <computeroutput>~/nxml-mode-200AMMDD</computeroutput> é a pasta que contém os ficheiros <filename>.elc</filename>. Lembre-se que o <filename>rng-auto.el</filename> não carrega tudo do modo 'nxml-mode'; simplesmente configura as coisas, para que as funcionalidades do 'nxml-mode' sejam carregadas automaticamente. Não deverá tentar carregar automaticamente o <filename>rng-auto.el</filename> propriamente dito."
+
+#: en_US/emacs-nxml.xml:242(para)
+msgid "To use nxml-mode automatically for files with an extension of <filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> or <filename>xhtml</filename>, add the following to your <filename>.emacs</filename> file:"
+msgstr "Para usar o 'nxml-mode' automaticamente para os ficheiros com as extensões <filename>xml</filename>, <filename>xsl</filename>, <filename>rng</filename> ou <filename>xhtml</filename>, adicione o seguinte ao seu ficheiro <filename>.emacs</filename>:"
+d9266 1
+a9266 1
+#: en_US/emacs-nxml.xml:250(computeroutput)
+d9268 4
+a9271 1
+msgid " (setq auto-mode-alist (cons\n\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n "
+d9277 11
+a9287 3
+#: en_US/emacs-nxml.xml:255(para)
+msgid "If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are running Emacs 21.3 or later, then I recommend enabling unify-8859-on-decoding-mode, by adding the following to your <filename>.emacs</filename> file:"
+msgstr "Se editar o XML com as codificações iso-8859-N em vez da iso-8859-1 e estiver a usar o Emacs 21.3 ou posterior, recomenda-se que active o 'unify-8859-on-decoding-mode', adicionando a seguinte sequência ao seu ficheiro <filename>.emacs</filename>:"
+d9289 1
+a9289 1
+#: en_US/emacs-nxml.xml:263(computeroutput)
+d9294 37
+a9330 15
+#: en_US/emacs-nxml.xml:266(para)
+msgid "To get validation and schema-sensitive editing, you need a RELAX NG Compact Syntax (RNC) schema for you document. The schema directory includes some schemas for popular document types."
+msgstr "Para ter uma validação e edição sensível ao esquema, precisa de um esquema de Sintaxe Compacta do Relax NG (RNC) do seu documento. A pasta do esquema inclui alguns esquemas para os tipos de documentos mais conhecidos."
+
+#: en_US/emacs-nxml.xml:272(para)
+msgid "For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://relaxng.org/</ulink>."
+msgstr "Para mais informações sobre o RELAX NG, consulte a página <ulink url=\"http://relaxng.org/\">http://relaxng.org/</ulink>."
+
+#: en_US/emacs-nxml.xml:277(para)
+msgid "For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial.html</ulink>"
+msgstr "Para um tutorial sobre a Sintaxe Compacta do RELAX NG, veja a página <ulink url=\"http://relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial.html</ulink>"
+
+#: en_US/emacs-nxml.xml:282(para)
+msgid "For automatically creating RNC schemas, I recommend my Trang program: <ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee.thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr "Para criar automaticamente os esquemas RNG, recomenda-se o programa Trang: <ulink url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee.thaiopensource.com/relaxng/trang.html\"</ulink>"
+d9332 1
+a9332 1
+#: en_US/emacs-nxml.xml:293(para)
+d9336 1
+a9336 1
+#: en_US/emacs-nxml.xml:298(para)
+d9340 1
+a9340 1
+#: en_US/emacs-nxml.xml:303(para)
+d9344 1
+a9344 1
+#: en_US/emacs-nxml.xml:288(para)
+d9348 22
+a9369 7
+#: en_US/emacs-nxml.xml:310(para)
+msgid "To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html\">http://www.pantor.com/download.html\"</ulink>."
+msgstr "Para converter um esquema de sintaxe em XML do RELAX NG (.rng) para um esquema RNC, poderá também usar a folha de estilo XSLT em <ulink url=\"http://www.pantor.com/download.html\">http://www.pantor.com/download.html\"</ulink>."
+
+#: en_US/emacs-nxml.xml:316(para)
+msgid "To convert a W3C XML Schema to an RNC schema, you need first to convert it to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+msgstr "Para converter um Esquema de XML da W3C num esquema RNC, terá primeiro de o converter para a sintaxe XML do RELAX NG, usando a ferramenta de conversão para RELAX NG da Sun, a 'rngconv' (assente sobre o MSV). Veja em <ulink url=\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+d9371 1
+a9371 1
+#: en_US/emacs-nxml.xml:323(para)
+d9375 10
+a9384 3
+#: en_US/emacs-nxml.xml:327(para)
+msgid "Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug reports, discussion. I will announce all new versions there."
+msgstr "Use por favor a lista <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> para os relatórios de erros, discussão, etc. Serão aí anunciadas todas as versões novas."
+d9386 1
+a9386 1
+#: en_US/emacs-nxml.xml:333(para)
+d9390 1
+a9390 1
+#: en_US/emacs-nxml.xml:336(para)
+d9394 1
+a9394 1
+#: en_US/acknowledgments.xml:11(title)
+d9398 65
+a9462 27
+#: en_US/acknowledgments.xml:13(para)
+msgid "This document is based on the a document started by Tammy Fox (tfox at redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray Fuller (jrfuller at redhat.com)."
+msgstr "Este documento baseia-se num documento iniciado por Tammy Fox (tfox at redhat.com) e com contribuições de Sandra Moore (smoore at redhat.com) e Johnray Fuller (jrfuller at redhat.com)."
+
+#: en_US/acknowledgments.xml:19(para)
+msgid "A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr "Uma correcção do Roozbeh Pournader (roozbeh at sharif.edu) foi aplicada para corrigir alguns erros ortográficos e explicar que o CVS anónimo não permite o envio de novas versões."
+
+#: en_US/acknowledgments.xml:25(para)
+msgid "Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to add the trailing slashes to the <command>figure</command> tag example in <filename>docs-xml-tags.xml</filename>."
+msgstr "Foram aplicadas correcções de Gavin Henry (ghenry at suretecsystems.com) par adicionar as barras finais ao exemplo da marca <command>figure</command>, como aparece em <filename>docs-xml-tags.xml</filename>."
+
+#: en_US/acknowledgments.xml:32(para)
+msgid "A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been applied to add <xref linkend=\"ch-vim\"/>."
+msgstr "Uma actualização do Joshua Daniel Franklin (joshuadfranklin at yahoo.com) para adicionar o <xref linkend=\"ch-vim\"/>."
+
+#: en_US/acknowledgments.xml:37(para)
+msgid "A patch from Karsten Wade (kwade at redhat.com) has been applied to add <xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields (stickstr5 at hotmail.com)."
+msgstr "Uma correcção de Karsten Wade (kwade at redhat.com) foi aplicada para adicionar o <xref linkend=\"sn-screenshots\"/>. Foi editada por Paul W. Frields (stickstr5 at hotmail.com)."
+
+#: en_US/acknowledgments.xml:43(para)
+msgid "A patch from Paul W. Frields (stickstr5 at hotmail.com) has been applied to add more explanation of the <command>screen</command> tag set to <xref linkend=\"sn-xml-tags-screen\"/>."
+msgstr "Uma correcção de Paul W. Frields (stickstr5 at hotmail.com) foi aplicada para adicionar mais explicações sobre o conjunto de marcas <command>screen</command> em <xref linkend=\"sn-xml-tags-screen\"/>."
+
+#: en_US/acknowledgments.xml:49(para)
+msgid "A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been applied to more fully explaing the document building system."
+msgstr "Uma correcção de Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) foi aplicada para descrever com maior pormenor o sistema de compilação de documentos."
+d9465 1
+a9465 1
+#: en_US/acknowledgments.xml:0(None)
+a9467 1
+
+@
+
+
+1.5
+log
+ at Finished the Docs Guide
+@
+text
+ at d5 1
+a5 1
+"PO-Revision-Date: 2007-04-24 02:47+0100\n"
+d41 6
+a46 1
+"X-POFile-SpellExtra: Authoring lang SYSTEM URLS\n"
+d272 1
+a272 1
+msgid "\n<!--$Id: pt.po,v 1.4 2007/04/23 10:39:29 zepires Exp $ -->\n\n <chapter id=\"ch-sample\">\n <title>Sample Chapter</title>\n\n <para>This is a sample chapter, showing you the XML tags used to create a\n chapter, sections, and subsections.</para>\n \n </chapter>\n"
+d275 1
+a275 1
+"<!--$Id: pt.po,v 1.4 2007/04/23 10:39:29 zepires Exp $ -->\n"
+d287 1
+a287 1
+msgstr "O capítulo poderá também ser didivido em secções (<sgmltag>section</sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). Veja mais detalhes em <xref linkend=\"sn-xml-tags-sections\"/>."
+d581 1
+a581 1
+msgstr "Uma declaração de exemplo de figuras."
+d684 1
+a684 1
+msgstr "Use as marcas <command><guibutton></command> e <command></guibutton></command> para demarcar um botão num ecrã ou menu. Po rexemplo:"
+d835 1
+a835 1
+msgstr "As secções abaixo irão discutar as utilizações correctas das diversas listas, bem como descrições para a sua criação."
+d839 1
+a839 1
+msgstr "Uma <command>ItemizedList</command> (lista por itens) é melhor usada para apresentar informações que sejam importantes para o leitor, mas esta não necessita de estar por uma determinada ordem. É mais reduzida que uma <command>VariableList</command> (lista variável) e apresenta a imformação de uma forma muito simples."
+a1422 1
+"\n"
+d1424 1
+a1424 1
+" <title>Compreendeer a Configuração</title>\n"
+d2183 1
+a2183 1
+" \",\"</userinput>. Existem duas formas de usar o seguinte exemplo; podê-lo-ácolocar direcamente no seu ficheiro <filename>.vimrc</filename> ou podê-lo-a gravar num ficheiro separado e fazendo referência com o comando <userinput>source</userinput> no seu <filename>.vimrc</filename>. <screen>\n"
+a2184 1
+"\n"
+a2186 1
+"\n"
+a2191 1
+"\n"
+d2207 1
+a2207 1
+"</screen>"
+d2413 1
+a2413 1
+msgstr "Este capítulo não poderá cobrir possivelmente material suficiente para que um leitor seja um bom escritor. Existem alguns manuais dedicados por inteiro ao estilo de scrita, tendo alguns deles centenas de páginas. Este capítulo contém instruções suficientes para os escritores médios compreenderem a utilização do estilo de documentação técnica."
+d2919 1
+a2919 1
+msgstr "Não use apóstrofos para denotar a pertença (específico do Inglês)"
+d3512 1
+a3512 1
+msgstr "Esta secção contém sugestões de utilização que se baseiam nas situações que os editores do Projecto de Documentação do Fedora encontraram no passado. Deverá ler e compreender estes exemplos para melhorar a sua própira documentação. Os editores do Projecto de Documentação do Fedora agradecem os exemplos adicionais."
+d3632 1
+a3632 1
+msgstr "Evite frases do tipo \"Uma das coisas mais importantes a fazer é <replaceable>XYZ</replaceable>.\" Se o procedimento for importante, o leitor já está à espera dele no seu tutorial. O inverso também se aplica: se um procedimento aparece no seu tutorial, o leitor espera que este seja umportante. Isto é particularmente verdadeiro se usar uma secção inteira para o procedimento em questão. Basta dizer, \"Faça <replaceable>XYZ</replaceable>.\". Depois disso, desenvolva de acordo com as necessidades. Se a secção completa disser respeito à forma como fazer <replaceable>XYZ</replaceable>, retire esta frase por inteiro. Consulte também a secção <xref linkend=\"vle-golden-rule-4\"/>."
+d3720 1
+a3720 1
+msgstr "Evite a pontuação nos títulos das secções ou advertênicas, excepto as vírgulas e somente quando necessário. Use um título que diga algo sobre o comentário da advertência, como \"É Necessário Reiniciar,\" em vez de usar apenas o tipo de advertência como título (\"Nota\")."
+d4008 1
+a4008 1
+msgstr "Para tirar a imagem, seleccione o elemento gráfico com o seu rato, passando-o para primeiro plano, ou organizando os elemenetos. Carregue em <keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> para capturar uma única janela. Para capturar o ecrã completo, use o <keycap>Print Screen</keycap>. Se estiver a tirar uma fotografia de vários elementos e os tiver agrupado em conjunto, poderá recortar a imagem resultante no <application>The GIMP</application>. A imagem estará no formato PNG."
+d4032 1
+a4032 1
+msgstr "Se usar uma imagem gráfica para ilustrar uma função e o modo textual tiver funções idênticas, não inclua ambas, a menos que a omissão de uma delas torne a sua dscrição menos clara."
+d4130 1
+a4130 1
+msgstr "Pense numa entidade de XML como um pedaço predefinido de informação. Poderá representar um bloco de código em XML, ou simplesmene uma palavra ou carácter. Se a informação se alterar, terá de ser substituída apenas uma vez na definição, de modo a corrigir todas as alterações."
+d4250 1
+a4250 1
+msgstr "Esta variável contém uma listagem de todos os ficheiros que contêm definições de entidades. O Projecto de Documentação do Fedora usa um formato em XML especial para guardar as entidades específicas do documeto, de modo que possam ser traduzidas e geradas na altura, como se fosse outro documento em XML qualquer. Aparecerá então um exemplo mais tarde neste guia."
+d4507 1
+a4507 1
+msgstr "São usadas as seguintes ferramentas"
+d4669 1
+a4669 1
+msgstr "Poderá usar o modo PSGML, que está disponível para o Emacs, de modo a ser mais fáicl de escrever no formato XML. O modo PSGML oferece o realce de sintaxe, a completação de marcas, etc."
+d4895 1
+a4895 1
+msgstr "Irá concluir se o processamento terminou quando lhe aparecer a mensagem <computeroutput>Fontifying...done</computeroutput> (A formatar... pronto) no fundo do seu ecrã. Grave a DTD processada num ficheiro com a opção <command>DTD -> Save Parsed DTD</command> (DTD -> Gravar a DTD processada) no menu."
+d4923 1
+a4923 1
+msgstr "Escolha a opção <command>DTD -> Load DTD</command> (DTD -> Carregar a DTD) do menu que aparece e escolher o ficheiro que gravou no passo anterior. Por exemplo, escolha o <filename>docbook.ced</filename>."
+d5273 1
+a5273 1
+msgstr "O <ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\">http://www.snee.com/bob/sgmlfree/psgmqref.html</ulink>—<citetitle>Emacs/PSGML Quick Reference</citetitle> é uma tabela de referência dos comandos do Eamcs para o modo do PSGML."
+d5281 1
+a5281 1
+msgstr "Truqes do PSGML"
+d5428 1
+a5428 1
+msgstr "ao seu ficheiro <filename>.emacs</filename>, onde o <computeroutput>~/nxml-mode-200AMMDD</computeroutput> é a pasta que contém os ficheiros <filename>.elc</filename>. Lembre-se que o <filename>rng-auto.el</filename> não carrega tudo do modo 'nxml-mode'; simplesmente configura as coisas, para que as funcionalidades do 'nxml-mode' sejm carregadas automaticamente. Não deverá tentar carregar automaticamente o <filename>rng-auto.el</filename> propriamente dito."
+d5489 1
+a5489 1
+msgstr "Para converter um Esquema de XML da W3C num esquema RNC, teá primeiro de o converter para a sintaxe XML do RELAX NG, usando a ferramenta de conversão para RELAX NG da Sun, a 'rngconv' (assente sobre o MSV). Veja em <ulink url=\"https://msv.dev.java.net/\">https://www.dev.java.net/</ulink>."
+@
+
+
+1.4
+log
+ at Updates on Documentation Guide
+@
+text
+ at d5 1
+a5 1
+"PO-Revision-Date: 2007-04-23 11:33+0100\n"
+d12 30
+d267 1
+a267 1
+msgid "\n<!--$Id: pt.po,v 1.3 2007/04/23 03:02:41 zepires Exp $ -->\n\n <chapter id=\"ch-sample\">\n <title>Sample Chapter</title>\n\n <para>This is a sample chapter, showing you the XML tags used to create a\n chapter, sections, and subsections.</para>\n \n </chapter>\n"
+d270 1
+a270 1
+"<!--$Id: pt.po,v 1.3 2007/04/23 03:02:41 zepires Exp $ -->\n"
+d500 1
+d1017 59
+d2178 29
+d2358 1
+a2358 1
+msgstr ""
+d2362 1
+a2362 1
+msgstr ""
+d2366 1
+a2366 1
+msgstr ""
+d2370 1
+a2370 1
+msgstr ""
+d2374 1
+a2374 1
+msgstr ""
+d2378 1
+a2378 1
+msgstr ""
+d2382 1
+a2382 1
+msgstr ""
+d2391 1
+a2391 1
+msgstr ""
+d2395 1
+a2395 1
+msgstr ""
+d2400 1
+a2400 1
+msgstr ""
+d2404 1
+a2404 1
+msgstr ""
+d2408 1
+a2408 1
+msgstr ""
+d2412 1
+a2412 1
+msgstr ""
+d2416 1
+a2416 1
+msgstr ""
+d2420 1
+a2420 1
+msgstr ""
+d2424 1
+a2424 1
+msgstr ""
+d2428 1
+a2428 1
+msgstr ""
+d2432 1
+a2432 1
+msgstr ""
+d2436 1
+a2436 1
+msgstr ""
+d2440 1
+a2440 1
+msgstr ""
+d2444 1
+a2444 1
+msgstr ""
+d2452 1
+a2452 1
+msgstr ""
+d2456 1
+a2456 1
+msgstr ""
+d2460 1
+a2460 1
+msgstr ""
+d2464 1
+a2464 1
+msgstr ""
+d2468 1
+a2468 1
+msgstr ""
+d2472 1
+a2472 1
+msgstr ""
+d2476 1
+a2476 1
+msgstr ""
+d2480 1
+a2480 1
+msgstr "Limpar"
+d2484 1
+a2484 1
+msgstr ""
+d2488 1
+a2488 1
+msgstr ""
+d2492 1
+a2492 1
+msgstr ""
+d2496 1
+a2496 1
+msgstr ""
+d2500 1
+a2500 1
+msgstr ""
+d2504 1
+a2504 1
+msgstr ""
+d2508 1
+a2508 1
+msgstr ""
+d2512 1
+a2512 1
+msgstr ""
+d2516 1
+a2516 1
+msgstr ""
+d2520 1
+a2520 1
+msgstr ""
+d2524 1
+a2524 1
+msgstr ""
+d2528 1
+a2528 1
+msgstr ""
+d2532 1
+a2532 1
+msgstr ""
+d2536 1
+a2536 1
+msgstr ""
+d2540 1
+a2540 1
+msgstr ""
+d2544 1
+a2544 1
+msgstr ""
+d2548 1
+a2548 1
+msgstr ""
+d2552 1
+a2552 1
+msgstr ""
+d2556 1
+a2556 1
+msgstr ""
+d2560 1
+a2560 1
+msgstr ""
+d2564 1
+a2564 1
+msgstr ""
+d2568 1
+a2568 1
+msgstr ""
+d2572 1
+a2572 1
+msgstr ""
+d2576 1
+a2576 1
+msgstr ""
+d2580 1
+a2580 1
+msgstr ""
+d2584 1
+a2584 1
+msgstr ""
+d2588 1
+a2588 1
+msgstr ""
+d2592 1
+a2592 1
+msgstr ""
+d2596 1
+a2596 1
+msgstr ""
+d2600 1
+a2600 1
+msgstr ""
+d2604 1
+a2604 1
+msgstr ""
+d2608 1
+a2608 1
+msgstr ""
+d2612 1
+a2612 1
+msgstr ""
+d2616 1
+a2616 1
+msgstr ""
+d2620 1
+a2620 1
+msgstr ""
+d2624 1
+a2624 1
+msgstr ""
+d2628 1
+a2628 1
+msgstr ""
+d2632 1
+a2632 1
+msgstr ""
+d2636 1
+a2636 1
+msgstr ""
+d2640 1
+a2640 1
+msgstr ""
+d2644 1
+a2644 1
+msgstr ""
+d2648 1
+a2648 1
+msgstr ""
+d2652 1
+a2652 1
+msgstr ""
+d2656 1
+a2656 1
+msgstr ""
+d2660 1
+a2660 1
+msgstr ""
+d2664 1
+a2664 1
+msgstr ""
+d2668 1
+a2668 1
+msgstr ""
+d2672 1
+a2672 1
+msgstr ""
+d2676 1
+a2676 1
+msgstr ""
+d2680 1
+a2680 1
+msgstr ""
+d2684 1
+a2684 1
+msgstr ""
+d2688 1
+a2688 1
+msgstr ""
+d2692 1
+a2692 1
+msgstr ""
+d2696 1
+a2696 1
+msgstr ""
+d2700 1
+a2700 1
+msgstr ""
+d2704 1
+a2704 1
+msgstr ""
+d2708 1
+a2708 1
+msgstr ""
+d2712 1
+a2712 1
+msgstr ""
+d2716 1
+a2716 1
+msgstr ""
+d2720 1
+a2720 1
+msgstr ""
+d2724 1
+a2724 1
+msgstr ""
+d2728 1
+a2728 1
+msgstr ""
+d2732 1
+a2732 1
+msgstr ""
+d2736 1
+a2736 1
+msgstr ""
+d2740 1
+a2740 1
+msgstr ""
+d2744 1
+a2744 1
+msgstr ""
+d2748 1
+a2748 1
+msgstr ""
+d2752 1
+a2752 1
+msgstr ""
+d2756 1
+a2756 1
+msgstr ""
+d2760 1
+a2760 1
+msgstr ""
+d2764 1
+a2764 1
+msgstr ""
+d2768 1
+a2768 1
+msgstr ""
+d2772 1
+a2772 1
+msgstr ""
+d2776 1
+a2776 1
+msgstr ""
+d2782 1
+a2782 1
+msgstr ""
+d2786 1
+a2786 1
+msgstr ""
+d2790 1
+a2790 1
+msgstr ""
+d2794 1
+a2794 1
+msgstr ""
+d2798 1
+a2798 1
+msgstr ""
+d2802 1
+a2802 1
+msgstr ""
+d2806 1
+a2806 1
+msgstr ""
+d2810 1
+a2810 1
+msgstr ""
+d2814 1
+a2814 1
+msgstr ""
+d2818 1
+a2818 1
+msgstr ""
+d2822 1
+a2822 1
+msgstr ""
+d2826 1
+a2826 1
+msgstr ""
+d2830 1
+a2830 1
+msgstr ""
+d2834 1
+a2834 1
+msgstr ""
+d2838 1
+a2838 1
+msgstr ""
+d2842 1
+a2842 1
+msgstr ""
+d2846 1
+a2846 1
+msgstr ""
+d2850 1
+a2850 1
+msgstr ""
+d2854 1
+a2854 1
+msgstr ""
+d2858 1
+a2858 1
+msgstr ""
+d2862 1
+a2862 1
+msgstr ""
+d2866 1
+a2866 1
+msgstr ""
+d2870 1
+a2870 1
+msgstr ""
+d2874 1
+a2874 1
+msgstr ""
+d2878 1
+a2878 1
+msgstr ""
+d2882 1
+a2882 1
+msgstr ""
+d2886 1
+a2886 1
+msgstr ""
+d2890 1
+a2890 1
+msgstr ""
+d2894 1
+a2894 1
+msgstr ""
+d2898 1
+a2898 1
+msgstr ""
+d2902 1
+a2902 1
+msgstr ""
+d2906 1
+a2906 1
+msgstr ""
+d2910 1
+a2910 1
+msgstr ""
+d2914 1
+a2914 1
+msgstr ""
+d2918 1
+a2918 1
+msgstr ""
+d2922 1
+a2922 1
+msgstr ""
+d2926 1
+a2926 1
+msgstr ""
+d2930 1
+a2930 1
+msgstr ""
+d2934 1
+a2934 1
+msgstr ""
+d2938 1
+a2938 1
+msgstr ""
+d2942 1
+a2942 1
+msgstr ""
+d2946 1
+a2946 1
+msgstr ""
+d2950 1
+a2950 1
+msgstr ""
+d2954 1
+a2954 1
+msgstr ""
+d2958 1
+a2958 1
+msgstr ""
+d2962 1
+a2962 1
+msgstr ""
+d2966 1
+a2966 1
+msgstr ""
+d2970 1
+a2970 1
+msgstr ""
+d2974 1
+a2974 1
+msgstr ""
+d2978 1
+a2978 1
+msgstr ""
+d2982 1
+a2982 1
+msgstr ""
+d2986 1
+a2986 1
+msgstr ""
+d2990 1
+a2990 1
+msgstr ""
+d2994 1
+a2994 1
+msgstr ""
+d2998 1
+a2998 1
+msgstr ""
+d3002 1
+a3002 1
+msgstr ""
+d3006 1
+a3006 1
+msgstr ""
+d3010 1
+a3010 1
+msgstr ""
+d3014 1
+a3014 1
+msgstr ""
+d3018 1
+a3018 1
+msgstr ""
+d3022 1
+a3022 1
+msgstr ""
+d3026 1
+a3026 1
+msgstr ""
+d3030 1
+a3030 1
+msgstr ""
+d3034 1
+a3034 1
+msgstr ""
+d3038 1
+a3038 1
+msgstr ""
+d3042 1
+a3042 1
+msgstr ""
+d3046 1
+a3046 1
+msgstr ""
+d3050 1
+a3050 1
+msgstr ""
+d3054 1
+a3054 1
+msgstr ""
+d3058 1
+a3058 1
+msgstr ""
+d3062 1
+a3062 1
+msgstr ""
+d3066 1
+a3066 1
+msgstr ""
+d3070 1
+a3070 1
+msgstr ""
+d3074 1
+a3074 1
+msgstr ""
+d3078 1
+a3078 1
+msgstr ""
+d3082 1
+a3082 1
+msgstr ""
+d3086 1
+a3086 1
+msgstr ""
+d3090 1
+a3090 1
+msgstr ""
+d3094 1
+a3094 1
+msgstr ""
+d3098 1
+a3098 1
+msgstr ""
+d3102 1
+a3102 1
+msgstr ""
+d3106 1
+a3106 1
+msgstr ""
+d3110 1
+a3110 1
+msgstr ""
+d3114 1
+a3114 1
+msgstr ""
+d3118 1
+a3118 1
+msgstr ""
+d3122 1
+a3122 1
+msgstr ""
+d3126 1
+a3126 1
+msgstr ""
+d3130 1
+a3130 1
+msgstr ""
+d3134 1
+a3134 1
+msgstr ""
+d3138 1
+a3138 1
+msgstr ""
+d3142 1
+a3142 1
+msgstr ""
+d3146 1
+a3146 1
+msgstr ""
+d3150 1
+a3150 1
+msgstr ""
+d3154 1
+a3154 1
+msgstr ""
+d3158 1
+a3158 1
+msgstr ""
+d3162 1
+a3162 1
+msgstr ""
+d3166 1
+a3166 1
+msgstr ""
+d3170 1
+a3170 1
+msgstr ""
+d3174 1
+a3174 1
+msgstr ""
+d3178 1
+a3178 1
+msgstr ""
+d3182 1
+a3182 1
+msgstr ""
+d3186 1
+a3186 1
+msgstr ""
+d3190 1
+a3190 1
+msgstr ""
+d3194 1
+a3194 1
+msgstr ""
+d3198 1
+a3198 1
+msgstr ""
+d3202 1
+a3202 1
+msgstr ""
+d3206 1
+a3206 1
+msgstr ""
+d3210 1
+a3210 1
+msgstr ""
+d3214 1
+a3214 1
+msgstr ""
+d3218 1
+a3218 1
+msgstr ""
+d3222 1
+a3222 1
+msgstr ""
+d3226 1
+a3226 1
+msgstr ""
+d3230 1
+a3230 1
+msgstr ""
+d3234 1
+a3234 1
+msgstr ""
+d3238 1
+a3238 1
+msgstr ""
+d3242 1
+a3242 1
+msgstr ""
+d3246 1
+a3246 1
+msgstr ""
+d3250 1
+a3250 1
+msgstr ""
+d3254 1
+a3254 1
+msgstr ""
+d3258 1
+a3258 1
+msgstr ""
+d3262 1
+a3262 1
+msgstr ""
+d3266 1
+a3266 1
+msgstr ""
+d3270 1
+a3270 1
+msgstr ""
+d3274 1
+a3274 1
+msgstr ""
+d3278 1
+a3278 1
+msgstr ""
+d3282 1
+a3282 1
+msgstr ""
+d3286 1
+a3286 1
+msgstr ""
+d3290 1
+a3290 1
+msgstr ""
+d3294 1
+a3294 1
+msgstr ""
+d3298 1
+a3298 1
+msgstr ""
+d3302 1
+a3302 1
+msgstr ""
+d3306 1
+a3306 1
+msgstr ""
+d3310 1
+a3310 1
+msgstr ""
+d3314 1
+a3314 1
+msgstr ""
+d3318 1
+a3318 1
+msgstr ""
+d3322 1
+a3322 1
+msgstr ""
+d3326 1
+a3326 1
+msgstr ""
+d3330 1
+a3330 1
+msgstr ""
+d3334 1
+a3334 1
+msgstr ""
+d3338 1
+a3338 1
+msgstr ""
+d3342 1
+a3342 1
+msgstr ""
+d3346 1
+a3346 1
+msgstr ""
+d3350 1
+a3350 1
+msgstr ""
+d3354 1
+a3354 1
+msgstr ""
+d3358 1
+a3358 1
+msgstr ""
+d3362 1
+a3362 1
+msgstr ""
+d3366 1
+a3366 1
+msgstr ""
+d3370 1
+a3370 1
+msgstr ""
+d3374 1
+a3374 1
+msgstr ""
+d3378 1
+a3378 1
+msgstr ""
+d3382 1
+a3382 1
+msgstr ""
+d3386 1
+a3386 1
+msgstr ""
+d3390 1
+a3390 1
+msgstr ""
+d3394 1
+a3394 1
+msgstr ""
+d3398 1
+a3398 1
+msgstr ""
+d3402 1
+a3402 1
+msgstr ""
+d3406 1
+a3406 1
+msgstr ""
+d3410 1
+a3410 1
+msgstr ""
+d3414 1
+a3414 1
+msgstr ""
+d3418 1
+a3418 1
+msgstr ""
+d3422 1
+a3422 1
+msgstr ""
+d3426 1
+a3426 1
+msgstr ""
+d3430 1
+a3430 1
+msgstr ""
+d3434 1
+a3434 1
+msgstr ""
+d3438 1
+a3438 1
+msgstr ""
+d3442 1
+a3442 1
+msgstr ""
+d3446 1
+a3446 1
+msgstr ""
+d3450 1
+a3450 1
+msgstr ""
+d3454 1
+a3454 1
+msgstr ""
+d3458 1
+a3458 1
+msgstr ""
+d3462 1
+a3462 1
+msgstr ""
+d3466 1
+a3466 1
+msgstr ""
+d3470 1
+a3470 1
+msgstr ""
+d3474 1
+a3474 1
+msgstr ""
+d3478 1
+a3478 1
+msgstr ""
+d3482 1
+a3482 1
+msgstr ""
+d3486 1
+a3486 1
+msgstr ""
+d3490 1
+a3490 1
+msgstr ""
+d3494 1
+a3494 1
+msgstr ""
+d3498 1
+a3498 1
+msgstr ""
+d3502 1
+a3502 1
+msgstr ""
+d3511 1
+a3511 1
+msgstr ""
+d3515 1
+a3515 1
+msgstr ""
+d3519 1
+a3519 1
+msgstr ""
+d3523 1
+a3523 1
+msgstr ""
+d3527 1
+a3527 1
+msgstr ""
+d3531 1
+a3531 1
+msgstr ""
+d3535 1
+a3535 1
+msgstr ""
+d3539 1
+a3539 1
+msgstr ""
+d3543 1
+a3543 1
+msgstr ""
+d3547 1
+a3547 1
+msgstr ""
+d3551 1
+a3551 1
+msgstr ""
+d3555 1
+a3555 1
+msgstr ""
+d3559 1
+a3559 1
+msgstr ""
+d3563 1
+a3563 1
+msgstr ""
+d3567 1
+a3567 1
+msgstr ""
+d3571 1
+a3571 1
+msgstr ""
+d3575 1
+a3575 1
+msgstr ""
+d3579 1
+a3579 1
+msgstr ""
+d3583 1
+a3583 1
+msgstr ""
+d3587 1
+a3587 1
+msgstr ""
+d3591 1
+a3591 1
+msgstr ""
+d3595 1
+a3595 1
+msgstr ""
+d3599 1
+a3599 1
+msgstr ""
+d3603 1
+a3603 1
+msgstr ""
+d3607 1
+a3607 1
+msgstr ""
+d3611 1
+a3611 1
+msgstr ""
+d3615 1
+a3615 1
+msgstr ""
+d3619 1
+a3619 1
+msgstr ""
+d3623 1
+a3623 1
+msgstr ""
+d3627 1
+a3627 1
+msgstr ""
+d3631 1
+a3631 1
+msgstr ""
+d3635 1
+a3635 1
+msgstr ""
+d3639 1
+a3639 1
+msgstr ""
+d3643 1
+a3643 1
+msgstr ""
+d3647 1
+a3647 1
+msgstr ""
+d3651 1
+a3651 1
+msgstr ""
+d3655 1
+a3655 1
+msgstr ""
+d3659 1
+a3659 1
+msgstr ""
+d3663 1
+a3663 1
+msgstr ""
+d3667 1
+a3667 1
+msgstr ""
+d3671 1
+a3671 1
+msgstr ""
+d3675 1
+a3675 1
+msgstr ""
+d3679 1
+a3679 1
+msgstr ""
+d3683 1
+a3683 1
+msgstr ""
+d3687 1
+a3687 1
+msgstr ""
+d3691 1
+a3691 1
+msgstr ""
+d3695 1
+a3695 1
+msgstr ""
+d3699 1
+a3699 1
+msgstr ""
+d3703 1
+a3703 1
+msgstr ""
+d3707 1
+a3707 1
+msgstr ""
+d3711 1
+a3711 1
+msgstr ""
+d3715 1
+a3715 1
+msgstr ""
+d3719 1
+a3719 1
+msgstr ""
+d3723 1
+a3723 1
+msgstr ""
+d3727 1
+a3727 1
+msgstr ""
+d3731 1
+a3731 1
+msgstr ""
+d3735 1
+a3735 1
+msgstr ""
+d3739 1
+a3739 1
+msgstr ""
+d3743 1
+a3743 1
+msgstr ""
+d3747 1
+a3747 1
+msgstr ""
+d3751 1
+a3751 1
+msgstr ""
+d3755 1
+a3755 1
+msgstr ""
+d3759 1
+a3759 1
+msgstr ""
+d3763 1
+a3763 1
+msgstr ""
+d3767 1
+a3767 1
+msgstr ""
+d3771 1
+a3771 1
+msgstr ""
+d3775 1
+a3775 1
+msgstr ""
+d3779 1
+a3779 1
+msgstr ""
+d3783 1
+a3783 1
+msgstr ""
+d3787 1
+a3787 1
+msgstr ""
+d3791 1
+a3791 1
+msgstr ""
+d3795 1
+a3795 1
+msgstr ""
+d3799 1
+a3799 1
+msgstr ""
+d3803 1
+a3803 1
+msgstr ""
+d3807 1
+a3807 1
+msgstr ""
+d3815 1
+a3815 1
+msgstr ""
+d3819 1
+a3819 1
+msgstr ""
+d3823 1
+a3823 1
+msgstr ""
+d3827 1
+a3827 1
+msgstr ""
+d3831 1
+a3831 1
+msgstr ""
+d3835 1
+a3835 1
+msgstr ""
+d3839 1
+a3839 1
+msgstr ""
+d3843 1
+a3843 1
+msgstr ""
+d3847 1
+a3847 1
+msgstr ""
+d3851 1
+a3851 1
+msgstr ""
+d3855 1
+a3855 1
+msgstr ""
+d3859 1
+a3859 1
+msgstr ""
+d3863 1
+a3863 1
+msgstr ""
+d3867 1
+a3867 1
+msgstr ""
+d3871 1
+a3871 1
+msgstr ""
+d3875 1
+a3875 1
+msgstr ""
+d3879 1
+a3879 1
+msgstr ""
+d3883 1
+a3883 1
+msgstr ""
+d3887 1
+a3887 1
+msgstr ""
+d3891 1
+a3891 1
+msgstr ""
+d3895 1
+a3895 1
+msgstr ""
+d3899 1
+a3899 1
+msgstr ""
+d3903 1
+a3903 1
+msgstr ""
+d3907 1
+a3907 1
+msgstr "atenção"
+d3911 1
+a3911 1
+msgstr ""
+d3915 1
+a3915 1
+msgstr ""
+d3919 1
+a3919 1
+msgstr ""
+d3923 1
+a3923 1
+msgstr ""
+d3927 1
+a3927 1
+msgstr ""
+d3931 1
+a3931 1
+msgstr ""
+d3935 1
+a3935 1
+msgstr ""
+d3939 1
+a3939 1
+msgstr ""
+d3943 1
+a3943 1
+msgstr ""
+d3947 1
+a3947 1
+msgstr ""
+d3951 1
+a3951 1
+msgstr ""
+d3955 1
+a3955 1
+msgstr ""
+d3959 1
+a3959 1
+msgstr ""
+d3963 1
+a3963 1
+msgstr ""
+d3967 1
+a3967 1
+msgstr ""
+d3971 1
+a3971 1
+msgstr ""
+d3975 1
+a3975 1
+msgstr ""
+d3979 1
+a3979 1
+msgstr ""
+d3983 1
+a3983 1
+msgstr ""
+d3987 1
+a3987 1
+msgstr ""
+d3991 1
+a3991 1
+msgstr ""
+d3995 1
+a3995 1
+msgstr ""
+d3999 1
+a3999 1
+msgstr ""
+d4003 1
+a4003 1
+msgstr ""
+d4007 1
+a4007 1
+msgstr ""
+d4011 1
+a4011 1
+msgstr ""
+d4015 1
+a4015 1
+msgstr ""
+d4019 1
+a4019 1
+msgstr ""
+d4023 1
+a4023 1
+msgstr ""
+d4027 1
+a4027 1
+msgstr ""
+d4031 1
+a4031 1
+msgstr ""
+d4035 1
+a4035 1
+msgstr ""
+d4039 1
+a4039 1
+msgstr ""
+d4043 1
+a4043 1
+msgstr ""
+d4047 1
+a4047 1
+msgstr ""
+d4051 1
+a4051 1
+msgstr ""
+d4055 1
+a4055 1
+msgstr ""
+d4060 1
+a4060 1
+msgstr ""
+d4064 1
+a4064 1
+msgstr ""
+d4070 4
+d4077 1
+a4077 1
+msgstr ""
+d4081 1
+a4081 1
+msgstr ""
+d4085 1
+a4085 1
+msgstr ""
+d4089 1
+a4089 1
+msgstr ""
+d4093 1
+a4093 1
+msgstr ""
+d4097 1
+a4097 1
+msgstr ""
+d4101 1
+a4101 1
+msgstr ""
+d4109 1
+a4109 1
+msgstr ""
+d4113 1
+a4113 1
+msgstr ""
+d4117 1
+a4117 1
+msgstr ""
+d4125 1
+a4125 1
+msgstr ""
+d4129 1
+a4129 1
+msgstr ""
+d4133 1
+a4133 1
+msgstr ""
+d4137 1
+a4137 1
+msgstr ""
+d4141 1
+a4141 1
+msgstr ""
+d4145 1
+a4145 1
+msgstr ""
+d4149 1
+a4149 1
+msgstr ""
+d4153 1
+a4153 1
+msgstr ""
+d4157 1
+a4157 1
+msgstr ""
+d4161 1
+a4161 1
+msgstr ""
+d4165 1
+a4165 1
+msgstr ""
+d4169 1
+a4169 1
+msgstr ""
+d4173 1
+a4173 1
+msgstr ""
+d4177 1
+a4177 1
+msgstr ""
+d4181 1
+a4181 1
+msgstr ""
+d4185 1
+a4185 1
+msgstr ""
+d4189 1
+a4189 1
+msgstr ""
+d4193 1
+a4193 1
+msgstr ""
+d4197 1
+a4197 1
+msgstr ""
+d4201 1
+a4201 1
+msgstr ""
+d4205 1
+a4205 1
+msgstr ""
+d4209 1
+a4209 1
+msgstr ""
+d4213 1
+a4213 1
+msgstr ""
+d4217 1
+a4217 1
+msgstr ""
+d4221 1
+a4221 1
+msgstr ""
+d4225 1
+a4225 1
+msgstr ""
+d4229 1
+a4229 1
+msgstr ""
+d4233 1
+a4233 1
+msgstr ""
+d4237 1
+a4237 1
+msgstr ""
+d4241 1
+a4241 1
+msgstr ""
+d4245 1
+a4245 1
+msgstr ""
+d4249 1
+a4249 1
+msgstr ""
+d4253 1
+a4253 1
+msgstr ""
+d4257 1
+a4257 1
+msgstr ""
+d4261 1
+a4261 1
+msgstr ""
+d4265 1
+a4265 1
+msgstr ""
+d4269 1
+a4269 1
+msgstr ""
+d4273 1
+a4273 1
+msgstr ""
+d4277 1
+a4277 1
+msgstr ""
+d4281 1
+a4281 1
+msgstr ""
+d4285 1
+a4285 1
+msgstr ""
+d4289 1
+a4289 1
+msgstr ""
+d4293 1
+a4293 1
+msgstr ""
+d4297 1
+a4297 1
+msgstr ""
+d4301 1
+a4301 1
+msgstr ""
+d4305 1
+a4305 1
+msgstr ""
+d4309 1
+a4309 1
+msgstr ""
+d4313 1
+a4313 1
+msgstr ""
+d4317 1
+a4317 1
+msgstr ""
+d4321 1
+a4321 1
+msgstr ""
+d4325 1
+a4325 1
+msgstr ""
+d4329 1
+a4329 1
+msgstr ""
+d4333 1
+a4333 1
+msgstr ""
+d4337 1
+a4337 1
+msgstr ""
+d4341 1
+a4341 1
+msgstr ""
+d4345 1
+a4345 1
+msgstr ""
+d4349 1
+a4349 1
+msgstr ""
+d4353 1
+a4353 1
+msgstr ""
+d4357 1
+a4357 1
+msgstr ""
+d4361 1
+a4361 1
+msgstr ""
+d4365 1
+a4365 1
+msgstr ""
+d4369 1
+a4369 1
+msgstr ""
+d4373 1
+a4373 1
+msgstr ""
+d4377 1
+a4377 1
+msgstr "tudo"
+d4381 1
+a4381 1
+msgstr ""
+d4385 1
+a4385 1
+msgstr ""
+d4389 1
+a4389 1
+msgstr ""
+d4393 1
+a4393 1
+msgstr ""
+d4397 1
+a4397 1
+msgstr ""
+d4401 1
+a4401 1
+msgstr ""
+d4405 1
+a4405 1
+msgstr ""
+d4409 1
+a4409 1
+msgstr ""
+d4413 1
+a4413 1
+msgstr ""
+d4417 1
+a4417 1
+msgstr ""
+d4421 1
+a4421 1
+msgstr ""
+d4425 1
+a4425 1
+msgstr ""
+d4429 1
+a4429 1
+msgstr ""
+d4433 1
+a4433 1
+msgstr ""
+d4437 1
+a4437 1
+msgstr ""
+d4441 1
+a4441 1
+msgstr ""
+d4445 1
+a4445 1
+msgstr ""
+d4449 1
+a4449 1
+msgstr ""
+d4453 1
+a4453 1
+msgstr ""
+d4457 1
+a4457 1
+msgstr ""
+d4461 1
+a4461 1
+msgstr ""
+d4465 1
+a4465 1
+msgstr ""
+d4469 1
+a4469 1
+msgstr ""
+d4473 1
+a4473 1
+msgstr ""
+d4477 1
+a4477 1
+msgstr ""
+d4481 1
+a4481 1
+msgstr ""
+d4485 1
+a4485 1
+msgstr ""
+d4502 1
+a4502 1
+msgstr ""
+d4506 1
+a4506 1
+msgstr ""
+d4510 1
+a4510 1
+msgstr ""
+d4514 1
+a4514 1
+msgstr ""
+d4518 1
+a4518 1
+msgstr ""
+d4522 1
+a4522 1
+msgstr ""
+d4526 1
+a4526 1
+msgstr ""
+d4530 1
+a4530 1
+msgstr ""
+d4534 1
+a4534 1
+msgstr ""
+d4542 1
+a4542 1
+msgstr ""
+d4547 1
+a4547 1
+msgstr ""
+d4551 1
+a4551 1
+msgstr ""
+d4556 1
+a4556 1
+msgstr ""
+d4560 1
+a4560 1
+msgstr ""
+d4564 1
+a4564 1
+msgstr ""
+d4568 1
+a4568 1
+msgstr ""
+d4578 5
+d4586 1
+a4586 1
+msgstr ""
+d4590 1
+a4590 1
+msgstr ""
+d4594 1
+a4594 1
+msgstr ""
+d4598 1
+a4598 1
+msgstr ""
+d4602 1
+a4602 1
+msgstr ""
+d4606 1
+a4606 1
+msgstr ""
+d4610 1
+a4610 1
+msgstr ""
+d4614 1
+a4614 1
+msgstr ""
+d4618 1
+a4618 1
+msgstr ""
+d4623 1
+a4623 1
+msgstr ""
+d4629 8
+d4640 1
+a4640 1
+msgstr ""
+d4644 1
+a4644 1
+msgstr ""
+d4648 1
+a4648 1
+msgstr ""
+d4652 1
+a4652 1
+msgstr ""
+d4656 1
+a4656 1
+msgstr ""
+d4664 1
+a4664 1
+msgstr ""
+d4668 1
+a4668 1
+msgstr ""
+d4672 1
+a4672 1
+msgstr ""
+d4676 1
+a4676 1
+msgstr ""
+d4681 1
+a4681 1
+msgstr ""
+d4685 1
+a4685 1
+msgstr ""
+d4689 1
+a4689 1
+msgstr ""
+d4694 125
+d4822 1
+a4822 1
+msgstr ""
+d4826 1
+a4826 1
+msgstr ""
+d4830 1
+a4830 1
+msgstr ""
+d4834 1
+a4834 1
+msgstr ""
+d4838 1
+a4838 1
+msgstr ""
+d4842 1
+a4842 1
+msgstr ""
+d4846 1
+a4846 1
+msgstr ""
+d4850 1
+a4850 1
+msgstr ""
+d4854 1
+a4854 1
+msgstr ""
+d4858 1
+a4858 1
+msgstr ""
+d4862 1
+a4862 1
+msgstr ""
+d4866 1
+a4866 1
+msgstr ""
+d4870 1
+a4870 1
+msgstr ""
+d4874 1
+a4874 1
+msgstr ""
+d4878 1
+a4878 1
+msgstr ""
+d4882 1
+a4882 1
+msgstr ""
+d4886 1
+a4886 1
+msgstr ""
+d4890 1
+a4890 1
+msgstr ""
+d4894 1
+a4894 1
+msgstr ""
+d4898 1
+a4898 1
+msgstr ""
+d4902 1
+a4902 1
+msgstr ""
+d4906 1
+a4906 1
+msgstr ""
+d4910 1
+a4910 1
+msgstr ""
+d4914 1
+a4914 1
+msgstr ""
+d4918 1
+a4918 1
+msgstr ""
+d4922 1
+a4922 1
+msgstr ""
+d4926 1
+a4926 1
+msgstr ""
+d4930 1
+a4930 1
+msgstr ""
+d4934 1
+a4934 1
+msgstr ""
+d4938 1
+a4938 1
+msgstr ""
+d4942 1
+a4942 1
+msgstr ""
+d4946 1
+a4946 1
+msgstr ""
+d4950 1
+a4950 1
+msgstr ""
+d4954 1
+a4954 1
+msgstr ""
+d4958 1
+a4958 1
+msgstr ""
+d4962 1
+a4962 1
+msgstr ""
+d4966 1
+a4966 1
+msgstr ""
+d4970 1
+a4970 1
+msgstr ""
+d4974 1
+a4974 1
+msgstr ""
+d4978 1
+a4978 1
+msgstr ""
+d4982 1
+a4982 1
+msgstr ""
+d4986 1
+a4986 1
+msgstr ""
+d4994 1
+a4994 1
+msgstr ""
+d5002 1
+a5002 1
+msgstr ""
+d5006 1
+a5006 1
+msgstr ""
+d5010 1
+a5010 1
+msgstr ""
+d5014 1
+a5014 1
+msgstr ""
+d5018 1
+a5018 1
+msgstr ""
+d5022 1
+a5022 1
+msgstr ""
+d5026 1
+a5026 1
+msgstr ""
+d5034 1
+a5034 1
+msgstr ""
+d5038 1
+a5038 1
+msgstr ""
+d5042 1
+a5042 1
+msgstr ""
+d5046 1
+a5046 1
+msgstr ""
+d5050 1
+a5050 1
+msgstr ""
+d5054 1
+a5054 1
+msgstr ""
+d5058 1
+a5058 1
+msgstr ""
+d5062 1
+a5062 1
+msgstr ""
+d5066 1
+a5066 1
+msgstr "Fim"
+d5070 1
+a5070 1
+msgstr ""
+d5074 1
+a5074 1
+msgstr ""
+d5078 1
+a5078 1
+msgstr ""
+d5082 1
+a5082 1
+msgstr ""
+d5086 1
+a5086 1
+msgstr ""
+d5090 1
+a5090 1
+msgstr ""
+d5094 1
+a5094 1
+msgstr ""
+d5098 1
+a5098 1
+msgstr ""
+d5102 1
+a5102 1
+msgstr ""
+d5110 1
+a5110 1
+msgstr ""
+d5114 1
+a5114 1
+msgstr ""
+d5118 1
+a5118 1
+msgstr ""
+d5122 1
+a5122 1
+msgstr ""
+d5126 1
+a5126 1
+msgstr "f"
+d5130 1
+a5130 1
+msgstr ""
+d5134 1
+a5134 1
+msgstr ""
+d5138 1
+a5138 1
+msgstr ""
+d5142 1
+a5142 1
+msgstr ""
+d5146 1
+a5146 1
+msgstr ""
+d5150 1
+a5150 1
+msgstr ""
+d5155 1
+a5155 1
+msgstr ""
+d5159 1
+a5159 1
+msgstr ""
+d5163 1
+a5163 1
+msgstr ""
+d5167 1
+a5167 1
+msgstr ""
+d5171 1
+a5171 1
+msgstr ""
+d5175 1
+a5175 1
+msgstr ""
+d5179 1
+a5179 1
+msgstr ""
+d5183 1
+a5183 1
+msgstr ""
+d5188 1
+a5188 1
+msgstr ""
+d5192 1
+a5192 1
+msgstr ""
+d5196 1
+a5196 1
+msgstr ""
+d5200 1
+a5200 1
+msgstr ""
+d5206 7
+d5216 1
+a5216 1
+msgstr ""
+d5220 1
+a5220 1
+msgstr ""
+d5224 1
+a5224 1
+msgstr ""
+d5228 1
+a5228 1
+msgstr ""
+d5232 1
+a5232 1
+msgstr ""
+d5236 1
+a5236 1
+msgstr ""
+d5240 1
+a5240 1
+msgstr ""
+d5244 1
+a5244 1
+msgstr ""
+d5252 1
+a5252 1
+msgstr ""
+d5256 1
+a5256 1
+msgstr ""
+d5260 1
+a5260 1
+msgstr ""
+d5264 1
+a5264 1
+msgstr ""
+d5268 1
+a5268 1
+msgstr ""
+d5272 1
+a5272 1
+msgstr ""
+d5276 1
+a5276 1
+msgstr ""
+d5280 1
+a5280 1
+msgstr ""
+d5284 1
+a5284 1
+msgstr ""
+d5288 1
+a5288 1
+msgstr ""
+d5292 1
+a5292 1
+msgstr ""
+d5296 1
+a5296 1
+msgstr ""
+d5300 1
+a5300 1
+msgstr ""
+d5304 1
+a5304 1
+msgstr ""
+d5308 1
+a5308 1
+msgstr ""
+d5316 1
+a5316 1
+msgstr ""
+d5320 1
+a5320 1
+msgstr ""
+d5324 1
+a5324 1
+msgstr ""
+d5328 1
+a5328 1
+msgstr ""
+d5332 1
+a5332 1
+msgstr ""
+d5336 1
+a5336 1
+msgstr ""
+d5340 1
+a5340 1
+msgstr ""
+d5344 1
+a5344 1
+msgstr ""
+d5348 1
+a5348 1
+msgstr ""
+d5352 1
+a5352 1
+msgstr ""
+d5356 1
+a5356 1
+msgstr ""
+d5360 1
+a5360 1
+msgstr ""
+d5364 1
+a5364 1
+msgstr ""
+d5368 1
+a5368 1
+msgstr ""
+d5372 1
+a5372 1
+msgstr ""
+d5376 1
+a5376 1
+msgstr ""
+d5380 1
+a5380 1
+msgstr ""
+d5384 1
+a5384 1
+msgstr ""
+d5388 1
+a5388 1
+msgstr ""
+d5392 1
+a5392 1
+msgstr ""
+d5396 1
+a5396 1
+msgstr ""
+d5400 1
+a5400 1
+msgstr ""
+d5404 1
+a5404 1
+msgstr ""
+d5408 1
+a5408 1
+msgstr ""
+d5412 1
+a5412 1
+msgstr ""
+d5416 1
+a5416 1
+msgstr ""
+d5422 2
+d5427 1
+a5427 1
+msgstr ""
+d5431 1
+a5431 1
+msgstr ""
+d5437 3
+d5443 1
+a5443 1
+msgstr ""
+d5448 1
+a5448 1
+msgstr ""
+d5452 1
+a5452 1
+msgstr ""
+d5456 1
+a5456 1
+msgstr ""
+d5460 1
+a5460 1
+msgstr ""
+d5464 1
+a5464 1
+msgstr ""
+d5468 1
+a5468 1
+msgstr ""
+d5472 1
+a5472 1
+msgstr ""
+d5476 1
+a5476 1
+msgstr ""
+d5480 1
+a5480 1
+msgstr ""
+d5484 1
+a5484 1
+msgstr ""
+d5488 1
+a5488 1
+msgstr ""
+d5492 1
+a5492 1
+msgstr ""
+d5496 1
+a5496 1
+msgstr ""
+d5500 1
+a5500 1
+msgstr ""
+d5504 1
+a5504 1
+msgstr ""
+d5512 1
+a5512 1
+msgstr ""
+d5516 1
+a5516 1
+msgstr ""
+d5520 1
+a5520 1
+msgstr ""
+d5524 1
+a5524 1
+msgstr ""
+d5528 1
+a5528 1
+msgstr ""
+d5532 1
+a5532 1
+msgstr ""
+d5536 1
+a5536 1
+msgstr ""
+@
+
+
+1.3
+log
+ at Updates on Documentation Guide
+@
+text
+ at d5 1
+a5 1
+"PO-Revision-Date: 2007-04-22 18:18+0100\n"
+d237 1
+a237 1
+msgid "\n<!--$Id: pt.po,v 1.2 2007/04/18 14:53:04 zepires Exp $ -->\n\n <chapter id=\"ch-sample\">\n <title>Sample Chapter</title>\n\n <para>This is a sample chapter, showing you the XML tags used to create a\n chapter, sections, and subsections.</para>\n \n </chapter>\n"
+d240 1
+a240 1
+"<!--$Id: pt.po,v 1.2 2007/04/18 14:53:04 zepires Exp $ -->\n"
+d1354 6
+d1363 1
+a1363 1
+msgstr ""
+d1367 1
+a1367 1
+msgstr ""
+d1371 1
+a1371 1
+msgstr ""
+d1375 1
+a1375 1
+msgstr ""
+d1379 1
+a1379 1
+msgstr ""
+d1383 1
+a1383 1
+msgstr ""
+d1388 1
+a1388 1
+msgstr ""
+d1392 1
+a1392 1
+msgstr ""
+d1401 1
+a1401 1
+msgstr ""
+d1405 1
+a1405 1
+msgstr ""
+d1409 1
+a1409 1
+msgstr ""
+d1413 1
+a1413 1
+msgstr ""
+d1417 1
+a1417 1
+msgstr ""
+d1421 1
+a1421 1
+msgstr ""
+d1427 4
+d1436 3
+d1442 1
+a1442 1
+msgstr ""
+d1446 1
+a1446 1
+msgstr ""
+d1450 1
+a1450 1
+msgstr ""
+d1454 1
+a1454 1
+msgstr ""
+d1458 1
+a1458 1
+msgstr ""
+d1462 1
+a1462 1
+msgstr ""
+d1466 1
+a1466 1
+msgstr ""
+d1470 1
+a1470 1
+msgstr ""
+d1474 1
+a1474 1
+msgstr ""
+d1480 16
+d1499 1
+a1499 1
+msgstr ""
+d1504 1
+a1504 1
+msgstr ""
+d1508 1
+a1508 1
+msgstr ""
+d1513 1
+a1513 1
+msgstr ""
+d1517 1
+a1517 1
+msgstr ""
+d1521 1
+a1521 1
+msgstr ""
+d1525 1
+a1525 1
+msgstr ""
+d1529 1
+a1529 1
+msgstr ""
+d1535 8
+d1546 1
+a1546 1
+msgstr ""
+d1551 1
+a1551 1
+msgstr ""
+d1556 1
+a1556 1
+msgstr ""
+d1560 1
+a1560 1
+msgstr ""
+d1564 1
+a1564 1
+msgstr ""
+d1568 1
+a1568 1
+msgstr ""
+d1572 1
+a1572 1
+msgstr ""
+d1578 25
+d1606 1
+a1606 1
+msgstr ""
+d1612 13
+d1628 1
+a1628 1
+msgstr ""
+d1632 1
+a1632 1
+msgstr ""
+d1636 1
+a1636 1
+msgstr ""
+d1640 1
+a1640 1
+msgstr ""
+d1644 1
+a1644 1
+msgstr ""
+d1648 1
+a1648 1
+msgstr ""
+d1652 1
+a1652 1
+msgstr ""
+d1656 1
+a1656 1
+msgstr ""
+d1660 1
+a1660 1
+msgstr ""
+d1664 1
+a1664 1
+msgstr ""
+d1668 1
+a1668 1
+msgstr ""
+d1672 1
+a1672 1
+msgstr ""
+d1676 1
+a1676 1
+msgstr ""
+d1680 1
+a1680 1
+msgstr ""
+d1684 1
+a1684 1
+msgstr ""
+d1688 1
+a1688 1
+msgstr ""
+d1694 54
+d1751 1
+a1751 1
+msgstr ""
+d1763 1
+a1763 1
+msgstr ""
+d1767 1
+a1767 1
+msgstr ""
+d1771 1
+a1771 1
+msgstr ""
+d1775 1
+a1775 1
+msgstr ""
+d1779 1
+a1779 1
+msgstr ""
+d1783 1
+a1783 1
+msgstr ""
+d1787 1
+a1787 1
+msgstr ""
+d1791 1
+a1791 1
+msgstr ""
+d1797 51
+d1851 1
+a1851 1
+msgstr ""
+d1855 1
+a1855 1
+msgstr ""
+d1859 1
+a1859 1
+msgstr ""
+d1867 1
+a1867 1
+msgstr ""
+d1875 1
+a1875 1
+msgstr ""
+d1879 1
+a1879 1
+msgstr ""
+d1883 1
+a1883 1
+msgstr ""
+d1887 1
+a1887 1
+msgstr ""
+d1891 1
+a1891 1
+msgstr ""
+d1895 1
+a1895 1
+msgstr ""
+d1899 1
+a1899 1
+msgstr ""
+d1903 1
+a1903 1
+msgstr ""
+d1907 1
+a1907 1
+msgstr ""
+d1911 1
+a1911 1
+msgstr ""
+d1915 1
+a1915 1
+msgstr ""
+d1919 1
+a1919 1
+msgstr ""
+d1923 1
+a1923 1
+msgstr ""
+d1929 4
+d1936 1
+a1936 1
+msgstr ""
+d1940 1
+a1940 1
+msgstr ""
+d1946 4
+d1953 1
+a1953 1
+msgstr ""
+d1958 1
+a1958 1
+msgstr ""
+d1962 1
+a1962 1
+msgstr ""
+d1966 1
+a1966 1
+msgstr ""
+d1972 4
+d1979 1
+a1979 1
+msgstr ""
+d1983 1
+a1983 1
+msgstr ""
+d1987 1
+a1987 1
+msgstr ""
+d1991 1
+a1991 1
+msgstr ""
+d1995 1
+a1995 1
+msgstr ""
+d1999 1
+a1999 1
+msgstr ""
+d2005 3
+d2011 1
+a2011 1
+msgstr ""
+d2015 1
+a2015 1
+msgstr ""
+d2019 1
+a2019 1
+msgstr ""
+d2023 1
+a2023 1
+msgstr ""
+d2027 1
+a2027 1
+msgstr ""
+d2033 3
+d2039 1
+a2039 1
+msgstr ""
+d2043 1
+a2043 1
+msgstr ""
+d2047 1
+a2047 1
+msgstr ""
+d2051 1
+a2051 1
+msgstr ""
+d2055 1
+a2055 1
+msgstr ""
+d2059 1
+a2059 1
+msgstr ""
+d2064 12
+d2079 1
+a2079 1
+msgstr ""
+d2083 1
+a2083 1
+msgstr ""
+d2091 1
+a2091 1
+msgstr ""
+d2095 1
+a2095 1
+msgstr ""
+d2099 1
+a2099 1
+msgstr ""
+d2103 1
+a2103 1
+msgstr ""
+d2107 1
+a2107 1
+msgstr ""
+d2111 1
+a2111 1
+msgstr ""
+d2115 1
+a2115 1
+msgstr ""
+d2119 1
+a2119 1
+msgstr ""
+d2123 1
+a2123 1
+msgstr ""
+d2127 1
+a2127 1
+msgstr ""
+d2131 1
+a2131 1
+msgstr ""
+d2137 51
+d2191 1
+a2191 1
+msgstr ""
+d2195 1
+a2195 1
+msgstr ""
+d2199 1
+a2199 1
+msgstr ""
+d2203 1
+a2203 1
+msgstr ""
+d2207 1
+a2207 1
+msgstr ""
+d2211 1
+a2211 1
+msgstr ""
+d2215 1
+a2215 1
+msgstr ""
+d2219 1
+a2219 1
+msgstr ""
+d2223 1
+a2223 1
+msgstr ""
+d2227 1
+a2227 1
+msgstr ""
+d2231 1
+a2231 1
+msgstr ""
+d2235 1
+a2235 1
+msgstr ""
+@
+
+
+1.2
+log
+ at Fixed spelling errors. Finished RH for today
+@
+text
+ at d5 1
+a5 1
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+d47 1
+a47 1
+msgstr ""
+d51 1
+a51 1
+msgstr ""
+d63 1
+a63 1
+msgstr ""
+d67 1
+a67 1
+msgstr ""
+d71 1
+a71 1
+msgstr ""
+d75 1
+a75 1
+msgstr ""
+d79 1
+a79 1
+msgstr ""
+d83 1
+a83 1
+msgstr ""
+d87 1
+a87 1
+msgstr ""
+d91 1
+a91 1
+msgstr ""
+d95 1
+a95 1
+msgstr ""
+d99 1
+a99 1
+msgstr ""
+d103 1
+a103 1
+msgstr ""
+d107 1
+a107 1
+msgstr ""
+d111 1
+a111 1
+msgstr ""
+d115 1
+a115 1
+msgstr ""
+d119 1
+a119 1
+msgstr ""
+d123 1
+a123 1
+msgstr ""
+d127 1
+a127 1
+msgstr ""
+d131 1
+a131 1
+msgstr ""
+d135 1
+a135 1
+msgstr ""
+d139 1
+a139 1
+msgstr ""
+d143 1
+a143 1
+msgstr ""
+d147 1
+a147 1
+msgstr ""
+d151 1
+a151 1
+msgstr ""
+d155 1
+a155 1
+msgstr ""
+d159 1
+a159 1
+msgstr ""
+d163 1
+a163 1
+msgstr ""
+d167 1
+a167 1
+msgstr ""
+d171 1
+a171 1
+msgstr ""
+d175 1
+a175 1
+msgstr ""
+d179 1
+a179 1
+msgstr ""
+d183 1
+a183 1
+msgstr ""
+d187 1
+a187 1
+msgstr ""
+d191 1
+a191 1
+msgstr ""
+d195 1
+a195 1
+msgstr ""
+d199 1
+a199 1
+msgstr ""
+d203 1
+a203 1
+msgstr ""
+d207 1
+a207 1
+msgstr ""
+d213 5
+d221 1
+a221 1
+msgstr ""
+d225 1
+a225 1
+msgstr ""
+d229 1
+a229 1
+msgstr ""
+d233 1
+a233 1
+msgstr ""
+d237 1
+a237 1
+msgid "\n<!--$Id: pt.po,v 1.1 2007/04/18 10:20:06 zepires Exp $ -->\n\n <chapter id=\"ch-sample\">\n <title>Sample Chapter</title>\n\n <para>This is a sample chapter, showing you the XML tags used to create a\n chapter, sections, and subsections.</para>\n \n </chapter>\n"
+d239 10
+d252 1
+a252 1
+msgstr ""
+d256 1
+a256 1
+msgstr ""
+d260 1
+a260 1
+msgstr ""
+d264 1
+a264 1
+msgstr ""
+d268 1
+a268 1
+msgstr ""
+d272 1
+a272 1
+msgstr ""
+d277 1
+a277 1
+msgstr ""
+d281 1
+a281 1
+msgstr ""
+d285 1
+a285 1
+msgstr ""
+d289 1
+a289 1
+msgstr ""
+d293 1
+a293 1
+msgstr ""
+d299 4
+d306 1
+a306 1
+msgstr ""
+d310 1
+a310 1
+msgstr ""
+d314 1
+a314 1
+msgstr ""
+d320 6
+d329 1
+a329 1
+msgstr ""
+d333 1
+a333 1
+msgstr ""
+d341 1
+a341 1
+msgstr ""
+d345 1
+a345 1
+msgstr ""
+d349 1
+a349 1
+msgstr ""
+d353 1
+a353 1
+msgstr ""
+d357 1
+a357 1
+msgstr ""
+d361 1
+a361 1
+msgstr ""
+d366 1
+a366 1
+msgstr ""
+d371 1
+a371 1
+msgstr ""
+d375 1
+a375 1
+msgstr ""
+d379 1
+a379 1
+msgstr ""
+d385 5
+d393 1
+a393 1
+msgstr ""
+d397 1
+a397 1
+msgstr ""
+d401 1
+a401 1
+msgstr ""
+d405 1
+a405 1
+msgstr ""
+d411 15
+d429 1
+a429 1
+msgstr ""
+d435 6
+d444 1
+a444 1
+msgstr ""
+d448 1
+a448 1
+msgstr ""
+d454 3
+d460 1
+a460 1
+msgstr ""
+d464 1
+a464 1
+msgstr ""
+d470 2
+d475 1
+a475 1
+msgstr ""
+d479 1
+a479 1
+msgstr ""
+d483 1
+a483 1
+msgstr ""
+d487 1
+a487 1
+msgstr ""
+d493 3
+d499 1
+a499 1
+msgstr ""
+d503 1
+a503 1
+msgstr ""
+d507 1
+a507 1
+msgstr ""
+d513 9
+d525 1
+a525 1
+msgstr ""
+d529 1
+a529 1
+msgstr ""
+d533 1
+a533 1
+msgstr ""
+d541 1
+a541 1
+msgstr ""
+d545 1
+a545 1
+msgstr ""
+d551 19
+d573 1
+a573 1
+msgstr ""
+d577 1
+a577 1
+msgstr ""
+d581 1
+a581 1
+msgstr ""
+d585 1
+a585 1
+msgstr ""
+d589 1
+a589 1
+msgstr ""
+d593 1
+a593 1
+msgstr ""
+d599 10
+d612 1
+a612 1
+msgstr ""
+d616 1
+a616 1
+msgstr ""
+d620 1
+a620 1
+msgstr ""
+d624 1
+a624 1
+msgstr ""
+d628 1
+a628 1
+msgstr ""
+d634 3
+d640 1
+a640 1
+msgstr ""
+d644 1
+a644 1
+msgstr ""
+d648 1
+a648 1
+msgstr ""
+d654 3
+d660 1
+a660 1
+msgstr ""
+d664 1
+a664 1
+msgstr ""
+d668 1
+a668 1
+msgstr ""
+d673 1
+a673 1
+msgstr ""
+d677 1
+a677 1
+msgstr ""
+d681 1
+a681 1
+msgstr ""
+d685 1
+a685 1
+msgstr ""
+d689 1
+a689 1
+msgstr ""
+d693 1
+a693 1
+msgstr ""
+d697 1
+a697 1
+msgstr ""
+d703 5
+d711 1
+a711 1
+msgstr ""
+d715 1
+a715 1
+msgstr ""
+d719 1
+a719 1
+msgstr ""
+d724 1
+a724 1
+msgstr ""
+d728 1
+a728 1
+msgstr ""
+d732 1
+a732 1
+msgstr ""
+d736 1
+a736 1
+msgstr ""
+d742 9
+d754 1
+a754 1
+msgstr ""
+d758 1
+a758 1
+msgstr ""
+d762 1
+a762 1
+msgstr ""
+d768 4
+d775 1
+a775 1
+msgstr ""
+d779 1
+a779 1
+msgstr ""
+d783 1
+a783 1
+msgstr ""
+d787 1
+a787 1
+msgstr ""
+d791 1
+a791 1
+msgstr ""
+d795 1
+a795 1
+msgstr ""
+d799 1
+a799 1
+msgstr ""
+d803 1
+a803 1
+msgstr ""
+d807 1
+a807 1
+msgstr ""
+d811 1
+a811 1
+msgstr ""
+d817 14
+d834 1
+a834 1
+msgstr ""
+d838 1
+a838 1
+msgstr ""
+d842 1
+a842 1
+msgstr ""
+d846 1
+a846 1
+msgstr ""
+d850 1
+a850 1
+msgstr ""
+d854 1
+a854 1
+msgstr ""
+d858 1
+a858 1
+msgstr ""
+d864 18
+d885 1
+a885 1
+msgstr ""
+d889 1
+a889 1
+msgstr ""
+d893 1
+a893 1
+msgstr ""
+d897 1
+a897 1
+msgstr ""
+d901 1
+a901 1
+msgstr ""
+d907 22
+d932 1
+a932 1
+msgstr ""
+d936 1
+a936 1
+msgstr ""
+d940 1
+a940 1
+msgstr ""
+d944 1
+a944 1
+msgstr ""
+d952 1
+a952 1
+msgstr ""
+d956 1
+a956 1
+msgstr ""
+d960 1
+a960 1
+msgstr ""
+d964 1
+a964 1
+msgstr ""
+d968 1
+a968 1
+msgstr ""
+d972 1
+a972 1
+msgstr ""
+d976 1
+a976 1
+msgstr ""
+d980 1
+a980 1
+msgstr ""
+d989 1
+a989 1
+msgstr ""
+d993 1
+a993 1
+msgstr ""
+d997 1
+a997 1
+msgstr ""
+d1001 1
+a1001 1
+msgstr ""
+d1005 1
+a1005 1
+msgstr ""
+d1009 1
+a1009 1
+msgstr ""
+d1013 1
+a1013 1
+msgstr ""
+d1017 1
+a1017 1
+msgstr ""
+d1021 1
+a1021 1
+msgstr ""
+d1025 1
+a1025 1
+msgstr ""
+d1029 1
+a1029 1
+msgstr ""
+d1033 1
+a1033 1
+msgstr ""
+d1037 1
+a1037 1
+msgstr ""
+d1041 1
+a1041 1
+msgstr ""
+d1045 1
+a1045 1
+msgstr ""
+d1049 1
+a1049 1
+msgstr ""
+d1053 1
+a1053 1
+msgstr ""
+d1057 1
+a1057 1
+msgstr ""
+d1061 1
+a1061 1
+msgstr ""
+d1065 1
+a1065 1
+msgstr ""
+d1069 1
+a1069 1
+msgstr ""
+d1073 1
+a1073 1
+msgstr ""
+d1079 26
+d1108 1
+a1108 1
+msgstr ""
+d1112 1
+a1112 1
+msgstr ""
+d1116 1
+a1116 1
+msgstr ""
+d1120 1
+a1120 1
+msgstr ""
+d1124 1
+a1124 1
+msgstr ""
+d1128 1
+a1128 1
+msgstr ""
+d1132 1
+a1132 1
+msgstr ""
+d1136 1
+a1136 1
+msgstr ""
+d1140 1
+a1140 1
+msgstr ""
+d1144 1
+a1144 1
+msgstr ""
+d1150 3
+d1156 1
+a1156 1
+msgstr ""
+d1160 1
+a1160 1
+msgstr ""
+d1164 1
+a1164 1
+msgstr ""
+d1168 1
+a1168 1
+msgstr ""
+d1174 5
+d1182 1
+a1182 1
+msgstr ""
+d1186 1
+a1186 1
+msgstr ""
+d1190 1
+a1190 1
+msgstr ""
+d1194 1
+a1194 1
+msgstr ""
+d1200 10
+d1213 1
+a1213 1
+msgstr ""
+d1217 1
+a1217 1
+msgstr ""
+d1221 1
+a1221 1
+msgstr ""
+d1225 1
+a1225 1
+msgstr ""
+d1231 11
+d1245 1
+a1245 1
+msgstr ""
+d1249 1
+a1249 1
+msgstr ""
+d1253 1
+a1253 1
+msgstr ""
+d1257 1
+a1257 1
+msgstr ""
+d1265 1
+a1265 1
+msgstr ""
+d1269 1
+a1269 1
+msgstr ""
+d1273 1
+a1273 1
+msgstr ""
+d1277 1
+a1277 1
+msgstr ""
+d1281 1
+a1281 1
+msgstr ""
+d1285 1
+a1285 1
+msgstr ""
+d1289 1
+a1289 1
+msgstr ""
+d1293 1
+a1293 1
+msgstr ""
+d1297 1
+a1297 1
+msgstr ""
+d1301 1
+a1301 1
+msgstr ""
+d1305 1
+a1305 1
+msgstr ""
+d1311 8
+d1322 1
+a1322 1
+msgstr ""
+d1328 9
+d1340 1
+a1340 1
+msgstr ""
+d1344 1
+a1344 1
+msgstr ""
+d1348 1
+a1348 1
+msgstr ""
+@
+
+
+1.1
+log
+ at Fixed some inconsistencies. Added documentation-guide PT translation
+@
+text
+ at d11 1
+d232 1
+a232 1
+msgid "\n<!--$Id: xml-tags.xml,v 1.5 2007/02/04 14:55:28 pfrields Exp $ -->\n\n <chapter id=\"ch-sample\">\n <title>Sample Chapter</title>\n\n <para>This is a sample chapter, showing you the XML tags used to create a\n chapter, sections, and subsections.</para>\n \n </chapter>\n"
+@
+
diff --git a/old-documentation-guide/po/pt_BR.po,v b/old-documentation-guide/po/pt_BR.po,v
new file mode 100644
index 0000000..8b54add
--- /dev/null
+++ b/old-documentation-guide/po/pt_BR.po,v
@@ -0,0 +1,11873 @@
+head 1.19;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.16
+ LIVE:1.12;
+locks; strict;
+comment @# @;
+
+
+1.19
+date 2008.05.12.06.13.11; author mdious; state Exp;
+branches;
+next 1.18;
+
+1.18
+date 2008.03.21.20.55.15; author pfonini; state Exp;
+branches;
+next 1.17;
+
+1.17
+date 2007.12.15.21.52.11; author pfrields; state Exp;
+branches;
+next 1.16;
+
+1.16
+date 2007.11.15.02.12.48; author pfrields; state Exp;
+branches;
+next 1.15;
+
+1.15
+date 2007.08.03.16.42.44; author pfrields; state Exp;
+branches;
+next 1.14;
+
+1.14
+date 2007.08.03.16.39.22; author pfrields; state Exp;
+branches;
+next 1.13;
+
+1.13
+date 2007.07.29.23.25.11; author pfrields; state Exp;
+branches;
+next 1.12;
+
+1.12
+date 2007.06.04.21.22.08; author nullck; state Exp;
+branches;
+next 1.11;
+
+1.11
+date 2007.05.28.21.02.06; author nullck; state Exp;
+branches;
+next 1.10;
+
+1.10
+date 2007.05.15.21.00.17; author nullck; state Exp;
+branches;
+next 1.9;
+
+1.9
+date 2007.05.08.22.42.16; author nullck; state Exp;
+branches;
+next 1.8;
+
+1.8
+date 2007.05.03.21.11.52; author nullck; state Exp;
+branches;
+next 1.7;
+
+1.7
+date 2007.05.02.21.18.16; author nullck; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.04.30.21.19.07; author nullck; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.04.26.21.14.11; author diegobz; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.04.26.17.53.30; author nullck; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.04.25.20.36.25; author nullck; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.04.20.20.24.22; author diegobz; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.04.20.20.22.54; author diegobz; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.19
+log
+ at updating pot and po files for noriko
+@
+text
+@# translation of pt_BR.po to
+# Diego Búrigo Zacarão <diegobz@@projetofedora.org>, 2007.
+# Nullck <nullck@@localhost.localdomain>, 2007.
+# Pedro Angelo Medeiros Fonini <pedro.fonini@@gmail.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: pt_BR\n"
+"POT-Creation-Date: 2008-05-13 02:06+1000\n"
+"PO-Revision-Date: 2008-03-21 17:49-0300\n"
+"Last-Translator: Pedro Angelo Medeiros Fonini <pedro.fonini@@gmail.com>\n"
+"Language-Team: Brazilian Portuguese <fedora-trans-pt_br@@redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-POFile-SpellExtra: pt Frields make Fox Emacs Tammy OPL Hat po Red Inc\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#: en_US/rpm-info.xml:22(rights)
+msgid "OPL"
+msgstr "OPL"
+
+#: en_US/rpm-info.xml:23(version)
+msgid "1.0"
+msgstr "1.0"
+
+#: en_US/rpm-info.xml:26(year)
+msgid "2003"
+msgstr "2003"
+
+#: en_US/rpm-info.xml:27(year)
+msgid "2004"
+msgstr "2004"
+
+#: en_US/rpm-info.xml:28(year)
+msgid "2005"
+msgstr "2005"
+
+#: en_US/rpm-info.xml:29(year)
+msgid "2006"
+msgstr "2006"
+
+#
+#: en_US/rpm-info.xml:30(year)
+msgid "2007"
+msgstr "2007"
+
+#: en_US/rpm-info.xml:31(year)
+#, fuzzy
+msgid "2008"
+msgstr "2003"
+
+#
+#: en_US/rpm-info.xml:32(holder)
+msgid "Red Hat, Inc. and others"
+msgstr "Red Hat, Inc. e outros"
+
+#: en_US/rpm-info.xml:34(title)
+msgid "Fedora Documentation Guide"
+msgstr "Guia de Documentação do Fedora"
+
+#: en_US/rpm-info.xml:35(desc)
+msgid "Guidelines and procedures for producing documentation for Fedora"
+msgstr "Instruções e procedimentos para produção da documentação para o Fedora"
+
+#: en_US/rpm-info.xml:39(details)
+msgid "Add L10n chapter (#441190)"
+msgstr ""
+
+#: en_US/rpm-info.xml:43(details)
+msgid "Fix some organization and missing targets (#371531)"
+msgstr ""
+
+#: en_US/rpm-info.xml:47(details)
+msgid "Add link to DocBook XML help for Windows"
+msgstr "Adicionado link para a ajuda do DocBook XML no Windows."
+
+#: en_US/rpm-info.xml:51(details)
+msgid "Add guidance on CVS web access and previewing work"
+msgstr "Adicionada orientação no acesso web do CVS, e na previsão do trabalho."
+
+#: en_US/rpm-info.xml:55(details)
+msgid "Add new chapter on publishing"
+msgstr "Adicionado novo capítulo sobre publicação."
+
+#: en_US/rpm-info.xml:59(details)
+msgid "Include information on LINGUAS usage"
+msgstr "Incluída informação sobre o uso do LINGUAS"
+
+#: en_US/rpm-info.xml:63(details)
+msgid "Remove unnecessary chapter on XML tags"
+msgstr "Removido capítulo desnecessário sobre tags XML"
+
+#: en_US/rpm-info.xml:67(details)
+msgid "Assorted fixes to reflect newer version of reality"
+msgstr ""
+
+#: en_US/rpm-info.xml:74(details)
+#, fuzzy
+msgid "Update to new content and build requirements"
+msgstr "Atualizado os novos requisitos de configuração"
+
+#: en_US/l10n.xml:13(title)
+msgid "Localization (L10n)"
+msgstr ""
+
+#: en_US/l10n.xml:14(para)
+msgid ""
+"This chapter discusses how translations are provided in Fedora documentation."
+msgstr ""
+
+#: en_US/l10n.xml:19(title)
+msgid "PO Files"
+msgstr ""
+
+#: en_US/l10n.xml:20(para)
+msgid ""
+"The cornerstone of translation when using XML files such as DocBook is the "
+"<firstterm>Portable Object</firstterm> or <acronym>PO</acronym> file. PO "
+"files provide a way for independent individuals or teams to translate "
+"documents. The Fedora Documentation Project toolchain includes rules for "
+"creating, updating, and maintaining these PO files."
+msgstr ""
+
+#: en_US/l10n.xml:28(para)
+msgid "PO files are usually found in two forms:"
+msgstr ""
+
+#: en_US/l10n.xml:33(para)
+msgid ""
+"the <filename class=\"extension\">.pot</filename> file, or <firstterm>PO "
+"Template</firstterm> (<acronym>POT</acronym>)"
+msgstr ""
+
+#: en_US/l10n.xml:41(para)
+msgid ""
+"the <filename class=\"extension\">.po</filename> file, or translation file "
+"(<acronym>PO</acronym>)"
+msgstr ""
+
+#: en_US/l10n.xml:47(para)
+msgid ""
+"A POT is, as the name suggests, a blank template for new translations. It "
+"contains some header information and a list of strings based on the content "
+"of the original XML file from which it was created. Translators do not alter "
+"the POT. The POT should only be changed after changes are made to the "
+"original XML file from which it is derived."
+msgstr ""
+
+#: en_US/l10n.xml:55(para)
+msgid ""
+"A translator who wishes to start working on a new language copies the POT to "
+"a locale-specific PO file. Then the translator uses any of a number of "
+"command-line or graphical tools to translate each of the strings in the "
+"list. A single POT is used to create many POs, one for each locale. These "
+"files are normally named for their locale code, such as <filename>de.po</"
+"filename>, <filename>it.po</filename>, and so on."
+msgstr ""
+
+#: en_US/l10n.xml:67(title)
+msgid "Creating or Updating a POT"
+msgstr ""
+
+#: en_US/l10n.xml:68(para)
+msgid ""
+"The POT is named after the document from which it is derived. If document "
+"named in the <filename>Makefile</filename>) is <filename>foo-tutorial.xml</"
+"filename>, the POT is named <filename>foo-tutorial.pot</filename>."
+msgstr ""
+
+#: en_US/l10n.xml:74(para)
+msgid "To create a new POT, use the following command:"
+msgstr ""
+
+#: en_US/l10n.xml:78(para)
+msgid ""
+"The same command is used to update the POT when the original XML sources "
+"change."
+msgstr ""
+
+#: en_US/l10n.xml:83(title)
+msgid "Keep POT Fresh"
+msgstr ""
+
+#: en_US/l10n.xml:84(para)
+msgid ""
+"Update the POT whenever the original XML changes. Many translators' tools "
+"automatically notify them of the change so they can update translations "
+"quickly."
+msgstr ""
+
+#: en_US/l10n.xml:92(title)
+msgid "Updating PO Files"
+msgstr ""
+
+#: en_US/l10n.xml:93(para)
+msgid ""
+"The translation files are created by the individual translators, and "
+"document maintainers do not normally need to create them. Translators update "
+"a list of locales in the <filename>po/LINGUAS</filename> file which defines "
+"all the locales for which translations exist."
+msgstr ""
+
+#: en_US/l10n.xml:100(para)
+msgid ""
+"Whenever the source XML files are updated, the maintainer must at least "
+"update the POT. It is helpful, however, to also merge these changes with the "
+"existing translations for those translators who are not automatically "
+"notified of changes."
+msgstr ""
+
+#: en_US/l10n.xml:107(title)
+msgid "Staying Current"
+msgstr ""
+
+#: en_US/l10n.xml:108(para)
+msgid ""
+"Always make sure your local copy of PO is fresh, using the CVS \"update\" "
+"command:"
+msgstr ""
+
+#: en_US/l10n.xml:114(para)
+msgid ""
+"To merge new changes into the existing PO translations, use the following "
+"command:"
+msgstr ""
+
+#: en_US/l10n.xml:121(title)
+msgid "Checking Statistics"
+msgstr ""
+
+#: en_US/l10n.xml:122(para)
+msgid "PO strings fall into three categories:"
+msgstr ""
+
+#: en_US/l10n.xml:127(para)
+msgid ""
+"<firstterm>translated</firstterm>, meaning the string has been handled by a "
+"translator and its source has not changed since then"
+msgstr ""
+
+#: en_US/l10n.xml:134(para)
+msgid ""
+"<firstterm>fuzzy</firstterm>, meaning the string has changed since it was "
+"last handled by a translator"
+msgstr ""
+
+#: en_US/l10n.xml:140(para)
+msgid ""
+"<firstterm>untranslated</firstterm>, meaning no translation has yet been "
+"provided for this string, or it is brand new"
+msgstr ""
+
+#: en_US/l10n.xml:146(para)
+msgid ""
+"To see a rough statistical tally of the string handling inside the PO for a "
+"module, use the following command:"
+msgstr ""
+
+#: en_US/l10n.xml:151(para)
+msgid ""
+"For each locale in the list, a count is shown of translated, fuzzy, and "
+"untranslated strings in that order. Tallies that only provide two numerals "
+"are usually translated followed by untranslated. Tallies with only one "
+"numeral are usually fully translated."
+msgstr ""
+
+#: en_US/l10n.xml:158(para)
+msgid ""
+"To see only a specific locale, append a dash and the locale code to the "
+"<command>postat</command> target:"
+msgstr ""
+
+#: en_US/publishing.xml:11(title)
+msgid "Publishing Official Documentation"
+msgstr "Publicando Documentação Oficial"
+
+#: en_US/publishing.xml:12(para)
+msgid ""
+"This chapter shows how to publish official Fedora Documentation Project work "
+"to the <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem> website. To publish official documentation, you must be approved "
+"to write to the web repository in CVS. Access for publishing is limited to "
+"contributors who have demonstrated capacity for working with CVS and other "
+"project tools. Once you have acquired and are comfortable with these skills, "
+"contributions as a publisher are welcome."
+msgstr ""
+"Este capítulo mostra como publicar o trabalho oficial do Projeto de "
+"Documentação do Fedora para o website <systemitem class=\"fqdomainname"
+"\">docs.fedoraproject.org</systemitem>. Para publicar documentação oficial "
+"você deve ter permissão para escrever no repositório em CVS. Acesso de "
+"publicação é limitado para contribuintes que demonstraram capacidade para "
+"trabalhar com CVS o outras ferramentas do projeto. Uma vez que você "
+"conseguiu essas habilidades e está comfortável com elas, contribuições são "
+"bem-vindas."
+
+#: en_US/publishing.xml:21(title)
+msgid "How the Site Works"
+msgstr "Como o Site Funciona"
+
+#: en_US/publishing.xml:22(para)
+msgid ""
+"The <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> "
+"website is a set of PHP files and scripts. Publishers maintain these files "
+"in a CVS repository, and the website host retrieves them hourly to refresh "
+"the site. The host does not automatically use the newest content for the "
+"website. Instead, it pulls files with the CVS tag <systemitem>LIVE</"
+"systemitem> to populate the website."
+msgstr ""
+
+#: en_US/publishing.xml:30(para)
+msgid ""
+"Each publisher sets up a local testing website on an available Fedora "
+"system. This site, sometimes called a <firstterm>sandbox</firstterm>, allows "
+"the publisher to test and view changes to documents, and ensure stability on "
+"the public site."
+msgstr ""
+
+#: en_US/publishing.xml:37(title)
+msgid "Setting Up a Web Sandbox"
+msgstr ""
+
+#: en_US/publishing.xml:38(para)
+msgid ""
+"To test document publishing, first set up a web sandbox on a local Fedora "
+"system."
+msgstr ""
+
+#: en_US/publishing.xml:42(para)
+msgid "Install the \"Web Server\" package group:"
+msgstr ""
+
+#: en_US/publishing.xml:43(screen)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Web Server\"'"
+msgstr ""
+
+#: en_US/publishing.xml:46(para)
+msgid "Create a folder for the web server to access the site files."
+msgstr ""
+
+#: en_US/publishing.xml:48(screen)
+#, no-wrap
+msgid "su -c 'mkdir /var/www/fedora'"
+msgstr ""
+
+#: en_US/publishing.xml:51(para)
+msgid ""
+"Change the permissions on this directory to make it easier to access for "
+"your normal user account."
+msgstr ""
+
+#: en_US/publishing.xml:53(replaceable) en_US/publishing.xml:62(replaceable)
+msgid "username"
+msgstr "utilizador"
+
+#: en_US/publishing.xml:53(screen)
+#, no-wrap
+msgid "su -c 'chown <placeholder-1/> /var/www/fedora'"
+msgstr ""
+
+#: en_US/publishing.xml:56(para)
+msgid "Link to the new directory from your home directory."
+msgstr ""
+
+#: en_US/publishing.xml:57(screen)
+#, no-wrap
+msgid "ln -s /var/www/fedora ~/fedora"
+msgstr ""
+
+#: en_US/publishing.xml:60(para)
+msgid "Retrieve the web module from CVS."
+msgstr ""
+
+#: en_US/publishing.xml:61(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora\n"
+"cvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+msgstr ""
+
+#: en_US/publishing.xml:64(title)
+msgid "Web CVS Access"
+msgstr ""
+
+#: en_US/publishing.xml:65(para)
+msgid ""
+"You must have access to the <systemitem>cvsweb</systemitem> module through "
+"the Fedora Account System to check in changes. If you do not have access, "
+"you can use <userinput><![CDATA[:pserver:anonymous]]></userinput> in place "
+"of <userinput><![CDATA[:ext:username]]></userinput> above. Visit the Fedora "
+"Account System at <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> "
+"for more information."
+msgstr ""
+
+#: en_US/publishing.xml:77(para)
+msgid ""
+"Edit the <filename>/etc/hosts</filename> file and add the following line "
+"<emphasis>after</emphasis> all other lines:"
+msgstr ""
+
+#: en_US/publishing.xml:80(screen)
+#, no-wrap
+msgid "127.0.0.1 docs.localhost.localdomain"
+msgstr ""
+
+#: en_US/publishing.xml:83(para)
+msgid ""
+"Create a file <filename>/etc/httpd/conf.d/fpo.conf</filename> with the "
+"following content:"
+msgstr ""
+
+#: en_US/publishing.xml:97(para)
+msgid ""
+"Create a file <filename>/etc/php.d/fpo.ini</filename> with the following "
+"content:"
+msgstr ""
+
+#: en_US/publishing.xml:99(screen)
+#, no-wrap
+msgid "include_path = \".:/var/www/fedora/web/include\""
+msgstr ""
+
+#: en_US/publishing.xml:102(para)
+msgid "Start the web server using the following command:"
+msgstr ""
+
+#: en_US/publishing.xml:103(screen)
+#, no-wrap
+msgid "su -c '/sbin/service httpd start'"
+msgstr ""
+
+#: en_US/publishing.xml:104(para)
+msgid "To have the web server start at every boot, use the following command:"
+msgstr ""
+
+#: en_US/publishing.xml:106(screen)
+#, no-wrap
+msgid "su -c '/sbin/chkconfig httpd on'"
+msgstr ""
+
+#: en_US/publishing.xml:109(para)
+msgid ""
+"To test the new sandbox site, open a Web browser and point it at the URL "
+"<uri>http://docs.localhost.localdomain</uri>."
+msgstr ""
+
+#: en_US/publishing.xml:113(title)
+msgid "Creating a New Publication"
+msgstr ""
+
+#: en_US/publishing.xml:115(title)
+msgid "General Guidelines"
+msgstr ""
+
+#: en_US/publishing.xml:116(para)
+msgid ""
+"Follow these guidelines to ensure maintainability and ease of use for all "
+"publishers."
+msgstr ""
+
+#: en_US/publishing.xml:120(para)
+msgid ""
+"Use a short, descriptive name for the document directory. The module name "
+"from its Docs CVS location is usually appropriate. Good examples include "
+"<filename class=\"directory\">install-guide/</filename> or <filename class="
+"\"directory\">example-tutorial/</filename>."
+msgstr ""
+
+#: en_US/publishing.xml:127(para)
+msgid ""
+"Under the document directory, include a branch directory if the document "
+"references specific features of a particular Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:132(para)
+msgid ""
+"Under the branch directory (or document directory if no branches are "
+"necessary), make at least a <filename class=\"directory\">en_US/</filename> "
+"directory. Make an additional directory for each locale that has been fully "
+"translated."
+msgstr ""
+
+#: en_US/publishing.xml:141(title)
+msgid "Adding Content"
+msgstr ""
+
+#: en_US/publishing.xml:142(para)
+msgid ""
+"To add content, follow the procedure below. The following commands show an "
+"example of adding content for a new document called the <citetitle>Foobar "
+"Tutorial</citetitle>. This document includes a translation for the \"zz_XX\" "
+"locale and follows specifics of each Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:149(para)
+msgid "Make the required directory structure."
+msgstr ""
+
+#: en_US/publishing.xml:150(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"mkdir foobar-tutorial\n"
+"mkdir foobar-tutorial/f7\n"
+"mkdir foobar-tutorial/f7/{en_US,zz_XX}"
+msgstr ""
+
+#: en_US/publishing.xml:156(para)
+msgid ""
+"Build the HTML version of each translation of the document from Docs CVS."
+msgstr ""
+
+#: en_US/publishing.xml:158(replaceable)
+msgid "~/my-docs/foobar-tutorial/F-7/"
+msgstr ""
+
+#: en_US/publishing.xml:158(screen)
+#, no-wrap
+msgid ""
+"cd <placeholder-1/>\n"
+"make html-en_US html-zz_XX"
+msgstr ""
+
+#: en_US/publishing.xml:162(para)
+msgid "Copy the HTML content to the web sandbox."
+msgstr ""
+
+#: en_US/publishing.xml:163(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/foobar-tutorial/f7/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/"
+msgstr ""
+
+#: en_US/publishing.xml:168(para)
+msgid ""
+"Convert the HTML in each directory to PHP using the provided "
+"<filename>docbookhtml2php.py</filename> script."
+msgstr ""
+
+#: en_US/publishing.xml:177(para)
+msgid ""
+"Create any necessary <filename>index.php</filename> files for the overall "
+"directories. Each document and branch directory must have an <filename>index."
+"php</filename> file directing users to appropriate content. In this example, "
+"the necessary files are <filename>foobar-tutorial/index.php</filename> and "
+"<filename>foobar-tutorial/f7/index.php</filename>. You do not need to write "
+"these files from scratch. Copy an existing file from another document, and "
+"change it as needed to suit the new document."
+msgstr ""
+
+#: en_US/publishing.xml:187(para)
+msgid ""
+"Depending on content, publication may include changing a higher-level "
+"<filename>index.php</filename> file."
+msgstr ""
+
+#: en_US/publishing.xml:191(para)
+msgid ""
+"To test the changes in your sandbox, open a web browser and point it at "
+"<uri>http://docs.localhost.localdomain/</uri>."
+msgstr ""
+
+#: en_US/publishing.xml:195(title)
+msgid "Always Test Changes"
+msgstr ""
+
+#: en_US/publishing.xml:196(para)
+msgid ""
+"<emphasis>Do not proceed further until you test all changes.</emphasis> "
+"Check that all links and index pages work."
+msgstr ""
+
+#: en_US/publishing.xml:204(title)
+msgid "Pushing Content to the Web"
+msgstr ""
+
+#: en_US/publishing.xml:205(para)
+msgid "To push your new content to the web site, follow this procedure:"
+msgstr ""
+
+#: en_US/publishing.xml:209(para)
+msgid "Add all the new file content to CVS."
+msgstr ""
+
+#: en_US/publishing.xml:210(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"cvs add foobar-tutorial\n"
+"cd foobar-tutorial\n"
+"cvs add f7\n"
+"cd f7\n"
+"cvs add en_US/ zz_XX/\n"
+"cvs add en_US/*php en_US/stylesheet-images/\n"
+"cvs add zz_XX/*php zz_XX/stylesheet-images/\n"
+"cvs add en_US/stylesheet-images/*png\n"
+"cvs add zz_XX/stylesheet-images/*png\n"
+"cd ../../\n"
+"cvs add foobar-tutorial/index.php\n"
+"cvs add foobar-tutorial/f7/index.php\n"
+msgstr ""
+
+#: en_US/publishing.xml:226(para)
+msgid ""
+"Commit the changes to CVS. Use a message that describes the document being "
+"committed."
+msgstr ""
+
+#: en_US/publishing.xml:228(replaceable)
+msgid "message about document"
+msgstr ""
+
+#: en_US/publishing.xml:228(screen)
+#, no-wrap
+msgid "cvs ci -m '<placeholder-1/>' foobar-tutorial/"
+msgstr ""
+
+#: en_US/publishing.xml:231(para)
+msgid "Tag the content <systemitem>LIVE</systemitem> in CVS."
+msgstr ""
+
+#: en_US/publishing.xml:233(screen)
+#, no-wrap
+msgid "cvs tag -F LIVE foobar-tutorial/"
+msgstr ""
+
+#: en_US/vim.xml:13(title)
+msgid "VIM and DocBook"
+msgstr ""
+
+#: en_US/vim.xml:16(primary) en_US/vim.xml:33(primary)
+msgid "VIM"
+msgstr ""
+
+#: en_US/vim.xml:19(para)
+msgid ""
+"VIM has many features to help you write XML content such as DocBook, "
+"including syntax highlighting and customizable key bindings. Additionally, "
+"one can easily use external programs from VIM for features such as spell-"
+"checking. This chapter assumes you already know generally how to use VIM; if "
+"you want to learn how, try the <command>vimtutor</command> or by typing "
+"<userinput>:help tutor</userinput> from inside VIM."
+msgstr ""
+
+#: en_US/vim.xml:30(title)
+msgid "Setting Up Your <filename>.vimrc</filename> File"
+msgstr ""
+
+#: en_US/vim.xml:34(secondary) en_US/emacs.xml:44(secondary)
+msgid "configuration file"
+msgstr ""
+
+#: en_US/vim.xml:37(para)
+msgid ""
+"Below is a short sample <filename>.vimrc</filename> file that turns on some "
+"VIM features useful for editing SGML or XML content such as DocBook: "
+"<screen>\n"
+"<computeroutput>\" Turn off vi compatibility settings like limited undo\n"
+"set nocompatible\n"
+"\" Syntax highlighting based on file extension\n"
+"syntax on\n"
+"\" Automatically insert newlines after 80 characters\n"
+"set textwidth=80\n"
+"\" Automatically indent\n"
+"set autoindent\n"
+"\" Match SGML tags with %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+msgstr ""
+
+#: en_US/vim.xml:55(para)
+msgid ""
+"Some of these features require the <filename>vim-enhanced</filename> package "
+"to be installed. If you are using or the <filename>vim-minimal</filename> "
+"package, or if you are using an older version of VIM, you may not have the "
+"<filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still "
+"download <ulink url=\"http://vim.org/scripts/script.php?script_id=39"
+"\">matchit.zip from Vim.org</ulink> and load it separately."
+msgstr ""
+
+#: en_US/vim.xml:69(title)
+msgid "Keymapping with VIM"
+msgstr ""
+
+#: en_US/vim.xml:71(para)
+msgid ""
+"VIM can speed up your DocBook creation by mapping frequently typed tags (or "
+"any words or phrases) onto short key combinations. By default, the keymap "
+"leader is the backslash (<literal>\\</literal>), but it can be redefined "
+"with a command like <userinput>let mapleader =\n"
+" \",\"</userinput>. There are two ways to use the following example; "
+"you can put it directly in your <filename>.vimrc</filename>, or you can save "
+"it in a separate file and load it with a <userinput>source</userinput> "
+"command in your <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\n"
+"\" skip ahead to after next tag without leaving insert mode\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\n"
+"\" common tags that start a new text block\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\n"
+"\" common tags that are placed inline\n"
+"\" use <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+"\" entities\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+msgstr ""
+
+#: en_US/vim.xml:110(para)
+msgid ""
+"Unfortunately, there is not currently a complete macro set for all DocBook "
+"commands, so you will need to define them yourself or customize the "
+"definitions in the examples from <xref linkend=\"sn-vim-additional-resources"
+"\"/>."
+msgstr ""
+
+#: en_US/vim.xml:119(title)
+msgid "Additional VIM Resources"
+msgstr ""
+
+#: en_US/vim.xml:121(para)
+msgid "Additional information about VIM may be found from:"
+msgstr ""
+
+#: en_US/vim.xml:127(para)
+msgid ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to "
+"Vi Improved (VIM)</citetitle>"
+msgstr ""
+
+#: en_US/vim.xml:134(para)
+msgid ""
+"The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick "
+"Reference Card</ulink>"
+msgstr ""
+
+#: en_US/vim.xml:140(ulink)
+msgid "Vim as XML Editor"
+msgstr ""
+
+#: en_US/vim.xml:145(para)
+msgid ""
+"The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the "
+"<filename>vim-common</filename> package —<filename>/usr/share/vim/"
+"<replaceable><version></replaceable>/doc/intro.txt</filename> or type "
+"<userinput>:help intro</userinput> from within VIM"
+msgstr ""
+
+#: en_US/tutorial.xml:13(title)
+msgid "The Layout of a Tutorial"
+msgstr ""
+
+#: en_US/tutorial.xml:14(para)
+msgid ""
+"In this chapter, you will find an example of a very short tutorial as used "
+"by the Fedora Documentation Project. This example is specific to the way the "
+"Docs Project uses DocBook XML. The example consists of a set of files used "
+"to hold the content and metadata for the tutorial."
+msgstr ""
+
+#: en_US/tutorial.xml:19(title)
+msgid "The Article"
+msgstr ""
+
+#: en_US/tutorial.xml:21(primary) en_US/tutorial.xml:56(primary)
+msgid "tutorial layout"
+msgstr ""
+
+#: en_US/tutorial.xml:22(secondary)
+msgid "article"
+msgstr ""
+
+#: en_US/tutorial.xml:24(para)
+msgid "Below is a sample article:"
+msgstr ""
+
+#: en_US/tutorial.xml:54(title)
+msgid "The Metadata"
+msgstr ""
+
+#: en_US/tutorial.xml:57(secondary)
+msgid "metadata"
+msgstr ""
+
+#: en_US/tutorial.xml:59(para)
+msgid ""
+"The <filename>rpm-info.xml</filename> file contains all the required "
+"metadata for the document. This metadata includes title, authorship, "
+"licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates "
+"the content of this file:"
+msgstr ""
+
+#: en_US/tutorial.xml:65(title)
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr ""
+
+#: en_US/tutorial.xml:95(para)
+msgid ""
+"If you are not familiar with XML editing, copy and paste this file from an "
+"existing module and then edit the values for the various elements as "
+"appropriate. Consult Fedora Documentation Project members and help channels "
+"for more assistance if needed."
+msgstr ""
+
+#: en_US/style.xml:14(title)
+msgid "Style"
+msgstr ""
+
+#: en_US/style.xml:16(para)
+msgid ""
+"Writing good technical documentation is not simply reproducing command lines "
+"and instruction sets. Good documentation is easy to read, understand, and "
+"translate, and presents a concise logical progression of concepts. Good "
+"documentation can also be defined by what it does <emphasis>not</emphasis> "
+"contain. Your tutorial should avoid:"
+msgstr ""
+
+#: en_US/style.xml:26(para)
+msgid "Excessive wordiness"
+msgstr ""
+
+#: en_US/style.xml:31(para)
+msgid "Unnecessary or undefined jargon"
+msgstr ""
+
+#: en_US/style.xml:36(para)
+msgid "Grammatical or spelling errors"
+msgstr ""
+
+#: en_US/style.xml:41(para)
+msgid "References to yourself or your experiences"
+msgstr ""
+
+#: en_US/style.xml:46(para)
+msgid "Remarks which might offend or confuse any reader"
+msgstr ""
+
+#: en_US/style.xml:51(para)
+msgid ""
+"This chapter contains style rules and guidelines for writing Fedora "
+"documentation. Guidelines are not the same as rules. It is acceptable to "
+"violate a guideline when it makes your material easier to understand. Follow "
+"guidelines whenever possible, but follow rules at all times. Assume any "
+"advice is a guideline unless identified otherwise."
+msgstr ""
+
+#: en_US/style.xml:62(title)
+msgid "Why Style Is Important"
+msgstr ""
+
+#: en_US/style.xml:64(para)
+msgid ""
+"Writing well comes naturally to almost no one. It is a skill that "
+"professional writers, even famous ones, must practice constantly. "
+"<firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> "
+"is the quality that separates elegant writing from the merely functional."
+msgstr ""
+
+#: en_US/style.xml:77(para)
+msgid ""
+"For example, refer to. <ulink url=\"http://www.online-literature.com/"
+"james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/"
+"ulysses/18/</ulink>. Please note that this example contains some mature "
+"themes and language, and is not suitable for all readers."
+msgstr ""
+
+#: en_US/style.xml:71(para)
+msgid ""
+"Elegance comes in many forms. In prose and poetry, elegant writing may not "
+"follow some (or any) common rules of grammar, syntax, or spelling. A good "
+"example is Episode 18, \"Penelope,\" in James Joyce's novel "
+"<citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long "
+"streams of words without punctuation to simulate a character's internal "
+"consciousness. By violating basic rules of grammar and syntax, Joyce "
+"simulates the disorganized but loosely connected thought patterns of the "
+"narrator."
+msgstr ""
+
+#: en_US/style.xml:89(para)
+msgid ""
+"Technical documentation, however, should always respect these rules. The "
+"more a document departs from standard language usage, the more difficult the "
+"material becomes for the reader. For example, readers may not be native "
+"speakers of the language used, or they might be reading a translation. If "
+"the writer uses slang, idioms, or jargon, a reader or translator may easily "
+"become confused. The following example compares two different written "
+"executions of the same idea:"
+msgstr ""
+
+#: en_US/style.xml:100(title)
+msgid "Incorrect style"
+msgstr ""
+
+#. I prefer "incorrect," because I think terms such as
+#. "problematic" are mealy-mouthed. They remind me of the late
+#. 1980's English textbook trend toward the politically correct yet
+#. wholly unhelpful "standard/nonstandard." But then, I tend to be
+#. dogmatic; it's probably my Catholic upbringing. [PWF]
+#: en_US/style.xml:108(para)
+msgid ""
+"So you made the changes I showed you in the last section. What's the next "
+"thing you should do? Just pop your thumb drive onto your system and read the "
+"<filename>messages</filename> log. When you see \"USB device found,\" then "
+"Bob's your uncle."
+msgstr ""
+
+#: en_US/style.xml:116(title)
+msgid "Correct style"
+msgstr ""
+
+#. I prefer "correct." See above. [PWF]
+#: en_US/style.xml:120(para)
+msgid ""
+"After you complete the configuration changes above, attach the USB removable "
+"media to your system. Use the <command>dmesg</command> command to examine "
+"the kernel message log. The message <computeroutput>USB device\n"
+"\t found</computeroutput> indicates that your device was installed "
+"successfully."
+msgstr ""
+
+#: en_US/style.xml:129(para)
+msgid ""
+"The first example is more conversational English, which is not appropriate "
+"for official written documentation. The second example is more formal, but "
+"as a result it is easier to comprehend, both for native readers and "
+"translators."
+msgstr ""
+
+#: en_US/style.xml:135(para)
+msgid ""
+"Following style rules and guidelines also makes readers more comfortable "
+"with a set of documents. Consistent style enhances the professional "
+"appearance of documentation, and its perceived value. On the other hand, "
+"lapses in punctuation or poor grammar negatively affect a reader's reaction "
+"to written material. A reader can feel that an otherwise correct technical "
+"document is lacking in authority, simply because it is poorly written. "
+"Readers feel at ease when they do not have to struggle to understand an "
+"author's use of language."
+msgstr ""
+
+#: en_US/style.xml:146(para)
+msgid ""
+"This chapter cannot possibly cover enough material to make every reader a "
+"good writer. Some manuals devoted entirely to writing style are themselves "
+"hundreds of pages long. This chapter provides enough guidelines for "
+"intermediate writers to understand style usage in technical documentation."
+msgstr ""
+
+#: en_US/style.xml:153(para)
+msgid ""
+"If you are not a practiced writer, whether of technical documentation or "
+"otherwise, you may benefit from other style resources. The following list is "
+"far from comprehensive, but provides a starting point:"
+msgstr ""
+
+#: en_US/style.xml:161(para)
+msgid ""
+"<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules "
+"and links to online versions can be found at: <ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>"
+msgstr ""
+
+#: en_US/style.xml:176(para)
+msgid ""
+"<citetitle>The Chicago Manual of Style</citetitle>, by the University of "
+"Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle."
+"org/\">http://www.chicagomanualofstyle.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:183(para)
+msgid ""
+"<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by "
+"Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/"
+"\">http://www.powa.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:190(para)
+msgid ""
+"There are many free software documentation projects which have developed "
+"their own style guidelines. This chapter, in fact, draws heavily on the "
+"<citetitle>GNOME Documentation Style Guidelines</citetitle> "
+"(<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</"
+"citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/"
+"\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr ""
+
+#: en_US/style.xml:203(title)
+msgid "Fundamental Concepts of Technical Documentation"
+msgstr ""
+
+#: en_US/style.xml:206(title)
+msgid "Bibliographic Information"
+msgstr ""
+
+#: en_US/style.xml:207(para)
+msgid "This section is drawn primarily from the <citetitle>GDSG</citetitle>."
+msgstr ""
+
+#. This section will reproduce mostly what is in Chapter 1 of
+#. the GDSG. There may be minor changes. FIXME: Make sure the
+#. appropriate front matter of the Documentation Guide includes
+#. attribution as required by the GNU FDL.
+#: en_US/style.xml:218(para)
+msgid ""
+"This chapter provides a brief introduction to writing technical "
+"documentation."
+msgstr ""
+
+#: en_US/style.xml:224(title)
+msgid "General Style Requirements"
+msgstr ""
+
+#: en_US/style.xml:225(para)
+msgid ""
+"Technical writing for the Fedora Project imposes special constraints beyond "
+"the basic requirements of good prose. Good Fedora technical documentation "
+"has the following characteristics:"
+msgstr ""
+
+#: en_US/style.xml:232(term)
+msgid "Comprehensive"
+msgstr ""
+
+#: en_US/style.xml:234(para)
+msgid ""
+"Describe all of the functionality of a product. Do not omit functionality "
+"that you regard as irrelevant for the user."
+msgstr ""
+
+#: en_US/style.xml:242(term)
+msgid "Conforming"
+msgstr ""
+
+#: en_US/style.xml:249(para)
+msgid ""
+"Describe what you see. Do not describe what you want to see. Present your "
+"information in the order that users experience the subject matter."
+msgstr ""
+
+#: en_US/style.xml:257(term)
+msgid "Clear"
+msgstr "Limpar"
+
+#: en_US/style.xml:259(para)
+msgid ""
+"Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>) to help make your writing clear."
+msgstr ""
+
+#: en_US/style.xml:275(term)
+msgid "Consistent"
+msgstr ""
+
+#: en_US/style.xml:277(para)
+msgid ""
+"Use agreed vocabulary throughout your documentation. Use the same vocabulary "
+"as other writers who are working on related documentation."
+msgstr ""
+
+#: en_US/style.xml:285(term)
+msgid "Concise"
+msgstr ""
+
+#: en_US/style.xml:287(para)
+msgid ""
+"Review your work frequently as you write your document. Ask yourself which "
+"words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for "
+"specific guidelines."
+msgstr ""
+
+#: en_US/style.xml:297(title)
+msgid "Golden Rules"
+msgstr ""
+
+#: en_US/style.xml:298(para)
+msgid ""
+"This section contains some basic style guidelines. Subsequent sections in "
+"this chapter expand on these guidelines to give more detailed guidance."
+msgstr ""
+
+#: en_US/style.xml:305(term)
+msgid "Golden Rule 1: Be brief"
+msgstr ""
+
+#: en_US/style.xml:309(para)
+msgid "Limit each sentence to fewer than 25 words."
+msgstr ""
+
+#: en_US/style.xml:314(para)
+msgid "Limit each procedure step to 23 words."
+msgstr ""
+
+#: en_US/style.xml:320(title)
+msgid "Incorrect: Too long"
+msgstr ""
+
+#: en_US/style.xml:321(para)
+msgid ""
+"Under normal operating conditions, the kernel does not always immediately "
+"write file data to the disks, storing it in a memory buffer and then "
+"periodically writing to the disks to speed up operations."
+msgstr ""
+
+#: en_US/style.xml:328(title)
+msgid "Correct: Less wordy"
+msgstr ""
+
+#: en_US/style.xml:329(para)
+msgid ""
+"Normally, the kernel stores the data in memory prior to periodically writing "
+"the data to the disk."
+msgstr ""
+
+#: en_US/style.xml:337(term)
+msgid "Golden Rule 2: Be organized"
+msgstr ""
+
+#: en_US/style.xml:341(para)
+msgid "Limit each paragraph to one topic."
+msgstr ""
+
+#: en_US/style.xml:346(para)
+msgid "Limit each sentence to one idea."
+msgstr ""
+
+#: en_US/style.xml:351(para)
+msgid "Limit each procedure step to one action."
+msgstr ""
+
+#: en_US/style.xml:357(title)
+msgid "Incorrect: Disorganized topics"
+msgstr ""
+
+#: en_US/style.xml:358(para)
+msgid ""
+"The <application>Workspace Switcher</application> applet helps you navigate "
+"all of the virtual desktops available on your system. The X Window system, "
+"working in hand with a piece of software called a <emphasis>window manager</"
+"emphasis>, allows you to create more than one virtual desktop, known as "
+"<emphasis>workspaces</emphasis>, to organize your work, with different "
+"applications running in each workspace. The <application>Workspace Switcher</"
+"application> applet is a navigational tool to get around the various "
+"workspaces, providing a miniature road map in the GNOME panel showing all "
+"your workspaces and allowing you to switch easily between them."
+msgstr ""
+
+#: en_US/style.xml:375(title)
+msgid "Correct: Organized topics"
+msgstr ""
+
+#: en_US/style.xml:376(para)
+msgid ""
+"Use the <application>Workspace Switcher</application> to add new "
+"<emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different "
+"applications in each workspace. The <application>Workspace Switcher</"
+"application> applet provides a miniature map that shows all of your "
+"workspaces. You can use the <application>Workspace Switcher</application> "
+"applet to switch between workspaces."
+msgstr ""
+
+#: en_US/style.xml:388(para)
+msgid ""
+"Plan the order of paragraphs before you start writing. Decide which topic "
+"you want to cover in each paragraph."
+msgstr ""
+
+#: en_US/style.xml:396(term)
+msgid "Golden Rule 3: Be demonstrative"
+msgstr ""
+
+#: en_US/style.xml:398(para)
+msgid ""
+"Use explicit examples to demonstrate how an application works. Provide "
+"instructions rather than descriptions."
+msgstr ""
+
+#: en_US/style.xml:403(title)
+msgid "Incorrect: Describes but does not demonstrate"
+msgstr ""
+
+#: en_US/style.xml:405(para)
+msgid ""
+"There is a text box that you can use to find out the definition of a word."
+msgstr ""
+
+#: en_US/style.xml:411(title)
+msgid "Correct: Demonstrates usage"
+msgstr ""
+
+#: en_US/style.xml:412(para)
+msgid ""
+"To request a definition of a word, type the word in the text box, then "
+"select <guilabel>Lookup</guilabel>."
+msgstr ""
+
+#: en_US/style.xml:418(para)
+msgid ""
+"Do not apply this guideline too rigidly. Sometimes you must explain how "
+"software works to support your how-to examples."
+msgstr ""
+
+#: en_US/style.xml:427(term)
+msgid "Golden Rule 4: Be objective"
+msgstr ""
+
+#: en_US/style.xml:429(para)
+msgid "Write in a neutral tone."
+msgstr ""
+
+#: en_US/style.xml:433(title)
+msgid "Incorrect: Sentence takes sides"
+msgstr ""
+
+#: en_US/style.xml:434(para)
+msgid "The applet is a handy little screen grabber."
+msgstr ""
+
+#: en_US/style.xml:439(title)
+msgid "Correct: Sentence is objective"
+msgstr ""
+
+#: en_US/style.xml:440(para)
+msgid "Use the applet to take screenshots."
+msgstr ""
+
+#: en_US/style.xml:452(title)
+msgid "Tone"
+msgstr ""
+
+#: en_US/style.xml:453(para)
+msgid ""
+"Inappropriate tone hinders reader access to information. A neutral tone free "
+"of opinion or personal flavor improves the reader's comprehension. Neutral "
+"tone helps writers to work in parallel on a large technical documentation "
+"project. Furthermore, additional writers may join the project at any time. "
+"Use of a neutral tone helps to achieve consistency across a documentation "
+"set, and thereby facilitates user access to information. The best way to "
+"achieve a common, neutral tone is to apply the following principles:"
+msgstr ""
+
+#: en_US/style.xml:466(term)
+msgid "Avoid humor"
+msgstr ""
+
+#: en_US/style.xml:468(para)
+msgid ""
+"Humor distracts from the information you are trying to provide. Humor also "
+"makes documentation difficult to translate. Stay factual."
+msgstr ""
+
+#: en_US/style.xml:476(term)
+msgid "Avoid personal opinions"
+msgstr ""
+
+#: en_US/style.xml:478(para)
+msgid ""
+"Whether you think a function is useful or woeful is irrelevant. Report the "
+"function to the user, with instructions about how to use the function. Stay "
+"accurate."
+msgstr ""
+
+#: en_US/style.xml:487(term)
+msgid "Avoid colloquial language"
+msgstr ""
+
+#: en_US/style.xml:489(para)
+msgid ""
+"Colloquial language is difficult to translate and usually culture-specific. "
+"Stay neutral."
+msgstr ""
+
+#: en_US/style.xml:496(term)
+msgid "Avoid topical expressions"
+msgstr ""
+
+#: en_US/style.xml:498(para)
+msgid ""
+"An expression that is in common use today might convey something completely "
+"different tomorrow. Stay technical."
+msgstr ""
+
+#: en_US/style.xml:505(term)
+msgid "Avoid aspirational statements"
+msgstr ""
+
+#: en_US/style.xml:507(para)
+msgid ""
+"Statements about the future developments of a product do not belong in "
+"technical documentation. Write about what you see right now. Stay real."
+msgstr ""
+
+#: en_US/style.xml:517(title)
+msgid "Reaching the Right Audience"
+msgstr ""
+
+#: en_US/style.xml:518(para)
+msgid ""
+"All of the decisions that you make about the structure and content of a "
+"manual follow from an understanding of the audience. Consider how the "
+"audience accesses the documentation, what sort of information the audience "
+"needs, and the experience level of the audience. Usually, you need to create "
+"documentation that is suitable for different audiences. The following "
+"sections introduce some of the audience-related topics you need to consider."
+msgstr ""
+
+#: en_US/style.xml:530(title)
+msgid "User Motivation"
+msgstr ""
+
+#: en_US/style.xml:531(para)
+msgid ""
+"Do not waste the time of the user who looks for information in your "
+"documentation. Users do not read technical documentation for entertainment. "
+"Users usually have specific questions. You need to give clear answers to "
+"those questions."
+msgstr ""
+
+#: en_US/style.xml:539(title)
+msgid "New Users"
+msgstr ""
+
+#: en_US/style.xml:540(para)
+msgid ""
+"New users to Fedora are likely to consult online tutorials for guidance "
+"about unfamiliar applications or functionality. Each tutorial should contain "
+"enough introductory information to tell new users how to start using the "
+"relevant functions. Each tutorial should also contain enough usage "
+"instructions to tell users the different actions that they can perform with "
+"the command or function. Keep these instructions task-oriented. Do not "
+"describe GUI screens, dialogs, and dialog elements in a tutorial, unless "
+"there is an unusual feature that affects your instructions."
+msgstr ""
+
+#: en_US/style.xml:554(title)
+msgid "Experienced Users"
+msgstr ""
+
+#: en_US/style.xml:555(para)
+msgid ""
+"Experienced users are more likely to use documentation as a reference. The "
+"documentation therefore needs to be complete, well-organized, and in the "
+"case of printed manuals, well-indexed."
+msgstr ""
+
+#: en_US/style.xml:563(title)
+msgid "Do Not Offend Your Audience"
+msgstr ""
+
+#: en_US/style.xml:564(para)
+msgid ""
+"To avoid offending your readers, apply the following guidelines to your "
+"documentation:"
+msgstr ""
+
+#: en_US/style.xml:570(term)
+msgid "Avoid insider language"
+msgstr ""
+
+#: en_US/style.xml:572(para)
+msgid ""
+"Insider language includes both undefined jargon and the tendency of the "
+"computer community to shorten words. For example, use the term "
+"<literal>documentation</literal> instead of the term <literal>docs</"
+"literal>. A term may be jargon if it fails all the following conditions:"
+msgstr ""
+
+#: en_US/style.xml:581(para)
+msgid ""
+"The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> "
+"(<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora."
+"redhat.com/docs/jargon-buster/</ulink>)."
+msgstr ""
+
+#: en_US/style.xml:588(para)
+msgid ""
+"The term does not appear in the <citetitle>American Heritage Dictionary</"
+"citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby."
+"com/61/ </ulink>)."
+msgstr ""
+
+#: en_US/style.xml:596(para)
+msgid ""
+"The term does not appear in the glossary of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:602(para)
+msgid ""
+"The term is not defined in the body text of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:611(term)
+msgid "Avoid gender-specific language"
+msgstr ""
+
+#: en_US/style.xml:613(para)
+msgid ""
+"Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</"
+"literal> do not exist. There is no need to identify gender in your "
+"instructions."
+msgstr ""
+
+#: en_US/style.xml:621(term)
+msgid "Avoid culture-specific language"
+msgstr ""
+
+#: en_US/style.xml:623(para)
+msgid ""
+"There is little point in giving an example that everyone in your town knows "
+"about, but is a complete mystery to everyone else in the world."
+msgstr ""
+
+#: en_US/style.xml:631(term)
+msgid "Avoid talking down to your reader"
+msgstr ""
+
+#: en_US/style.xml:633(para)
+msgid ""
+"There are few experiences more irritating for a user than documentation that "
+"says an action is easy or quick, when in fact the user cannot complete the "
+"action. Do not qualify or prejudge actions."
+msgstr ""
+
+#: en_US/style.xml:642(para)
+msgid ""
+"Other parts of this guide discuss in more detail tone and language usage "
+"that can cause offense."
+msgstr ""
+
+#: en_US/style.xml:653(title)
+msgid "Grammar and Usage Guidelines"
+msgstr ""
+
+#: en_US/style.xml:656(title)
+msgid "Bibliographical Information"
+msgstr ""
+
+#: en_US/style.xml:657(para)
+msgid ""
+"This section is drawn partly from the <citetitle>GDSG</citetitle>, and "
+"partly from <citetitle>The Elements of Style</citetitle>, updated as "
+"necessary for the needs of 21st-century technical documentation writers."
+msgstr ""
+
+#. FIXME: Again, check attribution viz. GNU FDL. This will be more work
+#. than the previous section.
+#: en_US/style.xml:668(para)
+msgid ""
+"This section contains an alphabetical list of grammar and usage guidelines "
+"for use in Fedora documentation. Many of these guidelines are only "
+"applicable to English-language usage, refer to the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of "
+"Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/"
+"cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:679(term)
+msgid "Abbreviations"
+msgstr ""
+
+#: en_US/style.xml:681(para)
+msgid ""
+"A shortened form of a word or phrase that takes the place of the full word "
+"or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, "
+"<literal>p.m.</literal>, and so on. Apply the following rules when you use "
+"abbreviations:"
+msgstr ""
+
+#: en_US/style.xml:689(para)
+msgid ""
+"Avoid creating new abbreviations. Unfamiliar abbreviations can confuse "
+"rather than clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:695(para)
+msgid "Do not explain or expand familiar abbreviations."
+msgstr ""
+
+#: en_US/style.xml:700(para)
+msgid "Do not include familiar abbreviations in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:706(para)
+msgid ""
+"For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other "
+"words\" and <literal>e.g.</literal> for \"for example\", do not use the "
+"abbreviation. Spell out the entire phrase."
+msgstr ""
+
+#: en_US/style.xml:715(term)
+msgid "Adjectives"
+msgstr ""
+
+#: en_US/style.xml:717(para)
+msgid ""
+"Use adjectives with caution. If an adjective is necessary to differentiate "
+"between items, then use adjectives. In all cases, test whether the phrase "
+"can stand alone without the adjective."
+msgstr ""
+
+#: en_US/style.xml:726(term)
+msgid "Acronyms"
+msgstr ""
+
+#: en_US/style.xml:728(para)
+msgid ""
+"A term that represents a multi-word term. Typically, acronyms are formed in "
+"the following ways:"
+msgstr ""
+
+#: en_US/style.xml:734(para)
+msgid ""
+"From the first letters of each word in a compound term, for example Table of "
+"Contents (TOC)."
+msgstr ""
+
+#: en_US/style.xml:740(para)
+msgid ""
+"From recognizable parts of a compound term, such as GNU Object Model "
+"Environment (GNOME)."
+msgstr ""
+
+#: en_US/style.xml:746(para)
+msgid "Apply the following rules when you use acronyms:"
+msgstr ""
+
+#: en_US/style.xml:751(para)
+msgid ""
+"On the first occurrence of an acronym, spell out the full term, with the "
+"acronym in parentheses."
+msgstr ""
+
+#: en_US/style.xml:757(para)
+msgid ""
+"Do not spell out the full compound for well-known acronyms, unless you think "
+"the information is useful for readers."
+msgstr ""
+
+#: en_US/style.xml:764(para)
+msgid ""
+"Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than "
+"clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:770(para)
+msgid ""
+"Write the acronym in uppercase letters, unless there is a compelling case "
+"for lowercase."
+msgstr ""
+
+#: en_US/style.xml:776(para)
+msgid "Include the acronym and the full term in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:785(term)
+msgid "Adverbs"
+msgstr ""
+
+#: en_US/style.xml:787(para)
+msgid ""
+"Use adverbs with caution. If an adverb is necessary to qualify the function "
+"of a component, then use an adverb. In all cases, test whether the phrase "
+"can stand alone without the adverb. Classic superfluous adverbs "
+"<literal>simply</literal>, <literal>easily</literal>, <literal>quickly</"
+"literal>."
+msgstr ""
+
+#: en_US/style.xml:798(term)
+msgid "Anthropomorphism"
+msgstr ""
+
+#: en_US/style.xml:802(para)
+msgid "Do not apply emotions, desires, or opinions to software applications."
+msgstr ""
+
+#: en_US/style.xml:808(para)
+msgid ""
+"Do not apply a sense of location or dimension to a software application. A "
+"user can not be \"in\" a text editor."
+msgstr ""
+
+#: en_US/style.xml:818(term)
+msgid "Articles"
+msgstr ""
+
+#: en_US/style.xml:820(para)
+msgid ""
+"Do not use the definite article <literal>the</literal> to begin any of the "
+"following items:"
+msgstr ""
+
+#: en_US/style.xml:826(para)
+msgid "Manual titles"
+msgstr ""
+
+#: en_US/style.xml:831(para)
+msgid "Chapter titles"
+msgstr ""
+
+#: en_US/style.xml:836(para) en_US/style.xml:1239(term)
+msgid "Headings"
+msgstr ""
+
+#: en_US/style.xml:841(para)
+msgid "Figure captions"
+msgstr ""
+
+#: en_US/style.xml:846(para)
+msgid "Table captions"
+msgstr ""
+
+#: en_US/style.xml:851(para)
+msgid "Callouts"
+msgstr ""
+
+#: en_US/style.xml:859(term)
+msgid "Apostrophe"
+msgstr ""
+
+#: en_US/style.xml:861(para)
+msgid "Do not use apostrophes except where absolutely required"
+msgstr ""
+
+#: en_US/style.xml:866(para)
+msgid "Do not use apostrophes to denote possession."
+msgstr ""
+
+#: en_US/style.xml:871(para)
+msgid "Do not use apostrophes to denote contractions."
+msgstr ""
+
+#: en_US/style.xml:876(para)
+msgid "Do not use apostrophes to denote plurals."
+msgstr ""
+
+#: en_US/style.xml:882(title)
+msgid "Incorrect: Apostrophes"
+msgstr ""
+
+#: en_US/style.xml:885(para)
+msgid ""
+"the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+msgstr ""
+
+#: en_US/style.xml:891(para)
+msgid "don't use the default option"
+msgstr ""
+
+#: en_US/style.xml:896(para)
+msgid "several SCSI disk's"
+msgstr ""
+
+#: en_US/style.xml:903(title)
+msgid "Correct: No apostrophes"
+msgstr ""
+
+#: en_US/style.xml:906(para)
+msgid ""
+"the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</"
+"guimenu>"
+msgstr ""
+
+#: en_US/style.xml:912(para)
+msgid "do not use the default option"
+msgstr ""
+
+#: en_US/style.xml:917(para)
+msgid "several SCSI disks"
+msgstr ""
+
+#: en_US/style.xml:926(term)
+msgid "Brackets"
+msgstr ""
+
+#: en_US/style.xml:930(para)
+msgid ""
+"Do not use brackets [such as these] as a substitute for parentheses (such as "
+"these)."
+msgstr ""
+
+#: en_US/style.xml:936(para)
+msgid "Use brackets for optional command line entries."
+msgstr ""
+
+#: en_US/style.xml:941(para)
+msgid ""
+"Do not use angle brackets to indicate variables in text, instead use the "
+"<sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref "
+"linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+msgstr ""
+
+#: en_US/style.xml:953(term)
+msgid "Capitalization"
+msgstr ""
+
+#: en_US/style.xml:955(para)
+msgid "Capitalize in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:960(para)
+msgid "All letters in acronyms, unless the acronym is a well-known exception"
+msgstr ""
+
+#: en_US/style.xml:966(para)
+msgid "Initial letter of the first word in a list"
+msgstr ""
+
+#: en_US/style.xml:971(para)
+msgid "Initial letter of the first word in a callout"
+msgstr ""
+
+#: en_US/style.xml:976(para)
+msgid "Initial letter of a key name, such as the <keycap>Shift</keycap> key"
+msgstr ""
+
+#: en_US/style.xml:982(para)
+msgid "Initial letter of a sentence"
+msgstr ""
+
+#: en_US/style.xml:986(title)
+msgid "Command Names"
+msgstr ""
+
+#: en_US/style.xml:987(para)
+msgid ""
+"Avoid starting a sentence with a command name or application name that has a "
+"lowercase initial letter."
+msgstr ""
+
+#: en_US/style.xml:994(para)
+msgid "Initial letter of a complete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:999(para)
+msgid "Do not capitalize in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1004(para)
+msgid "A compound term that is followed by an abbreviation or an acronym"
+msgstr ""
+
+#: en_US/style.xml:1010(para)
+msgid "When you want to emphasize something"
+msgstr ""
+
+#: en_US/style.xml:1015(para)
+msgid "Variable names"
+msgstr ""
+
+#: en_US/style.xml:1020(para)
+msgid "The initial letter of an incomplete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:1029(term)
+msgid "Captions"
+msgstr ""
+
+#: en_US/style.xml:1031(para)
+msgid ""
+"Use the same rules as for headings, for all captions accompanying figures "
+"and tables. Do not put a period at the end of a caption."
+msgstr ""
+
+#: en_US/style.xml:1039(term)
+msgid "Colon"
+msgstr ""
+
+#: en_US/style.xml:1041(para)
+msgid "Use a colon in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1046(para)
+msgid "To introduce a list"
+msgstr ""
+
+#: en_US/style.xml:1051(para)
+msgid "Before an explanation"
+msgstr ""
+
+#: en_US/style.xml:1056(para)
+msgid "After an introduction"
+msgstr ""
+
+#: en_US/style.xml:1061(para)
+msgid "Do not use a colon in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1066(para)
+msgid "To introduce a figure or a table"
+msgstr ""
+
+#: en_US/style.xml:1071(para)
+msgid "To introduce headings"
+msgstr ""
+
+#: en_US/style.xml:1076(para)
+msgid "At the end of an introduction to a procedure"
+msgstr ""
+
+#: en_US/style.xml:1084(term)
+msgid "Column headings"
+msgstr ""
+
+#: en_US/style.xml:1086(para)
+msgid "Use the same rules as for headings."
+msgstr ""
+
+#: en_US/style.xml:1092(term)
+msgid "Comma"
+msgstr ""
+
+#: en_US/style.xml:1094(para)
+msgid "Use commas in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1099(para)
+msgid "To separate items in a series"
+msgstr ""
+
+#: en_US/style.xml:1104(para)
+msgid "To separate the parts of a sentence"
+msgstr ""
+
+#: en_US/style.xml:1109(para)
+msgid "To separate nonrestrictive phrases"
+msgstr ""
+
+#: en_US/style.xml:1114(para)
+msgid "Instead of dashes to set off appositives"
+msgstr ""
+
+#: en_US/style.xml:1119(para)
+msgid "With <emphasis>for example</emphasis> and similar expressions"
+msgstr ""
+
+#: en_US/style.xml:1125(para)
+msgid "Do not use commas in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1130(para)
+msgid "In a series of adjectives used as one modifier"
+msgstr ""
+
+#: en_US/style.xml:1135(para)
+msgid "Between two short independent clauses"
+msgstr ""
+
+#: en_US/style.xml:1143(term) en_US/emacs-nxml.xml:86(title)
+msgid "Commands"
+msgstr ""
+
+#: en_US/style.xml:1145(para)
+msgid "Do not use commands as verbs."
+msgstr ""
+
+#: en_US/style.xml:1151(term)
+msgid "Contractions"
+msgstr ""
+
+#: en_US/style.xml:1153(para)
+msgid ""
+"Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</"
+"emphasis>, or <emphasis>isn't</emphasis>."
+msgstr ""
+
+#: en_US/style.xml:1160(term)
+msgid "Dash"
+msgstr ""
+
+#: en_US/style.xml:1162(para)
+msgid ""
+"Do not use the em dash or the en dash. Use a paragraph break or a colon "
+"instead, where you want to create an introductory piece of text. If you have "
+"several items that you want to introduce, then you can use a variable list."
+msgstr ""
+
+#: en_US/style.xml:1171(term)
+msgid "Ellipsis"
+msgstr ""
+
+#: en_US/style.xml:1173(para)
+msgid "Use an ellipsis in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1178(para)
+msgid "To show that you have omitted something from a sentence"
+msgstr ""
+
+#: en_US/style.xml:1183(para)
+msgid "To indicate a pause when you quote displayed text"
+msgstr ""
+
+#: en_US/style.xml:1191(term)
+msgid "Fractions"
+msgstr ""
+
+#: en_US/style.xml:1193(para)
+msgid "Follow these rules when using fractions:"
+msgstr ""
+
+#: en_US/style.xml:1198(para)
+msgid ""
+"Use numerals for fractions in tables and in units of measurement, but spell "
+"out fractions in prose."
+msgstr ""
+
+#: en_US/style.xml:1204(para)
+msgid ""
+"Use a space between a numeral and a related fraction, if there is a possible "
+"ambiguity. For example: 1 1/2 instead of 11/2."
+msgstr ""
+
+#: en_US/style.xml:1211(para)
+msgid ""
+"If a fraction is used in a compound modifier, insert a hyphen between the "
+"fraction and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1220(term)
+msgid "Gender"
+msgstr ""
+
+#: en_US/style.xml:1222(para)
+msgid "Refer to <xref linkend=\"sn-fundamentals-9\"/>."
+msgstr ""
+
+#: en_US/style.xml:1228(term)
+msgid "Grammar"
+msgstr ""
+
+#: en_US/style.xml:1230(para)
+msgid ""
+"Use standard American English grammar rules, refer to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1241(para)
+msgid "Use the following capitalization rules in headings:"
+msgstr ""
+
+#: en_US/style.xml:1246(para)
+msgid "Initial uppercase letter of the first word"
+msgstr ""
+
+#: en_US/style.xml:1251(para)
+msgid "Initial uppercase letter for all nouns, adjectives, and verbs."
+msgstr ""
+
+#: en_US/style.xml:1257(para)
+msgid ""
+"All lowercase letters for conjunctions, articles, and prepositions of fewer "
+"than four letters"
+msgstr ""
+
+#: en_US/style.xml:1263(para)
+msgid "Initial uppercase letter for prepositions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1269(para)
+msgid "Initial uppercase letter for conjunctions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1280(term)
+msgid "Hyphen"
+msgstr ""
+
+#: en_US/style.xml:1282(para)
+msgid "Use hyphens in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1287(para)
+msgid "With a numeral in a compound modifier"
+msgstr ""
+
+#: en_US/style.xml:1291(para)
+msgid "To prevent ambiguity"
+msgstr ""
+
+#: en_US/style.xml:1296(para)
+msgid ""
+"With some standard prefixes and suffixes. Use the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) for guidance"
+msgstr ""
+
+#: en_US/style.xml:1305(para)
+msgid "In spelled-out fractions"
+msgstr ""
+
+#: en_US/style.xml:1310(para)
+msgid ""
+"In variable names of two or more words, such as <replaceable>directory-name</"
+"replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+msgstr ""
+
+#: en_US/style.xml:1317(para)
+msgid "Do not use hyphens in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1322(para)
+msgid "For industry-accepted terms"
+msgstr ""
+
+#: en_US/style.xml:1327(para)
+msgid "To construct verbs"
+msgstr ""
+
+#: en_US/style.xml:1332(para)
+msgid "With an adverb ending in <emphasis>ly</emphasis>"
+msgstr ""
+
+#: en_US/style.xml:1337(para)
+msgid "With numerals as single modifiers"
+msgstr ""
+
+#: en_US/style.xml:1342(para)
+msgid ""
+"With a word that is listed as unhyphenated in the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+msgstr ""
+
+#: en_US/style.xml:1351(para)
+msgid "With trademarked terms"
+msgstr ""
+
+#: en_US/style.xml:1359(term)
+msgid "Latin terms"
+msgstr ""
+
+#: en_US/style.xml:1361(para)
+msgid "Do not use Latin terms. Use an equivalent English term instead."
+msgstr ""
+
+#: en_US/style.xml:1368(term)
+msgid "Like"
+msgstr ""
+
+#: en_US/style.xml:1370(para)
+msgid ""
+"Do not use the term <emphasis>like</emphasis> to denote equivalence or "
+"similarity."
+msgstr ""
+
+#: en_US/style.xml:1377(term)
+msgid "Lists"
+msgstr ""
+
+#: en_US/style.xml:1379(para)
+msgid "Introduce a list with a complete sentence that ends with a colon."
+msgstr ""
+
+#: en_US/style.xml:1386(term)
+msgid "Numbers"
+msgstr ""
+
+#: en_US/style.xml:1388(para)
+msgid "Spell out numbers in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1393(para)
+msgid ""
+"Numbers from zero through nine unless the number is part of a measurement"
+msgstr ""
+
+#: en_US/style.xml:1398(para)
+msgid "Approximations"
+msgstr ""
+
+#: en_US/style.xml:1403(para)
+msgid ""
+"Extreme values such as <emphasis>million</emphasis>, but precede the value "
+"with a numeral"
+msgstr ""
+
+#: en_US/style.xml:1409(para)
+msgid "Any number that begins a sentence"
+msgstr ""
+
+#: en_US/style.xml:1414(para)
+msgid ""
+"A number that is immediately followed by a numeral, for example: "
+"<literal>two 10 MB files</literal>"
+msgstr ""
+
+#: en_US/style.xml:1423(term)
+msgid "Numerals"
+msgstr ""
+
+#: en_US/style.xml:1425(para)
+msgid "Use numerals in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1430(para)
+msgid "The number 10 or greater"
+msgstr ""
+
+#: en_US/style.xml:1435(para)
+msgid "Negative numbers"
+msgstr ""
+
+#: en_US/style.xml:1439(para)
+msgid "Most fractions"
+msgstr ""
+
+#: en_US/style.xml:1444(para)
+msgid "Percentages"
+msgstr ""
+
+#: en_US/style.xml:1449(para)
+msgid "Decimals"
+msgstr ""
+
+#: en_US/style.xml:1454(para)
+msgid "Measurements"
+msgstr ""
+
+#: en_US/style.xml:1459(para)
+msgid "Units of time smaller than one second"
+msgstr ""
+
+#: en_US/style.xml:1464(para)
+msgid "References to bits and bytes"
+msgstr ""
+
+#: en_US/style.xml:1472(term)
+msgid "Parentheses"
+msgstr ""
+
+#: en_US/style.xml:1474(para)
+msgid "Use parentheses in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1479(para)
+msgid ""
+"To contain the abbreviation of a term on the first occurrence of the full "
+"term"
+msgstr ""
+
+#: en_US/style.xml:1485(para)
+msgid "In man page references, specifically the section number"
+msgstr ""
+
+#: en_US/style.xml:1493(term)
+msgid "Period"
+msgstr ""
+
+#: en_US/style.xml:1495(para)
+msgid "Use a period in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1500(para)
+msgid "To end a sentence"
+msgstr ""
+
+#: en_US/style.xml:1505(para)
+msgid "In file and directory names"
+msgstr ""
+
+#: en_US/style.xml:1510(para)
+msgid "In abbreviations that can be mistaken for words, such as a.m. and U.S."
+msgstr ""
+
+#: en_US/style.xml:1519(term)
+msgid "Punctuation"
+msgstr ""
+
+#: en_US/style.xml:1521(para)
+msgid ""
+"Use standard American English punctuation rules. In addition to the specific "
+"points of punctuation in this section, refer also to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1531(term)
+msgid "Punctuation in numbers"
+msgstr ""
+
+#: en_US/style.xml:1533(para)
+msgid ""
+"Do not use a comma in numerals of four digits. Use a comma in numerals of "
+"more than four digits."
+msgstr ""
+
+#: en_US/style.xml:1540(term)
+msgid "Quotation marks"
+msgstr ""
+
+#: en_US/style.xml:1542(para)
+msgid ""
+"Use quotation marks to indicate material that is taken verbatim from another "
+"source. Do not use quotation marks to excuse terms from legitimacy. If the "
+"term is not legitimate, then use another term. If you must use that term, "
+"declare the term in the glossary and make the term legitimate."
+msgstr ""
+
+#: en_US/style.xml:1553(term)
+msgid "See v. Refer to"
+msgstr ""
+
+#: en_US/style.xml:1555(para)
+msgid ""
+"When referring a user to another resource, use \"refer to\" instead of \"see"
+"\", and \"refer also to\" instead of \"see also\". This differentiates from "
+"the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag"
+"\">seealso</sgmltag> tags that are used in indexing. These tags create "
+"special links in the index. To be consistent throughout the document, we "
+"reserve the special words \"see\" and \"see also\" for hyperlinked index "
+"references, and use \"refer to\" and \"refer also to\" for non-hyperlinked "
+"and non-indexed references."
+msgstr ""
+
+#: en_US/style.xml:1570(term)
+msgid "Semicolon"
+msgstr ""
+
+#: en_US/style.xml:1572(para)
+msgid "Do not use semicolons."
+msgstr ""
+
+#: en_US/style.xml:1578(term)
+msgid "Slash"
+msgstr ""
+
+#: en_US/style.xml:1580(para)
+msgid ""
+"Except where required as part of a filename, do not use slashes \"/\" in "
+"your writing. The construction <literal>and/or</literal>, for example, does "
+"not exist. Use one or the other term instead."
+msgstr ""
+
+#: en_US/style.xml:1589(term)
+msgid "Spelling"
+msgstr ""
+
+#: en_US/style.xml:1591(para)
+msgid ""
+"Use standard American English spelling rules, refer to the "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+msgstr ""
+
+#: en_US/style.xml:1600(term)
+msgid "Titles"
+msgstr ""
+
+#: en_US/style.xml:1602(para)
+msgid "For manual titles use the same rules as for headings."
+msgstr ""
+
+#: en_US/style.xml:1608(term)
+msgid "Units"
+msgstr ""
+
+#: en_US/style.xml:1610(para)
+msgid "Follow these rules when using units:"
+msgstr ""
+
+#: en_US/style.xml:1615(para)
+msgid ""
+"Use standard abbreviations for units of measurements, do not invent your own "
+"abbreviations."
+msgstr ""
+
+#: en_US/style.xml:1621(para)
+msgid ""
+"For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of "
+"Electrical and Electronics Terms</citetitle>."
+msgstr ""
+
+#: en_US/style.xml:1630(para)
+msgid "Use periods for abbreviated units that might be mistaken for a word."
+msgstr ""
+
+#: en_US/style.xml:1636(para)
+msgid ""
+"Most standard abbreviations of units account for both singular and plural "
+"usage."
+msgstr ""
+
+#: en_US/style.xml:1642(para)
+msgid "Insert a space between the numeral and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1656(title)
+msgid "Composition Tips"
+msgstr ""
+
+#. This section will collect miscellanea and advice for specific
+#. situations that the FDP editors encounter. I hope they will feel
+#. free to e-mail me sticky situations or particularly interesting
+#. examples of work they've beautified. Hopefully not too much will be
+#. drawn from my own work! - PWF.
+#: en_US/style.xml:1668(para)
+msgid ""
+"This section contains usage tips based on situations the Fedora "
+"Documentation Project editors have encountered in the past. You should read "
+"and understand these examples to improve your own documentation. The Fedora "
+"Documentation Project editors welcome additional examples."
+msgstr ""
+
+#: en_US/style.xml:1676(title)
+msgid "Active Voice"
+msgstr ""
+
+#: en_US/style.xml:1677(para)
+msgid ""
+"Always use active voice, except when it is awkward to do so. The tutorial "
+"tells the user how to accomplish a task, and should give instructions "
+"clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. "
+"These words are redundant in a tutorial, since the reader assumes you are "
+"outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" "
+"\"might,\" and other words that indicate you are unsure about the subject "
+"matter. Your tutorial should cover a subject authoritatively. The reader "
+"should never be concerned about unknown effects of following the tutorial."
+msgstr ""
+
+#: en_US/style.xml:1690(title)
+msgid "Incorrect: Passive voice"
+msgstr ""
+
+#: en_US/style.xml:1691(para)
+msgid "The <command>yum update</command> command must be run."
+msgstr ""
+
+#: en_US/style.xml:1694(para)
+msgid "You might want to run the <command>yum update</command> command."
+msgstr ""
+
+#: en_US/style.xml:1700(title)
+msgid "Correct: Active voice"
+msgstr ""
+
+#: en_US/style.xml:1701(para)
+msgid "Run the <command>yum update</command> command."
+msgstr ""
+
+#: en_US/style.xml:1708(title)
+msgid "Present Tense"
+msgstr ""
+
+#: en_US/style.xml:1709(para)
+msgid ""
+"Write in the present tense. A good rule of thumb is that the words \"will\" "
+"and \"shall\" are almost never needed in describing what the user should do "
+"or see. They add unnecessary length to sentences and can confuse "
+"translators. They are also often indicators of passive voice; refer also to "
+"<xref linkend=\"sn-misc-active-voice\"/>."
+msgstr ""
+
+#: en_US/style.xml:1718(title)
+msgid "Incorrect: Future tense"
+msgstr ""
+
+#: en_US/style.xml:1719(para)
+msgid "The application will display a list of target files."
+msgstr ""
+
+#: en_US/style.xml:1722(para)
+msgid "A list of target files will be displayed by the application."
+msgstr ""
+
+#: en_US/style.xml:1727(title)
+msgid "Correct: Present tense"
+msgstr ""
+
+#: en_US/style.xml:1728(para)
+msgid "The application displays a list of target files."
+msgstr ""
+
+#: en_US/style.xml:1735(title)
+msgid "Narrative Voice"
+msgstr ""
+
+#: en_US/style.xml:1736(para)
+msgid ""
+"Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself "
+"the writer (whether including the reader or not), the Fedora Documentation "
+"Project, the Fedora community, or any other group. Do not refer to users "
+"with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word "
+"\"one.\" It is acceptable to refer to the reader with the second person "
+"pronoun \"you.\""
+msgstr ""
+
+#: en_US/style.xml:1745(title)
+msgid "Incorrect: First or third person"
+msgstr ""
+
+#: en_US/style.xml:1746(para)
+msgid ""
+"As described in the last section, I always run <command>up2date</command> "
+"before configuring the Samba server."
+msgstr ""
+
+#: en_US/style.xml:1751(para)
+msgid ""
+"If the user needs to back up his or her files, s/he should use the "
+"<command>tar</command> or <command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1757(title)
+msgid "Correct: Second (or no) person"
+msgstr ""
+
+#: en_US/style.xml:1758(para)
+msgid ""
+"Refer to the section on <command>up2date</command> before configuring the "
+"Samba server."
+msgstr ""
+
+#: en_US/style.xml:1762(para)
+msgid ""
+"If necessary, users can back up files with the <command>tar</command> or "
+"<command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1770(title)
+msgid "Negative Words"
+msgstr ""
+
+#: en_US/style.xml:1771(para)
+msgid ""
+"Avoid negative words when possible, since they give documentation an overly "
+"dogmatic tone. The word \"avoid\" is useful for this purpose. Note that "
+"contractions are often used for negative words such as <emphasis>don't</"
+"emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-"
+"contractions\"/>."
+msgstr ""
+
+#: en_US/style.xml:1782(title)
+msgid "Uncertainty"
+msgstr ""
+
+#: en_US/style.xml:1783(para)
+msgid ""
+"Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the "
+"like. While occasional use of these constructions is acceptable, overuse "
+"reduces the authority of your documentation. The documentation should "
+"adequately cover a stock installation of Fedora. It is impossible for a "
+"tutorial-length document to cover every possible configuration scenario. "
+"Address the most common scenarios and note discrepancies only as required."
+msgstr ""
+
+#: en_US/style.xml:1795(title)
+msgid "Redundant Coverage"
+msgstr ""
+
+#: en_US/style.xml:1796(para)
+msgid ""
+"Avoid covering redundant material, such as how to update a Fedora system. "
+"These overarching topics may be covered in other tutorials. Writers "
+"frequently violate this guideline because they feel their tutorial is not "
+"long enough. Keep your tutorial from wandering off-topic. Instead, refer the "
+"reader to a separate tutorial whenever possible for complete coverage of "
+"that topic."
+msgstr ""
+
+#: en_US/style.xml:1808(title)
+msgid "Self-referential Value Judgments"
+msgstr ""
+
+#: en_US/style.xml:1809(para)
+msgid ""
+"Avoid statements such as \"One of the most important things to do is "
+"<replaceable>XYZ</replaceable>.\" If the procedure is important, the reader "
+"already expects it to be in your tutorial. The converse is also true: If a "
+"procedure appears in your tutorial, the reader expects it is important. This "
+"is especially true if you use a whole section for the procedure in question. "
+"Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as "
+"required. If the whole section concerns how to do <replaceable>XYZ</"
+"replaceable>, leave this sentence out entirely. Refer also to <xref linkend="
+"\"vle-golden-rule-4\"/>."
+msgstr ""
+
+#: en_US/style.xml:1824(title)
+msgid "Precision of Language"
+msgstr ""
+
+#: en_US/style.xml:1825(para)
+msgid ""
+"Use precise words for actions users should take. Do not instruct users to "
+"\"go\" to a selection, or \"find\" a menu."
+msgstr ""
+
+#: en_US/style.xml:1830(title)
+msgid "Incorrect: Imprecise wording"
+msgstr ""
+
+#: en_US/style.xml:1833(para)
+msgid ""
+"Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+
+#: en_US/style.xml:1839(para)
+msgid "Find the option labeled <guilabel>Search</guilabel>"
+msgstr ""
+
+#: en_US/style.xml:1846(title)
+msgid "Correct: Precise wording"
+msgstr ""
+
+#: en_US/style.xml:1849(para)
+msgid ""
+"From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+
+#: en_US/style.xml:1855(para)
+msgid "Select the <guilabel>Search</guilabel> option"
+msgstr ""
+
+#: en_US/style.xml:1862(title)
+msgid "Do Not Discriminate Against Non-GUI Users"
+msgstr ""
+
+#: en_US/style.xml:1863(para)
+msgid ""
+"If you are writing about a GUI-only application, you may use \"click\" "
+"freely. If you are writing about an application that has a text-mode "
+"interface, use \"select\" instead as shown above."
+msgstr ""
+
+#: en_US/style.xml:1874(title)
+msgid "DocBook Tips"
+msgstr ""
+
+#: en_US/style.xml:1875(para)
+msgid ""
+"This section contains tips on how to use DocBook tags more effectively in "
+"your documentation."
+msgstr ""
+
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:268(title)
+msgid "Admonitions"
+msgstr ""
+
+#: en_US/style.xml:1882(para)
+msgid ""
+"Avoid overuse of admonitions. Keep admonitions short and effective by using "
+"only the most important material inside the admonition. Move any background "
+"material required to explain the admonition statements outside the "
+"admonition. Use a short but descriptive title for an admonition. Use title "
+"case for the admonition title."
+msgstr ""
+
+#: en_US/style.xml:1891(title)
+msgid "Incorrect: Lengthy admonition"
+msgstr ""
+
+#: en_US/style.xml:1894(title)
+msgid "Use <command>sfdisk</command> to check input"
+msgstr ""
+
+#: en_US/style.xml:1895(para)
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1909(title)
+msgid "Correct: Brief admonition"
+msgstr ""
+
+#: en_US/style.xml:1917(title)
+msgid "Check Input"
+msgstr ""
+
+#: en_US/style.xml:1918(para)
+msgid ""
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1910(para)
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"<placeholder-1/>"
+msgstr ""
+
+#: en_US/style.xml:1925(para)
+msgid ""
+"Avoid punctuation in titles for sections or admonitions, except for commas "
+"only where demanded. Use a title that says something about the admonition "
+"comment, such as \"Reboot Required,\" instead of simply using the admonition "
+"type for a title (\"Note\")."
+msgstr ""
+
+#: en_US/style.xml:1932(para)
+msgid ""
+"Follow the capitalization rules for headings in the title of an admonition."
+msgstr ""
+
+#: en_US/style.xml:1939(title)
+msgid "The <sgmltag class=\"starttag\">replaceable</sgmltag> Tag"
+msgstr ""
+
+#: en_US/style.xml:1941(para)
+msgid ""
+"If your documentation formally states a specific value will be used as a "
+"convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> "
+"tag in your text or examples."
+msgstr ""
+
+#: en_US/style.xml:1950(title)
+msgid "XML Entities"
+msgstr ""
+
+#: en_US/style.xml:1951(para)
+msgid ""
+"Use the entities provided by the Fedora Documentation Project. These "
+"entities are found in the <filename>common/</filename> folder in the "
+"<filename>fedora-docs</filename> distribution. (Refer also to <xref linkend="
+"\"ch-getting-files\"/>.) For instance, do not use abbreviations such as "
+"\"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" "
+"which produces the text \"Fedora 9.\""
+msgstr ""
+
+#: en_US/writing-guidelines.xml:11(title)
+msgid "Fedora Documentation Guidelines"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:14(primary)
+#: en_US/writing-guidelines.xml:15(see)
+msgid "recursion"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:19(primary)
+#: en_US/writing-guidelines.xml:26(secondary)
+msgid "RTFM"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:20(secondary)
+msgid "read the fine manual"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:21(seealso)
+#: en_US/writing-guidelines.xml:25(primary)
+msgid "humor"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:29(para)
+msgid ""
+"Please read this chapter carefully. This chapter describes the guidelines "
+"that must be followed such as naming conventions."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:32(para)
+msgid ""
+"This chapter only discusses tags used for documentation for the Fedora "
+"Project, not all available DocBook XML tags. For the complete list, refer to "
+"<ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr ""
+"Este capítulo discute somente as tag usadas para a documentação do Projeto "
+"Fedora e não todas as tags disponíveis do DocBook XML. Para a lista "
+"completa, visite <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html"
+"\"/>."
+
+#: en_US/writing-guidelines.xml:38(title)
+msgid "File Header"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:40(title)
+msgid "XML Header"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:41(para)
+msgid ""
+"In accordance with good XML practices, the first line in any DocBook XML "
+"source files should identify the file as XML. Use the following line as the "
+"first line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:47(title)
+msgid "CVS Id Header"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:48(para)
+msgid ""
+"All the files must contain the CVS Id header. Use the following line as the "
+"second line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:51(para)
+msgid ""
+"Any time the file is committed to CVS, the line is updated automatically to "
+"include information about the file. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:58(title)
+msgid "ID Naming Conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:61(primary)
+#: en_US/writing-guidelines.xml:74(primary)
+#: en_US/writing-guidelines.xml:275(primary)
+#: en_US/writing-guidelines.xml:280(primary)
+#: en_US/writing-guidelines.xml:285(primary)
+#: en_US/writing-guidelines.xml:290(primary)
+#: en_US/writing-guidelines.xml:295(primary)
+#: en_US/writing-guidelines.xml:300(primary)
+#: en_US/writing-guidelines.xml:306(primary)
+#: en_US/writing-guidelines.xml:312(primary)
+#: en_US/writing-guidelines.xml:318(primary)
+#: en_US/writing-guidelines.xml:324(primary)
+#: en_US/writing-guidelines.xml:350(primary)
+#: en_US/writing-guidelines.xml:355(primary)
+#: en_US/writing-guidelines.xml:360(primary)
+#: en_US/writing-guidelines.xml:365(primary)
+#: en_US/writing-guidelines.xml:370(primary)
+msgid "XML tags"
+msgstr "tags XML"
+
+#: en_US/writing-guidelines.xml:62(secondary)
+#: en_US/writing-guidelines.xml:66(primary)
+#: en_US/writing-guidelines.xml:79(primary)
+msgid "naming conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:69(para)
+msgid ""
+"This section explains the ID naming convention. IDs are unique identifiers "
+"that allow DocBook XML to cross-reference a section, chapter, or other "
+"element."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:75(secondary)
+#: en_US/writing-guidelines.xml:80(secondary)
+msgid "rules for defining an ID"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:83(para)
+msgid "The following general rules apply to IDs:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:87(para)
+msgid "Keep an ID as short and simple as possible."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:90(para)
+msgid ""
+"Start the ID with the special short two-character label. This makes URLs and "
+"other references to this ID human readable, by self-identifying the XML "
+"container type."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:96(para)
+msgid ""
+"<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used "
+"properly."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:102(title)
+msgid "Proper ID Usage"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:111(title)
+msgid "Two-Character Naming Conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:112(segtitle)
+msgid "Tag"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:113(segtitle)
+msgid "Prefix"
+msgstr "Prefixo"
+
+#: en_US/writing-guidelines.xml:115(sgmltag)
+msgid "preface"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:116(literal)
+msgid "pr-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:119(sgmltag)
+msgid "chapter"
+msgstr "Capitulo"
+
+#: en_US/writing-guidelines.xml:120(literal)
+msgid "ch-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:123(sgmltag)
+msgid "section"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:124(literal)
+msgid "sn-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:127(sgmltag)
+msgid "figure"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:128(literal)
+msgid "fig-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:131(sgmltag)
+#: en_US/writing-guidelines.xml:235(sgmltag)
+msgid "table"
+msgstr "table"
+
+#: en_US/writing-guidelines.xml:132(literal)
+msgid "tb-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:135(sgmltag)
+msgid "appendix"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:136(literal)
+msgid "ap-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:139(sgmltag)
+msgid "part"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:140(literal)
+msgid "pt-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:143(sgmltag)
+msgid "example"
+msgstr "exemplo"
+
+#: en_US/writing-guidelines.xml:144(literal)
+msgid "ex-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:148(para)
+msgid ""
+"Use the title of the item as the ID. Make your titles unique within a "
+"document to prevent conflicts. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:157(title)
+#, fuzzy
+msgid "XML Tags"
+msgstr "tags XML"
+
+#: en_US/writing-guidelines.xml:159(primary)
+msgid "xml tags"
+msgstr "tags xml"
+
+#: en_US/writing-guidelines.xml:160(secondary)
+msgid "caveats"
+msgstr "caveats"
+
+#: en_US/writing-guidelines.xml:163(para)
+msgid ""
+"It is very important that you remember the caveats in this section. These "
+"are learned suggestions or rules that make your XML experience better."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:171(term)
+msgid "Do Not Use Trademark Entities"
+msgstr "Não Use Entidades de Marca Registrada"
+
+#: en_US/writing-guidelines.xml:173(para)
+msgid ""
+"Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+"\"genentity\">reg</sgmltag> because the do not produce HTML output that "
+"works for all charsets. The HTML output produces by these entities are "
+"declared in the DTD and cannot be changed via the stylesheet."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:181(para)
+msgid ""
+"Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes "
+"as follows:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:184(segtitle)
+#, fuzzy
+msgid "DocBook XML source"
+msgstr "Tags do DocBook XML "
+
+#: en_US/writing-guidelines.xml:185(segtitle)
+msgid "Rendered content"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:189(trademark)
+msgid "trademark symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:196(trademark)
+msgid "registered trademark symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:202(trademark)
+msgid "copyright symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:209(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr "Conteúdo dentro de tags <sgmltag>para</sgmltag>"
+
+#: en_US/writing-guidelines.xml:211(para)
+msgid ""
+"In general, use <sgmltag>para</sgmltag> tags around anything other than a "
+"simple paragraph. Doing so will create additional white space within the "
+"text itself in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:216(para)
+msgid ""
+"Specifically, do not use <sgmltag>para</sgmltag> tags around the following "
+"(or, to put this another way, do not embed the following within <sgmltag "
+"class=\"element\">para</sgmltag> elements):"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:223(sgmltag)
+msgid "screen"
+msgstr "screen"
+
+#: en_US/writing-guidelines.xml:226(sgmltag)
+msgid "itemizedlist"
+msgstr "itemizedlist"
+
+#: en_US/writing-guidelines.xml:229(sgmltag)
+msgid "orderedlist"
+msgstr "orderedlist"
+
+#: en_US/writing-guidelines.xml:232(sgmltag)
+msgid "variablelist"
+msgstr "variablelist"
+
+#: en_US/writing-guidelines.xml:241(term)
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag>listitem</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:244(para)
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</"
+"emphasis> start immediately after the beginning <sgmltag class=\"starttag"
+"\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:252(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr "Índice dentro dos Tag de <sgmltag> screen</sgmltag>"
+
+#: en_US/writing-guidelines.xml:254(para)
+msgid ""
+"The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag"
+"\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis> be flush left in the XML file; otherwise, the "
+"extraneous whitespace will appear in the HTML version."
+msgstr ""
+"O índice dentro das<sgmltag>screen</sgmltag>tags(<sgmltag class=\"starttag"
+"\">screen</sgmltag>e<sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis>seja alinhada a esquerda na linha do XML; se não, "
+"aparecerá um espaço em branco na versão do HTML."
+
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:301(secondary)
+#: en_US/writing-guidelines.xml:307(secondary)
+#: en_US/writing-guidelines.xml:313(secondary)
+#: en_US/writing-guidelines.xml:319(secondary)
+#: en_US/writing-guidelines.xml:325(secondary)
+msgid "admonitions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:276(secondary)
+#: en_US/writing-guidelines.xml:302(tertiary)
+#: en_US/writing-guidelines.xml:371(secondary)
+msgid "warning"
+msgstr "atenção"
+
+#: en_US/writing-guidelines.xml:281(secondary)
+#: en_US/writing-guidelines.xml:308(tertiary)
+#: en_US/writing-guidelines.xml:356(secondary)
+msgid "tip"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:286(secondary)
+#: en_US/writing-guidelines.xml:314(tertiary)
+#: en_US/writing-guidelines.xml:351(secondary)
+msgid "note"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:291(secondary)
+#: en_US/writing-guidelines.xml:320(tertiary)
+#: en_US/writing-guidelines.xml:361(secondary)
+msgid "caution"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:296(secondary)
+#: en_US/writing-guidelines.xml:326(tertiary)
+#: en_US/writing-guidelines.xml:366(secondary)
+msgid "important"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:329(para)
+msgid ""
+"There are five types of admonitions in DocBook: <sgmltag class=\"element"
+"\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, "
+"<sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</"
+"sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the "
+"admonitions have the same structure: an optional <sgmltag class=\"element"
+"\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD "
+"does not impose any specific semantics on the individual admonitions. For "
+"example, DocBook does not mandate that a <sgmltag class=\"element\">warning</"
+"sgmltag> is reserved for cases where bodily harm can result."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:343(title)
+msgid ""
+"Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class="
+"\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, "
+"<sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element"
+"\">warning</sgmltag>"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:374(para)
+msgid ""
+"There are several ways to bring attention to text within a document. A "
+"<emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to "
+"bring additional information to the users' attention. A <emphasis><sgmltag "
+"class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful "
+"information or another way to do something. A <emphasis><sgmltag class="
+"\"element\">caution</sgmltag></emphasis> is used to show the user they must "
+"be careful when attempting a certain step. An <emphasis><sgmltag class="
+"\"element\">important</sgmltag></emphasis> tag set can be used to show the "
+"user a piece of information that should not be overlooked. While this "
+"information may not change anything the user is doing, it should show the "
+"user that this piece of information could be vital. A <emphasis><sgmltag "
+"class=\"element\">warning</sgmltag></emphasis> is used to show the reader "
+"that their current setup will change or be altered, such as files being "
+"removed, and they should not choose this operation unless they are alright "
+"with the consequences."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:394(para)
+msgid ""
+"The following lines of code show the basic setup for each case mentioned "
+"above, along with its appearance in HTML."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:403(title) en_US/emacs.xml:257(title)
+#: en_US/emacs.xml:562(title) en_US/emacs-nxml.xml:160(title)
+msgid "Note"
+msgstr "Nota"
+
+#: en_US/writing-guidelines.xml:404(para)
+#: en_US/writing-guidelines.xml:424(para)
+#: en_US/writing-guidelines.xml:434(para)
+#: en_US/writing-guidelines.xml:444(para)
+msgid "Body of text goes here."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:413(title) en_US/emacs-nxml.xml:114(title)
+msgid "Tip"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:414(para)
+msgid "Body of text goes here"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:423(title)
+msgid "Caution"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:433(title) en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr "Importante"
+
+#: en_US/writing-guidelines.xml:443(title)
+msgid "Warning"
+msgstr "Aviso"
+
+#: en_US/writing-guidelines.xml:451(title)
+msgid "Screenshots"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:454(primary)
+#: en_US/writing-guidelines.xml:459(see) en_US/writing-guidelines.xml:463(see)
+msgid "screenshots"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:455(secondary)
+msgid "how to take"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:458(primary)
+msgid "screen captures"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:462(primary)
+msgid "screen grabs"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:466(para)
+msgid ""
+"Screenshots are illustrations that show the state of a display the user may "
+"encounter. Screenshots can be either graphical or textual. However, "
+"screenshots use a great deal of space in a text document to convey "
+"relatively small amounts of information. The same space in the document can "
+"hold a greater amount of more descriptive and helpful information. "
+"Therefore, authors should avoid screenshots whenever possible in favor of "
+"descriptive text."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:474(para)
+msgid ""
+"One of the isolated instances in which screenshots are useful is to "
+"demonstrate a physical screen layout that is unfamiliar to a reader. "
+"<emphasis>This does not mean that illustrations of dialog boxes are good "
+"uses of screenshots.</emphasis> On the contrary, dialogs are simply "
+"instances of a user interface element with which a reader is already "
+"familiar. An annotated diagram in certain cases, however, explains to the "
+"reader where to find functional landmarks on the screen such as menu bars."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:482(para)
+msgid ""
+"The steps for taking a graphical screenshot illustrate how using text to "
+"describe a procedure is more concise than a series of screenshots."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:487(term)
+msgid "Graphical Screenshot"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:491(para)
+msgid ""
+"Create a new user account to make screenshots. The new account uses the "
+"distribution default theme, fonts, and element sizes. The resulting "
+"screenshot has an appearance familiar to the largest number of readers, and "
+"makes Fedora Documentation Project documents consistent."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:498(para)
+msgid ""
+"Before taking the screenshot, if possible, resize the targeted GUI element"
+"(s) to the smallest possible size. The target image should be 500 pixels "
+"wide or less. If the screenshot includes more than one GUI element, you may "
+"need to resize the screenshot in a following step."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:506(para)
+msgid ""
+"To take the screenshot, select the GUI element with the mouse to bring it to "
+"the forefront, or otherwise arrange the elements. Press "
+"<keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to "
+"capture a single GUI window. For capturing the entire desktop use "
+"<keycap>Print Screen</keycap>. If the shot includes multiple elements "
+"grouped closely together, crop the resulting PNG format image in "
+"<application>The GIMP</application>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:518(para)
+msgid ""
+"If necessary, resize the image using <application>The GIMP</application>. "
+"Open the image, then right-click on it and choose "
+"<menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</"
+"guimenuitem></menuchoice>. With the chain symbol intact, set the "
+"<guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click "
+"<guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</"
+"guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the "
+"image before converting it."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:534(para)
+msgid ""
+"With the image open in <application>The GIMP</application>, right-click the "
+"image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As..."
+"</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, "
+"select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</"
+"guibutton>. Allow flattening of the image by clicking <guibutton>Export</"
+"guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:545(para)
+msgid ""
+"A <guilabel>Save as PostScript</guilabel> window appears. Select "
+"<guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</"
+"guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:559(term)
+msgid "Text Screenshot"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:561(para)
+msgid ""
+"Textual screen information is also useful for readers. Follow these "
+"guidelines for textual screenshots:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:565(para)
+msgid ""
+"If a graphical screenshot illustrates a function, and the textual mode has "
+"identical functions, do not include both, unless omitting either would make "
+"your description unclear."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:571(para)
+msgid ""
+"Make the information generic over specific, and omit any username and "
+"machine information if possible. Do not include the shell prompt unless it "
+"is vital to the demonstration."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:577(para)
+msgid "Separate what the user types from sample command output."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:581(para)
+msgid ""
+"When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a "
+"procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show "
+"what the user types, and use <sgmltag class=\"element\">computeroutput</"
+"sgmltag> tags to show the resulting output."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:589(para)
+msgid ""
+"<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual "
+"screenshot usage."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:594(title)
+msgid "Correct Textual Screenshot (XML Source and HTML)"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:607(para)
+msgid ""
+"To find all the currently active ssh sessions, execute the following command:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:609(userinput)
+#, no-wrap
+msgid "ps ax | grep ssh"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:611(para)
+msgid "Output appears similar to the following:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:613(computeroutput)
+#, no-wrap
+msgid ""
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh user@@host.example.com\n"
+" 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:648(title)
+msgid "Previewing Your Work"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:649(para)
+msgid ""
+"The GNOME <application>Help</application> browser, also known as "
+"<command>yelp</command>, and the KDE <application>Khelp</application> "
+"documentation browser can render DocBook XML information as needed. Use "
+"these applications to preview your work if you prefer reading your work in a "
+"browser-like environment. Run the following command:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:656(para)
+msgid ""
+"Make sure to point the preferred help browser at the top parent file of your "
+"XML document. Once the document loads, you can add a bookmark for it for "
+"ease of use later."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:660(title)
+msgid "Using Bookmarks"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:661(para)
+msgid ""
+"Keeping your documents in the same place for every checkout session makes "
+"help browser bookmarks more effective."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:664(para)
+msgid ""
+"Once you have a bookmark stored, it will appear in the help browser at every "
+"use. You can now hit <keycap>F1</keycap> during any GUI session to launch "
+"the help browser. Then choose your bookmark from the menu to preview your "
+"document at any time."
+msgstr ""
+
+#: en_US/module-struct.xml:12(title)
+msgid "How Modules Work"
+msgstr ""
+
+#: en_US/module-struct.xml:13(para)
+msgid ""
+"Documentation modules have a specific structure that enables the "
+"preconfigured tools to work correctly. Follow this structure exactly or you "
+"may have problems building your module. The Fedora Documentation Project "
+"build tools locate resources in the module and use them to build new output "
+"such as HTML or RPM packages."
+msgstr ""
+
+#: en_US/module-struct.xml:19(title)
+msgid "Structure of a Module"
+msgstr ""
+
+#: en_US/module-struct.xml:20(para)
+msgid ""
+"<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example "
+"module, excluding any <filename class=\"directory\">CVS</filename> folders. "
+"Note that this example document does not have branches."
+msgstr ""
+
+#: en_US/module-struct.xml:25(title)
+msgid "Example Module Structure"
+msgstr ""
+
+#: en_US/module-struct.xml:47(title)
+msgid "CVS Module Contents"
+msgstr ""
+
+#: en_US/module-struct.xml:48(segtitle)
+msgid "Component"
+msgstr ""
+
+#: en_US/module-struct.xml:49(segtitle)
+msgid "Type"
+msgstr "Tipo"
+
+#: en_US/module-struct.xml:50(segtitle)
+msgid "Usage Notes"
+msgstr ""
+
+#: en_US/module-struct.xml:52(seg)
+msgid "Primary language directory"
+msgstr ""
+
+#: en_US/module-struct.xml:53(seg) en_US/module-struct.xml:94(seg)
+#: en_US/module-struct.xml:101(seg)
+msgid "required"
+msgstr ""
+
+#: en_US/module-struct.xml:56(filename)
+#: en_US/module-struct.xml:181(systemitem)
+msgid "en_US"
+msgstr "pt"
+
+#: en_US/module-struct.xml:60(firstterm)
+msgid "entities"
+msgstr ""
+
+#: en_US/module-struct.xml:61(para)
+msgid ""
+"Think of an XML entity as a predefined snippet of information. It can "
+"represent a chunk of XML source, or simply a word or character. If the "
+"information changes, it need be replaced only once, in the definition, to "
+"fix all usage."
+msgstr ""
+
+#: en_US/module-struct.xml:54(seg)
+msgid ""
+"This is the only directory absolutely required. It is named for the original "
+"language of the document, such as <placeholder-1/> (US English). The primary "
+"language does not have to be US English; all languages are supported. This "
+"directory contains all the XML source for the actual document, as well as "
+"XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr ""
+
+#: en_US/module-struct.xml:69(seg)
+msgid "Graphics directory"
+msgstr ""
+
+#: en_US/module-struct.xml:70(seg) en_US/module-struct.xml:80(seg)
+msgid "optional"
+msgstr ""
+
+#: en_US/module-struct.xml:71(filename) en_US/module-struct.xml:75(filename)
+msgid "figs/"
+msgstr ""
+
+#: en_US/module-struct.xml:71(seg)
+msgid ""
+"The <placeholder-1/> directory is an optional directory where graphics for "
+"the document should be stored. If graphics are screenshots that are "
+"particular to a language, the <placeholder-2/> directory can and should be "
+"stored in a language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:79(seg)
+msgid "Translation (PO) directory"
+msgstr ""
+
+#: en_US/module-struct.xml:81(filename) en_US/module-struct.xml:87(filename)
+msgid "po/"
+msgstr ""
+
+#: en_US/module-struct.xml:83(acronym)
+msgid "PO"
+msgstr ""
+
+#: en_US/module-struct.xml:88(filename)
+msgid "LINGUAS"
+msgstr ""
+
+#: en_US/module-struct.xml:89(firstterm)
+msgid "locales"
+msgstr ""
+
+#: en_US/module-struct.xml:81(seg)
+msgid ""
+"The <placeholder-1/> directory contains specially formatted Portable Object, "
+"or <placeholder-2/>, files created and used by translators. The Fedora "
+"Documentation Project build tools use these files to create translated "
+"versions of documents. The translated documents are not stored in CVS; they "
+"are created as needed from these PO files. The <placeholder-3/> directory "
+"also contains the <placeholder-4/> file, which lists the active translation "
+"<placeholder-5/>, or languages."
+msgstr ""
+
+#: en_US/module-struct.xml:93(seg) en_US/module-struct.xml:95(filename)
+msgid "Makefile"
+msgstr ""
+
+#: en_US/module-struct.xml:95(seg)
+msgid ""
+"The <placeholder-1/> controls the build process. Its content is discussed in "
+"<xref linkend=\"ex-makefile\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:100(filename) en_US/module-struct.xml:102(filename)
+msgid "rpm-info.xml"
+msgstr ""
+
+#: en_US/module-struct.xml:102(seg)
+msgid "The <placeholder-1/> file contains document specific metadata"
+msgstr ""
+
+#: en_US/module-struct.xml:107(title)
+msgid "Common Build Tools"
+msgstr ""
+
+#: en_US/module-struct.xml:108(para)
+msgid ""
+"Never add the <systemitem>docs-common</systemitem> build tools directory to "
+"an individual module. Special formatting in the module list downloads these "
+"tools when a user checks out a document module. For more information, refer "
+"to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:116(title)
+msgid "The Document Build System"
+msgstr ""
+
+#: en_US/module-struct.xml:121(para)
+msgid ""
+"In Linux and Fedora documentation, references to commands often include a "
+"number inside parentheses. This number represents the section of "
+"<firstterm>manpages</firstterm> that includes documentation for that "
+"command. To read the manpage for <command>make(1)</command>, use the command "
+"<command>man 1 make</command>."
+msgstr ""
+
+#: en_US/module-struct.xml:117(para)
+msgid ""
+"The build system can render the document into another format such as "
+"<abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</"
+"command><placeholder-1/> and shell scripts. Authors need <emphasis>no</"
+"emphasis> prior experience with either shell scripts or a <command>make(1)</"
+"command>."
+msgstr ""
+
+#: en_US/module-struct.xml:133(title)
+msgid "The Document <filename>Makefile</filename>"
+msgstr ""
+
+#: en_US/module-struct.xml:134(para)
+msgid ""
+"Each individual document has its own <filename>Makefile</filename>, which "
+"only needs to be a few lines long. The document <filename>Makefile</"
+"filename> content is designed for cut and paste operations."
+msgstr ""
+
+#: en_US/module-struct.xml:140(para)
+msgid ""
+"<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</"
+"filename> for a simple document with two files and two translations."
+msgstr ""
+
+#: en_US/module-struct.xml:146(title)
+msgid "Sample Document Makefile"
+msgstr ""
+
+#: en_US/module-struct.xml:162(para)
+msgid ""
+"Do not be concerned with some of the more complicated syntax such as the "
+"<command>XMLFILES_template</command> stanza. An explanation for this "
+"template appears a few paragraphs below."
+msgstr ""
+
+#: en_US/module-struct.xml:168(title)
+msgid "Makefile Variables"
+msgstr ""
+
+#: en_US/module-struct.xml:169(segtitle)
+msgid "Variable"
+msgstr ""
+
+#: en_US/module-struct.xml:170(segtitle) en_US/module-struct.xml:240(segtitle)
+msgid "Explanation"
+msgstr ""
+
+#: en_US/module-struct.xml:172(systemitem)
+msgid "DOCBASE"
+msgstr ""
+
+#: en_US/module-struct.xml:173(seg)
+msgid ""
+"This variable contains the name for the main (parent) XML document. Follow "
+"convention by naming your document after the module name."
+msgstr ""
+
+#: en_US/module-struct.xml:178(systemitem)
+msgid "PRI_LANG"
+msgstr ""
+
+#: en_US/module-struct.xml:179(seg)
+msgid ""
+"This variable contains the ISO code for the original version of the "
+"document, such as <placeholder-1/>."
+msgstr ""
+
+#: en_US/module-struct.xml:184(systemitem)
+msgid "DOC_ENTITIES"
+msgstr ""
+
+#: en_US/module-struct.xml:185(seg)
+msgid ""
+"This variable contains a listing of any files containing entity definitions. "
+"The Fedora Documentation Project uses a special XML format to record "
+"document-specific entities, so they can be translated and built on the fly "
+"like any other XML document. An example is shown later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:194(systemitem)
+msgid "XMLFILES_template"
+msgstr ""
+
+#: en_US/module-struct.xml:197(systemitem)
+msgid "${1}"
+msgstr ""
+
+#: en_US/module-struct.xml:202(systemitem)
+msgid "${1}/"
+msgstr ""
+
+#: en_US/module-struct.xml:195(seg)
+msgid ""
+"This template allows the build tools to work with the document in multiple "
+"languages once it is translated. The <placeholder-1/> marking is a variable "
+"used to substitute the appropriate language. This template is not terribly "
+"complicated. For a new module, duplicate this section exactly except for the "
+"actual filenames. Prepend the text <placeholder-2/>, in place of the "
+"language code directory name, to each filename in your document."
+msgstr ""
+
+#: en_US/module-struct.xml:208(title)
+msgid "Files Exempt From Listing"
+msgstr ""
+
+#: en_US/module-struct.xml:209(para)
+msgid ""
+"Do not include the document-specific entities XML file or the <filename>rpm-"
+"info.xml</filename> file, which will be discussed later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:213(para)
+msgid ""
+"The final section, beginning with <literal>define</literal>, locates the "
+"main <filename>Makefile.common</filename> for the build system. This "
+"<filename>Makefile.common</filename> file contains all the <application>make"
+"(1)</application> targets and rules to actually build the document and the "
+"various archives."
+msgstr ""
+
+#: en_US/module-struct.xml:222(title)
+msgid "The Document <filename>rpm-info.xml</filename>"
+msgstr ""
+
+#: en_US/module-struct.xml:223(para)
+msgid ""
+"Each document module's primary language directory contains a file called "
+"<filename>rpm-info.xml</filename>. This file contains document-specific "
+"metadata used to generate revision history, copyright, and contributor "
+"information. It follows a DTD specification included with the rest of the "
+"build system tools."
+msgstr ""
+
+#: en_US/module-struct.xml:232(title)
+msgid "Build System Actions"
+msgstr ""
+
+#: en_US/module-struct.xml:233(para)
+msgid ""
+"To render the <abbrev>XML</abbrev> document into another format, use one of "
+"the following <command>make</command> targets:"
+msgstr ""
+
+#: en_US/module-struct.xml:238(title)
+msgid "Build Targets"
+msgstr ""
+
+#: en_US/module-struct.xml:239(segtitle)
+msgid "Target"
+msgstr ""
+
+#: en_US/module-struct.xml:242(systemitem)
+msgid "help"
+msgstr ""
+
+#: en_US/module-struct.xml:243(seg)
+msgid "This target prints a list of available targets and their descriptions."
+msgstr ""
+
+#: en_US/module-struct.xml:247(systemitem)
+msgid "validate-xml"
+msgstr ""
+
+#: en_US/module-struct.xml:248(firstterm)
+msgid "validates"
+msgstr ""
+
+#: en_US/module-struct.xml:248(seg)
+msgid ""
+"This target <placeholder-1/> the XML files to make sure they are not only "
+"well-formed, but follow the DTD. Some viewers of XML documents may not work "
+"correctly until you run this target. This target includes copying required "
+"entity files so that validating XML viewers work properly"
+msgstr ""
+
+#: en_US/module-struct.xml:256(systemitem)
+msgid "html"
+msgstr ""
+
+#: en_US/module-struct.xml:257(abbrev) en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:293(abbrev) en_US/module-struct.xml:298(abbrev)
+msgid "HTML"
+msgstr ""
+
+#: en_US/module-struct.xml:261(systemitem)
+#: en_US/module-struct.xml:271(systemitem)
+msgid "${DOCBASE}"
+msgstr ""
+
+#: en_US/module-struct.xml:262(systemitem)
+#: en_US/module-struct.xml:272(systemitem)
+msgid "${LANG}"
+msgstr ""
+
+#: en_US/module-struct.xml:260(filename)
+msgid "<placeholder-1/>-<placeholder-2/>/"
+msgstr ""
+
+#: en_US/module-struct.xml:257(seg)
+msgid ""
+"This target builds the \"chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a separate directory named "
+"<placeholder-2/>. Each document section is a separate file within that "
+"directory."
+msgstr ""
+
+#: en_US/module-struct.xml:267(systemitem)
+msgid "html-nochunks"
+msgstr ""
+
+#: en_US/module-struct.xml:270(filename)
+msgid "<placeholder-1/>-<placeholder-2/>.html"
+msgstr ""
+
+#: en_US/module-struct.xml:268(seg)
+msgid ""
+"This target builds the \"non-chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a single file: <placeholder-2/>; no "
+"other files are created."
+msgstr ""
+
+#: en_US/module-struct.xml:276(systemitem)
+msgid "pdf"
+msgstr ""
+
+#: en_US/module-struct.xml:277(abbrev) en_US/module-struct.xml:278(abbrev)
+#: en_US/module-struct.xml:294(abbrev) en_US/module-struct.xml:299(abbrev)
+msgid "PDF"
+msgstr ""
+
+#: en_US/module-struct.xml:277(seg)
+msgid ""
+"This target builds only the <placeholder-1/> document for all document "
+"languages. <placeholder-2/> production is currently erratic and may not work "
+"for your document."
+msgstr ""
+
+#: en_US/module-struct.xml:282(systemitem)
+msgid "tarball"
+msgstr ""
+
+#: en_US/module-struct.xml:283(command)
+msgid "tar(1)"
+msgstr ""
+
+#: en_US/module-struct.xml:283(seg)
+msgid ""
+"This target builds only the <placeholder-1/> archive for all document "
+"languages."
+msgstr ""
+
+#: en_US/module-struct.xml:287(systemitem)
+msgid "all"
+msgstr "tudo"
+
+#: en_US/module-struct.xml:288(seg)
+msgid "This target builds all targets listed above."
+msgstr ""
+
+#: en_US/module-struct.xml:291(systemitem)
+#: en_US/module-struct.xml:300(filename)
+msgid "clean"
+msgstr ""
+
+#: en_US/module-struct.xml:293(emphasis)
+msgid "not"
+msgstr ""
+
+#: en_US/module-struct.xml:292(seg)
+msgid ""
+"This target deletes any temporary, or generated files, but does <placeholder-"
+"1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr ""
+
+#: en_US/module-struct.xml:297(systemitem)
+msgid "distclean"
+msgstr ""
+
+#: en_US/module-struct.xml:298(seg)
+msgid ""
+"This target erases all <placeholder-1/>, <placeholder-2/>, and archive "
+"files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr ""
+
+#: en_US/module-struct.xml:305(title)
+msgid "PDF Generation is Erratic"
+msgstr ""
+
+#: en_US/module-struct.xml:306(para)
+msgid ""
+"<abbrev>PDF</abbrev> production is currently erratic and may not work for "
+"your document."
+msgstr ""
+
+#: en_US/module-struct.xml:311(title)
+msgid "Adding or Changing Targets"
+msgstr ""
+
+#: en_US/module-struct.xml:312(para)
+msgid ""
+"To add a new target and rules, place them at the bottom of the document "
+"<filename>Makefile</filename>, below the <literal>include</literal> line. "
+"Follow your target definitions with a double colon, not a single colon. The "
+"double colon allows you to specify additional rules for existing targets, or "
+"to write rules for a new target."
+msgstr ""
+
+#: en_US/module-struct.xml:320(para)
+msgid ""
+"For more information on using <command>make(1)</command>, consult the online "
+"documentation with the command <command>info make</command> in a terminal."
+msgstr ""
+
+#: en_US/module-struct.xml:327(title)
+msgid "Using Document Image Files"
+msgstr ""
+
+#: en_US/module-struct.xml:328(para)
+msgid ""
+"Tutorial documents often make use of images such as <filename class="
+"\"extension\">.PNG</filename> files. Store image files in a <filename class="
+"\"directory\">figs/</filename> folder in the main module directory, as shown "
+"in <xref linkend=\"ex-module-structure\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:335(para)
+msgid ""
+"Depending on the output media, sometimes images may be scaled, streteched, "
+"or squashed. To minimize any distortions, we recommend that you use only "
+"<filename class=\"extension\">.PNG</filename> images. Avoid <filename class="
+"\"extension\">.JPG</filename> files. The <command>convert(1)</command> "
+"program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</"
+"abbrev> package, provides a convenient way to reformat <filename class="
+"\"extension\">.JPG</filename> images into <filename class=\"extension\">."
+"PNG</filename> format. For more information on formatting images such as "
+"screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:349(para)
+msgid ""
+"Image files may be organized into subdirectories under <filename>figs/</"
+"filename> if necessary. The document building system recreates the image "
+"subdirectory structure in the output documents."
+msgstr ""
+
+#: en_US/module-struct.xml:355(para)
+msgid ""
+"Images often contain labels or other text which may need to be localized. A "
+"screenshot of a program, for example, may require a version for each "
+"translated language. Name language-dependent image files such as program "
+"screenshots by adding the language code to the filename, such as "
+"<filename>menu-en_US.png</filename>. Language-independent images, such as "
+"<filename>icon.png</filename>, do not need language codes."
+msgstr ""
+
+#: en_US/module-struct.xml:365(para)
+msgid ""
+"Sometimes, a document may require images that do not follow the naming "
+"convention. To use these images with the document building system, create an "
+"ordinary text file containing the image filenames. This file must be named "
+"<filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</"
+"systemitem> so the build system finds it when searching for image filenames."
+msgstr ""
+
+#: en_US/module-struct.xml:374(para)
+msgid ""
+"<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one "
+"way to create this <filename>Manifest</filename> file."
+msgstr ""
+
+#: en_US/module-struct.xml:380(title)
+msgid "Building A Manifest"
+msgstr ""
+
+#: en_US/module-struct.xml:387(title)
+msgid "Adding a New DocBook XML File"
+msgstr ""
+
+#: en_US/module-struct.xml:388(para)
+msgid ""
+"To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:392(para)
+msgid "Place the new DocBook XML file in the primary language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:396(para)
+msgid ""
+"Edit the <filename>Makefile</filename> and add the filename to the "
+"<varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to "
+"the last existing line, and on the next line add an entry for the new file. "
+"Remember to add the <literal>${1}/</literal> prefix as a substitute for the "
+"language directory name."
+msgstr ""
+
+#: en_US/module-struct.xml:406(title)
+msgid "Adding a Translation"
+msgstr ""
+
+#: en_US/module-struct.xml:407(para)
+msgid ""
+"Translations are stored as PO (portable object) files, which the toolchain "
+"transforms into translated documents. Each PO file is based on the POT (PO "
+"template) for the document and translated by the Fedora Translation Project. "
+"To add a translation, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:414(para)
+msgid ""
+"If the <filename class=\"directory\">po/</filename> directory does not "
+"exist, create it and add it to CVS:"
+msgstr ""
+
+#: en_US/module-struct.xml:420(para)
+msgid "If it does not exist, create the POT file:"
+msgstr ""
+
+#: en_US/module-struct.xml:424(para)
+msgid ""
+"Add the new translation language to the <varname>OTHERS</varname> listing in "
+"the <filename>Makefile</filename>."
+msgstr ""
+
+#: en_US/module-struct.xml:429(para)
+msgid ""
+"Although translators often copy the POT manually to create the new PO file, "
+"the following command also works:"
+msgstr ""
+
+#: en_US/module-struct.xml:432(replaceable)
+msgid "lang"
+msgstr "língua"
+
+#: en_US/module-struct.xml:432(screen)
+#, no-wrap
+msgid "make po/<placeholder-1/>.po"
+msgstr "make po/<placeholder-1/>.po"
+
+#: en_US/intro.xml:13(title)
+msgid "Introduction"
+msgstr "Introdução"
+
+#: en_US/intro.xml:15(para)
+msgid ""
+"The goal of the Fedora Documentation Project is to create easy-to-follow, "
+"task-based documentation for Fedora users and developers. The Fedora "
+"Documentation Project uses the following tools:"
+msgstr ""
+
+#: en_US/intro.xml:23(para)
+msgid "DocBook XML v4.4"
+msgstr ""
+
+#: en_US/intro.xml:26(para)
+msgid "Custom XSLT stylesheets for both print and HTML versions"
+msgstr ""
+
+#: en_US/intro.xml:30(para)
+msgid "Custom scripts to generate HTML output (use <command>xmlto</command>)"
+msgstr ""
+
+#: en_US/intro.xml:34(para)
+msgid "Emacs with PSGML mode (optional, but recommended)"
+msgstr ""
+
+#: en_US/intro.xml:43(para)
+msgid ""
+"This document explains the tools used by the Fedora Documentation Project. "
+"It provides writing and tagging guidelines to ensure Fedora documentation is "
+"consistent and easy-to-follow."
+msgstr ""
+
+#: en_US/getting-files.xml:12(title)
+msgid "Prerequisites"
+msgstr ""
+
+#: en_US/getting-files.xml:14(para)
+msgid ""
+"To work on official Fedora documentation you need to install the required "
+"tools. Follow the directions below to configure your system."
+msgstr ""
+
+#: en_US/getting-files.xml:20(title)
+msgid "System Packages"
+msgstr "Pacotes do Sistema"
+
+#: en_US/getting-files.xml:22(para)
+msgid ""
+"Install the \"Authoring and Publishing\" package group, which contains "
+"required DocBook XML files, stylesheets and scripts:"
+msgstr ""
+
+#: en_US/getting-files.xml:28(userinput)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+msgstr ""
+
+#: en_US/getting-files.xml:31(para)
+msgid ""
+"Next, install the <filename>cvs</filename> package, which is used to handle "
+"revision control on files in the official repository:"
+msgstr ""
+
+#: en_US/getting-files.xml:37(userinput)
+#, no-wrap
+msgid "su -c 'yum install cvs'"
+msgstr ""
+
+#: en_US/getting-files.xml:40(para)
+msgid ""
+"If you plan to use <application>Emacs</application> to edit DocBook XML "
+"documentation, install <package>psgml</package>, which adds helpful and time-"
+"saving functionality to maximize editing efficiency:"
+msgstr ""
+
+#: en_US/getting-files.xml:44(userinput)
+#, no-wrap
+msgid "su -c 'yum install psgml'"
+msgstr ""
+
+#: en_US/getting-files.xml:48(title)
+msgid "Fedora Documentation Tools"
+msgstr ""
+
+#: en_US/getting-files.xml:50(para)
+msgid ""
+"The Fedora Documentation Project's custom scripts and stylesheets are stored "
+"in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</"
+"systemitem> CVS server. When you check out a document module from CVS, the "
+"tools are included in the module inside the <filename class=\"directory"
+"\">docs-common/</filename> directory. To work on existing documents in CVS, "
+"refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:59(para)
+msgid ""
+"The most powerful component in the Fedora Documentation Project toolbox is "
+"<firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for "
+"authoring technical documentation using <firstterm>Extensible Markup "
+"Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark "
+"pieces of content with descriptive tags. The following output is an example "
+"of DocBook XML:"
+msgstr ""
+
+#: en_US/getting-files.xml:76(para)
+msgid ""
+"This example article, entitled <citetitle>A Very Short Article</citetitle>, "
+"consists of only a single paragraph. The tags, or markup, surround elements "
+"of content to define the sense in which they are used. A paragraph, for "
+"example, is marked with <sgmltag>para</sgmltag> tags. Text that requires "
+"emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does "
+"not worry about the visual formatting such as italics or font size. Fedora "
+"Documentation Project build tools automatically perform all formatting tasks."
+msgstr ""
+
+#: en_US/getting-files.xml:85(para)
+msgid ""
+"The custom tools built by the Fedora Documentation Project render DocBook "
+"source into a variety of formats for publication and distribution. They also "
+"allow translators to create localized versions of the XML documents for "
+"Fedora users around the world. The flexibility of XML allows for a single "
+"document to be used many times for many purposes, like reusable code for a "
+"programmer."
+msgstr ""
+
+#: en_US/getting-files.xml:91(para)
+msgid ""
+"DocBook is itself very well documented. For more information about DocBook, "
+"visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also "
+"features complete copies of <citetitle>DocBook: The Definitive Guide</"
+"citetitle> to browse and download, the canonical source for DocBook "
+"information."
+msgstr ""
+
+#: en_US/getting-files.xml:97(title)
+#, fuzzy
+msgid "DocBook XML Versions"
+msgstr "Tags do DocBook XML "
+
+#: en_US/getting-files.xml:98(para)
+msgid ""
+"DocBook XML, like a computer program, has version numbers. The version used "
+"by Fedora Documentation Project right now is 4.4. The DocBook web site may "
+"document a slightly newer version, but the majority of the schema still "
+"applies."
+msgstr ""
+
+#: en_US/getting-files.xml:103(para)
+msgid ""
+"Contributors who use the Microsoft Windows operating system can still make "
+"use of DocBook tools. For more information, refer to <ulink url=\"http://www."
+"codeproject.com/winhelp/docbook_howto.asp\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:110(title)
+msgid "Naming Conventions"
+msgstr ""
+
+#: en_US/getting-files.xml:111(para)
+msgid ""
+"The Fedora Documentation Project provides the tools, scripts, and "
+"stylesheets to transform your <abbrev>XML</abbrev> documents into other "
+"output formats such as <abbrev>HTML</abbrev>. In addition, these tools can "
+"build your document into a <abbrev>RPM</abbrev> package. To take advantage "
+"of these services, follow the conventions in this section to name your files."
+msgstr ""
+
+#: en_US/getting-files.xml:119(para)
+msgid ""
+"On the CVS server, directories that contain document files are called "
+"<firstterm>modules</firstterm>. Each module represents a single document. "
+"Each document may consist of several <firstterm>branches</firstterm> if that "
+"document changes with each release of Fedora. Contributors can check out "
+"single branches of these modules or the entire module. Each document or "
+"branch may contain multiple XML source files."
+msgstr ""
+
+#: en_US/getting-files.xml:126(para)
+msgid ""
+"Use the <command>cvs co -c</command> command to view existing module names."
+msgstr ""
+
+#: en_US/getting-files.xml:129(title)
+msgid "Partial List of CVS Modules"
+msgstr ""
+
+#: en_US/getting-files.xml:130(userinput)
+#, no-wrap
+msgid "cd ~/localrepo/fedora-docs/"
+msgstr ""
+
+#: en_US/getting-files.xml:149(para)
+msgid ""
+"The leftmost entry in each line is the name of a module you can check out "
+"from CVS. The rest of the line ensures that checkouts include the proper "
+"branch of a document and the common build tools. For more information on "
+"CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:154(para)
+msgid ""
+"Note in the listing above that the <systemitem>about-fedora</systemitem> "
+"module has two branches available. One branch is for Fedora 7 and one is for "
+"forward development to match the current work of developers. On the other "
+"hand, the <systemitem>documentation-guide</systemitem> module is not "
+"branched."
+msgstr ""
+
+#: en_US/getting-files.xml:161(title)
+msgid "Modules Labeled <filename>-dir</filename>"
+msgstr ""
+
+#: en_US/getting-files.xml:162(para)
+msgid ""
+"Modules ending with the suffix <filename>-dir</filename> are not usually "
+"helpful to checkout directly. These modules do not include the common build "
+"tools and thus do not provide many of the functions contributors require."
+msgstr ""
+
+#: en_US/getting-files.xml:168(title)
+msgid "Module Names"
+msgstr ""
+
+#: en_US/getting-files.xml:169(para)
+msgid ""
+"Choose a module name that accurately reflects your document's subject, but "
+"avoid any name already taken. The document title without any use of the word "
+"<wordasword>fedora</wordasword> is a reasonable choice in most cases. Use "
+"the length descriptors <wordasword>tutorial</wordasword> or "
+"<wordasword>guide</wordasword> in the module name where appropriate."
+msgstr ""
+
+#: en_US/getting-files.xml:178(title)
+msgid "Avoid Redundancy"
+msgstr ""
+
+#: en_US/getting-files.xml:179(para)
+msgid ""
+"Do not use the word <wordasword>fedora</wordasword> to name modules in the "
+"Fedora Documentation Project CVS repository."
+msgstr ""
+
+#: en_US/getting-files.xml:185(title)
+msgid "Correct Module Naming"
+msgstr ""
+
+#: en_US/getting-files.xml:186(segtitle)
+msgid "Document Name"
+msgstr ""
+
+#: en_US/getting-files.xml:187(segtitle)
+msgid "CVS Module Name"
+msgstr ""
+
+#: en_US/getting-files.xml:189(seg)
+msgid "Desktop User Guide"
+msgstr ""
+
+#: en_US/getting-files.xml:190(seg)
+msgid "desktop-user-guide"
+msgstr ""
+
+#: en_US/getting-files.xml:194(application)
+msgid "Yum"
+msgstr ""
+
+#: en_US/getting-files.xml:193(seg)
+msgid "Software Management with <placeholder-1/>"
+msgstr ""
+
+#: en_US/getting-files.xml:195(seg)
+msgid "yum-guide"
+msgstr ""
+
+#: en_US/getting-files.xml:198(application)
+msgid "Pup"
+msgstr ""
+
+#: en_US/getting-files.xml:198(seg)
+#, fuzzy
+msgid "Using <placeholder-1/>"
+msgstr "make po/<placeholder-1/>.po"
+
+#: en_US/getting-files.xml:199(seg)
+msgid "pup-tutorial"
+msgstr ""
+
+#: en_US/getting-files.xml:204(title)
+#, fuzzy
+msgid "File Names"
+msgstr "nome do arquivo"
+
+#: en_US/getting-files.xml:205(para)
+msgid ""
+"Follow these guidelines for naming files to make collaboration and document "
+"reuse easy:"
+msgstr ""
+
+#: en_US/getting-files.xml:209(para)
+msgid ""
+"As with module names, avoid using the word <wordasword>fedora</wordasword> "
+"in file names since it is redundant."
+msgstr ""
+
+#: en_US/getting-files.xml:214(para)
+msgid ""
+"If the document is comprised of many XML files, avoid repeating the name of "
+"the document when naming the constituent files."
+msgstr ""
+
+#: en_US/getting-files.xml:219(para)
+msgid ""
+"Avoid numbering files to show order, since editors and authors often "
+"rearrange documents or reuse their files in other documents."
+msgstr ""
+
+#: en_US/emacs.xml:13(title)
+msgid "Emacs and PSGML Mode"
+msgstr ""
+
+#: en_US/emacs.xml:16(primary)
+msgid "PSGML"
+msgstr ""
+
+#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary)
+#: en_US/emacs.xml:43(primary) en_US/emacs.xml:224(primary)
+#: en_US/emacs.xml:233(primary) en_US/emacs.xml:238(primary)
+#: en_US/emacs.xml:243(primary) en_US/emacs.xml:523(application)
+#: en_US/emacs-nxml.xml:18(primary) en_US/emacs-nxml.xml:22(primary)
+msgid "Emacs"
+msgstr "Emacs"
+
+#: en_US/emacs.xml:25(secondary)
+msgid "PSGML mode"
+msgstr ""
+
+#: en_US/emacs.xml:28(para)
+msgid ""
+"You can use the PSGML mode available for Emacs to make it easier to write in "
+"XML format. PSGML mode provides syntax-highlighting, tag completion, and "
+"more."
+msgstr ""
+
+#: en_US/emacs.xml:35(title)
+msgid "Installing PSGML"
+msgstr ""
+
+#: en_US/emacs.xml:36(para)
+msgid "To install PSGML, use the <command>yum</command> command:"
+msgstr ""
+
+#: en_US/emacs.xml:37(userinput)
+#, no-wrap
+msgid "yum install psgml"
+msgstr ""
+
+#: en_US/emacs.xml:40(title)
+msgid "Setting Up Your <filename>.emacs</filename> File"
+msgstr ""
+
+#: en_US/emacs.xml:48(filename)
+msgid ".emacs"
+msgstr ""
+
+#: en_US/emacs.xml:51(para)
+msgid ""
+"For Emacs to parse your DocBook documents correctly, you must have a "
+"<filename>.emacs</filename> file. Cut and paste the following into your "
+"existing <filename>.emacs</filename> file or create a new one that contains "
+"the following lines:"
+msgstr ""
+
+#: en_US/emacs.xml:181(para)
+msgid ""
+"If you have a wheel mouse and are using Emacs version 21, you can add the "
+"following to your <filename>.emacs</filename> file so your wheel will work "
+"in <application>Emacs</application>:"
+msgstr ""
+
+#: en_US/emacs.xml:192(para)
+msgid ""
+"If you are using the older version 20 of <application>Emacs</application>, "
+"add the following instead:"
+msgstr ""
+
+#: en_US/emacs.xml:221(title)
+msgid "Customizing Emacs"
+msgstr ""
+
+#: en_US/emacs.xml:225(secondary)
+msgid "customizing"
+msgstr ""
+
+#: en_US/emacs.xml:229(filename)
+msgid ".Xresources"
+msgstr ""
+
+#: en_US/emacs.xml:234(secondary)
+msgid "colors"
+msgstr ""
+
+#: en_US/emacs.xml:239(secondary)
+msgid "font"
+msgstr ""
+
+#: en_US/emacs.xml:244(secondary)
+msgid "geometry"
+msgstr ""
+
+#: en_US/emacs.xml:247(para)
+msgid ""
+"The colors, font, and geometry (default size of window) for Emacs in your "
+"<filename>~/.Xresources</filename> file. The format for the settings is "
+"<userinput>emacs.keyword:value</userinput>."
+msgstr ""
+
+#: en_US/emacs.xml:253(para)
+msgid "The following is a sample <filename>~/.Xresources</filename> file."
+msgstr ""
+
+#: en_US/emacs.xml:258(para)
+msgid ""
+"If you have other settings in your <filename>~/.Xresources</filename>, add "
+"the following to the end of the file."
+msgstr ""
+
+#: en_US/emacs.xml:270(para)
+msgid "After modifying this file, execute the following command:"
+msgstr ""
+
+#: en_US/emacs.xml:273(command)
+msgid "xrdb -merge ~/.Xresources"
+msgstr ""
+
+#: en_US/emacs.xml:274(para)
+msgid "Then restart <application>Emacs</application> to apply the changes."
+msgstr ""
+
+#: en_US/emacs.xml:395(title)
+msgid "Basic Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:397(para)
+msgid "The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key."
+msgstr ""
+
+#: en_US/emacs.xml:403(title)
+msgid "Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:404(segtitle)
+msgid "Shortcut"
+msgstr ""
+
+#: en_US/emacs.xml:405(segtitle)
+msgid "Description"
+msgstr "Descrição"
+
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:412(keycap)
+#: en_US/emacs.xml:430(keycap) en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:443(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:458(keycap)
+#: en_US/emacs.xml:463(keycap) en_US/emacs.xml:468(keycap)
+#: en_US/emacs.xml:473(keycap) en_US/emacs.xml:478(keycap)
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:509(keycap)
+#: en_US/emacs.xml:514(keycap) en_US/emacs.xml:515(keycap)
+#: en_US/emacs.xml:520(keycap) en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap) en_US/emacs.xml:533(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "Ctrl"
+msgstr "Ctrl"
+
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:521(keycap) en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "c"
+msgstr ""
+
+#: en_US/emacs.xml:413(keycap)
+msgid "p"
+msgstr ""
+
+#: en_US/emacs.xml:407(seg) en_US/emacs.xml:508(seg) en_US/emacs.xml:514(seg)
+#: en_US/emacs.xml:520(seg) en_US/emacs.xml:532(seg) en_US/emacs.xml:540(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+
+#: en_US/emacs.xml:415(seg)
+msgid "Parse DTD"
+msgstr ""
+
+#: en_US/emacs.xml:431(keycap) en_US/emacs.xml:437(keycap)
+msgid "Shift"
+msgstr "Shift"
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:438(keycap)
+msgid ","
+msgstr ""
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:439(keycap)
+msgid "Tab"
+msgstr ""
+
+#: en_US/emacs.xml:430(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+msgstr ""
+
+#: en_US/emacs.xml:433(seg)
+msgid "Display list of valid tags"
+msgstr ""
+
+#: en_US/emacs.xml:436(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of "
+"tag, <placeholder-5/>"
+msgstr ""
+
+#: en_US/emacs.xml:440(seg)
+msgid "Complete the tag"
+msgstr ""
+
+#: en_US/emacs.xml:443(keycap)
+msgid "g"
+msgstr ""
+
+#: en_US/emacs.xml:445(seg)
+msgid "Cancel a command in the minibuffer"
+msgstr ""
+
+#: en_US/emacs.xml:449(keycap)
+msgid "/"
+msgstr "/"
+
+#: en_US/emacs.xml:448(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:450(seg)
+msgid "Close tag"
+msgstr ""
+
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:533(keycap)
+msgid "a"
+msgstr ""
+
+#: en_US/emacs.xml:455(seg)
+msgid "Move cursor to beginning of line"
+msgstr ""
+
+#: en_US/emacs.xml:458(keycap)
+msgid "e"
+msgstr ""
+
+#: en_US/emacs.xml:460(seg)
+msgid "Move cursor to the end of the line"
+msgstr ""
+
+#: en_US/emacs.xml:463(keycap)
+msgid "Home"
+msgstr ""
+
+#: en_US/emacs.xml:465(seg)
+msgid "Move cursor to the beginning of the file"
+msgstr ""
+
+#: en_US/emacs.xml:468(keycap)
+msgid "End"
+msgstr "Fim"
+
+#: en_US/emacs.xml:470(seg)
+msgid "Move cursor to the end of the file"
+msgstr ""
+
+#: en_US/emacs.xml:473(keycap)
+msgid "k"
+msgstr ""
+
+#: en_US/emacs.xml:475(seg)
+msgid "Cut line"
+msgstr ""
+
+#: en_US/emacs.xml:478(keycap)
+msgid "y"
+msgstr ""
+
+#: en_US/emacs.xml:480(seg)
+msgid "Paste line"
+msgstr ""
+
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:515(keycap)
+msgid "s"
+msgstr ""
+
+#: en_US/emacs.xml:485(seg)
+msgid "Search forward in the file"
+msgstr ""
+
+#: en_US/emacs.xml:488(keycap)
+msgid "r"
+msgstr ""
+
+#: en_US/emacs.xml:490(seg)
+msgid "Search backwards in the file"
+msgstr ""
+
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap) en_US/emacs.xml:527(keycap)
+msgid "Meta"
+msgstr ""
+
+#: en_US/emacs.xml:493(keycap)
+msgid "$"
+msgstr "$"
+
+#: en_US/emacs.xml:495(seg) en_US/emacs.xml:500(seg)
+msgid "Check spelling of current word"
+msgstr ""
+
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:514(keycap)
+#: en_US/emacs.xml:520(keycap)
+msgid "x"
+msgstr ""
+
+#: en_US/emacs.xml:499(keycap) en_US/emacs.xml:504(keycap)
+msgid "Enter"
+msgstr ""
+
+#: en_US/emacs.xml:498(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:503(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:505(seg)
+msgid "Check spelling of current buffer"
+msgstr ""
+
+#: en_US/emacs.xml:509(keycap)
+msgid "f"
+msgstr "f"
+
+#: en_US/emacs.xml:511(seg)
+msgid "Open file"
+msgstr ""
+
+#: en_US/emacs.xml:517(seg)
+msgid "Save file"
+msgstr ""
+
+#: en_US/emacs.xml:523(seg)
+msgid "Exit <placeholder-1/> and prompt to save files if necessary"
+msgstr ""
+
+#: en_US/emacs.xml:527(keycap)
+msgid "q"
+msgstr ""
+
+#: en_US/emacs.xml:529(seg)
+msgid "Fill paragraph"
+msgstr ""
+
+#: en_US/emacs.xml:536(computeroutput)
+#, no-wrap
+msgid "url"
+msgstr ""
+
+#: en_US/emacs.xml:537(computeroutput)
+#, no-wrap
+msgid "ulink"
+msgstr ""
+
+#: en_US/emacs.xml:535(seg)
+msgid ""
+"Edit attributes for a tag (for example, you can edit the <placeholder-1/> "
+"attribute of the <placeholder-2/> tag)"
+msgstr ""
+
+#: en_US/emacs.xml:544(seg)
+msgid "Exit edit attributes"
+msgstr ""
+
+#: en_US/emacs.xml:550(title) en_US/emacs-nxml.xml:77(title)
+msgid "Examples"
+msgstr ""
+
+#: en_US/emacs.xml:552(para)
+msgid ""
+"The table or reference card of Emacs and PSGML commands can be confusing for "
+"beginners. This section provides some examples of how to use them."
+msgstr ""
+
+#: en_US/emacs.xml:559(title)
+msgid "Tag Completion"
+msgstr ""
+
+#: en_US/emacs.xml:563(para)
+msgid "This section assumes that you have already parsed the DTD file."
+msgstr ""
+
+#: en_US/emacs.xml:567(para)
+msgid ""
+"To avoid having to type a tag repeatedly, use the key combination "
+"<keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. "
+"At the bottom of the <application>Emacs</application> window, the following "
+"prompt appears:"
+msgstr ""
+
+#: en_US/emacs.xml:574(prompt)
+msgid "Tag: <"
+msgstr ""
+
+#: en_US/emacs.xml:576(para)
+msgid ""
+"To view a list of available tags, use either the <keycap>Tab</keycap> or "
+"<keycap>?</keycap>. If you know the first few letters of a tag, enter them, "
+"followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, "
+"that tag appears. If more than one completion exists, a complete list of "
+"possible tags appears."
+msgstr ""
+
+#: en_US/emacs.xml:585(para)
+msgid ""
+"If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, "
+"<keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the "
+"example below:"
+msgstr ""
+
+#: en_US/emacs.xml:602(title)
+msgid "Tag Closure"
+msgstr ""
+
+#: en_US/emacs.xml:604(para)
+msgid ""
+"After you open a tag, you must close it. The easiest way to close an open "
+"tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</"
+"keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most "
+"recently opened tag."
+msgstr ""
+
+#: en_US/emacs.xml:616(title)
+msgid "Other Emacs Tasks"
+msgstr ""
+
+#: en_US/emacs.xml:619(title)
+msgid "Working with One Window"
+msgstr ""
+
+#: en_US/emacs.xml:620(para)
+msgid ""
+"Sometimes in <application>Emacs</application>, the window becomes split, "
+"with tags completions or other text in an alternate window. To return to a "
+"single window, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+msgstr ""
+
+#: en_US/emacs.xml:630(title)
+msgid "Saving Work"
+msgstr ""
+
+#: en_US/emacs.xml:631(para)
+msgid ""
+"To save your work, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>s</keycap></keycombo>."
+msgstr ""
+
+#: en_US/emacs.xml:642(title)
+msgid "The \"Clear/Quit\" Command"
+msgstr ""
+
+#: en_US/emacs.xml:643(para)
+msgid ""
+"If the tag completion process becomes unwieldy or confusing, use the "
+"keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to "
+"exit back to the text. <application>Emacs</application> clears any prompts "
+"and returns to the buffer text."
+msgstr ""
+
+#: en_US/emacs.xml:653(title)
+msgid "Opening a new file"
+msgstr ""
+
+#: en_US/emacs.xml:654(para)
+msgid ""
+"To open a new file, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the "
+"<application>Emacs</application> window. Enter the file name, using "
+"<keycap>Tab</keycap> completion if desired, of the file you wish to open."
+msgstr ""
+
+#: en_US/emacs.xml:668(title)
+msgid "Closing <application>Emacs</application>"
+msgstr ""
+
+#: en_US/emacs.xml:669(para)
+msgid ""
+"To close <application>Emacs</application> use the key sequence "
+"<keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, "
+"<keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have "
+"not saved your work, <application>Emacs</application> prompts you to save "
+"any changed files."
+msgstr ""
+
+#: en_US/emacs.xml:687(title) en_US/emacs-nxml.xml:127(title)
+msgid "Additional Resources"
+msgstr "Recursos Adicionais"
+
+#: en_US/emacs.xml:689(para)
+msgid ""
+"Additional Emacs and PSGML references are available at the following "
+"locations:"
+msgstr ""
+
+#: en_US/emacs.xml:697(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+msgid "Emacs Quick Reference Guide"
+msgstr ""
+
+#: en_US/emacs.xml:701(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs.xml:708(para)
+msgid ""
+"Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/"
+"usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+msgstr ""
+
+#: en_US/emacs.xml:714(para)
+msgid ""
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—"
+"<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of "
+"Emacs commands for PSGML mode."
+msgstr ""
+
+#: en_US/emacs.xml:723(citetitle)
+msgid "PSGML Tricks"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:11(title)
+msgid "Emacs and nXML Mode"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:14(primary) en_US/emacs-nxml.xml:51(primary)
+msgid "nXML"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:23(secondary)
+msgid "nXML mode"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:26(para)
+msgid ""
+"You can also use the nXML mode available for <application>Emacs</"
+"application> to make it even easier to write in DocBook XML format. nXML "
+"mode provides context-sensitive editing using completion, real time validity "
+"error checking, syntax highlighting and indentation. All you need to do is "
+"install an RPM!!"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:35(title)
+msgid "Early stages"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:36(para)
+msgid ""
+"Please be aware the nxml-mode for <application>Emacs</application> is quite "
+"new, so there are a few things that the advanced user might notice when "
+"using it with other documents types. If you keep an eye on the mailing-list, "
+"you can keep up to date with these, as well as ask questions. For more "
+"details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:48(title)
+msgid "Getting the nXML RPM"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:52(secondary)
+msgid "RPM"
+msgstr "RPM"
+
+#: en_US/emacs-nxml.xml:56(primary)
+msgid "nXML RPM"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:59(para)
+msgid ""
+"To use nXML mode with emacs, you will need to install the nXML RPM available "
+"from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/"
+"\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www."
+"thaiopensource.com/download/\">http://www.thaiopensource.com/download/</"
+"ulink>. The source requires a lot more work to setup, therefore we will only "
+"be concentrating on the RPM version."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:69(para)
+msgid ""
+"Information on where to get the source is available in <xref linkend=\"sn-"
+"emacs-additional-resources\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:79(para)
+msgid ""
+"Compared to PSGML mode there are only couple of commands that you need. This "
+"speeds up writing with <application>Emacs</application> considerably, which "
+"means you can concentrate more on the content of your article."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:88(para)
+msgid ""
+"To create a tag, type <userinput><</userinput> and then type the keyword. "
+"To complete the keyword, press <command>Ctrl-Ret</command>, then add the "
+"last <userinput>></userinput>. To close a tag, type <userinput></</"
+"userinput>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:97(para)
+msgid ""
+"When you open a document that doesn't have a DOCTYPE declaration at the top "
+"of the file, you will get this message and tag completion won't work because "
+"nXML will not know what format you are writing."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:104(para)
+msgid ""
+"To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</"
+"command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/"
+"schema/</filename> and load <filename>docbook.rnc</filename>. "
+"<application>Emacs</application> will then prompt you to save it in the "
+"current working directory."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:115(para)
+msgid ""
+"The commands already discussed are the only differences between using "
+"<application>Emacs</application> with PSGML mode and <application>Emacs</"
+"application> with nXML mode. You will still need to use all the same "
+"commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:129(para)
+msgid ""
+"Additional Emacs and nXML references are available at the following "
+"locations:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:136(ulink)
+msgid "http://www.thaiopensource.com/download/"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:137(citetitle)
+msgid "Author's download area"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:147(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:157(title)
+msgid "nXML README File"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:161(para)
+msgid ""
+"This file can be found in the directory you extracted the source into, or in "
+"<filename>/usr/share/doc/nxml-mode-<replaceable><version></"
+"replaceable>/</filename> if you installed the RPM."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:169(para)
+msgid "README file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:171(para)
+msgid ""
+"This is a new major mode for GNU Emacs for editing XML documents. It "
+"supports editing well-formed XML documents and also provides schema-"
+"sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:177(para)
+msgid ""
+"To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs "
+"version 20 will not work properly, nor will XEmacs. To get started, do the "
+"following:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:184(command)
+msgid "M-x load-file RET rng-auto.el RET"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:187(para)
+msgid ""
+"This defines the necessary autoloads. Now, visit a file containing an XML "
+"document, and do the following:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:192(command)
+msgid "M-x nxml-mode"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:195(para)
+msgid "Now do"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:200(command)
+msgid "C-h m"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:203(para)
+msgid ""
+"For information on how to use nxml-mode. The beginnings of a manual are in "
+"nxml-mode.info. You can read this using:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:209(command)
+msgid "C-u M-x info RET nxml-mode.info RET"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:212(para)
+msgid ""
+"It's also installed as an entry at the end of the top-level info directory. "
+"So you can read it with <command>C-h i</command> as usual."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:217(para)
+msgid ""
+"You can use <filename>test.valid.xml</filename> and <filename>test.invalid."
+"xml</filename> as examples of valid and invalid XML documents."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:223(para)
+msgid "To get things automatically loaded each time you start Emacs, add:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:228(computeroutput)
+#, no-wrap
+msgid ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+msgstr ""
+
+#: en_US/emacs-nxml.xml:232(para)
+msgid ""
+"to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-"
+"200YMMDD</computeroutput> is the directory containing the <filename>.elc</"
+"filename> files. Note that <filename>rng-auto.el</filename> does not load "
+"all of the nxml-mode code; it merely sets things up so that all the features "
+"of nxml-mode will be autoloaded properly. You should not try to autoload "
+"<filename>rng-auto.el</filename> itself."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:242(para)
+msgid ""
+"To use nxml-mode automatically for files with an extension of <filename>xml</"
+"filename>, <filename>xsl</filename>, <filename>rng</filename> or "
+"<filename>xhtml</filename>, add the following to your <filename>.emacs</"
+"filename> file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:250(computeroutput)
+#, no-wrap
+msgid ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+msgstr ""
+
+#: en_US/emacs-nxml.xml:255(para)
+msgid ""
+"If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are "
+"running Emacs 21.3 or later, then I recommend enabling unify-8859-on-"
+"decoding-mode, by adding the following to your <filename>.emacs</filename> "
+"file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:263(computeroutput)
+#, no-wrap
+msgid "(unify-8859-on-decoding-mode)"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:266(para)
+msgid ""
+"To get validation and schema-sensitive editing, you need a RELAX NG Compact "
+"Syntax (RNC) schema for you document. The schema directory includes some "
+"schemas for popular document types."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:272(para)
+msgid ""
+"For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://"
+"relaxng.org/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:277(para)
+msgid ""
+"For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://"
+"relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial."
+"html</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:282(para)
+msgid ""
+"For automatically creating RNC schemas, I recommend my Trang program: <ulink "
+"url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee."
+"thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:293(para)
+msgid "Infer an RNC schema from an instance document"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:298(para)
+msgid "Convert a DTD to an RNC schema"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:303(para)
+msgid "Convert a RELAX NG XML syntax schema to an RNC schema"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:288(para)
+msgid "You can use this to <placeholder-1/>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:310(para)
+msgid ""
+"To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also "
+"use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html"
+"\">http://www.pantor.com/download.html\"</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:316(para)
+msgid ""
+"To convert a W3C XML Schema to an RNC schema, you need first to convert it "
+"to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on "
+"top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www."
+"dev.java.net/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:323(para)
+msgid "The file <filename>NEWS</filename> describes recent changes."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:327(para)
+msgid ""
+"Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-"
+"mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug "
+"reports, discussion. I will announce all new versions there."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:333(para)
+msgid "James Clark"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:336(para)
+msgid "jjc@@thaiopensource.com"
+msgstr ""
+
+#: en_US/acknowledgments.xml:11(title)
+msgid "Acknowledgments"
+msgstr "Agradecimentos"
+
+#: en_US/acknowledgments.xml:13(para)
+msgid ""
+"This document is based on a document started by Tammy Fox (tfox at redhat."
+"com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray "
+"Fuller (jrfuller at redhat.com)."
+msgstr ""
+
+#: en_US/acknowledgments.xml:19(para)
+msgid ""
+"A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to "
+"fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr ""
+
+#: en_US/acknowledgments.xml:25(para)
+msgid ""
+"Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to "
+"add the trailing slashes to the <command>figure</command> tag example in "
+"<filename>docs-xml-tags.xml</filename>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:32(para)
+msgid ""
+"A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been "
+"applied to add <xref linkend=\"ch-vim\"/>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:37(para)
+msgid ""
+"A patch from Karsten Wade (kwade at redhat.com) has been applied to add "
+"<xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields "
+"(stickster at gmail.com)."
+msgstr ""
+
+#. This section has been removed.
+#. <para>
+#. A patch from Paul W. Frields (stickster at gmail.com) has been applied
+#. to add more explanation of the <command>screen</command> tag set to <xref
+#. linkend="sn-xml-tags-screen"></xref>.
+#. </para>
+#: en_US/acknowledgments.xml:50(para)
+msgid ""
+"A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been "
+"applied to more fully explaing the document building system."
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: en_US/acknowledgments.xml:0(None)
+msgid "translator-credits"
+msgstr "José Nuno Pires <jncp@@netcabo.pt>, 2006."
+@
+
+
+1.18
+log
+ at Translated a _few_ messages
+@
+text
+ at d8 1
+a8 1
+"POT-Creation-Date: 2007-12-15 16:51-0500\n"
+d42 1
+a43 1
+#
+d47 5
+a51 1
+#: en_US/rpm-info.xml:31(holder)
+d53 1
+d57 1
+a57 1
+#: en_US/rpm-info.xml:33(title)
+d61 1
+a61 1
+#: en_US/rpm-info.xml:34(desc)
+d65 5
+a69 1
+#: en_US/rpm-info.xml:38(details)
+d73 1
+a73 1
+#: en_US/rpm-info.xml:42(details)
+d77 1
+a77 1
+#: en_US/rpm-info.xml:46(details)
+d81 1
+a81 1
+#: en_US/rpm-info.xml:50(details)
+d85 1
+a85 1
+#: en_US/rpm-info.xml:54(details)
+d89 1
+a89 1
+#: en_US/rpm-info.xml:58(details)
+d93 1
+a93 1
+#: en_US/rpm-info.xml:62(details)
+d97 1
+a97 1
+#: en_US/rpm-info.xml:69(details)
+d102 171
+d287 8
+a294 2
+"Este capítulo mostra como publicar o trabalho oficial do Projeto de Documentação do Fedora para o website <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem>. Para publicar documentação oficial você deve ter permissão para escrever no repositório em CVS. Acesso de publicação é limitado para contribuintes que demonstraram capacidade para trabalhar com CVS o outras ferramentas do projeto. Uma vez que você conseguiu essas habilidades e está comfortável com elas, contribuições são bem-vindas."
+d509 2
+a510 1
+msgid "Build the HTML version of each translation of the document from Docs CVS."
+d1203 2
+a1204 1
+msgid "There is a text box that you can use to find out the definition of a word."
+d1403 2
+a1404 1
+msgid "The term does not appear in the glossary of the manual that you are writing."
+d1408 2
+a1409 1
+msgid "The term is not defined in the body text of the manual that you are writing."
+d1663 2
+a1664 1
+msgid "the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+d2086 2
+a2087 1
+msgid "Numbers from zero through nine unless the number is part of a measurement"
+d2623 2
+a2624 1
+msgid "Follow the capitalization rules for headings in the title of an admonition."
+d2649 1
+a2649 1
+"which produces the text \"Fedora 8.\""
+d3269 2
+a3270 1
+msgid "To find all the currently active ssh sessions, execute the following command:"
+d3883 2
+a3884 1
+msgid "To add a new DocBook XML file to an existing document, follow these steps:"
+d4123 2
+a4124 1
+msgid "Use the <command>cvs co -c</command> command to view existing module names."
+a5179 1
+
+@
+
+
+1.17
+log
+ at Update POT and PO
+@
+text
+ at d4 1
+d9 3
+a11 3
+"PO-Revision-Date: 2007-06-04 12:46-0300\n"
+"Last-Translator: Nullck <nullck@@localhost.localdomain>\n"
+"Language-Team: <en@@li.org>\n"
+d16 1
+a16 1
+"X-Generator: KBabel 1.11.1\n"
+d43 1
+a43 1
+#, fuzzy
+d45 1
+a45 1
+msgstr "2003"
+d48 1
+a48 1
+#, fuzzy
+d50 1
+a50 1
+msgstr "Red Hat, Inc."
+d66 1
+a66 1
+msgstr ""
+d70 1
+a70 1
+msgstr ""
+d74 1
+a74 1
+msgstr ""
+d78 1
+a78 1
+msgstr ""
+d82 1
+a82 1
+msgstr ""
+d95 1
+a95 1
+msgstr ""
+d107 2
+d112 1
+a112 1
+msgstr ""
+d323 1
+a323 2
+msgid ""
+"Build the HTML version of each translation of the document from Docs CVS."
+d1016 1
+a1016 2
+msgid ""
+"There is a text box that you can use to find out the definition of a word."
+d1215 1
+a1215 2
+msgid ""
+"The term does not appear in the glossary of the manual that you are writing."
+d1219 1
+a1219 2
+msgid ""
+"The term is not defined in the body text of the manual that you are writing."
+d1473 1
+a1473 2
+msgid ""
+"the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+d1895 1
+a1895 2
+msgid ""
+"Numbers from zero through nine unless the number is part of a measurement"
+d2431 1
+a2431 2
+msgid ""
+"Follow the capitalization rules for headings in the title of an admonition."
+d3076 1
+a3076 2
+msgid ""
+"To find all the currently active ssh sessions, execute the following command:"
+d3689 1
+a3689 2
+msgid ""
+"To add a new DocBook XML file to an existing document, follow these steps:"
+d3928 1
+a3928 2
+msgid ""
+"Use the <command>cvs co -c</command> command to view existing module names."
+a4984 442
+#~ msgid "DocBook XML Tags"
+#~ msgstr "Tags do DocBook XML "
+
+#~ msgid "XML"
+#~ msgstr "XML"
+
+#~ msgid "tags"
+#~ msgstr "tags"
+
+#~ msgid ""
+#~ "Please read this chapter carefully. This chapter describes the tags used "
+#~ "by the Docs Project. Some of the rules described are specific to the "
+#~ "project."
+#~ msgstr ""
+#~ "Por favor leia este capítulo com cuidado. Este capítulo descreve as tags "
+#~ "usadas pelo Projeto Docs. Algumas das regras descritas são específicas "
+#~ "para o projeto."
+
+#~ msgid ""
+#~ "If these tags are used appropriately, document searches will provide "
+#~ "meaningful results. These tags help search engines identify the "
+#~ "information relevant to the search request. Another benefit is that all "
+#~ "Fedora Project documents will have a similar look and feel (however, they "
+#~ "will have some differences depending upon the output format)."
+#~ msgstr ""
+#~ "Se estas tags forem usadas apropriadamente, as buscas fornecerão "
+#~ "resultados significativos. Estas formas de busca com auxilio de tags, "
+#~ "identificam a informação relevante à requisição de busca. Um outro "
+#~ "benefício é que todos os documentos do Projeto Fedora possuirão um visual "
+#~ "similar (entretanto, terão algumas diferenças dependendo do formato de "
+#~ "saída)."
+
+#~ msgid "general tag information"
+#~ msgstr "Informação geral da tag"
+
+#~ msgid ""
+#~ "Most tags in XML must have an opening and closing tag. A few tags, such "
+#~ "as <sgmltag class=\"emptytag\">xref</sgmltag>, have no content and close "
+#~ "themselves. Additionally, proper XML conventions say that there must be a "
+#~ "unique identifier for sections, chapters, figures, tables, and so on, so "
+#~ "that they may be correctly identified, and cross referenced if needed."
+#~ msgstr ""
+#~ "A maioria das tags em XML devem ter uma tag de abertura e uma tag de "
+#~ "fechamento. Algumas tags, tais como <sgmltag class=\"emptytag\">xref</"
+#~ "sgmltag>, não têm nenhum conteúdo e depois são fechadas. Adicionalmente, "
+#~ "as convenções apropriadas de XML dizem que deve haver um identificador "
+#~ "original para seções, capítulos, figuras, tabelas, e assim por diante, de "
+#~ "modo que possam corretamente ser identificadas, e se necessário é feito "
+#~ "auto remissão."
+
+#~ msgid ""
+#~ "Although XML is capable of handling many document types, the format "
+#~ "discussed here is the article format."
+#~ msgstr ""
+#~ "Embora originalmente XML seja capaz de manipular vários tipos de formato, "
+#~ "o formato discutido aqui é o formato de artigo."
+
+#~ msgid "Tags and Entities Caveats"
+#~ msgstr "Tag e Caveats das entidades"
+
+#~ msgid ""
+#~ "It is very important that you remember the caveats in this section. Even "
+#~ "though they are more strict than valid DocBook XML, these rules exist so "
+#~ "that both the HTML and PDF outputs look proper."
+#~ msgstr ""
+#~ "É muito importante que você recorde os caveats nesta seção. Mesmo que "
+#~ "sejam mais simplificados do que o XML DocBook válido , estas régras "
+#~ "existem de modo que as saídas do HTML e do pdf sejam visualizadas "
+#~ "apropriadamente."
+
+#~ msgid ""
+#~ "Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+#~ "sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+#~ "\"genentity\">reg</sgmltag> because they do not produce HTML output that "
+#~ "works for all charsets. The HTML output produces by these entities are "
+#~ "declared in the DTD and cannot be changed via the stylesheet."
+#~ msgstr ""
+#~ "Não use entidades de marca registrada<sgmltag class=\"genentity\"> trade</"
+#~ "sgmltag>, <sgmltag class=\"genentity\"> copy</sgmltag>, ou <sgmltag class="
+#~ "\"genentity\"> reg</sgmltag> porque não produzem a saida em HTML que "
+#~ "funcione com todos os charsets. A saída em HTML produzida por estas "
+#~ "entidades é declarada no DTD e não pode ser mudada através da planilha de "
+#~ "estilo."
+
+#~ msgid ""
+#~ "Instead, use the <sgmltag class=\"element\">trademark</sgmltag> tag and "
+#~ "its associates classes as follows:"
+#~ msgstr ""
+#~ "Preferêncialmente , use a tag <sgmltag class=\"element\">trademark</"
+#~ "sgmltag>e suas classes associadas como segue:"
+
+#~ msgid ""
+#~ "<sgmltag class=\"starttag\">trademark</sgmltag>trademark symbol after "
+#~ "me<sgmltag class=\"endtag\">trademark</sgmltag>"
+#~ msgstr ""
+#~ "<sgmltag class=\"starttag\">trademark</sgmltag> é simbolo de trademark "
+#~ "<sgmltag class=\"endtag\">trademark </sgmltag>"
+
+#~ msgid ""
+#~ "<sgmltag class=\"starttag\">trademark class=\"registered\"</"
+#~ "sgmltag>registered trademark symbol after me<sgmltag class=\"endtag"
+#~ "\">trademark</sgmltag>"
+#~ msgstr ""
+#~ "<sgmltag class=\"starttag\">trademark class=\"registered\"</"
+#~ "sgmltag>simbolo de trademark registrada<sgmltag class=\"endtag"
+#~ "\">trademark</sgmltag>"
+
+#~ msgid ""
+#~ "<sgmltag class=\"starttag\">trademark class=\"copyright\"</"
+#~ "sgmltag>copyright symbol after me<sgmltag class=\"endtag\">trademark</"
+#~ "sgmltag>"
+#~ msgstr ""
+#~ "<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag> "
+#~ "simbolo de copyright <sgmltag class=\"endtag\">trademark</sgmltag>"
+
+#~ msgid ""
+#~ "Do not use <sgmltag>para</sgmltag> tags around anything other than a "
+#~ "simple paragraph. Doing so will create additional white space within the "
+#~ "text itself in the PDF version."
+#~ msgstr ""
+#~ "Não use Tag <sgmltag>para</sgmltag> entre qualquer conteúdo com excessão "
+#~ "de um parágrafo simples. Fazendo assim você criará um espaço em branco "
+#~ "dentro do próprio texto na versão do pdf."
+
+#~ msgid ""
+#~ "Specifically, do not use <sgmltag>para</sgmltag> tags around the "
+#~ "following (or, to put this another way, do not embed the following within "
+#~ "<sgmltag>para</sgmltag> tags):"
+#~ msgstr ""
+#~ "Especificamente, não use Tag <sgmltag>para</sgmltag> entre o seguinte "
+#~ "conteúdo(ou, para pôr de outra maneira, não deixe o seguinte conteúdo "
+#~ "dentro das Tag <sgmltag>para</sgmltag>):"
+
+#~ msgid ""
+#~ "Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+#~ "sgmltag> tags"
+#~ msgstr ""
+#~ "Conteúdo em tags <sgmltag>para</sgmltag> dentro de tags "
+#~ "<sgmltag>listitem</sgmltag>"
+
+#~ msgid ""
+#~ "Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+#~ "sgmltag> tags <emphasis>must</emphasis> start immediately after the "
+#~ "beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra "
+#~ "white space in the PDF version."
+#~ msgstr ""
+#~ "Índice de tags <sgmltag> dentro das tags </sgmltag> listitem </sgmltag> "
+#~ "tags <emphasis>must</emphasis> começar imediatamente depois da tag "
+#~ "<sgmltag class=\"starttag\">para</sgmltag>para evitar o espaço branco "
+#~ "extra na versão do pdf."
+
+#~ msgid "application"
+#~ msgstr "Aplicação"
+
+#~ msgid ""
+#~ "An application is the name of a GUI software program. A command is the "
+#~ "name of an executable (text) program or a software command."
+#~ msgstr ""
+#~ "Uma aplicação é o nome de um programa, feito por um o software com GUI. "
+#~ "Um comando é o nome de um programa executável (texto) ou de um comando do "
+#~ "próprio o software."
+
+#~ msgid ""
+#~ "The <sgmltag class=\"starttag\">application</sgmltag> and <sgmltag class="
+#~ "\"endtag\">application</sgmltag> tags allow you to refer to an "
+#~ "application or program. For example, the following XML:"
+#~ msgstr ""
+#~ "A <sgmltag class=\"starttag\">application</sgmltag> e <sgmltag class="
+#~ "\"endtag\">application</sgmltag> são os tags que permitem que você "
+#~ "consulte a uma aplicação ou a um programa. Por exemplo, o seguinte XML:"
+
+#~ msgid ""
+#~ "\n"
+#~ "To view the Web in Linux, you can use\n"
+#~ "<placeholder-1/>Mozilla<placeholder-2/> \n"
+#~ "or <placeholder-3/>lynx<placeholder-4/> if\n"
+#~ "you only want a text-based browser.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Para ver uma página WEB no Linux, você pode usar\n"
+#~ "<placeholder-1/>Mozilla<placeholder-2/> \n"
+#~ "ou <placeholder-3/>lynx<placeholder-4/> se\n"
+#~ "você quer somente um browser baseado em texto.\n"
+
+#~ msgid "produces the following output:"
+#~ msgstr "produz a seguinte saida: "
+
+#~ msgid ""
+#~ "To view the Web in Linux, you can use <application>Mozilla</application> "
+#~ "or <application>lynx</application> if you only want a text-based browser."
+#~ msgstr ""
+#~ "Para ver uma pagina WEB no Linux, você pode usar Mozilla ou lynx se você "
+#~ "quiser somente um browser baseado em texto."
+
+#~ msgid "A DocBook book can be divided into chapters such as:"
+#~ msgstr "O livro DocBook pode ser dividido em capítulos como:"
+
+#, fuzzy
+#~ msgid ""
+#~ "\n"
+#~ "<!--$Id: pt_BR.po,v 1.16 2007/11/15 02:12:48 pfrields Exp $ -->\n"
+#~ "\n"
+#~ " <chapter id=\"ch-sample\">\n"
+#~ " <title>Sample Chapter</title>\n"
+#~ "\n"
+#~ " <para>This is a sample chapter, showing you the XML tags used "
+#~ "to create a\n"
+#~ " chapter, sections, and subsections.</para>\n"
+#~ " \n"
+#~ " </chapter>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<!--$Id: pt_BR.po,v 1.16 2007/11/15 02:12:48 pfrields Exp $ -->\n"
+#~ "\n"
+#~ " <chapter id=\"ch-sample\">\n"
+#~ " <title>Capitulo de Exemplo</title>\n"
+#~ "\n"
+#~ " <para>Este é um capítulo de exemplo, mostrando as tag's de XML "
+#~ "usadas para criar um capítulo, as seções, e as subseções..</para>\n"
+#~ " \n"
+#~ " </chapter>\n"
+
+#~ msgid ""
+#~ "The chapter can also be further divided into sections (<sgmltag>section</"
+#~ "sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). "
+#~ "Refer to <xref linkend=\"sn-xml-tags-sections\"/> for details."
+#~ msgstr ""
+#~ "O capítulo pode também ser dividido em subseções(<sgmltag>section</"
+#~ "sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.)."
+#~ "Referência <xref linkend=\"sn-xml-tags-sections\"/> para detalhes"
+
+#~ msgid "citetitle"
+#~ msgstr "Titulo Citado"
+
+#~ msgid ""
+#~ "An entity is a short hand way of referring to some predefined content, "
+#~ "such as a title or name. It can be defined within the parent document or "
+#~ "within a set of files that your DTD references for your specific "
+#~ "documentation set."
+#~ msgstr ""
+#~ " Uma entidade é uma maneira pratica de consultar algum índice "
+#~ "predefinido, tal como um título ou um nome. O mesmo pode ser definido "
+#~ "dentro do documento pai ou dentro de um conjunto de arquivos que sua DTD "
+#~ "referência, para suas configurações específicas de documentação"
+
+#, fuzzy
+#~ msgid ""
+#~ "The <sgmltag>citetitle</sgmltag> tag provides formatting for a specific "
+#~ "references (title can be manually typed out or if already defined within "
+#~ "your document set, given as an entity<placeholder-1/> )."
+#~ msgstr ""
+#~ "A tag<sgmltag>titulo citado</sgmltag> fornece um formato especifico de "
+#~ "referências(o título pode ser digitado manualmente para uma saída ou se "
+#~ "pode ser definido dentro de um padrão, dado como uma "
+#~ "entidade<footnote><placeholder-1/></footnote> )."
+
+#~ msgid "For example:"
+#~ msgstr "Por exemplo:"
+
+#~ msgid "IG"
+#~ msgstr "IG"
+
+#~ msgid ""
+#~ "\n"
+#~ "<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+
+#~ msgid ""
+#~ "The output looks like <citetitle>Installation Guide</citetitle> because "
+#~ "<sgmltag class=\"genentity\">IG</sgmltag> is an entity."
+#~ msgstr ""
+#~ "A saída é visualizada como a <citetitle>Guia da Instalação </citetitle> "
+#~ "porque <sgmltag class=\"genentity\">IG</sgmltag> é uma entidade."
+
+#~ msgid "command"
+#~ msgstr "comando"
+
+#~ msgid ""
+#~ "An application is the name of a GUI software program. A command is the "
+#~ "name of an executable (text) program or a software command. Any program "
+#~ "that is a command line or text-based only tool is marked with "
+#~ "<sgmltag>command</sgmltag> tags."
+#~ msgstr ""
+#~ "Uma aplicação é o nome de um programa, feito por um o software com GUI. "
+#~ "Um comando é o nome de um programa executável (texto) ou de um comando do "
+#~ "próprio o software.Todo o programa que for uma linha de comando ou "
+#~ "somente uma ferramenta baseada em texto é marcado com <sgmltag>command</"
+#~ "sgmltag> tags."
+
+#~ msgid ""
+#~ "If you have text that is a command, use the <sgmltag class=\"starttag"
+#~ "\">command</sgmltag> and <sgmltag class=\"endtag\">command</sgmltag> tags "
+#~ "such as:"
+#~ msgstr ""
+#~ "Se você tiver uma linha de comando, use o <sgmltag class=\"starttag"
+#~ "\">command</sgmltag> e <sgmltag class=\"endtag\">command</sgmltag> tags "
+#~ "como:"
+
+#~ msgid ""
+#~ "\n"
+#~ "To change your keyboard after installation, become root \n"
+#~ "and use the <command>redhat-config-keyboard</command> "
+#~ "command, \n"
+#~ "or you can type <command>setup</command> at the root prompt.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "Para mudar seu teclado após a instalação, se torne root \n"
+#~ "e use os comandos <command>redhat-config-keyboard</"
+#~ "command> , \n"
+#~ "ou você pode digitar <command>setup</command> no terminal.\n"
+
+#~ msgid "The output:"
+#~ msgstr "A saída: "
+
+#~ msgid ""
+#~ "To change your keyboard after installation, become root and use the "
+#~ "<command>redhat-config-keyboard</command> command, or you can type "
+#~ "<command>setup</command> at the root prompt."
+#~ msgstr ""
+#~ "Para mudar seu teclado após a instalação, se torne roote use os "
+#~ "comandos<command>redhat-config-keyboard</command> ou você pode digitar "
+#~ "<command>setup</command> no terminal."
+
+#~ msgid "Another example would be:"
+#~ msgstr "Um outro exemplo seria"
+
+#~ msgid ""
+#~ "\n"
+#~ "<command>MAILNOVIOLATIONS</command> — If set\n"
+#~ "to <command>true</command> this option tells Tripwire to\n"
+#~ "email a report at a regular interval regardless of whether or not\n"
+#~ "any violations have occured. The default value is\n"
+#~ "<command>true</command>.\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<command>MAILNOVIOLATIONS</command> — Se \n"
+#~ "for <command>true</command>esta opção envia ao Tripwire\n"
+#~ "um relatório regular por e-mail em caso de ocorrer ou não \n"
+#~ "violações. O valor padrão é \n"
+#~ "<command>true</command>.\n"
+
+#~ msgid "with the output:"
+#~ msgstr "com a saída:"
+
+#~ msgid ""
+#~ "<command>MAILNOVIOLATIONS</command>— If set to <command>true</"
+#~ "command> this variable tells Tripwire to email a report at a regular "
+#~ "interval regardless of whether or not any violations have occured. The "
+#~ "default value is <command>true</command>."
+#~ msgstr ""
+#~ "<command>MAILNOVIOLATIONS</command> — Se for marcado como <command> "
+#~ "true</command> esta opção envia ao Tripwire um relatório regular por e-"
+#~ "mail em caso de ocorrer ou não violações. O valor padrão é <command>true</"
+#~ "command>"
+
+#~ msgid ""
+#~ "In this example, the option value (true) is defined with a <"
+#~ "command> tag set. Because a option is a configuration file option "
+#~ "(command line options which would use the <option> tag set), and "
+#~ "because there is no configuration file option tag available to use, we "
+#~ "are extending the <command> tag set to define options in a "
+#~ "configuration file."
+#~ msgstr ""
+#~ "Neste exemplo, o valor da opção (true) é definido com um conjunto <"
+#~ "command> de tag's. Porque a opção é uma opção do arquivo de "
+#~ "configuração (a linha de comando options que usaria a tag <opção> "
+#~ "ajustada), e porque não há nenhuma tag de opção da linha da configuração "
+#~ "disponível para se usar, nós iremos extender o; <command> conjunto "
+#~ "das tag's para definir essa opções em um arquivo de configuração."
+
+#~ msgid ""
+#~ "Terms marked with <command>command</command> tags because there aren't "
+#~ "exact tags for them:"
+#~ msgstr ""
+#~ "Os termos são marcados com <command>command</command> tags porque não há "
+#~ "tag exatas para ele:"
+
+#~ msgid "Options in configuration files such as Apache directives"
+#~ msgstr "Opções do arquivo de configuração assim como diretivas do Apache"
+
+#~ msgid "daemon names"
+#~ msgstr "Nomes dos Deamons"
+
+#~ msgid "computeroutput"
+#~ msgstr "computeroutput"
+
+#~ msgid "To show computer output use the following tags:"
+#~ msgstr "Para exibir a computeroutput use as seguintes tags:"
+
+#~ msgid ""
+#~ "\n"
+#~ "<computeroutput>Do you want to delete this file? y n</"
+#~ "computeroutput>\n"
+#~ msgstr ""
+#~ "\n"
+#~ "<computeroutput>Você quer deletar este arquivo? y n</"
+#~ "computeroutput>\n"
+
+#~ msgid "Do you really want to delete this file? y n"
+#~ msgstr "Você realmente quer deletar este arquivo? y n"
+
+#~ msgid "emphasis"
+#~ msgstr "emphasis"
+
+#~ msgid ""
+#~ "To emphasis content, use the <command><emphasis></command> and "
+#~ "<command></emphasis></command> tags. For example:"
+#~ msgstr ""
+#~ "Para dar ênfase ao indice, use as tags <command><emphasis></"
+#~ "command> e <command></emphasis></command>. Por exemplo:"
+
+#~ msgid "filename"
+#~ msgstr "nome do arquivo"
+
+#~ msgid "para"
+#~ msgstr "para"
+
+#~ msgid "arch"
+#~ msgstr "arquitectura"
+
+#~ msgid "GNOME"
+#~ msgstr "GNOME"
+
+#~ msgid "KDE"
+#~ msgstr "KDE"
+
+#~ msgid "Hardware"
+#~ msgstr "'Hardware'"
+
+#~ msgid "Tammy Fox"
+#~ msgstr "Tammy Fox"
+
+#~ msgid "Johnray Fuller"
+#~ msgstr "Johnray Fuller"
+
+#~ msgid "Sandra Moore"
+#~ msgstr "Sandra Moore"
+
+#~ msgid "Paul W. Frields"
+#~ msgstr "Paul W. Frields"
+@
+
+
+1.16
+log
+ at Update POT/PO files for DocGuide, minor changes
+@
+text
+ at d7 1
+a7 1
+"POT-Creation-Date: 2007-11-14 21:12-0500\n"
+d60 4
+d67 1
+a67 1
+#: en_US/rpm-info.xml:42(details)
+d71 1
+a71 1
+#: en_US/rpm-info.xml:46(details)
+d75 1
+a75 1
+#: en_US/rpm-info.xml:50(details)
+d79 1
+a79 1
+#: en_US/rpm-info.xml:54(details)
+d83 1
+a83 1
+#: en_US/rpm-info.xml:58(details)
+d87 1
+a87 1
+#: en_US/rpm-info.xml:65(details)
+d3467 24
+d3494 2
+a3495 2
+#: en_US/module-struct.xml:243(abbrev) en_US/module-struct.xml:254(abbrev)
+#: en_US/module-struct.xml:279(abbrev) en_US/module-struct.xml:284(abbrev)
+d3499 2
+a3500 2
+#: en_US/module-struct.xml:247(systemitem)
+#: en_US/module-struct.xml:257(systemitem)
+d3504 2
+a3505 2
+#: en_US/module-struct.xml:248(systemitem)
+#: en_US/module-struct.xml:258(systemitem)
+d3509 1
+a3509 1
+#: en_US/module-struct.xml:246(filename)
+d3513 1
+a3513 1
+#: en_US/module-struct.xml:243(seg)
+d3521 1
+a3521 1
+#: en_US/module-struct.xml:253(systemitem)
+d3525 1
+a3525 1
+#: en_US/module-struct.xml:256(filename)
+d3529 1
+a3529 1
+#: en_US/module-struct.xml:254(seg)
+d3536 1
+a3536 1
+#: en_US/module-struct.xml:262(systemitem)
+d3540 2
+a3541 2
+#: en_US/module-struct.xml:263(abbrev) en_US/module-struct.xml:264(abbrev)
+#: en_US/module-struct.xml:280(abbrev) en_US/module-struct.xml:285(abbrev)
+d3545 1
+a3545 1
+#: en_US/module-struct.xml:263(seg)
+d3552 1
+a3552 1
+#: en_US/module-struct.xml:268(systemitem)
+d3556 1
+a3556 1
+#: en_US/module-struct.xml:269(command)
+d3560 1
+a3560 1
+#: en_US/module-struct.xml:269(seg)
+d3566 1
+a3566 1
+#: en_US/module-struct.xml:273(systemitem)
+d3570 1
+a3570 1
+#: en_US/module-struct.xml:274(seg)
+d3574 2
+a3575 2
+#: en_US/module-struct.xml:277(systemitem)
+#: en_US/module-struct.xml:286(filename)
+d3579 1
+a3579 1
+#: en_US/module-struct.xml:279(emphasis)
+d3583 1
+a3583 1
+#: en_US/module-struct.xml:278(seg)
+d3589 1
+a3589 1
+#: en_US/module-struct.xml:283(systemitem)
+d3593 1
+a3593 1
+#: en_US/module-struct.xml:284(seg)
+d3599 1
+a3599 1
+#: en_US/module-struct.xml:291(title)
+d3603 1
+a3603 1
+#: en_US/module-struct.xml:292(para)
+d3609 1
+a3609 1
+#: en_US/module-struct.xml:296(title)
+d3613 1
+a3613 1
+#: en_US/module-struct.xml:297(para)
+d3622 1
+a3622 1
+#: en_US/module-struct.xml:305(para)
+d3628 1
+a3628 1
+#: en_US/module-struct.xml:312(title)
+d3632 1
+a3632 1
+#: en_US/module-struct.xml:313(para)
+d3640 1
+a3640 1
+#: en_US/module-struct.xml:320(para)
+d3653 1
+a3653 1
+#: en_US/module-struct.xml:334(para)
+d3660 1
+a3660 1
+#: en_US/module-struct.xml:340(para)
+d3670 1
+a3670 1
+#: en_US/module-struct.xml:350(para)
+d3679 1
+a3679 1
+#: en_US/module-struct.xml:359(para)
+d3685 1
+a3685 1
+#: en_US/module-struct.xml:365(title)
+d3689 1
+a3689 1
+#: en_US/module-struct.xml:372(title)
+d3693 1
+a3693 1
+#: en_US/module-struct.xml:373(para)
+d3698 1
+a3698 1
+#: en_US/module-struct.xml:377(para)
+d3702 1
+a3702 1
+#: en_US/module-struct.xml:381(para)
+d3711 1
+a3711 1
+#: en_US/module-struct.xml:391(title)
+d3715 1
+a3715 1
+#: en_US/module-struct.xml:392(para)
+d3723 1
+a3723 1
+#: en_US/module-struct.xml:399(para)
+d3729 1
+a3729 1
+#: en_US/module-struct.xml:405(para)
+d3733 1
+a3733 1
+#: en_US/module-struct.xml:409(para)
+d3739 1
+a3739 1
+#: en_US/module-struct.xml:414(para)
+d3745 1
+a3745 1
+#: en_US/module-struct.xml:417(replaceable)
+d3749 1
+a3749 1
+#: en_US/module-struct.xml:417(screen)
+d5192 1
+a5192 1
+#~ "<!--$Id: pt_BR.po,v 1.15 2007/08/03 16:42:44 pfrields Exp $ -->\n"
+d5204 1
+a5204 1
+#~ "<!--$Id: pt_BR.po,v 1.15 2007/08/03 16:42:44 pfrields Exp $ -->\n"
+@
+
+
+1.15
+log
+ at Push new 0.3.1 POT and update PO - ERRATA, this time with new content file
+@
+text
+ at d7 1
+a7 1
+"POT-Creation-Date: 2007-08-03 12:42-0400\n"
+d60 8
+d71 1
+a71 1
+#: en_US/rpm-info.xml:42(details)
+d75 1
+a75 1
+#: en_US/rpm-info.xml:46(details)
+d79 1
+a79 1
+#: en_US/rpm-info.xml:50(details)
+d83 1
+a83 1
+#: en_US/rpm-info.xml:57(details)
+d188 4
+d194 10
+d208 1
+a208 1
+#: en_US/publishing.xml:68(screen)
+d213 1
+a213 1
+#: en_US/publishing.xml:71(para)
+d219 1
+a219 1
+#: en_US/publishing.xml:85(para)
+d225 1
+a225 1
+#: en_US/publishing.xml:87(screen)
+d230 1
+a230 1
+#: en_US/publishing.xml:90(para)
+d234 1
+a234 1
+#: en_US/publishing.xml:91(screen)
+d239 1
+a239 1
+#: en_US/publishing.xml:92(para)
+d243 1
+a243 1
+#: en_US/publishing.xml:94(screen)
+d248 1
+a248 1
+#: en_US/publishing.xml:97(para)
+d254 1
+a254 1
+#: en_US/publishing.xml:101(title)
+d258 1
+a258 1
+#: en_US/publishing.xml:103(title)
+d262 1
+a262 1
+#: en_US/publishing.xml:104(para)
+d268 1
+a268 1
+#: en_US/publishing.xml:108(para)
+d276 1
+a276 1
+#: en_US/publishing.xml:115(para)
+d282 1
+a282 1
+#: en_US/publishing.xml:120(para)
+d290 1
+a290 1
+#: en_US/publishing.xml:129(title)
+d294 1
+a294 1
+#: en_US/publishing.xml:130(para)
+d302 1
+a302 1
+#: en_US/publishing.xml:137(para)
+d306 1
+a306 1
+#: en_US/publishing.xml:138(screen)
+d315 1
+a315 1
+#: en_US/publishing.xml:144(para)
+d320 1
+a320 1
+#: en_US/publishing.xml:146(replaceable)
+d324 1
+a324 1
+#: en_US/publishing.xml:146(screen)
+d331 1
+a331 1
+#: en_US/publishing.xml:150(para)
+d335 1
+a335 1
+#: en_US/publishing.xml:151(screen)
+d343 1
+a343 1
+#: en_US/publishing.xml:156(para)
+d349 1
+a349 1
+#: en_US/publishing.xml:165(para)
+d360 1
+a360 1
+#: en_US/publishing.xml:175(para)
+d366 1
+a366 1
+#: en_US/publishing.xml:179(para)
+d372 1
+a372 1
+#: en_US/publishing.xml:183(title)
+d376 1
+a376 1
+#: en_US/publishing.xml:184(para)
+d382 1
+a382 1
+#: en_US/publishing.xml:192(title)
+d386 1
+a386 1
+#: en_US/publishing.xml:193(para)
+d390 1
+a390 1
+#: en_US/publishing.xml:197(para)
+d394 1
+a394 1
+#: en_US/publishing.xml:198(screen)
+d412 1
+a412 1
+#: en_US/publishing.xml:214(para)
+d418 1
+a418 1
+#: en_US/publishing.xml:216(replaceable)
+d422 1
+a422 1
+#: en_US/publishing.xml:216(screen)
+d427 1
+a427 1
+#: en_US/publishing.xml:219(para)
+d431 1
+a431 1
+#: en_US/publishing.xml:221(screen)
+d2456 1
+a2456 1
+"which produces the text \"Fedora 7.\""
+d3098 38
+d3875 8
+a3882 1
+#: en_US/getting-files.xml:106(title)
+d3886 1
+a3886 1
+#: en_US/getting-files.xml:107(para)
+d3895 1
+a3895 1
+#: en_US/getting-files.xml:115(para)
+d3905 1
+a3905 1
+#: en_US/getting-files.xml:122(para)
+d3910 1
+a3910 1
+#: en_US/getting-files.xml:125(title)
+d3914 1
+a3914 1
+#: en_US/getting-files.xml:126(userinput)
+d3919 1
+a3919 1
+#: en_US/getting-files.xml:145(para)
+d3927 1
+a3927 1
+#: en_US/getting-files.xml:150(para)
+d3936 1
+a3936 1
+#: en_US/getting-files.xml:157(title)
+d3940 1
+a3940 1
+#: en_US/getting-files.xml:158(para)
+d3947 1
+a3947 1
+#: en_US/getting-files.xml:164(title)
+d3951 1
+a3951 1
+#: en_US/getting-files.xml:165(para)
+d3960 1
+a3960 1
+#: en_US/getting-files.xml:174(title)
+d3964 1
+a3964 1
+#: en_US/getting-files.xml:175(para)
+d3970 1
+a3970 1
+#: en_US/getting-files.xml:181(title)
+d3974 1
+a3974 1
+#: en_US/getting-files.xml:182(segtitle)
+d3978 1
+a3978 1
+#: en_US/getting-files.xml:183(segtitle)
+d3982 1
+a3982 1
+#: en_US/getting-files.xml:185(seg)
+d3986 1
+a3986 1
+#: en_US/getting-files.xml:186(seg)
+d3990 1
+a3990 1
+#: en_US/getting-files.xml:190(application)
+d3994 1
+a3994 1
+#: en_US/getting-files.xml:189(seg)
+d3998 1
+a3998 1
+#: en_US/getting-files.xml:191(seg)
+d4002 1
+a4002 1
+#: en_US/getting-files.xml:194(application)
+d4006 1
+a4006 1
+#: en_US/getting-files.xml:194(seg)
+d4011 1
+a4011 1
+#: en_US/getting-files.xml:195(seg)
+d4015 1
+a4015 1
+#: en_US/getting-files.xml:200(title)
+d4020 1
+a4020 1
+#: en_US/getting-files.xml:201(para)
+d4026 1
+a4026 1
+#: en_US/getting-files.xml:205(para)
+d4032 1
+a4032 1
+#: en_US/getting-files.xml:210(para)
+d4038 1
+a4038 1
+#: en_US/getting-files.xml:215(para)
+d5164 1
+a5164 1
+#~ "<!--$Id: pt_BR.po,v 1.14 2007/08/03 16:39:22 pfrields Exp $ -->\n"
+d5176 1
+a5176 1
+#~ "<!--$Id: pt_BR.po,v 1.14 2007/08/03 16:39:22 pfrields Exp $ -->\n"
+@
+
+
+1.14
+log
+ at Push new 0.3.1 POT and update PO
+@
+text
+ at d7 1
+a7 1
+"POT-Creation-Date: 2007-08-03 12:38-0400\n"
+d80 334
+d5097 1
+a5097 1
+#~ "<!--$Id: pt_BR.po,v 1.13 2007/07/29 23:25:11 pfrields Exp $ -->\n"
+d5109 1
+a5109 1
+#~ "<!--$Id: pt_BR.po,v 1.13 2007/07/29 23:25:11 pfrields Exp $ -->\n"
+a5338 3
+
+#~ msgid "username"
+#~ msgstr "utilizador"
+@
+
+
+1.13
+log
+ at Update POT and PO with new metadata strings
+@
+text
+ at d7 1
+a7 1
+"POT-Creation-Date: 2007-07-28 18:02-0400\n"
+d60 12
+d75 1
+a75 1
+#: en_US/rpm-info.xml:45(details)
+d2533 1
+a2533 1
+#: en_US/emacs.xml:557(title) en_US/emacs-nxml.xml:160(title)
+d2770 1
+a2770 1
+#: en_US/module-struct.xml:46(title)
+d2774 1
+a2774 1
+#: en_US/module-struct.xml:47(segtitle)
+d2778 1
+a2778 1
+#: en_US/module-struct.xml:48(segtitle)
+d2782 1
+a2782 1
+#: en_US/module-struct.xml:49(segtitle)
+d2786 1
+a2786 1
+#: en_US/module-struct.xml:51(seg)
+d2790 2
+a2791 2
+#: en_US/module-struct.xml:52(seg) en_US/module-struct.xml:89(seg)
+#: en_US/module-struct.xml:96(seg)
+d2795 2
+a2796 2
+#: en_US/module-struct.xml:55(filename)
+#: en_US/module-struct.xml:177(systemitem)
+d2800 1
+a2800 1
+#: en_US/module-struct.xml:59(firstterm)
+d2804 1
+a2804 1
+#: en_US/module-struct.xml:60(para)
+d2812 1
+a2812 1
+#: en_US/module-struct.xml:53(seg)
+d2821 1
+a2821 1
+#: en_US/module-struct.xml:68(seg)
+d2825 1
+a2825 1
+#: en_US/module-struct.xml:69(seg) en_US/module-struct.xml:79(seg)
+d2829 1
+a2829 1
+#: en_US/module-struct.xml:70(filename) en_US/module-struct.xml:74(filename)
+d2833 1
+a2833 1
+#: en_US/module-struct.xml:70(seg)
+d2841 1
+a2841 1
+#: en_US/module-struct.xml:78(seg)
+d2845 1
+a2845 1
+#: en_US/module-struct.xml:80(filename) en_US/module-struct.xml:184(filename)
+d2849 1
+a2849 1
+#: en_US/module-struct.xml:82(acronym)
+d2853 9
+a2861 1
+#: en_US/module-struct.xml:80(seg)
+d2867 3
+a2869 1
+"are created as needed from these PO files."
+d2872 1
+a2872 1
+#: en_US/module-struct.xml:88(seg) en_US/module-struct.xml:90(filename)
+d2876 1
+a2876 1
+#: en_US/module-struct.xml:90(seg)
+d2882 1
+a2882 1
+#: en_US/module-struct.xml:95(filename) en_US/module-struct.xml:97(filename)
+d2886 1
+a2886 1
+#: en_US/module-struct.xml:97(seg)
+d2890 1
+a2890 1
+#: en_US/module-struct.xml:102(title)
+d2894 1
+a2894 1
+#: en_US/module-struct.xml:103(para)
+d2902 1
+a2902 1
+#: en_US/module-struct.xml:111(title)
+d2906 1
+a2906 1
+#: en_US/module-struct.xml:116(para)
+d2915 1
+a2915 1
+#: en_US/module-struct.xml:112(para)
+d2924 1
+a2924 1
+#: en_US/module-struct.xml:128(title)
+d2928 1
+a2928 1
+#: en_US/module-struct.xml:129(para)
+d2935 1
+a2935 1
+#: en_US/module-struct.xml:135(para)
+d2941 1
+a2941 1
+#: en_US/module-struct.xml:141(title)
+d2945 1
+a2945 1
+#: en_US/module-struct.xml:158(para)
+d2952 1
+a2952 1
+#: en_US/module-struct.xml:164(title)
+d2956 1
+a2956 1
+#: en_US/module-struct.xml:165(segtitle)
+d2960 1
+a2960 1
+#: en_US/module-struct.xml:166(segtitle) en_US/module-struct.xml:244(segtitle)
+d2964 1
+a2964 1
+#: en_US/module-struct.xml:168(systemitem)
+d2968 1
+a2968 1
+#: en_US/module-struct.xml:169(seg)
+d2974 1
+a2974 1
+#: en_US/module-struct.xml:174(systemitem)
+d2978 1
+a2978 1
+#: en_US/module-struct.xml:175(seg)
+d2984 1
+a2984 13
+#: en_US/module-struct.xml:180(systemitem)
+msgid "OTHERS"
+msgstr ""
+
+#: en_US/module-struct.xml:181(seg)
+msgid ""
+"This variable contains a listing of ISO codes for any other versions into "
+"which the document has been translated. The module must contain a "
+"<placeholder-1/> directory and a PO file for any indicated additional "
+"languages."
+msgstr ""
+
+#: en_US/module-struct.xml:188(systemitem)
+d2988 1
+a2988 1
+#: en_US/module-struct.xml:189(seg)
+d2996 1
+a2996 1
+#: en_US/module-struct.xml:198(systemitem)
+d3000 1
+a3000 1
+#: en_US/module-struct.xml:201(systemitem)
+d3004 1
+a3004 1
+#: en_US/module-struct.xml:206(systemitem)
+d3008 1
+a3008 1
+#: en_US/module-struct.xml:199(seg)
+d3018 1
+a3018 1
+#: en_US/module-struct.xml:212(title)
+d3022 1
+a3022 1
+#: en_US/module-struct.xml:213(para)
+d3028 1
+a3028 1
+#: en_US/module-struct.xml:217(para)
+d3037 1
+a3037 1
+#: en_US/module-struct.xml:226(title)
+d3041 1
+a3041 1
+#: en_US/module-struct.xml:227(para)
+d3050 1
+a3050 1
+#: en_US/module-struct.xml:236(title)
+d3054 1
+a3054 1
+#: en_US/module-struct.xml:237(para)
+d3060 1
+a3060 1
+#: en_US/module-struct.xml:242(title)
+d3064 1
+a3064 1
+#: en_US/module-struct.xml:243(segtitle)
+d3068 1
+a3068 1
+#: en_US/module-struct.xml:246(systemitem)
+d3072 2
+a3073 2
+#: en_US/module-struct.xml:247(abbrev) en_US/module-struct.xml:258(abbrev)
+#: en_US/module-struct.xml:283(abbrev) en_US/module-struct.xml:288(abbrev)
+d3077 2
+a3078 2
+#: en_US/module-struct.xml:251(systemitem)
+#: en_US/module-struct.xml:261(systemitem)
+d3082 2
+a3083 2
+#: en_US/module-struct.xml:252(systemitem)
+#: en_US/module-struct.xml:262(systemitem)
+d3087 1
+a3087 1
+#: en_US/module-struct.xml:250(filename)
+d3091 1
+a3091 1
+#: en_US/module-struct.xml:247(seg)
+d3099 1
+a3099 1
+#: en_US/module-struct.xml:257(systemitem)
+d3103 1
+a3103 1
+#: en_US/module-struct.xml:260(filename)
+d3107 1
+a3107 1
+#: en_US/module-struct.xml:258(seg)
+d3114 1
+a3114 1
+#: en_US/module-struct.xml:266(systemitem)
+d3118 2
+a3119 2
+#: en_US/module-struct.xml:267(abbrev) en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:284(abbrev) en_US/module-struct.xml:289(abbrev)
+d3123 1
+a3123 1
+#: en_US/module-struct.xml:267(seg)
+d3130 1
+a3130 1
+#: en_US/module-struct.xml:272(systemitem)
+d3134 1
+a3134 1
+#: en_US/module-struct.xml:273(command)
+d3138 1
+a3138 1
+#: en_US/module-struct.xml:273(seg)
+d3144 1
+a3144 1
+#: en_US/module-struct.xml:277(systemitem)
+d3148 1
+a3148 1
+#: en_US/module-struct.xml:278(seg)
+d3152 2
+a3153 2
+#: en_US/module-struct.xml:281(systemitem)
+#: en_US/module-struct.xml:290(filename)
+d3157 1
+a3157 1
+#: en_US/module-struct.xml:283(emphasis)
+d3161 1
+a3161 1
+#: en_US/module-struct.xml:282(seg)
+d3167 1
+a3167 1
+#: en_US/module-struct.xml:287(systemitem)
+d3171 1
+a3171 1
+#: en_US/module-struct.xml:288(seg)
+d3177 1
+a3177 1
+#: en_US/module-struct.xml:295(title)
+d3181 1
+a3181 1
+#: en_US/module-struct.xml:296(para)
+d3187 1
+a3187 1
+#: en_US/module-struct.xml:300(title)
+d3191 1
+a3191 1
+#: en_US/module-struct.xml:301(para)
+d3200 1
+a3200 1
+#: en_US/module-struct.xml:309(para)
+d3206 1
+a3206 1
+#: en_US/module-struct.xml:316(title)
+d3210 1
+a3210 1
+#: en_US/module-struct.xml:317(para)
+d3218 1
+a3218 1
+#: en_US/module-struct.xml:324(para)
+d3231 1
+a3231 1
+#: en_US/module-struct.xml:338(para)
+d3238 1
+a3238 1
+#: en_US/module-struct.xml:344(para)
+d3248 1
+a3248 1
+#: en_US/module-struct.xml:354(para)
+d3257 1
+a3257 1
+#: en_US/module-struct.xml:363(para)
+d3263 1
+a3263 1
+#: en_US/module-struct.xml:369(title)
+d3267 1
+a3267 1
+#: en_US/module-struct.xml:376(title)
+d3271 1
+a3271 1
+#: en_US/module-struct.xml:377(para)
+d3276 1
+a3276 1
+#: en_US/module-struct.xml:381(para)
+d3280 1
+a3280 1
+#: en_US/module-struct.xml:385(para)
+d3289 1
+a3289 1
+#: en_US/module-struct.xml:395(title)
+d3293 1
+a3293 1
+#: en_US/module-struct.xml:396(para)
+d3301 1
+a3301 1
+#: en_US/module-struct.xml:403(para)
+d3307 1
+a3307 1
+#: en_US/module-struct.xml:409(para)
+d3311 1
+a3311 1
+#: en_US/module-struct.xml:413(para)
+d3317 1
+a3317 1
+#: en_US/module-struct.xml:418(para)
+d3323 1
+a3323 1
+#: en_US/module-struct.xml:421(replaceable)
+d3327 1
+a3327 1
+#: en_US/module-struct.xml:421(screen)
+d3361 2
+a3362 2
+"This document explains the tools used by the Fedora Documentation Project "
+"and provides writing and tagging guidelines to make Fedora documentation is "
+d3654 1
+a3654 1
+#: en_US/emacs.xml:243(primary) en_US/emacs.xml:518(application)
+d3785 14
+a3798 5
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:522(keycap)
+msgid "Meta"
+msgstr ""
+d3800 5
+a3804 4
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:493(keycap)
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:509(keycap) en_US/emacs.xml:515(keycap)
+msgid "x"
+d3807 2
+a3808 3
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:494(keycap)
+#: en_US/emacs.xml:499(keycap)
+msgid "Enter"
+d3811 2
+a3812 1
+#: en_US/emacs.xml:407(seg)
+d3814 2
+a3815 2
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, "
+"<placeholder-3/>"
+d3818 1
+a3818 1
+#: en_US/emacs.xml:410(seg)
+d3822 1
+a3822 22
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:438(keycap) en_US/emacs.xml:443(keycap)
+#: en_US/emacs.xml:448(keycap) en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:458(keycap) en_US/emacs.xml:463(keycap)
+#: en_US/emacs.xml:468(keycap) en_US/emacs.xml:473(keycap)
+#: en_US/emacs.xml:478(keycap) en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:503(keycap) en_US/emacs.xml:504(keycap)
+#: en_US/emacs.xml:509(keycap) en_US/emacs.xml:510(keycap)
+#: en_US/emacs.xml:515(keycap) en_US/emacs.xml:516(keycap)
+#: en_US/emacs.xml:527(keycap) en_US/emacs.xml:528(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:537(keycap)
+msgid "Ctrl"
+msgstr "Ctrl"
+
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:443(keycap) en_US/emacs.xml:516(keycap)
+#: en_US/emacs.xml:527(keycap) en_US/emacs.xml:535(keycap)
+#: en_US/emacs.xml:537(keycap)
+msgid "c"
+msgstr ""
+
+#: en_US/emacs.xml:426(keycap) en_US/emacs.xml:432(keycap)
+d3826 1
+a3826 1
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:433(keycap)
+d3830 1
+a3830 1
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:434(keycap)
+d3834 1
+a3834 1
+#: en_US/emacs.xml:425(seg)
+d3840 1
+a3840 1
+#: en_US/emacs.xml:428(seg)
+d3844 1
+a3844 1
+#: en_US/emacs.xml:431(seg)
+d3851 1
+a3851 1
+#: en_US/emacs.xml:435(seg)
+d3855 1
+a3855 1
+#: en_US/emacs.xml:438(keycap)
+d3859 1
+a3859 1
+#: en_US/emacs.xml:440(seg)
+d3863 1
+a3863 1
+#: en_US/emacs.xml:444(keycap)
+d3867 1
+a3867 1
+#: en_US/emacs.xml:443(seg)
+d3871 1
+a3871 1
+#: en_US/emacs.xml:445(seg)
+d3875 1
+a3875 1
+#: en_US/emacs.xml:448(keycap) en_US/emacs.xml:528(keycap)
+d3879 1
+a3879 1
+#: en_US/emacs.xml:450(seg)
+d3883 1
+a3883 1
+#: en_US/emacs.xml:453(keycap)
+d3887 1
+a3887 1
+#: en_US/emacs.xml:455(seg)
+d3891 1
+a3891 1
+#: en_US/emacs.xml:458(keycap)
+d3895 1
+a3895 1
+#: en_US/emacs.xml:460(seg)
+d3899 1
+a3899 1
+#: en_US/emacs.xml:463(keycap)
+d3903 1
+a3903 1
+#: en_US/emacs.xml:465(seg)
+d3907 1
+a3907 1
+#: en_US/emacs.xml:468(keycap)
+d3911 1
+a3911 1
+#: en_US/emacs.xml:470(seg)
+d3915 1
+a3915 1
+#: en_US/emacs.xml:473(keycap)
+d3919 1
+a3919 1
+#: en_US/emacs.xml:475(seg)
+d3923 1
+a3923 1
+#: en_US/emacs.xml:478(keycap) en_US/emacs.xml:510(keycap)
+d3927 1
+a3927 1
+#: en_US/emacs.xml:480(seg)
+d3931 1
+a3931 1
+#: en_US/emacs.xml:483(keycap)
+d3935 1
+a3935 1
+#: en_US/emacs.xml:485(seg)
+d3939 6
+a3944 1
+#: en_US/emacs.xml:488(keycap)
+d3948 1
+a3948 1
+#: en_US/emacs.xml:490(seg) en_US/emacs.xml:495(seg)
+d3952 11
+a3962 1
+#: en_US/emacs.xml:493(seg)
+d3968 1
+a3968 1
+#: en_US/emacs.xml:498(seg)
+d3974 1
+a3974 1
+#: en_US/emacs.xml:500(seg)
+d3978 1
+a3978 1
+#: en_US/emacs.xml:504(keycap)
+d3982 1
+a3982 8
+#: en_US/emacs.xml:503(seg) en_US/emacs.xml:509(seg) en_US/emacs.xml:515(seg)
+#: en_US/emacs.xml:527(seg) en_US/emacs.xml:535(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+
+#: en_US/emacs.xml:506(seg)
+d3986 1
+a3986 1
+#: en_US/emacs.xml:512(seg)
+d3990 1
+a3990 1
+#: en_US/emacs.xml:518(seg)
+d3994 1
+a3994 1
+#: en_US/emacs.xml:522(keycap)
+d3998 1
+a3998 1
+#: en_US/emacs.xml:524(seg)
+d4002 1
+a4002 1
+#: en_US/emacs.xml:531(computeroutput)
+d4007 1
+a4007 1
+#: en_US/emacs.xml:532(computeroutput)
+d4012 1
+a4012 1
+#: en_US/emacs.xml:530(seg)
+d4018 1
+a4018 1
+#: en_US/emacs.xml:539(seg)
+d4022 1
+a4022 1
+#: en_US/emacs.xml:545(title) en_US/emacs-nxml.xml:77(title)
+d4026 1
+a4026 1
+#: en_US/emacs.xml:547(para)
+d4032 1
+a4032 1
+#: en_US/emacs.xml:554(title)
+d4036 1
+a4036 1
+#: en_US/emacs.xml:558(para)
+d4040 1
+a4040 1
+#: en_US/emacs.xml:562(para)
+d4048 1
+a4048 1
+#: en_US/emacs.xml:569(prompt)
+d4052 1
+a4052 1
+#: en_US/emacs.xml:571(para)
+d4061 1
+a4061 1
+#: en_US/emacs.xml:580(para)
+d4068 1
+a4068 1
+#: en_US/emacs.xml:597(title)
+d4072 1
+a4072 1
+#: en_US/emacs.xml:599(para)
+d4080 1
+a4080 1
+#: en_US/emacs.xml:611(title)
+d4084 1
+a4084 1
+#: en_US/emacs.xml:614(title)
+d4088 1
+a4088 1
+#: en_US/emacs.xml:615(para)
+d4096 1
+a4096 1
+#: en_US/emacs.xml:625(title)
+d4100 1
+a4100 1
+#: en_US/emacs.xml:626(para)
+d4107 1
+a4107 1
+#: en_US/emacs.xml:637(title)
+d4111 1
+a4111 1
+#: en_US/emacs.xml:638(para)
+d4119 1
+a4119 1
+#: en_US/emacs.xml:648(title)
+d4123 1
+a4123 1
+#: en_US/emacs.xml:649(para)
+d4132 1
+a4132 1
+#: en_US/emacs.xml:663(title)
+d4136 1
+a4136 1
+#: en_US/emacs.xml:664(para)
+d4145 1
+a4145 1
+#: en_US/emacs.xml:682(title) en_US/emacs-nxml.xml:127(title)
+d4149 1
+a4149 1
+#: en_US/emacs.xml:684(para)
+d4155 1
+a4155 1
+#: en_US/emacs.xml:692(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+d4159 1
+a4159 1
+#: en_US/emacs.xml:696(para)
+d4166 1
+a4166 1
+#: en_US/emacs.xml:703(para)
+d4172 1
+a4172 1
+#: en_US/emacs.xml:709(para)
+d4179 1
+a4179 1
+#: en_US/emacs.xml:718(citetitle)
+d4546 7
+a4552 8
+#: en_US/acknowledgments.xml:43(para)
+msgid ""
+"A patch from Paul W. Frields (stickster at gmail.com) has been applied to "
+"add more explanation of the <command>screen</command> tag set to <xref "
+"linkend=\"sn-xml-tags-screen\"/>."
+msgstr ""
+
+#: en_US/acknowledgments.xml:49(para)
+d4763 1
+a4763 1
+#~ "<!--$Id: xml-tags.xml,v 1.6 2007/06/23 05:25:29 pfrields Exp $ -->\n"
+d4768 2
+a4769 1
+#~ " <para>This is a sample chapter, showing you the XML tags used to create a\n"
+d4775 1
+a4775 1
+#~ "<!--$Id: pt_BR.po,v 1.12 2007/06/04 21:22:08 nullck Exp $ -->\n"
+d4780 2
+a4781 1
+#~ " <para>Este é um capítulo de exemplo, mostrando as tag's de XML usadas para criar um capítulo, as seções, e as subseções..</para>\n"
+d4866 2
+a4867 1
+#~ "and use the <command>redhat-config-keyboard</command> command, \n"
+d4872 2
+a4873 1
+#~ "e use os comandos <command>redhat-config-keyboard</command> , \n"
+d4956 2
+a4957 1
+#~ "<computeroutput>Do you want to delete this file? y n</computeroutput>\n"
+d4960 2
+a4961 1
+#~ "<computeroutput>Você quer deletar este arquivo? y n</computeroutput>\n"
+@
+
+
+1.12
+log
+ at some translatio
+@
+text
+ at d7 1
+a7 1
+"POT-Creation-Date: 2007-04-27 17:09-0300\n"
+d17 1
+a17 1
+#: en_US/rpm-info.xml:20(rights)
+d21 1
+a21 1
+#: en_US/rpm-info.xml:21(version)
+d25 1
+a25 1
+#: en_US/rpm-info.xml:24(year)
+d29 3
+a31 2482
+#: en_US/rpm-info.xml:25(year)
+msgid "2004"
+msgstr "2004"
+
+#: en_US/rpm-info.xml:26(year)
+msgid "2005"
+msgstr "2005"
+
+#: en_US/rpm-info.xml:27(year)
+msgid "2006"
+msgstr "2006"
+
+#: en_US/rpm-info.xml:28(holder)
+msgid "Red Hat, Inc."
+msgstr "Red Hat, Inc."
+
+#: en_US/rpm-info.xml:29(holder)
+msgid "Tammy Fox"
+msgstr "Tammy Fox"
+
+#: en_US/rpm-info.xml:30(holder)
+msgid "Johnray Fuller"
+msgstr "Johnray Fuller"
+
+#: en_US/rpm-info.xml:31(holder)
+msgid "Sandra Moore"
+msgstr "Sandra Moore"
+
+#: en_US/rpm-info.xml:32(holder)
+msgid "Paul W. Frields"
+msgstr "Paul W. Frields"
+
+#: en_US/rpm-info.xml:34(title)
+msgid "Fedora Documentation Guide"
+msgstr "Guia de Documentação do Fedora"
+
+#: en_US/rpm-info.xml:35(desc)
+msgid "Guidelines and procedures for producing documentation for Fedora"
+msgstr "Instruções e procedimentos para produção da documentação para o Fedora"
+
+#: en_US/rpm-info.xml:42(details)
+msgid "Update to new build requirements"
+msgstr "Atualizado os novos requisitos de configuração"
+
+#: en_US/xml-tags.xml:13(title)
+msgid "DocBook XML Tags"
+msgstr "Tags do DocBook XML "
+
+#: en_US/xml-tags.xml:16(primary) en_US/xml-tags.xml:34(primary)
+msgid "XML"
+msgstr "XML"
+
+#: en_US/xml-tags.xml:17(secondary)
+msgid "tags"
+msgstr "tags"
+
+#: en_US/xml-tags.xml:18(see) en_US/xml-tags.xml:167(primary)
+#: en_US/xml-tags.xml:205(primary) en_US/xml-tags.xml:241(primary)
+#: en_US/xml-tags.xml:276(primary) en_US/xml-tags.xml:361(primary)
+#: en_US/xml-tags.xml:386(primary) en_US/xml-tags.xml:417(primary)
+#: en_US/xml-tags.xml:471(primary) en_US/xml-tags.xml:523(primary)
+#: en_US/xml-tags.xml:555(primary) en_US/xml-tags.xml:593(primary)
+#: en_US/xml-tags.xml:659(primary) en_US/xml-tags.xml:667(primary)
+#: en_US/xml-tags.xml:673(primary) en_US/xml-tags.xml:703(primary)
+#: en_US/xml-tags.xml:709(primary) en_US/xml-tags.xml:739(primary)
+#: en_US/xml-tags.xml:745(primary) en_US/xml-tags.xml:774(primary)
+#: en_US/xml-tags.xml:780(primary) en_US/xml-tags.xml:785(primary)
+#: en_US/xml-tags.xml:791(primary) en_US/xml-tags.xml:833(primary)
+#: en_US/xml-tags.xml:861(primary) en_US/xml-tags.xml:908(primary)
+#: en_US/xml-tags.xml:963(primary) en_US/xml-tags.xml:968(primary)
+#: en_US/xml-tags.xml:1037(primary) en_US/xml-tags.xml:1047(primary)
+#: en_US/xml-tags.xml:1124(primary) en_US/xml-tags.xml:1129(primary)
+#: en_US/xml-tags.xml:1219(primary) en_US/xml-tags.xml:1224(primary)
+#: en_US/xml-tags.xml:1402(primary) en_US/xml-tags.xml:1407(primary)
+#: en_US/xml-tags.xml:1490(primary) en_US/xml-tags.xml:1533(primary)
+#: en_US/xml-tags.xml:1642(primary) en_US/xml-tags.xml:1688(primary)
+#: en_US/xml-tags.xml:1738(primary) en_US/xml-tags.xml:1782(primary)
+#: en_US/xml-tags.xml:1812(primary) en_US/xml-tags.xml:1983(primary)
+#: en_US/xml-tags.xml:2055(primary) en_US/xml-tags.xml:2174(primary)
+#: en_US/xml-tags.xml:2313(primary) en_US/xml-tags.xml:2341(primary)
+#: en_US/xml-tags.xml:2396(primary) en_US/xml-tags.xml:2437(primary)
+#: en_US/xml-tags.xml:2484(primary) en_US/writing-guidelines.xml:41(primary)
+#: en_US/writing-guidelines.xml:54(primary)
+#: en_US/writing-guidelines.xml:266(primary)
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:276(primary)
+#: en_US/writing-guidelines.xml:281(primary)
+#: en_US/writing-guidelines.xml:286(primary)
+#: en_US/writing-guidelines.xml:291(primary)
+#: en_US/writing-guidelines.xml:297(primary)
+#: en_US/writing-guidelines.xml:303(primary)
+#: en_US/writing-guidelines.xml:309(primary)
+#: en_US/writing-guidelines.xml:315(primary)
+#: en_US/writing-guidelines.xml:341(primary)
+#: en_US/writing-guidelines.xml:346(primary)
+#: en_US/writing-guidelines.xml:351(primary)
+#: en_US/writing-guidelines.xml:356(primary)
+#: en_US/writing-guidelines.xml:361(primary)
+msgid "XML tags"
+msgstr "tags XML"
+
+#: en_US/xml-tags.xml:21(para)
+msgid ""
+"Please read this chapter carefully. This chapter describes the tags used by "
+"the Docs Project. Some of the rules described are specific to the project."
+msgstr ""
+"Por favor leia este capítulo com cuidado. Este capítulo descreve as tags "
+"usadas pelo Projeto Docs. Algumas das regras descritas são específicas para "
+"o projeto."
+
+#: en_US/xml-tags.xml:26(para)
+msgid ""
+"If these tags are used appropriately, document searches will provide "
+"meaningful results. These tags help search engines identify the information "
+"relevant to the search request. Another benefit is that all Fedora Project "
+"documents will have a similar look and feel (however, they will have some "
+"differences depending upon the output format)."
+msgstr ""
+"Se estas tags forem usadas apropriadamente, as buscas fornecerão resultados "
+"significativos. Estas formas de busca com auxilio de tags, identificam a "
+"informação relevante à requisição de busca. Um outro benefício é que todos "
+"os documentos do Projeto Fedora possuirão um visual similar (entretanto, "
+"terão algumas diferenças dependendo do formato de saída)."
+
+#: en_US/xml-tags.xml:35(secondary)
+msgid "general tag information"
+msgstr "Informação geral da tag"
+
+#: en_US/xml-tags.xml:38(para)
+msgid ""
+"Most tags in XML must have an opening and closing tag. A few tags, such as "
+"<sgmltag class=\"emptytag\">xref</sgmltag>, have no content and close "
+"themselves. Additionally, proper XML conventions say that there must be a "
+"unique identifier for sections, chapters, figures, tables, and so on, so "
+"that they may be correctly identified, and cross referenced if needed."
+msgstr ""
+"A maioria das tags em XML devem ter uma tag de abertura e uma tag de "
+"fechamento. Algumas tags, tais como <sgmltag class=\"emptytag\">xref</"
+"sgmltag>, não têm nenhum conteúdo e depois são fechadas. Adicionalmente, as "
+"convenções apropriadas de XML dizem que deve haver um identificador original "
+"para seções, capítulos, figuras, tabelas, e assim por diante, de modo que "
+"possam corretamente ser identificadas, e se necessário é feito auto remissão."
+
+#: en_US/xml-tags.xml:45(para)
+msgid ""
+"Although XML is capable of handling many document types, the format "
+"discussed here is the article format."
+msgstr ""
+"Embora originalmente XML seja capaz de manipular vários tipos de formato, o "
+"formato discutido aqui é o formato de artigo."
+
+#: en_US/xml-tags.xml:48(para) en_US/writing-guidelines.xml:32(para)
+msgid ""
+"This chapter only discusses tags used for documentation for the Fedora "
+"Project, not all available DocBook XML tags. For the complete list, refer to "
+"<ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr ""
+"Este capítulo discute somente as tag usadas para a documentação do Projeto "
+"Fedora e não todas as tags disponíveis do DocBook XML. Para a lista "
+"completa, visite <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html"
+"\"/>."
+
+#: en_US/xml-tags.xml:56(title)
+msgid "Tags and Entities Caveats"
+msgstr "Tag e Caveats das entidades"
+
+#: en_US/xml-tags.xml:59(primary) en_US/writing-guidelines.xml:137(primary)
+msgid "xml tags"
+msgstr "tags xml"
+
+#: en_US/xml-tags.xml:60(secondary)
+#: en_US/writing-guidelines.xml:138(secondary)
+msgid "caveats"
+msgstr "caveats"
+
+#: en_US/xml-tags.xml:63(para)
+msgid ""
+"It is very important that you remember the caveats in this section. Even "
+"though they are more strict than valid DocBook XML, these rules exist so "
+"that both the HTML and PDF outputs look proper."
+msgstr ""
+"É muito importante que você recorde os caveats nesta seção. Mesmo que sejam "
+"mais simplificados do que o XML DocBook válido , estas régras existem de "
+"modo que as saídas do HTML e do pdf sejam visualizadas apropriadamente."
+
+#: en_US/xml-tags.xml:71(term) en_US/writing-guidelines.xml:149(term)
+msgid "Do Not Use Trademark Entities"
+msgstr "Não Use Entidades de Marca Registrada"
+
+#: en_US/xml-tags.xml:73(para)
+msgid ""
+"Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+"\"genentity\">reg</sgmltag> because they do not produce HTML output that "
+"works for all charsets. The HTML output produces by these entities are "
+"declared in the DTD and cannot be changed via the stylesheet."
+msgstr ""
+"Não use entidades de marca registrada<sgmltag class=\"genentity\"> trade</"
+"sgmltag>, <sgmltag class=\"genentity\"> copy</sgmltag>, ou <sgmltag class="
+"\"genentity\"> reg</sgmltag> porque não produzem a saida em HTML que funcione "
+"com todos os charsets. A saída em HTML produzida por estas entidades é "
+"declarada no DTD e não pode ser mudada através da planilha de estilo."
+
+#: en_US/xml-tags.xml:80(para)
+msgid ""
+"Instead, use the <sgmltag class=\"element\">trademark</sgmltag> tag and its "
+"associates classes as follows:"
+msgstr ""
+"Preferêncialmente , use a tag <sgmltag class=\"element\">trademark</"
+"sgmltag>e suas classes associadas como segue:"
+
+#: en_US/xml-tags.xml:85(para) en_US/writing-guidelines.xml:164(para)
+msgid ""
+"<sgmltag class=\"starttag\">trademark</sgmltag>trademark symbol after "
+"me<sgmltag class=\"endtag\">trademark</sgmltag>"
+msgstr ""
+"<sgmltag class=\"starttag\">trademark</sgmltag> é simbolo de trademark "
+"<sgmltag class=\"endtag\">trademark </sgmltag>"
+
+#: en_US/xml-tags.xml:91(para) en_US/writing-guidelines.xml:170(para)
+msgid ""
+"<sgmltag class=\"starttag\">trademark class=\"registered\"</"
+"sgmltag>registered trademark symbol after me<sgmltag class=\"endtag"
+"\">trademark</sgmltag>"
+msgstr ""
+"<sgmltag class=\"starttag\">trademark class=\"registered\"</sgmltag>simbolo "
+"de trademark registrada<sgmltag class=\"endtag\">trademark</sgmltag>"
+
+#: en_US/xml-tags.xml:97(para) en_US/writing-guidelines.xml:176(para)
+msgid ""
+"<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag>copyright "
+"symbol after me<sgmltag class=\"endtag\">trademark</sgmltag>"
+msgstr ""
+"<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag> simbolo "
+"de copyright <sgmltag class=\"endtag\">trademark</sgmltag>"
+
+#: en_US/xml-tags.xml:105(term) en_US/writing-guidelines.xml:184(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr "Conteúdo dentro de tags <sgmltag>para</sgmltag>"
+
+#: en_US/xml-tags.xml:107(para)
+msgid ""
+"Do not use <sgmltag>para</sgmltag> tags around anything other than a simple "
+"paragraph. Doing so will create additional white space within the text "
+"itself in the PDF version."
+msgstr "Não use Tag <sgmltag>para</sgmltag> entre qualquer conteúdo com excessão de um parágrafo simples. Fazendo assim você criará um espaço em branco dentro do próprio texto na versão do pdf."
+
+#: en_US/xml-tags.xml:112(para)
+msgid ""
+"Specifically, do not use <sgmltag>para</sgmltag> tags around the following "
+"(or, to put this another way, do not embed the following within "
+"<sgmltag>para</sgmltag> tags):"
+msgstr "Especificamente, não use Tag <sgmltag>para</sgmltag> entre o seguinte conteúdo(ou, para pôr de outra maneira, não deixe o seguinte conteúdo dentro das Tag <sgmltag>para</sgmltag>):"
+
+#: en_US/xml-tags.xml:118(sgmltag) en_US/xml-tags.xml:1810(command)
+#: en_US/xml-tags.xml:1813(secondary)
+#: en_US/writing-guidelines.xml:198(sgmltag)
+msgid "screen"
+msgstr "screen"
+
+#: en_US/xml-tags.xml:121(sgmltag) en_US/xml-tags.xml:960(command)
+#: en_US/xml-tags.xml:964(command) en_US/xml-tags.xml:970(tertiary)
+#: en_US/xml-tags.xml:975(command) en_US/writing-guidelines.xml:201(sgmltag)
+msgid "itemizedlist"
+msgstr "itemizedlist"
+
+#: en_US/xml-tags.xml:124(sgmltag) en_US/xml-tags.xml:1038(command)
+#: en_US/xml-tags.xml:1043(command) en_US/xml-tags.xml:1049(tertiary)
+#: en_US/writing-guidelines.xml:204(sgmltag)
+msgid "orderedlist"
+msgstr "orderedlist"
+
+#: en_US/xml-tags.xml:127(sgmltag) en_US/xml-tags.xml:1125(command)
+#: en_US/xml-tags.xml:1131(tertiary) en_US/xml-tags.xml:1136(command)
+#: en_US/writing-guidelines.xml:207(sgmltag)
+msgid "variablelist"
+msgstr "variablelist"
+
+#: en_US/xml-tags.xml:130(sgmltag) en_US/xml-tags.xml:2052(command)
+#: en_US/xml-tags.xml:2056(secondary) en_US/xml-tags.xml:2175(secondary)
+#: en_US/writing-guidelines.xml:111(sgmltag)
+#: en_US/writing-guidelines.xml:210(sgmltag)
+msgid "table"
+msgstr "table"
+
+#: en_US/xml-tags.xml:136(term)
+msgid ""
+"Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+"sgmltag> tags"
+msgstr "Conteúdo em tags <sgmltag>para</sgmltag> dentro de tags <sgmltag>listitem</sgmltag>"
+
+#: en_US/xml-tags.xml:139(para)
+msgid ""
+"Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+"sgmltag> tags <emphasis>must</emphasis> start immediately after the "
+"beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra "
+"white space in the PDF version."
+msgstr ""
+"Índice de tags <sgmltag> dentro das tags </sgmltag> listitem </sgmltag> tags <emphasis>must</emphasis> começar imediatamente depois da tag <sgmltag class=\"starttag\">para</sgmltag>"
+"para evitar o espaço branco extra na versão do pdf."
+
+#: en_US/xml-tags.xml:148(term) en_US/writing-guidelines.xml:227(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr "Índice dentro dos Tag de <sgmltag> screen</sgmltag>"
+
+#: en_US/xml-tags.xml:150(para) en_US/writing-guidelines.xml:229(para)
+msgid ""
+"The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag"
+"\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis> be flush left in the XML file; otherwise, the "
+"extraneous whitespace will appear in the HTML version."
+msgstr ""
+"O índice dentro das<sgmltag>screen</sgmltag>tags(<sgmltag class=\"starttag"
+"\">screen</sgmltag>e<sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis>seja alinhada a esquerda na linha do XML; se não, aparecerá um espaço em branco na versão do HTML."
+
+#: en_US/xml-tags.xml:164(sgmltag) en_US/xml-tags.xml:168(secondary)
+#: en_US/xml-tags.xml:182(sgmltag) en_US/xml-tags.xml:183(sgmltag)
+#: en_US/xml-tags.xml:184(sgmltag) en_US/xml-tags.xml:185(sgmltag)
+msgid "application"
+msgstr "Aplicação"
+
+#: en_US/xml-tags.xml:171(para)
+msgid ""
+"An application is the name of a GUI software program. A command is the name "
+"of an executable (text) program or a software command."
+msgstr "Uma aplicação é o nome de um programa, feito por um o software com GUI. Um comando é o nome de um programa executável (texto) ou de um comando do próprio o software."
+
+#: en_US/xml-tags.xml:174(para)
+msgid ""
+"The <sgmltag class=\"starttag\">application</sgmltag> and <sgmltag class="
+"\"endtag\">application</sgmltag> tags allow you to refer to an application "
+"or program. For example, the following XML:"
+msgstr ""
+"A <sgmltag class=\"starttag\">application</sgmltag> e <sgmltag class="
+"\"endtag\">application</sgmltag> são os tags que permitem que você consulte a uma aplicação ou a um programa. Por exemplo, o seguinte XML:"
+
+#: en_US/xml-tags.xml:180(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To view the Web in Linux, you can use\n"
+"<placeholder-1/>Mozilla<placeholder-2/> \n"
+"or <placeholder-3/>lynx<placeholder-4/> if\n"
+"you only want a text-based browser.\n"
+msgstr ""
+"\n"
+"Para ver uma página WEB no Linux, você pode usar\n"
+"<placeholder-1/>Mozilla<placeholder-2/> \n"
+"ou <placeholder-3/>lynx<placeholder-4/> se\n"
+"você quer somente um browser baseado em texto.\n"
+
+#: en_US/xml-tags.xml:190(para)
+msgid "produces the following output:"
+msgstr "produz a seguinte saida: "
+
+#: en_US/xml-tags.xml:194(para)
+msgid ""
+"To view the Web in Linux, you can use <application>Mozilla</application> or "
+"<application>lynx</application> if you only want a text-based browser."
+msgstr "Para ver uma pagina WEB no Linux, você pode usar Mozilla ou lynx se você quiser somente um browser baseado em texto."
+
+#: en_US/xml-tags.xml:202(sgmltag) en_US/xml-tags.xml:206(secondary)
+#: en_US/writing-guidelines.xml:99(sgmltag)
+msgid "chapter"
+msgstr "Capitulo"
+
+#: en_US/xml-tags.xml:209(para)
+msgid "A DocBook book can be divided into chapters such as:"
+msgstr "O livro DocBook pode ser dividido em capítulos como:"
+
+#: en_US/xml-tags.xml:214(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<!--$Id: pt_BR.po,v 1.11 2007/05/28 21:02:06 nullck Exp $ -->\n"
+"\n"
+" <chapter id=\"ch-sample\">\n"
+" <title>Sample Chapter</title>\n"
+"\n"
+" <para>This is a sample chapter, showing you the XML tags used to create a\n"
+" chapter, sections, and subsections.</para>\n"
+" \n"
+" </chapter>\n"
+msgstr ""
+"\n"
+"<!--$Id: pt_BR.po,v 1.11 2007/05/28 21:02:06 nullck Exp $ -->\n"
+"\n"
+" <chapter id=\"ch-sample\">\n"
+" <title>Capitulo de Exemplo</title>\n"
+"\n"
+" <para>Este é um capítulo de exemplo, mostrando as tag's de XML usadas para criar um capítulo, as seções, e as subseções..</para>\n"
+" \n"
+" </chapter>\n"
+
+#: en_US/xml-tags.xml:227(para)
+msgid ""
+"The chapter can also be further divided into sections (<sgmltag>section</"
+"sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). Refer "
+"to <xref linkend=\"sn-xml-tags-sections\"/> for details."
+msgstr ""
+"O capítulo pode também ser dividido em subseções(<sgmltag>section</"
+"sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.).Referência"
+" <xref linkend=\"sn-xml-tags-sections\"/> para detalhes"
+
+#: en_US/xml-tags.xml:238(sgmltag) en_US/xml-tags.xml:242(secondary)
+#: en_US/xml-tags.xml:262(sgmltag)
+msgid "citetitle"
+msgstr "Titulo Citado"
+
+#: en_US/xml-tags.xml:249(para)
+msgid ""
+"An entity is a short hand way of referring to some predefined content, such "
+"as a title or name. It can be defined within the parent document or within a "
+"set of files that your DTD references for your specific documentation set."
+msgstr " Uma entidade é uma maneira pratica de consultar algum índice predefinido, tal como um título ou um nome. O mesmo pode ser definido dentro do documento pai ou dentro de um conjunto de arquivos que sua DTD referência, para suas configurações específicas de documentação"
+
+#: en_US/xml-tags.xml:246(para)
+msgid ""
+"The <sgmltag>citetitle</sgmltag> tag provides formatting for a specific "
+"references (title can be manually typed out or if already defined within "
+"your document set, given as an entity<footnote><placeholder-1/></footnote> )."
+msgstr ""
+"A tag<sgmltag>titulo citado</sgmltag> fornece um formato especifico de referências"
+"(o título pode ser digitado manualmente para uma saída ou se pode ser definido dentro de um padrão, dado como uma entidade<footnote><placeholder-1/></footnote> )."
+
+#: en_US/xml-tags.xml:257(para) en_US/xml-tags.xml:2456(para)
+msgid "For example:"
+msgstr "Por exemplo:"
+
+#: en_US/xml-tags.xml:262(sgmltag)
+msgid "IG"
+msgstr "IG"
+
+#: en_US/xml-tags.xml:261(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+msgstr ""
+"\n"
+"<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+
+#: en_US/xml-tags.xml:265(para)
+msgid ""
+"The output looks like <citetitle>Installation Guide</citetitle> because "
+"<sgmltag class=\"genentity\">IG</sgmltag> is an entity."
+msgstr "A saída é visualizada como a <citetitle>Guia da Instalação </citetitle> porque <sgmltag class=\"genentity\">IG</sgmltag> é uma entidade."
+
+#: en_US/xml-tags.xml:273(sgmltag) en_US/xml-tags.xml:277(secondary)
+msgid "command"
+msgstr "comando"
+
+#: en_US/xml-tags.xml:280(para)
+msgid ""
+"An application is the name of a GUI software program. A command is the name "
+"of an executable (text) program or a software command. Any program that is a "
+"command line or text-based only tool is marked with <sgmltag>command</"
+"sgmltag> tags."
+msgstr ""
+"Uma aplicação é o nome de um programa, feito por um o software com GUI. Um comando é o nome de um programa executável (texto) ou de um comando do próprio o software.Todo o programa que for uma linha de comando ou somente uma ferramenta baseada em texto é marcado com <sgmltag>command</"
+"sgmltag> tags."
+
+#: en_US/xml-tags.xml:286(para)
+msgid ""
+"If you have text that is a command, use the <sgmltag class=\"starttag"
+"\">command</sgmltag> and <sgmltag class=\"endtag\">command</sgmltag> tags "
+"such as:"
+msgstr ""
+"Se você tiver uma linha de comando, use o <sgmltag class=\"starttag"
+"\">command</sgmltag> e <sgmltag class=\"endtag\">command</sgmltag> tags como:"
+
+#: en_US/xml-tags.xml:294(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To change your keyboard after installation, become root \n"
+"and use the <command>redhat-config-keyboard</command> command, \n"
+"or you can type <command>setup</command> at the root prompt.\n"
+msgstr ""
+"\n"
+"Para mudar seu teclado após a instalação, se torne root \n"
+"e use os comandos <command>redhat-config-keyboard</command> , \n"
+"ou você pode digitar <command>setup</command> no terminal.\n"
+
+#: en_US/xml-tags.xml:301(para) en_US/xml-tags.xml:374(para)
+#: en_US/xml-tags.xml:402(para) en_US/xml-tags.xml:446(para)
+#: en_US/xml-tags.xml:485(para) en_US/xml-tags.xml:500(para)
+#: en_US/xml-tags.xml:540(para) en_US/xml-tags.xml:575(para)
+#: en_US/xml-tags.xml:689(para) en_US/xml-tags.xml:725(para)
+#: en_US/xml-tags.xml:759(para) en_US/xml-tags.xml:816(para)
+#: en_US/xml-tags.xml:849(para) en_US/xml-tags.xml:887(para)
+#: en_US/xml-tags.xml:927(para) en_US/xml-tags.xml:1515(para)
+#: en_US/xml-tags.xml:1756(para) en_US/xml-tags.xml:1800(para)
+#: en_US/xml-tags.xml:1868(para) en_US/xml-tags.xml:2357(para)
+#: en_US/xml-tags.xml:2411(para) en_US/xml-tags.xml:2464(para)
+#: en_US/xml-tags.xml:2504(para)
+msgid "The output:"
+msgstr "A saída: "
+
+#: en_US/xml-tags.xml:304(para)
+msgid ""
+"To change your keyboard after installation, become root and use the "
+"<command>redhat-config-keyboard</command> command, or you can type "
+"<command>setup</command> at the root prompt."
+msgstr ""
+"Para mudar seu teclado após a instalação, se torne root"
+"e use os comandos<command>redhat-config-keyboard</command> ou você pode digitar "
+"<command>setup</command> no terminal."
+
+#: en_US/xml-tags.xml:310(para)
+msgid "Another example would be:"
+msgstr "Um outro exemplo seria"
+
+#: en_US/xml-tags.xml:313(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<command>MAILNOVIOLATIONS</command> — If set\n"
+"to <command>true</command> this option tells Tripwire to\n"
+"email a report at a regular interval regardless of whether or not\n"
+"any violations have occured. The default value is\n"
+"<command>true</command>.\n"
+msgstr ""
+"\n"
+"<command>MAILNOVIOLATIONS</command> — Se \n"
+"for <command>true</command>esta opção envia ao Tripwire\n"
+"um relatório regular por e-mail em caso de ocorrer ou não \n"
+"violações. O valor padrão é \n"
+"<command>true</command>.\n"
+
+#: en_US/xml-tags.xml:322(para)
+msgid "with the output:"
+msgstr "com a saída:"
+
+#: en_US/xml-tags.xml:326(para)
+msgid ""
+"<command>MAILNOVIOLATIONS</command>— If set to <command>true</command> "
+"this variable tells Tripwire to email a report at a regular interval "
+"regardless of whether or not any violations have occured. The default value "
+"is <command>true</command>."
+msgstr "<command>MAILNOVIOLATIONS</command> — Se for marcado como <command> true</command> esta opção envia ao Tripwire um relatório regular por e-mail em caso de ocorrer ou não violações. O valor padrão é <command>true</command>"
+
+#: en_US/xml-tags.xml:334(title) en_US/xml-tags.xml:509(title)
+#: en_US/xml-tags.xml:988(title) en_US/xml-tags.xml:1063(title)
+#: en_US/xml-tags.xml:1147(title) en_US/xml-tags.xml:1387(title)
+#: en_US/xml-tags.xml:1500(title) en_US/xml-tags.xml:1769(title)
+#: en_US/xml-tags.xml:1930(title) en_US/xml-tags.xml:2422(title)
+#: en_US/writing-guidelines.xml:394(title) en_US/emacs.xml:265(title)
+#: en_US/emacs.xml:565(title) en_US/emacs-nxml.xml:160(title)
+msgid "Note"
+msgstr "Nota"
+
+#: en_US/xml-tags.xml:334(para)
+msgid ""
+"In this example, the option value (true) is defined with a <command> "
+"tag set. Because a option is a configuration file option (command line "
+"options which would use the <option> tag set), and because there is no "
+"configuration file option tag available to use, we are extending the <"
+"command> tag set to define options in a configuration file."
+msgstr "Neste exemplo, o valor da opção (true) é definido com um conjunto <command> de tag's. Porque a opção é uma opção do arquivo de configuração (a linha de comando options que usaria a tag <opção> ajustada), e porque não há nenhuma tag de opção da linha da configuração disponível para se usar, nós iremos extender o; <command> conjunto das tag's para definir essa opções em um arquivo de configuração."
+
+#: en_US/xml-tags.xml:342(para)
+msgid ""
+"Terms marked with <command>command</command> tags because there aren't exact "
+"tags for them:"
+msgstr "Os termos são marcados com <command>command</command> tags porque não há tag exatas para ele:"
+
+#: en_US/xml-tags.xml:348(para)
+msgid "Options in configuration files such as Apache directives"
+msgstr "Opções do arquivo de configuração assim como diretivas do Apache"
+
+#: en_US/xml-tags.xml:351(para)
+msgid "daemon names"
+msgstr "Nomes dos Deamons"
+
+#: en_US/xml-tags.xml:358(command) en_US/xml-tags.xml:362(secondary)
+msgid "computeroutput"
+msgstr "computeroutput"
+
+#: en_US/xml-tags.xml:365(para)
+msgid "To show computer output use the following tags:"
+msgstr "Para exibir a computeroutput use as seguintes tags:"
+
+#: en_US/xml-tags.xml:369(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<computeroutput>Do you want to delete this file? y n</computeroutput>\n"
+msgstr ""
+"\n"
+"<computeroutput>Você quer deletar este arquivo? y n</computeroutput>\n"
+
+#: en_US/xml-tags.xml:378(computeroutput)
+#, no-wrap
+msgid "Do you really want to delete this file? y n"
+msgstr "Você realmente quer deletar este arquivo? y n"
+
+#: en_US/xml-tags.xml:383(command) en_US/xml-tags.xml:387(secondary)
+msgid "emphasis"
+msgstr "emphasis"
+
+#: en_US/xml-tags.xml:390(para)
+msgid ""
+"To emphasis content, use the <command><emphasis></command> and "
+"<command></emphasis></command> tags. For example:"
+msgstr ""
+"Para dar ênfase ao indice, use as tags <command><emphasis></command> e "
+"<command></emphasis></command>. Por exemplo:"
+
+#: en_US/xml-tags.xml:395(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"This installation <emphasis>will remove all</emphasis> existing\n"
+"Linux partitions on <emphasis>all</emphasis> hard drives in your\n"
+"system; non-Linux partitions will not be removed.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:406(para)
+msgid ""
+"This installation <emphasis>will remove all</emphasis> existing Linux "
+"partitions on <emphasis>all</emphasis> hard drives in your system; non-Linux "
+"partitions will not be removed."
+msgstr ""
+
+#: en_US/xml-tags.xml:414(command) en_US/xml-tags.xml:418(secondary)
+#: en_US/writing-guidelines.xml:123(sgmltag)
+msgid "example"
+msgstr "exemplo"
+
+#: en_US/xml-tags.xml:421(para)
+msgid ""
+"The <command><example></command> and <command></example></"
+"command> tags are used to format text within a document and is great for "
+"adding emphasis to show examples of code, exercises, and more."
+msgstr ""
+
+#: en_US/xml-tags.xml:426(para)
+msgid ""
+"The <command><example></command> tag set should be given an ID and "
+"title:"
+msgstr ""
+
+#: en_US/xml-tags.xml:429(screen)
+#, no-wrap
+msgid ""
+"\n"
+"\t<example id=\"static-ip\">\n"
+"\t <title>Static IP Address using DHCP</title>\n"
+"\n"
+"<screen width=60>\n"
+"<computeroutput>\n"
+"host apex {\n"
+" option host-name \"apex.example.com\";\n"
+" hardware ethernet 00:A0:78:8E:9E:AA; \n"
+" fixed-address 192.168.1.4;\n"
+"}\n"
+"<computeroutput>\n"
+"</screen>\n"
+"\n"
+"\t</example>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:451(title)
+msgid "Static IP Address using DHCP"
+msgstr ""
+
+#: en_US/xml-tags.xml:454(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"host apex {\n"
+" option host-name \"apex.example.com\";\n"
+" hardware ethernet 00:A0:78:8E:9E:AA; \n"
+" fixed-address 192.168.1.4;\n"
+"}\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:468(command) en_US/xml-tags.xml:472(secondary)
+msgid "filename"
+msgstr "nome do arquivo"
+
+#: en_US/xml-tags.xml:475(para)
+msgid ""
+"The <command><filename></command> and <command></filename></"
+"command> tags define a filename or path to a file. Since directories are "
+"just special files, they are marked with the <command>filename</command> "
+"tags as well. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:481(screen)
+#, no-wrap
+msgid ""
+"\n"
+"Edit the <filename>/home/smoore/sam.xml</filename> file to make\n"
+"changes or add comments.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:488(para)
+msgid ""
+"Edit the <filename>/home/smoore/sam.xml</filename> file to make changes or "
+"add comments."
+msgstr ""
+
+#: en_US/xml-tags.xml:493(para)
+msgid "They are also used to markup an RPM package name. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:496(screen)
+#, no-wrap
+msgid ""
+"\n"
+"To use the <application>Keyboard Configuration Tool</application>, the\n"
+"<filename>system-config-keyboard</filename> RPM package must be installed.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:503(para)
+msgid ""
+"To use the <application>Keyboard Configuration Tool</application>, the "
+"<command>redhat-config-keyboard</command> RPM package must be installed."
+msgstr ""
+
+#: en_US/xml-tags.xml:510(para)
+msgid ""
+"Directory names must end with a forward slash (<computeroutput>/</"
+"computeroutput>) to distinguish them from file names."
+msgstr ""
+
+#: en_US/xml-tags.xml:520(command) en_US/xml-tags.xml:524(secondary)
+msgid "firstterm"
+msgstr ""
+
+#: en_US/xml-tags.xml:527(para)
+msgid ""
+"The <command><firstterm></command> and <command></firstterm></"
+"command> tags helps to define a word that may be unfamiliar to the user, but "
+"that will be seen commonly throughout the text. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:534(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Nearly every modern-day operating system uses <firstterm>disk\n"
+"partitions</firstterm>, and Fedora is no exception.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:544(para)
+msgid ""
+"Nearly every modern-day operating system uses <firstterm>disk partitions</"
+"firstterm>, and Fedora is no exception."
+msgstr ""
+
+#: en_US/xml-tags.xml:552(command) en_US/xml-tags.xml:556(secondary)
+msgid "footnote"
+msgstr ""
+
+#: en_US/xml-tags.xml:559(para)
+msgid "If you need to make a footnote, use the following example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:563(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"For those of you who need to perform a server-class\n"
+"<footnote>\n"
+"<para>\n"
+"A server-class installation sets up a typical server\n"
+"environment. Note, no graphical environment is \n"
+"installed during a server-class installation.\n"
+"</para> \n"
+"</footnote> installation, refer to the <citetitle>Installation Guide</citetitle>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:580(para)
+msgid ""
+"A server-class installation sets up a typical server environment. Please "
+"note, no graphical environment is installed during a server-class "
+"installation."
+msgstr ""
+
+#: en_US/xml-tags.xml:579(para)
+msgid ""
+"For those of you who need to perform a server-class <footnote><placeholder-1/"
+"></footnote> installation, refer to the <citetitle>Installation Guide</"
+"citetitle>."
+msgstr ""
+
+#: en_US/xml-tags.xml:590(command) en_US/xml-tags.xml:594(secondary)
+#: en_US/writing-guidelines.xml:107(sgmltag)
+msgid "figure"
+msgstr ""
+
+#: en_US/xml-tags.xml:598(title) en_US/xml-tags.xml:1827(title)
+#: en_US/writing-guidelines.xml:424(title) en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr "Importante"
+
+#: en_US/xml-tags.xml:599(para)
+msgid "Order matters! The EPS file <emphasis>must</emphasis> be declared first."
+msgstr ""
+
+#: en_US/xml-tags.xml:605(para)
+msgid "An example figure declaration:"
+msgstr ""
+
+#: en_US/xml-tags.xml:610(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<figure id=\"fig-ksconfig-basic\">\n"
+" <title>Basic Configuration</title>\n"
+" <mediaobject>\n"
+" <imageobject>\n"
+" <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.eps\"\n"
+" format=\"EPS\"/>\n"
+" </imageobject>\n"
+" <imageobject>\n"
+" <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.png\"\n"
+" format=\"PNG\"/>\n"
+" </imageobject>\n"
+" <textobject>\n"
+" <phrase>\n"
+" Some text description of this image\n"
+" </phrase>\n"
+" </textobject>\n"
+" </mediaobject>\n"
+"</figure>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:632(para)
+msgid "The following describes what needs to be edited:"
+msgstr ""
+
+#: en_US/xml-tags.xml:637(emphasis)
+msgid "==> id=\"\" would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:639(emphasis)
+msgid "==> title would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:641(emphasis)
+msgid "==> .eps location would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:643(emphasis)
+msgid "==> .png location would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:645(emphasis)
+msgid "==> \"Some text...\" would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:636(screen)
+#, no-wrap
+msgid ""
+"\n"
+"<figure id=\"fig-ksconfig-basic\"> <placeholder-1/>\n"
+"\n"
+"<title>Basic Configuration</title> <placeholder-2/>\n"
+"\n"
+"fileref=\"./figs/ksconfig/ksconfig-basics.eps\"> <placeholder-3/>\n"
+"\n"
+"fileref=\"./figs/ksconfig/ksconfig-basics.png\"> <placeholder-4/>\n"
+" \n"
+"<phrase>Some text description of this image</phrase> <placeholder-5/>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:648(para)
+msgid ""
+"For more information on taking screenshots, refer to <xref linkend=\"sn-"
+"screenshots\"/>."
+msgstr ""
+
+#: en_US/xml-tags.xml:656(title)
+msgid "GUI Tags"
+msgstr ""
+
+#: en_US/xml-tags.xml:660(secondary) en_US/xml-tags.xml:668(secondary)
+#: en_US/xml-tags.xml:704(secondary) en_US/xml-tags.xml:740(secondary)
+#: en_US/xml-tags.xml:775(secondary) en_US/xml-tags.xml:786(secondary)
+msgid "GUI tags"
+msgstr ""
+
+#: en_US/xml-tags.xml:664(command) en_US/xml-tags.xml:669(tertiary)
+#: en_US/xml-tags.xml:674(secondary)
+msgid "guilabel"
+msgstr ""
+
+#: en_US/xml-tags.xml:677(para)
+msgid ""
+"Use the <command><guilabel></command> and <command></guilabel></"
+"command> tags as a default for GUI descriptions, like a screen name or "
+"screen title. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:683(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"The <guilabel>Authentication Configuration</guilabel> screen \n"
+"shows you how to make your system more secure.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:693(para)
+msgid ""
+"The <guilabel>Authentication Configuration</guilabel> screen shows you how "
+"to make your system more secure."
+msgstr ""
+
+#: en_US/xml-tags.xml:700(command) en_US/xml-tags.xml:705(tertiary)
+#: en_US/xml-tags.xml:710(secondary)
+msgid "guibutton"
+msgstr ""
+
+#: en_US/xml-tags.xml:713(para)
+msgid ""
+"Use the <command><guibutton></command> and <command></guibutton>"
+"</command> tags to denote a button on a screen or menu. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:719(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Check the <guibutton>Activate on boot</guibutton> button \n"
+"to have the X Window System start automatically.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:729(para)
+msgid ""
+"Check the <guibutton>Activate on boot</guibutton> button to have the X "
+"Window System start automatically."
+msgstr ""
+
+#: en_US/xml-tags.xml:736(command) en_US/xml-tags.xml:741(tertiary)
+#: en_US/xml-tags.xml:746(secondary)
+msgid "guiicon"
+msgstr ""
+
+#: en_US/xml-tags.xml:749(para)
+msgid ""
+"The <command><guiicon></command> and <command></guiicon></"
+"command> tags are used to denote a panel or desktop icon. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:754(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Double-click the <guiicon>Start Here</guiicon> icon on the desktop.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:763(para)
+msgid "Double-click the <guiicon>Start Here</guiicon> icon on the desktop."
+msgstr ""
+
+#: en_US/xml-tags.xml:770(title)
+msgid "<command>guimenu</command> and <command>guimenuitem</command>"
+msgstr ""
+
+#: en_US/xml-tags.xml:776(tertiary) en_US/xml-tags.xml:781(secondary)
+msgid "guimenu"
+msgstr ""
+
+#: en_US/xml-tags.xml:787(tertiary) en_US/xml-tags.xml:792(secondary)
+msgid "guimenuitem"
+msgstr ""
+
+#: en_US/xml-tags.xml:795(para)
+msgid ""
+"To note a menu (like in the installation program or within the control "
+"panel), use the <command><guimenu></command> and <command></"
+"guimenu></command> tags."
+msgstr ""
+
+#: en_US/xml-tags.xml:801(para)
+msgid ""
+"To note submenu items, use the <command><guimenuitem></command> and "
+"<command></guimenuitem></command> tags. (Please note that there should "
+"not be any breaks between these commands, but for printing purposes breaks "
+"have been inserted). For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:808(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Select \n"
+"<guimenu>Main Menu</guimenu> =>\n"
+"\t <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> to start the \n"
+"<application>Emacs</application> text editor.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:820(para)
+msgid ""
+"From the control panel, click on <guimenu>Main Menu</guimenu> => "
+"<guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</"
+"guimenuitem> to start the <application>Emacs</application> text editor."
+msgstr ""
+
+#: en_US/xml-tags.xml:830(command) en_US/xml-tags.xml:834(secondary)
+msgid "keycap"
+msgstr ""
+
+#: en_US/xml-tags.xml:837(para)
+msgid ""
+"To denote a specific key, you will need to use the <command><keycap></"
+"command> and <command></keycap></command> tags. Brackets are "
+"automatically added around the keycap, so do not add them in your XML code. "
+"For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:844(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To make your selection, press the <keycap>Enter</keycap> key.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:853(para)
+msgid "To make your selection, press the <keycap>Enter</keycap> key."
+msgstr ""
+
+#: en_US/xml-tags.xml:858(command) en_US/xml-tags.xml:862(secondary)
+msgid "menuchoice"
+msgstr ""
+
+#: en_US/xml-tags.xml:865(para)
+msgid ""
+"Often using a mouse is tedious for common tasks. Therefore, programmers "
+"often build in keyboard-shortcuts to simplify their program. These should be "
+"described using the shortcut tag as a wrapper for the keyboard tags. The "
+"shortcut tag must be wrapped inside the menuchoice tag. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:874(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Go to the menu bar and choose: \n"
+" <menuchoice>\n"
+" <shortcut>\n"
+" <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>\n"
+" </shortcut>\n"
+" <guimenu><accel>F</accel>ile</guimenu>\n"
+" <guimenuitem><accel>S</accel>ave</guimenuitem>\n"
+" </menuchoice>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:891(para)
+msgid ""
+"Go to the menu bar and choose: <menuchoice><shortcut><keycombo><keycap>Ctrl</"
+"keycap><keycap>s</keycap></keycombo></shortcut><guimenu><accel>F</accel>ile</"
+"guimenu><guimenuitem><accel>S</accel>ave</guimenuitem></menuchoice>."
+msgstr ""
+
+#: en_US/xml-tags.xml:905(command) en_US/xml-tags.xml:909(secondary)
+msgid "keycombo"
+msgstr ""
+
+#: en_US/xml-tags.xml:912(para)
+msgid ""
+"To illustrate a key combination, you need to use the <command><"
+"keycombo></command> and <command></keycombo></command>, "
+"<command><keycap></command> and <command></keycap></command> "
+"tags. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:920(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To reboot your system, press <keycombo>\n"
+"<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>\n"
+"</keycombo>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:931(para)
+msgid ""
+"To reboot your system, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</"
+"keycap><keycap>Del</keycap></keycombo>."
+msgstr ""
+
+#: en_US/xml-tags.xml:942(title) en_US/style.xml:1377(term)
+msgid "Lists"
+msgstr ""
+
+#: en_US/xml-tags.xml:945(primary) en_US/xml-tags.xml:969(secondary)
+#: en_US/xml-tags.xml:974(primary) en_US/xml-tags.xml:1042(primary)
+#: en_US/xml-tags.xml:1048(secondary) en_US/xml-tags.xml:1130(secondary)
+#: en_US/xml-tags.xml:1135(primary) en_US/xml-tags.xml:1225(secondary)
+#: en_US/xml-tags.xml:1230(primary) en_US/xml-tags.xml:1408(secondary)
+#: en_US/xml-tags.xml:1413(primary)
+msgid "lists"
+msgstr ""
+
+#: en_US/xml-tags.xml:946(secondary)
+msgid "creating"
+msgstr ""
+
+#: en_US/xml-tags.xml:949(para)
+msgid ""
+"There are several types of lists you can create using XML. You can have a "
+"itemized (bulleted) list, a ordered (numbered) list, or a variable list "
+"(presents a term and then a separate paragraph)."
+msgstr ""
+
+#: en_US/xml-tags.xml:953(para)
+msgid ""
+"There is also a list format for tables and for for creating a list of "
+"glossary terms and their definitions."
+msgstr ""
+
+#: en_US/xml-tags.xml:956(para)
+msgid ""
+"The sections below will discuss the proper uses for the various list and how "
+"to create them."
+msgstr ""
+
+#: en_US/xml-tags.xml:978(para)
+msgid ""
+"An <command>ItemizedList</command> is best used to present information that "
+"is important for the reader to know, but that does not need to be in a "
+"specific order. It is shorter than a <command>VariableList</command> and "
+"presents the information in a very simple way."
+msgstr ""
+
+#: en_US/xml-tags.xml:984(para)
+msgid ""
+"To create an <command>ItemizedList</command> (otherwise known as bulleted "
+"list), use the following command sequence:"
+msgstr ""
+
+#: en_US/xml-tags.xml:988(para) en_US/xml-tags.xml:1063(para)
+#: en_US/xml-tags.xml:1147(para)
+msgid ""
+"Notice below that the text for the list item is directly surrounded by the "
+"<command>para</command> tags. If you do not do this, you will find extra "
+"whitespace in your lists where the text does not line up correctly. This is "
+"most noticeable when you have a series of list items that consist of "
+"multiple lines of text. This whitespace is not as noticeable in the HTML "
+"output as it is in the PDFs."
+msgstr ""
+
+#: en_US/xml-tags.xml:998(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<itemizedlist> \n"
+" <listitem>\n"
+" <para>Getting familiar with the installation program's user interface</para>\n"
+" </listitem>\n"
+"\n"
+" <listitem>\n"
+" <para>Starting the installation program</para> \n"
+" </listitem>\n"
+"\n"
+" <listitem>\n"
+" <para>Selecting an installation method</para>\n"
+" </listitem>\n"
+"</itemizedlist>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1015(para) en_US/xml-tags.xml:1094(para)
+#: en_US/xml-tags.xml:1181(para) en_US/xml-tags.xml:1319(para)
+#: en_US/xml-tags.xml:1453(para) en_US/xml-tags.xml:1909(para)
+#: en_US/xml-tags.xml:1958(para)
+msgid "The output looks like:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1019(para)
+msgid "Getting familiar with the installation program's user interface"
+msgstr ""
+
+#: en_US/xml-tags.xml:1023(para)
+msgid "Starting the installation program"
+msgstr ""
+
+#: en_US/xml-tags.xml:1027(para)
+msgid "Selecting an installation method"
+msgstr ""
+
+#: en_US/xml-tags.xml:1034(command)
+msgid "OrderedList"
+msgstr ""
+
+#: en_US/xml-tags.xml:1052(para)
+msgid ""
+"An <command>orderedlist</command> is best used to present information that "
+"is important for the reader to know in a specific order. "
+"<command>orderedlist</command>s are a good way to convey step-by-step "
+"senarios to the audience you are writing for."
+msgstr ""
+
+#: en_US/xml-tags.xml:1057(para)
+msgid ""
+"To create an <command>orderedlist</command> (numbered list), use the "
+"following XML code sequence:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1073(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<orderedlist>\n"
+" <listitem>\n"
+" <para>Online &mdash; http://www.redhat.com/support/errata; supplies errata\n"
+" you can read online, and you can download diskette images\n"
+" easily.</para>\n"
+" </listitem>\n"
+"\t \n"
+" <listitem>\n"
+" <para>Email &mdash; By sending an empty mail message to errata@@redhat.com, \n"
+" you will receive an email containing a text listing of the \n"
+" complete errata of the installation program and related software \n"
+" (if errata exist at that time). Also included are URLs to each \n"
+" updated package and diskette image in the errata. Using these \n"
+" URLs, you can download any necessary diskette images. Please \n"
+" note: use binary mode when transferring a diskette image.</para> \n"
+" </listitem>\n"
+"</orderedlist>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1098(para)
+msgid ""
+"Online — http://www.redhat.com/support/errata; supplies errata you can "
+"read online, and you can download diskette images easily."
+msgstr ""
+
+#: en_US/xml-tags.xml:1105(para)
+msgid ""
+"Email — By sending an empty mail message to errata@@redhat.com, you "
+"will receive an email containing a text listing of the complete errata of "
+"the installation program and related software (if errata exist at that "
+"time). Also included are URLs to each updated package and diskette image in "
+"the errata. Using these URLs, you can download any necessary diskette "
+"images. Please note: use binary mode when transferring a diskette image."
+msgstr ""
+
+#: en_US/xml-tags.xml:1121(command)
+msgid "Variablelist"
+msgstr ""
+
+#: en_US/xml-tags.xml:1139(para)
+msgid ""
+"A <command>variablelist</command> best represents a list of terms and "
+"definitions or descriptions for those terms."
+msgstr ""
+
+#: en_US/xml-tags.xml:1142(para)
+msgid ""
+"To create a <command>variablelist</command>, use the following command "
+"sequence:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1157(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<variablelist>\n"
+" <varlistentry> \n"
+" <term> New Multi-CD Install </term>\n"
+" <listitem> \n"
+" <para>As the installation program continues to grow, Red Hat has developed \n"
+" an installation program capable of installing from \n"
+" multiple CD-ROMs.</para>\n"
+" </listitem>\n"
+" </varlistentry>\n"
+"\n"
+" <varlistentry>\n"
+" <term>XFree 4.0 </term>\n"
+" <listitem>\n"
+" <para>Configuration of your X Window System during the installation has \n"
+" never been more thorough. From choosing your monitor and its correct \n"
+" settings, to video card probing, to testing your desired X setup, \n"
+" Xconfigurator will help you set everything just right.</para>\n"
+" </listitem>\n"
+" </varlistentry>\n"
+"</variablelist>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1185(term)
+msgid "New Multi-CD Install"
+msgstr ""
+
+#: en_US/xml-tags.xml:1185(para)
+msgid ""
+"As the installation program continues to grow, Red Hat has developed an "
+"installation program capable of installing from multiple CD-ROMs."
+msgstr ""
+
+#: en_US/xml-tags.xml:1193(term)
+msgid "XFree 4.0"
+msgstr ""
+
+#: en_US/xml-tags.xml:1195(para)
+msgid ""
+"Configuration of your X Window System during the installation has never been "
+"more thorough. From choosing your monitor and its correct settings, to video "
+"card probing, to testing your desired X setup, Xconfigurator will help you "
+"set everything just right."
+msgstr ""
+
+#: en_US/xml-tags.xml:1205(title) en_US/writing-guidelines.xml:434(title)
+msgid "Warning"
+msgstr "Aviso"
+
+#: en_US/xml-tags.xml:1206(para)
+msgid ""
+"Do <emphasis>not</emphasis> specify the <computeroutput>frame</"
+"computeroutput> attribute to the table. Doing so breaks PDF production."
+msgstr ""
+
+#: en_US/xml-tags.xml:1216(title)
+msgid "Creating a List Within a Table Using <command>Simplelist</command>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1220(command) en_US/xml-tags.xml:1226(tertiary)
+#: en_US/xml-tags.xml:1231(command) en_US/xml-tags.xml:1237(command)
+msgid "simplelist"
+msgstr ""
+
+#: en_US/xml-tags.xml:1235(primary)
+msgid "tables"
+msgstr ""
+
+#: en_US/xml-tags.xml:1236(secondary)
+msgid "creating a list within a table"
+msgstr ""
+
+#: en_US/xml-tags.xml:1240(para)
+msgid ""
+"A <command>simplelist</command> is an unadorned list of items. "
+"<command>simplelist</command>s can be inline or arranged in columns."
+msgstr ""
+
+#: en_US/xml-tags.xml:1244(para)
+msgid ""
+"We use <command>simplelist</command> to add separate paragraphs of text "
+"within a table element. A regular list, such as <command>itemizedlist</"
+"command>, cannot be embedded within a table."
+msgstr ""
+
+#: en_US/xml-tags.xml:1248(para)
+msgid "The XML commands for a table look like:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1251(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"\t <table id=\"tb-hwinfo-hostbus\">\n"
+"\t <title>Host Bus Adapter Features and Configuration Requirements</title>\n"
+"\t \n"
+"\t <tgroup cols=\"3\">\n"
+"\t <colspec colnum=\"1\" colname=\"HostBus\" colwidth=\"33\"/>\n"
+"\t <colspec colnum=\"2\" colname=\"Features\" colwidth=\"34\"/>\n"
+"\t <colspec colnum=\"3\" colname=\"Single\" colwidth=\"33\"/>\n"
+"\t \n"
+"\t <thead>\n"
+"\t\t<row>\n"
+"\t\t <entry>Host Bus Adapter</entry>\n"
+"\t\t <entry>Features</entry>\n"
+"\t\t <entry>Single-Initiator Configuration</entry>\n"
+"\t\t</row>\n"
+"\t </thead>\n"
+"\t \n"
+"\t <tbody>\n"
+"\t\t\n"
+"\t\t<row>\n"
+"\t\t <entry>Adaptec 2940U2W</entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Ultra2, wide, LVD.</member>\n"
+"\t\t <member>HD68 external connector.</member>\n"
+"\t\t <member>One channel, with two bus segments.</member>\n"
+"\t\t <member>Set the onboard termination by using the BIOS\n"
+"\t\t\tutility.</member>\n"
+"\t\t <member>Onboard termination is disabled when the power is\n"
+"\t\t\toff.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist>\n"
+"\t\t <member>Set the onboard termination to automatic (the\n"
+"\t\t\tdefault).</member>\n"
+"\t\t <member>Use the internal SCSI connector for private\n"
+"\t\t\t(non-cluster) storage.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t</row>\n"
+"\t\t\n"
+"\t\t<row>\n"
+"\t\t <entry>Qlogic QLA1080</entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Ultra2, wide, LVD</member>\n"
+"\t\t <member>VHDCI external connector</member>\n"
+"\t\t <member>One channel</member>\n"
+"\t\t <member>Set the onboard termination by using the BIOS\n"
+"\t\t\tutility.</member>\n"
+"\t\t <member>Onboard termination is disabled when the power is off,\n"
+"\t\t\tunless jumpers are used to enforce termination.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t \n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Set the onboard termination to\n"
+"\t\t\tautomatic (the default).</member>\n"
+"\t\t <member>Use the internal SCSI connector for private\n"
+"\t\t\t(non-cluster) storage.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t</row>\n"
+"\t\t\n"
+"\t </tbody>\n"
+"\t </tgroup>\n"
+"\t </table>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1322(title)
+msgid "Host Bus Adapter Features and Configuration Requirements"
+msgstr ""
+
+#: en_US/xml-tags.xml:1331(entry)
+msgid "Host Bus Adapter"
+msgstr ""
+
+#: en_US/xml-tags.xml:1332(entry) en_US/xml-tags.xml:2144(entry)
+msgid "Features"
+msgstr ""
+
+#: en_US/xml-tags.xml:1333(entry)
+msgid "Single-Initiator Configuration"
+msgstr ""
+
+#: en_US/xml-tags.xml:1340(entry)
+msgid "Adaptec 2940U2W"
+msgstr ""
+
+#: en_US/xml-tags.xml:1343(member)
+msgid "Ultra2, wide, LVD."
+msgstr ""
+
+#: en_US/xml-tags.xml:1344(member)
+msgid "HD68 external connector."
+msgstr ""
+
+#: en_US/xml-tags.xml:1345(member)
+msgid "One channel, with two bus segments."
+msgstr ""
+
+#: en_US/xml-tags.xml:1346(member) en_US/xml-tags.xml:1367(member)
+msgid "Set the onboard termination by using the BIOS utility."
+msgstr ""
+
+#: en_US/xml-tags.xml:1348(member)
+msgid "Onboard termination is disabled when the power is off."
+msgstr ""
+
+#: en_US/xml-tags.xml:1353(member) en_US/xml-tags.xml:1375(member)
+msgid "Set the onboard termination to automatic (the default)."
+msgstr ""
+
+#: en_US/xml-tags.xml:1355(member) en_US/xml-tags.xml:1377(member)
+msgid "Use the internal SCSI connector for private (non-cluster) storage."
+msgstr ""
+
+#: en_US/xml-tags.xml:1361(entry)
+msgid "Qlogic QLA1080"
+msgstr ""
+
+#: en_US/xml-tags.xml:1364(member)
+msgid "Ultra2, wide, LVD"
+msgstr ""
+
+#: en_US/xml-tags.xml:1365(member)
+msgid "VHDCI external connector"
+msgstr ""
+
+#: en_US/xml-tags.xml:1366(member)
+msgid "One channel"
+msgstr ""
+
+#: en_US/xml-tags.xml:1369(member)
+msgid ""
+"Onboard termination is disabled when the power is off, unless jumpers are "
+"used to enforce termination."
+msgstr ""
+
+#: en_US/xml-tags.xml:1388(para)
+msgid ""
+"Notice how the <command>SimpleList</command> tags are used. The <"
+"entry> and <simplelist> tags must be aligned beside one another, "
+"otherwise you will receive a parsing error."
+msgstr ""
+
+#: en_US/xml-tags.xml:1393(para)
+msgid ""
+"For each paragraph or list item to be added within a <command>SimpleList</"
+"command>, the <member> tag set must be added around that particular "
+"text item."
+msgstr ""
+
+#: en_US/xml-tags.xml:1399(command) en_US/xml-tags.xml:1403(command)
+#: en_US/xml-tags.xml:1409(tertiary) en_US/xml-tags.xml:1414(command)
+msgid "glosslist"
+msgstr ""
+
+#: en_US/xml-tags.xml:1417(para)
+msgid ""
+"Use the <command>glosslist</command> command set to create a list of "
+"glossary terms and their definitions."
+msgstr ""
+
+#: en_US/xml-tags.xml:1421(para)
+msgid "In XML, an example looks like the following:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1424(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"\t <glosslist>\n"
+"\t <glossentry>\n"
+"\t <glossterm>applet</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>A small application, usually a utility or other\n"
+"\t simple program.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\n"
+"\t <glossentry>\n"
+"\t <glossterm>architecture</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>The design for organization and integration of \n"
+" components within a computer or computer system.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\n"
+"\t <glossentry>\n"
+"\t <glossterm>archive</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>To transfer files into storage for the purpose of \n"
+"\t saving space and/or organization.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\t </glosslist>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1459(glossterm)
+msgid "applet"
+msgstr ""
+
+#: en_US/xml-tags.xml:1461(para)
+msgid "A small application, usually a utility or other simple program."
+msgstr ""
+
+#: en_US/xml-tags.xml:1466(glossterm)
+msgid "architecture"
+msgstr ""
+
+#: en_US/xml-tags.xml:1468(para)
+msgid ""
+"The design for organization and integration of components within a computer "
+"or computer system."
+msgstr ""
+
+#: en_US/xml-tags.xml:1474(glossterm)
+msgid "archive"
+msgstr ""
+
+#: en_US/xml-tags.xml:1476(para)
+msgid ""
+"To transfer files into storage for the purpose of saving space and/or "
+"organization."
+msgstr ""
+
+#: en_US/xml-tags.xml:1487(command) en_US/xml-tags.xml:1491(secondary)
+msgid "option"
+msgstr ""
+
+#: en_US/xml-tags.xml:1494(para)
+msgid ""
+"If you have a command that offers an option or a flag, use the <command><"
+"option></command> and <command></option></command> tags."
+msgstr ""
+
+#: en_US/xml-tags.xml:1501(para)
+msgid ""
+"The <option> tag set is only meant to be used for command line "
+"options, not options in configuration files."
+msgstr ""
+
+#: en_US/xml-tags.xml:1505(para)
+msgid "In XML, specifying an option would look like the following:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1509(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"For example, with the command <command>ls</command> you can \n"
+"specify an option such as <option>-la</option>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1519(para)
+msgid ""
+"For example, with the command <command>ls</command> you can specify an "
+"option such as <option>-la</option>."
+msgstr ""
+
+#: en_US/xml-tags.xml:1525(title)
+msgid "Index Entries"
+msgstr ""
+
+#: en_US/xml-tags.xml:1528(primary) en_US/xml-tags.xml:1534(secondary)
+#: en_US/xml-tags.xml:1563(primary) en_US/xml-tags.xml:1595(primary)
+msgid "indexing"
+msgstr ""
+
+#: en_US/xml-tags.xml:1537(para)
+msgid ""
+"The following command sequence shows you the code inserted into the body of "
+"the text to add an index entry to your document:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1542(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<indexterm> <-- indicates a term to be placed in the index\n"
+"<primary>foo</primary> <-- indicates that \"foo\" is the first term\n"
+"<secondary>bar</secondary> <-- \"bar\" will be listed under \"foo\" \n"
+"</indexterm> <-- closes this index entry\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1551(primary)
+msgid "foo"
+msgstr ""
+
+#: en_US/xml-tags.xml:1552(secondary)
+msgid "bar"
+msgstr ""
+
+#: en_US/xml-tags.xml:1556(para)
+msgid ""
+"The <command><seealso></command> tag allows you to reference another "
+"index entry or refer to another manual. Make sure the <command><"
+"seealso></command> reference you are pointing to has its own entry. For "
+"example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1564(secondary)
+msgid "seealso tag"
+msgstr ""
+
+#: en_US/xml-tags.xml:1568(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<indexterm> \n"
+"<primary>SWAK</primary> \n"
+"<seealso>salutations</seealso>\n"
+"</indexterm>\n"
+"\n"
+"\n"
+"<indexterm> \n"
+"<primary>salutations</primary> \n"
+"</indexterm>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1582(primary)
+msgid "SWAK"
+msgstr ""
+
+#: en_US/xml-tags.xml:1583(seealso) en_US/xml-tags.xml:1587(primary)
+msgid "Salutations"
+msgstr ""
+
+#: en_US/xml-tags.xml:1590(para)
+msgid ""
+"The <command><see></command> tag allows you to reference to another "
+"index entry entirely. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1596(secondary)
+msgid "see tag"
+msgstr ""
+
+#: en_US/xml-tags.xml:1601(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<indexterm> \n"
+"<primary>Guinness</primary> \n"
+"<see>beer</see> <-- beer will be listed under \n"
+"the Guinness entry, but you must make sure beer also has its \n"
+"own entry to refer to.\n"
+"</indexterm>\n"
+"\n"
+"<indexterm>\n"
+"<primary>beer</primary>\n"
+"</indexterm>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1616(primary)
+msgid "Guinness"
+msgstr ""
+
+#: en_US/xml-tags.xml:1617(see) en_US/xml-tags.xml:1621(primary)
+msgid "Beer"
+msgstr ""
+
+#: en_US/xml-tags.xml:1624(para)
+msgid ""
+"To view the HTML output of the index entries shown here, refer to the "
+"<filename>generated-index.html</filename> file at the end of this document."
+msgstr ""
+
+#: en_US/xml-tags.xml:1628(para)
+msgid ""
+"How does the index get generated? If indexterms exist in the document and "
+"the beginning and ending index tags exist before the end tag for the book or "
+"article, an index is created because of the <command>generate.index</"
+"command> stylesheet parameter, which is set to true by default."
+msgstr ""
+
+#: en_US/xml-tags.xml:1638(command) en_US/xml-tags.xml:1643(secondary)
+msgid "para"
+msgstr "para"
+
+#: en_US/xml-tags.xml:1646(para)
+msgid ""
+"For any paragraph, the <command><para></command> and <command></"
+"para></command> tags must open and close that particular paragraph."
+msgstr ""
+
+#: en_US/xml-tags.xml:1651(para)
+msgid ""
+"Do not use para tags around anything other than a simple paragraph. Doing so "
+"will create additional white space within the text itself."
+msgstr ""
+
+#: en_US/xml-tags.xml:1655(para)
+msgid ""
+"Do not use <command><para></command> tags around the following (or, to "
+"put this another way, do not embed the following within <command><para>"
+"</command> tags):"
+msgstr ""
+
+#: en_US/xml-tags.xml:1661(command) en_US/xml-tags.xml:1896(command)
+#: en_US/xml-tags.xml:1904(command) en_US/xml-tags.xml:1953(command)
+msgid "<screen>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1664(command)
+msgid "<itemizedlist>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1667(command)
+msgid "<orderedlist>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1670(command)
+msgid "<variablelist>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1673(command)
+msgid "<table>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1680(command) en_US/xml-tags.xml:1689(secondary)
+#: en_US/writing-guidelines.xml:119(sgmltag)
+msgid "part"
+msgstr ""
+
+#: en_US/xml-tags.xml:1683(primary)
+msgid "parts"
+msgstr ""
+
+#: en_US/xml-tags.xml:1692(para)
+msgid ""
+"In the parent file, you can separate the chapters into parts to divide them "
+"into logical groups. For example, in the parent file, the <command>part</"
+"command> tags surround the chapter entities:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1698(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<part id=\"pt-foo\">\n"
+" <partintro>\n"
+" <para>Some text for the part intro</para>\n"
+" &CHAPTER; \n"
+"\n"
+" &ANOTHER-CHAPTER;\n"
+"</part>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1709(para)
+msgid ""
+"If you create a part, include a part introduction describing the contents of "
+"the part. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1715(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+" <part id=\"pt-setup\">\n"
+" <title>Getting Setup</title>\n"
+" <partintro>\n"
+" <para>This section contains information you will need when you first join\n"
+"\tthe Docs group. You might need to refer to this part again for\n"
+"\tinformation such as installing &FC;.</para>\n"
+" </partintro>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1726(para)
+msgid ""
+"In the HTML output, a separate HTML page is generated with the part number, "
+"title, introduction, and TOC. In the PDF output, the same information about "
+"the part is on a separate page."
+msgstr ""
+
+#: en_US/xml-tags.xml:1735(command) en_US/xml-tags.xml:1739(secondary)
+msgid "prompt"
+msgstr ""
+
+#: en_US/xml-tags.xml:1742(para)
+msgid ""
+"To show a prompt, such as a root or DOS prompt, use the <command><"
+"prompt></command> and <command></prompt></command> commands. For "
+"example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1748(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"At the <prompt>LILO:</prompt> boot prompt, type linux to \n"
+"boot into your Linux partition.\n"
+"\n"
+"At the <prompt>C:\\></prompt> prompt, type ....\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1760(para)
+msgid ""
+"At the <prompt>LILO:</prompt> boot prompt, type linux to boot into your "
+"Linux partition."
+msgstr ""
+
+#: en_US/xml-tags.xml:1764(para)
+msgid "At the <prompt>C:\\></prompt> prompt, type ...."
+msgstr ""
+
+#: en_US/xml-tags.xml:1770(para)
+msgid ""
+"When showing example computer output (usually in <command>screen</command> "
+"tags), do not include the prompt or command (unless the command or prompt is "
+"the actually computer output you want to show)."
+msgstr ""
+
+#: en_US/xml-tags.xml:1779(command) en_US/xml-tags.xml:1783(secondary)
+msgid "replaceable"
+msgstr ""
+
+#: en_US/xml-tags.xml:1786(para)
+msgid ""
+"To create replaceable text, use the tags <command><replaceable></"
+"command> and <command></replaceable></command> around the text you "
+"want to use as a variable."
+msgstr ""
+
+#: en_US/xml-tags.xml:1792(para)
+msgid ""
+"This example demonstrates how to use the <command>replaceable</command> tags "
+"when referencing the name of an RPM file:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1796(screen)
+#, no-wrap
+msgid ""
+"\n"
+"foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1805(replaceable)
+msgid "version-number"
+msgstr ""
+
+#: en_US/xml-tags.xml:1805(replaceable)
+msgid "arch"
+msgstr "arquitectura"
+
+#: en_US/xml-tags.xml:1804(screen)
+#, no-wrap
+msgid ""
+"\n"
+"foo-<placeholder-1/>.<placeholder-2/>.rpm\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1816(para)
+msgid ""
+"The <command><screen></command> command is used to format text within "
+"a document and is great for adding emphasis to show examples of code, "
+"computer output, and more. In HTML with the Fedora CSS file, this appears in "
+"box with a grey background. To use this command you only need the opening "
+"<command><screen></command> and closing <command></screen></"
+"command> tags around the text you are emphasizing."
+msgstr ""
+
+#: en_US/xml-tags.xml:1828(para)
+msgid ""
+"When using the <command><screen></command> tag, set everything within "
+"that screen to flush left. The contents of the <sgmltag class=\"starttag"
+"\">screen</sgmltag> element are rendered exactly as is, including any "
+"indentation. Using flush left prevents extra blank space in front of the "
+"text inside the gray background when the content is converted to HTML."
+msgstr ""
+
+#: en_US/xml-tags.xml:1838(para)
+msgid ""
+"The <command><screen></command> tag set may contain other inline tags, "
+"such as <command><computeroutput></command>, <command><userinput>"
+"</command>, or <command><replaceable></command>. Additional inline "
+"tags are not required by definition. The <command><screen></command> "
+"tags by themselves may provide sufficient context, especially for simple "
+"examples or file listings. Consider the context of the example, and use "
+"inline tags if they are helpful to the reader."
+msgstr ""
+
+#: en_US/xml-tags.xml:1849(para)
+msgid ""
+"If you use inline tags, remember that line breaks inside <command><"
+"screen></command> tags create line breaks in any rendered output. Place "
+"any inline tags <emphasis>on the same line</emphasis> as their content. Do "
+"not overuse tagging within a <command><screen></command> tag set."
+msgstr ""
+
+#: en_US/xml-tags.xml:1857(para)
+msgid "An example of <command><screen></command> is the following:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1862(computeroutput)
+#, no-wrap
+msgid ""
+"<screen>\n"
+"This is an example of a screen. You do not need &lt;para&gt; tags\n"
+"within this command.\n"
+"</screen>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1872(screen)
+#, no-wrap
+msgid ""
+"\n"
+"This is an example of a screen. You do not need <para> tags\n"
+"within this command.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1878(title)
+msgid "Using Inline Tags with <command>screen</command>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1879(para)
+msgid ""
+"If you choose to use inline tags inside a <command><screen></command> "
+"section, follow these guidelines for consistency. If the content in the "
+"screen is a listing of a configuration file or the output of a program, use "
+"the <command><computeroutput></command> tag set around the entire "
+"output. If the user should type the example on the command line or in a "
+"configuration file, use the <command><userinput></command> tag set. "
+"Separate input and output with a short sentence of narrative, as below:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1892(command) en_US/xml-tags.xml:1900(command)
+#: en_US/xml-tags.xml:1949(command)
+msgid "<para>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1894(command) en_US/xml-tags.xml:1902(command)
+#: en_US/xml-tags.xml:1951(command)
+msgid "</para>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1897(command) en_US/xml-tags.xml:1954(command)
+msgid "<userinput>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1897(command) en_US/xml-tags.xml:1954(command)
+msgid "</userinput>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1898(command) en_US/xml-tags.xml:1906(command)
+#: en_US/xml-tags.xml:1955(command)
+msgid "</screen>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1905(command)
+msgid "<computeroutput>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1905(command)
+msgid "</computeroutput>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1891(screen)
+#, no-wrap
+msgid ""
+"\n"
+"\t<placeholder-1/>\n"
+"\t Type the following command:\n"
+"\t<placeholder-2/>\n"
+"\n"
+"<placeholder-3/>\n"
+"<placeholder-4/>command -sw file1<placeholder-5/>\n"
+"<placeholder-6/>\n"
+"\n"
+"\t<placeholder-7/>\n"
+"\t You should see the following output:\n"
+"\t<placeholder-8/>\n"
+"\n"
+"<placeholder-9/>\n"
+"<placeholder-10/>Completed, time = 0.12 sec<placeholder-11/>\n"
+"<placeholder-12/>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1913(para)
+msgid "Type the following command:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1918(userinput)
+#, no-wrap
+msgid "command -sw file1"
+msgstr ""
+
+#: en_US/xml-tags.xml:1921(para)
+msgid "You should see the following output:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1926(computeroutput)
+#, no-wrap
+msgid "Completed, time = 0.12 sec"
+msgstr ""
+
+#: en_US/xml-tags.xml:1931(para)
+msgid ""
+"When showing a command or series of commands inside <command>screen</"
+"command> tags, do not show the prompt."
+msgstr ""
+
+#: en_US/xml-tags.xml:1937(para)
+msgid ""
+"If the <command><screen></command> shows the reader how to change only "
+"<emphasis>part</emphasis> of a line, mark the change with an inline "
+"<command><userinput></command> tag set. You may use the <command><"
+"userinput></command> tag set inside a larger area that is already marked "
+"inline with <command><computeroutput></command>. Do not include any "
+"extra lines of context in this case, unless excluding them would confuse the "
+"reader. The following example illustrates these guidelines:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1950(command)
+msgid "<filename>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1950(command)
+msgid "</filename>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1948(screen)
+#, no-wrap
+msgid ""
+"\n"
+"\t<placeholder-1/>\n"
+"\t Edit the <placeholder-2/>/etc/sysconfig/init<placeholder-3/> file as follows:\n"
+"\t<placeholder-4/>\n"
+"\n"
+"<placeholder-5/>\n"
+"GRAPHICAL=<placeholder-6/>yes<placeholder-7/> \n"
+"<placeholder-8/>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1962(para)
+msgid "Edit the <filename>/etc/sysconfig/init</filename> file as follows:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1967(userinput) en_US/xml-tags.xml:2153(entry)
+#: en_US/xml-tags.xml:2154(entry) en_US/xml-tags.xml:2158(entry)
+#: en_US/xml-tags.xml:2159(entry) en_US/xml-tags.xml:2163(entry)
+#: en_US/xml-tags.xml:2164(entry)
+#, no-wrap
+msgid "yes"
+msgstr ""
+
+#: en_US/xml-tags.xml:1966(screen)
+#, no-wrap
+msgid ""
+"\n"
+"GRAPHICAL=<placeholder-1/>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1970(para)
+msgid ""
+"For an explanation of how to use the <command>replaceable</command> tags "
+"within a set of <command>screen</command> tags, refer to <xref linkend=\"sn-"
+"xml-tags-replaceable\"/>."
+msgstr ""
+
+#: en_US/xml-tags.xml:1980(title)
+msgid "Sections"
+msgstr ""
+
+#: en_US/xml-tags.xml:1984(secondary) en_US/xml-tags.xml:1988(primary)
+msgid "sections"
+msgstr ""
+
+#: en_US/xml-tags.xml:1991(para)
+msgid ""
+"Within an article (or chapter if it is a DocBook XML book like the "
+"<citetitle>Installation Guide</citetitle>), you can have sections and "
+"subsections. <command><section></command> is always the highest "
+"section and you cannot have two sections of the same level within one "
+"another (a section 2 can be created within a section 1, but section 1 has to "
+"be closed before another section 1 can be created). The general layout "
+"follows:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2000(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<section id=\"sn-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"\n"
+"\n"
+" <section id=\"sn-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"\n"
+" <sect3 id=\"s3-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"\n"
+" </sect3>\n"
+"\n"
+" </section>\n"
+"\n"
+"</section>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2028(para)
+msgid ""
+"If you only need one level of sections in a DocBook article, you can use the "
+"<command>section</command> tag. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2034(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<section id=\"sn-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"</section>\n"
+"<section id=\"sn-anothername\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" More body text goes here.\n"
+" </para>\n"
+"</section>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2059(para)
+msgid "The following is an example of creating a table."
+msgstr ""
+
+#: en_US/xml-tags.xml:2066(command)
+msgid "\"tb-mockup-before-begin.\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2065(emphasis)
+msgid ""
+"This tells XML that you will be creating a table and the ID name is "
+"<placeholder-1/>"
+msgstr ""
+
+#: en_US/xml-tags.xml:2071(emphasis)
+msgid "This tells XML that you are creating a table with three columns."
+msgstr ""
+
+#: en_US/xml-tags.xml:2075(command)
+msgid "colspec"
+msgstr ""
+
+#: en_US/xml-tags.xml:2075(emphasis)
+msgid "<placeholder-1/> says that you are giving information about the column to XML"
+msgstr ""
+
+#: en_US/xml-tags.xml:2076(command)
+msgid "colnum=\"1\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2076(emphasis)
+msgid ""
+"<placeholder-1/> says that you are giving specifications for the first "
+"column."
+msgstr ""
+
+#: en_US/xml-tags.xml:2079(command)
+msgid "colname=\"Features\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2079(emphasis)
+msgid "<placeholder-1/> says that the title for this column will be \"Features.\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2082(command)
+msgid "colwidth=\"3\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2082(emphasis)
+msgid ""
+"<placeholder-1/> specifies the width of the column. This can be more tricky: "
+"such as two columns with widths of 1 and 2,the 1 is one-half the width of "
+"the 2, in respect to the page size. But, what if you need the 1 to be a "
+"little more than half of the 2, using a larger number ratio, such as 10 to "
+"20 would accomplish this. You could then change the 10 to an 11 or a 12 to "
+"make it a little more than half of the second column of 20. In no value is "
+"given, a value of 1 is assumed."
+msgstr ""
+
+#: en_US/xml-tags.xml:2096(emphasis)
+msgid "Contains one or more table row elements."
+msgstr ""
+
+#: en_US/xml-tags.xml:2099(emphasis)
+msgid "Contains one or more table cell (entry) elements."
+msgstr ""
+
+#: en_US/xml-tags.xml:2102(emphasis)
+msgid ""
+"Table cell element, one of several in a row element, defining columns within "
+"the row."
+msgstr ""
+
+#: en_US/xml-tags.xml:2111(emphasis)
+msgid "Contains one or more row elements, for the main text of the table."
+msgstr ""
+
+#: en_US/xml-tags.xml:2063(screen)
+#, no-wrap
+msgid ""
+"\n"
+"<table id=\"tb-mockup-before-begin\">\n"
+" <placeholder-1/>\n"
+"\n"
+"<title>Available Features of GNOME and KDE</title>\n"
+"\n"
+"<tgroup cols=\"3\">\n"
+" <placeholder-2/>\n"
+"\n"
+"<colspec colnum=\"1\" colname=\"Features\" colwidth=\"3\"/>\n"
+" <placeholder-3/> <placeholder-4/>\n"
+" \n"
+" <placeholder-5/>\n"
+" \n"
+" <placeholder-6/>\n"
+"\n"
+"<colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/>\n"
+"<colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/>\n"
+"\n"
+"<thead>\n"
+" <placeholder-7/>\n"
+"\n"
+"<row> \n"
+" <placeholder-8/>\n"
+"\n"
+"<entry>Features</entry>\n"
+" <placeholder-9/>\n"
+"\n"
+"<entry>GNOME</entry> \n"
+"<entry>KDE</entry>\n"
+"</row> \n"
+"</thead> \n"
+"\n"
+"<tbody> \n"
+" <placeholder-10/>\n"
+"\n"
+"<row> \n"
+"<entry>highly configurable</entry> \n"
+"<entry>yes</entry> \n"
+"<entry>yes</entry> \n"
+"</row> \n"
+"<row> \n"
+"<entry>multiple window managers </entry>\n"
+"<entry>yes</entry> \n"
+"<entry>yes</entry> \n"
+"</row> \n"
+"<row> \n"
+"<entry>Internet applications</entry> \n"
+"<entry>yes </entry> \n"
+"<entry>yes </entry> \n"
+"</row> \n"
+"</tbody> \n"
+"</tgroup> \n"
+"</table> \n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2135(title)
+msgid "Available Features of GNOME and KDE"
+msgstr ""
+
+#: en_US/xml-tags.xml:2145(entry)
+msgid "GNOME"
+msgstr "GNOME"
+
+#: en_US/xml-tags.xml:2146(entry)
+msgid "KDE"
+msgstr "KDE"
+
+#: en_US/xml-tags.xml:2152(entry)
+msgid "highly configurable"
+msgstr ""
+
+#: en_US/xml-tags.xml:2157(entry)
+msgid "multiple window managers"
+msgstr ""
+
+#: en_US/xml-tags.xml:2162(entry)
+msgid "Internet applications"
+msgstr ""
+
+#: en_US/xml-tags.xml:2171(title)
+msgid "Creating a List Within a Table"
+msgstr ""
+
+#: en_US/xml-tags.xml:2176(tertiary)
+msgid "list within a table"
+msgstr ""
+
+#: en_US/xml-tags.xml:2180(para)
+msgid ""
+"Creating a list within a table can be a difficult task. It requires strict "
+"formatting and a set of commands that are not available for command "
+"completion in <application>Emacs</application>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2185(para)
+msgid ""
+"The tags you will need to use are <command><simplelist></command> and "
+"<command><member></command>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2189(para)
+msgid ""
+"The following example will show you the proper formatting for creating a "
+"list within a table."
+msgstr ""
+
+#: en_US/xml-tags.xml:2194(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<table id=\"tb-hardware-powerswitch\">\n"
+" <title>Power Switch Hardware Table</title>\n"
+" <tgroup cols=\"4\">\n"
+" <colspec colnum=\"1\" colname=\"Hardware\" colwidth=\"2\"/>\n"
+" <colspec colnum=\"2\" colname=\"Quantity\" colwidth=\"2\"/>\n"
+" <colspec colnum=\"3\" colname=\"Description\" colwidth=\"6\"/> \n"
+" <colspec colnum=\"4\" colname=\"Required\" colwidth=\"2\"/>\n"
+"\n"
+" <thead>\n"
+"\t <row>\n"
+" <entry>Hardware</entry>\n"
+"\t <entry>Quantity</entry>\n"
+" <entry>Description</entry>\n"
+"\t <entry>Required</entry>\n"
+"\t </row>\n"
+" </thead>\n"
+"\t \n"
+" <tbody>\n"
+"\t \n"
+"\t<row>\n"
+" <entry>Serial power switches</entry>\n"
+"\n"
+"\t <entry>Two</entry>\n"
+"\n"
+"\t <entry><simplelist> <member>Power switches enable each cluster system\n"
+"\t to power-cycle the other cluster system. Note that clusters are\n"
+"\t configured with either serial or network attached power switches and\n"
+"\t not both.</member>\n"
+"\t\t \n"
+" <member>The following serial attached power switch has been\n"
+"\t fully tested:</member>\n"
+"\n"
+" <member>RPS-10 (model M/HD in the US, and model M/EC in\n"
+"\t Europe) </member>\n"
+"\n"
+" <member>Latent support is provided for the following serial\n"
+"\t attached power switch. This switch has not yet been fully\n"
+" tested:</member>\n"
+"\t\t \n"
+"\t <member>APC Serial On/Off Switch (partAP9211), <ulink\n"
+" url=\"http://www.apc.com/\">http://www.apc.com/</ulink></member>\n"
+" </simplelist></entry>\n"
+"\n"
+" <entry>Strongly recommended for data integrity under all failure\n"
+"\t conditions</entry>\n"
+"\n"
+"\t </row>\n"
+" </tbody>\n"
+" </tgroup>\n"
+"</table>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2248(para)
+msgid ""
+"Notice how the <command><simplelist></command> tag must be beside the "
+"<command><entry></command> tag? If you do not format this properly, it "
+"will not parse cleanly."
+msgstr ""
+
+#: en_US/xml-tags.xml:2252(para)
+msgid "The above example will look like the following:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2255(title)
+msgid "Power Switch Hardware Table"
+msgstr ""
+
+#: en_US/xml-tags.xml:2264(entry)
+msgid "Hardware"
+msgstr "'Hardware'"
+
+#: en_US/xml-tags.xml:2265(entry)
+msgid "Quantity"
+msgstr ""
+
+#: en_US/xml-tags.xml:2266(entry) en_US/emacs.xml:415(segtitle)
+msgid "Description"
+msgstr "Descrição"
+
+#: en_US/xml-tags.xml:2267(entry)
+msgid "Required"
+msgstr ""
+
+#: en_US/xml-tags.xml:2274(entry)
+msgid "Serial power switches"
+msgstr ""
+
+#: en_US/xml-tags.xml:2276(entry)
+msgid "Two"
+msgstr ""
+
+#: en_US/xml-tags.xml:2278(member)
+msgid ""
+"Power switches enable each cluster system to power-cycle the other cluster "
+"system. Note that clusters are configured with either serial or network "
+"attached power switches and not both."
+msgstr ""
+
+#: en_US/xml-tags.xml:2283(member)
+msgid "The following serial attached power switch has been fully tested:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2286(member)
+msgid "RPS-10 (model M/HD in the US, and model M/EC in Europe)"
+msgstr ""
+d33 3
+a35 5
+#: en_US/xml-tags.xml:2289(member)
+msgid ""
+"Latent support is provided for the following serial attached power switch. "
+"This switch has not yet been fully tested:"
+msgstr ""
+d37 3
+a39 3
+#: en_US/xml-tags.xml:2294(ulink)
+msgid "http://www.apc.com/"
+msgstr ""
+d41 4
+a44 3
+#: en_US/xml-tags.xml:2293(member)
+msgid "APC Serial On/Off Switch (partAP9211), <placeholder-1/>"
+msgstr ""
+d46 4
+a49 3
+#: en_US/xml-tags.xml:2297(entry)
+msgid "Strongly recommended for data integrity under all failure conditions"
+msgstr ""
+d51 3
+a53 3
+#: en_US/xml-tags.xml:2310(command) en_US/xml-tags.xml:2314(command)
+msgid "trademark"
+msgstr ""
+d55 3
+a57 7
+#: en_US/xml-tags.xml:2318(para)
+msgid ""
+"Do not use the trademark entities &trade;, &copy;, or &reg; "
+"because the do not produce HTML output that works for all charsets. The HTML "
+"output produces by these entities are declared in the DTD and cannot be "
+"changed via the stylesheet."
+msgstr ""
+d59 2
+a60 4
+#: en_US/xml-tags.xml:2323(para)
+msgid ""
+"Instead, use the <command>trademark</command> tag and its associates classes "
+"as follows:"
+d63 4
+a66 149
+#: en_US/xml-tags.xml:2328(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<trademark>trademark symbol after me</trademark>\n"
+"<trademark class=\"registered\">registered trademark symbol after me</trademark>\n"
+"<trademark class=\"copyright\">copyright symbol after me</trademark>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2338(command) en_US/xml-tags.xml:2342(command)
+msgid "userinput"
+msgstr ""
+
+#: en_US/xml-tags.xml:2345(para)
+msgid ""
+"To show what a user would type, use the <command>userinput</command> tag. "
+"For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2350(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"At the prompt, type:\n"
+"\n"
+"<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2361(para)
+msgid "At the prompt, type:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2366(userinput)
+#, no-wrap
+msgid "dd if=boot.img of=/dev/fd0 bs=1440k"
+msgstr ""
+
+#: en_US/xml-tags.xml:2393(command) en_US/xml-tags.xml:2397(secondary)
+#: en_US/emacs.xml:540(computeroutput)
+msgid "ulink"
+msgstr ""
+
+#: en_US/xml-tags.xml:2400(para)
+msgid "To create a URL link within your text, use the following example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2404(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Online &mdash; <ulink url=\"http://www.redhat.com/support/errata/\">\n"
+"http://www.redhat.com/support/errata/</ulink>; supplies errata \n"
+"you can read online, and you can download diskette images easily.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2415(para)
+msgid ""
+"Online —<ulink url=\"http://www.redhat.com/support/errata/\"> http://"
+"www.redhat.com/support/errata/</ulink>; supplies errata you can read online, "
+"and you can download diskette images easily."
+msgstr ""
+
+#: en_US/xml-tags.xml:2423(para)
+msgid ""
+"If the URL does not end in a filename, it must end in a slash "
+"(<computeroutput>/</computeroutput>) to be a properly formed URL. For "
+"example, <ulink url=\"http://www.redhat.com/\">http://www.redhat.com/</"
+"ulink>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2434(command) en_US/xml-tags.xml:2438(secondary)
+msgid "wordasword"
+msgstr ""
+
+#: en_US/xml-tags.xml:2441(para)
+msgid ""
+"The <wordasword> tag set is used to define a word meant specifically "
+"as a word and not representing anything else."
+msgstr ""
+
+#: en_US/xml-tags.xml:2444(para)
+msgid ""
+"A lot of technical documentation contains words that have overloaded "
+"meanings. Sometimes it is useful to be able to use a word without invoking "
+"its technical meaning. The <wordasword> element identifies a word or "
+"phrase that might otherwise be interpreted in some specific way, and asserts "
+"that it should be interpreted simply as a word."
+msgstr ""
+
+#: en_US/xml-tags.xml:2450(para)
+msgid ""
+"It is unlikely that the presentation of this element will be able to help "
+"readers understand the variation in meaning; good writing will have to "
+"achieve that goal. The real value of <wordasword> lies in the fact "
+"that full-text searching and indexing tools can use it to avoid false-"
+"positives."
+msgstr ""
+
+#: en_US/xml-tags.xml:2459(computeroutput)
+#, no-wrap
+msgid ""
+"To use <command>grep</command> to search for the word\n"
+"<wordasword>linux</wordasword>, use the command \n"
+"<command>grep linux</command>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2468(para)
+msgid ""
+"To use <command>grep</command> to search for the word <wordasword>linux</"
+"wordasword>, use the command <command>grep linux</command>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2472(para)
+msgid ""
+"In the example, the word \"linux\" is just a word. It is not meant to convey "
+"anything about Linux as a subject, or to add relevance or meaning to the "
+"content. It can be replaced with any other word without losing any of the "
+"context."
+msgstr ""
+
+#: en_US/xml-tags.xml:2481(command) en_US/xml-tags.xml:2485(secondary)
+msgid "xref"
+msgstr ""
+
+#: en_US/xml-tags.xml:2488(para)
+msgid ""
+"To refer to other sections or chapters within a manual, use the <command><"
+"xref></command> tag."
+msgstr ""
+
+#: en_US/xml-tags.xml:2493(para)
+msgid ""
+"The output of this displays the title of the section or chapter you are "
+"pointing the user to. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2498(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"For more information about the parent file, refer to\n"
+"<xref linkend=\"ch-tutorial\"></xref> and <xref linkend=\"sn-tutorial-parent\"></xref>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2508(para)
+msgid ""
+"For more information about the parent file, refer to <xref linkend=\"ch-"
+"tutorial\"/> and <xref linkend=\"sn-tutorial-parent\"/>."
+msgstr ""
+d207 1
+a207 1
+#: en_US/tutorial.xml:12(title)
+d213 4
+a216 5
+"In this chapter, you will find an example of a Fedora Project documentation "
+"parent file. This example is specific to the way the Docs Project uses "
+"DocBook XML. The parent file contains the main structural format of the "
+"book, a link to the entities file that contain common entities that should "
+"be used, and an entity to change the version and date of the tutorial."
+d219 2
+a220 2
+#: en_US/tutorial.xml:23(title)
+msgid "The Parent File"
+d223 2
+a224 2
+#: en_US/tutorial.xml:25(para)
+msgid "Below is a sample parent file:"
+d227 2
+a228 54
+#: en_US/tutorial.xml:30(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<!DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook XML V4.2//EN\"\n"
+" \"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd\" [\n"
+"\n"
+"<!ENTITY % FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-en.xml\">\n"
+"%FEDORA-ENTITIES-EN;\n"
+"\n"
+"<!ENTITY VERSION \"0.1\"> <!-- change version of tutorial here -->\n"
+"\n"
+"<!ENTITY DOCID \"example-tutorial-&VERSION; (2003-07-07)\"> <!-- change last modified date here -->\n"
+"\n"
+"<!ENTITY LEGALNOTICE SYSTEM \"../common/legalnotice-en.xml\">\n"
+"\n"
+"\n"
+"]>\n"
+"\n"
+"<article id=\"example-tutorial\" lang=\"en\">\n"
+" <articleinfo>\n"
+" <title>Example Tutorial</title>\n"
+" <copyright>\n"
+" <year>2003</year>\n"
+" <holder>Red Hat Inc.</holder>\n"
+" <holder>Tammy Fox</holder>\n"
+" </copyright>\n"
+" <authorgroup>\n"
+" <author>\n"
+"\t<surname>Fox</surname>\n"
+"\t<firstname>Tammy</firstname>\n"
+" </author>\n"
+" </authorgroup>\n"
+" &LEGALNOTICE;\n"
+" </articleinfo>\n"
+"\n"
+" <section id=\"some-section\">\n"
+" <title>Some Section</title>\n"
+"\n"
+" <para>\n"
+" This is an example section. You can also use section, section, etc.\n"
+" </para>\n"
+"\n"
+" <warning>\n"
+" <title>Warning</title>\n"
+" <para>\n"
+"\tExample of an admonition.\n"
+" </para>\n"
+" </warning>\n"
+"\n"
+" </section>\n"
+"\n"
+"<index id=\"generated-index\"></index>\n"
+"</article>\n"
+d231 2
+a232 2
+#: en_US/tutorial.xml:87(title)
+msgid "Including the License Information"
+d235 2
+a236 2
+#: en_US/tutorial.xml:90(primary)
+msgid "tutorial layout"
+d239 2
+a240 2
+#: en_US/tutorial.xml:91(secondary)
+msgid "license"
+d243 1
+a243 1
+#: en_US/tutorial.xml:94(para)
+d245 8
+a252 3
+"All Fedora Project manuals <emphasis>must</emphasis> contain the file "
+"<filename>legalnotice.xml</filename>. This file makes the license for the "
+"file the GNU Free Documentation License (FDL)."
+d255 6
+a260 2
+#: en_US/tutorial.xml:100(para)
+msgid "The sample parent file shows how it is included."
+d330 5
+a334 5
+"<citetitle>Ulysses</citetitle><footnote id=\"fn-ulysses\"><placeholder-1/></"
+"footnote>. There, Joyce uses long streams of words without punctuation to "
+"simulate a character's internal consciousness. By violating basic rules of "
+"grammar and syntax, Joyce simulates the disorganized but loosely connected "
+"thought patterns of the narrator."
+d642 2
+a643 1
+msgid "There is a text box that you can use to find out the definition of a word."
+d842 2
+a843 1
+msgid "The term does not appear in the glossary of the manual that you are writing."
+d847 2
+a848 1
+msgid "The term is not defined in the body text of the manual that you are writing."
+d1102 2
+a1103 1
+msgid "the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+d1508 4
+d1525 2
+a1526 1
+msgid "Numbers from zero through nine unless the number is part of a measurement"
+d1999 1
+a1999 1
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:259(title)
+d2050 1
+a2050 1
+"<warning><placeholder-1/><placeholder-2/></warning>"
+d2062 2
+a2063 1
+msgid "Follow the capitalization rules for headings in the title of an admonition."
+d2120 11
+d2132 31
+d2166 23
+a2188 3
+#: en_US/writing-guidelines.xml:42(secondary)
+#: en_US/writing-guidelines.xml:46(primary)
+#: en_US/writing-guidelines.xml:59(primary)
+d2192 1
+a2192 1
+#: en_US/writing-guidelines.xml:49(para)
+d2199 2
+a2200 2
+#: en_US/writing-guidelines.xml:55(secondary)
+#: en_US/writing-guidelines.xml:60(secondary)
+d2204 1
+a2204 1
+#: en_US/writing-guidelines.xml:63(para)
+d2208 1
+a2208 1
+#: en_US/writing-guidelines.xml:67(para)
+d2212 1
+a2212 1
+#: en_US/writing-guidelines.xml:70(para)
+d2219 1
+a2219 1
+#: en_US/writing-guidelines.xml:76(para)
+d2225 1
+a2225 1
+#: en_US/writing-guidelines.xml:82(title)
+d2229 1
+a2229 1
+#: en_US/writing-guidelines.xml:91(title)
+d2233 1
+a2233 1
+#: en_US/writing-guidelines.xml:92(segtitle)
+d2237 1
+a2237 1
+#: en_US/writing-guidelines.xml:93(segtitle)
+d2241 1
+a2241 1
+#: en_US/writing-guidelines.xml:95(sgmltag)
+d2245 1
+a2245 1
+#: en_US/writing-guidelines.xml:96(literal)
+d2249 5
+a2253 1
+#: en_US/writing-guidelines.xml:100(literal)
+d2257 1
+a2257 1
+#: en_US/writing-guidelines.xml:103(sgmltag)
+d2261 1
+a2261 1
+#: en_US/writing-guidelines.xml:104(literal)
+d2265 5
+a2269 1
+#: en_US/writing-guidelines.xml:108(literal)
+d2273 6
+a2278 1
+#: en_US/writing-guidelines.xml:112(literal)
+d2282 1
+a2282 1
+#: en_US/writing-guidelines.xml:115(sgmltag)
+d2286 1
+a2286 1
+#: en_US/writing-guidelines.xml:116(literal)
+d2290 5
+a2294 1
+#: en_US/writing-guidelines.xml:120(literal)
+d2298 5
+a2302 1
+#: en_US/writing-guidelines.xml:124(literal)
+d2306 1
+a2306 1
+#: en_US/writing-guidelines.xml:128(para)
+d2312 14
+a2325 1
+#: en_US/writing-guidelines.xml:141(para)
+d2331 5
+a2335 1
+#: en_US/writing-guidelines.xml:151(para)
+d2344 1
+a2344 1
+#: en_US/writing-guidelines.xml:159(para)
+d2350 26
+a2375 1
+#: en_US/writing-guidelines.xml:186(para)
+d2382 1
+a2382 1
+#: en_US/writing-guidelines.xml:191(para)
+d2389 17
+a2405 1
+#: en_US/writing-guidelines.xml:216(term)
+d2411 1
+a2411 1
+#: en_US/writing-guidelines.xml:219(para)
+d2419 3
+a2421 3
+#: en_US/writing-guidelines.xml:243(title)
+msgid "File Header"
+msgstr ""
+d2423 1
+a2423 1
+#: en_US/writing-guidelines.xml:245(para)
+d2425 4
+a2428 2
+"All the files must contain the CVS Id header. If you create a new file, the "
+"first line must be:"
+d2430 4
+d2435 6
+a2440 13
+#: en_US/writing-guidelines.xml:250(para)
+msgid ""
+"The first time it is committed to CVS (and every time it is committed to "
+"CVS) the line is updated automatically to include information about the "
+"file. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:262(primary)
+#: en_US/writing-guidelines.xml:292(secondary)
+#: en_US/writing-guidelines.xml:298(secondary)
+#: en_US/writing-guidelines.xml:304(secondary)
+#: en_US/writing-guidelines.xml:310(secondary)
+#: en_US/writing-guidelines.xml:316(secondary)
+d2444 3
+a2446 3
+#: en_US/writing-guidelines.xml:267(secondary)
+#: en_US/writing-guidelines.xml:293(tertiary)
+#: en_US/writing-guidelines.xml:362(secondary)
+d2450 3
+a2452 3
+#: en_US/writing-guidelines.xml:272(secondary)
+#: en_US/writing-guidelines.xml:299(tertiary)
+#: en_US/writing-guidelines.xml:347(secondary)
+d2456 3
+a2458 3
+#: en_US/writing-guidelines.xml:277(secondary)
+#: en_US/writing-guidelines.xml:305(tertiary)
+#: en_US/writing-guidelines.xml:342(secondary)
+d2462 3
+a2464 3
+#: en_US/writing-guidelines.xml:282(secondary)
+#: en_US/writing-guidelines.xml:311(tertiary)
+#: en_US/writing-guidelines.xml:352(secondary)
+d2468 3
+a2470 3
+#: en_US/writing-guidelines.xml:287(secondary)
+#: en_US/writing-guidelines.xml:317(tertiary)
+#: en_US/writing-guidelines.xml:357(secondary)
+d2474 1
+a2474 1
+#: en_US/writing-guidelines.xml:320(para)
+d2487 1
+a2487 1
+#: en_US/writing-guidelines.xml:334(title)
+d2495 1
+a2495 1
+#: en_US/writing-guidelines.xml:365(para)
+d2514 1
+a2514 1
+#: en_US/writing-guidelines.xml:385(para)
+d2520 9
+a2528 4
+#: en_US/writing-guidelines.xml:395(para)
+#: en_US/writing-guidelines.xml:415(para)
+#: en_US/writing-guidelines.xml:425(para)
+#: en_US/writing-guidelines.xml:435(para)
+d2532 1
+a2532 2
+#: en_US/writing-guidelines.xml:404(title) en_US/emacs.xml:348(title)
+#: en_US/emacs.xml:396(title) en_US/emacs-nxml.xml:114(title)
+d2536 1
+a2536 1
+#: en_US/writing-guidelines.xml:405(para)
+d2540 1
+a2540 1
+#: en_US/writing-guidelines.xml:414(title)
+d2544 9
+a2552 1
+#: en_US/writing-guidelines.xml:442(title)
+d2556 2
+a2557 2
+#: en_US/writing-guidelines.xml:445(primary)
+#: en_US/writing-guidelines.xml:450(see) en_US/writing-guidelines.xml:454(see)
+d2561 1
+a2561 1
+#: en_US/writing-guidelines.xml:446(secondary)
+d2565 1
+a2565 1
+#: en_US/writing-guidelines.xml:449(primary)
+d2569 1
+a2569 1
+#: en_US/writing-guidelines.xml:453(primary)
+d2573 1
+a2573 1
+#: en_US/writing-guidelines.xml:457(para)
+d2575 7
+a2581 6
+"There are two types of screenshots: graphical and textual. The philosophy on "
+"using these two types is <firstterm>rely on text over graphics</firstterm>. "
+"This means, if you can say it in text instead of showing a graphic, do so. A "
+"graphical screenshot of a GUI can create a good setting of objects to then "
+"describe textually, but you don't want to create a screenshot for each "
+"graphical step."
+d2584 1
+a2584 1
+#: en_US/writing-guidelines.xml:464(para)
+d2586 7
+a2592 5
+"The main reason for this preference is that a block of text can usually "
+"convey more meaning than the same physical space of graphics. This is highly "
+"dependent on the graphic; obviously, a photographic image of a scene can "
+"convey more than 1000 words can. A GUI screenshot is usually full of blank "
+"space with a few elements that can just as easily be described or listed."
+d2595 1
+a2595 1
+#: en_US/writing-guidelines.xml:470(para)
+d2601 1
+a2601 1
+#: en_US/writing-guidelines.xml:475(term)
+d2605 1
+a2605 1
+#: en_US/writing-guidelines.xml:479(para)
+d2607 4
+a2610 15
+"Set the theme to Bluecurve defaults. This gives a look that is familiar to "
+"most readers, and makes Fedora Documentation Project documents consistent. "
+"From the panel menu, choose <guimenu>Preferences</guimenu>, "
+"<guimenuitem>Theme</guimenuitem> and select <guimenuitem>Bluecurve</"
+"guimenuitem> from the theme list."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:488(para)
+msgid ""
+"Set fonts to Bluecurve defaults as well. From the panel menu, choose "
+"<guimenu>Preferences</guimenu>, <guimenuitem>Fonts</guimenuitem>. Set the "
+"<guilabel>Application font</guilabel> and the <guilabel>Desktop font</"
+"guilabel> to Sans Regular 10. Set the <guilabel>Window Title font</guilabel> "
+"to Sans Bold 10. Set the <guilabel>Terminal font</guilabel> to Monospace "
+"Regular 10."
+d2615 4
+a2618 4
+"Before taking the screenshot, try to resize the targeted GUI element(s) to "
+"the smallest possible size they can be. Your target is an image of 500 "
+"pixels or less. If you are doing a screenshot of more than one GUI element, "
+"you may need to resize the screenshot in a following step."
+d2623 2
+a2624 2
+"To take the screenshot, select the GUI element with your mouse, bringing it "
+"to the forefront, or otherwise arranging the elements. Press "
+d2627 25
+a2651 14
+"<keycap>Print Screen</keycap>. If you are taking a shot of multiple elements "
+"and have grouped them closely together, you can crop the resulting image in "
+"<application>The GIMP</application>. The image will be in the PNG format."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:519(para)
+msgid ""
+"If you need to, you can resize using <application>The GIMP</application>. "
+"With the image open, right-click on it and choose <guimenu>Image</guimenu> -"
+"> <guimenuitem>Scale Image...</guimenuitem>. With the chain symbol "
+"intact, set the <guilabel>New Width</guilabel> to <guilabel>500 px</"
+"guilabel>, and click <guibutton>OK</guibutton>. Be sure to "
+"<keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo> to save your "
+"changes to your PNG before converting to EPS."
+d2654 1
+a2654 1
+#: en_US/writing-guidelines.xml:532(para)
+d2656 1
+a2656 10
+"With the image open in <application>The GIMP</application>, right-click on "
+"the image, selecting <guimenu>File</guimenu> -> <guimenuitem>Save As...</"
+"guimenuitem>. Under <guimenu>Determine File Type:</guimenu>, select "
+"<guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</guibutton>. "
+"Allow flattening of the image by clicking <guibutton>Export</guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:541(para)
+msgid ""
+"In the <guilabel>Save as PostScript</guilabel> window, select "
+d2661 1
+a2661 1
+#: en_US/writing-guidelines.xml:555(term)
+d2665 1
+a2665 1
+#: en_US/writing-guidelines.xml:557(para)
+d2671 1
+a2671 1
+#: en_US/writing-guidelines.xml:561(para)
+d2673 3
+a2675 3
+"If you use a graphical screenshot to illustrate a function, and the textual "
+"mode has identical functions, do not include both, unless omitting either "
+"would make your description unclear."
+d2678 1
+a2678 1
+#: en_US/writing-guidelines.xml:567(para)
+d2680 1
+a2680 1
+"Make your information generic over specific, and omit any username and "
+d2685 1
+a2685 1
+#: en_US/writing-guidelines.xml:573(para)
+d2689 1
+a2689 1
+#: en_US/writing-guidelines.xml:577(para)
+d2697 1
+a2697 1
+#: en_US/writing-guidelines.xml:585(para)
+d2703 1
+a2703 1
+#: en_US/writing-guidelines.xml:590(title)
+d2707 3
+a2709 2
+#: en_US/writing-guidelines.xml:603(para)
+msgid "To find all the currently active ssh sessions, execute the following command:"
+d2712 1
+a2712 1
+#: en_US/writing-guidelines.xml:605(userinput)
+d2717 1
+a2717 1
+#: en_US/writing-guidelines.xml:607(para)
+d2721 1
+a2721 1
+#: en_US/writing-guidelines.xml:609(computeroutput)
+d2750 2
+a2751 1
+"module, excluding any <filename class=\"directory\">CVS</filename> folders:"
+d2754 1
+a2754 1
+#: en_US/module-struct.xml:24(title)
+d2758 1
+a2758 1
+#: en_US/module-struct.xml:45(title)
+d2762 1
+a2762 1
+#: en_US/module-struct.xml:46(segtitle)
+d2766 1
+a2766 1
+#: en_US/module-struct.xml:47(segtitle)
+d2770 1
+a2770 1
+#: en_US/module-struct.xml:48(segtitle)
+d2774 1
+a2774 1
+#: en_US/module-struct.xml:50(seg)
+d2778 2
+a2779 2
+#: en_US/module-struct.xml:51(seg) en_US/module-struct.xml:88(seg)
+#: en_US/module-struct.xml:95(seg)
+d2783 2
+a2784 2
+#: en_US/module-struct.xml:54(filename)
+#: en_US/module-struct.xml:160(systemitem)
+d2788 1
+a2788 1
+#: en_US/module-struct.xml:58(firstterm)
+d2792 1
+a2792 1
+#: en_US/module-struct.xml:59(para)
+d2800 1
+a2800 1
+#: en_US/module-struct.xml:52(seg)
+d2806 1
+a2806 2
+"XML source for document-specific <placeholder-2/><footnote><placeholder-3/></"
+"footnote>."
+d2809 1
+a2809 1
+#: en_US/module-struct.xml:67(seg)
+d2813 1
+a2813 1
+#: en_US/module-struct.xml:68(seg) en_US/module-struct.xml:78(seg)
+d2817 1
+a2817 1
+#: en_US/module-struct.xml:69(filename) en_US/module-struct.xml:73(filename)
+d2821 1
+a2821 1
+#: en_US/module-struct.xml:69(seg)
+d2829 1
+a2829 1
+#: en_US/module-struct.xml:77(seg)
+d2833 1
+a2833 1
+#: en_US/module-struct.xml:79(filename) en_US/module-struct.xml:167(filename)
+d2837 5
+a2841 1
+#: en_US/module-struct.xml:79(seg)
+d2843 5
+a2847 5
+"The <placeholder-1/> directory contains specially formatted files created "
+"and used by translators. The Fedora Documentation Project build tools use "
+"these files to create translated versions of documents. The translated "
+"documents are not stored in CVS; they are created as needed from these PO "
+"files."
+d2850 1
+a2850 1
+#: en_US/module-struct.xml:87(seg) en_US/module-struct.xml:89(filename)
+d2854 1
+a2854 1
+#: en_US/module-struct.xml:89(seg)
+d2860 1
+a2860 1
+#: en_US/module-struct.xml:94(filename) en_US/module-struct.xml:96(filename)
+d2864 1
+a2864 1
+#: en_US/module-struct.xml:96(seg)
+d2869 12
+d2884 10
+a2893 1
+#: en_US/module-struct.xml:103(para)
+d2897 3
+a2899 2
+"command> and shell scripts. Authors need <emphasis>no</emphasis> prior "
+"experience with either shell scripts or a <command>make(1)</command>."
+d2902 1
+a2902 1
+#: en_US/module-struct.xml:111(title)
+d2906 1
+a2906 1
+#: en_US/module-struct.xml:112(para)
+d2913 1
+a2913 1
+#: en_US/module-struct.xml:118(para)
+d2919 1
+a2919 1
+#: en_US/module-struct.xml:124(title)
+d2923 1
+a2923 1
+#: en_US/module-struct.xml:141(para)
+d2930 1
+a2930 1
+#: en_US/module-struct.xml:147(title)
+d2934 1
+a2934 1
+#: en_US/module-struct.xml:148(segtitle)
+d2938 1
+a2938 1
+#: en_US/module-struct.xml:149(segtitle) en_US/module-struct.xml:263(segtitle)
+d2942 1
+a2942 1
+#: en_US/module-struct.xml:151(systemitem)
+d2946 1
+a2946 1
+#: en_US/module-struct.xml:152(seg)
+d2952 1
+a2952 1
+#: en_US/module-struct.xml:157(systemitem)
+d2956 1
+a2956 1
+#: en_US/module-struct.xml:158(seg)
+d2962 1
+a2962 1
+#: en_US/module-struct.xml:163(systemitem)
+d2966 1
+a2966 1
+#: en_US/module-struct.xml:164(seg)
+d2974 1
+a2974 1
+#: en_US/module-struct.xml:171(systemitem)
+d2978 1
+a2978 1
+#: en_US/module-struct.xml:172(seg)
+d2986 1
+a2986 1
+#: en_US/module-struct.xml:181(systemitem)
+d2990 1
+a2990 1
+#: en_US/module-struct.xml:184(systemitem)
+d2994 1
+a2994 1
+#: en_US/module-struct.xml:189(systemitem)
+d2998 1
+a2998 1
+#: en_US/module-struct.xml:182(seg)
+d3008 1
+a3008 1
+#: en_US/module-struct.xml:195(title)
+d3012 1
+a3012 1
+#: en_US/module-struct.xml:196(para)
+d3018 1
+a3018 1
+#: en_US/module-struct.xml:200(para)
+d3027 1
+a3027 1
+#: en_US/module-struct.xml:209(title)
+d3031 1
+a3031 1
+#: en_US/module-struct.xml:210(para)
+d3040 1
+a3040 17
+#: en_US/module-struct.xml:216(para)
+msgid "<xref linkend=\"ex-rpminfo\"/> illustrates the content of this file:"
+msgstr ""
+
+#: en_US/module-struct.xml:219(title)
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr ""
+
+#: en_US/module-struct.xml:248(para)
+msgid ""
+"If you are not familiar with XML editing, copy and paste this file from an "
+"existing module and then edit the values for the various elements as "
+"appropriate. Consult Fedora Documentation Project members and help channels "
+"for more assistance if needed."
+msgstr ""
+
+#: en_US/module-struct.xml:255(title)
+d3044 1
+a3044 1
+#: en_US/module-struct.xml:256(para)
+d3050 1
+a3050 1
+#: en_US/module-struct.xml:261(title)
+d3054 1
+a3054 1
+#: en_US/module-struct.xml:262(segtitle)
+d3058 1
+a3058 1
+#: en_US/module-struct.xml:265(systemitem)
+d3062 2
+a3063 2
+#: en_US/module-struct.xml:266(abbrev) en_US/module-struct.xml:277(abbrev)
+#: en_US/module-struct.xml:302(abbrev) en_US/module-struct.xml:307(abbrev)
+d3067 2
+a3068 2
+#: en_US/module-struct.xml:270(systemitem)
+#: en_US/module-struct.xml:280(systemitem)
+d3072 2
+a3073 2
+#: en_US/module-struct.xml:271(systemitem)
+#: en_US/module-struct.xml:281(systemitem)
+d3077 1
+a3077 1
+#: en_US/module-struct.xml:269(filename)
+d3081 1
+a3081 1
+#: en_US/module-struct.xml:266(seg)
+d3089 1
+a3089 1
+#: en_US/module-struct.xml:276(systemitem)
+d3093 1
+a3093 1
+#: en_US/module-struct.xml:279(filename)
+d3097 1
+a3097 1
+#: en_US/module-struct.xml:277(seg)
+d3104 1
+a3104 1
+#: en_US/module-struct.xml:285(systemitem)
+d3108 2
+a3109 2
+#: en_US/module-struct.xml:286(abbrev) en_US/module-struct.xml:287(abbrev)
+#: en_US/module-struct.xml:303(abbrev) en_US/module-struct.xml:308(abbrev)
+d3113 1
+a3113 1
+#: en_US/module-struct.xml:286(seg)
+d3120 1
+a3120 1
+#: en_US/module-struct.xml:291(systemitem)
+d3124 1
+a3124 1
+#: en_US/module-struct.xml:292(command)
+d3128 1
+a3128 1
+#: en_US/module-struct.xml:292(seg)
+d3134 1
+a3134 1
+#: en_US/module-struct.xml:296(systemitem)
+d3138 1
+a3138 1
+#: en_US/module-struct.xml:297(seg)
+d3142 2
+a3143 2
+#: en_US/module-struct.xml:300(systemitem)
+#: en_US/module-struct.xml:309(filename)
+d3147 1
+a3147 1
+#: en_US/module-struct.xml:302(emphasis)
+d3151 1
+a3151 1
+#: en_US/module-struct.xml:301(seg)
+d3157 1
+a3157 1
+#: en_US/module-struct.xml:306(systemitem)
+d3161 1
+a3161 1
+#: en_US/module-struct.xml:307(seg)
+d3167 11
+a3177 1
+#: en_US/module-struct.xml:314(title)
+d3181 1
+a3181 1
+#: en_US/module-struct.xml:315(para)
+d3190 1
+a3190 1
+#: en_US/module-struct.xml:323(para)
+d3196 1
+a3196 1
+#: en_US/module-struct.xml:330(title)
+d3200 1
+a3200 1
+#: en_US/module-struct.xml:331(para)
+d3208 1
+a3208 1
+#: en_US/module-struct.xml:338(para)
+d3221 1
+a3221 1
+#: en_US/module-struct.xml:352(para)
+d3228 1
+a3228 1
+#: en_US/module-struct.xml:358(para)
+d3238 1
+a3238 1
+#: en_US/module-struct.xml:368(para)
+d3247 1
+a3247 1
+#: en_US/module-struct.xml:377(para)
+d3253 1
+a3253 1
+#: en_US/module-struct.xml:383(title)
+d3257 1
+a3257 1
+#: en_US/module-struct.xml:390(title)
+d3261 3
+a3263 2
+#: en_US/module-struct.xml:391(para)
+msgid "To add a new DocBook XML file to an existing document, follow these steps:"
+d3266 1
+a3266 1
+#: en_US/module-struct.xml:395(para)
+d3270 1
+a3270 1
+#: en_US/module-struct.xml:399(para)
+d3279 1
+a3279 1
+#: en_US/module-struct.xml:409(title)
+d3283 1
+a3283 1
+#: en_US/module-struct.xml:410(para)
+d3291 1
+a3291 1
+#: en_US/module-struct.xml:417(para)
+d3297 1
+a3297 1
+#: en_US/module-struct.xml:423(para)
+d3301 1
+a3301 1
+#: en_US/module-struct.xml:427(para)
+d3307 1
+a3307 1
+#: en_US/module-struct.xml:432(para)
+d3313 1
+a3313 1
+#: en_US/module-struct.xml:435(replaceable)
+d3317 1
+a3317 1
+#: en_US/module-struct.xml:435(screen)
+d3329 2
+a3330 5
+"task-based documentation for Fedora users and developers. Other than the "
+"<citetitle>Installation Guide</citetitle>, each tutorial should be in "
+"DocBook XML article format, with one article per topic. This way, writers "
+"can contribute documentation about a specific topic without having to worry "
+"about how it fits into a manual or how it flows with other topics."
+d3333 1
+a3333 5
+#: en_US/intro.xml:25(para)
+msgid "The following tools are used:"
+msgstr ""
+
+#: en_US/intro.xml:31(para)
+d3337 1
+a3337 1
+#: en_US/intro.xml:34(para)
+d3341 1
+a3341 1
+#: en_US/intro.xml:38(para)
+d3345 1
+a3345 1
+#: en_US/intro.xml:42(para)
+d3349 1
+a3349 1
+#: en_US/intro.xml:51(para)
+d3392 13
+a3404 1
+#: en_US/getting-files.xml:43(title)
+d3408 1
+a3408 1
+#: en_US/getting-files.xml:45(para)
+d3412 4
+a3415 2
+"systemitem> CVS server. Check them out along with the DocBook XML files for "
+"the existing docs."
+d3418 8
+a3425 3
+#: en_US/getting-files.xml:53(replaceable)
+#: en_US/getting-files.xml:54(replaceable)
+msgid "my-fedora-docs-sandbox"
+d3428 10
+a3437 3
+#: en_US/getting-files.xml:55(replaceable)
+msgid "username"
+msgstr "utilizador"
+d3439 1
+a3439 2
+#: en_US/getting-files.xml:53(userinput)
+#, no-wrap
+d3441 6
+a3446 5
+"mkdir <placeholder-1/>\n"
+"cd <placeholder-2/>\n"
+"export CVSROOT=:ext:<placeholder-3/>@@cvs.fedora.redhat.com:/cvs/docs\n"
+"cvs login\n"
+"cvs co docs-common"
+d3449 7
+a3455 2
+#: en_US/getting-files.xml:60(para)
+msgid "At the password prompt, press the <keycap>Enter</keycap> key."
+d3458 4
+a3461 3
+#: en_US/getting-files.xml:65(title)
+msgid "Common Files"
+msgstr ""
+d3463 1
+a3463 1
+#: en_US/getting-files.xml:66(para)
+d3465 4
+a3468 7
+"You need to perform this \"checkout\" step only once, although you may need "
+"to update the files later. These files are common to all the official "
+"documentation."
+msgstr ""
+
+#: en_US/getting-files.xml:73(para)
+msgid "To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+d3471 2
+a3472 2
+#: en_US/getting-files.xml:80(title)
+msgid "Filename Conventions"
+d3475 1
+a3475 1
+#: en_US/getting-files.xml:81(para)
+d3481 1
+a3481 1
+"of these services, you must follow conventions for naming your files."
+d3484 8
+a3491 2
+#: en_US/getting-files.xml:89(title)
+msgid "Document Filenames"
+d3494 1
+a3494 1
+#: en_US/getting-files.xml:90(para)
+d3496 1
+a3496 4
+"Each document lives in a peer directory to the <filename>docs-common</"
+"filename> directory you extracted from the Fedora archive earlier. On the "
+"CVS server, these directories are called <firstterm>modules</firstterm>. Use "
+"the <command>cvs co -c</command> command to view existing module names."
+d3499 1
+a3499 1
+#: en_US/getting-files.xml:98(title)
+d3503 1
+a3503 1
+#: en_US/getting-files.xml:99(userinput)
+d3508 22
+a3529 2
+#: en_US/getting-files.xml:100(computeroutput)
+#, no-wrap
+d3531 7
+a3537 8
+"build-docs infrastructure/build-docs\n"
+"cvsroot CVSROOT\n"
+"desktop-up2date desktop-up2date\n"
+"developer-guide developer-guide\n"
+"docs .\n"
+"docs-common docs-common\n"
+"documentation-guide documentation-guide\n"
+"example-tutorial example-tutorial"
+d3540 1
+a3540 1
+#: en_US/getting-files.xml:109(para)
+d3543 4
+a3546 1
+"avoid any name already taken."
+d3549 1
+a3549 1
+#: en_US/getting-files.xml:112(title)
+d3553 1
+a3553 1
+#: en_US/getting-files.xml:113(para)
+d3555 1
+a3555 1
+"Do not use the word <wordasword>Fedora</wordasword> to name modules in the "
+d3559 74
+d3642 3
+a3644 3
+#: en_US/emacs.xml:43(primary) en_US/emacs.xml:232(primary)
+#: en_US/emacs.xml:241(primary) en_US/emacs.xml:246(primary)
+#: en_US/emacs.xml:251(primary) en_US/emacs.xml:526(application)
+d3686 1
+a3686 126
+"the following lines: <screen><computeroutput><![CDATA[\n"
+";; turn on auto-fill in `text-mode' and derived modes \n"
+";;(mail, news, etc)\n"
+"(add-hook 'text-mode-hook 'turn-on-auto-fill)\n"
+"\n"
+";;\n"
+";;MODES\n"
+";;\n"
+"\n"
+"(setq auto-mode-alist (cons '(\"\\\\.sgml$\" . sgml-mode) auto-mode-alist))\n"
+"(setq auto-mode-alist (cons '(\"\\\\.sgm$\" . sgml-mode) auto-mode-alist))\n"
+"\n"
+";;\n"
+";;XML!!\n"
+";;\n"
+";;#############################################################\n"
+"\n"
+";;\n"
+";;PSGML mode stuff\n"
+";;\n"
+"\n"
+"(autoload 'sgml-mode \"psgml\" \"My Most Major Mode\" t)\n"
+"\n"
+"(setq sgml-mode-hook '(lambda () \"Defaults for XML mode.\" (turn-on-auto-"
+"fill) \n"
+"(setq fill-column 80)))\n"
+"\n"
+"(defun My-XML-keymap ()\n"
+" (local-set-key [(alt i)] \n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-indent-line)\n"
+" (sgml-insert-element 'item)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt l)] \n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-insert-element 'list)\n"
+" (sgml-insert-element 'item)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt p)]\n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-indent-line)\n"
+" (sgml-insert-element 'para)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt -)]\n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (insert \"—\")))) \n"
+"\n"
+"(add-hook 'sgml-mode-hook 'My-XML-keymap)\n"
+"\n"
+";;\n"
+";; Fix up indentation of data...\n"
+";;\n"
+"\n"
+"(setq-default sgml-indent-data t)\n"
+"\n"
+";;\n"
+";; XML markup faces.\n"
+";;\n"
+"\n"
+"(setq-default sgml-set-face t)\n"
+"\n"
+"\n"
+"(make-face 'sgml-comment-face)\n"
+"(make-face 'sgml-doctype-face)\n"
+"(make-face 'sgml-end-tag-face)\n"
+"(make-face 'sgml-entity-face)\n"
+"(make-face 'sgml-ignored-face)\n"
+"(make-face 'sgml-ms-end-face)\n"
+"(make-face 'sgml-ms-start-face)\n"
+"(make-face 'sgml-pi-face)\n"
+"(make-face 'sgml-sgml-face)\n"
+"(make-face 'sgml-short-ref-face)\n"
+"(make-face 'sgml-start-tag-face)\n"
+"\n"
+"(set-face-foreground 'sgml-comment-face \"maroon\")\n"
+"(set-face-foreground 'sgml-doctype-face \"dark green\")\n"
+"(set-face-foreground 'sgml-end-tag-face \"blue2\")\n"
+"(set-face-foreground 'sgml-entity-face \"red2\")\n"
+"(set-face-foreground 'sgml-ignored-face \"maroon\")\n"
+"(set-face-background 'sgml-ignored-face \"gray90\")\n"
+"(set-face-foreground 'sgml-ms-end-face \"maroon\")\n"
+"(set-face-foreground 'sgml-ms-start-face \"maroon\")\n"
+"(set-face-foreground 'sgml-pi-face \"maroon\")\n"
+"(set-face-foreground 'sgml-sgml-face \"maroon\")\n"
+"(set-face-foreground 'sgml-short-ref-face \"goldenrod\")\n"
+"(set-face-foreground 'sgml-start-tag-face \"blue2\")\n"
+"\n"
+"(setq-default sgml-markup-faces\n"
+" '((comment . sgml-comment-face)\n"
+" (doctype . sgml-doctype-face)\n"
+" (end-tag . sgml-end-tag-face)\n"
+" (entity . sgml-entity-face)\n"
+" (ignored . sgml-ignored-face)\n"
+" (ms-end . sgml-ms-end-face)\n"
+" (ms-start . sgml-ms-start-face)\n"
+" (pi . sgml-pi-face)\n"
+" (sgml . sgml-sgml-face)\n"
+" (short-ref . sgml-short-ref-face)\n"
+" (start-tag . sgml-start-tag-face)))\n"
+"\n"
+"\n"
+"(defun docbook-mode ()\n"
+" (sgml-mode)\n"
+" )\n"
+"\n"
+"\n"
+"\n"
+";;\n"
+";;END XML STUFF\n"
+";;\n"
+";;##################################################################\n"
+"\n"
+";PO mode stuff\n"
+"\n"
+"(setq auto-mode-alist\n"
+"\t(cons '(\"\\\\.pox?\\\\'\" . po-mode) auto-mode-alist))\n"
+"(autoload 'po-mode \"po-mode\")\n"
+"\n"
+"\n"
+" (global-set-key [(f1)] (lambda () (interactive) (manual-\n"
+" entry (current-word))))\n"
+"]]></computeroutput></screen>"
+d3689 1
+a3689 1
+#: en_US/emacs.xml:185(para)
+d3696 1
+a3696 1
+#: en_US/emacs.xml:198(para)
+d3702 1
+a3702 1
+#: en_US/emacs.xml:229(title)
+d3706 1
+a3706 1
+#: en_US/emacs.xml:233(secondary)
+d3710 1
+a3710 1
+#: en_US/emacs.xml:237(filename)
+d3714 1
+a3714 1
+#: en_US/emacs.xml:242(secondary)
+d3718 1
+a3718 1
+#: en_US/emacs.xml:247(secondary)
+d3722 1
+a3722 1
+#: en_US/emacs.xml:252(secondary)
+d3726 1
+a3726 1
+#: en_US/emacs.xml:255(para)
+d3730 1
+a3730 1
+"<computeroutput>emacs.keyword:value</computeroutput>"
+d3733 1
+a3733 1
+#: en_US/emacs.xml:261(para)
+d3737 1
+a3737 1
+#: en_US/emacs.xml:266(para)
+d3743 2
+a3744 2
+#: en_US/emacs.xml:282(para)
+msgid "After modifying this file, you must execute the command"
+d3747 1
+a3747 1
+#: en_US/emacs.xml:286(command)
+d3751 2
+a3752 2
+#: en_US/emacs.xml:287(para)
+msgid "and restart <application>Emacs</application> for the changes to take place."
+d3755 2
+a3756 89
+#: en_US/emacs.xml:295(title)
+msgid "Create Recompiled DTD Subset"
+msgstr ""
+
+#: en_US/emacs.xml:297(para)
+msgid ""
+"Emacs will perform syntax highlighting and indent correctly on DocBook XML "
+"files if you provide it with the proper Document Type Declarations (DTD) "
+"file. These two features will make your XML file look pretty and help you "
+"spot errors."
+msgstr ""
+
+#: en_US/emacs.xml:308(para)
+msgid ""
+"Find the parent file for the group of DocBook files. You will recognize this "
+"file by the header <filename><!DOCTYPE article PUBLIC \"-//OASIS//DTD "
+"DocBook V4.1//EN\"</filename>. An easy way to find this parent file is to "
+"use the command <command>grep DocBook *.xml</command>. Once you find the "
+"parent file, open it in Emacs with the command <command>emacs "
+"<replaceable><parentfile></replaceable>.xml</command> (where "
+"<replaceable><parentfile></replaceable>.xml is the parent file you "
+"found."
+msgstr ""
+
+#: en_US/emacs.xml:321(para)
+msgid "Choose <command>DTD -> Parse DTD</command> from the pulldown menu."
+msgstr ""
+
+#: en_US/emacs.xml:327(para)
+msgid ""
+"You will know the parsing is finished when you see the message "
+"<computeroutput>Fontifying...done</computeroutput> at the bottom of your "
+"screen. Save the parsed DTD to a file by choosing <command>DTD -> Save "
+"Parsed DTD</command> from the pulldown menu."
+msgstr ""
+
+#: en_US/emacs.xml:335(para)
+msgid ""
+"Press <keycap>Enter</keycap> to save the file to the default filename or "
+"rename the file keeping the <filename>.ced</filename> extension. It can be "
+"useful to name it something generic such as <filename>docbook.ced</filename> "
+"so you can refer to it when opening all DocBook files. This file can also be "
+"copied from directory to directory to be loaded."
+msgstr ""
+
+#: en_US/emacs.xml:304(para)
+msgid "To create a loadable Parsed DTD file: <placeholder-1/>"
+msgstr ""
+
+#: en_US/emacs.xml:349(para)
+msgid ""
+"You can also use the Emacs command <command>Meta-x sgml-parse-prolog</"
+"command> to parse the file, and then use the command <command>Meta-x sgml-"
+"save-dtd</command> to save the parsed DTD to a <filename>.ced</filename> "
+"file."
+msgstr ""
+
+#: en_US/emacs.xml:360(title)
+msgid "Load the Parsed DTD"
+msgstr ""
+
+#: en_US/emacs.xml:362(para)
+msgid ""
+"Now that you have saved the DTD settings, you can load the <filename>.ced</"
+"filename> file and see the syntax highlighting for your <filename>.sgml</"
+"filename> files."
+msgstr ""
+
+#: en_US/emacs.xml:372(para)
+msgid "Open an XML file in Emacs."
+msgstr ""
+
+#: en_US/emacs.xml:377(para)
+msgid ""
+"Choose <command>DTD -> Load DTD</command> from the pulldown menu and "
+"choose the file you saved from the previous step. For instance, choose "
+"<filename>docbook.ced</filename>."
+msgstr ""
+
+#: en_US/emacs.xml:384(para)
+msgid ""
+"You will know it is finished when you see the message "
+"<computeroutput>Fontifying...done</computeroutput> at the bottom of your "
+"screen. Loading the parsed DTD might take a long time. You can start editing "
+"the file before it finishes."
+msgstr ""
+
+#: en_US/emacs.xml:368(para)
+msgid "To load a parsed DTD file: <placeholder-1/>"
+a3759 10
+msgid ""
+"You can also use the Emacs command <command>Meta-x sgml-load-dtd</command> "
+"to load the parsed DTD."
+msgstr ""
+
+#: en_US/emacs.xml:406(title)
+msgid "Basic Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:408(para)
+d3763 1
+a3763 1
+#: en_US/emacs.xml:413(title)
+d3767 1
+a3767 1
+#: en_US/emacs.xml:414(segtitle)
+d3771 7
+a3777 4
+#: en_US/emacs.xml:418(keycap) en_US/emacs.xml:423(keycap)
+#: en_US/emacs.xml:428(keycap) en_US/emacs.xml:496(keycap)
+#: en_US/emacs.xml:501(keycap) en_US/emacs.xml:506(keycap)
+#: en_US/emacs.xml:530(keycap)
+d3781 3
+a3783 4
+#: en_US/emacs.xml:418(keycap) en_US/emacs.xml:423(keycap)
+#: en_US/emacs.xml:428(keycap) en_US/emacs.xml:501(keycap)
+#: en_US/emacs.xml:506(keycap) en_US/emacs.xml:511(keycap)
+#: en_US/emacs.xml:517(keycap) en_US/emacs.xml:523(keycap)
+d3787 2
+a3788 3
+#: en_US/emacs.xml:419(keycap) en_US/emacs.xml:424(keycap)
+#: en_US/emacs.xml:429(keycap) en_US/emacs.xml:502(keycap)
+#: en_US/emacs.xml:507(keycap)
+d3792 1
+a3792 1
+#: en_US/emacs.xml:417(seg)
+d3798 1
+a3798 1
+#: en_US/emacs.xml:420(seg)
+d3802 11
+a3812 31
+#: en_US/emacs.xml:423(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-save-dtd, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:425(seg)
+msgid "Save the Parse DTD"
+msgstr ""
+
+#: en_US/emacs.xml:428(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-load-dtd, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:430(seg)
+msgid "Load DTD"
+msgstr ""
+
+#: en_US/emacs.xml:433(keycap) en_US/emacs.xml:439(keycap)
+#: en_US/emacs.xml:446(keycap) en_US/emacs.xml:451(keycap)
+#: en_US/emacs.xml:456(keycap) en_US/emacs.xml:461(keycap)
+#: en_US/emacs.xml:466(keycap) en_US/emacs.xml:471(keycap)
+#: en_US/emacs.xml:476(keycap) en_US/emacs.xml:481(keycap)
+#: en_US/emacs.xml:486(keycap) en_US/emacs.xml:491(keycap)
+#: en_US/emacs.xml:511(keycap) en_US/emacs.xml:512(keycap)
+#: en_US/emacs.xml:517(keycap) en_US/emacs.xml:518(keycap)
+#: en_US/emacs.xml:523(keycap) en_US/emacs.xml:524(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:536(keycap)
+#: en_US/emacs.xml:543(keycap) en_US/emacs.xml:545(keycap)
+d3816 4
+a3819 4
+#: en_US/emacs.xml:433(keycap) en_US/emacs.xml:439(keycap)
+#: en_US/emacs.xml:451(keycap) en_US/emacs.xml:524(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:543(keycap)
+#: en_US/emacs.xml:545(keycap)
+d3823 1
+a3823 1
+#: en_US/emacs.xml:434(keycap) en_US/emacs.xml:440(keycap)
+d3827 5
+a3831 1
+#: en_US/emacs.xml:435(keycap) en_US/emacs.xml:442(keycap)
+d3835 1
+a3835 1
+#: en_US/emacs.xml:433(seg)
+d3838 1
+a3838 1
+"<keycombo><placeholder-3/><keycap/></keycombo>, <placeholder-4/>"
+d3841 1
+a3841 1
+#: en_US/emacs.xml:436(seg)
+d3845 1
+a3845 1
+#: en_US/emacs.xml:439(seg)
+d3848 2
+a3849 2
+"<keycombo><placeholder-3/><keycap/></keycombo>, type beginning of tag, "
+"<placeholder-4/>"
+d3852 1
+a3852 1
+#: en_US/emacs.xml:443(seg)
+d3856 1
+a3856 1
+#: en_US/emacs.xml:446(keycap)
+d3860 1
+a3860 1
+#: en_US/emacs.xml:448(seg)
+d3864 1
+a3864 1
+#: en_US/emacs.xml:452(keycap)
+d3868 1
+a3868 1
+#: en_US/emacs.xml:451(seg)
+d3872 1
+a3872 1
+#: en_US/emacs.xml:453(seg)
+d3876 1
+a3876 1
+#: en_US/emacs.xml:456(keycap) en_US/emacs.xml:536(keycap)
+d3880 1
+a3880 1
+#: en_US/emacs.xml:458(seg)
+d3884 1
+a3884 1
+#: en_US/emacs.xml:461(keycap)
+d3888 1
+a3888 1
+#: en_US/emacs.xml:463(seg)
+d3892 1
+a3892 1
+#: en_US/emacs.xml:466(keycap)
+d3896 1
+a3896 1
+#: en_US/emacs.xml:468(seg)
+d3900 1
+a3900 1
+#: en_US/emacs.xml:471(keycap)
+d3904 1
+a3904 1
+#: en_US/emacs.xml:473(seg)
+d3908 1
+a3908 1
+#: en_US/emacs.xml:476(keycap)
+d3912 1
+a3912 1
+#: en_US/emacs.xml:478(seg)
+d3916 1
+a3916 1
+#: en_US/emacs.xml:481(keycap)
+d3920 1
+a3920 1
+#: en_US/emacs.xml:483(seg)
+d3924 1
+a3924 1
+#: en_US/emacs.xml:486(keycap) en_US/emacs.xml:518(keycap)
+d3928 1
+a3928 1
+#: en_US/emacs.xml:488(seg)
+d3932 1
+a3932 1
+#: en_US/emacs.xml:491(keycap)
+d3936 1
+a3936 1
+#: en_US/emacs.xml:493(seg)
+d3940 1
+a3940 1
+#: en_US/emacs.xml:496(keycap)
+d3944 1
+a3944 1
+#: en_US/emacs.xml:498(seg) en_US/emacs.xml:503(seg)
+d3948 1
+a3948 1
+#: en_US/emacs.xml:501(seg)
+d3954 1
+a3954 1
+#: en_US/emacs.xml:506(seg)
+d3960 1
+a3960 1
+#: en_US/emacs.xml:508(seg)
+d3964 1
+a3964 1
+#: en_US/emacs.xml:512(keycap)
+d3968 2
+a3969 2
+#: en_US/emacs.xml:511(seg) en_US/emacs.xml:517(seg) en_US/emacs.xml:523(seg)
+#: en_US/emacs.xml:535(seg) en_US/emacs.xml:543(seg)
+d3975 1
+a3975 1
+#: en_US/emacs.xml:514(seg)
+d3979 1
+a3979 1
+#: en_US/emacs.xml:520(seg)
+d3983 1
+a3983 1
+#: en_US/emacs.xml:526(seg)
+d3987 1
+a3987 1
+#: en_US/emacs.xml:530(keycap)
+d3991 1
+a3991 1
+#: en_US/emacs.xml:532(seg)
+d3995 1
+a3995 1
+#: en_US/emacs.xml:539(computeroutput)
+d4000 6
+a4005 1
+#: en_US/emacs.xml:538(seg)
+d4011 1
+a4011 1
+#: en_US/emacs.xml:547(seg)
+d4015 1
+a4015 1
+#: en_US/emacs.xml:554(title) en_US/emacs-nxml.xml:77(title)
+d4019 1
+a4019 1
+#: en_US/emacs.xml:556(para)
+d4025 1
+a4025 1
+#: en_US/emacs.xml:562(title)
+d4029 2
+a4030 4
+#: en_US/emacs.xml:566(para)
+msgid ""
+"This section assumes that you have already loaded the DTD file (<filename>."
+"ced</filename>)."
+d4033 1
+a4033 1
+#: en_US/emacs.xml:571(para)
+d4035 4
+a4038 4
+"Instead of typing a tag each time you need to use it, use the key "
+"combination <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by "
+"<keycap><</keycap>. At the bottom of the <application>Emacs</application> "
+"window, you will see:"
+d4041 1
+a4041 2
+#: en_US/emacs.xml:578(computeroutput)
+#, no-wrap
+d4045 1
+a4045 1
+#: en_US/emacs.xml:581(para)
+d4048 4
+a4051 3
+"<keycap>?</keycap>. Or, if you know the first few letters of a tag, you can "
+"enter them followed by <keycap>Tab</keycap> for a complete list of available "
+"tags beginning with those letters or for a tag completion."
+d4054 1
+a4054 1
+#: en_US/emacs.xml:589(para)
+d4056 3
+a4058 4
+"Try the following: Type <keycap>Ctrl</keycap>-<keycap>c</keycap> followed by "
+"<keycap><</keycap>. Then enter the letter <keycap>k</keycap>, followed by "
+"<keycap>Tab</keycap>. You may have to use the <keycap>Tab</keycap> key "
+"several times to get a complete list."
+d4061 2
+a4062 2
+#: en_US/emacs.xml:596(para)
+msgid "The output should look similar to the example below:"
+d4065 1
+a4065 2
+#: en_US/emacs.xml:601(computeroutput)
+#, no-wrap
+d4067 8
+a4074 7
+"\n"
+"Click mouse-2 on a completion to select it.\n"
+"In this buffer, type RET to select the completion near point.\n"
+"\n"
+"Possible completions are:\n"
+"<keycap> <keycode>\n"
+"<keycombo> <keysym>\n"
+d4077 2
+a4078 2
+#: en_US/emacs.xml:613(title)
+msgid "Tag Closure"
+d4083 4
+a4086 4
+"Once you have started the tag of choice, you must close it. The easiest way "
+"to close an open tag is to use the keycombo <keycap>Ctrl</keycap>-<keycap>c</"
+"keycap>, followed by <keycap>/</keycap>. This will close the closest open "
+"tag you have."
+d4090 1
+a4090 1
+msgid "Other Emacs Tasks"
+d4093 1
+a4093 1
+#: en_US/emacs.xml:627(para)
+d4095 7
+a4101 6
+"<guilabel>Working with one window</guilabel>: Sometimes in "
+"<application>Emacs</application> the window becomes split (with tags "
+"completions or other text in the bottom window). The easiest way to get it "
+"back so that only your XML and text appear on one screen is to use the "
+"keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap>, followed by <keycap>1</"
+"keycap>."
+d4104 1
+a4104 1
+#: en_US/emacs.xml:636(para)
+d4106 4
+a4109 3
+"<guilabel>Saving your work</guilabel>: To save your work, use the following "
+"keycombo, <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</"
+"keycap>-<keycap>s</keycap>."
+d4112 5
+a4116 1
+#: en_US/emacs.xml:642(para)
+d4118 5
+a4122 5
+"<guilabel>The \"clear/quit\" command</guilabel>: I have found on some "
+"occasions that I have gotten too far into the tag completion process and "
+"need to just exit back out to my text. The easiest way to do this is the "
+"keycombo <keycap>Ctrl</keycap>-<keycap>g</keycap>. This command quits what "
+"you have been doing within the file, without quitting the file itself."
+d4125 2
+a4126 7
+#: en_US/emacs.xml:651(para)
+msgid ""
+"<guilabel>Opening a new file</guilabel>: To open a new file, use the "
+"keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</"
+"keycap>-<keycap>f</keycap>. At the bottom of the emacs window, you will be "
+"able to enter in the file name (using <keycap>Tab</keycap> completion if "
+"needed) of the file you wish to open."
+d4129 1
+a4129 1
+#: en_US/emacs.xml:660(para)
+d4131 5
+a4135 6
+"<guilabel>Closing emacs</guilabel>: The easiest way to close "
+"<application>emacs</application> is to use the keycombo <keycap>Ctrl</"
+"keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</keycap>-<keycap>c</"
+"keycap>. If you have not saved your work, it will prompt you to save the "
+"file, otherwise it will just quit the current emacs session you have been "
+"working with."
+d4138 1
+a4138 1
+#: en_US/emacs.xml:673(title) en_US/emacs-nxml.xml:127(title)
+d4142 1
+a4142 1
+#: en_US/emacs.xml:675(para)
+d4148 1
+a4148 5
+#: en_US/emacs.xml:682(ulink) en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr ""
+
+#: en_US/emacs.xml:683(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+d4152 1
+a4152 1
+#: en_US/emacs.xml:686(para) en_US/emacs-nxml.xml:147(para)
+d4156 1
+a4156 1
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+d4159 1
+a4159 1
+#: en_US/emacs.xml:693(para)
+d4162 1
+a4162 2
+"usr/share/doc/psgml-<replaceable><version></replaceable>/psgml.ps</"
+"filename>."
+d4165 1
+a4165 1
+#: en_US/emacs.xml:697(para)
+d4167 3
+a4169 8
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\">http://www."
+"snee.com/bob/sgmlfree/psgmqref.html</ulink>—<citetitle>Emacs/PSGML "
+"Quick Reference</citetitle> is a reference table of Emacs commands for PSGML "
+"mode."
+msgstr ""
+
+#: en_US/emacs.xml:705(ulink)
+msgid "http://www.snee.com/bob/sgmlfree/emcspsgm.html"
+d4172 1
+a4172 1
+#: en_US/emacs.xml:706(citetitle)
+d4291 11
+d4508 3
+a4510 3
+"This document is based on the a document started by Tammy Fox (tfox at "
+"redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and "
+"Johnray Fuller (jrfuller at redhat.com)."
+d4536 1
+a4536 1
+"(stickstr5 at hotmail.com)."
+d4541 1
+a4541 1
+"A patch from Paul W. Frields (stickstr5 at hotmail.com) has been applied to "
+d4557 439
+@
+
+
+1.11
+log
+ at some translatio
+@
+text
+ at d8 1
+a8 1
+"PO-Revision-Date: 2007-05-28 17:32-0300\n"
+d404 1
+a404 1
+"<!--$Id: pt_BR.po,v 1.10 2007/05/15 21:00:17 nullck Exp $ -->\n"
+d415 1
+a415 1
+"<!--$Id: pt_BR.po,v 1.10 2007/05/15 21:00:17 nullck Exp $ -->\n"
+d607 1
+a607 1
+msgstr ""
+d611 1
+a611 1
+msgstr ""
+d619 2
+d625 1
+a625 1
+msgstr ""
+d629 1
+a629 1
+msgstr ""
+d636 2
+@
+
+
+1.10
+log
+ at some translation
+@
+text
+ at d8 1
+a8 1
+"PO-Revision-Date: 2007-05-15 17:54-0300\n"
+d404 1
+a404 1
+"<!--$Id: pt_BR.po,v 1.9 2007/05/08 22:42:16 nullck Exp $ -->\n"
+d415 1
+a415 1
+"<!--$Id: pt_BR.po,v 1.9 2007/05/08 22:42:16 nullck Exp $ -->\n"
+d570 1
+a570 1
+msgstr ""
+d589 1
+a589 1
+msgstr ""
+d595 1
+a595 1
+msgstr ""
+d599 1
+a599 1
+msgstr ""
+d603 1
+a603 1
+msgstr ""
+@
+
+
+1.9
+log
+ at some translation - entrance 72
+@
+text
+ at d8 1
+a8 1
+"PO-Revision-Date: 2007-05-08 19:40-0300\n"
+d404 1
+a404 1
+"<!--$Id: pt_BR.po,v 1.8 2007/05/03 21:11:52 nullck Exp $ -->\n"
+d415 1
+a415 1
+"<!--$Id: pt_BR.po,v 1.8 2007/05/03 21:11:52 nullck Exp $ -->\n"
+d499 1
+a499 1
+"\">command</sgmltag> and <sgmltag class=\"endtag\">command</sgmltag> tags como:"
+d553 6
+d562 1
+a562 1
+msgstr ""
+@
+
+
+1.8
+log
+ at some translation - entrance 59
+@
+text
+ at d8 1
+a8 1
+"PO-Revision-Date: 2007-05-03 14:57-0300\n"
+d404 1
+a404 1
+"<!--$Id: pt_BR.po,v 1.7 2007/05/02 21:18:16 nullck Exp $ -->\n"
+d415 1
+a415 1
+"<!--$Id: pt_BR.po,v 1.7 2007/05/02 21:18:16 nullck Exp $ -->\n"
+d452 2
+d457 1
+a457 1
+msgstr ""
+d461 1
+a461 1
+msgstr ""
+d469 2
+d476 1
+a476 1
+msgstr ""
+d480 1
+a480 1
+msgstr ""
+d489 2
+d498 2
+d509 4
+d527 1
+a527 1
+msgstr ""
+d535 3
+d541 1
+a541 1
+msgstr ""
+d648 1
+a648 1
+msgstr ""
+d700 1
+a700 1
+msgstr ""
+@
+
+
+1.7
+log
+ at some translation - entrance 52
+@
+text
+ at d8 1
+a8 1
+"PO-Revision-Date: 2007-05-02 18:13-0300\n"
+a157 1
+
+d404 1
+a404 1
+"<!--$Id: pt_BR.po,v 1.6 2007/04/30 21:19:07 nullck Exp $ -->\n"
+d414 9
+d430 3
+d437 1
+a437 1
+msgstr ""
+d444 1
+a444 1
+msgstr ""
+@
+
+
+1.6
+log
+ at some translation - to revise in HTML - entrance 50
+@
+text
+ at d8 1
+a8 1
+"PO-Revision-Date: 2007-04-30 18:14-0300\n"
+d67 1
+a67 1
+msgstr "Instruções e procedimentos para produção de documentação para o Fedora"
+d75 1
+a75 1
+msgstr "Tags DocBook XML "
+d149 1
+a149 1
+"informação relevante à requisição de procura. Um outro benefício é que todos "
+d151 1
+a151 1
+"terão algumas diferenças dependendo do formato da saída)."
+d158 1
+a158 1
+#, fuzzy
+d227 3
+a229 3
+"Não use entidades de marca registrada<sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, ou <sgmltag class="
+"\"genentity\">reg</sgmltag> porque não produzem a saida em HTML que funcione "
+d263 1
+a263 1
+"<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag>simbolo "
+d328 1
+a328 1
+"Índice de tags<sgmltag> dentro das tags </sgmltag>listitem </sgmltag> tags <emphasis>must</emphasis>começar imediatamente depois da tag<sgmltag class=\"starttag\">para</sgmltag>"
+d333 1
+a333 1
+msgstr "Índice dentro dos Tag de <sgmltag>screen</sgmltag>"
+d364 1
+a364 1
+"A <sgmltag class=\"starttag\">application</sgmltag> and <sgmltag class="
+d384 1
+a384 1
+msgstr ""
+d390 1
+a390 1
+msgstr ""
+d395 1
+a395 1
+msgstr ""
+d399 1
+a399 1
+msgstr ""
+d405 1
+a405 1
+"<!--$Id: xml-tags.xml,v 1.5 2007/02/04 14:55:28 pfrields Exp $ -->\n"
+@
+
+
+1.5
+log
+ at some revisions
+@
+text
+ at d1 1
+a1 1
+# translation of pt_BR.po to Brazilian Portuguese
+a3 1
+# translation of pt_BR.po to
+d7 4
+a10 4
+"POT-Creation-Date: 2007-04-26 14:37-0300\n"
+"PO-Revision-Date: 2007-04-26 15:10-0300\n"
+"Last-Translator: Diego Búrigo Zacarão <diegobz@@projetofedora.org>\n"
+"Language-Team: Brazilian Portuguese <fedora-trans-pt_BR@@redhat.com>\n"
+d15 1
+a15 1
+"X-Generator: KBabel 1.11.4\n"
+d136 2
+a137 1
+"usadas pelo Projeto Docs. Algumas das regras descritas são específicas para o projeto."
+d149 2
+a150 2
+"informação relevante à requisição de procura. Um outro benefício é que todos os "
+"documentos do Projeto Fedora possuirão um visual similar (entretanto, "
+d189 2
+a190 1
+"completa, visite <ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+d229 3
+a231 4
+"\"genentity\">reg</sgmltag> porque não produzem a saida em HTML que "
+"funcione com todos os charsets. A saída em HTML produzida por estas "
+"entidades é declarada no DTD e não pode ser mudada através da planilha de "
+"estilo."
+d254 3
+a256 1
+msgstr "<sgmltag class=\"starttag\">trademark class=\"registered\"</sgmltag>simbolo de trademark registrada<sgmltag class=\"endtag\">trademark</sgmltag>"
+d263 2
+a264 2
+"<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag>simbolo de copyright "
+"<sgmltag class=\"endtag\">trademark</sgmltag>"
+d275 1
+a275 1
+msgstr ""
+d282 1
+a282 1
+msgstr ""
+d288 1
+a288 1
+msgstr ""
+d294 1
+a294 1
+msgstr ""
+d300 1
+a300 1
+msgstr ""
+d306 1
+a306 1
+msgstr ""
+d313 1
+a313 1
+msgstr ""
+d319 1
+a319 1
+msgstr ""
+d328 2
+d333 1
+a333 1
+msgstr ""
+d342 3
+d350 1
+a350 1
+msgstr ""
+d356 1
+a356 1
+msgstr ""
+d364 2
+d376 5
+d439 1
+a439 1
+"your document set, given as an entity<placeholder-1/> )."
+d778 3
+a780 2
+"For those of you who need to perform a server-class <placeholder-1/> "
+"installation, refer to the <citetitle>Installation Guide</citetitle>."
+d2968 5
+a2972 5
+"<citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long "
+"streams of words without punctuation to simulate a character's internal "
+"consciousness. By violating basic rules of grammar and syntax, Joyce "
+"simulates the disorganized but loosely connected thought patterns of the "
+"narrator."
+d4679 1
+a4679 1
+"<placeholder-1/>"
+d5286 2
+a5287 1
+"XML source for document-specific <placeholder-2/><placeholder-3/>."
+@
+
+
+1.4
+log
+ at some translations
+@
+text
+ at d1 1
+a1 1
+# translation of pt_BR.po to
+d4 1
+d8 4
+a11 4
+"POT-Creation-Date: 2007-04-20 17:17-0300\n"
+"PO-Revision-Date: 2007-04-26 14:48-0300\n"
+"Last-Translator: Nullck <nullck@@localhost.localdomain>\n"
+"Language-Team: <en@@li.org>\n"
+d16 1
+a16 1
+"X-Generator: KBabel 1.11.1\n"
+d68 1
+a68 1
+msgstr "Instruções e procedimentos para desenvolver a documentação do Fedora"
+d76 1
+a76 1
+msgstr "DocBook XML Tags"
+d129 1
+a129 1
+msgstr "XML tags"
+d135 3
+a137 1
+msgstr "Leia por favor este capítulo com cuidado. Este capítulo descreve os Tag usados pelo projeto dos Docs. Algumas das regras descritas são específicas ao projeto."
+d146 6
+a151 1
+msgstr "Se estas tags forem usadas apropriadamente, as buscas fornecerão resultados significativos. Estas formas de busca com auxilio das tags identificam a informação relevante ao pedido da procura. Um outro benefício é que todos os documentos do projeto de Fedora possuirão um visual similar (entretanto, terão algumas diferenças dependendo em cima do formato da saída)."
+d158 1
+d165 7
+a171 1
+msgstr "A maioria das tag's em XML devem ter uma tag abertura e uma tag de fechamento. Algumas tag's, tais como <sgmltag class=\"emptytag\">xref</sgmltag>, não têm nenhum índice e depois são fechadas. Adicionalmente, as convenções apropriadas de XML dizem que deve haver um identificador original para seções, capítulos, figuras, tabelas, e assim por diante, de modo que possam corretamente ser identificadas, e se necessário é feito remissão recíproca ."
+d177 3
+a179 1
+msgstr "Embora originalmente XML seja capaz de manipular varios tipos de formato , o formato discutido aqui é o formato de artigo."
+d187 3
+a189 2
+"Este capítulo discute somente as tag usadas para a documentação do projeto Fedora e não todas as tags disponíveis do DocBook XML. Para a lista completa, consultar o "
+"<ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+d209 4
+a212 1
+msgstr "É muito importante que você recorde os caveats nesta seção. Mesmo que sejam mais simplificados do que o XML DocBook válido , estas régras existem de modo que as saídas do HTML e do pdf sejam visualizadas apropriadamente."
+d216 1
+a216 1
+msgstr "Não use entidades da marca registrada"
+d226 6
+a231 3
+"Não use entidades de marca registrada<sgmltag class=\"genentity\">comercial</"
+"sgmltag>, <sgmltag class=\"genentity\">copiada</sgmltag>, ou <sgmltag class="
+"\"genentity\">registrada</sgmltag> porque não produzem a saida em HTML que trabalha com todos os charsets. A saída em HTML produzida por estas entidades é declarada no DTD e não pode ser mudada através da planilha de estilo."
+d237 3
+a239 1
+msgstr "Preferêncialmente , use a tag <sgmltag class=\"element\">trademark</sgmltag>e suas classes associadas como segue:"
+d245 3
+a247 1
+msgstr "<sgmltag class=\"starttag\">trademark</sgmltag> é simbolo da trademark <sgmltag class=\"endtag\">trademark </sgmltag>"
+d254 1
+a254 4
+msgstr ""
+"<sgmltag class=\"starttag\">trademark class=\"registered\"</"
+"sgmltag>simbolo registrado da trademark<sgmltag class=\"endtag"
+"\">trademark</sgmltag>"
+d261 2
+d266 1
+a266 1
+msgstr ""
+d391 1
+a391 1
+"<!--$Id: pt_BR.po,v 1.3 2007/04/25 20:36:25 nullck Exp $ -->\n"
+@
+
+
+1.3
+log
+ at some translation - entrance 25
+@
+text
+ at d8 1
+a8 1
+"PO-Revision-Date: 2007-04-25 17:16-0300\n"
+d67 1
+a67 1
+msgstr "Instruções e procedimentos para produzir a documentação do Fedora"
+d184 1
+a184 1
+msgstr ""
+d191 1
+a191 1
+msgstr ""
+d195 1
+a195 1
+msgstr ""
+d205 3
+d213 1
+a213 1
+msgstr ""
+d219 1
+a219 1
+msgstr ""
+d227 3
+d364 1
+a364 1
+"<!--$Id: pt_BR.po,v 1.2 2007/04/20 20:24:22 diegobz Exp $ -->\n"
+@
+
+
+1.2
+log
+ at some translation
+@
+text
+ at d1 1
+a1 1
+# translation of pt_BR.po to Brazilian Portuguese
+d3 1
+d8 3
+a10 3
+"PO-Revision-Date: 2007-04-20 17:23-0300\n"
+"Last-Translator: Diego Búrigo Zacarão <diegobz@@projetofedora.org>\n"
+"Language-Team: Brazilian Portuguese <fedora-trans-pt_BR@@redhat.com>\n"
+d15 1
+a15 1
+"X-Generator: KBabel 1.11.4\n"
+d67 1
+a67 1
+msgstr ""
+d71 1
+a71 1
+msgstr ""
+d75 1
+a75 1
+msgstr ""
+d83 1
+a83 1
+msgstr ""
+d128 1
+a128 1
+msgstr ""
+d134 1
+a134 1
+msgstr ""
+d143 1
+a143 1
+msgstr ""
+d147 1
+a147 1
+msgstr ""
+d156 1
+a156 1
+msgstr ""
+d162 1
+a162 1
+msgstr ""
+d170 2
+d175 1
+a175 1
+msgstr ""
+d179 1
+a179 1
+msgstr ""
+d358 1
+a358 1
+"<!--$Id: pt_BR.po,v 1.1 2007/04/20 20:22:54 diegobz Exp $ -->\n"
+@
+
+
+1.1
+log
+ at Added pt_BR.po
+@
+text
+ at d1 2
+d5 1
+a5 1
+"Project-Id-Version: PACKAGE VERSION\n"
+d7 3
+a9 3
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@@li.org>\n"
+d14 1
+d50 1
+a50 1
+msgstr ""
+d54 1
+a54 1
+msgstr ""
+d78 1
+a78 1
+msgstr ""
+d355 1
+a355 1
+"<!--$Id: xml-tags.xml,v 1.5 2007/02/04 14:55:28 pfrields Exp $ -->\n"
+d743 1
+a743 2
+msgid ""
+"Order matters! The EPS file <emphasis>must</emphasis> be declared first."
+d2151 1
+a2151 2
+msgid ""
+"<placeholder-1/> says that you are giving information about the column to XML"
+d2169 1
+a2169 2
+msgid ""
+"<placeholder-1/> says that the title for this column will be \"Features.\""
+d3229 1
+a3229 2
+msgid ""
+"There is a text box that you can use to find out the definition of a word."
+d3428 1
+a3428 2
+msgid ""
+"The term does not appear in the glossary of the manual that you are writing."
+d3432 1
+a3432 2
+msgid ""
+"The term is not defined in the body text of the manual that you are writing."
+d3686 1
+a3686 2
+msgid ""
+"the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+d4104 1
+a4104 2
+msgid ""
+"Numbers from zero through nine unless the number is part of a measurement"
+d4640 1
+a4640 2
+msgid ""
+"Follow the capitalization rules for headings in the title of an admonition."
+d5139 1
+a5139 2
+msgid ""
+"To find all the currently active ssh sessions, execute the following command:"
+d5671 1
+a5671 2
+msgid ""
+"To add a new DocBook XML file to an existing document, follow these steps:"
+d5854 1
+a5854 2
+msgid ""
+"To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+d6164 1
+a6164 2
+msgid ""
+"and restart <application>Emacs</application> for the changes to take place."
+d7077 1
+@
+
diff --git a/old-documentation-guide/po/zh_CN.po,v b/old-documentation-guide/po/zh_CN.po,v
new file mode 100644
index 0000000..99d9777
--- /dev/null
+++ b/old-documentation-guide/po/zh_CN.po,v
@@ -0,0 +1,11106 @@
+head 1.7;
+access;
+symbols
+ documentation-guide-0_3_2_1:1.5
+ LIVE:1.1;
+locks; strict;
+comment @# @;
+
+
+1.7
+date 2008.05.12.06.13.11; author mdious; state Exp;
+branches;
+next 1.6;
+
+1.6
+date 2007.12.15.21.52.11; author pfrields; state Exp;
+branches;
+next 1.5;
+
+1.5
+date 2007.11.15.02.12.48; author pfrields; state Exp;
+branches;
+next 1.4;
+
+1.4
+date 2007.08.03.16.42.44; author pfrields; state Exp;
+branches;
+next 1.3;
+
+1.3
+date 2007.08.03.16.39.22; author pfrields; state Exp;
+branches;
+next 1.2;
+
+1.2
+date 2007.07.29.23.25.11; author pfrields; state Exp;
+branches;
+next 1.1;
+
+1.1
+date 2007.03.11.21.33.24; author pfrields; state Exp;
+branches;
+next ;
+
+
+desc
+@@
+
+
+1.7
+log
+ at updating pot and po files for noriko
+@
+text
+@#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2008-05-13 02:06+1000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"#-#-#-#-# acknowledgments.po (PACKAGE VERSION) #-#-#-#-#\n"
+"#-#-#-#-# documentation-guide.po (PACKAGE VERSION) #-#-#-#-#\n"
+"#-#-#-#-# emacs-nxml.po (PACKAGE VERSION) #-#-#-#-#\n"
+"#-#-#-#-# emacs.po (PACKAGE VERSION) #-#-#-#-#\n"
+"#-#-#-#-# getting-files.po (PACKAGE VERSION) #-#-#-#-#\n"
+"#-#-#-#-# intro.po (PACKAGE VERSION) #-#-#-#-#\n"
+"#-#-#-#-# style.po (PACKAGE VERSION) #-#-#-#-#\n"
+"#-#-#-#-# tutorial.po (PACKAGE VERSION) #-#-#-#-#\n"
+"#-#-#-#-# vim.po (PACKAGE VERSION) #-#-#-#-#\n"
+"#-#-#-#-# xml-tags.po (PACKAGE VERSION) #-#-#-#-#\n"
+
+#: en_US/rpm-info.xml:22(rights)
+msgid "OPL"
+msgstr ""
+
+#: en_US/rpm-info.xml:23(version)
+msgid "1.0"
+msgstr ""
+
+#: en_US/rpm-info.xml:26(year)
+msgid "2003"
+msgstr ""
+
+#: en_US/rpm-info.xml:27(year)
+msgid "2004"
+msgstr ""
+
+#: en_US/rpm-info.xml:28(year)
+msgid "2005"
+msgstr ""
+
+#: en_US/rpm-info.xml:29(year)
+msgid "2006"
+msgstr ""
+
+#: en_US/rpm-info.xml:30(year)
+msgid "2007"
+msgstr ""
+
+#: en_US/rpm-info.xml:31(year)
+msgid "2008"
+msgstr ""
+
+#: en_US/rpm-info.xml:32(holder)
+msgid "Red Hat, Inc. and others"
+msgstr ""
+
+#: en_US/rpm-info.xml:34(title)
+msgid "Fedora Documentation Guide"
+msgstr ""
+
+#: en_US/rpm-info.xml:35(desc)
+msgid "Guidelines and procedures for producing documentation for Fedora"
+msgstr ""
+
+#: en_US/rpm-info.xml:39(details)
+msgid "Add L10n chapter (#441190)"
+msgstr ""
+
+#: en_US/rpm-info.xml:43(details)
+msgid "Fix some organization and missing targets (#371531)"
+msgstr ""
+
+#: en_US/rpm-info.xml:47(details)
+msgid "Add link to DocBook XML help for Windows"
+msgstr ""
+
+#: en_US/rpm-info.xml:51(details)
+msgid "Add guidance on CVS web access and previewing work"
+msgstr ""
+
+#: en_US/rpm-info.xml:55(details)
+msgid "Add new chapter on publishing"
+msgstr ""
+
+#: en_US/rpm-info.xml:59(details)
+msgid "Include information on LINGUAS usage"
+msgstr ""
+
+#: en_US/rpm-info.xml:63(details)
+msgid "Remove unnecessary chapter on XML tags"
+msgstr ""
+
+#: en_US/rpm-info.xml:67(details)
+msgid "Assorted fixes to reflect newer version of reality"
+msgstr ""
+
+#: en_US/rpm-info.xml:74(details)
+msgid "Update to new content and build requirements"
+msgstr ""
+
+#: en_US/l10n.xml:13(title)
+msgid "Localization (L10n)"
+msgstr ""
+
+#: en_US/l10n.xml:14(para)
+msgid ""
+"This chapter discusses how translations are provided in Fedora documentation."
+msgstr ""
+
+#: en_US/l10n.xml:19(title)
+msgid "PO Files"
+msgstr ""
+
+#: en_US/l10n.xml:20(para)
+msgid ""
+"The cornerstone of translation when using XML files such as DocBook is the "
+"<firstterm>Portable Object</firstterm> or <acronym>PO</acronym> file. PO "
+"files provide a way for independent individuals or teams to translate "
+"documents. The Fedora Documentation Project toolchain includes rules for "
+"creating, updating, and maintaining these PO files."
+msgstr ""
+
+#: en_US/l10n.xml:28(para)
+msgid "PO files are usually found in two forms:"
+msgstr ""
+
+#: en_US/l10n.xml:33(para)
+msgid ""
+"the <filename class=\"extension\">.pot</filename> file, or <firstterm>PO "
+"Template</firstterm> (<acronym>POT</acronym>)"
+msgstr ""
+
+#: en_US/l10n.xml:41(para)
+msgid ""
+"the <filename class=\"extension\">.po</filename> file, or translation file "
+"(<acronym>PO</acronym>)"
+msgstr ""
+
+#: en_US/l10n.xml:47(para)
+msgid ""
+"A POT is, as the name suggests, a blank template for new translations. It "
+"contains some header information and a list of strings based on the content "
+"of the original XML file from which it was created. Translators do not alter "
+"the POT. The POT should only be changed after changes are made to the "
+"original XML file from which it is derived."
+msgstr ""
+
+#: en_US/l10n.xml:55(para)
+msgid ""
+"A translator who wishes to start working on a new language copies the POT to "
+"a locale-specific PO file. Then the translator uses any of a number of "
+"command-line or graphical tools to translate each of the strings in the "
+"list. A single POT is used to create many POs, one for each locale. These "
+"files are normally named for their locale code, such as <filename>de.po</"
+"filename>, <filename>it.po</filename>, and so on."
+msgstr ""
+
+#: en_US/l10n.xml:67(title)
+msgid "Creating or Updating a POT"
+msgstr ""
+
+#: en_US/l10n.xml:68(para)
+msgid ""
+"The POT is named after the document from which it is derived. If document "
+"named in the <filename>Makefile</filename>) is <filename>foo-tutorial.xml</"
+"filename>, the POT is named <filename>foo-tutorial.pot</filename>."
+msgstr ""
+
+#: en_US/l10n.xml:74(para)
+msgid "To create a new POT, use the following command:"
+msgstr ""
+
+#: en_US/l10n.xml:78(para)
+msgid ""
+"The same command is used to update the POT when the original XML sources "
+"change."
+msgstr ""
+
+#: en_US/l10n.xml:83(title)
+msgid "Keep POT Fresh"
+msgstr ""
+
+#: en_US/l10n.xml:84(para)
+msgid ""
+"Update the POT whenever the original XML changes. Many translators' tools "
+"automatically notify them of the change so they can update translations "
+"quickly."
+msgstr ""
+
+#: en_US/l10n.xml:92(title)
+msgid "Updating PO Files"
+msgstr ""
+
+#: en_US/l10n.xml:93(para)
+msgid ""
+"The translation files are created by the individual translators, and "
+"document maintainers do not normally need to create them. Translators update "
+"a list of locales in the <filename>po/LINGUAS</filename> file which defines "
+"all the locales for which translations exist."
+msgstr ""
+
+#: en_US/l10n.xml:100(para)
+msgid ""
+"Whenever the source XML files are updated, the maintainer must at least "
+"update the POT. It is helpful, however, to also merge these changes with the "
+"existing translations for those translators who are not automatically "
+"notified of changes."
+msgstr ""
+
+#: en_US/l10n.xml:107(title)
+msgid "Staying Current"
+msgstr ""
+
+#: en_US/l10n.xml:108(para)
+msgid ""
+"Always make sure your local copy of PO is fresh, using the CVS \"update\" "
+"command:"
+msgstr ""
+
+#: en_US/l10n.xml:114(para)
+msgid ""
+"To merge new changes into the existing PO translations, use the following "
+"command:"
+msgstr ""
+
+#: en_US/l10n.xml:121(title)
+msgid "Checking Statistics"
+msgstr ""
+
+#: en_US/l10n.xml:122(para)
+msgid "PO strings fall into three categories:"
+msgstr ""
+
+#: en_US/l10n.xml:127(para)
+msgid ""
+"<firstterm>translated</firstterm>, meaning the string has been handled by a "
+"translator and its source has not changed since then"
+msgstr ""
+
+#: en_US/l10n.xml:134(para)
+msgid ""
+"<firstterm>fuzzy</firstterm>, meaning the string has changed since it was "
+"last handled by a translator"
+msgstr ""
+
+#: en_US/l10n.xml:140(para)
+msgid ""
+"<firstterm>untranslated</firstterm>, meaning no translation has yet been "
+"provided for this string, or it is brand new"
+msgstr ""
+
+#: en_US/l10n.xml:146(para)
+msgid ""
+"To see a rough statistical tally of the string handling inside the PO for a "
+"module, use the following command:"
+msgstr ""
+
+#: en_US/l10n.xml:151(para)
+msgid ""
+"For each locale in the list, a count is shown of translated, fuzzy, and "
+"untranslated strings in that order. Tallies that only provide two numerals "
+"are usually translated followed by untranslated. Tallies with only one "
+"numeral are usually fully translated."
+msgstr ""
+
+#: en_US/l10n.xml:158(para)
+msgid ""
+"To see only a specific locale, append a dash and the locale code to the "
+"<command>postat</command> target:"
+msgstr ""
+
+#: en_US/publishing.xml:11(title)
+msgid "Publishing Official Documentation"
+msgstr ""
+
+#: en_US/publishing.xml:12(para)
+msgid ""
+"This chapter shows how to publish official Fedora Documentation Project work "
+"to the <systemitem class=\"fqdomainname\">docs.fedoraproject.org</"
+"systemitem> website. To publish official documentation, you must be approved "
+"to write to the web repository in CVS. Access for publishing is limited to "
+"contributors who have demonstrated capacity for working with CVS and other "
+"project tools. Once you have acquired and are comfortable with these skills, "
+"contributions as a publisher are welcome."
+msgstr ""
+
+#: en_US/publishing.xml:21(title)
+msgid "How the Site Works"
+msgstr ""
+
+#: en_US/publishing.xml:22(para)
+msgid ""
+"The <systemitem class=\"fqdomainname\">docs.fedoraproject.org</systemitem> "
+"website is a set of PHP files and scripts. Publishers maintain these files "
+"in a CVS repository, and the website host retrieves them hourly to refresh "
+"the site. The host does not automatically use the newest content for the "
+"website. Instead, it pulls files with the CVS tag <systemitem>LIVE</"
+"systemitem> to populate the website."
+msgstr ""
+
+#: en_US/publishing.xml:30(para)
+msgid ""
+"Each publisher sets up a local testing website on an available Fedora "
+"system. This site, sometimes called a <firstterm>sandbox</firstterm>, allows "
+"the publisher to test and view changes to documents, and ensure stability on "
+"the public site."
+msgstr ""
+
+#: en_US/publishing.xml:37(title)
+msgid "Setting Up a Web Sandbox"
+msgstr ""
+
+#: en_US/publishing.xml:38(para)
+msgid ""
+"To test document publishing, first set up a web sandbox on a local Fedora "
+"system."
+msgstr ""
+
+#: en_US/publishing.xml:42(para)
+msgid "Install the \"Web Server\" package group:"
+msgstr ""
+
+#: en_US/publishing.xml:43(screen)
+#, fuzzy, no-wrap
+msgid "su -c 'yum groupinstall \"Web Server\"'"
+msgstr "配置文件"
+
+#: en_US/publishing.xml:46(para)
+msgid "Create a folder for the web server to access the site files."
+msgstr ""
+
+#: en_US/publishing.xml:48(screen)
+#, no-wrap
+msgid "su -c 'mkdir /var/www/fedora'"
+msgstr ""
+
+#: en_US/publishing.xml:51(para)
+msgid ""
+"Change the permissions on this directory to make it easier to access for "
+"your normal user account."
+msgstr ""
+
+#: en_US/publishing.xml:53(replaceable) en_US/publishing.xml:62(replaceable)
+msgid "username"
+msgstr ""
+
+#: en_US/publishing.xml:53(screen)
+#, no-wrap
+msgid "su -c 'chown <placeholder-1/> /var/www/fedora'"
+msgstr ""
+
+#: en_US/publishing.xml:56(para)
+msgid "Link to the new directory from your home directory."
+msgstr ""
+
+#: en_US/publishing.xml:57(screen)
+#, no-wrap
+msgid "ln -s /var/www/fedora ~/fedora"
+msgstr ""
+
+#: en_US/publishing.xml:60(para)
+msgid "Retrieve the web module from CVS."
+msgstr ""
+
+#: en_US/publishing.xml:61(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora\n"
+"cvs -d :ext:<placeholder-1/>@@cvs.fedoraproject.org:/cvs/fedora co web"
+msgstr ""
+
+#: en_US/publishing.xml:64(title)
+msgid "Web CVS Access"
+msgstr ""
+
+#: en_US/publishing.xml:65(para)
+msgid ""
+"You must have access to the <systemitem>cvsweb</systemitem> module through "
+"the Fedora Account System to check in changes. If you do not have access, "
+"you can use <userinput><![CDATA[:pserver:anonymous]]></userinput> in place "
+"of <userinput><![CDATA[:ext:username]]></userinput> above. Visit the Fedora "
+"Account System at <ulink url=\"http://admin.fedoraproject.org/accounts/\"/> "
+"for more information."
+msgstr ""
+
+#: en_US/publishing.xml:77(para)
+msgid ""
+"Edit the <filename>/etc/hosts</filename> file and add the following line "
+"<emphasis>after</emphasis> all other lines:"
+msgstr ""
+
+#: en_US/publishing.xml:80(screen)
+#, no-wrap
+msgid "127.0.0.1 docs.localhost.localdomain"
+msgstr ""
+
+#: en_US/publishing.xml:83(para)
+msgid ""
+"Create a file <filename>/etc/httpd/conf.d/fpo.conf</filename> with the "
+"following content:"
+msgstr ""
+
+#: en_US/publishing.xml:97(para)
+msgid ""
+"Create a file <filename>/etc/php.d/fpo.ini</filename> with the following "
+"content:"
+msgstr ""
+
+#: en_US/publishing.xml:99(screen)
+#, no-wrap
+msgid "include_path = \".:/var/www/fedora/web/include\""
+msgstr ""
+
+#: en_US/publishing.xml:102(para)
+msgid "Start the web server using the following command:"
+msgstr ""
+
+#: en_US/publishing.xml:103(screen)
+#, no-wrap
+msgid "su -c '/sbin/service httpd start'"
+msgstr ""
+
+#: en_US/publishing.xml:104(para)
+msgid "To have the web server start at every boot, use the following command:"
+msgstr ""
+
+#: en_US/publishing.xml:106(screen)
+#, no-wrap
+msgid "su -c '/sbin/chkconfig httpd on'"
+msgstr ""
+
+#: en_US/publishing.xml:109(para)
+msgid ""
+"To test the new sandbox site, open a Web browser and point it at the URL "
+"<uri>http://docs.localhost.localdomain</uri>."
+msgstr ""
+
+#: en_US/publishing.xml:113(title)
+msgid "Creating a New Publication"
+msgstr ""
+
+#: en_US/publishing.xml:115(title)
+msgid "General Guidelines"
+msgstr ""
+
+#: en_US/publishing.xml:116(para)
+msgid ""
+"Follow these guidelines to ensure maintainability and ease of use for all "
+"publishers."
+msgstr ""
+
+#: en_US/publishing.xml:120(para)
+msgid ""
+"Use a short, descriptive name for the document directory. The module name "
+"from its Docs CVS location is usually appropriate. Good examples include "
+"<filename class=\"directory\">install-guide/</filename> or <filename class="
+"\"directory\">example-tutorial/</filename>."
+msgstr ""
+
+#: en_US/publishing.xml:127(para)
+msgid ""
+"Under the document directory, include a branch directory if the document "
+"references specific features of a particular Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:132(para)
+msgid ""
+"Under the branch directory (or document directory if no branches are "
+"necessary), make at least a <filename class=\"directory\">en_US/</filename> "
+"directory. Make an additional directory for each locale that has been fully "
+"translated."
+msgstr ""
+
+#: en_US/publishing.xml:141(title)
+msgid "Adding Content"
+msgstr ""
+
+#: en_US/publishing.xml:142(para)
+msgid ""
+"To add content, follow the procedure below. The following commands show an "
+"example of adding content for a new document called the <citetitle>Foobar "
+"Tutorial</citetitle>. This document includes a translation for the \"zz_XX\" "
+"locale and follows specifics of each Fedora release."
+msgstr ""
+
+#: en_US/publishing.xml:149(para)
+msgid "Make the required directory structure."
+msgstr ""
+
+#: en_US/publishing.xml:150(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"mkdir foobar-tutorial\n"
+"mkdir foobar-tutorial/f7\n"
+"mkdir foobar-tutorial/f7/{en_US,zz_XX}"
+msgstr ""
+
+#: en_US/publishing.xml:156(para)
+msgid ""
+"Build the HTML version of each translation of the document from Docs CVS."
+msgstr ""
+
+#: en_US/publishing.xml:158(replaceable)
+msgid "~/my-docs/foobar-tutorial/F-7/"
+msgstr ""
+
+#: en_US/publishing.xml:158(screen)
+#, no-wrap
+msgid ""
+"cd <placeholder-1/>\n"
+"make html-en_US html-zz_XX"
+msgstr ""
+
+#: en_US/publishing.xml:162(para)
+msgid "Copy the HTML content to the web sandbox."
+msgstr ""
+
+#: en_US/publishing.xml:163(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/foobar-tutorial/f7/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-en_US/ en_US/\n"
+"cp -r ~/my-docs/foobar-tutorial/F-7/foobar-tutorial-zz_XX/ zz_XX/"
+msgstr ""
+
+#: en_US/publishing.xml:168(para)
+msgid ""
+"Convert the HTML in each directory to PHP using the provided "
+"<filename>docbookhtml2php.py</filename> script."
+msgstr ""
+
+#: en_US/publishing.xml:177(para)
+msgid ""
+"Create any necessary <filename>index.php</filename> files for the overall "
+"directories. Each document and branch directory must have an <filename>index."
+"php</filename> file directing users to appropriate content. In this example, "
+"the necessary files are <filename>foobar-tutorial/index.php</filename> and "
+"<filename>foobar-tutorial/f7/index.php</filename>. You do not need to write "
+"these files from scratch. Copy an existing file from another document, and "
+"change it as needed to suit the new document."
+msgstr ""
+
+#: en_US/publishing.xml:187(para)
+msgid ""
+"Depending on content, publication may include changing a higher-level "
+"<filename>index.php</filename> file."
+msgstr ""
+
+#: en_US/publishing.xml:191(para)
+msgid ""
+"To test the changes in your sandbox, open a web browser and point it at "
+"<uri>http://docs.localhost.localdomain/</uri>."
+msgstr ""
+
+#: en_US/publishing.xml:195(title)
+msgid "Always Test Changes"
+msgstr ""
+
+#: en_US/publishing.xml:196(para)
+msgid ""
+"<emphasis>Do not proceed further until you test all changes.</emphasis> "
+"Check that all links and index pages work."
+msgstr ""
+
+#: en_US/publishing.xml:204(title)
+msgid "Pushing Content to the Web"
+msgstr ""
+
+#: en_US/publishing.xml:205(para)
+msgid "To push your new content to the web site, follow this procedure:"
+msgstr ""
+
+#: en_US/publishing.xml:209(para)
+msgid "Add all the new file content to CVS."
+msgstr ""
+
+#: en_US/publishing.xml:210(screen)
+#, no-wrap
+msgid ""
+"cd ~/fedora/web/html/docs/\n"
+"cvs add foobar-tutorial\n"
+"cd foobar-tutorial\n"
+"cvs add f7\n"
+"cd f7\n"
+"cvs add en_US/ zz_XX/\n"
+"cvs add en_US/*php en_US/stylesheet-images/\n"
+"cvs add zz_XX/*php zz_XX/stylesheet-images/\n"
+"cvs add en_US/stylesheet-images/*png\n"
+"cvs add zz_XX/stylesheet-images/*png\n"
+"cd ../../\n"
+"cvs add foobar-tutorial/index.php\n"
+"cvs add foobar-tutorial/f7/index.php\n"
+msgstr ""
+
+#: en_US/publishing.xml:226(para)
+msgid ""
+"Commit the changes to CVS. Use a message that describes the document being "
+"committed."
+msgstr ""
+
+#: en_US/publishing.xml:228(replaceable)
+msgid "message about document"
+msgstr ""
+
+#: en_US/publishing.xml:228(screen)
+#, no-wrap
+msgid "cvs ci -m '<placeholder-1/>' foobar-tutorial/"
+msgstr ""
+
+#: en_US/publishing.xml:231(para)
+msgid "Tag the content <systemitem>LIVE</systemitem> in CVS."
+msgstr ""
+
+#: en_US/publishing.xml:233(screen)
+#, no-wrap
+msgid "cvs tag -F LIVE foobar-tutorial/"
+msgstr ""
+
+#: en_US/vim.xml:13(title)
+msgid "VIM and DocBook"
+msgstr "VIM 与 DocBook"
+
+#: en_US/vim.xml:16(primary) en_US/vim.xml:33(primary)
+msgid "VIM"
+msgstr "VIM"
+
+#: en_US/vim.xml:19(para)
+msgid ""
+"VIM has many features to help you write XML content such as DocBook, "
+"including syntax highlighting and customizable key bindings. Additionally, "
+"one can easily use external programs from VIM for features such as spell-"
+"checking. This chapter assumes you already know generally how to use VIM; if "
+"you want to learn how, try the <command>vimtutor</command> or by typing "
+"<userinput>:help tutor</userinput> from inside VIM."
+msgstr ""
+"VIM 有很多特性，有助于撰写类似 DocBook 的 XML 文档，包括语法高亮和可定制的按"
+"键绑定。另外，还可以用外部程序辅助 VIM 完成拼写检查等操作。本章假定您已知悉 "
+"VIM 一般用法；如果您要学习一般用法，执行 <command>vimtutor</command> 或在 "
+"VIM 中执行 <userinput>:help tutor</userinput>。"
+
+#: en_US/vim.xml:30(title)
+msgid "Setting Up Your <filename>.vimrc</filename> File"
+msgstr "设置 <filename>.vimrc</filename> 文件"
+
+#: en_US/vim.xml:34(secondary) en_US/emacs.xml:44(secondary)
+#, fuzzy
+msgid "configuration file"
+msgstr ""
+"#-#-#-#-# emacs.po (PACKAGE VERSION) #-#-#-#-#\n"
+"translator-credits\n"
+"#-#-#-#-# vim.po (PACKAGE VERSION) #-#-#-#-#\n"
+"配置文件"
+
+#: en_US/vim.xml:37(para)
+msgid ""
+"Below is a short sample <filename>.vimrc</filename> file that turns on some "
+"VIM features useful for editing SGML or XML content such as DocBook: "
+"<screen>\n"
+"<computeroutput>\" Turn off vi compatibility settings like limited undo\n"
+"set nocompatible\n"
+"\" Syntax highlighting based on file extension\n"
+"syntax on\n"
+"\" Automatically insert newlines after 80 characters\n"
+"set textwidth=80\n"
+"\" Automatically indent\n"
+"set autoindent\n"
+"\" Match SGML tags with %\n"
+"source $VIMRUNTIME/macros/matchit.vim</computeroutput>\n"
+"</screen>"
+msgstr ""
+"下面是一个示例 <filename>.vimrc</filename> 文件，打开了一些 VIM 特性，便于编"
+"辑类似 DocBook 的 SGML 或 XML 文档： <screen><computeroutput>\n"
+"\" 关闭 vi 兼容特性，类似有限的撤销\n"
+"set nocompatible\n"
+"\" 基于文件扩展名的语法高亮\n"
+"syntax on\n"
+"\" 在 80 个字符后面自动插入新行\n"
+"set textwidth=80\n"
+"\" 自动缩进\n"
+"set autoindent\n"
+"\" 使用 % 匹配 SGML 标记\n"
+"source $VIMRUNTIME/macros/matchit.vim\n"
+"</computeroutput></screen>"
+
+#: en_US/vim.xml:55(para)
+msgid ""
+"Some of these features require the <filename>vim-enhanced</filename> package "
+"to be installed. If you are using or the <filename>vim-minimal</filename> "
+"package, or if you are using an older version of VIM, you may not have the "
+"<filename>$VIMRUNTIME/macros/matchit.vim</filename> file. You can still "
+"download <ulink url=\"http://vim.org/scripts/script.php?script_id=39"
+"\">matchit.zip from Vim.org</ulink> and load it separately."
+msgstr ""
+"一些特性需要安装 <filename>vim-enhanced</filename>。如果您使用的是 "
+"<filename>vim-minimal</filename>，或者是旧版本的 VIM，可能不包含 <filename>"
+"$VIMRUNTIME/macros/matchit.vim</filename> 文件，那么可以在 Vim.org 下载 "
+"<ulink url=\"http://vim.org/scripts/script.php?script_id=39\">matchit.zip</"
+"ulink> 并加载。"
+
+#: en_US/vim.xml:69(title)
+msgid "Keymapping with VIM"
+msgstr "VIM 中的按键映射"
+
+#: en_US/vim.xml:71(para)
+msgid ""
+"VIM can speed up your DocBook creation by mapping frequently typed tags (or "
+"any words or phrases) onto short key combinations. By default, the keymap "
+"leader is the backslash (<literal>\\</literal>), but it can be redefined "
+"with a command like <userinput>let mapleader =\n"
+" \",\"</userinput>. There are two ways to use the following example; "
+"you can put it directly in your <filename>.vimrc</filename>, or you can save "
+"it in a separate file and load it with a <userinput>source</userinput> "
+"command in your <filename>.vimrc</filename>. <screen>\n"
+"<![CDATA[let mapleader = \",\"\n"
+"\n"
+"\" skip ahead to after next tag without leaving insert mode\n"
+"imap <leader>e <esc>/><cr>:nohlsearch<cr>a\n"
+"\n"
+"\" common tags that start a new text block\n"
+"imap<leader>pa <para><cr></para><esc>O\n"
+"imap<leader>sn <section id=\"\"><cr><para><esc>jo</section><esc>O\n"
+"imap<leader>pl <programlisting><cr></programlisting><esc>O<esc>0i\n"
+"imap<leader>cp <computeroutput></computeroutput><esc>O<esc>0i\n"
+"\n"
+"\" common tags that are placed inline\n"
+"\" use <esc>F>a\n"
+"imap<leader>en <envar></envar><esc>F>a\n"
+"imap<leader>fi <filename></filename><esc>F>a\n"
+"imap<leader>lt <literal></literal><esc>F>a\n"
+"imap<leader>re <replaceable></replaceable><esc>F>a\n"
+"imap<leader>ui <userinput></userinput><esc>F>a\n"
+"imap<leader>ul <ulink url=\"\"></ulink><esc>F>a\n"
+"imap<leader>si <systemitem></systemitem><esc>F>a\n"
+"imap<leader>us <systemitem class=\"username\"></systemitem><esc>F>a\n"
+"imap<leader>sy <systemitem class=\"systemname\"></systemitem><esc>F>a\n"
+"imap<leader>cm <command></"
+"command><esc>F>a \n"
+"\" entities\n"
+"imap <leader>> >\n"
+"imap <leader>< <]]>\n"
+"</screen>"
+msgstr ""
+"VIM 可以使创建 DocBook 文档更加快捷，只要将经常使用的标记 (或任何词汇短语) 定"
+"义为快捷键。默认情况下，键盘映射以反斜线 (<literal>\\</literal>) 开始，但是也"
+"可以用命令定义，类似 <userinput>let mapleader =\n"
+" \",\"</userinput>。有两种方式来使用下面的例子；您可以将它写在 "
+"<filename>.vimrc</filename> 文件中，或者将它保存为单独的文件，并在 "
+"<filename>.vimrc</filename> 文件中以 <userinput>source</userinput> 命令加载。"
+"<placeholder-1/>"
+
+#: en_US/vim.xml:110(para)
+msgid ""
+"Unfortunately, there is not currently a complete macro set for all DocBook "
+"commands, so you will need to define them yourself or customize the "
+"definitions in the examples from <xref linkend=\"sn-vim-additional-resources"
+"\"/>."
+msgstr ""
+"不幸的是，这不是所有 DocBook 命令的完整集合，因此您需要自行定义，或定制 "
+"<xref linkend=\"s1-vim-additional-resources\"/> 范例中的定义。"
+
+#: en_US/vim.xml:119(title)
+msgid "Additional VIM Resources"
+msgstr "其他 VIM 资源"
+
+#: en_US/vim.xml:121(para)
+msgid "Additional information about VIM may be found from:"
+msgstr "其他 VIM 相关的资源可以在这里找到："
+
+#: en_US/vim.xml:127(para)
+msgid ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> Example sgml-vimrc</ulink> from the <citetitle>Beginner's guide to "
+"Vi Improved (VIM)</citetitle>"
+msgstr ""
+"<ulink url=\"http://newbiedoc.sourceforge.net/text_editing/vim.html#JESSE-"
+"SGMLRC\"> 示例 sgml-vimrc</ulink>，来自 <citetitle>Beginner's guide to Vi "
+"Improved (VIM)</citetitle>"
+
+#: en_US/vim.xml:134(para)
+msgid ""
+"The <ulink url=\"http://tnerual.eriogerg.free.fr/vim.html\">VIM Quick "
+"Reference Card</ulink>"
+msgstr "VIM Quick Reference Card"
+
+#: en_US/vim.xml:140(ulink)
+msgid "Vim as XML Editor"
+msgstr "Vim 作为 XML 编辑器"
+
+#: en_US/vim.xml:145(para)
+msgid ""
+"The <citetitle>VIM REFERENCE MANUAL</citetitle>, which comes with the "
+"<filename>vim-common</filename> package —<filename>/usr/share/vim/"
+"<replaceable><version></replaceable>/doc/intro.txt</filename> or type "
+"<userinput>:help intro</userinput> from within VIM"
+msgstr ""
+"<citetitle>VIM REFERENCE MANUAL</citetitle>，包含在 <filename>vim-common</"
+"filename> 软件包中 /usr/share/vim/version/doc/intro.txt:help intro"
+
+#: en_US/tutorial.xml:13(title)
+msgid "The Layout of a Tutorial"
+msgstr "文档的布局"
+
+#: en_US/tutorial.xml:14(para)
+#, fuzzy
+msgid ""
+"In this chapter, you will find an example of a very short tutorial as used "
+"by the Fedora Documentation Project. This example is specific to the way the "
+"Docs Project uses DocBook XML. The example consists of a set of files used "
+"to hold the content and metadata for the tutorial."
+msgstr ""
+"在本章您将看到 !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 \"../common/fedora-entities-en.xml\" %FEDORA-"
+"ENTITIES-EN; !ENTITY VERSION \"0.1\" !-- change version of tutorial here -- !"
+"ENTITY DOCID \"example-tutorial-VERSION; (2003-07-07)\" !-- change last "
+"modified date here -- !ENTITY LEGALNOTICE SYSTEM \"../common/legalnotice-en."
+"xml\" ] article id=\"example-tutorial\" lang=\"en\" articleinfo titleExample "
+"Tutorial/title copyright year2003/year holder/holder holderTammy Fox/holder /"
+"copyright authorgroup author surnameFox/surname firstnameTammy/firstname /"
+"author /authorgroup LEGALNOTICE; /articleinfo section id=\"some-section\" "
+"titleSome Section/title para This is an example section. You can also use "
+"sect1, sect2, etc. /para warning titleWarning/title para Example of an "
+"admonition. /para /warning /section index id=\"generated-index\"/index /"
+"article legalnotice.xml"
+
+#: en_US/tutorial.xml:19(title)
+#, fuzzy
+msgid "The Article"
+msgstr "translator-credits"
+
+#: en_US/tutorial.xml:21(primary) en_US/tutorial.xml:56(primary)
+msgid "tutorial layout"
+msgstr ""
+
+#: en_US/tutorial.xml:22(secondary)
+msgid "article"
+msgstr ""
+
+#: en_US/tutorial.xml:24(para)
+msgid "Below is a sample article:"
+msgstr ""
+
+#: en_US/tutorial.xml:54(title)
+msgid "The Metadata"
+msgstr ""
+
+#: en_US/tutorial.xml:57(secondary)
+msgid "metadata"
+msgstr ""
+
+#: en_US/tutorial.xml:59(para)
+msgid ""
+"The <filename>rpm-info.xml</filename> file contains all the required "
+"metadata for the document. This metadata includes title, authorship, "
+"licensing, and revision history. <xref linkend=\"ex-rpminfo\"/> illustrates "
+"the content of this file:"
+msgstr ""
+
+#: en_US/tutorial.xml:65(title)
+#, fuzzy
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr ".emacs"
+
+#: en_US/tutorial.xml:95(para)
+msgid ""
+"If you are not familiar with XML editing, copy and paste this file from an "
+"existing module and then edit the values for the various elements as "
+"appropriate. Consult Fedora Documentation Project members and help channels "
+"for more assistance if needed."
+msgstr ""
+
+#: en_US/style.xml:14(title)
+msgid "Style"
+msgstr "写作风格"
+
+#: en_US/style.xml:16(para)
+msgid ""
+"Writing good technical documentation is not simply reproducing command lines "
+"and instruction sets. Good documentation is easy to read, understand, and "
+"translate, and presents a concise logical progression of concepts. Good "
+"documentation can also be defined by what it does <emphasis>not</emphasis> "
+"contain. Your tutorial should avoid:"
+msgstr ""
+"撰写完善的技术文档不仅仅指展示命令行和指令集。好文档应当容易阅读、理解、翻"
+"译，表达准确的概念间的逻辑关系。好文档也可以用 <emphasis>不应当做的</"
+"emphasis> 事情来定义。您的文档应当避免："
+
+#: en_US/style.xml:26(para)
+msgid "Excessive wordiness"
+msgstr "冗长"
+
+#: en_US/style.xml:31(para)
+msgid "Unnecessary or undefined jargon"
+msgstr "多余的，不加解释的行话"
+
+#: en_US/style.xml:36(para)
+msgid "Grammatical or spelling errors"
+msgstr "语法或拼写错误"
+
+#: en_US/style.xml:41(para)
+msgid "References to yourself or your experiences"
+msgstr "对个人经历的引证"
+
+#: en_US/style.xml:46(para)
+msgid "Remarks which might offend or confuse any reader"
+msgstr "可能触犯或迷惑用户的评论"
+
+#: en_US/style.xml:51(para)
+msgid ""
+"This chapter contains style rules and guidelines for writing Fedora "
+"documentation. Guidelines are not the same as rules. It is acceptable to "
+"violate a guideline when it makes your material easier to understand. Follow "
+"guidelines whenever possible, but follow rules at all times. Assume any "
+"advice is a guideline unless identified otherwise."
+msgstr ""
+"这一章包含了 style Ulysses http://www.online-literature.com/james_joyce/"
+"ulysses/18/ So you made the changes I showed you in the last section. What's "
+"the next thing you should do? Just pop your thumb drive onto your system and "
+"read the messages log. When you see \"USB device found,\" then Bob's your "
+"uncle. After you complete the configuration changes above, attach the USB "
+"removable media to your system. Use the dmesg command to examine the kernel "
+"message log. The message USB device found indicates that your device was "
+"installed successfully. The Elements of Style, http://bartleby.com/141/ The "
+"Chicago Manual of Style, http://www.chicagomanualofstyle.org/ Paradigm "
+"Online Writing Assistant, http://www.powa.org/ GNOME Documentation Style "
+"Guidelines (GDSG)GDSGhttp://developer.gnome.org/documents/style-guide/ GDSG "
+"The Elements of Style (http://www.bartleby.com/141/) Under normal operating "
+"conditions, the kernel does not always immediately write file data to the "
+"disks, storing it in a memory buffer and then periodically writing to the "
+"disks to speed up operations. Normally, the kernel stores the data in memory "
+"prior to periodically writing the data to the disk. The Workspace Switcher "
+"applet helps you navigate all of the virtual desktops available on your "
+"system. The X Window system, working in hand with a piece of software called "
+"a window manager, allows you to create more than one virtual desktop, known "
+"as workspaces, to organize your work, with different applications running in "
+"each workspace. The Workspace Switcher applet is a navigational tool to get "
+"around the various workspaces, providing a miniature road map in the GNOME "
+"panel showing all your workspaces and allowing you to switch easily between "
+"them. Use the Workspace Switcher to add new workspaces to the GNOME Desktop. "
+"You can run different applications in each workspace. The Workspace Switcher "
+"applet provides a miniature map that shows all of your workspaces. You can "
+"use the Workspace Switcher applet to switch between workspaces. There is a "
+"text box that you can use to find out the definition of a word. To request a "
+"definition of a word, type the word in the text box, then select Lookup. The "
+"applet is a handy little screen grabber. Use the applet to take screenshots. "
+"docs documentation Jargon Buster (http://fedora.redhat.com/docs/jargon-"
+"buster/) American Heritage Dictionary (http://www.bartleby.com/61/ ) GDSGThe "
+"Elements of Style American Heritage Dictionary (http://www.bartleby.com/61/) "
+"Chicago Manual of Style (http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/"
+"cmosfaq.html) Dr., a.m., p.m. i.e. (\"in other words\", e.g. (\"for example"
+"\", From the first letters of each word in a compound term, for example "
+"Table of Contents (TOC). From recognizable parts of a compound term, such as "
+"GNU Object Model Environment (GNOME). the the Main Menu'sHelp option don't "
+"use the default option several SCSI disk's the Help option on the Main Menu "
+"do not use the default option several SCSI disks replaceable Shift can't, "
+"don't, isn't Chicago Manual of Style ( http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html) American Heritage Dictionary (http://www."
+"bartleby.com/61/) directory-namefilename ly American Heritage Dictionary "
+"(http://www.bartleby.com/61/) Chicago Manual of Style (http://www.press."
+"uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html) See v. Refer to see seealso "
+"and/or American Heritage Dictionary (http://www.bartleby.com/61/) IEEE "
+"Standard Dictionary of Electrical and Electronics Terms yum update yum "
+"update yum update up2date tar cpio up2date tar cpio don't can't XYZ\" XYZ"
+"\"XYZ Main Menu - Foobar Search Main Menu Foobar Search DocBook sfdisk "
+"sfdisk sfdisk sfdisk -n sfdisk sfdisk sfdisk -n replaceable replaceable XML "
+"fedora-docs common/ FC; FCVER;\" \""
+
+#: en_US/style.xml:62(title)
+msgid "Why Style Is Important"
+msgstr "translator-credits"
+
+#: en_US/style.xml:64(para)
+msgid ""
+"Writing well comes naturally to almost no one. It is a skill that "
+"professional writers, even famous ones, must practice constantly. "
+"<firstterm>Style</firstterm><indexterm><primary>style</primary></indexterm> "
+"is the quality that separates elegant writing from the merely functional."
+msgstr ""
+
+#: en_US/style.xml:77(para)
+msgid ""
+"For example, refer to. <ulink url=\"http://www.online-literature.com/"
+"james_joyce/ulysses/18/\">http://www.online-literature.com/james_joyce/"
+"ulysses/18/</ulink>. Please note that this example contains some mature "
+"themes and language, and is not suitable for all readers."
+msgstr ""
+
+#: en_US/style.xml:71(para)
+msgid ""
+"Elegance comes in many forms. In prose and poetry, elegant writing may not "
+"follow some (or any) common rules of grammar, syntax, or spelling. A good "
+"example is Episode 18, \"Penelope,\" in James Joyce's novel "
+"<citetitle>Ulysses</citetitle><placeholder-1/>. There, Joyce uses long "
+"streams of words without punctuation to simulate a character's internal "
+"consciousness. By violating basic rules of grammar and syntax, Joyce "
+"simulates the disorganized but loosely connected thought patterns of the "
+"narrator."
+msgstr ""
+
+#: en_US/style.xml:89(para)
+msgid ""
+"Technical documentation, however, should always respect these rules. The "
+"more a document departs from standard language usage, the more difficult the "
+"material becomes for the reader. For example, readers may not be native "
+"speakers of the language used, or they might be reading a translation. If "
+"the writer uses slang, idioms, or jargon, a reader or translator may easily "
+"become confused. The following example compares two different written "
+"executions of the same idea:"
+msgstr ""
+
+#: en_US/style.xml:100(title)
+msgid "Incorrect style"
+msgstr ""
+
+#. I prefer "incorrect," because I think terms such as
+#. "problematic" are mealy-mouthed. They remind me of the late
+#. 1980's English textbook trend toward the politically correct yet
+#. wholly unhelpful "standard/nonstandard." But then, I tend to be
+#. dogmatic; it's probably my Catholic upbringing. [PWF]
+#: en_US/style.xml:108(para)
+msgid ""
+"So you made the changes I showed you in the last section. What's the next "
+"thing you should do? Just pop your thumb drive onto your system and read the "
+"<filename>messages</filename> log. When you see \"USB device found,\" then "
+"Bob's your uncle."
+msgstr ""
+
+#: en_US/style.xml:116(title)
+msgid "Correct style"
+msgstr ""
+
+#. I prefer "correct." See above. [PWF]
+#: en_US/style.xml:120(para)
+msgid ""
+"After you complete the configuration changes above, attach the USB removable "
+"media to your system. Use the <command>dmesg</command> command to examine "
+"the kernel message log. The message <computeroutput>USB device\n"
+"\t found</computeroutput> indicates that your device was installed "
+"successfully."
+msgstr ""
+
+#: en_US/style.xml:129(para)
+msgid ""
+"The first example is more conversational English, which is not appropriate "
+"for official written documentation. The second example is more formal, but "
+"as a result it is easier to comprehend, both for native readers and "
+"translators."
+msgstr ""
+
+#: en_US/style.xml:135(para)
+msgid ""
+"Following style rules and guidelines also makes readers more comfortable "
+"with a set of documents. Consistent style enhances the professional "
+"appearance of documentation, and its perceived value. On the other hand, "
+"lapses in punctuation or poor grammar negatively affect a reader's reaction "
+"to written material. A reader can feel that an otherwise correct technical "
+"document is lacking in authority, simply because it is poorly written. "
+"Readers feel at ease when they do not have to struggle to understand an "
+"author's use of language."
+msgstr ""
+
+#: en_US/style.xml:146(para)
+msgid ""
+"This chapter cannot possibly cover enough material to make every reader a "
+"good writer. Some manuals devoted entirely to writing style are themselves "
+"hundreds of pages long. This chapter provides enough guidelines for "
+"intermediate writers to understand style usage in technical documentation."
+msgstr ""
+
+#: en_US/style.xml:153(para)
+msgid ""
+"If you are not a practiced writer, whether of technical documentation or "
+"otherwise, you may benefit from other style resources. The following list is "
+"far from comprehensive, but provides a starting point:"
+msgstr ""
+
+#: en_US/style.xml:161(para)
+msgid ""
+"<citetitle>The Elements of Style</citetitle>, by William Strunk. Basic rules "
+"and links to online versions can be found at: <ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>"
+msgstr ""
+
+#: en_US/style.xml:176(para)
+msgid ""
+"<citetitle>The Chicago Manual of Style</citetitle>, by the University of "
+"Chicago Press. Online version: <ulink url=\"http://www.chicagomanualofstyle."
+"org/\">http://www.chicagomanualofstyle.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:183(para)
+msgid ""
+"<citetitle>Paradigm Online Writing Assistant</citetitle>, maintained by "
+"Chuck Guilford, Ph.D. Online only: <ulink url=\"http://www.powa.org/"
+"\">http://www.powa.org/</ulink>"
+msgstr ""
+
+#: en_US/style.xml:190(para)
+msgid ""
+"There are many free software documentation projects which have developed "
+"their own style guidelines. This chapter, in fact, draws heavily on the "
+"<citetitle>GNOME Documentation Style Guidelines</citetitle> "
+"(<firstterm>GDSG</firstterm>). You may read the original <citetitle>GDSG</"
+"citetitle> at <ulink url=\"http://developer.gnome.org/documents/style-guide/"
+"\">http://developer.gnome.org/documents/style-guide/</ulink>."
+msgstr ""
+
+#: en_US/style.xml:203(title)
+msgid "Fundamental Concepts of Technical Documentation"
+msgstr ""
+
+#: en_US/style.xml:206(title)
+msgid "Bibliographic Information"
+msgstr ""
+
+#: en_US/style.xml:207(para)
+msgid "This section is drawn primarily from the <citetitle>GDSG</citetitle>."
+msgstr ""
+
+#. This section will reproduce mostly what is in Chapter 1 of
+#. the GDSG. There may be minor changes. FIXME: Make sure the
+#. appropriate front matter of the Documentation Guide includes
+#. attribution as required by the GNU FDL.
+#: en_US/style.xml:218(para)
+msgid ""
+"This chapter provides a brief introduction to writing technical "
+"documentation."
+msgstr ""
+
+#: en_US/style.xml:224(title)
+msgid "General Style Requirements"
+msgstr ""
+
+#: en_US/style.xml:225(para)
+msgid ""
+"Technical writing for the Fedora Project imposes special constraints beyond "
+"the basic requirements of good prose. Good Fedora technical documentation "
+"has the following characteristics:"
+msgstr ""
+
+#: en_US/style.xml:232(term)
+msgid "Comprehensive"
+msgstr ""
+
+#: en_US/style.xml:234(para)
+msgid ""
+"Describe all of the functionality of a product. Do not omit functionality "
+"that you regard as irrelevant for the user."
+msgstr ""
+
+#: en_US/style.xml:242(term)
+msgid "Conforming"
+msgstr ""
+
+#: en_US/style.xml:249(para)
+msgid ""
+"Describe what you see. Do not describe what you want to see. Present your "
+"information in the order that users experience the subject matter."
+msgstr ""
+
+#: en_US/style.xml:257(term)
+msgid "Clear"
+msgstr ""
+
+#: en_US/style.xml:259(para)
+msgid ""
+"Read <citetitle>The Elements of Style</citetitle> (<ulink url=\"http://en."
+"wikipedia.org/wiki/The_Elements_of_Style\">http://en.wikipedia.org/wiki/"
+"The_Elements_of_Style</ulink>) to help make your writing clear."
+msgstr ""
+
+#: en_US/style.xml:275(term)
+msgid "Consistent"
+msgstr ""
+
+#: en_US/style.xml:277(para)
+msgid ""
+"Use agreed vocabulary throughout your documentation. Use the same vocabulary "
+"as other writers who are working on related documentation."
+msgstr ""
+
+#: en_US/style.xml:285(term)
+msgid "Concise"
+msgstr ""
+
+#: en_US/style.xml:287(para)
+msgid ""
+"Review your work frequently as you write your document. Ask yourself which "
+"words you can take out. Refer to <xref linkend=\"sn-fundamentals-2\"/> for "
+"specific guidelines."
+msgstr ""
+
+#: en_US/style.xml:297(title)
+msgid "Golden Rules"
+msgstr ""
+
+#: en_US/style.xml:298(para)
+msgid ""
+"This section contains some basic style guidelines. Subsequent sections in "
+"this chapter expand on these guidelines to give more detailed guidance."
+msgstr ""
+
+#: en_US/style.xml:305(term)
+msgid "Golden Rule 1: Be brief"
+msgstr ""
+
+#: en_US/style.xml:309(para)
+msgid "Limit each sentence to fewer than 25 words."
+msgstr ""
+
+#: en_US/style.xml:314(para)
+msgid "Limit each procedure step to 23 words."
+msgstr ""
+
+#: en_US/style.xml:320(title)
+msgid "Incorrect: Too long"
+msgstr ""
+
+#: en_US/style.xml:321(para)
+msgid ""
+"Under normal operating conditions, the kernel does not always immediately "
+"write file data to the disks, storing it in a memory buffer and then "
+"periodically writing to the disks to speed up operations."
+msgstr ""
+
+#: en_US/style.xml:328(title)
+msgid "Correct: Less wordy"
+msgstr ""
+
+#: en_US/style.xml:329(para)
+msgid ""
+"Normally, the kernel stores the data in memory prior to periodically writing "
+"the data to the disk."
+msgstr ""
+
+#: en_US/style.xml:337(term)
+msgid "Golden Rule 2: Be organized"
+msgstr ""
+
+#: en_US/style.xml:341(para)
+msgid "Limit each paragraph to one topic."
+msgstr ""
+
+#: en_US/style.xml:346(para)
+msgid "Limit each sentence to one idea."
+msgstr ""
+
+#: en_US/style.xml:351(para)
+msgid "Limit each procedure step to one action."
+msgstr ""
+
+#: en_US/style.xml:357(title)
+msgid "Incorrect: Disorganized topics"
+msgstr ""
+
+#: en_US/style.xml:358(para)
+msgid ""
+"The <application>Workspace Switcher</application> applet helps you navigate "
+"all of the virtual desktops available on your system. The X Window system, "
+"working in hand with a piece of software called a <emphasis>window manager</"
+"emphasis>, allows you to create more than one virtual desktop, known as "
+"<emphasis>workspaces</emphasis>, to organize your work, with different "
+"applications running in each workspace. The <application>Workspace Switcher</"
+"application> applet is a navigational tool to get around the various "
+"workspaces, providing a miniature road map in the GNOME panel showing all "
+"your workspaces and allowing you to switch easily between them."
+msgstr ""
+
+#: en_US/style.xml:375(title)
+msgid "Correct: Organized topics"
+msgstr ""
+
+#: en_US/style.xml:376(para)
+msgid ""
+"Use the <application>Workspace Switcher</application> to add new "
+"<emphasis>workspaces</emphasis> to the GNOME Desktop. You can run different "
+"applications in each workspace. The <application>Workspace Switcher</"
+"application> applet provides a miniature map that shows all of your "
+"workspaces. You can use the <application>Workspace Switcher</application> "
+"applet to switch between workspaces."
+msgstr ""
+
+#: en_US/style.xml:388(para)
+msgid ""
+"Plan the order of paragraphs before you start writing. Decide which topic "
+"you want to cover in each paragraph."
+msgstr ""
+
+#: en_US/style.xml:396(term)
+msgid "Golden Rule 3: Be demonstrative"
+msgstr ""
+
+#: en_US/style.xml:398(para)
+msgid ""
+"Use explicit examples to demonstrate how an application works. Provide "
+"instructions rather than descriptions."
+msgstr ""
+
+#: en_US/style.xml:403(title)
+msgid "Incorrect: Describes but does not demonstrate"
+msgstr ""
+
+#: en_US/style.xml:405(para)
+msgid ""
+"There is a text box that you can use to find out the definition of a word."
+msgstr ""
+
+#: en_US/style.xml:411(title)
+msgid "Correct: Demonstrates usage"
+msgstr ""
+
+#: en_US/style.xml:412(para)
+msgid ""
+"To request a definition of a word, type the word in the text box, then "
+"select <guilabel>Lookup</guilabel>."
+msgstr ""
+
+#: en_US/style.xml:418(para)
+msgid ""
+"Do not apply this guideline too rigidly. Sometimes you must explain how "
+"software works to support your how-to examples."
+msgstr ""
+
+#: en_US/style.xml:427(term)
+msgid "Golden Rule 4: Be objective"
+msgstr ""
+
+#: en_US/style.xml:429(para)
+msgid "Write in a neutral tone."
+msgstr ""
+
+#: en_US/style.xml:433(title)
+msgid "Incorrect: Sentence takes sides"
+msgstr ""
+
+#: en_US/style.xml:434(para)
+msgid "The applet is a handy little screen grabber."
+msgstr ""
+
+#: en_US/style.xml:439(title)
+msgid "Correct: Sentence is objective"
+msgstr ""
+
+#: en_US/style.xml:440(para)
+msgid "Use the applet to take screenshots."
+msgstr ""
+
+#: en_US/style.xml:452(title)
+msgid "Tone"
+msgstr ""
+
+#: en_US/style.xml:453(para)
+msgid ""
+"Inappropriate tone hinders reader access to information. A neutral tone free "
+"of opinion or personal flavor improves the reader's comprehension. Neutral "
+"tone helps writers to work in parallel on a large technical documentation "
+"project. Furthermore, additional writers may join the project at any time. "
+"Use of a neutral tone helps to achieve consistency across a documentation "
+"set, and thereby facilitates user access to information. The best way to "
+"achieve a common, neutral tone is to apply the following principles:"
+msgstr ""
+
+#: en_US/style.xml:466(term)
+msgid "Avoid humor"
+msgstr ""
+
+#: en_US/style.xml:468(para)
+msgid ""
+"Humor distracts from the information you are trying to provide. Humor also "
+"makes documentation difficult to translate. Stay factual."
+msgstr ""
+
+#: en_US/style.xml:476(term)
+msgid "Avoid personal opinions"
+msgstr ""
+
+#: en_US/style.xml:478(para)
+msgid ""
+"Whether you think a function is useful or woeful is irrelevant. Report the "
+"function to the user, with instructions about how to use the function. Stay "
+"accurate."
+msgstr ""
+
+#: en_US/style.xml:487(term)
+msgid "Avoid colloquial language"
+msgstr ""
+
+#: en_US/style.xml:489(para)
+msgid ""
+"Colloquial language is difficult to translate and usually culture-specific. "
+"Stay neutral."
+msgstr ""
+
+#: en_US/style.xml:496(term)
+msgid "Avoid topical expressions"
+msgstr ""
+
+#: en_US/style.xml:498(para)
+msgid ""
+"An expression that is in common use today might convey something completely "
+"different tomorrow. Stay technical."
+msgstr ""
+
+#: en_US/style.xml:505(term)
+msgid "Avoid aspirational statements"
+msgstr ""
+
+#: en_US/style.xml:507(para)
+msgid ""
+"Statements about the future developments of a product do not belong in "
+"technical documentation. Write about what you see right now. Stay real."
+msgstr ""
+
+#: en_US/style.xml:517(title)
+msgid "Reaching the Right Audience"
+msgstr ""
+
+#: en_US/style.xml:518(para)
+msgid ""
+"All of the decisions that you make about the structure and content of a "
+"manual follow from an understanding of the audience. Consider how the "
+"audience accesses the documentation, what sort of information the audience "
+"needs, and the experience level of the audience. Usually, you need to create "
+"documentation that is suitable for different audiences. The following "
+"sections introduce some of the audience-related topics you need to consider."
+msgstr ""
+
+#: en_US/style.xml:530(title)
+msgid "User Motivation"
+msgstr ""
+
+#: en_US/style.xml:531(para)
+msgid ""
+"Do not waste the time of the user who looks for information in your "
+"documentation. Users do not read technical documentation for entertainment. "
+"Users usually have specific questions. You need to give clear answers to "
+"those questions."
+msgstr ""
+
+#: en_US/style.xml:539(title)
+msgid "New Users"
+msgstr ""
+
+#: en_US/style.xml:540(para)
+msgid ""
+"New users to Fedora are likely to consult online tutorials for guidance "
+"about unfamiliar applications or functionality. Each tutorial should contain "
+"enough introductory information to tell new users how to start using the "
+"relevant functions. Each tutorial should also contain enough usage "
+"instructions to tell users the different actions that they can perform with "
+"the command or function. Keep these instructions task-oriented. Do not "
+"describe GUI screens, dialogs, and dialog elements in a tutorial, unless "
+"there is an unusual feature that affects your instructions."
+msgstr ""
+
+#: en_US/style.xml:554(title)
+msgid "Experienced Users"
+msgstr ""
+
+#: en_US/style.xml:555(para)
+msgid ""
+"Experienced users are more likely to use documentation as a reference. The "
+"documentation therefore needs to be complete, well-organized, and in the "
+"case of printed manuals, well-indexed."
+msgstr ""
+
+#: en_US/style.xml:563(title)
+msgid "Do Not Offend Your Audience"
+msgstr ""
+
+#: en_US/style.xml:564(para)
+msgid ""
+"To avoid offending your readers, apply the following guidelines to your "
+"documentation:"
+msgstr ""
+
+#: en_US/style.xml:570(term)
+msgid "Avoid insider language"
+msgstr ""
+
+#: en_US/style.xml:572(para)
+msgid ""
+"Insider language includes both undefined jargon and the tendency of the "
+"computer community to shorten words. For example, use the term "
+"<literal>documentation</literal> instead of the term <literal>docs</"
+"literal>. A term may be jargon if it fails all the following conditions:"
+msgstr ""
+
+#: en_US/style.xml:581(para)
+msgid ""
+"The term does not appear in the <citetitle>Fedora Jargon Buster</citetitle> "
+"(<ulink url=\"http://fedora.redhat.com/docs/jargon-buster/\">http://fedora."
+"redhat.com/docs/jargon-buster/</ulink>)."
+msgstr ""
+
+#: en_US/style.xml:588(para)
+msgid ""
+"The term does not appear in the <citetitle>American Heritage Dictionary</"
+"citetitle> (<ulink url=\"http://www.bartleby.com/61/\">http://www.bartleby."
+"com/61/ </ulink>)."
+msgstr ""
+
+#: en_US/style.xml:596(para)
+msgid ""
+"The term does not appear in the glossary of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:602(para)
+msgid ""
+"The term is not defined in the body text of the manual that you are writing."
+msgstr ""
+
+#: en_US/style.xml:611(term)
+msgid "Avoid gender-specific language"
+msgstr ""
+
+#: en_US/style.xml:613(para)
+msgid ""
+"Pronoun constructions such as <literal>his/her</literal> or <literal>s/he</"
+"literal> do not exist. There is no need to identify gender in your "
+"instructions."
+msgstr ""
+
+#: en_US/style.xml:621(term)
+msgid "Avoid culture-specific language"
+msgstr ""
+
+#: en_US/style.xml:623(para)
+msgid ""
+"There is little point in giving an example that everyone in your town knows "
+"about, but is a complete mystery to everyone else in the world."
+msgstr ""
+
+#: en_US/style.xml:631(term)
+msgid "Avoid talking down to your reader"
+msgstr ""
+
+#: en_US/style.xml:633(para)
+msgid ""
+"There are few experiences more irritating for a user than documentation that "
+"says an action is easy or quick, when in fact the user cannot complete the "
+"action. Do not qualify or prejudge actions."
+msgstr ""
+
+#: en_US/style.xml:642(para)
+msgid ""
+"Other parts of this guide discuss in more detail tone and language usage "
+"that can cause offense."
+msgstr ""
+
+#: en_US/style.xml:653(title)
+msgid "Grammar and Usage Guidelines"
+msgstr ""
+
+#: en_US/style.xml:656(title)
+msgid "Bibliographical Information"
+msgstr ""
+
+#: en_US/style.xml:657(para)
+msgid ""
+"This section is drawn partly from the <citetitle>GDSG</citetitle>, and "
+"partly from <citetitle>The Elements of Style</citetitle>, updated as "
+"necessary for the needs of 21st-century technical documentation writers."
+msgstr ""
+
+#. FIXME: Again, check attribution viz. GNU FDL. This will be more work
+#. than the previous section.
+#: en_US/style.xml:668(para)
+msgid ""
+"This section contains an alphabetical list of grammar and usage guidelines "
+"for use in Fedora documentation. Many of these guidelines are only "
+"applicable to English-language usage, refer to the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) and the <citetitle>Chicago Manual of "
+"Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/"
+"cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:679(term)
+msgid "Abbreviations"
+msgstr ""
+
+#: en_US/style.xml:681(para)
+msgid ""
+"A shortened form of a word or phrase that takes the place of the full word "
+"or phrase, such as <literal>Dr.</literal>, <literal>a.m.</literal>, "
+"<literal>p.m.</literal>, and so on. Apply the following rules when you use "
+"abbreviations:"
+msgstr ""
+
+#: en_US/style.xml:689(para)
+msgid ""
+"Avoid creating new abbreviations. Unfamiliar abbreviations can confuse "
+"rather than clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:695(para)
+msgid "Do not explain or expand familiar abbreviations."
+msgstr ""
+
+#: en_US/style.xml:700(para)
+msgid "Do not include familiar abbreviations in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:706(para)
+msgid ""
+"For abbreviations of phrases, such as <literal>i.e.</literal> for \"in other "
+"words\" and <literal>e.g.</literal> for \"for example\", do not use the "
+"abbreviation. Spell out the entire phrase."
+msgstr ""
+
+#: en_US/style.xml:715(term)
+msgid "Adjectives"
+msgstr ""
+
+#: en_US/style.xml:717(para)
+msgid ""
+"Use adjectives with caution. If an adjective is necessary to differentiate "
+"between items, then use adjectives. In all cases, test whether the phrase "
+"can stand alone without the adjective."
+msgstr ""
+
+#: en_US/style.xml:726(term)
+msgid "Acronyms"
+msgstr ""
+
+#: en_US/style.xml:728(para)
+msgid ""
+"A term that represents a multi-word term. Typically, acronyms are formed in "
+"the following ways:"
+msgstr ""
+
+#: en_US/style.xml:734(para)
+msgid ""
+"From the first letters of each word in a compound term, for example Table of "
+"Contents (TOC)."
+msgstr ""
+
+#: en_US/style.xml:740(para)
+msgid ""
+"From recognizable parts of a compound term, such as GNU Object Model "
+"Environment (GNOME)."
+msgstr ""
+
+#: en_US/style.xml:746(para)
+msgid "Apply the following rules when you use acronyms:"
+msgstr ""
+
+#: en_US/style.xml:751(para)
+msgid ""
+"On the first occurrence of an acronym, spell out the full term, with the "
+"acronym in parentheses."
+msgstr ""
+
+#: en_US/style.xml:757(para)
+msgid ""
+"Do not spell out the full compound for well-known acronyms, unless you think "
+"the information is useful for readers."
+msgstr ""
+
+#: en_US/style.xml:764(para)
+msgid ""
+"Avoid creating new acronyms. Unfamiliar acronyms can confuse rather than "
+"clarify a concept."
+msgstr ""
+
+#: en_US/style.xml:770(para)
+msgid ""
+"Write the acronym in uppercase letters, unless there is a compelling case "
+"for lowercase."
+msgstr ""
+
+#: en_US/style.xml:776(para)
+msgid "Include the acronym and the full term in the glossary of your manual."
+msgstr ""
+
+#: en_US/style.xml:785(term)
+msgid "Adverbs"
+msgstr ""
+
+#: en_US/style.xml:787(para)
+msgid ""
+"Use adverbs with caution. If an adverb is necessary to qualify the function "
+"of a component, then use an adverb. In all cases, test whether the phrase "
+"can stand alone without the adverb. Classic superfluous adverbs "
+"<literal>simply</literal>, <literal>easily</literal>, <literal>quickly</"
+"literal>."
+msgstr ""
+
+#: en_US/style.xml:798(term)
+msgid "Anthropomorphism"
+msgstr ""
+
+#: en_US/style.xml:802(para)
+msgid "Do not apply emotions, desires, or opinions to software applications."
+msgstr ""
+
+#: en_US/style.xml:808(para)
+msgid ""
+"Do not apply a sense of location or dimension to a software application. A "
+"user can not be \"in\" a text editor."
+msgstr ""
+
+#: en_US/style.xml:818(term)
+msgid "Articles"
+msgstr ""
+
+#: en_US/style.xml:820(para)
+msgid ""
+"Do not use the definite article <literal>the</literal> to begin any of the "
+"following items:"
+msgstr ""
+
+#: en_US/style.xml:826(para)
+msgid "Manual titles"
+msgstr ""
+
+#: en_US/style.xml:831(para)
+msgid "Chapter titles"
+msgstr ""
+
+#: en_US/style.xml:836(para) en_US/style.xml:1239(term)
+msgid "Headings"
+msgstr ""
+
+#: en_US/style.xml:841(para)
+msgid "Figure captions"
+msgstr ""
+
+#: en_US/style.xml:846(para)
+msgid "Table captions"
+msgstr ""
+
+#: en_US/style.xml:851(para)
+msgid "Callouts"
+msgstr ""
+
+#: en_US/style.xml:859(term)
+msgid "Apostrophe"
+msgstr ""
+
+#: en_US/style.xml:861(para)
+msgid "Do not use apostrophes except where absolutely required"
+msgstr ""
+
+#: en_US/style.xml:866(para)
+msgid "Do not use apostrophes to denote possession."
+msgstr ""
+
+#: en_US/style.xml:871(para)
+msgid "Do not use apostrophes to denote contractions."
+msgstr ""
+
+#: en_US/style.xml:876(para)
+msgid "Do not use apostrophes to denote plurals."
+msgstr ""
+
+#: en_US/style.xml:882(title)
+msgid "Incorrect: Apostrophes"
+msgstr ""
+
+#: en_US/style.xml:885(para)
+msgid ""
+"the <guimenu>Main Menu's</guimenu><guimenuitem>Help</guimenuitem> option"
+msgstr ""
+
+#: en_US/style.xml:891(para)
+msgid "don't use the default option"
+msgstr ""
+
+#: en_US/style.xml:896(para)
+msgid "several SCSI disk's"
+msgstr ""
+
+#: en_US/style.xml:903(title)
+msgid "Correct: No apostrophes"
+msgstr ""
+
+#: en_US/style.xml:906(para)
+msgid ""
+"the <guimenuitem>Help</guimenuitem> option on the <guimenu>Main Menu</"
+"guimenu>"
+msgstr ""
+
+#: en_US/style.xml:912(para)
+msgid "do not use the default option"
+msgstr ""
+
+#: en_US/style.xml:917(para)
+msgid "several SCSI disks"
+msgstr ""
+
+#: en_US/style.xml:926(term)
+msgid "Brackets"
+msgstr ""
+
+#: en_US/style.xml:930(para)
+msgid ""
+"Do not use brackets [such as these] as a substitute for parentheses (such as "
+"these)."
+msgstr ""
+
+#: en_US/style.xml:936(para)
+msgid "Use brackets for optional command line entries."
+msgstr ""
+
+#: en_US/style.xml:941(para)
+msgid ""
+"Do not use angle brackets to indicate variables in text, instead use the "
+"<sgmltag class=\"starttag\">replaceable</sgmltag> tag. Refer to <xref "
+"linkend=\"sn-xml-tags-replaceable\"/> for information about using this tag."
+msgstr ""
+
+#: en_US/style.xml:953(term)
+msgid "Capitalization"
+msgstr ""
+
+#: en_US/style.xml:955(para)
+msgid "Capitalize in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:960(para)
+msgid "All letters in acronyms, unless the acronym is a well-known exception"
+msgstr ""
+
+#: en_US/style.xml:966(para)
+msgid "Initial letter of the first word in a list"
+msgstr ""
+
+#: en_US/style.xml:971(para)
+msgid "Initial letter of the first word in a callout"
+msgstr ""
+
+#: en_US/style.xml:976(para)
+msgid "Initial letter of a key name, such as the <keycap>Shift</keycap> key"
+msgstr ""
+
+#: en_US/style.xml:982(para)
+msgid "Initial letter of a sentence"
+msgstr ""
+
+#: en_US/style.xml:986(title)
+msgid "Command Names"
+msgstr ""
+
+#: en_US/style.xml:987(para)
+msgid ""
+"Avoid starting a sentence with a command name or application name that has a "
+"lowercase initial letter."
+msgstr ""
+
+#: en_US/style.xml:994(para)
+msgid "Initial letter of a complete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:999(para)
+msgid "Do not capitalize in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1004(para)
+msgid "A compound term that is followed by an abbreviation or an acronym"
+msgstr ""
+
+#: en_US/style.xml:1010(para)
+msgid "When you want to emphasize something"
+msgstr ""
+
+#: en_US/style.xml:1015(para)
+msgid "Variable names"
+msgstr ""
+
+#: en_US/style.xml:1020(para)
+msgid "The initial letter of an incomplete sentence after a colon"
+msgstr ""
+
+#: en_US/style.xml:1029(term)
+msgid "Captions"
+msgstr ""
+
+#: en_US/style.xml:1031(para)
+msgid ""
+"Use the same rules as for headings, for all captions accompanying figures "
+"and tables. Do not put a period at the end of a caption."
+msgstr ""
+
+#: en_US/style.xml:1039(term)
+msgid "Colon"
+msgstr ""
+
+#: en_US/style.xml:1041(para)
+msgid "Use a colon in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1046(para)
+msgid "To introduce a list"
+msgstr ""
+
+#: en_US/style.xml:1051(para)
+msgid "Before an explanation"
+msgstr ""
+
+#: en_US/style.xml:1056(para)
+msgid "After an introduction"
+msgstr ""
+
+#: en_US/style.xml:1061(para)
+msgid "Do not use a colon in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1066(para)
+msgid "To introduce a figure or a table"
+msgstr ""
+
+#: en_US/style.xml:1071(para)
+msgid "To introduce headings"
+msgstr ""
+
+#: en_US/style.xml:1076(para)
+msgid "At the end of an introduction to a procedure"
+msgstr ""
+
+#: en_US/style.xml:1084(term)
+msgid "Column headings"
+msgstr ""
+
+#: en_US/style.xml:1086(para)
+msgid "Use the same rules as for headings."
+msgstr ""
+
+#: en_US/style.xml:1092(term)
+msgid "Comma"
+msgstr ""
+
+#: en_US/style.xml:1094(para)
+msgid "Use commas in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1099(para)
+msgid "To separate items in a series"
+msgstr ""
+
+#: en_US/style.xml:1104(para)
+msgid "To separate the parts of a sentence"
+msgstr ""
+
+#: en_US/style.xml:1109(para)
+msgid "To separate nonrestrictive phrases"
+msgstr ""
+
+#: en_US/style.xml:1114(para)
+msgid "Instead of dashes to set off appositives"
+msgstr ""
+
+#: en_US/style.xml:1119(para)
+msgid "With <emphasis>for example</emphasis> and similar expressions"
+msgstr ""
+
+#: en_US/style.xml:1125(para)
+msgid "Do not use commas in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1130(para)
+msgid "In a series of adjectives used as one modifier"
+msgstr ""
+
+#: en_US/style.xml:1135(para)
+msgid "Between two short independent clauses"
+msgstr ""
+
+#: en_US/style.xml:1143(term) en_US/emacs-nxml.xml:86(title)
+msgid "Commands"
+msgstr "命令"
+
+#: en_US/style.xml:1145(para)
+msgid "Do not use commands as verbs."
+msgstr ""
+
+#: en_US/style.xml:1151(term)
+msgid "Contractions"
+msgstr ""
+
+#: en_US/style.xml:1153(para)
+msgid ""
+"Do not use contractions such as <emphasis>can't</emphasis>, <emphasis>don't</"
+"emphasis>, or <emphasis>isn't</emphasis>."
+msgstr ""
+
+#: en_US/style.xml:1160(term)
+msgid "Dash"
+msgstr ""
+
+#: en_US/style.xml:1162(para)
+msgid ""
+"Do not use the em dash or the en dash. Use a paragraph break or a colon "
+"instead, where you want to create an introductory piece of text. If you have "
+"several items that you want to introduce, then you can use a variable list."
+msgstr ""
+
+#: en_US/style.xml:1171(term)
+msgid "Ellipsis"
+msgstr ""
+
+#: en_US/style.xml:1173(para)
+msgid "Use an ellipsis in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1178(para)
+msgid "To show that you have omitted something from a sentence"
+msgstr ""
+
+#: en_US/style.xml:1183(para)
+msgid "To indicate a pause when you quote displayed text"
+msgstr ""
+
+#: en_US/style.xml:1191(term)
+msgid "Fractions"
+msgstr ""
+
+#: en_US/style.xml:1193(para)
+msgid "Follow these rules when using fractions:"
+msgstr ""
+
+#: en_US/style.xml:1198(para)
+msgid ""
+"Use numerals for fractions in tables and in units of measurement, but spell "
+"out fractions in prose."
+msgstr ""
+
+#: en_US/style.xml:1204(para)
+msgid ""
+"Use a space between a numeral and a related fraction, if there is a possible "
+"ambiguity. For example: 1 1/2 instead of 11/2."
+msgstr ""
+
+#: en_US/style.xml:1211(para)
+msgid ""
+"If a fraction is used in a compound modifier, insert a hyphen between the "
+"fraction and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1220(term)
+msgid "Gender"
+msgstr ""
+
+#: en_US/style.xml:1222(para)
+msgid "Refer to <xref linkend=\"sn-fundamentals-9\"/>."
+msgstr ""
+
+#: en_US/style.xml:1228(term)
+msgid "Grammar"
+msgstr ""
+
+#: en_US/style.xml:1230(para)
+msgid ""
+"Use standard American English grammar rules, refer to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\"> http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1241(para)
+msgid "Use the following capitalization rules in headings:"
+msgstr ""
+
+#: en_US/style.xml:1246(para)
+msgid "Initial uppercase letter of the first word"
+msgstr ""
+
+#: en_US/style.xml:1251(para)
+msgid "Initial uppercase letter for all nouns, adjectives, and verbs."
+msgstr ""
+
+#: en_US/style.xml:1257(para)
+msgid ""
+"All lowercase letters for conjunctions, articles, and prepositions of fewer "
+"than four letters"
+msgstr ""
+
+#: en_US/style.xml:1263(para)
+msgid "Initial uppercase letter for prepositions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1269(para)
+msgid "Initial uppercase letter for conjunctions of four letters or longer"
+msgstr ""
+
+#: en_US/style.xml:1280(term)
+msgid "Hyphen"
+msgstr ""
+
+#: en_US/style.xml:1282(para)
+msgid "Use hyphens in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1287(para)
+msgid "With a numeral in a compound modifier"
+msgstr ""
+
+#: en_US/style.xml:1291(para)
+msgid "To prevent ambiguity"
+msgstr ""
+
+#: en_US/style.xml:1296(para)
+msgid ""
+"With some standard prefixes and suffixes. Use the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>) for guidance"
+msgstr ""
+
+#: en_US/style.xml:1305(para)
+msgid "In spelled-out fractions"
+msgstr ""
+
+#: en_US/style.xml:1310(para)
+msgid ""
+"In variable names of two or more words, such as <replaceable>directory-name</"
+"replaceable>. Note: <replaceable>filename</replaceable> is an exception."
+msgstr ""
+
+#: en_US/style.xml:1317(para)
+msgid "Do not use hyphens in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1322(para)
+msgid "For industry-accepted terms"
+msgstr ""
+
+#: en_US/style.xml:1327(para)
+msgid "To construct verbs"
+msgstr ""
+
+#: en_US/style.xml:1332(para)
+msgid "With an adverb ending in <emphasis>ly</emphasis>"
+msgstr ""
+
+#: en_US/style.xml:1337(para)
+msgid "With numerals as single modifiers"
+msgstr ""
+
+#: en_US/style.xml:1342(para)
+msgid ""
+"With a word that is listed as unhyphenated in the <citetitle>American "
+"Heritage Dictionary</citetitle> (<ulink url=\"http://www.bartleby.com/61/"
+"\">http://www.bartleby.com/61/</ulink>), and that uses a common prefix"
+msgstr ""
+
+#: en_US/style.xml:1351(para)
+msgid "With trademarked terms"
+msgstr ""
+
+#: en_US/style.xml:1359(term)
+msgid "Latin terms"
+msgstr ""
+
+#: en_US/style.xml:1361(para)
+msgid "Do not use Latin terms. Use an equivalent English term instead."
+msgstr ""
+
+#: en_US/style.xml:1368(term)
+msgid "Like"
+msgstr ""
+
+#: en_US/style.xml:1370(para)
+msgid ""
+"Do not use the term <emphasis>like</emphasis> to denote equivalence or "
+"similarity."
+msgstr ""
+
+#: en_US/style.xml:1377(term)
+msgid "Lists"
+msgstr ""
+
+#: en_US/style.xml:1379(para)
+msgid "Introduce a list with a complete sentence that ends with a colon."
+msgstr ""
+
+#: en_US/style.xml:1386(term)
+msgid "Numbers"
+msgstr ""
+
+#: en_US/style.xml:1388(para)
+msgid "Spell out numbers in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1393(para)
+msgid ""
+"Numbers from zero through nine unless the number is part of a measurement"
+msgstr ""
+
+#: en_US/style.xml:1398(para)
+msgid "Approximations"
+msgstr ""
+
+#: en_US/style.xml:1403(para)
+msgid ""
+"Extreme values such as <emphasis>million</emphasis>, but precede the value "
+"with a numeral"
+msgstr ""
+
+#: en_US/style.xml:1409(para)
+msgid "Any number that begins a sentence"
+msgstr ""
+
+#: en_US/style.xml:1414(para)
+msgid ""
+"A number that is immediately followed by a numeral, for example: "
+"<literal>two 10 MB files</literal>"
+msgstr ""
+
+#: en_US/style.xml:1423(term)
+msgid "Numerals"
+msgstr ""
+
+#: en_US/style.xml:1425(para)
+msgid "Use numerals in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1430(para)
+msgid "The number 10 or greater"
+msgstr ""
+
+#: en_US/style.xml:1435(para)
+msgid "Negative numbers"
+msgstr ""
+
+#: en_US/style.xml:1439(para)
+msgid "Most fractions"
+msgstr ""
+
+#: en_US/style.xml:1444(para)
+msgid "Percentages"
+msgstr ""
+
+#: en_US/style.xml:1449(para)
+msgid "Decimals"
+msgstr ""
+
+#: en_US/style.xml:1454(para)
+msgid "Measurements"
+msgstr ""
+
+#: en_US/style.xml:1459(para)
+msgid "Units of time smaller than one second"
+msgstr ""
+
+#: en_US/style.xml:1464(para)
+msgid "References to bits and bytes"
+msgstr ""
+
+#: en_US/style.xml:1472(term)
+msgid "Parentheses"
+msgstr ""
+
+#: en_US/style.xml:1474(para)
+msgid "Use parentheses in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1479(para)
+msgid ""
+"To contain the abbreviation of a term on the first occurrence of the full "
+"term"
+msgstr ""
+
+#: en_US/style.xml:1485(para)
+msgid "In man page references, specifically the section number"
+msgstr ""
+
+#: en_US/style.xml:1493(term)
+msgid "Period"
+msgstr ""
+
+#: en_US/style.xml:1495(para)
+msgid "Use a period in the following situations:"
+msgstr ""
+
+#: en_US/style.xml:1500(para)
+msgid "To end a sentence"
+msgstr ""
+
+#: en_US/style.xml:1505(para)
+msgid "In file and directory names"
+msgstr ""
+
+#: en_US/style.xml:1510(para)
+msgid "In abbreviations that can be mistaken for words, such as a.m. and U.S."
+msgstr ""
+
+#: en_US/style.xml:1519(term)
+msgid "Punctuation"
+msgstr ""
+
+#: en_US/style.xml:1521(para)
+msgid ""
+"Use standard American English punctuation rules. In addition to the specific "
+"points of punctuation in this section, refer also to the <citetitle>Chicago "
+"Manual of Style</citetitle> (<ulink url=\"http://www.press.uchicago.edu/Misc/"
+"Chicago/cmosfaq/cmosfaq.html\">http://www.press.uchicago.edu/Misc/Chicago/"
+"cmosfaq/cmosfaq.html</ulink>.)"
+msgstr ""
+
+#: en_US/style.xml:1531(term)
+msgid "Punctuation in numbers"
+msgstr ""
+
+#: en_US/style.xml:1533(para)
+msgid ""
+"Do not use a comma in numerals of four digits. Use a comma in numerals of "
+"more than four digits."
+msgstr ""
+
+#: en_US/style.xml:1540(term)
+msgid "Quotation marks"
+msgstr ""
+
+#: en_US/style.xml:1542(para)
+msgid ""
+"Use quotation marks to indicate material that is taken verbatim from another "
+"source. Do not use quotation marks to excuse terms from legitimacy. If the "
+"term is not legitimate, then use another term. If you must use that term, "
+"declare the term in the glossary and make the term legitimate."
+msgstr ""
+
+#: en_US/style.xml:1553(term)
+msgid "See v. Refer to"
+msgstr ""
+
+#: en_US/style.xml:1555(para)
+msgid ""
+"When referring a user to another resource, use \"refer to\" instead of \"see"
+"\", and \"refer also to\" instead of \"see also\". This differentiates from "
+"the <sgmltag class=\"starttag\">see</sgmltag> and <sgmltag class=\"starttag"
+"\">seealso</sgmltag> tags that are used in indexing. These tags create "
+"special links in the index. To be consistent throughout the document, we "
+"reserve the special words \"see\" and \"see also\" for hyperlinked index "
+"references, and use \"refer to\" and \"refer also to\" for non-hyperlinked "
+"and non-indexed references."
+msgstr ""
+
+#: en_US/style.xml:1570(term)
+msgid "Semicolon"
+msgstr ""
+
+#: en_US/style.xml:1572(para)
+msgid "Do not use semicolons."
+msgstr ""
+
+#: en_US/style.xml:1578(term)
+msgid "Slash"
+msgstr ""
+
+#: en_US/style.xml:1580(para)
+msgid ""
+"Except where required as part of a filename, do not use slashes \"/\" in "
+"your writing. The construction <literal>and/or</literal>, for example, does "
+"not exist. Use one or the other term instead."
+msgstr ""
+
+#: en_US/style.xml:1589(term)
+msgid "Spelling"
+msgstr ""
+
+#: en_US/style.xml:1591(para)
+msgid ""
+"Use standard American English spelling rules, refer to the "
+"<citetitle>American Heritage Dictionary</citetitle> (<ulink url=\"http://www."
+"bartleby.com/61/\">http://www.bartleby.com/61/</ulink>) for guidelines."
+msgstr ""
+
+#: en_US/style.xml:1600(term)
+msgid "Titles"
+msgstr ""
+
+#: en_US/style.xml:1602(para)
+msgid "For manual titles use the same rules as for headings."
+msgstr ""
+
+#: en_US/style.xml:1608(term)
+msgid "Units"
+msgstr ""
+
+#: en_US/style.xml:1610(para)
+msgid "Follow these rules when using units:"
+msgstr ""
+
+#: en_US/style.xml:1615(para)
+msgid ""
+"Use standard abbreviations for units of measurements, do not invent your own "
+"abbreviations."
+msgstr ""
+
+#: en_US/style.xml:1621(para)
+msgid ""
+"For further guidelines, refer to the <citetitle>IEEE Standard Dictionary of "
+"Electrical and Electronics Terms</citetitle>."
+msgstr ""
+
+#: en_US/style.xml:1630(para)
+msgid "Use periods for abbreviated units that might be mistaken for a word."
+msgstr ""
+
+#: en_US/style.xml:1636(para)
+msgid ""
+"Most standard abbreviations of units account for both singular and plural "
+"usage."
+msgstr ""
+
+#: en_US/style.xml:1642(para)
+msgid "Insert a space between the numeral and the unit of measurement."
+msgstr ""
+
+#: en_US/style.xml:1656(title)
+msgid "Composition Tips"
+msgstr ""
+
+#. This section will collect miscellanea and advice for specific
+#. situations that the FDP editors encounter. I hope they will feel
+#. free to e-mail me sticky situations or particularly interesting
+#. examples of work they've beautified. Hopefully not too much will be
+#. drawn from my own work! - PWF.
+#: en_US/style.xml:1668(para)
+msgid ""
+"This section contains usage tips based on situations the Fedora "
+"Documentation Project editors have encountered in the past. You should read "
+"and understand these examples to improve your own documentation. The Fedora "
+"Documentation Project editors welcome additional examples."
+msgstr ""
+
+#: en_US/style.xml:1676(title)
+msgid "Active Voice"
+msgstr ""
+
+#: en_US/style.xml:1677(para)
+msgid ""
+"Always use active voice, except when it is awkward to do so. The tutorial "
+"tells the user how to accomplish a task, and should give instructions "
+"clearly and concisely. Avoid using \"must,\" \"need to,\" and the like. "
+"These words are redundant in a tutorial, since the reader assumes you are "
+"outlining necessary steps to accomplish a task. Also avoid using \"maybe,\" "
+"\"might,\" and other words that indicate you are unsure about the subject "
+"matter. Your tutorial should cover a subject authoritatively. The reader "
+"should never be concerned about unknown effects of following the tutorial."
+msgstr ""
+
+#: en_US/style.xml:1690(title)
+msgid "Incorrect: Passive voice"
+msgstr ""
+
+#: en_US/style.xml:1691(para)
+msgid "The <command>yum update</command> command must be run."
+msgstr ""
+
+#: en_US/style.xml:1694(para)
+msgid "You might want to run the <command>yum update</command> command."
+msgstr ""
+
+#: en_US/style.xml:1700(title)
+msgid "Correct: Active voice"
+msgstr ""
+
+#: en_US/style.xml:1701(para)
+msgid "Run the <command>yum update</command> command."
+msgstr ""
+
+#: en_US/style.xml:1708(title)
+msgid "Present Tense"
+msgstr ""
+
+#: en_US/style.xml:1709(para)
+msgid ""
+"Write in the present tense. A good rule of thumb is that the words \"will\" "
+"and \"shall\" are almost never needed in describing what the user should do "
+"or see. They add unnecessary length to sentences and can confuse "
+"translators. They are also often indicators of passive voice; refer also to "
+"<xref linkend=\"sn-misc-active-voice\"/>."
+msgstr ""
+
+#: en_US/style.xml:1718(title)
+msgid "Incorrect: Future tense"
+msgstr ""
+
+#: en_US/style.xml:1719(para)
+msgid "The application will display a list of target files."
+msgstr ""
+
+#: en_US/style.xml:1722(para)
+msgid "A list of target files will be displayed by the application."
+msgstr ""
+
+#: en_US/style.xml:1727(title)
+msgid "Correct: Present tense"
+msgstr ""
+
+#: en_US/style.xml:1728(para)
+msgid "The application displays a list of target files."
+msgstr ""
+
+#: en_US/style.xml:1735(title)
+msgid "Narrative Voice"
+msgstr ""
+
+#: en_US/style.xml:1736(para)
+msgid ""
+"Do not use the first person \"I,\" \"we,\" or \"us\" to refer to yourself "
+"the writer (whether including the reader or not), the Fedora Documentation "
+"Project, the Fedora community, or any other group. Do not refer to users "
+"with a third person pronoun (\"he,\" \"she,\" or \"he or she\") or the word "
+"\"one.\" It is acceptable to refer to the reader with the second person "
+"pronoun \"you.\""
+msgstr ""
+
+#: en_US/style.xml:1745(title)
+msgid "Incorrect: First or third person"
+msgstr ""
+
+#: en_US/style.xml:1746(para)
+msgid ""
+"As described in the last section, I always run <command>up2date</command> "
+"before configuring the Samba server."
+msgstr ""
+
+#: en_US/style.xml:1751(para)
+msgid ""
+"If the user needs to back up his or her files, s/he should use the "
+"<command>tar</command> or <command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1757(title)
+msgid "Correct: Second (or no) person"
+msgstr ""
+
+#: en_US/style.xml:1758(para)
+msgid ""
+"Refer to the section on <command>up2date</command> before configuring the "
+"Samba server."
+msgstr ""
+
+#: en_US/style.xml:1762(para)
+msgid ""
+"If necessary, users can back up files with the <command>tar</command> or "
+"<command>cpio</command> command."
+msgstr ""
+
+#: en_US/style.xml:1770(title)
+msgid "Negative Words"
+msgstr ""
+
+#: en_US/style.xml:1771(para)
+msgid ""
+"Avoid negative words when possible, since they give documentation an overly "
+"dogmatic tone. The word \"avoid\" is useful for this purpose. Note that "
+"contractions are often used for negative words such as <emphasis>don't</"
+"emphasis> or <emphasis>can't</emphasis>. Refer to <xref linkend=\"vle-"
+"contractions\"/>."
+msgstr ""
+
+#: en_US/style.xml:1782(title)
+msgid "Uncertainty"
+msgstr ""
+
+#: en_US/style.xml:1783(para)
+msgid ""
+"Avoid overuse of \"typically,\" \"usually,\" \"most of,\" \"many,\" and the "
+"like. While occasional use of these constructions is acceptable, overuse "
+"reduces the authority of your documentation. The documentation should "
+"adequately cover a stock installation of Fedora. It is impossible for a "
+"tutorial-length document to cover every possible configuration scenario. "
+"Address the most common scenarios and note discrepancies only as required."
+msgstr ""
+
+#: en_US/style.xml:1795(title)
+msgid "Redundant Coverage"
+msgstr ""
+
+#: en_US/style.xml:1796(para)
+msgid ""
+"Avoid covering redundant material, such as how to update a Fedora system. "
+"These overarching topics may be covered in other tutorials. Writers "
+"frequently violate this guideline because they feel their tutorial is not "
+"long enough. Keep your tutorial from wandering off-topic. Instead, refer the "
+"reader to a separate tutorial whenever possible for complete coverage of "
+"that topic."
+msgstr ""
+
+#: en_US/style.xml:1808(title)
+msgid "Self-referential Value Judgments"
+msgstr ""
+
+#: en_US/style.xml:1809(para)
+msgid ""
+"Avoid statements such as \"One of the most important things to do is "
+"<replaceable>XYZ</replaceable>.\" If the procedure is important, the reader "
+"already expects it to be in your tutorial. The converse is also true: If a "
+"procedure appears in your tutorial, the reader expects it is important. This "
+"is especially true if you use a whole section for the procedure in question. "
+"Merely state, \"Do <replaceable>XYZ</replaceable>.\" Then elaborate as "
+"required. If the whole section concerns how to do <replaceable>XYZ</"
+"replaceable>, leave this sentence out entirely. Refer also to <xref linkend="
+"\"vle-golden-rule-4\"/>."
+msgstr ""
+
+#: en_US/style.xml:1824(title)
+msgid "Precision of Language"
+msgstr ""
+
+#: en_US/style.xml:1825(para)
+msgid ""
+"Use precise words for actions users should take. Do not instruct users to "
+"\"go\" to a selection, or \"find\" a menu."
+msgstr ""
+
+#: en_US/style.xml:1830(title)
+msgid "Incorrect: Imprecise wording"
+msgstr ""
+
+#: en_US/style.xml:1833(para)
+msgid ""
+"Go to the <guimenu>Main Menu</guimenu> -> <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+
+#: en_US/style.xml:1839(para)
+msgid "Find the option labeled <guilabel>Search</guilabel>"
+msgstr ""
+
+#: en_US/style.xml:1846(title)
+msgid "Correct: Precise wording"
+msgstr ""
+
+#: en_US/style.xml:1849(para)
+msgid ""
+"From the <guimenu>Main Menu</guimenu>, select <guimenuitem>Foobar</"
+"guimenuitem>"
+msgstr ""
+
+#: en_US/style.xml:1855(para)
+msgid "Select the <guilabel>Search</guilabel> option"
+msgstr ""
+
+#: en_US/style.xml:1862(title)
+msgid "Do Not Discriminate Against Non-GUI Users"
+msgstr ""
+
+#: en_US/style.xml:1863(para)
+msgid ""
+"If you are writing about a GUI-only application, you may use \"click\" "
+"freely. If you are writing about an application that has a text-mode "
+"interface, use \"select\" instead as shown above."
+msgstr ""
+
+#: en_US/style.xml:1874(title)
+msgid "DocBook Tips"
+msgstr ""
+
+#: en_US/style.xml:1875(para)
+msgid ""
+"This section contains tips on how to use DocBook tags more effectively in "
+"your documentation."
+msgstr ""
+
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:268(title)
+msgid "Admonitions"
+msgstr ""
+
+#: en_US/style.xml:1882(para)
+msgid ""
+"Avoid overuse of admonitions. Keep admonitions short and effective by using "
+"only the most important material inside the admonition. Move any background "
+"material required to explain the admonition statements outside the "
+"admonition. Use a short but descriptive title for an admonition. Use title "
+"case for the admonition title."
+msgstr ""
+
+#: en_US/style.xml:1891(title)
+msgid "Incorrect: Lengthy admonition"
+msgstr ""
+
+#: en_US/style.xml:1894(title)
+msgid "Use <command>sfdisk</command> to check input"
+msgstr ""
+
+#: en_US/style.xml:1895(para)
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1909(title)
+msgid "Correct: Brief admonition"
+msgstr ""
+
+#: en_US/style.xml:1917(title)
+msgid "Check Input"
+msgstr ""
+
+#: en_US/style.xml:1918(para)
+msgid ""
+"Always use the <command>sfdisk -n</command> command to check your input file "
+"before writing to the disk."
+msgstr ""
+
+#: en_US/style.xml:1910(para)
+msgid ""
+"The <command>sfdisk</command> command accepts a script file as standard "
+"input to set up partitions on a hard disk. Sometimes <command>sfdisk</"
+"command> will simply reject an erroneous input file. In other cases, it will "
+"use the input verbatim, writing an incorrect partition table to your disk. "
+"<placeholder-1/>"
+msgstr ""
+
+#: en_US/style.xml:1925(para)
+msgid ""
+"Avoid punctuation in titles for sections or admonitions, except for commas "
+"only where demanded. Use a title that says something about the admonition "
+"comment, such as \"Reboot Required,\" instead of simply using the admonition "
+"type for a title (\"Note\")."
+msgstr ""
+
+#: en_US/style.xml:1932(para)
+msgid ""
+"Follow the capitalization rules for headings in the title of an admonition."
+msgstr ""
+
+#: en_US/style.xml:1939(title)
+msgid "The <sgmltag class=\"starttag\">replaceable</sgmltag> Tag"
+msgstr ""
+
+#: en_US/style.xml:1941(para)
+msgid ""
+"If your documentation formally states a specific value will be used as a "
+"convention, do not use the <sgmltag class=\"starttag\">replaceable</sgmltag> "
+"tag in your text or examples."
+msgstr ""
+
+#: en_US/style.xml:1950(title)
+msgid "XML Entities"
+msgstr ""
+
+#: en_US/style.xml:1951(para)
+msgid ""
+"Use the entities provided by the Fedora Documentation Project. These "
+"entities are found in the <filename>common/</filename> folder in the "
+"<filename>fedora-docs</filename> distribution. (Refer also to <xref linkend="
+"\"ch-getting-files\"/>.) For instance, do not use abbreviations such as "
+"\"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" "
+"which produces the text \"Fedora 9.\""
+msgstr ""
+
+#: en_US/writing-guidelines.xml:11(title)
+msgid "Fedora Documentation Guidelines"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:14(primary)
+#: en_US/writing-guidelines.xml:15(see)
+msgid "recursion"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:19(primary)
+#: en_US/writing-guidelines.xml:26(secondary)
+msgid "RTFM"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:20(secondary)
+msgid "read the fine manual"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:21(seealso)
+#: en_US/writing-guidelines.xml:25(primary)
+msgid "humor"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:29(para)
+#, fuzzy
+msgid ""
+"Please read this chapter carefully. This chapter describes the guidelines "
+"that must be followed such as naming conventions."
+msgstr ""
+"请仔细阅读这一章。这一章描述了 Docs Project 使用的标记。一些规则是 Docs "
+"Project 特定的。"
+
+#: en_US/writing-guidelines.xml:32(para)
+msgid ""
+"This chapter only discusses tags used for documentation for the Fedora "
+"Project, not all available DocBook XML tags. For the complete list, refer to "
+"<ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:38(title)
+msgid "File Header"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:40(title)
+#, fuzzy
+msgid "XML Header"
+msgstr "nXML 模式"
+
+#: en_US/writing-guidelines.xml:41(para)
+msgid ""
+"In accordance with good XML practices, the first line in any DocBook XML "
+"source files should identify the file as XML. Use the following line as the "
+"first line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:47(title)
+msgid "CVS Id Header"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:48(para)
+msgid ""
+"All the files must contain the CVS Id header. Use the following line as the "
+"second line of any new XML file:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:51(para)
+msgid ""
+"Any time the file is committed to CVS, the line is updated automatically to "
+"include information about the file. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:58(title)
+msgid "ID Naming Conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:61(primary)
+#: en_US/writing-guidelines.xml:74(primary)
+#: en_US/writing-guidelines.xml:275(primary)
+#: en_US/writing-guidelines.xml:280(primary)
+#: en_US/writing-guidelines.xml:285(primary)
+#: en_US/writing-guidelines.xml:290(primary)
+#: en_US/writing-guidelines.xml:295(primary)
+#: en_US/writing-guidelines.xml:300(primary)
+#: en_US/writing-guidelines.xml:306(primary)
+#: en_US/writing-guidelines.xml:312(primary)
+#: en_US/writing-guidelines.xml:318(primary)
+#: en_US/writing-guidelines.xml:324(primary)
+#: en_US/writing-guidelines.xml:350(primary)
+#: en_US/writing-guidelines.xml:355(primary)
+#: en_US/writing-guidelines.xml:360(primary)
+#: en_US/writing-guidelines.xml:365(primary)
+#: en_US/writing-guidelines.xml:370(primary)
+msgid "XML tags"
+msgstr "XML 标记"
+
+#: en_US/writing-guidelines.xml:62(secondary)
+#: en_US/writing-guidelines.xml:66(primary)
+#: en_US/writing-guidelines.xml:79(primary)
+msgid "naming conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:69(para)
+msgid ""
+"This section explains the ID naming convention. IDs are unique identifiers "
+"that allow DocBook XML to cross-reference a section, chapter, or other "
+"element."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:75(secondary)
+#: en_US/writing-guidelines.xml:80(secondary)
+msgid "rules for defining an ID"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:83(para)
+#, fuzzy
+msgid "The following general rules apply to IDs:"
+msgstr "translator-credits"
+
+#: en_US/writing-guidelines.xml:87(para)
+msgid "Keep an ID as short and simple as possible."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:90(para)
+msgid ""
+"Start the ID with the special short two-character label. This makes URLs and "
+"other references to this ID human readable, by self-identifying the XML "
+"container type."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:96(para)
+msgid ""
+"<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used "
+"properly."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:102(title)
+msgid "Proper ID Usage"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:111(title)
+msgid "Two-Character Naming Conventions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:112(segtitle)
+msgid "Tag"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:113(segtitle)
+msgid "Prefix"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:115(sgmltag)
+msgid "preface"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:116(literal)
+msgid "pr-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:119(sgmltag)
+msgid "chapter"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:120(literal)
+msgid "ch-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:123(sgmltag)
+msgid "section"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:124(literal)
+msgid "sn-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:127(sgmltag)
+msgid "figure"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:128(literal)
+msgid "fig-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:131(sgmltag)
+#: en_US/writing-guidelines.xml:235(sgmltag)
+msgid "table"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:132(literal)
+msgid "tb-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:135(sgmltag)
+msgid "appendix"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:136(literal)
+msgid "ap-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:139(sgmltag)
+msgid "part"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:140(literal)
+msgid "pt-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:143(sgmltag)
+msgid "example"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:144(literal)
+msgid "ex-"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:148(para)
+msgid ""
+"Use the title of the item as the ID. Make your titles unique within a "
+"document to prevent conflicts. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:157(title)
+#, fuzzy
+msgid "XML Tags"
+msgstr "XML 标记"
+
+#: en_US/writing-guidelines.xml:159(primary)
+msgid "xml tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:160(secondary)
+msgid "caveats"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:163(para)
+msgid ""
+"It is very important that you remember the caveats in this section. These "
+"are learned suggestions or rules that make your XML experience better."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:171(term)
+msgid "Do Not Use Trademark Entities"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:173(para)
+msgid ""
+"Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+"\"genentity\">reg</sgmltag> because the do not produce HTML output that "
+"works for all charsets. The HTML output produces by these entities are "
+"declared in the DTD and cannot be changed via the stylesheet."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:181(para)
+msgid ""
+"Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes "
+"as follows:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:184(segtitle)
+#, fuzzy
+msgid "DocBook XML source"
+msgstr "DocBook XML 标记"
+
+#: en_US/writing-guidelines.xml:185(segtitle)
+msgid "Rendered content"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:189(trademark)
+msgid "trademark symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:196(trademark)
+msgid "registered trademark symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:202(trademark)
+msgid "copyright symbol after me"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:209(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:211(para)
+msgid ""
+"In general, use <sgmltag>para</sgmltag> tags around anything other than a "
+"simple paragraph. Doing so will create additional white space within the "
+"text itself in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:216(para)
+msgid ""
+"Specifically, do not use <sgmltag>para</sgmltag> tags around the following "
+"(or, to put this another way, do not embed the following within <sgmltag "
+"class=\"element\">para</sgmltag> elements):"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:223(sgmltag)
+msgid "screen"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:226(sgmltag)
+msgid "itemizedlist"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:229(sgmltag)
+msgid "orderedlist"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:232(sgmltag)
+msgid "variablelist"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:241(term)
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag>listitem</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:244(para)
+msgid ""
+"Content inside <sgmltag class=\"element\">para</sgmltag> elements within "
+"<sgmltag class=\"element\">listitem</sgmltag> elements <emphasis>must</"
+"emphasis> start immediately after the beginning <sgmltag class=\"starttag"
+"\">para</sgmltag> tag to avoid extra white space in the PDF version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:252(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:254(para)
+msgid ""
+"The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag"
+"\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis> be flush left in the XML file; otherwise, the "
+"extraneous whitespace will appear in the HTML version."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:301(secondary)
+#: en_US/writing-guidelines.xml:307(secondary)
+#: en_US/writing-guidelines.xml:313(secondary)
+#: en_US/writing-guidelines.xml:319(secondary)
+#: en_US/writing-guidelines.xml:325(secondary)
+msgid "admonitions"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:276(secondary)
+#: en_US/writing-guidelines.xml:302(tertiary)
+#: en_US/writing-guidelines.xml:371(secondary)
+msgid "warning"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:281(secondary)
+#: en_US/writing-guidelines.xml:308(tertiary)
+#: en_US/writing-guidelines.xml:356(secondary)
+#, fuzzy
+msgid "tip"
+msgstr "技巧"
+
+#: en_US/writing-guidelines.xml:286(secondary)
+#: en_US/writing-guidelines.xml:314(tertiary)
+#: en_US/writing-guidelines.xml:351(secondary)
+msgid "note"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:291(secondary)
+#: en_US/writing-guidelines.xml:320(tertiary)
+#: en_US/writing-guidelines.xml:361(secondary)
+msgid "caution"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:296(secondary)
+#: en_US/writing-guidelines.xml:326(tertiary)
+#: en_US/writing-guidelines.xml:366(secondary)
+#, fuzzy
+msgid "important"
+msgstr "注意"
+
+#: en_US/writing-guidelines.xml:329(para)
+msgid ""
+"There are five types of admonitions in DocBook: <sgmltag class=\"element"
+"\">caution</sgmltag>, <sgmltag class=\"element\">important</sgmltag>, "
+"<sgmltag class=\"element\">note</sgmltag>, <sgmltag class=\"element\">tip</"
+"sgmltag>, and <sgmltag class=\"element\">warning</sgmltag>. All of the "
+"admonitions have the same structure: an optional <sgmltag class=\"element"
+"\">title</sgmltag> followed by paragraph-level elements. The DocBook DTD "
+"does not impose any specific semantics on the individual admonitions. For "
+"example, DocBook does not mandate that a <sgmltag class=\"element\">warning</"
+"sgmltag> is reserved for cases where bodily harm can result."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:343(title)
+msgid ""
+"Creating a <sgmltag class=\"element\">note</sgmltag>, <sgmltag class="
+"\"element\">tip</sgmltag>, <sgmltag class=\"element\">caution</sgmltag>, "
+"<sgmltag class=\"element\">important</sgmltag>, or <sgmltag class=\"element"
+"\">warning</sgmltag>"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:374(para)
+msgid ""
+"There are several ways to bring attention to text within a document. A "
+"<emphasis><sgmltag class=\"element\">note</sgmltag></emphasis> is used to "
+"bring additional information to the users' attention. A <emphasis><sgmltag "
+"class=\"element\">tip</sgmltag></emphasis> is used to show the user helpful "
+"information or another way to do something. A <emphasis><sgmltag class="
+"\"element\">caution</sgmltag></emphasis> is used to show the user they must "
+"be careful when attempting a certain step. An <emphasis><sgmltag class="
+"\"element\">important</sgmltag></emphasis> tag set can be used to show the "
+"user a piece of information that should not be overlooked. While this "
+"information may not change anything the user is doing, it should show the "
+"user that this piece of information could be vital. A <emphasis><sgmltag "
+"class=\"element\">warning</sgmltag></emphasis> is used to show the reader "
+"that their current setup will change or be altered, such as files being "
+"removed, and they should not choose this operation unless they are alright "
+"with the consequences."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:394(para)
+msgid ""
+"The following lines of code show the basic setup for each case mentioned "
+"above, along with its appearance in HTML."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:403(title) en_US/emacs.xml:257(title)
+#: en_US/emacs.xml:562(title) en_US/emacs-nxml.xml:160(title)
+msgid "Note"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:404(para)
+#: en_US/writing-guidelines.xml:424(para)
+#: en_US/writing-guidelines.xml:434(para)
+#: en_US/writing-guidelines.xml:444(para)
+msgid "Body of text goes here."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:413(title) en_US/emacs-nxml.xml:114(title)
+msgid "Tip"
+msgstr "技巧"
+
+#: en_US/writing-guidelines.xml:414(para)
+msgid "Body of text goes here"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:423(title)
+msgid "Caution"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:433(title) en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr "注意"
+
+#: en_US/writing-guidelines.xml:443(title)
+msgid "Warning"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:451(title)
+msgid "Screenshots"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:454(primary)
+#: en_US/writing-guidelines.xml:459(see) en_US/writing-guidelines.xml:463(see)
+msgid "screenshots"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:455(secondary)
+msgid "how to take"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:458(primary)
+msgid "screen captures"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:462(primary)
+msgid "screen grabs"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:466(para)
+msgid ""
+"Screenshots are illustrations that show the state of a display the user may "
+"encounter. Screenshots can be either graphical or textual. However, "
+"screenshots use a great deal of space in a text document to convey "
+"relatively small amounts of information. The same space in the document can "
+"hold a greater amount of more descriptive and helpful information. "
+"Therefore, authors should avoid screenshots whenever possible in favor of "
+"descriptive text."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:474(para)
+msgid ""
+"One of the isolated instances in which screenshots are useful is to "
+"demonstrate a physical screen layout that is unfamiliar to a reader. "
+"<emphasis>This does not mean that illustrations of dialog boxes are good "
+"uses of screenshots.</emphasis> On the contrary, dialogs are simply "
+"instances of a user interface element with which a reader is already "
+"familiar. An annotated diagram in certain cases, however, explains to the "
+"reader where to find functional landmarks on the screen such as menu bars."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:482(para)
+msgid ""
+"The steps for taking a graphical screenshot illustrate how using text to "
+"describe a procedure is more concise than a series of screenshots."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:487(term)
+msgid "Graphical Screenshot"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:491(para)
+msgid ""
+"Create a new user account to make screenshots. The new account uses the "
+"distribution default theme, fonts, and element sizes. The resulting "
+"screenshot has an appearance familiar to the largest number of readers, and "
+"makes Fedora Documentation Project documents consistent."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:498(para)
+msgid ""
+"Before taking the screenshot, if possible, resize the targeted GUI element"
+"(s) to the smallest possible size. The target image should be 500 pixels "
+"wide or less. If the screenshot includes more than one GUI element, you may "
+"need to resize the screenshot in a following step."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:506(para)
+msgid ""
+"To take the screenshot, select the GUI element with the mouse to bring it to "
+"the forefront, or otherwise arrange the elements. Press "
+"<keycombo><keycap>Alt</keycap><keycap>Print Screen</keycap></keycombo> to "
+"capture a single GUI window. For capturing the entire desktop use "
+"<keycap>Print Screen</keycap>. If the shot includes multiple elements "
+"grouped closely together, crop the resulting PNG format image in "
+"<application>The GIMP</application>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:518(para)
+msgid ""
+"If necessary, resize the image using <application>The GIMP</application>. "
+"Open the image, then right-click on it and choose "
+"<menuchoice><guimenu>Image</guimenu><guimenuitem>Scale Image...</"
+"guimenuitem></menuchoice>. With the chain symbol intact, set the "
+"<guilabel>New Width</guilabel> to <guilabel>500 px</guilabel>, and click "
+"<guibutton>OK</guibutton>. Choose <menuchoice><guimenu>File</"
+"guimenu><guimenuitem>Save</guimenuitem></menuchoice> to save changes to the "
+"image before converting it."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:534(para)
+msgid ""
+"With the image open in <application>The GIMP</application>, right-click the "
+"image, and select <menuchoice><guimenu>File</guimenu><guimenuitem>Save As..."
+"</guimenuitem></menuchoice>. Under <guimenu>Determine File Type:</guimenu>, "
+"select <guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</"
+"guibutton>. Allow flattening of the image by clicking <guibutton>Export</"
+"guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:545(para)
+msgid ""
+"A <guilabel>Save as PostScript</guilabel> window appears. Select "
+"<guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</"
+"guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:559(term)
+msgid "Text Screenshot"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:561(para)
+msgid ""
+"Textual screen information is also useful for readers. Follow these "
+"guidelines for textual screenshots:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:565(para)
+msgid ""
+"If a graphical screenshot illustrates a function, and the textual mode has "
+"identical functions, do not include both, unless omitting either would make "
+"your description unclear."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:571(para)
+msgid ""
+"Make the information generic over specific, and omit any username and "
+"machine information if possible. Do not include the shell prompt unless it "
+"is vital to the demonstration."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:577(para)
+msgid "Separate what the user types from sample command output."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:581(para)
+msgid ""
+"When using <sgmltag class=\"element\">screen</sgmltag> to demonstrate a "
+"procedure, use <sgmltag class=\"element\">userinput</sgmltag> tags to show "
+"what the user types, and use <sgmltag class=\"element\">computeroutput</"
+"sgmltag> tags to show the resulting output."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:589(para)
+msgid ""
+"<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual "
+"screenshot usage."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:594(title)
+msgid "Correct Textual Screenshot (XML Source and HTML)"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:607(para)
+msgid ""
+"To find all the currently active ssh sessions, execute the following command:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:609(userinput)
+#, no-wrap
+msgid "ps ax | grep ssh"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:611(para)
+msgid "Output appears similar to the following:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:613(computeroutput)
+#, no-wrap
+msgid ""
+" 2564 ? S 0:23 /usr/sbin/sshd\n"
+" 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients\n"
+" 8032 pts/0 S 0:00 ssh user@@host.example.com\n"
+" 8032 pts/1 S 0:00 ssh root@@backup.example.com"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:648(title)
+msgid "Previewing Your Work"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:649(para)
+msgid ""
+"The GNOME <application>Help</application> browser, also known as "
+"<command>yelp</command>, and the KDE <application>Khelp</application> "
+"documentation browser can render DocBook XML information as needed. Use "
+"these applications to preview your work if you prefer reading your work in a "
+"browser-like environment. Run the following command:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:656(para)
+msgid ""
+"Make sure to point the preferred help browser at the top parent file of your "
+"XML document. Once the document loads, you can add a bookmark for it for "
+"ease of use later."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:660(title)
+msgid "Using Bookmarks"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:661(para)
+msgid ""
+"Keeping your documents in the same place for every checkout session makes "
+"help browser bookmarks more effective."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:664(para)
+msgid ""
+"Once you have a bookmark stored, it will appear in the help browser at every "
+"use. You can now hit <keycap>F1</keycap> during any GUI session to launch "
+"the help browser. Then choose your bookmark from the menu to preview your "
+"document at any time."
+msgstr ""
+
+#: en_US/module-struct.xml:12(title)
+msgid "How Modules Work"
+msgstr ""
+
+#: en_US/module-struct.xml:13(para)
+msgid ""
+"Documentation modules have a specific structure that enables the "
+"preconfigured tools to work correctly. Follow this structure exactly or you "
+"may have problems building your module. The Fedora Documentation Project "
+"build tools locate resources in the module and use them to build new output "
+"such as HTML or RPM packages."
+msgstr ""
+
+#: en_US/module-struct.xml:19(title)
+msgid "Structure of a Module"
+msgstr ""
+
+#: en_US/module-struct.xml:20(para)
+msgid ""
+"<xref linkend=\"ex-module-structure\"/> shows a directory tree of an example "
+"module, excluding any <filename class=\"directory\">CVS</filename> folders. "
+"Note that this example document does not have branches."
+msgstr ""
+
+#: en_US/module-struct.xml:25(title)
+msgid "Example Module Structure"
+msgstr ""
+
+#: en_US/module-struct.xml:47(title)
+msgid "CVS Module Contents"
+msgstr ""
+
+#: en_US/module-struct.xml:48(segtitle)
+msgid "Component"
+msgstr ""
+
+#: en_US/module-struct.xml:49(segtitle)
+msgid "Type"
+msgstr ""
+
+#: en_US/module-struct.xml:50(segtitle)
+msgid "Usage Notes"
+msgstr ""
+
+#: en_US/module-struct.xml:52(seg)
+msgid "Primary language directory"
+msgstr ""
+
+#: en_US/module-struct.xml:53(seg) en_US/module-struct.xml:94(seg)
+#: en_US/module-struct.xml:101(seg)
+msgid "required"
+msgstr ""
+
+#: en_US/module-struct.xml:56(filename)
+#: en_US/module-struct.xml:181(systemitem)
+msgid "en_US"
+msgstr ""
+
+#: en_US/module-struct.xml:60(firstterm)
+msgid "entities"
+msgstr ""
+
+#: en_US/module-struct.xml:61(para)
+msgid ""
+"Think of an XML entity as a predefined snippet of information. It can "
+"represent a chunk of XML source, or simply a word or character. If the "
+"information changes, it need be replaced only once, in the definition, to "
+"fix all usage."
+msgstr ""
+
+#: en_US/module-struct.xml:54(seg)
+msgid ""
+"This is the only directory absolutely required. It is named for the original "
+"language of the document, such as <placeholder-1/> (US English). The primary "
+"language does not have to be US English; all languages are supported. This "
+"directory contains all the XML source for the actual document, as well as "
+"XML source for document-specific <placeholder-2/><placeholder-3/>."
+msgstr ""
+
+#: en_US/module-struct.xml:69(seg)
+msgid "Graphics directory"
+msgstr ""
+
+#: en_US/module-struct.xml:70(seg) en_US/module-struct.xml:80(seg)
+msgid "optional"
+msgstr ""
+
+#: en_US/module-struct.xml:71(filename) en_US/module-struct.xml:75(filename)
+msgid "figs/"
+msgstr ""
+
+#: en_US/module-struct.xml:71(seg)
+msgid ""
+"The <placeholder-1/> directory is an optional directory where graphics for "
+"the document should be stored. If graphics are screenshots that are "
+"particular to a language, the <placeholder-2/> directory can and should be "
+"stored in a language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:79(seg)
+msgid "Translation (PO) directory"
+msgstr ""
+
+#: en_US/module-struct.xml:81(filename) en_US/module-struct.xml:87(filename)
+msgid "po/"
+msgstr ""
+
+#: en_US/module-struct.xml:83(acronym)
+msgid "PO"
+msgstr ""
+
+#: en_US/module-struct.xml:88(filename)
+msgid "LINGUAS"
+msgstr ""
+
+#: en_US/module-struct.xml:89(firstterm)
+msgid "locales"
+msgstr ""
+
+#: en_US/module-struct.xml:81(seg)
+msgid ""
+"The <placeholder-1/> directory contains specially formatted Portable Object, "
+"or <placeholder-2/>, files created and used by translators. The Fedora "
+"Documentation Project build tools use these files to create translated "
+"versions of documents. The translated documents are not stored in CVS; they "
+"are created as needed from these PO files. The <placeholder-3/> directory "
+"also contains the <placeholder-4/> file, which lists the active translation "
+"<placeholder-5/>, or languages."
+msgstr ""
+
+#: en_US/module-struct.xml:93(seg) en_US/module-struct.xml:95(filename)
+msgid "Makefile"
+msgstr ""
+
+#: en_US/module-struct.xml:95(seg)
+msgid ""
+"The <placeholder-1/> controls the build process. Its content is discussed in "
+"<xref linkend=\"ex-makefile\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:100(filename) en_US/module-struct.xml:102(filename)
+msgid "rpm-info.xml"
+msgstr ""
+
+#: en_US/module-struct.xml:102(seg)
+msgid "The <placeholder-1/> file contains document specific metadata"
+msgstr ""
+
+#: en_US/module-struct.xml:107(title)
+msgid "Common Build Tools"
+msgstr ""
+
+#: en_US/module-struct.xml:108(para)
+msgid ""
+"Never add the <systemitem>docs-common</systemitem> build tools directory to "
+"an individual module. Special formatting in the module list downloads these "
+"tools when a user checks out a document module. For more information, refer "
+"to <xref linkend=\"ch-getting-files-naming-modules\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:116(title)
+msgid "The Document Build System"
+msgstr ""
+
+#: en_US/module-struct.xml:121(para)
+msgid ""
+"In Linux and Fedora documentation, references to commands often include a "
+"number inside parentheses. This number represents the section of "
+"<firstterm>manpages</firstterm> that includes documentation for that "
+"command. To read the manpage for <command>make(1)</command>, use the command "
+"<command>man 1 make</command>."
+msgstr ""
+
+#: en_US/module-struct.xml:117(para)
+msgid ""
+"The build system can render the document into another format such as "
+"<abbrev>HTML</abbrev> or <abbrev>PDF</abbrev>, using <command>make(1)</"
+"command><placeholder-1/> and shell scripts. Authors need <emphasis>no</"
+"emphasis> prior experience with either shell scripts or a <command>make(1)</"
+"command>."
+msgstr ""
+
+#: en_US/module-struct.xml:133(title)
+#, fuzzy
+msgid "The Document <filename>Makefile</filename>"
+msgstr "设置 <filename>.vimrc</filename> 文件"
+
+#: en_US/module-struct.xml:134(para)
+msgid ""
+"Each individual document has its own <filename>Makefile</filename>, which "
+"only needs to be a few lines long. The document <filename>Makefile</"
+"filename> content is designed for cut and paste operations."
+msgstr ""
+
+#: en_US/module-struct.xml:140(para)
+msgid ""
+"<xref linkend=\"ex-makefile\"/> below shows the whole <filename>Makefile</"
+"filename> for a simple document with two files and two translations."
+msgstr ""
+
+#: en_US/module-struct.xml:146(title)
+msgid "Sample Document Makefile"
+msgstr ""
+
+#: en_US/module-struct.xml:162(para)
+msgid ""
+"Do not be concerned with some of the more complicated syntax such as the "
+"<command>XMLFILES_template</command> stanza. An explanation for this "
+"template appears a few paragraphs below."
+msgstr ""
+
+#: en_US/module-struct.xml:168(title)
+msgid "Makefile Variables"
+msgstr ""
+
+#: en_US/module-struct.xml:169(segtitle)
+msgid "Variable"
+msgstr ""
+
+#: en_US/module-struct.xml:170(segtitle) en_US/module-struct.xml:240(segtitle)
+msgid "Explanation"
+msgstr ""
+
+#: en_US/module-struct.xml:172(systemitem)
+msgid "DOCBASE"
+msgstr ""
+
+#: en_US/module-struct.xml:173(seg)
+msgid ""
+"This variable contains the name for the main (parent) XML document. Follow "
+"convention by naming your document after the module name."
+msgstr ""
+
+#: en_US/module-struct.xml:178(systemitem)
+msgid "PRI_LANG"
+msgstr ""
+
+#: en_US/module-struct.xml:179(seg)
+msgid ""
+"This variable contains the ISO code for the original version of the "
+"document, such as <placeholder-1/>."
+msgstr ""
+
+#: en_US/module-struct.xml:184(systemitem)
+msgid "DOC_ENTITIES"
+msgstr ""
+
+#: en_US/module-struct.xml:185(seg)
+msgid ""
+"This variable contains a listing of any files containing entity definitions. "
+"The Fedora Documentation Project uses a special XML format to record "
+"document-specific entities, so they can be translated and built on the fly "
+"like any other XML document. An example is shown later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:194(systemitem)
+msgid "XMLFILES_template"
+msgstr ""
+
+#: en_US/module-struct.xml:197(systemitem)
+msgid "${1}"
+msgstr ""
+
+#: en_US/module-struct.xml:202(systemitem)
+msgid "${1}/"
+msgstr ""
+
+#: en_US/module-struct.xml:195(seg)
+msgid ""
+"This template allows the build tools to work with the document in multiple "
+"languages once it is translated. The <placeholder-1/> marking is a variable "
+"used to substitute the appropriate language. This template is not terribly "
+"complicated. For a new module, duplicate this section exactly except for the "
+"actual filenames. Prepend the text <placeholder-2/>, in place of the "
+"language code directory name, to each filename in your document."
+msgstr ""
+
+#: en_US/module-struct.xml:208(title)
+msgid "Files Exempt From Listing"
+msgstr ""
+
+#: en_US/module-struct.xml:209(para)
+msgid ""
+"Do not include the document-specific entities XML file or the <filename>rpm-"
+"info.xml</filename> file, which will be discussed later in this guide."
+msgstr ""
+
+#: en_US/module-struct.xml:213(para)
+msgid ""
+"The final section, beginning with <literal>define</literal>, locates the "
+"main <filename>Makefile.common</filename> for the build system. This "
+"<filename>Makefile.common</filename> file contains all the <application>make"
+"(1)</application> targets and rules to actually build the document and the "
+"various archives."
+msgstr ""
+
+#: en_US/module-struct.xml:222(title)
+msgid "The Document <filename>rpm-info.xml</filename>"
+msgstr ""
+
+#: en_US/module-struct.xml:223(para)
+msgid ""
+"Each document module's primary language directory contains a file called "
+"<filename>rpm-info.xml</filename>. This file contains document-specific "
+"metadata used to generate revision history, copyright, and contributor "
+"information. It follows a DTD specification included with the rest of the "
+"build system tools."
+msgstr ""
+
+#: en_US/module-struct.xml:232(title)
+msgid "Build System Actions"
+msgstr ""
+
+#: en_US/module-struct.xml:233(para)
+msgid ""
+"To render the <abbrev>XML</abbrev> document into another format, use one of "
+"the following <command>make</command> targets:"
+msgstr ""
+
+#: en_US/module-struct.xml:238(title)
+msgid "Build Targets"
+msgstr ""
+
+#: en_US/module-struct.xml:239(segtitle)
+msgid "Target"
+msgstr ""
+
+#: en_US/module-struct.xml:242(systemitem)
+msgid "help"
+msgstr ""
+
+#: en_US/module-struct.xml:243(seg)
+msgid "This target prints a list of available targets and their descriptions."
+msgstr ""
+
+#: en_US/module-struct.xml:247(systemitem)
+msgid "validate-xml"
+msgstr ""
+
+#: en_US/module-struct.xml:248(firstterm)
+msgid "validates"
+msgstr ""
+
+#: en_US/module-struct.xml:248(seg)
+msgid ""
+"This target <placeholder-1/> the XML files to make sure they are not only "
+"well-formed, but follow the DTD. Some viewers of XML documents may not work "
+"correctly until you run this target. This target includes copying required "
+"entity files so that validating XML viewers work properly"
+msgstr ""
+
+#: en_US/module-struct.xml:256(systemitem)
+msgid "html"
+msgstr ""
+
+#: en_US/module-struct.xml:257(abbrev) en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:293(abbrev) en_US/module-struct.xml:298(abbrev)
+msgid "HTML"
+msgstr ""
+
+#: en_US/module-struct.xml:261(systemitem)
+#: en_US/module-struct.xml:271(systemitem)
+msgid "${DOCBASE}"
+msgstr ""
+
+#: en_US/module-struct.xml:262(systemitem)
+#: en_US/module-struct.xml:272(systemitem)
+msgid "${LANG}"
+msgstr ""
+
+#: en_US/module-struct.xml:260(filename)
+msgid "<placeholder-1/>-<placeholder-2/>/"
+msgstr ""
+
+#: en_US/module-struct.xml:257(seg)
+msgid ""
+"This target builds the \"chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a separate directory named "
+"<placeholder-2/>. Each document section is a separate file within that "
+"directory."
+msgstr ""
+
+#: en_US/module-struct.xml:267(systemitem)
+msgid "html-nochunks"
+msgstr ""
+
+#: en_US/module-struct.xml:270(filename)
+msgid "<placeholder-1/>-<placeholder-2/>.html"
+msgstr ""
+
+#: en_US/module-struct.xml:268(seg)
+msgid ""
+"This target builds the \"non-chunked\" <placeholder-1/> document for each "
+"defined translation. Output is placed in a single file: <placeholder-2/>; no "
+"other files are created."
+msgstr ""
+
+#: en_US/module-struct.xml:276(systemitem)
+msgid "pdf"
+msgstr ""
+
+#: en_US/module-struct.xml:277(abbrev) en_US/module-struct.xml:278(abbrev)
+#: en_US/module-struct.xml:294(abbrev) en_US/module-struct.xml:299(abbrev)
+msgid "PDF"
+msgstr ""
+
+#: en_US/module-struct.xml:277(seg)
+msgid ""
+"This target builds only the <placeholder-1/> document for all document "
+"languages. <placeholder-2/> production is currently erratic and may not work "
+"for your document."
+msgstr ""
+
+#: en_US/module-struct.xml:282(systemitem)
+msgid "tarball"
+msgstr ""
+
+#: en_US/module-struct.xml:283(command)
+msgid "tar(1)"
+msgstr ""
+
+#: en_US/module-struct.xml:283(seg)
+msgid ""
+"This target builds only the <placeholder-1/> archive for all document "
+"languages."
+msgstr ""
+
+#: en_US/module-struct.xml:287(systemitem)
+msgid "all"
+msgstr ""
+
+#: en_US/module-struct.xml:288(seg)
+msgid "This target builds all targets listed above."
+msgstr ""
+
+#: en_US/module-struct.xml:291(systemitem)
+#: en_US/module-struct.xml:300(filename)
+msgid "clean"
+msgstr ""
+
+#: en_US/module-struct.xml:293(emphasis)
+msgid "not"
+msgstr ""
+
+#: en_US/module-struct.xml:292(seg)
+msgid ""
+"This target deletes any temporary, or generated files, but does <placeholder-"
+"1/> erase any <placeholder-2/>, <placeholder-3/>, or archive files."
+msgstr ""
+
+#: en_US/module-struct.xml:297(systemitem)
+msgid "distclean"
+msgstr ""
+
+#: en_US/module-struct.xml:298(seg)
+msgid ""
+"This target erases all <placeholder-1/>, <placeholder-2/>, and archive "
+"files. This target automatically invokes the <placeholder-3/> target as well."
+msgstr ""
+
+#: en_US/module-struct.xml:305(title)
+msgid "PDF Generation is Erratic"
+msgstr ""
+
+#: en_US/module-struct.xml:306(para)
+msgid ""
+"<abbrev>PDF</abbrev> production is currently erratic and may not work for "
+"your document."
+msgstr ""
+
+#: en_US/module-struct.xml:311(title)
+msgid "Adding or Changing Targets"
+msgstr ""
+
+#: en_US/module-struct.xml:312(para)
+msgid ""
+"To add a new target and rules, place them at the bottom of the document "
+"<filename>Makefile</filename>, below the <literal>include</literal> line. "
+"Follow your target definitions with a double colon, not a single colon. The "
+"double colon allows you to specify additional rules for existing targets, or "
+"to write rules for a new target."
+msgstr ""
+
+#: en_US/module-struct.xml:320(para)
+msgid ""
+"For more information on using <command>make(1)</command>, consult the online "
+"documentation with the command <command>info make</command> in a terminal."
+msgstr ""
+
+#: en_US/module-struct.xml:327(title)
+msgid "Using Document Image Files"
+msgstr ""
+
+#: en_US/module-struct.xml:328(para)
+msgid ""
+"Tutorial documents often make use of images such as <filename class="
+"\"extension\">.PNG</filename> files. Store image files in a <filename class="
+"\"directory\">figs/</filename> folder in the main module directory, as shown "
+"in <xref linkend=\"ex-module-structure\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:335(para)
+msgid ""
+"Depending on the output media, sometimes images may be scaled, streteched, "
+"or squashed. To minimize any distortions, we recommend that you use only "
+"<filename class=\"extension\">.PNG</filename> images. Avoid <filename class="
+"\"extension\">.JPG</filename> files. The <command>convert(1)</command> "
+"program, from the <package role=\"rpm\">ImageMagick</package><abbrev>RPM</"
+"abbrev> package, provides a convenient way to reformat <filename class="
+"\"extension\">.JPG</filename> images into <filename class=\"extension\">."
+"PNG</filename> format. For more information on formatting images such as "
+"screenshots, refer to <xref linkend=\"sn-screenshots\"/>."
+msgstr ""
+
+#: en_US/module-struct.xml:349(para)
+msgid ""
+"Image files may be organized into subdirectories under <filename>figs/</"
+"filename> if necessary. The document building system recreates the image "
+"subdirectory structure in the output documents."
+msgstr ""
+
+#: en_US/module-struct.xml:355(para)
+msgid ""
+"Images often contain labels or other text which may need to be localized. A "
+"screenshot of a program, for example, may require a version for each "
+"translated language. Name language-dependent image files such as program "
+"screenshots by adding the language code to the filename, such as "
+"<filename>menu-en_US.png</filename>. Language-independent images, such as "
+"<filename>icon.png</filename>, do not need language codes."
+msgstr ""
+
+#: en_US/module-struct.xml:365(para)
+msgid ""
+"Sometimes, a document may require images that do not follow the naming "
+"convention. To use these images with the document building system, create an "
+"ordinary text file containing the image filenames. This file must be named "
+"<filename>figs/Manifest-</filename><systemitem class=\"macro\">${LANG}</"
+"systemitem> so the build system finds it when searching for image filenames."
+msgstr ""
+
+#: en_US/module-struct.xml:374(para)
+msgid ""
+"<xref linkend=\"ch-getting-files-build-system-manifest\"/> demonstrates one "
+"way to create this <filename>Manifest</filename> file."
+msgstr ""
+
+#: en_US/module-struct.xml:380(title)
+msgid "Building A Manifest"
+msgstr ""
+
+#: en_US/module-struct.xml:387(title)
+msgid "Adding a New DocBook XML File"
+msgstr ""
+
+#: en_US/module-struct.xml:388(para)
+msgid ""
+"To add a new DocBook XML file to an existing document, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:392(para)
+msgid "Place the new DocBook XML file in the primary language directory."
+msgstr ""
+
+#: en_US/module-struct.xml:396(para)
+msgid ""
+"Edit the <filename>Makefile</filename> and add the filename to the "
+"<varname>XMLFILES-${1}</varname> listing. Append a <keycap>\\</keycap> to "
+"the last existing line, and on the next line add an entry for the new file. "
+"Remember to add the <literal>${1}/</literal> prefix as a substitute for the "
+"language directory name."
+msgstr ""
+
+#: en_US/module-struct.xml:406(title)
+msgid "Adding a Translation"
+msgstr ""
+
+#: en_US/module-struct.xml:407(para)
+msgid ""
+"Translations are stored as PO (portable object) files, which the toolchain "
+"transforms into translated documents. Each PO file is based on the POT (PO "
+"template) for the document and translated by the Fedora Translation Project. "
+"To add a translation, follow these steps:"
+msgstr ""
+
+#: en_US/module-struct.xml:414(para)
+msgid ""
+"If the <filename class=\"directory\">po/</filename> directory does not "
+"exist, create it and add it to CVS:"
+msgstr ""
+
+#: en_US/module-struct.xml:420(para)
+msgid "If it does not exist, create the POT file:"
+msgstr ""
+
+#: en_US/module-struct.xml:424(para)
+msgid ""
+"Add the new translation language to the <varname>OTHERS</varname> listing in "
+"the <filename>Makefile</filename>."
+msgstr ""
+
+#: en_US/module-struct.xml:429(para)
+msgid ""
+"Although translators often copy the POT manually to create the new PO file, "
+"the following command also works:"
+msgstr ""
+
+#: en_US/module-struct.xml:432(replaceable)
+msgid "lang"
+msgstr ""
+
+#: en_US/module-struct.xml:432(screen)
+#, no-wrap
+msgid "make po/<placeholder-1/>.po"
+msgstr ""
+
+#: en_US/intro.xml:13(title)
+msgid "Introduction"
+msgstr "介绍"
+
+#: en_US/intro.xml:15(para)
+msgid ""
+"The goal of the Fedora Documentation Project is to create easy-to-follow, "
+"task-based documentation for Fedora users and developers. The Fedora "
+"Documentation Project uses the following tools:"
+msgstr ""
+
+#: en_US/intro.xml:23(para)
+msgid "DocBook XML v4.4"
+msgstr ""
+
+#: en_US/intro.xml:26(para)
+msgid "Custom XSLT stylesheets for both print and HTML versions"
+msgstr ""
+
+#: en_US/intro.xml:30(para)
+msgid "Custom scripts to generate HTML output (use <command>xmlto</command>)"
+msgstr ""
+
+#: en_US/intro.xml:34(para)
+msgid "Emacs with PSGML mode (optional, but recommended)"
+msgstr ""
+
+#: en_US/intro.xml:43(para)
+msgid ""
+"This document explains the tools used by the Fedora Documentation Project. "
+"It provides writing and tagging guidelines to ensure Fedora documentation is "
+"consistent and easy-to-follow."
+msgstr ""
+
+#: en_US/getting-files.xml:12(title)
+msgid "Prerequisites"
+msgstr "先决要求"
+
+#: en_US/getting-files.xml:14(para)
+msgid ""
+"To work on official Fedora documentation you need to install the required "
+"tools. Follow the directions below to configure your system."
+msgstr ""
+"在操作 xmlto docbook-style-xsl docbook-dtds DocBook DTD rpm -q xmlto rpm -q "
+"docbook-style-xsl rpm -q docbook-dtds yum(8) su -c 'yum install xmlto' su -c "
+"'yum install docbook-style-xsl' su -c 'yum install docbook-dtds' Fedora cvs."
+"fedora.redhat.com CVS Enter mkdir my-fedora-docs-sandbox cd my-fedora-docs-"
+"sandbox export CVSROOT=:pserver:anonymous@@cvs.fedora.redhat.com:/cvs/docs "
+"cvs login cvs co docs-common cvs co example-tutorial XML HTML PDF RPM docs-"
+"common cvs co -c ISO US(mydoc-en.xmlmydoc-zh_CN.xml I18N - -) ${LANG} "
+"${LANG} ${LANG} locale( ${LANG} UTF-8 mydoc-it.xml it.UTF-8 I18N HTML PDF "
+"make(1) Makefile MakefileMakefile n Makefile DOCBASE = mydoc LANGUAGES = en "
+"XMLEXTRAFILES-en= include ../docs-common/Makefile.common XML mydoc-en.xml "
+"LANGUAGES en mydoc-en.xmlXMLEXTRAFILES-en include(MakefileMakefile.common "
+"make(1) ${LANG} Makefile${LANG} LANGUAGES XMLEXTRAFILES-${LANG} XML HTML "
+"PDFmake html, make html-nochunk, make pdf all HTML, PDF tar(1) rpm(8) "
+"tarball tar(1) pdf PDF PDF html HTML ${DOCBASE}-${LANG}/ html-nochunks HTML "
+"${DOCBASE}-${LANG}.html clean HTML, PDF, distclean HTML, PDF, clean Makefile "
+"include .PNGfigs/ picture.png mydoc/figs/picture.png PNG JPG convert(1) "
+"ImageMagickRPM JPG figs/ words-en.png words-ru.png picture.png figs/Manifest-"
+"${LANG} figs/Manifest-${LANG} rm -f figs/Manifest-en find figs -print /tmp/"
+"manifest mv /tmp/manifest figs/Manifest-en vi figs/Manifest-en"
+
+#: en_US/getting-files.xml:20(title)
+msgid "System Packages"
+msgstr "translator-credits"
+
+#: en_US/getting-files.xml:22(para)
+msgid ""
+"Install the \"Authoring and Publishing\" package group, which contains "
+"required DocBook XML files, stylesheets and scripts:"
+msgstr ""
+
+#: en_US/getting-files.xml:28(userinput)
+#, no-wrap
+msgid "su -c 'yum groupinstall \"Authoring and Publishing\"'"
+msgstr ""
+
+#: en_US/getting-files.xml:31(para)
+msgid ""
+"Next, install the <filename>cvs</filename> package, which is used to handle "
+"revision control on files in the official repository:"
+msgstr ""
+
+#: en_US/getting-files.xml:37(userinput)
+#, no-wrap
+msgid "su -c 'yum install cvs'"
+msgstr ""
+
+#: en_US/getting-files.xml:40(para)
+msgid ""
+"If you plan to use <application>Emacs</application> to edit DocBook XML "
+"documentation, install <package>psgml</package>, which adds helpful and time-"
+"saving functionality to maximize editing efficiency:"
+msgstr ""
+
+#: en_US/getting-files.xml:44(userinput)
+#, fuzzy, no-wrap
+msgid "su -c 'yum install psgml'"
+msgstr "配置文件"
+
+#: en_US/getting-files.xml:48(title)
+msgid "Fedora Documentation Tools"
+msgstr ""
+
+#: en_US/getting-files.xml:50(para)
+msgid ""
+"The Fedora Documentation Project's custom scripts and stylesheets are stored "
+"in CVS on the <systemitem class=\"fqdomainname\">cvs.fedoraproject.org</"
+"systemitem> CVS server. When you check out a document module from CVS, the "
+"tools are included in the module inside the <filename class=\"directory"
+"\">docs-common/</filename> directory. To work on existing documents in CVS, "
+"refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:59(para)
+msgid ""
+"The most powerful component in the Fedora Documentation Project toolbox is "
+"<firstterm>DocBook XML</firstterm>. DocBook XML is a specific scheme for "
+"authoring technical documentation using <firstterm>Extensible Markup "
+"Language</firstterm>, or <acronym>XML</acronym>. XML allows authors to mark "
+"pieces of content with descriptive tags. The following output is an example "
+"of DocBook XML:"
+msgstr ""
+
+#: en_US/getting-files.xml:76(para)
+msgid ""
+"This example article, entitled <citetitle>A Very Short Article</citetitle>, "
+"consists of only a single paragraph. The tags, or markup, surround elements "
+"of content to define the sense in which they are used. A paragraph, for "
+"example, is marked with <sgmltag>para</sgmltag> tags. Text that requires "
+"emphasis is marked with <sgmltag>emphasis</sgmltag> tags. The author does "
+"not worry about the visual formatting such as italics or font size. Fedora "
+"Documentation Project build tools automatically perform all formatting tasks."
+msgstr ""
+
+#: en_US/getting-files.xml:85(para)
+msgid ""
+"The custom tools built by the Fedora Documentation Project render DocBook "
+"source into a variety of formats for publication and distribution. They also "
+"allow translators to create localized versions of the XML documents for "
+"Fedora users around the world. The flexibility of XML allows for a single "
+"document to be used many times for many purposes, like reusable code for a "
+"programmer."
+msgstr ""
+
+#: en_US/getting-files.xml:91(para)
+msgid ""
+"DocBook is itself very well documented. For more information about DocBook, "
+"visit <ulink url=\"http://www.docbook.org/\"/>. The DocBook site also "
+"features complete copies of <citetitle>DocBook: The Definitive Guide</"
+"citetitle> to browse and download, the canonical source for DocBook "
+"information."
+msgstr ""
+
+#: en_US/getting-files.xml:97(title)
+#, fuzzy
+msgid "DocBook XML Versions"
+msgstr "DocBook XML 标记"
+
+#: en_US/getting-files.xml:98(para)
+msgid ""
+"DocBook XML, like a computer program, has version numbers. The version used "
+"by Fedora Documentation Project right now is 4.4. The DocBook web site may "
+"document a slightly newer version, but the majority of the schema still "
+"applies."
+msgstr ""
+
+#: en_US/getting-files.xml:103(para)
+msgid ""
+"Contributors who use the Microsoft Windows operating system can still make "
+"use of DocBook tools. For more information, refer to <ulink url=\"http://www."
+"codeproject.com/winhelp/docbook_howto.asp\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:110(title)
+msgid "Naming Conventions"
+msgstr ""
+
+#: en_US/getting-files.xml:111(para)
+msgid ""
+"The Fedora Documentation Project provides the tools, scripts, and "
+"stylesheets to transform your <abbrev>XML</abbrev> documents into other "
+"output formats such as <abbrev>HTML</abbrev>. In addition, these tools can "
+"build your document into a <abbrev>RPM</abbrev> package. To take advantage "
+"of these services, follow the conventions in this section to name your files."
+msgstr ""
+
+#: en_US/getting-files.xml:119(para)
+msgid ""
+"On the CVS server, directories that contain document files are called "
+"<firstterm>modules</firstterm>. Each module represents a single document. "
+"Each document may consist of several <firstterm>branches</firstterm> if that "
+"document changes with each release of Fedora. Contributors can check out "
+"single branches of these modules or the entire module. Each document or "
+"branch may contain multiple XML source files."
+msgstr ""
+
+#: en_US/getting-files.xml:126(para)
+msgid ""
+"Use the <command>cvs co -c</command> command to view existing module names."
+msgstr ""
+
+#: en_US/getting-files.xml:129(title)
+msgid "Partial List of CVS Modules"
+msgstr ""
+
+#: en_US/getting-files.xml:130(userinput)
+#, no-wrap
+msgid "cd ~/localrepo/fedora-docs/"
+msgstr ""
+
+#: en_US/getting-files.xml:149(para)
+msgid ""
+"The leftmost entry in each line is the name of a module you can check out "
+"from CVS. The rest of the line ensures that checkouts include the proper "
+"branch of a document and the common build tools. For more information on "
+"CVS, refer to <xref linkend=\"ch-cvs\"/>."
+msgstr ""
+
+#: en_US/getting-files.xml:154(para)
+msgid ""
+"Note in the listing above that the <systemitem>about-fedora</systemitem> "
+"module has two branches available. One branch is for Fedora 7 and one is for "
+"forward development to match the current work of developers. On the other "
+"hand, the <systemitem>documentation-guide</systemitem> module is not "
+"branched."
+msgstr ""
+
+#: en_US/getting-files.xml:161(title)
+#, fuzzy
+msgid "Modules Labeled <filename>-dir</filename>"
+msgstr "设置 <filename>.vimrc</filename> 文件"
+
+#: en_US/getting-files.xml:162(para)
+msgid ""
+"Modules ending with the suffix <filename>-dir</filename> are not usually "
+"helpful to checkout directly. These modules do not include the common build "
+"tools and thus do not provide many of the functions contributors require."
+msgstr ""
+
+#: en_US/getting-files.xml:168(title)
+msgid "Module Names"
+msgstr ""
+
+#: en_US/getting-files.xml:169(para)
+msgid ""
+"Choose a module name that accurately reflects your document's subject, but "
+"avoid any name already taken. The document title without any use of the word "
+"<wordasword>fedora</wordasword> is a reasonable choice in most cases. Use "
+"the length descriptors <wordasword>tutorial</wordasword> or "
+"<wordasword>guide</wordasword> in the module name where appropriate."
+msgstr ""
+
+#: en_US/getting-files.xml:178(title)
+msgid "Avoid Redundancy"
+msgstr ""
+
+#: en_US/getting-files.xml:179(para)
+msgid ""
+"Do not use the word <wordasword>fedora</wordasword> to name modules in the "
+"Fedora Documentation Project CVS repository."
+msgstr ""
+
+#: en_US/getting-files.xml:185(title)
+msgid "Correct Module Naming"
+msgstr ""
+
+#: en_US/getting-files.xml:186(segtitle)
+msgid "Document Name"
+msgstr ""
+
+#: en_US/getting-files.xml:187(segtitle)
+msgid "CVS Module Name"
+msgstr ""
+
+#: en_US/getting-files.xml:189(seg)
+msgid "Desktop User Guide"
+msgstr ""
+
+#: en_US/getting-files.xml:190(seg)
+msgid "desktop-user-guide"
+msgstr ""
+
+#: en_US/getting-files.xml:194(application)
+msgid "Yum"
+msgstr ""
+
+#: en_US/getting-files.xml:193(seg)
+msgid "Software Management with <placeholder-1/>"
+msgstr ""
+
+#: en_US/getting-files.xml:195(seg)
+msgid "yum-guide"
+msgstr ""
+
+#: en_US/getting-files.xml:198(application)
+msgid "Pup"
+msgstr ""
+
+#: en_US/getting-files.xml:198(seg)
+msgid "Using <placeholder-1/>"
+msgstr ""
+
+#: en_US/getting-files.xml:199(seg)
+msgid "pup-tutorial"
+msgstr ""
+
+#: en_US/getting-files.xml:204(title)
+msgid "File Names"
+msgstr ""
+
+#: en_US/getting-files.xml:205(para)
+msgid ""
+"Follow these guidelines for naming files to make collaboration and document "
+"reuse easy:"
+msgstr ""
+
+#: en_US/getting-files.xml:209(para)
+msgid ""
+"As with module names, avoid using the word <wordasword>fedora</wordasword> "
+"in file names since it is redundant."
+msgstr ""
+
+#: en_US/getting-files.xml:214(para)
+msgid ""
+"If the document is comprised of many XML files, avoid repeating the name of "
+"the document when naming the constituent files."
+msgstr ""
+
+#: en_US/getting-files.xml:219(para)
+msgid ""
+"Avoid numbering files to show order, since editors and authors often "
+"rearrange documents or reuse their files in other documents."
+msgstr ""
+
+#: en_US/emacs.xml:13(title)
+msgid "Emacs and PSGML Mode"
+msgstr "Emacs 与 PSGML 模式"
+
+#: en_US/emacs.xml:16(primary)
+msgid "PSGML"
+msgstr "PSGML"
+
+#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary)
+#: en_US/emacs.xml:43(primary) en_US/emacs.xml:224(primary)
+#: en_US/emacs.xml:233(primary) en_US/emacs.xml:238(primary)
+#: en_US/emacs.xml:243(primary) en_US/emacs.xml:523(application)
+#: en_US/emacs-nxml.xml:18(primary) en_US/emacs-nxml.xml:22(primary)
+msgid "Emacs"
+msgstr "Emacs"
+
+#: en_US/emacs.xml:25(secondary)
+msgid "PSGML mode"
+msgstr "PSGML 模式"
+
+#: en_US/emacs.xml:28(para)
+msgid ""
+"You can use the PSGML mode available for Emacs to make it easier to write in "
+"XML format. PSGML mode provides syntax-highlighting, tag completion, and "
+"more."
+msgstr ""
+"您可以利用 Emacs 的 PSGML 模式以使编辑 XML 格式更容易。PSGML 模式提供了语法高"
+"亮，标记补全等功能。"
+
+#: en_US/emacs.xml:35(title)
+msgid "Installing PSGML"
+msgstr "设置您的 <filename>.emacs</filename>"
+
+#: en_US/emacs.xml:36(para)
+msgid "To install PSGML, use the <command>yum</command> command:"
+msgstr "Emacs"
+
+#: en_US/emacs.xml:37(userinput)
+#, no-wrap
+msgid "yum install psgml"
+msgstr "配置文件"
+
+#: en_US/emacs.xml:40(title)
+msgid "Setting Up Your <filename>.emacs</filename> File"
+msgstr ".emacs"
+
+#: en_US/emacs.xml:48(filename)
+msgid ".emacs"
+msgstr ""
+
+#: en_US/emacs.xml:51(para)
+msgid ""
+"For Emacs to parse your DocBook documents correctly, you must have a "
+"<filename>.emacs</filename> file. Cut and paste the following into your "
+"existing <filename>.emacs</filename> file or create a new one that contains "
+"the following lines:"
+msgstr ""
+
+#: en_US/emacs.xml:181(para)
+msgid ""
+"If you have a wheel mouse and are using Emacs version 21, you can add the "
+"following to your <filename>.emacs</filename> file so your wheel will work "
+"in <application>Emacs</application>:"
+msgstr ""
+
+#: en_US/emacs.xml:192(para)
+msgid ""
+"If you are using the older version 20 of <application>Emacs</application>, "
+"add the following instead:"
+msgstr ""
+
+#: en_US/emacs.xml:221(title)
+msgid "Customizing Emacs"
+msgstr ""
+
+#: en_US/emacs.xml:225(secondary)
+msgid "customizing"
+msgstr ""
+
+#: en_US/emacs.xml:229(filename)
+msgid ".Xresources"
+msgstr ""
+
+#: en_US/emacs.xml:234(secondary)
+msgid "colors"
+msgstr ""
+
+#: en_US/emacs.xml:239(secondary)
+msgid "font"
+msgstr ""
+
+#: en_US/emacs.xml:244(secondary)
+msgid "geometry"
+msgstr ""
+
+#: en_US/emacs.xml:247(para)
+msgid ""
+"The colors, font, and geometry (default size of window) for Emacs in your "
+"<filename>~/.Xresources</filename> file. The format for the settings is "
+"<userinput>emacs.keyword:value</userinput>."
+msgstr ""
+
+#: en_US/emacs.xml:253(para)
+msgid "The following is a sample <filename>~/.Xresources</filename> file."
+msgstr ""
+
+#: en_US/emacs.xml:258(para)
+msgid ""
+"If you have other settings in your <filename>~/.Xresources</filename>, add "
+"the following to the end of the file."
+msgstr ""
+
+#: en_US/emacs.xml:270(para)
+msgid "After modifying this file, execute the following command:"
+msgstr ""
+
+#: en_US/emacs.xml:273(command)
+msgid "xrdb -merge ~/.Xresources"
+msgstr ""
+
+#: en_US/emacs.xml:274(para)
+msgid "Then restart <application>Emacs</application> to apply the changes."
+msgstr ""
+
+#: en_US/emacs.xml:395(title)
+msgid "Basic Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:397(para)
+msgid "The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key."
+msgstr ""
+
+#: en_US/emacs.xml:403(title)
+msgid "Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:404(segtitle)
+msgid "Shortcut"
+msgstr ""
+
+#: en_US/emacs.xml:405(segtitle)
+msgid "Description"
+msgstr ""
+
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:412(keycap)
+#: en_US/emacs.xml:430(keycap) en_US/emacs.xml:436(keycap)
+#: en_US/emacs.xml:443(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:458(keycap)
+#: en_US/emacs.xml:463(keycap) en_US/emacs.xml:468(keycap)
+#: en_US/emacs.xml:473(keycap) en_US/emacs.xml:478(keycap)
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:509(keycap)
+#: en_US/emacs.xml:514(keycap) en_US/emacs.xml:515(keycap)
+#: en_US/emacs.xml:520(keycap) en_US/emacs.xml:521(keycap)
+#: en_US/emacs.xml:532(keycap) en_US/emacs.xml:533(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "Ctrl"
+msgstr ""
+
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:430(keycap)
+#: en_US/emacs.xml:436(keycap) en_US/emacs.xml:448(keycap)
+#: en_US/emacs.xml:521(keycap) en_US/emacs.xml:532(keycap)
+#: en_US/emacs.xml:540(keycap) en_US/emacs.xml:542(keycap)
+msgid "c"
+msgstr ""
+
+#: en_US/emacs.xml:413(keycap)
+msgid "p"
+msgstr ""
+
+#: en_US/emacs.xml:407(seg) en_US/emacs.xml:508(seg) en_US/emacs.xml:514(seg)
+#: en_US/emacs.xml:520(seg) en_US/emacs.xml:532(seg) en_US/emacs.xml:540(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+
+#: en_US/emacs.xml:415(seg)
+msgid "Parse DTD"
+msgstr ""
+
+#: en_US/emacs.xml:431(keycap) en_US/emacs.xml:437(keycap)
+msgid "Shift"
+msgstr ""
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:438(keycap)
+msgid ","
+msgstr ""
+
+#: en_US/emacs.xml:432(keycap) en_US/emacs.xml:439(keycap)
+msgid "Tab"
+msgstr ""
+
+#: en_US/emacs.xml:430(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, <placeholder-5/>"
+msgstr ""
+
+#: en_US/emacs.xml:433(seg)
+msgid "Display list of valid tags"
+msgstr ""
+
+#: en_US/emacs.xml:436(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>, type beginning of "
+"tag, <placeholder-5/>"
+msgstr ""
+
+#: en_US/emacs.xml:440(seg)
+msgid "Complete the tag"
+msgstr ""
+
+#: en_US/emacs.xml:443(keycap)
+msgid "g"
+msgstr ""
+
+#: en_US/emacs.xml:445(seg)
+msgid "Cancel a command in the minibuffer"
+msgstr ""
+
+#: en_US/emacs.xml:449(keycap)
+msgid "/"
+msgstr ""
+
+#: en_US/emacs.xml:448(seg)
+msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:450(seg)
+msgid "Close tag"
+msgstr ""
+
+#: en_US/emacs.xml:453(keycap) en_US/emacs.xml:533(keycap)
+msgid "a"
+msgstr ""
+
+#: en_US/emacs.xml:455(seg)
+msgid "Move cursor to beginning of line"
+msgstr ""
+
+#: en_US/emacs.xml:458(keycap)
+msgid "e"
+msgstr ""
+
+#: en_US/emacs.xml:460(seg)
+msgid "Move cursor to the end of the line"
+msgstr ""
+
+#: en_US/emacs.xml:463(keycap)
+msgid "Home"
+msgstr ""
+
+#: en_US/emacs.xml:465(seg)
+msgid "Move cursor to the beginning of the file"
+msgstr ""
+
+#: en_US/emacs.xml:468(keycap)
+msgid "End"
+msgstr ""
+
+#: en_US/emacs.xml:470(seg)
+msgid "Move cursor to the end of the file"
+msgstr ""
+
+#: en_US/emacs.xml:473(keycap)
+msgid "k"
+msgstr ""
+
+#: en_US/emacs.xml:475(seg)
+msgid "Cut line"
+msgstr ""
+
+#: en_US/emacs.xml:478(keycap)
+msgid "y"
+msgstr ""
+
+#: en_US/emacs.xml:480(seg)
+msgid "Paste line"
+msgstr ""
+
+#: en_US/emacs.xml:483(keycap) en_US/emacs.xml:515(keycap)
+msgid "s"
+msgstr ""
+
+#: en_US/emacs.xml:485(seg)
+msgid "Search forward in the file"
+msgstr ""
+
+#: en_US/emacs.xml:488(keycap)
+msgid "r"
+msgstr ""
+
+#: en_US/emacs.xml:490(seg)
+msgid "Search backwards in the file"
+msgstr ""
+
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:503(keycap) en_US/emacs.xml:527(keycap)
+msgid "Meta"
+msgstr ""
+
+#: en_US/emacs.xml:493(keycap)
+msgid "$"
+msgstr ""
+
+#: en_US/emacs.xml:495(seg) en_US/emacs.xml:500(seg)
+msgid "Check spelling of current word"
+msgstr ""
+
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:508(keycap) en_US/emacs.xml:514(keycap)
+#: en_US/emacs.xml:520(keycap)
+msgid "x"
+msgstr ""
+
+#: en_US/emacs.xml:499(keycap) en_US/emacs.xml:504(keycap)
+msgid "Enter"
+msgstr ""
+
+#: en_US/emacs.xml:498(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:503(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:505(seg)
+msgid "Check spelling of current buffer"
+msgstr ""
+
+#: en_US/emacs.xml:509(keycap)
+msgid "f"
+msgstr ""
+
+#: en_US/emacs.xml:511(seg)
+msgid "Open file"
+msgstr ""
+
+#: en_US/emacs.xml:517(seg)
+msgid "Save file"
+msgstr ""
+
+#: en_US/emacs.xml:523(seg)
+msgid "Exit <placeholder-1/> and prompt to save files if necessary"
+msgstr ""
+
+#: en_US/emacs.xml:527(keycap)
+msgid "q"
+msgstr ""
+
+#: en_US/emacs.xml:529(seg)
+msgid "Fill paragraph"
+msgstr ""
+
+#: en_US/emacs.xml:536(computeroutput)
+#, no-wrap
+msgid "url"
+msgstr ""
+
+#: en_US/emacs.xml:537(computeroutput)
+#, no-wrap
+msgid "ulink"
+msgstr ""
+
+#: en_US/emacs.xml:535(seg)
+msgid ""
+"Edit attributes for a tag (for example, you can edit the <placeholder-1/> "
+"attribute of the <placeholder-2/> tag)"
+msgstr ""
+
+#: en_US/emacs.xml:544(seg)
+msgid "Exit edit attributes"
+msgstr ""
+
+#: en_US/emacs.xml:550(title) en_US/emacs-nxml.xml:77(title)
+msgid "Examples"
+msgstr "范例"
+
+#: en_US/emacs.xml:552(para)
+msgid ""
+"The table or reference card of Emacs and PSGML commands can be confusing for "
+"beginners. This section provides some examples of how to use them."
+msgstr ""
+
+#: en_US/emacs.xml:559(title)
+msgid "Tag Completion"
+msgstr ""
+
+#: en_US/emacs.xml:563(para)
+msgid "This section assumes that you have already parsed the DTD file."
+msgstr ""
+
+#: en_US/emacs.xml:567(para)
+msgid ""
+"To avoid having to type a tag repeatedly, use the key combination "
+"<keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by <keycap><</keycap>. "
+"At the bottom of the <application>Emacs</application> window, the following "
+"prompt appears:"
+msgstr ""
+
+#: en_US/emacs.xml:574(prompt)
+msgid "Tag: <"
+msgstr ""
+
+#: en_US/emacs.xml:576(para)
+msgid ""
+"To view a list of available tags, use either the <keycap>Tab</keycap> or "
+"<keycap>?</keycap>. If you know the first few letters of a tag, enter them, "
+"followed by <keycap>Tab</keycap>. If the letters uniquely identify a tag, "
+"that tag appears. If more than one completion exists, a complete list of "
+"possible tags appears."
+msgstr ""
+
+#: en_US/emacs.xml:585(para)
+msgid ""
+"If you hit <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>, "
+"<keycap><</keycap>, <keycap>k</keycap>, a prompt appears similar to the "
+"example below:"
+msgstr ""
+
+#: en_US/emacs.xml:602(title)
+msgid "Tag Closure"
+msgstr ""
+
+#: en_US/emacs.xml:604(para)
+msgid ""
+"After you open a tag, you must close it. The easiest way to close an open "
+"tag is to use the key sequence <keycombo><keycap>Ctrl</keycap><keycap>c</"
+"keycap></keycombo>, <keycap>/</keycap>. This sequence closes the most "
+"recently opened tag."
+msgstr ""
+
+#: en_US/emacs.xml:616(title)
+msgid "Other Emacs Tasks"
+msgstr ""
+
+#: en_US/emacs.xml:619(title)
+msgid "Working with One Window"
+msgstr ""
+
+#: en_US/emacs.xml:620(para)
+msgid ""
+"Sometimes in <application>Emacs</application>, the window becomes split, "
+"with tags completions or other text in an alternate window. To return to a "
+"single window, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycap>1</keycap>."
+msgstr ""
+
+#: en_US/emacs.xml:630(title)
+msgid "Saving Work"
+msgstr ""
+
+#: en_US/emacs.xml:631(para)
+msgid ""
+"To save your work, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>s</keycap></keycombo>."
+msgstr ""
+
+#: en_US/emacs.xml:642(title)
+msgid "The \"Clear/Quit\" Command"
+msgstr ""
+
+#: en_US/emacs.xml:643(para)
+msgid ""
+"If the tag completion process becomes unwieldy or confusing, use the "
+"keysequence <keycombo><keycap>Ctrl</keycap><keycap>g</keycap></keycombo> to "
+"exit back to the text. <application>Emacs</application> clears any prompts "
+"and returns to the buffer text."
+msgstr ""
+
+#: en_US/emacs.xml:653(title)
+msgid "Opening a new file"
+msgstr ""
+
+#: en_US/emacs.xml:654(para)
+msgid ""
+"To open a new file, use the key sequence <keycombo><keycap>Ctrl</"
+"keycap><keycap>x</keycap></keycombo>, <keycombo><keycap>Ctrl</"
+"keycap><keycap>f</keycap></keycombo>. A prompt appears at the bottom of the "
+"<application>Emacs</application> window. Enter the file name, using "
+"<keycap>Tab</keycap> completion if desired, of the file you wish to open."
+msgstr ""
+
+#: en_US/emacs.xml:668(title)
+msgid "Closing <application>Emacs</application>"
+msgstr ""
+
+#: en_US/emacs.xml:669(para)
+msgid ""
+"To close <application>Emacs</application> use the key sequence "
+"<keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo>, "
+"<keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo>. If you have "
+"not saved your work, <application>Emacs</application> prompts you to save "
+"any changed files."
+msgstr ""
+
+#: en_US/emacs.xml:687(title) en_US/emacs-nxml.xml:127(title)
+msgid "Additional Resources"
+msgstr "其他资源"
+
+#: en_US/emacs.xml:689(para)
+msgid ""
+"Additional Emacs and PSGML references are available at the following "
+"locations:"
+msgstr ""
+
+#: en_US/emacs.xml:697(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+msgid "Emacs Quick Reference Guide"
+msgstr ""
+
+#: en_US/emacs.xml:701(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable>version</replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs.xml:708(para)
+msgid ""
+"Read <citetitle>Editing XML with Emacs and PSGML</citetitle> in <filename>/"
+"usr/share/doc/psgml-<replaceable>version</replaceable>/psgml.ps</filename>."
+msgstr ""
+
+#: en_US/emacs.xml:714(para)
+msgid ""
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\"/>—"
+"<citetitle>Emacs/PSGML Quick Reference</citetitle> is a reference table of "
+"Emacs commands for PSGML mode."
+msgstr ""
+
+#: en_US/emacs.xml:723(citetitle)
+msgid "PSGML Tricks"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:11(title)
+msgid "Emacs and nXML Mode"
+msgstr "Emacs 与 nXML 模式"
+
+#: en_US/emacs-nxml.xml:14(primary) en_US/emacs-nxml.xml:51(primary)
+msgid "nXML"
+msgstr "nXML"
+
+#: en_US/emacs-nxml.xml:23(secondary)
+msgid "nXML mode"
+msgstr "nXML 模式"
+
+#: en_US/emacs-nxml.xml:26(para)
+msgid ""
+"You can also use the nXML mode available for <application>Emacs</"
+"application> to make it even easier to write in DocBook XML format. nXML "
+"mode provides context-sensitive editing using completion, real time validity "
+"error checking, syntax highlighting and indentation. All you need to do is "
+"install an RPM!!"
+msgstr ""
+"您可以使用 <application>Emacs</application> 的 nXML 模式，使撰写 DocBook XML "
+"格式更加简单。nXML 模式提供了上下文敏感的编辑模式，包括补全、实时的有效性检"
+"测、语法高亮和缩进。为此您只要安装一个 RPM 软件包！"
+
+#: en_US/emacs-nxml.xml:35(title)
+msgid "Early stages"
+msgstr "开发早期"
+
+#: en_US/emacs-nxml.xml:36(para)
+msgid ""
+"Please be aware the nxml-mode for <application>Emacs</application> is quite "
+"new, so there are a few things that the advanced user might notice when "
+"using it with other documents types. If you keep an eye on the mailing-list, "
+"you can keep up to date with these, as well as ask questions. For more "
+"details, check out <xref linkend=\"sn-emacs-nxml-readme\"/>."
+msgstr ""
+"需要注意的是，<application>Emacs</application> 的 nXML 模式尚不完善，因此在编"
+"辑一些文档时，高级用户可能会注意到一些问题。如果您略微关注一下邮件列表，就可"
+"以获得相关信息，也可以问问题。请参考 <xref linkend=\"s1-emacs-nxml-readme\"/"
+">。"
+
+#: en_US/emacs-nxml.xml:48(title)
+msgid "Getting the nXML RPM"
+msgstr "下载 nXML RPM"
+
+#: en_US/emacs-nxml.xml:52(secondary)
+msgid "RPM"
+msgstr "RPM"
+
+#: en_US/emacs-nxml.xml:56(primary)
+msgid "nXML RPM"
+msgstr "nXML RPM"
+
+#: en_US/emacs-nxml.xml:59(para)
+msgid ""
+"To use nXML mode with emacs, you will need to install the nXML RPM available "
+"from <ulink url=\"http://people.redhat.com/twaugh/ftp/docbook/nxml-mode/"
+"\">Tim Waugh's</ulink> website or the source from <ulink url=\"http://www."
+"thaiopensource.com/download/\">http://www.thaiopensource.com/download/</"
+"ulink>. The source requires a lot more work to setup, therefore we will only "
+"be concentrating on the RPM version."
+msgstr ""
+"要在 emacs 中使用 nXML 模式，您需要安装 <ulink url=\"http://people.redhat."
+"com/twaugh/ftp/docbook/nxml-modee/\"> Tim Waugh <ulink> 网站上的 nXML RPM，或"
+"者下载 <ulink url=\"http://www.thaiopensource.com/download/\">http://www."
+"thaiopensource.com/download/</ulink> 的源代码。源代码需要花工夫来配置，因此这"
+"里只考虑 RPM 版本。</ulink></ulink>"
+
+#: en_US/emacs-nxml.xml:69(para)
+msgid ""
+"Information on where to get the source is available in <xref linkend=\"sn-"
+"emacs-additional-resources\"/>."
+msgstr ""
+"关于下载源代码请参考 <xref linkend=\"s1-emacs-additional-resources\"/>。"
+
+#: en_US/emacs-nxml.xml:79(para)
+msgid ""
+"Compared to PSGML mode there are only couple of commands that you need. This "
+"speeds up writing with <application>Emacs</application> considerably, which "
+"means you can concentrate more on the content of your article."
+msgstr ""
+"与 PSGML 模式相比，您只需有数几个命令。这样使用 <application>Emacs</"
+"application> 编辑就快捷多了，您可以更多地关注文章的内容。"
+
+#: en_US/emacs-nxml.xml:88(para)
+msgid ""
+"To create a tag, type <userinput><</userinput> and then type the keyword. "
+"To complete the keyword, press <command>Ctrl-Ret</command>, then add the "
+"last <userinput>></userinput>. To close a tag, type <userinput></</"
+"userinput>."
+msgstr ""
+"要创建一个标记，输入 <userinput><</userinput> 然后输入关键字。要完成这个关"
+"键字，按下 <command>Ctrl-Ret</command>，然后添加随后的 <userinput>></"
+"userinput>。要关闭一个标记，输入 <userinput></</userinput>。"
+
+#: en_US/emacs-nxml.xml:97(para)
+msgid ""
+"When you open a document that doesn't have a DOCTYPE declaration at the top "
+"of the file, you will get this message and tag completion won't work because "
+"nXML will not know what format you are writing."
+msgstr ""
+"当您打开不包含首部 DOCTYPE 声明的文件时，将看到如下信息，标记补全也无法实现，"
+"因为 nXML 不知道您在编辑的文件格式。"
+
+#: en_US/emacs-nxml.xml:104(para)
+msgid ""
+"To load the schema, type <command>Ctrl-c</command>, then <command>Ctrl-s</"
+"command> and navigate to <filename>/usr/share/emacs/site-lisp/nxml-mode/"
+"schema/</filename> and load <filename>docbook.rnc</filename>. "
+"<application>Emacs</application> will then prompt you to save it in the "
+"current working directory."
+msgstr ""
+"要加载 schema，按下 <command>Ctrl-c</command>，然后按 <command>Ctrl-s</"
+"command> 然后浏览 <filename>/usr/share/emacs/site-lisp/nxml-mode/schema/</"
+"filename> 并加载 <filename>docbook.rnc</filename>。<application>Emacs</"
+"application> 将提示您将它保存到工作目录。"
+
+#: en_US/emacs-nxml.xml:115(para)
+msgid ""
+"The commands already discussed are the only differences between using "
+"<application>Emacs</application> with PSGML mode and <application>Emacs</"
+"application> with nXML mode. You will still need to use all the same "
+"commands as discussed in <xref linkend=\"sn-emacs-basic-commands\"/>."
+msgstr ""
+"已描述过的命令只是 <application>Emacs</application> PSGML 模式与 "
+"<application>Emacs</application> nXML 模式的不同之处。您仍然需要使用 <xref "
+"linkend=\"s1-emacs-basic-commands\"/> 中描述的命令。"
+
+#: en_US/emacs-nxml.xml:129(para)
+msgid ""
+"Additional Emacs and nXML references are available at the following "
+"locations:"
+msgstr "其他的 Emacs 与 nXML 帮助可以在下列位置找到："
+
+#: en_US/emacs-nxml.xml:136(ulink)
+msgid "http://www.thaiopensource.com/download/"
+msgstr ""
+"<ulink url=\"http://www.thaiopensource.com/download/\">http://www."
+"thaiopensource.com/download/</ulink> Author's download area http://wks.uts."
+"ohio-state.edu/unix_course/intro-135.html Emacs Quick Reference Guide emacs /"
+"usr/share/emacs/version/etc/refcard.ps nXML README /usr/share/doc/nxml-mode-"
+"version/ README M-x load-file RET rng-auto.el RET M-x nxml-mode C-h m C-u M-"
+"x info RET nxml-mode.info RET C-h i test.valid.xml test.invalid.xml .emacs "
+"(load \"~/nxml-mode-200YMMDD/rng-auto.el\") ~/nxml-mode-200YMMDD .elc rng-"
+"auto.el rng-auto.el xml, xsl, rng xhtml .emacs (setq auto-mode-alist (cons "
+"'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-"
+"mode-alist)) .emacs (unify-8859-on-decoding-mode) http://relaxng.org/ http://"
+"relaxng.org/compact-tutorial.html http://eee.thaiopensource.com/relaxng/"
+"trang.html\" http://www.pantor.com/download.html\" https://www.dev.java.net/ "
+"NEWS http://groups.yahoo.com/group/emacs-nxml-mode James Clark "
+"jjc@@thaiopensource.com"
+
+#: en_US/emacs-nxml.xml:137(citetitle)
+msgid "Author's download area"
+msgstr "translator-credits"
+
+#: en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:147(para)
+msgid ""
+"Emacs reference card that comes with the <filename>emacs</filename> package. "
+"You can print it out as a reference. —<filename>/usr/share/emacs/"
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:157(title)
+msgid "nXML README File"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:161(para)
+msgid ""
+"This file can be found in the directory you extracted the source into, or in "
+"<filename>/usr/share/doc/nxml-mode-<replaceable><version></"
+"replaceable>/</filename> if you installed the RPM."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:169(para)
+msgid "README file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:171(para)
+msgid ""
+"This is a new major mode for GNU Emacs for editing XML documents. It "
+"supports editing well-formed XML documents and also provides schema-"
+"sensitive editing of XML documents using RELAX NG Compact Syntax."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:177(para)
+msgid ""
+"To use this, you need GNU Emacs version 21.x, preferably 21.3. GNU Emacs "
+"version 20 will not work properly, nor will XEmacs. To get started, do the "
+"following:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:184(command)
+msgid "M-x load-file RET rng-auto.el RET"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:187(para)
+msgid ""
+"This defines the necessary autoloads. Now, visit a file containing an XML "
+"document, and do the following:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:192(command)
+msgid "M-x nxml-mode"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:195(para)
+msgid "Now do"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:200(command)
+msgid "C-h m"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:203(para)
+msgid ""
+"For information on how to use nxml-mode. The beginnings of a manual are in "
+"nxml-mode.info. You can read this using:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:209(command)
+msgid "C-u M-x info RET nxml-mode.info RET"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:212(para)
+msgid ""
+"It's also installed as an entry at the end of the top-level info directory. "
+"So you can read it with <command>C-h i</command> as usual."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:217(para)
+msgid ""
+"You can use <filename>test.valid.xml</filename> and <filename>test.invalid."
+"xml</filename> as examples of valid and invalid XML documents."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:223(para)
+msgid "To get things automatically loaded each time you start Emacs, add:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:228(computeroutput)
+#, no-wrap
+msgid ""
+" (load \"~/nxml-mode-200YMMDD/rng-auto.el\")\n"
+" "
+msgstr ""
+
+#: en_US/emacs-nxml.xml:232(para)
+msgid ""
+"to your <filename>.emacs</filename>, where <computeroutput>~/nxml-mode-"
+"200YMMDD</computeroutput> is the directory containing the <filename>.elc</"
+"filename> files. Note that <filename>rng-auto.el</filename> does not load "
+"all of the nxml-mode code; it merely sets things up so that all the features "
+"of nxml-mode will be autoloaded properly. You should not try to autoload "
+"<filename>rng-auto.el</filename> itself."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:242(para)
+msgid ""
+"To use nxml-mode automatically for files with an extension of <filename>xml</"
+"filename>, <filename>xsl</filename>, <filename>rng</filename> or "
+"<filename>xhtml</filename>, add the following to your <filename>.emacs</"
+"filename> file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:250(computeroutput)
+#, no-wrap
+msgid ""
+" (setq auto-mode-alist (cons\n"
+"\t'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-mode-alist))\n"
+" "
+msgstr ""
+
+#: en_US/emacs-nxml.xml:255(para)
+msgid ""
+"If you edit XML using iso-8859-N encodings other than iso-8859-1 and you are "
+"running Emacs 21.3 or later, then I recommend enabling unify-8859-on-"
+"decoding-mode, by adding the following to your <filename>.emacs</filename> "
+"file:"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:263(computeroutput)
+#, no-wrap
+msgid "(unify-8859-on-decoding-mode)"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:266(para)
+msgid ""
+"To get validation and schema-sensitive editing, you need a RELAX NG Compact "
+"Syntax (RNC) schema for you document. The schema directory includes some "
+"schemas for popular document types."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:272(para)
+msgid ""
+"For more on RELAX NG, refer to <ulink url=\"http://relaxng.org/\">http://"
+"relaxng.org/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:277(para)
+msgid ""
+"For a tutorial on RELAX NG Compact Syntax, refer to <ulink url=\"http://"
+"relaxng.org/compact-tutorial.html\">http://relaxng.org/compact-tutorial."
+"html</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:282(para)
+msgid ""
+"For automatically creating RNC schemas, I recommend my Trang program: <ulink "
+"url=\"http://www.thaiopensource.com/relaxng/trang.html\">http://eee."
+"thaiopensource.com/relaxng/trang.html\"</ulink>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:293(para)
+msgid "Infer an RNC schema from an instance document"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:298(para)
+msgid "Convert a DTD to an RNC schema"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:303(para)
+msgid "Convert a RELAX NG XML syntax schema to an RNC schema"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:288(para)
+msgid "You can use this to <placeholder-1/>"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:310(para)
+msgid ""
+"To convert a RELAX NG XML syntax (.rng) schema to a RNC schema, you can also "
+"use the XSLT stylesheet from <ulink url=\"http://www.pantor.com/download.html"
+"\">http://www.pantor.com/download.html\"</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:316(para)
+msgid ""
+"To convert a W3C XML Schema to an RNC schema, you need first to convert it "
+"to RELAX NG XML syntax using Sun's RELAX NG converter tool rngconv (built on "
+"top of MSV). Refer to <ulink url=\"https://msv.dev.java.net/\">https://www."
+"dev.java.net/</ulink>."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:323(para)
+msgid "The file <filename>NEWS</filename> describes recent changes."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:327(para)
+msgid ""
+"Please use the list <ulink url=\"http://groups.yahoo.com/group/emacs-nxml-"
+"mode/\">http://groups.yahoo.com/group/emacs-nxml-mode</ulink> for bug "
+"reports, discussion. I will announce all new versions there."
+msgstr ""
+
+#: en_US/emacs-nxml.xml:333(para)
+msgid "James Clark"
+msgstr ""
+
+#: en_US/emacs-nxml.xml:336(para)
+msgid "jjc@@thaiopensource.com"
+msgstr ""
+
+#: en_US/acknowledgments.xml:11(title)
+msgid "Acknowledgments"
+msgstr "致谢"
+
+#: en_US/acknowledgments.xml:13(para)
+#, fuzzy
+msgid ""
+"This document is based on a document started by Tammy Fox (tfox at redhat."
+"com) and contributed to by Sandra Moore (smoore at redhat.com) and Johnray "
+"Fuller (jrfuller at redhat.com)."
+msgstr ""
+"本文档基于 Tammy Fox (tfox at redhat.com) 起草的一篇文档，并得到了 Sandra "
+"Moore (smoore at redhat.com) 和 Johnray Fuller (jrfuller at redhat.com) 的协"
+"助。"
+
+#: en_US/acknowledgments.xml:19(para)
+msgid ""
+"A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to "
+"fix a few typos and explain that anonymous CVS access does not allow commits."
+msgstr ""
+"Roozbeh Pournader (roozbeh at sharif.edu) 的补丁已被合并，修正了一些拼写错"
+"误，解释了匿名 CVS 访问时禁止提交的情况。"
+
+#: en_US/acknowledgments.xml:25(para)
+msgid ""
+"Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to "
+"add the trailing slashes to the <command>figure</command> tag example in "
+"<filename>docs-xml-tags.xml</filename>."
+msgstr ""
+"Gavin Henry (ghenry at suretecsystems.com) 的补丁已被合并，向 <filename>docs-"
+"xml-tags.xml</filename> 中的 <command>figure</command> 标记范例添加尾部斜线，"
+"以及添加 <xref linkend=\"ch-emacs-nxml\"/>。"
+
+#: en_US/acknowledgments.xml:32(para)
+msgid ""
+"A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been "
+"applied to add <xref linkend=\"ch-vim\"/>."
+msgstr ""
+"Joshua Daniel Franklin (joshuadfranklin at yahoo.com) 的补丁已被合并，添加 "
+"<xref linkend=\"ch-vim\"/>。"
+
+#: en_US/acknowledgments.xml:37(para)
+#, fuzzy
+msgid ""
+"A patch from Karsten Wade (kwade at redhat.com) has been applied to add "
+"<xref linkend=\"sn-screenshots\"/>. It was edited by Paul W. Frields "
+"(stickster at gmail.com)."
+msgstr ""
+"Karsten Wade (kwade at redhat.com) 的补丁已被合并，添加 <xref linkend=\"s1-"
+"screenshots\"/>。它为 Paul W. Frields (stickstr5 at hotmail.com) 编辑。"
+
+#. This section has been removed.
+#. <para>
+#. A patch from Paul W. Frields (stickster at gmail.com) has been applied
+#. to add more explanation of the <command>screen</command> tag set to <xref
+#. linkend="sn-xml-tags-screen"></xref>.
+#. </para>
+#: en_US/acknowledgments.xml:50(para)
+msgid ""
+"A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been "
+"applied to more fully explaing the document building system."
+msgstr ""
+"合并了 Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) 的补丁，详细解释文档"
+"构建系统。"
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: en_US/acknowledgments.xml:0(None)
+msgid "translator-credits"
+msgstr ""
+
+#, fuzzy
+#~ msgid ""
+#~ "A patch from Paul W. Frields (stickster at gmail.com) has been applied to "
+#~ "add more explanation of the <command>screen</command> tag set to <xref "
+#~ "linkend=\"sn-xml-tags-screen\"/>."
+#~ msgstr ""
+#~ "Paul W. Frields (stickstr5 at hotmail.com) 的补丁已被合并，向 <xref "
+#~ "linkend=\"s1-xml-tags-screen\"/> 中的 <command>screen</command> 标记集合添"
+#~ "加更多解释。"
+
+#~ msgid "DocBook XML Tags"
+#~ msgstr "DocBook XML 标记"
+
+#, fuzzy
+#~ msgid "XML"
+#~ msgstr ""
+#~ "#-#-#-#-# xml-tags.po (PACKAGE VERSION) #-#-#-#-#\n"
+#~ "XML\n"
+#~ "#-#-#-#-# xml-tags.po (PACKAGE VERSION) #-#-#-#-#\n"
+#~ "translator-credits"
+
+#~ msgid "tags"
+#~ msgstr "标记"
+
+#~ msgid ""
+#~ "Please read this chapter carefully. This chapter describes the tags used "
+#~ "by the Docs Project. Some of the rules described are specific to the "
+#~ "project."
+#~ msgstr ""
+#~ "请仔细阅读这一章。这一章描述了 Docs Project 使用的标记。一些规则是 Docs "
+#~ "Project 特定的。"
+
+#~ msgid ""
+#~ "If these tags are used appropriately, document searches will provide "
+#~ "meaningful results. These tags help search engines identify the "
+#~ "information relevant to the search request. Another benefit is that all "
+#~ "Fedora Project documents will have a similar look and feel (however, they "
+#~ "will have some differences depending upon the output format)."
+#~ msgstr ""
+#~ "如果这些标记运用合适，搜索文档时可以得到有意义的结果。这些标记帮助搜索引擎"
+#~ "确认与搜索条件相关的信息。另一个好处是使 XML XML http://www.docbook.org/"
+#~ "tdg/en/html/docbook.html xml trade;, copy;, reg; trademark trademark/"
+#~ "trademark trademark class=\"registered\"/trademark trademark class="
+#~ "\"copyright\"/trademark para para para (para screen itemizedlist "
+#~ "orderedlist variablelist table para listitem para listitem para screen "
+#~ "XML screen screen /screen) screen application XML application application "
+#~ "application /application applicationMozilla/application applicationlynx/"
+#~ "application Mozilla lynx chapter XML chapter chapter id=\"ch-sample\" "
+#~ "title/title para/para /chapter chapter sect1, sect2, sect3 citetitle XML "
+#~ "citetitle citetitle citetitleIG;/citetitle. IG; command XML command "
+#~ "application command command /command commandredhat-config-keyboard/"
+#~ "command commandsetup/command redhat-config-keyboard setup "
+#~ "commandMAILNOVIOLATIONS/command commandtrue/commandcommandtrue/command "
+#~ "MAILNOVIOLATIONS truetrue commandoption command command computeroutput "
+#~ "XML computeroutput computeroutput/computeroutput emphasis XML emphasis "
+#~ "emphasis /emphasis emphasis/emphasis emphasis/emphasis example XML "
+#~ "example example /example example example id=\"static-ip\" title/title "
+#~ "screen width=60 computeroutput host apex { option host-name \"apex."
+#~ "example.com\"; hardware ethernet 00:A0:78:8E:9E:AA; fixed-address "
+#~ "192.168.1.4; } computeroutput /screen /example host apex { option host-"
+#~ "name \"apex.example.com\"; hardware ethernet 00:A0:78:8E:9E:AA; fixed-"
+#~ "address 192.168.1.4; } filename XML filename filename /filename filename "
+#~ "filename/home/smoore/sam.xml/filename /home/smoore/sam.xml "
+#~ "applicationKeyboard Configuration Tool/applicationfilenamesystem-config-"
+#~ "keyboard/filename Keyboard Configuration Toolredhat-config-keyboard /) "
+#~ "firstterm XML firstterm firstterm /firstterm firsttermdisk partitions/"
+#~ "firstterm( disk partitions( footnote XML footnote footnote para /para /"
+#~ "footnote citetitleInstallation Guide/citetitle Installation Guide figure "
+#~ "XML figure figure id=\"fig-ksconfig-basic\" title/title mediaobject "
+#~ "imageobject imagedata fileref=\"./figs/ksconfig/ksconfig-basic.eps\" "
+#~ "format=\"EPS\"/ /imageobject imageobject imagedata fileref=\"./figs/"
+#~ "ksconfig/ksconfig-basic.png\" format=\"PNG\"/ /imageobject textobject "
+#~ "phrase /phrase /textobject /mediaobject /figure figure id=\"fig-ksconfig-"
+#~ "basic\" == id=\"\" title/title == fileref=\"./figs/ksconfig/ksconfig-"
+#~ "basics.eps\" == .eps fileref=\"./figs/ksconfig/ksconfig-basics.png\" == ."
+#~ "png phrase/phrase == \" XML GUI guilabel XML GUI guilabel XML guilabel "
+#~ "guilabel /guilabel guilabelAuthentication Configuration/guilabel "
+#~ "Authentication Configuration guibutton XML GUI guibutton XML guibutton "
+#~ "guibutton /guibutton guibuttonActivate on boot/guibutton Activate on boot "
+#~ "guiicon XML GUI guiicon XML guiicon guiicon /guiicon guiiconStart Here/"
+#~ "guiicon Start Here guimenu guimenuitem XML GUI guimenu XML guimenu XML "
+#~ "GUI guimenuitem XML guimenuitem guimenu /guimenu guimenuitem /guimenuitem "
+#~ "guimenuMain Menu/guimenu = guimenuitemProgramming/guimenuitem = "
+#~ "guimenuitemEmacs/guimenuitem applicationEmacs/application Main Menu = "
+#~ "Programming = Emacs Emacs keycap XML keycap keycap /keycap keycapEnter/"
+#~ "keycap Enter menuchoice XML menuchoice shortcut keycap menuchoice "
+#~ "menuchoice shortcut keycombokeycapCtrl/keycapkeycaps/keycap/keycombo /"
+#~ "shortcut guimenuaccelF/accelile/guimenu guimenuitemaccelS/accelave/"
+#~ "guimenuitem /menuchoice. CtrlsFileSave. keycombo XML keycombo keycombo /"
+#~ "keycombo, keycap /keycap keycombo keycapCtrl/keycapkeycapAlt/"
+#~ "keycapkeycapDel/keycap /keycombo. CtrlAltDel. itemizedlist XML "
+#~ "itemizedlist XML itemizedlist itemizedlist itemizedlist variablelist "
+#~ "itemizedlist ( para itemizedlist listitem para/para /listitem listitem "
+#~ "para/para /listitem listitem para/para /listitem /itemizedlist "
+#~ "orderedlist XML orderedlist orderedlist XML orderedlist orderedlist "
+#~ "orderedlist orderedlist ( para orderedlist listitem paramdash; http://www."
+#~ "redhat.com/support/errata; /para /listitem listitem paramdash; /para /"
+#~ "listitem /orderedlist http://www.redhat.com/support/errata; variablelist "
+#~ "XML variablelist XML variablelist variablelist variablelist variablelist "
+#~ "para variablelist varlistentry term /term listitem para/para /listitem /"
+#~ "varlistentry varlistentry termXFree 4.0 /term listitem paraX /para /"
+#~ "listitem /varlistentry /variablelist XFree 4.0 X frame simplelist XML "
+#~ "simplelist XML simplelist simplelist simplelist simplelist simplelist "
+#~ "simplelist itemizedlist XML table id=\"tb-hwinfo-hostbus\" title/title "
+#~ "tgroup cols=\"3\" colspec colnum=\"1\" colname=\"HostBus\" colwidth=\"33"
+#~ "\"/ colspec colnum=\"2\" colname=\"Features\" colwidth=\"34\"/ colspec "
+#~ "colnum=\"3\" colname=\"Single\" colwidth=\"33\"/ thead row entry/entry "
+#~ "entry/entry entrySingle-Initiator /entry /row /thead tbody row "
+#~ "entryAdaptec 2940U2W/entry entrysimplelist memberUltra2, wide, LVD./"
+#~ "member memberHD68 external connector./member memberOne channel, with two "
+#~ "bus segments./member memberSet the onboard termination by using the BIOS "
+#~ "utility./member memberOnboard termination is disabled when the power is "
+#~ "off./member /simplelist/entry entrysimplelist memberSet the onboard "
+#~ "termination to automatic (the default)./member memberUse the internal "
+#~ "SCSI connector for private (non-cluster) storage./member /simplelist/"
+#~ "entry /row row entryQlogic QLA1080/entry entrysimplelist memberUltra2, "
+#~ "wide, LVD/member memberVHDCI external connector/member memberOne channel/"
+#~ "member memberSet the onboard termination by using the BIOS utility./"
+#~ "member memberOnboard termination is disabled when the power is off, "
+#~ "unless jumpers are used to enforce termination./member /simplelist/entry "
+#~ "entrysimplelist memberSet the onboard termination to automatic (the "
+#~ "default)./member memberUse the internal SCSI connector for private (non-"
+#~ "cluster) storage./member /simplelist/entry /row /tbody /tgroup /table "
+#~ "Single-Initiator Adaptec 2940U2W Ultra2, wide, LVD. HD68 external "
+#~ "connector. One channel, with two bus segments. Set the onboard "
+#~ "termination by using the BIOS utility. Onboard termination is disabled "
+#~ "when the power is off. Set the onboard termination to automatic (the "
+#~ "default). Use the internal SCSI connector for private (non-cluster) "
+#~ "storage. Qlogic QLA1080 Ultra2, wide, LVD VHDCI external connector One "
+#~ "channel Set the onboard termination by using the BIOS utility. Onboard "
+#~ "termination is disabled when the power is off, unless jumpers are used to "
+#~ "enforce termination. Set the onboard termination to automatic (the "
+#~ "default). Use the internal SCSI connector for private (non-cluster) "
+#~ "storage. simplelist entry simplelist simplelist member glosslist XML "
+#~ "glosslist XML glosslist glosslist glosslist XML glosslist glossentry "
+#~ "glosstermapplet/glossterm glossdef para/para /glossdef /glossentry "
+#~ "glossentry glosstermarchitecture/glossterm glossdef para/para /glossdef /"
+#~ "glossentry glossentry glosstermarchive/glossterm glossdef para/para /"
+#~ "glossdef /glossentry /glosslist applet architecture archive option XML "
+#~ "option option /option option commandls/command option-la/option ls -la "
+#~ "XML indexterm -- primaryfoo/primary -- secondarybar/secondary -- \"bar\" /"
+#~ "indexterm -- foo bar seealso seealso seealso indexterm primarySWAK/"
+#~ "primary seealsosalutations/seealso /indexterm indexterm "
+#~ "primarysalutations/primary /indexterm SWAK Salutations Salutations see "
+#~ "see indexterm primaryGuinness/primary seebeer/see -- \"beer\" /indexterm "
+#~ "indexterm primarybeer/primary /indexterm Guinness Beer Beer generated-"
+#~ "index.html generate.index para XML para para /para para para (para screen "
+#~ "itemizedlist orderedlist variablelist table part parts XML part part part "
+#~ "id=\"pt-foo\" partintro para/para CHAPTER; ANOTHER-CHAPTER; /part part id="
+#~ "\"pt-setup\" title/title partintro paraFC; /para /partintro prompt XML "
+#~ "prompt prompt /prompt promptLILO:/prompt promptC:\\/prompt LILO: C:\\ "
+#~ "screen replaceable XML replaceable replaceable /replaceable replaceable "
+#~ "foo-replaceableversion-number/replaceable.replaceablearch/replaceable.rpm "
+#~ "foo-version-number.arch.rpm screen XML screen screen screen /screen "
+#~ "screen screen screen computeroutput, userinput, replaceable screen screen "
+#~ "screen screen screen lt;paragt; /screen para screen screen computeroutput "
+#~ "userinput para /parascreenuserinputcommand -sw file1/userinput/"
+#~ "screenpara /parascreencomputeroutputCompleted, time = 0.12 sec/"
+#~ "computeroutput/screen command -sw file1 Completed, time = 0.12 sec screen "
+#~ "screen userinput computeroutput userinput para filename/etc/sysconfig/"
+#~ "init/filename /parascreen GRAPHICAL=userinputyes/userinput/screen /etc/"
+#~ "sysconfig/init GRAPHICAL=yes screen replaceable section XML )sect1 sect1 "
+#~ "id=\"s1-uniquename\" title/title para /para sect2 id=\"s2-uniquename\" "
+#~ "title/title para /para sect3 id=\"s3-uniquename\" title/title para /para /"
+#~ "sect3 /sect2 /sect1 section section id=\"sn-uniquename\" title/title "
+#~ "para /para /section section id=\"sn-anothername\" title/title para /para /"
+#~ "section table XML table table id=\"tb-mockup-before-begin\" \"tb-mockup-"
+#~ "before-begin\" titleAvailable Features of GNOME and KDE/title tgroup cols="
+#~ "\"3\" colspec colnum=\"1\" colname=\"Features\" colwidth=\"3\"/ colspec "
+#~ "colnum=\"1\" colname=\"Features\" colwidth=\"3\" colspec colnum=\"2\" "
+#~ "colname=\"GNOME\" colwidth=\"2\"/ colspec colnum=\"3\" colname=\"KDE\" "
+#~ "colwidth=\"2\"/ thead row entryFeatures/entry entryGNOME/entry entryKDE/"
+#~ "entry /row /thead tbody row entry/entry entryyes/entry entryyes/entry /"
+#~ "row row entry/entry entryyes/entry entryyes/entry /row row entry/entry "
+#~ "entryyes /entry entryyes /entry /row /tbody /tgroup /table Available "
+#~ "Features of GNOME and KDE GNOME KDE yes yes yes yes yes yes XML table "
+#~ "Emacs simplelist member table id=\"tb-hardware-powerswitch\" title/title "
+#~ "tgroup cols=\"4\" colspec colnum=\"1\" colname=\"Hardware\" colwidth=\"2"
+#~ "\"/ colspec colnum=\"2\" colname=\"Quantity\" colwidth=\"2\"/ colspec "
+#~ "colnum=\"3\" colname=\"Description\" colwidth=\"6\"/ colspec colnum=\"4\" "
+#~ "colname=\"Required\" colwidth=\"2\"/ thead row entryHardware/entry "
+#~ "entryQuantity/entry entryDescription/entry entryRequired/entry /row /"
+#~ "thead tbody row entrySerial power switches/entry entryTwo/entry "
+#~ "entrysimplelist memberPower switches enable each cluster system to power-"
+#~ "cycle the other cluster system. Note that clusters are configured with "
+#~ "either serial or network attached power switches and not both./member "
+#~ "memberThe following serial attached power switch has been fully tested:/"
+#~ "member memberRPS-10 (model M/HD in the US, and model M/EC in Europe) /"
+#~ "member memberLatent support is provided for the following serial attached "
+#~ "power switch. This switch has not yet been fully tested:/member memberAPC "
+#~ "Serial On/Off Switch (partAP9211), ulink url=\"http://www.apc.com/"
+#~ "\"http://www.apc.com//ulink/member /simplelist/entry entryStrongly "
+#~ "recommended for data integrity under all failure conditions/entry /row /"
+#~ "tbody /tgroup /table simplelist entry Hardware Quantity Required Serial "
+#~ "power switches Two Power switches enable each cluster system to power-"
+#~ "cycle the other cluster system. Note that clusters are configured with "
+#~ "either serial or network attached power switches and not both.The "
+#~ "following serial attached power switch has been fully tested:RPS-10 "
+#~ "(model M/HD in the US, and model M/EC in Europe)Latent support is "
+#~ "provided for the following serial attached power switch. This switch has "
+#~ "not yet been fully tested:APC Serial On/Off Switch (partAP9211), http://"
+#~ "www.apc.com/ Strongly recommended for data integrity under all failure "
+#~ "conditions trademark XML trademark trade;, copy;, reg; trademark "
+#~ "trademark/trademark trademark class=\"registered\"/trademark trademark "
+#~ "class=\"copyright\"/trademark userinput XML userinput userinput "
+#~ "userinputdd if=boot.img of=/dev/fd0 bs=1440k/userinput dd if=boot.img of=/"
+#~ "dev/fd0 bs=1440k ulink XML ulink mdash; ulink url=\"http://www.redhat.com/"
+#~ "support/errata/\" http://www.redhat.com/support/errata//ulink; http://www."
+#~ "redhat.com/support/errata/; /)http://www.redhat.com/ wordasword XML "
+#~ "wordasword wordasword wordasword wordasword commandgrep/command "
+#~ "wordaswordlinux/wordaswordcommandgrep linux/command grep linuxgrep linux "
+#~ "xref XML xref xref xref linkend=\"ch-tutorial\"/xref xref linkend=\"s1-"
+#~ "tutorial-parent\"/xref"
+
+#~ msgid ""
+#~ "The goal of the Fedora Documentation Project is to create easy-to-follow, "
+#~ "task-based documentation for Fedora users and developers. Other than the "
+#~ "<citetitle>Installation Guide</citetitle>, each tutorial should be in "
+#~ "DocBook XML article format, with one article per topic. This way, writers "
+#~ "can contribute documentation about a specific topic without having to "
+#~ "worry about how it fits into a manual or how it flows with other topics."
+#~ msgstr ""
+#~ "Docs Project 的目标是为 DocBook XML v4.1 xmlto) Emacs PSGML Emacs nXML"
+
+#~ msgid "The following tools are used:"
+#~ msgstr "translator-credits"
+@
+
+
+1.6
+log
+ at Update POT and PO
+@
+text
+ at d5 1
+a5 1
+"POT-Creation-Date: 2007-12-15 16:51-0500\n"
+d51 5
+a55 1
+#: en_US/rpm-info.xml:31(holder)
+d59 1
+a59 1
+#: en_US/rpm-info.xml:33(title)
+d63 1
+a63 1
+#: en_US/rpm-info.xml:34(desc)
+d67 5
+a71 1
+#: en_US/rpm-info.xml:38(details)
+d75 1
+a75 1
+#: en_US/rpm-info.xml:42(details)
+d79 1
+a79 1
+#: en_US/rpm-info.xml:46(details)
+d83 1
+a83 1
+#: en_US/rpm-info.xml:50(details)
+d87 1
+a87 1
+#: en_US/rpm-info.xml:54(details)
+d91 1
+a91 1
+#: en_US/rpm-info.xml:58(details)
+d95 1
+a95 1
+#: en_US/rpm-info.xml:62(details)
+d99 1
+a99 1
+#: en_US/rpm-info.xml:69(details)
+d103 171
+d2754 1
+a2754 1
+"which produces the text \"Fedora 8.\""
+@
+
+
+1.5
+log
+ at Update POT/PO files for DocGuide, minor changes
+@
+text
+ at d5 1
+a5 1
+"POT-Creation-Date: 2007-11-14 21:12-0500\n"
+d64 4
+d71 1
+a71 1
+#: en_US/rpm-info.xml:42(details)
+d75 1
+a75 1
+#: en_US/rpm-info.xml:46(details)
+d79 1
+a79 1
+#: en_US/rpm-info.xml:50(details)
+d83 1
+a83 1
+#: en_US/rpm-info.xml:54(details)
+d87 1
+a87 1
+#: en_US/rpm-info.xml:58(details)
+d91 1
+a91 1
+#: en_US/rpm-info.xml:65(details)
+d3582 24
+d3609 2
+a3610 2
+#: en_US/module-struct.xml:243(abbrev) en_US/module-struct.xml:254(abbrev)
+#: en_US/module-struct.xml:279(abbrev) en_US/module-struct.xml:284(abbrev)
+d3614 2
+a3615 2
+#: en_US/module-struct.xml:247(systemitem)
+#: en_US/module-struct.xml:257(systemitem)
+d3619 2
+a3620 2
+#: en_US/module-struct.xml:248(systemitem)
+#: en_US/module-struct.xml:258(systemitem)
+d3624 1
+a3624 1
+#: en_US/module-struct.xml:246(filename)
+d3628 1
+a3628 1
+#: en_US/module-struct.xml:243(seg)
+d3636 1
+a3636 1
+#: en_US/module-struct.xml:253(systemitem)
+d3640 1
+a3640 1
+#: en_US/module-struct.xml:256(filename)
+d3644 1
+a3644 1
+#: en_US/module-struct.xml:254(seg)
+d3651 1
+a3651 1
+#: en_US/module-struct.xml:262(systemitem)
+d3655 2
+a3656 2
+#: en_US/module-struct.xml:263(abbrev) en_US/module-struct.xml:264(abbrev)
+#: en_US/module-struct.xml:280(abbrev) en_US/module-struct.xml:285(abbrev)
+d3660 1
+a3660 1
+#: en_US/module-struct.xml:263(seg)
+d3667 1
+a3667 1
+#: en_US/module-struct.xml:268(systemitem)
+d3671 1
+a3671 1
+#: en_US/module-struct.xml:269(command)
+d3675 1
+a3675 1
+#: en_US/module-struct.xml:269(seg)
+d3681 1
+a3681 1
+#: en_US/module-struct.xml:273(systemitem)
+d3685 1
+a3685 1
+#: en_US/module-struct.xml:274(seg)
+d3689 2
+a3690 2
+#: en_US/module-struct.xml:277(systemitem)
+#: en_US/module-struct.xml:286(filename)
+d3694 1
+a3694 1
+#: en_US/module-struct.xml:279(emphasis)
+d3698 1
+a3698 1
+#: en_US/module-struct.xml:278(seg)
+d3704 1
+a3704 1
+#: en_US/module-struct.xml:283(systemitem)
+d3708 1
+a3708 1
+#: en_US/module-struct.xml:284(seg)
+d3714 1
+a3714 1
+#: en_US/module-struct.xml:291(title)
+d3718 1
+a3718 1
+#: en_US/module-struct.xml:292(para)
+d3724 1
+a3724 1
+#: en_US/module-struct.xml:296(title)
+d3728 1
+a3728 1
+#: en_US/module-struct.xml:297(para)
+d3737 1
+a3737 1
+#: en_US/module-struct.xml:305(para)
+d3743 1
+a3743 1
+#: en_US/module-struct.xml:312(title)
+d3747 1
+a3747 1
+#: en_US/module-struct.xml:313(para)
+d3755 1
+a3755 1
+#: en_US/module-struct.xml:320(para)
+d3768 1
+a3768 1
+#: en_US/module-struct.xml:334(para)
+d3775 1
+a3775 1
+#: en_US/module-struct.xml:340(para)
+d3785 1
+a3785 1
+#: en_US/module-struct.xml:350(para)
+d3794 1
+a3794 1
+#: en_US/module-struct.xml:359(para)
+d3800 1
+a3800 1
+#: en_US/module-struct.xml:365(title)
+d3804 1
+a3804 1
+#: en_US/module-struct.xml:372(title)
+d3808 1
+a3808 1
+#: en_US/module-struct.xml:373(para)
+d3813 1
+a3813 1
+#: en_US/module-struct.xml:377(para)
+d3817 1
+a3817 1
+#: en_US/module-struct.xml:381(para)
+d3826 1
+a3826 1
+#: en_US/module-struct.xml:391(title)
+d3830 1
+a3830 1
+#: en_US/module-struct.xml:392(para)
+d3838 1
+a3838 1
+#: en_US/module-struct.xml:399(para)
+d3844 1
+a3844 1
+#: en_US/module-struct.xml:405(para)
+d3848 1
+a3848 1
+#: en_US/module-struct.xml:409(para)
+d3854 1
+a3854 1
+#: en_US/module-struct.xml:414(para)
+d3860 1
+a3860 1
+#: en_US/module-struct.xml:417(replaceable)
+d3864 1
+a3864 1
+#: en_US/module-struct.xml:417(screen)
+@
+
+
+1.4
+log
+ at Push new 0.3.1 POT and update PO - ERRATA, this time with new content file
+@
+text
+ at d5 1
+a5 1
+"POT-Creation-Date: 2007-08-03 12:42-0400\n"
+d64 8
+d75 1
+a75 1
+#: en_US/rpm-info.xml:42(details)
+d79 1
+a79 1
+#: en_US/rpm-info.xml:46(details)
+d83 1
+a83 1
+#: en_US/rpm-info.xml:50(details)
+d87 1
+a87 1
+#: en_US/rpm-info.xml:57(details)
+d191 4
+d197 10
+d211 1
+a211 1
+#: en_US/publishing.xml:68(screen)
+d216 1
+a216 1
+#: en_US/publishing.xml:71(para)
+d222 1
+a222 1
+#: en_US/publishing.xml:85(para)
+d228 1
+a228 1
+#: en_US/publishing.xml:87(screen)
+d233 1
+a233 1
+#: en_US/publishing.xml:90(para)
+d237 1
+a237 1
+#: en_US/publishing.xml:91(screen)
+d242 1
+a242 1
+#: en_US/publishing.xml:92(para)
+d246 1
+a246 1
+#: en_US/publishing.xml:94(screen)
+d251 1
+a251 1
+#: en_US/publishing.xml:97(para)
+d257 1
+a257 1
+#: en_US/publishing.xml:101(title)
+d261 1
+a261 1
+#: en_US/publishing.xml:103(title)
+d265 1
+a265 1
+#: en_US/publishing.xml:104(para)
+d271 1
+a271 1
+#: en_US/publishing.xml:108(para)
+d279 1
+a279 1
+#: en_US/publishing.xml:115(para)
+d285 1
+a285 1
+#: en_US/publishing.xml:120(para)
+d293 1
+a293 1
+#: en_US/publishing.xml:129(title)
+d297 1
+a297 1
+#: en_US/publishing.xml:130(para)
+d305 1
+a305 1
+#: en_US/publishing.xml:137(para)
+d309 1
+a309 1
+#: en_US/publishing.xml:138(screen)
+d318 1
+a318 1
+#: en_US/publishing.xml:144(para)
+d323 1
+a323 1
+#: en_US/publishing.xml:146(replaceable)
+d327 1
+a327 1
+#: en_US/publishing.xml:146(screen)
+d334 1
+a334 1
+#: en_US/publishing.xml:150(para)
+d338 1
+a338 1
+#: en_US/publishing.xml:151(screen)
+d346 1
+a346 1
+#: en_US/publishing.xml:156(para)
+d352 1
+a352 1
+#: en_US/publishing.xml:165(para)
+d363 1
+a363 1
+#: en_US/publishing.xml:175(para)
+d369 1
+a369 1
+#: en_US/publishing.xml:179(para)
+d375 1
+a375 1
+#: en_US/publishing.xml:183(title)
+d379 1
+a379 1
+#: en_US/publishing.xml:184(para)
+d385 1
+a385 1
+#: en_US/publishing.xml:192(title)
+d389 1
+a389 1
+#: en_US/publishing.xml:193(para)
+d393 1
+a393 1
+#: en_US/publishing.xml:197(para)
+d397 1
+a397 1
+#: en_US/publishing.xml:198(screen)
+d415 1
+a415 1
+#: en_US/publishing.xml:214(para)
+d421 1
+a421 1
+#: en_US/publishing.xml:216(replaceable)
+d425 1
+a425 1
+#: en_US/publishing.xml:216(screen)
+d430 1
+a430 1
+#: en_US/publishing.xml:219(para)
+d434 1
+a434 1
+#: en_US/publishing.xml:221(screen)
+d2571 1
+a2571 1
+"which produces the text \"Fedora 7.\""
+d3212 38
+d4009 8
+a4016 1
+#: en_US/getting-files.xml:106(title)
+d4020 1
+a4020 1
+#: en_US/getting-files.xml:107(para)
+d4029 1
+a4029 1
+#: en_US/getting-files.xml:115(para)
+d4039 1
+a4039 1
+#: en_US/getting-files.xml:122(para)
+d4044 1
+a4044 1
+#: en_US/getting-files.xml:125(title)
+d4048 1
+a4048 1
+#: en_US/getting-files.xml:126(userinput)
+d4053 1
+a4053 1
+#: en_US/getting-files.xml:145(para)
+d4061 1
+a4061 1
+#: en_US/getting-files.xml:150(para)
+d4070 1
+a4070 1
+#: en_US/getting-files.xml:157(title)
+d4075 1
+a4075 1
+#: en_US/getting-files.xml:158(para)
+d4082 1
+a4082 1
+#: en_US/getting-files.xml:164(title)
+d4086 1
+a4086 1
+#: en_US/getting-files.xml:165(para)
+d4095 1
+a4095 1
+#: en_US/getting-files.xml:174(title)
+d4099 1
+a4099 1
+#: en_US/getting-files.xml:175(para)
+d4105 1
+a4105 1
+#: en_US/getting-files.xml:181(title)
+d4109 1
+a4109 1
+#: en_US/getting-files.xml:182(segtitle)
+d4113 1
+a4113 1
+#: en_US/getting-files.xml:183(segtitle)
+d4117 1
+a4117 1
+#: en_US/getting-files.xml:185(seg)
+d4121 1
+a4121 1
+#: en_US/getting-files.xml:186(seg)
+d4125 1
+a4125 1
+#: en_US/getting-files.xml:190(application)
+d4129 1
+a4129 1
+#: en_US/getting-files.xml:189(seg)
+d4133 1
+a4133 1
+#: en_US/getting-files.xml:191(seg)
+d4137 1
+a4137 1
+#: en_US/getting-files.xml:194(application)
+d4141 1
+a4141 1
+#: en_US/getting-files.xml:194(seg)
+d4145 1
+a4145 1
+#: en_US/getting-files.xml:195(seg)
+d4149 1
+a4149 1
+#: en_US/getting-files.xml:200(title)
+d4153 1
+a4153 1
+#: en_US/getting-files.xml:201(para)
+d4159 1
+a4159 1
+#: en_US/getting-files.xml:205(para)
+d4165 1
+a4165 1
+#: en_US/getting-files.xml:210(para)
+d4171 1
+a4171 1
+#: en_US/getting-files.xml:215(para)
+@
+
+
+1.3
+log
+ at Push new 0.3.1 POT and update PO
+@
+text
+ at d5 1
+a5 1
+"POT-Creation-Date: 2007-08-03 12:38-0400\n"
+d83 334
+@
+
+
+1.2
+log
+ at Update POT and PO with new metadata strings
+@
+text
+ at d5 1
+a5 1
+"POT-Creation-Date: 2007-07-28 18:02-0400\n"
+d64 12
+d79 1
+a79 1
+#: en_US/rpm-info.xml:45(details)
+d2647 1
+a2647 1
+#: en_US/emacs.xml:557(title) en_US/emacs-nxml.xml:160(title)
+d2884 1
+a2884 1
+#: en_US/module-struct.xml:46(title)
+d2888 1
+a2888 1
+#: en_US/module-struct.xml:47(segtitle)
+d2892 1
+a2892 1
+#: en_US/module-struct.xml:48(segtitle)
+d2896 1
+a2896 1
+#: en_US/module-struct.xml:49(segtitle)
+d2900 1
+a2900 1
+#: en_US/module-struct.xml:51(seg)
+d2904 2
+a2905 2
+#: en_US/module-struct.xml:52(seg) en_US/module-struct.xml:89(seg)
+#: en_US/module-struct.xml:96(seg)
+d2909 2
+a2910 2
+#: en_US/module-struct.xml:55(filename)
+#: en_US/module-struct.xml:177(systemitem)
+d2914 1
+a2914 1
+#: en_US/module-struct.xml:59(firstterm)
+d2918 1
+a2918 1
+#: en_US/module-struct.xml:60(para)
+d2926 1
+a2926 1
+#: en_US/module-struct.xml:53(seg)
+d2935 1
+a2935 1
+#: en_US/module-struct.xml:68(seg)
+d2939 1
+a2939 1
+#: en_US/module-struct.xml:69(seg) en_US/module-struct.xml:79(seg)
+d2943 1
+a2943 1
+#: en_US/module-struct.xml:70(filename) en_US/module-struct.xml:74(filename)
+d2947 1
+a2947 1
+#: en_US/module-struct.xml:70(seg)
+d2955 1
+a2955 1
+#: en_US/module-struct.xml:78(seg)
+d2959 1
+a2959 1
+#: en_US/module-struct.xml:80(filename) en_US/module-struct.xml:184(filename)
+d2963 1
+a2963 1
+#: en_US/module-struct.xml:82(acronym)
+d2967 9
+a2975 1
+#: en_US/module-struct.xml:80(seg)
+d2981 3
+a2983 1
+"are created as needed from these PO files."
+d2986 1
+a2986 1
+#: en_US/module-struct.xml:88(seg) en_US/module-struct.xml:90(filename)
+d2990 1
+a2990 1
+#: en_US/module-struct.xml:90(seg)
+d2996 1
+a2996 1
+#: en_US/module-struct.xml:95(filename) en_US/module-struct.xml:97(filename)
+d3000 1
+a3000 1
+#: en_US/module-struct.xml:97(seg)
+d3004 1
+a3004 1
+#: en_US/module-struct.xml:102(title)
+d3008 1
+a3008 1
+#: en_US/module-struct.xml:103(para)
+d3016 1
+a3016 1
+#: en_US/module-struct.xml:111(title)
+d3020 1
+a3020 1
+#: en_US/module-struct.xml:116(para)
+d3029 1
+a3029 1
+#: en_US/module-struct.xml:112(para)
+d3038 1
+a3038 1
+#: en_US/module-struct.xml:128(title)
+d3043 1
+a3043 1
+#: en_US/module-struct.xml:129(para)
+d3050 1
+a3050 1
+#: en_US/module-struct.xml:135(para)
+d3056 1
+a3056 1
+#: en_US/module-struct.xml:141(title)
+d3060 1
+a3060 1
+#: en_US/module-struct.xml:158(para)
+d3067 1
+a3067 1
+#: en_US/module-struct.xml:164(title)
+d3071 1
+a3071 1
+#: en_US/module-struct.xml:165(segtitle)
+d3075 1
+a3075 1
+#: en_US/module-struct.xml:166(segtitle) en_US/module-struct.xml:244(segtitle)
+d3079 1
+a3079 1
+#: en_US/module-struct.xml:168(systemitem)
+d3083 1
+a3083 1
+#: en_US/module-struct.xml:169(seg)
+d3089 1
+a3089 1
+#: en_US/module-struct.xml:174(systemitem)
+d3093 1
+a3093 1
+#: en_US/module-struct.xml:175(seg)
+d3099 1
+a3099 13
+#: en_US/module-struct.xml:180(systemitem)
+msgid "OTHERS"
+msgstr ""
+
+#: en_US/module-struct.xml:181(seg)
+msgid ""
+"This variable contains a listing of ISO codes for any other versions into "
+"which the document has been translated. The module must contain a "
+"<placeholder-1/> directory and a PO file for any indicated additional "
+"languages."
+msgstr ""
+
+#: en_US/module-struct.xml:188(systemitem)
+d3103 1
+a3103 1
+#: en_US/module-struct.xml:189(seg)
+d3111 1
+a3111 1
+#: en_US/module-struct.xml:198(systemitem)
+d3115 1
+a3115 1
+#: en_US/module-struct.xml:201(systemitem)
+d3119 1
+a3119 1
+#: en_US/module-struct.xml:206(systemitem)
+d3123 1
+a3123 1
+#: en_US/module-struct.xml:199(seg)
+d3133 1
+a3133 1
+#: en_US/module-struct.xml:212(title)
+d3137 1
+a3137 1
+#: en_US/module-struct.xml:213(para)
+d3143 1
+a3143 1
+#: en_US/module-struct.xml:217(para)
+d3152 1
+a3152 1
+#: en_US/module-struct.xml:226(title)
+d3156 1
+a3156 1
+#: en_US/module-struct.xml:227(para)
+d3165 1
+a3165 1
+#: en_US/module-struct.xml:236(title)
+d3169 1
+a3169 1
+#: en_US/module-struct.xml:237(para)
+d3175 1
+a3175 1
+#: en_US/module-struct.xml:242(title)
+d3179 1
+a3179 1
+#: en_US/module-struct.xml:243(segtitle)
+d3183 1
+a3183 1
+#: en_US/module-struct.xml:246(systemitem)
+d3187 2
+a3188 2
+#: en_US/module-struct.xml:247(abbrev) en_US/module-struct.xml:258(abbrev)
+#: en_US/module-struct.xml:283(abbrev) en_US/module-struct.xml:288(abbrev)
+d3192 2
+a3193 2
+#: en_US/module-struct.xml:251(systemitem)
+#: en_US/module-struct.xml:261(systemitem)
+d3197 2
+a3198 2
+#: en_US/module-struct.xml:252(systemitem)
+#: en_US/module-struct.xml:262(systemitem)
+d3202 1
+a3202 1
+#: en_US/module-struct.xml:250(filename)
+d3206 1
+a3206 1
+#: en_US/module-struct.xml:247(seg)
+d3214 1
+a3214 1
+#: en_US/module-struct.xml:257(systemitem)
+d3218 1
+a3218 1
+#: en_US/module-struct.xml:260(filename)
+d3222 1
+a3222 1
+#: en_US/module-struct.xml:258(seg)
+d3229 1
+a3229 1
+#: en_US/module-struct.xml:266(systemitem)
+d3233 2
+a3234 2
+#: en_US/module-struct.xml:267(abbrev) en_US/module-struct.xml:268(abbrev)
+#: en_US/module-struct.xml:284(abbrev) en_US/module-struct.xml:289(abbrev)
+d3238 1
+a3238 1
+#: en_US/module-struct.xml:267(seg)
+d3245 1
+a3245 1
+#: en_US/module-struct.xml:272(systemitem)
+d3249 1
+a3249 1
+#: en_US/module-struct.xml:273(command)
+d3253 1
+a3253 1
+#: en_US/module-struct.xml:273(seg)
+d3259 1
+a3259 1
+#: en_US/module-struct.xml:277(systemitem)
+d3263 1
+a3263 1
+#: en_US/module-struct.xml:278(seg)
+d3267 2
+a3268 2
+#: en_US/module-struct.xml:281(systemitem)
+#: en_US/module-struct.xml:290(filename)
+d3272 1
+a3272 1
+#: en_US/module-struct.xml:283(emphasis)
+d3276 1
+a3276 1
+#: en_US/module-struct.xml:282(seg)
+d3282 1
+a3282 1
+#: en_US/module-struct.xml:287(systemitem)
+d3286 1
+a3286 1
+#: en_US/module-struct.xml:288(seg)
+d3292 1
+a3292 1
+#: en_US/module-struct.xml:295(title)
+d3296 1
+a3296 1
+#: en_US/module-struct.xml:296(para)
+d3302 1
+a3302 1
+#: en_US/module-struct.xml:300(title)
+d3306 1
+a3306 1
+#: en_US/module-struct.xml:301(para)
+d3315 1
+a3315 1
+#: en_US/module-struct.xml:309(para)
+d3321 1
+a3321 1
+#: en_US/module-struct.xml:316(title)
+d3325 1
+a3325 1
+#: en_US/module-struct.xml:317(para)
+d3333 1
+a3333 1
+#: en_US/module-struct.xml:324(para)
+d3346 1
+a3346 1
+#: en_US/module-struct.xml:338(para)
+d3353 1
+a3353 1
+#: en_US/module-struct.xml:344(para)
+d3363 1
+a3363 1
+#: en_US/module-struct.xml:354(para)
+d3372 1
+a3372 1
+#: en_US/module-struct.xml:363(para)
+d3378 1
+a3378 1
+#: en_US/module-struct.xml:369(title)
+d3382 1
+a3382 1
+#: en_US/module-struct.xml:376(title)
+d3386 1
+a3386 1
+#: en_US/module-struct.xml:377(para)
+d3391 1
+a3391 1
+#: en_US/module-struct.xml:381(para)
+d3395 1
+a3395 1
+#: en_US/module-struct.xml:385(para)
+d3404 1
+a3404 1
+#: en_US/module-struct.xml:395(title)
+d3408 1
+a3408 1
+#: en_US/module-struct.xml:396(para)
+d3416 1
+a3416 1
+#: en_US/module-struct.xml:403(para)
+d3422 1
+a3422 1
+#: en_US/module-struct.xml:409(para)
+d3426 1
+a3426 1
+#: en_US/module-struct.xml:413(para)
+d3432 1
+a3432 1
+#: en_US/module-struct.xml:418(para)
+d3438 1
+a3438 1
+#: en_US/module-struct.xml:421(replaceable)
+d3442 1
+a3442 1
+#: en_US/module-struct.xml:421(screen)
+d3476 2
+a3477 2
+"This document explains the tools used by the Fedora Documentation Project "
+"and provides writing and tagging guidelines to make Fedora documentation is "
+d3787 1
+a3787 1
+#: en_US/emacs.xml:243(primary) en_US/emacs.xml:518(application)
+d3920 13
+a3932 4
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:488(keycap)
+#: en_US/emacs.xml:493(keycap) en_US/emacs.xml:498(keycap)
+#: en_US/emacs.xml:522(keycap)
+msgid "Meta"
+d3935 5
+a3939 4
+#: en_US/emacs.xml:408(keycap) en_US/emacs.xml:493(keycap)
+#: en_US/emacs.xml:498(keycap) en_US/emacs.xml:503(keycap)
+#: en_US/emacs.xml:509(keycap) en_US/emacs.xml:515(keycap)
+msgid "x"
+d3942 2
+a3943 3
+#: en_US/emacs.xml:409(keycap) en_US/emacs.xml:494(keycap)
+#: en_US/emacs.xml:499(keycap)
+msgid "Enter"
+d3946 2
+a3947 1
+#: en_US/emacs.xml:407(seg)
+d3949 2
+a3950 2
+"<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, "
+"<placeholder-3/>"
+d3953 1
+a3953 1
+#: en_US/emacs.xml:410(seg)
+d3957 1
+a3957 22
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:438(keycap) en_US/emacs.xml:443(keycap)
+#: en_US/emacs.xml:448(keycap) en_US/emacs.xml:453(keycap)
+#: en_US/emacs.xml:458(keycap) en_US/emacs.xml:463(keycap)
+#: en_US/emacs.xml:468(keycap) en_US/emacs.xml:473(keycap)
+#: en_US/emacs.xml:478(keycap) en_US/emacs.xml:483(keycap)
+#: en_US/emacs.xml:503(keycap) en_US/emacs.xml:504(keycap)
+#: en_US/emacs.xml:509(keycap) en_US/emacs.xml:510(keycap)
+#: en_US/emacs.xml:515(keycap) en_US/emacs.xml:516(keycap)
+#: en_US/emacs.xml:527(keycap) en_US/emacs.xml:528(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:537(keycap)
+msgid "Ctrl"
+msgstr ""
+
+#: en_US/emacs.xml:425(keycap) en_US/emacs.xml:431(keycap)
+#: en_US/emacs.xml:443(keycap) en_US/emacs.xml:516(keycap)
+#: en_US/emacs.xml:527(keycap) en_US/emacs.xml:535(keycap)
+#: en_US/emacs.xml:537(keycap)
+msgid "c"
+msgstr ""
+
+#: en_US/emacs.xml:426(keycap) en_US/emacs.xml:432(keycap)
+d3961 1
+a3961 1
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:433(keycap)
+d3965 1
+a3965 1
+#: en_US/emacs.xml:427(keycap) en_US/emacs.xml:434(keycap)
+d3969 1
+a3969 1
+#: en_US/emacs.xml:425(seg)
+d3975 1
+a3975 1
+#: en_US/emacs.xml:428(seg)
+d3979 1
+a3979 1
+#: en_US/emacs.xml:431(seg)
+d3986 1
+a3986 1
+#: en_US/emacs.xml:435(seg)
+d3990 1
+a3990 1
+#: en_US/emacs.xml:438(keycap)
+d3994 1
+a3994 1
+#: en_US/emacs.xml:440(seg)
+d3998 1
+a3998 1
+#: en_US/emacs.xml:444(keycap)
+d4002 1
+a4002 1
+#: en_US/emacs.xml:443(seg)
+d4006 1
+a4006 1
+#: en_US/emacs.xml:445(seg)
+d4010 1
+a4010 1
+#: en_US/emacs.xml:448(keycap) en_US/emacs.xml:528(keycap)
+d4014 1
+a4014 1
+#: en_US/emacs.xml:450(seg)
+d4018 1
+a4018 1
+#: en_US/emacs.xml:453(keycap)
+d4022 1
+a4022 1
+#: en_US/emacs.xml:455(seg)
+d4026 1
+a4026 1
+#: en_US/emacs.xml:458(keycap)
+d4030 1
+a4030 1
+#: en_US/emacs.xml:460(seg)
+d4034 1
+a4034 1
+#: en_US/emacs.xml:463(keycap)
+d4038 1
+a4038 1
+#: en_US/emacs.xml:465(seg)
+d4042 1
+a4042 1
+#: en_US/emacs.xml:468(keycap)
+d4046 1
+a4046 1
+#: en_US/emacs.xml:470(seg)
+d4050 1
+a4050 1
+#: en_US/emacs.xml:473(keycap)
+d4054 1
+a4054 1
+#: en_US/emacs.xml:475(seg)
+d4058 1
+a4058 1
+#: en_US/emacs.xml:478(keycap) en_US/emacs.xml:510(keycap)
+d4062 1
+a4062 1
+#: en_US/emacs.xml:480(seg)
+d4066 1
+a4066 1
+#: en_US/emacs.xml:483(keycap)
+d4070 1
+a4070 1
+#: en_US/emacs.xml:485(seg)
+d4074 6
+a4079 1
+#: en_US/emacs.xml:488(keycap)
+d4083 1
+a4083 1
+#: en_US/emacs.xml:490(seg) en_US/emacs.xml:495(seg)
+d4087 11
+a4097 1
+#: en_US/emacs.xml:493(seg)
+d4103 1
+a4103 1
+#: en_US/emacs.xml:498(seg)
+d4109 1
+a4109 1
+#: en_US/emacs.xml:500(seg)
+d4113 1
+a4113 1
+#: en_US/emacs.xml:504(keycap)
+d4117 1
+a4117 8
+#: en_US/emacs.xml:503(seg) en_US/emacs.xml:509(seg) en_US/emacs.xml:515(seg)
+#: en_US/emacs.xml:527(seg) en_US/emacs.xml:535(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>, "
+"<keycombo><placeholder-3/><placeholder-4/></keycombo>"
+msgstr ""
+
+#: en_US/emacs.xml:506(seg)
+d4121 1
+a4121 1
+#: en_US/emacs.xml:512(seg)
+d4125 1
+a4125 1
+#: en_US/emacs.xml:518(seg)
+d4129 1
+a4129 1
+#: en_US/emacs.xml:522(keycap)
+d4133 1
+a4133 1
+#: en_US/emacs.xml:524(seg)
+d4137 1
+a4137 1
+#: en_US/emacs.xml:531(computeroutput)
+d4142 1
+a4142 1
+#: en_US/emacs.xml:532(computeroutput)
+d4147 1
+a4147 1
+#: en_US/emacs.xml:530(seg)
+d4153 1
+a4153 1
+#: en_US/emacs.xml:539(seg)
+d4157 1
+a4157 1
+#: en_US/emacs.xml:545(title) en_US/emacs-nxml.xml:77(title)
+d4161 1
+a4161 1
+#: en_US/emacs.xml:547(para)
+d4167 1
+a4167 1
+#: en_US/emacs.xml:554(title)
+d4171 1
+a4171 1
+#: en_US/emacs.xml:558(para)
+d4175 1
+a4175 1
+#: en_US/emacs.xml:562(para)
+d4183 1
+a4183 1
+#: en_US/emacs.xml:569(prompt)
+d4187 1
+a4187 1
+#: en_US/emacs.xml:571(para)
+d4196 1
+a4196 1
+#: en_US/emacs.xml:580(para)
+d4203 1
+a4203 1
+#: en_US/emacs.xml:597(title)
+d4207 1
+a4207 1
+#: en_US/emacs.xml:599(para)
+d4215 1
+a4215 1
+#: en_US/emacs.xml:611(title)
+d4219 1
+a4219 1
+#: en_US/emacs.xml:614(title)
+d4223 1
+a4223 1
+#: en_US/emacs.xml:615(para)
+d4231 1
+a4231 1
+#: en_US/emacs.xml:625(title)
+d4235 1
+a4235 1
+#: en_US/emacs.xml:626(para)
+d4242 1
+a4242 1
+#: en_US/emacs.xml:637(title)
+d4246 1
+a4246 1
+#: en_US/emacs.xml:638(para)
+d4254 1
+a4254 1
+#: en_US/emacs.xml:648(title)
+d4258 1
+a4258 1
+#: en_US/emacs.xml:649(para)
+d4267 1
+a4267 1
+#: en_US/emacs.xml:663(title)
+d4271 1
+a4271 1
+#: en_US/emacs.xml:664(para)
+d4280 1
+a4280 1
+#: en_US/emacs.xml:682(title) en_US/emacs-nxml.xml:127(title)
+d4284 1
+a4284 1
+#: en_US/emacs.xml:684(para)
+d4290 1
+a4290 1
+#: en_US/emacs.xml:692(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+d4294 1
+a4294 1
+#: en_US/emacs.xml:696(para)
+d4301 1
+a4301 1
+#: en_US/emacs.xml:703(para)
+d4307 1
+a4307 1
+#: en_US/emacs.xml:709(para)
+d4314 1
+a4314 1
+#: en_US/emacs.xml:718(citetitle)
+d4736 7
+a4742 12
+#: en_US/acknowledgments.xml:43(para)
+#, fuzzy
+msgid ""
+"A patch from Paul W. Frields (stickster at gmail.com) has been applied to "
+"add more explanation of the <command>screen</command> tag set to <xref "
+"linkend=\"sn-xml-tags-screen\"/>."
+msgstr ""
+"Paul W. Frields (stickstr5 at hotmail.com) 的补丁已被合并，向 <xref linkend="
+"\"s1-xml-tags-screen\"/> 中的 <command>screen</command> 标记集合添加更多解"
+"释。"
+
+#: en_US/acknowledgments.xml:49(para)
+d4755 10
+@
+
+
+1.1
+log
+ at Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge.
+@
+text
+ at d5 1
+a5 1
+"POT-Creation-Date: 2007-03-11 17:30-0400\n"
+d23 1
+a23 1
+#: en_US/rpm-info.xml:20(rights)
+d27 1
+a27 1
+#: en_US/rpm-info.xml:21(version)
+d31 1
+a31 1
+#: en_US/rpm-info.xml:24(year)
+d35 2
+a36 2571
+#: en_US/rpm-info.xml:25(year)
+msgid "2004"
+msgstr ""
+
+#: en_US/rpm-info.xml:26(year)
+msgid "2005"
+msgstr ""
+
+#: en_US/rpm-info.xml:27(year)
+msgid "2006"
+msgstr ""
+
+#: en_US/rpm-info.xml:28(holder)
+msgid "Red Hat, Inc."
+msgstr ""
+
+#: en_US/rpm-info.xml:29(holder)
+msgid "Tammy Fox"
+msgstr ""
+
+#: en_US/rpm-info.xml:30(holder)
+msgid "Johnray Fuller"
+msgstr ""
+
+#: en_US/rpm-info.xml:31(holder)
+msgid "Sandra Moore"
+msgstr ""
+
+#: en_US/rpm-info.xml:32(holder)
+msgid "Paul W. Frields"
+msgstr ""
+
+#: en_US/rpm-info.xml:34(title)
+msgid "Fedora Documentation Guide"
+msgstr ""
+
+#: en_US/rpm-info.xml:35(desc)
+msgid "Guidelines and procedures for producing documentation for Fedora"
+msgstr ""
+
+#: en_US/rpm-info.xml:42(details)
+msgid "Update to new build requirements"
+msgstr ""
+
+#: en_US/xml-tags.xml:13(title)
+msgid "DocBook XML Tags"
+msgstr "DocBook XML 标记"
+
+#: en_US/xml-tags.xml:16(primary) en_US/xml-tags.xml:34(primary)
+#, fuzzy
+msgid "XML"
+msgstr ""
+"#-#-#-#-# xml-tags.po (PACKAGE VERSION) #-#-#-#-#\n"
+"XML\n"
+"#-#-#-#-# xml-tags.po (PACKAGE VERSION) #-#-#-#-#\n"
+"translator-credits"
+
+#: en_US/xml-tags.xml:17(secondary)
+msgid "tags"
+msgstr "标记"
+
+#: en_US/xml-tags.xml:18(see) en_US/xml-tags.xml:167(primary)
+#: en_US/xml-tags.xml:205(primary) en_US/xml-tags.xml:241(primary)
+#: en_US/xml-tags.xml:276(primary) en_US/xml-tags.xml:361(primary)
+#: en_US/xml-tags.xml:386(primary) en_US/xml-tags.xml:417(primary)
+#: en_US/xml-tags.xml:471(primary) en_US/xml-tags.xml:523(primary)
+#: en_US/xml-tags.xml:555(primary) en_US/xml-tags.xml:593(primary)
+#: en_US/xml-tags.xml:659(primary) en_US/xml-tags.xml:667(primary)
+#: en_US/xml-tags.xml:673(primary) en_US/xml-tags.xml:703(primary)
+#: en_US/xml-tags.xml:709(primary) en_US/xml-tags.xml:739(primary)
+#: en_US/xml-tags.xml:745(primary) en_US/xml-tags.xml:774(primary)
+#: en_US/xml-tags.xml:780(primary) en_US/xml-tags.xml:785(primary)
+#: en_US/xml-tags.xml:791(primary) en_US/xml-tags.xml:833(primary)
+#: en_US/xml-tags.xml:861(primary) en_US/xml-tags.xml:908(primary)
+#: en_US/xml-tags.xml:963(primary) en_US/xml-tags.xml:968(primary)
+#: en_US/xml-tags.xml:1037(primary) en_US/xml-tags.xml:1047(primary)
+#: en_US/xml-tags.xml:1124(primary) en_US/xml-tags.xml:1129(primary)
+#: en_US/xml-tags.xml:1219(primary) en_US/xml-tags.xml:1224(primary)
+#: en_US/xml-tags.xml:1402(primary) en_US/xml-tags.xml:1407(primary)
+#: en_US/xml-tags.xml:1490(primary) en_US/xml-tags.xml:1533(primary)
+#: en_US/xml-tags.xml:1642(primary) en_US/xml-tags.xml:1688(primary)
+#: en_US/xml-tags.xml:1738(primary) en_US/xml-tags.xml:1782(primary)
+#: en_US/xml-tags.xml:1812(primary) en_US/xml-tags.xml:1983(primary)
+#: en_US/xml-tags.xml:2055(primary) en_US/xml-tags.xml:2174(primary)
+#: en_US/xml-tags.xml:2313(primary) en_US/xml-tags.xml:2341(primary)
+#: en_US/xml-tags.xml:2396(primary) en_US/xml-tags.xml:2437(primary)
+#: en_US/xml-tags.xml:2484(primary) en_US/writing-guidelines.xml:41(primary)
+#: en_US/writing-guidelines.xml:54(primary)
+#: en_US/writing-guidelines.xml:266(primary)
+#: en_US/writing-guidelines.xml:271(primary)
+#: en_US/writing-guidelines.xml:276(primary)
+#: en_US/writing-guidelines.xml:281(primary)
+#: en_US/writing-guidelines.xml:286(primary)
+#: en_US/writing-guidelines.xml:291(primary)
+#: en_US/writing-guidelines.xml:297(primary)
+#: en_US/writing-guidelines.xml:303(primary)
+#: en_US/writing-guidelines.xml:309(primary)
+#: en_US/writing-guidelines.xml:315(primary)
+#: en_US/writing-guidelines.xml:341(primary)
+#: en_US/writing-guidelines.xml:346(primary)
+#: en_US/writing-guidelines.xml:351(primary)
+#: en_US/writing-guidelines.xml:356(primary)
+#: en_US/writing-guidelines.xml:361(primary)
+msgid "XML tags"
+msgstr "XML 标记"
+
+#: en_US/xml-tags.xml:21(para)
+msgid ""
+"Please read this chapter carefully. This chapter describes the tags used by "
+"the Docs Project. Some of the rules described are specific to the project."
+msgstr ""
+"请仔细阅读这一章。这一章描述了 Docs Project 使用的标记。一些规则是 Docs "
+"Project 特定的。"
+
+#: en_US/xml-tags.xml:26(para)
+msgid ""
+"If these tags are used appropriately, document searches will provide "
+"meaningful results. These tags help search engines identify the information "
+"relevant to the search request. Another benefit is that all Fedora Project "
+"documents will have a similar look and feel (however, they will have some "
+"differences depending upon the output format)."
+msgstr ""
+"如果这些标记运用合适，搜索文档时可以得到有意义的结果。这些标记帮助搜索引擎确"
+"认与搜索条件相关的信息。另一个好处是使 XML XML http://www.docbook.org/tdg/en/"
+"html/docbook.html xml trade;, copy;, reg; trademark trademark/trademark "
+"trademark class=\"registered\"/trademark trademark class=\"copyright\"/"
+"trademark para para para (para screen itemizedlist orderedlist variablelist "
+"table para listitem para listitem para screen XML screen screen /screen) "
+"screen application XML application application application /application "
+"applicationMozilla/application applicationlynx/application Mozilla lynx "
+"chapter XML chapter chapter id=\"ch-sample\" title/title para/para /chapter "
+"chapter sect1, sect2, sect3 citetitle XML citetitle citetitle citetitleIG;/"
+"citetitle. IG; command XML command application command command /command "
+"commandredhat-config-keyboard/command commandsetup/command redhat-config-"
+"keyboard setup commandMAILNOVIOLATIONS/command commandtrue/"
+"commandcommandtrue/command MAILNOVIOLATIONS truetrue commandoption command "
+"command computeroutput XML computeroutput computeroutput/computeroutput "
+"emphasis XML emphasis emphasis /emphasis emphasis/emphasis emphasis/emphasis "
+"example XML example example /example example example id=\"static-ip\" title/"
+"title screen width=60 computeroutput host apex { option host-name \"apex."
+"example.com\"; hardware ethernet 00:A0:78:8E:9E:AA; fixed-address "
+"192.168.1.4; } computeroutput /screen /example host apex { option host-name "
+"\"apex.example.com\"; hardware ethernet 00:A0:78:8E:9E:AA; fixed-address "
+"192.168.1.4; } filename XML filename filename /filename filename filename/"
+"home/smoore/sam.xml/filename /home/smoore/sam.xml applicationKeyboard "
+"Configuration Tool/applicationfilenamesystem-config-keyboard/filename "
+"Keyboard Configuration Toolredhat-config-keyboard /) firstterm XML firstterm "
+"firstterm /firstterm firsttermdisk partitions/firstterm( disk partitions"
+"( footnote XML footnote footnote para /para /footnote citetitleInstallation "
+"Guide/citetitle Installation Guide figure XML figure figure id=\"fig-"
+"ksconfig-basic\" title/title mediaobject imageobject imagedata fileref=\"./"
+"figs/ksconfig/ksconfig-basic.eps\" format=\"EPS\"/ /imageobject imageobject "
+"imagedata fileref=\"./figs/ksconfig/ksconfig-basic.png\" format=\"PNG\"/ /"
+"imageobject textobject phrase /phrase /textobject /mediaobject /figure "
+"figure id=\"fig-ksconfig-basic\" == id=\"\" title/title == fileref=\"./figs/"
+"ksconfig/ksconfig-basics.eps\" == .eps fileref=\"./figs/ksconfig/ksconfig-"
+"basics.png\" == .png phrase/phrase == \" XML GUI guilabel XML GUI guilabel "
+"XML guilabel guilabel /guilabel guilabelAuthentication Configuration/"
+"guilabel Authentication Configuration guibutton XML GUI guibutton XML "
+"guibutton guibutton /guibutton guibuttonActivate on boot/guibutton Activate "
+"on boot guiicon XML GUI guiicon XML guiicon guiicon /guiicon guiiconStart "
+"Here/guiicon Start Here guimenu guimenuitem XML GUI guimenu XML guimenu XML "
+"GUI guimenuitem XML guimenuitem guimenu /guimenu guimenuitem /guimenuitem "
+"guimenuMain Menu/guimenu = guimenuitemProgramming/guimenuitem = "
+"guimenuitemEmacs/guimenuitem applicationEmacs/application Main Menu = "
+"Programming = Emacs Emacs keycap XML keycap keycap /keycap keycapEnter/"
+"keycap Enter menuchoice XML menuchoice shortcut keycap menuchoice menuchoice "
+"shortcut keycombokeycapCtrl/keycapkeycaps/keycap/keycombo /shortcut "
+"guimenuaccelF/accelile/guimenu guimenuitemaccelS/accelave/guimenuitem /"
+"menuchoice. CtrlsFileSave. keycombo XML keycombo keycombo /keycombo, keycap /"
+"keycap keycombo keycapCtrl/keycapkeycapAlt/keycapkeycapDel/keycap /keycombo. "
+"CtrlAltDel. itemizedlist XML itemizedlist XML itemizedlist itemizedlist "
+"itemizedlist variablelist itemizedlist ( para itemizedlist listitem para/"
+"para /listitem listitem para/para /listitem listitem para/para /listitem /"
+"itemizedlist orderedlist XML orderedlist orderedlist XML orderedlist "
+"orderedlist orderedlist orderedlist ( para orderedlist listitem paramdash; "
+"http://www.redhat.com/support/errata; /para /listitem listitem paramdash; /"
+"para /listitem /orderedlist http://www.redhat.com/support/errata; "
+"variablelist XML variablelist XML variablelist variablelist variablelist "
+"variablelist para variablelist varlistentry term /term listitem para/para /"
+"listitem /varlistentry varlistentry termXFree 4.0 /term listitem paraX /"
+"para /listitem /varlistentry /variablelist XFree 4.0 X frame simplelist XML "
+"simplelist XML simplelist simplelist simplelist simplelist simplelist "
+"simplelist itemizedlist XML table id=\"tb-hwinfo-hostbus\" title/title "
+"tgroup cols=\"3\" colspec colnum=\"1\" colname=\"HostBus\" colwidth=\"33\"/ "
+"colspec colnum=\"2\" colname=\"Features\" colwidth=\"34\"/ colspec colnum=\"3"
+"\" colname=\"Single\" colwidth=\"33\"/ thead row entry/entry entry/entry "
+"entrySingle-Initiator /entry /row /thead tbody row entryAdaptec 2940U2W/"
+"entry entrysimplelist memberUltra2, wide, LVD./member memberHD68 external "
+"connector./member memberOne channel, with two bus segments./member memberSet "
+"the onboard termination by using the BIOS utility./member memberOnboard "
+"termination is disabled when the power is off./member /simplelist/entry "
+"entrysimplelist memberSet the onboard termination to automatic (the "
+"default)./member memberUse the internal SCSI connector for private (non-"
+"cluster) storage./member /simplelist/entry /row row entryQlogic QLA1080/"
+"entry entrysimplelist memberUltra2, wide, LVD/member memberVHDCI external "
+"connector/member memberOne channel/member memberSet the onboard termination "
+"by using the BIOS utility./member memberOnboard termination is disabled when "
+"the power is off, unless jumpers are used to enforce termination./member /"
+"simplelist/entry entrysimplelist memberSet the onboard termination to "
+"automatic (the default)./member memberUse the internal SCSI connector for "
+"private (non-cluster) storage./member /simplelist/entry /row /tbody /tgroup /"
+"table Single-Initiator Adaptec 2940U2W Ultra2, wide, LVD. HD68 external "
+"connector. One channel, with two bus segments. Set the onboard termination "
+"by using the BIOS utility. Onboard termination is disabled when the power is "
+"off. Set the onboard termination to automatic (the default). Use the "
+"internal SCSI connector for private (non-cluster) storage. Qlogic QLA1080 "
+"Ultra2, wide, LVD VHDCI external connector One channel Set the onboard "
+"termination by using the BIOS utility. Onboard termination is disabled when "
+"the power is off, unless jumpers are used to enforce termination. Set the "
+"onboard termination to automatic (the default). Use the internal SCSI "
+"connector for private (non-cluster) storage. simplelist entry simplelist "
+"simplelist member glosslist XML glosslist XML glosslist glosslist glosslist "
+"XML glosslist glossentry glosstermapplet/glossterm glossdef para/para /"
+"glossdef /glossentry glossentry glosstermarchitecture/glossterm glossdef "
+"para/para /glossdef /glossentry glossentry glosstermarchive/glossterm "
+"glossdef para/para /glossdef /glossentry /glosslist applet architecture "
+"archive option XML option option /option option commandls/command option-la/"
+"option ls -la XML indexterm -- primaryfoo/primary -- secondarybar/secondary "
+"-- \"bar\" /indexterm -- foo bar seealso seealso seealso indexterm "
+"primarySWAK/primary seealsosalutations/seealso /indexterm indexterm "
+"primarysalutations/primary /indexterm SWAK Salutations Salutations see see "
+"indexterm primaryGuinness/primary seebeer/see -- \"beer\" /indexterm "
+"indexterm primarybeer/primary /indexterm Guinness Beer Beer generated-index."
+"html generate.index para XML para para /para para para (para screen "
+"itemizedlist orderedlist variablelist table part parts XML part part part id="
+"\"pt-foo\" partintro para/para CHAPTER; ANOTHER-CHAPTER; /part part id=\"pt-"
+"setup\" title/title partintro paraFC; /para /partintro prompt XML prompt "
+"prompt /prompt promptLILO:/prompt promptC:\\/prompt LILO: C:\\ screen "
+"replaceable XML replaceable replaceable /replaceable replaceable foo-"
+"replaceableversion-number/replaceable.replaceablearch/replaceable.rpm foo-"
+"version-number.arch.rpm screen XML screen screen screen /screen screen "
+"screen screen computeroutput, userinput, replaceable screen screen screen "
+"screen screen lt;paragt; /screen para screen screen computeroutput userinput "
+"para /parascreenuserinputcommand -sw file1/userinput/screenpara /"
+"parascreencomputeroutputCompleted, time = 0.12 sec/computeroutput/screen "
+"command -sw file1 Completed, time = 0.12 sec screen screen userinput "
+"computeroutput userinput para filename/etc/sysconfig/init/filename /"
+"parascreen GRAPHICAL=userinputyes/userinput/screen /etc/sysconfig/init "
+"GRAPHICAL=yes screen replaceable section XML )sect1 sect1 id=\"s1-uniquename"
+"\" title/title para /para sect2 id=\"s2-uniquename\" title/title para /para "
+"sect3 id=\"s3-uniquename\" title/title para /para /sect3 /sect2 /sect1 "
+"section section id=\"sn-uniquename\" title/title para /para /section section "
+"id=\"sn-anothername\" title/title para /para /section table XML table table "
+"id=\"tb-mockup-before-begin\" \"tb-mockup-before-begin\" titleAvailable "
+"Features of GNOME and KDE/title tgroup cols=\"3\" colspec colnum=\"1\" "
+"colname=\"Features\" colwidth=\"3\"/ colspec colnum=\"1\" colname=\"Features"
+"\" colwidth=\"3\" colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/ "
+"colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/ thead row entryFeatures/"
+"entry entryGNOME/entry entryKDE/entry /row /thead tbody row entry/entry "
+"entryyes/entry entryyes/entry /row row entry/entry entryyes/entry entryyes/"
+"entry /row row entry/entry entryyes /entry entryyes /entry /row /tbody /"
+"tgroup /table Available Features of GNOME and KDE GNOME KDE yes yes yes yes "
+"yes yes XML table Emacs simplelist member table id=\"tb-hardware-powerswitch"
+"\" title/title tgroup cols=\"4\" colspec colnum=\"1\" colname=\"Hardware\" "
+"colwidth=\"2\"/ colspec colnum=\"2\" colname=\"Quantity\" colwidth=\"2\"/ "
+"colspec colnum=\"3\" colname=\"Description\" colwidth=\"6\"/ colspec colnum="
+"\"4\" colname=\"Required\" colwidth=\"2\"/ thead row entryHardware/entry "
+"entryQuantity/entry entryDescription/entry entryRequired/entry /row /thead "
+"tbody row entrySerial power switches/entry entryTwo/entry entrysimplelist "
+"memberPower switches enable each cluster system to power-cycle the other "
+"cluster system. Note that clusters are configured with either serial or "
+"network attached power switches and not both./member memberThe following "
+"serial attached power switch has been fully tested:/member memberRPS-10 "
+"(model M/HD in the US, and model M/EC in Europe) /member memberLatent "
+"support is provided for the following serial attached power switch. This "
+"switch has not yet been fully tested:/member memberAPC Serial On/Off Switch "
+"(partAP9211), ulink url=\"http://www.apc.com/\"http://www.apc.com//ulink/"
+"member /simplelist/entry entryStrongly recommended for data integrity under "
+"all failure conditions/entry /row /tbody /tgroup /table simplelist entry "
+"Hardware Quantity Required Serial power switches Two Power switches enable "
+"each cluster system to power-cycle the other cluster system. Note that "
+"clusters are configured with either serial or network attached power "
+"switches and not both.The following serial attached power switch has been "
+"fully tested:RPS-10 (model M/HD in the US, and model M/EC in Europe)Latent "
+"support is provided for the following serial attached power switch. This "
+"switch has not yet been fully tested:APC Serial On/Off Switch (partAP9211), "
+"http://www.apc.com/ Strongly recommended for data integrity under all "
+"failure conditions trademark XML trademark trade;, copy;, reg; trademark "
+"trademark/trademark trademark class=\"registered\"/trademark trademark class="
+"\"copyright\"/trademark userinput XML userinput userinput userinputdd "
+"if=boot.img of=/dev/fd0 bs=1440k/userinput dd if=boot.img of=/dev/fd0 "
+"bs=1440k ulink XML ulink mdash; ulink url=\"http://www.redhat.com/support/"
+"errata/\" http://www.redhat.com/support/errata//ulink; http://www.redhat.com/"
+"support/errata/; /)http://www.redhat.com/ wordasword XML wordasword "
+"wordasword wordasword wordasword commandgrep/command wordaswordlinux/"
+"wordaswordcommandgrep linux/command grep linuxgrep linux xref XML xref xref "
+"xref linkend=\"ch-tutorial\"/xref xref linkend=\"s1-tutorial-parent\"/xref"
+
+#: en_US/xml-tags.xml:35(secondary)
+msgid "general tag information"
+msgstr ""
+
+#: en_US/xml-tags.xml:38(para)
+msgid ""
+"Most tags in XML must have an opening and closing tag. A few tags, such as "
+"<sgmltag class=\"emptytag\">xref</sgmltag>, have no content and close "
+"themselves. Additionally, proper XML conventions say that there must be a "
+"unique identifier for sections, chapters, figures, tables, and so on, so "
+"that they may be correctly identified, and cross referenced if needed."
+msgstr ""
+
+#: en_US/xml-tags.xml:45(para)
+msgid ""
+"Although XML is capable of handling many document types, the format "
+"discussed here is the article format."
+msgstr ""
+
+#: en_US/xml-tags.xml:48(para) en_US/writing-guidelines.xml:32(para)
+msgid ""
+"This chapter only discusses tags used for documentation for the Fedora "
+"Project, not all available DocBook XML tags. For the complete list, refer to "
+"<ulink url=\"http://www.docbook.org/tdg/en/html/docbook.html\"/>."
+msgstr ""
+
+#: en_US/xml-tags.xml:56(title)
+msgid "Tags and Entities Caveats"
+msgstr ""
+
+#: en_US/xml-tags.xml:59(primary) en_US/writing-guidelines.xml:137(primary)
+msgid "xml tags"
+msgstr ""
+
+#: en_US/xml-tags.xml:60(secondary)
+#: en_US/writing-guidelines.xml:138(secondary)
+msgid "caveats"
+msgstr ""
+
+#: en_US/xml-tags.xml:63(para)
+msgid ""
+"It is very important that you remember the caveats in this section. Even "
+"though they are more strict than valid DocBook XML, these rules exist so "
+"that both the HTML and PDF outputs look proper."
+msgstr ""
+
+#: en_US/xml-tags.xml:71(term) en_US/writing-guidelines.xml:149(term)
+msgid "Do Not Use Trademark Entities"
+msgstr ""
+
+#: en_US/xml-tags.xml:73(para)
+msgid ""
+"Do not use the trademark entities <sgmltag class=\"genentity\">trade</"
+"sgmltag>, <sgmltag class=\"genentity\">copy</sgmltag>, or <sgmltag class="
+"\"genentity\">reg</sgmltag> because they do not produce HTML output that "
+"works for all charsets. The HTML output produces by these entities are "
+"declared in the DTD and cannot be changed via the stylesheet."
+msgstr ""
+
+#: en_US/xml-tags.xml:80(para)
+msgid ""
+"Instead, use the <sgmltag class=\"element\">trademark</sgmltag> tag and its "
+"associates classes as follows:"
+msgstr ""
+
+#: en_US/xml-tags.xml:85(para) en_US/writing-guidelines.xml:164(para)
+msgid ""
+"<sgmltag class=\"starttag\">trademark</sgmltag>trademark symbol after "
+"me<sgmltag class=\"endtag\">trademark</sgmltag>"
+msgstr ""
+
+#: en_US/xml-tags.xml:91(para) en_US/writing-guidelines.xml:170(para)
+msgid ""
+"<sgmltag class=\"starttag\">trademark class=\"registered\"</"
+"sgmltag>registered trademark symbol after me<sgmltag class=\"endtag"
+"\">trademark</sgmltag>"
+msgstr ""
+
+#: en_US/xml-tags.xml:97(para) en_US/writing-guidelines.xml:176(para)
+msgid ""
+"<sgmltag class=\"starttag\">trademark class=\"copyright\"</sgmltag>copyright "
+"symbol after me<sgmltag class=\"endtag\">trademark</sgmltag>"
+msgstr ""
+
+#: en_US/xml-tags.xml:105(term) en_US/writing-guidelines.xml:184(term)
+msgid "Content inside <sgmltag>para</sgmltag> tags"
+msgstr ""
+
+#: en_US/xml-tags.xml:107(para)
+msgid ""
+"Do not use <sgmltag>para</sgmltag> tags around anything other than a simple "
+"paragraph. Doing so will create additional white space within the text "
+"itself in the PDF version."
+msgstr ""
+
+#: en_US/xml-tags.xml:112(para)
+msgid ""
+"Specifically, do not use <sgmltag>para</sgmltag> tags around the following "
+"(or, to put this another way, do not embed the following within "
+"<sgmltag>para</sgmltag> tags):"
+msgstr ""
+
+#: en_US/xml-tags.xml:118(sgmltag) en_US/xml-tags.xml:1810(command)
+#: en_US/xml-tags.xml:1813(secondary)
+#: en_US/writing-guidelines.xml:198(sgmltag)
+msgid "screen"
+msgstr ""
+
+#: en_US/xml-tags.xml:121(sgmltag) en_US/xml-tags.xml:960(command)
+#: en_US/xml-tags.xml:964(command) en_US/xml-tags.xml:970(tertiary)
+#: en_US/xml-tags.xml:975(command) en_US/writing-guidelines.xml:201(sgmltag)
+msgid "itemizedlist"
+msgstr ""
+
+#: en_US/xml-tags.xml:124(sgmltag) en_US/xml-tags.xml:1038(command)
+#: en_US/xml-tags.xml:1043(command) en_US/xml-tags.xml:1049(tertiary)
+#: en_US/writing-guidelines.xml:204(sgmltag)
+msgid "orderedlist"
+msgstr ""
+
+#: en_US/xml-tags.xml:127(sgmltag) en_US/xml-tags.xml:1125(command)
+#: en_US/xml-tags.xml:1131(tertiary) en_US/xml-tags.xml:1136(command)
+#: en_US/writing-guidelines.xml:207(sgmltag)
+msgid "variablelist"
+msgstr ""
+
+#: en_US/xml-tags.xml:130(sgmltag) en_US/xml-tags.xml:2052(command)
+#: en_US/xml-tags.xml:2056(secondary) en_US/xml-tags.xml:2175(secondary)
+#: en_US/writing-guidelines.xml:111(sgmltag)
+#: en_US/writing-guidelines.xml:210(sgmltag)
+msgid "table"
+msgstr ""
+
+#: en_US/xml-tags.xml:136(term)
+msgid ""
+"Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+"sgmltag> tags"
+msgstr ""
+
+#: en_US/xml-tags.xml:139(para)
+msgid ""
+"Content inside <sgmltag>para</sgmltag> tags within <sgmltag>listitem</"
+"sgmltag> tags <emphasis>must</emphasis> start immediately after the "
+"beginning <sgmltag class=\"starttag\">para</sgmltag> tag to avoid extra "
+"white space in the PDF version."
+msgstr ""
+
+#: en_US/xml-tags.xml:148(term) en_US/writing-guidelines.xml:227(term)
+msgid "Content inside <sgmltag>screen</sgmltag> tags"
+msgstr ""
+
+#: en_US/xml-tags.xml:150(para) en_US/writing-guidelines.xml:229(para)
+msgid ""
+"The content inside <sgmltag>screen</sgmltag> tags (<sgmltag class=\"starttag"
+"\">screen</sgmltag> and <sgmltag class=\"endtag\">screen</sgmltag>) "
+"<emphasis>must</emphasis> be flush left in the XML file; otherwise, the "
+"extraneous whitespace will appear in the HTML version."
+msgstr ""
+
+#: en_US/xml-tags.xml:164(sgmltag) en_US/xml-tags.xml:168(secondary)
+#: en_US/xml-tags.xml:182(sgmltag) en_US/xml-tags.xml:183(sgmltag)
+#: en_US/xml-tags.xml:184(sgmltag) en_US/xml-tags.xml:185(sgmltag)
+msgid "application"
+msgstr ""
+
+#: en_US/xml-tags.xml:171(para)
+msgid ""
+"An application is the name of a GUI software program. A command is the name "
+"of an executable (text) program or a software command."
+msgstr ""
+
+#: en_US/xml-tags.xml:174(para)
+msgid ""
+"The <sgmltag class=\"starttag\">application</sgmltag> and <sgmltag class="
+"\"endtag\">application</sgmltag> tags allow you to refer to an application "
+"or program. For example, the following XML:"
+msgstr ""
+
+#: en_US/xml-tags.xml:180(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To view the Web in Linux, you can use\n"
+"<placeholder-1/>Mozilla<placeholder-2/> \n"
+"or <placeholder-3/>lynx<placeholder-4/> if\n"
+"you only want a text-based browser.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:190(para)
+msgid "produces the following output:"
+msgstr ""
+
+#: en_US/xml-tags.xml:194(para)
+msgid ""
+"To view the Web in Linux, you can use <application>Mozilla</application> or "
+"<application>lynx</application> if you only want a text-based browser."
+msgstr ""
+
+#: en_US/xml-tags.xml:202(sgmltag) en_US/xml-tags.xml:206(secondary)
+#: en_US/writing-guidelines.xml:99(sgmltag)
+msgid "chapter"
+msgstr ""
+
+#: en_US/xml-tags.xml:209(para)
+msgid "A DocBook book can be divided into chapters such as:"
+msgstr ""
+
+#: en_US/xml-tags.xml:214(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<!--$Id: xml-tags.xml,v 1.5 2007/02/04 14:55:28 pfrields Exp $ -->\n"
+"\n"
+" <chapter id=\"ch-sample\">\n"
+" <title>Sample Chapter</title>\n"
+"\n"
+" <para>This is a sample chapter, showing you the XML tags used to create a\n"
+" chapter, sections, and subsections.</para>\n"
+" \n"
+" </chapter>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:227(para)
+msgid ""
+"The chapter can also be further divided into sections (<sgmltag>section</"
+"sgmltag>, <sgmltag>section</sgmltag>, <sgmltag>sect3</sgmltag>, etc.). Refer "
+"to <xref linkend=\"sn-xml-tags-sections\"/> for details."
+msgstr ""
+
+#: en_US/xml-tags.xml:238(sgmltag) en_US/xml-tags.xml:242(secondary)
+#: en_US/xml-tags.xml:262(sgmltag)
+msgid "citetitle"
+msgstr ""
+
+#: en_US/xml-tags.xml:249(para)
+msgid ""
+"An entity is a short hand way of referring to some predefined content, such "
+"as a title or name. It can be defined within the parent document or within a "
+"set of files that your DTD references for your specific documentation set."
+msgstr ""
+
+#: en_US/xml-tags.xml:246(para)
+msgid ""
+"The <sgmltag>citetitle</sgmltag> tag provides formatting for a specific "
+"references (title can be manually typed out or if already defined within "
+"your document set, given as an entity<placeholder-1/> )."
+msgstr ""
+
+#: en_US/xml-tags.xml:257(para) en_US/xml-tags.xml:2456(para)
+msgid "For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:262(sgmltag)
+msgid "IG"
+msgstr ""
+
+#: en_US/xml-tags.xml:261(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<placeholder-1/><placeholder-2/><placeholder-3/>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:265(para)
+msgid ""
+"The output looks like <citetitle>Installation Guide</citetitle> because "
+"<sgmltag class=\"genentity\">IG</sgmltag> is an entity."
+msgstr ""
+
+#: en_US/xml-tags.xml:273(sgmltag) en_US/xml-tags.xml:277(secondary)
+msgid "command"
+msgstr ""
+
+#: en_US/xml-tags.xml:280(para)
+msgid ""
+"An application is the name of a GUI software program. A command is the name "
+"of an executable (text) program or a software command. Any program that is a "
+"command line or text-based only tool is marked with <sgmltag>command</"
+"sgmltag> tags."
+msgstr ""
+
+#: en_US/xml-tags.xml:286(para)
+msgid ""
+"If you have text that is a command, use the <sgmltag class=\"starttag"
+"\">command</sgmltag> and <sgmltag class=\"endtag\">command</sgmltag> tags "
+"such as:"
+msgstr ""
+
+#: en_US/xml-tags.xml:294(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To change your keyboard after installation, become root \n"
+"and use the <command>redhat-config-keyboard</command> command, \n"
+"or you can type <command>setup</command> at the root prompt.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:301(para) en_US/xml-tags.xml:374(para)
+#: en_US/xml-tags.xml:402(para) en_US/xml-tags.xml:446(para)
+#: en_US/xml-tags.xml:485(para) en_US/xml-tags.xml:500(para)
+#: en_US/xml-tags.xml:540(para) en_US/xml-tags.xml:575(para)
+#: en_US/xml-tags.xml:689(para) en_US/xml-tags.xml:725(para)
+#: en_US/xml-tags.xml:759(para) en_US/xml-tags.xml:816(para)
+#: en_US/xml-tags.xml:849(para) en_US/xml-tags.xml:887(para)
+#: en_US/xml-tags.xml:927(para) en_US/xml-tags.xml:1515(para)
+#: en_US/xml-tags.xml:1756(para) en_US/xml-tags.xml:1800(para)
+#: en_US/xml-tags.xml:1868(para) en_US/xml-tags.xml:2357(para)
+#: en_US/xml-tags.xml:2411(para) en_US/xml-tags.xml:2464(para)
+#: en_US/xml-tags.xml:2504(para)
+msgid "The output:"
+msgstr ""
+
+#: en_US/xml-tags.xml:304(para)
+msgid ""
+"To change your keyboard after installation, become root and use the "
+"<command>redhat-config-keyboard</command> command, or you can type "
+"<command>setup</command> at the root prompt."
+msgstr ""
+
+#: en_US/xml-tags.xml:310(para)
+msgid "Another example would be:"
+msgstr ""
+
+#: en_US/xml-tags.xml:313(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<command>MAILNOVIOLATIONS</command> — If set\n"
+"to <command>true</command> this option tells Tripwire to\n"
+"email a report at a regular interval regardless of whether or not\n"
+"any violations have occured. The default value is\n"
+"<command>true</command>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:322(para)
+msgid "with the output:"
+msgstr ""
+
+#: en_US/xml-tags.xml:326(para)
+msgid ""
+"<command>MAILNOVIOLATIONS</command>— If set to <command>true</command> "
+"this variable tells Tripwire to email a report at a regular interval "
+"regardless of whether or not any violations have occured. The default value "
+"is <command>true</command>."
+msgstr ""
+
+#: en_US/xml-tags.xml:334(title) en_US/xml-tags.xml:509(title)
+#: en_US/xml-tags.xml:988(title) en_US/xml-tags.xml:1063(title)
+#: en_US/xml-tags.xml:1147(title) en_US/xml-tags.xml:1387(title)
+#: en_US/xml-tags.xml:1500(title) en_US/xml-tags.xml:1769(title)
+#: en_US/xml-tags.xml:1930(title) en_US/xml-tags.xml:2422(title)
+#: en_US/writing-guidelines.xml:394(title) en_US/emacs.xml:265(title)
+#: en_US/emacs.xml:565(title) en_US/emacs-nxml.xml:160(title)
+msgid "Note"
+msgstr ""
+
+#: en_US/xml-tags.xml:334(para)
+msgid ""
+"In this example, the option value (true) is defined with a <command> "
+"tag set. Because a option is a configuration file option (command line "
+"options which would use the <option> tag set), and because there is no "
+"configuration file option tag available to use, we are extending the <"
+"command> tag set to define options in a configuration file."
+msgstr ""
+
+#: en_US/xml-tags.xml:342(para)
+msgid ""
+"Terms marked with <command>command</command> tags because there aren't exact "
+"tags for them:"
+msgstr ""
+
+#: en_US/xml-tags.xml:348(para)
+msgid "Options in configuration files such as Apache directives"
+msgstr ""
+
+#: en_US/xml-tags.xml:351(para)
+msgid "daemon names"
+msgstr ""
+
+#: en_US/xml-tags.xml:358(command) en_US/xml-tags.xml:362(secondary)
+msgid "computeroutput"
+msgstr ""
+
+#: en_US/xml-tags.xml:365(para)
+msgid "To show computer output use the following tags:"
+msgstr ""
+
+#: en_US/xml-tags.xml:369(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<computeroutput>Do you want to delete this file? y n</computeroutput>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:378(computeroutput)
+#, no-wrap
+msgid "Do you really want to delete this file? y n"
+msgstr ""
+
+#: en_US/xml-tags.xml:383(command) en_US/xml-tags.xml:387(secondary)
+msgid "emphasis"
+msgstr ""
+
+#: en_US/xml-tags.xml:390(para)
+msgid ""
+"To emphasis content, use the <command><emphasis></command> and "
+"<command></emphasis></command> tags. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:395(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"This installation <emphasis>will remove all</emphasis> existing\n"
+"Linux partitions on <emphasis>all</emphasis> hard drives in your\n"
+"system; non-Linux partitions will not be removed.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:406(para)
+msgid ""
+"This installation <emphasis>will remove all</emphasis> existing Linux "
+"partitions on <emphasis>all</emphasis> hard drives in your system; non-Linux "
+"partitions will not be removed."
+msgstr ""
+
+#: en_US/xml-tags.xml:414(command) en_US/xml-tags.xml:418(secondary)
+#: en_US/writing-guidelines.xml:123(sgmltag)
+msgid "example"
+msgstr ""
+
+#: en_US/xml-tags.xml:421(para)
+msgid ""
+"The <command><example></command> and <command></example></"
+"command> tags are used to format text within a document and is great for "
+"adding emphasis to show examples of code, exercises, and more."
+msgstr ""
+
+#: en_US/xml-tags.xml:426(para)
+msgid ""
+"The <command><example></command> tag set should be given an ID and "
+"title:"
+msgstr ""
+
+#: en_US/xml-tags.xml:429(screen)
+#, no-wrap
+msgid ""
+"\n"
+"\t<example id=\"static-ip\">\n"
+"\t <title>Static IP Address using DHCP</title>\n"
+"\n"
+"<screen width=60>\n"
+"<computeroutput>\n"
+"host apex {\n"
+" option host-name \"apex.example.com\";\n"
+" hardware ethernet 00:A0:78:8E:9E:AA; \n"
+" fixed-address 192.168.1.4;\n"
+"}\n"
+"<computeroutput>\n"
+"</screen>\n"
+"\n"
+"\t</example>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:451(title)
+msgid "Static IP Address using DHCP"
+msgstr ""
+
+#: en_US/xml-tags.xml:454(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"host apex {\n"
+" option host-name \"apex.example.com\";\n"
+" hardware ethernet 00:A0:78:8E:9E:AA; \n"
+" fixed-address 192.168.1.4;\n"
+"}\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:468(command) en_US/xml-tags.xml:472(secondary)
+msgid "filename"
+msgstr ""
+
+#: en_US/xml-tags.xml:475(para)
+msgid ""
+"The <command><filename></command> and <command></filename></"
+"command> tags define a filename or path to a file. Since directories are "
+"just special files, they are marked with the <command>filename</command> "
+"tags as well. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:481(screen)
+#, no-wrap
+msgid ""
+"\n"
+"Edit the <filename>/home/smoore/sam.xml</filename> file to make\n"
+"changes or add comments.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:488(para)
+msgid ""
+"Edit the <filename>/home/smoore/sam.xml</filename> file to make changes or "
+"add comments."
+msgstr ""
+
+#: en_US/xml-tags.xml:493(para)
+msgid "They are also used to markup an RPM package name. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:496(screen)
+#, no-wrap
+msgid ""
+"\n"
+"To use the <application>Keyboard Configuration Tool</application>, the\n"
+"<filename>system-config-keyboard</filename> RPM package must be installed.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:503(para)
+msgid ""
+"To use the <application>Keyboard Configuration Tool</application>, the "
+"<command>redhat-config-keyboard</command> RPM package must be installed."
+msgstr ""
+
+#: en_US/xml-tags.xml:510(para)
+msgid ""
+"Directory names must end with a forward slash (<computeroutput>/</"
+"computeroutput>) to distinguish them from file names."
+msgstr ""
+
+#: en_US/xml-tags.xml:520(command) en_US/xml-tags.xml:524(secondary)
+msgid "firstterm"
+msgstr ""
+
+#: en_US/xml-tags.xml:527(para)
+msgid ""
+"The <command><firstterm></command> and <command></firstterm></"
+"command> tags helps to define a word that may be unfamiliar to the user, but "
+"that will be seen commonly throughout the text. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:534(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Nearly every modern-day operating system uses <firstterm>disk\n"
+"partitions</firstterm>, and Fedora Core is no exception.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:544(para)
+msgid ""
+"Nearly every modern-day operating system uses <firstterm>disk partitions</"
+"firstterm>, and Fedora Core is no exception."
+msgstr ""
+
+#: en_US/xml-tags.xml:552(command) en_US/xml-tags.xml:556(secondary)
+msgid "footnote"
+msgstr ""
+
+#: en_US/xml-tags.xml:559(para)
+msgid "If you need to make a footnote, use the following example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:563(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"For those of you who need to perform a server-class\n"
+"<footnote>\n"
+"<para>\n"
+"A server-class installation sets up a typical server\n"
+"environment. Note, no graphical environment is \n"
+"installed during a server-class installation.\n"
+"</para> \n"
+"</footnote> installation, refer to the <citetitle>Installation Guide</citetitle>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:580(para)
+msgid ""
+"A server-class installation sets up a typical server environment. Please "
+"note, no graphical environment is installed during a server-class "
+"installation."
+msgstr ""
+
+#: en_US/xml-tags.xml:579(para)
+msgid ""
+"For those of you who need to perform a server-class <placeholder-1/> "
+"installation, refer to the <citetitle>Installation Guide</citetitle>."
+msgstr ""
+
+#: en_US/xml-tags.xml:590(command) en_US/xml-tags.xml:594(secondary)
+#: en_US/writing-guidelines.xml:107(sgmltag)
+msgid "figure"
+msgstr ""
+
+#: en_US/xml-tags.xml:598(title) en_US/xml-tags.xml:1827(title)
+#: en_US/writing-guidelines.xml:424(title) en_US/emacs-nxml.xml:96(title)
+msgid "Important"
+msgstr "注意"
+
+#: en_US/xml-tags.xml:599(para)
+msgid ""
+"Order matters! The EPS file <emphasis>must</emphasis> be declared first."
+msgstr ""
+
+#: en_US/xml-tags.xml:605(para)
+msgid "An example figure declaration:"
+msgstr ""
+
+#: en_US/xml-tags.xml:610(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<figure id=\"fig-ksconfig-basic\">\n"
+" <title>Basic Configuration</title>\n"
+" <mediaobject>\n"
+" <imageobject>\n"
+" <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.eps\"\n"
+" format=\"EPS\"/>\n"
+" </imageobject>\n"
+" <imageobject>\n"
+" <imagedata fileref=\"./figs/ksconfig/ksconfig-basic.png\"\n"
+" format=\"PNG\"/>\n"
+" </imageobject>\n"
+" <textobject>\n"
+" <phrase>\n"
+" Some text description of this image\n"
+" </phrase>\n"
+" </textobject>\n"
+" </mediaobject>\n"
+"</figure>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:632(para)
+msgid "The following describes what needs to be edited:"
+msgstr ""
+
+#: en_US/xml-tags.xml:637(emphasis)
+msgid "==> id=\"\" would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:639(emphasis)
+msgid "==> title would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:641(emphasis)
+msgid "==> .eps location would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:643(emphasis)
+msgid "==> .png location would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:645(emphasis)
+msgid "==> \"Some text...\" would be edited"
+msgstr ""
+
+#: en_US/xml-tags.xml:636(screen)
+#, no-wrap
+msgid ""
+"\n"
+"<figure id=\"fig-ksconfig-basic\"> <placeholder-1/>\n"
+"\n"
+"<title>Basic Configuration</title> <placeholder-2/>\n"
+"\n"
+"fileref=\"./figs/ksconfig/ksconfig-basics.eps\"> <placeholder-3/>\n"
+"\n"
+"fileref=\"./figs/ksconfig/ksconfig-basics.png\"> <placeholder-4/>\n"
+" \n"
+"<phrase>Some text description of this image</phrase> <placeholder-5/>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:648(para)
+msgid ""
+"For more information on taking screenshots, refer to <xref linkend=\"sn-"
+"screenshots\"/>."
+msgstr ""
+
+#: en_US/xml-tags.xml:656(title)
+msgid "GUI Tags"
+msgstr ""
+
+#: en_US/xml-tags.xml:660(secondary) en_US/xml-tags.xml:668(secondary)
+#: en_US/xml-tags.xml:704(secondary) en_US/xml-tags.xml:740(secondary)
+#: en_US/xml-tags.xml:775(secondary) en_US/xml-tags.xml:786(secondary)
+msgid "GUI tags"
+msgstr ""
+
+#: en_US/xml-tags.xml:664(command) en_US/xml-tags.xml:669(tertiary)
+#: en_US/xml-tags.xml:674(secondary)
+msgid "guilabel"
+msgstr ""
+
+#: en_US/xml-tags.xml:677(para)
+msgid ""
+"Use the <command><guilabel></command> and <command></guilabel></"
+"command> tags as a default for GUI descriptions, like a screen name or "
+"screen title. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:683(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"The <guilabel>Authentication Configuration</guilabel> screen \n"
+"shows you how to make your system more secure.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:693(para)
+msgid ""
+"The <guilabel>Authentication Configuration</guilabel> screen shows you how "
+"to make your system more secure."
+msgstr ""
+
+#: en_US/xml-tags.xml:700(command) en_US/xml-tags.xml:705(tertiary)
+#: en_US/xml-tags.xml:710(secondary)
+msgid "guibutton"
+msgstr ""
+
+#: en_US/xml-tags.xml:713(para)
+msgid ""
+"Use the <command><guibutton></command> and <command></guibutton>"
+"</command> tags to denote a button on a screen or menu. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:719(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Check the <guibutton>Activate on boot</guibutton> button \n"
+"to have the X Window System start automatically.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:729(para)
+msgid ""
+"Check the <guibutton>Activate on boot</guibutton> button to have the X "
+"Window System start automatically."
+msgstr ""
+
+#: en_US/xml-tags.xml:736(command) en_US/xml-tags.xml:741(tertiary)
+#: en_US/xml-tags.xml:746(secondary)
+msgid "guiicon"
+msgstr ""
+
+#: en_US/xml-tags.xml:749(para)
+msgid ""
+"The <command><guiicon></command> and <command></guiicon></"
+"command> tags are used to denote a panel or desktop icon. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:754(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Double-click the <guiicon>Start Here</guiicon> icon on the desktop.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:763(para)
+msgid "Double-click the <guiicon>Start Here</guiicon> icon on the desktop."
+msgstr ""
+
+#: en_US/xml-tags.xml:770(title)
+msgid "<command>guimenu</command> and <command>guimenuitem</command>"
+msgstr ""
+
+#: en_US/xml-tags.xml:776(tertiary) en_US/xml-tags.xml:781(secondary)
+msgid "guimenu"
+msgstr ""
+
+#: en_US/xml-tags.xml:787(tertiary) en_US/xml-tags.xml:792(secondary)
+msgid "guimenuitem"
+msgstr ""
+
+#: en_US/xml-tags.xml:795(para)
+msgid ""
+"To note a menu (like in the installation program or within the control "
+"panel), use the <command><guimenu></command> and <command></"
+"guimenu></command> tags."
+msgstr ""
+
+#: en_US/xml-tags.xml:801(para)
+msgid ""
+"To note submenu items, use the <command><guimenuitem></command> and "
+"<command></guimenuitem></command> tags. (Please note that there should "
+"not be any breaks between these commands, but for printing purposes breaks "
+"have been inserted). For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:808(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Select \n"
+"<guimenu>Main Menu</guimenu> =>\n"
+"\t <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> to start the \n"
+"<application>Emacs</application> text editor.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:820(para)
+msgid ""
+"From the control panel, click on <guimenu>Main Menu</guimenu> => "
+"<guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</"
+"guimenuitem> to start the <application>Emacs</application> text editor."
+msgstr ""
+
+#: en_US/xml-tags.xml:830(command) en_US/xml-tags.xml:834(secondary)
+msgid "keycap"
+msgstr ""
+
+#: en_US/xml-tags.xml:837(para)
+msgid ""
+"To denote a specific key, you will need to use the <command><keycap></"
+"command> and <command></keycap></command> tags. Brackets are "
+"automatically added around the keycap, so do not add them in your XML code. "
+"For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:844(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To make your selection, press the <keycap>Enter</keycap> key.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:853(para)
+msgid "To make your selection, press the <keycap>Enter</keycap> key."
+msgstr ""
+
+#: en_US/xml-tags.xml:858(command) en_US/xml-tags.xml:862(secondary)
+msgid "menuchoice"
+msgstr ""
+
+#: en_US/xml-tags.xml:865(para)
+msgid ""
+"Often using a mouse is tedious for common tasks. Therefore, programmers "
+"often build in keyboard-shortcuts to simplify their program. These should be "
+"described using the shortcut tag as a wrapper for the keyboard tags. The "
+"shortcut tag must be wrapped inside the menuchoice tag. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:874(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Go to the menu bar and choose: \n"
+" <menuchoice>\n"
+" <shortcut>\n"
+" <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>\n"
+" </shortcut>\n"
+" <guimenu><accel>F</accel>ile</guimenu>\n"
+" <guimenuitem><accel>S</accel>ave</guimenuitem>\n"
+" </menuchoice>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:891(para)
+msgid ""
+"Go to the menu bar and choose: <menuchoice><shortcut><keycombo><keycap>Ctrl</"
+"keycap><keycap>s</keycap></keycombo></shortcut><guimenu><accel>F</accel>ile</"
+"guimenu><guimenuitem><accel>S</accel>ave</guimenuitem></menuchoice>."
+msgstr ""
+
+#: en_US/xml-tags.xml:905(command) en_US/xml-tags.xml:909(secondary)
+msgid "keycombo"
+msgstr ""
+
+#: en_US/xml-tags.xml:912(para)
+msgid ""
+"To illustrate a key combination, you need to use the <command><"
+"keycombo></command> and <command></keycombo></command>, "
+"<command><keycap></command> and <command></keycap></command> "
+"tags. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:920(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"To reboot your system, press <keycombo>\n"
+"<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap>\n"
+"</keycombo>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:931(para)
+msgid ""
+"To reboot your system, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</"
+"keycap><keycap>Del</keycap></keycombo>."
+msgstr ""
+
+#: en_US/xml-tags.xml:942(title) en_US/style.xml:1377(term)
+msgid "Lists"
+msgstr ""
+
+#: en_US/xml-tags.xml:945(primary) en_US/xml-tags.xml:969(secondary)
+#: en_US/xml-tags.xml:974(primary) en_US/xml-tags.xml:1042(primary)
+#: en_US/xml-tags.xml:1048(secondary) en_US/xml-tags.xml:1130(secondary)
+#: en_US/xml-tags.xml:1135(primary) en_US/xml-tags.xml:1225(secondary)
+#: en_US/xml-tags.xml:1230(primary) en_US/xml-tags.xml:1408(secondary)
+#: en_US/xml-tags.xml:1413(primary)
+msgid "lists"
+msgstr ""
+
+#: en_US/xml-tags.xml:946(secondary)
+msgid "creating"
+msgstr ""
+
+#: en_US/xml-tags.xml:949(para)
+msgid ""
+"There are several types of lists you can create using XML. You can have a "
+"itemized (bulleted) list, a ordered (numbered) list, or a variable list "
+"(presents a term and then a separate paragraph)."
+msgstr ""
+
+#: en_US/xml-tags.xml:953(para)
+msgid ""
+"There is also a list format for tables and for for creating a list of "
+"glossary terms and their definitions."
+msgstr ""
+
+#: en_US/xml-tags.xml:956(para)
+msgid ""
+"The sections below will discuss the proper uses for the various list and how "
+"to create them."
+msgstr ""
+
+#: en_US/xml-tags.xml:978(para)
+msgid ""
+"An <command>ItemizedList</command> is best used to present information that "
+"is important for the reader to know, but that does not need to be in a "
+"specific order. It is shorter than a <command>VariableList</command> and "
+"presents the information in a very simple way."
+msgstr ""
+
+#: en_US/xml-tags.xml:984(para)
+msgid ""
+"To create an <command>ItemizedList</command> (otherwise known as bulleted "
+"list), use the following command sequence:"
+msgstr ""
+
+#: en_US/xml-tags.xml:988(para) en_US/xml-tags.xml:1063(para)
+#: en_US/xml-tags.xml:1147(para)
+msgid ""
+"Notice below that the text for the list item is directly surrounded by the "
+"<command>para</command> tags. If you do not do this, you will find extra "
+"whitespace in your lists where the text does not line up correctly. This is "
+"most noticeable when you have a series of list items that consist of "
+"multiple lines of text. This whitespace is not as noticeable in the HTML "
+"output as it is in the PDFs."
+msgstr ""
+
+#: en_US/xml-tags.xml:998(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<itemizedlist> \n"
+" <listitem>\n"
+" <para>Getting familiar with the installation program's user interface</para>\n"
+" </listitem>\n"
+"\n"
+" <listitem>\n"
+" <para>Starting the installation program</para> \n"
+" </listitem>\n"
+"\n"
+" <listitem>\n"
+" <para>Selecting an installation method</para>\n"
+" </listitem>\n"
+"</itemizedlist>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1015(para) en_US/xml-tags.xml:1094(para)
+#: en_US/xml-tags.xml:1181(para) en_US/xml-tags.xml:1319(para)
+#: en_US/xml-tags.xml:1453(para) en_US/xml-tags.xml:1909(para)
+#: en_US/xml-tags.xml:1958(para)
+msgid "The output looks like:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1019(para)
+msgid "Getting familiar with the installation program's user interface"
+msgstr ""
+
+#: en_US/xml-tags.xml:1023(para)
+msgid "Starting the installation program"
+msgstr ""
+
+#: en_US/xml-tags.xml:1027(para)
+msgid "Selecting an installation method"
+msgstr ""
+
+#: en_US/xml-tags.xml:1034(command)
+msgid "OrderedList"
+msgstr ""
+
+#: en_US/xml-tags.xml:1052(para)
+msgid ""
+"An <command>orderedlist</command> is best used to present information that "
+"is important for the reader to know in a specific order. "
+"<command>orderedlist</command>s are a good way to convey step-by-step "
+"senarios to the audience you are writing for."
+msgstr ""
+
+#: en_US/xml-tags.xml:1057(para)
+msgid ""
+"To create an <command>orderedlist</command> (numbered list), use the "
+"following XML code sequence:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1073(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<orderedlist>\n"
+" <listitem>\n"
+" <para>Online &mdash; http://www.redhat.com/support/errata; supplies errata\n"
+" you can read online, and you can download diskette images\n"
+" easily.</para>\n"
+" </listitem>\n"
+"\t \n"
+" <listitem>\n"
+" <para>Email &mdash; By sending an empty mail message to errata@@redhat.com, \n"
+" you will receive an email containing a text listing of the \n"
+" complete errata of the installation program and related software \n"
+" (if errata exist at that time). Also included are URLs to each \n"
+" updated package and diskette image in the errata. Using these \n"
+" URLs, you can download any necessary diskette images. Please \n"
+" note: use binary mode when transferring a diskette image.</para> \n"
+" </listitem>\n"
+"</orderedlist>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1098(para)
+msgid ""
+"Online — http://www.redhat.com/support/errata; supplies errata you can "
+"read online, and you can download diskette images easily."
+msgstr ""
+
+#: en_US/xml-tags.xml:1105(para)
+msgid ""
+"Email — By sending an empty mail message to errata@@redhat.com, you "
+"will receive an email containing a text listing of the complete errata of "
+"the installation program and related software (if errata exist at that "
+"time). Also included are URLs to each updated package and diskette image in "
+"the errata. Using these URLs, you can download any necessary diskette "
+"images. Please note: use binary mode when transferring a diskette image."
+msgstr ""
+
+#: en_US/xml-tags.xml:1121(command)
+msgid "Variablelist"
+msgstr ""
+
+#: en_US/xml-tags.xml:1139(para)
+msgid ""
+"A <command>variablelist</command> best represents a list of terms and "
+"definitions or descriptions for those terms."
+msgstr ""
+
+#: en_US/xml-tags.xml:1142(para)
+msgid ""
+"To create a <command>variablelist</command>, use the following command "
+"sequence:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1157(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<variablelist>\n"
+" <varlistentry> \n"
+" <term> New Multi-CD Install </term>\n"
+" <listitem> \n"
+" <para>As the installation program continues to grow, Red Hat has developed \n"
+" an installation program capable of installing from \n"
+" multiple CD-ROMs.</para>\n"
+" </listitem>\n"
+" </varlistentry>\n"
+"\n"
+" <varlistentry>\n"
+" <term>XFree 4.0 </term>\n"
+" <listitem>\n"
+" <para>Configuration of your X Window System during the installation has \n"
+" never been more thorough. From choosing your monitor and its correct \n"
+" settings, to video card probing, to testing your desired X setup, \n"
+" Xconfigurator will help you set everything just right.</para>\n"
+" </listitem>\n"
+" </varlistentry>\n"
+"</variablelist>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1185(term)
+msgid "New Multi-CD Install"
+msgstr ""
+
+#: en_US/xml-tags.xml:1185(para)
+msgid ""
+"As the installation program continues to grow, Red Hat has developed an "
+"installation program capable of installing from multiple CD-ROMs."
+msgstr ""
+
+#: en_US/xml-tags.xml:1193(term)
+msgid "XFree 4.0"
+msgstr ""
+
+#: en_US/xml-tags.xml:1195(para)
+msgid ""
+"Configuration of your X Window System during the installation has never been "
+"more thorough. From choosing your monitor and its correct settings, to video "
+"card probing, to testing your desired X setup, Xconfigurator will help you "
+"set everything just right."
+msgstr ""
+
+#: en_US/xml-tags.xml:1205(title) en_US/writing-guidelines.xml:434(title)
+msgid "Warning"
+msgstr ""
+
+#: en_US/xml-tags.xml:1206(para)
+msgid ""
+"Do <emphasis>not</emphasis> specify the <computeroutput>frame</"
+"computeroutput> attribute to the table. Doing so breaks PDF production."
+msgstr ""
+
+#: en_US/xml-tags.xml:1216(title)
+msgid "Creating a List Within a Table Using <command>Simplelist</command>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1220(command) en_US/xml-tags.xml:1226(tertiary)
+#: en_US/xml-tags.xml:1231(command) en_US/xml-tags.xml:1237(command)
+msgid "simplelist"
+msgstr ""
+
+#: en_US/xml-tags.xml:1235(primary)
+msgid "tables"
+msgstr ""
+
+#: en_US/xml-tags.xml:1236(secondary)
+msgid "creating a list within a table"
+msgstr ""
+
+#: en_US/xml-tags.xml:1240(para)
+msgid ""
+"A <command>simplelist</command> is an unadorned list of items. "
+"<command>simplelist</command>s can be inline or arranged in columns."
+msgstr ""
+
+#: en_US/xml-tags.xml:1244(para)
+msgid ""
+"We use <command>simplelist</command> to add separate paragraphs of text "
+"within a table element. A regular list, such as <command>itemizedlist</"
+"command>, cannot be embedded within a table."
+msgstr ""
+
+#: en_US/xml-tags.xml:1248(para)
+msgid "The XML commands for a table look like:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1251(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"\t <table id=\"tb-hwinfo-hostbus\">\n"
+"\t <title>Host Bus Adapter Features and Configuration Requirements</title>\n"
+"\t \n"
+"\t <tgroup cols=\"3\">\n"
+"\t <colspec colnum=\"1\" colname=\"HostBus\" colwidth=\"33\"/>\n"
+"\t <colspec colnum=\"2\" colname=\"Features\" colwidth=\"34\"/>\n"
+"\t <colspec colnum=\"3\" colname=\"Single\" colwidth=\"33\"/>\n"
+"\t \n"
+"\t <thead>\n"
+"\t\t<row>\n"
+"\t\t <entry>Host Bus Adapter</entry>\n"
+"\t\t <entry>Features</entry>\n"
+"\t\t <entry>Single-Initiator Configuration</entry>\n"
+"\t\t</row>\n"
+"\t </thead>\n"
+"\t \n"
+"\t <tbody>\n"
+"\t\t\n"
+"\t\t<row>\n"
+"\t\t <entry>Adaptec 2940U2W</entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Ultra2, wide, LVD.</member>\n"
+"\t\t <member>HD68 external connector.</member>\n"
+"\t\t <member>One channel, with two bus segments.</member>\n"
+"\t\t <member>Set the onboard termination by using the BIOS\n"
+"\t\t\tutility.</member>\n"
+"\t\t <member>Onboard termination is disabled when the power is\n"
+"\t\t\toff.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist>\n"
+"\t\t <member>Set the onboard termination to automatic (the\n"
+"\t\t\tdefault).</member>\n"
+"\t\t <member>Use the internal SCSI connector for private\n"
+"\t\t\t(non-cluster) storage.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t</row>\n"
+"\t\t\n"
+"\t\t<row>\n"
+"\t\t <entry>Qlogic QLA1080</entry>\n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Ultra2, wide, LVD</member>\n"
+"\t\t <member>VHDCI external connector</member>\n"
+"\t\t <member>One channel</member>\n"
+"\t\t <member>Set the onboard termination by using the BIOS\n"
+"\t\t\tutility.</member>\n"
+"\t\t <member>Onboard termination is disabled when the power is off,\n"
+"\t\t\tunless jumpers are used to enforce termination.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t \n"
+"\t\t \n"
+"\t\t <entry><simplelist> \n"
+"\t\t <member>Set the onboard termination to\n"
+"\t\t\tautomatic (the default).</member>\n"
+"\t\t <member>Use the internal SCSI connector for private\n"
+"\t\t\t(non-cluster) storage.</member>\n"
+"\t\t </simplelist></entry>\n"
+"\t\t</row>\n"
+"\t\t\n"
+"\t </tbody>\n"
+"\t </tgroup>\n"
+"\t </table>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1322(title)
+msgid "Host Bus Adapter Features and Configuration Requirements"
+msgstr ""
+
+#: en_US/xml-tags.xml:1331(entry)
+msgid "Host Bus Adapter"
+msgstr ""
+
+#: en_US/xml-tags.xml:1332(entry) en_US/xml-tags.xml:2144(entry)
+msgid "Features"
+msgstr ""
+
+#: en_US/xml-tags.xml:1333(entry)
+msgid "Single-Initiator Configuration"
+msgstr ""
+
+#: en_US/xml-tags.xml:1340(entry)
+msgid "Adaptec 2940U2W"
+msgstr ""
+
+#: en_US/xml-tags.xml:1343(member)
+msgid "Ultra2, wide, LVD."
+msgstr ""
+
+#: en_US/xml-tags.xml:1344(member)
+msgid "HD68 external connector."
+msgstr ""
+
+#: en_US/xml-tags.xml:1345(member)
+msgid "One channel, with two bus segments."
+msgstr ""
+
+#: en_US/xml-tags.xml:1346(member) en_US/xml-tags.xml:1367(member)
+msgid "Set the onboard termination by using the BIOS utility."
+msgstr ""
+
+#: en_US/xml-tags.xml:1348(member)
+msgid "Onboard termination is disabled when the power is off."
+msgstr ""
+
+#: en_US/xml-tags.xml:1353(member) en_US/xml-tags.xml:1375(member)
+msgid "Set the onboard termination to automatic (the default)."
+msgstr ""
+
+#: en_US/xml-tags.xml:1355(member) en_US/xml-tags.xml:1377(member)
+msgid "Use the internal SCSI connector for private (non-cluster) storage."
+msgstr ""
+
+#: en_US/xml-tags.xml:1361(entry)
+msgid "Qlogic QLA1080"
+msgstr ""
+
+#: en_US/xml-tags.xml:1364(member)
+msgid "Ultra2, wide, LVD"
+msgstr ""
+
+#: en_US/xml-tags.xml:1365(member)
+msgid "VHDCI external connector"
+msgstr ""
+
+#: en_US/xml-tags.xml:1366(member)
+msgid "One channel"
+msgstr ""
+
+#: en_US/xml-tags.xml:1369(member)
+msgid ""
+"Onboard termination is disabled when the power is off, unless jumpers are "
+"used to enforce termination."
+msgstr ""
+
+#: en_US/xml-tags.xml:1388(para)
+msgid ""
+"Notice how the <command>SimpleList</command> tags are used. The <"
+"entry> and <simplelist> tags must be aligned beside one another, "
+"otherwise you will receive a parsing error."
+msgstr ""
+
+#: en_US/xml-tags.xml:1393(para)
+msgid ""
+"For each paragraph or list item to be added within a <command>SimpleList</"
+"command>, the <member> tag set must be added around that particular "
+"text item."
+msgstr ""
+
+#: en_US/xml-tags.xml:1399(command) en_US/xml-tags.xml:1403(command)
+#: en_US/xml-tags.xml:1409(tertiary) en_US/xml-tags.xml:1414(command)
+msgid "glosslist"
+msgstr ""
+
+#: en_US/xml-tags.xml:1417(para)
+msgid ""
+"Use the <command>glosslist</command> command set to create a list of "
+"glossary terms and their definitions."
+msgstr ""
+
+#: en_US/xml-tags.xml:1421(para)
+msgid "In XML, an example looks like the following:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1424(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"\t <glosslist>\n"
+"\t <glossentry>\n"
+"\t <glossterm>applet</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>A small application, usually a utility or other\n"
+"\t simple program.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\n"
+"\t <glossentry>\n"
+"\t <glossterm>architecture</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>The design for organization and integration of \n"
+" components within a computer or computer system.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\n"
+"\t <glossentry>\n"
+"\t <glossterm>archive</glossterm>\n"
+"\t <glossdef>\n"
+"\t\t<para>To transfer files into storage for the purpose of \n"
+"\t saving space and/or organization.</para>\n"
+"\t </glossdef>\n"
+"\t </glossentry>\n"
+"\t </glosslist>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1459(glossterm)
+msgid "applet"
+msgstr ""
+
+#: en_US/xml-tags.xml:1461(para)
+msgid "A small application, usually a utility or other simple program."
+msgstr ""
+
+#: en_US/xml-tags.xml:1466(glossterm)
+msgid "architecture"
+msgstr ""
+
+#: en_US/xml-tags.xml:1468(para)
+msgid ""
+"The design for organization and integration of components within a computer "
+"or computer system."
+msgstr ""
+
+#: en_US/xml-tags.xml:1474(glossterm)
+msgid "archive"
+msgstr ""
+
+#: en_US/xml-tags.xml:1476(para)
+msgid ""
+"To transfer files into storage for the purpose of saving space and/or "
+"organization."
+msgstr ""
+
+#: en_US/xml-tags.xml:1487(command) en_US/xml-tags.xml:1491(secondary)
+msgid "option"
+msgstr ""
+
+#: en_US/xml-tags.xml:1494(para)
+msgid ""
+"If you have a command that offers an option or a flag, use the <command><"
+"option></command> and <command></option></command> tags."
+msgstr ""
+
+#: en_US/xml-tags.xml:1501(para)
+msgid ""
+"The <option> tag set is only meant to be used for command line "
+"options, not options in configuration files."
+msgstr ""
+
+#: en_US/xml-tags.xml:1505(para)
+msgid "In XML, specifying an option would look like the following:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1509(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"For example, with the command <command>ls</command> you can \n"
+"specify an option such as <option>-la</option>.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1519(para)
+msgid ""
+"For example, with the command <command>ls</command> you can specify an "
+"option such as <option>-la</option>."
+msgstr ""
+
+#: en_US/xml-tags.xml:1525(title)
+msgid "Index Entries"
+msgstr ""
+
+#: en_US/xml-tags.xml:1528(primary) en_US/xml-tags.xml:1534(secondary)
+#: en_US/xml-tags.xml:1563(primary) en_US/xml-tags.xml:1595(primary)
+msgid "indexing"
+msgstr ""
+
+#: en_US/xml-tags.xml:1537(para)
+msgid ""
+"The following command sequence shows you the code inserted into the body of "
+"the text to add an index entry to your document:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1542(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<indexterm> <-- indicates a term to be placed in the index\n"
+"<primary>foo</primary> <-- indicates that \"foo\" is the first term\n"
+"<secondary>bar</secondary> <-- \"bar\" will be listed under \"foo\" \n"
+"</indexterm> <-- closes this index entry\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1551(primary)
+msgid "foo"
+msgstr ""
+
+#: en_US/xml-tags.xml:1552(secondary)
+msgid "bar"
+msgstr ""
+
+#: en_US/xml-tags.xml:1556(para)
+msgid ""
+"The <command><seealso></command> tag allows you to reference another "
+"index entry or refer to another manual. Make sure the <command><"
+"seealso></command> reference you are pointing to has its own entry. For "
+"example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1564(secondary)
+msgid "seealso tag"
+msgstr ""
+
+#: en_US/xml-tags.xml:1568(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<indexterm> \n"
+"<primary>SWAK</primary> \n"
+"<seealso>salutations</seealso>\n"
+"</indexterm>\n"
+"\n"
+"\n"
+"<indexterm> \n"
+"<primary>salutations</primary> \n"
+"</indexterm>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1582(primary)
+msgid "SWAK"
+msgstr ""
+
+#: en_US/xml-tags.xml:1583(seealso) en_US/xml-tags.xml:1587(primary)
+msgid "Salutations"
+msgstr ""
+
+#: en_US/xml-tags.xml:1590(para)
+msgid ""
+"The <command><see></command> tag allows you to reference to another "
+"index entry entirely. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1596(secondary)
+msgid "see tag"
+msgstr ""
+
+#: en_US/xml-tags.xml:1601(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<indexterm> \n"
+"<primary>Guinness</primary> \n"
+"<see>beer</see> <-- beer will be listed under \n"
+"the Guinness entry, but you must make sure beer also has its \n"
+"own entry to refer to.\n"
+"</indexterm>\n"
+"\n"
+"<indexterm>\n"
+"<primary>beer</primary>\n"
+"</indexterm>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1616(primary)
+msgid "Guinness"
+msgstr ""
+
+#: en_US/xml-tags.xml:1617(see) en_US/xml-tags.xml:1621(primary)
+msgid "Beer"
+msgstr ""
+
+#: en_US/xml-tags.xml:1624(para)
+msgid ""
+"To view the HTML output of the index entries shown here, refer to the "
+"<filename>generated-index.html</filename> file at the end of this document."
+msgstr ""
+
+#: en_US/xml-tags.xml:1628(para)
+msgid ""
+"How does the index get generated? If indexterms exist in the document and "
+"the beginning and ending index tags exist before the end tag for the book or "
+"article, an index is created because of the <command>generate.index</"
+"command> stylesheet parameter, which is set to true by default."
+msgstr ""
+
+#: en_US/xml-tags.xml:1638(command) en_US/xml-tags.xml:1643(secondary)
+msgid "para"
+msgstr ""
+
+#: en_US/xml-tags.xml:1646(para)
+msgid ""
+"For any paragraph, the <command><para></command> and <command></"
+"para></command> tags must open and close that particular paragraph."
+msgstr ""
+
+#: en_US/xml-tags.xml:1651(para)
+msgid ""
+"Do not use para tags around anything other than a simple paragraph. Doing so "
+"will create additional white space within the text itself."
+msgstr ""
+
+#: en_US/xml-tags.xml:1655(para)
+msgid ""
+"Do not use <command><para></command> tags around the following (or, to "
+"put this another way, do not embed the following within <command><para>"
+"</command> tags):"
+msgstr ""
+
+#: en_US/xml-tags.xml:1661(command) en_US/xml-tags.xml:1896(command)
+#: en_US/xml-tags.xml:1904(command) en_US/xml-tags.xml:1953(command)
+msgid "<screen>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1664(command)
+msgid "<itemizedlist>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1667(command)
+msgid "<orderedlist>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1670(command)
+msgid "<variablelist>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1673(command)
+msgid "<table>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1680(command) en_US/xml-tags.xml:1689(secondary)
+#: en_US/writing-guidelines.xml:119(sgmltag)
+msgid "part"
+msgstr ""
+
+#: en_US/xml-tags.xml:1683(primary)
+msgid "parts"
+msgstr ""
+
+#: en_US/xml-tags.xml:1692(para)
+msgid ""
+"In the parent file, you can separate the chapters into parts to divide them "
+"into logical groups. For example, in the parent file, the <command>part</"
+"command> tags surround the chapter entities:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1698(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<part id=\"pt-foo\">\n"
+" <partintro>\n"
+" <para>Some text for the part intro</para>\n"
+" &CHAPTER; \n"
+"\n"
+" &ANOTHER-CHAPTER;\n"
+"</part>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1709(para)
+msgid ""
+"If you create a part, include a part introduction describing the contents of "
+"the part. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1715(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+" <part id=\"pt-setup\">\n"
+" <title>Getting Setup</title>\n"
+" <partintro>\n"
+" <para>This section contains information you will need when you first join\n"
+"\tthe Docs group. You might need to refer to this part again for\n"
+"\tinformation such as installing &FC;.</para>\n"
+" </partintro>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1726(para)
+msgid ""
+"In the HTML output, a separate HTML page is generated with the part number, "
+"title, introduction, and TOC. In the PDF output, the same information about "
+"the part is on a separate page."
+msgstr ""
+
+#: en_US/xml-tags.xml:1735(command) en_US/xml-tags.xml:1739(secondary)
+msgid "prompt"
+msgstr ""
+
+#: en_US/xml-tags.xml:1742(para)
+msgid ""
+"To show a prompt, such as a root or DOS prompt, use the <command><"
+"prompt></command> and <command></prompt></command> commands. For "
+"example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1748(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"At the <prompt>LILO:</prompt> boot prompt, type linux to \n"
+"boot into your Linux partition.\n"
+"\n"
+"At the <prompt>C:\\></prompt> prompt, type ....\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1760(para)
+msgid ""
+"At the <prompt>LILO:</prompt> boot prompt, type linux to boot into your "
+"Linux partition."
+msgstr ""
+
+#: en_US/xml-tags.xml:1764(para)
+msgid "At the <prompt>C:\\></prompt> prompt, type ...."
+msgstr ""
+
+#: en_US/xml-tags.xml:1770(para)
+msgid ""
+"When showing example computer output (usually in <command>screen</command> "
+"tags), do not include the prompt or command (unless the command or prompt is "
+"the actually computer output you want to show)."
+msgstr ""
+
+#: en_US/xml-tags.xml:1779(command) en_US/xml-tags.xml:1783(secondary)
+msgid "replaceable"
+msgstr ""
+
+#: en_US/xml-tags.xml:1786(para)
+msgid ""
+"To create replaceable text, use the tags <command><replaceable></"
+"command> and <command></replaceable></command> around the text you "
+"want to use as a variable."
+msgstr ""
+
+#: en_US/xml-tags.xml:1792(para)
+msgid ""
+"This example demonstrates how to use the <command>replaceable</command> tags "
+"when referencing the name of an RPM file:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1796(screen)
+#, no-wrap
+msgid ""
+"\n"
+"foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1805(replaceable)
+msgid "version-number"
+msgstr ""
+
+#: en_US/xml-tags.xml:1805(replaceable)
+msgid "arch"
+msgstr ""
+
+#: en_US/xml-tags.xml:1804(screen)
+#, no-wrap
+msgid ""
+"\n"
+"foo-<placeholder-1/>.<placeholder-2/>.rpm\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1816(para)
+msgid ""
+"The <command><screen></command> command is used to format text within "
+"a document and is great for adding emphasis to show examples of code, "
+"computer output, and more. In HTML with the Fedora CSS file, this appears in "
+"box with a grey background. To use this command you only need the opening "
+"<command><screen></command> and closing <command></screen></"
+"command> tags around the text you are emphasizing."
+msgstr ""
+
+#: en_US/xml-tags.xml:1828(para)
+msgid ""
+"When using the <command><screen></command> tag, set everything within "
+"that screen to flush left. The contents of the <sgmltag class=\"starttag"
+"\">screen</sgmltag> element are rendered exactly as is, including any "
+"indentation. Using flush left prevents extra blank space in front of the "
+"text inside the gray background when the content is converted to HTML."
+msgstr ""
+
+#: en_US/xml-tags.xml:1838(para)
+msgid ""
+"The <command><screen></command> tag set may contain other inline tags, "
+"such as <command><computeroutput></command>, <command><userinput>"
+"</command>, or <command><replaceable></command>. Additional inline "
+"tags are not required by definition. The <command><screen></command> "
+"tags by themselves may provide sufficient context, especially for simple "
+"examples or file listings. Consider the context of the example, and use "
+"inline tags if they are helpful to the reader."
+msgstr ""
+
+#: en_US/xml-tags.xml:1849(para)
+msgid ""
+"If you use inline tags, remember that line breaks inside <command><"
+"screen></command> tags create line breaks in any rendered output. Place "
+"any inline tags <emphasis>on the same line</emphasis> as their content. Do "
+"not overuse tagging within a <command><screen></command> tag set."
+msgstr ""
+
+#: en_US/xml-tags.xml:1857(para)
+msgid "An example of <command><screen></command> is the following:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1862(computeroutput)
+#, no-wrap
+msgid ""
+"<screen>\n"
+"This is an example of a screen. You do not need &lt;para&gt; tags\n"
+"within this command.\n"
+"</screen>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1872(screen)
+#, no-wrap
+msgid ""
+"\n"
+"This is an example of a screen. You do not need <para> tags\n"
+"within this command.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1878(title)
+msgid "Using Inline Tags with <command>screen</command>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1879(para)
+msgid ""
+"If you choose to use inline tags inside a <command><screen></command> "
+"section, follow these guidelines for consistency. If the content in the "
+"screen is a listing of a configuration file or the output of a program, use "
+"the <command><computeroutput></command> tag set around the entire "
+"output. If the user should type the example on the command line or in a "
+"configuration file, use the <command><userinput></command> tag set. "
+"Separate input and output with a short sentence of narrative, as below:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1892(command) en_US/xml-tags.xml:1900(command)
+#: en_US/xml-tags.xml:1949(command)
+msgid "<para>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1894(command) en_US/xml-tags.xml:1902(command)
+#: en_US/xml-tags.xml:1951(command)
+msgid "</para>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1897(command) en_US/xml-tags.xml:1954(command)
+msgid "<userinput>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1897(command) en_US/xml-tags.xml:1954(command)
+msgid "</userinput>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1898(command) en_US/xml-tags.xml:1906(command)
+#: en_US/xml-tags.xml:1955(command)
+msgid "</screen>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1905(command)
+msgid "<computeroutput>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1905(command)
+msgid "</computeroutput>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1891(screen)
+#, no-wrap
+msgid ""
+"\n"
+"\t<placeholder-1/>\n"
+"\t Type the following command:\n"
+"\t<placeholder-2/>\n"
+"\n"
+"<placeholder-3/>\n"
+"<placeholder-4/>command -sw file1<placeholder-5/>\n"
+"<placeholder-6/>\n"
+"\n"
+"\t<placeholder-7/>\n"
+"\t You should see the following output:\n"
+"\t<placeholder-8/>\n"
+"\n"
+"<placeholder-9/>\n"
+"<placeholder-10/>Completed, time = 0.12 sec<placeholder-11/>\n"
+"<placeholder-12/>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1913(para)
+msgid "Type the following command:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1918(userinput)
+#, no-wrap
+msgid "command -sw file1"
+msgstr ""
+
+#: en_US/xml-tags.xml:1921(para)
+msgid "You should see the following output:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1926(computeroutput)
+#, no-wrap
+msgid "Completed, time = 0.12 sec"
+msgstr ""
+
+#: en_US/xml-tags.xml:1931(para)
+msgid ""
+"When showing a command or series of commands inside <command>screen</"
+"command> tags, do not show the prompt."
+msgstr ""
+
+#: en_US/xml-tags.xml:1937(para)
+msgid ""
+"If the <command><screen></command> shows the reader how to change only "
+"<emphasis>part</emphasis> of a line, mark the change with an inline "
+"<command><userinput></command> tag set. You may use the <command><"
+"userinput></command> tag set inside a larger area that is already marked "
+"inline with <command><computeroutput></command>. Do not include any "
+"extra lines of context in this case, unless excluding them would confuse the "
+"reader. The following example illustrates these guidelines:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1950(command)
+msgid "<filename>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1950(command)
+msgid "</filename>"
+msgstr ""
+
+#: en_US/xml-tags.xml:1948(screen)
+#, no-wrap
+msgid ""
+"\n"
+"\t<placeholder-1/>\n"
+"\t Edit the <placeholder-2/>/etc/sysconfig/init<placeholder-3/> file as follows:\n"
+"\t<placeholder-4/>\n"
+"\n"
+"<placeholder-5/>\n"
+"GRAPHICAL=<placeholder-6/>yes<placeholder-7/> \n"
+"<placeholder-8/>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1962(para)
+msgid "Edit the <filename>/etc/sysconfig/init</filename> file as follows:"
+msgstr ""
+
+#: en_US/xml-tags.xml:1967(userinput) en_US/xml-tags.xml:2153(entry)
+#: en_US/xml-tags.xml:2154(entry) en_US/xml-tags.xml:2158(entry)
+#: en_US/xml-tags.xml:2159(entry) en_US/xml-tags.xml:2163(entry)
+#: en_US/xml-tags.xml:2164(entry)
+#, no-wrap
+msgid "yes"
+msgstr ""
+
+#: en_US/xml-tags.xml:1966(screen)
+#, no-wrap
+msgid ""
+"\n"
+"GRAPHICAL=<placeholder-1/>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:1970(para)
+msgid ""
+"For an explanation of how to use the <command>replaceable</command> tags "
+"within a set of <command>screen</command> tags, refer to <xref linkend=\"sn-"
+"xml-tags-replaceable\"/>."
+msgstr ""
+
+#: en_US/xml-tags.xml:1980(title)
+msgid "Sections"
+msgstr ""
+
+#: en_US/xml-tags.xml:1984(secondary) en_US/xml-tags.xml:1988(primary)
+msgid "sections"
+msgstr ""
+
+#: en_US/xml-tags.xml:1991(para)
+msgid ""
+"Within an article (or chapter if it is a DocBook XML book like the "
+"<citetitle>Installation Guide</citetitle>), you can have sections and "
+"subsections. <command><section></command> is always the highest "
+"section and you cannot have two sections of the same level within one "
+"another (a section 2 can be created within a section 1, but section 1 has to "
+"be closed before another section 1 can be created). The general layout "
+"follows:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2000(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<section id=\"sn-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"\n"
+"\n"
+" <section id=\"sn-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"\n"
+" <sect3 id=\"s3-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"\n"
+" </sect3>\n"
+"\n"
+" </section>\n"
+"\n"
+"</section>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2028(para)
+msgid ""
+"If you only need one level of sections in a DocBook article, you can use the "
+"<command>section</command> tag. For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2034(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<section id=\"sn-uniquename\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" Body text goes here.\n"
+" </para>\n"
+"</section>\n"
+"<section id=\"sn-anothername\">\n"
+" <title>Insert Title Here</title>\n"
+" <para>\n"
+" More body text goes here.\n"
+" </para>\n"
+"</section>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2059(para)
+msgid "The following is an example of creating a table."
+msgstr ""
+
+#: en_US/xml-tags.xml:2066(command)
+msgid "\"tb-mockup-before-begin.\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2065(emphasis)
+msgid ""
+"This tells XML that you will be creating a table and the ID name is "
+"<placeholder-1/>"
+msgstr ""
+
+#: en_US/xml-tags.xml:2071(emphasis)
+msgid "This tells XML that you are creating a table with three columns."
+msgstr ""
+
+#: en_US/xml-tags.xml:2075(command)
+msgid "colspec"
+msgstr ""
+
+#: en_US/xml-tags.xml:2075(emphasis)
+msgid ""
+"<placeholder-1/> says that you are giving information about the column to XML"
+msgstr ""
+
+#: en_US/xml-tags.xml:2076(command)
+msgid "colnum=\"1\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2076(emphasis)
+msgid ""
+"<placeholder-1/> says that you are giving specifications for the first "
+"column."
+msgstr ""
+
+#: en_US/xml-tags.xml:2079(command)
+msgid "colname=\"Features\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2079(emphasis)
+msgid ""
+"<placeholder-1/> says that the title for this column will be \"Features.\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2082(command)
+msgid "colwidth=\"3\""
+msgstr ""
+
+#: en_US/xml-tags.xml:2082(emphasis)
+msgid ""
+"<placeholder-1/> specifies the width of the column. This can be more tricky: "
+"such as two columns with widths of 1 and 2,the 1 is one-half the width of "
+"the 2, in respect to the page size. But, what if you need the 1 to be a "
+"little more than half of the 2, using a larger number ratio, such as 10 to "
+"20 would accomplish this. You could then change the 10 to an 11 or a 12 to "
+"make it a little more than half of the second column of 20. In no value is "
+"given, a value of 1 is assumed."
+msgstr ""
+
+#: en_US/xml-tags.xml:2096(emphasis)
+msgid "Contains one or more table row elements."
+msgstr ""
+
+#: en_US/xml-tags.xml:2099(emphasis)
+msgid "Contains one or more table cell (entry) elements."
+msgstr ""
+
+#: en_US/xml-tags.xml:2102(emphasis)
+msgid ""
+"Table cell element, one of several in a row element, defining columns within "
+"the row."
+msgstr ""
+
+#: en_US/xml-tags.xml:2111(emphasis)
+msgid "Contains one or more row elements, for the main text of the table."
+msgstr ""
+
+#: en_US/xml-tags.xml:2063(screen)
+#, no-wrap
+msgid ""
+"\n"
+"<table id=\"tb-mockup-before-begin\">\n"
+" <placeholder-1/>\n"
+"\n"
+"<title>Available Features of GNOME and KDE</title>\n"
+"\n"
+"<tgroup cols=\"3\">\n"
+" <placeholder-2/>\n"
+"\n"
+"<colspec colnum=\"1\" colname=\"Features\" colwidth=\"3\"/>\n"
+" <placeholder-3/> <placeholder-4/>\n"
+" \n"
+" <placeholder-5/>\n"
+" \n"
+" <placeholder-6/>\n"
+"\n"
+"<colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/>\n"
+"<colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/>\n"
+"\n"
+"<thead>\n"
+" <placeholder-7/>\n"
+"\n"
+"<row> \n"
+" <placeholder-8/>\n"
+"\n"
+"<entry>Features</entry>\n"
+" <placeholder-9/>\n"
+"\n"
+"<entry>GNOME</entry> \n"
+"<entry>KDE</entry>\n"
+"</row> \n"
+"</thead> \n"
+"\n"
+"<tbody> \n"
+" <placeholder-10/>\n"
+"\n"
+"<row> \n"
+"<entry>highly configurable</entry> \n"
+"<entry>yes</entry> \n"
+"<entry>yes</entry> \n"
+"</row> \n"
+"<row> \n"
+"<entry>multiple window managers </entry>\n"
+"<entry>yes</entry> \n"
+"<entry>yes</entry> \n"
+"</row> \n"
+"<row> \n"
+"<entry>Internet applications</entry> \n"
+"<entry>yes </entry> \n"
+"<entry>yes </entry> \n"
+"</row> \n"
+"</tbody> \n"
+"</tgroup> \n"
+"</table> \n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2135(title)
+msgid "Available Features of GNOME and KDE"
+msgstr ""
+
+#: en_US/xml-tags.xml:2145(entry)
+msgid "GNOME"
+msgstr ""
+
+#: en_US/xml-tags.xml:2146(entry)
+msgid "KDE"
+msgstr ""
+
+#: en_US/xml-tags.xml:2152(entry)
+msgid "highly configurable"
+msgstr ""
+
+#: en_US/xml-tags.xml:2157(entry)
+msgid "multiple window managers"
+msgstr ""
+
+#: en_US/xml-tags.xml:2162(entry)
+msgid "Internet applications"
+msgstr ""
+
+#: en_US/xml-tags.xml:2171(title)
+msgid "Creating a List Within a Table"
+msgstr ""
+
+#: en_US/xml-tags.xml:2176(tertiary)
+msgid "list within a table"
+msgstr ""
+
+#: en_US/xml-tags.xml:2180(para)
+msgid ""
+"Creating a list within a table can be a difficult task. It requires strict "
+"formatting and a set of commands that are not available for command "
+"completion in <application>Emacs</application>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2185(para)
+msgid ""
+"The tags you will need to use are <command><simplelist></command> and "
+"<command><member></command>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2189(para)
+msgid ""
+"The following example will show you the proper formatting for creating a "
+"list within a table."
+msgstr ""
+
+#: en_US/xml-tags.xml:2194(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<table id=\"tb-hardware-powerswitch\">\n"
+" <title>Power Switch Hardware Table</title>\n"
+" <tgroup cols=\"4\">\n"
+" <colspec colnum=\"1\" colname=\"Hardware\" colwidth=\"2\"/>\n"
+" <colspec colnum=\"2\" colname=\"Quantity\" colwidth=\"2\"/>\n"
+" <colspec colnum=\"3\" colname=\"Description\" colwidth=\"6\"/> \n"
+" <colspec colnum=\"4\" colname=\"Required\" colwidth=\"2\"/>\n"
+"\n"
+" <thead>\n"
+"\t <row>\n"
+" <entry>Hardware</entry>\n"
+"\t <entry>Quantity</entry>\n"
+" <entry>Description</entry>\n"
+"\t <entry>Required</entry>\n"
+"\t </row>\n"
+" </thead>\n"
+"\t \n"
+" <tbody>\n"
+"\t \n"
+"\t<row>\n"
+" <entry>Serial power switches</entry>\n"
+"\n"
+"\t <entry>Two</entry>\n"
+"\n"
+"\t <entry><simplelist> <member>Power switches enable each cluster system\n"
+"\t to power-cycle the other cluster system. Note that clusters are\n"
+"\t configured with either serial or network attached power switches and\n"
+"\t not both.</member>\n"
+"\t\t \n"
+" <member>The following serial attached power switch has been\n"
+"\t fully tested:</member>\n"
+"\n"
+" <member>RPS-10 (model M/HD in the US, and model M/EC in\n"
+"\t Europe) </member>\n"
+"\n"
+" <member>Latent support is provided for the following serial\n"
+"\t attached power switch. This switch has not yet been fully\n"
+" tested:</member>\n"
+"\t\t \n"
+"\t <member>APC Serial On/Off Switch (partAP9211), <ulink\n"
+" url=\"http://www.apc.com/\">http://www.apc.com/</ulink></member>\n"
+" </simplelist></entry>\n"
+"\n"
+" <entry>Strongly recommended for data integrity under all failure\n"
+"\t conditions</entry>\n"
+"\n"
+"\t </row>\n"
+" </tbody>\n"
+" </tgroup>\n"
+"</table>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2248(para)
+msgid ""
+"Notice how the <command><simplelist></command> tag must be beside the "
+"<command><entry></command> tag? If you do not format this properly, it "
+"will not parse cleanly."
+msgstr ""
+
+#: en_US/xml-tags.xml:2252(para)
+msgid "The above example will look like the following:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2255(title)
+msgid "Power Switch Hardware Table"
+msgstr ""
+
+#: en_US/xml-tags.xml:2264(entry)
+msgid "Hardware"
+msgstr ""
+
+#: en_US/xml-tags.xml:2265(entry)
+msgid "Quantity"
+msgstr ""
+
+#: en_US/xml-tags.xml:2266(entry) en_US/emacs.xml:415(segtitle)
+msgid "Description"
+msgstr ""
+
+#: en_US/xml-tags.xml:2267(entry)
+msgid "Required"
+msgstr ""
+
+#: en_US/xml-tags.xml:2274(entry)
+msgid "Serial power switches"
+msgstr ""
+
+#: en_US/xml-tags.xml:2276(entry)
+msgid "Two"
+msgstr ""
+
+#: en_US/xml-tags.xml:2278(member)
+msgid ""
+"Power switches enable each cluster system to power-cycle the other cluster "
+"system. Note that clusters are configured with either serial or network "
+"attached power switches and not both."
+msgstr ""
+
+#: en_US/xml-tags.xml:2283(member)
+msgid "The following serial attached power switch has been fully tested:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2286(member)
+msgid "RPS-10 (model M/HD in the US, and model M/EC in Europe)"
+d39 2
+a40 4
+#: en_US/xml-tags.xml:2289(member)
+msgid ""
+"Latent support is provided for the following serial attached power switch. "
+"This switch has not yet been fully tested:"
+d43 2
+a44 2
+#: en_US/xml-tags.xml:2294(ulink)
+msgid "http://www.apc.com/"
+d47 2
+a48 2
+#: en_US/xml-tags.xml:2293(member)
+msgid "APC Serial On/Off Switch (partAP9211), <placeholder-1/>"
+d51 2
+a52 2
+#: en_US/xml-tags.xml:2297(entry)
+msgid "Strongly recommended for data integrity under all failure conditions"
+d55 2
+a56 2
+#: en_US/xml-tags.xml:2310(command) en_US/xml-tags.xml:2314(command)
+msgid "trademark"
+d59 2
+a60 148
+#: en_US/xml-tags.xml:2318(para)
+msgid ""
+"Do not use the trademark entities &trade;, &copy;, or &reg; "
+"because the do not produce HTML output that works for all charsets. The HTML "
+"output produces by these entities are declared in the DTD and cannot be "
+"changed via the stylesheet."
+msgstr ""
+
+#: en_US/xml-tags.xml:2323(para)
+msgid ""
+"Instead, use the <command>trademark</command> tag and its associates classes "
+"as follows:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2328(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<trademark>trademark symbol after me</trademark>\n"
+"<trademark class=\"registered\">registered trademark symbol after me</trademark>\n"
+"<trademark class=\"copyright\">copyright symbol after me</trademark>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2338(command) en_US/xml-tags.xml:2342(command)
+msgid "userinput"
+msgstr ""
+
+#: en_US/xml-tags.xml:2345(para)
+msgid ""
+"To show what a user would type, use the <command>userinput</command> tag. "
+"For example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2350(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"At the prompt, type:\n"
+"\n"
+"<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput>\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2361(para)
+msgid "At the prompt, type:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2366(userinput)
+#, no-wrap
+msgid "dd if=boot.img of=/dev/fd0 bs=1440k"
+msgstr ""
+
+#: en_US/xml-tags.xml:2393(command) en_US/xml-tags.xml:2397(secondary)
+#: en_US/emacs.xml:540(computeroutput)
+msgid "ulink"
+msgstr ""
+
+#: en_US/xml-tags.xml:2400(para)
+msgid "To create a URL link within your text, use the following example:"
+msgstr ""
+
+#: en_US/xml-tags.xml:2404(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"Online &mdash; <ulink url=\"http://www.redhat.com/support/errata/\">\n"
+"http://www.redhat.com/support/errata/</ulink>; supplies errata \n"
+"you can read online, and you can download diskette images easily.\n"
+msgstr ""
+
+#: en_US/xml-tags.xml:2415(para)
+msgid ""
+"Online —<ulink url=\"http://www.redhat.com/support/errata/\"> http://"
+"www.redhat.com/support/errata/</ulink>; supplies errata you can read online, "
+"and you can download diskette images easily."
+msgstr ""
+
+#: en_US/xml-tags.xml:2423(para)
+msgid ""
+"If the URL does not end in a filename, it must end in a slash "
+"(<computeroutput>/</computeroutput>) to be a properly formed URL. For "
+"example, <ulink url=\"http://www.redhat.com/\">http://www.redhat.com/</"
+"ulink>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2434(command) en_US/xml-tags.xml:2438(secondary)
+msgid "wordasword"
+msgstr ""
+
+#: en_US/xml-tags.xml:2441(para)
+msgid ""
+"The <wordasword> tag set is used to define a word meant specifically "
+"as a word and not representing anything else."
+msgstr ""
+
+#: en_US/xml-tags.xml:2444(para)
+msgid ""
+"A lot of technical documentation contains words that have overloaded "
+"meanings. Sometimes it is useful to be able to use a word without invoking "
+"its technical meaning. The <wordasword> element identifies a word or "
+"phrase that might otherwise be interpreted in some specific way, and asserts "
+"that it should be interpreted simply as a word."
+msgstr ""
+
+#: en_US/xml-tags.xml:2450(para)
+msgid ""
+"It is unlikely that the presentation of this element will be able to help "
+"readers understand the variation in meaning; good writing will have to "
+"achieve that goal. The real value of <wordasword> lies in the fact "
+"that full-text searching and indexing tools can use it to avoid false-"
+"positives."
+msgstr ""
+
+#: en_US/xml-tags.xml:2459(computeroutput)
+#, no-wrap
+msgid ""
+"To use <command>grep</command> to search for the word\n"
+"<wordasword>linux</wordasword>, use the command \n"
+"<command>grep linux</command>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2468(para)
+msgid ""
+"To use <command>grep</command> to search for the word <wordasword>linux</"
+"wordasword>, use the command <command>grep linux</command>."
+msgstr ""
+
+#: en_US/xml-tags.xml:2472(para)
+msgid ""
+"In the example, the word \"linux\" is just a word. It is not meant to convey "
+"anything about Linux as a subject, or to add relevance or meaning to the "
+"content. It can be replaced with any other word without losing any of the "
+"context."
+msgstr ""
+
+#: en_US/xml-tags.xml:2481(command) en_US/xml-tags.xml:2485(secondary)
+msgid "xref"
+msgstr ""
+
+#: en_US/xml-tags.xml:2488(para)
+msgid ""
+"To refer to other sections or chapters within a manual, use the <command><"
+"xref></command> tag."
+msgstr ""
+
+#: en_US/xml-tags.xml:2493(para)
+msgid ""
+"The output of this displays the title of the section or chapter you are "
+"pointing the user to. For example:"
+d63 2
+a64 6
+#: en_US/xml-tags.xml:2498(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"For more information about the parent file, refer to\n"
+"<xref linkend=\"ch-tutorial\"></xref> and <xref linkend=\"sn-tutorial-parent\"></xref>\n"
+d67 2
+a68 4
+#: en_US/xml-tags.xml:2508(para)
+msgid ""
+"For more information about the parent file, refer to <xref linkend=\"ch-"
+"tutorial\"/> and <xref linkend=\"sn-tutorial-parent\"/>."
+d251 1
+a251 1
+#: en_US/tutorial.xml:12(title)
+d256 1
+d258 4
+a261 5
+"In this chapter, you will find an example of a Fedora Project documentation "
+"parent file. This example is specific to the way the Docs Project uses "
+"DocBook XML. The parent file contains the main structural format of the "
+"book, a link to the entities file that contain common entities that should "
+"be used, and an entity to change the version and date of the tutorial."
+d278 3
+a280 2
+#: en_US/tutorial.xml:23(title)
+msgid "The Parent File"
+d283 2
+a284 2
+#: en_US/tutorial.xml:25(para)
+msgid "Below is a sample parent file:"
+d287 2
+a288 54
+#: en_US/tutorial.xml:30(computeroutput)
+#, no-wrap
+msgid ""
+"\n"
+"<!DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook XML V4.2//EN\"\n"
+" \"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd\" [\n"
+"\n"
+"<!ENTITY % FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-en.xml\">\n"
+"%FEDORA-ENTITIES-EN;\n"
+"\n"
+"<!ENTITY VERSION \"0.1\"> <!-- change version of tutorial here -->\n"
+"\n"
+"<!ENTITY DOCID \"example-tutorial-&VERSION; (2003-07-07)\"> <!-- change last modified date here -->\n"
+"\n"
+"<!ENTITY LEGALNOTICE SYSTEM \"../common/legalnotice-en.xml\">\n"
+"\n"
+"\n"
+"]>\n"
+"\n"
+"<article id=\"example-tutorial\" lang=\"en\">\n"
+" <articleinfo>\n"
+" <title>Example Tutorial</title>\n"
+" <copyright>\n"
+" <year>2003</year>\n"
+" <holder>Red Hat Inc.</holder>\n"
+" <holder>Tammy Fox</holder>\n"
+" </copyright>\n"
+" <authorgroup>\n"
+" <author>\n"
+"\t<surname>Fox</surname>\n"
+"\t<firstname>Tammy</firstname>\n"
+" </author>\n"
+" </authorgroup>\n"
+" &LEGALNOTICE;\n"
+" </articleinfo>\n"
+"\n"
+" <section id=\"some-section\">\n"
+" <title>Some Section</title>\n"
+"\n"
+" <para>\n"
+" This is an example section. You can also use section, section, etc.\n"
+" </para>\n"
+"\n"
+" <warning>\n"
+" <title>Warning</title>\n"
+" <para>\n"
+"\tExample of an admonition.\n"
+" </para>\n"
+" </warning>\n"
+"\n"
+" </section>\n"
+"\n"
+"<index id=\"generated-index\"></index>\n"
+"</article>\n"
+d291 2
+a292 2
+#: en_US/tutorial.xml:87(title)
+msgid "Including the License Information"
+d295 2
+a296 2
+#: en_US/tutorial.xml:90(primary)
+msgid "tutorial layout"
+d299 2
+a300 2
+#: en_US/tutorial.xml:91(secondary)
+msgid "license"
+d303 1
+a303 1
+#: en_US/tutorial.xml:94(para)
+d305 4
+a308 3
+"All Fedora Project manuals <emphasis>must</emphasis> contain the file "
+"<filename>legalnotice.xml</filename>. This file makes the license for the "
+"file the GNU Free Documentation License (FDL)."
+d311 11
+a321 2
+#: en_US/tutorial.xml:100(para)
+msgid "The sample parent file shows how it is included."
+d899 1
+a899 1
+"New users to Fedora Core are likely to consult online tutorials for guidance "
+d1623 4
+d2019 1
+a2019 1
+"adequately cover a stock installation of Fedora Core. It is impossible for a "
+d2030 2
+a2031 2
+"Avoid covering redundant material, such as how to update a Fedora Core "
+"system. These overarching topics may be covered in other tutorials. Writers "
+d2114 1
+a2114 1
+#: en_US/style.xml:1881(title) en_US/writing-guidelines.xml:259(title)
+d2203 1
+a2203 1
+"which produces the text \"Fedora Core 6.\""
+d2238 7
+d2246 32
+d2281 23
+a2303 3
+#: en_US/writing-guidelines.xml:42(secondary)
+#: en_US/writing-guidelines.xml:46(primary)
+#: en_US/writing-guidelines.xml:59(primary)
+d2307 1
+a2307 1
+#: en_US/writing-guidelines.xml:49(para)
+d2314 2
+a2315 2
+#: en_US/writing-guidelines.xml:55(secondary)
+#: en_US/writing-guidelines.xml:60(secondary)
+d2319 1
+a2319 1
+#: en_US/writing-guidelines.xml:63(para)
+d2324 1
+a2324 1
+#: en_US/writing-guidelines.xml:67(para)
+d2328 1
+a2328 1
+#: en_US/writing-guidelines.xml:70(para)
+d2335 1
+a2335 1
+#: en_US/writing-guidelines.xml:76(para)
+d2341 1
+a2341 1
+#: en_US/writing-guidelines.xml:82(title)
+d2345 1
+a2345 1
+#: en_US/writing-guidelines.xml:91(title)
+d2349 1
+a2349 1
+#: en_US/writing-guidelines.xml:92(segtitle)
+d2353 1
+a2353 1
+#: en_US/writing-guidelines.xml:93(segtitle)
+d2357 1
+a2357 1
+#: en_US/writing-guidelines.xml:95(sgmltag)
+d2361 1
+a2361 1
+#: en_US/writing-guidelines.xml:96(literal)
+d2365 5
+a2369 1
+#: en_US/writing-guidelines.xml:100(literal)
+d2373 1
+a2373 1
+#: en_US/writing-guidelines.xml:103(sgmltag)
+d2377 1
+a2377 1
+#: en_US/writing-guidelines.xml:104(literal)
+d2381 5
+a2385 1
+#: en_US/writing-guidelines.xml:108(literal)
+d2389 6
+a2394 1
+#: en_US/writing-guidelines.xml:112(literal)
+d2398 1
+a2398 1
+#: en_US/writing-guidelines.xml:115(sgmltag)
+d2402 1
+a2402 1
+#: en_US/writing-guidelines.xml:116(literal)
+d2406 5
+a2410 1
+#: en_US/writing-guidelines.xml:120(literal)
+d2414 5
+a2418 1
+#: en_US/writing-guidelines.xml:124(literal)
+d2422 1
+a2422 1
+#: en_US/writing-guidelines.xml:128(para)
+d2428 14
+a2441 1
+#: en_US/writing-guidelines.xml:141(para)
+d2447 5
+a2451 1
+#: en_US/writing-guidelines.xml:151(para)
+d2460 1
+a2460 1
+#: en_US/writing-guidelines.xml:159(para)
+d2466 26
+a2491 1
+#: en_US/writing-guidelines.xml:186(para)
+d2498 1
+a2498 1
+#: en_US/writing-guidelines.xml:191(para)
+d2505 17
+a2521 1
+#: en_US/writing-guidelines.xml:216(term)
+d2527 1
+a2527 1
+#: en_US/writing-guidelines.xml:219(para)
+d2535 2
+a2536 2
+#: en_US/writing-guidelines.xml:243(title)
+msgid "File Header"
+d2539 1
+a2539 1
+#: en_US/writing-guidelines.xml:245(para)
+d2541 4
+a2544 2
+"All the files must contain the CVS Id header. If you create a new file, the "
+"first line must be:"
+d2547 6
+a2552 13
+#: en_US/writing-guidelines.xml:250(para)
+msgid ""
+"The first time it is committed to CVS (and every time it is committed to "
+"CVS) the line is updated automatically to include information about the "
+"file. For example:"
+msgstr ""
+
+#: en_US/writing-guidelines.xml:262(primary)
+#: en_US/writing-guidelines.xml:292(secondary)
+#: en_US/writing-guidelines.xml:298(secondary)
+#: en_US/writing-guidelines.xml:304(secondary)
+#: en_US/writing-guidelines.xml:310(secondary)
+#: en_US/writing-guidelines.xml:316(secondary)
+d2556 3
+a2558 3
+#: en_US/writing-guidelines.xml:267(secondary)
+#: en_US/writing-guidelines.xml:293(tertiary)
+#: en_US/writing-guidelines.xml:362(secondary)
+d2562 3
+a2564 3
+#: en_US/writing-guidelines.xml:272(secondary)
+#: en_US/writing-guidelines.xml:299(tertiary)
+#: en_US/writing-guidelines.xml:347(secondary)
+d2569 3
+a2571 3
+#: en_US/writing-guidelines.xml:277(secondary)
+#: en_US/writing-guidelines.xml:305(tertiary)
+#: en_US/writing-guidelines.xml:342(secondary)
+d2575 3
+a2577 3
+#: en_US/writing-guidelines.xml:282(secondary)
+#: en_US/writing-guidelines.xml:311(tertiary)
+#: en_US/writing-guidelines.xml:352(secondary)
+d2581 3
+a2583 3
+#: en_US/writing-guidelines.xml:287(secondary)
+#: en_US/writing-guidelines.xml:317(tertiary)
+#: en_US/writing-guidelines.xml:357(secondary)
+d2588 1
+a2588 1
+#: en_US/writing-guidelines.xml:320(para)
+d2601 1
+a2601 1
+#: en_US/writing-guidelines.xml:334(title)
+d2609 1
+a2609 1
+#: en_US/writing-guidelines.xml:365(para)
+d2628 1
+a2628 1
+#: en_US/writing-guidelines.xml:385(para)
+d2634 9
+a2642 4
+#: en_US/writing-guidelines.xml:395(para)
+#: en_US/writing-guidelines.xml:415(para)
+#: en_US/writing-guidelines.xml:425(para)
+#: en_US/writing-guidelines.xml:435(para)
+d2646 1
+a2646 2
+#: en_US/writing-guidelines.xml:404(title) en_US/emacs.xml:348(title)
+#: en_US/emacs.xml:396(title) en_US/emacs-nxml.xml:114(title)
+d2650 1
+a2650 1
+#: en_US/writing-guidelines.xml:405(para)
+d2654 1
+a2654 1
+#: en_US/writing-guidelines.xml:414(title)
+d2658 9
+a2666 1
+#: en_US/writing-guidelines.xml:442(title)
+d2670 2
+a2671 2
+#: en_US/writing-guidelines.xml:445(primary)
+#: en_US/writing-guidelines.xml:450(see) en_US/writing-guidelines.xml:454(see)
+d2675 1
+a2675 1
+#: en_US/writing-guidelines.xml:446(secondary)
+d2679 1
+a2679 1
+#: en_US/writing-guidelines.xml:449(primary)
+d2683 1
+a2683 1
+#: en_US/writing-guidelines.xml:453(primary)
+d2687 1
+a2687 1
+#: en_US/writing-guidelines.xml:457(para)
+d2689 7
+a2695 6
+"There are two types of screenshots: graphical and textual. The philosophy on "
+"using these two types is <firstterm>rely on text over graphics</firstterm>. "
+"This means, if you can say it in text instead of showing a graphic, do so. A "
+"graphical screenshot of a GUI can create a good setting of objects to then "
+"describe textually, but you don't want to create a screenshot for each "
+"graphical step."
+d2698 1
+a2698 1
+#: en_US/writing-guidelines.xml:464(para)
+d2700 7
+a2706 5
+"The main reason for this preference is that a block of text can usually "
+"convey more meaning than the same physical space of graphics. This is highly "
+"dependent on the graphic; obviously, a photographic image of a scene can "
+"convey more than 1000 words can. A GUI screenshot is usually full of blank "
+"space with a few elements that can just as easily be described or listed."
+d2709 1
+a2709 1
+#: en_US/writing-guidelines.xml:470(para)
+d2715 1
+a2715 1
+#: en_US/writing-guidelines.xml:475(term)
+d2719 1
+a2719 1
+#: en_US/writing-guidelines.xml:479(para)
+d2721 4
+a2724 15
+"Set the theme to Bluecurve defaults. This gives a look that is familiar to "
+"most readers, and makes Fedora Documentation Project documents consistent. "
+"From the panel menu, choose <guimenu>Preferences</guimenu>, "
+"<guimenuitem>Theme</guimenuitem> and select <guimenuitem>Bluecurve</"
+"guimenuitem> from the theme list."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:488(para)
+msgid ""
+"Set fonts to Bluecurve defaults as well. From the panel menu, choose "
+"<guimenu>Preferences</guimenu>, <guimenuitem>Fonts</guimenuitem>. Set the "
+"<guilabel>Application font</guilabel> and the <guilabel>Desktop font</"
+"guilabel> to Sans Regular 10. Set the <guilabel>Window Title font</guilabel> "
+"to Sans Bold 10. Set the <guilabel>Terminal font</guilabel> to Monospace "
+"Regular 10."
+d2729 4
+a2732 4
+"Before taking the screenshot, try to resize the targeted GUI element(s) to "
+"the smallest possible size they can be. Your target is an image of 500 "
+"pixels or less. If you are doing a screenshot of more than one GUI element, "
+"you may need to resize the screenshot in a following step."
+d2737 2
+a2738 2
+"To take the screenshot, select the GUI element with your mouse, bringing it "
+"to the forefront, or otherwise arranging the elements. Press "
+d2741 25
+a2765 3
+"<keycap>Print Screen</keycap>. If you are taking a shot of multiple elements "
+"and have grouped them closely together, you can crop the resulting image in "
+"<application>The GIMP</application>. The image will be in the PNG format."
+d2768 1
+a2768 1
+#: en_US/writing-guidelines.xml:519(para)
+d2770 1
+a2770 21
+"If you need to, you can resize using <application>The GIMP</application>. "
+"With the image open, right-click on it and choose <guimenu>Image</guimenu> -"
+"> <guimenuitem>Scale Image...</guimenuitem>. With the chain symbol "
+"intact, set the <guilabel>New Width</guilabel> to <guilabel>500 px</"
+"guilabel>, and click <guibutton>OK</guibutton>. Be sure to "
+"<keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo> to save your "
+"changes to your PNG before converting to EPS."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:532(para)
+msgid ""
+"With the image open in <application>The GIMP</application>, right-click on "
+"the image, selecting <guimenu>File</guimenu> -> <guimenuitem>Save As...</"
+"guimenuitem>. Under <guimenu>Determine File Type:</guimenu>, select "
+"<guimenuitem>PostScript</guimenuitem>, then click <guibutton>OK</guibutton>. "
+"Allow flattening of the image by clicking <guibutton>Export</guibutton>."
+msgstr ""
+
+#: en_US/writing-guidelines.xml:541(para)
+msgid ""
+"In the <guilabel>Save as PostScript</guilabel> window, select "
+d2775 1
+a2775 1
+#: en_US/writing-guidelines.xml:555(term)
+d2779 1
+a2779 1
+#: en_US/writing-guidelines.xml:557(para)
+d2785 1
+a2785 1
+#: en_US/writing-guidelines.xml:561(para)
+d2787 3
+a2789 3
+"If you use a graphical screenshot to illustrate a function, and the textual "
+"mode has identical functions, do not include both, unless omitting either "
+"would make your description unclear."
+d2792 1
+a2792 1
+#: en_US/writing-guidelines.xml:567(para)
+d2794 1
+a2794 1
+"Make your information generic over specific, and omit any username and "
+d2799 1
+a2799 1
+#: en_US/writing-guidelines.xml:573(para)
+d2803 1
+a2803 1
+#: en_US/writing-guidelines.xml:577(para)
+d2811 1
+a2811 1
+#: en_US/writing-guidelines.xml:585(para)
+d2817 1
+a2817 1
+#: en_US/writing-guidelines.xml:590(title)
+d2821 1
+a2821 1
+#: en_US/writing-guidelines.xml:603(para)
+d2826 1
+a2826 1
+#: en_US/writing-guidelines.xml:605(userinput)
+d2831 1
+a2831 1
+#: en_US/writing-guidelines.xml:607(para)
+d2835 1
+a2835 1
+#: en_US/writing-guidelines.xml:609(computeroutput)
+d2864 2
+a2865 1
+"module, excluding any <filename class=\"directory\">CVS</filename> folders:"
+d2868 1
+a2868 1
+#: en_US/module-struct.xml:24(title)
+d2872 1
+a2872 1
+#: en_US/module-struct.xml:45(title)
+d2876 1
+a2876 1
+#: en_US/module-struct.xml:46(segtitle)
+d2880 1
+a2880 1
+#: en_US/module-struct.xml:47(segtitle)
+d2884 1
+a2884 1
+#: en_US/module-struct.xml:48(segtitle)
+d2888 1
+a2888 1
+#: en_US/module-struct.xml:50(seg)
+d2892 2
+a2893 2
+#: en_US/module-struct.xml:51(seg) en_US/module-struct.xml:88(seg)
+#: en_US/module-struct.xml:95(seg)
+d2897 2
+a2898 2
+#: en_US/module-struct.xml:54(filename)
+#: en_US/module-struct.xml:156(systemitem)
+d2902 1
+a2902 1
+#: en_US/module-struct.xml:58(firstterm)
+d2906 1
+a2906 1
+#: en_US/module-struct.xml:59(para)
+d2914 1
+a2914 1
+#: en_US/module-struct.xml:52(seg)
+d2923 1
+a2923 1
+#: en_US/module-struct.xml:67(seg)
+d2927 1
+a2927 1
+#: en_US/module-struct.xml:68(seg) en_US/module-struct.xml:78(seg)
+d2931 1
+a2931 1
+#: en_US/module-struct.xml:69(filename) en_US/module-struct.xml:73(filename)
+d2935 1
+a2935 1
+#: en_US/module-struct.xml:69(seg)
+d2943 1
+a2943 1
+#: en_US/module-struct.xml:77(seg)
+d2947 1
+a2947 1
+#: en_US/module-struct.xml:79(filename) en_US/module-struct.xml:163(filename)
+d2951 5
+a2955 1
+#: en_US/module-struct.xml:79(seg)
+d2957 5
+a2961 5
+"The <placeholder-1/> directory contains specially formatted files created "
+"and used by translators. The Fedora Documentation Project build tools use "
+"these files to create translated versions of documents. The translated "
+"documents are not stored in CVS; they are created as needed from these PO "
+"files."
+d2964 1
+a2964 1
+#: en_US/module-struct.xml:87(seg) en_US/module-struct.xml:89(filename)
+d2968 1
+a2968 1
+#: en_US/module-struct.xml:89(seg)
+d2974 1
+a2974 1
+#: en_US/module-struct.xml:94(filename) en_US/module-struct.xml:96(filename)
+d2978 1
+a2978 1
+#: en_US/module-struct.xml:96(seg)
+d2983 22
+a3004 1
+msgid "The Document Build System"
+d3007 1
+a3007 1
+#: en_US/module-struct.xml:103(para)
+d3011 3
+a3013 2
+"command> and shell scripts. Authors need <emphasis>no</emphasis> prior "
+"experience with either shell scripts or a <command>make(1)</command>."
+d3016 1
+a3016 1
+#: en_US/module-struct.xml:111(title)
+d3021 1
+a3021 1
+#: en_US/module-struct.xml:112(para)
+d3028 1
+a3028 1
+#: en_US/module-struct.xml:118(para)
+d3034 1
+a3034 1
+#: en_US/module-struct.xml:124(title)
+d3038 1
+a3038 1
+#: en_US/module-struct.xml:137(para)
+d3045 1
+a3045 1
+#: en_US/module-struct.xml:143(title)
+d3049 1
+a3049 1
+#: en_US/module-struct.xml:144(segtitle)
+d3053 1
+a3053 1
+#: en_US/module-struct.xml:145(segtitle) en_US/module-struct.xml:259(segtitle)
+d3057 1
+a3057 1
+#: en_US/module-struct.xml:147(systemitem)
+d3061 1
+a3061 1
+#: en_US/module-struct.xml:148(seg)
+d3067 1
+a3067 1
+#: en_US/module-struct.xml:153(systemitem)
+d3071 1
+a3071 1
+#: en_US/module-struct.xml:154(seg)
+d3077 1
+a3077 1
+#: en_US/module-struct.xml:159(systemitem)
+d3081 1
+a3081 1
+#: en_US/module-struct.xml:160(seg)
+d3089 1
+a3089 1
+#: en_US/module-struct.xml:167(systemitem)
+d3093 1
+a3093 1
+#: en_US/module-struct.xml:168(seg)
+d3101 1
+a3101 1
+#: en_US/module-struct.xml:177(systemitem)
+d3105 1
+a3105 1
+#: en_US/module-struct.xml:180(systemitem)
+d3109 1
+a3109 1
+#: en_US/module-struct.xml:185(systemitem)
+d3113 1
+a3113 1
+#: en_US/module-struct.xml:178(seg)
+d3123 1
+a3123 1
+#: en_US/module-struct.xml:191(title)
+d3127 1
+a3127 1
+#: en_US/module-struct.xml:192(para)
+d3133 1
+a3133 1
+#: en_US/module-struct.xml:196(para)
+d3135 2
+a3136 2
+"The final line, beginning with <literal>include</literal>, references the "
+"main <filename>Makefile</filename> for the build system. This "
+d3142 1
+a3142 1
+#: en_US/module-struct.xml:205(title)
+d3146 1
+a3146 1
+#: en_US/module-struct.xml:206(para)
+d3155 1
+a3155 18
+#: en_US/module-struct.xml:212(para)
+msgid "<xref linkend=\"ex-rpminfo\"/> illustrates the content of this file:"
+msgstr ""
+
+#: en_US/module-struct.xml:215(title)
+#, fuzzy
+msgid "Example <filename>rpm-info.xml</filename> File"
+msgstr ".emacs"
+
+#: en_US/module-struct.xml:244(para)
+msgid ""
+"If you are not familiar with XML editing, copy and paste this file from an "
+"existing module and then edit the values for the various elements as "
+"appropriate. Consult Fedora Documentation Project members and help channels "
+"for more assistance if needed."
+msgstr ""
+
+#: en_US/module-struct.xml:251(title)
+d3159 1
+a3159 1
+#: en_US/module-struct.xml:252(para)
+d3165 1
+a3165 1
+#: en_US/module-struct.xml:257(title)
+d3169 1
+a3169 1
+#: en_US/module-struct.xml:258(segtitle)
+d3173 1
+a3173 1
+#: en_US/module-struct.xml:261(systemitem)
+d3177 2
+a3178 2
+#: en_US/module-struct.xml:262(abbrev) en_US/module-struct.xml:273(abbrev)
+#: en_US/module-struct.xml:298(abbrev) en_US/module-struct.xml:303(abbrev)
+d3182 2
+a3183 2
+#: en_US/module-struct.xml:266(systemitem)
+#: en_US/module-struct.xml:276(systemitem)
+d3187 2
+a3188 2
+#: en_US/module-struct.xml:267(systemitem)
+#: en_US/module-struct.xml:277(systemitem)
+d3192 1
+a3192 1
+#: en_US/module-struct.xml:265(filename)
+d3196 1
+a3196 1
+#: en_US/module-struct.xml:262(seg)
+d3204 1
+a3204 1
+#: en_US/module-struct.xml:272(systemitem)
+d3208 1
+a3208 1
+#: en_US/module-struct.xml:275(filename)
+d3212 1
+a3212 1
+#: en_US/module-struct.xml:273(seg)
+d3219 1
+a3219 1
+#: en_US/module-struct.xml:281(systemitem)
+d3223 2
+a3224 2
+#: en_US/module-struct.xml:282(abbrev) en_US/module-struct.xml:283(abbrev)
+#: en_US/module-struct.xml:299(abbrev) en_US/module-struct.xml:304(abbrev)
+d3228 1
+a3228 1
+#: en_US/module-struct.xml:282(seg)
+d3235 1
+a3235 1
+#: en_US/module-struct.xml:287(systemitem)
+d3239 1
+a3239 1
+#: en_US/module-struct.xml:288(command)
+d3243 1
+a3243 1
+#: en_US/module-struct.xml:288(seg)
+d3249 1
+a3249 1
+#: en_US/module-struct.xml:292(systemitem)
+d3253 1
+a3253 1
+#: en_US/module-struct.xml:293(seg)
+d3257 2
+a3258 2
+#: en_US/module-struct.xml:296(systemitem)
+#: en_US/module-struct.xml:305(filename)
+d3262 1
+a3262 1
+#: en_US/module-struct.xml:298(emphasis)
+d3266 1
+a3266 1
+#: en_US/module-struct.xml:297(seg)
+d3272 1
+a3272 1
+#: en_US/module-struct.xml:302(systemitem)
+d3276 1
+a3276 1
+#: en_US/module-struct.xml:303(seg)
+d3282 11
+a3292 1
+#: en_US/module-struct.xml:310(title)
+d3296 1
+a3296 1
+#: en_US/module-struct.xml:311(para)
+d3305 1
+a3305 1
+#: en_US/module-struct.xml:319(para)
+d3311 1
+a3311 1
+#: en_US/module-struct.xml:326(title)
+d3315 1
+a3315 1
+#: en_US/module-struct.xml:327(para)
+d3323 1
+a3323 1
+#: en_US/module-struct.xml:334(para)
+d3336 1
+a3336 1
+#: en_US/module-struct.xml:348(para)
+d3343 1
+a3343 1
+#: en_US/module-struct.xml:354(para)
+d3353 1
+a3353 1
+#: en_US/module-struct.xml:364(para)
+d3362 1
+a3362 1
+#: en_US/module-struct.xml:373(para)
+d3368 1
+a3368 1
+#: en_US/module-struct.xml:379(title)
+d3372 1
+a3372 1
+#: en_US/module-struct.xml:386(title)
+d3376 1
+a3376 1
+#: en_US/module-struct.xml:387(para)
+d3381 1
+a3381 1
+#: en_US/module-struct.xml:391(para)
+d3385 1
+a3385 1
+#: en_US/module-struct.xml:395(para)
+d3394 1
+a3394 1
+#: en_US/module-struct.xml:405(title)
+d3398 1
+a3398 1
+#: en_US/module-struct.xml:406(para)
+d3406 1
+a3406 1
+#: en_US/module-struct.xml:413(para)
+d3412 1
+a3412 1
+#: en_US/module-struct.xml:419(para)
+d3416 1
+a3416 1
+#: en_US/module-struct.xml:423(para)
+d3422 1
+a3422 1
+#: en_US/module-struct.xml:428(para)
+d3428 1
+a3428 1
+#: en_US/module-struct.xml:431(replaceable)
+d3432 1
+a3432 1
+#: en_US/module-struct.xml:431(screen)
+d3444 3
+a3446 10
+"task-based documentation for Fedora users and developers. Other than the "
+"<citetitle>Installation Guide</citetitle>, each tutorial should be in "
+"DocBook XML article format, with one article per topic. This way, writers "
+"can contribute documentation about a specific topic without having to worry "
+"about how it fits into a manual or how it flows with other topics."
+msgstr "Docs Project 的目标是为 DocBook XML v4.1 xmlto) Emacs PSGML Emacs nXML"
+
+#: en_US/intro.xml:25(para)
+msgid "The following tools are used:"
+msgstr "translator-credits"
+d3448 1
+a3448 1
+#: en_US/intro.xml:31(para)
+d3452 1
+a3452 1
+#: en_US/intro.xml:34(para)
+d3456 1
+a3456 1
+#: en_US/intro.xml:38(para)
+d3460 1
+a3460 1
+#: en_US/intro.xml:42(para)
+d3464 1
+a3464 1
+#: en_US/intro.xml:51(para)
+d3526 13
+a3538 1
+#: en_US/getting-files.xml:43(title)
+d3542 1
+a3542 1
+#: en_US/getting-files.xml:45(para)
+d3546 4
+a3549 2
+"systemitem> CVS server. Check them out along with the DocBook XML files for "
+"the existing docs."
+d3552 8
+a3559 3
+#: en_US/getting-files.xml:53(replaceable)
+#: en_US/getting-files.xml:54(replaceable)
+msgid "my-fedora-docs-sandbox"
+d3562 9
+a3570 2
+#: en_US/getting-files.xml:55(replaceable)
+msgid "username"
+d3573 1
+a3573 2
+#: en_US/getting-files.xml:53(userinput)
+#, no-wrap
+d3575 6
+a3580 5
+"mkdir <placeholder-1/>\n"
+"cd <placeholder-2/>\n"
+"export CVSROOT=:ext:<placeholder-3/>@@cvs.fedora.redhat.com:/cvs/docs\n"
+"cvs login\n"
+"cvs co docs-common"
+d3583 7
+a3589 2
+#: en_US/getting-files.xml:60(para)
+msgid "At the password prompt, press the <keycap>Enter</keycap> key."
+d3592 4
+a3595 10
+#: en_US/getting-files.xml:65(title)
+msgid "Common Files"
+msgstr ""
+
+#: en_US/getting-files.xml:66(para)
+msgid ""
+"You need to perform this \"checkout\" step only once, although you may need "
+"to update the files later. These files are common to all the official "
+"documentation."
+msgstr ""
+d3597 1
+a3597 1
+#: en_US/getting-files.xml:73(para)
+d3599 4
+a3602 1
+"To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>."
+d3605 2
+a3606 2
+#: en_US/getting-files.xml:80(title)
+msgid "Filename Conventions"
+d3609 1
+a3609 1
+#: en_US/getting-files.xml:81(para)
+d3615 1
+a3615 1
+"of these services, you must follow conventions for naming your files."
+d3618 8
+a3625 2
+#: en_US/getting-files.xml:89(title)
+msgid "Document Filenames"
+d3628 1
+a3628 1
+#: en_US/getting-files.xml:90(para)
+d3630 1
+a3630 4
+"Each document lives in a peer directory to the <filename>docs-common</"
+"filename> directory you extracted from the Fedora archive earlier. On the "
+"CVS server, these directories are called <firstterm>modules</firstterm>. Use "
+"the <command>cvs co -c</command> command to view existing module names."
+d3633 1
+a3633 1
+#: en_US/getting-files.xml:98(title)
+d3637 1
+a3637 1
+#: en_US/getting-files.xml:99(userinput)
+d3642 23
+a3664 2
+#: en_US/getting-files.xml:100(computeroutput)
+#, no-wrap
+d3666 3
+a3668 8
+"build-docs infrastructure/build-docs\n"
+"cvsroot CVSROOT\n"
+"desktop-up2date desktop-up2date\n"
+"developer-guide developer-guide\n"
+"docs .\n"
+"docs-common docs-common\n"
+"documentation-guide documentation-guide\n"
+"example-tutorial example-tutorial"
+d3671 5
+a3675 1
+#: en_US/getting-files.xml:109(para)
+d3678 4
+a3681 1
+"avoid any name already taken."
+d3684 1
+a3684 1
+#: en_US/getting-files.xml:112(title)
+d3688 1
+a3688 1
+#: en_US/getting-files.xml:113(para)
+d3690 1
+a3690 1
+"Do not use the word <wordasword>Fedora</wordasword> to name modules in the "
+d3694 72
+d3775 3
+a3777 3
+#: en_US/emacs.xml:43(primary) en_US/emacs.xml:232(primary)
+#: en_US/emacs.xml:241(primary) en_US/emacs.xml:246(primary)
+#: en_US/emacs.xml:251(primary) en_US/emacs.xml:526(application)
+d3821 1
+a3821 126
+"the following lines: <screen><computeroutput><![CDATA[\n"
+";; turn on auto-fill in `text-mode' and derived modes \n"
+";;(mail, news, etc)\n"
+"(add-hook 'text-mode-hook 'turn-on-auto-fill)\n"
+"\n"
+";;\n"
+";;MODES\n"
+";;\n"
+"\n"
+"(setq auto-mode-alist (cons '(\"\\\\.sgml$\" . sgml-mode) auto-mode-alist))\n"
+"(setq auto-mode-alist (cons '(\"\\\\.sgm$\" . sgml-mode) auto-mode-alist))\n"
+"\n"
+";;\n"
+";;XML!!\n"
+";;\n"
+";;#############################################################\n"
+"\n"
+";;\n"
+";;PSGML mode stuff\n"
+";;\n"
+"\n"
+"(autoload 'sgml-mode \"psgml\" \"My Most Major Mode\" t)\n"
+"\n"
+"(setq sgml-mode-hook '(lambda () \"Defaults for XML mode.\" (turn-on-auto-"
+"fill) \n"
+"(setq fill-column 80)))\n"
+"\n"
+"(defun My-XML-keymap ()\n"
+" (local-set-key [(alt i)] \n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-indent-line)\n"
+" (sgml-insert-element 'item)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt l)] \n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-insert-element 'list)\n"
+" (sgml-insert-element 'item)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt p)]\n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (sgml-indent-line)\n"
+" (sgml-insert-element 'para)\n"
+" (sgml-indent-line)))\n"
+" (local-set-key [(alt -)]\n"
+" '(lambda ()\n"
+" (interactive)\n"
+" (insert \"—\")))) \n"
+"\n"
+"(add-hook 'sgml-mode-hook 'My-XML-keymap)\n"
+"\n"
+";;\n"
+";; Fix up indentation of data...\n"
+";;\n"
+"\n"
+"(setq-default sgml-indent-data t)\n"
+"\n"
+";;\n"
+";; XML markup faces.\n"
+";;\n"
+"\n"
+"(setq-default sgml-set-face t)\n"
+"\n"
+"\n"
+"(make-face 'sgml-comment-face)\n"
+"(make-face 'sgml-doctype-face)\n"
+"(make-face 'sgml-end-tag-face)\n"
+"(make-face 'sgml-entity-face)\n"
+"(make-face 'sgml-ignored-face)\n"
+"(make-face 'sgml-ms-end-face)\n"
+"(make-face 'sgml-ms-start-face)\n"
+"(make-face 'sgml-pi-face)\n"
+"(make-face 'sgml-sgml-face)\n"
+"(make-face 'sgml-short-ref-face)\n"
+"(make-face 'sgml-start-tag-face)\n"
+"\n"
+"(set-face-foreground 'sgml-comment-face \"maroon\")\n"
+"(set-face-foreground 'sgml-doctype-face \"dark green\")\n"
+"(set-face-foreground 'sgml-end-tag-face \"blue2\")\n"
+"(set-face-foreground 'sgml-entity-face \"red2\")\n"
+"(set-face-foreground 'sgml-ignored-face \"maroon\")\n"
+"(set-face-background 'sgml-ignored-face \"gray90\")\n"
+"(set-face-foreground 'sgml-ms-end-face \"maroon\")\n"
+"(set-face-foreground 'sgml-ms-start-face \"maroon\")\n"
+"(set-face-foreground 'sgml-pi-face \"maroon\")\n"
+"(set-face-foreground 'sgml-sgml-face \"maroon\")\n"
+"(set-face-foreground 'sgml-short-ref-face \"goldenrod\")\n"
+"(set-face-foreground 'sgml-start-tag-face \"blue2\")\n"
+"\n"
+"(setq-default sgml-markup-faces\n"
+" '((comment . sgml-comment-face)\n"
+" (doctype . sgml-doctype-face)\n"
+" (end-tag . sgml-end-tag-face)\n"
+" (entity . sgml-entity-face)\n"
+" (ignored . sgml-ignored-face)\n"
+" (ms-end . sgml-ms-end-face)\n"
+" (ms-start . sgml-ms-start-face)\n"
+" (pi . sgml-pi-face)\n"
+" (sgml . sgml-sgml-face)\n"
+" (short-ref . sgml-short-ref-face)\n"
+" (start-tag . sgml-start-tag-face)))\n"
+"\n"
+"\n"
+"(defun docbook-mode ()\n"
+" (sgml-mode)\n"
+" )\n"
+"\n"
+"\n"
+"\n"
+";;\n"
+";;END XML STUFF\n"
+";;\n"
+";;##################################################################\n"
+"\n"
+";PO mode stuff\n"
+"\n"
+"(setq auto-mode-alist\n"
+"\t(cons '(\"\\\\.pox?\\\\'\" . po-mode) auto-mode-alist))\n"
+"(autoload 'po-mode \"po-mode\")\n"
+"\n"
+"\n"
+" (global-set-key [(f1)] (lambda () (interactive) (manual-\n"
+" entry (current-word))))\n"
+"]]></computeroutput></screen>"
+d3824 1
+a3824 1
+#: en_US/emacs.xml:185(para)
+d3831 1
+a3831 1
+#: en_US/emacs.xml:198(para)
+d3837 1
+a3837 1
+#: en_US/emacs.xml:229(title)
+d3841 1
+a3841 1
+#: en_US/emacs.xml:233(secondary)
+d3845 1
+a3845 1
+#: en_US/emacs.xml:237(filename)
+d3849 1
+a3849 1
+#: en_US/emacs.xml:242(secondary)
+d3853 1
+a3853 1
+#: en_US/emacs.xml:247(secondary)
+d3857 1
+a3857 1
+#: en_US/emacs.xml:252(secondary)
+d3861 1
+a3861 1
+#: en_US/emacs.xml:255(para)
+d3865 1
+a3865 1
+"<computeroutput>emacs.keyword:value</computeroutput>"
+d3868 1
+a3868 1
+#: en_US/emacs.xml:261(para)
+d3872 1
+a3872 1
+#: en_US/emacs.xml:266(para)
+d3878 2
+a3879 2
+#: en_US/emacs.xml:282(para)
+msgid "After modifying this file, you must execute the command"
+d3882 1
+a3882 1
+#: en_US/emacs.xml:286(command)
+d3886 2
+a3887 7
+#: en_US/emacs.xml:287(para)
+msgid ""
+"and restart <application>Emacs</application> for the changes to take place."
+msgstr ""
+
+#: en_US/emacs.xml:295(title)
+msgid "Create Recompiled DTD Subset"
+d3890 2
+a3891 85
+#: en_US/emacs.xml:297(para)
+msgid ""
+"Emacs will perform syntax highlighting and indent correctly on DocBook XML "
+"files if you provide it with the proper Document Type Declarations (DTD) "
+"file. These two features will make your XML file look pretty and help you "
+"spot errors."
+msgstr ""
+
+#: en_US/emacs.xml:308(para)
+msgid ""
+"Find the parent file for the group of DocBook files. You will recognize this "
+"file by the header <filename><!DOCTYPE article PUBLIC \"-//OASIS//DTD "
+"DocBook V4.1//EN\"</filename>. An easy way to find this parent file is to "
+"use the command <command>grep DocBook *.xml</command>. Once you find the "
+"parent file, open it in Emacs with the command <command>emacs "
+"<replaceable><parentfile></replaceable>.xml</command> (where "
+"<replaceable><parentfile></replaceable>.xml is the parent file you "
+"found."
+msgstr ""
+
+#: en_US/emacs.xml:321(para)
+msgid "Choose <command>DTD -> Parse DTD</command> from the pulldown menu."
+msgstr ""
+
+#: en_US/emacs.xml:327(para)
+msgid ""
+"You will know the parsing is finished when you see the message "
+"<computeroutput>Fontifying...done</computeroutput> at the bottom of your "
+"screen. Save the parsed DTD to a file by choosing <command>DTD -> Save "
+"Parsed DTD</command> from the pulldown menu."
+msgstr ""
+
+#: en_US/emacs.xml:335(para)
+msgid ""
+"Press <keycap>Enter</keycap> to save the file to the default filename or "
+"rename the file keeping the <filename>.ced</filename> extension. It can be "
+"useful to name it something generic such as <filename>docbook.ced</filename> "
+"so you can refer to it when opening all DocBook files. This file can also be "
+"copied from directory to directory to be loaded."
+msgstr ""
+
+#: en_US/emacs.xml:304(para)
+msgid "To create a loadable Parsed DTD file: <placeholder-1/>"
+msgstr ""
+
+#: en_US/emacs.xml:349(para)
+msgid ""
+"You can also use the Emacs command <command>Meta-x sgml-parse-prolog</"
+"command> to parse the file, and then use the command <command>Meta-x sgml-"
+"save-dtd</command> to save the parsed DTD to a <filename>.ced</filename> "
+"file."
+msgstr ""
+
+#: en_US/emacs.xml:360(title)
+msgid "Load the Parsed DTD"
+msgstr ""
+
+#: en_US/emacs.xml:362(para)
+msgid ""
+"Now that you have saved the DTD settings, you can load the <filename>.ced</"
+"filename> file and see the syntax highlighting for your <filename>.sgml</"
+"filename> files."
+msgstr ""
+
+#: en_US/emacs.xml:372(para)
+msgid "Open an XML file in Emacs."
+msgstr ""
+
+#: en_US/emacs.xml:377(para)
+msgid ""
+"Choose <command>DTD -> Load DTD</command> from the pulldown menu and "
+"choose the file you saved from the previous step. For instance, choose "
+"<filename>docbook.ced</filename>."
+msgstr ""
+
+#: en_US/emacs.xml:384(para)
+msgid ""
+"You will know it is finished when you see the message "
+"<computeroutput>Fontifying...done</computeroutput> at the bottom of your "
+"screen. Loading the parsed DTD might take a long time. You can start editing "
+"the file before it finishes."
+msgstr ""
+
+#: en_US/emacs.xml:368(para)
+msgid "To load a parsed DTD file: <placeholder-1/>"
+a3894 10
+msgid ""
+"You can also use the Emacs command <command>Meta-x sgml-load-dtd</command> "
+"to load the parsed DTD."
+msgstr ""
+
+#: en_US/emacs.xml:406(title)
+msgid "Basic Emacs Commands"
+msgstr ""
+
+#: en_US/emacs.xml:408(para)
+d3898 1
+a3898 1
+#: en_US/emacs.xml:413(title)
+d3902 1
+a3902 1
+#: en_US/emacs.xml:414(segtitle)
+d3906 7
+a3912 4
+#: en_US/emacs.xml:418(keycap) en_US/emacs.xml:423(keycap)
+#: en_US/emacs.xml:428(keycap) en_US/emacs.xml:496(keycap)
+#: en_US/emacs.xml:501(keycap) en_US/emacs.xml:506(keycap)
+#: en_US/emacs.xml:530(keycap)
+d3916 3
+a3918 4
+#: en_US/emacs.xml:418(keycap) en_US/emacs.xml:423(keycap)
+#: en_US/emacs.xml:428(keycap) en_US/emacs.xml:501(keycap)
+#: en_US/emacs.xml:506(keycap) en_US/emacs.xml:511(keycap)
+#: en_US/emacs.xml:517(keycap) en_US/emacs.xml:523(keycap)
+d3922 2
+a3923 3
+#: en_US/emacs.xml:419(keycap) en_US/emacs.xml:424(keycap)
+#: en_US/emacs.xml:429(keycap) en_US/emacs.xml:502(keycap)
+#: en_US/emacs.xml:507(keycap)
+d3927 1
+a3927 1
+#: en_US/emacs.xml:417(seg)
+d3933 1
+a3933 1
+#: en_US/emacs.xml:420(seg)
+d3937 11
+a3947 31
+#: en_US/emacs.xml:423(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-save-dtd, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:425(seg)
+msgid "Save the Parse DTD"
+msgstr ""
+
+#: en_US/emacs.xml:428(seg)
+msgid ""
+"<keycombo><placeholder-1/><placeholder-2/></keycombo>sgml-load-dtd, "
+"<placeholder-3/>"
+msgstr ""
+
+#: en_US/emacs.xml:430(seg)
+msgid "Load DTD"
+msgstr ""
+
+#: en_US/emacs.xml:433(keycap) en_US/emacs.xml:439(keycap)
+#: en_US/emacs.xml:446(keycap) en_US/emacs.xml:451(keycap)
+#: en_US/emacs.xml:456(keycap) en_US/emacs.xml:461(keycap)
+#: en_US/emacs.xml:466(keycap) en_US/emacs.xml:471(keycap)
+#: en_US/emacs.xml:476(keycap) en_US/emacs.xml:481(keycap)
+#: en_US/emacs.xml:486(keycap) en_US/emacs.xml:491(keycap)
+#: en_US/emacs.xml:511(keycap) en_US/emacs.xml:512(keycap)
+#: en_US/emacs.xml:517(keycap) en_US/emacs.xml:518(keycap)
+#: en_US/emacs.xml:523(keycap) en_US/emacs.xml:524(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:536(keycap)
+#: en_US/emacs.xml:543(keycap) en_US/emacs.xml:545(keycap)
+d3951 4
+a3954 4
+#: en_US/emacs.xml:433(keycap) en_US/emacs.xml:439(keycap)
+#: en_US/emacs.xml:451(keycap) en_US/emacs.xml:524(keycap)
+#: en_US/emacs.xml:535(keycap) en_US/emacs.xml:543(keycap)
+#: en_US/emacs.xml:545(keycap)
+d3958 1
+a3958 1
+#: en_US/emacs.xml:434(keycap) en_US/emacs.xml:440(keycap)
+d3962 5
+a3966 1
+#: en_US/emacs.xml:435(keycap) en_US/emacs.xml:442(keycap)
+d3970 1
+a3970 1
+#: en_US/emacs.xml:433(seg)
+d3973 1
+a3973 1
+"<keycombo><placeholder-3/><keycap/></keycombo>, <placeholder-4/>"
+d3976 1
+a3976 1
+#: en_US/emacs.xml:436(seg)
+d3980 1
+a3980 1
+#: en_US/emacs.xml:439(seg)
+d3983 2
+a3984 2
+"<keycombo><placeholder-3/><keycap/></keycombo>, type beginning of tag, "
+"<placeholder-4/>"
+d3987 1
+a3987 1
+#: en_US/emacs.xml:443(seg)
+d3991 1
+a3991 1
+#: en_US/emacs.xml:446(keycap)
+d3995 1
+a3995 1
+#: en_US/emacs.xml:448(seg)
+d3999 1
+a3999 1
+#: en_US/emacs.xml:452(keycap)
+d4003 1
+a4003 1
+#: en_US/emacs.xml:451(seg)
+d4007 1
+a4007 1
+#: en_US/emacs.xml:453(seg)
+d4011 1
+a4011 1
+#: en_US/emacs.xml:456(keycap) en_US/emacs.xml:536(keycap)
+d4015 1
+a4015 1
+#: en_US/emacs.xml:458(seg)
+d4019 1
+a4019 1
+#: en_US/emacs.xml:461(keycap)
+d4023 1
+a4023 1
+#: en_US/emacs.xml:463(seg)
+d4027 1
+a4027 1
+#: en_US/emacs.xml:466(keycap)
+d4031 1
+a4031 1
+#: en_US/emacs.xml:468(seg)
+d4035 1
+a4035 1
+#: en_US/emacs.xml:471(keycap)
+d4039 1
+a4039 1
+#: en_US/emacs.xml:473(seg)
+d4043 1
+a4043 1
+#: en_US/emacs.xml:476(keycap)
+d4047 1
+a4047 1
+#: en_US/emacs.xml:478(seg)
+d4051 1
+a4051 1
+#: en_US/emacs.xml:481(keycap)
+d4055 1
+a4055 1
+#: en_US/emacs.xml:483(seg)
+d4059 1
+a4059 1
+#: en_US/emacs.xml:486(keycap) en_US/emacs.xml:518(keycap)
+d4063 1
+a4063 1
+#: en_US/emacs.xml:488(seg)
+d4067 1
+a4067 1
+#: en_US/emacs.xml:491(keycap)
+d4071 1
+a4071 1
+#: en_US/emacs.xml:493(seg)
+d4075 1
+a4075 1
+#: en_US/emacs.xml:496(keycap)
+d4079 1
+a4079 1
+#: en_US/emacs.xml:498(seg) en_US/emacs.xml:503(seg)
+d4083 1
+a4083 1
+#: en_US/emacs.xml:501(seg)
+d4089 1
+a4089 1
+#: en_US/emacs.xml:506(seg)
+d4095 1
+a4095 1
+#: en_US/emacs.xml:508(seg)
+d4099 1
+a4099 1
+#: en_US/emacs.xml:512(keycap)
+d4103 2
+a4104 2
+#: en_US/emacs.xml:511(seg) en_US/emacs.xml:517(seg) en_US/emacs.xml:523(seg)
+#: en_US/emacs.xml:535(seg) en_US/emacs.xml:543(seg)
+d4110 1
+a4110 1
+#: en_US/emacs.xml:514(seg)
+d4114 1
+a4114 1
+#: en_US/emacs.xml:520(seg)
+d4118 1
+a4118 1
+#: en_US/emacs.xml:526(seg)
+d4122 1
+a4122 1
+#: en_US/emacs.xml:530(keycap)
+d4126 1
+a4126 1
+#: en_US/emacs.xml:532(seg)
+d4130 1
+a4130 1
+#: en_US/emacs.xml:539(computeroutput)
+d4135 6
+a4140 1
+#: en_US/emacs.xml:538(seg)
+d4146 1
+a4146 1
+#: en_US/emacs.xml:547(seg)
+d4150 1
+a4150 1
+#: en_US/emacs.xml:554(title) en_US/emacs-nxml.xml:77(title)
+d4154 1
+a4154 1
+#: en_US/emacs.xml:556(para)
+d4160 1
+a4160 1
+#: en_US/emacs.xml:562(title)
+d4164 2
+a4165 4
+#: en_US/emacs.xml:566(para)
+msgid ""
+"This section assumes that you have already loaded the DTD file (<filename>."
+"ced</filename>)."
+d4168 1
+a4168 1
+#: en_US/emacs.xml:571(para)
+d4170 4
+a4173 4
+"Instead of typing a tag each time you need to use it, use the key "
+"combination <keycap>Ctrl</keycap>-<keycap>c</keycap>, followed by "
+"<keycap><</keycap>. At the bottom of the <application>Emacs</application> "
+"window, you will see:"
+d4176 1
+a4176 2
+#: en_US/emacs.xml:578(computeroutput)
+#, no-wrap
+d4180 1
+a4180 1
+#: en_US/emacs.xml:581(para)
+d4183 4
+a4186 3
+"<keycap>?</keycap>. Or, if you know the first few letters of a tag, you can "
+"enter them followed by <keycap>Tab</keycap> for a complete list of available "
+"tags beginning with those letters or for a tag completion."
+d4189 1
+a4189 1
+#: en_US/emacs.xml:589(para)
+d4191 3
+a4193 4
+"Try the following: Type <keycap>Ctrl</keycap>-<keycap>c</keycap> followed by "
+"<keycap><</keycap>. Then enter the letter <keycap>k</keycap>, followed by "
+"<keycap>Tab</keycap>. You may have to use the <keycap>Tab</keycap> key "
+"several times to get a complete list."
+d4196 2
+a4197 2
+#: en_US/emacs.xml:596(para)
+msgid "The output should look similar to the example below:"
+d4200 1
+a4200 2
+#: en_US/emacs.xml:601(computeroutput)
+#, no-wrap
+d4202 8
+a4209 7
+"\n"
+"Click mouse-2 on a completion to select it.\n"
+"In this buffer, type RET to select the completion near point.\n"
+"\n"
+"Possible completions are:\n"
+"<keycap> <keycode>\n"
+"<keycombo> <keysym>\n"
+d4212 2
+a4213 2
+#: en_US/emacs.xml:613(title)
+msgid "Tag Closure"
+d4218 4
+a4221 4
+"Once you have started the tag of choice, you must close it. The easiest way "
+"to close an open tag is to use the keycombo <keycap>Ctrl</keycap>-<keycap>c</"
+"keycap>, followed by <keycap>/</keycap>. This will close the closest open "
+"tag you have."
+d4225 1
+a4225 1
+msgid "Other Emacs Tasks"
+d4228 1
+a4228 1
+#: en_US/emacs.xml:627(para)
+d4230 7
+a4236 6
+"<guilabel>Working with one window</guilabel>: Sometimes in "
+"<application>Emacs</application> the window becomes split (with tags "
+"completions or other text in the bottom window). The easiest way to get it "
+"back so that only your XML and text appear on one screen is to use the "
+"keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap>, followed by <keycap>1</"
+"keycap>."
+d4239 1
+a4239 1
+#: en_US/emacs.xml:636(para)
+d4241 8
+a4248 3
+"<guilabel>Saving your work</guilabel>: To save your work, use the following "
+"keycombo, <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</"
+"keycap>-<keycap>s</keycap>."
+d4251 1
+a4251 1
+#: en_US/emacs.xml:642(para)
+d4253 5
+a4257 5
+"<guilabel>The \"clear/quit\" command</guilabel>: I have found on some "
+"occasions that I have gotten too far into the tag completion process and "
+"need to just exit back out to my text. The easiest way to do this is the "
+"keycombo <keycap>Ctrl</keycap>-<keycap>g</keycap>. This command quits what "
+"you have been doing within the file, without quitting the file itself."
+d4260 2
+a4261 7
+#: en_US/emacs.xml:651(para)
+msgid ""
+"<guilabel>Opening a new file</guilabel>: To open a new file, use the "
+"keycombo <keycap>Ctrl</keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</"
+"keycap>-<keycap>f</keycap>. At the bottom of the emacs window, you will be "
+"able to enter in the file name (using <keycap>Tab</keycap> completion if "
+"needed) of the file you wish to open."
+d4264 1
+a4264 1
+#: en_US/emacs.xml:660(para)
+d4266 5
+a4270 6
+"<guilabel>Closing emacs</guilabel>: The easiest way to close "
+"<application>emacs</application> is to use the keycombo <keycap>Ctrl</"
+"keycap>-<keycap>x</keycap> followed by <keycap>Ctrl</keycap>-<keycap>c</"
+"keycap>. If you have not saved your work, it will prompt you to save the "
+"file, otherwise it will just quit the current emacs session you have been "
+"working with."
+d4273 1
+a4273 1
+#: en_US/emacs.xml:673(title) en_US/emacs-nxml.xml:127(title)
+d4277 1
+a4277 1
+#: en_US/emacs.xml:675(para)
+d4283 1
+a4283 5
+#: en_US/emacs.xml:682(ulink) en_US/emacs-nxml.xml:142(ulink)
+msgid "http://wks.uts.ohio-state.edu/unix_course/intro-135.html"
+msgstr ""
+
+#: en_US/emacs.xml:683(citetitle) en_US/emacs-nxml.xml:143(citetitle)
+d4287 1
+a4287 1
+#: en_US/emacs.xml:686(para) en_US/emacs-nxml.xml:147(para)
+d4291 1
+a4291 1
+"<replaceable><version></replaceable>/etc/refcard.ps</filename>"
+d4294 1
+a4294 1
+#: en_US/emacs.xml:693(para)
+d4297 1
+a4297 2
+"usr/share/doc/psgml-<replaceable><version></replaceable>/psgml.ps</"
+"filename>."
+d4300 1
+a4300 1
+#: en_US/emacs.xml:697(para)
+d4302 3
+a4304 8
+"<ulink url=\"http://www.snee.com/bob/sgmlfree/psgmqref.html\">http://www."
+"snee.com/bob/sgmlfree/psgmqref.html</ulink>—<citetitle>Emacs/PSGML "
+"Quick Reference</citetitle> is a reference table of Emacs commands for PSGML "
+"mode."
+msgstr ""
+
+#: en_US/emacs.xml:705(ulink)
+msgid "http://www.snee.com/bob/sgmlfree/emcspsgm.html"
+d4307 1
+a4307 1
+#: en_US/emacs.xml:706(citetitle)
+d4467 11
+d4683 1
+d4685 3
+a4687 3
+"This document is based on the a document started by Tammy Fox (tfox at "
+"redhat.com) and contributed to by Sandra Moore (smoore at redhat.com) and "
+"Johnray Fuller (jrfuller at redhat.com)."
+d4720 1
+d4724 1
+a4724 1
+"(stickstr5 at hotmail.com)."
+d4730 1
+d4732 1
+a4732 1
+"A patch from Paul W. Frields (stickstr5 at hotmail.com) has been applied to "
+d4752 217
+@
+
More information about the docs-commits
mailing list