Hi,
I've got the whole of the Bible to validate, but have problems with the
header.
The basic header which is output from usfm2osis.pl allows the whole Bible to
validate (using Notepad++ and a copy of the Osis schema saved as a local
file).
?xml version=1.0 encoding=UTF-8?
osis
Hi Konstantin,
Following your announcement, I have added a new section to
http://www.crosswire.org/wiki/Current_Projects#Windows_Mobile_platform
http://www.crosswire.org/wiki/Current_Projects#Windows_Mobile_platform
in the hope that this will help recruit other volunteers.
David
Konstantin
Friday, March 26 and Saturday, March 27, 2009 in San Jose.
Join us at http://www.bibletechconference.com/ BibleTech:2010 to explore
the intersection of Bible study and technology. This two-day conference is
designed for publishers, programmers, webmasters, educators, bloggers and
anyone
I can not answer your question (nor have I tried it myself right now (with
being at work), but as I think that our osis2mod procedure will kill all of
the header stuff anyway, it is probably not necessary to add anything beyond
what is given by usfm2osis.pl
Peter
Original-Nachricht
The International Conference on Computing and Mission (
http://www.iccm-europe.org/ ICCM ) is an annual informal gathering of women
and men who have a common interest in computers and mission. We share a
vision of cooperation for effective use of technology bringing the Gospel to
every nation.
Have you tried validating it with http://xml-copy-editor.sourceforge.net/
XML Copy Editor , instead of with Notepad++ with the XML Tools plugin?
It's generally a good idea, just in case there is a subtle bug in the
plugin.
- David
johnduffy-2 wrote:
Hi,
I've got the whole of the Bible
Peter is right. Whatever you add in the header is useful mainly for
yourself. That kind of information usually goes in the conf file of the
module.
Daniel
Peter von Kaehne wrote:
I can not answer your question (nor have I tried it myself right now (with being at
work), but as I think that
I can add that jEdit has a nice validator plugin that I usually use.
Notepad++ can only validate to a certain length in your document.
Daniel
David Haslam wrote:
Have you tried validating it with http://xml-copy-editor.sourceforge.net/
XML Copy Editor , instead of with Notepad++ with the XML
Peter,
I've corrected the wrong type of double quotes, and then worked on it. In
the end, the validation schema only recognises the following Dublin Core
items, apart from Title:
creator, identifier, language, scope.
When I commented out the following , it validated, and would not validate
with
John,
header allows teiHeader as a child and this element can contain any
content. My guess is that it was provided as a way to maintain the
Dublin Core header elements from a TEI document. Perhaps Chris can comment.
In Him,
DM
On 11/02/2009 09:08 AM, johndu...@cgcf.net wrote:
Hi,
I've got
David, There was only one problem when using XML Copy Editor, apart from
lots of spelling issues, but that was probably
Daniel, I'll comment out the info just to keep it there, and copy it over
into the conf file as required.
Thanks
John Duffy
-Original Message-
From: Daniel Owens
On Fri, 30 Oct 2009, Troy A. Griffitts wrote:
Thanks for the detailed analysis Eeli-- most appreciated. If you have a
chance to make the changes you suggest and determine they work better
for you, I'd be happy to commit the delta. Do you think this is
something we can do without changing
Hi.
I just browsed the GNUstep pages again after some time:
http://www.gnustep.org/
The only missing things that hindered a MacSword 1.x port to GNUstep was
the missing WebKit and SearchKit.
Now a working WebKit port is there. Still in early stages but it is working.
SearchKit would need to be
Hi,
I just released Alkitab Bible Study 2.4 which is available at
http://www.kiyut.com/products/alkitab/index.html
The source code is available under development section.
What's New:
- Add search text capture for Global History
- Add Synchronize View
- Add alkitab.icns for Mac OSX
- Add basic
--- On Sun, 11/1/09, Greg Hellings greg.helli...@gmail.com wrote:
From: Greg Hellings greg.helli...@gmail.com
Subject: Re: [sword-devel] Understanding the structure of generic books and
their relationship with TreeKey.
To: SWORD Developers' Collaboration Forum sword-devel@crosswire.org
The code i was using already made use of those methods. However, i could go
down no further than the root level. I am wondering how to obtain the
children for the keys i've only been able to get. Here's is the current,
relevant part of the code i am using:
//
{
Dear Rendezvous,
In addition to Matthew and Greg's helpful reply, have a look at the
genbookutil in the utilities folder of the source:
https://crosswire.org/svn/sword/trunk/utilities/genbookutil.cpp
This utility exercises the basic SWORD genbook features. At the top is
a basic printTreeKey
This might be better. I'm probably still missing some logic.
void getSectionsList(TreeKey tk, list l)
{
l.append (tk-getText());
if tk-hasChildren()
{
tk-firstChild();
getSectionsList(tk, l);
}
while tk-nextSibling()
{
Just so there isn't confusion, I've corrected mine to match Troy's
link. My chaining back up was incorrect.
void getSectionsList(TreeKey *tk, list l)
{
l.append (tk-getText());
if tk-hasChildren()
{
tk-firstChild();
getSectionsList(tk, l);
It's probably easier to create a new TreeKey along the way, otherwise it
won't work properly (going to the parent at the end will lose the place in
the sibling iteration).
void getSectionsList(TreeKey tk, list l)
{
do {
l.append (tk-getText());
if (tk-hasChildren())
Here is the valid version of your header. Comments follow.
?xml version=1.0 encoding=UTF-8?
osis xmlns=http://www.bibletechnologies.net/2003/OSIS/namespace;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.bibletechnologies.net/2003/OSIS/namespace
DM Smith wrote:
John,
header allows teiHeader as a child and this element can contain any
content. My guess is that it was provided as a way to maintain the
Dublin Core header elements from a TEI document. Perhaps Chris can comment.
In Him,
DM
All of the Dublin Core header elements are
22 matches
Mail list logo
