Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
26 lines (18 sloc) 3.31 KB

date: 2020-01-05 title: "Hugo 0.62.2: A couple of Bug Fixes" description: "This version fixes a couple of bugs introduced in 0.62.0." categories: ["Releases"] images:

  • images/blog/hugo-bug-poster.png

The main driving force behind these patch releases in the new year has been getting a good story with portable links between GitHub and Hugo, using the new render hooks introduced in Hugo 0.62.0. And all was mostly well until a Hugo user asked about anchor links. Which is, when you look into it, a slightly sad Markdown story. They have been talking about anchors in Markdown over at the CommonMark forum for the last six years, but it has come to nothing. The current situation is that some Markdown engines support the {#anchorName} attribute syntax (Hugo's Goldmark does, GitHub does not) and for those that support auto-generation of IDs, the implementation often varies. And this makes for poor portability.

To improve this, Hugo has now reverse-engineered GitHub's implementation and made that the default strategy for generation or header IDs. We understand that this isn't everyone's cup of tea, so you can configure the behaviour to be one of github, github-ascii (some client-libraries have Unicode issues) or blackfriday (which will match how it behaved before Hugo 0.60).

You can’t perform that action at this time.