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
The current documentation is only available in English, which may pose a barrier for non-English-speaking users, particularly those who are more comfortable with Japanese. This language barrier can make it difficult for these users to fully understand and effectively utilize the library, potentially limiting the adoption and usage of the library within the Japanese-speaking community.
What is the feature you are proposing to solve the problem?
I am proposing to add i18n (internationalization) support to the documentation, specifically including a Japanese translation. This feature would allow users to access the documentation in their preferred language, making the library more accessible and easier to use for a broader audience. I am willing to contribute by translating the documentation into Japanese if this feature is implemented.
What alternatives have you considered?
If i18n support is not planned, I have considered translating the documentation unofficially and hosting it on a separate platform. This would still provide Japanese-speaking users with access to the documentation in their language, though it would not be as seamlessly integrated as an official i18n solution.
The text was updated successfully, but these errors were encountered:
I have created an unofficial Japanese translation of the documentation, which is now available at https://effect-doc-ja.vercel.app/.
I hope this resource can be of use to Japanese-speaking users who may find it easier to navigate the documentation in their native language. If there’s any interest in officially integrating this translation or in further collaboration, I would be more than happy to contribute.
Additionally, I chose to use Astro instead of Next.js for this project due to its superior development and build speeds. In previous repositories, the development server had significant startup times, which impacted productivity. If there is a move towards official i18n support, I am willing to provide MDX files to support this integration.
What is the problem this feature would solve?
The current documentation is only available in English, which may pose a barrier for non-English-speaking users, particularly those who are more comfortable with Japanese. This language barrier can make it difficult for these users to fully understand and effectively utilize the library, potentially limiting the adoption and usage of the library within the Japanese-speaking community.
What is the feature you are proposing to solve the problem?
I am proposing to add i18n (internationalization) support to the documentation, specifically including a Japanese translation. This feature would allow users to access the documentation in their preferred language, making the library more accessible and easier to use for a broader audience. I am willing to contribute by translating the documentation into Japanese if this feature is implemented.
What alternatives have you considered?
If i18n support is not planned, I have considered translating the documentation unofficially and hosting it on a separate platform. This would still provide Japanese-speaking users with access to the documentation in their language, though it would not be as seamlessly integrated as an official i18n solution.
The text was updated successfully, but these errors were encountered: