-
-
Notifications
You must be signed in to change notification settings - Fork 122
Add an explicit anchor to releases section #652
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
Conversation
- required for link to work after translation
✅ Deploy Preview for numpy-org ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Actually, I'm starting to think it might not be viable to keep translations for Currently there's a link to but maybe for the translated content it's better just to link to |
There's not nearly as many actual content updates though; most of the comments are just one-line entries for bug fix releases. How about splitting the release updates off into a separate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding this anchor seems like a straightforward fix. Thanks Albert.
Great idea. Then I guess we just don't want to link to the releases from the translated content? Does it make sense to not link to releases from the English content to avoid having slight differences between English and translated content? |
All markdown headings already have anchors generated, so this should not be necessary. Click in the navigation table on the left, and copy the URL, which will now contain the anchor. |
Either that, since there's not too much value in this list at the bottom of the news page, or just automate it somehow in a build step. There's no new translations to be done in this kind of thing:
all it needs is a one-off translation of the words "release notes". |
I think the anchor name depends on the header title, so after translation the link no longer works. Crowdin makes it difficult to change the internal link to use the translated header. Adding an explicit internal link in English gives something that can be linked to in translated pages. |
Oh true. I was thinking of the actual summaries of release notes that end up in |
Ah, gotcha! Yes, I think I had to fix that for other languages in the Hugo 114 update as well. Another way to spell this would be:
|
Nice! I like this syntax better. |
Brief description of what is fixed or changed
This PR adds an explicit anchor to the releases section of
news.md
. This is required for the link to work with translated content.cc @rgommers @melissawm