Okay, I've lived with the sentence diagrammer for a while - played with it's ins-and-outs. It really needs to have a tree diagram function. The blog arguments against its use miss the primary point - namely trees are flexible enough to represent any language from the morpheme level up to the phrase, clause, sentence and discourse level. To try to stuff Hebrew into the English Kellogg-Reed system is to muddle/murder the Hebrew syntactic rules. And Kellogg-Reed makes no effort to deal with tense information - often an important issue in translation. My take on the current diagrammer:
morpheme level - not supported
lexical item - Kellogg-Reed for Greek (acceptable); inadequate for Hebrew; shouldn't be applicable to translations
phrase block diagram - well supported for all languages
clause block diagram - well supported for all languages
proposition diagram (arcing) - can do adequately but certainly not as well as with a specialized tool
rhetorical structures (chiasm, concentric, parallel) - can do adequately but could be made easier
Yes, I do recognize that the current diagrammer supports some additional conventions but they are not ones that I have been working with.
But please give us a tree diagram function. After all, Logos changed the OpenText diagrams to tree diagrams so they must see value in them.
