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

Don't translate Markdown inside of URLs #463

Closed
Mimoja opened this issue May 5, 2020 · 3 comments
Closed

Don't translate Markdown inside of URLs #463

Mimoja opened this issue May 5, 2020 · 3 comments
Labels
can't reproduce This bug could not be confirmed

Comments

@Mimoja
Copy link

Mimoja commented May 5, 2020

When postinga link that accidentally contains markdown it will be translated when posted by the bridge while most normal users can post the link with riot just fine.

Take this example:

https://www.hr6.tum.de/fileadmin/_processed_/c/1/csm_smart__e8029ba795.jpg

_PROCESSED_ will be interpreted as Markdown and will render the link unusable. This happens both directions matrix <-> telegram

Note: some matrix clients appear to break this as well so even the MATRIX<=>MATRIX way does not always work properly.

@tulir
Copy link
Member

tulir commented May 5, 2020

What do you mean exactly? The bridge does no markdown stuff in either direction

@tulir tulir added the can't reproduce This bug could not be confirmed label May 5, 2020
@Mimoja
Copy link
Author

Mimoja commented May 5, 2020

Good to know. Thanks for the fast response.

Let me clarify (if necessary): When I post a telegram message with the link above, then the matrix side (riot-android) gets a broken link displayed. This does not happen if I post directly into the matrix channel.

@tulir
Copy link
Member

tulir commented May 5, 2020

Are you sure it's riot-android and not riotx-android? Sounds like element-hq/element-android#350

@Mimoja Mimoja closed this as completed May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can't reproduce This bug could not be confirmed
Development

No branches or pull requests

2 participants