You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a representative of a company based in China, we are exploring the potential for adding internationalization (i18n) support to Langflow. Our goal is to broaden the accessibility of Langflow to non-English-speaking users globally.
Motivation
Incorporating i18n support would enhance Langflow’s usability for a wider, global audience. For non-English-speaking users, this could significantly improve user experience and adoption. With an i18n feature, Langflow can reach more diverse markets and encourage a more inclusive environment for all users.
Your Contribution
We would like to know if there is already a plan in place for adding i18n support. If not, we are willing to contribute an implementation for i18n. Given that this is a significant change to the codebase, we would like to discuss the best approach to ensure a smooth integration.
If there are any discussions regarding this, please let us know, as it would be helpful to coordinate efforts.
The text was updated successfully, but these errors were encountered:
Feature Request
As a representative of a company based in China, we are exploring the potential for adding internationalization (i18n) support to Langflow. Our goal is to broaden the accessibility of Langflow to non-English-speaking users globally.
Motivation
Incorporating i18n support would enhance Langflow’s usability for a wider, global audience. For non-English-speaking users, this could significantly improve user experience and adoption. With an i18n feature, Langflow can reach more diverse markets and encourage a more inclusive environment for all users.
Your Contribution
We would like to know if there is already a plan in place for adding i18n support. If not, we are willing to contribute an implementation for i18n. Given that this is a significant change to the codebase, we would like to discuss the best approach to ensure a smooth integration.
If there are any discussions regarding this, please let us know, as it would be helpful to coordinate efforts.
The text was updated successfully, but these errors were encountered: