Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add language support #17

Open
PurkkaKoodari opened this issue Feb 21, 2021 · 0 comments
Open

Add language support #17

PurkkaKoodari opened this issue Feb 21, 2021 · 0 comments
Labels
🌠 feature New feature - accepted for development
Milestone

Comments

@PurkkaKoodari
Copy link
Member

PurkkaKoodari commented Feb 21, 2021

Add support for language versions of events.

The app can be used like most guilds, including Tietokilta, are currently doing: include Finnish and English in the same description field. However, we'd like to implement distinct language versions for each event.

  • The following must be localizable:
    • Event title, description, location, price, website URL, Facebook URL
    • Category (this may be reconsidered, as these should be kept in sync between locales)
    • Quota names
    • Questions
    • Answer options
  • The system might work as follows:
    • The app has a list of allowed locales, likely based on the available UI strings.
    • Each event has a "default" locale (will be migrated from the previous contents).
    • In addition, the editor allows creating additional locales with a specified locale.
  • The language shown should be the same as chosen for the UI strings (Add internationalization for UI strings #93), both in the app and integrated components.
    • If the event does not have that locale, the default locale will be shown instead.
  • Creating a locale must be easy and would likely involve a way to copy values from the default locale.
  • There should be an easy way to update all locales at once.
    • For example, when a field has the same value in multiple locales, and is modified in one, we could automatically update it in all locales or prompt the user to do so.
    • Alternatively, we could have an option to mark fields as "use in all locales" (in the default locale) or "copy from default locale" (in other locales), and that would be enabled by default.
@PurkkaKoodari PurkkaKoodari added the 🔄 enhancement Not a bug or feature label Feb 21, 2021
@PurkkaKoodari PurkkaKoodari added 🌠 feature New feature - accepted for development and removed 🔄 enhancement Not a bug or feature labels Sep 28, 2021
@PurkkaKoodari PurkkaKoodari added 💡 idea New feature idea - not on backlog and removed 🌠 feature New feature - accepted for development labels Oct 27, 2021
@PurkkaKoodari PurkkaKoodari added this to the 3.0.0 milestone Jan 8, 2023
@PurkkaKoodari PurkkaKoodari added 🌠 feature New feature - accepted for development and removed 💡 idea New feature idea - not on backlog labels Jan 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌠 feature New feature - accepted for development
Projects
None yet
Development

No branches or pull requests

1 participant