Date: Sun, 14 Sep 2014 08:03:09 -0700 (PDT)
From: TR NS <transfire@gmail.com>
To: lojban@googlegroups.com
Message-Id: <da900060-a551-4505-870d-c6b45dd9b3fd@googlegroups.com>
In-Reply-To: <20140914133015.GJ30324@stodi.digitalkingdom.org>
References: <20140809202309.GA23392@stodi.digitalkingdom.org>
 <ef0e6e19-e69c-4fda-aaf0-92f61190a1b5@googlegroups.com>
 <20140910173804.GP30324@stodi.digitalkingdom.org>
 <c247a67a-9722-4782-a921-83496caf617e@googlegroups.com>
 <20140910233108.GD30324@stodi.digitalkingdom.org>
 <20140911005841.GF30324@stodi.digitalkingdom.org>
 <20140911023800.GG30324@stodi.digitalkingdom.org>
 <d63f2561-3cfb-401b-a21c-4ac8210699f7@googlegroups.com>
 <20140912181104.GH30324@stodi.digitalkingdom.org>
 <984b6369-540d-4559-8703-640774f5666c@googlegroups.com>
 <20140914133015.GJ30324@stodi.digitalkingdom.org>
Subject: Re: [lojban] Re: The CLL project, technical directions
MIME-Version: 1.0
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
Content-Type: multipart/alternative; 
	boundary="----=_Part_1846_552728280.1410706989792"
X-Spam_score: -1.9
X-Spam_score_int: -18
X-Spam_bar: -

------=_Part_1846_552728280.1410706989792
Content-Type: text/plain; charset=UTF-8


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.


-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

------=_Part_1846_552728280.1410706989792
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br>On Sunday, September 14, 2014 9:30:18 AM UTC-4, Ro=
bin Powell wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;margi=
n-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">On Fri, Sep 1=
2, 2014 at 11:27:35AM -0700, TR NS wrote:
<br>&gt;=20
<br>&gt;=20
<br>&gt; On Friday, September 12, 2014 2:11:07 PM UTC-4, Robin Powell wrote=
:
<br>&gt; &gt;
<br>&gt; &gt; On Wed, Sep 10, 2014 at 11:04:49PM -0700, TR NS wrote:=20
<br>&gt; &gt; &gt;=20
<br>&gt; &gt; &gt;=20
<br>&gt; &gt; &gt; On the other hand, I have worked with the git repo enoug=
h now
<br>&gt; &gt; &gt; to think that perhaps an approach that combines (enhance=
d)
<br>&gt; &gt; &gt; markdown as a source format with your Ruby transforms wo=
uld be
<br>&gt; &gt; &gt; a good stop-gap solution (at least until these HTML/CSS =
print
<br>&gt; &gt; &gt; solutions mature). The markdown can take care of basic s=
tyling
<br>&gt; &gt; &gt; needs in a format that is much easier to work with, whil=
e the
<br>&gt; &gt; &gt; xhtml it produces along with pass-thru xml can be handle=
d via
<br>&gt; &gt; &gt; the Ruby code.=20
<br>&gt; &gt;
<br>&gt; &gt; For that, though, someone (and it won't be me) has to convert
<br>&gt; &gt; the source to markdown.=20
<br>&gt; &gt;
<br>&gt; &gt;
<br>&gt; I'd be happy to do that. I can just work on it a bit each week.
<br>&gt; Estimate it will take a week or two to do each chapter.
<br>
<br>That sounds like you're talking about doing it by hand?
<br>
<br>If so, I think you're badly underestimating how cross-reference
<br>heavy (i.e. index and glossary entries) this book is; that's a
<br>staggering amount of work.
<br>
<br>More importantly, the problem with by-hand changes is that it's hard
<br>to demonstrate that the *content* hasn't changed. &nbsp;I would
<br>definitely consider the burden of proof that the text is all the
<br>same to be on you in that case.
<br><br></blockquote><div><br></div><div>Only partially. Things like `&lt;q=
&gt;&lt;/q&gt;` can be changed to `"` using search and replace. I've alread=
y done this for the first two chapters so I know what it will basically tak=
e, and I left myself some breathing room. If I worked on it like a full-tim=
e job I probably could knock out a chapter every two days.</div><div><br></=
div><div>I don't know what *content* would change. Sure there could be an a=
ccidental typos or something but that's the nature of any work. I hope ther=
e 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.</div><div><br></div=
><div><br></div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;lojban&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:lojban+unsubscribe@googlegroups.com">lojban+unsub=
scribe@googlegroups.com</a>.<br />
To post to this group, send email to <a href=3D"mailto:lojban@googlegroups.=
com">lojban@googlegroups.com</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/group/lojban">http:=
//groups.google.com/group/lojban</a>.<br />
For more options, visit <a href=3D"https://groups.google.com/d/optout">http=
s://groups.google.com/d/optout</a>.<br />

------=_Part_1846_552728280.1410706989792--