>
> *It relies on DocBook, which has by far the lowest quality man(7) code
> generator on the planet.*
I'd say second-lowest... you should see marked(1)'s output:
https://github.com/markedjs/marked/blob/master/man/marked.1
On 6 March 2018 at 03:50, Ralph Corderoy wrote:
> Hi Ingo,
>
> > > It'
> Would it be possible to include these simple fixes in 1.22.4?
>
> https://lists.gnu.org/archive/html/groff/2017-02/msg00015.html
> https://lists.gnu.org/archive/html/groff/2017-02/msg00017.html
LGTM.
> And maybe also this one; [...]
>
> https://lists.gnu.org/archive/html/groff/2017-02/
Hi Ingo,
> > It's good a Markdown is working for you, but it and its ilk need to
> > die out. Others did a better job, e.g.
> > http://www.methods.co.nz/asciidoc/
>
> That may or may not be adequate for books, i don't know, but keep in
> mind that AsciiDoc must never, under any circumstances, be
Hi,
Ralph Corderoy wrote on Mon, Mar 05, 2018 at 03:43:43PM +:
> It's good a Markdown is working for you, but it and its ilk need to die
> out. Others did a better job, e.g. http://www.methods.co.nz/asciidoc/
That may or may not be adequate for books, i don't know, but keep
in mind that Asc
Hi Larry,
> I’m typesetting entire books out of Markdown (specifically, >
> MultiMarkdown).
And that's the problem. Markdown is ill specified, poorly thought out,
and in consequence there are many dialects of Markdown. Thus
http://commonmark.org/ and https://xkcd.com/927/
It's good a Markdow
On Fri, Feb 16, 2018 at 12:24:38AM +0100, Bertrand Garrigues wrote:
> I now have full access to GNU's ftp, and I have generated a release
> 1.22.3.rc1. The target is to stabilize this version before generating
> an official 1.22.4. If you think there are some important fixes that
> must be passed
Hash iteration order may differ between runs, which makes builds
harder to reproduce. Sort hash keys in gropdf and afmtodit output
to avoid this.
* src/devices/gropdf/gropdf.pl: Sort hash keys.
* src/utils/afmtodit/afmtodit.pl: Iterate over sorted keys rather
than using `each'.
---
ChangeLog
The hdtbl examples don't need good randomness, as they're only
example output; removing the process ID from consideration allows
better integration with reproducible builds.
* contrib/hdtbl/examples/common.roff (random-s1): Remove process ID.
---
ChangeLog | 10 ++
