* Most of text blocks are in fact output blocks
* On qubes-iso-building.rst, try to get something correct for console
lines starting with a comment
* Fixing a wrong :menuselection: item.
Statistics:
685 console
79 text
44 bash
35 output
16 yaml
9 systemd
9 c
8 python
4 ini
4 doscon
2 markdown
2 desktop
1 xorg.conf
1 xml+jinja
1 xml
1 kconfig
1 html
Changing `bash` lexer to `console` because it is appropriate most of
the time. Then after a manual review, some lexer have been changed.
I used `text` each time I was unsure, and for prompt outputs.
The page `/developer/building/qubes-iso-building.rst` still need to be
reviewed (look for lines starting with `$ #`).
I'm not sure about the Windows pages, should we use
[doscon](https://pygments.org/docs/lexers/#pygments.lexers.shell.MSDOSSessionLexer)
or `powershell`?
Is there an appropriate lexer for `guid.conf` content?
**Statistics - Before**
870 bash
9 python
9 c
2 yaml
**Statistics - After**
684 console
111 text
44 bash
16 yaml
9 systemd
9 c
8 python
4 ini
4 doscon
2 markdown
2 desktop
1 xorg.conf
1 xml+jinja
1 xml
1 kconfig
1 html
This suggests that the default lexer should be `console`.
This is plain rename without changing content, to help git track files
history.
Do not touch files that are going to be removed during conversion.
Thanks @parulin for the idea!
Whonix 16 will reach EOL before Qubes 4.1 reaches EOL, at which point
the table will be inaccurate. Since the Whonix support cycle does not
match the Qubes support cycle, and since whonix templates are not
official templates, it is better to remove from them from the table and
direct users to the Whonix website for official information about
support status.