跳到主要內容

Translation project 101

The propose of this article it to help new Gnomer become translation, especially help the Chinese who would like to join Chinese translation team but have troubles to handle all the English Guide . As a woman, I hope more women could be interested in or even a part of open source.

本文的目的是帮助 Gnome 新人成为翻译者,特别是帮助那些想加入中文翻译团队却因为英文  guide 而头疼的成员。作为女性,我希望更多女性对开源项目感兴趣,甚至成为其中一员。

I once tried to be a GNOME translator, so I found out ways to follow the guide of GNOME, but the translation is not in good format, not accepted. At that time I was wondering how hard translation will be. Until be taught by my mentor now, who are the committer of Chinese Translation team, the speaker of GNOME Asia 2013. If you get any questions with translation and workflow, you could ask himfor help.

今年早些时候,我试着加入GNOME团队,做过一点翻译,质量不是很理想。主要原因是对整个翻译的team以及工作流程了解的不够。感谢我的mentor,给了我许多帮助,他是GNOME 中文团队的committer,如果你在翻译过程中有任何问题,可以请教他。

The most important thing that I have learned is "work with the team".

翻译最首要的是:和团队协作。

So I would like to write an introducing guide in my way from failure,I will introduce the team in the first place.

所以我将自己从失败中学到的攻略分享给大家,会着重提到GNOME 中文翻译团队。

Here is the content of this blog
1. Register
2. Find a team
2.1 Translation roles
2.2 Introduce of Chinese translation team
3. Choose a file
4. Choose an editor
5. Basic skill
6. Workflow

以下为本文的目录
1.注册
2.加入团队
2.1团队中的角色
2.2 中国翻译团队的介绍
3.选择翻译文件
4.选择翻译编辑器
5.需要掌握的基本技能
6.工作流简要了解

1.Register

Before the whole translation introducing, I would like to talk about the quick-start with you guys.
在正式介绍整个翻译的具体知识之前,我们还是先快速了解下如何快速成为翻译者。

Register at https://l10n.gnome.org/register/

注册 l10n

2.Find a team

Join your team at http://l10n.gnome.org/users/team_join/

如果你是中国大陆的翻译者,请加入中文简体的团队

Knowing the translation roles will help you work better with the team.

了解团队中的角色至关重要,涉及到沟通,合作。

2.1 Translation roles

Translator

Translators contains persons helping with GNOME translations into a specific language, who added themselves to the translation team. Translators could add comment to a specific PO file translation, could reserve it for translations and could suggest new translations by upload a new PO file. The suggested translations will be reviewed by other team members.

翻译者

翻译者列表列出了所有有意向帮助翻译 GNOME 到该语言的人员,这些人员是自己将自己加入到其中的。 翻译者可以在 PO 翻译文件的页面上留下评论、占用文件进行翻译,或者是上传文件以便提交新的更新建议。上传的文件将被其他人审阅。

Reviewers

Reviewers are GNOME translators which were assigned by the team coordinator to review newly suggested translations (by translators, reviews or committers). They have access to all actions available to a translators with the addition of some reviewing task (ex reserve a translation file for proofreading, mark a translation as being ready to be included in GNOME).

审阅者

审阅者是小组指定的审阅新翻译的人员,他们有翻译者可用的全部权限,此外还有用于完成审阅的几个操作(占用文件进行审阅、标记翻译为可以提交等)的权限。

Committers

Committers are people with rights to make changes to the GNOME translations that will be release. Unless a translations is not committed by a committer, it will only remain visible in the web interface, as an attached po file.

Committers have access to all actions of a reviewer with the addition of marking a po file as committed and archiving a discussion for new suggestions.

提交者

提交者是小组中有权限将翻译提交到 GNOME 仓库并使之可以在软件下一次发布时一并被发行的人。如果没有提交者进行操作,所有的翻译、审阅都仅仅是在此网页平台上,而不能被应用到实际的仓库中。

提交者有审阅者可用的全部权限,同时还可以标记文件为已提交并将讨论归档以便接受新的翻译。

If you would like to know some useful information of being a translator and translation itself, following is the helping mail I received when I asked questions .


如果你想要了解一些成为翻译者以及翻译本身的资料,分享一份我收到的邮件,希望可以减少翻译组同学们的重复回复:

Glad to hear from you, here is a brief guide for participating:
https://live.gnome.org/TranslationProject/ContributeTranslations/zh

And here is a guide for conventions in translations:
http://people.ubuntu.com/~wzssyqa/gnome-translation-details.pdf

A tool for querying existing translations using web/sqlite (thanks
csslayer for hosting):
https://www.csslayer.info/l10n

Finally we have more related materials to look up when needed:
http://people.ubuntu.com/~happyaron/l10n/

3.Choose a file

Click the link into the release you prefer, and find a untranslated file suits your time and ability. Usually the stable release first, for the development may not frozen.

以上是按照发行版来归类的文件,点击链接进入,可以选择还未翻译的文件,占用并翻译。

一般来说先翻译stabledevelopment版本在代码未冻结之前,都是可能改变的。
Here is the possible states of file.

No status --无状态 --可以占用
Translating --被占用 --不可以
Proofreading --审阅中 --不可以
To commit --已提交 --不可以
Needs rework --需重做

There is a wonderful guide of choosing file.

4. Choose an editor
Editors I use now
    1. GVim (highly recommend) with po.vim plugin
GVim 快捷键操作方便,界面美观,跨平台应用

    1. Lokalize (KDE)
过滤器功能很好,适合翻译较多的文件

Other tools you may prefer:

poEdit -- www.poedit.net/
Virtaal -- www.virtaal.org/
OmegaT -- www.omegat.org/
Emacs with po-mode.el -- www.gnu.org/software/emacs/

  1. Basic skill
Don’t be upset, translation is not that hard, here is a simple one.

If you are not sure of your translation, you can tag it as “fuzzy”, like the following done.

If you would like to query existing translations, ask csslayer

In the following blog I will introduce some skill of gvim and vim use.



留言

  1. Nice post. Better if you provide some screenshots... and polish your English.

    The post should be more generalized, rather than focused on Chinese translation.

    Expecting your next post!

    回覆刪除

張貼留言

這個網誌中的熱門文章

Summary about Translation Work

I am so not good at summary, because it is so hard to make it meaningful and worth sharing. But looking back, review the condition of our translation work, will be at least helpful to help newer like me get involved more easily. 我非常不擅长总结,这个工作要做到有意义值的分享很有难度。但是回顾一下,理清现在中文翻译的情况,特别是从新人的角度,希望帮助其他加入者了解怎样成长更快,怎样对用户使用中文 GNOME 帮助更大。 After reading another intern who also works on translation, JuditGyimesi, whose blog is in different style. I changed my mind to share statics and skills. Maybe because I am a Chinese who was educated from a young age that every share need to give reader knowledge. From her blog I have learnt sharing when translating the translator feel happy still make sense. 在我参考了另外一位翻译实习生 JuditGyimesi 的 博客  以后,把这篇文章的风格修改了一下,不知道是不是因为自己是中国人的原因,过于希望在博客里分享知识,怎样做,能学会什么,或者简简单单的分享自己做了些什么,觉得很开心就好了。 Talk about the growth in the translation program, the most important must be understanding the important or urgent situation of each program need translated. And finding out the parts

Useful Gvim Skills for translation work

As I use linux as normal operating system, and prefer gvim very much. I would like to share some skills to help keep your hands away from mouse bracing the high efficient way of working. Especially for the survive stage vim newbees. I hope the article will help you get into the translation work faster than spending long time learning vim from 0. 因为日常使用linux系统,翻译工作的工具又比较偏爱gvim,所以分享一些小技巧,希望帮助大家远离“鼠标+键盘”的低效工作模式,特别是刚刚处于survive阶段的vim轻度用户。快速在翻译工作中高效使用vim。 1.MOVE    移动 1.1 move between msgstr       msgstr间移动 The basic item of .po file is msgstr, when whose state is untranslated and fuzzy need working on. So jump between the msgstr is very simple: 在翻译中基本单位是msgstr,需要翻译的状态是:未翻译和fuzzy,在这两种状态直接的跳跃方法很简单: In both normal and insert state, SHIFT+F1, next untranslated,  SHIFT+F2, pre untranslated  SHIFT+F5, next fuzzy, SHIFT+F6, pre fuzzy. 两种状态下,SHIFT+F1,下一条未翻译,SHIFT+F2,上一条未翻译。 SHIFT+F5,下一条fuzzy,SHIFT+F6,上一条fuzzy。 If you would like to find a pre msgstr which you j

Back to Blogger

Start up my blogger spot again~ After working in a frequent re-organizing business unit in a big company for nearly 10 years, struggling in the seas of system, Bigdata, ML/DL, cloud, etc. On one hand I feel myself like Columbus overrun the seven seas(OSI) dreaming for land, on the other hand I feel like farming the four seasons, harvesting less for climate change or tribes migrate.  This year I have a new plan, to start a journey back to land. To farm on a small, stable land, growing something I like. Ref: little forest   Why I choose back to blogger, my expectation of my renew blog: - To track the thoughts - To incubate articles - To communicate on related topics    My previous ways: - github issue     - Pro: quiet enough for me:)     - Con: no feedback and discussion for the thoughts - local obsidian notes/xmind     - Pro: very efficient to trace and summary     - Con: I am the only reader The only way I could find to seek meaningful communication through blog, of course to write in