One thing to note is that localization people need time to do the localizations, and the less they're getting paid for it, the longer they need. This means that you should at least try to avoid changing the localization keys (especially including defining new ones) shortly before a release. I know it's nice to not be constrained like that, but the reality is that if you're not paying then you're not going to get a fast turnaround in the majority of cases, so you have to plan for this and mitigate in your schedule. In effect, you have to stop thinking about the text shown to a user as something that can be finalized late in the project and instead start treating it as an important interface matter that you'll plan to lock down much earlier.
实际上，修饰它们是更好的选择。您已经完成了第一步 - 包含它们 - 表明它们的修复、更新等已包含在内并对产品有所帮助。下一步是公开感谢他们并赞赏他们。如您所见，这将获得前 80%。下一步是让他们亲自做出承诺。开始直接与他们互动。向他们发送您的感谢......不仅仅是通过电子邮件。如果您有一件产品 T 恤，请给他们寄一件带有手写便条的 T 恤。在您的发行说明中，链接到他们的网站。如果你亲自见到他们，请买他们的咖啡……无论如何。关键是你要不遗余力——无论多么小——承认他们正在不遗余力地走自己的路。
It's the 90-9-1 principle - http://www.90-9-1.com/ - and designating people in charge of things isn't going to do it. You can offer cash - rewards/pay - or you can groom them. If you bring money into the mix, remember that it quickly becomes tradeoff analysis. People will compare what you offer versus what they can earn on their own. Since I assume you don't have that much money, you don't want that sort of comparison.
Realistically, grooming them is a better option. You've done the first step - include them - show that their fixes, updates, etc are included and help the product. The next step is publicly thanking them and appreciating them. That will get the first 80% as you've seen. The next step is getting them personally committed. Start interacting with them directly. Send them your thanks.. not just in email. If you have a product t-shirt, send them one with a hand written note. In your release notes, link to their sites. If you ever see them in person, buy their coffee.. whatever. The point is that you go out of your way - however small - to acknowledge that they're going out of their own way.
I'm the Project Lead of the Open Source Project Management System web2project and have been doing this longer than I care to consider. ;)
Use both a carrot and a stick approach. Giving people credit in your "About" screen, and calling them the lead translator for a particular language (if they're willing to accept that responsibility) is a good thing. Don't include a translation until you've gotten someone to commit to being the lead translator for that language; just like with code, you don't want to accept contributions unless (a) you are able and willing to maintain those contributions or (b) someone who you consider reliable has volunteered to be responsible for maintaining it.
The "stick" is that if someone stops maintaining a language, and fails to appropriately pass the responsibility off to someone else, you will remove that language from the next version of your application. Most people who translate your app probably do so because they would prefer to use your app in their native language. The threat of removing the language from the next version, or the wake-up call when they find that the next version doesn't contain their language, might inspire them to come back and finish up the last 30% translation work.
You are getting it wrong, community translation is an ongoing process or lets say never ending approach.
This doesn't meant that is wrong, but you have to live with the fact that localization is always a compromise and that Usually, it is better to have 20 languages with 50% translation than having 10 languages 100% translated.
If one language is important, it will have more users, so it will have more contributors and the translation rate will be greater.
You don't know when and if the translation for a specific language will be 100%, probably never.
The good part is that you shouldn't care about obtaining 100%, you should spend your effort in motivating people to contribute.
Probably you already know, community translation doesn't play well with packed products.
The solution to this problem is to change the way you work and provide partial translations in your release and a simple update system that updates them (preferably a silent one, like the Chromium update).
PS. If you need to assure a 100% translation rate for a limited number of languages before your release, consider paying a translation vendor to do it.
Well, you get what you paid for. The strategy that you are planing to implement will not give you anything. That's because heroes have their own lives. The only way to get this done, is to engage more people to translate, because completion percentage is a function of a community size.
If your application is useful enough, you may try to give a link "help to translate into your language" and this could do for a while.
Think of creating discussion group or board that you could post "Call for translation" when you are ready to ship. Translators usually don't have a time to track changes.
发布评论
评论（5）
需要注意的一件事是，本地化人员需要时间来进行本地化，而且他们获得的报酬越少，他们需要的时间就越长。这意味着您至少应该尝试避免在发布前不久更改本地化密钥（尤其是定义新的密钥）。我知道不受这样的限制很好，但现实是，如果您不付款，那么在大多数情况下您将无法获得快速周转，因此您必须为此做好计划并减轻您的负担。日程。实际上，您必须停止将向用户显示的文本视为可以在项目后期完成的内容，而是开始将其视为重要的界面问题，您将计划更早地锁定它。
One thing to note is that localization people need time to do the localizations, and the less they're getting paid for it, the longer they need. This means that you should at least try to avoid changing the localization keys (especially including defining new ones) shortly before a release. I know it's nice to not be constrained like that, but the reality is that if you're not paying then you're not going to get a fast turnaround in the majority of cases, so you have to plan for this and mitigate in your schedule. In effect, you have to stop thinking about the text shown to a user as something that can be finalized late in the project and instead start treating it as an important interface matter that you'll plan to lock down much earlier.
这是 90-9-1 原则 - http://www.90-9-1.com/ - 指定专人负责事情是行不通的。你可以提供现金——奖励/报酬——或者你可以培养他们。如果您将资金纳入其中，请记住它很快就会变成权衡分析。人们会比较你提供的东西和他们自己能赚到的东西。因为我假设您没有那么多钱，所以您不需要进行这种比较。
实际上，修饰它们是更好的选择。您已经完成了第一步 - 包含它们 - 表明它们的修复、更新等已包含在内并对产品有所帮助。下一步是公开感谢他们并赞赏他们。如您所见，这将获得前 80%。下一步是让他们亲自做出承诺。开始直接与他们互动。向他们发送您的感谢......不仅仅是通过电子邮件。如果您有一件产品 T 恤，请给他们寄一件带有手写便条的 T 恤。在您的发行说明中，链接到他们的网站。如果你亲自见到他们，请买他们的咖啡……无论如何。关键是你要不遗余力——无论多么小——承认他们正在不遗余力地走自己的路。
It's the 90-9-1 principle - http://www.90-9-1.com/ - and designating people in charge of things isn't going to do it. You can offer cash - rewards/pay - or you can groom them. If you bring money into the mix, remember that it quickly becomes tradeoff analysis. People will compare what you offer versus what they can earn on their own. Since I assume you don't have that much money, you don't want that sort of comparison.
Realistically, grooming them is a better option. You've done the first step - include them - show that their fixes, updates, etc are included and help the product. The next step is publicly thanking them and appreciating them. That will get the first 80% as you've seen. The next step is getting them personally committed. Start interacting with them directly. Send them your thanks.. not just in email. If you have a product t-shirt, send them one with a hand written note. In your release notes, link to their sites. If you ever see them in person, buy their coffee.. whatever. The point is that you go out of your way - however small - to acknowledge that they're going out of their own way.
胡萝卜加大棒并用。在“关于”屏幕上给予人们信任，并称他们为特定语言的首席翻译（如果他们愿意接受这一责任）是一件好事。在你让某人承诺担任该语言的首席翻译之前，不要包含翻译；就像代码一样，您不想接受贡献，除非 (a) 您能够并且愿意维护这些贡献，或者 (b) 您认为可靠的人自愿负责维护它。
“坚持”是，如果有人停止维护一种语言，并且未能适当地将责任转嫁给其他人，您将从应用程序的下一版本中删除该语言。大多数翻译您的应用程序的人可能会这样做，因为他们更喜欢以其母语使用您的应用程序。从下一个版本中删除该语言的威胁，或者当他们发现下一个版本不包含他们的语言时的警钟，可能会激励他们回来完成最后 30% 的翻译工作。
Use both a carrot and a stick approach. Giving people credit in your "About" screen, and calling them the lead translator for a particular language (if they're willing to accept that responsibility) is a good thing. Don't include a translation until you've gotten someone to commit to being the lead translator for that language; just like with code, you don't want to accept contributions unless (a) you are able and willing to maintain those contributions or (b) someone who you consider reliable has volunteered to be responsible for maintaining it.
The "stick" is that if someone stops maintaining a language, and fails to appropriately pass the responsibility off to someone else, you will remove that language from the next version of your application. Most people who translate your app probably do so because they would prefer to use your app in their native language. The threat of removing the language from the next version, or the wake-up call when they find that the next version doesn't contain their language, might inspire them to come back and finish up the last 30% translation work.
您错了，社区翻译是一个持续的过程，或者可以说是永无止境的方法。
这并不意味着这是错误的，但您必须接受这样一个事实：本地化始终是一种妥协，并且通常，20 种语言 50% 翻译比 10 种语言 100% 翻译要好。
如果一种语言很重要，它就会有更多的用户，因此它会有更多的贡献者，翻译率也会更高。
您不知道特定语言的翻译何时以及是否会达到 100%，可能永远。
好的方面是，你不应该关心获得 100%，你应该花精力激励人们做出贡献。
也许您已经知道，社区翻译不适用于包装产品。
这个问题的解决方案是改变你的工作方式，并在你的版本中提供部分翻译和一个简单的更新系统来更新它们（最好是静默的，如 Chromium 更新）。
附言。如果您需要在发布之前确保有限数量的语言获得 100% 的翻译率，请考虑向翻译供应商付费来完成此任务。
You are getting it wrong, community translation is an ongoing process or lets say never ending approach.
This doesn't meant that is wrong, but you have to live with the fact that localization is always a compromise and that Usually, it is better to have 20 languages with 50% translation than having 10 languages 100% translated.
If one language is important, it will have more users, so it will have more contributors and the translation rate will be greater.
You don't know when and if the translation for a specific language will be 100%, probably never.
The good part is that you shouldn't care about obtaining 100%, you should spend your effort in motivating people to contribute.
Probably you already know, community translation doesn't play well with packed products.
The solution to this problem is to change the way you work and provide partial translations in your release and a simple update system that updates them (preferably a silent one, like the Chromium update).
PS. If you need to assure a 100% translation rate for a limited number of languages before your release, consider paying a translation vendor to do it.
好吧，你得到了你所付出的代价。你计划实施的策略不会给你带来任何好处。因为英雄有自己的生活。完成这项工作的唯一方法是让更多的人参与翻译，因为完成百分比是社区规模的函数。
如果您的应用程序足够有用，您可以尝试提供一个链接“帮助翻译成您的语言”，这可能会持续一段时间。
考虑创建讨论组或看板，当您准备好发货时，您可以在其中发布“请求翻译”。译者通常没有时间跟踪更改。
Well, you get what you paid for. The strategy that you are planing to implement will not give you anything. That's because heroes have their own lives. The only way to get this done, is to engage more people to translate, because completion percentage is a function of a community size.
If your application is useful enough, you may try to give a link "help to translate into your language" and this could do for a while.
Think of creating discussion group or board that you could post "Call for translation" when you are ready to ship. Translators usually don't have a time to track changes.