On Jabber/MSN/Googletalk/ICQ/Yahoo/AIM/etc. Bible chat bot(Eeli Kaikkonen) Eeli, Did you tested it on yahoo IM? I used to do a project chat with yahoo IM using jymsg package and it worked for a while and then stopped. It seems that yahoo changed a little bit in their protocol and jymsg was not able to logon. There were rumors that yahoo manipulate their protocol occasionally to make people feel something. gtalk/jabber works well with xmpp.
Thanks Yiguang --- [EMAIL PROTECTED] wrote: > Send sword-devel mailing list submissions to > sword-devel@crosswire.org > > To subscribe or unsubscribe via the World Wide Web, > visit > > http://www.crosswire.org/mailman/listinfo/sword-devel > or, via email, send a message with subject or body > 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it > is more specific > than "Re: Contents of sword-devel digest..." > > > Today's Topics: > > 1. KJV 2006 - 3rd beta (DM Smith) > 2. Re: KJV 2006 - 3rd beta (jhphx) > 3. Hello, Rod! (jhphx) > 4. Re: KJV 2006 - 3rd beta (DM Smith) > 5. Jabber/MSN/Googletalk/ICQ/Yahoo/AIM/etc. Bible > chat bot > (Eeli Kaikkonen) > 6. Re: KJV 2006 - 3rd beta (Terry T Biggs) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 19 Mar 2006 18:08:01 -0500 > From: DM Smith <[EMAIL PROTECTED]> > Subject: [sword-devel] KJV 2006 - 3rd beta > To: "SWORD Developers' Collaboration Forum" > <sword-devel@crosswire.org> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > I have readied another beta. Please take a look at > it for problems with > these changes and prior ones. There is still more to > be done (fixing > punctuation and spelling mistakes) so no need to > report these yet. > > You can get the module from here: > http://www.crosswire.org/~dmsmith/kjv2006 (The > download links are at the > bottom of the page.) > > Changes from the last beta: > * Fixed 2 problems noted with the last beta, both > regarding the merging > of the definite article into the following <w> > element. > * Paragraph markers are now positioned at the > beginning of a verse. > * Whitespace has been fixed and normalized: > A space follows each verse. > <w> elements that contained leading > punctuation and spacing have > had it moved to immediately before it. > <w> elements with trailing punctuation and > space have had it > moved to immediately after it. > Empty <w> elements followed by spaces and > punctuation have had it > moved before the element. > Newlines and tabs have been replaced with > spaces. > Spaces before certain punctuation marks have > been removed. (e.g. > ? ! , : ; ....) > Multiple spaces have been reduced to a single > space. > * Apostrophe problems have been fixed. > There were 17 different patterns of problems > that were solved. > Here are a few: > Fixed problems when a word ended with ' and > it should have ended > with 's. > Fixed problems when two words were run > together and these were > separated by a '. > Fixed problems where the ' or 's was not > inside the containing > element (e.g. <w>dog</w>'s became <w>dog's</w>) > Fixed problems where a space should have > followed a ' but it did not. > > Note: All of these changes were programmatic. There > may be some that > need to be undone. These will be identified when the > text is compared > with other etexts. > > Next step: > Create verse per line etexts from different sources. > Compare them with wdiff. > Fix obvious errors. > Catalog other errors. > Release another beta. > > In doing this effort I have discovered that a KJV > that you buy today, > probably, won't agree with the KJV 1796. This makes > it problematic in > producing an accurate 1796 version. I've been doing > some research on the > subject, and it appears that the "Old Scofield" or > an early version of > the Thompson's Chain Reference (version 1 -3) is > probably the closest. > As the latter is out of print, I will be purchasing > the former and using > it to do tie-breaking of reported errors. Another > possible reference is > http://www.interleafbible.com/ and it's etext at > http://printkjv.ifbweb.com/. > > So the next beta will not fix minor differences in > spelling. That will > be a following beta. > > Many thanks to Lynn Allan, Tim Lanfear and Miklos > Zsido who provided > long lists of problem verses. These have been > indispensable. > > > > > > > > > > > ------------------------------ > > Message: 2 > Date: Mon, 20 Mar 2006 20:28:29 -0700 > From: jhphx <[EMAIL PROTECTED]> > Subject: Re: [sword-devel] KJV 2006 - 3rd beta > To: "SWORD Developers' Collaboration Forum" > <sword-devel@crosswire.org> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > DM Smith wrote: > > I have readied another beta. Please take a look at > it for problems > > with these changes and prior ones. There is still > more to be done > > (fixing punctuation and spelling mistakes) so no > need to report these > > yet. > As you noted there are differences in the texts > often used today and the > text that this module is suppose to be a copy of. > Over the years I have > received many reports of spelling mistakes in this > module and in others. > Most often they were not mistakes, and the modules > were, in these cases, > true copies of their source texts. In some cases I > was surprised to find > the reports wrong. Sometimes the same text has a > word spelled more than > one way. You can not just compare one verse in a > text to another verse > in the same text. You have to compare the verse to > the source verse. You > also can not assume that one of the spellings in the > source text was a > mistake. Both spellings may have been allowed > spellings at the time of > publication, even though one may look wrong to us > today. If you use > another text as your standard for spelling any > changes based on that > other text should be considered provisional and need > to be tracked until > they can be confirmed by the true source text. As > the Sword Project is > the home of this electronic text perhaps it would be > good to have ways > to track changes and compare to earlier editions. > This list gets > archived but knowing what is in it to search for it > is another thing. > > Jerry > > === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page