Project

General

Profile

Actions

Feature #1876

closed

Language configuration

Added by Moritz Großfurtner over 1 year ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Start date:
2022-11-15
Estimated time:

Description

Make choice of languages configurable.
  • Set default ✅
  • Selected language should be persitent through the use of local storage. ✅
  • English & German are supported out of the box. Others can be added the same way. ✅

Related issues 1 (1 open0 closed)

Precedes OpenAtlas Discovery - Feature #2044: Additional language featuresAcknowledged2022-11-16Actions
Actions #1

Updated by Moritz Großfurtner about 1 year ago

Currently we are using vue i18n and it works well. I've discovered https://v8.i18n.nuxtjs.org/ which might be usefull if we want better SEO depending on the language as well as a few other features, though I'm not sure if it is necessary for our use case.
E.g. it also allows for persisting the language selection. However, it does so through the use of cookies, so I'm not sure if we want that.

Actions #2

Updated by Moritz Großfurtner about 1 year ago

It might also be a good idea to use this: https://github.com/olizilla/lol
For creating a list of locales to select from. Especially when adapting OAD for a different Project with more supported languages.

Actions #3

Updated by Moritz Großfurtner about 1 year ago

  • Status changed from Acknowledged to Resolved

It should work now, but if we decide to go with nuxt-i18n I'd need to look into it again.

Actions #4

Updated by Moritz Großfurtner about 1 year ago

  • Assignee set to Moritz Großfurtner
Actions #5

Updated by Alexander Watzinger about 1 year ago

I kind of avoid SEO and cookie topics in the backend but of course you are right, for presentation sites this absolutely makes sense.
SEO can't hurt for public available websites that present project results, when using cookies we will need a cookie disclaimer thingy but I guess, we will need that in the long run anyway.

Sadly I can't comment on the technical site of things but I added other frontend developers as watcher, maybe they want to comment too. You can always add watcher yourself in case you think this might be interesting for others.
Thank you for looking into this.

Actions #6

Updated by Moritz Großfurtner about 1 year ago

  • Assignee deleted (Moritz Großfurtner)

Thanks for the feedback and adding the others!
I'd try to avoid cookies as much as possilbe as well, but yes if we end up using cookies we'll defenitely need to add a disclaimer.

Actions #7

Updated by Moritz Großfurtner 9 months ago

  • Description updated (diff)

What still needs to be done is the integration of the navigation for nuxt content pages taking into account the selected locale.

Actions #8

Updated by Moritz Großfurtner 9 months ago

  • Status changed from Resolved to In Progress
Actions #9

Updated by Moritz Großfurtner 8 months ago

At the moment new locales can only be added by us in the main repository. Should it be possible for our partners to add their own .json files containing other locales? At the moment that would be needed to enable them to add support for multiple languages.
Additionally: How do we handle content in other languages that aren't supported in the user interface. Do we allow it?

Actions #10

Updated by Alexander Watzinger 8 months ago

Actions #11

Updated by Alexander Watzinger 8 months ago

I would say for completion of this issue it should be possible to set a default display language in the user managed configuration.
Adding additional content languages even if no user interface translations are available has no high priority so I created an extra issue in the wishlist (#2044).

Actions #12

Updated by Moritz Großfurtner 7 months ago

  • Status changed from In Progress to Closed

Implemented as planned and can be expanded upon in further features as suggested by @Alexander Watzinger .

Actions

Also available in: Atom PDF