You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For strings like '${mention(sender!, silent: true)} ${inlineLink('said', url)}: ' (the beginning of a quote-and-reply text), where part of it is styled with markdown syntax, or strings like
where the string is fragmented with TextStyle's, expressing them with the regular placeholders is challenging.
For the quote-and-reply string, we could define a string "{user} [said]({link}): ", but that requires the translators to write valid Markdown. We want something like {user} <z>said</z>:, where only said is translatable. In zulip-mobile, we have:
For strings like
'${mention(sender!, silent: true)} ${inlineLink('said', url)}: '
(the beginning of a quote-and-reply text), where part of it is styled with markdown syntax, or strings likewhere the string is fragmented with
TextStyle
's, expressing them with the regular placeholders is challenging.For the quote-and-reply string, we could define a string
"{user} [said]({link}): "
, but that requires the translators to write valid Markdown. We want something like{user} <z>said</z>:
, where onlysaid
is translatable. In zulip-mobile, we have:(See #1148 (comment))
To resolve this, we need to search for a similar API.
For quote-and-reply specifically, we want to translate the string using the realm's locale setting, not the user's.
This is a follow-up to:
The text was updated successfully, but these errors were encountered: