diff options
| author | Diego Búrigo Zacarão <diegobz@gmail.com> | 2007-04-20 20:22:54 +0000 |
|---|---|---|
| committer | Diego Búrigo Zacarão <diegobz@gmail.com> | 2007-04-20 20:22:54 +0000 |
| commit | ea2105d4151e2e1feb69825e12ecc86fe3c2a056 (patch) | |
| tree | 1475c3d8f87fcd2e7adf7c4ff09dcc545629c8d0 /po | |
| parent | 17dd5babf1a5710d4e9771b71390f09d262a53a9 (diff) | |
| download | documentation-guide-ea2105d4151e2e1feb69825e12ecc86fe3c2a056.tar.gz documentation-guide-ea2105d4151e2e1feb69825e12ecc86fe3c2a056.tar.xz documentation-guide-ea2105d4151e2e1feb69825e12ecc86fe3c2a056.zip | |
Added pt_BR.po
Diffstat (limited to 'po')
| -rw-r--r-- | po/pt_BR.po | 7086 |
1 files changed, 7086 insertions, 0 deletions
diff --git a/po/pt_BR.po b/po/pt_BR.po new file mode 100644 index 0000000..3aaced3 --- /dev/null +++ b/po/pt_BR.po @@ -0,0 +1,7086 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2007-04-20 17:17-0300\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" +"X-POFile-SpellExtra: pt Frields make Fox Emacs Tammy OPL Hat po Red Inc\n" + +#: en_US/rpm-info.xml:20(rights) +msgid "OPL" +msgstr "OPL" + +#: en_US/rpm-info.xml:21(version) +msgid "1.0" +msgstr "1.0" + +#: en_US/rpm-info.xml:24(year) +msgid "2003" +msgstr "2003" + +#: 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 "" + +#: en_US/rpm-info.xml:31(holder) +msgid "Sandra Moore" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: en_US/xml-tags.xml:16(primary) en_US/xml-tags.xml:34(primary) +msgid "XML" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: 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: pt_BR.po,v 1.1 2007/04/20 20:22:54 diegobz 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 "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 "" + +#: 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 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 <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 "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 "" + +#: 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 "" + +#: en_US/xml-tags.xml:2294(ulink) +msgid "http://www.apc.com/" +msgstr "" + +#: en_US/xml-tags.xml:2293(member) +msgid "APC Serial On/Off Switch (partAP9211), <placeholder-1/>" +msgstr "" + +#: en_US/xml-tags.xml:2297(entry) +msgid "Strongly recommended for data integrity under all failure conditions" +msgstr "" + +#: en_US/xml-tags.xml:2310(command) en_US/xml-tags.xml:2314(command) +msgid "trademark" +msgstr "" + +#: 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:" +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 "" + +#: 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:12(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 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 "" + +#: en_US/tutorial.xml:23(title) +msgid "The Parent File" +msgstr "" + +#: en_US/tutorial.xml:25(para) +msgid "Below is a sample parent file:" +msgstr "" + +#: 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" +msgstr "" + +#: en_US/tutorial.xml:87(title) +msgid "Including the License Information" +msgstr "" + +#: en_US/tutorial.xml:90(primary) +msgid "tutorial layout" +msgstr "" + +#: en_US/tutorial.xml:91(secondary) +msgid "license" +msgstr "" + +#: 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 "" + +#: en_US/tutorial.xml:100(para) +msgid "The sample parent file shows how it is included." +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: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:259(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 7.\"" +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:38(title) +msgid "ID Naming Conventions" +msgstr "" + +#: en_US/writing-guidelines.xml:42(secondary) +#: en_US/writing-guidelines.xml:46(primary) +#: en_US/writing-guidelines.xml:59(primary) +msgid "naming conventions" +msgstr "" + +#: 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 "" + +#: en_US/writing-guidelines.xml:55(secondary) +#: en_US/writing-guidelines.xml:60(secondary) +msgid "rules for defining an ID" +msgstr "" + +#: en_US/writing-guidelines.xml:63(para) +msgid "The following general rules apply to IDs:" +msgstr "" + +#: en_US/writing-guidelines.xml:67(para) +msgid "Keep an ID as short and simple as possible." +msgstr "" + +#: 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 "" + +#: en_US/writing-guidelines.xml:76(para) +msgid "" +"<xref linkend=\"ex-id-usage\"/> demonstrates some example ID attributes used " +"properly." +msgstr "" + +#: en_US/writing-guidelines.xml:82(title) +msgid "Proper ID Usage" +msgstr "" + +#: en_US/writing-guidelines.xml:91(title) +msgid "Two-Character Naming Conventions" +msgstr "" + +#: en_US/writing-guidelines.xml:92(segtitle) +msgid "Tag" +msgstr "" + +#: en_US/writing-guidelines.xml:93(segtitle) +msgid "Prefix" +msgstr "Prefixo" + +#: en_US/writing-guidelines.xml:95(sgmltag) +msgid "preface" +msgstr "" + +#: en_US/writing-guidelines.xml:96(literal) +msgid "pr-" +msgstr "" + +#: en_US/writing-guidelines.xml:100(literal) +msgid "ch-" +msgstr "" + +#: en_US/writing-guidelines.xml:103(sgmltag) +msgid "section" +msgstr "" + +#: en_US/writing-guidelines.xml:104(literal) +msgid "sn-" +msgstr "" + +#: en_US/writing-guidelines.xml:108(literal) +msgid "fig-" +msgstr "" + +#: en_US/writing-guidelines.xml:112(literal) +msgid "tb-" +msgstr "" + +#: en_US/writing-guidelines.xml:115(sgmltag) +msgid "appendix" +msgstr "" + +#: en_US/writing-guidelines.xml:116(literal) +msgid "ap-" +msgstr "" + +#: en_US/writing-guidelines.xml:120(literal) +msgid "pt-" +msgstr "" + +#: en_US/writing-guidelines.xml:124(literal) +msgid "ex-" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: en_US/writing-guidelines.xml:159(para) +msgid "" +"Instead, use the <sgmltag>trademark</sgmltag> tag and its associates classes " +"as follows:" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: en_US/writing-guidelines.xml:216(term) +msgid "" +"Content inside <sgmltag class=\"element\">para</sgmltag> elements within " +"<sgmltag>listitem</sgmltag> tags" +msgstr "" + +#: 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 "" + +#: en_US/writing-guidelines.xml:243(title) +msgid "File Header" +msgstr "" + +#: 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 "" + +#: 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) +msgid "admonitions" +msgstr "" + +#: en_US/writing-guidelines.xml:267(secondary) +#: en_US/writing-guidelines.xml:293(tertiary) +#: en_US/writing-guidelines.xml:362(secondary) +msgid "warning" +msgstr "atenção" + +#: en_US/writing-guidelines.xml:272(secondary) +#: en_US/writing-guidelines.xml:299(tertiary) +#: en_US/writing-guidelines.xml:347(secondary) +msgid "tip" +msgstr "" + +#: en_US/writing-guidelines.xml:277(secondary) +#: en_US/writing-guidelines.xml:305(tertiary) +#: en_US/writing-guidelines.xml:342(secondary) +msgid "note" +msgstr "" + +#: en_US/writing-guidelines.xml:282(secondary) +#: en_US/writing-guidelines.xml:311(tertiary) +#: en_US/writing-guidelines.xml:352(secondary) +msgid "caution" +msgstr "" + +#: en_US/writing-guidelines.xml:287(secondary) +#: en_US/writing-guidelines.xml:317(tertiary) +#: en_US/writing-guidelines.xml:357(secondary) +msgid "important" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: 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 choose this operation unless they are alright " +"with the consequences." +msgstr "" + +#: 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 "" + +#: 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) +msgid "Body of text goes here." +msgstr "" + +#: 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) +msgid "Tip" +msgstr "" + +#: en_US/writing-guidelines.xml:405(para) +msgid "Body of text goes here" +msgstr "" + +#: en_US/writing-guidelines.xml:414(title) +msgid "Caution" +msgstr "" + +#: en_US/writing-guidelines.xml:442(title) +msgid "Screenshots" +msgstr "" + +#: en_US/writing-guidelines.xml:445(primary) +#: en_US/writing-guidelines.xml:450(see) en_US/writing-guidelines.xml:454(see) +msgid "screenshots" +msgstr "" + +#: en_US/writing-guidelines.xml:446(secondary) +msgid "how to take" +msgstr "" + +#: en_US/writing-guidelines.xml:449(primary) +msgid "screen captures" +msgstr "" + +#: en_US/writing-guidelines.xml:453(primary) +msgid "screen grabs" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: en_US/writing-guidelines.xml:475(term) +msgid "Graphical Screenshot" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: 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 " +"<guilabel>Encapsulated PostScript</guilabel>, and click <guibutton>OK</" +"guibutton>." +msgstr "" + +#: en_US/writing-guidelines.xml:555(term) +msgid "Text Screenshot" +msgstr "" + +#: en_US/writing-guidelines.xml:557(para) +msgid "" +"Textual screen information is also useful for readers. Follow these " +"guidelines for textual screenshots:" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: en_US/writing-guidelines.xml:573(para) +msgid "Separate what the user types from sample command output." +msgstr "" + +#: 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 "" + +#: en_US/writing-guidelines.xml:585(para) +msgid "" +"<xref linkend=\"ex-text-screenshot-good\"/> is an example of textual " +"screenshot usage." +msgstr "" + +#: en_US/writing-guidelines.xml:590(title) +msgid "Correct Textual Screenshot (XML Source and HTML)" +msgstr "" + +#: en_US/writing-guidelines.xml:603(para) +msgid "" +"To find all the currently active ssh sessions, execute the following command:" +msgstr "" + +#: en_US/writing-guidelines.xml:605(userinput) +#, no-wrap +msgid "ps ax | grep ssh" +msgstr "" + +#: en_US/writing-guidelines.xml:607(para) +msgid "Output appears similar to the following:" +msgstr "" + +#: en_US/writing-guidelines.xml:609(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/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:" +msgstr "" + +#: en_US/module-struct.xml:24(title) +msgid "Example Module Structure" +msgstr "" + +#: en_US/module-struct.xml:45(title) +msgid "CVS Module Contents" +msgstr "" + +#: en_US/module-struct.xml:46(segtitle) +msgid "Component" +msgstr "" + +#: en_US/module-struct.xml:47(segtitle) +msgid "Type" +msgstr "Tipo" + +#: en_US/module-struct.xml:48(segtitle) +msgid "Usage Notes" +msgstr "" + +#: en_US/module-struct.xml:50(seg) +msgid "Primary language directory" +msgstr "" + +#: en_US/module-struct.xml:51(seg) en_US/module-struct.xml:88(seg) +#: en_US/module-struct.xml:95(seg) +msgid "required" +msgstr "" + +#: en_US/module-struct.xml:54(filename) +#: en_US/module-struct.xml:160(systemitem) +msgid "en_US" +msgstr "pt" + +#: en_US/module-struct.xml:58(firstterm) +msgid "entities" +msgstr "" + +#: 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 "" + +#: 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/><placeholder-3/>." +msgstr "" + +#: en_US/module-struct.xml:67(seg) +msgid "Graphics directory" +msgstr "" + +#: en_US/module-struct.xml:68(seg) en_US/module-struct.xml:78(seg) +msgid "optional" +msgstr "" + +#: en_US/module-struct.xml:69(filename) en_US/module-struct.xml:73(filename) +msgid "figs/" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:77(seg) +msgid "Translation (PO) directory" +msgstr "" + +#: en_US/module-struct.xml:79(filename) en_US/module-struct.xml:167(filename) +msgid "po/" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:87(seg) en_US/module-struct.xml:89(filename) +msgid "Makefile" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:94(filename) en_US/module-struct.xml:96(filename) +msgid "rpm-info.xml" +msgstr "" + +#: en_US/module-struct.xml:96(seg) +msgid "The <placeholder-1/> file contains document specific metadata" +msgstr "" + +#: en_US/module-struct.xml:102(title) +msgid "The Document Build System" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:111(title) +msgid "The Document <filename>Makefile</filename>" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: en_US/module-struct.xml:124(title) +msgid "Sample Document Makefile" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:147(title) +msgid "Makefile Variables" +msgstr "" + +#: en_US/module-struct.xml:148(segtitle) +msgid "Variable" +msgstr "" + +#: en_US/module-struct.xml:149(segtitle) en_US/module-struct.xml:263(segtitle) +msgid "Explanation" +msgstr "" + +#: en_US/module-struct.xml:151(systemitem) +msgid "DOCBASE" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:157(systemitem) +msgid "PRI_LANG" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:163(systemitem) +msgid "OTHERS" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:171(systemitem) +msgid "DOC_ENTITIES" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:181(systemitem) +msgid "XMLFILES_template" +msgstr "" + +#: en_US/module-struct.xml:184(systemitem) +msgid "${1}" +msgstr "" + +#: en_US/module-struct.xml:189(systemitem) +msgid "${1}/" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:195(title) +msgid "Files Exempt From Listing" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: en_US/module-struct.xml:209(title) +msgid "The Document <filename>rpm-info.xml</filename>" +msgstr "" + +#: 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 "" + +#: 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) +msgid "Build System Actions" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:261(title) +msgid "Build Targets" +msgstr "" + +#: en_US/module-struct.xml:262(segtitle) +msgid "Target" +msgstr "" + +#: en_US/module-struct.xml:265(systemitem) +msgid "html" +msgstr "" + +#: 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) +msgid "HTML" +msgstr "" + +#: en_US/module-struct.xml:270(systemitem) +#: en_US/module-struct.xml:280(systemitem) +msgid "${DOCBASE}" +msgstr "" + +#: en_US/module-struct.xml:271(systemitem) +#: en_US/module-struct.xml:281(systemitem) +msgid "${LANG}" +msgstr "" + +#: en_US/module-struct.xml:269(filename) +msgid "<placeholder-1/>-<placeholder-2/>/" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:276(systemitem) +msgid "html-nochunks" +msgstr "" + +#: en_US/module-struct.xml:279(filename) +msgid "<placeholder-1/>-<placeholder-2/>.html" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:285(systemitem) +msgid "pdf" +msgstr "" + +#: 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) +msgid "PDF" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:291(systemitem) +msgid "tarball" +msgstr "" + +#: en_US/module-struct.xml:292(command) +msgid "tar(1)" +msgstr "" + +#: en_US/module-struct.xml:292(seg) +msgid "" +"This target builds only the <placeholder-1/> archive for all document " +"languages." +msgstr "" + +#: en_US/module-struct.xml:296(systemitem) +msgid "all" +msgstr "tudo" + +#: en_US/module-struct.xml:297(seg) +msgid "This target builds all targets listed above." +msgstr "" + +#: en_US/module-struct.xml:300(systemitem) +#: en_US/module-struct.xml:309(filename) +msgid "clean" +msgstr "" + +#: en_US/module-struct.xml:302(emphasis) +msgid "not" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:306(systemitem) +msgid "distclean" +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:314(title) +msgid "Adding or Changing Targets" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: en_US/module-struct.xml:330(title) +msgid "Using Document Image Files" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: en_US/module-struct.xml:383(title) +msgid "Building A Manifest" +msgstr "" + +#: en_US/module-struct.xml:390(title) +msgid "Adding a New DocBook XML File" +msgstr "" + +#: en_US/module-struct.xml:391(para) +msgid "" +"To add a new DocBook XML file to an existing document, follow these steps:" +msgstr "" + +#: en_US/module-struct.xml:395(para) +msgid "Place the new DocBook XML file in the primary language directory." +msgstr "" + +#: 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 "" + +#: en_US/module-struct.xml:409(title) +msgid "Adding a Translation" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: en_US/module-struct.xml:423(para) +msgid "If it does not exist, create the POT file:" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: en_US/module-struct.xml:435(replaceable) +msgid "lang" +msgstr "língua" + +#: en_US/module-struct.xml:435(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. 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 "" + +#: en_US/intro.xml:25(para) +msgid "The following tools are used:" +msgstr "" + +#: en_US/intro.xml:31(para) +msgid "DocBook XML v4.4" +msgstr "" + +#: en_US/intro.xml:34(para) +msgid "Custom XSLT stylesheets for both print and HTML versions" +msgstr "" + +#: en_US/intro.xml:38(para) +msgid "Custom scripts to generate HTML output (use <command>xmlto</command>)" +msgstr "" + +#: en_US/intro.xml:42(para) +msgid "Emacs with PSGML mode (optional, but recommended)" +msgstr "" + +#: 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 "" + +#: 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:43(title) +msgid "Fedora Documentation Tools" +msgstr "" + +#: 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 "" + +#: en_US/getting-files.xml:53(replaceable) +#: en_US/getting-files.xml:54(replaceable) +msgid "my-fedora-docs-sandbox" +msgstr "" + +#: en_US/getting-files.xml:55(replaceable) +msgid "username" +msgstr "utilizador" + +#: en_US/getting-files.xml:53(userinput) +#, no-wrap +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 "" + +#: en_US/getting-files.xml:60(para) +msgid "At the password prompt, press the <keycap>Enter</keycap> key." +msgstr "" + +#: 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 "" + +#: en_US/getting-files.xml:73(para) +msgid "" +"To work on existing documents in CVS, refer to <xref linkend=\"ch-cvs\"/>." +msgstr "" + +#: en_US/getting-files.xml:80(title) +msgid "Filename Conventions" +msgstr "" + +#: 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 "" + +#: en_US/getting-files.xml:89(title) +msgid "Document Filenames" +msgstr "" + +#: 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 "" + +#: en_US/getting-files.xml:98(title) +msgid "Partial List of CVS Modules" +msgstr "" + +#: en_US/getting-files.xml:99(userinput) +#, no-wrap +msgid "cd ~/localrepo/fedora-docs/" +msgstr "" + +#: en_US/getting-files.xml:100(computeroutput) +#, no-wrap +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 "" + +#: 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 "" + +#: en_US/getting-files.xml:112(title) +msgid "Avoid Redundancy" +msgstr "" + +#: 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 "" + +#: 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: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) +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: <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 "" + +#: 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 "" + +#: en_US/emacs.xml:198(para) +msgid "" +"If you are using the older version 20 of <application>Emacs</application>, " +"add the following instead:" +msgstr "" + +#: en_US/emacs.xml:229(title) +msgid "Customizing Emacs" +msgstr "" + +#: en_US/emacs.xml:233(secondary) +msgid "customizing" +msgstr "" + +#: en_US/emacs.xml:237(filename) +msgid ".Xresources" +msgstr "" + +#: en_US/emacs.xml:242(secondary) +msgid "colors" +msgstr "" + +#: en_US/emacs.xml:247(secondary) +msgid "font" +msgstr "" + +#: en_US/emacs.xml:252(secondary) +msgid "geometry" +msgstr "" + +#: 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 "" + +#: en_US/emacs.xml:261(para) +msgid "The following is a sample <filename>~/.Xresources</filename> file." +msgstr "" + +#: 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 "" + +#: en_US/emacs.xml:282(para) +msgid "After modifying this file, you must execute the command" +msgstr "" + +#: en_US/emacs.xml:286(command) +msgid "xrdb -merge ~/.Xresources" +msgstr "" + +#: 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" +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/>" +msgstr "" + +#: 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 "" + +#: en_US/emacs.xml:406(title) +msgid "Basic Emacs Commands" +msgstr "" + +#: en_US/emacs.xml:408(para) +msgid "The <keycap>Meta</keycap> key is usually the <keycap>Alt</keycap> key." +msgstr "" + +#: en_US/emacs.xml:413(title) +msgid "Emacs Commands" +msgstr "" + +#: en_US/emacs.xml:414(segtitle) +msgid "Shortcut" +msgstr "" + +#: 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) +msgid "Meta" +msgstr "" + +#: 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) +msgid "x" +msgstr "" + +#: 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) +msgid "Enter" +msgstr "" + +#: en_US/emacs.xml:417(seg) +msgid "" +"<keycombo><placeholder-1/><placeholder-2/></keycombo> sgml-parse-prolog, " +"<placeholder-3/>" +msgstr "" + +#: en_US/emacs.xml:420(seg) +msgid "Parse DTD" +msgstr "" + +#: 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) +msgid "Ctrl" +msgstr "Ctrl" + +#: 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) +msgid "c" +msgstr "" + +#: en_US/emacs.xml:434(keycap) en_US/emacs.xml:440(keycap) +msgid "Shift" +msgstr "Shift" + +#: en_US/emacs.xml:435(keycap) en_US/emacs.xml:442(keycap) +msgid "Tab" +msgstr "" + +#: en_US/emacs.xml:433(seg) +msgid "" +"<keycombo><placeholder-1/><placeholder-2/></keycombo>, " +"<keycombo><placeholder-3/><keycap/></keycombo>, <placeholder-4/>" +msgstr "" + +#: en_US/emacs.xml:436(seg) +msgid "Display list of valid tags" +msgstr "" + +#: 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 "" + +#: en_US/emacs.xml:443(seg) +msgid "Complete the tag" +msgstr "" + +#: en_US/emacs.xml:446(keycap) +msgid "g" +msgstr "" + +#: en_US/emacs.xml:448(seg) +msgid "Cancel a command in the minibuffer" +msgstr "" + +#: en_US/emacs.xml:452(keycap) +msgid "/" +msgstr "/" + +#: en_US/emacs.xml:451(seg) +msgid "<keycombo><placeholder-1/><placeholder-2/></keycombo>, <placeholder-3/>" +msgstr "" + +#: en_US/emacs.xml:453(seg) +msgid "Close tag" +msgstr "" + +#: en_US/emacs.xml:456(keycap) en_US/emacs.xml:536(keycap) +msgid "a" +msgstr "" + +#: en_US/emacs.xml:458(seg) +msgid "Move cursor to beginning of line" +msgstr "" + +#: en_US/emacs.xml:461(keycap) +msgid "e" +msgstr "" + +#: en_US/emacs.xml:463(seg) +msgid "Move cursor to the end of the line" +msgstr "" + +#: en_US/emacs.xml:466(keycap) +msgid "Home" +msgstr "" + +#: en_US/emacs.xml:468(seg) +msgid "Move cursor to the beginning of the file" +msgstr "" + +#: en_US/emacs.xml:471(keycap) +msgid "End" +msgstr "Fim" + +#: en_US/emacs.xml:473(seg) +msgid "Move cursor to the end of the file" +msgstr "" + +#: en_US/emacs.xml:476(keycap) +msgid "k" +msgstr "" + +#: en_US/emacs.xml:478(seg) +msgid "Cut line" +msgstr "" + +#: en_US/emacs.xml:481(keycap) +msgid "y" +msgstr "" + +#: en_US/emacs.xml:483(seg) +msgid "Paste line" +msgstr "" + +#: en_US/emacs.xml:486(keycap) en_US/emacs.xml:518(keycap) +msgid "s" +msgstr "" + +#: en_US/emacs.xml:488(seg) +msgid "Search forward in the file" +msgstr "" + +#: en_US/emacs.xml:491(keycap) +msgid "r" +msgstr "" + +#: en_US/emacs.xml:493(seg) +msgid "Search backwards in the file" +msgstr "" + +#: en_US/emacs.xml:496(keycap) +msgid "$" +msgstr "$" + +#: en_US/emacs.xml:498(seg) en_US/emacs.xml:503(seg) +msgid "Check spelling of current word" +msgstr "" + +#: en_US/emacs.xml:501(seg) +msgid "" +"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-word, " +"<placeholder-3/>" +msgstr "" + +#: en_US/emacs.xml:506(seg) +msgid "" +"<keycombo><placeholder-1/><placeholder-2/></keycombo> ispell-buffer, " +"<placeholder-3/>" +msgstr "" + +#: en_US/emacs.xml:508(seg) +msgid "Check spelling of current buffer" +msgstr "" + +#: en_US/emacs.xml:512(keycap) +msgid "f" +msgstr "f" + +#: 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 "" + +#: en_US/emacs.xml:514(seg) +msgid "Open file" +msgstr "" + +#: en_US/emacs.xml:520(seg) +msgid "Save file" +msgstr "" + +#: en_US/emacs.xml:526(seg) +msgid "Exit <placeholder-1/> and prompt to save files if necessary" +msgstr "" + +#: en_US/emacs.xml:530(keycap) +msgid "q" +msgstr "" + +#: en_US/emacs.xml:532(seg) +msgid "Fill paragraph" +msgstr "" + +#: en_US/emacs.xml:539(computeroutput) +#, no-wrap +msgid "url" +msgstr "" + +#: 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 "" + +#: en_US/emacs.xml:547(seg) +msgid "Exit edit attributes" +msgstr "" + +#: en_US/emacs.xml:554(title) en_US/emacs-nxml.xml:77(title) +msgid "Examples" +msgstr "" + +#: 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 "" + +#: en_US/emacs.xml:562(title) +msgid "Tag Completion" +msgstr "" + +#: en_US/emacs.xml:566(para) +msgid "" +"This section assumes that you have already loaded the DTD file (<filename>." +"ced</filename>)." +msgstr "" + +#: 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 "" + +#: en_US/emacs.xml:578(computeroutput) +#, no-wrap +msgid "Tag: <" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: en_US/emacs.xml:596(para) +msgid "The output should look similar to the example below:" +msgstr "" + +#: 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 "" + +#: en_US/emacs.xml:613(title) +msgid "Tag Closure" +msgstr "" + +#: 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 "" + +#: en_US/emacs.xml:625(title) +msgid "Other Emacs Tasks" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: en_US/emacs.xml:673(title) en_US/emacs-nxml.xml:127(title) +msgid "Additional Resources" +msgstr "Recursos Adicionais" + +#: en_US/emacs.xml:675(para) +msgid "" +"Additional Emacs and PSGML references are available at the following " +"locations:" +msgstr "" + +#: 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) +msgid "Emacs Quick Reference Guide" +msgstr "" + +#: 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 "" + +#: 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 "" + +#: 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 "" + +#: en_US/emacs.xml:705(ulink) +msgid "http://www.snee.com/bob/sgmlfree/emcspsgm.html" +msgstr "" + +#: en_US/emacs.xml:706(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: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 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 "" + +#: 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 " +"(stickstr5 at hotmail.com)." +msgstr "" + +#: 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 "" + +#: 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 "" + +#. 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." |