May I make a plea for the use of or somesuch in HTML
documents? It was one of the first HTML commands I learnt back in 1996
when I started HTML coding. (Some -- my kids -- would say that my HTML
coding remains stuck in 1996, BTW.) Please, some margins in HTML pages
such as
http://www.catb.org/
On Thu, Mar 06, 2014, "Robert Thorsby" wrote:
> However, the groff project has been looking for a new leader for a
> long time -- since Werner first announced his intention to step
> aside. I, for one, am very glad that someone of Peter's calibre is
> being slowly shoehorned into the role. I suspec
On Thu, Mar 06, 2014, Eric S. Raymond wrote:
> What we can do, though, is look for ways to (a) reduce the inventory of
> low-level troff requests a man-page renderer has to support, and (b)
> further enrich the semantic content so that renderers can do a better
> job without having to ve as complex
On Thu, Mar 06, 2014, Keith Marshall wrote:
> On 06/03/14 16:35, Eric S. Raymond wrote:
> > No, what I want is for all Unix documentation to be properly
> > wenbbed and crosslinked.
>
> Well, that's certainly a vision to which I *can* subscribe, but
> groff is about so much more than Unix document
On 06/03/14 16:35, Eric S. Raymond wrote:
> No, what I want is for all Unix documentation to be properly wenbbed
and
> crosslinked.
I find it difficult to understand why groff needs a .hygiene, maybe it's
because I'm a dirty rascal! It seems to be a switch which is designed to
stop naughty man
Keith/Deri --
On Thu, Mar 06, 2014, Deri James wrote:
> If you are using mom the pdfmom command will do the forward
> references for you. If you are not using mom the actual command
> is:-
>
> groff -Tpdf -dPDF.EXPORT=1 -z $cmdstring 2>&1 | grep '^.ds' | groff -Tpdf -
> $preconv $cmdstring
>
>
On Thu 06 Mar 2014 21:47:15 Ralph Corderoy wrote:
> I'm guessing that
>
> grep '^\.ds'
>
> might be the intent.
>
> Cheers, Ralph.
Yes, indeed! Thanks.
Hi Deri,
> groff -Tpdf -dPDF.EXPORT=1 -z $cmdstring 2>&1 |
> grep '^.ds' |
> groff -Tpdf - $preconv $cmdstring
I'm guessing that
grep '^\.ds'
might be the intent.
Cheers, Ralph.
On 06/03/14 20:08, Deri James wrote:
> On Thu 06 Mar 2014 18:08:10 Keith Marshall wrote:
>> So, you're assuming that just one preliminary pass is sufficient to
>> resolve the cross references? That may not be so, and pdfroff is not so
>> naive; it performs at least two such passes, and then as man
On Thu 06 Mar 2014 18:08:10 Keith Marshall wrote:
> On 06/03/14 16:21, Deri James wrote:
> > If you are not using mom the actual command is:-
> >
> > groff -Tpdf -dPDF.EXPORT=1 -z $cmdstring 2>&1 \
> >
> > | grep '^.ds' | groff -Tpdf - $preconv $cmdstring
>
> So, you're assuming that just one
On 06/03/14 16:21, Deri James wrote:
> If you are not using mom the actual command is:-
>
> groff -Tpdf -dPDF.EXPORT=1 -z $cmdstring 2>&1 \
> | grep '^.ds' | groff -Tpdf - $preconv $cmdstring
So, you're assuming that just one preliminary pass is sufficient to
resolve the cross references? That
On 06/03/14 16:35, Eric S. Raymond wrote:
> No, what I want is for all Unix documentation to be properly wenbbed and
> crosslinked.
Well, that's certainly a vision to which I *can* subscribe, but groff is
about so much more than Unix documentation; indeed, my own personal use
case has nothing wha
Ingo Schwarze :
> The classical man(7) language is a purely presentational language
> and contains exactly three semantic macros as exceptions: TH, SH, SS.
> So basically, nothing except titles is semantic in there.
You left out the mnost common one: .P.
I'm aware that we're stuck with presentati
Keith Marshall :
> Eric, apparently, espouses a vision of an SGML-centric world. I can
> respect that, even though I do not share it; thankfully, from my POV,
> that vision is unlikely to be realized in my lifetime -- the printed
> page will not die out that soon!
That's not really true. If I we
On Thu 06 Mar 2014 09:21:57 Keith Marshall wrote:
> A further advantage of using pdfroff is that it will automatically
> handle the multiple groff passes required to resolve pdfmark cross
> references, if you use the -mpdfmark macro set. I don't know if -Tpdf
> will provide a similar level of supp
On 03/06/2014 07:29 AM, Keith Marshall wrote:
I've kept out of this debate, until now, primarily because I've yet to
formulate a defined opinion as to where I stand. However, I would like
to contribute a couple of pennyworth, at this juncture.
SGML technologies certainly have their place,
I've kept out of this debate, until now, primarily because I've yet to
formulate a defined opinion as to where I stand. However, I would like
to contribute a couple of pennyworth, at this juncture.
On 06/03/14 13:21, Ingo Schwarze wrote:
[...mostly snipped...]
>> The logical flow isn't groff =>
Hi Eric,
Eric S. Raymond wrote on Tue, Mar 04, 2014 at 12:57:20AM -0500:
> 4. Identify 'semantic' macro packages,
I fully agree with that.
> including man markup
Sorry, but you are completely wrong here.
The classical man(7) language is a purely presentational language
and contains exactly th
Hi Peter,
Peter Schaffter wrote on Mon, Mar 03, 2014 at 04:43:27PM -0500:
> if we're to figure out what to do about groff in the future,
> we're going to have to stick to the big picture.
Actually, as long as there is nobody who has the time and interest
and skills to actually do some groff C++
I respect the idea of a tribal society and I'm aware that FOSS needs
it. Being myself a standalone savage creature, I'm aware I am not
able to participate in this structure more than giving some opinion.
Do you really want a modern approach?
Man Pages
OSs should include just plain ASCII Englis
On 05/03/14 23:39, GregExp wrote:
> thank you for your help.
> The file I sended was make with
>
> groff -me -k -t foo > foo.pdf
And therein lies your problem: simply naming the file "foo.pdf" does not
magically make it a PDF file; it remains an improperly named PS file,
(because groff's default
21 matches
Mail list logo
