Wow... all of this sounds like a very promising and exciting move from the stringent KJV-only versification system currently in place to a much more lenient methodology for handling the texts. It seems to me that some of the problem could be to maintain the current system of Keys that are in place
First, on the topic of OSIS book abbreviations:
Almost everything you should ever need for Bibles is at
http://www.crosswire.org/~chrislit/osis/BibleBookNames.html
There are also the following, less up-to-date xml files, which add more
non-canonical materials. These were the the source materia
Troy,
> > So the solution in this case is not to allow for non-OSIS booknames like
> > JoshA and JoshB, but to encode the module correctly. That's what I am
> > planning for the upcoming (if we get permission) MT-LXX-parallel module.
> > If you get Josh 15, every verse will contain a table, the fi
I've been working on providing a VerseKey key interface for traversing
modules like the LXXM:
Is this really about v11n in Sword?
Hi Martin! Yes. This has been the way we've planned to implement v11n
in sword for the past year. You can see all the previous emails in the
archive an
Hi Troy.
> I've been working on providing a VerseKey key interface for traversing
> modules like the LXXM:
Is this really about v11n in Sword?
> First, I attempted to redo this module using OSIS book names for
> everything, and discovered that there just wasn't a nice book list we
> could
Troy,
My 2 cents.
I see this as a mapping of an external name (i.e. what the user know the
verse as) and an internal name (what the engine knows the verse as).
As you pointed out there are a whole host of issues with taking user
input and deciphering it into the internal name. Especially when y
Hey guys (especially frontend writers),
I've been working on providing a VerseKey key interface for traversing
modules like the LXXM:
http://crosswire.org/study/bookdisplay.jsp?mod=LXXM&gbsEntry=%2FJoshB%2F24%2F1
I'm having some difficulty fitting this into the exposed VerseKey
interface.
> -po: locale broken despite fixes. Very slow parsing, why? A native
> maintainer needs to fix this. Should not be included in the release in its
> current state.
Sorry, typo, the locale name is pl - Polish.
mg
___
sword-devel mailing list
[EMAIL PROTE
Sorry for the confusion I caused. I had 2 locales.d directories on my system,
and the wrong one was used in BibleTime. It works now.
I checked and fixed all locales. Problems remaining are:
-es: the known long booknames in Paul's letters
-id: the book of Judges is called "hakim-hakim", which will
Hi!
> Hey Troy,
>
> > 1) are you sure you have the latest CVS. We fixed Rev yesterday in
> > English.
>
> Yeah, works now. Thanks.
> The "1. Mose" style stuff still does not parse. Could you look at that
> please?
It works on my side. Make sure you installed the new de.conf :)
Joachim
--
<>< R
Hey Troy,
> 1) are you sure you have the latest CVS. We fixed Rev yesterday in
> English.
Yeah, works now. Thanks.
The "1. Mose" style stuff still does not parse. Could you look at that please?
> One day we'll rewrite that code and comment all the nuances, Lord
> willing, and make it easier to
Thanks for all the work Martin!
a few things:
1) are you sure you have the latest CVS. We fixed Rev yesterday in English.
2) I doubt the format of a Bible Book name like: TEXT 1. TEXT will parse
3) I think we could make this parse, and possibly your TEXT ROMNUM book
names, but it will take more
> thanks for the info. I think I got the point. =) However, German is not the
> only locale that has this kind of formatting. Others are cs, et, fi, hu,
> it, no, ru, uk. All of those would need to be updated, then.
All right. cs, de, et, fi, hu, it, no are now updated to include book names
witho
> PSS. Martin, yes, any other locale that ONLY includes '1. BOOK' syntax
> should also have '1 BOOK' syntax added-- if you'd like to help update
> those.
Alright. Willdo.
Martin
___
sword-devel mailing list
[EMAIL PROTECTED]
http://www.crosswire.org/m
The problem is resolved with adding the additional:
"1 BOOK..." entry for all the:
"1. BOOK..." entries.
I would think these would have been there anyway, since some users may
be lazy and not include the '.'. For English, we include all kinds of
variations, including, for example, "1 John", "1Jo
As Martin said, using '.' as an indicator of an ordinal value is
EXTREMELY common cross-linguistically.
On the other hand, I don't see why OSIS parsing needs to occur in the
same parser. OSIS references are completely controlled and don't
require the complexity of our general parser. The occu
Hey Troy,
thanks for the info. I think I got the point. =) However, German is not the
only locale that has this kind of formatting. Others are cs, et, fi, hu, it,
no, ru, uk. All of those would need to be updated, then.
Would it be enough to add book abbrevs like "1 Könige"
for the bookname "1
ECTED] On Behalf Of Troy A. Griffitts
Sent: Tuesday, June 17, 2003 1:18 PM
To: [EMAIL PROTECTED]
Subject: Re: [sword-devel] Verse parsing
Joachim and Martin,
I spent some time trying to track down the German verse parsing
error today and have some information for you.
To handle t
Joachim and Martin,
I spent some time trying to track down the German verse parsing error
today and have some information for you.
To handle the "1. Book" syntax, the parser decides if it has a book
name yet. It is does not, it strips the '.' and continues parsing.
This leaves the
Troy,
I added some tests. Have a look at verseparsing.sh to see the keys, because
missing lines are a bit confusing wirth runtest.sh.
getRangeText doesn't work and can't be put into verseparsing.sh.
Thank you!
Joachim
> Joachim,
> Could you add a bunch of test cases to tests/testsuite/vers
Joachim,
Could you add a bunch of test cases to tests/testsuite/verseparsing.sh
that represent failures, so I might be sure to catch all the problems.
Thanks for your testing!
-Troy.
Joachim Ansorg wrote:
Troy, thank you for working on parsing and on a testsuite.
I'm sorry to tell you that
Troy, thank you for working on parsing and on a testsuite.
I'm sorry to tell you that parsing is not yet working.
Try something like
./parsekey "1. Petrus 1:1" de
It doesn't output anything.
And VerseKey::getRangeText doesn't work. I have no idea how to fix this,
sorry.
Thanks you for
22 matches
Mail list logo
