Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (athena.apache.org: domain of david.medinets@gmail.com
 designates 74.125.82.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAL5zq9aK=0F_qN2ODw8Rjc6dwrvJBeVQ2W=D4yA3BX3OPaSbcQ@mail.gmail.com>
References: 
 <CAL5zq9aK=0F_qN2ODw8Rjc6dwrvJBeVQ2W=D4yA3BX3OPaSbcQ@mail.gmail.com>
Date: Wed, 24 Apr 2013 18:35:52 -0400
Message-ID: 
 <CAOiJXP4Yvuz6eEuNPRBcZjobgc-0phzWqCKu+GhUh_T6yhOmiQ@mail.gmail.com>
Subject: Re: Shell documentation appendix
From: David Medinets <david.medinets@gmail.com>
To: accumulo-dev <dev@accumulo.apache.org>
Content-Type: multipart/alternative; boundary=047d7b5d3e5ea774fe04db22ec7e

--047d7b5d3e5ea774fe04db22ec7e
Content-Type: text/plain; charset=ISO-8859-1

We've been talking about changing the documentation for some time now.
Should we take a poll and commit to the change? Once a decision is made,
the work to convert from latex to the next thing can be parceled out.
However, perhaps we should be taking a whole different approach and
switching to a Semantic Wiki. Is the ability to print chapters a
requirement?


On Wed, Apr 24, 2013 at 6:04 PM, Christopher <ctubbsii@apache.org> wrote:

> I noticed that there's a script that grabs shell output and builds an
> appendix for the user manual PDF. However, that doesn't appear to be
> automated as part of the documentation build profile.
>
> So, the questions are:
> 1) Do we need this?
> 2) Does it need to be run manually?
>
> Also, I guess there's some extra steps to convert the LaTeX source for
> the PDF into HTML... regarding that:
>
> 1) are those steps documented anywhere?
> 2) can we automate that procedure?
> 3) do we even need it?
>
> Personally, I think it'd be better to just do the PDF for now, until
> we get Doxia or something similar working.
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>

--047d7b5d3e5ea774fe04db22ec7e--