Skip to content
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

Inline equation after a link not correctly rendered #2075

Closed
tueda opened this issue Jun 7, 2021 · 3 comments
Closed

Inline equation after a link not correctly rendered #2075

tueda opened this issue Jun 7, 2021 · 3 comments

Comments

@tueda
Copy link

tueda commented Jun 7, 2021

Describe the current behavior

In text cells on Google Colaboratory, if an inline LaTeX math equation ($...$) is put just after an inline link without any spaces between them, then rendering this math expression is not triggered.

Example which does not work (without space):

[Google](https://www.google.com/)$x^2+y^2=a^2$.

image

If I put a tiny space, then it works as expected.

Example which does work (note the space between the link and the equation):

[Google](https://www.google.com/) $x^2+y^2=a^2$.

image

Note that, in some languages, spaces between words are not needed and actually some style guides or text linters may strictly forbid any additional spaces (ideally, typesetting or text display systems should handle spacing adjustment in this case if needed, rather than by users).

Describe the expected behavior

Equations should be rendered correctly even without any spaces.

What web browser you are using

Chrome (91.0.4472.77, 64bits, Windows 10)

Additional context

Workaround with no additional visible spaces: putting <!-- $ $ --> triggers the equation rendering:

[Google](https://www.google.com/)$x^2+y^2=a^2$.<!-- $ $ -->

image

Edit: unfortunately, this workaround does not work for the following case and worsens the output:

[Google](https://www.google.com/)$x \ge 0$.<!-- $ $ -->

image

@tueda tueda added the bug label Jun 7, 2021
@cperry-goog
Copy link

Thank you for your report! This is super helpful for us, we'll take a look.

@cperry-goog
Copy link

Internally tracked at b/190753449

@blois
Copy link
Contributor

blois commented Jun 23, 2021

This should now be fixed.

@blois blois closed this as completed Jun 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants