i18n file contains concatenated strings

[bajiat]

The i18n file contains strings that are parts of sentence.

The first rule of software internationalisation is never to use concatenated strings (Ui texts that are built from several parts). They can create localisation problems, because either the person translating does not know, which strings go together or translator cannot use natural word order for the entire sentence in target language, because a sentence has been split.

One example from the Apinf strings:

• "Meanwhile, you may" (key: Not Found.notFound_Message_Part2)
• "return to a previous page" (key: Not Found.notFound_Message_Part3)

All concatenated strings should be combined into entire meaningful text strings. Use parameters for replaceable items, if necessary.

Definition of done

• Find all cases of concatenated strings.
• Modify corresponding template to use only one i18n string in place of multiple parts of string.
• Modify the i18n file to merge multiple parts into one string corresponding template.
• If the strings have been concatenated because of HTML tags, make sure they get included and are not displayed on UI.

[55]

There is a blocking issue with links.
Can't get those to .json files. They don't work from there. Things like <br> or <strong> are working, but not <a href="#">link</a>.

Created related issue on i18n repo - TAPevents/tap-i18n#142