[Feature] Internationalization (i18n) support to the editor

[sharat87]

Having internationalization (i18n) in the editor canvas can help more diverse teams work on developing applications togather.

Front conversations

[yych42]

I’m trying to contribute to i18n, but unfortunately, I don’t have the technical resources to change the existing codebase. I found this framework, which I think might help to integrate i18n in the future. I hope this helps & would be very happy to contribute to Chinese localization once the infrastructure is in place.

https://github.com/formatjs/formatjs

[Nikhil-Nandagopal]

Thank you for the wonderful contribution @chen-yaoyu! We'll definitely keep this in mind when we restructure our codebase for i18n :)

[President]

I agree - this is very important for wide spread of AppSmith. Unfortunately not all of our clients can use English :-( I realize it may be hard to translate to all languages. So the best way can be be to allow developers to define all texts for all placeholders for every used control. Ideally few texts for few languages - so we could allow to select language by our users.

[vmulholl]

Hello, I'd like to show my interest in having the widgets show other languages as well (French is the most pressing one for myself). Ex. the table widget "filter", "download" etc. buttons For now I can try hiding the bar and creating interactive filters between 2 widgets. Let us know if we can help with the translations!

[shossur]

We can apply the localization support to the application developed using appsmith right? Also wanted to understand what is the timeline to complete this issue?

[IAIOMAN117]

Hi, I also like to show my intereset in having the widgets have option to display in other languages, my case is Spanish, more precisely in Latin American spanish, as the users I have for the app are Mexican and not all of them read english fluently.

Is there any ETA for the feature within the current RoadMap? If needed, I can help providing the necessary text translations if I receive the original texts.

[okaeiz]

Is this issue still open? How can I contribute to translate and localize Appsmith?

[onemoreahmad]

+1

[ame-appsmith]

Another user wanted to have the app translated into Chinese.

[maiconramos]

+1

[thomas-jablonski]

+1

[abutalha]

Please add Arabic and RTL support. we can bring you a huge user base.

[vishaldfreak]

We're trying to build ERP for our operations which are handled multiple countries India, China, Dubai, Thailand. It would make the whole app much more user friendly if the UI text, menus, everything could be translated to local language on select of a menu button.

[talmannn]

Hi. If would give ability to contribute localisation, I'd help with russian, ukrainian and hebrew. Also, RTL support would be a huge advantage.

[shossur]

+1

[harshaPatilG]

Hi, I see, this ticket is opened on May 2021, how early can we expect this feature?

[shossur]

I have 1 clarification appsmith is developing this feature for appsmith tool or internationalization support for application developed using appsmith also? If yes how the application developer will be defining the translation text from the appsmith tool?

[jansenfavero]

Olá! desenvolvo soluções web para gestão de informações para empresas e governos locais aqui no Brasil, gostaria muito de poder personalizar os textos de datas, filtros e campo de busca, no AppSmith

[Nikhil-Nandagopal]

@harshaPatilG @shossur @jansenfavero we currently don't have this on our roadmap. We will update here once we plan it

[IAIOMAN117]

Almost a year since I started to try to move the applicaiton I made from PoC to MVP, but sadly my users speak spanish only and the usability for them is very limited. I understand that this might not be on your roadmap, but there must be a way to at least workaround it. And I mean for the text that are inside the controls, If this could be added at least to the settings of each control I can deal with having to manually override each and single of them, but not having the posibility is a deal breaker for me.

[vidz1979]

+1... this is a must have for non-english countries. My application is "half translated" components are in english language and the rest of application is portuguese. Also I receive notifications from Google Chrome to translate page from english to portuguese because page language metadata is en-US.

@Nikhil-Nandagopal,

Have you tried an iterative approach in the case of internationalization? My thoughts: 1) adopt a language setting in application level 2) start to inform language setting in HTML metadata to avoid Chrome confusion (portuguese application with english meta) 3) set adopted components with application language setting. Eg: Uppy (FilePicker), DatePicker, etc. 4) lastly, adopt a translation system for the general UI of Appsmith (the hardest thing I guess)

[Nikhil-Nandagopal]

@vidz1979 so are you suggesting that right now you just want a way to specify the language so that chrome does not pop-up with this annoying notification? I agree with your approach here and we do plan on introducing language packs for all our widgets in the future but as you said that is a hard thing to achieve and we want to get it right.

[vidz1979]

Hey @Nikhil-Nandagopal, thanks for the feedback!

Yes, first step is let Chrome know about language used in the app

Second, about components language, I think many of components used by Appsmith are already translated, like FilePicker (powered by Uppy - https://uppy.io/docs/locales/#using-a-locale-pack-from-npm), it's only needed to pass down locale setting:

import Uppy from '@uppy/core';
import German from '@uppy/locales/lib/de_DE';
const uppy = new Uppy({
    locale: German,
});

---

Apart from this, I think that are two approaches for app translation:

• single language app: app has only one language (this is achieved by using the above steps).
• multi language app: app design is done in english, and every string is translated to targeted languages. Users can choose which language they'll use (or simply let the browser language by default).

The other aspect is Appsmith translation itself (login screen, home page, settings). It is a different thing and can be done concurrently.

[gehtalles-de]

@Nikhil-Nandagopal Is this topic anywhere on the actual development roadmap? Native language management would be a very important feature for me (and I guess many others from non-english speaking countries) to use Appsmith for business use cases..

Speaking about the frontend user, not the app developer. So at least all the component placeholders and such should be translatable in a way.

[vidz1979]

@gehtalles-de totally agree. It's a must have.

[guntribam]

Please put this in you priority backlog

[ayeah]

Another user wanted to have the app translated into Chinese.

A chinese version has been released, called pageplug, but it uses old version of appsmith, I still want official i18n support, please add this feature, allowing cummutity members to translate and share language pack files, including editor and apps.

[victorcai2006]

Another user wanted to have the app translated into Chinese.

A chinese version has been released, called pageplug, but it uses old version of appsmith, I still want official i18n support, please add this feature, allowing cummutity members to translate and share language pack files, including editor and apps. Yes, I also found that the version of Pageplug is older and there are some bugs that have not been fixed, so I just use AppSmith. If I can, I can also provide my help for the sinicization of Chinese.