hestiaAI / hestialabs-experiences

HestiaLabs Data Experiences & Digipower Academy
https://digipower.academy
Other
7 stars 1 forks source link

Put all text in translation files (refactoring) #929

Open andreaskundig opened 2 years ago

andreaskundig commented 2 years ago

In some places the application still allows text to be defined without a locale as a fallback (for example for the experience title). In other places this fallback doesn't work (for example the experience dataPortalHtml)

This line in TheDataExperience.vue uses t.title directly, without using the internationalization mechanism at all.

    {{ $tev(t.titleKey, t.title) }}

We should just make sure that the title is in the translations, and stop using the $tev fallback mechanism.

valentinoli commented 1 year ago

We need to figure out the priority of this before committing to it. This involves creating a "messages" file for every data experience we have that has not been localized. The essential question is: Do we want to localize every experience by default?

alexbfree commented 1 year ago

The general question we want to ask bizdev is: once we have finished meeting translation requirements for UFC, what is the priority for translating rest of our experiences, do we want to spend time on that?