Browse Source

Add key naming rules for dialogs.

test/jme/compound-poc
Benoit Marty 1 year ago
parent
commit
00adf78eeb
  1. 1
      tools/localazy/README.md

1
tools/localazy/README.md

@ -27,6 +27,7 @@ For code clarity and in order to download strings to the correct module, here ar @@ -27,6 +27,7 @@ For code clarity and in order to download strings to the correct module, here ar
- Keys for common accessibility strings must start by `a11y_`. Example: `a11y_hide_password`;
- Keys for strings used in a single screen must start with `screen_` followed by the screen name, followed by a free name. Example: `screen_onboarding_welcome_title`;
- Keys can have `_title` or `_subtitle` suffixes. Example: `screen_onboarding_welcome_title`, `screen_change_server_subtitle`;
- For dialogs, keys can have `_dialog_title`, `_dialog_content`, and `_dialog_submit` suffixes. Example: `screen_signout_confirmation_dialog_title`, `screen_signout_confirmation_dialog_content`, `screen_signout_confirmation_dialog_submit`;
- `a11y_` pattern can be used for strings that are only used for accessibility. Example: `a11y_hide_password`, `screen_roomlist_a11y_create_message`;
- Strings for error message can start by `error_`, or contain `_error_` if used in a specific screen only. Example: `error_some_messages_have_not_been_sent`, `screen_change_server_error_invalid_homeserver`.

Loading…
Cancel
Save