From 61a20c86d0c522791400bfd924fe6d26bb20d910 Mon Sep 17 00:00:00 2001 From: "Paul W. Frields" Date: Sun, 11 Mar 2007 21:33:23 +0000 Subject: Remove old and osbsolete zh_CN XML files. Preserve what we can in new PO file, thanks to the genius of xml2po and msgmerge. --- acknowledgments-zh_CN.xml | 11 - docs-emacs-nxml-zh_CN.xml | 123 - docs-emacs-zh_CN.xml | 533 --- docs-getting-files-zh_CN.xml | 286 -- docs-intro-zh_CN.xml | 24 - docs-rh-guidelines-zh_CN.xml | 415 --- docs-style-zh_CN.xml | 1047 ------ docs-tutorial-zh_CN.xml | 72 - docs-vim-zh_CN.xml | 87 - docs-xml-tags-zh_CN.xml | 1613 --------- documentation-guide-zh_CN.xml | 44 - po/zh_CN.po | 7465 +++++++++++++++++++++++++++++++++++++++++ 12 files changed, 7465 insertions(+), 4255 deletions(-) delete mode 100644 acknowledgments-zh_CN.xml delete mode 100644 docs-emacs-nxml-zh_CN.xml delete mode 100644 docs-emacs-zh_CN.xml delete mode 100644 docs-getting-files-zh_CN.xml delete mode 100644 docs-intro-zh_CN.xml delete mode 100644 docs-rh-guidelines-zh_CN.xml delete mode 100644 docs-style-zh_CN.xml delete mode 100644 docs-tutorial-zh_CN.xml delete mode 100644 docs-vim-zh_CN.xml delete mode 100644 docs-xml-tags-zh_CN.xml delete mode 100644 documentation-guide-zh_CN.xml create mode 100644 po/zh_CN.po diff --git a/acknowledgments-zh_CN.xml b/acknowledgments-zh_CN.xml deleted file mode 100644 index 11770bd..0000000 --- a/acknowledgments-zh_CN.xml +++ /dev/null @@ -1,11 +0,0 @@ - - - 致谢 - 本文档基于 Tammy Fox (tfox at redhat.com) 起草的一篇文档，并得到了 Sandra Moore (smoore at redhat.com) 和 Johnray Fuller (jrfuller at redhat.com) 的协助。 - Roozbeh Pournader (roozbeh at sharif.edu) 的补丁已被合并，修正了一些拼写错误，解释了匿名 CVS 访问时禁止提交的情况。 - Gavin Henry (ghenry at suretecsystems.com) 的补丁已被合并，向 docs-xml-tags.xml 中的 figure 标记范例添加尾部斜线，以及添加 。 - Joshua Daniel Franklin (joshuadfranklin at yahoo.com) 的补丁已被合并，添加 。 - Karsten Wade (kwade at redhat.com) 的补丁已被合并，添加 。它为 Paul W. Frields (stickstr5 at hotmail.com) 编辑。 - Paul W. Frields (stickstr5 at hotmail.com) 的补丁已被合并，向 中的 screen 标记集合添加更多解释。 - 合并了 Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) 的补丁，详细解释文档构建系统。 - diff --git a/docs-emacs-nxml-zh_CN.xml b/docs-emacs-nxml-zh_CN.xml deleted file mode 100644 index 071201b..0000000 --- a/docs-emacs-nxml-zh_CN.xml +++ /dev/null @@ -1,123 +0,0 @@ - - - Emacs 与 nXML 模式 - - nXML - - - Emacs - - - Emacs - nXML 模式 - - 您可以使用 Emacs 的 nXML 模式，使撰写 DocBook XML 格式更加简单。nXML 模式提供了上下文敏感的编辑模式，包括补全、实时的有效性检测、语法高亮和缩进。为此您只要安装一个 RPM 软件包！ - - 开发早期 - 需要注意的是，Emacs 的 nXML 模式尚不完善，因此在编辑一些文档时，高级用户可能会注意到一些问题。如果您略微关注一下邮件列表，就可以获得相关信息，也可以问问题。请参考 。 - - - 下载 nXML RPM - - nXML - RPM - - - nXML RPM - - 要在 emacs 中使用 nXML 模式，您需要安装 Tim Waugh 网站上的 nXML RPM，或者下载 http://www.thaiopensource.com/download/ 的源代码。源代码需要花工夫来配置，因此这里只考虑 RPM 版本。 - 关于下载源代码请参考 。 - - - 范例 - 与 PSGML 模式相比，您只需有数几个命令。这样使用 Emacs 编辑就快捷多了，您可以更多地关注文章的内容。 - - 命令 - 要创建一个标记，输入 < 然后输入关键字。要完成这个关键字，按下 Ctrl-Ret，然后添加随后的 >。要关闭一个标记，输入 </。 - - 注意 - 当您打开不包含首部 DOCTYPE 声明的文件时，将看到如下信息，标记补全也无法实现，因为 nXML 不知道您在编辑的文件格式。 - - 要加载 schema，按下 Ctrl-c，然后按 Ctrl-s 然后浏览 /usr/share/emacs/site-lisp/nxml-mode/schema/ 并加载 docbook.rnc。Emacs 将提示您将它保存到工作目录。 - - 技巧 - 已描述过的命令只是 Emacs PSGML 模式与 Emacs nXML 模式的不同之处。您仍然需要使用 中描述的命令。 - - - - - 其他资源 - 其他的 Emacs 与 nXML 帮助可以在下列位置找到： - - - - http://www.thaiopensource.com/download/ — Author's download area - - - - http://wks.uts.ohio-state.edu/unix_course/intro-135.html — Emacs Quick Reference Guide - - - - emacs 软件包附带了 Emacs 参考卡片。您可以打印一份，作为参考。— /usr/share/emacs/<version>/etc/refcard.ps - - - - - nXML README 文件 - - 注意 - 这个文件可以在您解压的源代码中找到，如果安装了 RPM，它的位置是 /usr/share/doc/nxml-mode-<version>/。 - - README 文件： - 这是 GNU Emacs 的一种新的主模式。它支持格式良好的 XML 文档，也为采用 RELAX NG Compact Syntax 的 XML 文档提供了 schema-sensitive 编辑模式。 - 要使用它，您需要 GNU Emacs 21.x 版本，推荐 21.3。GNU Emacs 20 版本中无法正常运作，XEmacs 也不行。要开始编辑，输入命令： - - M-x load-file RET rng-auto.el RET - - 这样定义了必需的 autoloads。然后，打开一个包含 XML 文档的文件，执行命令： - - M-x nxml-mode - - 然后执行 - - C-h m - - 来查看 nXML 模式的使用帮助。手册的起始页在 nxml-mode.info 中，可以这样阅读它： - - C-u M-x info RET nxml-mode.info RET - - 它也在顶层 info 目录最后添加了自己的一项，因此您可以和平常一样，用 C-h i 开始阅读。 - 您可以用 test.valid.xml 和 test.invalid.xml 作为正确和不正确的 XML 文档范例。 - 要在 Emacs 启动时自动加载这些，将下列内容加入您的 .emacs： - - -(load "~/nxml-mode-200YMMDD/rng-auto.el") - - - 这里 ~/nxml-mode-200YMMDD 是包含 .elc 文件的目录。注意 rng-auto.el 不会加载所有 nXML 模式的代码；它仅仅设置环境，使得 nXML 模式的所有特性得以正确地自动加载。您不应尝试自动加载 rng-auto.el 本身。 - 要在加载扩展名是 xml, xsl, rng 或 xhtml 的文件时自动切换到 nXML 模式，将下列内容加入您的 .emacs： - - -(setq auto-mode-alist - (cons '("\\.\\(xml\\|xsl\\|rng\\|xhtml\\)\\'" . nxml-mode) - auto-mode-alist)) - - - 如果您编辑 iso-8859-N 编码的 XML，而不是 iso-8859-1，并且您运行的是 Emacs 21.3 或更新版本，那么最好打开 unify-8859-on-decoding-mode，将下列内容加入您的 .emacs： - - (unify-8859-on-decoding-mode) - - 要使用验证以及 schema-sensitive 编辑模式，您需要文档的 RELAX NG Compact Syntax (RNC) schema 文件。schema 目录包含了常用文档类型的 schema。 - 关于 RELAX NG 请参考 http://relaxng.org/。 - 关于 RELAX NG Compact NG 的教程请参考 http://relaxng.org/compact-tutorial.html - 关于自动创建 RNC schema，推荐使用 Trang 程序：http://eee.thaiopensource.com/relaxng/trang.html" - 您可以使用它来 从已有文档得出 RNC schema将 DTD 转换为 RNC schema将 RELAX NG XML syntax schema 转换为 RNC schema - 要将 RELAX NG XML syntax (.rng) schema 转换为 RNC schema，您也可以使用 http://www.pantor.com/download.html" 的 XSLT 样式表。 - 要将 W3C XML Schema 转换为 RNC schema，您需要首先将它转换为 RELAX NG XML syntax，使用 Sun 的 RELAX NG 转换工具 rngconv (基于 MSV)。请参考 https://www.dev.java.net/。 - 文件 NEWS 描述了最近的更改。 - 请访问邮件列表 http://groups.yahoo.com/group/emacs-nxml-mode 来提交 bug 和参与讨论。我将在那里发布新版本。 - James Clark - jjc@thaiopensource.com - - diff --git a/docs-emacs-zh_CN.xml b/docs-emacs-zh_CN.xml deleted file mode 100644 index 67886e2..0000000 --- a/docs-emacs-zh_CN.xml +++ /dev/null @@ -1,533 +0,0 @@ - - - Emacs 与 PSGML 模式 - - PSGML - - - Emacs - - - Emacs - PSGML 模式 - - 您可以利用 Emacs 的 PSGML 模式以使编辑 XML 格式更容易。PSGML 模式提供了语法高亮，标记补全等功能。 - - 设置您的 <filename>.emacs</filename> - - Emacs - 配置文件 - - - - .emacs - - - 为使 Emacs 可以正确解析您的 DocBook 文档，您必须定制一个 .emacs 文件。将下列内容复制并粘贴到您已有的 .emacs 文件中，或者创建一个包含下列内容的新文件： -;; turn on auto-fill in `text-mode' and derived modes -;;(mail, news, etc) -(add-hook 'text-mode-hook 'turn-on-auto-fill) - -;; -;;MODES -;; - -(setq auto-mode-alist (cons '("\\.sgml$" . sgml-mode) auto-mode-alist)) -(setq auto-mode-alist (cons '("\\.sgm$" . sgml-mode) auto-mode-alist)) - -;; -;;XML!! -;; -;;############################################################# - -;; -;;PSGML mode stuff -;; - -(autoload 'sgml-mode "psgml" "My Most Major Mode" t) - -(setq sgml-mode-hook '(lambda () "Defaults for XML mode." (turn-on-auto-fill) -(setq fill-column 80))) - -(defun My-XML-keymap () - (local-set-key [(alt i)] - '(lambda () - (interactive) - (sgml-indent-line) - (sgml-insert-element 'item) - (sgml-indent-line))) - (local-set-key [(alt l)] - '(lambda () - (interactive) - (sgml-insert-element 'list) - (sgml-insert-element 'item) - (sgml-indent-line))) - (local-set-key [(alt p)] - '(lambda () - (interactive) - (sgml-indent-line) - (sgml-insert-element 'para) - (sgml-indent-line))) - (local-set-key [(alt -)] - '(lambda () - (interactive) - (insert "—")))) - -(add-hook 'sgml-mode-hook 'My-XML-keymap) - -;; -;; Fix up indentation of data... -;; - -(setq-default sgml-indent-data t) - -;; -;; XML markup faces. -;; - -(setq-default sgml-set-face t) - - -(make-face 'sgml-comment-face) -(make-face 'sgml-doctype-face) -(make-face 'sgml-end-tag-face) -(make-face 'sgml-entity-face) -(make-face 'sgml-ignored-face) -(make-face 'sgml-ms-end-face) -(make-face 'sgml-ms-start-face) -(make-face 'sgml-pi-face) -(make-face 'sgml-sgml-face) -(make-face 'sgml-short-ref-face) -(make-face 'sgml-start-tag-face) - -(set-face-foreground 'sgml-comment-face "maroon") -(set-face-foreground 'sgml-doctype-face "dark green") -(set-face-foreground 'sgml-end-tag-face "blue2") -(set-face-foreground 'sgml-entity-face "red2") -(set-face-foreground 'sgml-ignored-face "maroon") -(set-face-background 'sgml-ignored-face "gray90") -(set-face-foreground 'sgml-ms-end-face "maroon") -(set-face-foreground 'sgml-ms-start-face "maroon") -(set-face-foreground 'sgml-pi-face "maroon") -(set-face-foreground 'sgml-sgml-face "maroon") -(set-face-foreground 'sgml-short-ref-face "goldenrod") -(set-face-foreground 'sgml-start-tag-face "blue2") - -(setq-default sgml-markup-faces - '((comment . sgml-comment-face) - (doctype . sgml-doctype-face) - (end-tag . sgml-end-tag-face) - (entity . sgml-entity-face) - (ignored . sgml-ignored-face) - (ms-end . sgml-ms-end-face) - (ms-start . sgml-ms-start-face) - (pi . sgml-pi-face) - (sgml . sgml-sgml-face) - (short-ref . sgml-short-ref-face) - (start-tag . sgml-start-tag-face))) - - -(defun docbook-mode () - (sgml-mode) - ) - - - -;; -;;END XML STUFF -;; -;;################################################################## - -;PO mode stuff - -(setq auto-mode-alist - (cons '("\\.pox?\\'" . po-mode) auto-mode-alist)) -(autoload 'po-mode "po-mode") - - - (global-set-key [(f1)] (lambda () (interactive) (manual- - entry (current-word)))) - - - 您是否有一个滚轮鼠标？如果是，那么可以将下列内容加入您的 .emacs，这样您的滚轮将可以用在 Emacs 中 (适于 Emacs 版本 21)： - - -;; Enable wheelmouse support by default for emacs 21 -(cond (window-system -(mwheel-install) -)) - - - 如果您使用旧的 20 版本，应添加下列内容： - - -;; Enable wheelmouse support by default -(require 'mwheel) - - - - - - - - - 定制 Emacs - - Emacs - 定制 - - - - .Xresources - - - - Emacs - colors - - - Emacs - font - - - Emacs - geometry - - 在您的 ~/.Xresources 中配置 Emacs 的颜色，字体和默认窗口大小。设置的格式是 emacs.keyword:value - 下面是一个 ~/.Xresources 文件范例。 - - 注意 - 如果您的 ~/.Xresources 中包含其他设置，就将下列内容添加到文件结尾。 - - - -emacs.background: light gray -emacs.foreground: black -emacs.pointerColor: blue -emacs.cursorColor: blue -emacs.bitmapIcon: on -emacs.font: fixed -emacs.geometry: 90x25 - - - 修改文件后，您必须执行命令 - - xrdb -merge ~/.Xresources - - 并且重新运行 Emacs 以使改变生效。 - - - 创建重编译的 DTD 子集 - 如果给出了正确的文档类型声明 (DTD) 文件，Emacs 可以对 DocBook XML 文件进行正确的语法高亮和缩进。这些特性将使您的 XML 文件易于阅读，帮助您发现错误。 - 要创建一个可加载的已解析的 DTD 文件：找到一组 DocBook 文件的主控文件。您可以通过头部是否包含 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN" 来找到它。最简单的办法，是运行命令 grep DocBook *.xml。找到主控文件后，在 Emacs 中打开它，命令是 emacs <parentfile>.xml (这里 <parentfile>.xml 是你找到的主控文件)。在下拉菜单中选择 DTD -> Parse DTD。当您看到屏幕下方的 Fontifying...done 信息时，解析就完成了。将已解析的 DTD 保存为文件，方法是在下拉菜单中选择 DTD -> Save Parsed DTD。按下 Enter 来保存为默认文件名，或者修改文件名，但应保留 .ced 扩展名。可以将它命名为 docbook.ced 这样很通用的名字，这样您在打开所有 DocBook 文件的时候都可以引用它。这个文件也可以复制到要加载的目录中。 - - 技巧 - 您也可以使用 Emacs 命令 Meta-x sgml-parse-prolog 来解析这个文件，然后用命令 Meta-x sgml-save-dtd 来保存已解析的 DTD 到 .ced 文件中。 - - - - 加载已解析的 DTD - 现在您已保存了 DTD 设置，您可以加载这个 .ced 文件，看看 .sgml 文件语法高亮的效果。 - 要加载已解析的 DTD 文件：在 Emacs 中打开 XML 文件在下拉菜单中选择 DTD -> Load DTD 然后选择您在上一步保存的文件。例如，选择 docbook.ced。当您看到屏幕下方的 Fontifying...done 信息时，就加载完毕了。加载已解析的 DTD 可能需要很久。您可以在加载完毕前就开始编辑。 - - 技巧 - 您也可以使用 Emacs 命令 Meta-x sgml-load-dtd 来加载已翻译的 DTD。 - - - - 基本的 Emacs 命令 - - Meta 键通常指的是 Alt 键。 - - Emacs 命令 - - - - - - 快捷方式 - 描述 - - - - - - - Meta - x - sgml-parse-prolog, Enter - 解析 DTD - - - - - Meta - x - sgml-save-dtd, Enter - 保存已解析的 DTD - - - - - Meta - x - sgml-load-dtd, Enter - 加载 DTD - - - - - Ctrl - c - , Shift, Tab - 显示有效标记的列表 - - - - - Ctrl - c - , Shift, type beginning of tag, Tab - 补全标记 - - - - - Ctrl g - - 取消 minibuffer 中的命令 - - - - - Ctrl - c - , / - 关闭标记 - - - - - Ctrl a - - 将光标移动到行首 - - - - - Ctrl - e - - - 将光标移动到行尾 - - - - - Ctrl - Home - - - 将光标移动到文件开始 - - - - - Ctrl - End - - - 将光标移动到文件结束 - - - - - Ctrl - k - - - 剪切一行 - - - - - Ctrl y - - 粘贴一行 - - - - - Ctrl s - - 在文件中向前搜索 - - - - - Ctrl - r - - - 在文件中向后搜索 - - - - - Meta - $ - - - 检查当前单词的拼写 - - - - - Meta - x - ispell-word, Enter - 检查当前单词的拼写 - - - - - Meta - x - ispell-buffer, Enter - 检测当前 buffer 的拼写 - - - - - Ctrl - x - , Ctrlf - 打开文件 - - - - - Ctrl - x - , Ctrls - 保存文件 - - - - - Ctrl - x - , Ctrlc - 退出 Emacs，在需要时提示保存文件 - - - - - Meta q - - 段落重排 - - - - - Ctrl - c - , Ctrla - 编辑标记的属性 (例如，您可以编辑 ulink 标记的 url 属性) - - - - - Ctrl - c - , Ctrlc - 结束编辑属性 - - - -
- - - 范例 - Emacs 和 PSGML 的命令表 (参考卡片) 对于新手来说有些难。本节有一些例子，讲解如何使用它们。 - - 标记补全 - - 注意 - 本节假设您已经加载了 DTD 文件 (.ced)。 - - 需要插入标记时，不要输入它。按下组合键 Ctrl-c, 然后按下 <。在 Emacs 窗口的下方，您将看到： - - Tag: < - - 要查看所有标记的列表，按下 Tab 或 ?。如果您知道标记的首字母，可以按下它们，然后按 Tab，就可以看到有同样首字母的所有标记的列表。 - 尝试这样：按下 Ctrl-c 然后按 <，然后按下字母 k，然后按 Tab。为了得到完整的列表，您可能需要多次按下 Tab。 - 输出应当与下面类似： - - -Click mouse-2 on a completion to select it. -In this buffer, type RET to select the completion near point. - -Possible completions are: -<keycap> <keycode> -<keycombo> <keysym> - - - - - 标记关闭 - 当您开始了一个标记后，您必须关闭它。按下组合键 Ctrl-c，然后按 /。这样将关闭最近一个开放的标记。 - - - 其他 Emacs 任务 - - 恢复单个窗口: 有时 Emacs 窗口被划分 (下方的窗口有标记补全等内容)。要恢复到只有您的 XML 文本全屏显示的状态，最简单的办法是按下 Ctrl-x，然后按 1。 - - 保存作品: 要保存编辑结果，按下 Ctrl-x 然后按 Ctrl-s。 - - "清除/返回"命令:有时，在标记补全中玩得太多，需要直接返回编辑时，按下 Ctrl-g。这个命令将放弃当前动作，而不会关闭文件本身。 - - 打开文件: 要打开一个新文件，按下 Ctrl-x 然后按 Ctrl-f。在窗口下方，可以输入要打开文件名 (这里也可以使用 Tab 补全)。 - - 关闭 emacs: 要关闭 emacs，按下 Ctrl-x 然后按 Ctrl-c。如果您尚未保存，它将提示，否则它会简单地退出。 - - - - 其他资源 - 其他 Emacs 和 PSGML 参考可以在这里找到： - - - - http://wks.uts.ohio-state.edu/unix_course/intro-135.html — Emacs Quick Reference Guide - - emacs 软件包附带了 Emacs 参考卡片。您可以打印一份，作为参考。— /usr/share/emacs/<version>/etc/refcard.ps - - - /usr/share/doc/psgml-<version>/psgml.ps 中的 Editing XML with Emacs and PSGML。 - - - - http://www.snee.com/bob/sgmlfree/psgmqref.html — Emacs/PSGML Quick Reference 是一个 Emacs PSGML 模式的索引表。 - - - - http://www.snee.com/bob/sgmlfree/emcspsgm.html — PSGML Tricks - - - - diff --git a/docs-getting-files-zh_CN.xml b/docs-getting-files-zh_CN.xml deleted file mode 100644 index 7b0304f..0000000 --- a/docs-getting-files-zh_CN.xml +++ /dev/null @@ -1,286 +0,0 @@ - - - 先决要求 - 在操作 &FED; 文档之前，您必须安装合适的工具和软件包。下面的步骤将帮您配置系统。 -
- 系统软件包 - 要开始为 Docs Project 贡献力量，您需要适当的 DocBook XML 文件，样式表以及一些脚本。需要安装下列软件包： - - - - xmlto — 生成 HTML 和 PDF 输出。 - - - - docbook-style-xsl — 我们构建时默认的 XSLT 样式单。 - - - - docbook-dtds — DocBook DTD 针对 XML 的版本 - - - 您可以这样检查系统中的软件包，运行命令： - - -rpm -q xmlto -rpm -q docbook-style-xsl -rpm -q docbook-dtds - - - 如果缺少什么软件包，就用 yum(8) 来安装： - - -su -c 'yum install xmlto' -su -c 'yum install docbook-style-xsl' -su -c 'yum install docbook-dtds' - - -
-
- Fedora 文档工具 - 您只需执行这些步骤一次。这些文件对所有 &FDPX; 文档都是一致的。 - 常用的脚本和样式表都存放在 cvs.fedora.redhat.com CVS 服务器的仓库中。您需要将它们以及已有文档的 DocBook XML 文件检出。 - 当您看到密码提示时，按下 Enter 键。在下面的例子中，我们演示了如何获取一份已有的 &FDPX; 文档的复本。 - - mkdir my-fedora-docs-sandbox -cd my-fedora-docs-sandbox -export CVSROOT=:pserver:anonymous@cvs.fedora.redhat.com:/cvs/docs -cvs login -cvs co docs-common -cvs co example-tutorial - -
-
- 文件名约定 - &FDPX; 提供了工具、脚本和样式单来将您的 XML 文档转换为 HTML 和 PDF 输出格式。另外，您的文档还可以被自动构建为 RPM 软件包。 - 要利用这些服务，您应当遵循为文件命名的规范。无论选择什么名字，采用我们的建议将使事情简单许多。当然，如果您将自己的文档导入我们的构建系统，修改数以百计的文件名字也许过于繁杂；请放松，只要稍作修改就可以满足要求了。请继续阅读。 -
- 文档文件名 - 每个文档有单独的目录，与先前从 &FED; 文档中检出的 docs-common 目录并列。将您的文档目录命名为与内容相关的名字，避免使用已有的名称。前面提到的 cvs co -c 命令可以显示已有的名称。 -
-
- 与 I18N 国际化翻译组合作 - &FDPX; 包括一支活跃的翻译团队。项目文档被译为多种语言。根据约定，译文与原始文档处于同一目录；文件名必须唯一。 - &FDPX; 文件名的扩展名前面，必须是一个连字符加上 ISO 语言名称。例如，如果文件内容是 US(美国英语)，可以命名为 mydoc-en.xml；而它的简体中文译文将命名为 mydoc-zh_CN.xml，以此类推。 - 为了促进这种努力，文档构建系统假定每个文件都包含了 I18N 国际化语言环境标记。我们的文件名约定在 中讲述 - - &FDPX; 文件名约定 - - - - - - - 组件 - - - 描述 - - - - - - - - 除连字符外的其他字符 - - - - 文件名的第一部分可以是各种字符，只要不使用连字符(dash)。 - - - - - - - - - - - 连字符 (-) 用来引入 ${LANG} 文件名组件。 - - - - - - ${LANG} - - - - - ${LANG} 组件区分了文件内容的 locale(语言环境)。 - 除了根据语言区分文件外，我们还用 ${LANG} 的值作为输出文档时的 UTF-8 语言环境。例如，文档 mydoc-it.xml 在渲染时会使用 it.UTF-8 作为语言环境。 - 有关更多 I18N 本地化的信息请访问 网站。 - - - - -
- - 文档文件名是特别的 - 文档的主控文件 必须 依据文件命名约定，否则构建系统无法找到它。 - -
-
-
- 文档构建系统 - 一般的工作，类似将文档渲染为 HTML 或 PDF 可以很容易地用文档构建系统实现。 - 构建系统依赖于 make(1) 工具和 shell 脚本的强大功能，来自动完成这些工作。但是，作为作者，无须 有使用 shell 脚本或 Makefile 的经验。尽管每篇文档都拥有自己的 Makefile，它通常只有几行的长度，非常简单。文件 Makefile 的内容被设计为可以拷贝 'n 粘贴。 - 例如， 显示了一个简单文档(只有一个文件，且只有一种语言)的完整 Makefile。 - - 示例文档 Makefile(编译控制文件) - -DOCBASE = mydoc -LANGUAGES = en -XMLEXTRAFILES-en= -include ../docs-common/Makefile.common - - - 我们的主控 XML 文件是 mydoc-en.xml；尚未添加翻译。 - - LANGUAGES 定义列出了英语的语言环境 en；如果出现了其他翻译，只要将它们的语言环境追加在这个定义中。 - 这份文档只包括主控文件 mydoc-en.xml，但是其他文档也许被划分为多个文件。 XMLEXTRAFILES-en 定义可以记录附加文件，这样在文件被改动时，构建系统就会注意到，并且在需要的时候重新构建文档。这个定义只是简单的文件列表。 - 最后一行，以 include(包含)开始，引用了主控的构建系统的 Makefile。Makefile.common 文件包含了所有 make(1) 目标以及规则，用来实际地构建文档以及各种文件。 - 添加新的文档翻译： - - - 将已翻译的文件添加到文档目录。一定要用正确的 ${LANG} 文件名组件，使文件名相似而唯一。 - - - 编辑 Makefile，追加新的 ${LANG} 到 LANGUAGES 定义中。 - - - 创建新的 XMLEXTRAFILES-${LANG} 定义，以引用除了主控文件之外的所有其他受影响的文档文件。 - - -
- 构建系统动作 - 要将 XML 文旦渲染为 HTML 或 PDF，运行命令： make html, make html-nochunk, 或 make pdf。 - - 列出了已定义的构建系统目标。 - - 文档构建目标 - - - - - - - 目标 - - - 描述 - - - - - - - - all - - - - 构建 HTML, 和 PDF 格式的文档，包括所有的译本。 - 同时构建打包，包括 tar(1) 和 rpm(8)。 - - - - - - tarball - - - - 只构建 tar(1) 打包，针对所有文档语言。 - - - - - - pdf - - - - 只构建 PDF 文档，针对所有文档语言。 - 当前，PDF 生成还有问题，可能无法使用。 - - - - - - html - - - - 只构建 HTML 文档，针对每种翻译。输出被放在单独的目录中：${DOCBASE}-${LANG}/；每一节在那个目录中都有对应的文件。 - - - - - - html-nochunks - - - - 只构建 HTML 文档，针对每种翻译。输出是一个单独的文件：${DOCBASE}-${LANG}.html；不会创建其他文件。 - - - - - - clean - - - - 删除所有临时文件和生成的文件。不会 删除任何 HTML, PDF, 或文件打包。 - - - - - - distclean - - - - 删除所有 HTML, PDF, 和文件打包。同时自动执行 clean 目标。 - - - - -
- 您可以添加自己特定的目标和规则，只要将它们添加在文件 Makefile 的最后，在 include 一行的下面。 - 在您的目标定义后面一定要用双冒号，不能只用一个。这样，您就可以为已定义的目标添加步骤了。 -
-
- 使用文档图象文件 - 图象文件，例如 .PNG，通常会在文档中用到。尽管文档可以存放在任何地方，我们建议您将图象文件存放在文档目录的 figs/ 子目录中。换句话说，图象 picture.png 应该是 mydoc/figs/picture.png 文件。 - - 使用 PNG 图象，不要用 JPG - 根据输出媒介不同，有时图象会被缩放，拉伸或压缩。为了减少变形，我们建议您只使用 PNG 图象，避免 JPG 文件。 - 您会发现 convert(1) 程序，来自 ImageMagickRPM 软件包，提供了转换已有的 JPG 文件的好办法。 - - 您可以将图象文件组织为 figs/ 目录下的子目录。文档构建系统会在输出文档中复制图象子目录的结构。 - 另外，我们建议您遵循文件名命名的约定。例如，一幅图象经常会包含标题或其他文本。这些文本应当像文档内容一样被翻译，因此区分 words-en.png 与 words-ru.png 是个好主意。不包含文本的图象文件可以简单地命名为 picture.png 之类。 - 有时，文档需要使用不遵循命名约定的图象。您可以在文档构建系统中使用这些图象，但是您必须创建一个文本文件，列出要使用的图象文件名。这个文件必须命名为 figs/Manifest-${LANG}，这样构建系统就可以在搜索图象文件名时找到它。 - 创建 figs/Manifest-${LANG} 文件的简单办法是 。 - - 构建一份清单(Manifest) - -rm -f figs/Manifest-en -find figs -print >/tmp/manifest -mv /tmp/manifest figs/Manifest-en -vi figs/Manifest-en - - -
-
- diff --git a/docs-intro-zh_CN.xml b/docs-intro-zh_CN.xml deleted file mode 100644 index 01733e7..0000000 --- a/docs-intro-zh_CN.xml +++ /dev/null @@ -1,24 +0,0 @@ - - - 介绍 - Docs Project 的目标是为 &FC; 用户和开发者创建易于维护，基于任务的文档。除了 &IG; 之外，所有文档必须是 DocBook XML article 格式，每个主题一篇文章。这样，作者就可以专注于撰写一个主题，不必考虑它如何排版为一个手册，或如何与其他主题协调。 - 要用到的工具： - - - DocBook XML v4.1 - - - 自定义的打印版本和 HTML 版本的 XSLT 样式表 - - - 自定义的脚本，以生成 PDF 版本和 HTML 版本的输出 (使用 xmlto) - - - Emacs PSGML 模式 (可选，推荐使用) - - - Emacs nXML 模式 (可选，同样推荐使用) - - - 本文档的目的是解释 Docs Project 使用的工具，同时提供写作约定和标记约定，使文档一致且易于维护。 - diff --git a/docs-rh-guidelines-zh_CN.xml b/docs-rh-guidelines-zh_CN.xml deleted file mode 100644 index 7615ed2..0000000 --- a/docs-rh-guidelines-zh_CN.xml +++ /dev/null @@ -1,415 +0,0 @@ - - - &RH; 文档撰写约定 - - recursion - recursion - - - RTFM - read the f*'ing manual - humor - - - humor - RTFM - - 请仔细阅读本章。本章描述了必须遵循的约定，例如命名约定。 - - ID 命名约定 - - XML 标记 - 命名约定 - - - 命名约定 - - 后面您将看到这样的 ID 命名。它们有助于理解这些命名的含义。例如： - - -<chapter id="ch-uniquename"> - -<sect3="s3-install-make-disks"> - -<figure id="fig-redhat-config-kickstart-basic"> - - - ID 是独一无二的标识符，使得 DocBook XML 得知如何交叉参考章、节等等。 - 定义 ID 的一般规则如下： - - XML 标记 - 定义 ID 的规则 - - - 命名约定 - 定义 ID 的规则 - - - - 至多使用 32 个字母 (这里指的是引号中所有内容) - - - 尽量短小而简单 - - - 确保命名与内容相关 (使它可辨识) - - - 例如，"ch-uniquename" (有 13 个字母) 以及 "s3-install-make-disks" (有 21 个字母)。 - 特定一章中的小节应当在 ID 中包含这一章的名称 (这一章的 ID 去掉 "ch-")。例如，您在撰写 "ch-intro" 一章，需要将有关磁盘分区的内容作为第一节时，小节 ID 将类似于 "s1-intro-partition"，它包含了小节编号，这一章的 ID 以及这一节的独一无二的 ID。 - - 命名约定 - - - - - - 标记 - 前缀 - - - - - - 前言 - - - pr- - - - - - chapter - - - ch- - - - - - 节 - - - sn- - - - - - 第一节 - - - s1- - - - - - 第二节 - - - s2- - - - - - 第三节 - - - s3- - - - - - 第四节 - - - s4- - - - - - figure - - - fig- - - - - - table - - - tb- - - - - - 附录 - - - ap- - - - - - part - - - pt- - - - - - example - - - ex- - - - - -
- - - 文件头 - 所有文件必须包含 CVS Id 头部。 - 如果您创建了一个新文件，第一行必须是： - - -<!-- $Id: --> - - - 它被提交到 CVS 中时 (在每次提交时)，这一行都会自动更新，以包含关于文件的信息。例如： - - -<!-- $Id: --> - - - - - 创建提示 - - 提示 - - - XML 标记 - 警告 - - - XML 标记 - 技巧 - - - XML 标记 - 注意 - - - XML 标记 - 小心 - - - XML 标记 - 重要 - - - XML 标记 - 提示 - 警告 - - - XML 标记 - 提示 - 技巧 - - - XML 标记 - 提示 - 注意 - - - XML 标记 - 提示 - 小心 - - - XML 标记 - 提示 - 重要 - - DocBook 中有五种提示类型：小心，重要，注意，技巧和警告。 - 所有提示都有类似的结构：可选的标题，随后是段落级的元素。DocBook DTD 没有定义每种提示的特殊语义。例如，DocBook 并未规定警告必须用于可能造成重大损失的情况。 - - 创建技巧，注意，小心，重要和警告提示 - - XML 标记 - 注意 - - - XML 标记 - 技巧 - - - XML 标记 - 小心 - - - XML 标记 - 重要 - - - XML 标记 - 警告 - - 有很多方法来使文档中的文本引人注意。Note 用于显示附加信息。Tip 用于显示完成任务的其他方法。Caution 用于告诫用户在尝试某一步时必须小心。Important 用于提醒用户不可忽视的信息，尽管用户动作不受影响，但是必须提醒用户信息的重要性。Warning 用于提醒读者，他们的设置将被修改或变动，例如文件将被删除，如果他们在意这一后果，就不应继续动作。 - 下列代码将展示上面每种情况的写法，同时也展示了 HTML 显示效果。 - - -<note> -<title>注意</title> -<para>文本内容</para> -</note> - - - - 注意 文本内容 - - -<tip> -<title>技巧</title> -<para>文本内容</para> -</tip> - - - - 技巧 - 文本内容 - - - -<caution> -<title>小心</title> -<para>文本内容</para> -</caution> - - - - 小心 文本内容 - - -<important> -<title>重要</title> -<para>文本内容</para> -</important> - - - - 注意 - 文本内容 - - - -<warning> -<title>警告</title> -<para>文本内容</para> -</warning> - - - - 警告 文本内容 - - - - 屏幕截图 - - 屏幕截图 - 如何截取 - - - 屏幕快照 - 屏幕截图 - - - 屏幕抓图 - 屏幕截图 - - 有两种类型的屏幕截图：图象和文本。选择它们的原则是 尽量使用文本截图。这意味着，如果您可以用文本而不是图象来表达，那么就用文本。GUI 的图象截图可以首先引入一些对象，然后用文字加以描述，但是您不会总是为每一步都创建一副截图。 - 这样选择的主要目的是文本块通常比占据相同空间的图象包含更多信息。这和具体图象有关，某个场景的准确的截图也许抵得上一千字的效果。GUI 的截图通常有很大空白，只包含很少元素，这样便于描述或列举。 - 截取图象的步骤本身表明了，使用文字来描述一个过程比起一系列的屏幕截图要精确许多。 - - - 图象截图 - - - - 设置主题为默认主题。这样读者会熟悉这一外观，也使得 &FDP; 文档显得一致。从菜单中，选择 Preferences, Theme 然后选 Bluecurve (&FC; 4 不再使用 Bluecurve)。 - - - 设置字体为默认值。从菜单中，选择 Preferences, Fonts. 然后设置 Application font 和 Desktop font 为 Sans Regular 10。设置 Window Title font 为 Sans Bold 10。设置 Terminal font 为 Monospace Regular 10。 - - - 在截图之前，试着将目标 GUI 元素调整到尽可能小。您的目标应当是 500 像素或更小。如果您需要截取超过一个 GUI 元素，可以按照下面的步骤来缩放图象。 - - - 要截取图象，使用鼠标选择 GUI 元素，将它放到最前，或者调整元素排列。按下 AltPrint Screen 来截取单个 GUI 窗口。要抓去整个桌面，按下 Print Screen。如果您要截取包含很多元素的图象，并已将它们靠近，那么还可以在 The GIMP 中裁减结果图象到适当大小。截取的图象将是 PNG 格式。 - - - 如果需要，您可以使用 The GIMP 缩放图象。打开图象，在图象上点击右键，选择 Image -> Scale Image...。保持长宽比不变，设置 New Width 为 500 px，然后点击 OK。记住在转换为 EPS 之前按下 Ctrls 保存图象。 - - - 仍使用 The GIMP 编辑图象，在图象上点击右键，选择 File -> Save As...。在 Determine File Type: 列表中，选择 PostScript，然后点击 OK。点击 Export，允许平整图象。 - 在 Save as PostScript 窗口，选择 Encapsulated PostScript，然后点击 OK。 - - - 关于如何在 XML 中调用图象，请参考 。 - - - - 文本截图 - - 文本的屏幕信息对读者也很有用。如果您可以同时用图象和文本截图描述某个功能，就不要同时包含它们，除非忽略任何一个都将使描述不清楚。您应当使得信息更加通用。忽略用户名和主机名信息，区分用户的输入与示例的输出。在 screen 标记中，用户输入应当包含在 userinput 标记内，而用户看到的输出应当包含在 computeroutput 标记内。例如， 的用法应该改为这样 - - 不正确的文本截图 - - ps ax | grep ssh - - 2564 ? S 0:23 /usr/sbin/sshd - 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients - 8235 ? S 0:00 ssh -Nf rocky@philadelphia.net -L 6667:localhost -17223 pts/0 S 0:00 ssh rbalboa@core-router7 -17227 pts/2 S 0:10 ssh rbalboa@smbshare2 -21113 pts/7 S 1:19 ssh rocky@xxx.private - - - - - 正确的文本截图 - 要显示所有当前活动的 ssh 会话，执行下列命令： - - ps ax | grep ssh - - 输出将类似于： - - - 2564 ? S 0:23 /usr/sbin/sshd - 3092 ? S 0:00 /usr/bin/ssh-agent /etc/X11/xinit/Xclients - 8032 pts/0 S 0:00 ssh user@host.example.com - 8032 pts/1 S 0:00 ssh root@backup.example.com - - - - 关于 screen 标记，请参考 。 - - - - - - 图表和图象 - - images - - - 图表 - 创建 - - 待编辑 - - diff --git a/docs-style-zh_CN.xml b/docs-style-zh_CN.xml deleted file mode 100644 index 14e7228..0000000 --- a/docs-style-zh_CN.xml +++ /dev/null @@ -1,1047 +0,0 @@ - - - 写作风格 - 撰写完善的技术文档不仅仅指展示命令行和指令集。好文档应当容易阅读、理解、翻译，表达准确的概念间的逻辑关系。好文档也可以用 不应当做的 事情来定义。您的文档应当避免： - - - 冗长 - - - 多余的，不加解释的行话 - - - 语法或拼写错误 - - - 对个人经历的引证 - - - 可能触犯或迷惑用户的评论 - - - 这一章包含了 &FED; 文档写作风格的规则和准则。准则与规则不同，即使违反了准则，如果您的文章更加易于理解，那么没有关系。尽量遵循准则，总是遵循规则。如果没有明确表明，一个建议就是一个准则。 -
- 为何写作风格很重要 - 优秀的写作不是天生的。它是一种技术，即使专业的作者，甚至有名的作家，也必须时常练习。 写作风格style 是将优秀的作品与平直的描述区分开的特性。 - 优秀的作品有多种形式。对于诗歌和散文，优秀的作品不会遵循一定的语法、句法或拼写规则。一个著名的例子是 James Joyce 的小说 Ulysses 中的 Episode 18, "Penelope," http://www.online-literature.com/james_joyce/ulysses/18/。请注意这个例子包含一些成人内容，因此不适于所有用户。。那里，Joyce 使用长串的词汇，不加标点，来摹拟角色的内心意识。虽然违反了语法和句法的基本规则，Joyce 描绘了叙述者无组织却又松散联系的思考方式。 - 技术文档却必须遵循这些规则。文档与标准语法偏差越大，读者就会觉得越难理解。例如，读者也许并不以文档语言为母语，或者正在阅读译本。这时，如果作者使用方言、习语或者行话，读者和译者会很容易被迷惑。下面的例子比较了表达同样含义的不同做法： - - 不正确的风格 - - So you made the changes I showed you in the last section. What's the next thing you should do? Just pop your thumb drive onto your system and read the messages log. When you see "USB device found," then Bob's your uncle. - - - 正确的风格 - - After you complete the configuration changes above, attach the USB removable media to your system. Use the dmesg command to examine the kernel message log. The message USB device - found indicates that your device was installed successfully. - - 第一个例子是更口语化的英语，它不适于正式的文档。第二个例子更加正式，但是无论是对英语用户还是译者，它都更容易理解。 - 遵守写作风格规则和准则，可以使读者阅读大量文档时更轻松。一致的风格有助于增强文档的专业性和价值认同。另一方面，忽略标点或语法错误将使读者对文档产生抵触。读者会认为基本正确的一篇文档不够权威，因为它写得很差。读者不必为理解作者的语言而头疼时才会放松下来。 - 这一章不可能包含足够的内容，使每个读过的人变成一个好作者。一些专门讲述写作风格的手册可能会有几百页。这一章为中级作者理解技术文档的写作风格提供了足够的准则。 - 如果您不是有经验的作者，无论技术文档还是其他，您还可以从其他资源中学到很多。下面的列表仍不够完善，但是提供了一个起点： - - - - The Elements of Style, 作者 William Strunk. 在线阅读: http://bartleby.com/141/ - - - - - The Chicago Manual of Style, 作者 the University of Chicago Press. 在线阅读: http://www.chicagomanualofstyle.org/ - - - - Paradigm Online Writing Assistant, 维护者 Chuck Guilford, Ph.D. 在线阅读: http://www.powa.org/ - - - 很多自由软件的文档计划有自己的文档风格准则。实际上，这一章很多内容来自 GNOME Documentation Style Guidelines (GDSG)。您可以看到本来的 GDSG，位置是 http://developer.gnome.org/documents/style-guide/。 -
-
- 技术文档的基本概念 - - 参考书目信息 - 这一节来自 GDSG。 - - - 这一章提供了写作技术文档的简要介绍。 -
- 写作风格一般要求 - &FP; 技术文档写作在一般要求的基础上，有特殊的约束。好的 &FED; 技术文档应当有下列特点： - - - 完备 - - 描述一个产品的全部功能。不可忽略个人认为对用户没有用处的功能。 - - - - 一致 - - - - 描述看到的内容。不要描述想要看到的内容。将信息以用户切身经历的顺序表达出来。 - - - - 清楚 - - 阅读 The Elements of Style (http://www.bartleby.com/141/) 来撰写清楚的文档。 - - - - - - 连贯 - - 在文档中使用约定俗成的词汇。如果其他作者在撰写相关的文档，那么使用相同的词汇。 - - - - 简明 - - 写作时多检视作品，问问自己哪些可以删减。请参考 。 - - - -
-
- 原则 - 这一节包含了一些基本的风格准则。本章的后续小节将展开详述这些准则。 - - - 原则一：简短 - - - - 将每句话限制到 25 个词以下。 - - - 将每步过程限制到 23 个词以下。 - - - - 不正确：过长 - Under normal operating conditions, the kernel does not always immediately write file data to the disks, storing it in a memory buffer and then periodically writing to the disks to speed up operations. - - - 正确：短句 - Normally, the kernel stores the data in memory prior to periodically writing the data to the disk. - - - - - 原则二：有条理 - - - - 每段讲述一个主题。 - - - 每句话表达一个意思。 - - - 每步操作只包含一个动作。 - - - - 不正确：没有条理 - The Workspace Switcher applet helps you navigate all of the virtual desktops available on your system. The X Window system, working in hand with a piece of software called a window manager, allows you to create more than one virtual desktop, known as workspaces, to organize your work, with different applications running in each workspace. The Workspace Switcher applet is a navigational tool to get around the various workspaces, providing a miniature road map in the GNOME panel showing all your workspaces and allowing you to switch easily between them. - - - 正确：有条理 - Use the Workspace Switcher to add new workspaces to the GNOME Desktop. You can run different applications in each workspace. The Workspace Switcher applet provides a miniature map that shows all of your workspaces. You can use the Workspace Switcher applet to switch between workspaces. - - - 在撰写前规划段落的顺序。决定在每段应当涵盖的主题。 - - - - - 原则三：使用指示 - - 使用例子来演示如何操作。提供指示，而不是描述。 - - 不正确：描述而不指示 - There is a text box that you can use to find out the definition of a word. - - - 正确：指示用法 - To request a definition of a word, type the word in the text box, then select Lookup. - - - 不要过于教条。有时您需要解释，以说明那些范例。 - - - - - 原则四：客观 - - 以中立的语气写作。 - - 不正确：偏倚一方 - The applet is a handy little screen grabber. - - - 正确：客观陈述 - Use the applet to take screenshots. - - - - -
-
- 语气 - 不合适的语气会妨碍读者获取信息。中立的，不带个人好恶选择的语气可以促进读者的理解。中立的语气使较大的文档项目中的作者可以并行写作。另外，新的作者可以随时加入。中立的语气可以在系列文档之间实现一致，便于用户获得信息。要达到共同的中立的语气，最好的办法是采用下列原则： - - - 避免幽默 - - 幽默使注意力从您的信息中移开。幽默也使文档难以翻译。保持直白。 - - - - 避免个人好恶选择 - - 无论您认为某个功能是否好坏都不重要。将功能展示给用户，包含如何使用这些功能的指示。保持准确。 - - - - 避免口语 - - 口语难以翻译，通常是与文化相关的。保持中立。 - - - - 避免一时的论断 - - 一个论断在今天被认同，在明天就可能被推翻。保持技术化。 - - - - 避免展望将来 - - 关于某个产品的将来，这不属于技术文档。只撰写您现在看到的东西。要实际。 - - - -
-
- 面向正确的用户 - 您对文档的结构和内容的定夺应当基于对读者的理解。考虑读者如何获取文档，需要哪些信息，曾经的经验等等。通常，您需要创建适合不同群体的文档。下面几节包含了您需要考虑的与读者相关的主题。 -
-
- 用户的动机 - 不要浪费想在文档中获取信息的读者的时间。用户阅读技术文档不是为了取乐。用户通常带有特定的问题。您需要对这些问题作出明确的回答。 -
-
- 新用户 - &FC; 的新用户遇到不熟悉的应用程序或功能时，通常会查阅在线教程。每个教程应当包含足够的介绍信息，告诉新用户如何使用相关的功能。每个教程还应当包含足够的使用说明，告诉用户他们可以用这个命令或功能作出的种种动作。使这些说明面向任务。在教程中不要描述 GUI 屏幕、对话框和对话框元素，除非某个特性影响了您的说明。 -
-
- 有经验的用户 - 有经验的用户通常将文档作为参考。文档需要完备，组织合理，如果是打印的方式，还需要索引。 -
-
- 不要触犯读者 - 为避免触犯读者，文档应遵循下列准则： - - - 避免内部用语 - - 内部用语包括行话和计算机社群中常见的缩写风气。例如，使用docs 而不是 documentation。一个词如果满足下面的条件，就是一句行话： - - - 这个词没有包含在 &FED; Jargon Buster (http://fedora.redhat.com/docs/jargon-buster/) 中。 - - - 这个词没有包含在 American Heritage Dictionary (http://www.bartleby.com/61/ ) 中。 - - - 这个词没有出现在您撰写的文档的词汇表中。 - - - 这个词也没有在您撰写的文档中定义。 - - - - - - 避免性别相关的语言 - - 不要出现代词 他的/她的 或 他/她。在指令中不必区分性别。 - - - - 避免特定文化的语言 - - 如果您的范例只能让您周围方圆百里的人看懂，那么它没有意义。 - - - - 不要用高人一等的口气 - - 如果文档中说，一个动作很容易或很快，而实际上用户无法完成，那没有比这更能让读者郁闷的了。不要评价和判断动作。 - - - - 准则的其他部分是对可能造成触犯的语气和语言用法的详细说明。 -
-
-
- 语法和用法准则 - - 参考书目信息 - 这一节部分来自 GDSG，部分来自 The Elements of Style，为二十一世纪的技术文档作者进行了更新。 - - - 这一节包含了字母序排列的语法和用法准则，用于 &FED; 文档。很多准则只适用于英语，请参考 American Heritage Dictionary (http://www.bartleby.com/61/) 和 Chicago Manual of Style (http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html)。 - - - 缩写 - - 词或短语的简写形式，可以代替原来的词使用，例如 Dr., a.m., p.m. 等等。在使用缩写时，遵循下列规则： - - - 避免创造新的缩写。不熟悉的缩写造成混淆，无法表明一个概念。 - - - 不要解释或展开众所周知的缩写。 - - - 不要在文档的词汇表中包含众所周知的缩写。 - - - 对于短语的缩写，例如 i.e. ("in other words", 换句话说) 和 e.g. ("for example", 例如)，不要使用缩写。拼写出整个短语。 - - - - 形容词 - - 小心使用形容词。在必须使用形容词来区分对象时再用。无论合适，检查是否可以把形容词去掉。 - - - - 首字母组合词 - - 用来表达一个由多个词组成的概念。通常，首字母组合词是这样构造的： - - - From the first letters of each word in a compound term, for example Table of Contents (TOC). - - - From recognizable parts of a compound term, such as GNU Object Model Environment (GNOME). - - - 在使用首字母组合词的时候，遵循下列规则： - - - 在第一次使用时，拼写完整的名称，在括号中包含组合词。 - - - 不要拼写出众所周知的首字母组合，除非您认为这对读者有用。 - - - 不要创建新的首字母组合。不熟悉的组合将造成混淆，无法表达清楚。 - - - 用大写表示，除非必须用小写。 - - - 在文档的词汇表中包含首字母组合和全称。 - - - - - - 副词 - - 小心使用副词。在必须用副词修饰组件的功能时再用。无论合适，检测是否可以去掉副词。经典的冗余副词包括 容易地，简单地 和 迅速地。 - - - - 拟人 - - - - 不要让应用程序软件充满情绪、欲望或意见。 - - - 不要让应用程序软件产生位置、维度的感觉。用户不会 "处在" 一个文本编辑器里。 - - - - - - 冠词 - - 不要在下列对象前面使用定冠词 the： - - - 文章标题 - - - 段的标题 - - - 标题 - - - 图象说明 - - - 表格说明 - - - 列表 - - - - - - 撇号 - - 尽可能不要使用撇号 - - - 不要用撇号来表达从属和拥有的关系 - - - 不要用撇号来表达缩写 - - - 不要用撇号来表达复数 - - - - 不正确的撇号 - - - the Main Menu'sHelp option - - - don't use the default option - - - several SCSI disk's - - - - - 正确：不使用撇号 - - - the Help option on the Main Menu - - - do not use the default option - - - several SCSI disks - - - - - - - 方括号 - - - - 不要使用方括号 [就像这样] 替换圆括号 (就像这样) - - - 使用方括号表达可选的命令行参数 - - - 不要使用尖括号表达文本中的变量，应使用 replaceable 标记。标记用法请参考 。 - - - - - - 大写 - - 下列情况下大写： - - - 首字母缩写中的所有字母，除非是众所周知的特例 - - - 列表中第一个词的第一个字母 - - - 顺序列表中第一个词的第一个字母 - - - 按键名称的第一个字母，例如 Shift - - - 句子的第一个字母 - - 命令名 - 避免在句首使用命令名或应用程序名称，如果它们的首字母是小写的话。 - - - - 冒号后面完整句子的首字母 - - - 下列情况下不要大写： - - - 组合的名词，后面是缩写或首字母组合 - - - 如果要强调一些内容 - - - 变量名 - - - 冒号后面，不完整句子的首字母 - - - - - - 标题 - - 对于标题，以及图象和表格的说明，使用相同的规则。不要在标题最后加上句号。 - - - - 冒号 - - 在下列情况下，使用冒号： - - - 引入列表 - - - 在解释的前面 - - - 在介绍之后 - - - 下列情况下，不要使用冒号： - - - 要引入图象或表格 - - - 介绍标题 - - - 介绍一个过程之后 - - - - - - 表栏标题 - - 使用与标题相同的规则 - - - - 逗号 - - 下列情况下，使用逗号： - - - 区分系列中的对象 - - - 区分句子的部分 - - - 区分非限制性的短语 - - - 与破折号类似，表达同位语 - - - 在 例如， 和类似的表达中 - - - 下列情况下，不要使用逗号： - - - 一系列形容词修饰一个对象时 - - - 两个短的独立子句间 - - - - - - 命令 - - 不要将命令作为动词。 - - - - 缩写 - - 不要使用缩写，类似 can't, don't, 或 isn't。 - - - - 破折号 - - 不要使用破折号或连接号。使用分段或冒号，如果是介绍性文字的话。如果有很多内容要介绍，那么使用一个列表。 - - - - 省略号 - - 下列情况下，使用省略号： - - - 要表示忽略了句子的一部分 - - - 要表示引用文本的间断 - - - - - - 分数 - - 使用分数时，遵循这些规则： - - - 在表格中，以及度量单位中，使用分数的数字形式，在正文中使用文本形式。 - - - 数字和相连的分数间添加空格，以防混淆。例如：1 1/2 而不是 11/2。 - - - 如果分数用作复合的修饰，在分数和度量单位间添加连字符。 - - - - - - 性别 - - 请参考 。 - - - - 语法 - - 标准的英语语法规则，请参考 Chicago Manual of Style ( http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html)。 - - - - 标题 - - 在标题中使用下面的大写规则： - - - 第一个词的首字母大写 - - - 名词，形容词和动词的首字母大写 - - - 连词，冠词和少于四个字母的介词都应小写 - - - 四个字母的介词或更多时首字母大写 - - - 四个字母的连词或更多时大写 - - - - - - - - 连字符 - - 下列情况下，使用连字符： - - - 组合修饰中的数字 - - - 避免混淆 - - - 在标准的前缀和后缀中。请参考 American Heritage Dictionary (http://www.bartleby.com/61/)。 - - - 在拼写的分数中 - - - 在由两个或多个单词构成的变量名中，类似 directory-name。注意： filename 是特例。 - - - 下列情况下，不要使用连字符： - - - 对于行话 - - - 对于动词 - - - 以 ly 结尾的副词 - - - 数字作为单一修饰时 - - - - American Heritage Dictionary (http://www.bartleby.com/61/) 列为不需连字符的单词，以及有共同前缀的词 - - - 商标 - - - - - - 拉丁文名称 - - 不要使用拉丁文名称。使用相应的英文名称。 - - - - 像 - - 不要使用 像 来表达等价或相似。 - - - - 列表 - - 使用以冒号结尾的完整的句子引入列表。 - - - - 数字 - - 下列情况下，拼写出数字： - - - 从 0 到 9 的数字，除非数字是测度的一部分 - - - 估计 - - - 极端情况，类似 百万，但要在前面加上一个数字。 - - - 出现在句子开头的数字 - - - 后面紧接一个数的数字。例如：两个 10 MB 的文件 - - - - - - 数字形式 - - 下列情况下，使用数字： - - - 数字 10 或更大 - - - 负数 - - - 大多数分数 - - - 百分数 - - - 小数 - - - 测度 - - - 小于一秒的时间单位 - - - 对位和字节的引用 - - - - - - 圆括号 - - 下列情况下，使用圆括号： - - - 要包含第一次出现的名称的缩写 - - - 在手册页的引用中，指明章节号 - - - - - - 句点 - - 下列情况下，使用句号： - - - 结束句子 - - - 文件和目录名中 - - - 可能被误认为单词的缩写中，类似 a.m. 和 U.S. - - - - - - 标点 - - 使用标准的英语标点规则。请参考 Chicago Manual of Style (http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html)。 - - - - 数字中的标点 - - 不要在四位的数字中使用逗号。如果超过四位，那么使用逗号。 - - - - 引号 - - 使用引号来表示内容是不变地从其他来源复制的。不要使用引号来区分不合适的用词。如果用词不合适，换一个别的。如果必须用这个词，就在词汇表中解释它，使这种用法变得合理。 - - - - See v. Refer to - - 向用户提供参考资源时，使用 "refer to" 而不是 "see"，使用 "refer also to" 而不是 "see also"。这样可以与索引用到的 see 和 seealso 标记区分开。 这些标记用于在索引中创建特殊的链接。为了在文档中保持一致，我们保留关键字 "see" 和 "see also" 用作超链接的索引引用，使用 "refer to" 和 "refer also to" 表达非超链接的，非索引的引用。 - - - - 分号 - - 不要使用分号。 - - - - 斜线 - - 除了用作文件名的一部分之外，不要使用斜线 "/"。不能包含 and/or 这样的内容，应该换成其中任何一个。 - - - - 拼写 - - 使用标准的英语拼写规则，请参考 American Heritage Dictionary (http://www.bartleby.com/61/)。 - - - - 书名 - - 对于文档的名称，使用与标题相同的规则。 - - - - 单位 - - 使用单位时，遵循下列规则： - - - 使用标准的单位缩写，不要自行创造缩写。 - - - 请参考 IEEE Standard Dictionary of Electrical and Electronics Terms。 - - - 在缩写的可能被误解为单词的单位中使用句点。 - - - 大多数标准的缩写单位都同时适于单数和复数。 - - - 在数字和单位之间加上空格。 - - - - - -
-
- 行文技巧 - - 本节包含了一些技巧提示，来自 &FDP; 作者们曾遇到的情况。您应理解运用它们，来改善自己的文档。&FDP; 作者乐于接受新的范例。 -
- 主动语态 - 总是使用主动语态，除非这样很别扭。文档告诉用户如何完成一项任务，应当给出清楚简明的指令。避免使用"必须", "需要"之类的词。这些词在文档中是多余的，因为读者期望看到您给出必要的步骤来完成任务。同样，避免使用"可能," "也许"等等，表示您对问题不很确定的词。您的文档应当权威地描述一个主题。读者不应担心按照文档做会有莫名奇妙的效果。 - - 不正确：被动语态 - 命令 yum update 必须被运行。 - 您也许想运行 yum update 命令。 - - - 正确：主动语态 - 运行 yum update 命令。 - -
-
- 一般现在时态 - 以一般现在时态写作。最好的经验，是不需用 "将要" 来描述用户将要做或看到的内容。它们没有意义，并可能混淆翻译者。它们也通常与被动语态有关，请参考 。 - - 不正确：将来时态 - 应用程序将要显示目标文件的列表。 - 目标文件的列表将要被应用程序显示出来。 - - - 正确：一般现在时态 - 应用程序显示目标文件的列表。 - -
-
- 叙述的语气 - 不要用第一人称"我" "我们" 来引用作者自己 (无论是否包含读者)，&FDP;，&FED; 社群或任何群体。不要用第三人称指代用户 ("他" "她" 或 "他或她") 或者 "某人"。使用第二人称 "您" 来指代读者是可以的。 - - 不正确：第一或第三人称 - 正如上文所述，我通常在配置 Samba 服务器之前运行 up2date。 - 如果用户需要备份他的或她的文件，他或她应当使用 tar 或 cpio 命令。 - - - 正确：第二人称，或不使用代词 - 配置 Samba 服务器之前，请参考关于 up2date 的小节。 - 如果需要，用户可以使用 tar 或 cpio 命令来备份文件。 - -
-
- 否定的用词 - 避免说不，因为它使教程显得武断。可以使用"避免"来代替。注意否定的词通常使用缩写，例如 don't 或 can't。请参考 。 -
-
- 不确定 - 避免过度使用 "典型的"，"通常地"，"大多数时候"，"许多"等诸如此类的词。 -
-
- 多余的内容 - 避免涉及多余的内容，例如如何更新 &FC; 系统。这些关键的主题在其他教程中已有讲述。作者们经常违反这个准则，因为觉得自己的教程不够长。但是，不要偏离您的主题。如果其他教程可以完整的覆盖那些主题，那么指引读者阅读那些文档。 -
-
- 自行评估价值 - 避免类似 "最重要的是应该做 XYZ" 的表述。如果这个过程很重要，读者一定希望在您的文档中看到。反过来说，如果您的文档中出现了某个过程，作者一定会觉得那很重要，尤其是当这个过程占用了整整一节的时候。其实只要说 "做 XYZ"，然后详细说明就可以了。如果整整一节都是对如何做 XYZ 的说明，就干脆不要说这句话。请参考 。 -
-
- 明确的语言 - 对于用户应当做出的动作，使用明确的词汇。不要让读者 "去" 选择，或者让读者在菜单里 "找"。 - - 不正确：不明确的用词 - - - 转到 Main Menu -> Foobar - - - 找到标记 Search 的选项 - - - - - 正确：明确的用词 - - - 在 Main Menu 菜单中，选择 Foobar - - - 选择 Search 选项。 - - - - - 不要区别对待非图形界面用户 - 如果您的文档是关于纯图形界面程序的，那么可以随意使用 "点击"。如果应用程序有字符界面，那么可以使用 "选择"，像上面那样。 - -
-
- DocBook 技巧 - 这一节包含关于如何在文档中更有效地使用 DocBook 标记的技巧。 -
- 创建提示 - 避免过分使用提示。在提示中只包含最重要的内容，使提示尽可能短。将用来解释的背景说明移到提示之外。使用简短的描述性的标题。标题的大小写规则与正文标题一致。 - - 不正确：过长的提示 - - - 使用 <command>sfdisk</command> 检测输入 - - sfdisk 命令接受一个脚本文件作为标准输入，来设置硬盘的分区。sfdisk 有些情况下拒绝一个有错的输入文件。在另一些情况下，它将无保留的执行输入，在硬盘上写入错误的分区。在写入磁盘前，总是用 sfdisk -n 命令检测输入文件。 - - - - - 正确：简短的提示 - - sfdisk 命令接受一个脚本文件作为标准输入，来设置硬盘的分区。sfdisk 有些情况下拒绝一个有错的输入文件。在另一些情况下，它将无保留的执行输入，在硬盘上写入错误的分区。检测输入在写入磁盘前，总是用 sfdisk -n 命令检测输入文件。 - - 避免在章节或提示的标题中使用标点，除非必须使用逗号。在标题中包含与提示相关的内容，例如 "需要重启"，而不是简单地使用提示类型作为标题 ("警告")。 - 提示的标题应使用与正文标题相同的大小写规则。 -
-
- - <sgmltag class="starttag">replaceable</sgmltag> 标记 - 如果您的文档表述了作为约定的一个特定的值，那么不要在文中或示例中使用 replaceable 标记。 -
-
- XML 实体 - 使用 &FDP; 提供的实体。这些实体可以在 fedora-docs 的 common/ 目录找到。(请参考 。) 例如，不要使用缩写 "FC2"，应当使用预定义的实体 "&FC; &FCVER;"，这样将生成文本 "&FC; &FCVER;"。 -
-
-
- diff --git a/docs-tutorial-zh_CN.xml b/docs-tutorial-zh_CN.xml deleted file mode 100644 index a24e3bc..0000000 --- a/docs-tutorial-zh_CN.xml +++ /dev/null @@ -1,72 +0,0 @@ - - - 文档的布局 - 在本章您将看到 &PROJECT; 文档中，主控文件的示例。这个示例与 Docs Project 处理 DocBook XML 的方式相关。主控文件包含文档的主要结构，以及到定义公共实体的文件的链接，还包括定义文档版本和日期的实体。 - - 主控文件 - 下面是一个简单的主控文件 - - -<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - -<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../common/fedora-entities-en.xml"> -%FEDORA-ENTITIES-EN; - -<!ENTITY VERSION "0.1"> <!-- change version of tutorial here --> - -<!ENTITY DOCID "example-tutorial-&VERSION; (2003-07-07)"> <!-- change last modified date here --> - -<!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice-en.xml"> - - -]> - -<article id="example-tutorial" lang="en"> - <articleinfo> - <title>Example Tutorial</title> - <copyright> - <year>2003</year> - <holder>&FORMAL-RHI;</holder> - <holder>Tammy Fox</holder> - </copyright> - <authorgroup> - <author> - <surname>Fox</surname> - <firstname>Tammy</firstname> - </author> - </authorgroup> - &LEGALNOTICE; - </articleinfo> - - <section id="some-section"> - <title>Some Section</title> - - <para> - This is an example section. You can also use sect1, sect2, etc. - </para> - - <warning> - <title>Warning</title> - <para> - Example of an admonition. - </para> - </warning> - - </section> - -<index id="generated-index"></index> -</article> - - - - - 包含许可信息 - - 文档版式 - 许可 - - 所有 &PROJECT; 手册 必须 包含文件 legalnotice.xml。这个文件包含了 GNU Free Documentation License (FDL) 的文本。 - 示例主控文件显示了如何包含它们。 - - diff --git a/docs-vim-zh_CN.xml b/docs-vim-zh_CN.xml deleted file mode 100644 index a33623f..0000000 --- a/docs-vim-zh_CN.xml +++ /dev/null @@ -1,87 +0,0 @@ - - - VIM 与 DocBook - - VIM - - VIM 有很多特性，有助于撰写类似 DocBook 的 XML 文档，包括语法高亮和可定制的按键绑定。另外，还可以用外部程序辅助 VIM 完成拼写检查等操作。本章假定您已知悉 VIM 一般用法；如果您要学习一般用法，执行 vimtutor 或在 VIM 中执行 :help tutor。 - - 设置 <filename>.vimrc</filename> 文件 - - VIM - 配置文件 - - 下面是一个示例 .vimrc 文件，打开了一些 VIM 特性，便于编辑类似 DocBook 的 SGML 或 XML 文档： -" 关闭 vi 兼容特性，类似有限的撤销 -set nocompatible -" 基于文件扩展名的语法高亮 -syntax on -" 在 80 个字符后面自动插入新行 -set textwidth=80 -" 自动缩进 -set autoindent -" 使用 % 匹配 SGML 标记 -source $VIMRUNTIME/macros/matchit.vim - - - 一些特性需要安装 vim-enhanced。如果您使用的是 vim-minimal，或者是旧版本的 VIM，可能不包含 $VIMRUNTIME/macros/matchit.vim 文件，那么可以在 Vim.org 下载 matchit.zip 并加载。 - - - - VIM 中的按键映射 - VIM 可以使创建 DocBook 文档更加快捷，只要将经常使用的标记 (或任何词汇短语) 定义为快捷键。默认情况下，键盘映射以反斜线 (\) 开始，但是也可以用命令定义，类似 let mapleader = - ","。有两种方式来使用下面的例子；您可以将它写在 .vimrc 文件中，或者将它保存为单独的文件，并在 .vimrc 文件中以 source 命令加载。e />:nohlsearcha - -" common tags that start a new text block -imappa O -imaps1 joO -imappl O0i -imapcp O0i - -" common tags that are placed inline -" use F>a -imapen F>a -imapfi F>a -imaplt F>a -imapre F>a -imapui F>a -imapul F>a -imapsi F>a -imapus F>a -imapsy F>a -imapcm F>a -" entities -imap > > -imap < < -]]> - 不幸的是，这不是所有 DocBook 命令的完整集合，因此您需要自行定义，或定制 范例中的定义。 - - - 其他 VIM 资源 - 其他 VIM 相关的资源可以在这里找到： - - - - 示例 sgml-vimrc，来自 Beginner's guide to Vi Improved (VIM) - - - - VIM Quick Reference Card - - - - - Vim 作为 XML 编辑器 - - - - - VIM REFERENCE MANUAL，包含在 vim-common 软件包中 — /usr/share/vim/<version>/doc/intro.txt，可以在 VIM 中执行 :help intro 查看。 - - - - diff --git a/docs-xml-tags-zh_CN.xml b/docs-xml-tags-zh_CN.xml deleted file mode 100644 index f8029f8..0000000 --- a/docs-xml-tags-zh_CN.xml +++ /dev/null @@ -1,1613 +0,0 @@ - - - DocBook XML 标记 - - XML - 标记 - XML 标记 - - 请仔细阅读这一章。这一章描述了 Docs Project 使用的标记。一些规则是 Docs Project 特定的。 - 如果这些标记运用合适，搜索文档时可以得到有意义的结果。这些标记帮助搜索引擎确认与搜索条件相关的信息。另一个好处是使 &PROJECT; 文档拥有相同的外观。(不过，由于输出格式不同，外观仍然会有一些区别。) - - XML - 标记概要 - - XML 中所有标记必须有开标记和闭标记。另外，按照惯例，章、节、图象、表格等必须有唯一的标识符，这样可以被正确标识，需要的话也可以交叉引用。 - 尽管 XML 可以处理很多文档形式，这里介绍的只是 article 一种。 - 本章只介绍 &PROJECT; 文档使用的标记，并不是所有可用的 DocBook XML 标记。完整的列表请参考： - - - http://www.docbook.org/tdg/en/html/docbook.html - - - - 标记和实体警告 - - xml 标记 - 警告 - - 应当牢记本节的警告。它们比有效的 DocBook XML 更加严格，这些规则的存在，是为了使 HTML 和 PDF 输出看起来更合适。 - - - 不要使用商标实体 - - 不要使用商标实体 &trade;, &copy;, 或 &reg; 因为它们无法为所有字符集产生 HTML 输出。这些实体产生的 HTML 输出定义在 DTD 中，无法通过样式表改变。 - 应当使用 trademark 标记以及相关类别，如下所示： - - - <trademark>其后是商标符号</trademark> - - - <trademark class="registered">其后是注册商标符号</trademark> - - - <trademark class="copyright">其后是版权符号</trademark> - - - - - - - para 标记中的内容 - - 除非是文本段落，否则不要使用 para。这个标记在 PDF 中，会使其间的文本包含多余的空白。 - 特别的，在下列标记之外不要使用 para (换句话说，不要把下列标记包含在 para 中)： - - - <screen> - - - <itemizedlist> - - - <orderedlist> - - - <variablelist> - - - <table> - - - - - - 包含在 para 标记中的 listitem - - 包含在 para 中的 listitem 标记 必须 紧挨 <para> 的开始标记，以避免 PDF 中的多余空白。 - - - - 包含在 screen 标记中的内容 - - XML 文件中，screen 标记 (<screen> 和 </screen>) 必须 靠左对齐，screen 包含的内容必须同样靠左对齐，除非有意留出空白。否则，多余的空白将出现在 HTML 中。 - - - - - - - <command>application</command> - - - XML 标记 - application - - application 是图形界面应用程序的名字。command 是一个可执行的程序，或者运行应用程序的命令。 - - <application> 和 </application> 标记使您可以引用应用程序。例如，下面的 XML： - - -要在 Linux 中访问 Web，您可以使用 -<application>Mozilla</application> 或 -<application>lynx</application>，如果您只需要字符界面的话。 - - - 产生如下输出： - 要在 Linux 中访问 Web，您可以使用 -Mozilla 或 -lynx，如果您只需要字符界面的话。 - - - - <command>chapter</command> - - - XML 标记 - chapter - - 一篇 DocBook 文档可以划分为多章，类似： - - - <chapter id="ch-sample"> - <title>示例章</title> - - <para>这是示例章，显示了用于创建章、节和小节的 XML 标记。</para> - - </chapter> - - - chapter 还可以进一步划分为节 (sect1, sect2, sect3 等等)。请参考 。 - - - - <command>citetitle</command> - - - XML 标记 - citetitle - - - <citetitle>标记用来格式化一个特别的引用 (引用标题可以自行输入，也可以使用实体实体是引用其他手册或教程的快捷方式。它可以在主控文档中定义，对于特定的文档集合，也可以在 DTD 引用的文件中定义。，如果在文档中已经定义的话)。 - 例如： - - -<citetitle>IG;</citetitle>. - - - 输出类似于 &IG;，因为 &IG; 是已定义的实体。 - - - - <command>command</command> - - - XML 标记 - command - - application 是图形界面应用程序的名字。command 是一个可执行的程序，或者运行应用程序的命令。任何命令行程序，或是只有字符界面的工具都应以 command 标记。 - 如果某些文本是一个命令，那就用 <command> 和 </command> 标记： - - -要在安装后改变键盘设置，切换为 root 并使用 <command>redhat-config-keyboard</command> 命令，或者在 root 提示符下输入 <command>setup</command>。 - - - 输出： - 要在安装后改变键盘设置，切换为 root 并使用 redhat-config-keyboard 命令，或者在 root 提示符下输入 setup。 - 另一个例子： - - -<command>MAILNOVIOLATIONS</command> — 如果设置为 <command>true</command>，这个选项使得 Tripwire 定时发送邮件报告，无论是否出现了越权操作。默认值是 <command>true</command>。 - - - 输出： - - MAILNOVIOLATIONS — 如果设置为 true，这个选项使得 Tripwire 定时发送邮件报告，无论是否出现了越权操作。默认值是 true。 - - 注意 本例中，选项值 (true) 被标记为 <command>。由于选项是出现在配置文件中的，(命令行选项应当使用 <option> 标记，)并且由于没有为配置文件选项定义什么标记，我们约定使用 <command> 标记配置文件中的选项。 - 名词也标记为 command，因为没有其他合适的标记： - - - 配置文件中的选项，类似 Apache 指令 - - - 守护进程名称 - - - - - - <command>computeroutput</command> - - - XML 标记 - computeroutput - - 要显示屏幕输出，使用这个标记： - - -<computeroutput>您是否要删除文件? y n</computeroutput> - - - 输出： - - 您是否要删除文件? y n - - - - - <command>emphasis</command> - - - XML 标记 - emphasis - - 要强调的内容，使用 <emphasis> 和 </emphasis> 标记。例如： - - -安装过程将 <emphasis>删除所有</emphasis> 硬盘上的 <emphasis>所有</emphasis> 已有 Linux 分区，非 Linux 分区不会被删除。 - - - 输出： - 安装过程将 删除所有 硬盘上的 所有 已有 Linux 分区，非 Linux 分区不会被删除。 - - - - <command>example</command> - - - XML 标记 - example - - - <example> 和 </example> 标记用来格式化某个文档中的文本，适于显示代码示例等。 - - <example> 标记应当有一个 ID 和标题： - - <example id="static-ip"> - <title>使用 DHCP 的静态 IP 地址</title> - -<screen width=60> -<computeroutput> -host apex { - option host-name "apex.example.com"; - hardware ethernet 00:A0:78:8E:9E:AA; - fixed-address 192.168.1.4; -} -<computeroutput> -</screen> - - </example> - - 输出： - - 使用 DHCP 的静态 IP 地址 - - -host apex { - option host-name "apex.example.com"; - hardware ethernet 00:A0:78:8E:9E:AA; - fixed-address 192.168.1.4; -} - - - - - - - <command>filename</command> - - - XML 标记 - filename - - - <filename> 和 </filename> 标记定义文件名和路径。由于目录是特殊的文件，因此也使用 filename 标记。例如： - -编辑 <filename>/home/smoore/sam.xml</filename> 文件，修改它或加注释。 - - 输出： - 编辑 /home/smoore/sam.xml 文件，修改它或加注释。 - 它们也用来标记 RPM 软件包名称。例如： - -要使用 <application>Keyboard Configuration Tool</application>，必须安装 <filename>system-config-keyboard</filename> 软件包。 - - 输出： - 要使用 Keyboard Configuration Tool，必须安装 redhat-config-keyboard 软件包。 - - 注意 - 目录名必须以斜线 (/) 结尾，以与文件名区分。 - - - - - <command>firstterm</command> - - - XML 标记 - firstterm - - - <firstterm> 和 </firstterm> 标记用来定义一个用户不熟悉，但将频繁出现的词。例如： - - -几乎所有现代操作系统都使用 <firstterm>disk -partitions</firstterm>(磁盘分区)，&FC; 也不例外。 - - - 输出： - 几乎所有现代操作系统都使用 disk partitions(磁盘分区)，&FC; 也不例外。 - - - - <command>footnote</command> - - - XML 标记 - footnote - - 如果您需要添加脚注，可以这样： - - -如果您想进行服务器级 -<footnote> -<para> -服务器级安装用于安装典型的服务器环境。注意，服务器级安装不会安装图形界面。 -</para> -</footnote> 安装，请参考 <citetitle>Installation Guide</citetitle>。 - - - 输出： - 如果您想进行服务器级 服务器级安装用于安装典型的服务器环境。注意，服务器级安装不会安装图形界面。 安装，请参考 Installation Guide。 - - - - <command>figure</command> - - - XML 标记 - figure - - - 注意 - 顺序很重要！EPS 文件 必须 首先声明。 - - 示例图象声明： - - -<figure id="fig-ksconfig-basic"> - <title>基本设置</title> - <mediaobject> - <imageobject> - <imagedata fileref="./figs/ksconfig/ksconfig-basic.eps" - format="EPS"/> - </imageobject> - <imageobject> - <imagedata fileref="./figs/ksconfig/ksconfig-basic.png" - format="PNG"/> - </imageobject> - <textobject> - <phrase> - 一些关于图象的文本描述 - </phrase> - </textobject> - </mediaobject> -</figure> - - - 下面列出了需要修改的内容： - -<figure id="fig-ksconfig-basic"> ==> id="" 可以修改 - -<title>基本设置</title> ==> 标题可以修改 - -fileref="./figs/ksconfig/ksconfig-basics.eps"> ==> .eps 位置可以修改 - -fileref="./figs/ksconfig/ksconfig-basics.png"> ==> .png 位置可以修改 - -<phrase>一些关于图象的文本描述</phrase> ==> "一些关于..." 可以修改 - 关于获取屏幕截图，请参考 。 - - - 图形用户界面标记 - - XML 标记 - GUI 标记 - - - - <command>guilabel</command> - - - XML 标记 - GUI 标记 - guilabel - - - XML 标记 - guilabel - - 使用 <guilabel> 和 </guilabel> 作为描述 GUI 时的默认标记，类似窗体名称或窗体标题。例如： - - -<guilabel>Authentication Configuration</guilabel> 屏幕指引您如何配置更安全的系统。 - - - 输出： - - Authentication Configuration 屏幕指引您如何配置更安全的系统。 - - - - <command>guibutton</command> - - - XML 标记 - GUI 标记 - guibutton - - - XML 标记 - guibutton - - 使用 <guibutton> 和 </guibutton> 标记表示屏幕或菜单中的按钮。例如： - - -选择 <guibutton>Activate on boot</guibutton> 按钮，配置 X 窗口系统自动启动。 - - - 输出： - 选择 Activate on boot 按钮，配置 X 窗口系统自动启动。 - - - - <command>guiicon</command> - - - XML 标记 - GUI 标记 - guiicon - - - XML 标记 - guiicon - - - <guiicon> 和 </guiicon> 标记用来表示面板或桌面图标。例如： - - -双击桌面上的 <guiicon>Start Here</guiicon> 图标。 - - - 输出： - 双击桌面上的 Start Here 图标。 - - - - <command>guimenu</command> 和 <command>guimenuitem</command> - - XML 标记 - GUI 标记 - guimenu - - - XML 标记 - guimenu - - - XML 标记 - GUI 标记 - guimenuitem - - - XML 标记 - guimenuitem - - 要表示一个菜单 (安装程序或控制面板中的菜单)，使用 <guimenu> 和 </guimenu> 标记。 - 要表示子菜单，使用 <guimenuitem> 和 </guimenuitem> 标记。(请注意示例中为了输出需要，插入了一些换行。)例如： - - -选择 <guimenu>Main Menu</guimenu> => - <guimenuitem>Programming</guimenuitem> => <guimenuitem>Emacs</guimenuitem> 来启动 -<application>Emacs</application> 编辑器。 - - - 输出： - 选择 Main Menu => Programming => Emacs 来启动 Emacs 编辑器。 - - - - - <command>keycap</command> - - - XML 标记 - keycap - - 要表示某个按键，应当使用 <keycap> 和 </keycap> 标记。按键会自动加上尖括号，因此不要在 XML 代码中再加一次。例如： - - -要作出选择，按下 <keycap>Enter</keycap> 键。 - - - 输出： - 要作出选择，按下 Enter 键。 - - - <command>menuchoice</command> - - - XML 标记 - menuchoice - - 通常，使用鼠标对于频繁的操作过于繁琐。因此，程序员在程序中设置了快捷键来简化使用。应当使用 shortcut 标记包含 keycap 标记，然后再整个包含在 menuchoice 标记中，来表示快捷键。例如： - - -打开菜单并选择： - <menuchoice> - <shortcut> - <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo> - </shortcut> - <guimenu><accel>F</accel>ile</guimenu> - <guimenuitem><accel>S</accel>ave</guimenuitem> - </menuchoice>. - - - 输出： - 打开菜单并选择：CtrlsFileSave. - - - - <command>keycombo</command> - - - XML 标记 - keycombo - - 要描述按键组合，使用 <keycombo> 和 </keycombo>, <keycap> 和 </keycap> 标记。例如： - - -要重启系统，按下 <keycombo> -<keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap> -</keycombo>. - - - 输出： - 要重启系统，按下 CtrlAltDel. - - - - 列表 - - 列表 - 创建 - - 您可以用 XML 创建多种列表。您可以创建无序的枚举，有序的编号列表，或是变量表 (先是一个词，然后是单独的一段话)。 - 还有一种列表适于表格，最后一种是用于定义词汇解释的列表。 - 下面各节描述了各种列表，以及如何创建。 - - - <command>itemizedlist</command> - - - XML 标记 - - itemizedlist - - - - XML 标记 - 列表 - itemizedlist - - - 列表 - - itemizedlist - - - - itemizedlist 适于向读者呈现重要的信息，而信息是无序的。它比 variablelist 更短，也简单一点。 - 要创建 itemizedlist (也称为枚举列表)，可以这样： - - 注意 下面列表中的文本是直接包含在 para 标记中的。如果您使用列表，不要用这个标记，否则列表中会包含多余空白，无法对齐。如果多个列表项是多行文本，空白会更加明显。HTML 版本不会像 PDF 版本那样明显。 - - -<itemizedlist> - <listitem> - <para>熟悉安装程序的界面</para> - </listitem> - - <listitem> - <para>开始安装程序</para> - </listitem> - - <listitem> - <para>选择安装方法</para> - </listitem> -</itemizedlist> - - - 输出： - - - 熟悉安装程序的界面 - - - 开始安装程序 - - - 选择安装方法 - - - - - - <command>orderedlist</command> - - - XML 标记 - - orderedlist - - - - 列表 - - orderedlist - - - - XML 标记 - 列表 - orderedlist - - - orderedlist 适于向读者显示必须以一定顺序出现的信息。orderedlist 用来向读者描述一步一步的场景转换很不错。 - 要创建 orderedlist (有序列表) 可以这样： - - 注意 下面列表中的文本是直接包含在 para 标记中的。如果您使用列表，不要用这个标记，否则列表中会包含多余空白，无法对齐。如果多个列表项是多行文本，空白会更加明显。HTML 版本不会像 PDF 版本那样明显。 - - -<orderedlist> - <listitem> - <para>在线 &mdash; http://www.redhat.com/support/errata; 提供 - 可以在线阅读的更正，您也可以下载光盘镜像。 - </para> - </listitem> - - <listitem> - <para>电子邮件 &mdash; 发送空白邮件到 errata@redhat.com, - 您将收到完整的包含安装程序和相关软件 (如果有的话) 的更正说明。 - 同时还包括软件更新以及光盘镜像的 URL。通过这些 URL 来下载 - 镜像。请注意：下载时使用二进制模式。</para> - </listitem> -</orderedlist> - - - 输出： - - - 在线 — http://www.redhat.com/support/errata; 提供可以在线阅读的更正，您也可以下载光盘镜像。 - - - 电子邮件 — 发送空白邮件到 errata@redhat.com, 您将收到完整的包含安装程序和相关软件 (如果有的话) 的更正说明。同时还包括软件更新以及的光盘镜像的 URL。通过这些 URL 来下载镜像。请注意：下载时使用二进制模式。 - - - - - - <command>variablelist</command> - - - XML 标记 - - variablelist - - - - XML 标记 - 列表 - variablelist - - - 列表 - - variablelist - - - - variablelist 适于表现一个词以及相关的解释和描述。 - 要创建 variablelist 可以这样： - - 注意 下面列表中的文本是直接包含在 para 标记中的。如果您使用列表，不要用这个标记，否则列表中会包含多余空白，无法对齐。如果多个列表项是多行文本，空白会更加明显。HTML 版本不会像 PDF 版本那样明显。 - - -<variablelist> - <varlistentry> - <term> 新的多介质安装过程 </term> - <listitem> - <para>由于安装程序越来越大，RedHat 开发了 - 可以处理多张 CD-ROM 介质的安装程序。</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>XFree 4.0 </term> - <listitem> - <para>X 窗口系统的配置从来没有如此简单。 - 从选择显示器及其设置，到显卡探测，以及测试您期望的 X 窗口设置， - Xconfigurator 可以搞定一切。</para> - </listitem> - </varlistentry> -</variablelist> - - - 输出： - - - 新的多介质安装过程 由于安装程序越来越大，RedHat 开发了可以处理多张 CD-ROM 介质的安装程序。 - - XFree 4.0 - - X 窗口系统的配置从来没有如此简单。从选择显示器及其设置，到显卡探测，以及测试您期望的 X 窗口设置，Xconfigurator 可以搞定一切。 - - - - - 警告 - - 不要 设置表格的 frame 属性，否则 PDF 生成会失败。 - - - - 在表格中创建列表，使用 <command>simplelist</command> - - XML 标记 - - simplelist - - - - XML 标记 - 列表 - simplelist - - - 列表 - - simplelist - - - - 表格 - 在表格中创建列表 - - simplelist - - - - simplelist 是无修饰的列表。simplelist 可以内联或按列对齐。 - 使用 simplelist 在表格内添加分离的文本段落。通常的列表，例如 itemizedlist，不能嵌入在表格内。 - XML 代码如下： - - - <table id="tb-hwinfo-hostbus"> - <title>主机总线适配器特性及配置要求</title> - - <tgroup cols="3"> - <colspec colnum="1" colname="HostBus" colwidth="33"/> - <colspec colnum="2" colname="Features" colwidth="34"/> - <colspec colnum="3" colname="Single" colwidth="33"/> - - <thead> - <row> - <entry>主机总线适配器</entry> - <entry>特性</entry> - <entry>Single-Initiator 配置</entry> - </row> - </thead> - - <tbody> - - <row> - <entry>Adaptec 2940U2W</entry> - - <entry><simplelist> - <member>Ultra2, wide, LVD.</member> - <member>HD68 external connector.</member> - <member>One channel, with two bus segments.</member> - <member>Set the onboard termination by using the BIOS - utility.</member> - <member>Onboard termination is disabled when the power is - off.</member> - </simplelist></entry> - - <entry><simplelist> - <member>Set the onboard termination to automatic (the - default).</member> - <member>Use the internal SCSI connector for private - (non-cluster) storage.</member> - </simplelist></entry> - </row> - - <row> - <entry>Qlogic QLA1080</entry> - - <entry><simplelist> - <member>Ultra2, wide, LVD</member> - <member>VHDCI external connector</member> - <member>One channel</member> - <member>Set the onboard termination by using the BIOS - utility.</member> - <member>Onboard termination is disabled when the power is off, - unless jumpers are used to enforce termination.</member> - </simplelist></entry> - - - <entry><simplelist> - <member>Set the onboard termination to - automatic (the default).</member> - <member>Use the internal SCSI connector for private - (non-cluster) storage.</member> - </simplelist></entry> - </row> - - </tbody> - </tgroup> - </table> - - - 输出： - - 主机总线适配器特性及配置要求 - - - - - - - 主机总线适配器 - 特性 - Single-Initiator 配置 - - - - - Adaptec 2940U2W - - - Ultra2, wide, LVD. - HD68 external connector. - One channel, with two bus segments. - Set the onboard termination by using the BIOS utility. - Onboard termination is disabled when the power is off. - - - - - Set the onboard termination to automatic (the default). - Use the internal SCSI connector for private (non-cluster) storage. - - - - - Qlogic QLA1080 - - - Ultra2, wide, LVD - VHDCI external connector - One channel - Set the onboard termination by using the BIOS utility. - Onboard termination is disabled when the power is off, unless jumpers are used to enforce termination. - - - - - Set the onboard termination to automatic (the default). - Use the internal SCSI connector for private (non-cluster) storage. - - - - - -
- - 注意 - 注意 simplelist 标记的用法。<entry> 和 <simplelist> 标记必须靠紧，否则将产生解析错误。 - - 每个要加入 simplelist 的段落或列表项应当包含在 <member> 标记中。 - - - - <command>glosslist</command> - - - XML 标记 - - glosslist - - - - XML 标记 - 列表 - glosslist - - - 列表 - - glosslist - - - 使用 glosslist 来创建词汇表和解释。 - XML 代码如下： - - - <glosslist> - <glossentry> - <glossterm>applet</glossterm> - <glossdef> - <para>一个小程序，通常是实用工具或简单程序。</para> - </glossdef> - </glossentry> - - <glossentry> - <glossterm>architecture</glossterm> - <glossdef> - <para>计算机或计算机系统中， - 组件的组织和整合的设计。</para> - </glossdef> - </glossentry> - - <glossentry> - <glossterm>archive</glossterm> - <glossdef> - <para>将文件传送到存储设备，以节省空间和/或 - 加以组织。</para> - </glossdef> - </glossentry> - </glosslist> - - - 输出： - - - applet - - 一个小程序，通常是实用工具或简单程序。 - - - - architecture - - 计算机或计算机系统中，组件的组织和整合的设计。 - - - - archive - - 将文件传送到存储设备，以节省空间和/或加以组织。 - - - - - - - - <command>option</command> - - - XML 标记 - option - - 如果您的命令需要选项或设置标志，使用 <option> 和 </option> 标记。 - - 注意 - <option> 标记只用于命令行选项，不用于配置文件。 - - 指定选项的 XML 代码如下： - - -例如，运行命令 <command>ls</command> 时可以指定选项 <option>-la</option>。 - - - 输出： - 例如，运行命令 ls 时可以指定选项 。 - - - 索引节点 - - 创建索引 - - - XML 标记 - 创建索引 - - 下面的命令序列展示了如何向文档中添加一个索引项的代码： - - -<indexterm> <-- 这是要在索引中添加的词汇 -<primary>foo</primary> <-- 表示 "foo" 是首要条目 -<secondary>bar</secondary> <-- "bar" 将列在 "foo" 条目之下 -</indexterm> <-- 关闭索引项 - - - - foo - bar - - - <seealso> 标记允许您引用另一个索引项或其他手册。应确保您指向的 <seealso> 引用有自己的节点。例如： - - 创建索引 - seealso 标记 - - - -<indexterm> -<primary>SWAK</primary> -<seealso>salutations</seealso> -</indexterm> - - -<indexterm> -<primary>salutations</primary> -</indexterm> - - - - SWAK - Salutations - - - Salutations - - - <see> 标记允许您引用一个完整的索引节点。例如： - - 创建索引 - see 标记 - - - -<indexterm> -<primary>Guinness</primary> -<see>beer</see> <-- "beer" 将被列在 "Guinness" 条目下，但是应确保所引用的 "beer" 有自己的索引节点。 -</indexterm> - -<indexterm> -<primary>beer</primary> -</indexterm> - - - - Guinness - Beer - - - Beer - - 要查看这里的索引节点的 HTML 输出，请参考文档最后的 generated-index.html 文件。 - 索引是如何生成的? 如果文档中包含 indexterm，并且开标记和闭标记出现在文档或文章的结束标记之前，就创建索引，因为样式表参数 generate.index 的默认值是真。 - - - - <command>para</command> - - - XML 标记 - para - - 对于任意一段，<para> 和 </para> 标记必须作为这一段的开始和结束。 - 不要在除了简单段落之外使用 para 标记。否则，文本内部会产生多余的空白。 - 在下列标记周围不要使用 <para> (换句话说，不要把下列标记放在 <para> 标记中)： - - - - <screen> - - - - - <itemizedlist> - - - - - <orderedlist> - - - - - <variablelist> - - - - - <table> - - - - - - - <command>part</command> - - - parts - - - XML 标记 - part - - 在主控文件中，可以将章划分为部，以表示逻辑分组。例如，在主控文件中，以 part 标签包含章的实体： - - -<part id="pt-foo"> - <partintro> - <para>一些文本，对这一部分的介绍</para> - &CHAPTER; - - &ANOTHER-CHAPTER; -</part> - - - 如果您创建了一个 part，应当对内容作一些介绍。例如： - - - <part id="pt-setup"> - <title>设置环境</title> - <partintro> - <para>本节讲述当您刚加入 Docs Group 时需要的信息。 - 您也许会再参考本节中，有关安装 &FC; 的信息。</para> - </partintro> - - - 在 HTML 输出中，会生成单独的 HTML 页面，包含这一部的编号、标题、介绍和目录。在 PDF 输出中，这些信息会出现在单独的一页上。 - - - - <command>prompt</command> - - - XML 标记 - prompt - - 要显示提示符，类似 root 提示符或 DOS 提示符，使用 <prompt> 和 </prompt> 标记。例如： - - -在 <prompt>LILO:</prompt> 启动提示符下，输入 linux 来启动到 Linux 分区。 - -在 <prompt>C:\></prompt> 提示符下，输入... - - - 输出： - 在 LILO: 启动提示符下，输入 linux 来启动到 Linux 分区。 - 在 C:\> 提示符下，输入... - - 注意 - 在显示计算机输出的范例时 (通常是在 screen 标记中)，不要包含提示符或命令 (除非命令或提示符是您意图显示的计算机输出)。 - - - - - <command>replaceable</command> - - - XML 标记 - replaceable - - 要创建可替换的文本，使用 <replaceable> 和 </replaceable> 标记包围您用作可变值的文本。 - 这个例子演示了在引用 RPM 文件时如何使用 replaceable 标记。 - -foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm - - 输出： - -foo-version-number.arch.rpm - - - - - <command>screen</command> - - - XML 标记 - screen - - - <screen> 标记用来格式化文档中的文本，适于用来添加代码示例，计算机输出等等。在 HTML 中，使用 Fedora CSS 文件，可以显示为灰色背景的方框。需要这种效果时，只要将开标记 <screen> 和闭标记 </screen> 包围在需要强调的文本前后。 - - 注意 - 使用 <screen> 标记时，必须设置所包含的所有内容，包括 <screen> 标记本身为左对齐。这样，在转化为 HTML 时，在灰色背景内部文字之前不会出现多余的空白。 - - - <screen> 标记可能包含其他内联标记，类似 <computeroutput>, <userinput>, 或 <replaceable> 等等。其他内联标记未作要求。<screen> 标记本身可以提供足够的上下文，尤其对于简单的范例或列举文件而言。考虑范例的上下文，如果内联标记有助于阅读，那么就使用它。 - 如果您使用内联标记，牢记 <screen> 标记中的换行会在任何输出中生成换行。将标记与内容 放在同一行。不要在 <screen> 的内容中过分使用标记。 - - <screen> 示例如下： - - <screen> -这是 screen 的示例。其中无须使用 &lt;para&gt; 标记。 -</screen> - - 输出： - -这是 screen 的示例。其中无须使用 <para> 标记。 - - - 在 <command>screen</command> 中使用内联标记 - 如果您在 <screen> 中使用内联标记，遵循下列准则以保持一致。如果 screen 的内容是配置文件的清单或程序的输出，使用 <computeroutput> 标记包含整个输出。如果用户应当在命令行照范例输入，或是配置文件，使用 <userinput> 标记。用简短的叙述性的话来区分输入和输出，如下所示： - - <para> - 输入下面的命令： - </para><screen><userinput>command -sw file1</userinput></screen><para> - 可以看到下列输出： - </para><screen><computeroutput>Completed, time = 0.12 sec</computeroutput></screen> - 输出： - 输入下面的命令： - - command -sw file1 - - 可以看到下列输出： - - Completed, time = 0.12 sec - - - 注意 - 在 screen 标记中显示一条命令或命令序列时，不要显示提示符。 - - 如果 <screen> 向读者显示如何修改文本的 一部分，可以将修改部分以内联的 <userinput> 标记。您可以在大块内联的 <computeroutput> 文本中使用 <userinput>。这时不要包含更多上下文，除非必须这么做。下面的示例演示了这些准则： - - <para> - 编辑 <filename>/etc/sysconfig/init</filename> 文件，如下所示： - </para><screen> -GRAPHICAL=<userinput>yes</userinput></screen> - 输出： - 编辑 /etc/sysconfig/init 文件，如下所示： - -GRAPHICAL=yes - 对于如何在 screen 标记中使用 replaceable 标记，请参考 。 - - - - section - - XML 标记 - 节 - - - 节 - - 在文章中 (或者在 chapter 中，如果是 DocBook XML book 样式的话，类似 &IG;)，可以细分为节和小节。<sect1> 总是最顶层的节。如果两个 section 级别相同，那么一个不能包含另一个 (section 2 可以包含在 section 1 里面，但是如果再创建新的 section 1，必须先关闭当前的 section 1)。大致的布局如下： - - -<sect1 id="s1-uniquename"> - <title>插入标题</title> - <para> - 内容文本。 - </para> - - - <sect2 id="s2-uniquename"> - <title>插入标题</title> - <para> - 内容文本。 - </para> - - <sect3 id="s3-uniquename"> - <title>插入标题</title> - <para> - 内容文本。 - </para> - - </sect3> - - </sect2> - -</sect1> - - - 在 DocBook article 样式中，如果您只需要一级 section，可以使用 section 标记。例如： - - -<section id="sn-uniquename"> - <title>插入标题</title> - <para> - 内容文本。 - </para> -</section> -<section id="sn-anothername"> - <title>插入标题</title> - <para> - 内容文本。 - </para> -</section> - - - - - - <command>table</command> - - - XML 标记 - table - - 下面是创建表格的范例。 - -<table id="tb-mockup-before-begin"> - 这在 XML 中声明了一个表格，ID 是 "tb-mockup-before-begin"。 - -<title>Available Features of GNOME and KDE</title> - -<tgroup cols="3"> - 这在 XML 中声明了一个表格，包含三列。 - -<colspec colnum="1" colname="Features" colwidth="3"/> - colspec 表示您向 XML 声明的表格列信息。 colnum="1" 表示您对第一列的设定。colname="Features" 表示本列的标题是 "Features"。colwidth="3" 指定列宽。这里有些机关：如果两列的列宽分别是 1 和 2，那么 1 占据的页宽就是 2 的一半。但是，如果您需要让第一列比第二列的一半稍微宽一点，那么就用一个更大的数值，例如指定列宽分别为 10 和 20，然后把 10 增加到 11 或 12，这样就比第二列的 20 的一半大一点了。如果没有给定任何值，默认就是 1。 - -<colspec colnum="2" colname="GNOME" colwidth="2"/> -<colspec colnum="3" colname="KDE" colwidth="2"/> - -<thead> - 包含一个或多个表格行。 - -<row> - 包含一个或多个表格单元。 - -<entry>Features</entry> - 表格单元元素，一列表格单元中的一个，定义了行内的列。 - -<entry>GNOME</entry> -<entry>KDE</entry> -</row> -</thead> - -<tbody> - 包含一个或多个表格行，作为表格的主体。 - -<row> -<entry>高度可定制</entry> -<entry>yes</entry> -<entry>yes</entry> -</row> -<row> -<entry>多种窗口管理器</entry> -<entry>yes</entry> -<entry>yes</entry> -</row> -<row> -<entry>互联网程序</entry> -<entry>yes </entry> -<entry>yes </entry> -</row> -</tbody> -</tgroup> -</table> - - - Available Features of GNOME and KDE - - - - - - - 特性 - GNOME - KDE - - - - - 高度可定制 - yes - yes - - - 多种窗口管理器 - yes - yes - - - 互联网程序 - yes - yes - - - -
- - 在表格中创建列表 - - XML 标记 - table - 表格中的列表 - - 在表格中创建列表比较困难，它要求严格的格式化以及一些 Emacs 无法完成的命令补全。 - 需要使用的标记是 <simplelist> 和 <member>。 - 下面是在表格中创建列表的例子。 - - -<table id="tb-hardware-powerswitch"> - <title>不间断电源硬件</title> - <tgroup cols="4"> - <colspec colnum="1" colname="Hardware" colwidth="2"/> - <colspec colnum="2" colname="Quantity" colwidth="2"/> - <colspec colnum="3" colname="Description" colwidth="6"/> - <colspec colnum="4" colname="Required" colwidth="2"/> - - <thead> - <row> - <entry>Hardware</entry> - <entry>Quantity</entry> - <entry>Description</entry> - <entry>Required</entry> - </row> - </thead> - - <tbody> - - <row> - <entry>Serial power switches</entry> - - <entry>Two</entry> - - <entry><simplelist> <member>Power switches enable each cluster system - to power-cycle the other cluster system. Note that clusters are - configured with either serial or network attached power switches and - not both.</member> - - <member>The following serial attached power switch has been - fully tested:</member> - - <member>RPS-10 (model M/HD in the US, and model M/EC in - Europe) </member> - - <member>Latent support is provided for the following serial - attached power switch. This switch has not yet been fully - tested:</member> - - <member>APC Serial On/Off Switch (partAP9211), <ulink - url="http://www.apc.com/">http://www.apc.com/</ulink></member> - </simplelist></entry> - - <entry>Strongly recommended for data integrity under all failure - conditions</entry> - - </row> - </tbody> - </tgroup> -</table> - - - - <simplelist> 标记必须紧挨 <entry> 标记。如果不这样，就无法成功解析。 - 上面的示例看起来象这样： - - 不间断电源硬件 - - - - - - - - Hardware - Quantity - 描述 - Required - - - - - Serial power switches - Two - - Power switches enable each cluster system to power-cycle the other cluster system. Note that clusters are configured with either serial or network attached power switches and not both.The following serial attached power switch has been fully tested:RPS-10 (model M/HD in the US, and model M/EC in Europe)Latent support is provided for the following serial attached power switch. This switch has not yet been fully tested:APC Serial On/Off Switch (partAP9211), http://www.apc.com/ - - Strongly recommended for data integrity under all failure conditions - - - -
- - - - - <command>trademark</command> - - - XML 标记 - - trademark - - - 不要使用商标实体 &trade;, &copy;, 或 &reg; 因为它们无法为所有字符集产生 HTML 输出。这些实体产生的 HTML 输出定义在 DTD 中，无法通过样式表改变。 - 应当使用 trademark 标记以及相关类别，如下所示： - - -<trademark>其后是商标符号</trademark> -<trademark class="registered">其后是注册商标符号</trademark> -<trademark class="copyright">其后是版权符号</trademark> - - - - - - <command>userinput</command> - - - XML 标记 - - userinput - - - 要显示用户将输入的内容，使用 userinput 标记。例如： - - -在提示符下，输入： - -<userinput>dd if=boot.img of=/dev/fd0 bs=1440k</userinput> - - - 输出： - 在提示符下，输入： - - dd if=boot.img of=/dev/fd0 bs=1440k - - - - - - <command>ulink</command> - - - XML 标记 - ulink - - 要在文本中创建 URL，如下： - - -在线 &mdash; <ulink url="http://www.redhat.com/support/errata/"> -http://www.redhat.com/support/errata/</ulink>; 提供可以在线阅读的更正，您也可以下载光盘镜像。 - - - 输出： - 在线 — http://www.redhat.com/support/errata/; 提供可以在线阅读的更正，您也可以下载光盘镜像。 - - 注意 - 如果 URL 不是以文件名结尾，必须以斜线结束 (/)，才是格式正确的 URL，例如 http://www.redhat.com/。 - - - - - <command>wordasword</command> - - - XML 标记 - wordasword - - <wordasword> 标记用来定义一个词只作为语法单位，不代表其他含义。 - 许多技术文档使用了有丰富意义的词汇。有时又需要用到不带技术意味的这个词。<wordasword> 标记这样的词，指示这个词应当简单地理解为一个词而不是其他东西。 - 使用这个标记不会帮助读者理解其中的意义差别；好文档应当做到这一点。实际上 <wordasword> 的价值在于全文搜索和索引工具可以用它来减少虚假结果。 - 例如： - - 要使用 <command>grep</command> 搜索单词 -<wordasword>linux</wordasword>，使用命令 -<command>grep linux</command>。 - - 输出： - 要使用 grep 搜索单词 linux，使用命令 grep linux。 - 这个例子中，"linux" 仅仅是一个单词。文档不是以 Linux 为主题，这个词也不为内容添加任何相关含义，可以替换为其他任何词。 - - - - <command>xref</command> - - - XML 标记 - xref - - 要引用手册中其他章节，使用 <xref> 标记。 - 它的输出是您向读者指引的章节的标题。例如： - - -关于主控文件，请参考 -<xref linkend="ch-tutorial"></xref> 和 <xref linkend="s1-tutorial-parent"></xref> - - - 输出： - 关于主控文件，请参考 和 。 - - diff --git a/documentation-guide-zh_CN.xml b/documentation-guide-zh_CN.xml deleted file mode 100644 index 49b5df7..0000000 --- a/documentation-guide-zh_CN.xml +++ /dev/null @@ -1,44 +0,0 @@ - - - -%FEDORA-ENTITIES-EN; - - - - - - - - - - - - - -]> - - - &FP; 文档撰写准则 - 版本 &VERSION; - - 2003,2004,2005 - &FORMAL-RHI; - Tammy Fox - Johnray Fuller - Sandra Moore - - - - Fox - Tammy - - - Fuller - Johnray - - - Moore - Sandra - - &LEGALNOTICE; &INTRODUCTION; &GETTINGFILES; &GUIDELINES; &EMACS; &EMACS-NXML; &VIM; &TAGS; &TUTORIAL; &STYLE; &CVS; &ACKNOWLEDGMENTS; diff --git a/po/zh_CN.po b/po/zh_CN.po new file mode 100644 index 0000000..7fbb4ee --- /dev/null +++ b/po/zh_CN.po @@ -0,0 +1,7465 @@ +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2007-03-11 17:30-0400\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"#-#-#-#-# acknowledgments.po (PACKAGE VERSION) #-#-#-#-#\n" +"#-#-#-#-# documentation-guide.po (PACKAGE VERSION) #-#-#-#-#\n" +"#-#-#-#-# emacs-nxml.po (PACKAGE VERSION) #-#-#-#-#\n" +"#-#-#-#-# emacs.po (PACKAGE VERSION) #-#-#-#-#\n" +"#-#-#-#-# getting-files.po (PACKAGE VERSION) #-#-#-#-#\n" +"#-#-#-#-# intro.po (PACKAGE VERSION) #-#-#-#-#\n" +"#-#-#-#-# style.po (PACKAGE VERSION) #-#-#-#-#\n" +"#-#-#-#-# tutorial.po (PACKAGE VERSION) #-#-#-#-#\n" +"#-#-#-#-# vim.po (PACKAGE VERSION) #-#-#-#-#\n" +"#-#-#-#-# xml-tags.po (PACKAGE VERSION) #-#-#-#-#\n" + +#: en_US/rpm-info.xml:20(rights) +msgid "OPL" +msgstr "" + +#: en_US/rpm-info.xml:21(version) +msgid "1.0" +msgstr "" + +#: en_US/rpm-info.xml:24(year) +msgid "2003" +msgstr "" + +#: en_US/rpm-info.xml:25(year) +msgid "2004" +msgstr "" + +#: en_US/rpm-info.xml:26(year) +msgid "2005" +msgstr "" + +#: en_US/rpm-info.xml:27(year) +msgid "2006" +msgstr "" + +#: en_US/rpm-info.xml:28(holder) +msgid "Red Hat, Inc." +msgstr "" + +#: en_US/rpm-info.xml:29(holder) +msgid "Tammy Fox" +msgstr "" + +#: en_US/rpm-info.xml:30(holder) +msgid "Johnray Fuller" +msgstr "" + +#: en_US/rpm-info.xml:31(holder) +msgid "Sandra Moore" +msgstr "" + +#: en_US/rpm-info.xml:32(holder) +msgid "Paul W. Frields" +msgstr "" + +#: en_US/rpm-info.xml:34(title) +msgid "Fedora Documentation Guide" +msgstr "" + +#: en_US/rpm-info.xml:35(desc) +msgid "Guidelines and procedures for producing documentation for Fedora" +msgstr "" + +#: en_US/rpm-info.xml:42(details) +msgid "Update to new build requirements" +msgstr "" + +#: en_US/xml-tags.xml:13(title) +msgid "DocBook XML Tags" +msgstr "DocBook XML 标记" + +#: en_US/xml-tags.xml:16(primary) en_US/xml-tags.xml:34(primary) +#, fuzzy +msgid "XML" +msgstr "" +"#-#-#-#-# xml-tags.po (PACKAGE VERSION) #-#-#-#-#\n" +"XML\n" +"#-#-#-#-# xml-tags.po (PACKAGE VERSION) #-#-#-#-#\n" +"translator-credits" + +#: en_US/xml-tags.xml:17(secondary) +msgid "tags" +msgstr "标记" + +#: en_US/xml-tags.xml:18(see) en_US/xml-tags.xml:167(primary) +#: en_US/xml-tags.xml:205(primary) en_US/xml-tags.xml:241(primary) +#: en_US/xml-tags.xml:276(primary) en_US/xml-tags.xml:361(primary) +#: en_US/xml-tags.xml:386(primary) en_US/xml-tags.xml:417(primary) +#: en_US/xml-tags.xml:471(primary) en_US/xml-tags.xml:523(primary) +#: en_US/xml-tags.xml:555(primary) en_US/xml-tags.xml:593(primary) +#: en_US/xml-tags.xml:659(primary) en_US/xml-tags.xml:667(primary) +#: en_US/xml-tags.xml:673(primary) en_US/xml-tags.xml:703(primary) +#: en_US/xml-tags.xml:709(primary) en_US/xml-tags.xml:739(primary) +#: en_US/xml-tags.xml:745(primary) en_US/xml-tags.xml:774(primary) +#: en_US/xml-tags.xml:780(primary) en_US/xml-tags.xml:785(primary) +#: en_US/xml-tags.xml:791(primary) en_US/xml-tags.xml:833(primary) +#: en_US/xml-tags.xml:861(primary) en_US/xml-tags.xml:908(primary) +#: en_US/xml-tags.xml:963(primary) en_US/xml-tags.xml:968(primary) +#: en_US/xml-tags.xml:1037(primary) en_US/xml-tags.xml:1047(primary) +#: en_US/xml-tags.xml:1124(primary) en_US/xml-tags.xml:1129(primary) +#: en_US/xml-tags.xml:1219(primary) en_US/xml-tags.xml:1224(primary) +#: en_US/xml-tags.xml:1402(primary) en_US/xml-tags.xml:1407(primary) +#: en_US/xml-tags.xml:1490(primary) en_US/xml-tags.xml:1533(primary) +#: en_US/xml-tags.xml:1642(primary) en_US/xml-tags.xml:1688(primary) +#: en_US/xml-tags.xml:1738(primary) en_US/xml-tags.xml:1782(primary) +#: en_US/xml-tags.xml:1812(primary) en_US/xml-tags.xml:1983(primary) +#: en_US/xml-tags.xml:2055(primary) en_US/xml-tags.xml:2174(primary) +#: en_US/xml-tags.xml:2313(primary) en_US/xml-tags.xml:2341(primary) +#: en_US/xml-tags.xml:2396(primary) en_US/xml-tags.xml:2437(primary) +#: en_US/xml-tags.xml:2484(primary) en_US/writing-guidelines.xml:41(primary) +#: en_US/writing-guidelines.xml:54(primary) +#: en_US/writing-guidelines.xml:266(primary) +#: en_US/writing-guidelines.xml:271(primary) +#: en_US/writing-guidelines.xml:276(primary) +#: en_US/writing-guidelines.xml:281(primary) +#: en_US/writing-guidelines.xml:286(primary) +#: en_US/writing-guidelines.xml:291(primary) +#: en_US/writing-guidelines.xml:297(primary) +#: en_US/writing-guidelines.xml:303(primary) +#: en_US/writing-guidelines.xml:309(primary) +#: en_US/writing-guidelines.xml:315(primary) +#: en_US/writing-guidelines.xml:341(primary) +#: en_US/writing-guidelines.xml:346(primary) +#: en_US/writing-guidelines.xml:351(primary) +#: en_US/writing-guidelines.xml:356(primary) +#: en_US/writing-guidelines.xml:361(primary) +msgid "XML tags" +msgstr "XML 标记" + +#: en_US/xml-tags.xml:21(para) +msgid "" +"Please read this chapter carefully. This chapter describes the tags used by " +"the Docs Project. Some of the rules described are specific to the project." +msgstr "" +"请仔细阅读这一章。这一章描述了 Docs Project 使用的标记。一些规则是 Docs " +"Project 特定的。" + +#: en_US/xml-tags.xml:26(para) +msgid "" +"If these tags are used appropriately, document searches will provide " +"meaningful results. These tags help search engines identify the information " +"relevant to the search request. Another benefit is that all Fedora Project " +"documents will have a similar look and feel (however, they will have some " +"differences depending upon the output format)." +msgstr "" +"如果这些标记运用合适，搜索文档时可以得到有意义的结果。这些标记帮助搜索引擎确" +"认与搜索条件相关的信息。另一个好处是使 XML XML http://www.docbook.org/tdg/en/" +"html/docbook.html xml trade;, copy;, reg; trademark trademark/trademark " +"trademark class=\"registered\"/trademark trademark class=\"copyright\"/" +"trademark para para para (para screen itemizedlist orderedlist variablelist " +"table para listitem para listitem para screen XML screen screen /screen) " +"screen application XML application application application /application " +"applicationMozilla/application applicationlynx/application Mozilla lynx " +"chapter XML chapter chapter id=\"ch-sample\" title/title para/para /chapter " +"chapter sect1, sect2, sect3 citetitle XML citetitle citetitle citetitleIG;/" +"citetitle. IG; command XML command application command command /command " +"commandredhat-config-keyboard/command commandsetup/command redhat-config-" +"keyboard setup commandMAILNOVIOLATIONS/command commandtrue/" +"commandcommandtrue/command MAILNOVIOLATIONS truetrue commandoption command " +"command computeroutput XML computeroutput computeroutput/computeroutput " +"emphasis XML emphasis emphasis /emphasis emphasis/emphasis emphasis/emphasis " +"example XML example example /example example example id=\"static-ip\" title/" +"title screen width=60 computeroutput host apex { option host-name \"apex." +"example.com\"; hardware ethernet 00:A0:78:8E:9E:AA; fixed-address " +"192.168.1.4; } computeroutput /screen /example host apex { option host-name " +"\"apex.example.com\"; hardware ethernet 00:A0:78:8E:9E:AA; fixed-address " +"192.168.1.4; } filename XML filename filename /filename filename filename/" +"home/smoore/sam.xml/filename /home/smoore/sam.xml applicationKeyboard " +"Configuration Tool/applicationfilenamesystem-config-keyboard/filename " +"Keyboard Configuration Toolredhat-config-keyboard /) firstterm XML firstterm " +"firstterm /firstterm firsttermdisk partitions/firstterm( disk partitions" +"( footnote XML footnote footnote para /para /footnote citetitleInstallation " +"Guide/citetitle Installation Guide figure XML figure figure id=\"fig-" +"ksconfig-basic\" title/title mediaobject imageobject imagedata fileref=\"./" +"figs/ksconfig/ksconfig-basic.eps\" format=\"EPS\"/ /imageobject imageobject " +"imagedata fileref=\"./figs/ksconfig/ksconfig-basic.png\" format=\"PNG\"/ /" +"imageobject textobject phrase /phrase /textobject /mediaobject /figure " +"figure id=\"fig-ksconfig-basic\" == id=\"\" title/title == fileref=\"./figs/" +"ksconfig/ksconfig-basics.eps\" == .eps fileref=\"./figs/ksconfig/ksconfig-" +"basics.png\" == .png phrase/phrase == \" XML GUI guilabel XML GUI guilabel " +"XML guilabel guilabel /guilabel guilabelAuthentication Configuration/" +"guilabel Authentication Configuration guibutton XML GUI guibutton XML " +"guibutton guibutton /guibutton guibuttonActivate on boot/guibutton Activate " +"on boot guiicon XML GUI guiicon XML guiicon guiicon /guiicon guiiconStart " +"Here/guiicon Start Here guimenu guimenuitem XML GUI guimenu XML guimenu XML " +"GUI guimenuitem XML guimenuitem guimenu /guimenu guimenuitem /guimenuitem " +"guimenuMain Menu/guimenu = guimenuitemProgramming/guimenuitem = " +"guimenuitemEmacs/guimenuitem applicationEmacs/application Main Menu = " +"Programming = Emacs Emacs keycap XML keycap keycap /keycap keycapEnter/" +"keycap Enter menuchoice XML menuchoice shortcut keycap menuchoice menuchoice " +"shortcut keycombokeycapCtrl/keycapkeycaps/keycap/keycombo /shortcut " +"guimenuaccelF/accelile/guimenu guimenuitemaccelS/accelave/guimenuitem /" +"menuchoice. CtrlsFileSave. keycombo XML keycombo keycombo /keycombo, keycap /" +"keycap keycombo keycapCtrl/keycapkeycapAlt/keycapkeycapDel/keycap /keycombo. " +"CtrlAltDel. itemizedlist XML itemizedlist XML itemizedlist itemizedlist " +"itemizedlist variablelist itemizedlist ( para itemizedlist listitem para/" +"para /listitem listitem para/para /listitem listitem para/para /listitem /" +"itemizedlist orderedlist XML orderedlist orderedlist XML orderedlist " +"orderedlist orderedlist orderedlist ( para orderedlist listitem paramdash; " +"http://www.redhat.com/support/errata; /para /listitem listitem paramdash; /" +"para /listitem /orderedlist http://www.redhat.com/support/errata; " +"variablelist XML variablelist XML variablelist variablelist variablelist " +"variablelist para variablelist varlistentry term /term listitem para/para /" +"listitem /varlistentry varlistentry termXFree 4.0 /term listitem paraX /" +"para /listitem /varlistentry /variablelist XFree 4.0 X frame simplelist XML " +"simplelist XML simplelist simplelist simplelist simplelist simplelist " +"simplelist itemizedlist XML table id=\"tb-hwinfo-hostbus\" title/title " +"tgroup cols=\"3\" colspec colnum=\"1\" colname=\"HostBus\" colwidth=\"33\"/ " +"colspec colnum=\"2\" colname=\"Features\" colwidth=\"34\"/ colspec colnum=\"3" +"\" colname=\"Single\" colwidth=\"33\"/ thead row entry/entry entry/entry " +"entrySingle-Initiator /entry /row /thead tbody row entryAdaptec 2940U2W/" +"entry entrysimplelist memberUltra2, wide, LVD./member memberHD68 external " +"connector./member memberOne channel, with two bus segments./member memberSet " +"the onboard termination by using the BIOS utility./member memberOnboard " +"termination is disabled when the power is off./member /simplelist/entry " +"entrysimplelist memberSet the onboard termination to automatic (the " +"default)./member memberUse the internal SCSI connector for private (non-" +"cluster) storage./member /simplelist/entry /row row entryQlogic QLA1080/" +"entry entrysimplelist memberUltra2, wide, LVD/member memberVHDCI external " +"connector/member memberOne channel/member memberSet the onboard termination " +"by using the BIOS utility./member memberOnboard termination is disabled when " +"the power is off, unless jumpers are used to enforce termination./member /" +"simplelist/entry entrysimplelist memberSet the onboard termination to " +"automatic (the default)./member memberUse the internal SCSI connector for " +"private (non-cluster) storage./member /simplelist/entry /row /tbody /tgroup /" +"table Single-Initiator Adaptec 2940U2W Ultra2, wide, LVD. HD68 external " +"connector. One channel, with two bus segments. Set the onboard termination " +"by using the BIOS utility. Onboard termination is disabled when the power is " +"off. Set the onboard termination to automatic (the default). Use the " +"internal SCSI connector for private (non-cluster) storage. Qlogic QLA1080 " +"Ultra2, wide, LVD VHDCI external connector One channel Set the onboard " +"termination by using the BIOS utility. Onboard termination is disabled when " +"the power is off, unless jumpers are used to enforce termination. Set the " +"onboard termination to automatic (the default). Use the internal SCSI " +"connector for private (non-cluster) storage. simplelist entry simplelist " +"simplelist member glosslist XML glosslist XML glosslist glosslist glosslist " +"XML glosslist glossentry glosstermapplet/glossterm glossdef para/para /" +"glossdef /glossentry glossentry glosstermarchitecture/glossterm glossdef " +"para/para /glossdef /glossentry glossentry glosstermarchive/glossterm " +"glossdef para/para /glossdef /glossentry /glosslist applet architecture " +"archive option XML option option /option option commandls/command option-la/" +"option ls -la XML indexterm -- primaryfoo/primary -- secondarybar/secondary " +"-- \"bar\" /indexterm -- foo bar seealso seealso seealso indexterm " +"primarySWAK/primary seealsosalutations/seealso /indexterm indexterm " +"primarysalutations/primary /indexterm SWAK Salutations Salutations see see " +"indexterm primaryGuinness/primary seebeer/see -- \"beer\" /indexterm " +"indexterm primarybeer/primary /indexterm Guinness Beer Beer generated-index." +"html generate.index para XML para para /para para para (para screen " +"itemizedlist orderedlist variablelist table part parts XML part part part id=" +"\"pt-foo\" partintro para/para CHAPTER; ANOTHER-CHAPTER; /part part id=\"pt-" +"setup\" title/title partintro paraFC; /para /partintro prompt XML prompt " +"prompt /prompt promptLILO:/prompt promptC:\\/prompt LILO: C:\\ screen " +"replaceable XML replaceable replaceable /replaceable replaceable foo-" +"replaceableversion-number/replaceable.replaceablearch/replaceable.rpm foo-" +"version-number.arch.rpm screen XML screen screen screen /screen screen " +"screen screen computeroutput, userinput, replaceable screen screen screen " +"screen screen lt;paragt; /screen para screen screen computeroutput userinput " +"para /parascreenuserinputcommand -sw file1/userinput/screenpara /" +"parascreencomputeroutputCompleted, time = 0.12 sec/computeroutput/screen " +"command -sw file1 Completed, time = 0.12 sec screen screen userinput " +"computeroutput userinput para filename/etc/sysconfig/init/filename /" +"parascreen GRAPHICAL=userinputyes/userinput/screen /etc/sysconfig/init " +"GRAPHICAL=yes screen replaceable section XML )sect1 sect1 id=\"s1-uniquename" +"\" title/title para /para sect2 id=\"s2-uniquename\" title/title para /para " +"sect3 id=\"s3-uniquename\" title/title para /para /sect3 /sect2 /sect1 " +"section section id=\"sn-uniquename\" title/title para /para /section section " +"id=\"sn-anothername\" title/title para /para /section table XML table table " +"id=\"tb-mockup-before-begin\" \"tb-mockup-before-begin\" titleAvailable " +"Features of GNOME and KDE/title tgroup cols=\"3\" colspec colnum=\"1\" " +"colname=\"Features\" colwidth=\"3\"/ colspec colnum=\"1\" colname=\"Features" +"\" colwidth=\"3\" colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/ " +"colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/ thead row entryFeatures/" +"entry entryGNOME/entry entryKDE/entry /row /thead tbody row entry/entry " +"entryyes/entry entryyes/entry /row row entry/entry entryyes/entry entryyes/" +"entry /row row entry/entry entryyes /entry entryyes /entry /row /tbody /" +"tgroup /table Available Features of GNOME and KDE GNOME KDE yes yes yes yes " +"yes yes XML table Emacs simplelist member table id=\"tb-hardware-powerswitch" +"\" title/title tgroup cols=\"4\" colspec colnum=\"1\" colname=\"Hardware\" " +"colwidth=\"2\"/ colspec colnum=\"2\" colname=\"Quantity\" colwidth=\"2\"/ " +"colspec colnum=\"3\" colname=\"Description\" colwidth=\"6\"/ colspec colnum=" +"\"4\" colname=\"Required\" colwidth=\"2\"/ thead row entryHardware/entry " +"entryQuantity/entry entryDescription/entry entryRequired/entry /row /thead " +"tbody row entrySerial power switches/entry entryTwo/entry entrysimplelist " +"memberPower switches enable each cluster system to power-cycle the other " +"cluster system. Note that clusters are configured with either serial or " +"network attached power switches and not both./member memberThe following " +"serial attached power switch has been fully tested:/member memberRPS-10 " +"(model M/HD in the US, and model M/EC in Europe) /member memberLatent " +"support is provided for the following serial attached power switch. This " +"switch has not yet been fully tested:/member memberAPC Serial On/Off Switch " +"(partAP9211), ulink url=\"http://www.apc.com/\"http://www.apc.com//ulink/" +"member /simplelist/entry entryStrongly recommended for data integrity under " +"all failure conditions/entry /row /tbody /tgroup /table simplelist entry " +"Hardware Quantity Required Serial power switches Two Power switches enable " +"each cluster system to power-cycle the other cluster system. Note that " +"clusters are configured with either serial or network attached power " +"switches and not both.The following serial attached power switch has been " +"fully tested:RPS-10 (model M/HD in the US, and model M/EC in Europe)Latent " +"support is provided for the following serial attached power switch. This " +"switch has not yet been fully tested:APC Serial On/Off Switch (partAP9211), " +"http://www.apc.com/ Strongly recommended for data integrity under all " +"failure conditions trademark XML trademark trade;, copy;, reg; trademark " +"trademark/trademark trademark class=\"registered\"/trademark trademark class=" +"\"copyright\"/trademark userinput XML userinput userinput userinputdd " +"if=boot.img of=/dev/fd0 bs=1440k/userinput dd if=boot.img of=/dev/fd0 " +"bs=1440k ulink XML ulink mdash; ulink url=\"http://www.redhat.com/support/" +"errata/\" http://www.redhat.com/support/errata//ulink; http://www.redhat.com/" +"support/errata/; /)http://www.redhat.com/ wordasword XML wordasword " +"wordasword wordasword wordasword commandgrep/command wordaswordlinux/" +"wordaswordcommandgrep linux/command grep linuxgrep linux xref XML xref xref " +"xref linkend=\"ch-tutorial\"/xref xref linkend=\"s1-tutorial-parent\"/xref" + +#: en_US/xml-tags.xml:35(secondary) +msgid "general tag information" +msgstr "" + +#: en_US/xml-tags.xml:38(para) +msgid "" +"Most tags in XML must have an opening and closing tag. A few tags, such as " +"xref, 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 " +"." +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 trade, copy, or reg 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 trademark tag and its " +"associates classes as follows:" +msgstr "" + +#: en_US/xml-tags.xml:85(para) en_US/writing-guidelines.xml:164(para) +msgid "" +"trademarktrademark symbol after " +"metrademark" +msgstr "" + +#: en_US/xml-tags.xml:91(para) en_US/writing-guidelines.xml:170(para) +msgid "" +"trademark class=\"registered\"registered trademark symbol after metrademark" +msgstr "" + +#: en_US/xml-tags.xml:97(para) en_US/writing-guidelines.xml:176(para) +msgid "" +"trademark class=\"copyright\"copyright " +"symbol after metrademark" +msgstr "" + +#: en_US/xml-tags.xml:105(term) en_US/writing-guidelines.xml:184(term) +msgid "Content inside para tags" +msgstr "" + +#: en_US/xml-tags.xml:107(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 in the PDF version." +msgstr "" + +#: en_US/xml-tags.xml:112(para) +msgid "" +"Specifically, do not use para tags around the following " +"(or, to put this another way, do not embed the following within " +"para 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 para tags within listitem tags" +msgstr "" + +#: en_US/xml-tags.xml:139(para) +msgid "" +"Content inside para tags within listitem tags must start immediately after the " +"beginning para 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 screen tags" +msgstr "" + +#: en_US/xml-tags.xml:150(para) en_US/writing-guidelines.xml:229(para) +msgid "" +"The content inside screen tags (screen and screen) " +"must 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 application and application 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" +"Mozilla \n" +"or lynx 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 Mozilla or " +"lynx 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: zh_CN.po,v 1.1 2007/03/11 21:33:24 pfrields Exp $ -->\n" +"\n" +" <chapter id=\"ch-sample\">\n" +" <title>Sample Chapter</title>\n" +"\n" +" <para>This is a sample chapter, showing you the XML tags used to create a\n" +" chapter, sections, and subsections.</para>\n" +" \n" +" </chapter>\n" +msgstr "" + +#: en_US/xml-tags.xml:227(para) +msgid "" +"The chapter can also be further divided into sections (section, section, sect3, etc.). Refer " +"to 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 citetitle 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 )." +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" +".\n" +msgstr "" + +#: en_US/xml-tags.xml:265(para) +msgid "" +"The output looks like Installation Guide because " +"IG 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 command tags." +msgstr "" + +#: en_US/xml-tags.xml:286(para) +msgid "" +"If you have text that is a command, use the command and command 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 " +"redhat-config-keyboard command, or you can type " +"setup 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 "" +"MAILNOVIOLATIONS— If set to true " +"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 true." +msgstr "" + +#: en_US/xml-tags.xml:334(title) en_US/xml-tags.xml:509(title) +#: en_US/xml-tags.xml:988(title) en_US/xml-tags.xml:1063(title) +#: en_US/xml-tags.xml:1147(title) en_US/xml-tags.xml:1387(title) +#: en_US/xml-tags.xml:1500(title) en_US/xml-tags.xml:1769(title) +#: en_US/xml-tags.xml:1930(title) en_US/xml-tags.xml:2422(title) +#: en_US/writing-guidelines.xml:394(title) en_US/emacs.xml:265(title) +#: en_US/emacs.xml:565(title) en_US/emacs-nxml.xml:160(title) +msgid "Note" +msgstr "" + +#: en_US/xml-tags.xml:334(para) +msgid "" +"In this example, the option value (true) is defined with a <command> " +"tag set. Because a option is a configuration file option (command line " +"options which would use the <option> tag set), and because there is no " +"configuration file option tag available to use, we are extending the <" +"command> tag set to define options in a configuration file." +msgstr "" + +#: en_US/xml-tags.xml:342(para) +msgid "" +"Terms marked with command 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 <emphasis> and " +"</emphasis> 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 will remove all existing Linux " +"partitions on all 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 <example> and </example> 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 <example> 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 <filename> and </filename> tags define a filename or path to a file. Since directories are " +"just special files, they are marked with the filename " +"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 /home/smoore/sam.xml 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 Keyboard Configuration Tool, the " +"redhat-config-keyboard RPM package must be installed." +msgstr "" + +#: en_US/xml-tags.xml:510(para) +msgid "" +"Directory names must end with a forward slash (/) 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 <firstterm> and </firstterm> tags helps to define a word that may be unfamiliar to the user, but " +"that will be seen commonly throughout the text. For example:" +msgstr "" + +#: en_US/xml-tags.xml:534(computeroutput) +#, no-wrap +msgid "" +"\n" +"Nearly every modern-day operating system uses <firstterm>disk\n" +"partitions</firstterm>, and Fedora Core is no exception.\n" +msgstr "" + +#: en_US/xml-tags.xml:544(para) +msgid "" +"Nearly every modern-day operating system uses disk partitions, and Fedora Core is no exception." +msgstr "" + +#: en_US/xml-tags.xml:552(command) en_US/xml-tags.xml:556(secondary) +msgid "footnote" +msgstr "" + +#: en_US/xml-tags.xml:559(para) +msgid "If you need to make a footnote, use the following example:" +msgstr "" + +#: en_US/xml-tags.xml:563(computeroutput) +#, no-wrap +msgid "" +"\n" +"For those of you who need to perform a server-class\n" +"<footnote>\n" +"<para>\n" +"A server-class installation sets up a typical server\n" +"environment. Note, no graphical environment is \n" +"installed during a server-class installation.\n" +"</para> \n" +"</footnote> installation, refer to the <citetitle>Installation Guide</citetitle>.\n" +msgstr "" + +#: en_US/xml-tags.xml:580(para) +msgid "" +"A server-class installation sets up a typical server environment. Please " +"note, no graphical environment is installed during a server-class " +"installation." +msgstr "" + +#: en_US/xml-tags.xml:579(para) +msgid "" +"For those of you who need to perform a server-class " +"installation, refer to the Installation Guide." +msgstr "" + +#: en_US/xml-tags.xml:590(command) en_US/xml-tags.xml:594(secondary) +#: en_US/writing-guidelines.xml:107(sgmltag) +msgid "figure" +msgstr "" + +#: en_US/xml-tags.xml:598(title) en_US/xml-tags.xml:1827(title) +#: en_US/writing-guidelines.xml:424(title) en_US/emacs-nxml.xml:96(title) +msgid "Important" +msgstr "注意" + +#: en_US/xml-tags.xml:599(para) +msgid "" +"Order matters! The EPS file must 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\"> \n" +"\n" +"<title>Basic Configuration</title> \n" +"\n" +"fileref=\"./figs/ksconfig/ksconfig-basics.eps\"> \n" +"\n" +"fileref=\"./figs/ksconfig/ksconfig-basics.png\"> \n" +" \n" +"<phrase>Some text description of this image</phrase> \n" +msgstr "" + +#: en_US/xml-tags.xml:648(para) +msgid "" +"For more information on taking screenshots, refer to ." +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 <guilabel> and </guilabel> 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 Authentication Configuration 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 <guibutton> and </guibutton>" +" 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 Activate on boot 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 <guiicon> and </guiicon> 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 Start Here icon on the desktop." +msgstr "" + +#: en_US/xml-tags.xml:770(title) +msgid "guimenu and guimenuitem" +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 <guimenu> and </" +"guimenu> tags." +msgstr "" + +#: en_US/xml-tags.xml:801(para) +msgid "" +"To note submenu items, use the <guimenuitem> and " +"</guimenuitem> 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 Main Menu => " +"Programming => Emacs to start the Emacs 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 <keycap> and </keycap> 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 Enter 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: CtrlsFileSave." +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 <" +"keycombo> and </keycombo>, " +"<keycap> and </keycap> " +"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 CtrlAltDel." +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 ItemizedList 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 VariableList and " +"presents the information in a very simple way." +msgstr "" + +#: en_US/xml-tags.xml:984(para) +msgid "" +"To create an ItemizedList (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 " +"para 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 orderedlist is best used to present information that " +"is important for the reader to know in a specific order. " +"orderedlists 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 orderedlist (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 variablelist 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 variablelist, use the following command " +"sequence:" +msgstr "" + +#: en_US/xml-tags.xml:1157(computeroutput) +#, no-wrap +msgid "" +"\n" +"<variablelist>\n" +" <varlistentry> \n" +" <term> New Multi-CD Install </term>\n" +" <listitem> \n" +" <para>As the installation program continues to grow, Red Hat has developed \n" +" an installation program capable of installing from \n" +" multiple CD-ROMs.</para>\n" +" </listitem>\n" +" </varlistentry>\n" +"\n" +" <varlistentry>\n" +" <term>XFree 4.0 </term>\n" +" <listitem>\n" +" <para>Configuration of your X Window System during the installation has \n" +" never been more thorough. From choosing your monitor and its correct \n" +" settings, to video card probing, to testing your desired X setup, \n" +" Xconfigurator will help you set everything just right.</para>\n" +" </listitem>\n" +" </varlistentry>\n" +"</variablelist>\n" +msgstr "" + +#: en_US/xml-tags.xml:1185(term) +msgid "New Multi-CD Install" +msgstr "" + +#: en_US/xml-tags.xml:1185(para) +msgid "" +"As the installation program continues to grow, Red Hat has developed an " +"installation program capable of installing from multiple CD-ROMs." +msgstr "" + +#: en_US/xml-tags.xml:1193(term) +msgid "XFree 4.0" +msgstr "" + +#: en_US/xml-tags.xml:1195(para) +msgid "" +"Configuration of your X Window System during the installation has never been " +"more thorough. From choosing your monitor and its correct settings, to video " +"card probing, to testing your desired X setup, Xconfigurator will help you " +"set everything just right." +msgstr "" + +#: en_US/xml-tags.xml:1205(title) en_US/writing-guidelines.xml:434(title) +msgid "Warning" +msgstr "" + +#: en_US/xml-tags.xml:1206(para) +msgid "" +"Do not specify the frame 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 Simplelist" +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 simplelist is an unadorned list of items. " +"simplelists can be inline or arranged in columns." +msgstr "" + +#: en_US/xml-tags.xml:1244(para) +msgid "" +"We use simplelist to add separate paragraphs of text " +"within a table element. A regular list, such as itemizedlist, 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 SimpleList 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 SimpleList, 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 glosslist 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 <" +"option> and </option> 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 ls you can specify an " +"option such as ." +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 <seealso> tag allows you to reference another " +"index entry or refer to another manual. Make sure the <" +"seealso> 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 <see> 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 " +"generated-index.html 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 generate.index stylesheet parameter, which is set to true by default." +msgstr "" + +#: en_US/xml-tags.xml:1638(command) en_US/xml-tags.xml:1643(secondary) +msgid "para" +msgstr "" + +#: en_US/xml-tags.xml:1646(para) +msgid "" +"For any paragraph, the <para> and </" +"para> 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 <para> tags around the following (or, to " +"put this another way, do not embed the following within <para>" +" 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 part 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 <" +"prompt> and </prompt> 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 LILO: boot prompt, type linux to boot into your " +"Linux partition." +msgstr "" + +#: en_US/xml-tags.xml:1764(para) +msgid "At the C:\\> prompt, type ...." +msgstr "" + +#: en_US/xml-tags.xml:1770(para) +msgid "" +"When showing example computer output (usually in screen " +"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 <replaceable> and </replaceable> 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 replaceable tags " +"when referencing the name of an RPM file:" +msgstr "" + +#: en_US/xml-tags.xml:1796(screen) +#, no-wrap +msgid "" +"\n" +"foo-<replaceable>version-number</replaceable>.<replaceable>arch</replaceable>.rpm\n" +msgstr "" + +#: en_US/xml-tags.xml:1805(replaceable) +msgid "version-number" +msgstr "" + +#: en_US/xml-tags.xml:1805(replaceable) +msgid "arch" +msgstr "" + +#: en_US/xml-tags.xml:1804(screen) +#, no-wrap +msgid "" +"\n" +"foo-..rpm\n" +msgstr "" + +#: en_US/xml-tags.xml:1816(para) +msgid "" +"The <screen> 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 " +"<screen> and closing </screen> tags around the text you are emphasizing." +msgstr "" + +#: en_US/xml-tags.xml:1828(para) +msgid "" +"When using the <screen> tag, set everything within " +"that screen to flush left. The contents of the screen 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 <screen> tag set may contain other inline tags, " +"such as <computeroutput>, <userinput>" +", or <replaceable>. Additional inline " +"tags are not required by definition. The <screen> " +"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 <" +"screen> tags create line breaks in any rendered output. Place " +"any inline tags on the same line as their content. Do " +"not overuse tagging within a <screen> tag set." +msgstr "" + +#: en_US/xml-tags.xml:1857(para) +msgid "An example of <screen> 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 screen" +msgstr "" + +#: en_US/xml-tags.xml:1879(para) +msgid "" +"If you choose to use inline tags inside a <screen> " +"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 <computeroutput> tag set around the entire " +"output. If the user should type the example on the command line or in a " +"configuration file, use the <userinput> 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\n" +"\t Type the following command:\n" +"\t\n" +"\n" +"\n" +"command -sw file1\n" +"\n" +"\n" +"\t\n" +"\t You should see the following output:\n" +"\t\n" +"\n" +"\n" +"Completed, time = 0.12 sec\n" +"\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 screen tags, do not show the prompt." +msgstr "" + +#: en_US/xml-tags.xml:1937(para) +msgid "" +"If the <screen> shows the reader how to change only " +"part of a line, mark the change with an inline " +"<userinput> tag set. You may use the <" +"userinput> tag set inside a larger area that is already marked " +"inline with <computeroutput>. 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\n" +"\t Edit the /etc/sysconfig/init file as follows:\n" +"\t\n" +"\n" +"\n" +"GRAPHICAL=yes \n" +"\n" +msgstr "" + +#: en_US/xml-tags.xml:1962(para) +msgid "Edit the /etc/sysconfig/init 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=\n" +msgstr "" + +#: en_US/xml-tags.xml:1970(para) +msgid "" +"For an explanation of how to use the replaceable tags " +"within a set of screen tags, refer to ." +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 " +"Installation Guide), you can have sections and " +"subsections. <section> 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 " +"section 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 " +"" +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 "" +" 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 "" +" 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 "" +" 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 "" +" 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" +" \n" +"\n" +"<title>Available Features of GNOME and KDE</title>\n" +"\n" +"<tgroup cols=\"3\">\n" +" \n" +"\n" +"<colspec colnum=\"1\" colname=\"Features\" colwidth=\"3\"/>\n" +" \n" +" \n" +" \n" +" \n" +" \n" +"\n" +"<colspec colnum=\"2\" colname=\"GNOME\" colwidth=\"2\"/>\n" +"<colspec colnum=\"3\" colname=\"KDE\" colwidth=\"2\"/>\n" +"\n" +"<thead>\n" +" \n" +"\n" +"<row> \n" +" \n" +"\n" +"<entry>Features</entry>\n" +" \n" +"\n" +"<entry>GNOME</entry> \n" +"<entry>KDE</entry>\n" +"</row> \n" +"</thead> \n" +"\n" +"<tbody> \n" +" \n" +"\n" +"<row> \n" +"<entry>highly configurable</entry> \n" +"<entry>yes</entry> \n" +"<entry>yes</entry> \n" +"</row> \n" +"<row> \n" +"<entry>multiple window managers </entry>\n" +"<entry>yes</entry> \n" +"<entry>yes</entry> \n" +"</row> \n" +"<row> \n" +"<entry>Internet applications</entry> \n" +"<entry>yes </entry> \n" +"<entry>yes </entry> \n" +"</row> \n" +"</tbody> \n" +"</tgroup> \n" +"</table> \n" +msgstr "" + +#: en_US/xml-tags.xml:2135(title) +msgid "Available Features of GNOME and KDE" +msgstr "" + +#: en_US/xml-tags.xml:2145(entry) +msgid "GNOME" +msgstr "" + +#: en_US/xml-tags.xml:2146(entry) +msgid "KDE" +msgstr "" + +#: en_US/xml-tags.xml:2152(entry) +msgid "highly configurable" +msgstr "" + +#: en_US/xml-tags.xml:2157(entry) +msgid "multiple window managers" +msgstr "" + +#: en_US/xml-tags.xml:2162(entry) +msgid "Internet applications" +msgstr "" + +#: en_US/xml-tags.xml:2171(title) +msgid "Creating a List Within a Table" +msgstr "" + +#: en_US/xml-tags.xml:2176(tertiary) +msgid "list within a table" +msgstr "" + +#: en_US/xml-tags.xml:2180(para) +msgid "" +"Creating a list within a table can be a difficult task. It requires strict " +"formatting and a set of commands that are not available for command " +"completion in Emacs." +msgstr "" + +#: en_US/xml-tags.xml:2185(para) +msgid "" +"The tags you will need to use are <simplelist> and " +"<member>." +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 <simplelist> tag must be beside the " +"<entry> tag? If you do not format this properly, it " +"will not parse cleanly." +msgstr "" + +#: en_US/xml-tags.xml:2252(para) +msgid "The above example will look like the following:" +msgstr "" + +#: en_US/xml-tags.xml:2255(title) +msgid "Power Switch Hardware Table" +msgstr "" + +#: en_US/xml-tags.xml:2264(entry) +msgid "Hardware" +msgstr "" + +#: en_US/xml-tags.xml:2265(entry) +msgid "Quantity" +msgstr "" + +#: en_US/xml-tags.xml:2266(entry) en_US/emacs.xml:415(segtitle) +msgid "Description" +msgstr "" + +#: en_US/xml-tags.xml:2267(entry) +msgid "Required" +msgstr "" + +#: en_US/xml-tags.xml:2274(entry) +msgid "Serial power switches" +msgstr "" + +#: en_US/xml-tags.xml:2276(entry) +msgid "Two" +msgstr "" + +#: en_US/xml-tags.xml:2278(member) +msgid "" +"Power switches enable each cluster system to power-cycle the other cluster " +"system. Note that clusters are configured with either serial or network " +"attached power switches and not both." +msgstr "" + +#: en_US/xml-tags.xml:2283(member) +msgid "The following serial attached power switch has been fully tested:" +msgstr "" + +#: en_US/xml-tags.xml:2286(member) +msgid "RPS-10 (model M/HD in the US, and model M/EC in Europe)" +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), " +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 trademark 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 userinput 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 — 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:2423(para) +msgid "" +"If the URL does not end in a filename, it must end in a slash " +"(/) to be a properly formed URL. For " +"example, http://www.redhat.com/." +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 grep to search for the word linux, use the command grep linux." +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 <" +"xref> 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 and ." +msgstr "" + +#: en_US/vim.xml:13(title) +msgid "VIM and DocBook" +msgstr "VIM 与 DocBook" + +#: en_US/vim.xml:16(primary) en_US/vim.xml:33(primary) +msgid "VIM" +msgstr "VIM" + +#: en_US/vim.xml:19(para) +msgid "" +"VIM has many features to help you write XML content such as DocBook, " +"including syntax highlighting and customizable key bindings. Additionally, " +"one can easily use external programs from VIM for features such as spell-" +"checking. This chapter assumes you already know generally how to use VIM; if " +"you want to learn how, try the vimtutor or by typing " +":help tutor from inside VIM." +msgstr "" +"VIM 有很多特性，有助于撰写类似 DocBook 的 XML 文档，包括语法高亮和可定制的按" +"键绑定。另外，还可以用外部程序辅助 VIM 完成拼写检查等操作。本章假定您已知悉 " +"VIM 一般用法；如果您要学习一般用法，执行 vimtutor 或在 " +"VIM 中执行 :help tutor。" + +#: en_US/vim.xml:30(title) +msgid "Setting Up Your .vimrc File" +msgstr "设置 .vimrc 文件" + +#: en_US/vim.xml:34(secondary) en_US/emacs.xml:44(secondary) +#, fuzzy +msgid "configuration file" +msgstr "" +"#-#-#-#-# emacs.po (PACKAGE VERSION) #-#-#-#-#\n" +"translator-credits\n" +"#-#-#-#-# vim.po (PACKAGE VERSION) #-#-#-#-#\n" +"配置文件" + +#: en_US/vim.xml:37(para) +msgid "" +"Below is a short sample .vimrc file that turns on some " +"VIM features useful for editing SGML or XML content such as DocBook: " +"\n" +"\" 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\n" +"" +msgstr "" +"下面是一个示例 .vimrc 文件，打开了一些 VIM 特性，便于编" +"辑类似 DocBook 的 SGML 或 XML 文档： \n" +"\" 关闭 vi 兼容特性，类似有限的撤销\n" +"set nocompatible\n" +"\" 基于文件扩展名的语法高亮\n" +"syntax on\n" +"\" 在 80 个字符后面自动插入新行\n" +"set textwidth=80\n" +"\" 自动缩进\n" +"set autoindent\n" +"\" 使用 % 匹配 SGML 标记\n" +"source $VIMRUNTIME/macros/matchit.vim\n" +"" + +#: en_US/vim.xml:55(para) +msgid "" +"Some of these features require the vim-enhanced package " +"to be installed. If you are using or the vim-minimal " +"package, or if you are using an older version of VIM, you may not have the " +"$VIMRUNTIME/macros/matchit.vim file. You can still " +"download matchit.zip from Vim.org and load it separately." +msgstr "" +"一些特性需要安装 vim-enhanced。如果您使用的是 " +"vim-minimal，或者是旧版本的 VIM，可能不包含 " +"$VIMRUNTIME/macros/matchit.vim 文件，那么可以在 Vim.org 下载 " +"matchit.zip 并加载。" + +#: en_US/vim.xml:69(title) +msgid "Keymapping with VIM" +msgstr "VIM 中的按键映射" + +#: en_US/vim.xml:71(para) +msgid "" +"VIM can speed up your DocBook creation by mapping frequently typed tags (or " +"any words or phrases) onto short key combinations. By default, the keymap " +"leader is the backslash (\\), but it can be redefined " +"with a command like let mapleader =\n" +" \",\". There are two ways to use the following example; " +"you can put it directly in your .vimrc, or you can save " +"it in a separate file and load it with a source " +"command in your .vimrc. \n" +"e />:nohlsearcha\n" +"\n" +"\" common tags that start a new text block\n" +"imappa O\n" +"imapsn
jo
O\n" +"imappl O0i\n" +"imapcp O0i\n" +"\n" +"\" common tags that are placed inline\n" +"\" use F>a\n" +"imapen F>a\n" +"imapfi F>a\n" +"imaplt F>a\n" +"imapre F>a\n" +"imapui F>a\n" +"imapul F>a\n" +"imapsi F>a\n" +"imapus F>a\n" +"imapsy F>a\n" +"imapcm F>a \n" +"\" entities\n" +"imap > >\n" +"imap < <]]>\n" +"" +msgstr "" +"VIM 可以使创建 DocBook 文档更加快捷，只要将经常使用的标记 (或任何词汇短语) 定" +"义为快捷键。默认情况下，键盘映射以反斜线 (\\) 开始，但是也" +"可以用命令定义，类似 let mapleader =\n" +" \",\"。有两种方式来使用下面的例子；您可以将它写在 " +".vimrc 文件中，或者将它保存为单独的文件，并在 " +".vimrc 文件中以 source 命令加载。" +"" + +#: 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 ." +msgstr "" +"不幸的是，这不是所有 DocBook 命令的完整集合，因此您需要自行定义，或定制 " +" 范例中的定义。" + +#: en_US/vim.xml:119(title) +msgid "Additional VIM Resources" +msgstr "其他 VIM 资源" + +#: en_US/vim.xml:121(para) +msgid "Additional information about VIM may be found from:" +msgstr "其他 VIM 相关的资源可以在这里找到：" + +#: en_US/vim.xml:127(para) +msgid "" +" Example sgml-vimrc from the Beginner's guide to " +"Vi Improved (VIM)" +msgstr "" +" 示例 sgml-vimrc，来自 Beginner's guide to Vi " +"Improved (VIM)" + +#: en_US/vim.xml:134(para) +msgid "" +"The VIM Quick " +"Reference Card" +msgstr "VIM Quick Reference Card" + +#: en_US/vim.xml:140(ulink) +msgid "Vim as XML Editor" +msgstr "Vim 作为 XML 编辑器" + +#: en_US/vim.xml:145(para) +msgid "" +"The VIM REFERENCE MANUAL, which comes with the " +"vim-common package —/usr/share/vim/" +"<version>/doc/intro.txt or type " +":help intro from within VIM" +msgstr "" +"VIM REFERENCE MANUAL，包含在 vim-common 软件包中 /usr/share/vim/version/doc/intro.txt:help intro" + +#: 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 "" +"在本章您将看到 !DOCTYPE article PUBLIC \"-//OASIS//DTD DocBook XML V4.2//EN" +"\" \"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd\" [ !ENTITY % " +"FEDORA-ENTITIES-EN SYSTEM \"../common/fedora-entities-en.xml\" %FEDORA-" +"ENTITIES-EN; !ENTITY VERSION \"0.1\" !-- change version of tutorial here -- !" +"ENTITY DOCID \"example-tutorial-VERSION; (2003-07-07)\" !-- change last " +"modified date here -- !ENTITY LEGALNOTICE SYSTEM \"../common/legalnotice-en." +"xml\" ] article id=\"example-tutorial\" lang=\"en\" articleinfo titleExample " +"Tutorial/title copyright year2003/year holder/holder holderTammy Fox/holder /" +"copyright authorgroup author surnameFox/surname firstnameTammy/firstname /" +"author /authorgroup LEGALNOTICE; /articleinfo section id=\"some-section\" " +"titleSome Section/title para This is an example section. You can also use " +"sect1, sect2, etc. /para warning titleWarning/title para Example of an " +"admonition. /para /warning /section index id=\"generated-index\"/index /" +"article legalnotice.xml" + +#: en_US/tutorial.xml:23(title) +msgid "The Parent File" +msgstr "translator-credits" + +#: 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 must contain the file " +"legalnotice.xml. 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 not " +"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 "" +"这一章包含了 style Ulysses http://www.online-literature.com/james_joyce/" +"ulysses/18/ So you made the changes I showed you in the last section. What's " +"the next thing you should do? Just pop your thumb drive onto your system and " +"read the messages log. When you see \"USB device found,\" then Bob's your " +"uncle. After you complete the configuration changes above, attach the USB " +"removable media to your system. Use the dmesg command to examine the kernel " +"message log. The message USB device found indicates that your device was " +"installed successfully. The Elements of Style, http://bartleby.com/141/ The " +"Chicago Manual of Style, http://www.chicagomanualofstyle.org/ Paradigm " +"Online Writing Assistant, http://www.powa.org/ GNOME Documentation Style " +"Guidelines (GDSG)GDSGhttp://developer.gnome.org/documents/style-guide/ GDSG " +"The Elements of Style (http://www.bartleby.com/141/) Under normal operating " +"conditions, the kernel does not always immediately write file data to the " +"disks, storing it in a memory buffer and then periodically writing to the " +"disks to speed up operations. Normally, the kernel stores the data in memory " +"prior to periodically writing the data to the disk. The Workspace Switcher " +"applet helps you navigate all of the virtual desktops available on your " +"system. The X Window system, working in hand with a piece of software called " +"a window manager, allows you to create more than one virtual desktop, known " +"as workspaces, to organize your work, with different applications running in " +"each workspace. The Workspace Switcher applet is a navigational tool to get " +"around the various workspaces, providing a miniature road map in the GNOME " +"panel showing all your workspaces and allowing you to switch easily between " +"them. Use the Workspace Switcher to add new workspaces to the GNOME Desktop. " +"You can run different applications in each workspace. The Workspace Switcher " +"applet provides a miniature map that shows all of your workspaces. You can " +"use the Workspace Switcher applet to switch between workspaces. There is a " +"text box that you can use to find out the definition of a word. To request a " +"definition of a word, type the word in the text box, then select Lookup. The " +"applet is a handy little screen grabber. Use the applet to take screenshots. " +"docs documentation Jargon Buster (http://fedora.redhat.com/docs/jargon-" +"buster/) American Heritage Dictionary (http://www.bartleby.com/61/ ) GDSGThe " +"Elements of Style American Heritage Dictionary (http://www.bartleby.com/61/) " +"Chicago Manual of Style (http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/" +"cmosfaq.html) Dr., a.m., p.m. i.e. (\"in other words\", e.g. (\"for example" +"\", From the first letters of each word in a compound term, for example " +"Table of Contents (TOC). From recognizable parts of a compound term, such as " +"GNU Object Model Environment (GNOME). the the Main Menu'sHelp option don't " +"use the default option several SCSI disk's the Help option on the Main Menu " +"do not use the default option several SCSI disks replaceable Shift can't, " +"don't, isn't Chicago Manual of Style ( http://www.press.uchicago.edu/Misc/" +"Chicago/cmosfaq/cmosfaq.html) American Heritage Dictionary (http://www." +"bartleby.com/61/) directory-namefilename ly American Heritage Dictionary " +"(http://www.bartleby.com/61/) Chicago Manual of Style (http://www.press." +"uchicago.edu/Misc/Chicago/cmosfaq/cmosfaq.html) See v. Refer to see seealso " +"and/or American Heritage Dictionary (http://www.bartleby.com/61/) IEEE " +"Standard Dictionary of Electrical and Electronics Terms yum update yum " +"update yum update up2date tar cpio up2date tar cpio don't can't XYZ\" XYZ" +"\"XYZ Main Menu - Foobar Search Main Menu Foobar Search DocBook sfdisk " +"sfdisk sfdisk sfdisk -n sfdisk sfdisk sfdisk -n replaceable replaceable XML " +"fedora-docs common/ FC; FCVER;\" \"" + +#: en_US/style.xml:62(title) +msgid "Why Style Is Important" +msgstr "translator-credits" + +#: en_US/style.xml:64(para) +msgid "" +"Writing well comes naturally to almost no one. It is a skill that " +"professional writers, even famous ones, must practice constantly. " +"Stylestyle " +"is the quality that separates elegant writing from the merely functional." +msgstr "" + +#: en_US/style.xml:77(para) +msgid "" +"For example, refer to. http://www.online-literature.com/james_joyce/" +"ulysses/18/. 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 " +"Ulysses. 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 " +"messages 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 dmesg command to examine " +"the kernel message log. The message USB device\n" +"\t found 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 "" +"The Elements of Style, by William Strunk. Basic rules " +"and links to online versions can be found at: http://en.wikipedia.org/wiki/" +"The_Elements_of_Style" +msgstr "" + +#: en_US/style.xml:176(para) +msgid "" +"The Chicago Manual of Style, by the University of " +"Chicago Press. Online version: http://www.chicagomanualofstyle.org/" +msgstr "" + +#: en_US/style.xml:183(para) +msgid "" +"Paradigm Online Writing Assistant, maintained by " +"Chuck Guilford, Ph.D. Online only: http://www.powa.org/" +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 " +"GNOME Documentation Style Guidelines " +"(GDSG). You may read the original GDSG at http://developer.gnome.org/documents/style-guide/." +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 GDSG." +msgstr "" + +#. This section will reproduce mostly what is in Chapter 1 of +#. the GDSG. There may be minor changes. FIXME: Make sure the +#. appropriate front matter of the Documentation Guide includes +#. attribution as required by the GNU FDL. +#: en_US/style.xml:218(para) +msgid "" +"This chapter provides a brief introduction to writing technical " +"documentation." +msgstr "" + +#: en_US/style.xml:224(title) +msgid "General Style Requirements" +msgstr "" + +#: en_US/style.xml:225(para) +msgid "" +"Technical writing for the Fedora Project imposes special constraints beyond " +"the basic requirements of good prose. Good Fedora technical documentation " +"has the following characteristics:" +msgstr "" + +#: en_US/style.xml:232(term) +msgid "Comprehensive" +msgstr "" + +#: en_US/style.xml:234(para) +msgid "" +"Describe all of the functionality of a product. Do not omit functionality " +"that you regard as irrelevant for the user." +msgstr "" + +#: en_US/style.xml:242(term) +msgid "Conforming" +msgstr "" + +#: en_US/style.xml:249(para) +msgid "" +"Describe what you see. Do not describe what you want to see. Present your " +"information in the order that users experience the subject matter." +msgstr "" + +#: en_US/style.xml:257(term) +msgid "Clear" +msgstr "" + +#: en_US/style.xml:259(para) +msgid "" +"Read The Elements of Style (http://en.wikipedia.org/wiki/" +"The_Elements_of_Style) 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 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 Workspace Switcher applet helps you navigate " +"all of the virtual desktops available on your system. The X Window system, " +"working in hand with a piece of software called a window manager, allows you to create more than one virtual desktop, known as " +"workspaces, to organize your work, with different " +"applications running in each workspace. The Workspace Switcher applet is a navigational tool to get around the various " +"workspaces, providing a miniature road map in the GNOME panel showing all " +"your workspaces and allowing you to switch easily between them." +msgstr "" + +#: en_US/style.xml:375(title) +msgid "Correct: Organized topics" +msgstr "" + +#: en_US/style.xml:376(para) +msgid "" +"Use the Workspace Switcher to add new " +"workspaces to the GNOME Desktop. You can run different " +"applications in each workspace. The Workspace Switcher applet provides a miniature map that shows all of your " +"workspaces. You can use the Workspace Switcher " +"applet to switch between workspaces." +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 Lookup." +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 Core 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 " +"documentation instead of the term docs. 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 Fedora Jargon Buster " +"(http://fedora." +"redhat.com/docs/jargon-buster/)." +msgstr "" + +#: en_US/style.xml:588(para) +msgid "" +"The term does not appear in the American Heritage Dictionary (http://www.bartleby." +"com/61/ )." +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 his/her or s/he 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 GDSG, and " +"partly from The Elements of Style, 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 American " +"Heritage Dictionary (http://www.bartleby.com/61/) and the Chicago Manual of " +"Style (http://www.press.uchicago.edu/Misc/Chicago/cmosfaq/" +"cmosfaq.html.)" +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 Dr., a.m., " +"p.m., 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 i.e. for \"in other " +"words\" and e.g. 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 " +"simply, easily, quickly." +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 the 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 Main Menu'sHelp 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 Help option on the Main Menu" +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 " +"replaceable tag. Refer to 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 Shift 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 for example 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 can't, don't, or isn't." +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 ." +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 Chicago " +"Manual of Style ( http://www.press.uchicago.edu/Misc/Chicago/" +"cmosfaq/cmosfaq.html.)" +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 American " +"Heritage Dictionary (http://www.bartleby.com/61/) 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 directory-name. Note: filename 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 ly" +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 American " +"Heritage Dictionary (http://www.bartleby.com/61/), 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 like 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 million, 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: " +"two 10 MB files" +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 Chicago " +"Manual of Style (http://www.press.uchicago.edu/Misc/Chicago/" +"cmosfaq/cmosfaq.html.)" +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 see and seealso 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 and/or, 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 " +"American Heritage Dictionary (http://www.bartleby.com/61/) 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 IEEE Standard Dictionary of " +"Electrical and Electronics Terms." +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 yum update command must be run." +msgstr "" + +#: en_US/style.xml:1694(para) +msgid "You might want to run the yum update command." +msgstr "" + +#: en_US/style.xml:1700(title) +msgid "Correct: Active voice" +msgstr "" + +#: en_US/style.xml:1701(para) +msgid "Run the yum update 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 " +"." +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 up2date " +"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 " +"tar or cpio 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 up2date before configuring the " +"Samba server." +msgstr "" + +#: en_US/style.xml:1762(para) +msgid "" +"If necessary, users can back up files with the tar or " +"cpio 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 don't or can't. Refer to ." +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 Core. 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 Core " +"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 " +"XYZ.\" 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 XYZ.\" Then elaborate as " +"required. If the whole section concerns how to do XYZ, leave this sentence out entirely. Refer also to ." +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 Main Menu -> Foobar" +msgstr "" + +#: en_US/style.xml:1839(para) +msgid "Find the option labeled Search" +msgstr "" + +#: en_US/style.xml:1846(title) +msgid "Correct: Precise wording" +msgstr "" + +#: en_US/style.xml:1849(para) +msgid "" +"From the Main Menu, select Foobar" +msgstr "" + +#: en_US/style.xml:1855(para) +msgid "Select the Search 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 sfdisk to check input" +msgstr "" + +#: en_US/style.xml:1895(para) +msgid "" +"The sfdisk command accepts a script file as standard " +"input to set up partitions on a hard disk. Sometimes sfdisk 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 sfdisk -n 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 sfdisk -n command to check your input file " +"before writing to the disk." +msgstr "" + +#: en_US/style.xml:1910(para) +msgid "" +"The sfdisk command accepts a script file as standard " +"input to set up partitions on a hard disk. Sometimes sfdisk will simply reject an erroneous input file. In other cases, it will " +"use the input verbatim, writing an incorrect partition table to your disk. " +"" +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 replaceable 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 replaceable " +"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 common/ folder in the " +"fedora-docs distribution. (Refer also to .) For instance, do not use abbreviations such as " +"\"FC2.\" Instead, use the predefined entities \"&FC; &FCVER;,\" " +"which produces the text \"Fedora Core 6.\"" +msgstr "" + +#: en_US/writing-guidelines.xml:11(title) +msgid "Fedora Documentation Guidelines" +msgstr "" + +#: en_US/writing-guidelines.xml:14(primary) +#: en_US/writing-guidelines.xml:15(see) +msgid "recursion" +msgstr "" + +#: en_US/writing-guidelines.xml:19(primary) +#: en_US/writing-guidelines.xml:26(secondary) +msgid "RTFM" +msgstr "" + +#: en_US/writing-guidelines.xml:20(secondary) +msgid "read the fine manual" +msgstr "" + +#: en_US/writing-guidelines.xml:21(seealso) +#: en_US/writing-guidelines.xml:25(primary) +msgid "humor" +msgstr "" + +#: en_US/writing-guidelines.xml:29(para) +#, fuzzy +msgid "" +"Please read this chapter carefully. This chapter describes the guidelines " +"that must be followed such as naming conventions." +msgstr "" +"请仔细阅读这一章。这一章描述了 Docs Project 使用的标记。一些规则是 Docs " +"Project 特定的。" + +#: en_US/writing-guidelines.xml: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) +#, fuzzy +msgid "The following general rules apply to IDs:" +msgstr "translator-credits" + +#: 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 "" +" 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 "" + +#: 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 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/writing-guidelines.xml:159(para) +msgid "" +"Instead, use the trademark tag and its associates classes " +"as follows:" +msgstr "" + +#: en_US/writing-guidelines.xml:186(para) +msgid "" +"In general, use para 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 para tags around the following " +"(or, to put this another way, do not embed the following within para elements):" +msgstr "" + +#: en_US/writing-guidelines.xml:216(term) +msgid "" +"Content inside para elements within " +"listitem tags" +msgstr "" + +#: en_US/writing-guidelines.xml:219(para) +msgid "" +"Content inside para elements within " +"listitem elements must start immediately after the beginning para 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 "" + +#: en_US/writing-guidelines.xml:272(secondary) +#: en_US/writing-guidelines.xml:299(tertiary) +#: en_US/writing-guidelines.xml:347(secondary) +#, fuzzy +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) +#, fuzzy +msgid "important" +msgstr "注意" + +#: en_US/writing-guidelines.xml:320(para) +msgid "" +"There are five types of admonitions in DocBook: caution, important, " +"note, tip, and warning. All of the " +"admonitions have the same structure: an optional title followed by paragraph-level elements. The DocBook DTD " +"does not impose any specific semantics on the individual admonitions. For " +"example, DocBook does not mandate that a warning is reserved for cases where bodily harm can result." +msgstr "" + +#: en_US/writing-guidelines.xml:334(title) +msgid "" +"Creating a note, tip, caution, " +"important, or warning" +msgstr "" + +#: en_US/writing-guidelines.xml:365(para) +msgid "" +"There are several ways to bring attention to text within a document. A " +"note is used to " +"bring additional information to the users' attention. A tip is used to show the user helpful " +"information or another way to do something. A caution is used to show the user they must " +"be careful when attempting a certain step. An important 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 warning 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 rely on text over graphics. " +"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 Preferences, " +"Theme and select Bluecurve 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 " +"Preferences, Fonts. Set the " +"Application font and the Desktop font to Sans Regular 10. Set the Window Title font " +"to Sans Bold 10. Set the Terminal font 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 " +"AltPrint Screen to " +"capture a single GUI window. For capturing the entire desktop use " +"Print Screen. If you are taking a shot of multiple elements " +"and have grouped them closely together, you can crop the resulting image in " +"The GIMP. 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 The GIMP. " +"With the image open, right-click on it and choose Image -" +"> Scale Image.... With the chain symbol " +"intact, set the New Width to 500 px, and click OK. Be sure to " +"Ctrls 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 The GIMP, right-click on " +"the image, selecting File -> Save As.... Under Determine File Type:, select " +"PostScript, then click OK. " +"Allow flattening of the image by clicking Export." +msgstr "" + +#: en_US/writing-guidelines.xml:541(para) +msgid "" +"In the Save as PostScript window, select " +"Encapsulated PostScript, and click OK." +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 screen to demonstrate a " +"procedure, use userinput tags to show " +"what the user types, and use computeroutput tags to show the resulting output." +msgstr "" + +#: en_US/writing-guidelines.xml:585(para) +msgid "" +" 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 "" +" shows a directory tree of an example " +"module, excluding any CVS 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 "" + +#: 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:156(systemitem) +msgid "en_US" +msgstr "" + +#: 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 (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 ." +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 directory is an optional directory where graphics for " +"the document should be stored. If graphics are screenshots that are " +"particular to a language, the 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:163(filename) +msgid "po/" +msgstr "" + +#: en_US/module-struct.xml:79(seg) +msgid "" +"The 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 controls the build process. Its content is discussed in " +"." +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 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 " +"HTML or PDF, using make(1) and shell scripts. Authors need no prior " +"experience with either shell scripts or a make(1)." +msgstr "" + +#: en_US/module-struct.xml:111(title) +#, fuzzy +msgid "The Document Makefile" +msgstr "设置 .vimrc 文件" + +#: en_US/module-struct.xml:112(para) +msgid "" +"Each individual document has its own Makefile, which " +"only needs to be a few lines long. The document Makefile content is designed for cut and paste operations." +msgstr "" + +#: en_US/module-struct.xml:118(para) +msgid "" +" below shows the whole Makefile 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:137(para) +msgid "" +"Do not be concerned with some of the more complicated syntax such as the " +"XMLFILES_template stanza. An explanation for this " +"template appears a few paragraphs below." +msgstr "" + +#: en_US/module-struct.xml:143(title) +msgid "Makefile Variables" +msgstr "" + +#: en_US/module-struct.xml:144(segtitle) +msgid "Variable" +msgstr "" + +#: en_US/module-struct.xml:145(segtitle) en_US/module-struct.xml:259(segtitle) +msgid "Explanation" +msgstr "" + +#: en_US/module-struct.xml:147(systemitem) +msgid "DOCBASE" +msgstr "" + +#: en_US/module-struct.xml:148(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:153(systemitem) +msgid "PRI_LANG" +msgstr "" + +#: en_US/module-struct.xml:154(seg) +msgid "" +"This variable contains the ISO code for the original version of the " +"document, such as ." +msgstr "" + +#: en_US/module-struct.xml:159(systemitem) +msgid "OTHERS" +msgstr "" + +#: en_US/module-struct.xml:160(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 " +" directory and a PO file for any indicated additional " +"languages." +msgstr "" + +#: en_US/module-struct.xml:167(systemitem) +msgid "DOC_ENTITIES" +msgstr "" + +#: en_US/module-struct.xml:168(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:177(systemitem) +msgid "XMLFILES_template" +msgstr "" + +#: en_US/module-struct.xml:180(systemitem) +msgid "${1}" +msgstr "" + +#: en_US/module-struct.xml:185(systemitem) +msgid "${1}/" +msgstr "" + +#: en_US/module-struct.xml:178(seg) +msgid "" +"This template allows the build tools to work with the document in multiple " +"languages once it is translated. The 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 , in place of the " +"language code directory name, to each filename in your document." +msgstr "" + +#: en_US/module-struct.xml:191(title) +msgid "Files Exempt From Listing" +msgstr "" + +#: en_US/module-struct.xml:192(para) +msgid "" +"Do not include the document-specific entities XML file or the rpm-" +"info.xml file, which will be discussed later in this guide." +msgstr "" + +#: en_US/module-struct.xml:196(para) +msgid "" +"The final line, beginning with include, references the " +"main Makefile for the build system. This " +"Makefile.common file contains all the make" +"(1) targets and rules to actually build the document and the " +"various archives." +msgstr "" + +#: en_US/module-struct.xml:205(title) +msgid "The Document rpm-info.xml" +msgstr "" + +#: en_US/module-struct.xml:206(para) +msgid "" +"Each document module's primary language directory contains a file called " +"rpm-info.xml. 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:212(para) +msgid " illustrates the content of this file:" +msgstr "" + +#: en_US/module-struct.xml:215(title) +#, fuzzy +msgid "Example rpm-info.xml File" +msgstr ".emacs" + +#: en_US/module-struct.xml:244(para) +msgid "" +"If you are not familiar with XML editing, copy and paste this file from an " +"existing module and then edit the values for the various elements as " +"appropriate. Consult Fedora Documentation Project members and help channels " +"for more assistance if needed." +msgstr "" + +#: en_US/module-struct.xml:251(title) +msgid "Build System Actions" +msgstr "" + +#: en_US/module-struct.xml:252(para) +msgid "" +"To render the XML document into another format, use one of " +"the following make targets:" +msgstr "" + +#: en_US/module-struct.xml:257(title) +msgid "Build Targets" +msgstr "" + +#: en_US/module-struct.xml:258(segtitle) +msgid "Target" +msgstr "" + +#: en_US/module-struct.xml:261(systemitem) +msgid "html" +msgstr "" + +#: en_US/module-struct.xml:262(abbrev) en_US/module-struct.xml:273(abbrev) +#: en_US/module-struct.xml:298(abbrev) en_US/module-struct.xml:303(abbrev) +msgid "HTML" +msgstr "" + +#: en_US/module-struct.xml:266(systemitem) +#: en_US/module-struct.xml:276(systemitem) +msgid "${DOCBASE}" +msgstr "" + +#: en_US/module-struct.xml:267(systemitem) +#: en_US/module-struct.xml:277(systemitem) +msgid "${LANG}" +msgstr "" + +#: en_US/module-struct.xml:265(filename) +msgid "-/" +msgstr "" + +#: en_US/module-struct.xml:262(seg) +msgid "" +"This target builds the \"chunked\" document for each " +"defined translation. Output is placed in a separate directory named " +". Each document section is a separate file within that " +"directory." +msgstr "" + +#: en_US/module-struct.xml:272(systemitem) +msgid "html-nochunks" +msgstr "" + +#: en_US/module-struct.xml:275(filename) +msgid "-.html" +msgstr "" + +#: en_US/module-struct.xml:273(seg) +msgid "" +"This target builds the \"non-chunked\" document for each " +"defined translation. Output is placed in a single file: ; no " +"other files are created." +msgstr "" + +#: en_US/module-struct.xml:281(systemitem) +msgid "pdf" +msgstr "" + +#: en_US/module-struct.xml:282(abbrev) en_US/module-struct.xml:283(abbrev) +#: en_US/module-struct.xml:299(abbrev) en_US/module-struct.xml:304(abbrev) +msgid "PDF" +msgstr "" + +#: en_US/module-struct.xml:282(seg) +msgid "" +"This target builds only the document for all document " +"languages. production is currently erratic and may not work " +"for your document." +msgstr "" + +#: en_US/module-struct.xml:287(systemitem) +msgid "tarball" +msgstr "" + +#: en_US/module-struct.xml:288(command) +msgid "tar(1)" +msgstr "" + +#: en_US/module-struct.xml:288(seg) +msgid "" +"This target builds only the archive for all document " +"languages." +msgstr "" + +#: en_US/module-struct.xml:292(systemitem) +msgid "all" +msgstr "" + +#: en_US/module-struct.xml:293(seg) +msgid "This target builds all targets listed above." +msgstr "" + +#: en_US/module-struct.xml:296(systemitem) +#: en_US/module-struct.xml:305(filename) +msgid "clean" +msgstr "" + +#: en_US/module-struct.xml:298(emphasis) +msgid "not" +msgstr "" + +#: en_US/module-struct.xml:297(seg) +msgid "" +"This target deletes any temporary, or generated files, but does erase any , , or archive files." +msgstr "" + +#: en_US/module-struct.xml:302(systemitem) +msgid "distclean" +msgstr "" + +#: en_US/module-struct.xml:303(seg) +msgid "" +"This target erases all , , and archive " +"files. This target automatically invokes the target as well." +msgstr "" + +#: en_US/module-struct.xml:310(title) +msgid "Adding or Changing Targets" +msgstr "" + +#: en_US/module-struct.xml:311(para) +msgid "" +"To add a new target and rules, place them at the bottom of the document " +"Makefile, below the include 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:319(para) +msgid "" +"For more information on using make(1), consult the online " +"documentation with the command info make in a terminal." +msgstr "" + +#: en_US/module-struct.xml:326(title) +msgid "Using Document Image Files" +msgstr "" + +#: en_US/module-struct.xml:327(para) +msgid "" +"Tutorial documents often make use of images such as .PNG files. Store image files in a figs/ folder in the main module directory, as shown " +"in ." +msgstr "" + +#: en_US/module-struct.xml:334(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 " +".PNG images. Avoid .JPG files. The convert(1) " +"program, from the ImageMagickRPM package, provides a convenient way to reformat .JPG images into ." +"PNG format. For more information on formatting images such as " +"screenshots, refer to ." +msgstr "" + +#: en_US/module-struct.xml:348(para) +msgid "" +"Image files may be organized into subdirectories under figs/ if necessary. The document building system recreates the image " +"subdirectory structure in the output documents." +msgstr "" + +#: en_US/module-struct.xml:354(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 " +"menu-en_US.png. Language-independent images, such as " +"icon.png, do not need language codes." +msgstr "" + +#: en_US/module-struct.xml:364(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 " +"figs/Manifest-${LANG} so the build system finds it when searching for image filenames." +msgstr "" + +#: en_US/module-struct.xml:373(para) +msgid "" +" demonstrates one " +"way to create this Manifest file." +msgstr "" + +#: en_US/module-struct.xml:379(title) +msgid "Building A Manifest" +msgstr "" + +#: en_US/module-struct.xml:386(title) +msgid "Adding a New DocBook XML File" +msgstr "" + +#: en_US/module-struct.xml:387(para) +msgid "" +"To add a new DocBook XML file to an existing document, follow these steps:" +msgstr "" + +#: en_US/module-struct.xml:391(para) +msgid "Place the new DocBook XML file in the primary language directory." +msgstr "" + +#: en_US/module-struct.xml:395(para) +msgid "" +"Edit the Makefile and add the filename to the " +"XMLFILES-${1} listing. Append a \\ to " +"the last existing line, and on the next line add an entry for the new file. " +"Remember to add the ${1}/ prefix as a substitute for the " +"language directory name." +msgstr "" + +#: en_US/module-struct.xml:405(title) +msgid "Adding a Translation" +msgstr "" + +#: en_US/module-struct.xml:406(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:413(para) +msgid "" +"If the po/ directory does not " +"exist, create it and add it to CVS:" +msgstr "" + +#: en_US/module-struct.xml:419(para) +msgid "If it does not exist, create the POT file:" +msgstr "" + +#: en_US/module-struct.xml:423(para) +msgid "" +"Add the new translation language to the OTHERS listing in " +"the Makefile." +msgstr "" + +#: en_US/module-struct.xml:428(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:431(replaceable) +msgid "lang" +msgstr "" + +#: en_US/module-struct.xml:431(screen) +#, no-wrap +msgid "make po/.po" +msgstr "" + +#: en_US/intro.xml:13(title) +msgid "Introduction" +msgstr "介绍" + +#: en_US/intro.xml:15(para) +msgid "" +"The goal of the Fedora Documentation Project is to create easy-to-follow, " +"task-based documentation for Fedora users and developers. Other than the " +"Installation Guide, each tutorial should be in " +"DocBook XML article format, with one article per topic. This way, writers " +"can contribute documentation about a specific topic without having to worry " +"about how it fits into a manual or how it flows with other topics." +msgstr "Docs Project 的目标是为 DocBook XML v4.1 xmlto) Emacs PSGML Emacs nXML" + +#: en_US/intro.xml:25(para) +msgid "The following tools are used:" +msgstr "translator-credits" + +#: 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 xmlto)" +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 "" +"在操作 xmlto docbook-style-xsl docbook-dtds DocBook DTD rpm -q xmlto rpm -q " +"docbook-style-xsl rpm -q docbook-dtds yum(8) su -c 'yum install xmlto' su -c " +"'yum install docbook-style-xsl' su -c 'yum install docbook-dtds' Fedora cvs." +"fedora.redhat.com CVS Enter mkdir my-fedora-docs-sandbox cd my-fedora-docs-" +"sandbox export CVSROOT=:pserver:anonymous@cvs.fedora.redhat.com:/cvs/docs " +"cvs login cvs co docs-common cvs co example-tutorial XML HTML PDF RPM docs-" +"common cvs co -c ISO US(mydoc-en.xmlmydoc-zh_CN.xml I18N - -) ${LANG} " +"${LANG} ${LANG} locale( ${LANG} UTF-8 mydoc-it.xml it.UTF-8 I18N HTML PDF " +"make(1) Makefile MakefileMakefile n Makefile DOCBASE = mydoc LANGUAGES = en " +"XMLEXTRAFILES-en= include ../docs-common/Makefile.common XML mydoc-en.xml " +"LANGUAGES en mydoc-en.xmlXMLEXTRAFILES-en include(MakefileMakefile.common " +"make(1) ${LANG} Makefile${LANG} LANGUAGES XMLEXTRAFILES-${LANG} XML HTML " +"PDFmake html, make html-nochunk, make pdf all HTML, PDF tar(1) rpm(8) " +"tarball tar(1) pdf PDF PDF html HTML ${DOCBASE}-${LANG}/ html-nochunks HTML " +"${DOCBASE}-${LANG}.html clean HTML, PDF, distclean HTML, PDF, clean Makefile " +"include .PNGfigs/ picture.png mydoc/figs/picture.png PNG JPG convert(1) " +"ImageMagickRPM JPG figs/ words-en.png words-ru.png picture.png figs/Manifest-" +"${LANG} figs/Manifest-${LANG} rm -f figs/Manifest-en find figs -print /tmp/" +"manifest mv /tmp/manifest figs/Manifest-en vi figs/Manifest-en" + +#: en_US/getting-files.xml:20(title) +msgid "System Packages" +msgstr "translator-credits" + +#: en_US/getting-files.xml:22(para) +msgid "" +"Install the \"Authoring and Publishing\" package group, which contains " +"required DocBook XML files, stylesheets and scripts:" +msgstr "" + +#: en_US/getting-files.xml:28(userinput) +#, no-wrap +msgid "su -c 'yum groupinstall \"Authoring and Publishing\"'" +msgstr "" + +#: en_US/getting-files.xml:31(para) +msgid "" +"Next, install the cvs 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 cvs.fedoraproject.org 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 "" + +#: en_US/getting-files.xml:53(userinput) +#, no-wrap +msgid "" +"mkdir \n" +"cd \n" +"export CVSROOT=:ext:@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 Enter 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 ." +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 XML documents into other " +"output formats such as HTML. In addition, these tools can " +"build your document into a RPM 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 docs-common directory you extracted from the Fedora archive earlier. On the " +"CVS server, these directories are called modules. Use " +"the cvs co -c 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 Fedora to name modules in the " +"Fedora Documentation Project CVS repository." +msgstr "" + +#: en_US/emacs.xml:13(title) +msgid "Emacs and PSGML Mode" +msgstr "Emacs 与 PSGML 模式" + +#: en_US/emacs.xml:16(primary) +msgid "PSGML" +msgstr "PSGML" + +#: en_US/emacs.xml:20(primary) en_US/emacs.xml:24(primary) +#: en_US/emacs.xml:43(primary) en_US/emacs.xml: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 "PSGML 模式" + +#: en_US/emacs.xml:28(para) +msgid "" +"You can use the PSGML mode available for Emacs to make it easier to write in " +"XML format. PSGML mode provides syntax-highlighting, tag completion, and " +"more." +msgstr "" +"您可以利用 Emacs 的 PSGML 模式以使编辑 XML 格式更容易。PSGML 模式提供了语法高" +"亮，标记补全等功能。" + +#: en_US/emacs.xml:35(title) +msgid "Installing PSGML" +msgstr "设置您的 .emacs" + +#: en_US/emacs.xml:36(para) +msgid "To install PSGML, use the yum command:" +msgstr "Emacs" + +#: en_US/emacs.xml:37(userinput) +#, no-wrap +msgid "yum install psgml" +msgstr "配置文件" + +#: en_US/emacs.xml:40(title) +msgid "Setting Up Your .emacs File" +msgstr ".emacs" + +#: en_US/emacs.xml:48(filename) +msgid ".emacs" +msgstr "" + +#: en_US/emacs.xml:51(para) +msgid "" +"For Emacs to parse your DocBook documents correctly, you must have a " +".emacs file. Cut and paste the following into your " +"existing .emacs file or create a new one that contains " +"the following lines: " +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 .emacs file so your wheel will work " +"in Emacs:" +msgstr "" + +#: en_US/emacs.xml:198(para) +msgid "" +"If you are using the older version 20 of Emacs, " +"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 " +"~/.Xresources file. The format for the settings is " +"emacs.keyword:value" +msgstr "" + +#: en_US/emacs.xml:261(para) +msgid "The following is a sample ~/.Xresources file." +msgstr "" + +#: en_US/emacs.xml:266(para) +msgid "" +"If you have other settings in your ~/.Xresources, 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 Emacs 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 <!DOCTYPE article PUBLIC \"-//OASIS//DTD " +"DocBook V4.1//EN\". An easy way to find this parent file is to " +"use the command grep DocBook *.xml. Once you find the " +"parent file, open it in Emacs with the command emacs " +"<parentfile>.xml (where " +"<parentfile>.xml is the parent file you " +"found." +msgstr "" + +#: en_US/emacs.xml:321(para) +msgid "Choose DTD -> Parse DTD from the pulldown menu." +msgstr "" + +#: en_US/emacs.xml:327(para) +msgid "" +"You will know the parsing is finished when you see the message " +"Fontifying...done at the bottom of your " +"screen. Save the parsed DTD to a file by choosing DTD -> Save " +"Parsed DTD from the pulldown menu." +msgstr "" + +#: en_US/emacs.xml:335(para) +msgid "" +"Press Enter to save the file to the default filename or " +"rename the file keeping the .ced extension. It can be " +"useful to name it something generic such as docbook.ced " +"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: " +msgstr "" + +#: en_US/emacs.xml:349(para) +msgid "" +"You can also use the Emacs command Meta-x sgml-parse-prolog to parse the file, and then use the command Meta-x sgml-" +"save-dtd to save the parsed DTD to a .ced " +"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 .ced file and see the syntax highlighting for your .sgml files." +msgstr "" + +#: en_US/emacs.xml:372(para) +msgid "Open an XML file in Emacs." +msgstr "" + +#: en_US/emacs.xml:377(para) +msgid "" +"Choose DTD -> Load DTD from the pulldown menu and " +"choose the file you saved from the previous step. For instance, choose " +"docbook.ced." +msgstr "" + +#: en_US/emacs.xml:384(para) +msgid "" +"You will know it is finished when you see the message " +"Fontifying...done 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: " +msgstr "" + +#: en_US/emacs.xml:397(para) +msgid "" +"You can also use the Emacs command Meta-x sgml-load-dtd " +"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 Meta key is usually the Alt 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 "" +" sgml-parse-prolog, " +"" +msgstr "" + +#: en_US/emacs.xml:420(seg) +msgid "Parse DTD" +msgstr "" + +#: en_US/emacs.xml:423(seg) +msgid "" +"sgml-save-dtd, " +"" +msgstr "" + +#: en_US/emacs.xml:425(seg) +msgid "Save the Parse DTD" +msgstr "" + +#: en_US/emacs.xml:428(seg) +msgid "" +"sgml-load-dtd, " +"" +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 "" + +#: 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 "" + +#: en_US/emacs.xml:435(keycap) en_US/emacs.xml:442(keycap) +msgid "Tab" +msgstr "" + +#: en_US/emacs.xml:433(seg) +msgid "" +", " +", " +msgstr "" + +#: en_US/emacs.xml:436(seg) +msgid "Display list of valid tags" +msgstr "" + +#: en_US/emacs.xml:439(seg) +msgid "" +", " +", type beginning of tag, " +"" +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 ", " +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 "" + +#: 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 "" +" ispell-word, " +"" +msgstr "" + +#: en_US/emacs.xml:506(seg) +msgid "" +" ispell-buffer, " +"" +msgstr "" + +#: en_US/emacs.xml:508(seg) +msgid "Check spelling of current buffer" +msgstr "" + +#: en_US/emacs.xml:512(keycap) +msgid "f" +msgstr "" + +#: 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 "" +", " +"" +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 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 " +"attribute of the 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 (." +"ced)." +msgstr "" + +#: en_US/emacs.xml:571(para) +msgid "" +"Instead of typing a tag each time you need to use it, use the key " +"combination Ctrl-c, followed by " +"<. At the bottom of the Emacs " +"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 Tab or " +"?. Or, if you know the first few letters of a tag, you can " +"enter them followed by Tab 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 Ctrl-c followed by " +"<. Then enter the letter k, followed by " +"Tab. You may have to use the Tab 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 Ctrl-c, followed by /. 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 "" +"Working with one window: Sometimes in " +"Emacs 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 Ctrl-x, followed by 1." +msgstr "" + +#: en_US/emacs.xml:636(para) +msgid "" +"Saving your work: To save your work, use the following " +"keycombo, Ctrl-x followed by Ctrl-s." +msgstr "" + +#: en_US/emacs.xml:642(para) +msgid "" +"The \"clear/quit\" command: 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 Ctrl-g. This command quits what " +"you have been doing within the file, without quitting the file itself." +msgstr "" + +#: en_US/emacs.xml:651(para) +msgid "" +"Opening a new file: To open a new file, use the " +"keycombo Ctrl-x followed by Ctrl-f. At the bottom of the emacs window, you will be " +"able to enter in the file name (using Tab completion if " +"needed) of the file you wish to open." +msgstr "" + +#: en_US/emacs.xml:660(para) +msgid "" +"Closing emacs: The easiest way to close " +"emacs is to use the keycombo Ctrl-x followed by Ctrl-c. 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 "其他资源" + +#: 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 emacs package. " +"You can print it out as a reference. —/usr/share/emacs/" +"<version>/etc/refcard.ps" +msgstr "" + +#: en_US/emacs.xml:693(para) +msgid "" +"Read Editing XML with Emacs and PSGML in /" +"usr/share/doc/psgml-<version>/psgml.ps." +msgstr "" + +#: en_US/emacs.xml:697(para) +msgid "" +"http://www." +"snee.com/bob/sgmlfree/psgmqref.html—Emacs/PSGML " +"Quick Reference 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 "Emacs 与 nXML 模式" + +#: en_US/emacs-nxml.xml:14(primary) en_US/emacs-nxml.xml:51(primary) +msgid "nXML" +msgstr "nXML" + +#: en_US/emacs-nxml.xml:23(secondary) +msgid "nXML mode" +msgstr "nXML 模式" + +#: en_US/emacs-nxml.xml:26(para) +msgid "" +"You can also use the nXML mode available for Emacs 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 "" +"您可以使用 Emacs 的 nXML 模式，使撰写 DocBook XML " +"格式更加简单。nXML 模式提供了上下文敏感的编辑模式，包括补全、实时的有效性检" +"测、语法高亮和缩进。为此您只要安装一个 RPM 软件包！" + +#: en_US/emacs-nxml.xml:35(title) +msgid "Early stages" +msgstr "开发早期" + +#: en_US/emacs-nxml.xml:36(para) +msgid "" +"Please be aware the nxml-mode for Emacs 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 ." +msgstr "" +"需要注意的是，Emacs 的 nXML 模式尚不完善，因此在编" +"辑一些文档时，高级用户可能会注意到一些问题。如果您略微关注一下邮件列表，就可" +"以获得相关信息，也可以问问题。请参考 。" + +#: en_US/emacs-nxml.xml:48(title) +msgid "Getting the nXML RPM" +msgstr "下载 nXML RPM" + +#: en_US/emacs-nxml.xml:52(secondary) +msgid "RPM" +msgstr "RPM" + +#: en_US/emacs-nxml.xml:56(primary) +msgid "nXML RPM" +msgstr "nXML RPM" + +#: en_US/emacs-nxml.xml:59(para) +msgid "" +"To use nXML mode with emacs, you will need to install the nXML RPM available " +"from Tim Waugh's website or the source from http://www.thaiopensource.com/download/. The source requires a lot more work to setup, therefore we will only " +"be concentrating on the RPM version." +msgstr "" +"要在 emacs 中使用 nXML 模式，您需要安装 Tim Waugh 网站上的 nXML RPM，或" +"者下载 http://www." +"thaiopensource.com/download/ 的源代码。源代码需要花工夫来配置，因此这" +"里只考虑 RPM 版本。" + +#: en_US/emacs-nxml.xml:69(para) +msgid "" +"Information on where to get the source is available in ." +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 Emacs considerably, which " +"means you can concentrate more on the content of your article." +msgstr "" +"与 PSGML 模式相比，您只需有数几个命令。这样使用 Emacs 编辑就快捷多了，您可以更多地关注文章的内容。" + +#: en_US/emacs-nxml.xml:88(para) +msgid "" +"To create a tag, type < and then type the keyword. " +"To complete the keyword, press Ctrl-Ret, then add the " +"last >. To close a tag, type </." +msgstr "" +"要创建一个标记，输入 < 然后输入关键字。要完成这个关" +"键字，按下 Ctrl-Ret，然后添加随后的 >。要关闭一个标记，输入 </。" + +#: en_US/emacs-nxml.xml:97(para) +msgid "" +"When you open a document that doesn't have a DOCTYPE declaration at the top " +"of the file, you will get this message and tag completion won't work because " +"nXML will not know what format you are writing." +msgstr "" +"当您打开不包含首部 DOCTYPE 声明的文件时，将看到如下信息，标记补全也无法实现，" +"因为 nXML 不知道您在编辑的文件格式。" + +#: en_US/emacs-nxml.xml:104(para) +msgid "" +"To load the schema, type Ctrl-c, then Ctrl-s and navigate to /usr/share/emacs/site-lisp/nxml-mode/" +"schema/ and load docbook.rnc. " +"Emacs will then prompt you to save it in the " +"current working directory." +msgstr "" +"要加载 schema，按下 Ctrl-c，然后按 Ctrl-s 然后浏览 /usr/share/emacs/site-lisp/nxml-mode/schema/ 并加载 docbook.rnc。Emacs 将提示您将它保存到工作目录。" + +#: en_US/emacs-nxml.xml:115(para) +msgid "" +"The commands already discussed are the only differences between using " +"Emacs with PSGML mode and Emacs with nXML mode. You will still need to use all the same " +"commands as discussed in ." +msgstr "" +"已描述过的命令只是 Emacs PSGML 模式与 " +"Emacs nXML 模式的不同之处。您仍然需要使用 中描述的命令。" + +#: en_US/emacs-nxml.xml:129(para) +msgid "" +"Additional Emacs and nXML references are available at the following " +"locations:" +msgstr "其他的 Emacs 与 nXML 帮助可以在下列位置找到：" + +#: en_US/emacs-nxml.xml:136(ulink) +msgid "http://www.thaiopensource.com/download/" +msgstr "" +"http://www." +"thaiopensource.com/download/ Author's download area http://wks.uts." +"ohio-state.edu/unix_course/intro-135.html Emacs Quick Reference Guide emacs /" +"usr/share/emacs/version/etc/refcard.ps nXML README /usr/share/doc/nxml-mode-" +"version/ README M-x load-file RET rng-auto.el RET M-x nxml-mode C-h m C-u M-" +"x info RET nxml-mode.info RET C-h i test.valid.xml test.invalid.xml .emacs " +"(load \"~/nxml-mode-200YMMDD/rng-auto.el\") ~/nxml-mode-200YMMDD .elc rng-" +"auto.el rng-auto.el xml, xsl, rng xhtml .emacs (setq auto-mode-alist (cons " +"'(\"\\\\.\\\\(xml\\\\|xsl\\\\|rng\\\\|xhtml\\\\)\\\\'\" . nxml-mode) auto-" +"mode-alist)) .emacs (unify-8859-on-decoding-mode) http://relaxng.org/ http://" +"relaxng.org/compact-tutorial.html http://eee.thaiopensource.com/relaxng/" +"trang.html\" http://www.pantor.com/download.html\" https://www.dev.java.net/ " +"NEWS http://groups.yahoo.com/group/emacs-nxml-mode James Clark " +"jjc@thaiopensource.com" + +#: en_US/emacs-nxml.xml:137(citetitle) +msgid "Author's download area" +msgstr "translator-credits" + +#: en_US/emacs-nxml.xml: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 " +"/usr/share/doc/nxml-mode-<version>/ 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 C-h i as usual." +msgstr "" + +#: en_US/emacs-nxml.xml:217(para) +msgid "" +"You can use test.valid.xml and test.invalid." +"xml 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 .emacs, where ~/nxml-mode-" +"200YMMDD is the directory containing the .elc files. Note that rng-auto.el 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 " +"rng-auto.el itself." +msgstr "" + +#: en_US/emacs-nxml.xml:242(para) +msgid "" +"To use nxml-mode automatically for files with an extension of xml, xsl, rng or " +"xhtml, add the following to your .emacs 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 .emacs " +"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 http://" +"relaxng.org/." +msgstr "" + +#: en_US/emacs-nxml.xml:277(para) +msgid "" +"For a tutorial on RELAX NG Compact Syntax, refer to http://relaxng.org/compact-tutorial." +"html" +msgstr "" + +#: en_US/emacs-nxml.xml:282(para) +msgid "" +"For automatically creating RNC schemas, I recommend my Trang program: http://eee." +"thaiopensource.com/relaxng/trang.html\"" +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 " +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 http://www.pantor.com/download.html\"." +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 https://www." +"dev.java.net/." +msgstr "" + +#: en_US/emacs-nxml.xml:323(para) +msgid "The file NEWS describes recent changes." +msgstr "" + +#: en_US/emacs-nxml.xml:327(para) +msgid "" +"Please use the list http://groups.yahoo.com/group/emacs-nxml-mode for bug " +"reports, discussion. I will announce all new versions there." +msgstr "" + +#: en_US/emacs-nxml.xml:333(para) +msgid "James Clark" +msgstr "" + +#: en_US/emacs-nxml.xml:336(para) +msgid "jjc@thaiopensource.com" +msgstr "" + +#: en_US/acknowledgments.xml:11(title) +msgid "Acknowledgments" +msgstr "致谢" + +#: en_US/acknowledgments.xml:13(para) +msgid "" +"This document is based on 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 "" +"本文档基于 Tammy Fox (tfox at redhat.com) 起草的一篇文档，并得到了 Sandra " +"Moore (smoore at redhat.com) 和 Johnray Fuller (jrfuller at redhat.com) 的协" +"助。" + +#: en_US/acknowledgments.xml:19(para) +msgid "" +"A patch from Roozbeh Pournader (roozbeh at sharif.edu) has been applied to " +"fix a few typos and explain that anonymous CVS access does not allow commits." +msgstr "" +"Roozbeh Pournader (roozbeh at sharif.edu) 的补丁已被合并，修正了一些拼写错" +"误，解释了匿名 CVS 访问时禁止提交的情况。" + +#: en_US/acknowledgments.xml:25(para) +msgid "" +"Patches from Gavin Henry (ghenry at suretecsystems.com) have been applied to " +"add the trailing slashes to the figure tag example in " +"docs-xml-tags.xml." +msgstr "" +"Gavin Henry (ghenry at suretecsystems.com) 的补丁已被合并，向 docs-" +"xml-tags.xml 中的 figure 标记范例添加尾部斜线，" +"以及添加 。" + +#: en_US/acknowledgments.xml:32(para) +msgid "" +"A patch from Joshua Daniel Franklin (joshuadfranklin at yahoo.com) has been " +"applied to add ." +msgstr "" +"Joshua Daniel Franklin (joshuadfranklin at yahoo.com) 的补丁已被合并，添加 " +"。" + +#: en_US/acknowledgments.xml:37(para) +msgid "" +"A patch from Karsten Wade (kwade at redhat.com) has been applied to add " +". It was edited by Paul W. Frields " +"(stickstr5 at hotmail.com)." +msgstr "" +"Karsten Wade (kwade at redhat.com) 的补丁已被合并，添加 。它为 Paul W. Frields (stickstr5 at hotmail.com) 编辑。" + +#: en_US/acknowledgments.xml:43(para) +msgid "" +"A patch from Paul W. Frields (stickstr5 at hotmail.com) has been applied to " +"add more explanation of the screen tag set to ." +msgstr "" +"Paul W. Frields (stickstr5 at hotmail.com) 的补丁已被合并，向 中的 screen 标记集合添加更多解" +"释。" + +#: en_US/acknowledgments.xml:49(para) +msgid "" +"A patch from Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) has been " +"applied to more fully explaing the document building system." +msgstr "" +"合并了 Tommy Reynolds (Tommy.Reynolds at MegaCoder.com) 的补丁，详细解释文档" +"构建系统。" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +#: en_US/acknowledgments.xml:0(None) +msgid "translator-credits" +msgstr "" -- cgit