From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: virtio-comment@lists.linux.dev
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [RFC PATCH v1 0/2] Embed files as PDF attachments
Date: Sun, 15 Sep 2024 10:56:29 +0300 [thread overview]
Message-ID: <v1-proposal-attachfiles.manos.pitsidianakis@linaro.org> (raw)
The PDF specs allow for file attachments to documents. This can be used
to make the VIRTIO PDF spec a single source of truth by embedding
related files.
This series attaches the virtio-queue.h header file as a proof of
concept. It can be inspected and extracted using a compliant PDF viewer
such as Adobe's or Firefox's integrated PDF reader.
(Note: I'm not sure if Chrome supports it, my local version does not,
neither does Chromium.)
Programmatically extracting files is also possible, allowing for
downstream projects to update their headers by accessing the upstream
pdf file.
Example using the `pdfdetach` utility from the Xpdf package of tools
(`poppler-utils` package on debian/ubuntu):
$ pdfdetach -list virtio-v1.3-csd01.pdf
1 embedded files
1: virtio-queue.h
$ pdfdetach -save 1 virtio-v1.3-csd01.pdf
$ file virtio-queue.h
virtio-queue.h: C source, ASCII text
Manos Pitsidianakis (2):
specvars.tex: Add \virtioauthor command
Embed virtio-queue.h as PDF attachment
commands-html.tex | 7 +++++++
commands-pdf.tex | 10 ++++++++++
headerfile.tex | 2 ++
specvars.tex | 3 ++-
virtio.tex | 1 +
5 files changed, 22 insertions(+), 1 deletion(-)
base-commit: b495841a8e80d12c1130f8868f4128866291142d
--
γαῖα πυρί μιχθήτω
next reply other threads:[~2024-09-15 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 7:56 Manos Pitsidianakis [this message]
2024-09-15 7:56 ` [RFC PATCH v1 1/2] specvars.tex: Add \virtioauthor command Manos Pitsidianakis
2024-09-15 7:56 ` [RFC PATCH v1 2/2] Embed virtio-queue.h as PDF attachment Manos Pitsidianakis
2024-09-15 11:11 ` [RFC PATCH v1 0/2] Embed files as PDF attachments Michael S. Tsirkin
2024-09-15 11:31 ` Manos Pitsidianakis
2024-09-15 11:56 ` Michael S. Tsirkin
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=v1-proposal-attachfiles.manos.pitsidianakis@linaro.org \
--to=manos.pitsidianakis@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=virtio-comment@lists.linux.dev \
/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