How to use the context field in translation doctype?

ME_Technology · August 18, 2023, 1:46am

Omar-Abdullah · June 9, 2024, 6:51am

From my understanding from various posts I read, it is exactly the same value you pass to teh translation function for teh context parameter:

_(“Submit”, context=“Submit a DocType”)
_(“Submit”, context=“Submit a Comment”)

Please see those for better understanding:

github.com/frappe/frappe

Translation with context

opened 02:54PM - 26 Feb 19 UTC

closed 10:10AM - 26 May 20 UTC

barredterra

feature-request paid-development

### Motivation - One phrase can have different meanings in different contexts…. - Fixing an incorrect translation in one context makes the translation incorrect in another context. Get a feeling of the problem: https://www.youtube.com/watch?v=GAgp7nXdkLU Solution: Translations must be context-specific. ### Examples Phrase | Context | Translation (German) ----------|------------|------------------------------ Submit | Accounting | Buchen Submit | Comment | Senden Change amount | POS | Rückgeld Change amount | Stock | Menge ändern ### Proposal - Call the translation function `frappe._()` with a second parameter `context`. ```python _("Submit", context="Submit a DocType") # ... _("Submit", context="Submit a Comment") ``` Alternatively, we could use IDs wherever the text should be inserted and extract some context automatically. - Per default, there is the same translation for all contexts (see 1.) - The translator has the option to provide a different translation for a specific context (see 3.) ![translation_portal](https://user-images.githubusercontent.com/14891507/62430301-0b1d9980-b71b-11e9-8d92-281b9bf48d50.png) The context could also take a different form, such as the route of the view, a screenshot of the UI, or even a dict with more detailed information such as the gender of the user. #### Additional considerations * It should be possible to lock correct translations. (The current system of status points proved to be insufficient for this.) * Consistency of translations across the system must be assured. * The project's terminology and concepts should be defined (for all languages). * How do we address the user (formal or informal)? * How to use common terms ("E-Mail" or "eMail" or "email")? * [Example](https://help.phrase.com/en/articles/2135518-translation-glossary) ### See also * https://github.com/frappe/frappe/issues/2381 * https://github.com/frappe/frappe/issues/2382 * https://github.com/frappe/frappe/issues/19147 (Same issue) * https://discuss.frappe.io/t/enhancement-translation-moudel/259 (Same issue) * https://discuss.erpnext.com/t/specific-translationsindentifiers/13067 (Same issue) * https://discuss.erpnext.com/t/suggestion-retire-erpnext-translator-and-move-to-launchpad-or-similar/20294 (Switch to a different tool that supports context) ### Bounty This feature request is backed financially by the following companies. The bounty is dedicated to an effort to make good translations possible, for which the proposed feature is a necessary basis. If some part of the budget will be left, please propose additional improvements. USD 500.00 by [ALYF GmbH](https://alyf.de/) (@alyf-de) USD 500.00 by [itsdave](https://www.itsdave.de/) (@itsdaveit) USD 500.00 by [Libracore](https://www.libracore.com) (@libracore) USD 500.00 by [LIS Engineering GmbH](https://www.linux-ag.com/) USD 500.00 by [//SEIBERT/MEDIA](https://seibert-media.de/) (@seibert-media) **USD 2500.00 Total** Please leave a comment or text me, if you'd like to contribute as well. Discuss: https://discuss.erpnext.com/t/translations-should-be-context-specific/46114 Final thought: a good translation tool could also [pay](https://phrase.com/de/pricing) [for](https://lokalise.co/pricing) [itself](https://protemos.com/prices.html).