Using DM's suggestion I wrote a basic evaluation system to look at two
texts and compare versification contents. You can fetch it from
http://dl.thehellings.com/v11n_check.py
It requires the Sword Python bindings as well as the numpy Python
library for calculation of means and standard deviations
On 01/08/11 20:55, scribe...@gmail.com wrote:
> Many major frontends do not yet implement
> av11n so I hadn't put v11n mapping high on my list yet.
There is unfortunately here a bit of a chicken and egg situation.
Several frontend developers are on record that they will consider av11n
low priorit
Excuse me too. I really do not want anyone to hurry up. If you can create
a branch for me i would pull my work there and forget of it before the
best times. Also i will not be offended if for some reason, my work will
not be accepted.
Simply, i saw here a guy asking for complete list of dif
Dear Костя,
This is entirely my fault. v11n mapping is a big deal and I need to consider
any implementation completely before we move forward. Because of the many
projects that build on our engine, we try our hardest not to change interfaces
once we move forward. For better or worse, this make
This would be helpful when talking of reversification KJV<->Synodal.
http://crosswire.org/~kalemas/work/v11nmapping/Bible.Synodal.xml
p.s. i have done huge work making mappings system and testing this data
and a little upset that no one takes this into account.
David Haslam писал(а) в своём
Here are some of Illya's notes from 2008 on the Ohienko translation.
http://www.crosswire.org/forums/mvnforum/viewthread_thread,551
http://www.crosswire.org/forums/mvnforum/viewthread_thread,551
There is a direct link in it to a topic in the Go Bible Forum.
You'd need to be already logged in for
The xulSword program used primarily in Russia and the CIS has been
relying on Sword's own built in v11n capability since shortly after
1.6.1 was released. From that time a number of IBT texts have already
been released which use the "Synodal" verse system, including Russian
modules, Kazakh, Crimean
Writing such a utility would be trivial. Do we have any existing
modules which could be used to test it?
--Greg
2011/8/1 DM Smith :
> David's observation has got me thinking on whether there is a way to detect
> mismatches. The nature of osis2mod is to be lossless with regard to biblical
> mater
Hi Chris,
You'll be pleased to know that I didn't consciously remove any verse tags
from the excerpted Ukrainian passage tagged as Psalms 114:8:
It was done with no CL options, just using
diatheke -b Ukrainian -k "Gen - Rev"
and pasting from the above line in the captured output.
Yet if we have
Troy,
IBT hosts only one Russian language Bible module.
The others for Central Asia are:
- Crimean Tatar
- Karakalpak
- Khakas
- Kumyk
- Kyrgyz (Cyrillic)* Lingua Service/UBS
- Kyrgyz (Arabic)* Lingua Service/UBS
- Kyrgyz (Cyrillic)* Ray of Hope
- Kyrgyz (Arabic)* Ray of Hope
- Tatar
-
On 8/1/11 7:03 AM, DM Smith wrote:
David's observation has got me thinking on whether there is a way to
detect mismatches. The nature of osis2mod is to be lossless with regard
to biblical material. If a verse in the OSIS file is not in the v11n,
then it is appended it to the prior verse entry (
On 08/01/2011 10:54 AM, David Haslam wrote:
Greg recently wrote a script to measure the "matchingness" of an OSIS XML
file against each of our v11n schemes. It was reported in an earlier thread
in this mailing list.
Yes, I saw that. It's a great addition. This is a different idea: Does
an existi
For those who may have forgotten, .xsm is a .zip file with a renamed
extension.
The .xsm extension relates to the cool drag&drop install method for the IBT
MK application.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Change-to-Synodal-verse-system-tp3709069p37099
Greg recently wrote a script to measure the "matchingness" of an OSIS XML
file against each of our v11n schemes. It was reported in an earlier thread
in this mailing list.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Change-to-Synodal-verse-system-tp3709069p370989
Examining the IBT download page
http://www.ibt.org.ru/english/bible/info_bible_en.htm
http://www.ibt.org.ru/english/bible/info_bible_en.htm , there are now 16
.xsm modules (which should all be compatible with SWORD technology, assuming
av11n is supported for those that need it) and only 2 .zip mod
David's observation has got me thinking on whether there is a way to
detect mismatches. The nature of osis2mod is to be lossless with regard
to biblical material. If a verse in the OSIS file is not in the v11n,
then it is appended it to the prior verse entry (it is a bit more
complicated than t
On 01/08/11 14:55, Chris Little wrote:
> We added the SynodalP v11n specifically to support IBT's texts, and
> that's probably as much as we can do to accommodate these texts.
OK, to be sure I understand the summary of the issue:
IBT has legacy Russian Bibles that use v11n "P"
We have Russian Bib
http://www.crosswire.org/bugs/browse/MOD-166
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Change-to-Synodal-verse-system-tp3709069p3709644.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel
On 8/1/11 4:41 AM, Peter von Kaehne wrote:
Chris,
Von: Chris Little
At the time 1.6.2 was released, there were still no major Sword
apps that had been released with support for av11n to the extent
necessary to support Synodal-v11n modules. We had also only
released a couple of Synodal-v11n
This thread (plus something else) just prompted me to examine our Ukrainian
module with diatheke.
Psalms 114:8: що скелю обертає в озеро водне, а кремінь на водне джерело! Не
нам, Господи, не нам, але Йменню Своєму дай славу за милість Твою, за правду
Твою! Пощо мають казати народи: Де ж то їхній
Chris,
> Von: Chris Little
> At the time 1.6.2 was released, there were still no major Sword apps
> that had been released with support for av11n to the extent necessary to
> support Synodal-v11n modules. We had also only released a couple of
> Synodal-v11n modules and only released them to t
Peter,
Do we need to fix our Belarusian module dated 2009-12-22 ?
Versification=Synodal.
And yes - we should also raise the av11n matter with the xulsword developer,
so that he can take up any necessary actions on behalf of IBT.
David
--
View this message in context:
http://sword-dev.350566.n
At the time 1.6.2 was released, there were still no major Sword apps
that had been released with support for av11n to the extent necessary to
support Synodal-v11n modules. We had also only released a couple of
Synodal-v11n modules and only released them to the experimental
repository. According
It is probably worthwhile adding that while we had at CrossWire no Synodal v11n
based texts out ofr public consumption, IBT has been distributing many of its
modules in synodal v11n for a while.
So there is a problem beyond us few developers and testers.
Peter
Original-Nachricht -
An error in the Synodal verse system (canon_synodal.h) was fixed in
sword-1.6.2, which is great. Psalms 114:9 was missing from the verse
system, but has now been included.
My concern is that the fixed verse system has the same name as the old
one. So the many existing Synodal Sword modules are
25 matches
Mail list logo
