similar to: A new project using AsciiDoc: Network UPS Tools

I would like to learn AsciiDoc. Is there any good examples how to use AsciiDoc with R? I know that there is packages called ascii to do this, but it would be nice to see some examples how AsciiDoc works with R. Is there an AsciiDoc distribution for Max OS X? -Johannes

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

Arnaud, Thanks for removing the warning. I suspect that many users still using IE6 are doing so because of their IT department (rather than personal preference). IMHO, browser evangelism is slightly outside the scope of the NUT project :-) On Thu, Sep 3, 2009 at 8:31 AM, Arnaud Quette<aquette at alioth.debian.org> wrote: > Author: aquette > Date: Thu Sep 3 12:31:10 2009 > New

I need to install asciidoc on my build machine. There is a version for CentOS-5 available at dags rpm site. I have a repository configured for dag like so: [dag] name=Dag Wieers RPM Repository for Red Hat Enterprise Linux #Also see URL http://dag.wieers.com/home-made/apt/ baseurl=http://apt.sw.be/redhat/el$releasever/en/$basearch/dag gpgkey=http://dag.wieers.com/rpm/packages/RPM-GPG-KEY.dag.txt

FYI (mostly Charles and Arjen), a2x version has just been bumped to 8.6.3 in their trunk. So we will be able revert r2686 cheers, Arno 2010/11/12 Stuart Rackham > > > On 12/11/10 10:45, Arnaud Quette wrote: > >> Hi Stuart, >> >> 2010/11/10 Stuart Rackham >> >> The planned 28-Oct release date has slipped by, in the mean time I >> think all

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

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

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

The following changes since commit ddb10ce99c327888ade4d2ba3e4c50ad12aaa059: Matt Fleming (1): Delete 16-bit COMBOOT support are available in the git repository at: git://github.com/geneC/syslinux.git doc-elflink-for-mfleming Gene Cumm (3): txt/: Add new AsciiDoc formatted documentation Makefile: add txt/ NEWS: add txt/ Makefile | 2 +- NEWS

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

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

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

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

Hello, At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: > > On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: > > >> Don't worry about the battery physical properties for now - the > >> problem there is that we don't have enough information from the UPS > >> to do a proper calculation. With the V_interval[] settings, you can > >> tweak

On Jun 2, 2014, at 10:25 PM, Stefan Bruda wrote: > Hello, > > At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: >> >> On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> >>>> Don't worry about the battery physical properties for now - the >>>> problem there is that we don't have enough information from the UPS >>>> to do a

Hello list, I have explored https://github.com/networkupstools/nut repository and found that Riello UPS added into list of supported UPS. But current package for most distribution it's nut-2.6.5 which doesn't have Riello's models. Do we need to wait next upcoming nut release to get start with Riello? I tried to install from source but stuck: # git clone

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

> 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

On Oct 21, 2014, at 11:37 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Hummm, that got me past that barricade, but then it needed asciidoc, which > pulled in everything else it was fussing about. The everything else was > close to all of tex and latex, something north of 220 megs worth. Drive > space I have, but thats a heck of big hunk of dependency. You mean that