Multi-language tags, formats and other backend names

[maggie44]

Pending upstream change adding in i18n to Strapi: https://portal.productboard.com/strapi/1-roadmap/c/19-content-internationalization-ce-ee-v4

[maggie44]

i18n now implemented to Strapi and installed on our server. Requires coding adjustments to allow for the pulling the correct fields based on language selected.

https://strapi.io/documentation/developer-docs/latest/development/plugins/i18n.html#usage-with-the-graphql-plugin

[maggie44]

Strapi's new feature turned out to be a way to build parallel localised mirrors of the current database. Subsequently, everything from naming, tags and their relations and so forth would need to be redone and maintained for every language. This isn't a particularly useful feature for anyone below large corporations due to the maintenance cost vs benefit.

Subsequently going to put this back on hold pending changes upstream that allows a localisation that entails merely translation of strings, rather than mirroring. Most likely not until Strapi v4 is launched. Although currently using MongoDB database, so may not be able to upgrade immediately as it may not be supported in v4 at launch and may not have migration procedures: https://forum.strapi.io/t/dropping-mongodb-support/4549

For ref: https://forum.strapi.io/t/internationalization-i18n-available-in-strapi-v3-6/4390/5