Multiple language support

[SlyAceZeta]

Japanese especially, obviously, but a modular system to allow for multiple translations would be handy. If someone has not selected a language, we could have a modal pop-up when they first enter the site and then have it also accessible from the settings modal.

• [ ] Interface (form labels, placeholders, etc.)
• [x] Species dropdown
• [x] Ball dropdown
• [ ] Origin Mark dropdown
• [ ] Origin Game dropdown
• [ ] Current Game dropdown
• [x] Nature dropdown
• [x] Title dropdown
• [x] #43
• Mint dropdown removing per #62
• Ability dropdown removing per #62
• Characteristic dropdown removing per #62

[SadisticMystic]

PKHeX has the relevant strings for this arranged at https://github.com/kwsch/PKHeX/tree/master/PKHeX.Core/Resources/text/other . Most of them should be easy to parse, except the list of forms for when you get around to that.

[SadisticMystic]

In German, as well as the Asian languages, the title associated with a ribbon is placed before the Pokemon's name, rather than afterward as it does in ENG/FRE/SPA/ITA. Is it worth creating an extra semantic property for each language and possibly reversing the placement of name and title if a language is set that calls for it?

[SlyAceZeta]

In German, as well as the Asian languages, the title associated with a ribbon is placed before the Pokemon's name, rather than afterward as it does in ENG/FRE/SPA/ITA. Is it worth creating an extra semantic property for each language and possibly reversing the placement of name and title if a language is set that calls for it?

I've moved this to #43 as it's a related but separate issue.