On Sunday, September 14, 2014 9:30:18 AM UTC-4, Robin Powell wrote:
On Fri, Sep 12, 2014 at 11:27:35AM -0700, TR NS wrote:
>
>
> On Friday, September 12, 2014 2:11:07 PM UTC-4, Robin Powell wrote:
> >
> > On Wed, Sep 10, 2014 at 11:04:49PM -0700, TR NS wrote:
> > >
> > >
> > > On the other hand, I have worked with the git repo enough now
> > > to think that perhaps an approach that combines (enhanced)
> > > markdown as a source format with your Ruby transforms would be
> > > a good stop-gap solution (at least until these HTML/CSS print
> > > solutions mature). The markdown can take care of basic styling
> > > needs in a format that is much easier to work with, while the
> > > xhtml it produces along with pass-thru xml can be handled via
> > > the Ruby code.
> >
> > For that, though, someone (and it won't be me) has to convert
> > the source to markdown.
> >
> >
> I'd be happy to do that. I can just work on it a bit each week.
> Estimate it will take a week or two to do each chapter.
That sounds like you're talking about doing it by hand?
If so, I think you're badly underestimating how cross-reference
heavy (i.e. index and glossary entries) this book is; that's a
staggering amount of work.
More importantly, the problem with by-hand changes is that it's hard
to demonstrate that the *content* hasn't changed. I would
definitely consider the burden of proof that the text is all the
same to be on you in that case.
Only partially. Things like `<q></q>` can be changed to `"` using search and replace. I've already done this for the first two chapters so I know what it will basically take, and I left myself some breathing room. If I worked on it like a full-time job I probably could knock out a chapter every two days.
I don't know what *content* would change. Sure there could be an accidental typos or something but that's the nature of any work. I hope there are plans for through proof reading in any case. Also diff's can help if you'd like to double check my work. That's a good idea.