Re: [groff] Now online: gropdf / grops previewer

Hey Branden, > I'd love to see what the source looks like, but when I alter the URL, I > get a bunch of 404s. Everything is on GitHub . The browser-friendly version is on a separate branch , as I had to do a

Re: [groff] groff as the basis for comprehensive documentation?

It's taken me several hours to write this, so it damn well better be enlightening. > What i meant by the above sentence is that the CSS you gave, > with the exception of the dfn{} and kbd{} selectors, selects > nothing based on kind or class of content or semantic function. > … > consequently,

Re: [groff] Now online: gropdf / grops previewer

At 2018-04-23T09:04:25+1000, John Gardner wrote: > Well, here it is: > > https://rawgit.com/Alhadis/Roff.js/web-demo/index.html > > Some modifications were needed for web-delivery, and performance still > isn't optimal, but it works. You'll need a relatively recent browser to use > it (anything

[groff] Now online: gropdf / grops previewer

Well, here it is: https://rawgit.com/Alhadis/Roff.js/web-demo/index.html Some modifications were needed for web-delivery, and performance still isn't optimal, but it works. You'll need a relatively recent browser to use it (anything released within the last year should do). Few things to note

Re: [groff] Savannah bug field usage protocol

At 2018-04-22T11:29:39+0100, Colin Watson wrote: > On Sat, Apr 21, 2018 at 05:43:12PM -0400, G. Branden Robinson wrote: > > Our commit discipline is already supposed to include updating the > > ChangeLog, and, where appropriate, NEWS files as part of the commit > > where the underlying change is

Re: [groff] groff as the basis for comprehensive documentation?

Hi John, John Gardner wrote on Sat, Apr 21, 2018 at 04:48:33PM +1000: > Ingo, I've spent the last 13 years in front-end web development, > and I've been writing standards-compliant websites for almost > a decade. Sounds like you might have valueable input that could end up improving the mandoc

Re: [groff] groff as the basis for comprehensive documentation?

Hi Branden, G. Branden Robinson wrote on Sat, Apr 21, 2018 at 03:06:14AM -0400: > At 2018-04-20T23:19:44+0200, Ingo Schwarze wrote: >> John Gardner wrote: >>> Ingo Schwarze wrote: man://mandoc.1#EXIT_STATUS >>> Now, as for the SHOUTY SHOUTY... >> That's not a matter of SHOUTING, but of

Re: [groff] groff as the basis for comprehensive documentation?

Hi Larry, Larry Kollar wrote on Sat, Apr 21, 2018 at 10:44:43AM -0400: > I'm in violent agreement with your and Brandon's assessment > of all-caps headings. Shoot, there aren't many > terminal programs that *can't* do bold these days; > I think even that VT220 I keep > planning to connect to my

Re: [groff] groff as the basis for comprehensive documentation?

Hi Nate, Nate Bargmann wrote on Sat, Apr 21, 2018 at 12:59:16PM -0500: > But why do we focus on presentation when authoring a document? > I think that in large part we have trained ourselves to do so > using the various desktop word processing/publishing programs > that came down the pike. >

Re: [groff] groff as the basis for comprehensive documentation?

Hi James and Nate, James K. Lowden wrote on Sat, Apr 21, 2018 at 06:58:59PM -0400: > On Sat, 21 Apr 2018 08:16:36 -0500 Nate Bargmann wrote: >> Note that I am only working with Groff's man macro package and do >> understand that other macro packages may have greater demands on the >> HTML

Re: [groff] groff as the basis for comprehensive documentation?

On Sat 21 Apr 2018 08:16:36 Nate Bargmann wrote: > Note that I am only working with Groff's man macro package and do > understand that other macro packages may have greater demands on the > HTML generator. You might consider supporting mdoc macros. You may have seen:-

Re: [bug #53547] [PATCH] tmac/groff_ms.7.man: Change bold '[' and ']' to roman and other tidying

Hi Branden, G. Branden Robinson wrote on Sun, Apr 22, 2018 at 02:42:27AM -0400: > Follow-up Comment #6, bug #53547 (project groff): > > I did not find any need for this: > > \# The next argument must be longer than the indent from .TP (8n) > > or the spaces they refer to, nor for the

Re: [groff] Savannah bug field usage protocol

On Sat, Apr 21, 2018 at 05:43:12PM -0400, G. Branden Robinson wrote: > At 2018-04-21T14:21:03+0100, Ralph Corderoy wrote: > > Some projects maintain a `pending' release notes so that significant > > fixes and changes get added to as they're implemented. This might avoid > > the need to keep some

[bug #53547] [PATCH] tmac/groff_ms.7.man: Change bold '[' and ']' to roman and other tidying

Update of bug #53547 (project groff): Open/Closed:Open => Closed ___ Reply to this item at: ___

[bug #53547] [PATCH] tmac/groff_ms.7.man: Change bold '[' and ']' to roman and other tidying

Update of bug #53547 (project groff): Status: In Progress => Fixed ___ Reply to this item at: ___

[groff] 04/04: groff_ms(7): Make style fixes.

gbranden pushed a commit to branch master in repository groff. commit dbfa0b757b920eb6c44a2fd319180f525b138a28 Author: G. Branden Robinson Date: Sun Apr 22 02:38:52 2018 -0400 groff_ms(7): Make style fixes. * Escape hyphens used as minus signs or

[groff] 02/04: groff_man(7): Expand command synopsis section.

gbranden pushed a commit to branch master in repository groff. commit 5599c6decdc82d146b216b7111adfd55fa958294 Author: G. Branden Robinson Date: Sun Apr 22 01:51:43 2018 -0400 groff_man(7): Expand command synopsis section. This section now explains

[groff] 03/04: groff_ms(7): Correct apparent factual error.

gbranden pushed a commit to branch master in repository groff. commit ce142838ee78eb2b247e841ed73fac0e59c55584 Author: G. Branden Robinson Date: Sun Apr 22 02:16:23 2018 -0400 groff_ms(7): Correct apparent factual error. It doesn't seem to actually

[bug #53547] [PATCH] tmac/groff_ms.7.man: Change bold '[' and ']' to roman and other tidying

Follow-up Comment #6, bug #53547 (project groff): I did not find any need for this: \# The next argument must be longer than the indent from .TP (8n) or the spaces they refer to, nor for the transparent line indicators. Things seem to be rendering fine both to the utf8 and PDF output

[bug #53547] [PATCH] tmac/groff_ms.7.man: Change bold '[' and ']' to roman and other tidying

Update of bug #53547 (project groff): Severity:1 - Wish => 2 - Minor ___ Reply to this item at: ___