Hi Peter,
> Serving PDF manuals from the web has drawbacks, possibly serious ones:
> it assumes an installed PDF reader, and there's significant latency
> involved with firing one up.
I think the first assumption is reasonable these days, and the second I
only notice if it's Adobe Reader.
> [Der
Hi,
James K. Lowden wrote on Tue, Mar 18, 2014 at 12:03:33AM -0400:
> On Mon, 17 Mar 2014 21:49:49 -0400 Peter Schaffter wrote:
>> Serving PDF manuals from the web has drawbacks, possibly
>> serious ones: it assumes an installed PDF reader, and there's
>> significant latency involved with firing
Am 17.03.2014 22:44, schrieb Peter Schaffter:
...
On the subject of implementing Heirloom troff's paragraph-at-once
formatting and associated goodies, I wrote Gunnar about it. Here's
what he had to say:
"Sorry, but I haven't done anything related to those topics for
several years. I've ne
On Tue 18 Mar 2014 12:58:09 Ingo Schwarze wrote:
> Security-wise, PDF is
> one of the most dangerous file formats, nowadays.
That is true if the pdf reader you are using is configured to action all the
extra bits which Adobe added to the standard (i.e. forms, flash and
javascript). Without thes
Hello folks,
Peter Schaffter wrote:
> Here's the second draft of the mission statement, incorporating
> suggestions from Ingo, Eric, Pierre-Jean, and others. It's starting
> to come into focus, although a third pass will probably be necessary
> before we commit to it.
I mostly agree with that
The section dealing with manpages had me hemming and hawing for
days. The original wording wasn't vague; it stated the matter
clearly--the intention to improve the semantic usefulness of
manpage markup. Details of strategy/implementation were omitted
because the issue is a minefield, and part of
On Tue, Mar 18, 2014, Joachim Walsdorff wrote:
> it would be fine if you could provide an example text, formatted
> both with groff and Heirloom troff, to demonstrate us the
> typographic gain by `paragraph-at-once formatting´ against `line
> formatting´.
http://heirloom.sourceforge.net/doctools
Peter Schaffter wrote:
> On Tue, Mar 18, 2014, Joachim Walsdorff wrote:
> > it would be fine if you could provide an example text, formatted
> > both with groff and Heirloom troff, to demonstrate us the
> > typographic gain by `paragraph-at-once formatting´ against `line
> > formatting´.
>
>
On Tue, 18 Mar 2014 10:29:50 -0400
Peter Schaffter wrote:
> On Tue, Mar 18, 2014, Joachim Walsdorff wrote:
> > it would be fine if you could provide an example text, formatted
> > both with groff and Heirloom troff, to demonstrate us the
> > typographic gain by `paragraph-at-once formatting´ aga
On Tue, Mar 18, 2014, Pierre-Jean wrote:
> Nonetheless, I think that if the goal is to publish this
> mission statement in the hope that it encourages people to
> join the groff community, a bit more of « writing art » will
> be needed: words that encourage someone to come and work on
> groff.
I a
I wrote..
|find below something that adds the mentioned options and also
|tweaks the make system a bit -- 'make install' and 'make
|uninstall' seem to work again after the patch series is applied.
|There are still problems ('make install' with DESTDIR set results
|in some errors along the way,
Hi Steffen,
> That is, tr(1) is buggy
tr(1) seems to be behaving as I'd expect. The \n is a control character
and is being turned into space so you have to add another with echo. It
thinks 0-0x1f and 0x7f are cntrl.
$ recode /test8 tr -c '[:cntrl:]' - |
> tr '[:cntrl:]' c |
> fold
Heya, Ralph,
Ralph Corderoy wrote:
|Hi Steffen,
|
|> That is, tr(1) is buggy
|
|tr(1) seems to be behaving as I'd expect. The \n is a control character
oh yes, compilation on CRUX-3 Linux succeeds without any problems,
the font listing is worked from top to bottom.
Now the only problem th
Hi,
Deri James wrote on Tue, Mar 18, 2014 at 01:26:02PM +:
> On Tue 18 Mar 2014 12:58:09 Ingo Schwarze wrote:
>> Security-wise, PDF is one of the most dangerous file formats, nowadays.
> That is true if the pdf reader you are using is configured to action
> all the extra bits which Adobe add
Hi Peter,
Peter Schaffter wrote on Mon, Mar 17, 2014 at 05:44:21PM -0400:
> Here's the second draft of the mission statement,
It is clearly maturing.
[...]
> The section dealing with manpages had me hemming and hawing for
> days. The original wording wasn't vague; it stated the matter
> clearl
Peter Schaffter :
> Ignorance about groff as a complete typesetting system is
> practically pandemic. After five editions, O'Reilly's _Running
> Linux_ still demonstrates groff usage with a tutorial on writing
> manpages. And recently, I came upon this parenthetical comment at
> the Simon Fraser
Ingo Schwarze :
> Actually, there are four questions that are somewhat separate
> but also influence each other a bit:
>
> (1) What are we to do with man(7)?
> Eric proposes to carefully evolve it to introduce a small amount
> of semantic markup.
> I propose to provide continuing s
On Tue, Mar 18, 2014, Kristaps Dzonsons wrote:
> My agenda is just to have good manpages. To me, good means
> portable across systems and media, adhering to a common style, and
> having human-readable source. Good on GNU systems, BSD, HTML,
> PS... "good".
That puts us on the same page. :)
> T
On Tue, Mar 18, 2014, Eric S. Raymond wrote:
> > Peter Schaffter :
> > If groff is as powerful as TeX while being one tenth the size,
> > why on earth does the author dismiss it out-of-hand as weirdly
> > retrotech?
>
> That's not a mystery to me. If it stays one to you, we have a
> problem; yo
I am jumping in here, for which I apologize, because I have
not had enough time over the last couple of months to become
inovled in this discussion. All my spare time outside of my
regular work during this period has been spent typesetting with
groff: two newsletters, and a 200-plus-page book with
20 matches
Mail list logo
