From: Noel Ullreich <n.ullreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 0/3] Fixed formatting of pdf docs
Date: Tue, 3 Jan 2023 14:31:18 +0100 [thread overview]
Message-ID: <20230103133121.114234-1-n.ullreich@proxmox.com> (raw)
Updated the Latex stylesheet for:
* better kerning of the table of contents
* correct linebreaking of inline code snippets
Changed the table in the adoc file so that the table would correctly
render
Noel Ullreich (3):
Fixed inline code breaking in pdf docs
Fixed the table in 3.11.8
Fixed kerning in table of contents
asciidoc/dblatex-custom.sty | 18 ++++++++++++++++++
certificate-management.adoc | 24 ++++++++++++++++++++++--
2 files changed, 40 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2023-01-03 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 13:31 Noel Ullreich [this message]
2023-01-03 13:31 ` [pve-devel] [PATCH pve-docs 1/3] Fixed inline code breaking in " Noel Ullreich
2023-01-03 15:36 ` Thomas Lamprecht
2023-01-03 13:31 ` [pve-devel] [PATCH pve-docs 2/3] Fixed the table in 3.11.8 Noel Ullreich
2023-01-03 15:35 ` Thomas Lamprecht
2023-01-10 12:56 ` Noel Ullreich
2023-01-03 13:31 ` [pve-devel] [PATCH pve-docs 3/3] Fixed kerning in table of contents Noel Ullreich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230103133121.114234-1-n.ullreich@proxmox.com \
--to=n.ullreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox