> (Also, the term "loved one" that is used as an example, is that in a
> context of a verb or a description?, which makes a difference how to
> word it and explain it in the translation. So that we stay consistant
> with the example used across the many translations).
"Loved one" would end up as
Nic,
sometimes in the future, perhaps we(translators) can translate the "Search
Help" text that explains how to search in PocketSword, (i.e loved one, "loved
one", love*, etc.) Currently it is only in English, I'd figure it could be
helpful to non-English folks to know about the powerful ways
That will go a long way, thank you.
Johan
-Original Message-
From: Nic Carter [mailto:niccar...@mac.com]
Sent: 07 September 2010 03:39 AM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] PocketSword v1.3.2
Hoping that Notes, improved Bookmarks & improved search UI
Yeah - This should definitely use JSword. Negligible difference in
performance, and much easier to maintain for other developers who want to
get involved, etc. The Android NDK is definitely not somewhere you want to
go unless you have to. :)
On Tue, Sep 7, 2010 at 9:26 AM, Martin Denham wrote:
Also C++/JNI requires use of the Android NDK which only generates code
for ARMv5
or ARMv7-A architectures (see
http://developer.android.com/sdk/ndk/index.html) so not all Android devices
would be supported.
Regards
Martin
On 7 September 2010 15:40, DM Smith wrote:
> Some thoughts on whether to
Some thoughts on whether to use JSword or SWORD:
SWORD will be faster than JSword, but for the most part it won't matter.
The primary work of a Bible application are:
a) Convert a reference into a disk read. For a chapter of references,
even Psalm 119, this is so fast for both that it won't be
