-
Bug
-
Resolution: Done-Errata
-
Major
-
None
Fixing the badly rendered asciidoc markup that should provide an escape on used asterixes. In my local build, this worked perfectly fine, but for some reasons, it is not rendere as expected on Quarkus portal (main snapshot)
Bad asciidoc translation
![image](https://github.com/quarkusio/quarkus/assets/48474054/d72499e7-ed9c-4ca2-a9b0-61a135b3ee65)
Expected asciidoc translation
![image](https://github.com/quarkusio/quarkus/assets/48474054/d5070304-3262-4319-be8c-c802a0eedd38)
To fix this, I wanted to use `pass:[]` asciidoc macro that would allow me to use `*` in the backtick and render properly (no bold in the text, not escape macro leftovers). The `\` and `++` escape approaches weren't rendered properly, so I used the `pass[]` macro as my last resort.
I also wanted to reword the sentence slightly and put it in a bullet list:
```
An example of a global configuration that applies for all categories:
- `quarkus.log.console.pass:c,a[*]`
- `quarkus.log.file.pass:c,a[*]`
- `quarkus.log.syslog.pass:c,a[*]`
```
However, after consulting this with SME, we agreed on removing these handlers examples completely and replace then with the contextually correct examples (root and per-category) that better fits the overall context of this chapter.
- links to
-
RHSA-2023:124640 Red Hat build of Quarkus 3.2.9 release and security update