Maybe we all tend to think no-one is interested in our notes and bits of information, but for a person just starting on the language every bit of explanation helps.
In addition to the languages, we should also think about other aspects of Classical Studies. Many of us get some free web space when we sign up with an ISP, maybe we should consider using a bit of it to post information about ancient history, philosophy etc as well as Greek and Latin and post a link on the Textkit site. It doesn’t have to be a fancy web page, just in plain text. Even a revue of a textbook might be of value to people, especially those living in areas without lots of bookshops to browse through.
You can also consider contributing content to the Wikibooks projects. They have books for Latin, “Classical” Greek and Koine Greek, though all of them are embarrassingly empty right now. A motivated person or group of individuals could make a significant contribution to the work. There are countless books like these. The idea is to have them become as useful as the Wikipedia, but I have yet to see any quite like that. But it is something to think about.
I mean morphologically tagged. There isn’t much in the electronic format for full syntactical analysis. Although, I suspect that we will be seeing something of the sort soon. I know that Bibleworks has a diagramming mod with their newest software. It’s only a matter of time before someone comes up with a full set of diagrams. I know that Gramcord has full diagrams available in pdf format, but they were done years ago in a DOS progam called ChiWriter.
What are the constraints on the words for the lookup to perseus?
For instance, no \ marks and capitals must be lowercase with a * identifier? What else?
First of all, Perseus doesn’t always come up with a single definitive answer, but it has several, both for definition and morphological analysis. One must sort through the possibilities and make a judgement call as to which is the best. Often this entails looking up the dictionary entries for each word, since the Perseus quick-definition is not sufficient. Sometimes I am not sure that I am interpreting the Perseus information correctly. And sometimes Perseus simply does not give a satifactory possiblity at all. Cunliffe, at least, lets you know when you are on target by citing the uses of the word. Granted, sometimes the Perseus tool hits the target bullseye without much effort of the user, but too often I have to go through the circus of sifting through all the data…
Two more disadvantages are : the Perseus morphological tool isn’t very printable, so I must stick to the computer when doing my Greek (as opposed to, say, doing it in the open fresh air, or on the bus), and that you do have to actually click on the thing to get a new window, so your eyes keep wandering way off the text. Obviously, if I’m reading aloud, this stops me in my tracks. Even if I’m reading silently, it breaks the sense of what I’m trying to read.
The only remedy I see for this is a) having a human editor (or editors) sorting which defintion/grammatical interpretation is correct and b) having all the information in close proximity, so it’s only takes a quick dash of the eye to get it. If anybody can do this, or find another remedy, that would be wonderful.
By the way, when I used the term “parsed” I meant both definition and morphological tagging.
Well, from my experimentations, what I could do is automatically produce a 80% solution, which could be hand edited down pretty quickly to something useable.
For instance, [size=150]ἄλγε’[/size] appears to be a verb form OR a noun and you can’t tell unless you look at the context. Alas, I’ll report both entries and a human has to fix it up, but it’ll look to be a helluva lot less work of you are editing a mostly correct document already…
Now that I’ve kicked a few perl modules in the ribs I’ll see how soon I can get a demo page up.
For what it’s worth, and having myself dealt with these issues, all you can do is to report the several entries for a given word. The vocabulary tool in my Ancient Greek Text Manager program scrapes the public resolver’s HTML. Multiple definitions are then presented to the user in a select list from which she can choose the right definition.
AGTM tries to solve this by showing definitions when you mouseover a word in the text. Your eye does have to move some, but it’s better than the focus shift required by a new window.
I have heard much praise for the Ancient Greek Text Manager, but sadly I have not yet had a chance to evaluate it myself, being a boycotter of Microsoft products.
If you ever tire of your boycott, you might give it a try. It can be a useful tool.
I have begun to think about incorporating aspects of AGTM (e.g., vocabulary and text search) into the GTSS study group software. GTSS works for both IE and Mozilla.
I suppose it is actually my dad’s boycott, but he makes all the decisions about computers here, though I intend to maintain the boycott when I leave the house. I do not feel this is the place to go into the details (nor do I feel up to it) but the reasoning is essentially how Microsoft is monopolizing the industry, and ultimately controlling freedom of speech (my dad is a free-speech extremist), in addition to the structural superiority of UNIX based systems (Linux and Macintosh). My dad used to work as a professional computer programmer (1970’s-1990’s), so I believe he has a deeper knowledge of Microsoft’s impact on the industry than the average Joe.
Looks like I won’t get to the demo page today. The thing causing the delay is me having to do my greek homework. However, I finally got perseus to give me everything I wanted in the form I wanted, so the only thing left is the parsing of the HTML tables via some method, and the output of the analyzed text.
I think that’s where you would need to go into micro-economic or even macro-economic detail . Out of my league, I must admit. But still, no matter what software I’m forced or marketed to use: I am under the impression that I can still type just what I want.
Their foreign languages support is horrible. I had to buy another program to support hebrew (Davka Writer) and use a tack-on program (tavaultman keysoft) for greek.
I must say, the html output of a morphology/dictionary lookup in perseus is so unbelieveably convoluted, I’m just about to give up. This is possibly the worst HTML abuse I’ve ever seen.
There is one more method I’ll try if this one fails before I give up…