Right now, #Sibelius #Goldmark with Vodicka and #Suk's First from #Brno https://www.worldconcerthall.com/en/schedule/sibelius_goldmark_with_vodicka_and_suks_first_from_brno/86116/ #wch

In 15 minutes, #Sibelius #Goldmark with Vodicka and #Suk's First from #Brno https://www.worldconcerthall.com/en/schedule/sibelius_goldmark_with_vodicka_and_suks_first_from_brno/86116/ #wch

Today, #Sibelius #Goldmark with Vodicka and #Suk's First from #Brno https://www.worldconcerthall.com/en/schedule/sibelius_goldmark_with_vodicka_and_suks_first_from_brno/86116/ #wch

>Wie die AfD #Europa "neu" denkt: #Abschottung und #Goldmark – Ep. 245<

Aus aktuellem Anlass eine programmatische Durchleuchtung der afd.
😶‍🌫️... 🫣

#Thueringen

#Europawahl

https://youtube.com/watch?v=pUX2wP8DRwM&si=5MPkTbvs8-PdaPOF

Finally fixed #goldmark footnote support in my #Hugo shortcode. Thanks to the Hugo team, especially jmooring!

---

It should be {{ .Inner }} and not {{- .Inner -}} or {{- .Inner | markdownify -}} or {{ .Inner | mardownify }}.

There's a conflict causing all the messed-up rendering I see when testing.
1. The default of .Inner is markdown, so piping it to markdown again is definitely not a good idea.
2. The space cancellation feature (the hyphens) is causing the content of .Inner to get attached to the HTML code, which should not happen in markdown for certain HTML elements.

Having fixed that, footnotes within my shortcode "accordion" (HTML: details element) now works. It also fixed the problem I was having when calling my image shortcode within the accordion shortcode.

Here's my current Hugo shortcodes: https://codeberg.org/yelosan/hugo-shortcodes/src/branch/main/layouts/shortcodes

Now, I don't have to use my workaround shortcodes for footnotes. ^_^;;

#GoHugo #HugoShortcodes

Right now, a #Mozart's Divertimento and #Goldmark from #Saarbrücken https://pst.cr/6AXBj #wch

In 15 minutes, a #Mozart's Divertimento and #Goldmark from #Saarbrücken https://pst.cr/6AXBj #wch

Today, a #Mozart's Divertimento and #Goldmark from #Saarbrücken https://www.worldconcerthall.com/en/schedule/a_mozarts_divertimento_and_goldmark_from_saarbrucken/74568/ #wch

Right now, #Schubert #Goldmark with Capuçon and #Brahms' Second from #Paris https://pst.cr/TsX3w #wch

In 25 minutes, @PhilharRF plays #Schubert #Goldmark with Capuçon and #Brahms' Second from #Paris https://www.worldconcerthall.com/en/schedule/schubert_goldmark_with_capuson_and_brahms_second_from_paris/72617/ #wch

The other option would be building #Hugo myself, so that I can use my own #Goldmark extensions. But that would go too far I think. Yes, I very much prefer applications providing extensibility via interpreted languages, not requiring you to produce a custom build whenever you need a behavior change...

My #Goldmark Markdown parser issues have been closed - last year the author said that he didn't care enough about smart quotes to fix them, now he says that he doesn't want the algorithm to deviate from CommonMark emphasis. Which is a bit ridiculous - the latter is about markup.