Separate call/messages dnd summary string
The translation for call/messages may be feminine or masculine depending on the language which changes the way this string should be translated. Therefore, separate the string to prevent bad translations. Test: manual Fixes: 154687360 Change-Id: I3cbef72d41626a244ce82a0d0574427fb9c4462e
This commit is contained in:
@@ -150,10 +150,9 @@ public class ZenModePrioritySendersPreferenceController
|
||||
case KEY_CONTACTS:
|
||||
return mBackend.getContactsNumberSummary(mContext);
|
||||
case KEY_ANY:
|
||||
return mContext.getResources().getString(R.string.zen_mode_all_senders_summary,
|
||||
mContext.getResources().getString(mIsMessages
|
||||
? R.string.zen_mode_messages_list
|
||||
: R.string.zen_mode_calls_list));
|
||||
return mContext.getResources().getString(mIsMessages
|
||||
? R.string.zen_mode_all_messages_summary
|
||||
: R.string.zen_mode_all_calls_summary);
|
||||
case KEY_NONE:
|
||||
default:
|
||||
return null;
|
||||
|
Reference in New Issue
Block a user