Skip to content

Hopefully fix broken asciidoc escapes #360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dstelzer wants to merge 2 commits into
base: main
Choose a base branch
from
+5 −5
Open

Hopefully fix broken asciidoc escapes #360

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9aae8cd
hopefully fix broken asciidoc escapes
dstelzer Sep 16, 2026
589a5ee
I don't understand asciidoc...
dstelzer Sep 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion manual/modules/lang/pages/quickref.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ print.

xref:sugar.adoc#unicode[Unicode escapes]: ::

`\x{3C4}` is exactly equivalent to character U+03C4.
`+\x{3C4}+` is exactly equivalent to character U+03C4.

xref:execution.adoc#predicates[Rule definitions]: ::

Expand Down
8 changes: 4 additions & 4 deletions manual/modules/lang/pages/sugar.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -403,8 +403,8 @@ Slash-expressions may only appear in rule heads, never inside rule bodies.
Dialog can support just about any characters in source code, whether that's A, Ÿ,
Σ, 五, or ✨. However, these characters are not always easy to type. Sometimes it's
more convenient to refer to characters by Unicode codepoint; when this happens,
you can instead refer to those characters as `\x{41}`, `\x{178}`, `\x{3A3}`,
`\x{4e94}`, and `\x{2728}`. The two are exactly equivalent to the compiler, which
you can instead refer to those characters as `+\x{41}+`, `+\x{178}+`, `+\x{3A3}+`,
`+\x{4e94}+`, and `+\x{2728}+`. The two are exactly equivalent to the compiler, which
allows for some truly awful source code:

[source]
Expand All @@ -413,8 +413,8 @@ allows for some truly awful source code:
----

But this is far less readable than `(program entry point)` and should be avoided
at any cost. Still, `\x{200D}` is much clearer than a literal zero-width joiner,
and `\x{301}` much clearer than a literal combining acute accent. Sometimes the
at any cost. Still, `+\x{200D}+` is much clearer than a literal zero-width joiner,
and `+\x{301}+` much clearer than a literal combining acute accent. Sometimes the
difference between codepoints can be easier to read than the difference between
the actual characters.

Expand Down
Loading