From Fedora Project Wiki

< L10N‎ | Guide
Line 175: Line 175:




== Proofreading Software Translations ==
== 校对软件的译文 ==


Since Fedora 12, the composed live image has been available to download for reviewing and
从Fedora 12开始，尚在制作中的live映像可以提前下载，以便译员在用户界面下审阅和修正软件的译文。该live映像的制作大约会比Fedora软件译文定稿日（Fedora Software Translation Deadline）提前一周时间，直到最后的定稿日当天。该映像应该包含制作时所有已经提交的最新译文。
correcting software translation in user interface. This live image is composed around a week
before Fedora Software Translation Deadline and made available by deadline date. This image
should include all latest translation submitted at this point.


To proofread your translation as part of the software, follow these steps:
要在程序内校对您的译文，请采取如下步骤：


1. Change directory to the package you want to proofread. For example:
1. 更改目录至您要校对的软件包，例如：


   cd ~/myproject/system-config-printer/
   cd ~/myproject/system-config-printer/


2. Convert the po file to a mo file using msgfmt with -o option:
2. 使用msgmft命令，配合-o参数，将po文件转换成mo文件：


  msgfmt -o system-config-printer.mo ja.po
  msgfmt -o system-config-printer.mo ja.po


3. Back up the existing file and overwrite old one.
3. 备份当前文件，并用新文件覆盖之。


  su -
  su -
Line 199: Line 196:
  exit
  exit


4. Proofread the package with the translated strings as part of the application. The application related to the translated package runs with the translated strings.
4. 在程序内校对译文包中已经翻译的字符串，设置程序以翻译后的界面运行。


  LANG=ja_JP.UTF-8 system-config-printer
  LANG=ja_JP.UTF-8 system-config-printer


= 翻译 Fedora 文档 =
= 翻译 Fedora 文档 =

Revision as of 10:58, 19 January 2012

Fedora 本地化工作向导(不断完善中。。。)

简介

这份指南为翻译 Fedora 项目和文档提供一个快捷、简便、带有步骤的指导。您可以在本页面的末尾找到 FAQ。

我们需要反馈！
如果您发现了这份手册里的拼写错误，或者您想到了改进本手册的方法，请直接编辑本页面或者直接向 Fedora 本地化项目的邮件列表发送邮件。如果您有改进文档的建议，请尽可能具体地阐述。如果您发现了错误，请在报告中包含章节编号和部分上下文以使我们能容易地定位。


Fedora 本地化项目的网址为 https://fedora.transifex.net/。

寻求帮助

您可以将问题张贴到 trans 邮件列表，还可以通过因特网中继聊天(IRC)在 irc.freenode.org 上的 #fedora-l10n 房间寻求帮助。

您还可以在 Transifex 上看到许多信息：http://help.transifex.net/。

成为 Fedora 翻译人员

最开始您需要注册以获得翻译材料的访问权限：

  1. 新建一个 Transifex 账户
  2. 订阅邮件列表
  3. 介绍一下自己
  4. 加入与您使用的语言有关的 Fedora 翻译团队

您的自我介绍非常重要。它能提升您被批准拥有写入权限的机会。您可能也想 新建一个 Bugzilla 账户 解决用户报告的 bug。

开始使用 Transifex

Fedora 使用 Transifex 管理本地化工作流程。这些步骤会指导您新建 Transifex 账户并加入翻译团队。

http://fedora.transifex.net/

新建一个 Transifex 账户

  1. 访问 https://fedora.transifex.net/ 并点击右上角的 "Register"
  2. 填写表单点击 Register！您可以使用您的 Fedora 邮箱或者您新建 Fedora 账户时使用的邮箱。选择一个好的密码(如上所述)。不过如果您忘记了的话，密码可以被重置。
  3. 检查您的邮箱。您应该很快能收到一封邮件用于校验您的邮箱地址。其中会有一个链接 — 点击它！
  4. 现在您应该能够用您的资料登录 Transifex 了。

加入与您使用的语言有关的 Fedora 翻译团队

  1. 访问 Fedora 团队页面，它位于 https://www.transifex.net/projects/p/fedora/teams/。
  2. 如果您的语言在里面，点击它。
  3. 您应该能看到成员列表、领导人(协调人)。点击 "Join this team" 以请求加入团队。
  4. 团队领导人将会收到有关您的请求的提醒。他会检查您的信息，检查您是否已经做过自我介绍。
  5. 如果一切顺利，维护者会接受您的申请，您会接到通知。

这可能会花几小时或几天的工夫。如果时间更久，请点击 Transifex 上维护者的用户名，向他发送消息询问更多信息。

订阅邮件列表

  1. 访问 https://admin.fedoraproject.org/mailman/listinfo/trans 并订阅这个主要的翻译邮件列表。
  2. 等待确认邮件，它包括一个链接以确认您的订阅。点击链接确认。

检查 https://fedoraproject.org/wiki/L10N/Teams 看看是否有一个您的语言的专门的邮件列表。如果有，请也订阅那个列表。

介绍一下自己

  1. 在 https://fedoraproject.org/wiki/User:Username 创建一个个人页面。这对 Fedora 贡献人员互相认识并联络非常有用。您需要先 新建一个 Fedora 账户。
  2. 在 https://fedoraproject.org/wiki/L10N_Self_introduction 的指导下向 trans 邮件列表和您本地团队的邮件列表发布一个简短的个人介绍。请记得提及您的 FAS 用户名和您的语言。使用这些信息，您的语言领导人可以识别您并批准您为他的团队的翻译成员。

新建一个Bugzilla账户

If you are asked to use Bugzilla, create an account by visiting https://bugzilla.redhat.com/bugzilla/createaccount.cgi.

新建一个Fedora账户

The steps below guide you through the creation of a Fedora Account.

账户申请流程

  1. To sign up for a Fedora account, first visit https://admin.fedoraproject.org/accounts and select New Account.
  2. Fill in Username, Full Name and Email, and click Sign up!. Your password will be emailed to you.
  3. Go back to https://admin.fedoraproject.org/accounts and log in with your password. The welcome page will be displayed, and it reminds you that CLA is not completed.
  4. Telephone Number and Postal Address fields are also required to fill in for signing the CLA. These information is NOT accessible by others except admin groups. Please refer to Fedora Privacy Policy at https://fedoraproject.org/wiki/Legal:PrivacyPolicy.
  5. Other fields will be displayed by any other member by visiting the user's view page.
  6. Now click Save! located at the bottom of this page to save your information.

签署CLA协议

You must complete the Contributors License Agreement, or CLA.

  1. Visit https://admin.fedoraproject.org/accounts and login your account using your user name and password obtained from the previous process.
  2. In the Welcome page, click complete the CLA or go to https://admin.fedoraproject.org/accounts/user/edit.
  3. If the information of telephone number and postal address have not been provided yet, the Edit Account (user_name) page will be appeared. Otherwise Fedora Contributor License Agreement page will be displayed. Read through the agreement carefully and click I agree if you are happy to do so.
  4. The user-view page is appeared and shows the CLA: field as CLA Done.

开始翻译

The translatable part of a software package is available in one or more PO files. Some projects might use other file formats as well, such as QT TS ones. These files may be maintained in any of a number of version control systems (VCSs) depending on the project, such as Subversion, Mercurial, and git. They may be hosted on either fedorahosted.org or other systems.

This chapter explains how to translate the projects which use Transifex to manage their L10n workflow. Translators can work on the web interface or the command-line to obtain and submit files. Before you start, you must first prepare the directories which hold your po files.

Fedora and Upstream projects
Using Transifex, you can contribute to both Fedora and Upstream projects. Fedora ones are those which Fedora is upstream for, ie. maintaining and handling. These are usually only used by Fedora.

列出所有可被翻译的Fedora子项目

  1. Visit https://www.transifex.net/projects/p/fedora/.
  2. Choose the type of Fedora Projects you want to translate by choosing the appropriate Release. You should see Fedora itself, Fedora Documentation and other upstream projects. Click on the release you choose to contribute to. For example, click on the link pointing to https://www.transifex.net/projects/p/fedora/r/fedora-15/l/ja/.
  3. The new page shows the full statistics for this release per language. Choose your language.
  4. This page shows all translatable resources (ie. files) for this release. Click on one of the table rows to get information on the resource you're interested in.

You can bookmark this page for future reference. We'll call it the "Language-Release" page from now on. Here's an example URL:

https://www.transifex.net/projects/p/fedora/r/fedora-15/l/ja/


image


image


在线翻译

The easiest way to translate is by using the Transifex Web Editor. It's an intuitive interface which does not require you to download files on your system and re-upload them back.

  1. Follow the instructions above to locate the resource which interests you.
  2. On the popup, you should see a "Translate Now" button. If you are logged-in on Transifex and a member of the language team, it should be clickable. Click it!
  3. You should now be in the Transifex Web editor (codenamed Lotte). Go on and translate as much as you want, and at the end, click "Save and Exit".


Note: When you translate online, the file is automatically "Locked" and other people are notified about your work. Never translate something that another translator has already locked -- you might be overwriting his own work!


image


离线翻译

If you prefer to translate offline, you can simply download & upload a translation file.

Before you download any files, we suggest you prepare a directory to hold your files. The described structure below is an example only, and your structure can be formed differently. 

mkdir -p ~/fedora-translations/

Obtaining and Translating Projects

You can download a file to translate. You may need to communicate with other translators in your language team to avoid conflict. If you are not sure, please contact your language coordinator. Also locking a file will avoid potential conflicts.

  1. On your Release-Language page find the resource (table row) you want to translate and click on it for the popup to appear.
  2. Click on "Download for translation" button to download the file as the name of your choice to the directory you created in the previous section (e.g. abrt.po).
  3. Now the file is on your local workstation and ready for translation. Translate the file into your language eg. with a POeditor of your choice such as Lokalize or gtranslator.
  4. Check the integrity of your file before commit using msgfmt -cvo /dev/null abrt.po. If any error messages appear, correct it before commit.

Please note that all files offered from Transifex are already merged (msgmerged) with the POT files. This happens both when you download and when you upload files.


提交您的翻译内容

Once you finish translation work, commit the file using the same interface.

  1. Make sure you are logged in on Transifex.
  2. Navigate back to your Release-Language page and click on the resource you want to upload to. Be careful not to upload on a different resource.
  3. Click on the "Upload" button and locate your translated file on your local system, and Submit it. The interface might take some time (for large files up to one minute) and finally notify you that the file was submitted successfully. If you receive an error or some other message, please post it to the Fedora Localization Project mailing list so it can be addressed.

加入新文件

If one of the resources in the release is missing your translation, you should see it missing from the release page, and see a separate list at the bottom of the page as follows: 

The following resources don't have any translations in Japanese:
1) python-fedora → python-fedora.pot
  1. Click on it -- it will take you to that resource's main page.
  2. Click "Add Translation"
  3. Choose your language and click "Translate Online".
  4. Go ahead and translate online a few or all the strings, and then "Save and Exit".


校对软件的译文

从Fedora 12开始，尚在制作中的live映像可以提前下载，以便译员在用户界面下审阅和修正软件的译文。该live映像的制作大约会比Fedora软件译文定稿日（Fedora Software Translation Deadline）提前一周时间，直到最后的定稿日当天。该映像应该包含制作时所有已经提交的最新译文。

要在程序内校对您的译文，请采取如下步骤：

1. 更改目录至您要校对的软件包，例如： 

 cd ~/myproject/system-config-printer/

2. 使用msgmft命令，配合-o参数，将po文件转换成mo文件： 

msgfmt -o system-config-printer.mo ja.po

3. 备份当前文件，并用新文件覆盖之。 

su -
cp /usr/share/locale/ja/LC_MESSAGES/system-config-printer.mo system-config-printer.mo-backup
mv system-config-printer.mo /usr/share/locale/ja/LC_MESSAGES/
exit

4. 在程序内校对译文包中已经翻译的字符串，设置程序以翻译后的界面运行。 

LANG=ja_JP.UTF-8 system-config-printer

翻译 Fedora 文档

Translating Fedora docs is exactly the same as translating software, so just follow the same instructions as above. Make sure you select the "Fedora Documentation" Release, which will lead you to a separate Release-Language page, specialized in Docs.

Example:

https://fedora.transifex.net/projects/p/fedora/r/fedora-docs/


Understanding the Multiple Files Structure

Fedora Docs mostly use Publican. Unlike software, a guide has multiple po files structure. Each file corresponds to each chapter in that guide. The file name usually consists of the chapter name. This structure is very useful as more than one translator can work on certain guide same time.

New languages: Creating docbook-locales File

If you are creating the first-ever translation for a locale, you must first translate docbook-locales file used in all documents for your locale.

  1. Navigate to the docbook-locales Transifex project: https://www.transifex.net/projects/p/fedora-docbook-locales/resource/locale/
  2. If your language is not there, just add it.
  3. File a bug in Bugzilla against Product "Fedora Documentation" with Component "docs-requests". You may leave the details blank, or name the guide name(s) which you like to translate. Attach Files if Necessary. If you have any problems submitting po files using above instructions, you can attach it to the bug.
  4. Use the following Summary on the bug: "[ja]: New language support request."

发布您的成果

当您的文档翻译已经准备好可以发布在 Fedora 文档网站 上时，请依照以下步骤提交一份正式的翻译发布请求：

  1. 在 Bugzilla 提交 针对 Fedora 文档产品 publishing-requests 组件的 bug。记得在描述区域注明您想要发布的文档的名称与语言版本。如果您想要一次发布多份文档，请为每份文档分别提交 bug。
  2. FAS 中 docs-publishers 群组的成员会被提醒有您的请求，然后会发布您的翻译。一旦翻译得到发布，他们会为您关闭 bug。
发布翻译的其他方式
上面的步骤并不影响那些已经习惯于发布自己文档翻译的翻译团队。只要缺少必要人力或知识在 Fedora 文档网站上发布文档的翻译团队才需要在 Bugzilla 提交 bug 以发布他们的文档翻译。
成为 FAS 中 docs-publishers 群组的成员
如果您乐意帮忙处理发布过程，成为 FAS 中 docs-publishers 群组的成员，请联系 文档项目。为加速整个过程，建议翻译团队中至少有一个成员也在 FAS 的 docs-publishers 群组中以处理团队的发布请求。

什么样的文档需要翻译

对每个 Fedora 发行版本来说最重要的文档有：

  • docbook-locales
  • Common Content for Publican(Publican 常规内容)
  • Publican branding for Fedora
  • Documentation website(文档网站)
  • Release Notes(发行注记)
  • Burning ISOs(刻录ISO)
  • Live Image(Live 镜像)

翻译 Fedora 项目网站

Fedora 网站同样可以通过 Transifex 进行翻译。您可以在 Fedora Websites Release 找到所有 Fedora 网站相关的项目：

https://www.transifex.net/projects/p/fedora/r/fedora-websites/

下载、翻译、提交网站项目，流程和软件项目的一样。请注意新翻译不时就会拉取，根据发布状态，周期可能是每天或是每周一次。如果您注意到已经有一段时间没有更新您的翻译，您可以在网站团队的邮件列表上请求更新。通过添加 L10n 邮件列表到抄送，您可以告知其他团队您已经请求了更新。

加入新的 .po 文件

添加新的 po 文件的方式和软件项目的一致。如果您是有史以来第一次为一个 locale 新建翻译，您必须提醒 Fedora 网站团队把新语言添加到网站上。向 trans 邮件列表发布请求，以使网站团队可以把这个语言添加到网站的 Apache 配置中。

校对

一般说来，网站团队会提供测试站点以供校对。

翻译维基页面

Fedora Wiki 是项目相关信息的仓库。其中的一些页面需要被翻译以更好地服务 Fedora 社区。这一章会一步步地解释翻译维基页面的正确方法。

1.找到待翻译页面的英文版本

英语是 Fedora 项目维基的基础语言，所以首先需要有您要工作的页面的英文版本。(如果您要翻译的页面没有英文版本，参考下面的“处理没有英文版本的翻译”。)

如果页面顶部已经有一个语言模板，点击语言盒子右边的 edit 链接，跳到第 4 步；否则，继续看第 2 步。

如果您新建的页面没有英文版本，请新建一个新页面用于英文版本，添加模板 { { template|autolang } }， 然后添加模板 {{needs english}}。这会标识这个页面需要英文翻译，同时会新建一个基础页面。

2.在英文页面顶部加入语言框

编辑英文页面，在页面顶部添加模板 { { template|autolang} }： 

{ { autolang|base=yes } }

base=yes 部分对于英文页面是必需的。保存这个页面。

3.创建语言模板

{ { template|autolang } } autolang 模板应该会提供一个链接让您设置好语言盒。点击它会出现一个编辑页面。 不要更改任何内容，保存页面。然后点击语言盒右边的 edit 链接。

4.加入您使用的语言到模板中

到这一步您应该有了一个编辑框，其中有模板语法类似：{ { lang|en|page=Base page name } }

在 lang 和 page= 之间的文本是语言代码的列表。把您打算翻译到的语言的代码添加到列表中去。 使用下面的列表确定正确的 MediaWiki 语言代码。

http://fedoraproject.org/wiki http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/languages/Names.php?view=markup

请保持列表的字母序：保持语言代码的列表依照代码的字母顺序排列。举个例子，这意味着德语(de)应该出现在英语(en)之前。

5.开始创作新页面

点击对应您的语言的红色链接以打开新页面。在页面顶部插入模板 { { autolang } }，以使得语言列表出现在那里。 确定非英语的子页面的模板中不包含 base=yes。

6.移动已翻译的旧页面

对于不在正确位置的已翻译页面，请遵循以上的 1-4 步。然后复制新页面的标题(例如 Fedora Project Wiki/de)。 点击就业面顶部的 move 链接，把新页面名字粘贴到新标题区域。编辑新页面，在顶部添加 { { autolang } }。

FAQ (常见问题)

这里有一些有关本地化项目的常见问题。

我应该翻译法律声明吗?

不。您绝不要那么做。法律声明的准确措辞非常重要，不被律师认可的翻译版本非常冒险。Red Hat 是 Fedora 项目的法律代表和主要赞助商，它没有资源去对每一个翻译做交叉检查。当涉及到法律事务时，保持原始的英文声明原封不动即可。

我如何报告问题？

Before reporting (either opening a new ticket or the list), please search to see if there's an existing report opened. It sometimes help to ask in #fedora-l10n if there's a known issue at that exact moment. If not, please open a ticket describing what's wrong with the service in clarity. Include the nature of the problem, the project/resource, the time (in UTC) it happened and your Fedora username. If you suspect it might be a problem with the particular file you are uploading or the target file, include that information as well.

发现问题应向谁报告？

  • 针对仅限于Transifex的问题，应该使用网站右侧的"Feedback"（反馈）按钮来进行汇报。
    • 问题报告的范围包括：Transifex相关的疑问、可能的bug、请求增加新的功能、网站使用过程中遇到的问题（如网页反应很慢，无法登录等等）。
    • 不要用Feedback功能汇报Fedora项目缺失、请求创建Fedora小组、Fedora协调员等问题。
  • 针对仅限于Fedora L10n的问题，应该首先在IRC的#fedora-l10n频道里汇报，然后发信至trans-邮件列表。
    • 内容可以涉及小组内部提问、发布版本、项目、Fedora的维护者、开发者等。
    • 不要在此汇报Transifex的bug、功能请求、网站问题（如网页反应很慢、无法登录，或因发布版本中的项目缺失导致统计数据错误等）。

如何请求添加新的功能？

请参见上条，仅限于Transifex的问题。

我怎样新建一个团队？ (#new-team)

See L10N Maintainer on how to become a maintainer of a new language.


我的翻译文件已经100%完成，但我测试程序的时候还是只能看到英文字符！ (#missing-strings)

顺带一提，这没什么好担心的。别放在心上。问题可能出在如下几个方面：

  • 字符丢失是因为开发人员没有将其标记为译文，因此POT文件里没有这些字符，于是PO文件里当然也不会有。开发者需要对相应译文使用gettext。
  • 使用intltool的时候没有选中并包含相应的源文件。
  • Transifex上的POT文件没有更新。组件(component）页面有POT文件的生成日期。如果该时间过于久远（超过几个小时，例如一两天以前），请通知管理员；否则没问题。

数据统计是实时的吗？多久更新一次？ (#update-frequency)

Transifex项目页面上的数据统计总是实时的。发布页面则是每天更新一次。


如何在Transifex中添加新的模块？ (#add-transifex)

  1. Navigate to https://www.transifex.net/projects/add/
  2. Follow the instructions from http://help.transifex.net/intro/projects.html

If you want the Fedora Localization Project to handle your translations (i.e. you are NOT an upstream project):

  1. Click 'Access Control' on your Project Details Page
  2. Outsource team control to "The Fedora Project"
  3. Send an email to fedora-trans-list and let the contributors know about the change. One of the Fedora L10n Editors will add your project to one of the Fedora releases.

http://fedora.transifex.net/


Here are two more pages you might want to read:

我是开发者，怎样才能连.desktop文件一起翻译？

Transifex很快就会内置对.desktop文件的支持。

我找不到字符串"About this Computer"，它在哪儿？

可以在AboutThisComputer找到。

Is the section of export regulations shown at the bottom of the fedoraproject.org/get-fedora page translatable?

No. This is purposely set up as non-translatable. Please refer to Non-translatable export regulations?.

If some strings change past string freeze, how do I request a string freeze breakage?

Email the trans mailing list!

What if I overwrite a wrong file?

If you have overwritten a wrong file in your own locale, try to find the old file on the developer's git repo (http://git.fedorahosted.org/git/) and replace the wrongly updated file with this file.

Even though these are measures to correct mistake, we strongly advice you to take extra care while submitting the translations via Transifex and make sure that you are uploading file in proper location under proper locale because some projects don't keep translation files under their CVS tree (do I say "Anaconda" ? oO)

I'm from the Docs Project. How do I make my Guide / Release Notes / other document available for translation?

If you keep you document in a git repository, see Setting up a document with Transifex to find out how to make it available to translators on Transifex.net.

本指南编写人员

以下人员参与完善本页面:

  • Manuel Ospina
  • Paul W. Frields
  • Noriko Mizumoto
  • Dimitris Glezos
  • Diego Búrigo Zacarão
  • Piotr Drąg
  • Misha Shnurapet
  • Petr Kovar
Retrieved from "https://fedoraproject.org/w/index.php?title=L10N/Guide/zh-cn&oldid=267671"