Practically, this is easy to implement. The entire concept of managing
versification systems is contained in this file:
I know, i saw that there is no real need to store v11n description
statically.
This IMPLEMENTATION isn't where the work lies. Externalizing v11n
systems has always been a l
Dear Konstantin,
Thank you for the suggestion and enumeration of the many benefits of
having canon definitions stored outside of files.
Practically, this is easy to implement. The entire concept of managing
versification systems is contained in this file:
http://crosswire.org/svn/sword/trunk/sr
Dne 14.7.2011 16:50, Greg Hellings napsal(a):
They live within the SWORD source. If you have the swig executable
you can enable bindings. I prefer to do it with CMake like follows:
You seem to be using Fedora as well. Do you think it would be possible
to add Python bindings to the sword Rawhi
The subtle difference between my points #2 & #3 is in the word "readily".
If the only way of getting to non-KJV content is by typing in a reference,
that's not quite as "ready for the user experience" as simply using built in
navigation controls, whether drop-downs or lookups or what have you.
Bu
The v11n of the Psalms in some French Bibles is not that simple!
I explain as follows: where CT denotes Canonical Title.
In French Bibles, there are four categories of Psalms ...
1. Without a CT
2. With a CT, but normal text starts within verse 1
3. With a CT, but normal text starts
On Thu, Jul 14, 2011 at 10:24 AM, David Haslam wrote:
> See recently added section:
>
> http://crosswire.org/wiki/Alternate_Versification#Front-end_support_for_av11n_.3F
>
> In theory, there are several aspects to consider when looking at front-end
> application support for alternate versification
There is no CrossWire v11n defined for French Bibles yet. I put in a strong
plea for such last week.
Moreover, two of the French Bibles in CrossWire av11n repo do not have v11n
specified in their conf files.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/osis2mod-
See recently added section:
http://crosswire.org/wiki/Alternate_Versification#Front-end_support_for_av11n_.3F
In theory, there are several aspects to consider when looking at front-end
application support for alternate versification:
1. Can the module be installed at all, without causing the
They live within the SWORD source. If you have the swig executable
you can enable bindings. I prefer to do it with CMake like follows:
mkdir build && cd build
cmake -DSWORD_BINDINGS=Python ..
make -j5 && sudo make install
pushd bindings/swig/python
python setup.py build
sudo python setup.py inst
Dne 14.7.2011 02:11, Greg Hellings napsal(a):
I accept your challenge. For those of you with the ability to build
and install the Python bindings, you will find an (our first, in fact)
example Python script named av11n.py. It does as you suggest for an
Stupid question ... where does these bind
Dne 14.7.2011 12:10, Konstantin Maslyuk napsal(a):
As many v11ns exist already and even more can appear i would suggest to
add ability to load v11n from file. Module can contain one binary file
that will be loaded by SWMgr on module initialization, this file will
fully describe v11n and mappings.
Dne 13.7.2011 19:46, Chris Little napsal(a):
The v11n used for Czech sounds similar to what is supposed to be
employed for French Bibles.
Which is available where? I don't see it on
http://www.crosswire.org/wiki/Alternate_Versification/System_Identification.
Thanks a lot,
Matěj
--
http://w
On Thu, Jul 14, 2011 at 2:08 AM, Peter von Kaehne wrote:
> On Wed, 2011-07-13 at 23:45 -0500, Greg Hellings wrote:
>> Well as for current status I know BibleTime is ready for it and Xiphos
>> is not.
>
> Xiphosw is using it well enough to not crash. I think this applies to
> all current libsword a
As many v11ns exist already and even more can appear i would suggest to
add ability to load v11n from file. Module can contain one binary file
that will be loaded by SWMgr on module initialization, this file will
fully describe v11n and mappings.
Advantages are that you have only v11ns you are us
On Wed, 2011-07-13 at 23:45 -0500, Greg Hellings wrote:
> Well as for current status I know BibleTime is ready for it and Xiphos
> is not.
Xiphosw is using it well enough to not crash. I think this applies to
all current libsword applications. It is just that some parts of a
module are less acces
15 matches
Mail list logo
