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
This is a continuation of #64. That issue was about both an experiment to do to exercise features of Flutter, and a user-facing change to try in the app. We did the experiment and closed the issue, but the user-facing change remains open.
Adapting that issue's description:
Zulip web uses the font Source Sans 3 for most text, and Source Code Pro for code blocks and code spans.
Currently, in much of zulip-flutter as well as in the zulip-mobile RN app, we use system fonts. This has advantages but also disadvantages:
Since #94, we use Source Code Pro for code blocks and code spans, but continue to use system fonts for the rest of the text.
It would be neat to try using the same fonts as on web, for the entire content of messages. Probably for the rest of the message list too: recipient headers, dates, etc.
The text was updated successfully, but these errors were encountered:
This is a continuation of #64. That issue was about both an experiment to do to exercise features of Flutter, and a user-facing change to try in the app. We did the experiment and closed the issue, but the user-facing change remains open.
Adapting that issue's description:
Zulip web uses the font Source Sans 3 for most text, and Source Code Pro for code blocks and code spans.
Currently, in much of zulip-flutter as well as in the zulip-mobile RN app, we use system fonts. This has advantages but also disadvantages:
Since #94, we use Source Code Pro for code blocks and code spans, but continue to use system fonts for the rest of the text.
It would be neat to try using the same fonts as on web, for the entire content of messages. Probably for the rest of the message list too: recipient headers, dates, etc.
The text was updated successfully, but these errors were encountered: