[sword-devel] BibleCS name?
Chris Little
sword-devel@crosswire.org
Mon, 16 Jul 2001 15:08:19 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_003F_01C10E09.27978320
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
OK, I agree it should get a name change, immediately or soon. From
talking with Troy, it's clear to me that the Windows front end is not
synonymous with or even part of "The SWORD Project". What we need is a
name that people are going to understand and that is catchy. I think
BibleCS fails both those tests, especially when it doesn't currently act
as a Bible Contruction Set (I think that was what it stood for, right).
WinSword is simple, but kind of boring. Most of the names that are
synonyms for or types of swords would be over many people's heads and
don't have an obvious connection with the Bible. "The SWORD" is too
easily confused with "The SWORD Project". Scabbard is kind of good
because the software acts as a wrapper to the Sword library, but I've
got the same objections as for types of swords. HISword is cutesy and
relevent, but might be too much of a pun. Maybe "His Word"--or does
that ruin the pun entirely? And is that too similar to "The Word"
(OLB's new name that no one seems to accept). Also how about
"OpenBible" or "Open Bible"? I know Paul Gear's project has/had this
name, but that was specifically for Unix, so it could still use that
name. Besides, to my knowledge that project was kind of scrapped
(correct me if I'm wrong). "OpenBible" is simple and succint, and it
addresses two primary concerns, the openness of the software and the
fact that it is Bible software. Plus there are some good ad slogans we
could generate out of it like, "Open your Bible with OpenBible." :)
--Chris
------=_NextPart_000_003F_01C10E09.27978320
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2479.6" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D931404621-16072001>OK, I agree it should get a name =
change,=20
immediately or soon. From talking with Troy, it's clear to me that =
the=20
Windows front end is not synonymous with or even part of "The SWORD=20
Project". What we need is a name that people are going to =
understand and=20
that is catchy. I think BibleCS fails both those tests, especially =
when it=20
doesn't currently act as a Bible Contruction Set (I think that was what =
it stood=20
for, right).</SPAN></DIV>
<DIV><SPAN class=3D931404621-16072001><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D931404621-16072001>WinSword is simple, but kind of=20
boring. Most of the names that are synonyms for or types of swords =
would=20
be over many people's heads and don't have an obvious connection =
with the=20
Bible. "The SWORD" is too easily confused with "The SWORD=20
Project". Scabbard is kind of good because the software acts as a =
wrapper=20
to the Sword library, but I've got the same objections as for types of=20
swords. HISword is cutesy and relevent, but might be too much of a =
pun. Maybe "His Word"--or does that ruin the pun entirely? =
And is=20
that too similar to "The Word" (OLB's new name that no one seems to=20
accept). Also how about "OpenBible" or "Open Bible"? I know =
Paul=20
Gear's project has/had this name, but that was specifically for Unix, so =
it=20
could still use that name. Besides, to my knowledge that project =
was kind=20
of scrapped (correct me if I'm wrong). "OpenBible" is simple and =
succint,=20
and it addresses two primary concerns, the openness of the software and =
the fact=20
that it is Bible software. Plus there are some good ad slogans we =
could=20
generate out of it like, "Open your Bible with OpenBible." =
:)</SPAN></DIV>
<DIV><SPAN class=3D931404621-16072001><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D931404621-16072001>--Chris</SPAN></DIV></BODY></HTML>
------=_NextPart_000_003F_01C10E09.27978320--