Unify terminology

• jami-client-ios#382 (closed)

• jami-client-qt#1730 (closed)

• jami-web#208 (closed)

• The client should be reviewed to homogenize strings with other platforms.

• Text case should be homogenized.

• Use common base files for translation in Transifex

• Review all clients to homogenize strings

1. Should sucess be:
   (a) success

• https://review.jami.net/c/jami-client-android/+/28428/1/jami-android/app/src/main/res/values/strings.xml#591

Thank you

cc: @pnicolas @aberaud

changed the description

Also block yourself is still possible on Android and iOS? #1371

To do: link this ticket in this commit.

marked this issue as blocked by jami-client-qt#1730 (closed)

added i18n severitymedium sprintbacklog typerefactor wording labels

Unable to download to find string to update to Start audio call/Start video call jami-client-qt#1730 (comment 51880)

$ git clone ssh://ovari@review.jami.net:29420/jami-client-android.git
Cloning into 'jami-client-android'...
remote: Counting objects: 62, done
client_loop: send disconnect: Broken pipe.97 MiB | 180.00 KiB/s
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

https://review.jami.net/q/topic:%22unify-terminology%22

https://review.jami.net/c/jami-client-android/+/28608

Desktop client

Android client

#1741 (closed)

For consistency with Desktop client:

1. Should About be changed to:
   (a) Settings
2. Should Documents be changed to:
   (b) Files
3. Should About (or if renamed to Settings) be the last tab?

Thank you

mentioned in commit afddae7a

• Should take be accept?
• Should in be with?

1. Should Take call be:
   (a) Accept call
2. Should Answer in audio be:
   (a) Answer with device audio
   (b) Accept with audio
   (c) Accept with audio only
   (d) Accept with voice
   (e) Accept with video and hold other calls
   (f) Accept incoming call with audio only
   (g) Answer with audio
3. Should Answer in video be:
   (a) Accept with video
   (b) Accept incoming call with video
   (c) Answer with video
4. Should Hold and take call audio be:
   (a) Accept incoming call with audio only and hold current call
   (b) Accept with audio and hold current call
   (c) Accept with audio and hold other calls
5. Should Hold and take call video be:
   (a) Accept incoming call with video and hold current call
   (b) Accept with video and hold current call
   (c) Accept with video and hold other calls
6. Should End and take call be:
   (a) Accept incoming call and end current call

Thank you

https://review.jami.net/c/jami-client-android/+/28869

mentioned in issue #1752 (closed)

1. In appropriate situations, should Can\'t, Can't, Cannot, Won't, Won\'t be changed to:
   (a) Unable to
2. In appropriate situations, should can\'t, can't, cannot, won't, won\'t be changed to:
   (a) unable to

Thank you

jami-client-qt#1730 (comment 53057)

mentioned in issue jami-client-qt#1730 (closed)

• In appropriate situations, should view be visit?
• Should website be webpage as a page is opened?

1. Should View website be:
   (a) Visit webpage

Thank you

mentioned in issue jami-daemon#1056

https://review.jami.net/c/jami-client-android/+/28920

mentioned in commit 9b50c919

mentioned in commit e4e49419

1. Should like to and Are you sure you want to be:
   (b) Do you want to
   (c) Do you really want to

Thank you

https://review.jami.net/c/jami-client-android/+/29184

https://review.jami.net/c/jami-client-android/+/29175

#1778 (closed)

1. Should Started a call be:
   (a) Conference call in progress
   (b) Call in progress

jami-android/app/src/main/res/values/strings.xml

    <string name="ongoing_group_call">Ongoing Call</string>
    <string name="started_call">Started a call</string>

Or

2. Should Ongoing call be:
   (a) Conference call in progress
3. Should Started a call be:
   (a) Call in progress

Thank you

mentioned in issue #1167 (closed)

mentioned in commit 2cf6b910

mentioned in commit 3c2635f2

mentioned in issue jami-web#208 (closed)

changed the description

closed

https://review.jami.net/c/jami-client-android/+/29693/13/jami-android/app/src/main/res/values/strings.xml#366

• %1$s was invited to join the conversation.
• %1$s has joined the conversation.
• %1$s has left the conversation.
• %1$s was blocked from the conversation.

The strings show up in notifications on the Qt client (yet at the moment they are broken show shows as blank messages). Should they be similar to "Connection Established" notification below?

The strings in Android have been updated to hopefully be consistent with the Desktop clients and iOS client.

Adding "the conversation" in the strings may also help with obtaining better translations as the context is not always known.

The "blocked" message should have "conversation" as other blocks could happen such as A presenter blocked attendees from sending video. There are other scenarios which blocked can be utilized.

@aberaud

@ovari There might be different strings for the notification. Or the notification title might simply be the group name, and these strings used as the notification message, for instance:

Collaborative editor
'Bob' was invited

@aberaud the string should be fine in the notification message.

mentioned in commit 8a3ecde3

mentioned in commit 4943d019

mentioned in issue #1850