-
Notifications
You must be signed in to change notification settings - Fork 62
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
Proposal for Translating Fastify Website into Spanish #219
Comments
What is the goal of having the readme in spanish, if we can not ensure that we keep it up to date, as not every contributor can write spanish. Also spanish has more writing styles... Should we use argentinian spanish? gallego spanish? ecuadorian spanish? philipinian spanish? |
TBH, if we can leverage AI to translate the website at build time it would be cool. Doing it manually leads to unmaintaned docs. eg:
|
I think we should archive those 😅 I like the idea of ai generated translations at build time |
I think we could maintain a multilingual website, however we lack the resources to maintain multilingual docs. I agree on archiving those repos. |
We should be careful of these automated translations, especially over complex languages with different dialects like Spanish (I've seen such gibberish from AI translations). I'd say that if we can find a willing volunteer who can maintain those translations (not necessarily write all of them, but keep it up to date and flowing) it should be nice to have multilingual support. Not sure if @moradebianchetti81 would like to volunteer, but I can definitely help with the Spanish one if we want to give it a try with a pilot language |
Don't most browsers have translation features built in? For example, visiting https://www.nintendo.com/jp causes the following the pop up in Edge: |
Prerequisites
Issue
hi, i noticed that the fastify website is currently only in English, i wanted to see if there was an idea to translate it into another language such as Spanish.
The text was updated successfully, but these errors were encountered: