Hi Ralph,
On 4/10/23 17:56, Ralph Corderoy wrote:
> Hi Alejandro,
>
>> I'd use .cat.set for UTF8/ASCII pages, and .html.set for HTML pages.
>
> Yes, I was thinking if a .tr was being turned into several formats then
> I'd include troff's -T device in the filename.
>
> But as a general case, whe
On Mon Apr 10, 2023 at 1:37 PM EDT, Ralph Corderoy wrote:
> Hi DJ,
>
> > Since ditroff stands for “Device Independent troff”
>
> It does. It means the troff which doesn't have a device hard-coded
> within it but can instead take -Tps, -Tutf8, etc.
>
> The output of the device-independent troff is
Hi DJ,
> Since ditroff stands for “Device Independent troff”
It does. It means the troff which doesn't have a device hard-coded
within it but can instead take -Tps, -Tutf8, etc.
The output of the device-independent troff is specific to the chosen -T
device. Continuing to include the ‘independe
On Mon Apr 10, 2023 at 8:42 AM EDT, Ralph Corderoy wrote:
> > > troff lays out its input.
> > > The input has been placed on the page.
> > > It is typeset.
> > > It is set.
> > >
> > > troff chapter.tr >chapter.set
> >
> > $ file chapter.set
> > chapter.set: ditroff output text for Post
Hi Ralph,
On 4/10/23 17:56, Ralph Corderoy wrote:
> Hi Alejandro,
>
>> I'd use .cat.set for UTF8/ASCII pages, and .html.set for HTML pages.
>
> Yes, I was thinking if a .tr was being turned into several formats then
> I'd include troff's -T device in the filename.
>
> But as a general case, whe
Hi Alejandro,
> I'd use .cat.set for UTF8/ASCII pages, and .html.set for HTML pages.
Yes, I was thinking if a .tr was being turned into several formats then
I'd include troff's -T device in the filename.
But as a general case, where just one -T is being targeted, a plain
chapter.set seems suffic
On Mon, Apr 10, 2023 at 04:37:07PM +0100, Ralph Corderoy wrote:
> Subject: Re: A file suffix for troff's output.
>
> Some programs can act on the pattern to filenames, e.g.
> make(1). It can be told how to turn a .tr into a .set and a
> .set into a .ps. Even though all three
Hi Steve,
On 4/10/23 15:45, Steve Izma wrote:
> On Mon, Apr 10, 2023 at 10:03:34AM +0100, Ralph Corderoy wrote:
>> Subject: A file suffix for troff's output. (Was: pdfroff in groff
>> 1.23.0.rc3 changes compared to 1.22.4)
>>
>> troff chapter.tr >c
Hi Steve,
> > troff chapter.tr >chapter.set
> > grops chapter.set >chapter.ps
> >
> > Short, simple, not already widely used by another program,
> > pronounceable, a clear derivation.
>
> Maybe I'm mis-reading the problem here, but Postscript output from
> groff in my experience has alway
On Mon, Apr 10, 2023 at 10:03:34AM +0100, Ralph Corderoy wrote:
> Subject: A file suffix for troff's output. (Was: pdfroff in groff
> 1.23.0.rc3 changes compared to 1.22.4)
>
> troff chapter.tr >chapter.set
> grops chapter.set >chapter.ps
>
> Short, si
Quoth DJ Chase:
$ file chapter.set
chapter.set: ditroff output text for PostScript, ASCII text
Wouldn’t “.ditroff” be more appropriate?
file tells you that chapter.set contains the ouput of ditroff, not
ditroff itself. So no, both .set (which I find agreeable) and .trout
are
Hi DJ,
> > troff lays out its input.
> > The input has been placed on the page.
> > It is typeset.
> > It is set.
> >
> > troff chapter.tr >chapter.set
>
> $ file chapter.set
> chapter.set: ditroff output text for PostScript, ASCII text
>
> Wouldn’t “.ditroff” be more appropriate?
On Mon Apr 10, 2023 at 5:03 AM EDT, Ralph Corderoy wrote:
> troff lays out its input.
> The input has been placed on the page.
> It is typeset.
> It is set.
>
> troff chapter.tr >chapter.set
$ file chapter.set
chapter.set: ditroff output text for PostScript, ASCII text
Wouldn’
Hi Branden,
> Perhaps you can think of some alternative names for distinguishing
> formatter output that we expect non-groff output drivers to be able to
> cope with from those that exercise the extension.
troff lays out its input.
The input has been placed on the page.
It is typeset.
It is set.
14 matches
Mail list logo
