similar to: opus manpages

Dear authors of Vorbis, currently, the manpages that come with vorbistools 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

Hi I'm having a problem compiling opus-tools-0.1.7. Version opus-tools-0.1.6 seems to compile OK. I've tried with opus-1.0.3 and opus-1.1-beta. The errors are like this:- "undefined reference to `sqrtf'" etc. This OS is Peppermint Three, similar to Ubuntu 12.04. It uses:- gcc --version gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 Google says it's maybe something to do

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:

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 --------------

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

Hi, Seems like it's not linking with libm. I suspect it has to do with linking statically with libopus.a (is that intended?). Maybe opus-tools relies on the fact that libopus is linked with libm and doesn't explicitly add it? Greg? Jean-Marc On 09/24/2013 06:09 AM, bat guano wrote: > Hi > I'm having a problem compiling opus-tools-0.1.7. > Version opus-tools-0.1.6 seems to

This is the config line used:- PKG_CONFIG_PATH=3D"$HOME/builds/lib/pkgconfig" LDFLAGS=3D"-L$HOME/builds/li= b" CFLAGS=3D"-I$HOME/builds/include" ./configure --prefix=3D$HOME/builds --= host=3Di686-w64-mingw32 --disable-stack-protector @xubuntu:~/builds/bin$ wine ./opusenc -V opusenc opus-tools 0.1.5 (using libopus 1.0.1) Copyright (C) 2008-2012 Xiph.Org Foundation

opusdec -V opusdec opus-tools f2a2e88 (using libopus unknown) I've got an opus file encoded from a .wav off a cd, 44100Hz: opusinfo 2-24-Overture_in_C_\(In_Memoriam\).opus Processing file "2-24-Overture_in_C_(In_Memoriam).opus"... New logical stream (#1, serial: 38134f1f): type opus Encoded with libopus unknown User comments section follows... ENCODER=opusenc from opus-tools

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

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 >

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

Hi! I'm using the opus-tools package from the current Debian (it says it is 0.1.2). The output of opusinfo is strange: $ opusinfo demo01.opus Processing file "demo01.opus"... New logical stream (#1, serial: 0000456a): type opus Encoded with libopus 1.0.1-rc3 User comments section follows... ENCODER=opusenc from opus-tools 0.1.5 Opus stream 1: Pre-skip: 356 Playback

Hello, I have problems with encoding FLAC-Files with embedded pictures. Currently i use opus-tools 0.1.7 with libopus 1.1-rc2. After encoding opusinfo shows WARNING: Unknown picture type in METADATA_BLOCK_PICTURE comment 12 (stream 1): 1768776039 WARNING: Invalid mime type length in METADATA_BLOCK_PICTURE comment 12 (stream 1): 1697607790 bytes when 5562 are available When i play the files with

Hi Team, I'm looking to "upgrade" my sites ssh installation from the original. I have built openssh-2.3.0p1 and it looks good. I am puzzled as to why there are so many source distributions? However, that is not why am writing - the man pages provided do not format with either Solaris 'nroff -man' or 'groff -man'. What am I missing here? Thanks for your help. Scott

Hi Some Linux programs are 'static'. For example, these FFmpegs here ---> http://ffmpeg.gusari.org/static/ If we compile with Linux opusdec & opusenc & opusinfo & opusrtp using only static libraries libogg.a & libflac.a & libopus.a Are the four opus-tools programs then genuinely 'static', so that they will work on *any* Linux OS? $ ./opusenc -V opusenc

Hi, I had found a Opus TODO list in https://wiki.xiph.org/index.php?title=OpusTodo&mobileaction=toggle_view_desktop . The item "Opus-tools" interest me. And here is my question about "Port opusdec to libopusfile/libopusurl": 1. Does this function have achieved? On one hand, I think not literally. On the other hand, after briefly reviewing opusdec.c of opus-tools, I found

Since the opusenc and opusinfo changes were independent I split them up and landed the opusinfo changes (with updated mapping family numbers). - Mark On Thu, Sep 6, 2018 at 4:22 AM, Mark Harris <mark.hsj at gmail.com> wrote: > Hi Drew, > > Sorry for the delay. > > FYI the patch that you attached is not your latest version. This > thread that you replied to is an older

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 > > >

I compiled the latest (git master) of opus, libopusenc, opusfile and opus-tools: $ opusenc --version opusenc opus-tools 0.2-8-g4976421 (using libopus 1.3.1-4-gad8fe90d) I tried to encode a 3rd order Ambisonics wav file with the standard Ambix (ACN-SN3D) format; opusinfo is reporting : Streams: 16, Coupled: 0     Channel Mapping Family: 255 Map: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14,