翻译 - 多个不同的用户和分配用途 [英] Translator - multiple different users and allocating usage

问题描述

嗨新手在这里请原谅我，如果之前已经问过这个问题（我找不到任何东西）。

Hi newbie here so excuse me if this has been asked before (I cant find anything).

我正在开发一个将被许多不同的应用程序使用的应用程序顾客。我显然不想为他们购买翻译字符，而是希望他们来微软并购买自己的月度字符包。

I am developing an application that will be used by a number of different customers. I obviously don't want to be purchasing translation characters for them but rather would prefer them to come to Microsoft and purchase there own package of monthly characters.

我该如何管理呢？对于其他APis，他们只提供自己的密钥。我是否也为他们做同样的事情并让他们进入自己的clientID和clientSecret。

How do I go about managing this? With other APis, they just provide there own key. Do I do the same for them and get them to enter there own clientID and clientSecret.

谢谢

推荐答案

嗨Rescue193，

Hi Rescue193,

如果你的应用是针对消费者的，你不会让他们经历注册过程并获得他们自己的钥匙。不友好消费者。您自己注册，付费，然后向消费者收费，可能是您应用中的高级功能。一些
的免费翻译，其余的需要在应用内购买。

If your app is targeting consumers, you will NOT want to make them go through the signup process and get their own key. Not consumer friendly. You sign up yourself, pay for it, and then charge the consumers, maybe as a premium feature within your app. Some translations for free, the rest require an in-app purchase.

如果您的应用是针对开发人员或企业用户，那么您可以要求开发人员或企业管理员签名用他们自己的帐户。在您的应用中提供一个允许他们设置的功能。

If your app is targeting developers or enterprise users, then you can ask the developer or enterprise admin to sign up with their own account. Provide a feature in your app that allows them to set it.

创建译员帐户绝对不适合消费者。

The Translator account creation is definitely not suitable for consumers.

希望这有帮助，

Chris Wendt

Microsoft Translator

Hope this helps,
Chris Wendt
Microsoft Translator

这篇关于翻译 - 多个不同的用户和分配用途的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！