Thanks for reporting your issue, @amin79. I would need more information to understand the problem, could you please provide your full configuration? alongside an example of a document with input & output texts.

From what I can understand, are you referring to text romanization?

@pr-Mais Hello. There is nothing special in the configurations. Everything works as expected.
But, just in this example, I have a text which includes the name of some cities (In English): "ASPENDOS & PERGE & SIDE"
When I save it, since these are some meaningful words in Latin, it would be translated to "GET UP & GO ON & SIT"!

Since I don't have Latin in my target languages list, I don't expect it to be transited to Latin. I like it to remain as it is because these are some NAMES.

@amin79 It would be helpful to see your configuration regardless, to help us reproduce the issue and resolve it.

Can you provide the configuration, and the exact phrase (if possible) containing these city names, which has been mistranslated?

Since I don't have Latin in my target languages list, I don't expect it to be transited to Latin. I like it to remain as it is because these are some NAMES.

Sorry, do you mean translated from latin here? What is your target language? Target language is a key bit of information here that would help us reproduce and resolve.

I can confirm this is an issue/edge case with the translation API, which is out of scope for us to fix in the extension.

We could potentially add a workaround - the extension could accept an escape token for users to manually tag proper nouns.

I am going to close this issue for now, if such a feature would be helpful to you then feel free to open a fresh issue, or reply to this thread and I can open one for you.

curl -X POST \
  -H "Authorization: Bearer $(gcloud auth application-default print-access-token)" \
  -H "Content-Type: application/json" \
  -H "X-Goog-User-Project: <PROJECT_ID>" \
  -d '{
    "q": "ASPENDOS & PERGE & SIDE",
    "target": "es",
    "source": "en"
  }' \
  "https://translation.googleapis.com/language/translate/v2"

Hi @amin79

This PR #2254 resolves this issue by introducing V3 translation with glossaries.

It still has to pass through the review process but it should be released with the next version of the extension. Remember that Glossaries are case sensitive and that you need a source language to use them and to have the translation hub enabled in your project. This will make sure that whatever words you want (within the languages specified in the glossary) are translated (or not) in the appropriate manner.

Links and Resources

• Glossary Documentation
• Supported Languages List
• Service Account Key Documentation

Let me know if you have any more doubts.

Thank you for submitting the feature request.

Cheers!
Gustavo ;)