On Wed, Jul 02, 2025 at 11:23:14PM +0200, Patrice Dumas wrote:
> > I've been learning about features in "KOMA-Script" (a LaTeX system)
> > that allow for the creation of copyright pages:
> >
> > https://tex.stackexchange.com/questions/12570/how-to-add-a-copyright-page-to-the-report-class
> > https
On Mon, Jun 30, 2025 at 11:30:29PM +0100, Gavin Smith wrote:
> On Sun, Jun 29, 2025 at 06:53:20PM +0200, Patrice Dumas wrote:
> > > The user uses @maketitle to produce the title page, and the second page
> > > is created by the contents of the @copyrightpage block.
> > >
> > > We could also possib
On Sun, Jun 29, 2025 at 06:53:20PM +0200, Patrice Dumas wrote:
> > The user uses @maketitle to produce the title page, and the second page
> > is created by the contents of the @copyrightpage block.
> >
> > We could also possibly provide a @makecopyrightpage command
> > for a default copyright pag
On Sun, Jun 29, 2025 at 09:12:41PM +0100, Gavin Smith wrote:
> On Sun, Jun 29, 2025 at 06:53:20PM +0200, Patrice Dumas wrote:
> > > title verso page for TeX output (and possibly LaTeX output with texi2any).
> > > I don't think it's advisable to try and make it automatic. Sometimes
> > > users
> >
On Sun, Jun 29, 2025 at 06:53:20PM +0200, Patrice Dumas wrote:
> On Sun, Jun 29, 2025 at 01:31:31AM +0100, Gavin Smith wrote:
> > > > In the default case, when using @documentinfo, the copying text would
> > > > be output
> > > > on the verso of the title page in PDF output. No separate command
On Sun, Jun 29, 2025 at 01:31:31AM +0100, Gavin Smith wrote:
> > > In the default case, when using @documentinfo, the copying text would be
> > > output
> > > on the verso of the title page in PDF output. No separate command would
> > > be
> > > necessary.
> >
> > It is necessary if the user wa
> > In the default case, when using @documentinfo, the copying text would be
> > output
> > on the verso of the title page in PDF output. No separate command would be
> > necessary.
>
> It is necessary if the user wants a specific formatting different than
> the default.
Could we support input
On Thu, Jun 26, 2025 at 07:49:58PM +0100, Gavin Smith wrote:
> Coming back to this thread as I was prompted by Patrice:
>
> https://lists.gnu.org/archive/html/bug-texinfo/2025-01/msg00066.html
>
> I don't have a complete proposal but will post some comments to help
> get this conversation going a
Coming back to this thread as I was prompted by Patrice:
https://lists.gnu.org/archive/html/bug-texinfo/2025-01/msg00066.html
I don't have a complete proposal but will post some comments to help
get this conversation going again.
I like the proposed @documentinfo command to contain metadata such
On Sat, Jan 11, 2025 at 10:11:11PM +0100, Patrice Dumas wrote:
> I propose to add a @documentinfo block which would contain information
> that can be used for diverse purposes, but in particular to do the formatting
> previously assigned to @titlepage.
I don't object in principle but I can't promi
On Sun, Jan 12, 2025 at 07:53:20AM +0200, Eli Zaretskii wrote:
> without seeing examples. So how about showing one or more examples of
> formatting @titlepage block with the current commands, and what would
> it look like under this/these proposal(s)?
The example in the Texinfo manual:
@titlepag
> Date: Sat, 11 Jan 2025 22:11:11 +0100
> From: Patrice Dumas
>
> Hello,
>
> Here is a proposal to move on on the @titlepage redesign, which is mainly
> based on Gavin ideas in
> https://lists.gnu.org/archive/html/bug-texinfo/2019-03/msg00029.html
>
> I propose to add a @documentinfo block whic
Hello,
Here is a proposal to move on on the @titlepage redesign, which is mainly
based on Gavin ideas in
https://lists.gnu.org/archive/html/bug-texinfo/2019-03/msg00029.html
I propose to add a @documentinfo block which would contain information
that can be used for diverse purposes, but in partic
13 matches
Mail list logo
