I need all the Greek ANF texts I can get my hands on. If you know of any text that I do not have, please send me an e-mail with the text or a link to its location.
The apparatus is not in a very machine-readable format. It will take a while to parse and re-package in a way that makes sense. Sigh...
Interlinear manuscript view is now working. A la Swanson! :) Except, the apparatus needs to be better parsed.
A good Koine treebank would be nice to have. Does one exist? I sincerely doubt it. I will need to make my own training set, that could take a while.
What is it? Why is it? Well, since I am not overly burdened by large quantities of cash, I am not exactly able
to spend a large amount of money, or, in fact, any amount, on the fancy bible programs that are available. In addition, I don't think that some of their features are as
flexible as I would like. They also bundle much material that I frankly care nothing about. With all this in mind I decided to write my own. I also decided that, if I was to go
to that much trouble, I would share freely with anyone so consequently I developed it as a web-based application. That means that it will work in anyone's browser without any
further ado.
What started out as something effective but small, it has now grown to a fairly extensive application which has so far prevented my from putting at least a preliminary version out for public scrutiny. Vacation and work has also hampered my efforts. As soon as a few more features come together, I will upload it. The main problem is that I don't wish to put something up that has already been done by someone else. Although it has already pregressed well beyond the level of anything currently out there (i.e. freely available on the web) I do not feel that it is far enough ahead at this time. For a list of feature, planned as well as implemented, see below. Here is a sample screenshot and another.
If this project sounds interesting to you, check back here for occasional updates. And by the way, the link in the left menu for this project does not currently work.
If you have an interest in textual criticism and computer programming you might like my blog. I am always looking for topics, so let me know if there is any issue you think I should address.
Nothing to do with the bible but, hey, not everything here needs to have to do with that all of the time. So here is some pages I did on Vikings when I last went home to Denmark.
The vikingship museum was extremely cool, I could have spent all day there but I don't think that my kids would have stood for it. Literally...
This page also addresses the Eusebian Canon. It shows examples of how the various divisions where with an easy-to-follow explanation with illustrations from Codex A and minuscule 669.
Eventually, I will have more information on that page but that project has taken a temporary backseat due to bigger and better things being in the works.
If there is any particular feature you would like to see that isn't on the list below, please let me know. It might be possible, maybe it's already in there but I forgot to list it, maybe I have all the code parts but just need to piece it together differently. Once the program is on-line I will probably start a small forum so that future upgrades can be discussed.
Program basics
- The program is written in Perl, Javascript, SQL and HTML. It should run under box FIrefox and IE, I have not ( and probably will not) try it under other browsers.
- It is a windowing system which enables the user to customize what functions are active at any given time. The windows can be synchronized (default) or show separate sections and/or functions.
- The system relies on Ajax to keep refresh rates down.
Data contents
- The text is NA27/UBS4 based on the MorphGNT data.
- It has an extensive apparatus.
- It has a number of lexicons available.
- E-Catena based on CCEL data.
- Many patristic texts, some in critical editions.
- Many custom datasets for statistical, stylometric and syntactical analysis.
Features
Upon further review, it would simply take too long to do this list. So, let me just say that the goal is to have every feature I can think of, i.e. parsing (proper parsing, not just morphological), statistics, lexicon lookups, many types of displays, complex searches, concurrent views, etc. Check out the screenshot above for a preview of the Swanson, regular and Strong view along with the word count with links (can also be displayed by morphological form rather than occurrence).