Tim Chase wrote:
> Using the windows versions of the tool osis2mod I have run tests
> making four types of modules(raw, raw + cipher, zipped, zipped +
> cipher). In both cases that the -c switch was used ( -c
> abcd1234efgh5678) while the osis2mod program output indicated that
> the cipher key ph
\krmod\"
c:\sword\out\kjv\krmod\nt
c:\sword\out\kjv\krmod\nt.vss
c:\sword\out\kjv\krmod\ot
c:\sword\out\kjv\krmod\ot.vss
4 file(s) copied.
-Original Message-
From: Jonathan Marsden [mailto:jmars...@fastmail.fm]
Sent: Wednesday, August 26, 2009 10:50 PM
To: SWORD Developers&#x
Jonathan Marsden wrote:
> Peter's proposed "no instructions are needed"
> approach to testing and bug reproduction simply does not reveal this
> kind of important detail.
LOL! Admitted
___
sword-devel mailing list: sword-devel@crosswire.org
http://
Ben Morgan wrote:
> I didn't have USBINARY defined, so encyphering wasn't doing anything x-(
> Once I do, zipped modules seem to work as expected. Raw ones don't.
Makes sense to me -- all my tests so far were with the -z flag because
all the "real" modules I've seen have been compressed modules.
I didn't have USBINARY defined, so encyphering wasn't doing anything x-(
Once I do, zipped modules seem to work as expected. Raw ones don't.
God Bless,
Ben
---
Multitudes, multitudes,
in the valley of decisi
Ben Morgan wrote:
Then there is the question of why Jonathan has it working... Are you
sure cipherraw hasn't been near the module?
What is cipherraw? If it is another SWORD utility, then, yes, I'm sure.
See below.
Only osis2mod (well, and zip and unzip, and diatheke to read a verse,
onc
On Wed, Aug 26, 2009 at 9:54 AM, Ben Morgan wrote:
> On Wed, Aug 26, 2009 at 9:21 AM, Troy A. Griffitts
> wrote:
>
>> I believe the problem is with RawText, but haven't had time to confirm.
>>
>> My suspicion is that if you are building a compressed module,
>> enciphering should work.
>>
>> Just
On Wed, Aug 26, 2009 at 9:21 AM, Troy A. Griffitts wrote:
> I believe the problem is with RawText, but haven't had time to confirm.
>
> My suspicion is that if you are building a compressed module,
> enciphering should work.
>
> Just to clear up a few things...
>
> rawFilters get called (or should
I believe the problem is with RawText, but haven't had time to confirm.
My suspicion is that if you are building a compressed module,
enciphering should work.
Just to clear up a few things...
rawFilters get called (or should get called) when retrieving and when
setting text.
If there is still a
On 26/08/2009, DM Smith wrote:
> It does not work.
>
We found this out a while ago, didn't we?
> The code that has been there forever, no longer works. I checked out
> revision 1929 from June 2006 and with minor changes, compiled it against the
> current SWORD library. It has the same problem
Chris Little wrote:
> Actually, I'm pretty well dumbfounded now.
>
> I can't get the cipher to work anywhere that I've tried. ...
> I'm not sure how Jonathan is getting a positive result. I don't believe
> any significant changes to the cipher stuff were made between 2400 and
> head of osis2mod.
Just another example emphasizing a reason to have module creation be
part of the test suite!
If I have time tonight, after work, I'll try to tackle making some
test cases. Otherwise I will probably have a chance to get to it
later in the week.
--Greg
On Tue, Aug 25, 2009 at 9:16 AM, DM Smith wr
On 08/25/2009 08:14 AM, DM Smith wrote:
On Aug 25, 2009, at 5:42 AM, Chris Little wrote:
Jonathan Marsden wrote:
Tim Chase wrote:
Peter picked off my post to the module making forum. Here are the
steps that I went through for module creation on the windows platform
where the osis2mod with
Jonathan Marsden wrote:
> Peter von Kaehne wrote:
>
>> Ther appears to be a bug with the current osis2mod - using the
>> encryption option nothing appears to happen. The results are identical
>> with or without key
>>
>> I tried revision 2400 and current svn head
>
> It is always a helpful to spe
On Aug 25, 2009, at 5:42 AM, Chris Little wrote:
Jonathan Marsden wrote:
Tim Chase wrote:
Peter picked off my post to the module making forum. Here are the
steps that I went through for module creation on the windows
platform
where the osis2mod with cipher key does not produce an encryp
Jonathan Marsden wrote:
Tim Chase wrote:
Peter picked off my post to the module making forum. Here are the
steps that I went through for module creation on the windows platform
where the osis2mod with cipher key does not produce an encrypted
module. Running on windows..
Thanks for the det
Tim Chase wrote:
> Peter picked off my post to the module making forum. Here are the
> steps that I went through for module creation on the windows platform
> where the osis2mod with cipher key does not produce an encrypted
> module. Running on windows..
Thanks for the detailed info.
I'm not u
Hi Jonathan
Peter picked off my post to the module making forum. Here are the steps
that I went through for module creation on the windows platform where the
osis2mod with cipher key does not produce an encrypted module. Running on
windows..
I downloaded the sword-utilities-1.6.0-r2435.zi
Peter von Kaehne wrote:
> Ther appears to be a bug with the current osis2mod - using the
> encryption option nothing appears to happen. The results are identical
> with or without key
>
> I tried revision 2400 and current svn head
It is always a helpful to specify the "steps to reproduce" when
r
19 matches
Mail list logo
