mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
Merge pull request #13976 from wxy/20190531-Why-translation-platforms-matter
TSL:20190531 Why translation platforms matter.md
This commit is contained in:
Xingyu.Wang
GitHub
commit
d75343509b
@ -1,96 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wxy)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Why translation platforms matter)
|
||||
[#]: via: (https://opensource.com/article/19/5/translation-platforms)
|
||||
[#]: author: (Jean-Baptiste Holcroft https://opensource.com/users/jibec/users/annegentle/users/bcotton)
|
||||
|
||||
Why translation platforms matter
|
||||
======
|
||||
Technical considerations are not the best way to judge a good
|
||||
translation platform.
|
||||
![][1]
|
||||
|
||||
Language translation enables open source software to be used by people all over the world, and it's a great way for non-developers to get involved in their favorite projects. There are many [translation tools][2] available that you can evaluate according to how well they handle the main functional areas involved in translations: technical interaction capabilities, teamwork support capabilities, and translation support capabilities.
|
||||
|
||||
Technical interaction considerations include:
|
||||
|
||||
* Supported file formats
|
||||
* Synchronization with the source repository
|
||||
* Automation support tools
|
||||
* Interface possibilities
|
||||
|
||||
|
||||
|
||||
Support for teamwork (which could also be called "community animation") includes how a platform:
|
||||
|
||||
* Monitors changes (by a translator, on a project, etc.)
|
||||
* Follows up on updates pushed by projects
|
||||
* Displays the state of the situation
|
||||
* Enables or not review and validation steps
|
||||
* Assists in discussions between translators (from the same team and inter-languages) and with project maintainers
|
||||
* Supports global communication on the platform (news, etc.)
|
||||
|
||||
|
||||
|
||||
Translator assistance includes:
|
||||
|
||||
* A clear and ergonomic interface
|
||||
* A limited number of steps to find a project and start working
|
||||
* A simple way to read the flow between translation and distribution
|
||||
* Access to a translation memory machine
|
||||
* Glossary enrichment
|
||||
|
||||
|
||||
|
||||
There are no major differences, though there are some minor ones, between source code management platforms relating to the first two functional areas. ****I suspect that the last area pertains mainly to source code. However, the data handled is quite different and users are usually much less technically sophisticated than developers, as well as more numerous.
|
||||
|
||||
### My recommendation
|
||||
|
||||
In my opinion, the GNOME platform offers the best translation platform for the following reasons:
|
||||
|
||||
* Its site contains both the team organization and the translation platform. It's easy to see who is responsible and their roles on the team. Everything is concentrated on a few screens.
|
||||
* It's easy to find what to work on, and you quickly realize you'll have to download files to your computer and send them back once you modify them. It's not very sexy, but the logic is easy to understand.
|
||||
* Once you send a file back, the platform can send an alert to the mailing list so the team knows the next steps and the translation can be easily discussed at the global level (rather than commenting on specific sentences).
|
||||
* It has 297 languages.
|
||||
* It shows clear percentages on progress, both on basic sentences and advanced menus and documentation.
|
||||
|
||||
|
||||
|
||||
Coupled with a predictable GNOME release schedule, everything is available for the community to work well because the tool promotes community work.
|
||||
|
||||
If we look at the Debian translation team, which has been doing a good job for years translating an unimaginable amount of content for Fedora (especially news), we see there is a highly codified translation process based exclusively on emails with a manual push in the repositories. This team also puts everything into the process, rather than the tools, and—despite the considerable energy this seems to require—it has worked for many years while being among the leading group of languages.
|
||||
|
||||
My perception is that the primary issue for a successful translation platform is not based on the ability to make the unitary (technical, translation) work, but on how it structures and supports the translation team's processes. This is what gives sustainability.
|
||||
|
||||
The production processes are the most important way to structure a team; by putting them together correctly, it's easy for newcomers to understand how processes work, adopt them, and explain them to the next group of newcomers.
|
||||
|
||||
To build a sustainable community, the first consideration must be on a tool that supports collaborative work, then on its usability.
|
||||
|
||||
This explains my frustration with the [Zanata][3] tool, which is efficient from a technical and interface standpoint, but poor when it comes to helping to structure a community. GIven that translation is a community-driven process (possibly one of the most community-driven processes in open source software development), this is a critical problem for me.
|
||||
|
||||
* * *
|
||||
|
||||
_This article is adapted from "[What's a good translation platform?][4]" originally published on the Jibec Journal and is reused with permission._
|
||||
|
||||
Learn about seven tools and processes, both human and software, which are used to manage patch...
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/5/translation-platforms
|
||||
|
||||
作者：[Jean-Baptiste Holcroft][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jibec/users/annegentle/users/bcotton
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/people_remote_teams_world.png?itok=_9DCHEel
|
||||
[2]: https://opensource.com/article/17/6/open-source-localization-tools
|
||||
[3]: http://zanata.org/
|
||||
[4]: https://jibecfed.fedorapeople.org/blog-hugo/en/2016/09/whats-a-good-translation-platform/
|
||||
87
translated/talk/20190531 Why translation platforms matter.md
Normal file
87
translated/talk/20190531 Why translation platforms matter.md
Normal file
@ -0,0 +1,87 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wxy)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Why translation platforms matter)
|
||||
[#]: via: (https://opensource.com/article/19/5/translation-platforms)
|
||||
[#]: author: (Jean-Baptiste Holcroft https://opensource.com/users/jibec/users/annegentle/users/bcotton)
|
||||
|
||||
为什么翻译平台很重要
|
||||
======
|
||||
|
||||
技术上的考虑并不是判断一个好的翻译平台的最佳方式。
|
||||
|
||||
![][1]
|
||||
|
||||
语言翻译可以使开源软件能够被世界各地的人们使用，这是非开发人员参与他们喜欢的（开源）项目的好方法。有许多[翻译工具][2]，你可以根据他们处理翻译中涉及的主要功能区域的能力来评估：技术交互能力、团队支持能力和翻译支持能力。
|
||||
|
||||
技术交互方面包括：
|
||||
|
||||
* 支持的文件格式
|
||||
* 与开源存储库的同步
|
||||
* 自动化支持工具
|
||||
* 接口可能性
|
||||
|
||||
对团队合作（也可称为“社区活力”）的支持包括该平台如何：
|
||||
|
||||
* 监控变更（按译者、项目等）
|
||||
* 跟进由项目推动的更新
|
||||
* 显示进度状态
|
||||
* 是否启用审核和验证步骤
|
||||
* 协助（来自同一团队和跨语言的）翻译人员和项目维护人员之间的讨论
|
||||
* 平台支持的全球通信（新闻等）
|
||||
|
||||
翻译协助包括：
|
||||
|
||||
* 清晰、符合人体工程学的界面
|
||||
* 简单几步就可以找到项目并开始工作
|
||||
* 可以简单地阅读到翻译和分发之间流程
|
||||
* 可以使用翻译记忆机
|
||||
* 词汇表丰富
|
||||
|
||||
前两个功能区域与源代码管理平台的差别不大，只有一些小的差别。我觉得最后一个区域也主要与源代码有关。但是，它们处理的数据非常不同，它的用户通常比开发人员技术复杂得多，而且数量也更多。
|
||||
|
||||
### 我的推荐
|
||||
|
||||
在我看来，GNOME 平台提供了最好的翻译平台，原因如下：
|
||||
|
||||
* 其网站包含团队组织和翻译平台。很容易看出谁在负责以及他们在团队中的角色。一切都集中在几个屏幕上。
|
||||
* 很容易找到要处理的内容，并且你会很快意识到你必须将文件下载到计算机并在修改后将其发回。这个流程不是很先进，但逻辑很容易理解。
|
||||
* 一旦你发回文件，平台就可以向邮件列表发送警报，以便团队知道后续步骤，并且可以全局轻松讨论翻译（而不是评论特定句子）。
|
||||
* 它支持 297 种语言。
|
||||
* 它显示了基本句子、高级菜单和文档的明确的进度百分比。
|
||||
|
||||
再加上可预测的 GNOME 发布计划，社区可以使用一切可以促进社区工作的工具。
|
||||
|
||||
如果我们看看 Debian 翻译团队，他们多年来一直在为 Debian （LCTT 译注：此处原文是“Fedora”，疑为笔误）（尤其是新闻）翻译了难以想象的大量内容，我们看到他们有一个高度编码的翻译流程，完全基于电子邮件，手动推送到存储库。该团队还将所有内容都放在流程中，而不是工具中，尽管这似乎需要相当大的技术能力，但它已成为领先的语言群体之一，已经运作多年。
|
||||
|
||||
我认为，成功的翻译平台的主要问题不是基于单一的（技术、翻译）工作的能力，而是基于如何构建和支持翻译团队的流程。这就是可持续性的原因。
|
||||
|
||||
生产过程是构建团队最重要的方式；通过正确地将它们组合在一起，新手很容易理解该过程是如何工作的，采用它们，并将它们解释给下一组新人。
|
||||
|
||||
要建立一个可持续发展的社区，首先要考虑的是支持协同工作的工具，然后是可用性。
|
||||
|
||||
这解释了我为什么对 [Zanata][3] 工具沮丧，从技术和界面的角度来看，这是有效的，但在帮助构建社区方面却很差。我认为翻译是一个社区驱动的过程（可能是开源软件开发中最受社区驱动的过程之一），这对我来说是一个关键问题。
|
||||
|
||||
* * *
|
||||
|
||||
本文改编自“[什么是一个好的翻译平台？][4]”，最初发表在 Jibec 期刊上，并经许可重复使用。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/5/translation-platforms
|
||||
|
||||
作者：[Jean-Baptiste Holcroft][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[wxy](https://github.com/wxy)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jibec/users/annegentle/users/bcotton
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/people_remote_teams_world.png?itok=_9DCHEel
|
||||
[2]: https://opensource.com/article/17/6/open-source-localization-tools
|
||||
[3]: http://zanata.org/
|
||||
[4]: https://jibecfed.fedorapeople.org/blog-hugo/en/2016/09/whats-a-good-translation-platform/
|
||||
Loading…
Reference in New Issue
Block a user