I realize that this is a late reply to this note, but I think that it
pertains to the most recent thread regarding copyrights. Daniel if you
meant it when you wrote it and if you still mean it, perhaps this would
be a good time to help direct the activities of Jonathan and others.
If they are
Gabrial wrote:
> Would it be possible to share your list, so others can work on it in parallel?
That list is for e-Sword modules, _not_ Sword Project modules.
If you really want to spend time hunting down e-Sword modules, to
verify that they are currently publicly available, and then determine
w
Jonathon Blake wrote:
>
> Earlier this month I was given a list of 200 modules for e-Sword that
> allegedly are copyright infringements. When I get through that list,
> I will contact the legitimate copyright holder of every module that
> The Sword Project distributes, to verify that it can be
While all of this discussion is very intirguing, it seems to be clear
to everyone now that the Sword developers want nothing to do with even
a hint of illegality that would surround creation of tools to import
copyright materials from other formats (a very sagacious position, in
my view). Therefor
> From: Eicke Godehardt <[EMAIL PROTECTED]>
> I don't want to circumvent rights. That's why I'm not for sword modules
> of copyrighted texts in any form. But to provide a tool to build a
> module myself for my use only should be ok, as/when private usage is
> alowed. I'm even willing to pay fo
Eicke Godehardt wrote:
I don't want to circumvent rights. That's why I'm not for sword
modules of copyrighted texts in any form. But to provide a tool to
build a module myself for my use only should be ok, as/when private
usage is alowed.
It is relatively trivial to create an input file
Troy wrote:
> DO IT YOURSELF. This isn't a place to come and say, "you should know
> everything and be perfect." We've done the best we can with the supplied
> modules.
Earlier this month I was given a list of 200 modules for e-Sword that
allegedly are copyright infringements. When I get t
Jonathon Blake wrote:
DM SMith wrote:
Especially since at least several of them are _not_ public domain.
Please don't say things like this without a complete listing.
It doesn't matter how many, or how few modules there are.
You are right that
Jonathon,
Not to be harse here, but... Well, I guess I will be harse here. What
do you expect from our module repository? Whatever you answer here...
DO IT YOURSELF. This isn't a place to come and say, "you should know
everything and be perfect." We've done the best we can with the
suppl
Eicke wrote:
>But to provide a tool to build a module myself for my use only should
be ok, as/when private usage is allowed.
If anybody creates for The Sword Project, similar to The Bible Import
Tool for e-Sword, my advice is:
i) Create a list exclusively to support/discuss the tool;
ii) Ban all
--- [EMAIL PROTECTED] wrote:
>
> Philip,
> We've moved our code into a namespace since qpsword
> was written, so
> you're probably missing a: using namespace sword;
> near the top. Hope
> this helps. You might need to leave the using
> namespace sword off and
> add using sword::ModMap
DM SMith wrote:
> >Especially since at least several of them are _not_ public domain.
> Please don't say things like this without a complete listing.
It doesn't matter how many, or how few modules there are.
_All_ of them should provide explicit copyright information, and not a
line of "This mod
I don't want to circumvent rights. That's why I'm not for sword modules
of copyrighted texts in any form. But to provide a tool to build a
module myself for my use only should be ok, as/when private usage is
alowed. I'm even willing to pay for copyrighted sword modules, but
there is no one a
I work on BibleDesktop/JSword so that people can have free, high
quality software to use God's Word fully. I strongly support the rights
of individuals and corporations to their intellectual property and
copyrights. I am unwilling to provide people the tools to circumvent
these rights. I will "
I have been an active member of this mailing list for almost 2 years.
During that time I have been impressed with how careful Chris, Troy and
others are to ensure that no copyrighted texts are available without
permission for Crosswire to distribute.
If you find a module that should not be on
I have a similar "Problem" with german bible translations. But most
translations are free for browsing and private usage. So there is no
legal way to provide sword packages. But why not provide scripts, which
allow every user to build up his own package?
Just downloading, some magic sed/awk to t
Technologically it should not be an overly difficult way, but I would
be wary of the way that this could be viewed by the copyright holder
and by the respective authorities. Seeing as how I'm neither a
lawyer nor an expert on "intellectual propery" laws, I don't know, but
if someone does have an a
17 matches
Mail list logo
