Having responded for the location of mid-verse titles in the USFM source
files used for a module already released (TurNTB),
but based an authorized workaround, the other examples which need to be
tested and solved
are in the USFM source files for the *Tok Pisin* Bible which Michael Johnson
Jaak,
I accepted and applied your header file patch nearly 5 months ago. Are
you telling me that you still have 549 warnings from SWORD headers?
Troy
On 06/09/2013 11:55 PM, Jaak Ristioja wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09.06.2013 23:21, Troy A. Griffitts wrote:
I am unaware that SWORD does not support mid-verse section headings.
They are the easier case, as opposed to pre-verse section headings which
require special treatment. I am simply looking for a known location in
existing module with a mid-verse heading to check and see. If you know
of one,
I believe that the issue is simply that osis2mod identifies all titles
as pre-verse titles. Someone correct me if I'm wrong, but that's the
only issue I can really imagine.
--Chris
On 6/9/2013 11:46 PM, Troy A. Griffitts wrote:
I am unaware that SWORD does not support mid-verse section
They are supported. E.g. Song of Solomon in the ESV has them. E.g. 4:16:
http://crosswire.org/study/passagestudy.jsp?key=Song+of+Solomon+4%3A16#cv
Note that some of the titles here do look weird, but they are supported.
God Bless,
Ben
-
On 09/06/13 21:23, Greg Hellings wrote:
I don't think the crosswire cert has
ever been made wildcard as those certificates can be much more
expensive. So even if it wasn't out of date you'd probably see that warning.
StartSSL Class 2 certificate (which includes wild cards) is $59.90. Is
it
Dear Greg,
Von: Greg Hellings greg.helli...@gmail.com
On Jun 9, 2013 4:28 PM, Troy A. Griffitts scr...@crosswire.org wrote:
Do all the bindings build ok? It sounded like Peter still had some troubles.
I can work with him to find the difference between his environment and mine
and resolve
Osis2mod no longer does that. Mid verse titles are left as is where they occur.
Cent from my fone so theer mite be tipos. ;)
On Jun 10, 2013, at 2:50 AM, Chris Little chris...@crosswire.org wrote:
I believe that the issue is simply that osis2mod identifies all titles as
pre-verse titles.
Glad to hear Jaak. Your patches were committed with log messages as:
r2779 | scribe | 2013-01-29 01:06:01 +0100 (Tue, 29 Jan 2013) | 2 lines
Committed patch to safely bypass warnings for unused variables in empty
virtual
On Mon, Jun 10, 2013 at 5:39 AM, Peter von Kaehne ref...@gmx.net wrote:
Dear Greg,
Von: Greg Hellings greg.helli...@gmail.com
On Jun 9, 2013 4:28 PM, Troy A. Griffitts scr...@crosswire.org wrote:
Do all the bindings build ok? It sounded like Peter still had some
troubles.
I can work
At the time we prepared the TurNTB module for release, we were told that
SWORD did not support mid-verse titles.
Accordingly, the module was built after implementing the negotiated
workarounds in the USFM file for Acts.
My difficulty is this:
Starting with received USFM files in which there are
Addendum:
When I wrote:
If it doesn't find them there, the OSIS transformations described elsewhere
(the adding of the attribute subType=x-preverse) simply doesn't happen.
I should also have included,
( and moving the section title to AFTER the verse sID milestone)
David
--
View this
Actually I just remembered another serious flaw which causes a headache
for developers using Sword. I'll write a patch ASAP.
Blessings,
Jaak
On 10.06.2013 09:43, Troy A. Griffitts wrote:
Jaak,
I accepted and applied your header file patch nearly 5 months ago. Are
you telling me that you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm working on the patch but here's a short overview of the problem,
in case discussion is required. The problem is that source code using
Sword can't do stuff like:
#include sword/versekey.h
This is VERY BAD, because we must do
#include
A bit more on titles. In the old, old osis2mod (i.e. many versions ago) the
expectation was that the only markup between verses would be titles and that
titles would occur no where else.
At that time, the code pulled all titles out of the verse, no matter where they
occurred and prefixed the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached is a patch for this. Please apply.
SHA1SUM: 9a99e34ce419ea3288a32148d431ec971fb0e675
Blessings,
Jaak
On 10.06.2013 19:38, Jaak Ristioja wrote:
I'm working on the patch but here's a short overview of the
problem, in case discussion is
DM's message clarifies where the new release is heading,
but it doesn't alter the fact that usfm2osis.py places section titles
before the eID milestone of the previous verse (when there is one).
With the new release therefore, the new osis2mod (even after recompiling for
version 1.7),
would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Argh, someone must have changed things on SVN lately, so this patch
was invalid for the current trunk... I wish you guys would learn git
or something. Anyway, here's something which should apply to SVN 2819,
I hope.
SHA1SUM:
Just to ensure there is no misunderstanding...
Paratext permits but does not enforce sub-verses in the verse tag.
The USFM Reference does not document this feature.
We often see these explicit examples:
\v 3-5a Some verse text for three and a half verses
\v 5v-7 Some verse text for three and a
Typo. Oops! (v is next to b on qwerty keyboards)
I should have given this as the first example:
\v 3-5a Some verse text for three and a half verses
\v 5b-7 Some verse text for three and a half verses
David
--
View this message in context:
Yes - I totally agree with DM - thanks for the good reminder.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/I-implore-you-tp4652437p4652478.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
Only responding to the last part below.
On Jun 10, 2013, at 3:58 PM, David Haslam dfh...@googlemail.com wrote:
Just to ensure there is no misunderstanding...
Paratext permits but does not enforce sub-verses in the verse tag.
The USFM Reference does not document this feature.
We often
Yay!!!
In Him,
DM
On Jun 10, 2013, at 8:05 AM, Troy A. Griffitts scr...@crosswire.org wrote:
Thanks Ben,
This is exactly what I was looking for. Here's the link which forces the
module to ESV:
http://crosswire.org/study/passagestudy.jsp?mod=ESVkey=Song+of+Solomon+4%3A16#cv
I see - so what really complicates things is the \p line in the example?
Because in OSIS, *p* is not a milestoneable element. It allows for mixed
(text and element) content.
And your reply includes: There may or may not be spacing before or after
the title. It is entirely unnecessary.
Yet all
DM wrote, There may or may not be spacing before or after the title. It is
entirely unnecessary.
Objection: A title as inline text wouldn't look right in a front-end.
so did you mean additional spacing ?
David
--
View this message in context:
On Jun 10, 2013, at 4:53 PM, David Haslam dfh...@googlemail.com wrote:
DM wrote, There may or may not be spacing before or after the title. It is
entirely unnecessary.
Objection: A title as inline text wouldn't look right in a front-end.
so did you mean additional spacing ?
There is a
We've had quite a few postings in Farsi (I think). It appears that it is an
attempt to do a link exchange. Can someone take a look who can read it and
provide advice?
https://www.facebook.com/crosswirebiblesociety/posts/321948371272135
Thanks.
In Him,
DM
OK - so that must surely mean that *Xiphos 3.1.5* is malfunctional.
It didn't provide the new line before a pre-verse title, so it cannot be
treating a title as a block element.
The title text had the right text style, but appeared at the end of the
verse text.
David
--
View this message in
On Jun 10, 2013, at 5:20 PM, David Haslam dfh...@googlemail.com wrote:
OK - so that must surely mean that *Xiphos 3.1.5* is malfunctional.
I think they merely use the SWORD OSISxhtmlhref render filter.
When I looked at SwordWeb today, it surrounded it with h3, which is an HTML
block element.
Hang on a mo!
Where is the mid-verse title in Song 4? I can't see one there.
The only title that URL presented me is the one above verse 1.
And why is the verse 1 tag widowed?
NB. The URL didn't force navigation to the ESV at all, despite that module
name being in the passed parameters.
When
I saw that it didn't go to the ESV too. I had to pick it on the left.
Maybe you have headings turned off. If on, you should see one immediately
before verse 16 and one in it.
In Him,
DM
On Jun 10, 2013, at 5:28 PM, David Haslam dfh...@googlemail.com wrote:
Hang on a mo!
Where is
Though I can't read Farsi, the user's own page
https://www.facebook.com/immanuel.persian has many posts with English
pictorial content that show he's a keen advocate for studying the Bible.
I had no good reason to hide his posts.
Hope that helps.
David
--
View this message in context:
Xiphos picks off pre-verse headers and outputs them wrapped with
br/b%s/bbr/br/. That's all it does. It is the
responsibility of ... something else ... to see to it that there is
adequate whitespace being generated in the chapter prior to any header.
Yes, there have always been some modules
Do the postings differ one from another?
-- DM
On Jun 10, 2013, at 5:34 PM, David Haslam dfh...@googlemail.com wrote:
Though I can't read Farsi, the user's own page
https://www.facebook.com/immanuel.persian has many posts with English
pictorial content that show he's a keen advocate for
Got it.
*Together in the Garden of Love*
but the URL behaviour is still baffling. I was using Firefox.
Which browser were you using?
David
PS. Headings were already turned on.
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/I-implore-you-tp4652437p4652492.html
Sent
I tried both Firefox and Safari.
I don't think it has to do with the browser.
-- DM
On Jun 10, 2013, at 5:38 PM, David Haslam dfh...@googlemail.com wrote:
Got it.
*Together in the Garden of Love*
but the URL behaviour is still baffling. I was using Firefox.
Which browser were you
On Mon, 2013-06-10 at 17:04 -0400, DM Smith wrote:
We've had quite a few postings in Farsi (I think). It appears that it is an
attempt to do a link exchange. Can someone take a look who can read it and
provide advice?
https://www.facebook.com/crosswirebiblesociety/posts/321948371272135
Peter has commented with a polite please don't spam in Farsi.
I don't think any further action is warranted, as we want to keep this
brother on our side.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Posts-to-CrossWire-s-Facebook-page-tp4652484p4652494.html
On Mon, 2013-06-10 at 14:34 -0700, David Haslam wrote:
Though I can't read Farsi, the user's own page
https://www.facebook.com/immanuel.persian has many posts with English
pictorial content that show he's a keen advocate for studying the Bible.
No reason to spam though. If you got admin
When Chris renamed osisruby to osisglosses it involved an update to
Makefile.am. You will need to do a distclean and rerun your autogen.
--Greg
On Jun 10, 2013 9:02 PM, Karl Kleinpaste k...@kleinpaste.org wrote:
Making all in lib
make[1]: Entering directory `/home/karl/src/bible/sword/lib'
40 matches
Mail list logo
