=== Value proposition (why do we need to do this)?
* As a user, I want to be able to set the language I see the tool in so I can use it more efficiently.
* As a user, I want to be able to set language(s) I prefer so the tool can show those near the top of the language list when selecting languages for translating and I don't have to scroll through the language list every time.
I combined these two user stories here because the functionality is very similar.
=== Functionality/software changes
[] Option to change the tool interface language
** This uses ULS (or ULS backend like VE does see F26064883) for selecting language.
** The language user picks persists across sessions.
[] Option to set preferred languages
** This uses ULS (or ULS backend like VE does see F26064883) for selecting languages.
** The languages user picks persist across sessions.
=== User interface changes
==== Screenshots/mockups:
{F25780774}
==== Interface text/changes:
* ...
* ...
=== Does this need QA?
Yes