[sword-devel] Strong Numbered TSK Commentary [Re: TSK Commentary into generic cross-references (Peter von Kaehne)]
n_e_o_m at hotmail.com
Mon Apr 26 19:32:35 MST 2010
Thank you Jon, Peter, David for your replies.
It is going to take me some more time to digest the input.
I love the idea of Automatic Concordancing personally but I specifically need TSK
not just any concordance (which could be more systematically organized) because
this is something my Japanese Christian friends are waiting for.
And, the reason I need to go back to Strong's number (original texts) is because
English is also a translated text. So, if I work on a English concordance, it will
be a translation of a translation. Say, Greek word can have 5 meanings in English,
then say each English words can mean 5 meanings in Japanese. Then, I have a good
chance of being in Chinese whisper situation or too much options to even adjust manually.
I might be wrong since I have not read the detail implementation of Automatic Concordance and
seen the accuracy of their work. Surely I will keep my eye on this program and make use of it
if it helps as David is going to help us to contact Neil.
> From: jonmmorgan at gmail.com
> Date: Tue, 27 Apr 2010 00:50:39 +1000
> To: sword-devel at crosswire.org
> Subject: Re: [sword-devel] Strong Numbered TSK Commentary [Re: TSK Commentary into generic cross-references (Peter von Kaehne)]
> Strong's numbers may work if you have the numbers in both your source text and your target text (and I don't think we have many non-English Bibles tagged), but I'm still not sure that:
> a. Inferring them will be straightforward (just as an example, from memory the coverage of the Hebrew in the KJV OT is not as complete as the Greek in the NT, and some of the translation links will be one word to many or many words to one or even many words to many).
> b. Going from phrase to phrase will always be a straightforward mapping. If both the source text and the target text are comparatively word for word translations and maintain similar word order, it will probably work reasonably well. The less these conditions are true, the less straightforward the mapping is likely to be. At least some amount of manual editing would probably be desirable.
> An interesting presentation at BibleTech:2010 was on "Automatic Concordancing for Scripture in Any Language" by Neil Rees of the British & Foreign Bible Society. This was presenting a working attempt to solve a somewhat similar problem: how to reuse an existing (back of the Bible) concordance in a different language to make a new concordance for the Bible in that language. This includes detecting head words for each concordance entry and finding the equivalent head word in the target language. Rather than using any kind of original language tagging, they had a solution to gloss directly from the source headword to find the target headword. I don't know whether that approach is applicable to this problem, but if it is it would remove the need to have your target text marked up with Strong's or to infer the Strong's Numbers from the English headwords. There was a paper about it linked from the BibleTech page which provides more detail on the approach (http://www.bibletechconference.com/media/2010/NeilRees2010_ReesRidingGlossing_1.pdf). I imagine such an approach could have similar problems with matching phrases rather than words, though I seem to recall that it handled the case where one word in the source language went to multiple words in the target language. In their process, once the basic concordance was produced in the target language it was then checked and edited until it was ready for printing. The demo (going from Swahili to Welsh at the request of the audience) seemed to work well, though as I know neither Swahili nor Welsh I can't really vouch for its accuracy.
> On Mon, Apr 26, 2010 at 10:58 PM, Nakamaru Kunio> wrote:
> Hello Peter.
> Thank you for reply.
> It took a while to work out for language independent TSK.
> What I see so far is TSK keywords are based on KJV. so, they
> are "almost" convertable to strong's numbers with KJV with strong's number.
> once keywords are in strong's numbers, they become translatable with
> any dictionary to any natural language.
> translation can be done runtime or precompiled. or even just leave a
> link to a specified strong dictionary.
> Now, does anyone know if strong numbered TSK already exist?
> or knows a better community I should contact?
> Kunio Nakamaru
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel