similar to: manpages in mdoc(7)

Dear authors of Opus, currently, the manpages that come with opus-tools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the

Dear authors of NSD, currently, the manpages that come with NSD are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. See a version of nsd-checkzone.8 below as an example. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters:

ping On Jun 23 09:05:38, hans at stare.cz wrote: > Dear authors of vorbis-tools, > > the manpages are currently writen using the man(7) markup language. > Would there be any interest in having them rewritten to mdoc(7)? > > The mdoc(7) language allows for _semantic_ markup, expressing > things like "this is an optional argument", as opposed to the physical >

On Jan 01 00:05:09, jamie at catflap.org wrote: > Jan Stary via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > > > On Dec 31 11:43:56, paul at nohats.ca wrote: > > > Why not go to xml and use xml2man / pandoc ? > > > > Because it is a terrible manpage format > > and the toolchain produces broken crap. > > I have no specific knowledge on

Jan Stary <hans at stare.cz> wrote: > On Jan 01 00:05:09, jamie at catflap.org wrote: > > Jan Stary via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > > > > > On Dec 31 11:43:56, paul at nohats.ca wrote: > > > > Why not go to xml and use xml2man / pandoc ? > > > > > > Because it is a terrible manpage format > > >

Hi, On systems that have mandoc installed but are missing an nroff binary, the configure script will fall back to pre-formatted manual pages despite the fact that mandoc could be used. The proposed patch adds mandoc as a valid formatter to configure.ac. As mandoc supports the -mdoc flag, it can simply be added to the list of nroff-like binaries. Wolfgang -------------- next part --------------

http://bugzilla.mindrot.org/show_bug.cgi?id=550 Summary: Problems with .Ql in mdoc Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Documentation AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: cjwatson at

The attached patch (relative to the current CVS snapshot) uses a perl script to convert the OpenSSH manpages from the BSD -mdoc format to the -man format used by other systems. This allows the unformatted manpages to be installed normally, rather than defaulting to preformatted pages. I'd like to see this patch integrated into the portable version of OpenSSH. Please let me know what you

On 2016-09-28 00:10, Ingo Schwarze wrote: > The patch also inserts a few needless .PP before .SH, but that does > no harm. mdoc2man.awk is a terrible hack and not a proper parser > in the first place, so we shouldn't expect beauty in its output. > If the output is correct and portable, that's good enough. At some > point, we should replace mdoc2man.awk with mandoc -Tman

Hello Some time ago I posted a lil' patch to this list which adds milliseconds display of playlength to ogginfo. Some folks replied that it's plausible and this patch will be merged to the next version. Vorbistools-1.0.1 got out and the patch is not in it. Why? Anyway, here's this patch for vorbistools-1.0.1. I hope this time you will include it, because milliseconds support is

Guus The mdoc warnings (on FreeBSD 8) are getting a little bit annoying at times: anywi at lcrproxy:/usr/ports/security/tinc/work/tinc-1.0.19/doc % man tinc.conf 2>&1 | head -5 mdoc warning: Empty input line #6 mdoc warning: Empty input line #10 mdoc warning: Empty input line #15 mdoc warning: Empty input line #22 mdoc warning: Empty input line #30 There are hundreds. Ctrl-L refreshes

Greetings in Christ our Saviour. I am having an enormous amount of difficulties trying to do something that should be quite easy. Obviously, I am missing something. I have read everything I can find on this, and have tried everything I can think of and more... I am trying to mount a Win98 drive on my Redhat 7.0 box. The mounting is no problem. However, when I log into my user account and try

Version info: OpenSSH_7.3p1, OpenSSL 1.0.2i 22 Sep 2016, Arch linux The ssh-agent.1 man page seems to have an indentation oddity, at least, as formatted with recent Arch linux manpage toolset. Here's what appears in the formatted output just after the description of the the "-t" option: ---------- Begin formatted output ------------------------------------- -t life

Estimados compañeros me tiene loco un problema de codificación que no logro resolver. Importo un fichero cuyo nombre tiene acento. Pongamos por ejemplo "Adrián.doc". Escribo el siguiente comando: mdoc<-list.files(path = dest,pattern = "*.doc", full.names = TRUE) Entonces mdoc, además del path, se me presenta como: "Adria´n.doc" Aunque le quite la tilde con:

With this patch, ogginfo will display bitrate information (upper/lower/nominal/average bitrate). It is patched against today's CVS code (main branch). I am also working on true VBR support in oggenc (the user can specify the minimum & maximum bitrate) and will send a patch when it's done. <HR NOSHADE> <UL> <LI>application/x-gzip attachment: ogginfo-diff.gz

Hi, I'm using ogginfo a lot to get the comments section on the terminal. However ogginfo always verifies (reads) the whole stream to print some more information. I'd like to see an additional option that does just print the comments efficiently. For a player connected via USB 1, that would clearly make a difference. (I have a Perl script that renames files based on the comments, and I

Good day all, I have a small collection of ogg files (5Gb) on my fileserver which I have mounted over NFS. My problem is that ogginfo takes too long to be used practically in programs like gqmpeg due to naturally wanting to do a full file check on each ogg file for valadity etc. My question/request is; is there a way to make ogginfo only look at the headers (ie, first K or two of data) and

Hello I need to extract playback length from ogg vorbis file, with 1/100th second precision. The ogginfo program tells the playback length to 1 second precision. Why not to change ogginfo? I suppose many automatic tools need precision higher than 1 second. If you don't want to modify this ogginfo behaviour, please tell me how to get this playback length with high precision. Thank you very

>>I realize that I may have unintentionally been misleading you by leaving some information out. That error report from ogginfo keeps going, repeating the same 3 errors (as above) over and over again. It ends after a stream_truncated=true, not giving a final header_integrity=fail. (Perhaps because there's not another packet?) Then it reports a total playtime of 0. > >Yes,

Some detailed feedback that looks useful. ----- Forwarded message from Michael Semon <wayfarer42@postmaster.co.uk> ----- Delivery-Date: Tue Jul 16 05:29:37 2002 X-Mailer: MIME-tools 5.41 (Entity 5.404) From: "Michael Semon" <wayfarer42@postmaster.co.uk> Subject: CVS: ogg123 rocks! vcut no so much so... To: feedback@vorbis.com Hi! Being impatient for RC4, I downloaded