You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some developers dont use their static translations like this: {{'Good morning'|t}}
But like this: {{'homepage_welcome_message'|t}}
Reason for this is making translations more robust - with first option if i wanted to change english "good morning" string to something else, ("good day" maybe?) all other languages translation variables attached to this string would stop working. Even changing first letter to capital would break translations.
However, using 'homepage_welcome_message' in enupal translate plugin is not perfect for translating staff. Lets say they want to translate from english to german. They just see "homepage_welcome_message". If they saw multiple languages, they would see default value "homepage_welcome_message", but also english translation of it - "welcome" and then input that they have to fill in with german translation.
The text was updated successfully, but these errors were encountered:
@andrelopez What more info do you need? The last part of the post is a bit confusing, but I think I understand the ask.
If I understand correctly, this is a feature request to display the translation from the site's default language as an additional column in the Translations listing. This is so translators can refer to it instead of the translation string from the template, which may just be a placeholder name like homepage_welcome_message.
e.g.
This, where the French translator can refer to the English translation.
Template
English (default)
French (current)
"morning_greeting"
"Good Morning"
"Bonjour"
Instead of this, where the French translator has to switch to English to check the English phrase they're supposed to translate.
Template
French (current)
"morning_greeting"
"Bonjour"
Edit: Kay... I guess I don't know how to make markdown tables on GitHub. I even copied the one from their markdown guide and it doesn't work. Hopefully you get the point :)
I was just thinking it might be useful for the translator to be able to pick any available locale as the reference language, since they may have an easier time translating from a language other than the default language.
Some developers dont use their static translations like this:
{{'Good morning'|t}}
But like this:
{{'homepage_welcome_message'|t}}
Reason for this is making translations more robust - with first option if i wanted to change english "good morning" string to something else, ("good day" maybe?) all other languages translation variables attached to this string would stop working. Even changing first letter to capital would break translations.
However, using
'homepage_welcome_message'
in enupal translate plugin is not perfect for translating staff. Lets say they want to translate from english to german. They just see "homepage_welcome_message". If they saw multiple languages, they would see default value "homepage_welcome_message", but also english translation of it - "welcome" and then input that they have to fill in with german translation.The text was updated successfully, but these errors were encountered: