Date: Sun, 14 Sep 2014 09:29:46 -0700 (PDT)
From: TR NS <transfire@gmail.com>
To: lojban@googlegroups.com
Message-Id: <b049b5f7-637f-4e0e-9b18-36fccd233d7d@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_1726_724695786.1410712186488"
X-Spam_score: -1.9
X-Spam_score_int: -18
X-Spam_bar: -

------=_Part_1726_724695786.1410712186488
Content-Type: text/plain; charset=UTF-8


On Sunday, September 14, 2014 9:30:18 AM UTC-4, Robin Powell wrote:
>
>
> 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. 
>
>
Here's a preliminary example of chapter 
1: https://github.com/trans/cll/blob/markdown/source/01.md (better to look 
at it in raw format in you favorite text editor though)

A couple of points about it:

1. The changes that would have to be accounted for when the markdown is 
transformed to XHTML are: `<p>` instead of `<para>`, `<q>` instead of 
`<quote>`, `<li>` instead of `<listitem>` and a few others along the same 
lines. Basically XHTML instead of Docbook XML in the places where markdown 
is used. (All other XML is untouched and passed thru.) I still don't fully 
know what you have planned for the Ruby code, but these could be 
transformed at that level, or by adding some additional XSL transforms. Not 
a big deal either way. Probably the most difficult adjustment will be 
converting `<h*>` to `<section>` markup, but even that isn't terribly 
difficult.

2. indexterm could be marked-up better. I already wrote a plugin for pandoc 
to do it. But a Ruby solution would do just as well. This would make the 
source document even cleaner.

3. In this particular chapter, the image captions section is a bit odd. I 
wonder how useful these linkends are. I also considered using a table, but 
wasn't sure what would be best. I just ended up making them separate `pre` 
sections. Personally I think it would be better if they were first page 
footnotes of their respective chapters.

So look it over and let me know what you think. It isn't particularly 
revolutionary to use markdown as a first stage format, but it does make a 
big difference to the readability (and hence edit-ability) of the source 
documents.

-- 
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_1726_724695786.1410712186488
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;"><br>That soun=
ds 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>Here's a preliminary example of chapte=
r 1:&nbsp;https://github.com/trans/cll/blob/markdown/source/01.md (better t=
o look at it in raw format in you favorite text editor though)</div><div><b=
r></div><div>A couple of points about it:</div><div><br></div><div>1. The c=
hanges that would have to be accounted for when the markdown is transformed=
 to XHTML are: `&lt;p&gt;` instead of `&lt;para&gt;`, `&lt;q&gt;` instead o=
f `&lt;quote&gt;`, `&lt;li&gt;` instead of `&lt;listitem&gt;` and a few oth=
ers along the same lines. Basically XHTML instead of Docbook XML in the pla=
ces where markdown is used. (All other XML is untouched and passed thru.) I=
 still don't fully know what you have planned for the Ruby code, but these =
could be transformed at that level, or by adding some additional XSL transf=
orms. Not a big deal either way. Probably the most difficult adjustment wil=
l be converting `&lt;h*&gt;` to `&lt;section&gt;` markup, but even that isn=
't terribly difficult.</div><div><br></div><div>2. indexterm could be marke=
d-up better. I already wrote a plugin for pandoc to do it. But a Ruby solut=
ion would do just as well. This would make the source document even cleaner=
.</div><div><br></div><div>3. In this particular chapter, the image caption=
s section is a bit odd. I wonder how useful these linkends are. I also cons=
idered using a table, but wasn't sure what would be best. I just ended up m=
aking them separate `pre` sections. Personally I think it would be better i=
f they were first page footnotes of their respective chapters.</div><div><b=
r></div><div>So look it over and let me know what you think. It isn't parti=
cularly revolutionary to use markdown as a first stage format, but it does =
make a big difference to the readability (and hence edit-ability) of the so=
urce documents.</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_1726_724695786.1410712186488--