Open bmarty opened 1 year ago
String to remove from Localazy when the PR will be merged:
screen_account_provider_continue
(replaced by action_continue
)screen_change_server_submit
(was not used)screen_change_server_title
(was not used) I Actually restored this one, used on iOS now (not used on Android)screen_login_submit
(replaced by action_continue
)settings_title_general
(not used)screen_settings_oidc_account
(not used)rageshake_dialog_content
(not used, we are using rageshake_detection_dialog_content
)common_verification_cancelled
(we are using screen_session_verification_cancelled_title
)screen_session_verification_positive_button_ready
(replaced by action_start
)screen_room_details_people_title
(replaced by common_people
)screen_login_password_hint
(replaced by common_password
)screen_login_username_hint
(replaced by common_username
) common_select_your_server
(we use screen_change_server_title
) This one is already deleted 🤔screen_onboarding_subtitle
(unused)@pixlwave can you double check that this will not impact iOS if I remove the strings above?
From the above, we are using the following on iOS:
common_verification_cancelled
: this seems valid to me given it could easily be used in other scenarios (e.g. verifying other users). We also use common_verification_complete
too.common_select_your_server
: this is linked with screen_change_server_title
anyway, so maybe not desperate if we have both, but happy to update iOS if you think it would be better.Other string to remove:
screen_room_retry_send_menu_remove_action
(we now use action_remove
)Updating in EXI: https://github.com/vector-im/element-x-ios/pull/1827
common_select_your_server
→ screen_change_server_title
screen_room_retry_send_menu_remove_action
→ action_remove
Ok, so I will use common_verification_cancelled
.
We will be able to remove
screen_session_verification_cancelled_title
Updating in EXI: https://github.com/vector-im/element-x-ios/pull/1827
Merged on EXI.
Actually the following strings are not used anymore on EXA:
screen_change_server_form_header
screen_change_server_form_notice
screen_change_server_subtitle
screen_change_server_title
screen_login_title
screen_login_title_with_homeserver
screen_server_confirmation_change_server
screen_server_confirmation_message_login_element_dot_io
screen_server_confirmation_message_login_matrix_dot_org
screen_server_confirmation_message_register
screen_server_confirmation_title_login
screen_server_confirmation_title_register
@pixlwave OK to remove those ones?
No, we're using all of these except for screen_login_title
. I'm curious how we've diverged in this way?
Here is a comparative of the 2 apps, Android and iOS:
We do not have the same on boarding flow, that's why the strings are not the same.
There is an issue on Strings between iOS and Android application.
On Android, some strings have been added for submit buttons, like for instance:
https://github.com/vector-im/element-x-android/blob/develop/features/login/impl/src/main/res/values/localazy.xml#L40
instead of using the generic string https://github.com/vector-im/element-x-android/blob/develop/libraries/ui-strings/src/main/res/values/localazy.xml#L19
The value is the same in English, but translations can differ (maybe not for this particular example though), which is not what we want.
We should simplify by removing the extra string entries, and use the generic value when it exists. It will reduce the number of strings to translate and will ensure that Android and iOS are synced. The drawback is that it will not be possible to tweak a value for a particular string by just updating Localazy.
We can use the find duplicate facilities on Localazy to detect identical strings, and probably remove all the duplicates.