fix(shortcodes): use semicolon delimiter to avoid smart typography issue #13915
+27
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Shortcodes followed by a trailing dash (e.g.,
{{< version >}}-) were being rendered as hex-encoded strings:Root Cause
PR #13792 introduced a two-stage transformation that encodes shortcodes as
UUID-HEX-to safely pass through Pandoc's markdown parser. When a user writes{{< version >}}-, the encoded form becomesUUID-HEX--. Pandoc's+smartextension converts--to an en-dash–, breaking the decode pattern match.Fix
Changed the delimiter from
-to;in the UUID-HEX encoding format. Semicolons have no markdown meaning and are not affected by smart typography.Fixes #13913