Language identifier is missing from fenced code block when it is quoted

[Andrew15-5 (Andrew)]

Someone can write something like this:

```py
print()
```

But when you then quote its output:

print()

it will be quoted without the language identifier, like this:

print()

Specifically, I noticed this in https://forum.typst.app, and not only me. This is quite annoying to fix manually every time, so I’m pretty confident that this is a bug. Preserving the language identifier is the expected behavior.

[Andrew15-5 (Andrew)]

@Andrew15-5

But when you then quote its output:

print()

it will be quoted without the language identifier, like this:

Here is a live example of how the code block is quoted (without language identifier).

[Andrew15-5 (Andrew)]

Today I found out that you can actually get the info string by checking the HTML:

<code class="lang-py hljs language-python" data-highlighted="yes">
  <span class="hljs-built_in">print</span>
  ()
</code>

If the language is known(?), it looks like it will show full name in language-x, but your specified in lang-x. However, even though Python is identified (visually), both classes will include Python.

This will help know which info string is used by someone else, or any post that you can’t edit (or can).

[Falco]

@Andrew15-5

But when you then quote its output:

You mean when you quote with text selection right? Using the full quote button work just fine.

@Andrew15-5

print()

That is the expected behavior, as when you select text we don’t have access to the original markdown and do an approximation.

Same as reported in

Select to quote shouldn't strip < and > characters around links

This only happens with the “select to quote” feature, and not with full quotes, because when doing a full quote we fetch the original markdown so we can give 100% accuracy. Select to quote feature must do HTML → Markdown conversion, so there will always be missing content from the original, specially when it is invisible from an HTML point of view.

[Andrew15-5 (Andrew)]

@Falco

You mean when you quote with text selection right?

Yes.

@Falco

Using the full quote button work just fine.

There is no “Full quote” button.

@Falco

That is the expected behavior, as when you select text we don’t have access to the original markdown and do an approximation.

Can you not get the exact place in DOM where the selection is happening? Then it should be pretty easy to replicate whatever is needed.