Modules
  1. Modules
  2. MOD-167

TR StrongMorphs not separately marked up

    Details

      Description

      In the TR module StrongMorphs are not separately marked up and are not clear as morphological codes

        Issue Links

          Activity

          Hide
          DM Smith added a comment -

          Example: Luke 7:21
          7:21 en 1722

          {PREP} auth 846 {P-DSF} de 1161 {CONJ} th 3588 {T-DSF}
          wra 5610 {N-DSF} eyerapeusen 2323 5656 {V-AAI-3S} pollouv 4183
          {A-APM} apo 575 {PREP}

          noswn 3554

          {N-GPF} kai 2532 {CONJ} mastigwn
          3148 {N-GPF}

          kai 2532

          {CONJ} pneumatwn 4151 {N-GPN} ponhrwn 4190
          {A-GPN} kai 2532 {CONJ}

          tufloiv 5185

          {A-DPM} polloiv 4183 {A-DPM}

          ecarisato 5483 5662

          {V-ADI-3S} to 3588 {T-ASN} blepein 991 5721
          {V-PAN}

          is encoded as:
          <w lemma="strong:G1722" morph="robinson:PREP">εν</w> <w lemma="strong:G846" morph="robinson-DSF">αυτη</w> <w lemma="strong:G1161" morph="robinson:CONJ">δε</w> <w lemma="strong:G3588" morph="robinson:T-DSF">τη</w> <w lemma="strong:G5610" morph="robinson:N-DSF">ωρα</w> <w lemma="strong:G2323" morph="strongsMorph:G5656 robinson:V-AAI-3S">εθεραπευσεν</w> <w lemma="strong:G4183" morph="robinson:A-APM">πολλους</w> <w lemma="strong:G575" morph="robinson:PREP">απο</w> <w lemma="strong:G3554" morph="robinson:N-GPF">νοσων</w> <w lemma="strong:G2532" morph="robinson:CONJ">και</w> <w lemma="strong:G3148" morph="robinson:N-GPF">μαστιγων</w> <w lemma="strong:G2532" morph="robinson:CONJ">και</w> <w lemma="strong:G4151" morph="robinson:N-GPN">πνευματων</w> <w lemma="strong:G4190" morph="robinson:A-GPN">πονηρων</w> <w lemma="strong:G2532" morph="robinson:CONJ">και</w> <w lemma="strong:G5185" morph="robinson:A-DPM">τυφλοις</w> <w lemma="strong:G4183" morph="robinson:A-DPM">πολλοις</w> <w lemma="strong:G5483" morph="strongsMorph:G5662 robinson:V-ADI-3S">εχαρισατο</w> <w lemma="strong:G3588" morph="robinson:T-ASN">το</w> <w lemma="strong:G991" morph="strongsMorph:G5721 robinson:V-PAN">βλεπειν</w>

          There are two verbs that have strongsMorph in the morphology section.
          ecarisato 5483 5662 {V-ADI-3S}

          becomes <w lemma="strong:G5483" morph="strongsMorph:G5662 robinson:V-ADI-3S">εχαρισατο</w>
          and
          blepein 991 5721

          {V-PAN}

          becomes <w lemma="strong:G991" morph="strongsMorph:G5721 robinson:V-PAN">βλεπειν</w>

          Is it even worth having these strongsMorph morphological codes?

          I see you've added them to the Robinson module. Glad for that because they now have some meaning.
          In looking at G5663 it links to V-ADI and G5721 links to V-PAN.
          Does it make sense to have the code if it maps to the exact value or if it matches but is less specific.
          And if it differs, where does that leave the end user, even if a scholar?

          The nice thing about the Robinson Morphological codes is that after a few (dozen) trips to the module, it is not needed anymore. The G codes will always require lookup. There will be no point if a better, more understandable and more specific code is already there. And there will never be cause to memorize them.

          It appears that these codes are unchanged from old. In looking at Robinson's work on the markup, it appears that it has changed/improved over the years. I think Robinson's work supersedes these and these should be dropped. But if not, shouldn't they be marked as robinson:G5662, since they are now part of your Robinson's module?

          BTW, this issue has exposed 2 bugs in JSword. (These have no bearing on this problem.)
          The first is that if there is a strongsMorph before a robinson, then it won't display either. (It stops when it finds something other than robinson.)
          The second is that JSword does not handle the link in the Robinson's module.

          Show
          DM Smith added a comment - Example: Luke 7:21 7:21 en 1722 {PREP} auth 846 {P-DSF} de 1161 {CONJ} th 3588 {T-DSF} wra 5610 {N-DSF} eyerapeusen 2323 5656 {V-AAI-3S} pollouv 4183 {A-APM} apo 575 {PREP} noswn 3554 {N-GPF} kai 2532 {CONJ} mastigwn 3148 {N-GPF} kai 2532 {CONJ} pneumatwn 4151 {N-GPN} ponhrwn 4190 {A-GPN} kai 2532 {CONJ} tufloiv 5185 {A-DPM} polloiv 4183 {A-DPM} ecarisato 5483 5662 {V-ADI-3S} to 3588 {T-ASN} blepein 991 5721 {V-PAN} is encoded as: <w lemma="strong:G1722" morph="robinson:PREP">εν</w> <w lemma="strong:G846" morph="robinson -DSF">αυτη</w> <w lemma="strong:G1161" morph="robinson:CONJ">δε</w> <w lemma="strong:G3588" morph="robinson:T-DSF">τη</w> <w lemma="strong:G5610" morph="robinson:N-DSF">ωρα</w> <w lemma="strong:G2323" morph="strongsMorph:G5656 robinson:V-AAI-3S">εθεραπευσεν</w> <w lemma="strong:G4183" morph="robinson:A-APM">πολλους</w> <w lemma="strong:G575" morph="robinson:PREP">απο</w> <w lemma="strong:G3554" morph="robinson:N-GPF">νοσων</w> <w lemma="strong:G2532" morph="robinson:CONJ">και</w> <w lemma="strong:G3148" morph="robinson:N-GPF">μαστιγων</w> <w lemma="strong:G2532" morph="robinson:CONJ">και</w> <w lemma="strong:G4151" morph="robinson:N-GPN">πνευματων</w> <w lemma="strong:G4190" morph="robinson:A-GPN">πονηρων</w> <w lemma="strong:G2532" morph="robinson:CONJ">και</w> <w lemma="strong:G5185" morph="robinson:A-DPM">τυφλοις</w> <w lemma="strong:G4183" morph="robinson:A-DPM">πολλοις</w> <w lemma="strong:G5483" morph="strongsMorph:G5662 robinson:V-ADI-3S">εχαρισατο</w> <w lemma="strong:G3588" morph="robinson:T-ASN">το</w> <w lemma="strong:G991" morph="strongsMorph:G5721 robinson:V-PAN">βλεπειν</w> There are two verbs that have strongsMorph in the morphology section. ecarisato 5483 5662 {V-ADI-3S} becomes <w lemma="strong:G5483" morph="strongsMorph:G5662 robinson:V-ADI-3S">εχαρισατο</w> and blepein 991 5721 {V-PAN} becomes <w lemma="strong:G991" morph="strongsMorph:G5721 robinson:V-PAN">βλεπειν</w> Is it even worth having these strongsMorph morphological codes? I see you've added them to the Robinson module. Glad for that because they now have some meaning. In looking at G5663 it links to V-ADI and G5721 links to V-PAN. Does it make sense to have the code if it maps to the exact value or if it matches but is less specific. And if it differs, where does that leave the end user, even if a scholar? The nice thing about the Robinson Morphological codes is that after a few (dozen) trips to the module, it is not needed anymore. The G codes will always require lookup. There will be no point if a better, more understandable and more specific code is already there. And there will never be cause to memorize them. It appears that these codes are unchanged from old. In looking at Robinson's work on the markup, it appears that it has changed/improved over the years. I think Robinson's work supersedes these and these should be dropped. But if not, shouldn't they be marked as robinson:G5662, since they are now part of your Robinson's module? BTW, this issue has exposed 2 bugs in JSword. (These have no bearing on this problem.) The first is that if there is a strongsMorph before a robinson, then it won't display either. (It stops when it finds something other than robinson.) The second is that JSword does not handle the link in the Robinson's module.
          Hide
          Chris Little added a comment -

          I'm not even sure what the expected markup is, but it looks correct in the sample given, is correct in the forthcoming release of TR (2.3), and was very nearly correct in the current release (2.2.1).

          Show
          Chris Little added a comment - I'm not even sure what the expected markup is, but it looks correct in the sample given, is correct in the forthcoming release of TR (2.3), and was very nearly correct in the current release (2.2.1).

            People

            • Assignee:
              Chris Little
              Reporter:
              Peter von Kaehne
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: