9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <tlaronde@kergis.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Minutes of July 24 Plan 9 Foundation Board Meeting
Date: Fri, 29 Aug 2025 16:53:49 +0200	[thread overview]
Message-ID: <aLG-_V24J6FqNp7Q@kergis.com> (raw)
In-Reply-To: <CAJ5m4OGrRiNfHDzhVKAra8dWSoYqViNsucyYHmNvhbN1uznqBA@mail.gmail.com>

On Fri, Aug 29, 2025 at 07:02:42AM -0700, paul lalonde wrote:
> We met yesterday, and approved the minutes for the July meeting, please see
> attached.

On some points:

Papers for IWP9 and macros:

concerning the papers: I will add during September 2025 a variable
to TeX (in fact Prote) in order to be able to process macro definition
with the escape character being the beginning of the line ('/^\./') for
roff compatibility (handling utf-8 can also be done with minimal cost,
but I need to fix my ideas about the fonts handling; so I let this
mature). So even a *roff like macro package could be treated with
TeX/Prote as layout engine;

Making money:

Since PDF is an ISO spec, a lot of entities
mandate its use, requiring to digitally sign a PDF, keeping the
PDF "vectorial" (not to scan a signed paper, wrapping the raster image
in PDF, or not even to add an image of signature on a "vectorial"
PDF). 

This is "open", right? Yes, but you will have a hard time finding an
open (not AGPL) PDF library able to do it. So a lot of companies milk
the customers requiring whether to pay for every digitally signed PDF,
or to , or to engage for a monthly subscription.

Signing a PDF is neither rendering the PDF, nor implementing the whole
PDF: the signature is appended to the file, the xref being rewritten
(one reads the PDF from the end, searching for the last '/^%EOF\n/' to
get the offset to the xref that can reach out to previous xref.

Proposing such a service with reasonable prices, adding the
possibility to choose where a text about the signature will appear
(generally, such a text appears at the most inconvenient place when
displaying the file), could work.
for 
-- 
        Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T875cae76d659fc73-M32e557546a2dd453297be4ee
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2025-08-29 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29 14:02 paul lalonde
2025-08-29 14:53 ` tlaronde [this message]
2025-08-30 15:37 ` Paul Lalonde

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=aLG-_V24J6FqNp7Q@kergis.com \
    --to=tlaronde@kergis.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).