similar to: [nut-commits] svn commit r1953 - branches/AsciiDoc/docs/website/scripts

2011/11/5 Arnaud Quette <aquette.dev at gmail.com> > Hi Greg, > > 2011/11/4 Charles Lepple <clepple at gmail.com> > >> On Thu, Nov 3, 2011 at 12:23 AM, Greg Trounson <gregt at maths.otago.ac.nz> >> wrote: >> > These Socomec units have RS-232 connectors and claim to support JBUS. >> > On the nut compatibility page I only see one Socomec

Hi Stuart, sorry for the lag in answering, I know that you're awaiting feedback for the final release... 2010/10/19 Stuart Rackham > Hi Arnaud > > I successfully compiled all the docs in svn:// > svn.debian.org/nut/branches/AsciiDoc using the current AsciiDoc trunk, and > yes, the chunked manual only has a single toc. But there was the added > problem of the article

Hi, I've been thinking of moving to using asciidoc for vignettes. As part of doing so, it would be nice to have an R package with all the pieces preconfigured in order to let others build the vignettes without a lot of configuration work. Conceptually, the following combination would work: * rJava package * rJython package * ascii package for Sweave processing of original asciidoc source

On Jul 28, 2009, at 7:53 AM, Arnaud Quette wrote: > some testing around the NUT Packager Guide to validate the general > approach of the new documentation. > The shell script is there to track the command line used to generate > the HTML output, and the generated HTML file to show the result. Hi Arnaud, would it be OK for me to merge the contents of the shell script into

> +[[commands]] > Commands sent to the UPS drivers > -------------------------------- If anyone has any suggestions on how to differentiate between the Unix domain socket message command, and the TCP-to-upsd commands in the Developers Guide, let me know. -- - Charles Lepple

On Aug 14, 2009, at 8:31 AM, Charles Lepple wrote: > Author: clepple-guest > Date: Fri Aug 14 12:31:25 2009 > New Revision: 1931 > > Log: > Warn when making 'html' without asciidoc tool Heh. Now I get a warning when running automake (with or without asciidoc). I'll fix that later.

Arnaud, one thing that bothers me a little bit about the new CSS webpage layout is that the NUT banner at the top obscures the text in the top portion of the page. This is not too much of an issue until you click on a link within a document, and the browser scrolls to that anchor. Most of the time, the destination of the link will be hidden behind the NUT banner. Can we make the banner scroll

On Sep 8, 2009, at 8:30 AM, Charles Lepple wrote: [...] > +EXTRA_DIST = tripplite_usb.8.txt \ > + ups.conf.5.txt \ > + upsc.8.txt > + The EXTRA_DIST thing is a hack. Right now, we are not including the generated HTML properly, because I haven't figured out the automake way to do this correctly. Specifically, we want to treat the .txt files as source, and distribute the

On Mon, Sep 14, 2009 at 4:49 PM, Arnaud Quette <aquette at alioth.debian.org> wrote: > Author: aquette > Date: Mon Sep 14 20:49:59 2009 > New Revision: 1986 > > Log: > draft index of manual pages > > Added: > branches/AsciiDoc/docs/man/index.txt Cool! One potential issue: /sw/bin/asciidoc --backend=xhtml11 \ --attribute localdate=`TZ=UTC date +%Y-%m-%d` \

I'm looking for a little bit of help with the man page conversion. So far, about a third of the man pages are converted, and I think it would make sense to have a second or third set of eyes compare the output to be sure that we are not losing any information in the conversion process. In the tarballs generated from the AsciiDoc branch on http://buildbot.ghz.cc/public/nut/ you will find the

I guess this is more of a question for Arnaud, but what's the plan for merging the AsciiDoc branch back into the trunk? At the moment, we have a little under half of the man pages converted, but of course there are a few changes between the branch point and the head of the trunk that need to be incorporated as well. Should we just manually keep track of the changed man pages, and only merge

Can someone double-check the UTF-8 in the rhino Authors section? Showed up fine locally on my machine, but my web browser insists that it is Latin-1. - Charles On Nov 30, 2009, at 10:30 PM, Charles Lepple <clepple-guest at alioth.debian.org > wrote: > Author: clepple-guest > Date: Tue Dec 1 03:30:32 2009 > New Revision: 2147 > > Log: > AsciiDoc: convert powerpanel

On Jul 13, 2010, at 6:59 PM, Arnaud Quette wrote: > Author: aquette > Date: Tue Jul 13 22:59:52 2010 > New Revision: 2472 > URL: http://trac.networkupstools.org/projects/nut/changeset/2472 [...] > Modified: branches/AsciiDoc/docs/Makefile.am > = > = > = > = > = > = > = > = > ====================================================================== > ---

FYI, I've fixed the below error in the log, directly on the server. The "pre-revprop-change" hook is not in place, so "svn propedit / propset" do not work. 2010/8/28 Arnaud Quette > Author: aquette > Date: Sat Aug 28 00:23:05 2010 > New Revision: 2504 > URL: http://trac.networkupstools.org/projects/nut/changeset/2504 > > Log: > Fix page titles for

On Nov 4, 2010, at 6:21 PM, Arjen de Korte wrote: > Author: adkorte-guest > Date: Thu Nov 4 22:21:51 2010 > New Revision: 2669 > URL: http://trac.networkupstools.org/projects/nut/changeset/2669 > > Log: > Add checking minimum required version for AsciiDoc tools I noticed that somewhere around this commit, the documentation stopped being built by default in BuildBot.

2010/11/4 Arjen de Korte > Author: adkorte-guest > Date: Thu Nov 4 22:40:51 2010 > New Revision: 2671 > URL: http://trac.networkupstools.org/projects/nut/changeset/2671 > > Log: > Exclude -I. and extra developer warning flags with Net-SNMP support enabled > (using them is the responsibility of the NUT developers) > > Modified: >

> The Buildbot has detected a new failure of openSUSE on Network UPS > Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/openSUSE/builds/1012 Arjen, I think this is a bug in older versions of asciidoc/a2x where it ignores --destination-dir and tries to write the intermediate XML file to the read-only source directory. Looks like

It looks like there was an issue with the AsciiDoc merge from the trunk: http://buildbot.networkupstools.org/private/nut/builders/Ubuntu-lucid-x86/builds/119/steps/compile/logs/stdio As mentioned in the email about windows_port, I would recommend testing the branch after a merge from the trunk. You can either run "make distcheck", or contact me (off-list) to set up a password so

Hello, I'm starting to think that converting the Syslinux documentation to asciidoc would be the best, and probably easiest, way to get some kind of consistency between the web docs and what is shipped. I don't think it would be all that hard to do (see http://www.methods.co.nz/asciidoc/). Anyone interested in trying to tackle this? -hpa

On Jun 23, 2017, at 10:28 PM, Manuel Wolfshant wrote: > > Unfortunately they do not include any man pages, I did not have time to find a workaround for the hard requirement of newer versions for the tools used by the build process to create the man pages. You have mentioned the man pages several times, and I am slightly confused. If I grab a tarball from