[sword-devel] Sword, PHP, and PostNuke
Patrick Narkinsky
sword-devel@crosswire.org
Fri, 10 Jan 2003 10:22:02 -0500
> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--B_3125038923_3400025
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Does anyone know off-hand if support for STEP format would accomplish these
goals?
For what it=B9s worth, Accordance tends to put notes in a separate module,
which can then be put in a pane side-by-side with the actual text. I find
that that works quite well (especially if the footnote indicators are left
in the original text so you know they are there.)
Patrick
Thus spake "Rev. Michael Paul Johnson"> :
> At 23:39 08-01-03 -0500, Patrick Narkinsky wrote:
>> I was wondering... I am a bit concerned by this lack (since I am not a b=
ig
>> fan of KJV and am a big fan of the apocrypha - at least for research). W=
ould
>> there be an interest in a new file format to overcome the numbering/nami=
ng
> limitations? I might be willing to put some time into it if there were.
>=20
> Yes. I would like to see a format that:
>=20
> 1. Directly supports any reasonable versification (i. e. M-Text/WEB, NA/U=
BS,
> NIV, KJV, REB, etc.) for both the OT/NT Canon and the DC/Apocrypha.
> 2. Supports verse bridges (i. e. two or more verses translated as a unit
> without a clear indication of where one stops and the other starts) --
> necessary for the Tok Pisin Bible and many others.
> 3. Supports proper poetry and prose formatting. (It amazes me how many pe=
ople
> mangle these and see no value in them!)
> 4. Is open and easy to convert existing texts to and from.
> 5. Supports partial Bible texts (i. e. for Bible translations in progress=
).
> 6. Supports interlinear texts.
> 7. Supports footnotes, cross-references, and commentary notes (both edita=
ble
> personal notes and read-only notes by others). (Commentary should be in a
> separate file.)
>=20
> Compression and even compactness are not essential. Speed of access is
> important. Indexing can help do that, but it should be done such that an =
index
> can be built on-the-fly if it doesn't exist.
>=20
>=20
>=20
> Rev. Michael Paul Johnson
> Servant of Jesus Christ
> President, Rainbow Missions, Inc.
> Senior Editor, World English Bible
> http://eBible.org/mpj/ mpj@eBible.org
> Phone: 011+675+737-4519
> SIL BOX 421
> UKARUMPA 444
> EASTERN HIGHLANDS PROVINCE
> PAPUA NEW GUINEA
>=20
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church
"Fairy tales are more than true: not because they tell us that dragons
exist, but because they tell us that dragons can be beaten." - Chesterton
--B_3125038923_3400025
Content-type: text/html; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: [sword-devel] Sword, PHP, and PostNuke</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana">Does anyone know off-hand if support for STEP format w=
ould accomplish these goals?<BR>
<BR>
For what it’s worth, Accordance tends to put notes in a separate modu=
le, which can then be put in a pane side-by-side with the actual text. I fin=
d that that works quite well (especially if the footnote indicators are left=
in the original text so you know they are there.)<BR>
<BR>
Patrick<BR>
<BR>
Thus spake "Rev. Michael Paul Johnson"> :<BR>
<BR>
</FONT><BLOCKQUOTE><FONT FACE=3D"Verdana">At 23:39 08-01-03 -0500, Patrick Na=
rkinsky wrote:<BR>
</FONT><BLOCKQUOTE><FONT FACE=3D"Verdana">I was wondering... I am a bit conce=
rned by this lack (since I am not a big<BR>
fan of KJV and am a big fan of the apocrypha - at least for research). Woul=
d<BR>
there be an interest in a new file format to overcome the numbering/naming<=
BR>
</FONT></BLOCKQUOTE><FONT FACE=3D"Verdana">limitations? I might be will=
ing to put some time into it if there were.<BR>
<BR>
Yes. I would like to see a format that:<BR>
<BR>
1. Directly supports any reasonable versification (i. e. M-Text/WEB, NA/UBS=
, NIV, KJV, REB, etc.) for both the OT/NT Canon and the DC/Apocrypha.<BR>
2. Supports verse bridges (i. e. two or more verses translated as a unit wi=
thout a clear indication of where one stops and the other starts) -- necessa=
ry for the Tok Pisin Bible and many others.<BR>
3. Supports proper poetry and prose formatting. (It amazes me how many peop=
le mangle these and see no value in them!)<BR>
4. Is open and easy to convert existing texts to and from.<BR>
5. Supports partial Bible texts (i. e. for Bible translations in progress).=
<BR>
6. Supports interlinear texts.<BR>
7. Supports footnotes, cross-references, and commentary notes (both editabl=
e personal notes and read-only notes by others). (Commentary should be in a =
separate file.)<BR>
<BR>
Compression and even compactness are not essential. Speed of access is impo=
rtant. Indexing can help do that, but it should be done such that an index c=
an be built on-the-fly if it doesn't exist.<BR>
<BR>
<BR>
<BR>
Rev. Michael Paul Johnson<BR>
Servant of Jesus Christ<BR>
President, Rainbow Missions, Inc.<BR>
Senior Editor, World English Bible<BR>
http://eBible.org/mpj/ mpj@eBible.org<BR>
Phone: 011+675+737-4519<BR>
SIL BOX 421<BR>
UKARUMPA 444<BR>
EASTERN HIGHLANDS PROVINCE<BR>
PAPUA NEW GUINEA<BR>
<BR>
</FONT></BLOCKQUOTE><FONT FACE=3D"Verdana"><BR>
<BR>
--<BR>
Patrick Narkinsky - Apprentice Pastor, Hope Community Church<BR>
<BR>
"Fairy tales are more than true: not because they tell us that dragons=
exist, but because they tell us that dragons can be beaten." - Chester=
ton<BR>
</FONT>
</BODY>
</HTML>
--B_3125038923_3400025--