multi-language support

[StegSchreck]

Basic idea for the application context (not individual's cv data):

• having a JSON or properties file per language containing the translated keywords
  • open question: 1 file per language per component or 1 file per language for the entire application?
  • keywords should represent application structure, e.g. education.languages.title
• depending on which files are present, fill a selection dropdown
• selection dropdown to be placed in the header
  • header title text placement boundaries to be adjusted
  • language selection is a state. where to store? cookie?

For the individual's CV data (e.g. current employer's name and description) a different approach could be taken.

• copy of cv-items.data.ts containing same items (or even different?!?) but in different language
• enriching the structure of existing cv-items.data.ts with a layer representing the language chosen by selected language (see above)

Inspiration

• https://usersnap.com/blog/design-language-switch/
• http://www.flagsarenotlanguages.com/blog/best-practice-for-presenting-languages/

[StegSchreck]

• new component l10n offers the visitor to switch the language
  • selected language is stored in the browser's local storage
  • default is depending on what is configured in the feature-toggles.data.ts
• non-individual data is retrieved from l10n.data.ts via l10n.service.ts
• individual's cv-data is still only configurable in multiple languages so far --> Ability to maintain CV data in multiple languages #23