search

LinguistAI / Linguist-AI-MVP

3 stars 0 forks source link

Add dynamic language support (i.e. i18n) #16

Open can-aslan opened 1 year ago

can-aslan commented 1 year ago

Instead of having string literals and/or other hard-typed information shown to users, we can find and use a more structured way that;

https://www.i18next.com/

+ Maintainability, + Reliability, + Supportability, + Accessibility

tolgaozgun commented 1 year ago

Applies to both mobile and spring. @can-aslan would you take the task for technic implementation of localization for React Native part?

tolgaozgun commented 1 year ago

@KardelenCeren would you be interested in localization in the Spring part?

can-aslan commented 1 year ago

@tolgaozgun I have experience with i18n in Spring and React. I can setup both.

can-aslan commented 1 year ago

Will be handled with LINGUIST-62 and LINGUIST-63.

tolgaozgun commented 1 year ago

Will be handled with LINGUIST-62 and LINGUIST-63.

Before implementing could you work on a naming guideline? It should be different for screen titles, component titles texts etc in my opinion.

can-aslan commented 1 year ago

Can you give some examples of what you have in mind?

selimcanglr commented 1 year ago

I think this should not be our priority atm as it might be added in the future (with slightly more effort).