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
Complete the remaining tasks related to the translation infrastructure. This issue is an EPIC and will be divided into sub-issues. It follows closed issues #1656, #1527, and closed PRs #1690 and #1648.
Where the work begins: If additional dependencies can be avoided, it is a good thing. The first step is to evaluate the need for using the vue-i18n library, figuring out the most convenient and long-lasting approach to implement translation extraction from Vue components.
Who are the users that would benefit from the enhancement and how?
Skosmos users worldwide will have better access (user experience) to Skosmos in their preferred or native languages. Additionally service providers will be able to offer language features more easily and effectively.
(Name specific organizations, roles and/or communities if possible, and/or point to relevant discussion elsewhere)
What new functionalities would the enhancement make possible?
Support for translations in Vue components (additions to new components where needed as with the previous Vue components -> create a checklist for this)
Extraction of translations from Vue components using the Symfony console
Documentation and instructions for translation functionalities
Why is the enhancement important?
Skosmos is widely used around the world, so multilingual support is essential.
(Why should this be prioritized, instead of spending energy on something else? Who would do the work to make this happen?)
The text was updated successfully, but these errors were encountered:
Description of the enhancement
Complete the remaining tasks related to the translation infrastructure. This issue is an EPIC and will be divided into sub-issues. It follows closed issues #1656, #1527, and closed PRs #1690 and #1648.
Has sub-issues:
#1713
Where the work begins: If additional dependencies can be avoided, it is a good thing. The first step is to evaluate the need for using the vue-i18n library, figuring out the most convenient and long-lasting approach to implement translation extraction from Vue components.
Who are the users that would benefit from the enhancement and how?
Skosmos users worldwide will have better access (user experience) to Skosmos in their preferred or native languages. Additionally service providers will be able to offer language features more easily and effectively.
(Name specific organizations, roles and/or communities if possible, and/or point to relevant discussion elsewhere)
What new functionalities would the enhancement make possible?
Why is the enhancement important?
Skosmos is widely used around the world, so multilingual support is essential.
(Why should this be prioritized, instead of spending energy on something else? Who would do the work to make this happen?)
The text was updated successfully, but these errors were encountered: