Jonathan Morgan writes:
> You mean publishers need to have an argumentation base? Since they
> claim ownership of the text, their word is law, no matter how dubious
> you may think the decisions they make are.
...
> They are open source, and thus suspect by default. Does anything more
> need to
On Thu, Mar 12, 2009 at 1:01 AM, Karl Kleinpaste wrote:
> I wonder why we stress so much over encryption and avoidance of copying,
> right down to copy/paste. Nobody else does.
>
> Libronix, which I believe has the strongest per-user license mechanism
> and encryption facility in any Bible softwa
Sounds excellent, we need to do this with SwordReader. I hope David is
listening.
Karl Kleinpaste wrote:
SonWon writes:
Well yes and no, while the personal commentary covers notes it would
likely contain all of your notes where during a Bible study you may
not want to share that much so i
A few technical observations about your problem
On Wed, Mar 11, 2009 at 2:47 PM, Peter von Kaehne wrote:
> Karl's question is probably the one I will need to answer first:
>
> What problem do I want to solve?
>
> a) A bible which has not been (will not be) distributed sufficiently on
> paper to a
Hello,
there is a new tool for modul makers it is called mod2zef and it
converts Sword bible moduls to valid Zefania XML files.
http://zefania.de/infusions/pro_download_panel/image.php?did=14&pic_id=7
http://zefania.de/infusions/pro_download_panel/download.php?did=14
You have to select a sword
Karl's question is probably the one I will need to answer first:
What problem do I want to solve?
a) A bible which has not been (will not be) distributed sufficiently on
paper to allow recipients to compare with known good texts.
b) A hostile environment in which the Bible is considered a societ
Karl Kleinpaste wrote:
I wonder why we stress so much over encryption and avoidance of copying,
right down to copy/paste. Nobody else does.
After I sent my reply, I thought more about what I wrote. Aren't second
thoughts wonderful? :)
All of the things I said have one basic assumption, whi
Am 11.03.2009 um 14:21 schrieb mmital:
Libronix, which I believe has the strongest per-user license mechanism
and encryption facility in any Bible software today, nonetheless makes
it possible to copy/paste in such a manner that even Bible footnotes
are
preserved with proper formatting when
Yes, I echo Karl's response. In all of the many conversations I have
had with publisher, when they ask how we support 'paid' modules, I tell
them of our current system:
encrypt the text with 128-bit key.
supply the single key to the publisher to sell as they would like, which
unlocks the modu
>
> Libronix, which I believe has the strongest per-user license mechanism
> and encryption facility in any Bible software today, nonetheless makes
> it possible to copy/paste in such a manner that even Bible footnotes are
> preserved with proper formatting when pasting into Word.
>
This is also t
I wonder why we stress so much over encryption and avoidance of copying,
right down to copy/paste. Nobody else does.
Libronix, which I believe has the strongest per-user license mechanism
and encryption facility in any Bible software today, nonetheless makes
it possible to copy/paste in such a ma
I have received very similar enquiries when discussing things with Bible
Societies and Translation Agencies.
This is really several distinct topics rolled up into one, but which should
really be distinguished from one another.
- Provenance = ensuring that the text used by CrossWire to make a SWO
SonWon writes:
> Well yes and no, while the personal commentary covers notes it would
> likely contain all of your notes where during a Bible study you may
> not want to share that much so it would be nice to have Bible study
> specific notes. This would be idea to me.
This is why Xiphos provide
On Wed, Mar 11, 2009 at 11:29 PM, DM Smith wrote:
>
> On Mar 11, 2009, at 5:04 AM, Peter von Kaehne wrote:
>
>> One of the problems which has come up again and again when discussing
>> with publishers has been the worry that texts which are released to
>> CrossWire become an easy target for abuse
Am 11.03.2009 um 12:29 schrieb DM Smith:
On Mar 11, 2009, at 5:04 AM, Peter von Kaehne wrote:
One of the problems which has come up again and again when discussing
with publishers has been the worry that texts which are released to
CrossWire become an easy target for abuse - either commercia
On Mar 11, 2009, at 5:04 AM, Peter von Kaehne wrote:
One of the problems which has come up again and again when discussing
with publishers has been the worry that texts which are released to
CrossWire become an easy target for abuse - either commercial abuse
with
texts of some commercial imp
On 11/03/2009, Peter von Kaehne wrote:
>
> One of the problems which has come up again and again when discussing
> with publishers has been the worry that texts which are released to
> CrossWire become an easy target for abuse - either commercial abuse with
> texts of some commercial importance or
Am 11.03.2009 um 10:33 schrieb Mark Trompell:
On Wed, Mar 11, 2009 at 10:44 AM, Manfred Bergmann wrote:
Just a thought.
What about signing the module with a private key.
Every frontend has to have the public key included somewhere hidden.
This would enable an integrity check.
'somewhere hid
On Wed, Mar 11, 2009 at 10:44 AM, Manfred Bergmann wrote:
> Just a thought.
>
> What about signing the module with a private key.
> Every frontend has to have the public key included somewhere hidden.
> This would enable an integrity check.
'somewhere hidden' doesn't work too well with opensource
Just a thought.
What about signing the module with a private key.
Every frontend has to have the public key included somewhere hidden.
This would enable an integrity check.
Manfred
Am 11.03.2009 um 09:04 schrieb Peter von Kaehne:
One of the problems which has come up again and again when di
I have thought about this one myself. Surely there is a way that modules
can be flagged as modules not able to be exported using mod2osis or
mod2imp. That is the real issue, if I understand correctly. It should be
a no-brainer that encrypted modules should not be able to be exported.
That requi
One of the problems which has come up again and again when discussing
with publishers has been the worry that texts which are released to
CrossWire become an easy target for abuse - either commercial abuse with
texts of some commercial importance or, more worrying to me at least -
manipulation of t
On 10/03/2009, Chris Little wrote:
>
>
> Daniel Owens wrote:
>
>> One more thing to consider is poetic elements that are right-justified.
>> One of the translations I have worked on preparing for SWORD had "Selah"
>> right justified (VietNVB, in case you're interested). I just encoded it like
>>
23 matches
Mail list logo
