@byeskille mentionned the possibility of adding a language selection to the journalist / source interface. The simplest way to do it is with a drop down menu, in the same way most web site are expected to.
Echoing what I said in another thread: forcing a user to use the language set in the headers and not allowing an override is just all sorts of UX gore. The user could be using a public computer (library) or the translation might be bunk, and they want to switch languages to remove some of the ambiguity. Etc.
I moved the list of available languages under the SecureDrop logo:
It could be prettier but I suck at web design. If someone provides me with an image that looks better I’ll dot he CSS/HTML integration
The name of the languages are from the iso-639 python module. This may not be the best way and I’m open to suggestions. It feels good that the language names come from an externally maintained list though.
Now to writing tests and make a proper commit out of this.
Not sure what module to use, but definitely it should display the languages
in their native language (e.g., “Deutsch” and not “German”)
alphbetically by their display language (e.g., “italiano” after “espnanol” and not before because in English it’s Spanish)
This is how it’s done on most websites and what will be easiest to use. And it seems like that’s what you’re doing, so well done.
Also, it would be good to display the dialect because this could help a reader understand semantic differences between words that are shared between dialects (e.g., “Deutsch (Deutschland)” ), and we as non-natives in these other languages shouldn’t make any assumptions. Though this last point might be debatable.
that’s what I tried first but it does not fit and that looks really ugly. Instead of trying something creative by myself I thought best to wait until someone with some level of web design skill has an idea Do you know someone by any chance ?