@max_morais_dmm I love what you did there. This really needed addition. I just have two suggestions:
The current design having an icon over each field where the user click, get a pop up, choose target language, then enter the translation, seems like really time consuming if you want to translate each field in the form, what if:
– Add translate dropdown menu in the top of the form, the dropdown shows
----1- languages already translated, where clicking any of them allows you to edit translation
----2- add new translation, when click shows a popup asking for the target language.
– when adding new translation, the source language value will be in a label on top or under its field, and the field will be cleared ready to enter the translation, and if the user leaves the field empty then its value will be the same as source language.
This way you can translate the whole form at once.
I think each field should have a property “is translatable” as I would assume there are some use cases where you don’t want a certain field to be translated
@ganas that’s an initial prototype, I’m being playing with the options to turn it easy to the end user, and I agree with you that the actual behavior is a time consumer, by the way, is more contextualized, than the active translations
I agree about translatable field, but after discuss some certain situations, I think the best approach is go trought the fields types, is less one configuration, given to you see that icons, you need an specific role too, called “Translator”.
The major issues are the fetches in the code that aren’t not translated today, so, we need to think a bit more, on where to put that changes, to prevent a full refactor in an large among of places.
Lets implement this specifically for Item Description. Maybe a new child table in the Item Doctype that can be linked to a language (?). Will be happy to merge that PR
I’m really in need of this feature too. We’re located in Switzerland where people speak four different languages. Especially in Europe this is crucial for an ERP system.
It’s most important for product description, but would be nice for product name too.
Speaking of products: Where do you see the main difference between description and name? Because in the search fields for products, for example when adding product items to a quotation or an invoice, the auto-complete always shows both name and description. This always looks a bit stupid, considering name and description are often the same content.
@max_morais_dmm I try to use your new function to translate item name and item description but I think it does not work like it suppose to be. I see the earth icon, i can translate my field value to another language but it does not translate on website. Do I need to do something special?
This process seems actively going on. For SEO purposes is very important to have individual paths for the products with different languages (also the URL).
