Zh/DocsProject/Translation

文档项目/翻译

文档翻译人员不再需要' cvsdocs ' 成员的资格（开始一个新的项目时,可能需要' cvsdocs ' 成员的资格） 。请参阅有关如何成为文档项目贡献者和成为' cvsl10n'组成员的说明。另外，请参阅电子邮件翻译清单。请注意，我们的一些向导可能没有更新。

我们强烈建议您参阅快速翻译指南。如果您使用的是Windows ，你仍然可以参加翻译;参阅在 Windows 系统中翻译 Fedora 文档获得更多信息。

简介

这一程序仅适用于翻译 Fedora 的文档项目文件。如果您愿意帮助翻译 Fedora 中的程序 ，请访问 翻译项目页面。

在相关辅助工具完成之前，这只是一个临时的项目。未来的工具将便于使用。到那时，这项工作也是艰巨的。

文档项目的时间表包含所有终止翻译的文档。

如何开始

• Follow the instructions on to become a member of the L10N Project. Once you have a Fedora Account and have become a member of the group 'cvsl10n', you'll be able to contribute translations to Docs. You don't need to be also a member of 'cvsdocs'.

• To checkout a module from CVS:

export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
cvs co docs-common

• A Fedora Core 4 or later system with these packages installed:

gnome-doc-utils    // Provides xml2po
xmlto              // For testing build
make               // For testing build

To install these packages, use the following command:

su -c 'yum install gnome-doc-utils xmlto make'

• Subscriptions to fedora-docs-list , where all announcements and discussions take place, and fedora-docs-commits , so you can collaborate with other translators and toolmakers.

• Patience with the toolmakers as we learn about and build a good translation toolchain.

What to translate

The most important docs modules/directories for each release are the following:

1. docs-common/common/entities 1. release-notes/devel 1. homepage/devel 1. install-guide/devel 1. about-fedora/devel 1. readme/devel 1. readme-burning-isos/devel 1. readme-live-image/devel

To see all documents available in our repo, run:

export CVSROOT=:ext:username@cvs.fedoraproject.org:/cvs/docs
cvs co -c

Translation statistics

See: DocsProject/Translation/Statistics . In general, make postat and make postat-<lang> should work.

Translating Documents Into English

If you have original content in a language other than English, you are welcome to contribute it to Fedora. It must follow the same processes that other contributions follow. You must have an editor who is not one of the writers, and who can read the language well enough to edit for grammar and style. You also may need a technical edit in the native language.

Once you have a document accepted in the native language, follow the DocsProject/WorkFlow#GettingADocumentTranslated usual process to get it translated.

#!html

<!--

== Translation Process for Fedora Docs Project ==

This process covers translating XML-based documentation.  Refer to [[Languages| Languages]]  if you are interested in translating formal, static parts of the Wiki.  You want to join [http://www.redhat.com/mailman/listinfo/fedora-websites-list fedora-websites-list]  for discussions about the Wiki.

1. To list the available modules run these commands:
<pre>
export	CVSROOT=:ext:username@cvs.fedora.redhat.com:/cvs/docs
cvs co -c

To download a module to translate, list the current modules in the repository and then check out that module. You must also check out the docs-common module.

cvs co example-tutorial docs-common

1. OPTIONAL: This step is usually handled by the document author, so you will probably not have to perform it. If you have questions, ask on the fedora-docs-list. If no po/ folder exists, you may need to add one to the CVS repository and create a POT template:

mkdir po
cvs add po/
make pot

1. Change the OTHERS macro in the Makefile to include your translation language:

OTHERS = it pt_BR

1. Make a new PO file for your locale:

make po/it.po

1. Perform your translation using a tool like gtranslator or kbabel on Fedora, or poEdit on Windows, and save the PO file when done.

1. Test your build with the Makefile, try HTML output:

make html-it

1. Commit your translation (PO file only) into CVS. For the message string (-m option), you can use translation statistics or any other appropriate message. Remember these are emailed across the fedora-docs-commits mailing list. It is perfectly acceptable to do additional commits as you add to your translation.

cvs ci -m 'My message about translation' po/it.po

1. DO NOT commit any change to the Makefile until your translation is completely finished and ready for publication. If you have questions, ask on the fedora-docs-list. When your translation is finished, and builds correctly, then commit the Makefile change:

cvs ci -m 'Locale "it" translation finished' Makefile

-->

---