We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not a big deal, but since the 5.0 release there are fragments of markup left in the release notes. Just take a look at: https://github.com/WeblateOrg/weblate/releases/tag/weblate-5.0.1 and 5.0 There are {.xxx "..."} all over the place.
{.xxx "..."}
https://github.com/WeblateOrg/weblate/releases/tag/weblate-5.0.1
No response
Other
The text was updated successfully, but these errors were encountered:
Probably result of conversion from rst via pandoc:
weblate/scripts/create-release
Line 86 in 44f32c7
Sorry, something went wrong.
scripts: Use GitHub flavored markdown
0dff4f3
Fixes #9910
3e73d4a
Thank you for your report; the issue you have reported has just been fixed.
scripts: Use HTML as source for GitHub release notes
b12f50c
Using rendered HTML makes all links to the documentation work. Issue #9910
The Weblate 5.0 release note on GitHub is still not fixed.
Fixed that manually now, but there is really no intention to fix all the past release notes.
nijel
No branches or pull requests
Describe the issue
Not a big deal, but since the 5.0 release there are fragments of markup left in the release notes. Just take a look at:
https://github.com/WeblateOrg/weblate/releases/tag/weblate-5.0.1 and 5.0
There are
{.xxx "..."}
all over the place.I already tried
Steps to reproduce the behavior
https://github.com/WeblateOrg/weblate/releases/tag/weblate-5.0.1
Expected behavior
No response
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
Other
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: