> >I'd always thought that OK - yes - that is what it does. I suppose it
> >might be a slight improvement if it put out a verse range - but it's
> >never been an issue ass far as I am concerned.
>
> I disagree. The BibleCS and Bibletime version of presenting things could
> create serious problems
Hi there .
Greg Hellings wrote:
This might be a bit naive on my part, but is there a mechanism in the
Sword library that will tell the front-end that the presented text
covers multiple verses?
I'm fairly sure there isn't. I handled it by doing a strcmp() between
the previous verse and
Greg Hellings wrote:
This might be a bit naive on my part, but is there a mechanism in the
Sword library that will tell the front-end that the presented text
covers multiple verses? If I set a VerseKey to Genesis 1:2 is there a
way to retrieve where that entry begins and ends? For example, i
This might be a bit naive on my part, but is there a mechanism in the Sword library that will tell the front-end that the presented text covers multiple verses? If I set a VerseKey to Genesis 1:2 is there a way to retrieve where that entry begins and ends? For example, if the OSIS entry spans fro
I have entered an issue into Jira against BibleCS. Here is the text I
entered:
When two or more verses are marked in OSIS with a single verse tag, such
as ... the rendering of
the text by any client should indicate both 1 and 2. Of course part of
the problem is that osis2mod strips the verse
>
>I'd always thought that OK - yes - that is what it does. I suppose it
>might be a slight improvement if it put out a verse range - but it's
>never been an issue ass far as I am concerned.
>
I disagree. The BibleCS and Bibletime version of presenting things could create
serious problems when de
Hi there ..
Chris Little wrote:
I think (based on a copy of the TEV that I encoded and imported from
OSIS) that BibleCS functions like BibleTime. It doesn't print multiple
instances of a verse, but it fails to make any note of the verse range
covered. It just prints the verse number o
Barry Drake wrote:
Hi there .
[EMAIL PROTECTED] wrote:
Or rather gnomesword will make verses appear twic, while Bibletime
will not show that there are two verses linked... Not sure what the
Windows programme does here.
BibleCS does handle linked verses in the correct way.
I thin
Hi there .
[EMAIL PROTECTED] wrote:
Or rather gnomesword will make verses appear twic, while Bibletime will not show that there are two verses linked... Not sure what the Windows programme does here.
BibleCS does handle linked verses in the correct way.
God bless,
Barry
-- From Barr
[EMAIL PROTECTED] wrote:
Or rather gnomesword will make verses appear twic, while Bibletime will not show that there are two verses linked... Not sure what the Windows programme does here.
I suppose this is then something which needs to be dealt with at the
application level.
This is correct
Chris gave the proper way. If a front-end does not handle it properly it
is a bug in the front-end.
When this builds the index for the Sword module, then the two verses
will have the same start and length.
When a front-end for the Sword API gets a chapter, it will generally get
all the verses
Yes, like I said, I have contacted them. The fact that other parties
have permission to distribute the text, while showing good promise that
they may extend the same permission to us, does not mean that we may
distribute the text ourselves.
--Chris
[EMAIL PROTECTED] wrote:
These contact deta
Or rather gnomesword will make verses appear twic, while Bibletime will not
show that there are two verses linked... Not sure what the Windows programme
does here.
I suppose this is then something which needs to be dealt with at the
application level.
I have done this now for all "missing" ve
> The verses are actually combined, so you'd need something like:
>
> Ãbrahim oðlu, Davut oðlu Ãsa
> Mesih'in soyuyla ilgili kayýt þöyledir: Ãbrahim, Ãshak'ýn babasýydý.
> Ãshak, Yakub'un babasý; Yakup da Yahuda ve onun kardeþlerinin
> babasýydý.
I have tried this - the result i
These contact details are accurate:
The Translation Trust
PO Box 1017
Lessingham
NORWICH NR12 0WA
UNITED KINGDOM
Tel. +44 (0)1692 584900
Email [EMAIL PROTECTED]
National Patient Safety Agency - supporting Doctors.net.u
According to ccim (http://www.ccim.org/bible/dcb.html) the module belongs to
The Translation Trust
107 Stanstead Road London
SE23 1HH
United Kingdom.
Tel: 44 181 699 0967
Fax: 44 181 291 6764
[EMAIL PROTECTED]
http://www.translation-trust.org/html/home.html
These contact details appear to be ve
The verses are actually combined, so you'd need something like:
Ýbrahim oðlu, Davut oðlu Ýsa
Mesih'in soyuyla ilgili kayýt þöyledir: Ýbrahim, Ýshak'ýn babasýydý.
Ýshak, Yakub'un babasý; Yakup da Yahuda ve onun kardeþlerinin
babasýydý.
It looks like OLB consistently placed these combined verses i
The Turkish NT actually had some more significant problems than that, so
I have removed it from the site.
The primary problem was that it was copyrighted, so I have emailed the
copyright holders to get permission for us to distribute it.
The second problem was that it had the OLB as its sourc
>OK, so I don't know Turkish. I don't pretend to know Turkish. I hope someday
>to know it, but I do know a little about OSIS.
>
>The problem just seems to be that the text for the "misplaced" verses is
>placed within the following reference. As for correcting those mistakes, if
>you happen to
OK, so I don't know Turkish. I don't pretend to know
Turkish. I hope someday to know it, but I do know a little about
OSIS.
The problem just seems to be that the text for the "misplaced" verses
is placed within the following reference. As for correcting those
mistakes, if you happen to know Tur
Addendum:
The following link should give access to both files - the OSIS file and the new
conf file
http://www.doctors.net.uk/DocStore/DSView/Album.aspx?folderid=36645
Thanks
National Patient Safety Agency - supporting D
The Turkish NT currently on crosswire has two significant problems
1) three characters are wrongly encoded - the capital I with dot appears as a
capital Y with dot, the small I without dot appears as a small y with dot and
the "yumusak g" a g with a circumflex appears as some runic kind of sign
22 matches
Mail list logo
