=== Value proposition (why do we need to do this)?
As a user, I want to be able to add translations for a file so I can use the file in my local language.
This follows up from {T204596} and {T204849}.
=== Functionality/software changes
* Once the user has picked an image, they land up in the Translate view.
* Header:
** [] Button to go back and pick another file
** [] File title and link to see image on Commons
** [] Language settings dialog
** [] Login button (non-functional)
* Translation panel:
** [] In the 'from' language dropdown show 'Default' and give user the default language if one, if not give the user English
** [] The 'to' language dropdown should show the ULS with all languages with the 'Preferred languages' on top - the ones user picked in the language settings dialog (see mock for more details). The default option is 'Select a language'.
** [] Language labels on left
** [] Translation inputs on right
** [] Divider line clustering labels which fall under the same 'text' tag (follows from T202771)
* Image
** [] Image is sticky on scroll
* Buttons to upload image to Commons and download image above the image (both are non-functional for this ticket)
=== What this ticket does not include:
* Preview functionality
* Upload/download functionality
* Mobile compatibility (it's great if we get that for free but let's not include additional work for that in this ticket, it should be estimated separately)
=== User interface changes
==== Screenshots/mockups:
Mockup: https://prtksxna.github.io/svgtranslate-prototype/translate.html
{F26501292, height=400}
=== Does this need QA?
Yes