Jump to content

Swete's Introduction to the Old Testament in Greek...


Abram K-J

Recommended Posts

...would be nice.... It is in the public domain, I believe, and freely available. Of course, if an ambitious user wanted to make it into a User Tool for the Exchange.... :)

Link to comment
Share on other sites

I can't find an etext, apart from PDF, which preserves the Greek nicely, or the Hebrew for that matter. And the PDF looks like images which means multi-lingual OCR. I'll have to poke about more. And the CCEL one is not for disassembly without permission but its a nice readable download.

 

Thx

D

  • Like 1
Link to comment
Share on other sites

If you were to contact CCEL about their license and dissemination as a free User Tool, you could grab the source of their html version. It's unicode so the greek and hebrew would be preserved (as opposed to the plain text version) and because it's html you'd be able to import it pretty easily. Though, as I'm looking at it now, there would be some clean up you would need to do.

 

Anyway, it sounds like a great project for you guys. You know, with all that free time you have. ;)

  • Like 1
Link to comment
Share on other sites

This is probably worth looking into. The PDF is really quite nice, having lots of internal links and such. I missed the HTML version. I'll have to look again.

 

Thx

D

  • Like 1
Link to comment
Share on other sites

Thanks, guys. Graham, I thought we were the ones that were supposed to be recommending projects for other people to take on! :)

 

Daniel, will you let me know what you find/think if and as you look into it further?

Link to comment
Share on other sites

It's not so much that they have the html version available for download as much as you could save each page (do the printer-friendly version in order to remove all the header/link items). To get the html info.

 

Though, you could also try an html/xml export from the pdf file…

Link to comment
Share on other sites

Dude. Three cheers and a drink of choice for you, Graham!

Link to comment
Share on other sites

Just make a weekend trip to Maine and I'll take you up on it. :D

Edited by Graham Buck
  • Like 1
Link to comment
Share on other sites

I do love Maine! "God's Country," indeed.

Link to comment
Share on other sites

Abram, let me try a sample conversion and see if it looks at all promising and what the issues might be. (Inevitably, there will be some, he said optimistically :))

 

Graham, thanx for the converted PDF. I'll check it out.

 

Thx

D

  • Like 1
Link to comment
Share on other sites

Hmmm... I import to a User Tool from the .html file, but the Greek doesn't show up well... is that just part of the deal with pdf to html conversions?

Link to comment
Share on other sites

How is yours showing up? I just looked at the source and we've got a few things going on. First, the Acrobat html output is garbage. It'll get you in the ballpark, sure, but we've got paragraph breaks where there ought to be soft line breaks. You could regex the the junk out of it and try and clean that up, but that's a deal breaker for me.

 

If you copy/paste the source from the website you'll run into issues like this: post-30445-0-78740900-1404156889_thumb.png

 

That error that is highlighted is caused by this page marker tag in the source: post-30445-0-68001800-1404156987_thumb.png

 

And also, the tagging for footnotes is ignored in the User Tool editor so that you have the superscript for the footnote and then the text of the note immediately following.

 

I know how I would go about handling these, but I'm not sure that the User Tool editor functionality can do it the way I would.

Link to comment
Share on other sites

This is the sort of stuff I was concerned would be required. Not sure how big a deal it is. I have written pre-processing scripts for such stuff before. Looks like more of the same.

 

Thx

D

Link to comment
Share on other sites

Wow--mine looks like this. Did I do something wrong? I just imported a New User Tool from the .html file, Graham.

 

post-31802-0-61087400-1404161762_thumb.png

 

Since you're this far... want to just make it into a sell-able module? :)

 

I'm kidding--mostly. Thanks for your help (and, Daniel, for yours) in getting going on this.

Link to comment
Share on other sites

File converters so far as I've been able to tell, have trouble preserving multiple languages in the output file, or don't attempt to. So you end up with everything encoded in one language, which results in a dodgey output like this. But I will have to look at the file tonight and see, but if you load Graham's HTML file into a browser what do you see in that file at this point in the text ?

 

Thx

D

Link to comment
Share on other sites

It looks much better in Safari:

 

post-31802-0-73845500-1404163050_thumb.png

Link to comment
Share on other sites

Abram, how did you import the tool?

 

Oh, and which did you use? My pdf export? or the html source grabbed from the CCEL website?

Edited by Graham Buck
Link to comment
Share on other sites

I used the html file. I imported from File/User Files/Import User Tool, then import from html. Is there another way I should be doing it?

Link to comment
Share on other sites

It's a program version issue. I was using the latest beta. When I just attempted it the latest standard update I got the same result you did.

  • Like 1
Link to comment
Share on other sites

Okay--well, that's good to know, at least!

Link to comment
Share on other sites

ah interesting - I'll use the latest Windows beta then.

 

Thx

D

Link to comment
Share on other sites

Ok I've played with this a little now. There is work - ain't there always :)

 

So the printer friendly file relieves one of some things but it doesn't make that much difference to the imported tool as Acc was already ignoring quite a big of the stuff.

The Greek and Hebrew (though I cannot read Hebrew) looks fine. Paragraphing is good.

 

And the not so good :

 

Early pages such as the contents list, and the title pages and dedications have too much space or incorrect line breaking. Not hard to fix.

 

The footnotes as Graham mentioned need work. This pretty much has to be done by a script given the sheer number of them. I do not know if there is a way to represent these footnotes in a good way within a User Tool. For example can one create links within the tool to them. I need to check.

 

There are various stray bits of navigation text preserved in the import that need to be removed. As UTs don't have a search and replace function that would best be scripted in the source doc. In addition there are also stray URLs in the text which mean something in the context of the CCEL website but not Acc.

 

Finally there are a ton of links in the doc that could be converted to Acc links to scripture that would be really handy. I don't know if there is support for HTML import to construct such links during import, or in text import for that matter. In any case, it would require more scripting to get that massaged into a form that would then provide this functionality. And even then there are many other links that could be made to other texts that would be useful if one had Acc equivalents for them, or preserved as URL links in the UT pointing to their original targets. It looks like if the scripture links were put into Accordance canonical form that the Auto Link button would do the rest - very cool, but a script is required to do the conversion to canonical form. Luckily I have been developing a Python library to do that - oh yay !

 

Oh and post-finally - I won't delve into theology on that one :)

There are some tabular items like two columns of Demetrius and Genesis in comparison. UTs don't support tables and so this will need some special handling.

 

And post-post-oh dear ...

There are various small things like paragraph numbering for reference - actually not paras exactly but in any case they will need scripting out also.

 

Ah ok - the notes are duplicated at the end of the chapter - the peculiarity of how they have the clickovers done in the running text. So that may help, as one could just delete the ones in the text just leaving the reference to the one at the end. But the ones at the end need some CRs in the right places.

 

Ok, time to return to Deuteronomy. This ain't getting solved tonight.

 

Thx

D

Link to comment
Share on other sites

The footnotes as Graham mentioned need work. This pretty much has to be done by a script given the sheer number of them. I do not know if there is a way to represent these footnotes in a good way within a User Tool. For example can one create links within the tool to them. I need to check.

 

I was just wondering about footnotes in a User Tool. I don't know of a way to do it (or even a good way to fake footnotes).

 

A search and replace feature for User Tools is a good idea, too--that would help clean things up, though couldn't that also be done elsewhere before importing?

 

Thanks for checking this out, Daniel!

Link to comment
Share on other sites

Search and replace can be done quite simply in a text editor like BBEdit/TextWrangler. Just learn a little bit of Regular Expression syntax and you're on your way to stardom.

  • Like 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...