In short: text inside workspace textboxes are not translated.
Is this the supposed behaviour or is this a bug?.
Thanks is advance.
Armando
1 Like
If you added a custom field or custom app then Translations does not work but if you want to translate the text and go to the Translation doctype and set the language, source text, and Translated Text that is what you want to the result.
See the Example.
I hope this helps.
Thank You!
Thank you for your reply Nihantra.
This is the original text:
This is the translation from English to Portuguese:
This the result, not working:
Thank you for your help.
Best regards
Armando
1 Like
Login user Language must be the same which you use in translation DocType.
Please check it.
Thank You!
Found the issue/Bug like when You use a Bold Text or Header tag then the word can’t be translated.
When we use simple text then it worked. Please check it.
Thank You!
1 Like
Can you explain this a little bit more?
1 Like
Okay @TurkerTunali,
→ Custom field and Custom app Text/Name
Because By Default field name or default document name is already stored in the translation.csv file but when you added custom names and custom field names cannot be translated. If you want to translate the custom name then you can manage via Translation doctype and create a translation and set the source text and target text according to the language. user language must be the same as you use in translation doctype.
Thank You!
1 Like
Hello Nihantra,
I can confirm that when use simple text, translation works.
Thank you for your assistance.
Best regards
Armando
I thought that it never translated. Anything we translate it with the Translation doctype is great for us.
With whom would you like me to talk about solving this issue?
I’d also like to understand what we can achieve with this feature. We’d like to use software like Frappe Cloud in more than one language.