* add strings for 'Invalid Unencrypted'
* add a 'learn more' dialog for 'invalid unencrypted'; the dialog shows the known 'scan qr code' and the known help for it
* clarify wording, add 'for this chat'
* do not linkify domains
* draft a new welcome-message with focus about how to get in contact; the 'Invite Link' implies also contacts with delta chat not installed yet (we could also add a QR code to the invite page as well as adding a 'Manual contact' that fits for classic mail)
* add some dc background info
* rename 'Device Talk' to 'Info'
* Revert "rename 'Device Talk' to 'Info'"
This reverts commit 027e205718c2923bc774a2d069f3283fc9e0e7bd.
* improve english grammar, thanks @adzialocha
the hint already led to confusion on 37c3 testings of chatmail.
the hint that appears when a one-to-one-chat was just created manually
(by entering an email address manually) is a bit misleading when using chatmail,
as it says it 'does not matter if the other side uses Delta Chat'.
this is still true, however, with chatmail it is needed that messages
outside the chatmail-server are encrypted,
which is arguably not so easy without delta chat and QR code scanning.
this PR therefore just removes the hint;
it would still be great if the error message 'cannot encrypt' is improved,
however, this is another thing.
on smaller screens, email address easily is covered by the keyboard;
which will result in lots of confusion
this pr tweaks the or-ornament a little,
without looking much different afterwards
(less padding below, adapted colors)
B. Petersen