Skip to content
  1. Sep 28, 2019
  3. Sep 27, 2019
  5. Sep 26, 2019
  7. Sep 25, 2019
  9. Sep 24, 2019
  11. Sep 22, 2019
  13. Sep 21, 2019
  15. Sep 20, 2019
  17. Sep 19, 2019
  19. Sep 18, 2019
  21. Sep 16, 2019
  23. Sep 15, 2019
  25. Sep 13, 2019
  27. Sep 12, 2019
    • Daniel Gultsch's avatar
      when parsing omemo messages ensure we only find one element · e395da18
      Daniel Gultsch authored
      e395da18
    • Daniel Gultsch's avatar
      inherit language from parent message when finding localized body · a7c47a33
      Daniel Gultsch authored
      a7c47a33
    • Daniel Gultsch's avatar
      show language in message bubble if multiple language variants were received · 9bf5fb98
      Daniel Gultsch authored 
      XML and by inheritence XMPP has the feature of transmitting multiple language
variants for the same content. This can be really useful if, for example, you
are talking to an automated system. A chat bot could greet you in your own
language.

On the wire this will usually look like this:

```xml
<message to="you">
  <body>Good morning</body>
  <body xml:lang="de">Guten Morgen</body>
</message>
```

However receiving such a message in a group chat can be very confusing and
potentially dangerous if the sender puts conflicting information in there and
different people get shown different strings.

Disabeling support for localization entirely isn’t an ideal solution as on
principle it is still a good feature; and other clients might still show a
localization even if Conversations would always show the default language.

So instead Conversations now shows the displayed language in a corner of the
message bubble if more than one translation has been received.

If multiple languages are received Conversations will attempt to find one in
the language the operating system is set to. If no such translation can be
found it will attempt to display the English string.

If English can not be found either (for example a message that only has ru and
fr on a phone that is set to de) it will display what ever language came first.

Furthermore Conversations will discard (not show at all) messages with with
multiple bodies of the same language. (This is considered an invalid message)

The lanuage tag will not be shown if Conversations received a single body in
a language not understood by the user. (For example operating system set to
'de' and message received with one body in 'ru' will just display that body as
usual.)

As a guide line to the user: If you are reading a message where it is important
that this message is not interpreted differently by different people (like a
vote (+1 / -1) in a chat room) make sure it has *no* language tag.
      9bf5fb98
    • Daniel Gultsch's avatar
      pulled translations from transifex · 9273ba56
      Daniel Gultsch authored
      9273ba56
  29. Sep 11, 2019
  31. Sep 10, 2019
  33. Sep 09, 2019
  35. Sep 08, 2019