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

Spike approaches to internationalisation #1714

Closed
2 of 4 tasks
Tracked by #1708
NickColley opened this issue Jan 24, 2020 · 2 comments
Closed
2 of 4 tasks
Tracked by #1708

Spike approaches to internationalisation #1714

NickColley opened this issue Jan 24, 2020 · 2 comments

Comments

@NickColley
Copy link
Contributor

NickColley commented Jan 24, 2020

What

In #1709, we will hopefully have identified some possible approaches to internationalisation that we want to investigate further. We've also previously spoken about three options:

  1. Using some kind of internationalisation library (how does this work in practice? Is this too complex for what we need?)
  2. Allow services to provide us with the relevant translated string that they want to use (How does this work in situations where we need to deal with multiples/plurals, e.g: character count)
  3. Add a Nunjucks macro option language flag which toggles the component to Welsh (How would we get and maintain Welsh translations now and for future components? Is this scalable?)

We need to make some decisions on which approach would work best for us. We need to keep in mind:

  • We may want to implement a combination of approaches, especially if we have a short-term requirement to provide Welsh translations, but we need something more flexible in future
  • Any approach we pick should work with what service teams are currently doing in their own applications
  • Whether any of these solutions would also apply more generally to configuring more complex components and, if so, how

Why

So that we can get a better understanding of the approaches that work for us.
So that we can talk about the advantages and disadvantages of the approach in any proposal we write and share with the community.

Who needs to know about this

Developers

Depends on

#1709 and #2566

Done when

Note: it's likely that we may want to spike a few different approaches. It may make sense to write up separate cards for each spike when we know what those look like, so that they can be worked on in parallel/by different people. We can then come together to discuss what we've learnt.

  • We've tried out some viable approaches
  • Written up what we've learnt from our spikes
  • Will anything we do here affect ports of GOV.UK Frontend?
  • We have decided on an approach and are ready to share this with teams
@NickColley NickColley changed the title Prototype methods to configure JavaScript in components with options Prototype ways to configure JavaScript in components with options Jan 24, 2020
@NickColley NickColley changed the title Prototype ways to configure JavaScript in components with options Prototype ways to configure JavaScript in components using options Jan 24, 2020
@vanitabarrett vanitabarrett changed the title Prototype ways to configure JavaScript in components using options Spike approaches to internationalisation Mar 1, 2022
@querkmachine
Copy link
Member

querkmachine commented May 23, 2022

There are a couple of draft PRs of a potential approach currently open for feedback.

@querkmachine
Copy link
Member

Shifting this to 'In review' as I think the current spike is in a good place for consideration as to the approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment