-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TeX in the message list #46
Comments
The dark-theme color, like the light-theme one, doesn't have a source in Figma or the web app. I just chose it from some quick testing on my iPhone. (As the comment says, we'll drop the color when we support katex properly, zulip#46.)
The dark-theme color, like the light-theme one, doesn't have a source in Figma or the web app. I just chose it from some quick testing on my iPhone. (As the comment says, we'll drop the color when we support katex properly, zulip#46.)
We got a request for this as beta feedback in the Google Play Console:
|
And again today:
|
In the Lean community we asked how disappointed people would be if the app were rolled out to all users before full support for TeX. One user answered "heavily disappointed"; others reacted to that message suggesting they disagree. A different user "wouldn't mind" the current state, and another added:
|
See discussion with an idea from Tim:
|
Zulip's Markdown flavor supports TeX for mathematical notation, using KaTeX. This will be one of the more complex message-content features for us to support.
The way this works for web and for the existing RN-based mobile client is:
What I think we'll want to do in Flutter is:
lib/model/content.dart
andlib/widgets/content.dart
.Converting the HTML to Flutter widgets will involve having code in
lib/widgets/content.dart
that is written to correspond to the KaTeX CSS, just like much of the existing code there is written to correspond to the Zulip markdown-content CSS.That CSS is a few hundred lines of code. It's written in Less; but looking at the compiled output, it's not much longer than that source, and most of the difference is highly repetitive. So the real amount of information there is about what's in that one source file. That file is also highly stable over time — just as one might hope, given that TeX itself is famously extremely stable — with the last non-NFC change 20 months ago, in 2021-07.
So while this won't be a small subproject, it's one where I'm pretty confident we can do it well.
The text was updated successfully, but these errors were encountered: