On 12/28/2014 09:21 AM, David Haslam wrote:
> Would it not be rather useful for the module management component of SWORD
> front-ends to do something proactively when a module is installed that
> obsoletes an already installed module?
This is part of today's hacking on Xiphos. There is 4.0.0b in
h
On 12/28/2014 12:06 PM, David Haslam wrote:
With Chris being otherwise engaged, there's a crying need for an accomplished
Python programmer
to pick up where he last left off on developing and debugging the OSIS
converter usfm2osis.py
There are several issues in the CrossWire tracker, should anyo
Hi Robert,
" (e.g., when \d is used as a paragraph type marker with verses
logically "inside" the \d marker which is not actually documented [nor
banned] in the USFM specification)"
This is the subject of a separate (ongoing) email discussion that I started
the other day.
Actual thread titl
> On Dec 29, 2014, at 2:28 PM, Robert Hunt wrote:
>
> On 30/12/14 06:29, Peter von Kaehne wrote:
>> It is very well written and neatly done and does its job with near
>> perfection. I would welcome contributions to it, as long as they are
>> equally well done.
> Just for your info: usfm2osis.py
On 30/12/14 08:47, Peter Von Kaehne wrote:
As it stands - and I guess apart from David and Chris I
am probably one of the most prolific users of this and the
last, Perl based script, the occasions where I ended up in a
cr
As it stands - and I guess apart from David and Chris I am probably one of the most prolific users of this and the last, Perl based script, the occasions where I ended up in a crash are few and far in between. Much more often bad USFM produces bad OSIS, non validating OSIS, rather than crashes.
If you provide undefined/invalid input then the behavior of a convenience
script being undefined should be no surprise. It is not the place of this
script to be a USFM verification tool.
--Greg
On Dec 29, 2014 2:28 PM, "Robert Hunt" wrote:
> On 30/12/14 06:29, Peter von Kaehne wrote:
>
> It is
On 30/12/14 06:29, Peter von Kaehne wrote:
It is very well written and neatly done and does its job with near
perfection. I would welcome contributions to it, as long as they are
equally well done.
Just for your info: usfm2osis.py basically treats each USFM book as
> Gesendet: Montag, 29. Dezember 2014 um 18:13 Uhr
> Von: "Peter Von Kaehne"
>
> > Gesendet: Montag, 29. Dezember 2014 um 17:29 Uhr
> > Von: "Peter von Kaehne"
>
> >
> > I think the first task should be to evaluate JIRA's list and close down
> > as "won't fix" or as otherwise invalid what sh
FreSegond should not have been made using VulSearch.
Version 1.6 is still in the CrossWire Attic repo.
That used a versification that should have been OK as far as the numbering
of the Psalms.
When the module was created with the DC books added it should really have
been a separate module!
e.g. L
> Gesendet: Montag, 29. Dezember 2014 um 17:29 Uhr
> Von: "Peter von Kaehne"
>
> I think the first task should be to evaluate JIRA's list and close down
> as "won't fix" or as otherwise invalid what should not get done. Also
> sort feature requests from bugs. I have done now some of this.
Have
> On Dec 29, 2014, at 12:31 PM, Peter von Kaehne wrote:
>
> On Mon, 2014-12-29 at 11:45 +, Martin Denham wrote:
>> Hi,
>>
>> Regarding: 'JSword frontends will be able to download these modules
>> only once the Cron had its nightly run re permission update and zip
>> making.'
>> See the thre
If that happens then it becomes a filter and front end issue. But OSIS and
the engine would be correct, and you should target that, then file bugs
with such places where they render it improperly to allow each application
to determine whether its rendering is proper.
Compare your fear of misplaced
On Mon, 2014-12-29 at 11:45 +, Martin Denham wrote:
> Hi,
>
> Regarding: 'JSword frontends will be able to download these modules
> only once the Cron had its nightly run re permission update and zip
> making.'
> See the thread on this list entitled 'Missing ZIP files'
>
>
> I don't think th
On Mon, 2014-12-29 at 11:43 -0500, DM Smith wrote:
> Python is a pretty easy language for a programmer to learn. I’ve read a book
> on how to program in it. There’s a nice tutorial on the python website. But
> I’ve not done any serious programming in python. Just maintenance and
> debugging.
I
On 29/12/14 16:43, DM Smith wrote:
Python is a pretty easy language for a programmer to learn. I’ve read a book on
how to program in it. There’s a nice tutorial on the python website. But I’ve
not done any serious programming in python. Just maintenance and debugging.
Thanks for pointing me tow
Python is a pretty easy language for a programmer to learn. I’ve read a book on
how to program in it. There’s a nice tutorial on the python website. But I’ve
not done any serious programming in python. Just maintenance and debugging.
The only thing I found bothersome was the strict use of indent
Barry,
The Perl script was not comprehensive in terms of USFM tag coverage.
No further work is expected for usfm2osis.pl
usfm2osis.pl is now deprecated.
The Python script really is the way forward, despite its issues. Please see
http://crosswire.org/wiki/Converting_SFM_Bibles_to_OSIS#usfm2osis
usfm2osis was originally written in perl. Chris re-wrote it in python. It has
progressed/diverged significantly since then.
In Him,
DM
> On Dec 29, 2014, at 11:14 AM, Barry Drake wrote:
>
> On 28/12/14 20:06, David Haslam wrote:
>> With Chris being otherwise engaged, there's a crying n
Based on user feedback it appears that the Psalms read out in the user's
church and in their printed Bibles have a different number to the Psalms in
FreSegond and FreCrampon. I find that few, if any, Christians I
communicate with, outside of the Sword lists, are familiar with the
different versifi
I agree with Greg that the begin title and the begin verse should be reversed.
That, of course, will result in the orphaning of the verse number from the
title, placing the verse number at the beginning of the line preceding the
title.
I think that we should approach this as two issues: proper
Chris Little commented here in an issue for the FreSegond module
http://www.crosswire.org/tracker/browse/MOD-280
We should switch to Wikisource's edition, possibly using it as a basis for a
new versification system:
https://fr.wikisource.org/wiki/Bible_Segond_1910
---
In the Wikisou
On 28/12/14 20:06, David Haslam wrote:
With Chris being otherwise engaged, there's a crying need for an accomplished
Python programmer to pick up where he last left off on developing and debugging
the OSIS
converter usfm2osis.py
Hi David . I'm very interested in this project. I looked at
Martin,
In our FreSegond module, which was built from TextSource=Vulsearch to the
Vulg v11n,
Psalm 135 begins, (Psalms 135:1) Louez l'Éternel, car il est bon, Car sa
miséricorde dure à toujours!
In other French Bibles, those that follow the MT numbering system for
Psalms, this is Psalm 136.
e.g.
In the USFM Reference, the "d" in the \d marker denotes "descriptive", which
can be a tad misleading.
It is in fact reserved for the canonical Psalm titles (translated from the
Hebrew), as illustrated in the Example provided in the User Reference.
· Descriptive title (or "Hebrew subtitle")
· Som
Greg's suggestion had already been considered, but surely that would lead to
the following visual effect in front-ends?
Verse 1 tag on a line of its own ("widowed")
The title text on its own line.
A blank line for the paragraph element.
The rest of the text for verse 1.
The rest of the Psalm
My point is that this is a USFM to OSIS conversion issue, and may
require some hand editing. It really would then not be a SWORD issue at
all, once the text is converted properly. The canonical title could
live within the first verse, while the descriptive title would fall
outside of it. The
Based on your description last night and this OSIS snippet out looks like
the problem is with the sID and not the eID. Switch these two tags and it
should be fixed:
The title is a wholly included part of verse one and should be properly
nested as such.
--Greg
On Dec 29, 2014 6:07 AM, "David Hasl
Martin Denham has reminded us indirectly of this useful resource:
http://www.bibliquest.org/Bibliquest/Bibliquest-Discordances_de_numerotation_des_versets.htm
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Alternate-Versifications-tp4654366p4654441.html
Sent from
David Troidl wrote,
"There is a global attribute in OSIS for distinguishing canonical content
from non-canonical. Every element defaults to one state or the other.
The two should not be mixed together indiscriminately. "
That's not the issue here, David.
The descriptive Psalm titles in the Bi
There is a global attribute in OSIS for distinguishing canonical content
from non-canonical. Every element defaults to one state or the other.
The two should not be mixed together indiscriminately.
David
On 12/28/2014 3:24 PM, Greg Hellings wrote:
(Assuming you meant to say you can't move t
The French reply in Martin's message reads,
"Your answer and the link that you send us gives us no solution, gentlemen
developers, correct just the chapter and verses contain errors, this is the
right choice and make an effort, thank you"
The background is the well known difference in numbering P
Psalm 51 is one of four Psalms that have TWO verses assigned to the
descriptive canonical title.
Here's the first few lines of USFM
\c 51
\cl Salm 51
\d
\v 1 D'ar mestr-kaner; salm David.
\v 2 Pa zeuas Natan ar profed d'e gavout, goude ma voe aet David war-zu
Bat-Sheba.
\p
\v 3 O Doue! Gra trugar
The biggest problem constantly reported to me is the offset Psalms in
French Bibles.
One e-mail from yesterday:
There some mistakes in the numbering of french version for ex the psam 135
is supposed to be psalm 136.you could check the psalms for mistake like
that. Check the FreSegond version for
Hi,
Regarding: 'JSword frontends will be able to download these modules only
once the Cron had its nightly run re permission update and zip making.'
See the thread on this list entitled 'Missing ZIP files'
I don't think this cron job is running automatically yet and I can see that
atleast recver.
Actually, the number 66 is not quite right as a count of Psalms.
In four Psalms, the canonical title occupies the first TWO verses! These are
Psalms 51,52,54,60.
For these Psalms, there is an offset of two for the remaining verses, and so
the final two verses fall outside the V11N.
Ps.51.20-21
P
A little information, only posted here so that you know that I know.
These are the [extracted] references for verses appended by osis2mod when I
did a test build for the Breton KOAD21 Bible that now has 8 books from the
OT as well as the complete NT.
Num.30.17
Ps.3.9
Ps.4.9
Ps.5.13
Ps.6.11
Ps.7.1
Thanks DM, for your various comments.
For now, here's the OSIS snippet for the same part of Psalm 11.
Salm 11
D'ar mestr-kaner; salm David.
En em dennet on da gavout an AOTROU. Penaos eta e
lavarit da'm ene: Tec'h en ho menez evel ul labous?
Rak setu, ar re zrouk a stegn ar
wareg; kempennet o d
38 matches
Mail list logo
