Skip to content
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

Closed
MaxMorais opened this issue Nov 14, 2017 · 13 comments
Closed

Multilingual Improvements for Frappe #4483

MaxMorais opened this issue Nov 14, 2017 · 13 comments

Comments

@MaxMorais
Copy link
Contributor

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:

  • Data
  • Text
  • Small Text
  • Text Editor
  • Select

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.
image

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.
image
image

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.
image

Next Steps

  • Text inside the dialog to send an email should be in the recipient language, not the user language
  • Work on some kind of DocType where we could associate Standard Replies with DocTypes based on rules, like the Tax Rule. Example, when sending a Sales Invoice by email to an english recipient, Standard Reply X would be automatically fetched.

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.

@cosimot
Copy link

cosimot commented Nov 26, 2017

Simply fantastic!!! Love it!

@shelteradmin
Copy link

Hi Max, I am new to github, can you help me how to pull this feature to my local installation and implement it, please. !!

@cosimot
Copy link

cosimot commented Jan 6, 2018

Is this going to be merged?

@bern-lefebvre
Copy link

bern-lefebvre commented Jan 15, 2018

Hi all,

Here is an update regarding this issue.

  • It was decided to introduce a new field property called "Translatable". This property will control the availability of the "Translation" function.
    image

  • We can now remove the translation from the dialog box:
    image

A new Pull Request as been initiated.

Feedback welcomed

@cosimot
Copy link

cosimot commented Jan 15, 2018

This is great!!

@shelteradmin
Copy link

Dear aptech-admin how can I fork to your pull request. I want to test the awesome feature introduced by you.

@generare
Copy link

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.

@villiger
Copy link

This is absolutely great. I hope it will be merged into master soon.

@kaitorecca
Copy link

How about the progress of this merger?

@netchampfaris
Copy link
Contributor

This has been merged, #5002

@cosimot
Copy link

cosimot commented May 2, 2018

yeeeeeeeee

@iMoshi
Copy link
Contributor

iMoshi commented Sep 11, 2019

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? :)

@Tropicalrambler
Copy link

I am having the same issue I wish it would work out of box. Any progress on this?

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests