Hi there . Does anyone have access to Windows ce 6 (Windows Mobile
6)? I've had some correspondence with someone who's trying to get
SwordReader to work on this platform. The current build is for Windows
Mobile 5. He has installed it correctly, and has installed the KJV
module properly
Hi there I mentioned in an earlier post that I no longer use
Windows for ethical reasons. I had attended a lecture by Richard
Stallman (GNU) and was quite disturbed. True, Richard is 'over the
top'. He is a zealot and an absolutist. The real world is not ready
for his degree of
On 07/09/11 06:57, Chris Little wrote:
I convert the imp file to OSIS and use
osis2mod. I would guess that should work fine for a document with
verse-internal ThML markup too, as another option.
This should indeed work, even it is a nasty hack.
The main advantages from my angle are improved
On Wed, 2011-09-07 at 08:13 +0200, Barry Drake wrote:
but
the practices it is using to lock folk into Microsoft is nasty.
I do agree to this. This was one of the main reasons I felt compelled to
at least ensure that Bible translation work escapes from such lock-in,
so that the Word of God
On 7.9.2011 08:13, Barry Drake wrote:
Just wonder what you guys think?
Greetings from the Red Hat towers ;) (and yes, by far not the only one,
but certainly some of the reasons why I stick with Linux are ethical ones).
Blessings,
Matěj
smime.p7s
Description: S/MIME Cryptographic
On 07/09/11 16:22, Jonathan Morgan wrote:
I'm almost at the point of thinking that Microsoft has lost that
battle already. I see kids of three and four who haven't gone through
the education system, but are quite happy playing with iPhones, iPods,
and other similar non-Microsoft technology.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/2011 06:01 AM, Barry Drake wrote:
Hi there . Does anyone have access to Windows ce 6 (Windows Mobile
I just installed it on my Omnia. WinMo 6.5.
SwordReader fires up, but cannot see the module. I'm certain that Microsoft
must
Imho SwordReader hasn't support for path with non ascii symbols, i had
patched SwordReader Dll to work around this but the application wasn't
ever built with this library. So if path contain non ascii symbols
SwordReader can not find modules...
Also according to the current sources, path
I just want to throw this out there:
SwordReader is not at all supported at present. Currently I am
maintaining the the website only for historical reasons. If you or
anyone else involved here would like to take over the project, I'd be
happy to hand over the website. And probably many WinMo
And another little addition.
There is another Sword-derived application for WinCE at
http://bibletimemini.sf.net/. So, you can recommend it to that user, but
if he needs of ability to use Lexicons/Dictionaries he have to wait for a
little.
Greg Hellings greg.helli...@gmail.com писал(а) в
10 matches
Mail list logo
