An old thread from 2012 but something new to ponder for this module.
If anyone fancies a project in *text development*, now that Unicode 9.0
includes a new block for *uppercase Cherokee letters*, rewriting the source
text for the Cherokee NT and making use of the new letters would be an
interestin
As it happens, (and some of you will know that I'm in the habit of doing this
sort of thing recently), I already have made a counted word list of the
Cherokee Latin text. In fact, I've even back-converted the Latin word list
to Cherokee symbols as well.
For these word lists in general (ignoring th
On Mon, Jul 2, 2012 at 10:21 PM, DM Smith wrote:
>
>
> On Jul 2, 2012, at 10:38 PM, DM Smith wrote:
>
>>
>> On Jul 2, 2012, at 9:19 PM, Chris Little wrote:
>>
>>> On 7/2/2012 5:47 AM, Greg Hellings wrote:
Is there an available (and proper-name-tagged!) version of the Bible
in a sister t
On Jul 2, 2012, at 10:38 PM, DM Smith wrote:
>
> On Jul 2, 2012, at 9:19 PM, Chris Little wrote:
>
>> On 7/2/2012 5:47 AM, Greg Hellings wrote:
>>> Is there an available (and proper-name-tagged!) version of the Bible
>>> in a sister tongue to Cherokee that we could use as the basis for
>>> co
On Jul 2, 2012, at 9:19 PM, Chris Little wrote:
> On 7/2/2012 5:47 AM, Greg Hellings wrote:
>> Is there an available (and proper-name-tagged!) version of the Bible
>> in a sister tongue to Cherokee that we could use as the basis for
>> comparisons? "David" -> "dewi" seems a pretty distant compari
On 7/2/2012 5:47 AM, Greg Hellings wrote:
Is there an available (and proper-name-tagged!) version of the Bible
in a sister tongue to Cherokee that we could use as the basis for
comparisons? "David" -> "dewi" seems a pretty distant comparison that
is far more likely to yield issues than if we have
i.e. I was thinking in the context of one of the stated aims in our
http://www.crosswire.org/ home page .
"We are also a resource pool to other Bible societies and Christian
organizations that can't afford-- or don't feel it's their place-- to
maintain a quality programming staff in house. We pro
Greg's question would involve far more detailed research and pre-knowledge
than I have time to look into.
This site may help anyone get started. http://www.native-languages.org/
and there are missionary Bible translators working with several First Nation
peoples.
David
--
View this message in c
Peter writes, "I must confess my interest in Cherokee is fairly limited"
Quite so, and I would have said the same eight weeks ago.
My interest was stirred by existence of the SWORD module, and then by the
fact that the Cherokee NT project might still be a live project. See
http://www.cherokeenewt
On Mon, Jul 2, 2012 at 7:41 AM, David Haslam wrote:
> Hi DM,
>
> We should ignore pronunciation methods for processing Cherokee transcribed
> to Latin.
> The Sequoyah transliteration system is explicitly described as not being
> based on phonetics!
> Please refer to the Wikipedia page.
>
> The edi
Hi DM,
We should ignore pronunciation methods for processing Cherokee transcribed
to Latin.
The Sequoyah transliteration system is explicitly described as not being
based on phonetics!
Please refer to the Wikipedia page.
The edit distance method may be more fruitful, yet there are also hidden
ass
Chris wrote,
"It might make sense for me to add support for syllable-dividing hyphens in
Latin-Cherokee, like you see on the Cherokee NT website, since that would
facilitate its use as an input method. Then a user could type the hyphenated
text and precisely specify the desired syllable signs. "
ible 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"
> To: "SWORD Developers' Collaborat
On 7/1/2012 12:51 PM, ref...@gmx.net wrote:
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
On Jul 1, 2012, at 10:28 AM, David Haslam wrote:
> Hi Chris,
>
> I just tried "diatheke to transliterate as it outputs".
>
> I advise that this suffers from the weakness uncovered by my recent
> researches.
> Back conversion from this Latin transliteration would contain inaccuracies
> in the
- Reply message -
From: "Greg Hellings"
To: "SWORD Developers' Collaboration Forum"
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 wrote:
> I think what Greg said was correct.
On Sun, Jul 1, 2012 at 1:48 PM, DM Smith 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 or
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
(
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
letters/.
It only
What is the possible usefulness of back-conversion? The method Chris
proposed, if I understood him properly, would require no such bidi
transliteration. It would only require transliteration from Cherokee
into Latin and then a comparison of the Latin transliteration text
with known Latin representa
Hi Chris,
I just tried "diatheke to transliterate as it outputs".
I advise that this suffers from the weakness uncovered by my recent
researches.
Back conversion from this Latin transliteration would contain inaccuracies
in the Cherokee.
This should prompt us to consider how we might be able to
See also
http://www.translitteration.com/transliteration/en/cherokee/sequoyah/
This online service has been improved as a result of my contacting the
webmaster, with whom I gladly shared some of my research results.
See the second rule, which was not there earlier.
David
--
View this message in
Has the reversibility of the Cherokee transliteration been thoroughly tested,
Chris?
While I was considering the back conversion it became apparent that the
Cherokee to Latin transliteration would include real instances whereby the
same Latin output would be generated by different Cherokee syllabl
On Jun 30, 2012, at 7:42 AM, David Haslam wrote:
>
> For that reason, I've developed a TextPipe filter to transliterate the
> Cherokee text to the Sequoyah Latin equivalents, using the information in
> the Wikipedia page about Cherokee.
>
If you're using the icu-sword data bundle, which you
I'm going to top post rather than find an appropriate spot within your
message to post my reply. There are two (relatively) straightforward
ways to do this that come to mind immediately:
1) Use ThML. jesus or some such
should work great. You'd lose out support in BibleCS but... *shrug*
2) Implemen
This is an interesting question regarding the preservation of original
orthography, which may be unimportant to today's readers.
Ignoring sentence starts and presuming that words that should begin with a
"capital" letter are names. One could use the OSIS element. The renderer
would be responsi
A few weeks ago, I spent some time researching the Cherokee NT module
Che1860.
The source text comes from the *Cherokee New Testament* project at
www.cherokeenewtestament.org
The Cherokee New Testament was published in 1860 by the American Bible
Society.
The project's electronic edition is still
27 matches
Mail list logo
