On Thursday, January 30, 2003, at 06:45 AM, Daniel Glassey wrote:
Unfortunately (as far as I understand it) the way that software and
bible translations works is that even if you have bought the text for
one software program that gives you no rights at all to use it on any
others. At the mome
(presumably) would only enhance the value of the NIV text (which you are NOT
distributing), and (presumably) no money is involved, I think it is
comfortably within the bounds of fair use.
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church
"I would rather feel c
e else's work in the preparation of
my own - I just can't duplicate their work in my own.
On the other hand, if he wanted to take the NIV text and adapt it to produce
something like the New International Readers Version, that would violate the
copyright.
Patrick
--
Patrick Narkinsky - Ap
ld preserve a one-file download with a simple, XML-based format
(OSIS)
What you would do would be, the first time the module was opened, go through
and create the index. On modern hardware, this need not take a terribly long
time. This could be done in a background thread fairly easily.
Patrick
--
relevant.
So far as I know, there is no translation with a red letter edition
available which does not also offer a black-letter edition. What's the
issue here?
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church
"I would rather feel contrition than know how to defin
about any language you care to name. It is in
the public domain.
http://www.hwaci.com/sw/sqlite/
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church
"I would rather feel contrition than know how to define it."
- Thomas a Kempis
___
s a
surprising number of things to recommend it. It also gets the translation of
the Hebrew and Greek words for word/land right by often translating them as
"land".)
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church
"I would rather feel contritio
the NASB. Most literal? I think not.)
So far as I know, the only major English translation to translate YHWH
literally is the New Jerusalem (and, I suppose, the Jerusalem Bible as
well.)
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church
"I would rather f
Manuscripts read "the
Lord", "the lord", and THE LORD depending on which God is meant. NIV: Good
enough for Jesus, good enough for me.
*boik*
(The point being that often what is in translations has little to do with
what's in the original.)
Patrick
--
Patrick Narkinsky
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
;m rapidly moving "programming perl" to
the top shelf and keeping ruby in a nutshell in front of me.
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church
"Fairy tales are more than true: not because they tell us that dragons
exist, but beca
.
Patrick
Thus spake "Chris Little"> :
> On Wed, 8 Jan 2003, Patrick Narkinsky wrote:
>
>> Thus spake "Chris Little"> :
>>
>>> As a side note, Sword uses only .vss (not .bks or .chs) files and is
>>> limited to KJV versification.
Thus spake "Chris Little"> :
> As a side note, Sword uses only .vss (not .bks or .chs) files and is
> limited to KJV versification.
So, does this mean that some of the verses not included in modern
translations must be there? (e.g. Acts 8.38 if memory serves.)
Patrick
-
s, but databases
containing public domain works.
(All this silliness is a perfect example of why copyright law needs to be
completely revamped. Intellectual "property" is a ridiculous concept.)
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church
"Fairy tales a
lary tools. In
particular, I'm hoping to develop a very simplified greek<->english lexicon
which might be of some use in the Sword project.
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church
"Fairy tales are more than true: not because they tell us that drago
f the
verse numbering by one in the whole remainder of the chapter.
Just thought someone would like to know.
Patrick
--
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 d
wns, then put them in the same place on your map, but just
having a modern map is not enough.
Patrick
--
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
I thought about looking at doing an atlas some time
ago. At the time, I was not able to find any high-quality, freely available
maps to supply the data. Not to say that there are none - but I would check
for the data before I wrote the software.
Patrick
--
Patrick Narkinsky - Apprentice Pa
uestion from different sources different) was in the most ancient manuscripts
> proper names capitalized?
There were no iota subscripts, and all letters were capitalized. I'm not
aware of any first century exceptions to that, but I'm not a paleographer,
so could be wrong.
Patrick
--
P
n't mess with it. I do feel an itch for a Mac OS X
version, so I scratch it. I also don't feel an itch for a Mac OS 9 version
of sword - so I do all my development in cocoa. If you don't know how,
learn! That's what all the rest of us had to do.
Patrick
--
Patrick Narkinsky
and should
be understood with an holistic hermeneutic. It is a grave mistake to play
single proof-texts off against each other, since the truth of scripture is
not to be found in a single text out of context, but in all of the texts
taken together.
(Sorry for the off-topic discussion, but I felt
ve a right to an opinion.)
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church - 757-652-9540
"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
Thus spake "Keith Ralston"> :
(B
(B> $B&E&M(J $B&P&M&E&T&L&A&S&I(J $B&A&C&I&X(J is rendered with The Holy Ghost.
(B>Should the
(B> English article be tagged as belonging to PNEUMATI or hAGIO? I tagged
(B> PNEUMATI around the entire phrase. Then I tagged hAGIO inside that tag and
(B>
as with
proper names. We never say, in English, "The Jesus", but gk says hO IESOUS
all the time.) However, when the article is missing let context be your
guide. The absence of the article does not, by itself, prove anything other
than that the word might be indefinite.
Patrick
--
Patrick
Out of curiosity, with the greek tagging project, why is KJV being used
rather than e.g. RSV? Would've asked when it was first announced, but was
too busy to think about it.
Patrick
--
Patrick Narkinsky - Apprentice Pastor, Hope Community Church - 757-652-9540
"Fairy tales are more
tian Renz"> :
>> Wouldn't allowing multiple verse numbering schemes help this greatly?
>
> I think this is what Troy referred as "not a 'simple fix'". :)
> Everybody would love to have that, but it doesn't seem to be so easy
> to implement.
>
> Greetings,
> Christian
--
Patrick Narkinsky
757-596-3261
[EMAIL PROTECTED]
ested in possibly making the Deuterocanonical/Apocrypha
> books available as General Book modules. I don't know if/when Sword will
> support the Deuterocanonicals as Bible Modules, so I thought it might be
> easier to make them available as General Books. Would like feedback.
>
>
Now that I found the problem with UTF8...
In the greek, I'm not getting any accents. I looked around in diatheke, and
it appeared that the following call would turn on filters:
SWMgr *manager = new manager;
manager->setGlobalOption("Greek Accents","On");
However, I'm still not getting a
At this point, I am using rtf and an rtf filter to display verses. However,
greek text does not display correctly (take a look at the screenshot at
http://www.wingedpigs.com/patmos-102402.tiff for what I mean.) How is Greek
text encoded in sword? I have tried rendering with a couple of unicode
f
Thus spake "Chris Little"> :
> It's UTF-8 encoded Unicode. Everything should, at this point, be UTF-8
> encoded Unicode, except for some modules that are in Codepage 1252 and a
> couple of Czech modules that need to be fixed still.
Including Hebrew and Aramaic?
(Just making sure.)
I think my p
Thus spake "David Landrith"> :
>
> A group of friends and I are interested in creating an open source,
> full featured, and polished Bible reading software for MacOS X using
> SWORD. (We plan to call in "BibleChamp".
>
> I have perused the archives, and found a few scattered references to
> MacO
Thus spake "Don A. Elbourne Jr."> :
> If anyone else is interested in this, please jump in. The big hurdle I see
> is getting XUL to talk to Sword. I am guessing that XPCOM is the way to do
> this, but I'm not sure.
For what it's worth, I researched that question a bit and, yes, XPCOM is
what is
Don,
Could I bother you for a pre-print of the code? As I said, I'm interested
in doing a project along these lines and might be willing to help with parts
of it. (E.g. the Mozilla/XPCOM/Sword library integration.) The fact of the
matter is that I am horrible at starting projects but pretty go
Title: Re: [sword-devel] CCATS
Thus spake "John Baima"> :
GBS owns the copyright of the base text (which has changed since that CCAT text was done--I have a copy of the most recent edition), I was referring to the tagging.
For what it’s worth, unless I’m mistaken the text we’re discussing is b
34 matches
Mail list logo
