[sword-devel] Musings about the Cherokee NT module
refdoc at gmx.net
Sun Jul 1 12:51:03 MST 2012
While I must confess my interest in Cherokee is fairly limited, the process of proximity testing would be extremely helpful for study bible creation in any number of languages. Could you explain the algorithms with mire details? Are there cpan or python modules available?
Sent from my HTC
----- Reply message -----
From: "Greg Hellings" <greg.hellings at gmail.com>
To: "SWORD Developers' Collaboration Forum" <sword-devel at crosswire.org>
Subject: [sword-devel] Musings about the Cherokee NT module
Date: Sun, Jul 1, 2012 8:09 pm
On Sun, Jul 1, 2012 at 1:48 PM, DM Smith <dmsmith at crosswire.org> wrote:
> I think what Greg said was correct. I understood it the same way:
> Starting w/ a breakdown of the names in each verse in an English Bible, iterate over that set of verses in the Cherokee Bible, doing the following:
> For each word in the original Cherokee text transliterate into latin characters (So A -> B for each word). Then heuristically compare the list of English names to each B, determining the best B for each English name (So, C -> B for each word).
> At this point we have a transitive relationship of A -> B -> C thus, A can be tagged as a name.
Yes, this is my understanding as well. The process of transliterating
B back into A' (hopefully the same as A but unlikely to be 100% so) is
unnecessary because the A -> B process will be done in memory and in
the same process as the comparison. That way it already has the
mapping between the original and the transliteration and can properly
tag the original text rather than trying to round-trip the process.
On the otherhand, if we have a Latin version of a text that is closer
to Cherokee than any of our English texts, we can probably do the
heuristic step with even more confidence.
> As an optimization, the mapping from A <-> C can be retained and used.
> In Him,
> On Jul 1, 2012, at 2:34 PM, David Haslam wrote:
>> Hi Greg,
>> If all we wanted to achieve is the capitalization of proper names for the
>> transliteration, the back conversion wouldn't be needed.
>> We could even make a Cherokee Latin module, were we so inclined.
>> /Aside - I've even actually made one for myself, but without any uppercase
>> It only becomes relevant were we to go the whole way to restore the original
>> with proper names and sentence starts having 20% enlarged Cherokee syllabary
>> as observed in the PDF file I downloaded from Google books.
>> Does this answer your question?
>> Remember - these are musings that emerged from pursuing my curiosity much
>> further than I'd normally do.
>> For me it was what I learned during the process that's important, yet
>> something significant has emerged.
>> Namely that a detailed inspection of
>> http://en.wikipedia.org/wiki/Cherokee_syllabary brought to light:
>> (a) the potential for inaccuracies arising for theoretical a round trip
>> (b) confirmation from the Cherokee NT text that this was real, not just
>> (c) a demonstrable method to workaround this weakness
>> The Wikipedia page is something I edited while I was engaged in this line of
>> In particular, this section.
>> was added.
>> Best regards,
>> View this message in context: http://sword-dev.350566.n4.nabble.com/Musings-about-the-Cherokee-NT-module-tp4650474p4650482.html
>> Sent from the SWORD Dev mailing list archive at Nabble.com.
>> sword-devel mailing list: sword-devel at crosswire.org
>> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
sword-devel mailing list: sword-devel at crosswire.org
Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel