-
-
Notifications
You must be signed in to change notification settings - Fork 959
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
hoste.weblate.org - links get mangled #6258
Comments
We've been getting a lot of these on the Markdown/gettext sections of f-droid.org (f-droid/weblate-page, f-droid/weblate-posts, f-droid/weblate-docs). I have a utility script to catch them when I merge. The existing Weblate link checkers do mark these cases. |
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
@nijel where is that controlled? |
I can handle it.
|
Upon thinking about this, I guess the hard part here is that just about all HTML
would be valid in Markdown, so _safe-html_ is quite useful for Markdown text.
But then that does make it harder to write the _safe-html_ plugin.
Here's the official docs on using HTML in Markdown:
https://daringfireball.net/projects/markdown/syntax#html
|
This issue has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
I wonder if the safe_html plugin could be made to ignore the Markdown links. It seems like a pretty safe pattern: |
Thank you for your report; the issue you have reported has just been fixed.
|
Amazing, thanks! |
Steps to reproduce the behavior:
...Weblate F-Droid (<https:>).</https:>
Expected behavior
Translated string should be
...Weblate F-Droid (<https://hosted.weblate.org/languages/ro/f-droid/>).
The text was updated successfully, but these errors were encountered: