Thanks to all those working on SwordReader & SmartSword
Here are my initial thoughts:
1. Great icon in my menu!
2. Came up quickly with KJV Gen 1:1
3. Font was too small to read. I had to get my glasses... Compare with
Olive Tree BibleReader
(User can adjust this later so bigg
Chris,
I appreciate you helping to clear some confusion here since I think
that I helped with some of nudging. This is great news, since all Greek
modules will have a common morph reference. I think covering all the
combinations in the known works would be adequate since most of the
works are n
Troy,
Thanks! That did it! I will add this knowledge to the wiki page if you
don't mind.
A new module with accented Greek will be available soon.
In His Grace,
Robin
>Troy G. wrote:
>If you saw squares, then you likely had the encoding correct and the
>font wrong. Try opening BibleCS, then
DM, Sabastien,
Thanks for your references on encoding. I have read about encodings and Now
I need a practical example of making it thru the module process. Let's say I
have an alpha with an accent (I use PSPad to get the codes in right) and I
have this in XXX.imp. When I bring this into N
On Thu, 17 Jan 2008 [EMAIL PROTECTED] wrote:
>> Hi,
>>
>> I'm trying to display Unicode Greek in RawLD ThML with 1.5.9 BibleCS.
Does
>> anyone know what the .conf file should look like? "Encoding=Unicode or
>> "Encoding=UNICODE" does NOT work. I just get open squares where the
letters
>
Hi,
I'm trying to display Unicode Greek in RawLD ThML with 1.5.9 BibleCS. Does
anyone know what the .conf file should look like? "Encoding=Unicode or
"Encoding=UNICODE" does NOT work. I just get open squares where the letters
should have accents.
In His Grace,
Robin
E-mail: [EMAIL PR
Hi Guys!
I have sent three Daily Devotional module upgrades (DBD, Daily and SME)
to the below email but I have no idea where they are in the pipeline. Could
we have a list on the website or the Wiki that would list when mods were
submitted, approved, rejected, tested, by whom etc. That wou
All,
I did not get much response in pointing out a problem with morph codes
linked to an LD module. I understand that Hebrew Morph codes are in the works
but the problem is really in the LXX module since "GreekParse" is set
to "Robinson" in the global "options.conf" yet "Packard" is needed for
DM,
If there is enough interest in the Body, I would be glad to write a
prototype (well documented) in Perl (call it "mod2cust.pl") if someone
else would write the specs. Someone knowledgeable in mods who
wouldn't miss the "gotchas". It would probably take a few weeks(+ :).
In His Grace,
Robin
David,
I am with you 100%! If I can't get to a verse or do a search within 5 secs.
I'd almost rather use my "snail bible" or wait until I can study at home with
BibleCS or other system. Advancements in miniaturization have always
come with new technology and hardly ever by just porting softwa
Jon,
A good test for your new software would be to convert Nave's Topical Bible
(Nave) and Thompson Chain Topics (TCR) to "taglists". This would test unique
names, descriptions and give you lots of verse reference list examples. Just a
suggestion.
On Dec 3, 2007 12:36 AM, Jonathan Morgan
Hi Guys!
I believe the "Morph" problem is from the following code
in "mainfrm.cpp" of BibleCS.
--
if ((i >= (lookupKey.Length()-1)) && (i)) {
lookupKey = TrimJunk(lookupKey);
String curLex = LexDictPageControl->ActivePage->Caption;
String f
Barry, et al
That makes sense to me.
I have been doing some research on .conf files with BibleCS to see if I
could uncover why "Morph on" does not work with KJV-O.T. and also LXX. I
looked
at "kjv.conf" and "lxx.conf" first and noticed "GlobalOptionFilter=OSISMorph"
in KJV but "GBFMorph
Ben,
How about "ProxBible", "proxBible" or "ProxWord" since proximity search
seems to be the differentiating feature? Is there anything else that separates
it
from the crowd?
> If anyone can think of a better name than BPBible, that
> a) doesn't have Sword in the title (too much confus
David Trotz wrote:
<[sword-devel] SwordReader - Experimental Double Buffering
< added.
Actually in BibleCS if you click the verse up [^] & down [v] buttons there
is quite some flickering that goes on taking as much as 2 seconds on my
Pentium 4. It is worse if [Strongs], [Morph], &
David, (Barry)
I would be glad to test SwordReader on the emulator but don't have a Pocket
PC to measure performance. On a search thru the entire Bible for a sparse word
(e.g. "firkins") how long is it taking? Is it important to include Lucene
add-on? Anyway, the emulator is extremely slow
Jon, DM,
On the "Topic Tagging" request why not enhance the "Personal" commentary
software to allow topic tagging? In fact if someone was ambitious they could
publish a commentary fully "Tagged". Not sure where you would put the "Tag
Manager" but with storage and access resolved, the
Barry, Troy et al,
I found the following guidelines on porting Win32 to WinCE. Perhaps the
filehandle problem could be fixed with "CreateFileForMapping. Just a thought.
Summary of differences when moving from Win32 to WinCE
* Absence of image headers at the start of loaded image on
Barry, Troy et al,
I got the Pocket PC x86 emulator working with Troy's new fix to SWModule.
Besides the Search (Fi) working I got all the other Options working. This is
powerful stuff in a small container! I searched for "amos" in Amos and got
the seven verses, however "preview" was bl
Hi all,
Just to add more flame to the fire I used my 1.5.9 BibleCS version, gave it
"Amos" for the custom range and "amos" for the search word. It defaulted to
"Optimized Search" but I changed it to "Multiword" and clicked Search button.
It came back with the seven verses which I assumed
Dear EMailMaster,
I'm getting deluged with sword messages! Sometimes 5 or 6 a
day! Can I sign up for a DAILY option so I only get one a day at
most. Thanks!
In His Grace,
Robin
E-mail:
[EMAIL PROTECTED]
___
sword-devel mailing list: sword-d
In a message dated 1/30/2006 5:06:11 A.M. Pacific Standard Time,
[EMAIL PROTECTED] writes:
Re:
SWORDWEB Footnote / Cross-ref support
Feedback for the Cross-ref support: This is cool stuff! One
problem I see. When you click on the "x" it brings up 1 or more
references. If you click on
Looks like we need to start filtering SPAM!
In His Grace,
Robin
Phone:
650-948-8037 Fax: 650-948-9337 Cell: 650-518-0025E-mail:
[EMAIL PROTECTED]
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sw
In a message dated 12/2/2005 11:05:31 A.M. Pacific Standard Time,
[EMAIL PROTECTED] writes:
Yes,
keying the greek words to the KJV words, and using Strong's>numbers to
do the keying.>>For instance, it is useful to know that the LXX
uses paradiso where the>KJV translates the Hebrew as
Chris, Lynn,
Then could we see these changes incorporated in the "Standard" packages
users are downloading from Crosswire? Thanks!
In His Grace,
Robin
Phone:
650-948-8037 Fax: 650-948-9337 Cell: 650-518-0025E-mail:
[EMAIL PROTECTED]
___
sword
In a message dated 10/17/2005 11:57:46 P.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
Re:
bible for cell phones
Verizon already has a lookup for KJV but no search capability. I
think it also has a daily verse feature. It is not too expensive
either.
In His Grace,
Robin
Phon
In a message dated 10/17/2005 11:04:31 A.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
Chapter
translations (Mina Magdy)
Mina's message reminded me. Why won't anyone besides me stand up for
a shorter abbreviation for "Revelation of John". In my works I have used
"RV", "REV" and "
Subject: Re: [sword-devel] BibleCS Installer
Troy,
I expect that all the "real" bugs from 1.5.6 have been fixed in the 1.5.8
engine. At this point I do not have the time to get Eclipse and build the
latest BibleCS and install it over 1.5.6. I just wish to download
and install BibleCS 1.5.
In a message dated 6/11/2005 12:03:50 P.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
>Robin,> There a number of issues involved with
considering moving to >try/throw/catch error handling. The first
one that comes to mind is >language binding. Second is
cross-platform port
In a message dated 6/10/2005 12:03:57 P.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
Hey
Daniel, Thanks for the catch, but we don't check for
successful memory allocation anywhere in the engine. I'm not sure
what we'd do if we ran out of memory. Gracefully degradating fro
In a message dated 6/7/2005 12:04:26 P.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
Troy writes:
I
have good and bad news. I've been accepted to attend a summer class
overseas, during June 16-Aug 5. I am not planning any more work on
BibleCS before I leave.I'd like to hear
In a message dated 5/16/2005 8:37:04 A.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
Please don't get me wrong, I so appreciate the
reports. Thank you for all the time you've spent testing and making
us aware of where we fall short.
Troy,
There must be a faster way to re-ca
In a message dated 5/16/2005 8:37:04 A.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
Not, let me say a few things that might make you hopeful. Many of
the bugs you have reported do not belong under the SWORD module in our
bugtracker. Many of the issue that you mention are
Greetings from California!
There seem to be over 40 open issues linked to Sword 1.5.6 on the Jira
bugtracker. How many and which of these issues will be closed in
1.5.8? Are the unresolved issues automatically transferred to the 1.5.8
defect list (or Affects version updated to 1.5.8) once
34 matches
Mail list logo
