Hi James,
James K. Lowden wrote on Wed, Dec 05, 2018 at 11:29:37AM -0500:
> On Tue, 4 Dec 2018 05:40:58 +0100 Ingo Schwarze wrote:
>> For PDF output, by all means, use groff, it is much, much better
>> than mandoc for that. For mdoc to HTML, don't.
> Ingo, my colleague says the man macros EX an
On Tue, 4 Dec 2018 05:40:58 +0100
Ingo Schwarze wrote:
> For PDF output, by all means, use groff, it is much, much better
> than mandoc for that. For mdoc to HTML, don't.
Ingo, my colleague says the man macros EX and EE aren't supported on
the version of FreeBSD he uses, which I assume is using
Hi James,
James K. Lowden wrote on Mon, Dec 03, 2018 at 04:46:31PM -0500:
> I converted the Heimdal kf.1 page to html recently, and found what I
> consider to be problems with both appearance and HTML style.
For mdoc(7) input in particular, do not use "groff -mdoc -T html".
Use "mandoc -T html
>From gaius.mul...@southwales.ac.uk Thu Apr 14 20:37:49 2016
>
>I'd try changing it to:
>
>.if !'\*(.T'html' .na
>
>and also you could try:
>
>.if '\*(.T'html' .ll 20i
>.\" aweful hack I know
Doesn't make any difference, still
the white space between the last 2 words
in the longer headers is gon
Anton Shterenlikht writes:
>>From gaius.mul...@southwales.ac.uk Thu Apr 14 16:02:42 2016
>>
>>I wonder if it might be worth commenting out the .RP and see if html
>>generation works? It appears to be influencing the initial macros
>>which might be conflicting with html.
>
> Actually, after fixin
>From gaius.mul...@southwales.ac.uk Thu Apr 14 16:02:42 2016
>
>I wonder if it might be worth commenting out the .RP and see if html
>generation works? It appears to be influencing the initial macros
>which might be conflicting with html.
Actually, after fixing the .XS/.XE placement issue,
the ou
Anton Shterenlikht writes:
> I get this error:
>
> ./doc.1:4: macro error: RP is not allowed after the first page has started
>
> The command I invoke is:
>
> /usr/local/bin/groff -ept -ms -Thtml -P -Dhtmlimg -P -r -VV doc.ref > doc.html
>
> where doc.ref is the file after processing with soelim
Hi Anton,
> Are restrictions on the placement of XS/XE documented somewhere?
I suspect this is more that you've found a bug. :-)
Cheers, Ralph.
> Do you otherwise find the output is OK?
I think I found the problem.
I cut down the document until the
html looked ok. The problem seems to
appear when I use XS/XE immediately after NH,
e.g.
rat> cat bad.1
.NH 1
A title
.XS
A title
.XE
.PP
Some text
rat> /usr/local/bin/groff -ms -Thtml bad.1 >
>From ra...@inputplus.co.uk Thu Apr 14 12:50:29 2016
>
>I suspect the error can be ignored the two times it appears for you.
Ralph, thank you for a detailed analysis.
>Do you otherwise find the output is OK?
no, not at all:
http://eis.bris.ac.uk/~mexas/doc.html
I have other errors and warnings
Hi Anton,
> I get this error:
>
> ./doc.1:4: macro error: RP is not allowed after the first page has started
ms changes RP from its normal definition to triggering this error when a
`.wh 0' trap is triggered at the top of the page.
> The command I invoke is:
>
> /usr/local/bin/groff -ept
>From gaius.mul...@southwales.ac.uk Wed Apr 13 15:53:13 2016
>>
>> soelim doc.1 | pic | tbl | eqn -Tps:html | pre-grohtml troff -ms
>> -Thtml | post-grohtml
>>
>> What if I have a file that has already been processed
>> by soelim and refer?
>
>multiple preprocessing via soelim is fine - a no-op.
T
Hi Gaius,
> multiple preprocessing via soelim is fine - a no-op.
Good point. Though failed .so, e.g. `.so missing-file', are passed
through to the output and could in theory do something different on a
second pass. ;-)
Cheers, Ralph.
Anton Shterenlikht writes:
Anton Shterenlikht writes:
> So how do I use grohtml?
> As groff -Thtml?
>
> Using groff -Thtml -V shows me this pipeline:
>
> soelim doc.1 | pic | tbl | eqn -Tps:html | pre-grohtml troff -ms
> -Thtml | post-grohtml
>
> What if I have a file that has already been proc
>> What does -Tps:html mean?
>
> Yes, is the colon a special character here?
`ps:html' is used internally in the groff pipeline for communication
with eqn to enforce generation of image tags if inside of a pic image
(as needed by HTML output).
Werner
Hi Anton,
> As groff -Thtml?
Yes, that's easiest as groff knows what needs doing in various places
for the other programs.
> Using groff -Thtml -V shows me this pipeline:
>
> soelim doc.1 | pic | tbl | eqn -Tps:html |
> pre-grohtml troff -ms -Thtml | post-grohtml
>
> What if I have a file th
So how do I use grohtml?
As groff -Thtml?
Using groff -Thtml -V shows me this pipeline:
soelim doc.1 | pic | tbl | eqn -Tps:html | pre-grohtml troff -ms
-Thtml | post-grohtml
What if I have a file that has already been processed
by soelim and refer?
What does -Tps:html mean?
Thanks
Anton
i wrote:
|Anton Shterenlikht wrote:
||On FreeBSD 11-current, with groff 1.22 installed
||
||rat> pkg info -xo groff
||groff-1.22.2_4 textproc/groff
||rat> pkg info -xl groff|grep groh
||/usr/local/bin/post-grohtml
||/usr/local/bin/pre-grohtml
||/usr
Anton Shterenlikht wrote:
|On FreeBSD 11-current, with groff 1.22 installed
|
|rat> pkg info -xo groff
|groff-1.22.2_4 textproc/groff
|rat> pkg info -xl groff|grep groh
|/usr/local/bin/post-grohtml
|/usr/local/bin/pre-grohtml
|/usr/local/man/man1/gro
>> I tried adding a new line to ...\font\devutf8\r:
>>
>> u0410 24 0 0x411
>>
>> deliberately incrementing the device code by one,
>> and it did work!
>
> Doing this you are overriding the default mapping built into
> grohtml.
^^^
This is a typo, of course. I mean the utf8 device
> I tried adding a new line to ...\font\devutf8\r:
>
> u0410 24 0 0x411
>
> deliberately incrementing the device code by one,
> and it did work!
Doing this you are overriding the default mapping built into grohtml.
> Why doesn't the same action (when tested with the same input file)
> w
> Now I am trying to understand a very simple case: for the latin1
> device, no font definition contains a glyph named [`A],
??? I have this line in font/devlatin1/R:
`A 24 0 0300
Werner
Myself:
> Now I am trying to understand a very simple case:
> for the latin1 device, no font definition contains
> a glyph named [`A], while it is this glyph that
> [char192] maps to (by latin1.tmac). And this works
> correctly without any warning messages. Where does
> groff take the definiti
Another pecuilarity: When I use:
troff -mkoi8-r -Thtml test.roff > test.out
it works correctly and does not issue any warning
messages, but the command
pre-grohtml troff -mkoi8-r -Thtml test.roff > \
test.out
does issue the "can't find special character" warn-
ings. What is it that
Myself:
> 1. I tried to define glyphs for the characters
> reported in the abovementioned warnings, in
> the ...\fontevhtml\r file like this:
> [...]
Now I am trying to understand a very simple case:
for the latin1 device, no font definition contains a
glyph named [`A]
> [...] Second, he tells me that his opinion is that instead of me
> worrying about trying to repair his macros (which was my first
> impulse, to fix them, and then add calls to them in a little adapter
> macro package), I should instead try to see if I can fit my fixes
> all directly into the mm
Larry Kollar wrote:
> Chuck, did you see my response on 9 Dec?
> http://lists.gnu.org/archive/html/groff/2009-12/msg8.html
>
> One way or another, you have to get an HTML list wrapper to appear in the
> output, that should give you the break you need.
No, I hadn't seen that, it occurred (ap
Meg McRoberts wrote:
> I just checked and Amazon has 9 used copies available, two for
> less that $10:
>
> http://www.amazon.com/gp/offer-listing/0810462915/ref=dp_olp_used?ie=UTF8&condition=used
>
> Six are available at half.com:
>
> http://product.half.ebay.com/Unix-Text-Processing_W0QQtgZinfo
Miklos Somogyi wrote:
>
> My bible is a well-worn photocopy of "Using nroff & troff" from 1990.
> I wish that a pdf of it would float around somewhere to download and
> search ...
I'm forever interested in new sources of roff info ... so could you please
amplify on that reference? I mean, exact
Chuck Robey wrote:
> ... I was
> stating that I have no problem whatsoever with the mm macros when they're
> going
> to postscript or ascii, but when I have them as html output, the mm list
> macros
> show up very, very, badly. It looks like there isn't any leading spacing
> allowed after I u
> You ever see the Sam's book on Unix system typesetting?
There was a large project to retype the `Unix text processing' book
with groff (with permission from the authors)! The result is
available from here:
http://groff.ffii.org/groff/contrib/documentation/utp/
Werner
> Of course, I got this right after AI sent my mail to Gaius Mulley
> and Werner Lemberg. I asked them to decide about bothering the
> list, so I'll leave it up to them, such a thing as this is really,
> really going to raise the noise level here (for the short term) so I
> want to be certain I w
>> Look, I think I'm going to probably bore the list to death over the
>> rather dense topic of the html macros, so unless I get some
>> comments here and now, I'll take this private to Gaius Mulley and
>> Werner Lemberg.
Please don't. I haven't much time these days for groff...
> Bearing in mi
8/09, Chuck Robey wrote:
> From: Chuck Robey
> Subject: Re: [Groff] grohtml again
> To: rob...@thorsby.com.au
> Cc: groff@gnu.org
> Date: Monday, December 28, 2009, 6:37 PM
> Robert Thorsby wrote:
> > On 29/12/09 12:35:37, Chuck Robey wrote:
> >> You e
My bible is a well-worn photocopy of "Using nroff & troff" from 1990.
I wish that a pdf of it would float around somewhere to download and
search ...
Miklos
On 29/12/2009, at 01:37 PM, Chuck Robey wrote:
Robert Thorsby wrote:
On 29/12/09 12:35:37, Chuck Robey wrote:
You ever see the Sa
Robert Thorsby wrote:
> On 29/12/09 12:35:37, Chuck Robey wrote:
>> You ever see the Sam's book on Unix system
>> typesetting? I think I saw a pdf of it on
>> the web a year or two ago, (I have TWO
>> printed copies of it!), and you ought to
>> consider looking at it, it's easily the most
>> reada
On 29/12/09 12:35:37, Chuck Robey wrote:
> You ever see the Sam's book on Unix system
> typesetting? I think I saw a pdf of it on
> the web a year or two ago, (I have TWO
> printed copies of it!), and you ought to
> consider looking at it, it's easily the most
> readable things on all aspects of r
Robert Thorsby wrote:
> On 29/12/09 12:01:07, Chuck Robey wrote:
>> Look, I think I'm going to probably bore
>> the list to death over the rather dense
>> topic of the html macros, so unless I get
>> some comments here and now, I'll take
>> this private to Gaius Mulley and Werner Lemberg.
>
> Bear
On 29/12/09 12:01:07, Chuck Robey wrote:
> Look, I think I'm going to probably bore
> the list to death over the rather dense
> topic of the html macros, so unless I get
> some comments here and now, I'll take
> this private to Gaius Mulley and Werner Lemberg.
Bearing in mind that this is a low tr
Keith Marshall wrote:
> On Monday 28 December 2009 21:32:26 Chuck Robey wrote:
>> I don't want to violate anyone's privacy, but would it be proper
>> to ask the email address of the programmer who wrote the www.tmac
>> code?
>
> Did you read the header in www.tmac itself? There I see:
Yeah, I lo
On Monday 28 December 2009 21:32:26 Chuck Robey wrote:
> I don't want to violate anyone's privacy, but would it be proper
> to ask the email address of the programmer who wrote the www.tmac
> code?
Did you read the header in www.tmac itself? There I see:
|.ig
|www.tmac - macro package for adding
Mike Bianchi wrote:
> Chuck,
>
> As a fellow lover of mm (since the mid-1970s) I will try to help.
> Please send along:
> example files that illustrate your issues, both sources and results
> the simpler the examples, the better
>
> the command lines you use to create th
Chuck,
As a fellow lover of mm (since the mid-1970s) I will try to help.
Please send along:
example files that illustrate your issues, both sources and results
the simpler the examples, the better
the command lines you use to create the results from the sources
Gaius Mulley wrote:
> Chuck Robey writes:
>> My problem is in trying to use mm macro's list macros, for html output only.
>> I'm currently working around this by using chapters instead, but that's a
>> very
>> unsatisfactory solution. The problem is that when you begin the list, there
>> is
>>
Chuck Robey writes:
> I'm a very long-term user of groff (with the mm macros), I have a problem with
> my new attempts to get html output, and I'd appreciate either knowing if my
> problem has already been attended to, or if I need to try to do it myself,
> then
> maybe a pointer telling me whe
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> > Basically here is a patch for -me which allows the preprocessors:
> > tbl, eqn, gremlin to so something sensible with me based source
> > files. It also fixes titles, headings, paragraphs, indented
> > paragraphs, keeps, indices and a few other macro
> Basically here is a patch for -me which allows the preprocessors:
> tbl, eqn, gremlin to so something sensible with me based source
> files. It also fixes titles, headings, paragraphs, indented
> paragraphs, keeps, indices and a few other macros.
Applied to the CVS (with minor modifications).
Hi Werner and Zvezdan,
here is a patch to help grohtml translate -me documents into html.
It also fixes the bug as reported by Zvezdan on the 2nd of January.
More cheating as ESR might put it :-)
It handles the preprocessors gremlin, tbl, eqn and macros for
titles, section headings, indices, ip,
Hi,
not sure if my previous email made it to the outside world so here it
goes again (apologies if multiple copies arrive). Basically here is a
patch for -me which allows the preprocessors: tbl, eqn, gremlin to so
something sensible with me based source files. It also fixes titles,
headings, pa
Zvezdan Petkovic <[EMAIL PROTECTED]> writes:
> After this point all the letters are too small for comfortable reading.
>
> Questions:
> - This is not a too complicated paragraph, yet is it broken in
> two paragraphs at "interpretation of". Why?
Hi,
it is missing the html specials
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> > I personally use groff for PDF and PostScript documents, so I did
> > not care for grohtml too much. The recent discussion about
> > doclifter prompted me to recheck, and it seems to be a little -ms
> > centric.
>
> This is correct. The -me macros
> I personally use groff for PDF and PostScript documents, so I did
> not care for grohtml too much. The recent discussion about
> doclifter prompted me to recheck, and it seems to be a little -ms
> centric.
This is correct. The -me macros don't have special support for HTML.
Baically, it's nec
Zvezdan Petkovic <[EMAIL PROTECTED]>:
> This is a part of a paragraph from an -me document.
BTW, doclifter lifts -me documrnts. It doesn't di a very good job,
however; me macros don't carry as much structural info as man, ms,
or mm.
--
http://www.catb.org/~esr/";>Eric S. Raymond
Hi again Larry,
> What status close() returns depends on your awk. And closing a pipe
> should wait for the command to finish so if you've a grep that
> produces 1E6 lines and you just want to read the first then pipe it
> into `sed 1q' before reading it into awk so the grep gets a SIGPIPE on
>
Walter Harms wrote, quoting Ralph Corderoy:
>> ... if you've a grep that produces
>> 1E6 lines and you just want to read the first then pipe it into
>> `sed 1q' before reading it into awk so the grep gets a SIGPIPE on
>> writing to the finished sed, curtailing its largess.
>
> To access head or tai
Hi Wh,
> Ralph Corderoy wrote:
> > What status close() returns depends on your awk. And closing a pipe
> > should wait for the command to finish so if you've a grep that
> > produces 1E6 lines and you just want to read the first then pipe it
> > into `sed 1q' before reading it into awk so the gr
Ralph Corderoy wrote:
> Hi Larry,
>
>> Groff was barfing with a "too many open files" error, which I worked around
>> by doing "ulimit -n 768" first. I ended up with over 640 HTML files. I'm not
>> sure why all every output file has to be open at once, though.
>
>
> $
>
> What status clo
Hi Larry,
> Groff was barfing with a "too many open files" error, which I worked around
> by doing "ulimit -n 768" first. I ended up with over 640 HTML files. I'm not
> sure why all every output file has to be open at once, though.
Sounds like either a bug or a design artifact that'll need fix
Larry Kollar <[EMAIL PROTECTED]> writes:
> This is partly groff, and partly a utilities issue.
>
> I'm well along the way to getting grohtml output to work with OmniHelp, an
> LGPL'ed "HTML help" viewer [http://www.omsys.com/dcl/omnihelp.htm]. I
> have one last snag to work out, which is relate
Larry Kollar <[EMAIL PROTECTED]> writes:
> Gaius Mulley wrote:
>
> > > Putting a PS file before the '.TL' in a -ms file causes grohtml to hang
> > > at
> the
> > > beginning of generating HTML. This used to work, but I think it broke
> > > between 1.19.1 and 1.19.2.
> > >
> > > $ awk -f htb
Gaius Mulley wrote:
> > Putting a PS file before the '.TL' in a -ms file causes grohtml to hang at
the
> > beginning of generating HTML. This used to work, but I think it broke
> > between 1.19.1 and 1.19.2.
> >
> > $ awk -f htbl.awk test.ms | groff -ms -mtrace -mwww -Thtml -P-n -P-r
-
>
Larry Kollar <[EMAIL PROTECTED]> writes:
> Putting a PS file before the '.TL' in a -ms file causes grohtml to hang at
> the
> beginning of generating HTML. This used to work, but I think it broke
> between 1.19.1 and 1.19.2. Here's an example file:
>
> .\" begin
> \&
> .sp 2i
> .tm o
> The CVS isn't building grohtml.
It does.
> post-grohtml*
This is it, in combination with the pre-grohtml preprocessor binary.
Werner
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
Larry Kollar <[EMAIL PROTECTED]> writes:
> The CVS isn't building grohtml. I deleted src/devices/grohtml and updated, no
> difference. Here's a listing of the directory (after making), if that helps
> at all:
>
> % l src/devices/grohtml/
> CVS/grohtml.n html-text.cpp output.
> I wonder why it is that paragraphs inside a -ms .RS/.RE block get turned
> into a table by grohtml.
>
> The same happens with .IP. (maybe other requests too.)
>
> Wouldn't it be better if a were generated with an indentation? And
> an unordered list for .IPs?
>
> For example...
>
>
> .RS
Louis Guillaume <[EMAIL PROTECTED]> writes:
> Hi Everyone,
>
> Just a thought. I was looking at the code for this today and I think
> it's not something I'd know how to fix. Anyway...
>
> I wonder why it is that paragraphs inside a -ms .RS/.RE block get
> turned into a table by grohtml.
>
> The
> > Uh, too late. Please provide a patch w.r.t. to the current CVS.
>
> sure, here it is,
Applied, thanks.
Werner
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> > here is a better patch, I broke formatted text with the last
> > patch,
>
> Uh, too late. Please provide a patch w.r.t. to the current CVS.
>
>
Hi Werner,
sure, here it is,
Gaius
--- groff-cvs/src/devices/grohtml/post-html.cpp Wed Feb 16 14:
> here is a better patch, I broke formatted text with the last
> patch,
Uh, too late. Please provide a patch w.r.t. to the current CVS.
Werner
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
Gaius Mulley <[EMAIL PROTECTED]> writes:
> Werner LEMBERG <[EMAIL PROTECTED]> writes:
>
> > Gaius,
> >
> >
> > look at chapter 15.4 in pic-15.html. There you can see this:
> >
> > sh { anything...
> >
> >}
> >
> > but it should be this:
> >
> > sh { anything... }
> >
> > Definitel
70 matches
Mail list logo
