I met some unclear issue when I was using the azure translations api with c#: How to calculate the char precisely? for example, a letter in English is always a byte, i.e., a char, but a character in Chinese will be 2 bytes in unicode, and more in utf8, how could I calculate the char for a Chinese sentence? It seems there is some limitation on request speed. and if you request too fast you will get a too much request error. So how much is the limitation, for example, the chars per second? I saw the price document said, there is 2m char per month for free instance, so is it also available for s1 instance? Thank you so much.

details of some limitations of Azure translation

Suri 0

I met some unclear issue when I was using the azure translations api with c#:

How to calculate the char precisely? for example, a letter in English is always a byte, i.e., a char, but a character in Chinese will be 2 bytes in unicode, and more in utf8, how could I calculate the char for a Chinese sentence?
It seems there is some limitation on request speed. and if you request too fast you will get a too much request error. So how much is the limitation, for example, the chars per second?
I saw the price document said, there is 2m char per month for free instance, so is it also available for s1 instance?

Thank you so much.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.