Error "unknown shortcode token" when calling shortcode within fenced code block

[jmooring]

N.B. I'm not sure if this is a bug, or if we've fixed a bug.

Reproducible with v0.111.0 and later.

If a shortcode is called using the {{< >}} notation within a fenced code block, Chroma lexes the placeholder, triggering an error such as:

unknown shortcode token "HAHAHUGOSHORTCODE<span style="color:#f92672">-<span style="color:#a6e22e">s0<span style="color:#f92672">-<span style="color:#a6e22e">HBHB"

But this does not happen with all lexers, and may depend on where the shortcode is placed within the codeblock (not sure).

For example, this works:

```bash
{{< sc >}}
```

But this throws an error:

```go
{{< sc >}}
```

And both of these work:

```bash
{{% sc %}}
```

```go
{{% sc %}}
```

What the shortcode does is irrelevant (e.g., it can be empty).

Reference: https://discourse.gohugo.io/t/43387 (Kubernetes site)

Simple example:

git clone --single-branch -b hugo-forum-topic-43387 https://github.com/jmooring/hugo-testing hugo-forum-topic-43387
cd hugo-forum-topic-43387
hugo server

[bep]

N.B. I'm not sure if this is a bug, or if we've fixed a bug.

I suspect the latter; or possibly also a subtle change in some of the Chroma lexers.

```bash
{{< sc >}}
```

The technical reasons why this fails is that some Chroma highlighters highlights the hyphen in the temporary placeholder, which doesn't work ...

However, the above construct looks a little bit odd since the output of {{< sc >}} will not be highlighted by Chroma. {{% sc %}} will.

But we need to fix this anyway.

[craigbox]

Thanks @bep! I'll update the markup used in the Kubernetes docs.

FWIW, it was hard to find this due to #10735.

Error: Error building site: "/Users/craigbox/Documents/Projects/kubernetes.io/content/ja/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md:1:1": unknown shortcode token "HAHAHUGOSHORTCODE-s12</span>-HBHB"```

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.