When I tried today to validate an OSIS XML file to
http://www.bibletechnologies.net/osisCore.2.1.1.xsd
I found a page that tells me that *ForMinistry.com is Closed*.
? Anyone know what on earth has happened to
http://www.bibletechnologies.net/
Am I the first person in CrossWire to encounter
On 05/02/14 02:38, Kahunapule Michael Johnson wrote:
In that case, it is entirely up to you to deal with chapter number
starting point translation, if necessary. I think I have dealt with
all chapter or verse out of order issues before you get them. Perhaps
I should stop generating OSIS files.
At least whoever made the change hasn't wiped clean the Wayback Machine!
http://web.archive.org/web/20131124193134/http://www.bibletechnologies.net/
There are also a few snapshots in January 2014, but I didn't bother to check
these yet.
David
--
View this message in context:
On Wed, Feb 05, 2014 at 02:23:55AM -0800, David Haslam wrote:
When I tried today to validate an OSIS XML file to
http://www.bibletechnologies.net/osisCore.2.1.1.xsd
I found a page that tells me that *ForMinistry.com is Closed*.
? Anyone know what on earth has happened to
Several developers have a local copy already. Some even prefer it for speed.
The point is that usfm2osis.py generates the full line 2 as follows:
So even with a local copy, we'd each need to edit this line to use a local
copy - every time we need to validate an OSIS file.
Or, of course, we
To shorten the URL, this link redirects to the last known good snapshot...
http://bit.ly/1dpXfeD
This is only useful for the purpose of browsing the old site, including
downloads.
Can't use it with the schema definition line of an XML file.
i.e. This is not part of a solution.
David
--
On 05/02/14 10:31, Barry Drake wrote:
Progress so far:
I altered the OSIS to make the book names work. AddPs.151 was the
main source of the problem. osis2mod made a module that worked, and
./osis2mod temp eng-webbe_osis.xml -v NRSVA gave me a module.
I'll do some more trials later.
Re: Dual Ownership
Yes, CrossWire as always had the policy of requiring ownership be also
granted to CrossWire for any contributions which get added to our
repository. This has been discussed many times and should be posted
conspicuously in multiple locations on our website (I hope it is
On 02/05/2014 12:23 AM, David Haslam wrote:
When I tried today to validate an OSIS XML file to
http://www.bibletechnologies.net/osisCore.2.1.1.xsd
I found a page that tells me that *ForMinistry.com is Closed*.
? Anyone know what on earth has happened to
http://www.bibletechnologies.net/
With what does one replace the two instances in the validation line
where the namespace was on the lost domain?
http://www.bibletechnologies.net/2003/OSIS/namespace;
I'm not sufficiently XML savvy to know how.
David
--
View this message in context:
On 02/04/2014 06:27 PM, Kahunapule Michael Johnson wrote:
On 02/03/2014 12:19 PM, DM Smith wrote:
As to numbering, I just know how the v11n work in SWORD and JSword. They assume
that chapters start at 1 and verses start at one.
Somebody is going to have to do some number translation, then.
On 02/04/2014 06:38 PM, Kahunapule Michael Johnson wrote:
On 02/03/2014 12:04 PM, Chris Little wrote:
We build modules from your sites from USFM, so what you do with OSIS doesn't
affect us.
In that case, it is entirely up to you to deal with chapter number starting
point translation, if
On 02/05/2014 12:29 PM, David Haslam
wrote:
With what does one replace the two instances in the validation line
where the namespace was on the lost domain?
"http://www.bibletechnologies.net/2003/OSIS/namespace"
The namespace can remain the same. It
Title: signature
OK, I hear two votes for me to continue
generating OSIS files, so I won't rip that part of the code out of
Haiola and reclaim the server space. Instead, I'll help put OSIS
on life support in light of the rather inconvenient disappearance
of
14 matches
Mail list logo
