Re: [Groff] The future redux

2014-02-26 Thread James K. Lowden
On Wed, 26 Feb 2014 11:46:32 + Ralph Corderoy wrote: > > > man pages don't really need expressive typography. > > > > Man pages are constrained by xterm. A better display system would > > invite tables, graphs, equations, and links. > > I don't think they are. Or they didn't used to b

Re: [Groff] The future redux

2014-02-26 Thread Federico Lucifredi
While we are (slightly) digressing, may I ask the broader group, what are the best current tutorials for Groff? Most of the material I know of is… rather dated. Not necessarily bad, but not very recent either - and not very concise, either. What do you point to get new users started? What’s th

Re: [Groff] The future redux

2014-02-26 Thread Tadziu Hoffmann
> Three browsers, three layouts (surf uses webkit). Hmmm, well, I suspect if you used groff with -Tlatin1, -Tlj4, -Tdvi, and -Tps you might also get four different layouts... Simply consider different browsers like different devices. > Firefox's is perfect! It's better than the others, but I w

Re: [Groff] The future redux

2014-02-26 Thread Federico Lucifredi
On Feb 26, 2014, at 8:19 AM, Ralph Corderoy wrote: > Hi Walter, > >> Man pages are not tutorials or complete manuals > > Yes they are, or should be. They used to be. I learnt Perl 4 from > perl(1). Back then it was a single long man page, well-written by an > experienced Unix hand, Larry Wa

Re: [Groff] The future redux

2014-02-26 Thread hohe72
No, despite the Typos. Three browsers, three layouts (surf uses webkit). Firefox's is perfect! Holger "Eric S. Raymond" wrote (Wed, 26 Feb 2014 10:42:52 -0500): > hoh...@arcor.de : > > > Some years ago I enhanced geqn so it can emit MathML. > > > > What did I wrong? > > To emit MathXML get

Re: [Groff] The future redux

2014-02-26 Thread Walter Alejandro Iglesias
On Wed, Feb 26, 2014 at 01:19:14PM +, Ralph Corderoy wrote: > Hi Walter, > >> Man pages are not tutorials or complete manuals > > Yes they are, or should be. They used to be. I learnt Perl 4 from > perl(1). Back then it was a single long man page, well-written by an > experienced Unix hand,

Re: [Groff] The future redux

2014-02-26 Thread Mike Bianchi
On Wed, Feb 26, 2014 at 04:08:45PM +, Deri James wrote: >>On Wed 26 Feb 2014 10:19:07 Mike Bianchi wrote: >>> I cannot find  man.config  or any reference to it in Debian 7.4 >>(wheezy). >It looks like on debian the answer is to create a shell script called >"mandb_tfmt"

Re: [Groff] The future redux

2014-02-26 Thread Deri James
On Wed 26 Feb 2014 10:19:07 Mike Bianchi wrote: > I cannot find man.config or any reference to it in Debian 7.4 (wheezy). > 2.6.2 2012-06-18 MAN(1) > Only manpath.config . > > What am I missing? > > -- > Mike Bianchi > Foveal Systems > > 973 822-2085 It looks like on debian t

Re: [Groff] The future redux

2014-02-26 Thread Eric S. Raymond
hoh...@arcor.de : > > Some years ago I enhanced geqn so it can emit MathML. > > What did I wrong? To emit MathXML getqn needs an option that is not suppliued by the normal groff pipeline. -- http://www.catb.org/~esr/";>Eric S. Raymond

Re: [Groff] The future redux

2014-02-26 Thread Ralph Corderoy
Hi Mike, > > It may be necessary to alter the man.config command I gave for other > > pdf readers. > > I cannot find man.config or any reference to it in Debian 7.4 > (wheezy). > 2.6.2 2012-06-18 MAN(1) > Only manpath.config . > > What am I missing? Perhaps Deri's using BSD. http:/

Re: [Groff] The future redux

2014-02-26 Thread Clarke Echols
On 02/25/2014 11:59 PM, Volker Wolfram wrote: Hi all groffers, in fact I'm a newbie on groff tools and macros. But these tools are the BEST I've used EVER. I enjoy groff so much, I've developed my own three side perspective CAD macro to made my needs. And a macro for electrical and pipe sche

Re: [Groff] The future redux

2014-02-26 Thread Mike Bianchi
On Wed, Feb 26, 2014 at 02:42:45PM +, Deri James wrote: > : > It may be necessary to alter the man.config command I gave for > other pdf readers. I cannot find man.config or any reference to it in Debian 7.4 (wheezy). 2.6.2 2012-06-18 MAN(1) Only manpath.config . What am

Re: [Groff] The future redux

2014-02-26 Thread Clarke Echols
On 02/26/2014 06:33 AM, Tadziu Hoffmann wrote: Man pages are not tutorials or complete manuals Yes they are, or should be. They used to be. Fairly complete manuals, yes; tutorials, I don't think they ever were. The manual page for the fortran compiler says what the compiler options are

Re: [Groff] The future redux

2014-02-26 Thread hohe72
"Eric S. Raymond" wrote (Wed, 26 Feb 2014 08:29:00 -0500): > hoh...@arcor.de : > > I don't got to what extend the support of web/ html features shall > > be supported -- catchword: use case. For instance, will eqn code be > > traversed to MathJax? > > Some years ago I enhanced geqn so it can e

Re: [Groff] The future redux

2014-02-26 Thread Deri James
On Wed 26 Feb 2014 13:46:22 Walter Alejandro Iglesias wrote: > What do you want in a man page? Videos? 3D holograms? Only if they would help give an answer to the question you are trying to answer! > XTerm does not constrain nothing. It does what is expected from a terminal. > Do you think y

Re: [Groff] The future redux

2014-02-26 Thread Ralph Corderoy
Hi Tadziu, > > > Man pages are not tutorials or complete manuals > > > > Yes they are, or should be. They used to be. > > Fairly complete manuals, yes; tutorials, I don't think they ever > were. Yes, I was referring only to the "complete manuals" bit. Thanks for pointing out my ambiguity. I

Re: [Groff] The future redux

2014-02-26 Thread Tadziu Hoffmann
> > Man pages are not tutorials or complete manuals > > Yes they are, or should be. They used to be. Fairly complete manuals, yes; tutorials, I don't think they ever were. The manual page for the fortran compiler says what the compiler options are -- it does not teach you programming in fortr

Re: [Groff] The future redux

2014-02-26 Thread Daode
Volker Wolfram wrote: |Hi all groffers, | |in fact I'm a newbie on groff tools and macros. But these \ |tools are the BEST I've used EVER. I enjoy groff so much, I've developed my I fully agree -- after almost going stony because of loosing system content _and_ the backups (forgotten PGP pass

Re: [Groff] The future redux

2014-02-26 Thread Eric S. Raymond
hoh...@arcor.de : > I don't got to what extend the support of web/ html features shall be > supported -- catchword: use case. For instance, will eqn code be > traversed to MathJax? Some years ago I enhanced geqn so it can emit MathML. -- http://www.catb.org/~esr/";>Eric S. Raymond

Re: [Groff] The future redux

2014-02-26 Thread Ralph Corderoy
Hi Walter, > Man pages are not tutorials or complete manuals Yes they are, or should be. They used to be. I learnt Perl 4 from perl(1). Back then it was a single long man page, well-written by an experienced Unix hand, Larry Wall. I learnt ed and sed the same way many years before that. And

Re: [Groff] The future redux

2014-02-26 Thread Walter Alejandro Iglesias
On Wed, Feb 26, 2014 at 12:00:53PM +, Deri James wrote: > On Wed 26 Feb 2014 11:46:32 Ralph Corderoy wrote: >> Hi jkl, >> man pages don't really need expressive typography. >>> >>> Man pages are constrained by xterm. A better display system would >>> invite tables, graphs, equations, and

Re: [Groff] The future redux

2014-02-26 Thread Deri James
On Wed 26 Feb 2014 11:46:32 Ralph Corderoy wrote: > Hi jkl, > > > > man pages don't really need expressive typography. > > > > Man pages are constrained by xterm. A better display system would > > invite tables, graphs, equations, and links. > > I don't think they are. Or they didn't used to b

Re: [Groff] The future redux

2014-02-26 Thread Ralph Corderoy
Hi jkl, > > man pages don't really need expressive typography. > > Man pages are constrained by xterm. A better display system would > invite tables, graphs, equations, and links. I don't think they are. Or they didn't used to be. It was common to see man pages with `.if n' and `.if t', w

Re: [Groff] The future redux

2014-02-26 Thread Ralph Corderoy
Hi Eric, > Peter wrote: > > I think what happened is that, over time, near-exclusive use of the > > PostScript driver caused many of us to confuse groff output with > > grops output--if not intellectually, at least at the conceptual > > level. We began to think of groff as a PostScript typesettin

Re: [Groff] The future redux

2014-02-26 Thread hohe72
Volker Wolfram wrote (Wed, 26 Feb 2014 07:59:35 +0100): > And as a newbie I don't know about the code and design of groff. But > I've changed from LaTeX to groff because it is simple and easy to > understand. +1 Using Groff features a learning curve with raising success. > And that is very cool

Re: [Groff] The future redux

2014-02-26 Thread hohe72
I don't got to what extend the support of web/ html features shall be supported -- catchword: use case. For instance, will eqn code be traversed to MathJax? Holger