Change "." (full stop) to "।" (dandi) in Content Translation when people nare translating from any language to Punjabi.
This seems to be an issue with the external machine translation services. I reported this to Google Translate team, feel free to add more details there or subscribe to the report to get further updates.
We try to avoid making language-specific fixes on top of the output of Machine Translation Services since these get updated over time and patching on top of them tends to be unreliable. Instead, we plan to have a more general system to learn from user corrections (T96165), saving users from correcting the same problem again and again.
Meanwhile, there are a couple of alternatives for editors to correct these issues. For example:
- Individual editors can use the search and replace functionality (ctrl+f) to replace recurrent problems in the translation.
- Communities can create bots to fix common issues in translations after they are published. Those bots can target articles tagged with the "contenttranslation" edit tag or be applied more generally.