New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multilingual Improvements for Frappe #4483
Comments
Simply fantastic!!! Love it! |
Hi Max, I am new to github, can you help me how to pull this feature to my local installation and implement it, please. !! |
Is this going to be merged? |
This is great!! |
Dear aptech-admin how can I fork to your pull request. I want to test the awesome feature introduced by you. |
This sounds very good. I was just comparing some ERPs for a project and was sad that I can't use ERPNext due to missing multilingual features but this sounds promising, especially if not restricted only for product description. That would make the website mixed of different languages. |
This is absolutely great. I hope it will be merged into master soon. |
How about the progress of this merger? |
This has been merged, #5002 |
yeeeeeeeee |
Edited the DocType, so the field can be "Translated" but it isn't working. v12.1.2, trying to translate given Department, employment type etc. Any help on that? :) |
I am having the same issue I wish it would work out of box. Any progress on this? |
Multilingual Enhancement
Introduction
In countries where multiple languages are used, it is often a requirement to be able to communicate in the language of a customer or supplier. With this requirement in mind, and knowing that ERPNext already had the basis needed to achieve this, the challenge was to develop a tool that would cover as much as possible, but wihtout needing too much modifications to the core system.
Description
This modification add content translation at the field Level for the following type of fields:
For example, it enables translation of "Item Name" and "Description" of an Item. Also, and equally important, translation of Standard Reply, Blog and Web Pages is supported . All translations are stored in the Translation DocType of ERPNext. The accessibility of this feature is controlled by a Role named Translator. Only users with this role can access and modify translations.
The modification also add the possibility to enable / disable languages within ERPNext. This help to narrow the choice of translations offered to users to only those who are needed within the context of the company.
By nature, translations cannot be accessed within a dialog window.
Usage
First thing to do is to enable only the languages needed by external communications in the Language DocType.
Then assign the "Translator" role to concerned users.
Translations can be accessed by a small "earth" icon which can be found on the right of the label of every translatable field. There must be some text inside the field for the icon to appear. The icon will be grey if no translation exist and orange otherwise.
Inside the Translation dialog, the source text is displayed along with enabled languages, each on a separate collapsible section. Inside the collapsible section there is a text field in which the translated text must be entered. Translations are saved when the "Translate" button is pressed.
Next Steps
In continuation of:
#4288
And some clear discussion here:
https://discuss.erpnext.com/t/multilingual-item-description-terms-and-conditions-emails-etc/26601
@aptech-admin
@rmehta
The full change can be viewed here
develop...Aptitudetech:multilingual
We need to know, what else is needed from us of frappe team, to we get integrated into the core.
The text was updated successfully, but these errors were encountered: