Re: [sword-devel] Method Name Normalization

[Andrew Thule]

I just grabbed a fresh copy of sword via svn.

On Sat, Jan 19, 2013 at 11:13 AM, Troy A. Griffitts wrote:
In anticipation of a new release, I have a large checkin I'm about to
commit which will break everything for everyone compiling with -Werror.

The Makefile that comes with sword uses the -Werror directive, so grabbing
via svn and making is currently broken on the making of .libs/swmodule.o.

Could it be fixed it so that what comes via svn isn't broken.  Is the
solution to remove -Werror and try again?

~A


On Mon, Jan 21, 2013 at 6:49 AM, Troy A. Griffitts wrote:

> On 01/21/2013 12:28 PM, Nic Carter wrote:
>
>> Is there a reason for this being the abbreviation and not
>> "setIntroductions(bool)" and "isIntroductions()"? I find it strange that
>> you've fixed up "Lang()" and introduced "Intros()"... But, thanks for this
>> change. It was confusing before! :)
>>
>
> Yeah, well.  :)  Here was my thinking on this.  No one says "Lang" as a
> spoken abbreviation for Language, but we all use "Intros" regularly.  In
> fact-- seeking to justify my behavior-- it looks like google even claims
> "intro" as it's own word: https://www.google.com/search?**
> q=definition+intro 
>
>
> :)
>
>
>  Also, I think you forgot a "const" in echomod.cpp? (one of the tests.) I
>> say "think" cause it threw an error for me and then I realised I didn't
>> need that in my stuff, so I simply deleted it rather than "fix" it..
>>
>
> Fixed.  Thanks for the heads up Nic.
>
> Troy
>
>
>  . ;) Thanks for all of this. :) Still double checking it all with my
>> stuff, but looking good so far :) Thanks, ybic nic... :)
>> __**_ sword-devel mailing
>> list: sword-devel@crosswire.org http://www.crosswire.org/**
>> mailman/listinfo/sword-develInstructions
>>  to unsubscribe/change your settings at above page
>>
>
>
> __**_
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/**mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Method Name Normalization

[Andrew Thule]

To add .. the cmake build works, it is only the traditional
./configure;make;make install that appears broken.

~A


On Tue, Jan 22, 2013 at 1:09 PM, Andrew Thule  wrote:

> I just grabbed a fresh copy of sword via svn.
>
>
> On Sat, Jan 19, 2013 at 11:13 AM, Troy A. Griffitts 
> wrote:
> In anticipation of a new release, I have a large checkin I'm about to
> commit which will break everything for everyone compiling with -Werror.
>
> The Makefile that comes with sword uses the -Werror directive, so grabbing
> via svn and making is currently broken on the making of .libs/swmodule.o.
>
> Could it be fixed it so that what comes via svn isn't broken.  Is the
> solution to remove -Werror and try again?
>
> ~A
>
>
> On Mon, Jan 21, 2013 at 6:49 AM, Troy A. Griffitts 
> wrote:
>
>> On 01/21/2013 12:28 PM, Nic Carter wrote:
>>
>>> Is there a reason for this being the abbreviation and not
>>> "setIntroductions(bool)" and "isIntroductions()"? I find it strange that
>>> you've fixed up "Lang()" and introduced "Intros()"... But, thanks for this
>>> change. It was confusing before! :)
>>>
>>
>> Yeah, well.  :)  Here was my thinking on this.  No one says "Lang" as a
>> spoken abbreviation for Language, but we all use "Intros" regularly.  In
>> fact-- seeking to justify my behavior-- it looks like google even claims
>> "intro" as it's own word: https://www.google.com/search?**
>> q=definition+intro <https://www.google.com/search?q=definition+intro>
>>
>>
>> :)
>>
>>
>>  Also, I think you forgot a "const" in echomod.cpp? (one of the tests.) I
>>> say "think" cause it threw an error for me and then I realised I didn't
>>> need that in my stuff, so I simply deleted it rather than "fix" it..
>>>
>>
>> Fixed.  Thanks for the heads up Nic.
>>
>> Troy
>>
>>
>>  . ;) Thanks for all of this. :) Still double checking it all with my
>>> stuff, but looking good so far :) Thanks, ybic nic... :)
>>> __**_ sword-devel mailing
>>> list: sword-devel@crosswire.org http://www.crosswire.org/**
>>> mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel>Instructions
>>>  to unsubscribe/change your settings at above page
>>>
>>
>>
>> __**_
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel>
>> Instructions to unsubscribe/change your settings at above page
>>
>
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SFTP Support

[Andrew Thule]

Some versions of Ubuntu don't come with SFTP support included in CURL
(because of --without-libssh2 being set).  If this is the case,
instructions to  ensure SFTP is available in curl and libcurl can be found
here:

https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029

~A


On Fri, Dec 28, 2012 at 1:42 PM, Greg Hellings wrote:

> Further digging with help from our friends has revealed this nugget:
>
> $ curl-config --protocols
>
> produces a newline-delimited list of protocols that the particular
> build of libcurl supports. curl-config is a shell script which can be
> run on the build system and should satisfy both the requirements of
> native builds and cross-compiling support. We could use this to set a
> compiler macro indicating support (or not) for SFTP in the target
> libcurl library.
>
> If someone wants to tackle that in the autotools world, I can add
> detection to CMake as well. A simple command such as
> $ curl-config --protocols | grep SFTP | wc -l
> 1
>
> in Fedora will result in a value of 1 or greater if SFTP is supported
> while it should produce 0 if SFTP support is left out. An Ubuntu
> system produce this output:
> $ curl-config --protocols | grep SFTP | wc -l
> 0
>
> And it even works for cross-compiling:
> $ /usr/i686-w64-mingw32/sys-root/mingw/bin/curl-config --protocols |
> grep SFTP | wc -l
> 1
>
>
> This appears to be our best way forward if we want to enable
> compile-time enabling or disabling of this option.
>
> --Greg
>
> On Mon, Dec 24, 2012 at 8:43 AM, Greg Hellings 
> wrote:
> > Troy,
> >
> > On Sun, Dec 23, 2012 at 10:39 PM, Troy A. Griffitts
> >  wrote:
> >> Dear Greg,
> >>
> >> Looking to apply this SFTP patch, could you give me some background as
> to
> >> why the check to ignore across all transports for '.' and '..'?
> >
> > Our downloading method runs recursively from the given directory until
> > it runs out of directory depth. FTP servers don't usually seem to
> > return . and .. as valid paths, and the HTTP(S) transport attempts to
> > parse the returned HTML page to avoid the link to the parent
> > directory. But whatever options are passed by cURL to the SFTP
> > transport resulted in it returning . and .. as paths within the
> > current directory. Because '.' came first in the list, the installmgr
> > was running through an infinite loop whenever it tried to pull data
> > from the server.
> >
> > I added it at the level of all transports because we don't want to
> > either loop infinitely on '.' or accidentally pull a whole server
> > recursively by following '..' to the root of the server. It might be a
> > server config option that permits it, but I wanted to avoid the
> > possibility of the InlstallMgr class getting choked up on it.
> >
> > --Greg
> >
> >>
> >> Thanks,
> >>
> >> Troy
> >>
> >>
> >>
> >>
> >> On 12/03/2012 04:06 PM, Greg Hellings wrote:
> >>
> >> The attached patch will introduce support for SFTPSource transports in
> >> the SWORD engine, allowing a user to access remote repositories over
> >> SFTP (which is enabled by default when a user enables SSH).
> >>
> >> --Greg
> >>
> >>
> >>
> >> ___
> >> sword-devel mailing list: sword-devel@crosswire.org
> >> http://www.crosswire.org/mailman/listinfo/sword-devel
> >> Instructions to unsubscribe/change your settings at above page
> >>
> >>
> >>
> >> ___
> >> sword-devel mailing list: sword-devel@crosswire.org
> >> http://www.crosswire.org/mailman/listinfo/sword-devel
> >> Instructions to unsubscribe/change your settings at above page
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Location of prebuilt lucene indexes.

[Andrew Thule]

Daniel, the indexes themselves are created using the utility mkfastmod.  If
built, the lucene indexes typically sit off of the modules directory
directly .. ie:

.../modules/texts/ztext/kjv/lucene

Administrators of a repo, you can generate the lucene directories, and have
them automatically associated with the modules you are sharing by
generating the index and placing it directly off the module location in
your repo, ie:

/pub/sword/raw/modules/texts/ztext/kjv/lucene
(you can use rsync -av to copy a lucene directory from one location to
another).

If you look at many of the modules in the "Institute for Scripture
Research" repo, those repo administrators have done this already (look at
modules tbn, tkci, tkli, ttr, uzv for example).  The nice thing about when
repo administrators do this, is when you get a module from that repo, you
also automatically get the lucene index. I do the same for my own repo.

If Crosswire were to generate lucene indexes for all of the modules they
host, all module downloads would automatically come with them (at least
this seems to be my experience using pocketsword - only the modules that
have had these directories created seem to have search index's automatic).

Even so, you can generate these indexes yourself.

~A


On Wed, Jan 23, 2013 at 1:12 AM, Daniel Hughes  wrote:

> I noticed that some of the front ends offer the option of downloading
> prebuilt lucene indexes. However I can't seem to find them on
> ftp://ftp.crosswire.org
>
> Where are they hosted?
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Location of prebuilt lucene indexes.

[Andrew Thule]

Peter, DM, Thanks for your response.  I wasn't being critical and I agree.
 There are Pros and Cons either way (resource usage and download time being
considerations) as you point out.

I also agree it's ultimately it's up to the repo administrator and the
user, to decide for themselves what works best for them.  I happen to like
having the index included as part of the repo, because I'm not limited by
resources, and I don't mind the wait.

Regardless, it is still a matter of preference (based upon considerations,
such as the ones you cite).
~A

On Wednesday, January 23, 2013, DM Smith wrote:

>
> On Jan 23, 2013, at 11:02 AM, "Peter von Kaehne" 
> >
> wrote:
>
> >
> >> Von: Andrew Thule >
> >
> >> The nice thing about when
> >> repo administrators do this, is when you get a module from that repo,
> you
> >> also automatically get the lucene index.
> >
> > The reason that this is not done are manifold - including that sword and
> jsword indices are different, that not all platforms have the same
> lucene/clucene incarnation etc.
> >
> > Most users are better off not to use downloaded indices, but to create
> indices suitable for their specific frontend.
>
> To add to what Peter said, this mailing list's archives have extensive
> discussion on why we don't do this and why we have done it for mobile
> devices (only PocketSword and AndBible, and specific to them only).
>
> Also, the transfer time for a lucene index exceeds the time of a recent
> computer to build them, e.g. my laptop. As a Bible Desktop user, I'd really
> rather not transfer an index that is unusable by Bible Desktop.
>
> In Him,
> DM
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Location of prebuilt lucene indexes.

[Andrew Thule]

Peter, if I offended you, I hope you'll forgive me.

~A



On Wednesday, January 23, 2013, Peter von Kaehne wrote:

>
> > Von: Andrew Thule >
> >  There are Pros and Cons either way (resource usage and download time
> > being considerations) as you point out.
>
> There are no pros and only contras. And I certainly have not pointed out
> any pros. Nor has DM. Please stop using my name as supposedly in agreement
> with you. I find this offensive.
>
> FWIW - If you run a repo for anyone other than yourself with indeces
> included, you will create a significant risk of malfunction. For anyone
> other than the user of the specific version of libsword and clucene.
>
> As such no one expects from you anything anymore, so, further explanations
> are probably pointless.
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Location of prebuilt lucene indexes.

[Andrew Thule]

Thanks for making them .. It is appreciated! ...  I find them
incredibly useful (and I was surprised they worked by way of a repo too!)

I am sympathetic to many of the arguements presented against creating them
in repos, and I do create them for myself on the desktop (so to speak) so I
also see the value in that - that said, I almost entirely depend on the
repo indices in PocketSword (a most marvellous tool) where I cannot create
them, so cannot entirely see myself giving up that mode.

I haven't yet spent much time with the And-bible though I down own an Asus
ePad.
~A

On Wednesday, January 23, 2013, Nic Carter wrote:

>
> My suggestion would be to avoid pre-built indices. However, given I'm the
> one who first went about making them, I think there are pros in certain
> situations.  :P
>
> In my situation, I get to be gatekeeper over the entire solution
> (PocketSword), where users cannot change the version of clucene or libsword
> behind my back. And so I can be aware of when things might break (&
> increment my "v1" bit of the download URL of the indices).
>
> BTW, I would strongly suggest that no one else use either the and-bible or
> PocketSword pre-built indices due to incompatibilities that have been
> explained in other posts. :)
> I'd also strongly suggest that no one else creates new ones for another
> platform, unless it's absolutely necessary. They are messy, as you can
> probably gather from all these posts!  :)
>
>
> Thanks, ybic
>     nic...  :)
>
> On 24/01/2013, at 5:18 AM, Peter von Kaehne >
> wrote:
>
> >
> >> Von: Andrew Thule >
> >> There are Pros and Cons either way (resource usage and download time
> >> being considerations) as you point out.
> >
> > There are no pros and only contras. And I certainly have not pointed out
> any pros. Nor has DM. Please stop using my name as supposedly in agreement
> with you. I find this offensive.
> >
> > FWIW - If you run a repo for anyone other than yourself with indeces
> included, you will create a significant risk of malfunction. For anyone
> other than the user of the specific version of libsword and clucene.
> >
> > As such no one expects from you anything anymore, so, further
> explanations are probably pointless.
> >
> >
> > ___
> > sword-devel mailing list: sword-devel@crosswire.org 
> > http://www.crosswire.org/mailman/listinfo/sword-devel
> > Instructions to unsubscribe/change your settings at above page
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Xiphos: Checked out revision 4411. (errors)

[Andrew Thule]

Has something changed in the Xiphos build?

I've had no problems until 4411 (last successful build before was 4408).

The build starts off ok:

[ 42/130] cxx: src/backend/module_manager.cc ->
build/default/src/backend/module_manager_1.o
[ 43/130] cxx: src/backend/sword_main.cc ->
build/default/src/backend/sword_main_1.o
../src/backend/module_manager.cc: In function ‘MOD_MGR*
backend_module_mgr_get_next_module()’:
../src/backend/module_manager.cc:171:30: warning: ‘const char*
sword::SWModule::Name() const’ is deprecated (declared at
/usr/local/include/sword/swmodule.h:285) [-Wdeprecated-declarations]
../src/backend/module_manager.cc:171:30: error: invalid conversion from
‘const char*’ to ‘gchar* {aka char*}’ [-fpermissive]
../src/backend/module_manager.cc:176:43: warning: ‘const char*
sword::SWModule::Lang(char*)’ is deprecated (declared at
/usr/local/include/sword/swmodule.h:353) [-Wdeprecated-declarations]
../src/backend/module_manager.cc:177:43: warning: ‘const char*
sword::SWModule::Type() const’ is deprecated (declared at
/usr/local/include/sword/swmodule.h:313) [-Wdeprecated-declarations]
../src/backend/module_manager.cc:216:48: warning: ‘const char*
sword::SWModule::Description() const’ is deprecated (declared at
/usr/local/include/sword/swmodule.h:299) [-Wdeprecated-declarations]
../src/backend/module_manager.cc:216:48: error: invalid conversion from
‘const char*’ to ‘char*’ [-fpermissive]



But ends with:
../src/backend/sword_main.cc: In member function ‘const char*
BackEnd::get_next_listkey()’:
../src/backend/sword_main.cc:921:24: warning: ‘char sword::SWKey::Error()’
is deprecated (declared at /usr/local/include/sword/swkey.h:159)
[-Wdeprecated-declarations]
../src/backend/sword_main.cc: In member function ‘int
BackEnd::set_range(char*)’:
../src/backend/sword_main.cc:943:57: warning: ‘sword::ListKey
sword::VerseKey::ParseVerseList(const char*, const char*, bool, bool)’ is
deprecated (declared at /usr/local/include/sword/versekey.h:452)
[-Wdeprecated-declarations]
Waf: Leaving directory `/usr/local/src/xiphos/build'
Build failed:
 -> task failed (err #1):
{task: cxx module_manager.cc -> module_manager_1.o}
 -> task failed (err #1):
{task: cxx sword_main.cc -> sword_main_1.o}

Is anyone else having trouble?  I haven't changed my environment (since
revision 4408)  Can anyone tell from the above what the issue might be?
~A
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Xiphos: Checked out revision 4411. (errors)

[Andrew Thule]

I was Karl.  Thanks for the heads up.  I look forward to your fixes (no
rush).

~A


On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste wrote:

> If you're trying to build Xiphos against recently updated Sword, it's
> going to be a mess right now.  I'll deal with it by week's end.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Xiphos: Checked out revision 4411. (errors)

[Andrew Thule]

.. and thinking about it, you're correct.  Something had changed on my end,
namely the Sword revision I was running. I had forgotten about that, until
you pointed it out.

~A


On Thu, Jan 24, 2013 at 10:39 PM, Andrew Thule  wrote:

> I was Karl.  Thanks for the heads up.  I look forward to your fixes (no
> rush).
>
> ~A
>
>
> On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste wrote:
>
>> If you're trying to build Xiphos against recently updated Sword, it's
>> going to be a mess right now.  I'll deal with it by week's end.
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Xiphos: Checked out revision 4411. (errors)

[Andrew Thule]

Thanks Greg .. Ill go looking for the patch .. or perhaps I won't.  Ill
give it thought.
It might be best if I keep a working version of Xiphos, allowing for the
compiler problems, until Karl's updates are merged.

I'm not sure how bad Xiphos withdraw can get ..
~A


On Thu, Jan 24, 2013 at 10:42 PM, Greg Hellings wrote:

> If you monitored the proper message stream you'd see I have created a
> patch which attempts to fix this compile problem but introduces a minor
> display bug in the process (module text will not display at all...).
>
> --Greg
>
>
> On Thu, Jan 24, 2013 at 9:39 PM, Andrew Thule  wrote:
>
>> I was Karl.  Thanks for the heads up.  I look forward to your fixes (no
>> rush).
>>
>> ~A
>>
>>
>> On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste wrote:
>>
>>> If you're trying to build Xiphos against recently updated Sword, it's
>>> going to be a mess right now.  I'll deal with it by week's end.
>>>
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>>
>>
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Question about CMAKE build proceedures

[Andrew Thule]

I'm still fairly new to using CMAKE (but liking it).  I'm finally starting
to feel comfortable with its use, but still have questions .. so if this is
a newbie question, sorry.

Using traditional "./configure; make; make install' I could simply grab a
more recent copy (of sword) via svn and make && make install.

However, I'm finding with CMAKE I have to completely blow away my cmake
build directory before I "cmake -DSWORD_BINDINGS="Perl Python" ../sword".
If I don't, I seem to get never ending compiler/build loops.

Is it generally necessary to start with a fresh cmake build directory
before make && make install?

~A
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Question about CMAKE build proceedures

[Andrew Thule]

Thanks Greg.
Different tools, different philosophies - so it's nice to understand the
thinking behind the tool.
One thing to be said for Cmake builds, is the build information is so
well presented.

~A

On Thursday, January 24, 2013, Greg Hellings wrote:

> I have found it usually necessary. It is heavily encouraged in CMake, and
> enforced in SWORD's scripts for just that reason, to do a build from
> outside of the main source directory in an entirely enclosed environment.
>
> To be truthful, when building with the autofoo toolchain I usually found
> the same difficulty and got in the habit of building that from a
> subdirectory as well.
>
> In general, you shouldn't need to blow away the directory and start again
> unless the CMake files have changed or you want to use different options in
> the build process. As the maintainer of the CMake toolchain, I find myself
> doing it frequently, but most of the time it shouldn't be necessary. I have
> made quite a few changes over the past few months, though, to accommodate a
> number of enhancements, usually related to the bindings.
>
> --Greg
>
>
> On Thu, Jan 24, 2013 at 10:20 PM, Andrew Thule 
> 
> > wrote:
>
>> I'm still fairly new to using CMAKE (but liking it).  I'm finally
>> starting to feel comfortable with its use, but still have questions .. so
>> if this is a newbie question, sorry.
>>
>> Using traditional "./configure; make; make install' I could simply grab a
>> more recent copy (of sword) via svn and make && make install.
>>
>> However, I'm finding with CMAKE I have to completely blow away my cmake
>> build directory before I "cmake -DSWORD_BINDINGS="Perl Python" ../sword".
>> If I don't, I seem to get never ending compiler/build loops.
>>
>> Is it generally necessary to start with a fresh cmake build directory
>> before make && make install?
>>
>> ~A
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org > 'cvml', 'sword-devel@crosswire.org');>
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Python Build Errors (Ubuntu)

[Andrew Thule]

I continue to get the following build errors with the python bindings using
the following:
#cmake -DSWORD_BINDINGS="Perl Python" ../sword


 CUT ...

[ 90%] Generating Sword.cxx
/usr/local/src/sword/include/multimapwdef.h:26: Warning 389: operator[]
ignored (consider using %extend)
/usr/local/src/sword/include/versemgr.h:124: Warning 325: Nested class not
currently supported (Book ignored)
/usr/local/src/sword/include/versemgr.h:149: Warning 325: Nested class not
currently supported (System ignored)
/usr/local/src/sword/include/treekey.h:61: Warning 325: Nested class not
currently supported (PositionChangeListener ignored)
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
copying Sword.py -> build/lib.linux-x86_64-2.7
running build_ext
building '_Sword' extension
creating build/temp.linux-x86_64-2.7
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fPIC -I/usr/local/src/sword/bindings/swig/python
-I/usr/local/src/sword/include
-I/usr/local/src/sword/bindings/swig/python/..
-I/usr/local/src/sword/bindings/swig/python../../ -I/usr/include/python2.7
-c Sword.cxx -o build/temp.linux-x86_64-2.7/Sword.o
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for
Ada/C/ObjC but not for C++ [enabled by default]
Sword.cxx: In function ‘PyObject* _wrap_SWDisplay_Display(PyObject*,
PyObject*)’:
Sword.cxx:44967:43: warning: ‘char
sword::SWDisplay::Display(sword::SWModule&)’ is deprecated (declared at
/usr/local/src/sword/include/swdisp.h:50) [-Wdeprecated-declarations]
Sword.cxx: In function ‘PyObject*
_wrap_SWModule_StripText__SWIG_0(PyObject*, PyObject*)’:
Sword.cxx:49480:65: warning: ‘const char* sword::SWModule::StripText(const
char*, int)’ is deprecated (declared at
/usr/local/src/sword/include/swmodule.h:634) [-Wdeprecated-declarations]
Sword.cxx: In function ‘PyObject*
_wrap_SWModule_StripText__SWIG_1(PyObject*, PyObject*)’:
Sword.cxx:49521:60: warning: ‘const char* sword::SWModule::StripText(const
char*, int)’ is deprecated (declared at
/usr/local/src/sword/include/swmodule.h:634) [-Wdeprecated-declarations]
Sword.cxx: In function ‘PyObject*
_wrap_SWModule_StripText__SWIG_2(PyObject*, PyObject*)’:
Sword.cxx:49552:42: warning: ‘const char* sword::SWModule::StripText(const
char*, int)’ is deprecated (declared at
/usr/local/src/sword/include/swmodule.h:634) [-Wdeprecated-declarations]
Sword.cxx: In function ‘PyObject*
_wrap_SWModule_RenderText__SWIG_0(PyObject*, PyObject*)’:
Sword.cxx:49850:71: warning: ‘const char* sword::SWModule::RenderText(const
char*, int, bool)’ is deprecated (declared at
/usr/local/src/sword/include/swmodule.h:645) [-Wdeprecated-declarations]
Sword.cxx: In function ‘PyObject*
_wrap_SWModule_RenderText__SWIG_1(PyObject*, PyObject*)’:
Sword.cxx:49900:66: warning: ‘const char* sword::SWModule::RenderText(const
char*, int, bool)’ is deprecated (declared at
/usr/local/src/sword/include/swmodule.h:645) [-Wdeprecated-declarations]
Sword.cxx: In function ‘PyObject*
_wrap_SWModule_RenderText__SWIG_2(PyObject*, PyObject*)’:
Sword.cxx:49941:61: warning: ‘const char* sword::SWModule::RenderText(const
char*, int, bool)’ is deprecated (declared at
/usr/local/src/sword/include/swmodule.h:645) [-Wdeprecated-declarations]
Sword.cxx: In function ‘PyObject*
_wrap_SWModule_RenderText__SWIG_3(PyObject*, PyObject*)’:
Sword.cxx:49972:43: warning: ‘const char* sword::SWModule::RenderText(const
char*, int, bool)’ is deprecated (declared at
/usr/local/src/sword/include/swmodule.h:645) [-Wdeprecated-declarations]
g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-Bsymbolic-functions -Wl,-z,relro build/temp.linux-x86_64-2.7/Sword.o
-L/usr/local/src/cmakebuild -lsword -o build/lib.linux-x86_64-2.7/_Sword.so

(From here on it seems successful and sword works save for the python
bindings)
When I try to use the python binding, it fails.  I believe that these build
errors are the problem.
Any ideas about why this is failing?

~A
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] xmllint & the OSIS standard

[Andrew Thule]

I just started working with OSIS.  I create a KJV.osis file using:

%mod2osis KJV > KJV.osis

Then looking at the KJV.osis file I see this as header:



http://www.bibletechnologies.net/2003/OSIS/namespace";
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace
osisCore.2.5.xsd">



-=-=-=- Remainder Deleted -=-=-=-

The schemaLocation produced by mod2osis uses "osisCore.2.5.xsd".
Examples in the manual at the website (
http://www.bibletechnologies.net/ ) says the most recent version is
"osisCore.2.1.1.xsd".  Ok, no big deal, documentation is often the
last thing that gets updated.  So then I try the following command:

%xmllint --valid --noout KJV.osis

All I get is:

KJV.osis:3: validity error : Validation failed: no DTD found !
Location="http://www.bibletechnologies.net/2003/OSIS/namespace osisCore.2.5.xsd"

Then I try the following:
%xmllint --noout --dtdvalid
http://www.bibletechnologies.net/2003/OSIS/namespace/osisCore.2.5.xsd
KJV.osis
%xmllint --noout --dtdvalid
http://www.bibletechnologies.net/2003/OSIS/osisCore.2.5.xsd KJV.osis
%xmllint --noout --dtdvalid
http://www.bibletechnologies.net/2003//osisCore.2.5.xsd KJV.osis
%xmllint --noout --dtdvalid
http://www.bibletechnologies.net/osisCore.2.5.xsd KJV.osis
and:
%xmllint --noout --dtdvalid
http://www.bibletechnologies.net/2003/OSIS/namespace --schema
osisCore.2.5.xsd KJV.osis

All produce the same error, to the effect:
http://www.bibletechnologies.net/2003/OSIS/namespace/osisCore.2.5.xsd:2:
parser error : Content error in the external subset

^
Could not parse DTD
http://www.bibletechnologies.net/2003/OSIS/namespace/osisCore.2.5.xsd

Then I switch to looking at the osisCore.2.1.1.xsd file suggested at
( http://www.bibletechnologies.net/ ) site.  I create a test file
using the suggested headers mentioned in the documents at the same
site (as follows):

-=-=-=- File -=-=-=-



http://www.bibletechnologies.net/2003/OSIS/namespace";
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:noNamespaceSchemaLocation="osisCore.2.1.1"
  xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace
  http://www.bibletechnologies.net/osisCore.2.1.1.xsd";>





TEST
Bible.TEST
Bible.KJV


Bible.KJV








-=-=-=- End of File -=-=-=-

Expecting errors because the above file is missing stuff, I still
can't get xmllint to work with this, continue getting "no DTD found"
errors.

So here are some questions:
1. Given mod2osis generates .osis files pointing to osisCore.2.5.xsd
and the site ( http://www.bibletechnologies.net/ ) suggests
osisCore.2.1.1.xsd can someone tell me which version is the correct
version to use?
2. What is the most recent version (perhaps development-wise)?
3. Where can I get my hands on a valid .xsd file?
4. Can someone give me an example of an xmllint command (linux) that
works remotely?

Thanks.

~Andrew

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] xmllint & the OSIS standard

[Andrew Thule]

Merci beaucoup!

I'll give that a try.

~Andrew

On Sun, Apr 1, 2012 at 6:37 PM, Matěj Cepl  wrote:
> On 2.4.2012 00:28, Andrew Thule wrote:
>>
>> KJV.osis:3: validity error : Validation failed: no DTD found !
>> Location="http://www.bibletechnologies.net/2003/OSIS/namespace
>> osisCore.2.5.xsd"
>
>
> Yes, because .xsd file is not DTD, but XML Schema
> (https://en.wikipedia.org/wiki/XML_Schema_%28W3C%29).
>
> Try
>
> xmllint --noout --schema  KJV.osis
>
> Matěj
>
> --
> http://www.ceplovi.cz/matej/, Jabber: mceplceplovi.cz
> GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
>
> Somewhere at the edge of the Bell curve was the girl for me.
>    -- Based on http://xkcd.com/314/
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] xmllint & the OSIS standard

[Andrew Thule]

@ Troy, thanks for the .zip file.  I'm more interested in trying to
figure out how to create modules than a specific module.  My plan is
try checking some of the stock modules.  Writing a test module,
validate it, eliminate errors  so on.

@ Matěj, I wasn't having much success with --schema either.  Even so,
I downloaded a copy osisCore.2.1.1.xsd and the example you gave,
worked (thanks).

Is there a way to generate a .osis file from the stock modules without
using mod2osis?  Using mod2osis seems to generate tons of errors with
xmllint (presumably because the schema isn't supported).

What's the best way to starting to create a 'test' module for learning purposes?

~Andrew

If I download the .xsd file the command line example you gave should work

On Sun, Apr 1, 2012 at 6:53 PM, Troy A. Griffitts  wrote:
> 2.5 was crosswire modifications with hopes to get pushed into the core spec.
>
> Don't use mod2osis.  Use this:
>
> http://crosswire.org/~dmsmith/kjv2006/sword/kjvxml.zip
>
>
>
>
> On 04/02/2012 12:28 AM, Andrew Thule wrote:
>>
>> I just started working with OSIS.  I create a KJV.osis file using:
>>
>> %mod2osis KJV>  KJV.osis
>>
>> Then looking at the KJV.osis file I see this as header:
>>
>> 
>>
>> http://www.bibletechnologies.net/2003/OSIS/namespace";
>>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>   xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace
>> osisCore.2.5.xsd">
>>
>> > xml:lang="en">
>>
>> -=-=-=- Remainder Deleted -=-=-=-
>>
>> The schemaLocation produced by mod2osis uses "osisCore.2.5.xsd".
>> Examples in the manual at the website (
>> http://www.bibletechnologies.net/ ) says the most recent version is
>> "osisCore.2.1.1.xsd".  Ok, no big deal, documentation is often the
>> last thing that gets updated.  So then I try the following command:
>>
>> %xmllint --valid --noout KJV.osis
>>
>> All I get is:
>>
>> KJV.osis:3: validity error : Validation failed: no DTD found !
>> Location="http://www.bibletechnologies.net/2003/OSIS/namespace
>> osisCore.2.5.xsd"
>>
>> Then I try the following:
>> %xmllint --noout --dtdvalid
>> http://www.bibletechnologies.net/2003/OSIS/namespace/osisCore.2.5.xsd
>> KJV.osis
>> %xmllint --noout --dtdvalid
>> http://www.bibletechnologies.net/2003/OSIS/osisCore.2.5.xsd KJV.osis
>> %xmllint --noout --dtdvalid
>> http://www.bibletechnologies.net/2003//osisCore.2.5.xsd KJV.osis
>> %xmllint --noout --dtdvalid
>> http://www.bibletechnologies.net/osisCore.2.5.xsd KJV.osis
>> and:
>> %xmllint --noout --dtdvalid
>> http://www.bibletechnologies.net/2003/OSIS/namespace --schema
>> osisCore.2.5.xsd KJV.osis
>>
>> All produce the same error, to the effect:
>> http://www.bibletechnologies.net/2003/OSIS/namespace/osisCore.2.5.xsd:2:
>> parser error : Content error in the external subset
>> 
>> ^
>> Could not parse DTD
>> http://www.bibletechnologies.net/2003/OSIS/namespace/osisCore.2.5.xsd
>>
>> Then I switch to looking at the osisCore.2.1.1.xsd file suggested at
>> ( http://www.bibletechnologies.net/ ) site.  I create a test file
>> using the suggested headers mentioned in the documents at the same
>> site (as follows):
>>
>> -=-=-=- File -=-=-=-
>>
>> 
>>
>> http://www.bibletechnologies.net/2003/OSIS/namespace";
>>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>   xsi:noNamespaceSchemaLocation="osisCore.2.1.1"
>>   xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace
>>
>> http://www.bibletechnologies.net/osisCore.2.1.1.xsd";>
>>
>> > xml:lang="en">
>>
>>         
>>                 
>>                         TEST
>>                         Bible.TEST
>>                         Bible.KJV
>>                 
>>                 
>>                         Bible.KJV
>>                 
>>         
>>
>>         
>>         
>>         
>> 
>>
>> -=-=-=- End of File -=-=-=-
>>
>> Expecting errors because the above file is missing stuff, I still
>> can't get xmllint to work with this, continue getting "no DTD found"
>> errors.
>>
>> So here are some questions:
>> 1. Given mod2osis generates .osis files pointing to osisCore.2.5.xsd
>> and the site ( http://www.bibletechnologies.net/ ) 

Re: [sword-devel] xmllint & the OSIS standard

[Andrew Thule]

Thanks again for the links.  The wiki is a real resource! I did have
success with:
%xmllint --noout --schema osisCore.2.1.1.xsd kjv.xml (where the
kjv.xml came from Troy's kjvxml.zip file).

I take it the kjv.xml and the other .xml files in the kvjxml.zip are templates?



On Sun, Apr 1, 2012 at 7:40 PM, Greg Hellings  wrote:
> On Sun, Apr 1, 2012 at 6:10 PM, Andrew Thule  wrote:
>> @ Troy, thanks for the .zip file.  I'm more interested in trying to
>> figure out how to create modules than a specific module.  My plan is
>> try checking some of the stock modules.  Writing a test module,
>> validate it, eliminate errors  so on.
>>
>> @ Matěj, I wasn't having much success with --schema either.  Even so,
>> I downloaded a copy osisCore.2.1.1.xsd and the example you gave,
>> worked (thanks).
>>
>> Is there a way to generate a .osis file from the stock modules without
>> using mod2osis?  Using mod2osis seems to generate tons of errors with
>> xmllint (presumably because the schema isn't supported).
>
> mod2osis does not generate valid OSIS. This is a known and
> acknowledged problem and is not going to be fixed.
>
> --Greg
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Happy Easter

[Andrew Thule]

Death is broken!

On Mon, Apr 9, 2012 at 2:57 AM, Teus Benschop  wrote:
>>> > Happy Easter my friends and co-laborers in the Lord. He is risen!
>>>
>>> He is risen, indeed!
>> Alleluia!
> Amen, he is risen. He has been declared to be the Son of God with power
> through his resurrection from the dead ones. Teus.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Module Repository Mirrors (aside from the main repositories)?

[Andrew Thule]

The module repositories are listed here:
http://www.crosswire.org/wiki/Module_Repositories

Are there any mirror sites for the module repositories listed above
(CrossWire Main, CrossWire Beta, CrossWire av11n, CrossWire attic,
Xiphos etc)?
If not, would there be any interest (if someone were to offer to host
and run a mirror at no cost)?

~Andrew

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] xmllint & the OSIS standard

[Andrew Thule]

Thanks for the link.  This will be interesting once it gets up and
running (integration of apocrypha, for example, would be interesting.

Sorry if my questions have been asked before.  I'm new to the list and
find it difficult to easily search the archives.

~Andrew

On Mon, Apr 9, 2012 at 10:48 AM, David Haslam  wrote:
> Andrew,
>
> The file kjv.xml (from kjvxml.zip) is indeed what was used to make the KJV
> modules (v2.3 in Main, and v2.4 in Beta).
>
> For further imporvement work being done or considered for the KJV source
> text (since 2006), see also
> http://crosswire.org/wiki/User:Dmsmith/KJV2011
>
> DMSmith is the main 'pumpkin holder'.
> As he's giving priority to adding av11n capability to JSword (and Bible
> Desktop),
> the implementation of such minor improvements to the KJV source text has
> been delayed.
>
> David
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/xmllint-the-OSIS-standard-tp4524601p4542949.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Websites

[Andrew Thule]

(Relatively new to the list, so perhaps I shouldn't comment) I see both
perspectives being presented here and agree with both whole heartedly.  I
don't think they are mutually incompatible.

It is true Crosswire should be so much more than sword, that the goal of
getting the bible into the hands of many should not be limited to sword,
but the argument being made (as I understand it) isn't that efforts should
concentrate on one technology at the expense of another, or that the site
should cater to one over others, rather the argument is one about usage,
navigability, and perhaps branding.

Before joining this list, I came to Crosswire frequently - specifically for
the purpose of obtaining modules; seeing what other 'Sword' projects were
on the go, etc.  I was personally aware that Crosswire's focus was beyond
'Sword' but that's not what drew me in (I represent the typical European/N.
American middle class consumer however).  What drew me in was 'Sword'.
However, even if Sword is not the sole purpose of Crosswire, I expect it
accounts for much of the traffic.  So this is, in part, also about ease of
navigability, and branding, more than about selective effort.  (I'd bet an
analysis of the sites AWSTATs would show that Sword accounts for much of
the sites profiles, and that certainly is my experience).

Assuming there is general agreement that Crosswire != Sword what is the
'return on investment' for preserving the differentiation between
Crosswire/Sword, or being dogmatic about differentiating? Perhaps that
isn't even the correct question: is there some way to give the sword
component more exposure without subsuming the non-Sword bits of Crosswire?

The request to give sword modules greater exposure is valid if the
underlying concern is simply to make that part which (may) receive the
lions share of effort, and which (may) accounts for the lion's share of
traffic, more accessible with a stronger brand.  This should be achievable
without seeming to jeopardize the complete mission of Crosswire.

~Andrew

On Tue, Apr 10, 2012 at 10:33 AM, jhphx  wrote:

>  On 4/10/2012 6:01 AM, Mike Hart wrote:
>
>
>  I completely agree that for anyone on this list, getting any text onto
> an e-reader is trivial. However,  99.9% of the world does not have that
> knowledge, and getting homework, or Bible texts, onto a Kobo e-ink slate is
> beyond their competence. Which is why, again, Crosswire should be so much
> more than sword.  Things that are too easy to worry about here are unknown
> or impossible for someone who knows 5 people using a kindle e-ink device
> that speak Chinese, leaving for the homeland in 2 weeks, and the discussion
> about Christ got to a point they would consider transporting a ZH text back
> with them.
>
>
> A lot of people can't use anything until it shows up in their start menu.
> Even if they could download a file they would not know where to find the
> directory with the file that was downloaded. I used to support texts for
> downloading that were in TXT and DOC formats. It was amazing how many
> people couldn't figure out what to do with them once they downloaded them.
> That was in the DOS days but I still deal with people that don't have a
> clue. There is only so much that can be done in this regard.
>
> I like the idea of getting a program on the start menu which will lead
> them to the modules on their computers and on the net without them having
> to worry about what the web sites look like. Of course they still have to
> be able to get that program on the start menu. The job of presenting
> modules for downloading then goes to the front end developers. The
> alternative is to be something like CCEL.org. CCEL is a text library. To my
> knowledge Crosswire is not a text library. It is a software and software
> module library. A distinction that the end user should not have to be much
> concerned about, but that does not mean it works for people not using
> supported software or devices.
>
> Jerry
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Kindle/Nook Format

[Andrew Thule]

Quoting Peter "If I or someone in my organization has texts to hand to
Crosswire in epub format and declare them in the care of Crosswire, would
someone at Crosswire consider starting a repo of epub format texts?"

I can't speak officially for Crosswire, but I can volunteer resources to
host your epub formats Peter, since I have resources available to host (I
own some data centres).

I've been playing with how Sword software deals with FTP repositories. I
don't know if I've broached rules in doing this but I did this for two
reasons.  I wanted to get test modules onto my iPad and used the repository
to do that for testing purposes.  I also wanted to provide access to sword
modules to a friend who lives in an environment where 'crosswire' is
filtered.  So I set up a Crosswire/NET/Xiphos/IBT Mirror using the
following details:

Mirror Name: 1XO NET Bible Mirror
Mirror Machine Name: ftp.1xo.net
Repository Directory: /bible/sword
Link: ftp://ftp.1xo.net/bible/sword

Mirror Name: 1XO CrossWire Bible Society Mirror
Mirror Machine Name: ftp.1xo.net
Repository Directory: /crosswire/pub/sword/raw
Link: ftp://ftp.1xo.net/crosswire/pub/sword/raw

Mirror Name: 1XO CrossWire Bible Society (attic) Mirror
Mirror Machine Name: ftp.1xo.net
Repository Directory: /crosswire/pub/sword/atticraw
Link: ftp://ftp.1xo.net/crosswire/pub/sword/atticraw

Mirror Name: 1XO CrossWire Bible Society (av11n) Mirror
Mirror Machine Name: ftp.1xo.net
Repository Directory: /crosswire/pub/sword/raw
Link: ftp://ftp.1xo.net/crosswire/pub/sword/avraw

Mirror Name: 1XO CrossWire Bible Society (Beta) Mirror
Mirror Machine Name: ftp.1xo.net
Repository Directory: /crosswire/pub/sword/betaraw
Zip Directory: /crosswire/pub/sword/betapackages/rawzip
Link: ftp://ftp.1xo.net/crosswire/pub/sword/betaraw

Mirror Name: 1XO CrossWire Bible Society (Xperimental) Mirror
Mirror Machine Name: ftp.1xo.net
Repository Directory: /crosswire/pub/sword/raw
Link: ftp://ftp.1xo.net/crosswire/experimental

Mirror Name: 1XO IBT Mirror
Mirror Machine Name: ftp.1xo.net
Repository Directory: /ibt/pub/modsword/raw
Link: ftp://ftp.1xo.net/ibt/pub/modsword

Mirror Name: 1XO Xiphos Mirror
Mirror Machine Name: ftp.1xo.net
Repository Directory: /xiphos
Link: ftp://ftp.1xo.net/xiphos/

I'll continue running this until or unless someone asks me to stop with the
offer that if anyone else wants to use this mirror for other modules, let
me know. Also, I would be greatly appreciated if people would test this
mirror out by adding them to your Module Managers.

~Andrew

On Fri, Apr 13, 2012 at 3:24 AM, Peter von Kaehne  wrote:

> On Thu, 2012-04-12 at 15:50 -0700, Mike Hart wrote:
> >
> > Crosswire in 2004 listed palmbible+ as a crosswire program (today the
> > site claims that crosswire has no palm platform program.)
>
> FWIW, the site even then did not claim that Palm software is CrossWire,
> but listed it in an admittedly more confusing fashion than it is listed
> now.
> >
> > Besides a contact offlist, noone has made any statement for or against
> > releasing epubs via CrossWire.
>
> Owning a epub reader I can not see a less useful way for studying the
> Bible than using epub. The first thing I did was rooting it and
> installing And Bible on it to have a decent study tool.
>
> epub appears useless to me as a format for anything other than reading
> unidirectionally without any serious referencing forward and backward.
>
> That said, some publishers might indeed be happy for us to produce epubs
> too, but I have neither time nor inclination to work in that direction.
> If you want to produce a converter say OSIS to ePub or USFM to ePub and
> this converter works well, I am sure we could offer epubs to these
> publishers for their further use. Whether we would offer them ourselves
> for download is another question. I have no opinion on.
>
> Yours
>
> Peter
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Kindle/Nook Format

[Andrew Thule]

Ok I'll take it down .. no worries.



On Fri, Apr 13, 2012 at 3:49 PM, Mike Hart  wrote:

> I also apologize to PVK if somehow my request has turned into an
> impersonation of Peter.
>
> I'll respond to Andrew offlist about epub/mobi formats, but someone with
> specifics on licenses should inform him about redistributing some of the
> copyrighted texts that his posting implies.  In short, Andrew, Crosswire
> has permission to distribute many of the text they do, but that permission
> is not transferrable.  If, for example, you've mirrored  Crossway's English
> Standard Version module, you are risking both prosecution and having
> Crossway request that Crosswire stop distributing the module.
>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Kindle/Nook Format

[Andrew Thule]

Already done.

On Fri, Apr 13, 2012 at 7:48 PM, Peter von Kaehne  wrote:

>
> > Von: Andrew Thule 
> > I've been playing with how Sword software deals with FTP repositories. I
> > don't know if I've broached rules in doing this but I did this for two
> > reasons.
>
> Please take these repos down ASAP.
>
> You have no permission whatsoever to set up mirrors for modules where the
> license is restricted to CrossWire
>
> If you want to experiment, please restrict yourself to public domain
> modules and those which explicitly state that redistribution is permitted.
>
> Peter
>
>
> --
> NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
> Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] mirrors

[Andrew Thule]

On Sun, Apr 15, 2012 at 3:25 AM, Kahunapule Michael Johnson <
kahunap...@mpj.cx> wrote:

>  Comments below...
>
> I think that either proxies or mirrors can improve the probability of
> access from creative access countries. The primary difference is that a
> mirror increases the effective available download bandwidth while a proxy
> does not, unless it is a caching proxy. The main issue with mirrors is if
> they are periodically updated to the contents of the master site (which is
> good) or just mirrored once with content that eventually goes stale (which
> is not as good). If, like Ubuntu archive mirrors, all mirrors use rsync in
> a specific manner to update every 6 hours, then all archives contain the
> exact same data. I would rather see regularly-updated mirrors or caching
> proxies than simple proxies, just to get the added benefit of more capacity
> (and therefore more resistance to DOS attacks as well as more ability to
> distribute Scriptures to more people in a given time).
>

Not having access to rsync with the main Crosswire site, to avoid
fragmentation between the main site, and the mirror I emulated rsync via
FTP using the following in a cron job (which was as close as I could get):

/usr/bin/wget -nH -np -m --passive-ftp --user=anonymous --password=
mir...@user.com ftp://ftp.crosswire.org/pub/sword/raw

When something at the main site changed, it was replicated at the mirror,
if nothing changed, nothing was copies.  Nothing that existed on the mirror
differed from what was on the main sites (so the purpose was to have an
exact copy).

I provide this only to fill in technical details of how I was 'mirroring'
the main site, not to support some particular position or another.

~Andrew
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Suggestions: Red-Letter type Mark Up for Messianic References in OT

[Andrew Thule]

I've been playing with the following module:
http://crosswire.org/~dmsmith/kjv2006/sword/kjvxml.zip

Specifically, I've been looking at how text is 'altered' in appearance by
tags such as  divineName, foreign, ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Suggestions: Red-Letter type Mark Up for Messianic References in OT

[Andrew Thule]

Thanks Peter .. I have  looked over the OSIS document and been overwhelmed
by the options.  I seems to me to be two related strategies; consistently
alter text in a visible way (as the red-letter quote seems to do), or group
text into class types (as the foreign or divinename tags seem to do). Your
cross-reference note is a good one for inter-text connectivity.

Are there additional ways to set apart groups of particular texts, as
related (as the http://crosswire.org/~dmsmith/kjv2006/sword/kjvxml.zip
> >
> > Specifically, I've been looking at how text is 'altered' in appearance by
> > tags such as  divineName, foreign,  > References" in the OT for example, (or perhaps OT quotes in the NT), what
> > would be the preferable way of doing this?
> >
> > ~Andrew
>
> --
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Suggestions: Red-Letter type Mark Up for Messianic References in OT

[Andrew Thule]

Yes, thanks very much Troy - it does (get me started).

~Andrew

On Mon, Apr 23, 2012 at 3:09 PM, Troy A. Griffitts wrote:

> On 04/23/2012 06:55 PM, Andrew Thule wrote:
>
>> I've been playing with the following module:
>> http://crosswire.org/~dmsmith/**kjv2006/sword/kjvxml.zip<http://crosswire.org/%7Edmsmith/kjv2006/sword/kjvxml.zip>
>> <http://crosswire.org/%**7Edmsmith/kjv2006/sword/**kjvxml.zip<http://crosswire.org/%7Edmsmith/kjv2006/sword/kjvxml.zip>
>> >
>>
>>
>> Specifically, I've been looking at how text is 'altered' in appearance
>> by tags such as  divineName, foreign, > References" in the OT for example,
>>
>
> probably as Peter suggested, simply use a note with a catchWord to
> identify exactly the text.
>
>
>  (or perhaps OT quotes in the NT),
>>
>
> new testament quote/allusion to old testament
> verse
>
> and probably a  included to footnote the
> verses as suggested by Peter.  You might also include the global
> annotateRef="osisRef" on the seg to indicate the OT passages, but this is
> mostly meant for commentaries of other works.  I guess you could consider
> the NT a commentary on the OT :)  But we probably wouldn't ever expect that
> attribute to be there.
>
> Hope that gets you started.
>
> Troy
>
>  what would be the preferable way of doing this?
>>
>> ~Andrew
>>
>>
>>
>> __**_
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel>
>> Instructions to unsubscribe/change your settings at above page
>>
>
>
> __**_
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel>
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Inuktitut Version Sword Module

[Andrew Thule]

I'm working on an Inuktitut Version of the bible to make a sword
module.  The OSIS form is based upon example set in kjvxml.zip
The header looks as follows:

-=-=- HEAD -=-=-

http://www.bibletechnologies.net/2003/OSIS/namespace";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace
http://www.bibletechnologies.net/osisCore.2.1.1.xsd";>




Inuktitut Version
Bible.IUV
Gen-Rev
Bible.KJV


Bible.KJV



-=-=- HEAD -=-=-

John 3:16 looks as follows:

ᑍᒫᒃ ᑕᕝᕙ ᒎᑎᐅᑉ
ᓯᓚᖅᔪᐊᕐᖕᒥᐅᑦ ᓇᒡᓕᒋᕔᑦ ᐃᕐᖕᓂᑐᐊᓂ ᑐᓂᖕᒪᒍ, ᓇᓪᓕᐊᑦ ᑖᑦᓱᒧᖓ ᐅᒃᐱᖅᑐᖅ ᐊᓯᐅᖁᓇᒍ ᓄᖑᓱᐃᑦᑐᒥᒡᓕ
ᐃᓅᓯᖃᖁᓪᓗᒍ. 

Here's the iuv.conf file:

[IUV]
DataPath=./modules/texts/ztext/iuv/
ModDrv=zText
Encoding=UTF-8
BlockType=BOOK
CompressType=ZIP
SourceType=OSIS
Lang=iu
GlobalOptionFilter=OSISFootnotes
GlobalOptionFilter=OSISHeadings
MinimumVersion=1.6.0
SwordVersionDate=2009-05-29
Version=1.0
Description= Inuktitut Version
LCSH=Bible. Inuktitut.
DistributionLicense=Not for distribution (yet).
InstallSize=3858243


You get the idea.

I've not be able to get it to show up in Bibletime, Xiphos, etc.  I
know how to install Sword modules (I've done lots).  I have it
compiling (only a few errors, mostly warnings and info):

You are running osis2mod: $Rev: 2708 $
INFO(WRITE): Appending entry: Mark.16.9: 
ᐊᒡᓚᒃᓯᒪᔪᑐᕾᑦ ᐊᓯᖏᑦ ᐅᑯᓂᖓ ᐃᓚᔭᐅᒃᑲᓐᓂᖅᓯᒪᕗᑦ  [ᑕᕝᕙ ᐊᕐᖕᓁᑦ ᐲᑦᑐᕉᓯᒧᐊᖅᐳᑦ ᐃᓚᓐᓇᕆᔭᖏᓐᓄᓪᓗ, ᐅᖃᖅᐳᓪᓗ ᓁᑦᑐᒥᒃ
ᐅᖃᐅᑦᔭᐅᑦᔪᑎᒋᖅᑲᐅᔭᒥᖕᓂᒃ.
INFO(WRITE): Appending entry: Mark.16.10: ᑕᒪᑐᒪᓕ ᑭᖑᓂᖓᒍᑦ, ᔩᓱᓯ ᓇᖕᒥᓂᖅ
ᑎᓕᓯᓚᐅᖅᐳᖅ ᐃᓕᓐᓂᐊᖅᑎᒥᓂᒃ ᓯᕿᓂᐅᑉ ᓄᐃᕕᐊᓂᑦ ᓯᕿᓂᐅᑉ ᓂᐱᕕᐊᓄᑦ ᑎᑭᓪᓗᑎᒃ. ᑕᒪᑐᒥᖓ ᐅᖃᐅᓯᖃᖅᓗᑎᒃ
ᐃᔨᖅᓯᒪᓚᐅᖅᑐᒥᒃ ᐃᓅᓯᖃᕐᖕᓇᖅᑐᒥᒃ ᐱᐅᓕᔭᐅᓂᕐᖕᒥᒡᓗ ᐃᓱᖃᖏᑦᑐᒧᑦ.]16:10ᐃᓚᖏᑦ ᐊᒡᓚᒃᓯᒪᔪᑐᖃᕕᓃᑦ ᐋᖅᑭᒃᓱᖅᑕᐅᕙᒃᑐᕕᓃᓪᓗ
ᐊᒡᓚᑐᕾᑦ ᓁᓐᓂᖅᓴᐅᖕᒪᑕ, ᐃᓚᖏᓪᓗ ᑕᑭᓂᖅᓴᐅᓪᓗᑎᒃ ᑕᕝᕙᓐᖓᑦ ᕚᓯᖓ 9-ᒥᑦ–20-ᒧᑦ
ᐃᓚᓯᒪᓪᓗᑎᒃ  

WARNING(NESTING): verse Acts.15.23 is not well formed:(46,48)
INFO(V11N): Jude is not in the KJV versification. Appending content to
3John.1.14
INFO(WRITE): Appending entry: 3John.1.14:  ᓮᒻᒪᓂᐅᑉ ᐃᓚᒋᓕᑎᑦ. ᐃᓚᓐᓇᕆᔭᑦᑎᓐᓂᑦ ᑕᕝᕙᐅᕗᑏᖅᑕᐅᕗᑎᑦ. ᓇᖕᒥᓂᖅᓗ
ᐃᓚᓐᓇᕆᔭᕗᑦ ᑕᕝᕙᐅᕗᑏᖅᐸᕗᑦ ᑍᑲᓃᑦᑐᑦ. 


SUCCESS: /usr/local/bin/osis2mod: has finished its work and will now rest

Yet I still can't it show up in my modules list.  I think this is a
language issue.  I've tried changing language to iu_CA ... i.e.
xml:lang="iu" (as well as in conf file).

Any ideas why I'm not seeing it show up?  What must I do to get the IU
language recognized?

~Andrew
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Inuktitut Version Sword Module

[Andrew Thule]

Thanks all, got it working now.


On Wed, Jul 11, 2012 at 10:15 AM, Troy A. Griffitts
 wrote:
> I often have this problem when permissions are not set correctly on the
> module files.  I believe our module creation tools err on the side of
> security, producing files with less permission than you might need.  Be sure
> they're readable by the user running your software.
>
> Troy
>
>
> On 07/11/2012 06:21 AM, Andrew Thule wrote:
>>
>> I'm working on an Inuktitut Version of the bible to make a sword
>> module.  The OSIS form is based upon example set in kjvxml.zip
>> The header looks as follows:
>>
>> -=-=- HEAD -=-=-
>> 
>> http://www.bibletechnologies.net/2003/OSIS/namespace";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace
>> http://www.bibletechnologies.net/osisCore.2.1.1.xsd";>
>> > xml:lang="iu">
>>
>>  
>>  
>>  Inuktitut Version
>>  Bible.IUV
>>  Gen-Rev
>>  Bible.KJV
>>  
>>  
>>  Bible.KJV
>>  
>>  
>>  
>> -=-=- HEAD -=-=-
>>
>> John 3:16 looks as follows:
>>
>> ᑍᒫᒃ ᑕᕝᕙ ᒎᑎᐅᑉ
>> ᓯᓚᖅᔪᐊᕐᖕᒥᐅᑦ ᓇᒡᓕᒋᕔᑦ ᐃᕐᖕᓂᑐᐊᓂ ᑐᓂᖕᒪᒍ, ᓇᓪᓕᐊᑦ ᑖᑦᓱᒧᖓ ᐅᒃᐱᖅᑐᖅ ᐊᓯᐅᖁᓇᒍ ᓄᖑᓱᐃᑦᑐᒥᒡᓕ
>> ᐃᓅᓯᖃᖁᓪᓗᒍ. 
>>
>> Here's the iuv.conf file:
>>
>> [IUV]
>> DataPath=./modules/texts/ztext/iuv/
>> ModDrv=zText
>> Encoding=UTF-8
>> BlockType=BOOK
>> CompressType=ZIP
>> SourceType=OSIS
>> Lang=iu
>> GlobalOptionFilter=OSISFootnotes
>> GlobalOptionFilter=OSISHeadings
>> MinimumVersion=1.6.0
>> SwordVersionDate=2009-05-29
>> Version=1.0
>> Description= Inuktitut Version
>> LCSH=Bible. Inuktitut.
>> DistributionLicense=Not for distribution (yet).
>> InstallSize=3858243
>>
>>
>> You get the idea.
>>
>> I've not be able to get it to show up in Bibletime, Xiphos, etc.  I
>> know how to install Sword modules (I've done lots).  I have it
>> compiling (only a few errors, mostly warnings and info):
>>
>> You are running osis2mod: $Rev: 2708 $
>> INFO(WRITE): Appending entry: Mark.16.9: > subType="x-preverse" sID="pv10698"/>> scope="Mark.16.9!)-Mark.16.10!)" type="majorSection"/>
>> ᐊᒡᓚᒃᓯᒪᔪᑐᕾᑦ ᐊᓯᖏᑦ ᐅᑯᓂᖓ ᐃᓚᔭᐅᒃᑲᓐᓂᖅᓯᒪᕗᑦ > type="paragraph"/> > eID="pv10698"/>[ᑕᕝᕙ ᐊᕐᖕᓁᑦ ᐲᑦᑐᕉᓯᒧᐊᖅᐳᑦ ᐃᓚᓐᓇᕆᔭᖏᓐᓄᓪᓗ, ᐅᖃᖅᐳᓪᓗ ᓁᑦᑐᒥᒃ
>> ᐅᖃᐅᑦᔭᐅᑦᔪᑎᒋᖅᑲᐅᔭᒥᖕᓂᒃ.
>> INFO(WRITE): Appending entry: Mark.16.10: ᑕᒪᑐᒪᓕ ᑭᖑᓂᖓᒍᑦ, ᔩᓱᓯ ᓇᖕᒥᓂᖅ
>> ᑎᓕᓯᓚᐅᖅᐳᖅ ᐃᓕᓐᓂᐊᖅᑎᒥᓂᒃ ᓯᕿᓂᐅᑉ ᓄᐃᕕᐊᓂᑦ ᓯᕿᓂᐅᑉ ᓂᐱᕕᐊᓄᑦ ᑎᑭᓪᓗᑎᒃ. ᑕᒪᑐᒥᖓ ᐅᖃᐅᓯᖃᖅᓗᑎᒃ
>> ᐃᔨᖅᓯᒪᓚᐅᖅᑐᒥᒃ ᐃᓅᓯᖃᕐᖕᓇᖅᑐᒥᒃ ᐱᐅᓕᔭᐅᓂᕐᖕᒥᒡᓗ ᐃᓱᖃᖏᑦᑐᒧᑦ.]> type="source">16:10ᐃᓚᖏᑦ ᐊᒡᓚᒃᓯᒪᔪᑐᖃᕕᓃᑦ ᐋᖅᑭᒃᓱᖅᑕᐅᕙᒃᑐᕕᓃᓪᓗ
>> ᐊᒡᓚᑐᕾᑦ ᓁᓐᓂᖅᓴᐅᖕᒪᑕ, ᐃᓚᖏᓪᓗ ᑕᑭᓂᖅᓴᐅᓪᓗᑎᒃ ᑕᕝᕙᓐᖓᑦ ᕚᓯᖓ 9-ᒥᑦ–20-ᒧᑦ
>> ᐃᓚᓯᒪᓪᓗᑎᒃ  > eID="gen23373" scope="Mark.16.9!)-Mark.16.10!)" type="majorSection"/>
>> 
>> WARNING(NESTING): verse Acts.15.23 is not well formed:(46,48)
>> INFO(V11N): Jude is not in the KJV versification. Appending content to
>> 3John.1.14
>> INFO(WRITE): Appending entry: 3John.1.14: > subType="x-preverse" sID="pv12443"/>> type="paragraph"/> > eID="pv12443"/>ᓮᒻᒪᓂᐅᑉ ᐃᓚᒋᓕᑎᑦ. ᐃᓚᓐᓇᕆᔭᑦᑎᓐᓂᑦ ᑕᕝᕙᐅᕗᑏᖅᑕᐅᕗᑎᑦ. ᓇᖕᒥᓂᖅᓗ
>> ᐃᓚᓐᓇᕆᔭᕗᑦ ᑕᕝᕙᐅᕗᑏᖅᐸᕗᑦ ᑍᑲᓃᑦᑐᑦ. 
>> 
>> 
>> SUCCESS: /usr/local/bin/osis2mod: has finished its work and will now rest
>>
>> Yet I still can't it show up in my modules list.  I think this is a
>> language issue.  I've tried changing language to iu_CA ... i.e.
>> xml:lang="iu" (as well as in conf file).
>>
>> Any ideas why I'm not seeing it show up?  What must I do to get the IU
>> language recognized?
>>
>> ~Andrew
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ESV title filter failure

[Andrew Thule]

Just curious, how are you breaking this down so nicely into the Entry
Attributes?  Do you have a script or something that helps you look at
nesting, and xml parsing?

~Andrew

On Fri, Jun 22, 2012 at 3:12 AM, Peter von Kaehne  wrote:
> On Thu, 2012-06-21 at 19:22 -0400, Karl Kleinpaste wrote:
>> diatheke -b ESV -o fmhncvalsbx -k 'mark 16:9'
>
> peter@AOA110:~/Source/sword/examples/cmdline$ diatheke -b ESV -o
> fmhncvalsbx -k 'mark 16:9'
> Mark 16:9: [Some of the earliest manuscripts do not include 16:9-20.]
> []
> Jesus Appears to Mary Magdalene[Some of the earliest manuscripts do not
> include 16:9-20.] []
> Jesus Appears to Mary Magdalene
> [[Now when he rose early on the first day of the week, he appeared first
> to Mary Magdalene, from whom he had cast out seven demons.
> (ESV)
> peter@AOA110:~/Source/sword/examples/cmdline$ ./lookup ESV "Mark 16.9"
> ==Raw=Entry===
> Mark 16:9:
> [Some of the earliest manuscripts do not
> include 16:9-20.] osisRef="Mark.16.9" type="variant">Some manuscripts end the book with
> 16:8; others include verses 9-20 immediately after verse 8. A few
> manuscripts insert additional material after verse 14; one Latin
> manuscript adds after verse 8 the following: But they
> reported briefly to Peter and those with him all that they had been
> told. And after this, Jesus himself sent out by means of them, from east
> to west, the sacred and imperishable proclamation of eternal
> salvation. Other manuscripts include this same wording after verse
> 8, then continue with verses 9-20 subType="x-preverse" type="section">Jesus Appears to Mary
> Magdalene[[Now when he rose early on the first day of the week,
>  type="crossReference">John
> 20:14; [Matt.
> 28:9]he appeared first to  osisID="Mark.16.9!crossReference.g" osisRef="Mark.16.9"
> type="crossReference">Luke
> 8:2Mary Magdalene,  osisRef="Luke.8.2">Luke 8:2from whom he had cast out
> seven demons.
> ==Render=Entry
> .divineName {   font-variant: small-caps; 
>   }   .wordsOfJesus { color:
> red;}
> [Some of the earliest manuscripts do not include 16:9-20.]Jesus
> Appears to Mary Magdalene[Some of the earliest manuscripts do not
> include 16:9-20.]Jesus Appears to Mary Magdalene[[Now when
> he rose early on the first day of the week, he appeared first to Mary
> Magdalene, from whom he had cast out seven demons.
> ==
> Entry Attributes:
>
> [ Footnote ]
> [ 1 ]
> body = Some manuscripts end the book with 16:8; others 
> include verses
> 9-20 immediately after verse 8. A few manuscripts insert additional
> material after verse 14; one Latin manuscript adds after verse 8 the
> following: But they reported briefly to Peter and
> those with him all that they had been told. And after this, Jesus
> himself sent out by means of them, from east to west, the sacred and
> imperishable proclamation of eternal salvation. Other manuscripts
> include this same wording after verse 8, then continue with verses 9-20
> n = 1
> osisID = Mark.16.9!note.1
> osisRef = Mark.16.9
> type = variant
> [ 2 ]
> body = John 20:14;
> [Matt. 28:9]
> n = f
> osisID = Mark.16.9!crossReference.f
> osisRef = Mark.16.9
> refList = John.20.14; Matt.28.9
> type = crossReference
> [ 3 ]
> body = Luke 8:2
> n = g
> osisID = Mark.16.9!crossReference.g
> osisRef = Mark.16.9
> refList = Luke.8.2
> type = crossReference
> [ 4 ]
> body = Luke 8:2
> n = g
> osisID = Mark.16.9!crossReference.g
> osisRef = Mark.16.9
> refList = Luke.8.2
> type = crossReference
> [ Heading ]
> [ 0 ]
> type = x-textual-note
> [ 1 ]
> type = x-textual-note
> [ Interverse ]
> 0 = [Some of the earliest manuscripts do not include 16:9-20.]
> 1 = [Some of the earliest manuscripts do not include
> 16:9-20.]Jesus
> Appears to Mary Magdalene
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Changes to Existing Modules: How do I ..?

[Andrew Thule]

I've independently compiled a list of OT quotes in the NT, including
direct quotes, allusions, and possible allusions.  I did this from
lists available at a number of academic site.  Since not all sites are
of equal worth or of equal accuracy, I've validated each quote
manually (comparing OT to NT).

I've found a number of direct quotes missing from the OTPassages
module, and would like to 'update it' or improve upon it by ensuring
its completeness. If so, how do I go about this (procedurally).  Can I
just submit an updated OSIS file to this list for consideration, or
how does one go about obtaining permission to updating existing
modules?

~Andrew

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Changes to Existing Modules: How do I ..?

[Andrew Thule]

Thanks.  As OSIS files I assume?

On Tue, Jul 17, 2012 at 8:09 PM, Chris Little  wrote:
> Hi Andrew,
>
> Module submissions, including updates, may be sent to modu...@crosswire.org
>
> --Chris
>
>
> On 7/17/2012 9:39 AM, Andrew Thule wrote:
>>
>> I've independently compiled a list of OT quotes in the NT, including
>> direct quotes, allusions, and possible allusions.  I did this from
>> lists available at a number of academic site.  Since not all sites are
>> of equal worth or of equal accuracy, I've validated each quote
>> manually (comparing OT to NT).
>>
>> I've found a number of direct quotes missing from the OTPassages
>> module, and would like to 'update it' or improve upon it by ensuring
>> its completeness. If so, how do I go about this (procedurally).  Can I
>> just submit an updated OSIS file to this list for consideration, or
>> how does one go about obtaining permission to updating existing
>> modules?
>>
>> ~Andrew
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Changes to Existing Modules: How do I ..?

[Andrew Thule]

Thanks David.  I appreciate your module quite a bit, and want to
contribute to it by adding some references I've found in addition to
the ones you've noted.

I'll submit once I've generated a new version of the file (which I'm
working on now)

~Andrew

On Tue, Jul 17, 2012 at 9:03 PM, David Troidl  wrote:
> Hi Andrew,
>
> I submitted the original data.  I'd be happy to see improvements.  According
> to the module making page:
> When you feel your module is ready to be submitted, you may email it to
> modu...@crosswire.org.
>
> Peace,
>
> David
>
>
> On 7/17/2012 12:39 PM, Andrew Thule wrote:
>
> I've independently compiled a list of OT quotes in the NT, including
> direct quotes, allusions, and possible allusions.  I did this from
> lists available at a number of academic site.  Since not all sites are
> of equal worth or of equal accuracy, I've validated each quote
> manually (comparing OT to NT).
>
> I've found a number of direct quotes missing from the OTPassages
> module, and would like to 'update it' or improve upon it by ensuring
> its completeness. If so, how do I go about this (procedurally).  Can I
> just submit an updated OSIS file to this list for consideration, or
> how does one go about obtaining permission to updating existing
> modules?
>
> ~Andrew
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Question about use of note elements

[Andrew Thule]

One benefit of having markup is that rendering mark-up is left to the
client.  Even so, I'm looking at notes in Xiphos, Bibletime and
Alkitab and each treats them slightly different ways.

For example the following note 8:15 is rendered in:
Xiphos as superscript link "*n%2B" (with contents of the note treated
as footnote)
Bibletime as hover link "+" (with the contents of the note in a window
to the left of the main text)
Alkitab as superscript flat text as "+" (with the contents of the note
visible in a column to the left of the main text)

Of the three the Alkitab approach seems to be most in line with what
the OSIS manual says (about keeping notes inline).  The Xiphos
behavior complete perplexes me - how is *n%2B constructed?  If a
superscript is going to be generated, how can I influence that in the
module?

This note with out a reference  the light from…:
Heb. between the light and between the darkness is rendered in:
Xiphos as superscript link "*n2" (with contents of the note treated as footnote)
Bibletime as hover link * (with the contents of the note in a window
to the left of the main text)
Alkitab as a superscript 'a' (with the contents of the note visible in
a column to the left of the main text)

The OSIS2 Manual says a little about notes on page 44 section 8.3 but
points out that notes are not sharply defined.  Certainly the
treatment of them by clients reflects this.  So this raises a question
for OSIS module developers: Doesn't this represent somewhat of a
weakness with the OSIS standard?  What exceptions can we have with
respect to notes containing other elements, for example references
with in notes? Doesn't it seems the module developer is at the mercy
of client program a bit too much because of something of a lack of
clarity on the part of the standard?

~Andrew

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Question about Module Names, conf files, OSIS.xml (and fonts)

[Andrew Thule]

This isn't quit an OSIS question, but it is a Sword Module Question.

I've been working on an Inuktitut Sword Module, and been having some
font/rendering issues, most of which are now solved - but not all.
The last and final 'font' issue seems to be related to how a module is
represented in client software and where it seems to derive the
information from that it uses (I'm talking about the .conf files).

My ink.conf file is listed at bottom of email.

Xiphos behavior:
In the left pane in Xiphos I get:
Biblical Texts -> 'UTF8 missing font filler' (for language name)  ->
INK:Inuktitut Bible in Eastern Arctic Inuktitut

So Xiphos seems to be taking [Module Name]:Description.  I assume the
module name is coming from the .conf file though it could be coming
from osisWork="INK" tag.

For language I'm not sure if it's reading Lang=iu from the conf file
or xml:lang="iu" from the OSIS itself.  The 639-1 code for Inuktitut
is 'iu' according to:
http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes

BibleTime
In the left pane in BibleTIme I get:
Bibles -> iu -> INK

So Bibletime seems to be using either  xml:lang="iu" from the OSIS or
Lang=iu from the .conf file and Module Name from either the osisWork=
tag or the [ModuleName] in the conf file.  (I'm guessing the .conf
file though I could actually test this)

Alkitab
In the left pane in Alkitab I get:
Biblical Texts -> Inuktitut -> INK - Inuktitut Bible in Eastern Arctic Inuktitut

So Alkitab seems to behave similar to Xiphos, excepts gets the English
representation of the language rather than 'UTF8 missing font filler'

Is use of Sword .conf files outline anywhere for developers, besides:
http://www.crosswire.org/wiki/DevTools:conf_Files

I would specifically like to fix the Xiphos font rendering problem for
the module language name, but more generally would like to better
understand where the .conf influences the client verses where the OSIS
tags do.

[INK]
DataPath=./modules/texts/ztext/ink/
ModDrv=zText
BlockType=BOOK
CompressType=ZIP
SwordVersionDate=2010-10-18
SourceType=OSIS
GlobalOptionFilter=OSISFootnotes
GlobalOptionFilter=OSISScripRef
GlobalOptionFilter=OSISHeadings
GlobalOptionFilter=OSISRedLetterWords
OSISqToTick=false
MinimumVersion=1.6.0
Version=0.0.2
History_0.0.2=Changes to the conf file and fixes to specific tags such as notes
History_0.0.1=First working release
History_0.0=First release
Lang=iu
Description=Inuktitut Bible in Eastern Arctic Inuktitut
DistributionLicense=Copyrighted (c)Canadian Bible Society 2012;
permission must be obtained from the copyright holder.
LCSH=defaultReferenceScheme.English
TextSource=WWBS
Encoding=UTF-8
ShortCopyright=Eastern Arctic Inuktitut, (c)Canadian Bible Society 2012
ShortPromo=http://http://www.biblesociety.ca/";>Learn more
about the Canadian Bible Society.
About=This is the Inuktitut Bible (INK) in Eastern Arctic Inuktitut,
(c)Canadian Bible Society 2012
InstallSize=2643238

~Andrew

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Question about use of note elements

[Andrew Thule]

Karl, Chris, thanks for your responses.

Karl I appreciate your comments because you have removed some of the
mystique of Xiphos' behavior; which I appreciate.  My tool of choice
for personal bible work happens to be Xiphos (which I wish I could get
working in OSX sometimes).  I run it in a VM from Linux (on OSX).

I generally like OSIS because I'm most familiar with it.  As far as I
can tell though it seems static.  I'm not that familiar with ThML.
With respect to Xiphos development, I hope the *n and *x are
eventually scrapped in favour of n="ABCD".  That seems to make sense
to me, and puts influence of superscript presentation somewhat back in
the hands of the module developer.

Chris, the '%2B' is a bug then.  Is there a bug submission process for
Xiphos I can poke?
As far as notes being in line, that isn't actually my preference.  My
preference presentation-wise, if truth be know, I also the Alkitab
method; same windows, off to the side as a column (with nice font and
background to boot).  Having said that, with modules such as NETnotes
it's awful - the notes dominate the bottom of the frame where the
notes exceed the biblical content.  In that sense the Xiphos /
Bibletime approach seem more pragmatic.

However, this idea of in line notes was from the OSIS Manual which
says "It is customary to include the notes directly within the text,
at the point to which they apply", so I was trying not to fight the
standard in my understanding - go with the flow type of deal.  I don't
think module developers should influence note placement, even if I
think they should be able to influence presentation of 'note markers'
such as superscripts.

With respect to having a specific need, I don't think I do as long as
I understand more or less how each client treats notes (slightly)
differently, in denoting and presenting them.  I will likely have to
revisit when it appropriate to use notes and when to do
cross-references.

~Andrew



On Fri, Jul 20, 2012 at 3:07 PM, Chris Little  wrote:
> On 07/20/2012 11:06 AM, Andrew Thule wrote:
>>
>> One benefit of having markup is that rendering mark-up is left to the
>> client.  Even so, I'm looking at notes in Xiphos, Bibletime and
>> Alkitab and each treats them slightly different ways.
>>
>> For example the following note > type="source">8:15 is rendered in:
>> Xiphos as superscript link "*n%2B" (with contents of the note treated
>> as footnote)
>> Bibletime as hover link "+" (with the contents of the note in a window
>> to the left of the main text)
>> Alkitab as superscript flat text as "+" (with the contents of the note
>> visible in a column to the left of the main text)
>>
>> Of the three the Alkitab approach seems to be most in line with what
>> the OSIS manual says (about keeping notes inline).  The Xiphos
>> behavior complete perplexes me - how is *n%2B constructed?  If a
>> superscript is going to be generated, how can I influence that in the
>> module?
>
>
> If Xiphos is really rendering '%2B' instead of '+', then this is a bug. For
> some reason, the URL-encoded character is being rendered, rather than the
> intended '*n+'
>
> I don't know why you suggest that the notes should be inline, since you're
> not specifying the note placement in your example. The manual doesn't say
> notes should be rendered inline, just that they are encoded inline.
>
> In general, I would guess that every Sword front end will ignore the
> placement attribute anyway, in favor of its default note placement location.
> But I would also guess that no one has ever used the placement attribute in
> a Sword module.
>
>
>> This note with out a reference  the light from…:
>> Heb. between the light and between the darkness is rendered in:
>> Xiphos as superscript link "*n2" (with contents of the note treated as
>> footnote)
>> Bibletime as hover link * (with the contents of the note in a window
>> to the left of the main text)
>> Alkitab as a superscript 'a' (with the contents of the note visible in
>> a column to the left of the main text)
>
>
> My (personal) preference would be the Alkitab method, but none of these are
> incorrect since your example does not identify what the footnote marker
> should be, leaving it to the application to do its default.
>
>
>> The OSIS2 Manual says a little about notes on page 44 section 8.3 but
>> points out that notes are not sharply defined.  Certainly the
>> treatment of them by clients reflects this.  So this raises a question
>> for OSIS module developers: Doesn't this represent somewhat of a
>> weakness w

Re: [sword-devel] Question about Module Names, conf files, OSIS.xml (and fonts)

[Andrew Thule]

Chris thanks for your reply.

>> So Inuktitut is in Alkitab's database, where it was missing from Xiphos' (or 
>> there was some other problem there).

It doesn't seem to be completely so.  Xiphos renders Inuktitut
properly in the bible window and gives you the ability to expressly
choose fonts for bible rendering.  In the left pane (module window)
however the same is not true.  This problem isn't even typically of
all Xiphos instances.  In Linux the font renders properly as an
Inuktitut descriptor just as Kloine Greek and Hebrew do - however in
Windows it isn't so.  As far as I can tell it can't find the proper
font for UTF8 in the 'module window' whereas it can in the bible
window.  Font settings also only seem to affect one and not the other.
I can send a screen shot if anyone cares to see (or the OSIS text for
Inuktitut for testing purposes only).

Also thanks for pointing out errors in the .conf file, fixed and very
much appreciated.


On Fri, Jul 20, 2012 at 3:24 PM, Chris Little  wrote:
> On 07/20/2012 11:43 AM, Andrew Thule wrote:
>>
>> This isn't quit an OSIS question, but it is a Sword Module Question.
>>
>> I've been working on an Inuktitut Sword Module, and been having some
>> font/rendering issues, most of which are now solved - but not all.
>> The last and final 'font' issue seems to be related to how a module is
>> represented in client software and where it seems to derive the
>> information from that it uses (I'm talking about the .conf files).
>>
>> My ink.conf file is listed at bottom of email.
>>
>> Xiphos behavior:
>> In the left pane in Xiphos I get:
>> Biblical Texts -> 'UTF8 missing font filler' (for language name)  ->
>> INK:Inuktitut Bible in Eastern Arctic Inuktitut
>>
>> So Xiphos seems to be taking [Module Name]:Description.  I assume the
>> module name is coming from the .conf file though it could be coming
>> from osisWork="INK" tag.
>
>
> It comes from the module name. Sword discards the osisWork value.
>
>
>> For language I'm not sure if it's reading Lang=iu from the conf file
>> or xml:lang="iu" from the OSIS itself.  The 639-1 code for Inuktitut
>> is 'iu' according to:
>> http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
>>
>> BibleTime
>> In the left pane in BibleTIme I get:
>> Bibles -> iu -> INK
>>
>> So Bibletime seems to be using either  xml:lang="iu" from the OSIS or
>> Lang=iu from the .conf file and Module Name from either the osisWork=
>> tag or the [ModuleName] in the conf file.  (I'm guessing the .conf
>> file though I could actually test this)
>
>
> The BCP 47 tag (iu) comes from the Lang=iu line in the .conf file. Sword
> also discards the xml:lang value. INK comes from the module name.
>
>
>> Alkitab
>> In the left pane in Alkitab I get:
>> Biblical Texts -> Inuktitut -> INK - Inuktitut Bible in Eastern Arctic
>> Inuktitut
>>
>> So Alkitab seems to behave similar to Xiphos, excepts gets the English
>> representation of the language rather than 'UTF8 missing font filler'
>
>
> So Inuktitut is in Alkitab's database, where it was missing from Xiphos' (or
> there was some other problem there).
>
>
>> Is use of Sword .conf files outline anywhere for developers, besides:
>> http://www.crosswire.org/wiki/DevTools:conf_Files
>
>
> No, just there. Is there something lacking?
>
>
>> I would specifically like to fix the Xiphos font rendering problem for
>> the module language name, but more generally would like to better
>> understand where the .conf influences the client verses where the OSIS
>> tags do.
>
>
> OSIS doesn't directly affect anything, but it's expected that the module
> maker will copy the values from the OSIS doc to the .conf file.
>
> Some errors in your .conf file:
>
>
>> DistributionLicense=Copyrighted (c)Canadian Bible Society 2012;
>> permission must be obtained from the copyright holder.
>
>
> The above line is invalid. There are other attributes that can contain
> copyright holder data. Exactly the following DistributionLicense values are
> permitted:
>
> Public Domain
> Copyrighted
> Copyrighted; Permission to distribute granted to CrossWire
> Copyrighted; Free non-commercial distribution
> Copyrighted; Freely distributable
> Copyrighted; Permission granted to distribute non-commercially in SWORD
> format
> GFDL
> GPL
> Creative Commons: by-nc-nd
> Creative Commons: by-nc-sa
> Creative Commons: by-nc
> Creative Commons: by-nd
>

Re: [sword-devel] Question about Module Names, conf files, OSIS.xml (and fonts)

[Andrew Thule]

Karl, fonts 'appear' rendered differently in the main window (large
upper right where bible text appears) and not rendered at all (in
windows) in the pane immediately to the left (upper left above the
previewer pane), which I understand (perhaps incorrectly) pulls some
info from the .conf file.

In the 'module pane' upper left where you select modules, the
Inuktitut font is not being found/rendered.  I'm getting those obtuse
UTF8 boxes you get when fonts appear to be missing.

I can send you a screen shot if you want.

~Andrew

On Fri, Jul 20, 2012 at 4:48 PM, Karl Kleinpaste  wrote:
> Andrew Thule  writes:
>> Xiphos renders Inuktitut properly in the bible window and gives you
>> the ability to expressly choose fonts for bible rendering.  In the
>> left pane (module window) however the same is not true.
>
> I don't understand the distinction you're making between "the bible
> window" and "the module window."  All content is from a module, some of
> which are bibles.
>
> Or are you referring to the previewer, typically left-bottom pane?
>
>> As far as I can tell it can't find the proper font for UTF8 in the
>> 'module window' whereas it can in the bible window.  Font settings
>> also only seem to affect one and not the other.  I can send a screen
>> shot if anyone cares to see.
>
> If you do mean the previewer...  It's just another pane.  It is filled
> in nearly identical fashion to any other pane, using a font
> specification taken from the module whose content is to be presented
> there.  The font is knocked down one size, to reflect print-style
> footnote appearance, but other than that the content to be presented
> there (footnote text, or whatever else) is presented the same way as if
> it were in the normal pane where the module appears.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Question about use of note elements

[Andrew Thule]

>>Also, typically notes of this sort are labelled by letters or digits.  Is
>>there a reason why you're using non-alphanumerics?

I didn't realize there was a restriction on using non-alphanumerics.
I was also tempted to try "†".  I will dig into the standard to
conform to it, but no - no reason in particular - just a convenience
to try and make the note marker behaviour in Xiphos act like the other
two browsers (but now I understand why this is not so).

~Andrew

On Fri, Jul 20, 2012 at 4:42 PM, Karl Kleinpaste  wrote:
> Andrew Thule  writes:
>> Xiphos (which I wish I could get working in OSX sometimes).  I run it
>> in a VM from Linux (on OSX).
>
> Find us someone willing to put in the work to produce a Mac package.
> The build has been done before, but not in a manner representing a
> complete, install-ready package.  We've been asking, but no one has been
> willing to step up to take on the task.
>
> Check footnote 4 here:
> http://crosswire.org/wiki/Choosing_a_SWORD_program#Operating_Systems_and_Portability
>
>> I generally like OSIS because I'm most familiar with it.  As far as I
>> can tell though it seems static.  I'm not that familiar with ThML.
>
> ThML can be thought of as "HTML plus goodies," namely ,
> , , and variants.  However, ThML is not considered the
> proper, sufficiently modern method for module encoding today.  There are
> a few sticks in the mud like myself who persist with it.
>
>> Chris, the '%2B' is a bug then.  Is there a bug submission process for
>> Xiphos I can poke?
>
> If it were a Xiphos bug, from the menubar: Help -> Report Bug.
>
> But I don't perceive this as a Xiphos bug.  I believe the engine filter
> is where the mistake has occurred.  I don't understand why the '+'
> character would be interpreted to its %2B hex equivalent.
>
> Also, typically notes of this sort are labeled by letters or digits.  Is
> there a reason why you're using non-alphanumerics?
>
>> Having said that, with modules such as NETnotes it's awful - the notes
>> dominate the bottom of the frame where the notes exceed the biblical
>> content.  In that sense the Xiphos / Bibletime approach seem more
>> pragmatic.
>
> The longest footnotes in NET are at Ecc 1:1 and Song 5:4.  Having that
> volume of text as a footnote is absurd to me.  That's why it's good that
> the notes are a separate commentary-style module.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Question about Module Names, conf files, OSIS.xml (and fonts)

[Andrew Thule]

Yes, Xiphos in Linux is perfect.

On Friday, July 20, 2012, Karl Kleinpaste wrote:

> Andrew Thule > writes:
> > Karl, fonts 'appear' rendered differently in the main window (large
> > upper right where bible text appears) and not rendered at all (in
> > windows) in the pane immediately to the left (upper left above the
> > previewer pane), which I understand (perhaps incorrectly) pulls some
> > info from the .conf file.
> >
> > In the 'module pane' upper left where you select modules, the
> > Inuktitut font is not being found/rendered.  I'm getting those obtuse
> > UTF8 boxes you get when fonts appear to be missing.
>
> Oh, that.  Now I understand.  You mean the language names in the module
> selection tree itself.
>
> Yes, Inuktitut is a problematic font.
>
> This is a Windows-centric problem.  We have no knowledge of where
> Windows as a whole, or GTK-under-Windows (one of the several display
> toolkits Xiphos must use), finds its idea of default application font.
> Surprisingly to me, Windows seems the most crippled as to font awareness
> when compared to any UNIX or Linux system, which invariably in my
> experience are perfectly capable of handling such fonts.  When my Linux
> system first wants to display a new font, GTK-driven programs pop a
> dialog to ask if they should go hunt it down.  If someone knows how to
> handle such problems in Windows, I'm sure we'd all appreciate the
> education.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Question about use of note elements

[Andrew Thule]

Confusion comes from POSIX's permissive approach to basename/dirname.
POSIX.1-2001 suggests something to the effect that the trailing slash
denotes where the dirname ends and the basename begins (which is
unfortunately in my opinion)

For example if you look at basename/dirname (which conforms to POSIX.1-2001)
#include 
char *dirname(char *path);
char *basename(char *path);

Here's how the path breaks down:
path dirnamebasename
"/usr/lib""/usr""lib"
"/usr/"   "/"   "usr"
"usr" "."   "usr"
"/"   "/"   "/"

In my opinion, it would have been more useful NOT to differentiate
between basename and dirname but between path and file; where basename
is always fully specified (same as path except with trailing '/'
mandatory) and file is some element of basename.

The reason POSIX when this way is because it supports fully specified
pathnames and relative pathnames, and didn't think through ambiguity
caused by allowing for multiple syntaxes.

A path should always end in a slash (in my opinion).  Perhaps such a
rule can be incorporated in .conf syntax in upcoming major revisions
of the Sword lib - then you wouldn't have to check for it.

~Andrew

On Fri, Jul 20, 2012 at 5:14 PM, Chris Little  wrote:
> On 07/20/2012 12:48 PM, Andrew Thule wrote:
>>
>> However, this idea of in line notes was from the OSIS Manual which
>> says "It is customary to include the notes directly within the text,
>> at the point to which they apply", so I was trying not to fight the
>> standard in my understanding - go with the flow type of deal.  I don't
>> think module developers should influence note placement, even if I
>> think they should be able to influence presentation of 'note markers'
>> such as superscripts.
>
>
> I see. What the OSIS manual is referring to is encoding the notes inline. So
> you put the whole note within the XML document at the location where it
> logically occurs (or where you want the footnote marker to be).
>
> Where it is rendered is determined by the application. In theory, we could
> obey the placement attribute, which has values like 'inline', 'foot', and
> 'right', to determine where to place the footnote text itself in the
> rendered document. But, personally, I see those as pertaining primarily to
> printed works, so I'm quite satisfied to leave placement decisions to the
> application author. As an end-user, I prefer the practice of rendering note
> text in a separate window, as in Xiphos & PocketSword, among others.
>
>
> --Chris
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Question about use of note elements

[Andrew Thule]

Nic say:
"Also, it was rather trivial to get Xiphos working native under X11 on
a Mac, so that may be a lot easier than running it under a VM on a
Mac?"

You could be right, however I run the VM for other reasons.  I need
the tools 'Backtrack Linux' so nicely wraps together (day job requires
penetration tests tools and skills) so its no bother.

That said, if you can direct me to a link with some hints on building
it for X11 in OSX - I'd certainly give it a go and be appreciative.

~Andrew



On Fri, Jul 20, 2012 at 8:18 PM, Nic Carter  wrote:
>
> On 21/07/2012, at 6:42, Karl Kleinpaste  wrote:
>
>> Find us someone willing to put in the work to produce a Mac package.
>> The build has been done before, but not in a manner representing a
>> complete, install-ready package.  We've been asking, but no one has been
>> willing to step up to take on the task.
>
> FWIW, I spent half or a whole day looking into this a few months ago. It is 
> non-trivial and requires an understanding of the packaging systems that are 
> needed to get gtk across to OS X. Also, that previous work was done almost 3 
> years ago and the main project that was mentioned on that blog is no longer 
> being maintained. Jhbuild appears to still be the way to go but after 
> spending all that time on it I needed to let it go, as my free time was then 
> all used up. I may be willing to have another go later this year when the 
> migration to WebKit has been completed and you have removed several 
> dependencies from older libraries that you seemed to be in the process of 
> doing (& may have already done?)...
> Also, it was rather trivial to get Xiphos working native under X11 on a Mac, 
> so that may be a lot easier than running it under a VM on a Mac?  :) Of 
> course, ideally we want Xiphos as a native app  without the requirements of 
> running X11 However, for me the main desire for Xiphos on a Mac is to 
> be testing PS rendering and comparing it to Xiphos & MacSword & our web-based 
> interface & is not something I am able to be devoting much time to right now. 
> :(
>
> Thanks, ybic
> nic... :)
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Words of Christ tools

[Andrew Thule]

I am now at a stage where I have a non-English bible (Inuktitut) in nearly
valid Osis ( I say nearly because it still generates three 'not well
formed' warnings that I just haven't been able to figure out), and I'd like
to add markup to denote Words of Christ.

I have other valid osis modules that I can consult manually to enumerate
these verses but this is time consuming.  Are there any automated tools
that either generate verse lists that should contain 'Christ's words'
markup, or that don't but should'?

Though this module is in Inuktitut all quotations are denoted with "
characters, but not markup ( i.e ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

[Andrew Thule]

Last time this issue came up, it was made very clear that surrounding
the issue of FTP mirrors were sensitivities around the distribution of
Sword modules because of licensing encumbrances.  So this purpose of
this email is seek clarification about this given that InstallMgr
appears to be moving in a direct that may support multiple module
locations.

When Crosswire obtains license to distribute texts as Sword modules,
is there an explicit prohibition that precludes Crosswire from
distributing its modules in a distributed manner (because of policy
decisions, load-balancing issues, whatever). Specifically, is
Crosswire prohibited from mirroring itself (assuming the mirror is
completely synchronized with the parent site).

Assuming licensing restrictions are there to preserve the integrity of
the text (reasonable constraint), is Crosswire looking to mirror
itself at any point in the future for the sake of increasing the scope
of dissemination for the tools/technology?

Since Crosswire freely allows modules to be downloaded and governs the
use of these modules afterwards through the each modules' licensing
rights, is there something else that precludes their downstream
redistribution so long as the original license is honoured and
preserved?  (In other words, if the licenses is established by the
original module creator, or the license holder for the text, is
Crosswire able to impose additional restrictions on the use of the
text?  Should it (not)?)

Previously, I set up a mirror of all sites with SWORD modules as a
type of one-stop-shop site where I knew the modules were accessible to
locations where Crosswire isn't actually (or isn't advisable).  I was
told to shut it down, and I did - honouring the request.  Even so,
unless there are legal reasons the texts cannot be distributed from
mirrors, or there's been a project decision not to go down this road
(which hasn't been publicly communicated) it would be of great benefit
to provide additional clarify on Rights management.

(Not trying to stir any pots - I recognize the sensitivities - please be gentle)
~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

[Andrew Thule]

Greg, thanks for your response

On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings  wrote:

> I has, since at least the time I started with SWORD in 2004, always
> supported multiple install locations. The only difficulty I'm aware of
> comes with automatic updating if module ABC exists in Repository 1 and
> Repository 2 - currently InstallMgr has no way of knowing which one is
> the source of the currently installed ABC and thus it cannot determine
> from which source an update should be pulled. But it has always
> supported including multiple sources.

How is this the responsibility of InstallMgr?  If Module ABC exists in
two (or more) repositories, and Crosswire has permitted repositories
on the grounds that they be reflective of the main site, does it
matter if InstallMgr gets the module from site X vs site Y?  As far as
IntallMgr is concerned if the module was obtained from Site X it will
always seek updates from Site X.

If the user tries to install from Site Y, InstallMgr should be smart
enough to reinstall from Site Y (you can currently reinstall modules
from the same site), but then associate that module with Site Y,
removing its record in Site X.  The module should always be associated
with the site it was download from (last), should it not?  Likewise it
should always look for updates from the same source subject to be
changed.


> None of the modules I am aware of specify the particular manner in
> which Crosswire must or must not distribute the module. There are
> some, I believe, which limit to only Sword format which we try to
> avoid now as that prevents the creation of GoBible installers for the
> text and so on. However, there are none that currently specify "from
> only the primary www.crosswire.org server" or such.

This is good news (not as good as the Good News Christ gave us, but
good nonetheless.


> I would imagine Crosswire would do so if the issue ever arises that
> the server becomes unreliable (such as happened for a brief time this
> past Spring) or if the bandwidth requirements for modules alone became
> more than the current host provides. However, there are no such plans
> at the moment that have been discussed openly, thus it is safe to
> assume that there are no such plans at present.

I offer to host a mirror (freely) should Crosswire ever decide to do
this. (I currently own a company that hosts other very high bandwidth,
high-availablity sties (sites such as bash.org) so this isn't an idle
offer)


> So long as the license requirements are fulfilled, there is nothing
> preventing redistribution. As I recall, the initial reaction to your
> announcement was not that you must take it down but that you must
> filter those modules which are licensed for only Crosswire's
> distribution. Any modules which are in the Public Domain or which have
> licenses that do not restrict their distribution to e.g. CrossWire
> only, you are free to mirror. However, you would have to manually
> create such a list by inspecting each module's license individually by
> hand.

So mirrors authorized by Crosswire do not qualify as distributed by
Crosswire under 'CrossWire only'? Does that not say that Crosswire
will never distribute 'Crosswire only' modules from any place other
than one central site - unless it develops a process for authorizing
'official mirrors'.  If Crosswire specifically has some process which
grants and revokes official status as a mirror, could that then
redistribute these modules?


> The rights are clearly stated in each module within the official
> CrossWire repositories. Other repositories have their own methods and
> requirements and may or may not include license information. The
> license is there for you to observe and follow for each official CW
> module that you care to mirror. We only ask that you honor the license
> itself within the laws of where you live and host your mirror/cache.
> We also ask, as a project, that you honor the intent of the module
> owner. If the laws where the publisher lives are different from the
> laws where you plan to host the site, we would ask you honor what the
> publisher requires, even if there is no legal way to enforce that
> across international boundaries. We ask this because many of these
> modules are licensed for CrossWire to distribute with the good grace
> of the publisher/translator. None of us and few of them are lawyers,
> so licensing might not be water-tight and iron clad. If we give a
> good-faith attempt to follow intentions instead of the letter of what
> is written then we are more likely to garner good will from future
> publishers and content creators.
>
> --Greg

Agreed.

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

[Andrew Thule]

>> On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings  
>> wrote:

> It should. It does not. AFAIK it currently maintains no status
> information on whether ABC came from site X, site Y, a local install
> file, or was manually inserted into the install location. Since
> modules are just a collection of files on a disk bound together by a
> conf file, there is no way of preventing a user from unzipping a
> module she received in email into the folder. If that module is named
> ABC then InstallMgr will assume it is the same module as ABC from
> source X and offer an upgrade if the local version is less than site
> X's version.

I think it does - here's how I think it does.  In Linux at least, it
seems to track version numbers in the .conf file.  For example, I have
an Inuktitut sword module whose version information is kept locally
here:

~/.sword/InstallMgr/20120224005250/mods.d/ink.conf


The 20120224005250 bit seems to be explained in InstallMgr.conf as
being specific to a particular site.

[General]
PassiveFTP=true

[Sources]

FTPSource=1XO|x.xxx.xxx|/pub/sword/raw|||20120224005250


How I understand this then is that InstallMgr writes information about
modules in the form of .conf files (in my case ink.conf) to the
20120224005250 directory.  If there's a difference between the .conf
file in the 20120224005250 and the .conf file in the site associated
with 20120224005250 it means there's an update.

Thus, when you install from a different source InstallMgr could see
that you have a .conf file for that module (INK for example) (in your
InstallMgr directory or subdirectory) delete it and put the new copy
in a source directory from which it was downloaded establishing a link
between the most recent download and the module.

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

[Andrew Thule]

David, I suspected as much and don't deny the decision to support one
or more installation sites resides with the client developer.  That
said, InstallMgr appears to be moving in that direction, which I think
is a wonderful feature.  I suspect different client developers
influence each other feature-wise.

~A

On Thu, Jul 26, 2012 at 2:23 AM, David Haslam  wrote:
> Andrew,
>
> Not all front-ends use the SWORD-based InstallMgr whose behaviour you just
> observed.
>
> For a start, JSword based front-ends have their own JSword-based module
> manager.
>
> So it would be unfair to generalize from what happens with one SWORD-based
> front-end such as Xiphos.
>
> And, from what I can recall from earlier threads, PocketSword has its own
> install manager,
> even though the front-end itself is based on the SWORD API. No doubt Nic can
> clarify this.
>
> David
>
>
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/Legitimate-FTP-Mirrors-Module-Distribution-Rights-Question-tp4650611p4650621.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

[Andrew Thule]

On Thu, Jul 26, 2012 at 6:53 PM, Karl Kleinpaste  wrote:
> Frankly, I hope not.
>
> The repositories do not represent (as it were) individual bookstores,
> from any of which one might find any given module.  Rather, the repos
> represent individual publishers, and patrons get their modules directly,
> without a middle-man bookstore.

The value in differentiating source repositories is not to establish
'bookstores'.  Rather the value is in being able to support multiple
repositories where there may in fact be a common store of modules also
found elsewhere.  Because there are many modules not representing any
publishers, modules not subject to restrictions in their licenses,
there will be repos with redundant copies of modules.  Because the
number of modules without restriction in their license exceeds the
ones with restrictions, I'm guessing that the they get the greater
degree of consideration. But that raises the question I was alluding
to initially; what is the philosophy behind Crosswire's efforts to
distribute scripture? Is it to have one 'official' source or more?

If the philosophy is to restrict distribution to one 'official'
Crosswire site, other sites will be seen as 'bookstores' (and
competing ones at that).  On the other hand, if the philosophy is to
give the modules the widest possible distribution, two things likely
need to be established - a process by which mirrors become established
as 'official', and support for multiple site management in InstallMgr
(as well as other module distribution methods), in which case
provision for tracking source repos would be a desirable feature.

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Speaking of Fonts (free?) ...

[Andrew Thule]

.. I'm not sure if anyone else has found this treasure trove, but I've
managed to find 58 Free and Open Source Licensed, Unicode Hebrew
Fonts, including ancient ones such as Aramaic and Hebrew Habakkuk.  I
found these free-use fonts at the 'Open Siddur' project site:

http://opensiddur.org/2010/07/unicode-compliant-and-open-source-licensed-hebrew-fonts/

They are a great resources. If you're looking for some nice Hebrew
fonts to include with your software I recommend downloading the font
pack:
http://opensiddur.org/wp-content/uploads/2010/07/Open-Siddur-Project-Hebrew-Font-Pack-1.8.zip

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

[Andrew Thule]

On Sun, Jul 29, 2012 at 7:29 AM, Peter von Kaehne  wrote:
>> I really don't see your point about this.
> To second that - there is essentially no point.

Many publicly available repositories replicate themselves.  (Take
Sourceforge for example).  There are many reason why they do this.
Lower latency in downloads for example, fewer router hops between
client and source download, load balance downloads by distributing
them across multiple sites, reduce available from single point of
failure, and yes even security.  There are places in the world that
filter or monitor sites because of the word 'cross'.  The point should
be obious, suggesting Crosswire consider replicating itself (the site)
and it's module repository has benefits such as no single point of
failure etc - that is unless the chief concern is not text
distribution.

> People who access us from countries which control their internet and
> want to block the Bible, need to be cautious and come through proxies,
> tor or whatever or obtain stuff via CDs, USB sticks etc.

This might be your preference, but should Crosswire really control
it's own module distribution once it makes them available?

> Providing secondary download sources in the hope that they will not be
> observed while our main ones are - this is silly and actually more
> dangerous than going the long way via e.g. tor

Well such a scenario is only one possible benefit.  Tor nodes may also
be filtered (have you ever tried to look at a books.google.com book
through the Tor network for example?)   The benefit of Tor networks is
not that that they get around domain-name restrictions, but that they
get around tracing relationships between client and server.  Likewise,
if someone wanted to monitor access to sword modules (technically)
they would need look at but a single site. But again, this is somewhat
of a tangent.

> The offer is kind, is appreciated, but is essentially one which makes no
> sense to us, increases our opportunity costs and therefore should be
> declined.

No worries.  The goal wasn't to necessarily host a crosswise mirror
(though that was the offer) but to to ask Crosswire's philosophy on
module distribution. I wondered about how to provide maximum
dissemination to Sword modules in my possession not in the main repo,
some of which have not had their distribution rights negotiated.  I'd
like to balance licensing restrictions against broad availability.
Having them at a single site neither distributes risk, and represents
a single point of failure.  Similarly, if the applications of rights
such as "Copyrighted; Permission to distribute granted to CrossWire"
implies that module redistribution becomes restricted to one site only
- that likely shouldn't be the license attached to the module. (On the
other hand if Crosswire asserted it's right to text re-distribution
though through a sanctioned mirror program - I'd have less issue with
it).

> But we have been down this route of discussion already.

As far as I could tell, I was unable to find in the list archives
anywhere Crosswire had clarified that it wished to restrict Sword
module distribution for "Copyrighted; Permission to distribute granted
to CrossWire" modules to itself and control their re-distribution.
You've now answered that question which is good.


> In summary we welcome new volunteers, we are very happy for people to
> scratch their own itches instead of doing only what has been done before
> or following a prescribed programme, but some things simply do not make
> a lot of sense.

I didn't realize seeking clarification was an itch.  The 'proscribed
programme' you speak of wasn't clear.  It is clearer now.


> I am sure you have skills aplenty which could be usefully employed. Your
> bandwith though likely not. At least not in this moment.

Thanks, but this series of questions wasn't about me but about
Crosswire's policy which you've spoken to.

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Speaking of Fonts (free?) ...

[Andrew Thule]

Perfect David.  Quite welcome,

~A

On Sun, Jul 29, 2012 at 4:03 AM, David Haslam  wrote:
> Just listed this in http://crosswire.org/wiki/Fonts#Hebrew
>
> Thanks for the information, Andrew.
>
> David

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Speaking of Fonts (free?) ...

[Andrew Thule]

David, from your post the 'Ezra SIL Hebrew Unicode Font' is a stunning
font also.  I didn't have that one, so downloaded and installed it.  I
think it is similar to the FreeSerif font contained in the Open Siddur
font set though with a bit more aspect to it (more boldlike)

I think for Hebrew at least (at least how Xiphos renders them) the
Ezra SIL is one of the better ones, but i"m still partial to the
FreeSerif font contained in the Open Siddur set. They are both
traditional, and crisp enough beginning readers of Hebrew can readily
recognize them but the FreeSerif is slightly less 'bold' which works
well with the other English fonts.

~A


On Sun, Jul 29, 2012 at 9:21 AM, Andrew Thule  wrote:
> Perfect David.  Quite welcome,
>
> ~A
>
> On Sun, Jul 29, 2012 at 4:03 AM, David Haslam  wrote:
>> Just listed this in http://crosswire.org/wiki/Fonts#Hebrew
>>
>> Thanks for the information, Andrew.
>>
>> David
>
> ~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

[Andrew Thule]

I think the vision of having the module source provider 'contribute'
the module at a site (such as NET coming from crossway) is also a good
one.  That at least means should a single module source be 'shutdown',
others are still available, (even if not containing the module a users
trying to get).  For InstallMgr to support something like this would
be good.

(I spend much time in a heavily mined landlocked South-East Asian
Islamic country where becoming a Christian was punishable by death.
Crosswire was not accessible - and it was a real impediment

How does InstallMgr work when I go to the main Crosswire site and
download a module like KJV (version 2.3) and then update source from
say Crosswire Beta where it sees KJV (version 2.4) and suggests an
update (or is this a Xiphos thing)?

That's very nice 'feature' where it sees the module the same though
the source may be different (I presume by seeing the upgrade to
"Version=" in the .conf file).  Should an install module  software
support multiple sites, it would be very nice to continue recognizing
modules as the same regardless of their source.

~A


On Sun, Jul 29, 2012 at 11:45 AM, Troy A. Griffitts
 wrote:
> Hey guys.  Thanks for everyone speaking on this thread.  Andrew, I do
> appreciate your offer, I sympathize with your single point of failure and
> widest distribution possible points; however, I tend to agree with the
> replies given on this thread.  The primary benefit I see for a mirror would
> be faster downloads.  I'm not sure we have an issue currently.
>
> Technically:
>
> Changing InstallMgr to 'merge' modules from multiple repositories would be
> simple to do.  This is already done for the concept of global modules
> typically located someplace like /usr/share/sword/ and personal modules
> located at ~/.sword/.  The method to call is:
>
> /**
>  * Adds books from a new path to the library
>  * @param path the path in which to search for books
>  * @param multiMod whether or not to keep multiple copies of the
> same book if found in different paths
>  *  default - false, uses last found version of the book
>  */
> virtual void SWMgr::augmentModules(const char *path, bool multiMod =
> false);
>
>
> This would allow a frontend to give a unified list of modules from all
> repositories and would show the latest version available on any repo.  I
> prefer having the repositories separate for the user because it gives a
> certain flavor/theme/endorsement to the modules.  e.g., NET work comes
> directly from bible.org.  Hopefully soon, the ESV will come directly from
> Crossway, and my hope is that this will become a trend.  The Xiphos repo
> hosts brave modules which give newer features, but which might not yet be
> fully tested on all platforms (I hope this is a fair characterization).
>
> The mirror concept is different from this identity separation, I realize,
> but technically, the merging of modules from various mirrors could use the
> same facility.  We would need to tweak the code slightly to add an entry in
> the memory stamp of the loaded .conf to include all the mirrors which
> provide the module, so the frontend could offer a choice to the user and
> then get back to the correct repo to actually request the download, but it
> would be a simple addition and one a frontend could already do easily if
> they wanted to offer such.
>
> Also, technical comment to another item on this thread:
> We do support multiple copies of the same modules, as seen by the final
> parameter of the above method.  The default is false (don't keep multiple
> copies), but this functionality was requested by the Bibletime team a number
> of years ago, and I believe they turn it on by default (or at least they
> used to).  I only saw the benefit for developers, as Karl and David
> mentioned, so I left the default false.
>
> In general, please don't think distribution isn't one of our highest
> priorities.  My entire push to keep the definition of a 'module repository'
> as simple as any installed set of SWORD modules, is fuelled directly from
> that desire-- to technically enable anyone who installs a set a modules, to
> then become a distributor of those modules simply by making their storage
> location available to others.  If I thought sanctioned mirrors would
> legitimately increase Bible distribution, I would endorse the move.
>
> Hope this helps,
>
> Troy
>
>
>
>
>
>
> On 07/29/2012 05:07 PM, Greg Hellings wrote:
>>
>> On Sun, Jul 29, 2012 at 8:20 AM, Andrew Thule  wrote:
>>>
>>> On Sun, Jul 29, 2012 at 7:29 AM, Peter von Kaehne  wrote:
>>>>>
>>>>&

Re: [sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

[Andrew Thule]

On Mon, Jul 30, 2012 at 3:38 AM, Troy A. Griffitts  wrote:
> The final thing I didn't mention were modules like Gill. We've had
> trouble with tracking down a Gill module with a clean pedigree (well, maybe
> 'cleared' pedigree is a better word). Whereas, Xiphos is also braver is this
> regard to challenge legitimate copyright claims.

Troy does this mean that with respect to the modules you host, you go
through the rigamarole  of tracing back to source the copyright status
for the sake of due diligence?  If so, I'm impressed, but have some
off-line questions about validating a text I'm interested in turning
into a sword module. I'd like to know more about establishing a text's
pedigree.

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

[Andrew Thule]

Thanks Peter, I'm not so interested in the motives of those
contributing the modules or the process by which they are vetted.  I
wasn't specifically asking from a Crosswire repo perspective and I
have no doubt these go through a careful filter process.  Rather I'm
more interesting in finding out how I might validate the pedigree of a
translation not currently in the main repo, whose text is (nearly)
publicly available (meaning readily accessible).

I'd be doing the one taking the text, adding mark-up into OSIS, and I
know my own motivation. I don't know how to determine if there are
copyright encumbrances on the translation, and wouldn't necessarily be
submitting the outcome to Crosswire. So, though I suspect there are no
copyright encumbrance because of the age of the translation, I would
still like to be sure. I'd thus like to figure out how to trace this
back for myself.

~A

On Mon, Jul 30, 2012 at 2:38 PM, Peter von Kaehne  wrote:
> On 30/07/12 17:10, Andrew Thule wrote:
>> Troy does this mean that with respect to the modules you host, you go
>> through the rigamarole  of tracing back to source the copyright status
>> for the sake of due diligence?
>
> Yes. We have been caught out, we will get caught out again, no doubt,
> but we will always err on the side of caution if we do not know exactly
> where we are with a text.
>
>> I'd like to know more about establishing a text's
>> pedigree.
>
> There are three potential problems with a text which should be public
> domain.
>
> 1) The text is not the text it claims to be. Not unusual. A language X
> has an old bible translation which is definitely PD. We get a text,
> stating this is the old translation and then it transpires that it is in
> fact a much newer translation. Usually this is a mistake, occasionally
> it is malice.
>
> 2) The text is the text we think it is, but someone has edited/updated
> it. This is very hard sometimes as the edits might be subtle and not
> easily recognisable. They might even be deliberately hidden in order to
> establish a spurious copyright.
>
> 3) The text is the text we think it is, but it has been mutilated by
> poor copying, multiple format transformations, KJVifying and
> de-KJVifying in terms of versification, ripping out bits which are not
> deemed to be canonical enough by whoever handled it before etc etc.
>
> As a solution to above - We tend not to accept texts from just about
> everyone, but are very careful. If a text is PD, we do not accept in
> general a module, but ask for a link back to a authorative website where
> the text is hosted. We do ask questions who copied from whom and we
> generally whittle things down fast.
>
> We certainly do not accept texts (after poor experiences) from
> non-CrossWire bible software projects.
>
> When running our import routines, missing verses and odd versifications
> become obvious usually and this again highlights poor texts. There are
> other signs of poor text quality.
>
> Most of the texts we have imported over the last 3-4 years are directly
> from publishers (Bible societies etc) and others are from bona fide and
> often long established transcription projects.
>
> Hope this makes sense.
>
> Peter
>>
>> ~A
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] SCRIPT: Covert Traditional Book Names to Short Sword Names

[Andrew Thule]

The sword lib contains a file abbr.conf which contains mapping from
traditional book names to short sword module names as follows:
[Text]
Genesis=Gen
Exodus=Ex
Leviticus=Lev
Numbers=Num
Deuteronomy=Deut
Joshua=Josh
Judges=Judg
Ruth=Ruth
I Samuel=1Sam
...

I've grown too lazy to continue converting the names on the left in
that file to their sword equivalent on the right, so I've written a
script to do it. So that I could test the attached script which
translates traditional book names to short sword names, I generated
two text files from this abbr.conf file using the following:

% cat abbr.conf | awk -F"=" '{print $1}' > long.txt
% cat abbr.conf | awk -F"=" '{print $2}' > short.txt

For long.txt I converted Roman numerals to Arabic numerals (I to 1, II
to 2, III to 3) since the following script does not recognize Roman
numerals.

The following script will translate traditional book names to short
sword names as follows:

% cat long.txt | ./convert-long-2-short-names.php


-=-=-= convert-long-2-short-names.php Script -=-=-=-

#!/usr/bin/php -q


-=-=-=- script -=-=-=-

Feel free to use.

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SCRIPT: Covert Traditional Book Names to Short Sword Names

[Andrew Thule]

Opps.  The .php one works (though doesn't handle names of the form
1John). I didn't mean to send that one though.  This one is shorter
using awk not php slightly more elegant and handles books of the form
1 John and 1John:

-=-=-=- convert-long-2-short-names.awk Script -=-=-=-

#!/usr/bin/awk -f
BEG1N {
#FS=OFS="=";
}

{
gsub(/Genesis/,"Gen");
gsub(/Exodus/,"Ex");
gsub(/Leviticus/,"Lev");
gsub(/Numbers/,"Num");
gsub(/Deuteronomy/,"Deut");
gsub(/Joshua/,"Josh");
gsub(/Judges/,"Judg");
gsub(/Ruth/,"Ruth");
gsub(/1Samuel/,"1Sam");
gsub(/1\ Samuel/,"1Sam");
gsub(/2Samuel/,"2Sam");
gsub(/2\ Samuel/,"2Sam");
gsub(/1Kings/,"1Kgs");
gsub(/1\ Kings/,"1Kgs");
gsub(/2Kings/,"2Kgs");
gsub(/2\ Kings/,"2Kgs");
gsub(/1Chronicles/,"1Chr");
gsub(/1\ Chronicles/,"1Chr");
gsub(/2Chronicles/,"2Chr");
gsub(/2\ Chronicles/,"2Chr");
gsub(/Ezra/,"Ezra");
gsub(/Nehemiah/,"Neh");
gsub(/Esther/,"Esth");
gsub(/Job/,"Job");
gsub(/Psalms/,"Pss");
gsub(/Proverbs/,"Prov");
gsub(/Ecclesiastes/,"Eccl");
gsub(/Song/,"Song");
gsub(/Isaiah/,"Isa");
gsub(/Jeremiah/,"Jer");
gsub(/Lamentations/,"Lam");
gsub(/Ezekiel/,"Eze");
gsub(/Daniel/,"Dan");
gsub(/Hosea/,"Hos");
gsub(/Joel/,"Joel");
gsub(/Amos/,"Amos");
gsub(/Obadiah/,"Ob");
gsub(/Jonah/,"Jonah");
gsub(/Micah/,"Mic");
gsub(/Nahum/,"Nah");
gsub(/Habakkuk/,"Hab");
gsub(/Zephaniah/,"Zeph");
gsub(/Haggai/,"Hag");
gsub(/Zechariah/,"Zech");
gsub(/Malachi/,"Mal");
gsub(/Matthew/,"Mt");
gsub(/Mark/,"Mk");
gsub(/Luke/,"Lk");
gsub(/Acts/,"Acts");
gsub(/Romans/,"Rom");
gsub(/1Corinthians/,"1Cor");
gsub(/1\ Corinthians/,"1Cor");
gsub(/2Corinthians/,"2Cor");
gsub(/2\ Corinthians/,"2Cor");
gsub(/Galatians/,"Gal");
gsub(/Ephesians/,"Eph");
gsub(/Philippians/,"Php");
gsub(/Colossians/,"Col");
gsub(/1Thessalonians/,"1Thes");
gsub(/1\ Thessalonians/,"1Thes");
gsub(/2Thessalonians/,"2Thes");
gsub(/2\ Thessalonians/,"2Thes");
gsub(/1Timothy/,"1Tim");
gsub(/1\ Timothy/,"1Tim");
gsub(/2Timothy/,"2Tim");
gsub(/2\ Timothy/,"2Tim");
gsub(/Titus/,"Tit");
gsub(/Philemon/,"Phm");
gsub(/Hebrews/,"Heb");
gsub(/James/,"Jas");
gsub(/1Peter/,"1Pet");
gsub(/1\ Peter/,"1Pet");
gsub(/2Peter/,"2Pet");
gsub(/2\ Peter/,"2Pet");
gsub(/1John/,"1Jn");
gsub(/1\ John/,"1Jn");
gsub(/2John/,"2Jn");
gsub(/2\ John/,"2Jn");
gsub(/3John/,"3Jn");
gsub(/3\ John/,"3Jn");
gsub(/John/,"Jn");
gsub(/Jude/,"Jude");
gsub(/Revelation/,"Rev");
print;
}

END {
}

-=-=-=- end script -=-=-=-

Use is the same.


On Mon, Jul 30, 2012 at 9:14 PM, Andrew Thule  wrote:
> The sword lib contains a file abbr.conf which contains mapping from
> traditional book names to short sword module names as follows:
> [Text]
> Genesis=Gen
> Exodus=Ex
> Leviticus=Lev
> Numbers=Num
> Deuteronomy=Deut
> Joshua=Josh
> Judges=Judg
> Ruth=Ruth
> I Samuel=1Sam
> ...
>
> I've grown too lazy to continue converting the names on the left in
> that file to their sword equivalent on the right, so I've written a
> script to do it. So that I could test the attached script which
> translates traditional book names to short sword names, I generated
> two text files from this abbr.conf file using the following:
>
> % cat abbr.conf | awk -F"=" '{print $1}' > long.txt
> % cat abbr.conf | awk -F"=" '{print $2}' > short.txt
>
> For long.txt I converted Roman numerals to Arabic numerals (I to 1, II
> to 2, III to 3) since the following script does not recognize Roman
> numerals.
>
> The following script will translate traditional book names to short
> sword names as follows:
>
> % cat long.txt | ./convert-long-2-short-names.php
>
>
> -=-=-= convert-long-2-short-names.php Script -=-=-=-
>
> #!/usr/bin/php -q
> 
> //
> // Last modified: 20/07/2012
> //
> // This filter is for changing tradition book names to SWORD Module names
>
> function book_names($out) {
>
> $from = array(
>   "/(\W)([Gg])enesis(\W)/",
>   "/(\W)([Ee])xodus(\W)/",
>   "/(\W)([Ll])eviticus(\W)/",
>

Re: [sword-devel] SCRIPT: Covert Traditional Book Names to Short Sword Names

[Andrew Thule]

Perfect Peter, much appreciated.  I'll give it a go, and see how it goes.
 Its nice the API is so flexible.

~A

On Tuesday, July 31, 2012, Peter von Kaehne wrote:

>
> > Von: Andrew Thule >
>
> >  This one is shorter
> > using awk not php slightly more elegant and handles books of the form
> > 1 John and 1John:
>
> You did not tell what the ultimate purpose for your conversion is, but
> assuming you want to create OSIS references, you might want to investigate
> using the sword API for doing the job. That is one of the things it is
> excellent at.
>
> I created a a while ago a Perl script which translates following
>
>
> A_long_and_complicated_series_of_references_in_any_supported_language
>
> into
>
> 
>
> Where the "long and complicated series..." is broken up, translated into
> OSIS refs and put together into a crossreference note, with the original
> text as free text.
>
> The heavy lifting is done by Sword and relies on the sword Perl bindings
>
> It is in sword-tools/modules/crossreferences/xreffix.pl
>
> Unfortunately the PHP bindings are in a poor state AFAIK, but maybe you
> can reactivate them and use them for your purposes
>
> Yours
>
> Peter
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SCRIPT: Covert Traditional Book Names to Short Sword Names

[Andrew Thule]

On Tue, Jul 31, 2012 at 2:51 AM, Peter von Kaehne  wrote:
> You did not tell what the ultimate purpose for your conversion is, but 
> assuming you want to create OSIS references, you might want to investigate 
> using the sword API for doing the job. That is one of the things it is 
> excellent at.

The purpose of the script was support my effort to make conversion of
non-standard text formats into OSIS less manual - hopefully completely
automated.


> I created a a while ago a Perl script which translates following
>
> A_long_and_complicated_series_of_references_in_any_supported_language
>
> into
>
> 
>
> Where the "long and complicated series..." is broken up, translated into OSIS 
> refs and put together into a crossreference note, with the original text as 
> free text.
> The heavy lifting is done by Sword and relies on the sword Perl bindings
>
> It is in sword-tools/modules/crossreferences/xreffix.pl

I'm having trouble getting the Perl binding working, but am otherwise
keen to give xreffix.pl a try.

>
> Unfortunately the PHP bindings are in a poor state AFAIK, but maybe you can 
> reactivate them and use them for your purposes

PHP is not essential when sed and awk are instead unleashed.

That said, I have an additional question about converting to OSIS
standard book names.  I notice from my exercise of creating the above
scripts that abbr.conf doesn't actually contain the correct
abbreviations (from OSIS2MOD's perspective).

For example abbr.conf recommends:
Exodus=Ex
Psalms=Pss
Ezekiel=Eze
Obadiah=Ob
Matthew=Mt
Mark=Mk
Luke=Lk

Yet osis2mod produced errors, complaining about Ex, Pss, Eze, Ob, Mt,
Mk, and Lk.  These errors went away when I instead used:
Exodus=Exod
Psalms=Ps
Ezekiel=Ezek
Obadiah=Obad
Matthew=Matt
Mark=Mark
Luke=Luke

Have I failed to grasp the purpose of abbr.conf, or is this a hiccup
between abbr.conf and osis2mod?

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] SCRIPT: Covert Traditional Book Names to Short Sword Names

[Andrew Thule]

Thank you both. Both explanations make complete and utter sense.  I see now
the logic, but at the risk of furthering my appearance as a fool, may I ask
..

... notwithstanding the fact there is no direct need, if the OSIS
abbreviations are already mostly the same, and are not standard (public
facing) abbreviations and are mere tokens for osisID and osisRefs, why not
marry the two up for the sake of consistency (which, I recognize is the
hobgoblin of little minds, one of which, I possess).

Currently these tokens already match in nearly every instance except for
the seven I listed (hmm, curious, seven, providence perhaps?):

'Ex' vs 'Exod'
'Pss' vs 'Ps'
'Eze' vs 'Ezek'
'Ob' vs 'Obad'
'Mt' vs 'Matt'
'Mk' vs 'Mark'
'Lk' vs 'Luke'

I can see now why and how they aren't actually related, but still,
consistency is rarely a detriment even if but arbitrary.  I suppose given
all of the other things Sword developers are under pressure to accomplish,
this really is at the bottom of the list of things to worry about.

~A


On Wednesday, August 1, 2012, DM Smith wrote:

> Regarding the difference between the OSIS book abbreviations and abbr.conf:
> OSIS has a fixed abbreviation for each book.
>
> The SWORD Engine in parsing a reference tries to take arbitrary input and
> understand it. So the abbreviations there are for that purpose. They are
> also used as the "best" for displaying to an end user.
>
> In Him,
> DM
>
> On Aug 1, 2012, at 10:15 AM, Andrew Thule  wrote:
>
> > On Tue, Jul 31, 2012 at 2:51 AM, Peter von Kaehne 
> wrote:
> >> You did not tell what the ultimate purpose for your conversion is, but
> assuming you want to create OSIS references, you might want to investigate
> using the sword API for doing the job. That is one of the things it is
> excellent at.
> >
> > The purpose of the script was support my effort to make conversion of
> > non-standard text formats into OSIS less manual - hopefully completely
> > automated.
> >
> >
> >> I created a a while ago a Perl script which translates following
> >>
> >>
> A_long_and_complicated_series_of_references_in_any_supported_language
> >>
> >> into
> >>
> >> 
> >>
> >> Where the "long and complicated series..." is broken up, translated
> into OSIS refs and put together into a crossreference note, with the
> original text as free text.
> >> The heavy lifting is done by Sword and relies on the sword Perl bindings
> >>
> >> It is in sword-tools/modules/crossreferences/xreffix.pl
> >
> > I'm having trouble getting the Perl binding working, but am otherwise
> > keen to give xreffix.pl a try.
> >
> >>
> >> Unfortunately the PHP bindings are in a poor state AFAIK, but maybe you
> can reactivate them and use them for your purposes
> >
> > PHP is not essential when sed and awk are instead unleashed.
> >
> > That said, I have an additional question about converting to OSIS
> > standard book names.  I notice from my exercise of creating the above
> > scripts that abbr.conf doesn't actually contain the correct
> > abbreviations (from OSIS2MOD's perspective).
> >
> > For example abbr.conf recommends:
> > Exodus=Ex
> > Psalms=Pss
> > Ezekiel=Eze
> > Obadiah=Ob
> > Matthew=Mt
> > Mark=Mk
> > Luke=Lk
> >
> > Yet osis2mod produced errors, complaining about Ex, Pss, Eze, Ob, Mt,
> > Mk, and Lk.  These errors went away when I instead used:
> > Exodus=Exod
> > Psalms=Ps
> > Ezekiel=Ezek
> > Obadiah=Obad
> > Matthew=Matt
> > Mark=Mark
> > Luke=Luke
> >
> > Have I failed to grasp the purpose of abbr.conf, or is this a hiccup
> > between abbr.conf and osis2mod?
> >
> > ~A
> >
> > ___
> > sword-devel mailing list: sword-devel@crosswire.org
> > http://www.crosswire.org/mailman/listinfo/sword-devel
> > Instructions to unsubscribe/change your settings at above page
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] No errors. Valid OSIS. Not working. Looking for suggestions.

[Andrew Thule]

I'm working on a 'commentary' for the first time and having some trouble.

I very much like the module OTPassages. Chris has given me an IMP file
of the module OTPassages (quoted in the NT) which I have converted to
OSIS, xmllintetd and run through osis2mod all without problems.  When
I use osis2mod to convert the original OSIS module )(without changes,
and using the stock otpassage.conf) everything works.   The module
shows up as a commentary OTPassages, when I navigate the bible in the
NT, I see the references.  It works as it is suppose to.

However with the OSIS document where I've added references, xmllint
validates it perfectly, osis2mod also produces no errors, but nothing
at all shows up in the commentary section.  I've tested this in Xiphos
and Bibletime.  I know it is being taken as a commentary since it
shows up as one in both Xiphos and Bibletime, but no errors are
produce and nothing is ever seen. I Know the module is loaded since I
can see the module title once it is loaded.

I'm stuck here however, because it doesn't seem to be working
otherwise, yet I'm not getting a single errors.  It's like the module
is simply not there (though it seems loaded).  There's not text
references.  I've changed the name of this module to 'OTTEST' simply
to differentiate it from OTPassages and it shows up and loads as
OTTEST.  I've tried all of the -b 2|3|4 options with osis2mod.  I've
created raw versions, zipped versions, and looked at debug levels
1,16,128 all to no effect.

Anyone have any ideas where I can go from here to find out where the
problem lies?

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] No errors. Valid OSIS. Not working. Looking for suggestions.

[Andrew Thule]

I haven't had a chance to explore Peter's recommendations yet, but I
know it isn't file permissions.  I have a script that auto-magically
corrects them as part of the same process that runs osis2mod.

Both suggestions make me think the problem is below the client
application, which is consistent with the behaviour I'm seeing.

Thanks
~A.

On Thu, Aug 2, 2012 at 1:21 PM, Brian J Dumont  wrote:
>  ... or maybe file permissions on the module or conf file?
>
>
>
> On 08/02/2012 12:35 PM, Peter von Kaehne wrote:
>>
>> Usually path or driver errors.
>>
>> Wrong path to module or mismatch between driver and conf entry re driver.
>>
>> Peter
>>
>> On 02/08/12 15:29, Andrew Thule wrote:
>>>
>>> I'm working on a 'commentary' for the first time and having some trouble.
>>>
>>> I very much like the module OTPassages. Chris has given me an IMP file
>>> of the module OTPassages (quoted in the NT) which I have converted to
>>> OSIS, xmllintetd and run through osis2mod all without problems.  When
>>> I use osis2mod to convert the original OSIS module )(without changes,
>>> and using the stock otpassage.conf) everything works.   The module
>>> shows up as a commentary OTPassages, when I navigate the bible in the
>>> NT, I see the references.  It works as it is suppose to.
>>>
>>> However with the OSIS document where I've added references, xmllint
>>> validates it perfectly, osis2mod also produces no errors, but nothing
>>> at all shows up in the commentary section.  I've tested this in Xiphos
>>> and Bibletime.  I know it is being taken as a commentary since it
>>> shows up as one in both Xiphos and Bibletime, but no errors are
>>> produce and nothing is ever seen. I Know the module is loaded since I
>>> can see the module title once it is loaded.
>>>
>>> I'm stuck here however, because it doesn't seem to be working
>>> otherwise, yet I'm not getting a single errors.  It's like the module
>>> is simply not there (though it seems loaded).  There's not text
>>> references.  I've changed the name of this module to 'OTTEST' simply
>>> to differentiate it from OTPassages and it shows up and loads as
>>> OTTEST.  I've tried all of the -b 2|3|4 options with osis2mod.  I've
>>> created raw versions, zipped versions, and looked at debug levels
>>> 1,16,128 all to no effect.
>>>
>>> Anyone have any ideas where I can go from here to find out where the
>>> problem lies?
>>>
>>> ~A
>>>
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>
>
> --
> ---
> The question is not "Have you accepted Jesus into your heart", but "Has
> Jesus accepted you into His heart?"; not "have you given your whole
> life for God", but "has God given His whole life for you"
> - Pr Bryan Wolfmueller, 2010
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] No errors. Valid OSIS. Not working. Looking for suggestions.

[Andrew Thule]

Yes, thank you for the suggestions all.

Peter, your instincts are correct - it was a pathing problem.

Cheers
~A

On Thu, Aug 2, 2012 at 1:49 PM, DM Smith  wrote:
> Try creating a "raw" module and open the data files with a text editor to see 
> if they have what you expect. The -d 2 flag is useful in understanding the 
> data file.
>
> I agree w/ Peter et al, it is almost always a conf or a file permission 
> problem.
> In Him,
> DM
>
> On Aug 2, 2012, at 10:29 AM, Andrew Thule  wrote:
>
>> I'm working on a 'commentary' for the first time and having some trouble.
>>
>> I very much like the module OTPassages. Chris has given me an IMP file
>> of the module OTPassages (quoted in the NT) which I have converted to
>> OSIS, xmllintetd and run through osis2mod all without problems.  When
>> I use osis2mod to convert the original OSIS module )(without changes,
>> and using the stock otpassage.conf) everything works.   The module
>> shows up as a commentary OTPassages, when I navigate the bible in the
>> NT, I see the references.  It works as it is suppose to.
>>
>> However with the OSIS document where I've added references, xmllint
>> validates it perfectly, osis2mod also produces no errors, but nothing
>> at all shows up in the commentary section.  I've tested this in Xiphos
>> and Bibletime.  I know it is being taken as a commentary since it
>> shows up as one in both Xiphos and Bibletime, but no errors are
>> produce and nothing is ever seen. I Know the module is loaded since I
>> can see the module title once it is loaded.
>>
>> I'm stuck here however, because it doesn't seem to be working
>> otherwise, yet I'm not getting a single errors.  It's like the module
>> is simply not there (though it seems loaded).  There's not text
>> references.  I've changed the name of this module to 'OTTEST' simply
>> to differentiate it from OTPassages and it shows up and loads as
>> OTTEST.  I've tried all of the -b 2|3|4 options with osis2mod.  I've
>> created raw versions, zipped versions, and looked at debug levels
>> 1,16,128 all to no effect.
>>
>> Anyone have any ideas where I can go from here to find out where the
>> problem lies?
>>
>> ~A
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Alternate Versification question

[Andrew Thule]

osis2mod -h lists the following versifications supported:

  -v   specify a versification scheme to use (default is KJV)
 Note: The following are valid values for v11n:
Catholic
Catholic2
German
KJV
KJVA
Leningrad
Luther
MT
NRSV
NRSVA
Synodal
Vulg

However, this following page list others (such as LXX and GNT):
http://svn.crosswire.org/wiki/Alternate_Versification/System_Identification

I can see from this page that support for some of the versification
schemes appears to be a function of the development cycle with German,
Luther and Vulgate being added in 1.6.1 and Catholic and Catholic2
being added in 1.6.2:
http://svn.crosswire.org/wiki/Alternate_Versification#Supported_versification_systems

Cutting to the chase, my question is this, are versification schemes
such as LXX and GNT to be expected in subsequent development
iterations or are there otherways to employ them?  I'm specifically
interested in LXX as I've got valid OSIS for LXXE, but I'm constantly
banging into versification errors/warning when I create my module
ie.
INFO(V11N): Hos.7 is not in the NRSVA versification. Appending content
to Hos.6.11
INFO(V11N): Tob.8 is not in the NRSVA versification. Appending content
to Tob.7.16
INFO(V11N): Tob.11 is not in the KJVA versification. Appending content
to Tob.10.12
INFO(V11N): Sir.30.27 is not in the KJVA versification. Appending
content to Sir.30.25
ERROR(REF): Invalid osisID/annotateRef: 4Macc.18.1
etc.

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Thanks Greg .. I've done that, and compared what comes with Sword to
what's listed here:
https://crosswire.org/svn/sword-tools/trunk/versification/basicv11ns/

The only difference, as far as I was able to tell was canon_gnt.h does
not appear to ship with sword.  I assume it was pruned or included
with others.  Otherwise the contents appear the same.

I've found a verification here:
http://www.ccel.org/refsys/Bible.LXX.xml

I'm going to try to create a canon_lxx.h myself - but what use is
that?  If I successfully translate the CCEL LXX versification into a
canon_lxx.h file and submit it - does that actually help anything?

~A

On Wed, Aug 8, 2012 at 9:31 PM, Greg Hellings  wrote:
> Some have been pruned in the past because they were either duplicates
> or similar. It is also possible that some of the documentation is out
> of date. The best way to know for sure is to look at the installed
> header files, if you're on Linux, to see which ones are included. Each
> versification is listed in a header file with the name canon_.h
>
> Modifications must also be made in a few others places once that file
> is in place. If the one you need isn't supported (I don't see LXX or
> GNT at present) then you're welcome to create such a file and submit
> it along with your module.
>
> --Greg
>
> On Wed, Aug 8, 2012 at 8:25 PM, Andrew Thule  wrote:
>> osis2mod -h lists the following versifications supported:
>>
>>   -v   specify a versification scheme to use (default is 
>> KJV)
>>  Note: The following are valid values for 
>> v11n:
>> Catholic
>> Catholic2
>> German
>> KJV
>> KJVA
>> Leningrad
>> Luther
>> MT
>> NRSV
>> NRSVA
>> Synodal
>> Vulg
>>
>> However, this following page list others (such as LXX and GNT):
>> http://svn.crosswire.org/wiki/Alternate_Versification/System_Identification
>>
>> I can see from this page that support for some of the versification
>> schemes appears to be a function of the development cycle with German,
>> Luther and Vulgate being added in 1.6.1 and Catholic and Catholic2
>> being added in 1.6.2:
>> http://svn.crosswire.org/wiki/Alternate_Versification#Supported_versification_systems
>>
>> Cutting to the chase, my question is this, are versification schemes
>> such as LXX and GNT to be expected in subsequent development
>> iterations or are there otherways to employ them?  I'm specifically
>> interested in LXX as I've got valid OSIS for LXXE, but I'm constantly
>> banging into versification errors/warning when I create my module
>> ie.
>> INFO(V11N): Hos.7 is not in the NRSVA versification. Appending content
>> to Hos.6.11
>> INFO(V11N): Tob.8 is not in the NRSVA versification. Appending content
>> to Tob.7.16
>> INFO(V11N): Tob.11 is not in the KJVA versification. Appending content
>> to Tob.10.12
>> INFO(V11N): Sir.30.27 is not in the KJVA versification. Appending
>> content to Sir.30.25
>> ERROR(REF): Invalid osisID/annotateRef: 4Macc.18.1
>> etc.
>>
>> ~A
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

I guess you're saying that's what essentially defines a versification
.. (I wasn't sure if there was more to it ..).

Thanks.
~A

On Wed, Aug 8, 2012 at 10:09 PM, Greg Hellings  wrote:
> On Wed, Aug 8, 2012 at 9:05 PM, Andrew Thule  wrote:
>> Thanks Greg .. I've done that, and compared what comes with Sword to
>> what's listed here:
>> https://crosswire.org/svn/sword-tools/trunk/versification/basicv11ns/
>>
>> The only difference, as far as I was able to tell was canon_gnt.h does
>> not appear to ship with sword.  I assume it was pruned or included
>> with others.  Otherwise the contents appear the same.
>>
>> I've found a verification here:
>> http://www.ccel.org/refsys/Bible.LXX.xml
>>
>> I'm going to try to create a canon_lxx.h myself - but what use is
>> that?  If I successfully translate the CCEL LXX versification into a
>> canon_lxx.h file and submit it - does that actually help anything?
>
> It does if you are creating an LXX-based module.
>
> --Greg
>
>>
>> ~A
>>
>> On Wed, Aug 8, 2012 at 9:31 PM, Greg Hellings  
>> wrote:
>>> Some have been pruned in the past because they were either duplicates
>>> or similar. It is also possible that some of the documentation is out
>>> of date. The best way to know for sure is to look at the installed
>>> header files, if you're on Linux, to see which ones are included. Each
>>> versification is listed in a header file with the name canon_.h
>>>
>>> Modifications must also be made in a few others places once that file
>>> is in place. If the one you need isn't supported (I don't see LXX or
>>> GNT at present) then you're welcome to create such a file and submit
>>> it along with your module.
>>>
>>> --Greg
>>>
>>> On Wed, Aug 8, 2012 at 8:25 PM, Andrew Thule  wrote:
>>>> osis2mod -h lists the following versifications supported:
>>>>
>>>>   -v   specify a versification scheme to use (default is 
>>>> KJV)
>>>>  Note: The following are valid values for 
>>>> v11n:
>>>> Catholic
>>>> Catholic2
>>>> German
>>>> KJV
>>>> KJVA
>>>> Leningrad
>>>> Luther
>>>> MT
>>>> NRSV
>>>> NRSVA
>>>> Synodal
>>>> Vulg
>>>>
>>>> However, this following page list others (such as LXX and GNT):
>>>> http://svn.crosswire.org/wiki/Alternate_Versification/System_Identification
>>>>
>>>> I can see from this page that support for some of the versification
>>>> schemes appears to be a function of the development cycle with German,
>>>> Luther and Vulgate being added in 1.6.1 and Catholic and Catholic2
>>>> being added in 1.6.2:
>>>> http://svn.crosswire.org/wiki/Alternate_Versification#Supported_versification_systems
>>>>
>>>> Cutting to the chase, my question is this, are versification schemes
>>>> such as LXX and GNT to be expected in subsequent development
>>>> iterations or are there otherways to employ them?  I'm specifically
>>>> interested in LXX as I've got valid OSIS for LXXE, but I'm constantly
>>>> banging into versification errors/warning when I create my module
>>>> ie.
>>>> INFO(V11N): Hos.7 is not in the NRSVA versification. Appending content
>>>> to Hos.6.11
>>>> INFO(V11N): Tob.8 is not in the NRSVA versification. Appending content
>>>> to Tob.7.16
>>>> INFO(V11N): Tob.11 is not in the KJVA versification. Appending content
>>>> to Tob.10.12
>>>> INFO(V11N): Sir.30.27 is not in the KJVA versification. Appending
>>>> content to Sir.30.25
>>>> ERROR(REF): Invalid osisID/annotateRef: 4Macc.18.1
>>>> etc.
>>>>
>>>> ~A
>>>>
>>>> ___
>>>> sword-devel mailing list: sword-devel@crosswire.org
>>>> http://www.cros

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Yes I found that to be true (CCELs versification was, by the authors own
admission, error ridden).  Regardless, with a bit of work was able to
create one that wasn't, which the CCEL one helped validate.

~A

On Thursday, August 9, 2012, Chris Little wrote:

> On 08/08/2012 07:05 PM, Andrew Thule wrote:
>
>> Thanks Greg .. I've done that, and compared what comes with Sword to
>> what's listed here:
>> https://crosswire.org/svn/**sword-tools/trunk/**versification/basicv11ns/<https://crosswire.org/svn/sword-tools/trunk/versification/basicv11ns/>
>>
>> The only difference, as far as I was able to tell was canon_gnt.h does
>> not appear to ship with sword.  I assume it was pruned or included
>> with others.  Otherwise the contents appear the same.
>>
>> I've found a verification here:
>> http://www.ccel.org/refsys/**Bible.LXX.xml<http://www.ccel.org/refsys/Bible.LXX.xml>
>>
>> I'm going to try to create a canon_lxx.h myself - but what use is
>> that?  If I successfully translate the CCEL LXX versification into a
>> canon_lxx.h file and submit it - does that actually help anything?
>>
>
> I'll put a little time into a new versification system right now, but in
> general I would not accept any submissions of versification systems. CCEL's
> versification data, especially, is so error-ridden as to be worthless.
>
> --Chris
>
>
> __**_
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel>
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Thanks for the links.  Yes LXXE is Brenton which I'm in the process of
throwing at Tesseract, albeit with some effort.
 No I wasn't aware of Michael Johnson's efforts so should make some effort
to contact him.  I appreciate your comments.

~A


On Thursday, August 9, 2012, David Haslam wrote:

> I expect that LXXE does indeed mean the English Brenton.
>
> If so, then Andrew should be made aware that Michael Johnson is working on
> a
> modernized English LXX.
>
> See these two links:
>
> http://ebible.org/eng-Brenton/
> http://ebible.org/eng-lxx2012/
>
> David
>
>
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/Alternate-Versification-question-tp4650784p4650791.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Now that I've seen Michael has place his text in the public domain, really
appreciate you pointing out these links.

This is going to make things go much quicker.   Though I have already spent
some effort building source text, haven't pride enough to stop me from
using Michaels text instead, which as far as I can tell has fewer errors.

~A

On Thursday, August 9, 2012, David Haslam wrote:

> I expect that LXXE does indeed mean the English Brenton.
>
> If so, then Andrew should be made aware that Michael Johnson is working on
> a
> modernized English LXX.
>
> See these two links:
>
> http://ebible.org/eng-Brenton/
> http://ebible.org/eng-lxx2012/
>
> David
>
>
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/Alternate-Versification-question-tp4650784p4650791.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Michael, thanks very much.  I've spell corrected the following words:
kindreds to kindred
basons to basin
dulness to dullness.

Otherwise the text looks very good.
I've turned it into a sword module, and will keep working on improvements,
including comparing it to the text I had.  Let me know and I'll give you
FTP details where you can install the modules directly.

~ A

On Thursday, August 9, 2012, Kahunapule Michael Johnson wrote:

>  Yes, please do feel free to use the text I have posted on eBible.org, if
> you like. If you find errors in it, please let me know so that I can
> correct them. I have found some by comparing a couple of different sources,
> but there may still be a few typos/OCR errors. If you have done some work
> preparing text of the Brenton LXX, you might try comparing it to what I
> posted to see if there are any errors revealed in that process. This is a
> good way to redeem the work you have already done. Proofreading is hard.
> For proof of that, try searching for "statue" in some electronic copies of
> the ASV (other than the one at http://eBible.org/asv/), and see if it
> shouldn't actually be "statute". :-)
>
> The LXX2012 is a spelling-updated version of the Brenton translation, with
> numerous substitutions like "hath"->"has" done.
>
> Enjoy!
> Michael
> http://MLJohnson.org
>
> On 08/09/2012 07:59 AM, Andrew Thule wrote:
>
> Now that I've seen Michael has place his text in the public domain, really
> appreciate you pointing out these links.
>
>  This is going to make things go much quicker.   Though I have already
> spent some effort building source text, haven't pride enough to stop me
> from using Michaels text instead, which as far as I can tell has fewer
> errors.
>
>  ~A
>
> On Thursday, August 9, 2012, David Haslam wrote:
>
>> I expect that LXXE does indeed mean the English Brenton.
>>
>> If so, then Andrew should be made aware that Michael Johnson is working
>> on a
>> modernized English LXX.
>>
>> See these two links:
>>
>> http://ebible.org/eng-Brenton/
>> http://ebible.org/eng-lxx2012/
>>
>> David
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://sword-dev.350566.n4.nabble.com/Alternate-Versification-question-tp4650784p4650791.html
>> Sent from the SWORD Dev mailing list archive at Nabble.com.
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org  'cvml', 
> 'sword-devel@crosswire.org');>http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
>
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Yes from the CLI (initial training is painful - though skillful Internet
searches can often get you training files for particular fonts that are
close).  I tried using Qtesseract, but the compilation was somewhat
problematic, and felt the time investment (to get the thing to work) was
little worth the return (and went back to the command line).

Besides, if you get Tesseract trained well to work from the command line
you can automate most things in typical unix fashion via scripts and pipes.
 Because I'm mostly lazy, what effort I do spend, is spent making things
work more automatically.  Now that Tesseract takes .png files directly,
messy conversion business to .tiffs is gone and so effort scanning now ends
up being mostly preparatory with some touch up thrown in (scanning errors
can often be corrected through intelligent use of ispell/mspell/aspell).
 Even so, OCR work will always contain some degree of human effort.

Other than Qtesseract, I've no experience with other GUIs (I not so with
Python, for example, which cuts out most of the others)
~A

On Friday, August 10, 2012, David Haslam wrote:

> Andrew,
>
> Are you using Tesseract from the command line, or did you also install a
> http://en.wikipedia.org/wiki/Tesseract_%28software%29#User_interfaces GUI
> for Tesseract ?
> If so, which? and any comments worth sharing?
>
> David
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/Alternate-Versification-question-tp4650784p4650799.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Hmm, 'basons' was in my text too, so perhaps it was an antiquated word
chosen by Brenton.  Regardless, I'm working with your LXX2012 text, which
has already had some of the more archaic language improved, so will stick
with the change.

~A

On Thursday, August 9, 2012, Andrew Thule wrote:

> Michael, thanks very much.  I've spell corrected the following words:
> kindreds to kindred
> basons to basin
> dulness to dullness.
>
> Otherwise the text looks very good.
> I've turned it into a sword module, and will keep working on improvements,
> including comparing it to the text I had.  Let me know and I'll give you
> FTP details where you can install the modules directly.
>
> ~ A
>
> On Thursday, August 9, 2012, Kahunapule Michael Johnson wrote:
>
>>  Yes, please do feel free to use the text I have posted on eBible.org,
>> if you like. If you find errors in it, please let me know so that I can
>> correct them. I have found some by comparing a couple of different sources,
>> but there may still be a few typos/OCR errors. If you have done some work
>> preparing text of the Brenton LXX, you might try comparing it to what I
>> posted to see if there are any errors revealed in that process. This is a
>> good way to redeem the work you have already done. Proofreading is hard.
>> For proof of that, try searching for "statue" in some electronic copies of
>> the ASV (other than the one at http://eBible.org/asv/), and see if it
>> shouldn't actually be "statute". :-)
>>
>> The LXX2012 is a spelling-updated version of the Brenton translation,
>> with numerous substitutions like "hath"->"has" done.
>>
>> Enjoy!
>> Michael
>> http://MLJohnson.org
>>
>> On 08/09/2012 07:59 AM, Andrew Thule wrote:
>>
>> Now that I've seen Michael has place his text in the public domain,
>> really appreciate you pointing out these links.
>>
>>  This is going to make things go much quicker.   Though I have already
>> spent some effort building source text, haven't pride enough to stop me
>> from using Michaels text instead, which as far as I can tell has fewer
>> errors.
>>
>>  ~A
>>
>> On Thursday, August 9, 2012, David Haslam wrote:
>>
>>> I expect that LXXE does indeed mean the English Brenton.
>>>
>>> If so, then Andrew should be made aware that Michael Johnson is working
>>> on a
>>> modernized English LXX.
>>>
>>> See these two links:
>>>
>>> http://ebible.org/eng-Brenton/
>>> http://ebible.org/eng-lxx2012/
>>>
>>> David
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://sword-dev.350566.n4.nabble.com/Alternate-Versification-question-tp4650784p4650791.html
>>> Sent from the SWORD Dev mailing list archive at Nabble.com.
>>>
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>>
>>
>>
>> ___
>> sword-devel mailing list: 
>> sword-devel@crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>>
>>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Indeed, and I thought Eton was exclusive!

Does the next verse contain one too "and the lictors told..." or was
lictors a word?
~A

On Friday, August 10, 2012, David Haslam wrote:

> For the most amusing howler caused by an OCR error, install the Anderson
> (NT)
> module and read Acts 16:37
>
> btw.  If you're British, you'll find this even more amusing than the rest
> of
> you.
>
> David
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/Alternate-Versification-question-tp4650784p4650798.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

I was making changes to the LXX2012 version - but then quit.  I
decided to instead work on getting out a version with original text.
I've created a versification system based upon an 1857 edition of
Brenton's book (and consulted 2 other versions, including a 1900
edition).  The versification doesn't match the order your text was in,
but don't worry - it seems to take the OSIS and it it in order
correctly - however it is ordered in the OSIS based upon the
versification. (I tried  this on another module).  I've attached a
copy of the versification.

I'm going to continue working on the Brenton version so as to get out
a version with unmodified text.  Then I'll get back to the 2012
version later and update the English.  I found found printing errors
in two of the book I was consulting based upon your text where verses
would simply be followed by text from different chapters.  Your
version of the text seemed 'mostly' correct.  I was able to resolve
these problems (mostly) but not all.  For example:

Your Sirach 30 has 25 verses - the 1857 printed version has 31
Your Sirach 31 has 31 verses - the 1857 printed version has 26 (so
does the 1900)
Your Sirach 32 has 24 verses - the 1857 printed version has 20
Your Sirach 33 has 31 verses - the 1857 printed version has 12
Your Sirach 34 has 26 verses - the 1857 printed version has 31
Your Sirach 35 has 20 verses - the 1857 printed version has 24

I'm convinced the 1857 printed version has typesetting errors because
this is an instance when the verse numbers jumped around and seemed to
pull verses from other chapters (for example I think some of the
verses missing from Sirach 33 in the 1857 printed version show up
elsewhere.  I believe all of there verses are there, but the printed
version simply seems to mixed them in elsewhere.  I've not been able
to find out of the Greek LXX comes in different flavours these
editions could have been made from.

However your 1 Kings 9 missed a bunch of verses (numbering from 1Kings
9:1-14, 26-28) and comparing it to the printed text, I gave your
version an empty [9:15] and relabelled [9:26-28] to [9:16-18] and that
resolved the problem and both texts aligned perfectly.

Even with this change, there's something going on funny about
Sir.31-38 between different printed versions of the text and your
text. Even the 1900 version didn't agree with your text or the 1857
version (though it mostly followed the 1857 version nearly everywhere
else.  Ultimately, I couldn't resolve those issues.  All of the text
is there just in wrong chapters.  For the versification, I went with
your version of the text.. because I figured it would make it easiest
to produce a sword module if I didn't have figure out from the Greek
where the verses were actually suppose to be, and your text 'seemed'
correct to me.  The verses placement seemed to read the most correct.

~A


On Fri, Aug 10, 2012 at 10:50 PM, Kahunapule Michael Johnson
 wrote:
> I just implemented a lot of spelling corrections for the LXX2012 (thanks to
> David Haslam), so you might want to grab a fresh copy tomorrow.
>
>
> On 08/10/2012 03:40 AM, Andrew Thule wrote:
>
> Hmm, 'basons' was in my text too, so perhaps it was an antiquated word
> chosen by Brenton.  Regardless, I'm working with your LXX2012 text, which
> has already had some of the more archaic language improved, so will stick
> with the change.
>
> ~A
>
> On Thursday, August 9, 2012, Andrew Thule wrote:
>>
>> Michael, thanks very much.  I've spell corrected the following words:
>> kindreds to kindred
>> basons to basin
>> dulness to dullness.
>>
>> Otherwise the text looks very good.
>> I've turned it into a sword module, and will keep working on improvements,
>> including comparing it to the text I had.  Let me know and I'll give you FTP
>> details where you can install the modules directly.
>>
>> ~ A
>>
>> On Thursday, August 9, 2012, Kahunapule Michael Johnson wrote:
>>>
>>> Yes, please do feel free to use the text I have posted on eBible.org, if
>>> you like. If you find errors in it, please let me know so that I can correct
>>> them. I have found some by comparing a couple of different sources, but
>>> there may still be a few typos/OCR errors. If you have done some work
>>> preparing text of the Brenton LXX, you might try comparing it to what I
>>> posted to see if there are any errors revealed in that process. This is a
>>> good way to redeem the work you have already done. Proofreading is hard. For
>>> proof of that, try searching for "statue" in some electronic copies of the
>>> ASV (other than the one at http://eBible.org/asv/), and see if it shouldn't
>>> actually be 

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Thanks Chris.

Here's an English Septuagint versification system, based upon the text
I got from Michael  and compared to a number of printed version.  The
Chapter order doesn't quite follow the KJV or NSRV convention, but it
does follow the Septuagints order.

I appreciate it if you could add this so we can get an English
Septuagint module out.  I worked on this weekend quickly because I've
seen you reference you're working through another one, and I wanted to
get it in on your timeline.

One question - I stuck with the names listed in the abbrevs.h and I
understand that the short forms as markers.  So for example the
Septuagint calls the Prayer of Azariah the Song of the Three Children
(in Greek) and Breton translate it as such - yet the marker will be
PrAzar.  I have no issue with that, but how do I now influence the
appearance of the book names (however the program deals with them).

I see this can be done in locales, but is that the right place for it?
 I'd like to keep the Greek influenced names - since the original
language was Greek.  I.e.
Esias for Isaiah
Jermias for Jeremiah
Osee for Hosea
Aggaeus for Haggai

Etc.

~A

On Thu, Aug 9, 2012 at 2:17 AM, Chris Little  wrote:
> On 08/08/2012 07:05 PM, Andrew Thule wrote:
>>
>> Thanks Greg .. I've done that, and compared what comes with Sword to
>> what's listed here:
>> https://crosswire.org/svn/sword-tools/trunk/versification/basicv11ns/
>>
>> The only difference, as far as I was able to tell was canon_gnt.h does
>> not appear to ship with sword.  I assume it was pruned or included
>> with others.  Otherwise the contents appear the same.
>>
>> I've found a verification here:
>> http://www.ccel.org/refsys/Bible.LXX.xml
>>
>> I'm going to try to create a canon_lxx.h myself - but what use is
>> that?  If I successfully translate the CCEL LXX versification into a
>> canon_lxx.h file and submit it - does that actually help anything?
>
>
> I'll put a little time into a new versification system right now, but in
> general I would not accept any submissions of versification systems. CCEL's
> versification data, especially, is so error-ridden as to be worthless.
>
> --Chris
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
/**
 * canon_lxxe.h - Versification data for the LXXE system
 *
 * Copyright 2009 CrossWire Bible Society (http://www.crosswire.org)
 *	CrossWire Bible Society
 *	P. O. Box 2528
 *	Tempe, AZ  85280-2528
 *
 * This program is free software; you can redistribute it and/or modify it
 * under the terms of the GNU General Public License as published by the
 * Free Software Foundation version 2.
 *
 * This program is distributed in the hope that it will be useful, but
 * WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 * General Public License for more details.
 */

#ifndef CANON_LXXE_H
#define CANON_LXXE_H

SWORD_NAMESPACE_START


// Versification system: LXXE
// Book order: Gen Exod Lev Num Deut Josh Judg Ruth 1Sam 2Sam 1Kgs 2Kgs 1Chr 2Chr Ezra Neh Esth Job Ps Prov Eccl Song Isa Jer Lam Ezek Dan Hos Joel Amos Obad Jonah Mic Nah Hab Zeph Hag Zech Mal 1Esd Tob Jdt Wis Sir Bar EpJer PrAzar Sus Bel 1Macc 2Macc 3Macc 4Macc PrMan
// This versification data is based on examination of a 1857 edition of 'The Septuagint version of the Old Testament and Apocrypha.  Different editions have errors.  Most have been corrected here, and where two conflict the greater number was choosen.  The only place resolution was not possible was around Sirach 30-36 where a 1900 edition had printing errors mixing sections of chapters
// Note that 11QPs is included as Part of Ps, as Ps.151
// Two different version of PrMan are included; one as PrMan and the other as Ps.152

/**
 * [on]tbooks_lxxe - initialize static instance for all canonical
 *		 text names and chapmax
 */
// for otbooks_lxxe, use otbooks

/**
 * [on]tbooks_lxxe - initialize static instance for all canonical
 *   text names and chapmax
 */

struct sbook otbooks_lxxe[] = {
  {"Genesis", "Gen", "Gen", 50},
  {"Exodus", "Exod", "Exod", 40},
  {"Leviticus", "Lev", "Lev", 27},
  {"Numbers", "Num", "Num", 36},
  {"Deuteronomy", "Deut", "Deut", 34},
  {"Joshua", "J

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

That certainly explains the apparent disorder - thanks for that.

On Mon, Aug 13, 2012 at 12:11 PM, Chris Little  wrote:
> On 08/12/2012 11:23 PM, Andrew Thule wrote:
>>
>> I was making changes to the LXX2012 version - but then quit.  I
>> decided to instead work on getting out a version with original text.
>> I've created a versification system based upon an 1857 edition of
>> Brenton's book (and consulted 2 other versions, including a 1900
>> edition).  The versification doesn't match the order your text was in,
>> but don't worry - it seems to take the OSIS and it it in order
>> correctly - however it is ordered in the OSIS based upon the
>> versification. (I tried  this on another module).  I've attached a
>> copy of the versification.
>>
>> I'm going to continue working on the Brenton version so as to get out
>> a version with unmodified text.  Then I'll get back to the 2012
>> version later and update the English.  I found found printing errors
>> in two of the book I was consulting based upon your text where verses
>> would simply be followed by text from different chapters.  Your
>> version of the text seemed 'mostly' correct.  I was able to resolve
>> these problems (mostly) but not all.  For example:
>>
>> Your Sirach 30 has 25 verses - the 1857 printed version has 31
>> Your Sirach 31 has 31 verses - the 1857 printed version has 26 (so
>> does the 1900)
>> Your Sirach 32 has 24 verses - the 1857 printed version has 20
>> Your Sirach 33 has 31 verses - the 1857 printed version has 12
>> Your Sirach 34 has 26 verses - the 1857 printed version has 31
>> Your Sirach 35 has 20 verses - the 1857 printed version has 24
>>
>> I'm convinced the 1857 printed version has typesetting errors because
>> this is an instance when the verse numbers jumped around and seemed to
>> pull verses from other chapters (for example I think some of the
>> verses missing from Sirach 33 in the 1857 printed version show up
>> elsewhere.  I believe all of there verses are there, but the printed
>> version simply seems to mixed them in elsewhere.  I've not been able
>> to find out of the Greek LXX comes in different flavours these
>> editions could have been made from.
>>
>> However your 1 Kings 9 missed a bunch of verses (numbering from 1Kings
>> 9:1-14, 26-28) and comparing it to the printed text, I gave your
>> version an empty [9:15] and relabelled [9:26-28] to [9:16-18] and that
>> resolved the problem and both texts aligned perfectly.
>>
>> Even with this change, there's something going on funny about
>> Sir.31-38 between different printed versions of the text and your
>> text. Even the 1900 version didn't agree with your text or the 1857
>> version (though it mostly followed the 1857 version nearly everywhere
>> else.  Ultimately, I couldn't resolve those issues.  All of the text
>> is there just in wrong chapters.  For the versification, I went with
>> your version of the text.. because I figured it would make it easiest
>> to produce a sword module if I didn't have figure out from the Greek
>> where the verses were actually suppose to be, and your text 'seemed'
>> correct to me.  The verses placement seemed to read the most correct.
>
>
> Per the publisher's note at the second Sirach 30:16 of Brenton in my printed
> edition:
>
> "The Greek text of Ecclesiasticus 30:24-36:16 is in great disorder in
> virtually every Greek ms. Scholars are convinced by old translations
> (Arabic, Syriac, and Old Latin), however, that the order of modern English
> editions (e.g. NRSV) is correct. Brenton's versification reflects the
> conflict between the Greek text and the order observed in these other
> translations."
>
> --Chris
>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

not represent Brenton's LXX because the
> versification of Brenton's LXX is not supportable by Sword. Multiple verses
> of the same number within a chapter and verses that do not strictly increase
> cannot be represented by a SWText module, as currently implemented. Brenton
> includes both of these and so its native versification cannot be supported
> by Sword.

Respectfully, I disagree.   I made every effort to confirm Brenton's
English versification matched the typical underlying Greek LXX's
formats; and that the underlying Greek format he matched was
widespread.  By virtue your own comments explaining my observations
about the mess in Sirach 30-36 shows that I've largely matched the
underlying Greek (except where the Greek is inconsistent).

 This hows that I've done this diligently.  Otherwise, if the LXXE
versification system doesn't match the broad versification tradition
of LXX, I'd happy to amend any errors you see.  If you look at it,
you'll see this is a widespread LXX versification.  Or are you saying
LXX isn't a broad versification tradition?


> In short order, the Rahlfs versification system should be available in Sword
> SVN. That may suffice for your encoding needs in the near term.
> Subsequently, it may be possible to define a more general LXX versification
> system that excludes the Rahlfs'-specific books like the variants of Joshua
> & Judges, the Theodotian variant books, Odes, and PsSol and that adds verses
> absent from Rahlfs' in order to maximize verse coverage in similar editions.
> I'll certainly consult your versification system submission while working on
> that. Going forward, that might be a better candidate for the versification
> system employed by a Brenton module.

I'd be happy to give it a try, once its available.  Feel free to
consult the one I've submitted in the production Rahlf's-specific in
the meanwhile.  It wasn't done mindlessly or without due care and
attention and comparison to the broader LXX formats.

>
> On 08/12/2012 11:37 PM, Andrew Thule wrote:
>>
>> Thanks Chris.
>>
>> Here's an English Septuagint versification system, based upon the text
>> I got from Michael  and compared to a number of printed version.  The
>> Chapter order doesn't quite follow the KJV or NSRV convention, but it
>> does follow the Septuagints order.
>>
>> I appreciate it if you could add this so we can get an English
>> Septuagint module out.  I worked on this weekend quickly because I've
>> seen you reference you're working through another one, and I wanted to
>> get it in on your timeline.
>>
>> One question - I stuck with the names listed in the abbrevs.h and I
>> understand that the short forms as markers.  So for example the
>> Septuagint calls the Prayer of Azariah the Song of the Three Children
>> (in Greek) and Breton translate it as such - yet the marker will be
>> PrAzar.  I have no issue with that, but how do I now influence the
>> appearance of the book names (however the program deals with them).
>>
>> I see this can be done in locales, but is that the right place for it?
>>   I'd like to keep the Greek influenced names - since the original
>> language was Greek.  I.e.
>> Esias for Isaiah
>> Jermias for Jeremiah
>> Osee for Hosea
>> Aggaeus for Haggai
>>
>> Etc.
>
>
> There is no way for module authors to influence how titles appear in front
> ends, as far as verse pickers, searching, etc. are concerned. You can always
> add a  element before the first chapter of the book. Then the front
> end should print the title above chapter 1.
>
>
> --Chris
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Actually this whole business raises another issue.  In the collection
of modules I've been building up, I've added Dead Sea Scrolls texts as
OSIS (but have not yet created modules for them, pending working
though versification issues).

For biblical scrolls, versification isn't so much an issue, since they
can match which every versification system the module creator selects.
 For some non-biblical scrolls (such as 11QPs) since they do show up
in other versification traditions such as the Septuagint, they too can
be incorporated.   But many of the DJD translations/transliterations
are non-biblical scrolls, or fall out of typical versification
systems, though do naturally suggest one based upon where they were
found.  (i.e all 4Q... scrolls were found in Cave 4 at Qumran, all
11Q.. scrolls were found in Cave 11 etc).

What is the recommended approach for all other materials in terms of
turning them into modules?  (I guess I'm saying - I half expected
working through the versification system for the LXX and the LXXE
would have put me in a better position to create a versification
system for the DSS, but now I'm not sure which way I should go (in
terms of making a DJD module (Discoveries from the Judea Desert)?

~A

On Mon, Aug 13, 2012 at 2:43 PM, Andrew Thule  wrote:
> On Mon, Aug 13, 2012 at 1:48 PM, Chris Little  wrote:
>> Because we don't do dynamic loading of versification systems, whenever we
>> add a versification system to Sword, it takes up space in memory just to
>> hold the versification tables. Accordingly, we try to be as conservative as
>> possible in adding new versification systems. And once we have released a
>> Bible using a versification system, we can never change or remove that
>> versification system from the library. So we have to be extremely careful
>> that the versification systems we include in the library are correct.
>
> Greg wrote: "If the one you need isn't supported (I don't see LXX or
> GNT at present) then you're welcome to create such a file and submit
> it along with your module."
>
> I  must have mistook your earlier comments as well.. I implicitly took
> them to mean you're normally not open to having versifications
> submitted, but because you were already working on one be open to
> having an LXXE versification submitted.  I wouldn't have not wasted my
> time working one out if I had know there was not chance of influencing
> these things.
>
> Given that you have to be extremely careful as to which versification
> systems you include in the library, how do I go about incorporating it
> privately?  Is it a matter of including the canon_xxx.h file
> somewhere?  Whether the one I submitted gets distributed or not, I
> still require it for an English version of Brentons text for the LXXE
> module I've created.
>
>> We have two types of versification systems that we will add to Sword. The
>> first type is for particularly important individual texts, generally
>> specific manuscripts or editions. The Leningrad and Luther versifications
>> are in this category. Leningrad is used for exactly one manuscript, though
>> it appears in 2-3 modules, but it's of such significance that we added the
>> versification system to Sword. Luther, similarly, is employed specifically
>> by a set of translations by a single translator.
>>
>> The other type attempts to formalize a versification system representative
>> of numerous Bibles within a tradition. Examples of this include the KJV(A),
>> NRSV(A), Synodal, Catholic, & Catholic2. KJV(A) & NRSV(A) happen to exactly
>> match particular translations, but those versification systems are in wide
>> use beyond those translations. Synodal and the two Catholics began with the
>> versification systems of exemplar translations and were then expanded to
>> incorporate additional verses from translations within the same tradition so
>> that the system within Sword could achieve maximal coverage of the verses
>> within Bibles we might encode.
>>
>> Versification systems for particular manuscripts or editions are relatively
>> easy to define and incorporate in Sword, provided the edition they represent
>> is sufficiently significant to merit such treatment. The next versification
>> system that we'll add to Sword will be of this type, and that's Rahlfs,
>> representing Rahlfs' LXX. To construct it, I'll derive the versification
>> system based on a couple of independent encodings of Rahlfs', compare them,
>> and break any ties using the printed text of the DBG.
>
> Perhaps the Septuagint (in English) isn't significant enough to
> warrant such treatment .. but users willing to 

[sword-devel] locales.d submission Inuk: iu.conf & iu-utf8.conf

[Andrew Thule]

I've attached two files, iu.conf and iu-utf8.conf for inclusion in
locales.d.  Please feel free to add them as appropriate.  I would
appreciate a note once you make a decision one way or the other so I
can adjust my expectations accordingly.

~A


iu-utf8.conf
Description: Binary data


iu.conf
Description: Binary data
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] locales.d submission Inuk: iu.conf & iu-utf8.conf

[Andrew Thule]

On Wed, Aug 15, 2012 at 4:09 AM, Chris Little  wrote:

> I added the iu-utf8.conf file to SVN.

Thanks.


> In any case, and more to the point, your iu.conf file was just the UTF-8
> file with the locale name & encoding name changed. And the encoding it
> claimed to use, ISO 8859-10, is a Latin encoding, not a Canadian syllabics
> encoding.

There are others in locales modelled this way,  For example no.conf
and no-utf8.conf.  Now I recognize that Norsk employs the same
syllabics as English but ko.conf and hu.conf seem structured the same
way.  I used them as templates.

With respect to the use of ISO 8859-10 I was following the information
found here:
http://www.localization-translation.com/globalization-guide/localization-languages/localization-inuktitut.html

That said, it is not my intention to use a Latin encoding, and I
confess possessing a defective understanding of how the ISO 8859
system works, still endeavoured to do my best to figure out which 8859
system Inuktitut fell under.  If I've err'd simply replace the
incorrect encoding I gave it with the correct one.

The font I'm using personally is the Pigiarniq font found here:
http://www.gov.nu.ca/en/Fonts.aspx

~A

> If you meant to do a locale for Inuktitut written in Latin, I would
> recommend encoding that as UTF-8 in a iu_Latn-utf8.conf file. (And I think
> that a very worthy exercise, if some Inuktitut readers are more comfortable
> with the Latin writing system.) If a non-Unicode version is somehow useful,
> Latin-2 has the only non-ASCII character that I can determine is needed for
> Inuktitut (dark l: ł).
>
> --Chris
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] locales.d submission Inuk: iu.conf & iu-utf8.conf

[Andrew Thule]

On Wed, Aug 15, 2012 at 7:05 AM, David Haslam  wrote:
> I'm wondering whether the symbols that have a small circle above are really
> correct.
> Or whether these ought to be replaced by similar looking symbols that have a
> dot above.

I'm not seeing this problem.  I'm not seeing small circles you are.
I am seeing 'dots'. Can you attach a screenshot (perhaps offline)

>
> Question prompted by two things:
> (a) the absence in the Wikipedia page of any symbols with the small circle
> above
> (b) the observation that these symbols do not appear in the aforementioned
> online
> http://www.translitteration.com/transliteration/en/inuktitut/canadian-aboriginal-syllabics/
> Inuktitut – Canadian Aboriginal Syllabics transliteration system .
>   In fact, these symbols do not get transliterated to Latin by that form.

To be clear there are slightly different schemes and options.  This
one is used in Nunavut but will be understood everywhere the syllabics
are read.

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] locales.d submission Inuk: iu.conf & iu-utf8.conf

[Andrew Thule]

Yes, I see the comment you're directing my attention to now:

"The /ai/ ᐁ-series has been recently readopted in Nunavik; /ai/ in
Nunavut would be ᐊᐃ. Unicode gives long /aai/ as ᐂ, although I have
not seen this used in texts."

I'm not sure what to do with this however.  The bible this is suppose
to be supporting is also presenting ᐂ (not  ᐊᐃ), as is the OSIS, and
so is the USFM; the translators have not specifically spoken to.  So
the .conf file I sent is consistent with everything else I've seen.
Are you suggesting the wrong syllabic was used - or what do you
propose?

~A



On Wed, Aug 15, 2012 at 8:19 AM, Chris Little  wrote:
> On 08/15/2012 04:23 AM, David Haslam wrote:
>>
>> See also http://www.languagegeek.com/inu/inu_syllabarium.html
>>
>> "1. Long vowels are marked by a dot accent, so /laa/ is ᓛ. Long consonants
>> are shown by the appropriate final preceding the syllabic, so /ttu/ is ᑦᑐ.
>> The various dialects of the language handle the consonant clusters
>> differently, and some writers may omit the first element of the cluster
>> altogether in their writing. "
>>
>> This seems to conform my concerns. Inuktitut uses the dot accent, not the
>> small circle.
>
>
> See the end of 2. The ring above is used for . Similarly, a downward
> oriented glyph is used for .
>
> Neither of these are part of the Inuktitut Cultural Institute's
> orthographies. They would simply use  and  with a following .
>
> The original Unicode proposal for the script has a few details:
> http://www.evertype.com/standards/sl/n1441-en.html
>
>
> Updating the Bible itself to the standard orthography wouldn't be
> unwarranted. Including the standard orthographic forms in the locale file is
> really a necessity, whether the non-standard forms are included or not.
>
> --Chris
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] locales.d submission Inuk: iu.conf & iu-utf8.conf

[Andrew Thule]

On Wed, Aug 15, 2012 at 10:47 AM, Chris Little  wrote:
> On 08/15/2012 07:30 AM, Andrew Thule wrote:

> ᐂᑉᐸᖏᑦ (with a ring) would be transliterated aaippangit.
>
> If ᐄᑉᐸᖏᑦ (with a dot) was intended, that would be transliterated iippangit.

It's not clear to me where the error lies, whether it is a
Latin->Inuktitut transliteration problem, or a the wrong syllabic used
in translation or simply the difference between regional convention.
From the quote you gave it seems there are actually three
possibilities:

ᐂ, ᐄ, ᐊᐃ.

If it is simply a transliteration problem the fix should be easy
enough (search/replace) though.  I'm willing to try to resolve this.
Why do you believe ᐂ is incorrect?  Is it because of the comment '.. I
have not seen this used in texts."?  I am seeing it used in a texts
(namely the bible) so before I question anyone else, I want to ensure
I understand the concern.


> I just committed a transliterator to our SVN that will transform between
> Inuktitut written in syllabics and in Latin letters. I also placed it in the
> ICU Transform demo, if you want to test/play with it:
> http://demo.icu-project.org/icu-bin/translit .  Set Source 1 to Inuktitut
> and Target 1 to Latin (or vice versa), paste some text in the Input box, and
> click Transform.

This is a great tool!
Thanks.
~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] locales.d submission Inuk: iu.conf & iu-utf8.conf

[Andrew Thule]

It's all helpful David .. I'm no expert in Unicode either, and am
learning way more about fonts and international support than I ever
dared previously.

~A

On Wed, Aug 15, 2012 at 11:25 AM, David Haslam  wrote:
> Andrew,
>
> As I wrote earlier, I'm no expert on Inuktitut syllabics.
>
> Just exercising curiosity and lateral thinking.
>
> Chris is much more of an expert in knowledge of Unicode than I am.
>
> David
>
>
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/locales-d-submission-Inuk-iu-conf-iu-utf8-conf-tp4650852p4650866.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] locales.d submission Inuk: iu.conf & iu-utf8.conf

[Andrew Thule]

Agreed - though I'm not convinced the convention we're seeing
suggested by the Inuit Cultural Institute has been standardized to the
extend being suggested.

The language has regional variances, and the written form didn't exist
until it was introduced initially in Greenland, later Alaska based on
the Latin alphabet, whereas the written form we're dealing with,
Qaniujaaqpait was introduce introduced into  Nunavut eventually making
its way to isolated communities (Netsilik Inuit in Kugaaruk, and
Baffin Island).  Accordingly Latin Writing systems have begun to give
way to the Qaniujaaqpait form, but still reflects regional variations
in pronunciation such as the variations on vowels you seem to have
noticed (aai,  ii,  ai).

Given that this bible represents the single largest body of writing
using these glyphs in a single tome, it should try as much as possible
to represent the greatest norm.  That said, I'm not convinced the
restrictions you've noted represent that norm.  Which means I'm apt to
favour the forms submitted (which was done in Nunavut by native
speakers):

http://www.theglobeandmail.com/news/national/translation-makes-bible-available-to-inuktitut-speakers/article4227710/

However, do as you see best.  Your judgement is well trusted.
~A

On Wed, Aug 15, 2012 at 11:37 AM, Chris Little  wrote:
> On 08/15/2012 08:08 AM, Andrew Thule wrote:
>>
>> Yes, I see the comment you're directing my attention to now:
>>
>> "The /ai/ ᐁ-series has been recently readopted in Nunavik; /ai/ in
>> Nunavut would be ᐊᐃ. Unicode gives long /aai/ as ᐂ, although I have
>> not seen this used in texts."
>>
>> I'm not sure what to do with this however.  The bible this is suppose
>> to be supporting is also presenting ᐂ (not  ᐊᐃ), as is the OSIS, and
>> so is the USFM; the translators have not specifically spoken to.  So
>> the .conf file I sent is consistent with everything else I've seen.
>> Are you suggesting the wrong syllabic was used - or what do you
>> propose?
>>
>> ~A
>
>
> I would say that the translators should be trusted as much as possible, so
> if they want to use those glyphs in the Bible, they should be left alone.
>
> However, in the locale file, we should add spellings that do not use the
>  and  glyphs for users who may use the more restrictive
> orthography defined by the Inuit Cultural Institute.
>
>
> --Chris
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] locales.d submission Inuk: iu.conf & iu-utf8.conf

[Andrew Thule]

It appears so.

Please note that 'The Inuit Cultural Institute' is (mostly) a regional
thing, not a pan-national body representing all Inuit (as much as that
would be good).  It sometimes get (Canadian) government support
(though the Department of Indian and Northern Affairs) and sometimes
not. At some point in the past it had been cut off due to
mis-management, but I think it is again funded.

Still, not all Inuit communities claim they are represented by this
group.  When the Canadian Government officially split the North West
territories, creating Nunavut, and the Nunavut government, many of the
formal functions of the Cultural Institute were transferred to the
government of Nunavut, so it's role is now limited.

~A


On Wed, Aug 15, 2012 at 11:47 AM, David Haslam  wrote:
> Has the *Inuit Cultural Institute* changed its name?
>
> The first hit in Google is  http://www.avataq.qc.ca/ Avataq Cultural
> Institute .
>
> David
>
>
>
>
>
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/locales-d-submission-Inuk-iu-conf-iu-utf8-conf-tp4650852p4650870.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] locales.d submission Inuk: iu.conf & iu-utf8.conf

[Andrew Thule]

On Wed, Aug 15, 2012 at 11:55 AM, Chris Little  wrote:
> If this is the intended spelling of these words, i.e. if aaippangit was
> intended rather than iippangit, then there's no problem with including the
> spellings that use the ring characters in the Bible. However, I would still
> add extra lines to the locale that have separate  characters for every
>  and  character. So, for example, the Exodus block would be:
>
> ᒨᓯᓯᑦ ᐂᑉᐸᖏᑦ=Exod
> ᒨᓯᓯᑦ ᐋᐃᑉᐸᖏᑦ=Exod
> 2 ᒨᓯᓯᑦ=Exod
> 2ᒨᓯᓯᑦ=Exod
>
> with the first line in its original form, followed by the form that is
> restricted to the standard orthography.

I believe it was the intended spelling.

However, your proposed solution (of including both) is a very good
one.  I see no reason why the .conf file could not be modified to
include both.  That's certainly evident in other language .conf files.
  Also some of the other language .conf files includes partial
spellings (which I wasn't willing to do in this case), so I can't see
any downside to accepting both spellings.

You say tomato, I say tomato. :)
~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Chris.

I threw the canon_lxxe.h file in ./src/sword/include/

Edited ./src/sword/src/mgr/versemgr.cpp

Added:
#include  // LXXE v11n system

and;
systemVerseMgr->registerVersificationSystem("LXXE", otbooks_lxxe,
ntbooks, vm_lxxe);

recompiled and voila!
  -v   specify a versification scheme to use (default is KJV)
 Note: The following are valid values for v11n:
Catholic
German
KJV
KJVA
LXXE  <-- NOW HERE
Leningrad
Luther
MT
NRSV
NRSVA
Synodal
Vulg

The versification shows and up, but I still get errors when I make my
module.  Specifically:
when is use it with "osis2mod -v LXXE" I get

Error reading ulBuffNum
Error reading ulBuffNum

The var ulBuffNum shows up only in src/modules/common/zverse.cpp in:
zVerse::findoffset   - Finds the offset of the key verse from the indexes

Have I missed setting a value somewhere (uIBuffNum) that defines
offsets?  Any recommendations how I can fix this?

~A

~A

On Mon, Aug 13, 2012 at 4:47 PM, Chris Little  wrote:
> On 08/13/2012 11:43 AM, Andrew Thule wrote:
>>
>> Greg wrote: "If the one you need isn't supported (I don't see LXX or
>> GNT at present) then you're welcome to create such a file and submit
>> it along with your module."
>>
>> I  must have mistook your earlier comments as well.. I implicitly took
>> them to mean you're normally not open to having versifications
>> submitted, but because you were already working on one be open to
>> having an LXXE versification submitted.  I wouldn't have not wasted my
>> time working one out if I had know there was not chance of influencing
>> these things.
>
>
> In saying "in general I would not accept any submissions of versification
> systems" I was trying to discourage any efforts expended towards creating a
> new versification system. We accepted a versification system submission of
> sorts under very special circumstances, but have since removed it since it
> went unused. I cannot foresee any circumstances under which we would accept
> a versification system submission, but I wouldn't rule it out categorically.
>
>
>> Given that you have to be extremely careful as to which versification
>> systems you include in the library, how do I go about incorporating it
>> privately?  Is it a matter of including the canon_xxx.h file
>> somewhere?  Whether the one I submitted gets distributed or not, I
>> still require it for an English version of Brentons text for the LXXE
>> module I've created.
>
>
> I suppose you could add your .h file to include and add your system to the
> versification manager. If you grep the source for 'leningrad' add add your
> system to all of the same structures where that appears, you should get a
> functioning library with your versification system. The modules you build
> using this versification system would only be usable by persons with the
> same patch to Sword, though.
>
>
>> Perhaps the Septuagint (in English) isn't significant enough to
>> warrant such treatment .. but users willing to generate their own
>> versification systems, especially ones based upon historic documents,
>> should still be able to influence module creation shouldn't they?
>> Module creation presupposes a versification system, and it seems (to
>> spectators at least) there's been pressure last few revisions to open
>> up support for more.  Personally, I don't care one way or the other if
>> Crosswire is not interestd in the one I just submitted.  I am
>> interested though (as a module creator) that every time I OSIS2MOD my
>> LXXE it appends ridiculous amount of verses onto chapters in a
>> versification system neither the underlying Greek, or the English
>> translation employ.
>>
>> So restricting module creation to versification system 'officially
>> sanctioned' by Crosswise, however sound the logic behind imposing
>> distribution restrictions, seems arbitrary.  Either provide an
>> official Septuagint versification system close, or allow the user to
>> specific their own.
>
>
> Rest assured that I am absolutely committed to defining a versification
> system that satisfies your needs for a Brenton 

[sword-devel] ESV: Red Letter Edition Errors in [Matt 18:10][Matt 18:15][Matt 20:1] - Xiphos and Bibletime both show this error

[Andrew Thule]

I've tested this in both Xiphos and Bibletime and the 'Red Letters' of
Jesus' words appears black, not read in [Matt 18:10] and [Matt 18:15].
 There may be more instances (such as [Matt 20:1]), but these are the
three I've found.

In [Matt 18:10] Jesus' words follow an inter-verse title.  He says
"See that you do not despise one of these little ones. For I tell you
that in heaven their angels always see the face of my Father who is in
heaven" yet his words are not 'RED' in Xiphos or Bibletime.

In [Matt 18:15] Jesus' words again follow an inter-verse title.  He
says "If your brother sins against you, go and tell him his fault,
between you and him alone. If he listens to you, you have gained your
brother" yet again his words are not 'RED' in Xiphos or Bibletime.

[Matt 20:1] seems the same.

Is this a problem with the module, a bug in both Xiphos and Bibletime
or perhaps libSword?

~A

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Alternate Versification question

[Andrew Thule]

Yes.  Using debug produces little of value but I will run further test in
verbose mode later today and produce output. That said, I've sen the same
errors produced by working modules, that keep working, so I'm less sure now
than earlier those errors are related.

~ A

On Thursday, August 16, 2012, David Haslam wrote:

> Andrew,
>
> Some sanity checks before further work by others on the list
>
> Are you using *osis2mod* to make a compressed module (ztext) or a raw text
> module?
>
> Do you get the same error message for both?
>
> Have you tried any of the debug options?
>
>
> David
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/Alternate-Versification-question-tp4650784p4650882.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ESV: Red Letter Edition Errors in [Matt 18:10][Matt 18:15][Matt 20:1] - Xiphos and Bibletime both show this error

[Andrew Thule]

Are you seeing them though in Xiphos or Bibletime, ( can anyone else
recreate this) or is it just me?
~

On Thursday, August 16, 2012, David Haslam wrote:

> These verses display correctly as red text in both *xulsword* and in *Bible
> Desktop*.
>
> Even in *xiphos.exe 3.1.5-webkit* (Windows) these display correctly, with
> or
> without headings shown.
>
> David
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/ESV-Red-Letter-Edition-Errors-in-Matt-18-10-Matt-18-15-Matt-20-1-Xiphos-and-Bibletime-both-show-thisr-tp4650880p4650881.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ESV: Red Letter Edition Errors in [Matt 18:10][Matt 18:15][Matt 20:1] - Xiphos and Bibletime both show this error

[Andrew Thule]

Yes, I just tested in Windows, and it works for me in windows, but not in
Linux.  The difference being that I'm running the stock package in Windows,
but compiling from source in Linux, Bibletime, Xiphos, and Sword.

Sounding like it is my (Linux) install only. :(

~A

On Thursday, August 16, 2012, David Haslam wrote:

> These verses display correctly as red text in both *xulsword* and in *Bible
> Desktop*.
>
> Even in *xiphos.exe 3.1.5-webkit* (Windows) these display correctly, with
> or
> without headings shown.
>
> David
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/ESV-Red-Letter-Edition-Errors-in-Matt-18-10-Matt-18-15-Matt-20-1-Xiphos-and-Bibletime-both-show-thisr-tp4650880p4650881.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ESV: Red Letter Edition Errors in [Matt 18:10][Matt 18:15][Matt 20:1] - Xiphos and Bibletime both show this error

[Andrew Thule]

It's looking like its my installation only.  Perplexing.  Sorry for the
false alarm.
~ A

On Thursday, August 16, 2012, David Haslam wrote:

> I already mentioned Xiphos, and I didn't look at BibleTime.
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/ESV-Red-Letter-Edition-Errors-in-Matt-18-10-Matt-18-15-Matt-20-1-Xiphos-and-Bibletime-both-show-thisr-tp4650880p4650888.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ESV: Red Letter Edition Errors

[Andrew Thule]

Yes, my compiled version is kept up to date, and currently r2715, and only
noticed some time after 2703.  Glad I wasn't imagining it.

On Thursday, August 16, 2012, Karl Kleinpaste wrote:

> By the way, the bug I reported below in March also has yet to be addressed.
>
> http://www.crosswire.org/pipermail/sword-devel/2012-March/037501.html
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Speech synthesis voices?

[Andrew Thule]

That doesn't seem to imply it's not needed.  Rather, doesn't it seem to
imply the implementation should be generic, modular and bind to a variety
text to voice interfaces.

I know of a blind network admin.  He highlights nothing, rather festival
reads everything to him (far more quickly than I can hear what is being
said), and he has a 'Braille screen' (which more looks like a special
keyboard than a screen).

The nice thing about the suggestion for Sword to support the IVONA text to
speech engine more directly is IVONA's emphasis on Android devices, which
are making in-roads in the visually impaired community, as an accessibility
device.

Pondering it, perhaps this feature recommendation should be more geared to
the folks who work on Andbible.


On Saturday, August 18, 2012, DM Smith wrote:

> Not sure it is needed. On the Mac one can highlight text and have it read
> in a voice of their choice. And yes it reads punctuation as that is
> assistive to the blind.
>
> Linux can read text (festival?) but I've never bothered to look into it.
> Xiphos builds it in.
>
> It can be done in Java, see:
> http://today.java.net/pub/a/today/2006/04/13/vocal-java.html
>
> In Him,
> DM
> Cent from my fone so theer mite be tipos. ;)
>
> On Aug 18, 2012, at 10:31 AM, David Haslam 
> >
> wrote:
>
> > I've just added this idea "* Per module assignment of speech synthesis
> > voices, or none." in
> > http://crosswire.org/wiki/Frontends:FeatureList#General_UI_features
> > http://crosswire.org/wiki/Frontends:FeatureList#General_UI_features
> >
> > My suggestion is prompted by learning about the  http://www.ivona.com/IVONA
> > *TTS Engine* for Android, and the choice of voices available for various
> > languages.
> >
> > Some languages already have more than one voice. e.g. Geraint or Gwyneth
> for
> > Welsh.
> >
> > "Geraint and Gwyneth, first natural sounding Welsh voices are now
> available,
> > for individuals and non-commercial entities in the UK for free, as a
> result
> > of partnership between the Welsh Government, the Royal National
> Institute of
> > Blind People and IVONA. "
> >
> > Arfon Jones just installed this with his Android phone, and has used it
> > successfully with *and-bible* to read passages from the WelBeiblNet
> module.
> > He's very pleased with it. Minor quirks are the occasional reading out of
> > the word "comma" when the punctuation is present.
> >
> > btw.  IVONA is still in Beta, and is free of charge until the end of the
> > Beta period.
> > /I'm merely using this as an example, not seeking to advertise on their
> > behalf./
> >
> > This is something for front-end developers to consider, in as much as it
> > relates to the UI and the platform, as well as any preloaded TTS engine
> > and/or installed TTS application.
> >
> > David
> >
> >
> >
> > --
> > View this message in context:
> http://sword-dev.350566.n4.nabble.com/Speech-synthesis-voices-tp4650893.html
> > Sent from the SWORD Dev mailing list archive at Nabble.com.
> >
> > ___
> > sword-devel mailing list: sword-devel@crosswire.org 
> > http://www.crosswire.org/mailman/listinfo/sword-devel
> > Instructions to unsubscribe/change your settings at above page
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ESV: Red Letter Edition Errors

[Andrew Thule]

Another observation related to this bug is that it doesn't seem to honour
   tags in the first couple of verses either.
Look at [Psa 116:1-2], [Psa 118:1-2] in r2715 against earlier stock
versions.

Perhaps there are other tags not being honoured.
~A

On Thursday, August 16, 2012, Karl Kleinpaste wrote:

> It's a (recent) sword problem.
>
> I concur that in Xiphos 3.1.5-win32, all the red letters look fine.
> That's with a stock libsword as of when 3.1.5 was released (though
> current SVN then, as built by Greg).  But on my usual Linux systems, the
> breakage is seen.  (FYI, also Matt 25:1,14,31.)  There, sword is -r2715.
>
> I happen to have an old -r2679 tree lying around.  So I rebuilt that,
> installed it...and now my Linux Xiphos doesn't show the problem.
>
> Somewhere between 2679 and 2715, this was broken in Sword.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org 
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Speech synthesis voices?

[Andrew Thule]

How at the system level currently does the application differentiate
an active pane from an inactive one (based upon mouse-clicks)?  I'm
asking in ignorance incidentally.

It seems to me most applications, including Bibletime and Xiphos have
a 'sense' of active window vs inactive.  When I click on a window and
select the 'up and down' arrow, different things happen depending upon
which pane the application has 'active'.  With respect to text to
voice synthesis, shouldn't behaviour be the same?

If the active pane is the bible pane, the bible text is what should be
spoken.  If the commentary pane is active it should be the commentary
one.  Which presupposes that application developers provide some
accessibility feature that allows them to switch between panes
(windows) etc, be it keystroke or some other methods.

*shrugs*
~A

On Sun, Aug 19, 2012 at 5:57 PM, Karl Kleinpaste  wrote:
> Greg Hellings  writes:
>> TTS never struck me as something that is properly handled by the
>> application but should only be offered on the system level
>
> Bear in mind that I implemented Read Aloud back in the days of Fedora 5
> (2006).  I have no memory of there being _any_ system-level TTS support.
> The fact that I found Festival available at all was an accident.
>
> That said, how TTS is done "at the system level" is a pretty funny
> concept.  That is, if Xiphos isn't doing Read Aloud directly, but the
> user is expecting it "at the system level," what shall he expect to
> happen?  Every time he navigates a verse, the entire Bible chapter, as
> well as at least the commentary verse and possibly the entire commentary
> chapter, is displayed.  Shall TTS read both Bible and commentary verse
> in their entirety?  NETnote Ecc 1:1 is 8Kbytes of text, and takes nearly
> 12 minutes to speak.  How does one, at the system level, tell the system
> to read one pane and not another, and within one pane, to read only a
> certain slice of text?  I simply don't know.
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Rahlfs' LXX in experimental/Rahlfs v11n

[Andrew Thule]

Thanks Chris.

I've heard through the grapevine that Rick Brannan at Logos Software has
been beating his head against his desk over versification while working on
a digital LXX as well.

I'm half tempted to contact him; compare notes.

~A

On Monday, August 20, 2012, Chris Little wrote:

> I posted a new Rahlfs' LXX module to the experimental repository. I
> haven't tested it extensively, and there are some tricky parts of the text
> that may easily have been imported incorrectly. But it does at least employ
> the text's own versification system.
>
> The module corrects quite a few errors present in the CCAT text's
> morphology, and I've included the morphology codes in their original form
> (Packard) and converted them to Robinson's morphology. The Beta
> transliterated form of each word is also included in their xlit attributes,
> which depends on the OSISXlit filter that I haven't actually written yet.
> The current version includes the Greek lemma for each word, but I'll
> include Strong's numbers in the next release.
>
> Using the module requires that you use Sword SVN head, since it uses the
> new Rahlfs v11n. Well, it will work, with older versions of Sword, but the
> versification will be incorrect.
>
> There are empty verses and chapters in the module. I know. It's not an
> error. Don't report them unless you've actually confirmed there is an error
> by consulting a printed Rahlfs.
>
> --Chris
>
>
>
> __**_
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/**mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page