Azure Custom Translator incorrectly handles Markdown files

David Márquez Fàbrega 16 Reputation points
2022-03-14T07:23:53.063+00:00

Using the custom translator I'm finding multiple issues with Markdown.

When the targets are created, make sure that in **Type** you select **Mobile**. gets translated to Cuando se crean los objetivos, asegúrese ** de que en Tipo ** seleccione **Mobile**.. As you can see the bold text of Type is lost (only the word Tipo has to be inside the bold marks, not de que en Tipo).

Result:

When the targets are created, make sure that in Type you select Mobile

Cuando se crean los objetivos, asegúrese ** de que en Tipo ** seleccione Mobile

The no-loc flag extension is translated from :::no-loc... to ::no-loc... (it looses one double dot).

|-|-|
| :::no-loc text="TEST"::: | Number of weekly services |
| :::no-loc text="AVGBORN"::: | Total born average |
Azure Translator
Azure Translator
An Azure service to easily conduct machine translation with a simple REST API call.
408 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.