LaTeX Support in mobile #2660
Comments
|
What's the status on this? I just got a report about it from a friend. |
|
I just got another request for LaTeX support in mobile (I think I've seen at least 4 people ask for it), so we might want to think about picking this up now that #2788 is done. |
I think that day is today :) (for the PR review part) |
|
Thx for taking up the challenge of figuring out how to do this for react native. Nobody is able to solve this problem, within react-native (to add the capability to display latex or MathML). I have been researching this on and off for a couple of months, and the only thing I could find is that this need is listed in React-native feature request tracker: https://react-native.canny.io/feature-requests/p/latex-or-mathml-rendering-in-reactnative It seems like rendering latex/mathML from a Webview is the only viable path at the moment. |
|
hey @vladp! |
|
Bumping the priority because we just got another request for this feature -- with Tim's comment above, I guess that means at least 5 different people asking for it :-) , which is quite a lot. |
|
After trying multiple platforms I just settled for zulip only because it supported latex.. now I discover it does not yet in mobile.. Please add this support ASAP.. any road map? |
|
I second this request. |
At present, when loading content into the WebView, we inject all non-image assets as part of the generated HTML. This is more than a bit wasteful, considering that large swaths of the supporting CSS and JavaScript is entirely static from invocation to invocation; additionally, it makes KaTeX support somewhere between "nontrivial" and "impossible". This commit creates a build subsystem which can inject static webview-supporting assets into the application bundle, into a `webview` directory. We also create a stub directory for the subsystem copy assets from; at present this contains only a README.md file (which will *not* be copied), but this will be expanded in the following series of commits. Inspired by zulip#2690. Assists with zulip#2660, zulip#3595, and potentially many other issues.
At present, when loading content into the WebView, we inject all non-image assets as part of the generated HTML. This is more than a bit wasteful, considering that large swaths of the supporting CSS and JavaScript is entirely static from invocation to invocation; additionally, it makes KaTeX support somewhere between "nontrivial" and "impossible". This commit creates a build subsystem which can inject static webview-supporting assets into the application bundle, into a `webview` directory. We also create a stub directory for the subsystem to copy assets from; at present this contains only a README.md file (which will *not* be copied), but this will be expanded in the following series of commits. Inspired by zulip#2690. Assists with zulip#2660, zulip#3595, and potentially many other issues.
At present, when loading content into the WebView, we inject all non-image assets as part of the generated HTML. This is more than a bit wasteful, considering that large swaths of the supporting CSS and JavaScript is entirely static from invocation to invocation; additionally, it makes KaTeX support somewhere between "nontrivial" and "impossible". This commit creates a build subsystem which can inject static webview-supporting assets into the application bundle, into a `webview` directory. We also create a stub directory for the subsystem to copy assets from; at present this contains only a README.md file (which will *not* be copied), but this will be expanded in the following series of commits. Inspired by zulip#2690. Assists with zulip#2660, zulip#3595, and potentially many other issues.
At present, when loading content into the WebView, we inject all non-image assets as part of the generated HTML. This is more than a bit wasteful, considering that large swaths of the supporting CSS and JavaScript is entirely static from invocation to invocation; additionally, it makes KaTeX support somewhere between "nontrivial" and "impossible". This commit creates a build subsystem which can inject static webview-supporting assets into the application bundle, into a `webview` directory. We also create a stub directory for the subsystem to copy assets from; at present this contains only a README.md file (which will *not* be copied), but this will be expanded in the following series of commits. Inspired by zulip#2690. Assists with zulip#2660, zulip#3595, and potentially many other issues.
At present, when loading content into the WebView, we inject all non-image assets as part of the generated HTML. This is more than a bit wasteful, considering that large swaths of the supporting CSS and JavaScript is entirely static from invocation to invocation; additionally, it makes KaTeX support somewhere between "nontrivial" and "impossible". This commit creates a build subsystem which can inject static webview-supporting assets into the application bundle, into a `webview` directory. We also create a stub directory for the subsystem to copy assets from; at present this contains only a README.md file (which will *not* be copied), but this will be expanded in the following series of commits. Inspired by #2690. Assists with #2660, #3595, and potentially many other issues.
|
With #3636 landed, our app infrastructure is now in much better shape to be able to implement this feature! So I'm hoping we'll have this done sometime soon. |
|
I've just started using Zulip mobile and LaTeX rendering half works: the maths is correctly rendered, but then there's a unicode approximation that follows the rendered maths immediately afterwards. |
This incorporates the same KaTeX library we use in the Zulip webapp. We add the dependency, add a build-webview step to copy the needed files, and apply the stylesheet in our WebView HTML. There are a couple of cases where the resulting HTML and CSS doesn't quite look right. We'll go on to take care of those in upcoming commits. [greg: adapted to this build-webview structure] Fixes: zulip#2660
|
More voices of people eager for this feature, over on #3744:
and
|
|
I get the same problem as |
This incorporates the same KaTeX library we use in the Zulip webapp. We add the dependency, add a build-webview step to copy the needed files, and apply the stylesheet in our WebView HTML. There are a couple of cases where the resulting HTML and CSS doesn't quite look right. We'll go on to take care of those in upcoming commits. [greg: adapted to this build-webview structure] Fixes: zulip#2660
This incorporates the same KaTeX library we use in the Zulip webapp. We add the dependency, add a build-webview step to copy the needed files, and apply the stylesheet in our WebView HTML. There are a couple of cases where the resulting HTML and CSS doesn't quite look right. We'll go on to take care of those in upcoming commits. Fixes: zulip#2660
|
LaTeX support in the mobile app is now released! The new version is 26.24.147 if you're on iOS, and 26.25.148 on Android. (They're the same app built from the same code, just different version numbers due to a hiccup in the build.) @Yoshi8765 @parthi2929 @berceanu @thosgood @jedbrown @pyrocto @cortner and everyone else who's been wanting this -- please update, try it out, and don't hesitate to file new issues if you find something that doesn't look right 🙂 |
The Zulip app currently does not render LaTeX formatting correctly.
A simple example from a user in my realm:
Correctly rendering visual of post in desktop app:
Incorrect render on Android:
source code:
The text was updated successfully, but these errors were encountered: