Troy A. Griffitts wrote:
There are a number of issues that need to be addressed if we
change the modus operandi of verse number handling (which we are doing in
spite of your insistence that we are not). There are merits of using the
verse tag to provide the verse number, and there are merits t
Chris,
There are a number of issues that need to be addressed if we
change the modus operandi of verse number handling (which we are doing in
spite of your insistence that we are not). There are merits of using the
verse tag to provide the verse number, and there are merits to not use t
Joachim Ansorg wrote:
I was working on a new module anf run into trouble with your new module.
The module has titles so I think osis2mod put the title tag into each verse
followed by the verse tag.
Correct. We've always put titles into the verse that immediately
follows them.
My problem: That i
I agree with Joachim.
Terry
On Wed, 2004-07-21 at 04:29, Joachim Ansorg wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Chris,
>
> I was working on a new module anf run into trouble with your new module.
> The module has titles so I think osis2mod put the title tag into each verse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
I was working on a new module anf run into trouble with your new module.
The module has titles so I think osis2mod put the title tag into each verse
followed by the verse tag.
My problem: That is nowhere supported atm.
If I want to implement
I think maintaining OSIS markup is good. But I also see some problems here.
To be clear, my real intent was to store content more accurately &
completely than we had been. Everything else is just a side effect of
doing things the right way.
It's already hard to maintain own filters to make sure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Chris,
thanks for working on the module updates.
> In particular, verse tags are included within each verse. This means
> you can render verse numbers on the basis of markup contained in the
> text rather than on Sword's hardcoded verse numbers.
Troy A. Griffitts wrote:
Hey Chris,
I'm not sure you understood or answered any of my concerns.
oYou addressed your previous email to frontend developers
informing them of your markup changes. From this, I was under the
impression that you actually thought frontend developers needed
Hey Chris,
I'm not sure you understood or answered any of my concerns.
o You addressed your previous email to frontend developers informing
them of your markup changes. From this, I was under the impression that
you actually thought frontend developers needed to know about your
markup
Troy,
Troy A. Griffitts wrote:
I think we need more discussion before changing modus oparandi on
verse rendering for all clients of the API.
A few bylaws we've adhered to which are valuable to the users of the
engine:
oA client of the engine should only have to render Bible vers
Chris,
Thanks for all the hard work.
I think we need more discussion before changing modus oparandi on verse
rendering for all clients of the API.
A few bylaws we've adhered to which are valuable to the users of the
engine:
o A client of the engine should only have to render Bible ve
I just posted three new modules to the beta site (actually two are
updated, but they're from scratch and significantly different from their
previous versions). They are the AB (Apostle's Bible), EMTV (English
Majority Text Version), and UKJV (Updated King James Version)--all in
English. They
12 matches
Mail list logo
