Announcing *BibleTech: 2013! Seattle, Washington, March 15/16 : 2013*
Preparations are underway for BibleTech 2013. Set aside March 15-16, 2013
for a fresh look into the exciting ways that technology is affecting the way
we study, visualize, and communicate the Scriptures.
See http://bibletechco
On 08/13/2012 08:09 PM, David Haslam wrote:
> The relevant paragraph is,
>
> "In USFM, character level markup can be nested (embedded) within a paragraph
> element, or another character element, but (depending on the way in which
> the markers are written) does not necessarily cancel out the previo
The relevant paragraph is,
"In USFM, character level markup can be nested (embedded) within a paragraph
element, or another character element, but (depending on the way in which
the markers are written) does not necessarily cancel out the previous
marker's attributes. Paratext (a UBS translation e
On 08/13/2012 08:18 PM, Kahunapule Michael Johnson wrote:
I thought it would be odd for USFM to quietly deprecate explicit style end
markers in footnotes. I checked again, and it didn't.
In http://ubs-icap.org/chm/usfm/2.35/index.html?syntax_notes.htm ending a style
with another style and with
On 08/13/2012 07:48 AM, Chris Little wrote:
> Because we don't do dynamic loading of versification systems, whenever we add
> a versification system to Sword, it takes up space in memory just to hold the
> versification tables. Accordingly, we try to be as conservative as possible
> in adding ne
I thought it would be odd for USFM to quietly deprecate explicit style end
markers in footnotes. I checked again, and it didn't.
In http://ubs-icap.org/chm/usfm/2.35/index.html?syntax_notes.htm ending a style
with another style and with an explicit end marker are both listed as
acceptable. Altho
On 08/13/2012 12:10 PM, Andrew Thule wrote:
Actually this whole business raises another issue. In the collection
of modules I've been building up, I've added Dead Sea Scrolls texts as
OSIS (but have not yet created modules for them, pending working
though versification issues).
For biblical scr
On 08/13/2012 11:43 AM, Andrew Thule wrote:
Greg wrote: "If the one you need isn't supported (I don't see LXX or
GNT at present) then you're welcome to create such a file and submit
it along with your module."
I must have mistook your earlier comments as well.. I implicitly took
them to mean yo
Actually this whole business raises another issue. In the collection
of modules I've been building up, I've added Dead Sea Scrolls texts as
OSIS (but have not yet created modules for them, pending working
though versification issues).
For biblical scrolls, versification isn't so much an issue, si
On Mon, Aug 13, 2012 at 1:48 PM, Chris Little wrote:
> Because we don't do dynamic loading of versification systems, whenever we
> add a versification system to Sword, it takes up space in memory just to
> hold the versification tables. Accordingly, we try to be as conservative as
> possible in ad
That certainly explains the apparent disorder - thanks for that.
On Mon, Aug 13, 2012 at 12:11 PM, Chris Little wrote:
> On 08/12/2012 11:23 PM, Andrew Thule wrote:
>>
>> I was making changes to the LXX2012 version - but then quit. I
>> decided to instead work on getting out a version with origi
Because we don't do dynamic loading of versification systems, whenever
we add a versification system to Sword, it takes up space in memory just
to hold the versification tables. Accordingly, we try to be as
conservative as possible in adding new versification systems. And once
we have released
On 08/12/2012 11:23 PM, Andrew Thule wrote:
I was making changes to the LXX2012 version - but then quit. I
decided to instead work on getting out a version with original text.
I've created a versification system based upon an 1857 edition of
Brenton's book (and consulted 2 other versions, includ
13 matches
Mail list logo
