Internationalization of Content

[Daniel257P]

What's missing from the TRIP Guides

• Implement internationalization (i18n) support for the Trip Protocol project, ensuring that content is easily adaptable for users from diverse linguistic backgrounds.

Gist of expected content

• Explain how users will be able to choose their preferred language.
• The update on documentation for different languages
• Address the need to involve the community in contributing translations for additional languages.

Gist of current content

Currently there are no topics that specify directions on how to internationalize content in different languages.

[Alejandro1954-ops]

@Daniel257P could you specify what you mean? Content in different languages?

[Daniel257P]

@Daniel257P could you specify what you mean? Content in different languages?
In addition to documents such as a Litepaper, FAQ, and other guides, explain how the app can be set to the preferred language of drivers and passengers.

[Alejandro1954-ops]

@Daniel257P got it. I know TRIP is focused on US, specifically Texas, growth for now.

But as the network grows internationally with launched cities, I do not any reason as to why this cannot be implemented. It will require ongoing contributor work and adding language preference functionality by the dev team.

[hwhelchel]

@Daniel257P thanks for your contribution here. Internationalizing the Teleport app is out of scope of this issue.

That said, we could use content that explains:

• Principles to translating TRIP Guides content into other languages
• Where that international content should live from an information architecture perspective
• How that content is or isn't kept in sync with the English content

Since the Guides is under such heavy change right now I don't see internationalization being feasible without it being something like how Rails the popular open source project manages their translations:

It might be feasible to do something even more automated with AI or an translation API now or in the near future.